Open Network Connection error

[billbo911]

I know the exact cause of this error, what I'm needing to know is how to handle it correctly.

See the attached pic for more details.

I get this error when LabVIEW is attempting to connect to a socket on a server that is not up yet. The server is an off board vision processor. In reality, the processor should boot before the cRio does and this situation should not happen, but I want to be able to handle this error if and when it does occur.

Ideally I would like LV to just ignore the error and try again the next time the loop is executed. I can not find a way to do this, but then again, I may have missed the obvious. How do I configure LV to ignore this error?

[tilky]

as long as you wire an error indicator to the error output, labview will keep trying until it has no errors.

you might want to seriously decrease the timeout value, a minute is quite long

[Greg McKaskle]

My suggestion is similar. You decrease the timeout, and then you use the error code to control the downstream operation. Often you'll put the data handling code into a case structure, wire the error to the ? of the case structure, and then you can decide what to do in the error case. Sometimes you will do nothing, other times you will update a display to indicate "the other HW isn't responding; you are trying again; press that button to abort; etc.".

Greg McKaskle

[billbo911]

Originally Posted by Greg McKaskle

My suggestion is similar. You decrease the timeout, and then you use the error code to control the downstream operation. Often you'll put the data handling code into a case structure, wire the error to the ? of the case structure, and then you can decide what to do in the error case. Sometimes you will do nothing, other times you will update a display to indicate "the other HW isn't responding; you are trying again; press that button to abort; etc.".

Greg McKaskle

Thanks for the suggestions. I reduced the timeout to 5 seconds. I can modify that value as needed to match the boot time needed, if needed at all.
I also basically told LV to give no errors. It now waits patiently until the PCDuino is available to respond to connection requests.
Again, this situation "should" never come up, but now it is handled if it does. See the attachment to see how I did it.