Files
hexapod-robot/2026-current
mangavalkandClaude Opus 5.5 aeccba3be7 2026 remote: wiring as found on the real remote, IMU reset fix
- Nextion is on Serial2 (pins 7/8) - already in the last commit; docs updated.
- MPU6050 on Wire (18/19) so everything is on the edge headers (owner's
  choice); the two stick wires from 18/19 move to A7/A8 (21/22).
- Stick mapping checked on the real remote: left stick X/Y/twist on
  A3/A7/A8, right on A0/A1/A2, all inverted but the right twist.
- RemoteIMU: full device reset before waking. The remote's MPU6050 (likely
  a clone) answers and wakes without it but every data register reads 0.
  Axis defaults confirmed (+pitch nose down, +roll right side down).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-17 22:03:08 +01:00
..

Hexapod

A six-legged walking robot (Teensy 3.6) and its handheld remote (Teensy 4.0 + Nextion touchscreen), linked over nRF24L01.

The hexapod, OpenSCAD model in its standing pose The remote (v2), OpenSCAD model: black ASA with a red honeycomb and white ON/OFF inlay

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
dongle/                    USB nRF24 stick firmware (STM32F030): the PC-side radio, see dongle/README.md
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_inlays.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_top_multicolor.3mf OrcaSlicer project (owner) all parts on two plates; after re-exporting STLs, update its parts with Orca's "Reload from disk"
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 as the PC-side radio, on the same air settings 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. The stick is now reverse-engineered and reflashed with our own firmware (STM32F030 + Si24R1 + AT2401C); it shows up as a COM port and is updated wire-free over USB. See dongle/README.md. Still to do:
    • map the stick's LED and AT2401C power-amp control pins (app toggles them);
    • the radio protocol: today the remote only transmits a CmdPacket to 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. Owner's decisions: the remote wins, with a toggle on the remote that hands the robot to Unity and lets the remote's sticks control Unity instead; the PC is the hub while it's online, the robot is the hub when it isn't; goals: mirror the real robot in Unity, drive it from Unity, remote data to the PC, and PC data to the remote;
    • 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/).
  • 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