Page 1

MITSU BIS HI ELECTRIC MEL SEC A se ries Pro gram ma ble Con trol ler User's Ma nu al Profibus Modules A(1S)J71PB96F 981001 MITSU BIS HI ELECTRIC EU RO PE B.V. 65629-C FAC TO RY AU TO MA TION...
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.
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.
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"...
Page 6

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.
Page 7: Table Of Contents

Please forward a copy of this manual to the end user. Table of Contents About This Manual OVERVIEW 1-1 to 1-2 Software Configuration ............................1- 1 AJ71PB96F/A1SJ71PB96F Characteristics .......................1- 2 SYSTEM CONFIGURATION 2-1 to 2-10 Whole System Configuration ..........................2- 1 Applicable CPU Modules ............................2- 3 System Configuration Precaution Items ......................2- 4 2.3.1 Installable base units ..........................2- 4...
Page 8

COMMUNICATION THAT DO NOT REQUIRE THE SEQUENCE PROGRAM 7-1 to 7-38 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...
Page 9

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...
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: Overview

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. Software Configuration...
Page 12: Aj71pb96f/a1sj71pb96f Characteristics

1. OVERVIEW MELSEC-A 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.
Page 13: System Configuration

2. SYSTEM CONFIGURATION MELSEC-A 2. SYSTEM CONFIGURATION This section explains system configuration for the AJ71PB96F/A1SJ71PB96F. Whole System Configuration (1) For the A1SJCPU A1SJCPU (S3) A1SJ71PB96F A1SJHCPU Extension cable A1SC[ ]B Extension base A1S6[ ]B(S1)/A1S5[ ]B(S1 (2) For the compact building block type CPU...
Page 14

(4) Peripheral equipment configuration AJ71PB96F/ A1SJ71PB96F *1 Provided by the user Pin assignment AJ71PB96F/ IBM PC/AT RS-232 A1SJ71PB96F RS-232C (9 pin) (9 pin) Connection cable *1 IBM PC/AT or 100% compatible Utility software package SW0IX-PROFPE (Software version B or later...
Page 15: Applicable Cpu Modules

2. SYSTEM CONFIGURATION MELSEC-A 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 A1SJCPU, A1SJCPU-S3, A1SCPU, A1SCPU-S1, A2SCPU, A2SCPU-S1,...
Page 16: System Configuration Precaution Items

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.
Page 17: Combining With The Melsecnet (ii), Melsecnet/b, Or Melsecnet/10

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.
Page 18

2. SYSTEM CONFIGURATION MELSEC-A (2) MELSECNET/10 (for networks between PCs) (a) MELSECNET/10 two-layer system Mp : NET/10 control station 1Ns2 1Mp1 PROFIBUS other station Ns : NET/10 normal station (AnUCPU, A2ASCPU) NET/10 (No.1) N : NET/10 normal station (CPU other than 1Ns4 PROFIBUS other station AnU/A2AS)
Page 19

2. SYSTEM CONFIGURATION MELSEC-A (c) MELSECNET/10 and MELSECNET (II) mixed systems • When the intermediate terminal is an AnUCPU/A2ASCPU 1Ns1 PROFIBUS other station NET/10 (No.1) PROFIBUS other station 1Mp4 1Ns3 NET (II) PROFIBUS PROFIBUS other station other statio Stations accessible from the PROFIBUS other stations Installable 1Ns3/ stations...
Page 20

2. SYSTEM CONFIGURATION MELSEC-A (3) MELSECNET/10 (for remote I/O networks) (a) MELSECNET/10 two-layer system Mp : NET/10 control station PROFIBUS other station Ns : NET/10 normal station (AnUCPU, A2ASCPU) NET/10 (No.1) N : NET/10 normal station (CPU other than AnU/A2AS) Mr : NET/10 remote I/O master M : NET (II) master station : NET (II) local station...
Page 21

2. SYSTEM CONFIGURATION MELSEC-A (c) MELSECNET/10 and MELSECNET(II) compound system • When the intermediate station is an AnUCPU/A2ASCPU 1Ns1 PROFIBUS other station NET/10 (No.1) PROFIBUS other station 1Mp4 1Ns3 NET (II) PROFIBUS PROFIBUS other station other station NET/10 (No.2) Stations accessible from the PROFIBUS other stations Installable 1Ns3/ 1Mp4/...
Page 22

2. SYSTEM CONFIGURATION MELSEC-A • When the intermediate station is other than the AnUCPU/A2ASCPU 1Ns1 PROFIBUS other station NET/10 (No.1) PROFIBUS other station 1Mp4 NET (II) PROFIBUS PROFIBUS other station other station NET/10 (No.2) Stations accessible from the PROFIBUS other stations Installable 1N3/ 1Mp4/...
Page 23: Specifications

3. SPECIFICATIONS MELSEC-A 3. SPECIFICATIONS This section explains the AJ71PB96F/A1SJ71PB96F the general specifications, performance specifications, and transmission specifications. General Specification This section explains the AJ71PB96F/A1SJ71PB96F general specifications. Table 3.1 General Specification Item Specifications Ambient operating ° 0 to 55 temperature °...
Page 24: Performance Specifications

3. SPECIFICATIONS MELSEC-A 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 Synchronization method Asynchronous Electrical standards and characteristics EIA-RS485 compliance...
Page 25

3. SPECIFICATIONS MELSEC-A Transmission line Items Specifications Remarks PROFIBUS cable impedance Twisted pair cable User distribution Ω 100 to 120 (>100kHz) Capacity <60nF/km Ω Conductor resistance <160 Conductor cross section area >0.22mm Terminal resistance Set yes/no by the main module VP (6) switch 390Ω...
Page 26: Installation Specifications

3. SPECIFICATIONS MELSEC-A 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 ...
Page 27: Functions

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...
Page 28: Communication Relationship

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.
Page 29: Crl Setting Items And Default Values

4. FUNCTIONS MELSEC-A 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...
Page 30

4. FUNCTIONS MELSEC-A 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.
Page 31

4. FUNCTIONS MELSEC-A Max send PDU(L): This is the maximum size of a packet sent by low priority. Cyclic communication data is sent by low priority. Max Receive PDU(H): This is the maximum size of a packet received by high priority. Acyclic communication data is received at high priority.
Page 32: Support Service

4. FUNCTIONS MELSEC-A Support Service 4.4.1 FMS remote service Symbol meanings 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. Contains server functions For confirmed service, has the capability to receive instruction primitives and to transmit answer primitives.
Page 33

4. FUNCTIONS MELSEC-A Communication MSAC_SI/D MSAC_SI/O MSCY/D MSCY/O type Master Slave Master Slave Master Slave Master Slave emulation emulation emulation emulation Service   Initiate   Abort   Reject      Status   UnsolicitedStatus ...
Page 34

4. FUNCTIONS MELSEC-A Communication MSCY_SI/D MSCY_SI/O BRCT/ type MULT Master Slave Master Slave Service emulation emulation   Initiate   Abort  Reject      Status  UnsolicitedStatus      Identify   ...
Page 35: Fma7 Remote Service

4. FUNCTIONS MELSEC-A 4.4.2 FMA7 remote service Symbol meanings 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. Contains survey functions For confirmed service, has the capability to receive instruction primitives and to transmit answer primitives.
Page 36: Object Dictionary (od)

The copy retained by the client is called the remote 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...
Page 37

*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 •...
Page 38

4. FUNCTIONS MELSEC-A The following symbols are used for the above device names. Device Device name Device Device name symbol symbol Input Timer setting value (main) Output Timer setting value (sub) Latch relay Counter setting value (main) Internal relay Counter setting value (sub) Special relay Accumulator Annunciator...
Page 39

4. FUNCTIONS MELSEC-A Local OD abbreviations INDEX Object type Object dependent data Name (32 Data structure (data type INDEX/length) characters) Data type Boolean Data type Integer16 Data type BitStr Structured data type ------ (Boolean/1), (Interger16/2),..(Maximum 10 units) Name (32 Data Number of INDEX Local address...
Page 40

4. FUNCTIONS MELSEC-A 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 Boolean M0 to M4096 132 to 147 Unsigned16 TN0 to TN1023 148 to 155...
Page 41: Remote Od

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.
Page 42

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...
Page 43: I/o Signal List

(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

MELSEC-A (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).
Page 45: Buffer Memory

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.
Page 46: Information Area Explanation

4. FUNCTIONS MELSEC-A 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. Adress (decimal) Number of communications set up (maximum 32)
Page 47: Network Trouble Information Area

4. FUNCTIONS MELSEC-A 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. Adress (decimal) Trouble type 1376...
Page 48

4. FUNCTIONS MELSEC-A (2) When the trouble type is 200h (network trouble): Code 1 in type Code 2 in type Description Counter measure FMA7 event FMA7 event instance ID cause code The same address has been Check the addresses of the network defined twice.
Page 49: Timing Chart

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.
Page 50

4. FUNCTIONS MELSEC-A (2) When unconfirmed service is received: 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.
Page 51

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.
Page 52: Procedures Before System Operation

5. PROCEDURES BEFORE SYSTEM OPERATION MELSEC-A 5. PROCEDURES BEFORE SYSTEM OPERATION Procedures before Operation The procedure for newly connecting AJ71PB96F/A1SJ71PB96F to an existing PROFIBUS-FMS network is explained below. Startup Install the AJ71PB96F/A1SJ71PB96F in the PC base unit. Connect the AJ71PB96F/A1SJ71PB96F and the network with a twisted pair cable.
Page 53

Preloaded the partner station OD information in the AJ71PB96F/ A1SJ71PB96F? 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.
Page 54: Handling Precautions

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.
Page 55: Part Names And Settings

A1SJ71PB96F Name Description Remark Displays the AJ71PB96F/A1SJ71PB96F status. Name Display description 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.
Page 56

5. PROCEDURES BEFORE SYSTEM OPERATION MELSEC-A Name Description Remark Mode setting switch This sets the AJ71PB96F/A1SJ71PB96F operation status. (at time of shipment: 0) Switch No. MODE Online mode Parameter setting mode Self-diagnosis mode (refer to section 4.5) 3 to F...
Page 57: Self-diagnosis Execution Method

(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).
Page 58: Wiring

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,...
Page 59: Precautions Against Wiring

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.
Page 60

5. PROCEDURES BEFORE SYSTEM OPERATION MELSEC-A (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: Maintenance And Inspection

MELSEC-A 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.
Page 62: Communications That Require The Sequence Program

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.
Page 63: Information Report

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A (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.
Page 64

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A (2) Request answer area 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. •...
Page 65: Fms Communication Circuit Abort With Partner Station (abort: Requester)

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A FMS Communication Circuit Abort With Partner Station (Abort: Requester) This command aborts the connection. (1) Request area 0020h 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: Partner Station Status Read (status: Client)

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A Partner Station Status Read (Status: Client) This command is used to acquire the server station status. (1) Request area 0040h Status comman CREF No. (2) Request answer area Same as Initiate. (3) Data area Logical Status*1 Physical Status*2 Local Detail*3...
Page 67: Partner Station Identification Information Read (identify: Client)

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A Partner Station Identification Information Read (Identify: Client) This command is used to check the server station identification information. (1) Request area 0060h Identify comman CREF No. (2) Request answer area Same as for Initiate. (3) Data area Vendor name length The length of the vendor...
Page 68: Partner Station Variable Read (read: Client)

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A 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 Read command (selected depending on the bit-String data storage method difference) 01a0 or 01a1 h...
Page 69

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A (1-2) When the access mode is name Read command (selected depending on the bit-String data storage method 01a0 or 01a1 h CREF No. Always set to 1. (access mode Variable name length Variable name maximum 32 characters Subindex No.
Page 70

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A (2-2) During normal end (when the access mode is name) 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) *...
Page 71

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A 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.
Page 72

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A (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) Address : False 0 or NOT 0FFh : True (b) Integer (Integer, Unsigned) •...
Page 73

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A (d) Octet string (OctetString) When the value is 01h, 02h, 03h, 04h, 05h then the octet string is set as shown below. (e) Character string (VisibleString) When the value is “ABCDE,” the visible string is set as shown below. Floating point (FloatingPoint) This is the same format as for the AnACPU or AnUCPU, and is set from the 1536 address.
Page 74: Partner Station Variable Write (write: Client)

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A 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) Write command (selected depending upon the bit-String data storage method difference) 01c0 or 01c1 h CREF No.
Page 75

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A 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.
Page 76: Pc Cpu Variable Report (information Report: Requester)

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A 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. MMAC client and server MSAC, MSAC_SI, MSCY, MSCY_SI clients MSAC_SI, MSCY_SI server BRCT/MULT requester...
Page 77

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A (2-2) When the access mode is name InformationReport command (selected depending on the bit-String data storage method difference) 01e0 or 01e1 h CREF No. Specify the transmission destination CREF No Always set to 1. Variable name length Variable name maximum 32 characters...
Page 78: Pc Cpu Status Report (unsolicitedstatus: Requester)

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A 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. MMAC client and server MSAC, MSAC_SI, MSCY, MSCY_SI client MSAC_SI, MSCY_SI server BRCT/MULT request...
Page 79: Reporting The Partner Station Variable Data To The Pc Cpu (information Report: Receiver)

• 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.
Page 80

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A 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.
Page 81

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A 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.
Page 82

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A 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)
Page 83: Reports To The Partner Station Status Pc Cpu (unsolicited Status: Receiver)

• 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.
Page 84: Fma7 Connection Abort (fma7 Abort: Receiver)

6. COMMUNICATIONS THAT REQUIRE THE SEQUENCE PROGRAM MELSEC-A 6.13 FMA7 Connection Abort (FMA7 Abort: Receiver) This command is used when the PC CPU aborts the FMA7 connection. (1) Receive area 2020 Abort comman CREF No. Always set to 1. (2) Receive answer area The same as for Initiate.
Page 86: Communication That Do Not Require The Sequence Program

AJ71PB96F/A1SJ71PB96F is operating as a server. 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...
Page 87

7. COMMUNICATION THAT DO NOT REQUIRE THE SEQUENCE PROGRAM MELSEC-A • 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 •...
Page 88

(0 ≤ m ≤ 23) 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] •...
Page 89

7. COMMUNICATION THAT DO NOT REQUIRE THE SEQUENCE PROGRAM MELSEC-A • 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...
Page 90: Aj71pb96f/a1sj71pb96f Connection Abort (abort: Receiver)

MELSEC-A 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.
Page 91: Service Reject (reject)

7. COMMUNICATION THAT DO NOT REQUIRE THE SEQUENCE PROGRAM MELSEC-A 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: Pc Cpu Status Information (status: Server)

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).
Page 93: Aj71pb96f/a1sj71pb96f Identification Information (identify: Server)

7. COMMUNICATION THAT DO NOT REQUIRE THE SEQUENCE PROGRAM MELSEC-A 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.
Page 94: Object Attribute Acquisition (getod: Server)

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.
Page 95

7. COMMUNICATION THAT DO NOT REQUIRE THE SEQUENCE PROGRAM MELSEC-A [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...
Page 96: Initiate Objects Attribute Setting (initiateputod: Server)

7. COMMUNICATION THAT DO NOT REQUIRE THE SEQUENCE PROGRAM MELSEC-A 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. Server Clien InitiatePutOD.request InitiatePutOD.response PutOD.reques PutOD.response...
Page 97

• This means that ODs that are unused in other connections will be Reload, not free of Interacting overwritten. • The A1SJ71PB96F will forcefully abort other connections. • The VFD LogicalStatus will be changed to OD-LOADING-NON- INTERACTING. • This means that the entire OD will be overwritten.
Page 98: 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.
Page 99: Reading Device Memory And Buffer Memory (read: Server)

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.
Page 100: Writing Device Memory And Buffer Memory (write: Server)

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...
Page 101: Reading Program Capacity And Comment Capacity, Etc. (read: Server)

This specifies which element will be read. When a Subindex is not specified all of the elements will be read. The Array header element Subindex is 1. [Server (AJ71PB96F/A1SJ71PB96F) answer parameters] • Data The special array variable data format is as follows.
Page 102: Initiating Program, Parameter, And Comment, Device Buffer Memory Download (initiatedownloadsequence: Server)

[Parameters required by the client] • Access Specification Specify the Index and Name of the domain to be registered in the OD. Access Specification Setting value Index Domain Index Variable Name Domain Name [Server (AJ71PB96F/A1SJ71PB96F) answer parameters] None 7-17...
Page 103: Program, Parameter, Comment, Device And Buffer Memory Downloads (downloadsegument: Server)

MELSEC-A 7.1.14 Program, parameter, comment, device and buffer memory downloads (DownloadSegument: Server) DownloadSegument is conducted from the AJ71PB96F/A1SJ71PB96F after normal end of the InitiateDownloadSequence. [Server (AJ71PB96F/A1SJ71PB96F) transmission parameters] • Access Specification The Index or Name of the domain specified by InitiateDownloadSequence is specified.
Page 104: Program, Parameter, Comment, Device, And Buffer Memory Download Termination (terminatedownloadsegument: Server)

(TerminateDownloadSegument: Server) When the MoreFollows parameter of the DownloadSegument.response is False, or the data received using DownloadSegument.response was not correctly written into the PC CPU, a TerminationDownloadSegument is transmitted from the AJ71PB96F/A1SJ71PB96F. [Server (AJ71PB96F/A1SJ71PB96F) answer parameters] • Access Specification The Index or Name of the domain specified by InitiateDownloadSequence is specified.
Page 105: Initiating Program, Parameter, Comment, Device, And Buffer Memory Upload (initiateuploadsequence: Server)

[Parameters required by the client] • Access Specification Specify the Index or Name of the domain registered in the OD. Access Specification Setting value Index Domain Index Variable Name Domain Name [Server (AJ71PB96F/A1SJ71PB96F) answer parameters] None 7-20...
Page 106: Uploading Program, Parameter, Comment, And Device Buffer Memories (uploadsegument: Server)

• Load Data The read data is set. Note The AJ71PB96F/A1SJ71PB96F transmits the data in 128 byte units. For this reason, make the CRL Max send PDU (low) value 200 or more. • More Follows This notifies whether or not data remains to be uploaded.
Page 107: Termination Of Upload Of Program, Parameter, Comment, And Device Buffer Memories (terminateuploadsegument: Server)

[Parameters required by the client] • Access Specification The Index or Name of the domain specified by InitiateUploadSequence is specified. Access Specification Setting value Index Domain Index Variable Name Domain Name [Server (AJ71PB96F/A1SJ71PB96F) answer parameters] None 7-22...
Page 108: Execution Program Definition (create Program Invocation: Server)

For the sequence program to be operated from the client the Program Invocation for the main sequence program domain is defined. In the AJ71PB96F/A1SJ71PB96F only the Program Invocation can be allocated to the main sequence program domain. The sub sequence program cannot be allocated.
Page 109

7. COMMUNICATION THAT DO NOT REQUIRE THE SEQUENCE PROGRAM MELSEC-A • List of Domains Specify the sequence program domain INDEX or Name. In the AJ71PB96F/A1SJ71PB96F 1 domain can be allocated to 1 Program Invocation. List of Domains Setting value Index Domain Index...
Page 110: Execution Program Delete (delete Program Invocation: Server)

Status after execution NON-EXISTENT NON-EXISTENT [Parameters required by the client] • Access Specification Specify the Index or Name of the Program Invocation to be deleted. Access Specification Setting value Index PI Index PI Name PI Name [Server (AJ71PB96F/A1SJ71PB96F) answer parameters] None 7-25...
Page 111: Program Run (start: Server)

Use the GetOD service to check the PI status. [Parameters required by the client] • Access Specification Specify the Index or Name of the Program Invocation to be started up. Access Specification Setting value Index PI Index PI Name PI Name [Server (AJ71PB96F/A1SJ71PB96F) answer parameters] None 7-26...
Page 112: Program Pause (stop: Server)

Use the GetOD service to check the PI status. [Parameters required by the client] • Access Specification Specify the Index or Name of the Program Invocation to be paused. Access Specification Setting value Index PI Index PI Name PI Name [Server (AJ71PB96F/A1SJ71PB96F) answer parameters] None 7-27...
Page 113: Program Pause Cancel (resume: Server)

Use the GetOD service to check the PI status. [Parameters required by the client] • Access Specification Specify the Index or Name of the Program Invocation to be RUN. Access Specification Setting value Index PI Index PI Name PI Name [Server (AJ71PB96F/A1SJ71PB96F) answer parameters] None 7-28...
Page 114: Program Stop (reset: Server)

Use the GetOD service to check the PI status. [Parameters required by the client] • Access Specification Specify the Index or Name of the Program Invocation to be stopped. Access Specification Setting value Index PI Index PI Name PI Name [Server (AJ71PB96F/A1SJ71PB96F) answer parameters] None 7-29...
Page 115: Fma7 Service

CRL for FMS that could previously only be done using the utility SW0IX-PROFPE. To use the FMA7 service function the communication for FMA7 must be set in the AJ71PB96F/ A1SJ71PB96F using the SW0IX-PROFPE. The communication No. is fixed as No.1. (PROFIBUS-FMS prescribed) 7.2.1...
Page 116: Fma7 Connection Initiation (fma7 Initiate: Responder)

Feature Supported (n+8)th bit (0 ≤ n ≤ 8) ≥ Feature Supported (m+8)th bit Feature Supported (m)th bit (0 ≤ m ≤ 8) Note The Feature Supported value in AJ71PB96F/A1SJ71PB96F is fixed to 00 78 00 00 00 00 (hex). 7-31...
Page 117: Fma7 Connection Connection Abort (fma7 Abort: Receiver)

FMA7 Connection connection abort (FMA7 Abort: Receiver) A "FMA7 Abort" service from is issued to abort the connection of the FMA7 connection. When the AJ71PB96F/A1SJ71PB96F receives a FMA7 Abort the logical connection changes to the abort status. "Abort" is automatically issued and received when there is an error in the FMA7 protocol or parameters.
Page 118: Crl Setting Initiate (initiateloadcrl: Server)

7. COMMUNICATION THAT DO NOT REQUIRE THE SEQUENCE PROGRAM MELSEC-A 7.2.5 CRL setting initiate (InitiateLoadCRL: Server) When the CRL is set in the AJ71PB96F/A1SJ71PB96F the 3 services of InitiateLoadCRL, LoadCRL, and TerminateLoadCRL. Server Clien (A1SJ71PB96F) InitiateLoadCRL.reques InitiateLoadCRL.response LoadCRL.request LoadCRL.response (Repeat) LoadCRL.request...
Page 119: Crl Setting (loadcrl: Server)

LoadCRL must be repeated once for each CRL to be loaded. [Parameters required by the client] • CRL Entry static (CRL entry static portion) Set the CRL entry static portion. [Server (AJ71PB96F/A1SJ71PB96F) answer parameters] None 7.2.7 CRL setting end (TerminateLoadCRL: Server) This is used to announce that the CRL setting has ended.
Page 120: Crl Read (readcrl: Server)

Specify the No. of the CRL entry to be read. Desired CREF Explanation Reads the CRL header. No. of the CRL entry to be read. CRL Entry No. to read [Server (AJ71PB96F/A1SJ71PB96F) answer parameters] None • CRL Entry This sets the CRL Entry data. 7-35...
Page 121: Bus Parameter Read (readvalue: Server)

7. COMMUNICATION THAT DO NOT REQUIRE THE SEQUENCE PROGRAM MELSEC-A 7.2.9 Bus parameter read (ReadValue: Server) Use ReadValue to read the AJ71PB96F/A1SJ71PB96F bus parameters from the client. [Parameters required by the client] • Variable Identifier Parameters types for reading the Variable Identifier Vriable Identifier...
Page 122

7. COMMUNICATION THAT DO NOT REQUIRE THE SEQUENCE PROGRAM MELSEC-A [Server (AJ71PB96F/A1SJ71PB96F) answer parameters] • Current Value The following values are set using the Variable Identifier value. Vriable Identifier Current Value Address Addresses 0 to 126 set by the software package.
Page 123: Bus Parameter Setting (setvalue: Server)

MELSEC-A 7.2.10 Bus parameter setting (SetValue: Server) Use the SetValue to set the parameter in the AJ71PB96F/A1SJ71PB96F from the client. [Parameters required by the client] • Variable Identifier Set the parameter type to be set as shown in the following table.
Page 124: Troubleshooting

Refer to Sections 4.7.2 and 8.2.1 to check the error code descriptions read from the AJ71PB96F/A1SJ71PB96F. (b) Use the partner station with which the AJ71PB96F/A1SJ71PB96F is communicating to read the error codes returned from the AJ71PB96F/A1SJ71PB96F. Refer to Section 8.2.2 and check the causes of the error codes returned by the AJ71PB96F/A1SJ71PB96F.
Page 125: Error Code

8. TROUBLESHOOTING MELSEC-A Error Code 8.2.1 Answer area, receive area Following is shown the error codes set in the buffer memory request answer area and receive area. (1) Error codes Request answer area No. 1 → buffer memory address 66 address Request answer area No.
Page 126

8. TROUBLESHOOTING MELSEC-A (b) Initiate Error Description Counter measure code 2055h A FMS refusal answer is received. Refer to the error information and then check the data set in the buffer memory. 2061h An initiate request to the partner station for Set the correct connection No.
Page 127

8. TROUBLESHOOTING MELSEC-A (d) Status Error Description Counter measure code 2055h A FMS refusal response is received. Refer to the error information and then check the data set in the buffer memory. 205Fh A time up occurs during the timer monitoring Check the transmission route status and period.
Page 128

8. TROUBLESHOOTING MELSEC-A (g) Read Error Description Counter measure code 2053h A data type incorrect for the remote OD is Set the correct data type. specified. 2055h A MMS refusal response is received. Refer to the error information and check the data set in the buffer memory.
Page 129

8. TROUBLESHOOTING MELSEC-A (h) Write Error Description Counter measure code 2053h A data type incorrect for the remote OD is Set the correct data type. specified. 2055h A MMS refusal response is received. Refer to the error information and check the data set in the buffer memory.
Page 130

8. TROUBLESHOOTING MELSEC-A InformationReport Error Description Counter measure code 2201h The request transmission conditions are Check the connection attributes and station incorrect. attributes (master and slow) parameters. 2202h An incorrect access mode was specified. Specify the correct access mode. 2204h An undefined local station object (NULL) was Set the correct OD index/name.
Page 131: Communication Circuits

8. TROUBLESHOOTING MELSEC-A 8.2.2 Communication circuits Following is shown the error code that is returned to the partner station via the communication circuit. (1) Connection control (a) Initiate Class Code Cause • The number of maximum simultaneous Initiate (0) E_INIT_MAX_PDU_SIZE_INSUFF (1) processing services is incorrect.
Page 132

8. TROUBLESHOOTING MELSEC-A (4) Variable access (a) Common Class Code Cause • A data length was exceeded 128 bytes. ACCESS (6) E_ACCESS_OBJ_ACCESS_ UNSUPP (6) • A variable name was specified even though E_ACCESS_NAME_ACCESS_ UNSUPP (9) variable name access is not supported. •...
Page 133

8. TROUBLESHOOTING MELSEC-A (5) Domain control (a) Download Class Code Cause • An attempt was made to write data that is RESOURCE (4) E_RESOURCE_MEM_ UNAVAILABLE (1) larger than the capacity specified in the CPU parameter. • An attempt to download was made to a SERVICE (5) E_SERV_OBJ_STATE_CONFLICT domain that is not in the EXISTENT status.
Page 134

Class Code Cause • The specified CRL entry does not exist. CRL (6) E_FMA7_CRL_NO_CRL_ENTRY (9) Bus parameter control (a) SetValue Class Code Cause • A value that is not used by the USER (6) E_FMA7_USR_OTHERS (3) AJ71PB96F/A1SJ71PB96F was specified. 8-11...
Page 135: Appendix

MELSEC-A APPENDIX Appendix 1 Differences From the AJ71PB96 Following is an explanation between the AJ71PB96F/A1SJ71PB96F and the AJ71PB96. (1) Number of communications (a) AJ71PB96 If all of the PDU sizes for all of the communications are 200 or less; 32 communications.
Page 136

231 bytes 200 bytes c) Information Report (Receive) service In the AJ71PB96F/A1SJ71PB96F, if variables are designated , the variable name is handled as 32fixed characters. Thus, the size that can be handled is constant regardless of the variable size. Access mode...
Page 137

• SW0IX-PB96PE (b) AJ71PB96F/A1SJ71PB96F • SW0IX-PROFPE(Ver. B or later) Precautionary notes when using an AJ71PB96 and an AJ71PB96F/A1SJ71PB96F simultaneously Precautionary notes when communicating between an AJ71PB96 and an AJ71PB96F/A1SJ71PB96F or a product of other manufacturer The communication data size for a new product can exceed 128 bytes when the combination of...
Page 138: Appendix 2 Dissimilarities Between A1sj71pb96f New Products (software Version C Or Later) And Conventional Products (software Version B Or Before)

232 bytes 232 bytes b) Write service In the AJ71PB96F/A1SJ71PB96F, if variables are designated , the variable name is handled as 32 fixed characters. Thus, the size that can be handled is constant regardless of the variable size. Access mode...
Page 139

APPENDIX MELSEC-A (2) The data sizes that can be used in the remote OD for each data type and variable type have been changed. Variable type Simple variable Array variable Record variable Data type Boolean (B0) O *4 O *8 Integer8 (I8) O *4 O *8...
Page 140: Precautionary Notes When Using An A1sj71pb96f New Product (software Version C Or Later) And A Conventional Product (software Version B Or Later) Simultaneously

Version B or Later) Simultaneously (1) Precautionary notes when communicating between an A1SJ71PB96F new product (software version C or later) and an A1SJ71PB96F conventional product (software version B or before) or a product of other manufacturer The communication data size for a new product can exceed 128 bytes when the combination of products used are as follows: O: Supports communication data size exceeding 128 bytes : Spec not changed...
Page 141: Appendix 3 Vdf Physical Status Criteria Table

APPENDIX MELSEC-A Appendix 3 VDF Physical Status Criteria Table PC CPU Status on M9008 Status of D9015 VDF Physical Occurrence of Value (Self-diagnosis Status Name Self-diagnosis Error Error) Key (CPU) Parameter Program Remote Operational Partially- Operational Inoperable STOP Needs- Other than Commissioning Other than Other than...
Page 142: Appendix 4 Din 19245 Part 2

APPENDIX MELSEC-A Appendix 4 DIN 19245 Part 2 Attribute FMS Features Supported Service Primitive bit [n] Primitive bit [m] Get OD (Long form) .req,.con .ind,.res UnsolicitedStatus .req .ind InitiatePutOD .req,.con .ind,.res PutOD .req,.con .ind,.res TerminatePutOD .req,.con .ind,.res InitiateDownloadSequence .req,.con .ind,.res DownloadSegment .ind,.res .ind,.con 27...
Page 143

APPENDIX MELSEC-A Attribute FMA7 Services Supported Service Primitive bit [n] Primitive bit [m] reserved *) .req,.con .ind,.res InitiateLoad-CRL-Rem .req,.con .ind,.res Load-CRL-Rem, .req,.con .ind,.res TerminateLoad-CRL-Rem .req,.con .ind,.res Read-CRL-Rem .req,.con .ind,.res SetValueRem .req,.con .ind,.res ReadValueRem .req,.con .ind,.res LSAP-StatusRem .req,.con .ind,.res IdentRem .req,.con .ind,.res reserved *) .req,.con...
Page 144: Appendix 5 Maximum Service Counter

APPENDIX MELSEC-A Appendix 5 Maximum Service Counter The maximum service counter (SCC, RCC, SAC, RAC) is used with layer 7 (LLI). The setting ranges for each connection type are shown below. Connection Type : MMAC MASTER 0 to 1 0 to 2 0 to 1 0 to1 Connection Type : MSAC...
Page 145: Appendix 6 External Dimensions

APPENDIX MELSEC-A Appendix 6 External Dimensions (1) AJ71PB96F (0.17 AJ71PB96F SD/RD TOKEN READY FROM/TO PRM SE FAULT 0:ONLINE MODE 1:PRM SET 2:TES RS-232- PROFIBUS BUS TERMINATION (0.17 106 (4.17) 37.5 (1.48 unit: mm (inch A-11...
Page 146

APPENDIX MELSEC-A (2) A1SJ71PB96F A1SJ71PB96F TEST SD/RD TOKEN READY FROM/TO PRM SET FAULT MODE 0:ONLINE 1:PRM SET 2:TEST RS-232-C PROFIBUS BUS TERMINATION A1SJ71PB96F 93.6 (3.69 34.5(1.36) (0.26 (0.16 Unit : mm (inch) A-12...
Page 148

MITSU BIS HI ELECTRIC Prin ted in Ger ma ny / 10.98 MITSU BIS HI ELECTRIC EU RO PE B.V. FAC TO RY AU TO MA TION GOTHA ER STR. 8, D- 40880 RA TIN GEN PHO NE: +49 2102 486 0, FAX: +49 2102 486 717...

This manual also for:

Aj71pb96f

Mitsubishi Electric A1SJ71PB96F User Manual

Related Manuals for Mitsubishi Electric A1SJ71PB96F

Summary of Contents for Mitsubishi Electric A1SJ71PB96F

This manual also for:

Comments to this Manuals