Because of confusion with the build team, a robot left the factory with a beta version of the sd card image which had the startup scripts running twice: Once in the RunDexRun file (as per the old way of running jobs on startup) and again in the autoexec.jobs file (which is the new way of running jobs on startup). The second time it ran, the commands caused the robot to shake because the job assumes the robot is in open loop mode. Other than removing the confusion with the build team, perhaps we should change the job so it goes into open loop at the start.
Because of confusion with the build team, a robot left the factory with a beta version of the sd card image which had the startup scripts running twice: Once in the RunDexRun file (as per the old way of running jobs on startup) and again in the autoexec.jobs file (which is the new way of running jobs on startup). The second time it ran, the commands caused the robot to shake because the job assumes the robot is in open loop mode. Other than removing the confusion with the build team, perhaps we should change the job so it goes into open loop at the start.