07-26-2010 04:26 AM - edited 07-26-2010 04:33 AM
Hi there,
I've tried the function blocks in real time programming, the collect boolean array.
It was perfect for cRIO to build and to deploy. But when I build the windows program, which (automatically) includes the cRIO.vlib, then comes out the error. It said:
Possible reason(s):
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.
Without using the function block were the both windows program and the real time successfully built.
07-26-2010 08:04 AM
The errors you have posted are indicative of a file path problem, either from using non-explicit paths (which Development mode understands but Windows EXE does not), or, a path could be too long or buried too deep in subfolders causing the path to be too long. Investigate this before placing blame on the boolean array block.
07-26-2010 08:26 AM - edited 07-26-2010 08:28 AM
Hi,
the reason I blamed the collect boolean array function block is that if I delete the function block, the whole thing works!
And also it works well on the real-time without error.
Do I need to specify any path before I use the function block?
My project likes like this:
PS: the SSG is our real time (sbRIO).
07-26-2010 09:10 AM
Your project organization looks great, but regarding filename size, what matters is where the files are on your computer - if you have nested them so deep that Windows hit the limit path size.
I have never used that boolean block thing, but when using certain things on Real-Time platforms, you have to be careful to include files in the build specification.
07-27-2010 02:36 AM
You're right. Anyway, I've drop the "collect boolean array" and used shift register for instead.