Multi-Brand PLC Control: EtherNet/IP & CC-Link in Robot Lines

In modern manufacturing, robotic production lines often combine equipment from multiple vendors. A typical challenge arises when a supervisory system uses one industrial network protocol while field devices rely on another. This article examines a practical solution for integrating Rockwell Automation ControlLogix PLCs (EtherNet/IP) with Mitsubishi robot controllers and peripherals (CC-Link) using a dedicated protocol conversion gateway. The approach eliminates complex hardwiring, improves reliability, and enables real-time data exchange.

Project Background: The Multi-Brand Integration Dilemma

In an automotive component welding station, the upper-level monitoring system was built on a Rockwell ControlLogix platform supporting EtherNet/IP. Meanwhile, Mitsubishi robot controllers and auxiliary equipment communicated via CC-Link. Traditional integration methods demanded intermediate controllers and extensive hardwiring—over 200 I/O points—resulting in poor system stability, difficult troubleshooting, and limited scalability. The mean time between failures (MTBF) was only 72 hours, and signal transmission delays ranged from 15 to 20 ms, which is unacceptable for synchronized robot motion.

The Solution: Protocol Conversion Gateway as a Central Hub

The core of the solution is a specialized protocol conversion gateway with dual network interfaces. One side communicates with the Rockwell PLC via EtherNet/IP, while the other connects to the Mitsubishi PLC and robot controllers over CC-Link. Inside the gateway, a bidirectional data mapping table is established, enabling real-time conversion between the two protocols. The transmission delay is kept under 5 ms, meeting the stringent requirements for robot synchronous control.

Key Features of the Gateway Configuration

  • 128-point input / 128-point output data exchange area
  • Transparent transmission mode: appears as a generic Ethernet module to Rockwell PLC, and as an intelligent device station on CC-Link
  • Real-time bidirectional transfer of critical parameters: welding current, position coordinates, etc.

Implementation Process and Network Topology

The implementation was carried out in three phases:

  1. Network Planning: Assign IP addresses for EtherNet/IP devices and station numbers for CC-Link nodes.
  2. Gateway Parameter Configuration: Set up the data mapping tables and communication settings.
  3. Joint Commissioning: Verify data consistency and real-time performance across the entire system.
[Rockwell PLC]---(EtherNet/IP)---[Protocol Gateway]---(CC-Link)---[Mitsubishi PLC]
       |                                                      |
   [HMI]                                          [Mitsubishi Robot][Welder][Positioner]
    

Performance Comparison: Before vs. After

Metric Before Integration After Integration
MTBF (Mean Time Between Failures) 72 hours 240 hours
Signal Transmission Delay 15–20 ms <5 ms
New Device Integration Time 3–5 working days <4 hours
Hardwired I/O Points Over 200 Reduced by 80%
Wiring Cost Baseline 35% reduction

Industry Application Value

This integration approach is particularly valuable in robot-intensive industries such as automotive manufacturing and 3C electronics. In a new energy vehicle battery pack production line project, the same architecture successfully integrated seven robots from different brands, achieving full-line data connectivity. Compared to a single-vendor solution, this hybrid network approach saved over 40% in equipment investment.

Innovation Summary

The key innovation lies in breaking the “brand barrier” common in industrial automation. Through precisely tailored protocol conversion strategies, the project achieved:

  • Deep integration of heterogeneous systems: Seamless data-layer connection while preserving native performance of each brand’s equipment.
  • Cost-performance balance: Avoided forced replacement of existing devices, significantly reducing upgrade costs.
  • Improved maintenance convenience: A unified network monitoring interface reduced fault location time by 60%.

This “bridge-type” integration scheme provides manufacturers with a flexible and economical path for digital transformation, especially in scenarios involving upgrades of existing equipment. Looking ahead, with the development of Time-Sensitive Networking (TSN) technology, such cross-protocol integration solutions will play an even more important role in the Industrial Internet of Things (IIoT) ecosystem.

Technical Note: When implementing protocol gateways, ensure that the data mapping tables are correctly configured to match the endianness and data structure of both networks. Regular firmware updates and network diagnostics are recommended to maintain optimal performance.

Similar Posts