I too bought this radio and downloaded the software from the Midland website. The free Midland software is lacking in so many features that I use in Chirp and other paid programming software. Since I bought the radio for a mini go kit, would like the ability to use Chirp for this radio. I need to have standardized frequency channels across all my radios. Thanks!

I think the new AnyTone 778UV driver will support his radio, but the current version won't automatically detect it. However, I don't have this model to hand to try it out.

To help get this radio supported it would be great if someone could give it a go and give a little feedback. If that's you, here's how:

Update your Chirp installation to the latest.¶

With your radio connected, choose 'Download from radio' from the 'Radio' menu, and specify your serial port. Choose 'AnyTone' as the manufacturer, and '778UV' as the model, then hit OK.¶

Chirp will warn you that this is an experimental driver, say yes if you want to continue.¶

This won't work, and you'll see an error, hopefully something like 'radio version not in allowed list' - please attach a screenshot here.¶

Thank you!

Joe Milbourn wrote:

I think the new AnyTone 778UV driver will support his radio, but the current version won't automatically detect it. However, I don't have this model to hand to try it out.

To help get this radio supported it would be great if someone could give it a go and give a little feedback. If that's you, here's how:

Update your Chirp installation to the latest.¶

With your radio connected, choose 'Download from radio' from the 'Radio' menu, and specify your serial port. Choose 'AnyTone' as the manufacturer, and '778UV' as the model, then hit OK.¶

Chirp will warn you that this is an experimental driver, say yes if you want to continue.¶

This won't work, and you'll see an error, hopefully something like 'radio version not in allowed list' - please attach a screenshot here.¶

Thank you!

I loaded the latest chirp on a PC that didn't have it originally (Win10). Plugged in my Midland programming cable, it was seen in device manager as COM5. Started up CHIRP, went to download from the radio, selecting Anytone 778UV and when it tried to download data from the radio, the radio said "PC MODE", and shortly afterwards CHIRP said "Radio did not respond" and I found the radio was locked up. I power cycled the radio, did it again and now this time and EVERY attempt afterwards, the radio shows PC Mode, CHIRP says CLONING for 3 seconds, then the pop up goes away, chirp has a gray screen like nothing happened and second later the radio reboots BUT NO ERROR. No error from chirp or the radio.

Sorry I didn't get the screenshot the first time - I wanted to make sure I could repeat the problem and couldn't (other than the 'nothing happened' part).

Hope this helps.

Dave

I loaded the latest chirp on a PC that didn't have it originally (Win10). Plugged in my Midland programming cable, it was seen in device manager as COM5. Started up CHIRP, went to download from the radio, selecting Anytone 778UV and when it tried to download data from the radio, the radio said "PC MODE", and shortly afterwards CHIRP said "Radio did not respond" and I found the radio was locked up. I power cycled the radio, did it again and now this time and EVERY attempt afterwards, the radio shows PC Mode, CHIRP says CLONING for 3 seconds, then the pop up goes away, chirp has a gray screen like nothing happened and second later the radio reboots BUT NO ERROR. No error from chirp or the radio.

Thanks Dave! That's an error, but not the error I was expecting. Please could you repeat that once more and then attach the chirp debug log? Instructions how to find it at How_To_Report_Issues.

Dave, if you still have, or can re-create the USB capture you mention above please would you share it? Also, a saved file from the Midland software, doesn't matter what's in it, would be interesting to understand how similar this radio is to AT778.

Thanks
Joe

Edit:

• I downloaded the Retevis RT-95 software but when I ran it it complained about the radio model not matching and the only choice was to overwrite it to continue - so I unplugged the programming cable and let it error out.
• Finally found the Anytone programming software, it did the same thing as the Retevis software. I too chickened out of letting it do whatever overwrite it was going to do.

The programming software for all 3 looked the same GUI wise. They must be checking the model number when proceeding.

Dave

David Schmidt wrote:

When trying to load the new driver, I got this error.
"Unable to load module: invalid syntax"

thank you for trying! could you just confirm that you've got the Python file and not the HTML version? you need to click the link and then select download from the next page.

David Schmidt wrote:

Ah, that was it! I now have a new error however. See attached.

Thanks Dave - you need to choose 'Midland' as the radio vendor and 'DBR2500' as the model at the download from radio prompt.

Joe Milbourn wrote:

David Schmidt wrote:

Ah, that was it! I now have a new error however. See attached.

Thanks Dave - you need to choose 'Midland' as the radio vendor and 'DBR2500' as the model at the download from radio prompt.

Ah, thank you. I'll give it a go tonight and let you know the results. I appreciate you working on this!
Dave

David Schmidt wrote:

Hi Joe, it works! Not quite 100% right but it did download the contents and I was able to save the image (attached).

Awesome!

• I have a few disabled channels (public service freqs) and they're showing up with weird offset frequencies and the duplex value is not 'none'. Examples in the '2-CHIRPvsFactorySW.JPG'

Those offsets are programmed by the vendor s/w, in the example you've got open in 2-CHIRPvsFactorySW.JPG, the vendor s/w has defaulted the tx frequency to 136MHz, and the offset really is 25.55MHz.

However, the driver I gave you doesn't handle tx off, so the duplex value doesn't get set of off correctly. The driver I'll commit does do that properly.

• the CTCSS encode and decode values are entered in the factory download but in chirp only the activated mode shows up. (maybe this is normal).

The radio's model of tone encode/decode gets mapped onto chirp's model during import, and they're not quite the same, so they'll look different, but will (should?) work just the same. E.g. for your memory #1 you've got CTCSS encode and decode active, and set to the same frequency which chirp calls TSQL and just lists the tone once. If the tones were different chirp would call that 'Cross' with a cross mode of 'Tone->Tone' and list both tones. See DevelopersToneModes for a better explaination.

Looks very serviceable as is though! I can always touch it up in the factory software.

Hopefully you won't need to!

Thanks for trying things out, much appreciated.

J