Shared variable dialog window

[Ben_7128]

I want to ignore the dialog window or prevent it from coming up when there is an error in my shared variable.  I am reading data from a PLC on a manufacturing machine.  I am doing this on a separate server system and it isn’t monitored, so the fault does nothing but lock the Vi and prevent it from collecting data until someone happens to look at it.

I have a loop that is waiting for the variable to change and the most common error is when the PLC is turned off and there is no data available, however there are others that come up now and again.

I want to simply return to the loop and keep cycling until the data is there and readable again.

Is there a way to prevent the Shared Variable from halting on error?  Can I turn off the dialog box so that it doesn’t stop the Vi?

[AdnanZ]

I am not sure about the structure of your application but the the Clear Errors VI should help.

[Ben_7128]

The Shared Variable node displays the dialog box and waits for a user input.

I need something inside the node to tell it to ignor the trouble and not ask for user input.

If it did pass outside it would be easy but it doesn't get to the Error string so I can't clear it that way.

Thank you,

[RavensFan]

Adnan's reply is what you want.  Is it not working for you?

You wire the clear errors .vi to the error wire that comes out of the shared variable node.

[Ben_7128]

Well thank you.  I have looked at the Clear Errors several times and discounted it because I thought the dialog box was coming from the node.

Guess this wasn't that difficult after all.

Thank you,

Ben Potts

[RavensFan]

It is coming from LabVIEW's autmatic error handler.  There is also a VI option that can be changed globally for the VI to ignore the error.  But I don't recommend changing that unless you have accounted for all other errors you could possibly get elsewhere in the VI.  Any node that has an error output not wired to something else will have this dialog box pop up if the VI option is set to automatically handle the errors.

Another alternative is to wire the shared variable error to a tunnel on the loop, but don't do anything with it afterwards.