- Aug 8, 2018
- Reaction score
I agree with your assessment of the 3 vans, those are all I have seen too in Wgtn. Unfortunately I cannot see the frequencies (as they are hidden due to my remote setup) but would probably start with your recommendation as it should eliminate falses and make most if not all detections valid.@Zakk @DEMON5
For us in Wellington I would recommend have muting above 24.060 turned ON.
Please correct me if I'm wrong, but as far as I have seen in recent years, we only have three redflex vans in our area. A red hyundai van, a dark blue hyundai van and a silver VW van. In my experience, all of these three vans seem to be operating below 24.03.
Take a detour over SH29 on the way home. Mr Redflex is waiting. Be careful though, it got a friend of ours back in March while trying out her hyper SUV. She's now a waze user.Just need to find a redflex camera now, but not many around my parts but hopefully on my next trip to Auckland.
One thing I noticed today, is that I use the signal strength #2 option (the circular dial style rather than straight bar graph). With hide K mutes off, the frequency reading was greyed with audio muted but the circular signal strength dial was still in colour - should this (or can this) be grey as well. I didn't try this on the #1 straight bar graph signal strength. This might have been something that Uniden fixed on the 129 change log for mute memory frequencies ?
I haven't tried that, I only tested the other display option #1. However, with Hide mutes ON, those should not be displayed at all. Correct?
BRD said:8. Display Signal strength level in grey color for Mute Memory in Alert Display #2 mode
Correct, only when Hide Mutes is off, display option #2. When On, the entire alert is not displayed as intended.
Just checked, it was indeed a fix in the 1.29 changelog ;
Enhancing MRCD detection range Rear Antenna Sensitivity Attenuation Narrow down the frequency range of Mute Memory function - X Band: 25MHz-> 10MHz, K Band: 30MHz -> 10MHz, Ka Band : 100MHz- > 20MHz If the main alert is locked out, the secondary alert becomes the main alert so users can lockout...www.rdforum.org
I also consider most people would be running with hide mutes ON
@Mithheru, possible to find this code in 129 and implement the fix in this new firmware? Would be handy as I also run signal strength display option #2
I'm looking into this to see if there is an easy solution.
@Mithheru, would removing MRCD detection free up enough code as we don't require that feature here?I'm looking into this to see if there is an easy solution.
Post automatically merged:
I have found the fix, however, looks like there are several new blocks of code needed to draw all the alert blocks in grey etc. This would require more spare code than I currently have to play with.
I guess if you use the R7 on a daily basis for commuting you would get an idea of what K falses you get, and which settings would work best for you. The ones which pushed through were actually below the 24.060. Saying that, the flexibility you have added is perfect for R7 users in NZ!I'm running mine with 26.060-24.110 muted. Hide mutes ON. So with this setting I'm obviously finding the pole mount redflex cameras are also muted (thereby relying upon GPS warning for those). Still not seen a redflex van. So far, in this setting, I only know two false locations around Wellington region that are within this really narrow K range.