Mark-V voter mismatch

S

Thread Starter

Seobong

Hello? In our GE Large steam Turbine Mark V TMR system,

The following Diagnostic Alarms are persisting.
Could anyone please guide me to locate where is the problem? I understand these alarms are from
S-Core SDCC card.

Q1)
ㅇAlarms
IOMA TMS320 processer lagging
Voter mismatch, <S> SFL1
Voter mismatch, <S> FP_MSP
Voter mismatch, <S> SSDIFF2
Voter mismatch, <S> DV_ERR
Voter mismatch, <S> DV
Voter mismatch, <S> _L0059_SP
Voter mismatch, <S> L86CSTALL


Q2)
&#12615;Alarm
Voter mismatch, <T> SFL1
Voter mismatch, <T> FP_MSP
Voter mismatch, <T> SSDIFF2
Voter mismatch, <T> DV_ERR
Voter mismatch, <T> DV
Voter mismatch, <T> _L0059_SP
Voter mismatch, <T> L86CSTALL

The following Diagnostic Alarms are persisting only 12sec.
Could anyone please guide me to locate where is the problem?
 
Seobong,

<b>When did this problem start?</b>

If this problem has just recently started, <b>What has recently changed with regard to the way the turbine is being operated?</b> (Perhaps a new Control Room operations manager has instructed the operators to do something differently than was done in the past?)

Were some cards recently replaced in the Mark V; if so, which ones?

Did the problem occur after a maintenance outage, perhaps when the Mark V was powered down, and the Diag. Alarms began after the Mark V was powered up again?

Is the turbine running when these alarms are annunciated?

What is the grid frequency doing when these alarms are being annunciated?

What is "Q1" and what is "Q2"?

Is the generator breaker synchronized automatically (using the AutoSynch feature of the Mark V) or manually? Is the AutoSynch feature enabled when the unit is on-line and generating power, or is it disabled? (It should be disabled (usually automatically) after the generator breaker is closed and the unit is on-line, producing power.)

I can tell you that the L86CSTALL is a Diagnostic Alarm associated with Gas Turbines. (GE has a very annoying habit of not disabling gas- or steam turbine alarms when the panel is supplied for a steam- or gas turbine application....)

The first "group" of Diag. Alarms (Q1) are being annunciated by <S> processor, and probably more specifically by the TCEA card in Loc. 3 of the <P> core which is associated with <S> processor.

The second "group" of Diag. Alarms (Q2) are being annunciated by <T> processor, and probably more specifically by the TCEA card in Loc. 5 of the <P> core which is associated with <T> processor.
 
Thank you for your reply. And I'm sorry. I didn't share all of informations.

Well, the alarms was persisting from August 23. And then in September, another alarms are beginning.
(similar with the first alarms but little bit different. It's from <T>core)

Actually when the first alarms began. I've made a plan to replace a card SDCC from <S>core. According to TMS320 lagging alarm (&#8251;trouble shooting manual).
Then now I have another alarms in <T>core.
but I'm not sure that I replace the SDCC card in <S>core. Is that best way to solve the problem with <S>, <T> voter mismatch alram? If not? What is the real reason?
Why the Alarms persisting? So I need your help.

&#8251;Trouble shooting manual
0284 ;IOMA TMS320 LAGGING

CAUSE
The TMS320 coprocessor attached to the IOMA is not responding fast enough.
Since this should never be the case, this probably means that the TMS320 is, in fact, not running at all.
This diagnostic is currently only used on "B" system cards.

EFFECT
All phase-locked loop computations from the IOMA are suspect, including the BUS, GEN, CPD, and synch permissive signals.

ACTION
Make sure that JP33 is closed on the DCC cars. This jumper connects the oscillator to the TMS320 processor.
The SDCC card, however, does not have this jumper. If all else fails, try replacing the DCC/SDCC card.<pre>
1. First Alarms in <S>core

1) Aougust 23
&#12615;HMI Alrams
Time__________Date_____________Alarm ID________Message

21:10:38:15___8/23/2013________D2361___________Voter mismatch, <S> L86CSTALL
21:10:11:15___8/23/2013________D2363___________Voter mismatch, <S> _L0059_SP
21:09:50:15___8/23/2013________D3740___________Voter mismatch, <S> SSDIFF2
21:09:43:15___8/23/2013________D3737___________Voter mismatch, <S> DV_ERR
21:09:27:15___8/23/2013________D2360___________Voter mismatch, <S> L25X
20:54:13:18___8/23/2013________D3741___________Voter mismatch, <S> FP_MSP
20:54:13:18___8/23/2013________D3735___________Voter mismatch, <S> DV
20:54:06:18___8/23/2013________PD______________DIAGNOSTIC ALARM
20:54:06:00___8/23/2013________D284____________IOMA TMS320 processor lagging

&#12615;Prevote Data Display
23-AUG-2013 21:47:33

Pointname_________Voted__________R________________S_____________T___________Unit

DV________________96.08_________96.47_____________0.00_________96.30_________%
DV_ERR_____________0.00__________0.00___________-40.00_________0.00_________%
SSDIFF2____________0.0___________0.0___________-160.0___________0.0__________deg
FP_MSP__________103.58________103.94___________-40.00________103.54_________%
L25X_______________0_____________0________________1_____________0____________LOGIC
L86CSTALL_________0_____________0________________1_____________0____________LOGIC
_L0059_SP__________0_____________0________________1_____________0____________?

&#12615;IOMA DIAGNOSTICS
<S>
co_firmware_name =
co_firmware_major_rev =00
co_firmware_manor_rev =D8
co_prom_0_chksum =D800
co_prom_1_chksum =D800
co_restarts =2CC9
co_status_196 =D842
co_status_320 =D800
co_host_time_tick =05
co_io_time_tick =00
co_io_state =00A2
co_int_196 =66
co_int_320 =09

<R>,<T>
co_firmware_name =IOMA
co_firmware_major_rev =01
co_firmware_manor_rev =05
co_prom_0_chksum =0000
co_prom_1_chksum =0000
co_restarts =0000
co_status_196 =0000
co_status_320 =0000
co_host_time_tick =19
co_io_time_tick =19
co_io_state =00A7
co_int_196 =00
co_int_320 =00 </pre>
2. Second Alarms in <T>core
(The second Alarms persisting 12sec and then disappear)<pre>
1) September 1
&#12615;HMI Alarms

Time__________Date______________Alarm ID________Message

10:26:10:15___9/1/2013_________D4012___________Voter mismatch, <T> SFL1
10:26:10:15___9/1/2013_________D4002___________Voter mismatch, <T> FP_MSP
10:26:10:15___9/1/2013_________D4001___________Voter mismatch, <T> SSDIFF2
10:26:10:15___9/1/2013_________D3998___________Voter mismatch, <T> DV_ERR
10:26:10:15___9/1/2013_________D3996___________Voter mismatch, <T> DV
10:26:10:15___9/1/2013_________D2875___________Voter mismatch, <T> _L0059_SP
10:26:10:15___9/1/2013_________D2873___________Voter mismatch, <T> L86CSTALL
10:26:10:00___9/1/2013_________D1359___________TCQA Relays dropped on loss of output
10:26:10:00___9/1/2013_________D963____________TCD1 Relays dropped due to IONET failure
10:26:10:00___9/1/2013_________D755____________TCD2 Relays dropped due to IONET failure </pre>
2) September 19 <pre>
&#12615;HMI Alarms

Time__________Date______________Alarm ID________Message

10:26:10:15___9/19/2013________D4012___________Voter mismatch, <T> SFL1
10:26:10:15___9/19/2013________D4002___________Voter mismatch, <T> FP_MSP
10:26:10:15___9/19/2013________D4001___________Voter mismatch, <T> SSDIFF2
10:26:10:15___9/19/2013________D3998___________Voter mismatch, <T> DV_ERR
10:26:10:15___9/19/2013________D3996___________Voter mismatch, <T> DV
10:26:10:15___9/19/2013________D2875___________Voter mismatch, <T> _L0059_SP
10:26:10:15___9/19/2013________D2873___________Voter mismatch, <T> L86CSTALL

&#12615;Prevote Data Display
23-AUG-2013 17:30:33

Pointname_________Voted__________R________________S_____________T___________Unit

DV________________96.08_________96.47_____________0.00_________95.30_________%
DV_ERR____________0.00__________0.00___________-40.00__________0.00_________%
SSDIFF2____________0.0___________0.0___________-160.0___________0.0__________deg
SFDIFF2____________0.0___________0.0_____________-2.50__________0.0__________deg
FP_MSP__________103.58________103.94___________-40.00________103.54_________%
L25X_______________0_____________0________________1_____________0____________LOGIC
L86CSTALL_________0_____________0________________1_____________0____________LOGIC
_L0059_SP__________0_____________0________________1_____________0____________?
SFL1_______________0_____________0_______________64_____________0____________Hz



&#12615;IOMA DIAGNOSTICS
<S>(Only <S>core co_restarts count is Increasing)
co_firmware_name =
co_firmware_major_rev =00
co_firmware_manor_rev =D8
co_prom_0_chksum =D800
co_prom_1_chksum =D800
co_restarts =7824
co_status_196 =D842
co_status_320 =D800
co_host_time_tick =1F
co_io_time_tick =00
co_io_state =00A8
co_int_196 =66
co_int_320 =09

<R>,<T>
co_firmware_name =IOMA
co_firmware_major_rev =01
co_firmware_manor_rev =05
co_prom_0_chksum =0000
co_prom_1_chksum =0000
co_restarts =0000
co_status_196 =0000
co_status_320 =0000
co_host_time_tick =19
co_io_time_tick =19
co_io_state =00A7
co_int_196 =00
co_int_320 =00 </pre>
Thus, 10month ago I replaced all of <R>,<S>(TCQA,TCQB,TCEA,TCDA,TCPA) cores cards and DCC, LCC cards in <C>core.

And there wasn't any power down when the alarms persisting.
Therefore I can see A7 all of cores <R>,<S>,<T> DCC I/O status in mark-V cabinet.

Also, I'd like to show you signal trend but there is no option to uplaod image files. so if you give me your e-mail (My e-mail is [email protected]).

I'll send you the signal image file.
 
C
Apparently <S> core is at A2. If one reads the diagnostic on the core display, one might see Missing I/O card.
Using the keypad, one will probably find that TCEA is missing.

The cards in P core are x,y,and z which match their r,s, and t counterparts.

I would look at the LED diagnostic bars on those x,y,z boards.

I would probably find the LEDs not sequencing on the Y board and replace it. The TCEA boards have their own power supplies that sometimes fail.
 
Thanks for the response!! But I can see A7 all of cores <R>,<S>,<T> DCC I/O status. (Not at A2.) So I guess. It's not the problem about the TCEA. Nevertheless, you gave me great opinions.

Thanks again. So If you have any idea. plz help me.
 
Fist of all, I'm sorry. I make the same thread about mark-V voter mismatch alarms before what I made. Cause I'm really need specific information for my Mark-V. So If someone know the the way to restore to original condition. Please help me.

<b>Moderator's note:</b> This has been added to the original thread.

Second of all, the alarms was persisting from August 23. And then in September, another alarms are beginning.
(similar with the first alarms but little bit different. It's from <T>core)

Actually when the first alarms began. I've made a plan to replace a card SDCC from <S>core. According to TMS320 lagging alarm (&#8251;trouble shooting manual).
Then now I have another alarms in <T>core.
but I'm not sure that I replace the SDCC card in <S>core. Is that best way to solve the problem with <S>, <T> voter mismatch alram? If not? What is the real reason?
Why the Alarms persisting? So I need your help.

&#8251;Trouble shooting manual
0284 ;IOMA TMS320 LAGGING

CAUSE
The TMS320 coprocessor attached to the IOMA is not responding fast enough.
Since this should never be the case, this probably means that the TMS320 is, in fact, not running at all.
This diagnostic is currently only used on "B" system cards.

EFFECT
All phase-locked loop computations from the IOMA are suspect, including the BUS, GEN, CPD, and synch permissive signals.

ACTION
Make sure that JP33 is closed on the DCC cars. This jumper connects the oscillator to the TMS320 processor.
The SDCC card, however, does not have this jumper. If all else fails, try replacing the DCC/SDCC card.

1. First Alarms in <S>core<pre>
1) Aougust 23
&#12615;HMI Alrams
Time__________Date_____________Alarm ID________Message

21:10:38:15___8/23/2013________D2361___________Voter mismatch, <S> L86CSTALL
21:10:11:15___8/23/2013________D2363___________Voter mismatch, <S> _L0059_SP
21:09:50:15___8/23/2013________D3740___________Voter mismatch, <S> SSDIFF2
21:09:43:15___8/23/2013________D3737___________Voter mismatch, <S> DV_ERR
21:09:27:15___8/23/2013________D2360___________Voter mismatch, <S> L25X
20:54:13:18___8/23/2013________D3741___________Voter mismatch, <S> FP_MSP
20:54:13:18___8/23/2013________D3735___________Voter mismatch, <S> DV
20:54:06:18___8/23/2013________PD______________DIAGNOSTIC ALARM
20:54:06:00___8/23/2013________D284____________IOMA TMS320 processor lagging

&#12615;Prevote Data Display
23-AUG-2013 21:47:33

Pointname_________Voted__________R________________S_____________T__ _________Unit

DV________________96.08_________96.47_____________0.00_________96.3 0_________%
DV_ERR_____________0.00__________0.00___________-40.00_________0.00 _________%
SSDIFF2____________0.0___________0.0___________-160.0___________0.0 __________deg
FP_MSP__________103.58________103.94___________-40.00________103.54 _________%
L25X_______________0_____________0________________1_____________0__ __________LOGIC
L86CSTALL_________0_____________0________________1_____________0___ _________LOGIC
_L0059_SP__________0_____________0________________1_____________0__ __________?

&#12615;IOMA DIAGNOSTICS
<S>
co_firmware_name =
co_firmware_major_rev =00
co_firmware_manor_rev =D8
co_prom_0_chksum =D800
co_prom_1_chksum =D800
co_restarts =2CC9
co_status_196 =D842
co_status_320 =D800
co_host_time_tick =05
co_io_time_tick =00
co_io_state =00A2
co_int_196 =66
co_int_320 =09

<R>,<T>
co_firmware_name =IOMA
co_firmware_major_rev =01
co_firmware_manor_rev =05
co_prom_0_chksum =0000
co_prom_1_chksum =0000
co_restarts =0000
co_status_196 =0000
co_status_320 =0000
co_host_time_tick =19
co_io_time_tick =19
co_io_state =00A7
co_int_196 =00
co_int_320 =00

2. Second Alarms in <T>core
(The second Alarms persisting 12sec and then disappear)

1) September 1
&#12615;HMI Alarms

Time__________Date______________Alarm ID________Message

10:26:10:15___9/1/2013_________D4012___________Voter mismatch, <T> SFL1
10:26:10:15___9/1/2013_________D4002___________Voter mismatch, <T> FP_MSP
10:26:10:15___9/1/2013_________D4001___________Voter mismatch, <T> SSDIFF2
10:26:10:15___9/1/2013_________D3998___________Voter mismatch, <T> DV_ERR
10:26:10:15___9/1/2013_________D3996___________Voter mismatch, <T> DV
10:26:10:15___9/1/2013_________D2875___________Voter mismatch, <T> _L0059_SP
10:26:10:15___9/1/2013_________D2873___________Voter mismatch, <T> L86CSTALL
10:26:10:00___9/1/2013_________D1359___________TCQA Relays dropped on loss of output
10:26:10:00___9/1/2013_________D963____________TCD1 Relays dropped due to IONET failure
10:26:10:00___9/1/2013_________D755____________TCD2 Relays dropped due to IONET failure

2) September 19

&#12615;HMI Alarms

Time__________Date______________Alarm ID________Message

10:26:10:15___9/19/2013________D4012___________Voter mismatch, <T> SFL1
10:26:10:15___9/19/2013________D4002___________Voter mismatch, <T> FP_MSP
10:26:10:15___9/19/2013________D4001___________Voter mismatch, <T> SSDIFF2
10:26:10:15___9/19/2013________D3998___________Voter mismatch, <T> DV_ERR
10:26:10:15___9/19/2013________D3996___________Voter mismatch, <T> DV
10:26:10:15___9/19/2013________D2875___________Voter mismatch, <T> _L0059_SP
10:26:10:15___9/19/2013________D2873___________Voter mismatch, <T> L86CSTALL

&#12615;Prevote Data Display
9-SEP-2013 17:30:33

Pointname_________Voted__________R________________S_____________T__ _________Unit

DV________________96.08_________96.47_____________0.00_________95.3 0_________%
DV_ERR____________0.00__________0.00___________-40.00__________0.00 _________%
SSDIFF2____________0.0___________0.0___________-160.0___________0.0 __________deg
SFDIFF2____________0.0___________0.0_____________-2.50__________0.0 __________deg
FP_MSP__________103.58________103.94___________-40.00________103.54 _________%
L25X_______________0_____________0________________1_____________0__ __________LOGIC
L86CSTALL_________0_____________0________________1_____________0___ _________LOGIC
_L0059_SP__________0_____________0________________1_____________0__ __________?
SFL1_______________0_____________0_______________64_____________0__ __________Hz



&#12615;IOMA DIAGNOSTICS
<S>(Only <S>core co_restarts count is Increasing)
co_firmware_name =
co_firmware_major_rev =00
co_firmware_manor_rev =D8
co_prom_0_chksum =D800
co_prom_1_chksum =D800
co_restarts =7824
co_status_196 =D842
co_status_320 =D800
co_host_time_tick =1F
co_io_time_tick =00
co_io_state =00A8
co_int_196 =66
co_int_320 =09

<R>,<T>
co_firmware_name =IOMA
co_firmware_major_rev =01
co_firmware_manor_rev =05
co_prom_0_chksum =0000
co_prom_1_chksum =0000
co_restarts =0000
co_status_196 =0000
co_status_320 =0000
co_host_time_tick =19
co_io_time_tick =19
co_io_state =00A7
co_int_196 =00
co_int_320 =00 </pre>
Thus, 10month ago I replaced all of <R>,<S>(TCQA,TCQB,TCEA,TCDA,TCPA) cores cards and DCC, LCC cards in <C>core.

And there wasn't any power down when the alarms persisting.
Therefore I can see A7 all of cores <R>,<S>,<T> DCC I/O status in mark-V cabinet.

Also, I'd like to show you signal trend but there is no option to upload image files. so if you give me your e-mail (My e-mail is [email protected]).

I'll send you the signal image file.
 
B
> Thanks for the response!! But I can see A7 all of cores <R>,<S>,<T> DCC I/O status. (Not at A2.) So I guess. It's
> not the problem about the TCEA. Nevertheless, you gave me great opinions.

I recently had a TCEA card fail but show A7. I used the diagnostics page to view all the power supply and IO voltages and found that on the bad card the power supply voltages were way off. All reading a positive voltage when there were positive and negatives listed i.e. +15, -15, +125, -125. Since the other cards in that core responded with the right readings, I assumed it was just in the TCEA card. That was replaced and everything was fine. The repair company I used had nice presentation on how the power supplies in the Mark5s are all aging and developing noise. If we were not going to do a Mark5 - 6e upgrade, we would be replacing all the power supplies with fresh rebuilds (new capacitors.) Good luck!
 
Top