Omron CJ1W-DRM21- Manuals

vii TABLE OF CONTENTS PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi 1 Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii 2 General Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . ....

viii TABLE OF CONTENTS SECTION 5Remote I/O Slave Communications . . . . . . . . . . . . . . . . . 121 5-1 Slave Remote I/O Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 5-2 Fixed Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ...

ix About this Manual: This manual describes the installation and operation of CS1W-DRM21 DeviceNet Unit for SYSMACCJ-series PLCs and the CJ1W-DRM21 DeviceNet Unit for SYSMAC CJ-series PLCs, and includes thesections described below. Please read this manual and all manuals for related products careful...

xi 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 Unitand Programmable Controller (PC) You must read this section and understand the ...

xii Intended Audience 1 1 Intended Audience This manual is intended for the following personnel, who must also haveknowledge 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...

xiii Operating Environment Precautions 4 measure for such problems, external safety measures must be providedto 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 beingturned OFF. As ...

xiv Application Precautions 5 !Caution The operating environment of the PC System can have a large effect on thelongevity and reliability of the system. Improper operating environments canlead to malfunction, failure, and other unforeseeable problems with the PCSystem. Be sure that the operating env...

xv Application Precautions 5 • Double-check all the wiring and connection of terminal blocks and con- nectors 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 cabl...

xvi Conformance to EC Directives 6 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 relatedEMC standards so that they can be more easily built into other devices ormachines. The actu...

xvii Conformance to EC Directives 6 2. Wire the control panel with as thick and short electric lines as possible andground to 100 Ω min. 3. Keep DeviceNet communications cables as short as possible and groundto 100 Ω min. Ferrite Core (Data Line Filter): 0443-164151 (manufacturered by Fair-Rite Prod...

2 Overview of DeviceNet Section 1-1 1-1 Overview of DeviceNet DeviceNet is a multi-bit, multi-vendor network that combines controls and dataon a machine/line-control level and that conforms to DeviceNet open field net-work specifications. Three types of communications are supported: 1) Remote I/O ma...

3 Overview of DeviceNet Section 1-1 1-1-1 Overall System Configuration Note The Configurator is required if more than one Master is connected in a singlenetwork when a CVM1-DRM21-V1 or C200HW-DRM21-V1 is used. Master Features DeviceNet Master Units and DeviceNet Units Suppor t remote I/O communicati...

5 Overview of DeviceNet Section 1-1 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 Mast...

6 Overview of DeviceNet Section 1-1 1-1-2 Applicable Units and DeviceNet Functions Remote I/O Master DeviceNet Unit (Master) CPU Unit Remote I/O communications DeviceNet Slaves Item Master Model Without Configurator With Configurator Max. No. of Slave nodes per Master CS Series CS1W-DRM21 63 nodes C...

8 Overview of DeviceNet Section 1-1 Message Communications Communications Instructions Note FINS message communications are supported between any two PCs with aCS/CJ-series DeviceNet Unit (CS1W-DRM21/CJ1W-DRM21). They are notsuppor ted for PCs with a C200H DeviceNet Master Unit (C200HW-DRM21- Master...

9 Overview of DeviceNet Section 1-1 V1) or a CVM1/CV-series DeviceNet Master Unit (CVM1-DRM21-V1). Referto 6-3 Using FINS Message Communications for details. Communications Software Switches and Communications Status Dedicated words in the CPU Unit are allocated for DeviceNet communicationssoftware ...

11 Overview of DeviceNet Section 1-1 Note For details on Slaves, refer to the DeviceNet (CompoBus/D) Slaves Operation Manual (W347). Sensor Terminals 16 input points (NPN) DRT1-HD16S Connected to photoelectric and proximity sensors with connectors 8 input/8 output points (PNP) DRT1-ND16S Temperature...

12 Overview of DeviceNet Section 1-1 Waterproof and Environment-resistant Slaves (Communications Cable: Round Connectors) Special Slaves (Communications Cable: Normal Square Connectors) Name Appearance I/O points Model number Remarks Waterproof Terminals 4 input points (NPN) DRT1-ID04CL Dust and dri...

13 Overview of DeviceNet Section 1-1 MULTIPLE I/O TERMINAL Units Unit I/O points Words allocated in PC memory I/O connec- tions Unit power supply voltage Installa- tion Model number Remarks Input Output Communications Unit None Two sta-tus words 0 words None 24 VDC (sup-plied from out-side) DIN trac...

14 Overview of DeviceNet Section 1-1 Note The front-panel indicators and other parts of Analog Input Units, Analog Out-put Units, and Counter Units differ from those of other I/O Units. These Unitsbelong to a group called Special I/O Units. One I/O Unit Connecting Cable (cable length 40 mm) is inclu...

15 DeviceNet Unit Features Section 1-2 1-1-5 DeviceNet Configurator Use version 2 of the DeviceNet Configurator for the CS1W-DRM21/CJ1W-DRM21 DeviceNet Unit. Earlier versions of the DeviceNet Configurator do notsuppor t the CS1W-DRM21 DeviceNet Unit. Note The following Boards and Cards can be used. ...

18 DeviceNet Unit Features Section 1-2 CX-Programmer Programming and Monitoring of DeviceNet Slave PCs (Ver. 2.1 or Later) CX-Programmer Ver. 2.1 connected to a serial communications por t on aDeviceNet PC can be used to remotely program and monitor other DeviceNetPCs (i.e., PCs with a CS/CJ-series ...

19 DeviceNet Unit Features Section 1-2 Multiple PCs in a Single Network Multiple DeviceNet Units can be connected in a single network for messagecommunications between PCs as well as for remote I/O communicationsbetween PCs and slaves in multiple groups. This feature allows a DeviceNetto be used as ...

20 DeviceNet Unit Features Section 1-2 a DeviceNet Unit. (See Appendix D Memory Card Backup Function for more details.) 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 daisy-chain line conn...

21 Specifications Section 1-3 1-3 Specifications 1-3-1 DeviceNet Unit Model General Specifications General specifications of the CS/CJ-series DeviceNet Unit conform to thegeneral specifications for the SYSMAC CS/CJ-series CPU Units. Functional and Performance Specifications Applicable PC Unit classi...

28 Specifications Section 1-3 1-3-2 Comparison between CS1W-DRM21 and CJ1W-DRM21 Only the following items are different between the CS1W-DRM21 and theCS1W-DRM21. Otherwise, these Units are functionally the same. Communications power supply voltage 11 to 25 VDC (supplied from the communications conne...

29 Comparison with Previous Models Section 1-4 1-4 Comparison with Previous Models The following table provides a comparison between the CS1W-DRM21DeviceNet Unit and the C200HW-DRM21-V1 DeviceNet Master Unit used in aCS/CJ-series PC. Item C200HW-DRM21-V1 CS1W-DRM21/CJ1W-DRM21 Unit classification C20...

33 Outline of the Configurator Section 1-5 1-5 Outline of the Configurator Allocations for remote I/O communications can be set in any order of nodeaddresses from the Configurator. Users can also set remote I/O communica-tions connections. Device (master/slave) registration, I/O allocations, and oth...

34 Outline of the Configurator Section 1-5 Note 1. Master device parameters used in a scan list are created with either of thefollowing methods. a) Using the Parameter Wizard b) Setting all parameters 2. Connect only one Configurator to each Network. 3. Do not use the Configurator in a location with...

36 Basic Operating Procedures Section 1-6 1-6 Basic Operating Procedures 1-6-1 Network Installation Procedure Note For details on the network installation procedure, refer to the DeviceNet Oper- ation Manual ( W267 ). Only a general description is given here. 1-6-2 Hardware Preparations for Communic...

37 Basic Operating Procedures Section 1-6 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 Progr...

38 Basic Operating Procedures Section 1-6 message communications may not be possible unless the DeviceNet Unitis 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) mu...

39 Basic Operating Procedures Section 1-6 3. Check Unit Status 2 (word n+11, bit 03) from a Programming Device con-nected to the CPU Unit to see if the master function is ON (enabled). If itis enabled, skip step 4 below and proceed to step 5. 4. If the master function is OFF (disabled), turn ON the ...

40 Basic Operating Procedures Section 1-6 2. Check Unit Status 2 (word n+11, bit 07) from a Programming Device con-nected to the CPU Unit to see if the slave function is OFF (disabled). If it isdisabled, skip step 3 below and proceed to step 4. 3. If slave communications are enabled, turn ON the Sla...

42 List of Usage Methods by Purpose Section 1-7 1-7 List of Usage Methods by Purpose Situation Action Page Design Allocating any words for remote I/O In order of node addresses Set using the allocated DM Area words. (Master User Allocations Setup Table and Alloca-tion Size Setup Table) Note Allocati...

46 Nomenclature and Functions Section 2-1 2-1 Nomenclature and Functions 2-1-1 Nomenclature and Functions CS1W-DRM21 CJ1W-DRM21 Indicators The DeviceNet Units are equipped with the following indicators that indicatethe operating status of the node itself and the overall network. 1,2,3... 1. Two stat...

47 Nomenclature and Functions Section 2-1 2-1-2 Status Indicators: MS and NS The MS (Module Status) indicator indicates the status of the node itself andthe 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, orflas...

48 Nomenclature and Functions Section 2-1 2-1-3 Seven-Segment Display In addition to the MS and NS indicators, DeviceNet Units have a 2-digit, 7-segment display that normally indicates the master node address. When anerror occurs, the display will alternate between the error code and the nodeaddress...

49 Nomenclature and Functions Section 2-1 The following diagram shows the alternating error code/ node address display. The master’s error code and master’s node address will be displayed if anerror has occurred at the master. There is no priority in the error codes; all errors that have occurred wi...

50 Nomenclature and Functions Section 2-1 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 beenset on another slave node. 3. If the node address is the same as one set on another node, a node ad-dress duplication error will o...

51 Installing the DeviceNet Unit Section 2-2 Continue/Stop Remote I/O Communications When the DeviceNet Unit is used as a master, pin 3 is used to set whether ornot communications will stop after a communications error. If pin 3 is ON, remote I/O communications will be stopped if one of the follow-i...

52 Installing the DeviceNet Unit Section 2-2 • In the CS-series, up to 16 Units can be mounted to the CS1W-BC @@ 3 CPU Backplane or CS1W-BI @@ 3 Expansion CPU Backplane. • In the CJ-series, up to 16 Units can be mounted to the CPU Unit or Expansion Unit (but no more than 10 Units on either). 2-2-2 M...

53 Installing the DeviceNet Unit Section 2-2 Note When mounting the Unit, provide the clearance shown below to facilitate easymounting or dismounting. CJ-series 1. Carefully align the connectors to mount the DeviceNet Unit. 2. Move the yellow sliders on the top and bottom of the Unit until they clic...

54 Installing the DeviceNet Unit Section 2-2 • Provide separate conduits or ducts for the I/O lines to prevent noise from high-tension lines or power lines. • Leave the label attached to the Unit when wiring. Removing the label may result in malfunction if foreign matter enters the Unit. • Remove th...

55 Installing the DeviceNet Unit Section 2-2 2-2-4 External Dimensions CS1W-DRM21 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 Opera- tion Manual (W393) for the dimensions of the Unit when it is mounted t...

58 Overview of Word Allocations Section 3-1 3-1 Overview of Word Allocations The words shown in the following diagram are allocated according to the unitnumber setting. For each Unit, there are 25 words allocated in the CIO Areaand 100 words allocated in the DM Area. First word allocated in the CIO ...

59 Overview of Word Allocations Section 3-1 3-1-1 Allocated CIO Area Words Software switches, DeviceNet Unit status, and error data are allocated in theCIO Area according to the unit number, as shown below. Software switchesare bits used as commands from the CPU Unit to the DeviceNet Unit toenable e...

65 Allocated CIO Area Words Section 3-2 3-2-2 Software Switches 2 (Word n+1) All switches are turned ON by the user. The Unit automatically turns themOFF after the function is executed. Once a function is set by turning a switchON (except for the switches listed below), it is saved regardless of whe...

75 Allocated CIO Area Words Section 3-2 3-2-8 Master Status 2 (Word n+13) The leftmost eight bits indicate the status of master I/O allocations. Master I/O Allocation Status 10 Fixed Allocation Area Setting Failed Flag ON Unit Indicates that an error has occurred in one of the following operations: ...

78 Allocated CIO Area Words Section 3-2 3-2-10 Slave Status 2 (Word n+15) Master Node Addresses This indicates the node address of the remote master for slave communica-tions. Slave I/O Allocation Status This indicates the I/O allocation status of the slave. 3-2-11 Registered Slave Table (Words n+16...

79 Allocated CIO Area Words Section 3-2 3-2-12 Normal Slave Table (Words n+20 to n+23) This table indicates the slaves that are communicating normally with the mas-ter. The bits correspond to node addresses. The bits for slaves for which nor-mal I/O connections have been made are turned ON in this t...

81 Allocated DM Area Words Section 3-3 3-3 Allocated DM Area Words Data is stored at the offset positions shown in the figure below star ting fromthe first word allocated to the Unit in the DM Area. The first word can be calculated as follows from the unit number setting: First word m = D30000 + (25...

82 Allocated DM Area Words Section 3-3 Note If the setting is smaller than the optimum communications cycle time calcu-lated by the Unit and stored internally in the Unit, then the value calculated bythe Unit will be used. 3-3-2 Master User Allocations Setup Table This table is set by the user to sp...

83 Allocated DM Area Words Section 3-3 Note Make sure the CPU Unit is in PROGRAM mode and the master function isenabled before you set these values. Note See Allocation Size Setup Table (p. 84) for more details on the first word of the allocation size setup table. Areas and Word Ranges Name Range De...

84 Allocated DM Area Words Section 3-3 Setting Results 3-3-3 Allocation Size Setup Table The following allocation size setup tables must be set in the I/O memory in theCPU Unit to use the Master User Allocations Setup Table. The number of bytes set in the allocation size setup table are allocated in...

85 Allocated DM Area Words Section 3-3 Setting Example The following example shows the allocation when the size (bytes) for OUTblock 1 and IN block 1 is set in the allocation size setup table using the speci-fied values. Node address 0: OUT size: 1 byte, IN size: 5 bytesNode address 1: OUT size: 4 b...

87 Allocated DM Area Words Section 3-3 3-3-5 Communications Cycle Time Reference Table This table can be used to access the present, maximum and minimum com-munications cycle times. All the values in this table are cleared from the Unitand the maximum and minimum values are updated with new values w...

88 Allocated DM Area Words Section 3-3 Ranges Areas and Word Ranges 3-3-7 Slave User-set Allocations Reference Table The slave block settings can be accessed in the Slave User-set AllocationsReference Table. A maximum of two OUT and two IN areas (OUT 1, IN 1,OUT 2, and IN 2) can be used for slave co...

89 Allocated DM Area Words Section 3-3 Note OUT2 is not used. Ranges Areas and Word Ranges 3-3-8 Slave Detailed Status The status of the slaves controlled by the master function of the Unit is pro-vided by node address. Each word provides the status of two slaves. Name Range Details OUT 1/2 area See...

92 Master Remote I/O Communications Section 4-1 4-1 Master Remote I/O Communications Remote I/O communications are used to automatically transfer data betweenslaves and the CPU Unit without any special programming in the CPU Unitunder which the Master Unit is mounted. Master Communications Note 1. A...

93 Master Remote I/O Communications Section 4-1 Fixed Allocations Any one of the three areas below can be specified as the words allocated inthe 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 areasshown b...

94 Master Remote I/O Communications Section 4-1 The OUT and IN blocks will be allocated in order of slave node addresses.Each block is a maximum of 500 words. Each address is allocated at least one byte (rightmost). • More than one word is allocated for each slave with more than16 I/O points (accord...

95 Master Remote I/O Communications Section 4-1 4-1-2 Remote I/O Master Specifications Item Specifications Slave alloca-tion methods Fixed allo-cations 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...

96 Master Remote I/O Communications Section 4-1 4-1-3 Precautions on the Number of Master Units The following system configurations can be constructed based on variousnumbers of Master Units when DeviceNet Units are used. Note Only one Master Unit can be connected to a network if the user specifies ...

97 Master Remote I/O Communications Section 4-1 4-1-4 Procedure for Using Remote I/O Master Fixed Allocations for Remote I/O 1,2,3... 1. 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...

98 Master Remote I/O Communications Section 4-1 3. Turn ON the Master Enable Switch (word n bit 06). (The master will remainenabled 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 mas...

99 Scan List Section 4-2 nect/Connect Switch for that slave (words n+6 to n+9). This can be donewhen a slave is replaced or to register a slave in the scan list in prepara-tions to connect it to the network at a later time. The Disconnect/ConnectSwitches, however, are cleared when the power supply i...

100 Scan List Section 4-2 Creating the Scan List The way that a scan list is prepared varies with the allocation method asshown below. Note 1. Be sure to create a scan list before star ting actual system operation. 2. It is still possible to communicate with Units (with the scan list disabled) ifa s...

101 Fixed Allocations Section 4-3 you disable the scan list with a Master Unit that is set for user-setallocations. Par ticularly when multiple Master Units are connectedto a single network, communications will not be performed suc-cessfully if even one Master Unit on the network is operating withth...

102 Fixed Allocations Section 4-3 Note More than one Master Unit can be included in a single PC with fixed alloca-tions, as shown below (3 Units max.). 4-3-2 Procedure Step 1: Place the CPU Unit in PROGRAM mode. Step 2: Turn ON the Master Enable Switch If the master communications have been disabled...

103 Fixed Allocations Section 4-3 Fixed Allocations Area 1 OUT blocks are allocated to slaves from CIO 3200 to CIO 3263 and IN blocksare allocated to slaves from CIO 3300 to CIO 3363. Fixed Allocations Area 2 OUT blocks are allocated to slaves from CIO 3400 to CIO 3463 and IN blocksare allocated to ...

104 Fixed Allocations Section 4-3 Fixed Allocations Area 3 OUT blocks are allocated to slaves from CIO 3600 to CIO 3663 and IN blocksare allocated to slaves from CIO 3700 to CIO 3763. The Slave allocation order is fixed in the output (OUT) and IN blocks star tingfrom address 0. Each address is alloc...

105 Fixed Allocations Section 4-3 4-3-3 Changing System Components The scan list must be cleared in the following situations: • Adding a slave • Removing a slave • Changing a node address Turn OFF the Scan List Clear Switch (word n, bit 01) to clear the scan list.Remote I/O communications will be pe...

106 Fixed Allocations Section 4-3 Resulting Slave Allocation Turn ON the Scan List Enable Switch Turn ON the Scan List Enable Switch (word n, bit 00, CIO 150000 in thisexample). This will create a scan list based on data for slaves that are actuallyonline and will star t remote I/O communications wi...

107 User-set Allocations Section 4-4 4-4 User-set Allocations With a CS/CJ-series DeviceNet Unit, remote I/O communications slaves canbe allocated in any area (CIO, WR, HR, DM, or EM) using one of the followingmethods. • Setting through the allocated DM Area words (Master User Allocations Table) • S...

109 User-set Allocations Section 4-4 Procedure Step 1: Turn ON the Master Enable Switch Make sure that master communications have disabled by checking to see ifMaster Enable Function Flag (word n+11, bit 03) is OFF and then turn ON theMaster Enable Switch (word n+14, bit 06) to enable master communi...

110 User-set Allocations Section 4-4 Step 4: Turn ON the Slave User Allocations Switch Turn ON the Slave User allocations Switch (word n, bit 11). This will make theDeviceNet Unit read allocation results data for the slaves above from the CPUUnit and create a scan list based on data for slaves that ...

114 User-set Allocations Section 4-4 Procedure Step 1 Set the area, star t word, and words allocated for each block using the Config-urator. Step 2 Allocate words to all node addresses in each block as shown below using theConfigurator. • Each address is allocated at least one byte (rightmost or lef...

116 Starting and Stopping Remote I/O Communications Section 4-5 Configurator Setting Methods Refer to the DeviceNet Configurator Operation Manual (W382) for setting methods. 4-5 Starting and Stopping Remote I/O Communications 4-5-1 Starting Remote I/O Communications Remote I/O communications start a...

117 Example of Ladder Programming for Remote I/O Communications Section 4-6 Note Even if there is a communications error with the slave, the slave input data issaved in the allocated area. To prevent operating errors, make the ladder program so that no slave I/O pro-cessing will occur when the Unit ...

118 Errors that May Occur in Remote I/O Communications Section 4-7 4-7 Errors that May Occur in Remote I/O Communications The following errors may occur during remote I/O communications. Condition Error Details Results Indicators 7- segment display Error occurs in fixed allo-cations with the scan li...

122 Slave Remote I/O Communications Section 5-1 5-1 Slave Remote I/O Communications A CS/CJ-series DeviceNet Unit can function as a Slave Unit in remote I/Ocommunications and a single CS/CJ-series DeviceNet Unit can function asboth a Master Unit and a Slave Unit. This section describes Slave communi...

123 Slave Remote I/O Communications Section 5-1 5-1-2 Remote I/O and Slave Communications Specifications 5-1-3 Procedures for Using Remote I/O Slave Communications Fixed Allocations for Remote I/O 1,2,3... 1. Turn ON the communications, slave, and PC power supplies. Note Turn ON the communications p...

124 Slave Remote I/O Communications Section 5-1 munications, allocate areas, and then enable slave communications. The allo-cated 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,...

127 User-set Allocations Section 5-3 2. Only two blocks (OUT 1 and IN 1) can be allocated when setting are madewith the allocated DM Area words area, but there are three blocks (OUT 1and IN 1/2) available with the Configurator. Setting through the Allocated DM Area Words (Slave User Allocations Tabl...

128 User-set Allocations Section 5-3 • Areas and Word Ranges for the OUT 1/IN 1 Areas Step 3: Turn ON the Slave User Allocations Switch Turn ON the Slave User Allocations Switch (word n+1, bit 11). Step 4: Turn ON the Slave Enable Switch Turn ON the Slave Enable Switch (word n+1, bit 06). This will ...

130 User-set Allocations Section 5-3 Setting through the Configuration A maximum of three blocks can be allocated at any locations in I/O memoryfor the output (OUT) area block 1, input (IN) area block 1, and input (IN) areablock 2. The block allocation order and block allocation areas can be set as ...

134 Overview Section 6-1 6-1 Overview Message communications enable messages to be set between nodes on aDeviceNet network when required by system conditions. The messages canbe sent between PCs, between an OMRON PC and a master made byanother company, or between slaves. They can be used to send/rec...

135 Overview Section 6-1 Overall Structure Note If only the message communications function is being used and the remote I/O communications function is not being used, message communications arepossible even if the master function is disabled. In this case, it is not neces-sary to register a scan li...

136 Overview Section 6-1 Note 1. The DeviceNet Unit must be registered in the local network routing table ofthe CS/CJ-series PC when two or more Communications Units (includingthe DeviceNet Unit) are mounted to a CS/CJ-series PC. The commandswill not be sent if the Unit is not registered in the rout...

137 Overview Section 6-1 Sending FINS Message Communications Receiving FINS Message Communications Note C200H-series DeviceNet Master Units (C200H-DRM21-V1) and CVM1/CV-series DeviceNet Master Units (CVM1-DRM21-V1) both suppor t FINS mes-sage communications but it is executed by a special OMRON meth...

138 Overview Section 6-1 Note A specific FINS command (command 2801) is used to send explicit mes-sages. Note A specific FINS command (command 2801) is used to send explicit messages. Note This CS/CJ-series DeviceNet Unit (CS1W-DRM21 or CJ1W-DRM21) containsa PLC Object so that the I/O memory of the ...

139 Overview Section 6-1 6-1-5 Message Communications Error Indications There are two ways to obtain information on communications errors that occurin message communications: 1) Using the error history in the DeviceNet Unitand 2) Using DeviceNet Unit displays, indicators, and Master Status Areas. 1,...

140 Overview Section 6-1 6-1-6 Message Monitoring Timer A message monitoring timer monitors responses for the DeviceNet Unit. Atimer can be set for each device that will be communicated with (each mes-sage destination). Message monitoring timers are supported for both explicit message and FINSmessag...

141 FINS Commands and Responses Section 6-2 termeasures and errors recorded in error history that are not shown by theindicators. Note 1. The 7-segment display alternately displays the error and the master nodeaddress where the error occurred. 2. The send response message or reception response messa...

142 FINS Commands and Responses Section 6-2 Refer to SYSMAC CS/CJ Series Communication Commands Reference Man- ual (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-seriesPCs. Send/receive FINS command...

143 FINS Commands and Responses Section 6-2 The main response codes are listed below. Refer to SYSMAC CS/CJ Series Communication Commands Reference Manual (W342) for further details on response codes, including sub-response codes (SRES). 6-2-3 Units Supporting FINS Communications The parameters used...

145 Using FINS Message Communications Section 6-3 Commands Addressed to DeviceNet Units Command to Send Explicit DeviceNet Messages 6-3 Using FINS Message Communications There are two instructions that can be executed to send and receive data fromCS/CJ-series CPU Units: SEND(090) and RECV(098). Ther...

146 Using FINS Message Communications Section 6-3 3. In all cases other than the following two exceptions, a local network tablemust 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...

147 Using FINS Message Communications Section 6-3 The unit number of the DeviceNet Unit as a CPU Bus Unit is the number seton the rotary switches on the front panel (0 to 15). The network address is theaddress of the Network to which the CPU Bus Unit is connected (1 to 127).The network address is sp...

148 Using FINS Message Communications Section 6-3 4. Use the left-side table to create the local network table. Input the unit num-bers and corresponding local network addresses. 5. Use the right-side table to create the relay network table. Input the final net-work addresses and corresponding relay...

149 Using FINS Message Communications Section 6-3 Note 1. Indicates a Unit as shown in the following table. 2. Values of $00 to $3F indicate nodes 0 to 63. 3. Designates the length of time that the PC retries transmission when bit 15of C+3 is OFF and no response is received. The default value is $00...

150 Using FINS Message Communications Section 6-3 Note 1. Indicates a Unit as shown in the following table. 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 transmis-sion when bit 15 of C+3 is OFF and no response is received. The d...

151 Using FINS Message Communications Section 6-3 Note 1. Indicates a Unit as shown in the following table. 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 transmis-sion when bit 15 of C+3 is OFF and no response is received. The d...

152 Using FINS Message Communications Section 6-3 Communications Flags Communications Flag Operation • The Network Enabled Flag turns OFF when instructions are being sent or received (from when the instruction is issued until the response isreceived) and turns ON when the execution has been complete...

153 Using FINS Message Communications Section 6-3 in the following table. Communications Instructions Completion Codes The status at the completion of the execution of network communicationsinstructions is shown at the words indicated in the following table, as FINScompletion codes. During execution...

154 Using FINS Message Communications Section 6-3 Note 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 howmany banks can be used. 3. Do not exceed th...

155 Using FINS Message Communications Section 6-3 Program Example (021)MOV A503 D00006 11 A202 (021)MOV #0005 D00000 (021)MOV #0001 D00001 (021)MOV #0600 D00002 (021)MOV #0000 D00003 (025)ASL 0000 000 00 A202 00 0000 01 (071)BSET #1234 D01000 D01004 Sets 1234 in D01000 to D01004. Places data into co...

156 Using FINS Message Communications Section 6-3 Example 2: Sending a FINS Command Using CMND 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 withnode address 06. • The MEMORY AREA READ command (01 01) i...

157 Using FINS Message Communications Section 6-3 Example Program 6-3-6 Connecting Networks for FINS Communications CS/CJ-series DeviceNet Units can perform FINS communications betweennetworks. DeviceNet networks are handled the same way as other FA net-works such as Controller Link or SYSMAC LINK, ...

158 Sending Explicit Messages Section 6-4 When connecting networks, routing tables must be registered for the PC CPUUnits on all networks. When connecting two or more communication units (including the DeviceNetUnit) to a CS/CJ-series CPU Unit, the DeviceNet Unit must be registered inthe CS/CJ-serie...

161 Sending Explicit Messages Section 6-4 Parameters Destination node address (command): The node address of the destination of the explicit message. (The node address of the local DeviceNet Unit isspecified in the control data for the CMND(490) or IOWR instruction, but thenode address of the actual...

162 Sending Explicit Messages Section 6-4 D: First response word C: First control data word Command data is set in order star ting with the word specified for theCMND(490) operand S (first command word) and continuing with words withhigher addresses in I/O memory in the command block format. Command...

163 Sending Explicit Messages Section 6-4 The response format data in service data that is in word (2-byte) or double-word (4-byte) units, such as word data and ERROR CLEAR codes, is alsospecified from low to high bytes in response block format Example: Sending Explicit Messages Using CMND(490) Oper...

165 Receiving Explicit Messages Section 6-5 Program Example 6-5 Receiving Explicit Messages This CS/CJ-series DeviceNet Unit contains a PLC Object. The Unit willreceive messages addressed to the PLC Object, process service requestsaddressed to the CPU Unit, and return responses. The following servic...

166 Receiving Explicit Messages Section 6-5 • PCs with CVM1/CV-series DeviceNet Master Units (CVM1-DRM21-V1) • PCs with CS/CJ-series DeviceNet Units Example Note Status and the I/O memory read/write operations cannot be performed forPCs with a C200H-series or CVM1/CV-series DeviceNet Master Units. T...

168 Receiving Explicit Messages Section 6-5 CPU Information Read (Service Code: 0E Hex) Reads CPU Unit information, including operating mode, fatal/non-fatal errors,and the CPU Unit model. Command Block Response Block Parameters Destination node address (command): The node address of the CS/CJ- seri...

169 Receiving Explicit Messages Section 6-5 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 for-mat, as follows: 0001 Hex: PROGRAM mode; 0002 Hex: MONITOR m...

170 Receiving Explicit Messages Section 6-5 Response Block Parameters Destination node address (command): The node address of the CS/CJ- series DeviceNet Unit to which to write data, specified in 1-byte (2 digit) hexa-decimal. Service code (command, response): 10 Hex is specified for commands. For r...

171 Receiving Explicit Messages Section 6-5 Note Error clear codes are 1-word (2-byte) data, so the above codes are specified with the low byte first. The low to high bytes for the abovecodes are set as high to low bytes in I/O memory, when setting thecodes as data for operand S of CMND(490). For ex...

172 Receiving Explicit Messages Section 6-5 CPU Unit Status Read (Service Code: 40 Hex) This PLC Object ser vice reads status details (operation status, operatingmode, fatal and non-fatal errors, etc.) from the CPU Unit. Command Block Response Block Parameters Destination node address (command): The...

173 Receiving Explicit Messages Section 6-5 • 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 mod...

174 Receiving Explicit Messages Section 6-5 • Message Exists/Does Not Exist: When the MSG instruction is executed by the CPU Unit, the bit corresponding to the message number will turnON and be returned in 2 bytes (from low to high bytes). • Error Code : The highest priority error code of the errors...

176 Receiving Explicit Messages Section 6-5 Word Data Read (Service Code: 1D Hex) Word Data Read reads I/O memor y area data in CPU Units with a CS/CJ-series DeviceNet Units. The read word data is in word units. The responseblock is returned from low to high bytes. Command Block Response Block Param...

177 Receiving Explicit Messages Section 6-5 No of Read Words (command): The number of words of read data is speci- fied in 1-byte (2-digit) hexadecimal. The range is 01 to 64 Hex (1 to 100 deci-mal). No. of bytes received (response): The number of bytes received from the destination node address (re...

178 Receiving Explicit Messages Section 6-5 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. Address L, Address H (command): The address of the first word to which the data will be written is specified in he...

182 Connecting to the CX-Programmer via the DeviceNet Section 7-1 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 aPC containing a CS/CJ-series DeviceNet Unit to form an online connection,via the DeviceNet, to other PC CP...

183 Connecting to the CX-Programmer via the DeviceNet Section 7-1 7-1-1 Setting Node Addresses When the CX-Programmer is connected online, it uses FINS message com-munications. It is thus necessary to set the node address to a number otherthan 0 for DeviceNet Units mounted to the target PC, DeviceNe...

184 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 thenode address and click on the Edit Button. A dialogue box like the one be- low will appear. 3. Input the value, then click on the OK Button. Note To set the...

185 Connecting to the CX-Programmer via the DeviceNet Section 7-1 response monitor time in the CMND/SEND/RECV instruction to be thesame 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-ou...

187 Memory Card Backup Functions Section 7-2 7-2-1 Outline of Functions 1. Backing Up Unit Setup Files Saves all internal Unit setup data to the Memory Card mounted to the CPUUnit.Method: Turn ON the Setup File Backup Switch (word n+1, bit 15) to save theinternal Unit setup data to the Memory Card a...

188 Memory Card Backup Functions Section 7-2 Note If there is an error in the setup data or if the file could not be read, the FileRead/Write Error bit in Unit Status 2 (word n + 11, bit 08) will turn ON. 3. Saving Files from Configurator to Memory Card Device parameter files (.dvf files) for this D...

190 Remote I/O Communications Characteristics Section 8-1 8-1 Remote I/O Communications Characteristics This section describes the characteristics of remote I/O communicationswhen the DeviceNet Unit is used as a master in combination with OMRON’sslaves. Use this section for reference when planning o...

191 Remote I/O Communications Characteristics Section 8-1 Communications Cycle Time Calculation Use the equations shown below to calculate the communications cycle time(T RM ) for a network with one Master. Note that if the result of this calculation is less than 2 ms, the actual communications cycl...

192 Remote I/O Communications Characteristics Section 8-1 Slaves with More Than 8 Bytes of Input or Out put T RT = T OH + T BYTE-IN × B IN + T BYTE-OUT × B OUT [ms] T OH : Protocol overhead T BYTE-IN : The input byte transmission time B IN : The number of input words T BYTE-OUT : The output byte tra...

194 Remote I/O Communications Characteristics Section 8-1 Minimum I/O Response Time The minimum I/O response time occurs when the Slave’s I/O refreshing isexecuted just after the input signal is received by the DeviceNet Unit and theoutput signal is output at the beginning of the next I/O refresh cy...

195 Remote I/O Communications Characteristics Section 8-1 Note Although in the above diagram the Slaves are separated into two groups forconvenience, 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 ...

196 Message Communications Section 8-2 This programming is for a DeviceNet Unit with a unit number of 00. 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 isturned ON or restar t...

197 Message Communications Section 8-2 Note 1. If the CPU Unit attempts to send another message or receives a messagefrom another node within the message communications time, the secondmessage or the message being received from another node may be de-stroyed. Never execute a second communications in...

200 Troubleshooting with the DeviceNet Unit Indicators Section 9-1 9-1 Troubleshooting with the DeviceNet Unit Indicators 9-1-1 Determining Operating Status from the Indicators The following table shows the status of the MS and NS indicators and the 7-segment display during normal operation. Indicat...

201 Troubleshooting with the DeviceNet Unit Indicators Section 9-1 9-1-2 Troubleshooting Errors Occurring in the DeviceNet Unit Note 1. The 7-segment display will alternate between the Unit’s node address andthe code given in the tables in this section. 2. When a (master function) structure error or...

202 Troubleshooting with the DeviceNet Unit Indicators Section 9-1 remote I/O communications for a communications error, two errors can bedisplayed: The slave’s communications error and its most recent error. Master Errors Remote I/O Communications Stopped by a Communications Error Likely Cause Pin ...

203 Troubleshooting with the DeviceNet Unit Indicators Section 9-1 Correction Set the slaves’ node addresses again. Structure Error: I/O Area Range Exceeded Likely Cause The slave’s I/O area isn’t within the allowed range. (Occurs with the scan listdisabled.) DeviceNet Unit Response Records the erro...

205 Troubleshooting with the DeviceNet Unit Indicators Section 9-1 Correction Inspect the slave and then create the scan list again. Verification Error:I/O Size Mismatch Likely Cause The slave’s I/O data size does not match the registered scan list. (Occurs withthe scan list enabled.) DeviceNet Unit...

207 Troubleshooting with the DeviceNet Unit Indicators Section 9-1 • Matching master and slave baud rates • Proper cable lengths (trunk and branch lines) • Broken or loose cables • Installation of terminators at both ends of the trunk line • Excessive noise Software Switch Setting Errors CPU Unit St...

208 Troubleshooting with the DeviceNet Unit Indicators Section 9-1 Likely Cause The setting operation failed because a structure error occurred. DeviceNet Unit Response The only response is the error code displayed on the 7-segment display. Theerror display will be cleared the next time that a setti...

210 Troubleshooting with the DeviceNet Unit Indicators Section 9-1 DeviceNet Unit Response Records the error in the error log. • The Unit will go off–line and communications will be disabled. Error responses will be returned to all communications requests. • The exchange of data with the CPU Unit wi...

211 Troubleshooting with the DeviceNet Unit Indicators Section 9-1 DeviceNet Unit Response Records the error in the error log.Operation will continue using the default message monitoring timer values. Flags Allocated for C200H DeviceNet Master Unit (CIO n+24) Bit 14 (Error Flag) and bit 03 (the Stru...

212 Troubleshooting with the DeviceNet Unit Indicators Section 9-1 Correction Clear the scan list and register the scan list again or use the Configurator toreset the master scan list. Memory Access Error Likely Cause An error occurred in the Unit’s non-volatile memory itself. This error will occuri...

213 Troubleshooting with the DeviceNet Unit Indicators Section 9-1 CIO Area Flags Allocated to DeviceNet Unit Bits 00 and 04 of n+10 (the Unit Error Flag and Unit Memory Error Flag) willbe ON. Correction Replace the Unit if the error recurs. CPU Unit Exchange Errors Unit Number duplication Likely Ca...

214 Troubleshooting with the DeviceNet Unit Indicators Section 9-1 DeviceNet Unit Response Stops operation. Correction Set the communications speed correctly and restart the DeviceNet Units. CPU Unit Faulty (H6) DeviceNet Unit Response Records the error in the error log. (The time information is set...

215 Troubleshooting with the DeviceNet Unit Indicators Section 9-1 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...

217 Troubleshooting with the DeviceNet Unit Indicators Section 9-1 • Returns an error response (0302 Hex) to commands requiring a re- sponse. • Discards other frames and stores an error record (010B Hex) in the er- ror log. Flags Allocated for C200H DeviceNet Master Unit (CIO n+24) There is no statu...

218 Error Log Functions Section 9-2 • Installation of terminators at both ends of the trunk line • Excessive noise Unit Errors Special Unit Error 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...

219 Error Log Functions Section 9-2 When using the Configurator, the error log can be monitored with the mastererror history read operation. With the Configurator, the error log can only bemonitored and the data cannot be saved. Time Information The CPU Unit’s time information is used for the time s...

222 Troubleshooting Section 9-3 9-3 Troubleshooting 9-3-1 CPU Unit’s ERR/ALM Indicator Lit or Flashing Use the following table to troubleshoot the network when the DeviceNet Unitis mounted and the CPU Unit’s ERR/ALM indicator is lit or flashing. Note Refer to the CS1 Series CPU Unit Operation Manual...

223 Troubleshooting Section 9-3 9-3-3 I/O Link Problems Use the following table to troubleshoot I/O Link problems. 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’...

224 Troubleshooting Section 9-3 9-3-4 Communications Error Operation Settings Use the following table to correct problems with the DIP switch setting for con-tinuing/stopping communications for errors. 9-3-5 Scan List Problems Use the following table to troubleshoot scan list problems. Error Probabl...

225 Maintenance and Replacement Section 9-4 9-4 Maintenance and Replacement This section describes the routine cleaning and inspection recommended asregular maintenance as well as the Unit replacement procedure required if aDeviceNet Unit fails. 9-4-1 Cleaning Clean the DeviceNet Units regularly as ...

226 Maintenance and Replacement Section 9-4 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 recom- mend having spare Units available to restore network operation as quickly asp...

227 Maintenance and Replacement Section 9-4 Creating a New Network File Use the following procedure to write the settings to the DeviceNet Unit from anetwork 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 disp...

229 Appendix A Allocation Differences from C200H DeviceNet Master Units The following table shows the CS1W-DRM21/CJ1W-DRM21 DeviceNet Unit allocation areas that correspondto the C200HW-DRM21-V1 DeviceNet Master Unit allocation areas. Note The following table does not include the allocation areas tha...

230 Allocation Differences from C200H DeviceNet Master Units Appendix A Status Areas Master Status Area 1 An area with the exact same bit configuration as Master Status area 1 used for C200H DeviceNet Master Units,was set up. This area is called the Master Replacement Status 1. • The following table...

232 Allocation Differences from C200H DeviceNet Master Units Appendix A Master Status Area 2 Communications Cycle Time Present Value Registered Slave Table Name C200H DeviceNet Master Unit CS/CJ-series DeviceNet Unit Contents for CS/CJ- series DeviceNet Unit Differences from C200H DeviceNet Master U...

233 Allocation Differences from C200H DeviceNet Master Units Appendix A Normal Slave Table Replacing Ladder Programs from C200HW-DRM21-V1 If ladder programs have already been created for C200H DeviceNet Master Unit (C200HW-DRM21-V1)mounted to CS/CJ-series CPU Units, the ladder programs must be chang...

234 Allocation Differences from C200H DeviceNet Master Units Appendix A Replace the addresses as shown in the following table. Message Communications in Ladder Programs Note If there is a routing table in the CS/CJ-series CPU Unit, the DeviceNet Unit must be registered in it whenreplacing the C200HW...

235 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, ...

236 DeviceNet Connections Appendix B Connections Using Allocations Setting Connection Type The settings for remote I/O communications connections differ depending on the allocation method, as outlinedbelow. Fixed Allocation or User-set Allocations Using Allocated DM Area Words The Master CS/CJ-serie...

237 DeviceNet Connections Appendix B Note 1. Output data using poll connections and output data using COS or cyclic connections are transmittedusing the same frame. Therefore set the same output size (bytes) when combining poll and COS orpoll and cyclic. 2. The COS/cyclic hear tbeat timer is the sma...

238 DeviceNet Connections Appendix B Master COS Send Switch COS transmission is possible only for User-set allocations using the Configurator. When required, remote I/O output data can be output from the master to a specified slave. Output data can be sent at the communications cycle timing to the s...

241 Appendix C FINS Commands and Responses for DeviceNet Units List of Command Codes Refer to SYSMAC CS/CJ Series Communication Commands Reference Man- ual (W342) for details on end codes. RESET (0403) Resets (restar ts) the DeviceNet Unit. Command Block Resets the DeviceNet Unit. Response Block The...

242 FINS Commands and Responses for DeviceNet Units Appendix C • Baud rate Command Block Response Block End Codes Parameter Details [Model, Version] (Response)The DeviceNet Unit model and version are returned as outlined below in 20-byte ASCII code. If the data is less than 20 bytes, the remaining b...

243 FINS Commands and Responses for DeviceNet Units Appendix C Response Block End Codes Parameter Details [Operation status, Units status 1, Unit status 2, Master function status 1, Mas-ter function status 2, Slave function status 1, Slave function status 2](response) • Operation Status Fixed at 01 ...

244 FINS Commands and Responses for DeviceNet Units Appendix C For commands, the data to be sent to the specified node is specified, with amaximum 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 comma...

245 FINS Commands and Responses for DeviceNet Units Appendix C Returns the error history for the number specified by Read Record No., inorder from the Read Star t Record No. The total number of Error Histor y Databytes is 10 × Read Record No. One record of error history data is structured in 10 byte...

246 FINS Commands and Responses for DeviceNet Units Appendix C End Codes Important Point The Error History Clear command clears the RAM and EEP-ROM error his-tory tables. End code (hex) Contents 0000 Normal end 1001 Command length exceeds maximum command length.

247 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...

251 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 install...

252 Multi-vendor Applications Appendix E Master Unit Device Profile Object Mounting Identity Object (01 Hex) Message Router Object (02 Hex) General data Compatible DeviceNet Specifications Volume I - Release 2.0Volume II - Release 2.0 Vendor name OMRON Corporation Vendor ID = 47 Device profile name ...

255 Multi-vendor Applications Appendix E Note 1. Number of input bytes used by Slave. 2. Number of output bytes used by Slave. Object instance 2 Section Information Max. No. of instances Instance type Polled I/O 1 Produc-tion trig-ger Cyclic Transport type Server Transport class 2 Attribute ID conte...

260 Multi-vendor Applications Appendix E Note The refresh area types are shown in the following table. PC area Refresh area type Refresh address CIO 1 CIO 0000 to CIO 6143 DM 3 D00000 to D32767 WR 4 W000 to W511 HE 5 H 000 to H511 EM (bank 0) 8 E0_00000 to E0_32767 EM (bank 1) 9 E1_00000 to E1_32767...

261 Appendix F DeviceNet Explicit Message Send Command for Other Manufacturer Nodes Explicit Message Send (2801) Sends a DeviceNet explicit message to a specified object and receives aresponse. Command Block Response Block • When a normal response has been returned for the executed explicit message:...

262 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 instructioncontrol data for Expl...

263 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 com...

267 Revision History A manual revision code appears as a suffix to the catalog number on the front cover of the manual. The following table outlines the changes made to the manual during each revision. Page numbers refer to theprevious version. Revision code Date Revised content 1 October 2000 Origi...

vii TABLE OF CONTENTS PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi 1 Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii 2 General Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . ....

viii TABLE OF CONTENTS SECTION 5Remote I/O Slave Communications . . . . . . . . . . . . . . . . . 121 5-1 Slave Remote I/O Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 5-2 Fixed Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ...

ix About this Manual: This manual describes the installation and operation of CS1W-DRM21 DeviceNet Unit for SYSMACCJ-series PLCs and the CJ1W-DRM21 DeviceNet Unit for SYSMAC CJ-series PLCs, and includes thesections described below. Please read this manual and all manuals for related products careful...

xi 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 Unitand Programmable Controller (PC) You must read this section and understand the ...

xii Intended Audience 1 1 Intended Audience This manual is intended for the following personnel, who must also haveknowledge 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...

xiii Operating Environment Precautions 4 measure for such problems, external safety measures must be providedto 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 beingturned OFF. As ...

xiv Application Precautions 5 !Caution The operating environment of the PC System can have a large effect on thelongevity and reliability of the system. Improper operating environments canlead to malfunction, failure, and other unforeseeable problems with the PCSystem. Be sure that the operating env...

xv Application Precautions 5 • Double-check all the wiring and connection of terminal blocks and con- nectors 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 cabl...

xvi Conformance to EC Directives 6 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 relatedEMC standards so that they can be more easily built into other devices ormachines. The actu...

xvii Conformance to EC Directives 6 2. Wire the control panel with as thick and short electric lines as possible andground to 100 Ω min. 3. Keep DeviceNet communications cables as short as possible and groundto 100 Ω min. Ferrite Core (Data Line Filter): 0443-164151 (manufacturered by Fair-Rite Prod...

2 Overview of DeviceNet Section 1-1 1-1 Overview of DeviceNet DeviceNet is a multi-bit, multi-vendor network that combines controls and dataon a machine/line-control level and that conforms to DeviceNet open field net-work specifications. Three types of communications are supported: 1) Remote I/O ma...

3 Overview of DeviceNet Section 1-1 1-1-1 Overall System Configuration Note The Configurator is required if more than one Master is connected in a singlenetwork when a CVM1-DRM21-V1 or C200HW-DRM21-V1 is used. Master Features DeviceNet Master Units and DeviceNet Units Suppor t remote I/O communicati...

5 Overview of DeviceNet Section 1-1 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 Mast...

6 Overview of DeviceNet Section 1-1 1-1-2 Applicable Units and DeviceNet Functions Remote I/O Master DeviceNet Unit (Master) CPU Unit Remote I/O communications DeviceNet Slaves Item Master Model Without Configurator With Configurator Max. No. of Slave nodes per Master CS Series CS1W-DRM21 63 nodes C...

8 Overview of DeviceNet Section 1-1 Message Communications Communications Instructions Note FINS message communications are supported between any two PCs with aCS/CJ-series DeviceNet Unit (CS1W-DRM21/CJ1W-DRM21). They are notsuppor ted for PCs with a C200H DeviceNet Master Unit (C200HW-DRM21- Master...

9 Overview of DeviceNet Section 1-1 V1) or a CVM1/CV-series DeviceNet Master Unit (CVM1-DRM21-V1). Referto 6-3 Using FINS Message Communications for details. Communications Software Switches and Communications Status Dedicated words in the CPU Unit are allocated for DeviceNet communicationssoftware ...

11 Overview of DeviceNet Section 1-1 Note For details on Slaves, refer to the DeviceNet (CompoBus/D) Slaves Operation Manual (W347). Sensor Terminals 16 input points (NPN) DRT1-HD16S Connected to photoelectric and proximity sensors with connectors 8 input/8 output points (PNP) DRT1-ND16S Temperature...

12 Overview of DeviceNet Section 1-1 Waterproof and Environment-resistant Slaves (Communications Cable: Round Connectors) Special Slaves (Communications Cable: Normal Square Connectors) Name Appearance I/O points Model number Remarks Waterproof Terminals 4 input points (NPN) DRT1-ID04CL Dust and dri...

13 Overview of DeviceNet Section 1-1 MULTIPLE I/O TERMINAL Units Unit I/O points Words allocated in PC memory I/O connec- tions Unit power supply voltage Installa- tion Model number Remarks Input Output Communications Unit None Two sta-tus words 0 words None 24 VDC (sup-plied from out-side) DIN trac...

14 Overview of DeviceNet Section 1-1 Note The front-panel indicators and other parts of Analog Input Units, Analog Out-put Units, and Counter Units differ from those of other I/O Units. These Unitsbelong to a group called Special I/O Units. One I/O Unit Connecting Cable (cable length 40 mm) is inclu...

15 DeviceNet Unit Features Section 1-2 1-1-5 DeviceNet Configurator Use version 2 of the DeviceNet Configurator for the CS1W-DRM21/CJ1W-DRM21 DeviceNet Unit. Earlier versions of the DeviceNet Configurator do notsuppor t the CS1W-DRM21 DeviceNet Unit. Note The following Boards and Cards can be used. ...

18 DeviceNet Unit Features Section 1-2 CX-Programmer Programming and Monitoring of DeviceNet Slave PCs (Ver. 2.1 or Later) CX-Programmer Ver. 2.1 connected to a serial communications por t on aDeviceNet PC can be used to remotely program and monitor other DeviceNetPCs (i.e., PCs with a CS/CJ-series ...

19 DeviceNet Unit Features Section 1-2 Multiple PCs in a Single Network Multiple DeviceNet Units can be connected in a single network for messagecommunications between PCs as well as for remote I/O communicationsbetween PCs and slaves in multiple groups. This feature allows a DeviceNetto be used as ...

20 DeviceNet Unit Features Section 1-2 a DeviceNet Unit. (See Appendix D Memory Card Backup Function for more details.) 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 daisy-chain line conn...

21 Specifications Section 1-3 1-3 Specifications 1-3-1 DeviceNet Unit Model General Specifications General specifications of the CS/CJ-series DeviceNet Unit conform to thegeneral specifications for the SYSMAC CS/CJ-series CPU Units. Functional and Performance Specifications Applicable PC Unit classi...

28 Specifications Section 1-3 1-3-2 Comparison between CS1W-DRM21 and CJ1W-DRM21 Only the following items are different between the CS1W-DRM21 and theCS1W-DRM21. Otherwise, these Units are functionally the same. Communications power supply voltage 11 to 25 VDC (supplied from the communications conne...

29 Comparison with Previous Models Section 1-4 1-4 Comparison with Previous Models The following table provides a comparison between the CS1W-DRM21DeviceNet Unit and the C200HW-DRM21-V1 DeviceNet Master Unit used in aCS/CJ-series PC. Item C200HW-DRM21-V1 CS1W-DRM21/CJ1W-DRM21 Unit classification C20...

33 Outline of the Configurator Section 1-5 1-5 Outline of the Configurator Allocations for remote I/O communications can be set in any order of nodeaddresses from the Configurator. Users can also set remote I/O communica-tions connections. Device (master/slave) registration, I/O allocations, and oth...

34 Outline of the Configurator Section 1-5 Note 1. Master device parameters used in a scan list are created with either of thefollowing methods. a) Using the Parameter Wizard b) Setting all parameters 2. Connect only one Configurator to each Network. 3. Do not use the Configurator in a location with...

36 Basic Operating Procedures Section 1-6 1-6 Basic Operating Procedures 1-6-1 Network Installation Procedure Note For details on the network installation procedure, refer to the DeviceNet Oper- ation Manual ( W267 ). Only a general description is given here. 1-6-2 Hardware Preparations for Communic...

37 Basic Operating Procedures Section 1-6 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 Progr...

38 Basic Operating Procedures Section 1-6 message communications may not be possible unless the DeviceNet Unitis 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) mu...

39 Basic Operating Procedures Section 1-6 3. Check Unit Status 2 (word n+11, bit 03) from a Programming Device con-nected to the CPU Unit to see if the master function is ON (enabled). If itis enabled, skip step 4 below and proceed to step 5. 4. If the master function is OFF (disabled), turn ON the ...

40 Basic Operating Procedures Section 1-6 2. Check Unit Status 2 (word n+11, bit 07) from a Programming Device con-nected to the CPU Unit to see if the slave function is OFF (disabled). If it isdisabled, skip step 3 below and proceed to step 4. 3. If slave communications are enabled, turn ON the Sla...

42 List of Usage Methods by Purpose Section 1-7 1-7 List of Usage Methods by Purpose Situation Action Page Design Allocating any words for remote I/O In order of node addresses Set using the allocated DM Area words. (Master User Allocations Setup Table and Alloca-tion Size Setup Table) Note Allocati...

46 Nomenclature and Functions Section 2-1 2-1 Nomenclature and Functions 2-1-1 Nomenclature and Functions CS1W-DRM21 CJ1W-DRM21 Indicators The DeviceNet Units are equipped with the following indicators that indicatethe operating status of the node itself and the overall network. 1,2,3... 1. Two stat...

47 Nomenclature and Functions Section 2-1 2-1-2 Status Indicators: MS and NS The MS (Module Status) indicator indicates the status of the node itself andthe 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, orflas...

48 Nomenclature and Functions Section 2-1 2-1-3 Seven-Segment Display In addition to the MS and NS indicators, DeviceNet Units have a 2-digit, 7-segment display that normally indicates the master node address. When anerror occurs, the display will alternate between the error code and the nodeaddress...

49 Nomenclature and Functions Section 2-1 The following diagram shows the alternating error code/ node address display. The master’s error code and master’s node address will be displayed if anerror has occurred at the master. There is no priority in the error codes; all errors that have occurred wi...

50 Nomenclature and Functions Section 2-1 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 beenset on another slave node. 3. If the node address is the same as one set on another node, a node ad-dress duplication error will o...

51 Installing the DeviceNet Unit Section 2-2 Continue/Stop Remote I/O Communications When the DeviceNet Unit is used as a master, pin 3 is used to set whether ornot communications will stop after a communications error. If pin 3 is ON, remote I/O communications will be stopped if one of the follow-i...

52 Installing the DeviceNet Unit Section 2-2 • In the CS-series, up to 16 Units can be mounted to the CS1W-BC @@ 3 CPU Backplane or CS1W-BI @@ 3 Expansion CPU Backplane. • In the CJ-series, up to 16 Units can be mounted to the CPU Unit or Expansion Unit (but no more than 10 Units on either). 2-2-2 M...

53 Installing the DeviceNet Unit Section 2-2 Note When mounting the Unit, provide the clearance shown below to facilitate easymounting or dismounting. CJ-series 1. Carefully align the connectors to mount the DeviceNet Unit. 2. Move the yellow sliders on the top and bottom of the Unit until they clic...

54 Installing the DeviceNet Unit Section 2-2 • Provide separate conduits or ducts for the I/O lines to prevent noise from high-tension lines or power lines. • Leave the label attached to the Unit when wiring. Removing the label may result in malfunction if foreign matter enters the Unit. • Remove th...

55 Installing the DeviceNet Unit Section 2-2 2-2-4 External Dimensions CS1W-DRM21 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 Opera- tion Manual (W393) for the dimensions of the Unit when it is mounted t...

58 Overview of Word Allocations Section 3-1 3-1 Overview of Word Allocations The words shown in the following diagram are allocated according to the unitnumber setting. For each Unit, there are 25 words allocated in the CIO Areaand 100 words allocated in the DM Area. First word allocated in the CIO ...

59 Overview of Word Allocations Section 3-1 3-1-1 Allocated CIO Area Words Software switches, DeviceNet Unit status, and error data are allocated in theCIO Area according to the unit number, as shown below. Software switchesare bits used as commands from the CPU Unit to the DeviceNet Unit toenable e...

65 Allocated CIO Area Words Section 3-2 3-2-2 Software Switches 2 (Word n+1) All switches are turned ON by the user. The Unit automatically turns themOFF after the function is executed. Once a function is set by turning a switchON (except for the switches listed below), it is saved regardless of whe...

75 Allocated CIO Area Words Section 3-2 3-2-8 Master Status 2 (Word n+13) The leftmost eight bits indicate the status of master I/O allocations. Master I/O Allocation Status 10 Fixed Allocation Area Setting Failed Flag ON Unit Indicates that an error has occurred in one of the following operations: ...

78 Allocated CIO Area Words Section 3-2 3-2-10 Slave Status 2 (Word n+15) Master Node Addresses This indicates the node address of the remote master for slave communica-tions. Slave I/O Allocation Status This indicates the I/O allocation status of the slave. 3-2-11 Registered Slave Table (Words n+16...

79 Allocated CIO Area Words Section 3-2 3-2-12 Normal Slave Table (Words n+20 to n+23) This table indicates the slaves that are communicating normally with the mas-ter. The bits correspond to node addresses. The bits for slaves for which nor-mal I/O connections have been made are turned ON in this t...

81 Allocated DM Area Words Section 3-3 3-3 Allocated DM Area Words Data is stored at the offset positions shown in the figure below star ting fromthe first word allocated to the Unit in the DM Area. The first word can be calculated as follows from the unit number setting: First word m = D30000 + (25...

82 Allocated DM Area Words Section 3-3 Note If the setting is smaller than the optimum communications cycle time calcu-lated by the Unit and stored internally in the Unit, then the value calculated bythe Unit will be used. 3-3-2 Master User Allocations Setup Table This table is set by the user to sp...

83 Allocated DM Area Words Section 3-3 Note Make sure the CPU Unit is in PROGRAM mode and the master function isenabled before you set these values. Note See Allocation Size Setup Table (p. 84) for more details on the first word of the allocation size setup table. Areas and Word Ranges Name Range De...

84 Allocated DM Area Words Section 3-3 Setting Results 3-3-3 Allocation Size Setup Table The following allocation size setup tables must be set in the I/O memory in theCPU Unit to use the Master User Allocations Setup Table. The number of bytes set in the allocation size setup table are allocated in...

85 Allocated DM Area Words Section 3-3 Setting Example The following example shows the allocation when the size (bytes) for OUTblock 1 and IN block 1 is set in the allocation size setup table using the speci-fied values. Node address 0: OUT size: 1 byte, IN size: 5 bytesNode address 1: OUT size: 4 b...

87 Allocated DM Area Words Section 3-3 3-3-5 Communications Cycle Time Reference Table This table can be used to access the present, maximum and minimum com-munications cycle times. All the values in this table are cleared from the Unitand the maximum and minimum values are updated with new values w...

88 Allocated DM Area Words Section 3-3 Ranges Areas and Word Ranges 3-3-7 Slave User-set Allocations Reference Table The slave block settings can be accessed in the Slave User-set AllocationsReference Table. A maximum of two OUT and two IN areas (OUT 1, IN 1,OUT 2, and IN 2) can be used for slave co...

89 Allocated DM Area Words Section 3-3 Note OUT2 is not used. Ranges Areas and Word Ranges 3-3-8 Slave Detailed Status The status of the slaves controlled by the master function of the Unit is pro-vided by node address. Each word provides the status of two slaves. Name Range Details OUT 1/2 area See...

92 Master Remote I/O Communications Section 4-1 4-1 Master Remote I/O Communications Remote I/O communications are used to automatically transfer data betweenslaves and the CPU Unit without any special programming in the CPU Unitunder which the Master Unit is mounted. Master Communications Note 1. A...

93 Master Remote I/O Communications Section 4-1 Fixed Allocations Any one of the three areas below can be specified as the words allocated inthe 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 areasshown b...

94 Master Remote I/O Communications Section 4-1 The OUT and IN blocks will be allocated in order of slave node addresses.Each block is a maximum of 500 words. Each address is allocated at least one byte (rightmost). • More than one word is allocated for each slave with more than16 I/O points (accord...

95 Master Remote I/O Communications Section 4-1 4-1-2 Remote I/O Master Specifications Item Specifications Slave alloca-tion methods Fixed allo-cations 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...

96 Master Remote I/O Communications Section 4-1 4-1-3 Precautions on the Number of Master Units The following system configurations can be constructed based on variousnumbers of Master Units when DeviceNet Units are used. Note Only one Master Unit can be connected to a network if the user specifies ...

97 Master Remote I/O Communications Section 4-1 4-1-4 Procedure for Using Remote I/O Master Fixed Allocations for Remote I/O 1,2,3... 1. 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...

98 Master Remote I/O Communications Section 4-1 3. Turn ON the Master Enable Switch (word n bit 06). (The master will remainenabled 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 mas...

99 Scan List Section 4-2 nect/Connect Switch for that slave (words n+6 to n+9). This can be donewhen a slave is replaced or to register a slave in the scan list in prepara-tions to connect it to the network at a later time. The Disconnect/ConnectSwitches, however, are cleared when the power supply i...

100 Scan List Section 4-2 Creating the Scan List The way that a scan list is prepared varies with the allocation method asshown below. Note 1. Be sure to create a scan list before star ting actual system operation. 2. It is still possible to communicate with Units (with the scan list disabled) ifa s...

101 Fixed Allocations Section 4-3 you disable the scan list with a Master Unit that is set for user-setallocations. Par ticularly when multiple Master Units are connectedto a single network, communications will not be performed suc-cessfully if even one Master Unit on the network is operating withth...

102 Fixed Allocations Section 4-3 Note More than one Master Unit can be included in a single PC with fixed alloca-tions, as shown below (3 Units max.). 4-3-2 Procedure Step 1: Place the CPU Unit in PROGRAM mode. Step 2: Turn ON the Master Enable Switch If the master communications have been disabled...

103 Fixed Allocations Section 4-3 Fixed Allocations Area 1 OUT blocks are allocated to slaves from CIO 3200 to CIO 3263 and IN blocksare allocated to slaves from CIO 3300 to CIO 3363. Fixed Allocations Area 2 OUT blocks are allocated to slaves from CIO 3400 to CIO 3463 and IN blocksare allocated to ...

104 Fixed Allocations Section 4-3 Fixed Allocations Area 3 OUT blocks are allocated to slaves from CIO 3600 to CIO 3663 and IN blocksare allocated to slaves from CIO 3700 to CIO 3763. The Slave allocation order is fixed in the output (OUT) and IN blocks star tingfrom address 0. Each address is alloc...

105 Fixed Allocations Section 4-3 4-3-3 Changing System Components The scan list must be cleared in the following situations: • Adding a slave • Removing a slave • Changing a node address Turn OFF the Scan List Clear Switch (word n, bit 01) to clear the scan list.Remote I/O communications will be pe...

106 Fixed Allocations Section 4-3 Resulting Slave Allocation Turn ON the Scan List Enable Switch Turn ON the Scan List Enable Switch (word n, bit 00, CIO 150000 in thisexample). This will create a scan list based on data for slaves that are actuallyonline and will star t remote I/O communications wi...

107 User-set Allocations Section 4-4 4-4 User-set Allocations With a CS/CJ-series DeviceNet Unit, remote I/O communications slaves canbe allocated in any area (CIO, WR, HR, DM, or EM) using one of the followingmethods. • Setting through the allocated DM Area words (Master User Allocations Table) • S...

109 User-set Allocations Section 4-4 Procedure Step 1: Turn ON the Master Enable Switch Make sure that master communications have disabled by checking to see ifMaster Enable Function Flag (word n+11, bit 03) is OFF and then turn ON theMaster Enable Switch (word n+14, bit 06) to enable master communi...

110 User-set Allocations Section 4-4 Step 4: Turn ON the Slave User Allocations Switch Turn ON the Slave User allocations Switch (word n, bit 11). This will make theDeviceNet Unit read allocation results data for the slaves above from the CPUUnit and create a scan list based on data for slaves that ...

114 User-set Allocations Section 4-4 Procedure Step 1 Set the area, star t word, and words allocated for each block using the Config-urator. Step 2 Allocate words to all node addresses in each block as shown below using theConfigurator. • Each address is allocated at least one byte (rightmost or lef...

116 Starting and Stopping Remote I/O Communications Section 4-5 Configurator Setting Methods Refer to the DeviceNet Configurator Operation Manual (W382) for setting methods. 4-5 Starting and Stopping Remote I/O Communications 4-5-1 Starting Remote I/O Communications Remote I/O communications start a...

117 Example of Ladder Programming for Remote I/O Communications Section 4-6 Note Even if there is a communications error with the slave, the slave input data issaved in the allocated area. To prevent operating errors, make the ladder program so that no slave I/O pro-cessing will occur when the Unit ...

118 Errors that May Occur in Remote I/O Communications Section 4-7 4-7 Errors that May Occur in Remote I/O Communications The following errors may occur during remote I/O communications. Condition Error Details Results Indicators 7- segment display Error occurs in fixed allo-cations with the scan li...

122 Slave Remote I/O Communications Section 5-1 5-1 Slave Remote I/O Communications A CS/CJ-series DeviceNet Unit can function as a Slave Unit in remote I/Ocommunications and a single CS/CJ-series DeviceNet Unit can function asboth a Master Unit and a Slave Unit. This section describes Slave communi...

123 Slave Remote I/O Communications Section 5-1 5-1-2 Remote I/O and Slave Communications Specifications 5-1-3 Procedures for Using Remote I/O Slave Communications Fixed Allocations for Remote I/O 1,2,3... 1. Turn ON the communications, slave, and PC power supplies. Note Turn ON the communications p...

124 Slave Remote I/O Communications Section 5-1 munications, allocate areas, and then enable slave communications. The allo-cated 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,...

127 User-set Allocations Section 5-3 2. Only two blocks (OUT 1 and IN 1) can be allocated when setting are madewith the allocated DM Area words area, but there are three blocks (OUT 1and IN 1/2) available with the Configurator. Setting through the Allocated DM Area Words (Slave User Allocations Tabl...

128 User-set Allocations Section 5-3 • Areas and Word Ranges for the OUT 1/IN 1 Areas Step 3: Turn ON the Slave User Allocations Switch Turn ON the Slave User Allocations Switch (word n+1, bit 11). Step 4: Turn ON the Slave Enable Switch Turn ON the Slave Enable Switch (word n+1, bit 06). This will ...

130 User-set Allocations Section 5-3 Setting through the Configuration A maximum of three blocks can be allocated at any locations in I/O memoryfor the output (OUT) area block 1, input (IN) area block 1, and input (IN) areablock 2. The block allocation order and block allocation areas can be set as ...

134 Overview Section 6-1 6-1 Overview Message communications enable messages to be set between nodes on aDeviceNet network when required by system conditions. The messages canbe sent between PCs, between an OMRON PC and a master made byanother company, or between slaves. They can be used to send/rec...

135 Overview Section 6-1 Overall Structure Note If only the message communications function is being used and the remote I/O communications function is not being used, message communications arepossible even if the master function is disabled. In this case, it is not neces-sary to register a scan li...

136 Overview Section 6-1 Note 1. The DeviceNet Unit must be registered in the local network routing table ofthe CS/CJ-series PC when two or more Communications Units (includingthe DeviceNet Unit) are mounted to a CS/CJ-series PC. The commandswill not be sent if the Unit is not registered in the rout...

137 Overview Section 6-1 Sending FINS Message Communications Receiving FINS Message Communications Note C200H-series DeviceNet Master Units (C200H-DRM21-V1) and CVM1/CV-series DeviceNet Master Units (CVM1-DRM21-V1) both suppor t FINS mes-sage communications but it is executed by a special OMRON meth...

138 Overview Section 6-1 Note A specific FINS command (command 2801) is used to send explicit mes-sages. Note A specific FINS command (command 2801) is used to send explicit messages. Note This CS/CJ-series DeviceNet Unit (CS1W-DRM21 or CJ1W-DRM21) containsa PLC Object so that the I/O memory of the ...

139 Overview Section 6-1 6-1-5 Message Communications Error Indications There are two ways to obtain information on communications errors that occurin message communications: 1) Using the error history in the DeviceNet Unitand 2) Using DeviceNet Unit displays, indicators, and Master Status Areas. 1,...

140 Overview Section 6-1 6-1-6 Message Monitoring Timer A message monitoring timer monitors responses for the DeviceNet Unit. Atimer can be set for each device that will be communicated with (each mes-sage destination). Message monitoring timers are supported for both explicit message and FINSmessag...

141 FINS Commands and Responses Section 6-2 termeasures and errors recorded in error history that are not shown by theindicators. Note 1. The 7-segment display alternately displays the error and the master nodeaddress where the error occurred. 2. The send response message or reception response messa...

142 FINS Commands and Responses Section 6-2 Refer to SYSMAC CS/CJ Series Communication Commands Reference Man- ual (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-seriesPCs. Send/receive FINS command...

143 FINS Commands and Responses Section 6-2 The main response codes are listed below. Refer to SYSMAC CS/CJ Series Communication Commands Reference Manual (W342) for further details on response codes, including sub-response codes (SRES). 6-2-3 Units Supporting FINS Communications The parameters used...

145 Using FINS Message Communications Section 6-3 Commands Addressed to DeviceNet Units Command to Send Explicit DeviceNet Messages 6-3 Using FINS Message Communications There are two instructions that can be executed to send and receive data fromCS/CJ-series CPU Units: SEND(090) and RECV(098). Ther...

146 Using FINS Message Communications Section 6-3 3. In all cases other than the following two exceptions, a local network tablemust 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...

147 Using FINS Message Communications Section 6-3 The unit number of the DeviceNet Unit as a CPU Bus Unit is the number seton the rotary switches on the front panel (0 to 15). The network address is theaddress of the Network to which the CPU Bus Unit is connected (1 to 127).The network address is sp...

148 Using FINS Message Communications Section 6-3 4. Use the left-side table to create the local network table. Input the unit num-bers and corresponding local network addresses. 5. Use the right-side table to create the relay network table. Input the final net-work addresses and corresponding relay...

149 Using FINS Message Communications Section 6-3 Note 1. Indicates a Unit as shown in the following table. 2. Values of $00 to $3F indicate nodes 0 to 63. 3. Designates the length of time that the PC retries transmission when bit 15of C+3 is OFF and no response is received. The default value is $00...

150 Using FINS Message Communications Section 6-3 Note 1. Indicates a Unit as shown in the following table. 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 transmis-sion when bit 15 of C+3 is OFF and no response is received. The d...

151 Using FINS Message Communications Section 6-3 Note 1. Indicates a Unit as shown in the following table. 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 transmis-sion when bit 15 of C+3 is OFF and no response is received. The d...

152 Using FINS Message Communications Section 6-3 Communications Flags Communications Flag Operation • The Network Enabled Flag turns OFF when instructions are being sent or received (from when the instruction is issued until the response isreceived) and turns ON when the execution has been complete...

153 Using FINS Message Communications Section 6-3 in the following table. Communications Instructions Completion Codes The status at the completion of the execution of network communicationsinstructions is shown at the words indicated in the following table, as FINScompletion codes. During execution...

154 Using FINS Message Communications Section 6-3 Note 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 howmany banks can be used. 3. Do not exceed th...

155 Using FINS Message Communications Section 6-3 Program Example (021)MOV A503 D00006 11 A202 (021)MOV #0005 D00000 (021)MOV #0001 D00001 (021)MOV #0600 D00002 (021)MOV #0000 D00003 (025)ASL 0000 000 00 A202 00 0000 01 (071)BSET #1234 D01000 D01004 Sets 1234 in D01000 to D01004. Places data into co...

156 Using FINS Message Communications Section 6-3 Example 2: Sending a FINS Command Using CMND 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 withnode address 06. • The MEMORY AREA READ command (01 01) i...

157 Using FINS Message Communications Section 6-3 Example Program 6-3-6 Connecting Networks for FINS Communications CS/CJ-series DeviceNet Units can perform FINS communications betweennetworks. DeviceNet networks are handled the same way as other FA net-works such as Controller Link or SYSMAC LINK, ...

158 Sending Explicit Messages Section 6-4 When connecting networks, routing tables must be registered for the PC CPUUnits on all networks. When connecting two or more communication units (including the DeviceNetUnit) to a CS/CJ-series CPU Unit, the DeviceNet Unit must be registered inthe CS/CJ-serie...

161 Sending Explicit Messages Section 6-4 Parameters Destination node address (command): The node address of the destination of the explicit message. (The node address of the local DeviceNet Unit isspecified in the control data for the CMND(490) or IOWR instruction, but thenode address of the actual...

162 Sending Explicit Messages Section 6-4 D: First response word C: First control data word Command data is set in order star ting with the word specified for theCMND(490) operand S (first command word) and continuing with words withhigher addresses in I/O memory in the command block format. Command...

163 Sending Explicit Messages Section 6-4 The response format data in service data that is in word (2-byte) or double-word (4-byte) units, such as word data and ERROR CLEAR codes, is alsospecified from low to high bytes in response block format Example: Sending Explicit Messages Using CMND(490) Oper...

165 Receiving Explicit Messages Section 6-5 Program Example 6-5 Receiving Explicit Messages This CS/CJ-series DeviceNet Unit contains a PLC Object. The Unit willreceive messages addressed to the PLC Object, process service requestsaddressed to the CPU Unit, and return responses. The following servic...

166 Receiving Explicit Messages Section 6-5 • PCs with CVM1/CV-series DeviceNet Master Units (CVM1-DRM21-V1) • PCs with CS/CJ-series DeviceNet Units Example Note Status and the I/O memory read/write operations cannot be performed forPCs with a C200H-series or CVM1/CV-series DeviceNet Master Units. T...

168 Receiving Explicit Messages Section 6-5 CPU Information Read (Service Code: 0E Hex) Reads CPU Unit information, including operating mode, fatal/non-fatal errors,and the CPU Unit model. Command Block Response Block Parameters Destination node address (command): The node address of the CS/CJ- seri...

169 Receiving Explicit Messages Section 6-5 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 for-mat, as follows: 0001 Hex: PROGRAM mode; 0002 Hex: MONITOR m...

170 Receiving Explicit Messages Section 6-5 Response Block Parameters Destination node address (command): The node address of the CS/CJ- series DeviceNet Unit to which to write data, specified in 1-byte (2 digit) hexa-decimal. Service code (command, response): 10 Hex is specified for commands. For r...

171 Receiving Explicit Messages Section 6-5 Note Error clear codes are 1-word (2-byte) data, so the above codes are specified with the low byte first. The low to high bytes for the abovecodes are set as high to low bytes in I/O memory, when setting thecodes as data for operand S of CMND(490). For ex...

172 Receiving Explicit Messages Section 6-5 CPU Unit Status Read (Service Code: 40 Hex) This PLC Object ser vice reads status details (operation status, operatingmode, fatal and non-fatal errors, etc.) from the CPU Unit. Command Block Response Block Parameters Destination node address (command): The...

173 Receiving Explicit Messages Section 6-5 • 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 mod...

174 Receiving Explicit Messages Section 6-5 • Message Exists/Does Not Exist: When the MSG instruction is executed by the CPU Unit, the bit corresponding to the message number will turnON and be returned in 2 bytes (from low to high bytes). • Error Code : The highest priority error code of the errors...

176 Receiving Explicit Messages Section 6-5 Word Data Read (Service Code: 1D Hex) Word Data Read reads I/O memor y area data in CPU Units with a CS/CJ-series DeviceNet Units. The read word data is in word units. The responseblock is returned from low to high bytes. Command Block Response Block Param...

177 Receiving Explicit Messages Section 6-5 No of Read Words (command): The number of words of read data is speci- fied in 1-byte (2-digit) hexadecimal. The range is 01 to 64 Hex (1 to 100 deci-mal). No. of bytes received (response): The number of bytes received from the destination node address (re...

178 Receiving Explicit Messages Section 6-5 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. Address L, Address H (command): The address of the first word to which the data will be written is specified in he...

182 Connecting to the CX-Programmer via the DeviceNet Section 7-1 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 aPC containing a CS/CJ-series DeviceNet Unit to form an online connection,via the DeviceNet, to other PC CP...

183 Connecting to the CX-Programmer via the DeviceNet Section 7-1 7-1-1 Setting Node Addresses When the CX-Programmer is connected online, it uses FINS message com-munications. It is thus necessary to set the node address to a number otherthan 0 for DeviceNet Units mounted to the target PC, DeviceNe...

184 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 thenode address and click on the Edit Button. A dialogue box like the one be- low will appear. 3. Input the value, then click on the OK Button. Note To set the...

185 Connecting to the CX-Programmer via the DeviceNet Section 7-1 response monitor time in the CMND/SEND/RECV instruction to be thesame 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-ou...

187 Memory Card Backup Functions Section 7-2 7-2-1 Outline of Functions 1. Backing Up Unit Setup Files Saves all internal Unit setup data to the Memory Card mounted to the CPUUnit.Method: Turn ON the Setup File Backup Switch (word n+1, bit 15) to save theinternal Unit setup data to the Memory Card a...

188 Memory Card Backup Functions Section 7-2 Note If there is an error in the setup data or if the file could not be read, the FileRead/Write Error bit in Unit Status 2 (word n + 11, bit 08) will turn ON. 3. Saving Files from Configurator to Memory Card Device parameter files (.dvf files) for this D...

190 Remote I/O Communications Characteristics Section 8-1 8-1 Remote I/O Communications Characteristics This section describes the characteristics of remote I/O communicationswhen the DeviceNet Unit is used as a master in combination with OMRON’sslaves. Use this section for reference when planning o...

191 Remote I/O Communications Characteristics Section 8-1 Communications Cycle Time Calculation Use the equations shown below to calculate the communications cycle time(T RM ) for a network with one Master. Note that if the result of this calculation is less than 2 ms, the actual communications cycl...

192 Remote I/O Communications Characteristics Section 8-1 Slaves with More Than 8 Bytes of Input or Out put T RT = T OH + T BYTE-IN × B IN + T BYTE-OUT × B OUT [ms] T OH : Protocol overhead T BYTE-IN : The input byte transmission time B IN : The number of input words T BYTE-OUT : The output byte tra...

194 Remote I/O Communications Characteristics Section 8-1 Minimum I/O Response Time The minimum I/O response time occurs when the Slave’s I/O refreshing isexecuted just after the input signal is received by the DeviceNet Unit and theoutput signal is output at the beginning of the next I/O refresh cy...

195 Remote I/O Communications Characteristics Section 8-1 Note Although in the above diagram the Slaves are separated into two groups forconvenience, 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 ...

196 Message Communications Section 8-2 This programming is for a DeviceNet Unit with a unit number of 00. 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 isturned ON or restar t...

197 Message Communications Section 8-2 Note 1. If the CPU Unit attempts to send another message or receives a messagefrom another node within the message communications time, the secondmessage or the message being received from another node may be de-stroyed. Never execute a second communications in...

200 Troubleshooting with the DeviceNet Unit Indicators Section 9-1 9-1 Troubleshooting with the DeviceNet Unit Indicators 9-1-1 Determining Operating Status from the Indicators The following table shows the status of the MS and NS indicators and the 7-segment display during normal operation. Indicat...

201 Troubleshooting with the DeviceNet Unit Indicators Section 9-1 9-1-2 Troubleshooting Errors Occurring in the DeviceNet Unit Note 1. The 7-segment display will alternate between the Unit’s node address andthe code given in the tables in this section. 2. When a (master function) structure error or...

202 Troubleshooting with the DeviceNet Unit Indicators Section 9-1 remote I/O communications for a communications error, two errors can bedisplayed: The slave’s communications error and its most recent error. Master Errors Remote I/O Communications Stopped by a Communications Error Likely Cause Pin ...

203 Troubleshooting with the DeviceNet Unit Indicators Section 9-1 Correction Set the slaves’ node addresses again. Structure Error: I/O Area Range Exceeded Likely Cause The slave’s I/O area isn’t within the allowed range. (Occurs with the scan listdisabled.) DeviceNet Unit Response Records the erro...

205 Troubleshooting with the DeviceNet Unit Indicators Section 9-1 Correction Inspect the slave and then create the scan list again. Verification Error:I/O Size Mismatch Likely Cause The slave’s I/O data size does not match the registered scan list. (Occurs withthe scan list enabled.) DeviceNet Unit...

207 Troubleshooting with the DeviceNet Unit Indicators Section 9-1 • Matching master and slave baud rates • Proper cable lengths (trunk and branch lines) • Broken or loose cables • Installation of terminators at both ends of the trunk line • Excessive noise Software Switch Setting Errors CPU Unit St...

208 Troubleshooting with the DeviceNet Unit Indicators Section 9-1 Likely Cause The setting operation failed because a structure error occurred. DeviceNet Unit Response The only response is the error code displayed on the 7-segment display. Theerror display will be cleared the next time that a setti...

210 Troubleshooting with the DeviceNet Unit Indicators Section 9-1 DeviceNet Unit Response Records the error in the error log. • The Unit will go off–line and communications will be disabled. Error responses will be returned to all communications requests. • The exchange of data with the CPU Unit wi...

211 Troubleshooting with the DeviceNet Unit Indicators Section 9-1 DeviceNet Unit Response Records the error in the error log.Operation will continue using the default message monitoring timer values. Flags Allocated for C200H DeviceNet Master Unit (CIO n+24) Bit 14 (Error Flag) and bit 03 (the Stru...

212 Troubleshooting with the DeviceNet Unit Indicators Section 9-1 Correction Clear the scan list and register the scan list again or use the Configurator toreset the master scan list. Memory Access Error Likely Cause An error occurred in the Unit’s non-volatile memory itself. This error will occuri...

213 Troubleshooting with the DeviceNet Unit Indicators Section 9-1 CIO Area Flags Allocated to DeviceNet Unit Bits 00 and 04 of n+10 (the Unit Error Flag and Unit Memory Error Flag) willbe ON. Correction Replace the Unit if the error recurs. CPU Unit Exchange Errors Unit Number duplication Likely Ca...

214 Troubleshooting with the DeviceNet Unit Indicators Section 9-1 DeviceNet Unit Response Stops operation. Correction Set the communications speed correctly and restart the DeviceNet Units. CPU Unit Faulty (H6) DeviceNet Unit Response Records the error in the error log. (The time information is set...

215 Troubleshooting with the DeviceNet Unit Indicators Section 9-1 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...

217 Troubleshooting with the DeviceNet Unit Indicators Section 9-1 • Returns an error response (0302 Hex) to commands requiring a re- sponse. • Discards other frames and stores an error record (010B Hex) in the er- ror log. Flags Allocated for C200H DeviceNet Master Unit (CIO n+24) There is no statu...

218 Error Log Functions Section 9-2 • Installation of terminators at both ends of the trunk line • Excessive noise Unit Errors Special Unit Error 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...

219 Error Log Functions Section 9-2 When using the Configurator, the error log can be monitored with the mastererror history read operation. With the Configurator, the error log can only bemonitored and the data cannot be saved. Time Information The CPU Unit’s time information is used for the time s...

222 Troubleshooting Section 9-3 9-3 Troubleshooting 9-3-1 CPU Unit’s ERR/ALM Indicator Lit or Flashing Use the following table to troubleshoot the network when the DeviceNet Unitis mounted and the CPU Unit’s ERR/ALM indicator is lit or flashing. Note Refer to the CS1 Series CPU Unit Operation Manual...

223 Troubleshooting Section 9-3 9-3-3 I/O Link Problems Use the following table to troubleshoot I/O Link problems. 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’...

224 Troubleshooting Section 9-3 9-3-4 Communications Error Operation Settings Use the following table to correct problems with the DIP switch setting for con-tinuing/stopping communications for errors. 9-3-5 Scan List Problems Use the following table to troubleshoot scan list problems. Error Probabl...

225 Maintenance and Replacement Section 9-4 9-4 Maintenance and Replacement This section describes the routine cleaning and inspection recommended asregular maintenance as well as the Unit replacement procedure required if aDeviceNet Unit fails. 9-4-1 Cleaning Clean the DeviceNet Units regularly as ...

226 Maintenance and Replacement Section 9-4 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 recom- mend having spare Units available to restore network operation as quickly asp...

227 Maintenance and Replacement Section 9-4 Creating a New Network File Use the following procedure to write the settings to the DeviceNet Unit from anetwork 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 disp...

229 Appendix A Allocation Differences from C200H DeviceNet Master Units The following table shows the CS1W-DRM21/CJ1W-DRM21 DeviceNet Unit allocation areas that correspondto the C200HW-DRM21-V1 DeviceNet Master Unit allocation areas. Note The following table does not include the allocation areas tha...

230 Allocation Differences from C200H DeviceNet Master Units Appendix A Status Areas Master Status Area 1 An area with the exact same bit configuration as Master Status area 1 used for C200H DeviceNet Master Units,was set up. This area is called the Master Replacement Status 1. • The following table...

232 Allocation Differences from C200H DeviceNet Master Units Appendix A Master Status Area 2 Communications Cycle Time Present Value Registered Slave Table Name C200H DeviceNet Master Unit CS/CJ-series DeviceNet Unit Contents for CS/CJ- series DeviceNet Unit Differences from C200H DeviceNet Master U...

233 Allocation Differences from C200H DeviceNet Master Units Appendix A Normal Slave Table Replacing Ladder Programs from C200HW-DRM21-V1 If ladder programs have already been created for C200H DeviceNet Master Unit (C200HW-DRM21-V1)mounted to CS/CJ-series CPU Units, the ladder programs must be chang...

234 Allocation Differences from C200H DeviceNet Master Units Appendix A Replace the addresses as shown in the following table. Message Communications in Ladder Programs Note If there is a routing table in the CS/CJ-series CPU Unit, the DeviceNet Unit must be registered in it whenreplacing the C200HW...

235 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, ...

236 DeviceNet Connections Appendix B Connections Using Allocations Setting Connection Type The settings for remote I/O communications connections differ depending on the allocation method, as outlinedbelow. Fixed Allocation or User-set Allocations Using Allocated DM Area Words The Master CS/CJ-serie...

237 DeviceNet Connections Appendix B Note 1. Output data using poll connections and output data using COS or cyclic connections are transmittedusing the same frame. Therefore set the same output size (bytes) when combining poll and COS orpoll and cyclic. 2. The COS/cyclic hear tbeat timer is the sma...

238 DeviceNet Connections Appendix B Master COS Send Switch COS transmission is possible only for User-set allocations using the Configurator. When required, remote I/O output data can be output from the master to a specified slave. Output data can be sent at the communications cycle timing to the s...

241 Appendix C FINS Commands and Responses for DeviceNet Units List of Command Codes Refer to SYSMAC CS/CJ Series Communication Commands Reference Man- ual (W342) for details on end codes. RESET (0403) Resets (restar ts) the DeviceNet Unit. Command Block Resets the DeviceNet Unit. Response Block The...

242 FINS Commands and Responses for DeviceNet Units Appendix C • Baud rate Command Block Response Block End Codes Parameter Details [Model, Version] (Response)The DeviceNet Unit model and version are returned as outlined below in 20-byte ASCII code. If the data is less than 20 bytes, the remaining b...

243 FINS Commands and Responses for DeviceNet Units Appendix C Response Block End Codes Parameter Details [Operation status, Units status 1, Unit status 2, Master function status 1, Mas-ter function status 2, Slave function status 1, Slave function status 2](response) • Operation Status Fixed at 01 ...

244 FINS Commands and Responses for DeviceNet Units Appendix C For commands, the data to be sent to the specified node is specified, with amaximum 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 comma...

245 FINS Commands and Responses for DeviceNet Units Appendix C Returns the error history for the number specified by Read Record No., inorder from the Read Star t Record No. The total number of Error Histor y Databytes is 10 × Read Record No. One record of error history data is structured in 10 byte...

246 FINS Commands and Responses for DeviceNet Units Appendix C End Codes Important Point The Error History Clear command clears the RAM and EEP-ROM error his-tory tables. End code (hex) Contents 0000 Normal end 1001 Command length exceeds maximum command length.

247 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...

251 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 install...

252 Multi-vendor Applications Appendix E Master Unit Device Profile Object Mounting Identity Object (01 Hex) Message Router Object (02 Hex) General data Compatible DeviceNet Specifications Volume I - Release 2.0Volume II - Release 2.0 Vendor name OMRON Corporation Vendor ID = 47 Device profile name ...

255 Multi-vendor Applications Appendix E Note 1. Number of input bytes used by Slave. 2. Number of output bytes used by Slave. Object instance 2 Section Information Max. No. of instances Instance type Polled I/O 1 Produc-tion trig-ger Cyclic Transport type Server Transport class 2 Attribute ID conte...

260 Multi-vendor Applications Appendix E Note The refresh area types are shown in the following table. PC area Refresh area type Refresh address CIO 1 CIO 0000 to CIO 6143 DM 3 D00000 to D32767 WR 4 W000 to W511 HE 5 H 000 to H511 EM (bank 0) 8 E0_00000 to E0_32767 EM (bank 1) 9 E1_00000 to E1_32767...

261 Appendix F DeviceNet Explicit Message Send Command for Other Manufacturer Nodes Explicit Message Send (2801) Sends a DeviceNet explicit message to a specified object and receives aresponse. Command Block Response Block • When a normal response has been returned for the executed explicit message:...

262 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 instructioncontrol data for Expl...

263 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 com...

267 Revision History A manual revision code appears as a suffix to the catalog number on the front cover of the manual. The following table outlines the changes made to the manual during each revision. Page numbers refer to theprevious version. Revision code Date Revised content 1 October 2000 Origi...