🔧 Hardware · All Roles · Intermediate

V5 Motor Troubleshooting

Symptom → cause → fix. Use this when a motor is behaving wrong and you need to diagnose it in under 5 minutes. Also includes a pit diagnostic protocol for between-match emergencies.

When to use this: A motor is behaving unexpectedly — too hot, wrong speed, not responding, or acting erratically. Read the symptom row that matches what you're seeing.

🔍 Symptom → Cause → Fix Table

Symptom	Most likely cause	Fix
Motor overheating (temp warning on Brain)	Gear ratio too high, mechanism jammed, or motor running stalled against hard stop	Check for jams. Verify the gear ratio matches the motor's RPM setting in code. Add motor temperature monitoring with `motor.get_temperature()`. Consider a different cartridge.
Port not responding (Brain shows "?" on port)	Loose cable connection, damaged port, or wrong port number in code	Reseat the cable both ends — firm click. Try a different known-good port. Swap cable. If port is dead, reassign to an open port and update code.
Motor runs at wrong speed or reverses unexpectedly	Wrong cartridge installed, reversed polarity in code, or incorrect gear ratio	Check physical cartridge color (red=100rpm, green=200rpm, blue=600rpm) matches code. Check port sign — negative reverses direction. Verify gear ratio constant.
Motor shakes or vibrates under load	Shaft misalignment, loose shaft collar, or missing bearing	Every shaft needs support on both ends. Check all collars. Verify shaft is not bent — roll on flat surface. Add bearing block if missing.
Motor makes grinding noise	Mechanism collision inside motor, gear mesh too tight, or debris in gearbox	Run motor unloaded — still grinding? Replace motor. If only under load: check gear mesh distance and alignment.
Motor loses position under load (arm drops)	PID not tuned for holding, or brake mode not set	Set `motor.set_brake_mode(pros::E_MOTOR_BRAKE_HOLD)`. Alternatively add position hold in code: if joystick near zero, hold last position.
Motor spins freely when it should hold	Brake mode set to COAST instead of HOLD	Check brake mode setting in code. Should be `HOLD` for arms and lifts, `BRAKE` for drive motors.
Motor stutters or cuts out intermittently	Damaged cable, borderline port connection, or brownout under load	Wiggle cable while robot is running — if symptoms change, replace cable. Check battery charge. Add current limiting in code if motor draws spikes.
Motor draws too much current (brownout)	Mechanism physically blocked, or too much load on cartridge	Check for jams at full range of motion. Consider higher-torque cartridge (lower RPM). Distribute load across more motors if possible.
All motors slow down simultaneously	Battery low or bad connection	Check battery level. Swap for a fully charged battery. Check battery cable seating. Inspect battery connector pins for damage.

⏱ 5-Minute Pit Diagnostic Protocol

Use between matches when a motor is misbehaving. You have 3–5 minutes. Do these steps in order and stop when you find the problem.

Check the Brain port screen. Any port showing "?" = bad cable or dead port. Any port showing red temp = overheating. Takes 10 seconds.

Reseat all cables on the affected subsystem. Press each cable until you feel a click. Particularly the motor end. Do not skip this step — loose cables cause 40% of "broken motor" reports.

Move the mechanism by hand with robot off. Does it move freely through its full range of motion? Any hard stop, resistance, or grinding = mechanical problem. Any clicking = loose shaft collar or bearing.

Run a quick driver test. Power on. Drive normally for 30 seconds. Does the problem reproduce? Note exactly when it happens: startup, sustained use, under load, or during specific maneuver.

If motor is physically damaged, swap it. A motor swap takes 90 seconds with practice. Do not attempt complex repairs between matches. Swap now, diagnose at home.

🌡 Understanding Motor Temperatures

Temperature	Status	Action
Under 40°C	Normal operating temperature	None needed
40–55°C	Warm but functional	Monitor. Consider reducing load or speed
55–65°C	Hot — performance may reduce	V5 motors throttle power above 55°C. Fix the root cause (jam, ratio, overuse)
65°C+	Motor protecting itself	Stop immediately. Let cool 5+ minutes. Diagnose root cause before running again

Read temperature in code: int temp = motor.get_temperature(); — returns Celsius as integer.

⚙ STEM Highlight Physics: Thermal Physics & Motor Overload Diagnosis

Motor overheating applies thermal physics: power dissipated as heat equals I squared times R. When a motor is stalled or heavily loaded, current spikes while velocity drops to zero — maximum heat, minimum cooling from airflow. VEX V5 motors have thermal protection at 85 degrees C. The root cause is almost always mechanical: binding, undersized gear reduction, or load exceeding continuous torque rating.

🎤 Interview line: “When a motor overheats, we diagnose the root cause before replacing it. We measure the mechanism load and calculate whether the gear ratio can deliver the required torque. Three of our motor failures this season were traced to the same root cause: insufficient gear reduction for the load. Fixing the ratio eliminated the failures; replacing the motor alone would have reproduced them.”

A motor reads 127C after a 2-minute practice session. The thermal limit is 85C. What is the correct diagnosis?

⬛ The motor is defective — replace it

⬛ The motor is overloaded — gear ratio is too demanding, mechanism is binding, or wrong cartridge for the load

⬛ This temperature is normal during matches

📝

Notebook entry tip: Build & Program — Orange slide — Write a motor maintenance entry whenever a motor overheats, stalls, or is replaced: symptom, temperature reading, gear ratio and load, root cause, and fix applied. If you changed cartridge or ratio, record before/after temperature data. A maintenance log shows judges that hardware was managed systematically — failures triggered investigation, not just part swaps.