Mark 5 problem

C

Thread Starter

calvein

Hi,

We have a frame V GE make machine with Mark V control. Recently, there have been a number of diagnostic alarms in the machine and the machine tripped on L3SFLT, i.e.- Startup/ shutdown failure trip/ control system fault trip. Also, the processors R, S and T repeatedly fail and we have to reboot them. Can somebody please suggest something? If needed, I can give the complete set of diagnostic alarms. Please help.
 
B

Bob Johnston

This probably the least information on a fault report that we've seen. How do you reckon we can try and help with such little information.
Anyway, let's have a try. Sure send us the Diagnostics. What exactly do you mean by "processors R, S and T repeatedly fail" How do they fail?? Why do you need to re-boot?? Are you running with ground faults??
 
Okay, sorry for replying so late. To elaborate with the problem, the frame V machine running on Mark V DOS based system tripped once with the following alarms-

L86TXT- Exh high temp trip
L3SFLT- Startup shutdown communication failure trip

Along with these causes of tripping, the resultant alarms seen were-

Hydraulic protective trouble trip, FSR Gag not at Max.

The trip log was checked and it was seen that none of the exh TCs had crossed the limit. Also, TTXM was consistently well below TTRXB throughout. At that time, we made the mistake of not researching L3SFLT further.

A spurious trip was assumed and the machine was re-started. It tripped again after running for some four hours on L3SFLT. Further, it was observed that a lot of logics, which do not appear using the conventional search, appeared forced to 0 on the logic forcing display. It was also seen that in the PREVOTE DATA DISPLAY, some of the processors were repeatedly not responding. (The columns went blue and the data froze, while mismatching with the healthy processors)

We assumed the processors were hung, and everything became fine when that particular processor was rebooted. But this problem occurred every time a startup attempt was made. After a lot of discussions, the DCC/ LCC card was replaced on all the processors, and the EEPROM was also replaced that was compatible with windows system. I am not sure about whether the DCC or the LCC card was replaced, as it was done by the BGGTS expert. (BHEL GE GAS TURBINE SYSTEMS)

Now, the machine is running OK, but alarms such as “voter mismatch-L3CPOL” keep coming repeatedly. I am not sure whether the problem has been permanently solved.

The alarms that appeared on the second trip are as follows:

2:08:42 AM INLET TEMP LOW TO ATOMISING AIR COMPRESSOR
2:11:18 AM FORCED LOGIC SIGNAL DETECTED
2:12:06 AM DIAGNOSTIC ALARM <C><Q>
2:12:11 AM DIAGNOSTIC ALARM <C><Q>
2:12:20 AM DIAGNOSTIC ALARM <C><Q>
2:12:28 AM GT FIRING PERMISSIVE FROM DCS
2:13:52 AM EXHAUST SPREAD1 ABOVE ALLOWABLE SPREAD
2:13:54 AM STDBY ACCESS COMPT COOLING FAN RUNNING
2:13:57 AM STDBY ACCESS COMPT COOLING FAN RUNNING
2:13:59 AM TURB ACCE COMPT COOLING FAN TROUBLE
2:14:57 AM EXHAUST SPREAD1 ABOVE ALLOWABLE SPREAD
2:14:57 AM EXHAUST SPREAD1 ABOVE ALLOWABLE SPREAD
2:14:58 AM EXHAUST SPREAD1 ABOVE ALLOWABLE SPREAD
2:24:35 AM DIESEL FAILURE TO STOP
2:27:19 AM DIVERTER DAMPER INTERMEDIATE POSITION /LIMIT SW TRBL
2:27:39 AM BOILER DAMPER POSITION TROUBLE
2:44:21 AM DIVERTER DAMPER INTERMEDIATE POSITION /LIMIT SW TRBL
2:45:19 AM COMMON IO COMMUNICATION LOSS
2:45:20 AM DIAGNOSTIC ALARM <C><Q>
2:45:21 AM DIAGNOSTIC ALARM <C><Q>
2:45:29 AM COMMON IO COMMUNICATION LOSS
2:56:00 AM INJECTION TO FUEL RATIO LOW: 4 MIN AVG
3:15:34 AM DIAGNOSTIC ALARM <C><Q>
3:15:35 AM FORCED LOGIC SIGNAL DETECTED
3:15:35 AM INJECTION TO FUEL RATIO LOW: 4 MIN AVG
3:15:43 AM FORCED LOGIC SIGNAL DETECTED
3:15:43 AM INJECTION TO FUEL RATIO LOW: 4 MIN AVG
3:15:43 AM COMMON IO COMMUNICATION LOSS
3:15:59 AM COMMON IO COMMUNICATION LOSS
3:52:00 AM INJECTION TO FUEL RATIO LOW: HOURLY AVG
4:47:44 AM COMMON IO COMMUNICATION LOSS
4:47:49 AM DIAGNOSTIC ALARM <C><Q>
4:47:56 AM COMMON IO COMMUNICATION LOSS
4:48:02 AM COMMON IO COMMUNICATION LOSS
4:48:02 AM WHEELSPACE TEMP DIFFERENTIAL HIGH
4:48:03 AM WHEELSPACE TEMP DIFFERENTIAL HIGH
4:48:13 AM COMMON IO COMMUNICATION LOSS
4:49:35 AM COMMON IO COMMUNICATION LOSS
4:49:46 AM COMMON IO COMMUNICATION LOSS
4:50:50 AM COMMON IO COMMUNICATION LOSS
4:51:06 AM COMMON IO COMMUNICATION LOSS
4:53:15 AM COMMON IO COMMUNICATION LOSS
4:53:16 AM DIESEL FAILURE TO STOP
4:53:17 AM DIAGNOSTIC ALARM <C><Q>
4:53:33 AM DIAGNOSTIC ALARM <C><Q>
4:53:42 AM COMMON IO COMMUNICATION LOSS
4:53:45 AM COMMON IO COMMUNICATION LOSS
4:53:52 AM DIESEL FAILURE TO STOP
4:53:55 AM COMMON IO COMMUNICATION LOSS
4:54:12 AM COMMON IO COMMUNICATION LOSS
4:54:12 AM DIESEL FAILURE TO STOP
4:54:12 AM DIESEL FAILURE TO STOP
4:54:22 AM COMMON IO COMMUNICATION LOSS
4:54:35 AM COMMON IO COMMUNICATION LOSS
4:54:36 AM DIAGNOSTIC ALARM <C><Q>
4:55:13 AM HYDRAULIC PROTECTIVE TROUBLE
4:55:13 AM START-UP SHUTDOWN <C> COMM FAILURE-TRIP
4:55:14 AM DIESEL FAILURE TO STOP
4:55:14 AM INLET TEMP LOW TO ATOMISING AIR COMPRESSOR
4:55:14 AM TURB ACCE COMPT COOLING FAN TROUBLE
 
Top