Mitsubishi AJ71PB96 User manual

REVISIONS
Print Date
Apr., 1994
'The manual number
is given on the bottom left of the back cover.
*Manual Number
IB (NA) 66459-A
Revision
First edition

. --
2. COM~CATIONG -WITH AN All1 PB96
There are three possiblerelationships between two stations that are com-
municating by means of
FMS services:
(1) Initiator (station that sends a connection requestto another station) and
(2) Client (station that sends a confirmed service request to another
responder (station that sends
a responseto a request from anotherstation).
station) and
server (station that sends the reeponseto the confirmed
service request from another station).
another station) and receiver (station that receives unconfirmed service
requests fromanother station).
The role of an AJ71PB96 is determined by the master/slave station opera-
tion mode selection.
(3) Requester (station that sends an unconfirmed service requestto
(a) When operating as a master station, it can have the following roles:
0 Initiator or responder.
. Client or server.
Requester or receiver.
(b) When operating as a slavestation, it can have the following roles:
Responder only.
Server only.
Requester or receiver only.
Communicationwith an AJ71 PB96starts with the transmissionof the initi-
ate service from theclient; then, after a normal connection has been made,
data is exchangedwith the PC CPU by using services such as
VFD man-
agement, object management and variable access.
To release the connectionand end communication,the Abort service is
transmitted.
All the communication types below, which are regulated byPROFIBUS, can
be used with the AJ71
PB96.
Connection Oriented Communication
MMAC
. . . . . .Master - master acyclic connection
MSAC
. . . . . . .Master - slave acyclic connection (with no slave initiative)
MSAC-SI
. . . .Master - slave acyclic connection (with slave initiative)
MSCY
. . . . . . .Master - slave cyclic connection (with no slave initiative)
MSCY-SI
. . . .Master - slave cyclic connection (with slave initiative)
Connection Less Communication
BRCT
. . . . . . .Broadcast communication
MULT
. . . . . . .Multicast communication
In addition,
if both theAJ71 PB96 andthe communicating station are operat-
ing as master stations, master-mastercyclic communication canbe per-
formed by using MSCY
or MSCY-SI to communicatewith the
communicating station. This function is called "slave emulation".
2-1
2. COMMUNICATING WITH AN AJ71PB96

[FMS protocol (MMAC/D)J
(1) ConnectionEstablishment
AJ71P896 (master)
Communicating Station .(master)
Initiate
1
Arf71,PBW (rnader)
or
Communicating Station (master)
?,'
Initiate
(3) ConnectionRelease
AJ71
PB96 (master) CommunicatingStation (master)
Abort
L
(ReieW
I
,
Abort
(Rei-)
Abort I
2-3
2. COMMUNICATING WITH AN AJ71PB96

[FMS protocol (MMAC/I)]
(1) ConnectionEstablishment
A37tP896 (masm)
CommunicatingStation (master)
Initiate
-
(2) Data Transfer
I I
N71 W96 (master) I , Communicating Station. (master)
Read
*
Write '
I
Write
0
*' InformationReport
(3) Connection Release
AJ71
PB96 (master) Communicating Station (master)
Abort
Abort I
*
(Reject)
Abort
(Reiect)
2-4
I
c
1
1
P
2. COMMUNICATING WITH AN AJ71PB96

2. COMMUNICATING I .-- ( . .. WITHAN AdSPm. : 1.
MalsErza
[FMS protocol (MMAC/O)J
(1) ConnectionEstablisment
AJ71 PBQ6 (master)
Communicating .Station (master)
I
Initiate
(2) DataTransfer
I I
-.
,-
(3) ConnectionRelease
AJ71
PB96 (master) Communicating Station (master)
Abort
I
(Reject)
.
4
Abort [
.
Abort
(Reject)
2-5
2. COMMUNICATING WITH AN AJ71PB96

2-6
1
2. COMMUNICATING WITH AN AJ71PB96

2. COMMUNICATING A.. - . WITH ANA37IP096
. i .. humJ&GA
[FMS protocol (MSACID, IO: Slave station)]
(1) ConnectionEstablishment
AJ71
PB96 (slave)
Communicating Station (master)
I'
Initiate
Unsolicited
Status
Identify
(3) Connection Release
AJ71
PB96 (slave) CommunicatingStation (master)
Abort
.
'Abort
(Reiect)
(Reject)
Abort I
c
2-7
2. COMMUNICATING WITH AN AJ71PB96

[FMS protocol (MSAC-SI/D: Master station)]
(1) ConnectionEstablisment
A3-V PW3 {master) '...
Communicating Station ,(sl.ave)
I I
L...................
Write s
Information Report 1-4
Read I-,
(3) Cpnnection Release
AJ71
PB96 (master) Communicating Station (slave)
Abort
(Reiect)
b
.
-Abort
-
(Rei4
Abort
[
*
2-8
2. COMMUNICATING WITH AN AJ71PB96

2. COMMUNICATING .. I WITH AN A331 PB96..
wiLS6c-A
[FMS protocol (MSAC-SI/D, /0: Slave station)]
(1) ConnectionEstablishment
AJ71 PB96 (slave)
Communicating station (master)
I
~
Initiate
Unsolicited Status
Identify
Unsolicited Status
(Reject)
Abort (Reject)
2-9
2. COMMUNICATING WITH AN AJ71PB96

[FMS protocol (MSCY/D: Master station)]
(1) ConnectionEstablishment
-. Ant7B.~W (master) -I
...... Communicatjng, Statim (slave) - .
..
V'
Initial6
I
(2) Data Transfer
A171 PB96 (master) I Communicatirtg.8)ati1(s1ave)
. ................................................................................................................................
Unsolicited Status
r
Write
r
Read
L .
VFD Management ,
....................................................................................................................................................................
...................................................................................
..................................................
Variable Access-:
I
I
.. formation Report
t
J
...................................................................................................................................................................
(3) Connection Release
A371 PB96 (master) Communicating Station (slave)
Abort
' *
a 8
Abort
(Reject)
Abort I
(Reject)
2-10
2. COMMUNICATING WITH AN AJ71PB96

2. COMMUNICATINGWITHAN AJ71m96. ,.
MElS€G=A
[FMS protocol (MSAC/D, /0: Slave station)]
(1) ConnectionEstablishment
AJ71
P896 (slave) Communicating Station (master)
Initiate
*
(2) Data Transfer
M71P896 (slave) I , Communicating Station (master)
(3) Connection Release
AJ71
PB96 (slave) CommunicatingStation (master)
..
Abort
L
Abori
(ReiW
(Rei-)
Abort I
L
2- 11
2. COMMUNICATING WITH AN AJ71PB96

[FMS protocol (MSYC-SVD: Master station)]
(1) Connection Establismnt
Ad71 ,W6. (mamr).
CommunicatingStatim (ishue)
lraitiate
-.
I
(2)Data Transfer
Information Report
1-1
(3) ConnectionRelease
AJ71
PB96 (master) Communicating Station (slave)
AbOfi
-
(Reed)
*
8
Abort
(Reject)
Abort
4'
2- 12
t
2. COMMUNICATING WITH AN AJ71PB96

2. COMMUNICATING d'. . WITH ANAJ?lPB96 .
I M€ilSE&A
[FMS protocol (MSCY-SVD, /0: Slave station)]
(1) ConnectionEstablishment
AJ71
PBB6 (slave) Communicating Station (master)
.
Initiate
(2) Data Transfer
I 1
AJ71-96 (slave) I I CommunicatingStation(master)
(3) Connection Release
AJ71
PB96 (slave) CommunicatingStation (master)
Abort
* I
Abort
(Reject)
Abort I
.
(Reject)
2-13
2. COMMUNICATING WITH AN AJ71PB96

[FMS protocol (BRCT, MULT: Requester)]
(1) Connection Establishment'
No conrwrction is established for Connection Lass ComtWnicatlon.
(2) Data Transfer
AJ71PB96 (master)
I <
[FMS protocol (BRCT, MULT: Receiver)]
(1) Connection Establishment
Connection release is not performed in the case of Connection Less
Communication.
(2) DataTransfer
AJ71PB96 (master/slave) Communicating Station (master)
,.____.________.________.__.____________----------------------------------.__.__._.______.___.______._._.._.______.--.-.-.-.--~-
Unsoticited Status VFD Management
-;
(3) Connection Release
Connection release is not performed in the case
of Connection Less
Communication.
J
I
2- 14
2. COMMUNICATING WITH AN AJ71PB96