Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error executing Teleop Mode due to currentDrive = null on initial robot code/shuffleboard station startup #23

Open
cttdev opened this issue May 20, 2019 · 0 comments
Assignees
Labels
invalid This doesn't seem right question Further information is requested

Comments

@cttdev
Copy link
Member

cttdev commented May 20, 2019

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.

@cttdev cttdev added invalid This doesn't seem right question Further information is requested labels May 20, 2019
@cttdev 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid This doesn't seem right question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants