build-guides

Build Roadmap & Philosophy

Master build order, tools needed, and why we test before we integrate

Build Guide: Roadmap & Philosophy

Type: Build Guide

This is the master roadmap for building the Tick Slayer 3000. The build is broken into 9 guides that take you from unboxing parts to autonomous tick runs. Each guide is self-contained — you can stop at the end of any guide and have a working (partial) system.

Build Order

#GuideWhat You'll Have When Done
1Bench Testing ElectronicsEach passive component (multimeter checks, GPS, USB power) verified standalone
2Raspberry Pi SetupPi OS, Python venv, Adafruit libraries, hardware interfaces enabled
3Pi ↔ Hardware IntegrationPi driving every chip end-to-end from Python — servo sweeps, ADC reads, GPS parsed, camera capture
4Vehicle Prep & MountingTRX-4 ready to receive electronics, enclosure and mounts installed
5Wiring & Control IntegrationPi controlling the TRX-4 via PWM — throttle and steering
6First Drive & CalibrationRover driving under Pi control with tuned steering and speed
7Drag Cloth & Sampling RigComplete sampling apparatus attached and dragging properly
8Capture & Navigation SoftwareCamera pipeline, GPS logging, path record/replay all working
9Data Pipeline & First RunFull autonomous run with data flowing to the web app

Reference (not a step): Pi ↔ Dashboard API — every Convex mutation and query the rover code calls, with Python examples.

Why This Order

The build follows a principle: test small, then integrate. Every component gets verified on the bench before it goes on the rover. This means when something doesn't work after integration, you know the problem is in the wiring or connections — not the component itself.

The software and hardware tracks are interleaved intentionally:

Guide 1-3: Bench + Pi work (electronics validated standalone, then Pi-controlled)
Guide 4-5: Physical build & wiring (garage/workshop)
Guide 6:   First drive (outdoor, satisfying milestone)
Guide 7:   Sampling rig (back to the workshop)
Guide 8:   Software deep dive (desk work)
Guide 9:   Full integration & first real run (the payoff)

This keeps things from getting monotonous — you're never doing the same type of work for too long. The Guide 3 → Guide 5 split also means the highest-risk moment (wiring the Pi into a $400 TRX-4) is preceded by validating that the exact same code path works on a $2 spare servo on the desk.

Tools You'll Need

For electronics:

  • Multimeter (voltage and continuity testing)
  • Soldering iron + solder (a few connections required)
  • Wire strippers
  • Small Phillips and flathead screwdrivers
  • Breadboard + jumper wires (for bench testing)
  • Heat shrink tubing or electrical tape

For vehicle assembly:

  • Hex driver set (TRX-4 uses metric hex screws)
  • Zip ties (many)
  • Double-sided mounting tape (VHB or similar)
  • Drill with small bits (for mounting plate, if needed)
  • Velcro straps (for battery + camera mounting)

For the drag cloth:

  • Scissors or rotary cutter
  • Sewing machine or heavy needle + thread
  • PVC cutter or hacksaw (for drag bar)
  • Measuring tape

A Note on Patience

You'll be tempted to skip bench testing and jump straight to mounting everything on the rover. Don't. A 10-minute bench test saves hours of debugging when something doesn't work and everything is zip-tied inside a waterproof box on a moving vehicle. The bench testing guide exists because we learned this the hard way.

Ready?

Start with Guide 1: Bench Testing Electronics and work your way through. Each guide tells you exactly what parts and tools you need before you start, so you can grab everything and set up your workspace once.

Next →Guide 1: Bench Testing Electronics