You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Weird issue that occurs when currentDrive is set to null by shuffleboard when you start up shuffle board after a driver station power cycle. When shuffle board was not saved and driverstation was restarted immediately after the fact, currentDrive was not set to null but rather CurrentDrive.Arcade like it is supposed to be. However after shutting down and reopening after a period of ~24 hours the driver station was started up and currentDrive was null again, leading TeleopMode to have a nullPointerExpection. This is easily temporarily solved by setting the drop down menu to ARCADE but it would be nice to have a permanent solution.
The text was updated successfully, but these errors were encountered:
cttdev
changed the title
Error executing Teleop Mode due to currentDrive = null on initial robot code/shuffleboard station startup
Error executing Teleop Mode due to currentDrive = null on initial robot code/shuffleboard station startup
May 20, 2019
Weird issue that occurs when
currentDrive
is set tonull
by shuffleboard when you start up shuffle board after a driver station power cycle. When shuffle board was not saved and driverstation was restarted immediately after the fact,currentDrive
was not set tonull
but ratherCurrentDrive.Arcade
like it is supposed to be. However after shutting down and reopening after a period of ~24 hours the driver station was started up andcurrentDrive
wasnull
again, leadingTeleopMode
to have anullPointerExpection
. This is easily temporarily solved by setting the drop down menu toARCADE
but it would be nice to have a permanent solution.The text was updated successfully, but these errors were encountered: