Bug #10304
closedIcom E90 not working in new ChirpX
100%
Description
no longer works with new chirpx.
working ok on old chirp. new chirpx unable to open saved img, error is 'NoneType' object has no attribute 'get_mappings'
2nd, now tried to read radio, error is " failed to communicate with the radio, object of type 'lcfFrame' has no len()
Reads/W ok in old chirp fyi again.
Im available to test in gmt0 evenings after work.
Files
Updated by Dan Smith almost 2 years ago
We need a debug log (find it in the help menu) after you reproduce the problem so we can see what's going on. See How_To_Report_Issues .
Updated by Reverend Neil almost 2 years ago
- File chirp_debug-du2ui22d.txt chirp_debug-du2ui22d.txt added
attached debug. who knows why i didnt do that on original post with files.
to confirm, on closing new chirp, and opening old chirp, with no cable changes, reads writes fine.
Updated by Dan Smith almost 2 years ago
Can you try the attached module?
To use this, enable developer mode in the Help menu, then restart chirp. After you restart it, use File->Load Module and pick this file, then try to communicate with your radio.
Your log file didn't include the image loading "get mappings" part, so after you try with this module, if you can still reproduce that behavior, please do so and capture a debug log again.
Updated by Reverend Neil almost 2 years ago
- File chirp_debug-3bahz15q.txt chirp_debug-3bahz15q.txt added
ok, now radio communicates, downloaded process ok, but program did not open any edit window with the memory data...
Updated by Reverend Neil almost 2 years ago
- File chirp_debug-uvz7sgot.txt chirp_debug-uvz7sgot.txt added
this file is purely for the error when trying to open a pre-existing img from oldchirp.(22/1 image as above)
Updated by Reverend Neil almost 2 years ago
fyi, i guess what is done here, will also apply to the icom t90 also (japan version of e90)
Updated by Dan Smith almost 2 years ago
- Assignee set to Dan Smith
- Target version set to chirp-py3
Thanks Neil, sounds like I squashed the cloning problem and I see the issue with opening the old image (which is the same problem after clone not opening a window). I won't have it fixed before your end-of-GMT-0-day but I think I have what I need, thanks!
Updated by Dan Smith almost 2 years ago
- Status changed from Feedback to Closed
- % Done changed from 0 to 100
Applied in changeset github|ae5c7a581e7fa8c6724af5f7c1f1eac3290053e3.
Updated by Reverend Neil almost 2 years ago
suspect new issue, just downloaded 24th daily. now includes this update.
upload, download, open seems ok.
are you able to edit the section at bottom of memory list? the vfo section. i get 'Error has occured' then a minus number.
Updated by Reverend Neil almost 2 years ago
Thank you for your worthy efforts :-)
Updated by Dan Smith almost 2 years ago
Please, I need:
- The image you captured
- The memory you're editing in that image
- Exactly what change you're making
- The debug log after you reproduce it
Updated by Reverend Neil almost 2 years ago
- File chirp_debug-62e5ds98.txt chirp_debug-62e5ds98.txt added
- File Icom_IC-E90_2023-01-25a tmp .img Icom_IC-E90_2023-01-25a tmp .img added
unable to edit any special mems at bottom after mem 499. change a frequency then get a error in - range. think minus it relates to mem location as number starts from bottom -1 to -71 nears top of special list.
general chirp issue -
highlight a selection of rows, DEL key does not delete /blank rows unlike old chirp.
have to right click on a memory number and select delete xx rows.
This is on any img or radio mnfgr DL
Updated by Reverend Neil almost 2 years ago
UPDATE TO ABOVE special mems editing
I now dont think its purly with icom e90.
my yaesu 857d, does the same error with its special locations at bottom too.
Updated by Dan Smith almost 2 years ago
- Related to Bug #10316: Radios with negative-index specials are not editable added
Updated by Dan Smith almost 2 years ago
- Related to Bug #10317: Icom IC-E90 does not properly handle set_memory() of specials added
Updated by Dan Smith almost 2 years ago
Yep, there are still some issues in the E90 driver, but there are some fundamental ones with radios that use negative indexing for their special channels. I'm going to keep this closed for the original issue, but I created two new bugs referenced from this one that will represent the other two issues.