This section covers the various methods used to connect EasyBuilder Pro HMIs to PLCs and other control devices. These connections form the foundation of how data is exchanged between the HMI and the control system, enabling real-time monitoring, control, and system integration.
EasyBuilder Pro supports both native drivers and standard communication protocols, allowing HMIs to interface with a wide range of PLCs, including Maple Systems controllers and third-party devices. Native drivers provide direct access to PLC memory using vendor-specific addressing, often simplifying configuration and improving clarity when working within a single ecosystem. Standard protocols such as Modbus and BACnet enable interoperability across different manufacturers, making them well-suited for mixed-device environments or retrofit applications.
Connection methods can vary depending on system requirements, including Ethernet-based communication for high-speed data exchange and serial communication for simpler or legacy systems. Each approach has its own considerations for setup, performance, and scalability, allowing developers to choose the most appropriate method for the application.
In addition to direct HMI-to-PLC communication, features such as pass-through connectivity allow external engineering tools to access a PLC through the HMI. This enables programming, diagnostics, and troubleshooting without requiring a direct connection to the controller, which is especially useful in remote or restricted environments.
These connection options also support a wide range of data types and structures, from simple bit-level signals to complex register-based data, ensuring that both basic control and advanced system interactions can be handled effectively.
BACnet
BACnet is a communication protocol used primarily in building automation systems that allows HMIs to monitor and control devices such as HVAC, lighting, and energy systems. In EasyBuilder Pro, BACnet enables integration with building controllers using a standardized object-based structure for accessing data.
CODESYS & Remote I/O
In Maple Systems architectures, CODESYS is used as the control runtime while Remote I/O modules (iR Series) handle distributed inputs and outputs in the field. This structure allows the system to scale easily by adding I/O modules as needed, while keeping control logic centralized and the HMI focused on visualization and user interaction.
Maple Micro/Modular
Maple Micro and Modular PLCs are controllers designed to work seamlessly with Maple Systems HMIs using native drivers. This integration allows the HMI to access PLC memory directly using native addressing, simplifying configuration and improving communication efficiency.
Maple Micro/Modular (via Modbus)
Maple Micro and Modular PLCs can also be connected to HMIs using Modbus protocols when native drivers are not used. In this case, the HMI communicates with the PLC through standard Modbus registers, enabling compatibility with broader systems while maintaining reliable data exchange.
MODBUS RTU (Serial)
Modbus RTU is a serial communication protocol that allows HMIs to connect to devices over RS-232 or RS-485 networks. It is commonly used in systems where multiple devices share a communication line and provides a reliable method for exchanging data in non-Ethernet environments.
MODBUS TCP (Ethernet)
Modbus TCP is an Ethernet-based version of the Modbus protocol that enables communication between HMIs and devices over a network using IP addresses. It is widely used for connecting controllers and systems across modern industrial networks.
Siemens Pass-Through
This feature enables engineers to upload, download, monitor, and troubleshoot Siemens PLC programs using the HMI’s existing communication link to the controller. Siemens Pass Through simplifies maintenance and commissioning by reducing extra cabling requirements and allowing remote or local PLC access through the HMI connection infrastructure.