Running With Scissors
- Dec 12, 2015
- Reaction score
- Bay Area, CA
Sorry my mistake. I got distracted. Thanks Jon. My bad.Just a small correction, the Pro M is not an Attowave detector which is why it can filter BSM so well vs other Attowave products. It is made by our other contract manufacturer in South Korea. The XP and SP have similar BSM issues to the R3 since they are also Attowave products. They are less sensitive and the architecture is different so they are slightly better, but it's the same basic issue. But the Pro M is a completely different architecture.
Thanks!I suggest give to it a try and see if it behaves in your area. I have lots of Honda/Acura encounters and I can tell it's not quite on par with 1.37. I can use City mode on 1.48 for releif if I'm boxed in by BSM polluters. While 1.46 just screamed bloody murder no matter what the settings were.
Same here. 1.46 lasted about 3 hours and reverted back. I hope 1.48 will be better. I hope to do the update tonight.Ya. I couldn’t wait to get rid of 1.46!! It was awful. First day I had it. I drove on the freeway, and all it did was tell me where every Honda was—even if they were 6 lanes over on the other side of the freeway!!
Which do you prefer? I'm thinking about updating at least one of my R1's to 1.48 from 1.37, but if it's no better, than I'll wait till the next one!I don’t think 1.48 is any better at BSM filtering than 1.37- to me they appear the same. 1.46 was worse but so far 1.48 appears about the same as 1.37 as it relates to K filtering. Just my opinion so far using it several days
I agree. I'd be thrilled if they just gave us a setting to turn a notch filter on that eliminated everything from .196- .200Well, so much for that. I was behind a new Honda CRV for about nine miles on a country back road and the R3 was alerting at 1-2 bars the entire time. 24.198. I sound like a broken record, however, K band segmentation seems like a way to deal with Honda BSM falses.
I'm starting to feel the same way! 1.37 is a bad [email protected]#*h!After reading what's been posted so far, I'm staying with 1.37. I kinda feel like 1.37 might be the windows 7 of the R versions. It's as close to perfect as it gets. Maybe it just doesn't get better.
Agreed!! I just put together a video with my local MRCD cams as the stars of the show showing the difference between 1.46 and 1.48.They totally killed MRCD with 1.48, it is pretty much useless right now.
I have a fixed MRCD spot that was consistent with 1.46, now 1.48 doesn't see it until you are right on top of it.
See my post above with video link of my MRCD experience in 1.48I’m not sure what to make of this? Any videos?
I had an issue where the R3 was mistaking a K band speed sign for MRCD with 1.46. It only happened whe I switched on MRCD. It acted normally like the Pro-M, R-EX, and RC-M once I turned off MRCD
1 mile seems pretty far considering what and how MRCD operates.
Buying an MRCD set up us cost prohibitive. I think it starts at $30,000.00 and goes up.
Sent from my iPhone using Tapatalk