Locations where additional Ka segments (ie. segment 6) are needed

[Vortex]

There's some really good threads where people are talking about needing extra segments or wider sweeps, typically for Stalkers that transmit at 34.8xx or even 34.9xx.

Verified (Sort of) 34.853

I have been running various sweeps on my V1 and logging the hits. I came across 34.853 while driving past the Kent County Sheriff Department in Grand Rapids, MI. It was coming from their parking lot where a number of cruisers were parked. Should I assume that the Sheriff's office is using an old...

www.rdforum.org

Stalker high score

Every time I think I've found the upper limits of where a Stalker can drift, I find another one even higher. My previous *high score* was a NYSP running 34.929 last year Yesterday i was behind an Ulster County Sheriff (marked Tahoe) running a DSR 2X, both antennas at once. The weaker, more...

www.rdforum.org

https://www.rdforum.org/index.php?threads/57857/

It'd be handy to have a quick reference guide for the locations where people have seen confirmed radar guns that would require additional segments. Running 2/5/8 is the norm, of course, but let's cover the exceptions.

If there's anything funky that people have seen in a particular location which requires additional segments, it'll be listed below. (Read through the thread for more details and specifics.) Otherwise the standard 2/5/8 sweeps will be fine.

Alabama: 2/5/6/8: Segment 6
Alaska: 2/5/8
Arizona: 2/5/6/7/8: Segments 6 & 7 for reservation police with older ATR's
Arkansas: 2/5/6/8: Segment 6 around Omaha
California: 5/8: 2 not needed, 5 very common, 8 rare and almost unnecessary
Colorado: 2/5/8
Connecticut: 2/5/8
Delaware: 2/4/5/8: Segment 4
Florida: 2/5/6/8: Segment 6
Georgia: 2/5/6/8: Segment 6
Hawaii: 2/5/8
Idaho: 2/5/8
Illinois: 2/5/6/8: Segment 6
Indiana: 2/5/6/8/9: Segment 6 & 9
Iowa: 2/5/8
Kansas: 2/5/6/8: Segment 6 in Hutchinson
Kentucky: 1/2/4/5/8: Segments 1 & 4
Louisiana: 2/5/8
Maine: 5/8: Segment 2 not needed
Maryland: 2/5/6/8: Traffic cameras may need segment 6
Massachusetts: 2/5/6/8: Segment 6
Michigan: 2/5/6/8: Segment 6
Minnesota: 2/5/8
Mississippi: 2/5/8
Missouri: 2/5/8
Montana: 2/5/6/8: Segment 6
Nebraska: 2/5/8
Nevada: 2/5/8: Segment 9 in Caliente
New Hampshire: 5/6/8: Segment 2 not needed, add Segment 6 for 95
New Jersey: 2/4/5/6/8: Segments 4 & 6 for drifting Stalkers around 34.5 & 34.8
New Mexico: 2/4/5/6/8: Segment 4 and Segment 6
New York: 2/4/5/6/8: Segments 4, & 6 for drifting Stalkers around 34.5, 34.8, & 34.9
North Carolina: 2/5/6/8: Segment 6
North Dakota: 2/5/8
Ohio: 2/5/8
Oklahoma: 2/5/8
Oregon: 2/5/8
Pennsylvania: 2/5/8
Rhode Island: 2/5/8
South Carolina: 2/5/8
South Dakota: 2/5/8
Tennessee: 2/5/8
Texas: 2/4/5/6/8: Segment 4 in Carthage, Segment 6 in Dallas
Utah: 2/5/8
Vermont: 2/5/8
Virginia: 2/5/8
Washington: 2/4/5/8: Segment 4 in Mukilteo and 7 in Pierce County for a 35.2 Stalker ATR
West Virginia: 2/5/8
Wisconsin: 2/5/8
Wyoming: 2/5/8

Alberta: 2/4/5/6/8: Segment 4 & 6
British Columbia: 2/5/8
Manitoba: 2/5/8
New Brunswick: 2/5/8
Newfoundland and Labrador: 2/5/8
Northwest Territories: 2/5/8
Nova Scotia: 2/5/8
Nunavut: 2/5/8
Ontario: 2/5/6/8: Segment 6
Prince Edward Island: 2/5/8
Quebec: 2/5/8
Saskatchewan: 2/5/8
Yukon: 2/5/8

Note: False alerts on other segments can happen, especially with the Ka filters disabled. When reporting weird frequency alerts that you see, please confirm that it's actually coming from a police officer, not just that your radar detector displayed an unusual frequency.

For reference, here are the frequency ranges for each segment:

• Ka1 = 33.392 – 33.704
• Ka2 = 33.704 – 33.896 (33.8)
• Ka3 = 33.886 – 34.198
• Ka4 = 34.184 – 34.592
• Ka5 = 34.592 – 34.808 (34.7)
• Ka6 = 34.806 – 35.166
• Ka7 = 35.143 – 35.383
• Ka8 = 35.378 – 35.618 (35.5)
• Ka9 = 35.595 – 35.835
• Ka10 = 35.830 – 35.998

and here's an explanation about band segmentation in general.

 

[oldcelt]

@hammerdown

 

[rider9195]

Definitely NY.

Personally I never saw a performance loss when enabling seg 6. So why not have it enabled always?

I know some states or agencies require the radar units to be calibrated, so maybe that's why it is seen in only certain areas.

Sent from my SM-G900V using Tapatalk

 

[CJR238]

I encountered 34.8xx in Westchester county a few times.

 

[PointerCone]

There's some really good threads where people are talking about needing extra segments or wider sweeps, typically for Stalkers that transmit at 34.8xx or even 34.9xx.

https://www.rdforum.org/showthread.php?t=58025
https://www.rdforum.org/showthread.php?t=54213
https://www.rdforum.org/showthread.php?t=57857

It'd be handy to have a quick reference guide for the locations where people have seen confirmed radar guns that would require additional segments.

For example:

State: New York
Frequencies: 34.965
Segments: 6

34.965 is "legally" off the centered frequency of 34.7XX. Should you get a citation from that gun, you could certainly ask for the FCC Cert of unit.
I know that's the haunt of @oldcelt and @Nine_C1

 

[NPark]

In Ringwood NJ, confirmed segment 6, 34.83x


Sent from my iPhone using Tapatalk

 

[CJR238]

A confirmed frequency should have a standard type of encounter of that frequency ramping up and down with the LEO being the obvious source. Ideally seeing it more than once.

 

[Vortex]

A confirmed frequency should have a standard type of encounter of that frequency ramping up and down with the LEO being the obvious source. Ideally seeing it more than once.

Agreed. RD's can and do false on those frequencies too so it has to be a confirmed sighting like you describe.

 

[NPark]

Agreed. If your town is small enough, as mine is, and there's only 10 units total or so, I can be sure. Especially encountering them regularly.


Sent from my iPhone using Tapatalk

 

[thanks]

https://www.rdforum.org/showthread.php?t=57857

Unfortunately,
This link appears to be restricted...

 

[Dukes]

Unfortunately,
This link appears to be restricted...

Certain areas are only accessible after being promoted. You can learn more about RDF's promotion system here - https://www.rdforum.org/showthread.php?t=1624

 

[thanks]

I understand that promotion is required, just pointed out that not all of the links posted were accessible to all...
THank you

 

[Vortex]

I understand that promotion is required, just pointed out that not all of the links posted were accessible to all...
THank you

They're not intended to be accessible to all. They're simply a few example threads that have come up recently on the subject. Any nuggets of information about frequencies and locations that would be good to post in this thread will be copied over here as well so you won't miss anything.

@hiddencam @KASHER1979 , I know you guys have seen some stuff lately as well. Could you let me know the frequencies and locations?

 

[hiddencam]

They're not intended to be accessible to all. They're simply a few example threads that have come up recently on the subject. Any nuggets of information about frequencies and locations that would be good to post in this thread will be copied over here as well so you won't miss anything.

@hiddencam @Kasher1979, I know you guys have seen some stuff lately as well. Could you let me know the frequencies and locations?

34.855 at US-65, Omaha, AR. That's Boone County.

 

[Nine_C1]

34.965 is "legally" off the centered frequency of 34.7XX. Should you get a citation from that gun, you could certainly ask for the FCC Cert of unit.
I know that's the haunt of @oldcelt and @Nine_C1

My personal belief is that it's not out of tune Stalkers causing these readings but rather some anomaly in frequency determination (within the detector itself) when the source is a DSR2x operating both antennas simultaneously.

Consider this........the DSR2x is the only dual antenna radar unit designed to operate both antennas simultaneously, and to ensure no interference betwixt the two, one is tuned 10-20 MHZ below center and the other 10-20 MHZ above center. For this reason, the antennas provided with the DSR2x have a different serial prefix denoting the difference between the two antennas.

Also consider that (according to Stalker's patents) the DSR units utilize FM modulation to determine directional target information.

What this means (to me anyway) is that a DSR2x operating on both antennas simultaneously (and with some degree of modulation present on both channels) presents a unique challenge to the frequency counting scheme applied by our detectors but not necessarily any real issues with detecting the signal(s) themselves.

Let me explain my thoughts further. Our detectors are Superheterodynes.....meaning they MIX signals by design. The incoming signal is mixed with an internal signal and it's actually the difference between the two.......the intermediate frequency (or IF), that is tuned to and detected by the detector. In fact there are (3) mixing stages as the signal is downconverted until it ends up becoming a 10MHZ singal presented to the FM demodulator and then to the micro for alert processing.

With only one signal present, or multiple signals with various power amplitudes (and a sufficient frequency spread), it should be no big challenge to keep each one discrete with the correct frequency reported. But throw in two modulated signals fairly close in frequency and power amplitude and there could be some unanticipated mixer byproducts or a direct detection in the 1st IF or 2nd IF from the two radar signals THEMSELVES mixing.........and you could get some unexpected and inaccurate frequency readouts on your detector.

Basis for my belief......Pre BS/RDR I had witnessed (on several occasions) readings of 34.9xx with the RedLine vs. Ulster County Sheriff cars equipped with the DSR2x. Yet since BS/RDR I have had no issues picking these guys up running with just segs 2/5/8 enabled and the readout is always slightly above or below center (34.700) as I would expect. So what I think is that since I am not scanning up to 34.9xx I am not seeing the erroneous mixer output causing the 34.9xx readout, but rather each independent signal mixing with the 1st LO frequency (as it should) and thus getting a true (and accurate) frequency read on the signal(s) received.

What I am saying is that if you run into this scenario and you have seg 6 enabled on your RedLine it may report 34.9xx........but if you had seg 6 disabled it would likely report the correct frequency of 34.6xx or 34.7xx.

A side story.......different but applicable. With segs 2/5/8 enabled on my RedLine it would always report 33.7xx when I fired off my MPH Enforcer inside the car (as it should). And then one day I decide to go plink some targets with the MPH but I forget to shut the RedLine off, so it startled me when the RedLine shreaked it's warning when I plinked the 1st target (zapped myself.....Ha Ha) but when I looked up I was even more amazed at the frequency being reported......35.xxx! I'm like.....whoa.....this unit has fallen WAY the hell out of tune. Pretty upset with a radar I dropped $900 on I can tell you. Then it occured to me that I had disabled seg #2 on the RedLine some time ago. When I turned it back on it went back to reporting the correct frequency from the MPH unit. So this only proves one way that the frequency counting function inside our detectors can be spoofed......but I suspect the DSR2x has found another way (on occasion) with it's dual (modulated) signals.

 

[fishing66]

There's some really good threads where people are talking about needing extra segments or wider sweeps, typically for Stalkers that transmit at 34.8xx or even 34.9xx.

https://www.rdforum.org/showthread.php?t=58025
https://www.rdforum.org/showthread.php?t=54213
https://www.rdforum.org/showthread.php?t=57857

It'd be handy to have a quick reference guide for the locations where people have seen confirmed radar guns that would require additional segments.

If there's anything funky that people have seen in a particular location, it'll be listed below. Otherwise the standard 2/5/8 sweeps will be fine.

Alabama:
Alaska:
Arizona:
Arkansas:
California:
Colorado:
Connecticut:
Delaware:
Florida:
Georgia:
Hawaii:
Idaho:
Illinois:
Indiana:
Iowa:
Kansas:
Kentucky:
Louisiana:
Maine:
Maryland:
Massachusetts:
Michigan:
Minnesota:
Mississippi:
Missouri:
Montana:
Nebraska:
Nevada:
New Hampshire:
New Jersey: 34.83x in Ringwood
New Mexico:
New York: 34.8 & 34.965
North Carolina:
North Dakota:
Ohio:
Oklahoma:
Oregon:
Pennsylvania:
Rhode Island:
South Carolina:
South Dakota:
Tennessee:
Texas:
Utah:
Vermont:
Virginia:
Washington: 35.2 in Pierce County
West Virginia:
Wisconsin:
Wyoming:

34.556, Route 80 Eastbound in Rockaway NJ

 

[OpenRoad]

There was a post I did a few years ago where I found some traffic cameras that run inside segment 6 in Maryland.

 

[bhrodeoaz]

Here in AZ i have segged my redline for 2,5,6,7,8 for older ATRs used by various reservation police

 

[alloy00]

Great info as always, Nine. We should be able to test for this. For those running segment 6, next time you run across something in segment 6, turn it off and see if you still alert to the signal with only segment 5 enabled. I will turn on 6 and try this out too.

 

[oldcelt]

The readouts I've gotten that were above 34.900 in all but one case were running a single antenna. The 34.965 I got a few months ago was behind a DSR2x (Ulster Co Sheriff) running both antennas at once. I will also try to remove seg 6 (momentarily) next time I get a single ridiculously high readout, although that's not always possible to do reprogramming at 65 mph (+) and drive safely in traffic; e.g running the NYS Thruway between exits 23 & 24