While conventional approaches to robot programming and control make use of off-line
robot programming languages custom-delivered by the manufacturer, the very task of
learning such languages and implementing solutions itself consumes several precious
skilled man-hours. The problem deteriorates with any changes or upgradations made to the
robot. Newer robots of different configurations or from different manufacturers tend to
worsen the situation. There is still a class of robot-users who staunchly discard custom
software and dare to propound and make their own, for specific purposes. This exercise,
however, is an arduous and tricky one especially when one has no idea as to how the robot
is interfaced to the system (a matter which most manufacturers opt to make proprietary). By trying to debug the black box
that forms the robot interface, a user may risk damage to both the robot and the system
that controls it.The current day market is flooded with a broad spectrum of robots
ranging from those used in industry, for specialized purposes, to domestic ones and
finally to down-to-earth toy models. Each of these has its own dedicated custom hardware
and software, a problem that makes connection to a robots’ world a very convoluted
assignment. To sum up what needs to be looked into seriously is the formalization of the
robot’s interfacing circuitry, provision of a common command language and the setting
up of protocols for comprehending and sending them over the Internet to the system that
physically serves the robot(s). Without such features manufacturers and robot users will
continue to grope in the dark trying to reinvent a connecting mechanism every time they
concieve or wish to use a new robot. Protocols will also have to be evolved for supporting
agents that will serve and resolve autonomous decision-making issues that require
intelligence. One scenario where this is essential is Robot navigation.
The throughput in the Web based control strategy is erratic and unpredictable making
autonomy a vital issue to such robots. Such interfaces should guide the robot safely even
if the network has failed. The user interfaces for web based robots have to be very
user-friendly as the web users have virtually no knowledge of robot programming and
control. The information gathered by the robot should be comprehended not only by the
robot but also by the end-user. Innovative mechanisms have to be used to handle robot
commands issued by a large number of users connected to the web.
Prima facie, tethering a robot to the Internet appears a fairly routine and trivial
task but as one delves deeper into the problem, developing a graphical user interface for
a second and different one and connecting it to the same environment makes it a highly
complex task. The amount of work and time that goes into realizing this mission remains
enormous.
back
