Quote:
Originally Posted by Adam Freeman
The second time the issue showed itself slightly longer into auton (maybe 6-7s in), it almost seemed to be some sort of interaction between our CheezyVision timing and the field....since both times it seemed to occur right when we selected the HOT goal. We were going to stop using it, but the FTAs wanted us to keep everything exactly the same.
|
I would be very surprised if CheesyVision was responsible. There are only ~30 payload bytes (plus TCP overhead) being transmitted to the cRIO per second on one of the open ports listed in the manual. That is peanuts compared to the live video streams and Network Tables data that teams have used successfully for years. Besides which, we have evidence that this bug occurred prior to CheesyVision ever being used. I am confident that this problem is unrelated and will be fixed before Championships.
(But just in case, we are going to make our autonomous routines robust to the problem...)