CHIRP-next model report #10937
openlatest Retevis RT1 not found
Description
my work has 15 retevis RT1 radios. the first 10 purchased 2 years ago all work with Chirp-next just fine. the last batch of 5 we got from amazon this year get "no response from radio". the new 5 radios program fine with retevis CPS and retevis cable under windows7 in virtualbox so i do have correct cable and connection. i also tried with legacy same "no response from radio". is there something i'm missing? i also notice the new radios "talk" different. the old ones say "power high", the new ones say "high power".???
Updated by Jim Unroe 6 months ago
Most likely the radios have been changed in a way that made them incompatible with CHIRP. Unfortunately you didn't follow the instructions that you claimed to have read. There is not much that can be done without access to the 'new' radio or the information the should have been provided based on the instructions.
Updated by gaspo gaspo 6 months ago
my apologies, and thank you for your time and reply, there was no debug generated afaict if thats what you mean? i do have one radio that is flaky i could donate to the cause, and one already taken apart that failed. i'd love to help the chirp project in any way possible. if i missed something please let me know i thank you for your patience and time.
Updated by Jim Unroe 6 months ago
gaspo gaspo wrote in #note-2:
my apologies, and thank you for your time and reply, there was no debug generated afaict if thats what you mean? i do have one radio that is flaky i could donate to the cause, and one already taken apart that failed. i'd love to help the chirp project in any way possible. if i missed something please let me know i thank you for your patience and time.
I don't know how that can be. Just the simple act of launching CHIRP always creates a debug.log file. It may not contain any useful information, but I won't know that until I can see it.
So launch CHIRP-next. Try to download from the radio. Once it prompts with the "no response from radio", cancel the prompt, tap 'Help' in the menu bar and either choose 'Open debug log' or "Show debug log location'. Attach the latest debug.log to this issue.