Search results

Agreed. My last post was a hypothetical common problem causing the mismatch. In the case of L4, that is the output of other logic. Why is <T> not in agreement with <S> and <R> on L4? Below example (not necessarily this unit in question) L4 requires L4S before it will latch itself in; So why...

Thank you for confirming the Vote ID. That was a long shot at being your problem, but it's easy to confirm. Now you need to find the commonality of you voter mismatches in <T>. For example; Are they all digitals? Do they all go back to IO that lands on the DTBB? The Mk V is called triple...

Are you certain the DCC/LCC in <T> in fact has its VOTER ID set to <T> and not something else? It is possible to replace a DCC and not properly set the VOTER ID. The core might go to A7 as that is the I/O status, not the VOTER ID. You can set the voter id with the LCC pinpad. I've seen a site...

BN3500 as in Bently Nevada 3500? The 3500 is modular. One of the cards you can install is the 3500/92 communications gateway. There are various (i think 4) options for the back card. Depending on the back card chosen you will have various physical formats (1 DB9, 2 DB9's, etc). Once installed...

Also see attached. Helpful in understanding what is going on at any A status.

As WTF stated, there is a grease that protects the pins of ribbon cable from oxidizing and corroding, its called NyoGel 760G. The cable that connects DCC to LCC to TCQA is the 3PL. Why did TCQA go to A5? Maybe 3PL isn't seated correctly or is corroded. As far as 75 voter mismatches, the vote...

You might be getting confused by the format of the serial ports on the various models. The 200-PEU has two DB9 connectors on the front marked COM1 and COM2. The FGR2 series have what appear to be four ethernet ports on the front, however the format for all 4 ports is RJ45 (what most people think...

I scrolled right past <I>. So wouldn't the answer be 1. storage update to burn RAM to EEPROM 2 EEPROM UP T1 R CONST(or any known good core if TMR) 3. grab coffee. The Mk V runs in real time out of RAM, so what's in RAM had better be correct.

There is a way to determine what is in EEPROM. Hit Storage Update in the constants adjust tool, now what's in RAM is burned to EEPROM. After that you can use the UP option in the EEPROM tool to pull the same constants up into the AP1 file, EEPROM UP T1 R CONST. After that you have to reconcile...