Mitsubishi Electric Implementation

OPC-UA for Mitsubishi Electric

Open Platform Communications Unified Architecture - platform-independent standard for industrial communication and data exchange.

Type: Industrial EthernetSpeed: Network dependentReleased: 2008Organization: OPC Foundation
Network dependent
Bandwidth
Unlimited
Max Nodes
Network dependent
Max Distance
No
Real-Time

Protocol Overview

Mitsubishi FX5/Q-series support OPC UA via MC Works64 SCADA or third-party servers like Kepware. Native OPC UA server in newer CPUs (Q-series iQ-R). GX Works3 provides tag export for OPC UA.

When to Use OPC-UA

Choose OPC-UA for enterprise integration, cloud connectivity, multi-vendor environments, or Industry 4.0 initiatives requiring secure data exchange.

Mitsubishi Electric Hardware Requirements

Compatible Communication Modules

iQ-R series (RJ71EIP91 with OPC UA)
FX5U via MC Works64
Any PLC via Kepware/Matrikon OPC UA

Wiring Details

Network Setup

Standard Ethernet. Port 4840. Uses CPU Ethernet interface or dedicated Ethernet module.

Configuration

MC Works64: Configure OPC UA server settings. Import tag database from GX Works3. Set access permissions.

Mitsubishi Electric Software & Programming

Function Blocks & Instructions

MC Works64 OPC UA server
Kepware driver for Mitsubishi
Native server in iQ-R

Mitsubishi Electric Code Example

// MC Works64 OPC UA configuration:
// 1. Import GX Works3 project to get tag list
// 2. OPC UA Server settings > Enable server
// 3. Security: Anonymous, Username/Password, or Certificate
// 4. Endpoint: opc.tcp://SCADA-PC:4840

// Kepware driver:
// Add channel: Mitsubishi Ethernet Driver
// IP: 192.168.1.10, Protocol: SLMP
// Device structure: D registers, M relays auto-discovered
// OPC UA client connects to Kepware endpoint

Mitsubishi Electric-Specific Implementation Notes

Native OPC UA primarily via MC Works64 SCADA package. iQ-R series has built-in OPC UA server capability. SLMP (Seamless Message Protocol) used for underlying communication. Tag names from GX Works3 preserved in OPC UA address space.

Technical Specifications

Physical Layer

  • Physical Layer: IP-based
  • Cable Type: Any IP network media
  • Topology: Any IP network topology
  • Power Over Cable: No

Data Layer

  • Data Link: TCP/IP or SOAP/HTTPS
  • Encoding: Binary or XML
  • Error Detection: Built-in security
  • Frame Size: Network dependent

Performance

  • Scan Time: Configurable subscription rates
  • Deterministic: No
  • Real-Time: No

Certification

  • Certification Required: No
  • License Cost: Open source implementations available, commercial stacks vary
  • Version: 1.05

Advantages & Disadvantages

Advantages

  • Platform and vendor independent
  • Built-in security (encryption, authentication)
  • Rich information modeling
  • Works across firewalls
  • Supports complex data structures
  • Historical data access
  • Pub/sub and client/server models
  • Industry 4.0 and IoT ready

Disadvantages

  • Not designed for hard real-time
  • Higher complexity than traditional protocols
  • More computing resources required
  • Learning curve for information modeling
  • Overhead for simple applications

Common Use Cases & Applications

Enterprise system integration
MES/ERP connectivity
Cloud and IoT applications
Cross-platform data exchange
Industry 4.0 implementations
Historian integration
Multi-vendor system integration

Industry Adoption

Adoption LevelHigh and growing rapidly
Market ShareGrowing rapidly as Industry 4.0 standard
Geographic PresenceWorldwide
Primary Industries
All industriesParticularly strong in Process IndustriesPharmaceuticalsDiscrete Manufacturing

Supported Message Types

Read
Write
Subscribe
Method calls
Events
Historical access