Overview: https://youtu.be/GEOMYDXv6pE
Control demo: https://youtu.be/_Cw5fGa8i3s
Videos of autonomous use-cases: https://docs.innate.bot/welcome/mars-example-use-cases
Quickstart: https://docs.innate.bot/welcome/mars-quick-start.
Our last thread: https://news.ycombinator.com/item?id=42451707
When we started we felt there is currently no good affordable general-purpose that anyone can build on. There’s no lack of demand: hugging face’s SO-100 and LeKiwi are pretty clear successes already; but the hardware is unreliable, the software experience is barebone and keeps changing, and you often need to buy hidden extras to make them work (starting with a computer with a good gpu). The Turtlebots were good, but are getting outdated.
The open-source hobbyist movement lacks really good platforms to build on, and we wanted something robust and accessible. MARS is our attempt at making a first intuitive AI robot for everyone.
What it is:
- It comes assembled and calibrated
- Has onboard compute with a jetson orin nano 8gb
- a 5DoF arm with a wrist camera
- Sensors: RGBD wide-angle cam, 2D LiDAR, speakers
- Control via a dedicated app and a leader arm that plugs in iPhone and Android
- 2 additional USB ports + GPIO pins for extra sensors or effectors.
- And our novel SDK called BASIC that allows to run it like an AI agent with VLAs.
It boots in a minute, can be controlled via phone, programmable in depth with a PC, and the onboard agent lets it see, talk, plan, and act in real-time.
Our SDK BASIC allows to create “behaviors” (our name for programs) ranging from a simple hello world to a very complex long-horizon task involving reasoning, planning, navigation and manipulation. You can create skills that behaviors can run autonomously by training the arm or writing code tools, like for an AI agent.
You can also call the ROS2 topics to control the robot at a low-level. And anything created on top of this SDK can be easily shared with anyone else by just sharing the files.
This is intended for hobbyist builders and education, and we would love to have your feedback!
p.s. If you want to try it, there’s a temporary code HACKERNEWS-INNATE-MARS that lowers the price to $1,799.
p.p.s The hardware and software will be open-sourced too, if some of you want to contribute or help us prepare it properly feel free to join our discord at https://discord.gg/YvqQbGKH
This isn't so clear though: https://docs.innate.bot/main/software/basic/connecting-to-ba...
> BASIC is accessible for free to all users of Innate robots for 300 cumulative hours - and probably more if you ask us.
Is BASIC used just to create the behaviours or to run them too? It sounds like this is an API you host that turns a behaviour like "pick up socks" into ROS2 motor commands for the robot. Are you open sourcing this too, so anyone can run the (presumably GPU heavy) backend?
Does the robot needs an internet connection to work?
Also, more importantly, what does it look like with googly eyes stuck on?
It is required to run them, not to create them. And it's not about running "pick_up_socks", this one can already run on your robot. BASIC is required to chain it with other tasks such as navigating to another part of your house and then running another skill to drop the sock somewhere for example
Thank you for the remark, we will make it clearer in the docs
As a consequence: The robot does not necessarily require Internet to run, but if you want it to chain tasks while talking and using memory, yes it does.
As for the googly eyes, give me a minute...
Can it do complex tasks like "pick up socks from room A, drive to room B, and put in basket"? Is the intention to allow hobbyists to do actual work with it or is this version purely novelty rather than a functional "personal robot"?
Additionally, what is the limitation on speed of movement? It seems very slow in movement, is that intentional for safety or is that purely because of running the AI model locally?
https://docs.innate.bot/main/welcome/mars-example-use-cases
I take from your comment that the full capabilities of the robot are not properly represented and I take a note to film longer ones. And it can definitely do what you just asked. And multiple times in a row. I will note that it depends on the training quality of course.
On speed of movement, I now realize we didn't mention it anywhere so I added it in the overview but it's pretty fast. 0.7m.s-1 for the base, and the arm can be tormented quite a bit. Just took this video for you:
https://youtu.be/H-gAaTKLm9c
Does the MARS hardware really remove the hidden extras (computer with a gpu) mentioned as the downside of HF SO-101 or LeKiwi? While a jetson is good for inference, I feel like to train VLAs you would need access to a powerful GPU regardless. For Lerobot based hardware training ACT was relatively low profile if you use low resolution for the camera feeds, but with increased resolution or with more than one camera I already saw needing more than 8GB of VRAM. If VLA is on the table, finetuning something like the open sourced version of pi0 should already necessitate access to more than one 4090 or above I think.
Also, do you have plans for community-level datasets? I think Lerobot sort of does this with their data recording pipeline and HF integration.
The training does require external GPUs (but we provide that infra for free, straight from the app!), but the onboard jetson can run models trained though, as you can see in the examples. Everything you see in the vids is running onboard when it comes to manipulation, because we use a special version of ACT made specifically by us for this robot, that also includes a reward model (like DYNA does).
We have developed this system to also be able to run the other components smoothly so it also does SLAM, and has room for more processing even when running our ACT.
Now indeed this cannot run Pi-0 but from our experience - and the whole community in general - VLAs are not particularly better than ACT in the low data regime, and need a lot more compute.
As for community-level datasets, yes this is the plan. Anything you train can already be shared with others - just share the files. We didn't develop a centralized place for sharing datasets and behaviors but it is on the plan.
You could simply host the raw grunt in a base station somewhere else in the premises, keeping the device lighter and lower power.
Also I am curious about a couple of the parts, if you don't mind sharing - are those wheels the direct drive wheels from waveshare? And what is the RGBD camera? (Fwiw, even if it's hefty the MARS price tag seems fair to me).
On the motors, these are dynamixels from robotis, and we provide all three of position, velocity, and effort on the low-level SDK (in ROS2 too)
and much higher interfaces for interaction and ai manipulation. Like directly recording episodes of training data so that the arm can use a VLA instead of simple IK.
You've got a $250 computer, some lidar+camera sensor for maybe $1-200, 6 servos, and cheap plastic. Plus you want to charge a $50/mo software subscription fee for some software product, whatever I guess that's beside the point.
No shade on the idea because low-cost robotics is an unsolved need for the future. But this current iteration is just not competing well with other alternatives. Perhaps this is more of a comment on what we can accomplish in the West vs what's possible in Asia.
Why would I not go for this guy for $1600, and attach an arm? https://www.unitree.com/go2
It's not an apples-to-apples product comparison, but you get the point. There's just so much more raw value offered per dollar elsewhere.
As for the unitree robot, this one is not unlocked for development, does not have onboard GPU, and does not have an arm. If you want it, check the price they give, it's very prohibitive.
You could attach a cheap arm to it but it would also not be stable enough for AI algorithms to run it. We're researchers ourselves, we would have made it cheaper if we could, but then you just can't do anything with it.
Our platform will deliver the experience of a real AI robot, anything cheaper than that is kind of a lie - or forces you to assemble and calibrate, which we do for you here. It is just the nature of trying to deliver a really complete product that works, and we want to stand for that.
EDIT: You can take a look at our autonomous demos there, you need something reliable for these: https://docs.innate.bot/welcome/mars-example-use-cases
Sure, the package is really interesting and definitely got me interested. But not one of the demos seems like a good use of the hardware. If you want to position yourselves mainly as an educational tool I don't think that is a problem. But if you want to target the 'maker' community I think you should put some thought into that.
For example, you could change the 'security guard' demo into a 'housekeeper' demo. You make it roam your house during the day and keep an up-to-date list of things you need to buy. I think this should work reasonably well for laundry and cleaning products. And after you have some historical data you could even do some forecasts about when you need to buy things again.
Another example would be to have it integrated with weather data and when it starts to rain it goes around the house to check if all windows are properly closed. On this same note it could keep track of the window state during the day and send you a reminder to open/close some windows if the temperature/humidity is above/below some threshold.
I think that by having some more 'useful' examples you should be able to get more attention from the 'maker' community. My guess is that a lot of folks that are heavily into home automation would love to have a device like that help with random things around the house.
Best of luck with your product, and I hope you succeed because this idea looks really exciting.
As someone who's dabbled in this before, I guess I'd rather just sit down and plan a BOM and do it myself if that's your markup anyways. Not that it's totally unreasonable for people who just want something super simple out of the box that works.
My general commentary is just that it's sad how much basic servos and what not cost in North America. We've completely ceded this industry to Asia.
I would say the problem is that most manufacturers, including chinese, sell you platforms that are not reliable enough for AI manipulation, and there's a race to the bottom for it, to which we try not to participate to
Pretty lofty claims though, really think you're so above everyone on quality at this price point? I know what dynamixels are capable of, and I see the jitter in the demo videos.
Why aren't the manipulator specs easily accessible on the website? Have you run a real repeatability test? Payload even?
It's a neat high-fidelity garage build platform, but I don't see any reason to assume this price premium is due to hardware quality.
Quasi-Lego-style robo dog for RPi is $100-150 on AMZN
I especially like that you’re using ACT and BC to bootstrap be authoring process. Hopefully behaviors are modular and transportable - which I assume they will be given then arch.
That is the correct approach in my opinion.
Happy to have you onboard!