MDT DCS: Trouble-Shooting Hints for Experts

MDT GAS

FSM State Unknown

GAS DUs in state UNKNOWN usually indicate that there is no update of gas data. DUs also go to UNKNOWN if the DIP quality 'invalid' or 'bad' flag is set for data copied from ATLGCSIS2, i.e. for the DIP subscription itself. This happens very rarely.

Steps to locate the problem:

• Check whether the DPE gas_SCS_MDT_PlcCounter in the MDT Gas Project is updating. If YES, the problem is in the FSM only.

• make sure the ATLGCSIS2 project is available/reachable
• Check whether the DPE ATLGCSIS2:gas_MDT_PlcCounter is updating.
• make sure the MDT script mdtGas_dipDpConnect.ctl is running in the MDT Gas Project

• check if the gas control system is publishing data via DIP. In order to do so,
  • log on to the MDT SCS,
  • start the tool dipBrowser.jar from the shortcut on the desktop,
  • navigate to dip/ATLAS/GCS/ATLMDT and check if values are updated there.
• If there are no updates, or the item ATLAS/GCS is not there at all, call the MDT gas expert and ask him to check whether the gas system itself runs. If not, the situation will be handled by the gas expert. If yes, the gas piquet should be called for restarting the DIP publication manager in the gas PVSS projects, they have been instructed how to do so.
• If there are updates, ask the central DCS experts for a check on the ATLGCSIS2 project and DIP subscription.

FSM Status WARNING/ERROR without any gas alarms present

The FSM status for GAS DUs is directly linked to the alarms of the corresponding gas device (Mixer, Channel, ....). If an FSM status other than OK is observed with no alarm present, neither on the alarm screen nor visible in the FSM panels,

• Execute the FSM action REFRESH on the MDT GAS tree, forcing a new execution of the FSM DU callbacks.

(This is a known problem, still unsolved on FSM level)

-- StephanieZimmermann - 21 Aug 2008