Quote:
Originally Posted by Tom Line
That exact error has caused us to have the symptoms you are seeing. Try to determine why you are getting it. Are you developing on the driver station? Running on a busy network? Not deploying your code permanently?
|
The developing is being done on the same computer as the driver station being used to control, but it's not the classmate-PC from KOP. The network has only the robot and computer connected to it and the problem occurs when the code is run from labview for debugging AND when it is permanently built and deployed.
Could it be that the lag gives it that quick little signal?
I'm also thinking it could be the default camera Vision code. I'll try disabling vision tomorrow and see if the error goes away. If it does, does anyone think it would be worth disabling the vision loop overall, except when I deliberately want to use it (ie. case structure w/ joystick button; it's being used for auto-alignment w/ hoop)?