35.5 encounter earlier this week?

[justin81]

I came upon a CO Ka speed trap earlier this week while on my way to work. Frequency was 35.5 according to the spec display on my radar detector. However, I noticed some slight fluctuation between 35.5 and 35.4.

Was this an issue with my detector, or the radar gun itself? The detector held a steady 35.5 and this fluctuation occurred when I was practically on top of the source and then only for a few seconds.

Any explanation for this?

[ActiveKAjam]

Originally Posted by justin81

I came upon a CO Ka speed trap earlier this week while on my way to work. Frequency was 35.5 according to the spec display on my radar detector. However, I noticed some slight fluctuation between 35.5 and 35.4.

Was this an issue with my detector, or the radar gun itself? The detector held a steady 35.5 and this fluctuation occurred when I was practically on top of the source and then only for a few seconds.

Any explanation for this?

It's not your detector my X50 does this too. 35.5 Ka is the hardest radar signal to detect because it's very directional. 35.5 ka is the only reason I'm switching to a more sensitive detector.

[djrams80]

I see lots of 35.5Ka. It has always been between 34.450GHz - 35.550GHz. It's never exactly 35.500GHz. There is a range involved here. For instance, in this video, the readout on my SRX was 35.469GHz.

YouTube - V1 and SRX Working Together Against...

[NiTrO bOiE]

I've only seen an exact 35.5 once (the readout on my 8500 was 35.500 used on campus). Most of the time I see 35.49x (used by HP).

[TSi+WRX]

OK, guys, someone please explain this one to me......

A local township apparently recently got at least one new Ka unit. They've been, before then, entirely K or laser. For easier reference, we'll call this township the "HH" township (Highland Hills, in NE-Ohio).

When I first came upon the signal, I was rather confused - to be honest, I thought that it was another local township, going through the area.

To my surprise, that wasn't the case, and the HH cruiser shot by, with my 9500i displaying in the usual 33.8 area.

The strange thing happened just after he passed me (going the opposite way) - momentarily, the SpecMeter displayed 35.5.

In the next lane over, my direction of travel, was a box-truck.

Was this just some kind of once-in-a-blue-moon saturation/reflection effect?

I was later able to confirm that, indeed, the HH cruiser was operating 33.8, as I came across him yet again (taking the new toy out for a joyride, probably! ).

What happened?

[Azonehits]

Originally Posted by TSi+WRX

To my surprise, that wasn't the case, and the HH cruiser shot by, with my 9500i displaying in the usual 33.8 area.

The strange thing happened just after he passed me (going the opposite way) - momentarily, the SpecMeter displayed 35.5.

In the next lane over, my direction of travel, was a box-truck.

Was this just some kind of once-in-a-blue-moon saturation/reflection effect?

I was later able to confirm that, indeed, the HH cruiser was operating 33.8, as I came across him yet again (taking the new toy out for a joyride, probably! ).

What happened?

I know for a fact that my X50 will not ghost with 33.8 but does on 35.5 in spec mode and expert mode. After several tests using 35.5, at a distance, it will display 35.5 and as it gets closer, it will show 33.6XX or around 33. XXX and go back to 35.5. I have never seen it start with 33.8 then 35.5. What radar detector where you using?

[TSi+WRX]

^ 9500i, date code 4307, and it's been stellar, so far, greatly outpacing my Rev5 x50.

I'm keen to try this again, on my x50, to see what the scenario presents with on a second-check. I've also never seen this kind of behavior before, and I'm just wondering if the signal was so strong that it overloaded - or that it was ghosting (but why to the 35.5, when it was 33.8?).

I'm now half-way to thinking that I must have made a mistake, and saw 33.5 and mistook it for 35.5, but that's honestly me second-guessing myself. I could've sworn I really saw 35.5.

[Azonehits]

I've been saying it all the time but did not fulfill it. Hopefully, I can download the videos this weekend showing ghosting with 35.5 in spec and expert mode.

[TSi+WRX]

^ Don't beat yourself up, bruddah.

Honestly, you've made me feel a lot better, already.

It's just weird, like you said, what I saw. I've never seen that kind of thing before, with my x50.

As long as you think that it's still within the realm of *possibility*, that's all the confirmation/affirmation I needed.

The truth of the matter is that I *know* he's running 33.8 - that's what I saw when I initially encountered his cruiser, and again what I saw on the second pass, later on in the day (a situation where I didn't see the ghosting behavior I saw, at our initial meeting).

^ And that's really all the knowledge I need, until I can make a visual ID.

But like you said, it was just weird, and it gave me that "WTF " pause.

[bigalinwv]

Originally Posted by TSi+WRX

OK, guys, someone please explain this one to me......

A local township apparently recently got at least one new Ka unit. They've been, before then, entirely K or laser. For easier reference, we'll call this township the "HH" township (Highland Hills, in NE-Ohio).

When I first came upon the signal, I was rather confused - to be honest, I thought that it was another local township, going through the area.

To my surprise, that wasn't the case, and the HH cruiser shot by, with my 9500i displaying in the usual 33.8 area.

The strange thing happened just after he passed me (going the opposite way) - momentarily, the SpecMeter displayed 35.5.

In the next lane over, my direction of travel, was a box-truck.

Was this just some kind of once-in-a-blue-moon saturation/reflection effect?

I was later able to confirm that, indeed, the HH cruiser was operating 33.8, as I came across him yet again (taking the new toy out for a joyride, probably! ).

What happened?

This has happened to me once with a plain 8500. A Trooper went by me and it showed 33.8, he then got about 1/2 mile ahead of me and i/oed somebody and it read 35.5. There are no Troopers around here with anything other than one radar head in front, so it was technically impossible.

I think Azonehits had said he was able to replicate the same thing with an X50.