National Instruments 488.2 Driver
Alayna Rother
We've just updated our Windows 10 x64 DAQ machines to NI VISA 18.0 and NI 488.2 18.5. The machines were working fine with USB GPIB adapters using v 16 of the above. Now we find that GPIP-USB-B are not recognized by windows ('Unknown device'), while GPIB-USB-HS is working properly in device manage, but show up as generic USB device, and not as GPIB adapter in NI-MAX
I am having the same issue with the GPIB-USB-HS not showing the ability to scan for instruments. This is only true of version 18.5 of NI-488.2 and if I use version 17.6, the issue is not present. I read the knowledge base article, though this focuses on the idea that the incorrect driver was assigned by Windows for the device. In my case, the correct driver was assigned and there is still no option to scan for instruments.
Thank you for this solution. I was having the same problem with my USB GPIB and PCI GPIB busses using version 18.5. Going into services and starting the NI GPIB Enumeration Service, NI LXI Discovery Service, and NI Route Coordinator services as described in the article you provided is what fixed it. At first I was not allowed to start the services because when i clicked "start" a log on error appeared. This was fixed by right clicking the service, properties, log on tab, and changing to "log on as local system account".
I found the problem occurs in driver ver 17.6 and up, after NI added a check for counterfeit hardware. They removed all earlier versions from their site (for your convenience) since they didn't have this counterfeit check. Since so many people report this flagging their GPIB-USB-HS box as counterfeit, even though they bought it directly from NI, it appears to be a software bug. One guy even posted photos of his circuit board showing a custom NI logo-ed chip, so unlikely counterfeit.
Andrea W of NI Tech Support replied to my web complaint and said she would report it to their R&D team. In the meantime, she uploaded ver 17.0 to their ftp site for me. If like me, you may only need the 488.2 drivers (NI-MAX), not a full VISA setup. Internally, NI refers to the setup as "17.0 488.2". So, you will need go thru tech support to get this file.
I did not get it. How do you find the instrument i LV. I have downloaded a LLB file from ILX Lightwave and copied it to the C:\Program files\National instruments\Labview 2011\ instr.lib folder. But I don't understand how I can use it from LV. Can I find it in the pop-up menu in the Font panel or the Block diagram.
In the Find Instruments Drivers window you can click on the drivers and then choose an example or you can open the functions pallet in LabVIEW. You can then navigate to Instrument I/O >> Instr Drivers and VIs for your drivers will be located there.
Unfortunately another problem occur. The LabVIEW computer is placed on the lab and is not connected to the internet of security reasons. When I try to start the NI Instrument Driver Finder a error message is shown asking med to check my internet connection.
You will not be able to run the "Find Instrument Drivers" wizard without an internet connection. When you do run it, before you click okay, you should see your drivers show up in the list of installed drivers. This will me that LabVIEW did find the drivers.
As I said----When trying to interact with the instrument (Lock-in-Amplifier) using Keithley diagnostic tool and configuration, I am able to communicate with my Lock-in-Amplifier.....but not with LabVIEW
Also the solution is important to me because in my lab I have three GPIB cable one each from NI, Keithley and Agilent. So in one of the Labview code i have to connect three GPIB...so I need to know how can these three will be compatible with each other
1). I am able to see the agilent\Keysight GPIB on the NI MAX interface.... both under the devices and interfaces and the miscellaneous visa Resourses.... Also I am able communicate with my instrument using VISA Test panel...........Thanks....
I have attached the screenshot.....Also I want to know since I am able to see the agilent GPIB under miscellaneous VISA resources, so shall I use VISA communication subVI in LabVIEW instead of GPIB subVIs ??
EDIT: could you specify your lock-in-amplifier model and brand? Did you find device drivers for LabVIEW using VISA functions? Or at least you have a manual describing the command protocol? (SCPI commands, something else?)
I am using SR830 Model Lock-in-Amplifier. I have its manual with the list of commands. The LabVIEW VI that I made interacts perfectly with the Lock-in-Amplifier provided I use NI GPIB cable.... But using Agilents GPIB cable it gives GPIB error code 7 (after enabling the tulip in ni passport).....
Hmm, could you explain this further? So you have three GPIB cable (USB-GPIB adapter to be precise) from the above three manufacturers? What is your exact goal? You want to use 3 different PCs to communicate with different GPIB devices (amplifiers, etc)?? As I understood this is your case, yes?
Just in case, I would point out that if you only want to use a single PC to communicate with several GPIB devices, you only need a single GPIB cable! You can connect several GPIB devices to a single PC using a single GPIB cable. If this is the situation, just use the cable from NI, with the NI driver...
EDIT: so if you use the standard GPIB cables, you can see that the sockets enable you to connect a second cable on top of another, thus using 3 GPIB cable (not adapter) plus a single GPIB adapter, you can connect 3 instruments to your single NI-USB-GPIB adapter...
To test that the hardware is working properly, in Measurement & Automation Explorer, expand Devices and Interfaces, and then expand NI-IMAQ Devices, and expand the node that represents the board you want to use.
Verify that the version is compatible with the Image Acquisition Toolbox software. Supported NI-IMAQ driver versions are listed on the following hardware support web page: ( -support/national-instruments.html).
Hello, I would like to have a feed back regarding an issue I am experiencing with the GPIB-USB-HS driver in Windows 10. Attached is the a snap of the VISA and NI-488.2 version I have installed. First time I installed the drivers it actually worked for windows 10, but after a windows update it did not worked any more. I have reinstalled the divers but still is not working. Can I have any feedback on how to proceed next.
I also have the same issue and tried your suggestion, but this didn't work. The HS device just isn't showing in the device manager, yet NIExplorer knows it is there. I actually feel like Windows10 doesn't allow the device to work. Perhaps this is a red herring, but, when I restart the pc, the controller goes into ready state, when w10 starts the device goes into active, then goes off. If I unplug and replug, the device never gets into ready.
I had the problem about a month ago, so updated to 17, but w10 forced another update on me and now I think it stopped working since then. Actually, I also noticed my pc cannot find USB instruments like TEK2024 USB devices.
Thanks for getting back to me on this. So I checked the firewall and restarted. This didn't resolve it. It is a windows 10 driver issue. My is version is 1709 build 16299.125. Windows 10 is being explicit the drivers are unavailable. I also did a repair on my installation, this didn't resolve the issue.
I have two HS devices, neither are working on this pc... but both are seen, just no drivers supported... Both devices work on my office pc, both don't work on this pc (any port). This has the latest wX. It worked on here until the last update! I don't have any other USB devices on here when I'm trying to use the GPIBs.
To be honest it wouldn't surprise me if dell has done somethings in their control layers. So it is either going to be a dell update that resolves it or there is a genuine problem in the NI layer. I don't know enough about either so will work around the problem with serial for now.
I have enclosed a screenshot. My nose is near the grinder, people as asking me why I can't get this working. Dell just issued an update, that hasn't resolved it, so now it's NI turn. 1000 for each device is not cheap...
As a next step, I would like to see if this issue is local to the computer or not. Please attempt to use the device on another PC with a fresh install of NI 488.2 and VISA. I would be surprised if the issue is related to an OS update, it seems to be a driver issue. In the past I have seen this issue be fixed with an OS wipe (re-imaging). Although it is not the most glamorous answer, wiping all possible corruption may be the next step.
My procedure to resolve this was to, uninstall the NI software, and re-install...however I had to do this twice, the first never resolved the issue. The second time I went through my registry and removed all references to National Instruments, IVI, visa etc. After this, it worked. Half a day beats an OS wipe, that would have been days of reinstalling so i wasn't doing that.
The card is old since I would not like to go for newer drivers from the official National instruments site since I have a 16 bit program that needs to access the card. Also the driver CD that came with card is now molded which is not useful anymore.
National Instruments has removed NI-488.2 17.0 and earlier from theNI-488.2 Download Page. If you require an earlier version of the NI-488.2 driver, please reach out to NI Support to request for the specific driver version.
4a15465005