Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2152273.1
Update Date:2017-09-21
Keywords:

Solution Type  Problem Resolution Sure

Solution  2152273.1 :   SL500 - Robot Down - FSC 5066  


Related Items
  • Sun StorageTek SL500 Modular Library System
  •  
Related Categories
  • PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: SL500 Library
  •  




In this Document
Symptoms
Cause
Solution


Created from <SR 3-12882864861>

Applies to:

Sun StorageTek SL500 Modular Library System - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

SL500 robot is DOWN

Robot is not initializing

Service Required / Service Robot LEDs are on.

Time : 2016-06-15T16:44:49.988
Device Address : 0.0.9.0.2
User : unknown
Requester : default
Activity : 0000
Request Id : /usr/local/bin/Ifm
Level : warn
Result Code : 5066
Text : , "Director - fetchResponse() cmo_user_fetch: Retry Performed 5610; servo mech reach event 5066 at 2776 tachs, 2555 mils"

Time : 2016-06-17T16:47:32.057
Device Address : 0.0.6.0.2
User : unknown
Requester : default
Activity : 0000
Request Id : /usr/local/bin/Ifm
Level : error
Result Code : 5066
Text : , "Director - putResponse() servo mech reach event 5066 at 1473 tachs, 1356 mils"

Time : 2016-06-17T16:47:32.150
Device Address : 0.0.0.0.0
User : unknown
Requester : default
Activity : 3000
Request Id : (null)
Level : error
Result Code : 3313
Text : , "(request id = HOST/0x1021fbd8) IfmMove::doPut(): move back to source from (LMRC) 0,2,2,6 failed, going inop by default"

Time : 2016-06-17T16:47:32.537
Device Address : 0.0.0.0.0
User : unknown
Requester : default
Activity : 3000
Request Id : (null)
Level : error
Result Code : 3313
Text : , "(request id = HOST/0x1021fbd8) IfmMove::commonMoveCommand(): PUT request of tape 004481L3 from (LMRC) 0,1,1,9 to (LMRC) 0,2,2,6 failed:"

Cause

Robot assembly could be faulty.

Logs have shown a 5066 error as a result of an over current on one of the motors during robotic motion. The most likely cause of an over current condition on a motor is that an obstruction was encountered during that motion.

Solution

The most likely cause of an over current condition on a motor is that an obstruction was encountered during that motion.

The FE should check for obstructions that may have caused that motion to stop before it should have.

If no obstructions are found then a robot assembly needs to be replaced.


In this case, FSE has replaced the robot. After replacement the robot came online and working normal now.
 


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback