Error in/ Error out?

[cdizzle]

In LabView, what do the error in/error out segments do?

[MAldridge]

they do exactly what the name implies: they carry errors.

In the event that your program throws an error, you can have other functions fail and exit on error so that they don't try operating with invalid inputs. This is especially important for files. Imagine that I open a file that doesn't exist, the system will catch this and generate an error, but the write/read operations don't know about this error, to tell them about it, you carry the error cluster to the read/write vi's that you would use, and then your file access code could tell that it had no file, and it could then take the appropriate actions or exit.

Its also useful if you want to auto reconnect on error. I set up my team's camera to continuously try to establish a connection, but if you want to do this beware, the WPILib is bugged and the error cluster is not carried internally in one of the read VI's.

[Greg McKaskle]

Not that I'm doubting you, but where is it bugged? The exterminators are in the house.

Greg McKaskle

[MAldridge]

I think it is in one of the read VI's, the error cluster isn't carried to any of the internal property set functions, so rather than seeing that the reference is invalid, they fail and send an error as a dialog box, which kind of defeated the purpose of having the error cluster wired into it.

If you want I can dig out that code and find out exactly what VI it was that we modified.

[Greg McKaskle]

If you know what type of error or what type of I/O, that would be helpful.

Greg McKaskle

[cdizzle]

If you know what type of error or what type of I/O, that would be helpful.

Greg McKaskle

Well, I was just wondering about them in general, because I've seen them used in a bunch of example programs and tutorials, and thank you!