Honeywell controllers vs. the Experion PKS DCS — what TOP Server covers
Honeywell makes both standalone process controllers and full Distributed Control Systems. The TOP Server Honeywell Suite connects to the standalone instrument side — the HC900 Hybrid Controller and the UDC series loop controllers. Honeywell's Experion PKS DCS, which is the company's flagship large-scale process control platform, uses a completely different architecture and connectivity path not covered by TOP Server.
This distinction matters because both types of Honeywell hardware appear in the same facilities. An HC900 managing a batch heating skid or a UDC 3500 controlling a single temperature loop may sit alongside — or feed data into — an Experion PKS system managing the broader plant. TOP Server handles the instrument side of that picture.
If your Honeywell hardware is part of an Experion PKS, TDC 3000, or TPS system, the OPC interface is provided by Honeywell's own Experion OPC server built into the DCS platform — not TOP Server. The HC900 and UDC families are independently deployed controllers that communicate over standard network interfaces, which is why a third-party OPC server like TOP Server can connect to them directly.
The device families TOP Server connects to
The Honeywell Suite covers two distinct controller families. Each has its own communication protocol variant, its own Modbus register map, and its own driver in TOP Server.
Understanding Honeywell's Modbus variants
The core of understanding Honeywell connectivity is understanding that "Modbus" in this context does not mean standard Modbus TCP or Modbus RTU. Both the HC900 and UDC families use Honeywell-specific adaptations of the Modbus protocol — they share the Modbus framing, function codes, and transport, but their register maps and data structures are organized according to Honeywell's own specifications for each product line. A generic Modbus driver can reach these devices but will not correctly interpret the data without knowledge of those register structures.
Why Honeywell-specific drivers matter
The difference becomes concrete when you look at how control loop parameters are organized. In a standard Modbus device, a PID loop's setpoint might live at an arbitrary register address chosen by whoever programmed the device. In the HC900 and UDC controllers, Honeywell has defined a structured register map where every loop parameter — process value, setpoint, output, alarm status, auto/manual mode — has a specific, documented Modbus address. The HC900 and UDC drivers know this map natively, which enables features that a generic Modbus driver cannot provide.
Address range and data types
Both the HC900 and UDC drivers support the full Modbus address range — 0 to 65,535 decimal (0x0000 to 0xFFFF hex) — well beyond the 9,999-register limit that some Modbus tools impose. Both decimal and hexadecimal addressing are supported at the driver level, which is important because Honeywell documentation for these controllers frequently expresses register addresses in hex.
| Modbus Function Code | Register Type | Accessible From | Description |
|---|---|---|---|
| FC 01 | Coil (0x) | HC900 & UDC Serial | Discrete output bits — coil status read and write |
| FC 02 | Discrete Input (1x) | HC900 & UDC Serial | Discrete input bits — read only |
| FC 03 | Holding Register (4x) | HC900, UDC Ethernet & Serial | General-purpose read/write registers — primary area for process values, setpoints, control parameters |
| FC 04 | Input Register (3x) | HC900 & UDC Serial | Read-only input registers — analog and digital inputs |
| FC 05 | Write Single Coil | UDC Serial | Write a single discrete output bit |
| FC 06 | Write Single Register | UDC Serial | Write a single holding register |
| FC 16 | Write Multiple Registers | UDC Serial | Write a block of holding registers in one request |
| FC 20 | Read File Record | UDC Serial | Access extended memory including Loop Configuration Memory |
| FC 21 | Write File Record | UDC Serial | Write to extended memory including Loop Configuration Memory |
Word order swapping for 32-bit values: Both HC900 and UDC controllers store 32-bit floating point and long integer values across two consecutive 16-bit Modbus registers. Which register holds the high word and which holds the low word — the "word order" — can vary by controller model and configuration. The HC900 Ethernet and UDC drivers both include a configurable First Word Lo/Hi option that allows the word order to be matched to the specific controller's configuration. Incorrect word order is the most common cause of garbage float values when connecting to these controllers — if process values look nonsensical, check the word order setting first.
Protocol and driver comparison
| Driver | Device | Protocol | Transport | Max devices | Auto tag gen |
|---|---|---|---|---|---|
| HC900 Ethernet | HC900 Hybrid Controller | Honeywell HC900 Modbus TCP | TCP/IP Ethernet | 8,192 / channel | Yes — CSV import or manual config |
| UDC Ethernet | UDC 2500, 3200, 3500 | Honeywell UDC Modbus TCP | TCP/IP Ethernet | 256 / channel | Yes |
| UDC Serial | UDC 3000, UDC 3300 | Honeywell UDC Modbus RTU | RS-232 / RS-422 / RS-485 | 247 / channel | Manual tag entry |
How TOP Server connects to Honeywell controllers
The TOP Server Honeywell Suite bundles all three drivers in a single license. Here is a detailed breakdown of each driver, what it does, and the key configuration points.
Ethernet Encapsulation for UDC Serial: The UDC Serial driver supports Ethernet Encapsulation, allowing a serial-to-Ethernet converter (Moxa NPort, Digi, or equivalent) to bridge the Modbus RTU serial protocol over TCP/IP. TOP Server connects to the converter's IP address and port; the converter handles the physical RS-232/422/485 communication to the UDC controllers. This is the recommended approach for modernizing serial UDC installations — no long cable runs, the TOP Server machine can sit anywhere on the network.
Frequently asked questions
Ready to connect your Honeywell HC900 or UDC controllers?
TOP Server's Honeywell Suite covers every HC900 and UDC model — with Honeywell-specific Modbus drivers that make tag generation and loop parameter access far simpler than generic Modbus. Try it free or talk to an engineer.