Project

General

Profile

Actions

Bug #10304

closed

Icom E90 not working in new ChirpX

Added by Reverend Neil about 1 year ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
01/22/2023
Due date:
% Done:

100%

Estimated time:
Chirp Version:
next (py3)
Model affected:
Icom E90
Platform:
Windows
Debug Log:
I read the instructions above:

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

Icom_IC-E90_20230122.img (11.5 KB) Icom_IC-E90_20230122.img example working in old chirp Reverend Neil, 01/22/2023 09:12 PM
chirp_debug-du2ui22d.txt (3.46 KB) chirp_debug-du2ui22d.txt Reverend Neil, 01/23/2023 06:57 AM
icx90.py (36 KB) icx90.py Dan Smith, 01/23/2023 08:40 PM
chirp_debug-3bahz15q.txt (3.97 KB) chirp_debug-3bahz15q.txt Reverend Neil, 01/23/2023 09:15 PM
chirp_debug-uvz7sgot.txt (3.51 KB) chirp_debug-uvz7sgot.txt opening img err only Reverend Neil, 01/23/2023 09:20 PM
chirp_debug-62e5ds98.txt (5.89 KB) chirp_debug-62e5ds98.txt exception on edit specials Reverend Neil, 01/25/2023 06:37 AM
Icom_IC-E90_2023-01-25a tmp .img (11.6 KB) Icom_IC-E90_2023-01-25a tmp .img img, but any img will do Reverend Neil, 01/25/2023 06:38 AM

Related issues

Related to Bug #10316: Radios with negative-index specials are not editableClosedDan Smith01/25/2023

Actions
Related to Bug #10317: Icom IC-E90 does not properly handle set_memory() of specialsClosedDan Smith01/25/2023

Actions
Actions #1

Updated by Dan Smith about 1 year 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 .

Actions #2

Updated by Reverend Neil about 1 year ago

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.

Actions #3

Updated by Dan Smith about 1 year 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.

Actions #4

Updated by Reverend Neil about 1 year ago

ok, now radio communicates, downloaded process ok, but program did not open any edit window with the memory data...

Actions #5

Updated by Reverend Neil about 1 year ago

this file is purely for the error when trying to open a pre-existing img from oldchirp.(22/1 image as above)

Actions #6

Updated by Reverend Neil about 1 year ago

fyi, i guess what is done here, will also apply to the icom t90 also (japan version of e90)

Actions #7

Updated by Dan Smith about 1 year 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!

Actions #8

Updated by Dan Smith about 1 year ago

  • Status changed from Feedback to Closed
  • % Done changed from 0 to 100
Actions #9

Updated by Reverend Neil about 1 year 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.

Actions #10

Updated by Reverend Neil about 1 year ago

Thank you for your worthy efforts :-)

Actions #11

Updated by Dan Smith about 1 year 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
Actions #12

Updated by Reverend Neil about 1 year ago

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

Actions #13

Updated by Reverend Neil about 1 year 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.

Actions #14

Updated by Dan Smith about 1 year ago

  • Related to Bug #10316: Radios with negative-index specials are not editable added
Actions #15

Updated by Dan Smith about 1 year ago

  • Related to Bug #10317: Icom IC-E90 does not properly handle set_memory() of specials added
Actions #16

Updated by Dan Smith about 1 year 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.

Actions

Also available in: Atom PDF