Data centers liquid cooling systems often require multiple components to handle control, visualization, and communication. This typically includes a PLC, HMI, I/O modules, and additional gateways for protocol conversion and system integration.
Unitronics introduces a unified PLC+HMI solution designed to simplify this architecture. The platform combines control platform, HMI, I/O handling, and communications into a single device. This reduces system complexity, minimizes control equipment footprint, and removes the need for external protocol converters in many applications.
System architecture advantages:
- Single device for PLC, HMI, I/O, and data center related communication protocols
- Elimination of external gateways
- Reduced panel space and ease wiring
- Simplified system design and commissioning
Communication and integration:
- Native support for: Redfish, BACnet, Modbus TCP/RTU, OPC UA, REST API, SNMP, EtherNet/IP
- Enables direct integration with DCIM, BMS, SCADA, and cloud platforms
- Handles both field-level and system-level communication
Cooling application support:
- Suitable for RDHx, chillers, pumps, CDUs, CRAH units, etc.
- Real-time control, alarm management and diagnostics
- Centralized monitoring and local visualization via built-in HMI
Data center compatibility:
The platform is also designed to meet colocations and hyperscale requirements, where direct communication with IT and management systems is increasingly required.
- Native Redfish server for DCIM integration
- IPv6 support for modern network environments
- No middleware required between control and management layers
Deployment considerations:
The unified approach supports consistent system design across projects, which can reduce engineering effort and simplify replication in multi-site deployments.
This makes the platform suitable for OEMs, system integrators, and operators working on both industrial cooling systems and data center infrastructure.
A practical approach to system design
For engineers working on data center cooling systems, the biggest bottlenecks are usually not the control logic — but the system complexity and integration requirements.
Using a single control platform that already supports required protocols and system behavior changes that.
- Fewer components to configure
- Fewer points of failure
- Less time spent on communication setup
- Easier troubleshooting when something goes wrong
It’s not about adding more features, it’s about removing unnecessary layers.
