Background

Motorboard

The Motorboard: A Proven Foundation for RoboCup Success

The Motorboard served as the reliable powerhouse behind our RoboCup soccer robots. Engineered to bridge the gap between high‑current demand and precision control, it successfully managed five independent brushless DC (BLDC) motor drives. Every design choice, from the isolated power architecture to the signal conditioning, was built to withstand the chaotic environment of a competitive robot match.

Robust Power Architecture

To handle the high energy requirements of high‑speed maneuvers, the board operated on an 18.5 V Lithium Polymer (LiPo) battery. A key highlight of the design was the strict separation between the "brawn" and the "brains."

Dual‑Rail Power Tree

The board utilized a split power tree to ensure stability. While the motors drew directly from the high‑voltage rail, the logic components were powered by a dedicated low‑power side. This side used Buck Converters—efficient switching regulators that "stepped down" the battery voltage to 5 V and 3.3 V. Unlike simpler regulators that burn off excess voltage as heat, these converters kept the board cool and preserved battery life.

Safety‑First Boot Sequence

The board featured a hardware‑level enable switch for the high‑power rail. This allowed the system to boot up the microcontroller and sensors first, performing a "pre‑flight" check. Only once the software confirmed the system was healthy would the high‑power side be energized, preventing the motors from spinning unexpectedly during bench testing.

Precision Motor Control and Protection

Each of the five motor channels was driven by a 3‑Phase H‑Bridge. Since BLDC motors require electricity to be pulsed through three different coils in a specific sequence to rotate, these bridges acted as high‑speed electronic gates that managed that flow.

Low‑Side Current Monitoring

To prevent the motors from drawing too much power and damaging the electronics, we implemented low‑side current sensing. A tiny, high‑precision resistor was placed on the ground side of the motor circuit.

  • The Advantage: By placing the resistor on the "low side" (near 0 V), we could use a standard Differential Amplifier to measure the current. This kept the circuit simple and cost‑effective, as it didn't need to handle the high‑voltage spikes found on the "high side" of the motor.

Hardware Overcurrent Trip

Beyond software monitoring, the board featured a dedicated Overcurrent Detector. A resistor divider set a specific "trip point"; if the current spiked instantly—perhaps due to a stalled motor or a collision—the hardware would shut down the channel faster than the software could react, saving the transistors from thermal failure.

Signal Integrity in a Noisy Environment

Soccer robots generate significant electrical noise and physical vibrations. The Motorboard used specialized components to ensure the feedback signals remained crystal clear:

  • Differential Line Receivers: Motor encoders track the exact position of the wheels using "differential signaling"—sending the same data over two wires with opposite polarities. The board's receivers compared these two signals, effectively "subtracting" any interference picked up from the nearby high‑power motor wires.
  • Schmitt Triggers: To handle signal "bounce" caused by robot vibrations, we used Schmitt Triggers. These components use hysteresis, meaning they have two different voltage thresholds for turning a signal "on" or "off." This prevents a noisy signal from flickering back and forth and confusing the microcontroller.

Diagnostics and Mechanical Integration

The board was designed to be as easy to fix as it was to run.

  • Visual Status: Each motor channel was equipped with a Status LED tied directly to the high‑side power switch. This provided an instant visual confirmation of which motors were active, eliminating the need to probe the board with a multimeter during a frantic halftime repair.
  • High‑Speed Communication: The board communicated with the main controller via two protocols: UART for low‑bandwidth diagnostic logs and SPI for the high‑speed timing required to coordinate complex robot movements.
  • Reliable Interconnects: We utilized Slimstack connectors, chosen for their low physical profile and high "mate‑cycle" rating. This allowed the board to be removed and re‑installed dozens of times throughout a season without the connectors wearing out or losing their grip.

The final iteration of the Motorboard proved to be a "set‑and‑forget" component. By focusing on hardware‑level protection and signal clarity, it allowed the team to focus on winning games rather than troubleshooting power failures.