|
2 | 2 | icon: first
|
3 | 3 | ---
|
4 | 4 |
|
5 |
| -!!! warning |
6 |
| - |
7 |
| - These instructions are for Android Studio users only! Software support may be built into the SDK at a future date for Onbot Java and Blocks users as well, but only Android Studio is supported at this time. |
8 |
| - |
9 |
| -# Adding the Driver |
10 |
| - |
11 |
| -In order for the Optical Tracking Odometry Sensor to be recognized in the hardware configuration, you must first add the driver and upload it to the robot. It is also recommended to add the sample OpMode at the same time. |
| 5 | +## Update the FTC Robot Controller |
12 | 6 |
|
13 |
| -To do so, you'll need the driver (`SparkFunOTOS.java`) and sample OpMode (`SensorSparkFunOTOS.java`) from the [SparkFun Optical Tracking Odometry Sensor FTC Java Library GitHub Repo](https://github.com/sparkfun/SparkFun_Qwiic_OTOS_FTC_Java_Library). You can download them from the link or click on the button below: |
| 7 | +!!! attention |
14 | 8 |
|
15 |
| -<center> |
16 |
| - [SparkFun Optical Tracking Odometry Sensor FTC Java Library](https://github.com/sparkfun/SparkFun_Qwiic_OTOS_FTC_Java_Library/archive/refs/heads/main.zip){ .md-button .md-button--primary } |
17 |
| -</center> |
| 9 | + Version v9.2 of the [FTC SDK](https://github.com/sparkfun/SparkFun_Qwiic_OTOS_FTC_Java_Library) added [our Java driver](https://github.com/sparkfun/SparkFun_Qwiic_OTOS_FTC_Java_Library), so it is no longer necessary to manually install those files. Make sure you have at least v9.2 installed on your Control Hub before continuing! |
18 | 10 |
|
| 11 | +## Hardware Configuration |
19 | 12 |
|
20 |
| - |
21 |
| -Once you have the driver and sample OpMode files, add them to your TeamCode folder like so: |
22 |
| - |
23 |
| -<figure markdown> |
24 |
| -[{ width="600" }](assets/img/android_studio.png "Click to enlarge") |
25 |
| -<figcaption markdown>Android Studio</figcaption> |
26 |
| -</figure> |
27 |
| - |
28 |
| - |
29 |
| -Then upload the code to your robot like normal. |
30 |
| - |
31 |
| -# Hardware Configuration |
32 |
| - |
33 |
| -Make sure you've added the driver and uploaded it to the robot as outlined above. You can edit your robot's hardware configuration from the Driver Station. Select the I<sup>2</sup>C port that the OTOS is connected to, then tap the "Add" button. From the dropdown, you should see "SparkFun OTOS" like so: |
| 13 | +You can edit your robot's hardware configuration from the Driver Station. Select the I<sup>2</sup>C port that the OTOS is connected to, then tap the "Add" button. From the dropdown, you should see "SparkFun OTOS" like so: |
34 | 14 |
|
35 | 15 | <figure markdown>
|
36 | 16 | [{ width="600" }](assets/img/hardware_config.png "Click to enlarge")
|
37 | 17 | <figcaption markdown>Hardware Configuration</figcaption>
|
38 | 18 | </figure>
|
39 | 19 |
|
40 | 20 | !!! warning
|
41 |
| - If you don't see "SparkFun OTOS" in the dropdown, make sure you have added the driver and uploaded it to your robot. |
| 21 | + |
| 22 | + If you don't see "SparkFun OTOS" in the dropdown, make sure you have updated your Control Hub to use at least version v9.2 of the FTC SDK. |
42 | 23 |
|
43 | 24 | Then enter a name for the sensor. The sample OpMode assumes it is named `sensor_otos`, so that is recommended.
|
44 | 25 |
|
|
0 commit comments