The Need for Multi-Vendor Turbine Control
Heavy-duty gas turbines often pair GE Mark VIe for overall turbine control with Woodward Micronet for governor and protection functions. These two systems must exchange speed, load, valve position, and trip status in real time.
First, Modbus TCP offers a simple way to bridge them. Second, both controllers support Ethernet-based Modbus. Therefore, integration does not require exotic protocol gateways. However, register mapping discipline is critical because each vendor uses different conventions.
Step 1: Set Up the Ethernet Network
Connect the GE Mark VIe UDH Ethernet switch to the Woodward Micronet Ethernet module. Use a dedicated control network VLAN. Assign static IP addresses to both controllers:
- Mark VIe controller: 192.168.10.10
- Woodward Micronet: 192.168.10.20
- Subnet mask: 255.255.255.0
- Gateway: 192.168.10.1 if external access is required
Moreover, disable unused protocols on the Micronet Ethernet port to reduce attack surface. Finally, verify ping response from the Mark VIe toolbox before configuring Modbus.
Step 2: Configure Modbus TCP Server on Micronet
Woodward Micronet controllers can act as Modbus TCP servers. Enable the server in the Woodward GAP application. Define the holding registers that expose turbine data.
Typical mapped registers include:
- 40001: Actual turbine speed in RPM
- 40002: Load reference in MW
- 40003: Governor valve demand in percent
- 40004: Protection trip status word
- 40005: Lubricating oil pressure in psi
- 40006: Vibration channel 1 in mils
However, scaling matters. If Micronet stores speed as a floating-point value, map it as two consecutive 16-bit registers. Use IEEE 754 format and verify endianness. Finally, set the Modbus unit ID to 1 unless multiple devices share an Ethernet gateway.
Step 3: Add a Modbus Client in Mark VIe
In the Mark VIe toolbox, add a Modbus TCP client block. Enter the Micronet IP address and port 502. Configure read function code 03 for holding registers. Map each register to a Mark VIe variable name.
Use a read interval of 100 ms for trip-critical signals and 500 ms for monitoring-only values. Moreover, add a communication fault bit. If the client loses connection for three consecutive cycles, set the fault flag and transfer to safe state logic.
Step 4: Build Alarms and Trends
Create Mark VIe alarms for the Micronet trip status word. Add operator messages describing the expected response. For trends, plot speed, load reference, and valve demand together to diagnose governor interaction.
Second, test emergency shutdown sequences. Trip the turbine in simulation mode and confirm both systems react within the design time. Finally, document the complete register map in the control system dossier.
Conclusion & Action Advice
Integrating Woodward Micronet with GE Mark VIe through Modbus TCP gives operators a single view of turbine health. Use a dedicated control network, map registers carefully with correct scaling, and add communication fault logic. Test trip sequences before startup and keep the register map updated.