10-12-2006 06:17 AM
10-12-2006 09:26 AM
The logical name should only be needed if you were wanting to develop for IVI interchangeability or to include configuration settings from the driver session in your program. Trying the TCPIP resource name directly was a good idea. You can try the same thing with a VISA Open VI in LabVIEW to remove the driver layer from the equation. If this does not work, run NI-Spy while doing this to capture what is going on over the communication bus. One other thing is that even though you can ping it, just make sure that the ENET port is selected as the interface port on the instrument.
So the driver installed VIs into the LabVIEW instrument drivers menu palette? Do you know if the driver is IVI-COM or IVI-C?
10-16-2006 09:54 PM
03-09-2013 04:55 PM