From acde02ec8f0324bb663b14e45925cba0a7c64c8f Mon Sep 17 00:00:00 2001 From: Miriam Sinton-Remes Date: Thu, 25 Jul 2024 22:23:19 -0400 Subject: [PATCH 1/3] Updated part of the Programming Resources to reflect the new nomenclature --- .../configuring-dual-hubs.rst | 4 +- .../configuring-external-webcam.rst | 8 +- .../getting_started/getting-started.rst | 12 +- .../saving_config/saving-config.rst | 2 +- .../Configuring-Your-Android-Devices.rst | 115 +++++++++--------- .../The-FTC-Control-System.rst | 17 ++- ...Laptop-to-the-Program-&-Manage-Network.rst | 4 +- .../required_materials/Required-Materials.rst | 28 ++--- .../Controlling-a-Servo-(Blocks).rst | 4 +- .../Writing-an-Op-Mode-with-FTC-Blocks.rst | 28 ++--- .../managing_opmodes/managing-opmodes.rst | 2 +- .../running_op_modes/Running-Your-Op-Mode.rst | 12 +- .../using_sensors/Using-Sensors-(Blocks).rst | 8 +- ...ng-and-Running-an-Op-Mode-(OnBot-Java).rst | 28 ++--- 14 files changed, 134 insertions(+), 138 deletions(-) diff --git a/docs/source/hardware_and_software_configuration/configuring/configuring_dual_hubs/configuring-dual-hubs.rst b/docs/source/hardware_and_software_configuration/configuring/configuring_dual_hubs/configuring-dual-hubs.rst index 9a1498b3..7db447b7 100644 --- a/docs/source/hardware_and_software_configuration/configuring/configuring_dual_hubs/configuring-dual-hubs.rst +++ b/docs/source/hardware_and_software_configuration/configuring/configuring_dual_hubs/configuring-dual-hubs.rst @@ -12,7 +12,7 @@ ports. This document describes how to connect and configure two Expansion Hubs for use in the FIRST Tech Challenge. Note that the FIRST Tech Challenge -Game Manual Part 1 (rule , part f) limits the maximum number of +Competition Manual limits the maximum number of Expansion Hubs on a single robot to two. **Important Note:** This document describes the process for setting up a @@ -82,7 +82,7 @@ first Expansion Hub before connecting the second Expansion Hub. With your first Expansion Hub connected to the 12V battery and to the Robot Controller, launch the Settings menu from the Robot Controller app (note you -can also do this from the Driver Station app, if the Driver Station is +can also do this from the Driver Station app, if the Operator Console is paired to the Robot Controller). 1. Select the Advanced Settings item to display the Advanced Settings menu. diff --git a/docs/source/hardware_and_software_configuration/configuring/configuring_external_webcam/configuring-external-webcam.rst b/docs/source/hardware_and_software_configuration/configuring/configuring_external_webcam/configuring-external-webcam.rst index 4b523cb9..16a43b00 100644 --- a/docs/source/hardware_and_software_configuration/configuring/configuring_external_webcam/configuring-external-webcam.rst +++ b/docs/source/hardware_and_software_configuration/configuring/configuring_external_webcam/configuring-external-webcam.rst @@ -50,7 +50,7 @@ Camera Configuration Before using the external camera, it must be added to the active configuration file as a USB-connected device. -Use the Configure Robot menu item on the paired Driver Station phone to +Use the Configure Robot menu item on the paired Operator Console phone to add the webcam as a USB-connected device to an existing or newly created configuration file. Note that the Scan operation for the Configure Robot activity should detect the webcam and give it a default name of “Webcam @@ -85,7 +85,7 @@ Image Preview The *FIRST* Tech Challenge apps provide camera preview for ‘stream-enabled’ Op Modes using Vuforia or TensorFlow Object Detection (TFOD). -On a paired Driver Station phone, with the camera connected and +On a paired Operator Console phone, with the camera connected and configured, select a stream-enabled Op Mode. Press the INIT button, and wait briefly for streaming software to initialize; do not press the START button. Instead open the main menu (the 3 dots in upper right hand @@ -95,7 +95,7 @@ for safety. .. image:: images/DS-webcam-preview-CH-1.jpg -The camera image will appear on the Driver Station screen. Manually +The camera image will appear on the Operator Console screen. Manually touch the image to refresh it. To preserve bandwidth, only one frame is sent at a time. @@ -117,7 +117,7 @@ command: .. image:: images/activateBeforeWaitForStart.jpg If you do not see the Camera Stream option in your main menu on your -Driver Station, then verify that the Vuforia function is activated +Operator Console, then verify that the Vuforia function is activated before the waitForStart command in your Op Mode. Also make sure you’ve given the system enough time to initialize the Vuforia software before you check to see if Camera Stream is available. diff --git a/docs/source/hardware_and_software_configuration/configuring/getting_started/getting-started.rst b/docs/source/hardware_and_software_configuration/configuring/getting_started/getting-started.rst index d68f0b91..501fbf69 100644 --- a/docs/source/hardware_and_software_configuration/configuring/getting_started/getting-started.rst +++ b/docs/source/hardware_and_software_configuration/configuring/getting_started/getting-started.rst @@ -17,7 +17,7 @@ Connecting an Android Smartphone to an Expansion Hub If you are using an Android smartphone as a Robot Controller, you must physically connect the Robot Controller smartphone to the Expansion Hub using a USB cable and an On-The-Go (OTG) adapter. Also, you should -verify that the Driver Station is currently paired to the Robot +verify that the Operator Console is currently paired to the Robot Controller. Connecting an Android Smartphone to an Expansion Hub Instructions @@ -80,19 +80,19 @@ Getting the Control Hub Ready If you are using a Control Hub, you do not need to make any additional connections. You simply need to make sure that the Control Hub is -powered on and paired to the Driver Station. +powered on and paired to the Operator Console. -Creating a Configuration File Using the Driver Station +Creating a Configuration File Using the Operator Console ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Although the configuration file needs to reside on the Robot Controller, -for this tutorial we will use the Driver Station app to create the -configuration file remotely. The Driver Station can be used to create a +for this tutorial we will use the Operator Console app to create the +configuration file remotely. The Operator Console can be used to create a configuration file for a Control Hub or for an Android smartphone Robot Controller. -Creating a Configuration File on the Robot Controller using the Driver Station Instructions +Creating a Configuration File on the Robot Controller using the Operator Console Instructions ------------------------------------------------------------------------------------------- 1. Touch the three vertical dots in the upper right hand corner of diff --git a/docs/source/hardware_and_software_configuration/configuring/saving_config/saving-config.rst b/docs/source/hardware_and_software_configuration/configuring/saving_config/saving-config.rst index c1591dbf..7645ba87 100644 --- a/docs/source/hardware_and_software_configuration/configuring/saving_config/saving-config.rst +++ b/docs/source/hardware_and_software_configuration/configuring/saving_config/saving-config.rst @@ -56,7 +56,7 @@ back-arrow button to return to the main screen of the app. | 7. Verify that the configuration file is the active configuration -file on the main Driver Station screen. +file on the main Operator Console screen. .. image:: images/SavingConfigurationInformationNewStep7.jpg :align: center diff --git a/docs/source/programming_resources/shared/configuring_android/Configuring-Your-Android-Devices.rst b/docs/source/programming_resources/shared/configuring_android/Configuring-Your-Android-Devices.rst index daca6217..29df454f 100644 --- a/docs/source/programming_resources/shared/configuring_android/Configuring-Your-Android-Devices.rst +++ b/docs/source/programming_resources/shared/configuring_android/Configuring-Your-Android-Devices.rst @@ -8,18 +8,17 @@ Control Hub Configuration ^^^^^^^^^^^^^^^^^^^^^^^^^ .. note:: - References to the Driver Station smartphone may instead apply to the + References to the Operator Console smartphone may instead apply to the `REV Driver Hub `__, which is preloaded with the Driver Station (DS) app. Teams who are using a Control Hub (which has an integrated Android Device) -will only need to configure a single smartphone for use as a Driver -Station. The process is as follows: +will only need to configure a single smartphone for use as a Operator Console. The process is as follows: * Rename the smartphone to "-DS" (where is replaced by your team number). -* Install the Driver Station (DS) app onto the Driver Station phone. (The DS app is pre-installed on the REV Driver Hub.) +* Install the Driver Station (DS) app onto the Operator Console phone. (The DS app is pre-installed on the REV Driver Hub.) * Put your phone into Airplane Mode (with the WiFi radio still on). -* Pair (i.e., wirelessly connect) the Driver Station to the Control Hub. +* Pair (i.e., wirelessly connect) the Operator Console to the Control Hub. .. image:: images/ControlHubAndPhone.jpg :align: center @@ -27,7 +26,7 @@ Station. The process is as follows: | .. important:: Eventually the Control Hub will need be renamed so - that its name complies with Game Manual rule , but for now we will + that its name complies with the Competition Manual, but for now we will use the Control Hub with its default name. You can learn how to manage a Control Hub (and modify its name, password, etc.) in :doc:`this tutorial <../managing_control_hub/Managing-a-Control-Hub>`. @@ -37,14 +36,14 @@ Two Android Smartphone Configuration Teams who have two smartphones and are not using a Control Hub will need to configure one smartphone for use as a Robot Controller and a second -smartphone for use as a Driver Station. The process is as follows, +smartphone for use as an Operator Console. The process is as follows, * Rename one smartphone to "-RC" (replace with your team number). * Install the Robot Controller app onto the Robot Controller phone. * Rename a second smartphone to "-DS" (where is replaced by your team number). -* Install the Driver Station app onto the Driver Station phone. (The DS app is pre-installed on the REV Driver Hub.) +* Install the Driver Station app onto the Operator Console phone. (The DS app is pre-installed on the REV Driver Hub.) * Put your phones into Airplane Mode (with the WiFi radios still on). -* Pair (i.e., wirelessly connect) the Driver Station to the Robot Controller. +* Pair (i.e., wirelessly connect) the Operator Console to the Robot Controller. .. image:: images/twoAndroidPhones.jpg :align: center @@ -58,14 +57,13 @@ Renaming Your Smartphones The official rules of the FIRST Tech Challenge (see ) require that you change the Wi-Fi name of your smartphones to include your team -number and "-RC" if the phone is a Robot Controller or "-DS" if it is a -Driver Station. A team can insert an additional dash and a letter ("A", +number and "-RC" if the phone is a Robot Controller or "-DS" if it is an Operator Console. A team can insert an additional dash and a letter ("A", "B", "C", etc.) if the team has more than one set of Android phones. If, for example, a team has a team number of 9999 and the team has multiple sets of phones, the team might decide to name one phone "9999-C-RC" for the Robot Controller and the other phone "9999-C-DS" for -the Driver Station. The "-C" indicates that these devices belong to the +the Operator Console. The "-C" indicates that these devices belong to the third set of phones for this team. The name of a Robot Controller phone can be changed in the RC app, using @@ -73,7 +71,7 @@ instructions :ref:`found here `. @@ -101,28 +99,28 @@ level, as described below. * - Step - Image - * - 1. Browse the list of available apps on thesmartphone and locate the **Settings** icon.Click on **Settings** icon to display theSettings screen. + * - 1. Browse the list of available apps on the smartphone and locate the **Settings** icon. Click on **Settings** icon to display the Settings screen. - |rename1| - * - 2. Click on **Wi-Fi** to launch the Wi-Fiscreen. + * - 2. Click on **Wi-Fi** to launch the Wi-Fi screen. - |rename2| - * - 3. Touch the three vertical dots to display apop-up menu. + * - 3. Touch the three vertical dots to display a pop-up menu. - |rename3| * - 4. Select **Advanced** from the pop-up menu. - |rename4| - * - 5. Select **Wi-Fi Direct** from the **AdvancedWi-Fi** screen. + * - 5. Select **Wi-Fi Direct** from the **Advanced Wi-Fi** screen. - |rename5| - * - 6. Touch the three vertical dots to display apop-up menu. + * - 6. Touch the three vertical dots to display a pop-up menu. - |rename6| - * - 7. Select **Configure Device** from the pop-upmenu. + * - 7. Select **Configure Device** from the pop-up menu. - |rename7| - * - 8. Use touch pad to enter new name of device.If the device will be a Robot Controller,specify your team number and -RC. If thedevice will bea Driver Station, specify yourteam number and -DS. You can also set theWi-Fi Direct inactivity timeout to *Neverdisconnect* and then hit the\ **SAVE** buttonto save your changes. Note that in thescreenshot shown to the right, the team numberis 9999. The "-C" indicates that this is fromthe third pair of smartphones forthis team.The -RC indicates that this phonewill be aRobot Controller. + * - 8. Use touch pad to enter new name of device. If the device will be a Robot Controller, specify your team number and -RC. If thedevice will be an Operator Console, specify your team number and -DS. You can also set the Wi-Fi Direct inactivity timeout to *Never disconnect* and then hit the\ **SAVE** button to save your changes. Note that in the screenshot shown to the right, the team number is 9999. The "-C" indicates that this is from the third pair of smartphones for this team. The -RC indicates that this phone will be a Robot Controller. - |rename8| * - 9. After renaming phone, power cycle thedevice. @@ -199,13 +197,13 @@ follows: * - 1. Go to "Settings", then tap "About device"or "About phone". - |devop1| - * - 2. Scroll down, then tap Build number seventimes.Depending on your device and operatingsystem, you may need to tap Softwareinformation, then tap Build number seventimes. + * - 2. Scroll down, then tap Build number seven times. Depending on your device and operating system, you may need to tap Software information, then tap Build number seven times. - |devop2a| |devop2b| - * - 3. Enter your pattern, PIN or password toenable the Developer options menu. + * - 3. Enter your pattern, PIN or password to enable the Developer options menu. - - * - 4. The "Developer options" menu will nowappear in your Settings menu. Depending onyour device, it may appear under Settings >General > Developer options. + * - 4. The "Developer options" menu will now appear in your Settings menu. Depending on your device, it may appear under Settings >General > Developer options. - |devop4| * - 5. To disable the Developer options at anytime, tap the switch. @@ -216,7 +214,7 @@ Placing Phones into Airplane Mode with Wi-Fi On ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For the FIRST Tech Challenge competitions, it is important that you -place your Robot Controller and Driver Station phones into Airplane mode +place your Robot Controller and Operator Console phones into Airplane mode but keep their Wi-Fi radios turned on. This is important because you do not want any of the cellular telephone functions to be enabled during a match. The cellular telephone functions could disrupt the function of @@ -237,14 +235,14 @@ the robot during a match. * - Step - Image - * - 1. On the main Android screen of eachsmartphone, use your finger to slide from thetop of the screen down towards the bottom ofthe screen to display the quick configurationscreen.Note that for some smartphones youmight have to swipe down more than once todisplay the quick configuration screen,particularly if there are messages ornotifications displayed at the top of yourscreen.Look for the Airplane mode icon (whichis shaped like an airplane) and if the icon isnot activated, touch the icon to put the phoneinto airplane mode. + * - 1. On the main Android screen of each smartphone, use your finger to slide from the top of the screen down towards the bottom ofthe screen to display the quick configuration screen. Note that for some smartphones you might have to swipe down more than once to display the quick configuration screen, particularly if there are messages or notifications displayed at the top of your screen. Look for the Airplane mode icon (which is shaped like an airplane) and if the icon is not activated, touch the icon to put the phone into airplane mode. - |airplane1| - * - 2. Placing the phone into airplane mode willturn off the Wi-Fi radio. If the Wi-Fi iconhas a diagonal line through it (see Step 1above), then the Wi-Fi radio is disabled. Youwill need to touch the **Wi-Fi** icon on thequick configuration screen to turn the Wi-Firadio back on. + * - 2. Placing the phone into airplane mode will turn off the Wi-Fi radio. If the Wi-Fi icon has a diagonal line through it (see Step 1 above), then the Wi-Fi radio is disabled. You will need to touch the **Wi-Fi** icon on the quick configuration screen to turn the Wi-Fi radio back on. - |airplane2| -Pairing the Driver Station to the Robot Controller +Pairing the Operator Console to the Robot Controller ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. _control-hub-users-1: @@ -255,11 +253,11 @@ Control Hub Pairing The REV Robotics Control Hub should come with the Robot Controller app pre-installed. Once you have successfully installed the Driver Station on an Android phone, you will want to establish a secure -wireless connection between the Control Hub and the Driver Station. This -connection will allow your Driver Station phone to select op modes on +wireless connection between the Control Hub and the Operator Console. This +connection will allow your Operator Console phone to select op modes on your Robot Controller and send gamepad input to these programs. Likewise, it will allow your op modes running on your Robot Controller -to send telemetry data to your Driver Station phone where it can be +to send telemetry data to your Operator Console phone where it can be displayed for your drivers. The process to connect the two devices is known as "pairing." @@ -294,43 +292,43 @@ task. * - Step - Image - * - 1. Connect an approved 12V battery to thepower switch (REV-31-1387) and make sure theswitch is in the off position. Connect theswitch to an XT30 port on the Control Hub andturn the switch on. The LED should initiallybe blue on the Control Hub. + * - 1. Connect an approved 12V battery to the power switch (REV-31-1387) and make sure the switch is in the off position. Connect the switch to an XT30 port on the Control Hub and turn the switch on. The LED should initially be blue on the Control Hub. - |pairing1| - * - 2. It takes approximately 18 seconds for theControl Hub to power on. The Control Hub isready to pair with the Driver Station when theLED turns green. Note: the light blinks blueevery ~5 seconds to indicate that the ControlHub is healthy. + * - 2. It takes approximately 18 seconds for the Control Hub to power on. The Control Hub is ready to pair with the Driver Station when the LED turns green. Note: the light blinks blue every ~5 seconds to indicate that the Control Hub is healthy. - |pairing2| - * - 3. On the Driver Station device, browse theavailable apps and locate the **DriverStation** icon. Tap on the icon to launch theDriver Station app. Note that the first timeyou launch the app your Android device mightprompt you for permissions that the app willneed to run properly. Whenever prompted, press**Allow** to grant the requested permission. + * - 3. On the Driver Station device, browse the available apps and locate the ** FTC Driver Station** icon. Tap on the icon to launch the Driver Station app. Note that the first time you launch the app your Android device might prompt you for permissions that the app will need to run properly. Whenever prompted, press **Allow** to grant the requested permission. - |pairing3| - * - 4. Touch the three vertical dots on the upperright hand corner of the main screen of theDriver Station app. This will launch apop-up menu. + * - 4. Touch the three vertical dots on the upper right hand corner of the main screen of the Driver Station app. This will launch a pop-up menu. - |pairing4| * - 5. Select **Settings** from the pop-up menu. - |pairing5| - * - 6. From the **Settings** screen, look for andselect \ **Pairing Method** to launch the**Pairing** \ **Method** screen. + * - 6. From the **Settings** screen, look for and select \ **Pairing Method** to launch the **Pairing** \ **Method** screen. - |pairing6| - * - 7. Touch the words **Control Hub** to indicatethat this Driver Station will be pairing witha Control Hub. + * - 7. Touch the words **Control Hub** to indicate that this Operator Console will be pairing with a Control Hub. - |pairing7| - * - 8. From the **Settings** screen, look for andselect \ **Pair with Robot Controller** tolaunch the **Pair** \ **with RobotController** screen. + * - 8. From the **Settings** screen, look for and select \ **Pair with Robot Controller** to launch the **Pair** \ **with Robot Controller** screen. - |pairing8| * - 9. From **Pair with Robot Controller** screen,look for and press the **Wifi Settings** button to launch the device's Android WifiSettings screen. - |pairing9| - * - 10. Find the name of your Control Hub'swireless network from the list of availableWiFi networks. Click on the network name toselect the network. If this is the first timeyou are connecting to the Control Hub, thenthe default network name should begin with theprefix FTC- (FTC-1Ybr in this example).The default network name should be listed on asticker attached to the bottom side of theControl Hub. + * - 10. Find the name of your Control Hub's wireless network from the list of available WiFi networks. Click on the network name to select the network. If this is the first time you are connecting to the Control Hub, then the default network name should begin with the prefix FTC- (FTC-1Ybr in this example). The default network name should be listed on a sticker attached to the bottom side of the Control Hub. - |pairing10| - * - 11. When prompted, specify the password forthe Control Hub's WiFi network and press\ **Connect** to connect to the Hub. Note thatthe default password for the Control Hubnetwork is password. Also note that when youconnect to the Control Hub's WiFi networksuccessfully, the Driver Station will not haveaccess to the Internet. + * - 11. When prompted, specify the password for the Control Hub's WiFi network and press \ **Connect** to connect to the Hub. Note that the default password for the Control Hub network is ``password``. Also note that when you connect to the Control Hub's WiFi network successfully, the Operator Console will not have access to the Internet. - |pairing11| - * - 12. After you successfully connected to theHub, use the back arrow to navigate to theprevious screen. You should see the name ofthe WiFi network listed under "Current RobotController:". Use the back-arrow key to returnto the Settings screen. Then press theback-arrow key one more time to return to themain Driver Station screen. + * - 12. After you successfully connected to the Hub, use the back arrow to navigate to theprevious screen. You should see the name of the WiFi network listed under "Current Robot Controller:". Use the back-arrow key to return to the Settings screen. Then press the back-arrow key one more time to return to the main Operator Console screen. - |pairing12| - * - 13. Verify that the Driver Station screen haschanged and that it now indicates that it isconnected to the Control Hub.The name of theControl Hub's WiFi network (FTC-1Ybr in thisexample) should be displayed in the Networkfield on the Driver Station. + * - 13. Verify that the Operator Console screen has changed and that it now indicates that it is connected to the Control Hub. The name of the Control Hub's WiFi network (FTC-1Ybr in this example) should be displayed in the Network field on the Driver Station. - |pairing13| @@ -339,22 +337,21 @@ task. Two Android Smartphone Pairing ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -.. important:: If your Driver Station was previously paired to a +.. important:: If your Operator Console was previously paired to a Control Hub, and you currently would like to connect to an Android smartphone Robot Controller, then before attempting to pair to the Robot Controller, you should forget the Wi-Fi network for the previous Control - Hub (using the Android Wifi Settings screen on the Driver Station) and - then power cycle the Driver Station phone. If the previous Control Hub - is powered on and if you haven't forgotten this network, then the Driver - Station might try and connect to the Control Hub and might be unable to + Hub (using the Android Wifi Settings screen on the Operator Console) and + then power cycle the Operator Console phone. If the previous Control Hub + is powered on and if you haven't forgotten this network, then the Operator Console might try and connect to the Control Hub and might be unable to connect to the Robot Controller smartphone. Once you have successfully installed the apps onto your Android phones, you will want to establish a secure wireless connection between -the two devices. This connection will allow your Driver Station phone to +the two devices. This connection will allow your Operator Console phone to select op modes on your Robot Controller phone and send gamepad input to these programs. Likewise, it will allow your op modes running on your -Robot Controller phone to send telemetry data to your Driver Station +Robot Controller phone to send telemetry data to your Operator Console phone where it can be displayed for your drivers. The process to connect the two phones is known as pairing. @@ -384,38 +381,38 @@ Note that it will take an estimated 10 minutes to complete this task. * - Step - Image - * - 1. On the Robot Controller device, browse theavailable apps and locate the **RobotController** icon. Tap on the icon to launchthe Robot Controller app. Note that the firsttime you launch the app your Android devicemight prompt you for permissions that the appwill need to run properly. Whenever prompted,press **Allow** to grant the requestedpermission. + * - 1. On the Robot Controller device, browse the available apps and locate the **FTC Robot Controller** icon. Tap on the icon to launch the Robot Controller app. Note that the first time you launch the app your Android device might prompt you for permissions that the app will need to run properly. Whenever prompted, press **Allow** to grant the requested permission. - |pairingns1| |pairingns1b| - * - 2. Verify that the Robot Controller app isrunning. The **Robot Status** field shouldread running if it is working properly. + * - 2. Verify that the Robot Controller app is running. The **Robot Status** field should read running if it is working properly. - |pairingns2| - * - 3. On the Driver Station device, browse theavailable apps and locate the **DriverStation** icon. Tap on the icon to launch theDriver Station app. Note that the first timeyou launch the app your Android device mightprompt you for permissions that the app willneed to run properly. Whenever prompted, press**Allow** to grant the requested permission. + * - 3. On the Operator Console device, browse the available apps and locate the **FTC Driver Station** icon. Tap on the icon to launch the Driver Station app. Note that the first time you launch the app your Android device might prompt you for permissions that the app will need to run properly. Whenever prompted, press **Allow** to grant the requested permission. - |pairingns3| |pairingns3b| - * - 4. Touch the three vertical dots on the upperright hand corner of the main screen of theDriver Station app. This will launch apop-up menu. + * - 4. Touch the three vertical dots on the upper right hand corner of the main screen of the Driver Station app. This will launch a pop-up menu. - |pairingns4| * - 5. Select **Settings** from the pop-up menu. - |pairingns5| - * - 6. From the **Settings** screen, look for andselect \ **Pairing Method** to launch the**Pairing** \ **Method** screen. + * - 6. From the **Settings** screen, look for and select \ **Pairing Method** to launch the **Pairing** \ **Method** screen. - |pairingns6| - * - 7. Verify that the **Wifi Direct** mode isselected, which means that this Driver Stationwill be pairing with another Android device. + * - 7. Verify that the **Wifi Direct** mode is selected, which means that this Operator Console will be pairing with another Android device. - |pairingns7| - * - 8. From the **Settings** screen, look for andselect \ **Pair with Robot Controller** tolaunch the **Pair**\ \ **with RobotController** screen. + * - 8. From the **Settings** screen, look for and select \ **Pair with Robot Controller** to launch the **Pair** \ \ **with Robot Controller** screen. - |pairingns8| - * - 9. Find the name of your Robot Controller fromthe list and select it.After you have madeyour selection, use the back-arrow key toreturn to the Settings screen.Then press theback-arrow key one more time to return to themain Driver Station screen. + * - 9. Find the name of your Robot Controller from the list and select it. After you have made your selection, use the back-arrow key to return to the Settings screen. Then press the back-arrow key one more time to return to the main Operator Console screen. - |pairingns9| - * - 10. When the Driver Station returns to itsmain screen, the first time you attempt toconnect to the Robot Controller a promptshould appear on the Robot Controllerscreen.Click on the **ACCEPT** button toaccept the connection request from the DriverStation. + * - 10. When the Operator Console returns to its main screen, the first time you attempt to connect to the Robot Controller a prompt should appear on the Robot Controller screen. Click on the **ACCEPT** button to accept the connection request from the Operator Console. - |pairingns10| - * - 11. Verify that the Driver Station screen haschanged and that it now indicates that it isconnected to the Robot Controller.The name ofthe Robot Controller's remote network(9999-C-RC in this example) should bedisplayed in the Network field on the DriverStation. + * - 11. Verify that the Operator Console screen has changed and that it now indicates that it is connected to the Robot Controller. The name ofthe Robot Controller's remote network (9999-C-RC in this example) should be displayed in the Network field on the Operator Console. - |pairingns11| - * - 12. Verify that the Robot Controller screenhas changed and that it now indicates that itis connected to the Driver Station.The Networkstatus should read active, connected on theRobot Controller's main screen. + * - 12. Verify that the Robot Controller screen has changed and that it now indicates that it is connected to the Operator Console.The Network status should read active, connected on the Robot Controller's main screen. - |pairingns12| \ No newline at end of file diff --git a/docs/source/programming_resources/shared/control_system_intro/The-FTC-Control-System.rst b/docs/source/programming_resources/shared/control_system_intro/The-FTC-Control-System.rst index 90e742a4..901e338a 100644 --- a/docs/source/programming_resources/shared/control_system_intro/The-FTC-Control-System.rst +++ b/docs/source/programming_resources/shared/control_system_intro/The-FTC-Control-System.rst @@ -19,13 +19,13 @@ robot can complete, the more points a team will earn. (Photo courtesy of Dan Donovan, ©2017 Dan Donovan / www.dandonovan.com) -Autonomous vs. Driver-Controlled +AUTO vs. TELEOP ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -A *FIRST* Tech Challenge match has an *autonomous* phase and a -*driver-controlled* or *“tele-operated”* phase. In the autonomous phase +A *FIRST* Tech Challenge match has an AUTO phase and a +TELEOP phase. In the AUTO phase of a match the robot operates without any human input or control. In the -driver-controlled phase, the robot can receive input from up to two +TELEOP phase, the robot can receive input from up to two human drivers. Point-to-Point Control System @@ -47,12 +47,11 @@ There are two hardware options currently being used: REV Robotics Expansion Hub or the REV Robotics Control Hub. A second Android device sits with the team drivers and has one or two -gamepads connected. This second device is known as the *Driver Station*. -The Driver Station is sort of like a remote control that you might use -to control your television. The Driver Station allows a team to +gamepads connected. This second device is known as the *Operator Console*. +The Operator Console is sort of like a remote control that you might use +to control your television. The Operator Console allows a team to communicate remotely (using a secure, wireless connection) to the Robot -Controller and to issue commands to the Robot Controller. The Driver -Station consists of an Android device running an Driver Station app. +Controller and to issue commands to the Robot Controller. The Operator Console consists of an Android device running an Driver Station app. REV Robotics Expansion Hub ~~~~~~~~~~~~~~~~~~~~~~~~~~ diff --git a/docs/source/programming_resources/shared/program_and_manage_network/Connecting-a-Laptop-to-the-Program-&-Manage-Network.rst b/docs/source/programming_resources/shared/program_and_manage_network/Connecting-a-Laptop-to-the-Program-&-Manage-Network.rst index b1fb4ad4..7399f1b2 100644 --- a/docs/source/programming_resources/shared/program_and_manage_network/Connecting-a-Laptop-to-the-Program-&-Manage-Network.rst +++ b/docs/source/programming_resources/shared/program_and_manage_network/Connecting-a-Laptop-to-the-Program-&-Manage-Network.rst @@ -19,7 +19,7 @@ documentation for details on how to connect to a Wi-Fi network. Connecting Your Laptop to the Program & Manage Network Instructions ------------------------------------------------------------------- -1. On the Driver Station, touch the three dots in the upper right +1. On the Operator Console, touch the three dots in the upper right hand corner of the screen to launch the pop-up menu. Select **Program & Manage** from the pop-up menu to display the **Program & Manage** access information. @@ -129,7 +129,7 @@ available networks, or, if you are having problems connecting your laptop to the Program & Manage wireless network, make sure you answer the following questions: -1. Is the Robot Controller running and connected to the Driver Station? +1. Is the Robot Controller running and connected to the Operator Console? 2. Is your Windows laptop updated with the most current system updates and service packs? Older versions of Windows 8 and 10, for example, had issues that could prevent the laptop from displaying the Program diff --git a/docs/source/programming_resources/shared/required_materials/Required-Materials.rst b/docs/source/programming_resources/shared/required_materials/Required-Materials.rst index 75c41fbe..c24b3ef6 100644 --- a/docs/source/programming_resources/shared/required_materials/Required-Materials.rst +++ b/docs/source/programming_resources/shared/required_materials/Required-Materials.rst @@ -47,49 +47,49 @@ tutorials, you will need to have the following materials available: * - Required Item(s) - Image - * - Two (2) FIRST-approved* Android devices OR One (1) Control Hub and one (1) FIRSTapproved* Android device for the Driver Station + * - Two (2) FIRST-approved* Android devices OR One (1) Control Hub and one (1) FIRST-approved* Android device for the Operator Console - |androidphones| Or |chandphones| * - Wireless Internet access. - |wifi| - * - Laptop with Microsoft Windows 7, 8 or 10 andWi-Fi capability.Note that your laptop shouldhave the most current service packs and systemupdates from Microsoft.If you are using adifferent type of machine (such as aChromebook, Android Tablet, etc.) as yourprogramming device, the steps might differslightly on how to access the ProgrammingServer on the Robot Controller. Refer to yourdevice’s user documentation for details on howto connect to a Wi-Fi network. + * - Laptop with Microsoft Windows 7, 8 or 10 and Wi-Fi capability. Note that your laptop should have the most current service packs and systemu pdates from Microsoft. If you are using a different type of machine (such as a Chromebook, Android Tablet, etc.) as your programming device, the steps might differ slightly on how to access the Programming Server on the Robot Controller. Refer to your device’s user documentation for details on howto connect to a Wi-Fi network. - |laptop| - * - Javascript-enabled web browser (Google Chromeis the recommended browser). + * - Javascript-enabled web browser (Google Chrome is the recommended browser). - |chrome| - * - If you are using a smartphone as part of yourRobot Controller, you will also need a REVRobotics Expansion Hub (REV-31-1153) toconnect to the motors, servos, and sensors.Control Hub users will use the integratedports built into the Control Hub to connectmotors, servos, and sensors. + * - If you are using a smartphone as part of your Robot Controller, you will also need a REV Robotics Expansion Hub (REV-31-1153) to connect to the motors, servos, and sensors. Control Hub users will use the integrated ports built into the Control Hub to connect motors, servos, and sensors. - |exhub| - * - REV Robotics Switch, Cable, & Bracket(REV-31-1387). + * - REV Robotics Switch, Cable, & Bracket (REV-31-1387). - |switch| - * - If you are using an approved 12V battery thathas an Tamiya connector (like the TetrixW39057 battery) you will need a >REV RoboticsTamiya to XT30 Adapter Cable (REV-31-1382). Ifyou have a REV Robotics Slim Battery(REV-31-1302) then you will not need thisadapter since the REV battery already has anXT30 connector. + * - If you are using an approved 12V battery that has a Tamiya connector (like the Tetrix W39057 battery) you will need a >REV Robotics Tamiya to XT30 Adapter Cable (REV-31-1382). Ifyou have a REV Robotics Slim Battery (REV-31-1302) then you will not need this adapter since the REV battery already has an XT30 connector. - |tamiya| - * - *FIRST*-approved\* 12V Battery (such as TetrixW39057 or REV Robotics REV-31-1302).\*\ **Fora list of FIRST-approved 12V batteries, referto the current Game Manual Part 1, rule.**\ + * - *FIRST*-approved\* 12V Battery (such as Tetrix W39057 or REV Robotics REV-31-1302).\*\ **Fora list of FIRST-approved 12V batteries, refer to the current Competition Manual.**\ - |battery| Or |slimbattery| - * - *FIRST*-approved\* 12V DC Motor (such asTetrix W39530, with power cable W41352).\*\ **For a list of FIRST-approved 12V motors,refer to the current Game Manual Part 1,rule .**\ + * - *FIRST*-approved\* 12V DC Motor (such as Tetrix W39530, with power cable W41352).\*\ **For a list of FIRST-approved 12V motors,refer to the current Competition Manual.**\ - |motor| - * - REV Robotics Anderson to JST VH Cable(REV-31-1381). + * - REV Robotics Anderson to JST VH Cable (REV-31-1381). - |jst| - * - 180-Degree Standard Scale Servo (such as HitecHS-485HB). + * - 180-Degree Standard Scale Servo (such as Hitec HS-485HB). - |servo| - * - REV Robotics Color Sensor with 4-Pin Cable(REV-31-1154). + * - REV Robotics Color Sensor with 4-Pin Cable (REV-31-1154). - |color| - * - REV Robotics Touch Sensor with 4-Pin Cable(REV-31-1425). + * - REV Robotics Touch Sensor with 4-Pin Cable( REV-31-1425). - |touch| - * - If you are using a smartphone as your RobotController, you will need a USB Type A male totype mini-B male cable. Control Hub users donot need this cable. + * - If you are using a smartphone as your Robot Controller, you will need a USB Type A male to type mini-B male cable. Control Hub users donot need this cable. - |usba| - * - If you are using a smartphone as your RobotController, you will need two (2) micro USBOTG adapters. If you are using a Control Hubas your Robot Controller, you will need one(1) micro USB OTG adapter. + * - If you are using a smartphone as your Robot Controller, you will need two (2) micro USB OTG adapters. If you are using a Control Hub as your Robot Controller, you will need one(1) micro USB OTG adapter. - |otg| |otg| * - Logitech F310 USB Gamepad. diff --git a/docs/source/programming_resources/tutorial_specific/blocks/controlling_a_servo/Controlling-a-Servo-(Blocks).rst b/docs/source/programming_resources/tutorial_specific/blocks/controlling_a_servo/Controlling-a-Servo-(Blocks).rst index caf4505b..ec0d3065 100644 --- a/docs/source/programming_resources/tutorial_specific/blocks/controlling_a_servo/Controlling-a-Servo-(Blocks).rst +++ b/docs/source/programming_resources/tutorial_specific/blocks/controlling_a_servo/Controlling-a-Servo-(Blocks).rst @@ -286,7 +286,7 @@ field. | - This set of blocks will send the current servo position value to the Driver Station while the op mode is running. + This set of blocks will send the current servo position value to the Operator Console while the op mode is running. 25. Save your op mode and verify that it was saved successfully to the Robot Controller. @@ -306,6 +306,6 @@ designated as User #1 before running your op mode. | - You should now be able to control the servo position with the colored buttons. The servo position should be displayed on the Driver Station. + You should now be able to control the servo position with the colored buttons. The servo position should be displayed on the Operator Console. diff --git a/docs/source/programming_resources/tutorial_specific/blocks/creating_op_modes/Writing-an-Op-Mode-with-FTC-Blocks.rst b/docs/source/programming_resources/tutorial_specific/blocks/creating_op_modes/Writing-an-Op-Mode-with-FTC-Blocks.rst index 76e917fa..712cc51f 100644 --- a/docs/source/programming_resources/tutorial_specific/blocks/creating_op_modes/Writing-an-Op-Mode-with-FTC-Blocks.rst +++ b/docs/source/programming_resources/tutorial_specific/blocks/creating_op_modes/Writing-an-Op-Mode-with-FTC-Blocks.rst @@ -11,7 +11,7 @@ want their robot to follow a white line on the competition floor and then score a game element into a goal autonomously during a match. Teams write programs called *op modes* (which stands for "operational modes") to specify the behavior for their robot. These op modes run on the Robot -Controller after being selected on the Driver Station. +Controller after being selected on the Operator Console. Teams who are participating in the *FIRST* Tech Challenge have a variety of programming tools that they can use to create their own op modes. @@ -166,7 +166,7 @@ you create. They create the basic structure for your op mode. In the figure shown above, the main body of the op mode is defined by the outer purple bracket that has the words "to runOpMode" at the top. As the help tip indicates, this function is executed when this op mode -("MyFIRSTOpMode" in this example) is selected from the Driver Station. +("MyFIRSTOpMode" in this example) is selected from the Operator Console. It can be helpful to think of an op mode as a list of tasks for the Robot Controller to perform. The Robot Controller will process this list @@ -198,12 +198,12 @@ human user. The robot will ignore any comments in an op mode. Any programming blocks that are placed after the "Put initialization blocks here" comment (and before the "call MyFIRSTOpMode.waitForStart" block) will be executed when the op mode is first selected by a user at -the Driver Station. +the Operator Console. When the Robot Controller reaches the block labeled "call MyFIRSTOpMode.waitForStart" it will stop and wait until it receives a -Start command from the Driver Station. A Start command will not be sent -until the user pushes the Start button on the Driver Station. Any code +Start command from the Operator Console. A Start command will not be sent +until the user pushes the Start button on the Operator Console. Any code after the "call MyFIRSTOpMode.waitForStart" block will get executed after the Start button has been pressed. @@ -396,11 +396,11 @@ Inserting Telemetry Statements Your op mode is just about ready to run. However, before continuing, you will add a couple of telemetry statements that will send information -from the Robot Controller to the Driver Station for display on the -Driver Station user interface. This telemetry mechanism is a useful way -to display status information from the robot on the Driver Station. You +from the Robot Controller to the Operator Console for display on the +Operator Console user interface. This telemetry mechanism is a useful way +to display status information from the robot on the Operator Console. You can use this mechanism to display sensor data, motor status, gamepad -state, etc. from the Robot Controller to the Driver Station. +state, etc. from the Robot Controller to the Operator Console. Note that you will need an estimated 15 minutes to complete this task. @@ -425,7 +425,7 @@ below the "set motor1.Power to" block. Click on the green text block | - Note that the "call telemetry.update" block is an important block. Data that is added to the telemetry buffer will not be sent to the Driver Station until the "telemetry.update" method is called. + Note that the "call telemetry.update" block is an important block. Data that is added to the telemetry buffer will not be sent to the Operator Console until the "telemetry.update" method is called. 3. Click on the "Variables" block category and select the "tgtPower" block. Drag the block so it clicks into place next to the "number" @@ -436,7 +436,7 @@ parameter on the telemetry programming block. | - The Robot Controller will send the value of the variable tgtPower to the Driver Station with a key or label of "Target Power". The key will be displayed to the left of the value on the Driver Station. + The Robot Controller will send the value of the variable tgtPower to the Operator Console with a key or label of "Target Power". The key will be displayed to the left of the value on the Operator Console. 4. Repeat this process and name the new key "Motor Power". @@ -461,7 +461,7 @@ second telemetry block. | - Your op mode will now also send the motor power information from the Robot Controller to be displayed on the Driver Station. + Your op mode will now also send the motor power information from the Robot Controller to be displayed on the Operator Console. Saving Your Op Mode ~~~~~~~~~~~~~~~~~~~ @@ -487,9 +487,9 @@ Controller. If your save was successful, you should see the words Exiting Program & Manage Screen ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -After you have modified and saved your op mode, if your Driver Station +After you have modified and saved your op mode, if your Operator Console is still in the Program & Manage screen, then you should exit this -screen and return to the Main Driver Station screen. +screen and return to the Main Operator Console screen. Note it will take an estimated 1 minute to complete this task. diff --git a/docs/source/programming_resources/tutorial_specific/blocks/managing_opmodes/managing-opmodes.rst b/docs/source/programming_resources/tutorial_specific/blocks/managing_opmodes/managing-opmodes.rst index 16545b6f..31085887 100644 --- a/docs/source/programming_resources/tutorial_specific/blocks/managing_opmodes/managing-opmodes.rst +++ b/docs/source/programming_resources/tutorial_specific/blocks/managing_opmodes/managing-opmodes.rst @@ -59,7 +59,7 @@ Downloading an OpMode --------------------- Once an OpMode has been saved to a device, the OpMode can be selected via the -Driver Station or edited again via the programming interfaces. However, that +Operator Console or edited again via the programming interfaces. However, that Blocks program only exists as a Blocks File (**.blk**) on the device. Often it is desirable to save a copy of the program on your laptop (or on another device, or in some other safe location) or provide the program for use by diff --git a/docs/source/programming_resources/tutorial_specific/blocks/running_op_modes/Running-Your-Op-Mode.rst b/docs/source/programming_resources/tutorial_specific/blocks/running_op_modes/Running-Your-Op-Mode.rst index 6b46c040..1febb729 100644 --- a/docs/source/programming_resources/tutorial_specific/blocks/running_op_modes/Running-Your-Op-Mode.rst +++ b/docs/source/programming_resources/tutorial_specific/blocks/running_op_modes/Running-Your-Op-Mode.rst @@ -2,8 +2,8 @@ Running Your OpMode (All Languages) ----------------------------------- If your op mode requires input from a gamepad, then you will need to -connect a Logitech F310 gamepad to the Driver Station. Note that you can -have up to two gamepads connected through a USB hub to a Driver Station. +connect a Logitech F310 gamepad to the Operator Console. Note that you can +have up to two gamepads connected through a USB hub to an Operator Console. However, in this example, we will only have a solitary gamepad connected. @@ -20,7 +20,7 @@ switch on the bottom of the gamepad is set to the "X" position. | -2. Connect the gamepad to the Driver Station using the Micro USB OTG +2. Connect the gamepad to the Operator Console using the Micro USB OTG adapter cable. .. image:: images/RunningOpModeStep2.jpg @@ -40,7 +40,7 @@ controller to designate your gamepad as user #1. Note that pushing the Start button and the B button simultaneously would designate the gamepad as user #2. -4. On the Driver Station screen, touch the triangular-shaped, +4. On the Operator Console screen, touch the triangular-shaped, "TeleOp" dropdown list button to display a list available op modes. You should see your recently saved op mode among the list of available op modes that reside on your Robot Controller. @@ -60,7 +60,7 @@ Controller. | - Note that even though you are using the Driver Station to select the op mode, the actual op mode instructions will be executed on the Robot Controller phone. + Note that even though you are using the Operator Console to select the op mode, the actual op mode instructions will be executed on the Robot Controller phone. 6. Press the INIT button to initialize your op mode. @@ -87,5 +87,5 @@ left hand corner of the screen. | - If you want to stop your op mode, press the square-shaped Stop button on the Driver Station. + If you want to stop your op mode, press the square-shaped Stop button on the Operator Console. diff --git a/docs/source/programming_resources/tutorial_specific/blocks/using_sensors/Using-Sensors-(Blocks).rst b/docs/source/programming_resources/tutorial_specific/blocks/using_sensors/Using-Sensors-(Blocks).rst index d9fc0a32..62415468 100644 --- a/docs/source/programming_resources/tutorial_specific/blocks/using_sensors/Using-Sensors-(Blocks).rst +++ b/docs/source/programming_resources/tutorial_specific/blocks/using_sensors/Using-Sensors-(Blocks).rst @@ -7,7 +7,7 @@ Color-Distance Sensor A sensor is a device that lets the Robot Controller get information about its environment. In this example, you will use a REV Robotics Color-Distance sensor to display range (distance from an object) info to -the driver station. +the Operator Console. The Color-Range sensor uses reflected light to determine the distance from the sensor to the target object. It can be used to measure close @@ -80,7 +80,7 @@ the "number" field of the "call telemetry.addData" programming block. | - This will send the measured distance to the target in centimeters back to the Driver Station. + This will send the measured distance to the target in centimeters back to the Operator Console. 8. Save your op mode and verify that it was saved successfully to the Robot Controller. @@ -99,7 +99,7 @@ to run your updated op mode. | - As you run the op mode, if you move your hand above the color light sensor, you should see the measured distance change on the Driver Station screen. If the expression "NaN" (not a number) is displayed on the Driver Station, the target is most likely out of range (and the sensor does not detect any reflected light). + As you run the op mode, if you move your hand above the color light sensor, you should see the measured distance change on the Operator Console screen. If the expression "NaN" (not a number) is displayed on the Operator Console, the target is most likely out of range (and the sensor does not detect any reflected light). Touch Sensor ~~~~~~~~~~~~ @@ -222,5 +222,5 @@ to run your updated op mode. | - As you run the op mode and push or release the button, the telemetry message on the Driver Station should update to reflect the current state of the digital Touch Sensor. + As you run the op mode and push or release the button, the telemetry message on the Operator Console should update to reflect the current state of the digital Touch Sensor. diff --git a/docs/source/programming_resources/tutorial_specific/onbot_java/creating_op_modes/Creating-and-Running-an-Op-Mode-(OnBot-Java).rst b/docs/source/programming_resources/tutorial_specific/onbot_java/creating_op_modes/Creating-and-Running-an-Op-Mode-(OnBot-Java).rst index 38c94866..d7a523ec 100644 --- a/docs/source/programming_resources/tutorial_specific/onbot_java/creating_op_modes/Creating-and-Running-an-Op-Mode-(OnBot-Java).rst +++ b/docs/source/programming_resources/tutorial_specific/onbot_java/creating_op_modes/Creating-and-Running-an-Op-Mode-(OnBot-Java).rst @@ -26,7 +26,7 @@ robot to follow a white line on the competition floor and then score a game element into a goal autonomously during a match. Teams write programs called *op modes* (which stands for "operational modes") to specify the behavior for their robot. These op modes run on the Robot -Controller phone after being selected on the Driver Station phone. +Controller phone after being selected on the Operator Console phone. Teams who are participating in the FIRST Tech Challenge have a variety of programming tools that they can use to create their own op modes. @@ -314,8 +314,8 @@ In the next few statements of the example, the op mode prompts the user to push the start button to continue. It uses another object that is available in the runOpMode method. This object is called telemetry and the op mode uses the addData method to add a message to be sent to the -Driver Station. The op mode then calls the update method to send the -message to the Driver Station. Then it calls the waitForStart method, to +Operator Console. The op mode then calls the update method to send the +message to the Operator Console. Then it calls the waitForStart method, to wait until the user pushes the start button on the driver station to begin the op mode run. @@ -332,7 +332,7 @@ driver pushes the start button. After a start command has been received, the op mode enters a while loop and keeps iterating in this loop until the op mode is no longer active -(i.e., until the user pushes the stop button on the Driver Station): +(i.e., until the user pushes the stop button on the Operator Console): .. code-block:: java @@ -345,7 +345,7 @@ and keeps iterating in this loop until the op mode is no longer active As the op mode iterates in the while loop, it will continue to send telemetry messages with the index of "Status" and the message of -"Running" to be displayed on the Driver Station. +"Running" to be displayed on the Operator Console. Building Your Op Mode ~~~~~~~~~~~~~~~~~~~~~ @@ -461,8 +461,8 @@ the build button and verify that the op mode gets built properly. Running Your Op Mode ~~~~~~~~~~~~~~~~~~~~ -* If you successfully rebuilt your op mode, you are ready to run the op mode. Verify that the Driver Station is still connected to the Robot Controller. Since you designated that your example op mode is a tele-operated op mode, it will be listed as a "TeleOp" op mode. -* On the Driver Station, use the "TeleOp" dropdown list control to display the list of available op modes. Select your op mode ("MyFIRSTJavaOpMode") from the list. +* If you successfully rebuilt your op mode, you are ready to run the op mode. Verify that the Operator Console is still connected to the Robot Controller. Since you designated that your example op mode is a tele-operated op mode, it will be listed as a "TeleOp" op mode. +* On the Operator Console, use the "TeleOp" dropdown list control to display the list of available op modes. Select your op mode ("MyFIRSTJavaOpMode") from the list. .. image:: images/OnBotDoc_SelectMyFIRSTOpMode.jpg :align: center @@ -487,7 +487,7 @@ continue. | Once you press the start button, the op mode will continue to iterate -and send the "Status: Running" message to the Driver Station. To stop +and send the "Status: Running" message to the Operator Console. To stop the op mode, press the square-shaped stop button. .. image:: images/OnBotDoc_PressStop.jpg @@ -533,7 +533,7 @@ negative value of the gamepad1's left joystick: tgtPower = -this.gamepad1.left_stick_y; The object gamepad1 is available for you to access in the runOpMode -method. It represents the state of gamepad #1 on your Driver Station. +method. It represents the state of gamepad #1 on your Operator Console. Note that for the F310 gamepads that are used during the competition, the Y value of a joystick ranges from -1, when a joystick is in its topmost position, to +1, when a joystick is in its bottommost position. @@ -551,7 +551,7 @@ negating the joystick y value can be very useful in practice. The next set of statements sets the power of motorTest to the value represented by the variable tgtPower. The values for target power and actual motor power are then added to the set of data that will be sent -via the telemetry mechanism to the Driver Station. +via the telemetry mechanism to the Operator Console. .. code-block:: java @@ -569,7 +569,7 @@ Running Your Op Mode with a Gamepad Connected * Your op mode takes input from a gamepad and uses this input to control a DC motor. To run your op mode, you will need to connect a Logitech - F310 gamepad to the Driver Station. + F310 gamepad to the Operator Console. * Before you connect your gamepad to the phone, verify that the switch on the bottom of the gamepad is set to the "X" position. @@ -578,7 +578,7 @@ Running Your Op Mode with a Gamepad Connected | -Connect the gamepad to the Driver Station using the Micro USB OTG +Connect the gamepad to the Operator Console using the Micro USB OTG adapter cable. .. image:: images/RunningOpModeStep2.jpg @@ -599,7 +599,7 @@ simultaneously would designate the gamepad as user #2. If you successfully designated the gamepad to be user #1, you should see a little gamepad icon above the text "User 1" in the upper right hand -corner of the Driver Station Screen. Whenever there is activity on +corner of the Operator Console Screen. Whenever there is activity on gamepad #1, the little icon should be highlighted in green. If the icon is missing or if it does not highlight in green when you use your gamepad, then there is a problem with the connection to the gamepad. @@ -614,7 +614,7 @@ control the motion of the motor. As you run your op mode, be careful and make sure you do not get anything caught in the turning motor. Note that the User #1 gamepad icon should highlight green each time you move the joystick. Also note that the target power and actual motor power values -should be displayed in the telemetry area on the Driver Station. +should be displayed in the telemetry area on the Operator Console. .. image:: images/OnBotDoc_RunOpModeDCMotor.jpg :align: center From b0cceb2634398a2ea2e05a28a0e3c9f49f00b7eb Mon Sep 17 00:00:00 2001 From: Miriam Sinton-Remes Date: Sun, 28 Jul 2024 23:22:01 -0400 Subject: [PATCH 2/3] Reverted incorrect uses of the term "Operator Console" --- .../configuring-dual-hubs.rst | 2 +- .../configuring-external-webcam.rst | 8 +-- .../getting_started/getting-started.rst | 12 ++-- .../saving_config/saving-config.rst | 2 +- .../Configuring-Your-Android-Devices.rst | 66 +++++++++---------- .../The-FTC-Control-System.rst | 8 +-- ...Laptop-to-the-Program-&-Manage-Network.rst | 4 +- .../required_materials/Required-Materials.rst | 2 +- .../Controlling-a-Servo-(Blocks).rst | 4 +- .../Writing-an-Op-Mode-with-FTC-Blocks.rst | 28 ++++---- .../managing_opmodes/managing-opmodes.rst | 2 +- .../running_op_modes/Running-Your-Op-Mode.rst | 12 ++-- .../using_sensors/Using-Sensors-(Blocks).rst | 8 +-- ...ng-and-Running-an-Op-Mode-(OnBot-Java).rst | 28 ++++---- 14 files changed, 93 insertions(+), 93 deletions(-) diff --git a/docs/source/hardware_and_software_configuration/configuring/configuring_dual_hubs/configuring-dual-hubs.rst b/docs/source/hardware_and_software_configuration/configuring/configuring_dual_hubs/configuring-dual-hubs.rst index 7db447b7..905f8b7b 100644 --- a/docs/source/hardware_and_software_configuration/configuring/configuring_dual_hubs/configuring-dual-hubs.rst +++ b/docs/source/hardware_and_software_configuration/configuring/configuring_dual_hubs/configuring-dual-hubs.rst @@ -82,7 +82,7 @@ first Expansion Hub before connecting the second Expansion Hub. With your first Expansion Hub connected to the 12V battery and to the Robot Controller, launch the Settings menu from the Robot Controller app (note you -can also do this from the Driver Station app, if the Operator Console is +can also do this from the Driver Station app, if the DRIVER STATION is paired to the Robot Controller). 1. Select the Advanced Settings item to display the Advanced Settings menu. diff --git a/docs/source/hardware_and_software_configuration/configuring/configuring_external_webcam/configuring-external-webcam.rst b/docs/source/hardware_and_software_configuration/configuring/configuring_external_webcam/configuring-external-webcam.rst index 16a43b00..222f1070 100644 --- a/docs/source/hardware_and_software_configuration/configuring/configuring_external_webcam/configuring-external-webcam.rst +++ b/docs/source/hardware_and_software_configuration/configuring/configuring_external_webcam/configuring-external-webcam.rst @@ -50,7 +50,7 @@ Camera Configuration Before using the external camera, it must be added to the active configuration file as a USB-connected device. -Use the Configure Robot menu item on the paired Operator Console phone to +Use the Configure Robot menu item on the paired DRIVER STATION device to add the webcam as a USB-connected device to an existing or newly created configuration file. Note that the Scan operation for the Configure Robot activity should detect the webcam and give it a default name of “Webcam @@ -85,7 +85,7 @@ Image Preview The *FIRST* Tech Challenge apps provide camera preview for ‘stream-enabled’ Op Modes using Vuforia or TensorFlow Object Detection (TFOD). -On a paired Operator Console phone, with the camera connected and +On a paired DRIVER STATION device, with the camera connected and configured, select a stream-enabled Op Mode. Press the INIT button, and wait briefly for streaming software to initialize; do not press the START button. Instead open the main menu (the 3 dots in upper right hand @@ -95,7 +95,7 @@ for safety. .. image:: images/DS-webcam-preview-CH-1.jpg -The camera image will appear on the Operator Console screen. Manually +The camera image will appear on the DRIVER STATION screen. Manually touch the image to refresh it. To preserve bandwidth, only one frame is sent at a time. @@ -117,7 +117,7 @@ command: .. image:: images/activateBeforeWaitForStart.jpg If you do not see the Camera Stream option in your main menu on your -Operator Console, then verify that the Vuforia function is activated +DRIVER STATION, then verify that the Vuforia function is activated before the waitForStart command in your Op Mode. Also make sure you’ve given the system enough time to initialize the Vuforia software before you check to see if Camera Stream is available. diff --git a/docs/source/hardware_and_software_configuration/configuring/getting_started/getting-started.rst b/docs/source/hardware_and_software_configuration/configuring/getting_started/getting-started.rst index 501fbf69..06059533 100644 --- a/docs/source/hardware_and_software_configuration/configuring/getting_started/getting-started.rst +++ b/docs/source/hardware_and_software_configuration/configuring/getting_started/getting-started.rst @@ -17,7 +17,7 @@ Connecting an Android Smartphone to an Expansion Hub If you are using an Android smartphone as a Robot Controller, you must physically connect the Robot Controller smartphone to the Expansion Hub using a USB cable and an On-The-Go (OTG) adapter. Also, you should -verify that the Operator Console is currently paired to the Robot +verify that the DRIVER STATION is currently paired to the Robot Controller. Connecting an Android Smartphone to an Expansion Hub Instructions @@ -80,19 +80,19 @@ Getting the Control Hub Ready If you are using a Control Hub, you do not need to make any additional connections. You simply need to make sure that the Control Hub is -powered on and paired to the Operator Console. +powered on and paired to the DRIVER STATION. -Creating a Configuration File Using the Operator Console +Creating a Configuration File Using the DRIVER STATION ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Although the configuration file needs to reside on the Robot Controller, -for this tutorial we will use the Operator Console app to create the -configuration file remotely. The Operator Console can be used to create a +for this tutorial we will use the DRIVER STATION app to create the +configuration file remotely. The DRIVER STATION can be used to create a configuration file for a Control Hub or for an Android smartphone Robot Controller. -Creating a Configuration File on the Robot Controller using the Operator Console Instructions +Creating a Configuration File on the Robot Controller using the DRIVER STATION Instructions ------------------------------------------------------------------------------------------- 1. Touch the three vertical dots in the upper right hand corner of diff --git a/docs/source/hardware_and_software_configuration/configuring/saving_config/saving-config.rst b/docs/source/hardware_and_software_configuration/configuring/saving_config/saving-config.rst index 7645ba87..edd83761 100644 --- a/docs/source/hardware_and_software_configuration/configuring/saving_config/saving-config.rst +++ b/docs/source/hardware_and_software_configuration/configuring/saving_config/saving-config.rst @@ -56,7 +56,7 @@ back-arrow button to return to the main screen of the app. | 7. Verify that the configuration file is the active configuration -file on the main Operator Console screen. +file on the main DRIVER STATION screen. .. image:: images/SavingConfigurationInformationNewStep7.jpg :align: center diff --git a/docs/source/programming_resources/shared/configuring_android/Configuring-Your-Android-Devices.rst b/docs/source/programming_resources/shared/configuring_android/Configuring-Your-Android-Devices.rst index 29df454f..a3d54e87 100644 --- a/docs/source/programming_resources/shared/configuring_android/Configuring-Your-Android-Devices.rst +++ b/docs/source/programming_resources/shared/configuring_android/Configuring-Your-Android-Devices.rst @@ -8,17 +8,17 @@ Control Hub Configuration ^^^^^^^^^^^^^^^^^^^^^^^^^ .. note:: - References to the Operator Console smartphone may instead apply to the + References to the DRIVER STATION smartphone may instead apply to the `REV Driver Hub `__, which is preloaded with the Driver Station (DS) app. Teams who are using a Control Hub (which has an integrated Android Device) -will only need to configure a single smartphone for use as a Operator Console. The process is as follows: +will only need to configure a single smartphone for use as a DRIVER STATION. The process is as follows: * Rename the smartphone to "-DS" (where is replaced by your team number). -* Install the Driver Station (DS) app onto the Operator Console phone. (The DS app is pre-installed on the REV Driver Hub.) +* Install the Driver Station (DS) app onto the DRIVER STATION device. (The DS app is pre-installed on the REV Driver Hub.) * Put your phone into Airplane Mode (with the WiFi radio still on). -* Pair (i.e., wirelessly connect) the Operator Console to the Control Hub. +* Pair (i.e., wirelessly connect) the DRIVER STATION to the Control Hub. .. image:: images/ControlHubAndPhone.jpg :align: center @@ -36,14 +36,14 @@ Two Android Smartphone Configuration Teams who have two smartphones and are not using a Control Hub will need to configure one smartphone for use as a Robot Controller and a second -smartphone for use as an Operator Console. The process is as follows, +smartphone for use as an DRIVER STATION. The process is as follows, * Rename one smartphone to "-RC" (replace with your team number). * Install the Robot Controller app onto the Robot Controller phone. * Rename a second smartphone to "-DS" (where is replaced by your team number). -* Install the Driver Station app onto the Operator Console phone. (The DS app is pre-installed on the REV Driver Hub.) +* Install the Driver Station app onto the DRIVER STATION device. (The DS app is pre-installed on the REV Driver Hub.) * Put your phones into Airplane Mode (with the WiFi radios still on). -* Pair (i.e., wirelessly connect) the Operator Console to the Robot Controller. +* Pair (i.e., wirelessly connect) the DRIVER STATION to the Robot Controller. .. image:: images/twoAndroidPhones.jpg :align: center @@ -57,13 +57,13 @@ Renaming Your Smartphones The official rules of the FIRST Tech Challenge (see ) require that you change the Wi-Fi name of your smartphones to include your team -number and "-RC" if the phone is a Robot Controller or "-DS" if it is an Operator Console. A team can insert an additional dash and a letter ("A", +number and "-RC" if the phone is a Robot Controller or "-DS" if it is a DRIVER STATION. A team can insert an additional dash and a letter ("A", "B", "C", etc.) if the team has more than one set of Android phones. If, for example, a team has a team number of 9999 and the team has multiple sets of phones, the team might decide to name one phone "9999-C-RC" for the Robot Controller and the other phone "9999-C-DS" for -the Operator Console. The "-C" indicates that these devices belong to the +the DRIVER STATION. The "-C" indicates that these devices belong to the third set of phones for this team. The name of a Robot Controller phone can be changed in the RC app, using @@ -71,7 +71,7 @@ instructions :ref:`found here `. @@ -120,7 +120,7 @@ level, as described below. * - 7. Select **Configure Device** from the pop-up menu. - |rename7| - * - 8. Use touch pad to enter new name of device. If the device will be a Robot Controller, specify your team number and -RC. If thedevice will be an Operator Console, specify your team number and -DS. You can also set the Wi-Fi Direct inactivity timeout to *Never disconnect* and then hit the\ **SAVE** button to save your changes. Note that in the screenshot shown to the right, the team number is 9999. The "-C" indicates that this is from the third pair of smartphones for this team. The -RC indicates that this phone will be a Robot Controller. + * - 8. Use touch pad to enter new name of device. If the device will be a Robot Controller, specify your team number and -RC. If the device will be a DRIVER STATION, specify your team number and -DS. You can also set the Wi-Fi Direct inactivity timeout to *Never disconnect* and then hit the\ **SAVE** button to save your changes. Note that in the screenshot shown to the right, the team number is 9999. The "-C" indicates that this is from the third pair of smartphones for this team. The -RC indicates that this phone will be a Robot Controller. - |rename8| * - 9. After renaming phone, power cycle thedevice. @@ -214,7 +214,7 @@ Placing Phones into Airplane Mode with Wi-Fi On ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For the FIRST Tech Challenge competitions, it is important that you -place your Robot Controller and Operator Console phones into Airplane mode +place your Robot Controller and DRIVER STATION devices into Airplane mode but keep their Wi-Fi radios turned on. This is important because you do not want any of the cellular telephone functions to be enabled during a match. The cellular telephone functions could disrupt the function of @@ -242,7 +242,7 @@ the robot during a match. - |airplane2| -Pairing the Operator Console to the Robot Controller +Pairing the DRIVER STATION to the Robot Controller ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. _control-hub-users-1: @@ -253,11 +253,11 @@ Control Hub Pairing The REV Robotics Control Hub should come with the Robot Controller app pre-installed. Once you have successfully installed the Driver Station on an Android phone, you will want to establish a secure -wireless connection between the Control Hub and the Operator Console. This -connection will allow your Operator Console phone to select op modes on +wireless connection between the Control Hub and the DRIVER STATION. This +connection will allow your DRIVER STATION device to select op modes on your Robot Controller and send gamepad input to these programs. Likewise, it will allow your op modes running on your Robot Controller -to send telemetry data to your Operator Console phone where it can be +to send telemetry data to your DRIVER STATION phone where it can be displayed for your drivers. The process to connect the two devices is known as "pairing." @@ -310,7 +310,7 @@ task. * - 6. From the **Settings** screen, look for and select \ **Pairing Method** to launch the **Pairing** \ **Method** screen. - |pairing6| - * - 7. Touch the words **Control Hub** to indicate that this Operator Console will be pairing with a Control Hub. + * - 7. Touch the words **Control Hub** to indicate that this DRIVER STATION will be pairing with a Control Hub. - |pairing7| * - 8. From the **Settings** screen, look for and select \ **Pair with Robot Controller** to launch the **Pair** \ **with Robot Controller** screen. @@ -322,13 +322,13 @@ task. * - 10. Find the name of your Control Hub's wireless network from the list of available WiFi networks. Click on the network name to select the network. If this is the first time you are connecting to the Control Hub, then the default network name should begin with the prefix FTC- (FTC-1Ybr in this example). The default network name should be listed on a sticker attached to the bottom side of the Control Hub. - |pairing10| - * - 11. When prompted, specify the password for the Control Hub's WiFi network and press \ **Connect** to connect to the Hub. Note that the default password for the Control Hub network is ``password``. Also note that when you connect to the Control Hub's WiFi network successfully, the Operator Console will not have access to the Internet. + * - 11. When prompted, specify the password for the Control Hub's WiFi network and press \ **Connect** to connect to the Hub. Note that the default password for the Control Hub network is ``password``. Also note that when you connect to the Control Hub's WiFi network successfully, the DRIVER STATION will not have access to the Internet. - |pairing11| - * - 12. After you successfully connected to the Hub, use the back arrow to navigate to theprevious screen. You should see the name of the WiFi network listed under "Current Robot Controller:". Use the back-arrow key to return to the Settings screen. Then press the back-arrow key one more time to return to the main Operator Console screen. + * - 12. After you successfully connected to the Hub, use the back arrow to navigate to theprevious screen. You should see the name of the WiFi network listed under "Current Robot Controller:". Use the back-arrow key to return to the Settings screen. Then press the back-arrow key one more time to return to the main DRIVER STATION screen. - |pairing12| - * - 13. Verify that the Operator Console screen has changed and that it now indicates that it is connected to the Control Hub. The name of the Control Hub's WiFi network (FTC-1Ybr in this example) should be displayed in the Network field on the Driver Station. + * - 13. Verify that the DRIVER STATION screen has changed and that it now indicates that it is connected to the Control Hub. The name of the Control Hub's WiFi network (FTC-1Ybr in this example) should be displayed in the Network field on the Driver Station. - |pairing13| @@ -337,22 +337,22 @@ task. Two Android Smartphone Pairing ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -.. important:: If your Operator Console was previously paired to a +.. important:: If your DRIVER STATION was previously paired to a Control Hub, and you currently would like to connect to an Android smartphone Robot Controller, then before attempting to pair to the Robot Controller, you should forget the Wi-Fi network for the previous Control - Hub (using the Android Wifi Settings screen on the Operator Console) and - then power cycle the Operator Console phone. If the previous Control Hub - is powered on and if you haven't forgotten this network, then the Operator Console might try and connect to the Control Hub and might be unable to + Hub (using the Android Wifi Settings screen on the DRIVER STATION) and + then power cycle the DRIVER STATION phone. If the previous Control Hub + is powered on and if you haven't forgotten this network, then the DRIVER STATION might try and connect to the Control Hub and might be unable to connect to the Robot Controller smartphone. Once you have successfully installed the apps onto your Android phones, you will want to establish a secure wireless connection between -the two devices. This connection will allow your Operator Console phone to +the two devices. This connection will allow your DRIVER STATION device to select op modes on your Robot Controller phone and send gamepad input to these programs. Likewise, it will allow your op modes running on your -Robot Controller phone to send telemetry data to your Operator Console -phone where it can be displayed for your drivers. The process to connect +Robot Controller phone to send telemetry data to your DRIVER STATION +device where it can be displayed for your drivers. The process to connect the two phones is known as pairing. Note that it will take an estimated 10 minutes to complete this task. @@ -387,7 +387,7 @@ Note that it will take an estimated 10 minutes to complete this task. * - 2. Verify that the Robot Controller app is running. The **Robot Status** field should read running if it is working properly. - |pairingns2| - * - 3. On the Operator Console device, browse the available apps and locate the **FTC Driver Station** icon. Tap on the icon to launch the Driver Station app. Note that the first time you launch the app your Android device might prompt you for permissions that the app will need to run properly. Whenever prompted, press **Allow** to grant the requested permission. + * - 3. On the DRIVER STATION device, browse the available apps and locate the **FTC Driver Station** icon. Tap on the icon to launch the Driver Station app. Note that the first time you launch the app your Android device might prompt you for permissions that the app will need to run properly. Whenever prompted, press **Allow** to grant the requested permission. - |pairingns3| |pairingns3b| * - 4. Touch the three vertical dots on the upper right hand corner of the main screen of the Driver Station app. This will launch a pop-up menu. @@ -399,20 +399,20 @@ Note that it will take an estimated 10 minutes to complete this task. * - 6. From the **Settings** screen, look for and select \ **Pairing Method** to launch the **Pairing** \ **Method** screen. - |pairingns6| - * - 7. Verify that the **Wifi Direct** mode is selected, which means that this Operator Console will be pairing with another Android device. + * - 7. Verify that the **Wifi Direct** mode is selected, which means that this DRIVER STATION will be pairing with another Android device. - |pairingns7| * - 8. From the **Settings** screen, look for and select \ **Pair with Robot Controller** to launch the **Pair** \ \ **with Robot Controller** screen. - |pairingns8| - * - 9. Find the name of your Robot Controller from the list and select it. After you have made your selection, use the back-arrow key to return to the Settings screen. Then press the back-arrow key one more time to return to the main Operator Console screen. + * - 9. Find the name of your Robot Controller from the list and select it. After you have made your selection, use the back-arrow key to return to the Settings screen. Then press the back-arrow key one more time to return to the main DRIVER STATION screen. - |pairingns9| - * - 10. When the Operator Console returns to its main screen, the first time you attempt to connect to the Robot Controller a prompt should appear on the Robot Controller screen. Click on the **ACCEPT** button to accept the connection request from the Operator Console. + * - 10. When the DRIVER STATION returns to its main screen, the first time you attempt to connect to the Robot Controller a prompt should appear on the Robot Controller screen. Click on the **ACCEPT** button to accept the connection request from the DRIVER STATION. - |pairingns10| - * - 11. Verify that the Operator Console screen has changed and that it now indicates that it is connected to the Robot Controller. The name ofthe Robot Controller's remote network (9999-C-RC in this example) should be displayed in the Network field on the Operator Console. + * - 11. Verify that the DRIVER STATION screen has changed and that it now indicates that it is connected to the Robot Controller. The name ofthe Robot Controller's remote network (9999-C-RC in this example) should be displayed in the Network field on the DRIVER STATION. - |pairingns11| - * - 12. Verify that the Robot Controller screen has changed and that it now indicates that it is connected to the Operator Console.The Network status should read active, connected on the Robot Controller's main screen. + * - 12. Verify that the Robot Controller screen has changed and that it now indicates that it is connected to the DRIVER STATION.The Network status should read active, connected on the Robot Controller's main screen. - |pairingns12| \ No newline at end of file diff --git a/docs/source/programming_resources/shared/control_system_intro/The-FTC-Control-System.rst b/docs/source/programming_resources/shared/control_system_intro/The-FTC-Control-System.rst index 901e338a..301dfc7c 100644 --- a/docs/source/programming_resources/shared/control_system_intro/The-FTC-Control-System.rst +++ b/docs/source/programming_resources/shared/control_system_intro/The-FTC-Control-System.rst @@ -47,11 +47,11 @@ There are two hardware options currently being used: REV Robotics Expansion Hub or the REV Robotics Control Hub. A second Android device sits with the team drivers and has one or two -gamepads connected. This second device is known as the *Operator Console*. -The Operator Console is sort of like a remote control that you might use -to control your television. The Operator Console allows a team to +gamepads connected. This second device is known as the DRIVER STATION. +The DRIVER STATION is sort of like a remote control that you might use +to control your television. The DRIVER STATION allows a team to communicate remotely (using a secure, wireless connection) to the Robot -Controller and to issue commands to the Robot Controller. The Operator Console consists of an Android device running an Driver Station app. +Controller and to issue commands to the Robot Controller. The DRIVER STATION consists of an Android device running an Driver Station app. REV Robotics Expansion Hub ~~~~~~~~~~~~~~~~~~~~~~~~~~ diff --git a/docs/source/programming_resources/shared/program_and_manage_network/Connecting-a-Laptop-to-the-Program-&-Manage-Network.rst b/docs/source/programming_resources/shared/program_and_manage_network/Connecting-a-Laptop-to-the-Program-&-Manage-Network.rst index 7399f1b2..30d0cca6 100644 --- a/docs/source/programming_resources/shared/program_and_manage_network/Connecting-a-Laptop-to-the-Program-&-Manage-Network.rst +++ b/docs/source/programming_resources/shared/program_and_manage_network/Connecting-a-Laptop-to-the-Program-&-Manage-Network.rst @@ -19,7 +19,7 @@ documentation for details on how to connect to a Wi-Fi network. Connecting Your Laptop to the Program & Manage Network Instructions ------------------------------------------------------------------- -1. On the Operator Console, touch the three dots in the upper right +1. On the DRIVER STATION, touch the three dots in the upper right hand corner of the screen to launch the pop-up menu. Select **Program & Manage** from the pop-up menu to display the **Program & Manage** access information. @@ -129,7 +129,7 @@ available networks, or, if you are having problems connecting your laptop to the Program & Manage wireless network, make sure you answer the following questions: -1. Is the Robot Controller running and connected to the Operator Console? +1. Is the Robot Controller running and connected to the DRIVER STATION? 2. Is your Windows laptop updated with the most current system updates and service packs? Older versions of Windows 8 and 10, for example, had issues that could prevent the laptop from displaying the Program diff --git a/docs/source/programming_resources/shared/required_materials/Required-Materials.rst b/docs/source/programming_resources/shared/required_materials/Required-Materials.rst index c24b3ef6..a0dafc95 100644 --- a/docs/source/programming_resources/shared/required_materials/Required-Materials.rst +++ b/docs/source/programming_resources/shared/required_materials/Required-Materials.rst @@ -47,7 +47,7 @@ tutorials, you will need to have the following materials available: * - Required Item(s) - Image - * - Two (2) FIRST-approved* Android devices OR One (1) Control Hub and one (1) FIRST-approved* Android device for the Operator Console + * - Two (2) FIRST-approved* Android devices OR One (1) Control Hub and one (1) FIRST-approved* Android device for the DRIVER STATION - |androidphones| Or |chandphones| * - Wireless Internet access. diff --git a/docs/source/programming_resources/tutorial_specific/blocks/controlling_a_servo/Controlling-a-Servo-(Blocks).rst b/docs/source/programming_resources/tutorial_specific/blocks/controlling_a_servo/Controlling-a-Servo-(Blocks).rst index ec0d3065..3009462e 100644 --- a/docs/source/programming_resources/tutorial_specific/blocks/controlling_a_servo/Controlling-a-Servo-(Blocks).rst +++ b/docs/source/programming_resources/tutorial_specific/blocks/controlling_a_servo/Controlling-a-Servo-(Blocks).rst @@ -286,7 +286,7 @@ field. | - This set of blocks will send the current servo position value to the Operator Console while the op mode is running. + This set of blocks will send the current servo position value to the DRIVER STATION while the op mode is running. 25. Save your op mode and verify that it was saved successfully to the Robot Controller. @@ -306,6 +306,6 @@ designated as User #1 before running your op mode. | - You should now be able to control the servo position with the colored buttons. The servo position should be displayed on the Operator Console. + You should now be able to control the servo position with the colored buttons. The servo position should be displayed on the DRIVER STATION. diff --git a/docs/source/programming_resources/tutorial_specific/blocks/creating_op_modes/Writing-an-Op-Mode-with-FTC-Blocks.rst b/docs/source/programming_resources/tutorial_specific/blocks/creating_op_modes/Writing-an-Op-Mode-with-FTC-Blocks.rst index 712cc51f..b2f2f576 100644 --- a/docs/source/programming_resources/tutorial_specific/blocks/creating_op_modes/Writing-an-Op-Mode-with-FTC-Blocks.rst +++ b/docs/source/programming_resources/tutorial_specific/blocks/creating_op_modes/Writing-an-Op-Mode-with-FTC-Blocks.rst @@ -11,7 +11,7 @@ want their robot to follow a white line on the competition floor and then score a game element into a goal autonomously during a match. Teams write programs called *op modes* (which stands for "operational modes") to specify the behavior for their robot. These op modes run on the Robot -Controller after being selected on the Operator Console. +Controller after being selected on the DRIVER STATION. Teams who are participating in the *FIRST* Tech Challenge have a variety of programming tools that they can use to create their own op modes. @@ -166,7 +166,7 @@ you create. They create the basic structure for your op mode. In the figure shown above, the main body of the op mode is defined by the outer purple bracket that has the words "to runOpMode" at the top. As the help tip indicates, this function is executed when this op mode -("MyFIRSTOpMode" in this example) is selected from the Operator Console. +("MyFIRSTOpMode" in this example) is selected from the DRIVER STATION. It can be helpful to think of an op mode as a list of tasks for the Robot Controller to perform. The Robot Controller will process this list @@ -198,12 +198,12 @@ human user. The robot will ignore any comments in an op mode. Any programming blocks that are placed after the "Put initialization blocks here" comment (and before the "call MyFIRSTOpMode.waitForStart" block) will be executed when the op mode is first selected by a user at -the Operator Console. +the DRIVER STATION. When the Robot Controller reaches the block labeled "call MyFIRSTOpMode.waitForStart" it will stop and wait until it receives a -Start command from the Operator Console. A Start command will not be sent -until the user pushes the Start button on the Operator Console. Any code +Start command from the DRIVER STATION. A Start command will not be sent +until the user pushes the Start button on the DRIVER STATION. Any code after the "call MyFIRSTOpMode.waitForStart" block will get executed after the Start button has been pressed. @@ -396,11 +396,11 @@ Inserting Telemetry Statements Your op mode is just about ready to run. However, before continuing, you will add a couple of telemetry statements that will send information -from the Robot Controller to the Operator Console for display on the -Operator Console user interface. This telemetry mechanism is a useful way -to display status information from the robot on the Operator Console. You +from the Robot Controller to the DRIVER STATION for display on the +DRIVER STATION user interface. This telemetry mechanism is a useful way +to display status information from the robot on the DRIVER STATION. You can use this mechanism to display sensor data, motor status, gamepad -state, etc. from the Robot Controller to the Operator Console. +state, etc. from the Robot Controller to the DRIVER STATION. Note that you will need an estimated 15 minutes to complete this task. @@ -425,7 +425,7 @@ below the "set motor1.Power to" block. Click on the green text block | - Note that the "call telemetry.update" block is an important block. Data that is added to the telemetry buffer will not be sent to the Operator Console until the "telemetry.update" method is called. + Note that the "call telemetry.update" block is an important block. Data that is added to the telemetry buffer will not be sent to the DRIVER STATION until the "telemetry.update" method is called. 3. Click on the "Variables" block category and select the "tgtPower" block. Drag the block so it clicks into place next to the "number" @@ -436,7 +436,7 @@ parameter on the telemetry programming block. | - The Robot Controller will send the value of the variable tgtPower to the Operator Console with a key or label of "Target Power". The key will be displayed to the left of the value on the Operator Console. + The Robot Controller will send the value of the variable tgtPower to the DRIVER STATION with a key or label of "Target Power". The key will be displayed to the left of the value on the DRIVER STATION. 4. Repeat this process and name the new key "Motor Power". @@ -461,7 +461,7 @@ second telemetry block. | - Your op mode will now also send the motor power information from the Robot Controller to be displayed on the Operator Console. + Your op mode will now also send the motor power information from the Robot Controller to be displayed on the DRIVER STATION. Saving Your Op Mode ~~~~~~~~~~~~~~~~~~~ @@ -487,9 +487,9 @@ Controller. If your save was successful, you should see the words Exiting Program & Manage Screen ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -After you have modified and saved your op mode, if your Operator Console +After you have modified and saved your op mode, if your DRIVER STATION is still in the Program & Manage screen, then you should exit this -screen and return to the Main Operator Console screen. +screen and return to the Main DRIVER STATION screen. Note it will take an estimated 1 minute to complete this task. diff --git a/docs/source/programming_resources/tutorial_specific/blocks/managing_opmodes/managing-opmodes.rst b/docs/source/programming_resources/tutorial_specific/blocks/managing_opmodes/managing-opmodes.rst index 31085887..3ea334e5 100644 --- a/docs/source/programming_resources/tutorial_specific/blocks/managing_opmodes/managing-opmodes.rst +++ b/docs/source/programming_resources/tutorial_specific/blocks/managing_opmodes/managing-opmodes.rst @@ -59,7 +59,7 @@ Downloading an OpMode --------------------- Once an OpMode has been saved to a device, the OpMode can be selected via the -Operator Console or edited again via the programming interfaces. However, that +DRIVER STATION or edited again via the programming interfaces. However, that Blocks program only exists as a Blocks File (**.blk**) on the device. Often it is desirable to save a copy of the program on your laptop (or on another device, or in some other safe location) or provide the program for use by diff --git a/docs/source/programming_resources/tutorial_specific/blocks/running_op_modes/Running-Your-Op-Mode.rst b/docs/source/programming_resources/tutorial_specific/blocks/running_op_modes/Running-Your-Op-Mode.rst index 1febb729..cbba6b44 100644 --- a/docs/source/programming_resources/tutorial_specific/blocks/running_op_modes/Running-Your-Op-Mode.rst +++ b/docs/source/programming_resources/tutorial_specific/blocks/running_op_modes/Running-Your-Op-Mode.rst @@ -2,8 +2,8 @@ Running Your OpMode (All Languages) ----------------------------------- If your op mode requires input from a gamepad, then you will need to -connect a Logitech F310 gamepad to the Operator Console. Note that you can -have up to two gamepads connected through a USB hub to an Operator Console. +connect a Logitech F310 gamepad to the DRIVER STATION. Note that you can +have up to two gamepads connected through a USB hub to a DRIVER STATION. However, in this example, we will only have a solitary gamepad connected. @@ -20,7 +20,7 @@ switch on the bottom of the gamepad is set to the "X" position. | -2. Connect the gamepad to the Operator Console using the Micro USB OTG +2. Connect the gamepad to the DRIVER STATION using the Micro USB OTG adapter cable. .. image:: images/RunningOpModeStep2.jpg @@ -40,7 +40,7 @@ controller to designate your gamepad as user #1. Note that pushing the Start button and the B button simultaneously would designate the gamepad as user #2. -4. On the Operator Console screen, touch the triangular-shaped, +4. On the DRIVER STATION screen, touch the triangular-shaped, "TeleOp" dropdown list button to display a list available op modes. You should see your recently saved op mode among the list of available op modes that reside on your Robot Controller. @@ -60,7 +60,7 @@ Controller. | - Note that even though you are using the Operator Console to select the op mode, the actual op mode instructions will be executed on the Robot Controller phone. + Note that even though you are using the DRIVER STATION to select the op mode, the actual op mode instructions will be executed on the Robot Controller phone. 6. Press the INIT button to initialize your op mode. @@ -87,5 +87,5 @@ left hand corner of the screen. | - If you want to stop your op mode, press the square-shaped Stop button on the Operator Console. + If you want to stop your op mode, press the square-shaped Stop button on the DRIVER STATION. diff --git a/docs/source/programming_resources/tutorial_specific/blocks/using_sensors/Using-Sensors-(Blocks).rst b/docs/source/programming_resources/tutorial_specific/blocks/using_sensors/Using-Sensors-(Blocks).rst index 62415468..26696607 100644 --- a/docs/source/programming_resources/tutorial_specific/blocks/using_sensors/Using-Sensors-(Blocks).rst +++ b/docs/source/programming_resources/tutorial_specific/blocks/using_sensors/Using-Sensors-(Blocks).rst @@ -7,7 +7,7 @@ Color-Distance Sensor A sensor is a device that lets the Robot Controller get information about its environment. In this example, you will use a REV Robotics Color-Distance sensor to display range (distance from an object) info to -the Operator Console. +the DRIVER STATION. The Color-Range sensor uses reflected light to determine the distance from the sensor to the target object. It can be used to measure close @@ -80,7 +80,7 @@ the "number" field of the "call telemetry.addData" programming block. | - This will send the measured distance to the target in centimeters back to the Operator Console. + This will send the measured distance to the target in centimeters back to the DRIVER STATION. 8. Save your op mode and verify that it was saved successfully to the Robot Controller. @@ -99,7 +99,7 @@ to run your updated op mode. | - As you run the op mode, if you move your hand above the color light sensor, you should see the measured distance change on the Operator Console screen. If the expression "NaN" (not a number) is displayed on the Operator Console, the target is most likely out of range (and the sensor does not detect any reflected light). + As you run the op mode, if you move your hand above the color light sensor, you should see the measured distance change on the DRIVER STATION screen. If the expression "NaN" (not a number) is displayed on the DRIVER STATION, the target is most likely out of range (and the sensor does not detect any reflected light). Touch Sensor ~~~~~~~~~~~~ @@ -222,5 +222,5 @@ to run your updated op mode. | - As you run the op mode and push or release the button, the telemetry message on the Operator Console should update to reflect the current state of the digital Touch Sensor. + As you run the op mode and push or release the button, the telemetry message on the DRIVER STATION should update to reflect the current state of the digital Touch Sensor. diff --git a/docs/source/programming_resources/tutorial_specific/onbot_java/creating_op_modes/Creating-and-Running-an-Op-Mode-(OnBot-Java).rst b/docs/source/programming_resources/tutorial_specific/onbot_java/creating_op_modes/Creating-and-Running-an-Op-Mode-(OnBot-Java).rst index d7a523ec..e30e305e 100644 --- a/docs/source/programming_resources/tutorial_specific/onbot_java/creating_op_modes/Creating-and-Running-an-Op-Mode-(OnBot-Java).rst +++ b/docs/source/programming_resources/tutorial_specific/onbot_java/creating_op_modes/Creating-and-Running-an-Op-Mode-(OnBot-Java).rst @@ -26,7 +26,7 @@ robot to follow a white line on the competition floor and then score a game element into a goal autonomously during a match. Teams write programs called *op modes* (which stands for "operational modes") to specify the behavior for their robot. These op modes run on the Robot -Controller phone after being selected on the Operator Console phone. +Controller phone after being selected on the DRIVER STATION device. Teams who are participating in the FIRST Tech Challenge have a variety of programming tools that they can use to create their own op modes. @@ -314,8 +314,8 @@ In the next few statements of the example, the op mode prompts the user to push the start button to continue. It uses another object that is available in the runOpMode method. This object is called telemetry and the op mode uses the addData method to add a message to be sent to the -Operator Console. The op mode then calls the update method to send the -message to the Operator Console. Then it calls the waitForStart method, to +DRIVER STATION. The op mode then calls the update method to send the +message to the DRIVER STATION. Then it calls the waitForStart method, to wait until the user pushes the start button on the driver station to begin the op mode run. @@ -332,7 +332,7 @@ driver pushes the start button. After a start command has been received, the op mode enters a while loop and keeps iterating in this loop until the op mode is no longer active -(i.e., until the user pushes the stop button on the Operator Console): +(i.e., until the user pushes the stop button on the DRIVER STATION): .. code-block:: java @@ -345,7 +345,7 @@ and keeps iterating in this loop until the op mode is no longer active As the op mode iterates in the while loop, it will continue to send telemetry messages with the index of "Status" and the message of -"Running" to be displayed on the Operator Console. +"Running" to be displayed on the DRIVER STATION. Building Your Op Mode ~~~~~~~~~~~~~~~~~~~~~ @@ -461,8 +461,8 @@ the build button and verify that the op mode gets built properly. Running Your Op Mode ~~~~~~~~~~~~~~~~~~~~ -* If you successfully rebuilt your op mode, you are ready to run the op mode. Verify that the Operator Console is still connected to the Robot Controller. Since you designated that your example op mode is a tele-operated op mode, it will be listed as a "TeleOp" op mode. -* On the Operator Console, use the "TeleOp" dropdown list control to display the list of available op modes. Select your op mode ("MyFIRSTJavaOpMode") from the list. +* If you successfully rebuilt your op mode, you are ready to run the op mode. Verify that the DRIVER STATION is still connected to the Robot Controller. Since you designated that your example op mode is a tele-operated op mode, it will be listed as a "TeleOp" op mode. +* On the DRIVER STATION, use the "TeleOp" dropdown list control to display the list of available op modes. Select your op mode ("MyFIRSTJavaOpMode") from the list. .. image:: images/OnBotDoc_SelectMyFIRSTOpMode.jpg :align: center @@ -487,7 +487,7 @@ continue. | Once you press the start button, the op mode will continue to iterate -and send the "Status: Running" message to the Operator Console. To stop +and send the "Status: Running" message to the DRIVER STATION. To stop the op mode, press the square-shaped stop button. .. image:: images/OnBotDoc_PressStop.jpg @@ -533,7 +533,7 @@ negative value of the gamepad1's left joystick: tgtPower = -this.gamepad1.left_stick_y; The object gamepad1 is available for you to access in the runOpMode -method. It represents the state of gamepad #1 on your Operator Console. +method. It represents the state of gamepad #1 in your OPERATOR CONSOLE. Note that for the F310 gamepads that are used during the competition, the Y value of a joystick ranges from -1, when a joystick is in its topmost position, to +1, when a joystick is in its bottommost position. @@ -551,7 +551,7 @@ negating the joystick y value can be very useful in practice. The next set of statements sets the power of motorTest to the value represented by the variable tgtPower. The values for target power and actual motor power are then added to the set of data that will be sent -via the telemetry mechanism to the Operator Console. +via the telemetry mechanism to the DRIVER STATION. .. code-block:: java @@ -569,7 +569,7 @@ Running Your Op Mode with a Gamepad Connected * Your op mode takes input from a gamepad and uses this input to control a DC motor. To run your op mode, you will need to connect a Logitech - F310 gamepad to the Operator Console. + F310 gamepad to the DRIVER STATION. * Before you connect your gamepad to the phone, verify that the switch on the bottom of the gamepad is set to the "X" position. @@ -578,7 +578,7 @@ Running Your Op Mode with a Gamepad Connected | -Connect the gamepad to the Operator Console using the Micro USB OTG +Connect the gamepad to the DRIVER STATION using the Micro USB OTG adapter cable. .. image:: images/RunningOpModeStep2.jpg @@ -599,7 +599,7 @@ simultaneously would designate the gamepad as user #2. If you successfully designated the gamepad to be user #1, you should see a little gamepad icon above the text "User 1" in the upper right hand -corner of the Operator Console Screen. Whenever there is activity on +corner of the DRIVER STATION Screen. Whenever there is activity on gamepad #1, the little icon should be highlighted in green. If the icon is missing or if it does not highlight in green when you use your gamepad, then there is a problem with the connection to the gamepad. @@ -614,7 +614,7 @@ control the motion of the motor. As you run your op mode, be careful and make sure you do not get anything caught in the turning motor. Note that the User #1 gamepad icon should highlight green each time you move the joystick. Also note that the target power and actual motor power values -should be displayed in the telemetry area on the Operator Console. +should be displayed in the telemetry area on the DRIVER STATION. .. image:: images/OnBotDoc_RunOpModeDCMotor.jpg :align: center From e83e92442c298a29ff6156809d2bb21d3c059e40 Mon Sep 17 00:00:00 2001 From: Miriam Sinton-Remes Date: Mon, 29 Jul 2024 19:49:56 -0400 Subject: [PATCH 3/3] Fixed a typo --- .../shared/required_materials/Required-Materials.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/programming_resources/shared/required_materials/Required-Materials.rst b/docs/source/programming_resources/shared/required_materials/Required-Materials.rst index a0dafc95..5567604f 100644 --- a/docs/source/programming_resources/shared/required_materials/Required-Materials.rst +++ b/docs/source/programming_resources/shared/required_materials/Required-Materials.rst @@ -53,7 +53,7 @@ tutorials, you will need to have the following materials available: * - Wireless Internet access. - |wifi| - * - Laptop with Microsoft Windows 7, 8 or 10 and Wi-Fi capability. Note that your laptop should have the most current service packs and systemu pdates from Microsoft. If you are using a different type of machine (such as a Chromebook, Android Tablet, etc.) as your programming device, the steps might differ slightly on how to access the Programming Server on the Robot Controller. Refer to your device’s user documentation for details on howto connect to a Wi-Fi network. + * - Laptop with Microsoft Windows 7, 8 or 10 and Wi-Fi capability. Note that your laptop should have the most current service packs and system updates from Microsoft. If you are using a different type of machine (such as a Chromebook, Android Tablet, etc.) as your programming device, the steps might differ slightly on how to access the Programming Server on the Robot Controller. Refer to your device’s user documentation for details on howto connect to a Wi-Fi network. - |laptop| * - Javascript-enabled web browser (Google Chrome is the recommended browser).