07-20-2015 01:34 PM
I created a program in the LabView development environment with equipment that used the GPIB-USB-HS hardware to communicate between them and the computer. I have done this with other tests and had no problems. However, the problem happens when I create an executable and installer for a lab computer. According to MAX I have been using GPIB-USB-HS"GPIB1" to create my executeable and when I went to the lab computer to install it, that computer registered(again according to MAX) the same piece of hardware as GPIB-USB-HS"GPIB0". After I figured this out I realized I have 2 different USB to GPIB devices connected to the LabView environment" computer. I was creating the executable as a hard-coded GPIB-USB-HS"GPIB1" and when I went to run it on the lab computer it wasn't finding that piece of hardware because it was being reffered to as GPIB-USB-HS"GPIB0". I created 2 sessions on the lab computer with my extra GPIB to USB device to temporarily fix the problem, but is there a way I can hard code what session the GPIB will be used as? I attached a screenshot of my lab computer with max running and showing both GPIB to USB devices.
Thanks for your help!
07-20-2015 02:28 PM
Well first I must state the obvious: Do not hardcode your GPIB addresses.
If you must hardcode then remember that if your target machine only has one GPIB interface then it will always be "GPIB0"
07-20-2015 02:50 PM