03-31-2006 11:45 AM
04-04-2006 04:36 PM
Thank you for posting to the NI Discussion Forums! Let me first start off and let you know that you have right to be confused – though this message indicates that there could be a GPIB problem, you are indeed probably not experiencing any problems with GPIB. The error number for this problem is defined by both LabVIEW and GPIB so LabVIEW gives both to you.
That being said, this error could be tricky to resolve. First of all we will need to know more about your application – what its doing, what your trying to build it to (i.e. exe or dll), maybe the version of LabVIEW, the OS version, etc… I have encountered this problem when using shared variables in sub-VIs and building the VI into an exe. In this case sometimes reinstalling LabVIEW 8 will resolve the problem, other times removing shared variables from sub-VIs will fix the problem. You might want to start out building a much smaller VI that can reproduce the same problem – start with your main VI and keep stripping items out until you have a really simple VI in which to replicate the problem. You’re welcome to post that VI when done too and I can try to build it over here.
Please let me know if you can provide any additional information on your program, and whether the suggestions provided above fix the problem.
I look forward to hearing back from you –
03-06-2008 02:24 AM
03-07-2008 10:13 AM
04-12-2011 07:34 PM - edited 04-12-2011 07:36 PM
I have the same problem when I want to save my 2D array as jpg file. I get "NI-488: Command requires GPIB Controller to be Controller in Charge" when. I have attached an image of the simplified portion of my vi block diagram. The error is still the same.
Thanks for helping.
04-13-2011 10:01 AM
Please reread the earlier posts. You are NOT getting an NI-488 error. The message says possible reason(s). Note the plural. Your error is LabVIEW: An input parameter is invalid. Check the input to the flatten to pixmap and verify it is truly an 8 bit pixmap.
11-08-2011 04:13 PM
Same error here, when building a relatively simple vi that runs without error from within the development environment.
Any advice? Labview 8.5.1 professional.
10-09-2012 12:13 PM
Necro'ing and old thread but it relates to my problem
Same error as all posters above. Attempting to write a file via the "Write to Spreadsheet File (string).vi"
08-05-2013 08:38 AM
Whenever I get the error you all are describing it is always related to a file or filepath error or the file you are tryng to read is not in the location where it is looking.