Comment by XenophileJKO
15 days ago
I think for 95%+ of applications.. you just need a link to a data center anywhere.
My assumption is the hardware will have one/several smaller models running on it for locomotion, balance, etc.
Then the hardware "phones home" for decision making and planning.
Essentially the planning doesn't need to be close to the device as long as the local models can handle some part of the plan execution and make sure the robot doesn't fall over. The latency shouldn't be an issue. In fact more powerful centralized compute quickly creates an advantage over slower local compute in terms of end to end planning.
I can see some liability issues with that approach.
Liability issues will exist regardless of whether compute is on-device or central.
However, if the robot is in a contained environment like a home, there is less third party liability than for something like vehicles. Not none, of course, but less. And when you can get your arms around third party liability, first party liability can be better controlled by contractual agreements.
In general I expect on-device motor execution will allow it to safely come to a stop or enter a safe position if it loses the link to the execution planning cloud model.
[flagged]