Updated Using Two Expansion Hubs (markdown)
@ -41,6 +41,8 @@ Use this process to check the serial addresses for each of your Expansion Hubs.
|
||||
|
||||
**Important Note:** By default, a REV Robotics Expansion Hub should have its address preset at the factory to a value of 2. Also by default, a REV Robotics Control Hub should have the address for its internal Expansion Hub preset at the factory to a value of 1. If you are using a Control Hub combined with a second Expansion Hub, then their factory addresses (1 and 2 respectively) should not conflict. You should not need to change either address for this combination.
|
||||
|
||||
**Important Note:** An address of 1 is typically reserved for a Control Hub. As a general rule, you should avoid using an Expansion Hub with an address of 1. Your Expansion Hubs should all have non-conflicting addresses that are also not equal to 1.
|
||||
|
||||
### Changing the Address of an Expansion Hub
|
||||
You can use the Advanced Settings menu of the FTC Robot Controller App to change the address of an Expansion Hub. Note that it is recommended that when you change the address of an Expansion Hub, you only connect one Expansion Hub to the Robot Controller during the change address process.
|
||||
|
||||
@ -60,8 +62,6 @@ The USB serial number of the Expansion Hub and its currently assigned address sh
|
||||
|
||||
Use the dropdown list control on the right hand side to change the address to a non-conflicting value.
|
||||
|
||||
**Important Note:** An address of 1 is typically reserved for a Control Hub. If you are using two Expansion Hubs with an Android phone Robot Controller, than you should avoid assigning an address of 1 to either Expansion Hub.
|
||||
|
||||
<p align="center"><img src="https://github.com/FIRST-Tech-Challenge/WikiSupport/blob/master/ftc_app/images/Advanced/TwoExpansionHubs/NewAddress.jpg" width="175"> </p>
|
||||
|
||||
Push the "Done" button to change the address. You should see a message indicating that the Expansion Hub's address has been changed.
|
||||
|
Reference in New Issue
Block a user