Open Network Connection error

[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.