CHIRP

Noted issue reported with GA-510, had the same issue and contacted Radioddity Support with the same issue. Their response below:

After confirming with our technical team, the new batch of GA-510 radios might not be programmed with the programming software we provided before or Chirp. We will make a new programming software as soon as possible. We will be really appreciated it if you could keep the radio and help test the new programming software. The new programming software should come out this week and I will send it to you once I get it.

Received beta software from radioddity that allowed me to communicate with ga-510; however the radio still does not clone with CHIRP. Have downloaded and installed chirp-next-20230606 and continue getting message "Radio did not respond to clone request"

Ron Jones wrote in #note-2:

Received beta software from radioddity that allowed me to communicate with ga-510; however the radio still does not clone with CHIRP. Have downloaded and installed chirp-next-20230606 and continue getting message "Radio did not respond to clone request"

I dug out my Retevis RA685 and CHIRP-next downloads from and uploads to this radio just fine. What I would suspect after reading your previous note is that the "magic" string that is required to initiate the cloning process has changed in manufacturing. It is kind of like a password and if what CHIRP sends to the radio does not match what the radio is expecting, the radio ignores the request.

It requires access to the new programming software to reverse engineer what this new "magic" string is. Radioddity needs to share this "new" software with a CHIRP developer that is interested in investigating/addressing this problem. Please DO NOT upload the programming software to this ticket.

Jim KC9HI

I have the same issue, and Radioddity's response is here:

The new batch of GA-510 has a new chip, and it is not currently able to re-adapt the Chirp by updating the firmware. If you need to program the GA-510, please program it via CPS. Hope for your understanding.

My Debug log is here:

[2023-06-20 21:16:11,590] chirp.logger - DEBUG: CHIRP next-20230617 on Win32 (Unknown 10.0:19045) (Python 3.10.8)
[2023-06-20 21:16:11,657] chirp.wxui - DEBUG: Using locale: en_US (276)
[2023-06-20 21:16:11,661] 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-06-20 21:16:11,666] 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-06-20 21:16:11,922] main - INFO: Python/3.10.8 // Windows/Windows-10-10.0.19045-SP0 // CHIRP/next-20230617 // wx/4.2.0 msw (phoenix) wxWidgets 3.2.0
[2023-06-20 21:16:12,044] chirp.wxui.main - INFO: Ignoring dist stock conf DE Freenet Frequencies.csv because same name found in user dir
[2023-06-20 21:16:12,044] chirp.wxui.main - INFO: Ignoring dist stock conf EU LPD and PMR Channels.csv because same name found in user dir
[2023-06-20 21:16:12,044] chirp.wxui.main - INFO: Ignoring dist stock conf FR Marine VHF Channels.csv because same name found in user dir
[2023-06-20 21:16:12,044] chirp.wxui.main - INFO: Ignoring dist stock conf KDR444.csv because same name found in user dir
[2023-06-20 21:16:12,044] chirp.wxui.main - INFO: Ignoring dist stock conf NOAA Weather Alert.csv because same name found in user dir
[2023-06-20 21:16:12,045] chirp.wxui.main - INFO: Ignoring dist stock conf UK Business Radio Simple Light Frequencies.csv because same name found in user dir
[2023-06-20 21:16:12,045] chirp.wxui.main - INFO: Ignoring dist stock conf US 60 meter channels (Center).csv because same name found in user dir
[2023-06-20 21:16:12,045] chirp.wxui.main - INFO: Ignoring dist stock conf US 60 meter channels (Dial).csv because same name found in user dir
[2023-06-20 21:16:12,045] chirp.wxui.main - INFO: Ignoring dist stock conf US CA Railroad Channels.csv because same name found in user dir
[2023-06-20 21:16:12,045] chirp.wxui.main - INFO: Ignoring dist stock conf US Calling Frequencies.csv because same name found in user dir
[2023-06-20 21:16:12,045] chirp.wxui.main - INFO: Ignoring dist stock conf US FRS and GMRS Channels.csv because same name found in user dir
[2023-06-20 21:16:12,045] chirp.wxui.main - INFO: Ignoring dist stock conf US MURS Channels.csv because same name found in user dir
[2023-06-20 21:16:12,045] chirp.wxui.main - INFO: Ignoring dist stock conf US Marine VHF Channels.csv because same name found in user dir
[2023-06-20 21:16:12,441] chirp.wxui.main - INFO: Server reports next-20230619 is latest
[2023-06-20 21:16:18,570] chirp.wxui.clone - DEBUG: Using port 'COM3'
[2023-06-20 21:16:18,570] chirp.wxui.clone - DEBUG: Selected
[2023-06-20 21:16:18,688] chirp.wxui.clone - DEBUG: Serial opened: Serial(port='COM3', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=0.25, xonxoff=False, rtscts=False, dsrdtr=False) (rts=True dtr=True)
[2023-06-20 21:16:19,206] chirp.drivers.ga510 - DEBUG: Ack was b''
[2023-06-20 21:16:19,206] 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-06-20 21:16:24,101] chirp.wxui.clone - WARNING: Stopping clone thread

Ron Jones wrote in #note-2:

Received beta software from radioddity that allowed me to communicate with ga-510; however the radio still does not clone with CHIRP. Have downloaded and installed chirp-next-20230606 and continue getting message "Radio did not respond to clone request"

Have Radioddity email me to make arrangements for me do get a copy of their beta software.

Jim KC9HI

Jim Unroe wrote in #note-8:

Ron Jones wrote in #note-2:

Received beta software from radioddity that allowed me to communicate with ga-510; however the radio still does not clone with CHIRP. Have downloaded and installed chirp-next-20230606 and continue getting message "Radio did not respond to clone request"

Have Radioddity email me to make arrangements for me do get a copy of their beta software.

Jim KC9HI

I have a copy of the software that will program the radio provided by Radioddity, I can forward the email if you'd like?

From Radioddity:

The new batch of GA-510 radios might not be programmed with the programming software we provided before or Chirp.

Here is the CPS for the new version. Please kindly help test if it can solve the problem.
https://radioddity.s3.amazonaws.com/GA-510%20CPS%20v1.00.36.zip

Cheers,
Kate
Radioddity Support Team

Any updates on progress with this? More than happy to test bleeding edge builds unless I end up returning this radio due to its inability to be programmed via CHIRP

Still relevant issue, just got this radio and had to use the bad OEM software.

Alexander Park wrote in #note-12:

Still relevant issue, just got this radio and had to use the bad OEM software.

I don't know if someone is into it.

I managed to read from the new CPS software. It seems the new magic is PSEARCH instead of the old PROGROMBFHU.
CPS tries 3 times, toggles some signals and repeats once and gives up because the radio is not responding (correct, cause its a tiny serial sniffer written in Python).

But I am not able to trace the communication with the radio. I use com0com and hub4com on windows but CPS will not communicate via the virtual splitter.
Hope someone can help.

KR

bsilver eagle wrote in #note-14:

Hello All,

The GA-510 2023 behaves very closely to the UV17. The magics in the driver need changed to:

    _magic = b"PSEARCH"
    _magic_response_length = 8
    _magics = [[b"PASSSTA", 3], [b"SYSINFO", 1],
               [b"\x56\x00\x00\x0A\x0D", 13], [b"\x06", 1],
               [b"\x56\x00\x10\x0A\x0D", 13], [b"\x06", 1],
               [b"\x56\x00\x20\x0A\x0D", 13], [b"\x06", 1],
               [b"\x56\x00\x00\x00\x0A", 11], [b"\x06", 1],
               [b"\xFF\xFF\xFF\xFF\x0C\x44\x4d\x52\x31\x37\x30\x32", 1],
               [b"\02", 8], [b"\x06", 1]]
    _fingerprint = b"\x06" + b"DMR1702"

Using that set of commands the memory can be dumped from 0x0000 to 0xF0000 in 0x1000 increments.

However, the GA-510 appears to have memory blocks that move around every time it is written with CSP. Sometimes the channel memory is at 0x4000, sometimes at 0xe000, etc. The settings move around in memory in a similar fashion. It is not clear where in memory to read where the proper offsets are. Manually setting the proper #seekto addresses in the UV17 driver will populate the Memories and Settings tabs.

I believe the channel struct is:

    #seekto 0x4040;
    struct {
      lbcd rxfreq[4];
      lbcd txfreq[4];
      u8 unused1;
      ul16 rxtone;
      ul16 txtone;
      u8 unknown1:1,
         bcl:1,
         pttid:2,
         unknown2:1,
         wide:1,
         power:2;
      u8 scode:4,
         unknown6:2,
         freq_hop:1,
         scan:1;
      u8 unknown4;
    } memories[128];

It is not clear to me how to get these values into the Chirp GUI or how to handle the memory pages. I have attached two dumps for anyone who wishes to pursue this further. One has radio settings at 0x4000 and the other has channel settings at 0x4000. 'ABABA FGFGFG' are the Boot 1 & 2 lines to easily locate the settings block.

Any updates or progress with this Radio and it working with CHIRP?