PROFINET to PROFIBUS Gateway in Rubber Deflashing Lines
In the final stages of rubber product manufacturing, the deflashing machine—also known as a rubber trimming machine—plays a critical role. Using high-speed centrifugal impact, it efficiently removes flash from molded parts, serving as the last quality checkpoint for products like O-rings and precision gaskets. As factories embrace smart manufacturing, integrating such proven equipment into modern control systems often requires bridging two industrial communication eras: PROFINET and PROFIBUS.
Project Background and Challenges
A recent automation upgrade project for a rubber seal production line highlighted a common challenge. The existing high-performance deflashing machine relied on a PROFIBUS-DP slave interface, which had proven stable and reliable over years of operation. However, the new line controller was a Siemens S7-1200 PLC with PROFINET communication. The core issue was how to integrate the deflashing machine into the PROFINET network without altering its mature control logic.
Replacing the deflashing machine controller entirely would have been costly and risky. Adding a PROFIBUS communication module to the S7-1200 was possible but introduced configuration complexity and potential data consistency problems. For continuous flow operations involving start/stop and speed control, even minor communication delays could disrupt production timing.
The Role and Configuration of the Gateway
The solution lay in deploying a dedicated PROFINET-to-PROFIBUS protocol gateway. In this project, a high-performance gateway acted as both a translator and a bridge:
- Protocol Conversion: The gateway translates PROFINET telegrams from the S7-1200 into PROFIBUS-DP messages that the deflashing machine controller understands, and vice versa. Status signals and fault codes from the machine are sent back to the PLC in PROFINET format.
- Data Mapping: Using the gateway’s configuration software, engineers map PLC outputs like “start/stop” and “speed setpoint” to specific output data areas of the PROFIBUS slave. Feedback signals such as “running status,” “flash removal complete,” and “fault codes” are mapped from PROFIBUS input areas to PROFINET cyclic data exchange areas. No changes to the deflashing machine’s base program are required.
- Transparent Transmission: In Siemens TIA Portal, the gateway is configured as a standard PROFINET device with I/O address assignment. For the PLC programmer, controlling the deflashing machine becomes as straightforward as controlling a local PROFINET device.
Benefits and Value
The gateway implementation delivered significant advantages:
- Preserving Existing Investment: The deflashing machine, worth tens of thousands of dollars, continued to operate effectively, avoiding waste from equipment obsolescence or major retrofits.
- Enhanced System Compatibility: The S7-1200 PROFINET controller and the PROFIBUS slave device achieved seamless compatibility with stable, reliable communication that met real-time requirements for continuous flow production.
- Simplified Engineering: Electrical connections were straightforward—just connect the gateway to the PROFINET switch network and the PROFIBUS bus. Intuitive software configuration significantly shortened on-site commissioning time.
- Increased Data Transparency: Previously isolated deflashing machine data could now be uploaded in real time to SCADA or HMI systems, providing data support for OEE analysis and fault diagnosis.
Technical Insights and Best Practices
When deploying such gateways, several technical aspects ensure success. First, the gateway must support the required PROFIBUS baud rates—typically up to 12 Mbps—and handle the data volume of the application. For a deflashing machine, typical cyclic data might include 4 bytes of output (control word and speed reference) and 6 bytes of input (status word, actual speed, fault code). The gateway’s GSDML file is imported into TIA Portal, and the I/O mapping is configured via a user-friendly web interface or dedicated tool.
Network topology also matters. The PROFINET side connects to a managed switch, while the PROFIBUS side requires proper termination and addressing. In this project, the gateway was set as PROFIBUS master, and the deflashing machine as slave address 3. The update time was set to 2 ms, ensuring responsive control.
| Parameter | Value |
|---|---|
| PROFINET Interface | 100 Mbps, full-duplex, RJ45 |
| PROFIBUS Interface | DP-V0/V1, 9.6 kbps to 12 Mbps, D-sub 9-pin |
| Max PROFIBUS Slaves | 125 |
| Data Exchange Size | Up to 244 bytes input / 244 bytes output per slave |
| Configuration | Web interface or dedicated software, GSDML file |
| Operating Temperature | -20°C to +60°C |
Real-World Performance
After commissioning, the system achieved a communication cycle time of under 5 ms, well within the deflashing machine’s tolerance. The production line saw no interruptions due to communication faults over a three-month observation period. Operators could now monitor machine status and adjust parameters from the central HMI, reducing manual checks and improving overall equipment effectiveness (OEE) by an estimated 8%.
Conclusion
In industrial automation, bridging old and new technologies is a recurring challenge. This project demonstrates that a PROFINET-to-PROFIBUS gateway not only solves communication barriers but also unlocks the hidden value of existing equipment. It proves that on the path to Industry 4.0, a well-chosen protocol converter can be the key to integrating information silos and enabling flexible manufacturing, giving classic machines a new lease on life in modern production lines.
