Mitsubishi Electric A1SJ71PB96F, AJ71PB96F User Manual

Download

Page 1

MEL SEC A se ries

Pro gram ma ble Con trol ler

User's Ma nu al

Profibus Modules

A(1S)J71PB96F

981001

65629-C

MITSU BIS HI ELECTRIC

MITSU BIS HI ELECTRIC EU RO PE B.V.

FAC TO RY AU TO MA TION

Page 2

Page 3







SAFETY PRECAUTIONS



(Read these precautions before using.)

When using Mitsubishi equipment, thoroughly read this manual and the associated manuals introduced in this manual. Also pay careful attention to safety and handle the module properly.

These precautions apply only to Mitsubishi equipment. Refer to the CPU module user’s manual for a description of the PC system safety precautions.

These  SAFETY PRECAUTIONS  classify the safety precautions into two categories: “DANGER” and “CAUTION”.



DANGER

Procedures which may lead to a dangerous condition and cause death or serious injury if not carried out properly.



CAUTION

Procedures which may lead to a dangerous condition and cause superficial to medium injury, or physical damage only, if not carried out properly.

Depending on circumstances, procedures indicated by

CAUTION

may also be linked to serious

results. In any case, it is important to follow the directions for usage. Store this manual in a safe place so that you can take it out and read it whenever necessary. Always

forward it to the end user.

[DESIGN PRECAUTIONS]

DANGER



When controlling a PLC by connecting to another station via PROFIBUS for the purpose of changing the data, changing the program, or changing operation status (status control), an interlock circuit must be configured in the sequence program so that the entire system will always operate safely. If a remote PLC is a controlled in the manner indicated above by another station, the system may fail to respond immediately even if trouble occurs at the remote PLC due to data communication error. In addition to configuring the interlock circuit in the sequence program, determine the action to be taken by the system at the occurrence of the data communication error with regard to the processing between the other stations and PLC CPU.



CAUTION



When the PROFIBUS cable is laid, do not lay it close to main circuits or power lines. They should be installed 100mm(3.9inch) or more from each other. Not doing so could result in noise that would cause malfunction.

Page 4

[INSTALLATION PRECAUTIONS]



CAUTION

Use the module in the environment given in the general specifications of the CPU module’s User’s Manual.

Using the module outside the range of the general specifications may result in electric shock, fire or malfunction, or may damage or degrade the module.

Insert the tabs at the bottom of the module into the mounting holes in the base unit.

(The AnS series module shall be fastened by screws in the base unit at the specified torque.) Not installing the module correctly could result in malfunction, breakdowns or pieces of the product falling.

Do not touch the conductive area or electric parts of the module.

Doing so may cause module malfunction or breakdowns.

Tighten the screws with the specified torque. If the screws are loose, it could result in falling, breaks or

malfunction of the module. If the screws are too tight, it could result in falling, breaks or malfunction due to damage of the screws or the module.

[WIRING PRECAUTIONS]



CAUTION

Switch all phases of the external power supply of the PC system off before connecting the PROFIBUS cable.

Not doing so could cause failure or malfunction of the module.

Be careful not to let foreign matter such as filings or wire chips get inside the module. These can cause fire,

breakdowns and malfunction.

The PROFIBUS cable which is connected to the module must be protected with a duct or secured in position

with clamps. Unless the cable is thus protected or secured, the module or the cable could be damaged when the cable swings, moves or it is strained with careless pulls, or it could cause malfunction when the cable contacts with any undesirable objects.

When disconnecting the PROFIBUS cable from the module, do not pull by holding the cable section. To

disconnect the cable, make sure to hold the connector which is coupled with the module. Do not attempt to pull the cable to disconnect it from the module. It could damage the module or the cable, or cause malfunction due to a poor contact of the cable.

[STARTING AND MAINTENANCE PRECAUTIONS]



DANGER

Switch all phases of the external power supply off before cleaning. Not doing so could cause electric shock.

Page 5



CAUTION

Never disassemble or modify the module.

This may cause breakdowns, malfunction, injury and/or fire.

Switch all phases of the external power supply off before mounting or removing the module. If you do not

switch off the external power supply, it will cause breakdowns or malfunction of the module.

[OPERATING PRECAUTIONS]



DANGER

Do not write data into the "unused area" of the buffer memory of this modules. Also, do not output the

"unused" signal as the output signal to this module from the PC CPU. Writing data into the "unused area" or outputting an "unused" signal may cause system malfunctions in the PC.



CAUTION

The online operations conducted for the CPU module being operated (especially when changing data or

operation status), shall be conducted after the manual has been carefully read and a sufficient check of safety has been conducted. Operation mistakes could cause breakdowns to or malfunction of the module.

[DISPOSAL PRECAUTIONS]



CAUTION



When disposing of this product, treat it as industrial waste.

Page 6

Revisions

* The manual number is noted at the lower left of the back cover.

Print Date *Manual Number Revision

Mar. 1997 IB (NA)-66771-A First printing

Jul., 1997

IB(NA)-66771-B

Correction SAFETY PRECAUTIONS, Section 4.2, 4.4.1, 4.6, 4.7.1, 4.7.2, 6.5, 7.1.12,

7.2.9, 7.2.10, 8.2.1(1) Addition Section 4.8(3)

Oct., 1998

IB(NA)-66771-C

Model addition AJ71PB96F Correction SAFTY PRECAUTIONS, Chapter 1, 2, 3, Section 4.1, 4.2, 4.3, 4.5.1, 4.5.3,

4.6, 4.7, 4.8, Chapter 5, Section 6.2, 6.7, 6.11, 6.12, 7.1.1, 7.1.2, 7.1.4,

7.1.5, 7.1.6, 7.1.7, 7.1.8, 7.1.9, 7.1.10, 7.1.11, 7.1.12, 7.1.13, 7.1.14, 7.1.15,

7.1.16, 7.1.17, 7.1.18, 7.1.19, 7.1.20, 7.1.21, 7.1.22, 7.1.23, 7.1.24, 7.2, Chapter 8, Appendix 1

Addition Appendix 2, Appendix 5 Chapter alteration Appendix 2 → Appendix 3, Appendix 3 → Appendix 4, Appendix 4 → Appendix 6

This manual does not imply guarantee or implementation right for industrial ownership or implementation of other rights. Mitsubishi Electric Corporation is not responsible for industrial ownership problems caused by use of the contents of this manual.



1998 Mitsubishi Electric Corporation

Page 7

Introduction

Thank you for purchasing the Mitsubishi Programmable Controller MELSEC-A Series. Before using the equipment, please read this manual carefully to develop full familiarity with the functions and performance of the graphic operation terminal you have purchased, so as to ensure correct use. Please forward a copy of this manual to the end user.

Table of Contents

About This Manual

1. OVERVIEW 1-1 to 1-2

1.1 Software Configuration .......................................................................................................................................1- 1

1.2 AJ71PB96F/A1SJ71PB96F Characteristics.......................................................................................................1- 2

2. SYSTEM CONFIGURATION 2-1 to 2-10

2.1 Whole System Configuration..............................................................................................................................2- 1

2.2 Applicable CPU Modules....................................................................................................................................2- 3

2.3 System Configuration Precaution Items .............................................................................................................2- 4

2.3.1 Installable base units...............................................................................................................................2- 4

2.3.2 Combining with the MELSECNET (II), MELSECNET/B, or MELSECNET/10.........................................2- 5

3. SPECIFICATIONS 3-1 to 3-4

3.1 General Specification..........................................................................................................................................3- 1

3.2 Performance Specifications................................................................................................................................3- 2

3.3 Installation Specifications ...................................................................................................................................3- 4

4. FUNCTIONS 4-1 to 4-25

4.1 Positioning in The PROFIBUS-FMS Network.....................................................................................................4- 1

4.2 Bus Parameters..................................................................................................................................................4- 1

4.3 Communication Relationship..............................................................................................................................4- 2

4.3.1 CRL Setting Items and Default Values....................................................................................................4- 3

4.4 Support Service ..................................................................................................................................................4- 6

4.4.1 FMS remote service ................................................................................................................................4- 6

4.4.2 FMA7 remote service ..............................................................................................................................4- 9

4.5 Object Dictionary (OD)........................................................................................................................................4-10

4.5.1 Local OD 4- ............................................................................................................................................10

4.5.2 Local OD default setting..........................................................................................................................4-14

4.5.3 Remote OD..............................................................................................................................................4-15

4.6 I/O Signal List......................................................................................................................................................4-17

4.7 Buffer Memory ....................................................................................................................................................4-19

4.7.1 Information area explanation...................................................................................................................4-20

4.7.2 Network trouble information area............................................................................................................4-21

4.8 Timing Chart .......................................................................................................................................................4-23

5. PROCEDURES BEFORE SYSTEM OPERATION 5-1 to 5-10

5.1 Procedures before Operation .............................................................................................................................5- 1

5.2 Handling Precautions..........................................................................................................................................5- 3

5.3 Part Names and Settings....................................................................................................................................5- 4

5.4 Self-diagnosis Execution Method .......................................................................................................................5- 6

5.5 Wiring ................................................................................................................................................................5- 7

Page 8

5.5.1 PROFIBUS Cable Wiring.........................................................................................................................5- 7

5.5.2 Terminal switch........................................................................................................................................5- 7

5.5.3 Precautions Against Wiring .....................................................................................................................5- 8

5.6 Maintenance and Inspection...............................................................................................................................5-10

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM 6-1 to 6-23

6.1 FMS Service and Command No.........................................................................................................................6- 1

6.2 Program Example...............................................................................................................................................6- 1

6.2.1 Write ........................................................................................................................................................6- 1

6.2.2 Information Report...................................................................................................................................6- 2

6.3 FMS Communication Circuit Initiate With Partner Station (Initiate: Initiator)......................................................6- 2

6.4 FMS Communication Circuit Abort With Partner Station (Abort: Requester) .....................................................6- 4

6.5 Partner Station Status Read (Status: Client)......................................................................................................6- 5

6.6 Partner Station Identification Information Read (Identify: Client)........................................................................6- 6

6.7 Partner Station Variable Read (Read: Client).....................................................................................................6- 7

6.8 Partner Station Variable Write (Write: Client).....................................................................................................6-13

6.9 PC CPU Variable Report (Information Report: Requester)................................................................................6-15

6.10 PC CPU Status Report (Unsolicited Status: Requester) ....................................................................................6-17

6.11 Reporting the Partner Station Variable Data to the PC CPU (Information Report: Receiver)............................6-18

6.12 Reports to the Partner Station Status PC CPU (Unsolicited Status: Receiver)..................................................6-22

6.13 FMA7 Connection Abort (FMA7 Abort: Receiver)...............................................................................................6-23

7. COMMUNICATION THAT DO NOT REQUIRE THE SEQUENCE PROGRAM 7-1 to 7-38

7.1 FMS Service .......................................................................................................................................................7- 1

7.1.1 Connection with AJ71PB96F/A1SJ71PB96F (Initiate: Responder)........................................................7- 1

7.1.2 AJ71PB96F/A1SJ71PB96F connection abort (Abort: Receiver).............................................................7- 5

7.1.3 Service reject (Reject).............................................................................................................................7- 6

7.1.4 PC CPU status information (Status: Server)...........................................................................................7- 7

7.1.5 AJ71PB96F/A1SJ71PB96F identification information (Identify: Server).................................................7- 8

7.1.6 Object attribute acquisition (GetOD: Server)...........................................................................................7- 9

7.1.7 Initiate objects attribute setting (InitiatePutOD: Server) ..........................................................................7-11

7.1.8 Object attribute setting (PutOD: Server)..................................................................................................7-13

7.1.9 Object attribute setting termination (TerminatePutOD: Server)...............................................................7-13

7.1.10 Reading device memory and buffer memory (Read: Server)..................................................................7-14

7.1.11 Writing device memory and buffer memory (Write: Server)....................................................................7-15

7.1.12 Reading program capacity and comment capacity, etc. (Read: Server).................................................7-16

7.1.13 Initiating program, parameter, and comment, device buffer memory download

(InitiateDownloadSequence: Server).......................................................................................................7-17

7.1.14 Program, parameter, comment, device and buffer memory downloads

(DownloadSegument: Server).................................................................................................................7-18

7.1.15 Program, parameter, comment, device, and buffer memory download termination

(TerminateDownloadSegument: Server).................................................................................................7-19

7.1.16 Initiating program, parameter, comment, device, and buffer memory upload

(InitiateUploadSequence: Server)...........................................................................................................7-20

7.1.17 Uploading program, parameter, comment, and device buffer memories

(UploadSegument: Server)......................................................................................................................7-21

7.1.18 Termination of upload of program, parameter, comment, and device buffer memories

(TerminateUploadSegument: Server) .....................................................................................................7-22

7.1.19 Execution program definition (Create Program Invocation: Server)........................................................7-23

7.1.20 Execution program delete (Delete Program Invocation: Server).............................................................7-25

7.1.21 Program RUN (Start: Server) ..................................................................................................................7-26

7.1.22 Program pause (Stop: Server).................................................................................................................7-27

7.1.23 Program pause cancel (Resume: Server)...............................................................................................7-28

7.1.24 Program stop (Reset: Server)..................................................................................................................7-29

7.2 FMA7 Service .....................................................................................................................................................7-30

7.2.1 FMA7 communication..............................................................................................................................7-30

Page 9

7.2.2 FMA7 service outline...............................................................................................................................7-30

7.2.3 FMA7 connection initiation (FMA7 Initiate: Responder)..........................................................................7-31

7.2.4 FMA7 Connection connection abort (FMA7 Abort: Receiver).................................................................7-32

7.2.5 CRL setting initiate (InitiateLoadCRL: Server) ........................................................................................7-33

7.2.6 CRL setting (LoadCRL: Server) ..............................................................................................................7-34

7.2.7 CRL setting end (TerminateLoadCRL: Server).......................................................................................7-34

7.2.8 CRL read (ReadCRL: Server) .................................................................................................................7-35

7.2.9 Bus parameter read (ReadValue: Server)...............................................................................................7-36

7.2.10 Bus parameter setting (SetValue: Server)...............................................................................................7-38

8. TROUBLESHOOTING 8-1 to 8-11

8.1 Troubleshooting..................................................................................................................................................8- 1

8.2 Error Code ..........................................................................................................................................................8- 2

8.2.1 Answer area, receive area.......................................................................................................................8- 2

8.2.2 Communication circuits ...........................................................................................................................8- 8

APPENDIX A-1 to A-12

Appendix 1 Differences From the AJ71PB96............................................................................................................A- 1

Appendix 2 Dissimilarities Between A1SJ71PB96F New Products (Software Version C or Later)

and Conventional Products (Software Version B or Before)..................................................................A- 4

2.1 Dissimilarities Between A1SJ71PB96F New Products (Software Version C or Later)

and Conventional Products (Software Version B or Before)...........................................................A- 4

2.2 Precautionary Notes when Using an A1SJ71PB96F New Product (Software Version C or Later)

and a Conventional Product (Software Version B or Later) Simultaneously...................................A- 6

Appendix 3 VDF Physical Status Criteria Table........................................................................................................A- 7

Appendix 4 DIN 19245 Part 2....................................................................................................................................A- 8

Appendix 5 Maximum Service Counter.....................................................................................................................A-10

Appendix 6 External Dimensions ..............................................................................................................................A-11

Page 10

About This Manual

The following are manuals related to this product. Request for the manuals as needed according to the chart below.

Related Manual

Manual Name Manual No.

(Model code)

Type SW0IX-PROFPE Operating Manual IB-66772

(13JL20)

Page 11

1. OVERVIEW MELSEC-A

1-1

1. OVERVIEW

This manual explains the specifications, handling and communication services for type

AJ71PB96F/A1SJ71PB96F PROFIBUS-FMS interface module (hereafter abbreviated as

AJ71PB96F/A1SJ71PB96F, when explain separately, however, abbreviated as AJ71PB96F,

A1SJ71PB96F.) for connecting the A Series PC to the PROFIBUS-FMS network.

The AJ71PB96F/A1SJ71PB96F operates as the master station in the PROFIBUS-FMS network and

communicates with slave stations or other master stations.

1.1 Software Configuration

The AJ71PB96F/A1SJ71PB96F contains a Physical layer, Datalink layer, Application layer, and VFD

(Virtual Field Device) that comply with PROFIBUS-FMS and conducts data communication with the PC

CPU using a general data interface and buffer memory.

The software configuration is shown in the following diagram.

FROM/TO

VFD

FMS

FDL

PHY

FMA7

empty

FMA1/2

A Series PC

General

data

interface

Communication using

buffer memory

PC CPU device

read/write

communication

7th layer: Application

3rd layer to 6 th layer

2nd layer: Datalink laye 1st layer: Physical layer

Table 1.1 Software configuration

*FMS, LLI, FDL, PHY, FMA7, FMA1/2...PROFIBUS Protocol

Page 12

1. OVERVIEW MELSEC-A

1-2

1.2 AJ71PB96F/A1SJ71PB96F Characteristics

The AJ71PB96F/A1SJ71PB96F general characteristics are explained below.

(1) Operates as a client or server in the PROFUBUS-FMS network.

(a) When operating as a client:

•

The partner station variable can be read/written using the I/O signal X/Y and buffer memory.

•

The partner station status and ID information can be read using the I/O signal X/Y and the buffer memory.

•

The non-confirmation type service can be transmitted using the I/O signal X/Y and the buffer memory.

(b) When operating as a server:

•

The PC CPU device can be read/written to from the client. (without sequence program)

•

The sequence program, parameters, comments, device memory, and buffer memory can be uploaded/downloaded from the client. (without sequence program)

•

The sequence program can be run, stopped, or paused from the client. (without sequence program)

•

The non-confirmation type service can be received using the I/O signal X/Y and the buffer memory.

The service that can actually be used depends on the connection type and partner station installed service, etc. For details refer to Item 4-4.

(2) Operates as a master station in the PROFIBUS-FMS network.

In addition, the same operation as that of a slave station can be done using slave emulation.

(3) When used in combination with MELSECNET (II), MELSECNET/B or MELSECNET/10 the

client can access from the MELSECNET (II), MELSECNET/B or MELSECNET/10 station. For details refer to Item 2.3.2

(4) The client can read/set the OD (Object Dictionary), CRL (Connection Relationship List), and

bus parameter via the PROFIBUS-FMS network.

(5) The utility software package SW0IX-PROFPE is used when the OD, CRL, and bus

parameters are set in the AJ71PB96F/A1SJ71PB96F.

SW0IX-PROFPF

RS-232

AJ71PB96F/ A1SJ71PB96F

Operation management terminal IBM PC/AT or 100% compatible

PROFIBUS-FMS network

Utility Software Package

(Software version B or later)

Table 1.2 System configuration example

Page 13

2. SYSTEM CONFIGURATION MELSEC-A

2-1

2. SYSTEM CONFIGURATION

This section explains system configuration for the AJ71PB96F/A1SJ71PB96F.

2.1 Whole System Configuration

(1) For the A1SJCPU

A1SJCPU (S3)

Extension cable

Extension base

A1SJ71PB96F

A1SC[ ]B

A1S6[ ]B(S1)/A1S5[ ]B(S1

A1SJHCPU

(2) For the compact building block type CPU

Compact building block type CPU

Extension cable

A1SC[ ]B

Extension bas

Basic base

A1SJ71PB96F

A1S6[ ]B(S1)/A1S5[ ]B(S1)

A1S3[ ]B/A1S38HB

Page 14

2. SYSTEM CONFIGURATION MELSEC-A

2-2

(3) For the building block type CPU(A Series)

Building block type CPU

Extension cable

AC[ ]B

Extension bas

Basic base

AJ71PB96

A6[ ]B/A5[ ]B

A3[ ]B/A38HB

(4) Peripheral equipment configuration

AJ71PB96F/ A1SJ71PB96F

Connection cable *1

IBM PC/AT or 100% compatible

Utility software package

SW0IX-PROFPE

1 2 3 4 5 6 7 8 9

DCD RD SD DTR SG DSR RTS CTS RI

FG RD SD DTR SG DSR RTS CTS RI

IBM PC/AT RS-232

(9 pin)

AJ71PB96F/ A1SJ71PB96F RS-232C

(9 pin)

*1 Provided by the user

Pin assignment

(Software version B or later

Page 15

2. SYSTEM CONFIGURATION MELSEC-A

2-3

2.2 Applicable CPU Modules

The following table shows the CPUs that the AJ71PB96F/A1SJ71PB96F can use and the number that

can be installed.

(1) AJ71PB96F

Applicable CPU Modules Installable Number Remarks

A1SCPUC24-R2 1 *2 A1SJCPU, A1SJCPU-S3, A1SCPU, A1SCPU-S1, A2SCPU, A2SCPU-S1, A1SJHCPU, A1SHCPU, A2SHCPU, A2SHCPU-S1, A1NCPU, A1NCPU P21/R21, A2NCPU, A2NCPU P21/R21, A2NCPU-S1, A2NCPU P21/R21-S1, A3NCPU, A3NCPU P21/R21

A2ASCPU, A2ASCPU-S1, A2ASCPU-S30, A2ACPU, A2ACPU P21/R21, A2ACPU-S1, A2ACPU P21/R21-S1, A3ACPU, A3ACPU P21/R21, A2UCPU, A2UCPU-S1, A3UCPU, A4UCPU

Q2ASCPU, Q2ASCPU-S1, *1 Q2ASHCPU, Q2ASHCPU-S1 Q2ACPU, Q2ACPU-S1, Q3ACPU, Q4ACPU, Q4ARCPU

(2) A1SJ71PB96F

Applicable CPU Modules Installable Number Remarks

A1SCPUC24-R2 1 *2 A1SJCPU, A1SJCPU-S3, A1SCPU, A1SCPU-S1, A2SCPU, A2SCPU-S1, A1SJHCPU, A1SHCPU, A2SHCPU, A2SHCPU-S1

A2ASCPU, A2ASCPU-S1, A2ASCPU-S30

Q2ASCPU, Q2ASCPU-S1, *1 Q2ASHCPU, Q2ASHCPU-S1

*1: The accessible range is the A2ACPU/A3ACPU range.

Also, it is impossible to access to the file register R.

*2: When used with the special function modules (including the previous models such as the computer

link module, Ethernet module, etc.) the total installable number of modules will include the number of these modules used.

•

A1SJ71UC24-R2 (R4/PRF)

•

A1SJ71E71-B2-S3 (-B5-S3)

•

A1SD51S

•

A1SD21-S1

•

A1SJ61BT11: Only during intelligent mode

•

AJ71UC24

•

AJ71E71-S3

•

AD51H-S3

•

AD51-S3

•

AD51FD-S3

•

AD57G-S3

•

A870GOT, A850GOT, A810GOT, A975GOT, A970GOT, A960GOT : Only when connected to bus

•

A851GOT

•

AJ71C21-S1: Only during the basic program mode

•

AD22-S1

•

AJ61BT11: Only during intelligent mode • AJ71C23-S3

However, when the computer link module (A1SJ71UC24-R2, etc.) is used as a multiple drop link module, there is no limit to the above number of installable modules. Multiple modules can be installed within the number of I/O points in the PC CPU.

Page 16

2. SYSTEM CONFIGURATION MELSEC-A

2-4

2.3 System Configuration Precaution Items

2.3.1 Installable base units

The base modules that can be installed in the AJ71PB96F/A1SJ71PB96F are shown below.

(1) AJ71PB96F

Installable Base Units

Basic base unit Extension base unit A32B, A32B-S1, A35B, A38B, A38HB A52B, A55B, A58B, A62B, A65B, A68B

(2) A1SJ71PB96F

Installable Base Units

Basic base unit Extension base unit *1 A1S32B, A1S33B, A1S35B, A1S38B,

A1S38HB

A1S52B (S1), A1S55B (S1), A1S58B (S1), A1S65B (S1), A1S68B (S1)

*1: The no power supply module extension base unit A1S5 [ ] B (S1) may not have sufficient power

supply capacity, so use the A1S6 [ ] B (S1) when installing a A1SJ71PB96F in the extension base unit. When the A1S5 [ ] B (S1) must be installed, do so after referring to the chapter covering power supplies in the respective CPU Module User’s Manual.

Page 17

2. SYSTEM CONFIGURATION MELSEC-A

2-5

2.3.2 Combining with the MELSECNET (II), MELSECNET/B, or MELSECNET/10

Point

The AJ71PB96F/A1SJ71PB96F cannot be installed in a remote I/O station.

(1) For the MELSECNET (II) or MELSECNET/B

Installing the AJ71PB96F/A1SJ71PB96F in the PC CPU connected to the data link system makes it possible to read/write the other station PC CPU devices on MELSECNET (II) or MELSECNET/B from the PROFIBUS other station. However, PROFIBUS communication requests from the other station PC CPU on the MELSECNET (II) or MELSECNET/B cannot be transmitted. In addition, the A0J2CPUP23/R23 or A0J2P25/R25 cannot be accessed.

Master station (M)

Remote 2 station (r2)

Remote 3 station (R3)

Local 1 station (L1)

NET (II)

PROFIBUS other station

Local 2 station/3rd layer

master station (L2/m)

Local 3 station (l3)

Local 1 station (l1)

NET (II)

PROFIBUS other station

Stations that can be installed: Master and local stations. Cannot be installed in the remote I/O station.

Installable Stations accessible from the PROFIBUS other stations

stations

M L1 L2/m R3 l1 r2 l3



 

× × ×

L2/m



×



×



× ×



×



: Access is possible to all devices of the specified CPU.

: Access is not possible to the specified CPU.



: Access is possible from the special function module buffer memory.

Page 18

2. SYSTEM CONFIGURATION MELSEC-A

2-6

(2) MELSECNET/10 (for networks between PCs)

(a) MELSECNET/10 two-layer system

PROFIBUS other station1Mp1

PROFIBUS other station

1N3

1Ns2

1Ns4

NET/10 (No.1)

Mp : NET/10 control station Ns : NET/10 normal station (AnUCPU, A2ASCPU) N : NET/10 normal station (CPU other than

AnU/A2AS) M : NET (II) master station L : NET (II) local station R : Remote station

Stations accessible from the

PROFIBUS other stations

1Mp1 1Ns2 1N3 1Ns4

1Mp1 



1N3



×



×

1Ns4

   

(b) MELSECNET/10 multiple-layer station

PROFIBUS other station

1Mp11N2

1Ns4

NET/10 (No.1)

PROFIBUS other station

2N2

PROFIBUS other station

2Ns32Ns4

NET/10 (No.2)

1Ns3 2Mp1

Stations accessible from the PROFIBUS other stations

1Mp1 1N2

1Ns3/ 2Mp1

1Ns4 2N2 2Ns3 2Ns4

1Mp1 



1N2

 



1Ns3/2Mp1

      

2N2











2Ns3

      

Installable

stations

Installable

stations

Page 19

2. SYSTEM CONFIGURATION MELSEC-A

2-7

•

When the intermediate terminal is an AnUCPU/A2ASCPU

PROFIBUS other station1Ns1

1Ns3

1N2

1Mp4

NET/10 (No.1) PROFIBUS other station

PROFIBUS other station

PROFIBUS other statio

NET (II)

Stations accessible from the PROFIBUS other stations

1Ns1 1N2

1Ns3/

1Mp4 L1 L2 R3

1Ns1 



1Ns3/M

    



1Mp4

   









•

When the intermediate station is other than an AnUCPU/A2ASCPU

PROFIBUS other station1Mp1

1N3

1Ns2

1Ns4

NET/10 (No.1) PROFIBUS other station

PROFIBUS other station

PROFIBUS other statio

NET (II)

Stations accessible from the PROFIBUS other stations

1Mp1 1Ns2

1N3/

1Ns4 L1 L2 R3

1Mp1 



1N3/M









 



1Ns4

   









Installable

stations

Installable

stations

Page 20

2. SYSTEM CONFIGURATION MELSEC-A

2-8

(3) MELSECNET/10 (for remote I/O networks)

(a) MELSECNET/10 two-layer system

PROFIBUS other station1Mr

1R1

1R3

1R2

NET/10 (No.1)

Mp : NET/10 control station Ns : NET/10 normal station (AnUCPU, A2ASCPU) N : NET/10 normal station (CPU other than

AnU/A2AS) Mr : NET/10 remote I/O master M : NET (II) master station L : NET (II) local station R : Remote station

Stations accessible from the

PROFIBUS other stations

1Mr 1R1 1R2 1R3

1Mr 



(b) MELSECNET/10 multiple-layer system

PROFIBUS other station

1Mp11N2

1Ns4

NET/10 (No.1

PROFIBUS other station

2R1

2R22R3

NET/10 (No.2

1Ns3 2Mr

Stations accessible from the PROFIBUS other stations

1Mp1 1N2

1Ns3/

2Mr

1Ns4 2R1 2R2 2R3

1Mp1 



1N2

 



1Ns3/2Mr

      

Installable

stations

Installable

stations

Page 21

2. SYSTEM CONFIGURATION MELSEC-A

2-9

•

When the intermediate station is an AnUCPU/A2ASCPU

PROFIBUS other station1Ns1

1Ns3

1N2

1Mp4

NET/10 (No.1)

2R1

2R2

NET/10 (No.2)

PROFIBUS other station

M2Mr

NET (II)

Stations accessible from the PROFIBUS other stations

1Ns1 1N2

1Ns3/ M 1Mp4/

2Mr

2R1 2R2 L1 L2 R3

1Ns1 



 

1Ns3/M

      



1Mp4/2Mr

     









Installable

stations

Page 22

2. SYSTEM CONFIGURATION MELSEC-A

2-10

•

When the intermediate station is other than the AnUCPU/A2ASCPU

PROFIBUS other station1Ns1

1N3

1N2

1Mp4

NET/10 (No.1)

2R1

2R2

NET/10 (No.2)

PROFIBUS other station

M2Mr

NET (II)

Stations accessible from the PROFIBUS other stations

1Ns1 1N2

1N3/ M 1Mp4/

2Mr

2R1 2R2 L1 L2 R3

1Ns1 



 

1Ns3/M











1Mp4/2Mr

     









Installable

stations

Page 23

3. SPECIFICATIONS MELSEC-A

3-1

3. SPECIFICATIONS

This section explains the AJ71PB96F/A1SJ71PB96F the general specifications, performance specifications, and transmission specifications.

3.1 General Specification

This section explains the AJ71PB96F/A1SJ71PB96F general specifications.

Table 3.1 General Specification

Item Specifications

Ambient operating temperature

0 to 55

Ambient storage temperature -20 to 75°C Ambient operating humidity 10 to 90%RH, Non-condensing Ambient storage humidity 10 to 90%RH, Non-condensing Frequency Acceleration Amplitude No. of sweeps

10 to 57Hz —

0.075mm

(0.003inch)

Vibration resistance 57 to 150Hz 9.8m/s2 {1G} —

10 to 57Hz —

0.035mm

(0.001inch)

57 to 150Hz 4.9m/s2 {0.5G} — Shock resistance

Conforming to JIS B3501, IEC 1131-2

(147m/s2 {15G}, 3 times in each of 3 directions X Y Z) Operating ambience No corrosive gases Operating elevation 2000m (6562 feet) max. Installation location Control panel Over voltage category

II max.

Pollution level

2 max.

*1: This indicates the section of the power supply to which the equipment is assumed to be

connected between the public electrical power distribution network and the machinery within the premises. Category II applies to equipment for which electrical power is supplied from fixed facilities. The surge voltage withstand level for up to the rated voltage of 300V is 2500V.

*2: This index indicates the degree to which conductive material is generated in terms of the

environment in which the equipment is used. Pollution level 2 is when only non-conductive pollution occurs. A temporary conductivity caused by condensation must be expected occasionally.

10 times each in

X, Y, Z directions

(for 80 min.)

Conforming to

JIS B3501,

IEC 1131-2

Under intermittent vibration

Under continuous vibration

Page 24

3. SPECIFICATIONS MELSEC-A

3-2

3.2 Performance Specifications

This section explains performance specifications for the AJ71PB96F/A1SJ71PB96F.

Table 3.2 Performance Specifications

Item Specifications

Model AJ71PB96F A1SJ71PB96F Transmission speed 9.6, 19.2, 93.75, 187.5, 500, 1500kbps Coding method NRZ Synchronization method Asynchronous Electrical standards and characteristics EIA-RS485 compliance Medium Shield twisted cable Network configuration (topology) Bus type (However, tree type when a repeater is used)

Transmission

9.6kbps

19.2kbps

93.75kbps

1200m (3937ft.)

distance 187.5kbps 600m (1969ft.) 500kbps 200m (656ft.) 1500kbps 100m (328ft.) Number of connection nodes 32, 62 (1 repeater), 9 (2 repeaters), 122 (3 repeaters) Number of repeaters/network *1 3 repeaters (max)

Data link method

Token passing (between master-master), polling (between

master-slave) Transmittable data 241 bytes (max)/1 time Number of occupied I/O points 32 points (I/O allocation: special 32 points) 5VDC internal power consumption (A) 0.54 0.56

Withstand noise, withstand voltage, insulation resistance

According to the power supply module specifications of

the system in which the AJ71PB96F/A1SJ71PB96F will be

installed. (Refer to the CPU module's users manual.)

External dimensions (mm)

250 (9.84in.) (H) ×

37.5 (1.48in.) (W)

106 (4.17in.) (D)

130 (5.12in.) (H) ×

34.5 (1.36in.) (W)

97.6 (3.84in.) (D)

Weight (kg) 0.37(0.81lb) 0.27 (0.59lb)

*1 The transmission distance (m/network) can be extended by using a repeater.

Transmission distance (m/network) = (number of repeaters + 1) × transmission distance (m/segment)

Page 25

3. SPECIFICATIONS MELSEC-A

3-3

*2 Transmission line

Items Specifications Remarks

PROFIBUS cable impedance

Capacity Conductor resistance Conductor cross section area

Twisted pair cable 100 to 120

Ω

(>100kHz) <60nF/km <160

Ω

/km

>0.22mm

User distribution

Terminal resistance

390

Ω

150

Ω

390

Ω

VP (6)

RxD/TxD-N (8)

RxD/TxD-P (3)

DGND (5)

Set yes/no by the main module switch

Page 26

3. SPECIFICATIONS MELSEC-A

3-4

3.3 Installation Specifications

This section explains installation specifications for the AJ71PB96F/A1SJ71PB96F.

Table 3.3 Installation Specifications

OSI layer name PROFIBUS protocol Compliance standards

Application layer FMS, LLI, FMA7 PROFIBUS proprietary (DIN19245) Presentation layer



Session layer



Transport layer



Network layer



Data link layer FDL

FMA1/2

PROFIBUS proprietary (DIN19245)

Physical layer PHY RS-485

PROFIBUS proprietary (DIN19245)

Page 27

4. FUNCTIONS MELSEC-A

4-1

4. FUNCTIONS

4.1 Positioning in the PROFIBUS-FMS Network

The AJ71PB96F/A1SJ71PB96F in PROFIBUS-FMS network is positioned to the following.

(1) The AJ71PB96F/A1SJ71PB96F operates as a master station in the PROFIBUS-FMS

network.

(2) The AJ71PB96F/A1SJ71PB96F contains both client and server functions.

4.2 Bus Parameters

The bus parameters are the communication parameters prescribed for the PROFIBUS protocol No. 2 layer operation. Bus parameters are set using the SW0IX-PROFPE. The bus parameter rangers and default values that can be set in AJ71PB96F/A1SJ71PB96F are shown below.

Table 4.1 Bus Parameters Setting Items

Item Unit Setting range Default value

Local address 0 to 126 0 Baud rate 9.6, 19.2, 93.75, 187.5, 500, 1500kbps 9.6kbps Slot time Bit Time 37 to 16383 100 Min Tsdr Bit Time 11 to 1023 30 Max Tsdr Bit Time 37 to 65535 50 Quiet Time Bit Time 0 to 127 22 Setup Time Bit Time 1 to 255 5 Target Rotation Time Bit Time 256 to 16777215 10000 GAP Update Factor 1 to 100 1 Has 1 to 126 126 Max Retry Limit 0 to 7 1

Remark

Following is an explanation of the terminology used for bus parameters.

Tsdr: Station Delay Time as Responder Bit Time: The time required to transmit 1 bit = 1/baud rate Slot Time: The maximum time that the requester must wait for a response from the

responder. Max Tsdr < Slot Time

Min Tsdr: The minimum time required for the responder to respond.

Quiet Time < Min Tsdr, Setup Time < Min Tsdr Max Tsdr: The maximum time required for the responder to respond. Quiet Time: The time required for the repeater to switch from the transmission mode to the

receive mode. Setup Time: The time required for the requester to switch from the transmission mode to

the receive mode. Target Rotation Time: If the actual token rotation time becomes larger than this time, cyclic

communication will no longer be possible. GAP Update Factor: This shows how many times the station information can be updated for 1 token

rotation.

Station information update interval = G x Target Rotation Time HSA: Highest Station Address. The highest address of the stations connected to the

network. Max Retry Limit: The maximum number of transmission retries when data transmission fails.

Page 28

4. FUNCTIONS MELSEC-A

4-2

4.3 Communication Relationship

In PROFIBUS, all of the connection information must be written in CRL (Communication Relationship List) as communication relationships (hereafter abbreviated as communication). Communication contains connection oriented communication that is required for establishing logical circuits before communication and connection less list communication that does not have data communication certainty when establishing logical circuits before communication is not required. In addition, it also contains FMS communication and FMA7 communications.

The following communication types are prescribed for FMS communication.

MMAC (Master to Master Acyclic Connection) MSAC (Master to Slave Acyclic Connection) MSAC_SI (Master to Slave Acyclic Connection/Slave Initiative) MSCY (Master to Slave Cyclic Connection) MSCY_SI (Master to Slave Cyclic Connection/Slave Initiative) BRCT (Broadcast) MULT (Multicast)

In addition, the communications other than BRCT and MULT have the following attributes:

/D : Defined connection /I : Request open connection /O : Responder open connection

However, MSxx's /O connections are not allowed. (PROFIBUS standard) Of these, BRCT and MULT are connectionless communications and the others are connection oriented communications.

All FMA7 communications are connection oriented. In AJ71PB96F/A1SJ71PB96F, the above all communications are enable to use by using the software

package. In AJ71PB96F/A1SJ71PB96F, when the following conditions are met the maximum number of

communications including FMA7 communications can be set to 32. In other cases the maximum number of communications that can be set is 16.

(1) Communication type conditions

Communications are divided into the following two types.

Category I

MMAC (Master to Master Acyclic Connection) MSAC (Master to Slave Acyclic Connection) MSCA_SI (Master to Slave Acyclic Connection/Slave Initiative) SMA7 communication

Category II

MSCY (Master to Slave Cyclic Communication) MSCY_SI (Master to Slave Cyclic Communication/Slave Initiative) BRCT (Broadcast) MULT (Multicast)

The number of communications must satisfy the following formula. Category I number of communications × 2 + Category II number of communications ≤ 32

(2) PDU size conditions

All of the PDU sizes for all communications shall be 200 or less.

Page 29

4. FUNCTIONS MELSEC-A

4-3

4.3.1 CRL Setting Items and Default Values

The CRL setting items are shown below. At the time of shipment the default is set to 16 MMAC/O connections.

Table 4.2 CRL Setting Items

Item Setting range Default value

CREF 1 to 33 2 to 17 Symbol Connection name (32 characters) Connection_01 to

Connection_16 Password 0 to 255 0 Access Group 0 to 255 0 Local LSAP (SSAP) 0 to 60, 63, 128 2 to 17 Remote Address 0 to 127, 255 255 (ALL) Remote LSAP (DSAP) 0, 2 to 63, 128, 255 255 (ALL) Connection Type MMAC, MSAC, MSAC_SI, MSCY,

MSCY_SI, BRCT, MULT

MMAC

Connection Attribute /D, /I, /0 /0 Control Interval 0 to 4294967294 4096 Max SCC 0 to 1 1 Max RCC 0 to 2 2 Max SAC 0 to 1 1 Max RAC 0 to 1 1 Max send PDU (H) 0 to 241 241 Max send PDU (L) 0 to 241 241 Max receive PDU (H) 0 to 241 241 Max receive PDU (L) 0 to 241 241 Features Supported 00 00 00 00 00 00 to

FF FF FF FF FF FF

00 30 00 F9 B0 81

The default connection contains the following restriction items. (1) Connection establishment requests are only output from communication partner stations. (2) Communication is only possible with stations that do not support access protection. (3) Only for MMAC. (4) The only services that can be output by the PC are read and write.

For other cases the setting must be conducted using the SW0IX-PROFPE.

Page 30

4. FUNCTIONS MELSEC-A

4-4

Remark

Following is an explanation of the terminology used with CRL. (a) Connection Type

•

MMAC: Master to Master Acyclic Connection. Service requests can be sent from both stations.

•

MSAC: Master to Slave Acyclic Connection. Service requests can only be sent from the master station.

•

MSAC_SI: Master to Slave Acyclic Connection. (Service requests can be sent from the slave station.) In addition to the MSAC communication format InformationReport and UnsolicitedStatus can be sent from the slave station.

•

MSCY: Master to Slave Cyclic Connection. Service requests can only be sent from the master station.

•

MSCY_SI: Master to Slave Cyclic Connection: (Service requests can also be made from the slave station.) In addition to the MSCY communication format InformationReport and UnsolicitedStatus can be sent from the slave station.

•

BRCT: Broadcast communication (connectionless). InformationReport and UnsolicitedStatus can be sent from master stations to all stations.

•

MULT: Multicast communication (connectionless). InformationReport and UnsolicitedStatus can be sent to multiple stations within a certain group. The group consists of stations with the same Remote LSAP.

(b) Connection Attribute

•

/D: Define Connection. This attribute securely fixes the connection partner.

•

/I: Requester Open Connection. When establishing a connection multiple partner stations are connected to the LSAP of the receiving side. (However, the connections are not made at the same time.)

•

/O: Responder Open Connection. When establishing a connection multiple partner stations are connected to the LSAP of the receiving side. (However, the connections are not made at the same time.)

to which the connection is established is monitored to see if it is operating correctly.

(d) Max SCC: Max Send Confirmed request Counter. The number of maximum confirmed

services that can be sent by the confirmed service request side (client) before the response to the previously sent service is received.

(e) Max RCC: Max Receive Confirmed request Counter. The number of maximum confirmed

services that can be received by the confirmed service request reception side (server) before the previously sent service is returned.

(f) Max SAC: Max Send Acknowledged request Counter. This is the number of unconfirmed

services that can be sent by the unconfirmed service request sending side before the ACK of the previously sent service is received.

(g) Max RAC: Max Received Acknowledged request Counter. This is the number of

unconfirmed services that can be received by the unconfirmed services receiving side before the response to the previously sent service is returned.

(h) Max send PDU(H): This is the maximum size of a packet sent by high priority. Acyclic

communication data is sent by high priority.

Page 31

4. FUNCTIONS MELSEC-A

4-5

(i) Max send PDU(L): This is the maximum size of a packet sent by low priority. Cyclic

communication data is sent by low priority.

(j) Max Receive PDU(H): This is the maximum size of a packet received by high priority. Acyclic

communication data is received at high priority.

(k) Max Receive PDU(L): This is the maximum size of a packet received at low priority. Cyclic

communications are received at low priority.

(l) Features Supported: This shows whether or not each bit supports a service.

Page 32

4. FUNCTIONS MELSEC-A

4-6

4.4 Support Service

4.4.1 FMS remote service

Symbol meanings

C: Contains client functions

For confirmed service, has the capability to transmit request primitives and receive confirmation primitives. For unconfirmed service, has the capability of transmitting request primitives.

S: Contains server functions

For confirmed service, has the capability to receive instruction primitives and to transmit answer primitives.

For unconfirmed service, has the capability of receiving instruction primitives. B: Has functions as both client and server. x: Not supported

-: No combination

Communication MMAC/D MMAC/I MMAC/O MSAC/D MSAC/O

type

Service

Master Slave

emulation

Master Slave

emulation

Initiate Abort Reject Status UnsolicitedStatus Identify Get0D (short form) Get0D (long form) InitiatePut0D Put0D TerminatePut0D InitiateDownloadSequence DownloadSegment TerminateDownloadSequence RequestDomainDownload InitiateUploadSequence UploadSegment TerminateUploadSequence RequestDomainUpload CreateProgramInvocation DeleteProgramInvocation Start Stop Resume Reset Kill Read Write ReadWithType WriteWithType PhysRead PhysWrite InformationReport InformationReportWithType DefineVariableList DeleteVariableList EventNotification EventNotificationWithType AcknowledgeEventNotification AlterEventConditionMonitoring

B B S B B B B B S S S S C C X S S S X S S S S S S X B B X X X X B X X X X X X X

B S B B B B B S S S

S C C

S B S B B B B B S S S S C C X S S S X S S S S S S X B B X X X X B X X X X X X X

C B S C C C C C X X X X X X X X X X X X X X X X X X C C X X X X C X X X X X X X

S B S S S S S S S S S X X X X S S S X S S S S S S X S S X X X X S X X X X X X X

                                       

S B S S S S S S S S S X X X X S S S X S S S S S S X S S X X X X S X X X X X X X

Page 33

4. FUNCTIONS MELSEC-A

4-7

Communication MSAC_SI/D MSAC_SI/O MSCY/D

MSCY/O

type

Service

Master Slave

emulation

Master Slave

emulation

Master Slave

emulation

Master Slave

emulation

C B S C B C C C X X X X X X X X X X X X X X X X X X C C X X X X B X X X X X X X

S B S S B S S S S S S X X X X S S S X S S S S S S X S S X X X X B X X X X X X X

                                       

S B S S B S S S S S S X X X X S S S X S S S S S S X S S X X X X B X X X X X X X

C B S



                    

C C

   

      

S B S



                    

S S

   

      

                                       

S B S



                    

S S

   

      

Page 34

4. FUNCTIONS MELSEC-A

4-8

Communication

type

MSCY_SI/D MSCY_SI/O BRCT/

MULT

Service

Master Slave

emulation

Master Slave

emulation

C B S



                    

C C

   

      



                    

   

      

                                       

S B S



                    

S S

   

      

 



                          

      

Page 35

4. FUNCTIONS MELSEC-A

4-9

4.4.2 FMA7 remote service

Symbol meanings

C: Contains client functions

For confirmed service, has the capability to transmit request primitives and receive confirmation primitives. For unconfirmed service, has the capability of transmitting request primitives.

S: Contains survey functions

For confirmed service, has the capability to receive instruction primitives and to transmit answer primitives.

For unconfirmed service, has the capability of receiving instruction primitives. B: Has functions as both client and server. X: Not supported

Service Supported

FMA7_Initiate FMA7_Abort FMA7_Read_KBL_rem FMA7_Init_load_KBL_rem FMA7_Load_KBL_rem FMA7_Term_load_KBL_rem FMA7_Set_value_rem FMA7_Read_value_rem FMA7_LSAP_Status_rem FMA7_Indent_rem

S B S S S S S S X X

Page 36

4. FUNCTIONS MELSEC-A

4-10

4.5 Object Dictionary (OD)

In PROFIBUS, a communication target on the side of the server accessed from the client is called an object, and the server must have a table called an object dictionary in which the object attribute information is recorded. The OD on the server side is called the local OD. The client reads the server OD via communication and retains a copy and then conducts communication while referring to the read copy. The copy retained by the client is called the remote OD.

4.5.1 Local OD

In the AJ71PB96F/A1SJ71PB96F the memory areas shown in the table below can be registered in the local OD as objects. Setting is done by using the software package (excluding Program Invocation).

(1) AJ71PB96F/A1SJ71PB96F objects

Object type Object Number of

objects

registered

Supporting PC

ST-0D (Static Type 0D)

Structured data type 32 None (AJ71PB96F/A1SJ71PB96F internal

information)

S-0D (Static 0D)

Simple variable array number of records

Maximum 128

Device memory, buffer memory (However, buffer memory cannot be allotted to the record variable.)

Parameter domain

Main sequence domain Subsequence domain Main microcomputer domain Submicrocomputer domain Comment domain Expansion comment domain Device memory domain Buffer memory domain

Parameter

Main sequence program Subsequence program Main microcomputer program Submicrocomputer program Comment Expansion comment Device memory Buffer memory

DP-0D (Dynamic PI 0D)

Program Invocation (PI) *1 Maximum 32 Main sequence program

*1: Can only be set via a communication from the client.

Page 37

4. FUNCTIONS MELSEC-A

4-11

(2) Variables and data types

The following shows the relationship between the variables and data types that can be used by the AJ71PB96F/A1SJ71PB96F local OD and the device memory.

Simple variable Array variable Record variable Bit device Word device Bit device Word device Bit device Word device

Boolean Integer8 Integer16 Integer32 Unsigned8 Unsigned16 Unsigned32 Float VisibleStr OcteStr Date TimeOfDay TimeDiff BitStr



× × × × × × × × × × × ×





× × × ×



× × × × × × × × × × × ×





× × × ×



× × × × × × × × × × × × ×

× ×



× ×



× × × × × × × ×

*1: Maximum 128 bytes (1024 bits) *2: Maximum 64 words *3: Maximum 128 elements *4: Maximum 64 elements *5: Maximum 32 elements *6: 1 element byte length x Number of elements <= 128 bytes, and 1 element is 128 bytes or

less

*7: Maximum 10 elements

(3) Objects mapping data

Because the objects and PC memory area mapping shown above is set by the AJ71PB96F/ A1SJ71PB96F, the following items must be set by the software package.

(a) Structured data types

•

Index No

•

Number of elements

•

(Data type, data length) Maximum 10 unit combinations

(b) Simple variable

•

Index No.

•

Variable name

•

Data type

•

Network No.

•

PC No.

Head device

For device:

•

Device name

•

Device number

For buffer memory:

•

Y No.

•

Buffer memory address

•

Index No.

•

Variable name

•

Data type

•

Network No

•

PC No.

•

Number of elements Head device

For device:

•

Device name

•

Device number

For buffer memory:

•

Y No.

•

Buffer memory address

(d) Record variable

•

Index No.

•

Index name

•

Structured data type INDEX • Network No.

•

PC No. Head device

For device:

•

(Device name, device number) Maximum 10 unit combination

For buffer memory:

•

(Cannot be used)

(e) Domain

•

Index No.

•

Domain name

•

Network No.

•

PC No.

•

Domain type (program, parameter, ...)

•

Data length

Head device

For device:

•

Device name

•

Device number

For buffer memory:

•

Y No.

•

Buffer memory address

Page 38

4. FUNCTIONS MELSEC-A

4-12

The following symbols are used for the above device names.

Device

symbol

Device name Device

symbol

Device name

X Y L M

F TT TC CT

D SD

Input Output Latch relay Internal relay Special relay Annunciator Timer contact Timer coil Counter contact Counter coil Timer current value Counter current value Data register Special register

TS CM CS

Z V R B W

48R

Timer setting value (main) Timer setting value (sub) Counter setting value (main) Counter setting value (sub) Accumulator Index register Index register File register Link relay Link register Expansion file register No. 1 to Expansion file register No. 48

In addition, the variable name and the domain name length are 32 bytes (fixed), and any portion that used up to 32 bytes is filled with spaces. The symbols that can be used are as follows: _, 0 to 9, A to Z, a to z,!@#$%^&*()_+|-= []{}:;” ’`-<>?,./

(4) Specifies objects to be accessed

The data mentioned in (3) is set in the local OD, but when it will be used by a domain or in accessing the MELSECNET/10 other terminal, the following data is stored in the expansion address table.

•

Network No.

•

PC No.

•

Domain type

•

Device name

•

Device number

•

Y No.

•

Buffer memory address

The local OD abbreviation is shown below.

Page 39

4. FUNCTIONS MELSEC-A

4-13

Local OD abbreviations

INDEX Object type Object dependent data

Name (32 characters)

Data structure (data type INDEX/length)

3 14 15

Data type Data type Data type Structured data type

Boolean Integer16 BitStr

------

(Boolean/1), (Interger16/2),........(Maximum 10 units)

Name (32 characters)

INDEX

Data length

Number of elements

Local address

100 101 102

Array variable Simple variable Record variable

counter1 counter2 Sensor1

1 3

1 2

---

---10

Local station/D100 NET10 other station Local station/X0, local station/D40, ...

Name (32 characters)

Data length

Local address

103 104

Domain Domain

mainP

12288 1024

Name (32

characters)

INDEX

500 PI program 1 103

The client uses either the object name registered in the local OD or the index No. (INDEX) uniquely assigned to each object to specify the object to be accessed. For the above example where a simple variable is accessed, either the access No. = 101 or the variable name = counter2 is specified.

Page 40

4. FUNCTIONS MELSEC-A

4-14

4.5.2 Local OD default setting

The array variables are set as shown below in the default local OD.

Index Number of registrations/1 array Data Type Registration device range

100 to 131 128 Boolean M0 to M4096 132 to 147 64 Unsigned16 TN0 to TN1023 148 to 155 64 Unsigned16 CN0 to CN511 156 to 203 64 Unsigned16 D0 to D3071 204 to 219 64 Unsigned16 TM0 to TM1,023 220 to 228 64 Unsigned16 CM0 to CM511

The default array variable names are added as shown below.

ccddddLeee

cc: Device name ("M" if the device name is M) dddd: Device No. eee: Number of elements Example: A 64 unit array starting at D100 is D100L64

Page 41

4. FUNCTIONS MELSEC-A

4-15

4.5.3 Remote OD

In the PROFIBUS the client reads the server local OD using the GetOD service and maintains this information in the local station to be used while communicating. This maintained information is called the remote OD.

(1) AJ71PB96F/A1SJ71PB96F remote OD management

The remote ODs managed by the AJ71PB96F/A1SJ71PB96F are divided into two types: Automatic management remote OD (hereafter automatic remote OD) and preload remote OD. In the AJ71PB96F/A1SJ71PB96F the remote OD is managed for each communication and a maximum of 26 remote ODs can be managed for one communication. However, this number is the total of the automatic remote ODs and preload remote ODs, and a maximum of 20 preload remote ODs can be set for one station. Preload remote ODs are set using the software package. Automatic remote ODs use vacant space in the preload remote ODs.

(a) Automatic remote OD

When the AJ71PB96F/A1SJ71PB96F issues a Read/Write service, if the specified variable remote OD is not stored in the AJ71PB96F/A1SJ71PB96F, the AJ71PB96F/A1SJ71PB96F automatically issues a GetOD to acquire the variable remote OD and this acquired remote OD is stored in the AJ71PB96F/A1SJ71PB96F.

Yes No

GetOD

Read/Write

AJ71PB96F

A1SJ71PB96F

Parther stationACPU

Request

End

OD header search

Yes

OD header

acquisition

OD header

storage

Variable OD search

Variable OD

acquisition

Variable OD

storage

Data type search

Data type acquisition

Data type

storage

Read/Write issued

Page 42

4. FUNCTIONS MELSEC-A

4-16

In the above diagram the OD header (OD Object Description) records the OD's own information.

If there is no vacant for the automatic remote OD when the remote OD is acquired, the automatic remote OD of past acquired automatic remote ODs with the lowest frequency of use is selected and overwritten. When a connection is canceled, all the automatic remote ODs acquired by the canceled connection are deleted.

(b) Preload remote OD

The AJ71PB96F/A1SJ71PB96F has a function for automatically acquiring the remote ODs, but depending on the conditions there are times when this function cannot be used. In such a case the remote OD must be stored in advance in the AJ71PB96F/A1SJ71PB96F using the SW0IX-PROFPE.

The preload remote OD must be set in the following cases.

(1) When operating as a client using the MSCY or MSCY_SI connection, the variable OD

Read/Write using this connection.

(2) The variable ODs for which there is a possibility of a notification from the partner

station using Information Report for all "/D" and "/I" connections.

Even if the connection is canceled, the preload remote ODs will not be deleted.

(2) Variables and data types

The following shows the relationship between the variables and data types that can be used by the AJ71PB96F/A1SJ71PB96F remote OD and the device memory. These can be thought of data that can be handled as a client by the AJ71PB96F/A1SJ71PB96F.

Simple variable Array variable Record variable

Boolean Integer8 Integer16 Integer32 Unsigned8 Unsigned16 Unsigned32 Float VisibleStr OcteStr Date TimeOfDay TimeDiff BitStr



× × ×











× × ×



*3 *



× × ×



*7 *

*1: Maximum 232 bytes (1856 bits) *2: Maximum 116 words *3: Maximum 232 elements *4: Maximum 116 elements *5: Maximum 58 elements *6: 1 element byte length x Number of elements ≤ 232 bytes, and 1 element is 232 bytes or less *7: Maximum 8 elements *8: Maximum 8 elements, however the total number of bytes is 232 bytes or less

Page 43

4. FUNCTIONS MELSEC-A

4-17

4.6 I/O Signal List

The configuration of the I/O signal to be used to receive and send data with AJ71PB96F/ A1SJ71PB96F and the PC CPU is shown below.

Signal direction: AJ71PB96F/A1SJ71PB96F

→→→→

PC CPU Signal direction: PC CPU

→→→→

AJ71PB96F/A1SJ71PB96F

Device No. Description Device No. Description

X00 X01 X02 X03

Request process end signal (Area No. 1) Request process end signal (Area No. 2) Request process end signal (Area No. 3) UCS receive signal (Receive only area)

Y00 Y01 Y02 Y03

Request request signal (Area No. 1) Request request signal (Area No. 2) Request request signal (Area No. 3)

UCS read end signal (Receive only area) X04 Network trouble signal Y04 Network trouble read out end signal X05

Y05

Y06

Usage prohibited because used by system

X0C

Usage not possible Y07

X0D PROFIBUS-FMS I/F WDT error signal Unused X0E

Y0F

Y10 Usage not possible Usage not possible Y11

Y19

Unused

X1A Y1A X1B

X1C X1D

PROFIBUS-FMS I/F communication Ready signal

PROFIBUS-FMS I/F error signal PROFIBUS-FMS I/F module Ready signal

Usage prohibited because used by the

system

X1E X1F

Usage not possible

Y1F

Remark

•

WDT: Watchdog timer

•

The Y unused area can be used in place of the internal relay M.

•

Refer to the PC CPU User’s Manual for information regarding the relationship between the I/O No. and slot.

•

UCS: Unconfirmed Service

(1) A request process end signal (X00 to X02) and the request request signal (Y00 to Y02) are

used as the handshake signals when the PC CPU matches PROFIBUS communication. Refer to the Section covering the usage method. X03 and Y03 are used as unconfirmed service receive only.

(2) PROFIBUS I/F communication Ready signal (X1B)

This is turned on when the AJ71PB96F/A1SJ71PB96F communication preparation ends. Program the PC CPU so that this signal turns on when PROFIBUS communication is conducted.

(3) PROFIBUS I/F error signal (X1C)

This turns on when the AJ71PB96F/A1SJ71PB96F detects an error.

…

……

…

……

…

……

…

……

…

……

…

Page 44

4. FUNCTIONS MELSEC-A

4-18

(4) PROFIBUS I/F module Ready signal (X1D)

This turns on when the AJ71PB96F/A1SJ71PB96F module preparation ends. When self diagnostics is set this signal turns on when there is a self diagnostic normal end. Refer to the following flowchart for information regarding the difference with the communication Ready signal (X1B).

Differences between the X1B and X1D

YES

X1D ON

X1B ON

Conduct self

diagnostic?

Self diagnostic program

Self diagnostic

OK?

Communi-

cation preparation

end?

Error processing

Communication preparation

(5) PROFIBUS I/F watchdog timer error signal (X0D)

This turns on when the AJ71PB96F/A1SJ71PB96F detects a watchdog timer error.

(6) Network trouble signal (X04)

This turns on when a value is set in the buffer memory network trouble information area. To turn off the network trouble signal (X04), turn on the network trouble read out end signal (Y04).

Page 45

4. FUNCTIONS MELSEC-A

4-19

4.7 Buffer Memory

The configuration of the buffer memory used to receive and send data with the AJ71PB96F/ A1SJ71PB96F and the PC CPU is shown below. This buffer memory can be accessed using the FROM/TO instruction from the sequence program. As shown in the following diagram, the AJ71PB96F/A1SJ71PB96F buffer memory is divided into 3 request areas, 3 request answer areas, 1 information area and receive area, and 3 data areas and receive data area.

Address (decimal/hexadecimal)

The unit is word (16 bits).

63/

0h to

3Fh

Request area No. 1 (Description) This is the area in which the PC CPU sets the request data.

64/

127/

40h

7Fh

Request answer area No. 1 (Description) This is the area in which the answer for the request area No. 1 request is returned.

128/

191/

80h

BFh

Request area No. 2 (Description) Same as No. 1.

192/

255/

C0h

FFh

Request answer area No. 2 (Description) Same as No. 1.

256/

319/

100h

13Fh

Request area No. 3 (Description) Same as No. 1.

320/

383/

140h

17Fh

Request answer area No. 3 (Description) Same as No. 1.

384/

447/

180h

1BFh

Unused (Reserved)

448/

511/

1C0h

1FFh

Receive area (Description) The unconfirmed service receive control information is set. The received data is set

in the reception only data area.

512/

1152/

200h

480h

Information area (Description) This area displays the association information.

Unused 1376/

1407/

560h

57Fh

Network trouble information area (Description) This area displays the media level trouble information.

Unused 1536/

2047/

600h

7FFh

Data area No. 1 (Description) This is the area in which the data to be read/write by the client function using the

request area No. 1 is set.

2048/

2559/

800h

9FFh

Data area No. 2 (Description) Same as No. 1

2560/

3071/

A00h

BFFh

Data area No. 3 (Description) Same as No. 1

3072/

3535/

C00h

DCFh

Receive data area (Description) This sets the data received by the unconfirmed service.

Page 46

4. FUNCTIONS MELSEC-A

4-20

4.7.1 Information area explanation

Information, such as the AJ71PB96F/A1SJ71PB96F current number of communications, can be obtained when the PC CPU refers to this area. This area is configured as follows.

512 513 514 515 516

547

576 577 578 579 580 581 582 583

591

110

Adress

(decimal)

Number of communications set up (maximum 32) Number of client communications Number of server communications CREF#1 communication abbreviation information

: Low byte 0: Communication abort 1: Communication initiate

: High byte 0: Server 1: Clien

CREF#33 communication abbreviation information

CREF#1 communication detailed information

CREF No. Communication status 0: abort, 1: initiate Communication type 0: MMAC, 1: MSAC, 5: MSAC_SI,

3: MSCY, 7: MSCY_SI, 8: BRCT, 10: MULT

0: server, 1: clien

0: partner station, 1: ACPU, 2: Utility, 3: Reject, 255: Local station communication

Abort information

0: User (VFD/ACPU/utility), 1: FMS/FMA7, 2: LLI, 3: FDL Reason code prescribed in PROFIBUS

Abort initiator

server/client

Communication type

Communication status

CREF No.

Abort initiator layer Abort reason

*1 x 32 The *1 portion is displayed for one communication. Therefore, a maximum of 33 are displayed.

Reserved

Page 47

4. FUNCTIONS MELSEC-A

4-21

4.7.2 Network trouble information area

The AJ71PB96F/A1SJ71PB96F network trouble information can be obtained when the PC CPU refers to this area. The area configuration, detailed code, and counter measures are shown below.

Reserved

1376 1377 1378 1379

1407

*1 x 7

Trouble type Code 1 in type Code 2 in type

The latest trouble information is given the smallest No., and a maximum of 8 trouble information can be displayed. The old information is moved in numerical order downwards.

Adress

(decimal)

(1) When the trouble type is 100h (initialization trouble):

Code 1 in type Code 2 in type

Initialization

phase

FMS/FMA7

error code

Description Counter measure

4h FFFFh There is an error with the remote

OD setting information.

Correctly set the remote OD.

Ah Other than

FFFFh

There is an error with the local OD setting information.

Correctly set the local OD.

Bh Other than

FFFFh

There is an error with the bus parameter setting information.

Correctly set the bus parameter information.

Ch Other than

FFFFh

There is an error with the CRL setting information.

Correctly set the CRL.

Other



There is an error in the module. Contact Mitsubishi Electric.

Page 48

4. FUNCTIONS MELSEC-A

4-22

(2) When the trouble type is 200h (network trouble):

Code 1 in type Code 2 in type

FMA7 event

instance ID

FMA7 event

cause code

Description Counter measure

3h 1h The same address has been

defined twice.

Check the addresses of the network nodes.

5h The local station has separated

from the token passing ring.

Make the slot time and other bus parameters match those of the nodes on the network.

Other



Conduct an investigation of each parameter, conduct a module selfdiagnosis, etc.

(3) When the trouble type is 300h (receive unconfirmed service PDU discard):

Code 1 in type Code 2 in type

CREF number Service

command

Description Counter measure

CREF number 50h The Unsolicited Status PDU is

discarded when the unconfirmed service maximum receive capacity was exceeded in connectionless communication.

Configure the systems so that the unconfirmed service maximum receive capacity is not exceeded.

1E0h The information report PDU was

discarded because the unconfirmed service maximum receive capacity was exceeded during connectionless communication.

Configure the system so that the unconfirmed service maximum receive capacity is not exceeded.

(4) When the problem type is 310h (parameter setting error):

Code 1 in type Code 2 in type Description Counter measure

— —

Communication failed due to an incorrect parameter.

Carefully check the compatibility of all parameters.

Page 49

4. FUNCTIONS MELSEC-A

4-23

4.8 Timing Chart

(1) When a request is output by the AJ71PB96F/A1SJ71PB96F:

This is shown when the request area No. 1 is used.

Y00

X00

FROM/TO

TO TO FROM FROM

The command is set in request area No. 1 by the PC CPU's TO instruction. When necessary it is set in the request area No. 1.

Y00 is turned on to notify the AJ71PB96F/A1SJ71PB96F that the command ha been set.

The PC CPU waits for an answer from the AJ71PB96F/A1SJ71PB96F. After X00 is turned on, if necessary the FROM instruction is read from the answer area No. 1 and data area No. 1.

Y00 turns off.

Request issued Request canceled

Answer area and data area setting complete

Request area set

Data area set Answer

area read

Data area

read

A minimum of 30ms is required from when Y00 turns on to when the data is actually transmitted. A minimum of 30ms is required from when Y00 turns off till the X00 turns off. Leave Y00 on until reading of the answer area and data area is completed.

Page 50

4. FUNCTIONS MELSEC-A

4-24

(2) When unconfirmed service is received:

Y03

X03

FROM/TO

FROM FROM

X03 is turned on to notify the PC CPU that the AJ71PB96F/A1SJ71PB96F has received an unconfirmed service.

The PC CPU reads the data from the received area and received data area using the FROM instruction, and when reading is completed, Y03 turns on to notify such to the AJ71PB96F/A1SJ71PB96F.

The AJ71PB96F/A1SJ71PB96F turns off X03.

The PC CPU turns off Y03

Receive area/receive data area reading complete Reading complete reset

UCS reception

Receive

area read

Receive data

area read

A minimum of 30ms is required from when Y03 tuns off till X03 turns off. Turn off Y03 after confirming that X03 has turned off.

Page 51

4. FUNCTIONS MELSEC-A

4-25

(3) When network trouble is detected:

Y04

X04

FROM/TO

FROM

X04 is turned on to notify the PC CPU that network trouble was detected in the AJ71PB96F/A1SJ71PB96F.

The PC CPU uses the FROM command to read the network trouble information area and then Y04 is turned on to notify the AJ71PB96F/ A1SJ71PB96F that the read has ended.

The AJ71PB96F/A1SJ71PB96F turns off.

The PC CPU turns off Y04.

Network trouble information area read end

Read end reset

Network trouble detection

Network trouble information read out

Page 52

5. PROCEDURES BEFORE SYSTEM OPERATION MELSEC-A

5-1

5. PROCEDURES BEFORE SYSTEM OPERATION

5.1 Procedures before Operation

The procedure for newly connecting AJ71PB96F/A1SJ71PB96F to an existing PROFIBUS-FMS network is explained below.

Install the AJ71PB96F/A1SJ71PB96F in the PC base unit. Connect the AJ71PB96F/A1SJ71PB96F and the network

with a twisted pair cable.

This is a hardware error, so contact the

nearest Mitsubishi Electric dealer and

explain the symptoms to the dealer.

Put the AJ71PB96F/A1SJ71PB96F in self-diagnosis mode and turn onthe PC power supply to conduct a self-diagnosis of the AJ71PB96F/A1SJ71PB96F. (refer to Section 5.4.)

Startup

Turn the PC CPU key switch to stop.

Set the AJ71PB96F/A1SJ71PB96F to the parameter setting mode.

Reset the PC CPU and set the AJ71PB96F/A1SJ71PB96F

parameter. When setting the SW0IX-PR0FPE is required.

Set the AJ71PB96F/A1SJ71PB96F in online mode

and reset the PC CPU.

Establish a connection between the AJ71PB96F/

A1SJ71PB96F and the partner station using the

SW0IX-PROFPE and acquire the partner station OD.

At this time, the acquired OD information is not stored

in the AJ71PB96F/A1SJ71PB96F, so be careful.

Yes

* Parameter

Is parameter* setting required?

Acquire the

partner station OD information

online?

Bus parameter CRL information Local OD

Is the AJ71PB96F/ A1SJ71PB96F normal?

Page 53

5. PROCEDURES BEFORE SYSTEM OPERATION MELSEC-A

5-2

Set the AJ71PB96F/A1SJ71PB96F in the paramete

setting mode and reset the PC CPU.

Store the partner station OD information in the AJ71PB96F/

A1SJ71PB96F using the utility SW0IX-PROFPE.

Set the AJ71PB96F/A1SJ71PB96F in online mode

and reset the PC CPU.

Create the PC CPU program.

Turn the PC CPU to run.

Yes

Operate

Preloaded the

partner station OD information in

the AJ71PB96F/ A1SJ71PB96F?

Point

*: Creation of a sequence program is required when the PC launches communication or when

the PC is used as a client. Creating a sequence program is not required when the PC is used as a server or when answering a request from a client.

Page 54

5. PROCEDURES BEFORE SYSTEM OPERATION MELSEC-A

5-3

5.2 Handling Precautions

This section explains handling precautions for AJ71PB96F/A1SJ71PB96F.



CAUTION



Use the module in the environment given in the general specifications of the CPU module’s User’s Manual. Using the module outside the range of the general specifications may result in electric shock, fire or malfunctioning, or may damage or degrade the module.



Do not touch the conductive area or the electronic parts of the module. Doing so may cause malfunctioning or breakdowns.



Switch all phases of the external power supply of the PC system off before connecting the PROFIBUS cable. Not doing so could cause failure or malfunction of the module.



Be careful not to let foreign matter such as filling or wire chips get inside the module. These can cause fire, breakdowns and malfunctioning.



Never disassemble or modify the module. This may cause breakdowns, malfunctioning, injury and/or fire.



Insert the tabs at the bottom of the module into the mounting holes in the base unit. (The AnS series module shall be fastened by screws in the base unit at the specified torque.) Not installing the module correctly could result in malfunctioning, breakdown or pieces of the product falling.



Switch all phases of the external power supply off before mounting or removing the module. If you do not switch off the external power supply, it will cause breakdowns or malfunction of the module.



Tighten the screws with the specified torque. If the screws are loose, it could result in falling, breaks or malfunction of the module. If the screws are too tight, it could result in falling, breaks or malfunctions due to damage of the screws or the module.

(1) The AJ71PB96F/A1SJ71PB96F’s case is made of resin, so be careful not to drop it or strike

it hard.

(2) The module fixing screw (M4) fastening torque should be tighten within the range of 78.4 to

117.6N

••••

cm {8 to 12kg

••••

cm}

Page 55

5. PROCEDURES BEFORE SYSTEM OPERATION MELSEC-A

5-4

5.3 Part Names and Settings

Following is an explanation of the AJ71PB96F/AISJ71PB96F part names and settings.

MODE

0:ONLINE 1:PRM SET 2:TEST

RS-232-C

PROFIBUS

I/F

BUS TERMINATION

OFF ON

A1SJ71PB96F

RUN

SD/RD TOKEN READY

FROM/TO

PRM SET

FAULT

TEST B6 B5 B4 B3 B2 B1 B0

S T

. N O

(a)

(c)

(d)

(e)

(b)

(c)

(d)

(e)

AJ71PB96

RUN

SD/RD TOKEN READY

FROM/TO

PRM SET

FAULT

TEST

B6 B5 B4 B3 B2 B1 B0

S T

. N O

0:ONLINE 1:PRM SET 2:TEST

BUS TERMINATIO

RS-232-C

PROFIBUS

I/F

OFF ON

MODE

AJ71PB96F A1SJ71PB96F

No. Name Description Remark

(a) LED Displays the AJ71PB96F/A1SJ71PB96F status. Name Display description RUN Displays the AJ71PB96F/A1SJ71PB96F operation status.

Turned on: During normal operation Turned off: When there is an error

SD/RD Turns on when data is transmitted/received on the

PROFIBUS-FMS network. TOKEN Turns on when token is maintained. READY Turns on when the PROFIBUS-FMS network subscription

preparation is completed and during subscription. FROM/TO Turns on when a FROM/TO instruction from the PC CPU is

executed. PRM.SET Turns on during the parameter setting mode. FAULT Turns on when an error occurs. TEST Turns on when a self-diagnosis is executing. B0 to B6 Displays the station address during normal operation (binary).

Displays the test type during a self-diagnosis.

Page 56

5. PROCEDURES BEFORE SYSTEM OPERATION MELSEC-A

5-5

No. Name Description Remark

(b) Mode setting switch This sets the AJ71PB96F/A1SJ71PB96F operation status.

(at time of shipment: 0) Switch No. MODE 0 Online mode 1 Parameter setting mode 2 Self-diagnosis mode (refer to section 4.5) 3 to F Not usable (c) RS-232C interface

connector

Connector for connecting the peripheral equipment that conduct the

AJ71PB96F/A1SJ71PB96F operation.

(d) PROFIBUS interface

connector

Connector for connecting the table for the PROFIBUS-FMS network. *2

(e) PROFIBUS network

terminal resistance setting switch

This sets whether or not there is terminal resistance inside the

AJ71PB96F/A1SJ71PB96F. (at time of shipment: OFF)

ON: has terminal resistance

OFF: no terminal resistance

Always ON for both ends of the station on the PROFIBUS-FMS network.

*1: For the connector type, use a male B-Sub 9 pin. The user makes the RF-232C cable. (for

information regarding cable wiring, refer to SW0IX-PROFPE Operating Manual.)

*2: For the connector type, use a male D-Sub 9 pin. The user creates the PROFIBUS cable. (for

information regarding the cable wiring, refer to Item 5.5.1.)

Page 57

5. PROCEDURES BEFORE SYSTEM OPERATION MELSEC-A

5-6

5.4 Self-diagnosis Execution Method

(1) Self-diagnosis method

The AJ71PB96F/A1SJ71PB96F self-diagnosis method is conducted using the following procedure. (a) Set the mode setting switch to “2.” (b) The PC CPU will stop. (c) The PC power will turn on. In addition, the PC CPU will be reset. (d) The AJ71PB96F/A1SJ71PB96F self-diagnosis will be executed, and results will be displayed

using the LEDs (B0 to B6).

(2) Test results

The results of the executed test are displayed as shown below (LED B0 to B6 display status).

Test item LED

B6 B5 B4 B3 B2 B1 B0 TEST

(a) MPU test During test

       

Error

       

(b) Timer test During test

       

Error

       

       

Error

       

(d) DRAM test During test

       

       

Error

       



: Turned off



: Turned on

When the test results are normal, tests (a) to (d) are repeated. If an error is detected, then the LED status at the tie the error occurs for that test will be displayed.

Page 58

5. PROCEDURES BEFORE SYSTEM OPERATION MELSEC-A

5-7

5.5 Wiring

5.5.1 PROFIBUS Cable Wiring

This section explains the wiring to PROFIBUS connector for AJ71PB96F/A1SJ71PB96F

(1) Pin assignments for the connector

Pin No. Symbol Name Application

1 SHIELD*1 Shield, Protective Ground 2 RP*1 Reserved for Power 3 A/A’ RxD/TxD-P Receive/Transmit Data-P 4 CNTR-P*1 Control-P 5 C/C’ DGND Data Ground 6 VP*2 Voltage-Plus 7 RP*1 Reserved for Power 8 B/B’ RxD/TxD-N Receive/Transmit Data-N 9 CNTR-N*1 Control-N

*1 Signal is optional. *2 Signal is only necessary at a station at the end of the bus cable.

(2) Wiring

PROFIBUS cable

AJ71PB96F/A1SJ71PB96F

SHIELD

RxD/TxD-P

RxD/TxD-N

Remark

•

To apply to the EMC standard: Read the Section for the Installation in the A1S/A2SCPU User's Manual (Hardware). (after the Ib66468-E)

•

Please use the PROFIBUS cable with braided shield.

5.5.2 Terminal switch

Whether or not to set the built-in module terminal resistance (1/2W 150Ω × 2 units) can be selected by connecting a switch. (The stations on both ends of the PROFIBUS segment must be connected with terminal resistor.)

Silk display ON OFF

TERMINATOR Connects terminals resistor Disconnects terminal resistor

(setting at time of shipment)

When the AJ71PB96F/A1SJ71PB96F's bus termination switch is set to on (has terminal resistor), do not remove the PROFIBUS cable from the AJ71PB96F/A1SJ71PB96F during PROFIBUS-FMS network operation. If the cable is removed, then the terminal resistor in the network will disappear, causing an error and bringing down the network.

Page 59

5. PROCEDURES BEFORE SYSTEM OPERATION MELSEC-A

5-8

5.5.3 Precautions Against Wiring

As one of the requirements to give full play to AJ71PB96F/A1SJ71PB96F’s functions and make up the system with high reliability, it is necessary to have an external wiring unsusceptible to an influence of noise. Precautions against external wiring of AJ71PB96F/A1SJ71PB96F is described below.

(1) Do not route the wire of AJ71PB96F/A1SJ71PB96F close to or bundle it together with the

main circuit and high-tension lines, or the load-carrying lines from other than the PC. Otherwise, the module may be susceptible to an influence of noise and surge induction.

(2) The wires from the input/output modules of the PC should be away from the

communication cable of PROFIBUS-FMS interface module as far as possible as shown in the figure below.

Shield twisted-pair cabl

Wiring of input module

Wiring of output module

Shielded covering

Power supply module

PC CPU

Input module

Output module

AJ71PB96F/

A1SJ71PB96F

Page 60

5. PROCEDURES BEFORE SYSTEM OPERATION MELSEC-A

5-9

(3) Grounding

(a) When the PROFIBUS-FMS interface module is used, the FG and LG terminals of the power

supply module of the PC should basically be grounded.

(b) If communication cannot be performed after grounding because of abnormal voltage applied

to the FG terminal, the module may be used without grounding.

Page 61

5. PROCEDURES BEFORE SYSTEM OPERATION MELSEC-A

5-10

5.6 Maintenance and Inspection

For the AJ71PB96F/A1SJ71PB96F, eliminate the check of cable connection and looseness and do not include it as an inspection item. Otherwise, follow the inspection item instructions in the PC CPU User’s Manual to always use the system in good condition.



DANGER



Switch all phases of the external power supply off before cleaning. Not doing so could cause failure or malfunction of the module.



CAUTION



Never disassemble or modify the module. This may cause breakdowns, malfunctioning, injury and/or fire.



Switch all phases of the external power supply off before mounting or removing the module. If you do not switch off the external power supply, it will cause failure or malfunction of the module.



Do not touch the conductive area or the electronic parts of the module. Doing so may cause malfunctioning or breakdowns.

Page 62

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A

6-1

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM

This chapter explains the communication services that require the sequence program when the AJ71PB96F/A1SJ71PB96F conducts the communication services.

6.1 FMS Service and Command No.

Use the following command Nos. to identify the communication services used when the receive area is used to execute a communication service or an unconfirmed service is received by the receive area.

Communication service name Command Description

Initiate Abort Status UnsolicitedStatus Identify Read Write InformationReport FMA7 Abort

0010h 0020h 0040h 0050h 0060h

01a0, 01a1h

01c0, 01c1h

01e0, 01e1h

2020h

Connection initiated Connection aborted Partner station status information acquired PC CPU status notification Identification information acquired Data read Data write Arbitrary data transmitted FMA7 connection aborted

6.2 Program Example

A programming example is shown below. In the following example, the AJ71PB96F/A1SJ71PB96F is installed in the basic base unit No. 0 slot. Examples of the Write service that uses the request area and the Information Report that uses the receive area are shown.

6.2.1 Write

An example for the execution of the write service that uses the request area No. 1 is shown. In the following example, D100 to D123 are used to set the write control data and D300 is used to set the write data. In addition, the execution results are stored in D200 to D202.

(1) Request data set (TO instruction)

Write command

Connection identification No.

Access mode = INDEX

INDEX = 123h

Subindex = 6

Write control data set

Write data settig

Write data set

Request issue

Page 63

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A

6-2

(2) Answer data storage (FROM instruction)

Execution result write

Request cancel

Request command OFF

6.2.2 Information Report

The following shows an example of using the reception area to execute the Information Report service reception processing.

(1) Receive data storage (FROM instruction)

Receive area read

Receive data area rea

Read end signal set

Read end signal reset

6.3 FMS Communication Circuit Initiate With Partner Station (Initiate: Initiator)

The previously determined communication conditions are set and a communication path is established with the partner station. When a communication path is established, the CRL parameters need to be set using the software package.

(1) Request area

0010h

0 1 2 3 4

* *

Initiate commands CREF (communication information) No

Page 64

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A

6-3

(2) Request answer area

64 65 66 67 68

127

* *

If successful 0 and if unsuccessful an error code is set

Error code during communication Don't Care when other than an erro during communication

Explanation

For details regarding error codes, refer to Section 8.

•

The * denotes Don’t Care. The values set in the request area are ignored. The values set in the request answer area are undefined.

Page 65

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A

6-4

6.4 FMS Communication Circuit Abort With Partner Station (Abort: Requester)

This command aborts the connection.

(1) Request area

0020h

0 1 2 3 4

* *

Abort command CREF No.

This specifies the CREF No. of the partner with which the connection is aborted.

(2) Request answer area

Same as for Initiate.

Page 66

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A

6-5

6.5 Partner Station Status Read (Status: Client)

This command is used to acquire the server station status.

(1) Request area

0040h

0 1 2 3 4

* *

Status comman CREF No.

(2) Request answer area

Same as Initiate.

(3) Data area

153 153 153 153

Logical Status*1 Physical Status*2 Local Detail*3

Explanation

*1 The following values are set.

Communicable status (all services can be used) -------------- > 0 Communicable status (some services can be used)---------- > 2 OD loading--------------------------------------------------------------- > 4 OD loading--------------------------------------------------------------- > 5

*2 The following values are set.

Operational -------------------------------------------------------------- > 0 Partially operational---------------------------------------------------- > 1 Not operational---------------------------------------------------------- > 2 Requires operation----------------------------------------------------- > 3

*3 The following values are set.

1538 1539

Address Upper position Lower position

Second octe First octet

Therd octe

Page 67

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A

6-6

6.6 Partner Station Identification Information Read (Identify: Client)

This command is used to check the server station identification information.

(1) Request area

0060h

0 1 2 3 4

* *

Identify comman CREF No.

(2) Request answer area

Same as for Initiate.

(3) Data area

1536 1537

1552 1553 1554

1569 1570 1571

1586

Vendor name length

Vendor name

maximum 32 characters

Model name length

Model name

maximum 32 characters

Revision name length

Revision name

maximum 32 characters

The length of the vendor name set from the 1537 address

The length of the model set from the 1554 address

Revision name length set from the 1571 address

Page 68

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A

6-7

6.7 Partner Station Variable Read (Read: Client)

This command is used when the PC CPU reads the server data (variable).

(1) Request area (when the access mode is index)

(1-1) When the access mode is index

01a0 or 01a1 h

0 1 2 3 4 5 6 7 8

23 24 25

* *

Read command (selected depending on the bit-String data storage method difference)

CREF No.

Always set to 0. (access mode)

Index No

Subindex No. *1

Explanation

*1 The subindex No. specifies which array and which element of that area is accessed when

accessing an array label or record label. Specify 0 when accessing all elements of an array or a record variable, and specify a new element No. (the first element is 1) when accessing one element of an array or record variable.

Page 69

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A

6-8

(1-2) When the access mode is name

01a0 or 01a1 h

0 1 2 3 4 5 6 7 8

23 24

* *

Read command (selected depending on the bit-String data storage method

CREF No.

Always set to 1. (access mode

Variable name length

Variable name maximum 32 characters

Subindex No. *1

Explanation

*1 Set the same as for (1).

Note

A name is not specified in the access mode when the Long form’s GetOD client function is not supported by the specified connection.

(2) Request answer area

(2-1) When normal end (when the access mode is indexed)

64 65 66 67 68 69

85 86 87 88 89 90 91

* *

0 0

Access mode Index No.

Subindex *1 Variable type *2 Number of elements *3 Data type *4 Data length (byte value) *5 Data length (word value) *6 Buffer memory address

First element

Several elements are repeated.

Page 70

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A

6-9

(2-2) During normal end (when the access mode is name)

64 65 66 67 68 69

85 86 87 88 89 90 91

127

* *

0 1

Access mode Variable name length The variable name length

set from the 69 address

Read variable name

Subindex *1 Variable type * Number of elements * Data type *4 Data length (byte value) * Data length (word value) *6 Buffer memory address *7

Several elements are repeated.

First element

Explanation

*1 Subindex

This is set to the same value as the values set in the request area.

*2 Variable type (the following values are set.)

Simple variable --------------------------------------------------------- > 0007h Array----------------------------------------------------------------------- > 0008h

Record -------------------------------------------------------------------- > 0009h *3 The following values are set. *4 Data type (the following values are set)

Truth value (Boolean)------------------------------------------------- > 0001h

Integer with sign (Integer8) ------------------------------------------ > 0002h

Integer with sign (Integer16)----------------------------------------- > 0003h

Integer with sign (Integer32)----------------------------------------- > 0004h

Integer (Unsigned8) --------------------------------------------------- > 0005h

Integer (Unsigned16)-------------------------------------------------- > 0006h

Integer (Unsigned32)-------------------------------------------------- > 0007h

Floating point (FloatingPoint)---------------------------------------- > 0008h

Character string (VisibleString)------------------------------------- > 0009h

Octet string (OctetString)--------------------------------------------- > 000Ah

Bit string (BitString)---------------------------------------------------- > 000Eh *5 Data length (byte) (the following values are set)

Array, record-------> This shows the byte length for the data length of the data in one element.

Simple variable ---> This shows the byte value for the data data length. *6 Data length (word) (the following values are set)

Array, record-------> This shows the word value for the data length of the data in one element.

Simple variable ---> This shows the word value for the data data length. *7 Buffer memory address

The address of the buffer memory for reading this element is set.

Page 71

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A

6-10

Note

•

Because in PROFIBUS-FMS bit strings are read in 8 bit units, the bit string read is set to the octet length (byte length).

•

Data length (word) is used when reading from the buffer memory from the circuit program, and is to determine whether the first byte of the final word data in the data length (byte) value is valid/invalid.

•

When the data length (byte) is even, the final word data first byte is valid.

•

When the data length (byte) is odd, the final word data first byte is invalid.

(2-3) During failure The same as for Initiate.

Page 72

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A

6-11

(3) Data area

During normal end, the read data is set following the variable type.

(3-1) When the variable type is Simple Variable. (a) Truth value (Boolean)

0 or NOT

0 : False 0FFh

: True

153

Address

(b) Integer (Integer, Unsigned)

•

8 bit example: when the value is 8dh

x x 8dh153

•

16 bits

1536

Integer value

•

32 bits

low wor high word

1536 1537

<< When the command is 01a0h, 01c0h, 01e0h >>

01100111 10001101

10001001

153 153

The value is 10001101 01100111 10001001.

<< When the command is 01a1h, 01c1h, 01e1h >>

11100110 10110001

10010001

153 153

The value is 10001101 01100111 10001001

Page 73

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A

6-12

(d) Octet string (OctetString)

When the value is 01h, 02h, 03h, 04h, 05h then the octet string is set as shown below.

02h 01h

03h04h 05h

153 153 153

(e) Character string (VisibleString)

When the value is “ABCDE,” the visible string is set as shown below.

'B' 'A' 'D' 'C'

'E'

153 153 153

(f) Floating point (FloatingPoint)

This is the same format as for the AnACPU or AnUCPU, and is set from the 1536 address.

1536 1537

Bit 0 to 7

Bit 31

Bit 8 to 15 Bit 16 to 23

Bit 24 to 31

30 23 22 0

Exponential portion Mantissa portio

Mantissa portion sign

(3-2) When the variable type is Array or Record

The format data explained in SimpleVariable is divided into the number of elements. When the data length of one element is an odd number of bytes, a valid value is not set for the element’s first byte.

Example: When the VariableString array value is "ABCDE," "FGHIJ," then the setting is as follows.

'B' 'A' 'D' 'C'

'J'

1536 1537 1538 1539 1540 1541

'E' 'G' 'F' 'I' 'H'

Page 74

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A

6-13

6.8 Partner Station Variable Write (Write: Client)

This command is used when the PC CPU writes the server data (variable).

(1) Request area

(1-1) Request area (when the access mode is index)

01c0 or 01c1 h

0 1 2 3 4 5 6 7 8

23 24 25

* *

Write command (selected depending upon the bit-String data storage method difference)

CREF No.

Always set to 0.

Index No

Subindex No. *1

Explanation

*1 Subindex No.

Same as for read.

(1-2) Request area (when the access mode is name)

01c0 or 01c1 h

0 1 2 3 4 5 6 7 8

23 24

* *

Write command (selected depending on the bit-string data storage method difference).

CREF No.

Always set to 1.

Variable name length

Variable name

maximum 32 characters

Subindex No. *1

Page 75

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A

6-14

Explanation

*1 Set the same as in (1).

Note

The name is not set in the access mode when the Long form's GetOD client function is not supported by the specified connection.

(2) Request answer area

The same as for Initiate.

(3) Data area

Use the same format type for write data as that used for the Read data area.

Page 76

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A

6-15

6.9 PC CPU Variable Report (Information Report: Requester)

This command is used when arbitrary data, such as data registers, are transmitted. The InformationReport can be sent in the following cases.

1) MMAC client and server

2) MSAC, MSAC_SI, MSCY, MSCY_SI clients

3) MSAC_SI, MSCY_SI server

4) BRCT/MULT requester

(1) Request area

(1-1) When the access mode is index

01e0 or 01e1 h

0 1 2 3 4 5 6 7 8

* *

InformationReport command (selected depending on the bit-string data storage method difference)

CREF No.

Specify the transmission destination CREF No

Always set to 0

Index No

Subindex *

Explanation

*1 Subindex No.

Same as for Read.

Page 77

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A

6-16

(2-2) When the access mode is name

01e0 or 01e1 h

0 1 2 3 4 5 6 7 8

23 24

* *

InformationReport command (selected depending on the bit-String data storage method difference)

CREF No.

Specify the transmission destination CREF No

Always set to 1.

Variable name length

Variable name

maximum 32 characters

Subindex *1

Explanation

*1 Subindex No.

The same as for Read.

(2) Request answer area

Same as for Initiate.

(3) Data area

The data area is not used with this function. The transmitted data is the same as the server function Read.

Page 78

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A

6-17

6.10 PC CPU Status Report (UnsolicitedStatus: Requester)

This command is used to report the PC CPU status (including special relays) to the partner.

UnsolicitedStatus can be transmitted in the following cases.

1) MMAC client and server

2) MSAC, MSAC_SI, MSCY, MSCY_SI client

3) MSAC_SI, MSCY_SI server

4) BRCT/MULT request

(1) Request area

0050

0 1 2 3 4 5

* * * *

UnsolicitedStatus command CREF No.

Specify the transmission destination CREF No.

Explanation

*1 Set the same as for informationReport.

(2) Request answer area

The same as for Initiate.

(3) Data area

Data area is not used with this function. The transmitted data is the same as the server function status.

Page 79

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A

6-18

6.11 Reporting the Partner Station Variable Data to the PC CPU (Information Report: Receiver)

The receive data and variable information is set in the receive area and receive data area.

Note

•

Before the PC CPU reads the unconfirmed service data from the buffer memory, the number of following unconfirmed services that can be received by the AJ71PB96F/A1SJ71PB96F is one service per connection. When the second service is received, the AJ71PB96F/A1SJ71PB96F connection is forcefully aborted. For connectionless communication, the received service is discarded.

•

Communications that can receive unconfirmed services are listed below.

1) MMAC client and server

2) MSAC, MSAC_SI, MSCY_SI during slave simulation

3) MSAC_SI, MSCY_SI client and server

4) BRCT/MULT receiver

(1) Reception area

(1-1) When the access mode is index

448 449 450 451 452 453 454 455 456 457 458

474 475 476 477 478 479 480

512

* *

0 or FFFFh

01E0h

Error code *1

CREF No.

Set the transmission origin CREF No

InformationReport command

Access mode *2

OD flag *3 Index No

Subinde Variable type *4 Number of elements *5 Data type *6 Data length (byte) *7 Data length (word) *8 Buffer memory address *9

First elemen

Several elements are repeated

Page 80

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A

6-19

Explanation

*1 For details regarding the error codes, refer to the Appendix. *2 Always set to 0 when the access mode is index. *3 This displays whether or not the OD was referenced when setting the receive data in the

receive data area. Referenced -------------------------------------------------------------- > 0000h Not referenced---------------------------------------------------------- > FFFFh The OD is not referenced for the respond to open connection (/0), broadcast, or multicast connection.

*4 The variable type (the following values are set)

Simple Variable--------------------------------------------------------- > 0007h Array----------------------------------------------------------------------- > 0008h Record -------------------------------------------------------------------- > 0009h When OD flag = FFFFh----------------------------------------------- > FFFFh

Explanation

*5 Number of elements (the following values are set).

Simple Variable--------------------------------------------------------- > 0001h Array, Record ----------------------------------------------------------- > number of elements When OD flag = FFFFh----------------------------------------------- > 0001h

*6 Data type (the following values are set).

Truth value (Boolean)------------------------------------------------- > 0001h Integer with code (Integer8) ----------------------------------------- > 0002h Integer with code (Integer16)---------------------------------------- > 0003h Integer with code (Integer32)---------------------------------------- > 0004h Integer (Unsigned8) --------------------------------------------------- > 0005h Integer (Unsigned16)-------------------------------------------------- > 0006h Integer (Unsigned32)-------------------------------------------------- > 0007h Floating point (FloatingPoint)---------------------------------------- > 0008h Character string (VisibleString)------------------------------------- > 0009h Octet string (OctetString)--------------------------------------------- > 000Ah Bit string (BitString)---------------------------------------------------- > 000Eh When OD flag = FFFFh----------------------------------------------- > FFFFh

*7 Data length (byte) (the following values are set).

Array, Record -----> This shows the byte value for the data length of the data in one element. Simple Variable---> This shows the byte value for the data length. When OD flag = FFFFh--------> This shows the byte value for the data length.

*8 Data length (word) (the following values are set).

Array, Record -----> This shows the word value for the data length. Simple Variable---> This shows the word value for the data length When OD flag = FFFFh--------> This shows the word value for the data length.

*9 Buffer memory

The buffer memory address for reading the element is set.

Page 81

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A

6-20

Note

•

In PROFIBUS-FMS, the bit string is read in 8 bit units, so the bit string read is set to the octet length (byte length).

•

The data length (word) is used when reading from the buffer memory from the circuit program, and the data length (byte) value is used to determine whether the final word data first byte is valid/invalid.

•

When the data length (byte) is even, the last word data first byte is valid.

•

When the data length (byte) is odd, the final word data first byte is invalid.

(1-2) When the access mode is name

448 449 450 451 452 453 454 455 456 457 458

474 475 476 477 478 479 480

512

* *

0 or FFFFh

01E0h

Error code *1

This is set 0 when successful

and an error code when fails InformationReport command

Connection identification No

The received connection identification No. is set

Access mode *2

OD flag *3 Variable name lengt

The variable name length is se

from the 458 address.

Read variable name

Subinde Variable type *

Number of elements *5 Data type *6 Data length (byte) *7 Data length (word) * Buffer memory address *9

Several elements are repeated.

First elemen

Page 82

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A

6-21

Explanation

*1 For details regarding error codes, refer to the Appendix. *2 Always set to 1 when the access mode is name. *3 OD flag *4 Variable type *5 Number of elements *6 Data type *7 Data length (byte) *8 Data length (word) *9 Buffer memory address

(2) Receive data area

(2-1) When the receive area OD flag is FFFFh. The data is set unchanged in this area without the receive data that used the OD being interpreted. The data is set as follows. (The same as for OctetString.)

When the value is 01h, 02h, 03h, 04h, 05h, 06h, the settings are as follows.

02 01

0304

06 05

1536 1537 1538

(2-2) When the receive area OD flag is not FFFFh. The same as for the Write data area.

Page 83

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A

6-22

6.12 Reports to the Partner Station Status PC CPU (Unsolicited Status: Receiver)

The received partner station status information is set in the receive area and receive data area.

Note

•

Before the received unconfirmed service data is read from the buffer memory by the PC CPU, the number of following unconfirmed services that can be received by the AJ71PB96F/A1SJ71PB96F is one service per connection. When the second service is received, the AJ71PB96F/A1SJ71PB96F forcefully aborts the connection. For connectionless connection, the received service is discarded.

•

The communications that can receive unconfirmed services are as follows.

1) MMAC client and server

2) MSAC, MSAC_SI, MSCY, MSCY_SI during slave simulation

3) MSAC_SI, MSCY_SI client and server

4) BRCT/MULT receiver

(1) Receive area

0050h

448 449 450 451 452 453 454 455

512

* *

* * * *

Set to error code

if a failure and to 0 if successful

UnsolicitedStatus command CREF No.

Set to the received CREF No

(2) Receive data area

307 307 307 307 307

358

* *

Logical Status*1 Physical Status*2 Local Detail*3

Explanation

*1, *2, and *3 : The same as for Status.

Page 84

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A

6-23

6.13 FMA7 Connection Abort (FMA7 Abort: Receiver)

This command is used when the PC CPU aborts the FMA7 connection.

(1) Receive area

2020

0 1 2 3 4

* *

Abort comman CREF No.

Always set to 1.

(2) Receive answer area

The same as for Initiate.

Page 85

Page 86

7. COMMUNICATION THAT DO NOT REQUIRE

THE SEQUENCE PROGRAM MELSEC-A

7-1

7. COMMUNICATION THAT DO NOT REQUIRE THE SEQUENCE PROGRAM

This chapter explains the communication service parameters that can be specified in the client when the AJ71PB96F/A1SJ71PB96F is operating as a server.

7.1 FMS Service

7.1.1 Connection with AJ71PB96F/A1SJ71PB96F (Initiate: Responder)

When communicating with the AJ71PB96F/A1SJ71PB96F, the client issues an Initiate service to establish a connection.

[Parameters required by the client]

•

Version 0D (Calling)

OD version number

Version OD value

Client OD version

•

Profile Number (Calling)

Specify the profile number.

Profile Number value

Profile number supported by the client

•

Access Protection Supported (Calling)

Specify whether or not the access protection is supported.

Access Protection value Meaning

False = 0 Not supported False = FF (hex) Supported

•

Password (Calling)

Password allocated to each connection

Password value

00 (hex)

Page 87

7. COMMUNICATION THAT DO NOT REQUIRE

THE SEQUENCE PROGRAM MELSEC-A

7-2

•

Access Groups (Calling)

Access group allocated to each connection

Access Group’s value

00 00 (hex)

•

Max Send PDU Size (High Priority) (Calling)

FMS communication packet size that can be transmitted during High Priority use

Max Send PDU Size (H) value

PDU size

•

Max Send PDU Size (Low Priority) (Calling)

FMS communication packet size that can be transmitted during Low Priority use

Max Send PDU Size (L) value

PDU size

•

Max Receive PDU Size (High Priority) (Calling)

FMS communication packet size that can be received during High Priority use

Max Receive PDU Size (H) value

PDU size

•

Max Receive PDU Size (Low Priority) (Calling)

FMS communication packet size that can be received during Low Priority use

Max Receive PDU Size (L) value

PDU size

•

Feature Supported (Calling)

Service types that can be used

Features Supported value

Features supported octet string

Page 88

7. COMMUNICATION THAT DO NOT REQUIRE

THE SEQUENCE PROGRAM MELSEC-A

7-3

Point

When establishing a connection using PROFIBUS-FMS, the receive side capability must be greater than or equal to the transmission side visibility.

When a connection is established, make the following settings between the two stations.

Station A

Station B

MaxSendPDUSize

(High Priority)

≤

MaxReceivePDUSize

(High Priority)

MaxSendPDUSize

(Low Priority)

≤

MaxReceivePDUSize

(Low Priority)

MaxReceivePDUSize

(High Priority)

≥

MaxSendPDUSize

(High Priority)

MaxReceivePDUSize

(Low Priority)

≥

MaxSendPDUSize

(Low Priority)

Feature Supported (n)th bit

≤

Feature Supported (n+24)th bit

(0 ≤ m ≤ 23)

Feature Supported (m+24)th bit

(0 ≤ m ≤ 23)

≥

Feature Supported (m)th bit

Note

In the AJ71PB96F/A1SJ71PB96F, the value from the logical sum for each bit is the value set by the software package of C0 30 81 F9 D0 81 (hex) is used.

[Server (AJ71PB96F/A1SJ71PB96F) return parameters]

•

Version 0D (Calling)

OD version number

Version OD value

AJ71PB96F/A1SJ71PB96F OD version

Page 89

7. COMMUNICATION THAT DO NOT REQUIRE

THE SEQUENCE PROGRAM MELSEC-A

7-4

•

Profile Number (Calling)

This sets the station attributes and device identification.

Profile Number value

00 00 (hex)

•

Access Protection Supported (Calling)

This specifies whether or not access protection is supported.

Access Protection value Meaning

False = 0 Not supported

•

Password (Calling)

Password allocation for each connection

Password value

Set by the utility

•

Access Groups (Calling)

Access group allocated to each connection

Access Group’s value

Set by the utility

Page 90

7. COMMUNICATION THAT DO NOT REQUIRE

THE SEQUENCE PROGRAM MELSEC-A

7-5

7.1.2 AJ71PB96F/A1SJ71PB96F connection abort (Abort: Receiver)

An "Abort" service from client is issued to abort the connection with the AJ71PB96F/A1SJ71PB96F. When the AJ71PB96F/A1SJ71PB96F receive an abort, then a logical connection abort status is entered. An "Abort" is automatically issued when there is a PROFIBUS-FMS protocol or parameter error.

[Parameters required by the client]

•

Abort Identifier

This shows from which communication level an abort can be issued.

Abort Identifier Explanation

0 (USER) When aborted by the application 1 (FMS) Aborted by FMS 2 (LLI) Aborted by LLI 3 (Layer 2) Aborted by layer 2

Point

When the abort is executed by the user created application program, 0 (User) is suitable for the Abort Identifier value. Other values are used by the communicating device side that is actually conducting the communication.

•

Reason Code

This shows the reason for the abort.

Reason Code

Reason code prescribed by PROFIBUS

•

Abort Detail

This sets the abort detail report. This parameter usage method is prescribed by the profile supported by the request.

Abort Detail

Abort detail information (maximum 16 octet)

[Server (AJ71PB96F/A1SJ71PB96F) return parameter]

None

Page 91

7. COMMUNICATION THAT DO NOT REQUIRE

THE SEQUENCE PROGRAM MELSEC-A

7-6

7.1.3 Service reject (Reject)

A “Reject” service is issued when there is a problem in the FMS protocol, so this cannot be controlled by the user.

Page 92

7. COMMUNICATION THAT DO NOT REQUIRE

THE SEQUENCE PROGRAM MELSEC-A

7-7

7.1.4 PC CPU status information (Status: Server)

A “Status” service is issued from the client to acquire in the PC CPU status information. The AJ71PB96F/A1SJ71PB96F that received the service returns the data to the PC CPU special relay M9000 to M9008 (excluding M9001, M9003).

[Parameters required by the client]

None

[Server (AJ71PB96F/A1SJ71PB96F) return parameters]

•

Logical Status

Value Name Explanation

0 Ready for communication All operations are possible from the client. 2 Limited number of

services

(Not used)

4 OD-LOADING-NON-

INTERACTING

Loading ODs not used in common between connections.

5 OD-LOADING-

INTERACTING

Loading ODs not used in common between connections. All connections that are not loading ODs are forcefully aborted.

•

Physical Status

This shows the VFD status.

Value Name Explanation

0 Operational Operation is possible from the client. 1 Partially Operational Operation is possible from the client. However, self-diagnostic error

generation (N9008 is on). 2 Inoperable Operation is not possible from the client. 3 Needs Commissioning Operation is possible from the client. However, the PC CPU cannot

be run. In addition, there is a possibility that a self-diagnosis error will

occur.

For details, refer to Appendix 2 VDF Physical Status Criteria Table.

•

Local Detail

M9000 to M9008, D9015 actual information (excluding M9001, M9003)

Local Detail details

D9015 data

9008900790069005900490029000

LSBMSB

Note

The

mark is an undefined value. (Not set to either 0 or 1.)

There are special relays (M9000 number level) that are not used by the PC CPU. In this case, the value is undefined.

Page 93

7. COMMUNICATION THAT DO NOT REQUIRE THE SEQUENCE PROGRAM MELSEC-A

7-8

7.1.5 AJ71PB96F/A1SJ71PB96F identification information (Identify: Server)

An "Identify" service is issued from the client to obtain AJ71PB96F/A1SJ71PB96F identification information.

[Parameters required by the client]

None

[Server (AJ71PB96F/A1SJ71PB96F) answer parameters]

•

The following character strings are returned.

Item Character string

Vendor Name MITSUBISHI ELECTRIC Model Name MELSEC-A A1SJ71PB96F Revision VER XXX*1 YYMMDD *2

*1: This shows the version of model. *2: This shows the date of issue.

Page 94

7. COMMUNICATION THAT DO NOT REQUIRE THE SEQUENCE PROGRAM MELSEC-A

7-9

7.1.6 Object attribute acquisition (GetOD: Server)

A “GetOD” service is issued from the client to acquire the object attributes defined in AJ71PB96F/ A1SJ71PB96F. In PROFIBUS-FMS the object attributes are registered in the OD (Object Dictionary). One object attribute data is called an OD entry. This service is also use to learn the PI (Program Invocation) status.

[Parameters required by the client]

•

All Attributes

This specifies the acquisition format of the object attributes to be acquired.

All Attributes value Meaning

False = 0 Acquisition of specific attributes (minimum required) True = FF (hex) Acquisition of all attribute

Point

The following attributes cannot be acquired when "All Attributes = False" is specified. To acquire these attributes specify "True."

•

Password

•

Access Groups

•

Access Rights

•

Local Address

•

Name

•

Local Address-OD-ODES

•

Local Address-ST-OD

•

Local Address-S-OD

•

Local Address-DV-OD

•

Local Address-DP-OD

•

Extension

•

Access Specification

Specify the required specific values for the following cases.

Access Specification Setting value

Index Index of the OD entry to be acquired. Variable Name Name of the variable object to be acquired. Domain Name Name of the domain object to be acquired. PI Name Name of the PI object to be acquired. Start Index Index of the object for which acquisition will begin.

Page 95

7. COMMUNICATION THAT DO NOT REQUIRE THE SEQUENCE PROGRAM MELSEC-A

7-10

[Server (AJ71PB96F/A1SJ71PB96F) answer parameters]

•

List of Object Description

This sets the acquired OD entry data.

•

More Follows

This informs whether or not OD entries still remain.

More Follows value Meaning

False = 0 No more objects status True = FF (hex) More objects status

Note

The correct values for the program domain, command domain, and expansion command domain acquired using the GetOD service are not displayed. For information on the method to use to learn the correct domain size refer to Section 7.1.12 Reading Program Capacity and Comment Capacity, Etc."

Page 96

7. COMMUNICATION THAT DO NOT REQUIRE THE SEQUENCE PROGRAM MELSEC-A

7-11

7.1.7 Initiate objects attribute setting (InitiatePutOD: Server)

The three services of InitiatePutOD, PutOD, and TerminatePutOD are used by the AJ71PB96F/ A1SJ71PB96F to set the object attributes in the OD.

InitiatePutOD.request

InitiatePutOD.response

TerminatePutOD.reques

TerminatePutOD.response

PutOD.reques

Server

(Repeated)

Clien

PutOD.response

PutOD.reques

PutOD.response

Note

As far as possible, make the write OD the OD acquired using GetOD from the AJ71PB96F/ A1SJ71PB96F.

If there is a error with the write OD at worst communication cannot be conducted. If this happens, use the software package to rewrite the OD.

InitiatePutOD is used to announce the start of OD setting.

Page 97

7. COMMUNICATION THAT DO NOT REQUIRE THE SEQUENCE PROGRAM MELSEC-A

7-12

[Parameters required by the client]

•

Consequence (importance)

This shows the impact that changing the OD will have on other connections.

Consequence Meaning

Loading free of Interacting

•

This means that ODs that are unused in other connections will be overwritten.

•

The VFD LogicalStatus will be changed to OD-LOADING-NONINTERACTING.

Reload, not free of Interacting

•

This means that ODs that are unused in other connections will be overwritten.

•

The A1SJ71PB96F will forcefully abort other connections.

•

The VFD LogicalStatus will be changed to OD-LOADING-NONINTERACTING.

Newload, not free of Interacting

•

This means that the entire OD will be overwritten.

•

The A1SJ71PB96F will forcefully abort other connections.

•

The VFD LogicalStatus will be changed to OD-LOADINGINTERACTING.

[Server (AJ71PB96F/A1SJ71PB96F) answer parameters]

None

Page 98

7. COMMUNICATION THAT DO NOT REQUIRE THE SEQUENCE PROGRAM MELSEC-A

7-13

7.1.8 Object attribute setting (PutOD: Server)

This sets the actual OD data after InitiatePutOD is successful.

[Parameters required by the client]

•

List of Object Description

Set the data to be written in the OD.

[Server (AJ71PB96F/A1SJ71PB96F) answer parameters]

None

7.1.9 Object attribute setting termination (TerminatePutOD: Server)

This is used to announce that OD setting is being terminated.

[Parameters required by the client]

None

[Server (AJ71PB96F/A1SJ71PB96F) answer parameters]

None

Page 99

7. COMMUNICATION THAT DO NOT REQUIRE THE SEQUENCE PROGRAM MELSEC-A

7-14

7.1.10 Reading device memory and buffer memory (Read: Server)

A "Read" service is issued by the client to read the PC CPU device memory and special functions module buffer memories.

The device memories to be read must be registered in advance in the OD as an Array, Simple Variable, or Record using the software package. In addition, the buffer memory must be registered in the OD as an Array or Simple Variable.

[Parameters required by the client]

•

Access Specification

Read device specifications are executed by Index or Name.

Access Specification Setting value

Index Index of the variable to be read Variable Name Name of the variable to be read

•

Subindex

This specifies which element will be read when an Array or Record is read. If a Subindex is not specified then all the elements will be read. The Array or Record header element Subindex is 1.

[Server (AJ71PB96F/A1SJ71PB96F) answer parameters]

•

Data

This sets the value of the variable to be read.

The data arrangement when a bit-String is conducted using the following specifications, so be careful.

When accessing from the M100 using a 16 unit bit-String

M115M114M113M112M111M110M109M108

LSB

MSB

M107M106M105M104M103M102M101M100

In addition, in PROFIBUS-FMS the unit used to read Bit-String data is 8 bits. In other words, bit lengths that do not equal multiples of 8, such as 3 bits or 4 bits, are not read.

Page 100

7. COMMUNICATION THAT DO NOT REQUIRE THE SEQUENCE PROGRAM MELSEC-A

7-15

7.1.11 Writing device memory and buffer memory (Write: Server)

A "Write" services is issued from the client to write the data in the PC CPU device memory and special functions module buffer memories.

The device memories to be written must be registered in the OD in advance as an Array, Simple Variable, or Record using the software package. In addition, the buffer memory must be registered in the OD as an Array or Simple Variable.

[Parameters required by the client]

•

Access Specification

The device to be written is specified using the index or name.

Access Specification Setting value

Index Index of the variable to be read Variable Name Name of the variable to be read

•

Subindex

This specifies which element will be written when an Array or Record write is conducted. If a Subindex is not specified then all the elements will be written. The Array or Record header element Subindex is 1.

•

Data

This sets the data that will actually be written.

The data arrangement for a bit-String is conducted using the following specifications, so be careful.

When accessing from the M100 using a 16 unit bit-string

M115M114M113M112M111M110M109M108

LSB

MSB

M107M106M105M104M103M102M101M100

In addition, in PROFIBUS-FMS the unit used to write Bit-String data is 8 bits. In other words, bit lengths that do not equal multiples of 8, such as 3 bits or 4 bits, are not read.

[Server (AJ71PB96F/A1SJ71PB96F) answer parameters]

None

Mitsubishi Electric A1SJ71PB96F, AJ71PB96F User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual