2026 docs: review of every README against today's state

- 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>
This commit is contained in:
mangavalkandClaude Opus 5.5 committed 2026-11-17 22:56:14 +01:00
1 parent a59faf3b03
commit 179afdb705
9 files changed
+92 -33

No files matched your search

+27 -10
View File
@@ -30,15 +30,31 @@ Found by probing the board over SWD and confirmed at runtime by our firmware:
| SPI1 SCK / MISO / MOSI | PA5 / PA6 / PA7 → Si24R1 |
| nRF CSN / CE / IRQ | PA3 / PA4 / PA2 |
| status LED (active-high) | **PA0** — confirmed by eye |
| AT2401C TX/RX enable + unused | PA1, PB1, PF0, PF1 — **not yet distinguished** |
| AT2401C TX/RX enable + unused | PA1, PB1, PF0, PF1 — **not distinguishable** (see below) |
PA0 drives the LED (HIGH = on). The AT2401C control lines are among PA1, PB1,
PF0, PF1 (the TSSOP-20 has no other GPIO). Listening for ambient 2.4 GHz with
the radio's carrier-detect bit was too noisy to tell them apart, so they need a
real link test (dongle ↔ robot/remote, trying each pin while watching whether
packets get through). The radio still works without driving the amplifier, just
at reduced range. The app firmware can drive any pin (`0`-`4`), sweep them all
(`a`), and run a carrier-detect finder (`f`/`n`).
PA0 drives the LED (HIGH = on). The AT2401C control lines would be among PA1,
PB1, PF0, PF1 (the TSSOP-20 has no other GPIO). Listening for ambient 2.4 GHz
with the radio's carrier-detect bit was too noisy to tell them apart. The real
link test (2026-11-17: receiving the remote while switching all 16 on/off
combinations, at the desk and a few rooms away with the remote at minimum
power) got every packet in every combination, so either the link has plenty of
margin or the amplifier is switched in hardware. The firmware leaves them low;
the link works.
### App commands (USB serial, 115200, single keys, when not bridging)
| Key | Action |
|-----|--------|
| `v` | banner: version and a few radio registers |
| `r` | dump nRF registers |
| `x` | RX test on the hexapod's air settings; prints packets/s once a second |
| `0`-`4` | toggle PA0 (LED) / PA1 / PB1 / PF0 / PF1 |
| `a` | sweep every free pin high for 3 s each |
| `f` / `n` | carrier-detect finder on / next channel |
| `b` | reset into safeboot (what `safeboot_flash.py` uses) |
**SignalRGB** (if installed) opens every CH340 COM port it sees and holds it;
quit it while using the dongle.
### Programming header (5 holes next to the CH330N)
@@ -162,14 +178,15 @@ safeboot's 1.5 s cold-boot window.
## Air settings
Matches `shared/HexapodProtocol/HexapodProtocol.h`: 2.4 GHz channel 96
(2.496 GHz), 250 kbps, 5-byte address `HXPD1`, 16-bit CRC. The app sets these on
(2.496 GHz), 250 kbps, 5-byte address `HXPD1`, 16-bit CRC, auto-ack with
dynamic payload lengths and ack payloads (protocol v4). The app sets these on
the Si24R1 over SPI (same register layout as the nRF24L01+).
## Status / next
- [x] identify the hardware, map the radio + serial pins
- [x] permanent two-stage firmware, wire-free USB flashing
- [ ] identify the LED and AT2401C TX/RX-enable pins (app toggles the 5 free pins)
- [x] LED pin (PA0)
- [x] bridge mode: the dongle stands in for the robot's radio, Unity runs the
robot firmware (sim) behind it — see "Bridge mode" below
- [ ] the other direction: Unity as the remote, driving the real robot