The idea of the degraded channel is a good one. In the future I want to see the ability for hackers to try and disable or take over the robot via the communications channel. Need security on these designs...
- Issues of interference in the voice (various noises)
- Distance from the robot (that means a human needs
to be right next to the robot to be heard).
Remote commands are simpler, easier to have clarity,
simpler to recognize/follow without errors.
Think of it has the robot may be in a remote location, and perhaps a hazardous location. (For example space exploration). You would want simple commands to input remotely, and you would have intermitent communication issues and longer duration communication issues.
The robots still need to react to their surroundings.. (Balance, unforseen obstacles, falling, terrain, perhaps even damage like another robot running into them).
Yes, there are many legal hurdles to clear--some of them the same or similar to the driverless car--but I predict that by the time the algorithns are up to the the task, the law makers will have come to some sort of agreement with the service providers.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.