-
Notifications
You must be signed in to change notification settings - Fork 2
Troubleshooting
Here are some solutions for known problems
Try installing Gradle (if not already installed), opening a command prompt / terminal in the project root, and running gradle.exe wrapper
(Windows) or gradle wrapper
(Linux)
- Check to make sure you are properly connected with the robot, and it is turned on
- Try deploying again (sometimes a double-deploy is needed)
- Try restarting the robot from driverstation
- Try killing the power to the robot, then turning it on again
- Use Ethernet
Each time we update the WPILib version for the project, all project tools should update to reflect the new version (the version will be displayed on the loading screen of each tool). If this is not happening:
Open up the FRC tools install folder (~/wpilib/<year>/tools
for Linux, C:/Users/Public/wpilib/<year>/tools
for Windows), and delete all files except for:
- ScriptBase.py
- ScriptBase.vbs
- tools.json
- ToolsUpdater.jar
- ToolsUpdater.py
Then, run the following in the project root:
# Linux
./gradlew ./gradlew installAllTools
# Windows
.\gradlew.bat installAllTools
This comes from HERE.
Does your computer name have a dash in it? If so, try renaming it. Several teams have reported issues similar to this.
To get the controller connected:
- Plug it in
- Run
sudo xboxdrv --silent
- Start the simulation
For linux, the sc-controller project works great for mapping a steam controller to an xbox controller. An sc-controller binary is stored in the project at tools/linux/sc-controller
On windows, use the "default controller mode" setting in the steam controller settings.