Page 1 Cat. No. W379-E1-03 CVM1-DRM21-V1 C200HW-DRM21-V1 DeviceNet Master Units OPERATION MANUAL...
Page 2 CVM1-DRM21-V1 C200HW-DRM21-V1 DeviceNet Master Units Operation Manual Revised October 2010...
Page 4: Omron Product References
OMRON. No patent liability is assumed with respect to the use of the information contained herein. More- over, because OMRON is constantly striving to improve its high-quality products, the information contained in this manual is subject to change without notice.
Page 6: Table Of Contents
TABLE OF CONTENTS PRECAUTIONS ........xvii Intended Audience .
Page 7 TABLE OF CONTENTS SECTION 5 Software Switches and Status Area....121 Software Switch/Status Area Location ......... Software Switches .
Page 8 TABLE OF CONTENTS 8-22 CONNECTION DATA READ ..........8-23 CONTROLLER STATUS READ .
Page 9 TABLE OF CONTENTS SECTION 10 FINS Commands to DeviceNet Master Units... . 233 10-1 Command List ............10-2 RESET .
Page 10 About this Manual: This manual describes the installation and operation of the CVM1-DRM21-V1 and C200HW- DRM21-V1 DeviceNet Master Units and includes the sections described below. Please read this manual carefully and be sure you understand the information provided before attempting to install and operate the DeviceNet Master and Slave Units. Be sure to read the pre- cautions provided in the first section.
Page 11 About this Manual, Continued Section 9 provides information on the FINS commands that can be addressed to the CPU Units of CS-series and C200HX/HG/HE PLCs. Section 10 provides information on the FINS commands that can be addressed to the DeviceNet Mas- ter Units.
Page 12: Read And Understand This Manual
WHETHER SUCH CLAIM IS BASED ON CONTRACT, WARRANTY, NEGLIGENCE, OR STRICT LIABILITY. In no event shall the responsibility of OMRON for any act exceed the individual price of the product on which liability is asserted. IN NO EVENT SHALL OMRON BE RESPONSIBLE FOR WARRANTY, REPAIR, OR OTHER CLAIMS...
Page 13: Application Considerations
Application Considerations SUITABILITY FOR USE OMRON shall not be responsible for conformity with any standards, codes, or regulations that apply to the combination of products in the customer's application or use of the products. At the customer's request, OMRON will provide applicable third party certification documents identifying ratings and limitations of use that apply to the products.
Page 14 Performance data given in this manual is provided as a guide for the user in determining suitability and does not constitute a warranty. It may represent the result of OMRON's test conditions, and the users must correlate it to actual application requirements. Actual performance is subject to the OMRON Warranty and Limitations of Liability.
Page 16: Precautions
PRECAUTIONS This section provides general precautions for using the Programmable Controller (PLC) Systems and related devices. The information contained in this section is important for the safe and reliable application of PLC Systems. You must read this section and understand the information contained before attempting to set up or operate a PLC System.
Page 17: Intended Audience
It is extremely important that a PLC System and all PLC Units be used for the specified purpose and under the specified conditions, especially in applica- tions that can directly or indirectly affect human life. You must consult with your OMRON representative before applying a PLC System to the abovemen- tioned applications. Safety Precautions !WARNING Never attempt to disassemble any Units while power is being supplied.
Page 18: Operating Environment Precautions
Operating Environment Precautions • The PLC will turn OFF all outputs when its self-diagnosis function detects any error or when a severe failure alarm (FALS) instruction is executed. Unexpected operation, however, may still occur for errors in the I/O con- trol section, errors in I/O memory, and other errors that cannot be detected by the self-diagnosis function.
Page 19: Application Precautions
Application Precautions !Caution The operating environment of the PLC System can have a large effect on the longevity and reliability of the system. Improper operating environments can lead to malfunction, failure, and other unforeseeable problems with the PLC System. Be sure that the operating environment is within the specified condi- tions at installation and remains within the specified conditions during the life of the system.
Page 20: Ec Directives
EMC Directives OMRON devices that comply with EC Directives also conform to the related EMC standards, so that they can more easily be built in to other devices or the overall machine. The actual products have been checked for conformity to EMC standards.
Page 21 EC Directives The following examples shows how to reduce noise. 1,2,3... 1. Noise from the communications cable can be reduced by installing a ferrite core on the communications cable within 10 cm of the DeviceNet Master Unit. Ferrite Core (Data Line Filter): LF130B (manufactured by Easy Magnet Co.) Impedance specifications 105 Ω...
Page 22: Features And System Configuration
Master Unit Models ........1-1-3 DeviceNet Functions of OMRON Master Units ....1-1-4 Types of Slaves.
Page 23: Overview Of Devicenet
Overview of DeviceNet Section 1-1 Overview of DeviceNet 1-1-1 Introduction DeviceNet is a multi-bit, multi-vendor network that combines controls and data on a machine/line-control level and that conforms to DeviceNet open field network specifications. Two types of communications are supported: 1) Remote I/O communications that automatically transfer I/O between Slaves and the CPU Unit without any special programming in the CPU Unit and 2) Message communications that read/write messages, control operation, or perform other functions for Master...
Page 24 Overview of DeviceNet Section 1-1 System Configuration without a Configurator Master Unit CPU Unit Remote I/O communications Slave Slave Slave CVM1/CV-series, CS/CJ-series PLCs: 64 nodes max. C200HZ/HX/HG/HE PLCs: 51 nodes max. C200HS PLCs: 33 nodes max. Note When a C200HX/HG/HE Master Unit is being used in a CS-series PLC, the maximum number of nodes is 51 nodes.
Page 25: Master Unit Models
C200HW-DRM21-V1 CPU Rack or Expansion I/O Rack (Classified as Special I/ C200HZ/HX/HG/HE 10 or 16 O Units) C200HS 1-1-3 DeviceNet Functions of OMRON Master Units Remote I/O Master Function DeviceNet Master Unit CPU Unit Remote I/O communications DeviceNet Slaves Item...
Page 26 CS Series CS1W-DRM21(-V1) 100 input words x 2/100 output words x 1 points per Slave con- CJ Series CJ1W-DRM21 trollable by Master CVM1, CV Series CVM1-DRM21-V1 32 input/32 output words CS Series, C200HX/ C200HW-DRM21-V1 HG/HE C200HS Remote I/O alloca- CS Series...
Page 27 C200HX/HG/HE with command code) Note PLCs equipped with a C200HW-DRM21-V1 DeviceNet Master (for C200HX/ HG/HE or C200HS PLCs) or a CVM1-DRM21-V1 DeviceNet Master (for CVM1/CV-series PLCs) can communicate with each other through FINS mes- sage communications. Furthermore, PLCs equipped with a CS1W-DRM21(-V1) or a CJ1W-DRM21- V1 DeviceNet Unit (for CS/CJ-series PLCs) can also communicate with each other through FINS message communications.
Page 28 Overview of DeviceNet Section 1-1 The FINS message format used in the C200HW-DRM21-V1 and CVM1- DRM21-V1 DeviceNet Master Units is different from the FINS message for- mat used in the CS1W-DRM21-V1 and CJ1W-DRM21-V1 DeviceNet Units, so a PLC equipped with one of the DeviceNet Master Units cannot transmit FINS messages to a PLC equipped with one of the DeviceNet Units.
Page 29: Types Of Slaves
Overview of DeviceNet Section 1-1 1-1-4 Types of Slaves The following classifications are used for DeviceNet Slaves. For details on DRT1-series Slaves, including General-purpose Slaves, Envi- ronment-resistive Slaves, and Special Slaves, refer to the DeviceNet DRT1 Series Slave Operation Manual (W347). For details on DRT2-series Slaves, including General-purpose Slaves, Environment-resistive Slaves, and Special Slaves, refer to the DeviceNet DRT2 Series Slave Operation Manual (W404).
Page 30 Overview of DeviceNet Section 1-1 Name Appearance I/O points Model number Communi- Remarks cations cable Remote I/O 32 input points (NPN) DRT1-ID32ML Normal Compact (35 x 60 x 80 mm Terminals with square con- (W x D x H)) 32 input points (PNP) DRT1-ID32ML-1 Transistors nectors...
Page 31 Overview of DeviceNet Section 1-1 Waterproof and Environment-resistive Slaves Name Appearance I/O points Model number Communi- Remarks cations cable Waterproof 4 input points (NPN) DRT1-ID04CL Round con- Dust and drip-proof struc- Terminals nectors ture for environmental 4 input points (PNP) DRT1-ID04CL-1 resistance (IP 67) 8 input points (NPN)
Page 32 Overview of DeviceNet Section 1-1 ● DRT2 Slaves General-purpose Slaves Name Appearance I/O points Model number Remarks Remote I/O Termi- 16 input points (NPN) DRT2-ID16 Terminal block mounted/ nals with Transistors removed using screws. 16 input points (PNP) DRT2-ID16-1 16 output points (NPN) DRT2-OD16 16 output points (PNP) DRT2-OD16-1...
Page 33 Overview of DeviceNet Section 1-1 Environment-resistive Slaves Name Appearance I/O points Model number Remarks Environment-resis- 8 input points (NPN) DRT2-ID08C Waterproof, oil-proof, and tive Terminals spatter-proof construction 8 input points (PNP) DRT2-ID08C-1 (IP67). 16 input points (NPN) DRT2-HD16C 16 input points (PNP) DRT2-HD16C-1 8 output points (NPN) DRT2-OD08C...
Page 34 Overview of DeviceNet Section 1-1 MULTIPLE I/O TERMINAL Units Unit Words allocated in I/O connec- Unit Instal- Model Remarks points PC memory tions power lation number supply Input Output voltage Communications None Two sta- 0 words None 24 V DRT1-COM Unit tus words track...
Page 35 Overview of DeviceNet Section 1-1 Unit Words allocated in I/O connec- Unit Instal- Model Remarks points PC memory tions power lation number supply Input Output voltage Special Analog 4 inputs 4 words 0 words M3 terminal 24 V GT1-AD04 Inputs: Input block track...
Page 36: Devicenet Configurator
The Configurator is a software configuration tool for the DeviceNet network. The Configurator can be used to set parameters (the scan list) and monitor operation in OMRON Master Units. The Configurator can also be used to set parameters in OMRON and other companies’ Slaves.
Page 37: Devicenet Network Features
The DeviceNet communications specifications are open and standardized, so a DeviceNet-compatible device from any manufacturer can be connected. DeviceNet can be used in a variety of field-level applications by combining devices such as valves and sensors. OMRON Master Unit Another Company’s Master Unit DeviceNet Another Company’s...
Page 38: Remote I/O Communications And Message Communications
1-2-3 Remote I/O Communications and Message Communications DeviceNet supports message communications as well as remote I/O commu- nications. Message communications can be used to make device settings and monitor operation. OMRON Master Unit OMRON Master Unit Message communications DeviceNet Slaves...
Page 39: Devicenet Master Unit Version Comparison
2. The previous versions of DeviceNet Master Units (CVM1-DRM21 and C200HW-DRM21) cannot be used in the same Network as the new ver- sions (CVM1-DRM21-V1 and C200HW-DRM21-V1). They also cannot be mounted to the same PLC. 3. Refer to the CS/CJ Series DeviceNet Units Operation Manual (W380) for details on the differences of the CS/CJ-series DeviceNet Units.
Page 40 CS Series C200HX/HG/HE C200HS Series (All models) (All models) (All models) (All models) Master model number CVM1-DRM21-V1 C200HW-DRM21-V1 Unit type CPU Bus Unit Special I/O Unit Unit number setting range 0 to F 0 to F 0 to F 0 to 9...
Page 41 Specifications Section 1-4 Item Specification CVM1 and CV CS Series C200HX/HG/HE C200HS Series (All models) (All models) (All models) (All models) Remote I/O Slave allocation OUT: CIO 1900 to OUT: CIO 0050 to OUT: IR 50 to IR OUT: IR 50 to IR communica- CIO 1963 CIO 0099...
Page 42 Specifications Section 1-4 Item Specification CVM1 and CV CS Series C200HX/HG/HE C200HS Series (All models) (All models) (All models) (All models) Message com- Max. No. of FINS commands:8 FINS commands:8 FINS commands: munications nodes per Master Not supported. Explicit mes- Explicit messages:63 Unit sages:63...
Page 43: Overview Of Configurator Usage
Overview of Configurator Usage Section 1-5 Item Specification CVM1 and CV CS Series C200HX/HG/HE C200HS Series (All models) (All models) (All models) (All models) 1.72 + 0.022 × Number of words (ms) 2.27 + 0.077 × Effect on the CPU Unit’s cycle 1.1 ms time Number of words...
Page 44 PCMCIA Card. Excessive noise could cause the com- puter to malfunction. (Even if the computer malfunctions, the DeviceNet network itself will not be adversely affected.) 4. The OMRON Configurator can only be used with the following OMRON Master Units:...
Page 45 Number connectable to network One Configurator per network Compatible DeviceNet Masters OMRON Master Units: CS1W-DRM21, CJ1W-DRM21, CVM1-DRM21-V1, C200HW-DRM21-V1, 3G8F7- DRM21 Note: The Master Unit’s device parameters can be output in file format for an Open Network Controller or NetXServer for DeviceNet.
Page 46 List the device information (such as node address order and remote I/O configuration order) of devices connected to the network. Monitor status of OMRON Master. Monitor error log in OMRON Master. (Error log entries contain the error time stamp, error code, and error details.) Monitor Slave’s status and parameters.
Page 47: Basic Operating Procedures
Basic Operating Procedures Section 1-6 Basic Operating Procedures 1-6-1 DeviceNet Network Setup Flowchart The following flowchart outlines the basic flow of operations for setting up the DeviceNet system. Refer to the DeviceNet Operation Manual (W267) for detailed procedures on planning and wiring the network. Determine a suitable baud rate for the user's system.
Page 48: Hardware Preparations
Basic Operating Procedures Section 1-6 1-6-2 Hardware Preparations 1,2,3... 1. Make initial Master Unit settings. • Unit number (“UNIT No.” or “MACHINE No.” on front panel switch) • Node address (back panel DIP switch, pins 1 to 6) • Baud rate (front panel DIP switch, pins 1 and 2) •...
Page 49 Basic Operating Procedures Section 1-6 b) If the scan list is enabled at startup and will be registered again, pro- ceed to step page 28 c) If the scan list is enabled at startup and will not be changed, proceed to step page 28 Note: The status of the dots in the Master Unit’s 7-segment LED display indicate whether the scan list is enabled or disabled.
Page 50: Startup Procedure
Basic Operating Procedures Section 1-6 Note When there are 64 Master Units and Slave Units being used, set up communi- cations based on user-set allocations according to the following procedure. a) Turn ON the power supply to the Masters and turn OFF the power sup- ply to all Slaves.
Page 51 Basic Operating Procedures Section 1-6 Note It is also acceptable to turn ON the communications power supply and Slave’s power supply at the same time, the Slave’s power supply and PLC’s power supply at the same time, or all three power supplies at the same time. •...
Page 52: Operations Listed By Category
Operations Listed by Category Section 1-7 Operations Listed by Category Desired operation Method Page Design Customized remote I/O allocation Allocate I/O using the Configurator. User–friendly customization of remote I/ Allocate I/O using the Master parameter wizard in the O allocations Configurator.
Page 53 Operations Listed by Category Section 1-7...
Page 54: Master Unit Components And Installation
SECTION 2 Master Unit Components and Installation This section explains the main components of the Master Units and the installation procedures. Master Unit for CVM1 and CV-series PLCs ......2-1-1 Component Names and Functions .
Page 55: Master Unit For Cvm1 And Cv-Series Plcs
Master Unit for CVM1 and CV-series PLCs Section 2-1 Master Unit for CVM1 and CV-series PLCs 2-1-1 Component Names and Functions Indicators Rotary switch These switches set the Master's two-digit decimal unit number. Front-panel DIP switch The pins have the following functions: Pins 1 and 2: Baud rate Pin 3: Continue/Stop communications for error Pin 4: Reserved (Always keep OFF.)
Page 56: Switch Settings
Master Unit for CVM1 and CV-series PLCs Section 2-1 2-1-2 Switch Settings Rotary Switches The Master Unit’s two-digit decimal unit number is set with the rotary switches on the front of the Unit. The setting range is 00 to 15. Unit ×10 ×10...
Page 57 Master Unit for CVM1 and CV-series PLCs Section 2-1 Pins 7 and 8 are reserved for system use. Leave these pins set to OFF (0). Communications will not start if the same node address is used for the Master and another node (node address duplication error). Note Always turn OFF the PLC before changing the DIP switch settings.
Page 58: Master Unit Mounting Restrictions
Master Unit for CVM1 and CV-series PLCs Section 2-1 2-1-3 Master Unit Mounting Restrictions The CVM1/CV-series DeviceNet Master Units are classified as CPU Bus Units. When using a CVM1-BC053/BC103 Backplane, be sure to mount the Unit in a slot that can be used for CPU Bus Units. Note CVM1/CV-series DeviceNet Master Units can be used at the same time as SYSMAC BUS and SYSMAC BUS/2 Master Units even when the Configura- tor is not being used.
Page 59: Master Units For C200Hx/Hg/He And C200Hs Plcs
Master Units for C200HX/HG/HE and C200HS PLCs Section 2-2 Master Units for C200HX/HG/HE and C200HS PLCs 2-2-1 Component Names and Functions The following diagram shows the main components of the Master Unit. The functions of these components are described below. Indicators Rear-panel DIP switch These pins have the following functions:...
Page 60: Switch Settings
Master Units for C200HX/HG/HE and C200HS PLCs Section 2-2 2-2-2 Switch Settings Rotary Switch Setting The Master Unit’s one-digit hexadecimal unit number (“MACHINE No.”) is set with the rotary switch on the front of the Unit. MACHINE The unit number setting range depends on the CPU Unit being used, as shown in the following table.
Page 61 Master Units for C200HX/HG/HE and C200HS PLCs Section 2-2 DIP switch setting Node address Pin 6 Pin 5 Pin 4 Pin 3 Pin 2 Pin 1 The Master Unit is shipped with the node address to 0. Since the DIP switch is located on the back of the Master, the Master must be removed from the PLC in order to change the node address setting.
Page 62: Master Unit Mounting/Usage Restrictions
Master Units for C200HX/HG/HE and C200HS PLCs Section 2-2 Pin 3 is used to set the whether or not communications will stop after a com- munications error. Pin 3 Function Continue communications. Stop communications. If pin 3 is ON, communications will be stopped if a transfer error, transmission timeout, or Network power supply error occurs.
Page 63 Master Units for C200HX/HG/HE and C200HS PLCs Section 2-2 With automatic allocation (I/O table creation), it is possible that the actual I/O will be allocated to CIO 0050 to CIO 0099, so in systems with a large number of I/O points, always edit I/O tables using the CX-Programmer. (I/O tables cannot be edited with a Programming Console.) For details, refer to the CX-Programmer Operation Manual.
Page 64: Mounting Devicenet Master Units
Mounting DeviceNet Master Units Section 2-3 Mounting DeviceNet Master Units A sheet is attached to the Masters and Slaves to prevent pieces of wire from entering the Units. Install and wire the Units with the sheets in place. Stray strands of wire could cause malfunctions. Be sure to remove the sheet after installation and wiring to allow proper cool- ing.
Page 65: Mounting T-Branch Taps And Terminating Resistors
Mounting DeviceNet Master Units Section 2-3 1,2,3... 1. If a Configurator is used, up to 10 or 16 Master Units can be mounted to a PLC. Refer to the following table for details. If a Configurator is not used, only 1 Master Unit can be connected to a PLC. CPU model number Max.
Page 66: Remote I/O Communications
SECTION 3 Remote I/O Communications This section describes how to allocate I/O for remote I/O communications. Overview of the Remote I/O Functions ......3-1-1 Introduction .
Page 67: Overview Of The Remote I/O Functions
Overview of the Remote I/O Functions Section 3-1 Overview of the Remote I/O Functions 3-1-1 Introduction The remote I/O communications function automatically exchanges I/O data between Slaves and the CPU Unit of the PLC to which the Master Unit is mounted without any special programming.
Page 68 Overview of the Remote I/O Functions Section 3-1 more than one input or output word. If a Slave requires less than one word, it simply uses the rightmost bits in the word allocated to it. Blocks can be positioned in any order in memory. For example, the following order could be used: input block 1, output block 2, input block 2 , output block 1.
Page 69 Overview of the Remote I/O Functions Section 3-1 Configuration One Master in a network More than one Master in a network More than one Master in a Characteristics Same as previous version. The communications cycle time will The cycle time of the PLC will be increased.
Page 70 CVM1 and CV Series CS Series C200HX/HG/HE C200HS (all models) CV500/ C200HE- CVM1- others CPU11(-Z) others CPU01 (-V@) Master model num- CVM1-DRM21-V1 C200HW-DRM21-V1 Max. No. Without of slaves Configu- per Mas- rator ter Unit With Configu- rator Max. No. Without...
Page 71 Overview of the Remote I/O Functions Section 3-1 CVM1 and CV Series CS Series C200HX/HG/HE C200HS (all models) CV500/ C200HE- CVM1- others CPU11(-Z) others CPU01 (-V@) Alloca- Without Words in the default allocation areas are allocated in order of node address. tion Configu- 1 word per node...
Page 72 Overview of the Remote I/O Functions Section 3-1 Example: Verification Error*Slave Missing Master Status Area 1 Lit green Flashing red Bit 07 ON: Verification error Master Status Area 1 Master Unit Unit 2. Each time a communications error occurs, an error code is placed in an er- ror record in the error log kept in the RAM of the Master Unit.
Page 73 Overview of the Remote I/O Functions Section 3-1 Remote I/O Communications Errors Error MS/NS 7-segment Master status Error Stop Remote indicators display area 1 code (hex) communicati ons for communicati ons error C0 ↔ Master Scan list failure CPU Unit in PRO- MS: No change 07 08 GRAM mode...
Page 74: Scan Lists
Scan Lists Section 3-2 cations for a communications error” and a remote I/O communications time- out or send error occurs. Scan Lists Contents Master Units use scan lists to determine normal DeviceNet communications. The scan lists provide the following. • Slave I/O allocation information that shows the number of I/O points and node addresses allocated to each Slave.
Page 75: Default Remote I/O Allocation
Default Remote I/O Allocation Section 3-3 Note 1. Scan lists cannot be disabled from the Configurator. The scan list will al- ways be enabled when created on the Configurator and registered in a Master Unit. 2. Always enable the scan list during actual system operation. Although op- eration is possible with the scan list disabled when the default allocations are used, communications will continue even if Slaves do not start due to some problem, so the system may not operate properly.
Page 76 Default Remote I/O Allocation Section 3-3 When another company’s slave is being used, both the input and output areas might be used by the slave even if the slave is just an output slave or input slave. Be sure to check the slave’s specifications carefully before using it. CVM1 and CV-series PLCs The I/O areas consist of an input area (IR 2000 to IR 2063) and output area (IR 1900 to IR 1963).
Page 77: I/O Allocation And Errors
Default Remote I/O Allocation Section 3-3 C200HX/HG/HE PLCs The I/O areas consist of an input area (IR 350 to IR 399) and output area (IR 50 to IR 99). The input and output areas are allocated according to the Slaves’ node addresses, as shown in the following diagram. Node Output area Input area...
Page 78 Default Remote I/O Allocation Section 3-3 Change node address 04 to 03. Change node address 05 to 06. Node Node Input area Input area address address Setup Error: I/O Area This error will occur only for C200HX/HG/HE PLCs. Range Violation A setup error (I/O Area Range Violation) will occur and it won’t be possible to start DeviceNet communications if the allocations such as those shown in the following examples are used.
Page 79: Slave Models And I/O Allocations
Default Remote I/O Allocation Section 3-3 3-3-3 Slave Models and I/O Allocations The following table shows the default remote I/O allocations for OMRON Slaves. Required I/O Slave name Model number Output area Input area Outputs Inputs 0 pts 4 pts...
Page 80 Default Remote I/O Allocation Section 3-3 Required I/O Slave name Model number Output area Input area Outputs Inputs 0 pts 32 pts I/O Terminal DRT1-MD32ML(-1) See explanation follow- 2 words (16 bits each) (Connector) ing table. allocated. Analog Input Terminal DRT1-AD04 (2 inputs) B7AC Interface Termi-...
Page 81: Default Remote I/O Allocation Example
Default Remote I/O Allocation Section 3-3 Note DRT2-series Smart Slaves have data stored internally, so when allocating I/O, the user must specify which data is allocated for remote I/O communications with the Master Unit. Refer to 3-5 DeviceNet Remote I/O Communications for details.
Page 82 Default Remote I/O Allocation Section 3-3 3. Mount the Master Unit and wire the network. CVM1 and CV-series PLCs Master Units are treated as CPU Bus Units and can be mounted to the CPU Rack or Expansion CPU Rack. • Without Configurator: Only one Master Unit can mounted. •...
Page 83: Actual System Allocation Example
Default Remote I/O Allocation Section 3-3 12. Remote I/O communications will start with the scan list enabled. You can use the software switches to start and stop remote I/O communications. 13. Confirm that the MS and NS indicators on the Master Unit and all Slaves are lit green.
Page 84 Default Remote I/O Allocation Section 3-3 2. Make the initial settings for the Slaves. Slave Allocated points DIP switch settings Node Baud Pins 9 and 10 address rate (pins Inputs Outputs (pins 1 to 6) 7 and 8) DRT1-ID16X 16 pts 0 (pins 1 to 6 500 kbps Not used (OFF).
Page 85: User-Set Allocations
User-set Allocations Section 3-4 11. Confirm that the MS and NS indicators are lit at all nodes and that the 7- segment display on the Master Unit shows a node address of 10 and that the scan list is enabled Master Unit Node address: 10 Not lit: Scan list enabled...
Page 86 User-set Allocations Section 3-4 Input area Output area Start word Start word Input block 1 Output block 1 No. of words No. of words allocated ("oc- allocated ("oc- cupied") cupied") Start word Start word Input block 2 Output block 2 No.
Page 87 User-set Allocations Section 3-4 Note 1. Blocks can be allocated in any order, as shown in the following example. Output block 1 Input block 2 Output block 2 Input block 1 2. Output blocks do not need to match input blocks in terms of node address settings.
Page 88: Example Of User-Set Allocations
User-set Allocations Section 3-4 5. The same Slave cannot be allocated words in more than one Master. Master Master Words must be allocated to a Slave at one Master only. WRONG Slave 6. Always use the Configurator when there is more than one Master and en- able the scan lists.
Page 89: Basic Application Procedure
User-set Allocations Section 3-4 Setting I/O Allocations with the Configurator 1,2,3... 1. If there are Slaves with Output and Input sizes different from the default settings, edit the I/O information for those Slaves and set the correct I/O sizes (number of bytes). 2.
Page 90 User-set Allocations Section 3-4 CVM1 and CV–series PLCs Master Units are treated as CPU Bus Units and can be mounted to the CPU Rack or Expansion CPU Rack. • Without Configurator: Only one Master Unit can mounted. • With Configurator: Up to 16 Master Units can be mounted. C200HX/HG/HE PLCs Masters are treated as Special I/O Units and can be mounted to the CPU Rack or Expansion I/O Rack.
Page 91: Actual System Allocation Example
User-set Allocations Section 3-4 24. Switch the PLC to RUN mode. Note When there are 64 Master Units and Slave Units being used, set up communi- cations based on user-set allocations according to the following procedure. a) Turn ON the power supply to the Masters and turn OFF the power sup- ply to all Slaves.
Page 92 User-set Allocations Section 3-4 The following remote I/O configuration will be used for the above Network. Remote Adapter Master Unit A Output Terminal I/O Link Unit Sensor Terminal Master Unit B Analog Input Terminal Procedure 1,2,3... 1. Make the initial settings for the Master Units A and B as follows: a) Set the unit numbers.
Page 93 User-set Allocations Section 3-4 2. Make the initial settings for the Slaves. Slave Allocated points DIP switch settings Node Baud Pins 9 and 10 address rate (pins Inputs Outputs (pins 1 to 6) 7 and 8) DRT1-ID16X 16 pts 0 (pins1 to 6 500 kbps Not used (OFF).
Page 94 User-set Allocations Section 3-4 6. Turn ON the communications power supply. 7. Turn OFF all of the Slaves’ power supplies. 8. Connect the Configurator. 9. Place the Configurator online and read the network configuration file that was created in step page 72 10.
Page 95: Devicenet Remote I/O Communications
DeviceNet Remote I/O Communications Section 3-5 DeviceNet Remote I/O Communications This section describes how DRT2-slave data can be allocated for remote I/O communications with the Master Unit. 3-5-1 Overview of Remote I/O Allocations for Smart Slaves Unlike the DRT1-series Slaves, the DRT2-series Smart Slaves store data internally.
Page 96 DeviceNet Remote I/O Communications Section 3-5 Fixed Allocation Type Allocating default I/O data Allocating selected I/O data (patterns) Description I/O data is allocated to fixed addresses in the Selected I/O data (pattern) is allocated to fixed Master Unit in order of node address. addresses in the Master Unit.
Page 97: I/O Allocations For Smart Slaves
DeviceNet Remote I/O Communications Section 3-5 Type Selecting I/O data and allocating to user-defined addresses Description Select up to two types of I/O data, and allocate to user-defined addresses in the Master Unit. Method 1. Select up to two types of I/O data using the Configurator. 2.
Page 98 DeviceNet Remote I/O Communications Section 3-5 Method 3 can be performed by allocating real I/O data and Generic Status Flags independently in the Master’s connection path using the Configura- tor. (This method can be used only with CS/CJ-series Master Units.) ■...
Page 99 DeviceNet Remote I/O Communications Section 3-5 Note 1. Bits 00 and 01 (I/O power supply voltage statuses 1 and 2, respectively) indicate the status of the system power supply, as follows Name System configuration Basic Unit Basic Unit Basic Unit Basic Unit only Input...
Page 100 DeviceNet Remote I/O Communications Section 3-5 Example 2: Using 16 outputs. OUT Area Address header Allocated 16 outputs. IN Area Address header Generic Status Flags Example 3: Using 16 inputs and 8 inputs (Expansion Unit). IN Area Address header Allocated 16 inputs. Address header + 1 Allocated 8 inputs.
Page 101 DeviceNet Remote I/O Communications Section 3-5 quently, increasing network traffic and possibly affecting the communications cycle time. ■ I/O Data for Analog Input Terminal (DRT2-AD04) Data (patterns) Analog Data 1 (8 input bytes) (default) Analog Data 2 (8 input bytes) Generic Status Flags (1 input byte) Top/Valley Detection Timing Flags (2 input bytes) Analog Status Flags (4 input bytes)
Page 102: Message Communications
SECTION 4 Message Communications This section describes message communications using FINS commands sent from the ladder diagram program of the PLC. Overview ........... . 4-1-1 Message Communications Specifications .
Page 103: Overview
The message communications functions allow messages to be sent between nodes on a DeviceNet Network when required by system conditions. The messages can be sent between PLCs, between an OMRON PLC and a Mas- ter made by another company, or between Slaves. They can be used to send/ receive data;...
Page 104 2. The FINS command code can be set to 28 01 to send explicit DeviceNet messages to DeviceNet nodes for OMRON Special Slaves or devices by other manufacturers. 3. The Data length maximums shown in the table are recommended values.
Page 105 No command transfer Note The C200HW-DRM21-V1 DeviceNet Master Unit (for C200HX/HG/HE and C200HS PLCs) and CVM1-DRM21-V1 DeviceNet Master Unit (for CVM1 and CV-series PLCs) use a proprietary OMRON protocol for FINS message com- munications. In contrast, the CS1W-DRM21 and CJ1W-DRM21 DeviceNet Units (for CS-series and CJ-series PLCs) use Explicit messaging for FINS communications, which is the standard messaging protocol in DeviceNet.
Page 106: Message Communications Specifications
Overview Section 4-1 4-1-1 Message Communications Specifications CVM1 and CV-series CS-series, C200HZ/HX/HG/ C200HS Master Unit model number CVM1-DRM21-V1 C200HW-DRM21-V1 Max. No. of FINS Not supported. communi- messages cations Explicit nodes per messages Master Unit Communi- Data SEND(192)/RECV(193) None Not supported.
Page 107 Overview Section 4-1 Example: Routing table error Flashing red Not relevant Master Status Area 1 Master Unit Unit Message Communications Errors Error MS/NS 7-segment Master status Error indicators display area 1 code (hex) E0 ↔ Master Send error Network power error MS: No change Bit 05 turns ON.
Page 108: Fins Commands/Responses
Refer to 6-2 Message Communications Time for details on the message communications time. FINS Commands/Responses The FINS communication protocol was developed by OMRON for use with factory automation control devices. FINS communications enable reading/ writing PLC memory and controlling operation without extensive programming in the user program in the PLC.
Page 109 FINS Commands/Responses Section 4-2 1 byte 1 byte (For CVM1/CV-series PLC) Word Command 1 byte 1 byte Word Response 2 bytes 158 bytes max. FINS header DeviceNet Master Unit Automatically Command Text generated code and attached CPU Unit (CVM1, CV-series, CS-series, Command or C200HX/HG/HE) DeviceNet network...
Page 110: Units Supporting Fins Communications
FINS Commands/Responses Section 4-2 Main code Main code 11: Parameter error 30: Access right error 40: Abort 4-2-2 Units Supporting FINS Communications The parameters used for FINS commands depend on the Unit that is process- ing the command. Command details are provided in other sections for the fol- lowing Units.
Page 111 FINS Commands/Responses Section 4-2 Commands Addressed to CVM1 and CV-series CPU Units Function Name Command Page code Manipulating data in data areas and force-setting/ MEMORY AREA READ resetting bits: MEMORY AREA WRITE CIO Area, DM Area, EM Area, Timer/Counter Area, MEMORY AREA FILL Transition Area, Step Area MULTIPLE MEMORY AREA READ...
Page 112: Message Communications For Cvm1 And Cv-Series Plcs
Manipulating the PLC clock CLOCK READ Note Although CS-series CPU Units support other commands, only the ones listed above can be sent through a C200HW-DRM21-V1 DeviceNet Master Unit. Commands Addressed to CVM1-DRM21-V1 and C200HW-DRM21-V1 DeviceNet Master Units Name Command Page...
Page 113: Data Send/Receive Instructions
Message Communications for CVM1 and CV-series PLCs Section 4-3 Unit #04 Unit #05 Unit #06 Unit #07 Network 1 Network 2 Network 3 Network 4 Address of CPU Bus Unit’s local network unit number The unit number of the DeviceNet Master Unit as a CPU Bus Unit is the num- ber set on the rotary switches on the front panel.
Page 114 Message Communications for CVM1 and CV-series PLCs Section 4-3 The possible values for D depend on the Unit from which the data is being transmitted. If D is in the EM Area, data will be transferred to the current EM bank in the PLC to which the data is being transmitted.
Page 115: Sending Fins Commands
Message Communications for CVM1 and CV-series PLCs Section 4-3 The control words, beginning with C, specify the number of words to be received, the source node, and other parameters. Some control data parame- ters depend on the Unit being transmitted from. Normally a response is required with RECV(193), so set C+3 bit 15 to OFF.
Page 116 15 of C+3 is OFF and no response is received. The default value is $0000, which indicates 2 seconds. Sending Explicit Explicit messages can be sent to OMRON Special Slaves and DeviceNet Messages devices made by other manufacturers by setting the FINS command code to...
Page 117: Using Send(192), Recv(193), And Cmnd(194
Message Communications for CVM1 and CV-series PLCs Section 4-3 28 01. When this is done, set the response monitoring time in C+5 to at least 0014 hex (2 s). If it is set to less than 2 s, communications may be busy even if the next command is executed after the first one times out.
Page 118 Message Communications for CVM1 and CV-series PLCs Section 4-3 Communications Flag The relationship between the Message Communications Enabled Flag and Operation the NS indicator is shown in the following table. Message Network status NS indicator Communications Enabled Flag ON (1) Communications connection made (network Lit green normal)
Page 119: Programming Examples
Message Communications for CVM1 and CV-series PLCs Section 4-3 Data area CV500/CVM1-CPU01-E1 CV1000/CV2000/CVM1-CPU11/21-E Timer Area T000 to T511 T0000 to T1023 Counter Area C000 to C511 C0000 to C1023 DM Area D0000 to D8191 D00000 to D24575 EM Area E00000 to E32765 (See note.) Note EM Memory must be mounted to the CPU Unit to use the EM Area.
Page 120 Message Communications for CVM1 and CV-series PLCs Section 4-3 A500 (041) BSET #1234 D01000 D01004 Sets 1234 in D01000 to D01004. First Scan Flag (030) MOV #0005 D00000 Places data into control data words to specify the 5 words to be transmitted to the CPU Unit of node 06 of network 01, through port 0, with response, 0 retries, (030) MOV #0001 D00001...
Page 121 Message Communications for CVM1 and CV-series PLCs Section 4-3 D01002 = E800:Command parameters D01003 = 0005:Command parameters D = D02000:First response word at local node C = D00000:First control word Settings (hex). D00000 = 0008:Number of command bytes D00001 = 000E:Number of response bytes D00002 = 0001:Destination network address D00003 = 0600:Destination node address (06) Destination unit address (00 = CPU Unit)
Page 122: Message Communications For Cs-Series And C200Hx/Hg/He Plcs
Message Communications for CS-series and C200HX/HG/HE PLCs Section 4-4 Message Communications for CS-series and C200HX/HG/ HE PLCs 4-4-1 Instructions for Message Communications Use the IOWR instruction to send any FINS commands from a CS-series or C200HX/HG/HE PLC equipped with a C200HW-DRM21-V1 DeviceNet Mas- ter Unit.
Page 123 Message Communications for CS-series and C200HX/HG/HE PLCs Section 4-4 Destination Unit Address Unit Setting CPU Unit Communications Unit Special I/O Unit $10 to $1F: Unit No. + 10 The source words (starting with S) provide execution parameter and the com- mand data as shown in the following table.
Page 124 Message Communications for CS-series and C200HX/HG/HE PLCs Section 4-4 Local node Destination node Local Remote Master Unit Master Unit CPU Unit CPU Unit Interpretation Interpretation 1st response word Response monitoring time No. of command bytes Command data Execution Execution Response data 1: For commands addressed to Master Unit 2: For commands addressed to CPU Unit...
Page 125 Message Communications for CS-series and C200HX/HG/HE PLCs Section 4-4 The destination information provides the destination unit number of the Spe- cial I/O Unit and the number of words to be written, as shown in the following diagram. Digits 2 to 4: Number of words to write (001 to 128 BCD) Digit 1: Destination unit number of the Special I/O Unit (0 to F hex) Note Not all data area words can be specified for the first response word in S and S+1.
Page 126: Using Iowr
0000 to F128 Constants Sending Explicit Explicit messages can be sent to OMRON Special Slaves and DeviceNet Messages devices made by other manufacturers by setting the FINS command code to 28 01. When this is done, set the response monitoring time in C+5 to at least 0014 hex (2 s).
Page 127 Message Communications for CS-series and C200HX/HG/HE PLCs Section 4-4 Communications Flags Flag Address Functions Equals Flag C200HX/HG/HE: The Equals Flag turns OFF when an error SR 25506 occurs in writing a command from the CPU Unit to the Master Unit. This Flag turns ON after a command has been written normally from the CPU Unit to the Master Unit.
Page 128 Message Communications for CS-series and C200HX/HG/HE PLCs Section 4-4 Response Received in the Same Cycle IOWR CPU Unit executed Command written Master Unit Message Response : Peripheral servicing Equals Flag (SR 25506) Response read Message Communications Enabled Flag Response Received in the Next Cycle IOWR CPU Unit executed...
Page 129: C200Hx/Hg/He Programming Example: Sending A Fins Command
Message Communications for CS-series and C200HX/HG/HE PLCs Section 4-4 CORRECT: Properly Reads Response DIFU(13) C SET D Instructions to read response Message Communications Enabled Flag RSET D Execution Message condition Communications Enabled Flag IOWR 25506 4-4-4 C200HX/HG/HE Programming Example: Sending a FINS Command Master Unit IOWR...
Page 130 Message Communications for CS-series and C200HX/HG/HE PLCs Section 4-4 DM 1001 = D000:Rest of first response word DM 1002 = 0064:Response monitoring time DM 1003 = 0008:No. of command bytes DM 1004 = 0101:Command code DM 1005 = 8203:Command parameters DM 1006 = E800:Command parameters DM 1007 = 0005:Command parameters D = #0008:Destination information...
Page 131 Message Communications for CS-series and C200HX/HG/HE PLCs Section 4-4 25315 BSET(71) Sets 0000 in DM 0000 to DM 2999. First #0000 Scan Flag DM 0000 DM 2999 Sets 0001 in IR 000. MOV(21) #0001 25315 Place data into control data word to specify re MOV(21) sponse, destination node address 06, and destination #0600...
Page 132: Sending Explicit Messages
Sending Explicit Messages The FINS command code 28 01 can be used to send explicit DeviceNet mes- sages to OMRON Special Slaves and DeviceNet devices made by other man- ufacturers. The use of explicit messages is illustrated in the following diagram.
Page 133 Destination unit address: Local node address: 05 FE or 12 (hex) PLC's Unit The node address of the non-OMRON node is set as the destination node address in the FINS command data. Node 05 Command code Node address of the non-OMRON node:...
Page 134: Fins Command: Explicit Message Send (28 01)
Sending Explicit Messages Section 4-5 WRONG: The FINS com- mand must be addressed to the local Master Unit. Explicit message FINS command Slave or master by other manufacturer 4-5-1 FINS Command: EXPLICIT MESSAGE SEND (28 01) EXPLICIT MESSAGE SEND will send an explicit DeviceNet message to the specified object and receive a response.
Page 135 5. Contact the ODVA to obtain DeviceNet specifications. Contact information is provided below. TEL: 1 734-975-8840 FAX: 1 734-922-0027 Email: odva at odva.org Website: http://www.odva.org/ 6. For details on explicit messages to OMRON Special I/O Slaves, refer to the DeviceNet Slaves Operation Manual (W347).
Page 136: Programming Examples
Explicit message Operation The vendor code is read from a slave (OMRON vendor code: 002F hex) using the EXPLICIT MESSAGE SEND command, 28 01. The command data is writ- ten starting at DM01000, and the response data is stored starting at D02000.
Page 137 Sending Explicit Messages Section 4-5 A500 (041) BSET #0000 D00000 D02999 Sets 0000 in D00000 to D02999. First Scan Flag (030) MOV #0009 D00000 Place data into control data words to specify sending 9 bytes to node 05 (unit FE) on network 01 and to receive 10 bytes in return.
Page 138 Section 4-5 Operation The vendor code is read from a slave (OMRON vendor code: 002F hex) using the EXPLICIT MESSAGE SEND command, 28 01. The command data is writ- ten starting at DM 1000, and the response data is stored starting at DM 2000.
Page 139 Sending Explicit Messages Section 4-5 25315 Sets 0000 in DM 0000 to DM 2999. BSET(71) #0000 First Scan DM 0000 Flag DM 2999 Sets 0001 in IR 000. MOV(21) #0001 25315 Place control data into control data word to specify MOV(21) response, destination node address 05, and destina- #05FE...
Page 140 Sending Explicit Messages Section 4-5 Message Communications Enabled Flag (ON after re- sponse received for mes- sages communications executed a previous cycle) 10112 00002 Compares contents of DM 2001 to 0000 after CMP(20) IOWR execution and response reception have #0000 been completed the previous cycle.
Page 141 Sending Explicit Messages Section 4-5...
Page 142: Software Switches And Status Area
SECTION 5 Software Switches and Status Area This section describes the software switches used to control DeviceNet operation and the status area used to access DeviceNet status. Software Switch/Status Area Location......Software Switches .
Page 143: Software Switch/Status Area Location
Software Switch/Status Area Location Section 5-1 Software Switch/Status Area Location The software switch/status flag area contains the software switches required to control the network and the status flags that indicate the status of the net- work and Slaves. In CVM1 and CV-series PLCs, the software switch and sta- tus flag data is stored in the CPU Bus Unit Area, and in CS-series and C200HX/HG/HE/HS PLCs, it is stored in the Special I/O Unit Area.
Page 144: Software Switches
Software Switches Section 5-2 Master Unit CPU Unit Special I/O Unit Area (For Unit No. 0) IR 100 Unit number 08 IR 100 First word for Unit No. 0 to 9 Software switches (1 word) IR 101 = 100 + 10 x Unit No. 10 words First word for Unit No.
Page 145 Software Switches Section 5-2 Name CVM1 and CV- CS-series C200HX/HG/HE/HS Function series PLCs PLCs Enable Scan List CIO 1500 + 25 x CIO 2000 + 10 x Unit No. 0 to 9: Turn from OFF to ON when Unit No. Unit No.
Page 146: Status Area
Status Area Section 5-3 The Clear Scan List software switch is effective only when the PLC is in PRO- GRAM mode and communications are being performed with the scan list enabled. The status of this bit is ignored when the Master Unit is already oper- ating with the scan list disabled.
Page 147 Status Area Section 5-3 CVM1 and CV-series PLCs CS-series and C200HX/HG/HE/HS PLCs CIO Area IR Area Master status area 1 Master status area 1 First word + 1 First word + 1 (1 word) (1 word) First word + 2 Registered Slaves data Registered Slaves data First word + 2...
Page 148: Master Status Area 1
Status Area Section 5-3 5-3-2 Master Status Area 1 The following diagram shows the structure of Master Status Area 1. CVM1 and CV-series PLCs CIO 1501 + 25 x Unit No. CS-series PLCs CIO 2001 + 10 x Unit No. C200HX/HG/HE/HS PLCs Unit No.
Page 149 Status Area Section 5-3 • A data error occurred in the configuration data for the scan list or other data. (Configuration data error) • A PLC mounting error occurred for a C200HX, C200HG, C200HE, or C200HS PLC. • A routing table error occurred for a CVM1 or CV-series PLC. The Error/Remote I/O Communications Stopped Flag (bit 14) will turn ON whenever this flag turns ON.
Page 150 Status Area Section 5-3 Remote I/O Communications Stopped Status Flag (Bit 08) This flag is turned ON (1) when remote I/O communications are stopped for an error. It will be turned OFF (0) when remote I/O communications are oper- ating normally or when they have been stopped for an error which has already been cleared but the Communications Continue/Stop for Communications setting has been set to stop communications.
Page 151: Master Status Area 2
Status Area Section 5-3 Error/Communications Stopped Flag (Bit 14) This flag is turned ON (1) when any of the bits 00 to 06 in Master Status Area 1 are ON. It can be used as an execution condition for processing errors. This flag will remain ON if communications were stopped due to a communi- cations error, network power supply error, or transmission timeout error but remained stopped even though the cause of the error has been cleared.
Page 152: Registered Slave Data
Status Area Section 5-3 munications Flag is ON). The following example is for CVM1 and CV-series PLCs. Remote I/O Error/Communications Communications Stopped Flag Flag 1501 1501 JMP #0001 Slave I/O processing JME #0001 Message Communications The following type of programming can be used to execute message commu- nications when the Message Communications Enabled Flag is ON and the IOWR Write Normal Flag (Equals Flag) are ON.
Page 153: Normal Slave Data
Status Area Section 5-3 5-3-7 Normal Slave Data The bits in the Normal Slave Data Area correspond to the Slaves’ node addresses, as shown in the following diagram. First Words CVM1 and CV-series PLCs First word + 6 CIO 1506 + 25 x Unit No. CS-series PLCs First word + 7 CIO 2006 + 10 x Unit No.
Page 154: Communications Timing
SECTION 6 Communications Timing This section describes the time required for a complete communications cycle, for an output response to be made to an input, to start the system, and to send a message. Remote I/O Communications Characteristics ......6-1-1 Communications Cycle Time and Refresh Time .
Page 155: Remote I/O Communications Characteristics
Remote I/O Communications Characteristics This section describes the characteristics of DeviceNet communications when OMRON Master and Slave Units are being used. Use this section for refer- ence when planning operations that require precise I/O timing. The equations provided here are valid under the following conditions: 1,2,3...
Page 156 Note Refer to the PLC’s Operation Manual for more details on the refresh time and the PLC’s cycle time. Master Unit for CVM1 and CV-series PLCs (CVM1-DRM21-V1) The PLC’s cycle time is increased by 1.1 ms. This is the extra time required...
Page 157: I/O Response Time
Remote I/O Communications Characteristics Section 6-1 Master Unit for C200HX/HG/HE and C200HS PLCs (C200HW-DRM21-V1) The PLC’s cycle time is increased by the amount shown below. The extra time is required for I/O refreshing. DeviceNet Unit I/O refreshing time (ms) 1.72 + 0.022 × the number of words refreshed CS Series, C200HX, C200HG, and C200HE...
Page 158 Remote I/O Communications Characteristics Section 6-1 :Input Slave’s communications time/Slave (See page 135.) RT-IN :Output Slave’s communications time/Slave (See page 135.) RT-OUT :The PLC’s peripheral servicing cycle time PLC2 The minimum I/O response time (T ) is the total of the following terms: RT-IN PLC2 RT-OUT...
Page 159 Remote I/O Communications Characteristics Section 6-1 Minimum I/O Response Time The minimum I/O response time occurs with the I/O timing shown in the fol- lowing diagram. Cycle time Program Program Program execution execution execution Peripheral Peripheral servicing servicing Master Unit processing Input Output PLC0...
Page 160 Remote I/O Communications Characteristics Section 6-1 Cycle time Program Program Program Program execution execution execution execution Peripheral Peripheral servicing servicing Master Unit processing Input Output PLC0 PLC0 PLC0 : The Input Slave’s ON (OFF) delay : The Output Slave’s ON (OFF) delay : Master Unit’s communications cycle time (See page 134.) : The PLC’s cycle time (program execution + peripheral servicing) PLC0...
Page 161 Remote I/O Communications Characteristics Section 6-1 Program execution Master Unit processing Input Output −T : The Input Slave’s ON (OFF) delay : The Output Slave’s ON (OFF) delay : Input Slave’s communications time/Slave (See page 135.) RT-IN : Output Slave’s communications time/Slave (See page 135.) RT-OUT : The PLC’s cycle time : The PLC’s DeviceNet Unit refresh time (See page 135.)
Page 162 Remote I/O Communications Characteristics Section 6-1 : The Input Slave’s ON (OFF) delay : The Output Slave’s ON (OFF) delay : The communications cycle time for the total Network (See page 134.) : The PLC’s cycle time : The PLC’s DeviceNet Unit refresh time (See page 135.) The maximum I/O response time (T ) is the total of the following terms: + 2 ×...
Page 163: More Than One Master In Network
Remote I/O Communications Characteristics Section 6-1 Peripheral servic- Instruction execu- Peripheral serv- ing cycle time tion cycle time icing cycle time DeviceNet Master Unit DeviceNet I/O response time DRT1-COM Communications Unit Input Unit Output Unit : Input Unit ON (OFF) delay time : Output Unit ON (OFF) delay time : I/O Unit interface cycle time CYCIF...
Page 164: System Startup Time
Remote I/O Communications Characteristics Section 6-1 Group B Group A Master B Master A Slave A Slave B Slave C Slave D Slave E Slave F Group A communications Group A communications cycle time: T cycle time: T RM-A RM-B In Networks with two Masters, the communications cycle time for the entire Network will be the sum of the communications cycle times for the groups.
Page 165: Message Communications Time
Message Communications Time Section 6-2 Remote I/O Communications Slaves' I/O pro- cessing Flag Error/Communications Stopped Flag Note Include only the Slaves’ I/O processing between the JMP(004) and JME(005) instructions. If actual I/O processing is performed, the Slaves’ I/O processing will not be executed when a communications error occurs and the previous values will be maintained.
Page 166 Message Communications Time Section 6-2 Message Communications Only (No Remote I/O Communications) The following equation can be used to compute the message communications time when remote I/O communications are not being used. Communications cycle time = 2 (see note) + 0.11 × T + 0.6 [ms] : The baud rate factor (500 kbps: T...
Page 167 Message Communications Time Section 6-2...
Page 168: Troubleshooting And Maintenance
SECTION 7 Troubleshooting and Maintenance This section describes error processing, periodic maintenance operations, and troubleshooting procedures needed to keep the DeviceNet network operating properly. We recommend reading through the error processing procedures before operation so that operating errors can be identified and corrected more quickly. Indicators and Error Processing .
Page 169: Indicators And Error Processing
Indicators and Error Processing Section 7-1 Indicators and Error Processing 7-1-1 Master Unit Indicators DeviceNet Master Units have an MS (Module Status) indicator that indicates the status of the node itself and an NS (Network Status) indicator that indi- cates the status of the Network. The Master Units also have a 2-digit, 7-seg- ment display and two dot indicators.
Page 170 Indicators and Error Processing Section 7-1 error occurs, the display will alternate between the error code and the node address of the faulty Slave. Normal: Master Unit's node address Error: Error code and faulty node address Scan list enabled/disabled Dot Indicators The dots at the lower-right corner of each digit show whether the scan list is enabled or disabled for DeviceNet remote I/O communications.
Page 171: Identifying Errors From The Indicators
Indicators and Error Processing Section 7-1 There is no priority in the error codes; all errors that have occurred will be dis- played in order. All error codes begin with letters, so they can be distinguished from node addresses immediately. 7-1-4 Identifying Errors from the Indicators The indicators can be used to identify the cause of an error.
Page 172: Errors Occurring In The Master Unit
A watchdog timer error occurred in the Master Unit and Master Unit operation will stop. Replace the Master Unit. ON (red) The MS indicator will be OFF in C200HW-DRM21-V1, ON (red) in the CVM1-DRM21-V1. A0 ⇔ Mnn Communications stopped The Master has been set to stop communications in the...
Page 173 Indicators and Error Processing Section 7-1 Display/Indicator status Error Probable cause and remedy 7-segment d2 ⇔ Snn Flashing Setup error: The number of I/O points/Slave has exceeded 64 bytes. (green) (red) Slave not supported The Master Unit will attempt to reconnect to the Slaves with the error.
Page 174 Indicators and Error Processing Section 7-1 Display/Indicator status Error Probable cause and remedy 7-segment E4 ⇔ Mnn Flashing PLC mounting error (for CS-series and C200HX/HG/HE PLCs: (red) V1 Master Units only; see A Configurator was not used to configure a network that note 1 at end of table) includes another DeviceNet Master Unit, a SYSMAC BUS Remote I/O Master Unit, or I/O Link Unit.
Page 175 Indicators and Error Processing Section 7-1 Display/Indicator status Error Probable cause and remedy 7-segment F3 ⇔ Mnn Flashing Incorrect switch settings A mistake has been made in the DIP switch settings. (green) Master Unit operation will stop. Bits 00 and 14 will be ON in Master Status Area 1. Check the settings and restart the Master Unit.
Page 176: Error Log Function
CPU Unit for C200HX/HG/HE and C200HS PLCs.) Note Even with the CVM1-DRM21-V1, the time stamp is not provided for any error that occurs during initialization with the PLC.
Page 177: Error Codes
Error Log Function Section 7-2 7-2-3 Error Codes The error codes used in the error log are described in the following table. The error codes cover errors such as destroyed responses for messages commu- nications, which are not displayed on the front-panel indicators. Error Error details Error...
Page 178: Fins Commands For Error Logs
Error Log Function Section 7-2 Note When monitoring the error log from the Configurator, the information in the “Meaning” column is also displayed. 7-2-4 FINS Commands for Error Logs ERROR LOG READ Command Block 1 byte No. of records First record Command to read to read...
Page 179 Error Log Function Section 7-2 CVM1 and CV-series PLCs: Using CMND(194) CMND Master Unit (194) (unit No. 0) Unit Node address 05 FINS command FINS unit address FE or 10 (hex) Network 01 The program reads 20 records of error log data from the Master Unit, stores the data, and then clears the error log.
Page 180 Error Log Function Section 7-2 D = D02000:First response word at local node C = D00006:First control word Settings (hex). D00006 = 0002: Number of command bytes D00007= 0004: Number of response bytes D00008 = 0001: Destination network address (01) D00009 = 05FE: Destination node address (05) Destination FINS unit address (FE = Master Unit) D00010= 0000:...
Page 181 Error Log Function Section 7-2 Message Com- munications Enabled Flag Reads 20 records from node 05 in network 01 and 000000 A50200 150112 151000 (194) stores the data beginning at D02000. Control data is CMND D01000 D02000 D00000 specified starting at D00000. Port En- Error Log (060)
Page 182 Error Log Function Section 7-2 IOWR Master Unit (machine No. 0) Unit Node address 05 FINS command FINS unit address FE or 10 (hex) Network 01 The program reads 20 records of error log data from the Master Unit, stores the data, and then clears the error log.
Page 183 Error Log Function Section 7-2 Clearing the Error Log C = DM 0000:Control word Settings (hex) DM 0000 = 05FE: Response Destination node address: 05 Destination FINS unit address: FE (Master Unit) S = DM 1010:First source word Settings (hex) DM 1010 = 8207:First response word: DM 2000 DM 1011 = D000:Rest of first response word DM 1012 = 0064:Response monitoring time...
Page 184 Error Log Function Section 7-2 25315 Sets 0000 in DM 0000 to DM 2999. BSET(71) First #0000 Scan Flag DM 0000 DM 2999 Sets the contents of IR 000 to 0001 (i.e., turns ON MOV(21) IR 00000). #0001 25315 MOV(21) Place data into control data words to specify reading 20 records from the error log from the Master Unit at First...
Page 185 Error Log Function Section 7-2 25315 Place 2005, 0100, and 0199 into DM 0097, DM 0098, MOV(21) and DM 0099 to use DM 2005, DM 0100, and DM 0199 First #2005 as the initial addresses for indirectly addressing storing Scan the response code, the first error log data word, and the Flag DM 0097...
Page 186 Error Log Function Section 7-2 00003 XFER Uses indirect addressing with DM 0097 and DM 0098 to store 5 words of data in consecutive words (remov- #0005 ing the error log data from the response data). *DM 0097 *DM 0098 ADD(30) Adds 0005 to the contents of DM 0097 to move to the next 5 words.
Page 187: Troubleshooting
Troubleshooting Section 7-3 00000 Moves the contents of DM 6032 (Master Status Area 2 MOV(21) for Unit 00) to IR 001. Execution DM 6032 condition 10112 00100 Shifts the contents of IR 000 one bit to the left to turn ASL(25) ON IR 000001.
Page 188 Troubleshooting Section 7-3 PLC Error Use the following table to troubleshoot errors in a PLC that has a CVM1- (CVM1-DRM21-V1) DRM21-V1 Master Unit installed. Refer to the CV-series PLCs Operation Manual: Ladder Diagrams for more details. Error Probable cause An I/O verification error occurred.
Page 189 • Check whether the Slaves are operating properly. When an OMRON Slave is being used, refer to the troubleshooting tables in the DeviceNet Operation Manual (W267). If another company’s Slave is being used, refer to that Slave’s user’s...
Page 190 • The simultaneity of node-units of data is ensured between the PLC and Master Unit. • In OMRON Slaves, the simultaneity of word-units of data is ensured. • If another company’s Slave is being used, refer to that Slave’s user’s manual for details.
Page 191: Maintenance
Maintenance Section 7-4 Maintenance This section describes the routine cleaning and inspection recommended as regular maintenance. 7-4-1 Cleaning Clean the DeviceNet Units regularly as described below in order to keep it in its optimal operating condition. • Wipe the Unit with a dry, soft cloth for regular cleaning. •...
Page 192 • When a Unit is being returned for repair, attach a sheet of paper detailing the problem and return the Unit to your OMRON dealer. • If there is a faulty contact, try wiping the contact with a clean, lint-free cloth dampened with alcohol.
Page 193 Maintenance Section 7-4 Recreating the Allocations from the Configurator The following procedure can be used to recreate user-set allocations and write them to the Master Unit. 1,2,3... 1. Turn on power to the Master Unit, Slaves, and Configurator. 2. Place the Configurator online and create the device list. 3.
Page 194: Fins Commands To Cvm1 And Cv-Series Cpu Units
SECTION 8 FINS Commands to CVM1 and CV-series CPU Units This section provides information on the FINS commands that can be addressed to the CPU Units of CVM1 and CV- series PLCs. Command List ..........Memory Area Designations .
Page 195 8-35 ERROR LOG CLEAR......... . . 8-36 FILE NAME READ .
Page 196: Command List
Command List Section 8-1 Command List The beginning portions of the command and response blocks up to the com- mand codes and the FCS and terminator have been omitted for simplicity, but must be added for actual transmission if not automatically generated for the transmission method being used.
Page 197: Memory Area Designations
Memory Area Designations Section 8-2 Name Command PLC mode Page code MONITOR DEBUG PROGRAM FILE DELETE Valid Valid Valid Valid VOLUME LABEL CREATE/DELETE Valid Valid Valid Valid FILE COPY Valid Valid Valid Valid FILE NAME CHANGE Valid Valid Valid Valid FILE DATA CHECK Valid Valid...
Page 198 Memory Area Designations Section 8-2 CV500 or CVM1-CPU01-E Memory area Data Data area address Address used in Memory No. of communications area code bytes CIO, TR, CPU Bit status 000000 to 25515 000000 to 09FB0F Bus Link, and TR0 to TR7 09FF00 to 09FF07 Auxiliary Areas G00000 to G25515...
Page 199: Word/Bit Addresses
Section 8-2 Memory Area Designations Memory area Data Data area address Address used in Memory No. of communications area code bytes Timer Area/ Completion Flag sta- T0000 to T1023 000000 to 03FF00 Counter Area C0000 to C1023 080000 to 0BFF00 Completion Flag sta- T0000 to T1023 000000 to 03FF00...
Page 200: Volume Labels And File Names
Volume Labels and File Names Section 8-3 8-2-2 Data Configurations The configuration of the various types of data that can be read or written is shown below. The number of bytes required for each type of data is also given. Flag or Bit Status (One 00: Bit is OFF (0) Byte)
Page 201: Memory Area Read
MEMORY AREA READ Section 8-4 Volume Label/File Name Extension Period Volume Label/File Name Each volume label or file name must have eight ASCII characters with or with- out spaces (ASCII 20). If less than eight letters are used, add spaces to the end of the label/name.
Page 202: Memory Area Write
MEMORY AREA WRITE Section 8-5 Memory area Data Memory area No. of code bytes Word contents Transition Flag status Step Flag status Forced status Bit status Word contents Expansion DM Word contents, specified bank 90 to 97 (banks 0 to 7) Word contents, current bank Action Flag status...
Page 203: Memory Area Fill
MEMORY AREA FILL Section 8-6 The following data can be written (refer to page 176 Memory Area Designa- tions for the word/bit address designations): Memory area Data Memory area No. of code bytes CIO, TR, CPU Bus Word contents Link, and Auxiliary Timer/Counter Word contents Step...
Page 204: Multiple Memory Area Read
MULTIPLE MEMORY AREA READ Section 8-7 The following data can be written (refer to page 176 Memory Area Designa- tions for memory area designations): Memory area Data Memory area No. of code bytes CIO, TR, CPU Bus Word contents Link, and Auxiliary Timer/Counter Word contents Expansion DM...
Page 205: Memory Area Transfer
MEMORY AREA TRANSFER Section 8-8 Memory area Data Memory area No. of code bytes Timer/Counter Completion Flag status Completion Flag status (with forced status) Word contents Transition Flag status Flag status (with forced status) Step Flag status Status Step Timer PV Forced Status Bit status Word contents...
Page 206: Composite Registration Read
COMPOSITE REGISTRATION READ Section 8-9 Response Block Command Response code code Parameters Memory area code (command): The data area to transfer from and the data area to transfer to. Beginning address (command): The first word/value to transfer from and the first word to transfer to. No.
Page 207: Register Composite Read
REGISTER COMPOSITE READ Section 8-10 8-10 REGISTER COMPOSITE READ Registers the contents to be read with the COMPOSITE REGISTRATION READ command (01 10). Up to 100 items can be registered for reading for 2- bytes data; up to 50 items for 4-byte data, i.e., up to 200 bytes of data can be read.
Page 208: Parameter Area Read
PARAMETER AREA READ Section 8-11 Memory area Data Memory area No. of code bytes Forced Status Bit status Word contents Expansion DM Word contents, specified bank 90 to 97 (banks 0 to 7) Word contents, current bank Action Flag status Register Register contents Expansion DM current bank no.
Page 209 PARAMETER AREA READ Section 8-11 No. of words x 2 (each word consists of two bytes) Parameter Areas There are five parameter areas, each of which has consecutive word addresses beginning from 0000. The following data can be read. The word ranges in parentheses show the possible values for the beginning word.
Page 210: Parameter Area Write
PARAMETER AREA WRITE Section 8-12 8-12 PARAMETER AREA WRITE Writes data to the specified number of consecutive parameter area words starting from the specified word. All words in the specified parameter area must be written at the same time to ensure complete data. A maximum of 76 words can be written with each command.
Page 211: Parameter Area Clear
PARAMETER AREA CLEAR Section 8-13 addresses beginning from 0000. The following data can be read. The word ranges in parentheses show the possible values for the beginning word. 80 10 80 00 PLC Setup (0000 to 00FF) (0000 to 0FFF) 80 11 80 01 Peripheral Device settings...
Page 212: Program Area Protect
PROGRAM AREA PROTECT Section 8-14 No. of words (command): The number of words to clear (see diagram below). Data (command): Set to 0000. The number of word addresses where the data (0000) should be written is specified by the number of words in the com- mand block.
Page 213: Program Area Protect Clear
PROGRAM AREA PROTECT CLEAR Section 8-15 Password (command): Set any four ASCII characters. The password is used with the PROGRAM AREA PROTECT CLEAR command (refer to page 192 PROGRAM AREA PROTECT CLEAR). 8-15 PROGRAM AREA PROTECT CLEAR Restores write and read access rights so that data can be written to and read from the program area.
Page 214: Program Area Write
PROGRAM AREA WRITE Section 8-17 Response Block Response Program No. of Command Beginning word Data code bytes code Parameters Program no. (command and response): Set to 0000. Beginning word (command and response): Set between 00000E00 and 0000FFFE for the CV500 or CVM1-CPU01 and between 00000E00 and 0001FFFE for the CV1000/CV2000 or the CVM1-CPU11/21.
Page 215: Program Area Clear
PROGRAM AREA CLEAR Section 8-18 Beginning word (command and response): Set between 00000E00 and 0000FFFE for the CV500 or CVM1-CPU01 and between 00000E00 and 0001FFFE for the CV1000/CV2000 or the CVM1-CPU11/21. The beginning word must be an even number. No. of bytes (command and response): The number of bytes in an even number (150 or smaller).
Page 216: Stop
STOP Section 8-20 Command Block Command Program Mode code Response Block Response Command code code Parameters Program no. (command): Set to 0000. Mode (command): As follows: 0001:DEBUG mode 0002:MONITOR mode 0004:RUN mode Note If the mode is not specified, the PLC will go to MONITOR mode. 8-20 STOP Changes the PLC to PROGRAM mode, stopping program execution.
Page 217 CONTROLLER DATA READ Section 8-21 Command Block Command Data to be read (00 or 01) code Response Block The format is as follows if 00 is specified as the data to be read: 20 bytes 20 bytes 40 bytes 12 bytes Command Response Controller...
Page 218 CONTROLLER DATA READ Section 8-21 1st byte 12th byte Program Memory card No. of steps/ No. of DM words area size size transitions Timer/counter Expansion Kind of memory card IOM size size DM size Item Meaning Unit Program area size The size of PLC Setup and program area K words (1K words = 1,024 words) IOM size...
Page 219: Connection Data Read
CONNECTION DATA READ Section 8-22 8-22 CONNECTION DATA READ Reads the model number of the specified Units. Command Block Command No. of Units code Unit address Response Block 20 bytes 20 bytes Response Command Model number Model number code code Unit address Unit address No.
Page 220: Controller Status Read
CONTROLLER STATUS READ Section 8-23 8-23 CONTROLLER STATUS READ Reads the status of the Controller. Note To read the error log, read the appropriate Auxiliary Area words or execute the ERROR LOG READ command (refer to page 208 ERROR LOG READ). Command Block Command code...
Page 221: Cycle Time Read
CYCLE TIME READ Section 8-24 First byte Second byte 15 14 13 12 11 10 9 1: Momentary power interruption 1: CPU Bus Unit setting error 1: Battery error 1: SYSMAC BUS error 1: SYSMAC BUS/2 error 1: CPU Bus Unit error 1: I/O verification error 1: CPU bus error 1: Non-fatal SFC error...
Page 222: Clock Read
CLOCK READ Section 8-25 Command Response code code The response format is as follows when the parameter is 01 (when reading): Command Response Average cycle time Max. cycle time Min. cycle time code code Parameters Parameter code (command): As follows: 00: Initializes the cycle time.
Page 223: Clock Write
CLOCK WRITE Section 8-26 8-26 CLOCK WRITE Sets the clock. Note 1. The PLC automatically checks the range of the specified data. If any por- tion of the data is incorrect, the clock will not be set. 2. If any other device holds the access right, the clock will not be set. Command Block Command Year Month Date Hour...
Page 224: Message Clear
MESSAGE CLEAR Section 8-28 Response Block 32 bytes 32 bytes Command Message Response Message no. Message code code parameter Parameters Message no. parameter (command and response): In the command block, turn ON (1) the bits of the messages to be read. In the response block, the bits of the messages being returned will be ON (1).
Page 225: Fal/Fals Read
FAL/FALS READ Section 8-29 Response Block Command Response code code Parameters Message no. (command): Turn ON the bits of the messages to be cleared. First byte Second byte Set to 0 Message no. 0 Message no. 1 01: Message clear Message no.
Page 226: Access Right Acquire
ACCESS RIGHT ACQUIRE Section 8-30 Error message (response): The error message specified in the FAL(006) or FALS(007) instruction. If there is no error, 16 spaces (ASCII 20) will be returned. 8-30 ACCESS RIGHT ACQUIRE Acquires the access right as long as no other device holds it. Execute the ACCESS RIGHT ACQUIRE command when you need to execute commands continuously without being interrupted by other devices.
Page 227: Access Right Forced Acquire
ACCESS RIGHT FORCED ACQUIRE Section 8-31 8-31 ACCESS RIGHT FORCED ACQUIRE Acquires the access right even if another device already holds it. Note 1. Even if any other device has the access right, the access right can be ac- quired with this command and a normal response code will be returned. 2.
Page 228: Error Clear
ERROR CLEAR Section 8-33 Command Block Command Program code Response Block Command Response code code Parameters Program no. (command): Set to 0000. 8-33 ERROR CLEAR Clears errors or error messages from the PLC. A normal response will be returned even if the error has not occurred. Note The cause of the error must be removed before executing the ERROR CLEAR command or the same error will occur again after the ERROR CLEAR command is executed.
Page 229: Error Log Read
ERROR LOG READ Section 8-34 Error code Meaning 0400 to 0415 CPU Bus Unit setting error (the rightmost two digits are the unit number in BCD of the Unit that has the error). 4101 to 42FF FAL(006) executed in the user program. The following codes can be used only when the PLC is in PROGRAM mode: Error code Meaning...
Page 230: Error Log Clear
ERROR LOG CLEAR Section 8-35 No. of stored records (response): The number of records that have been recorded. No. of records (command and response): The number of records to read. With the DeviceNet network, up to 15 records can be read at the same time. Error log data (response): The specified error log records will be returned in sequence starting from the beginning record number.
Page 231 FILE NAME READ Section 8-36 Response Block 26 bytes 20 bytes 20 bytes Response Command Disk data No. of File data File data code code files Parameters Disk no. (command): Set to 0000 for the file device (memory card). Beginning file position (command): The first file to be read (the first file number is 0000).
Page 232: Single File Read
SINGLE FILE READ Section 8-37 Date/Time The date and time that the file was created (see below). File Capacity The capacity (bytes) of the file. Date/Time The configuration of the clock data (four bytes or 32 bits) is as follows: 3rd byte 1st byte 2nd byte...
Page 233: Memory Card Format
MEMORY CARD FORMAT Section 8-39 name as an existing file. When a new file is written or an existing file is modi- fied, the file will record the clock data of the PLC as the date of the file. Note Writing a new file or modifying an existing file must be done within the capac- ity of the file device or the SINGLE FILE WRITE command cannot be exe- cuted.
Page 234: File Delete
FILE DELETE Section 8-40 Response Block Command Response code code Parameters Disk no. (command): Set to 0000 for the file device (memory card). 8-40 FILE DELETE Deletes files stored by the file device connected to the PLC. Note 1. The specified files will be deleted in sequence. If non-existing file names have been specified, the PLC will ignore them and the operation will con- tinue.
Page 235: File Copy
FILE COPY Section 8-42 Command Disk no. Parameter code code Response Block Command Response code code Parameters Disk no. (command): Set to 0000 for the file device (memory card). Parameter code (command and response): As follows: 0000: Creates a new volume label. If a label already exists, nothing will be executed.
Page 236: File Data Check
FILE DATA CHECK Section 8-44 Command Block 12 bytes 12 bytes Command Disk no. Old file name New file name code Response Block Command Response code code Parameters Disk no. (command): Set to 0000 for the file device (memory cards). Old and new file names (command): The original file name and a new name for the file (refer to page 179 Volume Labels and File Names for the configuration of the file name).
Page 237: Memory Area File Transfer
MEMORY AREA FILE TRANSFER Section 8-45 Example • Data:13 3A E4 F3 CC 0B 3C 5F A2 • Words:133A E4F3 CC0B 3C5F A200 • Total:133A + E4F3 + CC0B + 3C5F + A200 = 2A297 • Checksum:A297 Data “File data” refers to the data in a file that a file device stores. A file data check is done with the checksum.
Page 238: Parameter Area File Transfer
PARAMETER AREA FILE TRANSFER Section 8-46 No. of items (command and response): In the command block, the number of items to be transferred or compared. In the response block, the number of items transferred or compared. Disk no. (command): Set to 0000 for the file device (memory cards). File name (command): The file to be transferred or compared (refer to page 179 Volume Labels and File Names for the configuration of the file name).
Page 239: Program Area File Transfer
PROGRAM AREA FILE TRANSFER Section 8-47 Response Block Command Response No. of words code code Parameters Parameter code (command): As follows: 0000: Data transfer from the PLC’s parameter area to the file device. 0001: Data transfer from the file device to the PLC’s parameter area. 0002: Data compared.
Page 240: Forced Set/Reset
FORCED SET/RESET Section 8-48 Note 1. The checksum is stored at the front (bytes 0 and 1) of the file. Thus file transfer or comparison is effective from the next byte after the checksum. 2. This command cannot be executed when the access right is held by any other device or when the PLC is write-protected by the key switch on the front panel.
Page 241: Forced Set/Reset Cancel
FORCED SET/RESET CANCEL Section 8-49 Command Block Set/Reset Set/reset Command No. of Bit/flag Bit/flag specification specification code bits/flags Memory area code Memory area code Forced set/reset data Forced set/reset data Response Block Command Response code code Parameters No. of bits/flags (command): The number of bits/flags to be controlled. Set/Reset specification (command): The action to be taken for each bit/flag Value Name...
Page 242 FORCED SET/RESET CANCEL Section 8-49 Response Block Command Response code code Note The bits (flags) in the following memory areas can be forced set or forced reset, and cancelled. Memory area Data Memory code CIO, TR, CPU Bus Link, Bits status and Auxiliary Timer/Counter Completion Flag status...
Page 243 FORCED SET/RESET CANCEL Section 8-49...
Page 244: Fins Commands To Cs-Series And C200Hx/Hg/He Cpu Units
SECTION 9 FINS Commands to CS-series and C200HX/HG/HE CPU Units This section provides information on the FINS commands that can be addressed to the CPU Units of CS-series and C200HX/HG/HE PLCs. Command List ..........Memory Area Designations .
Page 245: Command List
Command List Section 9-1 Command List The beginning portions of the command and response block up to the com- mand codes and the FCS and terminator have been omitted for simplicity, but must be added for actual transmission if not automatically generated for the transmission method being used.
Page 246: Word/Bit Addresses
Section 9-2 Memory Area Designations Memory area Data Data area address Address used in Memory No. of communications area code bytes 1st and 2nd 3rd byte bytes Timer Area/ Completion Flag TIM 000 to TIM 511 0000 to 01FF 00 to 00 Counter Area status CNT 000 to CNT 511...
Page 247: Memory Area Read
MEMORY AREA READ Section 9-3 9-2-2 Data Configuration The configuration of the various types of data that can be read or written is shown below. The number of bytes required for each type of data is also given. Flag or Bit Status (One 00: Bit is OFF (0) Byte) 01: Bit is ON (1)
Page 248: Memory Area Write
MEMORY AREA WRITE Section 9-4 Memory Areas The following area can be read (refer to page 224 Memory Area Designations for PLC word/bit address designations): Memory area Data Memory area No. of code bytes CIO, LR, HR, or AR Word contents area Timer/Counter Completion Flag status...
Page 249: Multiple Memory Area Read
MULTIPLE MEMORY AREA READ Section 9-5 The following data can be written (refer to page 224 Memory Area Designa- tions for the word/bit address designations): Memory area Data Memory area No. of code bytes CIO, LR, HR, or AR Word contents area Timer/Counter Word contents...
Page 250: Composite Registration Read
COMPOSITE REGISTRATION READ Section 9-6 Note Refer to page 226 Data Configurations for the various data configurations. COMPOSITE REGISTRATION READ Reads the memory areas according to the addresses specified with the COM- POSITE READ REGISTRATION command (01 11). Note 1. Although this command is addressed to the CPU Unit, it is actually pro- cessed by the DeviceNet Master Unit.
Page 251: Controller Data Read
CONTROLLER DATA READ Section 9-8 Command Block Command Read address Read address code Memory area code Memory area code 100 items max. for 2-byte data (see description above) Response Block Command Response code code Parameters Memory area code (command): The data area to read. Read address (command): The word/bit/flag to read.
Page 252: Controller Status Read
CONTROLLER STATUS READ Section 9-9 mation does not require 20 bytes, the remainder of the 20 bytes will be filled with spaces (ASCII 20). CONTROLLER STATUS READ Reads the status of the Controller. Command Block Command code Response Block Command Response code code...
Page 253 CLOCK READ Section 9-10...
Page 254: Fins Commands To Devicenet Master Units
SECTION 10 FINS Commands to DeviceNet Master Units This section provides information on the FINS commands that can be addressed to the DeviceNet Master Units. 10-1 Command List ..........10-2 RESET .
Page 255: Command List
Command List Section 10-1 10-1 Command List The beginning portions of the command and response block up to the com- mand codes and the FCS and terminator have been omitted for simplicity, but must be added for actual transmission if not automatically generated for the transmission method being used.
Page 256: Echoback Test
(ASCII 20). The Master Unit version will be “0200” for all PLCs. The following model data will be returned. CVM1 and CV-series PLCs:CVM1-DRM21-V1 CS-series and C200HX/HG/HE/HS PLCs:C200HW-DRM21-V1 10-4 ECHOBACK TEST Executes an echo test between the local node and a destination node.
Page 257 ERROR LOG READ Section 10-5 Response Block 10 bytes 10 bytes Command Response Max. no. of No. of No. of Error log Error log code code stored records stored records data data records (1 record) (1 record) Parameters Beginning record no. (command): Designates the beginning record number in a range of 0000 to 0013 (0 to 19 in decimal) (the first record is 0000).
Page 258: Error Log Clear
ERROR LOG CLEAR Section 10-6 10-6 ERROR LOG CLEAR Clears all error log records to all zeros. Note This command cannot be executed if any other device has the access right. Command Block Command format Response Block Command Response format code...
Page 259 ERROR LOG CLEAR Section 10-6...
Page 260: Sending Explicit Messages To Devicenet Devices By Other Manufacturers
Appendix A Sending Explicit Messages to DeviceNet Devices by Other Manufacturers FINS Command: EXPLICIT MESSAGE SEND (28 01) 1. EXPLICIT MESSAGE SEND will send an explicit DeviceNet message to the specified object and re- ceive a response. Command Block 152 bytes max. Command Class ID Instance ID...
Page 261 Error code (response): An error code defined by DeviceNet. Note 1. This command sends a DeviceNet-defined explicit message to an OMRON Special I/O Slave Unit or a Slave manufactured by another company and receives a response.
Page 262: Fins Command Response Codes
Refer to the operation manual for the device returning the response for details when troubleshooting the error. Note The CVM1-DRM21-V1 and C200HW-DRM21-V1 DeviceNet Master Units do not support communica- tions between networks, so the Relay Error Flag (bit 7 of the first byte) is always OFF.
Page 263 FINS Command Response Codes Appendix B Main code Sub- Probable cause Check point Remedy code 01: Local node error Local node not part of Net- Local node status in Add to Network. work network Token time-out, node Max. node address Set the local node’s node address address too large below the maximum node address.
Page 264 FINS Command Response Codes Appendix B Main code Sub- Probable cause Check point Remedy code 05: Routing error Routing error in control data Control data in Be sure the Unit is listed in the or routing tables. instruction or routing routing tables for CVM1 and CV- tables series PLCs, address only within...
Page 265 FINS Command Response Codes Appendix B Main code Sub- Probable cause Check point Remedy code 11: Parameter error A correct memory area Memory area code in Check the command’s memory code has not been used or command data area code and set the appropriate Expansion Data Memory is code.
Page 266 FINS Command Response Codes Appendix B Main code Sub- Probable cause Check point Remedy code 20: Read not possible 02 The data is protected. Execute the instruction again after issuing the PROGRAM AREA PROTECT CLEAR command. An attempt was made to File name Check the file name and either download a file that is being...
Page 267 FINS Command Response Codes Appendix B Main code Sub- Probable cause Check point Remedy code 22: Not executable in The mode is wrong (execut- Check the operating mode. current mode ing). Data links are active. Data link status Check the data link status before execution.
Page 268 FINS Command Response Codes Appendix B Main code Sub- Probable cause Check point Remedy code 25: Unit error Parity/checksum error Contents of memory Transfer correct data into memory. occurred because of incor- being processed rect data. I/O setting error (The regis- I/O Unit configuration Either change the actual configura- tered I/O configuration dif- tion to match the registered one, or...
Page 269 FINS Command Response Codes Appendix B Main code Sub- Probable cause Check point Remedy code 26: Command error The specified area is not Program area com- The program area is not protected, protected. This response mand protection so it isn’t necessary to clear protec- code will be returned if an tion.
Page 270: Node Address Settings Table
Appendix C Node Address Settings Table Each Slave’s node address is set in binary with pins 1 through 6 of the Slave’s DIP switch. There are some dif- ferences in the location and orientation of the DIP switches, but the node address is always set in binary. (0: OFF, 1: ON) DIP switch setting Node...
Page 271 Node Address Settings Table Appendix C...
Page 272: Connecting Another Company's Slaves
We recommend using the Configurator when connecting another company’s Slave to an OMRON Master. Connection when the EDS File Is Available The other company’s Slave can be treated just like an OMRON Slave by installing the EDS file in the OMRON Configurator.
Page 273 Connecting Another Company’s Slaves Appendix D • Produced Connection Size This is the amount of memory (usually expressed in bytes) occupied as input words. • Consumed Connection Size This is the amount of memory (usually expressed in bytes) occupied as output words. If the connection size is an even number of bytes, the number of occupied words is: (bytes ÷...
Page 274: Master Unit Device Profile
Data Specifications General data Compatible DeviceNet Specifications Volume I - Release 1.2 Volume II - Release 1.1 Vendor name OMRON Corporation Vendor ID = 47 Device profile name Communication Adapter Profile number = 12 Manufacturer catalog number Manual number (W267)
Page 275 Master Unit Device Profile Appendix E DeviceNet Object (0x03) Object class Attribute Not supported 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 6 MAC ID switch changed 7 Baud rate switch changed...
Page 276: Glossary
The DeviceNet uses CAN technology. configurator A device used to make system settings, read IDs, read/write parameters, read the network configuration, etc. OMRON provides a DeviceNet Configurator for OMRON Master Units. consumed connection The size in bytes of the data received through a connection.
Page 277 Revision History...
Page 278: Index
Index Numerics commands delivering commands through a network 7-segment display commands for C200HX/HG/HE PLCs meaning CLOCK READ COMPOSITE REGISTRATION READ CONTROLLER DATA READ CONTROLLER STATUS READ MEMORY AREA READ access right MEMORY AREA WRITE acquiring MULTIPLE MEMORY AREA READ releasing REGISTER COMPOSITE READ adaptors commands for CVM1 and CV-series PLCs...
Page 279 Index REGISTER COMPOSITE READ SINGLE FILE READ data areas SINGLE FILE WRITE See also Memory Areas STOP DeviceNet VOLUME LABEL CREATE/DELETE remote I/O communications commands for Master Units DeviceNet Configurator CONTROLLER DATA READ dimensions ERROR LOG CLEAR Master Units ERROR LOG READ CS-series, C200HX/HG/HE, and C200HS PLCs LOOP-BACK TEST CVM1 and CV-series PLCs...
Page 280 Index FALS instruction CVM1 and CV-series PLCs in asynchronous mode fatal error data CVM1 and CV-series PLCs in synchronous mode files minimum changing file names CS-series and C200HX/HG/HE/HS PLCs checking data CVM1 and CV-series PLCs in asynchronous mode comparing copying CVM1 and CV-series PLCs in synchronous mode creating/deleting volume labels I/O size mismatch...
Page 281 Index indicators CS-series and C200HX/HG/HE/HS PLCs CVM1 and CV-series PLCs Parameter Areas mounting clearing rotary switch comparing/transferring CS-series and C200HX/HG/HE/HS PLCs reading CVM1 and CV-series PLCs writing troubleshooting memory areas changing to PROGRAM mode designating addresses changing to RUN mode reading PLC memory address reading contents...
Page 282 Index enabled mode transferring I/O memory files Scan List Disabled Mode Flag Transmission Error Flag Scan List Operation Completed Flag troubleshooting Master Units Scan List Operation Error Flag status flags allocation C200HX/HG/HE/HS PLCs CS-series PLCs Units CVM1 and CV-series PLCs reading the model numbers of connected Units Communications Error Flag Communications Stoppage Cleared Flag...
Page 284: 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. W379-E1-03 Revision code The following table outlines the changes made to the manual during each revision. Page numbers refer to the previous version.
Page 285 Revision History...
Page 286 The Netherlands IL 60173-5302 U.S.A. Tel: (31)2356-81-300/Fax: (31)2356-81-388 Tel: (1) 847-843-7900/Fax: (1) 847-843-7787 © OMRON Corporation 2002 All Rights Reserved. OMRON (CHINA) CO., LTD. OMRON ASIA PACIFIC PTE. LTD. In the interest of product improvement, Room 2211, Bank of China Tower, No.

This manual is also suitable for:

C200hw-drm21-v1

Omron CVM1-DRM21-V1 Operation Manual

Quick Links

Troubleshooting

Need help?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Omron CVM1-DRM21-V1

Summary of Contents for Omron CVM1-DRM21-V1