-
Notifications
You must be signed in to change notification settings - Fork 3
A Complete Guide for Hardware Configuration
sbottingota edited this page Sep 8, 2024
·
4 revisions
This guide was made because the FTC official documentation is a confusing mess.
You should follow the steps in this guide in the order they are written.
- This link is mostly sufficient for a elementary understanding of the hardware.
- However, it does not mention the Driver Hub, which is a replacement for the Driver Station smartphone that comes with all the software installed.
- This team does not use any smartphones, so ignore any documentation related to phones.
- Robot Controller - Control Hub
- Driver Station - Driver Hub The Robot Controller and Driver Station can also be a smartphone, hence the different naming, but we are not using smartphones.
- The Control Hub takes 18 seconds to turn on, where it will have a constant blue light.
- If you have a Expansion Hub connected to your Hub, it will flash blue occasionally. This is normal.
- Download the REV Hardware Client
- Turn on the Control Hub
- Open the REV Hardware Client, and press Update on anything you see (except if it's the Robot Controller app and your repository is forked from the FtcRobotController repository (it should be, but isn't in 2024-2025), in which case follow this guide to update.)
- Find a USB-A to USB-C cable (the ones we're using in 2024 to 2025 should be orange, but if you can't find this someone's phone charger is likely to be identical)
- Charge the Driver Hub by connecting the USB-C end into the Driver Hub and the USB-A end into your computer or a charger
- Turn the Driver Hub on with the power button
- Swipe from the very top of the screen to down, and hold down the WiFi icon.
- Connect to school WiFi
- Go to Software Manager and press Update All
- Use the link
- Ignore the content about smartphones.
- Ask your senior for the WiFi password.
- If you cannot connect to the Control Hub at all and none of the passwords work, reset the Control Hub and use the default password. Use this link to reset.
Be not afraid of wiring - it seems like the hardest part of the process, but is one of the easiest and can be done in under half an hour.
The guide for motors is entirely wrong.
- No adapter is necessary for FTC REV HD and Core motors. (which we are using in the 2024 to 2025 season, and will use for the foreseeable future)
- Simply plug a 4 pin JST cable and a JST VH cable into the motor and then connect them into the motor ports.
Connect the two Hubs before you change the address of one of the Hubs!
- The process is the same for two Expansion Hubs or one Control and one Expansion hub.
Here is the link for this process on the FTC docs; however, read the above first
Make sure to standardize the naming of your hardware devices, record the names somewhere, and then refer to them when writing code.
- Connect the gamepad to driver station with the cable.
- Press buttons displayed on screen (Options + Cross for first gamepad) (Options + Circle for second gamepad) (Follow instructions on the Driver Hub)
- The Driver Hub displays if the gamepads are connected.
- Find a USB-A to USB-C cable (the ones we're using in 2024 to 2025 should be orange)
- Connect the USB-C end into the Control Hub, and the USB-A end into your computer. (Use an adapter if necessary)
- If done correctly, Android Studio should display "REV Control Hub v1.0" next to the green Run button.
- Press green Run button
- Look at the progress bar at the bottom of the screen - it's done when the "Launching on devices" bar disappears, NOT when it says "BUILD SUCCESSFUL".
- Turn on the Driver Station.
- Open the Robot Controller App.
- Make sure the correct config file is selected.
- Select the TeleOp or Autonomous OpMode you want to run.
- Press the INIT button, and then the Play button.
This link contains links to ALL of the hardware configuration guides in the FTC documentation.
| Shortcuts: | 🧑💻 Code |
🏠 Wiki Home |
🧾 FTCLib Docs |
☑️ Project |
|---|