SL150 - Robot Malfunction, 0064 - ROBOT_Z_INTERNAL_ERROR - Fault Code:9131
(Doc ID 2455952.1)
Last updated on JULY 25, 2022
Applies to:
StorageTek SL150 Modular Tape Library - Version All Versions and laterInformation in this document applies to any platform.
Symptoms
When robot initializes, it ends up slanted in the library.
2018-09-28 08:09:55 0064 - ROBOT_Z_INTERNAL_ERROR - Fault Code:9131
2018-09-28T08:02:03.083, 0.0.0.0.0, 519, robot, /usr/local/bin/Ifm, error, 0000, 5088, "Director - initResponse() directorSelfInit; srv_z_sweep: move up to Un-Slack failed. mcuIfStatus = 1, mechStatus = 1; End of Text"
2018-09-28T08:02:03.091, 0.0.0.0.0, 3202, ifm, , error, 0100, 5088, "IfmInitThread:Failure to Initialize...reason==Z failed to detect Unslack during Z Sweep up - GOING INOP"
2018-09-28T08:05:38.828, 0.0.0.0.0, 519, robot, /usr/local/bin/Ifm, error, 0000, 5084, "Director - initResponse() directorSelfInit; srv_z_sweep: first move up past z home sensor failed. Failed to see Z home sensor, reached z range limit 6713 steps; End of Text"
2018-09-28T08:05:38.843, 0.0.0.0.0, 3202, ifm, , error, 0100, 5084, "IfmInitThread:Failure to Initialize...reason==Failed to detect the Z Home Sensor during Z Sweep - GOING INOP"
2018-09-28T08:06:00.884, 0.0.0.0.0, 000, VMonitor, , error, 0000, 7027, "VMonitorDriveInit driveInfo::issueCommand(): Drive Get Info Response Bad Result Code = 6414 For Drive ID 1"
2018-09-28T08:09:52.983, 0.0.0.0.0, 519, robot, /usr/local/bin/Ifm, error, 0000, 5088, "Director - initResponse() directorSelfInit; srv_z_sweep: move up to Un-Slack failed. mcuIfStatus = 1, mechStatus = 1; End of Text"
2018-09-28T08:09:52.993, 0.0.0.0.0, 3202, ifm, , error, 0100, 5088, "IfmInitThread:Failure to Initialize...reason==Z failed to detect Unslack during Z Sweep up - GOING INOP"
2018-09-28T08:10:15.024, 0.0.0.0.0, 000, VMonitor, , error, 0000, 7027, "VMonitorDriveInit driveInfo::issueCommand(): Drive Get Info Response Bad Result Code = 6414 For Drive ID 1"
2018-09-28T08:10:37.063, 0.0.0.0.0, 000, VMonitor, , error, 0000, 7027, "VMonitorDriveInit driveInfo::issueCommand(): Drive Get Info Response Bad Result Code = 6414 For Drive ID 3"
2018-09-28T08:10:59.099, 0.0.0.0.0, 000, VMonitor, , error, 0000, 7027, "VMonitorDriveInit driveInfo::issueCommand(): Drive Get Info Response Bad Result Code = 6414 For Drive ID 4"
2018-09-28T08:19:09.284, 0.0.0.0.0, 519, robot, /usr/local/bin/Ifm, error, 0000, 5088, "Director - initResponse() directorSelfInit; srv_z_sweep: move up to Un-Slack failed. mcuIfStatus = 1, mechStatus = 1; End of Text"
2018-09-28T08:19:09.298, 0.0.0.0.0, 3202, ifm, , error, 0100, 5088, "IfmInitThread:Failure to Initialize...reason==Z failed to detect Unslack during Z Sweep up - GOING INOP"
O,0061,2018-09-28T07:48:02.853,9103,ROBOT_Z_RANGE_ERROR,1,Robot,,,,,,,,,Check for unseated tape. Inspect/replace robot
I,,2018-09-28T08:01:47.831,,,,,,,,,,,,,----> Library Start-up Detected <---- FW Version:0201 (1.34.00)
C,0061,2018-09-28T08:02:04.843,9103,ROBOT_Z_RANGE_ERROR,,,,,,,,,,,Resolved
O,0062,2018-09-28T08:02:05.848,9131,ROBOT_Z_INTERNAL_ERROR,1,Robot,,,,,,,,,Replace robot
I,,2018-09-28T08:05:23.582,,,,,,,,,,,,,----> Library Start-up Detected <---- FW Version:0201 (1.34.00)
C,0062,2018-09-28T08:05:40.565,9131,ROBOT_Z_INTERNAL_ERROR,,,,,,,,,,,Resolved
O,0063,2018-09-28T08:05:40.576,9135,ROBOT_Z_HOME_SENSOR_INIT_ERROR,1,Module 1 Chassis,2,Robot,,,,,,,Check base module locate sensor. Inspect/replace base module chassis. Inspect/replace robot
I,,2018-09-28T08:09:37.708,,,,,,,,,,,,,----> Library Start-up Detected <---- FW Version:0201 (1.34.00)
C,0063,2018-09-28T08:09:54.732,9135,ROBOT_Z_HOME_SENSOR_INIT_ERROR,,,,,,,,,,,Resolved
O,0064,2018-09-28T08:09:55.736,9131,ROBOT_Z_INTERNAL_ERROR,1,Robot,,,,,,,,,Replace robot
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |