diff --git a/content/Glossary/A-Stop (Autonomous Stop).md b/content/Glossary/A-Stop (Autonomous Stop).md new file mode 100644 index 0000000..79f48d8 --- /dev/null +++ b/content/Glossary/A-Stop (Autonomous Stop).md @@ -0,0 +1,7 @@ +The A-Stop is a physical button which will disable the robot temporarily until the [[Teleoperated Period (Teleop)]] starts. + +As of 2024, the A-Stop button at competition is red and looks like this: + +![[Pasted image 20241217183900.png]] + +Not to be confused with the [[E-Stop (Emergency Stop)]] button. \ No newline at end of file diff --git a/content/Glossary/A-Stop.md b/content/Glossary/A-Stop.md deleted file mode 100644 index 3c6a19b..0000000 --- a/content/Glossary/A-Stop.md +++ /dev/null @@ -1 +0,0 @@ -The A-Stop is a physical button which will disable the robot temporarily until the [[Teleoperated Period (Teleop)]] starts. \ No newline at end of file diff --git a/content/Glossary/E-Stop (Emergency Stop).md b/content/Glossary/E-Stop (Emergency Stop).md index 30404ce..8e228ea 100644 --- a/content/Glossary/E-Stop (Emergency Stop).md +++ b/content/Glossary/E-Stop (Emergency Stop).md @@ -1 +1,5 @@ -TODO \ No newline at end of file +The E-Stop is a physical button that forcibly stops all activity on the robot. After pressing E-Stop, the robot will be inoperable and must be rebooted. To be used only when the robot is out of control or otherwise in an emergency situation. + +When not hooked up to the [[FMS (Field Managment System)|FMS]], pressing the space bar on the [[Driver Station]] computer will E-Stop the robot. + +Not to be confused with the [[A-Stop (Autonomous Stop)]] button. \ No newline at end of file diff --git a/content/Glossary/Enabled & Disabled.md b/content/Glossary/Enabled & Disabled.md new file mode 100644 index 0000000..7cda321 --- /dev/null +++ b/content/Glossary/Enabled & Disabled.md @@ -0,0 +1,18 @@ +When an FRC robot is "enabled", it is actively running the robot program and may move and perform actions. When a robot is "disabled", it is prevented from operating mechanisms, but may still run background portions of the robot program. + +When the robot is enabled, the [[RSL (Robot Signal Light)]] will continuously flash. When disabled, the RSL will be solid. + +When not connected to the [[FMS (Field Managment System)|FMS]], the robot may be disabled at any time by pressing the Enter key. + +**NEVER REACH INSIDE A ROBOT WHEN IT IS ENABLED.** An enabled robot may do anything at any time. Serious injuries may occur if you reach inside an enabled robot. + +**ALWAYS RESPECT A ROBOT'S SPACE WHEN IT IS ENABLED.** Robots move quickly and unpredictably, and may reach outside their frame with various mechanisms. + +## Enabling procedure + +For safety, we always observe the following procedure when enabling the robot: + +1. Look at the robot and ensure that no one has any part of their body on or in the robot, or is otherwise actively working on it. +2. **Loudly** say the word "ENABLING!" so that everyone can hear. +3. Enable the robot. + diff --git a/content/Glossary/Endgame.md b/content/Glossary/Endgame.md index 87073b0..e208109 100644 --- a/content/Glossary/Endgame.md +++ b/content/Glossary/Endgame.md @@ -4,4 +4,4 @@ A final objective to perform at the end of the [[Teleoperated Period (Teleop)]], - Balancing on seesaws - Deploying miniature robots to race up poles -The time for endgame objectives is often signaled by a loud noise, such as a train whistle, fanfare, or guitar riff. \ No newline at end of file +The time for endgame objectives is often signaled by a loud noise, such as a train whistle, fanfare, or guitar riff. For details, see the current [[Game Manual]]. \ No newline at end of file diff --git a/content/Glossary/FMS (Field Managment System).md b/content/Glossary/FMS (Field Managment System).md new file mode 100644 index 0000000..e10bd52 --- /dev/null +++ b/content/Glossary/FMS (Field Managment System).md @@ -0,0 +1,5 @@ +The Field Management System is _FIRST_'s field system at competition. It connects to all the teams' [[Driver Station]] computers and [[Enabled & Disabled|enables and disables]] the robots in lockstep. It also connects to field elements, referee consoles, team number displays, etc. and automates the scorekeeping and visuals of the game. + +At competition, drivers connect the [[Driver Station]] to the FMS via Ethernet. The FMS then takes over control of the Driver Station. + +For technical details of the FMS, see the [FMS whitepaper](https://wpilib.screenstepslive.com/s/fms/m/whitepaper/l/608744-fms-whitepaper). diff --git a/content/Glossary/Radio.md b/content/Glossary/Radio.md index 1eb9c83..86435c3 100644 --- a/content/Glossary/Radio.md +++ b/content/Glossary/Radio.md @@ -1,7 +1,7 @@ --- author: Idrees Ahmad --- -A small Wi-Fi router that maintains wireless communication between the [[Driver Station]] and [[Robot]]. Prior to the 2025 season, this consisted of an OpenMesh radio, however, this has now been replaced with the Vivid-Hosting VH-109. +A small Wi-Fi router that maintains wireless communication between the [[Driver Station]] and robot. Prior to the 2025 season, this consisted of an OpenMesh radio, however, this has now been replaced with the Vivid-Hosting VH-109. ![[WCP-1538_2048x2048 Medium 1.png]] diff --git a/content/Glossary/SPARK MAX.md b/content/Glossary/SPARK MAX.md index 3a91aa2..fe9fda5 100644 --- a/content/Glossary/SPARK MAX.md +++ b/content/Glossary/SPARK MAX.md @@ -6,4 +6,13 @@ The SPARK MAX is most commonly used to control the [[NEO]] and [[NEO 550]] brush The SPARK MAX supports multiple control modes, including built-in [[PID (Closed-Loop Control))|closed-loop]] control, and the ability for multiple SPARK MAXes to mirror each other in a leader/follower configuration. It also has a data port on top which can be used with external sensors, such as the [REV Through Bore Encoder](https://www.revrobotics.com/rev-11-1271/) inside a [[MAXSwerve]] module. -The SPARK MAX connects to the [[roboRIO]] via [[CAN]]. It can be configured using the proprietary [REV Hardware Client](https://docs.revrobotics.com/rev-hardware-client). \ No newline at end of file +The SPARK MAX connects to the [[roboRIO]] via [[CAN]]. It can be configured using the proprietary [REV Hardware Client](https://docs.revrobotics.com/rev-hardware-client). + +## Status LED + +The SPARK MAX has a status LED that displays a variety of colors and patterns to indicate different modes and error conditions. We encourage you to visit and bookmark the following page: https://docs.revrobotics.com/brushless/spark-max/status-led + +## Resources + +- Documentation: https://docs.revrobotics.com/brushless/spark-max/overview +- Software resources: https://docs.revrobotics.com/brushless/revlib/revlib-overview diff --git a/content/Images/Pasted image 20241217183900.png b/content/Images/Pasted image 20241217183900.png new file mode 100644 index 0000000..c8ed7ea Binary files /dev/null and b/content/Images/Pasted image 20241217183900.png differ