Omron CJ1W-DRM21 Manual do Utilizador Página 1

CS-series DeviceNet Unit: CS1W-DRM21CJ-series DeviceNet Unit: CJ1W-DRM21Operation ManualRevised July 2001

xiiIntended Audience 11 Intended AudienceThis manual is intended for the following personnel, who must also haveknowledge of electrical systems (an el

87Allocated DM Area Words Section 3-33-3-5 Communications Cycle Time Reference TableThis table can be used to access the present, maximum and minimum

88Allocated DM Area Words Section 3-3RangesAreas and Word Ranges3-3-7 Slave User-set Allocations Reference TableThe slave block settings can be access

89Allocated DM Area Words Section 3-3Note OUT2 is not used.RangesAreas and Word Ranges3-3-8 Slave Detailed StatusThe status of the slaves controlled b

90Allocated DM Area Words Section 3-303, 11 Slave Remote I/O Communica-tions Error FlagON Unit Indicates that an error has occurred in remote I/O comm

91SECTION 4Remote I/O Master CommunicationsThis section describes the remote I/O communications performed as a DeviceNet master by the Devicenet Unit.

92Master Remote I/O Communications Section 4-14-1 Master Remote I/O CommunicationsRemote I/O communications are used to automatically transfer data be

93Master Remote I/O Communications Section 4-1Fixed AllocationsAny one of the three areas below can be specified as the words allocated inthe CIO Area

94Master Remote I/O Communications Section 4-1The OUT and IN blocks will be allocated in order of slave node addresses.Each block is a maximum of 500

95Master Remote I/O Communications Section 4-14-1-2 Remote I/O Master SpecificationsItem SpecificationsSlave alloca-tion methodsFixed allo-cationsSele

96Master Remote I/O Communications Section 4-14-1-3 Precautions on the Number of Master UnitsThe following system configurations can be constructed ba

xiiiOperating Environment Precautions 4measure for such problems, external safety measures must be providedto ensure safety in the system.• When the 2

97Master Remote I/O Communications Section 4-14-1-4 Procedure for Using Remote I/O MasterFixed Allocations for Remote I/O1,2,3... 1. Turn ON the commu

98Master Remote I/O Communications Section 4-13. Turn ON the Master Enable Switch (word n bit 06). (The master will remainenabled even if the power is

99Scan List Section 4-2nect/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 s

100Scan List Section 4-2Creating the Scan List The way that a scan list is prepared varies with the allocation method asshown below.Note 1. Be sure t

101Fixed Allocations Section 4-3you disable the scan list with a Master Unit that is set for user-setallocations. Particularly when multiple Master Un

102Fixed Allocations Section 4-3Note More than one Master Unit can be included in a single PC with fixed alloca-tions, as shown below (3 Units max.).4

103Fixed Allocations Section 4-3Fixed Allocations Area 1OUT blocks are allocated to slaves from CIO 3200 to CIO 3263 and IN blocksare allocated to sla

104Fixed Allocations Section 4-3Fixed Allocations Area 3OUT blocks are allocated to slaves from CIO 3600 to CIO 3663 and IN blocksare allocated to sla

105Fixed Allocations Section 4-34-3-3 Changing System ComponentsThe scan list must be cleared in the following situations:• Adding a slave • Removing

106Fixed Allocations Section 4-3Resulting Slave Allocation Turn ON the Scan List Enable SwitchTurn ON the Scan List Enable Switch (word n, bit 00, CIO

xivApplication Precautions 5The operating environment of the PC System can have a large effect on thelongevity and reliability of the system. Improper

107User-set Allocations Section 4-44-4 User-set AllocationsWith a CS/CJ-series DeviceNet Unit, remote I/O communications slaves canbe allocated in any

108User-set Allocations Section 4-4• The first bit for node allocations is always bit 00 when setting alloca-tions with the allocated DM Area words, b

109User-set Allocations Section 4-4Procedure Step 1: Turn ON the Master Enable SwitchMake sure that master communications have disabled by checking to

110User-set Allocations Section 4-4Step 4: Turn ON the Slave User Allocations SwitchTurn ON the Slave User allocations Switch (word n, bit 11). This w

111User-set Allocations Section 4-44. Multiple masters cannot share the same slave.5. Be sure to use user-set allocations and operate the Master Unit

112User-set Allocations Section 4-4Allocation Size Setup TableResulting Slave AllocationsTurning ON the Master User Allocations SwitchTurn ON the Mast

113User-set Allocations Section 4-4Setting through the ConfiguratorSlaves can be allocated words in any order for the following blocks: OUT block1, OU

114User-set Allocations Section 4-4ProcedureStep 1Set the area, start word, and words allocated for each block using the Config-urator.Step 2Allocate

115User-set Allocations Section 4-4d) The start bit for node addresses can be bit 00 or bit 08. If it is bit08 however, 2 or more bytes cannot be allo

116Starting and Stopping Remote I/O Communications Section 4-5Configurator Setting MethodsRefer to the DeviceNet Configurator Operation Manual (W382)

xvApplication Precautions 5• Double-check all the wiring and connection of terminal blocks and con-nectors before mounting the Units.• Use crimp termi

117Example of Ladder Programming for Remote I/O Communications Section 4-6Note Even if there is a communications error with the slave, the slave input

118Errors that May Occur in Remote I/O Communications Section 4-74-7 Errors that May Occur in Remote I/O CommunicationsThe following errors may occur

119Errors that May Occur in Remote I/O Communications Section 4-7Note Remote I/O communications will stop (7-segment display: A0) if DIP switchpin 3 o

121SECTION 5Remote I/O Slave CommunicationsThis section describes the remote I/O communications performed as a DeviceNet slave by the DeviceNet Unit.5

122Slave Remote I/O Communications Section 5-15-1 Slave Remote I/O CommunicationsA CS/CJ-series DeviceNet Unit can function as a Slave Unit in remote

123Slave Remote I/O Communications Section 5-15-1-2 Remote I/O and Slave Communications Specifications5-1-3 Procedures for Using Remote I/O Slave Comm

124Slave Remote I/O Communications Section 5-1munications, allocate areas, and then enable slave communications. The allo-cated areas will not be vali

125Fixed Allocations Section 5-2Note 1. Enable slave communications in CS1W-DRM21 or CJ1W-DRM21 proper-ties if the Configurator is used.2. Use Configu

126User-set Allocations Section 5-3Fixed Allocation Area 1Fixed Allocation Area 2Fixed Allocation Area 35-3 User-set AllocationsWith a CS/CJ-series De

127User-set Allocations Section 5-32. Only two blocks (OUT 1 and IN 1) can be allocated when setting are madewith the allocated DM Area words area, bu

xviConformance to EC Directives 66 Conformance to EC Directives6-1 Applicable Directives• EMC Directives6-2 ConceptsEMC DirectivesOMRON devices that c

128User-set Allocations Section 5-3• Areas and Word Ranges for the OUT 1/IN 1 AreasStep 3: Turn ON the Slave User Allocations SwitchTurn ON the Slave

129User-set Allocations Section 5-3• Slave User Allocations Table• Slave areasStep 1: Turn ON the Slave User Allocations SwitchMake sure that slave co

130User-set Allocations Section 5-3Setting through the ConfigurationA maximum of three blocks can be allocated at any locations in I/O memoryfor the o

131User-set Allocations Section 5-3Connection Types and Allocated I/O AreasThe following table shows the relationship between various connection combi

133SECTION 6Message CommunicationsThis section describes message communications using FINS commands sent from the ladder program in the CPU Unit ofthe

134Overview Section 6-16-1 OverviewMessage communications enable messages to be set between nodes on aDeviceNet network when required by system condit

135Overview Section 6-1Overall StructureNote If only the message communications function is being used and the remote I/O communications function is n

136Overview Section 6-1Note 1. The DeviceNet Unit must be registered in the local network routing table ofthe CS/CJ-series PC when two or more Communi

137Overview Section 6-1Sending FINS Message CommunicationsReceiving FINS Message CommunicationsNote C200H-series DeviceNet Master Units (C200H-DRM21-V

138Overview Section 6-1Note A specific FINS command (command 2801) is used to send explicit mes-sages.Note A specific FINS command (command 2801) is u

xviiConformance to EC Directives 62. Wire the control panel with as thick and short electric lines as possible andground to 100 Ω min.3. Keep DeviceNe

139Overview Section 6-16-1-5 Message Communications Error IndicationsThere are two ways to obtain information on communications errors that occurin me

140Overview Section 6-16-1-6 Message Monitoring TimerA message monitoring timer monitors responses for the DeviceNet Unit. Atimer can be set for each

141FINS Commands and Responses Section 6-2termeasures and errors recorded in error history that are not shown by theindicators.Note 1. The 7-segment d

142FINS Commands and Responses Section 6-2Refer to SYSMAC CS/CJ Series Communication Commands Reference Man-ual (W342) for details on FINS commands.6-

143FINS Commands and Responses Section 6-2The main response codes are listed below. Refer to SYSMAC CS/CJ SeriesCommunication Commands Reference Manua

144FINS Commands and Responses Section 6-2Refer to SYSMAC CS/CJ Series Communication Commands Reference Man-ual (W342) for information on FINS comman

145Using FINS Message Communications Section 6-3Commands Addressed to DeviceNet UnitsCommand to Send Explicit DeviceNet Messages6-3 Using FINS Message

146Using FINS Message Communications Section 6-33. In all cases other than the following two exceptions, a local network tablemust be made, and the De

147Using FINS Message Communications Section 6-3The unit number of the DeviceNet Unit as a CPU Bus Unit is the number seton the rotary switches on the

148Using FINS Message Communications Section 6-34. Use the left-side table to create the local network table. Input the unit num-bers and correspondin

1SECTION 1Features and System ConfigurationThis section provides an overview of the DeviceNet network, including features, specifications, and system

149Using FINS Message Communications Section 6-3Note 1. Indicates a Unit as shown in the following table.2. Values of $00 to $3F indicate nodes 0 to 6

150Using FINS Message Communications Section 6-3Note 1. Indicates a Unit as shown in the following table.2. Values of $00 to $3E indicate nodes 0 to 6

151Using FINS Message Communications Section 6-3Note 1. Indicates a Unit as shown in the following table.2. Values of $00 to $3E indicate nodes 0 to 6

152Using FINS Message Communications Section 6-3Communications FlagsCommunications Flag Operation• The Network Enabled Flag turns OFF when instruction

153Using FINS Message Communications Section 6-3in the following table.Communications Instructions Completion CodesThe status at the completion of the

154Using FINS Message Communications Section 6-3Note 1. A000 to A477 in the Auxiliary Area are write-protected.2. There can be up to 13 banks of EM Me

155Using FINS Message Communications Section 6-3Program Example (021)MOV A503 D0000611A202 (021)MOV #0005 D00000 (021)MOV #0001 D00001 (021)MOV #0600

156Using FINS Message Communications Section 6-3Example 2: Sending a FINS Command Using CMNDOperation• The PC with DeviceNet Unit 1 with node address

157Using FINS Message Communications Section 6-3Example Program6-3-6 Connecting Networks for FINS CommunicationsCS/CJ-series DeviceNet Units can perfo

158Sending Explicit Messages Section 6-4When connecting networks, routing tables must be registered for the PC CPUUnits on all networks.When connectin

2Overview of DeviceNet Section 1-11-1 Overview of DeviceNetDeviceNet is a multi-bit, multi-vendor network that combines controls and dataon a machine/

159Sending Explicit Messages Section 6-46-4-1 Sending Explicit MessagesThe FINS command code 28 01 can be used to send explicit DeviceNet mes-sages to

160Sending Explicit Messages Section 6-4The following diagram shows an example of actual node address specifica-tions.Note Depending on conditions, th

161Sending Explicit Messages Section 6-4Parameters Destination node address (command): The node address of the destinationof the explicit message. (Th

162Sending Explicit Messages Section 6-4D: First response wordC: First control data wordCommand data is set in order starting with the word specified

163Sending Explicit Messages Section 6-4The response format data in service data that is in word (2-byte) or double-word (4-byte) units, such as word

164Sending Explicit Messages Section 6-4Settings (Hex).D00000 = 0009: Number of command bytesD00001 = 000A: Number of response bytesD00002 = 0001: Des

165Receiving Explicit Messages Section 6-5Program Example6-5 Receiving Explicit MessagesThis CS/CJ-series DeviceNet Unit contains a PLC Object. The Un

166Receiving Explicit Messages Section 6-5• PCs with CVM1/CV-series DeviceNet Master Units (CVM1-DRM21-V1)• PCs with CS/CJ-series DeviceNet UnitsExamp

167Receiving Explicit Messages Section 6-5I/O Memory Read/Write for CPU UnitsThe commands and responses for the explicit messages that can be sent and

168Receiving Explicit Messages Section 6-5CPU Information Read (Service Code: 0E Hex)Reads CPU Unit information, including operating mode, fatal/non-f

3Overview of DeviceNet Section 1-11-1-1 Overall System ConfigurationNote The Configurator is required if more than one Master is connected in a single

169Receiving Explicit Messages Section 6-5Read data (response): The specified information is returned in order.• CPU Unit operating mode (attribute ID

170Receiving Explicit Messages Section 6-5Response BlockParameters Destination node address (command): The node address of the CS/CJ-series DeviceNet

171Receiving Explicit Messages Section 6-5Note Error clear codes are 1-word (2-byte) data, so the above codes arespecified with the low byte first. Th

172Receiving Explicit Messages Section 6-5CPU Unit Status Read (Service Code: 40 Hex)This PLC Object service reads status details (operation status, o

173Receiving Explicit Messages Section 6-5• Operation status: Returns the operation status of the CPU Unit in 1-byte(2-digit) hexadecimal.• Operating

174Receiving Explicit Messages Section 6-5• Message Exists/Does Not Exist: When the MSG instruction is executedby the CPU Unit, the bit corresponding

175Receiving Explicit Messages Section 6-5Response BlockParameters Destination node address (command): The node address of the CS/CJ-series DeviceNet

176Receiving Explicit Messages Section 6-5Word Data Read (Service Code: 1D Hex)Word Data Read reads I/O memory area data in CPU Units with a CS/CJ-ser

177Receiving Explicit Messages Section 6-5No of Read Words (command): The number of words of read data is speci-fied in 1-byte (2-digit) hexadecimal.

178Receiving Explicit Messages Section 6-5Instance ID (command): The type of memory area to which the data will bewritten is specified in hexadecimal

4Overview of DeviceNet Section 1-1Configurator Features• Enables user-set allocations for remote I/O (choice of node address order,2 area allocations,

179Receiving Explicit Messages Section 6-5Response BlockParameters Destination node address (command): The node address of the CS/CJ-series DeviceNet

181SECTION 7Other FunctionsThis section describes connecting to CX-Programmer via the DeviceNet and the Memory Card backup function. 7-1 Connecting to

182Connecting to the CX-Programmer via the DeviceNet Section 7-17-1 Connecting to the CX-Programmer via the DeviceNetWith CX-Programmer Ver. 2.1 or la

183Connecting to the CX-Programmer via the DeviceNet Section 7-17-1-1 Setting Node AddressesWhen the CX-Programmer is connected online, it uses FINS m

184Connecting to the CX-Programmer via the DeviceNet Section 7-12. Double-click on the node address (#) that you want to change, or select thenode add

185Connecting to the CX-Programmer via the DeviceNet Section 7-1response monitor time in the CMND/SEND/RECV instruction to be thesame as or slightly l

186Memory Card Backup Functions Section 7-2a maximum of four-fold (for a communications speed of 500 Kbps) in com-parison with connection by a periphe

187Memory Card Backup Functions Section 7-27-2-1 Outline of Functions1. Backing Up Unit Setup FilesSaves all internal Unit setup data to the Memory Ca

188Memory Card Backup Functions Section 7-2Note If there is an error in the setup data or if the file could not be read, the FileRead/Write Error bit

189SECTION 8Communications TimingThis section describes the time required for remote I/O communications and message communications.8-1 Remote I/O Comm

iv

5Overview of DeviceNet Section 1-1Temperature Input Terminals• Temperature data is input as binary data for 4 inputs.• Thermocouple and platinum resis

190Remote I/O Communications Characteristics Section 8-18-1 Remote I/O Communications CharacteristicsThis section describes the characteristics of rem

191Remote I/O Communications Characteristics Section 8-1Communications Cycle Time CalculationUse the equations shown below to calculate the communicat

192Remote I/O Communications Characteristics Section 8-1Slaves with More Than 8 Bytes of Input or Out putTRT = TOH + TBYTE-IN × BIN + TBYTE-OUT × BOUT

193Remote I/O Communications Characteristics Section 8-1TIN: The Input Slave’s ON (OFF) delayTOUT: The Output Slave’s ON (OFF) delayTRM:Network’s comm

194Remote I/O Communications Characteristics Section 8-1Minimum I/O Response TimeThe minimum I/O response time occurs when the Slave’s I/O refreshing

195Remote I/O Communications Characteristics Section 8-1Note Although in the above diagram the Slaves are separated into two groups forconvenience, th

196Message Communications Section 8-2This programming is for a DeviceNet Unit with a unit number of 00.Note Refer to 3-2 Allocated CIO Area Words for

197Message Communications Section 8-2Note 1. If the CPU Unit attempts to send another message or receives a messagefrom another node within the messag

198Message Communications Section 8-2Shown below is the response time required to return data for 100 words.• BYTE DATA READ request sending time: TBR

199SECTION 9Troubleshooting and MaintenanceThis section describes error processing, periodic maintenance operations, and troubleshooting procedures ne

6Overview of DeviceNet Section 1-11-1-2 Applicable Units and DeviceNet FunctionsRemote I/O MasterDeviceNet Unit (Master)CPU UnitRemote I/O communicati

200Troubleshooting with the DeviceNet Unit Indicators Section 9-19-1 Troubleshooting with the DeviceNet Unit Indicators9-1-1 Determining Operating Sta

201Troubleshooting with the DeviceNet Unit Indicators Section 9-19-1-2 Troubleshooting Errors Occurring in the DeviceNet UnitNote 1. The 7-segment dis

202Troubleshooting with the DeviceNet Unit Indicators Section 9-1remote I/O communications for a communications error, two errors can bedisplayed: The

203Troubleshooting with the DeviceNet Unit Indicators Section 9-1CorrectionSet the slaves’ node addresses again.Structure Error: I/O Area Range Exceed

204Troubleshooting with the DeviceNet Unit Indicators Section 9-1Flags Allocated for C200H DeviceNet Master Unit (CIO n+24)Bit 14 (Error Flag) and bit

205Troubleshooting with the DeviceNet Unit Indicators Section 9-1CorrectionInspect the slave and then create the scan list again.Verification Error:I/

206Troubleshooting with the DeviceNet Unit Indicators Section 9-1DeviceNet Unit ResponseRecords the error in the error log.The master will periodicall

207Troubleshooting with the DeviceNet Unit Indicators Section 9-1• Matching master and slave baud rates• Proper cable lengths (trunk and branch lines)

208Troubleshooting with the DeviceNet Unit Indicators Section 9-1Likely CauseThe setting operation failed because a structure error occurred.DeviceNet

209Troubleshooting with the DeviceNet Unit Indicators Section 9-1return to normal when the network power supply is restored, although scan-ning will n

7Overview of DeviceNet Section 1-1Remote I/O Slave (only Units Mounted in a PC)DeviceNet Unit (Master)CPU UnitIN area OUT areaRemote I/O communication

210Troubleshooting with the DeviceNet Unit Indicators Section 9-1DeviceNet Unit ResponseRecords the error in the error log.• The Unit will go off–line

211Troubleshooting with the DeviceNet Unit Indicators Section 9-1DeviceNet Unit ResponseRecords the error in the error log.Operation will continue usi

212Troubleshooting with the DeviceNet Unit Indicators Section 9-1CorrectionClear the scan list and register the scan list again or use the Configurato

213Troubleshooting with the DeviceNet Unit Indicators Section 9-1CIO Area Flags Allocated to DeviceNet UnitBits 00 and 04 of n+10 (the Unit Error Flag

214Troubleshooting with the DeviceNet Unit Indicators Section 9-1DeviceNet Unit ResponseStops operation.CorrectionSet the communications speed correct

215Troubleshooting with the DeviceNet Unit Indicators Section 9-1DeviceNet Unit ResponseContinues processing but data exchange with the CPU Unit is st

216Troubleshooting with the DeviceNet Unit Indicators Section 9-1CIO Area Flags Allocated to DeviceNet UnitBit 00 of n+10 (Unit Error Flag) will be ON

217Troubleshooting with the DeviceNet Unit Indicators Section 9-1• Returns an error response (0302 Hex) to commands requiring a re-sponse.• Discards o

218Error Log Functions Section 9-2• Installation of terminators at both ends of the trunk line• Excessive noiseUnit ErrorsSpecial Unit ErrorDeviceNet

219Error Log Functions Section 9-2When using the Configurator, the error log can be monitored with the mastererror history read operation. With the Co

8Overview of DeviceNet Section 1-1Message CommunicationsCommunications InstructionsNote FINS message communications are supported between any two PCs

220Error Log Functions Section 9-20101 Transmission failed because the local node is not participating in the network.FINS message communications comm

221Error Log Functions Section 9-2Note The error information is not written to EEPROM when a memory error occursin the error log area (EEPROM).0343 St

222Troubleshooting Section 9-39-3 Troubleshooting9-3-1 CPU Unit’s ERR/ALM Indicator Lit or FlashingUse the following table to troubleshoot the network

223Troubleshooting Section 9-39-3-3 I/O Link ProblemsUse the following table to troubleshoot I/O Link problems.The DeviceNet Unit’s MS indicator is ON

224Troubleshooting Section 9-39-3-4 Communications Error Operation SettingsUse the following table to correct problems with the DIP switch setting for

225Maintenance and Replacement Section 9-49-4 Maintenance and ReplacementThis section describes the routine cleaning and inspection recommended asregu

226Maintenance and Replacement Section 9-49-4-3 Replacing Faulty UnitsReplace a faulty DeviceNet Unit as soon as possible. Refer to the DeviceNetSlave

227Maintenance and Replacement Section 9-4Creating a New Network FileUse the following procedure to write the settings to the DeviceNet Unit from anet

229Appendix AAllocation Differences from C200H DeviceNet Master UnitsThe following table shows the CS1W-DRM21/CJ1W-DRM21 DeviceNet Unit allocation are

230Allocation Differences from C200H DeviceNet Master Units Appendix AStatus AreasMaster Status Area 1An area with the exact same bit configuration as

9Overview of DeviceNet Section 1-1V1) or a CVM1/CV-series DeviceNet Master Unit (CVM1-DRM21-V1). Referto 6-3 Using FINS Message Communications for det

231Allocation Differences from C200H DeviceNet Master Units Appendix ACommuni-cations Error FlagIR 2001+ (10 × unit No.)Unit No. 0 to 9: IR 101+(10 ×

232Allocation Differences from C200H DeviceNet Master Units Appendix AMaster Status Area 2Communications Cycle Time Present ValueRegistered Slave Tabl

233Allocation Differences from C200H DeviceNet Master Units Appendix ANormal Slave TableReplacing Ladder Programs from C200HW-DRM21-V1If ladder progra

234Allocation Differences from C200H DeviceNet Master Units Appendix AReplace the addresses as shown in the following table.Message Communications in

235Appendix BDeviceNet ConnectionsDeviceNet has several different protocols for remote I/O communications between Master and Slave devices.Connections

236DeviceNet Connections Appendix BConnections Using AllocationsSetting Connection TypeThe settings for remote I/O communications connections differ d

237DeviceNet Connections Appendix BNote 1. Output data using poll connections and output data using COS or cyclic connections are transmittedusing th

238DeviceNet Connections Appendix BMaster COS Send SwitchCOS transmission is possible only for User-set allocations using the Configurator.When requir

239DeviceNet Connections Appendix BThe following diagram shows the transmission timing. After the COS send instruction has been sent to theDeviceNet (

241Appendix CFINS Commands and Responses for DeviceNet UnitsList of Command CodesRefer to SYSMAC CS/CJ Series Communication Commands Reference Man-ual

10Overview of DeviceNet Section 1-1General-purpose Slaves (Communications Cable: Normal Square Connectors)Name Appearance I/O points Model number Rema

242FINS Commands and Responses for DeviceNet Units Appendix C• Baud rateCommand BlockResponse BlockEnd CodesParameter Details[Model, Version] (Respons

243FINS Commands and Responses for DeviceNet Units Appendix CResponse BlockEnd CodesParameter Details[Operation status, Units status 1, Unit status 2,

244FINS Commands and Responses for DeviceNet Units Appendix CFor commands, the data to be sent to the specified node is specified, with amaximum of 53

245FINS Commands and Responses for DeviceNet Units Appendix CReturns the error history for the number specified by Read Record No., inorder from the R

246FINS Commands and Responses for DeviceNet Units Appendix CEnd CodesImportant PointThe Error History Clear command clears the RAM and EEP-ROM error

247Appendix DMemory Card Backup FunctionsThe DeviceNet Unit stores the following setup data in the internal non-volatile memory (EEPROM).• Master scan

248Memory Card Backup Functions Appendix DOutline of Functions1. Backing Up Unit Setup FilesSaves all internal Unit setup data to the Memory Card moun

249Memory Card Backup Functions Appendix D3. Saving Files from Configurator to Memory CardDevice parameter files (.dvf files) for this DeviceNet Unit

251Appendix EMulti-vendor ApplicationsThis appendix provides precautions and reference material needed when using DeviceNet (CompoBus/D)Units as Devic

252Multi-vendor Applications Appendix EMaster Unit Device ProfileObject MountingIdentity Object (01 Hex)Message Router Object (02 Hex)General data Com

11Overview of DeviceNet Section 1-1Note For details on Slaves, refer to the DeviceNet (CompoBus/D) Slaves OperationManual (W347).Sensor Terminals 16 i

253Multi-vendor Applications Appendix EDeviceNet Object (03 Hex)Connection Object (05 Hex)Item ID content Get (read) Set (write) ValueObject class Att

254Multi-vendor Applications Appendix EObject instance 1 Section Information Max. No. of instancesInstance typeExplicit Message 1Produc-tion trig-gerC

255Multi-vendor Applications Appendix ENote 1. Number of input bytes used by Slave.2. Number of output bytes used by Slave.Object instance 2 Section

256Multi-vendor Applications Appendix ENote 1. Number of input bytes used by Slave.Object instance 3 Section Information Max. No. of instancesInstanc

257Multi-vendor Applications Appendix ENote 1. Number of input bytes used by Slave.Object instance 4 Section Information Max. No. of instancesInstanc

258Multi-vendor Applications Appendix E1. The following table shows the instance type by communications type.2. The following table shows the transpor

259Multi-vendor Applications Appendix EDeviceNet service Parameter optionObject instance 1 (CIO area)Service 1CBlock String Read Logical Area Address

260Multi-vendor Applications Appendix ENote The refresh area types are shown in the following table.PC area Refresh area type Refresh addressCIO 1 CIO

261Appendix FDeviceNet Explicit Message Send Command for Other Manufacturer NodesExplicit Message Send (2801)Sends a DeviceNet explicit message to a s

262DeviceNet Explicit Message Send Command for Other Manufacturer Nodes Appendix FParameter Details[Send Destination Node Address] (Command)Specifies

12Overview of DeviceNet Section 1-1Waterproof and Environment-resistant Slaves (Communications Cable: Round Connectors)Special Slaves (Communications

263IndexAadaptorsremote, 4, 10allocationsSee also I/O allocationsapplicable Units, 6applicationsprecautions, xivCC200HW-DRM21-V1changing ladder progra

264Indexspecifications, 34dimensions, 55DM AreaSee also I/O allocationsdot indicatorsSee also seven-segment displayEEC Directives, xviEEPROMdata, 26,

Index265display section, 27Master Unit, 200meaning, 47message communications errors, 139seven-segment display, 48statusMS and NS, 47troubleshooting, 2

266IndexSsafety precautions, xiiscan lists, 99errors, 224setupsaving setup files, 19, 186, 247seven-segment displaymeaning, 48Slave Units, 7, 9, 20com

267Revision HistoryA manual revision code appears as a suffix to the catalog number on the front cover of the manual. The following table outlines the

13Overview of DeviceNet Section 1-1MULTIPLE I/O TERMINAL UnitsUnit I/O pointsWords allocated in PC memoryI/O connec-tionsUnit power supply voltageInst

14Overview of DeviceNet Section 1-1Note The front-panel indicators and other parts of Analog Input Units, Analog Out-put Units, and Counter Units diff

vNotice:OMRON products are manufactured for use according to proper procedures by a qualified operatorand only for the purposes described in this manu

15DeviceNet Unit Features Section 1-21-1-5 DeviceNet ConfiguratorUse version 2 of the DeviceNet Configurator for the CS1W-DRM21/CJ1W-DRM21 DeviceNet U

16DeviceNet Unit Features Section 1-2Explicit Message CommunicationsNote Refer to 6-4 Sending Explicit Messages for details on remote I/O communica-ti

17DeviceNet Unit Features Section 1-2taneously. A Unit that is used as a slave supports fixed and user-set alloca-tions. The maximum I/O for the slave

18DeviceNet Unit Features Section 1-2CX-Programmer Programming and Monitoring of DeviceNet Slave PCs (Ver. 2.1 or Later)CX-Programmer Ver. 2.1 connect

19DeviceNet Unit Features Section 1-2Multiple PCs in a Single NetworkMultiple DeviceNet Units can be connected in a single network for messagecommunic

20DeviceNet Unit Features Section 1-2a DeviceNet Unit. (See Appendix D Memory Card Backup Function for moredetails.) Note Refer to 7-2 Memory Card Bac

21Specifications Section 1-31-3 Specifications1-3-1 DeviceNet UnitModelGeneral Specifications General specifications of the CS/CJ-series DeviceNet Uni

22Specifications Section 1-3Words allo-cated in the CPU Unit DeviceNet remote I/O communi-cations When used as a MasterFixed alloca-tionsFixed words i

23Specifications Section 1-3Remote I/O master com-municationsSlave allocation method Fixed allo-cationsSelect one of the following fixed allocation ar

24Specifications Section 1-3Remote I/O master Max. No. of Slaves con-nected per DeviceNet UnitFixed allocations 63 nodesUser-set allocationsBy allo-ca

viTrademarks and CopyrightsDeviceNet is a registered trademark of the Open DeviceNet Vendor Association, Inc.Windows, Windows 95, Windows 98, Windows

25Specifications Section 1-3Remote I/O slaveAllocation method Fixed allo-cationsSelect one of the following fixed allocation areas using the Slave Fix

26Specifications Section 1-3Default settings • Scan list: Not supported • Master communications: Supported• Slave communications: Disabled• Remote I/O

27Specifications Section 1-3Other func-tionsRemote programming/monitoring func-tionsA CX-Programmer connected to the serial communications port of a P

28Specifications Section 1-31-3-2 Comparison between CS1W-DRM21 and CJ1W-DRM21Only the following items are different between the CS1W-DRM21 and theCS1

29Comparison with Previous Models Section 1-41-4 Comparison with Previous ModelsThe following table provides a comparison between the CS1W-DRM21Device

30Comparison with Previous Models Section 1-4Remote I/O communica-tions MasterFixed alloca-tionsC200H DeviceNet words in CIO Area1,600 points (50 inpu

31Comparison with Previous Models Section 1-4Remote I/O communica-tions MasterMax. No. of slaves con-nectedWith no Configurator (fixed allocations): 5

32Comparison with Previous Models Section 1-4Starting and stopping remote communications during I/O communicationsStarts or stops remote I/O communica

33Outline of the Configurator Section 1-51-5 Outline of the ConfiguratorAllocations for remote I/O communications can be set in any order of nodeaddre

34Outline of the Configurator Section 1-5Note 1. Master device parameters used in a scan list are created with either of thefollowing methods.a) Using

viiTABLE OF CONTENTSPRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi1 Intended Audience . . . . . . . . . . . . . . .

35Outline of the Configurator Section 1-5Main functions Setup functions Master device parameter settings for OMRON’s Master• Remote I/O master allocat

36Basic Operating Procedures Section 1-61-6 Basic Operating Procedures1-6-1 Network Installation ProcedureNote For details on the network installation

37Basic Operating Procedures Section 1-6Node address (Pins 1 to 6)Baud rate (Pins 7 and 8)Etc.3. Mount the Master and wire the network.Treat as a CPU

38Basic Operating Procedures Section 1-6message communications may not be possible unless the DeviceNet Unitis registered in the local network table.1

39Basic Operating Procedures Section 1-63. Check Unit Status 2 (word n+11, bit 03) from a Programming Device con-nected to the CPU Unit to see if the

40Basic Operating Procedures Section 1-62. Check Unit Status 2 (word n+11, bit 07) from a Programming Device con-nected to the CPU Unit to see if the

41Basic Operating Procedures Section 1-64. Switch the CPU Unit to RUN mode. Slave remote I/O communications willbegin.Message Communications Only (Nei

42List of Usage Methods by Purpose Section 1-71-7 List of Usage Methods by PurposeSituation Action PageDesign Allocating any words for remote I/OIn or

43List of Usage Methods by Purpose Section 1-7Operation Stopping remote I/O communica-tions with all SlavesStop communications using the Configurator

45SECTION 2Nomenclature and InstallationThis section describes the nomenclature and installation of the DeviceNet Unit.2-1 Nomenclature and Functions

viiiTABLE OF CONTENTSSECTION 5Remote I/O Slave Communications. . . . . . . . . . . . . . . . . 1215-1 Slave Remote I/O Communications . . . . . . .

46Nomenclature and Functions Section 2-12-1 Nomenclature and Functions2-1-1 Nomenclature and FunctionsCS1W-DRM21CJ1W-DRM21IndicatorsThe DeviceNet Unit

47Nomenclature and Functions Section 2-12-1-2 Status Indicators: MS and NSThe MS (Module Status) indicator indicates the status of the node itself and

48Nomenclature and Functions Section 2-12-1-3 Seven-Segment DisplayIn addition to the MS and NS indicators, DeviceNet Units have a 2-digit, 7-segment

49Nomenclature and Functions Section 2-1The following diagram shows the alternating error code/ node address display.The master’s error code and maste

50Nomenclature and Functions Section 2-1Note 1. The node address is set to 63 at the factory.2. Any node address from 0 through 63 can be set as long

51Installing the DeviceNet Unit Section 2-2Continue/Stop Remote I/O CommunicationsWhen the DeviceNet Unit is used as a master, pin 3 is used to set wh

52Installing the DeviceNet Unit Section 2-2• In the CS-series, up to 16 Units can be mounted to the CS1W-BC 3CPU Backplane or CS1W-BI3 Expansion CPU B

53Installing the DeviceNet Unit Section 2-2Note When mounting the Unit, provide the clearance shown below to facilitate easymounting or dismounting.CJ

54Installing the DeviceNet Unit Section 2-2• Provide separate conduits or ducts for the I/O lines to prevent noise fromhigh-tension lines or power lin

55Installing the DeviceNet Unit Section 2-22-2-4 External DimensionsCS1W-DRM21 These diagrams show the dimensions of the DeviceNet Unit. Refer to the

ixAbout this Manual:This manual describes the installation and operation of CS1W-DRM21 DeviceNet Unit for SYSMACCJ-series PLCs and the CJ1W-DRM21 Devi

57SECTION 3Allocated CIO and DM WordsThis section describes the words allocated to the DeviceNet Unit in the CIO Area and DM Area. These words both en

58Overview of Word Allocations Section 3-13-1 Overview of Word AllocationsThe words shown in the following diagram are allocated according to the unit

59Overview of Word Allocations Section 3-13-1-1 Allocated CIO Area WordsSoftware switches, DeviceNet Unit status, and error data are allocated in theC

60Allocated CIO Area Words Section 3-23-2 Allocated CIO Area WordsData is stored at the offset positions shown in the figure below starting fromthe fi

61Allocated CIO Area Words Section 3-2• Unit status area 2 (word n+11)• Master Status 1 (word n+12)Word n [n = CIO 1,500 + (25 x unit number)]Bit Name

62Allocated CIO Area Words Section 3-202 Remote I/O Com-munica-tions Start SwitchOFF→ONUser Starts remote I/O communications.Note 1. The switch is ign

63Allocated CIO Area Words Section 3-206 Master Enable SwitchOFF→ONUser Enables master communications. (The Unit automati-cally restarts.)Once enabled

64Allocated CIO Area Words Section 3-211 Master User-set Alloca-tions SwitchOFF→ONUser Reads setup data from the Master User Allocations Setup Table (

65Allocated CIO Area Words Section 3-23-2-2 Software Switches 2 (Word n+1)All switches are turned ON by the user. The Unit automatically turns themOFF

66Allocated CIO Area Words Section 3-206 Slave Enable SwitchOFF→ONUser Enables slave communications. (The Unit automatically restarts.)To use fixed al

xSYSMAC CS/CJ Series Communication Com-mands Reference ManualCS1G/H-CPU-E CPU UnitsCS1W-SCB21/41 Serial Communications BoardsCS1W-SCU21 Serial Communi

67Allocated CIO Area Words Section 3-208 Slave Fixed Allo-cation Set-ting 1 SwitchOFF→ONUser Allocates the following words to the slave.• OUT 1 area (

68Allocated CIO Area Words Section 3-211 Slave User Alloca-tions SwitchOFF→ONUser Reads setup data from the Slave User Allocations Setup Table in the

69Allocated CIO Area Words Section 3-2Note 1. When the Master function is enabled, the Unit Setup File cannot be backedup unless the scan list is enab

70Allocated CIO Area Words Section 3-2Remote I/O communications will restart if a user turns OFF a bit that is ON.More than one of these switches may

71Allocated CIO Area Words Section 3-23-2-5 Unit Status 1 (Word n+10)Word n+10 [n = CIO 1,500 + (25 x unit number)]Bit Name Status Controlled byUnit o

72Allocated CIO Area Words Section 3-23-2-6 Unit Status 2 (Word n+11)Word n+11 [n = CIO 1,500 + (25 x unit number)]07 Network Power Error FlagON Unit

73Allocated CIO Area Words Section 3-201 Remote I/O Communica-tions FlagON Unit Indicates that remote I/O communications are being performed for the m

74Allocated CIO Area Words Section 3-23-2-7 Master Status 1 (Word n+12)Word n+12 [n = CIO 1,500 + (25 x unit number)]Bit Name Status Controlled byUnit

75Allocated CIO Area Words Section 3-23-2-8 Master Status 2 (Word n+13)The leftmost eight bits indicate the status of master I/O allocations.Master I/

76Allocated CIO Area Words Section 3-23-2-9 Slave Status 1 (Word n+14)Word n+14 [n = CIO 1,500 + (25 x unit number)]Bit Name Status Controlled byUnit

xiPRECAUTIONSThis section provides general precautions for using the DeviceNet Unit and related devices.The information contained in this section is i

77Allocated CIO Area Words Section 3-211 COS Send Failed FlagON Unit Indicates that an attempt was made to send COS to a Master using the Slave COS se

78Allocated CIO Area Words Section 3-23-2-10 Slave Status 2 (Word n+15)Master Node Addresses This indicates the node address of the remote master for

79Allocated CIO Area Words Section 3-23-2-12 Normal Slave Table (Words n+20 to n+23)This table indicates the slaves that are communicating normally wi

80Allocated CIO Area Words Section 3-2Note Although the bit configurations are the same, the word addresses are different(because this is a CS/CJ-seri

81Allocated DM Area Words Section 3-33-3 Allocated DM Area WordsData is stored at the offset positions shown in the figure below starting fromthe firs

82Allocated DM Area Words Section 3-3Note If the setting is smaller than the optimum communications cycle time calcu-lated by the Unit and stored inte

83Allocated DM Area Words Section 3-3Note Make sure the CPU Unit is in PROGRAM mode and the master function isenabled before you set these values.Note

84Allocated DM Area Words Section 3-3Setting Results3-3-3 Allocation Size Setup TableThe following allocation size setup tables must be set in the I/O

85Allocated DM Area Words Section 3-3Setting ExampleThe following example shows the allocation when the size (bytes) for OUTblock 1 and IN block 1 is

86Allocated DM Area Words Section 3-3Areas and Word RangesSetting ResultsName Range DetailsSlave OUT 1 area See Areas and Word Ranges.Specifies the OU