Quote:
Originally Posted by Tom Line
I know that in labview, if the board is not connected and you have error reporting turned on the first message you get on your user diagnostics screen is one reporting that there is an error or the board is not plugged in.
Since I believe that information is getting packaged up and sent from the robot, I'd wager you can unpackage it on the robot to check it against a string etc.
This is all in labview, however, and I'm not sure what language you're using. I haven't dug deeply into the pre-packaged error information, though I know you can see it in one of the clusters when running the code from your developement computer as well.
|
My first line says Windriver C/C++ so it is not Labview.
The error message is local to the driver station laptop - it is not coming from the robot (as Alan also points out).
Thanks