yeah, if the camera code hasn't finished we found the same issuse of timeouts and other bad things happening to the robot (took a whole 1.5 hours of our testing time to figure out it was the camera
). The problem seems to be WPILib's internal handling of errors and their lack of a limiter on number of errors per second. It looks like the I/O gets overwhelmed and code slows down
__________________
"To have no errors would be life without meaning. No strugle, no joy"
"A network is only as strong as it's weakest linksys"