Mitsubishi Ethernet

See purchasing information for more details
mitsubishi ethernet demo download

Product Overview

The Mitsubishi Ethernet device driver works in conjunction with KEPServerEX to exchange data between OPC clients and Mitsubishi A and Q Series PLCs connected via the AJ71E71 or QJ71E71 family of communication cards. KEPServerEX automatically optimizes data acquisition based on client demand, and ensures data integrity through extensive error handling.

Resources

Performance

  • Supports device auto-demotion
  • Supports PC numbers network bridging
  • Uses AJ71E71 family of communications cards
  • Supports the following Memory Types: CC, X, Y, M, B, L, F, TS, TC, TN, CS, CT, CN, D, W, R
  • Supports the following Q-specific Memory Types: DX, DY, SB, SM, V, SS, SC, SN, SD, SW, Z
  • Supports all data types

Protocols

  • MELSEC

Supported Devices

  • All A Series and Q (Q mode) Series PLCs
  • FX3U
  • Mitsubishi iQ-F Series CPUs
  • Mitsubishi iQ-R Series CPUs
  • Mitsubishi L Series
  • Mitsubishi QnA Series

Available Languages

  • English
  • Japanese
  • Simplified Chinese

Application Support

  • DDE Format CF_Text and AdvancedDDE
  • NIO Interface for iFIX
  • OPC .NET Service (OPC .NET) Version 1.00
  • OPC Alarms and Events (OPC AE) Version 1.10
  • OPC Data Access (OPC DA) Versions 1.0a, 2.0, 2.05a, and 3.0
  • OPC Unified Architecture (OPC UA) Version 1.02
  • SuiteLink and FastDDE for Wonderware

Release Notes

6.2.460.0

7/6/2017

  • Added Chinese language support.

6.2.429.0

6/8/2017

  • Added the ability to interface with Mitsubishi iQ-R series CPUs through the CPU’s built-in Ethernet Port or through the RJ71EN71 Ethernet module.
  • Added the ability to interface with Mitsubishi iQ-F series CPUs through the CPU’s built-in Ethernet Port.
  • Enhanced support for limited bandwidth scenarios by reducing the minimum Word Block Size from 16 to 1 for the Q, QnA, and L series controllers.
  • Fixed an issue that introduced in version 6.1 that prevented arrays larger than the maximum block size from being accessed for the A, FX3U, and Q series controllers. Users of the Q Series must edit the server project to adjust the block size to be equal to or larger than the array size.
  • Fixed an issue in the Q, QnA, and L series models where writes were not allowed for arrays larger than 256.

    Note: Support for reading arrays larger than 256 was added in V6.1.

6.1.601.0

4/4/2017

  • Added support for Random Writes on some models so multiple writes can be sent in a single request significantly increasing the write performance.
  • Added support for QnA and L Series Models.
  • Added the ability for users to specify read/write block sizes. Larger block sizes can greatly increase read performance.

6.0.2107.0

11/15/2016

  • Added support for Chinese, Japanese, and Korean (CJK) characters.
  • Added support for redundant and multiple CPU configurations to the Q-Series model.
  • Added Japanese language support.

5.21.114.0

3/20/2017

  • Added support for Chinese, Japanese and Korean (CJK) characters.
  • Added support for redundant and multiple CPU configurations to the Q-Series device model.

5.14.491.0

2/18/2014

  • The Mitsubishi Ethernet Driver now handles the closing of a connection correctly whether it was initiated by the server or by the device.
  • Fixed an issue with the A Series model where Boolean Special Int. Relays were bit shifted in memory.

5.10.205

11/13/2012

Fixed the address validation failures that resulted from leading zeroes.

5.8.109.0

2/21/2012

Corrected issues that prevented the Synchronization Method from persisting. Fixed an issue where the Time and Date Synchronization dialog was not being updated correctly after the model was changed but had not been applied.

5.6.122.0

7/25/2011

  • Increased the address ranges allowed for B, CC, CN, CS, F, L, M, SB, SW, TC, TN, TS, V, and Z memory types.

5.4.131.0

10/28/2010

  • Resolved issue for native Boolean address types where driver returned "Bad Address" instead of "Bad Type" on first attempt at adding dynamic tag of data type Double.
  • Fixed an issue wherein the parser did not accept addresses for X, Y, W, and ZR if the hex component immediately followed the memory type.

5.3.118.0

6/9/2010

  • Added Support for "L" suffix to CN type.
  • Fixed issue where address parser allowed Date data types for bit addresses.
  • No longer deactivate tags for out of range errors.
  • Enhanced event log messages for read and write errors.
  • Added support for ZR file registers to the Q Series model.

5.1.71.0

10/21/2009

  • Added support for Double and Date data types to A Series and FX3U models.
  • Added support for Extended Data Registers to Q series models.
  • Added support for Extended Link Registers to Q series models.
  • Added support for Double and Date data types to Q series models.

What Is a Driver?

KEPServerEX is more than an OPC server—it's a connectivity platform for industrial automation and IoT. Simply download KEPServerEX, and then select from Kepware's library of more than 150 device drivers, client drivers, and advanced plug-ins to fit the communication requirements unique to your industrial control system.

A driver is a software component that enables KEPServerEX to meet the connectivity requirements of a specific device, system, or other data source. The driver handles all proprietary communications to the data source for KEPServerEX; the client interfaces handle all supported OPC, proprietary, and open standards connectivity to applications that monitor or control the devices.

Drivers may be licensed individually or in suites. Additional drivers can be licensed on demand as connectivity needs evolve.

Purchasing Information

This product is available for purchase through the following suites:


© PTC Inc. All Rights Reserved.