NVD question from a newbie

Status
Not open for further replies.
Joined
Dec 11, 2007
Messages
127
Location
Central CT
You've got to check the PLC for D-Sub before you plug in the I/O. Hours should be rated in MTBF, but if not ask an LEO if he has a GPS.

Are all these TLAs really helping? I don't really mean to be an *******, but I had to go to Google to figure out what you were talking about and whether I knew anything about it (I don't).
 
I plan on buying some used gen 3 pvs-7 nvd's. What should I look out for? I'm told that the current usage has only been very low hours, guessed at 20 hours or so.

how would you rate the newcon brand? do these need to be turned on monthly to keep from damaging the ITT or is this a myth? what would you consider to be a good price?

I'm a newbie here so I apologize in advance if a NVD question doesn't belong here--I didn't see any applicable subject areas. Thanks in advance for the help. And, hello to all.
 
Night Vision Goggles

Not sure they will keep this topic active because it is not firearm related. But you should look for clean glass (Scratches, etc). Look through them in a dark room and make sure the IR illuminator works, and that there are minimal dark spots. Even brand new ones will have very fine dark spots, lines, etc. Make sure the eye pieces adjust smoothly left and right, and will stay in place. Make sure you can use AA batteries, IIRC all PVS-7 models can. And if you can, make sure it comes with either the head harness or helmet mount.

As far as brand, I don't know, I was only using what our supply had, PVS-7A through D models. The D models were the nicest and clearest model I used. Blackouted driving on a moonless night on the back roads of Fort Dix was not a problem with any of them, Just that the D's were nice and clear/crisp.

Be ready to drop a nice chunk of change on a decent set.

Some good info here: http://www.militaryinfrared.com/AN_PVS_&_Night_Vision_Goggles.html
 
Incidentally

If anyone is confused by the appearance of a REPLY post above (before) the actual original post, please be advised that the server clock was adjusted to be correct (it's been off since the recent outage).

Jack Fred is the OP.

Everything else is a reply.

Sorry for the inconvenience.
 
Dis must be de place.

I'm with you, OP.

In general, I hate acronyms.

I sometimes keep a copy of google running and have to paste the acronyms into the search window. About 60% of the time (a guess), the meaning of the acronym comes up in the hits, without having to go to the actual site to ascertain the meaning.

I'm sorry to say that the military folk are very "into" acronyms and frankly, I can't be bothered to decipher their intent when they have two or three arcane milspeak acronyms per sentence.

I'm sure their posts have worthy content, but much of the time I figure I'll just have to wait four or five years for their argot to enter the rest of the language.

However, the really worst examples of acronyms are in the information technology area. I found one once on the Microsoft site which was something like twelve letters. I finally got a rush of brains to the head and realized it was really a combination of four other acronyms.

I screen-captured it, and printed it out with the famous legend from Dante's Inferno under it: "Abandon all hope, ye who enter here."

I posted the printout on the wall right by my office entrance.

ACP I can go along with... but twelve letters?

Jeez!

(And thanks, Arfin Greebly... that was confozzling.)
 
Last edited:
If anyone is confused by the appearance of a REPLY post above (before) the actual original post, please be advised that the server clock was adjusted to be correct (it's been off since the recent outage).

BLAM! Take that, audit log timestamps! ;)
I've really grown to love NTP (network time protocol). Never again will I have 15 computers, all running on different times.
 
Status
Not open for further replies.
Back
Top