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

11-14-22 add: An incorrect red mark here can be cleared by correcting the date in the Android device Settings.

Westside Robotics
2022-11-14 09:13:59 -08:00
parent 36780258a4
commit 39bebb5b08
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
FTC-Self-Inspect.md

@ -56,7 +56,7 @@ These combinations can display **slightly different** Self Inspect categories, s
- Items 9 and 10 here must be Yes and No. `Wi-Fi Enabled` means the DS device's Wi-Fi radio is **ON**, to use Wi-Fi Direct. It must **not** be connected to a Standard/infrastructure Wi-Fi source, such as an internet router or a Control Hub, when intending to pair with an RC phone. - Items 9 and 10 here must be Yes and No. `Wi-Fi Enabled` means the DS device's Wi-Fi radio is **ON**, to use Wi-Fi Direct. It must **not** be connected to a Standard/infrastructure Wi-Fi source, such as an internet router or a Control Hub, when intending to pair with an RC phone.
- Item 11 indicates whether the **device's Wi-Fi Direct name** meets FTC format requirements. It does not check whether the paired device has a matching RC name (team number). In this case, the phones are legally named 2468-A-DS and 2468-A-RC. <i>DS Settings (Driver Station Name) allows only FTC-legal names, but any name can be entered in the DS phone's Android Wi-Fi Direct settings.</i> - Item 11 indicates whether the **device's Wi-Fi Direct name** meets FTC format requirements. It does not check whether the paired device has a matching RC name (team number). In this case, the phones are legally named 2468-A-DS and 2468-A-RC. <i>DS Settings (Driver Station Name) allows only FTC-legal names, but any name can be entered in the DS phone's Android Wi-Fi Direct settings.</i>
- Item 12 verifies that a DS device does **not** have an RC app installed. - Item 12 verifies that a DS device does **not** have an RC app installed.
- Item 13 ensures the DS app meets the minimum version **for the current FTC season**, based on the device's system date.<p> - Item 13 ensures the DS app meets the minimum version **for the current FTC season**, based on the device's system date. An "incorrect" red mark here can be cleared by correcting the date in the **Android device Settings**.<p>
<br> <br>
@ -99,7 +99,7 @@ The same points apply as for DS Self Inspect 1 (immediately above), except:
- Item 10's No would be **rejected** if the DS Pairing Method was set to Control Hub. - Item 10's No would be **rejected** if the DS Pairing Method was set to Control Hub.
- Item 11 indicates whether the **device name** meets FTC format requirements. It does not check whether the paired device has a matching RC name (team number). - Item 11 indicates whether the **device name** meets FTC format requirements. It does not check whether the paired device has a matching RC name (team number).
- Item 12 verifies that the Driver Hub does **not** have an RC app installed. - Item 12 verifies that the Driver Hub does **not** have an RC app installed.
- Item 13 ensures the DS app meets the minimum version **for the current FTC season**, based on the device's system date. This particular version 7.0.1 does not exactly match the RC phone's 7.0. Such a "Point mismatch" is allowed under [updated FTC rules](https://ftc-qa.firstinspires.org/qa/176). - Item 13 ensures the DS app meets the minimum version **for the current FTC season**, based on the device's system date. This particular version 7.0.1 does not exactly match the RC phone's 7.0. Such a "Point mismatch" is allowed under [updated FTC rules](https://ftc-qa.firstinspires.org/qa/176). Otherwise, an "incorrect" red mark here can be cleared by correcting the date in the **Android device Settings**.
<br> <br>
<p align="center">[[/images/FTC-Self-Inspect/tDS-3b.png]] <p align="center">[[/images/FTC-Self-Inspect/tDS-3b.png]]
@ -136,7 +136,7 @@ Now we change to **Robot Controller** Self Inspect screens. Again, RC screens c
- Item 5 lists the Expansion Hub addresses and firmware levels. This example shows one Expansion Hub, but two can be listed here. A check-mark indicates all firmware is up-to-date based on the current version of the RC app. This item shows "N/A" if no Hubs are connected. - Item 5 lists the Expansion Hub addresses and firmware levels. This example shows one Expansion Hub, but two can be listed here. A check-mark indicates all firmware is up-to-date based on the current version of the RC app. This item shows "N/A" if no Hubs are connected.
- Item 10 `RC Password` appears only in RC Self Inspect, not in DS Self Inspect. It checks the FTC requirement for a Control Hub password different than the factory default ("password"). Although aimed only at the Control Hub, this item does appear on RC phones (as here) which don't have a default password and thus always get the check-mark. - Item 10 `RC Password` appears only in RC Self Inspect, not in DS Self Inspect. It checks the FTC requirement for a Control Hub password different than the factory default ("password"). Although aimed only at the Control Hub, this item does appear on RC phones (as here) which don't have a default password and thus always get the check-mark.
- Item 14 ensures the RC app meets the minimum version **for the current FTC season**, based on the device's system date. It does not check for a match with the DS app version. - Item 14 ensures the RC app meets the minimum version **for the current FTC season**, based on the device's system date. It does not check for a match with the DS app version. An "incorrect" red mark here can be cleared by correcting the date in the **Android device Settings**.
- Item 15 verifies that the RC device does **not** have an DS app installed. - Item 15 verifies that the RC device does **not** have an DS app installed.
[<p align="right"><i>Return to Top</i>](#introduction)<p> [<p align="right"><i>Return to Top</i>](#introduction)<p>