Bug #11532
closedBug reading from Retevis RT622 - looks similar to issue 10080
100%
Description
I am trying to download an image from a Retevis RT622 that was previously programmed with an older version of CHIRP.
I get the error message "Radio identification failed."
I have a few Retevis RT622s and only have this issue with this one. Using the same cable and exact setup works fine with other Retevis RT622 radios.
I updated to the latest CHIRP, I tried different USB ports and adapters from USB C to A and they all seem to be the same, not working with this one radio only (and working fine with the others).
I see a past issue about 2 years ago - issue number 10080. (chirpmyradio.com/issues/10080)
Which looks to be the same symptoms.
I tried to read my problematic radio using the modified driver as in that issue but I get an error message that the driver is incompatible. I expect CHIRP has changed that much since then and also see that issue was in Legacy and I am using NEXT.
I think this radio was probably originally programmed with Legacy but fairly sure most of mine were also.
I see from issue number 10080 —
“It seems that the OEM CPS can "zero" the identification string. Apparently it can be edited to be anything that you want.
For now, this patch includes this new identification string to the list of strings known strings. If additional strings appear in the future, another solution will need to be found.”
I am on a Mac and never used the OEM software on any of my radios. So perhaps the string has been corrupted somehow?
I wonder if there is some way to get this back -
I am happy to try anything and also report any more details if I missed something.
CHIRP is amazing and very helpful (use it all the time) Thank you for all the work. I wish I could contribute more.
Files