the path so farsection through the machine, illustrative
How real robots are built, and why the hard part starts after the first one works.
Pick a machine. See how it senses, thinks and acts, what changes when you build a fleet of it, and which parts of the software Device to Cloud Flywheel does for you. Step through it with the buttons below, or keep scrolling.
Early accessDevice to Cloud Flywheel: free to self-host for your whole organization, or hosted by us.Get early access →You may have seen machines crawling through vegetable fields, killing weeds with lasers instead of herbicide or hand crews.
A young weed can look almost the same as the crop, and the machine has to find it and hit a growing point a few millimetres across while it keeps moving.
For every small step the machine takes, it runs these 5 steps in a loop.
- Sense
- Light, See
- Think
- Decide, Aim
- Act
- Fire
Light
Inside the closed hood, LED bars light the bed the same way at noon and at dusk.
See
The downward camera beside one laser takes a frame of the bed.
Decide
The computer on the deck runs the weed model on the frame, marks the weed, and finds its growing point, the few millimetres where a shot kills the plant.
Aim
The computer predicts where the weed will be when it reaches the laser row and turns the steering mirror in one laser module to that spot.
Fire
With the hood interlock showing the hood closed, the laser fires and the mirror puts the beam on the growing point.
You build the hardware and its sense, think, act loop on makeshift software.
ssh weeder-01 'tail -f /var/log/detector.log' scp weeder-01:/data/run-0412/*.mp4 ./to-label/ rsync model-v7.onnx weeder-01:/opt/models/ # hope nothing is mid-row
This works for one machine. It does not work for a fleet.
Then you redo the software.
Going from one robot to two, let alone a thousand, means redoing much of the software: fleet management, firmware control, and a great deal of integration. It takes real money, forces hard choices about where to spend it, and raises the barrier to entry.
Log
The machine records video of the bed in short segments, whether or not anyone is watching.
Device to Cloud Flywheel can record the camera in short video segments, kept on the machine until they upload.
Return
When the link allows, the machine uploads its recorded segments.
Device to Cloud Flywheel uploads them when the link allows, and reports which programs are running.
Learn
The fleet's records, this weed among them, are the raw material for the next model.
Device to Cloud Flywheel moves the frames your team picks to your trainer, checked by checksum, when you start the job.
Ship
The new model goes out as a declaration of what each machine should run.
Device to Cloud Flywheel sends the new model to a first group, then you advance, pause or roll back.
What your team builds, and what Device to Cloud Flywheel does for you
Then the loop starts again at 01 light, with the new model.
- The weed model
- Laser, mirror and timing control
- The hood interlock and safety chain
- Connects each weeder with one command, so nobody has to SSH into machines in the field
- Records camera video in short segments and uploads it when the link allows
- Moves the frames your team picks to your trainer when you start the job
- Sends the new model to a first group of machines, with pause and rollback
Get early accessSee every part of the laser weeder, drawn step by step →