SL500 - Is not initializing after check 3717 and 5037.

Asset ID:	1-72-2221414.1
Update Date:	2018-01-11
Keywords:

Solution Type Problem Resolution Sure

Solution 2221414.1 : SL500 - Is not initializing after check 3717 and 5037.

Applies to:

Sun StorageTek SL500 Modular Library System - Version All Versions and later
Information in this document applies to any platform.

Symptoms

The SL500 showing in SLConsole library with red flag.

The SL500 will not initialize after reboot via SLConsole and lost communication with SLConsole.

The ping command was responding with success.

No cartridge in hand.

Changes

Cause

Robot Module - Reach and Gripper are failing during initialization.

2017-01-06T16:13:24.768 warn 0.0.0.1.0 0000 "director_verde_init_reach_and_grip: Reach sweep failed, retrying"
2017-01-06T16:13:25.757 warn 0.0.0.0.0 5037 "Asynchronous shutdown request for track"
2017-01-06T16:13:25.804 warn 0.0.0.0.0 5037 "Asynchronous shutdown request for z"
2017-01-06T16:13:25.843 warn 0.0.0.0.0 5037 "Asynchronous shutdown request for wrist"
2017-01-06T16:13:25.924 warn 0.0.0.0.0 5037 "Asynchronous shutdown request for reach"
2017-01-06T16:13:25.936 error 0.0.0.1.0 0000 "Director - initResponse() Initialize: failed init of reach and grip.; End of Text"
2017-01-06T16:13:26.024 warn 0.0.0.0.0 1104 "LibifLibrary::LibifLibrary() 0x10261110 - attempt to create a duplicate LibifLibrary"
2017-01-06T16:13:26.026 error 0.0.0.0.0 3717 "IfmInitThread:Failure to Initialize...reason==Robot initialization failed - GOING INOP"

Solution

Replaced Robot Module

Attachments

This solution has no attachment