LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

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

The complete error message I receive is:

Error 1 occurred at New File in Untitled 2,Possible reason(s):

LabVIEW: An input parameter is invalid.
---
NI-488: Command requires GPIB Controller to be Controller in Charge.

I get this when I am running my program and I try to save my data to a file. Any file operations I try I get this message. I have programs that I previously written with no GPIB devices and the file operations work fine. Now even with subsequent programs if I try and use the file operations, I get this message when the file operations themselves go to execute. I have been all over the boards but cannot find any solution. Any ideas out there? Could it be that I have something wired wrong? The thing that confuses me is that if I open a new blank VI and simply put a New File icon on the block diagram with a file path assigned, I get the error. No GPIB devices are in the VI. But again, if I run a program that I previously have written, with file operations, it works fine.
0 Kudos
Message 1 of 5
(3,614 Views)
Your error has nothing to do with GPIB. Error code 1 when used with LabVIEW means an input parameter is invalid. If you're using GPIB and get error code 1, then the second message would apply. Since the source of the error is New File and that's a LabVIEW function, you have an invalid parameter there. Check that your path, permisssions, etc. are correct.
Message 2 of 5
(3,613 Views)
Dennis-I am not sure of your explanation. I am using GPIB so in that case does the second message apply? I guess I was not looking at the error as two separate messages.
0 Kudos
Message 3 of 5
(3,608 Views)
The source of the error is New File, right? The source of the error should always be looked at when an error message gives a couple of different possible reasons.
Message 4 of 5
(3,605 Views)
Once again, thanks for your help Dennis. I found out what my problem was. I was formatting a string and converting it to a path for my file name. Part of the string I was creating was from a query in a previous sequence. That query was one bit too big and wound up having a carriage return at the end. So my path for my new file had a carriage return in the middle. That was an interesting one to find. Thanks again. --- Troy
0 Kudos
Message 5 of 5
(3,599 Views)