Losing faith in my V1

[LeftLaneInPA]

Lately, my 3.8952 V1 has been giving me some real short Ka-band detections. And in most cases, I'm pretty sure that it's C/O, but the range I was getting an alert was... frightening.

The last couple of Ka-band alerts I've been getting, I'm seeing the cop with my own two eyes before the V1 goes off and I would have been toast if it wasn't for Waze. The one before last was a NJ State Trooper on the side of the road with a customer. It was obviously C/O because he wasn't in the car at the time, he was out talking to the motorist. My V1 didn't go off until about 800 feet away, even though the cop car was clearly visible.

The last one was a park ranger running 35.5 Ka-band, sitting on the side of the road. My V1 didn't go off until I was quite literally close enough to see his hair style. Again, almost positive that it was C/O because he was on his cell phone talking to somebody as I passed, not paying attention to passing traffic at all.

What's most disturbing is that I won't get maximum alert on the V1 until I'm literally 10-20 feet in front of the cop, if even that. I've passed cops running Ka-band C/O and even though I got within 15 feet of them, the V1 never "maxed out".

So far, K-band detections seem fine, but Ka-band has shown a drastic drop-off in range the past two months or so. I've been holding off sending it in for repair to see if the "new" V1 was coming out, but it looks like I'm going to have no choice now.

Very disappointing.

 

[Deacon]

What did VR have to say about it?

 

[LeftLaneInPA]

What did VR have to say about it?

I haven't contacted them yet.

 

[Nine_C1]

Lately, my 3.8952 V1 has been giving me some real short Ka-band detections. And in most cases, I'm pretty sure that it's C/O, but the range I was getting an alert was... frightening.

The last couple of Ka-band alerts I've been getting, I'm seeing the cop with my own two eyes before the V1 goes off and I would have been toast if it wasn't for Waze. The one before last was a NJ State Trooper on the side of the road with a customer. It was obviously C/O because he wasn't in the car at the time, he was out talking to the motorist. My V1 didn't go off until about 800 feet away, even though the cop car was clearly visible.

The last one was a park ranger running 35.5 Ka-band, sitting on the side of the road. My V1 didn't go off until I was quite literally close enough to see his hair style. Again, almost positive that it was C/O because he was on his cell phone talking to somebody as I passed, not paying attention to passing traffic at all.

What's most disturbing is that I won't get maximum alert on the V1 until I'm literally 10-20 feet in front of the cop, if even that. I've passed cops running Ka-band C/O and even though I got within 15 feet of them, the V1 never "maxed out".

So far, K-band detections seem fine, but Ka-band has shown a drastic drop-off in range the past two months or so. I've been holding off sending it in for repair to see if the "new" V1 was coming out, but it looks like I'm going to have no choice now.

Very disappointing.

I don't know if this makes you feel any better, but this can and DOES happen with any detector.

I've had 35.5 reception on an M3 drop to where I got burned with CO (luckily during testing)……...an R3 that was seeing CO 34.7 (after me).......and an LRD950 that I had to take a part and re-tune as the center frequency had drifted by over 60 MHZ. Don't want to run one of those on Ka Narrow unless it's very close to center.

It's not unknown for the V1 to "lose it's tune"...……...in fact it was fairly common until they added the crystal tuner and digital temp control back on version 3.851. Even so, there are numerous components in the RF section that can give out or go rotten over time that self tuning cannot compensate for.

The master controller for any detector is still you...…….when you notice sub-par performance on a regular basis that is the only notice you'll get that it's time return to mother ship for a checkup.

Good luck.

 

[johnboy00]

Try this in JBV1:

1. Push "<Factory Reset>" profile.
2. Push your usual profile and sweeps.

Then report if same or better.

 

[Tallyho]

There's really only 2 ways to diagnose this, either send it to VR or test it yourself.

If you are running custom sweeps all bets are off and the first thing to do is turn those off completely. There's very little reason to run them.

Never seen a V1 out of tune on Ka either, but I have seen corrupted sweeps.

 

[RedRocket]

Same thing happened to Ka detection on my V1 a few years ago, X & K-band worked fine but lost most of expected range until within about 300ft before alert sounded.

 

[LeftLaneInPA]

Try this in JBV1:

1. Push "<Factory Reset>" profile.
2. Push your usual profile and sweeps.

Then report if same or better.

Will give that a try.

Post automatically merged: Sep 16, 2019

If you are running custom sweeps all bets are off and the first thing to do is turn those off completely. There's very little reason to run them.

I'll also try this as well. I'll turn off Euro Mode and just run "Auto" with Ka turned on and see what happens.

 

[Tallyho]

Same thing happened to Ka detection on my V1 a few years ago, X & K-band worked fine but lost most of expected range until within about 300ft before alert sounded.

What version firmware out of curiosity and was this in Euro mode?

 

[InsipidMonkey]

Happy to provide a Ka gun if you want to do some controlled testing. PM me.

 

[Tallyho]

Will give that a try.

Post automatically merged: Sep 16, 2019

I'll also try this as well. I'll turn off Euro Mode and just run "Auto" with Ka turned on and see what happens.

In this day and age why VR doesn't turn off Ka Guard from the factory boggles my mind.

I wouldn't run in Auto either, although that could solve the issue. Just turn Feature#6 in the down arrow position when manually programming your V1 to turn off Ka Guard.

No reason to leave you more exposed than necessary.

 

[RedRocket]

What version firmware out of curiosity and was this in Euro mode?

I do not remember exact f/w, but it was before the last update of 38952 as I recall.Did not run Euro mode.

 

[LeftLaneInPA]

I wouldn't run in Auto either, although that could solve the issue. Just turn Feature#6 in the down arrow position when manually programming your V1 to turn off Ka Guard.

I've never had Ka Guard turned on, ever.

 

[johnboy00]

In this day and age why VR doesn't turn off Ka Guard from the factory boggles my mind.

I wouldn't run in Auto either, although that could solve the issue. Just turn Feature#6 in the down arrow position when manually programming your V1 to turn off Ka Guard.

No reason to leave you more exposed than necessary.

You can turn Ka Guard off and on in less than 3 seconds with JBV1. Long press the V1 settings at bottom of alert screen, tap Ka Guard.

 

[Deadhead1971]

I’ve had some short range 35.5 encounters C/O on my Uniden R1- around curves, hills and other visual obstructions. With a short range R1 alert, I can only imagine it would be less on a V1.

 

[LouG]

I'm putting my money on corrupted sweeps.

 

[LeftLaneInPA]

I’ve had some short range 35.5 encounters C/O on my Uniden R1- around curves, hills and other visual obstructions. With a short range R1 alert, I can only imagine it would be less on a V1.

These were clear straightaways when I already had a visual on the cop cars.

 

[Deacon]

Definitely do a factory reset, see how that changes things first. Here are the steps:

1. With power being supplied to the V1, starting with the Control Knob in the "off" position.
2. Press and hold the Control Knob in while twisting the Knob "on" and continue holding in the Knob until all front-panel lights are on (takes about 5 seconds).
3. Release the Control Knob.
4. Press and immediately release the Control Knob to display software version.
5. Press and hold the Control Knob until the Front Arrow is illuminated to return all programming features to the factory default.
6. Press and immediately release the Control Knob to exit software version display.

Turn it off and back on again, and then see how it reacts in pure factory setup. Ideally you have a test source to work with (worst case scenario an unexpecting and unaware LEO down the road running C/O—best case scenario buy or borrow radar equipment) in order to see if there’s any difference. Then push your sweeps and compare. Or just disable Ka Guard and go from there.

 

[Choose Life]

Had non crystal controlled V1 that would have a 35.5 gun practically running in its front horn and it had a couple bars and dropped signal while still 300ft away more or less
You just need a tune up

 

[Brainstorm69]

I'm putting my money on corrupted sweeps.

Have to agree this is a likely culprit. Try the reset as others have suggested. I'd even try re-pushing your sweeps right away. It it still acts weird, then try other trouble shooting or send to VR.