CHIRP

I am also receiving this error on a daily build, installed on Linux Mint.

I have a ICOM ID-51A Plus 2 and receiving the same errors as mentioned above post on Windows 10

Gerry Carpinetti wrote:

I have a ICOM ID-51A Plus 2 and receiving the same errors as mentioned above post on Windows 10

Anyone able to fix this problem. I just downloaded the most current version on Windows 10 and having this same problem.

Not to turn this into a "me too" fest, but I'm having the same issue with this radio on both Windows 10 and Mac OS.

Thank you, the log is helpful. This radio has a new version number in its firmware:

[2020-08-28 12:39:39,639] chirp.drivers.icf - INFO: This model: 000: 33 90 00 03 00 00 00 00   3.......
[2020-08-28 12:39:39,639] chirp.drivers.icf - INFO: Supp model: 000: 33 90 00 02 00 00 00 00   3.......

A developer needs to look into it and see what it takes to talk with this version.

Is the Plus2 still not supported? I'm not sure if this ticket is up to date, but I'm experiencing similar behavior with version daily-20221025 in November 2022. Thanks.

Would additional detail, logs, etc., help get this resolved?

I updated Chrip, enabled developer mode, and loaded the plus2 module. I get a red background. Then I do download from radio, 51aplus2. The radio gives one quick beep then I get a dialog "An error has occurred. Failure to communicate with the radio: unpack requires a string argument of length 4." But the radio keeps going with "CLONE OUT" for a while longer, gives a couple quick beeps, and returns to normal. So it seems the command to "read" went to the radio, which then sent its output, but Chirp isn't able to parse what comes back from the radio.

Are there additional debug logs I could provide that would help?

Thanks

Hi Marc, that looks like it might be a different bug that I introduced in the last day. Can you tell me what sort of cable you're using?

Regardless, you might want to back up two versions from current and try the module there to rule out the difference. You can find the older versions here:

https://trac.chirp.danplanet.com/chirp_daily/

I would try 20221109.

Actually, that could also be that the 51plus and 51plus2 differ by more than I expected. If you don't mind trying the older version to rule that out, that would help. If it turns out not to help, then that probably means it's the other thing and I'll generate a different module for you to try.

And my cable is ICOM OPC-2350LU, plus a USB-A to microUSB adapter cable. Both came with the radio used, so I don't know if the adapter cable was originally included with the ICOM cable or not. But the combination worked fine for me when using the ICOM upload/download software, so I'm reasonably confident they work OK.

Okay, that's good news that the older builds behave the same. That means I didn't break anything :)

It likely means the Plus and Plus2 are more different than I expected, so I'll have to work on that a bit. I'm able to open your ICF file with the module loaded, so hopefully the memory format isn't much different.

Awesome, thanks for the report. I will need to do some work to make this into something I can put in the main build, but the hard work is done at least.

Yes, today's build is broken on windows and mac because of bug #10130.

Trying to tweak values in chirp and uploading them to see if the radio agrees would be my next step (which I see you've just now done - very nice). Also, if you can, a debug log from both an upload and download using tomorrow's build (since today's was broken) would be helpful as it will log some extra information for me.

In general, I don't spend a lot of time decoding the settings in the radio (i.e. the stuff under the Settings tab) except for very popular radios. The channels are very laborious to enter manually on the radio, and decoding the channel format once works for all 1000 memories. The settings on the other hand are ALL different and a lot of work. Thus, there's a lot of bang-for-buck on the channels, much less so on the settings.

If there's something specific in the settings that is likely to be helpful to have exposed in chirp, I can see about adding it for you, but no promises. It takes an enormous amount of time to decode all of them (especially for a complex radio like this) and other volunteers have spent years decoding all the bits from simpler and wildly more popular radios like the UV5R.