When testing our code, sometimes when we deploy, then the robot code light on Driverstation stays red. We then take out the change that we made, and when we redeploy, then the error that was showing what was wrong for the previous code shows up in the Driverstation. I don’t know if this is a bug or not, but it would be nice to know what the error is when our robot code is showing red on the Driverstation instead of fixing it and then it shows us what the error was. Has anyone else ran into this problem?
PS: We program in java, but this might be a multi-platform thing.
No, but you can get a more reliable log over ssh
tail -f /home/lvuser/FRC_UserProgram.log
Try it, and does the same problem occur?
This is a known bug in the driver station, that has been fixed for the 2017 season. As a temporary workaround, import the
package, and at the the very beginning of RobotInit, add a call to
That will force the robot to be seen as connected, and it will print the error messages. However, this will not be needed in 2017.