Aliasing for radio clones

Version 2 (Pavel Milanes, 06/29/2016 01:34 pm) → Version 3/4 (Dan Smith, 07/01/2016 09:50 am)

h1. Aliasing for radio clones.

If you have a question like the following this page has info you need to know about, keep reading:

My FooBar-300 radio shows itself as China_radio-100 once I opened a saved image of it, it’s that normal?

Since June 2016 Chirp support a feature called radio aliasing, and it’s used to represent a clone of a real radio in the user interface for the users convenience. This is more a trick in the guts of Chirp for the developers but it has a quirk the users need to know about.

h2. The problem.

Some radio manufacturers – mostly from Asia – are assembling some re-branded radios by request with custom names, at the end this radios are no more than perfect clones of a previous existing radios from the Chirps point of view. The perfect example for this is the Baofeng UV-5R with all the [[Baofeng_UV5R_Variants]].

This is no problem at all for using the radios in the day to day work, work on it’s features and performance, but for Chirp developers it’s: we need that every radio to have its has it’s own and unique identification code or ID to get it clearly identified.

Before the alias feature implementation you have to know before hand that your Juentai JT-6188 Mini was just a clone of the QYT KT-8900 and so on with other vendors/models.

This has brought a lot of confusion and problems on the user side. The bugs side, the site issues and questions on the user mailing list are proof prof of that, that; with users asking about support for specific radio models that are no more than that just clones of others.

h2. The fix.

The first approach was to educate the users by putting comments on the [[Supported_Radios]] page about the clones and the right radio to select, and answering issues on the site and emails on the user list. That proved to be just a partial fix, as newcomers keep asking the same questions all over again (Who reads read the manual anyway?)

Recently we added Then, in a new debate in the developers list, Dan came across with this alias feature. with this feature that allows developers has the option to register the radio clones as what they are: clones. This allows us clones (technically aliases for a real radio) and allow to show them on the users interface as a distinct it’s own VENDOR/MODEL for the user's convenience.

users pleasure and peace of mind.

h2. A quirk you will notice and a workaround.

This alias feature has a issue we can't easily fix in software: when you download an and image of a radio that is it’s a clone and save it, that image will be detected as became the real radio once opened again in Chirp. This may be confusing as Chirp and you opened an image of you radio, but Chirp is suddenly saying it is will found yourself asking a different model (i.e. similar question to the model your radio is cloned from). one on top of this page.

For example, if you read and save an image of a Juentai JT-6188 Mini, when you re-open it from the file in your hard drive, you will find found Chirp telling you that this image is for a QYT KT-8900, not the Juentai JT-6188 Mini. This Mini, this is completely normal and you are safe using it for your clone radio.

It’s confusing, we know; but remember that Chirp’s team always encourage to keep a few images for every radio and do not cross use them with other radio models or variants. For that reason we have implemented also a suggested naming schema on the saving of a img file to cope with that.

Once you want to save a copy of your radio data you will find Chirp is suggesting you to use the {vendor}_{model}_{date}.img schema, for the above example you will receive the suggestion to use this: Juentai_JT-6188 Mini_{date}.img

So when you look for and old image file of your radio you will always know that this image was for that particular radio vendor & model as it’s stated on the file name, this will help you with the mentioned quirk in the aliasing feature.

h2. Present and future.

So far we have just a few clones or aliases listed in Chirp. We on Chirp, we hope other developers will use this functionality jump to implement it for the remaining aliases, specially for the Baofeng UV-5R huge family of clones, but it’s we know its’t a huge task and will take time.

Some example radio So far this radios are implemented as clones at the time of this writing: or aliases:

* Juentai_JT-6188 Mini (clone of a QYT KT-8900 variant)
* Juentai_JT-6188 Plus (clone of Waccom Mini-8900)
* QYT KT-UV980 (clone of Waccom Mini-8900)
* Jetstream JT2705M (clone of Waccom Mini-8900)
* Sainsonic GT-890 (clone of a QYT KT-8900 variant)
* Luiton LT-588UV (clone of a QYT KT-8900 variant)

We will update this page with more clones as they are implemented or ported to Chirp.