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:
1 parent
1591105f26
commit
175a1a0da8
3 files changed
+41
-42
No files matched your search
@@ -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.
|
||||
Reference in new issue
Block a user