Troubleshooting guide (en) 07/2020 - v.1.1 ©Copyright 2019-2020: Mobile Industrial Robots A/S.
9
Error code
Error type
Description
Solution
504, "Battery
MIR 100/200:
Unable to
detect
hardware
configuration."
Hardware
error.
Can resolve
itself.
There is an error in the
robot software that
prevents it from
determining the
hardware configuration.
Reboot the robot. If the problem
persists, and you have not updated to
the latest software, it is recommended
to update your robot. this may solve
the issue.
If the issue occurred after a software
update to the latest version, try to roll
back to a functioning software version
and report the issue to Technical
Support.
If the issue persists, execute a
USB restore. See the guide
How to USB
restore MiR100/MiR200
, found on the
Distributor site.
601, "Teensy:
Gyroscope data
timed out - Last
Gyroscope
message
received %
(seconds)d
seconds ago"
Hardware
error.
Can resolve
itself.
The MiR board is not
receiving data from the
gyroscope.
Try rebooting the robot. If the issue
persists, check cable 110 that connects
the robot computer to the MiR board
(see
and
). If the
cable is correctly connected, try to
replace the cable or the MiR board.
602, "Teensy:
Gyroscope data
is jumping
ALOT!"
Hardware
error.
Can resolve
itself.
See error
Gyroscope data timed
out - Last Gyroscope
message received %
(seconds)d seconds ago"
above
650, "Unable to
find
LightController
MCU"
Hardware
error.
Can resolve
itself.
The connection from the
robot computer to the
MiR board is faulty.
Try rebooting the robot. If the issue
persists, check cable 110 that connects
the robot computer to the MiR board
(see
and
). If the
cable is correctly connected, try to
replace the cable or the MiR board.