Error ibtsta: (1) set gpib(0), status 0X8100 returned when 0X100 expected

[afj]

To: Steven B.,

Working with our Network Administrator, we found that our device hostname was valid and that the device was successfully able to configure itself using DHCP. However our Network Administrator convinced us that using a Static IP Address was the best way to go. So we now have a valid IP Address associated with our GPIB_ENET/100 device. We cycled power and now when we run the EthernetConfig utility our device comes up with no exclamation mark and no errors. We are able to successfully "ping" the device also. Also we have confirmed that our subnet mask is 255.255.255.0.

There is still one problem left however, that is when we go to run the ibtsta utility to check our software
installation we continue to get several errors of which this is the first:

Error: (1) set gpib(0), status 0X8100 returned when 0X100 expected.  Error ENEB returned.

We run the instgpib utility to re-install the software with the same errors. One thing is that we copied the files from the floppy disk from a PC to a HP-UNIX machine via the network. Will this cause problems? Do we need a floppy disk drive to install the files?


Thank you,

Abel Fernandez
Raytheon EWS
805-879-2594

[Steven B]

Hello Abel,

I think we are getting close. It is a good sign that you are able to ping the device. To get past this error, I have one more idea as to what might possibly be causing this problem. It is described in the following Knowledgebase, however it is described as a problem on Solaris.

http://digital.ni.com/public.nsf/websearch/C1221E8E3B12204B86256CC700713F70?OpenDocument

It does sound like a very similar problem to what you are seeing though, so could you try the solution of renaming the device the way it describes?

Thanks,

Steven B.
Applications Engineering
National Instruments

[afj]

To: Steven B.,

Thank you for your support. We have properly installed our GPIB-ENET/100 device software and hardware. Looking back, I think we had so many problems because we started by trying to communicate with the device without being on the network. It probably would have been fine but we were not using a cross over cable so we could never have communicated. Once we plugged our system to the network the GPIB-ENET/100 device was able to successfully configure itself using DHCP. We chose to use static IP settings because it was reccommended for small networks like ours. After using static settings we were able to ping the device. The final problem where the ibtsta utili
ty gave us the "ENEB" error was due to the fact that I had not configured the gpib settings using the ibconf utility. Once I renamed the default "gpib0" to the hostname I gave the GPIB-ENET/100 device ibtsta ran smoothly. Our application using LabView which is about 5 years old worked seamlessly with the GPIB-ENET/100 device.

Your support is appreciated. We are satisfied customers.


Thank you,

Abel Fernandez
Electrical Engineer II
Raytheon EWS

[Steven B]

Hello Abel,

Great! I'm glad you were able to get that working. Let us know if you have further questions!

Regards,

Steven B.
Applications Engineering
National Instruments