GPIB Write and GPIB Read keeps returning error 0

[Elsa Fung]

Hi!
I have an IOTech IEEE PCI488 card (suppose to be compatible with LabVIEW), LabVIEW 8.0, and NI488.2 installed.

The problem I have is that GPIB Write and GPIB Read keeps returning an error (code 0: problem connecting to driver) even though everything seems to be ok (the IEEE device receives whatever I sent, and GPIB Read is able to retrieve information from the device).  However, when I turn off the IEEE device connected and send a write command through GPIB Write in LabVIEW, GPIB Write still returns error code 0 (problem connecting to driver) where it should have returned code 2: no listener (same thing when I use GPIB Read).

I repaired the NI488.2 component with the NI CD, and tried to see if error 2 will come up.  I turned off the device and send a command via GPIB Write.  This time, GPIB Write returns error 2 (no listener).  I tried sending a command when the device is turned off a few more times, and GPIB Write still returns the correct error (code 2: no listener).  After confirming GPIB Write returns the correct error, I turned on the device and send a command to it, the device received the command, but still returns error 0 (problem connecting to driver or device).  After getting error 0, I turned off the device again, and send a command to the device, this time, GPIB Write returns error 0 instead of 2. 

I repaired the NI488.2 component again.  The same thing happened.  It seems like after I receive error 0 (even though everything looks good), GPIB Write and GPIB Read no longer returns the proper error!

I emailed IOTech about this problem already (they're pretty bad about responding though...), but want to see if anyone knows/have similar problem here...

Thank you,
See-Ming Fung

[Dennis_Knutson]

My guess would be that the IOTech board really isn't 100% compatible with the version of the NI GPIB driver that you are using. I have never seen that error but then I've only used NI and Agilent GPIB boards and always use VISA. The NI driver may be getting something unexpected back from the IOTech board and it will report that error before any other error (like the no listener you expect). IOTech should be able to tell you which version of NI-GPIB they tested their board with and then you can install that version. Doesn't IOTech ship their own driver? You can try using that with the Call Library Function Node. They also have something called Driver488/NI. Is this a driver you have installed? It would appear to me that you need this.

[Elsa Fung]

That makes sense... but then for some reason, my other computer doesn't have this problem (it also has an IOTech card).. this thing's driving me crazy -__-

[Elsa Fung]

IOTech responded and said that they're not sure what costed it, and they can't do anything about it at this time other than forwarding the problem to the Engineering department.

I managed to get rid of the error by doing the following:
1) Repair NI488.2
2) Uncheck the "Enable Block Mode" box in IEEE Configuration

After doing so, my system no longer generates the mysterious error 0 after every GPIB Write/Read.  I recheck the "Enable Block Mode" box and tried GPIB Write/Read again, error 0 no longer comes up.

So I guess I'm good to go.  Hope this information will help those IOTech users out there.

See-Ming

[VSthoratec]

HI there,

I am having a similar issue happening on the serial side. I keeping getting the "0, No error" when I try to measure current on BK9123.

I have repaired Labviiew, MAX, DAQmx.

Can someone advise on how to do this as suggested by the previous person on the thread?

 Uncheck the "Enable Block Mode" box in IEEE Configuratio

Thanks and regards,

Vani