CC-Link IE to DeviceNet Gateway for Mitsubishi PLC Integration
In modern industrial automation, the coexistence of different communication protocols often creates data silos that hinder efficiency. A typical scenario occurs when a factory uses Mitsubishi Q series PLCs with CC-Link IE for high-speed control, while field devices like smart meters operate on DeviceNet. Without a direct communication path, data must be collected manually, leading to delays and errors. This article explores a proven solution using a protocol conversion gateway to bridge CC-Link IE and DeviceNet, enabling seamless data integration and real-time monitoring.
Key Challenge:
27 DeviceNet smart meters needed to communicate with a Mitsubishi CC-Link IE PLC network. Manual data collection every two hours resulted in a 1.2% cumulative error and prevented real-time energy management.
The Protocol Gap: CC-Link IE vs. DeviceNet
CC-Link IE is a deterministic gigabit Ethernet protocol widely used in Mitsubishi Electric control systems for high-speed, large-volume data exchange. DeviceNet, based on CAN bus, is common for connecting lower-level devices like sensors, actuators, and power meters. These protocols differ not only in physical layer and data format but also in communication models. A direct connection is impossible without a gateway that can translate between the two.
Gateway Solution: How It Works
A dedicated protocol gateway acts as a bridge. On the DeviceNet side, it functions as a master, polling slave devices (smart meters) and collecting data such as voltage, current, power, and energy. On the CC-Link IE side, it appears as a slave device to the PLC master. The gateway’s internal mapping table links DeviceNet input data to CC-Link IE registers, allowing the PLC to read meter values as if they were local I/O.
Typical Configuration Steps
- CC-Link IE side: Set station number (e.g., 3) and communication speed (1 Gbps). Map PLC registers (e.g., WR0–WR100) to gateway memory.
- DeviceNet side: Set baud rate (typically 500 kbps) and configure slave device MAC IDs. Define polling cycles for each meter.
- Data mapping: Assign specific DeviceNet parameters to corresponding CC-Link IE register addresses. For example, voltage from meter 1 to WR10, current to WR11, etc.
Real-World Application: Energy Monitoring in Automotive Parts Manufacturing
In an automotive components plant, 27 smart meters on DeviceNet were measuring energy consumption of production lines. The central control system used a Mitsubishi Q PLC with CC-Link IE. Before integration, operators manually recorded meter readings every two hours, leading to a 1.2% error and no real-time visibility. After installing a gateway (model NY-CE-DEM), the data flow became fully automated.
| Parameter | Before Integration | After Integration |
|---|---|---|
| Data Collection Frequency | Every 2 hours (manual) | Every 1 second (automatic) |
| Data Accuracy | ~98.8% (1.2% error) | 100% |
| Labor Cost per Year | ~$10,000 (manual reading) | $0 (automated) |
| System Scalability | Limited by manual process | Up to 32 DeviceNet slaves per gateway |
Technical Details: Data Exchange Mechanism
The gateway performs protocol conversion at the hardware level, ensuring low latency. The process involves:
- DeviceNet Polling: The gateway, as DeviceNet master, sends explicit messages to each meter according to a configured scan list. It retrieves raw data frames containing electrical parameters.
- Data Extraction: The internal engine parses the DeviceNet frames, extracting engineering values (e.g., 480.5 V, 125.3 A).
- CC-Link IE Mapping: These values are placed into the gateway’s CC-Link IE output area, which the PLC reads cyclically via the CC-Link IE network. The PLC can also write commands to the gateway’s input area to control DeviceNet devices if needed.
Result:
The Mitsubishi PLC now accesses real-time energy data from all 27 meters every second, enabling dynamic energy monitoring, load balancing, and predictive maintenance alerts.
Benefits Beyond Connectivity
Implementing a CC-Link IE to DeviceNet gateway delivers several operational advantages:
- Cost Savings: Eliminating manual data collection saves approximately $10,000 annually in labor. More importantly, accurate energy data helps identify waste, leading to reduced utility bills.
- Improved Decision-Making: Real-time data feeds into SCADA or MES systems, providing dashboards for energy consumption trends, peak demand analysis, and equipment efficiency.
- Scalability: A single gateway can handle up to 32 DeviceNet nodes, allowing easy expansion as new meters or devices are added.
- Investment Protection: Existing DeviceNet meters and Mitsubishi PLC infrastructure remain unchanged, avoiding costly replacements.
Choosing the Right Gateway
When selecting a protocol converter, consider the following:
- Protocol Support: Ensure it supports both CC-Link IE (Field or Control) and DeviceNet with the required baud rates and I/O sizes.
- Configuration Ease: Look for gateways with user-friendly software for mapping and diagnostics.
- Performance: Hardware-based conversion ensures minimal latency, critical for real-time control.
- Reliability: Industrial-grade design with wide temperature range and galvanic isolation.
Conclusion
The integration of DeviceNet devices into a CC-Link IE network is a common challenge in factories upgrading to smart manufacturing. A dedicated protocol gateway provides a cost-effective, reliable, and scalable solution. By enabling real-time data acquisition from energy meters, sensors, or actuators, manufacturers can unlock the full potential of their automation systems, improve energy efficiency, and move toward data-driven operations. This approach is applicable not only to energy monitoring but also to any scenario where heterogeneous industrial networks must coexist.
Typical Applications:
Automotive assembly lines, food and beverage processing, packaging machinery, material handling systems, and any facility using Mitsubishi PLCs with legacy DeviceNet devices.
