- Bottom shell: the brace pivot bosses stand on pillars and the lip's tie band steps out at 45 deg (both were floating overhangs); the kickstand barrel sits on the bed. Checked by slicing the STLs layer by layer: only bridges are left. STLs re-exported. - remote_v2_top_multicolor.3mf: now the owner's OrcaSlicer project (all parts on two plates); export_3mf.py regenerates the plain multi-part file. - README "Planned": a USB nRF24 stick on the PC so Unity can talk to both the robot and the remote (what to work out), plus pointers to the other notes for later. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Hexapod
A six-legged walking robot (Teensy 3.6) and its handheld remote (Teensy 4.0 + Nextion touchscreen), linked over nRF24L01.
The remote above is the new design (hardware/openscad/remote_v2.scad, not
printed yet). The original printed remote is on the
archive page.
robot/ robot firmware: IK, gait, body pose, IMU stabilization, state machine
remote/ remote firmware: 2 x 3-axis sticks, MPU6050 tilt, Nextion UI, RF24 TX
shared/ HexapodProtocol: the CmdPacket wire format + radio settings used by both
sim/ the unchanged robot firmware compiled into a DLL for the simulation
Hexapod_Simulation_Unity/ Unity project that runs that DLL on the 3D model
hardware/openscad/ OpenSCAD model of the robot (rebuilt from the Fusion designs) and the new remote
hardware/openscad/stl/ print-ready STL exports
hardware/fusion360/ Fusion 360 designs: body, legs, servo, servo horn, remote case
scripts/ PlatformIO helper (per-environment sketch folder)
This is the 2026-current/ folder of the hexapod-robot repo; the earlier
generations (2009 onwards) are in the folders next to it, see
../README.md.
Build (PlatformIO)
pio run # build both
pio run -e robot -t upload
pio run -e remote -t upload
pio device monitor -e robot
Simulation
From this 2026-current folder in PowerShell (the dev PC is Windows):
.\sim\build.ps1 # build hexapod_sim.dll + run the headless firmware checks
Then open Hexapod_Simulation_Unity and press Play. See
sim/README.md.
Printing the remote (v2)
STLs in hardware/openscad/stl/remote_v2/,
already in print orientation; everything prints in ASA without supports.
Regenerate them from remote_v2.scad with -D 'PART="..."'.
| File | Part | Notes |
|---|---|---|
remote_v2_top_multicolor.3mf |
top shell with both inlays | One object with three parts on filaments 1/2/3: case black, honeycomb red, ON/OFF white. The inlays are the first 3 layers (0.6 mm) of the face-down shell, so the colour swaps only happen there. Made by hardware/openscad/export_3mf.py from the three STLs below |
remote_v2_top.stl + _inlay.stl + _text.stl |
the same, as STLs | Load the three at once and keep them as one multi-part object |
remote_v2_bottom.stl |
bottom shell | flat underside on the bed |
remote_v2_kickstand.stl |
table stand | |
remote_v2_eyelet.stl |
neck-strap eyelet | on the top face (slots to balance it) or on the front edge |
remote_v2_bail.stl |
body brace | swings down and back to rest against your body |
Hardware (besides the electronics of the old remote):
- 14 x M3 heat-set inserts (4.0 mm hole, ~5.7 mm long): 4 shell screws, 2 + 2 eyelet (top and front), 2 brace pivots, 4 main-board clamps
- M3 x 12 x 4 (shells), M3 x 8 button head x 2 (eyelet), M3 x 16 button head + washer x 2 (brace), M3 x 8 button head + 7 mm washer x 4 (main board clamps, no holes in the board), M3 x 40 + nut (kickstand pin)
- M2.5 x 14 x 8 (joysticks, into their own boxes), M2.5 self-tapping x 4 (display), M3 self-tapping x 2 (UPS board), M2 self-tapping x 2 (switch)
- Set the Nextion's display direction to 180 in the Nextion Editor: the display is mounted turned round so its connector clears the Teensy's USB plug.
Design notes, checks and open points: hardware/openscad/PLANNING.md.
Planned
- PC radio link (owner, later): a USB nRF24L01 stick on the PC (it
probably shows up as a serial port), on the same radio as the robot and the
remote, so Unity on the PC can both receive data from (telemetry) and send
data to the robot and the remote. Not designed yet. To work out:
- what the stick's firmware does: many of these sticks are a USB-serial
chip with a microcontroller set up by AT commands (address, channel, data
rate) that passes raw payloads through; check that it can match
HXP_RADIO_*inshared/HexapodProtocol/HexapodProtocol.h(channel 96, 250 kbps, 5-byte addressHXPD1, fixed payload ofsizeof(CmdPacket)) and whether it can do auto-ack and ack payloads; - the radio protocol: today the remote only transmits a
CmdPacketto the robot and nothing comes back. Three nodes need an address per node (or per pipe), a packet type byte, and telemetry back (e.g. as ack payloads or in time slots) so the nodes don't talk over each other; who has priority when the PC and the remote both send commands; - Unity side: a serial-port reader/writer next to the simulation (the
2019 generation already drove the robot from Unity, through the remote
over USB: see
../2019-teensy-nrf24/).
- what the stick's firmware does: many of these sticks are a USB-serial
chip with a microcontroller set up by AT commands (address, channel, data
rate) that passes raw payloads through; check that it can match
- Remote battery level and the IMU on the normal pin headers: see remote/README.md, "Planned".
- Robot power: a stable 6 V supply for the 18 servos, see hardware/openscad/PLANNING.md, "Notes for future designs".
Where to go next
- robot/README.md: placeholder geometry to measure, the bench-check checklist, and the serial test harness for driving the robot without a remote.
- remote/README.md: wiring, control scheme, stick calibration, and the remote's serial console.
- remote/NEXTION.md: how to build the touchscreen HMI.
- shared/HexapodProtocol/HexapodProtocol.h: the protocol. Change it only by reflashing both boards.

