S
We have Mark-VI Control System installed on Hitachi H-25 Gas Turbine. There were no prior Process/ Diagnostic alarms existing on the machine. These are single fuel turbines on gas.
Recently, we had an issue where the turbine tripped on generator lockout relay burnout. The same was checked and restored to healthy by our Electrical team; however we started facing issues on the control end detailed as follows. This resulted in T-core diagnostic alarms prohibiting machine start-up.
Repeated Alarms displayed were as follows:
VCMI IO State Exchange for <T> Failed
VPRO Communications Fault
XMIT Suspended. CPU Switched (reset immediately each time)
Turbine was started by forcing the signals to contribute in removing TCP minor trouble fault. Currently following alarms are displaying as Process:
UCVx Overtemperature
UCVx Airflow or overtemperature trouble
TCP Minor Trouble
Diagnostic:
<T> Slot 6 VSVO Diagnostic Alarm (interestingly, VSVO card in actual is installed on Slot 5)
<T> Slot 1 VCMI Diagnostic Alarm
Details on diagnostic faults in Control Toolbox:
VSVO: VSVO card not online. Servos suicided (code= 46)
VCMI: IONET-1 Communication Failure (Code= 45)
Using DEFAULT Input Data, Rack R0 (Code= 49)
Also, there is some haphazard behavior on timing and the dates being displayed against these alarms are not the actual ones but going back to 1989!
Also, on control toolbox T controller is showing Boot status.
Additionally, physically on T Controller VCMI card IONET 1, no LED is blinking and M-Var and voltage indication from system going to DCS are also in bad PV (these signals are going from Analog card installed in Simplex at the T controller only).
As rectification measures, before turbine start-up; VSVO card was replaced; power down of T-controller and respective Protection controller (Z); however the problem is persisting. Field signals for VSVO from IGV, GCV and SRV for servos were also verified and found OK. The turbine is now running for 4-5 days with no other abnormality other than the observations detailed above. There was an idea to download the logic again onto T-controller, however i do not think that this would be an issue since other two controllers (R & S) are working fine. Most likely to me it seems to be either VCMI card issue or some problem with the VSVO particular slot.
Would appreciate some insight and probable reason into these existing and diagnostic alarms.
Recently, we had an issue where the turbine tripped on generator lockout relay burnout. The same was checked and restored to healthy by our Electrical team; however we started facing issues on the control end detailed as follows. This resulted in T-core diagnostic alarms prohibiting machine start-up.
Repeated Alarms displayed were as follows:
VCMI IO State Exchange for <T> Failed
VPRO Communications Fault
XMIT Suspended. CPU Switched (reset immediately each time)
Turbine was started by forcing the signals to contribute in removing TCP minor trouble fault. Currently following alarms are displaying as Process:
UCVx Overtemperature
UCVx Airflow or overtemperature trouble
TCP Minor Trouble
Diagnostic:
<T> Slot 6 VSVO Diagnostic Alarm (interestingly, VSVO card in actual is installed on Slot 5)
<T> Slot 1 VCMI Diagnostic Alarm
Details on diagnostic faults in Control Toolbox:
VSVO: VSVO card not online. Servos suicided (code= 46)
VCMI: IONET-1 Communication Failure (Code= 45)
Using DEFAULT Input Data, Rack R0 (Code= 49)
Also, there is some haphazard behavior on timing and the dates being displayed against these alarms are not the actual ones but going back to 1989!
Also, on control toolbox T controller is showing Boot status.
Additionally, physically on T Controller VCMI card IONET 1, no LED is blinking and M-Var and voltage indication from system going to DCS are also in bad PV (these signals are going from Analog card installed in Simplex at the T controller only).
As rectification measures, before turbine start-up; VSVO card was replaced; power down of T-controller and respective Protection controller (Z); however the problem is persisting. Field signals for VSVO from IGV, GCV and SRV for servos were also verified and found OK. The turbine is now running for 4-5 days with no other abnormality other than the observations detailed above. There was an idea to download the logic again onto T-controller, however i do not think that this would be an issue since other two controllers (R & S) are working fine. Most likely to me it seems to be either VCMI card issue or some problem with the VSVO particular slot.
Would appreciate some insight and probable reason into these existing and diagnostic alarms.