Micah Andelman

ENES100 OTV

Class
ENES100, Introduction to Engineering Design
When
Fall 2026
Role
Electrical subsystem and navigation code on an eight-person team
Built with
Arduino UNO R4 WiFi, C++, arduino-cli, GitHub Actions, Claude Code
Status
Rewiring the robot before the final arena run

Skip the 3D tour

An autonomous vehicle for ENES100's water-sampling mission. An overhead camera tells it where it is in the arena. At the pool it lowers an arm, measures the water's depth, checks it for pollution and pumps a sample. Then it follows the wall past the obstacles and drives under the limbo to the goal.

I designed the robot's entire electrical subsystem: power, motor drivers, sensors and wiring. I also implemented my navigation code with subsystem sketches from my teammates, who each wrote and calibrated one part as its own Arduino sketch, and I merged everything into one codebase and fixed whatever broke. I test everything in ENES100's browser simulator first, and a single build flag switches the same code between the simulator and the real robot.

40/40
randomized simulator runs passed
1,620
lines of firmware

On the bench

These photos show the working prototype. Its wiring kept slipping or falling out, so I rewired it to make it reliable and presentable, and before the final run I am rewiring it again so it looks cleaner and runs more smoothly.

The OTV prototype on a lab bench, seen from the side: an ArUco marker on dowels above the deck, the sampling arm with its sensor mount reaching over a black container, and a drive wheel
The arm with its sensor mount, the ArUco marker the overhead camera tracks, and one of the drive wheels.
The OTV prototype from above, showing the ArUco marker, two SG90 servos, the arm and the wiring on the deck
From above, with the two SG90 servos that move the arm.
The ENES100 arena: a gray floor with white target squares, blue lines and white obstacle blocks at the far end, inside a wooden border
The 4 × 2 m ENES100 arena, with the obstacles at the far end.

The OTV in 3D

From the team's Onshape CAD. Arduino, breadboard and wiring added from photos.

  1. 01 / 06

    The robot

    A plywood deck on two drive wheels and a caster, 21.7 cm wide, 24.1 cm long with the arm down and about 16 cm tall to the top of the ArUco marker. It has to stay under 3 kg and fit under the limbo.

  2. 02 / 06

    Drive

    Two JGY370 worm-gear motors, 6 V and 30 RPM, each turning an 8 cm wheel directly, with a caster at the back. Running the sides at different speeds steers it and lets it turn in place.

  3. 03 / 06

    Brains

    An Arduino UNO R4 WiFi. The overhead vision system tracks the ArUco marker on top and sends position and heading over Wi-Fi. It has to stop within 150 mm of the pool.

  4. 04 / 06

    Arm

    A printed arm between two SG90 servos. One motion swings it down over the pool, so the sensors at the tip face the water and the intake tube dips in.

  5. 05 / 06

    Depth

    The HC-SR04 at the tip times a ping off the water to measure how deep it is. The reading has to be right within 4 mm.

  6. 06 / 06

    Sample

    A peristaltic pump, switched by a MOSFET on D10, pulls at least 20 mL up the tube. The sample has to stay on board until the end of the run.

Overhead visionArUco marker, over Wi-Fi Front ultrasonicHC-SR04, obstacles Arm ultrasonicHC-SR04, water depth Color sensorPollution check ArduinoUNO R4 WiFi1,620 lines of C++ DRV8871, leftDrive motor DRV8871, rightDrive motor Sampling arm2 × SG90 servo PumpMOSFET switched 9.6 V packMain power 5 V converterLM2596 step-down

Select a part to see what it does, how it is wired and the code that runs it.

The course run in 3D

  1. 01 / 08

    Start

    It starts in a random square, A or B, facing a random way. An overhead camera finds the ArUco marker on top and sends position and heading over Wi-Fi. If that signal drops out, the robot stops and waits for it.

  2. 02 / 08

    To the pool

    It turns in place to face the pool, with wheel speed proportional to how far off its heading is, then drives at it. It has to stop within 150 mm of the edge.

  3. 03 / 08

    Sample

    The arm comes down one degree at a time. The HC-SR04 pings the water several times and keeps the median for the depth. The color sensor calls the water polluted if any channel sees a strong non-black color. The pump pulls at least 20 mL up the hose.

  4. 04 / 08

    Back off

    Arm up. It backs away from the pool and turns toward the top wall.

  5. 05 / 08

    To the wall

    Up to the top wall, then along it, 12.5 cm off. The front HC-SR04 watches ahead the whole way.

  6. 06 / 08

    Obstacles

    Along the wall past both obstacle rows. Underneath: a worm-gear motor for each wheel in a printed mount, the rear caster and the front HC-SR04, which only calls an obstacle after several close pings in a row.

  7. 07 / 08

    Limbo

    Down into the 56 cm limbo lane and under the bar, which clears the floor by 18.4 cm.

  8. 08 / 08

    Goal

    In the goal zone. In 40 randomized simulator runs it never went more than 1 mm past a wall and cleared the obstacles by 1.6 to 2 cm.

Top-down map of the 4 by 2 meter ENES100 arena with the route the OTV drives: start square, mission site, up to the top wall, along it past two obstacle rows, then down through the limbo to the goal.

The route my code drives in ENES100's simulator, drawn to scale on the 4 × 2 m arena. The robot starts in a random square and samples the pool in the other one. It then drives up to the top wall, follows it through the 25 cm gap past both rows of obstacles, and cuts down to the limbo lane to reach the goal. I checked 40 randomized runs against the robot's footprint. It never went more than 1 mm past a wall, and it cleared the obstacles by 1.6 to 2 cm.

Questions about this project, or looking for an intern? [email protected]