CS1 / CJ1 DeviceNet Units Operation Manual

CS1 / CJ1 DeviceNet Units Operation Manual

Cat. No. W380-E1-07

SYSMAC CS/CJ Series

CS Series: CS1W-DRM21(-V1)

CJ Series: CJ1W-DRM21

DeviceNet Units

OPERATION MANUAL

CS-series DeviceNet Unit: CS1W-DRM21(-V1)

CJ-series DeviceNet Unit: CJ1W-DRM21

Operation Manual

Revised March 2008

iv

Notice:

OMRON products are manufactured for use according to proper procedures by a qualified operator and only for the purposes described in this manual.

The following conventions are used to indicate and classify precautions in this manual. Always heed the information provided with them. Failure to heed precautions can result in injury to people or damage to property.

!DANGER

Indicates an imminently hazardous situation which, if not avoided, will result in death or serious injury. Additionally, there may be severe property damage.

!WARNING

Indicates a potentially hazardous situation which, if not avoided, could result in death or serious injury. Additionally, there may be severe property damage.

!Caution

Indicates a potentially hazardous situation which, if not avoided, may result in minor or moderate injury, or property damage.

OMRON Product References

All OMRON products are capitalized in this manual. The word “Unit” is also capitalized when it refers to an OMRON product, regardless of whether or not it appears in the proper name of the product.

The abbreviation “Ch,” which appears in some displays and on some OMRON products, often means

“word” and is abbreviated “Wd” in documentation in this sense.

The abbreviation “PLC” means Programmable Controller. “PC” is used, however, in some Programming Device displays to mean Programmable Controller.

Visual Aids

The following headings appear in the left column of the manual to help you locate different types of information.

Note

Indicates information of particular interest for efficient and convenient operation of the product.

Reference

Indicates supplementary information on related topics that may be of interest to the user.

1,2,3...

1.

Indicates lists of one sort or another, such as procedures, checklists, etc.

v

Trademarks and Copyrights

DeviceNet is a registered trademark of the Open DeviceNet Vendor Association, Inc.

Windows, Windows 95, Windows 98, Windows Me, Windows NT, and Windows 2000 are registered trademarks of the Microsoft Corporation.

Other product names and company names in this manual are trademarks or registered trademarks of their respective companies.

The copyright of the DeviceNet Unit belongs to OMRON Corporation.

OMRON, 2000

All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form, or by any means, mechanical, electronic, photocopying, recording, or otherwise, without the prior written permission of

OMRON.

No patent liability is assumed with respect to the use of the information contained herein. Moreover, because OMRON is constantly striving to improve its high-quality products, the information contained in this manual is subject to change without notice. Every precaution has been taken in the preparation of this manual. Nevertheless, OMRON assumes no responsibility for errors or omissions. Neither is any liability assumed for damages resulting from the use of the information contained in this publication.

vi

TABLE OF CONTENTS

PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4

5

6

2

3

General Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Safety Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Operating Environment Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Application Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Conformance to EC Directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 1

Features and System Configuration . . . . . . . . . . . . . . . .

1-1 Overview of DeviceNet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-2

1-3

1-4

1-5

1-6

1-7

DeviceNet Unit Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Comparison with Previous Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Outline of the Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Basic Operating Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

List of Usage Methods by Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 2

Nomenclature and Installation . . . . . . . . . . . . . . . . . . . .

2-1 Nomenclature and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-2 Installing the DeviceNet Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 3

Allocated CIO and DM Words . . . . . . . . . . . . . . . . . . . .

3-1 Overview of Word Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-2

3-3

Allocated CIO Area Words . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Allocated DM Area Words . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 4

Remote I/O Master Communications . . . . . . . . . . . . . . .

4-1 Master Remote I/O Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-2

4-3

4-4

4-5

4-6

4-7

Scan List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fixed Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

User-set Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Starting and Stopping Remote I/O Communications . . . . . . . . . . . . . . . . . . . . . . .

Example of Ladder Programming for Remote I/O Communications . . . . . . . . . . .

Errors that May Occur in Remote I/O Communications . . . . . . . . . . . . . . . . . . . .

xv

xvi xvi xvi

xvii

xviii

xx

49

50

55

61

62

64

84

19

26

33

37

40

46

1

2

95

96

103

105

111

120

120

122

vii

TABLE OF CONTENTS

SECTION 5

Remote I/O Slave Communications . . . . . . . . . . . . . . . . . 125

5-1 Slave Remote I/O Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

5-2

5-3

Fixed Allocations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

User-set Allocations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

129

130

SECTION 6

Message Communications . . . . . . . . . . . . . . . . . . . . . . . . 137

6-1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

6-2

6-3

6-4

6-5

FINS Commands and Responses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Using FINS Message Communications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Sending Explicit Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Receiving Explicit Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

145

149

161

168

SECTION 7

Other Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

7-1 Connecting to the CX-Programmer via the DeviceNet . . . . . . . . . . . . . . . . . . . . . 182

7-2

7-3

Memory Card Backup Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Simple Backup Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

186

189

SECTION 8

Communications Timing . . . . . . . . . . . . . . . . . . . . . . . . . 193

8-1 Remote I/O Communications Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

8-2 Message Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

SECTION 9

Troubleshooting and Maintenance . . . . . . . . . . . . . . . . . 205

9-1

9-2

Troubleshooting with the DeviceNet Unit Indicators . . . . . . . . . . . . . . . . . . . . . .

Error Log Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

206

224

9-3

9-4

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Maintenance and Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

228

231

Appendices

A Allocation Differences from C200H DeviceNet Master Units . . . . . . . . . . . . . . .

D

E

B

C

DeviceNet Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

FINS Commands and Responses for DeviceNet Units . . . . . . . . . . . . . . . . . . . .

Multi-vendor Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DeviceNet Explicit Message Send Command for Other Manufacturer Nodes . .

235

241

247

253

263

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

viii

About this Manual:

This manual describes the installation and operation of CS1W-DRM21(-V1) (see note) DeviceNet Unit for SYSMAC CJ-series PLCs and the CJ1W-DRM21 DeviceNet Unit for SYSMAC CJ-series PLCs, and includes the sections described below.

Note

In this manual, both the CS1W-DRM21 and the CS1W-DRM21-V1 are indicated by the following notation: CS1W-DRM21(-V1)

Please read this manual and all manuals for related products carefully and be sure you understand the information provided before attempting to install and operate the DeviceNet Unit. Be sure to read the precautions provided in the following section.

Section 1

provides an overview of the DeviceNet network, including features, specifications, and system.

Section 2

describes the nomenclature and installation of the DeviceNet Unit.

Section 3

describes the words allocated to the DeviceNet Unit in the CIO Area and DM Area. These words both enable controlling the DeviceNet Unit and accessing Unit and network status.

Section 4

describes the remote I/O communications performed as a master by the DeviceNet Unit.

Section 5

describes the remote I/O communications performed as a slave by the DeviceNet Unit.

Section 6

describes message communications using FINS commands sent from the ladder program in the CPU Unit of the PLC.

Section 7

describes connecting to CX-Programmer via the DeviceNet and the Memory Card backup function.

Section 8

describes the time required for remote I/O communications and message communications.

Section 9

describes error processing, periodic maintenance, and troubleshooting procedures needed to keep the DeviceNet network operating properly. We recommend reading through the error processing procedures before operation so that operating errors can be identified and corrected more quickly.

The Appendices provide information on allocation differences with C200H-series DeviceNet Units,

DeviceNet connections, remote programming and monitoring, Memory Card backups, FINS commands and responses, sending DeviceNet explicit message to Non-OMRON nodes, and multi-vendor applications.

The following manuals provide information on the DeviceNet and OMRON DeviceNet products.

Manual

CS/CJ-series DeviceNet

Unit Operation Manual

(This manual)

DeviceNet

Operation Manual

Products

CS1W-DRM21(-V1) and CJ1W-DRM21

DeviceNet Units

CVM1-DRM21-V1 DeviceNet Master Unit

C200HW-DRM21-V1 DeviceNet Master Unit

CQM1-DRT21 I/O Link Unit

DRT1-series DeviceNet Slaves

GT1-series DeviceNet Slaves

Contents

Information on CS/CJseries DeviceNet Units.

Information on C200Hseries, CVM1, and CVseries DeviceNet Units, as well as general DeviceNet communications specifications and wiring methods.

Information on using the

Configurator.

Cat. No.

W380

W267

W382

DeviceNet Configurator

Ver. 2.

@

Operation Manual

DRT2 Series DeviceNet

Slaves

Operation Manual

DeviceNet Slaves Operation Manual

WS02-CFDC1-E DeviceNet Configurator

3G8F5-DRM21 ISA Board

3G8E2-DRM21 PCMCIA Board

DRT2-ID/OD/MD32SL(H)(-1)

DRT2-MD16S

DRT2 Series

C200HW-DRT21

CQM1-DRT21

DRT1 Series

Information on DRT2-series

DeviceNet Slaves.

W404

Information on DeviceNet

Slaves.

W347

ix

About this Manual, Continued

Manual

DeviceNet MULTIPLE I/O

TERMINAL Operation

Manual

DeviceNet Master Units

Operation Manual

DRT1-COM

GT1 Series

Products

C200HW-DRM21-V1

CVM1-DRM21-V1

SYSMAC CS/CJ/NSJ

Series Communications

Commands Reference

Manual

CX-Programmer

Operation Manual

CS1G/H-CPU @@ H

CS1G/H-CPU @@ -EV1

CS1D-CPU @@ H

CS1D-CPU @@ S

CS1W-SCU @@ -V1

CS1W-SCB @@ -V1

CJ1G/H-CPU @@ H

CJ1G-CPU @@ P

CJ1G-CPU @@

CJ1M-CPU @@

CJ1W-SCU @@ -V1

CP1H-X @@@@ @

CP1H-XA @@@@ @

CP1H-Y @@@@ @

NSJ @ @@@@ (B)-G5D

NSJ @ @@@@ (B)-M3D

WS02-CXPC1-EV70

Contents

Information on MULTIPLE

I/O TERMINALs, one type of DeviceNet slave.

Information on C200H and

CVM1/CV-series DeviceNet

Master Units.

Describes the communications commands used with

CS-series, CJ-series, and

CP-series PLCs and NSJ

Controllers.

Cat. No.

W348

W379

W342

Information on setting and monitoring networks, such as the use of routing tables.

W446

x

!WARNING

Failure to read and understand the information provided in this manual may result in personal injury or death, damage to the product, or product failure. Please read each section in its entirety and be sure you understand the information provided in the section and related sections before attempting any of the procedures or operations given.

Read and Understand this Manual

Please read and understand this manual before using the product. Please consult your OMRON representative if you have any questions or comments.

Warranty and Limitations of Liability

WARRANTY

OMRON's exclusive warranty is that the products are free from defects in materials and workmanship for a period of one year (or other period if specified) from date of sale by OMRON.

OMRON MAKES NO WARRANTY OR REPRESENTATION, EXPRESS OR IMPLIED, REGARDING NON-

INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR PARTICULAR PURPOSE OF THE

PRODUCTS. ANY BUYER OR USER ACKNOWLEDGES THAT THE BUYER OR USER ALONE HAS

DETERMINED THAT THE PRODUCTS WILL SUITABLY MEET THE REQUIREMENTS OF THEIR

INTENDED USE. OMRON DISCLAIMS ALL OTHER WARRANTIES, EXPRESS OR IMPLIED.

LIMITATIONS OF LIABILITY

OMRON SHALL NOT BE RESPONSIBLE FOR SPECIAL, INDIRECT, OR CONSEQUENTIAL DAMAGES,

LOSS OF PROFITS OR COMMERCIAL LOSS IN ANY WAY CONNECTED WITH THE PRODUCTS,

WHETHER SUCH CLAIM IS BASED ON CONTRACT, WARRANTY, NEGLIGENCE, OR STRICT

LIABILITY.

In no event shall the responsibility of OMRON for any act exceed the individual price of the product on which liability is asserted.

IN NO EVENT SHALL OMRON BE RESPONSIBLE FOR WARRANTY, REPAIR, OR OTHER CLAIMS

REGARDING THE PRODUCTS UNLESS OMRON'S ANALYSIS CONFIRMS THAT THE PRODUCTS

WERE PROPERLY HANDLED, STORED, INSTALLED, AND MAINTAINED AND NOT SUBJECT TO

CONTAMINATION, ABUSE, MISUSE, OR INAPPROPRIATE MODIFICATION OR REPAIR.

xi

Application Considerations

SUITABILITY FOR USE

OMRON shall not be responsible for conformity with any standards, codes, or regulations that apply to the combination of products in the customer's application or use of the products.

At the customer's request, OMRON will provide applicable third party certification documents identifying ratings and limitations of use that apply to the products. This information by itself is not sufficient for a complete determination of the suitability of the products in combination with the end product, machine, system, or other application or use.

The following are some examples of applications for which particular attention must be given. This is not intended to be an exhaustive list of all possible uses of the products, nor is it intended to imply that the uses listed may be suitable for the products:

• Outdoor use, uses involving potential chemical contamination or electrical interference, or conditions or uses not described in this manual.

• Nuclear energy control systems, combustion systems, railroad systems, aviation systems, medical equipment, amusement machines, vehicles, safety equipment, and installations subject to separate industry or government regulations.

• Systems, machines, and equipment that could present a risk to life or property.

Please know and observe all prohibitions of use applicable to the products.

NEVER USE THE PRODUCTS FOR AN APPLICATION INVOLVING SERIOUS RISK TO LIFE OR

PROPERTY WITHOUT ENSURING THAT THE SYSTEM AS A WHOLE HAS BEEN DESIGNED TO

ADDRESS THE RISKS, AND THAT THE OMRON PRODUCTS ARE PROPERLY RATED AND INSTALLED

FOR THE INTENDED USE WITHIN THE OVERALL EQUIPMENT OR SYSTEM.

PROGRAMMABLE PRODUCTS

OMRON shall not be responsible for the user's programming of a programmable product, or any consequence thereof.

xii

Disclaimers

CHANGE IN SPECIFICATIONS

Product specifications and accessories may be changed at any time based on improvements and other reasons.

It is our practice to change model numbers when published ratings or features are changed, or when significant construction changes are made. However, some specifications of the products may be changed without any notice. When in doubt, special model numbers may be assigned to fix or establish key specifications for your application on your request. Please consult with your OMRON representative at any time to confirm actual specifications of purchased products.

DIMENSIONS AND WEIGHTS

Dimensions and weights are nominal and are not to be used for manufacturing purposes, even when tolerances are shown.

PERFORMANCE DATA

Performance data given in this manual is provided as a guide for the user in determining suitability and does not constitute a warranty. It may represent the result of OMRON's test conditions, and the users must correlate it to actual application requirements. Actual performance is subject to the OMRON Warranty and

Limitations of Liability.

ERRORS AND OMISSIONS

The information in this manual has been carefully checked and is believed to be accurate; however, no responsibility is assumed for clerical, typographical, or proofreading errors, or omissions.

xiii

xiv

PRECAUTIONS

This section provides general precautions for using the DeviceNet Unit and related devices.

The information contained in this section is important for the safe and reliable application of the DeviceNet Unit and Programmable Controller (PLC) You must read this section and understand the information contained before attempting to set up or operate a DeviceNet Unit as part of a PLC.

3

4

5

1

2

6

Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

General Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Safety Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Operating Environment Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Application Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Conformance to EC Directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-1 Applicable Directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-2 Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-3 Conformance to EC Directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xvi xvi xvi

xvii

xviii

xx xx xx xx

xv

Intended Audience

1

1

Intended Audience

This manual is intended for the following personnel, who must also have knowledge of electrical systems (an electrical engineer or the equivalent).

• Personnel in charge of installing FA systems.

• Personnel in charge of designing FA systems.

• Personnel in charge of managing FA systems and facilities.

2 General Precautions

The user must operate the product according to the performance specifications described in the operation manuals.

Before using the product under conditions which are not described in the manual or applying the product to nuclear control systems, railroad systems, aviation systems, vehicles, combustion systems, medical equipment, amusement machines, safety equipment, and other systems, machines, and equipment that may have a serious influence on lives and property if used improperly, consult your OMRON representative.

Make sure that the ratings and performance characteristics of the product are sufficient for the systems, machines, and equipment, and be sure to provide the systems, machines, and equipment with double safety mechanisms.

This manual provides information for installing and operating the DeviceNet

Unit. Be sure to read this manual before operation and keep this manual close at hand for reference during operation.

3

!WARNING

It is extremely important that a PLC and all PLC Units be used for the specified purpose and under the specified conditions, especially in applications that can directly or indirectly affect human life. You must consult with your OMRON representative before applying a PLC System to the above mentioned applications.

Safety Precautions

!WARNING

Never attempt to disassemble a Unit or touch the inside of Unit while power is being supplied. Doing so may result in serious electrical shock or electrocution.

!WARNING

Provide safety measures in external circuits, i.e., not in the Programmable

Controller (CPU Unit including associated Units; referred to as “PLC”), in order to ensure safety in the system if an abnormality occurs due to malfunction of the PLC or another external factor affecting the PLC operation. Not doing so may result in serious accidents.

• Emergency stop circuits, interlock circuits, limit circuits, and similar safety measures must be provided in external control circuits.

• The PLC will turn OFF all outputs when its self-diagnosis function detects any error or when a severe failure alarm (FALS) instruction is executed.

As a countermeasure for such errors, external safety measures must be provided to ensure safety in the system.

• The PLC outputs may remain ON or OFF due to deposition or burning of the output relays or destruction of the output transistors. As a counter-

xvi

Operating Environment Precautions

4

measure for such problems, external safety measures must be provided to ensure safety in the system.

• When the 24-VDC output (service power supply to the PLC) is overloaded or short-circuited, the voltage may drop and result in the outputs being turned OFF. As a countermeasure for such problems, external safety measures must be provided to ensure safety in the system.

!WARNING

The CPU Unit refreshes I/O even when the program is stopped (i.e., even in

PROGRAM mode). Confirm safety thoroughly in advance before changing the status of any part of memory allocated to I/O Units, Special I/O Units, or CPU

Bus Units. Any changes to the data allocated to any Unit may result in unexpected operation of the loads connected to the Unit. Any of the following operation may result in changes to memory status.

• Transferring I/O memory data to the CPU Unit from a Programming

Device.

• Changing present values in memory from a Programming Device.

• Force-setting/-resetting bits from a Programming Device.

• Transferring I/O memory files from a Memory Card or EM file memory to the CPU Unit.

• Transferring I/O memory from a host computer or from another PLC on a network.

!Caution

Execute online edit only after confirming that no adverse effects will be caused by extending the cycle time. Otherwise, the input signals may not be readable.

4

!Caution

Confirm safety at the destination node before transferring a program to another node or changing contents of the I/O memory area. Doing either of these without confirming safety may result in injury.

Operating Environment Precautions

Do not install the Unit in any of the following locations.

• Locations subject to direct sunlight.

• Locations subject to temperatures or humidities outside the range specified in the specifications.

• Locations subject to condensation as the result of severe changes in temperature.

• Locations subject to corrosive or flammable gases.

• Locations subject to dust (especially iron dust) or salt.

• Locations subject to exposure to water, oil, or chemicals.

• Locations subject to shock or vibration.

Provide proper shielding when installing in the following locations:

• Locations subject to static electricity or other sources of noise.

• Locations subject to strong electromagnetic fields.

• Locations subject to possible exposure to radiation.

• Locations near to power supply lines.

xvii

Application Precautions

5

!Caution

The operating environment of the PLC System can have a large effect on the longevity and reliability of the system. Improper operating environments can lead to malfunction, failure, and other unforeseeable problems with the PLC

System. Be sure that the operating environment is within the specified conditions at installation and remains within the specified conditions during the life of the system.

5 Application Precautions

Observe the following precautions when using the DeviceNet Unit.

!WARNING

Failure to abide by the following precautions could lead to serious or possibly fatal injury. Always heed these precautions.

• Always connect to a class-3 ground (100

or less) when installing the

Units.

!Caution

Failure to abide by the following precautions could lead to faulty operation or the PLC or the system or could damage the PLC or PLC Units. Always heed these precautions.

• Install double safety mechanisms to ensure safety against incorrect signals that may be produced by broken signal lines or momentary power interruptions.

• Enable the scan list to before operating the system.

• When adding a new node to the network, make sure that the baud rate is the same as other nodes.

• Use specified communications cables.

• Do not extend connection distances beyond the ranges given in the specifications.

• Always turn OFF the power supply to the personal computer, Slaves, and

Communications Units before attempting any of the following.

• Mounting or dismounting the DeviceNet Unit, Power Supply Units, I/O

Units, CPU Units, or any other Units.

• Assembling a Unit.

• Setting DIP switches or rotary switches.

• Connecting or wiring the cables.

• Connecting or disconnecting connectors.

• Be sure that the terminal blocks, connectors, Memory Units, expansion cables, and other items with locking devices are properly locked into place. Improper locking may result in malfunction.

• Be sure that all the mounting screws, terminal screws, Unit mounting screws, and cable connector screws are tightened to the torque specified in the relevant manuals. Incorrect tightening torque may result in malfunction.

• Leave the label attached to the Unit when wiring. Removing the label may result in malfunction if foreign matter enters the Unit.

• Remove the label after the completion of wiring to ensure proper heat dissipation. Leaving the label attached may result in malfunction.

• Always use the power supply voltage specified in this manual.

xviii

Application Precautions

5

• Double-check all the wiring and connection of terminal blocks and connectors before mounting the Units.

• Use crimp terminals for wiring. Do not connect bare stranded wires directly to terminals.

• Observe the following precautions when wiring the communications cable.

• Separate the communications cables from the power lines or high-tension lines.

• Do not bend the communications cables.

• Do not pull on the communications cables.

• Do not place heavy objects on top of the communications cables.

• Be sure to wire communications cable inside ducts.

• Use appropriate communications cables.

• Take appropriate measures to ensure that the specified power with the rated voltage and frequency is supplied in places where the power supply is unstable. An incorrect power supply may result in malfunction.

• Install external breakers and take other safety measures against short-circuiting in external wiring. Insufficient safety measures against short-circuiting may result in burning.

• Double-check all the wiring and switch settings before turning ON the power supply.

• Check the user program for proper execution before actually running it on the Unit. Not checking the program may result in an unexpected operation.

• Confirm that no adverse effect will occur in the system before attempting any of the following. Not doing so may result in an unexpected operation.

• Changing the operating mode of the PLC.

• Force-setting/force-resetting any bit in memory.

• Changing the present value of any word or any set value in memory.

• After replacing Units, resume operation only after transferring to the new

CPU Unit and/or Special I/O Units the contents of the DM Area, HR Area, and other data required for resuming operation. Not doing so may result in an unexpected operation.

• When transporting or storing the product, cover the PCBs with electrically conductive materials to prevent LSIs and ICs from being damaged by static electricity, and also keep the product within the specified storage temperature range.

• When transporting the Unit, use special packing boxes and protect it from being exposed to excessive vibration or impacts during transportation.

• Do not attempt to disassemble, repair, or modify any Units.

xix

Conformance to EC Directives

6

6-1

6-2

6-3

6

Conformance to EC Directives

Applicable Directives

• EMC Directives

Concepts

EMC Directives

OMRON devices that comply with EC Directives also conform to the related

EMC standards so that they can be more easily built into other devices or machines. The actual products have been checked for conformity to EMC standards. (See the following note.) Whether the products conform to the standards in the system used by the customer, however, must be checked by the customer.

EMC-related performance of the OMRON devices that comply with EC Directives will vary depending on the configuration, wiring, and other conditions of the equipment or control panel in which the OMRON devices are installed.

The customer must, therefore, perform final checks to confirm that devices and the overall machine conform to EMC standards.

Note

Applicable EMS (Electromagnetic Susceptibility) and EMI (Electromagnetic

Interference standards in the EMC (Electromagnetic Compatibility) standards are as follows:

Unit

CS1W-DRM21(-V1)

CJ1W-DRM21

EMS

EN61000-6-2

EMI

EN61000-6-4

Conformance to EC Directives

DeviceNet products that meet EC directives must be installed as follows:

1,2,3...

1,2,3...

.

1. DeviceNet Units are designed for installation inside control panels. All DeviceNet Units must be installed within control panels.

2. Used reinforced insulation or double insulation for the DC power supplies used for the communications power supply, internal circuit power supply, and the I/O power supplies.

3. DeviceNet products that meet EC directives also meet the common emission standard (EN61000-6-4). When DeviceNet products are built into equipment, however, the measure necessary to ensure that the standard is met will vary with the overall configuration of the control panel, the other devices connected to the control panel, and other conditions. You must therefore confirm that EC directives are met for the overall machine or device, particularly for the radiated emission requirement (10 m).

The following examples show means of reducing noise.

1. Noise from the communications cable can be reduced by installing a ferrite core on the communications cable within 10 cm of the DeviceNet Unit.

xx

Conformance to EC Directives

Ferrite Core (Data Line Filter): 0443-164151 (manufactured by

Fair-Rite Products Co., Ltd.)

Impedance specifications

25 MHZ:

100 MHZ:

156

250

30 mm

33 mm

13 mm

29 mm

6

2. Wire the control panel with as thick and short electric lines as possible and ground to 100

min.

3. Keep DeviceNet communications cables as short as possible and ground to 100 Ω min.

xxi

Conformance to EC Directives

6 xxii

SECTION 1

Features and System Configuration

This section provides an overview of the DeviceNet network, including features, specifications, and system configurations.

1-1

1-2

1-3

1-4

1-5

1-6

1-7

Overview of DeviceNet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-1-1

1-1-2

Overall System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Applicable Units and DeviceNet Functions . . . . . . . . . . . . . . . . . . .

1-1-3

1-1-4

Masters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Types of Slave. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-1-5 DeviceNet Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DeviceNet Unit Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-3-1 DeviceNet Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-3-2 Comparison between CS1W-DRM21(-V1) and CJ1W-DRM21 . . .

Comparison with Previous Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Outline of the Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-5-1 Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-5-2 Configurator Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Basic Operating Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-6-1

1-6-2

1-6-3

1-6-4

Network Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Hardware Preparations for Communications . . . . . . . . . . . . . . . . . .

Creating Routing Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Procedures Prior to Starting Communications . . . . . . . . . . . . . . . . .

List of Usage Methods by Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

37

37

38

40

26

26

32

33

40

40

41

42

46

19

19

9

9

2

3

6

1

Overview of DeviceNet

1-1

Section 1-1

Overview of DeviceNet

DeviceNet is a multi-bit, multi-vendor network that combines controls and data on a machine/line-control level and that conforms to DeviceNet open field network specifications.

Three types of communications are supported: 1) Remote I/O master communications that automatically transfer I/O between slaves and the CPU Unit to which a DeviceNet Unit is mounted without any special programming in the

CPU Unit, 2) Remote I/O slave communications that automatically transfer I/O between the Master and the CPU Unit to which a DeviceNet Unit is mounted, and 3) Message communications that read/write messages, control operation, or perform other functions for other CPU Units to which a DeviceNet Unit is mounted and slaves. Message communications are achieved by executing specific instructions (SEND (192), RECV (193), and CMND (194)) from the program in the CPU Unit to which the DeviceNet Unit is mounted.

Remote I/O master communications

Fixed allocations

User-set allocations

DeviceNet functions

Remote I/O slave communications

Message communications

Fixed allocations

User-set allocations

Explicit message communications

FINS message communications

1,2,3...

The following functions are supported with a CS/CJ-series DeviceNet Unit.

1.

2.

3.

Without the Configurator Software Tool a) I/O area words can be flexibly allocated for remote I/O Master and

Slave communications. Three types of fixed allocations as well as user-set allocations through allocated DM Area words are possible.

b) More than one DeviceNet Unit can be mounted under a single PLC.

c) More than one DeviceNet Unit can be connected in a single network.

With the Configurator, remote I/O can be allocated in any order, i.e., not necessarily in the other of node addresses.

Note

The Configurator that is connected through a dedicated Board or

Card uses one node in the DeviceNet network. It does not use a node if it is connected by a serial line.

A CS/CJ-series DeviceNet Unit can function as either a master or slave in remote I/O communications. Both can be used simultaneously.

With a CS/CJ-series DeviceNet Unit, the DeviceNet network can be treated exactly like a Controller Link, Ethernet, or other network for message communications or remote programming and monitoring by a CX-Programmer.

2

Overview of DeviceNet

1-1-1 Overall System Configuration

DeviceNet Unit or

DeviceNet Master Unit

CS Series

CS1W-DRM21(-V1)

C200HZ/HX/HG/E/HS:

C200HW-DRM21-V1

CJ Series

CJ1W- DRM21

CVM1/CV Series:

CVM1-DRM21-V1

Photoelectric sensors, proximity sensors, limit switches, etc.

Photoelectric sensors, proximity sensors, limit switches, etc.

Input

Terminal

Section 1-1

Input Remote

Adapter (used with Input Block)

Photoelectric sensors or proximity sensors with connectors

Sensor

Terminal

DeviceNet

Configurator

(personal computer)

CQM1

I/O Link

Unit

Output

Terminal

Output Remote

Adapter (used with Output

Block)

Environment-resistant Terminal

(Inputs, outputs, or mixed I/O)

Solenoids, valves, etc.

Solenoids, valves, etc.

: T-branch Taps or multi-drop connections

Photoelectric sensors, proximity sensors, limit switches, etc.

Solenoids, valves, etc.

DeviceNet Unit or

DeviceNet Master Unit

(See note.)

C200H I/O Link Unit

Analog

Input

Terminal

Analog sensors, etc.

Analog

Output

Terminal

Temperature Input Terminal

RS-232C

Unit

Inputs Outputs Outputs Inputs

MULTIPLE I/O TERMINAL

Inverters, valves, etc.

Thermocouple, platinum resistance thermometer

Bar code readers, etc.

Note

The Configurator is required if more than one Master is connected in a single network when a CVM1-DRM21-V1 or C200HW-DRM21-V1 is used.

Master Features

DeviceNet Master Units and DeviceNet Units

Support remote I/O communications between OMRON PLCs (CS-series, CJseries, CVM1, CV-series, or C200HX/HG/HE/HS) and slaves.

Support message communications between OMRON PLCs, or between an

OMRON PLC and slaves and masters from other companies.

VME Master Boards

Supports remote I/O communications between a VME System and slaves.

3

Overview of DeviceNet

Configurator Features

Slave Features

Section 1-1

• Enables user-set allocations for remote I/O (choice of node address order,

2 area allocations, etc.).

• Enables serial connection to the Programming Device Port of a PLC.

• Enables user settings for DeviceNet remote I/O communications connections.

• Enables multiple Masters on a single PLC.

• Enables multiple Masters in a single network.

I/O Terminals

• Provide general-purpose I/O via terminal blocks (M3).

• Available in the following models:

• 8-point Transistor Input Terminal

• 16-point Transistor Input Terminal

• 8-point Transistor Output Terminal

• 16-point Transistor Output Terminal

Environment-resistant Terminals

• Improved I/O Terminals that conform to IP66 for spatter-, water-, and oilresistance.

• Available in the following models:

• 8-point Transistor Input Terminal

• 8-point Transistor Output Terminal

• 16-point Transistor I/O Terminal (8 inputs and 8 outputs)

Remote Adapters

• Used in combination with G70D and other I/O Blocks to handle relay outputs, power MOS FET Relay outputs, etc.

• Available in 16-point input and 16-point output models.

I/O Link Units

• More than one I/O Link Unit can be mounted to a CQM1 PLC.

• Link 16 inputs and 16 outputs between the PLC and the Master.

Sensor Terminals

• Accept inputs from photoelectric and proximity sensors with connectors.

• Available in 16-point input and 8-point input/8-point output models.

• Output signals can be used for sensor teaching and external diagnosis.

Analog Input Terminals

• Convert analog inputs to binary.

• Switchable between 2 and 4 input points using the DIP switch.

• Handle inputs of 0 to 5 V, 1 to 5 V, 0 to 10 V, –10 to +10 V, 0 to 20 mA, or

4 to 20 mA.

• Available in models with a resolution of either 1/6,000 or 1/3,000.

Analog Output Terminals

• Convert binary data to analog outputs.

• Provides outputs of 1 to 5 V, 0 to 10 V, –10 to +10 V, 0 to 20 mA, or 4 to

20mA.

4

Overview of DeviceNet

Section 1-1

• Available in models with a resolution of 1/6,000.

Temperature Input Terminals

• Temperature data is input as binary data for 4 inputs.

• Thermocouple and platinum resistance thermometer inputs are available.

C200H I/O Link Units

• Special I/O Slaves that mount to C200HX/HG/HE PLCs and read/write data from the Master to the specified words in the CPU Unit.

• Read and write areas specified for up to 512 bits each (32 words each).

• Any memory area words can be read or written using DeviceNet explicit messages.

RS-232C Units

• Special I/O Slaves that provide two RS-232C ports and control I/O from the Masters.

MULTIPLE I/O TERMINALs

• Multiple I/O Units can be combined under a Communications Unit and treated as a single Slave.

• Special I/O Units, such as Analog I/O Units, and High-speed Counter

Units are also available.

5

Overview of DeviceNet

1-1-2 Applicable Units and DeviceNet Functions

Remote I/O Masters

DeviceNet Unit (Master)

CPU Unit

Remote I/O communications

DeviceNet

Section 1-1

Slaves

Item

Max. No. of Slave nodes per

Master

Master

CS Series

CJ Series

CVM1, CV Series

CS Series,

C200HX/HG/HE

C200HS

CS Series Max. No. of control points per

Master

CJ Series

Model

CS1W-DRM21(-V1)

CJ1W-DRM21

CVM1-DRM21-V1

C200HW-DRM21-V1

CS1W-DRM21(-V1)

CJ1W-DRM21

Without Configurator

63 nodes

With Configurator

50 nodes 63 nodes

32 nodes

2,048 pts (64 input /64 output words) or

16,000 pts (500 input/

500 output words)

63 nodes

32,000 pts (500 words x 4 blocks)

CVM1, CV Series

CS Series,

C200HX/HG/HE

C200HS

CVM1-DRM21-V1

C200HW-DRM21-V1

2,048 pts (64 input/ 64 output words)

1,600 pts (50 input/50 output words)

6,400 (100 words x

4 blocks

Without messages:

4,800 pts

With messages:

1,600 pts

1,280 1,024 pts (32 input/32 output words)

100 input/100 output words Max. No. of I/O points per

Slave controllable by

Master

CS Series

CJ Series

CVM1, CV Series

CS Series,

C200HX/HG/HE

C200HS

CS Series Remote

I/O allocation areas

CJ Series

CS1W-DRM21(-V1)

CJ1W-DRM21

CVM1-DRM21-V1

C200HW-DRM21-V1

CS1W-DRM21(-V1)

CJ1W-DRM21

CVM1, CV Series

CS Series,

C200HX/HG/HE

C200HS

CVM1-DRM21-V1

C200HW-DRM21-V1

32 input/32 output words

CS/CJ DeviceNet words in CIO Area, and user-allocated words in CIO Area,

DM Area, and other areas.

DeviceNet Area

C200H DeviceNet words in CIO Area

(including dedicated words/ bits)

User-allocated words in CIO Area,

DM Area, and other areas.

User-allocated words in CIO Area,

DM Area, and other areas.

6

Overview of DeviceNet

Remote I/O Slaves (only Units Mounted in a PLC)

DeviceNet Unit (Master)

CPU Unit

Remote I/O communications

DeviceNet

Section 1-1

IN area OUT area

CPU Unit

DeviceNet Unit (Slave)

Slaves

IN area

OUT area

Item

Max. No. of I/O pts per Slave

CPU Unit to which a Slave is mounted

CS Series

Unit Model

CS1W-DRM21(-V1)

CJ Series CJ1W-DRM21

C200HW-DRT21

Without the

Configurator

With the

Configurator

32 pts (1 input/

1 output word) or

3,200 pts (100 input/100 output words)

4,800 pts

(100 input words x

2/100 output words x 1)

1,024 pts (32 input/32 output words)

Allocation areas in the CPU Unit to which this Slave is mounted

CS Series,

C200HX/HG/HE

CQM1H

CQM1 Series

CS Series

CJ Series

CS Series,

C200HX/HG/HE

CQM1H

CQM1 Series

CQM1-DRT21

CS1W-DRM21(-V1)

CJ1W-DRM21

C200HW-DRT21

CQM1-DRT21

32 pts (1 input/1 output word)

CIO, WR, DM, EM, HR

CIO, DM, EM, AR, LR, T/C

CIO

7

Overview of DeviceNet

Message Communications

Section 1-1

Master Master

8

RS-232C

Interface Unit

Master

Communications Instructions

Unit model Send Receive

SEND(192)

None

---

FINS commands

CMND(194) CS Series

CJ Series

CVM1, CV Series

CS Series,

C200HX/HG/HE

C200HS

CS1W-DRM21(-V1)

CJ1W-DRM21

CVM1-DRM21-V1

C200HW-DRM21-V1

Item

Max. No. of nodes per

Master for message communications using

FINS commands

Master model

CS Series

CJ Series

CVM1, CV Series

CS Series,

C200HX/HG/HE

SEND(192) RECV(193)

RECV(193)

None

CMND(194)

IOWR

Model

CS1W-DRM21(-V1)

CJ1W-DRM21

CVM1-DRM21-V1

C200HW-DRM21-V1

Capacity

62 nodes

(Node address 0 cannot be used in FINS communications.)

8 nodes

8 nodes

Max. No. of nodes per

Master for message communications using explicit messages

CS Series

CJ Series

CVM1, CV Series

CS Series, C200HX/

HG/HE

CS1W-DRM21(-V1)

CJ1W-DRM21

CVM1-DRM21-V1

C200HW-DRM21-V1

63 nodes

63 nodes

63 nodes

Max. message length CS Series

CJ Series

CS1W-DRM21(-V1)

CJ1W-DRM21

SEND(192): 267 words

RECV(193): 269 words

CMND(194): 542 bytes (starting with command code)

CVM1-DRM21-V1 SEND(192): 76 words CVM1, CV Series

CS Series,

C200HX/HG/HE

C200HW-DRM21-V1

CMND(194): 160 bytes

(starting with command code)

IOWR(223): 160 bytes (starting with command code)

Note

FINS message communications are supported between any two PLCs with a

CS/CJ-series DeviceNet Unit (CS1W-DRM21(-V1)/CJ1W-DRM21). They are not supported for PLCs with a C200H DeviceNet Master Unit (C200HW-

Overview of DeviceNet

Section 1-1

DRM21-V1) or a CVM1/CV-series DeviceNet Master Unit (CVM1-DRM21-

V1). Refer to

6-3 Using FINS Message Communications

for details.

Communications Software Switches and Communications Status

Dedicated words in the CPU Unit are allocated for DeviceNet communications software switches and status.

Master

Software switches

Status area

Control scan list registration/clearing, remote I/O communications start/stop, and other parameters

Enables monitoring communications errors, communications status of Masters, registered Slave data, normal Slave data, etc.

1-1-3

PLC

Masters

CS Series

CJ Series

CVM1/CV Series

CS Series

C200HX/HG/HE

C200HS

Model

CS1W-DRM21(-V1)

DeviceNet Unit

CJ1W-DRM21

CVM1-DRM21-V1

DeviceNet Master

Unit

C200HW-DRM21-V1

DeviceNet Master

Unit

Mountable position Master/Slave function

With

Configurator

Master and Slave 16

Maximum number of mountable units

Without

Configurator

CPU or Expansion CPU

Rack (Classified as CPU

Bus Units)

CPU Rack or Expansion

Rack (Classified as CPU

Bus Units)

CPU or Expansion CPU

Rack (Classified as CPU

Bus Units)

CPU Rack or Expansion

I/O Rack (Classified as

Special I/O Units)

Master only 16

16

10 or 16

10

1

1-1-4 Types of Slave

The following classifications are used for DeviceNet Slaves.

• General-purpose Slaves:

Slave with I/O functions for I/O that uses an ordinary connector connected to a communications cable.

• Environment-resistant Slaves:

Slave with I/O functions for I/O that uses a round, waterproof connector connected to a communications cable.

• Special Slaves:

Slave with functions not related to I/O (e.g., message communications) for

I/O that uses an ordinary connector connected to a communications cable.

• Analog Slaves:

Slave with I/O functions for analog values that uses an ordinary connector connected to a communications cable.

9

Overview of DeviceNet

Section 1-1

DRT1 Series

General-purpose Slaves (Communications Cable: Normal Square Connectors)

Name

Remote I/O Terminals with Transistors

Remote I/O Terminals with Transistors and

3-tier Terminal Block

Remote I/O Terminals with Transistors and

Connectors

Remote Adapters

Appearance I/O points

8 input points (NPN)

Model number

DRT1-ID08

8 input points (PNP) DRT1-ID08-1

16 input points (NPN) DRT1-ID16

16 input points (PNP) DRT1-ID16-1

8 output points (NPN) DRT1-OD08

8 output points (PNP) DRT1-OD08-1

16 output points

(NPN)

DRT1-OD16

16 output points

(PNP)

DRT1-OD16-1

16 input points (NPN) DRT1-ID16T

16 input points (PNP) DRT1-ID16T-1

16 input points (NPN) DRT1-ID16TA

16 input points (PNP) DRT1-ID16TA-1

16 output points

(NPN)

DRT1-OD16T

DRT1-OD16T-1 16 output points

(PNP)

16 output points

(NPN)

DRT1-OD16TA

DRT1-OD16TA-1 16 output points

(PNP)

8 input points+8 output points (NPN)

8 input points+8 output points (PNP)

8 input points+8 output points (NPN)

DRT1-MD16T

DRT1-MD16T-1

DRT1-MD16TA

8 input points+8 output points (PNP)

DRT1-MD16TA-1

32 input points (NPN) DRT1-ID32ML

32 input points (PNP) DRT1-ID32ML-1

32 output points

(NPN)

DRT1-OD32ML

32 output points

(PNP)

16 input points+16 output points (NPN)

DRT1-OD32ML-1

DRT1-MD32ML

16 input points+16 output points (PNP)

DRT1-MD32ML-1

16 input points (NPN) DRT1-ID16X

16 input points (PNP) DRT1-ID16X-1

16 output points

(NPN)

DRT1-OD16X

16 output points

(PNP)

DRT1-OD16X-1

---

---

Remarks

Simple wiring (not necessary to tighten multiple wires together and wiring locations are easy to understand)

The [email protected] D16TA(-1) does not need a separate power supply for internal circuits

(uses the communications power supply).

Compact (35 x 60 x 80 mm

(W x D x H))

Connects to a Relay Terminal through a MIL cable.

Does not need a separate power supply for internal circuits (uses the communications power supply).

Compact (85 x 50 x 40 mm

(W x D x H))

Connects to a G70D Relay terminal and can be used for a relay output or a power MOS-

FET relay output.

10

Overview of DeviceNet

Name

Sensor Terminals

Appearance

CQM1 I/O Link Unit

Section 1-1

I/O points Model number

16 input points (NPN) DRT1-HD16S

Remarks

Connected to photoelectric and proximity sensors with connectors

8 input/8 output points (PNP)

DRT1-ND16S

16 internal inputs/

16 internal outputs

(between CQM1 and

Master)

CQM1-DRT21 Remote I/O communications between PLCs

CPM2A/CPM1A

I/O Link Unit

32 internal inputs/

32 internal outputs

(between CPM2A/

CPM1A and Master)

CPM1A-DRT21 Remote I/O communications between PLCs

Note

For details on Slaves, refer to the

DeviceNet (CompoBus/D) Slaves Operation

Manual

(W347).

11

Overview of DeviceNet

Section 1-1

Waterproof and Environment-resistant Slaves (Communications Cable: Round Connectors)

Name

Waterproof Terminals

Environment-resistant Terminals

B7AC Interface Terminal

Appearance I/O points

4 input points (NPN)

4 input points (PNP)

8 input points (NPN)

Model number

DRT1-ID04CL

DRT1-ID04CL-1

DRT1-ID08CL

8 input points (PNP) DRT1-ID08CL-1

4 output points (NPN) DRT1-OD04CL

4 output points (PNP) DRT1-OD04CL-1

8 output points (NPN) DRT1-OD08CL

8 output points (PNP) DRT1-OD08CL-1

8 input points (NPN) DRT1-ID08C

8 output points (NPN) DRT1-OD08C

16 input points (NPN) DRT1-HD16C

16 input points (PNP) DRT1-HD16C-1

16 output points

(NPN)

DRT1-WD16C

DRT1-WD16C-1 16 output points

(PNP)

8 input points+8 output points (NPN)

DRT1-MD16C

8 input points+8 output points (PNP)

10 input points x 3

DRT1-MD16C-1

DRT1-B7AC

Remarks

Dust and drip-proof structure for environmental resistance

(IP 67)

XS2 Series connector system eliminates the need for tools for sensor, valve or other connections.

Spatter, dust and drip-proof structure for environmental resistance (IP 66)

XS2 Series connector system eliminates the need for tools for sensor, valve or other connections.

Splits 1 B7AC Unit into 3 branches.

XS2 Series connector system eliminates the need for tools.

Dust and drip-proof structure for environmental resistance

(IP 66)

Special Slaves (Communications Cable: Normal Square Connectors)

Name

C200H I/O Link Unit

RS-232C Unit

Programmable

Slaves

Appearance I/O points

512 inputs max.

(32 words)

512 outputs max.

(32 words)

16 inputs (1 word)

512 inputs max.

(32 words)

512 outputs max.

(32 words)

Model number

C200HW-DRT21

DRT1-232C2

CPM2C-S100C-DRT

CPM2C-S110C-DRT

Remarks

Supports remote I/O and message communications between PLCs.

Max. I/O area: 512 input points and 52 output points

Any I/O words can be allocated.

Two RS-232C ports mounted

Data sent and received by explicit message (151 bytes max.)

Executes settings and control through explicit messages.

Reflects RS-232C port status in the input.

Controller that enables communications with CompoBus/

S Master.

Enables message communications using explicit messages.

12

Overview of DeviceNet

Section 1-1

DRT2 Series

General-purpose Slaves (Communications Cable: Normal Square Connectors)

Name

Remote I/O Terminals with Transistors

Remote I/O Terminal with Relay Outputs

Appearance I/O points

8 input points (NPN)

8 input points (PNP)

8 output points

(NPN)

Model number

DRT2-ID08

DRT2-ID08-1

DRT2-OD08

8 output points

(PNP)

16 input points

(NPN)

DRT2-OD08-1

DRT2-ID16

16 input points (PNP) DRT2-ID16-1

16 output points

(NPN)

DRT2-OD16

DRT2-OD16-1 16 output points

(PNP)

8 input points/8 output points (NPN)

8 input points/8 output points (PNP)

16 output points

DRT2-MD16

DRT2-MD16-1

DRT2-ROS16

Remarks

Terminal block mounted/ removed using screws.

Relay outputs

Remote I/O Terminal

Expansion Units with

Transistors

Remote I/O Terminals with 3-tier Terminal Blocks and

Transistors

16 input points

(NPN)

XWT-ID16

16 input points (PNP) XWT-ID16-1

XWT-OD16 16 output points

(NPN)

16 output points

(PNP)

8 input points (NPN)

8 input points (PNP)

XWT-OD16-1

XWT-ID08

XWT-ID08-1

8 output points

(NPN)

8 output points

(PNP)

XWT-OD08

XWT-OD08-1

16 input points

(NPN)

DRT2-ID16TA

16 input points (PNP) DRT2-ID16TA-1

DRT2-OD16TA 16 output points

(NPN)

16 output points

(PNP)

8 input points/8 output points (NPN)

8 input points/8 output points (PNP)

DRT2-OD16TA-1

DRT2-MD16TA

DRT2-MD16TA-1

Expansion Unit for increasing inputs or outputs of the Basic Unit.

Wiring locations easy to find (wiring to the same terminal not required).

Cannot be expanded with an Expansion Unit.

13

Overview of DeviceNet

Name

Sensor Connector

Terminals with Transistors

Appearance

MIL Connector Terminals with Transistors

Board MIL Connector Terminals with

Transistors

R

E

O

O

TE

U

O m

T

R

C ro n

E

R

M

IN

A

L tio n

:

2

C or

4V po ra

S

O

U R

E

:

2

IN

A

L

E

M

O

TE m ro

T

E

R

M ra tio n

C or po

4V n

Section 1-1

I/O points

16 input points

(NPN)

Model number

DRT2-ID16S

16 input points (PNP) DRT2-ID16S-1

8 input points/8 output points (NPN)

DRT2-MD16S

8 input points/8 output points (PNP)

16 input points

(NPN)

DRT2-MD16S-1

DRT2-ID16ML

16 input points (PNP) DRT2-ID16ML-1

16 output points

(NPN)

DRT2-OD16ML

16 output points

(PNP)

16 input points

(NPN)

DRT2-OD16ML-1

DRT2-ID16MLX

16 input points (PNP) DRT2-ID16MXL-1

16 output points

(NPN)

DRT2-OD16MLX

16 output points

(PNP)

32 input points

(NPN)

DRT2-OD16MXL-1

DRT2-ID32ML

32 input points (PNP) DRT2-ID32ML-1

32 output points

(NPN)

DRT2-OD32ML

DRT2-OD32ML-1 32 output points

(PNP)

16 input points/16 output points (NPN)

16 input points/16 output points (PNP)

32 input points

(NPN)

DRT2-MD32ML

DRT2-MD32ML-1

DRT2-ID32B

32 input points (PNP) DRT2-ID32B-1

32 output points

(NPN)

DRT2-OD32B

DRT2-OD32B-1 32 output points

(PNP)

16 input points/16 output points (NPN)

DRT2-MD32B

16 input points/16 output points (PNP)

32 input points

(NPN)

DRT2-MD32B-1

DRT2-ID32BV

32 input points (PNP) DRT2-ID32BV-1

32 output points

(NPN)

DRT2-OD32BV

DRT2-OD32BV-1 32 output points

(PNP)

16 input points/16 output points (NPN)

16 input points/16 output points (PNP)

DRT2-MD32BV

DRT2-MD32BV-1

Remarks

Use industry standard sensor connectors.

Connects to relay terminal using MIL cable.

A connecting cable

(10 cm) is included.

Connects to relay terminal using MIL cable.

MIL connectors mounted parallel to board

MIL connectors mounted perpendicular to board

14

Overview of DeviceNet

Section 1-1

Name

Screw-less Clamp

Terminal with Transistors

Appearance I/O points

16 input points

(NPN)

Model number

DRT2-ID16SL

16 input points (PNP) DRT2-ID16SL-1

16 output points

(NPN)

DRT2-OD16SL

16 output points

(PNP)

16 input points

(NPN)

DRT2-OD16SL-1

DRT2-ID16SLH

16 input points (PNP) DRT2-ID16SLH-1

16 output points

(NPN)

DRT2-OD16SLH

16 output points

(PNP)

32 input points

(NPN)

DRT2-OD16SLH-1

DRT2-ID32SL

32 input points (PNP) DRT2-ID32SL-1

32 output points

(NPN)

DRT2-OD32SL

DRT2-OD32SL-1 32 output points

(PNP)

16 input points/16 output points (NPN)

16 input points/16 output points (PNP)

32 input points

(NPN)

DRT2-MD32SL

DRT2-MD32SL-1

DRT2-ID32SLH

32 input points (PNP) DRT2-ID32SLH-1

32 output points

(NPN)

DRT2-OD32SLH

DRT2-OD32SLH-1 32 output points

(PNP)

16 input points/16 output points (NPN)

DRT2-MD32SLH

16 input points/16 output points (PNP)

DRT2-MD32SLH-1

Remarks

Without detection function

With detection function

Without detection function

With detection function

Environment-resistant Slaves (Communications Cable: Round Waterproof Connectors)

Name

Environment-resistive Terminals

Appearance I/O points

8 input points (NPN)

8 input points (PNP)

Model number

DRT2-ID08C

DRT2-ID08C-1

16 input points

(NPN)

DRT2-HD16C

16 input points (PNP) DRT2-HD16C-1

DRT2-OD08C 8 output points

(NPN)

8 output points

(PNP)

DRT2-OD08C-1

Remarks

Waterproof, oil-proof, and spatter-proof construction (IP67).

Equipped with detection functions.

15

Overview of DeviceNet

Section 1-1

Name

Environment-resistive Terminals, Standard Models

Appearance I/O points

4 input points (NPN)

4 input points (PNP)

4 output points

(NPN)

4 output points

(PNP)

8 input points (NPN)

8 input points (PNP)

16 input points

(NPN)

Model number

DRT2-ID04CL

DRT2-ID04CL-1

DRT2-OD04CL

DRT2-OD04CL-1

DRT2-ID08CL

DRT2-ID08CL-1

DRT2-HD16CL

16 input points (PNP) DRT2-HD16CL-1

8 output points

(NPN)

DRT2-OD08CL

DRT2-OD08CL-1 8 output points

(PNP)

16 output points

(NPN)

DRT2-WD16CL

DRT2-WD16CL-1 16 output points

(PNP)

8 input points/8 output points (NPN)

8 input points/8 output points (PNP)

DRT2-MD16CL

DRT2-MD16CL-1

Analog Slaves (Communications Cable: Normal Square Connectors)

Name

Analog Terminals

Appearance I/O points

4 input points

(0 to 5 V, 1 to 5 V,

0 to 10 V,

10 to 10 V, 0 to

20 mA, 4 to 20 mA)

Model number

DRT2-AD04

Remarks

Waterproof, oil-proof, and spatter-proof construction (IP67).

Not equipped with detection functions.

Remarks

Terminal block mounted/ removed using screws.

The DRT2-AD04H is a

High-resolute Terminal

(1/30,000 FS).

4 input points

(0 to 5 V, 1 to 5 V,

0 to 10 V, 0 to 20 mA,

4 to 20 mA)

DRT2-AD04H

2 output points

(0 to 5 V, 1 to 5 V,

0 to 10 V,

10 to 10 V, 0 to

20 mA, 4 to 20 mA)

DRT2-DA02

Temperature Input

Terminals

4 input points

(Switchable between

R, S, K1, K2, J1, J1,

T, E, B, N, L1, L2, U,

W, and PL2.)

DRT2-TS04T

4 input points

(Switchable between

PT, JPT, PT2, and

JPT2.)

DRT2-TS04P

Thermocouple input

Platinum resistance thermometer input

16

Overview of DeviceNet

Section 1-1

MULTIPLE I/O TERMINAL Units

Unit I/O points

Communications Unit None

Basic I/O

Units

Transistor

Input Units

16 input points

Words allocated in PC memory

Input Output

Two status words

1 word

0 words

0 words

I/O connections

None

M3 terminal block

Unit power supply voltage

24 VDC

(supplied from outside)

Installation

DIN track

16 input points

1 word

16 input points

1 word

16 input points

1 word

32 input points

2 words

0 words

0 words

0 words

0 words

0 words

1 word

Connector

(made by

MOLEX)

Connector

(made by

FUJITSU)

Connector

(D-sub,

25 pin)

High-density connector (made by

FUJITSU)

M3 terminal block

Model number

DRT1-COM

GT1-ID16

GT1-ID16-1

GT1-ID16MX

GT1-ID16MX-1

GT1-ID16ML

GT1-ID16ML-1

GT1-ID16DS

GT1-ID16DS-1

GT1-ID32ML

GT1-ID32ML-1

GT1-OD16

GT1-OD16-1

Transistor

Output

Units

16 output points

16 output points

16 output points

16 output points

32 output points

0 words

0 words

0 words

0 words

0 words

1 word

1 word

1 word

2 words

1 word

Connector

(made by

MOLEX)

Connector

(made by

FUJITSU)

Connector

(D-sub,

25 pin)

High-density connector (made by

FUJITSU)

M3 terminal block

GT1-OD16MX NPN

GT1-OD16MX-1 PNP

GT1-OD16ML NPN

GT1-OD16ML-1 PNP

GT1-OD16DS NPN

GT1-OD16DS-1 PNP

GT1-OD32ML NPN

GT1-OD32ML-1 PNP

GT1-ROS16

Remarks

---

NPN

PNP

NPN

PNP

NPN

PNP

NPN

PNP

NPN

PNP

NPN

PNP

--Relay Output Units

16 output points

8 output points

0 words 1 word GT1-ROP08 ---

17

Overview of DeviceNet

Section 1-1

Special

I/O Units

(See note.)

Unit

Analog

Input Units

I/O points

Words allocated in PC memory

Input Output

4 inputs 4 words

8 inputs 8 words

0 words

0 words

I/O connections

M3 terminal block

Connector

(made by

MOLEX)

Unit power supply voltage

24 VDC

(supplied from outside)

Installation

DIN track

Model number

GT1-AD04

GT1-AD08MX

Analog

Output

Units

Counter

Unit

4 outputs

4 outputs

1 input

0 words 4 words M3 terminal block

0 words 4 words Connector

(made by

MOLEX)

Temperature Input

Unit

4 inputs 4 or 8 words

4 inputs

(varies with data format)

0 words

0 words

M3 terminal block

M3 terminal block

3 words 3 words M3 terminal block

GT1-DA04

GT1-DA04MX

GT1-TS04T

GT1-TS04P

GT1-CT01

Remarks

Inputs:

4 to 20 mA,

0 to 20 mA,

0 to 5 V,

1 to 5 V,

0 to 10 V,

–10 to 10 V

Outputs:

4 to 20 mA

0 to 5 V,

1 to 5 V,

0 to 10 V,

–10 to 10 V

Outputs:

0 to 5 V,

1 to 5 V,

0 to 10 V,

–10 to 10 V

Sensor types: R, S,

K, J, T, B, L

Sensor types:

Pt100,

JPt100

1 external input

2 external outputs

Note

The front-panel indicators and other parts of Analog Input Units, Analog Output Units, and Counter Units differ from those of other I/O Units. These Units belong to a group called Special I/O Units.

One I/O Unit Connecting Cable (cable length 40 mm) is included with each I/O

Unit. One end connector is attached to the Communications Unit.

I/O Unit Connecting Cables with a cable lengths of 0.1, 0.3, 0.4, 0.6, and 1 m

(GCN1-010/030/040/060/100) are sold separately (see below).

Length

Note

For details on MULTIPLE I/O TERMINAL Units, refer to the

DeviceNet MULTI-

PLE I/O TERMINAL Operation Manual

(W348).

18

DeviceNet Unit Features

Section 1-2

1-1-5

Product name

DeviceNet

Configurator

(Ver. 2)

DeviceNet Configurator

Use version 2 of the DeviceNet Configurator for the CS1W-DRM21(-V1)/

CJ1W-DRM21 DeviceNet Unit. Earlier versions of the DeviceNet Configurator do not support the CS1W-DRM21 DeviceNet Unit.

Model

WS02-CFDC1-E

Components

Installation disk

(CD-ROM)

Network connection to computer

Any of the following:

• Serial connection

• PCI Board

• PCMCIA Card

(See the table below.)

Applicable computer

IBM PC/AT or compatible

OS

Windows 95, 98,

Me, NT4.0, 2000, or XP

Model

Note

The following Boards and Cards can be used.

Components

3G8F7-DRM21 Dedicated PCI Board (DeviceNet

Configurator is not included.)

3G8E2-DRM21-V1 Dedicated PCMCIA Card with

DeviceNet Configurator (Ver. 2)

Applicable computer

IBM PC/AT or compatible

OS

Windows 95, 98,

NT4.0, 2000, or XP

Windows 98, Me,

2000, or XP

Note

Use Configurator version 2.10 or higher for the CJ1W-DRM21.

1-2 DeviceNet Unit Features

The following are features of the CS-series and CJ-series DeviceNet Units

(CS1W-DRM21(-V1) and CJ1W-DRM21).

Multi-vendor Network

Simultaneous Remote I/O

Communications and

Messaging Services

Devices made by other companies (masters or slaves) can be connected to

DeviceNet because it conforms to open field network specifications. By using a combination of valves, sensors, and other DeviceNet products, the network can be adapted to various field-level applications.

Remote I/O communications that constantly transfer I/O between a DeviceNet

Unit and slaves as well as message communications where the DeviceNet

Unit sends and receives data as needed can both be executed simultaneously. When a DeviceNet network is constructed, this feature ensures the network will be able to handle applications that require the free flow back and forth of bit data and message data. FINS commands can be executed along with DeviceNet explicit messages in message communications.

Remote I/O Communications

CS/CJ-series DeviceNet

Unit (master)

Remote I/O (master) function

DeviceNet

Slave

Slave Slave

Note

Refer to

SECTION 4 Remote I/O Master Communications

for details on remote I/O communications.

19

DeviceNet Unit Features

Section 1-2

Explicit Message Communications

CS/CJ-series

DeviceNet Unit

RS-232C

Slave

Explicit message

DeviceNet

RS-232C

Slave

CS/CJ-series

DeviceNet Unit

Note

Refer to

6-4 Sending Explicit Messages

for details on remote I/O communica-

tions.

FINS Message Communications

CS/CJ-series

DeviceNet Unit

Slave

FINS message

DeviceNet

Slave

CS/CJ-series

DeviceNet Unit

Note

Refer to

6-3 Using FINS Message Communications

for details on FINS com-

munications.

User-set allocations without the Configurator

With CS/CJ-series DeviceNet Units, remote I/O communications can be allocated in any area without the Configurator simply by using DM Area settings.

If the Configurator is used, it allows you to change the node address order for more flexible I/O allocations. This feature ensures the proper I/O allocations for any application and it makes effective use of PLC memory by simplifying programming.

Note

Refer to

4-4 User-set Allocations

for details.

Slave Functions

CS/CJ-series DeviceNet Units can be used as both masters and slaves, and master and slave communications can be executed either separately or simul-

20

DeviceNet Unit Features

Section 1-2

taneously. A Unit that is used as a slave supports fixed and user-set allocations. The maximum I/O for the slave function is 100 words.

CS/CJ-series DeviceNet Unit

(Master)

Master PLC

DeviceNet

CS/CJ-series

DeviceNet Unit (Slave)

Slave PLC

64 nodes max.

Note

Refer to

SECTION 5 Remote I/O Slave Communications

for details.

Configurator Connection through a Serial Line

The Configurator can also be connected either as a DeviceNet node or to a serial port on a CPU Unit or a Serial Communication Unit/Board.

CS/CJ-series DeviceNet Unit

(Master)

CPU Unit

Configurator

Scan list registration

Serial connection

(Host Link or Peripheral Bus)

DeviceNet

21

DeviceNet Unit Features

Section 1-2

CX-Programmer

Programming and

Monitoring of DeviceNet

Slave PLCs (Ver. 2.1 or higher)

CX-Programmer Ver. 2.1 connected to a serial communications port on a

DeviceNet PLC can be used to remotely program and monitor other

DeviceNet PLCs (i.e., PLCs with a CS/CJ-series DeviceNet Unit or a Programmable Slave).

CS/CJ-series DeviceNet

Unit (master)

CX-Programmer

DeviceNet

Programmable

Slave

Serial line (Host Link or peripheral bus)

CS/CJ-series DeviceNet

Unit (master)

CS/CJ-series

Ethernet Unit

CS/CJ-series DeviceNet

Unit (master)

CX-Programmer

Ethernet

DeviceNet

Programmable

Slave

CS/CJ-series DeviceNet

Unit (master)

Note

Refer to

7-1 Connecting to the CX-Programmer via the DeviceNet

for details.

Inter-network Connections

FINS messages can be sent back and forth between DeviceNet and other networks (e.g., Controller Link, SYSMAC LINK, and Ethernet). This feature enables seamless message communications between all types of networks, including DeviceNet.

Controller Link Unit

Controller Link Unit

CS/CJ-series DeviceNet Unit

Controller Link

FINS message

DeviceNet

CS/CJ-series

DeviceNet Unit

Note

Refer to

6-3 Using FINS Message Communications

for details.

22

DeviceNet Unit Features

Section 1-2

Multiple PLCs in a Single

Network

Multiple DeviceNet Units can be connected in a single network for message communications between PLCs as well as for remote I/O communications between PLCs and slaves in multiple groups. This feature allows a DeviceNet to be used as a common bus that can integrate all types of control with less wiring.

CS/CJ-series DeviceNet Unit

(Master)

CS/CJ-series

DeviceNet Unit (Master)

Master PLC

Master PLC

CS/CJ-series

DeviceNet Unit

(Slave)

DeviceNet

Slave PLC

Remote I/O

Remote I/O

Note

Refer to

4-1 Master Remote I/O Communications

for details.

Multiple DeviceNet Units on a Single PLC

Up to 16 CS/CJ-series DeviceNet Units can be mounted to a single PLC. This feature enables greater DeviceNet remote I/O control capacity and ensures that DeviceNet can easily handle line expansion as well as other applications.

CS/CJ-series DeviceNet Unit

(master) (See note 1.)

CS/CJ-series DeviceNet Unit

(master)

DeviceNet DeviceNet

CS/CJ-series DeviceNet Unit

(slave) (See note 2.)

CS/CJ-series DeviceNet Unit

(master) (See note 1.)

DeviceNet

DeviceNet

DeviceNet

Note

1.

2.

3.

Multiple Units can be mounted without the Configurator.

DeviceNet Units set as both slaves and/or masters can be mounted at the same time.

Refer to

4-1 Master Remote I/O Communications

for details.

23

DeviceNet Unit Features

Section 1-2

DeviceNet Unit Setup Files

(Memory Card Backup)

Setup data (e.g., scan lists) in a DeviceNet Unit can be written as a file to the

Memory Card mounted in a CPU Unit. This feature greatly simplifies

DeviceNet Unit replacement. A DeviceNet Unit device parameter file (same as data setup file) that is prepared offline using the Configurator can be saved on a Memory Card, and setup data from the Memory Card can be downloaded to a DeviceNet Unit. (See

Appendix D Memory Card Backup Function

for more details.)

CS/CJ-series DeviceNet Unit

Configurator

CPU Unit

Memory Card

File save

File load

Loads setup data to a DeviceNet Unit using a software switch in CIO Area of the CPU Unit.

System Backup (Simple

Backup)

Note

Refer to

7-2 Memory Card Backup Functions

for details.

The CPU Unit’s simple backup function enables backup data for the entire

PLC, including DeviceNet Units, the CPU Unit, and Serial Communications

Units/Boards to be saved on or downloaded from a Memory Card.

Setup data in CS1W-DRM21-V1 or CJ1W-DRM21

DeviceNet Unit

Example: Protocol macro data in Serial Communications Unit

All data including user programs, parameters, and

I/O memory in the CS1-H or CJ1-H CPU Unit.

All data

Memory Card

Backup data (obtained using the CPU Unit’s simple backup function)

The simple backup function is supported only when using a combination of a

CS1-H CPU Unit with a CS1W-DRM21-V1 DeviceNet Unit, or a CJ1-H CPU

Unit with a CJ1W-DRM21 DeviceNet Unit.

Note

Refer to

7-3 Simple Backup Function

for details.

24

DeviceNet Unit Features

Various Connection

Methods

Maximum Network Length of 500 m

High-speed

Communications

Compatibility with Slow

Slaves

A Wide Variety of Slaves

Section 1-2

Normal multi-drop, T-branch multi-drop (with up to three branches), and daisychain line connections are available. These methods can be combined to construct a flexible system that suits the floor layout.

A network can connect up to 63 Slaves and can handle remote I/O communications of up to 2,000 byes (16,000 points without the Configurator) per

DeviceNet Unit. A maximum network length of 500 m is possible with a baud rate of125 Kbps using thick cable.

High-speed communications are possible at up to 500 Kbps for a trunk line length of 100 m.

The communications cycle time can be set even without the Configurator so slaves with slow response times can be used.

A wide variety of I/O devices, like Remote I/O Terminals, Environment-resistant Terminals, Remote Adapters, Sensor Terminals, Temperature Input Terminals, CQM1 I/O Link Units, Analog I/O Terminals, C200H I/O Link Units,

RS-232C Units, MULTIPLE I/O TERMINALs, Temperature Adjusters, Inverters, and Intelligent Plugs can be used as slaves.

25

Specifications

Section 1-3

1-3 Specifications

1-3-1 DeviceNet Unit

Model

Applicable PLC

CS Series

CJ Series

Unit classification

CPU Bus Unit

Types of communications

• Remote I/O communications master (fixed or user-set allocations)

• Remote I/O communications slave (fixed or user-set allocations)

• Message communications

Model number

CS1W-DRM21(-V1)

CJ1W-DRM21

General Specifications

General specifications of the CS/CJ-series DeviceNet Unit conform to the general specifications for the SYSMAC CS/CJ-series CPU Units.

Functional and Performance Specifications

DeviceNet Unit model

Applicable PLC

Unit classification

Applicable unit numbers

Mounting position

No. of

Masters that can be mounted

Item

Fixed allocations

User-set allocations

CS1W-DRM21(-V1)

CS Series

Specification

CJ1W-DRM21

CJ Series

CPU Bus Unit

0 to F

CPU Rack, CS Expansion Rack

(Cannot be mounted to a C200H

Expansion I/O Rack or SYSMAC BUS

Slave Rack.)

CPU Rack or Expansion Rack

3 Units max. (Unique words must be allocated using the Allocated CIO

Area Words Software Switches.)

By allocated

DM Area words

16 Units max. (Unique words must be allocated using the user setup tables in the allocated DM Area words.)

By Configurator 16 Units max. (Unique words must be allocated using the Configurator.)

No. of

Slaves that can be mounted

Fixed allocations

User-set allocations

By allocated

DM Area words

3 Units max. (Unique words must be allocated using the Allocated CIO

Area Words Software Switches)

16 Units max. (Unique words must be allocated using the user setup tables in the allocated DM Area words.)

By Configurator 16 Units max. (Unique words must be allocated using the Configurator.)

No. of Units that can be connected per network 64 Units max.

Words allocated in the CPU

Unit

DeviceNe t remote

I/O communications

When used as a Master

When used as a Slave

Fixed allocations

User-set allocations

Fixed allocations

User-set allocations

Fixed words in the CS/CJ-series DeviceNet Area in the CIO Area (any of three settings).

Any I/O memory (Set using the allocated DM Area words or Configurator.)

Fixed words in the CS/CJ-series DeviceNet Area in the CIO Area (one of three settings).

Any I/O memory words (Set in allocated DM Area words or Configurator.)

CIO Area words allocated for the

CPU Bus Unit

DM Area words allocated for the

CPU Bus Unit

Other I/O memory

25 words/Unit (allocation for one Unit)

CPU Unit to DeviceNet Unit: 9 words for the software switches, 6 words for the status area, 8 words for the registered slaves and normal slaves tables

100 words/Unit (allocation for one Unit)

Scan List User Setup Table, Slave User Setup Table, Master I/O Allocation Reference Table, Slave I/O Allocation Reference Table, Detailed

Slave Status Table, etc.

CPU Unit to DeviceNet Unit: Table for communications cycle time settings

Set the allocation size table for all slaves in any area when remote I/O communications is set to user-set allocations from the setting in the allocated DM Area words.

26

Specifications

Section 1-3

Item

Supported connections (communications)

Remote I/O master communications

Slave allocation method Fixed allocations

User-set allocations

Specifications

• Remote I/O communications (master and slave): Master/slave connection (poll, bit-strobe, COS, cyclic)

• Explicit message and FINS message communications: Explicit connection

All conform to DeviceNet communications standards.

Select one of the following fixed allocation areas using the Fixed

Allocated Area Switches 1, 2, and 3 in the software switches in the allocated CIO Area words.

I/O Size Allocated words

(CIO

Area)

Fixed

Allocation

Area

Setting

1

Fixed

Allocation

Area

Setting

2

Fixed

Allocation

Area

Setting

3

Output

(OUT) area

Input (IN) area

64 words

64 words

3200 to

3263

3300 to

3363

3400 to

3463

3500 to

3563

3600 to

3663

3700 to

3763

By allocated DM

Area words

By Configurator

Select one of the above areas using the software switches. All are fixed at 1 word per node address.

The default setting is Fixed Allocation Area Setting 1.

Set the areas and the first words for the OUT 1 and

IN 1 blocks in the Scan List Setup Table in the allocated DM Area words. Set the allocation size for each slave using the Allocation Size Setup Table

(any words). Allocations must be in the order of node addresses.

Allocated words

The input and output areas can be the following sizes starting from any word in any of the following areas: CIO Area,

WR Area, HR Area, DM, Area, or EM

Area.

Output

(OUT) area

500 words max.

×

1 block

Input (IN) area

500 words max.

×

1 block

Set the areas for the OUT 1/2 and IN 1/2 blocks, the first words, and the allocation sizes for all slaves using the Configurator. Blocks can be set for nodes in any order.

Allocated words

The input and output areas can be the following sizes starting from any word in any of the following areas: CIO Area,

WR Area, HR Area, DM, Area, or EM

Area.

Output

(OUT) area

500 words max.

×

2 blocks

Input (IN) area

500 words max.

×

2 blocks

27

Specifications

Section 1-3

Remote I/O master

Remote I/O slave

Item

Max. No. of Slaves connected per DeviceNet Unit

Fixed allocations

User-set allocations

By allocated DM

Area words

By Configurator

63 nodes

Specifications

Max. No. of I/O points per

DeviceNet Unit

Fixed allocations

User-set allocations

By allocated DM

Area words

By Configurator

Fixed allocations Max. No. of I/O per Slave controllable by a DeviceNet

Unit

User-set allocations

Allocation method Fixed allocations

2,048 pts (64 input words, 64 output words)

16,000 pts (500 input words x 1 block, 500 output words x 1 block)

32,000 pts (500 input words x 2 blocks, 500 output words x 2 blocks)

2,048 pts (64 input words, 64 output words)

By allocated DM

Area words

By Configurator

3,200 pts (100 input words, 100 output words)

3,200 pts (100 input words, 100 output words)

Select one of the following fixed allocation areas using the Slave

Fixed Allocated Area Switches 1, 2, and 3 in the software switches in the allocated CIO Area words.

I/O Size Allocated words

(CIO

Area)

Fixed

Allocation

Area

Setting

1

Fixed

Allocation

Area

Setting

2

Fixed

Allocation

Area

Setting

3

User-set allocations

Output

(OUT) area to the slave from the master

Input

(OUT) area to the master from the slave

3370 3570 3770

3270 3470 3670

Note

Select one of the preceding areas using the software switches. All are fixed at 1 word per node address. The default setting is Fixed Allocation Area Setting 1.

By allocated DM

Area words

Set the areas, the first words, and slave allocation size for the OUT 1 and IN 1 blocks (total of 2 blocks) using the Slave User Allocation Setup Table in the allocated DM Area words.

Allocated words

The input and output areas can be the following sizes starting from any word in any of the following areas: CIO Area,

WR Area, HR Area, DM, Area, or EM

Area.

Output (OUT) area from this slave

Input (IN) area to this slave

100 words

100 words

28

Specifications

Section 1-3

Remote I/O slave

Item

Allocation method User-set allocations

By Configurator

Max. No. of I/O points per

DeviceNet Unit slave

Default settings

Fixed allocations

User-set allocations

By allocated DM

Area words

By Configurator

Data stored in non-volatile memory (EEPROM) in the

DeviceNet Unit

Input (IN) area to this slave

32 points (1 input word, 1 output word)

100 words

3,200 pts (100 input words, 100 output words)

4,800 pts (100 input words x 2, 100 output words x 1)

• Scan list: Not supported

• Master communications: Supported

• Slave communications: Disabled

• Remote I/O communications: Start

• Master fixed allocations: Fixed Allocation Area Setting 1

• Slave fixed allocations: Fixed Allocation Area Setting 1

Saves the following data settings (same as the backup file on the

Memory Card).

• Master scan list

• Slave scan list

• Message monitoring timer list (monitoring time for explicit message responses)

• Communications time settings

• Master/Slave enabled

Applicable connections

Communications cycle time

Allocated words

Specifications

Set the areas for the OUT 1/2 and IN 1/2 blocks, the first words, and the slave allocation sizes using the

Configurator.

The input and output areas can be the following sizes starting from any word in any of the following areas: CIO Area,

WR Area, HR Area, DM, Area, or EM

Area.

Output (OUT) area from this slave

100 words

• The DeviceNet Unit automatically selects the applicable connection.

• The user can also specify poll, bit-strobe, COS (change of state) or cyclic for the applicable connection of each slave using the Configurator. Up to two types of connections can be set for each Slave (although COS and cyclic cannot be specified simultaneously).

Uses values calculated using the following equations to derive default value.

Example: 16 Input Slaves (16 points each), 16 Output Slaves

(16 points each), and a baud rate of 500 Kbps: 9.3 ms

The user can set a value within a range from 2 to 500 ms. However, the calculated value is only enabled when the calculated value from the conditions equation is greater than the setting.

Note

Uses the default value calculated using 1 input word and

1 output word even for missing nodes when the scan list is disabled.

29

Specifications

Section 1-3

Message communications

Other functions

Item

Max. No. of nodes for message communications per DeviceNet Unit

FINS message communications (Node address 0 cannot be used in FINS communications.)

Send explicit messages

Specifications

62 nodes

63 nodes

Note

FINS message communications using

SEND/RECV are not supported on

PCs to which a

C200H DeviceNet

Master Unit or a

CVM1/CV

DeviceNet Master

Unit is mounted.

Explicit message are supported however.

SEND/RECV instructions Execution commands

Sending and receiving FINS commands connected through a serial line

Inter–network communications

Remote programming/monitoring functions

Different type of network

Operation from the Configurator connected through a serial line

Same type of network

Memory Card backup function

FINS commands to send/receive data

Any FINS commands CMND instruction

Executes FINS commands from a host computer to a PC (to which a CS/CJ-series DeviceNet Unit is mounted) on DeviceNet through Host Link connections. A PLC can also send unsolicited

FINS commands over DeviceNet to a host computer connected through Host Link.

Allows transmission across the same type of networks between

DeviceNet networks when multiple Units are mounted (can cross up to three levels).

Allows transmission across different types of networks between

DeviceNet and other networks (e.g., Controller Link, SYSMAC

LINK and Ethernet) (can cross up to three levels).

A CX-Programmer connected to the serial communications port of a PLC to which a CS/CJ-series DeviceNet Unit is mounted can remotely program and monitor DeviceNet slave PLCs with a CS/

CJ-series DeviceNet Unit mounted. Either the peripheral port or built-in RS-232C port can be used with the Host Link or peripheral bus protocol. (Scheduled for CX-Programmer Ver. 2.1 or higher)

Note

1. Serial ports on a Serial Communications Board/Unit can be used in addition to the ports on the CPU Unit.

2. Inter-network communications across up to 3 levels is possible (even over different types of network).

3. This is also possible from a CX-Programmer on network.

Allows all online monitoring and setup functions to be performed on a master PLC on the DeviceNet network from the Configurator connected through a serial line (scan list registration, communications parameter settings, etc.).

Allows DeviceNet Unit data settings (scan list, communication cycle time settings, etc.) to be backed up as a file to a Memory

Card in the CPU Unit. The data settings can also be restored into the DeviceNet Unit from the Memory Card in the CPU Unit. Setting data can be restored into a DeviceNet Unit simply by carrying the Memory Card to the site if the device parameter file prepared from the Configurator is saved to Memory Card from a

PLC.

Simple backup function Enables all setup data in the DeviceNet Unit’s non-volatile memory (EEPROM), as well as all data in the CPU Unit, to be automatically backed up to, restored from, or compared with a file in a

Memory Card mounted in the CPU Unit.

Note

The simple backup function is supported only when using a combination of a CS1-H CPU Unit with a

CS1W-DRM21-V1 DeviceNet Unit, or a CJ1-H CPU

Unit with a CJ1W-DRM21 DeviceNet Unit.

30

Specifications

Other functions

Item

Error history in the DeviceNet Unit

Communications cycle time setting

Message monitoring timer

COS/cyclic heartbeat timer setting

Device data check function

Configurator connection method

Setting section

Display section

Front connector

Communications power supply voltage

Influence on CPU Unit cycle time

Current consumption

External dimensions

Weight

Standard accessories

Section 1-3

Specifications

Supported. (The history can be accessed up by the Configurator or using a FINS command.)

Supported (in the allocated DM Area words or from the Configurator).

Sets the response monitoring time (explicit connection opening interval) in the DeviceNet Unit for explicit message communications. Settings can be made separately for all targeted devices using the Configurator.

Sets the minimum SEND interval in COS or cyclic connections for all targeted devices. The setting is made using the Configurator.

Performs a comparison check on the following device data when slave data registered in the scan list is compared with actual slave data. The Configurator can be used to set this function for all targeted Slaves.

Vendor, device type and product code

1) Serial connection (peripheral bus or Host Link)

2) Direct DeviceNet connection through a dedicated Board/Card

The online functions available are the same for both 1) and 2).

Rotary switches:

Unit No. (hexadecimal x 1), node address (decimal x 2)

Front panel DIP switch: Baud rate, stop or continue communications when an error occurs

Two LED indicators (2 colors): Display Unit and network status.

Two-digit 7-segment display: Displays the DeviceNet Unit node address, error code, and node address where an error occurred.

2 dot LED indicators: Display whether the registration scan list is enabled or not.

One communications connector (communications data: CAN H and CAN L, communications power supply: V+, V–, shielded)

Use the XW4B-05C1-H1-D connector provided to connect the communications cable.

Note

Use the XW4B-05C4-T-D connector sold separately for multi-drop connections.

11 to 25 VDC (supplied from the communications connector)

0.7 ms+0.001 x the number of words allocated

CS1W-DRM21(-V1):

Communications power supply: 30 mA at 24 VDC, (supplied from the communications connector)

Internal circuit power supply: 290 mA max. at 5 VDC (supplied from the Power Supply Unit)

CJ1W-DRM21:

Communications power supply: 18 mA at 24 VDC, (supplied from the communications connector)

Internal circuit power supply: 290 mA max. at 5 VDC (supplied from the Power Supply Unit)

CS1W-DRM21(-V1): 35 x 130 x 101 mm (W x H x D)

CJ1W-DRM21: 31 x 90 x 65 mm (W x H x D)

CS1W-DRM21: 172 g (including the connector provided)

CS1W-DRM21-V1: 169 g (including the connector provided)

CJ1W-DRM21: 118 g (including the connector provided)

One XW4B-05C1-H1-D connector to connect to a node from a Tbranch Tap.

31

Specifications

1-3-2

Section 1-3

Comparison between CS1W-DRM21(-V1) and CJ1W-DRM21

Only the following items are different between the CS1W-DRM21(-V1) and the CJ1W-DRM21. Otherwise, these Units are functionally the same.

Item CS1W-DRM21(-V1)

Consumption current Communications power supply: 30 mA at 24 VDC

External dimensions 35 x 130 x 101 mm

(W x H x D)

Weight (including connector) 172 g (CS1W-DRM21)

169 g (CS1W-DRM21-V1)

CJ1W-DRM21

Communications power supply: 18 mA at 24 VDC

31 x 90 x 65 mm

(W x H x D)

118 g

32

Comparison with Previous Models

Section 1-4

1-4 Comparison with Previous Models

The following table provides a comparison between the CS1W-DRM21(-V1)

DeviceNet Unit and the C200HW-DRM21-V1 DeviceNet Master Unit used in a

CS/CJ-series PLC.

Item

Unit classification

Mounting position

No. of Masters that can be mounted

Fixed allocations

C200HW-DRM21-V1

C200H Special I/O Unit

CPU Rack, C200H I/O Expansion Rack, CSseries Expansion Rack

1 Master

16 Masters (Configurator required)

CS1W-DRM21(-V1)/CJ1W-DRM21

CPU Bus Unit

CPU Rack, CS/CJ-series Expansion Rack

3 Masters (Select unique words must be allocated using the software switches.)

3 Slaves (Select unique words must be allocated using the software switches.)

16 Masters (even without the Configurator) User-set allocations

Routing table registration Not necessary When creating a routing table, registration in a local network table is necessary.

Unit No. that can be set

Masters on a single network

Remote I/O communications

Master

Slave

Message communications

0 to F

Multiple Masters, Configurator required

X

0 to F

Multiple Masters even without the Configurator

Explicit message send, FINS message communications

Explicit message send, FINS message communications

Note

Can send and receive explicit messages to the PC to which a C200H

DeviceNet Master Unit or CVM1/CV

DeviceNet Master Unit is mounted.

Cannot sent or receive FINS messages.

Not required Registration in the scan list when using only message communications

Area used to exchange data with the

CPU Unit

(not including remote I/

O allocation)

Allocated

CIO Area words

Allocated DM

Area words

Dedicated

DM area

Required

2,000 to 2,009 + (10 x unit number)

Not used

D06032 to D06033 + (2 x unit number)

1,500 to 1,524 + (25 x unit number)

D30000 to D30099 (100 x unit number)

Not used.

Note

With user-set allocations using the allocated DM Area words however, the Allocation Size Setup Table must be allocated to a position in I/O memory.

33

Comparison with Previous Models

Section 1-4

Remote I/O communications Master

Item

Fixed allocations

User-set allocations

C200HW-DRM21-V1

C200H DeviceNet words in CIO Area

1,600 points (50 input words, 50 output words)

Output area: CIO 0050 to CIO 0099

Input area: CIO 0350 to CIO 0399

CS1W-DRM21(-V1)/CJ1W-DRM21

CS/CJ-series DeviceNet words in CIO Area

2,048 points (64 input words, 64 output words)

Select one of the following using the software switch.

Output area: (1) CIO 3200 to CIO 3263

(2) CIO 3400 to CIO 3463

(3) CIO 3600 to CIO 3663

Input area: (1) CIO 3300 to CIO 3363

(2) CIO 3500 to CIO 3563

(3) CIO 3700 to CIO 3763

Node addresses: 0 to 63, node address order, 1 word/node address

Node addresses: 0 to 49, node address order, 1 word/node address

• Slaves with 8 points: Require 1 word even though they are allocated the rightmost byte

(requires 1 node address)

• Slaves with 16 points: Require 1 word (require 1 node address)

• Slaves with over 16 points: Require multiple words (require multiple node addresses)

Set by the Configurator.

When using the message communications function:

1,600 pts max. (800 input words, 800 output words)

When not using the message communications function:

4,800 pts max. (2,400 input words, 2,400 output words)

Set from allocated DM Area words (Master

User Allocation Setup Table) or the Configurator.

When set from allocated DM Area words:

16,000 pts max. (8,000 input words, 8,000 output words)

When set from the Configurator:

32,000 pts max. (16,000 input words, 16,000 output words)

The following areas can be set:

CIO: 0000 to 0235, 0300 to 0511

CIO: 1000 to 1063

HR: HR000 to HR099

DM: D00000 to D05999

The following areas can be set:

CIO: 0000 to 6143

WR: W000 to W511

HR: HR000 to HR511 words

DM: D00000 to D32767

EM: E00000 to E32767 (Banks 0 to C supported)

Any position in the allocation areas given above.

OUT 1, OUT 2, IN 1, and IN 2, for a total of 4 blocks can be set at any size (total for 1 to 4 blocks) at any position in the allocation areas given above.

Any node addresses can be set within a block.

Using allocated DM Area words: Total of two block, OUT 1 and IN 1.

Using the Configurator: A total of 3 blocks,

OUT 1, IN 1, and IN 2

500 words max. per block With a total of 4 blocks and a maximum of

100 words per block, the maximum number of words is 100 using message communications and 300 without using the message communications.

Using allocated DM Area words:

1,000 words total for 2 blocks

Using the Configurator:

2,000 words total for 4 blocks

Maximum of 32 input words, 32 output words per slave.

Using 2 connections:

Maximum of 200 input words, 100 output words per slave.

Using 1 connection:

Maximum of 100 input words, 100 output words per slave.

There are the following restrictions.

• The bytes 7 to 15 cannot be used for start bytes for slaves with more than 8 points.

• More than one master cannot share a slave.

• Slaves with 8 points: Require the leftmost or rightmost byte (does not require 1 word)

• Slaves with 16 points: Require 1 word

• Slave with over 16 points: Require multiple words (the last byte will be the rightmost byte with an odd number of bytes)

34

Comparison with Previous Models

Section 1-4

Remote I/O communications Master

Remote I/O

Slave

Message communications

Configuration connection method

Item

Max. No. of slaves connected

Fixed allocations

User-set allocations

Execute commands

C200HW-DRM21-V1

With no Configurator (fixed allocations):

50 nodes

With no Configurator (user-set allocations):

63 nodes

No

CS1W-DRM21(-V1)/CJ1W-DRM21

63 nodes for fixed or user-set allocations

No

Sending/receiving data: No

Any FINS command: IOWR instruction

Max. No. of nodes for message communications

Gateway function from serial communications

Inter-network function

8 nodes

Not supported

Not supported

Serial connection

Direct connection to

DeviceNet

I/O communications at startup

Not supported

Supported

Specifies I/O communications start/stop after each slave on the scan list starts

(nodes that perform explicit message communications must also be registered in the scan list).

DeviceNet words in CIO Area: 32 points

(1 input word, 1 output word)

Select one of the following:

Input area to the Slave:

(1) CIO 3370, (2) CIO 3570, (3) CIO 3770

Output area from the Slave:

(1) CIO 3270, (2) CIO 3470, (3) CIO 3670

Set in the allocated DM Area words or the

Configurator.

The following areas can be set:

CIO: CIO 0000 to CIO 6143

WR: W000 to W511

HR: HR000 to HR511

DM: D00000 to D32767

EM: E00000 to E32767 (Banks 0 to C supported)

Using the allocated DM Area words:

Can create OUT 1 and IN 1 for a total of 2 blocks.

Using the Configurator:

Can create OUT 1, IN 1, and IN 2 for a total of 3 blocks.

100 words max. per block

Using the allocated DM Area words: 200 words total for 2 blocks

Using the Configurator: 300 words total for 3 blocks

Sending/receiving data: SEND/RECV instructions

Any FINS command: CMND instruction

63 nodes

Allows the CX-Programmer connected by a serial line to remotely control and monitor a

PLC on the DeviceNet (scheduled for Ver.

2.1).

Supported

Allows inter-network communications between DeviceNet and networks like Controller Link and Ethernet (3 levels max.).

Supported (Peripheral Bus or Host Link connection to a CPU Unit or a Serial Communication Board/Unit)

Supported

Sets Master start/stop (using a software switch or the Configurator).

Performs I/O communications only with slaves registered in the scan list. (Explicit message nodes do not have to be registered in the scan list.)

35

Comparison with Previous Models

Section 1-4

Item

Starting and stopping remote communications during I/O communications

C200HW-DRM21-V1 CS1W-DRM21(-V1)/CJ1W-DRM21

Starts or stops remote I/O communications using the Configurator or the software switch from a Programming Device.

Remote I/O communications with a communications error

Sets remote I/O communications start or stop when an error occurs in master communications (set on DIP switch on the front of the Master).

Communications parameters Can be changed (communications cycle time).

Supported Sending explicit messages to slaves made by another company

Master error history

Setting communications cycle time

Monitoring current communications cycle time

Switch that disables communications error stoppage

Error with multiple Units mounted

Yes (Can be read by the Configurator or FINS command.)

Supported (by the Configurator)

Supported

The switch that cancels communications error stoppage is different from the one that starts remote I/O communications.

A mounting error occurs with fixed allocations.

Supported (with or without the Configurator)

The same software switch is used to cancel communications error stoppage and to start remote I/O communications.

An error does not occur even with multiple

Units mounted. Operation will continue even if the same words are allocated to more than one Unit.

No check for multiple mounted Units.

Error code on the front panel 7-segment display

Error with multiple Units mounted

PLC initialization error

Display: E4

Display: F5 Used more detailed error codes in initialization phase. Display: H @ .

Changed to H3 (related to the above).

Changed to H5 (related to the above).

RAM error

Incorrect switch setting

Routing table error

PLC Unit

WDT error

EEPROM error

Configuration data error (scan list SUM error)

Display: F5

Display: F5

Display: E5

Display: All lit

Display: F8 Stops operation to store the scan list.

Display: E8 Continues operation in DIS-

ABLED mode.

Changed to HC (related to the above).

Display: E7 Unit does not reset. Explicit server functions run.

Display: E3 Operation continues for error history only (scan list stored in flash ROM)

Display: F7 Stops remote I/O communications in Master communications.

36

Outline of the Configurator

Section 1-5

1-5 Outline of the Configurator

Allocations for remote I/O communications can be set in any order of node addresses from the Configurator. Users can also set remote I/O communications connections.

Device (master/slave) registration, I/O allocations, and other operations are especially easy to perform because of graphic operations, including dragging and dropping icons.

Any of the following methods can be used to connect the Configurator to

DeviceNet. All the connection methods support the same online connection functions.

Connection from Dedicated Board/

Card Installed in Computer

Serial Connection from COM port of Computer

WS02-CFDC1-E

Configurator

ISA Board or PCMCIA Card

DeviceNet Network

CS/CJ-series

DeviceNet Unit

WS02-CFDC1-E

Configurator

COM port

Peripheral bus or Host Link

Peripheral or RS-232C port of

CPU Unit or RS-232C port of

Communications Board/Unit

DeviceNet network

The Configurator is not treated as a single DeviceNet Node.

The Configurator is treated as a single

DeviceNet node.

1-5-1

Product

Models

Configurator

(Ver. 2.

@ )

Model

WS02-CFDC1-E

Contents

Installation disk

(CD-ROM)

Method of connecting personal computer to network

Either one of the following methods

• Serial connection

• Dedicated PCI Board

• Dedicated PCMCIA Card

(See table below.)

Personal computer

IBM PC/AT or compatible

OS

Windows 95,

98, Me, NT4.0,

2000, or XP

Note

Use the following dedicated Boards and Card.

Model

3G8F7-DRM21

3G8E2-DRM21-

V1

Contents Personal computer

Dedicated PCI Board (Configurator is not included.) IBM PC/AT or compatible

Dedicated PCMCIA Card and Configurator (Ver.2) installation disk

OS

Windows 95, 98, NT4.0, 2000, or XP

Windows 98, Me, 2000, or XP

The main functions of the Configurator are illustrated below. For further details, refer to the

DeviceNet Configurator Operation Manual

(W382).

37

Outline of the Configurator

Section 1-5

Setup functions

Remote I/O master allocations (with creation of a scan list) and remote I/O slave allocations

Enabling or disabling master or slave function of CS/CJ-series

DeviceNet Unit.

Setting master device parameters except scan list parameters

(i.e., connection settings, device data checks, and communications cycle time)

Main functions of

Configurator

Setting other manufacturers' slave and master device parameters

Displaying a device information list

Monitoring functions

Storage functions

Monitoring master status, Unit status, Master error logs, and communications cycle data

Saving offline device information prepared with master device parameters or online network device information (Data is saved as network configuration files.)

Note

1.

2.

3.

4.

Master device parameters used in a scan list are created with either of the following methods.

a) Using the Parameter Wizard b) Setting all parameters

Connect only one Configurator to each Network.

Do not use the Configurator in a location with too much electromagnetic noise, particularly when using a PCMCIA Card. If noise is too extreme, the computer may run out-of-control, although there will be no negative effects on the DeviceNet network even if noise causes the computer to run out-ofcontrol.

The only DeviceNet masters that can be handled by the Configurator are

OMRON’s CS1W-DRM21(-V1), CJ1W-DRM21, CVM1-DRM21-V1, and

C200HW-DRM21-V1.

1-5-2 Configurator Specifications

Operating environment

Item

Hardware

OS

Network connection method

Dedicated

Board/Card

Network status

Connectable number of

Boards/Cards

Specification

Personal computer: IBM PC/AT or compatible

CPU: Pentium 166 MHz or higher (with Windows NT)

Memory: 32 Mbytes

Hard disk: A minimum of 15 Mbytes

Windows 95, 98, Me, NT4.0, 2000 or XP

Dedicated Board/Card 3G8F7-DRM21: Dedicated PCI Board

3G8E2-DRM21-V1: Dedicated PCMCIA Card

Serial connection (to

DeviceNet network with gateway)

• Peripheral or RS-232C port of PLC with DeviceNet

Unit mounted.

• RS-232C port of Serial Communications Board/Unit.

Serial communications mode: Peripheral bus or Host

Link

A single node address is used.

One/network

38

Outline of the Configurator

Section 1-5

Main functions

Item

Setup functions

Monitoring functions

Storage functions

Other functions

Files that can be written

Master device parameter settings for OMRON’s Master

• Remote I/O master allocations (with a scan list)

The node address order can be set as desired. Two output blocks and two input blocks can be allocated. (See note.)

• Remote I/O slave allocations

• Setting master remote I/O communications connections

• Setting slave remote I/O communications connections

• Enabling or disabling device data checks through remote I/O communications

(checks on slave vendor ID, device type, and product code data)

• Setting an explicit message monitor timer list

• Setting a COS/cyclic heart beat timer value

• Setting the communications cycle time

Note

Specification

1. A device Parameter Wizard is supported for the Master.

2. Using remote I/O master allocations eliminate restrictions on node addresses. Furthermore, a number of masters can be mounted to the PLC with no allocation area duplication.

Setting parameters for other manufacturers’ slaves (EDS file required).

Setting node addresses and baud rates

• Listing information on devices connected to the network (in node address order or remote I/O configuration order, for example)

• Monitoring Unit status data, Master function status data, and slave function status data

• Monitoring Master error history

CVM1-DRM21-V1 or C200HW-DRM21-V1: Up to 20 records of time, error code, and error condition data

CS1W-DRM21-V1 or CJ1W-DRM21: Up to 96 records of time, error code, and error condition data

• Monitoring communication cycle time

Saving offline device information prepared with master device parameters or online network device information. Such data is saved as network configuration files.

• Reading/writing and preparing EDS files

• Checking for duplicate I/O allocations in master parameters

• Printing master/slave device parameters

• Installing Expansion Modules to expand functions

• Master parameter files (parameters for OMRON Master: 1 file per node)

Note

Slave communications are saved as well in the master device parameters file with the DeviceNet Unit.

• Slave device parameter files (parameters for slaves: 1 file per node)

• Network file (all master/slave parameters for masters/slaves in the device list: 1 file/ network)

• EDS file (DeviceNet device definition file: 1 file/device type)

39

Basic Operating Procedures

Section 1-6

1-6

1-6-1

Basic Operating Procedures

Network Installation Procedure

Note

For details on the network installation procedure, refer to the

DeviceNet Operation Manual

(

W267

). Only a general description is given here.

(1)

Determine a suitable baud rate for the system.

(2)

Determine the node arrangement, the wiring configuration, and the cable lengths.

A) Restrictions on lengths of trunk lines and branch lines and total drop line length. (Selection of thick cables or thin cables)

B) Separation from noise sources.

Check

Do (1) and (2) above meet the

DeviceNet specifications?

(3)

Yes

Determine the method for providing a communications power supply.

(4)

Arrange for the required devices.

No

Delivery of devices.

1-6-2

(5)

Installation

Hardware Preparations for Communications

1,2,3...

1.

2.

Set the initial settings for the DeviceNet Unit:

Unit No. (UNIT No.)

Node address (NODE ADR)

Baud rate (DIP switches 1 to 2)

Communications continue/stop setting for communications errors (DIP switch pin 3)(with Master communications)

I/O hold/clear for communications errors (DIP switch pin 4)(with Slave communications)

Set the initial settings for slaves:

40

Basic Operating Procedures

Section 1-6

Note

3.

4.

5.

Node address (Pins 1 to 6)

Baud rate (Pins 7 and 8)

Etc.

Mount the Master and wire the network.

Treat as a CPU Bus Unit.

Can mount to a CPU Rack or Expansion Rack.

With fixed allocations: 3 Units max.

With user-set allocations: 16 Units max.

Connect a Programming Device to the PLC and turn ON the power supply to the PLC.

Generate the I/O tables.

1.

2.

A slave may not go online if the communications power supply is turned

ON after the slave is turned ON.

The communications power supply and slave power supply, the slave power supply and PLC power supply, or all three of these power supplies may be turned ON simultaneously.

1-6-3 Creating Routing Tables

The DeviceNet Unit functions as a Communications Unit in the same way as a

SYSMAC LINK Unit, Controller Link Unit, and Ethernet Unit.

It is therefore necessary to create routing tables for the communications functions to be used, as shown in the table below.

Mounted Units

DeviceNet Unit is the only Communications Unit mounted

Multiple DeviceNet

Units mounted as

Communications

Units

DeviceNet Unit and other Communications Unit mounted simultaneously

Using master or slave functions only

Using explicit message communications

(not supported across networks)

Not necessary (See note 1.)

Not necessary (See note 1.)

Local network table necessary (See note 2.)

Local network table necessary (See note 2.)

Using FINS message communications not across networks

Using FINS message communications across networks

Local network table (see note 2.) and relay network table are necessary.

Note

Note

1.

2.

If a local network table already exists in the CPU unit being used, the DeviceNet Unit must be registered in that table.

The DeviceNet Unit must be registered in the local network table.

Refer to

6-3 Using FINS Message Communications

for information on the

routing tables.

The routing tables are created using CX-Net inside the CX-Programmer.

Refer to the

CX-Programmer Operation Manual

(WS02-CXPC1-EV50)

(W446) for details.

1.

2.

A local network table is sometimes necessary even when the DeviceNet

Unit is not operating across networks.

If you prepare a local network table inside the CPU Unit, be sure to register the DeviceNet Unit.

41

Basic Operating Procedures

Section 1-6

3.

Even if a local network table exists inside the CPU Unit, the 7-segment display of the DeviceNet Unit may indicate “HC” and FINS message/explicit message communications may not be possible unless the DeviceNet Unit is registered in the local network table.

Procedures Prior to Starting Communications 1-6-4

Using the Master Function

To use the master function, the Master Enable Switch (word n, bit 06) must be turned ON from a Programming Device. Enable master communications through CS1W-DRM21(-V1) properties if you are using a Configurator.

Note

1.

2.

Make sure the scan list is enabled when using the master function. This will allow you to check whether slaves are online or not from the CPU Unit so that you will be able to determine whether or not the DeviceNet is communicating properly.

Remote I/O communications with a specified slave can be turned OFF

(disconnected) by turning ON (1) the corresponding Disconnect/Connect

Switch (words n+6 to n+9) when a slave is replaced or is registered in the scan list prior to being connected. These switches are cleared when the power supply is turned OFF, however, so a bit must be turned back ON (1) from the ladder program when the power turns ON for it to be valid again.

Fixed Allocations

Use the following procedure to use fixed allocations. Refer to

4-3 Fixed Allocations

for details on fixed allocations.

1,2,3...

1.

2.

3.

4.

5.

6.

Turn ON the communications, slave, and PLC power supplies.

Note

Turn ON the communications power supply before turning ON the slave power supplies or the slaves may not go online.

Switch the CPU Unit to PROGRAM mode.

Check Unit Status 2 (word n+11, bit 03) from a Programming Device connected to the CPU Unit to see if the master function is ON (enabled). If it is enabled, skip step 4 below and proceed to step 5.

If the master function is OFF (disabled), turn ON the Master Enable Switch

(word n, bit 06) from a Programming Device connected to the CPU Unit.

Note

Execute this only when master communications are turned OFF. (If the Master Enable Switch is turned ON when master communications are ON, a Unit error will occur and a C2 error will be displayed on the 7-segment display on the front panel.)

Turn ON the Master Fixed Allocation Area Setting 1 to 3 Switches (word n, bits 8 to 10). Master remote I/O communications will begin with the scan list disabled.

Turn ON the Scan List Enable Switch (word n, bit 00). Master remote I/O communications will begin with the scan list enabled.

Switch the CPU Unit to RUN mode.

7.

User-set Allocations Using Allocated DM Area Words

Use the following procedure to set allocations using the words allocated to the

Unit in the DM Area. Refer to

4-4 User-set Allocations

for details on user-set

allocations.

1,2,3...

1.

Turn ON the communications, slave, and PLC power supplies.

Note

Turn ON the communications power supply before turning ON the slave power supplies or the slaves may not go online.

42

Basic Operating Procedures

Section 1-6

2.

3.

4.

5.

6.

Switch the CPU Unit to PROGRAM mode.

Check Unit Status 2 (word n+11, bit 03) from a Programming Device connected to the CPU Unit to see if the master function is ON (enabled). If it is enabled, skip step 4 below and proceed to step 5.

If the master function is OFF (disabled), turn ON the Master Enable Switch

(word n, bit 06) from a Programming Device connected to the CPU Unit.

Note

Execute this only when master communications are turned OFF. (If the Master Enable Switch is turned ON when master communications are enabled, a Unit error will occur and a C2 error will be displayed on the 7-segment display on the front panel.)

Input data in advance into the Master User Allocation Setup Table (words m+1 to m+6) and the Allocation Size Setup Table (specify the position in words m+5 and m+6)

Turn ON the Master User-set Allocation Switch (word n, bit 11). Master remote I/O communications will begin with the scan list enabled.

Switch the CPU Unit to RUN mode.

7.

User-set Allocations Using the Configurator

Use the following procedure to set allocations using the Configurator. Refer to

DeviceNet Configurator Operation Manual

for details on Configurator operating procedures

1,2,3...

1.

2.

3.

4.

5.

Turn ON the communications, slave, and PLC power supplies.

Note

Turn ON the communications power supply before turning ON the slave power supplies or the slaves may not go online.

Switch the CPU Unit to PROGRAM mode.

Create a network configuration file and device parameters file from the

Configurator. (Enable master communications in CS1W-DRM21(-V1) properties at this time.)

Download the above files to the devices on the network. Remote I/O communications will begin with the scan list enabled.

Switch the CPU Unit to RUN mode.

Using Slave Function

To use the slave function, the Slave Enable Switch (word n+1, bit 06) must be turned ON from a Programming Device. Enable slave communications through CS1W-DRM21(-V1)/CJ1W-DRM21 properties if you are using a Configurator.

With fixed allocations or allocations set in the allocated DM Area words, slave communications must be disabled prior to area allocation and must be enabled following area allocation. The order of the procedure is thus Slave

Stop Switch (if slave communications are enabled), area allocation, and Slave

Enable Switch.

Note

Slave communications must be disabled prior to area allocation when using fixed allocations or allocations set in the allocated DM Area words, and the settings must be read to the Unit when slave communications are enabled.

Allocations will not be valid if slave communications are enabled during area allocation.

Fixed Allocations

Use the following procedure to use fixed allocations. Refer to

5-2 Fixed Allocations

for details on fixed allocations.

43

Basic Operating Procedures

Section 1-6

1,2,3...

1.

2.

3.

4.

5.

6.

Switch the CPU Unit to PROGRAM mode.

Check Unit Status 2 (word n+11, bit 07) from a Programming Device connected to the CPU Unit to see if the slave function is OFF (disabled). If it is disabled, skip step 3 below and proceed to step 4.

If slave communications are enabled, turn ON the Slave Stop Switch (word n+1, bit 07).

Turn ON the Slave Fixed Allocation Area Settings 1 to 3 Switches (word n+1, bits 8 to 10).

Turn ON the Slave Enable Switch (word n+1, bit 06) from a Programming

Device connected to the CPU Unit.

Note

Execute this only when slave communications are turned OFF. (If the

Slave Enable Switch is turned ON when slave communications are enabled, a Unit error will occur and a C2 error will be displayed on the 7-segment display on the front panel.)

Switch the CPU Unit to RUN mode. Slave remote I/O communications will begin.

User-set Allocations Using Allocated DM Area Words

Use the following procedure to set allocations using the words allocated to the

Unit in the DM Area. Refer to

5-3 User-set Allocations

for details on user-set allocations.

1,2,3...

1.

2.

3.

4.

5.

6.

7.

Switch the CPU UNit to PROGRAM mode.

Check Unit Status 2 (word n+11, bit 07) from a Programming Device connected to the CPU Unit to see if the slave function is OFF (disabled). If it is disabled, skip step 3 below and proceed to step 4.

If Slave is enabled, turn ON the Slave Stop Switch (word n+1, bit 07).

Input data in advance into the Slave User Allocation Setup Table (words m+8 to m+13).

Turn ON the user Slave User-set Allocation Switch (word n+1, bit 11).

Turn ON the Slave Enable Switch (word n+1, bit 06) from a Programming

Device connected to the CPU Unit.

Note

Execute this only when slave communications are turned OFF. (If the

Slave Enable Switch is turned ON when slave communications are enabled, a Unit error will occur and a C2 error will be displayed on the 7-segment display on the front panel.)

Switch the CPU Unit to RUN mode. Slave remote I/O communications will begin.

User-set Allocations Using the Configurator

Use the following procedure to set allocations using the Configurator. Refer to

DeviceNet Configurator Operation Manual

for details on Configurator operating procedures

1,2,3...

1.

2.

3.

Switch the CPU Unit to PROGRAM mode.

Create a device parameter file from the Configurator. (Enable Slave communications in CS1W-DRM21(-V1) properties at this time.) Then download the file to the DeviceNet Unit.

Turn ON the Slave Enable Switch (word n+1, bit 06) from a Programming

Device connected to the CPU Unit.

Note

Execute this only when slave communications are turned OFF. (If the

Slave Enable Switch is turned ON when slave communications are

44

Basic Operating Procedures

Section 1-6

4.

enabled, a Unit error will occur and a C2 error will be displayed on the 7-segment display on the front panel.)

Switch the CPU Unit to RUN mode. Slave remote I/O communications will begin.

Message Communications Only (Neither Master nor Slave Function Used)

The DeviceNet Unit does not have to be registered in the scan list if it is only used for message communications. Message communications (send and receive) can be executed with both master and slave communications disabled.

45

List of Usage Methods by Purpose

Section 1-7

1-7

Design

List of Usage Methods by Purpose

Situation

Allocating any words for remote I/O

In order of node addresses

Not in order of node addresses

Using the Unit as a slave

Action

Set using the allocated DM Area words.

(Master User Allocations Setup Table and Allocation Size Setup Table)

Note

Allocations using allocated DM Area words:

Order of node addresses and two blocks,

OUT 1 and IN 1.

112

Set using the configurator.

Note

Allocations using Configurator: Any node address order and four blocks, OUT 1, IN 1,

OUT 2 and IN 2. Allocation is much easier using a wizard.

Set using the allocated DM Area words.

117

126

Performing message communications between PLCs to which

DeviceNet Units are mounted

Mounting multiple DeviceNet

Units using master communications to a single PLC

Mounting multiple DeviceNet

Units using slave communications to a single PLC

Connecting multiple PLCs (master communications) in a network

Execute communications instructions from the user program.

3 Units max. with fixed allocations

16 Units max. with user-set allocations

3 Units max. with fixed allocations

16 Units max. with user-set allocations

Connecting a single Master PLC and multiple Slave PLCs in a network

Sending DeviceNet explicit messages

Supported by user-set allocations using allocated

DM Area words or user-set allocations using the

Configurator.

Set multiple PLCs to Slave mode from the allocated DM Area words or the Configurator.

Note

Up to 64 Units may be on a network.

(Example: 1 Master PLC and 63 Slave

PLCs)

Set the FINS command code to 2801.

138

96

126

126

126

142

Setting the node address for a

DeviceNet Unit

Setting the baud rate for the

DeviceNet Unit

Stopping remote I/O communications for communications errors

Holding OUT data in slave I/O memory for communications errors

Set the rotary switches on the front of the

DeviceNet Unit.

Set the DIP switch on the front of the DeviceNet

Unit.

Set the DIP switch on the front of the DeviceNet

Unit.

Set the DIP switch on the front of the DeviceNet

Unit.

53

54

55

55

Page

46

List of Usage Methods by Purpose

Operation

Section 1-7

Situation

Stopping remote I/O communications with all Slaves

Using a scan list in remote I/O communications (fixed allocations)

Enabling a scan list in remote I/O communications (user-set allocations by allocated DM Area words)

Changing the communications system configuration

Action

Stop communications using the Configurator or the

Remote I/O Communications Stop Switch in the allocated CIO Area words.

Turn ON the Scan List Enable Switch in the allocated CIO Area words.

66

65

Set the allocation areas using the allocated DM

Area words, and turn ON the user-set allocations user setting switch for the allocated CIO Area words.

Turn ON the Scan List Clear Switch for the allocated CIO Area words, and turn the Scan List

Enable Switch back ON after you change the communications system.

Monitor the Master Status 2 status codes in the allocated CIO Area words from a Programming

Device.

68

104

78

Checking master I/O allocation status (fixed allocations, user-set allocations by allocated DM Area words, user-set allocations by the

Configurator)

Checking to see if all slaves are registered in the scan list

Checking to see if all slaves are performing remote I/O communications properly

Checking to see if there is an error history in the DeviceNet

Unit

Monitoring the error history in the

DeviceNet Unit

Monitoring status of the

DeviceNet Unit

Checking the current communications cycle time

Adjusting the communications cycle time

Saving all parameters, like scan list data, for masters and slaves on the network

Replacing a DeviceNet Unit

Check the Registered Slave Table in the allocated

CIO Area words.

Check the Normal Slave Table in the allocated CIO

Area words.

Check the error history (registration yes/no) in the allocated CIO Area words from a Programming

Device.

Execute the device monitor function from the Configurator (Error History Tab).

Execute the device monitor function from the Configurator (Status and Unit Status Tabs).

Execute the device monitor function from the Configurator (Current Communications Cycle Time

Tab).

Execute the device parameter edit function from the Configurator (Communications Cycle Time

Tab).

Save the network configuration from the Configurator.

81

82

76

Page

DeviceNet Configurator Operation Manual

1. Insert a Memory Card in the CPU Unit and turn

ON the Unit Setup File Backup Switch in the allocated CIO Area words.

2. Replace the DeviceNet Unit.

3. Turn ON the Unit Setup File List Switch in the allocated CIO Area words.

4. Turn ON Scan List Clear Switch in the allocated

CIO Area words.

5. Make sure the slave is connected, and then turn

ON the Scan List Enable Switch.

232

47

List of Usage Methods by Purpose

Section 1-7

48

SECTION 2

Nomenclature and Installation

This section describes the nomenclature and installation of the DeviceNet Unit.

2-1

2-2

Nomenclature and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-1-1

2-1-2

Nomenclature and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Status Indicators: MS and NS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-1-3

2-1-4

Seven-Segment Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Switch Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Installing the DeviceNet Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-2-1 System Configuration Precautions . . . . . . . . . . . . . . . . . . . . . . . . . .

2-2-2

2-2-3

2-2-4

Mounting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Handling Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

External Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

52

53

55

55

50

50

51

56

57

59

49

Nomenclature and Functions

Section 2-1

2-1 Nomenclature and Functions

2-1-1 Nomenclature and Functions

CS1W-DRM21(-V1)

DRM21

MS

NS

CS

Indicators

UNIT

No.

3210

FEDC

BA987

NODE

ADR 10

654

987

X10

1

10

654

987

X10

0

1

2

3

4

DR0

DR1

ESTP

HOLD

ON

Unit No. switch

This switch sets the unit number of the DeviceNet Unit as a one-digit hexadecimal value.

Node address switches

These switches set the node address as a two-digit decimal value.

DIP switch

The pins have the following functions:

Pins 1 and 2: Baud rate

Pin 3: Continue/Stop communications for error

(when used as a Master)

Pin 4: Hold/clear I/O for communications error

(when used as a Slave)

Communications connector

Connect the Network communications cable to this connector. The communications power for this Unit is also supplied through this connector.

A parallel connector with screws (XW4B-05C1-H1-D) is provided for node connection.

CJ1W-DRM21

1,2,3...

DRM21

MS

NS

12

34

9

678 x10

1

9

678

NODE

ADR x10

0

ON

2

1

4 HOLD

3

ESTP

DR1

DR0

Indicators

Unit No. switch

This switch sets the unit number of the DeviceNet Unit as a onedigit hexadecimal value.

Node address switches

These switches set the node address as a two-digit decimal value.

DIP switch

The pins have the following functions:

Pins 1 and 2: Baud rate

Pin 3: Continue/Stop communications for error (when used as a

Master)

Pin 4: Hold/clear I/O for communications error (when used as a

Slave)

Communications connector

Connect the Network communications cable to this connector. The communications power for this Unit is also supplied through this connector.

A parallel connector with screws (XW4B-O5C1-H1-D) is provided for node connection.

Indicators

The DeviceNet Units are equipped with the following indicators that indicate the operating status of the node itself and the overall network.

1.

2.

3.

Two status indicators (two-color: Green or red LEDs)

A two-digit, 7-segment display

Two dot indicators

50

Nomenclature and Functions

Section 2-1

2. Two-digit, 7-segment display

MS

1. Status indicators

NS

3. Dot indicators

2-1-2 Status Indicators: MS and NS

The MS (Module Status) indicator indicates the status of the node itself and the NS (Network Status) indicator indicates the status of the network.

The MS and NS indicators can be green or red and they can be OFF, ON, or flashing (alternating 0.5-s ON and 0.5-s OFF.) The following table shows the meaning of these indicator conditions.

Indicator

MS

Color

Green

Status

ON

Meaning (likely errors)

NS

Red

---

Green

Red

---

ON

Flashing

OFF

ON

Flashing

ON

Flashing

OFF

Normal operating status

Communications are being performed normally.

A non-recoverable, fatal error has occurred.

(Watchdog timer error, memory error, or system error.)

Replace the DeviceNet Unit.

A recoverable, non-fatal error has occurred. (Structure error, switch setting error, PLC initialization error, PLC interface error, or routing table error.)

Correct the error and reset the Unit.

Power isn’t being supplied or the Unit is being reset.

The Unit is online with the network and remote I/O communications have been established with a slave registered in the scan list or message communications have been established.

The Unit is online with the network, but neither remote

I/O communications nor message communications have been established. Either the scan list is being read, or both remote I/O communications and message communications are disabled.

A fatal communications error has occurred. Network communications are not possible.

(Node address duplicated or Bus Off error)

A non-fatal communications error has occurred. (Communications error, setup error, or verification error)

The Unit is not online with the network.

(There is no network power supply, the Unit is being reset, a minor failure, or a sending error has occurred.)

51

Nomenclature and Functions

2-1-3

Section 2-1

Seven-Segment Display

In addition to the MS and NS indicators, DeviceNet Units have a 2-digit, 7segment display that normally indicates the master node address. When an error occurs, the display will alternate between the error code and the node address of the faulty slave.

There are dot indicators at the lower-right corner of each digit. The left dot indicator shows whether or not the master is operating and whether the scan list is enabled or disabled. The right dot indicator shows whether or not the slave is operating.

Normal: Master Unit's node address

Error: Error code and faulty node address

Indicates whether the slave is operating or stopped.

Indicates whether the master is operating or stopped and whether the scan list is enabled or disabled.

Seven-segment Digits

The following table shows the functions of the 7-segment digits.

Status

Remote I/O communications active and normal

From power ON to completion of node address check (master function disabled, slave function disabled, or both disabled)

Remote I/O communications started

Display

Displays the master’s node address

(00 to 63)

Lit

Flashing

Flashing (until communications actually start)

Flashing From completion of the node address check until the start of remote I/O communications

Error Watchdog timer

Memory error or system error

Other errors

Not lit

Error code only Lit

Scan list Reading

Registered

Alternately displays the error code and error node address (see diagram below)

“- -” Flashing

52

Nomenclature and Functions

Section 2-1

Error code

(1 s)

OFF (0.1 s)

The following diagram shows the alternating error code/ node address display.

Faulty slave's node address

(1 s)

OFF (0.3 s)

Error code

(1 s)

OFF (0.1 s)

Faulty slave's node address

(1 s)

OFF (0.3 s)

OFF (0.3 s)

Master's node address (1 s)

OFF (0.1 s)

Master's error code (1 s)

OFF (0.3 s)

If there is an error at the DeviceNet Unit.

The master’s error code and master’s node address will be displayed if an error has occurred at the master.

There is no priority in the error codes; all errors that have occurred will be displayed in order. All error codes begin with letters, so they can be distinguished from node addresses immediately.

Dot Indicators

The following table shows the functions of the dot indicators.

Indicator

Left dot

Right dot

Content

Scan list enabled/ disabled, master function disabled

Slave function disabled

Display

ON: Master function disabled

Flashing: Scan list disabled mode

OFF: Scan list enabled mode

ON: Slave function disabled

OFF: Slave operating

2-1-4 Switch Settings

Unit No. Switch

CS1W-DRM21(-V1) CJ1W-DRM21

654

3210

BA987

FEDC

01

23

CDE

4567

89

AB

Use this switch to set the unit number of the DeviceNet Unit as a CPU Bus

Unit. The unit number setting determines the CIO and DM area words allocated to the Unit as software switches and the status area.

Setting method: One-digit hexadecimal

Setting range: 0 to F

Note

1.

2.

3.

4.

5.

The unit number is set to 0 at the factory.

Any unit number from 0 to F can be set as long as it hasn’t been set on another CPU Bus Unit connected to the same PLC.

Use a small flat-blade screwdriver to turn the rotary switches; be careful not to damage the switch.

Always turn OFF the PLC before changing the unit number setting.

If the unit number is the same as one set on another CPU Bus Unit connected to the same PLC, a duplicate number error will occur in the PLC and it won’t be possible to start up the DeviceNet network.

Node Address Switches

Use these switches to set the node address of the Unit.

CS1W-DRM21(-V1)

10

654

987

X10

1

10

654

987

X10

0

CJ1W-DRM21

9

12

34

678

X

10

1

9

12

34

678

Setting method: Two-digit decimal

X

10

0

Setting range: 0 to 63

53

Nomenclature and Functions

DIP Switch

Note

Note

Section 2-1

1.

2.

3.

4.

The node address is set to 63 at the factory.

Any node address from 0 through 63 can be set as long as it hasn’t been set on another slave node.

If the node address is the same as one set on another node, a node address duplication error will occur and it won’t be possible to start up network communications.

Node address 0 cannot be used for FINS message communication. Use a node address other than 0 for FINS message communication.

The DIP switch on the front of the DeviceNet Unit is used to set the baud rate, whether communications will be continued or stopped when a communications error occurs, and whether to hold or clear the remote outputs when a communications error occurs in the slave function.

CS1W-DRM21(-V1)

Baud rate

Continue/stop communications for communications error (when used as a master)

Hold/clear I/O for communications error (when used as a slave)

ON

CJ1W-DRM21

ON

Hold/clear I/O for communications error (when used as a slave)

Continue/stop communications for communications error (when used as a master)

Baud rate

The settings of the DIP switch pins are shown in the following table. All pins are set to OFF at the factory.

1

2

3

Pin

Baud rate

Function Setting

See the next table.

4

Continue/stop remote I/O communications for communication errors (when used as a master)

Hold/clear remote outputs for communications error (when used as a slave)

OFF:

ON:

Clear remote outputs

Hold remote outputs

Baud Rate

Pins 1 and 2 are used to set the baud rate as shown in the following table.

Baud rate Pin 1

OFF

ON

OFF

ON

Pin 2

OFF

OFF

ON

ON

125 kbps

250 kbps

500 kbps

Not allowed.

1.

2.

Always turn OFF the PLC before changing the DIP switch settings.

Set the same baud rate on all of the nodes (Master and Slaves) in the Network. Any slaves with baud rates different from the master’s rate won’t be able to participate in communications and may cause a communications error between nodes that have been set properly.

54

Installing the DeviceNet Unit

Communications

Connectors

Section 2-2

Continue/Stop Remote I/O Communications

When the DeviceNet Unit is used as a master, pin 3 is used to set whether or not communications will stop after a communications error.

Pin 3

OFF

ON

Continue communications.

Stop communications.

Function

If pin 3 is ON, remote I/O communications will be stopped if one of the following errors occurs.

Remote I/O Communications Error Flag (n+12, bit 02 is ON)

Send Timeout Flag (n+10, bit 08 is ON)

Network Power Error Flag (n+10, bit 07 is ON)

Remote I/O communications will remain stopped even if the error is cleared.

(Message communications and slave functions will continue.) To resume communications, turn ON the Remote I/O Communications Start Bit (word n, bit

02) of Software Switches 1. Refer to

3-2 Allocated CIO Area Words

for details.

Note

The 7-segment display will show “A0” when remote I/O communications stop.

Refer to

SECTION 9 Troubleshooting and Maintenance.

If pin 3 is OFF, remote I/O communications will stop if a send timeout or network power error occurs, but will restart automatically when the cause of the error is cleared.

Hold/Clear Remote Outputs

When the DeviceNet Unit is used as a slave, pin 4 is used to set whether to hold or clear remote outputs when a communications error occurs.

Note

If the DeviceNet Unit is used as a slave, the 7-segment display will show “L9” when remote I/O communications stop. Refer to

SECTION 9 Troubleshooting and Maintenance.

Color stickers that match communications cable colors are attached to the communications connectors. Match the colors when connecting communications cables to the connectors. These colors are given in the following table

Color

Black

Blue

---

White

Red

Signal

Power line, negative voltage (V–)

Communications line, low (CAN L)

Shield

Communications line, high (CAN H)

Power line, positive voltage (V+)

For details on communications specifications and wiring, refer to

DeviceNet

(CompoBus/D) Operation Manual

(W267).

Note

Before connecting communications cables, turn OFF the PLC power supply, all slave power supplies, and the communications power supply.

2-2

2-2-1

Installing the DeviceNet Unit

System Configuration Precautions

• I/O words are allocated to CPU Bus Units according to the unit number setting on the switch located on the front panel of the Unit, not according to Unit slot numbers. Refer to

3-1 Overview of Word Allocations.

55

Installing the DeviceNet Unit

Section 2-2

• In the CS-series, up to 16 Units can be mounted to the CS1W-BC @@ 3

CPU Backplane or CS1W-BI @@ 3 Expansion CPU Backplane.

• In the CJ-series, up to 16 Units can be mounted to the CPU Unit or

Expansion Unit (but no more than 10 Units on either).

2-2-2 Mounting

1,2,3...

CS-series

Mount the DeviceNet Unit to the Backplane using the following procedure.

1.

Hook the claw on the bottom of the Unit onto the Backplane.

Claw

Backplane

2.

3.

Insert the Unit into Backplane connectors and securely tighten the screw at the bottom of the Unit. Tighten the screws to a torque of 0.4 N·m.

When removing the Unit, first loosen the screw at the bottom of the Unit.

Fixing screws

56

Installing the DeviceNet Unit

Section 2-2

Note

When mounting the Unit, provide the clearance shown below to facilitate easy mounting or dismounting.

Duct

20 mm min.

Backplane

20 mm min.

Duct

Phillips screwdriver

CJ-series

1.

Carefully align the connectors to mount the DeviceNet Unit.

Connectors

PA205R

POWER

PROGRAMMABLE

CONTROLLER

OPEN

RUN

INH

PRPHL

COMM

DRM21

MS

NS

AC100-240V

L1

L2/N

4

PERIPHERAL

RUN

OUTPUT

AC240V

DC24V

PORT

2.

Move the yellow sliders on the top and bottom of the Unit until they click into position, to lock.

Slider

2-2-3

PA205R

POWER

Release

Lock

PROGRAMMABLE

CONTROLLER

OPEN

RUN

INH

PRPHL

COMM

BUSY

DRM21

MS

AC100-240V

L1

L2/N

ON

4

PERIPHERAL

RUN

OUTPUT

DC24V

PORT

Note

If the sliders are not securely locked, the DeviceNet Unit functions may not operate sufficiently.

To dismount the Unit, move the sliders to the “Release” direction.

Handling Precautions

• Always turn OFF the power supply to the PLC before mounting or dismounting a Unit or connecting or disconnecting cables.

57

Installing the DeviceNet Unit

Section 2-2

• Provide separate conduits or ducts for the I/O lines to prevent noise from high-tension lines or power lines.

• Leave the label attached to the Unit when wiring. Removing the label may result in malfunction if foreign matter enters the Unit.

• Remove the label after the completion of wiring to ensure proper heat dissipation. Leaving the label attached may result in malfunction.

CS1W-DRM21(-V1)

Remove the label after wiring.

CJ1W-DRM21

4 HOLD

3

ESTP

2 DR1

1 DR0

MS

Remove the label after wiring.

58

Installing the DeviceNet Unit

2-2-4 External Dimensions

CS1W-DRM21(-V1)

35

DRM21

130

UNIT

No.

3210

FEDC

NODE

ADR 10

654

987

X10

1

10

654

987

X10

0

1

2

3

4

DR0

DR1

ESTP

HOLD

ON

88

13.7

101

Section 2-2

35

7

12 15 8

These diagrams show the dimensions of the DeviceNet Unit. Refer to the

CS1

Series CPU Unit Operation Manual

(W339) or the

CJ Series CPU Unit Operation Manual

(W393) for the dimensions of the Unit when it is mounted to the

Backplane. (All dimensions are in mm.)

CJ1W-DRM21

31

13.7

65

MS

NS

UNIT

NO.

1

50

ON

90

3

2

4 HOLD

ESTP

DR1

1 DR0

35

5

11 15 5

59

Installing the DeviceNet Unit

Section 2-2

60

SECTION 3

Allocated CIO and DM Words

This section describes the words allocated to the DeviceNet Unit in the CIO Area and DM Area. These words both enable controlling the DeviceNet Unit and accessing Unit and network status.

3-1

3-2

3-3

3-2-4

3-2-5

3-2-6

3-2-7

3-2-8

3-2-9

3-2-10

3-2-11

Overview of Word Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-1-1

3-1-2

Allocated CIO Area Words. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Allocated DM Area Words . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Allocated CIO Area Words . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-2-1 Software Switches 1 (Word n) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-2-2

3-2-3

Software Switches 2 (Word n+1) . . . . . . . . . . . . . . . . . . . . . . . . . . .

Master COS Send Switches (Words n+2 to n+5) . . . . . . . . . . . . . . .

Disconnect/Connect Switches (Words n+6 to n+9) . . . . . . . . . . . . .

Unit Status 1 (Word n+10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Unit Status 2 (Word n+11) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Master Status 1 (Word n+12) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Master Status 2 (Word n+13) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Slave Status 1 (Word n+14) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Slave Status 2 (Word n+15) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Registered Slave Table (Words n+16 to n+19) . . . . . . . . . . . . . . . . .

3-2-12

3-2-13

Normal Slave Table (Words n+20 to n+23) . . . . . . . . . . . . . . . . . . .

C200H Master Replacement Master Status 1 (Word n+24) . . . . . . .

Allocated DM Area Words . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-3-1 Communications Cycle Time Setup Table . . . . . . . . . . . . . . . . . . . .

3-3-2

3-3-3

3-3-4

3-3-5

Master User Allocations Setup Table . . . . . . . . . . . . . . . . . . . . . . . .

Allocation Size Setup Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Slave User Allocations Setup Table . . . . . . . . . . . . . . . . . . . . . . . . .

Communications Cycle Time Reference Table . . . . . . . . . . . . . . . .

3-3-6

3-3-7

3-3-8

Master User-set Allocations Reference Table . . . . . . . . . . . . . . . . .

Slave User-set Allocations Reference Table. . . . . . . . . . . . . . . . . . .

Slave Detailed Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

85

87

88

90

82

82

84

84

90

91

92

78

79

81

81

73

74

75

77

64

64

69

72

62

63

63

61

Overview of Word Allocations

3-1

Section 3-1

Overview of Word Allocations

The words shown in the following diagram are allocated according to the unit number setting. For each Unit, there are 25 words allocated in the CIO Area and 100 words allocated in the DM Area.

First word allocated in the CIO Area: n = CIO 1,500 + (25 x unit number)

First word allocated in the DM Area: m = D30,000 + (100 x unit number)

CPU Unit

CPU Bus Unit

CIO Area

CIO 1500

CIO 1501

Software switches

DeviceNet Unit

Unit number: 0

Local memory

Unit #0 25 wds

(I/O refresh) status

25 wds

CIO 1524

CIO 1525

CIO 1526

Unit #1

25 wds

CIO 1549

Unit #15

Unit #0

Unit #1

CIO 1875

25 wds

CIO 1899

D30000

D30001

CPU Bus Unit

Allocated DM Area words setup tables

100 wds

(I/O refresh) status

D30099

D30100

D30101

100 wds

D30199

D31500

Unit #15

100 wds

D31599

Local memory

100 wds

Note

The CPU Bus Unit Setup words are not used with a CS/CJ-series DeviceNet

Unit.

62

Overview of Word Allocations

3-1-1

3-1-2

Section 3-1

Allocated CIO Area Words

Software switches, DeviceNet Unit status, and error data are allocated in the

CIO Area according to the unit number, as shown below. Software switches are bits used as commands from the CPU Unit to the DeviceNet Unit to enable executing Unit functions.

5

6

3

4

1

2

0

Unit number

7

Allocated words

CIO 1500 to CIO 1524

CIO 1525 to CIO 1549

CIO 1550 to CIO 1574

CIO 1575 to CIO 1599

CIO 1600 to CIO 1624

CIO 1625 to CIO 1649

CIO 1650 to CIO 1674

CIO 1675 to CIO 1699

11

12

13

14

8

Unit number

9

10

15

Allocated words

CIO 1700 to CIO 1724

CIO 1725 to CIO 1749

CIO 1750 to CIO 1774

CIO 1775 to CIO 1799

CIO 1800 to CIO 1824

CIO 1825 to CIO 1849

CIO 1850 to CIO 1874

CIO 1875 to CIO 1899

Allocated DM Area Words

The User Allocations Setup Tables and individual slave status by node address are allocated in the DM area.

4

5

2

3

6

7

0

Unit number

1

Allocated words

D30000 to D30099

D30100 to D30199

D30200 to D30299

D30300 to D30399

D30400 to D30499

D30500 to D30599

D30600 to D30699

D30700 to D30799

10

11

12

13

8

Unit number

9

14

15

Allocated words

D30800 to D30899

D30900 to D30999

D31000 to D31099

D31100 to D31199

D31200 to D31299

D31300 to D31399

D31400 to D31499

D31500 to D31599

63

Allocated CIO Area Words

3-2

Section 3-2

Allocated CIO Area Words

Data is stored at the offset positions shown in the figure below starting from the first word allocated to the Unit in the CIO Area.

The first word can be calculated as follows from the unit number setting:

First word n = CIO 1,500 + (25 x unit number) n+10 n+11 n+12 n+13 n+14 n+15 n+16 n+17 n+18 n+19 n+20 n+21 n+22 n+23 n+24

Word n n+1 n+2

Bit 15 n+3 n+4 n+5 n+6 n+7 n+8 n+9

Software Switches 1

Software Switches 2

Master COS Send Switches (4 words)

Disconnect/Connect Switches (4 words)

Unit Status 1

Unit Status 2

Master Status 1

Master Status 2

Slave Status 1

Slave Status 1

Registered Slave Table (4 words)

Normal Slave Table (4 words)

C200H Master Replacement Status (1)

Bit 00 Direction

I/O

CPU Unit

DeviceNet Unit

Outputs

CPU Unit

DeviceNet Unit

Inputs

CPU Unit

DeviceNet Unit

3-2-1 Software Switches 1 (Word n)

All switches execute some function when the user turns them ON. They turn

OFF automatically after the function has been executed. Once a function is set by turning a switch ON (except for the switches listed below), it is saved regardless of whether the power is turned OFF and ON again.

Remote I/O Communications Start Switch (bit 02, 03)

Remote I/O Communications Stop Switch (bit 04)

Note

No functions other than master and slave communications are disabled by stopping master or slave communications.

If multiple bits are turned ON simultaneously, the requests will generate errors but they will not alter Unit operation. The corresponding error bits in the following words will turn ON if a request made by a software switch ends in an error.

64

Allocated CIO Area Words

Section 3-2

• Unit status area 2 (word n+11)

• Master Status 1 (word n+12)

Word n [n = CIO 1,500 + (25 x unit number)]

Bit

00

01

Name

Scan List

Enable

Switch

Scan List

Clear

Switch

Status

OFF

ON

OFF

OFF

ON

OFF

Controlled by

User

Unit

User

Unit

Unit operation

Enables the scan list with fixed allocations.

Note

The allocated words are the ones set for use when with the scan list is disabled.

The following allocated words are the default settings when the scan list is disabled.

• OUT area: CIO 3200 to CIO 3263 (1 word/1 node address)

• IN area: CIO 3300 to CIO 3363 (1 word/1 node address)

Returns to OFF when the scan list is registered and the

Unit starts operating with the scan list enabled.

Clears and disables the scan list.

This switch clears the scan list and operates the Unit using fixed allocations with the scan list disabled regardless of the previous operation settings. The fixed allocations used the last time the scan list was disabled will be used.

Returns to OFF when the scan list data is cleared and the Unit starts operating with the scan list disabled.

Operation conditions

CPU

Unit operating mode

Master function

Program mode

Enabled

Scan list status

Disabled

Default setting

Scan list disabled

Program mode

Enabled

Enabled

Scan list disabled

65

Allocated CIO Area Words

Section 3-2

Bit

02

03

04

05

Name

Remote

I/O Communications Start

Switch

Remote I/O

Communications

Start

Switch

OFF

ON

OFF

Remote

I/O Communications Stop

Switch

OFF

ON

Reserved by system

Status

OFF

ON

OFF

OFF

---

Controlled by

User

Unit

User

Unit

User

Unit

---

Unit operation

Starts remote I/O communications.

Note

1. The switch is ignored if remote I/O communications are already running.

2. This switch is used to restart remote I/O communications if they are stopped by a communications error.

3. Communications with a slave will fail even if remote I/O communications are started if the Disconnect/Connect Switch (corresponding bit in words n+6 to 9) is ON (1:

Connect).

Returns to OFF at the start of remote I/O communications.

Note

This switch will stop remote I/O communications if DIP switch pin 3 on the front panel (remote I/O communications start/stop with a communications error) is ON (stop) and there is an ongoing communications or send error.

This switch functions the same as bit 02 above.

Note

This switch is used to ensure compatibility between the software switches and C200H

DeviceNet Master (C200HW-DRM21-V1).

Stops remote I/O communications.

Once remote I/O communications have been stopped, they will remain stopped until the Unit has been restarted or the remote I/O communications have been restarted (i.e., until the Remote I/O Communications

Start Switch is turned ON).

Note

1. The switch is ignored if remote I/O communications are already stopped.

2. Message communications will remain enabled even if remote I/O communications have stopped.

Returns to OFF when remote I/O communications stop.

---

Operation conditions

CPU

Unit operating mode

Master function

Scan list status

--Enabled

---

Default setting

None

---

---

---

Enabled

Enabled

---

---

---

-----

66

Allocated CIO Area Words

Section 3-2

Bit

06

07

08

09

10

Name

Master

Enable

Switch

Master

Stop

Switch

Master

Fixed

Allocation Setting 1

Switch

Master

Fixed

Allocation

Setting 2

Switch

Master

Fixed

Allocation Setting 3

Switch

Status

OFF

ON

OFF

OFF

ON

OFF

OFF

ON

OFF

OFF

ON

OFF

OFF

ON

OFF

Controlled by

User

Unit

User

Unit

User

Unit

User

Unit

User

Unit

Unit operation

Enables master communications. (The Unit automatically restarts.)

Once enabled, the Unit will function as a Master regardless of whether the power is turned OFF and back ON again until the Master Stop Switch (word n, bit

07) is turned ON.

Note

1. Master communications are enabled in the default settings.

Operation conditions

CPU

Unit operating mode

Master function

Scan list status

Program mode

Disabled

---

Default setting

Master enabled

2. If this bit is turned ON with master communications enabled, a Unit status error will occur and a C2 error will be displayed on the 7segment display. The 7-segment display will go out automatically after 30 seconds.

Returns to OFF at the start of master communications.

Stops master communications. (The Unit automatically restarts.)

Turn this switch ON if the Unit will be used only for slave communications.

Returns to OFF after master communications stop.

Allocates the following words for use when the scan list is disabled (default setting). (The Unit automatically restarts.)

• OUT area: CIO 3200 to CIO 3263 (1 word/1 node address)

• IN area: CIO 3300 to CIO 3363 (1 word/1 node address)

Note

The I/O words used with the scan list disabled are also used with the scan list enabled. (Use the Scan List Enable Switch (word n, bit 00).)

Returns to OFF after the fixed allocation areas are set.

Functions the same as bit 08 to allocate the following words. (The Unit automatically restarts.)

• OUT area: CIO 3400 to CIO 3463 (1 word/1 node address)

• IN area: CIO 3500 to CIO 3563 (1 word/1 node address)

Returns to OFF after the fixed allocation areas are set.

Functions the same as bit 08 to allocate the following words. (The Unit automatically restarts.)

• OUT area: CIO 3600 to CIO 3663 (1 word/1 node address)

• IN area: CIO 3700 to CIO 3763 (1 word/1 node address)

Returns to OFF after the fixed allocation areas are set.

Program mode

Program mode

Program mode

Program mode

Enabled

Enabled

Enabled

Enabled

---

Disabled

Disabled

Disabled

Master

Fixed

Allocation

Setting

1 enabled

67

Allocated CIO Area Words

Section 3-2

Bit

11

12

13

Name

Master

User-set

Allocations

Switch

Temporary Setting

Switch for

Communications

Cycle

Time

Communications

Cycle

Time Setting

Switch

Status

OFF

ON

OFF

OFF

ON

OFF

OFF

ON

OFF

Controlled by

User

Unit

User

Unit

User

Unit

Unit operation

Reads setup data from the Master User Allocations

Setup Table (words m+1 to m+7) in the DM Area and registers the scan list. (The Unit automatically restarts.)

Once registered, the Unit will operate with master userset allocations regardless of whether the power is turned OFF and back ON again until the scan list is cleared.

Returns to OFF when the scan list is registered and the

Unit starts operating with the scan list enabled.

Note

If there is a setting error, an error code will be stored in the Master User Allocations Setup

Table (words m+1 to m+7) and the Scan List

Register/Clear Failed Flag (word n+12, bit 11) will turn ON.

Reads setup data from the Communications Cycle

Time Setup Table (word m) in the DM Area and temporarily changes the cycle time. The settings are not stored in non-volatile memory in the Unit and will not be valid again if the power is turned OFF and back ON or if the Unit is restarted.

Use this to temporarily extend the communications cycle time with a ladder program to place priority on message communication.

Note

The cycle time can be changed in any CPU Unit operating mode.

Returns to OFF after the communications cycle time is changed.

The Communications Cycle Time Reference Table

(words m+15 to m+18) will be cleared before the switch returns to OFF if the change was successfully completed.

Note

The Communications Cycle Time Setting Failed

Flag (word n+12, bit 12) turns ON if there is a setting error, and the Communications Cycle

Time Reference Table (words m+15 to m +18) will not be cleared.

Reads setup data from the communications cycle time setup table (word m) in the DM area to change the communications cycle time, and to store the communications cycle time in non-volatile memory in the Unit.

The settings will therefore be valid again if the power is turned OFF and back ON or if the Unit is restarted.

Returns to OFF after the communications cycle time is changed.

The Communications Cycle Time Reference Table

(words m+15 to m+18) will clear before the switch returns to OFF if the change was successfully completed.

Note

The Communications Cycle Time Setting Failed

Flag (word n+12 bit 12) will turn ON if there is a setting error. In that case, the Communications

Cycle Time Reference Table (words m+15 to m

+18) will not be cleared.

Operation conditions

CPU

Unit operating mode

Master function

Scan list status

Program mode

Enabled

---

Default setting

Master

Fixed

Allocation

Setting

1 enabled

---

Program mode

---

---

---

---

None

None

68

Allocated CIO Area Words

Section 3-2

Bit

14

Name

Communications

Cycle

Time

Reference

Table

Clear

Switch

OFF

ON

OFF

Status Controlled by

User

Unit

Unit operation

Clears data in the Communications Cycle Time Reference Table (words m+15 to m+18). The data that is cleared will be updated with new data.

Returns to OFF after the data in the Communications

Cycle Time Reference Table (words m+15 to m+18) has been cleared.

Operation conditions

CPU

Unit operating mode

Master function

Scan list status

-------

Default setting

None

3-2-2 Software Switches 2 (Word n+1)

All switches are turned ON by the user. The Unit automatically turns them

OFF after the function is executed. Once a function is set by turning a switch

ON (except for the switches listed below), it is saved regardless of whether the power is turned OFF and back ON again.

• Slave COS Send Switch (bit 12)

• Unit Setup File Restore Switch (bit 14)

• Unit Setup File Backup Switch (bit 15)

If multiple bits are turned ON simultaneously, the requests will generate errors but they will not alter Unit operation. The corresponding error bits in the following words will turn ON if a request made by a software switch ends in an error.

• Slave Status 1

Word n+1 [n = CIO 1,500 + (25 x unit number)]

Bit Name Status Controlled by

Unit operation

-----

Operation conditions

CPU

Unit operating mode

Slave function

-----

Default setting

--00 to

05

Reserved by system

---

69

Allocated CIO Area Words

Section 3-2

Bit

06

07

08

09

Name

Slave

Enable

Switch

Slave Stop

Switch

Slave

Fixed Allocation Setting 1

Switch

Slave

Fixed Allocation Setting 2

Switch

Status

OFF

ON

OFF

OFF

ON

OFF

OFF

ON

OFF

OFF

ON

OFF

Controlled by

User

Unit

User

Unit

User

Unit

User

Unit

Unit operation

Enables slave communications. (The Unit automatically restarts.)

To use fixed allocations, turn this switch ON after turning

ON a Slave Fixed Allocation Setting Switch (word n+1, bits 08 to 10). To used user-set allocations, turn this switch ON after turning ON the User Setting Switch

(word n+1, bit 11).

Once enabled, the Unit will function as a slave regardless of whether the power is turned OFF and back ON again until the Slave Stop Switch (word n+1, bit 07) is turned ON.

Note

1. Slave communications are enabled in the default setting.

2. If this bit is turned ON with Slave enabled, a

Unit status error will occur and a C2 error will be displayed on the 7-segment display. The

7-segment display will go out automatically after 30 seconds.

Returns to OFF at the start of slave communications.

Operation conditions

CPU

Unit operating mode

Program mode

Slave function

Disabled

Default setting

Slave disabled

Disabled

Slave disabled

Stops slave communications. (The Unit automatically restarts.) Turn this switch ON if the Unit will be used only for master communications.

Returns to OFF after slave communications stop.

Allocates the following words to the slave.

• OUT 1 area (input to the CPU Unit):

CIO 3370 (1 word allocated)

• IN 1 area (output from the CPU Unit):

CIO 3270 (1 word allocated)

• OUT 2 area: Not used

• IN 2 area: Not used

Note

1. Slave communications must be disabled before this switch is turned ON. After the switch is turned ON, turn the Slave Enable

Switch (word n+1, bit 06) ON to enable Fixed

Allocation Setting 1.

2. This is the default setting for the Unit.

3. The words allocated by this switch are used as the I/O area for the slave. (Use the Slave

Enable Switch (word n+1, bit 06).)

Returns to OFF after fixed allocations have been set.

Allocates the following words to the slave.

• OUT 1 area (input to the CPU Unit):

CIO 3570 (1 word allocated)

• IN 1 area (output from the CPU Unit):

CIO 3470 (1 word allocated)

• OUT 2 area: Not used

• IN 2 area: Not used

Note

Same as notes 1 to 3 for bit 08.

Returns to OFF after fixed allocations have been set.

Program mode

Program mode

Program mode

Enabled

Disabled

Slave

Fixed

Allocation setting 1 enabled

70

Allocated CIO Area Words

Section 3-2

Bit

10

11

12

13

Name

Slave

Fixed Allocation setting 3 switch

Slave User

Allocations

Switch

Status

OFF

ON

OFF

OFF

ON

OFF

Slave

COS Send

Switch

OFF

ON

OFF

Controlled by

User

Unit

User

Unit

User

Unit operation

Allocates the following words to the slave.

• OUT 1 area (input to the CPU Unit):

CIO 3770 (1 word allocated)

• IN 1 area (output from the CPU Unit):

CIO 3670 (1 word allocated)

• OUT 2 area: Not used

• IN 2 area: Not used

Note

Same as notes 1 to 3 for bit 08.

Returns to OFF after fixed allocations have been set.

Reads setup data from the Slave User Allocations Setup

Table in the DM Area and registers slave user-set allocations.

Once registered, the Unit will operate with slave user-set allocations regardless of whether the power is turned

OFF and back ON again until slave communications are disabled (i.e., until Slave Disable Switch (word n+1, bit

07) is turned ON).

Slave communications must be disabled before this switch is turned ON.

Note

After the switch is turned ON, turn the Slave

Enable Switch (word n+1, bit 06) ON to enable user-set allocations.

Returns to OFF at the start of operation for slave userset allocations.

Note

The Slave Function Enable/Stop Failed Flag

(word n+14, bit 08) in Unit Status 2 will turn ON if there is a setting error.

Sends COS IN data to the master.

Program mode

---

Operation conditions

CPU

Unit operating mode

Program mode

Slave function

Disabled

Default setting

Slave

Fixed

Allocation setting 1 enabled

Disabled

---

Slave

Fixed

Allocation setting 1 enabled

None

Unit

Reserved by system

-----

Returns to OFF after transmission is completed regardless of whether it was completed normally or in error.

---------

71

Allocated CIO Area Words

Section 3-2

Bit

14

15

Name

Unit Setup

File

Restore

Switch

Unit Setup

File

Backup

Switch

Status

OFF

ON

OFF

OFF

ON

OFF

Controlled by

User

Unit

User

Unit

Unit operation

Reads Unit settings (scan list, communications cycle time settings, etc.) from the file on a Memory Card in the CPU Unit and writes the data as Unit settings. See

7-2

Memory Card Backup Functions

for details.

(The Unit automatically restarts.)

Note

After the file data is read, the Unit automatically restarts with the new data.

Returns to OFF when the Unit restarts if the data is read properly.

Note

The File Read/Write Error Flag

(word n+11, bit 08) in Unit Status 2 will turn ON if there is a setup data error or a file read error.

Operation conditions

CPU

Unit operating mode

Master function

Program mode

---

Scan list status

---

Slave function

---

Default setting

None

Writes user settings (scan list, communications cycle time settings, etc.) as a file on the Memory Card in the CPU Unit. See

7-2

Memory Card Backup Functions

for details.

Note

Files can only be backed up with the scan list enabled.

---

Returns to OFF after the data is written to a file.

Note

The File Read/Write Error Flag

(word n+11, bit 08) in Unit Status 2 will turn ON if data failed to be written to file.

--Enabled

(See note

1.)

--None

Note

1.

When the Master function is enabled, the Unit Setup File cannot be backed up unless the scan list is enabled.

3-2-3

n+2 n+3 n+4 n+5

Master COS Send Switches (Words n+2 to n+5)

One Master COS Send Switch is allocated to each slave node address. If the switch for a slave is turned ON, then COS output data will be sent to that slave.

Bit15 Bit14 Bit13 Bit12 Bit11 Bit10 Bit09 Bit08 Bit07 Bit06 Bit05 Bit04 Bit03 Bit02 Bit01 Bit00

15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00

31

47

63

30

46

62

29

45

61

28

44

60

27

43

59

26

42

58

25

41

57

24

40

56

23

39

55

22

38

54

21

37

53

20

36

52

19

35

51

18

34

50

17

33

49

16

32

48

More than one of these switches may be turned ON at the same time. The switches will return to OFF starting at the switches for the slaves to which

COS data has been sent.

If a send error occurs, the corresponding bit will turn ON in Slave Detailed

Status.

72

Allocated CIO Area Words

Section 3-2

3-2-4 Disconnect/Connect Switches (Words n+6 to n+9)

One Disconnect/Connect Switch is allocated to each slave node address. If the switch for a slave is turned ON, then remote I/O communications to that slave will be temporarily stopped (i.e., it is disconnected from the network). A communications error will occur at the end for any slave has been disconnected if the corresponding switch is turned ON during communications.

These switches are used primarily to replace slaves or to reserve a place for a slave that will be added (when a Unit is registered in the scan list but not yet connected). A communications error and verification error for the slave that has been disconnected will not be generated at the master as long as the corresponding switch is ON.

Note

These switches do not add or remove slaves from the registered scan list.

Bit

n+6 n+7 n+8 n+9

Bit15 Bit14 Bit13 Bit12 Bit11 Bit10 Bit09 Bit08 Bit07 Bit06 Bit05 Bit04 Bit03 Bit02 Bit01 Bit00

15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00

31

47

63

30

46

62

29

45

61

28

44

60

27

43

59

26

42

58

25

41

57

24

40

56

23

39

55

22

38

54

21

37

53

20

36

52

19

35

51

18

34

50

17

33

49

16

32

48

Name

Disconnect/

Connect

Switch

ON

OFF

Status

Remote I/O communications will restart if a user turns OFF a bit that is ON.

More than one of these switches may be turned ON at the same time. If the switch for a slave that is not using remote I/O communications is turned ON, it will be ignored.

A Unit that has been disconnected can still perform message communications.

Turning ON this bit does not effect the communications cycle time (except that it increases blank time in the communications cycle).

Note

All Disconnect/Connect Switches are cleared and return to OFF when the power is turned OFF. If required, write the ladder program to turn them back ON when the power is turned ON.

Controlled by

User

Unit operation

Stops remote I/O communications for the corresponding Slave.

User Starts remote I/O communications for the corresponding Slave.

73

Allocated CIO Area Words

Section 3-2

3-2-5 Unit Status 1 (Word n+10)

Word n+10 [n = CIO 1,500 + (25 x unit number)]

Bit

00

01

02

Name

Unit Error

Flag

Master

Function

Error Flag

Status

ON

OFF

ON

OFF

Controlled by

Unit

Unit

Unit

Unit

---

Unit operation

Displays DeviceNet Unit operating errors.

This bit turns ON if any bit from 01 to 15 in Unit Status 1 turns ON. (OR of bits 01 to 15)

Usage example: When writing the ladder program for remote I/O communications, set a NC input conditions for this bit to control Slave I/O processing.

Indicates that the an error has not occurred or turns OFF when the error has cleared.

Indicates that a master error has occurred. (Master Status 1 (See word n+12.))

The master errors are as follows:

• Verification Error Flag (word n+12, bit 00)

• Structure Error Flag (word n+12, bit 01)

• Remote I/O Communications Error Flag (word n+12, bit 02)

• Invalid Scan List Data Flag (word n+12, bit 04)

• Remote I/O Refresh Error Flag (word n+12, bit 05)

Indicates that the error has not occurred or turns OFF when the error has been cleared.

---

03

Reserved by system

Slave Function Error

Flag

---

ON Unit

04

05

06

Unit Memory Error

Flag

Node

Address

Duplicated

Flag

OFF

ON

OFF

Bus Off Flag ON

OFF

ON

OFF

Unit

Unit

Unit

Unit

Unit

Unit

Unit

Indicates that a slave error has occurred. (Slave Status 1 (See word n+14.))

The slave errors are as follows:

• Remote I/O Communications Error Flag for OUT 1/ IN 1 (word n+14, bit

02)

• Remote I/O Communications Error Flag for OUT 2/ IN 2 (word n+14, bit

03)

• Invalid Setup Data Flag (word n+14, bit 04)

• Remote I/O Refresh Error Flag (word n+14, bit 05)

Indicates that the error has not occurred or turns OFF when the error has been cleared.

Indicates an error in internal memory where the error history is stored.

(The error occurs when the Unit starts up or when the error history is written.)

Indicates that the error has not occurred. Once this error has occurred, the bit will remain ON and will not return to OFF.

Indicates that a Bus OFF error (communications were stopped by multiple transmissions) has occurred. When a Bus OFF occurs, the Unit goes offline and all communications stop (remote I/O communications stop, slave operation stop, and message communications are disabled).

Indicates that the error has not occurred. Once this error has occurred, the bit will remain ON and will not return to OFF.

Indicates a duplicate node address check error when the Unit starts up.

The Unit goes offline and all communications stop. (Remote I/O communications stop, slave operation stop, and message communications are disabled.)

Indicates that the error has not occurred. Once this error has occurred, the bit will remain ON and will not return to OFF.

74

Allocated CIO Area Words

Section 3-2

Bit Name Status

07 Network

Power Error

Flag

ON

OFF

08 Send Timeout Flag

ON

OFF

Controlled by

Unit

Unit

Unit

Unit

---

Unit operation

Indicates that there is no power from the network power supply.

Note

Remote I/O communications stop if DIP switch pin 3 (remote I/O communications stop/continue setting for a communications error) on the front panel is ON (stop).

Indicates that the error has not occurred or turns OFF when the network power supply has restarted.

Indicates that a send timeout occurred due to one of the following factors:

• No slaves present.

• Mismatched baud rate settings.

Note

Remote I/O communications stop if DIP switch pin 3 (remote I/O communications stop/continue setting for a communications error) on the front panel is ON (stop).

Returns to OFF at the start of communications even with just one slave present.

--09 to

11

12

Reserved by system

---

Routing

Table Error

Flag

ON

13 Invalid Message Timer

List Flag

OFF

ON

OFF

Unit

Unit

Unit

Unit

Incorrect data in the routing tables set in the CPU Unit. Refer to

1-6-3 Creating Routing Tables

.

Indicates that the error has not occurred if a routing table has been set.

Indicates that the data in the message monitoring timer list is not correct.

Indicates that the data in the message monitoring timer list is correct.

Turns OFF if the Configurator registers a message monitoring timer list when the error occurs.

The message monitoring timer list shows the time spent waiting for responses in message communications. It is set from the Configurator.

--14 to

15

Reserved by system

-----

3-2-6 Unit Status 2 (Word n+11)

Word n+11 [n = CIO 1,500 + (25 x unit number)]

Bit

00

Name

Online Flag

Status

ON

OFF

Controlled by

Unit

Unit

Unit operation

Indicates that the Unit is online. The Unit normally goes online automatically.

Note

When executing message communications instructions (SEND/

RECV/CMND) from the ladder program, use an AND of input conditions for the Network Communications Enabled Flag in the CPU

Unit (A20200 to A20207) and this bit.

Indicates that the Unit is offline. A Unit will go offline under the following conditions:

• Operation is stopped by the hardware/software check at startup.

• An error occurred in the duplicate node address check (word n+10, bit

06).

• A Bus OFF error has occurred (word n+10, bit 05).

75

Allocated CIO Area Words

Section 3-2

Bit

01 Remote I/O

Communications Flag

ON

02

03

04

05

06

Reserved by system

---

Master

Function

Enabled

Flag

Scan List

Disabled

Flag

ON

OFF

ON

OFF

--Reserved by system

Automatic

Slave

Connection

Flag

ON

OFF

07

08

Name Status

OFF

Slave Function Enabled

Flag

File Read/

Write Error

Flag

ON

OFF

ON

OFF

09 to

14

15

Reserved by system

---

Error History Flag

ON

OFF

Controlled by

Unit

Unit

---

Unit operation

Indicates that remote I/O communications are being performed for the master function. Normally, the Unit will perform remote I/O communications automatically.

Note

This bit only indicates the start of remote I/O communications, and does not indicate whether data has actually been exchanged with slaves. Actual data exchange between one or more slaves is monitored from I/O Data Communications Flag (word n+12 bit 15).

Therefore use I/O Data Communications Flag rather than this bit as the input condition in I/O processing for slaves from the ladder program.

Indicates remote I/O communications have stopped. This bit turns OFF in order to stop communications under the following conditions:

• No slaves are registered in the scan list.

• Invalid Setup Data Flag (word n+12, bit 04)

• A remote I/O communications error or sending error (network power error or send timeout error) occurred with DIP switch pin 3 (remote I/O communications stop/continue setting for communications errors) on the front panel turned ON.

• The remote I/O Communications Stop Switch (word n, bit 04) is ON.

---

Unit

Unit

Unit

Unit

---

Unit

Unit

Unit

Unit

Unit

Unit

---

Unit

Unit

Indicates that master communications are enabled (Unit is operating as a

Master) (default setting).

Indicates that master communications are disabled.

Indicates that the Unit is operating with the scan list disabled (default setting).

Indicates that the Unit is operating with the scan list enabled.

---

Indicates that the connection type was automatically set in the slave scan list.

This flag is valid only with slave communications enabled.

Indicates that the connection type was set from the Configurator in the slave scan list.

Note

The type of connection in slave communications cannot be specified without the Configurator. If it is not set from the Configurator, it will be set automatically.

Indicates that slave communications are enabled.

Indicates that slave communications are disabled (default setting).

Indicates that an error has occurred when user setup data is read from a

Memory Card in the CPU Unit or when data is written as a file to a Memory Card.

Indicates that the error has not occurred. Turns OFF when the Unit has successfully completed the operation.

---

Indicates that an error history has been registered. Turns ON at the first error history for the Unit.

Indicates that no errors have been registered in the error history. Turns

OFF when the Unit receives an error history clear request.

76

Allocated CIO Area Words

Section 3-2

3-2-7 Master Status 1 (Word n+12)

Word n+12 [n = CIO 1,500 + (25 x unit number)]

Bit

00

01

02

03

04

05

06 to

07

08

Name

Verification

Error Flag

Structure

Error Flag

Status

ON

OFF

ON

OFF

Remote I/O

Communications Error

Flag

ON

OFF

Reserved by system

---

Invalid Scan

List Data

Flag

ON

OFF

Remote I/O

Refresh

Error Flag

ON

Reserved by system

OFF

---

ON

Controlled by

Unit

Unit

Unit

Unit

Unit

Unit

---

Unit operation

Indicates that the data in the slave registered in the scan list is different from the data from the actual slave. It occurs with the scan list enabled.

Indicates that a verification error has not occurred or turns OFF when a verification error is cleared.

Indicates that I/O allocations cannot be made with the scan list disabled.

Indicates that a structure error has not occurred or turns OFF when a structure error is cleared.

Indicates that a remote I/O communications timeout has occurred during remote I/O communications with slaves.

Remote I/O communications will stop if DIP switch pin 3 (remote I/O communications stop/continue setting for communications errors) on the front panel is ON (stop).

This error occurs with the scan list enabled or disabled.

Indicates that a remote I/O communications error has not occurred or turns OFF when a remote I/O communications error is cleared.

---

Unit

Unit

Unit

Unit

---

Unit

Indicates that there is incorrect data in the scan list (mismatched checksum). Remote I/O communications in the Unit will stop. (Slave operations and message communications will continue.)

Indicates that the scan list data is correct.

Turns OFF when an incorrect scan list data error occurs and then the correct scan list is registered.

Indicates that the I/O memory in the CPU Unit that is to be refreshed is not present during I/O refreshing for the master. It occurs in several situations, such as when an I/O area is allocated in an EM bank that is not present.

Indicates that no master I/O refresh errors have occurred.

---

09

Master

Function

Enable/

Disable

Failed Flag

OFF

User

Allocation

Area Setting

Failed Flag

ON

OFF

Unit

Unit

Unit

Indicates that an error has occurred in one of the following operations:

• Master enable (word n, bit 06)

• Master stop (word n, bit 07)

Once this bit turns ON, it will remain ON until the operation is successfully completed.

Indicates that the error has not occurred. The bit turns OFF when the operation is successfully completed.

Indicates that an error has occurred in one of the following operations:

• Master user-set allocations user setting (word n, bit 11)

Once this bit turns ON, it will remain ON until the operation is successfully completed.

Details on the master user-set allocation results are output to the Master

User Allocations Setup Table.

Indicates that the error has not occurred. The bit turns OFF when the operation is successfully completed.

77

Allocated CIO Area Words

Section 3-2

Bit Name Status

10 Fixed

Allocation

Area Setting

Failed Flag

ON

OFF

11 Scan List

Register/

Clear Failed

Flag

ON

OFF

12 Communications Cycle

Time

Setting

Failed Flag

ON

OFF

Controlled by

Unit

Unit

Unit

Unit

Unit

Unit

---

Unit operation

Indicates that an error has occurred in one of the following operations:

• Fixed Allocation Setting 1 (word n, bit 08)

• Fixed Allocation Setting 2 (word n, bit 09)

• Fixed Allocation Setting 3 (word n, bit 10)

Once this bit turns ON, it will remain ON until the operation is successfully completed.

Indicates that the error has not occurred. The bit turns OFF when the operation is successfully completed.

Indicates that an error has occurred in one of the following operations:

• Scan list enabled (word n, bit 00)

• Scan list clear (word n, bit 01)

Once this bit turns ON, it will remain ON until the operation is successfully completed.

Indicates that the error has not occurred. The bit turns OFF when the operation is successfully completed.

Indicates that an error has occurred when setting the communications cycle time (word n, bit 12).

Once this bit turns ON, it will remain ON until the next communications cycle time is set.

Indicates that the error has not occurred. The bit turns OFF when the operation is successfully completed.

--13 to

14

15

Reserved by system

---

I/O Data

Communications Flag

ON

3-2-8

OFF

Unit

Unit

Indicates that at least one slave is performing remote I/O communications.

Usage example: When writing the ladder program for remote I/O communications, set a NO input condition for this bit to control slave I/O processing.

Indicates that remote I/O communications are not being conducted with any slaves.

Master Status 2 (Word n+13)

The leftmost eight bits indicate the status of master I/O allocations.

Word

Bit 15 n+13

Master I/O Allocation Status

Bit 08 Bit 07

Reserved by system

Bit 00

Master I/O Allocation Status

00 Hex

01 Hex

02 Hex

03 Hex

11 Hex

12 Hex

13 Hex

20 Hex

30 Hex

80 Hex

Code Details

Unit starting up

Fixed allocation status 1 (with the scan list disabled)

Fixed allocation status 2 (with the scan list disabled)

Fixed allocation status 3 (with the scan list disabled)

Fixed allocation status 1

Fixed allocation status 2

Fixed allocation status 3

User-set allocations in the allocated DM Area words

User-set allocations from the Configurator

Master function disabled

78

Allocated CIO Area Words

Section 3-2

3-2-9 Slave Status 1 (Word n+14)

Word n+14 [n = CIO 1,500 + (25 x unit number)]

Bit

00 to

01

02

Name

Reserved by system

---

Status Controlled by

-----

Unit

Unit operation

Indicates that a communications error has occurred in the OUT 1/IN 1 slave I/O connection.

03

04

Remote I/O

Communications Error

Flag for

OUT 1/ IN 1

Remote I/O

Communications Error

Flag for

OUT 2/ IN 2

ON

OFF

ON

OFF

Invalid Setup

Data Flag

ON

Unit

Unit

Unit

Unit

Indicates that a remote I/O communications error has not occurred or turns OFF when a remote I/O communications error is cleared.

Indicates that a communications error has occurred in the OUT 2/IN 2

Slave I/O connection.

Indicates that a remote I/O communications error has not occurred or turns OFF when a remote I/O communications error is cleared.

05

06 to

07

08

Remote I/O

Refresh

Error

OFF

ON

Reserved by system

OFF

---

ON

Unit

Unit

Unit

---

Unit

Indicates that there is incorrect data in slave settings (mismatched checksum). The Unit stops slave communications. (Remote I/O communications and message communications continue.)

Indicates that a Unit is operating with the correct slave setup data or without slave communications being set.

Turns OFF when the slave is properly set after a slave setup data error occurs.

Indicates that the I/O memory in the CPU Unit that is to be refreshed is not present during I/O refreshing for the slave function. It occurs in several situations, such as when an I/O area is allocated in a EM bank that is not present.

Indicates that a slave I/O refresh error has not occurred.

---

09

10

Slave

Function

Enable/

Disable

Failed Flag

OFF

User

Allocation

Area Setting

Failed Flag

ON

OFF

Fixed

Allocation

Area Setting

Failed Flag

ON

OFF

Unit

Unit

Unit

Unit

Unit

Indicates that an error has occurred in one of the following operations:

• Slave function enabled (word n+1, bit 06)

• Slave function disabled (word n+1, bit 07)

Once this bit turns ON, it will remain ON until the operation is successfully completed.

Indicates that the error has not occurred. The bit turns OFF when the operation is successfully completed.

Indicates that an error has occurred in the following operation:

• Slave user-set allocations user setting (word n+1, bit 11)

Once this bit turns ON, it will remain ON until the operation is successfully completed.

Indicates that the error has not occurred. The bit turns OFF when the operation is successfully completed.

Indicates that an error has occurred in one of the following operations:

• Slave Fixed Allocation Setting 1 (word n+1, bit 08)

• Slave Fixed Allocation Setting 2 (word n+1, bit 09)

• Slave Fixed Allocation Setting 3 (word n+1, bit 10)

Once this bit turns ON, it will remain ON until the operation is successfully completed.

Indicates that the error has not occurred. The bit turns OFF when the operation is successfully completed.

79

Allocated CIO Area Words

Section 3-2

Bit

11

12

13

14

15

Name

COS Send

Failed Flag

Connection

2 Established Flag

Connection

1 Established Flag

OFF

ON

Remote I/O

Communications Flag for

OUT 2/IN 2

OFF

ON

OFF

Remote I/O

Communications Flag for

OUT 1/IN 1

Status

ON

OFF

ON

ON

OFF

Controlled by

Unit

Unit

Unit

Unit

Unit

Unit

Unit

Unit

Unit

Unit

Unit operation

Indicates that an attempt was made to send COS to a Master using the

Slave COS send switch (Slave COS Send Switch in n+1) in Software

Switches 2, but the transmission failed.

The following may cause the failure of COS signal transmission.

• A COS connection was not established with a master.

• Bus OFF error occurred.

• A network power error occurred.

• A send timeout occurred.

Once this bit turns ON, it will remain ON until the operation is successfully completed.

Indicates that the error has not occurred. The bit turns OFF when COS is successfully sent.

Indicates that an I/O connection has been established for OUT 2/IN 2.

This bit turns ON even if valid I/O data has not been exchanged.

Indicates that an I/O connection has not been established for OUT 2/IN 2.

Indicates that an I/O connection has been established for OUT 1/IN 1.

This bit turns ON even if valid I/O data has not been exchanged.

Indicates that an I/O connection has not been established for OUT 1/IN 1.

Indicates that an I/O connection has been established for OUT 2/IN 2 and the slave is conducting normal remote I/O communications with the master.

Indicates that an I/O connection has been established for OUT 2/IN 2 and the slave is not conducting normal remote I/O communications with the master.

Usage example: When writing the ladder program for slave remote I/O communications, used a NO input conditions for this bit to control I/O processing with the master.

Indicates that an I/O connection has been established for OUT 1/IN 1 and the Slave is conducting normal remote I/O communications with the Master.

Indicates that an I/O connection has been established for OUT 1/IN 1 and the slave is not conducting normal remote I/O communications with the master.

Usage example: When writing the ladder program for slave remote I/O communications, used a NO input conditions for this bit to control I/O processing with the master.

80

Allocated CIO Area Words

3-2-10 Slave Status 2 (Word n+15)

Word n+15

Bit 15

Slave I/O Allocation Status

Bit 08 Bit 07

Master Node Address

Bit 00

Section 3-2

Master Node Addresses

Slave I/O Allocation Status

This indicates the node address of the remote master for slave communications.

Name

Master Node

Address

Range

0000 to 003F Hex

(0 to 63)

Details

This information is valid when the Remote

I/O Communications Flag (word n+14, bit

14 or 15) is ON in Slave Status 1.

This indicates the I/O allocation status of the slave.

Code

00 Hex

01 Hex

02 Hex

03 Hex

20 Hex

30 Hex

80 Hex

Details

Unit starting up

Fixed Allocation Setting 1

Fixed Allocation Setting 2

Fixed Allocation Setting 3

User-set allocations using allocated DM Area words

Set from the Configurator

Slave function disabled

3-2-11 Registered Slave Table (Words n+16 to n+19)

This table indicates the slaves that are registered in the master scan list. The bits correspond to node addresses. This table is updated when the Unit starts up and when a scan list is registered.

n+16 n+17 n+18 n+19

Bit15 Bit14 Bit13 Bit12 Bit11 Bit10 Bit09 Bit08 Bit07 Bit06 Bit05 Bit04 Bit03 Bit02 Bit01 Bit00

15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00

31

47

63

30

46

62

29

45

61

28

44

60

27

43

59

26

42

58

25

41

57

24

40

56

23

39

55

22

38

54

21

37

53

20

36

52

19

35

51

18

34

50

17

33

49

16

32

48

Operation with the Scan

List Disabled

This table indicates the slaves to which a connection has been established at least once. When registering a scan list using the Scan List Enable Switch

(word n, bit 00), the bits corresponding to the slaves that are registered are turned ON in this table.

This table indicates the slaves that have been registered in the scan list.

Operation with the Scan

List Enabled

Bit Name Status

– Slave

Registered

Flags

ON

OFF

Controlled by

Unit

Unit

Unit operation

With the scan list disabled: Indicates slaves to which a connection has been established at least once.

With the scan list enabled: Indicates that a slave has been registered in the scan list.

Indicates that a slave has not been registered in the scan list.

81

Allocated CIO Area Words

Section 3-2

3-2-12 Normal Slave Table (Words n+20 to n+23)

This table indicates the slaves that are communicating normally with the master. The bits correspond to node addresses. The bits for slaves for which normal I/O connections have been made are turned ON in this table. These are not flags to show the remote I/O communications status. n+20 n+21 n+22 n+23

Bit15 Bit14 Bit13 Bit12 Bit11 Bit10 Bit09 Bit08 Bit07 Bit06 Bit05 Bit04 Bit03 Bit02 Bit01 Bit00

15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00

31

47

63

30

46

62

29

45

61

28

44

60

27

43

59

26

42

58

25

41

57

24

40

56

23

39

55

22

38

54

21

37

53

20

36

52

19

35

51

18

34

50

17

33

49

16

32

48

Bit

Name

Slave Normal Flags

Status

ON

OFF

In the following cases, the status of communications up to the most recent status is saved and then status is cleared when communications are restarted

(i.e., when connection is made again).

• Communications power supply error

• Send timeout

• Remote I/O communications stopped

• When a communications error occurs with DIP switch pin 3 (remote I/O communications stop/continue setting for communications errors) on the front panel ON (stop)

This table is updated continuously.

Controlled by

Unit

Unit

Unit operation

Indicates normal connection.

Indicates that not all connections have been made.

3-2-13 C200H Master Replacement Master Status 1 (Word n+24)

To simplify changes to ladder programs for a C200H DeviceNet Master Unit

(C200HW-DRM21-V1), Master Replacement Status 1, which has the same bit configuration as Master Status Area 1, is provided for C200H DeviceNet Master Units.

Word n+24 [n = CIO 1,500 + (25 x unit number)]

Bit

00

01

02

Name

Unit Memory

Error Flag

Node

Address

Duplicated/

Bus Off Flag

Reserved by system

---

Status

ON/OFF

ON/OFF

Controlled by

Unit

Unit

---

C200HW-

DRM21-V1 status

Switch Setting Error or

EEPROM

Error Flag

Node

Address

Duplicated/

Bus Off Flag

Reserved by system

Details and CS1W-DRM21(-V1) status

This is the same as a Unit memory error (word n+10, bit

04).

Note

This bit is also used for incorrect switch settings for the C200HW-DRM21-V1. The Unit will not start if the switch settings are incorrect.

This bit turns ON if any one of the following flags turns

ON:

• Node Address Duplicated Flag (word n+10, bit 06)

• Bus Off Flag (word n+10, bit 05)

Reserved by system

82

Allocated CIO Area Words

Section 3-2

Bit Name

03 Configuration Error

Flag

04

05

Structure

Error Flag

Send Error

Flag

Status

ON/OFF

ON/OFF

ON/OFF

06

07

08

Communications Error

Flag

Verification

Error Flag

I/O Data

Communications Not

Running Flag

ON/OFF

ON/OFF

ON/OFF

09 Reserved by system

---

10 Reserved by system

---

11 Reserved by system

---

12 Message

Communications Permitted Flag

ON/OFF

13

14

Invalid Scan

List Data Flag

Error Flag

ON/OFF

ON/OFF

15 Remote I/O

Communications Flag

ON/OFF

Controlled by

Unit

Unit

Unit

Unit

Unit

Unit

---

---

---

Unit

Unit

Unit

Unit

C200HW-

DRM21-V1 status

Configuration Error

Flag

Structure

Error Flag

Send Error

Flag

Details and CS1W-DRM21(-V1) status

This bit turns ON if any of the following flags turn ON:

• Routing Table Error Flag (word n+10, bit 12)

• Invalid Message Timer List Flag (word n+10, bit 13)

• Invalid Scan List Data Flag (word n+12, bit 04)

• Remote I/O Refresh Error Flag (word n+12, bit 05)

Note

The C200HW-DRM21-V1 does not support slave communications. Scan list data errors for slave communications are not relevant.

This is the same as the Structure Error Flag in word n+12, bit 01.

This bit turns ON if any one of the following bits turns ON:

• Network Power Error Flag (word n+10, bit 07)

• Send Timeout Flag (word n+10, bit 08)

This is the same as the Remote I/O Communications Flag

(word n+12, bit 02).

Communications Error

Flag

Verification

Error Flag

This is the same as the Verification Error Flag in word n+12, bit 00.

I/O Data

Communications Not

Running

Flag

Scan List

Operation

Completed

Flag

This operates in the reverse way of the Remote I/O Communications Flag (word n+11 bit 01).

---

Scan List

Operation

Error Flag

Communications Error

Stop Cleared

Flag

---

---

Message

Communications Permitted Flag

The same as the Online Flag in word n+11, bit 00.

Note

When executing message communications instructions (SEND/RECV/CMND) from the ladder program, use an AND of input conditions for the

Network Communications Enabled Flag in the

CPU Unit (A20200 to A20207) and this bit.

Invalid Scan

List Data Flag

The same operation as the Invalid Scan List Data Flag

(word n+11, bit 04).

Error Flag

Remote I/O

Communications Flag

This bit turns ON if bit 00, 01 or 03 to 07 in this word

(n+24) turns ON.

The same as I/O Data Communications Flag (word n+12 bit 15).

Note

Although the bit configurations are the same, the word addresses are different

(because this is a CS/CJ-series CPU Bus Unit). Change the words using a replacement operation from the Programming Device.

83

Allocated DM Area Words

3-3

Section 3-3

m+31 to m+42 m+43 to m+74 m+75 to m+99 m+1 to m+7 m+8 to m+14 m+15 to m+18 m+19 to m+30

Allocated DM Area Words

Data is stored at the offset positions shown in the figure below starting from the first word allocated to the Unit in the DM Area.

The first word can be calculated as follows from the unit number setting:

First word m = D30000 + (25 x unit number)

Word m

Bit 15

Communications Cycle Time Setup Table

Bit 00 Direction

Outputs

CPU Unit

DeviceNet Unit

Master User Allocations Setup Table (7 words)

Slave User Allocations Setup Table (7 words)

Communications Cycle Time Reference Table (4 words)

Master User-set Allocations Reference Table (12 words)

Slave User-set Allocations Reference Table (12 words)

Slave Detailed Status Table (32 words)

Reserved by system

I/O

CPU Unit

DeviceNet Unit

Inputs

CPU Unit

DeviceNet Unit

3-3-1 Communications Cycle Time Setup Table

This table sets the communications cycle time for the master.

The standard communications cycle time can be updated with these switches.

Temporary Setting

Switch for Communications Cycle

Time

Communications

Cycle Time Reference Table Clear

Switch

Word n, bit 12

Word n, bit 13

Returns to the previous setting when the power is turned

OFF or the Unit is restarted.

Also effective the next time the Unit is started, because the set value is stored in nonvolatile memory.

84

Allocated DM Area Words

Section 3-3

3-3-2

Word m

Bit 15 Bit 00

Communications cycle time setting (ms)

Name

Communications

Cycle Time Setting

Range

0000 to 01F4 Hex

(0 to 500)

Details

Sets the communications cycle time in milliseconds. Setting range: 0 to 500 ms

If this bit is set to 0, the optimum time calculated by the Unit will be used. If a value higher than 500 ms is set, then the Unit will operate at 500 ms.

If the setting cannot be correctly made for some reason, the Scan List Register/Clear

Failed Flag (word n+12, bit 11) in Master Status 1 and the Temporary Setting Switch for

Communications Cycle Time (word n, bit 12) will be turned OFF.

Note

If the setting is smaller than the optimum communications cycle time calculated by the Unit and stored internally in the Unit, then the value calculated by the Unit will be used.

Master User Allocations Setup Table

This table is set by the user to specify the I/O words used by the master. Only

OUT block 1 and IN block 1 can be set using this table.

Word

Bit 15 Bit 08 Bit 07 Bit 00 m+1

Reserved by system

OUT block 1 area m+2

First word in OUT block 1 m+3

Reserved by system

IN block 1 area m+4

First word in IN block 1 m+5

Reserved by system

Allocation size setup table area m+6

First word in the allocation size setup table m+7

Setting results

Note

OUT blocks 1 and 2 and IN blocks 1 and 2 can be set from the Configurator.

I/O allocations can be updated in the master by setting this table and turning

ON the Master User-set Allocations Switch (word n, bit 11). The Unit will restart automatically and start operating with the scan list enabled.

85

Allocated DM Area Words

Section 3-3

Areas and Word Ranges

Note

Make sure the CPU Unit is in PROGRAM mode and the master function is enabled before you set these values.

Name

OUT block 1 area

Range

See

Areas and

Word Ranges

.

Details

Specifies the OUT block area. The OUT block is not allocated when set to 00 Hex.

Specifies the first word for the OUT block.

First word in OUT block 1

IN block 1 area Specifies the IN block area. The IN block is not allocated when set to 00 Hex.

Specifies the first word for the IN block.

First word in IN block 1

Allocation size setup table area

First word in the allocation size setup table

(See note.)

Setting results See

Setting

Results

.

Specifies the area for the allocation size setup table. An area is not allocated when set to 00 Hex.

Specifies the first word of the allocation size setup table.

Gives the setting results.

Note

See

Allocation Size Setup Table

(p. 87) for more details on the first

word of the allocation size setup table.

Code

00 Hex

01 Hex

03 Hex

04 Hex

05 Hex

08 to 14

Hex

---

CIO Area (CIO)

Name

Data Memory (DM)

Work Area (WR)

Holding Relay (HR)

Expansion Data Memory (EM)

Bank 0 to bank C (13 banks)

Word range

The block is not allocated.

0000 to 17FF Hex (0 to 6143)

0000 to 7FFF Hex (0 to 32767)

0000 to 01FF Hex (0 to 511)

0000 to 01FF Hex (0 to 511)

0000 to 7FFF Hex (0 to 32767) for all banks

86

Allocated DM Area Words

Section 3-3

Setting Results

3-3-3

I+1

Code

0000

Hex

1101

Hex

1103

Hex

110C

Hex

1104

Hex

2201

Hex

2201

Hex

2606

Hex

Description

Completed normally ---

Details

No area

Address range specification error

Parameter error

Address range overflow

• Incorrect area setting.

• The allocated size in the allocation size setup table is 0.

The first word is outside the setting range.

• The OUT or IN size in the allocation size setup table exceeds 200 bytes.

• Both the OUT and IN blocks are set for no allocations.

• No slaves are allocated.

• The block or the allocation size setup table exceeds the valid word range.

• The block is larger than 1,000 bytes.

The CPU Unit is not in PROGRAM mode.

Wrong operating mode

Unit busy

Cannot execute service

Service cannot be executed because the Unit is busy.

The Unit master communications have not been disabled.

Allocation Size Setup Table

The following allocation size setup tables must be set in the I/O memory in the

CPU Unit to use the Master User Allocations Setup Table.

The number of bytes set in the allocation size setup table are allocated in word units in order of node addresses for OUT block 1 and then IN block 1.

Set the sizes within a range from 0 to 200 bytes (100 words).

Word

I

Bit 15 Bit 08 Bit 07

Node address 0 OUT size (bytes)

Node address 0 IN size (bytes)

Bit 00

Node address 1 OUT size (bytes)

Node address 1 IN size (bytes)

:

:

I+63

Node address 63 OUT size (bytes)

Node address 63 IN size (bytes)

87

Allocated DM Area Words

Section 3-3

3-3-4

I

I+1

I+2

Allocation size setup table

1 5

4 3

Setting Example

The following example shows the allocation when the size (bytes) for OUT block 1 and IN block 1 is set in the allocation size setup table using the specified values.

Node address 0: OUT size: 1 byte, IN size: 5 bytes

Node address 1: OUT size: 4 byte, IN size: 3 bytes

Node address 2: OUT size: 1 byte, IN size: 2 bytes

00 15 IN block 1 00 s

15 OUT block 1

Not usable 00 s+1 01 01 k k+1

00

00

00

00

:

1

:

2 s+2 s+3

01

Not usable

: l: First word of the allocation size setup table s: First word of OUT block 1 k: First word of IN block 1

:

01

02 k+2 k+3 k+4 k+5

Not usable

01

Not usable

02

: :

00

01

01

02

Note

1.

2.

The numbers in the OUT 1 and IN 1 blocks represent node addresses.

Bytes are allocated in order in the blocks in word units in the order of node addresses. If the allocated size is 1 byte, the rightmost byte is used, but the leftmost byte cannot be used.

Slave User Allocations Setup Table

The I/O areas specified here for the slave OUT 1 area, for slave IN 1 area are used if the slave function is enabled using the Slave User-set Allocations

Switch (word n+1, bit 11).

Word

Bit 15 Bit 08 Bit 07 Bit 00 m+8

00 Hex fixed

Slave OUT 1 area m+9

First word of the Slave OUT 1 area m+10

00 Hex fixed

OUT 1 area size (bytes) m+11

00 Hex fixed

Slave IN 1 area m+12

First word of the Slave IN 1 area m+13

00 Hex fixed

IN 1 area size (bytes) m+14

Setting results

I/O allocations for the slaves can be updated by setting this table and turning

ON the Slave User-set Allocations Switch (word n+1, bit 11). The Unit restarts automatically and starts operating with the scan list enabled.

Note

Make sure the CPU Unit is in PROGRAM mode and the Unit has stopped slave communications before you set these values.

88

Allocated DM Area Words

Section 3-3

Name

Slave OUT 1 area

First word in the Slave OUT

1 area

OUT 1 area size

Range

See

Areas and Word

Ranges

.

Slave IN 1 area

00 to C8

Hex

(0 to 200 bytes)

See

Areas and Word

Ranges

.

First word in the Slave IN 1 area

IN 1 area size

Setting results

00 to C8

Hex

(0 to 200 bytes)

See

Setting

Results

.

Details

Specifies the OUT 1 area. The OUT 1 area is not available if this is set at 0.

Specifies the first word in the OUT 1 area.

Specifies the size of the OUT 1 area in bytes. The OUT 1 area is not allocated when set to 00 Hex.

Specifies the IN 1 area. The IN 1 area is not allocated when set to 00 Hex.

Specifies the first word in the IN 1 area.

Specifies the size of the IN 1 area in bytes. The IN 1 area is not allocated when set to 00 Hex.

Shows the setting results.

Areas and Word Ranges

Code

00 Hex

01 Hex

03 Hex

04 Hex

05 Hex

08 to 14

Hex

CIO Area (CIO)

Name

Data Memory (DM)

Work Area (WR)

Holding Relay (HR)

Expansion Data Memory (EM)

Bank 0 to bank C (13 banks)

Word range

The area is not used.

0000 to 17FF Hex (0 to 6143)

0000 to 7FFF Hex (0 to 32767)

0000 to 01FF Hex (0 to 511)

0000 to 01FF Hex (0 to 511)

0000 to 7FFF Hex (0 to 32767) for all banks

Setting Results

Code

0000 Hex

1101 Hex

1103 Hex

110C Hex

1104 Hex

2201 Hex

2201 Hex

2606 Hex

Description

Completed normally

No area

Address range specification error

Parameter error

Address range overflow

Wrong operating mode

Unit busy

---

Details

Incorrect area setting.

The first word is outside the setting range.

• The OUT 1 or IN 1 area size exceeds

200 bytes.

• The OUT 1 and IN 1 area size is 0.

• Both the OUT 1 and IN 1 blocks are set for no allocations.

The allocated area exceeds the valid word range.

The CPU Unit is not in PROGRAM mode.

Cannot execute service

Service cannot be executed because the

Unit is busy.

The Unit slave communications have not been disabled.

89

Allocated DM Area Words

3-3-5

Section 3-3

Communications Cycle Time Reference Table

This table can be used to access the present, maximum and minimum communications cycle times. All the values in this table are cleared from the Unit and the maximum and minimum values are updated with new values when the Communications Cycle Time Reference Table Clear Switch (word n, bit

13) is turned ON.

Word m+15

Bit 15 Bit 00

Communications cycle time setting value (ms) m+16

Communications cycle time present value (ms) m+17

Communications cycle time maximum value (ms) m+18

Communications cycle time minimum value (ms)

Ranges

3-3-6

Communications cycle time setting value (ms)

Name

Communications cycle time present value (ms)

Communications cycle time maximum value (ms)

Communications cycle time minimum value (ms)

Range

0000 to

01F4 Hex (0 to 500)

0000 to

FFFF Hex

(0 to 65535)

Details

Provide the communications cycle time setting as well as the present, maximum, and minimum communications cycle time in milliseconds. The default settings is

0000Hex (0).

Master User-set Allocations Reference Table

The settings (area and size) for a maximum of four blocks (OUT block 1, OUT block 2, IN block 1, and IN block 2) can be accessed in the master user-set allocations reference table.

The OUT 1 and IN 1 areas and sizes are valid even if a Configurator is not being used.

Word

Bit 15 Bit 08 Bit 07 Bit 00 m+19

Reserved by system

OUT block 1 area m+20

First word in OUT block 1 m+21

No. of bytes in OUT block 1 m+22

Reserved by system

IN block 1 area m+23

First word in IN block 1 m+24

No. of bytes in IN block 1 m+25

Reserved by system

OUT block 2 area m+26

First word in OUT block 2 m+27

No. of bytes in OUT block 2 m+28

Reserved by system

IN block 2 area m+29

First word in IN block 2 m+30

No. of bytes in IN block 2

90

Allocated DM Area Words

Section 3-3

Ranges

Name

OUT block 1/2 area

First word in OUT block 1/2

No. of bytes in OUT block 1/2

Range

See

Areas and Word

Ranges

.

IN block 1/2 area

First word in IN block 1/2

No. of bytes in IN block 1/2

0000 to

03E8 Hex

(0 to 1,000 bytes)

See

Areas and Word

Ranges

.

0000 to

03E8 Hex

(0 to 1,000 bytes)

Details

Shows the area.

Shows the first word for the block.

Shows the block size in bytes. The OUT block has not been allocated if this is set at 00 Hex.

Shows the area.

Shows the first word for the block.

Shows the block size in bytes. The OUT block has not been allocated if this is set at 00 Hex.

Areas and Word Ranges

3-3-7

Code

00 Hex

01 Hex

03 Hex

04 Hex

05 Hex

08 to 14

Hex

---

CIO Area (CIO)

Name

Data Memory (DM)

Work Area (WR)

Holding Relay (HR)

Expansion Data Memory (EM)

Bank 0 to bank C (13 banks)

Word range

The block is not used.

0000 to 17FF Hex (0 to 6143)

0000 to 7FFF Hex (0 to 32767)

0000 to 01FF Hex (0 to 511)

0000 to 01FF Hex (0 to 511)

0000 to 7FFF Hex (0 to 32767) for all banks

Slave User-set Allocations Reference Table

The slave block settings can be accessed in the Slave User-set Allocations

Reference Table. A maximum of two OUT and two IN areas (OUT 1, IN 1,

OUT 2, and IN 2) can be used for slave communications and their area and size can be accessed in the table.

The OUT 1 and IN 1 areas and sizes are valid even if a Configurator is not being used.

Word

Bit 15 Bit 08 Bit 07 Bit 00 m+31

Reserved by system

Slave OUT 1 area m+32

First word in the slave OUT 1 area m+33

OUT 1 area size (bytes) m+34

Reserved by system

Slave IN 1 area m+35

First word in slave IN 1 m+36

IN 1 area size (bytes) m+37

Reserved by system

Slave OUT 2 area (Always 0) m+38

First word in the slave OUT 2 area (Always 0) m+39

OUT 2 area size (bytes) (Always 0) m+40

Reserved by system

Slave IN 2 area m+41

First word in slave IN 2 m+42

IN 2 area size (bytes)

91

Allocated DM Area Words

Section 3-3

Note

OUT2 is not used.

Ranges

Name

OUT 1/2 area

First word in the OUT block

1/2

OUT 1/2 area size

Range

See

Areas and Word

Ranges

.

IN 1/2 area

First word in the IN blocks1/2

00 to C8 Hex

(0 to 200 bytes)

See

Areas and Word

Ranges

.

IN 1/2 area size 00 to C8 Hex

(0 to 200 bytes)

Details

Shows the area.

Shows the first word for the area.

Shows the area by size in bytes.

Shows the area.

Shows the first word for the area.

Shows the block size in bytes.

Areas and Word Ranges

3-3-8

Code

00 Hex

01 Hex

03 Hex

04 Hex

05 Hex

08 to 14 Hex

Name

---

CIO Area (CIO)

Data Memory (DM)

Work Area (WR)

Holding Relay (HR)

Expansion Data Memory (EM)

Bank 0 to bank C (13 banks)

Word range

The block is not used.

0000 to 17FF Hex (0 to 6143)

0000 to 7FFF Hex (0 to 32767)

0000 to 01FF Hex (0 to 511)

0000 to 01FF Hex (0 to 511)

0000 to 7FFF Hex (0 to 32767) for all banks

Slave Detailed Status

The status of the slaves controlled by the master function of the Unit is provided by node address. Each word provides the status of two slaves.

Word m+43

Bit 15 Bit 08 Bit 07

Detailed slave status at node address 1

Bit 00

Detailed slave status at node address 0 m+44

Detailed slave status at node address 3

Detailed slave status at node address 2

: to m+74

Detailed slave status at node address 63

Detailed slave status at node address 62

Bit

00, 08

01, 09

02, 10

Name Status

Slave Error

Flags

ON

OFF

Slave Verification Error

Flags

ON

OFF

Slave Configuration

Error Flags

ON

OFF

Controlled by

Unit

Unit

Unit

Unit

Unit

Unit

Unit operation

Indicates that a remote I/O communications error has occurred with the slave. More specifically, this bit turns ON when at least one of the following errors occurs:

• Verification Error Flag (word n+12 bit 00)

• Structure Error Flag (word n+12 bit 01)

• Remote I/O Communications Error Flag (word n+12 bit 02)

Indicates that an error has not occurred or turns OFF when the error has been cleared.

Indicates that the data for the slave registered in the scan list is different from the actual Slave. It occurs with the scan list enabled.

Indicates that a verification error has not occurred or turns OFF when a verification error is cleared.

Indicates that an error that disables I/O allocations has occurred at the Slave (with the scan list disabled).

Indicates that a structure error has not occurred or turns OFF when the structure error is cleared.

92

Allocated DM Area Words

Section 3-3

Bit

03, 11

04, 12

05, 13

06, 14

07, 15

Name

Slave

Remote I/O

Communications Error

Flag

ON

OFF

Reserved by system

---

Master COS

Send Failure Flag

ON

Status Controlled by

Unit

Unit

---

Unit operation

Indicates that an error has occurred in remote I/O communications with the Slave.

This bit turns ON if a timeout occurs in at least one connection with multiple connections set.

This error occurs with the scan list enabled or disabled.

Indicates that a remote I/O communications error has not occurred or turns OFF when a remote I/O communications error is cleared.

---

Unit

Scan List

Registration

Flag

Remote I/O

Communications Flag

OFF

ON

OFF

ON

OFF

Unit

Unit

Unit

Unit

Unit

Indicates that COS sent to a slave destination failed.

Use the Master COS Send Switch (n+2/n+3/n+4/n+5 words) to send

COS.

The following may be cause failure of COS signal transmission.

• Remote I/O communications stopped

• A COS connection was not established

• Bus OFF has occurred.

• A network power error has occurred.

• A send timeout has occurred.

Once this bit turns ON, it will remain ON until the operation is successfully completed.

Indicates that the error has not occurred. The bit turns OFF when

COS is successfully sent.

Indicates that the slave is registered in the scan list.

The Unit is operating with the scan list disabled or the Unit is not registered in the scan list.

Indicates that normal remote I/O communications were conducted with the slaves at all set connections.

This bit turns OFF if a timeout occurs in at least one connection with multiple connections set.

Indicates that remote I/O communications failed (no slave present, no scan list registered, verification error, structure error) or that a communications error is occurring.

93

Allocated DM Area Words

Section 3-3

94

SECTION 4

Remote I/O Master Communications

This section describes the remote I/O communications performed as a DeviceNet master by the Devicenet Unit.

4-1

4-2

4-3

4-4

4-5

4-6

4-7

Master Remote I/O Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-1-1

4-1-2

Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Remote I/O Master Specifications . . . . . . . . . . . . . . . . . . . . . . . . . .

4-1-3

4-1-4

Precautions on the Number of Master Units. . . . . . . . . . . . . . . . . . .

Procedure for Using Remote I/O Master . . . . . . . . . . . . . . . . . . . . .

Scan List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fixed Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-3-1

4-3-2

4-3-3

4-3-4

Allocated Words . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Changing System Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fixed Allocations Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

User-set Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Starting and Stopping Remote I/O Communications . . . . . . . . . . . . . . . . . . .

4-5-1

4-5-2

Starting Remote I/O Communications . . . . . . . . . . . . . . . . . . . . . . .

Stopping Remote I/O Communications . . . . . . . . . . . . . . . . . . . . . .

4-5-3 Restarting Remote I/O Communications . . . . . . . . . . . . . . . . . . . . .

Example of Ladder Programming for Remote I/O Communications . . . . . . .

Errors that May Occur in Remote I/O Communications . . . . . . . . . . . . . . . .

111

120

120

120

105

106

109

109

100

101

103

105

96

96

99

120

120

122

95

Master Remote I/O Communications

Section 4-1

4-1 Master Remote I/O Communications

Remote I/O communications are used to automatically transfer data between slaves and the CPU Unit without any special programming in the CPU Unit under which the Master Unit is mounted.

Master Communications

CS/CJ-series DeviceNet Unit (master)

CS/CJ-series CPU Unit

Remote I/O communications

DeviceNet

Note

Slaves

1.

2.

A CS/CJ-series DeviceNet Unit can function as either a master or slave in remote I/O communications and it can even function as both a master and a slave at the same time. Turn ON the Master Enable Switch (word n, bit

06) in the Software Switches in the words allocated in the CIO Area to set the CS/CJ-series DeviceNet Unit to function as a master. Once this switch is turned ON and master communications are enabled, the Unit will continue to perform master communications regardless of whether the power is turned OFF and back ON again. Turn ON the Master Stop Switch (word n, bit 07) to stop master communications. Master communications are the focus of this section.

In the following descriptions, a CS/CJ-series DeviceNet Unit set to function as a master is referred to as a “Master Unit” and a CS/CJ-series DeviceNet

Unit set to function as a slave is referred to as a “Slave Unit”.

4-1-1 Allocations

All slaves are allocated words in the I/O memory of the CPU Unit to which the

Master Unit is mounted. They are allocated using one of the following methods:

1) Fixed allocations

2) User-set allocations

96

Master Remote I/O Communications

Fixed Allocations

Section 4-1

Any one of the three areas below can be specified as the words allocated in the CIO Area for fixed allocations. The output (OUT) block and the input (IN) block are allocated strictly in order of node addresses in one of the areas shown below.

Select one.

CS/CJ Series

OUT block 1

IN block 1

OUT block 2

IN block 2

CIO 3200

CIO 3201

Address 0

Address 1

CIO 3262

CIO 3263

Address 62

Address 63

CIO 3300

CIO 3301

Address 0

Address 1

CIO 0362

CIO 0363

Address 62

Address 63

CIO 3400

CIO 3401

Address 0

Address 1

CIO 3462

CIO 3463

Address 62

Address 63

CIO 3500

CIO 3501

Address 0

Address 1

CIO 3562

CIO 3563

Address 62

Address 63

To Slaves

From Slaves

To Slaves

From Slaves

OUT block 3

IN block 3

CIO 3600

CIO 3601

Address 0

Address 1

CIO 3662

CIO 3663

Address 62

Address 63

CIO 3700

CIO 3701

Address 0

Address 1

CIO 3762

CIO 3763

Address 62

Address 63

To Slaves

From Slaves

Words are allocated to slaves starting from address 0 in the output (OUT) and

IN blocks. Each address is allocated at least one byte (rightmost).

• More than one word is allocated for each slave (according to its node address) with more than16 I/O points.

• The rightmost byte of the word is allocated to each slave that has less than 16 I/O points.

User-set Allocations

Using the Master User

Allocations Table

The following methods are used for user-set allocations:

• Using a Master User Allocations Table (allocated DM Area words)

• Using the Configurator

In the Master User Allocations Table, set the areas and first words for the output block (OUT 1) and the input block (IN 1) and set the area and first word for the Allocation Size Setup Table. In the Allocation Size Setup Table, set the allocation sizes for the slave input and output blocks. Each slave can be allocated two blocks, OUT 1 and IN 1, according to the settings in these tables.

97

Master Remote I/O Communications

Section 4-1

The OUT and IN blocks will be allocated in order of slave node addresses.

Each block is a maximum of 500 words.

CPU Unit

Specified in allocated DM words

OUT block 1

IN block 1

Ascending order starting from address 0

Address

To Slaves

Address

Ascending order starting from address 0

Address

From Slaves

Address

Using the Configurator

Each address is allocated at least one byte (rightmost).

• More than one word is allocated for each slave with more than16 I/O points (according to its node address).

• The rightmost byte of the word is allocated to each slave that has less than 16 I/O points.

When using the Configurator, each slave can be allocated four blocks: Output

(OUT) blocks 1 and 2 and input blocks 1 and 2. Each block is a maximum of

500 words.

The position of each block can be set. An order (such as IN block 1, OUT block 2, IN block

2 and OUT block 1) can also be used.

CPU Unit

Output area

Address

Any address order

OUT block 1

Address

To Slaves

Address

OUT block 2

Any address order

To Slaves

Address

Address

Any address order

Input area

IN block 1

IN block 2

Address

Address

From Slaves

Any address order

From Slaves

Address

Any order can be used for block allocations and for slave allocations within each block. Each address is allocated at least one byte (rightmost).

• More than one word is allocated for each slave with more than16 I/O points (using it’s node address).

• The leftmost or rightmost byte of the word is allocated to each slave that has less than 16 I/O points.

98

Master Remote I/O Communications

Section 4-1

4-1-2 Remote I/O Master Specifications

Item

Slave allocation methods

No. of Masters that can be mounted

Fixed allocations

User-set allocations

Specifications

Select one of the following fixed allocation areas using the Fixed Allocated Area Switches 1,

2, and 3 in the software switches in the allocated CIO Area words.

I/O Size Allocated words (CIO

Area)

Fixed Allocation Area Setting 1

Fixed Allocation Area Setting 2

Fixed Allocation Area Setting 3

Output

(OUT) area

64 words 3200 to 3263 3400 to 3463 3600 to 3663

By allocated

DM Area words

By Configurator

Fixed allocations

User-set allocations

By allocated

DM Area words

Input (IN) area

64 words 3300 to 3363 3500 to 3563 3700 to 3763

Select one of the above areas using the software switches. All are fixed at 1 word per node address. The default setting is Fixed Allocation Area Setting 1.

Set the areas and the first words for the OUT 1 and IN 1 blocks in the scan list Setup Table in the allocated DM Area words. Set the allocation size for each slave using the allocation size Setup Table (any words). Allocations must be in the order of node addresses.

Allocated words

The input and output areas can be the following sizes starting from any word in any of the following areas: CIO Area, WR

Area, HR Area, DM, Area, or EM Area.

Output (OUT) area

500 words max.

×

1 block

Input (IN) area

500 words max.

×

1 block

Set the areas for the OUT 1/2 and IN 1/2 blocks, the first words, and the allocation sizes for all slaves using the Configurator. Blocks can be set for nodes in any order.

Allocated words

The input and output areas can be the following sizes starting from any word in any of the following areas: CIO Area, WR

Area, HR Area, DM, Area, or EM Area.

Output (OUT) area

Input (IN) area

500 words max.

×

2 blocks

500 words max.

×

2 blocks

3 Units max. (Unique words must be allocated using the Allocated CIO Area

Words Software Switches.)

16 Units max. (Unique words must be allocated using the user Setup Table in the allocated DM Area words.)

Max. No. of slaves connected per

DeviceNet Unit

By Configurator

Fixed allocations

User-set allocations

By allocated

DM Area words

By Configurator

16 Units max. (Unique words must be allocated using the Configurator.)

63 nodes

Max. No. of I/O points per

DeviceNet Unit

Fixed allocations

User-set allocations

By allocated

DM Area words

By Configurator

2,048 pts (64 input words, 64 output words)

16,000 pts (500 input words x 1 block, 500 output words x 1 block)

32,000 pts (500 input words x 2 blocks, 500 output words x 2 blocks)

99

Master Remote I/O Communications

Section 4-1

Item

Max. No. of I/O per Slave controllable by a

DeviceNet Unit

Fixed allocations

User-set allocations

By allocated

DM Area words

By Configurator

Specifications

2,048 pts (64 input words, 64 output words)

3,200 pts (100 input words, 100 output words)

3,200 pts (100 input words, 100 output words)

4-1-3 Precautions on the Number of Master Units

The following system configurations can be constructed based on various numbers of Master Units when DeviceNet Units are used.

Pattern

Configuration

One Master Unit connected on a single network

Multiple Master Units connected on a single network

Multiple Master Units connected to a single PLC

Yes

A B

Remote I/O communications

Fixed allocations

Userset allocations

By DM

Area words

By

Configurator

Precautions

Same as previous networks.

×

(See note.)

(See note.)

(Up to 3 Master Units can be used.)

• The communications cycle time is longer.

Note

The communications cycle time for the network in the figure above is TA+TB if sections A and B above are separate networks with a communications cycle time of TA and TB.

• Multiple Master Units cannot share a single Slave Unit.

• Bus Off errors (communications stopped by multiple transmissions) may occur if multiple

Master Units with disabled scan lists are present on a single network.

• The cycle time of the PLC is longer.

• Make sure that each word allocated in the system is allocated to only one Master Unit.

Note

Only one Master Unit can be connected to a network if the user specifies a

COS or cyclic connection from the Configurator. Remote I/O communications errors may occur is more than one Master Unit is connected for a COS or cyclic connection.

100

Master Remote I/O Communications

Section 4-1

4-1-4 Procedure for Using Remote I/O Master

Fixed Allocations for Remote I/O

1,2,3...

1.

2.

3.

4.

5.

6.

7.

Turn ON the communications, slave, and PLC power supplies.

Note

Turn ON the communications power supply prior to turning ON the slave power supply or the slaves may not go online.

Switch the CPU Unit to PROGRAM mode.

Turn ON the Master Enable Switch (word n, bit 06). (The master will remain enabled even if the power is turned OFF and back ON again.)

Note

Execute this only when master communications are turned OFF. (If the Master Enable Switch is turned ON when master communications are enabled, a Unit error will occur and a C2 error will be displayed on the 7-segment display on the front panel.)

Perform the following steps to start with the scan list disabled.

Skip to step 5. to re-register and enable the scan list.

Skip to step 6. to start with the scan list enabled without any changes to

the fixed allocations or scan list.

Note

The mode can be confirmed from the dots on the 7-segment display on the Master Unit.

Left dot not lit: Scan list enabled

Left dot flashing: Scan list disabled a) Turn ON a Master Fixed Allocation Setting Switch (word n, bits 08 to

10).

b) Monitor and check the registered slave data area to see if communications are possible with registered slaves.

c) Turn ON the Scan List Enable Switch (word n bit 00) from a Programming Device.

d) Go to step 6.

Perform the following steps to re-register the scan list when starting with the scan list enabled.

a) Turn ON the Scan List Clear Switch (word n, bit 01) from a Programming Device.

b) Turn ON a Master Fixed Allocation Setting Switch (word n, bits 08 to

10).

c) Monitor and check the registered slave data area to see if communications are possible with registered slaves.

d) Turn ON the Scan List Enable Switch (word n, bit 00) from a Programming Device.

Start master remote I/O communications with the scan list enabled. Use the software switches to start or stop communications.

Check to see if both the MS and NS indicators are lit green on the master and all slaves.

Switch the CPU Unit to RUN mode.

8.

User-set Remote I/O Allocations Using DM Area Settings

1,2,3...

1.

Turn ON the communications, slave, and PLC power supplies.

2.

Note

Turn ON the communications power supply prior to turning ON the slave power supply or the slaves may not go online.

Switch the CPU Unit to PROGRAM mode.

101

Master Remote I/O Communications

Section 4-1

3.

4.

5.

6.

7.

8.

Turn ON the Master Enable Switch (word n bit 06). (The master will remain enabled even if the power is turned OFF and back ON again.)

Note

Execute this only when master communications are turned OFF. (If the Master Enable Switch is turned ON when master communications are enabled, a Unit error will occur and a C2 error will be displayed on the 7-segment display on the front panel.)

Set data in the Master User Allocation Setup Table (words m+1 to m+6) and the Allocation Size Setup Table in the DM Area words allocated to the

Unit from the PLC Programming Device.

Turn ON the Master User-set Allocations Switch (word n, bit 11).

Start master remote I/O communications with the scan list enabled. Use the software switches to start or stop communications.

Check to see if both the MS and NS indicators are lit green on the master and all slaves.

Note

The mode can be confirmed from the dots on the 7-segment display on the Master Unit.

Left dot not lit: Scan list enabled

Left dot flashing: Scan list disabled

Switch the CPU Unit to RUN mode.

User-set Remote I/O Allocations Using the Configurator

1,2,3...

1.

Connect the Configurator to the network through a serial line or dedicated

Board/Card.

2.

3.

4.

Turn ON the communications, slave, and PLC power supplies.

Note

Turn ON the communications power supply prior to turning ON the slave power supply or the slaves may not go online.

Switch the CPU Unit to PROGRAM mode.

Perform the following steps to allocate areas, create scan lists, and download the settings to the nodes.

a) Create a network configuration offline on the Configurator.

b) Enable master communications in the CS1W-DRM21(-V1) properties.

c) Create master device parameters.

d) Save the data as a network component file.

Note

If desired, you can also go directly online and download the network component file to the network devices without saving the file.

5.

6.

7.

8.

9.

e) Read the network component file, go online, and download the file to the network devices.

Start master remote I/O communications with the scan list enabled. Use the software switches to start or stop communications.

Check to see if both the MS and NS indicators are lit green on the Master

Unit and all Slave Units.

Note

The mode can be confirmed from the dots on the 7-segment display on the Master Unit.

Left dot not lit: Scan list enabled

Left dot flashing: Scan list disabled

Read the network components using the Configurator.

Save the components as a network component file using the Configurator.

Switch the CPU Unit to RUN mode.

Note

1.

Remote I/O communications with a specified slave can be stopped to effectively disconnect the slave from the network by turning ON the Discon-

102

Scan List

Section 4-2

2.

nect/Connect Switch for that slave (words n+6 to n+9). This can be done when a slave is replaced or to register a slave in the scan list in preparations to connect it to the network at a later time. The Disconnect/Connect

Switches, however, are cleared when the power supply is turned OFF, so the bit must be turned back ON from the ladder program after the power turns ON in order for it to remain effective.

Use Configurator Ver. 2.10 or higher for the CJ1W-DRM21.

4-2 Scan List

A scan list is used to register the slaves with which the Master Unit communicates in DeviceNet remote I/O communications. It is the basis on which the

Master Unit communicates with slaves.

The Master Unit does not contain a scan list by default. The CS/CJ-series

DeviceNet Unit, however, has a default setting that allows it to communicate with all slaves even with the scan list disabled, but this operating mode should not be used for normal operation. Always create a scan list prior to operating the Unit.

Scan List Contents

Node address

Allocated IN/OUT sizes and allocation

Vendor

Item

Device type

Product code

Connection type

Connection path

The contents of the scan list is listed in the following table. When a Master

Unit goes online, it compares each of these items with the slaves that are actually connected to the network. The items that are compared, however, will depend on the allocation method that is used.

Description Fixed allocations User-set allocations using allocated DM

Area words

User-set allocations from the

Configurator

Compared Node address for every Slave

Settings of the number of bytes allocated to every slave in a data area of the Master Unit

Compared

Compared

Unique manufacturer

ID

Unique product type value

Unique product model value

Applicable DeviceNet protocol

(See

Appendix B

DeviceNet Connections

for details.)

Type of slave I/O data

(See

Appendix B

DeviceNet Connections

for details.)

Not compared

Not compared

Not compared

Automatically set

Cannot be set

Compared

Set from Configurator

Set from Configurator

Set from Configurator

Automatically set or set from Configurator

Set from Configurator

103

Scan List

Section 4-2

Creating the Scan List

Note

The way that a scan list is prepared varies with the allocation method as shown below.

Fixed allocations

With the CPU Unit in PRO-

GRAM mode:

1. Turn ON the one of the

Master Fixed Allocation

Setting 1 Switches (1 to

3).

2. Turn ON the Scan List

Enable Switch.

User-set allocations through the allocated DM

Area words area

With the CPU Unit in PRO-

GRAM mode, turn ON the

Master User Allocations

Setup Switch.

User-set allocations through the Configurator

Create a list from the Configurator. (Acquire a list of online devices, use it to create a scan list, and then register the scan list in the

Master Unit.)

1.

2.

Be sure to create a scan list before starting actual system operation.

It is still possible to communicate with Units (with the scan list disabled) if a scan list is not created when fixed allocations areas 1 to 3 are used. This may result in faulty operation because the Master Unit will communicate with slaves even if they do not start up due to problems, such as equipment failure if there is no a scan list.

Scan List Enabled and Scan List Disabled

The scan list must be made. The scan list modes are described here.

Scan List Enabled (Used for Actual Operation)

Scan List Disabled (Used when Changing System

Components)

Remote I/O communications are performed according to the registered scan list and only with slaves that are on the list. A verification error occurs (word n+12, bit 00 in the status area turns ON) if a slave registered on the scan list is not present on the network, if a slave did not start up when remote I/O communications started, or if the number of I/O points did not match the number registered.

Remote I/O communications can be performed with fixed allocations instead of a scan list in order to change a system component. Do not operate without a scan list during actual system operation. Use this mode only to replace a

Master Unit or to change a system component (change a connected slave or a node address).

Note a)

To disable the scan list, turn ON the Scan List Clear Switch (word n, bit 01) during remote I/O communications with the scan list enabled (with fixed allocations, user-set allocations using allocated

DM Area words, or user-set allocations using the Configurator). In all these cases, remote I/O communications are executed using the fixed allocations area that was last used when the list was disabled. All slaves are targeted for remote I/O communications with the scan list disabled.

b)

Slaves that are connected to the network while communications are in progress are also targeted for communications. Errors cannot be confirmed, however, even if there are slaves present that did start up due to problems such as equipment failure because there is no scan list available to check communications against.

The communications cycle time will also be significantly longer than the calculated value.

c)

The scan list is automatically enabled when user-set allocations are set using the allocated DM Area words or the Configurator. If the list is subsequently cleared using a software switch, fixed allocations (1 to 3) will be used for remote I/O communications when the scan list is disabled. Make sure the system has stopped before

104

Fixed Allocations

Section 4-3

you disable the scan list with a Master Unit that is set for user-set allocations. Particularly when multiple Master Units are connected to a single network, communications will not be performed successfully if even one Master Unit on the network is operating with the scan list disabled. Once the list is disabled, the user-set allocations data registered in the Master Unit is lost.

Backing Up the Scan List

A scan list must be created to switch the DeviceNet Unit to operation with the scan list disabled or to replace a DeviceNet Unit. It is important to back up the list using one of the following methods:

Fixed Allocations or Userset Allocations in

Allocated DM Area Words

User-set Allocations from the Configurator

Save the scan list as a backup file on Memory Card by turning ON the Setup

File Backup Switch (word n+1, bit 15) in the words allocated in the CIO Area.

Save the scan list as a backup file on Memory Card or save it either as a network component file and master parameter file using the Configurator. In the preceding cases, turn ON the Setup File Restore Switch (word n+1, bit 14) in the words allocated in the CIO Area to input setup data, such as the scan list backed up on Memory Card, into a DeviceNet Unit.

4-3

4-3-1

Fixed Allocations

Allocated Words

Words in the CS/CJ-series DeviceNet CIO Area in the CPU Unit are allocated.

An area of words can be selected from one of three fixed allocation areas.

Use a Software Switch to select the allocation area.

Each area is comprised of an OUT area that is used to write output data to slaves and an IN area that is used for input from slaves in remote I/O communications.

Area

Fixed allocation area 1

Fixed allocation area 2

Fixed allocation area 3

Area 3

CIO 3600

CIO 3601

CIO 3602

Area 2

CIO 3400

CIO 3401

CIO 3402

OUT area (word)

CIO 3200 to CIO 3263

CIO 3400 to CIO 3463

CIO 3600 to CIO 3663

IN area (word)

CIO 3300 to CIO 3363

CIO 3500 to CIO 3563

CIO 3700 to CIO 3763

Selection method

Turn ON the Master Fixed Allocation Setting

1 Switch (word n, bit 08).

Turn ON the Master Fixed Allocation Setting

2 Switch (word n, bit 09).

Turn ON the Master Fixed Allocation Setting

3 Switch (word n, bit 10).

A maximum of 3 DeviceNet Units can be included as masters in a single PLC because the three allocation areas above are set individually for fixed allocations. The default setting is fixed allocations area 1.

Each OUT/IN area is allocated to a slave according to its node address as shown below. Allocated words are determined by the node address in fixed allocations as shown.

OUT area

Node address

IN area

Area 1

CIO 3200

CIO 3201

CIO 3202

Area 1

CIO 3300

CIO 3301

CIO 3302

Area 2

CIO 3500

CIO 3501

CIO 3502

Area 3

CIO 3700

CIO 3701

CIO 3702

CIO 3661

CIO 3662

CIO 3663

CIO 3461

CIO 3462

CIO 3463

CIO 3261

CIO 3262

CIO 3263

CIO 3361

CIO 3362

CIO 3363

CIO 3561

CIO 3562

CIO 3563

CIO 3761

CIO 3762

CIO 3763

105

Fixed Allocations

Section 4-3

Note

More than one Master Unit can be included in a single PLC with fixed allocations, as shown below (3 Units max.).

Master Unit

Master Unit

Slave

Slave

4-3-2 Procedure

Step 1: Place the CPU Unit in PROGRAM mode.

Step 2: Turn ON the

Master Enable Switch

If the master communications have been disabled (if Master Function Enable

Flag (word n+11, bit 03) is OFF), turn ON the Master Enable Switch (word n, bit 06) to enable master communications. Once Master communications have been enabled by turning this switch ON, it will not change even if the power is turned OFF and back ON again.

Note

If the master communications are enabled (if Master Function Enable

Flag (word n+11, bit 03) is ON), skip this step and go onto the next step. (If the Master Enable Switch is turned ON when master communications are enabled, a Unit error will occur and a C2 error will be displayed on the 7-segment display on the front panel.)

Step 3: Turn ON the Scan

List Clear Switch

If the Unit is in the Scan List Enable mode (if Scan List Disabled Flag (word n+11, bit 04) is OFF), turn ON the Scan List Clear Switch (word n, bit 01) to change to the Scan List Disable mode.

Note

If the Unit is already in the Scan List Disable mode (if the Scan List

Disabled Flag (word n+11, bit 04) is ON), skip this step and go onto the next step. (If the Scan List Clear Switch is turned ON when the

Unit is in the Scan List Disable mode, a Unit error will occur and a C2 error will be displayed on the 7-segment display on the front panel.)

Step 4: Select Fixed

Allocations Area 1 to 3

Word n, bit 09

Word n, bit 10

Turn ON the Master Fixed Allocation Setting 1 to 3 Switch (word n, bits 08 to

10) in the Software Switches in the words allocated in the CIO Area to select the fixed allocations area from1 to 3. One word will be allocated per node address in order of node addresses for the output (OUT) block and one word for the input (IN) block in the CS/CJ-series DeviceNet CIO Area.

First word n = CIO 1500 + (25 x unit number)

Software Switch address

Word n, bit 08

Software Switch name

Master Fixed Allocation

Setting 1 Switch

Master Fixed Allocation

Setting 2 Switch

Master Fixed Allocation

Setting 3 Switch

Fixed allocations area number

Fixed allocations area

1

Allocated

OUT area

CIO 3200 to

CIO 3263

Fixed allocations area

2

CIO 3400 to

CIO 3463

Fixed allocations area

3

CIO 3600 to

CIO 3663

Allocated

IN area

CIO 3300 to

CIO 3363

CIO 3500 to

CIO 3563

CIO 3700 to

CIO 3763

Step 5: Turn ON the Scan

List Enable Switch

Remote I/O communications will start with the scan list disabled after a fixed allocations area has been selected. Check to see if communication is proceeding normally with each slave, and then turn ON the Scan List Enable

Switch (word n, bit 00) to communicate with the scan list enabled.

106

Fixed Allocations

Section 4-3

Bit

CIO 3200

Fixed Allocations Area 1

OUT blocks are allocated to slaves from CIO 3200 to CIO 3263 and IN blocks are allocated to slaves from CIO 3300 to CIO 3363.

CS/CJ-series DeviceNet CIO Area

OUT block

Bit

CIO 3200

CIO 3201

CIO 3202

Address 0

Address 1

Address 2 to to

CIO 3263

OUT block

CIO 3260

CIO 3261

CIO 3262

CIO 3263 to

Address 60

Address 61

Address 62

Address 63

Output to Slaves

Bit

CIO 3300 to

CIO 3363

IN block

IN block

Bit

CIO 3300

CIO 3301

CIO 3302

Address 0

Address 1

Address 2 to to

CIO 3360

CIO 3361

CIO 3362

CIO 3363

Address 60

Address 61

Address 62

Address 63

Input from Slaves

CS/CJ-series DeviceNet CIO Area

Bit

CIO 3400 to

OUT block

Fixed Allocations Area 2

OUT blocks are allocated to slaves from CIO 3400 to CIO 3463 and IN blocks are allocated to slaves from CIO 3500 to CIO 3563.

OUT block

Bit

CIO 3400

CIO 3401

CIO 3402 to

Address 0

Address 1

Address 2 to

Output to Slaves

CIO 3463

CIO 3460

CIO 3461

CIO 3462

CIO 3463

Address 60

Address 61

Address 62

Address 63

IN block

Bit

CIO 3500 to

CIO 3563

IN block

CIO 3500

CIO 3501

CIO 3502 to

CIO 3560

CIO 3561

CIO 3562

CIO 3563

Address 0

Address 1

Address 2 to

Address 60

Address 61

Address 62

Address 63

Input from Slaves

107

Fixed Allocations

Section 4-3

CS/CJ-series DeviceNet CIO Area

Bit

CIO 3600

Fixed Allocations Area 3

OUT blocks are allocated to slaves from CIO 3600 to CIO 3663 and IN blocks are allocated to slaves from CIO 3700 to CIO 3763.

OUT block

Bit

CIO 3600

CIO 3601

CIO 3602

Address 0

Address 1

Address 2 to to

Output to Slaves to

OUT block

CIO 3663

CIO 3660

CIO 3661

CIO 3662

CIO 3663

Address 60

Address 61

Address 62

Address 63

IN block

Bit

CIO 3700 to

CIO 3763

IN block

CIO 3700

CIO 3701

CIO 3702 to

CIO 3760

CIO 3761

CIO 3762

CIO 3763

Address 0

Address 1

Address 2 to

Address 60

Address 61

Address 62

Address 63

Input from Slaves

The Slave allocation order is fixed in the output (OUT) and IN blocks starting from address 0. Each address is allocated at least one byte (rightmost).

• More than one word is allocated for each slave (according to it’s node address) with more than16 I/O points.

• The rightmost byte of the word is allocated to each slave that has less than 16 I/O points.

Note

The table below shows how fixed allocations areas differ between the

C200HW-DM21-V1 DeviceNet Master Unit of the C200H-series, and the

CS1W-DRM21(-V1) DeviceNet Unit of the CS/CJ-series and CJ1W-DRM21

DeviceNet Unit of the CJ-series.

Item C200HW-DRM21-V1

Fixed allocations area

Output area

C200 DeviceNet CIO Area

CIO 0050 to CIO 0099

Input area CIO 0350 to CIO 0399

CS1W-DRM21(-V1)

/CJ1W-DRM21

CS/CJ-series DeviceNet CIO

Area

CIO 3200 to CIO 3263

CIO 3400 to CIO 3463

CIO 3600 to CIO 3663

CIO 3300 to CIO 3363

CIO 3500 to CIO 3563

CIO 3700 to CIO 3763

108

Fixed Allocations

Section 4-3

4-3-3 Changing System Components

The scan list must be cleared in the following situations:

• Adding a slave

• Removing a slave

• Changing a node address

Turn OFF the Scan List Clear Switch (word n, bit 01) to clear the scan list.

Remote I/O communications will be performed with the scan list disabled using fixed allocations in the fixed allocations area that was used the last time the list was disabled. Make sure that communications with all slaves are operating properly after the scan list is cleared and the system component is changed, and then turn ON the Scan List Enable Switch (word n, bit 00) again to register all slaves currently online in the scan list. Remote I/O communications will continue during this time with the scan list enabled.

4-3-4 Fixed Allocations Example

This example shows the allocations that are used when Fixed Allocations 1 are used for the following slaves.

8

9

6

7

0

Node address

1

2

3

4

5

Outputs

0 pts

8 pts

0 pts

16 pts

8 pts

16 pts

0 pts

32 pts

8 pts

Inputs

0 pts

16 pts

0 pts

8 pts

16 pts

48 pts

0 pts

Product

8-pt Transistor Input Terminal

(DRT1-ID08)

8-pt Transistor Output Terminal

(DRT1-OD08)

16-pt Transistor Input Terminal

(DRT1-ID16)

16-pt Transistor Output Terminal (DRT1-OD16)

8-pt Input and 8-pt Output Environment-resistant Terminal

(DRT1-MD16C)

CQM I/O Link Terminal (CQM1-

DRT21)

C200 I/O Link Unit (C200HW-

DRM21) with 48 input pts (3 words)

Analog Output Terminal with 2 output pts (DRT2-DA02)

Resulting Slave Allocation

Slave type

8 inputs

8 outputs

16 inputs

16 outputs

8 inputs, 8 outputs

16 inputs, 16 outputs

32 inputs

(Master)

32 outputs

Allocation

Node address setting

00

01

02

03

04

05

06

07

08

Node address

Output Input

00

0 8

01

02

03

04

05

8

0

16

8

16

0

16

0

8

16

06

07

08

0 32

Master Unit

09

10

11

32

None

See note 1.

0

None

See note 2.

OUT block

CIO

3200

15

Allocation disabled

0

3201

Allocation disabled

Allocated

3202

Allocation disabled

3203

3204

3205

Allocated

Allocation disabled

Allocated

Allocated

3206

3207

3208

3209

3210

3211

Allocation disabled

Allocation enabled

Allocated

Allocated

Not used

Not used

IN block

CIO

3300

15

Allocation disabled

3301

3302

Allocated

Allocation disabled

Allocated

0

3303

3304

3305

Allocation disabled

Allocation disabled

Allocated

Allocated

3306

3307

3308

Allocated

Allocated

Allocation enabled

3309

3310

3311

Allocation enabled

Not used

Not used

63 None None 3263 Not used 3363 Not used

109

Fixed Allocations

Turn ON the Scan List

Enable Switch

Note

Section 4-3

1.

2.

The Master Unit does not require any word allocation and so it can use any available address.

Blocks for which allocation is enabled can be allocated to Slaves as long as the blocks do not overlap.

Turn ON the Scan List Enable Switch (word n, bit 00, CIO 150000 in this example). This will create a scan list based on data for slaves that are actually online and will start remote I/O communications with the scan list enabled.

110

User-set Allocations

Section 4-4

4-4 User-set Allocations

With a CS/CJ-series DeviceNet Unit, remote I/O communications slaves can be allocated in any area (CIO, WR, HR, DM, or EM) using one of the following methods.

• Setting through the allocated DM Area words (Master User Allocations

Table)

• Setting through the Configurator

User-set Allocations Methods

Method

Allocation areas

No. of allocated blocks

Block allocation order

Node address order

Start bit for allocations

Set through the allocated DM Area words (Master User Allocations Table)

CIO: 0000 to 6143

WR: W000 to W511

HR: HR000 to HR511

DM: D00000 to D32767

EM: E00000 to E32767 (Banks 0 to C)

2 blocks: OUT 1 and IN 1

OUT 1 and IN 1 can be created anywhere in the above areas.

Set through the Configurator

4 blocks: OUT 1, IN 1, OUT 2 and IN 2

OUT 1, IN 1, OUT 2, and IN 2 can be created anywhere in the above areas.

Any order

Allocations must be in order of node addresses (0 to 63 in ascending order)

Note

1. Not all nodes need to be allocated, reducing the number of words required.

2. Node addresses do not have to correspond between blocks.

All allocations start from bit 00 (Cannot start from bit 08. All allocations are in 1 word units.)

500 words max.

Any order

Note

1. Node addresses do not have to correspond between blocks.

2. One node address cannot be allocated to different blocks.

Allocations can start from bit 00 or bit 08.

Allocations starting from bit 08 are in

1-byte units only.

1,000 words max. for a total of 2 blocks 2,000 words max. for a total of 4 blocks

The leftmost byte (bits 07 to 15) cannot be used.

Allocation size

Slave allocation limits

Per block

Total size

Slaves with more than 8 points

Slaves with 8 points

Slaves with 16 points

Slaves with more than 16 points

Allocated to the leftmost or rightmost bytes (not allocated a word)

Allocated one word

Allocated multiple words (with an odd number of bytes, only the rightmost byte is allocated in the last word)

Note

Functions will vary as shown below depending on whether allocations are set through the allocated DM Area words (Master User Allocations Table) or through the Configurator.

• Words are always allocated to slaves in order of ascending node addresses when allocations are set with the allocated DM Area words.

The order can be determined by the user when the Configurator is used. (However, even when using the allocated DM Area words, nodes do not have to be allocated words, reducing the number of words required.)

• Only two blocks (OUT 1 and IN 1) can be allocated when setting are made with the allocated DM Area words area, but there are four blocks

(OUT 1/2 and IN 1/2) available with the Configurator.

111

User-set Allocations

Section 4-4

• The first bit for node allocations is always bit 00 when setting allocations with the allocated DM Area words, but can be either bit 00 or bit

08 with the Configurator. (Allocations for slaves with two bytes or more cannot start at bit 08.

Setting through the Allocated DM Area Words (Master User Allocations Table)

All slaves are allocated words in order of node addresses in two blocks: OUT block 1 and IN block 1.

OUT areas

Addresses are in ascending order.

Not all nodes need to be allocated and addresses for nodes with no allocations are skipped.

Area specified in I/O memory

Bit

First word specified

Bit

First word specified

Address 0

Node addresses in ascending order to

Output to Slaves

OUT block 1 to to

Bit

First word specified to

IN block 1

IN areas

Bit

First word specified

Address 0

Node addresses in ascending order

Addresses are in ascending order.

Not all nodes need to be allocated and addresses for nodes with no allocations are skipped.

to to

Input from Slaves

The block allocation order and block allocation areas can be set. Node addresses in each block are allocated words in ascending order from 0 to 63.

Node addresses that are not allocated are skipped (not allocated words).

Each address is allocated at least one byte (rightmost byte, 1 word, or multiple words).

• More than one word is allocated for each slave (according to it’s node address) with more than16 I/O points.

• The rightmost byte of the word is allocated to each slave that has less than 16 I/O points.

Note

Multiple Master Units can be included in a single PLC as shown below using user-set allocations (16 Units max.).

Master Unit

Master Unit

Slave

Slave

112

User-set Allocations

Procedure

Section 4-4

Step 1: Turn ON the Master Enable Switch

Make sure that master communications have disabled by checking to see if

Master Enable Function Flag (word n+11, bit 03) is OFF and then turn ON the

Master Enable Switch (word n, bit 06) to enable master communications.

Once master communications have been enabled by turning this switch ON, they will remain enabled even if the power is turned OFF and back ON again.

Note

Do not turn ON the Master Enable Switch unless master communications are stopped. (If the Master Enable Switch is turned ON when master communications are enabled, a Unit error will occur and a C5 error will be displayed on the 7-segment display on the front panel.)

Step 2: Setting the Master User Allocations Table

This table specifies the area and first word for each block and the area and first word for the Allocation Size Setup Table.

• Master User Allocations Table

Bit m+1 wd m+2 wd

15 08 07

First word m = D30,000+(100 x unit no.)

00

0 0

First word of OUT block 1

OUT block 1 area

Can be set anywhere past here.

m+3 wd m+4 wd m+5 wd m+6 wd

0 0

First word of IN block 1

IN block 1 area

0 0

Area for Allocation

Size Setup Table

First word of Allocation Size Setup Table

Can be set anywhere past here.

Code

00 Hex

01 Hex

03 Hex

04 Hex

05 Hex

08 to 14 Hex

• Areas and Word Ranges for OUT Block 1, IN Block 1, and the Allocation Size Setup Table

Name

---

CIO Area (CIO)

Data Memory (DM)

Work (WR)

HR (HR)

Expansion Data Memory (EM)

Bank 0 to bank C (13 banks)

Word range

The block is not used.

0000 to 17FF Hex (0 to 6143)

0000 to 7FFF Hex (0 to 32767)

0000 to 01FF Hex (0 to 511)

0000 to 01FF Hex (0 to 511)

0000 to 7FFF Hex (0 to 32767) for all banks

Step 3: Setting the Allocation Size Setup Table

Specify the area and first word in this table at words m+5 and m+6. IN and

OUT sizes for all nodes are set here as shown in the table below. The setting range for each node is 0 to 200 bytes (0 to 100 words), although actual size depends on the allocated slaves. The maximum size per block is 500 words. If the size set here is larger than 1 byte, the start bit for all slaves is bit 00 and size is allocated in ascending node address order starting from the beginning of the OUT 1 and IN 1 areas in word units. If the size is set at 0 bytes for a node address, it is skipped the words are allocated to the next address.

• Allocation Size Setup Table

113

User-set Allocations

Section 4-4

l is the first word in the Allocation Size Setup Table and is specified at words m+5 and m+6

Bit 15

I+0

08 07

Node address 0 OUT size (bytes) Node address 0 IN size (bytes)

00

I+1 to

Node address 1 OUT size (bytes) to

Node address 1 IN size (bytes)

I+62

I+63

Node address 62 OUT size (bytes)

Node address 63 OUT size (bytes)

Node address 62 IN size (bytes)

Node address 63 IN size (bytes)

Master User Allocations Table in the allocated DM Area words

Bit m+1 wd m+2 wd m+3 wd m+4 wd m+5 wd m+6 wd

OUT block 1 area

First word of OUT block 1

IN block 1 area

First word of IN block 1

Size Setup Table

Area

First word of Size Setup Table

Step 4: Turn ON the Slave User Allocations Switch

Turn ON the Slave User allocations Switch (word n, bit 11). This will make the

DeviceNet Unit read allocation results data for the slaves above from the CPU

Unit and create a scan list based on data for slaves that are actually online prior to starting remote I/O communications with the scan list enabled.

Note

The Master User Allocations Switch not only reads slave allocation data, but it also enables the scan list.

Specify the first word.

Specify the first word.

Specify the size.

OUT block

Bit

First word specified

Node address 0

Node address 1

Node address 63

Output to Slaves

Set first word.

Allocation Size Setup Table in allocated DM Area words

Bit

I wd

Address 0

OUT size

Address 1

OUT size

Address 0

IN size

Address 1

IN size

I+1 wd to

I+63 wd

Address 63

OUT size

Address 63

IN size

IN block

Bit

First word specified

Node address 0

Node address 1

Input from Slaves

Node address 63

Note

Specify the first word.

1.

2.

Any order can be used for the OUT 1 and IN 1 blocks.

Node addresses do not have to correspond between output block 1 and input block 1.

Example: This is not necessary.

OUT block 1 IN block 1

Node address 01

Node address 01

Node address 02

Node address 02

Node address 03

3.

The start bit for node addresses must always be bit 00, and never bit 08.

114

User-set Allocations

4.

Multiple masters cannot share the same slave.

Master

Master

Section 4-4

5.

Slave

Be sure to use user-set allocations and operate the Master Unit with the scan list enabled if multiple masters are connected to a single network.

Communications will not be possible if there is more than one master with the scan list disabled connected to a network.

Example Settings for User-set Allocations through Allocated DM Area Words

This example uses the following settings for unit number 0.

• OUT block 1 area and first word: WR (04 Hex), 50 (0032 Hex)

• IN block 1 area and first word: WR (04 Hex), 100 (0064 Hex)

• Allocation Size Setup Table area and first word: DM (03 Hex), 00100

(0064 Hex)

This example shows user-set allocations for the following slaves.

0

Node address

1

4

5

2

3

Changing System Components

In the following situations, the table must be reset, the Master User Allocations Switch (word n, bit 11) turned ON, and the scan list recreated:

• Adding a slave

• Removing a slave

• Changing a node address

• Changing a node allocation

There is no need to clear the scan list.

Outputs

16 pts

8 pts

16 pts

0 pts

None

160 pts

0 pts

8 pts

16 pts

8 pts

Inputs

160 pts

Product

16-pt Transistor Output Terminal (DRT1-

OD16)

8-pt input and 8-pt Output Environmentresistant Terminal (DRT1-MD16C)

CQM I/O Link Terminal (CQM1-DRT21)

8-pt Transistor Input Terminal (DRT1-

ID08)

---

CS/CJ-series DeviceNet Unit (CS1W-

DRM21(-V1)) (Slave Unit)

Master User Allocations Table

OUT block 1 area: WR (04 Hex)

First word of OUT block 1: 50 (0032 Hex)

IN block 1 area: WR (04 Hex)

First word of IN block 1: 100 (0064 Hex)

Area for the Allocation Size Setup Table: DM (03 Hex)

First word of the Allocation Size Setup Table: 00100 (0064 Hex)

115

User-set Allocations

Allocation Size Setup Table

OUT sizes specified in the leftmost byte

Address 0 OUT: 2 (bytes)

Address 1 OUT: 1 (bytes)

Address 2 OUT: 2 (bytes)

Address 3 OUT: 0 (bytes)

Address 4 OUT: 0 (bytes)

Address 5 OUT: 20 (bytes)

IN sizes specified in the rightmost byte

Address 0 IN: 0 (bytes)

Address 1 IN: 1 (bytes)

Address 2 IN: 2 (bytes)

Address 3 IN: 1 (bytes)

Address 4 IN: 0 (bytes)

Address 5 IN: 20 (bytes)

Resulting Slave Allocations

OUT area 1

Address 0

Not used Address 1

Address 2

Address 0 allocated two bytes (1 word).

Address 1 allocated 1 byte, leftmost byte is not used.

Address 2 allocated two bytes (1 word).

Address 5

Address 5 allocated 20 bytes (10 words).

Section 4-4

IN area 1

Not used Address 1

Address 2

Not used Address 3

Address 1 allocated 1 byte, leftmost byte is not used.

Address 2 allocated two bytes (1 word).

Address 3 allocated 1 byte, leftmost byte is not used.

Address 5

Address 5 allocated 20 bytes (10 words).

Turning ON the Master User Allocations Switch

Turn ON the Master User Allocations Switch (word n, bit 11, CIO 150011 in this example). The Master User Allocations Switch will read the allocation results data for the above slaves and create a scan list based on data for slaves that are actually online prior to starting remote I/O communications with the scan list enabled.

116

User-set Allocations

Section 4-4

Setting through the

Configurator

Specified area in I/O memory

User-set block order

Bit

First word specified

Slaves can be allocated words in any order for the following blocks: OUT block

1, OUT block 2, IN block 1, and IN block 2.

OUT block 1

User-set block order

Bit

First word specified

Address

Address

Address to

OUT block 1 to to

Address

Address

Address

Address

Output to slaves

Bit

First word specified

IN block 1

Bit

First word specified

Address

Address

Address

User-set block order to

IN block 1 to to

Address

Address

Address

Address

Input from slaves

OUT block 2

User-set block order

Bit

First word specified to

OUT block 2

Bit

First word specified to

IN block 2

Bit

First word specified

Address

Address

Address to

Address

Address

Address

Address

IN block 2

Bit

First word specified

Address

Address

Address to to

Address

Address

Address

Address

Output to slaves

User-set block order

Input from slaves

The block allocation order, block allocation areas, and order of node addresses in each block can be set by the user, each address is allocated at least one byte (rightmost or leftmost byte).

• More than one word is allocated for each slave (according to it’s node address) with more than16 I/O points.

• The leftmost or rightmost byte of the word is allocated to each slave that has less than 16 I/O points.

117

User-set Allocations

Procedure

Section 4-4

Step 1

Set the area, start word, and words allocated for each block using the Configurator.

Step 2

Allocate words to all node addresses in each block as shown below using the

Configurator.

OUT block 1

Node address 00

Node address 00: DRT1-OD16 (16 output pts)

Node address 03

Node address 03: DRT2-DA02 (2 analog output points = 32 bits)

IN block 1

Node address 01: DRT1-ID08 (8 input pts)

Node address 01

Node address 02

Node address 02: DRT1-ID08 (8 input pts)

• Each address is allocated at least one byte (rightmost or leftmost byte).

Note a)

The order of all blocks can be set as desired by the user.

OUT block 1

IN block 2

OUT block 2

IN block 1

b)

Node addresses do not have to correspond between an output block and input block.

Example: This is not necessary.

OUT block 1 IN block 1

Node address 01

Node address 01

Node address 02

Node address 03

Node address 02

c)

The same node address cannot be allocated more than once.

Example:

OUT block 1

Node address 02

OUT block 2

Node address 02

118

User-set Allocations

Section 4-4 d)

The start bit for node addresses can be bit 00 or bit 08. If it is bit

08 however, 2 or more bytes cannot be allocated as shown below.

Start byte

e)

Multiple masters cannot share the same slave.

Master Master

Slave

You can determine whether there are duplicate node addresses in the

I/O allocations (scan lists) that were created simply by conducting a master parameter file duplicate check from the Configurator.

f)

Be sure to use user-set allocations and operate with the scan list enabled if multiple masters are connected to a single network. A

Bus OFF errors will occur if multiple fixed allocations masters operating with the scan list disabled are present on a single network.

g)

Multiple Master Units can be included in a single PLC as shown below using user-set allocations (16 Units max.).

Master Unit

Master Unit

Slave

Slave

Slave types

16 output pts

Combination of 8 input and output pts

Combination of 16 input and output pts

8 input pts

32 output pts

Slave types

48 input pts

8 input pts

Combination of 8 output and 16 input pts

Note

Use Configurator Ver. 2.10 or higher for the CJ1W-DRM21.

Example of User-set Allocations Using the Configurator

IN area

Node address setting

00

01

02

03

10

Node address setting

04

09

12

Node address

04

09

12

Node address

00

01

02

03

10

Allocation status

Output

16 pts

8 pts

16 pts

0 pts

32 pts

Output

0 pts

0 pts

8 pts

Input

0 pts CIO 1950

15

OUT block 1

Allocation (00)

8 pts

16 pts

CIO 1951

Allocation (01)

CIO 1952

Not used

Allocation (02)

00

8 pts

0 pts

CIO 1953

CIO 1954

Allocation

Allocation

(10)

Input

48 pts

8 pts

16 pts

01000

15

OUT area

OUT block 2

Not used

00

Allocation (12)

IN block 1

CIO 1900

15 00

Allocation (02)

CIO 1901

Allocation (01) Allocation (03)

10 wd

11 wd

12 wd

13 wd

14 wd

15 wd

15

IN block 2

00

Allocation

Allocation

Allocation

(04)

Not used

Allocation (12)

Not used

Allocation (09)

119

Starting and Stopping Remote I/O Communications

Section 4-5

Configurator Setting Methods

Refer to the

DeviceNet Configurator Operation Manual

(W382) for setting methods.

4-5 Starting and Stopping Remote I/O Communications

4-5-1 Starting Remote I/O Communications

Remote I/O communications start automatically after the power is turned ON or the Unit is restarted.

The I/O Data Communications Flag (word n+12, bit 15) is turned ON when remote I/O communications is started with at least one slave.

4-5-2 Stopping Remote I/O Communications

Remote I/O communications stop under the following user-controlled conditions. Message communications can still be performed when the remote I/O communications stop.

Stop Communications

With All Slaves

Remote I/O communications stop when the Remote I/O Communications

Stop Switch (word n, bit 04) is turned ON.

Stop Communications

With a Specified Slave

Remote I/O communications stop when the Disconnect/Connect Switch for the desired slave (words n+6 to n+9) is turned ON. (Units are disconnected from remote I/O communication when the Disconnect/Connect Switch is turned ON.)

Note

The communications cycle time is not shorter even though a slave has been disconnected from remote I/O communications by turning ON the Disconnect/

Connect Switch. (Blank time in the communications cycle will only be increased.)

4-5-3 Restarting Remote I/O Communications

Remote I/O communications restart under the following conditions.

Restart Communications with All Slaves

Restart Communications with Specified Slave

Remote I/O communications restart when the Remote I/O Communications

Start Switch (word n, bit 02 or 03) is turned ON. (Only communications with slaves with the Disconnect/Connect Switch turned OFF will be restarted.)

Remote I/O communications restart when the Disconnect/Connect Switch for the desired slave (words n+6 to n+9) is turned OFF. (A slave will participate in remote I/O communications while the Disconnect/Connect Switch is OFF.)

4-6 Example of Ladder Programming for Remote I/O

Communications

When writing ladder programming for remote I/O communications, make sure it performs I/O processing with a Slave under the following conditions:

• The I/O Data Communications Flag (word n+12, bit 15) is ON.

• The Unit Error Flag (word n+10, bit 00) is OFF.

Example: There is no jump and slave I/O is processed when the JMP(004) instruction input condition is ON in the following instructions. There is a jump and slave I/O is not processed when the JMP(004) instruction input condition is OFF.

120

Example of Ladder Programming for Remote I/O Communications

I/O Data Communications

Flag (word n+12, bit 15)

Unit Error Flag

(word n+10, bit 00)

Slave I/O processing

Section 4-6

Note

Even if there is a communications error with the slave, the slave input data is saved in the allocated area.

To prevent operating errors, make the ladder program so that no slave I/O processing will occur when the Unit Error Flag (word n+10, bit 00) is ON.

121

Errors that May Occur in Remote I/O Communications

Section 4-7

4-7

Condition

Error occurs in fixed allocations with the scan list disabled

Errors that May Occur in Remote I/O Communications

The following errors may occur during remote I/O communications.

Error

Structure

Error Flag

(word n+12, bit 04) turns

ON

Error occurs in either fixed or user-set allocations with the scan list enabled

Verification

Error Flag

(word n+12, bit 00) turns

ON

Details Results

Duplicate I/

O area

I/O area range exceeded

Unsupported

Slave

No slaves present

I/O size mismatched

Incorrect vendor

Incorrect device type

Incorrect product code

Incorrect connection bus

Unsupported connection

The same I/O word is allocated to two or more slaves. (This occurs whenever a slave that is allocated multiple words has one of the words allocated to the node address of another Slave.)

A slave is allocated an area outside the fixed allocations area.

(This occurs whenever slaves are allocated multiple words and a slave is allocated a word beyond node address 63 in the fixed allocations area.)

The I/O size of a slave exceeds

200 bytes (100 words). (This occurs if either the IN or the OUT size exceeds 200 bytes.)

A Slave registered in the scan list is not present.

The I/O size registered in the scan list does not match the I/O size of the slave.

Note

I/O size is compared in 8point (1-byte) units. If I/O size is registered at 8 points for example, then an error I/O size mismatch will not occur with a Slave with just one input point connected.

The vendor registered in the scan list does not match the slave vendor.

The device type registered in the scan list does not match the slave device type.

The product code registered in the scan list does not match the slave product code.

The connection bus registered in the scan list is set incorrectly.

The slave does not support the connection registered in the scan list.

Reconnect with the error slave and continue remote I/O communications.

Indicators 7segment display

d0 MS: Not related

NS:

Flashes red d1 d2 d5 d6 d6 d6 d6 d6 d6

122

Errors that May Occur in Remote I/O Communications

Section 4-7

Condition

Fixed or user-set allocations

Error

I/O communications error

Network power error

Send timeout

Duplicated node address

Bus OFF detected

Master scan list logic error

Details Results Indicators 7segment display

d9 A timeout occurred during remote

I/O communications. (The Slave response timed out 6 times in a row or an error occurred 3 times in a row.)

Reconnect with the error Slave and continue remote I/O communications.

*1

The network is not supplying communications power.

A communications request was not successfully completed due to the following reasons:

• There are no devices on the network.

• Baud settings do not match for every node.

• CAN controller error

The master node address is the same address as another node.

Bus OFF error was detected.

The master scan list data is incorrect.

MS: Not related

NS:

Flashes red

MS: Not related

NS: Goes out

All communications stop (remote

I/O communications stop, slave operation stops, and message communications are disabled).

Remote I/O communications stop

(Slave operation stops, but message communications are enabled).

MS: Not related

NS:

Flashes red

MS:

Flashes red

NS: Not related

E0

E2

F0

F1

E8

Note

Remote I/O communications will stop (7-segment display: A0) if DIP switch pin 3 on the front panel is turned ON to specify stopping remote I/O communications for I/O communications errors.

123

Errors that May Occur in Remote I/O Communications

Section 4-7

124

SECTION 5

Remote I/O Slave Communications

This section describes the remote I/O communications performed as a DeviceNet slave by the DeviceNet Unit.

5-1

5-2

5-3

Slave Remote I/O Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-1-1

5-1-2

Allocation Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Remote I/O and Slave Communications Specifications . . . . . . . . . .

5-1-3 Procedures for Using Remote I/O Slave Communications . . . . . . .

Fixed Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-2-1

5-2-2

Allocated Words . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

User-set Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-3-1 Connection Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-3-2

5-3-3

Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Connection Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

126

126

127

127

129

129

129

130

131

131

134

125

Slave Remote I/O Communications

Section 5-1

5-1 Slave Remote I/O Communications

A CS/CJ-series DeviceNet Unit can function as a Slave Unit in remote I/O communications and a single CS/CJ-series DeviceNet Unit can function as both a Master Unit and a Slave Unit. This section describes Slave communications.

Slave Communications

CS/CJ-series DeviceNet Unit (Master)

CS/CJ-series CPU Unit

IN area

OUT area

Remote I/O communications

DeviceNet

IN area

CS/CJ-series CPU Unit

CS/CJ-series DeviceNet Unit (Slave)

OUT area

5-1-1

Slaves

Note

1.

2.

In the following descriptions, the areas used to transfer data from the master to the slaves are called OUT areas and the areas used to transfer data from the slaves to the master are called the IN areas.

In the following descriptions, a CS/CJ-series DeviceNet Unit set to function as a master is referred to as a “Master Unit” and a CS/CJ-series DeviceNet

Unit set to function as a slave is referred to as a “Slave Unit”.

Allocation Methods

All slaves are allocated words in the I/O memory of the CPU Unit to which the

Master Unit is mounted. They are allocated using one of the following methods:

1) Fixed allocations

2) User-set allocations

126

Slave Remote I/O Communications

Section 5-1

5-1-2 Remote I/O and Slave Communications Specifications

Item

Allocation method

Max. No. of I/

O points per

DeviceNet

Unit slave

Fixed allocations

User-set allocations

User-set allocations

Allocated words

(CIO Area)

I/O

Specifications

Select one of the following fixed allocation areas using the Slave Fixed Allocated Area

Switches 1, 2, and 3 in the software switches in the allocated CIO Area words.

Size Fixed Allocation Area

Setting 1

Fixed Allocation Area

Setting 2

Fixed Allocation Area

Setting 3

Output (OUT) area to the slave from the master

3370 3570 3770

Input (OUT) area to the master from the slave

3270 3470 3670

Note

Select one of the preceding areas using the software switches. All are fixed at 1 word per node address. The default setting is Fixed Allocation Area Setting 1.

By allocated DM

Area words

Set the areas, the first words, and slave allocation size for the OUT 1 and IN 1 blocks (total of 2 blocks) using the Slave User Allocation Setup

Table in the allocated DM Area words.

Allocated words The input and output areas can be the following sizes starting from any word in any of the following areas: CIO Area, WR Area, HR Area, DM, Area, or

EM Area.

By Configurator

Fixed allocations

By allocated DM

Area words

By Configurator

Output (OUT) area from this slave

Input (IN) area to this slave

100 words

100 words

Set the areas for the OUT 1 and IN 1/2 blocks, the first words, and the slave allocation sizes using the Configurator.

Allocated words The input and output areas can be the following sizes starting from any word in any of the following areas: CIO Area, WR Area, HR Area, DM, Area, or

EM Area.

Output (OUT) area from this slave

Input (IN) area to this slave

32 points (1 input word, 1 output word)

3,200 pts (100 input words, 100 output words)

100 words

100 words

4,800 pts (100 input words x 2, 100 output words x 1)

5-1-3 Procedures for Using Remote I/O Slave Communications

Fixed Allocations for Remote I/O

1,2,3...

1.

2.

3.

4.

5.

6.

Turn ON the communications, slave, and PLC power supplies.

Note

Turn ON the communications power supply prior to turning ON the slave power supply or the slaves may not go online.

Switch the CPU Unit to PROGRAM mode.

Turn ON the Slave Stop Switch (word n+1, bit 07) from the PLC Programming Device to stop slave communications.

Turn ON one of the Slave Fixed Allocation Setting Switches (1 to 3: word n+1, bits 08 to 10) from a Programming Device.

Turn ON the Slave Enable Switch (word n+1, bit 06) from a Programming

Device to enable slave communications.

Switch the CPU Unit to RUN mode.

Slave remote I/O communications will start up.

Note

Slave communications must be disabled prior to area allocation and must be enabled after area allocation. The order of the procedure is 1) stop slave com-

127

Slave Remote I/O Communications

Section 5-1

munications, allocate areas, and then enable slave communications. The allocated areas will not be valid if the procedure is done in any other order.

User-set Remote I/O Allocations Using DM Area Settings

1,2,3...

1.

2.

3.

4.

5.

6.

Turn ON the communications, slave, and PLC power supplies.

Note

Turn ON the communications power supply prior to turning ON the slave power supply or the slaves may not go online.

Switch the CPU Unit to PROGRAM mode.

Turn ON the Slave Stop Switch (word n+1, bit 07) from the PLC Programming Device to stop slave communications.

Allocate areas as follows: a) Set the Slave User Allocation Setup Table (m+8 to m+13 words) and the Allocation Size Setup Table in the allocated DM Area words from a

Programming Device.

b) Turn ON the Slave User Allocations Switch (word n+1, bit 11) from a

Programming Device.

Turn ON the Slave Enable Switch (word n+1, bit 06) from a Programming

Device to enable slave communications.

Switch the CPU Unit to RUN mode.

Slave remote I/O communications will start up.

Note

1.

2.

Slave communications must be disabled prior to area allocation and must be enabled after area allocation. The order of the procedure is 1) stop slave communications, allocate areas, and then enable slave communications. The allocated areas will not be valid if the procedure is done in any other order.

In fixed allocation or user-set allocations through the allocated DM Area settings, area allocations must be set with slave communications disabled and will be transferred to Units when slave communications are enabled.

User-set Remote I/O Allocations Using the Configurator

1,2,3...

1.

2.

3.

4.

5.

Connect the Configurator to the network through a serial line or dedicated

Board/Card.

Turn ON the communications, slave, and PLC power supplies.

Note

Turn ON the communications power supply prior to turning ON the slave power supply or the slaves may not go online.

Switch the CPU Unit to PROGRAM mode.

Perform the following steps to allocate areas, create scan lists, and download the settings to the nodes.

a) Enable slave communications in CS1W-DRM21(-V1) or CJ1W-

DRM21 properties using the Configurator.

b) Create the device parameters to set slave communications.

c) Save the data as a device parameter file.

Note

If desired, you can also go directly online and download the device parameter file to the DeviceNet Unit slave without saving the file.

d) Read the device parameter file, go online, and download the file to the

DeviceNet Unit slave

.

Switch the CPU Unit to RUN mode.

Slave remote I/O communications will start up.

128

Fixed Allocations

Note

Section 5-2

1.

2.

Enable slave communications in CS1W-DRM21(-V1) or CJ1W-DRM21 properties if the Configurator is used.

Use Configurator Ver. 2.10 or higher for the CJ1W-DRM21.

5-2 Fixed Allocations

5-2-1 Allocated Words

Words in the CS/CJ-series DeviceNet CIO Area in the CPU Unit are allocated.

Words can be selected from one of three fixed allocation areas. Use a Software Switch to select the allocation area.

Each area is comprised of an OUT area that is used to write data to the master IN area and an IN area that is used for inputs from the master OUT area in remote I/O communications.

Area

Fixed allocation area 1

OUT area

(master to slave)

CIO 3370

IN area

(slave to master)

CIO 3270

Selection method

Fixed allocation area 2

Fixed allocation area 3

CIO 3570

CIO 3770

CIO 3470

CIO 3670

Turn ON the Slave Fixed Allocation Setting 1 Switch (word n, bit 08).

Turn ON the Slave Fixed Allocation Setting 2 Switch (word n, bit 09).

Turn ON the Slave Fixed Allocation Setting 3 Switch (word n, bit 010).

A maximum of 3 DeviceNet Units can be included as slaves in a single PLC because the three allocation areas above are set individually for fixed allocations. The default setting is fixed allocations area 1.

5-2-2 Procedure

Step 1: Stop Slave

Communications

If the Unit is already functioning as a Slave Unit, turn ON the Slave Stop

Switch (word n+1, bit 07) to stop slave communications. This step is not necessary if slave communications have already stopped.

Step 2: Select a Fixed

Allocation Area

Software switch address

Word n+1, bit 08

Turn ON one of the Slave Fixed Allocation Setting Switches (1 to 3: word n+1, bits 08 to 10) in the allocated CIO Area words to select a fixed allocation area between 1 and 3. One words is allocated for the output (OUT) area from the

Slave Unit to the master and another word is allocated for the input (IN) area from the master to the Slave Unit in the CS/CJ-series DeviceNet CIO Area, as shown below.

First word n = CIO 1500 + (25 x unit number)

Software switch name Fixed allocation area

Fixed allocation area 1

Allocated output

(OUT) area

(master to slave)

CIO 3370

Allocated input (IN) area

(slave to master)

CIO 3270

Word n+1, bit 09

Word n+1, bit 10

Slave Fixed Allocation

Setting 1 Switch

Slave Fixed Allocation

Setting 2 Switch

Slave Fixed Allocation

Setting 3 Switch

Fixed allocation area 2

Fixed allocation area 3

CIO 3570

CIO 3770

CIO 3470

CIO 3670

Step 3: Turn ON the Slave

Enable Switch

Turn ON the Slave Enable Switch (word n+1, bit 06). This will allocated the fixed allocation areas as slave areas and the DeviceNet Unit will start slave remote I/O communications. Slave communications will run automatically after that whenever the power is turned ON.

129

User-set Allocations

Section 5-3

Fixed Allocation Area 1

CS/CJ-series DeviceNet CIO Area

Bit

CIO 3370

Slave

15

Output (OUT) area

0

Bit

CIO 3270

15

Input (IN) area

0

Fixed Allocation Area 2

CS/CJ-series DeviceNet CIO Area

Bit

CIO 3570

Slave

15

Output (OUT) area

0

Bit

CIO 3470

15

Input (IN) area

0

Fixed Allocation Area 3

CS/CJ-series DeviceNet CIO Area

Bit

CIO 3770

Slave

15

Output (OUT) area

0

Bit

CIO 3670

15

Input (IN) area

0

Master

OUT area

IN area

Master

OUT area

IN area

Master

OUT area

IN area

5-3 User-set Allocations

With a CS/CJ-series DeviceNet Unit, remote I/O communications slaves can be allocated in any area (CIO, WR, HR, DM, or EM) using one of the following methods.

• Setting through the allocated DM Area words (Slave User Allocations

Table)

• Setting through the Configurator

User-set Allocations Methods

Method

Allocation areas

No. of allocation blocks

Allocation size Per block

Total size

Connection type

Set through the allocated DM Area words (Master User Allocations Table)

CIO: 0000 to 6143

WR: W000 to W511

HR: HR000 to HR511

DM: D00000 to D32767

EM: E00000 to E32767 (Banks 0 to C)

2 blocks: OUT 1 and IN 1

100 words max.

200 words max. for a total of 2 blocks

Automatic (connection specified by the master)

Set through the Configurator

3 blocks: OUT 1, IN 1 and IN 2

300 words max. for a total of 3 blocks

Automatic or user specified

Note

1.

Functions will vary as shown below depending on whether allocations are set through the allocated DM Area words (Slave User Allocations Table) or through the Configurator.

130

User-set Allocations

Section 5-3

2.

Only two blocks (OUT 1 and IN 1) can be allocated when setting are made with the allocated DM Area words area, but there are three blocks (OUT 1 and IN 1/2) available with the Configurator.

Setting through the Allocated DM Area Words (Slave User Allocations Table)

Words can be allocated for the OUT 1 area (master to Slave Unit) and IN 1 area (Slave Unit to master) from any specified I/O memory location specified in the settings in the allocated DM area words.

Specified area in I/O memory

Master

Slave

Bit

First word specified

15 0

OUT 1 area OUT area to

Bit

First word specified

15 to

IN 1 area

0

IN area

5-3-1

5-3-2

Connection Types

The type of connection cannot be specified when the allocated DM area words is used for settings. The master specifies a poll, bit-strobe, COS, or cyclic connection.

Procedure

Step 1: Stop Slave Communications

If the Unit is already functioning as a slave, turn ON the Slave Stop Switch

(word n+1, bit 07) to stop slave communications. This step is not necessary if slave communications have already stopped.

Step 2: Set the Slave User Allocations Table

This table is used to specify the areas, first words, and sizes for OUT block 1 and IN block 1.

• Slave User Allocations Table

First word m = D30000 + (100 x unit number)

Allocated DM area words

Word m+8 Bits 00 to 07

Word m+9 Bits 00 to 15

Word m+10

Word m+11

Word m+12

Word m+13

Bits 00 to 07

Bits 00 to 07

Bits 00 to 15

Bits 00 to 07

Details

Slave OUT 1 area

First word of the slave OUT 1 area

Slave OUT 1 area size (in bytes)

Slave IN 1 area

First word of the slave IN 1 area

Slave IN 1 area size (in byte)

Select from following table

Select from following table

131

User-set Allocations

Section 5-3

• Areas and Word Ranges for the OUT 1/IN 1 Areas

Code

00 Hex

01 Hex

03 Hex

04 Hex

05 Hex

08 Hex to

14 Hex

Name

---

CIO Area (CIO)

DM Area (DM)

Word Area (WR)

Holding Area (HR)

Expansion Data Memory (EM)

Bank 0 to C (13 banks)

Word range

The block is not used.

0000 to 17FF Hex (0 to 6143)

0000 to 7FFF Hex (0 to 32767)

000 to 01FF Hex (0 to 511)

000 to 01FF Hex (0 to 511)

0000 to 7FFF Hex (0 to 32767) for all banks

Step 3: Turn ON the Slave User Allocations Switch

Turn ON the Slave User Allocations Switch (word n+1, bit 11).

Step 4: Turn ON the Slave Enable Switch

Turn ON the Slave Enable Switch (word n+1, bit 06). This will allocated the above areas as slave areas and the DeviceNet Unit will start slave remote I/O communications.

Note

Once slave communications are enabled by turning ON the Slave Enable

Switch, the Unit will continue to perform slave communications even after the power is turned OFF and back ON again.

Slave User Allocations Table in the Allocated DM Area Words

Slave output (OUT) area

Bit

Word m+8

Word m+9

Word m+10

Word m+11

Word m+12

Word m+13

OUT 1 area

First word of the OUT 1 area

OUT 1 area size

IN block 1 area

First word of the IN 1 area

IN 1 area size

Specify the first word.

Specify the size.

Specify the first word.

Bit

First word specified to to

Master

OUT area

Specify the size.

Slave input (IN) area

Bit

First word specified to to

Master

IN area

Specify the first word.

Specify the size.

Example Settings for User-set Allocations through Allocated DM Area Words

This example uses the following settings for unit number 0.

• OUT block 1 area and first word: WR (04 Hex), 50 (0032 Hex), 20-byte size (14 Hex, 10 words)

• IN block 1 area and first word: WR (04 Hex), 100 (0064 Hex), 10-byte size (0A Hex, 5 words)

132

User-set Allocations

Section 5-3

• Slave User Allocations Table

OUT block 1 area: WR (04 Hex)

First word of OUT block 1: 50 (0032 Hex)

OUT block 1 size: 20 bytes (14 Hex, 10 words)

IN block 1 area: WR (04 Hex)

First word of IN block 1: 100 (0064 Hex)

IN block 1 size: 10 bytes (0A Hex, 5 words)

• Slave areas

OUT area 1

IN area 1 to

Step 1: Turn ON the Slave User Allocations Switch

Make sure that slave communications have stopped prior to performing this operation. Turn ON the Slave User Allocations Switch (word n+1, bit 11:

CIO 150111 in this example). This will allocate the above areas as slave areas and the DeviceNet Unit will start slave remote I/O communications.

Step 2: Turn ON the Slave Enable Switch

Turn ON the Slave Enable Switch (word n+1, bit 06: CIO 150106 in this example). This will allocate the above areas as slave areas and the DeviceNet Unit will start slave remote I/O communications.

133

User-set Allocations

Setting through the

Configuration

Section 5-3

A maximum of three blocks can be allocated at any locations in I/O memory for the output (OUT) area block 1, input (IN) area block 1, and input (IN) area block 2.

Specified area in I/O memory

User-set block order

Bit

First word specified

15 0

Master

Slave output

(OUT) area 1

OUT area to

Bit

First word specified

15 to

Slave input

(IN) area 1

0

IN area

Bit

First word specified

15 to

Slave input

(IN) area 2

0

IN area

5-3-3

The block allocation order and block allocation areas can be set as required.

Refer to the

DeviceNet Configurator Operation Manual

(W382) for details on the allocation procedure.

Connection Types

The type of connection can be specified if the Configurator is used for settings. The number of applicable allocation areas varies with the type of connection used.

• A maximum of three areas (OUT 1, IN 1, and IN 2) can be used when multiple connections are specified.

• Two allocation areas (OUT 1 and IN 1) can be used if the automatic connection setting or a single connection is specified.

134

User-set Allocations

Section 5-3

Connection Types and Allocated I/O Areas

The following table shows the relationship between various connection combinations and the allocated areas that are applicable with those connections.

IN 1 area IN 2 area Specified connection type

Poll

Bit-strobe

COS

Cyclic

Poll+bit-strobe

Poll+COS (See note.)

Poll+cyclic (See note.)

COS+bit-strobe

Cyclic+bit-strobe

OUT 1 area

Poll OUT data

Not used

COS OUT data

Cyclic OUT data

Poll OUT data

Poll/COS OUT data

Poll/cyclic OUT data

COS OUT data

Cyclic OUT data

Poll IN data

Bit-strobe IN data

COS IN data

Cyclic IN data

Poll IN data

Poll IN data

Poll IN data

COS IN data

Cyclic IN data

Not used

Not used

Not used

Not used

Bit-strobe IN data

COS IN data

Cyclic IN data

Bit-strobe IN data

Bit-strobe IN data

Note

1.

2.

With poll + COS connections, the OUT data is the same for poll and COS.

Set the same OUT areas for poll and COS connections when specifying the areas with the Configurator. With poll + cyclic connections as well, the

OUT data is the same for poll and cyclic. Set the same OUT areas for poll and cyclic when specifying the areas with the Configurator.

Use Configurator Ver. 2.10 or higher for the CJ1W-DRM21.

135

User-set Allocations

Section 5-3

136

SECTION 6

Message Communications

This section describes message communications using FINS commands sent from the ladder program in the CPU Unit of the PLC.

6-1

6-2

6-3

6-4

6-5

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-1-1

6-1-2

Outline of Message Communications. . . . . . . . . . . . . . . . . . . . . . . .

FINS Message Communications . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-1-3

6-1-4

6-1-5

6-1-6

Explicit Message Communications . . . . . . . . . . . . . . . . . . . . . . . . .

Message Communications Specifications . . . . . . . . . . . . . . . . . . . .

Message Communications Error Indications . . . . . . . . . . . . . . . . . .

Message Monitoring Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-1-7 Message Communications Errors . . . . . . . . . . . . . . . . . . . . . . . . . . .

FINS Commands and Responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-2-1

6-2-2

FINS Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Sending/Receiving FINS Command/Responses. . . . . . . . . . . . . . . .

6-2-3

6-2-4

Units Supporting FINS Communications . . . . . . . . . . . . . . . . . . . . .

FINS Command Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Using FINS Message Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-3-1 Setting Node Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-3-2

6-3-3

6-3-4

6-3-5

Creating Routing Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Data Send/Receive Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Sending FINS Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Using SEND(090), RECV(098), and CMND(490) . . . . . . . . . . . . .

6-3-6 Connecting Networks for FINS Communications . . . . . . . . . . . . . .

Sending Explicit Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-4-1

6-4-2

Sending Explicit Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Sending Explicit Messages Using CMND(490). . . . . . . . . . . . . . . .

Receiving Explicit Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-5-1 List of PLC Object Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

147

147

149

149

144

145

145

146

138

138

139

141

142

143

144

160

161

162

164

149

152

154

155

168

169

137

Overview

Section 6-1

6-1

6-1-1

Overview

Message communications enable messages to be set between nodes on a

DeviceNet network when required by system conditions. The messages can be sent between PLCs, between an OMRON PLC and a master made by another company, or between slaves. They can be used to send/receive data; read time data, error histories, and other data; or control operation, e.g., by force-setting/resetting bits.

There are two types of messages: FINS messages and explicit messages.

Outline of Message Communications

Item

Outline

Remote device

Features

FINS messages

Message communications for

OMRON products that use the

FINS protocol.

OMRON PLCs (with a CS/CJseries DeviceNet Unit)

Provide a greater range of services than explicit messages by sending and receiving FINS commands.

Have message compatibility with other OMRON networks, such as

Controller Link, SYSMAC LINK, and Ethernet (up to 3 levels)

Explicit messages

General-purpose message communications using the DeviceNet protocol.

Other manufacturer masters or slaves.

OMRON PLCs with C200H or

CVM1/CV-series DeviceNet Master

Unit or CS/CJ-series DeviceNet

Units

OMRON PLCs with C200H I/O

Link Units

Enable message communications with DeviceNet devices from other manufacturers.

Can receive explicit messages from OMRON PLCs with C200H- or CVM1/CV-series DeviceNet

Master Units and can send explicit messages to OMRON PLCs with

C200H I/O Link Units

FINS communications function

Send

Receive

Message communications functions

Explicit message communications function

Send

Receive

138

Overview

Overall Structure

CPU Unit

CMND(490) instruction

CMND(490) instruction

(2801 Hex)

FINS message

FINS Explicit message

DeviceNet Unit

FINS message function

Explicit message function

Section 6-1

DeviceNet network

OMRON special message communications

FINS message

DeviceNet message communications

Explicit message

6-1-2

Type of FINS message

Network communications instructions

PLC to PLC (both must be CS/CJ-series PLCs with a CS/CJ-series

DeviceNet Unit) (See note 1.)

Note

Inter-network communications is possible with other DeviceNet networks, Controller Link networks, or other networks. (See note 2.)

Note

If only the message communications function is being used and the remote

I/O communications function is not being used, message communications are possible even if the master function is disabled. In this case, it is not necessary to register a scan list.

FINS Message Communications

Messages can be exchanged using FINS commands between DeviceNet nodes (masters and/or slaves) that support FINS messages.

Data send/receive

SEND/RECV instructions

CS/CJ-series PLC CS/CJ-series PLC

FINS commands

CMND(490) instructions

CS/CJ-series PLC CS/CJ-series PLC

Command to

Master Unit

Command

CS/CJ-series PLC

Command to

CPU Unit

Command

PLC to OMRON Slave

CS/CJ-series PLC

CS/CJ-series PLC

Slave

Data length (excluding command code)

SEND instruction: 267 words; RECV instruction: 269 words

542 bytes max.

Command

Slave

139

Overview

Section 6-1

Note

1.

2.

The DeviceNet Unit must be registered in the local network routing table of the CS/CJ-series PLC when two or more Communications Units (including the DeviceNet Unit) are mounted to a CS/CJ-series PLC. The commands will not be sent if the Unit is not registered in the routing tables.

For DeviceNet networks connected to a CS/CJ-series DeviceNet Unit, message communications can be conducted between networks, including other DeviceNet networks as well as Controller Link, SYSMAC LINK, and

Ethernet networks. Up to three levels of networks can be crossed. Routing tables (containing local network tables and relay network tables) must be registered in the CPU Units of each PLC on the network.

Up to 3 network levels, including DeviceNet, can be crossed.

Controller Link Unit

Controller Link Unit

CS/CJ-series DeviceNet Unit

CS/CJ-series CPU Unit

Remote I/O communications

CS/CJ-series DeviceNet Unit

DeviceNet

Controller Link

DeviceNet

CS/CJ-series DeviceNet Unit

Note

FINS commands sent and received by the CS/CJ-series DeviceNet

Unit include commands addressed to the CS/CJ-series CPU Unit and commands addressed to the CS/CJ-series DeviceNet Unit.

FINS message communications is possible between two PLCs with CS1W-

DRM21(-V1) or CJ1W-DRM21 DeviceNet Units.

FINS messages cannot be sent or received for PLCs with C200H-series

DeviceNet Master Units (C200HW-DRM21-V1) or CVM1/CV-series

DeviceNet Master Units (CVM1-DRM21-V1). Explicit messages, however, can be received from these PLCs.

The following table outlines which CPU Unit support for FINS message communications.

CPU Unit sending message

CS Series

CJ Series

CS Series

C200HX/

HG/HE

CVM1/CV

Series

Mounted

DeviceNet

Unit/

DeviceNet

Master Unit

FINS message

Instructions to send/ receive data

SEND/RECV

Instructions to execute any FINS command

CMND

CS

Series

CS1W-

DRM21

(-V1)

Can receive

CPU Unit in receiving message

CJ Series CS

Series

C200HX/

HG/HE

CJ1W-

DRM21

C200HW-

DRM21-

V1

C200HW-

DRM21-

V1

CVM1/CV

Series

CVM1-

DRM21-

V1

Cannot receive

Cannot receive

Cannot receive

CS1W-

DRM211(-V1)

CJ1W-

DRM21

C200HW-

DRM21-V1

C200HW-

DRM21-V1

CVM1-

DRM21-V1

Not supported

Not supported

SEND/RECV

IOWR

IOWR

CMND

Cannot receive

Cannot receive

Cannot receive

Can receive

Can receive

Can receive

Can receive

Can receive

Can receive

Can receive

Can receive

Can receive

140

Overview

Section 6-1

CS1W-DRM21(-V1)

CJ1W-DRM21

CS/CJ-series

CPU Unit

Sending FINS Message Communications

CS1W-DRM21(-V1)

CJ1W-DRM21

C200HW-DRM21-V1

CVM1-DRM21-V1

CS/CJ-series

CPU Unit

Command can be sent.

DeviceNet

Command cannot be sent.

Command cannot be sent.

X

X

C200HX/HG

/HE(-Z)

CPU Unit

CVM1/CVseries

CPU Unit

CS1W-DRM21 (-V1)

CJ1W-DRM21

Receiving FINS Message Communications

CS1W-DRM21 (-V1)

CJ1W-DRM21

C200HW-DRM21-V1

CVM1-DRM21-V1

6-1-3

CS/CJ-series

CPU Unit

CS/CJ-series

CPU Unit

C200HX/HG/

HE(-Z) CPU

Unit

CVM1/CVseries

CPU Unit

Command can be received

X

X

DeviceNet

Command cannot be received

Command cannot be received

Note

C200H-series DeviceNet Master Units (C200H-DRM21-V1) and CVM1/CVseries DeviceNet Master Units (CVM1-DRM21-V1) both support FINS message communications but it is executed by a special OMRON method. With this CS/CJ-series DeviceNet Unit (CS1W-DRM21(-V1) or CJ1W-DRM21), the standard message protocol for DeviceNet (i.e., explicit messages) has been used for FINS communications. For this reason, FINS communications is not possible between CS/CJ-series DeviceNet Units (CS1W-DRM21(-V1) or

CJ1W-DRM21) and C200H-series DeviceNet Master Units (C200H-DRM21-

V1) or CVM1/CV-series DeviceNet Master Units (CVM1-DRM21-V1).

Explicit Message Communications

Service requests can be sent to C200H I/O Link Units and other OMRON slaves, PLCs with CS/CJ-series DeviceNet Units, and DeviceNet masters and slaves made by other manufacturers using explicit messages defined for

DeviceNet.

Service requests to read/write CPU Unit status I/O memory can also be received from PLCs with C200H-series DeviceNet Master Units (C200HW-

DRM21-V1), PLCs with CVM1/CV-series DeviceNet Master Units (CVM1-

DRM21-V1), PLCs with CS/CJ-series DeviceNet Units, and DeviceNet masters made by other manufacturers using explicit messages.

141

Overview

Section 6-1

Note

A specific FINS command (command 2801) is used to send explicit messages.

Item

Network communications instruction

Remote devices and supported functions

Sending

CMND(490) using FINS command code 2801 Hex can be used to send explicit messages to

DeviceNet devices. (See note.)

Masters/slaves made by other manufacturers. Supported services determine supported functions.

PLCs with CS/CJ-series DeviceNet Units mounted.

Remote CPU Unit status read/write and I/O memory read/write functions supported.

PLCs with C200H I/O Link Units mounted. Remote

CPU Unit I/O memory read/write function supported.

Receiving

Automatically responds to explicit messages from other devices.

Masters made by other manufacturers.

PLCs with CS/CJ-series DeviceNet Units.

PLCs with C200H-series DeviceNet Master

Units.

PLCs with CVM1/CV-series DeviceNet Master

Units.

All listed devices support status read/write and I/

O memory read/write for the local CPU Unit.

Note

A specific FINS command (command 2801) is used to send explicit messages.

Note

This CS/CJ-series DeviceNet Unit (CS1W-DRM21(-V1) or CJ1W-DRM21) contains a PLC Object so that the I/O memory of the CPU Unit of the

DeviceNet Unit can be read/written from other devices. The C200HW-DRT21

I/O Link Unit also contains a PLC Object so that the I/O memory of the CPU

Unit of the I/O Link Unit can be read/written from other devices. The C200HW-

DRM21-V1 and CVM1-DRM21-V1 DeviceNet Master Units, however, do not have PLC Objects, the I/O memory of the CPU Unit for these Units cannot be read or written from other devices.

6-1-4 Message Communications Specifications

Applicable PLC

Unit model number

Item

Max. No. of communications nodes per Unit

Communications instructions

Sources: destinations

FINS messages

Explicit messages

Sending/ receiving data

FINS commands

Explicit

DeviceNet messages

Data length (excluding command code)

Specification

CS/CJ-series

CS1W-DRM21(-V1)/CJ1W-DRM21

62 (node address 0 cannot be used for FINS communications)

63

SEND and RECV instructions

CMND(490) instruction

There are FINS commands addressed to the PLC and others addressed to the CS/CJ-series DeviceNet Unit.

Note

FINS commands can be sent to PLCs with CS/CJ-series DeviceNet

Units mounted to them. FINS commands cannot be sent to PLCs with C200HW-DRM21-V1 or CVM1-DRM21-V1 DeviceNet Master

Units mounted to them.

CMND(490) instruction

Sends explicit messages to masters/slaves made by other manufacturers,

PLCs with C200H I/O Link Units, or PLCs with CS/CJ-series DeviceNet

Units mounted to them.

1:1 (Broadcasting is not supported)

SEND:

RECV:

CMND

267 words max.

269 words max.

542 bytes max.

142

Overview

Section 6-1

Item

No. of simultaneous instructions

Response monitoring time

Specification

One each for 8 ports (ports 0 to 7)

Refer to

3-25 Network Instructions

in the

CS/CJ Series Programmable

Controllers Instructions Reference Manual

(W340) for information on ports

(logical ports).

Default setting:

User setting:

2 s

0.1 to 6553.5 s

0 to 15

Supported (Data send/receive or FINS commands).

Retries

FINS message communications commands

Received from CS/CJseries CPU Unit with CS/

CJ-series DeviceNet Unit

Received from CVM1/CVseries CPU Units with

CVM1/CV-series DeviceNet

Master Unit

Not supported.

Received from CS/CJseries and C200HX/HG/HE

CPU Units with C200Hseries DeviceNet Master

Unit

Received from C200HX/HG/

HE Units with C200H-series

DeviceNet Master Unit

Internetwork connections Same network type

Different network type

Supports internetwork communications between DeviceNet networks with

CS/CJ-series DeviceNet Units mounted (up to 3 levels).

Supports internetwork communications between DeviceNet networks with

CS/CJ-series DeviceNet Units mounted and other networks (Controller

Link, SYSMAC LINK, and Ethernet; up to 3 levels).

Message monitor timer function (explicit message communications)

The response monitoring time for DeviceNet Units during explicit message communications (the interval the explicit connection is open) can be set from the Configurator for each device. (The settings for all devices can be stored in the DeviceNet Unit. This is called the Message Monitoring Timer

List.)

6-1-5 Message Communications Error Indications

There are two ways to obtain information on communications errors that occur in message communications: 1) Using the error history in the DeviceNet Unit and 2) Using DeviceNet Unit displays, indicators, and Master Status Areas.

1,2,3...

1.

Each time a communications error occurs, an error code is placed in an error record in the error history kept in the RAM of the DeviceNet Unit. Up to

96 records can be stored in the error history. The time and data the record occurred is also recorded.

The error history can be read or cleared from the CPU Unit by sending an

FINS command to the DeviceNet Unit (Error History Read/Clear). The contents of the error history can also be monitored from the Configurator.

Code

Code

Code

96 records

FINS command

Read-out

Monitor

CPU Unit

Configurator

2.

The MS and NS indicators and the 7-segment display on the front panel of the DeviceNet Unit can be used together with the Master Status Area 1 in the CPU Unit to obtain information on a communications error that has occurred. This information can be used as the basis for troubleshooting.

143

Overview

Section 6-1

Example:

Routing table error

Flashing red

Not relevant

Master Status Area 1

6-1-6

6-1-7

Device-

Net Unit

CPU

Unit

Message Monitoring Timer

A message monitoring timer monitors responses for the DeviceNet Unit. A timer can be set for each device that will be communicated with (each message destination).

Message monitoring timers are supported for both explicit message and FINS message communications. The timers can be set with version 2 or higher of the DeviceNet Configurator. The default setting is 2 seconds (2,000 ms). The setting range is 500 to 30,000 ms.

If the response from the remote communications device (message destination) is slow, the timer setting must be increased. In particular, responses take time in FINS message communications that cross different network layers, so this setting must be increased. The next message cannot be sent to the same communications device during the response waiting time, so the setting should not be set too high.

The DeviceNet Unit uses this timer to monitor message timeouts. The CPU

Unit performs the monitoring based on the response monitoring time for

CMND, SEND(090), and RECV instructions. There will be no effect, therefore, if either the message monitoring timer or the response monitoring time for

CMND/SEND/RECV instructions setting only is increased or decreased. Both must be increased or decreased for there to be an effect.

Set the response monitoring time for the CMND, SEND(090), and RECV instructions the same as or longer than the message monitoring timer, i.e.,

CMND, SEND(090), RECV instructions

≥ message monitoring timer.

If a lot of timeouts occur, maintain this relationship but lengthen the time for both.

Note

When performing remote programming or monitoring from the CX-Programmer (scheduled to be supported by version 2.1 and later), set the message monitoring timer in the CS/CJ-series DeviceNet Unit mounted to the PLC connected to the CX-Programmer to at least 20 s (20,000 ms). This setting is required only for the Unit that will perform remote programming.

Message Communications Errors

The following table shows the main errors that occur when messages are sent or received. Refer to

SECTION 9 Troubleshooting and Maintenance

for coun-

144

FINS Commands and Responses

Section 6-2

Network power error

Send timeout

Routing table error

Node address duplicated

Bus Off detected

Error

CPU Unit service monitoring error

Other CPU error

Local node not part of network; cannot send

No. of retries limit exceeded; cannot send

Remote device busy; cannot send

Header error; cannot send

Reception buffer full; message destroyed

Illegal message received; received message destroyed

Local node busy; cannot send termeasures and errors recorded in error history that are not shown by the indicators.

MS

No change

Flashing red No change

No change

Flashing red Not lit

No change

Indicators

NS

Not lit

Lit red

No change

HE

H7

No change

Unit status 1

(word n+10)

7-segment display

E0

E2

HC

F0

F1

Bit 07 turns

ON.

Bit 08 turns

ON.

Bit 12 turns

ON.

Bit 06 turns

ON.

Bit 05 turns

ON.

––

––

Error history code (Hex)

0341

0342

021A

0211

0340

0002

0006

0101

0103

0109

0112

0117

0118

0119

Note

1.

2.

The 7-segment display alternately displays the error and the master node address where the error occurred.

The send response message or reception response message will be destroyed if any of the following occur:

• If any communications instructions (SEND(090), RECV(098), or

CMND) are executed from the PLC at intervals less than the message communications time.

• If messages are received from other nodes at intervals less than the message communications time.

Be sure that the interval between sending messages (i.e., the interval for executing communications instructions from the PLC) and the interval for receiving messages at any one node are longer than the message com-

munications time. Refer to

8-2 Message Communications

for details on the

message communications time.

6-2

6-2-1

FINS Commands and Responses

FINS Communications

The FINS communication protocol was developed by OMRON for use with factory automation control devices. FINS communications enable PLC memory read/write and operation control without extensive programming in the user program in the PLC. FINS communications use an independent system of addresses that does not rely on the addresses used in the DeviceNet network. This enables communications not only with nodes on the DeviceNet network, but also with devices and PLCs connected via other FA networks, such as the SYSMAC NET and SYSMAC LINK Networks.

145

FINS Commands and Responses

6-2-2

Section 6-2

Refer to

SYSMAC CS/CJ Series Communication Commands Reference Manual

(W342) for details on FINS commands.

Sending/Receiving FINS Command/Responses

FINS commands are sent using the CMND(490) instruction for CS/CJ-series

PLCs. Send/receive FINS commands and responses and the data formats used are illustrated in the following diagram. Unless otherwise specified, all data is hexadecimal.

1 byte 1 byte

(For CS/CJ-series PLC)

Word

@CMND

Command

Response

Word

1 byte 1 byte

2 bytes

FINS header

Automatically generated and attached

Command code

540 bytes max.

Command

Text

DeviceNet

Unit

DeviceNet network

Response

2 bytes 2 bytes 538 bytes max.

FINS header

CS/CJ-series CPU Unit

Automatically generated and attached

Command code

Response code

Command Codes

Response Codes

Text

Command codes are represented by a 2-byte hexadecimal code. FINS commands always begin with a 2-byte command code and any parameters that are required follow the command code.

Response codes are represented by a 2-byte hexadecimal code that indicates the results of command execution. The first byte provides the main response code (MRES), which classifies the results, and the second byte provides the sub-response code (SRES), which provides details on the results.

146

FINS Commands and Responses

Section 6-2

The main response codes are listed below. Refer to

SYSMAC CS/CJ Series

Communication Commands Reference Manual

(W342) for further details on response codes, including sub-response codes (SRES).

Main code

00: Normal completion

01: Local node error

02: Destination node error

03: Communications controller error

04: Unsupported setting error (service not supported)

05: Routing error

10: Command format error

11: Parameter error

Main code

20: Read not possible

21: Write not possible

22: Not executable in current mode

23: No Unit

24: Start/stop not possible

25: Unit error

26: Command error

30: Access right error

40: Abort

6-2-3 Units Supporting FINS Communications

The parameters used for FINS commands depend on the Unit that is processing the command. Command details are provided in

Appendix E FINS Commands and Responses for DeviceNet Units

for commands and responses addressed to DeviceNet Units.

Refer to

SYSMAC CS/CJ Series Communication Commands Reference Manual

(W342) for information on commands and responses addressed to CS/CJseries CPU Units.

6-2-4 FINS Command Lists

Commands Addressed to CS/CJ-series CPU Units

Function Name

Manipulating data in data areas and force-setting/ resetting bits:

CIO Area, DM Area, EM

Area, Timer/Counter Area,

Transition Area, Step Area

Manipulating parameters:

PLC Setups, I/O tables, routing tables, etc.

Manipulating program areas

Controlling operation

Reading PLC model information

MEMORY AREA READ

MEMORY AREA WRITE

MEMORY AREA FILL

MULTIPLE MEMORY AREA READ

MEMORY AREA TRANSFER

PARAMETER AREA READ

PARAMETER AREA WRITE

PARAMETER AREA CLEAR

PROGRAM AREA READ

PROGRAM AREA WRITE

PROGRAM AREA CLEAR

RUN (RUN, DEBUG, MONITOR modes)

STOP (PROGRAM mode)

CONTROLLER DATA READ

CONNECTION DATA READ

Reading PLC status CONTROLLER STATUS READ

CYCLE TIME READ

Manipulating the PLC clock CLOCK READ

CLOCK WRITE

Manipulating messages MESSAGE READ

MESSAGE CLEAR

FAL/FALS READ

Command code

01 01

02

03

02

03

03

06

07

08

04

05

01

02

04

05

06

07

09

01

20

01

02

01

02

01

02

20

147

FINS Commands and Responses

Section 6-2

Function Name

Controlling access rights

Manipulating error data

Manipulating File Memory

Force-setting/resetting bits

ACCESS RIGHT ACQUIRE

ACCESS RIGHT FORCED ACQUIRE

ACCESS RIGHT RELEASE

ERROR CLEAR

ERROR LOG READ

ERROR LOG CLEAR

FILE NAME READ

SINGLE FILE READ

SINGLE FILE WRITE

MEMORY CARD FORMAT

FILE DELETE

VOLUME LABEL CREATE/DELETE

FILE COPY

FILE NAME CHANGE

MEMORY AREA FILE TRANSFER

PARAMETER AREA FILE TRANSFER

PROGRAM AREA FILE TRANSFER

CREATE/DELETE DIRECTORY

FORCED SET/RESET

FORCED SET/RESET CANCEL

Command code

0C 01

02

03

21

22

02

03

04

05

01

02

03

01

23

0B

0C

15

01

06

07

08

0A

02

Refer to

SYSMAC CS/CJ Series Communication Commands Reference Manual

(W342) for information on FINS commands addressed to CS/CJ-series

PLCs.

Commands Addressed to DeviceNet Units

RESET

Name Command code

04 03

Page

247

CONTROLLER DATA READ

CONTROLLER STATUS READ

ECHOBACK TEST

ERROR LOG READ

ERROR LOG CLEAR

Command to Send Explicit DeviceNet Messages

Name

EXPLICIT MESSAGE SEND

05

06

08

21

01

01

01

02

03

247

248

249

250

251

Command code

28 01

Page

263

148

Using FINS Message Communications

Section 6-3

6-3 Using FINS Message Communications

There are two instructions that can be executed to send and receive data from

CS/CJ-series CPU Units: SEND(090) and RECV(098). There is another instruction that can be executed to send any FINS command: CMND(490).

6-3-1 Setting Node Addresses

Set the nodes for FINS message communications to node addresses other than 0. Node address 0 has a special meaning (local node) in message communications. If 0 is set as a node address for the Unit, message communications will not be possible.

6-3-2 Creating Routing Tables

The DeviceNet Unit functions as a

Communications Unit

in the same way as the

SYSMAC LINK Unit, Controller Link Unit, and Ethernet Unit.

It is therefore necessary to create routing tables for the communications functions to be used, as shown in the table below.

Mounted Units

DeviceNet is the only

Communications

Unit mounted

Multiple DeviceNet

Units mounted as

Communications

Units

DeviceNet Unit and other Communications Unit mounted simultaneously

Using master or slave functions only

Using explicit message communications (not supported across networks)

Not necessary (See note 1.)

Not necessary (See note 1.)

Using FINS message communications not across networks

Local network table necessary (See note 2.)

Local network table necessary (See note 2.)

Using FINS message communications across networks

Local network table

(See note 2.) and relay network table are necessary.

Note

1.

2.

3.

4.

5.

6.

If a local network table already exists in the CPU unit being used, the DeviceNet Unit must be registered in that table.

The DeviceNet Unit must be registered in the local network table.

In all cases other than the following two exceptions, a local network table must be made, and the DeviceNet Unit must be registered in it.

a) When there is only one DeviceNet Unit.

b) When only multiple DeviceNet Units are mounted, with no remote I/O communications.

A local network table is sometimes necessary even when the DeviceNet

Unit is not operating across networks.

If you prepare a local network table inside the CPU Unit, be sure to register the DeviceNet Unit.

Even if a local network table exists inside the CPU Unit, the 7-segment display of the DeviceNet Unit may indicate “HC” and FINS message/explicit message communications may not be possible unless the DeviceNet Unit is registered in the local network table.

149

Using FINS Message Communications

Routing Tables

Local Network Tables

Section 6-3

The routing tables register the communications path from a Communications

Unit on the local PLC, such as a DeviceNet Unit, Controller Link Unit, SYS-

MAC LINK Unit, or Ethernet Unit, to the network to which the remote PLC is connected. The routing tables are made up of two tables, the local network table and the relay network table, as described below.

The local network table lists the unit numbers of the Communications Units mounted to the PLC and the addresses of the Networks to which each Unit belongs. If multiple Communications Units are mounted to one PLC CPU Unit, the local network table is used to distinguish between network addresses.

The following type of table is used to show which Communications Unit data must be sent through to reach a destination network address, when sending data to a network address from one PLC’s CPU Unit.

Local Network Address CPU Bus Unit’s unit number

Example

Local network: The address (1 to 127) of the network to which the Communications Unit belongs.

CPU Bus Unit’s unit number: The unit number of the CPU Bus Unit.

Unit #00

Unit #01

Unit #02

Network address 1

Network address 2

Network address 3

Local Network Table

1

2

Address of local network

3

CPU Bus Unit’s unit number

00

01

02

The unit number of the DeviceNet Unit as a CPU Bus Unit is the number set on the rotary switches on the front panel (0 to 15). The network address is the address of the Network to which the CPU Bus Unit is connected (1 to 127).

The network address is specified when this local network table for the routing table is created.

150

Using FINS Message Communications

Relay Network Tables

Section 6-3

Relay network tables show the destination network (final network) and the network and node address of the first relay point on the way to that network

(the first point to which communications are sent). The relay points are followed on the way to the final network.

Final Network Address Relay Network Address Relay Node Address

Final network address: The address of the final network (1 to 127).

Relay network address: The address of the network to which the first relay point belongs (1 to 127).

Relay node address: The node address of the first relay point.

Procedure for Creating the Routing Table

Use the CX-Net function for creating/sending routing tables in the CX-Programmer, with the following procedure.

1.

Select

Start/Program/Omron/CX-Server/CX-Net Network Configuration Tool

to start the CX-Net.

2.

Select

Edit/FINS Local

from the

Routing Table

Menu. The following PLC

Routing Table Window will appear.

3.

Click on the

Table View

Tab. A table like that shown below will appear.

151

Using FINS Message Communications

Section 6-3

4.

5.

6.

7.

Use the left-side table to create the local network table. Input the unit numbers and corresponding local network addresses.

Use the right-side table to create the relay network table. Input the final network addresses and corresponding relay network addresses and relay node addresses.

Save the finished routing table.

Go online, then load and send the routing table.

Note

Use CX-Programmer Ver. 2.1 or higher to register the DeviceNet Unit in the routing tables. Actually, registration is possible using versions prior to CX-Programmer Ver. 2.0, but “DeviceNet” will not be displayed in the list of network types when creating the routing tables with CX-Net. In this case, select one of the network types that are displayed (CLK, SLK, etc.). This will enable the

DeviceNet to be registered in the routing table.

6-3-3 Data Send/Receive Instructions

NETWORK SEND: SEND(090)

Description

SEND(090) transfers data beginning at word S in the local PLC to addresses beginning at D at the designated node on the designated Network.

Local node (source) Destination node

(192)

SEND

Ladder Symbol

S D C

S: 1

D: 1

C: 1 st

Operands st st

source word

destination word

control word

Variations

SEND

No. of words

(specified in C)

Control Data

Note

The control data depends on the destination. The following information is for

DeviceNet networks.

Word

C

C+1

C+2

C+3

C+4

Bits 00 to 07 Bits 08 to 15

Number of words: 1 to 267 words ($0001 to $010B)

Destination network address

(0 to 127, i.e., $01 to $7F, 0 = local network)

Set to 0.

Destination unit address (See note

1.)

Bits 00 to 03:

No. of retries (0 to 15, i.e., $0 to $F)

Bits 04 to 07:

Set to 0.

Destination node address (See note

2.)

Bits 08 to 10:

Transmission port number

($0 to $7)

Bit 11 to 14:

Set to 0.

Bit 15: ON: No response.

OFF: Response returned.

Response monitoring time ($0001 to $FFFF = 0.1 to 6553.5 seconds) (See note 3.)

1.

Indicates a Unit as shown in the following table.

Unit

CPU Unit

User program in FA computer

CPU Bus Unit

Setting

00

01

$10 to $1F: Unit numbers 0 to 15

$FE: The local Unit

152

Using FINS Message Communications

Section 6-3

2.

3.

Values of $00 to $3F indicate nodes 0 to 63.

Designates the length of time that the PLC retries transmission when bit

15 of C+3 is OFF and no response is received. The default value is $0000, which indicates 2 seconds.

NETWORK RECEIVE: RECV(098)

Description

RECV(098) transfers data beginning at word S from the designated node on the designated Network to addresses beginning at D at the local node.

Local node (destination) Source node

Ladder Symbol

(098)

(@)RECV S D C

Operands

S: 1 st

D: 1

C: 1 st st

source word

destination word

control word

Variations

RECV(098) m

No. of words

(specified in C)

Control Data

Note

The control data depends on the source node. The following information is for

DeviceNet Networks.

Word

C

C+1

Bits 00 to 07

Number of words: 1 to 269, i.e., $0001 to $010D)

Bits 08 to 15

Source network address

(0 to 127, i.e., $00 to $7F, 0 = local network)

Set to 0.

C+2

C+3

C+4

Source unit address (See note 1.)

Bits 00 to 03:

No. of retries (0 to 15 in hexadecimal, i.e., $0 to $F)

Bits 04 to 07:

Set to 0.

Source node address (See note 2.)

Bits 08 to 10:

Transmission port number

($0 to $7)

Bit 11 to 14:

Set to 0.

Bit 15: ON: No response.

OFF: Response returned.

Response monitoring time ($0001 to $FFFF = 0.1 to 6553.5 seconds) (See note 3.)

1.

Indicates a Unit as shown in the following table.

Unit Setting

CPU Unit

User program in FA computer

00

01

CPU Bus Unit $10 to $1F: Unit numbers 0 to 15

$FE: The local Unit

2.

3.

Values of $00 to $3E indicate nodes 0 to 63.

Designates the length of time in (0.1-s units) that the PLC retries transmission when bit 15 of C+3 is OFF and no response is received. The default value is $0000, which indicates 2 seconds. If baud rate is slow and the response monitoring time is short, an error may occur.

153

Using FINS Message Communications

Section 6-3

6-3-4 Sending FINS Commands

DELIVER COMMAND: CMND(490)

Description

CMND(490) can be used in the user program of the CS/CJ-series CPU Unit to send FINS commands to read/write I/O memory, read status data, change the operating mode, and perform other functions at other nodes.

CMND(490) transmits the command beginning at word S to the designated

Unit at the destination node address in the designated network, and receives the response beginning at word D.

Local node (source) Destination node

Ladder Symbol

(490)

(@)CMND S D C

Command

Interpretation

Operands

S: 1 st command word

D: 1 st

C: 1 st response word control word

Variations

CMND(490)

Command data

Response

Execution

Response data

Note

Word

C

C+1

C+2

C+3

C+4

C+5

Bits 00 to 07 Bits 08 to 15

Number of command bytes to send: 0 to 542 (i.e., $0000 to $021E)

Number of response bytes to receive: 0 to 542 (i.e., $0000 to $021E)

Destination network address

(0 to 127, i.e., $00 to $7F, 0 = local network)

Set to 0.

Destination unit FINS address (See note 1.)

Bits 00 to 03:

No. of retries (0 to 15, i.e., $0 to $F)

Bits 04 to 07:

Set to 0.

Destination node address (See note

2.)

Bits 08 to 10:

Transmission port number

($0 to $7)

Bit 11 to 14:

Set to 0.

Bit 15: ON: No response.

OFF: Response returned.

Response monitoring time ($0001 to $FFFF = 0.1 to 6553.5 seconds) (See note 3.)

1.

Indicates a Unit as shown in the following table.

Unit Setting

CPU Unit

User program in FA computer

00

01

CPU Bus Unit $10 to $1F: Unit numbers 0 to 15

$FE: The local Unit

2.

3.

Values of $00 to $3E indicate nodes 0 to 63.

Designates the length of time in (0.1-s units) that the PLC retries transmission when bit 15 of C+3 is OFF and no response is received. The default value is $0000, which indicates 2 seconds. If baud rate is slow and the response monitoring time is short, an error may occur.

154

Using FINS Message Communications

Section 6-3

6-3-5

Note

Explicit messages can be sent to OMRON slaves and DeviceNet devices made by other manufacturers by setting the FINS command code to 28 01.

When this is done, set the response monitoring time in C+5 to at least the value set for the message monitoring timer (default: 2 s). If it is set to less than the value for the message monitoring timer (default:2 s), communications may be busy even if the next command is executed after the first one times out.

Using SEND(090), RECV(098), and CMND(490)

SEND(090), RECV(098), and CMND(490) instructions normally use an AND of the Network Enabled Flag in the CPU Unit (A20200 to A2020007 corresponding to ports 0 to 7) and the Online Flag (word n+11, bit 00) (or the Message Communications Permitted Flag (word n+24, bit 12)) for the DeviceNet

Unit.

Note

The Online Flag and the Message Communication Permitted Flag perform the same operation.

Execution condition

Network

Enabled Flag

Online Flag

SEND(090), RECV(098), or CMND(490) word n+11, bit 00 or

Execution condition

Network

Enabled Flag

Message

Communications

Permitted Flag

SEND(090), RECV(098), or CMND(490) word n+24, bit 12

Communications Flags

Type Name Content

CPU Unit Network Enabled Flag

Word

A202

Address

Bit

7 6 5 4 3 2 1 0

0: Execution not possible (executing)

1: Execution possible (not executing)

Network Error Flag A219

7 6 5 4 3 2 1 0

0: Normal completion

1: Error

Communications Flag Operation

• The Network Enabled Flag turns OFF when instructions are being sent or received (from when the instruction is issued until the response is received) and turns ON when the execution has been completed, whether normally or with an error.

• The Network Error Flag maintains its status until the next send or receive is executed.

• The Network Error Flag turns OFF when the next communications instruction is executed, regardless of whether the previous execution ended with an error.

• The relationship between the Message Communications Permitted Flag and the NS indicator and between the Message Communications Permit-

155

Using FINS Message Communications

Section 6-3

ted Flag and the NS indicators on the front of the DeviceNet Unit is shown in the following table.

Message

Communications

Permitted Flag

ON

OFF

Network status

Communications connection made (network normal)

Communications connection not made (network normal, but communications not established)

Non-fatal communications error (error in one or more Slaves)

Offline or power supply is OFF (no power supply, resetting, minor failure, or send error)

Fatal communications error

NS indicator

Lit green

Flashing green

Flashing red

Not lit

Lit red

Network Enabled Flag

1

0

Communications instruction

1

Execution

Error Flag

0

Completion code

Instruction

1 executed

00

Previous code

00 Normal end

Instruction

2 executed

00

04 Busy

Instruction

3 executed

00

00 Normal end

Communications Instructions Completion Codes

The status at the completion of the execution of network communications instructions is shown at the words indicated in the following table, as FINS completion codes. During execution of the instructions the status will be 00 or

$0000 and this will be reflected at the end of the execution of the network communications instruction.

Words

Port #0 to #7

Completion Codes

(A203 to A210)

Functions

A203 to A210 contain the completion codes for the results of communications instruction execution for ports #0 to

#7, respectively.

Note

For the CS/CJ-series, the completion codes are stored as 2 bytes of data (1 word) upon completion of the execution of SEND(090),

RECV(098), and CMND(490). These codes are the same as the response codes for FINS commands. The first byte of the completion code is placed in bits 08 to 15 and the second byte is placed in bits

00 to 07.

Timing of Reading Responses

Responses should be read on the rising edge (upward differentiation) of the

Network Enabled Flag, as shown in the following diagram.

Network Enabled

Flag

Processing to read response

156

Using FINS Message Communications

Section 6-3

Send/Receive Data Areas

The size of the data areas that can be used with SEND and RECV depends on the PLC that is being used. The following table shows the areas that can be used for CS/CJ-series PLCs.

CIO Area

Work Area WR

Holding Area

Auxiliary Area

Data Area

Timer Area

Counter Area

DM Area

EM Area

Range

CIO 0000 to CIO 6143

W000 to W511

H000 to H511

A000 to A959 (See note 3.)

T0000 to T4095

C0000 to C4095

D00000 to D32767

E00000 to E32767 (See note 2.)

Note

1.

2.

3.

A000 to A477 in the Auxiliary Area are write-protected.

There can be up to 13 banks of EM Memory. Refer to the operation manual for the CPU Unit for information on whether it has EM Memory and how many banks can be used.

Do not exceed the boundary of the data areas for the PLC you are using.

Programming Examples

Example 1: Sending Data Using SEND

CS/CJ-series DeviceNet Unit No. 0

CS/CJ-series

DeviceNet Unit

Node 05

CPU

Unit

CS/CJ-series

PLC

Network 01

CPU

Unit

CS/CJ-series

PLC

Unit address: 00

Node 06

SEND

Operation

• The data from the 5 words D01000 to D01004 from the PLC with DeviceNet Unit 1 with node address 05 are sent to D03000 to D03004 in the PLC with DeviceNet Unit 2 with node address 06.

• The completion code is stored in D00006 when execution of SEND has been completed.

Command Details

The following command is used: [SEND S

S = D01000:

D = D03000:

C = D00000:

D

First source word at local (source) node

First destination word at destination node

C]

First control word; settings are given below (Hex).

D00000 = 0005:

D00001 = 0001:

D00002 = 0600:

D00003 = 0000:

D00004 = 0064:

Number of words to send

Destination network address

Destination node address (06)

Destination unit address (00 = CPU Unit)

Response, communications port 0, no retries

Response monitoring time

157

Using FINS Message Communications

Program Example

A202

11

First Scan Flag

(071)

BSET #1234 D01000 D01004

(021)

MOV #0005 D00000

(021)

MOV #0001 D00001

(021)

MOV #0600 D00002

(021)

MOV #0000 D00003

(021)

MOV #0064 D00004

(021)

MOV #0001 0000

Execution condition

000

00

A202

00

1511

00

Network

Enabled

Flag

Online Flag

(Word n+11, bit 00)

0000

01

A202

00

A202

08

(090)

SEND D01000 D03000 D00000

(025)

ASL 0000

Network

Enabled

Flag

Network

Execution

Error Flag

(021)

MOV A503 D00006

(061)

ASR 0000

(001)

END

Section 6-3

Sets 1234 in D01000 to D01004.

Places data into control data words to specify the 5 words to be transmitted to the CPU Unit of node 06 of network 01, through port 0, with response, 0 retries, and a response monitoring time of 10.0 seconds.

Places 0001 into CIO 0000

Transfers 5 words of data from D01000 to D01004 from the PLC of node 05 to D03000 to D03004 in the PLC of node 06.

Shifts the contents of CIO 0000 one bit to the left.

Stores the completion code in A203 to D00006.

Shifts the contents of CIO 0000 one bit to the right and retries the next cycle (CIO 000000 ON).

158

Using FINS Message Communications

Example 2: Sending a FINS Command Using CMND

CS/CJ-series

DeviceNet Unit No. 0

Section 6-3

CMND

CS/CJ-series

DeviceNet Unit

Node 05

CPU

Unit

CPU

Unit

Unit address: 00

Node 06

Network 01

MEMORY AREA READ command

Operation

• The PLC with DeviceNet Unit 1 with node address 5 reads the data from the 5 words D01000 to D01004 from the PLC with DeviceNet Unit

2 with node address 06.

• The MEMORY AREA READ command (01 01) is used to read variable data.

• Command data is written starting from D01000 in the PLC with DeviceNet Unit 1 with node address 5 and the response data is written starting from D02000.

• The completion code is stored in D00006 when execution of SEND has been completed.

Command Details

The following command is used: [CMND S

D00000 = 0008:

D00001 = 000E:

D00002 = 0001:

D00003 = 0600:

D00004 = 0000:

D00005 = 0064:

D

S = D01000: First command word at local node

Settings (Hex)

D01000 = 0101:

D01001 = 8203:

Command Code

Command parameters

D01002 = E800:

D01003 = 0005:

Command parameters

Command parameters

D = D02000:

C = D00000:

First response word at local node

First control word

Settings (Hex).

C]

Number of command bytes

Number of response bytes

Destination network address

Destination node address (06)

Destination unit address (00 = CPU Unit)

Response, communications port 0, no retries

Response monitoring time

159

Using FINS Message Communications

A500

15

First Scan Flag

Example Program

(071)

BSET #0000 D00000 D02999

(021)

MOV #0008 D00000

(021)

MOV #000E D00001

(021)

MOV #0001 D00002

(021)

MOV #0600

(021)

MOV #0000

(021)

MOV #0064

(021)

MOV #0101

D00003

D00004

D00005

D01000

(021)

MOV #8203 D01001

(021)

MOV #E800

(021)

MOV #0005

(021)

MOV #0001

D01002

D01003

0000

Execution condition

0000

00

A202

00

15110

00

Port

Enabled

Flag

Online Flag

(word n+11, bit 00)

(490)

CMND D01000 D02000 D00000

(025)

ASL 0000

0000

01

A202

00

A219

00

Port

Enabled

Flag

Port

Execution

Error Flag

(021)

MOV A203 D00006

(026)

ASR 0000

(001)

END

Section 6-3

Sets 0000 in D00000 to D02999.

Place data into control data words to specify to read

5 words D01000 to D01004 from the PLC of node 06 and network 01 to the PLC of node 05.

Place the command data for MEMORY AREA READ into D01000 to D01003.

Places 0001 into CIO 0000

Reads 5 words D01000 to D01004 from the PLC of node

06 and network 01 to the PLC of node 05 and stored the data beginning at D02000.

Shifts the contents of CIO 0000 one bit to the left.

Stores the network error response code in A203 to

D00006.

Shifts the contents of CIO 0000 one bit to the right to reset CIO 000000.

6-3-6 Connecting Networks for FINS Communications

CS/CJ-series DeviceNet Units can perform FINS communications between networks. DeviceNet networks are handled the same way as other FA networks such as Controller Link or SYSMAC LINK, and the OA network Ethernet.

DeviceNet networks can be connected to the other DeviceNet networks or to other types of networks.

Note

Explicit message communications cannot be performed between networks.

160

Sending Explicit Messages

Up to 3 levels of networks, including DeviceNet, are possible.

Controller Link Unit

Controller Link Unit

CS/CJ-series DeviceNet Unit

CS/CJ-series CPU Unit

Remote I/O communications

DeviceNet

CS/CJ-series DeviceNet Unit

Controller Link

Section 6-4

DeviceNet

CS/CJ-series

DeviceNet Unit

6-4

When connecting networks, routing tables must be registered for the PLC

CPU Units on all networks.

When connecting two or more communication units (including the DeviceNet

Unit) to a CS/CJ-series CPU Unit, the DeviceNet Unit must be registered in the CS/CJ-series PLC CPU Unit routing table (for the local network table only). Commands cannot be executed if the DeviceNet Unit is not registered.

Sending Explicit Messages

CS/CJ-series DeviceNet Units can send explicit messages. FINS command headers are attached to explicit messages and sent. Explicit messages can be sent to the following destinations.

• Masters or slaves made by other manufacturers

• Other PLCs with a CS/CJ-series DeviceNet Unit.

• PLCs (Slaves) with C200H I/O Link Units (See note).

Note

Only reading and writing I/O memory is possible for PLCs with

C200H I/O Link Units. Status reading/writing is not possible.

Example

CS/CJ-series DeviceNet Unit

CS/CJ-series CPU Unit

Other manufacturer master or slave or

CS/CJ-series DeviceNet Unit

Explicit messages can be sent

FINS header

Explicit message

DeviceNet

C200H I/O Link Unit

C200HX/HG/HE or

CS/CJ-series

CPU Unit (Slave)

Note

Only I/O memory read/write possible

161

Sending Explicit Messages

Section 6-4

6-4-1 Sending Explicit Messages

The FINS command code 28 01 can be used to send explicit DeviceNet messages to OMRON slaves and DeviceNet devices made by other manufacturers. The use of explicit messages is illustrated in the following diagram.

CPU Unit

Slave or Master by other manufacturer

Explicit message

FINS header

DeviceNet Unit

FINS header

Explicit message

CMND

(490)

Use 28 01 for the

FINS command code.

DeviceNet network

FINS header

Response

FINS header

Response

The local DeviceNet Unit is specified as the destination in the communications instruction in the PLC’s user program (not the OMRON Special Slave or

DeviceNet device made by another manufacturer), and the node address of the actual destination (i.e., the Slave or Master made by another manufacturer) is specified in the command data for the explicit message send command.

FINS command

CMND

Control data in C+3

Destination node address:

Destination unit address:

Local node address

Unit No. of DeviceNet Unit +10 (Hex)

PLC's

CPU Unit

Explicit message

Slave or Master not by OMRON

162

Sending Explicit Messages

Section 6-4

The following diagram shows an example of actual node address specifications.

Machine No. of DeviceNet Unit: 2

CMND

S

D

C

The node address of the non-OMRON node is set as the destination node address in the FINS command data.

8 7 0

S

S+1

15

2

0

8

6

0 1

Command code

PLC's

CPU

Unit

Node 05

Explicit message

Node 06

(Slave or Master not by OMRON)

C+3

15

0

5

Explicit command block

Node address of the non-

OMRON node: 06 Hex

8 7 0

F E

Destination node address:

Local node address: 05

Destination unit address:

FE or 12 (Hex)

Note

Depending on conditions, the destination slave may not always accept an explicit message. Always perform retry processing when sending explicit messages.

FINS Command: EXPLICIT MESSAGE SEND (28 01)

EXPLICIT MESSAGE SEND will send an explicit DeviceNet message to the specified class and receive a response.

Command Block

28 01

534 bytes max.

Command code

Class ID

Service code

Destination node address

Instance ID Service data

Response Block

Normal Response

28 01

534 bytes max.

Command code

Response code

No. of bytes received

Service data

Service code

Destination node address (remote node)

Error Responses

The following response is returned if an error occurs for the explicit message.

28 01

Command code

Response code

No. of bytes received

Error code

Service code 94 (Hex)

Destination node address (remote node)

The following response is returned if the explicit message cannot be sent or times out.

163

Sending Explicit Messages

Section 6-4

Command code

Response code

Parameters

6-4-2

Note

Destination node address (command):

The node address of the destination of the explicit message. (The node address of the local DeviceNet Unit is specified in the control data for the CMND(490), but the node address of the actual destination is specified here in the FINS command.)

Service code (command, response):

A service code defined for DeviceNet.

In a normal response, bit 15 of the service code specified in the command will be turned ON and returned. In an error response, 94 Hex will always be returned.

Class ID (command):

The class ID of the destination of the explicit message.

Instance ID (command):

The instance ID of the destination of the explicit message.

Service data (command, response):

The data defined for the services codes.

No. of bytes received (response):

The number of bytes received from the destination node address (remote node).

Destination node address (remote node):

The node address of the

OMRON Special I/O Slave Unit or Slave manufactured by another company to which the explicit message was sent is returned.

Error code (response):

An error code defined by DeviceNet.

1.

2.

3.

4.

5.

6.

This command sends a DeviceNet-defined explicit message to an OMRON

Special I/O Slave Unit or a Slave manufactured by another company and receives a response.

Unlike other FINS commands, this command is addressed to the local DeviceNet Unit. The actual destination of the explicit message is given in the command data, as described above.

If the DeviceNet Unit receives an explicit message, it will automatically return a response.

Refer to the DeviceNet Specification for details on parameters for explicit messages.

Contact the Open DeviceNet Vendor Association, Inc. (ODVA) at 8222

Wiles Road, Suite 287, Coral Springs, FL 33067 USA (phone: 954-340-

5412, fax: 954-340-5413, e-mail: [email protected], Home page: http://www.odva.org/) to obtain copies of the specification.

For details on explicit messages to OMRON Special I/O Slaves, refer to the

DeviceNet Slaves Operation Manual

(W347).

Sending Explicit Messages Using CMND(490)

CMND(490) can be used in the CPU Unit ladder program of the CS/CJ-series

DeviceNet Unit to send explicit messages.

FINS command headers are attached to the explicit messages and sent.

After the FINS command header and the FINS completion code are sent, the explicit message response is received.

S D C ] The following command is used: [ CMND

S: First command word

D: First response word

164

28 01

Sending Explicit Messages

Section 6-4

C: First control data word

Command data is set in order starting with the word specified for the

CMND(490) operand S (first command word) and continuing with words with higher addresses in I/O memory in the command block format.

Command Format Example: Writing Error Clear Codes to the CPU Unit

Set in this order starting from the word specified for the

CMND(490) operand S (first command word) and continuing with words with higher addresses.

28 01 01 10 00 2F 00 00 65 FE FF

Command code

Service

Code

Class ID

Destination node address

Instance ID

Service Data

Method for Setting Data from CMND(490) Operand S

Bit

FINS command code

Node address, Service Code

Class ID

Instance ID

Service Data

Service Data

In the same way, response data is set from the starting with the word specified for CMND(490) operand D (first response word) and continuing with words with higher addresses in I/O memory in the response block format.

Note

Service data that is in word (2-byte) or double-word (4-byte) units, such as word data and ERROR CLEAR codes, is specified from low to high (U) bytes in command block format. For example, to specify word data $1234, specify

$34 and then $12. To specify $12345678, specify $78 to $56 to $34 to $12.

The command blocks are shown in the following diagram.

165

Sending Explicit Messages

Command Block

Eg. For $1234

Eg. For $15678234

Service Data

Service Data

The format from CMND(490) operand S onwards will be set as follows:

Example: $1234

From higher byte

Bit

Example: $12345678

From higher byte

Bit

Bit

From lower byte

Bit

From lower byte

Section 6-4

The response format data in service data that is in word (2-byte) or doubleword (4-byte) units, such as word data and ERROR CLEAR codes, is also specified from low to high bytes in response block format

Example: Sending Explicit Messages Using CMND(490)

DeviceNet Unit No. 0

CMND(490) instruction

PLC's

CPU

Unit

Node address 05

Unit address FE Hex or 10 Hex

Operation

Command Details

Explicit message

Slave node 11

The vendor code is read from a Slave (OMRON vendor code: 002F Hex) using the EXPLICIT MESSAGE SEND command, 28 01. The command data is written starting at DM01000, and the response data is stored starting at

D02000. When execution of CMND(490) has been completed, the completion code is stored in D00006 and the instruction is executed again.

The following command is used: [ CMND S D

S = D01000: First command word at local node

Settings (Hex)

D01000 = 2801:

D01001 = 0B0E:

D01002 = 0001:

D01003 = 0001:

D01004 = 0100:

Command Code

Slave node address: 11

Service code: 0E

Class ID: 0001

Instance ID: 0001

Attribute ID: 01

D = D02000:

C = D00000:

First response word at local node

First control word

C ]

166

Sending Explicit Messages

Response

Section 6-4

Settings (Hex).

D00000 = 0009:

D00001 = 000A:

D00002 = 0001:

D00003 = 05FE:

D00004 = 0000:

D00005 = 0064:

Number of command bytes

Number of response bytes

Destination network address: 1

Destination node address: 05

Destination unit address: FE (or 10)

Response, communications port 0, no retries

Response monitoring time

D02000 = 2801

D02001 = 0000

D02002 = 0004

D02003 = 0B8E:Response source node address 11: 0B Hex

Normal completion 8E Hex

D02004= 2F00: Vendor code stored from high to low byte

167

Receiving Explicit Messages

A200

11

First Scan Flag

Section 6-5

Program Example

(071)

BSET #0000 D00000 D02999

(021)

MOV #0009 D00000

(021)

MOV #000A D00001

(021)

MOV #0001 D00002

(021)

MOV #05FE

(021)

MOV #0000

D00003

D00004

(021)

MOV #0064

(021)

MOV #2801

D00005

D01000

(021)

MOV #0B0E D01001

(021)

MOV #0001

(021)

MOV #0001

(021)

MOV #0100

(021)

MOV #0001

D01002

D01003

D01004

0000

Sets 0000 in D00000 to D02999.

Place data into control data words to specify sending

9 bytes to node 05 (unit FE) on network 01 and to receive 10 bytes in return.

Place the command data for EXPLICIT MESSAGE

SEND into D01000 to D01004.

Places 0001 into CIO 0000

Execution condition

0000

00

A202

00

1511

00

0000

01

Port

Enabled

Flag

Message

Communications

Permitted

Flag

A202

00

A219

00

(490)

CMND D01000 D02000 D00000

(025)

ASL 0000

Sends 9 bytes of command data to node 05 (unit FE) on network 01 and receives 10 bytes of response data and stores it in D02000.

Shifts the contents of CIO 0000 one bit to the left.

Port

Enabled

Flag

Port

Execution

Error Flag

(021)

MOV A203 D00006

(026)

ASR 0000

(001)

END

Stores the completion code in A203 to D00006.

Shifts the contents of CIO 0000 one bit to the right and retry at next cycle (CIO 000000 ON).

6-5 Receiving Explicit Messages

This CS/CJ-series DeviceNet Unit contains a PLC Object. The Unit will receive messages addressed to the PLC Object, process service requests addressed to the CPU Unit, and return responses.

The following services are provided by the PLC Object.

• CPU Unit status read/write

• CPU Unit I/O memory read/write

The explicit messages can be received from the following sources:

• Masters made by other manufacturers

• PLCs with C200H-series DeviceNet Master Units (C200HW-DRM21-V1)

168

Receiving Explicit Messages

Section 6-5

• PLCs with CVM1/CV-series DeviceNet Master Units (CVM1-DRM21-V1)

• PLCs with CS/CJ-series DeviceNet Units

Example

CS/CJ-series

DeviceNet Unit

C200H-series

DeviceNet Master Unit C200HX/HG/HE

CS/CJ-series CPU Unit

CPU Unit

Other manufacturer master

Explicit messages can be received

Explicit message

DeviceNet

Note

Status and the I/O memory read/write operations cannot be performed for

PLCs with a C200H-series or CVM1/CV-series DeviceNet Master Units. The

CPU Unit of a CS/CJ-series DeviceNet Unit can also send an explicit message to read/write I/O memory of PLCs with C200H I/O Link Units.

6-5-1 List of PLC Object Services

PLC Objects provide the following services.

Status Read/Write for CPU Units

Services

CPU Unit Information Read

Service code

0E Hex

Class ID

2F Hex

CPU Unit Write

CPU Unit Status

Read

10 Hex

40 Hex

Instance ID

00 Hex

Request service data

Attribute ID =

64 Hex

Attribute ID =

65 Hex

Attribute ID =

66 Hex

Attribute ID =

64 Hex,

Attribute Value

Attribute ID =

65 Hex

Attribute Value

None

Changes the operating mode of the

CPU Unit.

Clears errors.

Contents

Reads the operating mode of the

CPU Unit.

Reads if there is a fatal or non-fatal error in the CPU Unit.

Reads CPU Unit model.

Reads the detailed status of the CPU

Unit.

Operation status: Stop, run, CPU standby

Operating modes: PROGRAM, MON-

ITOR, RUN

Fatal error information: Error flags, including memory errors, I/O bus errors, system errors

Messages: Message No. when MSB instruction executed by CPU Unit

Error codes: Error code for the most serious errors

Error messages: Messages stored in

CPU Unit when FAL/FALS instruction executed

169

Receiving Explicit Messages

Section 6-5

I/O Memory Read/Write for CPU Units

Service Service code

Byte Data Read IC Hex

Word Data

Read

ID Hex

Byte Data Write IE Hex

Word Data Write IF Hex

Class ID

2F Hex

Instance ID

Specifies area (01 Hex to 14 Hex)

Request service data

Address, No. of read bytes

Contents

Reads the specified node data in byte units.

The word data is read in order, from high to low bytes.

Read data: 200 bytes max.

Address, No. of read words

Reads the specified node data in word units. The word data is read in order, from high to low bytes.

Read data: 200 bytes max.

Address, word data

Writes the specified node data in byte units.

The word data is specified in order, from high to low bytes.

Write data: 200 bytes max.

Address word data

Writes the specified node data in word units. The word data is specified in order, from high to low bytes.

Write data: 200 bytes max.

The commands and responses for the explicit messages that can be sent and received are described on the following pages.

Note

In the following command and response formats, all boxes represents 1 byte.

170

Receiving Explicit Messages

Section 6-5

CPU Information Read (Service Code: 0E Hex)

Reads CPU Unit information, including operating mode, fatal/non-fatal errors, and the CPU Unit model.

Command Block

0E 2F

(*)

00

(*)

Class ID

Service Code

Attribute ID

Instance ID

Note

A body format of either 8 bits or 16 bits is possible.

Response Block

8E

Parameters

Service Code

Attribute Value

Service code (command, response):

0E Hex is specified for commands.

For responses, the highest bit be ON and 8E Hex will be returned.

Class ID (command):

Always 2F Hex.

Instance ID (command):

Always 00 Hex.

Attribute ID (command):

The read information is specified by the attribute ID.

The attribute IDs are listed in the following table.

64

65

66

Attribute ID (Hex) Contents

CPU Unit operating mode

CPU Unit errors

CPU Unit model

Attribute value size

1 word (2 bytes)

1 word (2 bytes)

22 bytes

• CPU Operating Mode (when Attribute ID = 64 Hex)

Reads the CPU Unit operating mode.

• CPU Unit Errors (when Attribute ID = 65 Hex)

Reads if there are any fatal or non-fatal errors in the CPU Unit.

• CPU Unit Model (when Attribute ID = 66 Hex)

Reads the CPU Unit model.

Read data (response):

The specified information is returned in order.

• CPU Unit operating mode (attribute ID = 64 Hex).

The CPU Unit operating mode is returned in 1-word (2-byte) hexadecimal format, as follows:

0001 Hex: PROGRAM mode; 0002 Hex: MONITOR mode;

0004 Hex: RUN mode

PROGRAM mode

MONITOR mode

RUN mode

171

Receiving Explicit Messages

Section 6-5

Note

The codes for the above modes are 1-word (2-byte) data and are returned in low byte first. For example, for PROGRAM mode, the code is returned as 01

Hex followed by 00 Hex.

• CPU Unit Errors (when Attribute ID = 65 Hex)

The CPU Unit fatal/non-fatal error data is returned in 1-word (2-byte) hexadecimal format, as follows:

01 Hex: Error; 00 Hex: No error.

1: Error

• CPU Unit Model (when Attribute ID = 65 Hex)

The CPU Unit model is returned in ASCII.

Size: 2 bytes (Always 1400 Hex) + Model: 20 bytes (fixed). Unused area is filled with 20 Hex (spaces) and returned.

20 bytes

Byte Byte Byte Byte Byte

Unit name

CPU Unit Write (Service Code: 10 Hex)

This PLC Object service writes CPU Unit information, including the operating mode and clearing errors.

Command Block

10 2F

(*)

00

(*)

Class ID

Service Code

Attribute ID

Instance ID Attribute Value

Note

A body format of either 8 bits or 16 bits is possible.

Response Block

90

Parameters

Service Code

Service code (command, response):

10 Hex is specified for commands. For responses, the highest bit will turn ON and 90E Hex will be returned.

Class ID (command):

Always 2F Hex.

Instance ID (command):

Always 00 Hex.

Attribute ID (command):

Information to write is specified by the attribute ID.

The attribute IDs are listed in the following table.

64

65

Attribute ID (Hex) Contents

CPU Unit operating mode

CPU Unit errors

Attribute value size

1 word (2 bytes)

1 word (2 bytes)

• CPU Operating Mode (Attribute ID = 64 Hex)

Changes the CPU Unit operating mode.

172

Receiving Explicit Messages

Section 6-5

The Attribute Values are as follows:

0001 Hex: PROGRAM mode; 0002 Hex: MONITOR mode;

0004 Hex: RUN mode

Note

The specified code for the above operating modes are 1-word (2-byte data, and are specified with the low byte first. For example, for PRO-

GRAM mode, the code is specified as 01 Hex followed by 00 Hex. Accordingly, the low to high bytes for the above codes are set as high to low bytes in I/O memory, when setting the codes as data for operand S of CMND(490).

• Clearing CPU Unit Errors (when Attribute ID = 65 Hex)

Clears any fatal or non-fatal errors in the CPU Unit. Sets the error clear code to Attribute Value. The error clear codes are listed in the following table.

Error code

(Hex)

FFFE

0008B

009A

009B

02F0

0300 to 035F

00A0 to 00A1

0500 to 055F

00E7

00F7

0200 to 020F

0400 to 040F

4101 to 42FF

Data cleared

Current error (clears the highest priority error)

Interrupt task error

Basic I/O error

PLC Setup error

Inner Board non-fatal error

Special I/O Unit error

SYSMAC BUS error

Special I/O Unit settings error

I/O verification error

When registered and actual I/O tables are different

When disconnecting or connecting I/O Units

Battery error

CS/CJ-series CPU Bus Unit error (last 2 digits are binary code for the Unit No.)

For parity errors generated when data transferred between CS/CJseries CPU Bus Unit and CPU Unit

For watchdog timer errors in CS/CJ-series CPU Bus Unit

CPU Bus settings error (last 2 digits are binary code for the Unit

No.)

System error (FAL): FAL instruction executed

Note

Error clear codes are 1-word (2-byte) data, so the above codes are specified with the low byte first. The low to high bytes for the above codes are set as high to low bytes in I/O memory, when setting the codes as data for operand S of CMND(490). For example, to specify battery error 00F7 Hex, specify the error code as F7 Hex followed by

00 Hex, as shown in the following diagram.

Command Block

10 2F 00 65 F7 00

Class ID

Service Code

Attribute ID

Instance ID Attribute Value

173

Receiving Explicit Messages

Section 6-5

CPU Unit Status Read (Service Code: 40 Hex)

This PLC Object service reads status details (operation status, operating mode, fatal and non-fatal errors, etc.) from the CPU Unit.

Command Block

40 2F

(*)

00

(*)

Service Code Instance ID

Class ID

Note

A body format of either 8 bits or 16 bits is possible.

Response Block

C0

Parameters

Service Code

Detailed status

Service code (command, response):

40 Hex is specified for commands. For responses, the highest bit will turn ON and C0 Hex will be returned.

Class ID (command):

Always 2F Hex.

Instance ID (command):

Always 00 Hex.

Read data (response):

The read data is given in the following table. The data is returned after the service code in the order shown in the table (high to low).

Operation Status

RUN mode

Fatal error information (L)

Fatal error information (H)

Non-fatal error information (L)

Non-fatal error information (H)

Message exists/does not exist (L)

Message exists/does not exist (H)

Error code (L)

Error code (H)

Error message (16 bytes)

Operation status:

Returns the operation status of the CPU Unit in 1-byte

(2-digit) hexadecimal.

Operating mode:

Returns the operating mode of the CPU Unit in 1-byte

(2-digit) hexadecimal.

0001 Hex: PROGRAM mode; 0002 Hex: MONITOR mode;

0004 Hex: RUN mode

Fatal error information:

Returns the fatal error information for the CPU

Unit in 2 bytes (low to high).

174

Receiving Explicit Messages

Section 6-5

1: System error (FALS)

1: Cycle time over

1: Program error

1: I/O setting error

1: No. of I/O points exceeded

1: Inner Board fatal error

1: Number duplicate use error

1: I/O Bus error

1: Memory error

Non-fatal error information:

Returns the non-fatal error information for the CPU Unit in 2 bytes (low to high).

Unspecified (reserved for system use)

1: Special I/O Unit error

1: CPU Bus settings error

1: Battery error

1: SYSMAC BUS error

1: Special I/O Unit

1: CS1-series CPU Bus Unit error

1: Inner Board error

1: I/O verification error

1: PLC system error

1: Unspecified (reserved for system use)

1: Basic I/O Unit error

1: Interrupt task error

1: Unspecified (reserved for system use)

1: System error (FAL)

Message Exists/Does Not Exist:

When the MSG instruction is executed by the CPU Unit, the bit corresponding to the message number will turn

ON and be returned in 2 bytes (from low to high bytes).

Message No. 0 (1: exists; 0: does not exist)

Message No. 1 (1: exists; 0: does not exist)

Message No. 2 (1: exists; 0: does not exist)

Message No. 3 (1: exists; 0: does not exist)

Message No. 4 (1: exists; 0: does not exist)

Message No. 5 (1: exists; 0: does not exist)

Message No. 6 (1: exists; 0: does not exist)

Message No. 7 (1: exists; 0: does not exist)

Error Code

: The highest priority error code of the errors existing when the command is executed will be returned in 2-byte decimal (from low to high bytes). If there are no errors, the error code will be 0000.

175

Receiving Explicit Messages

Section 6-5

Note

For information on the severity of error codes, refer to the

CS1 Series

CPU Unit Operation Manual

(W339) or the

CJ Series CPU Unit Operation Manual

(W393).

Error Messages:

If the above error codes have occurred when FAL/FALS instructions are executed with registered messages, those messages are returned in 16-byte ASCII. If there are no registered messages or if the error codes have not occurred due to execution of FAL/FALS instructions, the code is returned in ASCII with 20 Hex (space) in 16 bytes.

Byte Data Read (Service Code: 1C Hex)

Byte Data Read reads any I/O memory area data in a CPU Unit with a CS/CJseries DeviceNet Unit mounted. The read word data is in byte units. The response block is returned from high to low bytes.

Command Block

1C 2F

(*) (*)

Class ID

Service Code

Address L

Instance ID

No. of bytes read

Address H

Note

A body format of either 8 bits or 16 bits is possible.

Response Block

9C

Parameters

Service Code Word data L

Word data H

Word data L

Word data H

Read data (200 bytes max.)

Service code (command, response):

IC Hex is specified for commands. For responses, the highest bit will turn ON and 9C Hex will be returned.

Class ID (command):

Always 2F Hex.

Instance ID (command):

The memory area that will read the data is specified as shown in the following table.

Instance ID (Hex)

01

03

04

05

08 to 14

CPU Unit memory area for read

CIO

DM

WR

HR

EM, banks 0 to C

Word range

0000 to 6143

D00000 to D32767

W000 to W511

H000 to H511

En_00000 to En_32767

(n: 0 to C)

Address L, Address H (command):

The address of the first word from which to read the data is specified in hexadecimal as shown below.

Address L: The lower 2 digits when the first word address is given in 4-digit hexadecimal.

Address H: The higher 2 digits when the first word address is given in 4-digit hexadecimal.

No of Read Bytes (command):

The number of bytes of read data is specified in 1-byte (2-digit) hexadecimal. The range is 01 to C8 Hex (1 to 200 decimal).

176

Receiving Explicit Messages

Section 6-5

Important Points

No. of bytes received (response):

The number of bytes received from the destination node address (remote node) is returned in hexadecimal.

Destination node address (response):

The node address of the CS/CJseries DeviceNet Unit that returned the response is returned in hexadecimal.

Read data (response):

The specified area, word, and byte data is returned in order from word H (high byte: bits 8 to 15) to word L (low byte: bits 0 to 7). If an odd number is specified for the number of read bytes, the last 1 byte of data will be read to the high word.

The actual address L, address H, and number of read bytes that can be specified depends on the model of the CPU Unit of the CS/CJ-series DeviceNet

Unit and the type of memory area. Do not exceed the boundary of the data areas for the PLC you are using.

Word Data Read (Service Code: 1D Hex)

Word Data Read reads I/O memory area data in CPU Units with a CS/CJseries DeviceNet Units. The read word data is in word units. The response block is returned from low to high bytes.

Command Block

1C 2F

(*) (*)

Class ID

Service Code

Address L

Instance ID

No. of words read

Address H

Note

A body format of either 8 bits or 16 bits is possible.

Response Block

9D

Parameters

Service Code Word data H

Word data L

Word data H

Word data L

Read data (200 bytes max.)

Service code (command, response):

ID Hex is specified for commands. For responses, the highest bit will turn ON and 9D Hex will be returned.

Class ID (command):

Always 2F Hex.

Instance ID (command):

The type of memory area that will read the data is specified as shown in the following table.

Instance ID (Hex)

01

03

04

05

08 to 14

CPU Unit memory area for read

CIO

DM

WR

HR

EM, banks 0 to C

Word range

0000 to 6143

D00000 to D32767

W000 to W511

H000 to H511

En_00000 to En_32767

(n: 0 to C)

Address L, Address H (command):

The address of the first word to read the data from is specified in hexadecimal as shown below.

Address L: The lower 2 digits when the first word address is given in 4-digit hexadecimal.

177

Receiving Explicit Messages

Section 6-5

Important Points

Address H: The higher 2 digits when the first word address is given in 4-digit hexadecimal.

No of Read Words (command):

The number of words of read data is specified in 1-byte (2-digit) hexadecimal. The range is 01 to 64 Hex (1 to 100 decimal).

Read data (response):

The specified area, word, and byte data is returned in order from word L (low byte: bits 0 to 7) to word H (high byte: bits 8 to 15).

The actual address L, address H, and number of write data bytes that can be specified depends on the CPU Unit of the CS/CJ-series DeviceNet Unit and the Memory Area. Do not exceed the boundary of the data areas for the PLC you are using.

Byte Data Write (Service Code: 1E Hex)

Byte Data Write writes data to I/O memory area in CPU Units with CS/CJseries DeviceNet Units mounted. The write word data is in byte units. The command block is specified from high to low bytes, as shown in the following diagram.

Command Block

1E 2F

(*) (*)

Class ID

Service Code

Address L

Instance ID

Word data H

Address H Word data L

Word data H

Word data L

Write data (200 bytes max.)

Note

A body format of either 8 bits or 16 bits is possible.

Response Block

9E

Parameters

Service Code

Service code (command, response):

IE Hex is specified for commands. For responses, the highest bit will turn ON and 9E Hex will be returned.

Class ID (command):

Always 2F Hex.

Instance ID (command):

The type of memory area to which the data will be written is specified as shown in the following table.

Instance ID (Hex)

01

03

04

05

08 to 14

CPU Unit memory area for write

CIO

DM

WR

HR

EM, banks 0 to C

Word range

0000 to 6143

D00000 to D32767

W000 to W511

H000 to H511

En_00000 to En_32767

(n: 0 to C)

Address L, Address H (command):

The address of the first word to which the data will be written is specified in hexadecimal as shown below.

Address L: The lower 2 digits when the first word address is displayed in 4digit hexadecimal.

178

Receiving Explicit Messages

Section 6-5

Important Points

Address H: The higher 2 digits when the first word address is displayed in 4digit hexadecimal.

Write data (response):

The specified area and write data is returned in order from word H (higher byte: bits 8 to 15) to word L (lower byte: bits 0 to 7). If an odd number is specified, the last 1 byte of data will be written to word H.

The actual address L, address H, and number of write data words that can be specified depends on the type of CPU Unit with CS/CJ-series DeviceNet Unit mounted and the type of memory area. Do not exceed the boundary of the data areas for the PLC you are using.

Word Data Write (Service Code: 1F Hex)

Word Data Write writes data to any I/O memory area in CPU Units with CS/

CJ-series DeviceNet Units mounted. The write word data is in word units. The response block is returned from low to high bytes.

Command Block

1F 2F

(*) (*)

Class ID

Service Code

Address L

Instance ID

Word data L

Address H Word data H

Word data L

Word data H

Write data (200 bytes max.)

Note

A body format of either 8 bits or 16 bits is possible.

Response Block

9F

Parameters

Service Code

Service code (command, response):

IF Hex is specified for commands. For responses, the highest bit will turn ON and 9F Hex will be returned.

Class ID (command):

Always 2F Hex.

Instance ID (command):

The memory area to which the data is written is specified as shown in the following table.

Instance ID (Hex)

01

03

04

05

08 to 14

CPU Unit memory area for write

CIO

DM

WR

HR

EM, banks 0 to C

Word range

0000 to 6143

D00000 to D32767

W000 to W511

H000 to H511

En_00000 to En_32767

(n: 0 to C)

Address L, Address H (command):

The address of the first word to which the data is written is specified in hexadecimal as shown below.

Address L: The lower 2 digits when the first word address is displayed in 4digit hexadecimal.

Address H: The higher 2 digits when the first word address is displayed in 4digit hexadecimal.

179

Receiving Explicit Messages

Important Points

Section 6-5

Write data (response):

The specified area and write data is returned in order from word L (lower byte: bits 0 to 7) to word H (higher byte: bits 8 to 15).

The actual address L, address H, and number of read words that can be specified depends on the mode of CPU Unit for the CS/CJ-series DeviceNet Unit and the type of memory areas. Do not exceed the boundary of the data areas for the PLC you are using.

180

SECTION 7

Other Functions

This section describes connecting to CX-Programmer via the DeviceNet and the Memory Card backup function.

7-1

7-2

7-3

Connecting to the CX-Programmer via the DeviceNet. . . . . . . . . . . . . . . . . .

7-1-1

7-1-2

7-1-3

Setting Node Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Setting the Message Monitoring Timer of the DeviceNet Unit . . . .

7-1-4

Setting the Frame Length when Using the CX-Programmer via the DeviceNet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Response when Using the CX-Programmer via the DeviceNet . . . .

Memory Card Backup Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7-2-1 Outline of Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7-2-2 File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Simple Backup Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7-3-1

7-3-2

7-3-3

Overview of Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Operating Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

182

183

183

185

185

186

187

188

189

189

189

190

181

Connecting to the CX-Programmer via the DeviceNet

7-1

Section 7-1

Connecting to the CX-Programmer via the DeviceNet

With CX-Programmer Ver. 2.1 or higher, a serial connection can be made to a

PLC containing a CS/CJ-series DeviceNet Unit to form an online connection, via the DeviceNet, to other PLC CPU Units on the network.

• CS-series CPU Unit

• CJ-series CPU Unit

• Programmable Slave

DeviceNet Unit

Serial -->

DeviceNet gateway

CX-Programmer Ver. 2.1 or higher

Serial connection (Host Link or peripheral bus)

Online connection (enabling all online functions, including remote programming and monitoring)

DeviceNet

Programmable

Slave

CS-series CPU

Unit

CJ-series CPU

Unit

It is also possible to form an online connection (for remote programming or monitoring) with the PLC CPU Units shown above on the DeviceNet network from another network.

CX-Programmer

Ver. 2.1 or higher

Ethernet --> DeviceNet gateway

Ethernet

Ethernet Unit

DeviceNet Unit

Online connection (enabling all online functions, including remote programming and monitoring)

DeviceNet

DeviceNet Unit

Programmable

Slave

CS/CJ-series

182

Connecting to the CX-Programmer via the DeviceNet

Section 7-1

7-1-1 Setting Node Addresses

When the CX-Programmer is connected online, it uses FINS message communications. It is thus necessary to set the node address to a number other than 0 for DeviceNet Units mounted to the target PLC, DeviceNet Units mounted to a PLC which is connected by a serial connection to the CX-Programmer, or DeviceNet Units mounted to a PLC relaying between networks.

If a DeviceNet Unit with the address node 0 exists in the online connection path, connection will not be possible.

7-1-2 Setting the Message Monitoring Timer of the DeviceNet Unit

When connecting the CX-Programmer via the DeviceNet, set the message monitoring timer inside the following DeviceNet Units to 20,000 ms (20 s).

• The DeviceNet Unit mounted to the PLC with the serial connection to the

CX-Programmer.

• The DeviceNet Unit mounted to the PLC relaying between networks.

DeviceNet Unit

CX-Programmer Ver.

2.1 or higher

CX-Programmer Ver.

2.1 or higher

Serial connection (Host

Link or peripheral bus)

DeviceNet

Ethernet

Ethernet Unit

DeviceNet Unit

Set the message monitoring timer of this DeviceNet Unit to 20,000 ms (20 s).

Set the message monitoring timer of this

DeviceNet Unit to

20,000 ms (20 s).

DeviceNet

Setting the Message

Monitoring Timer

1,2,3...

Use the Configurator to set the message monitoring timer.

Use the following procedure to set the message monitoring timer.

1.

Select

Device/Parameter/Edit

and then click the

Message Timer

Tab.

183

Connecting to the CX-Programmer via the DeviceNet

Section 7-1

184

2.

Double-click on the node address (#) that you want to change, or select the node address and click on the

Edit

Button. A dialogue box like the one below will appear.

Note

3.

Input the value, then click on the

OK

Button.

Note

To set the same value for all of the devices, select the node addresses to be set, then click on

Copy to All Device

.

1.

2.

The default setting for the message monitoring timer is 2,000 ms (2 s). If it is used without being changed, a communications error will result when the

CX-Programmer is operated. The setting range is 500 to 30,000 ms. Set in units of ms.

The message monitoring timer serves as a timeout monitor for message communications (both explicit and FINS). Settings can be made for each device to which messages are to be sent. When the response from the target device is slow, the setting value must be increased. This is often the case when FINS messages are sent across networks, because the response time is typically slow. However, when the setting is increased, subsequent messages cannot be sent to the same device until it is finished waiting for the response.

Whereas the DeviceNet Unit monitors the message time-out with this timer, the CPU Unit monitors with the response monitor time set in the CMND/

SEND/RECV instruction. There is thus no effect when only one of them, i.e., only the message monitoring timer or only the response monitor time in the CMND/SEND/RECV instruction, is increased or decreased. Set the

Connecting to the CX-Programmer via the DeviceNet

7-1-3

Section 7-1

response monitor time in the CMND/SEND/RECV instruction to be the same as or slightly longer than the time for the message monitoring timer

(Response monitor time in the CMND/SEND/RECV instruction

≥ message monitoring timer.)

If time-outs occur frequently, increase both of the settings equally, while maintaining the relationship between them.

Setting the Frame Length when Using the CX-Programmer via the

DeviceNet

When using the CX-Programmer via the DeviceNet, set the frame length in the

Network Settings

under

Change PLC

from the CX-Programmer to 542 bytes or less.

When using the peripheral bus, the value must be changed because the default setting is 1,004 bytes. The Host Link (SYSMAC WAY) does not need to be changed because the factory setting is 540 bytes.

The frame length setting is made with the following window. Click on the

Settings

Button to the right of

Network Type

in the

Change PLC

Dialog Box to access this window.

Set this value to 542 or less.

7-1-4

Refer to the operation manual for the CX-Programmer for details.

Response when Using the CX-Programmer via the DeviceNet

To assure appropriate remote I/O response in the DeviceNet field network, the

DeviceNet Unit is designed to prioritize remote I/O communications over message communications. For this reason, when the CX-Programmer is connected via the DeviceNet Unit, its response suffers by up to a nine-fold drop

(for a communications speed of 500 Kbps) in comparison with connection by a peripheral bus.

The following methods can be used to improve this response.

1,2,3...

1.

Temporarily disable remote I/O communications.

Operate the CX-Programmer after disabling remote I/O communications by turning ON the Remote I/O Communications Stop Switch (word n, bit

04) in the allocated CIO Area words. This will limit the drop in response to

185

Memory Card Backup Functions

Section 7-2

2.

a maximum of four-fold (for a communications speed of 500 Kbps) in comparison with connection by a peripheral bus.

Temporarily extend the communications cycle time.

Operate the CX-Programmer after extending the cycle time in the Communications Cycle Time Setup Table (word m) in the DM Area, and turning ON the Temporary Setting Switch for Communications Cycle Time (word n, bit

12).

Extending the communications cycle time 1.5 times will result in a 20%-

30% improvement in response. However, whereas the CX-Programmer response will increasingly improve by extending the communications cycle time, the remote I/O communications response will suffer.

Note

The CX-Programmer response decreases in accordance with decreases in the DeviceNet communications speed. At a speed of 125 Kbps, response will suffer by up to a twenty-fold drop in comparison with connection by a peripheral bus.

Accordingly, a DeviceNet communications speed of 500 Kbps is recommended when the CX-Programmer is connected to the network via the

DeviceNet Unit.

7-2 Memory Card Backup Functions

The DeviceNet Unit stores the following setup data in the internal non-volatile memory (EEPROM).

• Master scan lists

• Slave scan lists

• Message monitoring timer lists

• Communications cycle time settings

• Master/Slave functions enabled/disabled settings

Note

Backup is possible only when scan lists are enabled.

With the CS/CJ-series DeviceNet Unit, all this setup data can be backed up to and restored from a Memory Card mounted to the CPU Unit. (See note.)

Note

The data can be backed up to a Memory Card only. It cannot be backed up to a EM file.

If all setup data for a DeviceNet Unit that starts normally is saved on a Memory Card, that data can be read and used when replacing DeviceNet Units, making the replacement process smooth.

Device parameter files (.dvf files) created using the Configurator can be saved from the computer to the Memory Card and can be restored to the DeviceNet

Unit mounted to the CPU Unit. This means that setup data created using the

Configurator (scan lists and other parameters) can be downloaded to

DeviceNet Units simply by taking the Memory Card to site.

186

Memory Card Backup Functions

DeviceNet Unit

CPU Unit

All setup data

Backup

Restore

Section 7-2

Unit Setup File Backup Switch

Unit Setup File Restore Switch

Memory Card

Save file

Load file

Configurator (computer)

7-2-1 Outline of Functions

1. Backing Up Unit Setup Files

Saves all internal Unit setup data to the Memory Card mounted to the CPU

Unit.

Method: Turn ON the Setup File Backup Switch (word n+1, bit 15) to save the internal Unit setup data to the Memory Card as a Unit Setup File.

DeviceNet Unit CPU Unit

Unit Setup File Backup switch data

Memory Card

Backup

2. Restoring Unit Setup Files

Restoring Unit Setup Files involves reading the data and setting it to a Unit.

The data saved to the Memory Card mounted to the CPU Unit is read to the

Unit.

Method: Turn ON the Unit Setup File Restore Switch (word n+1, bit 14) to read the Unit setup data file on the Memory Card and to enable these settings as the Unit settings.

187

Memory Card Backup Functions

DeviceNet Unit

All setup data

CPU Unit

Section 7-2

Unit Setup File Restore Switch

Memory Card

Restore

Note

If there is an error in the setup data or if the file could not be read, the File

Read/Write Error bit in Unit Status 2 (word n + 11, bit 08) will turn ON.

3. Saving Files from Configurator to Memory Card

Device parameter files (.dvf files) for this DeviceNet Unit that have been created using the Configurator can be saved on the Memory Card via the HMC-

AP001 Memory Card Adaptor as file name DNnnBKUP.dvf (where nn is the

Unit number in 2-digit hexadecimal). This DeviceNet Unit can be mounted to the CPU Unit and, by turning ON the Unit Setup File Restore Switch (word n, bit 14), the setup data can be restored to the DeviceNet Unit.

Note

The file name when saving setup data to the Memory Card must be DNnn-

BKUP.dvf (where nn is the Unit number in 2-digit hexadecimal). For example, for unit number 00, the file name must be DN00BKUP.dvf. If the file is saved under another name, the data cannot be restored from the Memory Card to the DeviceNet Unit.

CPU Unit DeviceNet Unit

All setup data

Unit Setup File Restore Switch

HMC-AP001 Memory Card Adaptor

Memory Card

Memory Card

Configurator (computer)

Restore

Saving device parameter file

Saved as file name DNnnBKUP.dvf, where nn is the Unit number in 2-digit hexadecimal.)

7-2-2 File Names

The following files are created on the Memory Card.

Directory (fixed): Route and directory.

File name (fixed): DNnnBKUP.dvf (nn: Unit number in 2-digit hexadecimal).

Note

The data in the above files is compatible with the data in the DeviceNet Unit device parameter file.

188

Simple Backup Function

Section 7-3

7-3

7-3-1

Simple Backup Function

Overview of Function

The CPU Unit’s simple backup function can be used when either a CS1W-

DRM21-V1 DeviceNet Unit is mounted to a CS1-H CPU Unit, or a CJ1W-

DRM21 DeviceNet Unit to a CJ1-H CPU Unit. This function enables all setup data in the internal non-volatile memory (EEPROM) of the DeviceNet Unit, as well as all data in the CPU Unit, to be automatically backed up to, restored from, or compared with a file in a Memory Card mounted in the CPU Unit.

When all the setup data in the DeviceNet Unit is written to the Memory Card using a simple backup operation, it is backed up as a Unit/Board backup file in the Memory Card under the file name BACKUP @@ .PRM.

Note

The boxes in the backup file name represent the unit address of the

DeviceNet Unit, which is the unit number + 10 hex.

This backup file is also used when downloading data from or comparing data with a file in the Memory Card.

DeviceNet Unit

Memory Card Power Supply Switch

CPU Unit

All data

All setup data

Backing up data

Restoring data

Comparing data

Memory Card

7-3-2

Note

The following table shows the Units that support the simple backup function.

Make sure that the Units being used support the function.

CPU Unit

CS1-H CPU Unit

CS1 CPU Unit

CJ1-H CPU Unit

CJ1 CPU Unit

CS1W-DRM21-V1

Yes

No

No

No

DeviceNet Unit

CS1W-DRM21

No

No

No

No

CJ1W-DRM21

No

No

Yes

No

Note

The DeviceNet Unit’s setup data that is created as a Unit/Board backup file is the same setup data that is backed up and restored when using the backup function described in

7-2 Memory Card Backup Functions

, but is not compatible with the device parameter file. In the same way, although the content of the device parameter file created using DeviceNet Configurator Ver.2.

@ is the same, it is not compatible with the backup file created using the simple backup function.

Applications

Use the simple backup function to create a backup file of data for the entire

PLC, including the CPU Unit and Serial Communications Units/Boards, or when replacing all the Units.

189

Simple Backup Function

Section 7-3

7-3-3 Operating Methods

Backing Up DeviceNet Unit Setup Files to Memory Card

Set the DIP switch on the front panel of the CPU Unit, as shown in the following table, and press down the Memory Card Power Supply Switch for 3 seconds.

DIP switch on front panel of

CPU Unit

Pin 7 Pin 8

ON OFF

DeviceNet Unit

Memory Card Power Supply Switch

CPU Unit

All data

All setup data

Backing up data

Memory Card

This operation will create the DeviceNet backup file and also write the file to the Memory Card.

When the Memory Card Power Supply Switch is pressed, the MCPWR indicator on the front of the CPU Unit will flash once and then will be lit while data is being written. If the data is written normally, the indicator will turn OFF.

Restoring DeviceNet Unit Setup Files from Memory Card (Reading and Setting in Unit)

Set the DIP switch on the front panel of the CPU Unit, as shown in the following table, turn the power to the CPU Unit OFF and then ON again.

DIP switch on front panel of

CPU Unit

Pin 7

ON

Pin 8

OFF

DeviceNet Unit

Power ON

All setup data

Restoring data

CPU Unit

All data

Memory Card

This operation will read the DeviceNet Unit setup data file from the Memory

Card and restore the data in the DeviceNet Unit.

190

Simple Backup Function

Section 7-3

When the power supply is ON, the MCPWR indicator on the front of the CPU

Unit will turn ON, flash once, and then will remain lit while data is being read.

After the data is read correctly, the indicator will turn OFF.

Note

The 7-segment display on the front panel will display “H8” when restoring data from a Memory Card fails. If this happens, the data on the Memory Card may not be correct. Make sure that the backup operation ends normally before performing the restore operation.

Comparing DeviceNet Unit Setup Files in Memory Card

Set the DIP switch on the front panel of the CPU Unit, as shown in the following table, and press down the Memory Card Power Supply Switch for 3 seconds.

DIP switch on front panel of

CPU Unit

Pin 7

OFF

Pin 8

OFF

DeviceNet Unit

Memory Card Power Supply Switch

CPU Unit

All data

Memory Card

All setup data

Comparing data

This operation will compare the data in the DeviceNet setup file in the Memory

Card with the setup data in the DeviceNet Unit.

When the Memory Card Power Supply Switch is pressed, the MCPWR indicator on the front of the CPU Unit will flash once, and then will remain lit while data is being compared. If the data is the same, the indicator will turn OFF.

Note

The following table compares the simple backup functions with the Memory

Card backup functions described in

7-2 Memory Card Backup Functions

.

191

Simple Backup Function

Section 7-3

Applicable

CPU Units

Function

CS Series

Applicable

DeviceNet Units

CJ Series

Back up, restore, and compare data

File name

CJ Series

CS Series

Compatibility with DeviceNet Configurator device parameter file

Simple backup

CS1-H CPU Units only

Memory Card backup

CS1 CPU Units (-V

@

)

CS1-H CPU Units

CJ1-H CPU Units

CJ1M CPU Units

CS1W-DRM21-V1 only

CJ1 CPU Units

CJ1-H CPU Units

CS1W-DRM21-V1

CS1W-DRM21

CJ1W-DRM21 CJ1W-DRM21

The following setup data in the DeviceNet Unit’s internal non-volatile memory

(EEPROM):

• Master scan lists

• Slave scan lists

• Message monitoring timer lists

• Communications cycle time settings

• Master/slave functions enabled/disabled settings

BACKUP

@@

.PRM

(

@@

: Unit address = Unit number +

10 hex)

DNnnBKUP.dvf (nn: Unit number in 2digit hexadecimal)

No Yes

Note

The file must have the same extension (.dvf) as the device parameter file created using

DeviceNet Configurator.

Storage media

Operating method

Main applications

Backing up data to

Memory Card

Restoring data from

Memory Card

Comparing data with

Memory Card

Memory Card mounted in CPU Unit

Turn ON pin 7 and turn OFF pin 8 of the

CPU Unit’s DIP switch, and press down the Memory Card Power Supply Switch for three seconds.

Turn ON pin 7 and turn OFF pin 8 of the

CPU Unit’s DIP switch, and turn ON the power to the CPU Unit.

Turn OFF pins 7 and 8 of the CPU

Unit’s DIP switch, and press down the

Memory Card Power Supply Switch for three seconds.

Turn OFF the Setup File Backup Switch

(word n+1, bit 15) and then turn it ON again.

Turn OFF the Unit Setup File Restore

Switch (word n+1, bit 14) and then turn it ON again.

None

• Replacing the entire PLC including the CPU Unit and other Units (Serial

Communications Units/Boards, etc.)

• Replacing the DeviceNet Unit only.

• Using the DeviceNet Configurator to create setup data, save it in the Memory Card, and then write the data to the DeviceNet Unit from the Memory

Card.

• Using multiple DeviceNet Units with the same settings (copying the settings from the Memory Card to multiple DeviceNet Units).

192

SECTION 8

Communications Timing

This section describes the time required for remote I/O communications and message communications.

8-1

8-2

Remote I/O Communications Characteristics. . . . . . . . . . . . . . . . . . . . . . . . .

8-1-1

8-1-2

Communications Cycle Time and Refresh Time . . . . . . . . . . . . . . .

I/O Response Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8-1-3

8-1-4

More than One Master in Network . . . . . . . . . . . . . . . . . . . . . . . . . .

System Startup Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Message Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8-2-1 Message Communications Time. . . . . . . . . . . . . . . . . . . . . . . . . . . .

8-2-2 Calculating the Maximum Message Response Time . . . . . . . . . . . .

194

194

197

199

199

200

200

201

193

Remote I/O Communications Characteristics

Section 8-1

8-1 Remote I/O Communications Characteristics

This section describes the characteristics of remote I/O communications when the DeviceNet Unit is used as a master in combination with OMRON’s slaves. Use this section for reference when planning operations that require precise I/O timing.

The equations provided here are valid under the following conditions:

1,2,3...

1.

2.

3.

4.

The DeviceNet Unit is operating with the scan list enabled.

All of the required Slaves are participating in communications.

No errors are being indicated at the DeviceNet Unit

Messages aren’t being produced in the Network (from another company’s configurator, for example).

Note

The values provided by these equations may not be accurate if another company’s Master or Slave is being used in the Network.

8-1-1 Communications Cycle Time and Refresh Time

This section explains the communications cycle time, communications time per slave, and refresh time required for calculating processing time by the

DeviceNet Unit.

Communications Cycle Time

The communications cycle time is the time from the completion of a Slave’s remote I/O communications processing until remote I/O communications with the same Slave are processed again. The communications cycle time is used to calculate the maximum I/O response time.

The communications cycle time depends on the number of Masters in the

Network and on whether or not message communications are being performed. The following explanation is for a network with one Master. For networks with several Masters, refer to

More than One Master in Network

in the following section.

Communications Cycle

Time Graph

The following graph shows communications cycle time for the number of slaves when there are both 16-point output and 16-point input slaves.

Inputs: Bit strobe, Outputs: Poll connection

Number of Slaves

: Communications cycle time: 500 kbps (ms)

: Communications cycle time: 250 kbps (ms)

: Communications cycle time: 125 kbps (ms)

194

Remote I/O Communications Characteristics

Section 8-1

Communications Cycle

Time Calculation

Use the equations shown below to calculate the communications cycle time

(T

RM

) for a network with one Master. Note that if the result of this calculation is less than 2 ms, the actual communications cycle time will be 2 ms.

T

RM

=

Σ

(Communications time per Slave)

+ High-density Unit processing time

+ Explicit message communications time

+ COS/Cyclic connection time (ms)

+ 0.01

×

N + 1.0 [ms]

Communications Time per Slave:

This is the communications time required for a single Slave.

Σ

(Communications time per Slave)” represents the total of the “Communications time per Slave” for all the Slaves in the network.

High-density Unit Processing Time:

3.5 ms

This is added if there are any Slaves in the network that use at least 8 bytes for input, output, or both.

Explicit Message Communications Time:

(0.11

×

T

B

)

× n [ms]

The explicit message communications time is added as a delay time when explicit communications (sending or receiving) are performed.

n= Number of explicit messages (both sending and receiving) that occur in one cycle time

T

B

= The baud rate factor

(500 kbps: T

B

= 2; 250 kbps: T

B

= 4; 125 kbps: T

B

= 8)

COS/Cyclic Connection Time:

{(0.05+0.008

×

S)

×

T

B

}

×

n (ms)

The COS/cyclic connection time is added as a delay time when COS/cyclic communications are performed.

S: Total number of inputs and outputs in the COS/cycle connection (bytes)

T

B

: The baud rate factor

(500 kbps: T

B

= 2; 250 kbps: T

B

= 4; 125 kbps: T

B

= 8) n: Number of nodes occurring simultaneously within 1 communications cycle time in the COS/Cyclic connection

N: Number of Slaves

Communications Time/Slave

The communications time per Slave is the communications time required for a single Slave.

Output Slaves with Less

Than 8 Bytes of Output

Input Slaves with Less

Than 8 Bytes of Input

The following equations show the communications time/Slave (T

RT

) for each kind of Slave Unit.

The communications time for each slave is not related to the type of connection (protocol) used by the slave.

T

RT

= 0.016

×

T

B

×

S

OUT1

+ 0.11

×

T

B

+ 0.07 [ms]

S

OUT1

: The number of Output Slave output words

T

B

: The baud rate factor

(500 kbps: T

B

= 2; 250 kbps: T

B

= 4; 125 kbps: T

B

= 8)

T

RT

= 0.016

×

T

B

×

S

IN1

+ 0.06

×

T

B

+ 0.05 [ms]

S

IN1

T

B

:

: The number of Input Slave input words

The baud rate factor

(500 kbps: T

B

= 2; 250 kbps: T

B

= 4; 125 kbps: T

B

= 8)

195

Remote I/O Communications Characteristics

Mixed I/O Slaves with Less

Than 8 Bytes of Input or

Output

Slaves with More Than 8

Bytes of Input or Out put

Section 8-1

T

RT

= 0.016

×

T

B

×

(S

OUT2

+ S

IN2

) + 0.11

×

T

B

+ 0.07 [ms]

S

OUT2

: The number of Mixed I/O Slave output words

S

IN2

: The number of Mixed I/O Slave input words

T

B

: The baud rate factor

(500 kbps: T

B

= 2; 250 kbps: T

B

= 4; 125 kbps: T

B

= 8)

T

RT

= T

OH

+ T

BYTE-IN

×

B

IN

+ T

BYTE-OUT

×

B

OUT

[ms]

T

OH

:

T

BYTE-IN

:

Protocol overhead

The input byte transmission time

The number of input words B

IN

:

T

BYTE-OUT :

B

OUT :

The output byte transmission time

The number of output words

Baud rate

500 kbps

250 kbps

125 kbps

T

OH

0.306 ms

0.542 ms

1.014 ms

T

BYTE-IN

0.040 ms

0.073 ms

0.139 ms

T

BYTE-OUT

0.036 ms

0.069 ms

0.135 ms

For Input Slaves take B

OUT

to be 0, and for Output Slaves take B

IN

to be 0.

Refresh Time

Note

The refresh time is the time required for I/O data to be exchanged between the PLC’s CPU Unit and the DeviceNet Unit. The CPU Unit’s cycle time is increased when a DeviceNet Unit is mounted, as shown below.

Processing item

I/O refresh

Processing time

DeviceNet Unit I/O refreshing time (ms)

0.7 + 0.001

×

the number of words refreshed (See note 1.)

1.

2.

3.

4.

The number of words refreshed is the total number of words in the I/O area that are used by the Slaves, including any unused words between words actually used by the Slaves. For example, if there are only two Input Slaves with node addresses 1 and 5, the 5 input words for nodes 1 through 5 would be refreshed even though the input words for nodes 2, 3, and 4 are unused.

If message communications are being performed, just add the number of words used in message communications to the above number of words for whenever messages are being processed.

When the message communications are performed, an event execution time must be added to the PLC cycle time.

For details about refresh time or PLC cycle time, refer to operation manual of the PLC.

196

Remote I/O Communications Characteristics

Section 8-1

8-1-2 I/O Response Time

Maximum I/O Response Time

Communications Cycle

Time

PLC Cycle Time

The maximum I/O response time will be as shown below if the DeviceNet Unit takes in data immediately after I/O refreshing and if the communications cycle time is longer than the PLC cycle time.

PLC

Communications cycle

ON input data notice delayed

Instruction execution

Instruction execution

Transfers to the shared RAM when PLC scan is completed.

Takes into the

PLC's internal memory.

Instruction execution

Slave

Communications Cycle

Time < PLC Cycle Time

T

PLC

T

PLC

T

PLC

T

IN

:

T

OUT

:

T

RM

:

T

PLC

:

The Input Slave’s ON (OFF) delay

The Output Slave’s ON (OFF) delay

Network’s communications cycle time (See page 195.)

The PLC’s cycle time (See note below.)

Note

The PLC’s cycle time will be delayed as shown below for one DeviceNet Unit. For details, refer to

Refresh Time

on page 196.

0.7 ms + (number of occupied words

×

0.001 ms)

The maximum I/O response time (T

MAX

) is the total of the following terms:

T

MAX

= T

IN

+ T

RM

×

2 + T

PLC

×

3 + T

OUT

The maximum I/O response time will be as shown below if the DeviceNet Unit takes in data immediately after I/O refreshing and if the communications cycle time is shorter than the PLC cycle time.

PLC

Transfers to the shared RAM when communications cycle is completed.

Communications cycle

Instruction execution

Instruction execution

Slave

T

PLC

T

PLC

T

IN

:

T

OUT

:

The Input Slave’s ON (OFF) delay

The Output Slave’s ON (OFF) delay

197

Remote I/O Communications Characteristics

Section 8-1

Note

T

RM

:

T

PLC

:

Network’s communications cycle time (See page 195.)

The PLC’s cycle time (See note below.)

Note

The PLC’s cycle time will be delayed as shown below for one DeviceNet Unit. For details, refer to

Refresh Time

on page 196.

0.7 ms + (number of occupied words

×

0.001 ms)

The maximum I/O response time (T

MAX

) is the total of the following terms:

T

MAX

= T

IN

+ T

RM

×

2 + T

PLC

×

2 + T

OUT

1.

2.

Refer to the

DeviceNet Slaves Operation Manual

(W347 or W404) for details on the Input and Output Slaves’ delay times.

Refer to

Refresh Time

on page 196 and to the PLC’s Operation Manual for

details on the PLC’s cycle time.

Minimum I/O Response Time

The minimum I/O response time occurs when the Slave’s I/O refreshing is executed just after the input signal is received by the DeviceNet Unit and the output signal is output at the beginning of the next I/O refresh cycle.

T

PLC

PLC

Instruction execution

Master Unit processing

Input

Output

Note

(T

PLC

+T

RF

)

T

IN

:

T

OUT

:

The Input Slave’s ON (OFF) delay

The Output Slave’s ON (OFF) delay

T

RT-IN

: Input Slave’s communications time/Slave (See page 195.)

T

RT-OUT

: Output Slave’s communications time/Slave (See page 195.)

T

PLC

: The PLC’s cycle time

T

RF

:

The PLC’s DeviceNet Unit refresh time (See page 196.)

The minimum I/O response time (T

MIN

) is the total of the following terms:

1.

2.

T

MIN

= T

IN

+ T

RT-IN

+ T

PLC

+ T

RF

+ T

RT-OUT

+ T

OUT

Refer to the

DeviceNet Slaves Operation Manual

(W347 or W404) for details on the Input and Output Slaves’ delay times.

Refer to

Refresh Time

on page 196 and to the PLC’s Operation Manual for

details on the PLC’s cycle time.

198

Remote I/O Communications Characteristics

8-1-3

Section 8-1

More than One Master in Network

The following equation shows the remote I/O communications cycle time

(T

RM

) when there is more than one master in the network. An example for two masters is used.

First, the network is divided into two groups: Master A and the slaves in remote I/O communications with it and master B and the slaves in remote I/O communications with it.

Group A Group B

Master A Master B

Slave A

Slave B

Slave C

Slave D Slave E

Slave F

Slaves in remote I/O communications with Master A

Slaves in remote I/O communications with Master B

Note

Although in the above diagram the Slaves are separated into two groups for convenience, the actual physical positions in the Network are irrelevant.

Next, we can refer to

8-1-1 Communications Cycle Time and Refresh Time

and calculate the communications cycle time for each group as if they were separate Networks.

Group A

Group B

Master A

Master B

Slave A

Slave B

Slave C

Slave D Slave E

Slave F

Group A communications cycle time: T

RM-A cycle time: T

RM-B

In Networks with two Masters, the communications cycle time for the entire

Network will be the sum of the communications cycle times for the groups.

T

RM

= T

RM-A

+ T

RM-B

Although this example shows only two Masters in the Network, the total communications cycle time for any Network can be calculated by dividing it into groups and adding the communications cycle times of all groups.

8-1-4 System Startup Time

Master Function

This section describes the system startup time for a network operating with the scan list enabled. The system startup time is the delay from the time that the DeviceNet Unit (master) is turned ON until remote I/O communications begin. Here, we assume that the scan list is enabled and that remote I/O communications are set to start automatically at startup.

The following table shows the system startup times for two cases. In the first case, the DeviceNet Unit starts up just after all of the Slaves’ power supplies are turned ON. In the second case, the DeviceNet Unit is restarted while communications are in progress.

199

Message Communications

Program Example

Section 8-2

Case Slave’s indicator status System startup time

5 seconds The Master is started just after

Slave startup.

Just the Master is restarted.

Just the Slaves are restarted.

The NS indicator is OFF or flashing green.

The NS indicator is flashes red while the Master is OFF.

---

7 seconds

9 seconds

As shown in the preceding table, it takes time for DeviceNet communications to start up. This programming uses flags in the Master status area to prevents the Slaves’ I/O processing from being performed until remote I/O communications start up.

This programming is for a DeviceNet Unit with a unit number of 00.

1512

15

1510

00

Remote I/O

Communications

(n+12, bit 15)

Unit Error

(n+10, bit 00)

Slaves' I/O processing

Note

Refer to

3-2 Allocated CIO Area Words

for details on the Master Status Area.

Slave Function

8-2

8-2-1

It takes approximately four seconds from the time that the Devicenet Unit is turned ON or restarted as a slave until remote I/O communications with the master begin.

Message Communications

Message Communications Time

The message communications time is the time required from the time a Master Unit starts to send a message over the Network to another node until the

Master Unit completes sending the message (data for SEND(192)/

RECV(193) and FINS commands for CMND(194)/IOWR).

The following equation can be used to compute the approximate message communications time.

Message communications time =

Communications cycle time x ((No. of message bytes + 15)

÷

6 + 1)

No. of message bytes: No. of data bytes following the FINS command code

The communications cycle time depends on whether or not remote I/O communications are being used.

Message Communications Only (No Remote I/O Communications)

The following equation can be used to compute the message communications time when remote I/O communications are not being used.

Communications cycle time =

2 (see note) + 0.11

×

T

B

+ 0.6 [ms]

200

Message Communications

8-2-2

Section 8-2

Note

T

B

: The baud rate factor

(500 kbps: T

B

= 2; 250 kbps: T

B

= 4; 125 kbps: T

B

= 8)

The communications cycle time will be 2 ms even if remote I/O communications are not being used.

Remote I/O and Message Communications

Performing message communications in addition to remote I/O communications will increase the message communications time.

Communications cycle time=

Communications cycle time for remote I/O communications only

+ 0.11

×

T

B

+ 0.6 [ms]

T

B

: The baud rate factor

(500 kbps: T

B

= 2; 250 kbps: T

B

= 4; 125 kbps: T

B

= 8)

(Varies depending on the baud rate.)

Note

1.

2.

3.

If the CPU Unit attempts to send another message or receives a message from another node within the message communications time, the second message or the message being received from another node may be destroyed. Never execute a second communications instruction before the message communications time has elapsed and never send messages to any one node at intervals less than the message communications time.

If send or receive messages are destroyed, error records will be placed in the error history of the Master Unit. If an error occurs, read the error history using the FINS command or monitor the error history from the Configurator.

The above equations can be used to find the approximate message communications time, but this is a typical time, not the maximum time. The message communications time will vary depending on the frequency of message communications, the load on the remote node, the communications cycle time, and other factors. For any one Master Unit, the message communications time can be greatly increased due to heavy loads and the user program must be written to allow for this.

Calculating the Maximum Message Response Time

The message response time is the time required from the time a DeviceNet

Unit starts to receive an I/O memory read request message (BYTE DATA

READ explicit message) until the DeviceNet Unit completes sending the response message to the client.

The message response times described below are based on the following conditions:

1,2,3...

1.

2.

3.

4.

5.

6.

Only one DeviceNet Unit is mounted.

The I/O memory read request is returned from CS/CJ-series PLC in two cycle time.

Baud rate: 500 Kbps

Communications cycle time: 3 ms (no remote I/O communications)

PLC’s cycle time: 10 ms

DeviceNet Unit’s refresh time: 2 ms (See note.)

Note

The PLC’s cycle time will be delayed as shown below for one DeviceNet Unit. For details, refer to

Refresh Time

on page 196.

0.7 ms + (number of occupied words

×

0.001 ms)

201

Message Communications

Request from One Client (BYTE DATA READ)

PLC

Instruction execution

Instruction execution

BYTE DATA READ processing time:

PLC's cycle time x 2

Shared memory

Section 8-2

DeviceNet internal buffer

Communications cycle

Read request

Client

Read result

T

PLC

T

PLC

Shown below is the response time required to return data for 100 words.

• BYTE DATA READ request sending time: T

BRS

DeviceNet header (4 bytes) + Parameters (3 bytes) = 7 bytes (no fragment)

Therefore, T

BRS

= 1 communications cycle time (T

RM

) = 3 ms

• PLC’s processing time: T

PC

x 2

T

PLC

x 2 = PLC’s cycle time x 2 = 10 x 2 = 20 ms

• BYTE DATA READ response receiving time: T

BRR

DeviceNet header (3 bytes) + Number of words to be read x 2 = 203 bytes

Therefore, T

BRR

= 1 + 203 bytes/6 communications cycle time = 35 communications cycle time

• DeviceNet Unit refresh time: T

RF

= 2 ms

The message response time will be as follows:

= T

RM

+ T

PLC

x 2 + T

RM

x 35 + T

RF

x 2 =3+20+105+4

= 132 ms

Shown below is the response time required to return data for 100 words to 8 clients.

• BYTE DATA READ request sending time: T

BRS

DeviceNet header (4 bytes) + Parameters (3 bytes) = 7 bytes (no fragment)

Therefore, T

BRS

= 1 communications cycle time (T

RM

) = 3 ms

• PLC’s processing time: T

PLC

x 6 + T

PLC

x 2 = T

PLC

x 8

The following time is required to process data with other clients before the

PLC starts processing.

7 other clients/2 = Approximately cycle time x 3

If one processing requires twice the cycle time, the time will be as follows:

Cycle time x 3 x 2 = Cycle time x 6

PLC’s processing time: T

PLC

x 2 = Cycle time x 2

Total time will be as follows:

Cycle time x 8

202

Message Communications

Section 8-2

• BYTE DATA READ response receiving time: T

BRR

DeviceNet header (3 bytes) + Number of words to be read x 2 = 203 bytes

Therefore, T

BRR

= 1 + 203 bytes/6 communications cycle time = 35 communications cycle time

• DeviceNet Unit refresh time: T

RF

= 2 ms

The message response time will be as follows:

= T

RM

+ T

PLC

x 8 + T

RM

x 35 + T

RF

x 2 x 8 =3+80+105+32

= 220 ms

Note

The above equations can be used to find the approximate message response time, but this is the typical time, not the maximum time. The message response time will vary depending on the frequency of message communications, the load on the remote node, the communications cycle time, and other factors. For any one DeviceNet Unit, the message communications time can be greatly increased due to heavy loads and the user program must be written to allow for this.

203

Message Communications

Section 8-2

204

SECTION 9

Troubleshooting and Maintenance

This section describes error processing, periodic maintenance operations, and troubleshooting procedures needed to keep the DeviceNet network operating properly. We recommend reading through the error processing procedures before operation so that operating errors can be identified and corrected more quickly.

9-1

9-2

9-3

9-4

Troubleshooting with the DeviceNet Unit Indicators . . . . . . . . . . . . . . . . . . .

9-1-1

9-1-2

Determining Operating Status from the Indicators. . . . . . . . . . . . . .

Troubleshooting Errors Occurring in the DeviceNet Unit . . . . . . . .

Error Log Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9-2-1 Error Log Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9-2-2 Error Codes and Detail Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9-3-1

9-3-2

9-3-3

9-3-4

CPU Unit’s ERR/ALM Indicator Lit or Flashing. . . . . . . . . . . . . . .

Remote I/O Communications Disabled . . . . . . . . . . . . . . . . . . . . . .

I/O Link Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Communications Error Operation Settings. . . . . . . . . . . . . . . . . . . .

9-3-5 Scan List Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Maintenance and Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9-4-1

9-4-2

9-4-3

Cleaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Replacing Faulty Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

230

231

231

231

232

228

228

229

230

206

206

207

224

224

225

228

205

Troubleshooting with the DeviceNet Unit Indicators

Section 9-1

9-1 Troubleshooting with the DeviceNet Unit Indicators

9-1-1

MS

OFF

ON

(green)

ON

(green)

ON

(green)

ON

(green)

Determining Operating Status from the Indicators

The following table shows the status of the MS and NS indicators and the 7segment display during normal operation.

Indicator status

NS 7-segment

OFF OFF

Network/Unit status Comments

Initializing with PLC Initialization processing with the PLC is in progress.

Restart the DeviceNet Unit if this status continues for an extended period of time. Replace the CPU

Unit and/or DeviceNet Unit if the problem is not corrected by restarting.

The node address duplication check is performed after initialization.

OFF

Flashing

(green)

ON

(green)

ON

(green)

Master’s node address

(flashing)

Master’s node address

(flashing)

Master’s node address

Checking for node address duplication

Waiting for remote I/O communications

Waiting for message communications connection

Master’s node address

- - (flashing)

Remote I/O or message communications in progress.

Scan list operation in progress.

The Unit will have this status until remote I/O communications are performed with the master or slave function. (When both functions are operating, the

Unit will have this status until remote I/O communications are performed with either function.)

The Unit will have this status when both the master and slave functions are disabled and the Unit is waiting for a connection by message communications.

This is the normal display when the master and/or slave is active.

The scan list is being saved in flash memory or the scan list is being cleared.

206

Troubleshooting with the DeviceNet Unit Indicators

Section 9-1

9-1-2 Troubleshooting Errors Occurring in the DeviceNet Unit

Error category

Master function

Software settings errors

Master function

Slave function

Unit errors

CPU Unit exchange

Remote I/O communications stopped by a communications error

CPU Unit status error

Unit status error

Structure error

Incorrect setting

Multiple switches ON

Structure errors

I/O area duplication

I/O area range exceeded

Unsupported slave

Verification errors

Non-existent slave

Illegal vendor

Illegal connection path

I/O size mismatch

Illegal device

Illegal product code

Unsupported connection

Remote I/O communications error

Network errors Network power supply error

Transmission timeout error

Memory access errors

Message monitoring timer list logic error

Slave scan list logic error

Master scan list logic error

Memory access error

Network errors Node address duplication

CPU Unit exchange

Bus Off detected

Unit number duplication

CPU Unit faulty (H2)

DeviceNet Unit faulty

Node address setting error

Communications speed setting error

CPU Unit faulty (H6)

I/O table not registered

Simple backup function restore error

CPU Unit memory faulty

CPU Unit faulty (Hb)

Routing table logic error

I/O refresh error

CPU Unit service monitoring error

CPU Unit watchdog timer error

Remote I/O communications error

Special Unit error

CPU Unit fatal error

Output OFF error

A0

H5

H6

H7

H8

HA

F1

H1

H2

H3

H4

E6

E7

E8

E9

F0 d6 d9

E0

E2

Hb

HC

Hd

HE

HF

L9

OFF

---

---

C0

C2

C4

C5

C6 d0 d1 d2 d5 d6 d6 d6 d6 d6

Note

Error

1.

2.

7-segment

---

Indicators

MS

---

NS

Error log

(Hex)

0346

Page

208

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

Red (flashing)

---

---

---

---

---

Red (flashing)

Red (flashing)

OFF or

Red (flashing)

---

---

---

---

Red (lit) ---

---

Red (flashing) OFF

Red (lit)

Red (flashing)

---

Red (lit)

---

---

OFF

OFF

---

Red (flashing)

OFF

---

---

0340

---

---

---

---

---

000F

0006

---

0012

0344

0345

0341

0342

021A

021A

021A

0602

0211

0011

021A

0347

0002

0001

0345

0601

---

---

---

---

---

---

---

0343

0343

0343

0344

0344

0344

0344

0344

0344

219

220

220

220

220

216

219

219

219

219

212

212

214

215

216

217

217

218

215

221

221

221

222

223

223

213

213

213

214

214

208

209

209

209

210

210

211

211

211

223

The 7-segment display will alternate between the Unit’s node address and the code given in the tables in this section.

When a (master function) structure error or verification error occurs, only the most recent error is displayed for each slave. If the Unit is set to stop

207

Troubleshooting with the DeviceNet Unit Indicators

Section 9-1

remote I/O communications for a communications error, two errors can be displayed: The slave’s communications error and its most recent error.

Master Errors

Remote I/O

Communications Stopped by a Communications

Error

Structure Error:

I/O Area Duplication

A0

7-segment

---

MS indicator

---

NS indicator Error log (Hex)

0346

Likely Cause

Pin 3 on the master’s DIP switch is set to stop communications in the event of a communications error and communications have been stopped due to a remote I/O communications error, network power supply error, or transmission timeout.

DeviceNet Unit Response

Remote I/O communications as a master will stop. Remote I/O communications as a slave and message communications will continue.

Flags Allocated for C200H DeviceNet Master Unit (CIO n+24)

Bit 14 (the Error Flag) will be ON as well as bit 05 or 06 (the Sending Error

Flag or Communications Error Flag).

CIO Area Flags Allocated to DeviceNet Unit

Bit 00 of n+10 (Unit Error Flag) will be ON together with one of the following combinations:

• Bit 02 of n+12 (the Remote I/O Communications Error Flag) and bit 01 of n+10 (the Master Function Error Flag) ON.

• Bit 07 of n+10 (the Network Power Error Flag) ON.

• Bit 08 of n+10 (the Send Timeout Flag) ON.

Correction

Perform error processing according to the cause:

• Remote I/O communications error (See error d9.)

• Network power supply error (See error E0.)

• Transmission timeout error (See error E2.)

Correct the cause of the error and then restart remote I/O communications by toggling bit 02 of n (the Remote I/O Communications Start Switch.) d0

7-segment

---

MS indicator NS indicator

Red (flashing)

Error log (Hex)

0343

Likely Cause

The slave’s I/O areas overlap. (Occurred with the scan list disabled.)

Errors will occur in the active slaves.

DeviceNet Unit Response

Records the error in the error log.

The master will periodically attempt to reconnect with the slave with the structure error.

Flags Allocated for C200H DeviceNet Master Unit (CIO n+24)

Bit 14 (the Error Flag) and bit 04 (the Structure Error Flag) will be ON.

CIO Area Flags Allocated to DeviceNet Unit

Bit 01 of n+12 (the Structure Error Flag) and bits 00 and 01 of n+10 (the Unit

Error Flag and Master Function Error Flag) will be ON.

208

Troubleshooting with the DeviceNet Unit Indicators

Structure Error:

I/O Area Range Exceeded

Structure Error:

Unsupported Slave

Section 9-1

Correction

Set the slaves’ node addresses again.

d1

7-segment

---

MS indicator NS indicator

Red (flashing)

Error log (Hex)

0343

Likely Cause

The slave’s I/O area isn’t within the allowed range. (Occurs with the scan list disabled.)

DeviceNet Unit Response

Records the error in the error log. The master will periodically attempt to reconnect with the slave with the structure error.

Flags Allocated for C200H DeviceNet Master Unit (CIO n+24)

Bit 14 (the Error Flag) and bit 04 (the Structure Error Flag) will be ON.

CIO Area Flags Allocated to DeviceNet Unit

Bit 01 of n+12 (the Structure Error Flag) and bits 00 and 01 of n+10 (the Unit

Error Flag and Master Function Error Flag) will be ON.

Correction

Set the slaves’ node addresses again or use user-set allocations.

d2

7-segment

---

MS indicator NS indicator

Red (flashing)

Error log (Hex)

0343

Likely Cause

The size of the slave’s input and/or output area exceeded 200 bytes. (Occurs with the scan list disabled.)

DeviceNet Unit Response

Records the error in the error log.

The master will periodically attempt to reconnect with the slave with the structure error.

Flags Allocated for C200H DeviceNet Master Unit (CIO n+24)

Bit 14 (Error Flag) and bit 04 (the Structure Error Flag) will be ON.

CIO Area Flags Allocated to DeviceNet Unit

Bit 01 of n+12 (Structure Error Flag) and bits 00 and 01 of n+10 (Unit Error

Flag and Master Function Error Flag) will be ON.

Correction

Use slaves with input and output areas of 200 bytes max.

Verification Error:

Non-existent Slave

d5

7-segment

---

MS indicator NS indicator

Red (flashing)

Error log (Hex)

0344

Likely Cause

A slave registered in the scan list doesn’t exist or the local node’s (master’s) node address is registered in the scan list. (Occurs with the scan list enabled.)

DeviceNet Unit Response

Records the error in the error log.

• If a slave is involved, the master will periodically attempt to reconnect.

• If the master is involved, it will not send an OPEN frame to itself.

209

Troubleshooting with the DeviceNet Unit Indicators

Verification Error:

Illegal Vendor

Verification Error:

Illegal Connection Path

Section 9-1

Flags Allocated for C200H DeviceNet Master Unit (CIO n+24)

Bit 14 (Error Flag) and bit 07 (Comparison Error Flag) will be ON.

CIO Area Flags Allocated to DeviceNet Unit

Bit 00 of n+12 (Comparison Error Flag) and bits 00 and 01 of n+10 (Unit Error

Flag and Master Function Error Flag) will be ON.

Correction

Check the following:

• Matching master and slave baud rates

• Proper cable lengths (trunk and branch lines)

• Broken or loose cables

• Installation of terminators at both ends of the trunk line

• Excessive noise d6

7-segment

---

MS indicator NS indicator

Red (flashing)

Error log (Hex)

0344

Likely Cause

The Configurator is set to check the vendor and the slave’s vendor does not match the registered scan list. (Occurs with the scan list enabled.)

DeviceNet Unit Response

Records the error in the error log.

The master will periodically attempt to reconnect with the slave with the verification error.

Flags Allocated for C200H DeviceNet Master Unit (CIO n+24)

Bit 14 (Error Flag) and bit 07 (Comparison Error Flag) will be ON.

CIO Area Flags Allocated to DeviceNet Unit

Bit 00 of n+12 (Comparison Error Flag) and bits 00 and 01 of n+10 (Unit Error

Flag and Master Function Error Flag) will be ON.

Correction

Inspect the slave and then create the scan list again.

d6

7-segment

---

MS indicator NS indicator

Red (flashing)

Error log (Hex)

0344

Likely Cause

The connection path was set with the Configurator and there is a mistake in the connection path setting in the scan list. (Occurs with the scan list enabled.)

DeviceNet Unit Response

Records the error in the error log.

The master will periodically attempt to reconnect with the slave with the verification error.

Flags Allocated for C200H DeviceNet Master Unit (CIO n+24)

Bit 14 (Error Flag) and bit 07 (Comparison Error Flag) will be ON.

CIO Area Flags Allocated to DeviceNet Unit

Bit 00 of n+12 (Comparison Error Flag) and bits 00 and 01 of n+10 (Unit Error

Flag and Master Function Error Flag) will be ON.

210

Troubleshooting with the DeviceNet Unit Indicators

Verification Error:

I/O Size Mismatch

Verification Error:

Illegal Device

Verification Error:

Illegal Product Code

Section 9-1

Correction

Inspect the slave and then create the scan list again.

d6

7-segment

---

MS indicator NS indicator

Red (flashing)

Error log (Hex)

0344

Likely Cause

The slave’s I/O data size does not match the registered scan list. (Occurs with the scan list enabled.)

DeviceNet Unit Response

Records the error in the error log.

The master will periodically attempt to reconnect with the slave with the verification error.

Flags Allocated for C200H DeviceNet Master Unit (CIO n+24)

Bit 14 (Error Flag) and bit 07 (Comparison Error Flag) will be ON.

CIO Area Flags Allocated to DeviceNet Unit

Bit 00 of n+12 (Comparison Error Flag) and bits 00 and 01 of n+10 (Unit Error

Flag and Master Function Error Flag) will be ON.

Correction

Inspect the slave and then create the scan list again.

d6

7-segment

---

MS indicator NS indicator

Red (flashing)

Error log (Hex)

0344

Likely Cause

The Configurator is set to check the device type and the slave’s device type does not match the registered scan list. (Occurs with the scan list enabled.)

DeviceNet Unit Response

Records the error in the error log.

The master will periodically attempt to reconnect with the slave with the verification error.

Flags Allocated for C200H DeviceNet Master Unit (CIO n+24)

Bit 14 (Error Flag) and bit 07 (Comparison Error Flag) will be ON.

CIO Area Flags Allocated to DeviceNet Unit

Bit 00 of n+12 (Comparison Error Flag) and bits 00 and 01 of n+10 (Unit Error

Flag and Master Function Error Flag) will be ON.

Correction

Inspect the slave and then create the scan list again.

d6

7-segment

---

MS indicator NS indicator

Red (flashing)

Error log (Hex)

0344

Likely Cause

The Configurator is set to check the product code and the slave’s product code does not match the registered scan list. (Occurs with the scan list enabled.)

211

Troubleshooting with the DeviceNet Unit Indicators

Verification Error:

Unsupported Connection

Remote I/O

Communications Error

Section 9-1

DeviceNet Unit Response

Records the error in the error log.

The master will periodically attempt to reconnect with the slave with the verification error.

Flags Allocated for C200H DeviceNet Master Unit (CIO n+24)

Bit 14 (Error Flag) and bit 07 (Comparison Error Flag) will be ON.

CIO Area Flags Allocated to DeviceNet Unit

Bit 00 of n+12 (Comparison Error Flag) and bits 00 and 01 of n+10 (Unit Error

Flag and Master Function Error Flag) will be ON.

Correction

Inspect the slave and then create the scan list again.

d6

7-segment

---

MS indicator NS indicator

Red (flashing)

Error log (Hex)

0344

Likely Cause

The device does not support the I/O service specified in the scan list. (Occurs with the scan list enabled.)

DeviceNet Unit Response

Records the error in the error log.

The master will periodically attempt to reconnect with the slave with the verification error.

Flags Allocated for C200H DeviceNet Master Unit (CIO n+24)

Bit 14 (Error Flag) and bit 07 (Comparison Error Flag) will be ON.

CIO Area Flags Allocated to DeviceNet Unit

Bit 00 of n+12 (Comparison Error Flag) and bits 00 and 01 of n+10 (Unit Error

Flag and Master Function Error Flag) will be ON.

Correction

Inspect the slave and then create the scan list again.

d9

7-segment

---

MS indicator NS indicator

Red (flashing)

Error log (Hex)

0345

Likely Cause

A timeout occurred during remote I/O communications using the master function. (The response from the slave timed out 6 consecutive times.)

DeviceNet Unit Response

Records the error in the error log.

The master will periodically attempt to reconnect with the slave with the error, but remote I/O communications will stop if the master is set to stop communications.

Flags Allocated for C200H DeviceNet Master Unit (CIO n+24)

Bit 14 (Error Flag) and bit 06 (Communications Error Flag) will be ON.

CIO Area Flags Allocated to DeviceNet Unit

Bit 02 of n+12 (Remote I/O Communications Error Flag) and bits 00 and 01 of n+10 (Unit Error Flag and Master Function Error Flag) will be ON.

Correction

Check the following:

212

Troubleshooting with the DeviceNet Unit Indicators

Section 9-1

• Matching master and slave baud rates

• Proper cable lengths (trunk and branch lines)

• Broken or loose cables

• Installation of terminators at both ends of the trunk line

• Excessive noise

Software Switch Setting Errors

CPU Unit Status Error

C0

7-segment

---

MS indicator

---

NS indicator Error log (Hex)

---

Likely Cause

The software settings operation couldn’t be performed because the CPU Unit wasn’t in PROGRAM mode.

DeviceNet Unit Response

The only response is the error code displayed on the 7-segment display. The error display will be cleared the next time that a settings operation is completed normally.

Correction

Switch the CPU Unit to PROGRAM mode and try the operation again.

Unit Status Error

C2

7-segment

---

MS indicator

---

NS indicator Error log (Hex)

---

Likely Cause

The setting operation failed because the Unit could not perform the requested process in its current status. The most common causes of Unit status errors during settings operations are listed below:

• The master was stopped and a software switch operation relating to the master function was performed. (This does not include the master enable operation.)

• The scan list was enabled and a software switch operation was performed that can only be performed while the scan list is disabled. (Scan list enable and fixed allocation setting operations)

• The scan list was disabled and a software switch operation was performed that can only be performed while the scan list is enabled. (Clear scan list and Backup Unit settings file operations)

• The slave was stopped and a software switch operation relating to the slave function was performed. (This does not include the slave enable operation.)

DeviceNet Unit Response

The only response is the error code displayed on the 7-segment display. The error display will be cleared the next time that a settings operation is completed normally.

Correction

Change the Unit’s status to allow the operation and try the operation again.

Structure Error

C4

7-segment

---

MS indicator

---

NS indicator Error log (Hex)

---

213

Troubleshooting with the DeviceNet Unit Indicators

Incorrect Setting

Multiple Switches ON

Section 9-1

Likely Cause

The setting operation failed because a structure error occurred.

DeviceNet Unit Response

The only response is the error code displayed on the 7-segment display. The error display will be cleared the next time that a settings operation is completed normally.

Correction

Correct the cause of the structure error. (See errors d0 to d2.)

C5

7-segment

---

MS indicator

---

NS indicator Error log (Hex)

---

Likely Cause

There was an error in the parameters specified in the user settings and the requested settings could not be made.

DeviceNet Unit Response

The only response is the error code displayed on the 7-segment display. The error display will be cleared the next time that a settings operation is completed normally.

Correction

Check the parameters in the user settings and try the operation again.

C6

7-segment

---

MS indicator

---

NS indicator Error log (Hex)

---

Likely Cause

Two or more software switches were ON simultaneously or a second software switch was turned ON before a prior operation was completed.

DeviceNet Unit Response

The only response is the error code displayed on the 7-segment display. The error display will be cleared the next time that a settings operation is completed normally.

Correction

Execute software switch operations one at a time.

Network Errors

Network Power Error

E0

7-segment

---

MS indicator NS indicator

OFF or Red (flashing)*

Error log (Hex)

0341

Note

The NS indicator will flash red if the error occurs during remote I/O communications, otherwise the indicator will be OFF.

Likely Cause

The communications power supply is not being supplied properly from the network.

DeviceNet Unit Response

Records the error in the error log.

As long as power isn’t being supplied remote I/O communications will remain stopped and errors will be returned in response to requests for message transmissions. The indicator status, scanning, and message processing will

214

Troubleshooting with the DeviceNet Unit Indicators

Section 9-1

return to normal when the network power supply is restored, although scanning will not resume if the DeviceNet Unit is set to stop remote I/O communications when a communications error occurs.

Flags Allocated for C200H DeviceNet Master Unit (CIO n+24)

Bit 14 (Error Flag) and bit 05 (the Sending Error Flag) will be ON.

CIO Area Flags Allocated to DeviceNet Unit

Bits 00 and 07 of n+10 (the Unit Error Flag and Network Power Error Flag) will be ON.

Correction

Check the network power supply and the wiring of the network cables.

Transmission Timeout

Error

E2

7-segment

---

MS indicator NS indicator

OFF or Red (flashing)*

Error log (Hex)

0342

Note

The NS indicator will flash red if the error occurs during remote I/O communications, otherwise the indicator will be OFF.

Likely Cause

A transmission request was not completed normally for one of the following reasons:

• There is not even one device such as a slave in the network.

• The communications speed settings are not the same in all of the nodes.

• CAN controller error

DeviceNet Unit Response

Records the error in the error log.

As long as transmission timeout is in effect, remote I/O communications will remain stopped and errors will be returned in response to requests for message transmissions. The indicator status, scanning, and message processing will return to normal when the network power supply is restored, although scanning will not resume if the DeviceNet Unit is set to stop remote I/O communications when a communications error occurs.

Flags Allocated for C200H DeviceNet Master Unit (CIO n+24)

Bit 14 (Error Flag) and bit 05 (the Sending Error Flag) will be ON.

CIO Area Flags Allocated to DeviceNet Unit

Bits 00 and 08 of n+10 (the Unit Error Flag and Send Timeout Flag) will be

ON.

Correction

Check the following:

• Matching master and slave baud rates

• Proper cable lengths (trunk and branch lines)

• Broken or loose cables

• Installation of terminators at both ends of the trunk line

• Excessive noise

Node Address Duplication

Error

F0

7-segment

---

MS indicator NS indicator

Red (lit)

Error log (Hex)

0211

Likely Cause

The master’s node address is also set on another node.

215

Troubleshooting with the DeviceNet Unit Indicators

Section 9-1

DeviceNet Unit Response

Records the error in the error log.

• The Unit will go off–line and communications will be disabled. Error responses will be returned to all communications requests.

• The exchange of data with the CPU Unit will continue.

Flags Allocated for C200H DeviceNet Master Unit (CIO n+24)

Bit 14 (Error Flag) and bit 01 (the Node Address Duplicated/Bus Off Flag) will be ON.

CIO Area Flags Allocated to DeviceNet Unit

Bits 00 and 06 of n+10 (the Unit Error Flag and Duplicated Node Address

Flag) will be ON.

Correction

Check the node addresses set on other nodes in the network. Correct the settings to eliminate the duplication and restart the DeviceNet Units.

Bus Off Detected

F1

7-segment

---

MS indicator NS indicator

Red (lit)

Error log (Hex)

0340

Likely Cause

A Bus Off condition was detected.

DeviceNet Unit Response

Records the error in the error log.

• The Unit will go off–line and communications will be disabled. Error responses will be returned to all communications requests.

• The exchange of data with the CPU Unit will continue.

Flags Allocated for C200H DeviceNet Master Unit (CIO n+24)

Bit 14 (Error Flag) and bit 01 (the Node Address Duplicated/Bus Off Flag) will be ON.

CIO Area Flags Allocated to DeviceNet Unit

Bits 00 and 05 of n+10 (the Unit Error Flag and Bus Off Flag) will be ON.

Correction

Check the following:

• Matching master and slave baud rates

• Proper cable lengths (trunk and branch lines)

• Broken or loose cables

• Installation of terminators at both ends of the trunk line

• Excessive noise

Memory Access Errors

Message Monitoring

Timer List Logic Error

E6

7-segment MS indicator

Red (flashing) ---

NS indicator Error log (Hex)

021A

Likely Cause

There is an error in the contents of the message monitoring timer list stored in non-volatile memory.

216

Troubleshooting with the DeviceNet Unit Indicators

Slave Scan List Logic

Error

Master Scan List Logic

Error

Section 9-1

DeviceNet Unit Response

Records the error in the error log.

Operation will continue using the default message monitoring timer values.

Flags Allocated for C200H DeviceNet Master Unit (CIO n+24)

Bit 14 (Error Flag) and bit 03 (the Structure Error Flag) will be ON.

CIO Area Flags Allocated to DeviceNet Unit

Bits 00 and 13 of n+10 (the Unit Error Flag and Incorrect Message Monitoring

Timer List Data Flag) will be ON.

Correction

Use the Configurator to register the message monitoring timer list again.

E7

7-segment MS indicator

Red (flashing) ---

NS indicator Error log (Hex)

021A

Likely Cause

There is an error in the contents of the slave scan list stored in non-volatile memory.

DeviceNet Unit Response

Records the error in the error log.

• The slave remote I/O communications will be stopped.

• Message processing and the exchange of data with the CPU Unit will continue. Normal operation will resume when the slave scan list is written normally. (Start the slave remote I/O communications.)

CIO Area Flags Allocated to DeviceNet Unit

Bits 00 and 03 of n+10 (the Unit Error Flag and Slave Error Flag) and bit 04 of n+14 (Invalid Setup Data Flag) will be ON.

Correction

Disable the slave, reset the allocations, and the enable the slave again or use the Configurator to reset the slave scan list.

E8

7-segment MS indicator

Red (flashing) ---

NS indicator Error log (Hex)

021A

Likely Cause

There is an error in the contents of the master scan list stored in non-volatile memory.

DeviceNet Unit Response

Records the error in the error log.

• The master remote I/O communications will be stopped.

• Message communications and the exchange of data with the CPU Unit as a slave will continue. Normal operation will resume when the master scan list is written normally. (Start the master remote I/O communications.)

Flags Allocated for C200H DeviceNet Master Unit (CIO n+24)

Bit 14 (Error Flag) and bit 03 (the Structure Error Flag) will be ON.

CIO Area Flags Allocated to DeviceNet Unit

Bits 00 and 01 of n+10 (the Unit Error Flag and Master Function Error Flag) and bit 04 of n+12 (the Invalid Scan List Data Flag) will be ON.

217

Troubleshooting with the DeviceNet Unit Indicators

Section 9-1

Correction

Clear the scan list and register the scan list again or use the Configurator to reset the master scan list.

Memory Access Error

E9

7-segment MS indicator

Red (flashing) ---

NS indicator Error log (Hex)

0602

Likely Cause

An error occurred in the Unit’s non-volatile memory itself. This error will occur in the following cases.

1,2,3...

1.

2.

3.

4.

5.

6.

7.

8.

An error occurs reading the identity information during initialization

All 96 error log records cannot be used during initialization or registering an error log record

An error occurs while reading or writing the error log

An error occurs while reading or writing the master function enabling data or the master scan list

An error occurs while reading or writing the slave function enabling data or the slave scan list

An error occurs while reading or writing the message monitoring timer

An error occurs while reading or writing the communications cycle time set value

An error occurs while reading the identity information during Identity object server processing

Note

This error does occur for checksum errors while reading data.

DeviceNet Unit Response

Registers an error record with error code 0602 in the RAM error log area.

For error 1:

Normal operation continues

For error 2 or 3:

Remaining writes to EEPROM are all ignored. Other than that, normal operation continues. (Error records continue to be written to RAM.)

For error 4:

The master remote I/O communications are stopped. Other operations continue.

For error 5:

The slave scanning is stopped and other operations continue.

For error 6:

The default values are used for the message monitoring timer and operation continues.

For error 7:

The communications cycle time is set automatically and operation continues.

For error 8:

Operation continues.

Flags Allocated for C200H DeviceNet Master Unit (CIO n+24)

Bit 14 (Error Flag) and bit 00 (the Incorrect Switch Settings/EEPROM Error

Flag) will be ON.

218

Troubleshooting with the DeviceNet Unit Indicators

Section 9-1

CIO Area Flags Allocated to DeviceNet Unit

Bits 00 and 04 of n+10 (the Unit Error Flag and Unit Memory Error Flag) will be ON.

Correction

Replace the Unit if the error recurs.

CPU Unit Exchange Errors

Unit Number duplication

H1

7-segment MS indicator

Red (flashing) OFF

NS indicator Error log (Hex)

---

Likely Cause

The unit number is duplicated on another Unit.

DeviceNet Unit Response

Stops operation.

Correction

Set the unit numbers correctly and restart the DeviceNet Units.

CPU Unit Faulty (H2)

H2

7-segment MS indicator

Red (flashing) OFF

NS indicator Error log (Hex)

---

DeviceNet Unit Response

Stops operation.

Correction

Replace the CPU Unit if the error recurs when the CPU Unit is restarted.

DeviceNet Unit Faulty

H3

7-segment MS indicator

Red (lit) OFF

NS indicator Error log (Hex)

---

DeviceNet Unit Response

Stops operation.

Correction

Replace the DeviceNet Unit if the same error recurs when the Unit is mounted to another CPU Unit.

Node Address Setting

Error

H4

7-segment MS indicator

Red (flashing) OFF

NS indicator Error log (Hex)

---

Likely Cause

The node address set on the rotary switches is out-of-range (64 or higher.)

DeviceNet Unit Response

Stops operation.

Correction

Set the node address correctly and restart the DeviceNet Units.

Communications Speed

Setting Error

H5

7-segment MS indicator

Red (flashing) OFF

NS indicator

Likely Cause

The communications speed is set incorrectly.

Error log (Hex)

---

219

Troubleshooting with the DeviceNet Unit Indicators

Section 9-1

DeviceNet Unit Response

Stops operation.

Correction

Set the communications speed correctly and restart the DeviceNet Units.

CPU Unit Faulty (H6)

I/O Table Not Registered

Simple Backup Function

Restore Error

CPU Unit Memory Faulty

H6

7-segment MS indicator

Red (flashing) OFF

NS indicator Error log (Hex)

000F

DeviceNet Unit Response

Records the error in the error log. (The time information is set to all zeroes.)

Stops operation.

Correction

Replace the CPU Unit if the error recurs when the CPU Unit is restarted.

Error log (Hex)

0006 H7

7-segment MS indicator

Red (flashing) OFF

NS indicator

Likely Cause

The CPU Unit’s I/O table is not registered.

DeviceNet Unit Response

Records the error in the error log.

Stops operation.

Correction

Create the I/O table.

H8

7-segment MS indicator

Red (flashing) ---

NS indicator Error log (Hex)

---

Likely Cause

Restoring data from the Memory Card failed for the simple backup function.

DeviceNet Unit Response

The data in the Memory Card is not restored, and the settings in the Unit remain as they were before the simple backup operation was performed.

Flags Allocated for C200H DeviceNet Master Unit (CIO n+24)

---

CIO Area Flags Allocated to DeviceNet Unit

---

Correction

The data on the Memory Card may not be correct. Make sure that the backup operation ends normally before performing the restore operation.

HA

7-segment MS indicator

Red (flashing) ---

NS indicator

Likely Cause

A parity error occurred while reading the routing table.

DeviceNet Unit Response

Records the error in the error log and continues processing

The routing table is treated as missing.

Error log (Hex)

0012

220

Troubleshooting with the DeviceNet Unit Indicators

CPU Unit Faulty (Hb)

Routing Table Logic Error

Section 9-1

Flags Allocated for C200H DeviceNet Master Unit (CIO n+24)

Bit 14 (Error Flag) and bit 03 (the Structure Error Flag) will be ON.

CIO Area Flags Allocated to DeviceNet Unit

Bits 00 and 12 of n+10 (the Unit Error Flag and Routing Table Error Flag) will be ON.

Correction

Register the routing table in the CPU Unit again and restart the CPU Unit.

Replace the CPU Unit if the error recurs.

Hb

7-segment MS indicator

Red (flashing) ---

NS indicator Error log (Hex)

0011

Likely Cause

A timeout occurred while reading the routing table.

DeviceNet Unit Response

Continues processing but data exchange with the CPU Unit is stopped.

The routing table is treated as missing.

Records the error in the error log.

Flags Allocated for C200H DeviceNet Master Unit (CIO n+24)

Bit 14 (Error Flag) and bit 03 (the Structure Error Flag) will be ON.

CIO Area Flags Allocated to DeviceNet Unit

Bits 00 and 12 of n+10 (the Unit Error Flag and Routing Table Error Flag) will be ON.

Correction

Register the routing table in the CPU Unit again and restart the CPU Unit.

Replace the CPU Unit if the error recurs.

HC

7-segment MS indicator

Red (flashing) ---

NS indicator Error log (Hex)

021A

Likely Cause

There is an error in the contents of the routing table.

DeviceNet Unit Response

Records the error in the error log.

The routing table is treated as missing and processing continues.

Flags Allocated for C200H DeviceNet Master Unit (CIO n+24)

Bit 14 (Error Flag) and bit 03 (the Structure Error Flag) will be ON.

CIO Area Flags Allocated to DeviceNet Unit

Bits 00 and 12 of n+10 (the Unit Error Flag and Routing Table Error Flag) will be ON.

Correction

Refer to

1-6-3 Creating Routing Tables

. Set the routing table in the CPU Unit

correctly and restart the DeviceNet Units.

I/O Refresh Error

Hd

7-segment MS indicator

Red (flashing) ---

NS indicator Error log (Hex)

0347

221

Troubleshooting with the DeviceNet Unit Indicators

CPU Unit Service

Monitoring Error

Section 9-1

Likely Cause

The I/O areas set in the master scan list or slave scan list do not exist in the

CPU Unit. This error can occur when the Unit is mounted to a different CPU

Unit with a different number of EM banks or EM that has been converted to file memory.

Note

This error may occur during remote I/O communications, too.

DeviceNet Unit Response

Records the error in the error log.

Stops remote I/O communications for the function (master or slave) using the non-existent area.

There is a possibility that this error will occur again. If it does occur again, restart remote I/O communications to return the system to normal operation.

Flags Allocated for C200H DeviceNet Master Unit (CIO n+24)

Bit 14 (Error Flag) and bit 03 (the Structure Error Flag) will be ON.

CIO Area Flags Allocated to DeviceNet Unit

Bit 00 of n+10 (Unit Error Flag) will be ON together with one of the following combinations:

• Bit 05 of n+12 (the Master I/O Refresh Error Flag) and bit 01 of n+10 (the

Master Function Error Flag) ON.

• Bit 05 of n+14 (Remote I/O Refresh Error Flag) and bit 03 of n+10 (the

Slave Error Flag) ON.

Correction

Check the master scan list and slave scan list and reset with a correct allocation.

HE

7-segment MS indicator

Red (flashing) ---

NS indicator Error log (Hex)

0002

Likely Cause

Servicing from the CPU Unit is not at fixed intervals. Servicing is normally monitored at 11 s.

DeviceNet Unit Response

• Records the error in the error log.

• Stops master and slave remote I/O communications.

Performs the following processing if it receives FINS frames that must be passed along to the CPU Unit:

• Returns an error response (0302 Hex) to commands requiring a response.

• Discards other frames and stores an error record (010B Hex) in the error log.

Note

Remote I/O communications will not restart automatically for this error. First confirm that the error has been eliminated and then perform the procedure to start remote I/O communications.

Flags Allocated for C200H DeviceNet Master Unit (CIO n+24)

There is no status notification because communications with the CPU Unit are disabled.

CIO Area Flags Allocated to DeviceNet Unit

There is no status notification because communications with the CPU Unit are disabled.

222

Troubleshooting with the DeviceNet Unit Indicators

Section 9-1

CPU Unit Watchdog Timer

Error

HF

7-segment MS indicator

Red (flashing) ---

NS indicator Error log (Hex)

0001

Likely Cause

An error occurred in the CPU Unit.

Note

The CPU Unit’s watchdog timer error can occur during initialization.

DeviceNet Unit Response

• Records the error in the error log.

• Stops master and slave remote I/O communications.

Performs the following processing if it receives FINS frames that must be passed along to the CPU Unit:

• Returns an error response (0302 Hex) to commands requiring a response.

• Discards other frames and stores an error record (010B Hex) in the error log.

Flags Allocated for C200H DeviceNet Master Unit (CIO n+24)

There is no status notification because communications with the CPU Unit are disabled.

CIO Area Flags Allocated to DeviceNet Unit

There is no status notification because communications with the CPU Unit are disabled.

Correction

Replace the CPU Unit.

CPU Unit Fatal Error

Correction

Inspect the CPU Unit’s operating environment.

---

7-segment

---

MS indicator

---

NS indicator Error log (Hex)

---

DeviceNet Unit Response

Output data is set to 0. (With the master, these are output bits. With the slave, these are input bits to the other master.)

Output OFF Error

---

7-segment

---

MS indicator

---

NS indicator Error log (Hex)

---

Likely Cause

The Output OFF Bit (A50015) was turned ON in the CPU Unit.

DeviceNet Unit Response

Output data is set to 0. (With the master, these are output bits. With the slave, these are input bits to the other master.)

Slave Errors

Remote I/O

Communications Error

L9

7-segment

---

MS indicator NS indicator

Red (flashing)

Error log (Hex)

0345

223

Error Log Functions

Section 9-2

Likely Cause

A timeout occurred during remote I/O communications using the slave function.

DeviceNet Unit Response

Records the error in the error log.

If slave has outputs, the status of those outputs is determined by the hold/ clear outputs setting for communications errors.

CIO Area Flags Allocated to DeviceNet Unit

Bits 00 and 03 of n+10 (the Unit Error Flag and Slave Error Flag) and bits 02 and 03 of n+14 (the Remote I/O Communications Error Flag for OUT1/IN1 and Remote I/O Communications Error Flag for OUT2/IN2) will be ON.

Correction

Check the following:

• Matching master and slave baud rates

• Proper cable lengths (trunk and branch lines)

• Broken or loose cables

• Installation of terminators at both ends of the trunk line

• Excessive noise

Unit Errors

Special Unit Error

7-segment

OFF

MS indicator

Red (lit) OFF

NS indicator Error log (Hex)

0601

DeviceNet Unit Response

Records the error in the error log.

Stops the Unit.

Correction

Restart the CPU Unit. Replace the DeviceNet Unit if the error recurs.

9-2 Error Log Functions

Errors detected by the DeviceNet Unit are stored in the error log along with the date and time of their occurrence. The error log can be read, cleared, and monitored using FINS commands or a Configurator.

9-2-1 Error Log Table

Error Log Table

Error Log Storage Area

Each time an error occurs, one error record is recorded in the DeviceNet

Unit’s RAM error log table. The table can record up to 96 records. If another error occurs when the table is full, the oldest record will be erased to make room for the new error record.

The error log table records the following information.

• Error code

• Detail code

• Time of occurrence (The CPU Unit’s time is used for the time stamp.)

When an error is detected, information on the error and the time stamp are stored in the Unit’s internal RAM as an error log record. Serious errors are recorded in EEPROM as well as RAM. The error log records in EEPROM are retained even when the Unit’s power is turned OFF or the Unit is restarted.

224

Error Log Functions

Section 9-2

Time Information

The error log records in EEPROM are copied to RAM when the DeviceNet

Unit is turned ON.

When the error log is read with a FINS command or from the Configurator, only the error log records in RAM are read. When the error log is cleared with a FINS command or from the Configurator, the error log records in RAM and

EEPROM are erased.

Note

Refer to

9-2-2 Error Codes and Detail Codes

for a table listing the error codes.

Reading and Clearing the

Error Log

The error log table can be read or cleared by sending a FINS command to the

DeviceNet Unit. Use the DeviceNet Unit’s unit address as the FINS command’s destination unit address. (The unit address is the unit number+10

Hex.)

Refer to the

SYSMAC CS/CJ Series Communication Commands Reference

Manual

(W342) for details on using the FINS commands. Refer to the

Appendix E FINS Commands and Responses for DeviceNet Units

for details on

FINS commands addressed to the DeviceNet Unit.

When using the Configurator, the error log can be monitored with the master error history read operation. With the Configurator, the error log can only be monitored and the data cannot be saved.

The CPU Unit’s time information is used for the time stamps in the DeviceNet

Unit’s error log records. If the time information cannot be read from the CPU

Unit, the time stamp will contain all zeroes.

The DeviceNet Unit’s time stamps will not be correct or consistent unless the time has been correctly in the CPU Unit. Moreover, if the battery is replaced in a CS/CJ-series CPU Unit, the time must be set again the next time that power is turned ON.

9-2-2 Error Codes and Detail Codes

Error code

(Hex)

0001

0002

0006

Error

CPU Unit watchdog timer error

CPU Unit service monitoring error (The servicing time from the CPU Unit is not fixed.)

Other CPU error

First byte

00 Hex

Monitoring time (ms)

000F

0011

0012

CPU Unit initialization error

Event timeout

CPU Unit memory error

Detail code

Second byte

00 Hex

Bit 14 ON:

Bit 11 ON:

Other bits:

00 Hex

MRC

Duplicate unit number setting

Unit not in registered I/O table

Reserved for system

01 Hex: Read error

02 Hex: Write error

00 Hex

SRC

03 Hex: Routing table

04 Hex: CPU Bus Unit settings error

05 Hex: Special Unit CIO or DM allocation

Yes

Yes

Yes

Yes

Record stored in

EEPROM

Yes

Yes

225

Error Log Functions

Section 9-2

Error code

(Hex)

0101

0105

0106

0107

0108

0109

010B

010D

010E

Error

First byte

Detail code

Second byte

Transmission failed because the local node is not participating in the network.

Transmission failed because of a node address setting error.

Transmission failed because of a node address duplication error.

FINS message communications command:

Bit 15: OFF

Bits 14 to 8: SNA

Bits 7 to 0: SA1

FINS message communications response:

Bit 15: ON

Bits 14 to 8: DNA

Bits 7 to 0: DA1

Transmission failed because the other node is not participating in the network.

Transmission failed because there is no Unit with the specified unit number.

Transmission failed because the other node is busy.

Transmission failed because of a CPU Unit error. Frame discarded due to one of the following:

• A cyclic service monitoring timeout occurred.

• A CPU Unit watchdog timer error occurred.

• Another CPU Unit error occurred.

Explicit message communications command:

Bit 15: OFF

Bits 14 to 8: 0

Bit 7: ON

Bits 6 to 0: Node address of command source

Explicit message communications response:

Bit 15: ON

Bits 14 to 8: 0

Bit 7: ON

Bits 6 to 0: Node address of command source

Transmission failed because the destination address is not registered in the routing table.

Transmission failed because the routing table has not been registered.

010F

0110

0111

0112

0117

Transmission failed because of a routing table error.

Transmission failed because of too many repetitions.

Transmission failed because the command exceeded the max. command length.

Transmission failed because of a header error.

0118

0120

0123

0124

0125

021A

0211

0300

0340

0341

0342

Packet discarded because the internal reception buffer is full.

Illegal packet discarded.

Unexpected routing error

Packet discarded because the internal transmission buffer is full.

Routing failed because maximum frame length was exceeded.

Packet discarded because of response timeout.

Setting table logic error 00 Hex

Node address duplication (cause)

Packet discarded because of parameter error.

Bus Off detected

Network power supply error

Transmission timeout

03 Hex: Routing table

0A Hex: Master scan list

0B Hex: Slave scan list

0C Hex: Message monitoring timer list

0D Hex: Scan time

Local node address 00 Hex

Same as the code (such as 0101 Hex) in the discarded FINS/explicit message packet.

00 Hex

00 Hex

00 Hex

00 Hex

00 Hex

00 Hex

Record stored in

EEPROM

No

Yes

No

No

No

No

No

226

Error Log Functions

Section 9-2

Error code

(Hex)

0343 Structure error

0344

0345

0346

0347

0348

0601

0602

Verification error

Remote I/O communications error

Remote I/O communications stopped because of a remote I/O communications error.

I/O refreshing error

Message discarded because a new request was received.

Special Unit error

Error

Special Unit memory error

First byte

Detail code

Second byte

01 Hex: I/O area duplication

02 Hex: I/O area range exceeded

03 Hex: Unsupported slave

01 Hex: Non-existent slave

Slave’s node address

Slave’s node address

02 Hex: Illegal header

03 Hex: Illegal device type

04 Hex: Illegal product code

05 Hex: Unsupported connection

06 Hex: I/O size mismatch

07 Hex: Illegal connection path

01 Hex: Master

02 Hex: Slave

Master:

Slave’s node address

Slave:

Master’s node address

01 Hex: Remote I/O communications error

02 Hex: Network power supply error

03 Hex: Transmission timeout

Remote I/O comm. error:

Slave’s node address

Power supply error:

Local (master’s) node address

Transmission timeout:

Local (master’s) node address

00 Hex 01 Hex: Master

02 Hex: Slave

Same as the code (such as 0101 Hex) in the discarded FINS/explicit message packet.

Uncertain contents

01 Hex: Read error

02 Hex: Write error

06 Hex: Error log

09 Hex: Identity data

0A Hex: Master scan list

0B Hex: Slave scan list

0C Hex: Message monitoring timer list

0D Hex: Communications cycle time setting

Record stored in

EEPROM

No

No

No

No

No

No

Yes

Yes

(See note.)

Note

The error information is not written to EEPROM when a memory error occurs in the error log area (EEPROM).

227

Troubleshooting

Section 9-3

9-3 Troubleshooting

9-3-1 CPU Unit’s ERR/ALM Indicator Lit or Flashing

Use the following table to troubleshoot the network when the DeviceNet Unit is mounted and the CPU Unit’s ERR/ALM indicator is lit or flashing.

Error

An I/O verification error occurred.

A CPU Bus Unit setting error occurred.

A CPU Bus error occurred.

An I/O Bus error occurred.

Probable cause

• Make sure that the Unit is connected properly.

• Check the I/O table with the I/O Table Verification operation and correct it if necessary. After correcting it, perform the I/O Table Create operation.

• The CPU Bus Unit model registered in the I/O table does not match the model of CPU Bus Unit actually mounted. Check the I/O table with the I/O

Table Verification operation and correct it if necessary.

• After correcting the I/O table, perform the I/O Table Create operation.

• Make sure that the Unit is connected properly.

• Restart the Unit. Replace the Unit if it doesn’t restart.

• Make sure that the Unit is connected properly.

• Restart the Unit. Replace the Unit if it doesn’t restart.

Note

Refer to the

CS1 Series CPU Unit Operation Manual

(W339) or the

CJ Series

CPU Unit Operation Manual

(W393) for more details on these errors.

9-3-2 Remote I/O Communications Disabled

Use the following table to troubleshoot the network when remote I/O data communications won’t start. (The I/O Data Communications Flag remains

OFF in Master Status 1.)

Error

All of the DeviceNet Unit’s indicators are OFF.

The DeviceNet Unit’s MS indicator is ON and green, but the NS indicator remains OFF.

(The NS indicator normally goes ON about 2 s after the MS indicator.)

Probable cause

• Check whether power is being supplied to the PLC.

• Check whether the DeviceNet Unit is mounted in the Backplane correctly.

• When a watchdog timer (WDT) error has occurred in the PLC, follow the procedures described in the PLC’s manual to correct the problem.

• All of a CS1W-DRM21(-V1) or CJ1W-DRM21 Unit’s indicators will be

OFF when a CPU Bus Unit error has occurred. Check for a CPU Bus

Unit error.

• Restart the Unit. Replace the Unit if it doesn’t restart.

• If the DeviceNet Unit’s 7-segment display is displaying an error code, refer to the tables in

9-1 Troubleshooting with the DeviceNet Unit Indicators

.

• Make sure that the master’s unit number setting is correct.

• Make sure that the unit number is not duplicated on another Special

Unit.

• Check the I/O table with the I/O Table Verification operation and correct it if necessary. After correcting it, perform the I/O Table Create operation.

Restart the Unit. Replace the Unit if it doesn’t restart.

228

Troubleshooting

Section 9-3

Error

The DeviceNet Unit’s MS indicator is ON and green, but the NS indicator continues to flash green.

(The NS indicator normally goes ON 2 s after the MS indicator.)

The DeviceNet Unit’s MS and NS indicators are

ON and green, but the 7-segment display continues to flash the master’s node address.

(The node address normally stops flashing within 8 s after the NS lights.)

Probable cause

• If the DeviceNet Unit’s 7-segment display is displaying an error code, refer to the tables in

9-1 Troubleshooting with the DeviceNet Unit Indicators

.

• Restart the Unit. Replace the Unit if it doesn’t restart.

• Check that the DeviceNet Unit’s baud rate matches the baud rates set on all of the slaves. If they don’t match, set all of the baud rates to the same value.

• Make sure that there are121-

terminators connected at both ends of the trunk line. Connect 121-

terminators if the wrong resistance is being used.

• Check whether all of the slaves’ settings are correct.

• Check whether the communications cables are wired correctly.

• Check whether the power supply cables and power supply are wired and set correctly.

• Check for broken wires in the communications and power supply cables attached to the connectors.

• Check whether the slaves are operating properly.

When an OMRON slave is being used, refer to the

DeviceNet Slaves

Operation Manual

(W347).

• If another company’s slave is being used, refer to that slave’s user’s manual.

9-3-3 I/O Link Problems

Use the following table to troubleshoot I/O Link problems.

Error

The I/O isn’t simultaneous.

At startup, OFF outputs are output from the slaves.

Probable cause

Observe the following precautions when writing application programs:

• The simultaneity of node-units of data is ensured between the PLC and DeviceNet Unit.

• In OMRON slaves, the simultaneity of word-units of data is ensured.

• If another company’s slave is being used, refer to that slave’s user’s manual for details.

When the master is operating in scan list enabled mode and the PLC is set to maintain the status of I/O area bits, those held output points will be output from the output slaves at startup.

Be sure to perform the Create Scan List operation and operate the master with the scan list enabled.

Refer to the

CS1 Series CPU Unit Operation Manual

(W339) or the

CJ

Series CPU Unit Operation Manual

(W393) for details on maintaining

I/O area data with the IOM Hold Bit.

229

Troubleshooting

Section 9-3

9-3-4 Communications Error Operation Settings

Use the following table to correct problems with the DIP switch setting for continuing/stopping communications for errors.

Error

Communications are stopped even though there is no communications error.

Communications are stopped by the DIP switch setting, but don’t resume after toggling the Clear Communications Error Stoppage Bit.

Probable cause

When pin 3 on the DIP switch is ON, communications will be stopped if a communications error, transmission timeout, or network power supply error occurs.

While communications are stopped, the 7-segment displays will alternately display error code A0 and the error code of the communications error that caused the stoppage.

After a network power supply error or transmission timeout is corrected, the indicators will show just the communications stoppage code (A0).

• When communications can’t be restarted with slaves that were communicating normally before the stoppage, stop the communications again.

Check that the slave has started up and perform the “clear communications error stoppage” operation.

• It may be necessary to perform the operation twice if the network contains another company’s slave that take a long time to join the network.

9-3-5 Scan List Problems

Use the following table to troubleshoot scan list problems.

Error

A scan list couldn’t be created by the “create scan list” operation.

A scan list couldn’t be cleared by the “clear scan list” operation.

Probable cause

Neither the create scan list nor clear scan list operations can be performed until the I/O Data Communications flag goes ON. (The I/O Data Communications flag will be OFF for a short time after the power is first turned ON and after the scan list clear operation is executed.)

Make sure that the I/O Data Communications flag is ON before attempting to execute the create scan list or clear scan list operations.

The “create scan list” or “clear scan list” operation was executed, but the master’s 7segment displays still display “- -”.

(The “- -” display usually lasts for 1 s after the “create scan list” operation or 0.1 s after the “clear scan list” operation.)

Restart the DeviceNet Unit, execute the clear scan list operation, and then the create scan list operation if necessary.

Replace the DeviceNet Unit if this doesn’t correct the problem.

230

Maintenance and Replacement

Section 9-4

9-4

9-4-1

Maintenance and Replacement

This section describes the routine cleaning and inspection recommended as regular maintenance as well as the Unit replacement procedure required if a

DeviceNet Unit fails.

Cleaning

Clean the DeviceNet Units regularly as described below in order to keep the network in its optimal operating condition.

• Wipe the Unit daily with a dry, soft cloth.

• When a spot can’t be removed with a dry cloth, dampen the cloth with a neutral cleanser (2% solution), wring out the cloth, and wipe the Unit.

• A smudge may remain on the Unit from gum, vinyl, or tape that was left on for a long time. Remove the smudge when cleaning.

9-4-2

!Caution

Never use volatile solvents such as paint thinner, benzene, or chemical wipes.

These substances could damage the surface of the Unit.

Inspection

Inspection Equipment

Inspection Procedure

Be sure to inspect the system periodically to keep it in its optimal operating condition. In general, inspect the system once every 6 to 12 months, but inspect more frequently if the system is used with high temperature or humidity or under dirty/dusty conditions.

Prepare the following equipment before inspecting the system.

Required Equipment

Have a standard and Phillips-head screwdriver, multimeter, alcohol, and a clean cloth.

Equipment Required Occasionally

Depending on the system conditions, a synchroscope, oscilloscope, thermometer, or hygrometer (to measure humidity) might be needed.

Check the items in the following table and correct any items that are below standard.

Environmental conditions

Installation

Item Standard

Ambient and cabinet temperature 0

°

C to 55

°

C

Ambient and cabinet humidity

(with no condensation or icing)

10% to 90%

Dust/dirt accumulation

Are the Units installed securely?

Are the communications connectors fully inserted?

Are the external wiring screws tight?

None

No looseness

No looseness

No looseness

Are the connecting cables undamaged?

No damage

---

---

---

Equipment

Thermometer

Hygrometer

---

---

231

Maintenance and Replacement

Section 9-4

9-4-3 Replacing Faulty Units

Precautions

Replace a faulty DeviceNet Unit as soon as possible. Refer to the

DeviceNet

Slaves Operation Manual

(W347 or W404) or the

MULTIPLE I/O TERMINALs

Operation Manual

(W348) for details on replacing slaves. We recommend having spare Units available to restore network operation as quickly as possible.

Observe the following precautions when replacing a faulty Unit.

• After replacement make sure that there are no errors with the new Unit.

• When a Unit is being returned for repair, attach a sheet of paper detailing the problem and return the Unit to your OMRON dealer.

• If there is a faulty contact, try wiping the contact with a clean, lint-free cloth dampened with alcohol.

Settings after Replacing

DeviceNet Units

Note

To prevent electric shock when replacing a Unit, be sure to stop communications in the network and turn OFF the power supplies to all of the nodes (master and slaves) before removing the faulty Unit.

When the master is being used, the scan list (network file) must be registered after replacing the DeviceNet Unit.

All of the settings data stored in the DeviceNet Unit can be saved to the CPU

Unit’s Memory Card

1

and later read from the Memory Card

2

. It will be much easier to replace the Unit if you save all of the settings data when the Unit is operating normally.

Note

1,2,3...

1,2,3...

1.

2.

3.

Toggle (OFF to ON) the Unit Setup File Backup Switch (word n+1, bit 15).

Toggle (OFF to ON) the Unit Setup File Restore Switch (word n+1, bit 14).

The backup file is saved to the CPU Unit’s Memory Card with the filename

DNnnBKUP.dvf. (The number “nn” is the unit number in 2-digit hexadecimal.)

Default Remote I/O Allocations

Turn ON power to all slaves and then turn ON the Scan List Enable Switch (bit

00). The scan list will be registered.

User-set Remote I/O Allocations

The scan list can be written to the DeviceNet Unit from the CPU Unit’s Memory Card or a network file saved on a disk.

Using the Settings Data Stored in the CPU Unit’s Memory Card

Use the following procedure to write all of the settings data from the Memory

Card to the DeviceNet Unit.

1.

2.

3.

Turn ON power to the PLC.

Switch the CPU Unit to PROGRAM mode.

Toggle (OFF to ON) the Unit Setup File Restore Bit (word n+1, bit 14).

Using a Network File Stored on a Floppy Disk or Hard Disk

Use the following procedure to write the settings to the DeviceNet Unit from a network file saved on a disk.

1.

2.

Turn ON power to the DeviceNet Unit and the Configurator.

Place the Configurator online and read the network file that was previously saved.

232

Maintenance and Replacement

1,2,3...

Note

Section 9-4

3.

Use the Edit Device Parameters operation, specify the DeviceNet Unit that has been replaced, and write the settings from the network file to the DeviceNet Unit.

Creating a New Network File

Use the following procedure to write the settings to the DeviceNet Unit from a network file saved on a disk.

1.

2.

3.

4.

Turn ON power to the DeviceNet Unit, slaves, and the Configurator.

Place the Configurator online and display the Device List.

Specify the DeviceNet Unit that has been replaced, and use the Edit Device Parameters operation to register slaves and allocate I/O.

Write the settings to the devices.

1.

2.

When using user-set remote I/O allocations, always save the network file to a floppy disk or hard disk to restore operation quickly if the DeviceNet

Unit needs to be replaced.

When the CPU Unit is replaced, be sure that all data in the DM Area, HR

Area, and other memory areas is transferred to the new CPU Unit before starting operation.

233

Maintenance and Replacement

Section 9-4

234

Appendix A

Allocation Differences from C200H

DeviceNet Master Units

The following table shows the CS1W-DRM21(-V1)/CJ1W-DRM21 DeviceNet Unit allocation areas that correspond to the C200HW-DRM21-V1 DeviceNet Master Unit allocation areas.

Note

The following table does not include the allocation areas that exist only in CS/CJ-series DeviceNet Units.

Refer to this table when using ladder programs in the CS1W-DRM21(-V1)/CJ1W-DRM21 that have been used in C200HW-DRM21-V1 DeviceNet Master Units and make adjustments as required.

Use the CX-Programmer replacement operation to change ladder program addresses. When using a CX-Programmer Ver. 1.2 or earlier, use the global replace utility function to globally replace addresses.

Software Switches

Name

Scan List

Enable

Switch

Scan List

Clear

Switch

Remote I/O

Communications

Start Switch

Remote I/O

Communications

Start Switch

Remote I/O

Communications

Stop Switch

C200H DeviceNet Master

Unit

Word address Bit

CS/CJ

Series

IR 2000 +

(10

No.)

×

unit

C200HX/

HG/HE,

C200HS

Unit No. 0 to 9: IR 100

+(10

×

unit

No.)

Unit No. A to F: IR 400

+(10

×

unit

No. – 10)

00

01

02

03

04

CS/CJ-series

DeviceNet Unit

Bit CS/CJseries word address

Unit No.: Set on rotary switches on front panel (0 to 15).

Contents for CS/CJseries DeviceNet Unit

Differences from C200Hseries DeviceNet Master

Unit

CIO 1500 +

(25

×

unit

No.)

00

01

02

03

04

OFF

ON

Registers to scan list the slaves recognized during operation in scan list disabled mode and starts operation in scan list enabled mode (PLC Unit in

PROGRAM mode).

OFF

ON

Disables scan list registration and starts operation in disabled mode (PLC Unit in

PROGRAM mode).

OFF

ON

Restarts remote I/O communications stopped with communications error based on settings.

No differences.

Different usage: Switch returns to OFF when processing completed.

No differences.

Different usage: Unit switch returns to OFF when processing completed.

OFF

ON

Starts communications

OFF

ON

Stops remote I/O communications

Includes bit 03 remote I/O communications start switch functions in CS/CJseries DeviceNet Unit.

Different usage: Unit switch returns to OFF when processing completed.

Includes bit 02 communications error stop clear switch functions in CS/CJ-series

DeviceNet Unit.

Different usage: Unit switch returns to OFF when processing completed.

Different usage: Unit switch returns to OFF when processing completed.

235

Allocation Differences from C200H DeviceNet Master Units

Appendix A

Status Areas

Master Status Area 1

An area with the exact same bit configuration as Master Status area 1 used for C200H DeviceNet Master Units, was set up. This area is called the Master Replacement Status 1.

• The following table compares the C200H DeviceNet Master Unit Master Status Area 1 and the CS/CJseries DeviceNet Unit Master Replacement Status 1.

Names for

C200H

DeviceNet

Master

Unit

Master

Status

Area 1

Switch Setting Error or

EEPROM

Error Flag

IR 2001+

(10

×

unit

No.)

Node

Address

Duplicated/

Bus Off

Flag

Reserved for system use

Configuration Error

Flag

C200H DeviceNet Master Unit

Word address

CS/CJ

Series

C200HX/

HG/ HE,

C200HS

Unit No. 0 to 9: IR

101+(10

× unit No.)

Unit No. A to F: IR

401+(10

× unit No.

– 10)

Bit

00

01

02

03

Names for

CS/CJseries

DeviceNet

Unit Master

Replacement Status 1

Unit Error

Flag

CS/CJ-series

DeviceNet Unit

CS/CJseries word address

CIO 1524+

(25

×

unit

No.)

Bit

00

Node

Address

Duplicated/

Bus Off

Flag

Reserved for system use

Configuration Error

Flag

01

02

03

Details and CS1W-DRM21(-V1)/

CJ1W-DRM21 status

This is the same as a Unit memory error (word n+10, bit 04).

Note

This bit is also used for incorrect switch settings for the C200HW-

DRM21-V1. The Unit will not start if the switch settings are incorrect.

This bit turns ON if any one of the following flags turns ON:

• Node address duplicated (word n+10, bit 06)

• Bus Off (word n+10, bit 05)

Reserved by system

Structure

Error Flag

Send Error

Flag

04

05

Structure

Error Flag

Send Error

Flag

04

05

This bit turns ON if any of the following flags turn ON:

• Routing table error (word n+10, bit

12)

• Invalid message timer list (word n+10, bit 13)

• Invalid Scan List Data (word n+12, bit 04)

• Remote I/O refresh error (word n+12, bit 05)

Note

The C200HW-DRM21-V1 does not support slave communications. Scan list data errors for slave communications are not relevant.

This is the same as the Structure Error

Flag in word n+12, bit 01.

This bit turns ON if any one of the following bits turns ON:

• Network power error (word n+10, bit

07)

• Send timeout (word n+10, bit 08)

236

Allocation Differences from C200H DeviceNet Master Units

Appendix A

Names for

C200H

DeviceNet

Master

Unit

Master

Status

Area 1

C200H DeviceNet Master Unit

Word address

CS/CJ

Series

C200HX/

HG/ HE,

C200HS

Bit

Communications

Error Flag

Verification

Error Flag

I/O Data

Communications Not

Running

Flag

Scan List

Operation

Completed

Flag

Scan List

Operation

Error Flag

Communications

Error Stop

Cleared

Flag

Message

Communications

Enable Flag

IR 2001+

(10

No.)

×

unit

Unit No. 0 to 9: IR

101+(10

× unit No.)

Unit No. A to F: IR

401+(10

× unit No.

– 10)

06

07

08

09

10

11

12

Names for

CS/CJseries

DeviceNet

Unit Master

Replacement Status 1

Communications

Error Flag

Verification error

I/O Data

Communications Not

Running

Flag

CS/CJ-series

DeviceNet Unit

CS/CJseries word address

CIO 1524+

(25

×

unit

No.)

Bit

06

07

08

Reserved for system use

09

Reserved for system use

Reserved for system use

Message

Communications Permitted Flag

10

11

12

Scan List

Disabled

Flag

Error Flag

13

14

Scan List

Disabled

Flag

Error Flag

13

14

Details and CS1W-DRM21(-V1)/

CJ1W-DRM21 status

This is the same as the Remote I/O

Communications Error Flag (word n+12, bit 02).

This is the same as the Verification

Error Flag in word n+12, bit 00.

This operates in the reverse way of the

Remote I/O Communications Flag

(word n+11 bit 01).

---

---

---

The same as the Online Flag in word n+11, bit 00.

Note

When executing message communications instructions

(SEND/RECV/CMND) from the ladder program, use an AND of input conditions for the Network

Communications Enabled Flag in the CPU Unit (A20200 to

A20207) and this bit.

The same as operation as the Scan

List Disabled Flag (word n+11, bit 04).

I/O Data

Communications Flag

15 I/O Data

Communications

Flag

15

This bit turns ON if bit 00, 01 or 03 to

07 in this word (n+24) turns ON.

The same as I/O Data Communications Flag (word n+12 bit 15).

237

Allocation Differences from C200H DeviceNet Master Units

Appendix A

Master Status Area 2

Name C200H DeviceNet Master Unit

Error History

Flag

Word address

CS/CJ Series

D06032+ (2 unit No.)

×

C200HX/HG/

HE, C200HS

DM6032+ (2

× unit No.)

Bit

00

Master I/O

Allocation

Status

15

CS/CJ-series

DeviceNet Unit

Bit CS/CJ-series word address

Contents for CS/CJseries DeviceNet Unit

Differences from C200H

DeviceNet

Master Unit

CIO 1511 +

(25

×

unit No.)

15

CIO 1513 +

(25

×

unit No.)

08 to

15

1: When error history is stored in Master Unit

0: When error history is not stored in Master Unit

1: When scan list has been created using Configurator and operating in scan list enabled mode

(user-set allocations)

0: When operating in scan list disabled mode or when operating in scan list enabled mode based on the scan list registered by software switch settings

(fixed allocations)

No difference.

Shown in 1byte code for

CS1W-

DRM21(-V1)/

CJ1W-

DRM21

Communications Cycle Time Present Value

Name

Communications cycle time present value

C200H DeviceNet Master Unit

Word address

CS/CJ

Series

D06033+ (2

× unit No.)

C200HX/HG/

HE, C200HS

DM6033+ (2 unit No.)

×

Bit

00 to

15

CS/CJ-series

DeviceNet Unit

CS/CJ-series word address

m+16

Bit

00 to

15

Contents for CS/CJseries DeviceNet Unit

C200H

DeviceNet

Master Unit

The present value of the communications cycle time is stored in 4-digit

BCD. The unit is ms. The digits below decimal place are rounded up.

Stored in hexadecimal.

Registered Slave Table

Name

Registered slave table

C200H DeviceNet Master Unit

Word address

CS/CJ Series

4 words starting with 2002 + (10 unit No.)

×

C200HX/HG/HE,

C200HS

Unit No. 0 to 9: 4 words starting with

IR 102 +(10

×

unit

No.)

Unit No. A to F: 4 words starting with

IR 402 +(10

×

unit

No. – 10)

Bit

For CS/CJ-series

DeviceNet Unit

CS/CJ-series word address

00 to

15

4 words starting with n+16

Bit

00 to

15

C200H DeviceNet

Master Unit

No differences.

238

Allocation Differences from C200H DeviceNet Master Units

Appendix A

Normal Slave Table

Name

Normal slave table

C200H DeviceNet Master Unit

Word address

CS/CJ Series C200HX/HG/HE,

C200HS

4 words starting with CIO 2006 +

(10

×

unit No.)

Unit No. 0 to 9: 4 words starting with

IR 106 +(10

×

unit

No.)

Unit No. A to F: 4 words starting with

IR 406 + (10

×

unit

No. – 10)

Bit

00 to

15

For CS/CJ-series

DeviceNet Units

Word address

CS/CJ Series

4 words starting with n+20

Bit

00 to

15

C200H DeviceNet Master Unit

With the C200HW-DRM21-V1, normal slave information is held, and when remote I/O communications are started again, the information is cleared to OFF, even in the following cases:

Network power supply error

Send timeout

Remote I/O communications stopped

When remote I/O communications are stopped due to a communications error, only the bits for the slaves that caused the stoppage will turn OFF. Also, the “corresponding Slave remote I/O communications timeout” in the detailed information for that slave

(m+37 to m+68 bit 11 or bit 03) will turn ON. The communications timeout bits for all other slaves will remain OFF.

For the CS1W-DRM21(-V1) or

CJ1W-DRM21, however, all normal slave information will turn OFF when the remote I/O communications are stopped, including for a communications error.

Replacing Ladder Programs from C200HW-DRM21-V1

If ladder programs have already been created for C200H DeviceNet Master Unit (C200HW-DRM21-V1) mounted to CS/CJ-series CPU Units, the ladder programs must be changed when replacing the C200HW-

DRM21-V1 with this Unit.

Remote I/O Communications and Status Monitor Ladder Programs

• When using a CX-Programmer Ver. 2.0, use its replacement function to globally replace addresses.

• When using a CX-Programmer Ver. 1.2 or earlier, use the global replace utility function to globally replace addresses.

239

Allocation Differences from C200H DeviceNet Master Units

Appendix A

Replace the addresses as shown in the following table.

Area type C200HW-DRM21-V1

First word of IN area in fixed remote I/O allocations

First word of OUT area in fixed remote I/O allocations

Word 50

Software switches

Communications error stop clear

Remote I/O communications start

Remote I/O communications stop

Master status area 1

Master status area 2 Scan list registration by Configurator

Error history

First word of registered slave table

First word of normal slave table

IR 350

IR 2000 +10

×

unit

No.

Bit 02

Bit 03

Bit 04

IR 2000 +10

×

unit

No.+ 1

D06032+2

×

unit

No.+1, bit 15

D06032+2

×

unit

No.+1, bit 00

IR 2000 +10

×

unit

No.+2

IR 2000 +10

×

unit

No.+6

This Unit (CS1W-

DRM21(-V1))

Can be allocated to

CIO 350 from Configurator or in allocated

DM Area words

Can be allocated to

CIO 50 from Configurator or in allocated

DM Area words

CIO 1500 +25

×

unit

No.

Bit 02

Bit 03

Bit 04

CIO 1500 +25

×

unit

No.+ 24

CIO 1500 +25

×

unit

No.+ 13

Note

Allocated as status code.

CIO 1500 +25

×

unit

No.+bit 15 of 11

CIO 1500 +25

×

unit

No.+16

CIO 1500 +25

×

unit

No.+20

Remarks

Completely compatible.

Completely compatible.

Only word address changed.

Only word address changed.

Cannot be accessed from ladder program.

Only word address changed.

Only word address changed.

Message Communications in Ladder Programs

Instructions

Message communications instructions

C200HW-DRM21-V1

IOWR instructions

Instruction execution conditions

Message Communications Enabled Flag

(IR 2000 +10

×

unit No.+

1, bit 12)

This Unit (CS1W-

DRM21(-V1))

CMND instructions

(SEND/RECV also possible for FINS data communications)

Remarks

Change instructions and message data.

AND condition for 1. Message Communications

Permitted Flag (CIO 1500

+25

×

unit No.+24, bit 12) and

2. Network Communications Enabled Flag

(A20200 to A20207: Correspond to ports 0 to 7)

Change execution conditions.

Note

The Message Communications

Permitted Flag (CIO 1500 +25

×

unit

No.+ 24, bit 12) is the same even when online as (CIO 1500 +25

×

unit No.+

11, bit 00)

Note

If there is a routing table in the CS/CJ-series CPU Unit, the DeviceNet Unit must be registered in it when replacing the C200HW-DRM21-V1 with the CS1W-DRM21(-V1) or CJ1W-DRM21. If the DeviceNet Unit is not registered, it will result in a routing table error, and the 7-segment display of the DeviceNet Unit will indicate “HC”.

240

Appendix B

DeviceNet Connections

DeviceNet has several different protocols for remote I/O communications between Master and Slave devices.

Connections are units used to monitor those protocols.

There are four kinds of DeviceNet remote I/O communications protocols (connections): Poll, bit–strobe, COS

(change of state), and cyclic. CS/CJ-series DeviceNet Units support all four types.

The connection used by the DeviceNet Unit is automatically selected if the Configurator is not used.

If the Configurator is used, the connection can be automatically selected by the DeviceNet Unit or the user can specify the connections for each slave. Up to two connections can be set. COS and cyclic connections cannot be specified at the same time. The characteristics of each connection are outlined in the following table.

Connection

Poll

Bit-strobe

COS (Change of

State)

Cyclic

Characteristics

Used for basic I/O.

Used for input of 8 bytes or less. Sends broadcasting requests from master and receives input from slaves.

Communications occur at regular cycles (heartbeat timer) and the connection is determined by the master or slave sending the data.

Data can be sent only when required, which reduces the network communications load.

This connection can be used to send data to the master or slave if the master or slave data changes.

Note

COS and cyclic connections cannot be used at the same time.

COS connections are given priority over poll and bit-strobe connections, which may result in a longer communications cycle time due to the higher frequency of COS connections used to send data or large amounts of data sent using COS. Therefore, COS connections are effective when changes to data are infrequent (approximately 100 ms min.), or to give higher priority to small amounts of data.

For DeviceNet Units, the transmission timing can be decided in the user program.

The following points apply for CS/CJ-series DeviceNet Units:

If the Master COS Send Switch is turned ON, remote I/O communications output data can be sent every time from the master using COS to the slaves that support COS.

If the Slave COS Send Switch is turned ON, remote I/O communications output data can be sent every time from the slave using COS to the master (input data from the perspective of the master).

Even if the software switch is not turned ON, the COS communications using regular cycles (heartbeat timer) can be performed simultaneously.

Note

This CS/CJ-series DeviceNet Unit supports COS.

Communications timing is determined by regular cycles (heartbeat timer).

Masters and slaves send output or input data in regular cycles.

Cyclic connections are have higher priority than poll or bit-strobe connections, which may result in a longer communications cycle time due to large amounts of data sent using cyclic connections. Therefore, cyclic connections are effective when changes to data are infrequent, or the amount of data to be sent is small.

Note

1.

2.

The C200HW-DRM21-V1 and CVM1-DRM21-V1 DeviceNet Master Units use bit-strobe connections with slaves with 8 or less input points and poll connections with other slaves. The DeviceNet Unit automatically chooses the connection.

There can be only one master on each network if COS or cyclic connections are used.

241

DeviceNet Connections

Appendix B

Connections Using Allocations

Allocation method

Without Configurator

Fixed allocation (scan list disabled or enabled)

With Configurator

User-set allocations using allocated DM

Area word settings

User-set allocations using Configurator

Contents

Only 1 connection, automatically selected by the DeviceNet Unit.

(Either a polling or bit-strobe connection is used.)

Only 1 connection, automatically selected by the DeviceNet Unit based on the I/O area set in the Master User Allocations Table.

The user can select the connection to be used for each node address with the Configurator e.g., poll could be used for data and COS could be used for status. Automatic selection or user selection can be specified. Two connections can be used simultaneously for one slave (but

COS and cyclic cannot be used simultaneously.)

Setting Connection Type

The settings for remote I/O communications connections differ depending on the allocation method, as outlined below.

Fixed Allocation or User-set Allocations Using Allocated DM Area Words

The Master CS/CJ-series DeviceNet Unit automatically selects either poll or bit-strobe, whichever makes the communications cycle time shortest.

User-set allocations Using Configurator

The Master CS/CJ-series DeviceNet Unit can make an automatic selection, the same as above, or the user can select up to two connections for a Slave. The setting method is outlined below.

1.

2.

3.

Select the Master Node in the Network Configuration Window in the Configurator.

Select

Device – Parameters – Edit – All Masters

and select the corresponding Slave. Click the

Detailed

Settings

Button.

On the Connection Tab Page shown below, select a check box.

• Automatic selection

• User selection

Select up to two connections from poll, bit–strobe, COS and cyclic. COS and cyclic connections cannot be used at the same time.

242

DeviceNet Connections

Appendix B

Note

1.

Output data using poll connections and output data using COS or cyclic connections are transmitted using the same frame. Therefore set the same output size (bytes) when combining poll and COS or poll and cyclic.

2.

The COS/cyclic heartbeat timer is the smallest transmission interval for COS or cyclic connections.

It can be set for each corresponding slave.

Refer to

DeviceNet Configurator Operation Manual

(W382) for details on Configurator operation.

Connection Path

Connection path are parameters that specify the type of I/O data in the slaves. Depending on the type of slave, the internal I/O data type may be able to be selected. If it can, the connection path and I/O data type in the slave specified for remote I/O communications.

The connection path settings will differ depending on the allocation method, as outlined below.

Fixed Allocation or User-set Allocations Using DM

Connection path settings cannot be made.

User-set Allocations Using Configurator

The Configurator can be used to set the type of I/O data in the slave, using the connection path. The user can use this method to set the I/O data type in the master and the remote I/O communications slave.

The connection path is saved by the Configurator to the CS/CJ-series DeviceNet Unit scan list and when the remote I/O communications are started, the connection path is set to the slave via the DeviceNet network.

Master

Slave

I/O data

Connection

Connection path

Data 1 Data 2

243

DeviceNet Connections

Appendix B

Master COS Send Switch

COS transmission is possible only for User-set allocations using the Configurator.

When required, remote I/O output data can be output from the master to a specified slave.

Output data can be sent at the communications cycle timing to the specified slave by other connections selected automatically or by the user (only when using the Configurator).

In this case, the communications timing is not dependant on the communications cycle time but it is dependant on the CPU Unit cycle time.

Note

When a master or slave sending data with COS communications must handle large quantities of data or when data is sent frequently using COS communications, the communications cycle time may actually be longer than when using poll communications. This can have a large impact on the performance of remote I/O communications and delay responses. Therefore, give ample consideration to the system performance when using COS.

DeviceNet Units use the Master COS Send Switch in the allocated CIO Area words to execute COS transmissions from the master to slaves. The procedure is outlined below.

Step 1

Before executing COS transmission, the connection for the destination slave must be set to COS in the master scan list, using the Configurator.

Step 2

If the bit allocated to each node address from n + 2 words to n + 5 words is turned from OFF to ON, the output data is sent to that node address at a timing independent of the communications cycle time.

COS send switch OFF to ON

I/O refresh Time

CPU Unit user program

COS send instruction

DeviceNet Unit

Communications cycle time

Communications cycle time

Communications cycle time

Communications cycle time

Slave

I/O using normal connection

COS output

Multiple bits can be turned OFF to ON simultaneously and output data can be sent to multiple node addresses simultaneously.

244

DeviceNet Connections

Appendix B

The following diagram shows the transmission timing. After the COS send instruction has been sent to the

DeviceNet (at the I/O refresh timing for the CPU Unit), the COS transmission is executed to each slave immediately after the refresh (remote I/O communications), which each slave is performed during the communications cycle. Therefore, when there are a lot of destination slaves, the COS send timing may be delayed in order of the node addresses.

Multiple COS send switches (node address #1, #2, #3) turned OFF to ON

I/O refresh

Time

CPU Unit user program

COS send instruction

DeviceNet Unit

Node #1 Node #2 Node #3 Node #4 Node #1

COS

#1

Node #2

COS

#2

Node #3

COS

#3

Node #4

Communications cycle time Communications cycle time

Slave # 1

Slave # 2

Slave # 3

: I/O using normal connection

: Output using COS (sent to fit in between normal cycles)

245

DeviceNet Connections

Appendix B

246

Appendix C

FINS Commands and Responses for

DeviceNet Units

List of Command Codes

RESET

Command type Command code

0403

CONTROLLER DATA READ 0501

CONTROLLER STATUS READ 0601

ECHOBACK TEST

ERROR LOG READ

0801

2102

ERROR LOG CLEAR 2103

247

247

248

249

250

251

Reference page

Refer to

SYSMAC CS/CJ Series Communication Commands Reference Manual

(W342) for details on end codes.

RESET (0403)

Resets (restarts) the DeviceNet Unit.

Command Block

Resets the DeviceNet Unit.

Command code

Response Block

There are no responses for this command

End Code

1001

End code (hex) Contents

The command length exceeds maximum command length.

Explanation

• Resets the DeviceNet Unit.

• A communications error has occurred at the Slave but the Slave will restore after the DeviceNet Unit has started up.

• The remote device communicating the message may have timed out but communications can be performed normally after the DeviceNet Unit has started up.

READ CONTROLLER INFORMATION (0501)

Reads the following DeviceNet Unit information.

• Model

• Version

• Node address

247

FINS Commands and Responses for DeviceNet Units

• Baud rate

Command Block

Appendix C

Command code

Response Block

05 01

Command code

End code

20 bytes

Model

20 bytes

Version Node address

Baud rate

End Codes

0000

1001

End code (hex) Contents

Normal end

Command length exceeds maximum command length.

Parameter Details

[Model, Version] (Response)

The DeviceNet Unit model and version are returned as outlined below in 20byte ASCII code. If the data is less than 20 bytes, the remaining bytes will be filled by 20 Hex (space).

• Model:

CS1W-DRM21 @@@@@@@@@@ ( @ : space)

Or:

CJ1W-DRM21

@@@@@@@@@@

(

@

: space)

Version:

V1.00V1.02V1.01

@@@@@ ( @ : space)

• Node Address:

The following DeviceNet Unit node addresses are returned: 00 to 3F hex.

• Baud Rate:

0 hex: 125 kbps

1 hex: 250 kbps

2 hex: 500 kbps

READ CONTROLLER STATUS (0601)

Reads the internal status of the DeviceNet Unit.

Command Block

Command code

248

FINS Commands and Responses for DeviceNet Units

Response Block

Appendix C

Command code

End code Operation status

Unit status 1

Unit status 2

Master function status 1

Master function status 2

Slave function status 1

Slave function status 2

End Codes

End code (hex)

0000

1001

2606

Contents

Normal end

Command length exceeds maximum command length.

Service cannot be executed.

Parameter Details

[Operation status, Units status 1, Unit status 2, Master function status 1, Master function status 2, Slave function status 1, Slave function status 2]

(response)

• Operation Status

Fixed at 01 hex.

• Units status 1, Unit status 2, Master function status 1, Master function status 2, Slave function status 1, Slave function status 2

The same value as the status in the allocated CIO Area words is returned.

ECHOBACK TEST (0801)

Performs an echo back test (communications test between nodes) between specified nodes.

Command Block

538 bytes max.

Command code

Test data

Response Block

Command code

End code

538 bytes max.

Test data

End Codes

Parameter Details

End code (hex)

0000

1001

1002

Contents

Normal end

Command length exceeds maximum command length.

The command length is insufficient for the smallest command.

There is no test data.

[Test Data] (Command, Response)

249

FINS Commands and Responses for DeviceNet Units

Appendix C

For commands, the data to be sent to the specified node is specified, with a maximum of 538 bytes.

For responses, The test data that was sent by the command is returned.

Explanation

An error has occurred if the test data sent by the command and the tests data returned by the response are different.

READ ERROR HISTORY (2102)

Reads the error history saved in the DeviceNet Unit.

Command Block

Command code

Beginning record no.

No. of records

Response Block

Command code

End code Max. no. of stored records

No. of stored records

End Codes

No. of read records

Error log data (for

1 record)

Error log data (for

1 record)

End code (hex)

0000

1001

1002

1103

110C

Contents

Normal end

Command length exceeds maximum command length.

The command length is insufficient for the smallest command.

Outside address range error

The Read start record No. is larger than the number of records currently stored.

Parameter error

No. of read records= 0.

Parameter Details

[Read Start Record No.](Command)

Specifies the record number where the read is to start in 2-byte (4-digit) hexadecimal. The record number is specified from 0000 to 005F hex (0 to 95 decimal), with the first word being 0000 hex.

[Read Record No.](Command, response)

For commands, specifies the number of records to be read. The specification range is 0001 to 0060 hex (1 to 96 decimal).

For responses, the number of records actually read is returned.

[Max. No. of Records] (Response)

The maximum number of errors that can be recorded in DeviceNet Unit error history. Fixed to 0060 hex (96 decimal) for DeviceNet Units.

[No. Stored] (Response)

The number of error history records stored at the point when the command was executed. The range is 0000 to 0060 hex (0 to 96 decimal).

[Error History Data] (Response)

250

FINS Commands and Responses for DeviceNet Units

Appendix C

Returns the error history for the number specified by Read Record No., in order from the Read Start Record No. The total number of Error History Data bytes is 10

×

Read Record No.

One record of error history data is structured in 10 bytes as shown in the following diagram.

1st byte 10th byte

Error code Detailed information

Minute Second Day Time Year Month

• Error Codes, Detailed Information

Shows the contents of the error stored in that record. Refer to

9-2 Error

Log Functions

for details.

• Minutes, Seconds, Day, Time, Year, Month

Shows the date and time that the error stored in that record occurred.

Explanation

• Reads the error history data recorded in the DeviceNet Unit from the specified point for the specified number of records.

• Up to 96 records are recorded in the DeviceNet Unit and the oldest data will be the first to be replaced when the maximum is reached.

Important Points

• If there are fewer error history records than the Read Record No., the records up to the last (latest) record stored at the point of command execution and then the processing/communications will end normally. The actually number of records read will be returned as the Read Record No.

• If more than the current number of records is specified for Read Record

No., the end code 1103 hex will be returned.

• If the Read Record No. is 0000, the processing will end normally even if there are no error records.

• If the Read Start Record No. is specified as 0000, the end code 110C hex is returned.

ERROR HISTORY CLEAR (2103)

Command Block

Command code

Response Block

Command code

End code

251

FINS Commands and Responses for DeviceNet Units

End Codes

0000

End code (hex)

1001

Appendix C

Contents

Normal end

Command length exceeds maximum command length.

Important Point

The Error History Clear command clears the RAM and EEP-ROM error history tables.

252

Appendix D

Multi-vendor Applications

This appendix provides precautions and reference material needed when using DeviceNet (CompoBus/D)

Units as DeviceNet components in a multi-vendor environment.

Connecting another Company’s Slaves to an OMRON Master

If a Slave has an EDS file, it can be installed in OMRON’s Configurator to enable handling it just like an

OMRON Slave. (OMRON’s Configurator already has installed all of the Slave EDS files currently registered with the ODVA.)

In particular, be sure to determine the number of words in the OMRON Master Unit that the Slave requires for input and output.

For Connection Object Interface 2 (Polled I/O Connection), the number of I/O words allocated in the OMRON

Master can be found from the “Produced Connection Size” and “Consumed Connection Size” as shown below.

Up to 100 words can be allocated to inputs and another 100 words to outputs.

Produced Connection Size

This is the amount of memory (usually in bytes) allocated as input.

Consumed Connection Size

This is the amount of memory (usually in bytes) allocated as output.

If the connection size is an even number of bytes, the number of allocated words is: (bytes

÷

2).

If the connection size is an odd number of bytes, the number of allocated words is: [(bytes +1)

÷

2)].

If the connections size is zero (0), no words are allocated.

For Connection Object Interface 3 (Bit Strobed I/O Connection), the number of input words allocated in the

OMRON Master can be found from the “Produced Connection Size” as shown below.

Produced Connection Size

This is the amount of memory (usually in bytes) allocated as input.

If the connection size is an even number of bytes, the number of allocated words is: (bytes

÷

2).

If the connection size is an odd number of bytes, the number of allocated words is: [(bytes +1)

÷

2)].

Connecting an OMRON Slave to another Company’s Configurator

When another company’s configurator (a device that makes environment settings on DeviceNet Masters and

Slaves) is connected, it will be able to read settings from OMRON Masters and Slaves but not change them.

When another company’s configurator is being used, we recommend creating an OMRON Slave EDS file (a file that contains each Slave’s parameters and operating information). Refer to the OMRON Slave device profile as well as the Configurator’s manual for details on creating an EDS file.

253

Multi-vendor Applications

Appendix D

Master Unit Device Profile

General data Compatible DeviceNet Specifications

Physical conformance data

Communications data

Vendor name

Device profile name

Manufacturer catalog number

Manufacturer revision

Network current consumption

Connector type

Physical insulation

Supported indicators

MAC ID setting

Default MAC ID

Baud rate setting

Supported baud rates

Predefined Master/Slave connection set

Dynamic connection support (UCMM)

Explicit message fragmentation support

Volume I - Release 2.0

Volume II - Release 2.0

OMRON Corporation

Communication Adapter

Manual number (W267, W347)

Vendor ID = 47

Profile number = 12

1.1

24 VDC, 30 mA max.

Open plug

Yes

Module, Network

Rotary switch

63

DIP switch

125 kbps, 250 kbps, and 500 kbps

Group 2 client

Group 2 only client

Group 2 server

Yes

Yes

Object Mounting

Identity Object (01 Hex)

Object class Attribute

Service

Not supported

Not supported

Item

Object instance Attribute

Service

ID content

1 Vendor

2 Product type

3 Product code

4 Revision

5 Status (bits supported)

6 Serial number

7 Product name

8 State

DeviceNet Service

05 Reset

0E Get Attribute Single

Yes

Yes

Yes

Yes

Get (read)

Yes

Yes

Yes

Set (write)

No

No

No

No

No

No

No

No

No

Value

47

12

CS1W-DRT21: 02

CJ1W-DRT21: 05

1.1

---

Unique for each Unit

CS1W-DRM21 or CJ1W-

DRM21

---

Parameter option

None

None

Message Router Object (02 Hex)

Object class

Object instance

Attribute

Service

Attribute

Service

Vendor specification addition

Not supported

Not supported

Not supported

Not supported

No

254

Multi-vendor Applications

DeviceNet Object (03 Hex)

Item

Object class Attribute

Service

ID content

1 Revision

DeviceNet service

0EGet Attribute Single

Appendix D

Get (read)

Yes

Set (write)

No

Value

2

Parameter option

No

Object class

Item

Attribute

Service

3 BOI

ID content

1 MAC ID

2 Baud rate

4 Bus–off counter

5 Allocation information

Get (read)

Yes

Yes

Yes

Yes

Yes

6 MAC ID switch changed No

7 Baud rate switch changed

No

8 MAC ID switch value

9 Baud rate switch value

No

No

DeviceNet service

0E Get Attribute Single

4B Allocate Master/Slave Connection Set

4C Release Master/Slave Connection Set

No

No

Set (write)

No

No

No

No

No

No

No

0

0

Value

Parameter option

No

No

No

Connection Object (05 Hex)

Object class Attribute

Service

Max. number of instances

Not supported

Not supported

203

255

Multi-vendor Applications

Appendix D

Object instance 1

Section

Instance type

Production trigger

Transport type

Transport class

Attribute

Information

Explicit Message

Cyclic

Server

3

ID content

Service

Max. No. of instances

1

1 State

2 Instance type

3 Transport class trigger

4 Produced connection ID

5 Consumed connection ID

6 Initial comm. characteristics

7 Produced connection size

8 Consumed connection size

9 Expected packed rate

12 Watchdog time-out action

13 Produced connection path length

14 Produced connection path

15 Consumed connection path length

16 Consumed connection path

17 Production inhibit time

DeviceNet service

05 Reset

0E Get Attribute Single

10 Set Attribute Single

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Get

(read)

Yes

Yes

Yes

Yes

Yes

No

No

No

No

No

Yes

No

No

No

No

No

No

No

No

Set

(write)

Value

---

0

83 hex

---

---

21 hex

553

Format 16-16: 557

Format 8-8: 555

Format 16-8, 8-16: 556

---

1 or 3

0 empty

0 empty

---

Parameter option

No

No

No

256

Multi-vendor Applications

Appendix D

Object instance 2

Section

Instance type

Production trigger

Transport type

Transport class

Attribute

Information

Polled I/O

Cyclic

Server

2

ID content

Service

1 State

2 Instance type

3 Transport class trigger

4 Produced connection ID

5 Consumed connection ID

6 Initial comm. characteristics

7 Produced connection size

8 Consumed connection size

9 Expected packed rate

12 Watchdog time-out action

13 Produced connection path length

14 Produced connection path

15 Consumed connection path length

16 Consumed connection path

17 Production inhibit time

DeviceNet service

05 Reset

0E Get Attribute Single

10 Set Attribute Single

Note

1.

2.

Number of input bytes used by Slave.

Number of output bytes used by Slave.

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Get

(read)

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Max. No. of instances

1

Yes

No

No

No

No

No

No

No

No

No

No

No

Set

(write)

No

No

Yes

Value

---

1

82 hex

---

---

1

See note 1.

See note 2.

---

0

4

20 94 24 01 hex

4

20 94 24 01 hex

---

Parameter option

No

No

No

257

Multi-vendor Applications

Appendix D

Object instance 3

Section

Instance type

Production trigger

Transport type

Transport class

Attribute

Information

Bit Strobed I/O

Cyclic

Server

2

ID content

Service

1 State

2 Instance type

3 Transport class trigger

4 Produced connection ID

5 Consumed connection ID

6 Initial comm. characteristics

7 Produced connection size

8 Consumed connection size

9 Expected packed rate

12 Watchdog time-out action

13 Produced connection path length

14 Produced connection path

15 Consumed connection path length

16 Consumed connection path

17 Production inhibit time

DeviceNet service

05 Reset

0E Get Attribute Single

10 Set Attribute Single

Note

1.

Number of input bytes used by Slave.

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Get

(read)

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Max. No. of instances

1

Yes

No

No

No

No

No

No

No

No

No

No

No

Set

(write)

No

No

Yes

Value

---

1

82 hex

---

---

2

See note 1.

8

---

0

0 empty

4

20 94 24 01 hex

---

Parameter option

No

No

No

258

Multi-vendor Applications

Appendix D

Object instance 4

Section

Instance type

Production trigger

Transport type

Transport class

Attribute

Information

COS/cyclic I/O

Cyclic

Client

0 (no ACK)/2 (with ACK)

ID content

Service

17 Production inhibit time

DeviceNet service

05 Reset

0E Get Attribute Single

10 Set Attribute Single

Note

1.

Number of input bytes used by Slave.

Max. No. of instances

1

1 State

2 Instance type

3 Transport class trigger

4 Produced connection ID

5 Consumed connection ID

6 Initial comm. characteristics

7 Produced connection size

8 Consumed connection size

9 Expected packed rate

12 Watchdog time-out action

13 Produced connection path length

14 Produced connection path

15 Consumed connection path length

Yes

Yes

Yes

Yes

Yes

Yes

Yes

16 Consumed connection path

Get

(read)

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

No

No

Yes

No

No

No

No

No

No

No

Set

(write)

No

No

No

No

Yes

Value

---

1

02 hex (with Cyclic

ACK)

12 hex (with COS

ACK)

00 hex (no Cyclic

ACK)

10 hex (no COS ACK)

---

FFFF hex (no ACK)

01 hex (with ACK)

0F hex (no ACK)

See note 1.

---

---

0

4

20 94 24 01 hex

0 (no ACK)

4 (with ACK) empty (no ACK)

20 2B 24 01 (with

ACK)

---

Parameter option

No

No

No

259

Multi-vendor Applications

Appendix D

Object instance 5 and above

Section

Instance type

Production trigger

Transport type

Transport class

Attribute

Information

Explicit Message/ I/O Message

Cyclic

Server

0/2/3

ID content

Service

1 State

2 Instance type

3 Transport class trigger

4 Produced connection ID

5 Consumed connection ID

6 Initial comm. characteristics

7 Produced connection size

8 Consumed connection size

9 Expected packed rate

12 Watchdog time-out action

13 Produced connection path length

14 Produced connection path

15 Consumed connection path length

16 Consumed connection path

17 Production inhibit time

DeviceNet service

05 Reset

0E Get Attribute Single

10 Set Attribute Single

1.

The following table shows the instance type by communications type.

Communications type

Explicit Message

I/O

0

1

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Get

(read)

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

No

No

No

No

No

No

No

No

No

No

No

Set

(write)

No

No

Yes

Max. No. of instances

199

Value

---

---

---

---

---

See note 1.

See note 2.

---

---

---

---

---

---

---

---

Parameter option

No

No

No

Instance type

2.

The following table shows the transport class trigger by connection type.

Format

Poll client

COS (M) client

COS (M) server

Cyclic (M) client

Cyclic (M) server

Bit-strobe client

Explicit client

Explicit server

Transport class trigger

22 hex

12 hex (with ACK)/10 hex (no ACK)

92 hex (with ACK)/90 hex (no ACK)

02 hex (with ACK)/00 hex (no ACK)

82 hex (with ACK)/80 hex (no ACK)

22 hex

22 hex

83 hex

PLC Object (2F Hex)

Object class Attribute

Service

Not supported

Not supported

260

Multi-vendor Applications

Object instance 1

(CIO area)

Service

Object instance 3

(DM area)

Service

Object instance 4

(WR area)

Service

Object instance 5

(HR area)

Service

Object instance 6

(AR area)

Service

Object instance 7

(TIM/CNT area)

Service

Object instance 8-

20 (EM0 to

EMC area)

Service

DeviceNet service

1CBlock String Read

1DBlock StringN Read

1EBlock String Write

1FBlock StringN Write

1CBlock String Read

1DBlock StringN Read

1EBlock String Write

1FBlock StringN Write

1CBlock String Read

1DBlock StringN Read

1EBlock String Write

1FBlock StringN Write

1CBlock String Read

1DBlock StringN Read

1EBlock String Write

1FBlock StringN Write

1CBlock String Read

1DBlock StringN Read

1EBlock String Write

1FBlock StringN Write

1CBlock String Read

1DBlock StringN Read

1EBlock String Write

1FBlock StringN Write

1CBlock String Read

1DBlock StringN Read

1EBlock String Write

1FBlock StringN Write

Appendix D

Parameter option

Logical Area Address Length

Logical Area Address Length

Logical Area Address

Logical Area Address

Logical Area Address Length

Logical Area Address Length

Logical Area Address

Logical Area Address

Logical Area Address Length

Logical Area Address Length

Logical Area Address

Logical Area Address

Logical Area Address Length

Logical Area Address Length

Logical Area Address

Logical Area Address

Logical Area Address Length

Logical Area Address Length

Logical Area Address

Logical Area Address

Logical Area Address Length

Logical Area Address Length

Logical Area Address

Logical Area Address

Logical Area Address Length

Logical Area Address Length

Logical Area Address

Logical Area Address

261

Multi-vendor Applications

Note

The refresh area types are shown in the following table.

PLC area

CIO

DM

WR

HE

EM (bank 0)

EM (bank 1)

EM (bank 2)

EM (bank 3)

EM (bank 4)

EM (bank 5)

EM (bank 6)

EM (bank 7)

EM (bank 8)

EM (bank 9)

EM (bank 10)

EM (bank 11)

EM (bank 12)

D

E

F

10

9

A

B

C

11

12

13

14

1

5

8

3

4

Refresh area type

Appendix D

Refresh address

CIO 0000 to CIO 6143

D00000 to D32767

W000 to W511

H 000 to H511

E0_00000 to E0_32767

E1_00000 to E1_32767

E2_00000 to E2_32767

E3_00000 to E3_32767

E4_00000 to E4_32767

E5_00000 to E5_32767

E6_00000 to E6_32767

E7_00000 to E7_32767

E8_00000 to E8_32767

E9_00000 to E9_32767

EA_00000 to EA_32767

EB_00000 to EB_32767

EC_00000 to EC_32767

262

Appendix E

DeviceNet Explicit Message Send Command for Other Manufacturer Nodes

Command

Explicit message send 2801

Command code

Explicit Message Send (2801)

Sends a DeviceNet explicit message to a specified object and receives a response.

Command Block

534 bytes max.

Command code

Class ID

Service code

Destination node address

Instance ID

Service data

Response Block

• When a normal response has been returned for the executed explicit message:

534 bytes max.

Command code

End code No. of bytes received

Service data

Service code

Source node address (local node)

• When an error response has been returned for the executed explicit message:

Command code

End code No. of bytes received

Error code

Service code 94 (hex)

Source node address (local node)

• When the explicit message execution failed or timed out:

Command code

End code

263

DeviceNet Explicit Message Send Command for Other Manufacturer Nodes

Appendix E

Parameter Details

[Send Destination Node Address] (Command)

Specifies the node address of the explicit message destination.

The local node DeviceNet Unit is specified for CMND and IOWR instruction control data for Explicit Message Send commands and the actual destination node is specified here.

[Service Code] (Command, response)

For commands, the service code defined by the DeviceNet is specified.

For normal responses, the value for when bit 15 of the service code specified in the command turns ON is returned. For error responses, 94 hex, which indicates an error, is returned.

[Class ID] (Command)

Specifies the class ID for the explicit message destination.

[Instance ID] (Command)

Specifies the instance ID for the explicit message destination.

[Service Data] (Command, response)

For commands, specifies the data defined by the service code.

For responses, returns the reception data defined by the service code.

[No. of Bytes Received] (Response)

Returns the number of bytes received after Source (local node) Node

Address.

[Source (local node) Node Address] (Response)

Returns the local node DeviceNet node address that was the source of the explicit message.

[Error Code] (Response)

Returns the error code defined by the DeviceNet.

Explanation

• The Explicit Message Send command sends a DeviceNet-defined explicit message to an OMRON Special I/O Slave Unit or a Slave manufactured by another company and receives a response.

• Unlike other FINS commands, the Explicit Message Send command specifies the local node DeviceNet Unit as the CMND and IOWR instruction control code destination. The actual destination node is specified using the Destination Node Address in the Explicit Message Send command.

Always specify the local node DeviceNet Unit in the CMND or IOWR instruction control code. If another node Master unit is specified an error will occur.

• If the DeviceNet Master Unit receives an explicit message, it will automatically return a response.

Note

1.

2.

3.

Refer to DeviceNet Specifications for explicit message parameter details.

For information on explicit messages for OMRON slave, refer to

DeviceNet Slave Manual

(W347 or

W404).

Contact the Open DeviceNet Vendor Association, Inc. (ODVA) at 8222 Wiles Road, Suite 287, Coral

Springs, FL 33067 USA (phone: 954-340-5412, fax: 954-340-5413, e-mail: [email protected],

Home page: http://www.odva.org/) to obtain copies of the specification.

264

Index

A

adaptors remote

,

4

,

10

allocations

See also

I/O allocations

applicable Units

,

6

applications precautions

, xviii

C

C200HW-DRM21-V1 changing ladder programs

,

82

comparison

,

33

cables

I/O Unit Connecting Cable

,

18

CIO Area

See also

I/O allocations

cleaning

,

231

commands delivering commands through a network

,

154

explicit message commands

,

171

FINS commands lists

,

147

,

247

communications

,

27

,

194

,

195

connection types

,

131

,

134

,

241

connectors cycle time

,

55

,

84

,

194

,

238

See also

cycle time

errors

,

230

flags

,

155

hardware preparation

,

40

high-speed

,

25

instructions

,

8

,

155

completion codes

,

156

message communications

,

3

,

8

,

19

,

30

,

45

,

137

,

200

data area sizes

,

157

data send/receive instructions

,

152

errors

,

143

,

144

explicit messages

,

141

commands

BYTE DATA READ

,

176

BYTE DATA WRITE

,

178

CPU INFORMATION READ

,

171

CPU UNIT STATUS READ

,

174

CPU UNIT WRITE

,

172

WORD DATA READ

,

177

WORD DATA WRITE

,

179

list of PLC object services

,

169

receiving

,

168

send command for other manufacturer nodes

EXPLICIT MESSAGE SEND (2801)

,

263

sending

,

161

,

162

sending using CMND(490)

,

164

FINS messages

,

139

,

145

command lists

,

147

commands

ECHO BACK TEST (0801)

,

249

ERROR HISTORY CLEAR (2103)

,

251

READ CONTROLLER INFORMATION

(0501)

,

247

READ CONTROLLER STATUS (0601)

,

248

READ ERROR HISTORY (2102)

,

250

RESET (0403)

,

247

connecting networks

,

160

sending/receiving

,

146

,

154

Units supporting

,

147

maximum message response time

,

201

monitoring timer

,

144

overview

,

138

programming examples

,

157

specifications

,

142

structure

,

139

time

,

200

timing for reading responses

,

156

using

,

149

procedures prior to starting

,

42

remote I/O

,

3

,

19

,

27

errors

,

122

,

228

example ladder programming

,

120

restarting

,

120

See also

Master Units

See also

Slave Units

specifications

,

127

starting

,

120

stopping

,

120

scan lists

,

103

software switches

,

9

status

,

9

time/Slave

,

25

,

29

,

195

timing

,

193

Configurator

See also

DeviceNet Configurator

connections

,

25

,

241

connection path

,

243

supported

,

27

,

29

using allocations

,

242

CPU Units errors

,

219

indicators

,

228

I/O memory read/write

,

170

status read/write

,

169

CX-Programmer

,

22

cycle time

,

194

communications

,

25

,

194

reference table

,

90

setup table

,

84

specifications

,

29

,

238

D

DeviceNet Configurator

,

19

,

21

,

31

connecting an OMRON slave to another company’s configurator

,

253

connections

,

242

functions

,

37

,

39

making slave allocations

,

98

,

117

,

134

models

,

37

outline

,

37

saving files to Memory Card

,

188

265

266

specifications

,

38

dimensions

,

59

DM Area

See also

I/O allocations

dot indicators

See also

seven-segment display

E

EC Directives

, xx

EEPROM data

,

29

,

186

errors

,

207

codes

,

225

display

,

52

communications

,

230

error flags

,

74

,

77

,

79

,

82

error log functions error log table

,

224

,

224

master

,

208

memory access

,

216

message communications

,

143

,

144

network

,

214

remote I/O communications

,

122

scan lists

,

230

slave

,

223

software switch

,

213

Unit

,

224

explicit message communications

See also

communications

F

features

,

19

multi-vendor network

,

19

FINS communications command codes

,

247

completion codes

,

156

connecting networks

,

160

See also

communications

fixed allocations

See also

I/O allocations

flags

See also

communications

functions

,

6

,

30

,

31

,

50

DeviceNet Configurator

,

4

,

19

master

,

3

,

6

,

199

Memory Card backup

,

186

slave

,

4

,

7

,

20

,

200

I

I/O allocations

,

96

allocation size setup table

,

87

fixed

,

42

,

43

,

105

,

129

allocated words

,

105

,

129

changing system components

,

109

CIO Area

,

97

connections

,

242

example

,

109

Index

procedure

,

106

,

129

using remote I/O master

,

101

using remote I/O slave

,

127

methods

,

126

user-set

,

20

,

85

,

88

,

111

,

130

connection types

,

131

,

134

connections using

,

242

master user-set allocations reference table

,

90

methods

,

97

,

111

,

130

procedure

,

42

,

44

,

131

setting through allocated DM area words

,

112

,

131

setting through Configurator

,

117

,

134

slave user-set allocations reference table

,

91

using remote I/O master

,

101

,

102

using remote I/O slave

,

128

word allocations

,

26

CIO Area

,

63

,

64

C200 master replacement master status 1 (word n+24)

,

82

disconnect/connect switches (words n+6 to n+9)

,

73

master COS send switches (words n+2 to n+5)

,

72

,

244

master status 1 (word n+12)

,

77

master status 2 (word n+13)

,

78

normal slave table (words n+20 to n+23)

,

82

registered slave table (words n+16 to n+19)

,

81

slave status 1 (word n+14)

,

79

slave status 2 (word n+15)

,

81

software switches 1 (word n)

,

64

software switches 2 (word n+1)

,

69

unit status 1 (word n+10)

,

74

unit status 2 (word n+11)

,

75

DM Area

,

63

,

84

allocation size setup table

,

87

communications cycle time reference table

,

90

communications cycle time setup table

,

84

master user allocations setup table

,

85

master user-set allocations reference table

,

90

slave detailed status

,

92

slave user allocations setup table

,

88

slave user-set allocations reference table

,

91

overview

,

62

I/O Link Units

,

4

C200H I/O Link Unit

,

5

,

12

CQM 1 I/O Link Unit

,

11

errors

,

229

I/O memory read/write for CPU Units

,

170

I/O response times maximum

,

197

minimum

,

198

CS1-series and C200HX/HG/HE/HS PCs

,

198

I/O Terminals

,

4

environment-resistant

,

4

,

12

water-resistant

,

12

I/O Units connecting cable

,

18

See also

Master Units

See also

Slave Units

indicators

display section

,

31

Master Unit

,

206

meaning

,

51

message communications errors

,

143

seven-segment display

,

52

status

MS and NS

,

51

troubleshooting

,

206

,

228

inspection

,

231

installation

,

55

instructions

CMND(490)

,

154

,

155

RECV(098)

,

153

,

155

SEND(090)

,

152

,

155

L

ladder programs replacing

,

239

M

maintenance

,

231

cleaning

,

231

inspection

,

231

Master Units

,

6

,

9

connecting another company’s slave to an OMRON master

,

253

device profile

,

254

errors

,

208

I/O allocations

,

85

See also

I/O allocations

indicators multiple

,

206

,

23

,

199

node address display

,

52

number of

,

100

precautions

,

100

remote I/O communications

,

96

procedures

,

101

specifications

,

28

,

99

status

,

206

status areas

,

236

system startup time

,

199

user-set allocations reference table

,

90

using master function

,

42

memory access errors

,

216

Memory Card

,

24

,

30

,

186

message communications

See also

communications message monitoring timer

,

144

message response time

,

201

mounting

,

56

objects

,

254

MULTIPLE I/O TERMINAL Units

,

5

,

17

multi-vendor environment

,

253

multi-vendor network

See also

features

Index

N

networks connecting for FINS communications

,

160

errors

,

214

installation procedure

,

40

inter-network connections

,

22

multiple masters

,

199

multiple PCs on a single network

,

23

O

objects

,

254

Connection Object

,

255

DeviceNet Object

,

255

Identity Object

,

254

Message Router Object

,

254

PC Object

,

260

See also

PLC object services operation basic operation procedures

,

40

operating environment precautions

,

xvii

operating status

Master Unit

,

206

overview

,

2

P

PLC object services

,

169

precautions

,

xv

applications

,

xviii

general

,

xvi

handling

,

57

Master Units number of

,

100

operating environment

,

xvii

safety

,

xvi

system configuration

,

55

previous models comparison

,

33

replacing ladder programs

,

239

programming examples

,

157

See also

instructions

See also

ladder programs

R

refresh time

,

196

remote I/O communications characteristics

,

194

See also

communications replacement

,

232

replacing ladder programs

,

239

See also

setup routing tables

,

150

local network tables

,

150

relay network tables

,

151

RS-232C Units

,

5

,

12

267

268

S

safety precautions

,

xvi

scan lists

,

103

errors

,

230

setup saving setup files

,

24

,

186

seven-segment display meaning

,

52

Slave Units

,

7

,

9

,

25

communications time

,

195

connecting an OMRON slave to another company’s configurator

,

253

connecting another company’s slave to an OMRON master

,

253

environment-resistant

,

12

errors

,

223

faulty node address display

,

52

general-purpose

,

10

I/O allocations

,

88

See also

I/O allocations

monitoring

,

22

multiple

,

23

programmable

,

12

programming

,

22

remote I/O communications

,

126

procedures

,

127

specifications

,

28

,

29

,

127

See also

adaptors

See also

I/O Link Units

See also

I/O Terminals

See also

MULTIPLE I/O TERMINAL Units

See also

RS-232C Units

See also

terminals

special status

,

12

,

92

system startup time

,

200

user-set allocations reference table

,

91

using slave function

,

43

water-resistant

,

12

specifications default settings

,

29

general

,

26

network length

,

25

other functions remote I/O

,

30

,

31

,

28

,

29

,

99

startup procedures communications

,

42

startup times

,

199

status areas comparison with previous models

,

236

indicators

,

51

Master Unit

,

206

read/write for CPU Units

,

169

switches

,

31

,

50

procedures prior to starting communications

,

42

settings

,

53

errors

,

230

Index

software switches comparison with previous models

,

235

See also

I/O allocations

setting errors

,

213

system configuration

,

3

startup times

,

199

T

tables error log

,

224

local network

,

150

normal slave

,

239

registered slave

,

238

relay network

,

151

routing

,

150

terminals analog input

,

4

analog output

,

4

B7AC Interface Terminal

,

12

remote I/O

,

10

See also

I/O Terminals

sensor

,

4

,

11

temperature input

,

5

timer message monitoring

,

144

timing communications

,

193

reading responses

,

156

troubleshooting

,

205

,

228

U

Units applicable

,

7

usage

,

46

user-set allocations

See also

I/O allocations

V

VME Master Boards

,

3

W

waterproof

,

12

word allocations

See also

I/O allocations

Revision History

A manual revision code appears as a suffix to the catalog number on the front cover of the manual.

Cat. No. W380-E1-07

Revision code

The following table outlines the changes made to the manual during each revision. Page numbers refer to the previous version.

Date Revised content Revision code

1

2

October 2000

July 2001

Original production

Major revisions to add the CJ-series DeviceNet Unit. “CS1” was changed to “CS” or “CS/CJ” as appropriate and the following changes were made. Other changes are as follows:

Page ix:

Manual contents updated and manuals added to table.

Page xiv:

Precaution added on providing double safety mechanisms.

Page xv:

EMC standards updated.

Page xvi:

Impedances, manufacturer, and dimensions changed.

Page 2:

Changed to “DeviceNet Unit” to clarify meaning.

Page 3:

Corrected callout at upper right of page.

Pages 8 and 25:

Number of node for FINS communications changed.

Pages 8, 16, 17, 18, 19:

Notes added.

Pages 10, 11, 15:

Products added.

Page 15:

OS updated in table.

Page 16:

Graphics changed.

Page 17:

Bottom graphic and description changed.

Page 31:

Routing table item added to table.

Page 33:

Maximum words per slave item added to table.

Page 34:

Corrected CIO 3770 number.

Page 36, 37:

Added PCI Board info to graphic and tables.

Page 39:

Note added.

Page 41:

Routing table section added.

Pages 42, 43, 44:

Slight change in procedure.

Page 48:

Graphic added.

Pages 48, 49, 50:

Information added from previous sections 8-2, 8-3, and graphics changed.

Page 51:

Graphics changed.

Page 52:

Note added, graphic added.

Page 55:

CJ-series explanation added.

Page 56:

Graphic added.

Page 60:

Information added to Software Switches 1 description.

Pages 62, 63, 64, 65:

Table items added.

Page 95:

Address numbers changed in graphic.

Page 101:

Note in item 7 corrected (Right changed to Left).

Page 101:

Same note in item 6 corrected (Right changed to Left).

Page 102:

Note 2 added concerning Configurator Ver. 2.10.

Page 105:

Change made to Step 2 of 4-3-2, and Step 3 added.

Page 107:

Table changed.

Page 109:

Allocation tables changed.

Page 114:

Changes made to Changing System Components section.

Page 118:

Note added concerning Configurator Ver. 2.10.

Page 119:

Changes made to 4-5-1.

Page 119:

Changes made to 4-5-2.

Page 120:

Note added.

Page 127:

Note 2 added concerning Configurator Ver. 2.10.

Page 133:

Note 2 added concerning Configurator Ver. 2.10.

Page 140:

Explanation of node address 0 added to table.

Page 142:

Revision made to note in section 6-1-6.

Pages 146, 147, 148, 149:

Sections 6-3 to 6-3-2 newly added.

Pages 157, 158:

Section 6-4 moved from previous location in section 6-6.

Page 160:

Note content changed.

Page 174:

Reference to manual changed in Note.

Pages 181, 182, 183, 184, 185:

Sections 7-1 to 7-1-4 newly added.

Pages 185, 186, 187:

Sections 7-2 to 7-2-2 moved from Appendix.

Page 193:

PC cycle time delay calculation in two Notes changed from 0.25 ms + 1.5 ms to 0.7 ms.

Page 194:

Table item changed from (TPC-TRF) to (TPC+TRF).

Page 197:

PC cycle time delay calculation changed from 0.25 ms + 1.5 ms to 0.7 ms.

Page 200:

Information from previous sections 8-2, 8-3 moved to pages 48, 49, 50.

Page 222:

Reference to Slaves Operation Manual changed.

Page 225:

Reference to Slaves Operation Manual changed.

Page 225:

DNnnBKUP.DAT changed to DNnnBKUP.dvf in Note 3.

Page 232:

Note added.

269

Revision code

03

04

05

06

07

Date Revised content

January 2003

September 2003

July 2005

February 2007

March 2008

“PLC” was changed to “PC,” where appropriate, throughout the manual.

Page v:

Changes made to text under “OMRON Product References.”

Page xvi:

Text removed from table.

Page 4:

Line added after “Analog Input Terminals.” Minor change made to text under “Analog Output

Terminals.”

Page 10:

Heading added.

Page 12:

Tables added.

Page 31:

Minor change made to text in sixth box from top of rightmost column.

Page 106:

Changes made to diagram in several places.

Page 143:

Four commands removed from bottom table.

Page 144:

One command added and one command removed from table.

Page 159:

Unit name corrected in one place in first diagram.

Pages 168, 169, 170, 171, 172, 174, 175, 176, 177, 178, 179:

Block formats changed.

Pages 168, 172, 174, 176, 177, 178:

Notes added.

Pages 168, 170, 172, 175, 176, 177, 178, 179:

Information on destination node address removed.

Pages 168, 172, 177, 178, 179:

Information on the number of bytes received removed.

Pages 168, 170, 172, 175, 176, 177, 179:

Minor numerical changes made to Class ID.

Pages 168, 170, 172:

Minor numerical changes made to Instance ID.

Page 171:

Text under block format removed.

Pages 175, 176, 178, 179:

Minor change made to information on Instance ID.

Page 252:

Manufacturer revision changed in first table. Product code and revision number changed in third table.

“(-V1)” was added to the CS1W-DRM21 model number throughout the manual.

Page ix:

Note added.

Page x:

Information corrected in table.

Pages 21, 28, 184, and 210:

Information on simple backup function added.

Page 29:

Information on CS1W-DRM2-V1 added and model number corrected.

Page 31:

Information in fourth row from the bottom in rightmost column corrected.

Page 38:

Manual name corrected and catalog number added.

Page 46:

“For this Unit” added in two places.

Page 126:

Total allocation size corrected for Configurator setting.

Page 187:

Information added and term changed.

Page 222:

Manual reference added.

Page 231:

Information added to table.

Page 232:

Graphic changed.

Page 234:

Note changed.

Pages 243 to 245:

Appendix deleted.

Page v:

Information on general precautions notation added.

Page x:

Information on liability and warranty added.

Pages ix and x:

Updated manual information.

Page xx:

Added “(-V1)” to model numbers in table and changed “EN50081-2” to “EN6100-6-4” (two locations).

Page 13:

Updated list of models, added “equipped with detection functions” to remarks for Environment-resistive Slaves, and changed remarks for Analog Terminals.

Page 38:

Updated CX-Programmer model number and added catalog number for manual.

Page 48:

Added “Unit” to callouts.

Page 89:

Corrected word numbers.

Page 105:

Corrected information for node addresses 6 to 11.

Page 116:

Corrected bit number of Remote I/O Communications Start Switch.

Page 160:

Removed “or IOWR instruction.”

Page 188:

Added CJ-series CPU Units toward top of table.

Pages 194, 128, and 260:

Added “W404.”

Page 203:

Added error “H8.”

Page 222:

Added “0D Hex” for the setting table logic error.

Page 260:

Removed “CompoBus/D.”

Page 9:

Added bulleted item at bottom of page.

Page 11:

Deleted five rows from table.

Page 15:

Added eight rows to table.

Page 19:

Removed ISA Board and added PCI Board. Added “XP” to OS specifications. Changed model number for PCMCIA Card.

Pages 37 and 38:

Corrected Board/Card information in tables.

Page 39:

Corrected model numbers under “monitoring functions.”

Pages 39, 143, 218, 224, and 251:

Corrected number of records to “96.”

Page 109:

Changed model number in last row of table.

Page 118:

Changed model number in top figure.

Page 250:

Changed ranges for the first four parameters.

Page 253:

Changed the number of words that can be allocated to “100.”

270

Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement

Table of contents