2. The Hardware Paradigm

To program a physical FRC mechanism effectively, you must understand the constraints of the electrical signals traveling exactly underneath your code. In FRC, code doesn’t just run; it actively bridges power systems and data packets.

1. The RoboRIO (The Brain)

The NI RoboRIO 2.0 is an embedded Linux computer. This is where your compiled Java code actually lives and executes. Every 20 milliseconds, the RoboRIO evaluates your code, parses sensor data, and issues torque commands outward.

2. The FRC Radio (The Network)

The RoboRIO does not have native WiFi. A separate module—the Radio (like the Vivid-Hosting VH-109 or OpenMesh)—must be physically ethernet-connected to the RIO. Your laptop talks securely to the Radio, which then pipelines the connection.

Caution

FMS vs Pit Strategy

When you are in the Pit or at home, you configure the Radio to emit a standard 5GHz WiFi signal or you plug an Ethernet/USB-B cord directly into the RoboRIO to deploy code.

At official competitions, you must use the Radio Kiosk. This physically rewrites your Radio’s firmware to bind directly to the official Field Management System (FMS). Once hooked to FMS, your laptop connects via Ethernet to a Driver Station pedestal on the field boundary, ensuring extreme security.

3. The CAN Bus (The Nervous System)

The RoboRIO does not directly spin motors. Instead, it “talks” to them using a protocol called CAN (Controller Area Network).

• The CAN Bus is a literal yellow and green wire daisy-chained sequentially through every motor controller.

• Because data flows serially, every motor requires a unique CAN ID (a number from 1 to 60) so the RoboRIO can target exactly who to command.

• The CANivore: MARSLib utilizes CTRE hardware heavily. Standard RoboRIO CAN processing becomes bogged down around 50% utilization. We route all drivetrain components into a separate USB CANivore card, isolating high-bandwidth torque streams and speeding up loop times substantially.

4. Power Shedding & Brownouts

An FRC battery supplies ~12V of DC electricity. However, when 14 different high-torque motors try to pull max acceleration simultaneously, the physical laws of electric load cause the battery voltage to momentarily crash down toward 6.0V.

If the voltage drops below 6.3V, the RoboRIO forcefully severs all motor connection to prevent the main CPU from dying. This is known as a Brownout. In MARSLib, we must dynamically shed power and strictly enforce motor current caps to avoid stalling the battery.

---

📖 Further Reading & External Resources

• WPILib “Zero to Robot” Guide - The official foundational pipeline for FRC control systems.

• FRC 0 to Auto Youtube Series - Outstanding video tutorials exploring command-based programming for novices.

• WPILib Command-Based Documentation - Deep dive into Subsystem and Command scheduling architecture.