CHIRP

This radio appears to be the same as the Anytone AT-779UV, which has already been listed here: https://chirp.danplanet.com/issues/8953

I do agree that the Radioddity closely resembles the AnyTone AT-779UV. CHIRP, however, does not support the AT-779UV. CHIRP does support the AnyTone AT-778UV but I don't expect that the AT-778UV model selection will support the AT-779UV model selection.

To support this model (or its AnyTone variant) will will most likely require getting the Radioddity DB20-G and/or Anytone AT-779UV radio, compatible programming cable and programming software into the hands of a volunteer developer that is interested in doing the reverse engineering.

Jim KC9HI

I'' give it a try tonight and report back.

Alex Martin wrote:

I'' give it a try tonight and report back.

After any error message, close CHIRP and then attach the debug.log file that was generated.

Jim KC9HI

So, on another note, I am curious if macOS CHIRP works with all 'supported' radios because I was unable to confirm if the supplied programming cable worked in macOS (as in did it have a drive?r), so for now let's not worry about those logs. I was able to confirm the software provided by Radiodiity worked in Windows, so Tried both AT-778UV and AT-778UV VOX and here is the debug log (From Windows):

[2021-07-26 16:43:35,407] chirp.ui.reporting - DEBUG: Checking for updates
[2021-07-26 16:43:35,562] chirp.ui.reporting - DEBUG: Server reports version daily-20210724 is latest
[2021-07-26 16:43:55,842] chirp.ui.mainapp - DEBUG: User selected AnyTone 778UV on port COM4
[2021-07-26 16:43:55,950] chirp.ui.clone - DEBUG: Clone thread started
[2021-07-26 16:43:56,450] chirp.ui.reporting - DEBUG: Reporting exception
[2021-07-26 16:43:56,450] chirp.ui.common - ERROR: -- Exception: --
[2021-07-26 16:43:56,450] chirp.ui.common - ERROR: Traceback (most recent call last):
File "chirp\ui\clone.pyo", line 255, in run
File "chirp\drivers\anytone778uv.pyo", line 695, in sync_in
File "chirp\drivers\anytone778uv.pyo", line 495, in do_download
RadioError: No initial response from radio.

[2021-07-26 16:43:56,450] chirp.ui.common - ERROR: ----------------
[2021-07-26 16:43:56,450] chirp.ui.clone - ERROR: Clone failed: No initial response from radio.
[2021-07-26 16:43:56,513] chirp.ui.clone - DEBUG: Clone thread ended
[2021-07-26 16:43:56,513] chirp.ui.reporting - DEBUG: Reporting model usage: AnyTone_778UV,download,True
[2021-07-26 16:43:56,528] chirp.ui.inputdialog - ERROR: --- Exception Dialog: No initial response from radio. ---
[2021-07-26 16:43:56,528] chirp.ui.inputdialog - ERROR: Traceback (most recent call last):
File "chirpw", line 68, in
AttributeError: 'NoneType' object has no attribute 'split'

[2021-07-26 16:43:56,528] chirp.ui.inputdialog - ERROR: ----------------------------
[2021-07-26 16:43:56,528] chirp.ui.reporting - DEBUG: Reporting exception
[2021-07-26 16:44:15,122] chirp.ui.mainapp - DEBUG: User selected AnyTone 778UV VOX on port COM4
[2021-07-26 16:44:15,232] chirp.ui.clone - DEBUG: Clone thread started
[2021-07-26 16:44:15,733] chirp.ui.reporting - DEBUG: Reporting exception
[2021-07-26 16:44:15,733] chirp.ui.common - ERROR: -- Exception: --
[2021-07-26 16:44:15,733] chirp.ui.common - ERROR: Traceback (most recent call last):
File "chirp\ui\clone.pyo", line 255, in run
File "chirp\drivers\anytone778uv.pyo", line 695, in sync_in
File "chirp\drivers\anytone778uv.pyo", line 495, in do_download
RadioError: No initial response from radio.

[2021-07-26 16:44:15,733] chirp.ui.common - ERROR: ----------------
[2021-07-26 16:44:15,733] chirp.ui.clone - ERROR: Clone failed: No initial response from radio.
[2021-07-26 16:44:15,809] chirp.ui.clone - DEBUG: Clone thread ended
[2021-07-26 16:44:15,809] chirp.ui.reporting - DEBUG: Reporting model usage: AnyTone_778UV VOX,download,True
[2021-07-26 16:44:15,809] chirp.ui.inputdialog - ERROR: --- Exception Dialog: No initial response from radio. ---
[2021-07-26 16:44:15,809] chirp.ui.reporting - DEBUG: Reporting exception
[2021-07-26 16:44:15,809] chirp.ui.inputdialog - ERROR: Traceback (most recent call last):
File "chirpw", line 68, in
AttributeError: 'NoneType' object has no attribute 'split'

[2021-07-26 16:44:15,809] chirp.ui.inputdialog - ERROR: ----------------------------

For reference as mentioned above, not sure if the programming cable is working correctly on macOS (I do see a /dev/cu.usbserial-1440 as an option in Radio -> Download from Radio that is not there with the cable unplugged (and that is the one I am selecting), but here is that debug log:

[2021-07-26 16:55:08,267] chirp.ui.reporting - DEBUG: Server reports version daily-20210724 is latest
[2021-07-26 16:55:23,121] chirp.ui.mainapp - DEBUG: User selected AnyTone 778UV on port /dev/cu.usbserial-1440
[2021-07-26 16:55:23,131] chirp.ui.clone - DEBUG: Clone thread started
[2021-07-26 16:55:23,632] chirp.ui.reporting - DEBUG: Reporting exception
[2021-07-26 16:55:23,632] chirp.ui.common - ERROR: -- Exception: --
[2021-07-26 16:55:23,633] chirp.ui.common - ERROR: Traceback (most recent call last):
File "/Applications/CHIRP.app/Contents/Resources/chirp/chirp/ui/clone.py", line 255, in run
self.__radio.sync_in()
File "/Applications/CHIRP.app/Contents/Resources/chirp/chirp/drivers/anytone778uv.py", line 695, in sync_in
self._mmap = do_download(self)
File "/Applications/CHIRP.app/Contents/Resources/chirp/chirp/drivers/anytone778uv.py", line 495, in do_download
raise e
RadioError: No initial response from radio.

[2021-07-26 16:55:23,633] chirp.ui.common - ERROR: ----------------
[2021-07-26 16:55:23,633] chirp.ui.clone - ERROR: Clone failed: No initial response from radio.
[2021-07-26 16:55:23,635] chirp.ui.clone - DEBUG: Clone thread ended
[2021-07-26 16:55:23,648] chirp.ui.reporting - DEBUG: Reporting model usage: AnyTone_778UV,download,True
[2021-07-26 16:55:23,649] chirp.ui.reporting - DEBUG: Reporting exception
[2021-07-26 16:55:23,649] chirp.ui.inputdialog - ERROR: --- Exception Dialog: No initial response from radio. ---
[2021-07-26 16:55:23,649] chirp.ui.inputdialog - ERROR: Traceback (most recent call last):
File "/Applications/CHIRP.app/Contents/MacOS/../Resources/chirp/chirpw", line 76, in
os.putenv("LANG", langs[0])
IndexError: list index out of range

[2021-07-26 16:55:23,649] chirp.ui.inputdialog - ERROR: ----------------------------
[2021-07-26 16:59:50,387] chirp.ui.mainapp - DEBUG: User selected AnyTone 778UV VOX on port /dev/cu.usbserial-1440
[2021-07-26 16:59:50,394] chirp.ui.clone - DEBUG: Clone thread started
[2021-07-26 16:59:50,895] chirp.ui.reporting - DEBUG: Reporting exception
[2021-07-26 16:59:50,895] chirp.ui.common - ERROR: -- Exception: --
[2021-07-26 16:59:50,895] chirp.ui.common - ERROR: Traceback (most recent call last):
File "/Applications/CHIRP.app/Contents/Resources/chirp/chirp/ui/clone.py", line 255, in run
self.__radio.sync_in()
File "/Applications/CHIRP.app/Contents/Resources/chirp/chirp/drivers/anytone778uv.py", line 695, in sync_in
self._mmap = do_download(self)
File "/Applications/CHIRP.app/Contents/Resources/chirp/chirp/drivers/anytone778uv.py", line 495, in do_download
raise e
RadioError: No initial response from radio.

[2021-07-26 16:59:50,895] chirp.ui.common - ERROR: ----------------
[2021-07-26 16:59:50,895] chirp.ui.clone - ERROR: Clone failed: No initial response from radio.
[2021-07-26 16:59:50,897] chirp.ui.clone - DEBUG: Clone thread ended
[2021-07-26 16:59:50,910] chirp.ui.reporting - DEBUG: Reporting model usage: AnyTone_778UV VOX,download,True
[2021-07-26 16:59:50,911] chirp.ui.inputdialog - ERROR: --- Exception Dialog: No initial response from radio. ---
[2021-07-26 16:59:50,911] chirp.ui.reporting - DEBUG: Reporting exception
[2021-07-26 16:59:50,911] chirp.ui.inputdialog - ERROR: Traceback (most recent call last):
File "/Applications/CHIRP.app/Contents/MacOS/../Resources/chirp/chirpw", line 76, in
os.putenv("LANG", langs[0])
IndexError: list index out of range

[2021-07-26 16:59:50,911] chirp.ui.inputdialog - ERROR: ----------------------------

Jim Unroe wrote:

... CHIRP, however, does not support the AT-779UV.
My apologies for the confusion - my bad.

Alex Martin wrote:

So, on another note, I am curious if macOS CHIRP works with all 'supported' radios...

Then open another ticket. This one is about support for the DB20-G.

Jim KC9HI

Jim Unroe wrote:

Alex Martin wrote:

So, on another note, I am curious if macOS CHIRP works with all 'supported' radios...

Then open another ticket. This one is about support for the DB20-G.

Jim KC9HI

FYI, I was able to get macOS to see the USB to Serial port cord correctly. Sorry to mention that here before, just did it so I could add both logs.

Alex Martin wrote:

Jim Unroe wrote:

Alex Martin wrote:

So, on another note, I am curious if macOS CHIRP works with all 'supported' radios...

Then open another ticket. This one is about support for the DB20-G.

Jim KC9HI

FYI, I was able to get macOS to see the USB to Serial port cord correctly. Sorry to mention that here before, just did it so I could add both logs.

Two things regarding macOS and your programming cable.

1. /dev/cu.usbserial-1440 would indicate to me that your programming cable identifies as having a Prolific type USB-to-Serial chip. Nearly all programming cables with a Prolific chip were made with an unauthorized copy of the chip. The driver auto installed by Windows and available for macOS are intentionally incompatible with these chips.

One workaround is to get a programming cable made with a different chip.

The workaround for Windows is to download, install and select the older Prolific v3.2.0.0 driver that was available before the were crippled. See this miklor.com "USB Cables & Drivers":https://www.miklor.com/COM/UV_Drivers.php page for a link to the driver and instructions for selecting it.

The workaround for macOS is to purchase a 3rd party driver that doesn't care if the chip is genuine or not. I purchased mine from "mac-usb-serial.com":https://www.mac-usb-serial.com/

1. The CHIRP MacOS Unified Application build for macOS does not include the Python future module. Radios like the AnyTone AT-778UV and Radioddity GA-510 that require the future module will not show up in CHIRP when the future module is not present.

Jim KC9HI

Since it appears that someone, perhaps it is Radioddity that is offering to LOAN a DB-20G
(Equipment Loan Offered: Yes), can the CHIRP engineers PLEASE get the Windows version working for this radio?? I own one and have been waiting since July 2021, I can't be alone out here. This very economical mobile radio HAS been around for quite a while and has very popular sales, which means there are a LOT of them out in use. Please HELP! (the Radioddity programming software is horrible.)

Keith Benicek wrote:

Since it appears that someone, perhaps it is Radioddity that is offering to LOAN a DB-20G
(Equipment Loan Offered: Yes), can the CHIRP engineers PLEASE get the Windows version working for this radio?? I own one and have been waiting since July 2021, I can't be alone out here. This very economical mobile radio HAS been around for quite a while and has very popular sales, which means there are a LOT of them out in use. Please HELP! (the Radioddity programming software is horrible.)

I would consider looking at it, but I don't do loans. It takes many hours working closely and constantly with the factory software, which, as you have pointed out, is no picnic.

The Retevis RA25 looks similar to the Radioddity DB-20G, so it is likely that either of those could be useful in the project started.

Jim KC9HI

FCC applications state that the Retevis and radioddity models of the radio are electrically identical to the anytone 779UV, and use it as the basis for their marketing name change.

Whoever wants to get this radio working in chirp, please let me know. I am willing to send a free radio.

I would love support for this radio as well. Ya'll aren't the only ones out there. I'm sure there's a pretty broad base considering the price and functionality of the radio.

Just wanted to comment to add another voice to those who'd like to see support for this radio, in case such things are a consideration. I would think there must be quite a few of these radios out there, especially considering the Anytone and Retevis versions.

One more who would love to see this supported (and then be able to lose the Radioddity app). My son and I have the db20-g, does that count as 2 more? ;)

This is indeed the same as the 779UV as previously stated. Feel like this issue should be closed as a duplicate.

@Alex_Martin: please send a DB20-G into CHIRP so they can work on it.

@Alex_Martin: or an AT-779UV; whichever you have and are willing to send in.

Jim Unroe wrote in #note-3:

I do agree that the Radioddity closely resembles the AnyTone AT-779UV. CHIRP, however, does not support the AT-779UV. CHIRP does support the AnyTone AT-778UV but I don't expect that the AT-778UV model selection will support the AT-779UV model selection.

To support this model (or its AnyTone variant) will will most likely require getting the Radioddity DB20-G and/or Anytone AT-779UV radio, compatible programming cable and programming software into the hands of a volunteer developer that is interested in doing the reverse engineering.

Jim KC9HI

Would like to send you my Radioddity DB-20G (or another Chirp developer) so you can get it added to Chirp. Let me know the process for this.

I have never participated in this project, but I am a software developer with an AT-779UV of my own. I’m interested in contributing. Where do I start?

Peter Baker,

I found this link:
https://chirp.danplanet.com/projects/chirp/wiki/DevelopersAdd_a_Radio

J M wrote in #note-25:

Peter Baker,

I found this link:
https://chirp.danplanet.com/projects/chirp/wiki/DevelopersAdd_a_Radio

I have been working on this in my spare time since my post. I’ve figured out all the data types and done analysis on the serial commands. There is one set of values related to tones that have some unusual correlation I haven’t figured out, but once I get done mapping everything out and confirming all properties are accepted via serial using PowerShell, I’ll start working in Python.

J M wrote in #note-25:

Peter Baker,

I found this link:
https://chirp.danplanet.com/projects/chirp/wiki/DevelopersAdd_a_Radio

Peter Baker wrote in #note-26:

J M wrote in #note-25:

Peter Baker,

I found this link:
https://chirp.danplanet.com/projects/chirp/wiki/DevelopersAdd_a_Radio

I have been working on this in my spare time since my post. I’ve figured out all the data types and done analysis on the serial commands. There is one set of values related to tones that have some unusual correlation I haven’t figured out, but once I get done mapping everything out and confirming all properties are accepted via serial using PowerShell, I’ll start working in Python.

J M wrote in #note-25:

Peter Baker,

I found this link:
https://chirp.danplanet.com/projects/chirp/wiki/DevelopersAdd_a_Radio

Maybe you've already seen this, but I just noticed that some other folks appear to also be/have been working on this: http://intrepid.danplanet.com/pipermail/chirp_devel/2023-July/007168.html

Just thought I'd point that out.

Xikteny R wrote in #note-27:

Maybe you've already seen this, but I just noticed that some other folks appear to also be/have been working on this: http://intrepid.danplanet.com/pipermail/chirp_devel/2023-July/007168.html

Just thought I'd point that out.

That's me! I had figured out almost all of the memory map and started customizing an existing driver to pull down the data. But got pulled onto other things and I haven't touched the code in a few months. IIRC, I got it to start reading but throws an error, it uses a different checksum than the driver I based it on and I was fixing that.

Peter Baker wrote in #note-26:

I’ve figured out all the data types and done analysis on the serial commands. There is one set of values related to tones that have some unusual correlation I haven’t figured out, but once I get done mapping everything out and confirming all properties are accepted via serial using PowerShell, I’ll start working in Python.
<<

Peter, send me a DM about where in memory you can't figure out the tones config, I'll let you know if I figured that spot out.

To whom it may concern,

Will we be able to change the frequency settings of the radio, like we can do with the UV-5R? For example, the chip (RDA1846) of the BaoFeng UV-5R allows for more open frequency ranges e.g.- the 1.25m band, and through 520Mhz to 600Mhz, etc...

For clarification, will we be able to open the frequency range to the full capability of the SDR chip?

Gary, anyway you could start uploading your module progress to the issue so others can take a look and poke around?

Oh also, if you haven't already noticed the stock software has a bug where after you open a data file it will not write any radio settings that you haven't opened a dialog for. In other words, if you open a data file you need to click on the "Function Setup" and "Information of Scanning" to actually get that stuff to load into memory before sending to your radio or it doesn't send. That's how mine has always worked, this software is terrible.

D'oh. User error. Please disregard the previous report.

I had the radio configured to chirp.drivers.btech.DB25G by mistake.

Charles Randall wrote in #note-34:

D'oh. User error. Please disregard the previous report.

I had the radio configured to chirp.drivers.btech.DB25G by mistake.

Were you able to make headway after changing the driver?

No traction on this? My python script is still working for me but way less convenient than just having it come out of Chirp. I am not bright enough to write a module for this.

Usage:

dat_to_csv.py
csv_to_dat.py [,]

Provide filenames without extensions. [] are optional parameters. Leave a display 'line' blank to not update it. (You have to access CPS 'Function Setup' to actually write display lines and other settings to the radio.) Creates files with the same name as the source data filename. csv_to_dat.py will not overwrite an existing DAT file, but create one with '_New' appended. These scripts will deal with the scan limit and VFO memories numbered 501 through 506. Scan Limits: PL1=501 PH1=502 PL2=503 PH2=504 and VFOs: VFO1=505 VFO2=506. dat_to_csv.py will extract them from the DAT file to the CSV file. If they are not in your CSV file, csv_to_dat.py will copy them from your settings file. A lot of the simple special features are encoded in the CSV file comment field. dat_to_csv.py will provide warnings for features that are not handled. See dat_to_csv.py for file format comments.

Sorry, the usage lines didn't process... Trying again:

dat_to_csv.py source_dat_filename
csv_to_dat.py source_settings_dat_filename source_csv_filename [upper_display_line,lower_display_line]

Fred: Cowboy Pilot uses the Retevis Ra-25 software. In my previous experimentation, I found the Ra-25 generated code plugs to NOT be compatible with the Anytone/Radioddity CPS software. Are you getting different results?

Michael, I just saw Fred's scripts today I'm planning on trying them out with the RA25, I'll let you know if it works.

So I'm almost certain it won't work out of the box, it looks for a text string at 258D, the RA25 has "RA_25UV" instead of AT779UV. It seriously could be as simple as changing it though, I'm guessing they are basically the same. I'll do some experiments when I get some time.

csv_to_dat.py has a test at line 170 for the radio model string. Try
adding the RA_25UV string to the if statement test with an 'or' and let
everyone knows if that works. Thanks!

On 1/10/2025 9:08 PM, Matt Bickford wrote:

My comment is before attempting to use Fred's Python files. I do not have the Ra-25; only the DB20-G and AT-779UV. When I downloaded the Retevis CPS software to create a code-plug I found that the Ra-25 code plug would not load into my Radioddity or Anytone CPS software. It appeared to be proprietary.

Can you post or email a DB20-G CPS data file that was read in from the radio so I can take a look at it and see if it has a similar structure to the AT-779UV CPS data file? An RA-25 file would be useful too... I only have an AT-779UV. Thanks!

RT Software has just released its CPS software for $25 download, for the Anytone AT-779UV and it has been reported that it works with the DB20-G as well. They claim the delay to develop their version, was due to the wiring of the USB cable that was enclosed with these radios (?!?) and they claim their software works with these enclosed cables. They do offer their USB cable either separately or as a combo price.

Given that I have no experience with Python, I will acquire this software, rather than learn Python for one purpose only.

Perhaps someone can reverse engineer this software to figure out how to get Chirp to work with these radios, as well.