Files
hexapod-robot/2026-current/remote/NEXTION.md
T
mangavalkandClaude Opus 5.5 0b836af8de 2026 remote: tabbed Nextion UI, robot telemetry, servo centre calibration
Protocol v4: CmdPacket grows to 26 bytes (cal_cmd, cal_servo, cal_value);
new 30-byte Telemetry rides back on the nRF24 ack payload (robot state,
IMU, battery, 18 joint angles, packets/s, servo-cal echo). Each end drops
wrong-length packets, so version mismatches still fail closed.

Robot (owner-approved): SERVO_CAL state while disarmed, per-servo centre
trims (+-200 us) in EEPROM, telemetry, battery reading; the IMU estimate
now always runs (leveling still gated by ROBOT GYRO).

Remote: generated HMI (scripts/make_remote_hmi.py) with pages splash,
drive, status, servos, cal, setup, upload; page-aware NextionUI that only
writes the showing page and only what changed; servo calibration and
UPDATE DISPLAY on the touchscreen and serial console; battery module.
The display is on Serial2 (pins 7/8), found on the real remote; the old
sketch's Serial1 was never connected to it.

Sim: RF24 shim supports ack payloads, API version 8
(hxsim_get_ack_payload); sim_smoke checks telemetry and every CAL command.
Unity CmdPacket mirror updated.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-17 14:42:37 +01:00

5.6 KiB
Raw Blame History

Nextion HMI

remote.HMI in this folder is the touchscreen project (NX4832T035, 480×320). It's generated by ../scripts/make_remote_hmi.py: change the layout there and re-run it, rather than editing the .HMI in Nextion Editor (an Editor edit is lost on the next run). Then open remote.HMI in Nextion Editor, compile, and upload the .tft: SETUP › UPDATE DISPLAY (tap twice) or serial key U puts the remote in USB passthrough for the upload.

python scripts\make_remote_hmi.py          (from 2026-current)

It needs the tools/nextion-hmi-tools submodule, Pillow, DejaVu Sans Mono (found in matplotlib, or --font-dir), and the old remote HMI (../../2019-teensy-nrf24/remote-nextion/remote.HMI, read only) for the splash picture. To look at a page without the Editor, use the nxhmi MCP server's render_page.

Pages

id Page Contents
0 splash spider picture, 1.5 s, then drive
1 drive ARM, SIT/STAND, gait, mode, right-stick mode, both gyros, speed + height sliders, messages
2 status remote and robot IMU roll/pitch, the 6 stick axes, both batteries, radio
3 servos all 18 joint angles (robot telemetry), laid out as a top view of the robot
4 cal servo centre calibration: START/STOP, leg and joint, trim ±1/±10 µs, ZERO, REVERT, SAVE
5 setup stick calibration, LEVEL REMOTE, UPDATE DISPLAY, backlight, versions
6 upload shown during display update mode

Pages 1–5 share a frame: a top bar (tLink link quality, tState robot state + battery, red bKill DISARM) and tab buttons bTab0–bTab4 that switch pages locally (page drive, ...). The page order is the page id, and must match UiPage in UiTypes.h.

How the firmware talks to it

  • Display → remote: every touch sends a custom frame with printh: '#' (0x23), length, command byte, optional value byte. "Send Component ID" is off everywhere.
  • Page tracking: each page's Preinitialize event sends 'P' + its page id, so the remote always knows which page is showing. After a remote restart it asks with sendme.
  • Remote → display: the remote writes only the showing page, by local component name (no vscope = global, no display RAM spent), and only what changed (NextionUI hashes every instruction). Everything is re-sent every 2 s and after the display restarts (0x88), so a dropped byte heals itself. Render rate is 20 Hz (SERVOS 10 Hz), and a render is skipped rather than blocking when the TX buffer is full.
  • The remote is authoritative: plain buttons only, nothing toggles locally. Exceptions that are purely local: the tabs, and the backlight slider (dim / dims).
  • Program.s sets bauds=115200 (= NEXTION_BAUD in Config.h), stored in the display.

Commands (display → remote)

Component Event code Command
every page printh 23 02 50 <id> (Preinitialize) P page shown
bKill printh 23 01 4B K disarm, always accepted
bArm printh 23 01 41 A toggle arm (needs sticks centered)
bStand printh 23 01 53 S toggle sit/stand
bGait printh 23 01 47 G tripod ↔ wave
bMode printh 23 01 4D M direct ↔ heading-hold
bRs printh 23 01 58 X right stick rotate ↔ translate
bRGyro printh 23 01 52 R remote-gyro tilt on/off
bBGyro printh 23 01 42 B robot self-stabilize on/off
hSpeed printh 23 02 56 + prints hSpeed.val,1 (move + release) V + speed 0..255
hHeight printh 23 02 48 + prints hHeight.val,1 (move + release) H + height 0..200, 100 = default
bCal printh 23 01 43 C start / save stick calibration
bCalX printh 23 01 51 Q cancel stick calibration
bZero printh 23 01 5A Z zero handset level
bUpd printh 23 01 55 U display update mode (second tap within 3 s)
bCalOn printh 23 01 4F O servo calibration start/stop
bL0–bL5 printh 23 02 4C 0n L + leg (0 FR, 1 MR, 2 RR, 3 RL, 4 ML, 5 FL)
bJ0–bJ2 printh 23 02 4A 0n J + joint (0 coxa, 1 femur, 2 tibia)
bM10 bM1 bP1 bP10 bZeroT printh 23 02 54 0n T + trim step: 0 −10, 1 −1, 2 +1, 3 +10, 4 zero (µs)
bSave printh 23 01 57 W save trims on the robot
bRevert printh 23 01 45 E reload trims from the robot's EEPROM

To add a control: pick an unused command byte, add it to NextionUI::decodeCustom() and UiCmd, handle it in RemoteState::handle(), add the component in make_remote_hmi.py, and a row here.

What the remote writes (remote → display)

Page Components
all but splash/upload tLink txt/pco, tState txt/pco
drive bArm bStand txt/bco, bGait bMode bRs txt, bRGyro bBGyro bco, hSpeed hHeight val, tSpeed tHeight tMsg txt
status tRRoll tRPitch tBRoll tBPitch txt, hRRoll hRPitch hBRoll hBPitch val (0..90 = ±45°), hLX hLY hLT hRX hRY hRT val (0..200 = ±1000), tBatt tRadio txt. The indicator sliders have touch switched off (tsw in Preinitialize)
servos tJ0–tJ17 txt (index = leg × 3 + joint), jJ0–jJ17 val (position in the servo's travel), tSrv txt/pco
cal bCalOn txt/bco, bL0–bL5 bJ0–bJ2 bco (selected = green), tTrim txt, bSave bco (orange = unsaved), tMsg txt
setup bCal txt/bco, bUpd txt/bco, tVer txt, tMsg txt

txt_maxl of each text is set in the generator to fit the longest string the firmware writes. Keep them in step when you change a format string.