130,000+ miles with JBV1!
Lifetime Premium Member
- Feb 8, 2016
- Reaction score
- Western NC
The picture for me is getting clearer now.Hardware is latest, firmware one behind latest (basically the one where the default out of box for Junk isn’t On and I have to flip it On). Mute lever is at 10 o’clock and volume goes from 2 to 3 or 4 o’clock depending on “at the moment“ needs. It’s not a muting issue, it’s just a detection issue. K anything is always there and alerts, doesn’t matter if it’s 1 bar or 3 bars... it’s mostly door opener issues, sometimes we use BSM incorrectly. GMCs, some Honda’s, Mazda’s, Acura’s will have BSM hits, but mostly door openers, depending on area. It’s not that big a deal, I know where everything that alerts is and how it alerts pattern wise, so I don’t miss a legit K band, but I really thought the gen 2 was going to have better filtering and from what I’m reading, it addresses maybe 10–15% of it in A mode and that’s simply not enough for me. Hopefully K is just buggy at the moment and a firmware update can address things on the gen 2, but who knows.
The other thing is, I also tend to drive much closer than most and hearing some of the short distance punch through stories even on filtered new ones makes me think I’ll still cross within that threshold and it’ll still alert.
If you have to turn on Junk-K-Fighter then you are using v3.894. (Starting late 2014 - Early 2015 I believe)
There was also a third firmware released before shutdown; v3.8952 that came out after mine.
I have some tests (and even unposted videos) about TMF2 that most likely directly applies to what your experiences are.
Normally for me, TMF2 combined with the built-in K-band muting features means that I'd barely hear a muted alert from a BSM vehicle before I passed it. "Beep", "beep", done.
Over a period of a few weeks Brainstorm69 and I were discussing how TMF2 works. One morning I had a great opportunity to repeatedly test TMF2 by following a new Honda Pilot for roughly 20 miles at desolate highway speeds (70-80 MPH) and mostly straight roads.
Using my own car's distance-measuring cruise-control system, I was able to determine that TMF2 would completely resist alerting to the Honda in front of me until I got to about 25 yards behind it. ONCE the alerts started though, it would continue to alert until I backed off to around 100 yards. I did the test something like 15 times in a row and got the same results each time. I also noted that I could stay around 35 yards away for minutes at a time and never get an alert. I believe I could stay that same distance the entire trip and not hear a peep.
Turning off TMF2 showed that I would get the Honda's BSM even farther than 100 yards and there was no relief until I backed off even further. (Beyond 110 yards. Couldn't measure any farther away than that.)
Note that Custom Sweeps mode is very much like All Bogies, but you can enable and disable K-band by holding down the mute button. In Custom Sweeps, the Logic modes are off I'd say.
I don't believe that TMF2 has any sense of speed so I'd say that the same distances would apply at 25 MPH, etc.
Having said all of that, in my experience, the Gen2 K-Verifyer is tremendously better at not alerting to Honda/Acura at 24.200+/-. I can go days and not get a single beep from a Honda and even the occasional false Honda beep is due to saturation of the band from other sources.
It also seems quieter against Mazda at 24.125+/- but isn't entirely silent up close.
GM's are still an issue. What I notice now is that one signal of the pair is often not showing an alert. That's causing the BSM filter that looks for those pairs to fail to activate.
I'd bet that if you are in situations where you drive close behind BSM cars, you might not be able to tell much of a difference. TMF2 is the primary "filter" in those instances, not the Logic modes.
Post automatically merged:
I don't think anyone has had both v4.1018 and v4.1019 available to them to test yet.