How to Troubleshoot Common FRC Electrical Problems

A reliable electrical system is the foundation of every FIRST Robotics Competition machine. When a robot refuses to enable, loses a motor during a match or resets as it accelerates, the cause is often a loose connection, an overloaded circuit, a weak battery or a communication fault rather than a mysterious software failure.

Australian teams face the same FRC control-system requirements as teams elsewhere, while working with local school workshops, long travel distances and suppliers that may not stock every specialised part. A disciplined troubleshooting process helps teams in Sydney, Melbourne, Brisbane and regional areas find faults quickly and return to productive testing.

Start With Safety And Symptoms

Disconnect the battery before changing wiring, tightening terminals or reaching inside the robot. Remove jewellery, secure loose clothing and keep the robot firmly supported so wheels cannot touch the floor unexpectedly. A charged 12-volt FRC battery can deliver very high current, making a short circuit capable of melting wire, damaging connectors or causing burns.

Record exactly what happened before taking the system apart. Did the robot fail during startup, lose only one mechanism, reboot when several motors moved, or stop communicating after a sharp impact? A timeline is valuable: an instant failure often points to power or wiring, while a fault that appears after movement may indicate a broken conductor, CAN connection or mechanical overload.

Teams do not need an expensive laboratory to begin. A quality multimeter, insulated probes, spare fuses where permitted, crimping tools, a terminal screwdriver and labelled test leads cover many first checks. Community workshops, school technicians and library maker programmes can also provide useful equipment; supporters such as the Friends of the Library show how community organisations can help maintain access to practical learning resources.

Check The Battery And Main Power Path

Begin at the battery and follow the complete high-current path: battery connector, main breaker, power distribution hardware, motor-controller feeds and return connections. Inspect for loose Anderson contacts, damaged housings, overheated lugs, crushed cable insulation and terminals that can be moved by hand. A connector may look connected while its internal contact has backed out.

Measure battery voltage with the robot disabled, then observe it while the drive train accelerates. A healthy, fully charged FRC battery commonly reads close to 12.5–13 volts at rest, but the important clue is how far the voltage falls under load. A severe drop suggests an aged battery, poor connection or excessive current demand. Rotate batteries through testing rather than assuming a battery is good because it worked in the previous event.

Use only approved FRC batteries, chargers and wiring practices. Australian mains power uses 230 volts, so battery charging stations need appropriate protection, ventilation and supervision. Do not improvise with household power cables, automotive jump leads or unapproved adapters simply because they are easy to obtain from a local hardware shop.

Investigate Breakers And Power Distribution

A tripped breaker is evidence, not the root cause. Determine which branch opened and what was operating at that moment. A motor drawing excessive current because a gearbox is jammed, a chain is too tight or a mechanism has reached its hard stop can repeatedly trip the same channel. Resetting the breaker without removing the mechanical cause can turn an intermittent issue into component damage.

Check the power distribution board or hub for correct polarity, secure screws and signs of heat. Confirm that every branch uses the correct gauge and that wires are not sharing a terminal in a way the rules or device manufacturer does not allow. Label both ends of each cable, especially on a complex competition robot where a reversed feed can consume valuable pit time.

When a branch is dead, test from the source towards the load rather than probing randomly. Verify voltage at the distribution output, at the motor controller input and finally at the controller output when commanded safely. A missing reading identifies the section that deserves closer inspection, while a normal reading under no load does not prove that a connection can carry current.

Trace CAN Bus And Control Wiring

Many FRC motor controllers communicate over the Controller Area Network, commonly called CAN. A single open circuit, reversed pair, poor crimp or loose termination can produce device errors across the bus. Inspect the complete chain and compare every device ID with the robot configuration. Keep CAN wiring twisted, protected from sharp edges and separated from areas where repeated flexing occurs.

Look at diagnostic lights and driver-station messages before replacing hardware. If one controller disappears, isolate the suspected device and test the remaining network. If many devices vanish together, inspect the roboRIO connection, power to the distribution hardware and the common CAN path first. Replacing several controllers at once can hide the actual fault and quickly consume a team’s limited parts budget.

Route signal cables away from pinch points and high-current cable movement. Use strain relief at connectors and leave enough service loop for maintenance without allowing wires to rub on aluminium edges. Photographing a known-good wiring layout is useful when rebuilding between events, especially when a regional team has travelled hours to a competition in Adelaide, Perth or Townsville.

Examine Motor Controllers And Mechanisms

A motor controller may show a fault because of its own electronics, but it may also be reporting a downstream problem. Inspect the three motor leads, connector crimps and mounting points. Look for discolouration, melted insulation or a lead that pulls free under gentle pressure. Brushless motor phases and encoder connections need particular care because a partially seated plug can create erratic operation.

Disconnect the mechanical load where safe and test the motor at low output. If the motor runs unloaded but fails when connected, inspect bearings, shafts, belts, chains and gearboxes. A mechanism that binds near one position can draw high current only during part of its travel, making the problem appear random during driver practice.

Set current limits and ramp rates thoughtfully in software, then confirm they match the motor and mechanism. Current limiting can protect hardware, but it cannot compensate for a seized bearing or incorrect gearing. Record which subsystem fails and exchange components methodically, changing one item at a time so the evidence remains useful.

Separate Software Errors From Electrical Faults

Read the driver station, roboRIO and controller logs before making changes. A robot that is disabled because of an interlock, emergency-stop state, invalid command or watchdog event needs a different response from one that is losing power. Confirm that the expected code version is deployed and that the correct CAN IDs, inversion settings and sensor channels are configured.

Use a known-good test mode with one subsystem enabled at a time. Start with low output, watch battery voltage and listen for unusual sounds. If a motor responds in a simple test but not in the full command sequence, inspect subsystem requirements, button bindings, limit-switch logic and safety conditions. If it fails in every mode, return to power, wiring and hardware checks.

Teams familiar with other youth robotics platforms should remember that the workflow and control hardware differ. For example, FIRST Tech Challenge resources can help explain another FIRST programme, but FRC teams must rely on the current FRC control-system documentation, event rules and device manuals for their robot.

Build A Repeatable Fault-Finding Routine

Use a written checklist at every test session. Note the battery number, match or practice time, subsystem, driver-station message, motor output, voltage readings and recent changes. Assign one person to operate the controls and another to observe measurements; this prevents unsafe movement and gives the team a clear record.

The comparison below can help narrow the first inspection area without treating symptoms as a final diagnosis.

Symptom	Likely First Checks	Useful Confirmation
Robot will not power on	Battery, connector, main breaker, distribution input	Measure voltage at each stage
RoboRIO or controllers reboot	Battery sag, loose high-current connection, excessive load	Watch voltage during acceleration
One motor is missing	Branch wiring, controller power, CAN connection, device ID	Test the motor and controller separately
Several CAN devices disappear	CAN chain, roboRIO connection, common power	Isolate sections of the bus
Breaker trips repeatedly	Jammed mechanism, hard stop, short circuit, current limit	Test unloaded, then add load gradually
Motor stutters or runs backwards	Phase leads, inversion, damaged connector, configuration	Compare with a known-good motor
Fault appears after driving over bumps	Strain relief, crimps, battery seating, frame pinch points	Wiggle-test only while disabled

Before an event, conduct a controlled shake and drive test with the robot raised securely, then repeat under realistic load. Inspect the robot after transport because vibration in a trailer from Canberra to Melbourne can loosen a connector that was perfect in the workshop. Keep a labelled spare harness and a documented wiring diagram in the pit so repairs are based on evidence rather than guesswork.

A strong troubleshooting culture is part of the engineering learning that FRC is designed to provide. Teams should invite mentors, teach students to take measurements, and treat every fault as data. Safe, methodical diagnosis saves money, protects hardware and gives students confidence when the robot behaves unexpectedly.

Bring this process into your next build session by checking the battery path, documenting every controller connection and running one controlled subsystem test at a time. Connect with Maryland FIRST Robotics for programme knowledge, mentoring resources and FIRST community opportunities that help students turn electrical problems into practical engineering experience.