CSP LMC Troubleshooting

Since the CSP LMC is the entry point of all the CSP sub-elements, the State, ObsState and HealthState of the CSP LMC have to reflect also the State, ObsState and HealthState of all the CSP subsystems. In order to identify the cause of a particular condition of the CSP LMC, the starting point is to understand the subsystems status. For doing that, we have defined some tables to link the status of the CSP LMC and the one of the subsystems.

Recover from a FAULT obsState

If something goes wrong with the observation, the obsState of the Mid CSP.LMC Subarray could transition to FAULT. Note that this condition differs from the one where the State of a TANGO Device is in FAULT (see below). To recover from this situation, issue the Restart command. This command will release also all the resources, bringing the subarray into an EMPTY obsState.

Considering the deployment and proxies defined in the example page, the sequence of operations and responses is:

csp_sub1.obsState -> FAULT

csp_sub1.restart()

csp_sub1.commandResult -> ('restart', '1')
csp_sub1.obsState -> RESTARTING
csp_sub1.commandResult -> ('restart', '0')
csp_sub1.obsState -> EMPTY

Please note that if the MID CBF device AdminMode is DISABLE/UNKNOWN, the CSP LMC is not able to communicate with it. For this reason, despite the restart command, the CSP LMC will go into ObsState FAULT.

In this case, the best approach should be to set the AdminMode to OFFLINE and then to ONLINE/MAINTENANCE before proceeding with the restart command.

Recover from a FAULT State

When an internal error occours in the Mid CSP.LMC Subarray or in the Controller, the DevState (State) of the device can transition to FAULT. To recover from this condition, the Reset command needs to be issued. Successufull execution of this command will return the device in its initial state, that is OFF/EMPTY for subarrays and STANDBY for the Controller.

Recover from a subarray FAILED HealthState

When the DishID-VCC map configuration fails, the subarrays HEALTHSTATE goes to FAILED. In this condition, the ON command cannot be issued to the MID CBF device. To solve this situation, a new successful InitSysParam command has to be issued.