Overland Tandberg NEO S Series Service Manual page 40

NEO S-Series Library Service Manual
Error
Code Description
B2 Robotic controller
communication failed
B3 Robotic controller urgent stop
due to a released magazine
B4 Cartridge did not transport
completely
Gripper could not pick
cartridge and CP sensor not
present
After pushing the cart CP
sensor still present
B5 Robotic controller doesn't
respond on command
C0 Network initialization failed
C1 Telnet Interface initialization
failed
C2 Web server initialization failed Check network cable and network
C6 Ping command did not
reached target
C7 Cannot Upgrade from USB
C8 Cannot Upgrade from FTP
C9 Cannot Upgrade Robotic from
Flash
D0 ROM error.
ROM checksum incorrect
10400666-005
User Action
Reset the unit and retry
operation. After several
occurrences contact technical
support
Check if magazine are completely
inserted and retry operation. After
several occurrences contact
technical support
Reset the unit and retry
operation. After several
occurrences contact technical
support
Check network cable and network
configuration. If the error recurs,
contact technical support
Check network cable and network
configuration. If the error recurs,
contact technical support
configuration. If the error recurs,
contact technical support
Check network cable and network
configuration. If the error recurs,
contact technical support
Retry of Firmware upgrade, if not
successful contact technical
support
Retry of Firmware upgrade, if not
successful contact technical
support
Retry of Firmware upgrade, if not
successful contact technical
support
Retry of Firmware upgrade, if not
successful contact technical
support
©2015-20 Overland-Tandberg
Event Codes and Acronyms
Critical Component Status
Robotic probably defect
• No communication from library controller to
robotic controller.
• Robotic hardware not working (cables,
distribution boards, robotics controller).
• Download robotic firmware fails.
Magazines released
Magazine present sensor defect.
• CP sensor defect
• Cartridge sticks in slot/drive
Robotic probably defect
• No communication from library controller to
robotic controller.
• Robotic hardware not working (cables,
distribution boards, robotics controller).
• Download robotic firmware fails.
Library controller probably defect
probably a hardware problem, check library
controller
Library controller probably defect, probably a
hardware problem, check library controller
Library controller probably defect, probably a
hardware problem, check library controller
Library controller probably defect, probably a
hardware problem, check library controller
Library controller probably defect, probably a
hardware problem, check library controller
Library controller probably defect, probably a
hardware problem, check library controller
Library controller probably defect, probably a
hardware problem, check library controller
Library controller probably defect, probably a
hardware problem, check library controller
40
