MOSS: a small, mostly 3D-printed litter-picking rover. Cleaner streets, one maker at a time.
Python
Changelog: first drive at the gamepad (10 October), firmware v3, teleop through dimOS, drive-line verdict, CAD R19 / R12 in progress; Software and firmware pages follow
openclawd6cd0ebb8b7a
diff --git a/.gitignore b/.gitignoreindex 29d7dc7..db5cefd 100644--- a/.gitignore+++ b/.gitignore@@ -7,3 +7,4 @@ __pycache__/.pytest_cache/recordings/.venv/+firmware/**/build/diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 7b0bfd2..d6d7e8b 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -2,6 +2,13 @@Hardware revisions. Dates are when it was real, not when it was planned.+- **10 October 2026, first drive at the gamepad.** The V0.5 rover, arm mounted, driven on the floor from a gamepad through dimOS: forward, reverse, turns, pivots. What it took and what it showed:+ - Firmware `qtpy-mdd3a-v3` on the QT Py ESP32-S3 (`firmware/MOSS_QTPY_MDD3A/`): the 25 % commissioning limit is gone, full stick is 100 % PWM (at 25 % the loaded tracks did not move at all); left track direction fixed in the firmware, encoder counts follow; `ramp UP DOWN` sets the rise and fall slopes live; a build switch for the Cytron MDD10A (PWM + DIR) next to the MDD3A build; the board names its driver in the banner and the telemetry. Host test updated.+ - Teleop: the base runs as a dimOS blueprint (`moss-gamepad` in [vector-dimos](https://github.com/metrox-eth/vector-dimos)): deadman on the pad, twist to track percent, keepalive inside the firmware's 300 ms deadman, tank steering (past half turn stick the inner track reverses), one launcher with gates (pad, board, firmware, battery) and a telemetry line every two seconds while driving.+ - Seen under load: the board applies 100 %, the 3S battery drops from 11.6 V at rest to 10.8 V in a pivot. Verdict on the drive line: the MDD3A (3 A per channel) and the 56:1 motors leave no headroom for ramps. Next on the drive line: Cytron MDD10A (10 A per channel) and JGB37-520 motors at 110 rpm (higher ratio), both not installed yet; the firmware build for the MDD10A already exists.+ - Tracks: the double tensioner holds, the bearings keep mechanical friction low; the TPU tracks may need running in, or print settings that make them more supple.+ - In CAD, no part printed or fitted: hull R19 with an integrated mount for the MDD10A (rotated hole pattern 55.88 x 78.74 mm, four M3 x 6 into 2.7 mm pilot holes, no inserts), charging jack moved to clear the larger board, the motor-side drive-spacer passages opened to 9.5 mm; transmission R12-C1 (two drive-shaft spacers that were missing, 3.5 mm, PETG) and R12-C2 (matching screw-head recesses on the inner frames and inner tensioner plates, so all four tension screws become M4 x 35). CAD checks only; the production plates and the BOM are not reconciled to it, and nothing is frozen.+ - Still open on V0.6: fan spacing and clip retention next to the motor brackets, inserts for the LiDAR mount, upper cover and arm platform, the LiDAR collision, one consistent hole pattern per wheel type.- **V0.6** (October 2026): modular compute and perception plates (Jetson or Raspberry Pi; RealSense or Orbbec Gemini), XT30 power block, 12 V to 5 V converter for the Pi, hull R7, tracks 70 teeth at 10 mm pitch.- **V0.5** (1 October 2026): redrawn on the real robot; one-piece hull, two tensioners per track, mounts for every board, magnets for the bin. 107 printed parts.- **V0.4** (24 September 2026): revised hull, screw-terminal controller, one dual motor driver.diff --git a/Software.md b/Software.mdindex 1632181..b55e8a5 100644--- a/Software.md+++ b/Software.md@@ -2,28 +2,29 @@The stack is dimOS. The microcontroller drives the motors; dimOS, on the Jetson or the Pi, does teleop, recording, navigation and manipulation. The policies come later, from pooled data.-**The motor firmware drove the prototype. The computer side is tested against a fake serial port only.**+**The motor firmware drove the prototype, and since 10 October the rover is driven on the floor from a gamepad through dimOS (vector-dimos `moss-gamepad`, below).**## Motor firmware, ESP32-S3-[`firmware/`](firmware/). Newline-terminated commands over USB serial at 115200 baud:+[`firmware/`](firmware/). Current board: Adafruit QT Py ESP32-S3 on its screw-terminal carrier, firmware `firmware/MOSS_QTPY_MDD3A/` (native USB; one build for the Cytron MDD3A, one for the MDD10A). The DevKitC snapshot `firmware/MOSS_ESP32S3/` is the V0.3 bench firmware, kept as history. Newline-terminated commands over USB serial at 115200 baud:| Command | What it does ||---|---|| `status` | one telemetry line || `arm` | ready to drive, for 10 s if no drive comes |-| `drive L R` | track speeds, −25 to +25 percent; must be repeated, 300 ms without one stops and disarms |+| `drive L R` | track speeds, −100 to +100 percent; must be repeated, 300 ms without one stops and disarms |+| `ramp UP DOWN` | milliseconds per percent, rise and fall; default 30 / 15 || `test left 10` | one motor for one second, bench only || `stop` | stops and disarms || `zero` | resets the encoder counts (disarmed only) |-Telemetry every 200 ms as JSON: mode, raw encoder ticks, battery voltage. Disarmed at boot, nothing moves by itself. The 25 % limit is the commissioning limit; it stays until speed control exists. No speed loop, no odometry in metres yet.+Telemetry every 200 ms as JSON: firmware and driver names, mode, applied and target percent, raw encoder ticks, battery voltage. Disarmed at boot, nothing moves by itself. The 25 % commissioning limit was lifted after the first drive on the floor (10 October): full stick is 100 % PWM, the host caps lower when it wants to (`MOSS_MAX_PCT`). No speed loop, no odometry in metres yet.The board reads battery voltage through an INA219. It does not measure motor current: the shunt is not in the motor line.-## Teleop and navigation: dimOS, `moss_dimos/`+## Teleop and navigation: dimOS-MOSS runs [dimOS](https://github.com/dimensionalOS) by Dimensional, on the Jetson or on the Pi: a gamepad module publishing a Twist behind a deadman, differential-drive kinematics, then navigation and the pick. Speed control and odometry come next.+MOSS runs [dimOS](https://github.com/dimensionalOS) by Dimensional, on the Jetson or on the Pi. The base that drove on 10 October is the `moss-gamepad` blueprint of [vector-dimos](https://github.com/metrox-eth/vector-dimos): a gamepad module publishing a Twist behind a deadman, a tracked-base adapter that turns the twist into track percent and keeps the firmware's deadman fed, tank steering (past half turn stick the inner track reverses), a launcher with gates (pad present, board present, firmware disarmed, battery above its floor). `moss_dimos/` in this repository is the earlier skeleton of the same idea, cold-tested only. Navigation and the pick come next, then speed control and odometry.## Bench tool, `moss_pi/`diff --git a/firmware/README.md b/firmware/README.mdindex e224e33..d4e3d0d 100644--- a/firmware/README.md+++ b/firmware/README.md@@ -1,4 +1,10 @@-# MOSS ESP32-S3 commissioning firmware+# MOSS motor firmware++**Current: [`MOSS_QTPY_MDD3A/`](MOSS_QTPY_MDD3A/)**, QT Py ESP32-S3 on its screw-terminal carrier, native USB, limit 100 % since the first drive on the floor (10 October 2026), `ramp` command, one build per driver (Cytron MDD3A by default, `-DMOSS_DRIVER_MDD10A` for the MDD10A, see its `bench/README.md`). Host test: `tests/control_v04_test.cpp`.++The rest of this page is the V0.3 bench firmware on the DevKitC, kept as history.++## MOSS ESP32-S3 commissioning firmware (V0.3, history)Reference source snapshot for the firmware restored after the 20 September 2026 bench tests. MAX_PERCENT=25. The temporary 100% firmware is not the default.