2b4750f8f4b6406e37f9ced766a99a0c250710bc
Dongle (app):
- bridge mode: stands in for the robot's radio (ch 96 / 250k / HXPD1,
auto-ack, dynamic payloads, ack payloads). Received packets go to the PC
as A5-framed 'R' frames; the PC's 'A' frames become the ack payload of
the next packet, like robot/Comms.cpp; dropped after ~0.5 s without a
refresh. 'S' status once a second.
- USART RX through circular DMA into a ring buffer, overrun stall
disabled, error flags cleared: a burst (e.g. SignalRGB probing the port)
used to deafen the app until a replug.
- RX test mode ('x') accepts protocol v4's dynamic-length packets.
- safeboot_flash.py --knock: keeps knocking across a replug to catch
safeboot's cold-boot window when the app doesn't answer.
Unity:
- SimRemote sources: Keyboard, or the real remote via the dongle
(DongleLink.cs: kernel32 serial, auto-finds the CH340, all port I/O on
one background thread). Packets go into the firmware byte for byte, the
robot's telemetry goes back on the ack, so the remote's display shows
the sim. Tested end to end with the real remote.
- Dropped the USB joystick and robot-serial-harness inputs and the old
Serial/Serial2/Serial3/HandleHoystick scripts (and their components in
Main.unity): no USB links to remote or robot any more.
- Test panel: dongle status; no sideways scroll bar.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Hexapod robot
Everything about my six-legged walking robot, from the first FPGA-driven version in 2009 to the current Teensy robot with its firmware-in-the-loop Unity simulation. Each generation has its own folder, named after the year it started, with its firmware, simulation, hardware, documents and photos together.
Working on the robot now? Go to 2026-current/. Everything else is history.
Timeline
| Folder | When | Hardware | What it did |
|---|---|---|---|
2009-fpga/ |
2009–2011 | FPGA, own frame design | the first version. The code is lost; photos, videos and the frame design (original-frame/, the base of every version up to 2023) are left |
2011-firefly-mega-ssc32/ |
2011–2012 | Arduino Mega 2560 + Lynxmotion SSC-32 | "FireFly": walking sequences with a Wii Nunchuk, later IR remote, ultrasonic radar head and GPS |
2012-simulation/ |
2012–2014 | PC | a Visual Studio leg-IK visualiser (2012) and a Processing 3D simulator (2014) |
2014-ik-core-task-queue/ |
≤ Feb 2014 | Arduino | a rewrite of the IK core around a task queue, without servo output yet |
2016-ssc32-processing-port/ |
~2016–2018 | Arduino + SSC-32 | the Processing simulator's classes ported to Arduino, driving the SSC-32 again |
2018-unity-sim/ |
2018–2023 | PC + SSC-32, later the Teensy | Unity computes the walking and drives the robot: first the SSC-32 over serial, from 2019 through the remote |
2019-teensy-nrf24/ |
2019–2022 | Teensy 3.6 on the robot (replaces the SSC-32), Teensy remote with Nextion screen, nRF24L01 | servo passthrough: Unity → remote over USB → radio → robot |
2026-current/ |
2026– | Teensy 3.6 robot, Teensy 4.0 remote, Fusion 360 designed parts, OpenSCAD rebuild and new remote | IK, gait, body pose and IMU stabilisation on the robot; the unchanged firmware also runs inside Unity |
Repository notes
- Photos, videos, PDFs, Office files, CAD and other binaries are stored with Git LFS (see
.gitattributes). A normal clone downloads them; setGIT_LFS_SKIP_SMUDGE=1to clone only the code. - Files are stored exactly as they were (no line-ending conversion), so old code is byte-for-byte the original.
- This repo was put together in October 2026 from the Gitea repos
Hexapod_2027,Hexapod,Hexapod-App,Hexapod-processing,Hexapod_Simulation_Unity,remoteandHexapod-Archief, the NAS folderProjecten\Electronics\Hexapod, the Arduino sketchbook and the Fusion 360 exports. The history of every repo exceptHexapod-Archiefis kept (its own history only held the same photos and videos again). Old code versions that only existed as rar files or backup folders are dated commits.
Languages
C++
52.9%
C#
16.7%
OpenSCAD
11.4%
C
10.2%
Python
5%
Other
3.8%