diff --git a/source/field-monitor/field-connectivity/connectivity-guide.rst b/source/field-monitor/field-connectivity/connectivity-guide.rst index 28f5980..d06b213 100644 --- a/source/field-monitor/field-connectivity/connectivity-guide.rst +++ b/source/field-monitor/field-connectivity/connectivity-guide.rst @@ -1,84 +1,90 @@ .. _field-monitor-connectivity-guide: Connectivity Guide -====================== - -.. note:: - The screenshots in this article show a former version of the field monitor. While some of the columns are missing or look slightly different, the concepts and information described are still accurate. +================== Introduction ------------ -When using the Field Monitor to diagnose connectivity issues, always work from left to right. All connection statuses are reported to the FMS by the Driver Station (DS). This means that regardless of true connection status, a Radio won't "go green" until the DS is fully connected. Additionally, a roboRIO won't "go green" unless the Radio is connected. +When using the Field Monitor to diagnose connectivity issues, always work from driver station, to radio, to roboRIO. +On the field monitor, this means work from left to right. All connection statuses are reported +to the FMS by the Driver Station (DS). This means that regardless of true connection status, a robot radio won't fully connect +until the driver station is fully connected. Similarly, the roboRIO won't fully connect until the robot radio is fully connected. + +:ref:`Status Indicators ` describes all of the potential status indicators in detail. .. image:: images/connectivity-guide-1.png -In this example, all six teams have a varying connectivity state. +In this example, each team has a different connectivity state. * Team 1: Fully connected and match-ready. -* Team 2: All connected indicators, but yellow sqaure and exclamation mark for RIO is still present. This state is generally the result of a robot code issue, and will prevent the field from "going green" until resolved. +* Team 2: Same as 1. * Team 3: No roboRIO connection. -* Team 4: Wrong station. This signifies that the team must move to the correct station (in most cases, stations 1 and 3 are flipped). "Team Mismatch" signifies that the team has come up for the wrong match or has plugged in before the scoring table finalized the previous match, in which case their DS is "Waiting". -* Team 5: An ethernet cable is plugged in, but the DS isn't properly communicating with the FMS. +* Team 4: The team's driver station laptop is connected to the wrong driver station. +* Team 5: An ethernet cable is plugged in, but the driver station software is not running or is unable to communicate with the FMS. * Team 6: No Radio connection. A Radio connection is required in order to have a roboRIO connection. .. note:: - Reminder: When troubleshooting connectivity, always start with the DS and work your way from left to right on the Field Monitor. + When troubleshooting connectivity, always start with the driver station and work your way from left to right on the Field Monitor. Driver Station Troubleshooting ------------------------------ -DS Ethernet -^^^^^^^^^^^ +You are verifying that the driver station has Ethernet connectivity and properly configured software. + +Driver Station Ethernet +^^^^^^^^^^^^^^^^^^^^^^^ + +.. image:: images/ds-x.png -If the Field Monitor shows yellow square with an exclamation mark for DS connection, move on to **DS Software**. +This status indicates no ethernet connectivity. -#. Verify DS ethernet cable is securely plugged into the DS computer, making sure to check for worn out ethernet ports. -#. Verify the DS computer is turned on and logged in. -#. Verify the DS computer's ethernet adapter is enabled and functioning. (Quickly access network adapters by typing "ncpa.cpl" into the start menu and pressing the return key). -#. If the adapter is found in step 3: +#. Verify ethernet cable is securely plugged into the laptop, making sure to check for worn out ethernet ports. +#. Verify the laptop is turned on and logged in. +#. Verify the ethernet adapter is enabled and functioning. Quickly access network adapters by typing "ncpa.cpl" into the start menu and pressing the return key. +#. If the adapter is found in the previous step: * Disable/Re-enable the adapter. - * Restart the DS Computer. - * Verify the cable by connecting to a different device. + * Restart the laptop. + * Verify the ethernet cable by connecting to a different device. * Use a USB to ethernet adapter. - * Offer a loaner DS. + * Offer a loaner laptop. -#. If no adapter is found in step 3: +#. If no adapter is found: - * Restart the DS computer. + * Restart the laptop. * Use a USB to ethernet adapter. - * Offer a loaner DS. + * Offer a loaner laptop. +Driver Station Software +^^^^^^^^^^^^^^^^^^^^^^^ -DS Software -^^^^^^^^^^^ +.. image:: images/ds-bang.png -If the Field Monitor shows a white circle with a checkmark for DS connection, move on to **Robot Troubleshooting**. +This status indicates a device is connected at the driver station, but FMS cannot communicate with the Driver Station software. -#. Confirm the DS software is running on the DS computer. -#. Confirm the team is in the correct station, and in practice matches, verify the correct number was entered prior to Prestart. -#. Disable all additional network adapters. (Quickly access network adapters by typing "ncpa.cpl" into the start menu and pressing the return key) -#. Verify the DS computer's ethernet adapter is enabled and functioning. -#. If the adapter is found in step 4: +#. Confirm the driver station software is running. +#. Disable all additional network adapters. Quickly access network adapters by typing "ncpa.cpl" into the start menu and pressing the return key. +#. Verify the ethernet adapter is enabled and functioning. If not, move back to `Driver Station Ethernet`_. +#. If the adapter is found: * Verify the adapter is set to 'Obtain an IP address automatically' (DHCP). * Disable/Re-enable the adapter. - * Restart the DS Computer. - * Verify the cable by connecting to a different device. + * Restart the laptop. + * Verify the ethernet cable by connecting to a different device. * Use a USB to ethernet adapter. - * Offer a loaner DS. + * Offer a loaner laptop. -#. If no adapter is found in step 4: +#. If no adapter is found: - * Restart the DS computer. + * Restart the laptop. * Use a USB to ethernet adapter. - * Offer a loaner DS. + * Offer a loaner laptop. #. Restart the DS Software -#. Disable all three Windows Defender Firewall profiles (Domain, Public, Private) as well as any third-party firewall applications if present. +#. Check whether firewalls are enabled via the Driver Station Diagnostics tab. If so, disable all three Windows Defender Firewall profiles (Domain, Public, Private) as well as any third-party firewall applications if present. - * If the firewall cannot be disabled (often due to lack of admin access) consider using the loaner DS. + * If the firewall cannot be disabled (often due to lack of admin access) consider using the loaner laptop. * If the firewall can't be disabled but allows for specified ports to be opened, create port exceptions for: .. list-table:: @@ -105,82 +111,92 @@ If the Field Monitor shows a white circle with a checkmark for DS connection, mo - Limelight Camera or Team Use #. Release/Renew the IP address. -#. If the DS still has not connected, look for other possible solutions. For example, check ethernet cable, check for odd DS configurations such as MacOS running a Windows virtual machine. flaky computer, weak battery, very high CPU usage, etc. +#. If the driver station still has not connected, look for other possible solutions. For example, check ethernet cable, check for odd DS configurations such as MacOS running a Windows virtual machine. flaky computer, weak battery, very high CPU usage, etc. #. If the team still has not connected: * Get an FTA involved. - * Offer a loaner DS. + * Offer a loaner laptop. * Follow up by working with the team to troubleshoot when time allows. - -Robot Troubleshooting +Radio Troubleshooting --------------------- -Note: When troubleshooting a robot, a team-member should perform any actions which require contacting the robot. You should only contact a robot if the team directly asks for your assistance. +.. image:: images/radio-x.png + +This status indicates the radio is not connected to the Field Access Point. + +Note: When troubleshooting a robot, a team member should perform any actions which require contacting the robot. You should only contact a robot if the team directly asks for your assistance. VH-109 Robot Radio ^^^^^^^^^^^^^^^^^^ -If the Field Monitor shows signal bars for the Radio connection, move on to **roboRIO**. - -#. Verify the robot is powered on. Locate the radio and check that it is receiving power. (~45 second boot time) +#. Verify the robot is powered on. +#. Locate the radio and check that it is receiving power. (~45 second boot time) #. Verify the radio is in client (bridge) mode and programmed for the event. * Blue 6GHz LED indicates the radio is in Client Mode and Linked. If the Field Monitor still does not show a Radio connected, verify firewalls are disabled on the DS. * SYS LED will blink in a Blink/Blink/Pause .._.._ pattern to indicate the radio has been programmed and is attempting to connect to the field AP. At the discretion of the FTA, the radio may be (re)programmed on the field. - #. If a radio is powered on and booted in client mode but does not link to the field: * Verify the radio has been programmed for the current event in progess. (Radios must be reprogrammed for each new event) * Check with the team to ensure they have no backup radios powered on in the venue. - OM5P Robot Radio (China Events Only) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -If the Field Monitor shows signal bars for the Radio connection, move on to **roboRIO**. - -#. Verify the robot is powered on. Locate the radio and check that it is receiving power. (~60 second boot time) +#. Verify the robot is powered on. +#. Locate the radio and check that it is receiving power. (~60 second boot time) #. Verify the radio is in bridge mode and programmed for the event. * Green LED indicates the radio is in Bridge Mode and Linked. If the Field Monitor still does not show a Radio connected, verify firewalls are disabled on the DS. * Amber/Red LEDs indicate the radio is in AP Mode and has yet to be programmed. At the discretion of the FTA, the radio may be (re)programmed on the field. - #. If a radio is powered on and booted in bridge mode but does not link to the field: * Verify the radio has been programmed for the current event in progess. (Radios must be reprogrammed for each new event) * Check with the team to ensure they have no backup radios powered on in the venue. -roboRIO -^^^^^^^ +roboRIO Troubleshooting +----------------------- + +.. image:: images/rio-x.png + +This status indicates that the driver station software cannot communicate with the roboRIO. + +.. image:: images/radio-laptop.png + :scale: 50% + +This status indicates that the radio cannot communicate with the roboRIO. #. Verify the roboRIO is receiving power. #. Check for activity on the amber ethernet traffic light on the roboRIO. If there is no activity on the link light (not flashing, or flashing very slow): * Confirm the ethernet cable is fully seated on both ends. + * If the robot has a switched ethernet network, verify the switch is powered up. * Confirm the green ethernet link light on the roboRIO is illuminated. If it is not, the cable should be replaced. * Have the team move the cable to a different port on the radio, or directly into the radio if the roboRIO was connected through a switch. - * Reset the roboRIO. (Circular blue button on the front panel) - * Power Cycle the robot. - + * Reset the roboRIO. (Circular blue button on the front panel, or via the button in the Driver Station Diagnostics tab) + * Power cycle the robot. #. For roboRIO 2.0 models, verify the microSD card is present and fully seated. #. Confirm that the yellow roboRIO status light is not on or blinking. If it is, the roboRIO must be re-imaged. #. Verify all firewalls are disabled on the DS. #. Reset the roboRIO. (Circular blue button on the front panel) -#. Power Cycle the robot. +#. Power cycle the robot. #. Confirm the roboRIO is running the correct image. -#. If the Field Monitor shows a green connection with the roboRIO but the team's row has a yellow background: - - * Ask the team if code was changed between matches. (If yes, the team likely did not build/deploy correctly) - * For roboRIO 2.0 models, verify the microSD card is present and fully seated. - * Check the DS diagnostics tab for messages from the robot. - * Reset the roboRIO. (Circular blue button on the front panel) - * Power Cycle the robot. +Code Troubleshooting +-------------------- +.. image:: images/roborio-bang.png + :scale: 50% +This status indicates that the roboRIO is present, but no code is detected. +#. Ask the team if code was changed between matches. (If yes, the team likely did not build/deploy correctly) +#. For roboRIO 2.0 models, verify the microSD card is present and fully seated. +#. Check the Driver Station Diagnostics tab for messages from the robot. +#. Restart the robot code via the button in the Driver Station Diagnostics tab. +#. Reset the roboRIO. (Circular blue button on the front panel, or via the button in the Driver Station Diagnostics tab) diff --git a/source/field-monitor/field-connectivity/images/ds-bang.png b/source/field-monitor/field-connectivity/images/ds-bang.png new file mode 100644 index 0000000..ae8cd33 Binary files /dev/null and b/source/field-monitor/field-connectivity/images/ds-bang.png differ diff --git a/source/field-monitor/field-connectivity/images/ds-x.png b/source/field-monitor/field-connectivity/images/ds-x.png new file mode 100644 index 0000000..eff26fa Binary files /dev/null and b/source/field-monitor/field-connectivity/images/ds-x.png differ diff --git a/source/field-monitor/field-connectivity/images/radio-laptop.png b/source/field-monitor/field-connectivity/images/radio-laptop.png new file mode 100644 index 0000000..e213be5 Binary files /dev/null and b/source/field-monitor/field-connectivity/images/radio-laptop.png differ diff --git a/source/field-monitor/field-connectivity/images/radio-x.png b/source/field-monitor/field-connectivity/images/radio-x.png new file mode 100644 index 0000000..5b1f2af Binary files /dev/null and b/source/field-monitor/field-connectivity/images/radio-x.png differ diff --git a/source/field-monitor/field-connectivity/images/rio-x.png b/source/field-monitor/field-connectivity/images/rio-x.png new file mode 100644 index 0000000..5e83a6b Binary files /dev/null and b/source/field-monitor/field-connectivity/images/rio-x.png differ diff --git a/source/field-monitor/field-connectivity/images/roboRIO-bang.png b/source/field-monitor/field-connectivity/images/roboRIO-bang.png new file mode 100644 index 0000000..7d20303 Binary files /dev/null and b/source/field-monitor/field-connectivity/images/roboRIO-bang.png differ diff --git a/source/field-monitor/live/live-monitor.rst b/source/field-monitor/live/live-monitor.rst index 17e6fe7..697b181 100644 --- a/source/field-monitor/live/live-monitor.rst +++ b/source/field-monitor/live/live-monitor.rst @@ -1,115 +1,124 @@ .. _field-monitor-live-simple: -Live Monitor -====================== +Field Monitor +============= -The Field Monitor provides a live view of robot and field status. To view the Field Monitor, access the web interface at 10.0.100.5 and select Field Monitor from the navigation bar. - -.. note:: - The images below show the previous version of the Live Field Monitor. While the conditions described are still accurate, the actual columns displayed on the "Simple" version of the monitor is different then depicted below. - - -Basic Layout ------------- +The Field Monitor provides a live view of robot and field status. To view the Field Monitor, access the web interface at 10.0.100.5 and select Field Monitor from the navigation bar. Use ctrl-b to swap the position of the red and blue field ends. .. image:: images/field-monitor-1.png -The Field Monitor program shows the same details as the Status tab available in Match Test and Match Play. - -The match number and match status are displayed across the top and bottom of the Field Monitor screen. Occasionally, the top and bottom status bars will not display the same information, such as when the text is too large for one line (it will show part of the status on each line). In the middle are details about each team. From left to right, the details on the Field Monitor are: - -* Player Station - The first number indicates the station, the second number is the team in that station. Example: Team #6 is in station Red 3 - - * Example: Team #6 is in station Red 3 - -DS - DS is in FMS mode (i.e. connected to FMS) when a green circle is shown. A green circle with a black X indicates that the computer is plugged in but the DS software is not linked (full FMS only). - -BWU - Indicates the Bandwidth Utilization/Consumption for that particular team +The Field Monitor shows match state and robot/driver station connectivity. The top row of the field monitor shows the match number and the match status. -Radio - Indicates that the DS is able to reach the radio on the robot +Driver station pane +------------------- -Rio - Indicates that the DS is able to reach the roboRIO on the robot +Each of the six driver stations has a pane that shows status for that station. In each pane, the first number indicates the station, +and the second number indicates the team assigned to that station. In the example above, team #4 is assigned to the Red 3 station. -Battery - Battery voltage reported by the Robot +Four symbols show the connectivity state of the station. -Status - The state and mode of the robot. “A” indicates Autonomous, “T” indicates Teleoperated. A red square means the robot is disabled; a green circle is shown when enabled. A black diamond with an “E” is shown for an e-stopped robot +====== =========== +Label Description +====== =========== +DS Driver Station connectivity. +Radio Robot radio connectivity. +RIO indicates whether the Driver Station is communicating with the roboRIO. +Robot indicates the current state of the robot. +====== =========== -Avg Trip - The average time required to send a message to the robot and have the robot respond (this is basically like a ping.) Units are in milliseconds. +:ref:`Status Indicators ` provides details on the meaning of the connectivity state symbols. -Packets - indicates the number of packets dropped in the DS-to-Robot link. Typically there are some lost packets. In a very tame wireless environment, this number will be less than 100. (Note: this number can “underflow” to ~65000 which does not indicate an issue) +When a robot is fully connected, the statistics section populates with useful metrics about the robot and its connectivity to the field. -Below are many potential Field Monitor states are shown (but not an exhaustive list) +============== =========== +Label Description +============== =========== +Trip Time The round trip time taken by an ICMP echo request (ping) from the driver station to the roboRIO, in milliseconds. +BWU Network bandwidth consumption between the driver station and robot, in megabits per second. +Missed Packets Count of ICMP echo requests (ping) that were not acknowledged by the roboRIO. +Battery Current voltage and lowest voltage reported by the roboRIO. +============== =========== Prior to Prestart ----------------- .. image:: images/field-monitor-1.png -Rows remain yellow until the DS and Robot have fully linked with FMS, at which point the row turns white. If the team is Bypassed, the row turns brown (see above). +No valid robot data is shown prior to prestart. It is normal to see TEAM MISMATCH prior to prestart, as the comparison is being +made to the teams from the previous match. Pre-Start Complete ------------------ .. image:: images/field-monitor-2.png -Team 1 has something plugged in, but not a DS (or DS software is not yet open). +Once prestart is completed, valid data is shown on the monitor. -Team 5 is actually plugged into Team 4's Driver Station, and so a yellow bar is shown on Team 4 that says "MOVE TO STATION 2" to identify that they need to move to station 2. The team's DS will also indicate that they are plugged into the incorrect spot and should move to the correct Driver Station. +Team 1 has a computer connected in to the driver station, but the Driver Station software is not running. + +Team 5 is connected to Team 4's Driver Station, indicated by the yellow bar "MOVE TO STATION 2". The team's driver station and the +display on the back of the team sign will also indicate that they should move to a different station. .. image:: images/field-monitor-3.png -In this example, the team in Station 4 has a team number that is not one expected in the match. Teams expected are 1,2,3,4,5,6, and the team number plugged into Station 4 is Team 8. So this team gets a yellow bar that says "TEAM MISMATCH". This can also happen when a team for the next match plugs in to a Player Station prior to a prestart. +The team in Station 4 has a team number that is not in the match. TEAM MISMATCH can also appear if the match has not been prestarted. Match Ready ----------- .. image:: images/field-monitor-4.png -Team 4 is Bypassed in this example. +The match is ready to start. Team 4 is Bypassed (will not run in this match). Match Running ------------- .. image:: images/field-monitor-5.png -Match Running (Estop and Disconnect) ------------------------------------- +All robots are running in autonomous mode. + +Match Running (e-stop and radio disconnect) +------------------------------------------- .. image:: images/field-monitor-6.png -In this example, team 4 has pressed their Estop, and team 1 has dropped robot communication (and Radio communication). +Robots are running in teleop mode. Team 4's robot has been e-stopped, either by the e-stop button in their station or by field staff. +Team 1's radio is not connected to the field access point. -Match Cancelled ---------------- +Match Aborted +------------- .. image:: images/field-monitor-7.png -Shown after a cancel match button is pressed, or the Arena Estop. It will return to "Ready for Prestart" promptly. +Indicates that a running match was stopped by field personnel. It will return to "Ready for Prestart" promptly. Match Over ---------- .. image:: images/field-monitor-8.png -All teams are dropped when the match finishes (in many cases, their DS would remain connected, hence the Yellow exclamation points) +The match ran to completion successfully. Robot radios are no longer connected. Driver station laptops are connected but there is +no longer communication with the driver station softare. +Special indicators +------------------ .. image:: images/field-monitor-10.png -In the above screenshot, blue station 1 has a white key icon next to the team number. This indicates that the team's WPA Key has not been used in a match yet. It may have been used in a connection test, but the icon indicates the key has not yet been used in a match. +In blue station 1, the white key icon indicates that the team has not yet participated in a match. -Additionally, red station 2 has a walkie-talkie icon next to the team number. This indicates that the robot radio connected to the field has a different MAC Address than the one used in their last match. This icon will never show for a team's first match as there is no previous MAC Address recorded by FMS. If the radio is removed from the robot and the radio with the previously used MAC Address is placed in the robot and connected to the field, the indicator will go away. +In red station 2, the walkie-talkie icon indicates that the robot radio's MAC address is new for this team. +This icon does not show for a team's first match. -Both of these icons will show as soon as the Robot Radio connects to the field and will stay on screen the entire time the radio is connected to the field, including throughout the entire match. - -Both of these icons will show on all screen sizes. +The robot radio must be connected for these icons to appear. +Responsive layout +----------------- .. image:: images/field-monitor-9.png :align: center -| -| On smaller resolution screens, the page will hide some information in favor of making the 4 main status indicators more easily visible. +On smaller resolution screens, the page will hide some information in favor of making the 4 main status indicators more easily visible. .. image:: images/field-monitor-mobile.png :align: center diff --git a/source/field-monitor/status-indicators/status-indicators.rst b/source/field-monitor/status-indicators/status-indicators.rst index 2389729..d3cbaba 100644 --- a/source/field-monitor/status-indicators/status-indicators.rst +++ b/source/field-monitor/status-indicators/status-indicators.rst @@ -3,8 +3,10 @@ Status Indicators ================= -Driver Station (DS) -------------------- +This page describes the status indicators on the :ref:`Field Monitor `. + +Driver Station +-------------- .. note:: For suggestions on resolving issues with the Driver Station computer and software, please go to the Driver Station Troubleshooting section of the :ref:`Connectivity Guide ` @@ -14,12 +16,12 @@ Indicator Explanation ======================================== =========== .. image:: images/yellow-x.png No device is detected. .. image:: images/yellow-exclamation.png A device is connected at the station, but FMS cannot communicate with the Driver Station software. -.. image:: images/white-check.png Device is connected with Driver Station software running and communicating with FMS. +.. image:: images/white-check.png A device is connected with Driver Station software running and correct team number assigned. ======================================== =========== -Radio ------ +Robot radio +----------- .. note:: For suggestions on resolving issues with the robot radio, please go to the Robot Troubleshooting section of the :ref:`Connectivity Guide ` @@ -27,26 +29,26 @@ Radio =================================== =========== Indicator Explanation =================================== =========== -.. image:: images/yellow-x.png No device is detected. -.. image:: images/yellow-laptop.png A radio is connected to the Robot Access Point, but cannot communicate with the Driver Station software. **NOTE**: The radio communicates with the Driver Station software through the Rio, so if the Rio is not connected this indicator will still show. -.. image:: images/radio-1-bar.png Radio is connected to the Robot Access Point, can communicate with the Driver Station software, and has poor connection quality. -.. image:: images/radio-2-bars.png Radio is connected to the Robot Access Point, can communicate with the Driver Station software, and has fair connection quality. -.. image:: images/radio-3-bars.png Radio is connected to the Robot Access Point, can communicate with the Driver Station software, and has good connection quality. -.. image:: images/radio-4-bars.png Radio is connected to the Robot Access Point, can communicate with the Driver Station software, and has excellent connection quality. +.. image:: images/yellow-x.png The radio is not connected to the Field Access Point. +.. image:: images/yellow-laptop.png The radio is connected to the Field Access Point, but cannot communicate with the Driver Station software. The radio communicates with the Driver Station software through the roboRIO, so if the roboRIO is not connected this indicator will still show. +.. image:: images/radio-1-bar.png The radio is connected to the Field Access Point, can communicate with the Driver Station software, and has poor connection quality. +.. image:: images/radio-2-bars.png The radio is connected to the Field Access Point, can communicate with the Driver Station software, and has fair connection quality. +.. image:: images/radio-3-bars.png The radio is connected to the Field Access Point, can communicate with the Driver Station software, and has good connection quality. +.. image:: images/radio-4-bars.png The radio is connected to the Field Access Point, can communicate with the Driver Station software, and has excellent connection quality. =================================== =========== -Rio +roboRIO --- .. note:: - For suggestions on resolving issues with the Rio, please go to the Robot Troubleshooting section of the :ref:`Connectivity Guide ` + For suggestions on resolving issues with the roboRIO, please go to the Robot Troubleshooting section of the :ref:`Connectivity Guide ` ======================================== =========== Indicator Explanation ======================================== =========== -.. image:: images/yellow-x.png No device is detected. -.. image:: images/yellow-exclamation.png Rio is powered on and responding to ping, but the code is likely not running. -.. image:: images/white-check.png Rio is powered on and responding to ping with code running. +.. image:: images/yellow-x.png roboRIO is not detected. +.. image:: images/yellow-exclamation.png roboRIO is detected, but no robot code is observed running. +.. image:: images/white-check.png roboRIO is detected, with robot code running. ======================================== =========== @@ -56,14 +58,14 @@ Robot Status ======================================== =========== Indicator Explanation ======================================== =========== -.. image:: images/white-square.png Robot Status not being displayed. Auto and Teleoperated status is hidden outside of the match and will show this indicator. **NOTE**: the E-Stop and A-Stop indicator will show outside of a match if the robot is in either of those states. -.. image:: images/yellow-x.png Robot Status is unknown -.. image:: images/black-e.png Robot is E-Stopped -.. image:: images/black-a.png Robot is A-Stopped -.. image:: images/yellow-a.png Robot is disabled in Auto mode -.. image:: images/yellow-t.png Robot is disabled in Teleoperated mode -.. image:: images/white-a.png Robot is enabled in Auto mode -.. image:: images/white-t.png Robot is enabled in Teleoperated mode +.. image:: images/yellow-x.png Robot Status is unknown. +.. image:: images/white-square.png Robot is ready, and is not e-stopped or a-stopped. +.. image:: images/black-e.png Robot is E-Stopped. +.. image:: images/black-a.png Robot is A-Stopped. +.. image:: images/yellow-a.png Robot is disabled in Auto mode. +.. image:: images/yellow-t.png Robot is disabled in Teleoperated mode. +.. image:: images/white-a.png Robot is enabled in Auto mode. +.. image:: images/white-t.png Robot is enabled in Teleoperated mode. ======================================== =========== @@ -73,8 +75,8 @@ Other Indicators ======================================== =========== Indicator Explanation ======================================== =========== -.. image:: images/radio.png The radio currently connected to the Robot Access Point has a different MAC Address than the one used by this team in their previous match. -.. image:: images/key.png The team's WPA key has not yet been used in a match. -.. image:: images/bypassed.png The robot has been bypassed by the Scorekeeper at the direction of the FTA. -.. image:: images/not-ready.png The robot is not fully connected and ready for match operation. **NOTE**: This indicator is driven by the same data that drives the Rio indicators. This is equivalent to the row background changing to yellow in the previous version of the Field Monitor. +.. image:: images/radio.png The radio currently connected to the Field Access Point has a different MAC address than the one used by this team in their previous match. +.. image:: images/key.png The team has not yet participated in a match (their WPA key has not been used). +.. image:: images/bypassed.png The robot has been bypassed by the Scorekeeper and will not run in this match. +.. image:: images/not-ready.png The robot is not fully connected and ready for match operation. This indicator is driven by the same data that drives the roboRIO indicators. ======================================== =========== \ No newline at end of file diff --git a/source/index.rst b/source/index.rst index 4e41692..782f41f 100644 --- a/source/index.rst +++ b/source/index.rst @@ -44,8 +44,9 @@ FMS Manual :caption: Field Monitor field-monitor/live/live-monitor - field-monitor/field-connectivity/connectivity-guide field-monitor/status-indicators/status-indicators + field-monitor/field-connectivity/connectivity-guide + .. toctree:: :maxdepth: 2