SCDS/FtcRobotControllerSDK
7
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Updated Managing a Control Hub (markdown)

FTC Engineering
2019-08-14 11:25:10 -04:00
parent d73581accd
commit c04aced061
1 changed files with 6 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
Managing-a-Control-Hub.md

@ -160,8 +160,10 @@ Follow these steps to disable the built-in Android controller of a Control Hub:
6. Type the command “reboot” to reboot your Android controller. Upon reboot, the Android controller should detect that the “persist.ftcandroid.db.disable” propery is now set to true. It will disable the connection between the Android device and the built in Expansion Hub of the Control Hub. 6. Type the command “reboot” to reboot your Android controller. Upon reboot, the Android controller should detect that the “persist.ftcandroid.db.disable” propery is now set to true. It will disable the connection between the Android device and the built in Expansion Hub of the Control Hub.
You should now be able to use your Control Hub as an Expansion Hub. Note that if you do this you might need to change the serial address of the Control Hub's internal Expansion Hub. By default, the serial number for a Control Hub is set to 1. If you re-enable the internal Android Controller, you should set the serial number back to 1. You should now be able to use your Control Hub as an Expansion Hub. Note that if you do this you might need to change the serial address of the Control Hub's internal Expansion Hub. By default, the serial number for a Control Hub is set to 1. If you re-enable the internal Android Controller, you should set the serial number back to 1.
 
Enabling the Built-In Android Controller **IMPORTANT NOTE:** A _disabled_ internal Android controller is not really disabled. Instead, the Robot Controller app is not active and a user can connect to the Expansion Hub portion of the Control Hub using the USB **Mini** port on the back of the Control Hub. When you disable your internal Android controller, you still might see the Wi-Fi network established by the internal Android controller (which is still powered on whenever the Control Hub is turned on).
#### Enabling the Built-In Android Controller
Follow these steps to enable the built-in Android controller of a Control Hub: Follow these steps to enable the built-in Android controller of a Control Hub:
1. Connect a USB micro cable from your development laptop to the port labeled "USB C" on the Control Hub. 1. Connect a USB micro cable from your development laptop to the port labeled "USB C" on the Control Hub.
2. From a terminal on your laptop, use adb to shell into the Android controller. 2. From a terminal on your laptop, use adb to shell into the Android controller.
@ -169,8 +171,9 @@ Follow these steps to enable the built-in Android controller of a Control Hub:
4. Use the command “setprop persist.ftcandroid.db.disable false” to change this system property. 4. Use the command “setprop persist.ftcandroid.db.disable false” to change this system property.
5. Type the command “getprop persist.ftcandroid.db.disable” to verify that the property was changed to false. 5. Type the command “getprop persist.ftcandroid.db.disable” to verify that the property was changed to false.
6. Type the command “reboot” to reboot your Android controller. Upon reboot, the Android controller should detect that the “persist.ftcandroid.db.disable” propery is now set to false. It will enable the connection between the Android device and the built in Expansion Hub of the Control Hub. It will also launch the Robot Controller app on the built-in Android controller and operate as a Control Hub. 6. Type the command “reboot” to reboot your Android controller. Upon reboot, the Android controller should detect that the “persist.ftcandroid.db.disable” propery is now set to false. It will enable the connection between the Android device and the built in Expansion Hub of the Control Hub. It will also launch the Robot Controller app on the built-in Android controller and operate as a Control Hub.
 
Note that if you had previously changed the serial address of the internal Expansion Hub to a value other than 1, then you should change the address back to 1 once the internal Android controller has been re-enabled. After the address change, you will need to reboot your machine and recreate your configuration file for your Control Hub. Note that if you had previously changed the serial address of the internal Expansion Hub to a value other than 1, then you should change the address back to 1 once the internal Android controller has been re-enabled. After the address change, you will need to reboot your machine and recreate your configuration file for your Control Hub.