Correct DH OS note, add link to FTC Q&A re. Point mismatch.
Westside Robotics
@ -92,15 +92,15 @@ The same points apply as for DS Self Inspect 1 (immediately above), except:
|
||||
<p align="center">[[/images/FTC-Self-Inspect/tDS-3a.png]]
|
||||
<br><i><b>DS Self Inspect 3, on Driver Hub paired to RC phone</b></i><p>
|
||||
|
||||
- Item 4 appears only on the Driver Hub. The check-mark indicates the Operating System is up-to-date with the current version of the DS app.
|
||||
- Item 4 appears only on the Driver Hub. The check-mark indicates the Operating System meets the minimum version requirement in the FTC Game Manual.
|
||||
- Note that `Airplane Mode` has been omitted from the DS inspection, only for Driver Hub. FTC rules exclude the Driver Hub and Control Hub from the Airplane Mode requirement.
|
||||
- Item 8 `Location services` appears only on devices running **Android 8** or higher. This is an SDK/Android technology requirement, not an FTC rule.
|
||||
- Items 9 and 10 must be Yes and No. `Wi-Fi Enabled` means the Driver Hub's Wi-Fi radio is **ON**, to use Wi-Fi Direct for the RC phone. The Driver Hub is technically **able to also be connected** to a Standard/infrastructure Wi-Fi source, including an internet router or a Control Hub. Item 10 confirms this is not happening; see next example.
|
||||
- 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 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; Self Inspect will soon allow this 'point mismatch'.
|
||||
|
||||
- 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).
|
||||
<br>
|
||||
|
||||
<p align="center">[[/images/FTC-Self-Inspect/tDS-3b.png]]
|
||||
<br><i><b>DS Self Inspect 3, on Driver Hub paired to RC phone</b></i><p>
|
||||
@ -148,7 +148,7 @@ Now we change to **Robot Controller** Self Inspect screens. Again, RC screens c
|
||||
|
||||
This RC Self Inspect screen displayed on the paired DS phone is the "same" as the previous one on the RC phone, with two differences:
|
||||
- The 3-dots menu is missing from the header. This menu offered a single choice, to disconnect the Wi-Fi Direct. But this cannot be performed as an RC action, from a DS phone connected by that same Wi-Fi Direct.
|
||||
- Item 14 did not appear on the RC phone's display of this RC Self Inspect. Here is the verification that the DS app and RC app have matching versions; in this case both apps are version 7.0. The rejection of 'point mismatches' (e.g. 7.0 vs. 7.0.1) will be corrected soon.
|
||||
- Item 14 did not appear on the RC phone's display of this RC Self Inspect. Here is the verification that the DS app and RC app have matching versions; in this case both apps are version 7.0. Any "Point mismatch" (e.g. 7.0 vs. 7.0.1) is allowed under [updated FTC rules](https://ftc-qa.firstinspires.org/qa/176).
|
||||
|
||||
[<p align="right"><i>Return to Top</i>](#introduction)<p>
|
||||
|
||||
@ -175,7 +175,7 @@ This is also the same screen, except the RC phone was connected to an internet r
|
||||
|
||||
This display on a paired Driver Hub is the "same" RC Self Inspect screen as the one immediately above, but there are two differences:
|
||||
- The 3-dots menu is missing from the header. This menu offered a single choice, to disconnect the Wi-Fi Direct. But this cannot be performed as an RC action, from a Driver Hub connected by that same Wi-Fi Direct.
|
||||
- Item 14 did not appear on the RC phone's display of this RC Self Inspect. Here is the check for matching versions of the DS app and RC app. In this case, the DS app is 7.0.1 and the RC app is 7.0, rejected here as a mismatch. FTC rules will clarify that such 'point mismatches' are acceptable; the Self Inspect screens will be corrected soon.
|
||||
- Item 14 did not appear on the RC phone's display of this RC Self Inspect. Here is the check for matching versions of the DS app and RC app. In this case, the DS app is 7.0.1 and the RC app is 7.0, rejected here as a mismatch. Such a "Point mismatch" is allowed under [updated FTC rules](https://ftc-qa.firstinspires.org/qa/176).
|
||||
|
||||
[<p align="right"><i>Return to Top</i>](#introduction)<p>
|
||||
|
||||
@ -196,7 +196,7 @@ Looking now at the **Control Hub**, the Self Inspect screen has a few difference
|
||||
- Item 9 does apply here to the Control Hub. Its password must be changed from the factory default ("password").
|
||||
- Items 10 and 11 should be Yes and Yes for Control Hub, which uses only Standard/infra Wi-Fi. Item 11 does not indicate **what** the Control Hub is connected to (but it must be the DS phone displaying this screen).
|
||||
- Item 12 shows the Standard Wi-Fi **network name**, or Access Point (AP), that is broadcast by the Control Hub. The check-mark indicates the AP has a correctly formatted FTC name. This does **not** check that the DS and RC names match (team number). In fact, this DS phone is 2468-A-DS and this Control Hub is 9999-A-RC, an **illegal combination** to be flagged by the FTC team or the Field Inspector.
|
||||
- Item 14 appears only on DS displays of RC Self Inspect. Here is the check for matching versions of DS app and RC app; in this case both apps are version 7.0. The rejection of 'point mismatches' (e.g. 7.0 vs. 7.0.1) will be corrected soon.
|
||||
- Item 14 appears only on DS displays of RC Self Inspect. Here is the check for matching versions of DS app and RC app; in this case both apps are version 7.0. Any "Point mismatch" (e.g. 7.0 vs. 7.0.1) is allowed under [updated FTC rules](https://ftc-qa.firstinspires.org/qa/176).
|
||||
- Item 15 verifies that an RC device does **not** have an DS app installed. This would be quite a mistake for a Control Hub, lacking an onboard screen.
|
||||
|
||||
[<p align="right"><i>Return to Top</i>](#introduction)<p>
|
||||
@ -208,13 +208,13 @@ For a Control Hub, the Self Inspect categories displayed on Driver Hub are the s
|
||||
<p align="center">[[/images/FTC-Self-Inspect/tRC-6b.png]]
|
||||
<br><i><b>RC Self Inspect 6, appearing on Driver Hub paired to Control Hub</b></i><p>
|
||||
|
||||
The only reporting difference here is the 'mismatch' between the Driver Hub's DS app version of 7.0.1 and the Control Hub's 7.0. This is likely to happen since Driver Hubs are typically auto-updated, in this case to a DS version intended only for old Android 6 phones. Soon a correction will accept such 'point version' mismatches.<p>
|
||||
The only reporting difference here is the 'mismatch' between the Driver Hub's DS app version of 7.0.1 and the Control Hub's 7.0. This is likely to happen since Driver Hubs are typically auto-updated, in this case to a DS version intended only for old Android 6 phones. Such a "Point mismatch" is allowed under [updated FTC rules](https://ftc-qa.firstinspires.org/qa/176).<p>
|
||||
<br>
|
||||
|
||||
<p align="center">[[/images/FTC-Self-Inspect/tRC-6a.png]]
|
||||
<br><i><b>RC Self Inspect 6, appearing on Driver Hub paired to Control Hub</b></i><p>
|
||||
<br><i><b>RC Self Inspect 6, appearing on Driver Hub previously paired to Control Hub</b></i><p>
|
||||
|
||||
Lastly... with no connection, a DS device cannot display any information about the RC device status.
|
||||
Lastly... with no active connection, a DS device cannot display any information about the RC device status.
|
||||
|
||||
[<p align="right"><i>Return to Top</i>](#introduction)<p>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user