Question for guys using IR scopes/scanners

popper43

Well-known member
How much of the 'stuff' in your menu do you really use? How many have deleted bad pixels, etc. I wrote a vendor today with some recommendations that manufacturers make. Basically, make an app ( and a computer app) to make menu setup which are then downloaded to the sight. My basis - there are only a few VOx array makers. Lots of housing/lens/display makers. Basically saying it's the SW that will make or break a product. I get tired of looking through a heavy rifle scope to make changes - luckily that's not often. Your suggestions and opinions?
Edit: some reasons for your opinions.
Mil/electricians/security/electronic and now doctors use IR scanners. Most of the software is canned, even menu methodology. NUC is even canned but the metal flapper (1-2$ per) operation. WIFI/Bluetooth/charging/etc. Loose zero, probably SW. Loose power, same. Buttons don't work, same. I worked on a medical product, Co needed to add 64K memory for an upgrade. I looked at their code and re-wrote, using 32K of original memory and speeded up operation. I'm no genius and don't intend to make IR scopes, just want comments to make them better and easier to use.
Edit again: Got the old ATN scanner out to look at wife's feet (neuropathy). Then recharged it and turned off. Sitting at computer and hear clicking! NUCing when OFF. Silly SW.
 
Last edited:
Back
Top