Firmware 1.46 Released

Crunchy

PSL +5
Intermediate User
Beginner User
General User
Newly Registered
Joined
Mar 5, 2018
Messages
183
Reaction score
283
Rating - 0%
0   0   0
Sweet ride....Self test was directed at the user referring to GPS acquiring more slowly since updating.....That would drive me crazy if I had to manually turn my on at start up......Would be afraid I would forget to turn on sometimes when I had a lot on my mind....

--- DOUBLEPOST MERGED ---



Your terrain looks like mine....Not much else a detector can do in that situation...It has to see the source and there was really no way for it to see it until it came around the bend....I have multiple encounters similar with both filters off and just a slight more warning than you got in this video....One reason with 1.46 although I am getting more BSMs if I can grab an extra second or two when driving in such terrain I will take the trade off...
Terrain probably had a lot to do with it , but I turned off tsr because the close call made me uncomfortable. We won’t know if it really has an impact until Someone actually tests it.

--- DOUBLEPOST MERGED ---

That short detection distance might have been the result the LEO lighting up the vehicle in front of you, might have not been transmitting up to that point
It could have been I/O but that rarely happens around here. I don’t believe it was but I’m not 100% sure.
 

cruiser66

PSL +5
Intermediate User
Beginner User
General User
Newly Registered
Joined
Jun 14, 2011
Messages
214
Reaction score
167
Rating - 0%
0   0   0
Yes, but quoting an article as evidence that is over a year old doesn't do much good, especially when it is known that the older 1.25 firmware did indeed introduce a delay to control traffic sensors on TMF. This was changed later to reduce the delay on 1.31 and 1.37 versions of TMF to almost nothing, then changed again to help out Colorado folks struggling with a particular type of traffic sensor back to the old 1.25 TMF delay.

The article is just a point in time, a singular dot on the continuum. If you don't know the whole timeline and history, and don't know when the article was written in relationship to that history, quoting Vortex means nothing, regardless of how well respected he is and how high of an authority he is in the community. Things change, and when they do information that was correct can now be false, and vice-versa through no fault of the writer.

In this case it was correct for 1.25, incorrect for 1.31 and 1.37, and now correct again for 1.46.


I'm sticking to 1.37. Filtering of BSMs over just about everything else is my new mantra.
Thanks for your feedback! Threads like this really helps us all to collectively understand the finer nuances of features, especially TSF.
Also agree with you last statement about BSM filtering. As I have mentioned in a number of posts, is the second most important thing to me after solid Ka detection (not factoring in Auto lockouts and arrows which the R3 and Pro M do not have).
I recall that as of 1.37 the guide still said not to use TSF; otherwise I would not have referenced it. However I was not aware that all the while, per your assessment, it was not accurate that "TSF On reduces reactivity" on 1.37 and I could have had less BSM falses while on 1.37 by enabling TSF. Oh well, better to find out about that late than never, as well as some of the nuances of TSF (not versed in the specifics of it frankly as always had it off for fear of missing I/O given recommendation by Vortex and have other priorities in life which preclude me from devoting even more time to this hobby. :)

Now my dilemma of whether to go with 1.37 or 1.46:
I had been considering reverting back to 1.37 with TSF On given feedback in this thread that it should help reduce false K band alerts due to BSM. However MRCD/T is now in use in 2 areas not too far away (NY and MD) and MRCD/T use in the US will undoubtedly continue to proliferate over time; new installations could happen at any time without my knowledge leaving me unprotected to this growing threat (of course even 1.46 misses some MRCD/T signals due to the R3 hardware limitation of how low in the K band it can actually scan and detect signals; that is a different dilemma since the Pro M catches these).
 

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,668
Reaction score
4,246
Location
Alberta Canada
Rating - 0%
0   0   0
The only difference I noticed is that have a known highway information site that causes K band false everytime I pass it, but today it was alerting to K-band and as soon as I was close to it changed to MRCD alert.
Your not seeing things, it’s known to happen if you leave MRCD on.

Some of those signs use their radar on 2 different settings. 1 to pick up movement, and one to trigger the action. It’s especially true for solar powered speed signs that need to conserve battery power.

Something like a motion detection light.


Sent from my iPhone using Tapatalk
 

mookiwan

Learning to Drive
General User
Newly Registered
Joined
Oct 10, 2018
Messages
14
Reaction score
29
Rating - 0%
0   0   0
Thanks for your feedback! Threads like this really helps us all to collectively understand the finer nuances of features, especially TSF.
Also agree with you last statement about BSM filtering. As I have mentioned in a number of posts, is the second most important thing to me after solid Ka detection (not factoring in Auto lockouts and arrows which the R3 and Pro M do not have).
I recall that as of 1.37 the guide still said not to use TSF; otherwise I would not have referenced it. However I was not aware that all the while, per your assessment, it was not accurate that "TSF On reduces reactivity" on 1.37 and I could have had less BSM falses while on 1.37 by enabling TSF. Oh well, better to find out about that late than never, as well as some of the nuances of TSF (not versed in the specifics of it frankly as always had it off for fear of missing I/O given recommendation by Vortex and have other priorities in life which preclude me from devoting even more time to this hobby. :)

Now my dilemma of whether to go with 1.37 or 1.46:
I had been considering reverting back to 1.37 with TSF On given feedback in this thread that it should help reduce false K band alerts due to BSM. However MRCD/T is now in use in 2 areas not too far away (NY and MD) and MRCD/T use in the US will undoubtedly continue to proliferate over time; new installations could happen at any time without my knowledge leaving me unprotected to this growing threat (of course even 1.46 misses some MRCD/T signals due to the R3 hardware limitation of how low in the K band it can actually scan and detect signals; that is a different dilemma since the Pro M catches these).
I am in the same boat as you. I follow vortex on YouTube and got the r3 updated to 1.46 with his recommended settings. I have noticed a lot more noise on this update than 1.37. K wide k filter on tsf off. So I came looking around the internet and found this forum. Didn’t know there was a way to decrease bsm chatter even more with tsf on 1.37. Always thought I had to live with every detector being a LEO / Honda detector. I am now debating going back to 1.37 to try out the tsf.


Sent from my iPhone using Tapatalk
 

Pumanator

rawr
Beginner User
General User
Newly Registered
Joined
Jan 25, 2014
Messages
59
Reaction score
54
Location
Durham-Chapel Hill, NC
Rating - 0%
0   0   0
...it is known that the older 1.25 firmware did indeed introduce a delay to control traffic sensors on TMF. This was changed later to reduce the delay on 1.31 and 1.37 versions of TMF to almost nothing, then changed again to help out Colorado folks struggling with a particular type of traffic sensor back to the old 1.25 TMF delay.

In this case it was correct for 1.25, incorrect for 1.31 and 1.37, and now correct again for 1.46.

Is there a current recommended settings thread or video for 1.37? I've also been running with TSF off per the original recommended settings from Vortex as of June 2017. I'm running 1.37 now and would enjoy cutting down on BSMs.
 

OPPOP

PSL +5
Intermediate User
Beginner User
General User
Newly Registered
Joined
Feb 5, 2014
Messages
231
Reaction score
195
Location
Vancouver, BC
Rating - 0%
0   0   0
Ok another day of testing. Definitely I can confirm the R3 is falsing so much more than before. But i am staying at 1.46 because of RLC muting option. I am really hoping we can get old TSF back. Beta testers, any update from Uniden?
 

aim4squirrels

Currently edging...
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
Jul 21, 2015
Messages
2,245
Reaction score
3,210
Location
DFW Texas
Rating - 0%
0   0   0
Is there a current recommended settings thread or video for 1.37? I've also been running with TSF off per the original recommended settings from Vortex as of June 2017. I'm running 1.37 now and would enjoy cutting down on BSMs.
I don't believe so. Vortex didn't make a video for each iteration of the next firmware, he usually just did it for big changes.

I run k filter ON, K Band at 70%, TSF On, K narrow, but you need to know your territory. If you have cops that like to I/O, if you have lots of hills, lots of bends in the road or other obstructions you might want to increase k band sensitivity. If you've run into legitimate cop signals beyond the narrow range of 21.080-24.200, you might not want to run K narrow.
 

Brainstorm69

TXCTG 2016 MOTY
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
May 23, 2015
Messages
7,803
Reaction score
14,824
Location
Lone Star State
Rating - 0%
0   0   0
Ok another day of testing. Definitely I can confirm the R3 is falsing so much more than before. But i am staying at 1.46 because of RLC muting option. I am really hoping we can get old TSF back. Beta testers, any update from Uniden?
Our Uniden contact is out of the office until 10/22.
 

mookiwan

Learning to Drive
General User
Newly Registered
Joined
Oct 10, 2018
Messages
14
Reaction score
29
Rating - 0%
0   0   0
I think I am going to run 1.46 (highway, k wide, k filter on, tsf off, mrcd on) for a few weeks to see if I pick up any mrcd in the area (upstate ny). Then if I get no hits I’m going to go back to 1.37 (highway, k wide, k filter on, tsf ON) to see if that helps with BSM. I will also dable with advance mode and decrease k strength until I find a sweet spot.


Sent from my iPhone using Tapatalk
 

Vortex

Making Videos
Administrator
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
Jul 19, 2012
Messages
19,982
Reaction score
38,129
Location
Washington State
Rating - 100%
10   0   0
Thanks for your feedback! Threads like this really helps us all to collectively understand the finer nuances of features, especially TSF.
Also agree with you last statement about BSM filtering. As I have mentioned in a number of posts, is the second most important thing to me after solid Ka detection (not factoring in Auto lockouts and arrows which the R3 and Pro M do not have).
I recall that as of 1.37 the guide still said not to use TSF; otherwise I would not have referenced it. However I was not aware that all the while, per your assessment, it was not accurate that "TSF On reduces reactivity" on 1.37 and I could have had less BSM falses while on 1.37 by enabling TSF. Oh well, better to find out about that late than never, as well as some of the nuances of TSF (not versed in the specifics of it frankly as always had it off for fear of missing I/O given recommendation by Vortex and have other priorities in life which preclude me from devoting even more time to this hobby. :)
I'm glad you're taking the time to learn more about the nuances of the menu options and filters so that you can make an educated decision as to whether or not you should or shouldn't use a particular setting. IMHO, that's the way to do it, so props to you.

When I say "not to use a setting," that's not intended to be some universal blanket statement. It's mainly geared to be a general recommendation for people who are looking for a good starting place, particularly if they don't want to take the time to learn their detector's settings and when to change what setting.

You've got the idea behind TSF now and when you should or shouldn't use it, and I'm glad to see that. :) Nicely done!
 

sdrawkcaB

sdrawkcaB|Backwards
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
Mar 6, 2018
Messages
2,562
Reaction score
4,453
Rating - 100%
1   0   0

cruiser66

PSL +5
Intermediate User
Beginner User
General User
Newly Registered
Joined
Jun 14, 2011
Messages
214
Reaction score
167
Rating - 0%
0   0   0
I'm glad you're taking the time to learn more about the nuances of the menu options and filters so that you can make an educated decision as to whether or not you should or shouldn't use a particular setting. IMHO, that's the way to do it, so props to you.

When I say "not to use a setting," that's not intended to be some universal blanket statement. It's mainly geared to be a general recommendation for people who are looking for a good starting place, particularly if they don't want to take the time to learn their detector's settings and when to change what setting.

You've got the idea behind TSF now and when you should or shouldn't use it, and I'm glad to see that. :) Nicely done!

Thanks for the compliment! :) Right, I totally agree about recommendations not being intended to be universal. IN this specific instance (i.e. TSF) I was more referring to the specific statement that TSF On slows reactivity. Given I have been hit by I/O K band late at night in NJ about 5 or 6 years ago I did not want my R3 to miss potential I/O K band shots of vehicles ahead of me which could provide advance warning of a threat that no detector can help with if you don't have another vehicle in front that gets hit by the I/O shot.
Now that I know TSF works differently in 1.37 and some other versions than it does in 1.46, I can experiment with it and then decide which firmware and settings to stick with.

Keep up the great work! Really enjoy all your well put together videos, as well as your Escort interview; even if nothing came out of the latter, you deserve a lot of credit for trying and all the hard work that entailed.
 
Last edited:

HaloInReverse

Premium Member
Premium Member
Beginner User
General User
Newly Registered
Joined
Jun 7, 2017
Messages
85
Reaction score
79
Location
Vegas
Rating - 0%
0   0   0
Either Ka filtering is awesome now or I've got a serious problem which is worrying me on my 30 mile commute to work...

Normally I pick up 3 Ka signals before entering the military installation I work on, and they're constant unless I mute the signals. Today I picked up one Ka signal closer than usual, and then not a peep, even going through the gates.

Also noticed that the "Your Speed" signs I usually pick up in a construction zone right before home are not alerting either. Mute memory had these locations flagged and were still visible on the R3, but not getting indications of these signs anymore.

Ka filter is off, Ka is set to 100%. I'm utilizing Vortex's recommended settings in Advanced, and they were also used in 1.37 without any issues. Flashed 1.46 in recovery mode and reset factory settings blah blah blah...
 
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,668
Reaction score
4,246
Location
Alberta Canada
Rating - 0%
0   0   0
Either Ka filtering is awesome now or I've got a serious problem which is worrying me on my 30 mile commute to work...

Normally I pick up 3 Ka signals before entering the military installation I work on, and they're constant unless I mute the signals. Today I picked up one Ka signal closer than usual, and then not a peep, even going through the gates.

Also noticed that the "Your Speed" signs I usually pick up in a construction zone right before home are not alerting either. Mute memory had these locations flagged and were still visible on the R3, but not getting indications of these signs anymore.

Ka filter is off, Ka is set to 100%. I'm utilizing Vortex's recommended settings in Advanced, and they were also used in 1.37 without any issues. Flashed 1.46 in recovery mode and reset factory settings blah blah blah...
Did you activate MRCD?


Sent from my iPhone using Tapatalk
 

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,668
Reaction score
4,246
Location
Alberta Canada
Rating - 0%
0   0   0
MRCD is off.

Sent from my Pixel 2 XL using Tapatalk
Sounds good. Thanks.

A nice new option is that the R3 can now mute memory Ka signals for circumstances such as yours.


Sent from my iPhone using Tapatalk
 

HaloInReverse

Premium Member
Premium Member
Beginner User
General User
Newly Registered
Joined
Jun 7, 2017
Messages
85
Reaction score
79
Location
Vegas
Rating - 0%
0   0   0
Sounds good. Thanks.

A nice new option is that the R3 can now mute memory Ka signals for circumstances such as yours.


Sent from my iPhone using Tapatalk
Uhh, the military installation signals are not in mute memory...nor were the 3 I usually pick up detected.

Sent from my Pixel 2 XL using Tapatalk
 

Donation drives

RDF Server & License Fees (Mar 2019) (ACTIVE)

This donation drive covers the server and licensing fees for RDF for the month of March 2019...
Goal
$334.00
Earned
$450.00
This donation drive ends in

Latest threads

Social Group Activity

Forum statistics

Threads
79,180
Messages
1,180,197
Members
18,163
Latest member
rebait1
Top