Omron NT-DRT21 Operation Manual

NT-DRT21
DeviceNet (CompoBus/D)

Interface Unit

Operation Manual

Produced August 2000

!

!

!

v

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 dam­age to property.

DANGER Indicates an imminently hazardous situation which, if not avoided, will result in death or

serious injury.

WARNING Indicates a potentially hazardous situation which, if not avoided, could result in death or

serious injury.

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 “PC” means Programmable Controller and is not used as an abbreviation for any­thing else.

The abbreviation “PT” refers to OMRON NT-series and NTH-series Programmable Terminals. The
DeviceNet (CompoBus/D) Interface Unit is used with NT31, NT31C, NT631, and NT631C PTs.

“CS1 Series” refers to CS1H and CS1G PCs and related products.
“C Series” refers to C200H, C1000H(F), C2000H, C200HS, CPM1, and CQM1 PCs and related prod-

ucts.

“CVM1/CV Series” refers to CV500, CV1000, CV2000, and CVM1 PCs and related products.
“CPU Unit” refers to OMRON CS1-series, C200HX/HG/HE(-Z), C-series, and CVM1/CV-series CPU

Units.
“Support Tool” refers to the following NT-series Support Tools for Windows (Ver. 3.2 or later):

• Ver. 3.2: NT-ZJ3AT1-EV3/NT-ZJCAT1-EV3

• Ver. 4.1: NT-ZJCAT1-EV4

Only the above Support Tools can be used to create screen data for PTs to which the DeviceNet
(CompoBus/D) Interface Unit is mounted.

The term “host” refers to the control device (e.g., PC or computer) that controls the PT.

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.

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

vi

 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 permis­sion 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 informa­tion contained in this publication.

TABLE OF CONTENTS

vii

PRECAUTIONS xi. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

2 General Precautions xii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3 Safety Precautions xii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4 Operating Environment Precautions xiii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5 Application Precautions xiii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6 Conformance to EC Directives xvii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 1

Introduction 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-1 Features of the DeviceNet Interface Unit 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-2 DeviceNet Functions 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-3 System Configuration 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-4 Outline of Configurator 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-5 Functions of the DeviceNet (CompoBus/D) Interface Unit 10. . . . . . . . . . . . . . . . . . . . . . .

SECTION 2

Operating Procedures 15. . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-1 Operating Procedures Flowchart 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-2 Simple System Configuration 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 3

Network Design 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-1 Network Configuration 22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-2 Limitations on the Network Configuration 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-3 Sharing the Communications Power Supply 27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-4 Grounding the Network 37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-5 Noise Precautions 38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-6 Correcting Faulty Operation Caused by Noise 40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-7 Sharing the Same Power Supply 40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 4

Installation and Network Connection 43. . . . . . . . . . . . . . .

4-1 Components and Their Functions 44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-2 Mounting the Unit on the PT 45. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-3 Connecting to the DeviceNet Network 45. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 5

PT Settings and Operations 51. . . . . . . . . . . . . . . . . . . . . . .

5-1 Installing the System Program 52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-2 Structure of the System Menu 56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-3 Initializing DeviceNet (CompoBus/D) Memory Switches 57. . . . . . . . . . . . . . . . . . . . . . . .

5-4 Serial Port A Settings 59. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-5 DeviceNet (CompoBus/D) Memory Switch Settings 61. . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-6 Checking the PT Settings 64. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-7 Checking Communications with the PT 66. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-8 Checking the System Program Version 67. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 6

Remote I/O Communications 69. . . . . . . . . . . . . . . . . . . . . .

6-1 Overview of Remote I/O Communications 70. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-2 Settings with the NT-series Support Tool 72. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-3 Allocating PT Memory to the Host (Master) 74. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-4 Allocating PT Data to PT Memory 81. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TABLE OF CONTENTS

viii

SECTION 7

Message Communications 83. . . . . . . . . . . . . . . . . . . . . . . . .

7-1 Overview of Message Communications 84. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7-2 Using Message Communications 85. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7-3 Explicit Messages 99. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7-4 Sample Program 103. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 8

Error Processing 107. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8-1 Error Screens Specific to the DeviceNet Interface Unit 108. . . . . . . . . . . . . . . . . . . . . . . . . .

8-2 Troubleshooting with the LED Indicators 109. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Appendices

A Device Protocol 111. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B Comparison of System Program Functions 117. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C Standard Models 119. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Index 123. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Revision History 125. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ix

About this Manual:

This manual describes the installation and operation of the NT-DRT21 DeviceNet (CompoBus/D) Inter­face Unit and includes the sections described below. The DeviceNet Interface Unit can be used with the
NT31, NT31C, NT631, and NT631C Programmable Terminals (PTs).

Please read this manual carefully and be sure you understand the information provided before attempting
to install and operate a DeviceNet Interface Unit.

Section 1 describes the main features and basic functions of the DeviceNet (CompoBus/D) system and
the DeviceNet (CompoBus/D) Interface Unit.

Section 2 shows a simple system configuration example and basic procedures up to using the PT con­nected to the DeviceNet Interface Unit.

Section 3 provides information required when designing a network, such as precautions regarding the
configuration of the DeviceNet network to which the CompoBus/D Interface Unit connects.

Section 4 explains how to mount the DeviceNet Interface Unit on the PT and connect the Unit to the Devi­ceNet network.

Section 5 explains the PT settings and operations required to use the DeviceNet Interface Unit.
Section 6 shows how to use remote I/O communications with the DeviceNet Interface Unit and how to use

the PT when using remote I/O communications.
Section 7 explains how to use message communications with a DeviceNet Interface Unit and how to use

the PT when message communications are being used.
Section 8 explains how to troubleshoot errors that may occur when using the DeviceNet Interface Unit.

Refer to the CompoBus/D (DeviceNet) User’s Manual and the PT’s User’s Manual for more details.
The Appendices provide relevant DeviceNet protocol specifications, comparisons between different

system program versions, and a list of related products.

Copyrights and Trademarks

DeviceNet is a registered trademark of the Open DeviceNet Vendor Association.
The copyright to the software installed in the DeviceNet (CompoBus/D) Master Unit belongs to Woodhead

Industries Inc.
Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the

United States and/or other countries.
Other product names and company names that appear in this manual are trademarks or registered trade-

marks of their respective companies.

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.

!

x

Related Manuals

The following manuals are related to DeviceNet or PT applications. Refer to them as required. Catalog
suffixes showing the version and production site have been omitted. Be sure you have the correct version
for your region.

Application Contents Manual name Catalog

number

Connecting or
programming for a
PT connected to
DeviceNet

Connecting a PT with a DeviceNet Interface Unit to a
DeviceNet network.

Communications between the PT and DeviceNet
network.

Installing the system program for the DeviceNet
Interface Unit into the PT.

PT system menus for using the DeviceNet Interface
Unit.

DeviceNet (CompoBus/D)
Interface Unit Operation
Manual

(This manual)

V066

Operating a PT Descriptions of PT function and operation.

Refer to the Setup Manual for your PT for settings,
peripheral device connections, and other hardware
information. Refer to the Reference Manual for PT

NT31/NT31C
Setup Manual

V062

information. Refer to the Reference Manual for PT
functions, details on screen elements, and host
communications.

A PT with a DeviceNet Interface Unit has
functionality equivalent to a PT with a model number

NT631/NT631C
Setup Manual

V063

ending in “V1” (system program version 2.1). These
three manuals describe the functions of PTs with
model numbers ending in “V2.” Refer to Appendix B
Comparison of System Program Functions for details
on differences before using any functions.

NT31/NT631
Reference Manual

V064

Creating or
transferring screen
data or installing
system programs

Descriptions of methods for creating and transferring
screens.

(The Support Tool is used to create and transfer
screens for the PT to which the DeviceNet Interface
Unit is mounted. You must use version 3.2 or later of
the Support Tool.)

NT-series Support Tool for
Windows
Operation Manual

V061

Constructing a
DeviceNet network

Information on OMRON DeviceNet products and
network configuration.

DeviceNet (CompoBus/D)
Operation Manual

W267

Refer to the DeviceNet (CompoBus/D) Operation
Manual for overall network details and using the

DeviceNet (CompoBus/D)
Slave Operation Manual

W347

Manual for overall network details and using the
DeviceNet Master Unit and refer to the DeviceNet
(CompoBus/D) Configurator Operation Manual for
detailed control and setting methods.

DeviceNet (CompoBus/D)
MULTIPLE I/O TERMINAL
Operation Manual

W348

DeviceNet (CompoBus/D)
Configurator Operation
Manual

W328

xi

PRECAUTIONS

This section provides general precautions for using the CS1-series Programmable Controllers (PCs) and related devices.

The information contained in this section is important for the safe and reliable application of Programmable Control­lers. You must read this section and understand the information contained before attempting to set up or operate a PC
system.

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

2 General Precautions xii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3 Safety Precautions xii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4 Operating Environment Precautions xiii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5 Application Precautions xiii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6 Conformance to EC Directives xvii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

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

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

6-4 Relay Output Noise Reduction Methods xvii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

!

!

!

!

3Safety Precautions

xii

1 Intended Audience

This manual is intended for the following personnel, who must also have knowl­edge 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 ma­chines, 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 using the DeviceNet (CompoBus/D) I/F
Unit. Be sure to read this manual before attempting to use the Unit and keep this
manual close at hand for reference during operation.

WARNING It is extremely important that a PC and all PC 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 PC System to the above-mentioned
applications.

3 Safety Precautions

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 PC on a net­work.

WARNING Do not attempt to take any Unit apart while the power is being supplied. Doing so

may result in electric shock.

WARNING Do not touch any of the terminals or terminal blocks while the power is being

supplied. Doing so may result in electric shock.

!

!

!

!

!

!

!

!

5Application Precautions

xiii

WARNING Do not attempt to disassemble, repair, or modify any Units. Any attempt to do so

may result in malfunction, fire, or electric shock.

WARNING Do not touch the Power Supply Unit while power is being supplied or

immediately after power has been turned OFF. Doing so may result in electric
shock.

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.

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.

Caution Tighten the screws on the terminal block of the AC Power Supply Unit to the

torque specified in the operation manual. The loose screws may result in burning
or malfunction.

4 Operating Environment Precautions

Caution Do not operate the control system in the following locations:

• Locations subject to direct sunlight.

• Locations subject to temperatures or humidity outside the range specified in

the specifications.

• Locations subject to condensation as the result of severe changes in tempera­ture.

• Locations subject to corrosive or flammable gases.

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

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

• Locations subject to shock or vibration.

Caution Take appropriate and sufficient countermeasures when installing systems in the

following locations:

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

• Locations subject to strong electromagnetic fields.

• Locations subject to possible exposure to radioactivity.

• Locations close to power supplies.

Caution The operating environment of the PC System can have a large effect on the lon-

gevity and reliability of the system. Improper operating environments can lead to
malfunction, failure, and other unforeseeable problems with the PC System. Be
sure that the operating environment is within the specified conditions at installa­tion and remains within the specified conditions during the life of the system.

5 Application Precautions

Observe the following precautions when using the PC System.

• You must use the CX-Programmer (programming software that runs on Win­dows) if you need to program more than one task. A Programming Console
can be used to program only one cyclic task plus interrupt tasks. A Program­ming Console can, however, be used to edit multitask programs originally
created with the CX-Programmer.

!

!

5Application Precautions

xiv

• There are restrictions in the areas and addresses that can be accessed in I/O
memory of the CS1-series CPU Units when using the C200H Special I/O Units
in combination with the following functions.

• There are restrictions in data transfer with the CPU Unit when program­ming transfers inside an ASCII Unit using the PC READ, PC WRITE, and
similar commands.

• There are restrictions in data transfer with the CPU Unit for allocated bits
and DM area specifications (areas and addresses for source and destina­tion specifications).

• The DeviceNet (CompoBus/D) output area for a DeviceNet Master Unit
(CIO 0050 to CIO 0099) overlaps with the I/O bit area (CIO 0000 to CIO

0319). Do not use automatic allocations for I/O in any system where al­locations to the DeviceNet system will overlap with allocations to I/O Units.
Instead, use a Programming Device or the CX-Programmer to manually
allocate I/O for the DeviceNet devices, being sure that the same words
and bits are not allocated more than once, and transfer the resulting I/O
table to the CPU Unit. If DeviceNet communications are attempted when
the same bits are allocated to both DeviceNet devices and I/O Units (which
can occur even if automatic allocation is used), the DeviceNet devices and
I/O Units may both exhibit faulty operation.

• Special bits and flags for PC Link Units (CIO 0247 to CIO 0250) overlap
with the I/O bit area (CIO 0000 to CIO 0319). Do not use automatic alloca­tions for I/O in any system where allocations to the I/O Units will overlap
with allocations to I/O Units. Instead, use a Programming Device or the
CX-Programmer to manually allocate I/O to I/O Units, being sure that the
the special bits and flags for PC Link Units are not used, and transfer the
resulting I/O table to the CPU Unit. If operation is attempted when the spe­cial bits and flags for PC Link Units are also allocated to I/O Units (which
can occur even if automatic allocation is used), the PC Link Units and I/O
Units may both exhibit faulty operation.

WARNING Always heed these precautions. Failure to abide by the following precautions

could lead to serious or possibly fatal injury.

• Always connect to a ground of 100 Ω or less when installing the Units. Not con­necting to a ground of 100 Ω or less may result in electric shock.

• A ground of 100 Ω or less must be installed when shorting the GR and LG ter­minals on the Power Supply Unit.

• Always turn OFF the power supply to the PC before attempting any of the fol­lowing. Not turning OFF the power supply may result in malfunction or electric
shock.

• Mounting or dismounting I/O Units, CPU Units, Inner Boards, or any other
Units.

• Assembling the Units.

• Setting DIP switches or rotary switches.

• Connecting cables or wiring the system.

• Connecting or disconnecting the connectors.

Caution Failure to abide by the following precautions could lead to faulty operation of the

PC or the system, or could damage the PC or PC Units. Always heed these pre­cautions.

• When using a CPU Unit for the first time, install the CS1W-BAT1 Battery pro­vided with the Unit and clear all memory areas from a Programming Device
before starting to program.

5Application Precautions

xv

• When using the internal clock, turn ON power after installing the battery and
set the clock from a Programming Device or using the DATE(735) instruction.
The clock will not start until the time has been set.

• When creating an AUTOEXEC.IOM file from a Programming Device (a Pro­gramming Console or the CX-Programmer) to automatically transfer data at
startup, set the first write address to D20000 and be sure that the size of data
written does not exceed the size of the DM Area. When the data file is read
from the Memory Card at startup, data will be written in the CPU Unit starting at
D20000 even if another address was set when the AUTOEXEC.IOM file was
created. Also, if the DM Area is exceeded (which is possible when the CX-Pro­grammer is used), the remaining data will be written to the EM Area.

• Always turn ON power to the PC before turning ON power to the control sys­tem. If the PC power supply is turned ON after the control power supply, tempo­rary errors may result in control system signals because the output terminals
on DC Output Units and other Units will momentarily turn ON when power is
turned ON to the PC.

• Fail-safe measures must be taken by the customer to ensure safety in the
event that outputs from Output Units remain ON as a result of internal circuit
failures, which can occur in relays, transistors, and other elements.

• Fail-safe measures must be taken by the customer to ensure safety in the
event of incorrect, missing, or abnormal signals caused by broken signal lines,
momentary power interruptions, or other causes.

• Interlock circuits, limit circuits, and similar safety measures in external circuits
(i.e., not in the Programmable Controller) must be provided by the customer.

• Do not turn OFF the power supply to the PC when data is being transferred. In
particular, d o not turn OFF the power supply when reading or writing a Memory
Card. Also, do not remove the Memory Card when the BUSY indicator is lit. To
remove a Memory Card, first press the memory card power supply switch and
then wait for the BUSY indicator to go out before removing the Memory Card.

• If the I/O Hold Bit is turned ON, the outputs from the PC will not be turned OFF
and will maintain their previous status when the PC is switched from RUN or
MONITOR mode to PROGRAM mode. Make sure that the external loads will
not produce dangerous conditions when this occurs. (When operation stops
for a fatal error, including those produced with the FALS(007) instruction, all
outputs from Output Unit will be turned OFF and only the internal output status
will be maintained.)

• When supplying power at 200 to 240 VAC, always remove the metal jumper
from the voltage selector terminals. The product will be destroyed if 200 to
240 VAC is supplied while the metal jumper is attached.

• Always use the power supply voltages specified in the operation manuals. An
incorrect voltage may result in malfunction or burning.

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

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

• Do not apply voltages to the Input Units in excess of the rated input voltage.
Excess voltages may result in burning.

• Do not apply voltages or connect loads to the Output Units in excess of the
maximum switching capacity. Excess voltage or loads may result in burning.

• Disconnect the functional ground terminal when performing withstand voltage
tests. Not disconnecting the functional ground terminal may result in burning.

5Application Precautions

xvi

• Install the Units properly as specified in the operation manuals. Improper
installation of the Units may result in malfunction.

• Be sure that all the mounting screws, terminal 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 re­sult in malfunction if foreign matter enters the Unit.

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

• Use crimp terminals for wiring. Do not connect bare stranded wires directly to
terminals. Connection of bare stranded wires may result in burning.

• Wire all connections correctly.

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

ply. Incorrect wiring may result in burning.

• Mount Units only after checking terminal blocks and connectors completely.

• Be sure that the terminal blocks, Memory Units, expansion cables, and other

items with locking devices are properly locked into place. Improper locking
may result in malfunction.

• Check switch settings, the contents of the DM Area, and other preparations
before starting operation. Starting operation without the proper settings or data
may result in an unexpected operation.

• 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 PC.

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

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

• Resume operation only after transferring to the new CPU Unit the contents of

the DM Area, HR Area, and other data required for resuming operation. Not
doing so may result in an unexpected operation.

• Do not pull on the cables or bend the cables beyond their natural limit. Doing
either of these may break the cables.

• Do not place objects on top of the cables or other wiring lines. Doing so may
break the cables.

• When replacing parts, be sure to confirm that the rating of a new part is correct.
Not doing so may result in malfunction or burning.

• Before touching a Unit, be sure to first touch a grounded metallic object in order
to discharge any static build-up. Not doing so may result in malfunction or dam­age.

• When transporting or storing circuit boards, cover them in antistatic material to
protect them from static electricity and maintain the proper storage tempera­ture.

• Do not touch circuit boards or the components mounted to them with your bare
hands. There are sharp leads and other parts on the boards that may cause
injury if handled improperly.

• Do not short the battery terminals or charge, disassemble, heat, or incinerate
the battery. Do not subject the battery to strong shocks. Doing any of these
may result in leakage, rupture, heat generation, or ignition of the battery. Dis­pose of any battery that has been dropped on the floor or otherwise subjected
to excessive shock. Batteries that have been subjected to shock may leak if
they are used.

6Conformance to EC Directives

xvii

• UL standards required that batteries be replaced only by experienced techni­cians. Do not allow unqualified persons to replace batteries.

6 Conformance to EC Directives

6-1 Applicable Directives

• EMC Directives

• Low Voltage Directive

6-2 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 ma­chines. The actual products have been checked for conformity to EMC stan­dards (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 Direc­tives will vary depending on the configuration, wiring, and other conditions of the
equipment or control panel in which the OMRON devices are installed. The cus­tomer must, therefore, perform final checks to confirm that devices and the over­all machine conform to EMC standards.

Note Applicable EMC (Electromagnetic Compatibility) standards are as follows:

EMS (Electromagnetic Susceptibility): EN61131-2
EMI (Electromagnetic Interference): EN50081-2

(Radiated emission: 10-m regulations)

Low Voltage Directive

Always ensure that devices operating at voltages of 50 to 1,000 VAC or 75 to
1,500 VDC meet the required safety standards for the PC (EN61131-2).

6-3 Conformance to EC Directives

The CS1-series PCs comply with EC Directives. To ensure that the machine or
device in which a CS1-series PC is used complies with EC directives, the PC
must be installed as follows:

1, 2, 3... 1. The PC must be installed within a control panel.

2. Reinforced insulation or double insulation must be used for the DC power
supplies used for the communications and I/O power supplies.

3. PCs complying with EC Directives also conform to the Common Emission
Standard (EN50081-2). When a PC is built into a machine, however, noise
can be generated by switching devices using relay outputs and cause the
overall machine to fail to meet the Standards. If this occurs, surge killers
must be connected or other measures taken external to the PC.

The following methods represent typical methods for reducing noise, and
may not be sufficient in all cases. Required countermeasures will vary
depending on the devices connected to the control panel, wiring, the config­uration of the system, and other conditions.

6-4 Relay Output Noise Reduction Methods

The CS1-series PCs conforms to the Common Emission Standards
(EN50081-2) of the EMC Directives. However, noise generated by relay output
switching may not satisfy these Standards. In such a case, a noise filter must be
connected to the load side or other appropriate countermeasures must be pro­vided external to the PC.

6Conformance to EC Directives

xviii

Countermeasures taken to satisfy the standards vary depending on the devices
on the load side, wiring, configuration of machines, etc. Following are examples
of countermeasures for reducing the generated noise.

Countermeasures

Refer to EN50081-2 for more details.
Countermeasures are not required if the frequency of load switching for the

whole system including the PC is less than 5 times per minute.
Countermeasures are required if the frequency of load switching for the whole

system including the PC is more than 5 times per minute.

Countermeasure Examples

When switching an inductive load, connect a surge protector , diodes, etc., in par­allel with the load or contact as shown below.

Circuit Current Characteristic Required element

AC DC

CR method

Power
supply

Inductive

load

Yes Yes If the load is a relay or solenoid, there

is a time lag between the moment the
circuit is opened and the moment the
load is reset.

If the supply voltage is 24 or 48 V,
insert the surge protector in parallel
with the load. If the supply voltage is
100 to 200 V, insert the surge
protector between the contacts.

The capacitance of the capacitor must
be 1 to 0.5 µF per contact current of
1 A and resistance of the resistor must
be 0.5 to 1 Ω per contact voltage of
1 V. These values, however, vary with
the load and the characteristics of the
relay. Decide these values from
testing, and take into consideration
that the capacitance suppresses spark
discharge when the contacts are
separated and the resistance limits
the current that flows into the load
when the circuit is closed again.

The dielectric strength of the capacitor
must be 200 to 300 V. If the circuit is
an AC circuit, use a capacitor with no
polarity.

Diode method

Power
supply

Inductive

load

No Yes The diode connected in parallel with

the load changes energy accumulated
by the coil into a current, which then
flows into the coil so that the current
will be converted into Joule heat by
the resistance of the inductive load.

This time lag, between the moment
the circuit is opened and the moment
the load is reset, caused by this
method is longer than that caused by
the CR method.

The reversed dielectric strength value
of the diode must be at least 10 times
as large as the circuit voltage value.
The forward current of the diode must
be the same as or larger than the load
current.

The reversed dielectric strength value
of the diode may be two to three times
larger than the supply voltage if the
surge protector is applied to electronic
circuits with low circuit voltages.

V aristor method

Power
supply

Inductive

load

Yes Yes The varistor method prevents the

imposition of high voltage between the
contacts by using the constant voltage
characteristic of the varistor. There is
time lag between the moment the
circuit is opened and the moment the
load is reset.

If the supply voltage is 24 or 48 V,
insert the varistor in parallel with the
load. If the supply voltage is 100 to
200 V, insert the varistor between the
contacts.

---

6Conformance to EC Directives

xix

When switching a load with a high inrush current such as an incandescent lamp,
suppress the inrush current as shown below.

OUT

COM

R

OUT

COM

R

Countermeasure 1

Providing a dark current of approx.
one-third of the rated value through
an incandescent lamp

Countermeasure 2

Providing a limiting resistor

1

SECTION 1

Introduction

This section describes the main features and basic functions of the DeviceNet (CompoBus/D) system and the DeviceNet
(CompoBus/D) Interface Unit.

1-1 Features of the DeviceNet Interface Unit 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-2 DeviceNet Functions 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-2-1 DeviceNet Features 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-2-2 Communications Functions of Master Units 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-2-3 DeviceNet (CompoBus/D) Communications Specifications 6. . . . . . . . . . . . . . . . .

1-3 System Configuration 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-3-1 Master Units 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-3-2 Example System Configuration 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-4 Outline of Configurator 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-5 Functions of the DeviceNet (CompoBus/D) Interface Unit 10. . . . . . . . . . . . . . . . . . . . . . . . .

1-5-1 Communications Using the DeviceNet Interface Unit 10. . . . . . . . . . . . . . . . . . . . .

1-5-2 Contrast with the Regular Memory Link Method 11. . . . . . . . . . . . . . . . . . . . . . . . .

1-1SectionFeatures of the DeviceNet Interface Unit

2

1-1 Features of the DeviceNet Interface Unit

The DeviceNet Interface Unit is an interface that connects PTs (Programmable
Terminals) to a DeviceNet network. The DeviceNet Interface Unit can connect
NT31, NT31C, NT631, and NT631C PTs.

DeviceNet is a industry-standard network, so the DeviceNet Interface Unit is
compatible with devices from different vendors. An OMRON PT can be con­trolled from another company’s Master when it is connected to the DeviceNet
network.

The DeviceNet Interface Unit allows a PT to be connected easily to an existing
DeviceNet network. Separate PT wiring is not required and wiring work is re­duced. The DeviceNet network has a maximum communications distance of
500 m, so a PT in a remote location can be controlled from the Master.

The DeviceNet Interface Unit supports both remote I/O communications and ex­plicit message communications.

• Remote I/O Communications
Remote I/O communications can exchange data (32 input words and 32 out­put words max.) with the PT at high speed and without programming, just like
regular I/O.

• Explicit Message Communications
More complicated control operations can be performed by sending explicit
messages from the Master when required.

A PT connected through the DeviceNet Interface Unit can execute simulated di­rect access with Memory Link. The PT can be controlled from the DeviceNet
Master that acts as the host by reading and writing PT memory within the PT.

Master

Data transfer and control
through remote I/O com­munications and explicit
message communica­tions

Communications
power supply

T-branch Tap

Slave

(C200H I/O Link Unit)

Slave

Slave

T-branch Tap
with termination

T-branch Tap
with termination

Slave

PT connected to Device­Net Interface Unit

Network length 500 m max.

Compatible with Other
Companies’ Masters

Easily Connect to an
Existing DeviceNet
Network

Supports Remote I/O and
Explicit Message
Communications

Memory Link Control

1-2SectionDeviceNet Functions

3

1-2 DeviceNet Functions

1-2-1 DeviceNet Features

This section explains the features of the DeviceNet network.
The DeviceNet conforms to the DeviceNet open field network specification,

which means that devices (Masters and Slaves) produced by other manufactur­ers can be connected to the Network. A wide range of field-level applications can
thus be supported by combining valve devices, sensors, and other devices.

Remote I/O communications that constantly exchange I/O data between the
Master and Slaves can be executed simultaneously with message communica­tions that send/receive Master Unit data as required by the application. A Devi­ceNet network can thus be installed to flexibly handle applications that require
both bit data and message data.

A Configurator (sold separately) can be used to enable connection of more than
one Master to the Network, allowing message communications between Mas­ters and remote I/O communications between multiple groups of Masters and
Slaves. This allows the DeviceNet network to be used as a common bus to unify
controls while reducing wiring.

A Configurator (sold separately) can be used to enable mounting more than one
Master Unit to a single PC, allowing control of many more points. This feature
can easily handle line expansions and other applications.

A Configurator (sold separately) can be used to enable flexible allocation of I/O,
i.e., in any area and in any order. This allows I/O allocations that suit the applica­tion to simplify programming and enable effective usage of PC memory areas.

A Configurator (sold separately) can be used to set the communications cycle
time, enabling usage of Slaves with slow response times.

Use a multi-drop trunk line, T-branch multi-drop lines, or daisy-chain drop lines.
All three connection methods can be combined to flexibly construct a network
that meets the needs of the application.

Multi-drop trunk line

T-branch multi-drop line

Trunk line

Drop line

Daisy-chain
drop line

Multi-vendor Network

Simultaneous Remote I/O
and Message Services

Connect Multiple Masters
to the Same Network

Multi-layer Networks
Allow Multi-point Control
and Line Expansion

Free Remote I/O
Allocation

Handle Slaves with
Different Response
Speeds

Easily Expand or Change
Lines with Various
Connection Methods

1-2SectionDeviceNet Functions

4

1-2-2 Communications Functions of Master Units

Remote I/O Communications

Master Unit

Output area Input area

Allocated in I/O memory
(e.g., IR/CIO Area)

Automatically input/output

Slave Slave

A

B

Note Input and output areas are automatically allocated in fixed areas unless a Confi-

gurator is used. A Configurator can be used to freely allocate input blocks 1 and
2, and output blocks 1 and 2, anywhere in I/O memory.

Item Master Unit model Without Configurator With Configurator

Max. number of Slave

CVM1, CV Series 63 nodes

nodes per Master

CS1 Series,
C200HZ/HX/HG/HE

50 nodes 63 nodes

C200HS 32 nodes 63 nodes

Max. number of control

CVM1, CV Series 2,048 pts (64 input/64 output words) 6,400 pts (100 words x 4 blocks)

points per Master

CS1 Series,
C200HZ/HX/HG/HE

1,600 pts (50 input/50 output words) Without messages: 4,800 pts

With messages: 1,600 pts

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

Max. number of I/O

CVM1, CV Series

32 input/32 output words
points per Slave
controllable by Master

CS1 Series,
C200HZ/HX/HG/HE

C200HS

Remote I/O allocation

CVM1, CV Series

Fixed words in IR Area (or CIO area Any area
areas

CS1 Series,
C200HZ/HX/HG/HE

for CS1-series PCs)

C200HS

Reference Setting the number of words used by the DeviceNet Interface Unit changes the

maximum number of Units that can be connected in a single DeviceNet Network.

1-2SectionDeviceNet Functions

5

Message Communications

Master Unit Master Unit

PT (DeviceNet
Interface Unit)

IOWR

Communications Instructions

Master Unit model Send Receive FINS

commands

CVM1, CV Series SEND(192) RECV(193) CMND(194)
CS1 Series,

C200HZ/HX/HG/HE

None None IOWR

C200HS ---

Item Master Unit model Capacity

Max. number of nodes per Master

CVM1, CV Series 8 nodes
Unit for message communications
using FINS commands

CS1 Series,

C200HZ/HX/HG/HE

8 nodes

C200HS Not supported
Max. number of nodes per Master

CVM1, CV Series 63 nodes
Unit for message communications
using explicit messages

CS1 Series,

C200HZ/HX/HG/HE

63 nodes

C200HS Not supported
Max. message length

CVM1, CV Series SEND(192): 152 bytes

RECV(193): 156 bytes
CMND(194): 160 bytes (starting with command code)

CS1 Series,

C200HZ/HX/HG/HE

IOWR: 160 bytes (starting with command code)

Reference 1. When sending explicit messages from an OMRON Master Unit, use the EX-

PLICIT MESSAGE SEND (28 01) FINS command.

2. The SEND and RECV instructions are used for communications between
OMRON Master Units; they are not used with the DeviceNet Interface Unit.

3. Explicit messages cannot be sent when a C200HS is used as the Master.

1-2SectionDeviceNet Functions

6

1-2-3 DeviceNet (CompoBus/D) Communications Specifications

Item Specification

Communications protocol DeviceNet
Supported connections

(communications)

Master-Slave: Remote I/O and explicit messages
Peer-to-peer: FINS commands (see note 1)
Both conform to DeviceNet specifications

Connection forms (see note 2) Combination of multi-drop and T-branch

connections (for trunk or drop lines)
Baud rate 500 kbps, 250 kbps, or 125 kbps (switchable)
Communications media Special 5-wire cables (2 signal lines, 2 power

lines, 1 shield line)
Communications

distances

500 kbps Network length: 100 m max. (see note 3)

Drop line length: 6 m max.

Total drop line length: 39 m max.

250 kbps Network length: 250 m max. (see note 3)

Drop line length: 6 m max.

Total drop line length: 78 m max.

125 kbps Network length: 500 m max. (see note 3)

Drop line length: 6 m max.

Total drop line length: 156 m max.
Communications power supply 24 VDC supplied externally
Max. number of nodes 64 nodes (including Configurator when used)
Max. number of Masters Without Configurator:1

With Configurator: 63
Max. number of Slaves 63 Slaves
Communications cycle time

(see note 4)

Without Configurator: Calculated from conditions

Ex: Input Slaves (16-pt): 16

Output Slaves (16-pt) :16
Cycle time at 500 kbps: 9.7 ms

With Configurator: Set between 2 and 500 ms

Calculated value takes priority if longer.

Max. communications cycle
time with multiple Masters
(see note 5)

Calculated from conditions.

Ex: Input Slaves (16-pt): 16

Output Slaves (16-pt) :16
Max. cycle time at 500 kbps: 18 ms

Error control checks CRC error check

Note 1. FINS communications are not supported by the DeviceNet Interface Unit.

2. Terminating resistors are required at both ends of trunk line.

3. Indicates the length when thick cables are used. Reduce the network length
to 100 m max. when using thin cables. When using both thick and thin cables
together, refer to Combining Thick and Thin Cables in 3-2-2 Maximum Net-
work Length.

4. Indicates the maximum time for remote I/O communications from a Master
to a specific Slave until remote I/O communications are conducted again for
the same Slave.

5. The communications cycle time when more than one Master is present on a
single network.

Refer to t h e DeviceNet (CompoBus/D) Operation Manual (W267) for other com-
munications specifications, such as communications cycle times.

1-3SectionSystem Configuration

7

1-3 System Configuration

A CompoBus/D (DeviceNet) system can be constructed in two ways: fixed al­location or free allocation.

A DeviceNet system can be constructed easily even without the Configurator.
With fixed allocation, predetermined words are allocated to each node for the
Slave’s I/O.

An OMRON Master Unit must be used in order to perform fixed allocation. More­over, with fixed allocation only one Master Unit can be used in a DeviceNet net­work and only one Master Unit may be mounted to a PC.

The Configurator can be used to freely allocate the words used by each Slave.
With free allocation, more than one Master Unit can be connected in a Device-

Net network and each Master’s Slave I/O can be set independently. More than
one Master Unit may be mounted to each PC and those Masters can be used
independently. Furthermore, other companies’ Masters can be used.

Reference 1. The maximum number of words occupied by the DeviceNet Interface Unit is

32 input words and 32 output words. The number of input words and output
words can be set independently from 0 to 32 words. Do not allocate words
that are allocated to another Slave.

2. The maximum number of points controlled by each Master is lower with
fixed allocation than it is with free allocation. When the DeviceNet Interface
Unit is allocated a large number of words, do not exceed the maximum num­ber of points that can be controlled by the Master. In particular , if a C200HS
is used as the Master with fixed allocation, the DeviceNet Interface Unit will
use all of the available points (32 input words and 32 output words) and it
won’t be possible to connect another Slave.

3. Each Master Unit and Configurator is connected as a single node in the De­viceNet network and requires a unique node number.

1-3-1 Master Units

The following OMRON Master Units are available.

Applicable PC Master Unit model Mounting position

Max. number of Units

number

With

Configurator

Without

Configurator

CVM1, CV Series CVM1-DRM21-V1 CPU or Expansion CPU Rack

(Classified as CPU Bus Units)

16

1

CS1 Series

C200HW-DRM21-V1 CPU Rack or Expansion I/O Rack

16

C200HZ/HX/HG/HE

(Classified as Special I/O Units)

10 or 16
(see note)

C200HS 10

Note Some CPUs can control 16 Master Units and other CPUs can control 10.

Fixed Allocation

Free Allocation

1-3SectionSystem Configuration

8

1-3-2 Example System Configuration

System Configuration without a Configurator (Fixed Allocation)

Master Unit

CPU Unit

Remote I/O communications

Slave Slave

CVM1/CV-series PCs: 64 nodes max.
CS1-series, C200HZ/HX/HG/HE PCs: 51 nodes max.
C200HS PCs: 33 nodes max.

PT

System Configuration with a Configurator (Free Allocation)

Master Unit

CPU Unit

Remote I/O communications

Slave

Slave

Master Unit Master Unit

Message
communications

Configurator

ISA Board

64 nodes max.

64 nodes max.

PT

PT

1-4SectionOutline of Configurator

9

1-4 Outline of Configurator

The Configurator is required to use any of the following functions.

• User-set remote I/O allocations

• More than one Master Unit per PC (i.e., per CPU Unit)

• More than one Master Unit per network

• Setting communications parameters

The Configurator is run on an IBM PC/AT or compatible computer connected to
the network as a DeviceNet node. Connection is made either through an ISA
Board or PCMCIA Card, as shown in the following diagrams. (The Configurator
can be removed from the network after settings have been completed.)

ISA Board in IBM PC/AT or Compatible

Configurator software

ISA Board

3G8F5-DRM21

PCMCIA Card in IBM PC/AT or Compatible

Configurator software

PCMCIA Card

3G8E2-DRM21

Network Interface Unit

Configurators

Model number Components Connector to network Applicable computer OS

3G8F5-DRM21 Dedicated ISA Board

and Configurator
Installation Disk

Dedicated ISA Board

IBM PC/AT or
compatible

Windows 95 or
Windows NT 3.51/4.0

3G8E2-DRM21 Dedicated PCMCIA

Card and Configurator
Installation Disk

Dedicated PCMCIA
Card

(See “Minimum System
Requirements” below.)

Windows 95

Minimum System Requirements

The minimum system requirements for an IBM PC/AT or compatible computer
are as follows:

CPU: i486/DX2 66 MHz min. (for Windows 95)

Pentium 90 MHz min. (for Windows NT)

Memory: 12 MB min., 16 MB recommended (for Windows 95)

16 MB min., 24 MB recommended (for Windows NT)

Hard disk: 5 MB of free space min.

1-5SectionFunctions of the DeviceNet (CompoBus/D) Interface Unit

10

The main functions of the Configurator are illustrated below. For details, refer to
the DeviceNet (CompoBus/D) Configurator Operation Manual (W328).

Configurator
functions

Setup functions

Setting remote I/O allocations (scan list)
Setting other Master parameters (initial remote

I/O status, communications cycle time)
Setting Slave parameters for Slaves not from

OMRON

Monitoring functions

Displaying connected device lists
Monitoring Master status, Master error histories,

and communications cycle times

Operating functions

Starting/stopping remote I/O communications

File management functions

Reading/writing files for connected device data
(online) and device data resulting from setting
Master parameters (offline)

Note 1. Connect only one Configurator to each Network.

2. Do not use a Configurator in locations subjected to excessive noise, particu­larly when using a PCMCIA Card. Excessive noise will cause the computer
to run out of control. (This will not, however, adversely af fect the DeviceNet
network.)

3. The OMRON Configurator can only be used for OMRON Master Units
(CVM1-DRM21-V1, C200HW-DRM21-V1). Do not use the Configurator for
other company’s Master Units.

1-5 Functions of the DeviceNet (CompoBus/D) Interface Unit

A PT connected to the DeviceNet Interface Unit uses the Memory Link method.
In the Memory Link method, the PT memory area within the PT is treated as a
virtual PC memory area. This method allows PT memory and PT display ele­ments to be accessed with simulated direct access.

1-5-1 Communications Using the DeviceNet Interface Unit

With the regular Memory Link method, the PT and host are connected through
RS-232C or RS-422A communications and the host controls the PT through the
PT memory by sending commands to the PT that read/write PT memory data.

When a DeviceNet Interface Unit is used, the PT is connected to the host (Mas­ter) through the DeviceNet network. In contrast to the regular Memory Link
method, PT memory is accessed using one of the following two methods.

The DeviceNet Interface Unit is connected to the network as a DeviceNet Slave.
As a DeviceNet Slave, the input and output areas can each contain up to 32
words.

In the DeviceNet system, the input area is regularly read by the Master and the
output area is regularly written from the Master. This process maintains consis­tency between the Slave’s input and output areas and the input and output areas
allocated to the Master.

Once the PT memory’s input and output areas have been set, PT memory can
be read and written without having the host (Master) manage communications.

The maximum size of the input and output areas is only 32 words each, but data
is transferred automatically at high speed so it is useful to allocate areas that re­quire regular data transfers with the host such as the PT status control area and
PT status notify area or areas that are frequently refreshed such as the numeral
memory tables.

Parts of PT memory other than the input and output areas can be read/written by
sending explicit messages from the host.

Main Configurator
Functions

Accessing PT Memory
through Input and Output
Areas

Accessing PT Memory
with Explicit Message
Communications

1-5SectionFunctions of the DeviceNet (CompoBus/D) Interface Unit

11

Transferring data with explicit message communications takes more time than
transferring data with the input and output areas, but all of PT memory can be
accessed.

If explicit message communications are used as the main method to transfer
data, the DeviceNet Interface Unit’s input and output areas can be reduced to
their minimum required sizes and more input and output area capacity will be
available for other Slaves.

Note Observe the following precautions in order to minimize the communications time

required for explicit message communications.

• Limit the amount of data transmitted in each message communications event.

• Consider setting the ladder program in the host that controls the DeviceNet In-

terface Unit so that it transfers just the data in the displayed screen. (In this
case, it will be necessary to write a ladder program section for each screen.)

PT

Remote I/O

communications

Master Unit

CPU Unit

PT status

control area

PT status

notify area

Touch switch

Numeral
memory
table

Direct access

PT memory

Input
area

Output
area

DeviceNet Network

Explicit message com­munications (Transfers
data in any area.)

Lamp

1-5-2 Contrast with the Regular Memory Link Method

The following operations are different with the DeviceNet Interface Unit and with
regular Memory Link method.

• The transmission direction of the input area is always PT → Host and that of
the output area is always Host → PT, so two-way functions cannot be used
when using the input and output areas.

• Except for remote I/O communications, no locally-initiated communications
functions are supported by the DeviceNet Interface Unit. With explicit mes­sage communications, communications are always executed by commands
sent from the host and corresponding responses from the PT.

• Since the DeviceNet Interface Unit does not support locally-initiated commu­nications functions other than remote I/O communications, it is necessary to
set the strobe ON interval to match system requirements and always read the
status of the strobe at the Master. (Set the interval in the system menu.)

The following table lists the operational differences between the regular Memory
Link and the DeviceNet Interface Unit’s Memory Link that arise due to differ-

1-5SectionFunctions of the DeviceNet (CompoBus/D) Interface Unit

12

ences described above and differences in the hardware used for communica­tions.

Item With Regular Memory Link With DeviceNet Interface Unit

Communications
with host (method
used to read/write
PT memory)

Data transfer by Memory Link commands via
RS-232C or RS-422A communications

• Data transfer through the DeviceNet input and
output areas (The contents of corresponding
words in the host are updated automatically.)

• Data transfer by explicit message communica­tions

Refer to 1-5-1 Communications Using the
DeviceNet Interface Unit for more details.

Functions possible
between the PT and
host

The following functions can be executed with
the Memory Link command:

• Read/write PT memory, numeral memory
tables, character string tables, or bit memory
tables.

• Clear numeral memory tables, character string
tables, or bit memory tables.

• Notify the host of a touch switch, numeral, or
character input.

• Notify the host of a change in the direct area or
PT memory.

• Change the PT’s operating mode.

• Send a resend request to the PT.

• Return an error response to an illegal command

from the host.

The following functions can be executed by
sending explicit messages:

• Read/write PT memory.
(Data is automatically transferred through the
input and output areas. Data can be transferred
to or from any area with explicit message com­munications.)

Structure of the PT
status notify area

PT status notify bits

00 0

Bit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

Word m

Word m+1

Word

Numeral/character string memory table number

(4-digit BCD or hexadecimal)

Bit

Screen number (4 BCD digits)

Numeral/character string memory table number

(4-digit BCD or hexadecimal)

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

Word m

Word m+1

Word m+2

Word

00 0PT status notify bits

PT status notify
area’s “Displayed
screen number”

None
(The current screen number can be found in
the PT status control area’s “screen number”.)

Notify the host of the displayed screen number.

Strobe of the PT
status notify area’s
“PT status notify bit”

The strobe goes ON for a fixed time when the
displayed screen is changed or the contents of
the numeral or character string memory table
are changed. (At the same time, the host is
notified by the Memory Link command.)

The strobe goes ON for time set in the system
menu. (There is no notification to the host. The
strobe’s ON time must be longer than the
interval between data reads from the host.)

Window control
area

Normally, this area is used in both directions
and the contents of this area are mirrored in the
corresponding area in the host.

• Specification of the displayed window from the
host to the PT

• Notification of the displayed window from the
PT to the host

• When allocated to the input area, only notifica­tion of the displayed window from the PT to the
host is performed.

• When allocated to the output area, only specifi­cation of the displayed window from the host to
the PT is performed.

• When allocated to an area other than the input
or output area, it is necessary to regularly read
the contents to recognize changes and write
data to control the displayed window.

Notification to the
host

Notify the host with the notification command. None. (The user must confirm contents by

regularly reading data at the locations where
changes are expected or allocating part of the
input area so that data is read automatically.)

System program in
the PT

Use the factory-installed system program or the
system program included with the Support Tool.

Install the system program included with the
DeviceNet Interface Unit.

1-5SectionFunctions of the DeviceNet (CompoBus/D) Interface Unit

13

Item With DeviceNet Interface UnitWith Regular Memory Link

Simultaneous use
with the Memory
Unit

Possible The Memory Unit cannot be used because the

DeviceNet Interface Unit also uses the
Expansion Interface Connector on the back of
the PT. (It is possible to reconnect the Memory
Unit and save data such as the DeviceNet
Interface Unit’s screen data.)

Use of the RS-422A
port

Possible (for communications with the host) Not possible (A bar code reader or computer

running Support Tool can be connected to the
RS-232C port.)

Any functions that are not listed in the table above are identical with the regular
Memory Link and the Memory Link used with the DeviceNet Interface Unit. Com­munications between the PT and host are different between the regular Memory
Link and the Memory Link used with the DeviceNet Interface Unit, but data ex­change between the PT (parts, memory tables, etc.) and PT memory are the
same.

This manual explains only the functions particular to the DeviceNet Interface
Unit and their usage. Refer to the appropriate manual listed below for details on
procedures such as operating the PT and creating screens.

• NT31/NT31C setup and connections:
NT31/NT31C Setup Manual (V062)

• NT631/NT631C setup and connections:
NT631/NT631C Setup Manual (V063)

• NT31/NT31C and NT631/NT631C functions and control:
NT31/NT631 Reference Manual (V064)

• Support Tool operations and operations such as creating screens:
NT-series Support Tool Operation Manual (V061)

Note The manuals listed above cover the “-V2” versions of the NT31/NT31C and

NT631/NT631C, but the PT will operate as a “-V1” version when the DeviceNet
Interface Unit is connected so some functions listed in the manuals will not be
usable. Refer to Appendix B for details on differences between functions in the
“-V1” versions (system version 2.1) and the “-V2” versions.

15

SECTION 2

Operating Procedures

This section shows a simple system configuration example and basic procedures up to using the PT connected to the Device­Net Interface Unit.

2-1 Operating Procedures Flowchart 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-1-1 PT Settings Procedure 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-1-2 Flowchart 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-1-3 Preparations prior to Communications 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-1-4 Setting Up Communications 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-1-5 Starting Remote I/O Communications During Operation 20. . . . . . . . . . . . . . . . . . .

2-2 Simple System Configuration 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .