1. Manuals
  2. Brands
  3. Omron Manuals
  4. Recording Equipment
  5. NT-DRT21
  6. Operation manual

Omron NT-DRT21 Operation Manual

Devicenet compobus/d interface unit
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
NT-DRT21
DeviceNet (CompoBus/D)
Interface Unit
Operation Manual
Produced August 2000

Advertisement

Table of Contents
loading

Related Manuals for Omron NT-DRT21

Summary of Contents for Omron NT-DRT21

  • Page 1 NT-DRT21 DeviceNet (CompoBus/D) Interface Unit Operation Manual Produced August 2000...
  • Page 2 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”...
  • Page 3 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.

  • Page 4: Table Of Contents

    TABLE OF CONTENTS PRECAUTIONS ....... . . 1 Intended Audience .
  • Page 5 TABLE OF CONTENTS SECTION 7 Message Communications ......Overview of Message Communications ........Using Message Communications .
  • Page 6 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).
  • Page 7 PT to which the DeviceNet Interface Unit is mounted. You must use version 3.2 or later of the Support Tool.) Constructing a Information on OMRON DeviceNet products and DeviceNet (CompoBus/D) W267 DeviceNet network network configuration.

  • Page 8: Precautions

    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.

  • Page 9: Intended Audience

    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.

  • Page 10: Operating Environment Precautions

    Application Precautions 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.
  • Page 11 Application Precautions • 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.
  • Page 12 Application Precautions • 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.
  • Page 13 Application Precautions • 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.

  • Page 14: Conformance To Ec Directives

    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.
  • Page 15 Conformance to EC Directives 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.
  • Page 16 Conformance to EC Directives When switching a load with a high inrush current such as an incandescent lamp, suppress the inrush current as shown below. Countermeasure 1 Countermeasure 2 Providing a dark current of approx. Providing a limiting resistor one-third of the rated value through an incandescent lamp...

  • Page 17: Introduction

    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. Features of the DeviceNet Interface Unit ........DeviceNet Functions .

  • Page 18: Features Of The Devicenet Interface Unit

    Compatible with Other DeviceNet is a industry-standard network, so the DeviceNet Interface Unit is Companies’ Masters 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.

  • Page 19: Devicenet Functions

    DeviceNet Functions Section DeviceNet Functions 1-2-1 DeviceNet Features This section explains the features of the DeviceNet network. Multi-vendor 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.

  • Page 20: Communications Functions Of Master Units

    DeviceNet Functions Section 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 Note Input and output areas are automatically allocated in fixed areas unless a Confi- gurator is used.
  • Page 21 IOWR: 160 bytes (starting with command code) C200HZ/HX/HG/HE 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;...

  • Page 22: Devicenet (Compobus/D) Communications Specifications

    DeviceNet Functions Section 1-2-3 DeviceNet (CompoBus/D) Communications Specifications Item Specification Communications protocol DeviceNet Supported connections Master-Slave: Remote I/O and explicit messages (communications) 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)

  • Page 23: System Configuration

    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.

  • Page 24: Example System Configuration

    System Configuration Section 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. System Configuration with a Configurator (Free Allocation) Master Unit Master Unit Master Unit...

  • Page 25: Outline Of Configurator

    Outline of Configurator Section 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 •...

  • Page 26: Functions Of The Devicenet (Compobus/D) Interface Unit

    PCMCIA Card. Excessive noise will cause the computer to run out of control. (This will not, however, adversely affect 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.

  • Page 27: Contrast With The Regular Memory Link Method

    Functions of the DeviceNet (CompoBus/D) Interface Unit Section 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.
  • Page 28 Functions of the DeviceNet (CompoBus/D) Interface Unit Section ences described above and differences in the hardware used for communica- tions. Item With Regular Memory Link With DeviceNet Interface Unit • Data transfer through the DeviceNet input and Communications Data transfer by Memory Link commands via with host (method RS-232C or RS-422A communications output areas (The contents of corresponding...
  • Page 29 Functions of the DeviceNet (CompoBus/D) Interface Unit Section Item With Regular Memory Link With DeviceNet Interface Unit Simultaneous use Possible The Memory Unit cannot be used because the with the Memory DeviceNet Interface Unit also uses the Unit Expansion Interface Connector on the back of the PT.

  • Page 30: Operating Procedures

    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. Operating Procedures Flowchart ..........2-1-1 PT Settings Procedure .

  • Page 31: Operating Procedures Flowchart

    Operating Procedures Flowchart Section Operating Procedures Flowchart This section shows a flowchart of the basic operating procedures up to using the PT connected to the DeviceNet Interface Unit. 2-1-1 PT Settings Procedure Setting the PT Memory’s Input Setting the PT Configuration with and Output Areas the NT-series Support Tool Turn ON the PT’s power supply.

  • Page 32: Flowchart

    Operating Procedures Flowchart Section 2-1-2 Flowchart The following flowchart outlines the basic flow of operations for setting up the DeviceNet system. Determine a suitable baud rate for the user’s system. Refer to the DeviceNet (CompoBus/D) Op- eration Manual (W267). Refer to Section 3 Network Design. Determine the node arrangement, the wiring configura- tion, and the cable lengths.

  • Page 33: Preparations Prior To Communications

    Operating Procedures Flowchart Section 2-1-3 Preparations prior to Communications 1, 2, 3... 1. Set the initial settings for the Master Unit: Unit number (“UNIT No.” or “MACHINE No.” on front panel switch) Node address (back panel DIP switch) Baud rate (back panel DIP switch) Communications continue/stop setting for communications error (front pan- el switch) 2.
  • Page 34 Operating Procedures Flowchart Section c) Turn ON the Scan List Enable Bit in the Master’s software switches (bit Remote I/O communications will start with the scan list enabled. You can use the Master’s software switches to start and stop remote I/O communica- tions.

  • Page 35: Simple System Configuration

    DeviceNet network is operating normally. Simple System Configuration OMRON manufactures a variety of devices that are compatible with the Device- Net standard, including devices that handle bit I/O, temperature inputs, analog I/O, and other functions. Moreover, devices manufactured by other companies can be connected if they conform to DeviceNet standards.

  • Page 36: Network Design

    SECTION 3 Network Design This section 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. Network Configuration ........... . 3-1-1 Network Components .

  • Page 37: Network Configuration

    Network Configuration Section Network Configuration The following diagram shows the configuration of a DeviceNet network. Terminating Resistors Terminating Resistors are connected at each are connected at each DeviceNet Communications end of the trunk line. end of the trunk line. cables are used. power supply 24 VDC Power Supply Tap...

  • Page 38: Connections

    (For further details, refer to Appendix C Standard Models.) XW4B 05C4-T-D (w/o set screw) (made by OMRON) Use a T-branch Tap instead if the connector extends too far from the side of the Master Unit or DeviceNet Interface Unit and interferes with the Unit in the adjacent slot.

  • Page 39: Limitations On The Network Configuration

    Limitations on the Network Configuration Section Limitations on the Network Configuration 3-2-1 Baud Rate and Communications Distance The communications distance in a DeviceNet network is also restricted by the baud rate, as shown in the following table. Baud rate Maximum network length Drop line Total drop length...

  • Page 40: Drop Line Lengths

    Limitations on the Network Configuration Section Note Combining Thick and Thin Cables The most distant nodes can also be connected by a combination of thin and thick cables. When these cables are combined, the following conditions must be met and the maximum network length will be shorter than when only thick cables are used.

  • Page 41: Total Drop Line Length

    Limitations on the Network Configuration Section 3-2-4 Total Drop Line Length This is the total sum length of all the drop lines. Even when the length of each individual drop line is 6 m or less, be sure not to exceed the maximum total drop line length.

  • Page 42: Sharing The Communications Power Supply

    Sharing the Communications Power Supply Section Sharing the Communications Power Supply It is necessary to supply communications power to each node in the DeviceNet network. 3-3-1 Prerequisite Conditions • The communications power supply must be 24 VDC. • The communications power supply must be connected to the trunk line. •...

  • Page 43: Determining The Communications Power Supply Method

    Sharing the Communications Power Supply Section 3-3-2 Determining the Communications Power Supply Method This section provides a basic flow chart to determine which communications power supply method to use. Use the flow chart below to determine the commu- nications power supply on the trunk line. The current carried by each drop line must be less than the permissible current which can be calculated with the for- mula on page 27.

  • Page 44: Locating The Power Supply

    Sharing the Communications Power Supply Section 3-3-3 Locating the Power Supply Power Supply Location The power supply can be located in the configurations shown below. Basically, Patterns select from the configurations 1. and 2. Consider using configuration 3. when power supply specifications cannot be met by configurations 1.
  • Page 45 Sharing the Communications Power Supply Section Note If power supply specifications cannot be met with a single power supply when the current capacity of the thick cable exceeds 8 A even after the power supply location is modified, use more than one communications power supply. In con- figuration 1.

  • Page 46: Step 1: Determining The Best Location For The Power Supply From A Graph

    Sharing the Communications Power Supply Section Thick Cable Distance (m) Max. current (A) 8.00 8.00 5.42 2.93 2.01 1.53 1.23 1.03 0.89 0.78 0.69 0.63 Max. current (A) Distance (m) Thin Cable Distance (m) Max. current (A) 3.00 3.00 3.00 2.06 1.57 1.26...
  • Page 47 Sharing the Communications Power Supply Section • If the nodes are already located at both sides of the power supply, move the power supply in the direction that requires the larger current capacity. • If thin cable is being used, replace it with thick cable. If, after following the above procedure, B is still less than A, go to Step 2 and de- termine the actual position of the nodes by the formula calculation method.

  • Page 48: Step 2: Calculating The Best Location Of The Actual Nodes

    Sharing the Communications Power Supply Section 3-3-5 Step 2: Calculating the Best Location of the Actual Nodes Go to Step 2 if the best location for the power supply cannot be determined from the graphs. The second method calculates the best location for each actual node and does not estimate the worst possible configuration for the power sup- ply.
  • Page 49 Sharing the Communications Power Supply Section each node using the formula below. If the best location for each node can be de- termined using the formula, the specifications for the power supply to each node can also be met. Do not exceed the maximum current capacity of the cable (Thick cable: 8 A and thin cable: 3 A).
  • Page 50 Sharing the Communications Power Supply Section Countermeasures If the best locations cannot be determined using either the first or second formu- lae, follow the procedure as shown below. • Locate the communications power supply in the center of the network and the nodes to both sides of it.

  • Page 51: Step 3: Splitting The System Into Multiple Power Supplies

    Power Supply Tap Configuration Model Name Specifications Manufacturer DCN1-1P Power Supply Includes two OMRON Branch Tap connectors 1485T-P2T5-T5 Power supply tap Includes ground Allen-Bradley terminal Power Supply Tap Connector C Fuse A...

  • Page 52: Grounding The Network

    Grounding the Network Section Internal Circuitry of the Power Supply Tap Power Supply Tap Fuse A Fuse B CAN H CAN H 5-wire cables 5-wire cables Shield Shield on side A on side B CAN L Fuses used: CAN L Little fuse 312008 V–...

  • Page 53: Noise Precautions

    Noise Precautions Section 2. Always ground to 100 Ω or less. 3. Always use a separate ground. Never use the same ground as for inverters or other drive system devices. 3-4-1 Ground Wire Connection Grounding from a The network can be grounded by inserting the ground wire into the same hole as Connector the communications cable’s shield wire, as shown in the following diagram.
  • Page 54 Noise Precautions Section Install surge suppressors on devices that generates noise, particularly devices that have an inductive component such as motors, transformers, solenoids, and magnetic coils. Surge suppressor Surge suppressor (Installed next to device) (Installed next to device) DC input type Device AC input type Device...

  • Page 55: Correcting Faulty Operation Caused By Noise

    Sharing the Same Power Supply Section Correcting Faulty Operation Caused by Noise When noise is thought to be the cause of a malfunction in the DeviceNet net- work, the following measures may be effective. Communications Cable Suspend the communications cable shielding wire without grounding it. This will Shielding filter the noise that flows from the ground to the communications cable and will filter the noise current that flows in the shielding wire.
  • Page 56 Sharing the Same Power Supply Section Because of space and cost difficulties involved in preparing individual power supplies, sharing the same power supply may be unavoidable. If this is the case, take the following precautions. • Be sure to keep the I/O power supply separate. •...

  • Page 57: Installation And Network Connection

    SECTION 4 Installation and Network Connection This section explains how to mount the DeviceNet Interface Unit on the PT and connect the Unit to the DeviceNet network. Components and Their Functions ..........Mounting the Unit on the PT .

  • Page 58: Components And Their Functions

    Components and Their Functions Section Components and Their Functions Front view Rear view Mounting screws Attach the DeviceNet In- terface Unit to the PT. LED indicators Indicate the status of the Communications connector PT connector DeviceNet network and Connects the Unit to a DeviceNet the I/F Unit.

  • Page 59: Mounting The Unit On The Pt

    Connecting to the DeviceNet Network Section Mounting the Unit on the PT Mount the DeviceNet Interface Unit to the Expansion Interface Connector on the back of the PT as shown in the following diagram. (The Expansion Interface Connector is under the “note” label.) This example shows an NT31/NT31C PT. Mounting screws Note 1.
  • Page 60 Connecting to the DeviceNet Network Section 3. Remove the exposed weaving, remove the aluminum tape from the signal and power lines, and strip the covering from the signal and power lines to the proper length for the crimp terminal connectors. Twist together the wires of each of the signal and power lines.

  • Page 61: Installing And Removing The Connector

    Use a flat-blade screwdriver that is consistently thin at the end. The following diagram shows the dimensions of the OMRON XW4Z-00C screwdriver which is made specifically for tightening these set screws. Side view Front view 0.6 mm...

  • Page 62: Connecting Communications Cables To T-Branch Taps

    Connecting to the DeviceNet Network Section 2. Use crimp terminals for wiring. Connecting bare twisted wires can cause the cables to come OFF, break, or short circuit, most likely resulting in incorrect operation and possibly damage to the Units. 3. Use suitable crimp tools and crimping methods when attaching crimp termi- nals.

  • Page 63: Connecting Terminating Resistors

    Manufacturer XW4B-05C1-H1-D Connector for T-branch Tap connection of a OMRON node (with connector attachment screws) Align the cable connector with the socket on the T-branch Tap as shown in the following diagram and fully insert the connector into the socket. Tighten the set screws to secure the connection.

  • Page 64: Pt Settings And Operations

    SECTION 5 PT Settings and Operations This section explains the PT settings and operations required to use the DeviceNet Interface Unit. Installing the System Program ..........5-1-1 PT Operations .

  • Page 65: Installing The System Program

    Installing the System Program Section Installing the System Program A special system program must be installed in the PT in order to use the Device- Net Interface Unit. The system program for the DeviceNet (CompoBus/D) Inter- face Unit is included with the Unit. This section explains how to install the system program in the PT.
  • Page 66 Installing the System Program Section Reference The PT will enter system installer mode automatically when the power is turned ON if the PT does not contain a system program or contains a corrupted system program. Setting the Display In system installer mode, the first screen sets the display language to English or Language Japanese.
  • Page 67 Starting the System Installer 1, 2, 3... 1. Start the system installer by selecting Start/Programs/Omron/Ntst3.2e/ NT-series System Installer from the Windows Start Button. (The menu names in your system may be slightly different depending upon the Support Tool version and selections made when the Support Tool was installed.)
  • Page 68 Installing the System Program Section • Select Download System/Exit from the menu. • Click the X button in the upper-right corner of the main system installer window. • Double-click the system installer icon in the upper-left corner of the system in- staller window.

  • Page 69: Structure Of The System Menu

    Structure of the System Menu Section Structure of the System Menu The System Menu allows the various functions of the PT to be executed using touch switches displayed as a menu on the touch panel. The structure of the sys- tem menu (menu tree) is shown below.

  • Page 70: Initializing Devicenet (Compobus/D) Memory Switches

    Initializing DeviceNet (CompoBus/D) Memory Switches Section Initializing DeviceNet (CompoBus/D) Memory Switches In addition to the standard OMRON memory initialization functions, the system menu for the DeviceNet Interface Unit has a function that initializes Compo- Bus/D setting switches. Refer to the PT’s User’s Manual for details on the other memory initialization op- erations.
  • Page 71 Initializing DeviceNet (CompoBus/D) Memory Switches Section Press Memory Switch. Press CompoBus/D Setting Switch. Press Yes. The memory switches for the DeviceNet Inter- face Unit will be initialized. The message Ini- tializing will be displayed while initialization is in progress. When initialization is completed, a message will be displayed and then the reset screen will be displayed.

  • Page 72: Serial Port A Settings

    The bar code reader type, connection method, communications settings, and op- eration are all the same as they are with standard OMRON system pro- grams. This manual does not provide details on these subjects. Refer to the PT’s Setup Manual for details.
  • Page 73 Serial Port A Settings Section Press PT Memory Switch. Press the touch switch (next screen) or touch switch (previous screen) to display the third memory switch setting screen. Press Comm. A Bar-Code and then select ON or None. The setting option changes each time that the touch switch is pressed.

  • Page 74: Devicenet (Compobus/D) Memory Switch Settings

    DeviceNet (CompoBus/D) Memory Switch Settings Section Press Quit. Pressing “Abort” on the communication condition/confirmation method setting screen causes the PT to return to the memory switch setting screen (3/3) without changing the settings. (The previous settings will still be effective). When the communication condition/confirmation method settings have been completed, the PT returns to the memory switch setting screen (3/3).
  • Page 75 DeviceNet (CompoBus/D) Memory Switch Settings Section Make the following settings in the DeviceNet Interface Unit’s system menu to use the PT as a Slave in DeviceNet remote I/O communications. Item Function Settings Default Comm. Speed Sets the speed used for communications with the 125, 250, or 500 kbps 125 kbps DeviceNet Master.
  • Page 76 DeviceNet (CompoBus/D) Memory Switch Settings Section Press Memory Switch. Press CompoBus/D Setting Switch. Press the touch switch (next screen) or touch switch (previous screen) to display the desired CompoBus/D switch setting screen. The current settings will be displayed when the desired screen is selected. The setting option changes each time the touch switch is pressed.

  • Page 77: Checking The Pt Settings

    When the DeviceNet Interface Unit is used, the PT status control area contains 5 words, the PT status notify area contains 3 words, and the window control area contains 9 words. (In the standard OMRON configuration, the PT status notify area contains 2 words.) The “Expansion I/F”...
  • Page 78 Checking the PT Settings Section Contents of Screen 3/3 Item Meaning Connection Status Shows whether or not the DeviceNet Interface Unit is installed. Comm. Speed Communications speed in the DeviceNet network OUT Area Shows the DeviceNet output area words allocated in PT memory.

  • Page 79: Checking Communications With The Pt

    Checking Communications with the PT Section Checking Communications with the PT Use the following operation in the system menu to check communications be- tween the PT and the DeviceNet Interface Unit. Press Maintenance Mode. Ver 2.10 Press I/O Check. Press I/F Check. Press CompoBus/D.

  • Page 80: Checking The System Program Version

    Checking the System Program Version Section The communications check begins when Execute is pressed in the Compo- Bus/D Communications Check screen. The data string “01 02 04 08 10 20 40 80” is sent to the DeviceNet Interface Unit and displayed under Sending Data. If communications with the Unit are normal, the same data “01 02 04 08 10 20 40 80”...
  • Page 81 Checking the System Program Version Section The PT model, system program name, system program version, and creation date will be dis- played. After checking the system program information, press Quit to return to the ex- pansion mode menu.

  • Page 82: Remote I/O Communications

    SECTION 6 Remote I/O Communications This section 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. Overview of Remote I/O Communications ........6-1-1 Data Exchange with the DeviceNet Interface Unit .

  • Page 83: Overview Of Remote I/O Communications

    Overview of Remote I/O Communications Section Overview of Remote I/O Communications The Master and Slaves can communicate as described below with DeviceNet remote I/O communications. • Input Area: Inputs at the Slave are read automatically and mirrored in the Master’s input area.
  • Page 84 Overview of Remote I/O Communications Section Set the input and output areas with the DeviceNet Master Unit’s software switches or the Configurator. Master Unit I/O memory The DeviceNet Interface Unit’s input Output area Input area and output areas are allocated in the Master’s I/O memory (work area etc.).

  • Page 85: Settings With The Nt-Series Support Tool

    Settings with the NT-series Support Tool Section strobe status. If the strobe ON time is shorter than the CPU Unit’s cycle time, the Master may not read changes in the PT’s status properly. Strobe signal (PT → Master) Strobe ON time (30 to 100 ms) Settings with the NT-series Support Tool This section explains the settings required at the Support Tool when using a PT...
  • Page 86 Settings with the NT-series Support Tool Section Allocating Control/Notify The following three control and notify areas must be allocated in PT memory in Areas order for the PT to be used. • PT status control area (5 words) • PT status notify area (3 words) •...

  • Page 87: Allocating Pt Memory To The Host (Master)

    Allocating PT Memory to the Host (Master) Section Reference 1. The number of words allocated to the memory tables can be set with the Support Tool. 2. The output area and input area can be allocated up to 32 words of PT memory each.
  • Page 88 Allocating PT Memory to the Host (Master) Section Allocate input and output areas to PT memory from the PT’s system menu by selecting CompoBus/D Setting Switches. Item Function Setting range Default Output area leading Sets the leading PT memory address of the PT’s output PM0000 to PM9999 PM0000 address...

  • Page 89: Allocating Input And Output Areas To The Master

    Allocating PT Memory to the Host (Master) Section 6-3-2 Allocating Input and Output Areas to the Master The DeviceNet Interface Unit’s input and output areas are allocated to the Unit as a DeviceNet Slave in the Master’s I/O memory. Fixed Allocation With fixed allocation, words in the CPU Unit are allocated in the order of node numbers starting from node 00.
  • Page 90 Allocating PT Memory to the Host (Master) Section User-set (Free) Allocation A Configurator can be used to allocate a total of 4 blocks” blocks 1 and 2 in the output area and input blocks 1 and 2 in the input area in any order. Blocks can be positioned in any order in memory, e.g., the following order is okay: input block 1, output block 2, input block 2, output block 1.
  • Page 91 Allocating PT Memory to the Host (Master) Section Data Areas for Remote I/O Communications Item Master model Fixed Allocation Free Allocation (Without Configurator) (With Configurator) Maximum number of CVM1/CV-series 63 nodes Slaves per Master CS1-series, 50 nodes 63 nodes C200HX/HG/HE C200HS 32 nodes 63 nodes...
  • Page 92 Allocating PT Memory to the Host (Master) Section Fixed Allocation The Master Unit’s software settings for the following example procedure are shown below. PC model Leading word address CIO 1500 + (25 × unit number) CVM1/CV-series CIO 2000 + (10 × unit number) CS1-series IR 100 + (10 ×...
  • Page 93 Allocating PT Memory to the Host (Master) Section After a short time, turn the scan list clear bit OFF again. We recommend turning the bit OFF after verifying the results of the operation in the master status area. 9. Use a PC Programming Device to turn bit 00 of the software switches (the scan list enable bit) from OFF to ON.

  • Page 94: Allocating Pt Data To Pt Memory

    Allocating PT Data to PT Memory Section If remote I/O communications are operating properly, we recommend read- ing the network configuration with the Configurator and saving that configu- ration as a file for future reference. Allocating PT Data to PT Memory The following data can be allocated in PT memory.
  • Page 95 Allocating PT Data to PT Memory Section • Allocate the PT status notify area to the DeviceNet Interface Unit’s input area if at all possible. It won’t be possible to receive notifications from the PT if the PT status notify area is allocated to the Unit’s output area. Also, exchanging data by message communications takes some time, so changes in PT status may not be recognized immediately if message communications are used.

  • Page 96: Message Communications

    SECTION 7 Message Communications This section explains how to use message communications with a DeviceNet Interface Unit and how to use the PT when mes- sage communications are being used. Overview of Message Communications ........7-1-1 Exchanging Data with the DeviceNet Interface Unit .

  • Page 97: Overview Of Message Communications

    Reference 1. Use the EXPLICIT MESSAGE SEND (28 01) FINS command when send- ing an explicit message from an OMRON Master Unit. With CVM1/CV-series PCs, send FINS commands with the CMND instruc- tion. With CS1-series or C200HX/HG/HE PCs, send FINS commands with the IOWR instruction.

  • Page 98: Using Message Communications

    Using Message Communications Section Similarly, the Master Unit attaches a FINS header to the response from the PT and returns it to the CPU Unit as a FINS response. OMRON Slave or another manufacturer’s DeviceNet Master or Slave Master Unit...
  • Page 99 No. of bytes received (response): The number of bytes received from the des- tination node address (local node). Destination node address (response): 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.

  • Page 100: Using The Cmnd Instruction In Cvm1 And Cv-Series Pcs

    Using Message Communications Section Always specify the local node’s DeviceNet Master Unit in the control code of the CMND or IOWR instruction. An error will occur if another node’s Master Unit is specified. 2. If the DeviceNet Master Unit receives an explicit message, it will automati- cally return a response.
  • Page 101 Using Message Communications Section Item Setting method Loc Netwk The network address of each CPU Bus Unit mounted to the PC (1 to 127) SIOU unit # The unit number of each CPU Bus Unit mounted to the PC and connecting it to a network (0 to 15) DELIVER COMMAND: Specify CMND(194) in the ladder program as shown below.
  • Page 102 Using Message Communications Section Reference When sending explicit messages, set the response monitoring time in C+5 to 0014 Hex (2 seconds) or higher. If a shorter time is set, communications may still be busy when the next command is sent after a timeout occurs. The maximum number of bytes that can be transferred (shown above) is the maximum number of bytes allowed with CMND(194).
  • Page 103 Using Message Communications Section Message Network status NS indicator Communications Enabled Flag ON (1) Communications connection made (network Lit green normal) Communications connection not made Flashing green (network normal, but communications not established) Non-fatal communications error (error in one Flashing red or more Slaves) OFF (0) Offline or power supply is off (no power...

  • Page 104: Using The Iowr Instruction In Cs1-Series And C200Hx/Hg/He Pcs

    Using Message Communications Section 7-2-3 Using the IOWR Instruction in CS1-series and C200HX/HG/HE PCs Use the IOWR instruction when sending explicit messages from a CS1-series or C200HX/HG/HE PC. CS1-series PCs Specify IOWR in the CS1-series PC’s ladder program as shown below. Ladder Symbols IOWR @IOWR...
  • Page 105 Using Message Communications Section The source words (starting with S) provide execution parameter and the com- mand data as shown in the following table. Word Contents Address of first word containing response (See Specifying the Leading Address of the Response Words on page 93.) Response monitoring time (hex) 0000: 1000 to 028F:...
  • Page 106 Using Message Communications Section Area Indirect DM/EM *D00000 to *D32767 addresses in BCD *E00000 to *E32767 *En_00000 to *En_32767 (n = 0 to C) Constants #0000 to #FFFF D: #0000 to #000F (binary) D+1: #0001 to #0080 Data Registers DR0 to DR15 Index Registers Indirect addressing ,IR0 to ,IR15...
  • Page 107 Using Message Communications Section C200HX/HG/HE PCs Specify IOWR in the C200HX/HG/HE PC’s ladder program as shown below. Ladder Symbols IOWR @IOWR Operands C: Control code S: 1 source word D: Destination information Local node Destination node Local Remote CPU Unit Master Unit Master Unit CPU Unit...
  • Page 108 Using Message Communications Section The source words (starting with S) provide execution parameter and the com- mand data as shown in the following table. Word Contents Address of first word containing response (See Specifying the Leading Address of the Response Words on page 95.) Response monitoring time (hex) 0000: 1000 to 028F:...
  • Page 109 Using Message Communications Section Area Allowed range Data area specifier Address (Hex) (Hex) IR Area IR 000 to IR 511 0000 to 01FF Link Area LR 00 to LR 63 03E8 to 0427 Holding Area HR 00 to HR 99 0428 to 048B Auxiliary Area AR 00 to AR 27...
  • Page 110 Using Message Communications Section The unit address of the local Master Unit is not between 0 and F, the Master Unit is mounted on a Slave Rack, etc. 2. The behavior of the Message Communications Enabled Flag in CVM1 and CV-series PCs is different from the behavior in CS1-series and C200HX/ HG/HE PCs.
  • Page 111 Using Message Communications Section Use the type of programming shown below. The programming shown at the top will not always read the response properly. WRONG: Can Improperly Read Response Execution Message condition Communications Enabled Flag IOWR 25506 DIFU(13) C SET D Instructions to read response Message...

  • Page 112: Explicit Messages

    This section describes the explicit messages supported by the DeviceNet Inter- face Unit. When sending explicit messages from an OMRON Master Unit, use the CMND or IOWR instruction to send the message data as an EXPLICIT MESSAGE SEND (28 01) FINS command. Only the normal response is shown here; refer to 7-2-1 EXPLICIT MESSAGE SEND (FINS Command 28 01) for details on re- sponses returned when errors occur.

  • Page 113: Pt Memory Read (L→ H)

    The max. number of bytes that can be read at one time is 250 bytes (FA Hex). When an OMRON Master is being used, the maximum is 240 bytes (F0 Hex). Read data (response): The specified contents of PT memory are returned in 4-digit hexadecimal.

  • Page 114: Pt Memory Write (H→ L)

    The max. number of bytes that can be written at one time is 248 bytes (F8 Hex). When an OMRON Master is being used, the maximum is 240 bytes (F0 Hex). Write data (command): The write data is the 4-digit hexadecimal data that is...

  • Page 115: Pt Memory Write (L→ H)

    The max. number of bytes that can be written at one time is 248 bytes (F8 Hex). When an OMRON Master is being used, the maximum is 240 bytes (F0 Hex). Write data (command): The write data is the 4-digit hexadecimal data that is...

  • Page 116: Sample Program

    Sample Program Section leading address with the rightmost 2 digits (Data L) first and the leftmost 2 digits (Data H) second, as shown in the following diagram. Write data 02 01 14 13 26 25 Leading address Leading address + 1 Leading address + 2 Sample Program Operation...
  • Page 117 Sample Program Section 25315 BSET (71) Clears (writes #0000 to) DM 0000 to DM 2999. #0000 First Cycle Flag DM0000 DM2999 Writes #0001 to IR 000 to indicate the progress of MOV (21) processing. #0001 Writes #3FFE to DM 0000. (Sets destination node MOV (21) number to 3F Hex and destination unit address to #3FFE...
  • Page 118 Sample Program Section Continued from previous page 00002 To read just the error code, the leftmost byte of ANDW (34) DM 2003 is set to 00 and the result is stored in #00FF DM 0010. DM2003 DM0010 If execution of IOWR was completed in the last CMP (20) cycle, the content of DM 0010 (service code) is #0094...

  • Page 119: Error Processing

    SECTION 8 Error Processing This section explains how to troubleshoot errors that may occur when using the DeviceNet Interface Unit. Refer to the Device- Net (CompoBus/D) Operation Manual (W267) and the PT’s User’s Manual for more details. Error Screens Specific to the DeviceNet Interface Unit .

  • Page 120: Error Screens Specific To The Devicenet Interface Unit

    Error Screens Specific to the DeviceNet Interface Unit Section Error Screens Specific to the DeviceNet Interface Unit The following error messages may be displayed when using a DeviceNet Inter- face Unit in addition to the regular error screens (error messages) displayed at the PT.

  • Page 121: Troubleshooting With The Led Indicators

    Troubleshooting with the LED Indicators Section Troubleshooting with the LED Indicators 8-2-1 Meaning of the LED Indicators The DeviceNet Interface Unit has 2 two-color (red or green) LED indicators. MS (Module Status) LED: Indicates the PT’s status as a Slave. NS (Network Status) LED: Indicates the status of the network.

  • Page 122: Identifying And Correcting Errors In Slaves

    Troubleshooting with the LED Indicators Section 8-2-2 Identifying and Correcting Errors in Slaves MS LED NS LED Meaning Remarks Remote I/O Remote I/O Remote I/O communications, message (green) (green) communications or communications in communications, or both are being message progress or message executed.

  • Page 123: A Device Protocol

    Appendix A Device Protocol Compatible DeviceNet Volume I-Release 1.3 General data specifications Volume II-Release 1.3 Vendor name OMRON Corporation Vendor ID = 47 Device profile name Slave: Human Machine Interface Profile number = 18 Product catalog number V066 Product revision...
  • Page 124 Appendix A Device Protocol DeviceNet Object (0x03) Attribute Not supported Object class Service Not supported Item ID content Get (read) Set (write) Value Object instance Attribute 1 MAC ID 2 Baud rate 3 BOI 00 (hexadecimal) 4 Bus Off counter 5 Allocation information Item DeviceNet service...
  • Page 125 Appendix A Device Protocol Item Section Information Max. number of instances Object instance 2 Instance type Polled I/O Production trigger Cyclic Transport type Server Transport class Item ID content Value (read) (write) Object instance 2 Attribute 1 State 2 Instance type 01 (hexadecimal) 3 Transport class trigger 82 (hexadecimal)
  • Page 126 Appendix A Device Protocol Item ID content Value (read) (write) Object instance 3 Attribute 1 State 2 Instance type 01 (hexadecimal) 3 Transport class trigger 82 (hexadecimal) 4 Produced connection ID 5 Consumed connection ID 6 Initial comm. characteristics 01 (hexadecimal) 7 Produced connection size (See note) 8 Consumed connection size...
  • Page 127 Appendix A Device Protocol PT Status Object (0x8C) Attribute Not supported Object class Service Not supported Item ID content Value (read) (write) Object instance Attribute 1 Display Number 2 Memory Table 3 PT Status Item DeviceNet service Parameter option Object instance Service 01 Get_Attribute_All Window Control Object (0x8D)

  • Page 128: B Comparison Of System Program Functions

    Appendix B Comparison of System Program Functions A PT with the DeviceNet Interface Unit installed will operate with the functions of a “-V1” version (system program version 2.1) of the PT regardless of the PT’s actual version. The functions that can actually be used in newer PTs will differ from the functions described in the PT’s manual when the DeviceNet Interface Unit’s system program is installed.
  • Page 129 Appendix B Comparison of System Program Functions Differences from System Program Version 3.0 The following table shows the differences between system program version 3.0 (described in the manuals for the “-V2” PTs) and system program version 2.1 (used with the DeviceNet Interface Unit). Item Ver.

  • Page 130: C Standard Models

    Appendix C Standard Models Model Specifications NT31 STN monochrome display, ivory NT31-ST121(-EVj) NT31-ST121B(-EVj) NT31 STN monochrome display, black NT31C-ST141(-EVj) NT31C STN color display, ivory NT31C STN color display, black NT31C-ST141B(-EVj) NT631-ST211(-EVj) NT631 High-intensity EL display (yellow), ivory NT631-ST211B(-EVj) NT631 High-intensity EL display (yellow), black NT631C-ST141(-EVj) NT631C STN color display, ivory NT631C STN color display, black...
  • Page 131 Thin cable, 5-wire, 150 m Allen-Bradley (see note 2) Note 1. The specifications for cables made by Showa Electric Wire & Cable are identical to the OMRON cable specifications. 2. The cables made by Allen-Bradley are stiffer than those made by OMRON and Showa Electric Wire &...
  • Page 132 Model Name Specifications Manufacturer DCN1-1P Power Supply Branch Tap Required when connecting two or more power OMRON supplies. Two connectors are attached and a terminating resistor is included. 1485T-P2T5-T5 Power Supply Tap Required when connecting two or more power Allen-Bradley (see note) supplies.

  • Page 133: Index

    Index A–B features, 2 applications, precautions, xiii FINS command, EXPLICIT MESSAGE SEND, 85 bar code reader, settings, 59 fixed allocation, 7, 8 baud rate, maximum, 24 with remote I/O communications, 76 branching patterns, 23 free allocation, 7 with remote I/O communications, 77 functions, functions of the DeviceNet Interface Unit, 10 cables, preparing communications cables, 45 G–I...
  • Page 134 Index DeviceNet network, connecting to a DeviceNet network, 2 safety precautions. See precautions network connecting to a DeviceNet network, 2, 45 serial port A settings, 59 designing, 21 grounding the network, 37 specifications, communications specifications, 6 network configuration, 22 standard models, 119 network length, maximum, 24 surge suppressors, to reduce noise, 39 noise, reducing noise, 38, 40...

  • Page 135: Revision History

    Revision History A manual revision code appears as a suffix to the catalog number on the front cover of the manual. Cat. No. V066-E1-1 Revision code The following table outlines the changes made to the manual during each revision. Page numbers refer to the previous version.

Table of Contents