• Not Answered

deltaV v. 13.0 HMI lost communication with CSLS, historian server remained connected (trend is not interrupted)

Dear Sirs/Madam,

We have deltaV v. 13.0 installed in our offshore plaforms. Last week a strange error happened. our HMI is lost all signals from 2 CSLSes, other CSLSes (connected to the same SZ controller) are still functional with following alarm messages:

126 2:18:33 AM SIS_EVENT PROCESS ST-PIP-SIS PIP-FCS-SZ-01 PIP-USD-4320-SO SIS Start Up Bypass Module SIF_ERRORS 4-INFO Condition Cleared An input block or parameter reference has Bad status on its output
127 2:18:33 AM SIS_EVENT PROCESS ST-PIP-SIS PIP-FCS-SZ-01 PIP-USD-2956-SO SIS Start Up Bypass Module SIF_ERRORS 4-INFO Condition Cleared An input block or parameter reference has Bad status on its output
128 2:18:33 AM SIS_EVENT PROCESS ST-PIP-SIS PIP-FCS-SZ-01 PIP-USD-2806-SO SIS Start Up Bypass Module SIF_ERRORS 4-INFO Condition Cleared An input block or parameter reference has Bad status on its output
129 2:18:31 AM SIS_EVENT PROCESS ST-PIP-SIS PIP-FCS-SZ-01 PIP-USD-4320-SO SIS Start Up Bypass Module SIF_ERRORS 4-INFO Condition Set An input block or parameter reference has Bad status on its output
130 2:18:31 AM SIS_EVENT PROCESS ST-PIP-SIS PIP-FCS-SZ-01 PIP-USD-2956-SO SIS Start Up Bypass Module SIF_ERRORS 4-INFO Condition Set An input block or parameter reference has Bad status on its output
131 2:18:31 AM SIS_EVENT PROCESS ST-PIP-SIS PIP-FCS-SZ-01 PIP-USD-2806-SO SIS Start Up Bypass Module SIF_ERRORS 4-INFO Condition Set An input block or parameter reference has Bad status on its output

Then the LSN safety network is switched over for these CSLSes:

74 2:23:08 AM EVENT SYSTEM AREA_A PIP-FCS-SZ-01 LSN COMM ACTIVE 4-INFO Switched to Primary LSN - PIP-SIS-RC-CD2-1
75 2:23:06 AM EVENT SYSTEM AREA_A PIP-FCS-SZ-01 LSN COMM ACTIVE 4-INFO Switched to Secondary LSN - PIP-SIS-RC-CD2-1

During this time: all signals from CSLSes can't be read from HMI but still recorded by Historian server. 

Please help to answer following question:

1. What are possible causes of this incident? 

2. Why LSN is switched to primary then secondary? It should remain in secondary if it's functional, and primary has been fault.

3. I know that DeltaV LSN has star topology and historian server have IP address with second priority after Processional Plus. In my case if Historian server still recorded, Do we have problem with network traffic in deltav control network, or this is just lost communication between SZ controller and CSLS or lost package between HMI and SZ controller.  

Thanks in advance!