Skip to content
Early access openRev 0.1Robots in the lab 0001Local --:--:--
//Learn

What do you want to build today?

Each machine here is taught part by part: what every part does, what every step asks of it, and why each one is hard. Then it follows the machine out to a fleet.

Pick the work above, or roll for a machine. Each one is drawn part by part, then followed out to its fleet.

Follow one piece of work.

Each page takes one piece of work through the parts of one machine, then out to its fleet: the data coming back, the next version trained or written, and that version going out again. The fleet steps name the Device to Cloud Flywheel solution that does the work, and the pages are grouped here by that solution.

The fleet drawings show 1,000 machines to show the problem at that size; Device to Cloud Flywheel has been run on fleets of single digits to low tens of devices. Each solution's name and “you have” text come from its solution page, with punctuation or wording adjusted in places.

Solution 01 of 09

Laptops, desktops, and Raspberry Pis

You have: A handful of ordinary computers you look after, a home server, a few Pis, the machines under someone's desk. Today you keep a VPN up so you can SSH in and fix things by hand.

Solution 02 of 09

A ROS 2 robot

You have: Robots already running ROS 2. You have a stack you are not going to replace, and you want fleet operations around it rather than instead of it.

Solution 03 of 09

A PX4 drone fleet

You have: Drones running PX4. Flights produce logs you want off the aircraft, and firmware and parameters you need to roll out without bricking a fleet.

Solution 04 of 09

Cameras and vision devices

You have: Cameras in the field, fixed, on a machine, or a browser on a laptop. You want to see them live and pull frames back for training.

  • Follow one weed
    Laser weederfollow one weed, shown aboveat 06 log
  • Follow one frame

    Smart camera

    It cannot send every frame, so it has to decide, on the wall, which few seconds are worth keeping, in light that changes all day and on a site its model has never seen.

    Follow one frame through the smart cameraat 04 stream, 05 log, 06 return

Solution 05 of 09

A robot arm running a learned policy

You have: An arm, a LeRobot SO-101 or similar, and a policy you retrain as you collect more demonstrations.

Solution 06 of 09

PLC and Modbus machines

You have: Industrial machines speaking Modbus behind a small computer. The meaning of a register is knowledge that currently lives in someone's head.

Solution 07 of 09

Heavy equipment, simulated then real

You have: Machines too expensive to experiment on. You want to train against a simulator and deploy the result to the real thing through the same path.

Solution 08 of 09

Photoreal simulation with Isaac

You have: An Isaac Sim scene and a need for training imagery that looks like what the machine will actually see.

Solution 09 of 09

Training a policy and shipping it to the fleet

You have: Field data coming back from machines, and a model you want to improve and redeploy without a bespoke pipeline each time. It runs across the other solutions rather than describing one kind of device.

  • Follow one weed
    Laser weederfollow one weed, shown aboveat 08 learn, 09 ship
  • Follow one shirt
    Laundry folding robotfollow one shirt, shown aboveat 05 log, 06 return, 07 learn
  • Follow one tote
    Warehouse AMRfollow one tote, shown aboveat 08 learn
  • Follow one frame
    Smart camerafollow one frame, shown aboveat 07 learn, 08 ship