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:
1 parent
a59faf3b03
commit
179afdb705
9 files changed
+92
-33
No files matched your search
@@ -41,8 +41,9 @@ still a placeholder. Check all of it against the real robot:
|
||||
needed ±90° offsets there, which left the servos at the end of their
|
||||
travel.
|
||||
- `RADIO_CE_PIN` / `RADIO_CSN_PIN` / `RADIO_SCK_PIN`: 39 / 15 / 14, as in
|
||||
the old sketch. Address, channel, data rate, PA level and payload size
|
||||
are in `shared/HexapodProtocol` so they can't drift from the remote.
|
||||
the old sketch. Address, channel, data rate, PA level and the packet
|
||||
structs are in `shared/HexapodProtocol` so they can't drift from the
|
||||
remote.
|
||||
|
||||
## Bench-check checklist (do this before the first stand-up)
|
||||
|
||||
@@ -62,7 +63,11 @@ for your build:
|
||||
down).
|
||||
3. **RobotIMU register map** (`RobotIMU.cpp`) — written for an MPU6050-style
|
||||
chip (I2C addr `0x68`). If your gyro is a different part, its register
|
||||
addresses and scale factors will differ; swap them in.
|
||||
addresses and scale factors will differ; swap them in. Also check that
|
||||
it gives live readings at all (the robot's roll/pitch on the remote's
|
||||
STATUS page): the remote's MPU6050 answered and woke up but read all
|
||||
zeros until it got a full device reset (`PWR_MGMT_1 = 0x80`), which
|
||||
`RobotIMU::begin()` doesn't do.
|
||||
4. **Sit-pose assumption** — the built-in sit pose in `robot.ino` assumes all
|
||||
six feet stay grounded and simply lowers the body (a 0.4x height blend).
|
||||
If your chassis is meant to rest its belly on the ground instead, this
|
||||
@@ -83,7 +88,8 @@ for your build:
|
||||
|
||||
This exact code also compiles for the PC and runs in the Unity model. See
|
||||
`../sim/README.md`. `sim/build/sim_smoke.exe` is a quick headless check
|
||||
after every change.
|
||||
after every change. In Unity the simulated robot can also be driven by the
|
||||
real remote over the radio, through the USB nRF24 dongle.
|
||||
|
||||
## Testing without a remote yet
|
||||
|
||||
@@ -163,6 +169,7 @@ robot/
|
||||
├── StateMachine.h/.cpp - DISARMED/SIT/STAND/WALKING with smoothed sit-stand blend
|
||||
├── InputMapper.h/.cpp - CmdPacket -> twist/pose/mode decoding
|
||||
├── Limits.h/.cpp - workspace clamp, joint rate limit, stance polygon check
|
||||
├── Comms.h/.cpp - nRF24L01 receive (packet definition is in shared/HexapodProtocol)
|
||||
└── ServoDriver.h/.cpp - servo attach/relax/write
|
||||
├── Comms.h/.cpp - nRF24L01 receive + telemetry as ack payload (packets in shared/HexapodProtocol)
|
||||
├── ServoDriver.h/.cpp - servo PWM write/relax, per-servo centre trims (EEPROM), SERVO_CAL
|
||||
└── Battery.h/.cpp - battery voltage through a divider (not wired yet)
|
||||
```
|
||||
Reference in new issue
Block a user