- The robot/hardware should provide a TCP stack
- The firmware running on robot should be written in a way to work against viam sdk (which necessitates having a high-level OS like Linux running on it)
- Viam is like LabView/Simulink or ROS as-a-web-service
Congrats on launching, btw
- The firmware running on the robot should have internet access
If you use the cloud service (consumption based & optional) then you'll need internet access for configuration, logging, etc... But if you lose connectivity, the robot will operate just fine until the TLS cert expires (always at least 30 days in the future). Configs are cached locally so even a full robot reboot without internet access will work fine.
We think teleoperation is important as making perfect fully autonomous robots is incredibly hard, and by having humans in the loop, we can achieve much more tangible progress on real world problems.
Can I run the server on my own cloud?
All open source code is here: https://github.com/viamrobotics
The pinned `rdk` repo is the primary codebase.