Reading DSE8610 Modbus Registers in WinCC Flexible 2008 SP3

Problem Overview

Engineers integrating a Deep Sea Electronics DSE8610 generator controller with a Siemens WinCC Flexible 2008 SP3 runtime commonly hit a wall: the DSE8610 is not present in the WinCC Flexible PLC device list. The HMI software ships with a curated catalog of Siemens SIMATIC PLCs and a handful of third-party drivers, but DSE controllers are not included as native entries. This means that the standard "Add PLC" wizard cannot auto-create the correct communication channel, and the engineer must configure the Modbus TCP link manually.

The DSE8610 supports both Modbus RTU over RS-485 and Modbus TCP over Ethernet. The Modbus TCP path is the practical choice for remote panel HMI integration because it allows the WinCC Flexible runtime on a PC or Panel to poll the controller's holding registers directly over the plant LAN. Once the channel is built manually, any register documented in the DSE Modbus register map (generator voltage, current, frequency, engine RPM, oil pressure, coolant temperature, breaker state, alarm flags, and so on) can be exposed as an HMI tag.

Prerequisites

1. WinCC Flexible 2008 SP3 (32-bit or 64-bit) installed and licensed, with the ES (Engineering System) and RT (Runtime) components.
2. WinCC Flexible 2008 SP3 update package installed (HF releases above SP3 are recommended for stability on x64 hosts).
3. DSE8610 controller with Ethernet port enabled and a configured static IP address on the same subnet as the HMI.
4. TCP port 502 reachable (default Modbus TCP port on DSE86xx series).
5. Current DSE8610 Modbus register map PDF supplied by DSE or the generator OEM. Do not rely on a register address posted on a forum - the OEM-supplied map is the only authoritative source, and addresses can change between firmware revisions of the DSE8610 (firmware revisions 5.x, 6.x, and 7.x have shipped with different mappings).
6. PC with Ethernet adapter on the same subnet for the engineering PC and the target runtime.

Modbus TCP Communication Fundamentals

Modbus TCP is an open, application-layer protocol that wraps the classic Modbus PDU inside a TCP segment. The connection is established by a Modbus client (the HMI / WinCC Flexible runtime) to a Modbus server (the DSE8610) on TCP port 502. Once the socket is open, the client issues a request and the server responds with the same function code and a data payload.

For the DSE8610 generator controller the relevant Modbus function codes are:

Each Modbus TCP request is framed as a 7-byte MBAP header followed by the standard Modbus PDU. The MBAP header carries the Transaction ID, the Protocol Identifier (0x0000 for Modbus), the Length field, and the Unit Identifier. The DSE8610 uses the Unit Identifier as its Modbus slave address (default 1). Refer to the Siemens TIA Portal Modbus TCP and Modbus RTU overview for the client/server model that WinCC Flexible follows.

WinCC Flexible Communication Driver Selection

WinCC Flexible 2008 SP3 ships with a generic Modicon Modbus TCP driver under the "Modicon" family. This driver is not Modicon-specific at the wire level - it implements the standard Modbus TCP client and can be pointed at any Modbus TCP server, including the DSE8610. Two driver entries are typically present:

• Modicon Modbus TCP/IP - direct Ethernet, point-to-point or multipoint via a Modbus TCP gateway.
• Modicon Modbus (RTU over serial) - used when the HMI is talking RS-485 to a DSE8610 serial port.

For the DSE8610 over Ethernet, select Modicon Modbus TCP/IP. Even though the device list inside this driver is populated with Schneider Electric / Modicon PLCs, the driver itself accepts any Modbus TCP server; the device list is purely cosmetic. The polling engine inside WinCC Flexible RT uses the function code, starting address, and length you bind to each tag - it never validates the remote vendor.

Step-by-Step Configuration in WinCC Flexible ES

Step 1 - Create a new Connection

1. Open the WinCC Flexible project in the Engineering System.
2. In the project tree, expand Communication > Connections.
3. Double-click Connections to open the connection editor.
4. Click the empty row to create a new connection, then set:
     Communication driver: Modicon Modbus TCP/IP
     Station: descriptive name, e.g. DSE8610_Genset_1
5. Leave the HMI device as the local endpoint (it is implied by the driver selection).

Step 2 - Configure the Slave (DSE8610) Endpoint

1. In the connection parameters table, set the Partner (PLC) IP address to the static address configured on the DSE8610 (for example, 192.168.1.50).
2. Set the Partner port to 502 (DSE default Modbus TCP port).
3. Set the Modbus Station Address to 1 (DSE default Modbus unit ID; verify against the controller's configured Modbus ID in DSE Configuration Suite).
4. Set the Cycle time for the connection. For generator telemetry a cycle of 1000 ms is a good starting point. Faster polling (e.g. 250 ms) can saturate the DSE8610 Modbus buffer on a busy multi-master segment.

Step 3 - Define Tags Bound to DSE Holding and Input Registers

1. Open Communication > Tags.
2. Create a new tag, for example Gen_L1L2_Voltage.
3. Set the Connection to the new Modbus TCP connection from Step 1.
4. Set the Address format. For the Modicon Modbus TCP driver in WinCC Flexible, the addressing syntax is:
   DB<area>.<register-type><address> or directly a numeric MW-style word address mapped to a Modbus register, depending on the driver build. The driver build shipped with SP3 accepts a numeric Modbus register directly in the address field; check the driver help under Addressing.
5. Map the tag to the correct Modbus function code by setting the data type and the access mode (read / write). For a DSE input measurement (e.g. generator line voltage) use function code 04 (Read Input Registers); for a DSE setpoint or configuration value use function code 03 (Read Holding Registers).

Step 4 - Address Mapping for Common DSE8610 Registers

The exact register map varies by DSE8610 firmware. The following table shows a representative example. Always confirm with the OEM-supplied map for your specific firmware revision.

Step 5 - Configure the Connection on the HMI Device

1. Open Device Settings on the HMI panel (or PC runtime target).
2. Set the HMI's own IP address, subnet mask, and default gateway so it can reach the DSE8610 subnet.
3. Confirm the panel's transfer and runtime ports are not conflicting with the Modbus TCP port 502.
4. Compile the project and transfer to the runtime target.

Compiling and Verifying the Runtime

1. Select Project > Compiler > All in WinCC Flexible ES. The compile must complete with zero errors and zero warnings about the Modbus connection.
2. Start Runtime on the target or perform a transfer and then start runtime locally on the engineering PC.
3. Open an I/O Field or Bar element on a test screen bound to one of the new tags, for example Gen_L1L2_Voltage.
4. Observe the value. If it tracks the value shown on the DSE8610 front panel within the configured scaling, the channel is live.
5. Watch the connection status indicator in the runtime. A green / "connected" icon confirms the MBAP handshake succeeded.

Verification Checklist

• ping <DSE8610_IP> from the engineering PC returns replies with TTL near 64 or 128.
• WinCC Flexible Runtime shows connection OK for the DSE8610 partner.
• A 16-bit input tag returns a plausible unsigned integer; the value changes when the generator state changes.
• A 32-bit measurement (e.g. total kW) returns a plausible value, with the high and low words correctly ordered. If the reading is wildly wrong, swap the word order in the tag definition - some Modbus masters expect big-endian (high-word-first) while the DSE8610 may publish little-endian depending on firmware.
• Alarm flags from the DSE8610 map to discrete inputs and surface correctly on a WinCC alarm view.

Troubleshooting Matrix

Performance and Polling Strategy

The DSE8610 has a single Modbus TCP server process. Polling the full register map at 100 ms will starve the controller. Group related tags into a contiguous register block and let the WinCC Flexible driver request the block in one PDU. For generator telemetry:

• Fast (250 - 500 ms): Generator voltage, current, frequency, power, breaker state. These are the values an operator watches in real time.
• Medium (1000 ms): Engine RPM, oil pressure, coolant temperature, fuel level.
• Slow (5 - 10 s): Energy counters, hours-run counters, event log reads, configuration setpoints that rarely change.

Split the tags across multiple WinCC Flexible connections with different cycle times if your driver build supports it, or use one connection and adjust the per-tag acquisition cycle where the runtime allows.

Safety and Operational Notes

When the HMI runtime crashes or the network drops, the DSE8610 will continue operating on its internal logic; remote commands queued by the HMI do not survive a runtime restart. For critical control paths, always keep the DSE8610's local pushbuttons as the primary control surface and use the HMI as a supervisory view.

Alternate Path - Modbus RTU over RS-485

If the DSE8610 variant on site has only an RS-485 port and no Ethernet, the same WinCC Flexible Modicon Modbus (RTU) driver is used. The wiring, addressing, and tag setup are identical, except:

• Use a serial cable from the HMI's COM port to the DSE8610 RS-485 A / B terminals.
• Set baud rate, parity, and stop bits to match the DSE configuration (typical: 19200, 8, N, 1).
• Set the Modbus station address to the unit ID of the DSE8610.
• Add a 120 Ω termination resistor at each end of the RS-485 trunk.

FAQ