Ubbe you forgot to say the TRX scans Voice Channels the same as a CHEAP Chinese DMR Radios and does not TRUNK TRACK DMR SYSTEMS like the x36's SDSx00's 996P2's or the 325P2's do.
Whistlers way of tracking calls by the voice channels seems to work better, 100% success, compared to Unidens control channel tracking at probably a 90% success. At bigger sites with many frequencies or a busy system, the voice channel tracking could have a delay until the call is found, the first syllable are lost, depending of where in the scan of frequencies the scanner are, compared to the active call that are configured to be tracked.
If a Uniden are locked to a single DMR control channel and not scanning them, the success rate of hearing a call increase. The longer the hold time for a site the better the success rate becomes. If I scan DMR systems conventionally with a 536 it seems to always manage to catch the call but a lot of functions are lost in that mode. One problem with Unidens bad DMR decode quality are that as soon as there's a bit error it seems that it could interpret that as an encryption and instantly leaves the system during scan. It skips over active calls in sites with weak signals too often during normal trunked scan.
It's exactly the opposite for P25 where Uniden really shines and that mode works perfect even if the P25 signal are mostly covered in noise.
Unidens DMR decode seems to work without error correction as it needs a perfect signal without any kind of noise. As I remember the DMR decode worked almost perfect before Uniden added RAS compability. At that mode the site scrambles the checksums for the datastream, which are used to do error correction. It probably are some kind of bug in the firmware that switches to RAS mode, that disable error correction in the scanner, at the slightest bit error, even when the system does not use RAS. The same bug probably makes the decode function think it receives an encrypted signal.
/Ubbe