45
Error Handling
165
50602800
LOG_ALERT
Cannot move without destination point.
166
50702200
LOG_ERR
Starting point is out of global grid map.
167
50702500
LOG_ERR
Path planner got empty data.
168
50704200
LOG_ERR
The global path was not planned within expected time.
169
50712100
LOG_ERR
Path planner failed to get global path.
170
50802200
LOG_ERR
Planner got abnormal pose in local map.
171
50802500
LOG_ERR
Local planner got empty data.
172
50804100
LOG_ERR
The local path was not planned within expected time.
173
50808600
LOG_ERR
The local planner could not get odometer data.
174
50902600
LOG_ERR
Cannot perform the unknown motion.
175
50904200
LOG_ERR
Motion integrator timed out.
176
50909100
LOG_ERR
Motion integrator detected potential collision.
177
51002500
LOG_ERR
Motion manager got empty data.
178
51002700
LOG_ERR
Motion manager found wrong format of pose.
179
51012100
LOG_ALERT
Motion manager failed to initiate (mp_multi).
180
51112100
LOG_ERR
Motion behavior error.
181
60207300
LOG_ALERT
Modbus adapter system is not ready.
182
60205100
LOG_ALERT
There is no desired parameter file(plc_api.cfg).
183
60204200
LOG_ERR
Modbus cannot get a response from WebSocket server.
184
60207200
LOG_ERR
Modbus sent the restart command to the robot, but it
does not work.
185
60406100
LOG_ALERT
Reactor failed to initiate.
186
60406300
LOG_ERR
Reactor exceeds maximum retrying count.
* ‘nn’ on the code: device or special index for this error (00~99)
Table 3: Periodic Maintenance