- README / CLAUDE.md layout: dongle/, hardware/, tools/ submodule,
make_remote_hmi.py; telemetry in the protocol; the PC can take the
robot's place on the radio. CLAUDE.md: NextionUI is on Serial2 (said
Serial1); remote-without-robot via the dongle + sim.
- remote/README: MPU6050 supply row; stick calibration button names of the
new SETUP page; upload/USB-port hints.
- remote/NEXTION.md: display on Serial2, how the Editor upload goes.
- robot/README: Battery in the file list, Comms/ServoDriver roles, packet
structs instead of payload size, check the IMU gives live data (the
remote's MPU6050 needed a full reset; RobotIMU::begin() only wakes it).
- sim/README: smoke test covers telemetry and servo calibration;
OpenScadModel.
- dongle/README: AT2401C test result, app command table, SignalRGB note,
air settings incl. ack payloads.
- PLANNING.md: the display direction is in the generated HMI.
- Unity README: what the project is.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- PLANNING.md: IMU on the pin headers is done; battery firmware is done
except the % curve and the low-battery warning.
- README "Where to go next": link sim/README and dongle/README.
- remote/README intro: telemetry comes back; the sim can answer via the dongle.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- TOP_GROW: top shell 10 mm taller (room behind the display); the bottom
shell is unchanged, dependent heights follow Z_SPLIT / Z_BOT.
- Nextion dimensions as measured by the owner: board 100.6 x 55, LCD
85.7 x 55 x 3.86 plus a 1.3 mm flex cable, 11.21 mm glass to back of J1.
LCD pocket allows the cable on either short side; bezel 1.0 mm (the
display sat on the Teensy).
- Display posts tapped M3 for M3 x 5 machine screws, 1.2 mm skin under the
top face (was M2.5 self-tapping). README screw list and PLANNING.md
updated; STLs regenerated.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- remote_v2.scad: main board is the measured 56 x 80 mm perfboard, held by
4 side clamps (M3 button head + washer into inserts), no holes in the board
- export_3mf.py writes remote_v2_top_inlays.3mf (top shell + honeycomb +
ON/OFF on filaments 1/2/3); remote_v2_top_multicolor.3mf stays the
owner's OrcaSlicer project
- STLs re-exported, README printing table and PLANNING notes updated
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- 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>
remote_v2.scad: a new remote for the same electronics, 216 x 116 x 32 mm,
ASA, two shells printed without supports and joined with M3 heat-set
inserts. Hangs level from a neck strap on a balance-point eyelet (top face
or front edge) with a fold-out body brace; kickstand for the table.
JH-D300X-R1 sticks clamp the plate; main perfboard (Teensy 4.0, nRF24,
IMU) clamped at its sides under the display; UPS board with its LEDs
through the floor. Red honeycomb and white ON/OFF inlays in the first
3 layers. Every part checked for collisions.
- stl/remote_v2/: print-ready STLs, plus a multi-part 3MF (export_3mf.py)
with the inlays on filaments 2 and 3
- ARCHIVE.md: the original remote with the owner's photos; README shows v2
and how to print it
- Notes for later: battery-voltage reading, IMU on Wire (18/19) with two
stick axes moved to A7/A8, a stable 6 V supply for the 18 servos
- remote.scad: its sticks are JH-D300X-R1 (the model uses the D400X drawing)
- *.3mf through Git LFS; repo README says Teensy 4.0 remote
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Board teensy41 -> teensy40. All pins exist on the 4.0; the MPU6050's
Wire2 (SDA2 25 / SCL2 24) is on the underside solder pads.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
hardware/openscad/ rebuilds the broken Fusion models as OpenSCAD:
body (top/bottom plate, standoffs, battery bay, switch), legs (coxa
bracket, femur link, tibia, horn adapters, TPU socks, servo cables),
the whole robot, and the remote (shell, lid, Nextion 3.5", JH-D400X-R4
sticks, 18650 UPS board, IMU, Teensy 4.0, USB-C breakout). Every part
was checked by slicing against the original STEP solids; the original's
bugs are fixed and listed in PLANNING.md.
The robot now uses a hexagon leg layout (corner legs 60 deg round from
the mid legs; the corner coxa brackets need turning on their splines).
Physical limits from a collision sweep of the model are in Config.h:
per-leg coxa limits and LEG_CLEARANCE_MM 56 (a leg is 55.2 mm wide at
the joints); the sim API exports them (version 7). sim_smoke passes.
Unity loads the model (export_unity.py -> Resources/OpenScadModel,
OpenScadModel.cs builds a new rig in place of the old scene's robot).
The PCB model's mounting holes now use the exact EasyEDA grid. README
shows renders of both.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>