New Model #3941

AnyTone 5888UV III

Added by Greg March over 6 years ago. Updated over 2 years ago.

Status:Feedback Start date:08/19/2016
Priority:Normal Due date:
Assignee:- % Done:


Target version:chirp-daily
Chirp Version:daily Equipment Loan Offered:Yes


I'd like to add a request for the new AnyTone triband mobile. I will include a sample .dat file from the radio here.

AnyTone-20160819-02.dat - AnyTone .dat file - three frequencies loaded, 2m, 1.25m and 70cm (12.9 kB) Greg March, 08/19/2016 08:06 am

AnyTone-20160819-02.fre - I noticed a .fre file as well. Including it here if it helps (273 Bytes) Greg March, 08/19/2016 08:06 am

Related issues

duplicated by New Model #4415: AnyTone 5888UV III Rejected 01/16/2017
duplicated by New Model #6317: Anytone AT-5888UV III TriBand Closed 12/22/2018
duplicated by New Model #6697: AnyTone AT-5888UVIII Closed 04/12/2019
duplicated by New Model #6949: AnyTone 5888uv III Closed 07/28/2019

Associated revisions

Revision 3425:ce301ee484b0
Added by Brad Schuler about 2 years ago

[anytone_iii] Add the new radio AnyTone 5888UV-III

Related to issue #3941

Add support for the tri-band AnyTone 5888UV-III.
Limited inclusion of 2-tone, 5-tone, and scramble settings.

Revision 3426:1418baa380c1
Added by Dan Smith about 2 years ago

Fix crash in anytone_iii when memobj isn't loaded

The new anytone_iii driver inspected the memory object during get_features(),
just to count the memories, which shouldn't be necessary. This papers over
that failure with the statically-defined value, but ideally, we'd just replace
the dynamic check with a static number. However, this fixes the build, and
is the least amount of change.

Related to #3941

Revision 3464:786c6252a1ed
Added by Dan Smith almost 2 years ago

Remove errant ui import from anytone_iii driver

The patch for #3941 imports a module from the UI for some reason, but
does not use it. This seems to have been breaking the PPA build because
we don't have gtk as a build-dep (for good reason). Drivers should be
independent of the UI and are not allowed to import things from it. Since
this driver wasn't actually using the import, removing it should be simple.

Fixes #8493


Updated by Bernhard Hailer over 2 years ago

  • Status changed from New to Feedback
  • Target version set to chirp-daily
  • Chirp Version changed from 0.4.0 to daily

Does the AnyTone AT-5888UV drive of Chirp work for this radio?

Updated by Doug Ausmus over 2 years ago

In (duplicate) ticket #6317, there were TWO volunteers to loan a radio for this, but every issue (including all duplicates) is marked "no" for equipment loan.

What is needed to kick this up a notch? Looks like it has been sitting for a number of years now and has gotten requests every year since 2016, including offers of equipment loan.

Both Doug Ausmus (me, offered on 1/14/2019) and Craig Raper (offered on 2/9/2019) can likely still provide a radio loaner to make this happen.

@Bernhard Hailer asked a question in (dup) #6317, "Is the III different from the AT-5888UV implemented in Chirp?" and the answer is, "When I tested it a year ago the tri-band or ID caused chirp to fail on the III tri-band radio. It seems to be expecting the old dual-band version."

In 2016 two files were submitted by Greg March. What else is needed? The factory software is a real pain and most of my other radios are using chirp.

Thanks and 73-

Updated by Doug Ausmus over 2 years ago

Please change Equipment Loan to YES

Updated by Bernhard Hailer over 2 years ago

  • Equipment Loan Offered changed from No to Yes

Done. Having stated that:

The addition of a new radio to Chirp requires two things:
1) a volunteer developer who takes the task to work on this driver,
2) availability of test equipment, such as a loaner radio (see Rules For Loaning A Radio).
Unfortunately, you need to wait until both conditions have been met.

Or, you could decide to get your hands dirty yourself - check Wiki, "Developers".

Also available in: Atom PDF