06-17-2010 02:22 AM
I've picked up some remnants of a driver for this device and I'm trying to ressurect it for a new project.
Basic comms between the host and the GPIB-ENET device are working OK, I can scan the GPIB bus for instruments and pick up the address of the connected analyser sucessfully.
But, if I try and write commands to the instrument I get a GPIB error.
Communication works fine using the windows based NI explorer tool so I captured the Ethernet traffic and found several message types that I don't recognise. It also appears to be sending messages on port 5015 as well as the main port 5000.
SO, my question: Is there a document covering the interface with this device at a low-level TCP message level? Or, as I suspect, is this stuff secret and I'm expected to buy some expensive software from NI?
Solved! Go to Solution.
06-28-2010 02:43 AM - edited 06-28-2010 02:45 AM
SOLVED.
After connecting to the GPIB-ENET100 using ibfind and setting various options at board level it is essential to drop and reconnect the socket before attempting to connect and communicate at device level.
My version of ibfind opens a socket and my version of ibonl closes the socket when called to set a board/device offline.
The driver now works perfectly.