Hi

It can be a new unknown variant (again...) please repeat the procedure and catch the log and attach it to this issue for reviewing, that will allow us to identify the new second ID...

Cheers from Pavel (driver developer)

Got it, it seems like a new variant in the wild.

Will process ASAP and came back with a test for you to make.

73 Pavel CO7WT

Wondering if you need further information :)

To the 9 people who have emailed me about this. No I have not heard anything back yet. I suggest maybe submitting your debug logs too ? I am just someone who uses chirp, not one of the developers.

That worked! I am able to both read from radio and upload to radio. Thanks Pavel. 73 & Happy New Year. Ron WB2PKR

Hi Ron,

Glad it worked, take your time and try to test it a little more to check everything is in place.

Then on your comments about "extensive" test (or lack of them, meaning all worked ok) I will push the changes into main Chirp.

73 Pavel CO7WT
Happy New Year to All!

Hi Pavel,

I cant say Ive done a comprehensive regressive test, but I have verified that this fix did not corrupt any of my data in the rig that was having the problem nor the older firmware version of this rig that I have.
All looks good to me.

I have stored memories on 2m, 1.25m and 70cm as well as GMRS, FRS, Marine VHF, FM Broadcast, and some local govt and biz VHF/UHF.
I also have customized my advanced settings.

All appears to be OK with my single config file for this rig when using the fix to connect to the newer firmware as well as an older firmware version of this rig.

Thx. 73 & HNY Ron WB2PKR