Mitsubishi A Series PLC Protocol

Overview

The Mitsubishi A serial downloadable protocol is for communication between the Mitsubishi A inverters and an OCS. This is a Master/Slave protocol.

Cscape Configuration

To configure OCS for the Mitsubishi protocol, select the Protocol Configuration from the Program menu in CSCAPE software. Select the appropriate protocol type on the desired port. To make sure that the Software is able to configure the equipment for the correct protocol, ensure MitsiA.dll file is in the Protocols directory of the current working/open Cscape.

Serial Port Configuration

The default link settings for the terminal are : 9600 baud, No parity, 8 data bits, 1 stop bit, RS232 communication and No handshaking.

Selecting Device Register

The packet format changes based on Device Type selected.

Address Mapping for OCS and Supported Functions

MitsiA.dll (Version 1.00 and Later) supports the following addressing modes:

Enter the desired parameter address in the Device Register field or click " > " button to view the parameter range details.

Mitsubishi A Series Drive Parameters

Parameter Type	Parameter Range	Format
DATA REGISTER (D)	0-6143	DECIMAL
SPECIAL DATA REGISTER (D)	9000-9255	DECIMAL
LINK REGISTER (W)	0-0FFF	HEXADECIMAL
FILE REGISTER (R)	0-8191	DECIMAL
TIMER PRESENT VALUE (TN)	0-2047	DECIMAL
COUNTER PRESENT VALUE (CN)	0-1023	DECIMAL
INPUT REGISTER (X)	0-07FF	HEXADECIMAL
OUTPUT REGISTER (Y)	0-07FF	HEXADECIMAL
INTERNAL RELAY (M)	0-8191	DECIMAL
SPECIAL RELAY (M)	9000-9255	DECIMAL
LATCH RELAY (L)	0-8191	DECIMAL
STEP RELAY (S)	0-8191	DECIMAL
LINK RELAY (B)	0-0FFF	HEXADECIMAL
ANNUNCIATOR (F)	0-2047	DECIMAL
TIMER CONTACTS (TS)	0-2047	DECIMAL
COUNTER CONTACTS (CS)	0-1023	DECIMAL
TIMER COILS (TC)	0-2047	DECIMAL
COUNTER COILS (CC)	0-1023	DECIMAL

Network Communication Errors

In order to access the Network statistics, user must assign the “Network status register” in network configuration. The table below gives the details of statistics.

Number	Statistics	Location	Description

1	Update interval exceeded count	%Rx	This register explains number of times that the actual transaction scan time to complete all transactions exceeded specified update interval. Generally used as an indicator that an excessive number of triggered transfers or failed communication retries are occurring that is lengthening the expected transaction scan time. If the Update interval is set to zero (update as fast as possible), this 32-bit register alternately specifies the actual transaction scan time in mSec resolution.
2	No response count	%R(x+2)	This register explains number of times that a device(s) did not respond to a transaction. This includes ALL failed transaction, not just those after the retry count is exceeded.
3	Corrupt Response Count	%R(x+4)	This register explains number of times that a device(s) returned an invalid or failed response to a transaction. This includes ALL failed. Transaction, not just those after the retry count is exceeded.
4	Valid Response Count	%R(x+6)	This register explains total number of valid responses.

NOTE: %Rx: 32-bit network status register configured in Network configuration. For example: %R500(501).

Device Communication Errors

Error	Error Number	Description
INVALID_BLOCK	-203	Invalid size for data type.
NO_RESPONSE_FROM_PLC	-204	Timeout while waiting for remote node response.
INVALID_RESPONSE_FROM_PLC	-205	Corrupted response from remote node.
INVALID_INITIALISATION	-207	Internal Error - Unable to open port.

Connection Details

Illustrations below show the various end-of-cable connectors required:

25-Pin D-Type Male	10-Pin Weidmuller Cage Clamp	8-Pin RJ 45 Plug	9-Pin DB Male

CN1	CN1	MJ1/MJ2	Port 1

Port 1 — DB9 (Female at OCS end)

MJ1/MJ2 — RJ45 (Female at OCS end)

CN1 — 10-Pin Weidmuller Cage Clamp (Female at OCS end)

CN1 — DB25 (Female at OCS end)

NOTES:

Do not connect to unlisted pins.
Recommended Cable: Beldon 9503, twisted multipair, screened.
Connect the screens together at the shield / earth pin of the PLC.