Lifetime RDF Contributor
Lifetime Premium Member
- Jul 31, 2016
- Reaction score
View attachment 65356 Okay, this should hopefully address the requests of 99% of people with R1 and R3's.
What I did:
1) Video the heartbeat icon of the R1 turning on and off at 240 fps
2) Calculate time from heartbeat on to heartbeat on again = Time of 1 "scan cycle" (according to Uniden R series user manuals, this was calculated for 4 cycles to obtain an average)
3) I added a chart showing how much bandwidth is scanned for each segment or setting
Note1- If I did not test the exact settings you run and you wish to get an approximate scan time (in ms) for your settings, add up the total bandwidth (in MHz) scanned under your settings, and plug in for 'x' in the slope-intercept formula to calculate 'y' which will be roughly the time to complete 1 cycle (since bandwidth scanned and scan cycle time are roughly linear).
Note2- The GHz per second "scan speed" (overall scan time/total bandwidth scanned) appears to increase as you increase the total bandwidth scanned. This most likely does not mean that the detector is scanning faster, but rather it is not being penalized for segmenting or "switching" between segments as much.
K or Ka Filtering does not seem affect scan times within a statistical difference.
@benzr @thesilverbullet @Salty @NPark
I tried to replicate the calculations for my settings. I'm running some fairly unusual settings because 33.8 is 90% of what I see here in Iowa. I've seen 1 K band, 1 34.7, 1 35.5 and 1 laser in the last 9 months of driving. I've had a dozen encounters with the city low power K band photo radar trucks (which interestingly in 4 dedicated runs are picked up at around 100 ft with K band Advanced 70%, but completely not detected at 100%. Go figure. More testing needed. Since the PD publishes the locations of these each week, I just mark them in Waze if I think I'm going to be around them that day). Dozens, maybe a hundred other encounters have all been 33.8. I've been trying Ka POP on both to see how it impacts performance, but also to see if it increases falsing. In my daily drives (40 minutes a day in town, around the interstate bypass twice a week), I'm not counting any more falses. Even though it can't be used to ticket, my logic for running Ka POP on is that it's theoretically available to run in 90% of the radar guns here. And if it's available, my logic continues, it's possible that an officer would use POP to pick out targets, who might otherwise be unaware they are being clocked, even if they are running an RD, to initially get a read on someone, then switch to regular mode to get a speed that can be used to ticket. I'm hoping to pick-up those POP "chirps" if they truly exist. I've picked up one POP signal, in about 90 days of running KaPOP on, but I could not verify the source.
Uniden R3, Advanced mode, X off, K wide 70%, Ka 2/5/6/8 100%, K filter, Ka POP on, Ka filter, Laser, GPS. (I'm running Seg 6 because I travel through IL, IN, OH and PA twice a year and I don't want to miss the reported out of tune 34.7 guns in IL and IN. I manually switch on X band which is already set @ 70% in Advanced when I hit OH on those drives.)
Using my iPhone in slo-mo 720p/240fps mode, I recorded a 30 second set of cycles. I counted 131 "heartbeat" cycles, or 262 cycles for a full 60 seconds.
60 seconds/262 cycles counted = 229ms/cycle
It's still scanning 1208Mhz for 2/5/6/8, but those extra POP scans are "only" slowing my unit down by 28ms over regular 2/5/6/8.