Personal Page of DM3MAT

Some radios are actually identical to others. They also identify themselves as a different radio. An example for such a radio is the Retevis RT3S, this radio is simply a relabeled TyT MD-UV390. The RT3S actually identifies itself as a MD-UV390. From the perspective of the CPS, these two radios are indistinguishable. Consequently, qdmr and dmrconf will always identify the RT3S as a MD-UV390.

There are, however, virtually identical radios. These are radios that actually identify themselves as different models but the firmware, communication protocol and codeplug is basically identical to another model. An example for such virtually identical models are the AnyTone AT-D868UV and the BTech DMR-6X2. Each model identifies itself correspondingly and thus is distinguished by the CPS. Some of these relationships between virtually identical models are known to qdmr and dmrconf. In these cases, the CPS will treat these radios as identical.

Some of these close relationships between models are not known to dmrconf. In these cases, dmrconf will stop with an error that a radio is unknown although it actually supported as a different model. In these rare cases, it is possible to override the radio detection using the --radio option.

This option is usually used to specify the type whenever the radio model is not detected. This option also overrides the model detection and thus allows to handle virtually identical radios. For example, if the relation ship between the AT-D868UV and the DMR-6X2 would have not been known to dmrconf, a codeplug could read anyway from the device by calling

dmrconf read --radio=d868uv codeplug_6x2.yaml

Here the radio detection (resulting the detection of a DMR-6X2) gets overridden and the radio is handled as a AT-D868UV.

If you know of such virtually identical radios that dmrconf does not recognize, consider filing an issue at the bug tracker.