Add Systemcore Introduction and component overview

Author: sciencewhiz

source/docs/contributing/frc-docs/style-guide.rst

@@ -20,6 +20,7 @@ All text content should be on the same line. If you need readability, use the wo
 
 Use the following case for these terms:
 
+- Systemcore (not SystemCore or systemcore)
 - roboRIO (not RoboRIO, roboRio, or RoboRio)
 - LabVIEW (not labview or LabView)
 - Visual Studio Code (VS Code) (not vscode, VScode, vs code, etc)

source/docs/controls-overviews/control-system-hardware.rst

@@ -36,21 +36,21 @@ The goal of this document is to provide a brief overview of the hardware compone
 
         Diagram courtesy of FRC\ |reg| Team 3161 and Stefen Acepcion.
 
-## NI roboRIO
+## Limelight Systemcore
 
-.. image:: images/control-system-hardware/roborio.png
-  :alt: NI roboRIO
+.. image:: images/control-system-hardware/systemcore.png
+  :alt: Limelight Systemcore
   :width: 500
 
-The :ref:`NI-roboRIO <docs/software/roborio-info/roborio-introduction:roboRIO Introduction>` is the main robot controller used for FRC. The roboRIO serves as the "brain" for the robot running team-generated code that commands all of the other hardware.
+The :doc:`Limelight Systemore </docs/software/systemcore-info/systemcore-introduction>` is the main robot controller used for FRC. The Systemcore serves as the "brain" for the robot running team-generated code that commands all of the other hardware.
 
 ## CTRE Power Distribution Panel
 
 .. image:: images/control-system-hardware/power-distribution-panel.png
   :alt: CTRE Power Distribution Panel
   :width: 500
 
-The :ref:`CTRE Power Distribution Panel <docs/software/can-devices/power-distribution-module:Power Distribution Module>` (PDP) is designed to distribute power from a 12VDC battery to various robot components through auto-resetting circuit breakers and a small number of special function fused connections. The PDP provides 8 output pairs rated for 40A continuous current and 8 pairs rated for 30A continuous current. The PDP provides dedicated 12V connectors for the roboRIO, as well as connectors for the Voltage Regulator Module and Pneumatics Control Module. It also includes a CAN interface for logging current, temperature, and battery voltage. For more detailed information, see the [PDP User Manual](https://ctre.download/files/user-manual/PDP%20User's%20Guide.pdf).
+The :ref:`CTRE Power Distribution Panel <docs/software/can-devices/power-distribution-module:Power Distribution Module>` (PDP) is designed to distribute power from a 12VDC battery to various robot components through auto-resetting circuit breakers and a small number of special function fused connections. The PDP provides 8 output pairs rated for 40A continuous current and 8 pairs rated for 30A continuous current. The PDP provides dedicated 12V connectors for the Systemcore, as well as connectors for the Voltage Regulator Module and Pneumatics Control Module. It also includes a CAN interface for logging current, temperature, and battery voltage. For more detailed information, see the [PDP User Manual](https://ctre.download/files/user-manual/PDP%20User's%20Guide.pdf).
 
 ## CTRE Power Distribution Panel 2.0
 
@@ -138,7 +138,7 @@ The power supply for an FRC robot is a single 12V 18Ah Sealed Lead Acid (SLA) ba
 
          AndyMark am-3583
 
-The Robot Signal Light (RSL) is required to be either Allen-Bradley 855PB-B12ME522 or AndyMark am-3583.  It is directly controlled by the roboRIO and will flash when enabled and stay solid while disabled.
+The Robot Signal Light (RSL) is required to be either Allen-Bradley 855PB-B12ME522 or AndyMark am-3583.  It is directly controlled by the Systemcore and will flash when enabled and stay solid while disabled.
 
 ## CTRE Pneumatics Control Module
 
@@ -186,7 +186,7 @@ The TalonFX Motor Controller is a brushless motor controller from Cross The Road
   :alt: Victor SPX
   :width: 500
 
-The [Victor SPX Motor Controller](https://store.ctr-electronics.com/victor-spx/) is a CAN or PWM controlled motor controller from Cross The Road Electronics/VEX Robotics. The device is connectorized to allow easy connection to the roboRIO PWM connectors or a CAN bus. The case is sealed to prevent debris from entering the controller. For more information, see the [Victor SPX User Guide](https://ctre.download/files/user-manual/Victor%20SPX%20User's%20Guide.pdf).
+The [Victor SPX Motor Controller](https://store.ctr-electronics.com/victor-spx/) is a CAN or PWM controlled motor controller from Cross The Road Electronics/VEX Robotics. The device is connectorized to allow easy connection to the Systemcore Smart I/O connectors or a CAN bus. The case is sealed to prevent debris from entering the controller. For more information, see the [Victor SPX User Guide](https://ctre.download/files/user-manual/Victor%20SPX%20User's%20Guide.pdf).
 
 ### Talon SRX
 
@@ -327,16 +327,16 @@ The [Servo Hub](https://www.revrobotics.com/rev-11-1855/) from Rev Robotics can
   :alt: Servo Power Module
   :width: 300
 
-The Servo Power Module from Rev Robotics is capable of expanding the power available to servos beyond what the roboRIO integrated power supply is capable of. The Servo Power Module provides up to 90W of 6V power across 6 channels. All control signals are passed through directly from the roboRIO. For more information, see the [Servo Power Module webpage](https://www.revrobotics.com/rev-11-1144/).
+The Servo Power Module from Rev Robotics is capable of powering servos. The Servo Power Module provides up to 90W of 6V power across 6 channels. All control signals are passed through directly from the Systemcore. For more information, see the [Servo Power Module webpage](https://www.revrobotics.com/rev-11-1144/).
 
 ## Microsoft Lifecam HD3000
 
 .. image:: images/control-system-hardware/microsoft-lifecam.png
   :alt: Microsoft Lifecam HD3000
   :width: 300
 
-The Microsoft Lifecam HD3000 is a USB webcam that can be plugged directly into the roboRIO. The camera is capable of capturing up to 1280x720 video at 30 FPS. For more information about the camera, see the [Microsoft product page](https://www.microsoft.com/en/accessories/business/lifecam-hd-3000-for-business). For more information about using the camera with the roboRIO, see the :ref:`Vision Processing <docs/software/vision-processing/index:Vision Processing>` section of this documentation.
+The Microsoft Lifecam HD3000 is a USB webcam that can be plugged directly into the Systemcore. The camera is capable of capturing up to 1280x720 video at 30 FPS. For more information about the camera, see the [Microsoft product page](https://www.microsoft.com/en/accessories/business/lifecam-hd-3000-for-business). For more information about using the camera with the Systemcore, see the :ref:`Vision Processing <docs/software/vision-processing/index:Vision Processing>` section of this documentation.
 
 ## Image Credits
 
-Image of roboRIO courtesy of National Instruments. Image of DMC-60 courtesy of Digilent. Image of SD540 courtesy of Mindsensors. Images of Jaguar Motor Controller, Talon SRX, Victor 888, Victor SP, and Victor SPX courtesy of VEX Robotics, Inc. Image of SPARK MAX, SPARK Flex, Servo Hub, ATO Breakers, Power Distribution Hub, and Pneumatic Hub courtesy of REV Robotics. Images of TalonFX, TalonFXS, and Power Distribution Panel 2.0 courtesy of Cross The Road Electronics, LLC. Image of Thrifty Nova courtesy of The Thrifty Bot. Lifecam, PDP, PCM, SPARK, and VRM photos courtesy of *FIRST*\ |reg|. Image of the VH-109 radio courtesy of Vivid-Hosting. All other photos courtesy of AndyMark Inc.
+Image of DMC-60 courtesy of Digilent. Image of SD540 courtesy of Mindsensors. Images of Jaguar Motor Controller, Talon SRX, Victor 888, Victor SP, and Victor SPX courtesy of VEX Robotics, Inc. Image of SPARK MAX, SPARK Flex, Servo Hub, ATO Breakers, Power Distribution Hub, and Pneumatic Hub courtesy of REV Robotics. Images of TalonFX, TalonFXS, and Power Distribution Panel 2.0 courtesy of Cross The Road Electronics, LLC. Image of Thrifty Nova courtesy of The Thrifty Bot. Lifecam, PDP, PCM, SPARK, and VRM photos courtesy of *FIRST*\ |reg|. Image of the VH-109 radio courtesy of Vivid-Hosting. Image of SystemCore courtesy of Limelight. All other photos courtesy of AndyMark Inc.

source/docs/controls-overviews/images/control-system-hardware/roborio.png

@@ -147,7 +147,7 @@ Batteries need to be kept away from both extreme heat and cold. This generally m
 
 ## Battery Best Practices
 
-- Only use a charged battery for competition matches. If you are in a situation where you have run out of charged batteries, please ask a veteran team for help! Nobody wants to see a robot dead on the field (:ref:`brownout <docs/software/roborio-info/roborio-brownouts:roboRIO Brownout and Understanding Current Draw>`) due to a bad or uncharged battery.
+- Only use a charged battery for competition matches. If you are in a situation where you have run out of charged batteries, please ask a veteran team for help! Nobody wants to see a robot dead on the field (:ref:`brownout <docs/software/systemcore-info/roborio-brownouts:roboRIO Brownout and Understanding Current Draw>`) due to a bad or uncharged battery.
 
 - Teams are strongly recommended to use properly rated tools and stringent quality control practices for crimping processes (ask local veteran teams or a commercial electrician for help), or use vendor-made Battery Leads.
 

source/docs/controls-overviews/images/control-system-hardware/systemcore.png

@@ -43,7 +43,7 @@ The RS-232 bus can also be used through the `MXP expansion port`_.
 
 The roboRIO RS-232 serial port uses RS-232 signaling levels (+/- 15v). The MXP serial port uses CMOS signaling levels with a 3.3v output, and a 3.3v to 5v tolerant input.
 
-.. note:: By default, the onboard RS-232 port is utilized by the roboRIO's serial console. In order to use it for an external device, the serial console must be disabled using the :ref:`Imaging Tool <docs/zero-to-robot/step-3/imaging-your-roborio:Imaging your roboRIO 1>` or :ref:`docs/software/roborio-info/roborio-web-dashboard:roboRIO Web Dashboard`.
+.. note:: By default, the onboard RS-232 port is utilized by the roboRIO's serial console. In order to use it for an external device, the serial console must be disabled using the :ref:`Imaging Tool <docs/zero-to-robot/step-3/imaging-your-roborio:Imaging your roboRIO 1>` or :ref:`docs/software/systemcore-info/roborio-web-dashboard:roboRIO Web Dashboard`.
 
 ## USB Client
 

source/docs/hardware/hardware-basics/robot-battery.rst

@@ -36,7 +36,7 @@ If this ping succeeds, but the .local ping fails, it is likely that either the r
 .. image:: images/roborio-troubleshooting/roborio-ip-address.png
    :alt: The IP address from the roboRIO webdashboard.
 
-If you are troubleshooting an Ethernet connection, it may be helpful to first make sure that you can connect to the roboRIO using the USB connection. Using the USB connection, open the :ref:`roboRIO webdashboard <docs/software/roborio-info/roborio-web-dashboard:roboRIO Web Dashboard>` and verify that the roboRIO has an IP address on the ethernet interface. If you are tethering to the roboRIO directly this should be a self-assigned ``169.*.*.*`` address, if you are connected to the VH-109 radio, it should be ``10.TE.AM.2`` where TEAM is your five digit FRC team number(:ref:`TE.AM IP Notation <docs/networking/networking-introduction/ip-configurations:TE.AM IP Address Notation>`). If the only IP address here is the USB address, verify the physical roboRIO ethernet connection. If the IP address is ``10.TE.AM.XX``, ensure you've :ref:`set the roboRIO team number <docs/zero-to-robot/step-3/roborio2-imaging:Setting the roboRIO Team Number>`
+If you are troubleshooting an Ethernet connection, it may be helpful to first make sure that you can connect to the roboRIO using the USB connection. Using the USB connection, open the :ref:`roboRIO webdashboard <docs/software/systemcore-info/roborio-web-dashboard:roboRIO Web Dashboard>` and verify that the roboRIO has an IP address on the ethernet interface. If you are tethering to the roboRIO directly this should be a self-assigned ``169.*.*.*`` address, if you are connected to the VH-109 radio, it should be ``10.TE.AM.2`` where TEAM is your five digit FRC team number(:ref:`TE.AM IP Notation <docs/networking/networking-introduction/ip-configurations:TE.AM IP Address Notation>`). If the only IP address here is the USB address, verify the physical roboRIO ethernet connection. If the IP address is ``10.TE.AM.XX``, ensure you've :ref:`set the roboRIO team number <docs/zero-to-robot/step-3/roborio2-imaging:Setting the roboRIO Team Number>`
 
 ## Disabling Network Adapters
 

source/docs/hardware/sensors/serial-buses.rst

@@ -100,7 +100,7 @@ To begin, ensure you are on the :guilabel:`Monitor` tab and click :guilabel:`Hea
    :alt: Location of heap dump button in VisualVM
    :width: 700
 
-This heap dump will be stored on the target system (SystemCore) and must be retrieved using SFTP. See :doc:`this article </docs/software/roborio-info/roborio-ftp>` for information on retrieving the dump from the SystemCore.
+This heap dump will be stored on the target system (SystemCore) and must be retrieved using SFTP. See :doc:`this article </docs/software/systemcore-info/roborio-ftp>` for information on retrieving the dump from the SystemCore.
 
 Once downloaded, the dump can be analyzed with VisualVM.
 

source/docs/networking/networking-introduction/roborio-network-troubleshooting.rst

@@ -35,4 +35,4 @@ By default the deploy directory in your project is transferred to the SystemCore
 
 This will overwrite any duplicate files found in the ``/home/systemcore/deploy`` directory on the RIO and copy over any additional not present there.  If ``deleteOldFiles`` is false it will not remove any files no longer present in the project deploy directory.  Changing it to `true` helps prevent programs like :doc:`Choreo </docs/software/pathplanning/choreo/index>` and [PathPlanner](https://github.com/mjansen4857/pathplanner) from getting confused by files that were deleted locally but still exist on the SystemCore.
 
-If you want to manage the SystemCore files directly, the :doc:`FTP documentation </docs/software/roborio-info/roborio-ftp>` provides one method to do so.
+If you want to manage the SystemCore files directly, the :doc:`FTP documentation </docs/software/systemcore-info/roborio-ftp>` provides one method to do so.

source/docs/software/advanced-gradlerio/profiling-with-visualvm.rst

@@ -55,7 +55,7 @@ This will cause the JVM to write heap dumps to a file named ``frc-usercode.hprof
 
 .. warning:: Configuring the JVM this way requires that the flash drive remain connected to the roboRIO while your code is running.
 
-Larger SD cards may provide enough onboard storage to allow the use of these options on the roboRIO 2 without a USB flash drive. To do this, set the ``-XX:HeapDumpPath`` option to reference a path on the SD card, and use :doc:`FTP/SFTP to transfer the heap dump to a computer </docs/software/roborio-info/roborio-ftp>` before deleting it from the SD card.
+Larger SD cards may provide enough onboard storage to allow the use of these options on the roboRIO 2 without a USB flash drive. To do this, set the ``-XX:HeapDumpPath`` option to reference a path on the SD card, and use :doc:`FTP/SFTP to transfer the heap dump to a computer </docs/software/systemcore-info/roborio-ftp>` before deleting it from the SD card.
 
 Note that the JVM will **not** overwrite heap dumps with the exact path and filename specified by ``-XX:HeapDumpPath`` if they already exist, nor will it dump the process heap to a file with a different name. If a path to a directory is supplied instead of a path to a file, the JVM will instead write out heap dumps with unique filenames within the specified directory, with the name ``java_pidNNNN.hprof``, where ``NNNN`` is the process ID of the JVM that ran out of memory. Note that this can cause large files to build up on disk if they are not cleaned out, so if you configure the JVM this way, be sure to frequently copy heap dumps to a computer and delete them from the flash drive/SD card afterward.
 
@@ -77,7 +77,7 @@ If you continue to run out of memory even after investigating with VisualVM and
 - Periodically calling the garbage collector
 - Setting up swap on a USB flash drive
 
-Implementing most of these options require :doc:`connecting with SSH </docs/software/roborio-info/roborio-ssh>` to the roboRIO and running commands. If run incorrectly, it may require a reimage to recover, so be careful when following the instructions.
+Implementing most of these options require :doc:`connecting with SSH </docs/software/systemcore-info/roborio-ssh>` to the roboRIO and running commands. If run incorrectly, it may require a reimage to recover, so be careful when following the instructions.
 
 ### Setting sysctls