Mitsubishi Electric A1SJ71DN91, AJ71DN91 User Manual

Download

Page 1

A1SJ71DN91,

AJ71DN91

User’s manual

_______________________________________________________________________________________________________

SHNA 4004A

Page 2

REVISIONS

*The manual number is given on the bottom left of the back cover.

Print Date *Manual Number Revision

Oct., 1998 SH (NA) -4004-A First edition

This manual confers no industrial property rights or any rights of any other kind, nor does it confer any patent licenses. Mitsubishi Electric Corporation cannot be held responsible for any problems involving industrial property rights which may occur as a result of using the contents noted in this manual.

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

CAUTION

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.

[System Design Precautions]

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

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

DANGER

• If a communication error occurs in the network of the DeviceNet, the communication error station enters the state

shown below. (1) The master station (AJ71DN91, A1SJ71DN91) holds the data that was input from a slave station before the

occurrence of a communication error.

(2) Whether the output signal of the slave station goes OFF or is retained depends on the slave station

specifications or the parameter setting at the master station. Create the interlock circuit on a sequence program which uses the communication state of the slave stations so that the system operation is secured. At the same time, a safety system must be provided outside the slave station.

CAUTION

• Do not bundle control lines or communication wires together with main circuit or power lines, or lay them close to

these lines. As a guide, separate these lines by a distance of at least 100 mm, otherwise malfunctions may occur due to noise.

Page 4

[Cautions on Mounting]

CAUTION

• Use the PC in an environment that conforms to the general specifications in the manual.

Using the PC in environments outside the ranges stated in the general specifications will cause electric shock, fire, malfunction, or damage to/deterioration of the product.

• Make sure that the module fixing projection on the base of the module is properly engaged in the module fixing hole

in the base unit before mounting the module.(A(1S)J71DN91 must be screwed to the base unit with the specified torque.) Failure to mount the module properly will result in malfunction or failure, or in the module falling.

• Do not touch conductive parts or electronic components of the module with your bare hands.

This could cause malfunction or failure of the module.

[Cautions on Wiring]

DANGER

• Switch off all phases of the power supply outside the PC before starting installing or wiring work.

If all phases are not switched off, there will be a danger of electric shock or damage to the product.

CAUTION

• Connect the FG terminal to a dedicated PC ground connection with class 3 grounding or higher.

Failure to do this may result in malfunction.

• Tighten terminal screws to the prescribed torque.

Loose terminal screws can cause shorting and malfunctions.

• Make sure that no foreign matter such as chips or wire offcuts gets inside the module.

It will cause fire, failure, or malfunction.

• The communication cables and power cables connected to the unit must be enclosed in a duct or fixed with clamps.

Failure to do this can result in malfunction due to damage to the unit or cables or defective cable contact caused by looseness or movement of the cables or accidental pulling on the cables.

• When disconnecting a communication cable and power cable from the unit, do not pull on the cable itself.

If the cable has a connector, pull on the connector to disconnect it from the unit. If the cable has no connector, loosen the screw where the cable attaches to the unit before disconnecting the cable. Pulling on a cable while it is connected to the unit can damage the unit or cable, or cause malfunctions due to defective cable contact. Always turn off all external power supply phases before touching any terminals. Failure to do this may result in malfunction.

Page 5

[Cautions on Startup and Maintenance]

CAUTION

• Always turn off all external power supply phases before touching any terminals.

Failure to do this may result in malfunction.

• Always turn off all external power supply phases before cleaning or tightening the terminal screws.

Failure to do this may result in malfunction.

• Do not disassemble or modify any module.

This will cause failure, malfunction, injuries, or fire.

• Always turn off all external power supply phases before mounting or dismounting the unit.

Failure to do this may result in malfunction or damage to the unit.

[Cautions on Disposal]

CAUTION

• Dispose of this product as industrial waste.

Page 6

INTRODUCTION

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

1. OUTLINE 1 – 1 ~ 1 – 8

1.1 Features.........................................................................................................................................1 – 1

1.2 Communication Outline...................................................................................................................1 – 3

1.2.1 Network configuration........................................................................................................1 – 3

1.2.2 Outline of parameter settings.............................................................................................1 – 5

1.2.3 Outline of DN91 - slave station communication...................................................................1 – 5

2. SYSTEM CONFIGURATION 2 – 1 ~ 2 – 6

2.1 Overall Configuration......................................................................................................................2 – 1

2.1.1 Sample system configuration connected with a trunk line....................................................2 – 1

2.1.2 Sample system configuration connected with a drop line.....................................................2 – 1

2.1.3 System configuration with a DeviceNet master unit.............................................................2 – 2

2.2 Applicable Systems ........................................................................................................................2 – 3

2.2.1 Mountable CPUs and number of units................................................................................2 – 3

2.2.2 Important points about the system configuration................................................................. 2 – 4

2.2.3 Operating environment of the configuration software (parameter setting tool)......................2 – 5

2.3 Products Connectable to a Slave Station.........................................................................................2 – 6

3. SPECIFICATIONS 3 – 1 ~ 3 – 26

3.1 General Specifications....................................................................................................................3 – 1

3.2 Performance Specifications .............................................................................................................3 – 2

3.2.1 Maximum transfer distance for thick cable/thin cable combination.......................................3 – 2

3.3 PC CPU I/O Signals........................................................................................................................3 – 3

3.3.1 Table of I/O signals............................................................................................................3 – 3

3.3.2 I/O signal details ............................................................................................................... 3 – 5

3.4 Buffer Memory................................................................................................................................3 – 8

3.4.1 Buffer memory table..........................................................................................................3 – 8

3.4.2 Details of the buffer memory..............................................................................................3 – 9

− i −

Page 7

4. FUNCTIONS 4 – 1 ~ 4 – 5

4.1 I/O Communication Functions .........................................................................................................4 – 1

4.2 Message Communication Functions................................................................................................4 – 3

4.2.1 Get attribute ......................................................................................................................4 – 3

4.2.2 Set attribute......................................................................................................................4 – 4

4.2.3 Read communication error information...............................................................................4 – 5

5. SETTINGS AND PROCEDURES BEFORE OPERATION 5 – 1 ~ 5 – 10

5.1 Settings and Procedures.................................................................................................................5 – 1

5.1.1 DN91 start-up procedure when setting parameters with a sequence program......................5 – 1

5.1.2 DN91 start-up when setting parameters with the configuration software ..............................5 – 2

5.2 Mounting and Installation ................................................................................................................ 5 – 3

5.2.1 Handling instructions.........................................................................................................5 – 3

5.2.2 Installation environment.....................................................................................................5 – 3

5.3 Nomenclature.................................................................................................................................5 – 4

5.4 LED Displays and Indicator Descriptions..........................................................................................5 – 5

5.5 Connecting Communication Cable to DN91.....................................................................................5 – 6

5.6 Instructions for Connecting the Network Power Supply.....................................................................5 – 7

5.6.1 Network power supply unit installation position...................................................................5 – 7

5.6.2 Calculating network power supply unit installation position and current capacity .................. 5 – 8

6. PARAMETER SETTINGS 6 – 1 ~ 6 – 7

6.1 Setting Parameter...........................................................................................................................6 – 1

6.2 Important Points about the Parameter Settings ................................................................................ 6 – 2

6.3 Setting with a Sequence Program ...................................................................................................6 – 2

6.4 Setting Parameters with the Configuration Software (Parameter Setting Tool)...................................6 – 3

6.4.1 Setting configuration..........................................................................................................6 – 3

6.4.2 Setting master parameters ................................................................................................6 – 4

6.4.3 Setting bus parameters ..................................................................................................... 6 – 5

6.4.4 Set the device (slave station) parameters...........................................................................6 – 6

7. PROGRAMMING 7 – 1 ~ 7 – 9

7.1 Important Points about Programming...............................................................................................7 – 1

7.2 System Configuration......................................................................................................................7 – 2

7.3 Setting Parameters with a Sequence Program.................................................................................7 – 4

7.4 I/O Communication with Slave Stations ...........................................................................................7 – 6

7.4.1 Reading slave station I/O data...........................................................................................7 – 6

7.4.2 Writing slave station I/O data.............................................................................................7 – 6

7.5 Message Communication ................................................................................................................7 – 7

7.5.1 Message communication – reading ....................................................................................7 – 7

7.5.2 Message communication – writing ..................................................................................... 7 – 8

7.6 Acquiring Error Information..............................................................................................................7 – 9

− ii −

Page 8

8. TROUBLESHOOTING 8 – 1 ~ 8 – 12

8.1 Troubleshooting Tables...................................................................................................................8 – 2

8.1.1 Troubleshooting by Symptom Type....................................................................................8 – 2

8.1.2 Problems due to incorrect parameter settings .....................................................................8 – 5

8.2 Troubleshooting Using LED Indications............................................................................................8 – 5

8.2.1 Errors caused by the master unit .......................................................................................8 – 5

8.2.2 Errors caused by incorrect parameter settings or abnormal network....................................8 – 6

8.3 Troubleshooting Using Error Codes.................................................................................................8 – 8

8.3.1 Communication error codes...............................................................................................8 – 8

8.3.2 Execution error codes for message communication..........................................................8 – 11

APPENDICES APP – 1 ~ APP – 4

APPENDIX 1 External View ...............................................................................................................APP – 1

1.1 AJ71DN91.................................................................................................................................APP – 1

1.2 A1SJ71DN91.............................................................................................................................APP – 2

APPENDIX 2 Parameter Setting Sheet ..............................................................................................APP – 3

APPENDIX 3 List of Communication Parameter with Each Maker’s Slave Station................................APP – 4

− iii −

Page 9

1. OUTLINE

1.1 Features

MELSEC-A

This manual gives information including the specifications and descriptions of parts of the AJ71DN91/A1SJ71DN91 DeviceNet Master Unit (hereafter AJ71DN91, A1SJ71DN91, or DN91), which is used in combination with the MELSEC-A/QnA Series PLC CPU. DN91 is the DeviceNet master station which controls the DeviceNet devices. See the DeviceNet Specifications (Release 2.0) Volume 1 and Volume 2 for details about the DeviceNet Specifications. DeviceNet is a registered trademark of the Open DeviceNet Vendor Association, Inc.

POINT

While it is considered connectable with most commercially available Device-Net products, we cannot guarantee the connectivity with products of other manufacturers.

This section describes the features of DN91. (1) Conforms to the DeviceNet specifications (Release 2.0).

(2) DN91 operates as the DeviceNet master station to permit I/O and message

(3) Each master unit can communicate with up to 63 slave stations.

(4) The communication method for I/O communication can be selected indepen-dently for

DeviceNet network

(5) I/O communication permits communication of 256 bytes of inputs (2048 points) and 256

communications with the DeviceNet slave stations.

each slave station from the following four methods prescribed for DeviceNet: polling, bit strobe, change of state, and cyclic. However, only one communication method can be selected for each slave station.

DN91

Polling

Bit strobe

Change of state

Cyclic

Slave station 1 Slave station 2 Slave station 3 Slave station 4

bytes of outputs (2048 points) in the edit mode.

(6) Each message communication can communicate 240-byte message data.

(7) Any of the following two methods may be used to set the DN91 parameters:

• Use TO command of the sequence program to set the parameters.

• Use the configuration software to set the parameters. (Refer to the Section 2.2.3 for

the configuration software.)

1 − 1

Page 10

1. OUTLINE MELSEC-A

REMARK

When a network analyzer is connected to monitor the DeviceNet network, DN91 is recognized as a product of the Hilscher company.

1 − 2

Page 11

1. OUTLINE

1.2 Communication Outline

1.2.1 Network configuration

The DN91-based DeviceNet network is configured as shown below.

MELSEC-A

Termination

resistance

Master station

Slave station Slave station

Tap

Drop line (branch)

Drop line

Network power

supply unit

(24 VDC)

Power tap

Slave station Slave station

Slave station

Trunk line

Termination

resistance

1) Up to 64 units can be connected including the master station (DN91) and slave stations.

2) The positions of the master station and slave stations are not fixed. They can be arranged at any position on the network.

3) The network comprises trunk lines and drop lines. A termination resistance must be connected to each end of a trunk line.

4) A network power supply must be connected to supply power to the network communication circuits in each station.

1 − 3

Page 12

1. OUTLINE MELSEC-A

(1) Network Specifications

This section describes the network specifications of a DeviceNet using DN91. (a) Communication Speed

The communication speed can be selected as 125, 250, or 500 kbaud using a sequence program or a configuration software. The maximum cable length depends on the communication speed. See 3.2 Performance Specifications for details.

(b) Network Power Supply Methods

The following methods are available to supply network power to each station:

1) Connect a dedicated power tap to the trunk line cable and connect a network power supply unit to it.

2) Supply power from the network power supply unit through network cables to each station.

REMARK

Contact ODVA or the ODVA Japan office for inquiries about the following devices required for the DeviceNet network configuration:

• Network power supply unit

• Power tap

• Tap

• Termination resistance

• Cable

Contact Details for ODVA

Open DeviceNet Vender Association, Inc.

Address 8222 Wiles Road, Suite 287, Coral Springs, FL 33067 USA TEL.305-340-5412 FAX.305-340-5413

ODVA Japan Office

Address The Japan Chapter of ODVA Kyoto Research Park 17, Chudoji Minami-Machi, Shimogyo Kyoto 600-8813 Japan TEL.075-315-9175 FAX.075-315-2898

1 − 4

Page 13

1. OUTLINE

1.2.2 Outline of parameter settings

Parameter setting is required in advance to communicate with slave stations. The parameters include DeviceNet communication speed, station number (MAC ID) of DN91, the number of I/O points of slave stations etc. They are set in any of the following methods and stored in separate areas of E2PROM inside DN91.

• Use the sequence program.

• Use the configuration software.

1.2.3 Outline of DN91 - slave station communication

Communication between the DN91 and slave stations is outlined below. (1) Outline of I/O Communication

I/O communication is a function to communicate I/O data with slave stations. An outline of I/O communication is shown below. See 4.1 I/O Communication Functions for details.

Buffer memory

MELSEC-A

Slave stationDN91PLC CPU

Device

FROM

X, Y, M, D, R

Input data area

(Up to 2048

points)

Output data area

(Up to 2048

points)

Input

Output

The following four I/O communication methods are available:

One of these four communication methods can be chosen to match the specification of each slave station.

1) Bit strobe

2) Polling

3) Change of state

4) Cyclic

1 − 5

Page 14

1. OUTLINE

Message

MELSEC-A

(2) Outline of Message Communication

Message communication is a function to read and write slave station attribute data. An outline of message communication is shown below. See 4.2 Message Communication Functions for details. (a) Reading attributes

Slave stationDN91PLC CPU

Device Class

D, R

Device

D, R

FROM

communication command area

Message

communication

result area

communication

data area

(Up to 240 byte)

Instance

Attribute Attribute

Instance

Attribute

Class

Instance

Attribute

Instance

Attribute Attribute Attribute

1 − 6

Page 15

1. OUTLINE

Message

MELSEC-A

(b) Writing attributes

Slave stationDN91PLC CPU

Device

D, R

Device

D, R

FROM

communication command area

Message

communication

data area

(Up to 240 byte)

Message

communication

result area

Class

Instance

Attribute Attribute

Class

Instance

Attribute

Instance

Attribute Attribute

Class

Instance

Attribute Attribute

Instance

Attribute

1 − 7

Page 16

1. OUTLINE

I/O

Device

MELSEC-A

D, R

FROM

DN91PLC CPU

Message communication command area

Slave information

storage area *

Message communication

result area

Message communication

data area

(Up to 240 byte)

communi-

cation

Slave station

Class 1

Instance

Attribute Attribute

Instance

Attribute Attribute Attribute

Class

Instance

Attribute Attribute Attribute

Instance

Attribute

*: Stores the status of each slave station during I/O communication.

1 − 8

Page 17

2. SYSTEM CONFIGURATION

This section describes the system configuration on DeviceNet.

2.1 Overall Configuration

A master station can communicate with up to 63 slave stations. Each station is connected via a tap on the trunk line or is directly connected to the trunk line. The system configuration using AJ71DN91/A1SJ71DN91 as the master station is described below.

2.1.1 A typical system configuration that connects with a trunk line

Termination

resistance

Slave station

Tap

Slave station

MELSEC-A

Slave stations: max. 63

stations

Power

supply: 24

VDC

Trunk line

Master station

DeviceNet master unit AJ71DN91/A1SJ71DN91

2.1.2 A typical system configuration that connects with a drop line

Termination

resistance

Tap

Drop line

Master station

Slave stationSlave station

DeviceNet master unit AJ71DN91/A1SJ71DN91

Trunk line

Slave stations: max. 63

stations

Power

supply: 24

VDC

2 − 1

Page 18

2. SYSTEM CONFIGURATION

2.1.3 System configuration with a DeviceNet master unit

DeviceNet network

CPU

STOP

RUN

L.CLR

RUN

ERROR

RESETRESET

CPU

PULL

PLC CPU

Trunk line or drop line

A1SJ71DN91

RUN L.RUN MS NS

DeviceNet

MELSEC-A

Main base

Extension Cable

Extension base

RS-232-C

DeviceNet master unit

AJ71DN91 A1SJ71DN91

RS-232C cross-cable

Configuration unit (*)

*: PC/AT-compatible computer + configuration software

2 − 2

Page 19

2. SYSTEM CONFIGURATION

2.2 Applicable Systems

This section describes important points regarding which CPU units can be used and the system configuration.

2.2.1 Mountable CPUs and number of units

Table 2.1 shows which PLC CPUs can be mounted and the number of units.

Mounting Position

A0J2CPU A0J2HCPU A1SCPU(S1) A1SHCPU A1SJCPU(S3) A1SJHCPU(S8) A1SCPUC24-R2 A2SCPU(S1) A2SHCPU(S1) A2ASCPU(S1/S30) Q2ASCPU(S1) Q2ASHCPU(S1) A1CPU A2CPU(S1)

PLC CPU

Data link and network

A3CPU A1NCPU A2NCPU(S1) A3NCPU A3MCPU A3HCPU A2ACPU(S1) A3ACPU A2UCPU(S1) A3UCPU A4UCPU Q2ACPU(S1) Q3ACPU Q4ACPU Q4ARCPU MELSECNET remote I/O station MELSECNET/B remote I/O station

MELSECNET/10 remote I/O station

Table 2.1 Mountable CPUs and Number of Units

Number of Mountable Units

A1SJ71DN91 AJ71DN91

Cannot be used

No restriction

Cannot be used

AJ72LP25 AJ72BR15

A1SJ72QLP25 AJ72QLP25 A1SJ72QBR15 AJ72QBR15

Cannot be used

MELSEC-A

No restriction

Cannot be used

No restriction

2 − 3

Page 20

2. SYSTEM CONFIGURATION

2.2.2 Important points about the system configuration

This section gives some important points about configuration of a DeviceNet network system.

(1) Maximum Number of Units

Units up to the number of CPU I/Os may be installed. The DN91 uses 32 I/O points and one slot.

(2) Applicable Base Units

The DN91 can be mounted in any main base unit or extension base unit slot, with the following exceptions.

(a) Avoid mounting the DN91 in an extension base unit with no power supply (A5 B,

A1S5 B extension base unit) as the power supply capacity may be insufficient. If the DN91 is mounted in this type of unit, select the power supply unit and extension cable with due consideration to the current capacity of the power supply unit and the voltage drop in the extension cable. See the user's manual of your PLC CPU for details.

(b) The DN91 cannot be mounted in the final slot of the A3CPU(P21/R21) expansion

7th stage.

MELSEC-A

(3) Not Mountable in MELSECNET(II), MELSECNET/B Remote I/O Station

DN91 cannot be mounted in a MELSECNET(II), MELSECNET/B remote I/O station.

(4) Cautions When Connecting Wiring

To avoid noise interference, separate DeviceNet communication cables, power cables, and I/O unit signal cables.

(5) No Remote Operation from Another Node

It is not enabled to read, write, or monitor the sequence program of the PLC CPU, which contains the DN91, and the data of slave stations via nodes on the DeviceNet.

2 − 4

Page 21

2. SYSTEM CONFIGURATION

2.2.3 Operating environment of the configuration software (parameter setting tool)

This section describes the operating environment when setting DN91 parameters with the configuration software. The configuration software is a peripheral device which installs the following configuration software in a personal computer to allocate communication data for each slave station to the DeviceNet master station.

(1) Configuration Software

SyCon Ver. 2.0.6.2 or later (Include DLL file Ver. 2.5.0.1 or later.)

(2) Operating Environment of the Configuration Software

The operating environment is shown below.

Table 2.2 Operating Environment

Item Environment

Personal computer PC/AT compatible personal computer CPU Intel 486 processor, or above OS Windows95, WindowsNT3.51, WindowsNT4.0 * Free disk space 10 Mbyte min. RAM 16 Mbyte min. Display resolution 800 x 600 dot, min. External storage CD-ROM drive (for installation only)

MELSEC-A

*: Registered trademark of Microsoft Corporation.

(3) RS-232C Cross-cable

The wiring connections of the RS-232C cross-cable which links the PC/AT-compatible personal computer and DN91 are shown below.

A(1S)D53DN15Dsub

female connector

(9 pin)

Signal

Name

 1 1 DCD RD 2 2 RxD SD 3 3 TxD

DTR 4 4 DTR

SG 5 5 GND

 6 6 DSR RS 7 7 RTS CS 8 8 CTS

 9 9 RI

Number

not connected

PC/AT-compatible

PC Dsub female

connectors

(9 pin)

Number

Signal

Name

• Shielded cable is recommended.

• Connection of is recommended to eliminate directionality.

2 − 5

Page 22

2. SYSTEM CONFIGURATION

REMARK

Configurator suppliers are listed below.

• USA Synergetic Micro Systems, Inc. 2506 Wisconsin Ave. Downers Grove, IL USA 60515

TEL: +1-630-434-1770 FAX: +1-630-434-1987

• Germany Hilscher Gesellschaft füE Systemautomation GmbH Rheinstrasse 78 D-65795 Hattersheim Germany

TEL: +49-6190-9907-0 FAX: +49-6190-9907-50

• Japanese Agent NPS Ltd. 4F Shinjuku No. 7 Hayama Building 1-36-2 Shinjuku Shinjuku-ku Tokyo

TEL: 03-3226-8110 FAX: 03-3226-8113

MELSEC-A

2.3 Products Connectable to a Slave Station

While it is considered connectable with most commercially available DeviceNet products, we cannot guarantee the connectivity with products of other manufa-cturers.

2 − 6

Page 23

3. SPECIFICATIONS

3.1 General Specifications

Table 3.1 shows the general specifications of the DN91.

Operating ambient temperature

Operating ambient humidity

Storage ambient temperature

Storage ambient humidity

Vibration resistance

Shock resistance Conforming to JIS B 3501, IEC 1131-2 (147 m/s2 {15G}, 3 times in 3 directions) Operating

environment Operating altitude 2000 m max. Installation

position Over-voltage

category Degree of

contamination

Table 3.1 General Specifications

Item Specification

0 to 55 °C

10 to 90 %RH, no condensation

- 20 to 75 °C

10 to 90 %RH, no condensation

Frequency Acceleration Amplitude

Intermittent

Conforming to JIS B3501, IEC1131-2

vibrations

Continuous vibrations

10 to 57 Hz  0.075 mm

57 to 150 Hz

Frequency Acceleration Amplitude

10 to 57 Hz  0.035 mm

57 to 150 Hz

No corrosive gas

In control box

9.8 m/s {1G}

4.9 m/s

{0.5G}

II max.

2 max.

MELSEC-A

Number of

Sweeps



10 in X, Y, and Z directions (80 minutes)

*1: Indicates the position of the distribution board to which the device is assumed to be connected

between the public power network and the position of the machine in the factory. Category II is applicable to devices supplied by power from fixed plant. For devices rated up to 300 V, surge-voltage resistance is 2500 V.

*2: Indicator showing the degree of generation of conducting material in the device operating

environment. A degree of contamination of 2 indicates that only non-conducting contamination occurs. However, temporary conductivity may arise in this environment due to accidental condensation.

*3: JIS (Japanese Industrial Standard)

3 − 1

Page 24

3. SPECIFICATIONS

3.2 Performance Specifications

Table 3.2 shows the general specifications of the DN91.

By node type Group 2 dedicated client Settable station numbers 0 to 63 Maximum number of

slave stations to communicate with

Communication speed Select 125 kbaud, 250 kbaud, or 500 kbaud

Communication specification

Max. cable length *

Amperage consumption (mA) required on the

network Number of occupied I/Os Special 32 points Internal current consumption

at 5 VDC (A) Product weight (kg) A1SJ71DN91: 0.23, AJ71DN91: 0.43

Table 3.2 Performance Specifications

Item Specification

I/O communication

volume

Message communication

Communication data

Send 2048 points (256 bytes) Re-

ceive Send 240 bytes Re-

ceive

Communi-

cation Speed

125 kbaud 500 m 156 m 250 kbaud 250 m 78 m 500 kbaud 100 m

Trunk Line Max. Transfer Distance Drop Line

Thick

Cable

2048 points (256 bytes)

Thin

Cable

100 m See 3.2.1 6 m

240 bytes

Thick Cable/Thin

Cable Combination

26.5

0.24

MELSEC-A

Max. Total

39 m

*: See the DeviceNet Specifications (Release 2.0) Volume 1 and Volume 2 for details about the

maximum cable lengths.

3.2.1 Maximum transfer distance of a trunk line that contains both thick and thin cables

This section shows the maximum transfer distances for thick cable/thin cable com-binations.

Communication

Speed

125 kbaud (Thick cable length + 5) x thin cable length ≤ 500 m 250 kbaud (Thick cable length + 2.5) x thin cable length ≤ 250 m 500 kbaud Thick cable length x thin cable length ≤ 100 m

Trunk Line Max. Transfer Distance with a Thick Cable/Thin Cable

Combination

3 − 2

Page 25

3. SPECIFICATIONS

3.3 PLC CPU I/O Signals

This section describes the I/O signals for the DN91 PLC CPU.

3.3.1 Table of I/O signals

Table 3.3 shows the table of DN91 I/O signals. The letter "n" in the table represents the leading I/O number of DN91. It is determin-ed by the position installed and the unit installed before DN91. <Example> If the DN91 head I/O number is "X/Y30"

Input Number Signal Name Output Number Signal Name

MELSEC-A

Xn0 to X(n+1)F → X30 to X4F Yn0 to Y(n+1)F → Y30 to Y4F

Table 3.3 Table of I/O Signals

DN91 →→ PLC CPU PLC CPU →→ DN91

Xn0 Watchdog timer error Yn0 Xn1 Refreshing Yn1

Xn2 Xn3 Error set signal Yn3

Xn4 Slave down signal Yn4 Xn5

Xn6 Parameter being set Yn6 Xn7 Parameter setting complete Yn7

Xn8 Yn8

Xn9 Yn9 XnA YnA XnB YnB XnC YnC XnD YnD XnE

XnF Unit ready YnF X(n+1)0 Y(n+1)0 Unusable X(n+1)1 Y(n+1)1 Refresh request

X(n+1)2 Y(n+1)2 X(n+1)3 Y(n+1)3 Error reset request

X(n+1)4 Y(n+1)4 X(n+1)5 Y(n+1)5 X(n+1)6 Y(n+1)6 X(n+1)7 Y(n+1)7 Parameter set request X(n+1)8 Y(n+1)8 X(n+1)9 Y(n+1)9

X(n+1)A Y(n+1)A X(n+1)B Y(n+1)B X(n+1)C Y(n+1)C X(n+1)D Y(n+1)D X(n+1)E Y(n+1)E X(n+1)F

Message communication complete

Message communication error signal

Unusable

Yn2

Yn5

Unusable

YnE

Message communication request

Unusable

Y(n+1)F

3 − 3

Page 26

3. SPECIFICATIONS

Important

MELSEC-A

The output signals designated as "unusable" in Table 3.3 are reserved for system use and are not available to the user. Normal operation cannot be guaranteed if the user operates one of these output signals (that is, turns the signal ON or OFF).

3 − 4

Page 27

3. SPECIFICATIONS

3.3.2 I/O signal details

This section explains the I/O signal ON/OFF timing and conditions.

(1) Watchdog timer error: Xn0

(2) Refreshing: Xn1, Refresh request: Y(n+1)1

MELSEC-A

Turns ON if an error occurs in DN91. OFF: Unit normal ON: Unit abnormal

Watchdog timer error (Xn0)

Unit ready (XnF)

These signals determine whether the data in the input data area and output data area of the buffer memory is used to refresh the network. Refresh is conducted if the status of the master communication status area in buffer memory is "operation in progress." (a) To start the data refresh, turn ON refresh request (Y(n+1)1) with a sequen-ce

program.

(b) When refresh request (Y(n+1)1) is turned ON, the refresh operation starts and

refreshing (Xn1) turns ON automatically.

program.

(d) The data refreshing is interrupted with "Refreshing" signal (Xn1) turned OFF

automatically and "OFF" or 0 data transmitted to all slave stations. Refreshing the input data area still continues.

Refresh request (Y(n+1)1)

Refreshing (Xn1)

3 − 5

Page 28

3. SPECIFICATIONS

(3) Message communication complete : Xn2

MELSEC-A

Message communication error signal : Xn5 Message communication request : Y(n+1)2 These signals are used for message communication. Message communication is conducted if the status of the master communication status area in buffer memory is "operation in progress." (a) Follow the procedure below to conduct message communication.

1) Write the message communication data to the message communication command area in buffer memory.

2) Turn ON message communication request (Y(n+1)2) with a sequence program. (Set the interval of turning ON the message communication request at 100 ms

or over.)

(b) The message communication completes with the results written onto the "Message

communication results" area, and the message communication complete (Xn2) turns ON.

communication error signal (Xn5).

Message communication request (Y(n+1)2)

Message communication complete (Xn2)

Message communication error signal (Xn5)

FROM/TO

(d) After reading the communication data with FROM command, the sequence program

is used to turn OFF the message communication request (Y(n+1)2). The message communication complete (Xn2) and message communication error signal (Xn5) automatically turns OFF.

Write message

communication

command (TO

instruction)

Error involved

Write message

communication

data (TO

instruction)

(For data send only) (For data receive only)

Read message communication results (FROM

instruction)

No error

Read message communication

data (FROM

instruction)

(4) Error set signal: Xn3, Error reset request: Y(n+1)3

These signals are used to notify an error and reset error codes. (a) If an error occurs, error information is stored in the error information area in buffer

memory and the error set signal (Xn3) turns ON. The error set signal automatically turns OFF when the cause of the error is removed.

(b) Once the cause of error is removed, turning ON the error-resetting request

(Y(n+1)3) with the sequence program clears the error code set on the "error information" area.

Error reset request (Y(n+1)3)

Error set signal (Xn3)

FROM/TO

3 − 6

Read error

information (FROM

instruction)

Page 29

3. SPECIFICATIONS

(5) Slave down signal: Xn4

(6) Parameter-being-set : Xn6

MELSEC-A

This signal indicates whether any slave station has stopped communication. (a) This signal turns ON if any slave station for which parameters are set stops

communication. OFF : All stations communicating normally ON : Abnormal communication at a station Which station has stopped communication can be confirmed from the station communication status area at addresses 01BCH to 01BFH of the buffer memory.

(b) This signal automatically turns OFF when the slave station communication restarts.

Parameter set complete : Xn7 Parameter set request : Y(n+1)7 These signals are used to set parameters with a sequence program. Set the parameters when the refreshing (Xn1) signal is OFF. (a) Follow the procedure below to write parameters.

1) Write the parameters to the parameter set area in buffer memory.

2) Turn on parameter set request (Y(n+1)7) with a sequence program.

(b) Once the write request is received and the parameter analysis completes normally,

parameter-writing action gets executed with the parameter-being-set (Xn6) turned ON.

operation is complete. Communication with other slave stations is disabled while parameters are being set. Parameter set complete (Xn7) automatically turns OFF when parameter set request (Y(n+1)7) turns OFF.

Refresh request (Y(n+1)1)

Refreshing (Xn1)

Parameter set request (Y(n+1)7)

Parameter being set (Xn6)

Parameter set complete (Xn7)

TO instruction

POINTS

(1) If refreshing (Xn1) is ON when parameter set request (Y(n+1)7) turns ON,

parameter set complete (Xn7) does not turn ON. First, turn OFF refresh request (Y(n+1)1) and confirm that refreshing (Xn1) is OFF before turning parameter set request (Y(n+1)7) OFF and back ON.

(2) If parameter set request (Y(n+1)7) is ON when refresh request (Y(n+1)1) turns ON,

refreshing (Xn1) does not turn ON. First, turn OFF parameter set request (Y(n+1)7), then reset refresh request (Y(n+1)1) and turn it back ON.

Write parameter

data

3 − 7

Page 30

3. SPECIFICATIONS MELSEC-A

(7) Unit ready: XnF

This signal indicates whether the unit is able to operate. It turns ON automatically when unit operation is enabled.

3.4 Buffer Memory

Buffer data is used for data communication between DN91 and the PLC CPU. It is used for reading and writing of DN91 buffer memory data and for the PLC CPU FROM/TO instructions. The buffer memory returns to zero (0) when powered OFF or when the PLC CPU reset. If the parameters are set by the sequence program, however, the "Parameter" area is initialized with the parameters that are already set.

3.4.1 Buffer memory table

The buffer memory table is shown in Table 3.4.

Table 3.4 Buffer Memory Table

Address

Hexadecimal Decimal

0000H to 007FH 0 to 127 Input data Stores input data from each slave station. Disabled 3.4.2 (1) 0080H to 00FFH 128 to 255 Output data Stores output data for each slave station. Enabled 3.4.2 (2) 0100H to 010FH 256 to 271 Not used   

0110H to 011FH 272 to 287

0120H to 012FH 288 to 303

0130H to 01A7H 304 to 423

01A8H to 01A9H 424 to 425 Model display Setting is "DN91" in ASCII code Disabled

01AAH to 01AFH 426 to 431 Not used  

01B0H 432

01B1H 433 Error information

01B2H 434 Bus error counter 01B3H 435 Bus-off counter Stores the number of communication errors. Disabled 3.4.2 (9)

01B4H to 01B7H 436 to 439 01B8H to 01BBH 440 to 443 Not used    01BCH to 01BFH 444 to 447 01C0H to 01C3H 448 to 451 Not used    01C4H to 01C7H 452 to 455 01C8H to 01CBH 456 to 459 Not used   

01CCH to 01CFH 460 to 463

01D0H to 01D3H 464 to 467 Not used    01D4H to 03CFH 468 to 975 Parameter

Message communication command

Message communication result

Message communication data

Master communication status

Configuration status of each station

Communication status of each station

Error status of each station

Down-station detection disabled setting

Item Contents

Stores request data for message communication.

Stores result data from message communication.

Stores communication data for message communication.

Stores the DN91 status Disabled 3.4.2 (6) Upper byte: Error code

Lower byte: Stores station number where the

error occurred.

Stores the number of error detections for communication data.

Indicates whether parameters are set for each slave station.

Indicates whether each station is conducting I/O communication

Indicates whether an error has occurred for each station.

Sets whether a down slave station is reflected in the slave down signal (Xn4).

Area to set parameters with a sequence program.

Write Enabled/

Disabled by CPU

Enabled 3.4.2 (3)

Disabled 3.4.2 (4)

Enabled 3.4.2 (5)

Disabled 3.4.2 (7)

Disabled 3.4.2 (8)

Disabled 3.4.2 (10)

Disabled 3.4.2 (11)

Disabled 3.4.2 (12)

Disabled 3.4.2 (13)

Enabled 3.4.2 (14)

See

Page



3 − 8

Page 31

3. SPECIFICATIONS

3.4.2 Details of the buffer memory

This section describes details about the items listed in Table 3.4.

(1) Input Data

(Addresses : 0000H to 007FH/0 to 127) Data received from each slave station is saved. The order of the data differs according to whether the parameters were set by a sequence program or by the configuration software.

(a) Parameters set by a sequence program

If the parameters were set by a sequence program, the data is saved as a series of words of a slave station. In the case of double-word data, the data is saved as the lower word followed by the upper word. If an odd number of byte input modules is available, one byte of free area must be inserted in order to arrange the data as a series of words. A bit input module and a byte input module are handled equally. See the example below. <Example> Station 1 - Byte input modules = 3

Station 2 - Byte input modules = 1 Station 3 - Byte input modules = 1

MELSEC-A

Word input modules = 2 Double-word input modules = 2

Buffer memory

address

0000H

0001H Free

0002H Word module No. 1

0003H Word module No. 2

0004H

0005H

0006H

0007H

0008H

0009H

Byte module

No. 2

Double-word module No. 1,

Double-word module No. 2,

Byte module

No. 1

Byte module

No. 3

lower word

upper word

lower word

upper word

Byte module

No. 1

Byte module

No. 1

With an odd number of byte input modules, insert one byte of free area.

Station 1 input data

Station 2 input data

Station 3 input data

Word input module : numeric data represented by bits 9 to 16 Double-word input module : numeric data represented by bits 17 to- 32 Byte input module : numeric data represented by ON/OFF data or

bits 1 to 8

3 − 9

Page 32

3. SPECIFICATIONS MELSEC-A

(b) Parameters set by configuration software

The buffer memory address at which the input data for each station is stored is shown in the diagram below. The address is displayed for the Customized I/O data, I. Addr item on the screen.

The memory address is determined by the value of the Customized I/O data, I. Addr item in the diagram above and the addressing mode set from the configuration software Master Setting screen. See the example below. <Example> Consider the case where the Customized I/O data, I. Addr item is set as follows:

Data Type I. Addr

BYTE 0 …1)

BYTE 2 …2) WORD 3 …3) WORD 5 …4)

1) If the addressing mode is byte addressing The setting screen appears as:

and the relationship between the buffer memory address and I. Addr is shown in the diagram below.

0000H 1) 0001H 2) 0002H 3) 0003H 4)

3 5

0 2 4 6

3 − 10

Page 33

3. SPECIFICATIONS

(2) Output Data

MELSEC-A

2) If the addressing mode is word addressing The setting screen appears as:

and the relationship between the buffer memory address and I. Addr is a 1:1 correspondence, as shown in the diagram below.

0000H 1) 0001H 0002H 2) 0003H 3) 0004H 0005H 4)

See the Configuration Software Manual for details about the configura-tion software.

(Addresses : 0080H to 00FFH/128 to 255) Data sent to each slave station is written with the TO instruction. As in the case of the input data, the data order differs according to whether the parameters were set by a sequence program or by the configura-tion software. (a) Parameters set by a sequence program

If the parameters were set by a sequence program, the data is saved as a series of words of a slave station. In the case of double-word data, the data is saved as the lower word followed by the upper word. If an odd number of byte input modules is available, one byte of free area must be inserted in order to arrange the data as a series of words. See the example below. <Example> Station 1 - Byte output modules = 3

Word output modules = 2

Double-word output modules = 2 Station 2 - Byte output modules = 1 Station 3 - Byte output modules = 1

Buffer memory

address

0080H

0081H Free

0082H Word module No. 1

2 3

Byte module

No. 2

Byte module

No. 1

Byte module

No. 3

With an odd number of byte input modules, insert one byte of free area.

0083H Word module No. 2

0084H

0085H

0086H

0087H

0088H

0089H

Double-word module No. 1,

lower word

Double-word module No. 1,

upper word

Double-word module No. 2,

lower word

Double-word module No. 2,

upper word

Byte module

3 − 11

No. 1

Station 1 output data

Station 2 output data

Station 3 output data

Page 34

3. SPECIFICATIONS MELSEC-A

(b) Parameters set by configuration software

The buffer memory address at which the input data for each station is stored is displayed for the Customized I/O data, O. Addr item on the configuration software screen. The memory address is determined by the value of the Customized I/O data, O. Addr item on the configuration software screen and the addressing mode set from the configuration software Master Setting screen. See the example below. <Example> Consider the case where the Customized I/O data, O. Addr item is set as follows:

Data Type O. Addr

BYTE 0 …1)

BYTE 2 …2) WORD 3 …3) WORD 5 …4)

1) If the addressing mode is byte addressing The setting screen appears as:

and the relationship between the buffer memory address and O. Addr is shown in the diagram below.

0080H 1) 0081H 2) 0082H 3) 0083H 4)

3 5

0 2 4 6

2) If the addressing mode is word addressing The setting screen appears as:

and the relationship between the buffer memory address and O. Addr is a 1:1 correspondence, as shown in the diagram below.

0080H 1) 0081H 0082H 2) 0083H 3) 0084H 0085H 4)

2 3

3 − 12

Page 35

3. SPECIFICATIONS

(3) Message Communication Commands (Addresses - 0110H to 011FH/272 to 287)

MELSEC-A

TO command is used to write the message communication command. (a) Reading Attribute Data from a Slave Station

1) Set the command data in the message communication command area using the TO instruction.

2) Turn ON message communication request (Y(n+1)2) with a sequence program.

3) Message communication complete (Xn2) automatically turns ON when the message communication completes.

4) Check the message communication error signal (Xn5) to see if the message communication has been normally completed.

5) The read attribute data is saved in the message communication data area.

Table 3.5 shows the data that should be set by a sequence program.

Table 3.5 Set Data for Get Attribute

Buffer Memory

Address

(Hexadecimal)

0110H Command number 0101H = Get Attribute

0111H

0112H Instance ID Object instance ID to read attribute data

0113H Attribute ID

Item Contents

Slave station number (slave MAC ID), class ID

Lower byte: Slave station number to read

Upper byte: Object class ID to read attribute data

Lower byte: Object attribute ID to read attribute

Upper byte: Always set to 0

attribute data (MAC ID)

data

(b) Writing Attribute Data to a Slave Station

1) Set the command data in the message communication command area using the TO instruction.

2) Set the attribute data to be written in the message communication data area using the TO instruction.

3) Turn ON message communication request (Y(n+1)2) with a sequence program.

4) Message communication complete (Xn2) automatically turns ON when the message communication completes.

5) Check the message communication error signal (Xn5) to see if the message communication has been normally completed.

Table 3.6 shows the data that should be set by a sequence program.

Table 3.6 Set Data for Set Attribute

Buffer Memory

Address

(Hexadecimal)

0110H Command number 0102H = Set Attribute

0111H

0112H Instance ID Object instance ID

0113H

Item Contents

Slave station number (slave MAC ID), class ID

Attribute ID, data length

Lower byte: Slave station number (MAC ID) Upper byte: Object class ID

Lower byte: Object attribute ID Upper byte: Byte length of attribute data to be

written 1 to 240 (1H to F0H)

3 − 13

Page 36

3. SPECIFICATIONS MELSEC-A

1) Set the command data in the message communication command area using the TO instruction.

2) Turn ON message communication request (Y(n+1)2) with a sequence program.

3) Once reading action completes, the message communication complete (Xn2) automatically turns ON.

4) The read attribute data is saved in the message communication data area.

Table 3.7 shows the set data to read communication error information

Table 3.7 Set Data To Read Communication Error Information

Buffer Memory

Address

(Hexadecimal)

0110H Command number 0001H = Read Communication Error Information

0111H

(d) When resetting:

Buffer Memory

Address

(Hexadecimal)

0110H Command number 0120H = Reset

0111H

0112H Instance ID Object instance ID

Item Contents

Slave station number (slave MAC ID)

Lower byte: Slave station number to read error

Upper byte: Always set to 0

Table 3.8 Reset Setting Data

Item Contents

Slave station number (slave MAC ID), class ID

Lower byte: slave station number (MAC ID) Upper byte: object class ID

information (MAC ID)

(4) Message Communication Results (Addresses - 0120H to 012FH/288 to 303)

When the message communication commands are used, the process result is set in the DN91 message communication result area and message communica-tion complete (Xn2) turns ON. The process results can be read with a FROM instruction in a sequence prog-ram. The process results are stored as shown in the table below. See 8.3.2 Message Communication Execution Error Codes for details about the buffer memory address 00A1H execution error code.

Table 3.9 Get Attribute Result Data

Buffer Memory

Address

(Hexadecimal)

0120H Command number 0101H = Get Attribute 0121H Execution error code

0122H

0123H Instance ID Object instance ID

0124H

Item Contents

Slave station number (slave MAC ID), class ID

Attribute ID, data length

Normal completion: 0000H Error : Execution error code

Lower byte: Slave station number (MAC ID) Upper byte: Object class ID

Lower byte: Object attribute ID Upper byte: Number of bytes 1 to 240 (1H to F0H) of

read attribute data

Table 3.10 Set Attribute Result Data

3 − 14

Page 37

3. SPECIFICATIONS

Buffer Memory

Address

(Hexadecimal)

0120H Command number 0102H = Set Attribute

0121H Execution error code

0112H

0123H Instance ID Instance ID

0124H Attribute ID

Item Contents

Slave station number (slave MAC ID), class ID

Normal completion: 0000H Error : Execution error code

Lower byte: Slave station number (MAC ID) Upper byte: Object class ID

Lower byte: Object attribute ID to write attribute data Upper byte: Number of bytes of attribute data

(1 to 240)

Table 3.11 Result Data for Reading Communication Error Information

Buffer Memory

Address

(Hexadecimal)

0120H Command number 0001H = Read Communication Error Information 0121H Execution error code

Item Contents

Normal completion: 0000H Error : Execution error code

MELSEC-A

Table 3.12 Reset Setting Data

Buffer Memory

Address

(Hexadecimal)

0120H Command number 0120H = Reset 0121H Execution error code

0122H

0123H Instance ID Object instance ID

Item Contents

Normal completion: 0000H Error : Execution error code

Slave station number (slave MAC ID), class ID

Lower byte: slave station number (MAC ID) Upper byte: object class ID

(5) Message Communication Data (Addresses - 0130H to 01A7H/304 to 423)

The message communication data area is used for the following applications. (a) Get Attribute Data

The attribute data read through the message communication is stored as a byte string.

0130H Second byte First byte

Fourth byte Third byte

Sixth byte Fifth byte

Read attribute data

…………………..

01A7H

…

3 − 15

Page 38

3. SPECIFICATIONS MELSEC-A

(b) Set Attribute Data

Attribute data to be written via message communication is written as a byte string .

0130H Second byte First byte

Fourth byte Third byte

Sixth byte Fifth byte

Write attribute data

…………………..

01A7H

…

Stores read communication error information. The data set at each address is shown in Table 3.13.

Table 3.13 Set Data for Read Communication Error Information

Buffer Memory

Address

(Hexadecimal)

0130H Slave status 0131H Unusable 

0132H

0133H General error codes

0134H

0135H

Item Contents

Indicates whether the slave station has parameters set and whether it responded. (See 1).)

Communication error codes

Additional error codes

Number of heartbeat timeouts

Stores the same error code as the upper byte of buffer memory address 01B1H. See 8.3.1 Communication Error Codes for details about the error codes.

Stores the DeviceNet general error code that has been sent from a slave station. Valid only when the communication error code is 35 (0023H). (Refer to 2).)

Stores the additional error codes sent by the slave stations.

Stores the number of times the DN91 detected a slave station down.

*1: See the slave station manual for details about the actual problems and remedies. *2: See the slave station manual for a description of each error code.

3 − 16

Page 39

3. SPECIFICATIONS

the response bit is ON.

MELSEC-A

1) Slave status The problem at a slave station is notified by turning bits ON and OFF, as shown in the diagram below.

0130H

Bit 15 to bit 8 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

Used by the system

These problems have occurred if

No response from slave station

Slave station refused written attribute data

I/O data size set in parameters differs from the actual size.

Set as reserved station in the parameters

3 − 17

Page 40

3. SPECIFICATIONS MELSEC-A

2) Table 3.14 shows the DeviceNet general error codes

Table 3.14 Table of DeviceNet General Error Codes

Error Code

Hexadecimal Decimal

0000H to 0001H 0 to 1 Reserved Reserved by DeviceNet.

0002H 2 Resource unavailable

0003H to 0007H 3 to 7 Reserved Reserved by DeviceNet.

0008H 8 Service not supported 0009H 9 Invalid attribute value Abnormal attribute data in the requested service.

000AH 10 Reserved Reserved by DeviceNet. 000BH 11 Already in requested mode/state

000CH 12 Object state conflict 000DH 13 Reserved Reserved by DeviceNet.

000EH 14 Attribute not settable 000FH 15 Privilege violation The service request destination has no access rights. 0010H 16 Device state conflict

0011H 17 Reply data too large The response data length exceeded the processable data length. 0012H 18 Reserved Reserved by DeviceNet. 0013H 19 Not enough data The requested service did not supply sufficient data for processing. 0014H 20 Attribute not supported The requested service designated an undefined attribute. 0015H 21 Too much data The requested service included invalid data. 0016H 22 Object does not exist The requested service designated an unmounted object. 0017H 23 Reserved Reserved by DeviceNet.

0018H 24 No stored attribute data

0019H 25 Store operation failure

001AH to 001EH 26 to 30 Reserved Reserved by DeviceNet.

001FH 31 Vendor specific error

0020H 32 Invalid parameter

0021H to 0027H 33 to 39 Future extensions Reserved by DeviceNet.

0028H 40 Invalid Member ID

0029H 41 Member not settable

002AH to 00CFH 42 to 207 Reserved Reserved by DeviceNet.

00D0H to 00FFH 208 to 255

Reserved for Object Class and service errors

Error Name Description

The requested service could not be run as the required resource was not free.

The requested service is not supported. Or, the requested service is undefined in the designated object class or instance.

The designated object is already transferred to the requested mode or status.

The designated object was not in a status to execute the requested service.

An unchangeable attribute was designated for the requested setting service.

The designated device was not in a status to execute the requested service.

The object attribute data was not saved before the service was requested.

The object attribute data was not saved due a problem during the save processing.

An error specific to a vendor occurred. The "Additional error code" area (0134H) of the error response shows the specific error. The error code is used only when any of the error codes shown in this table or within the object class definition does not correspond to the relevant error.

A parameter problem occurred with the requested service. This code is used if the parameter does not meet the requirements in this specification of DeviceNet or the important conditions defined in the application object specifications.

The member ID of the requested service designated an unmounted class, instance, or attribute.

An unchangeable member was designated for the requested setting service.

Error codes in this range are used to represent errors unique to object classes. The codes of the range are used only when any of the error codes shown in this table do not correctly explain the error that has occurred. "DeviceNet general error code" area (0133H) may be explained in further detail using the "Additional error code" area (0134H).

3 − 18

Page 41

3. SPECIFICATIONS

continue.

been turned OFF.

(6) Master Communication Status (Address 01B0H/432)

MELSEC-A

The master communication status is shown by the upper and lower bytes, as shown below. (a) Upper Byte

This byte shows the DN91 I/O communication status. It contains a value indicating the communication status, as shown in Table 3.15.

Table 3.15 I/O Communication Statuses

Value Name Operation

0000H OFFLINE Initializing 0040H STOP I/O communication stopped

0080H CLEAR 00C0H OPERATE Conducting I/O communication

When powering ON, after normal completion of self-diagnosis and parameter check, the state automatically advances from "OFFLINE" to "OPERATE". When Refreshing (Xn1) is ON, "0" data is sent to reset the output data of slave stations. While setting parameters, the state advances from "OPERATE", "CLEAR", "STOP", and to "OFFLINE".

Resetting output data for all slave stations after 0 data was sent.

OFFLINE

STOP

CLEAR

OPERATE

(b) Lower Byte

This byte shows the device network communication status. The bits turn ON/OFF according to the communication status, as shown in the diagram below.

Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

Abnormal communication with a station

Since communication with a slave station failed, output to all slave stations has

Always OFF

The bit turns ON when the corresponding problem occurs.

3 − 19

Parameter error

Severe network problems. Communication cannot

Page 42

3. SPECIFICATIONS

(7) Error Information (Address 01B1H/433)

MELSEC-A

Stores the detected communication error code. (a) The error information is stored in the error information area when an error occurs.

The error set signal (Xn3) turns ON.

(b) The data in the "Error information" area is cleared by turning ON the error reset

request (Y(n+1)3) through the sequence program.

number in the lower byte, as described below.

1) Upper Byte This byte stores the error codes. See 8.3.1 Communication Error Codes for details.

2) Lower Byte This byte stores the station number (MAC ID) of the station where the error occurred. FEH, FFH (254, 255) : Host station (DN91) 0H to 3FH (0 to 63) :Station number (MAC ID) of the slave station

where the error occurred

REMARK

If an error occurs in multiple stations, the error for the station with the lowest station number (MAC ID) is stored.

(8) Bus Error Counter (Address 01B2H/434)

Stores the number of times the invalid frame count of CAN chip (DeviceNet communication chip) exceeded 96. Any increase in the value indicates the instability of communication.

(9) Bus-off Counter (Address 01B3H/435)

Stores the number of times DN91moved into the state of Bus-off. Any increase in the value indicates the instability of communication.

(10) Station Configuration Status (Address 01B4H to 01B7H/436 to 439)

Stores the parameter setting status for each slave station.

• If a bit is ON, the parameters are set.

• If a bit is OFF, the parameters are not set.

The buffer memory addresses and the station number corresponding to each bit are shown in Table 3.16.

Table 3.16 Station Number Corresponding to Each Bit in the Station

Configuration Status

Buffer Memory Address Station Number Corresponding to Each Bit

(Hexadecimal) Bit 15 Bit 14 … Bit 1 Bit 0

01B4H Station 15 Station 14 … Station 1 Station 0 01B5H Station 31 Station 30 … Station 17 Station 16 01B6H Station 47 Station 46 … Station 33 Station 32 01B7H Station 63 Station 62 … Station 49 Station 48

3 − 20

Page 43

3. SPECIFICATIONS

(11) Station Communication Status (Address 01BCH to 01BFH/444 to 447)

(12) Station Problem Status (Address 01C4H to 01C7H/452 to 455)

MELSEC-A

Stores whether or not I/O communication is normal for each slave station.

• If a bit is ON, I/O communication

• If a bit is OFF, I/O communication interrupted

The buffer memory addresses and the station number corresponding to each bit are shown in Table 3.17.

Table 3.17 Station Number Corresponding to Each Bit in the Station

Communication Status

Buffer Memory Address Station Number Corresponding to Each Bit

(Hexadecimal) Bit 15 Bit 14 … Bit 1 Bit 0

01BCH Station 15 Station 14 … Station 1 Station 0 01BDH Station 31 Station 30 … Station 17 Station 16 01BEH Station 47 Station 46 … Station 33 Station 32

01BFH Station 63 Station 62 … Station 49 Station 48

Stores whether or not a communication error has occurred for each slave station.

• If a bit is ON, problem information exists

• If a bit is OFF, no problem information exists

Follow the procedure below to turn OFF a bit. (a) Read the communication error information for the station, using the buffer memory

message communication area. (For information on reading com-munication error information, see 3.4.2 (3) Message Communication Com-mands, (4) Message Communication Results, and (5) Message Communi-cation Data.)

(b) When Read Communication Error Information is executed, the correspond-ing bit

automatically turns OFF. The buffer memory addresses and the station number corresponding to each bit are shown in Table 3.18.

Table 3.18 Station Number Corresponding to Each Bit in the Station

Problem Status

Buffer Memory Address Station Number Corresponding to Each Bit

(Hexadecimal) Bit 15 Bit 14 … Bit 1 Bit 0

01C4H Station 15 Station 14 … Station 1 Station 0 01C5H Station 31 Station 30 … Station 17 Station 16 01C6H Station 47 Station 46 … Station 33 Station 32 01C7H Station 63 Station 62 … Station 49 Station 48

3 − 21

Page 44

3. SPECIFICATIONS

(13) Down-station Detection Disabled Setting (Address 01CCH to 01CFH/460 to 463)

MELSEC-A

This setting determines whether the down status of a slave station shown in the Station Communication Status (Address 01BCH to 01BFH/444 to 447) is reflect-ed in the slave down signals (Xn4).

• If a bit is ON, the corresponding slave down signal (Xn4) does not turn ON

when a slave station is down.

• If a bit is OFF, the corresponding slave down signal (Xn4) does turn ON when a

slave station is down. The buffer memory addresses and the station number corresponding to each bit are shown in Table 3.19.

Table 3.19 Station Number Corresponding to Each Bit for the

Down-station Detection Disabled Settings

Buffer Memory Address Station Number Corresponding to Each Bit

(Hexadecimal) Bit 15 Bit 14 … Bit 1 Bit 0

01CCH Station 15 Station 14 … Station 1 Station 0 01CDH Station 31 Station 30 … Station 17 Station 16 01CEH Station 47 Station 46 … Station 33 Station 32 01CFH Station 63 Station 62 … Station 49 Station 48

POINT

Turn ON the relevant bit for prohibition of faulty station detection with stations designated as reserved in parameter settings. If the bit is left OFF, any reserved station will be recognized faulty.

3 − 22

Page 45

3. SPECIFICATIONS

(14) Parameters (Address 0154H to 034FH/340 to 847)

Used to set parameters via the sequence program. The parameters set by a sequence program are written to E2PROM. Once parameters have been set, they do not require setting again until changes are made to the parameters. After DN91 is turned ON, if the E2PROM contains valid parameters, the parameters from E2PROM are stored in the parameter area Follow the procedure below to write new parameters. (a) Set parameters in the parameter area, as shown in Table 3.20.

(b) Turn ON the parameter set request (Y(n+1)7) with a sequence program.

Table 3.20 Parameter Set Data

Buffer Memory

Address (16 hex)

01D4H Host station (MAC ID)

01D5H Baud rate

01D6H, 01D7H Not used 

01D8H

01D9H

01DAH

01DBH

01DCH

01DDH

Station number for the first slave station

Connection type for the first slave station

Number of byte modules for the first slave station

Number of word modules for the first slave station

Number of double-word modules for the first slave station

Expected packet rate for the first slave station (EXPECTED PACKET RATE)

Item Contents

MELSEC-A

Stores the station number (MAC ID) of DN91 in a range from 0000H to 0003H. Setting parameters with this value set at FFFFH invalidates the parameters that have been set by the sequence program.

Select the baud rate: 1 = 500 Kbps, 2 = 250 Kbps, 3 = 125 Kbps

Lower byte: Station number (MAC ID) of first slave station

0 to 63

Upper byte: 01H → Station that supports UCMM and uses the message group 3.

02H → Station that supports UCMM and uses the message group 2. 03H → Station that supports UCMM and uses the message group 1. 04H → Station that does not support UCMM. (Dedicated server of

group 2)

80H → Reserved station

Select the connection type for I/O communication: 0001H = polling, 0002H = bit strobe, 0004H = change of state, 0008H = cyclic

Lower byte: Number of input byte modules Upper byte: Number of output byte modules (8 points of bit modules are calculated as one byte module.)

Lower byte: Number of input word modules Upper byte: Number of output word modules

Lower byte: Number of input double-word modules Upper byte: Number of output double-word modules

Sets the expected packet rate at the slave station. Setting = 0000H (default) → 200 ms Setting ≠ 0000H → The value (setting - 1) is the communication watchdog timer

setting (ms). The setting will vary depending on the connection type. Refer to Table 3.21 for further details of the setting.

3 − 23

Page 46

3. SPECIFICATIONS MELSEC-A

Buffer Memory

Address (16 hex)

Watchdog timeout action for the

01DEH

01DFH

01E0H to 01E7H 01E8H to 01EFH Setting for the third slave station

01F0H to 01F7H Setting for the 4th slave station 01F8H to 01FFH Setting for the 5th slave station

0200H to 0207H Setting for the 6th slave station

0208H to 020FH Setting for the 7th slave station

0210H to 0217H Setting for the 8th slave station

0218H to 021FH Setting for the 9th slave station

0220H to 0227H Setting for the 10th slave station

0228H to 022FH Setting for the 11th slave station

0230H to 0237H Setting for the 12th slave station Same as with the first slave station

0238H to 023FH Setting for the 13th slave station

0240H to 0247H Setting for the 14th slave station

0248H to 024FH Setting for the 15th slave station

0250H to 0257H Setting for the 16th slave station

0258H to 025FH Setting for the 17th slave station

0260H to 0267H Setting for the 18th slave station

0268H to 026FH Setting for the 19th slave station

0270H to 0277H Setting for the 20th slave station

0278H to 027FH Setting for the 21st slave station

0280H to 0287H Setting for the 22nd slave station

0288H to 028FH Setting for the 23rd slave station

0290H to 0297H Setting for the 24th slave station

0298H to 029FH Setting for the 25th slave station 02A0H to 02A7H Setting for the 26th slave station 02A8H to 02AFH Setting for the 27th slave station 02B0H to 02B7H Setting for the 28th slave station 02B8H to 02BFH Setting for the 29th slave station 02C0H to 02C7H Setting for the 30th slave station 02C8H to 02CFH Setting for the 31st slave station 02D0H to 02D7H Setting for the 32nd slave station

first slave station (WATCHDOG TIMEOUT ACTION)

First Slave Station Production Inhibit Time

Setting for the second slave station

Item Contents

Slave station watchdog timeout action Set value = 0000H (default value)

Equal to TIMEOUT below.

Set value = 0001H: TIMEOUT

Connection enters timeout status. Can only be reset by the operator stopping and restarting communication.

Set value = 0002H: AUTO DELETE

Connection is automatically deleted. Communication stops and automatically restarts. Outputs are cleared to 0.

Set value = 0003H: AUTO RESET

Communication is continued with the connection maintained. Outputs are not cleared to 0.

Sets the production inhibit time. Setting = 0000H (default) → 20 ms Setting ≠ 0000H → The value (setting - 1) is the minimum transmission interval

(ms). The setting will vary depending on the connection type. Refer to Table 3.21 for further details of the setting.

Same as with the first slave station Same as with the first slave station

3 − 24

Page 47

3. SPECIFICATIONS MELSEC-A

Buffer Memory

Address (16 hex)

02D8H to 02DFH Setting for the 33rd slave station 02E0H to 02E7H Setting for the 34th slave station 02E8H to 02EFH Setting for the 35th slave station

02F0H to 02F7H Setting for the 36th slave station 02F8H to 02FFH Setting for the 37th slave station

0300H to 0307H Setting for the 38th slave station

0308H to 030FH Setting for the 39th slave station

0310H to 0317H Setting for the 40th slave station

0318H to 031FH Setting for the 41st slave station

0320H to 0327H Setting for the 42nd slave station

0328H to 032FH Setting for the 43rd slave station

0330H to 0337H Setting for the 44th slave station

0338H to 033FH Setting for the 45th slave station

0340H to 0347H Setting for the 46th slave station

0348H to 034FH Setting for the 47th slave station

0350H to 0357H Setting for the 48th slave station

0358H to 035FH Setting for the 49th slave station

0360H to 0367H Setting for the 50th slave station

0368H to 036FH Setting for the 51st slave station

0370H to 0377H Setting for the 52nd slave station

0378H to 037FH Setting for the 53rd slave station

0380H to 0387H Setting for the 54th slave station

0388H to 038FH Setting for the 55th slave station

0390H to 0397H Setting for the 56th slave station

0398H to 039FH Setting for the 57th slave station 03A0H to 03A7H Setting for the 58th slave station 03A8H to 03AFH Setting for the 59th slave station 03B0H to 03B7H Setting for the 60th slave station 03B8H to 03BFH Setting for the 61st slave station 03C0H to 03C7H Setting for the 62nd slave station 03C8H to 03CFH Setting for the 63rd slave station

Item Contents

Same as with the first slave station Same as with the first slave station Same as with the first slave station Same as with the first slave station Same as with the first slave station Same as with the first slave station Same as with the first slave station Same as with the first slave station Same as with the first slave station Same as with the first slave station Same as with the first slave station Same as with the first slave station Same as with the first slave station Same as with the first slave station Same as with the first slave station Same as with the first slave station Same as with the first slave station Same as with the first slave station Same as with the first slave station Same as with the first slave station Same as with the first slave station Same as with the first slave station Same as with the first slave station Same as with the first slave station Same as with the first slave station Same as with the first slave station Same as with the first slave station Same as with the first slave station Same as with the first slave station Same as with the first slave station Same as with the first slave station

3 − 25

Page 48

3. SPECIFICATIONS

Table 3.21 Details of Expected Packet Rate and Production Inhibit Time

(1) Set the communication watchdog timer value for a

slave station. Any interruption of communication between the master and slave stations for the time setting, the slave station executes the action designated by the Watchdog Timeout Action.

Polling

Bit strobe

Change of state

Cyclic

(2) When the expected packet rate setting ≠ 1,

or the expected packet rate ≠ 0 ms,

(3) When the setting value = 1, or when the Expected

packet rate = 0 ms, the Watchdog timer monitoring is disabled.

(1) Set the communication watchdog timer value for a

slave station. Any interruption of communication between the master and slave stations for the time setting, the slave station executes the action designated by the Watchdog Timeout Action.

(2) When the expected packet rate setting ≠ 1,

or the expected packet rate ≠ 0 ms,

(3) When the setting value = 1, or when the Expected

packet rate = 0 ms, the Watchdog timer monitoring is disabled.

(1) Always set the value = 1 or, in other word, set the

expected packet rate = 0 ms.

(1) Designate the data transmission interval from a

slave station to the master station.

(2) When the expected packet rate setting ≠ 1,

or the expected packet rate ≠ 0 ms,

(3) The setting value = 1 or the Expected packet rate

= 0 ms is prohibited.

MELSEC-A

Expected Packet Rate Production Inhibit Time

(1) Set the minimum transmission interval, or the

minimum time a slave can get the transmission data ready. The master station sends the polling request at this interval.

it must be the Expected packet rate ≥ the Production inhibit time.

(1) Set the minimum transmission interval, or the

minimum time a slave can get the transmission data ready. The master station sends the polling request at this interval.

it must be the Expected packet rate ≥ the Production inhibit time.

(3) This value must be the same for all bit strobe

connections.

(1) Always set the value = 1, or set the production

inhibit time = 0 ms.

(1) Designate the data transmission interval from the

master station to slave stations.

it must be the Expected packet rate ≥ the Production inhibit time.

(3) The setting value = 1 or the Production inhibit time

= 0 ms is prohibited.

3 − 26

Page 49

4. FUNCTIONS

This section describes the functions. The DN91 offers the following two types of functions. Proper parameter setting is required in advance.

• I/O communication functions (see Section 4.1)

• message communication functions (see Section 4.2)

4.1 I/O Communication Functions

The I/O communication functions conduct I/O data communication with the slave stations. The I/O communication functions allow the communication type to be set to match the slave station specification. Four connection types are available: polling, bit strobe, change of state, and cyclic. The connection type can be set using parameters.

SET Y(n+1)7

MELSEC-A

Slave stationDN91PLC CPU

1) Parameter set

Xn7 Parameter set complete

SET Y(n+1)1

Refresh command

FROM

Xn1 Refreshing

Refresh request

Refreshing

0000H

Iinput data

007FH

0080H

Output data

00FFH

area

Input

Output

[Parameter Set]

1) Write parameters onto the "Parameter" area of the buffer memory, and turn ON the parameter setting request (Y(n+1)1) via the sequence program to set the parameters. When the parameters are successfully written, the Parameter Setting Complete (Xn7) automatically turns ON. Once the parameters are set, no subsequent parameter setting is required as long as no change in the parameters is necessary. When setting the parameters via the configuration software, do not use the sequence program to set the parameters.

[Refresh]

2) Communication with the slave stations starts when the refresh request signal (Y(n+1)1) turns ON.

4 − 1

Page 50

4. FUNCTIONS MELSEC-A

[Input Data]

3) The input status of each slave station is automatically stored in the input data area of the DN91 buffer memory.

4) The input statuses stored in the input data area of the buffer memory are read to the PLC CPU using sequence program FROM instruction.

[Output Data]

5) The ON/OFF information output to the slave stations is written to the output data area of the buffer memory using the sequence program TO instruction.

6) The ON/OFF information stored in the output data area of the buffer memory is automatically output to the slave stations.

4 − 2

Page 51

4. FUNCTIONS

4.2 Message Communication Functions

The message communication functions read and write data to the slave station special area.

4.2.1 Get attribute

MELSEC-A

Slave station (MAC ID)DN91PC CPU

SET Y(n+1)2

Xn2

Xn2 Message communication complete

FROM

0110H

011FH

0120H

012FH

0130H

01A7H

Message communication command area

Message communication request

Message communication

result area

Message communication

data area

Message communication complete

Class

Instance

Attribute Attribute

Iinstance

Attribute

Class

Instance

Attribute

Instance

Attribute Attribute Attribute

1) Set "Get Attribute" in the buffer memory message communication command area using the sequence program TO instruction.

2) Turn ON message communication request (Y(n+1)2) with a sequence program to send the data set in the buffer memory message communication command area to the slave stations and start message communication.

3) DN91 receives data from the slave stations and processes it as follows:

• The slave station special data set in the message communication command area is

stored in the message communication data area of the buffer memory.

• The result of processing the message communication is stored in the message

communication results area of buffer memory.

4) When the process result is stored in the message communication results area of buffer memory, message communication ends and the message communication complete (Xn2) signal automatically turns ON.

5) When the slave station data ends normally in the buffer memory message communication area, it is read to the PC CPU using the sequence program FROM instruction.

4 − 3

Page 52

4. FUNCTIONS

4.2.2 Set attribute

MELSEC-A

SET Y(n+1)2

Following

Xn2 Message communication complete

processes

DN91PC CPU

0110H

011FH 0130H

01A7H

0120H

012FH

Message communication command area

Message communication

data area

Message communication request

Message communication

result area

Message communication complete

Slave station (MAC ID)

Class

Iinstance

Attribute Attribute

Class

Instance

Attribute

Instance

Attribute Attribute

Class

Instance

Attribute Attribute

Instance

Attribute

1) Set "Set Attribute" in the buffer memory message communication command area using the sequence program TO instruction.

2) Set the data to be written in the buffer memory message communication data area using the sequence program TO instruction.

3) Turn ON message communication request (Y(n+1)2) to write the data stored in the buffer memory message communication data area to the special area of the slave station set by the message communication command area.

4) When the write operation is complete, the message communication result is stored in the message communication results area of buffer memory.

5) When the process result is stored in the message communication results area of buffer memory, message communication ends and the message communication complete (Xn2) signal automatically turns ON.

4 − 4

Page 53

4. FUNCTIONS

4.2.3 Read communication error information

MELSEC-A

PC CPU

SET Y(n+1)2

Xn2

Xn2 Message communication complete

FROM

DN91

0110H

011FH

0120H

012FH 0130H

01A7H

Message communication command area

Message communication request

Slave information

storage area

Message communication

result area

Message communication

data area

Message communication complete

I/O Communi-

cation

Slave station (MAC ID)

Class 1

Instance

Attribute Attribute

Instance

Attribute Attribute Attribute

Class

Instance

Attribute Attribute Attribute

Instance

Attribute

*: Stores the status of each slave station during I/O communication.

1) Set "Read Communication Error Information" in the buffer memory message communication command area using the sequence program TO instruction.

2) Turn ON message communication request (Y(n+1)2) with a sequence program to read the accumulated error information from the relevant slave stations to the DN91.

3) DN91 receives data from the slave stations and processes it as follows:

• The slave station error information set in the message communication command area

is stored in the message communication data area of the buffer memory.

• The result of processing the message communication is stored in the message

communication results area of buffer memory.

4) When the process result is stored in the message communication results area of buffer memory, message communication ends and the message communication complete (Xn2) signal automatically turns ON.

5) The slave station communication error information stored in the buffer memory message communication data area is read to the PC CPU using the sequence program FROM instruction.

4 − 5

Page 54

5. SETTINGS AND PROCEDURES BEFORE OPERATION

DeviceNet cable.)

Parameter setting

completed?

"Communication

5. SETTINGS AND PROCEDURES BEFORE OPERATION

This section describes the procedure before start-up of a system using DN91.

5.1 Settings and Procedures

5.1.1 DN91 start-up procedure when setting parameters with a sequence program

Start

MELSEC-A

Modify the parameter-setting sequence program.

Develop a parameter-setting sequence program.

Mount DN91 on the base unit, and power ON the unit. (Set the CPU key switch to STOP, and do not connect the

Write the parameter-setting sequence program.

Set the CPU key switch to RUN. (Parameter setting completes.)

Set the CPU key switch to STOP, and turn OFF the power.

Connect the DeviceNet cable.

Power ON the DeviceNet network and slave stations.

successfully

YES

Refer to Section 6.3 and Section 7.

Set the CPU key switch to RUN.

Modify the parameter-setting sequence program.

Set the CPU key switch to STOP.

Power ON the unit. (Set the CPU key switch to STOP.)

Develop a control sequence program

Write the control sequence program onto the PLC CPU.

Set the CPU key switch to RUN.

error code"

(Monitor the buffer memory

area = 0?

to check it.)

Yes

Operates normally?

Yes

Operation

5 − 1

Modify the control sequence program.

Page 55

5. SETTINGS AND PROCEDURES BEFORE OPERATION

Files/Hilscher GmbH/SyCon/Fieldbus/DEVNet/EDS.)

"Communication

5.1.2 DN91 start-up when setting parameters with the configuration software

Start

Obtain EDS file for the slave station used from the manufacturer of the station.

Copy the EDS file onto the EDS storage folder of the configuration software. (If, for example, the software is installed in the folder "Program Files" of drive C, copy the file onto C:/Program

MELSEC-A

Write the parameters onto DN91.

Modify the parameters with the configuration software.

Prepare parameters with the configuration software.

Mount DN91 on the base unit, and power ON the unit. (Set the CPU key switch to STOP, and do not connect the DeviceNet cable.)

Write the parameters onto DN91.

Power OFF the unit.

Connect the DeviceNet network cable.

Power ON the DeviceNet network and slave stations.

Power ON the unit. (Set the CPU key switch to STOP.)

error code"

(Monitor the buffer memory

area = 0?

to check it.)

Yes

Refer to Section 6.4.

Develop a control sequence program.

Write the control sequence program onto the PLC CPU.

Set the CPU key switch to RUN.

Operates normally?

Yes

Operation

5 − 2

Modify the control sequence program.

Page 56

5. SETTINGS AND PROCEDURES BEFORE OPERATION

5.2 Mounting and Installation

This section describes handling instructions of the DN91 unit between unpacking and installation and the unit installation environment. For details about the DN91 unit mounting and installation, see the users manual for the PLC CPU unit being used.

5.2.1 Handling instructions

This section describes handling instructions related to the DN91. (1) The unit casing and terminal block are made of plastic. Do not drop the unit or apply

strong shocks to it.

(2) Do not remove the printed circuit board from the unit casing.

This can cause faults.

(3) During wiring operations, take care that no wiring offcuts or other foreign matter gets

inside the unit. Clean out any foreign matter that does get inside the unit.

MELSEC-A

(4) Tighten the unit mounting screws and terminal screws in the torque ranges specified

below.

5.2.2 Installation environment

Do not mount an A Series PC under in the following environments: (1) Locations where the ambient temperature is outside the range 0 to 55 °C.

(2) Locations where the ambient humidity is outside the range 10 to 90 %.

(3) Locations where condensation occurs due to sudden temperature fluctuations.

(4) Locations where corrosive or flammable gases exist.

(5) Locations with a high level of conductive dust or iron filings, oil mist, salt, or organic

solvent.

(6) Locations exposed to direct sunlight.

Type of Screw

A1SJ71DN91 Module mounting screw 78 to 118 (8 to 12) [6.93 to 10.48] DeviceNet Connector screw 35.3 to 48.0 (3.6 to 4.9) [3.13 to 4.26] DeviceNet Connector wire screw 60.8 to 82.3 (6.2 to 8.3) [5.40 to 7.31]

Tightening Torque Range

N ⋅⋅ cm (kg ⋅⋅ cm) [lb ⋅⋅ inch]

(7) Locations subject to strong electric or magnetic fields.

(8) Locations where vibrations or shocks are directly transmitted to the unit.

5 − 3

Page 57

5. SETTINGS AND PROCEDURES BEFORE OPERATION

5.3 Nomenclature

This section describes the AJ71DN91 and A1SJ71DN91 parts.

AJ71DN91

DeviceNet connector

MELSEC-A

J71DN91

RUN L.RUN MS NS

DeviceNet

RS-232-C

A1SJ71DN91

RS-232C connector

DeviceNet connector

1SJ71DN91

RUN L.RUN MS NS

DeviceNet

5 − 4

RS-232-C

RS-232C connector

Page 58

5. SETTINGS AND PROCEDURES BEFORE OPERATION

5.4 LED Displays and Indicator Descriptions

This section describes the names of the LEDs at the top of the AJ71DN91 and A1SJ71DN91 front panel and provides indicator descriptions.

MELSEC-A

J71DN91

1SJ71DN91

RUN L.RUN MS NS

LED

Name

RUN Red Normal opera-

L.RUN Red

Color Description LED Display Status

tion display

Communication status display

Green

Red Module status

Green Network status

Red Network status

Module status display

display

Lit Normal operation Not lit

Flashing

Lit Communicating Not lit Communication stopped Flashing (periodic) Preparing for communication Flashing (random) Communication parameter error Lit

Flashing Parameter error Not used

Lit Communication enabled with on-line

Flashing Communication not enabled with on-

Flashing There is a connection that has timed

Unit error detected No power supply Parameters being loaded Unit error detected Parameters being loaded

DeviceNet interface unit operating normally

slave stations

line slave stations Duplicate MAC ID errorLit Bus-off error occurred

out.

5 − 5

Page 59

5. SETTINGS AND PROCEDURES BEFORE OPERATION

5.5 Connecting Communication Cable to DN91

(1) Connecting communication cables

This section describes how to connect the communication cable to the DN91.

V+ (red)

CAN_H (white)

Shield (drain wire)

CAN_L (blue)

V- (black)

The DN91 DeviceNet connector is shown in the diagram above. The side of the connector is color-coded with the corresponding cable lead colors. Connect the communication cable, ensuring that each cable lead color matches the marking on the connector.

MELSEC-A

(2) Grounding the network

DeviceNet network is to be grounded at a single point. And select a point for grounding in the vicinity of the center of the network. Connect a cable shield (drain wire) to the ground of the power supply unit for Class-D (Class-3) grounding. If the network contains multiple power supply units, ground a unit that is positioned near the center of the network and do not ground at any other positions. When using multiple power supply units, use power taps.

Power tap

FG V+ V-

Power supply unit

Power tap

(near the center of the network)

FG V+ V-

Power supply unit

Power tap

V+ CAN_H Shield (drain wire) CAN_L V-

FG V+ V-

Power supply unit

5 − 6

Page 60

5. SETTINGS AND PROCEDURES BEFORE OPERATION

5.6 Instructions for Connecting the Network Power Supply

This sections describes the instructions for connecting the network power supply.

5.6.1 Network power supply unit installation position

Follow the procedure below to determine the position to install the network power supply unit.

1) Calculate the current consumption of the stations required on the network.

2) Measure the total length of the network.

3) Refer to Tables 5.1 and 5.2 to determine the maximum current capacity corresponding to

the network length and type of cable used.

4) If the current value calculated at step 1) is less than the current value calculated at step

3), any of the network power supply unit installation positions described in Section 5.6.2 can be used.

5) If the current value calculated at step 1) exceeds the current value calculated at step 3),

refer to Section 5.6.2 to determine whether the network power supply unit can be installed near the center of the network to supply power to all stations.

6) If the results from step 5) indicate that power cannot be supplied to all stations, increase

the number of network power supply units.

MELSEC-A

Table 5.1 Maximum Current Capacity Corresponding to

the Network Length of Thick Cable

Network length (m) 0 25 50 100 150 200 250 300 350 400 450 500 Maximum current (A) 8.00 8.00 5.42 2.93 2.01 1.53 1.23 1.03 0.89 0.78 0.69 0.63

Table 5.2 Maximum Current Capacity Corresponding to

the Network Length of Thin Cable

Network length (m) 0 10 20 30 40 50 60 70 80 90 100 Maximum current (A) 3.00 3.00 3.00 2.06 1.57 1.26 1.06 0.91 0.80 0.71 0.64

POINT

Use a network power supply unit with a current capacity exceeding the required total current consumption.

5 − 7

Page 61

5. SETTINGS AND PROCEDURES BEFORE OPERATION

Termination

Network

unit

Termination Termination

Termination

Network

unit

5.6.2 Calculating network power supply unit installation position and current capacity

This section describes the calculating network power supply unit installation position and current capacity.

(1) Network power supply unit connected to an end of the network

The current capacity is calculated as shown below when the network power supply unit is connected to the end of a thick-cable network with a total length of 200 m.

power supply

MELSEC-A

resistance

master

Master station

0.1A 0.15A 0.05A 0.25A 0.1A

Slave station Slave station Slave stationSlave station

200m

Total power supply distance = 200 m Total current capacity = 0.1 A + 0.15 A + 0.05 A + 0.25 A + 0.1 A = 0.65 A Max. current capacity of 200 m of thick cable (from Table 5.1) = 1.53 A

Therefore, this configuration allows power supply to all stations.

(2) Network power supply unit connected to the center of the network

The current capacity is calculated as shown below when the network power supply unit is connected at the center of a thick-cable network. In this case, the network power supply unit can supply twice the current compared to when it is connected to the end of the network.

power supply

resistance

Master

0.1A 0.25A 0.2A 0.25A 0.15A

Slave station Slave station Slave stationSlave station

120m

Slave station

0.15A

120m

Power supply distance left of the network power supply unit = power supply distance right of the network power supply unit = 120 m Total current capacity to the left = 0.1 A + 0.25 A + 0.2 A = 0.55 A Total current capacity to the right = 0.15 A + 0.25 A + 0.15 A = 0.55 A Max. current capacity of 120 m of thick cable (from Table 5.1) = approx. 2.56 A (Linearly interpolated between 100 m and 150 m.)

Therefore, this configuration allows power supply to all stations.

5 − 8

resistance

Page 62

5. SETTINGS AND PROCEDURES BEFORE OPERATION

Termination

Network

unit

Termination Termination

Network

(3) Remedy for Insufficient Network Power Supply Current Capacity

If the network power supply unit is connected to a thick-cable network, as shown below.

power supply

MELSEC-A

resistance

Master station Slave station Slave station Slave stationSlave station

1.1A 1.25A 0.5A 0.25A 0.85A

Slave station

0.25A

120m120m

Power supply distance left of the network power supply unit = power supply distance right of the network power supply unit = 120 m Total current capacity to the left = 1.1 A + 1.25 A + 0.5 A = 2.85 A Total current capacity to the right = 0.25 A + 0.25 A + 0.85 A = 1.35 A Max. current capacity of 120 m of thick cable (from Table 5.1) = approx. 2.56 A (Linearly interpolated between 100 m and 150 m.)

In this configuration, the current capacity to the left of the network power supply unit is insufficient. If this type of situation occurs, move the network power supply unit in the direction of insufficient current capacity (to the left in the diagram above).

power supply

resistance

Master station Slave station Slave station Slave stationSlave station

1.1A 1.25A

100m 140m

Total power supply distance left of the network power supply unit = 100 m Total power supply distance right of the network power supply unit = 140 m Total current capacity to the left = 1.1 A + 1.25 A = 2.35 A Total current capacity to the right = 0.5 A + 0.25 A + 0.25 A + 0.85 A = 1.85 A Max. current capacity of 100 m of thick cable (from Table 5.1) = approx. 2.93 A Max. current capacity of 140 m of thick cable (from Table 5.1) = approx. 2.19 A (Linearly interpolated between 100 m and 150 m.)

As a result of shifting the network power supply unit in the direction of insuffi-cient current capacity, it is able to supply power to all stations.

0.5A

Slave station

0.25A

resistance

0.25A 0.85A

5 − 9

Page 63

5. SETTINGS AND PROCEDURES BEFORE OPERATION

Network

Termination

(4) Mixed Trunk Line and Drop Line

The current capacity is calculated as shown below when the network power supply unit is connected to a network with 200 m of thick-cable trunk line and 6 m of thin-cable drop line.

power supply

MELSEC-A

resistance

Master station Slave stationSlave station Slave station

1.0A 0.15A 0.05A 0.25A

Slave station

0.1A

200m

Thick-cable power supply distance = 200 m Drop line power supply distance = 6 m Total current capacity = 0.5 A + 0.15 A + 0.05 A + 0.25 A + 0.1 A = 1.05 A Max. current capacity of 200 m of thick cable (from Table 5.1) = 1.53 A Max. current capacity of 6 m of drop line (from Table 5.3) = 0.75 A Total current of devices connected to drop line = 0.1 A

Therefore, this configuration allows power supply to all stations.

Table 5.3 Maximum Current Capacity Corresponding to

the Drop Line Length

Drop line length (m) 0.30 0.90 1.50 2.25 3.00 4.50 6.00 Max. current (A) 3.00 3.00 3.00 2.00 1.50 1.00 0.75

5 − 10

Page 64

6. PARAMETER SETTINGS

This section describes the parameter settings required for DN91 operation. The following two methods are available to set the parameters: Parameters that have been set are stored in separate areas on E2PROM within DN91. Once the parameters are set, no subsequent parameter setting is required as long as no change in the parameters is necessary.

• Setting with a sequence program (see Section 6.3)

• Setting with the configuration software (see Section 6.4)

6.1 Settings Parameter

The parameters may be set by the following two methods:

• Use TO command of the sequence program to set the parameters.

• Use the configuration software to set the parameters.

The following discusses the parameter-setting methods.

(1) Parameter setting by the sequence program

The sequence program-based parameter setting includes the following contents:

1) Host station number (MAC ID of the host station)

2) Baud rate

3) Station number of the n-th unit

4) Connection type of the n-th slave station

5) Number of byte modules for the n-th slave station

6) Number of word modules for the n-th slave station

7) Number of double-word modules for the n-th slave station

8) Expected packet rate for the n-th slave station

9) Watchdog timeout action for the n-th slave station

10) Production inhibit time for the n-th slave station

MELSEC-A

The setting of above-shown items 3) to 10) may be done for 63 units.

To construct a network of DeviceNet that contains DN91 as the master, setting station numbers (MAC IDs) is required for DN91 and slave stations. Station numbers available for them are 0 to 63, and any numbers may be used for DN91 and slave stations as long as they do not mutually overlap. Refer to the operation manual of the slave station for the procedure of setting station numbers (MAC IDs) of the slave stations.

For the procedure and details of setting parameters through the sequence program, refer to Section 7.3 “Setting Parameters with a Sequence Program” and 3.4.2 (14) “Buffer Memory”.

(2) Parameter setting by the configuration software

The Configuration software-based parameter setting includes the following contents:

1) Setting configuration

2) Master parameter setting

3) Bus parameter setting

4) Device (slave) parameter setting

For the procedure and details of setting parameters with the configuration software, refer to Section 6.4 “Setting Parameters with the Configuration Software”.

6.2 Important Points about the Parameter Settings

6 − 1

Page 65

6. PARAMETER SETTINGS

Setting the address mode to the byte address using the configuration software may result in the division of a word data into upper and lower bytes and may be stored in separate addresses of the buffer memory. For that reason, data processing by the sequence program may be required.

REMERK

See the slave station manual for details about the slave station data transfer specifications.

6.3 Setting with a Sequence Program

See the following sections for the methods of setting parameters with a sequence program:

3.3.2 (6) I/O Signal Details, 3.4.2 (14) Parameters, 7.3 Setting Parameters with a Sequence

Program.

POINT

MELSEC-A

Avoid any setting that validates both parameter setting procedures of using the sequence program and of using configuration software.

1) Setting parameters with the sequence program erases the parameter settings that have been set with the configuration software.

2) When using the configuration software to set the parameters, follow the setting procedure as shown below:

• Set the parameters, referring to 6.4 Setting Parameters with the Configuration

Software.

• To invalidate the settings that have been set with the sequence program, use the

sequence program to write FFFFH onto the host station number (01D4H) of the buffer memory and turn ON the parameter-setting request (Y(n+1)7).

6 − 2

Page 66

6. PARAMETER SETTINGS

6.4 Setting Parameters with the Configuration Software (Parameter Setting Tool)

This system gives an outline of the setting method using the configuration software. While the following explanations are based on screens of SyCon Ver. 2.0.6.2, the screen hierarchy and items of the setting are subject to change due to potential changes in the specifications of the configuration software. Refer to the operation manual of the configuration software for the latest information.

The following four steps are required to set the DN91 parameters:

1) Set configuration

2) Set master parameters

3) Set bus parameters

4) Set device (slave) parameters

6.4.1 Setting configuration

Set the DeviceNet network configuration on the screen below.

MELSEC-A

6 − 3

Page 67

6. PARAMETER SETTINGS

6.4.2 Setting master parameters

Set the master parameters on the screen below.

MELSEC-A

Set the items as follows:

1) Startup behavior after system initialization Select "Controlled release of the communication by the application program."

2) User program monitoring This is the time to monitor whether the DN91 is operating normally (units: 1 msec). Set a value of 30 msec, or higher.

3) Addressing mode Select byte addressing or word addressing as the addressing mode.

4) Storage format Designate the data format of the word data. Select "Little Endian."

5) Handshake of the process data Select buffered or device controlled.

6) Hardware parameter Select "8 KB dual-port memory."

6 − 4

Page 68

6. PARAMETER SETTINGS

6.4.3 Setting bus parameters

Set the bus parameters on the screen below.

Set the items as follows:

1) Baudrate Select one of the following baud rate settings:

• 125 Kbit/s (125 kbaud)

• 250 Kbit/s (250 kbaud)

• 500 Kbit/s (500 kbaud)

2) MAC ID Master Set the DN91 station number as a value from 0 to 63.

MELSEC-A

3) Heartbeat Timeout Set the interval for checking any existence of slave stations.

4) Auto clear mode on Set to turn OFF, or not, output to all stations in case an error occurs with any single station.

6 − 5

Page 69

6. PARAMETER SETTINGS

6.4.4 Set the device (slave station) parameters

Set the slave station parameters on the screen below.

MELSEC-A

Set the items as follows:

1) MAC ID Set the slave station number as a value from 0 to 63.

2) Description Enter a name for the slave station.

3) Activate device in actual configuration Set whether the station is an actively communicating station or a reserved station.

• Checked : Actively communicating station

• Not checked : Reserved station

4) Actual chosen IO connection Select the I/O data communication type: Polling, bit strobe, change of

state, or cyclic.

5) UCMM check Set if a slave station has the UCMM functionality or not. If it does, also set the message group that is used for message communication.

6) Fragmented Timeout Set the time for waiting for the acknowledgement of receipt from a slave station for the case of divided message transmission and receipt.

7) Expected packet rate Set the expected packet rate. See 3.4.2(14) Parameters for details about the settings.

8) Production inhibit time Set the production inhibit time. See 3.4.2(14) Parameters for details about the settings.

6 − 6

Page 70

6. PARAMETER SETTINGS

9) Watchdog timeout action

Set the action on a watchdog timeout. See 3.4.2(14) Parameters for details about the settings.

10) Configured I/O connection data and its offset address

Set the I/O module configuration. Also, set I. Addr and O. Addr to the DN91 buffer memory address allocated to the I/O module I/O data.

MELSEC-A

6 − 7

Page 71

7. PROGRAMMING

X0F

Communication program

Unit error

Unit ready

X0F

Unit error

Unit ready

Station number 0 error processing program

K4M0 H1BC

FROM

Station number 1 error processing program

Station number 0 normal processing program

Station number 1 normal processing program

Slave communication status

Refresh processing request, I/O communication read program

I/O communication write program

7. PROGRAMMING

This section describes how to create programs.

7.1 Important Points about Programming

Follow the points below when creating a program.

(1) Creating a Slave Station I/O Communication Program

• Place the I/O communication reading program at the beginning of the sequence

program.

• Place the I/O communication writing program at the end of the sequence program.

MELSEC-A

(2) Read received data and write send data when no unit error has occurred and the unit is

in ready status.

(3) Create a program to detect the communication status of each station and apply an

interlock. Also, create processing programs to handle faults.

(4) In case parameter setting has been done previously with the sequence program, the

settings are stored in the buffer memory when powered ON. To set the parameters from the scratch, clear the "Parameter" area of the buffer memory to zero(0).

7 − 1

Page 72

7. PROGRAMMING

Polling

Bit strobe

X100 to X10F : Input data

A(1S)J71DN91

7.2 System Configuration

The program described in this section is based on the system described below.

1) DN91 is set to station number 5, the first sensor is set to station number 1, and the second

2) Bit strobe communication is used between DN91 and station number 5.

3) Input data is assigned from X100 to X117 and output data is assigned from Y100 to Y10F.

4) The communication status of each station is stored in M0 and M1.

5) If an error occurs, the error information is read to D500, the station number where the error

6) Message communication write attribute data is set in D30 to D39.

7) DN91 is mounted in slot 0 of the main base unit.

MELSEC-A

remote I/O is set to station number 0.

Polling communication is used between DN91 and the remote I/O.

Sensor : Inputs X100 to X117 Remote I/O : Inputs X100 to X117

: Outputs Y100 to Y10F

occurred to D501, and the error code to D502.

station number 1

Station number 4

Rockwell Automation Japan

Flex I/O DeviceNet adapter + 16-point input

(1794ADN + IB16)

*: The Flex I/O DeviceNet adapter by Rockwell Automation Japan has 2-byte input data.

Both IB16 and OB16 have 2-byte input data and 2-byte output data.

Y100 to Y10F : Output data M3, M4 : Communication status of each station D500 : Error information D501 : Station number where error occurred D502 : Error code D30 : Write attribute data

Station number 3

Rockwell Automation Japan

Flex I/O DeviceNet adapter + 16-point input

(1794ADN + OB16)

7 − 2

Page 73

7. PROGRAMMING

Y10F to Y100

X10F to X100

DN91 master station

FROM

PLC CPU

Input data

Output 15 to output 00

Output data

Remote I/O (station number 3)

0001

0003H0002H0000

0080H0081

Status

Input 15 to input 00

Dummy output

I15 to 00

Status

O15 to O00

Dummy output

The relationship between the PLC CPU, master station buffer memory, first slave station (remote I/O), and second slave station (remote I/O) is shown below.

MELSEC-A

Remote I/O (station number 4)

16-point input

16-point output

7 − 3

Page 74

7. PROGRAMMING

Y17

MOVP

D0K1MOVP

H104

MOVP

D4H2MOVP

H204

MOVP

X0FX1X7

MOVP

D8K1MOVP

MOVP

D10K0MOVP

D11

Y17

H103

MOVP

D12H1MOVP

D13

H204

MOVP

D14H0MOVP

D15

MOVP

D16

X0FX1X7

K501

MOVP

D17

MOVP

D18

K200MOD19D0H1D4

TOP

K20

SET

Y17

RST

Y17

RST

K21

MOVP

D19

Y17

7.3 Setting Parameters with a Sequence Program

This section describes a sample sequence program to set parameters.

Parameter set command

MELSEC-A

Set host station to 1.

Set baud rate to 500 kbps.

Set first slave station (sensor) to station number 4.

Connection to sensor Set connection type to bit strobe.

Input byte module = 4 Output byte module = 2

Input word module = 0 Output word module = 0 Input double-word module = 0 Output double-word module = 0

Expected packet rate Default = 500 ms

Watchdog timeout action default = TIMEOUT

Production inhibit time Default = 10 ms

Set second slave station (remote I/O) to 3.

Set to polling the connection type for the second slave station. Input byte module = 4 Output byte module = 2

Input word module = 0 Output word module = 0

Input double-word module = 0 Output double-word module = 0

Expected packet rate = 500ms

Watchdog timeout action = Auto erase Production inhibit time = 20 ms

Write parameter data to the buffer memory parameter area. Set parameter set request.

Reset parameter set request.

Parameter set command

7 − 4

Page 75

7. PROGRAMMING

Stores host station number 1

PLC CPU

Buffer memory

01D4

01D5

−

01D6

−

01D7

H104

01D8

01D9

H204

01DA

01DB

01DC

01DD

D10

01DE

D11

01DF

D12

H103

01E0

D13

01E1

D14

H204

01E2

D15

01E3

D16

01E4

D17

K501

01E5

D18

01E6

D19

K21

01E7

AUTO DELETE

The relationship between PLC CPU and master station buffer memory and the meaning of buffer memory data is shown below.

MELSEC-A

Stores baud rate = 500 kbaud Unused Unused Stores station number of first slave station = 4 Stores connection type of first slave station = bit strobe Stores input/output byte modules of first slave station Stores input/output word modules of first slave station Stores input/output double-word modules of first slave station Set expected packet rate of first slave station to default value Stores watchdog timeout action type of first slave station = TIMEOUT Set production inhibited time of first slave station to default value Stores station number of second slave station = 3 Stores connection type of second slave station = polling Stores input/output byte modules of second slave station Stores input/output word modules of second slave station Stores input/output double-word modules of second slave station Stores expected packet rate of second slave station = 500 ms Stores watchdog timeout action type of second slave station = Stores production inhibited time of second slave station = 20 ms

7 − 5

Page 76

7. PROGRAMMING

X0FM4M4X1X0F

X101

Parameter setting program

X0F

Parameter setting program

Refresh request program

Y100

K4Y100

H81

Y102

Y103

Y105

Y107

M3X0X0F

Refresh

Station number 4 error processing program

X100

K4Y100

H80H0TOPK1K4M0

H1BC

FROM K4

Y11

K4X100

FROM

7.4 I/O Communication with Slave Stations

This section describes a sample sequence program to conduct I/O communication.

7.4.1 Reading slave station I/O data

Parameter request program

command

MELSEC-A

Parameter setting program (see Section 7.3)

Output data initial value setting Refresh request

Read communication status

Read input data

Station number 4 input data processing program

7.4.2 Writing slave station I/O data

Station number 3 output data processing program

Parameter setting program (see Section 7.3)

Refresh request program (see Section 7.4.1)

Write output data

7 − 6

Page 77

7. PROGRAMMING

Writing

Read

Error processing program

X0FX2Y12X2Y12

Reading

H101

MOVP

D0D0H110H0TOPK4H0503

MOVP

D1K2MOVP

D2K9MOVP

D10

H120H0FROMP

SET

Reading

SET

Y12K0<>

D11

K0=D11

DECP

D14K2D14/PD14

INCP

D14

MOVP

D20

H130H0FROMP

K0Z

RST

Y12

RST

Read

7.5 Message Communication

This section describes a sample sequence program to conduct message communication.

7.5.1 Message communication - reading

The following sample program represents a case of reading attributes of expected packet rate for the polling connection from the station number 3.

attributes

MELSEC-A

Set attribute read command

Station number 3 slave station Class ID =5

Instance ID = 2

Attribute ID = 9

Write request data to buffer memory

attributes

Set message communication request

Read result from buffer memory

Calculate read length of received data

Read received data

Reset message communication request

7 − 7

Page 78

7. PROGRAMMING

Reading

Error processing program

X0FX2Y12X2Y12

Writing

H102

MOVP

H110 H0

TOPK4H0503

MOVP

H209

MOVP

D10

H120

FROMP

SET

Writing

K0<>D11

RST

Y12

RST

Write

D30

H130H0TOP

Reading

Write

K1000

MOV

D30

SET

Y12

7.5.2 Message communication - writing

The following sample program represents a case of writing attributes of expected packet rate for the polling connection from the station number 3.

attributes

MELSEC-A

Set onto D30 the data to be written.

Write send data to buffer memory

Set attribute write command

Station number 3 slave station Class ID = 5

Instance ID = 2

Send data byte length=2 Attribute ID =9

attributes

Write request data to buffer memory

Set message communication request

Read result from buffer memory

Reset message communication request

7 − 8

Page 79

7. PROGRAMMING

D500

MOVP

D502

SFRP

D500

H1B1H0FROMP

D500

H0FF

WANDP

D501

RST

Y13X3SET

Y13

7.6 Acquiring Error Information

This section describes a sample sequence program to acquire error information.

Error reset

MELSEC-A

Read error information

Station number generating error

Error information

Error code

Set error reset request

Reset error reset request

7 − 9

Page 80

8. TROUBLESHOOTING

This section describes errors which may occur when using a DN91 master unit and the troubleshooting procedures.

This section is divided into the following sub-sections.

Section 8.1 Troubleshooting Tables

Determine the appropriate remedy from the symptom of the problem.

Section 8.2 Troubleshooting using LED Indications

Determine the appropriate remedy from the LED indicator status.

Section 8.3 Troubleshooting using Error Codes

Determine the appropriate remedy from the error codes. The timing to check the error codes and the reference buffer memory are

shown below.

Timing to Check Error Codes Error Codes to Check Remedy

When the error set signal (Xn3) turns ON

When the message communication complete signal (Xn2) turns ON.

Communication error code (01B1H, upper byte)

Error code (0121H) after conducting message communication.

Take remedial actions in accordance with Section

8.3.1 “Communication error codes”.. See 8.3.2 Execution Error Codes for Message

Communication.

MELSEC-A

8 − 1

Page 81

8. TROUBLESHOOTING

8.1 Troubleshooting Tables

Determine the appropriate remedy from the symptom of the problem.

8.1.1 Troubleshooting by Symptom Type

Refer to the following tables to determine the appropriate remedy for the symptom.

Symptom Check Item Remedy

No Communication With Any Slave Station Is communication cable connected to the DN91 DeviceNet interface connector? Are cable locking screws fully tightened? Check that the communication cable is correctly connected, referring to 5.5 Connecting Communication Cable to DN91.

Is the network power supply connected? Is the power turned ON?

Is the network power supply capacity sufficient?

Is the position where the network power supply is connected OK? Determine whether the network power supply is connected to a suitable position, referring to 5.6 Instructions for

Connecting the Network Power Supply. No Communication With Any Slave Station

Does any slave station have the same station number as

the DN91?

Is refresh request (Y(n+1)1) ON?

Is a termination resistance correctly connected to each end

of the network?

Is the same baud rate set for each station?

Does the cable length exceed the permitted limit?

Check the cable length restrictions appropriate for the cable

thickness and baud rate, referring to 3.2 Performance

Specifications.

Check the parameter settings.

Check the error codes.

See 8.3 Troubleshooting using Error Codes.

MELSEC-A

Correctly connect the cable.

Turn ON the network power supply.

Replace with a power supply of larger capacity.

Add a power supply. Reduce the network load.

Change the position where the network power supply is connected.

Set the station numbers to avoid duplication.

Turn ON refresh request (Y(n+1)1) with a sequence program.

Check if termination resistances are connected and if they are connected correctly.

Make sure that the same baud rate is set for each station.

Reduce the cable length. Reduce the baud rate. If thin cable is used in the trunk line,

replace it with thick cable. See 8.1.2 Problems Due to Incorrect

Parameter Settings

Remedy for error code

8 − 2

Page 82

8. TROUBLESHOOTING

Symptom Check Item Remedy

Is the power supply connected to that station? Turn ON the slave station power supply.

Is the network power supply capacity sufficient?

Is the position where the network power supply is connected

OK?

Determine whether the network power supply is connected

to a suitable position, referring to 5.6 Instructions for

Connecting the Network Power Supply.

Is the communication cable correctly connected to that slave

unit (no discontinuity)?

No Communication With Slave Stations After A Certain Station

No Communication With A Certain Station

Are the slave stations set in the parameters?

Is a termination resistance correctly connected to each end

of the network?

Is the same baud rate set for each station?

Does the cable length exceed the permitted limit?

Check the cable length restrictions appropriate for the cable

thickness and baud rate, referring to 3.2 Performance

Specifications.

Check the parameter settings.

Check the error codes.

See 8.3 Troubleshooting using Error Codes.

Is the power supply connected to that station? Turn ON the slave station power supply.

Is the network power supply capacity sufficient?

Is the position where the network power supply is connected

OK?

Determine whether the network power supply is connected

to a suitable position, referring to 5.6 Instructions for

Connecting the Network Power Supply.

Is the communication cable correctly connected to that slave

unit?

Is the slave station set in the parameters? Set the slave station in the parameters.

Is the slave station set as a reserved station in the

parameters?

Does any slave station have the same station number as

another slaves station?

Station number in the parameters differs from the station

number of the actual slave station.

Do the I/O data length and I/O communication connection

type in the parameters match those of the actual station?

MELSEC-A

Replace with a power supply of larger capacity.

Add a power supply. Reduce the network load.

Change the position where the network power supply is connected.

Correctly connect the cable.

Set the slave stations in the parameters. If a station is set as a reserved station, change the parameter setting to actively communicating station.

Check if termination resistances are connected and if they are connected correctly.

Make sure that the same baud rate is set for each station.

Reduce the cable length. Reduce the baud rate. If thin cable is used in the trunk line,

replace it with thick cable. See 8.1.2 Problems Due to Incorrect

Parameter Settings Take the remedy described for the error

code.

Replace with a power supply of larger capacity.

Add a power supply. Reduce the network load.

Change the position where the network power supply is connected.

Correctly connect the cable.

Change the slave station from a reserved station to an actively communicating station.

Set the station numbers to avoid duplication.

Set the station number in the parameters to match the station number of the actual slave station.

Set the I/O data length and I/O communication connection type in the parameters to match those of the actual station.

8 − 3

Page 83

8. TROUBLESHOOTING

Symptom Check Item Remedy

Is the correct I/O data area referred to in buffer memory?

Check that the I/O data area is correct, referring to 3.4.2

Details of the Buffer Memory.

Is the correct baud rate set for the slave station?

Is a termination resistance correctly connected to each end

of the network? No Communication With A

Certain Station

Cannot Read Message Communication

Cannot Write Message Communication

Cannot Read Message Communication Errors

A Communication Error Occurs when DeviceNet is Started Up

Does the cable length exceed the permitted limit?

Check the cable length restrictions appropriate for the cable

thickness and baud rate, referring to 3.2 Performance

Specifications.

Check the parameter settings.

Check the error codes.

See 8.3 Troubleshooting using Error Codes.

Is Get Attribute (0101H) stored in the message

communication command area of buffer memory?

Also, are the correct station number of the slave station,

class ID, instance ID, and attribute ID stored in the message

communication command area of buffer memory?

Is message communication write processing or message

communication error read processing conducted at the

same time as the message communication read program is

executed?

Is Set Attribute (0102H) stored in the message

communication command area of buffer memory?

Also, are the correct station number of the slave station,

class ID, instance ID, and attribute ID stored in the message

communication command area of buffer memory?

Is message communication read processing or message

communication error read processing conducted at the

same time as the message communication write program is

executed?

Is Read Communication Error Information (0001H) stored in

the message communication command area of buffer

memory? Also, is the correct station number of the slave

station stored in the message communication command

area?

Is message communication read processing or message

communication write processing conducted at the same

time as the message communication error read program is

executed?

Are parameters set by the configuration software and

parameters set by the sequence program both valid?

MELSEC-A

Set the correct reference area.

Make the baud rate setting match the baud rate setting at the slave station.

Check if termination resistances are connected and if they are connected correctly.

Reduce the cable length. Reduce the baud rate. If thin cable is used in the trunk line,

replace it with thick cable. See 8.1.2 Problems Due to Incorrect

Parameter Settings Take the remedy described for the error

code.

Modify the sequence program to store the correct values.

Modify the sequence program so that these are executed at different times.

Modify the sequence program to store the correct values.

Modify the sequence program so that these are executed at different times.

Modify the sequence program to store the correct values.

Modify the sequence program so that these are executed at different times.

Disable one set of parameters, referring to 6.2 Setting with a Sequence Program.

8 − 4

Page 84

8. TROUBLESHOOTING

8.1.2 Problems due to incorrect parameter settings

Refer to the following tables to determine the appropriate remedy for problems arising due to incorrect parameters or an incorrect sequence program.

Symptom Check Item Remedy

Parameters Cannot be Set by Sequence Program (Parameter set complete (Xn7) does not turn ON after parameter set request (Y(n+1)7) turns ON.)

Parameter settings made by the sequence program are ignored.

Parameter settings made by the configuration software are ignored.

Is refresh request (Y(n+1)1) ON before parameter set request (Y(n+1)7) turns ON? Also, is refresh request (Y(n+1)1) ON before parameter set complete (Xn7) turns ON?

Is FFFFH stored in the host station number storage area of buffer memory?

Have parameter settings made by the sequence program been disabled?

Have the parameter settings made by the configuration software been disabled using the configuration software settings?

MELSEC-A

Ensure refresh request (Y(n+1)1) does not turn ON between parameter set request (Y(n+1)7) turning ON and parameter set complete (Xn7) turning ON.

Store a station number from 0 to 63 in the host station number storage area of buffer memory.

Set FFFFH as the host station number in buffer memory with the sequence program.

Change the parameter settings, referring to 6.3 Setting Parameters with the Configuration Software.

8.2 Troubleshooting Using LED Indications

Determine the cause of the error from the LED indicator status and take the appropriate remedy.

8.2.1 Errors caused by the master unit

RUN

L.RUN

LED

LEDMSLEDNSLED

l l

O O  

O ¥  

GreenlGreen

Normal operation None None

PC power supply is not turned ON.

Abnormal DN91 unit

Error is caused by another unit.

Abnormal DN91 unit Is DN91 unit defective? Repair or replace the DN91 unit.

Parameters being loaded Wait and see

Status Check Item Remedy

Is PC power supply turned ON? Turn ON the power supply.

Correctly mounted in base unit? Correctly mount in base unit. Is DN91 unit defective? Repair or replace the DN91 unit. Is another unit (including the

base unit) defective?

l : Lit O : not lit ¥: Flashing ¥ r: Flashing (random)  : Undetermined

Repair or replace the unit.

DN91 unit is defective if flashing continues. Repair or replace the DN91 unit.

8 − 5

Page 85

8. TROUBLESHOOTING MELSEC-A

8.2.2 Errors caused by incorrect parameter settings or abnormal network

RUN

L.RUN

LED

LEDMSLEDNSLED

l O   Communication stopped Are parameters set? Set parameters.

l ¥   Communication ready Wait and see

l ¥ r   Parameter error Check the parameters. Correct the parameters.

l 

l l

Green

GreenlRed¥Timeout occurred at a

 Parameter error Check the parameters. Correct the parameters.

connection.

Status Check item Remedy

Parameters are defective if flashing continues. Repair or replace the parameters.

Wrong connection type for a slave station?

Is the slave station power turned ON?

Is the same baud rate set for all slave stations?

Is a termination resistance connected?

Is the communication cable correctly connected?

Does the total cable length exceed the permitted limit?

Does the drop line length or total drop line length exceed the permitted limit?

Is the network power supply correctly connected?

Is the network power supply capacity sufficient?

Is the production inhibit time set too short in the parameters?

Is the expected packet rate set too short in the parameters?

Incorrect slave I/O data length in the parameters?

Correct the parameters.

Turn ON the slave station power.

Set the same baud rate for all slave stations.

Connect a termination resistance.

Correctly connect the communication cable.

Reduce the baud rate. Reduce the total cable length. Reduce the baud rate. Reduce the drop line length or

total drop line length. Correctly connect the network

power supply. Increase the network power

supply capacity. Change the position of the

network power supply.

Correct the parameters.

l : Lit O : Not lit ¥: Flashing ¥ r: Flashing (random)  : Undetermined

8 − 6

Page 86

8. TROUBLESHOOTING

RUN

L.RUN

LED

LEDMSLEDNSLED

l l

Duplicate station number error

GreenlRed

Bus-off error

Green Green¥Online communication not

established

MELSEC-A

Status Check item Remedy

Is a station number used for more than one station?

Is the same baud rate set for all stations?

Is a termination resistance connected?

Is the communication cable correctly connected?

Does the total cable length exceed the permitted limit?

Reduce the total cable length.

Wrong connection type for a slave station?

Is the slave station power turned ON?

Is the same baud rate set for all stations?

Is a termination resistance connected?

Is the communication cable correctly connected?

Does the total cable length exceed the permitted limit?

Does the drop line length or total drop line length exceed the permitted limit?

Is the network power supply correctly connected?

Is the network power supply capacity sufficient?

Is the production inhibit time set too short in the parameters?

Is the expected packet rate set too short in the parameters?

Incorrect slave I/O data length in the parameters?

Correct the station numbers.

Set the same baud rate for all stations.

Connect a termination resistance.

Correctly connect the communication cable.

Reduce the baud rate. Is the network power supply

capacity sufficient? Increase the network power

supply capacity. Change the position of the

network power supply.

Correct the parameters.

Turn ON the slave station power.

Set the same baud rate for all stations.

Connect a termination resistance.

Correctly connect the communication cable.

Reduce the baud rate. Reduce the total cable length. Reduce the baud rate. Reduce the drop line length or

total drop line length. Correctly connect the network

power supply. Increase the network power

supply capacity. Change the position of the

network power supply.

Correct the parameters.

l : Lit O : Not lit ¥: Flashing ¥ r: Flashing (random)  : Undetermined

8 − 7

Page 87

8. TROUBLESHOOTING

8.3 Troubleshooting Using Error Codes

Determine the problem and the appropriate remedy from the error codes. Error codes include communication error codes and execution error codes for message communication.

(1) Check the details of the communication error codes by turning on the error reset signal

(Xn3) to read the error codes.

(2) Check the details of the message communication execution error codes by turning ON

the message communication complete signal (Xn2) to read the error codes.

8.3.1 Communication error codes

Error information is stored at address 0131H in buffer memory. It is separated into an upper byte and a lower byte.

Upper byte: Error code Lower byte: Station number where error was detected

MELSEC-A

Buffer memory

01B1H

Lower byteUpper byte

Station number where error was detected Error code

(1) In case the error-detected station number (lower byte of the error data) is FFH:

Error Code

35 H DN91 36 H DN91 Host station number (MAC ID) is out of range.. • Set the host station number in a range of 0 to 63.

39 H DN91

D2 H DN91

Error

Detected

Details Remedy

Baud rate setting is out of range.

There are two or more stations in the network that have the same station number (MAC ID).

No configuration software-based parameters are set.

• Properly set the baud rate.

• Set station numbers to avoid duplication.

• Set the parameters with the configuration software.

(When the parameters are set with the sequence program, the error code has no significance.)

8 − 8

Page 88

8. TROUBLESHOOTING

(2)In case the error-detected station number (lower byte of the error data) is FEH:

Error Code

Error

Detected

MELSEC-A

Details Remedy

01 H DN91

02 H DN91

03 H DN91

04 H DN91

05 H DN91

06 H DN91

07 H DN91 No slave station is set. • Set at least one slave station.

08 H DN91

09 H DN91

0A H DN91

0B H DN91

0C H DN91 E2PROM check-sum error.

Host station number (MAC ID) in the buffer memory is out of range.

Baud rate in the buffer memory setting is out of range.

Lower byte of the slave station in the buffer memory setting is out of range.

Upper byte of the slave station in the buffer memory setting is out of range.

Connection type in the buffer memory setting is out of range.

There is a slave station set in the buffer memory having the same station number as with the host station.

Total length of all input data for all slave stations is too large.

Total length of all output data for all slave stations is too large.

Watchdog timeout action value in the parameters is illegal.

Expected packet rate in the buffer memory is smaller than the production inhibit time.

• Set the host station number within 0000H to 0003H or FFFFH.

• Set the value within 1 to 3.

• Set within 0 to 63.

• Set at 01H or 80H.

• Set one of 0001H, 0002H, 0004H, and 0008H.

• Set the station numbers to avoid any overlap among

all stations.

• Keep the total length of 256 bytes or less for all slave stations.

• Set one of 0000H, 0001H, 0002H, and 0003H.

• Set the value of Expected packet rate >= Production

inhibit time.

• Rewrite the parameters.

• Avoid powering OFF or resetting in the midst of

writing the parameters.

8 − 9

Page 89

8. TROUBLESHOOTING MELSEC-A

(3) In case the error-detected station number (lower byte of the error information) is any

value other than FFH and FEH:

Error Code

01 H DN91

1E H DN91 The slave station did not respond.

20 H

23 H

24 H DN91

25 H DN91

26 H DN91

27 H

28 H DN91

29 H

2A H DN91

2B H DN91

2C H DN91

2D H DN91

3B H DN91

45 H DN91 O-address in the parameters exceeds 255. • Set the O-address at 255 or less. 46 H DN91 I-address in the parameters exceeds 255. • Set the I-address at 255 or less. 47 H DN91 Illegal connection type is designated. • Check if the connection type value is correct.

49 H DN91

Error

Detected

Slave

station

Slave

station

Slave

station

Slave

station

Details Remedy

A fault has been detected with the network after communication being started.

The slave station responded with an error that is not defined.

The slave station responded with an error when establishing a connection.

Input data size of the parameters differs from the size of the actual slave station

Output data size of the parameters differs from the size of the actual slave station.

Received response data for the function that is not supported by DN91.

The connection is already in the designated mode.

Unexpected illegal data has been received when establishing a connection.

Connection is already established with the slave station.

Polling response data length differs from the length of data that has been read from the slave station when establishing a connection.

The first division data has been received twice during divided receipt of polling response.

Division data number that has been received is not what is expected during divided receipt of polling response.

Intermediate or the last data has been received before receiving the first division data during divided receipt of polling response.

Two or more station numbers of the same MAC ID have been detected in the parameters.

The value of the expected packet rate is less than that of the production inhibit time.

• Check if cables are properly connected.

• Inspect the state of the network and slave stations

closely: Are MAC IDs and baud rate properly set? Any faulty slave stations? Any missing terminal resistance? etc.

• Read the communication error information, and take remedial actions thereupon.

• Refer to the operation manual of the slave station, and set a proper input data size.

• Refer to the operation manual of the slave station, and set a proper output data size.

• Refer to the operation manual of the slave station, and avoid sending from the slave station any function that is not supported by DN91.

• Inspect the state of the network and slave stations closely as for any missing terminal resistance.

• Wait and observe for a while, and if the connection is not established, reset the slave station.

• Inspect the state of the network and slave stations closely as for any missing terminal resistance.

• The parameters contain two or more slave stations having the same station number. Correct the station numbers.

• The parameters contain slave station(s) of the same station number as the host station number.

• Set the expected packet rate value greater than that of the production inhibit time.

8 − 10

Page 90

8. TROUBLESHOOTING

8.3.2 Execution error codes for message communication

The execution error codes are stored at address 00A1H in buffer memory.

Normal completion : 0000H Faulty : Execution error code

Buffer memory

0121H

(1) Reading communication error information

MELSEC-A

Normal completion: 0000H Faulty : Execution error code

Error Code

161 DN91

Error Code

Error

Detected

Error

Detected

Slave

station

Slave

station

Slave

station

Slave

station

Details Remedy

Designated slave station number is outside the range 0 to 63.

(2) Reading/writing attributes

Details Remedy

The required resources could not be used for the object to execute a requested service.

The requested service was not mounted or was not defined for this object class or instance.

Invalid attribute data was detected.

The object is already in the mode or status requested by the service.

• Designate from 0 to 63.

• Refer to the slave station manual to determine the

conditions for the slave station to notify this error, and take the appropriate remedy.

• Check if the designated station number, class ID, instance ID, and attribute ID are correct.

• Refer to the slave station manual to determine the conditions for the slave station to notify this error, and take the appropriate remedy.

• Check if the designated station number, class ID, instance ID, and attribute ID are correct.

• Refer to the slave station manual to determine the conditions for the slave station to notify this error, and take the appropriate remedy.

• Check if the designated station number, class ID, instance ID, and attribute ID are correct.

• Use Get Attribute to confirm the current status.

• Refer to the slave station manual to determine the

conditions for the slave station to notify this error, and take the appropriate remedy.

Slave

station

Slave

station

The object cannot execute the requested service in the current mode or status.

A request was received to change a protected attribute.

8 − 11

• Check if the designated station number, class ID, instance ID, and attribute ID are correct.

• Use Get Attribute to confirm the current status.

• Refer to the slave station manual to determine the

conditions for the slave station to notify this error, and take the appropriate remedy.

• Check if the designated station number, class ID, instance ID, and attribute ID are correct.

• Refer to the slave station manual to determine the conditions for the slave station to notify this error, and take the appropriate remedy.

Page 91

8. TROUBLESHOOTING MELSEC-A

Error Code

17 DN91 The slave station did not respond.

50 DN91 Incorrect response data format.

55 DN91

57 DN91 Incorrect sequence during packet receipt.

200 DN91

257 DN91 Data length set in buffer memory exceeds 241. • Set the data length 240 or less.

258 DN91

Error

Detected

Slave

station

Slave

station

Slave

station

Slave

station

Slave

station

Slave

station

Details Remedy

The enabled/privilege check failed

The requested service cannot be executed in the current device status.

Insufficient data supplied after the designated operations were conducted.

The designated attribute is not supported.

The service supplied more data than expected.

The designated object does not exist in the slave station.

Designated slave station number is outside the range 0 to 63.

No parameters set for the designated slave station.

Incorrect value was set in command number of buffer memory message communication command area.

• Check if the designated station number, class ID, instance ID, and attribute ID are correct.

• Refer to the slave station manual to determine the conditions for the slave station to notify this error, and take the appropriate remedy.

• Check if the designated station number, class ID, instance ID, and attribute ID are correct.

• Refer to the slave station manual to determine the conditions for the slave station to notify this error, and take the appropriate remedy.

• Investigate overall status of network and slave station. Is the slave station down, or the termination resistance disconnected, for example?

• Check if the designated station number, class ID, instance ID, and attribute ID are correct.

• For Set Attribute, check if the designated data is insufficient and the data length is correct.

• Refer to the slave station manual to determine the conditions for the slave station to notify this error, and take the appropriate remedy.

• Check if the designated station number, class ID, instance ID, and attribute ID are correct.

• Refer to the slave station manual to determine the conditions for the slave station to notify this error, and take the appropriate remedy.

• Set the data returned by the slave station to 240 bytes maximum.

• Check if the designated station number, class ID, instance ID, and attribute ID are correct.

• Refer to the slave station manual to determine the conditions for the slave station to notify this error, and take the appropriate remedy.

• Investigate overall status of network and slave station. Is the termination resistance disconnected, for example?

• Designate from 0 to 63.

• Investigate overall status of network and slave

station. Is the termination resistance disconnected, for example?

• Designate a slave station with set parameters.

• Set one of 0000H, 0001H, 0002H, and 0003H

command number.

8 − 12

Page 92

APPENDICES

250 (9.84)

APPENDICES

APPENDIX 1 External View

1.1 AJ71DN91

J71DN91

DeviceNet

RUN L.RUN MS

MELSEC-A

4.2

(0.17)

106 (4.17)

RS-232-C

37.5 (1.48)

Unit : mm (inch)

APP − 1

Page 93

APPENDICES

130 (5.12)

34.5 (1.36)

1.2 A1SJ71DN91

1SJ71DN91

MELSEC-A

RUN L.RUN MS

DeviceNet

6.5

(0.26)

RS-232-C

93.6 (3.69)

Unit : mm (inch)

APP − 2

Page 94

APPENDICES

APPENDIX 2 Parameter Setting Sheet

MELSEC-A

Item Setting Range

Host station number (host station MAC ID)

Baud rate 1 to 3 01D5H

Station number of th station

Connection type of th slave station

Number of byte module points in th slave station

Number of word module points in th slave station

Number of doubleword module points in th slave station

Expected packet rate for th slave station

th Slave Station Watchdog Timeout Actions

th Slave Station Production Inhibit Time

0000H to 003FH (0 to 63)

Upper byte: 0001H or 0080H

Lower byte: 0000H to 003FH (0 to 63)

0001H, 0002H, 0004H, 0008H

Upper byte: Number of output byte modules

Lower byte: Number of input byte modules

Upper word: Number of output word modules

Lower word: Number of input word modules

Upper double-word: Number of output double-word modules

Lower double-word: Number of input double-word modules

Communication watchdog timer value for slave station (ms)

0000H, 0001H, 0002H, 0003H

Slave station minimum send interval (ms)

Buffer Memory

01D4H Station numer of DN91.

01D8H + ( -1) x 8

01D9H + ( -1) x 8

01DAH + ( -1)x 8 Units: Bytes (for both)

01DBH + ( -1) x 8 Units: Words (for both)

01DCH + ( -1)x 8 Units: Double-words (for both)

01DDH + ( -1) x 8

01DEH + ( -1) x 8

01DFH + ( -1) x 8

Address

Comments

1: 500kbaud 2: 250kbaud 3: 125kbaud

0001H: Actively communicating station 0080H: Reserved station

Station number of nth slave station Connection type for I/O communication

0001H: Polling 0002H: Bit strobe 0004H: Change of state 0008H: Cyclic

Set the communication watchdog timer value for the slave station. Sets the slave station communication watchdog timer. If the communication between the master station and the first slave station ceases during this set time, the first slave station takes the action designated in buffer memory address 01DEH. If set value = 0000H (default value), setting = 200 ms If set value ≠ 0000H, communication watchdog timer setting = (set value - 1) ms

Slave station watchdog timeout action Set value = 0000H (default value) Set value = 0001H: TIMEOUT Set value = 0002H: AUTO DELETE Set value = 0003H: AUTO RESET

The slave station minimum send interval sets the minimum time that the slave station can prepare the data to send. The master station sends polling requests and bit strobe requests to the slave station during this interval. If set value = 0000H (default value), setting = 20 ms If set value ≠ 0000H, minimum send interval = (set value - 1) ms

Notes:1) = 1 to 63

2) Copy this sheet for use when setting the parameters.

Set

Value

APP − 3

Page 95

APPENDICES

APPENDIX 3 List of Communication Parameter with Each Maker’s Slave Station

Examples of parameter setting for communicating with each maker’s slave station are listed below. Contact each maker for inquires about the details of parameter setting.

MELSEC-A

Maker Name

Mitsubishi Electric Corporation

Rockwell Automation Japan

OMRON Corporation

Type Name

A500 series

FR-A5ND

inverter DeviceNet option

Flex I/O

1794ADN

communicati on adapter

1794-IB16

Flex I/O input modules

Flex I/O

1794-OB16

output modules

DRT1-ID08

CompuBus/D 8 points input

CompuBus/D

DRT1-ID16

16 points input

CompuBus/D

DRT1-OD08

8 points output

CompuBus/D

DRT1-OD16

16 points output

Set Value(in brackets set value when parameters are set with a sequence

program is indicated)

Number of

Double

Word

Modules

Expected

Packet

Rate

1000 ms

(K1001)

1000 ms

(K1001)

1000 ms

(K1001)

0 ms

(H0)

30 ms

(K31)

Watchdog

Timeout

Action

Timeout

(H1)

Timeout

(H1)

Production

Inhibit

Time

10 ms

(K11)

10 ms

(K11)

10 ms

(K11)

0 ms

(H0)

25 ms

(K26)

Connection

Type

Polling (H1)

Bit strobe (H2)

Change of state(H4)

Cyclic (H8)

Number of

Byte

Modules

Output Input Output Input Output Input

Number of

Word

Modules

04H 04H 00H 00H 00H 00H

00H 02H 00H 00H 00H 00H

- 02H 02H 00H 00H 00H 00H - - - - -

Polling (H1)/ Bit strobe

00H 01H 00H 00H 00H 00H

1000 ms

(K1001)

Timeout

(H1)

10 ms

(K11)

(H2) Polling

(H1)/ Bit strobe

00H 02H 00H 00H 00H 00H

1000 ms

(K1001)

Timeout

(H1)

10 ms

(K11)

(H2)

Polling (H1)

01H 00H 00H 00H 00H 00H

02H 00H 00H 00H 00H 00H

1000 ms

(K1001)

1000 ms

(K1001)

Timeout

(H1)

Timeout

(H1)

10 ms

(K11)

10 ms

(K11)

Remark

Message

UCMM

Yes 3

No -

Group

APP − 4

Mitsubishi Electric A1SJ71DN91, AJ71DN91 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

REVISIONS

•• SAFETY PRECAUTIONS ••

INTRODUCTION

CONTENTS

1. OUTLINE

1.1 Features

1.2 Communication Outline

1.2.1 Network configuration

1.2.2 Outline of parameter settings

1.2.3 Outline of DN91 - slave station communication

2. SYSTEM CONFIGURATION

2.1 Overall Configuration

2.1.1 A typical system configuration that connects with a trunk line

2.1.2 A typical system configuration that connects with a drop line

2.1.3 System configuration with a DeviceNet master unit

2.2 Applicable Systems

2.2.1 Mountable CPUs and number of units

2.2.2 Important points about the system configuration

2.2.3 Operating environment of the configuration software (parameter setting tool)

2.3 Products Connectable to a Slave Station

3. SPECIFICATIONS

3.1 General Specifications

3.2 Performance Specifications

3.2.1 Maximum transfer distance of a trunk line that contains both thick and thin cables

3.3 PLC CPU I/O Signals

3.3.1 Table of I/O signals

3.3.2 I/O signal details

3.4 Buffer Memory

3.4.1 Buffer memory table

3.4.2 Details of the buffer memory

4. FUNCTIONS

4.1 I/O Communication Functions

4.2 Message Communication Functions

4.2.1 Get attribute

4.2.2 Set attribute

4.2.3 Read communication error information

5. SETTINGS AND PROCEDURES BEFORE OPERATION

5.1 Settings and Procedures

5.1.1 DN91 start-up procedure when setting parameters with a sequence program

5.1.2 DN91 start-up when setting parameters with the configuration software

5.2 Mounting and Installation

5.2.1 Handling instructions

5.2.2 Installation environment

5.3 Nomenclature

5.4 LED Displays and Indicator Descriptions

5.5 Connecting Communication Cable to DN91

5.6 Instructions for Connecting the Network Power Supply

5.6.1 Network power supply unit installation position

5.6.2 Calculating network power supply unit installation position and current capacity

6. PARAMETER SETTINGS

6.1 Settings Parameter

6.2 Important Points about the Parameter Settings

6.3 Setting with a Sequence Program

6.4 Setting Parameters with the Configuration Software (Parameter Setting Tool)

6.4.1 Setting configuration

6.4.2 Setting master parameters

6.4.3 Setting bus parameters

6.4.4 Set the device (slave station) parameters

7. PROGRAMMING

7.1 Important Points about Programming

7.2 System Configuration

7.3 Setting Parameters with a Sequence Program

7.4 I/O Communication with Slave Stations

7.4.1 Reading slave station I/O data

7.4.2 Writing slave station I/O data

7.5 Message Communication

7.5.1 Message communication - reading

7.5.2 Message communication - writing

7.6 Acquiring Error Information

8. TROUBLESHOOTING

8.1 Troubleshooting Tables

8.1.1 Troubleshooting by Symptom Type

8.1.2 Problems due to incorrect parameter settings

8.2 Troubleshooting Using LED Indications

8.2.1 Errors caused by the master unit

8.2.2 Errors caused by incorrect parameter settings or abnormal network