I did some Google searching on this issue but I did not discover anything beyond this page:
http://digital.ni.com/public.nsf/allkb/78B4FE652DE1F9C18625682D006CEAA7
Here is the issue I encountered and some questions relating to it. I have a single test stand set up using a single GPIB-ENET 100 box to control the instruments. Two work stations are set up to control this test stand (not at the same time). The issue I encountered yesterday was that after the test stand was accessed by one of the two computers, the GPIB-ENET box would not respond to the second computer. None of the functions (ibfind, ibdev, ibwrt, etc.) from the second computer worked properly and I was unable to do a scan for devices (using MAX) from that computer without an error.
Now according to the link provided, it should be possible for both machines to access the same GPIB-ENET device. The software on neither machine utilizes the iblock and ibunblock functions since they were written with the assumption that the GPIB controller is an internal board on the PC. This should not be an issue, though, since the operators know not to access the same test stand at the same time.
I checked the versions of MAX each system had and found that the machine that can access the ENET device has version 5.0.0f1 and the machine that cannot has version 4.7.1. I am not sure how that translates to what IEEE 488.2 driver version they each have (my first question) but I am sure the machine that has MAX 5.0.0f1 has version 3.0 due to my prior issue I had with this system running DOS software on a Windows 7 machine (the second system does not use DOS software).
What IEEE 488.2 driver versions installs MAX 4.7.1 and/or how can I determine which IEEE 488.2 driver is installed? Also, would the drivers on both machines have to be the same if they are accessing the same ENET device or do they simply need to support accessing ENET devices? Incidentally, I corrected the problem by powering off and powering back on the ENET device but I was hoping that there was a way that I can ensure that this issue will not occur again in the future.
Has anyone else encountered this issue and if so, how were you able to correct it and prevent it from happening again in the future?
