diff --git a/2026-current/README.md b/2026-current/README.md index a009b89..9d53105 100644 --- a/2026-current/README.md +++ b/2026-current/README.md @@ -110,7 +110,11 @@ Design notes, checks and open points: [hardware/openscad/PLANNING.md](hardware/o robot without a remote. - **[remote/README.md](remote/README.md)**: wiring, control scheme, stick calibration, and the remote's serial console. -- **[remote/NEXTION.md](remote/NEXTION.md)**: how to build the touchscreen - HMI. +- **[remote/NEXTION.md](remote/NEXTION.md)**: the touchscreen HMI (generated + by `scripts/make_remote_hmi.py`). +- **[sim/README.md](sim/README.md)**: the robot firmware in simulation, headless + and in Unity, with the keyboard or the real remote over the radio. +- **[dongle/README.md](dongle/README.md)**: the USB nRF24 stick, its firmware, + flashing and the bridge protocol. - **[shared/HexapodProtocol/HexapodProtocol.h](shared/HexapodProtocol/HexapodProtocol.h)**: the protocol. Change it only by reflashing both boards. diff --git a/2026-current/hardware/openscad/PLANNING.md b/2026-current/hardware/openscad/PLANNING.md index fe1f3ef..b14fa34 100644 --- a/2026-current/hardware/openscad/PLANNING.md +++ b/2026-current/hardware/openscad/PLANNING.md @@ -213,15 +213,17 @@ charge/on LEDs show through two slots in the floor. for the stall current. The battery must also fit the bay (see open question 3) and leave room for the servo plugs. -- Remote: connect the IMU to the normal pin headers instead of the Teensy - 4.0's underside pads; see `remote/README.md`, "Planned" (Wire on 18/19, - the two stick axes there move to A7/A8). +- Remote: the IMU is on the normal pin headers (done 2026-11-17: Wire on + 18/19, the two stick axes that were there moved to A7/A8; display on + Serial2, 7/8). Pinout in `remote/README.md`, "Wiring". - Remote: measure the 18650's voltage on the Teensy to show how much charge is left (owner, later). Divider ~100k/100k from the cell's + (holder or the UPS board's B+, not the 5 V output) to A6 (pin 20, free), 100 nF to GND; - full cell = ~2.1 V at the pin. Firmware: average, Li-ion curve to %, show - on the Nextion with a low-battery warning (optionally send it to the robot). + full cell = ~2.1 V at the pin. Firmware: reading, smoothing and the volts + on the STATUS page are done (`remote/Battery`, pin still 255 = not wired); + still to do: Li-ion curve to %, and a low-battery warning. The robot + already sends its own battery voltage back in the telemetry. - Servo wires barely fit on the real robot: the six servo headers hang above the battery bay, and the front pair sits right over the bay's end diff --git a/2026-current/remote/README.md b/2026-current/remote/README.md index 21aa32d..ec85efa 100644 --- a/2026-current/remote/README.md +++ b/2026-current/remote/README.md @@ -4,7 +4,9 @@ Handheld transmitter for the hexapod. It reads two 3-axis twist-grip joysticks and an MPU6050, takes operator commands from a Nextion touchscreen, and sends a `CmdPacket` (defined in `../shared/HexapodProtocol/HexapodProtocol.h`) to the robot over nRF24L01 -at 100 Hz. +at 100 Hz. The robot's `Telemetry` comes back in the radio's ack payloads. +Without the robot, the Unity simulation can answer instead, through the +USB nRF24 dongle (`../sim/README.md`). ## Planned