Bug #10514
openGA510 not responding to clone request
0%
Description
I'm attempting to program a new Radioddity GA510. Have downloaded the latest version of CHIRP and seated the cable (which came with the radio) firmly. When I try to "download from radio," I get a consistent error message: "RADIO DID NOT RESPOND TO CLONE REQUEST." (Note: the radio screen briefly displays a "program" icon before the error message appears on my computer screen.
The app is calling for USB-SERIAL (CH340) COM9, which appears to be functioning with current driver. I am using a PC running Windows 10.
DEBUG LOG:
[2023-04-13 13:06:37,213] chirp.logger - DEBUG: CHIRP next-20230411 on Win32 (Unknown 10.0:19045) (Python 3.10.8)
[2023-04-13 13:06:37,343] chirp.wxui - DEBUG: Using locale: en_US (276)
[2023-04-13 13:06:37,356] chirp.wxui - DEBUG: Translation loaded=True for CHIRP: en_US (de,el,en_US,es,fr,hu,it,nl,pl,pt_BR,ru,tr_TR,uk_UA,zh_CN) from C:\Program Files (x86)\CHIRP\chirp\locale
[2023-04-13 13:06:37,367] chirp.wxui - DEBUG: Translation loaded=False for wxstd: en_US (af,an,ar,ca,ca@valencia,co,cs,da,de,el,es,eu,fa_IR,fi,fr,gl_ES,hi,hr,hu,id,it,ja,ka,ko_KR,lt,lv,ms,nb,ne,nl,pl,pt,pt_BR,ro,ru,sk,sl,sq,sv,ta,tr,uk,vi,zh_CN,zh_TW)
[2023-04-13 13:06:38,099] main - INFO: Python/3.10.8 // Windows/Windows-10-10.0.19045-SP0 // CHIRP/next-20230411 // wx/4.2.0 msw (phoenix) wxWidgets 3.2.0
[2023-04-13 13:06:38,134] chirp.wxui.main - INFO: Ignoring dist stock conf DE Freenet Frequencies.csv because same name found in user dir
[2023-04-13 13:06:38,134] chirp.wxui.main - INFO: Ignoring dist stock conf EU LPD and PMR Channels.csv because same name found in user dir
[2023-04-13 13:06:38,135] chirp.wxui.main - INFO: Ignoring dist stock conf FR Marine VHF Channels.csv because same name found in user dir
[2023-04-13 13:06:38,135] chirp.wxui.main - INFO: Ignoring dist stock conf KDR444.csv because same name found in user dir
[2023-04-13 13:06:38,135] chirp.wxui.main - INFO: Ignoring dist stock conf NOAA Weather Alert.csv because same name found in user dir
[2023-04-13 13:06:38,135] chirp.wxui.main - INFO: Ignoring dist stock conf SE Jaktradio 155MHz.csv because same name found in user dir
[2023-04-13 13:06:38,136] chirp.wxui.main - INFO: Ignoring dist stock conf UK Business Radio Simple Light Frequencies.csv because same name found in user dir
[2023-04-13 13:06:38,136] chirp.wxui.main - INFO: Ignoring dist stock conf US 60 meter channels (Center).csv because same name found in user dir
[2023-04-13 13:06:38,136] chirp.wxui.main - INFO: Ignoring dist stock conf US 60 meter channels (Dial).csv because same name found in user dir
[2023-04-13 13:06:38,136] chirp.wxui.main - INFO: Ignoring dist stock conf US CA Railroad Channels.csv because same name found in user dir
[2023-04-13 13:06:38,136] chirp.wxui.main - INFO: Ignoring dist stock conf US Calling Frequencies.csv because same name found in user dir
[2023-04-13 13:06:38,137] chirp.wxui.main - INFO: Ignoring dist stock conf US FRS and GMRS Channels.csv because same name found in user dir
[2023-04-13 13:06:38,137] chirp.wxui.main - INFO: Ignoring dist stock conf US MURS Channels.csv because same name found in user dir
[2023-04-13 13:06:38,137] chirp.wxui.main - INFO: Ignoring dist stock conf US Marine VHF Channels.csv because same name found in user dir
[2023-04-13 13:06:38,428] chirp.wxui.main - INFO: Server reports next-20230411 is latest
[2023-04-13 13:06:43,568] chirp.wxui.clone - DEBUG: Using port 'COM9'
[2023-04-13 13:06:43,569] chirp.wxui.clone - DEBUG: Selected
[2023-04-13 13:06:43,570] chirp.wxui.clone - DEBUG: Serial opened: Serial
[2023-04-13 13:06:44,090] chirp.drivers.ga510 - DEBUG: Ack was b''
[2023-04-13 13:06:44,090] chirp.wxui.clone - ERROR: Failed to clone: Radio did not respond to clone request
Traceback (most recent call last):
File "chirp\wxui\clone.py", line 66, in run
File "chirp\drivers\ga510.py", line 369, in sync_in
File "chirp\drivers\ga510.py", line 69, in do_download
File "chirp\drivers\ga510.py", line 58, in start_program
chirp.errors.RadioError: Radio did not respond to clone request
[2023-04-13 13:06:49,420] chirp.wxui.clone - WARNING: Stopping clone thread
Updated by Dan Smith about 1 year ago
This is almost definitely a radio connectivity issue (i.e. wrong serial port, radio turned off, cable not fully inserted). However, you might want to walk back to an older release (0409 or older) to see if that changed anything. There's a potential bug (#10515) in the latest release that could possibly be causing this for you, depending on your cabling.
Updated by Andy S 4 months ago
This is definitly not a connectivity problem. This also happen when the old Radioddity tool (CPS) is used.
Theres a new GA510-Version which needs the new Radioddity tool due to new protocol.
So CHIRP should support the new type also.
Is there a way to analyze the traffic easily? I'll try it myself then.
Maybe try to sniff CPS comunication? What will be the best tool for that?
Updated by Jim Unroe 4 months ago
- I read the instructions above set to Yes
Andy S wrote in #note-2:
This is definitly not a connectivity problem. This also happen when the old Radioddity tool (CPS) is used.
Theres a new GA510-Version which needs the new Radioddity tool due to new protocol.So CHIRP should support the new type also.
Is there a way to analyze the traffic easily? I'll try it myself then.
Maybe try to sniff CPS comunication? What will be the best tool for that?
The radio was changed in a way that broke CHIRP support. According to issue #10600 which duplicates this ticket, the currently shipping radios don't work with to original factory CPS, either. They require a completely different CPS in order to program them.
A change this significant would require that a developer have physical access to one of these radios and the appropriate programming software.
Updated by Andy S 4 months ago
Jim Unroe wrote in #note-3:
Andy S wrote in #note-2:
This is definitly not a connectivity problem. This also happen when the old Radioddity tool (CPS) is used.
Theres a new GA510-Version which needs the new Radioddity tool due to new protocol.So CHIRP should support the new type also.
Is there a way to analyze the traffic easily? I'll try it myself then.
Maybe try to sniff CPS comunication? What will be the best tool for that?The radio was changed in a way that broke CHIRP support. According to issue #10600 which duplicates this ticket, the currently shipping radios don't work with to original factory CPS, either. They require a completely different CPS in order to program them.
A change this significant would require that a developer have physical access to one of these radios and the appropriate programming software.
Ok. I read the other issue. Seems no one is into it? I have a new radio, the new CPS software and I am able to program Python. Just need a way to sniff the communication. What is the best way here?
Updated by Jim Unroe 4 months ago
Andy S wrote in #note-4:
Ok. I read the other issue. Seems no one is into it? I have a new radio, the new CPS software and I am able to program Python. Just need a way to sniff the communication. What is the best way here?
What I started out using was a program called Portmon. I had to give it up because it is limited to working 32-bit Windows 7 and older operating systems.
I did a lot of searching for a replacement. I found a free version that was limited to 5 sessions per day and only 20 minutes per session. After becoming sufficiently annoyed by these limitations I finally found and paid the $69 registration fee for a program called Serial Port Monitor. I have upgraded it a few time (they offer a 50% discount for upgrades) but eventually paid to get their lifetime upgrade plan so any future upgrades are free (I just upgraded it a few days ago).
Some say that Wireshark can do it. I looked at it a few times but have not been able to figure it out. This might be due to a laziness on my part since I already have a lot of money invested in something that is working well for me.