Provoked by the latest testing results by @Heywood, I decided to do a short testing today with my R1 against the nearest MRCD unit by the JENOPTIK ROBOT GmbH, Germany. I did a test there about year ago with FW 1.46 that you can remember here. Was curious if the claim in the FW update 1.53 will live up to my expectations firsthand.
I have put everything together in a single video. Three runs - half of them with K band on and MRCD on, half of them with deactivated K band and only MRCD On. I did that because my R1 reacted initially just like in this video from Australia. First K band which was long enough detection for an MRCD and then the usual mrcd announcement. I wanted too see both cases. K filter is off during all the test runs. I will not give numbers in meters but everybody is able visually to see for themselves, it is enough. Most users should keep in mind that MRCD is very hard to detect, let alone from a long distance. You should also bear in mind that this unit here is installed in a specially designed box to limit the emission into one narrow direction and that is why it is hard to be detected from the enforcement side, from the back. But if you think that MRCD is bad, think again... We've had here recently something called "Cordon M2" that is even worse than an MRCD's
Here is the video itself I recorded for you:
Conclusions:
1. All the three detections were consistent and stable for an Uniden, even better than with FW 1.46 and caught at a longer distance.
2. Initial detection could be announced as "K band" gradually going to MRCD. But I can live with that as long as these detections are even more awesome as range than the previous ones.
3. Based on the above-mentioned sources and videos, also this report and the current results, I can admit that firmware 1.53 is the best one so far for MRCD detection by Uniden for Uniden R1 and R3. Also it is one of the best all-rounded firmwares made by Uniden for all bands.
I have put everything together in a single video. Three runs - half of them with K band on and MRCD on, half of them with deactivated K band and only MRCD On. I did that because my R1 reacted initially just like in this video from Australia. First K band which was long enough detection for an MRCD and then the usual mrcd announcement. I wanted too see both cases. K filter is off during all the test runs. I will not give numbers in meters but everybody is able visually to see for themselves, it is enough. Most users should keep in mind that MRCD is very hard to detect, let alone from a long distance. You should also bear in mind that this unit here is installed in a specially designed box to limit the emission into one narrow direction and that is why it is hard to be detected from the enforcement side, from the back. But if you think that MRCD is bad, think again... We've had here recently something called "Cordon M2" that is even worse than an MRCD's
Conclusions:
1. All the three detections were consistent and stable for an Uniden, even better than with FW 1.46 and caught at a longer distance.
2. Initial detection could be announced as "K band" gradually going to MRCD. But I can live with that as long as these detections are even more awesome as range than the previous ones.
3. Based on the above-mentioned sources and videos, also this report and the current results, I can admit that firmware 1.53 is the best one so far for MRCD detection by Uniden for Uniden R1 and R3. Also it is one of the best all-rounded firmwares made by Uniden for all bands.
Last edited: