Table 31 Main error codes (continued)
Error code
Description
B0
Command from the library controller to robotics
controller did not complete in time allotted
B1
Robot controller reported format error on
command from library controller
B2
Communication to robot from library controller
failed
B3
Robot stopped due to a released magazine
B4
"Tape in gripper
expected value
B5
Robotic controller not responding to command
from library controller
B8
Library Extender missing.
1
" sensor did not report the
Details and solution
Reset the device and retry the operation.
Reset the device and retry the operation.
Update the firmware to the latest version.
Power cycle the device and retry the
operation.
Check that all magazines are completely
inserted and retry the operation.
If this error was caused by a manual
magazine removal, replace the magazine
and try the operation again.
In earlier firmware versions, the device could
appear unresponsive if a magazine was left
out of the device too long. Power cycle the
device to restore operation. Update to the
latest firmware version to prevent this issue
in the future.
Update the firmware to the latest version.
Remove the magazines and inspect them for
a stuck tape. If no tapes are stuck in the
magazines, shine a light in one of the open
magazine bays to see if there is a tape in the
robot or drive. If there is a tape in the robot,
replace the magazines and power-cycle the
device. If there is a tape in a drive, replace
the magazines and run the Force Tape Eject
operation. (For MSL2024, see
drive to eject a tape (Support > Force Drive
To Eject Tape)" (page
111)). For MSL4048,
MSL8048, or MSL8096, see
a drive (Support > Force Drive
Eject)" (page
130).)
Run the wellness test
Update the firmware to the latest version.
MSL8048 and MSL8096: If this error occurs
with sub-code 02, verify that the robotics
cable is installed correctly.
Power cycle the device and retry the
operation.
See
"Sub-codes for error B8" (page 170)
details.
If this is a new installation, verify that the
Extender is installed properly and that both
libraries are powered on.
Update the firmware to the latest version.
Power cycle both libraries.
"Forcing the
"Force ejecting
for
Error codes 159