| Asset ID: |
1-72-1020246.1 |
| Update Date: | 2017-09-25 |
| Keywords: | |
Solution Type
Problem Resolution Sure
Solution
1020246.1
:
SL500 - Robot Goes INOP with Result Code 5416
| Related Items |
- Sun StorageTek SL500 Modular Library System
|
| Related Categories |
- PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: SL500 Library
|
PreviouslyPublishedAs
254829
Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Confidential for Partners and Oracle Support personnel
Applies to:
Sun StorageTek SL500 Modular Library System - Version Not Applicable and later
All Platforms
Symptoms
SL500 robot goes INOP due to RC_5416
RC5426
Result code 5426
Failed target calibration
Going Inop
Robot initialization failed
Fails to initialize
5416 "Targeting packet received from scanner too short to contain valid data"
Log history (1)
2009-02-28T02:29:50.951, 0.0.0.0.0, 502, robot, /usr/local/bin/Ifm, error, 0000, 5416, "Director - putResponse() cmo_calibrate failed to find target for address (LMRC) 0,1,1,4 after 2 attempts, cmo_status=3; End of Text"
2009-02-28T02:30:43.731, 0.0.0.0.0, 502, robot, /usr/local/bin/Ifm, error, 0000, 5416, "Director - putResponse() cmo_calibrate failed to find target for address (LMRC) 0,1,1,4 after 2 attempts, cmo_status=3; End of Text"
2009-02-28T02:30:43.789, 0.0.0.0.0, 3202, ifm, , error, 3000, 3313, "(request id = HOST/0x101bbac0) IfmMove::doPut(): move back to source from (LMRC) 0,1,1,4 failed, going inop"
2009-02-28T02:30:43.897, 0.0.0.0.0, 3202, ifm, , error, 3000, 3322, "(request id = HOST/0x101bbac0) IfmMove::doPut() to (LMRC) 0,1,1,4 : cartridge in hand, going inop
Log history (2)
2009-03-02T02:07:07.019, 0.0.0.0.0, 502, robot, /usr/local/bin/Ifm, error, 0000, 5416, "Director - auditResponse() : cmo_user_audit: Failed target calibration for (LMRC) 0,1,1,4, result code=5416"
2009-03-02T02:07:07.064, 0.0.0.0.0, 3202, ifm, , error, 0100, 3717, "IfmInitThread:Failure to Initialize...reason==Robot initialization failed - GOING INOP"
Log history (3)
2009-03-04T01:59:41.336, 0.0.0.0.0, 503, robot, /usr/local/bin/Ifm, error, 0000, 5010, "Director - fetchResponse() servo mech z event 5010 at 49231 tachs, 11394 mils"
2009-03-04T01:59:41.354, 0.0.0.0.0, 3202, ifm, , error, 3000, 3312, "(request id = HOST/0x101bbac0) ***ERROR::IfmMove::doFetch(): WE ARE INOP"
Changes
{CHANGE}
Cause
{CAUSE}
Solution
Resolution
Physical mis-alignment between Base Module and DEM
Replaced robot twice but problem was not fixed.
All above logs indicated error detected area is 0,1,1,4 and positioned 11,394mils = 29cm from the top.
Do a visual inspection around mentioned area and found some distortion by the chassis.. (Between BM and DEM)
Attached picture shows chassis distorted.
SL500, Initialization failure, RC5416
Attachments
This solution has no attachment
