LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Multiple error cluster lines

Hallo LabVIEWers,

trying to make a good programming style, I implement error cluster inputs
and outputs on each of my VIs very thoroughly.
Now then, if I use eg the VI Server to call my VIs (call by reference node)
I have two error cluster outputs in my data flow, one from the Call by
reference and one from my own VI.

Now my question: How should I handle these two flows, is there a way to or
them together ? Should I ignore one of them ? Should I keep them seperate ?
Wiring the CallByReference output cluster to the own VI's input doesnt't
work because of cycle dataflow dependancies (of course)! What's a good
LabVIEW style and what are your suggestions ??

Thank you

Oliver
0 Kudos
Message 1 of 3
(2,022 Views)
There is a function in the Time & Dialog pallet on the function pallete called Merge Errors.vi. I think this does what you want.
0 Kudos
Message 2 of 3
(2,022 Views)
Under the Time&Dialog palette

-------------------
Merge Errors

Lets you merge error I/O clusters from different functions. The function
first looks for errors among error in 1, error in 2 and error in 3, then
through error array in. The first error found is reported. If no errors are
found, the function then looks for warnings and returns the first warning
found. If no error warning is found, the function returns no error.

Click the parameters for more information.
--------------------

If you're in LV5 you'll just have to implement a similar function.

Oliver Friedrich wrote in message
news:3a910d74@newsgroups.ni.com...
> Hallo LabVIEWers,
>
> trying to make a good programming style, I implement error cluster inputs
>
and outputs on each of my VIs very thoroughly.
> Now then, if I use eg the VI Server to call my VIs (call by reference
node)
> I have two error cluster outputs in my data flow, one from the Call by
> reference and one from my own VI.
>
> Now my question: How should I handle these two flows, is there a way to or
> them together ? Should I ignore one of them ? Should I keep them seperate
?
> Wiring the CallByReference output cluster to the own VI's input doesnt't
> work because of cycle dataflow dependancies (of course)! What's a good
> LabVIEW style and what are your suggestions ??
>
> Thank you
>
> Oliver
>
>
0 Kudos
Message 3 of 3
(2,022 Views)