Returning old timer with 3.826 question

[Buz]

Haven't been here in what feels like a couple years.

Quick question.
Still have 3.826 working great. Has anything come along worthy of an upgrade or am I good?

Buz

[AirMoore]

Nope you're good to go, their newest units have some digit components so that they have an "E" error, which is basically akin to "Service Required" from Belscort... basically they just copied Belscorts idea of a self-test.


For awhile "E" errors plagued their units, with E's everywhere... now they have secured this and seem to be in good working order... as far as real upgrades worthy of more money into the new unit... not in my book.

My $.02 on that.


My .826 is around and kicking... nice to see you back.

[ghz1]

Don't think VR have copied bell at all. Wasn't it VR who ran a self test first?The "E's" been there for a very long time? not just in the latest firmware. Anyway My V1 was a .826 then I got it changed to a.863. I'm really happy with it ( I was happy with my .826 too). My Ka is hotter. Just remember if your going to upgrade it, It MAY not come back the same detector. Could be better/worst.
The "E" thing was around the .85's doesn't seem to be a problem with the .863 and up.

So in short no don't do it.

[AirMoore]

Don't think VR have copied bell at all. Wasn't it VR who ran a self test first?The "E's" been there for a very long time?

No I do believe Belscort had this long before VR mate.

[jdong]

I think Belscort was definitely first on the scene for self-tuning and self-diagnostics.

But IMO the >=3.858 revision is a good thing to have just for the presence of this feature; I've read too many painful stories here about earlier V1's dying silently and only realizing that after a no-alert ticket.

[ghz1]

http://www.radardetector.net/forums/...libration.html



Pete Kaufman wrote: (thats the V1 Dude)

Dear Sir:

Thanks for your email.


The V1 has always had a self-test sequence. You can hear the test for the different radar and laser bands as well as see the visual displays. This means that the V1 is performing self-diagnostics on all of its circuitry.



Of course, if you feel that the V1 is not working properly, you can always send it in for a check-up.

Cordially,



Pete Kaufman
Sales Department


and them KpatZ...
"The V1 does have some self tests, but LO calibration isn't one of the things it tests, AFAIK.

The 3.85x versions have more tests than older ones, which likely explain the increased occurrence of "E" codes on them. I had a 1.7 circa 2000 that threw an E code due to a memory error after jump starting my car."


and Jim....
"You really can't compare the V1 and the Belscorts in regards to the self-cal stuff, since they operate differently.

The Belscorts calibrate the 1st LO by looking for [normally unwanted] mixer products of the first LO and 2nd LO ("markers"). Since the 2nd LO is crystal referenced, by looking for these markers it "knows" where it is at, and can then calibrate the 1st LO accordingly. Supposably, it does this every so often during normal operation, one person was told every 8 minutes. The only time it throws up the "Self-Cal" message is when it has trouble locating the markers. After a certain number of attempts, if it still doesn't see the markers, it throws a "service required".

The V1 samples the 1st LO directly, and then divides it down to compare it with some sort of known reference, and can adjust the 1st LO accordingly. Though I havent looked at it, I suspect that it is a phase locked loop. I also suspect that if this PLL gets maxed out one way or the other, it will throw an "E". But I don't know this for certain..."

[jdong]

Great info, man!

[mikered30]

I didnt know the older V1s can throw an E.

[kpatz]

I didnt know the older V1s can throw an E.

They can, but it's exeedingly rare. It requires something to be fried such as the memory chip.

[proudNMAmember]

The 3.826 revision was pretty good but some units had some k band automuting problems.