Project

General

Profile

Actions

Bug #11652

closed

Some memories read as 4MHz offset

Added by Pres Waterman 9 months ago. Updated 9 months ago.

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

100%

Estimated time:
Chirp Version:
next
Model affected:
Icom ID-51
Platform:
Windows
Debug Log:
I read the instructions above:
Yes

Description

(Describe what you were doing)
Using CHIRP to program iCom ID-51A

(Describe what you expected to happen)
Memories whose offset shows as 5MHz to be 5MHz

(Describe what actually happened instead)
Memories 7,8,10,11,12 actually are 4MHz (on the display as well as iCom CS-51 factory software)

(Has this ever worked before? New radio? Does it work with OEM software?)

ALSO every memory CHIRP programs as TSQ shows ERROR when read on iCom CS-51 software

Also, in CHIRP, where are the D-star specific fields such as URCALL, RPT1, RPT2, MYCALL?


Files

config.txt (1.7 KB) config.txt Pres Waterman, 11/01/2024 02:25 PM
Icom_ID-51_20241101.img (127 KB) Icom_ID-51_20241101.img Pres Waterman, 11/01/2024 02:25 PM
debug_log.txt (136 KB) debug_log.txt Pres Waterman, 11/01/2024 02:25 PM
id_31_51.py (13 KB) id_31_51.py Dan Smith, 11/01/2024 04:30 PM
config.txt (1.72 KB) config.txt Pres Waterman, 11/02/2024 08:28 AM
Icom_ID-51_20241101.img (127 KB) Icom_ID-51_20241101.img Pres Waterman, 11/02/2024 08:28 AM
debug_log.txt (14.6 KB) debug_log.txt Pres Waterman, 11/02/2024 08:28 AM
id_31_51.py (13.1 KB) id_31_51.py Updated module Dan Smith, 11/02/2024 08:34 AM
config.txt (1.72 KB) config.txt Pres Waterman, 11/02/2024 09:35 PM
Icom_ID-51_20241103.img (127 KB) Icom_ID-51_20241103.img Pres Waterman, 11/02/2024 09:35 PM
debug_log.txt (11.7 KB) debug_log.txt Pres Waterman, 11/02/2024 09:35 PM

Related issues 1 (0 open1 closed)

Related to Bug #11657: ID31/51 some TSQL/DTCS show as "error" in CS-31Closed11/03/2024

Actions

Updated by Pres Waterman 9 months ago

[Uploaded from CHIRP next-20241101]

Actions #2

Updated by Dan Smith 9 months ago

Please, only one actual problem per issue. It makes the paperwork complicated to have multiple things.

I found and fixed the issue with the offset. Please test and confirm the attached module with these instructions: LoadingTestModules.

Please file another ticket for the TSQ issue and I'll look at/fix that separately (I see it too while testing with your image locally).

The DV callsign settings are in the properties dialog on DV memories. Right-click, properties on a memory.

Actions #3

Updated by Dan Smith 9 months ago

  • Subject changed from Some emeories read as 4MHz offset to Some memories read as 4MHz offset
Actions #4

Updated by Pres Waterman 9 months ago

Hi Dan

When this started I read the ID-51A into CHIRP, removed/moved some memories
and noticed CHIRP displayed 5MHz but the radio got 4MHz on some memories. I
then read the radio with iCom CS-51, corrected the TSQ and 4MHz issues, and
wrote to the radio. I then sent you the bug report.

To comply with your followup request, I read the radio into CHIRP and
re-wrote it back. I did NOT load the test module, as I wanted to prove that
without the fix the 4MHz problem exists and with the module it goes away.

It seems to have fixed itself. I didn't try the module (as I couldn't tell
if it was successful). Both CHIRP and CS-51 now read the radio without
the 4MHz (or the TSQ) issues.

Thanks for your thoughts

-Pres

On Fri, Nov 1, 2024 at 7:31 PM Dan Smith redmine@chirpmyradio.com wrote:

Actions #5

Updated by Dan Smith 9 months ago

Just downloading and re-uploading the image from the radio will not touch any bits. You have to edit a memory with chirp to get it to make any changes, so it didn't just fix itself, you just weren't tickling the bug.

If you could, save an image of the fixed radio for later. Then:

  • Open the file you attached here and upload to the radio
  • Confirm it's wrong
  • Close the file
  • Load the module
  • Open the file again
  • Edit something about one of the broken memories (just changing the name is enough)
  • Upload that back to the radio and confirm it looks right

I don't have an ID-51, so I can't test this, so your help in confirming is appreciated.

Actions #6

Updated by Pres Waterman 9 months ago

Will do.

Night

-Pres

On Fri, Nov 1, 2024 at 11:17 PM Dan Smith redmine@chirpmyradio.com wrote:

Updated by Pres Waterman 9 months ago

[Uploaded from CHIRP next-20241101]

Good morning Dan.

I opened the file I sent you, wrote to the radio and confirmed memory #10 was 4MHz.

I closed the file, applied the patch, opened the file, renamed KD2UQK W to KD2UQK-W, wrote to the radio.

Memory 10, 11 and 12 are now 3.2MHz versus 5MHz. Interesting.

NOT changing #7 and #8 left them at 4MHz. Renaming #10, 11 and 12 made them 3.2MHz.

Actions #8

Updated by Dan Smith 9 months ago

Aha, yes, I didn't fully fix the bug on one half of the cycle, so that makes sense. Glad we tested!

Please repeat but with this new module applied, thanks.

Updated by Pres Waterman 9 months ago

[Uploaded from CHIRP next-20241101]

The latest fix worked! Good job

Actions #10

Updated by Dan Smith 9 months ago

  • Related to Bug #11657: ID31/51 some TSQL/DTCS show as "error" in CS-31 added
Actions #11

Updated by Dan Smith 9 months ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF