From 8e5932bb8b81d052d9ed364e32678dfc82c73cc0 Mon Sep 17 00:00:00 2001 From: Westside Robotics Date: Mon, 26 Dec 2022 11:28:55 -0800 Subject: [PATCH] 12-26-2022 restore Return-to-Top function. Header-only link is no longer recognized, now requires full URL. --- FTC-Self-Inspect.md | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/FTC-Self-Inspect.md b/FTC-Self-Inspect.md index 724e541..2200c9b 100644 --- a/FTC-Self-Inspect.md +++ b/FTC-Self-Inspect.md @@ -43,7 +43,7 @@ This means that the Self Inspect screens can report as follows: These combinations can display **slightly different** Self Inspect categories, status phrases, and pass/fail results. They are described below; click the **blue link** to explore the Self Inspect screen for that device and combination. -[

Return to Top](#introduction)

+

[[Return to Top|https://github.com/FIRST-Tech-Challenge/FtcRobotController/wiki/FTC Self Inspect]]

## DS Self Inspect 1, on DS phone paired to RC phone @@ -73,7 +73,7 @@ Here's a report from the same phone, with many items **rejected** by Self Inspec - Item 11 rejects the device's **Wi-Fi Direct name** for not meeting FTC format requirements. The bad name shown here was created in the DS phone's Android Wi-Fi Direct settings; not possible using the app's DS Settings (Driver Station Name). - Item 12 rejects the presence of an RC app installed on this DS device. The rejection is not for the older version (6.2), but simply for being an RC app. -[

Return to Top](#introduction)

+

[[Return to Top|https://github.com/FIRST-Tech-Challenge/FtcRobotController/wiki/FTC Self Inspect]]

## DS Self Inspect 2, on DS phone paired to Control Hub @@ -85,7 +85,7 @@ The same points apply as for DS Self Inspect 1 (immediately above), except: - Item 10's Yes would be **rejected** if the DS Pairing Method was set to Wi-Fi Direct -- thus intending to connect with an RC phone. - Item 11 shows the Standard Wi-Fi **network name**, or Access Point (AP), that the DS phone is connected to. The check-mark indicates the AP is an FTC legal device (Control Hub) and has a correctly formatted name. This does **not** check that the DS and RC names match (team number). In fact, this 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. -[

Return to Top](#introduction)

+

[[Return to Top|https://github.com/FIRST-Tech-Challenge/FtcRobotController/wiki/FTC Self Inspect]]

## DS Self Inspect 3, on Driver Hub paired to RC phone @@ -108,7 +108,7 @@ The same points apply as for DS Self Inspect 1 (immediately above), except: This Self Inspect screen appeared while the Driver Hub was paired to an RC phone, then was *also* connected to to a Control Hub via Standard Wi-Fi. The DS home screen temporarily showed "Connected" (to RC phone) and "No Heartbeat", then recovered its pairing to the RC phone. - Item 10 shows the discrepancy. The DS app soon closes this Standard Wi-Fi connection, allowing the Driver Hub to remain paired only with the RC phone. -[

Return to Top](#introduction)

+

[[Return to Top|https://github.com/FIRST-Tech-Challenge/FtcRobotController/wiki/FTC Self Inspect]]

## DS Self Inspect 4, on Driver Hub paired to Control Hub @@ -125,7 +125,7 @@ This Self Inspect screen appeared while the Driver Hub was paired to an RC phone This Self Inspect screen appeared after the Driver Hub was paired to a Control Hub, then was connected to a Wi-Fi internet router. - Item 11 shows the error. The Driver Hub can connect via Standard Wi-Fi to only one AP at a time; this network is not an FTC RC device. -[

Return to Top](#introduction)

+

[[Return to Top|https://github.com/FIRST-Tech-Challenge/FtcRobotController/wiki/FTC Self Inspect]]

## RC Self Inspect 1, appearing on RC phone paired with DS phone @@ -139,7 +139,7 @@ Now we change to **Robot Controller** Self Inspect screens. Again, RC screens c - 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. -[

Return to Top](#introduction)

+

[[Return to Top|https://github.com/FIRST-Tech-Challenge/FtcRobotController/wiki/FTC Self Inspect]]

## RC Self Inspect 2, appearing on DS phone paired to RC phone @@ -150,7 +150,7 @@ This RC Self Inspect screen displayed on the paired DS phone is the "same" as th - 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. Any "Point mismatch" (e.g. 7.0 vs. 7.0.1) is allowed under updated FTC rules (was Q&A #176 for 2021-2022 season). -[

Return to Top](#introduction)

+

[[Return to Top|https://github.com/FIRST-Tech-Challenge/FtcRobotController/wiki/FTC Self Inspect]]

## RC Self Inspect 3, appearing on RC phone paired with Driver Hub @@ -166,7 +166,7 @@ The above screen is the same as RC Self Inspect 1, where the DS device is a DS p This is also the same screen, except the RC phone was connected to an internet router, while paired with a Driver Hub. The Standard Wi-Fi connection caused the RC phone to temporarily lose that pairing, which was able to be restored. - Item 12 shows the rejection: connected via Standard Wi-Fi, but **not** to an FTC DS device. -[

Return to Top](#introduction)

+

[[Return to Top|https://github.com/FIRST-Tech-Challenge/FtcRobotController/wiki/FTC Self Inspect]]

## RC Self Inspect 4, appearing on Driver Hub paired to RC phone @@ -177,7 +177,7 @@ This display on a paired Driver Hub is the "same" RC Self Inspect screen as the - 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. Such a "Point mismatch" is allowed under updated FTC rules (was Q&A #176 for 2021-2022 season). -[

Return to Top](#introduction)

+

[[Return to Top|https://github.com/FIRST-Tech-Challenge/FtcRobotController/wiki/FTC Self Inspect]]

## RC Self Inspect 5, appearing on DS phone paired to Control Hub @@ -199,7 +199,7 @@ Looking now at the **Control Hub**, the Self Inspect screen has a few difference - 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 (was Q&A #176 for 2021-2022 season). - 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. -[

Return to Top](#introduction)

+

[[Return to Top|https://github.com/FIRST-Tech-Challenge/FtcRobotController/wiki/FTC Self Inspect]]

## RC Self Inspect 6, appearing on Driver Hub paired to Control Hub @@ -216,7 +216,7 @@ The only reporting difference here is the 'mismatch' between the Driver Hub's DS Lastly... with no active connection, a DS device cannot display any information about the RC device status. -[

Return to Top](#introduction)

+

[[Return to Top|https://github.com/FIRST-Tech-Challenge/FtcRobotController/wiki/FTC Self Inspect]]

## Summary @@ -226,7 +226,7 @@ Self Inspect may be reviewed in Field Inspection at an FTC tournament, but is ** Each inspection screen updates automatically, with or without a Restart Robot. This allows quick verification that issues have been resolved. -[

Return to Top](#introduction)

+

[[Return to Top|https://github.com/FIRST-Tech-Challenge/FtcRobotController/wiki/FTC Self Inspect]]

=============