Skip to content

armgit / moss

Public Imported from GitHub
0

MOSS: a small, mostly 3D-printed litter-picking rover. Cleaner streets, one maker at a time.

Python

README and Software: dimOS is the software layer; two cameras and a lidar, said plainly

metrox2db92e7b382e
diff --git a/README.md b/README.md
index 1663b7c..e48d6fa 100644
--- a/README.md
+++ b/README.md
@@ -32,9 +32,10 @@ The Jetson configuration is the one on the bench. Every line is in the [BOM](BOM
- Tracked base, two geared DC motors with encoders, printed TPU tracks, an ESP32-S3 driving the motors.
- A bin you empty by hand at the end of a run.
-- An SO-101 arm (open source) with a NormaCore parallel-jaw gripper, widened to a 90 mm grip, and a small camera in the hand.
-- A depth camera or a Mighty tracking camera at the nose, a 2D lidar for navigation.
-- Software: dimOS for teleop and navigation, LeRobot for data and policies. A Raspberry Pi path without dimOS for the first drives.
+- An SO-101 arm (open source) with a NormaCore parallel-jaw gripper, widened to a 90 mm grip.
+- Two cameras: a depth camera at the nose, a colour camera in the hand.
+- A 2D lidar for navigation.
+- Software: dimOS for teleop and navigation, LeRobot for data and policies.
The rule we build by: pick up more litter with less technology. Every part has to earn its place against a person with a bag.
diff --git a/Software.md b/Software.md
index 9ec522f..0347d4a 100644
--- a/Software.md
+++ b/Software.md
@@ -1,6 +1,6 @@
# Software
-Three layers. The microcontroller drives the motors. The computer on top sends it speeds and reads its telemetry. The policies come later, from pooled data.
+Three layers. The microcontroller drives the motors. dimOS, on the Jetson or the Pi, does teleop and navigation. The policies come later, from pooled data.
**The motor firmware drove the prototype. The computer side is tested against a fake serial port only.**
@@ -21,9 +21,13 @@ Telemetry every 200 ms as JSON: mode, raw encoder ticks, battery voltage. Disarm
The board reads battery voltage through an INA219. It does not measure motor current: the shunt is not in the motor line.
-## Driving from a Raspberry Pi, `moss_pi/`
+## Teleop and navigation: dimOS, `moss_dimos/`
-Keyboard or gamepad teleop, no dimOS, Python standard library plus pyserial (and pygame for a pad).
+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.
+
+## Bench tool, `moss_pi/`
+
+Talks to the firmware from any computer over USB, to arm, drive and log telemetry during commissioning. Python standard library plus pyserial, and pygame for a pad.
```
python3 -m venv .venv && . .venv/bin/activate
@@ -38,10 +42,6 @@ python -m moss_pi.telemetry_log --port /dev/ttyUSB0 --out telemetry.jsonl
Nothing moves until you arm with the deadman released. Hold the deadman to drive; release and it brakes, then disarms. The stick is open loop: full stick is 25 % duty. Put the rover on blocks for the first run.
-## Driving from a Jetson, `moss_dimos/`
-
-The dimOS side: a gamepad module publishing a Twist behind a deadman, differential-drive kinematics, the same pure teleop logic as the Pi path. The driver that speaks to the firmware from dimOS, speed control and odometry are not written yet. Navigation and the pick come from dimOS once the base is reliable.
-
## Data and policies
Demonstrations are recorded in the LeRobot format with the same camera names on every rover, so datasets pool without rework. The rules are in [docs/data.md](docs/data.md). The simulator (MuJoCo body, three recorded pickup missions) is in [moss-jev](https://github.com/metrox-eth/moss-jev).