Build Help And Troubleshooting

Nolan’s Quick Fix Guide, 12 Things To Check Before You Panic

Sometimes your ROV acts like it woke up and chose violence. Before anyone starts blaming the laws of physics, here is my calm down checklist. This list exists because I have personally lived the moment where you think the robot is broken, but the robot is actually fine and one wire is just being dramatic.

Step 1, check the tether first

If your ROV is drifting, spinning, or “pulling,” check the tether. A tether can steer your robot like an invisible hand. If it is snagged, twisted, or dragging, your robot will feel “broken” even when it is not.

Nolan rule: If the tether is mad, the robot will be mad.

Step 2, check prop direction and tightness

Prop direction matters. A lot. If you have one motor pushing the wrong way, you are fighting yourself. Also check that props are secure. A loose prop can make a motor feel weak.

Step 3, motor mounts and alignment

Grab each motor and gently try to move it. Any wiggle means your ROV will drive like it is arguing with itself. Even small misalignment changes how it tracks and turns.

Step 4, connections you trust too much

Connections can look perfect and still be the entire problem. Lightly tug each connection. If it moves, fix it. Corrosion or water sneaking into a connection can cause random problems that show up only sometimes, which is the most annoying kind.

Step 5, drag and dangling stuff

Loose wires, long zip ties, floppy foam, anything hanging creates drag. Drag makes turning messy and speed inconsistent. Clean up your frame. Make it sleek.

Step 6, trim and balance

If your robot is nose up, nose down, or rolling, adjust flotation and weight placement. Tiny changes can make a giant difference. It is like moving one kid on a seesaw and suddenly the whole thing changes.

Step 7, test one thing at a time

If you change five things between runs, you learn nothing. Change one thing, test it, record it, decide.

Step 8, verify controls on land

Before pool time, check that each switch and control direction matches what you expect. Fixing it on land is fast. Fixing it while everyone is waiting for their pool lane is not fun.

Step 9, do a baseline run

If something feels wrong, do one baseline run with no changes, just observe. That baseline tells you whether your “fix” actually fixed anything.

Step 10, write down what changed right before it broke

This is the best troubleshooting question on Earth. What changed right before the problem started. That answer is usually the clue.

Step 11, check for human error

Sometimes the robot is fine and we are just tired. Slow down. Small stick movements. Controlled turns. Calm wins.

Step 12, remember this

A design not working is not failure. It is information. Information is good. Engineers love information.

If you are stuck, you are not behind. You are doing engineering.