Why Can I Communicate with My GPIB Instrument in MAX, but Not in LabVIEW?

Updated Dec 15, 2017

Reported In




  • LabVIEW Full

Issue Details

I have a GPIB-USB instrument that I can use and communicate with in NI MAX, but I cannot use instrument in LabVIEW. How do I fix this? 


LabVIEW expects your GPIB board to have the default interface name of GPIB0 and the default primary address of 0 (PAD0). If your board has a different interface name or primary address, then you have to specify this in LabVIEW. One solution is to make sure that your GPIB board uses the default interface name and primary address (GPIB0 and PAD0, respectively), which you can modify in MAX (you may need to reboot your system for these changes to be seen in LabVIEW); however, if you have multiple GPIB boards in your system, then you may not be able to do that. To modify the configuration settings in MAX, select your GPIB interface under the Devices and Interfaces folder, right-click on the interface and select Properties.

Another solution is to specify the GPIB board information explicitly as an input to the GPIB functions in LabVIEW. More information on setting the GPIB board address for the GPIB VIs can be found in the Online Help for the GPIB VIs. (See also the related KnowledgeBase entry on specifying the GPIB board information in LabVIEW, linked below.)

Additional Information

MAX does not have this problem, because it searches for GPIB hardware at all interface names and primary addresses dynamically. Another point to remember is that MAX is able to communicate with your instrument, because you tell it which board to use to communicate with your instrument. LabVIEW needs that same input from you to be able to do the same thing.

Also if you have used an Agilent device in the past, make sure that the Tulip settings are correct in NI MAX. 


Not Helpful