- May 7, 2019
- Reaction score
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.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.
Update- looks like there are a few mentions of very similar behavior.
Most Acura’s I’ve noticed false in the K Block range (24.194-24.204). I have also run into some late model MDXs that give a 24.168 false as well. The other day I came across a Honda Odyssey that gave a 24.211 false. Honda’s/Acura’s are a PITA. So if your R7 was indeed falsing to your own car, mute memory is useless. It works on GPS, so as soon as you’re outside of the lockout range you created, the detector will alert again if it’s your car creating the false. Use mute memory only for stationary false alerts. You can try running in Advanced mode if you’re not already and lower your K sensitivity. Make sure K filter is on, try turning TSF on. K Narrow is another option that only scans up to 24.200 so that will definitely help. I use K Wide as I encounter a lot of legit K Band, but Narrow might work for you. You just have to dial in the settings over time to what works best for you and your area, but driving the worst BSM offender for the R Series will most likely make it more difficult to accomplish.
2012. On my way to work this morning same thing 24.216 to 24.223 it would alert then say rear/front (mainly rear) and shut off. Then step up a digit after a minute and do the same thing. I am going to test this out further on my road trip coming up this Friday as I am headed through the mountains where there would not be any alerts at certain sections.
There were barely any vehicles around me. On the original firmware this did not happen. It was the quietest thing ever but with the update it introduced this issue. I will play with some settings suggested above as I run the City mode currently. I still need to do a factory reset after the firmware update I did as I was doing some reading this morning and that's what was suggested as a procedure.