We have GE FRAME 9E TURBINE with MARK VIE controller , problem is communication lost with exciter ex2100 that leads to fail to transfer between M1 &M2 and no responding for any command to ex2100 from cimplicity HMI
hent: Ip ping is ok for M1 &M2
Try with going online from ToolboxST and see if they are in controlling state?
If not, its better to get help from OEM, instead of creating further damage.
Try with going online from ToolboxST and see if they are in controlling state?
If not, its better to get help from OEM, instead of creating further damage.
Since we are talking about exciter issue, look into the exciter's controller.
Technically the same controller hardware is used for both Turbine controls & Exciter controls.
Some models carry additional expander carrier board for Exciter.
Since we are talking about exciter issue, look into the exciter's controller.
Technically the same controller hardware is used for both Turbine controls & Exciter controls.
Some models carry additional expander carrier board for Exciter.
It would help to know what communication protocol your system is using between the Mark VIe and the EX2100. From what you’ve described, it sounds like the Mark VIe was upgraded, but the EX2100 was not, and I’ve seen communication issues arise when newer controllers interface with older excitation systems.
A few things to check:
When communication is lost, what does the EX2100 itself display? It should generate fault codes or status messages that point toward the cause.
In ToolboxST, what does the Exciter status show at the moment communication drops? Any alarms, loss‑of‑link indicators, or invalid data flags would be useful.
Even though IP ping works for M1 and M2, that only confirms network reachability—not that the application‑level communication is healthy.
We’ll need more information about the network topology, protocol type, and any recent configuration changes.
If you can provide the EX2100 fault list and the ToolboxST status indications, we can narrow this down quickly.
It would help to know what communication protocol your system is using between the Mark VIe and the EX2100. From what you’ve described, it sounds like the Mark VIe was upgraded, but the EX2100 was not, and I’ve seen communication issues arise when newer controllers interface with older excitation systems.
A few things to check:
When communication is lost, what does the EX2100 itself display? It should generate fault codes or status messages that point toward the cause.
In ToolboxST, what does the Exciter status show at the moment communication drops? Any alarms, loss‑of‑link indicators, or invalid data flags would be useful.
Even though IP ping works for M1 and M2, that only confirms network reachability—not that the application‑level communication is healthy.
We’ll need more information about the network topology, protocol type, and any recent configuration changes.
If you can provide the EX2100 fault list and the ToolboxST status indications, we can narrow this down quickly.
The protocol communication between MARK VIe and Ex2100 called EGD (ETHERNET GLOBAL DATA) , I don't think that we've upgraded MARK VIe,but may be someone changed some configurations.
The exciter alarm list itself is clear,and the exciter is ready to start in cimplicity HMI, but there is one alarm in MARK VIe "communication lost between MARK VIe and Exciter"
The specific issue is the measurements of Exciter are shown in MARK VIe,but there are no manual commands and Auto adjusting from MARK VIe to exciter
In brief, what are called "external signals" in the exciter toolbox like "voltage raise and lower,transfer between M1, & M2 , fault reset" don't reach to exciter.
Thanks for your interest
Facebook
Google
GitHub
Linkedin
