R1/R3 1.48 Firmware NO OFF TOPIC POSTS

GTO_04

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
May 21, 2011
Messages
4,001
Reaction score
3,804
Rating - 0%
0   0   0
Uhmmm. It was near a CVS off 37 that was locked out. You have experienced a total k band lockout within lockout area on 1.48? Like questions some of have had how lockouts work with other brands? You have a R3 too? How has 1.48 done for you? I will go back to narrow when I get it back out.
I have an R1 (1.37), no R3. To my knowledge there have been no complaints with the R3 regarding locking out a real LEO but you never know.

GTO_04
 

cihkal

Pure Energy
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Acceptus
Newly Registered
Joined
Apr 21, 2014
Messages
3,096
Reaction score
5,080
Rating - 0%
0   0   0
Couple of things I've noticed after flashing 1.48 today...

First thing, when MRCD is off my R will not false to my 2018 CX-5's BSM/ACC system. If I turn MRCD on it will pick up the K signal at 24.124ish which is right around where I see other detectors, such as the V1, pick up this signal. I tested this in my parking garage to reflect off the walls and general driving around. With MRCD on the falsing from picking up my CX-5's system is pretty regular and what I would note as not acceptable. This was not the case with the first firmware which brought about MRCD capabilities.

Tested how well my R3 picks up Chicago's MRCT cameras on 1.48 and wanted to mention a few things as well. First, I did notice that it will sometimes detect the signal as a regular K signal and then switch to MRCD, or vice versa. Next, it now appears to report all three frequency channels of the MRCT camera; I knew the camera transmits at three different K frequencies from the FCCID documentation. It always reports the camera's lowest channel which is around 24.082GHz. With all-threat display I noticed two other K signals would be reported as well when detecting the camera, and sometimes a third in the all-threat display which is my car's BSM/ACC system. Prior to 1.48 it would sometimes show a K signal in the all-threat display while picking up MRCT systems. Not an issue, just something to note. Lastly, performance when the camera is forwarding facing seems to be more unpredictable than before, see the below results:

R3 (FW 1.48): GPS Functions on, Highway Mode, X off, K wide, Ka 2/4/5/6/8, Laser on, MRCD on, K Filter on, TSF on, Ka filter off, Ka & K Pop off, Ka Priority on

30mph RF Run 1: 1975ish ft
30mph RF Run 2: 1975ish ft
30mph RF Run 3: 1975ish ft

30mph FF Run 1: 200ish ft
30mph FF Run 2: 0ish ft - alert at camera pole
30mph FF Run 3: several car lengths after camera pole; ticket scenario if speeding

Pro M (FW US 16): GPS Functions on, Auto-City Mode, X on, K wide, Ka Narrow 33.8/34.7/35.5 on, Laser on, MRCT Narrow on, MR Filter high, TSRej high, Ka filter on, Ka Pop off

30mph RF Run 1: 2588ish ft (course max)
30mph RF Run 2: 2588ish ft (course max)
30mph RF Run 3: 2588ish ft (course max) - MRCD Narrow on as well with no ill effects on range noted

30mph FF Run 1: 600ish ft
30mph FF Run 2: 600ish ft
30mph FF Run 3: 600ish ft - MRCD Narrow on as well with no ill effects on range noted

Both RD's were operated at seperate times for testing, CX-5 was able to false both due to reflections from BSM/ACC system using the settings listed, and traffic was light for this area since I was testing after 12am. Based on the above I will say that whatever changes were made to improve K when MRCD is on impacted K/MRCD in ways that may not have been intended. I'm not here to say why I think so because I really don't know. If anything, what I can say with confidence is as of 1.48 I think Uniden needs to spend a good amount of time refining MRCD/MRCT detection on the R series; especially if the challenges are from the firmware side of things rather than due to a hardware limitation (not talking about scanning range limits). If that is the case, as a consumer I personally would not expect the R7 to be much different with MRCD/MRCT (other than being able to scan below 24.000 for all Canada/Euro Multaradar) until performance on the current R units is improved in this area. Right now, the Pro M appears to be much more refined on K and Multaradar than the R series on 1.48. I hope to see a large improvement in this area in a future update because I think things are too unpredictable on MRCD/MRCT which make this feature not very helpful at times.
 
Last edited:

SixPackABS

PSL +15
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
Feb 14, 2014
Messages
2,356
Reaction score
2,047
Rating - 0%
0   0   0
@cihkal
So it is the MRCD that makes both RD false in our CX5. No wonder when I got back to fw 1.37 on my R3, which doesn't have the MRCD thingy I no longer have that issue.
 

Gowski

Premium Member
Premium Member
Intermediate User
Beginner User
General User
Newly Registered
Joined
Apr 9, 2017
Messages
752
Reaction score
1,111
Location
NH
Rating - 0%
0   0   0
Wasn’t TSF brought back to v1.25 in 1.46 and stayed in 1.48? I’m curious to know if that’s what causing some of these MRCD issues or perceptions, Since we’ve been running a different/newer TSF for so long now, we may not remember what it was like in 1.25 and how it acted to certain BSM offenders. And now mixing it with MRCD I think a lot of 1.37 vs 1.48 testing with TSF on and off is required to rule it out. IMO it’s not just MRCD causing the problem it’s the way TSF and MRCD are interacting together. But I’m no expert so my hat goes off to @cihkal and all our other great members for their time and hard work here.
:hatsoff:
 
Last edited:

OBeerWANKenobi

This is not the car you're looking for.....
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
Mar 20, 2018
Messages
2,572
Reaction score
5,739
Location
Right Behind You! (Wisconsin)
Rating - 0%
0   0   0
Wasn’t TSF brought back to v1.25 in 1.46 and stayed in 1.48? I’m curious to know if that’s what causing some of these MRCD issues or perceptions, Since we’ve been running a different/newer TSF for so long now, we may not remember what it was like in 1.25 and how it acted to certain BSM offenders. And now mixing it with MRCD I think a lot of 1.37 vs 1.48 testing with TSF on and off is required to rule it out. IMO it’s not just MRCD causing the problem it’s the way TSF and MRCD are interacting together. But I’m no expert so my hat goes off to @cihkal and all our other great members for their time and hard work here.
:hatsoff:
TSF was changed in 1.48 to reduce the lag in detection broght on in 1.46 but neither is necessarily comparable to earlier FW versions. I agree that it's possible that TSF settings may be causing misbehavior with MRCD.
Couple of things I've noticed after flashing 1.48 today...

First thing, when MRCD is off my R will not false to my 2018 CX-5's BSM/ACC system. If I turn MRCD on it will pick up the K signal at 24.124ish which is right around where I see other detectors, such as the V1, pick up this signal. I tested this in my parking garage to reflect off the walls and general driving around. With MRCD on the falsing from picking up my CX-5's system is pretty regular and what I would note as not acceptable. This was not the case with the first firmware which brought about MRCD capabilities.

Tested how well my R3 picks up Chicago's MRCT cameras on 1.48 and wanted to mention a few things as well. First, I did notice that it will sometimes detect the signal as a regular K signal and then switch to MRCD, or vice versa. Next, it now appears to report all three frequency channels of the MRCT camera; I knew the camera transmits at three different K frequencies from the FCCID documentation. It always reports the camera's lowest channel which is around 24.082GHz. With all-threat display I noticed two other K signals would be reported as well when detecting the camera, and sometimes a third in the all-threat display which is my car's BSM/ACC system. Prior to 1.48 it would sometimes show a K signal in the all-threat display while picking up MRCT systems. Not an issue, just something to note. Lastly, performance when the camera is forwarding facing seems to be more unpredictable than before, see the below results:

R3 (FW 1.48): GPS Functions on, Highway Mode, X off, K wide, Ka 2/4/5/6/8, Laser on, MRCD on, K Filter on, TSF on, Ka filter off, Ka & K Pop off, Ka Priority on

30mph RF Run 1: 1975ish ft
30mph RF Run 2: 1975ish ft
30mph RF Run 3: 1975ish ft

30mph FF Run 1: 200ish ft
30mph FF Run 2: 0ish ft - alert at camera pole
30mph FF Run 3: several car lengths after camera pole; ticket scenario if speeding

Pro M (FW US 16): GPS Functions on, Auto-City Mode, X on, K wide, Ka Narrow 33.8/34.7/35.5 on, Laser on, MRCT Narrow on, MR Filter high, TSRej high, Ka filter on, Ka Pop off

30mph RF Run 1: 2588ish ft (course max)
30mph RF Run 2: 2588ish ft (course max)
30mph RF Run 3: 2588ish ft (course max) - MRCD Narrow on as well with no ill effects on range noted

30mph FF Run 1: 600ish ft
30mph FF Run 2: 600ish ft
30mph FF Run 3: 600ish ft - MRCD Narrow on as well with no ill effects on range noted

Both RD's were operated at seperate times for testing, CX-5 was able to false both due to reflections from BSM/ACC system using the settings listed, and traffic was light for this area since I was testing after 12am. Based on the above I will say that whatever changes were made to improve K when MRCD is on impacted K/MRCD in ways that may not have been intended. I'm not here to say why I think so because I really don't know. If anything, what I can say with confidence is as of 1.48 I think Uniden needs to spend a good amount of time refining MRCD/MRCT detection on the R series; especially if the challenges are from the firmware side of things rather than due to a hardware limitation (not talking about scanning range limits). If that is the case, as a consumer I personally would not expect the R7 to be much different with MRCD/MRCT (other than being able to scan below 24.000 for all Canada/Euro Multaradar) until performance on the current R units is improved in this area. Right now, the Pro M appears to be much more refined on K and Multaradar than the R series on 1.48. I hope to see a large improvement in this area in a future update because I think things are too unpredictable on MRCD/MRCT which make this feature not very helpful at times.
Since you seem to have a couple locations where you are able to get pretty consistent runs, would you mind running with TSF off and trying the same test when you get a chance?

Also, an entirely different note, have you found the need for segment 4 on ka-band in Illinois? I'm running 6 for my limited excursions in the Illinois but I thought for was only really necessary for some places out east.
 

Gowski

Premium Member
Premium Member
Intermediate User
Beginner User
General User
Newly Registered
Joined
Apr 9, 2017
Messages
752
Reaction score
1,111
Location
NH
Rating - 0%
0   0   0
TSF was changed in 1.48 to reduce the lag in detection
Ah ok, I didn’t think there was a TSF change in 1.48. I thought it was the same [1.25] from 1.46. And that they made other changes to correct the MRCD lag. Did Uniden specify this somewhere?
 

OBeerWANKenobi

This is not the car you're looking for.....
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
Mar 20, 2018
Messages
2,572
Reaction score
5,739
Location
Right Behind You! (Wisconsin)
Rating - 0%
0   0   0
I'm not sure if it shows up officially anywhere. I don't think there's a changelog. It definitely shows up repeatedly in testing done by multiple testers though. It's also been mentioned by reliable sources here on the form that one of their goals was to fix the delay introduced by 1.46.
 

GTO_04

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
May 21, 2011
Messages
4,001
Reaction score
3,804
Rating - 0%
0   0   0
I'm not sure if it shows up officially anywhere. I don't think there's a changelog. It definitely shows up repeatedly in testing done by multiple testers though. It's also been mentioned by reliable sources here on the form that one of their goals was to fix the delay introduced by 1.46.
@BestRadarDetectors did confirm that TSF on 1.46 would have a (longer) similar delay to that of 1.25, but no TSF change was confirmed with 1.48 so as far as we know there has been no change.

GTO_04
 

crabu2

Learning to Fly
Beginner User
General User
Newly Registered
Joined
Aug 11, 2017
Messages
463
Reaction score
223
Rating - 0%
0   0   0
I installed fw 1.48 using recovery.

I’ve got TSF on and K set at @60%. K filter ON.

I don’t know if it’s a delay or a reduction in sensitive, but when I drove by a known K source, there’s definitely loss in range. Was in a hurry, so I didn’t have time to play with the settings.

As for MRCD, I found it in Bel Air, MD. It’s on a RLC, at the intersection of business US1 and rt 24.

I didn’t get the alert till I was stopped under it, it was showing 24.112.

Drove over 90 miles and not a single Ka hit.

I tried to delete a few speed cams that haven’t existed for over a year and I can’t seem to do it. All it does is mute on and off. I can’t seem to get it to delete. What am I doing wrong or does 1.48 have problem with deleting speed cams?
 

OBeerWANKenobi

This is not the car you're looking for.....
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
Mar 20, 2018
Messages
2,572
Reaction score
5,739
Location
Right Behind You! (Wisconsin)
Rating - 0%
0   0   0
@BestRadarDetectors did confirm that TSF on 1.46 would have a (longer) similar delay to that of 1.25, but no TSF change was confirmed with 1.48 so as far as we know there has been no change.

GTO_04
Maybe I'm misunderstanding you but there is definitely a change from 1.46 to 1.48 in how the detector reacts to K band with TSF ON. 1.48 reacts much more quickly than 1.46. I'd call that portion confirmed.
 

GTO_04

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
May 21, 2011
Messages
4,001
Reaction score
3,804
Rating - 0%
0   0   0
Maybe I'm misunderstanding you but there is definitely a change from 1.46 to 1.48 in how the detector reacts to K band with TSF ON. 1.48 reacts much more quickly than 1.46. I'd call that portion confirmed.
Good point. That could be due to changes in the MRCD firmware or TSF feature but they did not mention any changes to the TSF so we don't know for sure. It is possible that changes to MRCD can be at play here, as MRCD does not seem to be as good as with 1.48, but reactivity on K band improved.

GTO_04
 
Last edited:

Mystic330

Learning to Drive
General User
Newly Registered
Joined
Jan 16, 2019
Messages
27
Reaction score
37
Rating - 0%
0   0   0
I have tested with stationary cams in MD on 1.48 (see the MRCD 1.48 testing thread) with TSF on and off, and I do not see any significant difference in the wacky MRCD detections I see with 1.48. 1.46 detects my MRCD cams beautifully, so if some K band code was tweaked, it is affecting MRCD in a negative way regardless of the TSF code.
-- Double Post Merged: --
I tried to delete a few speed cams that haven’t existed for over a year and I can’t seem to do it. All it does is mute on and off. I can’t seem to get it to delete. What am I doing wrong or does 1.48 have problem with deleting speed cams?
This is a known issue that is present in 1.46 and 1.48 (not sure if it worked in 1.37 or not) - Nobody can delete/mute-memory speed cams.
Some of us are having trouble delete/mute-memory anything on 1.46 and 1.48 (specifically K-band alerts). Mine worked for a while under 1.46, then stopped working - I factory reset and downloaded FW again and it seemed to start working again - under 1.46. (I am not actively running 1.48 because of the MRCD issues)
 
Last edited:

DrHow

Premium Member
Premium Member
Intermediate User
Beginner User
General User
Newly Registered
Joined
May 18, 2018
Messages
1,176
Reaction score
1,419
Rating - 0%
0   0   0
Couple of things I've noticed after flashing 1.48 today...

First thing, when MRCD is off my R will not false to my 2018 CX-5's BSM/ACC system. If I turn MRCD on it will pick up the K signal at 24.124ish which is right around where I see other detectors, such as the V1, pick up this signal. I tested this in my parking garage to reflect off the walls and general driving around. With MRCD on the falsing from picking up my CX-5's system is pretty regular and what I would note as not acceptable. This was not the case with the first firmware which brought about MRCD capabilities.

Tested how well my R3 picks up Chicago's MRCT cameras on 1.48 and wanted to mention a few things as well. First, I did notice that it will sometimes detect the signal as a regular K signal and then switch to MRCD, or vice versa. Next, it now appears to report all three frequency channels of the MRCT camera; I knew the camera transmits at three different K frequencies from the FCCID documentation. It always reports the camera's lowest channel which is around 24.082GHz. With all-threat display I noticed two other K signals would be reported as well when detecting the camera, and sometimes a third in the all-threat display which is my car's BSM/ACC system. Prior to 1.48 it would sometimes show a K signal in the all-threat display while picking up MRCT systems. Not an issue, just something to note. Lastly, performance when the camera is forwarding facing seems to be more unpredictable than before, see the below results:

R3 (FW 1.48): GPS Functions on, Highway Mode, X off, K wide, Ka 2/4/5/6/8, Laser on, MRCD on, K Filter on, TSF on, Ka filter off, Ka & K Pop off, Ka Priority on

30mph RF Run 1: 1975ish ft
30mph RF Run 2: 1975ish ft
30mph RF Run 3: 1975ish ft

30mph FF Run 1: 200ish ft
30mph FF Run 2: 0ish ft - alert at camera pole
30mph FF Run 3: several car lengths after camera pole; ticket scenario if speeding

Pro M (FW US 16): GPS Functions on, Auto-City Mode, X on, K wide, Ka Narrow 33.8/34.7/35.5 on, Laser on, MRCT Narrow on, MR Filter high, TSRej high, Ka filter on, Ka Pop off

30mph RF Run 1: 2588ish ft (course max)
30mph RF Run 2: 2588ish ft (course max)
30mph RF Run 3: 2588ish ft (course max) - MRCD Narrow on as well with no ill effects on range noted

30mph FF Run 1: 600ish ft
30mph FF Run 2: 600ish ft
30mph FF Run 3: 600ish ft - MRCD Narrow on as well with no ill effects on range noted

Both RD's were operated at seperate times for testing, CX-5 was able to false both due to reflections from BSM/ACC system using the settings listed, and traffic was light for this area since I was testing after 12am. Based on the above I will say that whatever changes were made to improve K when MRCD is on impacted K/MRCD in ways that may not have been intended. I'm not here to say why I think so because I really don't know. If anything, what I can say with confidence is as of 1.48 I think Uniden needs to spend a good amount of time refining MRCD/MRCT detection on the R series; especially if the challenges are from the firmware side of things rather than due to a hardware limitation (not talking about scanning range limits). If that is the case, as a consumer I personally would not expect the R7 to be much different with MRCD/MRCT (other than being able to scan below 24.000 for all Canada/Euro Multaradar) until performance on the current R units is improved in this area. Right now, the Pro M appears to be much more refined on K and Multaradar than the R series on 1.48. I hope to see a large improvement in this area in a future update because I think things are too unpredictable on MRCD/MRCT which make this feature not very helpful at times.
The 1.48 range to detection numbers don’t look much different than your tests prior with 1.45/46 (45/46 had more traffic to add reflectivity?)?

Did you observe Mazda kicking off Pro M (yours or other cars running by or close to you) out in the wild yet? I like your garage test. Gives a baseline to start with.

As always, thanks for your efforts the result in helpful tests.
 
Last edited:

Heywood

Learning Something New, Still Dying Stupid
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
May 12, 2016
Messages
2,535
Reaction score
3,856
Location
Alberta Canada
Rating - 0%
0   0   0
I tried to delete a few speed cams that haven’t existed for over a year and I can’t seem to do it. All it does is mute on and off. I can’t seem to get it to delete. What am I doing wrong or does 1.48 have problem with deleting speed cams?
I just tried deleting a RLC with FW 1.48. It worked as it should.

I just double clicked the mute button on the cigarette adapter. I didn’t try it on the detector itself.

The thing I hate about the RLC on the R3, it alerts for the whole intersection regardless of what direction your approaching it.


Sent from my iPhone using Tapatalk
 
Last edited:

crabu2

Learning to Fly
Beginner User
General User
Newly Registered
Joined
Aug 11, 2017
Messages
463
Reaction score
223
Rating - 0%
0   0   0
I just tried deleting a RLC with FW 1.48. It worked as it should.

I just double clicked the mute button on the cigarette adapter. I didn’t try it on the detector itself.

The thing I hate about the RLC on the R3, it alerts for the whole intersection regardless of what direction your approaching it.


Sent from my iPhone using Tapatalk
I tried it on and RLC too and it wouldn't do it. In when I was on 1.31 and 1.37, I had no problems with deleting RLC. I just couldn't do speed cams. Now I can't do either.
 

Mystic330

Learning to Drive
General User
Newly Registered
Joined
Jan 16, 2019
Messages
27
Reaction score
37
Rating - 0%
0   0   0
I just tried deleting a RLC with FW 1.48. It worked as it should.

I just double clicked the mute button on the cigarette adapter. I didn’t try it on the detector itself.

The thing I hate about the RLC on the R3, it alerts for the whole intersection regardless of what direction your approaching it.


Sent from my iPhone using Tapatalk
Red light cams (RLC) are different than Speed Cams - RLCs, like K-band, are allowed via the s/w to be mute-deleted - Speed cams are not.
Some of us are also hitting what I suspect is a bug where RLCs and K-band mute-deletes cannot be set for some reason.
 

Heywood

Learning Something New, Still Dying Stupid
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
May 12, 2016
Messages
2,535
Reaction score
3,856
Location
Alberta Canada
Rating - 0%
0   0   0
Red light cams (RLC) are different than Speed Cams - RLCs, like K-band, are allowed via the s/w to be mute-deleted - Speed cams are not.
Some of us are also hitting what I suspect is a bug where RLCs and K-band mute-deletes cannot be set for some reason.
That makes sense.

Our stationary speed cameras are “Speed on Green” in conjunction with our RLC’s.

We have the fun mobile, move every 2 hours, hide in the weeds type of MRCD truck cameras. Unmarked of course.
Lol.


Sent from my iPhone using Tapatalk
 

Brainstorm69

TXCTG 2016 MOTY
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
May 23, 2015
Messages
7,688
Reaction score
14,261
Location
Lone Star State
Rating - 0%
0   0   0
Good point. That could be due to changes in the MRCD firmware or TSF feature but they did not mention any changes to the TSF so we don't know for sure. It is possible that changes to MRCD can be at play here, as MRCD does not seem to be as good as with 1.48, but reactivity on K band improved.

GTO_04
One of the things Uniden improved with 1.48 was to shorten the delay with TSF on. This was intentional based on feedback from the beta testers and everyone on the Forum. As I recall, they are still working to shorten the K-band delay caused by MRCD on.
 

leesrt

Mature Speeder
Beginner User
General User
Newly Registered
Joined
Feb 3, 2015
Messages
490
Reaction score
643
Location
Florida
Rating - 0%
0   0   0
Ok, the last post confirmed what I thought. Wasn't there testing already done that shows with TSF and MRCD on there was delay in the k band? If so, why is the testing still happening with TSF and MRCD on?
 

G39x

Huntin' Rabbits
Intermediate User
Beginner User
General User
Newly Registered
Joined
Nov 1, 2016
Messages
394
Reaction score
348
Location
Nashville, TN
Rating - 0%
0   0   0
Ok, the last post confirmed what I thought. Wasn't there testing already done that shows with TSF and MRCD on there was delay in the k band? If so, why is the testing still happening with TSF and MRCD on?
I think it is just to test the delay hit that happened on 1.46, which would miss a lot of QT shots. I think 1.48 fixed that issue as they lowered the delay. Now the issue on hand is BSM and the K-band delay with MRCD which is being worked on as mentioned. BSM will probably be looked at next after the delay issue is remedied hopefully. Need some secret sauce on the BSM issue. Hopefully there is a hardware update for the R1/R3's which to me is highly unlikely.
 

Donation drives

RDF Server & License Fees (Jan/Feb 2019)

This donation drive covers the server and licensing fees for RDF for the months of January and February 2019...
Goal
$795.00
Earned
$800.00
This donation drive ends in

Latest threads

Social Group Activity

Forum statistics

Threads
78,301
Messages
1,164,718
Members
18,005
Latest member
Aviator92
Top