Quote:
Originally Posted by RufflesRidge
What would indicate to the communications process that robot code was running if the DS thread was locked and not calling into the communications process anymore?
|
Actually I was backwards. If user code freezes but the DS loop stays running, those would be the symptoms. The DS loop would flag the comms saying it is running, however when using IterativeRobot, the flags stating which mode the robot is in is are called in the main user code loop. So if the main user thread froze, or got stuck in a blocking call, the DS would still see comms and code, however the mode report calls don't happen and no movements would be responded to since no main loop is running.
__________________
All statements made are my own and not the feelings of any of my affiliated teams.
Teams 1510 and 2898 - Student 2010-2012
Team 4488 - Mentor 2013-2016
Co-developer of
RobotDotNet, a .NET port of the WPILib.