LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Using scripting to extract data from the ErrorRing Xnode

Solved!
Go to solution

Hello all,

 

I am currently in the process of making an application using a few ErrorRing to generate custom errors. I would like to be able to generate a table of all the ErrorRings used in my project, along with their error codes and descriptions, in a way that does not involve copying and pasting stuff manualy.

 

I have not managed to find a way to recover the error data of the ErrorRing Xnode using LabVIEW scripting. Does anybody know a way, or is the ErrorRing data forever hidden in some kind of private space ?

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

There is a way to get this information but it requires the use of an internal property for Xnodes. No publicly facing way to do this that I could find unfortunately.

Matt J | National Instruments | CLA
0 Kudos
Message 2 of 5
(2,897 Views)
Solution
Accepted by topic author Rfoxtrot

The only thing I can think of, is for each XNode, copy it to an empty scratch block diagram, create an indicator for it, then get the value of the indicator (then clear the BD and go to the next XNode).  Note that XNodes seem to have no properties nor methods, but an XNode reference can be cast to a Node class, and from there you can get to the terminals.

"If you weren't supposed to push it, it wouldn't be a button."
0 Kudos
Message 3 of 5
(2,893 Views)

Thanks ! That's a neat trick that i was missing. It does not seems possible to get the exact format string this way but this will be more than enough for my application.

 

Implementation attached.

 

 

0 Kudos
Message 4 of 5
(2,876 Views)
Solution
Accepted by topic author Rfoxtrot

I know this was already solved a long time ago, but in the past year I've learned a lot.

The attached VI gives a nice way to get the format string from an Error Ring.

"If you weren't supposed to push it, it wouldn't be a button."
0 Kudos
Message 5 of 5
(2,578 Views)