Multi-HMI SCADA Monitoring with Siemens PLC in Baggage Handling
Project Overview and Core Challenges
A medium-sized airport with an annual passenger throughput exceeding 8 million required an upgrade to its baggage handling automation system. The sorting area spans 2,000 square meters and includes one main sorting line, 63 sorting chutes, 20 light grid sensors, and multiple sorting robots. The core controller is a Siemens 300 series PLC, which collects data from light grid sensors and equipment parameters such as sorting speed and chute status. It executes commands for start/stop and path control to ensure accurate baggage sorting and minimize delays or lost luggage.
The project’s primary requirement was to establish stable bidirectional communication between the PLC and three Siemens HMIs (touch panels) plus two upper computers (SCADA hosts). The three HMIs are deployed at both ends and the middle control point of the sorting line, allowing field operators to issue sorting commands and view equipment status and fault information for their respective zones. The two upper computers are located in the maintenance control room and the dispatch center, enabling real-time monitoring of the entire sorting line, data statistics, and remote fault diagnosis. This setup aims for visualized, multi-terminal collaborative management to reduce manual dependency and baggage delay rates.
Before implementation, two core pain points existed. First, protocol incompatibility caused communication failure: the Siemens 300 PLC uses the proprietary MPI protocol (physical layer RS-485, default baud rate 187.5 kbit/s), while the HMIs used Modbus and the upper computers used TCP/IP. These three protocols could not interoperate, creating isolated communication islands. Second, multi-terminal collaboration was impossible; direct connections led to signal conflicts and data corruption when multiple terminals attempted simultaneous communication. The only recourse was manual inspection every 15 minutes, increasing workload and resulting in a baggage delay rate above 3%. Additionally, complex wiring was susceptible to vibration interference, further exacerbating communication issues.
Device Selection and Implementation
To address multi-terminal communication, protocol incompatibility, and the airport environment, a wireless Ethernet module was selected after extensive evaluation. This module is specifically designed for Siemens 300 series PLCs and integrates core functions of serial-to-Ethernet conversion, Ethernet bridging, and protocol conversion. It supports up to 32 simultaneous terminal connections, making it ideal for multi-HMI and SCADA setups without replacing existing equipment.
Key selection criteria included: strong compatibility with MPI, Modbus, and TCP/IP protocols without modifying original configurations; wireless communication with a range of up to 150 meters in open areas, eliminating extensive wiring and resisting electromagnetic interference and vibration; comprehensive functionality as an Ethernet converter and bridge for seamless protocol translation and multi-terminal data synchronization; and easy deployment with a compact form factor that fits inside the PLC control cabinet, configurable via a web server without occupying the PLC programming port. Deployment was completed in 1.5 working days.
Implementation involved three steps: first, mounting the module in the PLC cabinet and connecting it to the MPI port with proper anti-vibration measures; second, configuring parameters via the web server for PLC protocol, terminal addresses, and wireless settings; third, conducting online tests with all three HMIs and two upper computers simultaneously to verify communication stability, real-time command execution, and data acquisition, ensuring no signal conflicts for 24/7 operation.
Gateway Functionality
The wireless Ethernet module serves as a core communication gateway, integrating serial-to-Ethernet, Ethernet conversion, and bridging capabilities tailored for multi-terminal environments:
- Serial-to-Ethernet Conversion: Converts the PLC’s MPI serial data (sensor readings, equipment parameters) into Ethernet packets, enabling bidirectional data transfer with HMIs and SCADA hosts. This breaks the barrier between serial and Ethernet devices, allowing legacy PLCs to achieve multi-terminal Ethernet communication without upgrades.
- Ethernet Conversion and Bridging: Acts as an Ethernet converter to seamlessly translate between MPI, Modbus, and TCP/IP protocols, making PLC data readable by all terminals. As an Ethernet bridge, it establishes a communication link between the PLC and multiple terminals, supporting up to 32 concurrent connections and ensuring parallel communication without interference, suitable for zoned control and multi-role collaboration.
- Wireless Communication: Provides stable wireless transmission, adapting to the dispersed layout of multiple terminals without cabling. It resists interference and vibration, preventing communication interruptions and supporting real-time data access and command issuance for 24/7 operations.
- Auxiliary Functions: Includes real-time device status monitoring for troubleshooting multi-terminal communication faults, online firmware upgrades for future expansion, and support for Modbus TCP master/slave functionality to enhance compatibility and reduce maintenance costs.
System Topology
The system architecture consists of the Siemens 300 PLC connected via its MPI port to the wireless Ethernet module. The module then communicates wirelessly with three HMIs (using Modbus TCP) and two SCADA PCs (using TCP/IP). All devices are on the same network segment, with the module acting as a protocol bridge. The HMIs are placed at strategic points along the conveyor line, while the SCADA stations are in the control room and dispatch center. This topology allows real-time data flow: sensor data from the PLC is converted and broadcast to all terminals, and commands from any HMI or SCADA are routed back to the PLC without collision, thanks to the module’s internal arbitration.
Before and After Comparison
| Aspect | Before Upgrade | After Upgrade |
|---|---|---|
| Communication Method | Manual inspection every 15 min; no real-time data | Real-time wireless communication; all terminals synchronized |
| Baggage Delay Rate | >3% | <0.5% |
| Fault Response Time | 15-30 minutes (manual detection) | <1 minute (automatic alarm) |
| Wiring Complexity | Extensive RS-485 cabling, prone to vibration damage | Wireless, no additional cables |
| Multi-terminal Support | None; only one terminal could connect at a time | 32 terminals simultaneously, no conflicts |
Future Trends in Gateway Technology
Driven by smart airport initiatives and multi-terminal communication needs, Ethernet gateways with serial-to-Ethernet and bridging functions are evolving in four directions:
- Multi-Protocol Compatibility: Supporting a wider range of industrial protocols (e.g., PROFINET, EtherNet/IP) for plug-and-play integration of diverse devices, enhancing multi-vendor collaboration.
- Wireless and High-Speed: Adopting 5G and Wi-Fi 6 for faster transmission, accommodating more terminals in large-scale airport deployments.
- Intelligence and Integration: Embedding edge computing for fault prediction and remote maintenance, consolidating functions into compact, all-in-one devices.
- Localization and Customization: Accelerating the shift to domestically produced hardware and software, offering tailored solutions for multi-terminal scenarios to support smart airport upgrades.
Conclusion
The airport baggage handling upgrade successfully resolved communication challenges between a Siemens 300 series PLC and multiple HMIs/SCADA systems using a wireless Ethernet gateway. By leveraging serial-to-Ethernet conversion, protocol bridging, and multi-terminal support, the project achieved real-time collaborative control, significantly reducing baggage delay rates and operational costs while improving efficiency and passenger experience. This case demonstrates the value of such gateways in modernizing legacy automation systems for smart airports.
