Once you have the ENET driver installed and the bus address setup to reference the GPIB-ENET, access to it would procede as with any other GPIb controller. That is, all of the networking and TCP calls are 100% transparent to the user.
For example, if I have a PCI-GPIB board installed as GPIB0 and I then add the GPIB-ENET as GPIB1, the only alterations to my code would be to the bus address. That is, if my code looks something like:
ud = ibfind("gpib0")
ibsre (ud, 1)
ibonl (ud, 0)
I would change it to :
ud = ibfind ("gpib1")
ibsre (ud, 1)
ibonl (ud,0)
The driver is able to distinguish that GPIB1 is mapped to the ENET and will make any appropriate TCP calls to drive the ENET's bus.
From LabVIEW, you can use any of the VISA or standard 488 function with the ENET as yo
u would with a standard interface.
As troubleshooting steps, make sure that you can communicate using IBIC (http://www.ni.com/support/gpib/max/ibic.exe), with VISAIC (nivisaic.exe) and using the LabVIEW examples. If IBIC does not work then there is either a configuration problem, a hardware problem, or a problem with your instrument. Make sure that you have all setting properly set and that you are terminating the communication correctly. It would help if you had a second instrument that you know works to test with as well. If IBIC works but VISA does not then you need to look at your VISA installation. If both of the interactive utilities work but LabVIEW does not, then you need to approach this from a general application problem versus a driver or hardware. Again, make sure things like termination and comand structure are properly developed for your instrument. Your best source for troubleshooting this are the IBIC utility and your instrument's manuals.
Ryan Mosley
National
Instruments, Applications Engineer
http://www.ni.com/exchange