Uniden R1/R3 Change Log and Firmware Versions

[DChiJEllis]

I just picked up an R3 today from Best Buy, this is my first RD in over 15 years! Anyways, serial starts with 9A02 and firmware version is 2019/10/02 150.213.115 - So I dont need to upgrade firmware? Glad to contribute anything I can for the community!

Yes, you’re up to date.

 

[Got Jeep]

I may have missed it, is there a reason that FW 1.50 isn't listed in the OP ?

 

[Kaizer911]

v1.53 – 02/24/2020

- Enhancing MRCD detection range and accuracy.
- MRCD always has priority over other radar alert (X, K, Ka) even when Ka priority is ON.
- MRCD alert is not muted by Quiet Ride.
- Alert “POI limit speed” and “radar” shown in turn if detected at the same time.
- Overspeed alerts every 1.5 seconds.
- Press “Mute/Dim” key for 0.5 seconds at standby mode to enter DIM mode (currently 1.0 seconds.
- Shorten display change time to 2 seconds from 3 seconds when changing DIM and detection modes.


Sent from my iPhone XS Max using Tapatalk

 

[Mithheru]

The new 153 firmware also has DSP version 214. Therefore looks as though Uniden likely further developed 213 that was shipped on some of the newer R3s. As we reported, it was likely there was also a bug in 213 so, probably everyone with that version maybe worthwhile updating to 153. with its DSP 214.

 

[RoverTtx]

I wish you could mute it while Mrs Uniden lady announces frequencies. You have to wait til she's done. That's a little thing I really dislike!


Sent from my Moto Z2 using Tapatalk

 

[aradarnut]

I wish you could mute it while Mrs Uniden lady announces frequencies. You have to wait til she's done. That's a little thing I really dislike!


Sent from my Moto Z2 using Tapatalk

Turn it off

 

[RoverTtx]

Turn it off [emoji2369]

Kind of like saying k band makes noise, so just turn it off!

I like the feature but when I have others in the car/I'm on a call etc and need to mute, I hate that little waiting period. Doesn't mean the best solution is to turn it off.

Sent from my Moto Z2 using Tapatalk

 

[CamBro]

www.dropbox.com: Uniden R1-R3 Firmware

(These notes and firmware files are also available on Uniden’s website
Radar Detectors - Uniden Support)

Warning – These updates are NOT for Australia/New Zealand models.

R1/R3 (Last Updated 01/18/2019 v1.48)

1. Ensure your R1/R3 is powered off using the power button
2. Connect R1/R3 to PC with USB cable
3. PC may automatically download USB drivers if needed. If message says that the device is not recognized, you can manually install the USB driver here: [ZIP] (Install drivers and then reconnect radar detector to PC)
4. Download and install appropriate file:
   R1 – “Uniden R Series SW Download Tool and Firmware” [ZIP]
   R3 – “Uniden R Series SW Download Tool and Firmware” [ZIP]
   R1/R3 for MAC – “Uniden R Series SW Drivers, Download Tool and Firmware” [ZIP]
5. After downloading, extract the files to a new folder.
6. Run “Uniden R Series SW Download Tool V1.22.msi”
7. After download tool is installed, run “Uniden R Series SW Download Tool V1.22” from newly created shortcut. Your version of firmware will appear on the application.
8. Select the OPEN button and browse to the “R1_v148.207.000.bin” or “R3_v148.207.114.db190104.bin” file from the previously extracted files, then select START DOWNLOAD.
9. After update is complete, close the program.
10. Firmware/Database/Voice is all updated with a single program now.
11. Reset the device to the factory default settings by using the menu after new firmware has been installed.

Fixes (v 1.48 – 01/18/2019)

• Improved Laser falsing
• Improved detection delay when MRCD is on
• Red light database updated 1/4/2019

R3/DFR7 DATABASE UPDATE
(Last Updated 10/4/2018)

• Database File

MAC UPDATE PROGRAM FOR R1/R3 (05/14/2018)

• Download MAC Update Program with latest firmware
• Install Uniden R Series Tool V1.1 pkg file
• Install VCP USB Driver program
• Allow installation of USB Driver and Download programs in Security and Privacy settings

R1/R3 1.46
(Last Updated 10/05/2018)

• MRCD / MRCT (Alert priority: Laser, MRCD, Ka, K, X)
• Customizable tones for Multaradar
• Lockouts now available for Ka band as an option, also enables MRCD lockouts
• Ka bogey tone, alerts for new signal > 5 MHz different, customizable new bogey tones
• TSF returned to v1.25, better for drivers in CO
• Dark mode blinking dot
• Brightness setting for dark mode
• Uniden boot logo color now matches main display color
• Default display color is now red (helps with burn-in)
• Maximum display brightness reduced slightly
• Voltage display location slightly shifts around over time
• AM/PM design changed
• R3: GPS lockouts now allow for 500 locations, up from 200
• R3: Manual user points up to 500, up from 200
• R3: Ability to mute a RLC alert or delete it
• R3: Latest GPS database

R3/DFR7 DATABASE UPDATE
(Last Updated 04/03/2018)

• Database File

R1/R3 1.37
(Last Updated 03/09/2018)
v 1.36 – 03/09/2018

• Frequency display font size
• Ka frequency call out(Ka frequency voice on/off)
• R3: Auto Dim
• R3: OverSpeed Alert Mute
• R3: Mute memory lock outs 8 points within the same radius (previously 5)

v 1.37 – 03/09/2018

• Shorten the gap between Ka frequency voice announcement and beep alert
• Increase Ka frequency call out voice
• R3: Scan mode display(using Auto Dim) bug fix
• R3: Ka Mute memory bug fix: Users who use initial FW version(Ka mute memory firmware) might have Ka mute memory even they use the update FW because Ka mute memory is still stored in the memory.
• R3: GPS firmware update – sometimes failure occure during GPS DB update due to communication time problem between PC and product. We fixed this problem.
• R3: v1.37 firmware has the latest GPS DB.
• Download program (v1.22) – Firmware/Voice/GPS now can be updated with single program. Stabilized the update during GPS DB update

Note: 1.36 was release with a bug that was fixed in 2 days and rereleased as 1.37. Any references to 1.34 were for a beta version that became 1.36.


R1/R3 1.31
(Last Updated 10/19/2017)

• Ka band segmentation
• White and purple display modes
• Power cable mute button can now adjust display brightness (press and hold mute button)

R1/R3 1.30
(Last Updated 08/17/2017)
Added Database Update (08/17/2017)

• Improvements to ghosting K -> Ka and Ka -> K
• Display mode box color matches display color
• Lockout range reduced from +/- 50 MHz to +/- 30 MHz (R3 only)
• Lockouts no longer affect Ka (R3 only)
• Delete RLC by hitting mute button twice (R3 only)
• Altimeter changed from 4 digits max to 5 digits max (R3 only)
• Band priority alerts (Ka priority)
• Advanced mode (use defined sensitivity adjustments for X/K/Ka in 10% increments)
• Mode display (can replace time or heartbeat scanner)
• New user selectable tones for X/K/Ka/Laser
• User selectable automute levels

R1/R3 1.26
(Last Updated 06/13/2017)

• Improvements on ghosting, 35.5 false issues, and BSM falsing

R1/R3 1.25
(Original Release 06/01/2017)

How do you get the updated R3 software for a New Zealand Uniden R3?

 

[Deacon]

Seems like mostly crickets around here. July of 2019 was 1.50, then the minor 1.53 update this March. Is this the last we’ve seen of R1/R3 updates?

 

[Viking59]

Seems like mostly crickets around here. July of 2019 was 1.50, then the minor 1.53 update this March. Is this the last we’ve seen of R1/R3 updates?

Except for database updates, yes, 1.53 is the last FW update.

 

[Deacon]

1.53 is the last FW update.

It’s the most recent firmware update. The question is will it be the last firmware update we ever see.

 

[CarefulDriver]

It’s the most recent firmware update. The question is will it be the last firmware update we ever see.

I hope not. According to @Heywood , all updates after 1.46 have actually made MRCD detection worse, even though changelog claims opposite. Perhaps it will still change in future.

 

[Viking59]

It’s the most recent firmware update. The question is will it be the last firmware update we ever see.

I didnt mean that it was literally the LAST update. They will probably issue a new update with additional improvements. When? You'd have to ask Uniden.

 

[Heywood]

It’s a trickledown effect.
The R7 is the flag ship.... so If there's movement on the R7 FW.... I wouldn’t be overly surprised that there may be something for the R3/R1.

Another way to look at it... the FW numbers are sequential. The R7 went from a public FW 1.29 to 1.33. That means they tested and rejected .30,.31,.32 for public distribution.

Obviously they haven’t been sitting on their hands. They’ve been busy improving it.... they just haven’t been releasing any details any more.

Now will we see FW 1.54? Hard to say. You might, or might not. Depends what the beta testers discover.

Obviously they are working on stuff... and the R1/R3/R7 are closely related... so I wouldn’t say that 1.53 is the final update. Makes no sense.

 

[Deacon]

I wouldn’t say that 1.53 is the final update. Makes no sense.

It’s the FI-NAL UP-date...doodahdoodoo... doo dah doo too too...

But seriously, why would it make no sense? I’d they’re happy with it, and it’s still selling well, and the R7 is unique in its ability to leverage the automatic lockouts they got from Escort, does it make sense to mess with it?

I can maybe see some BSM improvements coming if they manage it for the R7 and can cheaply apply it to the R1/R3.

 

[Heywood]

It’s the FI-NAL UP-date...doodahdoodoo... doo dah doo too too...

But seriously, why would it make no sense? I’d they’re happy with it, and it’s still selling well, and the R7 is unique in its ability to leverage the automatic lockouts they got from Escort, does it make sense to mess with it?

I can maybe see some BSM improvements coming if they manage it for the R7 and can cheaply apply it to the R1/R3.

That’s what I would guess.
BSM
MRCD
Maybe less Lidar false’s
The option to choose alert priorities?
Maybe a K band bogey alert?

Some of the stuff that we seen come out on the R7’s 1.33 update that doesn’t include the rear antenna stuff.

Just a guess. The R7 is close to a pancaked double R3. Stuff like that.

Post automatically merged: Oct 21, 2020

Forgot to throw on the wish list. Better way to implement lockouts.

There’s a few things.

 

[skd]

I hope not. According to @Heywood , all updates after 1.46 have actually made MRCD detection worse, even though changelog claims opposite. Perhaps it will still change in future.

My last quick runs around an MRCD camera didn't testify to your statement as far as we talking about the MRCD features. In fact, quite the opposite, I found it more or less better than 1.46 in this regard. Other bands are quite decent and responsive as well and driving with this FW, I have had many great safes with FW 1.53 for several months. Generally, I can sleep easily with the safety it gives and the MRCD detection I saw. A week ago I was concerned about a mobile enforcement radar here that turned out to be too hard of a competitor against R1 but my suspicions are that it is something similar as a technology with the Redflex, if not the same, and if it is true, this it would be bad news for any detector on the market right now. So I can't probably blame FW 1.53 because FW 1.37 didn't alert it at all. But as a whole, we could see some improvements with the filters at least for less false alerts and quicker reactivity. Every gas station door cell is a huge irritating factor. Also, as Heywood mentioned, maybe an option for anybody to change the individual preference for the priority of signals.

 

[CarefulDriver]

My last quick runs around an MRCD camera didn't testify to your statement as far as we talking about the MRCD features. In fact, quite the opposite, I found it more or less better than 1.46 in this regard. Other bands are quite decent and responsive as well and driving with this FW, I have had many great safes with FW 1.53 for several months. Generally, I can sleep easily with the safety it gives and the MRCD detection I saw. A week ago I was concerned about a mobile enforcement radar here that turned out to be too hard of a competitor against R1 but my suspicions are that it is something similar as a technology with the Redflex, if not the same, and if it is true, this it would be bad news for any detector on the market right now. So I can't probably blame FW 1.53 because FW 1.37 didn't alert it at all. But as a whole, we could see some improvements with the filters at least for less false alerts and quicker reactivity. Every gas station door cell is a huge irritating factor. Also, as Heywood mentioned, maybe an option for anybody to change the individual preference for the priority of signals.

Are we talking about Multaradar C (European version of MRCD) that operates somewhere at 24.1 Ghz? That could explain the difference when compared to Heywood's testing. Have you tested turning K band off? Does it still alert to MRCD after that?

 

[skd]

Are we talking about Multaradar C (European version of MRCD) that operates somewhere at 24.1 Ghz? That could explain the difference when compared to Heywood's testing. Have you tested turning K band off? Does it still alert to MRCD after that?

Yes. You can see these runs for yourself in the Countermeasure Testing Results section.

 

[CarefulDriver]

Yes. You can see these runs for yourself in the Countermeasure Testing Results section.

Awesome I will. I consider updating then (I'm from Europe too).