Loading video...

Video Failed to Load

Go Home

MOSS the 3D printed open source litter picking robot on the beach for the first time. Tracks are well sized for sand: dry sand low dunes, damp sand and the waterline, no problem. The big dry dunes near the entrance are another story, the ground clearance is low and...

15,826 views • 14 days ago •via X (Twitter)

32 Comments

metr0x's profile picture
metr0x14 days ago

Build guide CAD & STL files Bill of materials GitHub repository Join the kit waitlist

Robert Scoble's profile picture
Robert Scoble14 days ago

You should visit @mehul and license his algorithms.

metr0x's profile picture
metr0x14 days ago

@mehul Matic (@maticrobots) is such a great bot! As an independent open source builder I don't think it's possible for me to licence something like this tho

Robert Scoble's profile picture
Robert Scoble14 days ago

@mehul @maticrobots You should meet anyway. And you never know until you ask.

metr0x's profile picture
metr0x14 days ago

@mehul @maticrobots Very true

Joseph Urban's profile picture
Joseph Urban14 days ago

I can imagine a ton of customers that want their grounds continually cleaned up. A night vision capability would timeshift the task to low traffic times.

metr0x's profile picture
metr0x14 days ago

My robot vac is good at cleaning with the light off, for litter pick and place I'd add a headlight tho. Interesting to explore this when daylight is nailed.

Joseph Urban's profile picture
Joseph Urban14 days ago

I just took a walk through San Francisco. Leaves falling on the sidewalks. Imagine if the robot were to pick them up, one by one, stack them like cards, and clear the block by morning?

Ethan's profile picture
Ethan14 days ago

Beach cleanup! Full size industrial robot arms mounted on autonomous ATVs with a dump trailer in tow is what I ultimately see here. You should see if you can get a sponsorship from one of the big guys and build @sendcutsend @OSHBuilt

Fuchiio's profile picture
Fuchiio14 days ago

We're gonna need a bigger version!

metr0x's profile picture
metr0x14 days ago

Agreed, but you know how scaling a robot also scale it's cost: Back-of-the-envelope calculation 2 x 2 x 2 = 8 4 x 4 x 4 = 64 8 x 8 x 8 = 512 If a 20 cm robot cost $80 A 40 cm one cost $640 A 80 cm one cost $5120 Ofc it's not linear like this as some parts remain the same price. But it's the idea.

Frémont's profile picture
Frémont14 days ago

This is so cool. I want to see it pick up some gahbahge!

metr0x's profile picture
metr0x14 days ago

Me too 😆

Frémont's profile picture
Frémont14 days ago

Following to see!

⚡️ john's profile picture
⚡️ john14 days ago

WOAH i love this guy! would love to build and send to some NYC beaches

Jeff-Edge's profile picture
Jeff-Edge14 days ago

Sand is a serious terrain challenge! Well done. Did you have to take it apart to clean it? Next, the chasm between remote control and autonomous..! You might encounter me down in the gorge.

metr0x's profile picture
metr0x14 days ago

Awesome this is the idea of opening it, there’s only so much I can do. Nope just blasted some compressed air.

Jeff-Edge's profile picture
Jeff-Edge14 days ago

Compressed air cleaned = well designed. Bet mine would be crunchy after the beach. My next move would be to choose a specific use case and setup a training loop. First figure out how it decides where to go next. Need to trust it won't go where it shouldn't. Then can set it on autopilot and dive into trash identification: probably fine tune a SAM. Then collect teleop data on how to pick up different types of trash, fine tune whatever the latest/greatest action/world model is. Get to a supervisor level with the right buttons to catch edge cases and make corrections that can be fed back into training. Then see how many you can supervise at once, how hands off you can be. Finally leave that system on auto and jump to the next use case. I looked at the unknowns on that timeline and decided to do a fundraising project: augmented reality multiplayer games played on your phone's web browser.

metr0x's profile picture
metr0x14 days ago

That's a big road map. I see you have your own rover, I thought you was building MOSS, awesome let's share our notes, I am just getting started, I am trying to avoid overthinking it, the part that will need the most training is the detector I think, then aim the gripper at the trash and the pick and place should be a kind of scripted reflex at some point. I don't like much how stuff is complexified with AI lately. I don't think a litter picking robot need this. If the grasp fail try again, it's cheaper than LLM orchestration of VLA via API kind of stuff.

Jeff-Edge's profile picture
Jeff-Edge14 days ago

Yeah, I landed on that same differential drive tank-tread design in the spring. The difference between what I made playing with blender and what you made is humbling! Your components all fit and stuff.. Overthinking it comes with trying to get automation to work. "If the grasp fails try again" is an ACT policy. I had about 70% success picking up a specific object in a specific environment with just 30 training examples. Can run the training on an old gaming PC and run the policy itself on a Raspberry Pi. No APIs. Your sensor stack rocks. DimOS is the future. Running DORA on the bot's Pi-5 instead of ROS makes life better. Can fine tune a vision model that should run on the realsense (runs on my Oak-D Lite with depth). That's a free-software-on-an old-gaming-computer job too. Lots of labeling. So it's: - trash search - identify trash - deterministic move in reach - fire the ACT policy depending on the trash - deterministic drop in bucket - rerun loop. I didn't know anything about this a year ago. You got this.

metr0x's profile picture
metr0x14 days ago

The button supervision make me think of DAgger, I've got 90% on ACT a few month ago but from my perspective there is too much variability in litter and conditions for ACT / VLAs, so I start with a scripted grasp and the wrist camera as detector. Do you know a good labeled dataset for litter ? If I don't find one I may spend a couple day shooting litter form different angles and have a model like GroundAnything, from GroundingPI to label the data.

Jeff-Edge's profile picture
Jeff-Edge14 days ago

Right, your on it! Excited to see if a scripted approach works, cuz yeah, variabilities.

metr0x's profile picture
metr0x14 days ago

Mee too lamo, I'll report on X for sure, mabe I am wrong but let's try the less expensive first.

Amar's profile picture
Amar14 days ago

Would love to manage a fleet of these! We need a Trash-Collected-Per-Moss leader board.

Broky Lu Robot Mechanical's profile picture
Broky Lu Robot Mechanical13 days ago

Equal motor rotation doesn't guarantee equal travel over sand. Comparing track deflection under the same applied force could give you a repeatable tensioning baseline before adjusting the steering controller.

metr0x's profile picture
metr0x13 days ago

This is a very complicated way of saying I need to adjust tracks tension.

jim's profile picture
jim14 days ago

Littering the landscape with litter picking robots. 100 years from now even the bugs will be robotic.

Simone's profile picture
Simone14 days ago

how much sand did you have to clear out afterwards? a quick post-beach teardown would be fun to see.

metr0x's profile picture
metr0x14 days ago

Nothing inside the hull, I just use the air compressor on and inside the tracks.

Tejas's profile picture
Tejas14 days ago

How do you deal with waterproofing/Splash proofing? Or does your design not accommodate for that

metr0x's profile picture
metr0x14 days ago

Yes I have tried to design it splash proof, lips at the hull / cover interface, non woven membrane for the speaker, 45° vents for the fans, I've printed a set of TPU gaskets but did not installed it yet. I love all these questions about collecting litter at night, under the rain, but thb from my perspective, I'll do it in good conditions first, there is still a lot a work on the autonomous side. It's the current priority. For now it should be good enough to handle splashes, not rain yet, arm servos would not like this too.

Tejas's profile picture
Tejas14 days ago

Agreed with you. My robot is using a similar stack to yours for a different function. I want to make it workcij ideal conditions first and work on autonomy then the weather proofing can happen around that

Related Videos

Someone ran Claude Code on a beach where any device overheats and that spot suddenly turned out to be the best home for the most powerful AI in the world. This is the reMarkable Paper Pro. A paper tablet for notes with no browser and no social media and not a single app. He sat down right on the sand in the open sun and brought up Claude Code on Opus 4.6 over the Claude API on the paper screen and opened his project ~/repos/webs while the waves broke a few steps away. For years every device had the same trouble outside. In direct sun the screen glares and washes out and heats up and instead of your work you see your own reflection. But e-ink does not blast its own light into your face. It reflects the sunlight like the page of a book. And here is what came out of it. The very thing that kills any normal screen outside turned into fuel for this one. The brighter the sun the sharper the picture because it has nothing to glare with and nothing to wash out. And then comes the thing no laptop on a beach will give you. Your eyes do not get tired. You can watch Opus think on max effort for an hour and it reads like a book in the sun and not a backlight you squint into. The picture only comes alive. In bright light it does not fade but turns sharper and higher in contrast than it ever was in a room. The charge lasts for days. E-ink barely touches the battery so there is no outlet anywhere on the sand and the tablet does not care. It weighs as much as a notebook. The whole setup folds into a beach bag like a pad with a pen on top. Everything on the screen is for real. Claude Code v2.1.110 and Opus 4.6 on the Claude API and the project ~/repos/webs open right on the e-ink in the middle of the sand. In my opinion this is the most unexpected home for an AI this year. Not an office with the blinds drawn and not a monitor cranked to full brightness but a quiet sheet of paper on the sand that open sun only makes better and on it the most powerful Claude writes code right on the page like a pen.

Blaze

89,713 views • 4 months ago

"Men do not stay for platitudes. Platitudes do not carry a soul through the winter. When the child is in the ground, when the marriage is in ruins, when the diagnosis comes back and the floor drops out of the world, no one was ever held up by 'be kind and stay positive.' They are held, if they are held at all, by something with iron in it. By a witness that the heavens are real and open, that God still speaks, that the dead are not lost, that there is power on the earth greater than the darkness. The early Saints had that, and they knew they had it, because they had felt it in their own bodies. They were healed under hands. They spoke in tongues. They saw visions and buried their children in the certainty of resurrection and crossed a continent on the strength of a fire they could not have faked. That is what converts a man and that is what keeps him, not a well managed self-help program, but the living evidence that what we preach is true. So the cure is not complicated, and it is not new. It is to be again the Church of our fathers. Stop apologizing. Stop trimming the glorious truth into something the world will pat on the head. Speak with authority and with the hammer, the way Joseph spoke, the way Brigham spoke, the way men speak when they actually believe the heavens have opened over them. Reach again for the gifts of the Spirit, and stop pretending they were a founding era curiosity, because a testimony built on argument crumbles in the first storm and a testimony built on the manifest power of God does not. And above all, live as though the heavens are open, because they are, and they have only ever felt closed to a people who stopped expecting them to answer. The Saints are not leaving because the gospel is too much. They are leaving because we have made it too little. Make it glorious and demanding again, and watch who comes back through the door. The hungry have not gone anywhere. We simply stopped setting the table."

Kirk Rollins

63,131 views • 5 months ago

People who watch this always ask the same thing. If you got buried up to your neck in wet sand 10 feet from the ocean, could you dig yourself out? The answer is even more horrifying than you may think. MythBusters actually tested it. In dry, loose sand way up the beach, one of them eventually dug himself out, but it took about 86 minutes of nonstop, exhausting work, and the sand kept falling back into every gap. In wet sand with water added to act like waves and a rising tide, the other guy could barely move his fingers. The water kept pushing sand back into every space he made, and they had to stop the test. Near the water, getting yourself out just didn't work at all. Real beach cases say the same thing. People who end up trapped to the neck when a hole caves in almost never get out on their own. One Florida case took about 60 rescuers and two hours. A teenager in Lincolnshire was stuck up to his neck for about an hour while people dug him out, and his parents had to keep his mouth and nose clear the whole time. A teen in San Diego couldn't be pulled out at all, so lifeguards had to dig. The weight of the sand on your chest alone can squeeze your breathing enough to kill you before the water even shows up, and people have died in holes only a few feet deep. The only way a really strong person has a real shot is in dry sand way above the tide line, and even then it's slow and not a sure thing. If you're stuck neck-deep in sand by the water, you need other people with shovels, and even then rescue isn't guaranteed in time.

Matt Wallace

226,780 views • 1 month ago

Okay, the Huawei Mate 90 with camera module actually looks pretty awesome. This is the first phone camera accessory in a long time that actually brings something new to the table. Most of the add-on lenses from other manufacturers sit over the phone’s existing camera and magnify whatever that little sensor can already see. Useful, but you are still stuck with the phone’s telephoto. This one does not work that way. The module has its own 1-inch sensor built into it, larger than either of the big cameras already in the phone, and the phone’s lenses are not in the path at all. When it locks on, the phone is the mount, the battery, the screen, and the computer. You control the zoom, the focus, and the aperture from the phone, or from a ring on the lens itself. It does not even carry its own battery. The phone feeds power straight through the contacts, including the motors that drive the zoom. It is a REAL optical zoom, 24 mm to 240 mm on a 35 mm scale, continuous, on that same 1-inch sensor the whole way. Not a jump from a wide camera to a tiny periscope. Ten times, in one lens, with the aperture running from f/2.0 at the wide end to f/4.5 at the long end. For a portrait that is the difference between a normal lens and a short telephoto you would actually pack, and then on out to a reach you normally only get by cropping hard or carrying a separate body. Sony tried something like this years ago with the lens cameras that clamped onto a phone and communicated over Wi-Fi. Those had the right instinct and a miserable experience with terrible latency. This is wired in. The phone drives it. I have been looking for a compact system to carry for interviews when I am traveling. Right now that usually means three Micro Four Thirds bodies for my three required shots (one on me, one on the guest, and a wide shot with both of us). I keep picturing a couple of these in a carry-on instead. Same idea, a lot less bulk, and the phone I am already holding becomes the recorder and the monitor. I'm starting to see a bunch of photos and videos coming out on these and it looks really impressive.

Daniel Dumbrill

26,494 views • 1 month ago

your agent has thirty tools. it calls two of them. the other twenty eight are not sitting idle somewhere. they are in the request, every request, and they are doing damage in two places at once. first the obvious one. tool schemas go into the prompt, and a schema is not a name. it is a description, a parameter list, types, required fields, an example. thirty of those is a few thousand tokens that ship with every single call, including the ones where the agent just says thanks and stops. you are paying rent on twenty eight tools that have never fired. second, and this is the one that costs more. when the request says cancel the order, the model picks by matching against everything available. four of your tools are plausible: cancel_order, refund_order, update_order, void_order. it is choosing among them based on the descriptions you wrote, one afternoon, months ago. every tool you add is another candidate in that shortlist. the twenty eight you never call are not neutral. they are noise in the one decision that determines whether the run works. > why it grows without anyone deciding to nobody adds thirty tools on purpose. you add one for a task, it works, it stays. six months later the registry is a catalogue and no one has ever removed anything, because removing a tool feels risky and adding one feels free. and there is no feedback telling you otherwise. the unused ones never error. they never appear in a failing trace. they are invisible in exactly the way that lets them accumulate. > what to actually do count calls per tool over the last thousand runs. this is one group-by and it usually shocks people. the ones at zero are pure cost. ship the tools the task needs, not the whole registry. a research phase does not need deploy. a writing phase does not need the database. swap the set between phases instead of loading everything up front. same agent, different tools, depending on where the run is. and when two tools could both plausibly answer the same request, that is not redundancy you can ignore. it is a coin flip you built into the system. the twenty eight tools are not unused. they are used every time, by the part of the run you cannot see.

Hanako

24,656 views • 3 months ago