CS-series DeviceNet Unit: CS1W-DRM21 CJ-series DeviceNet Unit: CJ1W-DRM21 Operation Manual Revised July 2001
iv
Notice: OMRON products are manufactured for use according to proper procedures by a qualified operator and only for the purposes described in this manual. The following conventions are used to indicate and classify precautions in this manual. Always heed the information provided with them. Failure to heed precautions can result in injury to people or damage to property. !DANGER !WARNING !Caution Indicates an imminently hazardous situation which, if not avoided, will result in death or serious injury.
Trademarks and Copyrights DeviceNet is a registered trademark of the Open DeviceNet Vendor Association, Inc. Windows, Windows 95, Windows 98, Windows Me, Windows NT, and Windows 2000 are registered trademarks of the Microsoft Corporation. Other product names and company names in this manual are trademarks or registered trademarks of their respective companies. The copyright of the DeviceNet Unit belongs to OMRON Corporation. OMRON, 2000 All rights reserved.
TABLE OF CONTENTS PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi 1 Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii 2 General Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii 3 Safety Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TABLE OF CONTENTS SECTION 5 Remote I/O Slave Communications . . . . . . . . . . . . . . . . . 121 5-1 Slave Remote I/O Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 5-2 Fixed Allocations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 5-3 User-set Allocations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 SECTION 6 Message Communications . . . . . .
About this Manual: This manual describes the installation and operation of CS1W-DRM21 DeviceNet Unit for SYSMAC CJ-series PLCs and the CJ1W-DRM21 DeviceNet Unit for SYSMAC CJ-series PLCs, and includes the sections described below. Please read this manual and all manuals for related products carefully and be sure you understand the information provided before attempting to install and operate the DeviceNet Unit. Be sure to read the precautions provided in the following section.
Manual Products @@ Contents Cat. No. CS1G/H-CPU SYSMAC CS/CJ Series -E CPU Units Communication ComCS1W-SCB21/41 Serial Communications mands Reference Manual Boards CS1W-SCU21 Serial Communications Unit Information on FINS and W342 Host Link commands that can be sent to CS/CJ-series CPU Units. CX-Net Operation Manual Information on setting and W362 monitoring networks, such as the use of routing tables.
PRECAUTIONS This section provides general precautions for using the DeviceNet Unit and related devices. The information contained in this section is important for the safe and reliable application of the DeviceNet Unit and Programmable Controller (PC) You must read this section and understand the information contained before attempting to set up or operate a DeviceNet Unit as part of a PC. 1 2 3 4 5 6 Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 Intended Audience 1 Intended Audience This manual is intended for the following personnel, who must also have knowledge of electrical systems (an electrical engineer or the equivalent). • Personnel in charge of installing FA systems. • Personnel in charge of designing FA systems. • Personnel in charge of managing FA systems and facilities. 2 General Precautions The user must operate the product according to the performance specifications described in the operation manuals.
Operating Environment Precautions 4 measure for such problems, external safety measures must be provided to ensure safety in the system. • When the 24-VDC output (service power supply to the PC) is overloaded or short-circuited, the voltage may drop and result in the outputs being turned OFF. As a countermeasure for such problems, external safety measures must be provided to ensure safety in the system. !WARNING The CPU Unit refreshes I/O even when the program is stopped (i.e., even in PROGRAM mode).
5 Application Precautions !Caution 5 The operating environment of the PC 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 PC System. Be sure that the operating environment is within the specified conditions at installation and remains within the specified conditions during the life of the system.
5 Application Precautions • Double-check all the wiring and connection of terminal blocks and connectors before mounting the Units. • Use crimp terminals for wiring. Do not connect bare stranded wires directly to terminals. • Observe the following precautions when wiring the communications cable. • Separate the communications cables from the power lines or high-tension lines. • Do not bend the communications cables. • Do not pull on the communications cables.
6 Conformance to EC Directives 6 Conformance to EC Directives 6-1 Applicable Directives • EMC Directives 6-2 Concepts EMC Directives OMRON devices that comply with EC Directives also conform to the related EMC standards so that they can be more easily built into other devices or machines. The actual products have been checked for conformity to EMC standards. (See the following note.
6 Conformance to EC Directives Ferrite Core (Data Line Filter): 0443-164151 (manufacturered by Fair-Rite Products Co., Ltd.) Impedance specifications 25 MHZ: 156 Ω 100 MHZ: 250 Ω 30 mm 13 mm 33 mm 29 mm 2. Wire the control panel with as thick and short electric lines as possible and ground to 100 Ω min. 3. Keep DeviceNet communications cables as short as possible and ground to 100 Ω min.
SECTION 1 Features and System Configuration This section provides an overview of the DeviceNet network, including features, specifications, and system configurations. 1-1 Overview of DeviceNet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1-1-1 Overall System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1-1-2 Applicable Units and DeviceNet Functions . . . . . . . . . . . . . . . . . . . 6 1-1-3 Masters . . . . . . . . . . . . . .
Section 1-1 Overview of DeviceNet 1-1 Overview of DeviceNet DeviceNet is a multi-bit, multi-vendor network that combines controls and data on a machine/line-control level and that conforms to DeviceNet open field network specifications.
Section 1-1 Overview of DeviceNet 1-1-1 Overall System Configuration DeviceNet Unit or DeviceNet Master Unit CS Series C200HZ/HX/HG/E/HS: CS1W-DRM21 C200HW-DRM21-V1 CJ Series , CVM1/CV Series: CJ1W- DRM21 CVM1-DRM21-V1 Photoelectric sensors, proximity sensors, limit switches, etc. Photoelectric sensors, proximity sensors, limit switches, etc. I/O Link Unit CQM1 Output Remote Adapter (used with Output Block) Output Terminal Solenoids, valves, etc. Solenoids, valves, etc.
Section 1-1 Overview of DeviceNet Configurator Features • Enables user-set allocations for remote I/O (choice of node address order, 2 area allocations, etc.). • Enables serial connection to the Programming Device Port of a PC. • Enables user settings for DeviceNet remote I/O communications connections. • Enables multiple Masters on a single PC. • Enables multiple Masters in a single network. Slave Features I/O Terminals • Provide general-purpose I/O via terminal blocks (M3).
Section 1-1 Overview of DeviceNet Temperature Input Terminals • Temperature data is input as binary data for 4 inputs. • Thermocouple and platinum resistance thermometer inputs are available. C200H I/O Link Units • Special I/O Slaves that mount to C200HX/HG/HE PCs and read/write data from the Master to the specified words in the CPU Unit. • Read and write areas specified for up to 512 bits each (32 words each). • Any memory area words can be read or written using DeviceNet explicit messages.
Section 1-1 Overview of DeviceNet 1-1-2 Applicable Units and DeviceNet Functions Remote I/O Master DeviceNet Unit (Master) CPU Unit Remote I/O communications DeviceNet Slaves Item Max. No.
Section 1-1 Overview of DeviceNet Remote I/O Slave (only Units Mounted in a PC) DeviceNet Unit (Master) CPU Unit IN area OUT area IN area OUT area Remote I/O communications DeviceNet CPU Unit DeviceNet Unit (Slave) Slaves Item Max. No.
Section 1-1 Overview of DeviceNet Message Communications Master Master RS-232C Interface Unit Communications Instructions Master Unit model CS Series CS1W-DRM21 CJ Series CJ1W-DRM21 CVM1, CV Series CS Series, C200HX/HG/HE Send Receive FINS commands SEND(192) RECV(193) CMND(194) CVM1-DRM21-V1 SEND(192) RECV(193) CMND(194) C200HW-DRM21-V1 None None IOWR C200HS --- Item Max. No.
Section 1-1 Overview of DeviceNet V1) or a CVM1/CV-series DeviceNet Master Unit (CVM1-DRM21-V1). Refer to 6-3 Using FINS Message Communications for details. Communications Software Switches and Communications Status Dedicated words in the CPU Unit are allocated for DeviceNet communications software switches and status.
Section 1-1 Overview of DeviceNet General-purpose Slaves (Communications Cable: Normal Square Connectors) Name Remote I/O Terminals with Transistors Appearance I/O points Model number 8 input points (NPN) DRT1-ID08 8 input points (PNP) DRT1-ID08-1 Remarks --- 16 input points (NPN) DRT1-ID16 16 input points (PNP) DRT1-ID16-1 8 output points (NPN) DRT1-OD08 --- 8 output points (PNP) DRT1-OD08-1 Remote I/O Terminals with Transistors and 3-tier Terminal Block 16 output points (NPN) DRT1-OD16 16
Section 1-1 Overview of DeviceNet Name Sensor Terminals Appearance I/O points 8 input/8 output points (PNP) Temperature Input Terminals Model number 16 input points (NPN) DRT1-HD16S Remarks Connected to photoelectric and proximity sensors with connectors DRT1-ND16S 4 thermocouple input DRT1-TS04T points (4 words) Thermocouple inputs Temperature resistance thermometer inputs 4 temperature resis- DRT1-TS04P tance thermometer input points (4 words) 4 input points (4 words) or 2 input points (2 word
Section 1-1 Overview of DeviceNet Waterproof and Environment-resistant Slaves (Communications Cable: Round Connectors) Name Appearance Waterproof Terminals I/O points Model number 4 input points (NPN) DRT1-ID04CL 4 input points (PNP) DRT1-ID04CL-1 8 input points (NPN) DRT1-ID08CL 8 input points (PNP) DRT1-ID08CL-1 4 output points (NPN) DRT1-OD04CL 4 output points (PNP) DRT1-OD04CL-1 Remarks Dust and drip-proof structure for environmental resistance (IP 67) XS2 Series connector system elimina
Section 1-1 Overview of DeviceNet MULTIPLE I/O TERMINAL Units Unit I/O points Words allocated in PC memory Input Communications Unit None Output Two sta- 0 words tus words Basic I/O Transistor 16 input 1 word Units Input Units points 0 words 16 input 1 word points 0 words 16 input 1 word points 0 words 16 input 1 word points 0 words 32 input 2 words points 0 words 16 output points 0 words 16 output points 0 words 16 output points 0 words 16 output points 0 words 32 output points 0
Section 1-1 Overview of DeviceNet Unit I/O points Words allocated in PC memory Input Special I/O Units (See note.
Section 1-2 DeviceNet Unit Features 1-1-5 DeviceNet Configurator Use version 2 of the DeviceNet Configurator for the CS1W-DRM21/CJ1WDRM21 DeviceNet Unit. Earlier versions of the DeviceNet Configurator do not support the CS1W-DRM21 DeviceNet Unit. Product name DeviceNet Configurator (Ver. 2) Model WS02-CFDC1-E Components Network connection to computer Installation disk (CD-ROM) Any of the following: • Serial connection • PCMCIA Card • ISA Board (See the table below.
Section 1-2 DeviceNet Unit Features Explicit Message Communications CS/CJ-series DeviceNet Unit Explicit message DeviceNet RS-232C Slave RS-232C Slave CS/CJ-series DeviceNet Unit Note Refer to 6-4 Sending Explicit Messages for details on remote I/O communications. FINS Message Communications CS/CJ-series DeviceNet Unit FINS message DeviceNet Slave Slave CS/CJ-series DeviceNet Unit Note Refer to 6-3 Using FINS Message Communications for details on FINS communications.
Section 1-2 DeviceNet Unit Features taneously. A Unit that is used as a slave supports fixed and user-set allocations. The maximum I/O for the slave function is 100 words. CS/CJ-series DeviceNet Unit (Master) Master PC DeviceNet CS/CJ-series DeviceNet Unit (Slave) Slave PC 64 nodes max. Note Refer to SECTION 5 Remote I/O Slave Communications for details.
Section 1-2 DeviceNet Unit Features CX-Programmer Programming and Monitoring of DeviceNet Slave PCs (Ver. 2.1 or Later) CX-Programmer Ver. 2.1 connected to a serial communications port on a DeviceNet PC can be used to remotely program and monitor other DeviceNet PCs (i.e., PCs with a CS/CJ-series DeviceNet Unit or a Programmable Slave).
Section 1-2 DeviceNet Unit Features Multiple PCs in a Single Network Multiple DeviceNet Units can be connected in a single network for message communications between PCs as well as for remote I/O communications between PCs and slaves in multiple groups. This feature allows a DeviceNet to be used as a common bus that can integrate all types of control with less wiring.
Section 1-2 DeviceNet Unit Features a DeviceNet Unit. (See Appendix D Memory Card Backup Function for more details.) CS/CJ-series DeviceNet Unit Configurator CPU Unit Memory Card File save File load Loads setup data to a DeviceNet Unit using a software switch in CIO Area of the CPU Unit. Note Refer to 7-2 Memory Card Backup Functions for details. Various Connection Methods Normal multi-drop, T-branch multi-drop (with up to three branches), and daisychain line connections are available.
Section 1-3 Specifications 1-3 Specifications 1-3-1 DeviceNet Unit Model Applicable PC CS Series Unit classification CPU Bus Unit CJ Series General Specifications Types of communications Model number • Remote I/O communications master (fixed CS1W-DRM21 or user-set allocations) • Remote I/O communications slave (fixed CJ1W-DRM21 or user-set allocations) • Message communications General specifications of the CS/CJ-series DeviceNet Unit conform to the general specifications for the SYSMAC CS/CJ-se
Section 1-3 Specifications Item Words allocated in the CPU Unit DeviceNet When remote I/O used as communi- a Master cations When used as a Slave Specification Fixed allocations User-set alloca- Any I/O memory (Set using the allocated DM Area words or Contions figurator.) Fixed allocations Fixed words in the CS/CJ-series DeviceNet Area in the CIO Area (one of three settings). User-set alloca- Any I/O memory words (Set in allocated DM Area words or Contions figurator.
Section 1-3 Specifications Item Remote I/O Slave allocation method master communications Specifications Fixed allocations Select one of the following fixed allocation areas using the Fixed Allocated Area Switches 1, 2, and 3 in the software switches in the allocated CIO Area words.
Section 1-3 Specifications Item Remote I/O master Max. No. of Slaves connected per DeviceNet Unit Specifications Fixed allocations User-set allocations 63 nodes By allocated DM Area words By Configurator Max. No.
Section 1-3 Specifications Item Remote I/O slave Allocation method Specifications Fixed allocations Select one of the following fixed allocation areas using the Slave Fixed Allocated Area Switches 1, 2, and 3 in the software switches in the allocated CIO Area words.
Section 1-3 Specifications Item Specifications Default settings • • • • • • Scan list: Not supported Master communications: Supported Slave communications: Disabled Remote I/O communications: Start Master fixed allocations: Fixed Allocation Area Setting 1 Slave fixed allocations: Fixed Allocation Area Setting 1 Data stored in non-volatile memory (EEPROM) in the DeviceNet Unit Saves the following data settings (same as the backup file on the Memory Card).
Section 1-3 Specifications Item Other functions Specifications Remote programming/monitoring functions A CX-Programmer connected to the serial communications port of a PC to which a CS/CJ-series DeviceNet Unit is mounted can remotely program and monitor DeviceNet slave PCs with a CS/ CJ-series DeviceNet Unit mounted. Either the peripheral port or built-in RS-232C port can be used with the Host Link or peripheral bus protocol. (Scheduled for CX-Programmer Ver. 2.1 or later) Note 1.
Section 1-3 Specifications Item Specifications Communications power supply voltage 11 to 25 VDC (supplied from the communications connector) Influence on CPU Unit cycle time 0.7 ms+0.001 x the number of words allocated Current consumption CS1W-DRM21: Communications power supply: 30 mA at 24 VDC, (supplied from the communications connector) Internal circuit power supply: 290 mA max.
Section 1-4 Comparison with Previous Models 1-4 Comparison with Previous Models The following table provides a comparison between the CS1W-DRM21 DeviceNet Unit and the C200HW-DRM21-V1 DeviceNet Master Unit used in a CS/CJ-series PC. Item C200HW-DRM21-V1 CS1W-DRM21/CJ1W-DRM21 Unit classification C200H Special I/O Unit Mounting position CPU Rack, C200H I/O Expansion Rack, CS- CPU Rack, CS/CJ-series Expansion Rack series Expansion Rack No.
Comparison with Previous Models Item Remote I/O communications Master Fixed allocations C200HW-DRM21-V1 Section 1-4 CS1W-DRM21/CJ1W-DRM21 C200H DeviceNet words in CIO Area 1,600 points (50 input words, 50 output words) CS/CJ-series DeviceNet words in CIO Area 2,048 points (64 input words, 64 output words) Output area: CIO 0050 to CIO 0099 Input area: CIO 0350 to CIO 0399 Select one of the following using the software switch.
Section 1-4 Comparison with Previous Models Item C200HW-DRM21-V1 Remote I/O communications Master Max. No.
Section 1-4 Comparison with Previous Models Item C200HW-DRM21-V1 CS1W-DRM21/CJ1W-DRM21 Starting and stopping remote Starts or stops remote I/O communications using the Configurator or the software switch from a Programming Device. communications during I/O communications Remote I/O communications Sets remote I/O communications start or stop when an error occurs in master communicawith a communications error tions (set on DIP switch on the front of the Master).
Section 1-5 Outline of the Configurator 1-5 Outline of the Configurator Allocations for remote I/O communications can be set in any order of node addresses from the Configurator. Users can also set remote I/O communications connections. Device (master/slave) registration, I/O allocations, and other operations are especially easy to perform because of graphic operations, including dragging and dropping icons. Any of the following methods can be used to connect the Configurator to DeviceNet.
Section 1-5 Outline of the Configurator Remote I/O master allocations (with creation of a scan list) and remote I/O slave allocations Setup functions Enabling or disabling master or slave function of CS/CJ-series DeviceNet Unit. Setting master device parameters except scan list parameters (i.e.
Section 1-5 Outline of the Configurator Item Main functions Setup functions Specification Master device parameter settings for OMRON’s Master • Remote I/O master allocations (with a scan list) The node address order can be set as desired. Two output blocks and two input blocks can be allocated. (See note.
Section 1-6 Basic Operating Procedures 1-6 1-6-1 Basic Operating Procedures Network Installation Procedure Note For details on the network installation procedure, refer to the DeviceNet Operation Manual (W267). Only a general description is given here. Determine a suitable baud rate for the system. (1) (2) Determine the node arrangement, the wiring configuration, and the cable lengths. A) Restrictions on lengths of trunk lines and branch lines and total drop line length.
Section 1-6 Basic Operating Procedures Node address (Pins 1 to 6) Baud rate (Pins 7 and 8) Etc. 3. Mount the Master and wire the network. Treat as a CPU Bus Unit. Can mount to a CPU Rack or Expansion Rack. With fixed allocations: 3 Units max. With user-set allocations: 16 Units max. 4. Connect a Programming Device to the PC and turn ON the power supply to the PC. 5. Generate the I/O tables. Note 1. A slave may not go online if the communications power supply is turned ON after the slave is turned ON. 2.
Section 1-6 Basic Operating Procedures message communications may not be possible unless the DeviceNet Unit is registered in the local network table. 1-6-4 Procedures Prior to Starting Communications Using the Master Function To use the master function, the Master Enable Switch (word n, bit 06) must be turned ON from a Programming Device. Enable master communications through CS1W-DRM21 properties if you are using a Configurator. Note 1.
Section 1-6 Basic Operating Procedures 3. Check Unit Status 2 (word n+11, bit 03) from a Programming Device connected to the CPU Unit to see if the master function is ON (enabled). If it is enabled, skip step 4 below and proceed to step 5. 4. If the master function is OFF (disabled), turn ON the Master Enable Switch (word n, bit 06) from a Programming Device connected to the CPU Unit. Note Execute this only when master communications are turned OFF.
Section 1-6 Basic Operating Procedures 2. Check Unit Status 2 (word n+11, bit 07) from a Programming Device connected to the CPU Unit to see if the slave function is OFF (disabled). If it is disabled, skip step 3 below and proceed to step 4. 3. If slave communications are enabled, turn ON the Slave Stop Switch (word n+1, bit 07). 4. Turn ON the Slave Fixed Allocation Area Settings 1 to 3 Switches (word n+1, bits 8 to 10). 5.
Section 1-6 Basic Operating Procedures 4. Switch the CPU Unit to RUN mode. Slave remote I/O communications will begin. Message Communications Only (Neither Master nor Slave Function Used) The DeviceNet Unit does not have to be registered in the scan list if it is only used for message communications. Message communications (send and receive) can be executed with both master and slave communications disabled.
Section 1-7 List of Usage Methods by Purpose 1-7 List of Usage Methods by Purpose Situation Design Allocating any words for remote I/O Action 108 In order of node Set using the allocated DM Area words. addresses (Master User Allocations Setup Table and Allocation Size Setup Table) Note Allocations using allocated DM Area words: Order of node addresses and two blocks, OUT 1 and IN 1. Not in order of node addresses 42 Page Set using the configurator.
Section 1-7 List of Usage Methods by Purpose Situation Operation Action Page Stopping remote I/O communica- Stop communications using the Configurator or the 62 tions with all Slaves Remote I/O Communications Stop Switch in the allocated CIO Area words. Using a scan list in remote I/O communications (fixed allocations) Turn ON the Scan List Enable Switch in the allocated CIO Area words.
SECTION 2 Nomenclature and Installation This section describes the nomenclature and installation of the DeviceNet Unit. 2-1 2-2 Nomenclature and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 2-1-1 Nomenclature and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 2-1-2 Status Indicators: MS and NS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 2-1-3 Seven-Segment Display . . . . . . . . . . . . . . . . . . . . . . . .
Section 2-1 Nomenclature and Functions 2-1 2-1-1 Nomenclature and Functions Nomenclature and Functions CS1W-DRM21 DRM21 CS MS Indicators NS 6543 DCB UNIT No. 210FE A987 32 65 4 32 10 9 X101 87 87 NODE ADR 1 0 9 Unit No. switch This switch sets the unit number of the DeviceNet Unit as a one-digit hexadecimal value. X100 65 4 1 2 3 4 1 DR0 2 DR1 3 ESTP 4 HOLD Node address switches These switches set the node address as a two-digit decimal value.
Section 2-1 Nomenclature and Functions 2. Two-digit, 7-segment display MS 1. Status indicators NS 3. Dot indicators 2-1-2 Status Indicators: MS and NS The MS (Module Status) indicator indicates the status of the node itself and the NS (Network Status) indicator indicates the status of the network. The MS and NS indicators can be green or red and they can be OFF, ON, or flashing (alternating 0.5-s ON and 0.5-s OFF.) The following table shows the meaning of these indicator conditions.
Section 2-1 Nomenclature and Functions 2-1-3 Seven-Segment Display In addition to the MS and NS indicators, DeviceNet Units have a 2-digit, 7segment display that normally indicates the master node address. When an error occurs, the display will alternate between the error code and the node address of the faulty slave. There are dot indicators at the lower-right corner of each digit. The left dot indicator shows whether or not the master is operating and whether the scan list is enabled or disabled.
Section 2-1 Nomenclature and Functions The following diagram shows the alternating error code/ node address display. OFF (0.1 s) OFF (0.3 s) Faulty slave's node address (1 s) Error code (1 s) OFF (0.1 s) Error code (1 s) OFF (0.3 s) Faulty slave's node address (1 s) OFF (0.1 s) OFF (0.3 s) Master's node address (1 s) OFF (0.3 s) Master's error code (1 s) If there is an error at the DeviceNet Unit.
Section 2-1 Nomenclature and Functions Note 1. The node address is set to 63 at the factory. 2. Any node address from 0 through 63 can be set as long as it hasn’t been set on another slave node. 3. If the node address is the same as one set on another node, a node address duplication error will occur and it won’t be possible to start up network communications. 4. Node address 0 cannot be used for FINS message communication. Use a node address other than 0 for FINS message communication.
Section 2-2 Installing the DeviceNet Unit Continue/Stop Remote I/O Communications When the DeviceNet Unit is used as a master, pin 3 is used to set whether or not communications will stop after a communications error. Pin 3 Function OFF Continue communications. ON Stop communications. If pin 3 is ON, remote I/O communications will be stopped if one of the following errors occurs.
Section 2-2 Installing the DeviceNet Unit • In the CS-series, up to 16 Units can be mounted to the CS1W-BC CPU Backplane or CS1W-BI 3 Expansion CPU Backplane. @@ @@3 • In the CJ-series, up to 16 Units can be mounted to the CPU Unit or Expansion Unit (but no more than 10 Units on either). 2-2-2 Mounting CS-series Mount the DeviceNet Unit to the Backplane using the following procedure. 1,2,3... 1. Hook the claw on the bottom of the Unit onto the Backplane. Claw Backplane 2.
Section 2-2 Installing the DeviceNet Unit Note When mounting the Unit, provide the clearance shown below to facilitate easy mounting or dismounting. Duct 20 mm min. Backplane 20 mm min. Duct Philips screwdriver CJ-series 1. Carefully align the connectors to mount the DeviceNet Unit. Connectors PA205R POWER RUN DRM21 INH PRPHL PROGRAMMABLE CONTROLLER MS NS COMM OPEN L1 AC100-240V L2/N 4 PERIPHERAL RUN OUTPUT AC240V DC24V PORT 2.
Section 2-2 Installing the DeviceNet Unit • Provide separate conduits or ducts for the I/O lines to prevent noise from high-tension lines or power lines. • Leave the label attached to the Unit when wiring. Removing the label may result in malfunction if foreign matter enters the Unit. • Remove the label after the completion of wiring to ensure proper heat dissipation. Leaving the label attached may result in malfunction. CS1W-DRM21 Remove the label after wiring. CJ1W-DRM21 Remove the label after wiring.
Section 2-2 Installing the DeviceNet Unit External Dimensions CS1W-DRM21 13.7 35 DRM21 101 CS MS NS 6543 EDCB UNIT No. 210F A987 32 87 X101 65 4 1 2 3 4 130 88 109 87 32 NODE ADR 1 0 9 X100 65 4 1 DR0 2 DR1 3 ESTP 4 HOLD ON 35 7 12 15 8 These diagrams show the dimensions of the DeviceNet Unit. Refer to the CS1 Series CPU Unit Operation Manual (W339) or the CJ Series CPU Unit Operation Manual (W393) for the dimensions of the Unit when it is mounted to the Backplane.
SECTION 3 Allocated CIO and DM Words This section describes the words allocated to the DeviceNet Unit in the CIO Area and DM Area. These words both enable controlling the DeviceNet Unit and accessing Unit and network status. 3-1 3-2 3-3 Overview of Word Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 3-1-1 Allocated CIO Area Words. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 3-1-2 Allocated DM Area Words . . . . . . . . . . . . . . . . . .
Section 3-1 Overview of Word Allocations 3-1 Overview of Word Allocations The words shown in the following diagram are allocated according to the unit number setting. For each Unit, there are 25 words allocated in the CIO Area and 100 words allocated in the DM Area.
Section 3-1 Overview of Word Allocations 3-1-1 Allocated CIO Area Words Software switches, DeviceNet Unit status, and error data are allocated in the CIO Area according to the unit number, as shown below. Software switches are bits used as commands from the CPU Unit to the DeviceNet Unit to enable executing Unit functions.
Section 3-2 Allocated CIO Area Words 3-2 Allocated CIO Area Words Data is stored at the offset positions shown in the figure below starting from the first word allocated to the Unit in the CIO Area.
Section 3-2 Allocated CIO Area Words • Unit status area 2 (word n+11) • Master Status 1 (word n+12) Word n [n = CIO 1,500 + (25 x unit number)] Bit 00 01 Name Status Scan List Enable Switch OFF→ ON User OFF Unit OFF→ ON User OFF Unit Scan List Clear Switch Controlled by Unit operation Operation conditions CPU Mas- Scan list ter Unit oper- func- status ating tion mode ProEnDisgram abled abled mode Enables the scan list with fixed allocations.
Section 3-2 Allocated CIO Area Words Bit 02 Name Status Remote I/ OFF→ ON O Communications Start Switch OFF 03 04 Remote I/O OFF→ Communi- ON cations OFF Start Switch Remote I/ OFF→ ON O Communications Stop Switch OFF 05 62 Reserved --by system Controlled by User Unit User Unit User Unit --- Unit operation Operation condi- Default tions setting CPU Mas- Scan list ter Unit oper- func- status ating tion mode --En--None abled Starts remote I/O communications. Note 1.
Section 3-2 Allocated CIO Area Words Bit 06 07 08 Name Master Enable Switch Master Stop Switch Master Fixed Allocation Setting 1 Switch 09 Master Fixed Allocation Setting 2 Switch 10 Master Fixed Allocation Setting 3 Switch Status OFF→ ON Controlled by User OFF OFF→ ON Unit User OFF OFF→ ON Unit User OFF OFF→ ON Unit User OFF OFF→ ON Unit User OFF Unit Unit operation Enables master communications. (The Unit automatically restarts.
Section 3-2 Allocated CIO Area Words Bit 11 12 Name Status Master User-set Allocations Switch OFF→ ON User OFF Unit OFF→ Temporary Set- ON ting Switch for Communications Cycle Time OFF 13 64 Commu- OFF→ nications ON Cycle Time Setting Switch OFF Controlled by User Unit User Unit Unit operation Operation conditions CPU Mas- Scan list ter Unit oper- func- status ating tion mode En--ProReads setup data from the Master User Allocations gram abled Setup Table (words m+1 to m+7) in the DM Ar
Section 3-2 Allocated CIO Area Words Bit 14 Name Status Communications Cycle Time Reference Table Clear Switch OFF→ ON User OFF Unit 3-2-2 Controlled by Unit operation Clears data in the Communications Cycle Time Reference Table (words m+15 to m+18). The data that is cleared will be updated with new data. Returns to OFF after the data in the Communications Cycle Time Reference Table (words m+15 to m+18) has been cleared.
Section 3-2 Allocated CIO Area Words Bit Name Status Controlled by Unit operation Operation conditions Default setting CPU Slave Unit funcoper- tion ating mode 06 Slave Enable Switch OFF→ ON 07 Slave Stop OFF→ Switch ON OFF OFF 66 User Enables slave communications. (The Unit automatically Program restarts.) To use fixed allocations, turn this switch ON after turning mode ON a Slave Fixed Allocation Setting Switch (word n+1, bits 08 to 10).
Section 3-2 Allocated CIO Area Words Bit Name Status Controlled by Unit operation Operation conditions Default setting CPU Slave Unit funcoper- tion ating mode 08 OFF→ Slave Fixed Allo- ON cation Setting 1 Switch OFF 09 OFF→ Slave Fixed Allo- ON cation Setting 2 Switch 10 OFF→ Slave Fixed Allo- ON cation setting 3 switch OFF OFF User ProAllocates the following words to the slave.
Section 3-2 Allocated CIO Area Words Bit Name Status Controlled by Unit operation Operation conditions Default setting CPU Slave Unit funcoper- tion ating mode 11 User Reads setup data from the Slave User Allocations Setup ProTable in the DM Area and registers slave user-set alloca- gram mode tions. Once registered, the Unit will operate with slave user-set allocations regardless of whether the power is turned OFF and back ON again until slave communications are disabled (i.e.
Section 3-2 Allocated CIO Area Words Bit 15 Name Status Unit Setup OFF→ ON File Backup Switch OFF Controlled by Operation conditions CPU Mas- Scan Slave list functer Unit oper- func sta- tion ating tion tus mode User Writes user settings (scan list, communica- --tions cycle time settings, etc.) as a file on the Memory Card in the CPU Unit. See 7-2 Memory Card Backup Functions for details. Note Files can only be backed up with the scan list enabled.
Section 3-2 Allocated CIO Area Words Bit15 Bit14 Bit13 Bit12 Bit11 Bit10 Bit09 Bit08 Bit07 Bit06 Bit05 Bit04 Bit03 Bit02 Bit01 Bit00 n+6 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00 n+7 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 n+8 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 n+9 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 Remote I/O communications will restart if a user turns OFF a bit that is ON.
Section 3-2 Allocated CIO Area Words 3-2-5 Unit Status 1 (Word n+10) Word n+10 [n = CIO 1,500 + (25 x unit number)] Bit 00 01 Name Unit Error Flag Master Function Error Flag Status Controlled by Unit operation ON Unit Displays DeviceNet Unit operating errors. This bit turns ON if any bit from 01 to 15 in Unit Status 1 turns ON.
Section 3-2 Allocated CIO Area Words Bit 07 08 Name Network Power Error Flag Send Timeout Flag Status Controlled by Unit operation ON Unit Indicates that there is no power from the network power supply. Note Remote I/O communications stop if DIP switch pin 3 (remote I/O communications stop/continue setting for a communications error) on the front panel is ON (stop). OFF Unit Indicates that the error has not occurred or turns OFF when the network power supply has restarted.
Section 3-2 Allocated CIO Area Words Bit 01 Name Status Remote I/O ON Communications Flag OFF Controlled by Unit operation Unit Indicates that remote I/O communications are being performed for the master function. Normally, the Unit will perform remote I/O communications automatically. Note This bit only indicates the start of remote I/O communications, and does not indicate whether data has actually been exchanged with slaves.
Section 3-2 Allocated CIO Area Words 3-2-7 Master Status 1 (Word n+12) Word n+12 [n = CIO 1,500 + (25 x unit number)] Bit 00 01 02 Name Verification Error Flag Structure Error Flag Status Controlled by Unit operation ON Unit Indicates that the data in the slave registered in the scan list is different from the data from the actual slave. It occurs with the scan list enabled. OFF Unit Indicates that a verification error has not occurred or turns OFF when a verification error is cleared.
Section 3-2 Allocated CIO Area Words Bit Name Status Unit operation Unit Indicates that an error has occurred in one of the following operations: • Fixed Allocation Setting 1 (word n, bit 08) • Fixed Allocation Setting 2 (word n, bit 09) • Fixed Allocation Setting 3 (word n, bit 10) Once this bit turns ON, it will remain ON until the operation is successfully completed. OFF Unit Indicates that the error has not occurred. The bit turns OFF when the operation is successfully completed.
Section 3-2 Allocated CIO Area Words 3-2-9 Slave Status 1 (Word n+14) Word n+14 [n = CIO 1,500 + (25 x unit number)] Bit Name Status Controlled by Unit operation 00 to 01 Reserved by --system --- --- 02 Remote I/O ON Communications Error OFF Flag for OUT 1/ IN 1 Unit Indicates that a communications error has occurred in the OUT 1/IN 1 slave I/O connection. Unit Indicates that a remote I/O communications error has not occurred or turns OFF when a remote I/O communications error is cleared.
Section 3-2 Allocated CIO Area Words Bit 11 Name COS Send Failed Flag Status Controlled by Unit operation ON Unit Indicates that an attempt was made to send COS to a Master using the Slave COS send switch (Slave COS Send Switch in n+1) in Software Switches 2, but the transmission failed. The following may cause the failure of COS signal transmission. • A COS connection was not established with a master. • Bus OFF error occurred. • A network power error occurred. • A send timeout occurred.
Section 3-2 Allocated CIO Area Words 3-2-10 Slave Status 2 (Word n+15) Word Bit 15 Bit 08 Bit 07 Bit 00 Slave I/O Allocation Status n+15 Master Node Addresses Master Node Address This indicates the node address of the remote master for slave communications. Name Range Master Node Address Slave I/O Allocation Status Details 0000 to 003F Hex (0 to 63) This information is valid when the Remote I/O Communications Flag (word n+14, bit 14 or 15) is ON in Slave Status 1.
Section 3-2 Allocated CIO Area Words 3-2-12 Normal Slave Table (Words n+20 to n+23) This table indicates the slaves that are communicating normally with the master. The bits correspond to node addresses. The bits for slaves for which normal I/O connections have been made are turned ON in this table. These are not flags to show the remote I/O communications status.
Section 3-2 Allocated CIO Area Words Bit Name Status Controlled by C200HWDRM21-V1 status Details and CS1W-DRM21 status 03 Configuration Error Flag ON/OFF Unit Configuration Error Flag This bit turns ON if any of the following flags turn ON: • Routing Table Error Flag (word n+10, bit 12) • Invalid Message Timer List Flag (word n+10, bit 13) • Invalid Scan List Data Flag (word n+12, bit 04) • Remote I/O Refresh Error Flag (word n+12, bit 05) Note The C200HW-DRM21-V1 does not support slave communic
Section 3-3 Allocated DM Area Words 3-3 Allocated DM Area Words Data is stored at the offset positions shown in the figure below starting from the first word allocated to the Unit in the DM Area.
Section 3-3 Allocated DM Area Words Word m Name Communications Cycle Time Setting Bit 15 Bit 00 Communications cycle time setting (ms) Range Details 0000 to 01F4 Hex Sets the communications cycle time in milli(0 to 500) seconds. Setting range: 0 to 500 ms If this bit is set to 0, the optimum time calculated by the Unit will be used. If a value higher than 500 ms is set, then the Unit will operate at 500 ms.
Section 3-3 Allocated DM Area Words Note Make sure the CPU Unit is in PROGRAM mode and the master function is enabled before you set these values. Name OUT block 1 area Range See Areas and Word Ranges. Details Specifies the OUT block area. The OUT block is not allocated when set to 00 Hex. First word in OUT block 1 Specifies the first word for the OUT block. IN block 1 area Specifies the IN block area. The IN block is not allocated when set to 00 Hex.
Section 3-3 Allocated DM Area Words Setting Results Code 3-3-3 Description Details 0000 Hex Completed normally --- 1101 Hex No area • Incorrect area setting. • The allocated size in the allocation size setup table is 0. 1103 Hex Address range specifi- The first word is outside the setting range. cation error 110C Hex Parameter error • The OUT or IN size in the allocation size setup table exceeds 200 bytes. • Both the OUT and IN blocks are set for no allocations. • No slaves are allocated.
Section 3-3 Allocated DM Area Words Setting Example The following example shows the allocation when the size (bytes) for OUT block 1 and IN block 1 is set in the allocation size setup table using the specified values.
Section 3-3 Allocated DM Area Words Name Range Slave OUT 1 area First word in the Slave OUT 1 area OUT 1 area size Details See Areas and Word Ranges. Specifies the OUT 1 area. The OUT 1 area is not available if this is set at 0. 00 to C8 Hex (0 to 200 bytes) Specifies the size of the OUT 1 area in bytes. The OUT 1 area is not allocated when set to 00 Hex. Specifies the first word in the OUT 1 area. See Areas and Word First word in the Slave IN 1 Ranges. area Specifies the IN 1 area.
Section 3-3 Allocated DM Area Words 3-3-5 Communications Cycle Time Reference Table This table can be used to access the present, maximum and minimum communications cycle times. All the values in this table are cleared from the Unit and the maximum and minimum values are updated with new values when the Communications Cycle Time Reference Table Clear Switch (word n, bit 13) is turned ON.
Section 3-3 Allocated DM Area Words Ranges Name Range Details See Areas and Word Ranges. Shows the area. No. of bytes in OUT block 1/2 0000 to 03E8 Hex (0 to 1,000 bytes) Shows the block size in bytes. The OUT block has not been allocated if this is set at 00 Hex. IN block 1/2 area See Areas and Word Ranges. Shows the area. 0000 to 03E8 Hex (0 to 1,000 bytes) Shows the block size in bytes. The OUT block has not been allocated if this is set at 00 Hex.
Section 3-3 Allocated DM Area Words Note OUT2 is not used. Ranges Name Range OUT 1/2 area Details See Areas and Word First word in the OUT block Ranges. 1/2 Shows the area. OUT 1/2 area size 00 to C8 Hex (0 to 200 bytes) Shows the area by size in bytes. IN 1/2 area See Areas and Word Ranges. Shows the area. 00 to C8 Hex (0 to 200 bytes) Shows the block size in bytes. First word in the IN blocks1/2 IN 1/2 area size Shows the first word for the area. Shows the first word for the area.
Section 3-3 Allocated DM Area Words Bit 03, 11 Name Status ON Slave Remote I/O Communications Error Flag Indicates that an error has occurred in remote I/O communications with the Slave. This bit turns ON if a timeout occurs in at least one connection with multiple connections set. This error occurs with the scan list enabled or disabled. Unit Indicates that a remote I/O communications error has not occurred or turns OFF when a remote I/O communications error is cleared.
SECTION 4 Remote I/O Master Communications This section describes the remote I/O communications performed as a DeviceNet master by the Devicenet Unit. 4-1 Master Remote I/O Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 4-1-1 Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 4-1-2 Remote I/O Master Specifications . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 4-1 Master Remote I/O Communications 4-1 Master Remote I/O Communications Remote I/O communications are used to automatically transfer data between slaves and the CPU Unit without any special programming in the CPU Unit under which the Master Unit is mounted. Master Communications CS/CJ-series DeviceNet Unit (master) CS/CJ-series CPU Unit Remote I/O communications DeviceNet Slaves Note 1.
Section 4-1 Master Remote I/O Communications Fixed Allocations Any one of the three areas below can be specified as the words allocated in the CIO Area for fixed allocations. The output (OUT) block and the input (IN) block are allocated strictly in order of node addresses in one of the areas shown below. CS/CJ Series OUT block 1 CIO 3200 CIO 3201 CIO 3262 CIO 3263 IN block 1 CIO 3300 CIO 3301 CIO 0362 CIO 0363 CIO 3400 OUT block 2 CIO 3401 CIO 3462 CIO 3463 Select one.
Section 4-1 Master Remote I/O Communications The OUT and IN blocks will be allocated in order of slave node addresses. Each block is a maximum of 500 words. CPU Unit Specified in allocated DM words Ascending order starting from address 0 Address OUT block 1 To Slaves Address IN block 1 Ascending order starting from address 0 Address From Slaves Address Each address is allocated at least one byte (rightmost).
Section 4-1 Master Remote I/O Communications 4-1-2 Remote I/O Master Specifications Item Slave allocation methods Specifications Fixed allocations Select one of the following fixed allocation areas using the Fixed Allocated Area Switches 1, 2, and 3 in the software switches in the allocated CIO Area words.
Section 4-1 Master Remote I/O Communications Item Specifications 2,048 pts (64 input words, 64 output words) Max. No.
Master Remote I/O Communications 4-1-4 Section 4-1 Procedure for Using Remote I/O Master Fixed Allocations for Remote I/O 1,2,3... 1. Turn ON the communications, slave, and PC power supplies. Note Turn ON the communications power supply prior to turning ON the slave power supply or the slaves may not go online. 2. Switch the CPU Unit to PROGRAM mode. 3. Turn ON the Master Enable Switch (word n, bit 06). (The master will remain enabled even if the power is turned OFF and back ON again.
Master Remote I/O Communications Section 4-1 3. Turn ON the Master Enable Switch (word n bit 06). (The master will remain enabled even if the power is turned OFF and back ON again.) Note Execute this only when master communications are turned OFF. (If the Master Enable Switch is turned ON when master communications are enabled, a Unit error will occur and a C2 error will be displayed on the 7-segment display on the front panel.) 4.
Section 4-2 Scan List nect/Connect Switch for that slave (words n+6 to n+9). This can be done when a slave is replaced or to register a slave in the scan list in preparations to connect it to the network at a later time. The Disconnect/Connect Switches, however, are cleared when the power supply is turned OFF, so the bit must be turned back ON from the ladder program after the power turns ON in order for it to remain effective. 2. Use Configurator Ver. 2.10 or later for the CJ1W-DRM21.
Section 4-2 Scan List Creating the Scan List The way that a scan list is prepared varies with the allocation method as shown below. Fixed allocations With the CPU Unit in PROGRAM mode: 1. Turn ON the one of the Master Fixed Allocation Setting 1 Switches (1 to 3). 2. Turn ON the Scan List Enable Switch. Note User-set allocations User-set allocations through the allocated DM through the Configurator Area words area With the CPU Unit in PROGRAM mode, turn ON the Master User Allocations Setup Switch.
Section 4-3 Fixed Allocations you disable the scan list with a Master Unit that is set for user-set allocations. Particularly when multiple Master Units are connected to a single network, communications will not be performed successfully if even one Master Unit on the network is operating with the scan list disabled. Once the list is disabled, the user-set allocations data registered in the Master Unit is lost.
Section 4-3 Fixed Allocations Note More than one Master Unit can be included in a single PC with fixed allocations, as shown below (3 Units max.). Master Unit Master Unit Slave Slave 4-3-2 Procedure Step 1: Place the CPU Unit in PROGRAM mode. Step 2: Turn ON the If the master communications have been disabled (if Master Function Enable Master Enable Switch Flag (word n+11, bit 03) is OFF), turn ON the Master Enable Switch (word n, bit 06) to enable master communications.
Section 4-3 Fixed Allocations Fixed Allocations Area 1 OUT blocks are allocated to slaves from CIO 3200 to CIO 3263 and IN blocks are allocated to slaves from CIO 3300 to CIO 3363.
Section 4-3 Fixed Allocations Fixed Allocations Area 3 OUT blocks are allocated to slaves from CIO 3600 to CIO 3663 and IN blocks are allocated to slaves from CIO 3700 to CIO 3763.
Section 4-3 Fixed Allocations 4-3-3 Changing System Components The scan list must be cleared in the following situations: • Adding a slave • Removing a slave • Changing a node address Turn OFF the Scan List Clear Switch (word n, bit 01) to clear the scan list. Remote I/O communications will be performed with the scan list disabled using fixed allocations in the fixed allocations area that was used the last time the list was disabled.
Section 4-3 Fixed Allocations Resulting Slave Allocation OUT area 1 Node address: Pts 0: 0 pts 1: 8 pts CIO Allocation disabled Address 1 Address 3 Allocation disabled Address 4 5: 16 pts Address 5 Address 6 Address 6 Allocation disabled Allocation disabled Allocation disabled Allocation disabled Not used 6: 32 pts 7: None 8: 0 pts 9: None 10: None 11: None 12: None to IN area 1 Node address: Pts CIO 0: 8 pts 1: 0 pts 2: 16 pts 3: 0 pts 4: 8 pts 5: 16 pts 6: 0 pts 7: None 8: 64 pts 9: None 10: None
Section 4-4 User-set Allocations 4-4 User-set Allocations With a CS/CJ-series DeviceNet Unit, remote I/O communications slaves can be allocated in any area (CIO, WR, HR, DM, or EM) using one of the following methods.
Section 4-4 User-set Allocations • The first bit for node allocations is always bit 00 when setting allocations with the allocated DM Area words, but can be either bit 00 or bit 08 with the Configurator. (Allocations for slaves with two bytes or more cannot start at bit 08. Setting through the Allocated DM Area Words (Master User Allocations Table) All slaves are allocated words in order of node addresses in two blocks: OUT block 1 and IN block 1. Addresses are in ascending order.
Section 4-4 User-set Allocations Procedure Step 1: Turn ON the Master Enable Switch Make sure that master communications have disabled by checking to see if Master Enable Function Flag (word n+11, bit 03) is OFF and then turn ON the Master Enable Switch (word n+14, bit 06) to enable master communications. Once master communications have been enabled by turning this switch ON, they will remain enabled even if the power is turned OFF and back ON again.
Section 4-4 User-set Allocations l is the first word in the Allocation Size Setup Table and is specified at words m+5 and m+6 08 07 00 Bit 15 Node address 0 OUT size (bytes) Node address 0 IN size (bytes) I+0 I+1 Node address 1 IN size (bytes) Node address 1 OUT size (bytes) to to I+62 Node address 62 OUT size (bytes) Node address 62 IN size (bytes) I+63 Node address 63 OUT size (bytes) Node address 63 IN size (bytes) Step 4: Turn ON the Slave User Allocations Switch Turn ON the Slave User alloc
Section 4-4 User-set Allocations 4. Multiple masters cannot share the same slave. Master Master Slave 5. Be sure to use user-set allocations and operate the Master Unit with the scan list enabled if multiple masters are connected to a single network. Communications will not be possible if there is more than one master with the scan list disabled connected to a network.
Section 4-4 User-set Allocations Allocation Size Setup Table OUT sizes specified in the leftmost byte IN sizes specified in the rightmost byte Address 0 OUT: 2 (bytes) Address 0 IN: 0 (bytes) Address 1 OUT: 1 (bytes) Address 2 OUT: 2 (bytes) Address 1 IN: 1 (bytes) Address 2 IN: 2 (bytes) Address 3 OUT: 0 (bytes) Address 4 OUT: 0 (bytes) Address 5 OUT: 20 (bytes) Address 3 IN: 1 (bytes) Address 4 IN: 0 (bytes) Address 5 IN: 20 (bytes) Resulting Slave Allocations OUT area 1 Address 0 Not used Addres
Section 4-4 User-set Allocations Setting through the Configurator Slaves can be allocated words in any order for the following blocks: OUT block 1, OUT block 2, IN block 1, and IN block 2.
Section 4-4 User-set Allocations Procedure Step 1 Set the area, start word, and words allocated for each block using the Configurator. Step 2 Allocate words to all node addresses in each block as shown below using the Configurator.
Section 4-4 User-set Allocations d) The start bit for node addresses can be bit 00 or bit 08. If it is bit 08 however, 2 or more bytes cannot be allocated as shown below. Start byte e) Multiple masters cannot share the same slave. Master Master Slave You can determine whether there are duplicate node addresses in the I/O allocations (scan lists) that were created simply by conducting a master parameter file duplicate check from the Configurator.
Starting and Stopping Remote I/O Communications Section 4-5 Configurator Setting Methods Refer to the DeviceNet Configurator Operation Manual (W382) for setting methods. 4-5 4-5-1 Starting and Stopping Remote I/O Communications Starting Remote I/O Communications Remote I/O communications start automatically after the power is turned ON or the Unit is restarted. The I/O Data Communications Flag (word n+12, bit 15) is turned ON when remote I/O communications is started with at least one slave.
Example of Ladder Programming for Remote I/O Communications Section 4-6 I/O Data Communications Unit Error Flag Flag (word n+12, bit 15) (word n+10, bit 00) Slave I/O processing Note Even if there is a communications error with the slave, the slave input data is saved in the allocated area. To prevent operating errors, make the ladder program so that no slave I/O processing will occur when the Unit Error Flag (word n+10, bit 00) is ON.
Section 4-7 Errors that May Occur in Remote I/O Communications 4-7 Errors that May Occur in Remote I/O Communications The following errors may occur during remote I/O communications.
Section 4-7 Errors that May Occur in Remote I/O Communications Condition Fixed or user-set allocations Error Details I/O communications error A timeout occurred during remote I/O communications. (The Slave response timed out 6 times in a row or an error occurred 3 times in a row.) Network power error The network is not supplying communications power. Send timeout A communications request was not successfully completed due to the following reasons: • There are no devices on the network.
SECTION 5 Remote I/O Slave Communications This section describes the remote I/O communications performed as a DeviceNet slave by the DeviceNet Unit. 5-1 5-2 5-3 Slave Remote I/O Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 5-1-1 Allocation Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 5-1-2 Remote I/O and Slave Communications Specifications . . . . . . . . . .
Section 5-1 Slave Remote I/O Communications 5-1 Slave Remote I/O Communications A CS/CJ-series DeviceNet Unit can function as a Slave Unit in remote I/O communications and a single CS/CJ-series DeviceNet Unit can function as both a Master Unit and a Slave Unit. This section describes Slave communications.
Section 5-1 Slave Remote I/O Communications 5-1-2 Remote I/O and Slave Communications Specifications Item Allocation method Specifications Fixed allocations Select one of the following fixed allocation areas using the Slave Fixed Allocated Area Switches 1, 2, and 3 in the software switches in the allocated CIO Area words.
Slave Remote I/O Communications Section 5-1 munications, allocate areas, and then enable slave communications. The allocated areas will not be valid if the procedure is done in any other order. User-set Remote I/O Allocations Using DM Area Settings 1,2,3... 1. Turn ON the communications, slave, and PC power supplies. Note Turn ON the communications power supply prior to turning ON the slave power supply or the slaves may not go online. 2. Switch the CPU Unit to PROGRAM mode. 3.
Section 5-2 Fixed Allocations Note 1. Enable slave communications in CS1W-DRM21 or CJ1W-DRM21 properties if the Configurator is used. 2. Use Configurator Ver. 2.10 or later for the CJ1W-DRM21. 5-2 5-2-1 Fixed Allocations Allocated Words Words in the CS/CJ-series DeviceNet CIO Area in the CPU Unit are allocated. Words can be selected from one of three fixed allocation areas. Use a Software Switch to select the allocation area.
Section 5-3 User-set Allocations Fixed Allocation Area 1 CS/CJ-series DeviceNet CIO Area Master Slave Bit 15 Bit 0 OUT area Output (OUT) area CIO 3370 15 0 Input (IN) area CIO 3270 IN area Fixed Allocation Area 2 CS/CJ-series DeviceNet CIO Area Bit Slave 15 0 OUT area Output (OUT) area CIO 3570 Bit Master 15 0 IN area Input (IN) area CIO 3470 Fixed Allocation Area 3 CS/CJ-series DeviceNet CIO Area Master Slave Bit 15 CIO 3770 Bit 0 Output (OUT) area 15 CIO 3670 5-3 OUT area 0 I
Section 5-3 User-set Allocations 2. Only two blocks (OUT 1 and IN 1) can be allocated when setting are made with the allocated DM Area words area, but there are three blocks (OUT 1 and IN 1/2) available with the Configurator. Setting through the Allocated DM Area Words (Slave User Allocations Table) Words can be allocated for the OUT 1 area (master to Slave Unit) and IN 1 area (Slave Unit to master) from any specified I/O memory location specified in the settings in the allocated DM area words.
Section 5-3 User-set Allocations • Areas and Word Ranges for the OUT 1/IN 1 Areas Code Name Word range 00 Hex --- The block is not used.
Section 5-3 User-set Allocations • Slave User Allocations Table OUT block 1 area : WR (04 Hex) First word of OUT block 1: 50 (0032 Hex) OUT block 1 size: 20 bytes (14 Hex, 10 words) IN block 1 area : WR (04 Hex) First word of IN block 1: 100 (0064 Hex) IN block 1 size: 10 bytes (0A Hex, 5 words) • Slave areas OUT area 1 to IN area 1 Step 1: Turn ON the Slave User Allocations Switch Make sure that slave communications have stopped prior to performing this operation.
Section 5-3 User-set Allocations Setting through the Configuration A maximum of three blocks can be allocated at any locations in I/O memory for the output (OUT) area block 1, input (IN) area block 1, and input (IN) area block 2.
Section 5-3 User-set Allocations Connection Types and Allocated I/O Areas The following table shows the relationship between various connection combinations and the allocated areas that are applicable with those connections.
SECTION 6 Message Communications This section describes message communications using FINS commands sent from the ladder program in the CPU Unit of the PC. 6-1 6-2 6-3 6-4 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 6-1-1 Outline of Message Communications. . . . . . . . . . . . . . . . . . . . . . . . 134 6-1-2 FINS Message Communications . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 6-1 Overview 6-1 Overview Message communications enable messages to be set between nodes on a DeviceNet network when required by system conditions. The messages can be sent between PCs, between an OMRON PC and a master made by another company, or between slaves. They can be used to send/receive data; read time data, error histories, and other data; or control operation, e.g., by force-setting/resetting bits. There are two types of messages: FINS messages and explicit messages.
Section 6-1 Overview Overall Structure CPU Unit CMND(490) instruction CMND(490) instruction (2801 Hex) DeviceNet Unit FINS message FINS Explicit message FINS message function Explicit message function OMRON special message communications FINS message DeviceNet network DeviceNet message communications Explicit message Note If only the message communications function is being used and the remote I/ O communications function is not being used, message communications are possible even if the master
Section 6-1 Overview Note 1. The DeviceNet Unit must be registered in the local network routing table of the CS/CJ-series PC when two or more Communications Units (including the DeviceNet Unit) are mounted to a CS/CJ-series PC. The commands will not be sent if the Unit is not registered in the routing tables. 2.
Section 6-1 Overview Sending FINS Message Communications CS1W-DRM21 CJ1W-DRM21 CS1W-DRM21 CJ1W-DRM21 CS/CJ-series CPU Unit C200HW-DRM21-V1 CVM1-DRM21-V1 CVM1/CVseries CPU Unit C200HX/HG /HE (-Z) CPU Unit CS/CJ-series CPU Unit Command can be sent. DeviceNet Command cannot be sent. X X Command cannot be sent.
Section 6-1 Overview Note A specific FINS command (command 2801) is used to send explicit messages. Item Sending Receiving Network commu- CMND(490) using FINS command code 2801 Hex nications instruc- can be used to send explicit messages to tion DeviceNet devices. (See note.) Automatically responds to explicit messages from other devices. Remote devices and supported functions Masters made by other manufacturers. PCs with CS/CJ-series DeviceNet Units. PCs with C200H-series DeviceNet Master Units.
Section 6-1 Overview Item Specification Response monitoring time Default setting: User setting: Retries 2s 0.1 to 6553.5 s 0 to 15 FINS message communications commands Received from CS/CJseries CPU Unit with CS/ CJ-series DeviceNet Unit Supported (Data send/receive or FINS commands). Received from CVM1/CVseries CPU Units with CVM1/CV-series DeviceNet Master Unit Not supported.
Section 6-1 Overview Example: Routing table error Flashing red Not relevant Master Status Area 1 DeviceNet Unit 6-1-6 CPU Unit Message Monitoring Timer A message monitoring timer monitors responses for the DeviceNet Unit. A timer can be set for each device that will be communicated with (each message destination). Message monitoring timers are supported for both explicit message and FINS message communications. The timers can be set with version 2 or later of the DeviceNet Configurator.
Section 6-2 FINS Commands and Responses termeasures and errors recorded in error history that are not shown by the indicators. Error Indicators MS Network power error No change NS Not lit Send timeout Unit status 1 (word n+10) Error history code (Hex) E0 Bit 07 turns ON. 0341 E2 Bit 08 turns ON. 0342 7-segment display Routing table error Flashing red No change HC Bit 12 turns ON. 021A Node address duplicated No change F0 Bit 06 turns ON. 0211 F1 Bit 05 turns ON.
Section 6-2 FINS Commands and Responses Refer to SYSMAC CS/CJ Series Communication Commands Reference Manual (W342) for details on FINS commands. 6-2-2 Sending/Receiving FINS Command/Responses FINS commands are sent using the CMND(490) instruction for CS/CJ-series PCs. Send/receive FINS commands and responses and the data formats used are illustrated in the following diagram. Unless otherwise specified, all data is hexadecimal.
Section 6-2 FINS Commands and Responses The main response codes are listed below. Refer to SYSMAC CS/CJ Series Communication Commands Reference Manual (W342) for further details on response codes, including sub-response codes (SRES).
Section 6-2 FINS Commands and Responses Function Manipulating the PC clock Name CLOCK READ Command code 07 CLOCK WRITE Manipulating messages MESSAGE READ 01 02 09 20 0C 01 MESSAGE CLEAR FAL/FALS READ Controlling access rights Manipulating error data Manipulating File Memory ACCESS RIGHT ACQUIRE ACCESS RIGHT FORCED ACQUIRE 02 ACCESS RIGHT RELEASE 03 ERROR CLEAR 21 02 ERROR LOG CLEAR 03 FILE NAME READ 22 01 SINGLE FILE READ 02 SINGLE FILE WRITE 03 MEMORY CARD FORMAT 04 FILE DEL
Section 6-3 Using FINS Message Communications Commands Addressed to DeviceNet Units Name Command code Page RESET 04 03 241 CONTROLLER DATA READ 05 01 241 CONTROLLER STATUS READ 06 01 242 ECHOBACK TEST 08 01 243 ERROR LOG READ 21 02 244 03 245 ERROR LOG CLEAR Command to Send Explicit DeviceNet Messages Name EXPLICIT MESSAGE SEND 6-3 Command code 28 01 Page 261 Using FINS Message Communications There are two instructions that can be executed to send and receive data from CS/CJ-
Section 6-3 Using FINS Message Communications 3. In all cases other than the following two exceptions, a local network table must be made, and the DeviceNet Unit must be registered in it. a) When there is only one DeviceNet Unit. b) When only multiple DeviceNet Units are mounted, with no remote I/O communications. 4. A local network table is sometimes necessary even when the DeviceNet Unit is not operating across networks. 5.
Section 6-3 Using FINS Message Communications Address of local network CPU Bus Unit’s unit number 2 01 3 02 The unit number of the DeviceNet Unit as a CPU Bus Unit is the number set on the rotary switches on the front panel (0 to 15). The network address is the address of the Network to which the CPU Bus Unit is connected (1 to 127). The network address is specified when this local network table for the routing table is created.
Section 6-3 Using FINS Message Communications 4. Use the left-side table to create the local network table. Input the unit numbers and corresponding local network addresses. 5. Use the right-side table to create the relay network table. Input the final network addresses and corresponding relay network addresses and relay node addresses. 6. Save the finished routing table. 7. Go online, then load and send the routing table. Note Use CX-Programmer Ver. 2.
Section 6-3 Using FINS Message Communications Word Note Bits 00 to 07 Bits 08 to 15 C+3 Bits 00 to 03: No. of retries (0 to 15, i.e., $0 to $F) Bits 04 to 07: Set to 0. Bits 08 to 10: Transmission port number ($0 to $7) Bit 11 to 14: Set to 0. Bit 15: ON: No response. OFF: Response returned. C+4 Response monitoring time ($0001 to $FFFF = 0.1 to 6553.5 seconds)3 1. Indicates a Unit as shown in the following table.
Section 6-3 Using FINS Message Communications Note 1. Indicates a Unit as shown in the following table. Unit Setting CPU Unit 00 User program in FA computer 01 CPU Bus Unit $10 to $1F: Unit numbers 0 to 15 $FE: The local Unit 2. Values of $00 to $3E indicate nodes 0 to 63. 3. Designates the length of time in (0.1-s units) that the PC retries transmission when bit 15 of C+3 is OFF and no response is received. The default value is $0000, which indicates 2 seconds.
Section 6-3 Using FINS Message Communications Word C Note Bits 00 to 07 Bits 08 to 15 Number of command bytes to send: 0 to 542 (i.e., $0000 to $021E) C+1 Number of response bytes to receive: 0 to 542 (i.e., $0000 to $021E) C+2 Destination network address (0 to 127, i.e., $00 to $7F, 0 = local network) Set to 0. C+3 Destination unit FINS address1 Destination node address2 C+4 Bits 00 to 03: No. of retries (0 to 15, i.e., $0 to $F) Bits 04 to 07: Set to 0.
Section 6-3 Using FINS Message Communications Execution condition Network Enabled Flag Message Communications Permitted Flag SEND(090), RECV(098), or CMND(490) word n+24, bit 12 Communications Flags Type Name Address Word Network Enabled Flag A202 Network Error Flag A219 Bit 7 6 5 4 3 2 1 0 Port 7 Port 6 Port 5 Port 4 Port 3 Port 2 Port 1 Port 0 CPU Unit Content 0: Normal completion 1: Error Port 7 Port 6 Port 5 Port 4 Port 3 Port 2 Port 1 Port 0 7 6 5 4 3 2 1 0 0: Execution not possible
Section 6-3 Using FINS Message Communications in the following table.
Section 6-3 Using FINS Message Communications Data Area Note Range Holding Area H000 to H511 Auxiliary Area A000 to A959 (*3) Timer Area T0000 to T4095 Counter Area C0000 to C4095 DM Area D00000 to D32767 EM Area E00000 to E32767 (*2) 1. A000 to A477 in the Auxiliary Area are write-protected. 2. There can be up to 13 banks of EM Memory. Refer to the operation manual for the CPU Unit for information on whether it has EM Memory and how many banks can be used. 3.
Section 6-3 Using FINS Message Communications Program Example A202 11 (071) BSET #1234 D01000 D01004 Sets 1234 in D01000 to D01004. (021) MOV #0005 D00000 (021) MOV #0001 D00001 Places data into control data words to specify the 5 words to be transmitted to the CPU Unit of node 06 of network 01, through port 0, with response, 0 retries, and a response monitoring time of 10.0 seconds.
Section 6-3 Using FINS Message Communications Example 2: Sending a FINS Command Using CMND CS/CJ-series DeviceNet Unit No. 0 CMND CS/CJ-series DeviceNet Unit CPU Unit Node 05 CPU Unit Unit address: 00 Node 06 Network 01 MEMORY AREA READ command Operation • The PC with DeviceNet Unit 1 with node address 5 reads the data from the 5 words D01000 to D01004 from the PC with DeviceNet Unit 2 with node address 06. • The MEMORY AREA READ command (01 01) is used to read variable data.
Section 6-3 Using FINS Message Communications Example Program A500 15 (071) BSET #0000 D00000 D02999 Sets 0000 in D00000 to D02999.
Section 6-4 Sending Explicit Messages Up to 3 levels of networks, including DeviceNet, are possible. Controller Link Unit Controller Link Unit CS/CJ-series DeviceNet Unit CS/CJ-series CPU Unit Remote I/O communications DeviceNet Controller Link CS/CJ-series DeviceNet Unit DeviceNet CS/CJ-series DeviceNet Unit When connecting networks, routing tables must be registered for the PC CPU Units on all networks.
Section 6-4 Sending Explicit Messages 6-4-1 Sending Explicit Messages The FINS command code 28 01 can be used to send explicit DeviceNet messages to OMRON slaves and DeviceNet devices made by other manufacturers. The use of explicit messages is illustrated in the following diagram. Slave or Master by other manufacturer DeviceNet De viceNet Unit CPU Unit Explicit message FINS header FINS header CMND (490) DeviceNet network Use 28 01 for the FINS command code.
Section 6-4 Sending Explicit Messages The following diagram shows an example of actual node address specifications. Machine No. of DeviceNet Unit: 2 The node address of the non-OMRON node is set as the destination node address in the FINS command data.
Section 6-4 Sending Explicit Messages 28 01 Command code Parameters Response code Destination node address (command): The node address of the destination of the explicit message. (The node address of the local DeviceNet Unit is specified in the control data for the CMND(490) or IOWR instruction, but the node address of the actual destination is specified here in the FINS command.) Service code (command, response): A service code defined for DeviceNet.
Section 6-4 Sending Explicit Messages D: First response word C: First control data word Command data is set in order starting with the word specified for the CMND(490) operand S (first command word) and continuing with words with higher addresses in I/O memory in the command block format. Command Format Example: Writing Error Clear Codes to the CPU Unit Set in this order starting from the word specified for the CMND(490) operand S (first command word) and continuing with words with higher addresses.
Section 6-4 Sending Explicit Messages Command Block Eg. For $1234 Eg.
Section 6-4 Sending Explicit Messages Settings (Hex).
Section 6-5 Receiving Explicit Messages Program Example A200 11 (071) BSET #0000 D00000 D02999 Sets 0000 in D00000 to D02999.
Section 6-5 Receiving Explicit Messages • PCs with CVM1/CV-series DeviceNet Master Units (CVM1-DRM21-V1) • PCs with CS/CJ-series DeviceNet Units Example CS/CJ-series C200H-series DeviceNet Unit DeviceNet Master Unit C200HX/HG/HE CPU Unit CS/CJ-series CPU Unit Other manufacturer master Explicit messages can be received Explicit message DeviceNet Note Status and the I/O memory read/write operations cannot be performed for PCs with a C200H-series or CVM1/CV-series DeviceNet Master Units.
Section 6-5 Receiving Explicit Messages I/O Memory Read/Write for CPU Units Service Service code Byte Data Read IC Hex Class ID 2F Hex Instance ID Specifies area (01 Hex to 14 Hex) Request service data Contents Address, No. Reads the specified node data in byte units. of read bytes The word data is read in order, from high to low bytes. Read data: 200 bytes max. Word Data Read ID Hex Address, No. Reads the specified node data in word units.
Section 6-5 Receiving Explicit Messages CPU Information Read (Service Code: 0E Hex) Reads CPU Unit information, including operating mode, fatal/non-fatal errors, and the CPU Unit model. Command Block Attribute ID Class ID Service code Instance ID Destination node address Response Block Service Code Attribute Value Destination node address No.
Section 6-5 Receiving Explicit Messages Read data (response): The specified information is returned in order. • CPU Unit operating mode (attribute ID = 64 Hex). The CPU Unit operating mode is returned in 1-word (2-byte) hexadecimal format, as follows: 0001 Hex: PROGRAM mode; 0002 Hex: MONITOR mode; 0004 Hex: RUN mode PROGRAM mode MONITOR mode RUN mode Note The codes for the above modes are 1-word (2-byte) data and are returned in low byte first.
Section 6-5 Receiving Explicit Messages Response Block Service Code Destination node address No. of bytes received Parameters Destination node address (command): The node address of the CS/CJseries DeviceNet Unit to which to write data, specified in 1-byte (2 digit) hexadecimal. Service code (command, response): 10 Hex is specified for commands. For responses, the highest bit will turn ON and 90E Hex will be returned. Class ID (command): Always 002F Hex. Instance ID (command): Always 0000 Hex.
Section 6-5 Receiving Explicit Messages Error code (Hex) Data cleared 00F7 Battery error 0200 to 020F CS/CJ-series CPU Bus Unit error (last 2 digits are binary code for the Unit No.) For parity errors generated when data transferred between CS/CJseries CPU Bus Unit and CPU Unit For watchdog timer errors in CS/CJ-series CPU Bus Unit 0400 to 040F CPU Bus settings error (last 2 digits are binary code for the Unit No.
Section 6-5 Receiving Explicit Messages CPU Unit Status Read (Service Code: 40 Hex) This PLC Object service reads status details (operation status, operating mode, fatal and non-fatal errors, etc.) from the CPU Unit. Command Block Class ID Service Code Instance ID Destination node address Response Block Service Code Detailed status Destination node address No.
Section 6-5 Receiving Explicit Messages • Operation status: Returns the operation status of the CPU Unit in 1-byte (2-digit) hexadecimal. • Operating mode: Returns the operating mode of the CPU Unit in 1-byte (2-digit) hexadecimal. 0001 Hex: PROGRAM mode; 0002 Hex: MONITOR mode; 0004 Hex: RUN mode • Fatal error information: Returns the fatal error information for the CPU Unit in 2 bytes (low to high). 1: System error (FALS) 1: Cycle time over 1: Program error 1: I/O setting error 1: No.
Section 6-5 Receiving Explicit Messages • Message Exists/Does Not Exist: When the MSG instruction is executed by the CPU Unit, the bit corresponding to the message number will turn ON and be returned in 2 bytes (from low to high bytes). Message No. 0 (1: exists; 0: does not exist) Message No. 1 (1: exists; 0: does not exist) Message No. 2 (1: exists; 0: does not exist) Message No. 3 (1: exists; 0: does not exist) Message No. 4 (1: exists; 0: does not exist) Message No.
Section 6-5 Receiving Explicit Messages Response Block Service Code Word data L Word data L Word data H Word data H Destination node address No. of bytes received Parameters Read data (200 bytes max.) Destination node address (command): The node address of the CS/CJseries DeviceNet Unit from which to read data, specified in 1-byte (2 digit) hexadecimal. Service code (command, response): IC Hex is specified for commands. For responses, the highest bit will turn ON and 9C Hex will be returned.
Section 6-5 Receiving Explicit Messages Word Data Read (Service Code: 1D Hex) Word Data Read reads I/O memory area data in CPU Units with a CS/CJseries DeviceNet Units. The read word data is in word units. The response block is returned from low to high bytes. Command Block Address L Class ID Address H Service Code Instance ID Destination node address No.
Section 6-5 Receiving Explicit Messages No of Read Words (command): The number of words of read data is specified in 1-byte (2-digit) hexadecimal. The range is 01 to 64 Hex (1 to 100 decimal). No. of bytes received (response): The number of bytes received from the destination node address (remote node) is returned in hexadecimal. Destination node address (response): The node address of the CS/CJseries DeviceNet Unit that returned the response is returned in hexadecimal.
Section 6-5 Receiving Explicit Messages Instance ID (command): The type of memory area to which the data will be written is specified in hexadecimal as shown in the following table.
Section 6-5 Receiving Explicit Messages Response Block Service Code Destination node address No. of bytes received Parameters Destination node address (command): The node address of the CS/CJseries DeviceNet Unit to which the data is written, specified in 1-byte (2 digit) hexadecimal. Service code (command, response): IF Hex is specified for commands. For responses, the highest bit will turn ON and 9F Hex will be returned. Class ID (command): Always 002F Hex.
SECTION 7 Other Functions This section describes connecting to CX-Programmer via the DeviceNet and the Memory Card backup function. 7-1 7-2 Connecting to the CX-Programmer via the DeviceNet. . . . . . . . . . . . . . . . . . 182 7-1-1 Setting Node Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 7-1-2 Setting the Message Monitoring Timer of the DeviceNet Unit . . . .
Section 7-1 Connecting to the CX-Programmer via the DeviceNet 7-1 Connecting to the CX-Programmer via the DeviceNet With CX-Programmer Ver. 2.1 or later, a serial connection can be made to a PC containing a CS/CJ-series DeviceNet Unit to form an online connection, via the DeviceNet, to other PC CPU Units on the network. • CS-series CPU Unit • CJ-series CPU Unit • Programmable Slave DeviceNet Unit CX-Programmer Ver. 2.
Section 7-1 Connecting to the CX-Programmer via the DeviceNet 7-1-1 Setting Node Addresses When the CX-Programmer is connected online, it uses FINS message communications. It is thus necessary to set the node address to a number other than 0 for DeviceNet Units mounted to the target PC, DeviceNet Units mounted to a PC which is connected by a serial connection to the CX-Programmer, or DeviceNet Units mounted to a PC relaying between networks.
Connecting to the CX-Programmer via the DeviceNet Section 7-1 2. Double-click on the node address (#) that you want to change, or select the node address and click on the Edit Button. A dialogue box like the one below will appear. 3. Input the value, then click on the OK Button. Note To set the same value for all of the devices, select the node addresses to be set, then click on Copy to All Device. Note 1. The default setting for the message monitoring timer is 2,000 ms (2 s).
Section 7-1 Connecting to the CX-Programmer via the DeviceNet response monitor time in the CMND/SEND/RECV instruction to be the same as or slightly longer than the time for the message monitoring timer (Response monitor time in the CMND/SEND/RECV instruction ≥ message monitoring timer.) If time-outs occur frequently, increase both of the settings equally, while maintaining the relationship between them.
Memory Card Backup Functions Section 7-2 a maximum of four-fold (for a communications speed of 500 Kbps) in comparison with connection by a peripheral bus. 2. Temporarily extend the communications cycle time. Operate the CX-Programmer after extending the cycle time in the Communications Cycle Time Setup Table (word m) in the DM Area, and turning ON the Temporary Setting Switch for Communications Cycle Time (word n, bit 12). Extending the communications cycle time 1.
Section 7-2 Memory Card Backup Functions DeviceNet Unit Unit Setup File Backup Switch CPU Unit Unit Setup File Restore Switch Configurator (computer) All setup data Memory Card Backup Save file Restore 7-2-1 Load file Outline of Functions 1. Backing Up Unit Setup Files Saves all internal Unit setup data to the Memory Card mounted to the CPU Unit. Method: Turn ON the Setup File Backup Switch (word n+1, bit 15) to save the internal Unit setup data to the Memory Card as a Unit Setup File.
Section 7-2 Memory Card Backup Functions DeviceNet Unit CPU Unit All setup data Unit Setup File Restore Switch Memory Card Restore Note If there is an error in the setup data or if the file could not be read, the File Read/Write Error bit in Unit Status 2 (word n + 11, bit 08) will turn ON. 3. Saving Files from Configurator to Memory Card Device parameter files (.
SECTION 8 Communications Timing This section describes the time required for remote I/O communications and message communications. 8-1 8-2 Remote I/O Communications Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . 190 8-1-1 Communications Cycle Time and Refresh Time . . . . . . . . . . . . . . . 190 8-1-2 I/O Response Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 8-1-3 More than One Master in Network . . . . . . . . . . . . . . . . . . . . .
Remote I/O Communications Characteristics 8-1 Section 8-1 Remote I/O Communications Characteristics This section describes the characteristics of remote I/O communications when the DeviceNet Unit is used as a master in combination with OMRON’s slaves. Use this section for reference when planning operations that require precise I/O timing. The equations provided here are valid under the following conditions: 1,2,3... 1. The DeviceNet Unit is operating with the scan list enabled. 2.
Remote I/O Communications Characteristics Communications Cycle Time Calculation Section 8-1 Use the equations shown below to calculate the communications cycle time (TRM) for a network with one Master. Note that if the result of this calculation is less than 2 ms, the actual communications cycle time will be 2 ms. TRM= Σ (Communications time per Slave) + High-density Unit processing time + Explicit message processing time + COS/Cyclic connection time (ms) + 0.01 × N + 1.
Section 8-1 Remote I/O Communications Characteristics TRT = TOH + TBYTE-IN × TOH : TBYTE-IN : BIN : TBYTE-OUT : BOUT : Slaves with More Than 8 Bytes of Input or Out put Baud rate 500 kbps 250 kbps 125 kbps BIN + TBYTE-OUT × BOUT [ms] Protocol overhead The input byte transmission time The number of input words The output byte transmission time The number of output words TOH 0.306 ms 0.542 ms 1.014 ms TBYTE-IN 0.040 ms 0.073 ms 0.139 ms TBYTE-OUT 0.036 ms 0.069 ms 0.
Section 8-1 Remote I/O Communications Characteristics TIN: TOUT: TRM: TPC: The Input Slave’s ON (OFF) delay The Output Slave’s ON (OFF) delay Network’s communications cycle time (See page 191.) The PC’s cycle time (See note below.) Note The PC’s cycle time will be delayed as shown below for one DeviceNet Unit. For details, refer to Refresh Time on page 192. 0.7 ms + (number of occupied words × 0.
Section 8-1 Remote I/O Communications Characteristics Minimum I/O Response Time The minimum I/O response time occurs when the Slave’s I/O refreshing is executed just after the input signal is received by the DeviceNet Unit and the output signal is output at the beginning of the next I/O refresh cycle.
Section 8-1 Remote I/O Communications Characteristics Note Although in the above diagram the Slaves are separated into two groups for convenience, the actual physical positions in the Network are irrelevant. Next, we can refer to 8-1-1 Communications Cycle Time and Refresh Time and calculate the communications cycle time for each group as if they were separate Networks.
Section 8-2 Message Communications This programming is for a DeviceNet Unit with a unit number of 00. 1512 15 1510 00 Remote I/O Communications (n+12, bit 15) Unit Error (n+10, bit 00) Slaves' I/O processing Note Refer to 3-2 Allocated CIO Area Words for details on the Master Status Area. Slave Function It takes approximately four seconds from the time that the Devicenet Unit is turned ON or restarted as a slave until remote I/O communications with the master begin.
Section 8-2 Message Communications Note 8-2-2 1. If the CPU Unit attempts to send another message or receives a message from another node within the message communications time, the second message or the message being received from another node may be destroyed. Never execute a second communications instruction before the message communications time has elapsed and never send messages to any one node at intervals less than the message communications time. 2.
Section 8-2 Message Communications Shown below is the response time required to return data for 100 words.
SECTION 9 Troubleshooting and Maintenance This section describes error processing, periodic maintenance operations, and troubleshooting procedures needed to keep the DeviceNet network operating properly. We recommend reading through the error processing procedures before operation so that operating errors can be identified and corrected more quickly. 9-1 9-2 9-3 9-4 Troubleshooting with the DeviceNet Unit Indicators . . . . . . . . . . . . . . . . . . .
Section 9-1 Troubleshooting with the DeviceNet Unit Indicators 9-1 9-1-1 Troubleshooting with the DeviceNet Unit Indicators Determining Operating Status from the Indicators The following table shows the status of the MS and NS indicators and the 7segment display during normal operation. Indicator status MS NS Network/Unit status Comments 7-segment OFF OFF OFF Initializing with PC Initialization processing with the PC is in progress.
Section 9-1 Troubleshooting with the DeviceNet Unit Indicators 9-1-2 Troubleshooting Errors Occurring in the DeviceNet Unit Error category Error Indicators MS 7-segment Master function Software settings errors Remote I/O communications stopped by a communications error CPU Unit status error Unit status error Structure error Incorrect setting Multiple switches ON Master funcStructure I/O area duplication tion errors I/O area range exceeded Unsupported slave Verification Non-existent slave errors Ill
Section 9-1 Troubleshooting with the DeviceNet Unit Indicators remote I/O communications for a communications error, two errors can be displayed: The slave’s communications error and its most recent error.
Section 9-1 Troubleshooting with the DeviceNet Unit Indicators Correction Set the slaves’ node addresses again. Structure Error: I/O Area Range Exceeded 7-segment d1 MS indicator --- NS indicator Red (flashing) Error log (Hex) 0343 Likely Cause The slave’s I/O area isn’t within the allowed range. (Occurs with the scan list disabled.) DeviceNet Unit Response Records the error in the error log. The master will periodically attempt to reconnect with the slave with the structure error.
Section 9-1 Troubleshooting with the DeviceNet Unit Indicators Flags Allocated for C200H DeviceNet Master Unit (CIO n+24) Bit 14 (Error Flag) and bit 07 (Comparison Error Flag) will be ON. CIO Area Flags Allocated to DeviceNet Unit Bit 00 of n+12 (Comparison Error Flag) and bits 00 and 01 of n+10 (Unit Error Flag and Master Function Error Flag) will be ON.
Section 9-1 Troubleshooting with the DeviceNet Unit Indicators Correction Inspect the slave and then create the scan list again. Verification Error: I/O Size Mismatch 7-segment d6 MS indicator --- NS indicator Red (flashing) Error log (Hex) 0344 Likely Cause The slave’s I/O data size does not match the registered scan list. (Occurs with the scan list enabled.) DeviceNet Unit Response Records the error in the error log.
Section 9-1 Troubleshooting with the DeviceNet Unit Indicators DeviceNet Unit Response Records the error in the error log. The master will periodically attempt to reconnect with the slave with the verification error. Flags Allocated for C200H DeviceNet Master Unit (CIO n+24) Bit 14 (Error Flag) and bit 07 (Comparison Error Flag) will be ON.
Section 9-1 Troubleshooting with the DeviceNet Unit Indicators • Matching master and slave baud rates • Proper cable lengths (trunk and branch lines) • Broken or loose cables • Installation of terminators at both ends of the trunk line • Excessive noise Software Switch Setting Errors CPU Unit Status Error 7-segment C0 MS indicator --- NS indicator --- Error log (Hex) --- Likely Cause The software settings operation couldn’t be performed because the CPU Unit wasn’t in PROGRAM mode.
Section 9-1 Troubleshooting with the DeviceNet Unit Indicators Likely Cause The setting operation failed because a structure error occurred. DeviceNet Unit Response The only response is the error code displayed on the 7-segment display. The error display will be cleared the next time that a settings operation is completed normally. Correction Correct the cause of the structure error. (See errors d0 to d2.
Section 9-1 Troubleshooting with the DeviceNet Unit Indicators return to normal when the network power supply is restored, although scanning will not resume if the DeviceNet Unit is set to stop remote I/O communications when a communications error occurs. Flags Allocated for C200H DeviceNet Master Unit (CIO n+24) Bit 14 (Error Flag) and bit 05 (the Sending Error Flag) will be ON.
Section 9-1 Troubleshooting with the DeviceNet Unit Indicators DeviceNet Unit Response Records the error in the error log. • The Unit will go off–line and communications will be disabled. Error responses will be returned to all communications requests. • The exchange of data with the CPU Unit will continue. Flags Allocated for C200H DeviceNet Master Unit (CIO n+24) Bit 14 (Error Flag) and bit 01 (the Node Address Duplicated/Bus Off Flag) will be ON.
Section 9-1 Troubleshooting with the DeviceNet Unit Indicators DeviceNet Unit Response Records the error in the error log. Operation will continue using the default message monitoring timer values. Flags Allocated for C200H DeviceNet Master Unit (CIO n+24) Bit 14 (Error Flag) and bit 03 (the Structure Error Flag) will be ON. CIO Area Flags Allocated to DeviceNet Unit Bits 00 and 13 of n+10 (the Unit Error Flag and Incorrect Message Monitoring Timer List Data Flag) will be ON.
Section 9-1 Troubleshooting with the DeviceNet Unit Indicators Correction Clear the scan list and register the scan list again or use the Configurator to reset the master scan list. Memory Access Error 7-segment E9 MS indicator Red (flashing) NS indicator --- Error log (Hex) 0602 Likely Cause An error occurred in the Unit’s non-volatile memory itself. This error will occur in the following cases. 1,2,3... 1. An error occurs reading the identity information during initialization 2.
Section 9-1 Troubleshooting with the DeviceNet Unit Indicators CIO Area Flags Allocated to DeviceNet Unit Bits 00 and 04 of n+10 (the Unit Error Flag and Unit Memory Error Flag) will be ON. Correction Replace the Unit if the error recurs. CPU Unit Exchange Errors Unit Number duplication 7-segment H1 MS indicator Red (flashing) NS indicator OFF Error log (Hex) --- Likely Cause The unit number is duplicated on another Unit. DeviceNet Unit Response Stops operation.
Section 9-1 Troubleshooting with the DeviceNet Unit Indicators DeviceNet Unit Response Stops operation. Correction Set the communications speed correctly and restart the DeviceNet Units. CPU Unit Faulty (H6) 7-segment H6 MS indicator Red (flashing) NS indicator OFF Error log (Hex) 000F DeviceNet Unit Response Records the error in the error log. (The time information is set to all zeroes.) Stops operation. Correction Replace the CPU Unit if the error recurs when the CPU Unit is restarted.
Section 9-1 Troubleshooting with the DeviceNet Unit Indicators DeviceNet Unit Response Continues processing but data exchange with the CPU Unit is stopped. The routing table is treated as missing. Records the error in the error log. Flags Allocated for C200H DeviceNet Master Unit (CIO n+24) Bit 14 (Error Flag) and bit 03 (the Structure Error Flag) will be ON. CIO Area Flags Allocated to DeviceNet Unit Bits 00 and 12 of n+10 (the Unit Error Flag and Routing Table Error Flag) will be ON.
Section 9-1 Troubleshooting with the DeviceNet Unit Indicators CIO Area Flags Allocated to DeviceNet Unit Bit 00 of n+10 (Unit Error Flag) will be ON together with one of the following combinations: • Bit 05 of n+12 (the Master I/O Refresh Error Flag) and bit 01 of n+10 (the Master Function Error Flag) ON. • Bit 05 of n+14 (Remote I/O Refresh Error Flag) and bit 03 of n+10 (the Slave Error Flag) ON. Correction Check the master scan list and slave scan list and reset with a correct allocation.
Section 9-1 Troubleshooting with the DeviceNet Unit Indicators • Returns an error response (0302 Hex) to commands requiring a response. • Discards other frames and stores an error record (010B Hex) in the error log. Flags Allocated for C200H DeviceNet Master Unit (CIO n+24) There is no status notification because communications with the CPU Unit are disabled. CIO Area Flags Allocated to DeviceNet Unit There is no status notification because communications with the CPU Unit are disabled.
Section 9-2 Error Log Functions • Installation of terminators at both ends of the trunk line • Excessive noise Unit Errors Special Unit Error 7-segment OFF MS indicator Red (lit) NS indicator OFF Error log (Hex) 0601 DeviceNet Unit Response Records the error in the error log. Stops the Unit. Correction Restart the CPU Unit. Replace the DeviceNet Unit if the error recurs.
Section 9-2 Error Log Functions When using the Configurator, the error log can be monitored with the master error history read operation. With the Configurator, the error log can only be monitored and the data cannot be saved. Time Information The CPU Unit’s time information is used for the time stamps in the DeviceNet Unit’s error log records. If the time information cannot be read from the CPU Unit, the time stamp will contain all zeroes.
Section 9-2 Error Log Functions Error code (Hex) 0101 0105 0106 0107 0108 0109 010B Error Detail code First byte Second byte Transmission failed because the local node is not participating in the network. FINS message communications command: Bit 15: OFF Bits 14 to 8: SNA Transmission failed because of a node address Bits 7 to 0: SA1 setting error. FINS message communications response: Transmission failed because of a node address Bit 15: ON duplication error.
Section 9-2 Error Log Functions Error code (Hex) Error Detail code First byte Second byte Record stored in EEPROM 0343 Structure error 01 Hex: I/O area duplication 02 Hex: I/O area range exceeded 03 Hex: Unsupported slave Slave’s node address No 0344 Verification error 01 Hex: Non-existent slave 02 Hex: Illegal header 03 Hex: Illegal device type 04 Hex: Illegal product code 05 Hex: Unsupported connection 06 Hex: I/O size mismatch 07 Hex: Illegal connection path Slave’s node address No 0345
Section 9-3 Troubleshooting 9-3 9-3-1 Troubleshooting CPU Unit’s ERR/ALM Indicator Lit or Flashing Use the following table to troubleshoot the network when the DeviceNet Unit is mounted and the CPU Unit’s ERR/ALM indicator is lit or flashing. Error Probable cause An I/O verification error occurred. • Make sure that the Unit is connected properly. • Check the I/O table with the I/O Table Verification operation and correct it if necessary. After correcting it, perform the I/O Table Create operation.
Section 9-3 Troubleshooting Error Probable cause The DeviceNet Unit’s MS indicator is ON and green, but the NS indicator continues to flash green. (The NS indicator normally goes ON 2 s after the MS indicator.) • If the DeviceNet Unit’s 7-segment display is displaying an error code, refer to the tables in 9-1 Troubleshooting with the DeviceNet Unit Indicators. • Restart the Unit. Replace the Unit if it doesn’t restart.
Section 9-3 Troubleshooting 9-3-4 Communications Error Operation Settings Use the following table to correct problems with the DIP switch setting for continuing/stopping communications for errors. Error Probable cause Communications are stopped even though there is no communications error. When pin 3 on the DIP switch is ON, communications will be stopped if a communications error, transmission timeout, or network power supply error occurs.
Section 9-4 Maintenance and Replacement 9-4 Maintenance and Replacement This section describes the routine cleaning and inspection recommended as regular maintenance as well as the Unit replacement procedure required if a DeviceNet Unit fails. 9-4-1 Cleaning Clean the DeviceNet Units regularly as described below in order to keep the network in its optimal operating condition. • Wipe the Unit daily with a dry, soft cloth.
Section 9-4 Maintenance and Replacement 9-4-3 Replacing Faulty Units Replace a faulty DeviceNet Unit as soon as possible. Refer to the DeviceNet Slaves Operation Manual (W347) for details on replacing slaves. We recommend having spare Units available to restore network operation as quickly as possible. Precautions Observe the following precautions when replacing a faulty Unit. • After replacement make sure that there are no errors with the new Unit.
Maintenance and Replacement Section 9-4 Creating a New Network File Use the following procedure to write the settings to the DeviceNet Unit from a network file saved on a disk. 1,2,3... 1. Turn ON power to the DeviceNet Unit, slaves, and the Configurator. 2. Place the Configurator online and display the Device List. 3. Specify the DeviceNet Unit that has been replaced, and use the Edit Device Parameters operation to register slaves and allocate I/O. 4. Write the settings to the devices. Note 1.
Appendix A Allocation Differences from C200H DeviceNet Master Units The following table shows the CS1W-DRM21/CJ1W-DRM21 DeviceNet Unit allocation areas that correspond to the C200HW-DRM21-V1 DeviceNet Master Unit allocation areas. Note The following table does not include the allocation areas that exist only in CS/CJ-series DeviceNet Units.
Appendix A Allocation Differences from C200H DeviceNet Master Units Status Areas Master Status Area 1 An area with the exact same bit configuration as Master Status area 1 used for C200H DeviceNet Master Units, was set up. This area is called the Master Replacement Status 1. • The following table compares the C200H DeviceNet Master Unit Master Status Area 1 and the CS/CJseries DeviceNet Unit Master Replacement Status 1.
Appendix A Allocation Differences from C200H DeviceNet Master Units Names for C200H DeviceNet Master Unit Master Status Area 1 C200H DeviceNet Master Unit CS/CJ Series C200HX/ HG/ HE, C200HS Communications Error Flag IR 2001+ (10 × unit No.) Unit No. 0 to 9: IR 101+(10 × unit No.) Unit No. A to F: IR 401+(10 × unit No. – 10) Word address Bit Names for CS/CJseries DeviceNet Unit Master Replacement Status 1 07 CIO 1524+ (25 × unit No.
Appendix A Allocation Differences from C200H DeviceNet Master Units Master Status Area 2 Name C200H DeviceNet Master Unit Word address Error History Flag Bit CS/CJ-series DeviceNet Unit Contents for CS/CJseries DeviceNet Unit Differences from C200H DeviceNet Master Unit Bit CS/CJ Series C200HX/HG/ HE, C200HS CS/CJ-series word address D06032+ (2 × DM6032+ (2 × 00 unit No.) unit No.) CIO 1511 + 15 (25 × unit No.
Appendix A Allocation Differences from C200H DeviceNet Master Units Normal Slave Table Name C200H DeviceNet Master Unit Word address CS/CJ Series Normal slave table 4 words starting with CIO 2006 + (10 × unit No.) For CS/CJ-series DeviceNet Units Bit C200HX/HG/HE, C200HS Unit No. 0 to 9: 4 00 to words starting with 15 IR 106 +(10 × unit No.) Unit No. A to F: 4 words starting with IR 406 + (10 × unit No.
Appendix A Allocation Differences from C200H DeviceNet Master Units Replace the addresses as shown in the following table. Area type First word of IN area in fixed remote I/O allocations C200HW-DRM21-V1 IR 350 First word of OUT area in fixed remote I/O alloca- Word 50 tions IR 2000 +10 × unit No. Software switches This Unit (CS1WDRM21) Remarks Completely compatiCan be allocated to CIO 350 from Config- ble.
Appendix B DeviceNet Connections DeviceNet has several different protocols for remote I/O communications between Master and Slave devices. Connections are units used to monitor those protocols. There are four kinds of DeviceNet remote I/O communications protocols (connections): Poll, bit–strobe, COS (change of state), and cyclic. CS/CJ-series DeviceNet Units support all four types. The connection used by the DeviceNet Unit is automatically selected if the Configurator is not used.
Appendix B DeviceNet Connections Connections Using Allocations Allocation method Without Configurator With Configurator Contents Fixed allocation (scan Only 1 connection, automatically selected by list disabled or the DeviceNet Unit. (Either a polling or bitenabled) strobe connection is used.) User-set allocations using allocated DM Area word settings Only 1 connection, automatically selected by the DeviceNet Unit based on the I/O area set in the Master User Allocations Table.
Appendix B DeviceNet Connections Note 1. Output data using poll connections and output data using COS or cyclic connections are transmitted using the same frame. Therefore set the same output size (bytes) when combining poll and COS or poll and cyclic. 2. The COS/cyclic heartbeat timer is the smallest transmission interval for COS or cyclic connections. It can be set for each corresponding slave. Refer to DeviceNet Configurator Operation Manual (W382) for details on Configurator operation.
Appendix B DeviceNet Connections Master COS Send Switch COS transmission is possible only for User-set allocations using the Configurator. When required, remote I/O output data can be output from the master to a specified slave. Output data can be sent at the communications cycle timing to the specified slave by other connections selected automatically or by the user (only when using the Configurator).
Appendix B DeviceNet Connections The following diagram shows the transmission timing. After the COS send instruction has been sent to the DeviceNet (at the I/O refresh timing for the CPU Unit), the COS transmission is executed to each slave immediately after the refresh (remote I/O communications), which each slave is performed during the communications cycle. Therefore, when there are a lot of destination slaves, the COS send timing may be delayed in order of the node addresses.
Appendix C FINS Commands and Responses for DeviceNet Units List of Command Codes Command type Command code Reference page RESET 0403 241 CONTROLLER DATA READ 0501 241 CONTROLLER STATUS READ 0601 242 ECHOBACK TEST 0801 243 ERROR LOG READ 2102 244 ERROR LOG CLEAR 2103 245 Refer to SYSMAC CS/CJ Series Communication Commands Reference Manual (W342) for details on end codes. RESET (0403) Resets (restarts) the DeviceNet Unit. Command Block Resets the DeviceNet Unit.
Appendix C FINS Commands and Responses for DeviceNet Units • Baud rate Command Block Command code Response Block 05 01 Command code End code 20 bytes 20 bytes Model Version Node Baud address rate End Codes End code (hex) Contents 0000 Normal end 1001 Command length exceeds maximum command length. Parameter Details [Model, Version] (Response) The DeviceNet Unit model and version are returned as outlined below in 20byte ASCII code.
Appendix C FINS Commands and Responses for DeviceNet Units Response Block Command End code Operation Unit code status status 1 Unit status 2 Master function status 1 Slave function status 1 Master function status 2 Slave function status 2 End Codes End code (hex) Contents 0000 Normal end 1001 Command length exceeds maximum command length. 2606 Service cannot be executed.
Appendix C FINS Commands and Responses for DeviceNet Units For commands, the data to be sent to the specified node is specified, with a maximum of 538 bytes. For responses, The test data that was sent by the command is returned. Explanation An error has occurred if the test data sent by the command and the tests data returned by the response are different. READ ERROR HISTORY (2102) Reads the error history saved in the DeviceNet Unit. Command Block Command Beginning code record no. No.
Appendix C FINS Commands and Responses for DeviceNet Units Returns the error history for the number specified by Read Record No., in order from the Read Start Record No. The total number of Error History Data bytes is 10 × Read Record No. One record of error history data is structured in 10 bytes as shown in the following diagram.
Appendix C FINS Commands and Responses for DeviceNet Units End Codes End code (hex) Contents 0000 Normal end 1001 Command length exceeds maximum command length. Important Point The Error History Clear command clears the RAM and EEP-ROM error history tables.
Appendix D Memory Card Backup Functions The DeviceNet Unit stores the following setup data in the internal non-volatile memory (EEPROM). • Master scan lists • Slave scan lists • Message monitoring timer lists • Communications cycle time settings • Master/Slave functions enabled/disabled settings Note Backup is possible only when scan lists are enabled. With the CS1 DeviceNet Unit, all this setup data can be backed up to and restored from a Memory Card mounted to the CPU Unit (see note).
Appendix D Memory Card Backup Functions Outline of Functions 1. Backing Up Unit Setup Files Saves all internal Unit setup data to the Memory Card mounted to the CPU Unit. Method: Turn ON the Setup File Backup Switch (word n+1, bit 15) to save the internal Unit setup data to the Memory Card as a Unit Setup File. DeviceNet Unit CPU Unit Unit Setup File Backup switch Memory Card data Backup 2. Restoring Unit Setup Files Restoring Unit Setup Files involves reading the data and setting it to a Unit.
Appendix D Memory Card Backup Functions 3. Saving Files from Configurator to Memory Card Device parameter files (.dvf files) for this DeviceNet Unit that have been created using the Configurator can be saved on the Memory Card via the HMC-AP001 Memory Card Adaptor as file name DNnnBKUP.dvf (where nn is the Unit number in 2-digit hexadecimal).
Appendix E Multi-vendor Applications This appendix provides precautions and reference material needed when using DeviceNet (CompoBus/D) Units as DeviceNet components in a multi-vendor environment. Connecting another Company’s Slaves to an OMRON Master If a Slave has an EDS file, it can be installed in OMRON’s Configurator to enable handling it just like an OMRON Slave. (OMRON’s Configurator already has installed all of the Slave EDS files currently registered with the ODVA.
Appendix E Multi-vendor Applications Master Unit Device Profile General data Compatible DeviceNet Specifications Volume I - Release 2.0 Volume II - Release 2.0 Vendor name OMRON Corporation Vendor ID = 47 Device profile name Communication Adapter Profile number = 12 Manufacturer catalog number Manual number (W267, W347) Manufacturer revision 1.0 Physical conform- Network current consumption ance data Connector type Communications data 24 VDC, 30 mA max.
Appendix E Multi-vendor Applications DeviceNet Object (03 Hex) Item Object class ID content DeviceNet service Parameter option 0EGet Attribute Single No ID content Service 1 MAC ID No Value Service Attribute Yes Set (write) 1 Revision Item Object class Get (read) Attribute Get (read) Yes 2 Set (write) Value No 2 Baud rate Yes No 3 BOI Yes No 0 0 4 Bus–off counter Yes No 5 Allocation information Yes No 6 MAC ID switch changed No No 7 Baud rate switch changed No No 8
Appendix E Multi-vendor Applications Object instance 1 Section Information Max. No. of instances Instance type Explicit Message 1 Production trigger Cyclic Transport type Server Transport class 3 Attribute Service 254 ID content Get (read) Set (write) Value 1 State Yes No --- 2 Instance type Yes No 0 3 Transport class trigger Yes No 83 hex 4 Produced connection ID Yes No --- 5 Consumed connection ID Yes No --- 6 Initial comm.
Appendix E Multi-vendor Applications Object instance 2 Section Information Max. No. of instances Instance type Polled I/O 1 Production trigger Cyclic Transport type Server Transport class 2 Attribute Service ID content Get (read) Set (write) Value 1 State Yes No --- 2 Instance type Yes No 1 3 Transport class trigger Yes No 82 hex 4 Produced connection ID Yes No --- 5 Consumed connection ID Yes No --- 6 Initial comm.
Appendix E Multi-vendor Applications Object instance 3 Section Information Max. No. of instances Instance type Bit Strobed I/O 1 Production trigger Cyclic Transport type Server Transport class 2 Attribute ID content 1 State Service Yes Set (write) No Value --- 2 Instance type Yes No 1 3 Transport class trigger Yes No 82 hex 4 Produced connection ID Yes No --- 5 Consumed connection ID Yes No --- 6 Initial comm.
Appendix E Multi-vendor Applications Object instance 4 Section Information Max. No.
Appendix E Multi-vendor Applications Object instance 5 and above Section Information Max. No. of instances Instance type Explicit Message/ I/O Message 199 Production trigger Cyclic Transport type Server Transport class 0/2/3 Attribute ID content Get (read) 1 State Service Yes Set (write) No Value --- 2 Instance type Yes No See note 1. 3 Transport class trigger Yes No See note 2. 4 Produced connection ID Yes No --- 5 Consumed connection ID Yes No --- 6 Initial comm.
Appendix E Multi-vendor Applications DeviceNet service Object Service instance 1 (CIO area) Object instance 3 (DM area) Service Object instance 4 (WR area) Service Object instance 5 (HR area) Service Object instance 6 (AR area) Service Object instance 7 (TIM/CNT area) Service Service Object instance 820 (EM0 to EMC area) Parameter option 1CBlock String Read Logical Area Address Length 1DBlock StringN Read Logical Area Address Length 1EBlock String Write Logical Area Address 1FBlock Stri
Appendix E Multi-vendor Applications Note The refresh area types are shown in the following table.
Appendix F DeviceNet Explicit Message Send Command for Other Manufacturer Nodes Command Command code Explicit message send 2801 Explicit Message Send (2801) Sends a DeviceNet explicit message to a specified object and receives a response. Command Block 534 bytes max. Class ID Service code Command code Instance ID Service data Destination node address Response Block • When a normal response has been returned for the executed explicit message: 534 bytes max. Command code End code No.
DeviceNet Explicit Message Send Command for Other Manufacturer Nodes Appendix F Parameter Details [Send Destination Node Address] (Command) Specifies the node address of the explicit message destination. The local node DeviceNet Unit is specified for CMND and IOWR instruction control data for Explicit Message Send commands and the actual destination node is specified here. [Service Code] (Command, response) For commands, the service code defined by the DeviceNet is specified.
Index A adaptors remote, 4, 10 allocations See also I/O allocations applicable Units, 6 applications precautions, xiv C C200HW-DRM21-V1 changing ladder programs, 79 comparison, 29 cables I/O Unit Connecting Cable, 14 CIO Area See also I/O allocations cleaning, 225 commands delivering commands through a network, 150 explicit message commands, 168 FINS commands lists, 143, 241 communications, 22, 190, 191 connection types, 127, 130, 235 connectors, 51 cycle time, 81, 190, 232 See also cycle time errors, 224
Index specifications, 34 dimensions, 55 DM Area See also I/O allocations dot indicators See also seven-segment display E EC Directives, xvi EEPROM data, 26, 186, 247 errors, 201 codes, 219 display, 48 communications, 224 error flags, 71, 74, 76, 79 error log functions, 218 error log table, 218 master, 202 memory access, 210 message communications, 139, 140 network, 208 remote I/O communications, 118 scan lists, 224 slave, 217 software switch, 207 Unit, 218 explicit message communications See also communica
Index display section, 27 Master Unit, 200 meaning, 47 message communications errors, 139 seven-segment display, 48 status MS and NS, 47 troubleshooting, 200, 222 inspection, 225 installation, 51 instructions CMND(490), 150, 151 RECV(098), 149, 151 SEND(090), 148, 151 L ladder programs replacing, 233 M maintenance, 225 cleaning, 225 inspection, 225 Master Units, 6, 9 connecting another company’s slave to an OMRON master, 251 device profile, 252 errors, 202 I/O allocations, 82 See also I/O allocations indi
Index S safety precautions, xii scan lists, 99 errors, 224 setup saving setup files, 19, 186, 247 seven-segment display meaning, 48 Slave Units, 7, 9, 20 communications time, 191 connecting an OMRON slave to another company’s configurator, 251 connecting another company’s slave to an OMRON master, 251 environment-resistant, 12 errors, 217 faulty node address display, 48 general-purpose, 10 I/O allocations, 85 See also I/O allocations monitoring, 18 multiple, 19 programmable, 12 programming, 18 remote I/O c
Revision History A manual revision code appears as a suffix to the catalog number on the front cover of the manual. Cat. No. W380-E1-2 Revision code The following table outlines the changes made to the manual during each revision. Page numbers refer to the previous version. Revision code Date 1 October 2000 2 July 2001 Revised content Original production Major revisions to add the CJ-series DeviceNet Unit. “CS1” was changed to “CS” or “CS/CJ” as appropriate and the following changes were made.
