Woodward easYgen-3200XT

Generator paralleling controller

easYgen-3200XT-P1 provides generator management, synchronisation and load sharing with a local display. Woodward publishes several selectable data protocols for the XT family. Matching the selected protocol to its table is more useful than copying a register list from a different easYgen generation.

easYgen-3200XT controller
  • Modbus RTU
  • Modbus TCP

Generator paralleling controller

Compatibility

Documented Modbus RTU and TCP interface

RS-485 Modbus RTU and Ethernet Modbus TCP on easYgen-3200XT-P1

This guide follows manual 37574D for 3100XT/3200XT-P1 and the OEM XT protocol-selection article. The display-less 3100XT is shown beside the 3200XT in the manual; it is not a different view of the same housing.

Connect it with

Route into Edge

When the documented monitoring interface is fitted and configured

  • Modbus
  • Edge
  • Platforms
Generator paralleling controller
Interface
Gateway
Edge
Output
easYgen-3200XTeasYgen-3200XT
Isolated serial interfaceApproved RS-485-to-host adapter
ZGW-20 GatewayHosts Edge locally
EpiSensor EdgeEdge Gateway
Customer platformMQTT · API · files
Modbus RTU · RS-485
Isolated serial
Runs locally
Optional onward data
Save the ToolKit settings and note the selected data protocol, such as 5003, 5010 or 5016. For TCP, record parameter 7485 (Modbus/TCP slave ID) and the configured endpoint. Use the protocol-specific value types and scaling for the first read. The customer-platform output is optional; Edge remains the local system of record.

When the documented monitoring interface is fitted and configured

  • Modbus
  • Edge
  • Platforms
Generator paralleling controller
Interface
Gateway
Edge
Output
easYgen-3200XTeasYgen-3200XT
Protected EthernetSegmented LAN
ZGW-20 GatewayHosts Edge locally
EpiSensor EdgeEdge Gateway
Customer platformMQTT · API · files
Modbus TCP
Protected Ethernet
Runs locally
Optional onward data
Save the ToolKit settings and note the selected data protocol, such as 5003, 5010 or 5016. For TCP, record parameter 7485 (Modbus/TCP slave ID) and the configured endpoint. Use the protocol-specific value types and scaling for the first read. The customer-platform output is optional; Edge remains the local system of record.

Models

Download
ModelsInterfaceRoute into Edge
easYgen-3200XTRS-485 Modbus RTU and Ethernet Modbus TCP on easYgen-3200XT-P1Save the ToolKit settings and note the selected data protocol, such as 5003, 5010 or 5016. For TCP, record parameter 7485 (Modbus/TCP slave ID) and the configured endpoint. Use the protocol-specific value types and scaling for the first read.

Specifications

This guide follows manual 37574D for 3100XT/3200XT-P1 and the OEM XT protocol-selection article. The display-less 3100XT is shown beside the 3200XT in the manual; it is not a different view of the same housing.12

Plant role
Generator paralleling controller2
Monitoring and configuration
RS-485 Modbus RTU and Ethernet Modbus TCP on easYgen-3200XT-P12
Model distinction
This guide follows manual 37574D for 3100XT/3200XT-P1 and the OEM XT protocol-selection article. The display-less 3100XT is shown beside the 3200XT in the manual; it is not a different view of the same housing.12

Interface

Documented measurements and integration boundaries for easYgen-3200XT.

  • Generator electrical measurements defined in the selected data protocol
  • Engine measurements and configurable analogue values
  • Operating mode, alarm and breaker indication data

Assessment

RS-485 Modbus RTU and Ethernet Modbus TCP on easYgen-3200XT-P1

InteroperabilitySupported with conditions
RS-485 Modbus RTU and Ethernet Modbus TCP on easYgen-3200XT-P112
AccuracySupported with conditions
The documentation identifies electrical and operating measurements for this plant role. CT configuration and measurement location determine how those values are used.12
SecurityNot yet assessed
The cited documentation does not establish an authenticated, encrypted Edge monitoring connection.
ReliabilityNot yet assessed
The controller application distinguishes operating conditions and alarms. Retain communication availability alongside the plant readings.
RuggednessNot yet assessed
Installation and enclosure requirements depend on the panel and the exact hardware variant.
ScalabilityNot yet assessed
Assign one device identity per controller and keep generator, mains and busbar measurements separate.
LifecycleSupported with conditions
Retain the exact model documentation and configuration when replacing a controller or communication module.12

Setup

  1. Save the ToolKit settings and note the selected data protocol, such as 5003, 5010 or 5016.

    For TCP, record parameter 7485 (Modbus/TCP slave ID) and the configured endpoint. Use the protocol-specific value types and scaling for the first read.

  2. Record CT ratios and the physical measurement location.

    Compare the first electrical values with the controller display before using them in totals or trends.

  3. Keep missing responses distinct from a stopped generator.

    Store communication availability beside running state so a disconnected cable does not look like healthy standby.

  4. Build a read-only point list for monitoring.

    Remote start, synchronisation and breaker operation require a separate control design with the existing panel interlocks and feedback.