When I spoke at Oredev this year I nearly stumbled across these fucking things.
Some kind of RC-car looking robot vision thing. With Raspberry Pis on them. In the booth next to where I found it Neo4j was doing .. something .. with a PuppyPi robot dog thing. So I thought it was theirs. Or some other exhibitor. But no. Asking the organizers it turns out these were just fun pieces of kit they had around from a past event. No-one quite knew how they worked on the current staff and there hadn’t been enough time or interest to bring them online. They’d been essentially set out as decor. Interesting-looking pieces for attendees to mull over.
When I expressed that I do work with embedded stuff day-to-day and could probably revive them I was offered to bring them home since they were currently e-waste. They had some more stuff in a box. My haul. 5 fairly complete Donkey Car open-source robotics platforms. And some spare stuff. Some LiPo batteries that died fairly quickly and some nimh batteries that seem okay if a bit weak currently.
I let some volunteers strip 4 of the 5 Pi 3s. I have enough leftover Pi devices from Goatmire. The coolest part to me is the RC car foundation and the convenient setup for running it with a Pi. The Pi-to-motor controller is a PCA9685. Then the ESC is just whatever this RC car shipped with.
The open source 3D printable platform sat on top of the RC foundation with screws and a lot of zip ties. Some ancient RPi camera modules completed the setup. A glorious if slightly past its prime robot.
Of course. Being who I am as a person I was never going to run the Python project. This was always a Nerves project and due to recent development in the ecosystem it was guaranteed to be a BEAM Bots project. Turns out there was already a servo library for the PCA9685. I run Elixir on my devices damnit.
We’ve already proven that the BEAM is good enough to balance a robot on two wheels. This didn’t even need help standing up. Seemed easy enough. And frankly it was. Without an agent it would have taken me a decent chunk of time to look up details, enter them, get familiar with all the parts of BEAM Bots that I hadn’t touched. Now I skipped that which I have mixed feelings about.
BEAM Bots is a high-level declarative robot abstractions. So reading the results of agentic work is pretty easy. I have not looked very closely at this source (which will be linked below). My interest was in getting it working and figuring out something to do with it more than caring about the details of how it worked.
While I was goofing off failing to understand that I had plugged in a bad battery on the late evening after my return from Oredev, I also had another agent check the camera, make it work over a live stream via Membrane and get it into the BEAM Bots Dashboard LiveView thing. That’s a phenomenal tool by the way. It is really nice to build in an ecosystem that does soft real-time UI so well with minimal effort.
Once I plugged in a working battery everything just worked. Throttle, steering and the camera worked. And then I requested a CLI control. That worked through the BB CLI tools that I’m not fully in tune with yet. Then I had it add it to the live dashboard thing instead.
It all just works. This means I could apply anything from my work on computer vision with Elixir that I spoke about at ElixirConf EU. I don’t know exactly what driving based on object detection would look like. But it feels related to another thing I want to do involving a robot arm and a Fairphone 3. Anyway. This is what the robotics framework is for.
I haven’t had time to play with the car much beyond getting it going. I’ve ordered some fresh LiPo batteries and a charger. I’ve sworn at the proliferation of connectors in the RC community which is not my world. And then I decided I wanted a way to get the thing switched between my home and office wifi without connecting cables.
So I added blue_heron which supports RPi3 in a very straightforward manner. And I told my agent to add tools for setting the wifi. I think it did Improv. I haven’t used that part yet because I realized I could ask for a joystick. And..
It is not the ideal control for this and I did get some 2.4GHz receivers and controllers in the box that I can probably wire up. But my end goal is not RC cars. Though I bet my kids would enjoy that.
While I was still driving it in a web browser from my laptop I did get the joy of a live camera feed to drive it in first person mode (not the drone headset kind, the video game kind). Unfortunately this specific car, which is the only one I’ve brought to life so far, has lost its camera. I think it died when I hit something. When I let it go full throttle it is kind of aggressive and it can hit things quite hard.
So what is my end goal? Tinkering really. I’d love to do some kind of coordinated driving over Erlang distribution. They really don’t have enough sensors to do it well. But it might be amusing enough to do it very poorly? Or try to make them do it with computer vision only?
So I have four more I can bring up. My expectation is that they’ll come up perfectly great on the RPi 3A devices I have around and I think the screw holes will even still line up.
Thanks to Hanna and Maisa at Oredev for letting me take these home and bring them back. And thanks to the people who made the frameworks I used to do this.
The joy of putting the BEAM (Erlang VM) on something and then slapping down Elixir libraries until it does absolutely ridiculous stuff just never ends for me. Things just click together on top of a shared runtime abstraction. It all just fits.
And thanks to the original Donkey Car project. And to whoever assembled and used these units at an Oredev in the past. If you know more what they were used for, let me know.
And if you have something you’d like to see me attempt with them, I might just consider it.
You can reach me with email at lars@underjord.io and either the fediverse @lawik@hachyderm.io or Bluesky . You can also get influenced by me on LinkedIn but I don’t recommend that place.
Thanks for reading





