[Maxzillian]

Our team encountered no robot control twice this weekend. During both matches the autonomous worked, but once the robot switched to teleop there was no control at all. The team was told both times that the field showed the robot was communicating and the driver's station showed no loss of comm.

I quizzed an alumni who was volunteering for a little more information and he stated that they found that our driver's station was showing no signals from the joysticks. However, after discussing this with our driver, he had diagnosed the joysticks while the match was running and found that the driver's station was seeing them correctly. Keep in mind, the field and the driver's station showed no errors what-so-ever.

After this match we took the robot back to the pits WITHOUT TURNING IT OFF, and tethered it to the driver's station. The robot continued to not respond to any teleop control, but showed that it was communicating and the cRIO was flashing the User1 indicator, which generally indicates that teleop is active. We rebooted the program and it worked fine after that point.

The frustrating bit is not once could we duplicate this while tethered and it never happened while testing the robot for two weeks during the build season. So far it has only happened when connected to the game field. Unfortunately, one time had to occur during a quarter final match. :\

It has been very disappointing and I hope something is done to address it soon as we haven't been able to determine any obvious cause.


Edit: I should point out that our robot is controlled using Jaguars only. Four Jaguars run off PWM signal to control the 4 drive motors (mecanum). Another 4 are operated off CAN to control the tube mechanism. None of the Jaguars work at all when this occurs.