T127: Robotics Communication Error; T128: Incompatible Robot Installation - IBM TS3310 Maintenance Information

Detection Scenario
Root Causes
Possible FRUs
Resolution

T127: Robotics Communication Error

Description
Detection Scenario
Root Causes
Possible FRUs
Resolution

T128: Incompatible Robot Installation

Description
Detection Scenario
Root Causes
Possible FRUs
Resolution
6-52
TS3310 Tape Library Maintenance Information
Robotics firmware reports a specific hardware error identifying the Imager
component of the Picker assembly as the source.
1. Obstructions in the view path of the robot Imager.
2. Electrical hardware failure.
v Picker Assembly (if Model 1 or Model 2 robot is installed)
v Robot Assembly (if Model 2 robot is installed)
Perform "DR092: Resolve Robotics Hardware Error - Scanner" on page 6-88.
This ticket occurs with Model 2 robots only.
GUI Description: The library controller firmware lost communication with
the robotics subsystem.
Explanation: The library is not able to communicate with the Model 2
robotics subsystem. This ticket is generated if the library had previously
established a communication link with the robotics subsystem, but that link
has now been lost and cannot be reestablished.
The library firmware did establish communication with the robotics
subsystem but encountered a communication failure during operation and
communication could not be reestablished.
1. Damaged module terminator or module-to-module cable with bent or
broken pins.
2. An intermittent door-open condition disconnecting power from the robot.
3. A cable spool or connection problem.
4. A picker assembly hardware failure.
5. A Y-carriage assembly connection problem.
6. A robot controller board hardware or software failure.
7. An LCB serial communication link failure.
v Cable Spool
v Robot Assembly (replace entire unit)
Perform "DR093: Resolve Robotics Communication Error" on page 6-88.
GUI Description: The library control firmware detected that an incompatible
robot is installed.
Explanation: The library has an incompatible robot installed. This may
happen when a GA-style (Model 1) robot is replaced with the Model 2 robot,
or vice versa.
Library firmware detects a change in robot model, which is incompatible
with the current library configuration.
The robot was replaced with an incompatible robot type.
v Robot Assembly
Perform "DR094: Resolve Incompatible Robot Installed" on page 6-88.