R1/R3 v1.50 Firmware Released

KnightHawk

Learning to Drive
General User
Joined
Apr 26, 2018
Messages
316
Reaction score
299
Location
Somewhere Out There
I was behind a new CR-V on my drive home and started getting the random 24.211, 24.214, 24.161 24.141 PTs with K-Block on. I turned off K-Block and power cycled the detector. It immediately started alerting in the 24.199-24.204 K-Block range only. If others can confirm similar behavior I think we can assume there are secondary frequencies that Honda/Acura vehicles are emitting. The R3 is definitely trying to filter them as the heartbeat stalls and stutters but eventually the secondary frequencies are getting through. We only see them when K-Block silences the primary signal.
Drove with the R7 today and encountered 2 MDX vehicles with different frequencies from 24.140 -24.148 and the other one was 24.160-24.167. Had K block on during initial encounter. Turned off K block and reboot. Showed the same frequencies after reboot. No frequencies showing within the K block frequency range. I did not use my R3 for obvious reasons. Just got my R7.
-- Double Post Merged: --
Tried this exact same thing today with the exact same results. Fell in line in freeway traffic behind an MDX, and the R3 showed 24.159 at 2 bars strength. Shut off K block, power cycled, and came back at full blast with 24.199. Turned K Block back on again, power cycled, and sure enough was hit with 24.159. It might very well be a secondary frequency, but I still feel the R3 is just spitting back an arbitrary K Band frequency due to lack of being able to process such a strong signal with the block and all.

Note that with K block enabled, the alert both times remained at 2 bars, but was full strength with K Block off.

Advanced
K Band 60%
K Filter ON
TSF On
K Narrow
K Block Toggled
Not sure if this is just an R3 only issue but not seen this happening with the R7 with 2 encounters with Acura MDX's today.
 
Last edited:

HeadShot

Catch Me If You Can
Beginner User
Joined
Sep 14, 2017
Messages
78
Reaction score
85
Location
PA
You don’t open the bin file directly. Once you install the update software, open it and make sure it finds your detector, then open the bin file within the update software and click start download. Make sure you install the drivers before doing anything else. This video should help. Ignore the firmware versions being referenced. The update procedure is the same though.

Thinking the same thing. Doesn't sound like drivers are installed.
 

thebenzman

Learning to Drive
General User
Joined
Oct 8, 2016
Messages
8
Reaction score
0
My 2 cents ... 90% quieter with "K Block". Very happy with the results! Now, asking for the moon, K band segmentation would be nice (block out the new 24.160 and 24.167 falses from some Acuras and Pacificas...)
 

Deacon

TXCTG
Advanced User
Premium Member
Joined
Nov 13, 2016
Messages
10,056
Reaction score
12,258
Location
Hill Country, TX
Now, asking for the moon, K band segmentation would be nice (block out the new 24.160 and 24.167 falses from some Acuras and Pacificas...)
As someone who has to deal with feature requests often, I’m glad you stated WHY you’re asking for a certain thing. But in light of that, I would suggest you instead say what it is you’re hoping to accomplish rather than a request for a particular implementation approach. In this case, a notch filter for 24.164 +- 4MHz might be a way to extend K Block to take it further. But segmentation for K is probably not the right approach to back your way into a notch filter.
 

KnightHawk

Learning to Drive
General User
Joined
Apr 26, 2018
Messages
316
Reaction score
299
Location
Somewhere Out There
The problem with BSM as I encountered them today with 2 MDX's is that, the range is so wide from 24.140 to 24.167.
 

thebenzman

Learning to Drive
General User
Joined
Oct 8, 2016
Messages
8
Reaction score
0
As someone who has to deal with feature requests often, I’m glad you stated WHY you’re asking for a certain thing. But in light of that, I would suggest you instead say what it is you’re hoping to accomplish rather than a request for a particular implementation approach. In this case, a notch filter for 24.164 +- 4MHz might be a way to extend K Block to take it further. But segmentation for K is probably not the right approach to back your way into a notch filter.
Fair point. However, I suppose a good way to view this is instead of just asking for a firmware to block, allowing the user to segment could future proof when this poorly designed BSM's use other frequencies to annoy RD users
 

BlueV1

"(Don't) Give Hate a Chance" -Jamiroquai
Advanced User
Lifetime Premium Member
Joined
Feb 8, 2016
Messages
3,377
Reaction score
6,315
Location
Western NC
The segmenting of K-band has been discussed quite a bit here. :)

Quick establishment of details:
  • US Ka band is 2,600 MHz wide and is usually divided into 10 260 MHz segments
  • US K-band is typically 200 MHz wide total
  • If US K-band were divided up into 10 segments, each would be 20 MHz wide
  • Some preset segments would require using two segments for a total of 40 MHz for one issue on the border between the two

There are already better (in my opinion) methods of accomplishing the quieting down of falses that I already use. Free-form segmenting of Ka and Free-form muting of K and X allows us to specify exact troublesome ranges that we encounter.
Getting a signal of 24.167 from lots of vehicles, mute only 7 MHz of 24.164 to 24.170.
Getting a 34.655? Free-form segment around 34.650 to 34.660. Still getting 34.649 to 34.661 sometimes? Expand it to 34.645 to 34.665.

With the variation we see in BSM frequencies alone, the most future proof method is to use this free form method in all detectors.
 

Nutfield

PSL +0 = road rage victim
General User
Joined
Jan 30, 2015
Messages
29
Reaction score
13
Location
Nutfield
My 2 cents ... 90% quieter with "K Block". Very happy with the results!
I am liking the K block too. Now I can forget about my idea to start a Go-Fund-Me to buy Ka radar guns for the local PDs so I could turn K band off. :wink:
 
Last edited:

AdamIsAdam

Learning to Drive
General User
Joined
Mar 30, 2019
Messages
9
Reaction score
17
Location
Long Island, NY
For me it’s attracted a load of 24.168 - 24.170.:rolleyes: Where did they all come from ?
Well, over all I'm getting less K-Band noise. But, getting hits in some places that I did not use too. Really that is all I have for now on 1.50 firmware. Didn't get any Ka hits this weekend.

After only about an hour or two, I also saw a lot more falses in ranges and locations I hadn't seen before like some others.
 

GTO_04

Premium RDF Member
Advanced User
Premium Member
Joined
May 22, 2011
Messages
4,455
Reaction score
4,991
I think we should be able to figure it out based on whether the R7 is seeing similar falses when K-Block is on. I’ll try to read through some of the K-Block related posts to see if they are getting the same thing.

Update- looks like there are a few mentions of very similar behavior.
I have not downloaded the 1.50 firmware (yet). Are K block and K narrow mutually exclusive? Of can you enable both features?

GTO_04
 

oversteer325

Learning to Fly
Beginner User
Joined
May 7, 2019
Messages
91
Reaction score
209
Location
NC/SC
I have not downloaded the 1.50 firmware (yet). Are K block and K narrow mutually exclusive? Of can you enable both features?

GTO_04
I run K wide so I can’t say for sure, but since a portion of k block is in the k narrow range I’d expect k block to still be available as an option.
 

Pumanator

rawr
Beginner User
Joined
Jan 25, 2014
Messages
78
Reaction score
73
Location
Durham-Chapel Hill, NC
The K Block filter is nice, but for those like me who live where LEO utilize K band, there is an inherent risk of potentially missing a true alert. A middle ground to know that an alert in the K Block range is being received could prove useful to those who value situational awareness. It would be nice to at least be able to view the signal strength.

The K block feature could produce a single chirp, followed by muting only the K block range when a signal is received. This could also be accompanied with the display showing the muted frequency and the display lighting up if in dark mode.
 

Nagorg

If a frog had wings...
Intermediate User
Lifetime Premium Member
Joined
Jul 14, 2017
Messages
275
Reaction score
222
Location
Texas
I was going to flash up from 1.37 to 1.50 but I gather that if K is used frequently in my area, I'm better off sticking with 1.37 for now. Is that a fair summary?

Reading a lot of these posts, I cant help but think how I dont have some of these problems when running my V1 and JBV1 thanks to things like time based muting etc.. But I'll be traveling and want to take my R3 for use in the rental.
 

NorEaster18

Probably stuck in traffic...
Intermediate User
Joined
Sep 5, 2018
Messages
413
Reaction score
788
Location
Northeast US
I was going to flash up from 1.37 to 1.50 but I gather that if K is used frequently in my area, I'm better off sticking with 1.37 for now. Is that a fair summary?

Reading a lot of these posts, I cant help but think how I dont have some of these problems when running my V1 and JBV1 thanks to things like time based muting etc.. But I'll be traveling and want to take my R3 for use in the rental.
I see 1-2 legitimate K band encounters daily and have zero problems with 1.50. It actually got easier to determine a real encounter from a false because it falses much less.

Although caveat is that I mostly see Decatur K band units, so not much experience facing the Kustom low-power stuff
 

KnightHawk

Learning to Drive
General User
Joined
Apr 26, 2018
Messages
316
Reaction score
299
Location
Somewhere Out There
I have not downloaded the 1.50 firmware (yet). Are K block and K narrow mutually exclusive? Of can you enable both features?

GTO_04
Don't know if it is mutually exclusive but I ran my R3 with K block and K narrow enabled. No punch throughs with the K block frequencies so far.
 

Deacon

TXCTG
Advanced User
Premium Member
Joined
Nov 13, 2016
Messages
10,056
Reaction score
12,258
Location
Hill Country, TX
I was going to flash up from 1.37 to 1.50 but I gather that if K is used frequently in my area, I'm better off sticking with 1.37 for now. Is that a fair summary?
I bought my dad a DFR7 a couple years back for father’s day to replace his old crappy Cobra. He had started complaining about the falses to the point where he turned off K-band altogether, a bad idea where he lives. Someone shared a refurbished R3 deal on Woot a couple weeks ago, and I suggested it, and he pulled the trigger. It came with 1.37 loaded. I’m helping him upgrade to 1.50, because I think at this point there’s no advantage to holding back on an older version, only improvements in 1.50 that make the upgrade worth it.

So, short version, my advice is to go ahead and give 1.50 a shot. You’ll probably like it :)
 

AdamIsAdam

Learning to Drive
General User
Joined
Mar 30, 2019
Messages
9
Reaction score
17
Location
Long Island, NY
I'm loving 1.50. But what's with all the 24.168 false alerts now?!
 
Last edited:

Mauserguy27

Learning to Drive
General User
Joined
Aug 30, 2019
Messages
40
Reaction score
80
Location
Southern Ohio
I upgraded from 1.48 to 1.50 and enabled K Block it really didn’t do much if anything for me under many different settings. That’s just my experience my unit was chatty, not to mention it had very poor performance out of the box and after some testing and tuning. I sent it back to Amazon I’m glad to hear some people are having improvements over 1.48.
 

Discord Server

Latest threads

Forum statistics

Threads
77,536
Messages
1,181,589
Members
19,832
Latest member
radardetectorguy
Top