The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
This is not a good idea.
Navigation, path-planning and path-following controllers generally requires loop rates between 10 and 100Hz, and a corresponding processing (and network) latency of less than 10 to 100mS.
The average WiFi and 3G/4G/LTE cellular networks can barely meet these latency guarantees, and even when they do, there isn't a lot of latency budget left over to do computation. If the AWS or Heroku servers are more than a few hundred kilometers away, the round-trip time to the servers and back can start to add up, too!
You might be able to get acceptable performance if you work directly with a wireless carrier to get dedicated bandwidth and latency guarantees, or if you control your local wifi network and communicate with servers that are in the same building, but those options are out of reach for most users.
It is possible to offload some of your very heavy processing to cloud services, but keep in mind that the latency will be high. This could be good for things like recognizing objects, updating a very large map shared between many robots, or a variety of other things that aren't terribly sensitive to latency.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
