Error 1 an input parameter is invalid on cluster wire

[DrAlexShaw]

I have a system with numerous subvi's, however all seems to compile ok and when I run the top level vi it seems to be working fine. However when I press a button to launch a routine that calls numerous sub vis, I get an error:

Labview: An input parameter is invalid. For example, if the input is a path, the path may contain a character not allowed by the OS such as ? or @.

The top level VI "mastercontrol2.vi" was stopped at Wire on the block diagram of "FPGASigGen_GetDataPont.vi".

[OK]

I am then taken to the block diagram of the said VI, and the section of pink cluster wire from the cluster constant is highlighted, in the  section just after it enters the while loop. The top level VI then stops executing.

I have tried rebuilding this part of the code in different ways, but always with the same result. The suggested cause in the error message is clearly a red herring, because I don't do any file access anywhere.

Any help would be greatly appreciated!

Using Labview 2011 11.0

[crossrulz]

The only thing I see in your code that would cause an error code 1 would be the FPGA reference.  Are you sure that reference is valid?

[DrAlexShaw]

Hello, thanks for the reply.

However, if I am pretty certain that the FPGA ref is not the cause. A probe on the wire seems to show a valid refence number, and there is also other error handling and checking during start up that should blow if the reference is not working.

[crossrulz]

Just because you see a reference number in the probe does not mean that the reference is valid.  If a parallel process closes the reference, you will still have that reference number, but the reference will become invalid.  This is the usual case for an error code 1 when dealing with references.

[DrAlexShaw]

ok, the happy news is that this problem has gone away.

The annoying thing is that I don't know why.

I did do some more checking along the lines you suggested - I didn't find anything though, as there is only one place where the controller shuts down the target, and that was down the data stream from where this routine was executing. I also checked that the FPGA component didn't shut itself down by running its interface while testing.

All the same- thank you crossrulz for your suggestions, they were more logical than anything I had tried in the last day or so!

However I did check for and install some updates to the labview software, so maybe this was the difference.