Band Segments in My Area, STI-R+ Data Dump. Comments?

[Wannago]

Today I did a dump of my STI-R+. Since I got it installed, I have logged the following Ka hits:

27 different freqs within seg #1
2 different freqs within seg #2
3 different freqs within seg #3
0 freqs within seg #4
12 different freqs within seg #5
0 freqs within seg #6
0 freqs within seg #7
11 different freqs within seg #8
0 freqs within seg #9
0 freqs within seg#10

As I am currently running with band seg disabled, I want to turn segmentation on. I have been told that there is no difference between the hardware / KA freqs used by cops in the US vs here in Canada, and as such, I should be able to turn off all segments except 2, 5, and 8. I decided to leave them all on for awhile and see what frequencies are used.

All of this data was gleaned while in the city, and with many of them, I never saw a cop, so can't confirm many of the bands with the exception of 34.682 (Seg #5).

Based on the above, am I safe to only use 2,5, and 8? What about all the hits in seg #1? Would all those seg #1 hits be falses?

Also, I assume date and time in the data is in UTC (GMT)?

Thanks.

[kpatz]

Segment #1 is probably all Cobras and satellite dishes...

I never knew the STi-R+ logged hits by segment. That's pretty neat.

[nine_c1]

Logging hits by frequency........that is SO FRIGGIN COOL!

Now THAT is a very usefull tool for the expert user! And what a smart approach, to log hits for a while BEFORE segmenting the unit Wannago! You're gonna be good at this.

Like Kpatz said, most of your hits to date have been falses in segment one unless they are running some old photo radars in your area.

Segment 2 and 3 are also likely false alerts due to leaky detectors, but the 2 hits in segment two could possibly be MPH Ka units which are centered on 33.8.........however, MPH units are not nearly as popular as Stalker and Kustom. I'd leave Seg 2 on for a while and try to ID the LEO if there really is one, if you come to find these are all falses in your area, then you can kill Seg 2 as well just in your local area. When traveling abroad, I'd always run with at least 2/5/8 to be safe.

The hits in segments 5 and 8 are all legit! It's also good to see a clean slate in segs 4,6 and 7 and 9. This is insurance that you have not run into any LEO's with out of spec radar units.

Wow........I didn't see anything about this data logging feature mentioned in the online manual for the Plus, but I remember seeing a reference to it on a Canadian website. I asked Escort about it but never got a response!

http://escortradarforum.com/forums/s...8&postcount=78

It's excellent to hear it's real and available on the Plus!

[snoopyc4]

Segment #1 is Ka 33.392-33.704. I'm guessing you've encountered a ton of leaky radar detectors (probably Cobras) since their frequency usually hovers around Ka 33.6.

[Wannago]

Sadly, I can't take the credit for discovering this...another forum member (can't remember who) told me about this while ago, so today I decided to give it a try.

In detector tools, there is an option (tab) called "Police Verification" where you can download the data - this gives you the information. It is saved in a MS Excel format (.csv file). It doesn't actually group them into the specific segments; I ran a quick pivot table then did that myself manually. The report shows the actual frequencies. FYI...I believe the time is in UTC (GMT) and the speed is in MPH. I recall the April 6th alert, and it was on a major freeway and even though I have my unit set to DISPLAY in metric, it looks like the data is stored in Standard format - I sure wasn't going ~60 km/h on that road.

Below is a picture of some of my actual data as it is saved from the RD:

[kpatz]

OMG... it's the ultimate GEEK's radar detector! You can export Excel spreadsheets out of it! Now I really want one!!

I can see my "Radar Bands By Town" thread suddenly becoming far more sophisticated. I should put it on a website where you can upload your STi-R+ spreadsheets to it and it updates automatically.

That feature would be really neat if it were tied into a carputer or something that could pull the data in realtime and update a Trapster-like database with actual radar hits with GPS locations. I wonder if Belscort had that in mind when they added this feature. Actually it's probably the database it keeps for locking out falses, and they let you download it to verify that you didn't lock out anything "real". Does it indicate in the spreadsheet if a particular frequency/location is locked out?

I noticed it has 4 X columns, 2 K columns and 2 Ka columns? 1 column per bogey as shown in an Escort "expert mode" display perhaps?

I have to wonder what it logs for laser? PPS rate? You should shoot your unit with a laser source and then export the spreadsheet and see what comes up in the laser column.

Are you running with RDR on or off? Locked out any falses w/GPS? I wonder if it logs alerts that are filtered out using those features.

[SaltyinNJ]

Holy crap thats AWESOME!

[Wannago]

I have to wonder what it logs for laser? PPS rate? You should shoot your unit with a laser source and then export the spreadsheet and see what comes up in the laser column.

Are you running with RDR on or off? Locked out any falses w/GPS? I wonder if it logs alerts that are filtered out using those features.

My antenna is mounted behind my bumper cover, so it can't detect laser (I have a LI for that) so unfortunately, I can't test the Laser data. I have laser "off" in my options.

I have RDR off, and yes, the unit has locked out several falses on its own, plus a handful of X falses that I manually locked out. I don't see anything on the spreadsheet that appears to indicate if any specific alert was filtered or not. However, now that you mention it, there are several entries that have a date, time, lat / long, heading and speed entry, but there is no frequency information listed in any of the bands columns (see rows 9, 33, 39,40, and 41 above as example). I was wondering why it would log this info without logging a frequency as well, but now I wonder if those are perhaps the locked out locations?

If you like, shoot me a PM and I can email you the full spreadsheet...it is rather extensive...over 38,000 rows

[Wannago]

Earlier today, I picked up a Ka photo radar van on the way to work; pretty good detection by the STI-R + and a defininte save, as he was parked in a pretty nasty spot (backed in partially behind a building so that he looked like one of several parked vehicles in the same spot), although I wasn't speeding by "that" much. So tonight, I decided to do the Defender database update, and while I was at it, I decided to turn band segmentation on (to use only bands 2,5, and 8). I also did another dump of my data.

This morning's photo radar van was shooting 34.592. Another photo radar van from 2 days ago was using 34.595. I was able to verify a local ghost car running C/O 34.674 Ka.

Looking in the user manual, 34.592 is the divider between seg 4 and 5. This makes me a bit nervous. I'm assuming the local cops all use the same photo radar units, and that it is not unusual to have a variance in the frequencies (34.592 to 34.595). However, in my uneducated opinion, if the 34.592 gun had been off by another .001, I wouldn't have received an alert and would have instead been getting a nice surprise in the mail.

Is this something that I should worry about, or is it a one-off with a gun that is a bit out of tune? Should I perhaps turn on seg 4 as well?

Thinking a bit more about the ability to dump data from these units, that might come in handy in the event that I were to get a ticket when I KNEW I wasn't speeding. All I would have to do is present the spreadsheet that will show the date, time, location, speed, and frequency of the radar. Of course, it could be argued that the data in a spreadsheet is easily altered, but it still might help to create "reasonable doubt".

[kpatz]

I'd leave segment 4 on just in case. Sounds like you have some of the older-style photo radars that fall into that gap.

34.674 from the ghost car is within the range of a Stalker unit (they're 34.7 but they can vary by +/- 50 MHz or so, or more). That's well within segment 5.

I wonder though if the segments on the STi-R+ have hard cutoff points or if they leave a little leeway in there. Say, if 34.592 is where segment 4 ends and segment 5 begins, there may be a 10-20 Mhz window that overlaps both segments, so 34.592 would alert if either segment 4 or 5 are on. If you encounter a photo radar van that falls below 34.592, try turning segment 4 off and make another pass by it to see if it still picks it up. You may still be ok in segment 5.

Definitely turn segment 1 off though. That's where 99 percent of the Crapras live.