2026 docs: catch the READMEs up with today's state

- README: the HMI is generated turned round (nothing to set in the Editor);
  PC radio link: bridge mode done, no USB links any more, what's left
  (Unity driving the real robot, three nodes at once).
- remote/README checklist: sticks and IMU checked, display uploaded, radio
  checked against the sim through the dongle; replace the IMU board.
- CLAUDE.md: display runs the new HMI; next steps.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
mangavalkandClaude Opus 5.5 committed 2026-11-17 22:52:44 +01:00
1 parent 1591105f26
commit 175a1a0da8
3 files changed
+41 -42

No files matched your search

+6 -6
View File
@@ -409,9 +409,8 @@ Remote (`remote/README.md` has detail):
- The Nextion must have `bauds=115200` in Program.s, and the HMI must match
`NEXTION.md`. The working HMI is `remote/remote.HMI`, generated by
`scripts/make_remote_hmi.py` (owner-approved design, 2026-11-17; the old 6-page one in
`../2019-teensy-nrf24/remote-nextion/` only lends its splash picture). The display still
runs the old HMI until the new `.tft` is uploaded: use serial key `U` for that first upload,
the old UPLOAD button isn't recognised any more. Edit and render it with the `nxhmi` MCP server
`../2019-teensy-nrf24/remote-nextion/` only lends its splash picture). It's on the real
display (turned 180°, see `remote/NEXTION.md`). Edit and render it with the `nxhmi` MCP server
(registered in the repo root `.mcp.json`; code is the git submodule `tools/nextion-hmi-tools`,
run `git submodule update --init` after cloning; CLI `python -m nxhmi` with `PYTHONPATH` =
`tools/nextion-hmi-tools/src`): `info`, `get_page`, `render_page`, `set_attributes`,
@@ -468,6 +467,7 @@ Remote (`remote/README.md` has detail):
rate limiting on any setpoint that can jump, and paired `.h/.cpp` per
concern.
- Planned or possible next steps: wire the battery dividers (firmware is
ready on both sides, pins still 255) and add a low-battery warning; try
ack-payload telemetry and servo calibration on the real radios (only
simulated so far).
ready on both sides, pins still 255) and add a low-battery warning;
flash the robot with protocol v4 and try telemetry and servo calibration
with it (the real remote ↔ dongle ↔ Unity sim path already works over the
air, 2026-11-17); Unity driving the real robot through the dongle.
+22 -25
View File
@@ -72,36 +72,33 @@ Hardware (besides the electronics of the old remote):
board clamps, no holes in the board), M3 x 40 + nut (kickstand pin)
- M2.5 x 14 x 8 (joysticks, into their own boxes), M3 x 5 machine screws x 4
(display, tap the posts M3), 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.
- The display is mounted turned round so its connector clears the Teensy's USB
plug. `remote.HMI` is generated for that (display direction 270 in the
Editor's terms, see [remote/NEXTION.md](remote/NEXTION.md)), nothing to set.
Design notes, checks and open points: [hardware/openscad/PLANNING.md](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](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](remote/README.md), "Planned".
- **PC radio link:** a USB nRF24L01 stick on the PC as the PC-side radio, on
the same air settings as the robot and the remote. It's reverse-engineered
and runs our own firmware (STM32F030 + Si24R1 + AT2401C, updated wire-free
over USB), see **[dongle/README.md](dongle/README.md)**. Done (2026-11-17):
its **bridge mode** lets the real remote drive the Unity simulation over the
air, with the sim's telemetry going back to the remote's display as the ack
payload ([sim/README.md](sim/README.md), "Using it in Unity"). There's no USB
link to the remote or the robot any more; everything goes over the radio.
Still to do:
- Unity driving the **real** robot (the dongle transmitting instead of
listening) and mirroring it;
- three nodes at once: today the dongle answers the remote *instead of* the
robot. Needs an address per node (or per pipe), a packet type byte, and a
rule for who has priority. 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.
- Remote battery level: see [remote/README.md](remote/README.md), "Planned".
- Robot power: a stable 6 V supply for the 18 servos, see
[hardware/openscad/PLANNING.md](hardware/openscad/PLANNING.md), "Notes for
future designs".
+13 -11
View File
@@ -158,18 +158,20 @@ and the servo-calibration state.
1. **Stick directions:** with `p`, confirm each logical axis reads
positive for right / forward / counterclockwise twist. Flip it in
`STICK_INVERT[]` if not.
`STICK_INVERT[]` if not. Done on the real remote (2026-11-17), then
the sweep calibration.
2. **IMU mounting:** with `p`, dip the right edge down to get +roll, and
tip the far edge down to get +pitch. If not, fix `IMU_AXIS_FROM_CHIP` /
`IMU_AXIS_SIGN`.
3. **Nextion baud:** the generated HMI sets `bauds=115200` in Program.s.
The display still runs the old HMI (probably 9600) until you upload
the new one; Nextion Editor finds the baud rate by itself. For that
first upload use serial key `U`: the old HMI's UPLOAD button isn't
recognised any more.
4. **Radio:** with the robot powered, `tLink` / `p` should show ~100%, and
`p` should print robot telemetry. If it reads NO LINK, check that both
boards were built from the same `HexapodProtocol.h`: each end drops
packets of the wrong size.
`IMU_AXIS_SIGN`. Done (defaults are right). The first GY-521 got its
supply reversed once and its regulator now runs hot: redo this check
on the replacement, and see whether it still needs the reset in
`RemoteIMU::begin()`.
3. **Nextion:** the generated HMI sets `bauds=115200` in Program.s and is
on the display (upload through SETUP › UPDATE DISPLAY or serial `U`).
4. **Radio:** with the robot (or the Unity sim behind the USB dongle)
running, `tLink` / `p` should show ~100%, and `p` should print robot
telemetry. If it reads NO LINK, check that both ends were built from
the same `HexapodProtocol.h`: each end drops packets of the wrong size.
Done against the Unity sim through the dongle; not yet with the robot.
5. **End to end with the robot on a stand:** use `d` to dump packets and
confirm each field changes the way the table above says.