|
Re: No Robot Code Driver station
This behavior means that your code is experiencing an Exception somewhere in the initialization. I would recommend connecting with net console to watch the initialization and find the bug. I have seen often that the error exception doesn't tell you the line number in your code but rather in WPILib because they catch the error. If you surround all your initialization code with your own try catch loop and print the Exception it should tell you exactly where the Exception occurred.
(One of my most common mistakes is trying to push data to the SmartDashboard in the robot constructor. For some reason you have to wait to write to SmartDashboard in robotInit, when commands call init, or a period begins.)
|