After receiving the Control Hub it is advised to unbox the device, power the Control Hub on, and start the configuration process. Below are the required materials to run through the initial bring up of the Control Hub and links to the different steps of the process.

Required Materials

• Control Hub (REV-31-1595)

• 12v Slim Battery (REV-31-1302)

• Driver Hub (REV-31-1596)

• Gamepad (REV-31-2983, REV-39-1865, or approved FTC gamepad)

• USB A to USB C (included with Control Hub)

• Windows PC running the REV Hardware Client

Optional Additional Materials needed to Connect an Expansion Hub:

• Expansion Hub (REV-31-1153)

• XT30 Extension Cable (REV-31-1392, included with Expansion Hub)

• JST PH 3-pin Communication Cable (REV-31-1417, included with Expansion Hub)

In order to manage the Control Hub (REV-31-1595) or programming using the onboard programming languages, a computer or other Wi-Fi enabled device will need to connect to the Control Hub's Robot Controller Console. The Robot Control Console is a local network created by the Control Hub to program and manage the device.

By default, the Control Hub has a name that begins with "FTC-" or "FIRST-" followed by four characters that are assigned randomly. The default password for the network is "password". If either of these is forgotten, there are a few ways to recovery or reset the password on the Control Hub.

There are two ways to access the Robot Controller Console. The first will cover how to access the Robot Controller Console with the REV Hardware Client. It is recommended to use the REV Hardware Client as it will allow the user to access the Robot Controller Console over a wired connection.

The second will run through accessing the Robot Controller Console via a web browser.

REV Hardware Client

Download the latest version of the REV Hardware Client and install on a Windows PC.

Startup the REV Hardware Client. Once the hub is fully connected it will show up on the front page of the UI under the Hardware Tab. Select the Control Hub.

After selecting the Connected Hardware the Update tab will pop up. Select the Program and Manage tab. This will take you to the Robot Controller Console build into the REV Hardware Client.

Once in the Robot Controller Console, the homepage of the console will appear. In the upper right corner is the navigation menu which will allow users to access the Blocks, OnBot Java, and Manage pages within the console.

Web Browser

With the Control Hub powered, access the Wi-Fi network selector. For Windows 10 devices, click the Wi-Fi Network icon in the lower right corner of the desktop.

Look for the Wi-Fi that matches the naming protocol of the device.

Once you have found the target network in the list, click on it to select it then press connect.

Provide the network password (in this example “password”) and press “Next” to continue.

Once a wireless connection is established, the status is displayed in the wireless settings for the device.

Open a web browser (Chrome, Firefox, Edge, Internet Explorer) and navigate to "192.168.43.1:8080" through the address bar.

From the Robot Controller Console users can update the Wi-Fi settings, upgrade the operating system and firmware, as well as program the device. It is strongly recommended that you go through all steps above before you begin programming.

Videos

Using the REV Hardware Client

Using a Web Browser

One of the first recommendations made to users of the REV Control System is to update Wi-Fi settings, specifically the name and the password.

All Control Hub's come with a default network name and password. It is useful to change the name and password especially in environments where there are multiple Control Hubs running like at an event or in a classroom. Changing from the default adds an element of network security to the Hub by reducing the potential for access from outside sources.

The Control Hub (REV-31-1595) can utilize either the 2.4 GHz or 5 GHz Wi-Fi band. REV Robotics advises that during competition teams utilize a 5 GHz channel for robot communication. Consult the table below for Driver Station devices that can operate on the 5 GHz band.

Supported Android Devices and Wi-Fi Band Capabilities

As of the 2024-2025 FTC season, Android phones must be running Android 7 (Nougat) or newer to be compatible with the Driver Station App. Please check the game manual for full rules.

The following section will highlight how to access and make changes within the Wi-Fi settings. This section will use the REV Hardware Client to showcase how to make these changes. Once a user has connected to the Robot Controller Console, either via the Hardware Client or a web browser, the steps for accessing Wi-Fi settings are the same.

Steps to Updating Wi-Fi Settings

While in the Robot Controller Console select the menu button. In the image below the menu button is highlighted by an orange square in the upper right-hand corner.

When the menu opens, select Manage.

The Manage page is where the Wi-Fi Settings live. The following steps will show and discuss each change as it is made. Please keep in mind the following warning while moving through the steps:

You will need to reconnect to the new Wi-Fi network after changing the name and/or password. This is true for any Wi-Fi connection, but if you are accessing the REV Hardware Client via a USB connection the Hub will stay connected. Though, you may need to close and reopen the Hardware Client in order to see the changes.

Changing Control Hub Name

Under Wi-Fi Settings, there is an option to change the name of the Control Hub.

For FTC teams you will want to change the name from the default to team number - RC. (i.e. 99999-RC)

Changing the Control Hub Password

Under Wi-Fi Settings, there is an option to change the password of the Control Hub. There are not any restrictions on the password. Changing it from the default is advised but it does not have to change to anything complicated.

Changing the Wi-Fi Band and Channel

The Control Hub is capable of utilizing either the 2.4 GHz or 5 GHz Wi-Fi band. This change is also made within the Wi-Fi Settings.

The Robot Controller Console makes it easy to change between the 2.4 GHz an 5GHz bands. It is advised to check the Legal Android and Wi-Fi Band Capabilities table to determine which band to operate in.

Once a Wi-Fi band is chosen there are two options for dealing with Wi-Fi channels. One option is to let the Control Hub auto default on a channel. The other is to set a specific channel. Both options can be accessed via the drop down menu under the Wi-Fi channel section of the Wi-Fi settings.

It is valuable to know how to change the Wi-Fi Band and Channel as technical staff at an event can request to change those settings.

When you first receive your Control Hub (REV-31-1595), you will have to connect it to a supported Android Device, like a Driver Hub. The following section of the page will walk through how to pair a Driver Hub or Driver Station phone to a Control Hub.

Connecting the Driver Station with the Control Hub

Once you have powered on your Control Hub follow through the process for connection to either a Driver Hub or a Driver Station phone.

Before configuring your Control Hub, devices must be connected to the Control Hub. Below is a sample wiring diagram to show a sample of actuators and sensors usable with the Control Hub.

Wiring Best Practices

Sometimes poorly wired FTC robots can quickly become a tangled mess. Good wire management is crucial for two reasons: it simplifies troubleshooting electrical issues and prevents them from arising in the first place. Here are some helpful tips to keep in mind when wiring your robot effectively.

• Use cables with appropriate lengths to avoid excess cluttering the robot. Alternatively, if a cable must be longer than needed, utilize the full length by routing it neatly.

• Proper cable management keeps everything organized and accessible. Zip ties and Velcro straps are popular choices for their ease of use and adjustability.

• Secure cables away from the areas where the robot might move, such as the drivetrain or arm mechanism.

• Label your wires according to their function. This is especially helpful since wires may be difficult to access later, and clear labels will save you time deciphering their purpose.

• Double-check your wiring with a smart tug before every practice and match to ensure all connections are secure.

For more information on the connectors and cables used with the Control Hub see the links below:

Being able to connect to the Robot Controller Console, connect a Driver Station to a Control Hub, and the basics of wiring different actuators and sensors is just the start!

This section focuses on the next steps for using the REV Control System, including getting started with programming and best practices for managing the Control Hub and Slim Batteries.

Getting Started with Programming

Now that the Control Hub is setup, it is ready to start programming to control a robot.

Hello Robot, available for Blocks and OnBot Java, will walk you through the basics of getting started moving motors, using sensors, and programming a basic drivetrain!

Before you program:

In order for the Control Hub to properly communicate with hardware components, you must perform a two part process known as hardware mapping. One of the most important, and commonly forgotten steps, when getting started programming is the creation of the configuration file, which is the first part of the hardware mapping process.

A properly created configuration file, defines each hardware component with a unique name and a port type and number. After attaching hardware components to the Hub, use the Driver Station application to create a configuration, before beginning to program.

Adding a Expansion Hub

Depending on the application more motor, sensor, or servo ports maybe needed. If your robot needs more motors adding an Expansion Hub might be necessary. Adding an Expansion Hub adds the same amount of hardware ports as one Control Hub (an additional four motor ports, six servo ports, and all the sensor ports) to the system.

Managing the Control Hub

The Control Hub and Expansion Hub are field upgradable devices. When new software is released with new features, bug fixes, and season specific changes users can update the device themselves. Checking for software updates at the start of September and then about every 6-8 weeks is recommended.

To check for software updates you can use the REV Hardware Client.

Slim Battery Best Practices

To maintain and care for your battery, reference the general best practices on the 12V Slim Battery (REV-31-1302) product page or the information below. This includes how to properly store, charge, and care for your battery on the long term.

All rechargeable batteries have a finite lifespan. Factors that affect lifespan include the number of discharge/charge cycles and the average loading of the battery. The following best practices can help maximize the lifespan of your battery:

• Charge rate

  • Minimum: 1.5A

  • Maximum: 3.0A

  • Recommended: 1.8A or 2.0A

• Do not overcharge

  • Disconnect the battery from the charger once it indicates a full charge.

  • Typical charge time does not exceed 2 hours.

  • Do not charge a battery that hasn't been discharged significantly.

    • For example, running the robot under minimal load for a few minutes will not significantly discharge the battery.

• Minimum no-load voltage: 9.0V

  • Discharging the battery past 9.0V can reduce the lifespan of the battery and can permanently damage the cells.

  • Periodic dips below 9.0V when under load is expected and OK.

    • For example, don't forget to unplug your battery after you are finished running the robot and don't run your robot until it completely stops responding!

• Temperature

  • Let the battery cool before and after charging.

  • The battery may feel warm after heavy loading or after charging. This is normal.