Revision as of 10:48, 25 October 2023

Why

• Create a program testing platform. We want to create programs that we can copy to the competitions robot without modification.

Check Points

Check Point 1

Rename the Controller Hub

• Power up the Control Hub
• Power up your laptop
• connect to the Control Hub network -
  • Its name starts with "FTC". For example something like FTC-WBy6
  • The password is "password"
• Open a web browser: 192.168.43.1:8080
• Go to the "Manage" tab
• Locate the Robot Controller Settings
  • In this case change the Robot Controller Name is OrRAS11-RC
  • Leave the password as is
• Connect your laptop to OrRAS11-RC

Check Point 2

Down loading the Mecanum Demo Program

• Locate the the Drive Mecanum program in GetHub and copy it to your laptop. You will need internet access for this step
  • DriveMecanumEpp.java
• Load the program into your robot

Check point 3

Pair the Driver and the Control Hub

See

• [https://www.youtube.com/watch?v=XOtzRAZ5HyM youtube of Connecting a Driver Hub to a Control Hub

Check Point 4

Connect and Configure the motors

• Configure these motors with the same I2C connections and motor names as the competition robot.
• Change the motor names in the java program to match the configuruation
• Build

Check Point 5

Update the Control Hub

• See Updating Control Hub
• Use the Google Chrome we browser - TBD double check
• You will need to install a program name REV Hardware Client
• Test

Update the Driver Hub

• See Updating Control Hub
• Test

Synchronizing the Platforms

Check Point 6

• It is important that the Competition and Autonomous Platforms are in sync so that you can easily move software you have developed on the Autonomous Platform to run on the Competition Platform. In a similar manner you want improvements made on the Competition Platform to be copied to the Autonomous Platform. Develop a mechanism for doing this. Start by meeting with your conterparts.
• GitHub has mechanisms for supporting this. I suggest mastering it when you find yourself getting into trouble.
• Android Studio integrates GitHub into its development platform. Android Studio can be difficult to master and typically new uses get lost in it. You have to decide whether mastering its complexity is worth its numerous benefits and when is the best to to do that.
• This can be a difficult but important decision. We started with OnBot Java because it is an easier place to state but ultimately it is not industry grade.