Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

NI-488: Command requires GPIB Controller to be Controller in Charge

Hi,
I have a power supplier from Kepco. When I tried to run the VI send by the company, I always received the error:
 
Error 1 occurred at Scan From String (arg 1) in KepcoDCPwr Query Voltage Limit.vi->KepcoDCPwr Interactive Example.vi
 
Possible reason(s):
LabVIEW:  An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
=========================
NI-488:  Command requires GPIB Controller to be Controller-In-Charge.
 
I use LABVIEW 8.2   Do you know how to solve this? Thanks
0 Kudos
Message 1 of 6
(11,147 Views)
One reason to get error code 1 from the scan from string is when the input string is empty. The VI you posted is in LabVIEW 5 and I can't open it with 8.5 but try communicating to the instrument in MAX. Send the query that is in the subVI and see if you get a response. You can also open the subVI and probe the string input to the scan from string and see if there is anything there.
Message 2 of 6
(11,123 Views)

Hi,

Error 1 is also described in the GPIB Error Codes and Common Solutions KnowledgeBase.  This document describes common GPIB errors, possible causes, and solutions.  Good luck!

Regards,

Rima

Rima H.
Web Product Manager
0 Kudos
Message 3 of 6
(11,113 Views)
Thank you for the help.
 
Yes, in the SubVI, after the VISA reading, the responding string buffer is empty. That caused the problem. But it happened randomly, sometimes the buffer is not empty.
 
The labview I use is v.8.2, it can open the VI, but I don't know whether it's due to the version.
 
 
0 Kudos
Message 4 of 6
(11,092 Views)
It probably has nothing to do with the version of LabVIEW. It just might require a delay between the VISA Write and the VISA Read. When the VI was originally written, everthing ran a bit slower (computers, etc.) and that could be the reason you are seeing an occasional problem now.
0 Kudos
Message 5 of 6
(11,087 Views)
Yes you are right. I put a delay between the VISA Write and the VISA Read and fix the problem. Thanks.
0 Kudos
Message 6 of 6
(11,056 Views)