U
SING THE
R
OBOT
C
ONNECTING TO
R
OBOTS
45
7.9 Connecting to Robots
Communication with a robot is available through:
•
Direct interaction with the robot. This type of
communication refers to the direct operation of
the robot using the user interface. There are
some instructions which can only be issued using
this method of communication.
•
Direct access using a smartphone, tablet, or
personal computer.
•
Remote access via the web server. This method
of communication allows a user to connect to the
robot using a smartphone, tablet, or personal
computer, via a web server using the internet.
•
A user account is required to access the web
server. This depends on the concepts of Entities,
Users and Roles, and Robots.
Through access to the web server the user can:
•
Receive notifications about problems encoun-
tered by the robot (alarms and warnings).
•
Issue commands to remotely control the robot,
such as send to station, start from station, etc.
•
Change or remotely configure some parameters,
such as the working hour.
•
Monitor the performance of the robot.
•
Implement automatic software updates.
7.9.1 Entities, Users and Roles, Robots
Entities
An entity is a group of users and robots associated with
a "site". Each entity can have a number of robots that
are used within the site.
There are five entities in the image below that are
related in a hierarchical structure. The parent entity is
the "City Authority". It has four child entities:
•
Sports Field 1
•
Sports Field 2
•
Park West
•
Park East
Collision too close to
station ({X}m)
The robot is leaving the
charging station. The
robot encountered an
obstacle (at {X} meters
from the charging
station), but was unable
to move around it
because it was too close
to the charge arms.
Obstacle too close to the
charging station.
DMA Error, on sonars:
{0}
A hardware error in the
sonar control system.
LongCollision ({0}) event
detected
either a lift or a
backwards sensor has
been blocked for at least
10 seconds.
Still in collision
({0})!alarm
A maneuver to avoid a
collision has failed after
one minute.
Wait for no collision
Occurs after a collision.
The robot moves
backwards and then
checks if the obstacle is
still there. It will then
wait until the obstacle
has been removed. This
message appears while it
is waiting.
Did not find the zone due
to collision ({0})
Robot has crossed the
peripheral wire, but was
unable to re-enter the
zone to be mowed
because of an obstacle.
ManualTask shall not
complete: MotorDrive is
in safety.
Robot did not start.
The wire is currently
configured to be
ignored.
Robot sends a cautionary
message before starting
work. It can come out of
its area and there is a
risk it could fall into
water
Cannot start MotorMow
If we are in
Alarm/Safety. Check
navigation.
Robot was asked to
start, but an existing
alarm has not been
cleared.
Error Message
Description
3
1
2
6
8
0
4
5
7
9
X
DRAFT
05-23-2019