LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

collect boolean array (real time function block) causes unsuccessful build

Hi there,

 

I've tried the function blocks in real time programming, the collect boolean array.

19837iD090941FB4CF0775

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):

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.

 

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.

function block error.png

 

Without using the function block were the both windows program and the real time successfully built. 

0 Kudos
Message 1 of 5
(2,852 Views)

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.

Richard






0 Kudos
Message 2 of 5
(2,828 Views)

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:

19859i82A1ABB0D05799F1

 

PS: the SSG is our real time (sbRIO).

0 Kudos
Message 3 of 5
(2,818 Views)

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.

Richard






0 Kudos
Message 4 of 5
(2,807 Views)

You're right. Anyway, I've drop the "collect boolean array" and used shift register for instead.

0 Kudos
Message 5 of 5
(2,787 Views)