Recent posts

thank you very much. I will do this possibly next week. currently drowned in work that mostly been put off for later. my own fault.   :-\
My instructions do not use Huntron Workstation at all to gather this info, the instructions I included are for Windows "Device Manager", a built in Microsoft utility included in Windows versions since Windows 95's time, that's still used today.

All the Windows versions of Workstation, that I understand, require the basic device drivers for the any Huntron peripherals to function, this likely wasn't true under DOS but we're talking about modern Windows software for the past 30-ish years.

Workstation does do not interface directly with the Huntron hardware without the proper Windows drivers installed for each piece of equipment i.e. the Prober drive system to move the prober carriage uses a serial port internally, but newer probers put a RS232 Serial to USB adapter inside the Prober frame to create a USB port a driver is needed there, the prober camera(s) need drivers (or PCB board drivers for VERY old cameras that used a PCI/ISA board) to work, and the tracker/curve tracer driver is required for Workstation to utilize Tracker unit.  Whichever prober setup you have you will need at least several drivers installed for everything to work in concert before running Workstation.  Though all the currently supported drivers are included in the workstation set up files but are not part of Workstation application itself.

You must have all hardware powered on and USB connections properly inserted into your running computer. USB peripherals that have no power do not show up anywhere on the computer as they are considered dead and inactive. So in order to do any of this you will have to plug in your prober and actually turn it and be aware that it could move or otherwise start up so make sure your area is clear and free of obstruction. But you have to have both the prober powered on as well as the Prober's USB interface plugged in to the computer as, even for serial only probers, the camera is on the USB string internally, which is what we want to find.

The quickest way to launch "Device Manager" for any modern Windows version, this should work on Windows XP, Vista, 7, 8, 8.1, 10, 11 is to press down the "Windows Key" on your keyboard (the key to the left of the spacebar with a Windows logo printed on it) and while holding down the "Windows Key", press the r key on the keyboard.  Then a small box/window titled "run" will appear. Lift all fingers up from the keyboard (no keys being pressed) and type into the RUN window: devmgmt.msc  and then click the "OK" button in the run window to run the command.  The Device Manager Program should now start up.  You'll see a bunch of device listings and categories on an expandable tree.

Find the UNKNOWN DEVICES area and locate the webcam (there may be several unknown devices entries here).  Go through each one by right-clicking on each entry to bring up the alternate menu and left-click on "properties" in that menu that just popped up, then click on the "Details" Tab in the new window, and scroll down the drop-down list to "Hardware IDs" you should find this information.  Similar to the picture I posted in my second message on this thread.  To get out of all this stuff just hit cancel or the tiny red "X" on each of the Device Manager window(s) that appeared and the program will close.

You may not be able to copy the text out using your mouse cursor so you may have to write it by hand on a piece of paper or something. Go through all your "unknown device" entries and just get the "Hardware ID" strings for each of them. You shouldn't have that many in your system. I can tell what's what because I do this for a living so just post all you strings, I can figure out which one is the webcam.

Go ahead and post the strings you find but your USB camera is going to be prefaced with the string "USB" in the Hardware ID (just like mine in my screenshot).  But other USB components may be plugged into your system that don't have an appropriate driver so just go ahead and post what you have and I'll tell you if any of them are a working camera that this driver can use or if I can find a similar driver for you.

Once a driver is found all you have to do is go back to device manager, Play the same unknown device entry that that string belongs to, and right click instead of going to properties on the menu go to "update driver" then follow the wizard prompts to select the folder where the driver is in your folder system that you download and unzipped then it will discover the rest by auto-install.
currently I am running workstation 3.5.4. and the USB Access Prober is not recognized by my version of the software. Is there another way than through the workstation to get the USB hardware ID string?
I don't have all the softwares at the moment to run the Access Prober. but I been looking for and collecting information and any software I come across for when eventually I have the budget to purchase the workstation software 4.XXX in order to run the Access Prober with my Protrack KJ4 hopefully.
thank you for posting and sharing.

Please post your USB Hardware ID string (as shown the thread above) and I'll quickly take a look for you to see what I can find.
Quote from: Al1234 on July 10, 2024, 10:01:54 PMthank you, I have that camera But no switchhhh :'(  :'(  :'(  :'(  :'(  :-\
Did you try the driver? It may work.
thank you, I have that camera But no switchhhh :'(  :'(  :'(  :'(  :'(  :-\
Thank you for providing that additional information and bringing up an important point. It hadn't occurred to me that there could be two or more cameras that look nearly the same so as to be confusing. Before anyone exerts too much energy into this here are the hardware IDs supported by the x64 driver. This should take somebody 20 seconds to look up in device manager. Often time a device may have two or more identifiers in order to do driver matching.

This particular driver matches the major number and doesn't pay attention to revisions. As you'll see in my screenshot attached to the bottom of this post. My camera first presents its ID with revision then presents an ID without it for the driver to match on. You may see something similar and if so you should still attempt to use this driver if one of these complete strings matches a portion of your Hardware ID.

The Hardware ID of the camera I'm using is:

The camera chip is a SN9C201

The 64-Bit driver supports the following additional cameras:


More cameras with an audio Mic feature are also supported but since those weren't used on these probers, I omitted them in this listing.

In Device Manager, if you right-click on the unknown device for this camera, go select Properties, Details Tab, and scroll down the drop-down list to Hardware IDs you should find this information.

In regards to the lens being very loose I would agree that it's loose but I have not yet found it the level where my prober has lost focus to indicate that the lens is moving slowly and might fall out. But it is a concern that the operator needs to pay attention to because as I mentioned you have to adjust the lens manually to achieve focus and you'll find that it is very very light with almost no resistance. Which obviously means it could keep turning under the vibration and movement of your prober during operation.

Thanks for the post, Josh.
There were production models of Access and Access 2 Probers that shipped with these cameras about 9-12 years ago. The cameras were primarily helpful when setting Teach Height. As Windows versions updated the driver support for the cameras did not keep up. We finally gave up on trying to support them and eventually removed them from the Access Probers. If I recall correctly there were at least two different cameras used. You could tell the difference by the little slider switch on the back. Cameras without the switch may not work with the driver Josh posted.
The lens on these cameras were a bit loose from the supplier and could fall out of focus as the Prober moved. We originally shipped them with a bit of teflon tape on the threads to help secure the lens.
Hi All,
All this information is from my own research as a private individual. Nothing in this message is officially supported or endorsed by Huntron.  This driver file and instructions are "use at your own risk", but they have worked perfectly well for me and I'm providing them in good faith to the community for as long as possible. I can't promise how long my link will be up, but I will endeavor to keep it up and if for some reason it's not please try messaging me to get a copy of the file.

Some History: Some of the USB Access Probers were given the option of being fitted with a small auxiliary observation camera.


This was actually a very popular generic webcam chipset and the last driver to officially be released for it was for Windows Vista X64 in 2007.  However, this driver was signed and so the signature is intact and valid in Windows 11 and it works just fine in my Windows 11 installation which is what I'm using my prober on now.

Please note that Windows 11 is not an officially supported OS by Huntron at the time of this writing for Huntron Workstation, but so far it works fine for my needs.  This driver should work just fine on Windows 10 x64 as well. I'm pretty sure this zip file has both x64 and x86-32 Bit drivers in it but I didn't test for 32-Bit drivers specifically. But the driver directory tree looks like it's there so most likely if you're running an older version of Windows that's 32-Bit this driver should still help you. But I wouldn't try to install it on XP, there's older driver files for that but if you have Vista or higher this is for you.

Below is the link & password to my OneDrive share for a zip file, containing this driver.

Password to Download is: Huntron$Prober&WebcamDriver2024!Ap_jIW4gm2Wa5TrlDMRIYixWwo4B?e=ntgaTP

There is no setup file for this device. It is designed to be consumed directly through Windows device manager. Please expand the zip file into your downloads or otherwise known user directory location. Start device manager and look in unknown devices for the WebCam's entry. Right click and select "update drivers".  Once the update drivers dialogue appears you want to say "browse my computer for drivers", after that you want to hit the "browse" button under the "search for drivers in this location" text field.

You need to go to the location you unzipped this driver file at and only open the topmost folder name. Windows will search the entire driver folder and find the driver automatically and because it's signed already it shouldn't prompt you for any security overrides it should just install and work. I've not seen any control panel or configuration application for this WebCam it just automatically works "as-is" with automatic exposure and its lighting system automatically turning on, on its own.

I advise you to reboot your PC after the driver install just to make sure everything went to plan. You should be able to see the WebCam listed in the available streams in Workstation's image pane, live camera tab, now under the "select" button.  The drop-down list should not show an additional camera source!

From my discussions with Huntron technical support, this camera option was more to demonstrate and watch the prober more than it was to aid you in alignment or any other task. It does help a little bit in alignment but certainly only in one dimension and so most of the time you would want to use this as a live video feed watching the prober do its job.  I was told that this option was discontinued a long time ago and that there is no old stock of this camera, if you were interested in this feature today. And that since it wasn't particularly critical it was a seldom requested option.

But I'm someone where I want all my features fully working whether they're vestigial or not, so at least this gets the camera working should you ever need it. It also provides some additional amount of lighting in the other direction which might be useful as well. The camera has a very delicate thread on the lens that allows for manual focus. You'll need to twist the lens to do the focusing as there is no autofocus mechanism. Simply use the live view of the camera using either the windows camera application or any other live WebCam application to stare at the surface you want and gently adjust the focus ring.

If anyone else is also setting up under Windows 11 and runs across a few little issues feel free to post onto this and I can put any of the additional tips I found setting up the prober if anyone is interested. I hesitate to just post them here because again Windows 11 is not an officially supported platform by Huntron and I'd hate for them to start getting people calling in using an unsupported operating system and demanding support.

To those of you with this camera option, best of luck and I'm sure it'll feel great having the camera back online again for whatever you might need it for.
Obsolete Software / Re: WS 3.5.4 works on window 1...
Last post by admin - June 27, 2024, 07:03:13 AM
3.5.4 will install and open in Win10 but you will not be able to connect to hardware.