E5AR - Temperature Controller OMRON - Free user manual and instructions

USER MANUAL E5AR OMRON

E5AR/ER Digital Controller DeviceNet Communications User’s Manual Produced February 2004

Notice: OMRON products are manufaciured for use according to proper procedures by a qualified operator and only for the purposes described in this manual. This manual describes the functions, performance, and application methods needed for optimum use of the E5AR/E5ER-DRT Digital Controllers. Please observe the following items when using the ESAR/E5ER-DRT Digital Controllers. + This product is designed for use by qualified personnel with a knowledge of electrical systems. + Read this manual carefully and make sure you understand it well to ensure that you are using the ESAR/E5ER-DRT Digital Controllers correctly. + Keep this manual in a safe location so that it is available for reference when required. Visual Aids The following headings appear in the left column of the manual to help you locate different types of information. Note Indicates information of particular interest for efficient and convenient opera- tion of the product. 1,2,3.. 1. Indicates lists of one sort or another, such as procedures, checklists, etc. Trademarks + COMBICON is a registered trademark of Phoenix Contact. + DeviceNet is a registered trademark of the Open DeviceNet Vendors Association, Inc. + Other product names and company names that appear in this manual are the trademarks or regis- tered trademarks of the respective companies. © OMRON, 2004 All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form, or by any means, mechanical, electronic, photocopying, recording, or otherwise, without the prior written permission of OMRON. No patent liability is assumed with respect to the use of the information contained herein. Moreover, because OMRON is con- Stantly striving to improve its high-quality products, the information contained in this manual is subject to change without notice. Every precaution has been taken in the preparation of this manual. Nevertheless, OMRON assumes no responsibility for errors or omissions. Neither is any liability assumed for damages resulting from the use of the information contained in this publication.

Read and Understand this Manual Please read and understand this manual before purchasing the product. Please consult your OMRON representative if you have any questions or comments. Warranty and Limitations of Liability WARRANTY OMRON's exclusive warranty is that the products are free from defects in materials and workmanship for a period of one year (or other period if specified) from date of sale by OMRON. OMRON MAKES NO WARRANTY OR REPRESENTATION, EXPRESS OR IMPLIED, REGARDING NON- INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR PARTICULAR PURPOSE OF THE PRODUCTS. ANY BUYER OR USER ACKNOWLEDGES THAT THE BUYER OR USER ALONE HAS DETERMINED THAT THE PRODUCTS WILL SUITABLY MEET THE REQUIREMENTS OF THEIR INTENDED USE. OMRON DISCLAIMS ALL OTHER WARRANTIES, EXPRESS OR IMPLIED.

LIMITATIONS OF LIABILITY

OMRON SHALL NOT BE RESPONSIBLE FOR SPECIAL, INDIRECT, OR CONSEQUENTIAL DAMAGES, LOSS OF PROFITS OR COMMERCIAL LOSS IN ANY WAY CONNECTED WITH THE PRODUCTS, WHETHER SUCH CLAIM IS BASED ON CONTRACT, WARRANTY, NEGLIGENCE, OR STRICT LIABILITY. In no event shall the responsibility of OMRON for any act exceed the individual price of the product on which liability is asserted. IN NO EVENT SHALL OMRON BE RESPONSIBLE FOR WARRANTY, REPAIR, OR OTHER CLAIMS REGARDING THE PRODUCTS UNLESS OMRON'S ANALYSIS CONFIRMS THAT THE PRODUCTS WERE PROPERLY HANDLED, STORED, INSTALLED, AND MAINTAINED AND NOT SUBJECT TO CONTAMINATION, ABUSE, MISUSE, OR INAPPROPRIATE MODIFICATION OR REPAIR. Application Considerations

OMRON shall not be responsible for conformity with any standards, codes, or regulations that apply to the combination of products in the customers application or use of the products. At the customer's request, OMRON will provide applicable third party certification documents identifying ratings and limitations of use that apply to the products. This information by itself is not sufficient for a complete determination of the suitability of the products in combination with the end product, machine, system, or other application or use. The following are some examples of applications for which particular attention must be given. This is not intended to be an exhaustive list of all possible uses of the products, nor is it intended to imply that the uses listed may be suitable for the products. + Outdoor use, uses involving potential chemical contamination or electrical interference, or conditions or uses not described in this manual. - Nuclear energy control systems, combustion systems, railroad systems, aviation systems, medical equipment, amuse- ment machines, vehicles, safety equipment, and installations subject to separate industry or government regulations. + Systems, machines, and equipment that could present a risk to life or property. Please know and observe all prohibitions of use applicable to the products. NEVER USE THE PRODUCTS FOR AN APPLICATION INVOLVING SERIOUS RISK TO LIFE OR PROPERTY WITHOUT ENSURING THAT THE SYSTEM AS À WHOLE HAS BEEN DESIGNED TO ADDRESS THE RISKS, AND THAT THE OMRON PRODUCTS ARE PROPERLY RATED AND INSTALLED FOR THE INTENDED USE WITHIN THE OVERALL EQUIPMENT OR SYSTEM. PROGRAMMABLE PRODUCTS OMRON shall not be responsible for the user's programming of a programmable product, or any consequence thereof.

Product specifications and accessories may be changed at any time based on improvements and other reasons. Itis our practice to change model numbers when published ratings or features are changed, or when significant construction changes are made. However, some specifications of the products may be changed without any notice. When in doubt, special model numbers may be assigned to fix or establish key specifications for your application on your request. Please consult with your OMRON representative at any time to confirm actual specifications of purchased products.

DIMENSIONS AND WEIGHTS

Dimensions and weights are nominal and are not to be used for manufacturing purposes, even when tolerances are shown. PERFORMANCE DATA Performance data given in this manual is provided as a guide for the user in determining suitability and does not constitute a warranty. It may represent the result of OMRON's test conditions, and the users must correlate it to actual application requirements. Actual performance is subject to the OMRON Warranty and Limitations of Liability.

ERRORS AND OMISSIONS

The information in this manual has been carefully checked and is believed to be accurate; however, no responsibility is assumed for clerical, typographical, or proofreading errors, or omissions.

Precautions for Safe Use © Definition of Safety Notices and Information © Symbols viii The following notation is used in this manual to provide precautions required to ensure safe usage of the product. The safety precautions that are provided are extremely important to safety. Always read and heed the information provided in all safety precautions. The following notation is used. Indicates a potentially hazardous situation which, if not avoided, will result in minor or moderate injury, or may result À WARNING in serious injury or death. Additionally there may be significant property damage. Indicates a potentially hazardous situation which, if not VAN (7: \H (eo R avoided, may result in minor or moderate injury or in property damage. Symbol Meaning General Caution Indicates non-specific general cautions, warnings, and dangers. Caution Electrical Shock Caution Indicates possibility of electric shock under specific conditions. Prohibition Indicates non-specific general prohibitions. General Caution Indicates non-specific general cautions, warnings, and dangers. Mandatory Caution e0b& EE

© Precautions À WARNING Always provide protective circuits in the network. Without protective cir- cuits, malfunctions may possibly result in accidents that cause serious injury or significant property damage. Provide double or triple safety mea- sures in external control circuits, such as emergency stop circuits, inter- lock circuits, or limit circuits, to ensure safety in the system if an abnormality occurs due to malfunction of the product or another external factor affecting the product's operation.

Do not attempt to disassemble, repair, or modify the product. Doing so may occasionally result in minor injury due to electric shock. À CAUTION Do not touch the terminals, or electronic components or patterns on the PCB within 1 minute after turning OFF the power. Doing so may occa- sionally result in minor injury due to electric shock. Do not allow pieces of metal, wire clippings, or fine metallic shavings or filings from installation to enter the product. Doing so may occasionally result in electric shock, fire, or malfunction. Do not use the product in locations where flammable or explosive gases are present. Doing so may occasionally result in minor or moderate explosion, causing minor or moderate injury, or property damage. Do not attempt to disassemble, repair, or modify the product. Doing so may occasionally result in minor or moderate injury due to electric shock. Tighten the screws on the terminal block and the connector locking screws securely using a tightening torque within the following ranges. Loose screws may occasionally cause fire, resulting in minor or moderate injury, or damage to the equipment. Terminal block screws: 0.40 to 0.56 N-m Connector locking screws: 0.25 to 0.30 N-m Perform correct setting of the product according to the application. Failure to do so may occasionally cause unexpected operation, resulting in minor or moderate injury, or damage to the equipment. Ensure safety in the event of product failure by taking safety measures, such as installing a separate overheating prevention alarm system. Prod- uct failure may occasionally prevent control, or operation of alarm out- puts, resulting in damage to the connected facilities and equipment. Do not use the equipment for measurements within Measurement Cate- gories Il, Ill, or IV (according to IEC61010-1). Doing so may occasionally cause unexpected operation, resulting in minor or moderate injury, or damage to the equipment. Use the equipment for measurements only Within the Measurement Category for which the product is designed. The service life of the output relays depends on the switching capacity and switching conditions. Consider the actual application conditions and use the product within the rated load and electrical service life. Using the product beyond its service life may occasionally result in contact welding or burning. >. 6 000

CAUTION Make sure that the product will not be adversely affected if the DeviceNet cycle time is lengthened as a result of changing the program with online editing. Extending the cycle time may cause unexpected operation, occa- VAN sionally resulting in minor or moderate injury, or damage to the equip- ment. Before transferring programs to other nodes or changing 1/0 memory of other nodes, check the nodes to confirm safety. Changing the program or 1/0 memory of other nodes may occasionally cause unexpected opera- VAN tion, resulting in minor or moderate injury, or damage to the equipment.

Precautions for Safe Use

Use and store the product within the specified ambient temperature and humidity ranges. lf several products are mounted side-by-side or arranged in a vertical line, the heat dissipation will cause the internal temperature of the products to rise, shortening the service life. If necessary, cool the prod- ucis using a fan or other cooling method. Provide sufficient space around the product for heat dissipation. Do not block the vents on the product. Use the product within the noted supply voltage and rated load. Be sure to confirm the name and polarity for each terminal before wiring the terminal block and connectors. Do not connect anything to unused terminals. Use the specified size of crimp terminals (M3, width: 5.8 mm max.) for wir- ing the terminal block. To connect bare wires to the terminal block, use AWG22 to AWG14 (cross- sectional area: 0.326 to 2.081 mm?) to wire the power supply terminals and AWG28 to AWG16 (cross-sectional area: 0.081 to 1.309 mm?) for other terminals. (Length of exposed wire: 6 to 8 mm) Ensure that the rated voltage is achieved no longer than 2 s after turning the power ON. Turn OFF the power first before drawing out the product. Never touch the terminals or the electronic components, or subject them to physical shock. When inserting the product, do not allow the electronic components to con- tact the case. Do not remove the inner circuit board. Output turns OFF when shifting to the initial setting level in certain modes. Take this into consideration when setting up the control system. . Allow the product to warm up for at least 30 minutes after the power is turned ON. . Install surge absorbers or noise filters in devices near the product that gen- erate noise (in particular, devices with an inductance component, such as motors, transformers, solenoids, and magnetic coils). If a noise filter is used for the power supply, check the voltage and current, and install the noise filter as close as possible to the product. Separate the product as far as possible from devices generating strong high-frequency noise (e.g., high-frequency welders and high-frequency sewing machines) or surges. Do not tie noise filter input/output wires together. . Keep the wiring for the product's terminal block and connector separate from high-voltage, high-current power lines to prevent inductive noise. Do not run the wiring parallel to or in the same cable as power lines. The influ- ence of noise can also be reduced by using separate wiring ducts or shield lines. . Install an external switch or circuit breaker and label them clearly so that the operator can quickly turn OFF the power.

16. Do not use the product in the following locations.

+ Locations where dust or corrosive gases (in particular, sulfuric or ammo- nia gas) are present. + Locations where icing or condensation may occur. + Locations exposed to direct sunlight. + Locations subject to excessive shock or vibration. + Locations where the product may come into contact with water or oil. + Locations subject to direct radiant heat from heating equipment. + Locations subject to extreme temperature changes.

17. Cleaning: Do not use thinners. Use commercially available alcohol.

18. Use the specified cables for the communications lines and stay within the

specified DeviceNet communications distances.

19. Do not pull the DeviceNet communications cables with excessive force or

bend them past their natural bending radius.

20. Do not connect or remove connectors while the DeviceNet power is being

supplied. Doing so will cause product failure or malfunction.

EC Directives Concepts Conformance to EC D 1,2,3... 1,2,3... + EMC Directives EMC Directives OMRON devices that comply with EC Directives also conform to the related EMC standards so that they can be more easily built into other devices or the overall machine. The actual products have been checked for conformity to EMC standards. Whether the products conform to the standards in the system used by the customer, however, must be checked by the customer. EMC-related performance of the OMRON devices that comply with EC Direc- tives will vary depending on the configuration, wiring, and other conditions of the equipment or control panel on which the OMRON devices are installed. The customer must, therefore, perform the final check to confirm that devices and the overall machine conform to EMC standards. irectives The E5AR/E5ER-DRT Digital Controllers comply with EC Directives. To ensure that the machine or device in which the Unit is used complies with EC Directives, the Unit must be installed as follows:

1. You must use reinforced insulation or double insulation for the DC power

supplies used for the communications power supply, internal power supply, and 1/0 power supplies.

2. Units complying with EC Directives also conform to the Common Emission

Standard (EN61326). Radiated emission characteristics (10-m regula- tions) may vary depending on the configuration of the control panel used, other devices connected to the control panel, wiring, and other conditions. You must therefore confirm that the overall machine or equipment complies with EC Directives. The following example shows one means of reducing noise.

1. Noise from the communications cable can be reduced by installing a ferrite

core on the communications cable within 10 cm of the DeviceNet Master Unit. Ferrite Core (Data Line Filter): 0443-164151 (manufactured by Fair-Rite Products Co., Ltd.) Impedance specifications 25 MHz 105Q 100 MHz 190Q xii

13mm 29 mm [ O] Wire the control panel with as thick and short electric lines as possible and ground to 100 Q min. Keep DeviceNet communications cables as short as possible and ground to 100 Q min.

Operating Procedures. .......... 2-1 2-2 Functions Supported Only by the ESAR/ER-DRT ................................

Troubleshooting and Maintenance .................... 7-1 Indicators and Error Processing 7-2 Maintenance

About this Manual: This manual describes the installation and operation of the E5SAR/E5ER-DRT Digital Controllers and includes the sections described below. Please read this manual carefully and be sure you understand the information provided before attempting to install or operate an ESAR/E5ER-DRT Digital Controller. Be sure to read the precautions provided in the following section. Precautions provides general precautions for using E5SAR/E5ER-DRT Digital Controllers and related devices.

Section 1 introduces the features and specifications of E5AR/E5ER-DRT Digital Controllers.

Section 2 outlines the basic operating procedures for the E5AR/E5ER-DRT Digital Controllers.

Section 3 describes the methods used to install and wire E5AR/E5ER-DRT Digital Controllers.

Section 4 describes the input (IN) areas and output (OUT) areas that E5AR-DRT and E5ER-DRT Dig-

ital Controllers can use for remote 1/0 communications. The methods to allocate data for master com- munications are also described using sample programming.

Section 5 describes how to send explicit messages to the ESAR/E5ER-DRT Digital Controller, includ-

ing how to send CompoWay/F commandés using explicit messages.

Section 6 provides information on the time required for a complete communications cycle, for an out-

put response to be made to an input, to start the system, and to send messages.

Section 7 describes error processing, periodic maintenance operations, and troubleshooting proce-

dures needed to keep the DeviceNet Network operating properly. Details on resetting replaced Con- trollers are also provided. Read through the error processing procedures in both this manual and the operation manual for the DeviceNet master being used before operation so that operating errors can be identified and corrected more quickly. The Appendices provide the device profile of the DeviceNet Communications Unit, additional informa- tion on DeviceNet, a list of hardware products for DeviceNet, and the DeviceNet objects that are mounted. A\ WARNING Failure to read and understand the information provided in this manual may result in per- sonal injury or death, damage to the product, or product failure. Please read each section in its entirety and be sure you understand the information provided in the section and related sections before attempting any of the procedures or operations given. Xvii

Related Manuals: The following manuals are related to operating a system containing the ESAR/E5ER. Read and under- stand all related manuals before attempting to use the ESAR/ESER in an actual system. Operation Manual Name Cat. No. Contents E5AR/ER Digital Controller H124 Describes the E5AR/E5ER DeviceNet-compatible Digi- DeviceNet Communications tal Controllers that are available along with the User's Manual DeviceNet functions, specifications, and operating methods. E5AR/E5ER Digital Controller Z182 Describes the E5AR/E5ER Digital Controllers that are User's Manual available along with functions, specifications, and oper- ating methods. Refer to this manual for information on all specifications and functions except those for DeviceNet. DeviceNet Operation Manual W267 Describes the configuration of a DeviceNet network, connection types, and other information related to DeviceNet, including how to use network cables and connectors and their specifications, along with the methods for supplying communications power. CVM1/CV DeviceNet Master Unit W379 Describes the specifications, functions, and application C200HX/HG/HE and C200HS methods of the CVM1/CV DeviceNet Master Unit and DeviceNet Master Unit the C200HX/HG/HE and C200HS DeviceNet Master Operation Manual Unit. CS/CJ DeviceNet Unit W380 Describes the specifications, functions, and application Operation Manual methods of the CS/CJ DeviceNet Unit. (The CS/CJ DeviceNet Unit can function simultaneously both as a DeviceNet master and as a slave.) DeviceNet Configurator Ver. 2 W382 Describes the operation methods of the DeviceNet Configurator. The DeviceNet Configurator is a Support Software package that provides graphic display opera- tions to construct, set up, and maintain a DeviceNet network.

1-1 Features 1-1-1 Outline The ESAR-DRT and E5ER-DRT (E5AR/ER-DRT) are Digital Controllers that use DeviceNet for communications. The E5AR/ER-DRT Digital Controllers are slaves that connect to the DeviceNet open field network. DeviceNet communications enable controlling operation, collecting measurement data, and writing settings from a host com- puter or PLC. The E5AR/ER-DRT support both remote 1/0 communications and explicit message communications. Remote 1/0 communications allow the master and the E5AR/ER-DRT to auto- matically share data via high-speed 1/0 without any special programming of the master. Remote 1/0 communications are particularly suited to operation control, error warnings, and monitoring applications. Explicit messages use a communications protocol for sending commands and receiving responses. The main application for explicit message communica- tions is for changing E5SAR/ER-DRT settings data. 1-1-2 Communications Connection Example Host computer Host link PLC DeviceNet Unit Le + CPU Unit Remote O0 Devicenet Explicit messages Explicit messages | Configurator

ESAR/ER-DRT| | ESAR/ER-DRT| ESAR/ER-DRT

1-1-3 Using DeviceNet Remote 1/0 Communications The master and E5AR/ER-DRT Digital Controllers can share 1/0 by using remote 1/0 communications. Data in the ESAR/ER-DRT Digital Controllers, such as process values (PVs) and set points (SPs), can be allocated for com- munications with the master to enable sending and receiving the allocated data via remote 1/0 communications without requiring special programming.

Explicit Message Communications Automatically Detects Baud Rate + User-set Data Allocations with a Configurator The specific data required for communications with the master can be allocated by using 1/0 allocations from the DeviceNet Configurator. + By sending commands from a PLC, various operations can be performed, including reading/writing specific monitor values and parameters, such as reading process values or writing set points, and performing operations using operation commands. CompoWay/F communications commands can also be executed using explicit message communications. + Previously, the baud rate had to be set for each slave, but the E5AR/ER- DRT Digital Controllers automatically detect and match the baud rate of the master, so this setting is not required. (If the master's baud rate is changed, turn OFF the communications power supply to the Digital Con- troller and then turn it ON again.) 1-1-4 Default Communications Settings The default settings required for communications when ESAR/ER-DRT are used as DeviceNet slaves are listed in the following diagram. Communications Settings: Node address Be sure that the same node address is not Operation for communications used for another Unit on the same network errors Communications Data Allocations: Monitor value settings Operation commands Status Refer to the DeviceNet Operation Manual (Cat. No. W267) for information such as the order for turning ON power to the master and slaves and master l/ © tables. 1-1-5 Data Allocation ESAR/ER-DRT communications data must be allocated for the IN and OUT Areas for remote 1/0 communications. Up to 100 words each can be allocated for the IN and OUT Areas. The data for each word is allocated using the parameters communications write data allocations 1 to 100 and communica- tions read data allocations 1 to 100. Unused words can be specified to reserve space according to data types or to otherwise reduce the number of words. Refer to 4-2 1/0 Allocation on page 4-2 for details on allocation methods. 1-1-6 Remote 1/0 Communications Read/write table data is automatically read and written when communications start. The Communications Write setting must be set to ON to write data from the master to the E5AR/ER-DRT. Data will not be written to the Digital Con- troller if the Communications Write setting is OFF. The following diagram shows communications with the default data allocation parameters.

Note The Communications Write setting is ON by default. Master Output (OUT) Area Input (IN) Area Write Area Write data Output Enable Bit

1-2 Specifications 1-2-1 DeviceNet Communications Specifications Item Specifications Communications protocol Conforms to DeviceNet Communica- Remote 1/0 + Master-slave connections (polling, bit-strobe, COS, or cyclic) tions functions | communications + Conform to DeviceNet specifications. 1/0 allocations + Can allocate any 1/0 data from the Configurator. + Can allocate any data, such parameters specific to the DeviceNet and the Digital Controller variable area. + Up to 2 blocks for the IN Area, up to a total of 100 words (See note 1.) + One block for the OUT Area, up to 100 words (The first word is always allocated to Output Enable Bits.) (See note 2.) Message com- munications - Explicit message communications + CompoWay/F communications commands can be sent (commandés are sent in explicit message format). Connection format Combination of multidrop and T-branch connections (for trunk and drop lines) Baud rate DeviceNet: 500, 250, or 125 kbps, or automatic detection of master baud rate Communications media Special 5-wire cable (2 signal lines, 2 power lines, and 1 shield line) Communications distance Baud rate Network length Drop line length Total drop line length 500 kbps 100 m max. (100 m max.) | 6 m max. 39 m max. 250 kbps 100 m max. (250 m max.) | 6 m max. 78 m max. 125 kbps 100 m max. (500 m max.) | 6 m max. 156 m max. The values in parentheses apply when Thick Cables are used. Communications power supply 11 to 25 VDC Maximum number of nodes that can be connected 64 (includes Configurator when used) Maximum number of slaves that can be connected

Error control CRC error detection Power supply Power supplied from DeviceNet communications connector Note (1) The IN Area can be divided into two blocks only when a CS/CyJ-series De- viceNet Unit is used as the master. (The connection type can also be se- lected.) fa CVM1, CV, or C200HX/HG/HE DeviceNet Master Unit is used as the master, the IN Area must be in 1 block with a maximum 100 words (200 bytes). (Polling connection only.) (2) Ifa CVM1, CV, or C200HX/HG/HE DeviceNet Master Unit used, only up to 32 words can be allocated per node. 1-2-2 DeviceNet General Specifications Item Specifications Supply voltage DeviceNet power supply: 24 VDC (internal circuit) Allowable voltage range DeviceNet power supply: 11 to 25 VDC Current consumption DeviceNet power supply: 50 mA max. (24 VDC) Vibration resistance Vibration: 10 to 55 Hz Acceleration: 20 m/s? Shock resistance 150 m/s? max. 3 times each in 3 axes, 6 directions Dielectric strength 2,000 VAC Insulation resistance 20 MQ min. (at 500 VDC) 1-5

Item Specifications Ambient temperature —10 to 55°C (with no condensation or icing) —10 to 50°C (for 3-year warranty) Ambient humidity 25% to 85% Storage temperature —25 to 65°C (with no condensation or icing) Enclosure rating IP00 (connector) Memory protection EEPROM (100,000 write operations) Weight Connector cover: Approx. 2 g DeviceNet connector: Approx. 10 g 1-6

Introduction Section 2-1 2-1 Introduction Use the procedures in the following sections to prepare the ESAR/ER-DRT Digital Controllers for use. Refer to the following reference pages/sections provided for detailed information on each step. 2-1-1 Setup Procedure Step Item Details Reference 1 Mount the Digital Controller. Mount the Digital Controller to the panel. page 3-4 2 Wire the Digital Controller. Wire the temperature inputs and control outputs to the Digital | page 3-10 Controller terminals. Note Do not turn ON the power supply to the peripheral devices at this time. 3 Turn ON the power to the Digital Con-| Turn ON the power connected to the Digital Controller. page 3-10 roller. Note The Digital Controller will start. 4 Set the DeviceNet node address. Set the DeviceNet node address (0 to 63) for the Digital Con- | page 2-3 troller on the front panel. Set a unique node address for each slave connected to the same master. 5 Turn OFF the power to the Digital Turn OFF the power connected to the Digital Controller. — Controller. 2-1-2 Startup Procedure Prepare the master, DeviceNet communications power supply, and Configura- tor that will be used in the system. Use the Configurator to allocate Digital Controller data in the IN and OUT Areas. Refer to the DeviceNet Operation Manual ( W267) for information on related connection devices. Note Up to 100 words each can be allocated in the IN Area and OUT Area for remote 1/0 communications. To read and write larger amounts of data, use explicit messages. Use explicit message communications also for reading and writing data only when required. Step Item Details Reference 6 Connect the DeviceNet com- | Connect the DeviceNet communications connector. page 3-15 munications connector. Note Do not turn ON the communications power supply at this time. This power supply is also used as the inter- nal circuit power supply for DeviceNet communica- tions. 7 Turn ON the power to the Digi- | Turn ON the power connected to the Digital Controller. page 3-10 tal Controller. Note The Digital Controller will start. 8 Turn ON the DeviceNet com- | Turn ON the communications power supply to DeviceNet. |--- munications power (V+, V). | Note The DeviceNet communications will start. 9 Check the MS/NS indicators Check that the status of the MS and NS indicators is as fol- | page 3-3 lows: MS: Operating normally when lit green. NS: Operating normally when lit green. (DeviceNet online or communications connected.) 2-2

Step Item Details Reference 10 Operate from the Configurator. | Set from the Configurator when changing data allocated in | SECTION 4 the IN and OUT Areas from the default values. Remote 1/0 Com- To split the IN Area used by the E5AR/ER-DRT into two munications areas, select E5AR/ER-DRIT in the masters Edit Device Parameters Window and set the connection in the detailed settings. When the IN Area is split into two areas, for example, oper- ating parameters, such as set points and process values, can be allocated in IN Area 1, and status values can be allo- cated in IN Area 2. For example, IN Area 1 can be allocated in the DM Area and IN Area 2 can be allocated in the CIO Area. Start remote 1/O communica- tions. Enable the master's scan list and change the PLC to RUN |--- Mode. Remote 1/0 communications will start, and the contents of the IN and OUT Areas in the master and E5AR/ER-DRT Digital Controller will be synchronized. Use explicit message commu- nications. Send explicit messages from the master. SECTION 5 Explicit messages can be used to perform control and mon- Explicit Message itoring that cannot be achieved using the IN and OUT Areas | Communications alone, by sending explicit messages to the E5AR/ER-DRT Digital Controller. Observe the following precautions when editing device parameters using the Configurator. + It is recommended that device default values are uploaded before the parameters are edited because the EDS parameter defaults and the device defaults are different. + If “Unit No” (communications unit number) is displayed in the Communi- cations Setting parameter group, set the “Unit No” to the node address. + If “input 2 Type’ is displayed in the Input Initial Setting parameter group for the ESAR-TTIIB-DRT, ESER-IIIB-DRT, ESAR-CIIUIF-DRT, or E5ER-CIUIDIF-DRT, set the “Input 2 Type” to 15. The default value may not be downloaded. + Related settings are not initialized when data is downloaded from the Configurator. Refer to the Appendix in the ESAR/E5ER Digital Controller Users Manual (Cat. No. H124) for information on how to correctly set related data. + The automatic selection range upper limit (DV) can be set from the front panel or it can be set using the automatic selection range upper limit (PV) parameter (PID*AUT(PV)). When using the automatic selection range upper limit (PV) parameter, set the value obtained from the following equation: Automatic selection range upper limit (PV) = Automatic selection range upper limit (DV) + Sensor setting range lower limit 2-1-3 Setting Node Addresses DeviceNet node addresses are set in the communications setting level. Set the node addresses on the front panel of the E5AR/ER-DRT. + The node address will be 0 if an address between 64 and 99 is set.

Functions Supported Only by the ESAR/ER-DRT Section 2-2 ETS RUN level Setting Operation Approximation | setina Fa fus [iso Bank sating level PID sating Adjusiment Austment 2 level lei | me RL an Te Control stops. Input initial Controliniial Controliniial Alarm seting es Communications] saine — 7, cotns | seuna2 lon Eos 7 ee level _ [TE la [E ler [ee Les [a li [es Ke Las ane LT con on DS connai Fr Setting Parameters Press the LEVEL Key for at least 3 s to move from the RUN level to the input initial setting level. Press the LEVEL Key several times to move from the input initial setting level to the communications setting level. The communications unit number (L'-n4) (DeviceNet node address) will be displayed. [Press the UP and DOWN Keys to change the setting. ] The number of words allocated will depend on the E5AR/ER-DRT communi- cations data allocations. The following points are important when setting node addresses or allocating 1/0 memory. + Do not allocate the same words to other slaves. + Make sure the 1/0 area does not exceed the valid range. 2-2 Functions Supported Only by the E5AR/ER-DRT A Configurator is used to make settings for the network power monitor func- tion, accumulated ON (RUN) time monitor function, and control at error func- tion. 2-2-1 Network Power Monitor Function The ESAR/ER-DRT has a network power monitor function that turns ON the Communications Power Voltage Monitor Error Flag in the General Status when the communications power voltage drops below the set monitor value. The monitor value for the network power voltage is set using the Configurator and is found in the General Setting parameter group.

Functions Supported Only by the ESAR/ER-DRT Section 2-2 2-2-2 Accumulated ON (RUN) Time Monitor Function The E5AR/ER-DRT has accumulated ON (RUN) time monitor functions which record internally the total time communications power is supplied or the accu- mulated RUN (control) time. The Unit Maintenance Flag in the General Status Will turn ON if the accumulated time exceeds a set monitor value. The Detection Mode and Detection Time are set using a Configurator and are found in the General Setting parameter group. The ON (RUN) time monitor function can be used as a guide for replacing the ESAR/ER-DRT Digital Controller. Measurement unit: 0.1 h Measurement range: O0 to 429496729.5 h (Stored data: 00000000 to FFFFFFFF hex). Note (1) The ON or RUN time is held even when the power is turned OFF. (2) Both the ON and RUN time monitor functions cannot be used at the same time for one word. (3) The accumulated time will not be measured if communications power is not supplied to the E5AR/ER-DRT. (4) The ESAR/ER-DRT Digital Controller checks the ON/RUN status of the target channel approximately every 0.1 h (6 min.). 2-2-3 Operation for Communications Errors The “Control at Error” specifies the operation to be performed if a DeviceNet communications error occurs. The Control at Error setting is made using the Configurator and is found in the Communications Setting parameter group. Setting range Unit Default Continue — Continue Stop 2-5

Functions Supported Only by the ESAR/ER-DRT Section 2-2 2-6

Part Names and Functions

3-1 3-1-1 Part Names DeviceNet Communications Connector 3-1-2 External Dimensions E5AR E5AR

Part Names and Functions _DeviceNet “connector “MS/NS indicators Top: MS Bottom: NS DeviceNet connector MS/NS Indicators Top: Bottom: NS The DeviceNet communications connector is used to connect the communica- tions cable to the DeviceNet network. The DeviceNet communications power is also supplied through this connector. The connector provided with the Con- troller is the FKC 2.5/5-STF-5.08 AU M (Phoenix Contact). u21.5) fr, 28

Part Names and Functions

3-1-3 MS and NS Indicators The indicators show the status of the Digital Controller and the DeviceNet Normal Indicator Display Network. Indicator Name Color Status Meaning (main errors) MS Module status Green ms / [The Controller is normal. Red SX ms / |Fatalerror + Controller error N + Watchdog timer error (DeviceNet communications) VMS Non-fatal error + Unit error 7 SN leUnit changed - Display Unit error + Non-volatile memory error OFF Ms No power is being supplied. LI . DeviceNet communications power is not being sup- plied. + Power is not being supplied to the Controller. + The Controller is being reset. + Waiting for initialization to start. NS Network status Green X ns / |Online/communications established (normal network CL] status) 7 N ns / | Online/communications not established (waiting for D | connection to be established with the master) 7 N Red ns / [Fatal communications error (The Controller has CL] detected an error that does not allow communications / ù with the network.) + Node address duplication error + Bus OFF error detected NS Non-fatal communications error + Communications timeout 7 N OFF NS Offline or power supply is OFF + Waiting for completion of the master's node address duplication check. + DeviceNet communications power is not being sup- plied. N N / : C2 Et Ca Flashing Æ “cit 7 N 7 N The MS and NS indicators are both lit green when the status of the Controller and the Network are normal. 3-3

needs to be watertight, attach the provided watertight pack- (1) Watertight packing (1) Watertight packing ing. (Model Y92S-P5) If the front of the Controller does not need to be watertight, the watertight packing does not need to be attached.

2. Insert the Controller into the

cutout in the panel.

3. Insert the accompanying fit-

tings into the grooves on the top and bottom of the rear case.

4. Gradually tighten the screws in

the top and bottom fittings, al- ternating between each so that they are balanced. Tighten un- til the ratchet turns without en- gaging. 3-4

Part Names and Functions

Pulling Out the Controller Note Normally there is no need to pull out the Controller, however, it can be pulled out if needed for maintenance. When pulling out the Controller, place a cloth over the screwdriver to prevent scratches and other damage. Remove the DeviceNet connector before drawing out the Controller.

How to Use the Terminals

3-2 How to Use the Terminals Verify the layout of the terminals (A on and 1 on) using the engravings on the top and sides of the case. 3-2-1 Connections E5AR

How to Use the Terminals

_VSIEN fear 7 (SR PRF500 auary outputs Potontometor 0, [f] fransistor output) )}

(outre CLEA 3-2-2 Precautions when Wiring + To avoid the effects of noise, wire the signal wires and power lines sepa- rately. + Use crimp terminals to connect to the terminals. - Tighten screws to the following torques Terminal block screws: 0.40 to 0.56 N:m Connector screws: 0.25 to 0.30 Nm + The crimp terminals must be M3 and either of the following shapes.

@) 5.8 mm or less 3-9

How to Use the Terminals

3-2-3 Wiring Power Supply (Terminals) The inside of the frames around terminal numbers in the wiring diagrams indi- cate the interior of the Controller, and the outside of the frame indicates the exterior. + Connect terminals A1 to A2 as follows: ESAR The input power supply depends on the model. .__ 100 to 240 VAC, or 24 VAC/VDC (no polarity) A BIc)0]E fl 5 UT UT [al a - [5] 5 - - Input voltage E5AR E5ER 3 3 100 to 240 VAC 50/60Hz 22 VA 17 VA E E 24 VAC 50/60Hz 15 VA 11 VA sn 24 VDC (no polarity) 10W 7W ESER LS E

cie Inputs (Terminals) - For Input 1 (IN1), connect terminals K4 to K6 on the E5AR, or Ed to E6 on the E5ER, as shown below according to the input type. E5SAR - For a multi-point input type, connect inputs 2 to 4 (IN2 to IN4) in the same = A En RCE RER ME = way according to the number of input points. [al 5 ESAR El 5 INT _IN2 IN3 IN4 ï ï 2 IN4| IN2[2]

5 IE] ciole To prevent the appearance of error displays due to unused inputs, set the number of enabled channels.

How to Use the Terminals

Control Outputs or Transfer Outputs + On the E5SAR, control output 1 (OUT1) outputs to terminals F5 and F6, and control output 2 (OUT2) outputs to terminals F3 and F4. + On the E5ER, control output 1 (OUT1) outputs to terminals C5 and C6, and control output 2 (OUT2) outputs to terminals C3 and C4. + On a multi-point input type, output takes place from control output 3 (OUT3) and control output 4 (OUTA4). Puise voltage output ù + Puise voltage output D'Or 2 Linear eurrent output + If terminals 5 and 6 are used for pulse voltage output, approximately 2 V are output when the power is turned ON. (Load resistance: 10 kQ or less (Terminals) E5SAR À FICIOTE T T 2 2 E5SAR EI E [al 4 (il 5 5 G w 2 1 © 2 2 ; à à G Éour2lours + Fr BSlourilours E cnol ë G

ESER ESER D E T T E EF [al a & E] 5 G G ï 1 z 2 louraour. E Blourilou & cote for 10 ms) + For linear current output, the power is turned ON. approximately 2 mA are output for 1 ms when + Control outputs that are not used for control can be used for transfer out- put with the “control output/transfer output assignment” setting. + Specifications for each output type are listed in the following table. Output type Specifications Pulse voltage output Output voltage: 12 VDC+15%, -20% (PNP) Maximum load current: 40 mA, with short-cirouit protection circuit Linear current output 0 to 20 mA DC (resolution: approx. 54,000) 4to 20 mA DC (resolution: approx. 43,000) Load: 500 Q or less

• The Position-proportional Models have relay outputs (250 VAC, 1 A). Control output 1 (OUT1) closed output. E5AR is open output and control output 2 (OUT2) is

©@]| our [©] (Closed oupur)

our: {Open output) our2 (Closed output) our {Open output) + Relay output specifications are as follows: 250 VAC, 1 A (including inrush current) 3-11

How to Use the Terminals Section 3-2 Auxiliary Outputs + On the ESAR- ALT, auxiliary outputs 1 to 4 (SUB1 to 4) output to termi- (Terminals) nals B1 to B6. + Relay output specifications are as follows: E5AR E5AR

ESER + On the E5ER-CITUIU auxiliary outputs 1 and 2 (SUB1 and 2) output to ter- minals D3 to D6. E5ER

- Transistor output specifications are as follows: Max. Load voltage: 30 VDC Max. Load current: 50 mA Residual voltage: 1.5 V Leakage current: 0.4 mA

How to Use the Terminals Section 3-2 Potentiometer Inputs + If you want to use a Controller with position-proportional control to monitor (Terminals) the amount of valve opening or perform closed control, connect a potenti- E5AR ometer (PMTR) as shown below. A B C D E 1 1 ESER

B à Ce [5] 5 w G 6 (OI 1 ï z Puref2] 5 4 4 [EI s CN ONCE EE D EN FE s - For information on the potentiometer, see the manual for the valve you ESER are connecting. Terminal number meanings are as follows: ns E O: OPEN, W: WIPE, C: CLOSE 1 1 The input range is 100 Q to 2.5 kKQ (between C and O). [3] 3 [al 4 [5] 5 1 [1] 2 Puel 2]

C D E Event Inputs - To use the event inputs with the E5AR, connect event inputs 1 and 2 (EV1 (Terminals) and EV2) to terminals K1 to K3 as shown below. ESAR — + To use the event inputs with the E5ER, connect event inputs 1 and 2 (EV1 7 T and EV2) to terminals EÂ to E3 as shown below. El 3 E5AR 4 4 =. [5] 5 1 M on 6 6 EX « T ETRE] 2 En EV2 2 Er [2 3 LD 3 CE) Contact inputs … Solid-state inputs

5 G F G H l J K KI ESER y A B 2 2 ESER : ei s El sy [5] 5 2) er FM G G 3 2 1 Evi | <] GContactinputs Solid-state inputs 2 EV2 [2 3 Com] 3

G G C D E - The ratings for event inputs are given in the following table. Contact inputs ON: 1 KQ max., OFF: 100 KQ min. Solid-state inputs ON residual voltage: 1.5 V or less OFF leakage current: 0.1 mA or less 3-13

How to Use the Terminals

DeviceNet Communications Cables Wiring Section 3-3 3-3 DeviceNet Communications Cables Wiring The methods used for preparing DeviceNet communications cables to be connected for DeviceNet communications are explained here. For details on the DeviceNet Network, such as supplying the DeviceNet com- munications power and grounding the DeviceNet Network, refer to the DeviceNet Operation Manual (W267). The wiring methods for Thin Cable are described in this section. 3-3-1 Preparing DeviceNet Communications Cables Use the following procedure to prepare and connect the communications cables to the connectors. 1,2,3...

Remove approximately 30 to 80 mm of the cable covering, being careful not to damage the shield mesh underneath. Do not remove too much cov- ering or a short circuit may result. Approx. 30 to 80 mm (Remove as little as possible.)

Carefully peel back the shield mesh to reveal the signal lines, power lines, and the shield wire. The shield wire is slightly harder to the touch than the mesh. ———— Shield wire Remove the exposed mesh and the aluminum tape from the signal and power lines. Strip the covering from the signal and power lines to the prop- er length for the crimp terminals. Twist together the wires of each of the sig- nal and power lines. Strip to match the crimp terminals. Attach crimp terminals to the lines and then cover any exposed areas with vinyl tape or heat-shrink tubing. Orient the connector properly, then insert each of the signal lines, power supply lines, and the shield wire into the connector holes from the top in the order red, white, shield, blue, black, as shown in the following diagram. The DeviceNet-compatible Controllers are equipped with screwless con- nectors, so the cables do not need to be secured with screws as with pre- vious DeviceNet communications connectors. With the orange lever pushed down, insert each of the lines into the back of the holes. Release the orange lever and genitly tug on each line to check that it is con- nected properly. 3-15

DeviceNet Communications Cables Wiring Section 3-3 Blue (CAN low) — Black (-V) The colors correspond to the signal lines as follows: Color Signal Red Power line, positive voltage (+V) White Communications line, high (CAN high) _— Shield Blue Communications line, low (CAN low) Black Communications cable, negative voltage (-V) + We recommend the following crimp terminals (for Thin Cables) Power Lines: Phoenix Contact Al-series Crimp Terminals AI-0.5-6WH (product code 3200687) Signal Lines: Phoenix Contact Al-series Crimp Terminals AI-0.25-6BU (product code 3201291) Te — TT Crimp terminal Line Insert the line and crimp. The following crimp tool is also available. Phoenix Contact ZA3 Crimp Tool 3-3-2 Attaching the DeviceNet Communications Unit Connector Align the DeviceNet Communications Unit connector with the cable connec- tor, and insert the cable connector fully into the DeviceNet Communications Unit connector. Tighiten the set screws to a torque between 0.25 and 0.8 N:m to secure the connector. E5AR

DeviceNet Communications Cables Wiring Section 3-3 + Using the Connector Provided with the DeviceNet Communications Unit for a Multidrop Connection (Using Thin Cables) + When using Thin Cables for a multidrop connection, two wires of the same color can be inserted into the one hole. Crimp the two lines together that are to be inserted into the same hole us- ing a special crimp terminal, as shown in the following diagram. Crimp Terminal for Two Lines

Crimp terminal Lines We recommend the following crimp terminals and crimp tools. Crimp terminal Crimp tool Phoenix Contact Phoenix Contact Model: AI-TWIN2x0.5-8WH (product code Model: UD6 (product code 1204436) 3200933) 3-17

DeviceNet Communications Cables Wiring Section 3-3 3-3-3 Insulation Blocks As shown in the following diagram, each function block of the ESAR/E5ER- DRT is electrically insulated. The following are functionally insulated from each other: 1) each of the inputs,

2) event inputs, voltage outputs, and current outputs, and 3) communications.

The following are insulated from each other with basic insulation: 1) inputs, event inputs, voltage outputs, current outputs, communications, 2) relay out- put, and 3) transistor outputs. If reinforced insulation is required, the input, event input, voltage output, cur- rent output, and communications terminals must be connected to devices that have no exposed chargeable parts and whose basic insulation is suitable for the applicable maximum voltage of connected parts. Input 1/potentiometer input Input 4 Power supply Event inputs, voltage outputs, current outputs ! Communications — Reinforced insulation Relay output — Basic insulation Transistor output ---- Functional insulation To comply with safety standards, always use an EN/IEC-compliant power supply with reinforced insulation or double insulation for the DeviceNet power supply.

• Remote 1/0 Communications This section describes the input (IN) areas and output (OUT) areas that ESAR-DRT and ESER-DRT Digital Controllers can use for remote 1/0 communications. The methods to allocate data for master communications are also described using sample programming. 41 OvervieW p. 4
• .44seseeeeeeeeeeees 42 4-2 1/0 Allocation 4-2 4-2-1 Allocation Area Size. 4-3 4-2-2 Allocation Parameters p. 4
• -3 4-2-3 Allocation Default Values p. 4
• -4 4-2-4 Allocation Data Size (IN Data Size and OUT Data Size) p. 4
• -5 4-2-5 Allocation Settings p. 4
• -5 ÈË 4-2-6 Input Data : . 4-11 SE 4-2-7 Output Data p. 4
• -11 3 4-2-8 Operation Commands.…. 4-12 É Ë 4-3 Ladder Programming Examples . ee . 4-13 4-3-1 RUN/STOP Sample Programming p. 4
• -13 4-3-2 Change SP Sample Programming -16 p. 4

Overview Section 4-1 4-1 Overview 1/0 memory in the master can be allocated to data from the E5AR/ER-DRT Digital Controller, such as data from the Digital Controllers variable area, merely by specifying what Controller data is to be transferred to where. Data is automatically exchanged between the master and Digital Controller, allowing the Digital Controller to be controlled and monitored from the master without requiring special communications programming. DeviceNet Master CPU Unit Master CPU Unit 1/0 memory | IN Area OUT Area DeviceNet 4 — ESAR/ESER-DRT 7 Digital Controller Allocated data IN Area PVS, etc. OUT Area Operation commandes, etc. 4-2 |/O Allocation The Configurator can be used to select any data from the list of allocation parameters for the Digital Controller and then allocate the data in a user-set destination. Data is selected by specifying the allocation number assigned to the desired parameter. DeviceNet Master CPU Unit / / Ds IN Area DeviceNet Configurator / (el [Es — {| OUT Area rm DeviceNet ___L, Master CPU Unit /O memory ESAR/ESER-DRT a Digital Controller Allocated data IN Area OUT Area 4-2

4-2-1 Allocation Area Size Note Note The size of allocated data in each of the IN and OUT Areas is shown in the following table. 1/0 memory Words Bytes Setting Allocated data | Allocated data size: 2 bytes | size: 4 bytes IN Area © to 100 0 to 200 100 50 OUT Area © to 100 0 to 200 100 50 (1) When the master is a CS/CJ-series DeviceNet Unit, the IN Area can be divided into two areas (IN Area 1 and IN Area 2). Any allocation data from the list of parameters can be allocated in each area. (2) The actual size of the allocated area depends on the size of allocation data selected. (3) The default allocation data size is two bytes. When the allocation data size is two bytes, the monitor and setting data will be displayed in the range FFFF hex to 0000 hex. Data will be fixed at 7FFF hex or 8000 hex if the data exceeds the range that can be displayed. For example, —32769 would be displayed as 8000 hex. The following data sizes are fixed, however. + General status: 2 bytes (fixed) + ESAR/ER-DRT status: 4 bytes (fixed) + ESAR/ER-DRT Output Enable Bits and operation commands: 2 bytes (fixed) Refer to 4-2-6 Input Data on page 4-11 for details on General Status. Refer to 4-2-7 Output Data on page 4-11 for details on Output Enable Bits and opera- tion commands. Allocation data sizes are specified for the IN Area 1/0 allocations and OUT Area [/O allocations. If the allocation data size is 4 bytes, up to 50 allocations can be set. Any allocations set beyond that limit will be invalid. If the total allo- cated area for IN Area 1 and IN Area 2 exceeds the maximum number of words (100 words), the items allocated in IN Area 2 that exceed the maximum number of words will be invalid. 4-2-2 Allocation Parameters Note The parameters that can be allocated are shown below. These parameters can be broadly classified as ESAR/ER-DRT status bits/operation commands, and E5AR/ER-DRT operation data and setting data.

1. ESAR/ER-DRT Status Bits/Operation Commands

The status bits and operation commands for the E5SAR/ER-DRT Digital Controller are shown in the following table. Read Write Item Yes No General status No Yes Operation commands (1) When items that are write-only are allocated in the IN Area, they are al- ways set to 0.

1/0 Allocation Section 4-2 (2) When items that are read-only are allocated in the OUT Area, they are allocated words in memory but operate the same as if they had not been allocated.

2. E5AR/ER-DRT Operation Data and Setting Data

Monitor values and setting data with communications addresses that be- long to the following variable types can be allocated. Duplicate settings are possible and are processed in ascending order. Variable type Co Variable type CO C1 Variable type C1 Ca Operation monitor C6 RUN level C7 Adjustment level C8 Adjustment 2 level C9 Bank setting level CA PID setting level CB Approximation setting level Note lfitems are allocated in the read-only area of the OUT Area, words are allocated in memory but operate as if they had not been allo- cated.

3. Output Enable Bits

Output Enable Bits are allocated in the first word of the OUT Area. When Output Enable Bits are allocated in the IN Area, they are always set to O (OFF). Note If data allocated to the IN or OUT Area is changed, use a software reset or cycle the power to enable the new settings. 4-2-3 Allocation Default Values The default values for 1/0 allocations are listed in the following table. Area Item Allocation number IN Area PV (process value) 3 MV (manipulated variable) monitor (heating) 13 Status (4 bytes) 7 OUT Area | Output Enable Bits 1 SP (set point) 9 Bank 0: Alarm 1 value 81 Bank 0: Alarm 1 upper limit 82 Bank 0: Alarm 1 lower limit 83 Bank 0: Alarm 2 value 84 Bank 0: Alarm 2 upper limit 85 Bank 0: Alarm 2 lower limit 86 Operation commands 1 Note The above monitor values and settings are all for channel 1.

4-2-4 Allocation Data Size (IN Data Size and OUT Data Size) Setting range Unit Default 2byte: 2 bytes Abyte: 4 bytes Bytes 2 bytes 4-2-5 Allocation Settings The 1/0 allocation settings are listed in the following table. Allocated | Allocated Allocation number Item Attribute ton Lou (2-bytes decimal) Channel|Channel|Channel| Channel

1/0 Allocation Section 4-2 Allocated | Allocated Allocation number Item Attribute on OUT (2-bytes decimal) Channel|Channel|Channel| Channel

Yes Yes 37 353 669 985 Input value 1 for input calibration ch Yes Yes 38 354 670 986 Input correction 1 ch Yes Yes 39 355 671 987 Input value 2 for input calibration ch Yes Yes 40 356 672 988 Input correction 2 ch Yes Yes ai 357 673 989 (Reserved) ch Yes No 46 362 678 994 (Reserved) Common Yes Yes 47 363 679 995 Disturbance gain ch Yes Yes 48 364 680 996 Disturbance time constant ch Yes Yes 49 365 681 997 Disturbance rectification constant ch Yes Yes 50 366 682 998 Disturbance judgement width ch Yes Yes 51 367 683 999 First order lag operation 1: Time constant Common Yes Yes 52 368 684 1000 First order lag operation 2: Time constant Common Yes Yes 53 369 685 1001 First order lag operation 3: Time constant Common Yes Yes 54 370 686 1002 First order lag operation 4: Time constant Common Yes Yes 55 371 687 1003 Move average 1: Number of measurement for | Common moving average Yes Yes 56 372 688 1004 Move average 2: Number of measurement for | Common moving average Yes Yes 57 373 689 1005 Move average 3: Number of measurement for | Common moving average Yes Yes 58 374 690 1006 Move average 4: Number of measurement for | Common moving average Yes Yes 59 375 691 1007 Extraction of square root operation 1: Low-cut | Common point Yes Yes 60 376 692 1008 Extraction of square root operation 2: Low-cut | Common point Yes Yes 61 377 693 1009 Extraction of square root operation 3: Low-cut | Common point Yes Yes 62 378 694 1010 Extraction of square root operation 4: Low-cut | Common point Yes Yes 63 379 695 1011 Analog parameter 1 (Control ratio) Common Yes Yes 64 380 696 1012 (Reserved) Common Yes Yes 65 381 697 1013 (Reserved) Common Yes Yes 66 382 698 1014 (Reserved) Common Yes Yes 67 383 699 1015 (Reserved) Common Yes Yes 68 384 700 1016 (Reserved) Common Yes Yes 69 385 701 1017 (Reserved) Common Yes Yes 70 386 702 1018 (Reserved) Common Yes Yes 71 387 703 1019 (Reserved) Common Yes Yes 72 388 704 1020 (Reserved) Common Yes Yes 73 389 705 1021 (Reserved) Common Yes Yes 74 390 706 1022 (Reserved) Common Yes Yes 75 391 707 1023 (Reserved) Common Yes Yes 76 392 708 1024 (Reserved) Common Yes Yes 77 393 709 1025 (Reserved) Common Yes Yes 78 394 710 1026 (Reserved) Common Yes Yes 79 395 711 1027 Bank 0: LSP ch Yes Yes 80 396 712 1028 Bank 0: PID set No. ch 4-6

1/0 Allocation Section 4-2 Allocated | Allocated Allocation number Item Attribute ton Lou (2-bytes decimal) Channel|Channel|Channel| Channel

Yes Yes 81 397 713 1029 Bank 0: Alarm 1 value ch Yes Yes 82 398 714 1030 Bank 0: Alarm 1 upper limit ch Yes Yes 83 399 715 1031 Bank 0: Alarm 1 lower limit ch Yes Yes 84 400 716 1032 Bank 0: Alarm 2 value ch Yes Yes 85 401 717 1033 Bank 0: Alarm 2 upper limit ch Yes Yes 86 402 718 1034 Bank 0: Alarm 2 lower limit ch Yes Yes 87 403 719 1035 Bank 0: Alarm 3 value ch Yes Yes 88 404 720 1036 Bank 0: Alarm 3 upper limit ch Yes Yes 89 405 721 1037 Bank 0: Alarm 3 lower limit ch Yes Yes 90 406 722 1038 Bank 0: Alarm 4 value ch Yes Yes 91 407 723 1039 Bank 0: Alarm 4 upper limit ch Yes Yes 92 408 724 1040 Bank 0: Alarm 4 lower limit ch Yes Yes 93 409 725 1041 Bank 1: LSP ch Yes Yes Same as for bank 1 for 94, 410, 726, and 1042 on. ch Yes Yes 106 422 738 1054 Bank 1: Alarm 4 lower limit ch Yes Yes 107 423 739 1055 Bank 2: LSP ch Yes Yes Same as for bank 1. ch Yes Yes 120 436 752 1068 Bank 2: Alarm 4 lower limit ch Yes Yes 121 437 753 1069 Bank 3: LSP ch Yes Yes Same as for bank 1 for 122, 438, 754, and 1070 on. ch Yes Yes 134 450 766 1082 Bank 3: Alarm 4 lower limit ch Yes Yes 135 451 767 1083 Bank 4: LSP ch Yes Yes Same as for bank 1 for 136, 452, 768, and 1084 on. ch Yes Yes 148 464 780 1096 Bank 4: Alarm 4 lower limit ch Yes Yes 149 465 781 1097 Bank 5: LSP ch Yes Yes Same as for bank 1 for 150, 466, 782, and 1098 on. ch Yes Yes 162 478 794 1110 Bank 5: Alarm 4 lower limit ch Yes Yes 163 479 795 1111 Bank 6: LSP ch Yes Yes Same as for bank 1 for 164, 480, 796, and 1112 on. ch Yes Yes 176 492 808 1124 Bank 6: Alarm 4 lower limit ch Yes Yes 177 493 809 1125 Bank 7: LSP ch Yes Yes Same as for bank 1 for 178, 493, 809, and 1126 on. ch Yes Yes 190 506 822 1138 Bank 7: Alarm 4 lower limit ch Yes Yes 191 507 823 1139 PID 1: Proportional band ch Yes Yes 192 508 824 1140 PID 1: Integral time ch Yes Yes 193 509 825 1141 PID 1: Derivative time ch Yes Yes 194 510 826 1142 PID 1: Integral time (0.01 s unit) ch Yes Yes 195 511 827 1143 PID 1: Derivative time (0.01 s unit) ch Yes Yes 196 512 828 1144 PID 1: MV upper limit ch Yes Yes 197 513 829 1145 PID 1: MV lower limit ch Yes Yes 198 514 830 1146 PID 1: Automatic selection range upper limit |ch Yes Yes 199 515 831 1147 PID 1: Automatic selection range lower limit |ch Yes Yes 200 516 832 1148 PID 2: Proportional band ch Yes Yes Same as for PID 1 for 201, 517, 833, and 1149 on. ch Yes Yes 208 524 840 1156 PID 2: Automatic selection range upper limit |ch Yes Yes 209 525 841 1157 PID 3: Proportional band ch 4-7

1/0 Allocation Section 4-2 Allocated | Allocated Allocation number Item Attribute ton Lou (2-bytes decimal) Channel|Channel|Channel| Channel Yes Yes Same as for PID 1 for 210, 526, 842, and 1158 on. ch Yes Yes 217 533 849 1165 PID 3: Automatic selection range upper limit |ch Yes Yes 218 534 850 1166 PID 4: Proportional band ch Yes Yes Same as for PID 1 for 219, 535, 851, and 1167 on. ch Yes Yes 226 542 858 1174 PID 4: Automatic selection range upper limit |ch Yes Yes 227 543 859 1175 PID 5: Proportional band ch Yes Yes Same as for PID 1 for 228, 544, 860, and 1176 on. ch Yes Yes 235 551 867 1183 PID 5: Automatic selection range upper limit |ch Yes Yes 236 552 868 1184 PID 6: Proportional band ch Yes Yes Same as for PID 1 for 237, 553, 869, and 1185 on. ch Yes Yes 244 560 876 1192 PID 6: Automatic selection range upper limit |ch Yes Yes 245 561 877 1193 PID 7: Proportional band ch Yes Yes Same as for PID 1 for 246, 562, 878, and 1194 on. ch Yes Yes 253 569 885 1201 PID 7: Automatic selection range upper limit |ch Yes Yes 254 570 886 1202 PID 8: Proportional band ch Yes Yes Same as for PID 1 for 255, 571, 887, and 1203 on. ch Yes Yes 262 578 894 1210 PID 8: Automatic selection range upper limit |ch Yes Yes 263 579 895 1211 Straight-line 1 approximation: Input 1 Common Yes Yes 264 580 896 1212 Straight-line 1 approximation: Input 2 Common Yes Yes 265 581 897 1213 Straight-line 1 approximation: Output 1 Common Yes Yes 266 582 898 1214 Straight-line 1 approximation: Output 2 Common Yes Yes 267 583 899 1215 Straight-line 2 approximation: Input 1 Common Yes Yes 268 584 900 1216 Straight-line 2 approximation: Input 2 Common Yes Yes 269 585 901 1217 Straight-line 2 approximation: Output 1 Common Yes Yes 270 586 902 1218 Straight-line 2 approximation: Output 2 Common Yes Yes 271 587 903 1219 (Reserved) Common Yes Yes 272 588 904 1220 (Reserved) Common Yes Yes 273 589 905 1221 (Reserved) Common Yes Yes 274 590 906 1222 (Reserved) Common Yes Yes 275 591 907 1223 (Reserved) Common Yes Yes 276 592 908 1224 (Reserved) Common Yes Yes 277 593 909 1225 (Reserved) Common Yes Yes 278 594 910 1226 (Reserved) Common Yes Yes 279 595 911 1227 Broken-line 1 approximation: Input 1 Common Yes Yes Same pattern as for straight-line 1 approximation for 280, 596, 912, and 1228 on. Common Yes Yes 298 614 930 1246 Broken-line 1 approximation: Input 20 Common Yes Yes 299 615 931 1247 Broken line 1 approximation: Output 1 Common Yes Yes Same pattern as for straight-line 1 approximation for 300, 616, 932, and 1248 on. Common Yes Yes 318 [634 [250 I 1266 [Broken line 1 approximation: Output 20 Common Note Do not use allocation numbers that are reserved.

4-10 Note (a) Position-proportional models have an open output for control out- put (heating side) and a closed output for control output (cooling side). (b) Control output (both heating and cooling sides) is always OFF for linear outputs. (c) Either the control output (heating) or control output (cooling) is OFF for pulse voltage outputs, depending on the control output type.

4-2-6 Input Data The input data specific to Digital Controllers with DeviceNet communications that is not allocated in the variable area of the ESAR/ER-DRT is described here. General Status (Setting: 2) ESAR/ESER-DRT Unit Maintenance Flag 0: Within range (less than monitor value) 1: Outside range (monitor value or higher) Communications Power Voltage Monitor Error Flag 0: Normal (higher than monitor value) 1: Error (monitor value or lower) Not used. + The Communications Power Voltage Monitor Error Flag indicates the sta- tus of the power being supplied through the DeviceNet communications cable. < The Unit Maintenance Flag is set to 1 when the total ON time or run time of the E5SAR/ER-DRT Digital Controller exceeds the monitor value. 4-2-7 Output Data Output Enable Bits Output data specific to DeviceNet that is not allocated to the ESAR/E5ER vari- able area is described here. Output Enable Bits are used when settings are written to the OUT Area, e.g., when SP are set or RUN/STOP is executed using operation commands. The area for Output Enable Bits is always allocated in the first word of the OUT Area. When Output Enable Bits are set to O (OFF), the settings and bits set in the OUT Area are not transmitted and, therefore, nothing is executed. The set- tings can be executed by setting the Output Enable Bits to 1 (ON). Writing is not executed if the Output Enable Bits are not set to 1. Setting Output Enable Bits prevents unintentional setting changes and enables various settings in the OUT Area to be enabled simultaneously. For example, a new value may written to a word for which a SP has already been set. If the Output Enable Bits are set to 1 and then set to O, no SP will be writ- ten even if one is accidentally allocated. (However, care must be taken because writing is enabled if Output Enable Bits are set to 1.) Furthermore, if set values are written for all the channels and the Output Enable Bits are set to 1, the set values will all be enabled at once. Note When Output Enable Bits are set to 1, data allocated to the OUT Area is writ- ten whenever it changes. 4-11

4-2-8 Operation Commands Operation commands are used to RUN and STOP, to move to setting area 1, and other similar operations. As shown in the following table, operation com- mands are executed using a combination of command codes, related infor- mation, and strobes. 4-12 Command Details Related information Memory write area code Upper byte Lower byte 00 Communications write |0 (See note 1.) 0: OFF (Read only) Non-volatile memory 1: ON (Read/write) o1 RUN/STOP 0 to 3, F (See note 2.) | 0: Run; 1: Stop Depends on write mode. 02 Bank selection 0 to 3, F (See note 2.) | O to 7: Bank O to bank 7 Depends on write mode. 03 AT execute 0 to 3, F (See note 2.) | 0: Current PID set number Does not write data. 1 to 8: PID set number 04 Write mode 0 (See note 1.) 0: Backup mode Non-volatile memory 1: RAm write mode 05 RAM data save 0 (See note 1.) 0 Non-volatile memory 06 Software reset 0 (See note 1.) 0 Does not write data. 07 Move to Setting Area 1 | 0 (See note 1.) 0 Does not write data. 08 Move to protect level |0 (See note 1.) 0 Does not write data. 09 Auto/manual 0 to 3, F (See note 2.) | 0: Auto mode Depends on write mode. 1: Manual mode 0A AT cancel 0 to 3, F (See note 2.) | 0: Cancel Does not write data. 0B Initialize setting 0 (See note 1.) 0 Non-volatile memory oc Latch reset 0 to 3, F (See note 2.) |0 Does not write data. 0D SP mode 0 to 3, F (See note 2.) | 0: LSP; 1: RSP Depends on write mode. Note (1) Operations apply to all channels. (2) The channel is specified. 0: Channel 1; 1: Channel 2; 2: Channel 3; 3: Channel 4; F: All channels (3) The write mode defaults are in backup mode. Operation commands are created as shown in the following diagram. 15 7 9 BitNo. Strobe Ste Operation |L 11 n command Command code Upper byte Lower byte Related information Bit 15 is strobe 2 and bit 14 is strobe 1. A logical OR is taken between the two leftmost bits of the command code and bits 15 and 14, and the result is attached as the strobe to the operation command. The command code for ESAR/ER operation commandés is O[1 hex, so when the logical OR is 8[1 hex, the strobe is ON.

Hex With the CS1W-DRM21 and CJ1W-DRM21DeviceNet Units, operation com- mands are made ready for execution by writing to the allocated words (CIO 3209 when the default 1/0 allocation (fixed allocation area 1) is set.) Operation commands are executed only when the Output Enable Bit is set to 1 (ON) and the strobe is ON. The strobe is ON when the following two condi- tions are met:

1. Strobe 2 = 1 and strobe 1 = 0

2. The strobe was cleared after the previous operation command was exe-

cuted. Strobe 1 _ _ nr) 8|11F/|1 Strobe 2 Operation command | =-- Operation command executed. Software resets are executed again even if the strobe has not been cleared. Therefore the Output Enable Bit or the strobe must be cleared after the soft- ware reset command has been sent. 4-3 Ladder Programming Examples 4-3-1 Outline RUN/STOP Sa mple Programming The RUN/STOP ladder programming example here is executed under the fol- lowing conditions. + Using default 1/0 allocations to allocate data in fixed allocation area 1 of a CS/Cy-series DeviceNet Unit (OUT Area = CIO 3200 to CIO 3263, IN Area = CIO 3300 to CIO 3363). This ladder programming example executes RUN and STOP for the E5AR/ ER-DRT. RUN and STOP are executed using operation commandés. Output Enable Bit (CIO 320100) and strobe are used to execute the operation command. 4-13

Ladder Programming Examples Section 4-3 Operation - First, the Output Enable Bit is turned ON. The hexadecimal values are set to D1000 and D1001 at the start of the ladder program. These values pre- pare the channel 1 RUN operation command 0100 hex and the STOP operation command 0101 hex. + RUN is executed for channel 1 when CIO 000000 turns ON. - The contents of D1000 (= 0100 hex) is copied to CIO 3209, where the operation command is allocated. < The strobe is turned ON (strobe 1 = 0 and strobe 2 = 1) and the operation command is executed. The RUN/STOP status is checked and the strobe is disabled for RUN (to prevent unintentional setting changes.) + STOP is executed when CIO 000100 turns ON. The contents of D1000 (= 0100 hex) is copied to CIO 3209, where the operation command is allo- cated. 4-14

000005 }| RESET || sets srobe 2 - 0 ASL (025) |! shift the contents of CIO 0000 o one bit to the lof ‘000006 JL MOV (021) } Copies the contents of D1001 (000020) IT Dioo1 || to CIO 8208. Execution condition 3208 ASL (025) L' snitts the contents of CIO 0001 : one bit to the lof tot 000007 1 RESET || sois strobe (000023 it 320914 ASL (025) | snitts the contents of CIO 0001 : one bit to the lof 000008 1 SET] sois strobe (000028 ETES ASL (025) || Shi the contents of GIO 0001 H—— = one bit to the let es RUVSTOP 000008 = SET _ |) sots stobe (600030 ETS ASL (025) || Shi the contents of GIO 0001 = one bit to the let 000010 j| RESET_ |] got strobe ASL (025) snitts the contents of CIO 0001 : one bit to the lof 000011 [EN ] (000036) eo 4-15

Ladder Programming Examples Section 4-3 4-3-2 Change SP Sample Programming Outline Operation Programming Example The ladder programming example here is for setting and changing SP. The program is for execution under the following conditions. + Using simple 1/0 allocation to allocate data in fixed allocation area 1 of a CS/CJ-series DeviceNet Unit of CS/CyJ-series DeviceNet Unit (OUT Area = CIO 3200 to CIO 3263, IN Area = CIO 3300 to CIO 3363). This ladder program example sets and changes the SP for the E5AR/ER- DRT. Output Enable Bit (CIO 320100) is used to write SP. + The value used as SP is set in D1000 and D1001 at the start of the ladder program. In this example, the SP is set to 100.0, so the hexadecimal number 03E8 is written to D1000. + Once the execution condition (CIO000000) turns ON, the SP is set to CIO 3202. + The Output Enable Bit (CIO320200) is turned ON and the SP is written. + A timer is used to turn OFF the Output Enable Bit after 0.1 s (see note). Note: If using this kind of ladder programming, do not use the timer method shown here. Instead, allocate the SP, check that the setting has changed, and then turn OFF the Output Enable Bit using the following steps.

1. Use a Configurator or other Programming Device to allocate the SP to the

2. Check that the SP has been written and then turn OFF the Output Enable

000003 mn ASL (025) Shits the contents of CIO 0000 (000008 il 0 one bit to the lof 000004 1! RESET Coana 1} Turms OFF Ouiput Enable Bi. ASL (025) Shits the contents of CIO 0000 o one bit to the lof 000005 END (O0!) (Oo0013

Overview of Explicit Message Communications Section 5-1 5-1 5-1-1 Overview of Explicit Message Communications Explicit Message Communications Explicit message communications is a communications protocol for sending commands from the master as explicit messages, and receiving explicit mes- sages as responses from the nodes that receive the commandés. Explicit messages can be sent from the master to the Digital Controller to read and write the ESAR/E5ER Digital Controller variable area, send operation commands, and read and write various other DeviceNet functions supported by the Digital Controller. Explicit message communications can be used to send and receive data that is not allocated in the IN and OUT Areas due to word size restrictions, and data that does not require the frequent refreshing used by the IN Area and OUT Area. Use either of the following two methods depending on the application. Reading/Writing E5AR/E5ER Variable Area Data and Sending Operation Commands Send CompoWay/F communications commands to E5AR/E5ER Digital Con- trollers by embedding them in explicit messages. Reading/Writing E5AR/E5ER-DRT Maintenance Information Send explicit messages specific to the DeviceNet-compatible Digital Control- ler. DeviceNet Master / 4 CPU Unit instruction CompoWay/F communications | Explicit message sent to command sent to ESAR/ESER DeviceNet-compatible Digital Controller (embedded in Digital Controller explicit message) F- ESAR/E5ER-DRT Digital Controller 5-1-2 Explicit Message Types The explicit messages sent to the Digital Controller can be divided into two types: messages in which CompoWay/F commands are embedded and mes- sages specific to DeviceNet-compatible Digital Controllers. Sending CompoWay/F Commands to the E5AR/E5ER-DRT (Embedded in Explicit Messages) The master can send CompoWay/F communications commandés to the E5AR/ E5ER Digital Controller by sending them as explicit message data. When DeviceNet-compatible Digital Controllers are used, the explicit mes- sages are automatically converted to CompoWay/F communications com- mands and sent to the E5SAR/E5ER-DRT Digital Controller. The responses from the Digital Controller are converted into explicit messages and returned to the master. CompoWay/F commandés are used to read from and write to the ESAR/ES5ER variable area and to execute operation commands. CompoWay/F commands consist of binary commands and ASCII commandés.

Overview of Explicit Message Communications Section 5-1 Sending Explicit Messages Specific to DeviceNet-compatible Di HE CompoWay/F Binary Commands CompoWay/F binary commands are CompoWay/F communications com- mands expressed in hexadecimal, and are easy to execute from ladder pro- grams. CompoWay/F communications commands that include ASCII data, however, cannot be sent or received. Therefore, Read Controller Attribute (05

03) and broadcasting (unit number = XX) cannot be used.

HE CompoWay/F ASCII Commands CompoWay/F ASCII commands are CompoWay/F communications com- mands expressed in ASCII, so numerical values must be converted to ASCII when executing these commands from a ladder program. CompoWay/F binary commands cannot be used. Broadcasting (unit number = XX) cannot be used, but all other CompoWay/F communications commands can be sent and received, including Read Controller Attribute (05 03), which cannot be used with CompoWay/F binary commands. tal Controllers The master can send explicit messages to a DeviceNet-compatible Digital Controller to control various operations supported only by DeviceNet-compat- ible Digital Controllers and to read DeviceNet-specific settings and status information. These explicit messages are used to read and write maintenance information specific to DeviceNet-compatible Digital Controllers. 5-1-3 Explicit Messages Basic Format Command Block Response Block The basic formats of explicit message commands and responses are described here. Destination ï node Senee Class ID | Instance ID | Attribute ID Data address Destination Node Address This parameter specifies the node address of the Controller to which the explicit messages (commands) will be sent in single-byte (2-digit) hexadeci- mal. Service Code, Class ID, Instance ID, Attribute ID These parameters specify the command type, processing target, and pro- cessing details. The Attribute ID does not need to be specified for some commands. Data Specifies the details of the commandés, set values, etc. The data section is not required for read commands. The following format is used when a normal response is returned for the sent explicit message. No. of bytes Source node received address Service code Data

Sending Compo Way/F Commands to the Digital Controller Section 5-2 The following format is used when an error response is returned for the sent explicit message. cnee Source node | Service code Error code 0004 hex, fixed | 24dress (2 bytes, fixed) Number of Bytes Received The number of data bytes received from the source node address is returned as a hexadecimal. When an error response is returned for the explicit mes- sage, the contents is always 0004 hex. Source Node Address The node address of the master that sent the explicit message is returned as a hexadecimal. Service Code For normal responses, the service code specified in the command turns with the most significant bit (bit 07) turned ON is returned. (For example, when the service code of the command is OE hex, the service code of the response will be 8E hex.) When an error response is returned for the explicit message, the service code is always 94 hex. Data Read data is included in the response only when a read command is exe- cuted. There is no data for commands that do not read data. Error Code The following table shows the error codes for explicit messages. Error Error name Cause code 08FF | Service not supported |The service code is incorrect. 09FF | Invalid Attribute value |The Attribute Value is not supported. 16FF | Object does not exist |The Instance ID is not supported. 15FF | Too much data The data string is too long. 13FF | Not enough data The data string is too short. 14FF | Attribute not supported | The Attribute ID is not supported. OCFF | Object state conflict The command cannot be executed. OEFF |Attribute not settable | A write service code was sent for a read-only Attribute ID. 20** Invalid Parameter There is an error in the specified parameter. 5-2 Sending CompoWay/F Commands to the Digital Controller The master can send CompoWay/F command frames to the E5AR/E5ER- DRT Digital Controller by embedding them in explicit message commandés, and receive CompoWay/F response frames that are embedded in explicit messages responses. The following services, however, cannot be used. + Monitor value/set data composite registration read + Monitor value/set data composite read registration (write) + Monitor value/set data composite read registration confirmation (read)

Sending Compo Way/F Commands to the Digital Controller Section 5-2 5-2-1 CompoWay/F Binary Commands CompoWay/F binary commands use hexadecimal values for the CompoWay/ F frames, and not ASCII. Therefore, the data volume is about half of Compo- Way/F ASCII commands. The following restrictions apply. + Read Controller Attribute (05 03), which includes ASCII in the Compo- Way/F frame, cannot be used. The following command and response formats are used when executing CompoWay/F binary commands from an OMRON Master. Command Block ad Service dess Code ClassiD instance ID Data (CompoWay/F command frame data) T T 6 nex Éone*] 0086 ex ixed | 0001 hex fixed L L ‘bye bye Z2byes 2byes… Speciledinbinary Unit IS Sub (ee Sub See. Stress SD FINS-mini command text oo nex |00 hex fixed |ixed Note Specify the same value as the destination node address. Broadcasting cannot be specified. Response Block Normal Response No cfreceneg SE lo. of receive Service bytes Paduss Code Dala (CompoWay/F response frame data)

Zbyes bye 1DYe — Respondein binary (nexadecimal Uni Su. End No. address code FINS-mini response text [00 hex |00 hex fixed [fixed 5-2-2 CompoWay/F ASCII Commands When CompoWay/F ASCII commands are used, the CompoWay/F frames are expressed in ASCII (each digit in a specified numerical value is also con- verted to ASCII, so 52 is specified as ASCII 3532). The following command and response formats are used when the commands are executed from an OMRON Master Unit.

Explicit Messages Specific to DeviceNet-compatible Digital Controllers Section 5-3 Command Block Destina- tion node Service address Code ClassID Instance ID Data (CompoWay/F command frame data) T T 87 hex | 0086 nex fixed | 0001 hex fixed fixed | l Tbye tbe Z2byes Z2byes… Specliedin ASCI Ê Uni No {See noie) Subradcress SI FINS-mini command text T T [0]= 30 gooj- 3030 || hex fixed hex Note Specify the same value as the destination node address. Broadcasting cannot be specified. Response Block Normal Response No. of Source io. of receive node … Service bytes address Code Dala (CompoWay/F response frame data) 87 Hex fixed

Zbyes ibye 1bye; Retumsin ASCI Unit No. Sub-address End code FINS-mini response text T T

3030 Hex L fed L 5-3 Explicit Messages Specific to DeviceNet-compatible Digital Controllers The following list shows explicit messages that can be sent to E5SAR/E5ER- DRT Digital Controllers. These messages are used to read and write mainte- nance information (such as Unit conduction time or total RUN time) for the DeviceNet-compatible Digital Controller. For details on sending explicit messages from an OMRON Master PLC, refer to the DeviceNet Master Unit operation manual. Note The number of digits used for the Class ID, Instance ID, and Aïttribute ID depends on the master used. When sending parameters from an OMRON Master Unit, the values are expressed as follows: Class ID: 4-digit (2-byte) hexadecimal Instance ID: 4-digit (2-byte) hexadecimal Attribute ID: 2-digit (1-byte) hexadecimal

5-3-1 Reading General Status Explicit Read/ Function Command Response message | write Service | Class | Instance | Attribute | Data code ID size General Read Reads the DeviceNet-com- | OE hex 95 hex | 01 hex 65 hex — 1 byte Status patible Controller's general Read status bits (8 bits). (Refer to page 4-11). 5-3-2 Writing Maintenance Mode Data Explicit Read/ Function Command Response message | write Service | Class [Instance] Attribute | Data code ID ID ID size Mainte- Save Records the maintenance | 16 hex 95hex |Othex |75hex — — nance counter (PV of total ON/ Counter RUN time for all Digital Save Controllers) in memory. 5-3-3 Setting and Monitoring the Digital Controller Channels Explicit | Read/ Function Command Response message | write Service | Class | Instance | Attribute | Data size code ID ID Digital Con- | Read | Reads the monitor 0E hex 7Ahex |01to04 |65 hex 1 byte troller mode for maintenance hex 00 hex: Unit Channel information of the Digi- conduction Mainte- tal Controller channel time mode nance Infor- (see note 1) specified 01 hex: Total mation by the Instance ID (1 to RUN time Monitor 4). mode Mode Write | Writes the monitor 10hex |7Ahex |01to04 |65hex 1 byte mode for maintenance hex 00 hex: Unit information of the Digi- conduction tal Controller channel time mode (see note 1) specified 01 hex: by the Instance ID (1 to Total RUN 4). time mode Set Value |Read |Reads the set value 0E hex 7Ahex |01to04 |68 hex 4 bytes for Unit (monitor value) for the hex 00000000 to Conduction Unit conduction time or FFFFFFFF Time or total RUN time (unit: s) hex (0 to Total RUN of the Digital Controller 4294967295) Time channel (see note 1) specified by the Instance ID (1 to 4). Write | Writes the set value 10 hex 7Ahex |01to04 |68 hex 4 bytes (monitor value) for the hex 00000000 Unit conduction time or to total RUN time (unit: s) FFFFFFFF of the Digital Controller hex (0 to channel (see note 1) 429496729 specified by the 5) Instance ID (1 to 4). 5-7

Explicit Messages Specific to DeviceNet-compatible Digital Controllers Section 5-3 Explicit | Read/ Function Command Response message | write Service | Class | Instance | Attribute | Data size code ID ID ID Unit Con- |Read |Readsthe PV forthe |O0E hex 7Ahex |01to04 |66 hex 4 bytes duction Unit conduction time or hex 00000000 to Time or total RUN time (unit: s) FFFFFFFF Total RUN of the Digital Controller hex (0 to Time Read channel (see note 1) 4294967295) specified by the Instance ID (1 to 4). Monitor Read |Reads the monitor sta- | OE hex 7Ahex |01to04 |67 hex 1 byte Status of tus for the Unit conduc- hex 00 hex: Within Unit Con- tion time or total RUN range duction time (unit: s) of the Dig- 01 hex: Out of Time or ital Controller channel range (moni- Total RUN (see note 1) specified tor value Time Read by the Instance ID (1 to exceeded) 4). Note The following table shows the relationship between the Instance IDs (01 to

04) and the Digital Controller channels (1 to 4).

Instance ID Channel Instance ID Channel 1 (01 hex) Channel 1 2 (02 hex) Channel 2 03 (03 hex) Channel 3 4 (04 hex) Channel 4 5-8

Communications Performance This section provides information on the time required for a complete communications cycle, for an output response to be made to an input, to Start the system, and to send messages. 6-1 6-2 Remote 1/0 Communications Performance .......................... 6-1-1 6-1-2 6-1-3 1/0 Response Time Communications Cycle time and Refresh Processing Time. Networks with More Than One Master ...................... Message Communications Performance. 6-2-1 Message Communications Time.

6-6 6-6 Communications. Performance 6-1

Remote 1/0 Communications Performance Section 6-1 6-1 Remote 1/0 Communications Performance Note The performance of remote 1/0 communications between an OMRON Master Unit and OMRON Slave is described in this section. Use this information for reference with precise timing is required. The following conditions are assumed in the calculations provided in this sec- tion. + The Master Unit is operating with the scan list enabled. - All required slaves are participating in communications. + No error has occurred in the Master Unit. + No messages are being sent on the network by Configurators or other devices from other manufacturers. The calculations given in the section may not be accurate if a master from another manufacturer is used or if slaves from other manufacturers are used on the same network. 6-1-1 1/0 Response Time CS/CJ-series, C200HX/HG/HE (-Z), and C200HS PLCs Note The 1/0 response time is the time required from when the master is notified of an input on an input slave until an output is made on an output slave (includ- ing ladder diagram processing in the PLC). um 1/0 Response Time The minimum 1/0 response time occurs when the slave 1/0 refresh is per- formed immediately after the input is received by the master and the output is sent to the output slave at the beginning of the next 1/O refresh. PLC Program execution Master Unit mn Input Output Tarn CPLGTRP) Tarour TOUT Tin: ON/OFF delay time of the input slave (0 used as minimum value) Tour: ON/OFF delay time of the output slave (0 used as minimum value) TRTIN: Communications time for one slave for input slaves TarourT: Communications time for one slave for output slaves TpLc: Cycle time of PLC TRE: DeviceNet Unit refresh time at PLC Refer to the operation manuals for the slaves for the input slave ON/OFF delay times and the output slave ON/OFF delay times. Refer to 6-1-2 Com- munications Cycle time and Refresh Processing Time and to the operation manual for the PLC for the PLC cycle time.

Remote 1/0 Communications Performance Section 6-1 The minimum 1/0 refresh time can be calculated as follows: Tin = Tin + Tarn + (pic — TRE) + Tarour + Tour Maximum [/0 Response Time The maximum 1/0 response time occurs under the conditions shown in the following diagram. Program Program Program PLe execution execution ‘execution Master Unit EG 5 Input \ Input TN Tam Tec Tec Ta Trm Tour Tin: ON/OFF delay time of the input slave (0 used as minimum value) Tour: ON/OFF delay time of the output slave (0 used as minimum value) TM: Communications time for entire network TpLc: Cycle time of PLC TRF: DeviceNet Unit refresh time at PLC Note Refer to the operation manuals for the slaves for the input slave ON/OFF delay times and the output slave ON/OFF delay times. Refer to 6-1-2 Com- munications Cycle time and Refresh Processing Time and to the operation manual for the PLC for the PLC cycle time. The maximum 1/0 refresh time can be calculated as follows: Tax = Tin + 2 X Tam + 2 X Tpic + TRF + TOUT 6-1-2 Communications Cycle time and Refresh Processing Time This section describes the communications cycle time and refresh processing time, which are required to calculate various processing times for DeviceNet. Communications Cycle Time The communications cycle time is the time from the completion of a slave's 1/0 communications processing until 1/0 communications with the same slave are processed again. The communications cycle time is the maximum com- munications cycle time Tin + Tour: The equations used to calculate the communications cycle time are described here. Communications Cycle Time Equations Total communications cycle time = IN communications cycle time + OUT com- munications cycle time. MIN Communications Cycle Time IN communications cycle time = (39 ms + 8 ms x number of allocated data) + (6 ms x total allocated words in IN Areas 1 and 2)

Remote 1/0 Communications Performance Section 6-1 HE OUT Commu ns Cycle Time Refresh Processing Time CS/CJ-series. Note C200HX/HG/HE (-Z), and C200HS PLCs OUT communications cycle time = (29 ms + 27 ms x number of allocated data) + (7 ms x total allocated words in OUT Areas 1 and 2) The refresh processing time is the time required for the CPU Unit of the PLC and the DeviceNet Master Unit to pass 1/O information back and forth. The cycle time of the PLC is affected as described below when a DeviceNet Unit is mounted. Refer to the operation manuals for the PLCSs for details on the refresh pro- cessing time and the PLC's cycle time. The following times for 1/O refreshing are added to the cycle time of the PLC when a Master Unit is mounted. Item Processing time 1/0 refresh | DeviceNet Unit 1/0 Refresh Processing CS/CJ-series or C200HX/HG/HE (-Z) PLCS

1.72 + 0.022 x number of allocated words (see note) ms

2.27 + 0.077 x number of allocated words (see note) ms

Note The number of allocated words is the total number of 1/0 area words allocated to all of the slaves. Any unused areas within the al- locations must be included. For example, if only node address 1 with a 1-word input and node address 5 with a 1-word input are connected, the total number of words would be 5. When message communications are performed, the number of words required for message communications would have to be added to the above to- tal number of words during the cycles in which message communi- cations are processed. 6-1-3 Networks with More Than One Master The communications cycle time, Tam, when there is more than one master in the same network is described in this section. Here, a network with two mas- ters is used as an example. First, separate the network into two groups, slaves that perform remote 1/0 communications with master À and those that perform remote 1/0 communi- cations with master B. Group À Group B Master À Master B Slave a Slave b Slave c Slave d Slave e Slave Slaves performing remote 1/0 Slaves performing remote 1/0 communications with master À communications with master B Note Although for convenience, the slave are positioned in groups with the mas- ters, in the actual network, the physical positions of the slaves will not neces- sarily be related to the master with which they communicate. Next, calculate the communications cycle time for each group referring to 6-1- 2 Communications Cycle time and Refresh Processing Time.

Remote 1/0 Communications Performance Section 6-1 System Startup Time Sample Program Note Group A Group B Master À Master B Slave a Slave b Slave c Slave d Slave e Slave t Group À communications cycle time: Try. Group À communications cycle time: Ta.8 The communications cycle time for the overall network when there are two masters will be as follows: TR = TRu-A + Tam.8 Although this example uses a network with only two masters, the same method can be used for any number of masters. Simply divide the network up according to remote l/O communications groups and then add all of the com- munications cycle times for the individual groups to calculate the communica- tions cycle time for the overall network. This section describes the system startup time for a Network, assuming that the scan list is enabled and that remote 1/0 communications are set to start automatically at startup. The system startup time is the delay from the time that the Master Unit is turned ON or restarted until the time remote 1/0 com- munications begin. The system startup time when the Master Unit is set to start Up immediately after power supplies of all the slaves are turned ON is different from when the Master Unit is restarted while communications are in progress. The startup times are shown in the following table. Condition Slave's indicator status System startup time The master is started NS indicator is OFF or flashing green. |6s immediately after slave startup. The master only is NS indicator is flashing red while the |8s restarted. master is OFF. The slaves only are —— 105 restarted. The times described above are required for the DeviceNet system to start. The sample program in this section shows how to use the Master Slave Sta- tus to skip slave 1/0 processing until remote 1/0 communications have started. Refer to the operation manual for the Master Unit for information on the Mas- ter Status Area. The following conditions apply to this sample program. PLC: CS1 Series Master Unit's unit number: 00

Message Communications Performance Section 6-2

15 14 (009 | W Ç JMP#0001 ) /O Data Commuications Slave VO Flag Error/Error processing Communications Stop Flag (00) N ( JME#oo0t ) 6-2 Message Communications Performance 6-2-1 Message Communications Time Only Message Communications (Remote 1/0 Communications Stopped) Note Note The message communications time is the time required from when the Master Unit starts to send a message on the network until the entire message has been sent when a message is being sent from one node to another. The mes- sage will consist of data for a SEND or RECV instruction and a FINS com- mand for an IOWR or CMND instruction. If another message is sent before the message communications time elapses or is a message is received from another node before the message communi- cations time elapses, the response message being sent or the message being received may be corrupted. When performing message communications it is thus necessary to allow the message communications time to elapse before performing message communications again using SEND, RECV, CMND, or IOWR instructions and to allow the message communications time to elapse between sending messages to the same node. If a send or receive message is corrupted, a record will be stored in the error log in the Master Unit. Use a FINS command to read the error record or use the Configurator to monitor the error log. The message communications time can be estimated using the following equation: Message communications time = Communications cycle time x {(number of message bytes + 15)+6+1} The number of message bytes in the number of bytes after the FINS com- mand code. The communications cycle time will depend on whether remote 1/0 communications is being used and can be calculated as described next. Communications cycle time = 2 (see note) + 0.11 x TB + 0.6 ms TB depends on the baud range as follows: 500 KB/s: 2, 250 KB/s: 4, 125 KB/s: 8 The communications cycle time when remote 1/0 communications are stopped is 2 ms.

Message Communications Performance Section 6-2 Message Communications and Remote 1/0 Communications Note Communications cycle time = (communications cycle time for only remote 1/0 communications + 0.11 x TB + 0.6 ms TB depends on the baud range as follows: 500 KB/s: 2, 250 KB/s: 4, 125 KB/s: 8 The above calculations for the message communications times are only for use as guidelines. They do not produce maximum values. The message com- munications time depends on the frequency of messages, the load on the remote node, the communications cycle time, etc. If network traffic is concen- trated on one Master Unit, long times will be required that those produced by the above calculations. Be sure to consider this when designing the system.

Message Communications Performance Section 6-2 6-8

• Troubleshooting and Maintenance This section describes error processing, periodic maintenance operations, and troubleshooting procedures needed to keep the DeviceNet Network operating properly. Details on resetting replaced Controllers are also provided. Read through the error processing procedures in both this manual and the operation manual for the DeviceNet master being used before operation so that operating errors can be identified and corrected more quickly. 7-1 Indicators and Error Processing p. 7
• -2 7-2 Maintenance p. 7
• -3 7-2-1 Cleaning p. 7
• -3 7-2-2 Inspection 7-3 7-2-3 Replacing Controllers -4 Troubleshooting and Maintenance p. 7

Indicators and Error Processing Section 7-1 7-1 _Indicators and Error Processing The following table lists the indicator status when errors occur, the probable causes and processing. 7-2 Indicator status Probable cause Remedy MS: OFF NS: OFF The power is not being supplied to the Control- ler. Supply communications power from the DeviceNet connector. The power voltage is not within the permitted range. Use a power supply voltage within the permitted range. The Controller is faulty. Replace the Controller. MS: Flashing red NS: No change A checksum error has occurred in the parame- ters registered in EEPROM. A EEPROM hardware error has occurred. Repairs are required if this error per- sists even if the parameters are reset. Contact your nearest OMRON repre- sentative. NS: Flashing green DeviceNet communica- tions. MS: ON red The Digital Controller is | Repairs are required. Contact your NS: OFF faulty nearest OMRON representative. MS: ON green Waiting to connect to Check the following items and restart the Controller. + Are lengths of cables (trunk and branch lines) correct? + Are cables short-circuited, broken, or loose? + Are cables wired correctly? + Is terminating resistance connected to both ends of the trunk line only? + Is noise interference excessive? + Is the power to the master ON? The Digital Controller is faulty. Repairs are required. Contact your nearest OMRON representative. NS: Flashing red out has occurred. MS: ON green The DeviceNet is in Bus | Check the following items and restart NS: ON red OFF status. the Controller. + Are lengths of cables (trunk and branch lines) correct? + Are cables short-circuited, broken, or loose? + Is terminating resistance connected to both ends of the trunk line only? + Is noise interference excessive? Node addresses dupli- | Reset node addresses correctly. cated. The Controller is faulty. | Repairs are required. Contact your nearest OMRON representative. MS: ON green A communications time- | Check the following items and restart the Controller. + Are lengths of cables (trunk and branch lines) correct? + Are cables short-circuited, broken, or loose? + Is terminating resistance connected to both ends of the trunk line only? + Is noise interference excessive? The Digital Controller is faulty. Repairs are required. Contact your nearest OMRON representative.

7-2 Maintenance 7-2-1 Cleaning Note 7-2-2 Inspection Inspection Equipment Equipment Required for Regular Inspection Other Equipment that May Be Required Inspection Procedure This section describes the routine cleaning and inspection recommended as regular maintenance. Handling methods when replacing Controllers are also explained here. Clean the Controllers regularly as described below in order to keep the Net- work in its optimal operating condition. + Wipe the Controller with a dry, soft cloth for regular cleaning. + When dust or dirt cannot be removed with a dry cloth, dampen the cloth With a neutral cleanser (2%), wring out the cloth, and wipe the Controller. + Smudges may remain on the Controller from gum, vinyl, or tape that was left on for a long time. Remove these smudges when cleaning. Never use volatile solvents, such as paint thinner or benzene, or chemical wipes to clean the Controller. These substances may damage the surface of the Controller. Inspect the system periodically to keep it in its optimal operating condition. In general, inspect the system once every 6 to 12 months, but inspect more frequenily if the system is used in high-temperature, humid, or dusty condi- tions. Prepare the following equipment before inspecting the system. A flat-blade and a Phillips screwdriver, a screwdriver for connecting communi- cations connectors, a tester (or a digital voltmeter), industrial alcohol, and a clean cloth are required for routine inspection. A synchroscope, oscilloscope, thermometer, or hygrometer may be required. Check the items in the following table and correct any condition that is below standard by adjusting the Controller or improving the environmental condi- tions. Inspection item Details Standard Equipment Environmental conditions Are ambient and cabinet temperatures —10 to +55°C Thermometer correct? Are ambient and cabinet humidity cor- 25% to 85% Hygrometer rect? Has dust or dirt accumulated? No dust or dirt Visual inspection Installation conditions Are the connectors of the communica- No looseness Philips screwdriver tions cables fully inserted? Are the external wiring screws tight? No looseness Philips screwdriver Are the connecting cables undamaged? | No external damage | Visual inspection

7-2-3 Replacing Controllers Precautions Note The Network consists of the DeviceNet Master Unit and Slave Units. The entire network is affected when a Unit is faulty, so a faulty Unit must be repaired or replaced quickly. We recommend having spare Units available to restore Network operation as quickly as possible. Observe the following precautions when replacing a faulty Controller. + After replacement make sure that there are no errors with the new Con- troller. + When a Controller is being returned for repair, attach a sheet of paper detailing the problem and return the Controller to your OMRON dealer. - If there is a faulty contact, try wiping the contact with a clean, lint-free cloth dampened with alcohol. Before replacing a Controller, always stop Network communications and turn OFF the power to all the nodes in the Network.

Appendix A Detailed DeviceNet Specifications Data Size and Connection Types If the connection type can be set when another company's configurator is being used, select a connection sup- ported by the DeviceNet Communications Unit. The following table shows the connection types and data sizes for OMRON DeviceNet Communications Units. Model Supported connections Data size (bytes) Poll Bit strobe Change of Cyclic IN OUT state (COS) ESAR/ER-DRT Yes Yes Yes Yes 0 to 200 0 to 200 (See note.) |(See note.) Note The size of the IN/OUT Areas depends on the setting. DeviceNet 1/0 communications support the following types of connections. Connection type Details Remarks Poll Used to exchange data between the master and individual slaves by sending and receiving com- mands and responses. (Output data is allocated for commands and input data is allocated for responses). Bit strobe Used to broadcast commands from the master and receive input responses from multiple slaves. By using one command only, the communica- tions cycle time is short, but bit strobe connec- tions can be used only with slaves with 8 or less input points. Change of state (COS) Normally, input and output data are sent by mas- ter and slaves at regular cycles, but with a COS connection, data is sent to the master or slave when the master or slave data changes. By setting a long cycle interval, the Network will not be loaded with communications for minor data changes, thereby improving the overall effi- ciency of the Network. Cyclic Masters and slaves send output or input data at regular cycles. A-1

Detailed DeviceNet Specifications Appendix A Device Profiles The following device profiles contain more detailed DeviceNet specifications for DeviceNet communications if more information needs to be registered in the scan list. General data Compatible DeviceNet Specifications Volume | - Release 2.0 Volume 11 - Release 2.0 Vendor name OMRON Corporation Vendor ID = 47 Device profile name Slaves: Generic Device Manufacturer catalog number H124 Manufacturer revision 1.01 Physical conformance Network current consumption 50 mA max. data Connector type Open plug Physical layer insulation No Supported indicators Module, Network MAC ID setting Software switch Default MAC ID

Baud rate setting Automatic recognition Supported baud rates 125 kbps, 250 kbps, and 500 kbps Communications data Predefined Master/Slave connection set Group 2 only server Dynamic connection support (UCMM)

B-4 Produced Connection Paths IN Area 1: 20_04_24_64_30_03 IN Area 2: 20_04_24_65_30_03

2. Consumed Connection Paths

OUT Area: 20_04_24_6E_30_03

Appendix C DeviceNet Connection Hardware DeviceNet Communications Cables Model Specifications Manufacturer DCA1-5C10 Thin Cable: 5 wires, 100 m OMRON DVN24-10G Thin Cable: 5 wires, 10 m Nihon Wire & Cable (See note 1.) DVN24-30G Thin Cable: 5 wires, 30 m Nihon Wire & Cable (See note 1.) DVN24-50G Thin Cable: 5 wires, 50 m Nihon Wire & Cable (See note 1.) DVN24-100G Thin Cable: 5 wires, 100 m Nihon Wire & Cable (See note 1.) DVN24-300G Thin Cable: 5 wires, 300 m Nihon Wire & Cable (See note 1.) DVN24-500G Thin Cable: 5 wires, 500 m Nihon Wire & Cable (See note 1.) 1485C-P1-C150 Thin Cable: 5 wires, 150 m Allen-Bradiey (See note 2.) female socket on micro-size end) Cable length: 1 m,2m,5m, and 10m DCAI-5CNCILIW1 Cable with shielded micro-size (M12) connectors on both ends (female OMRON socket and male plug) Cable length: 0.5 m, 1 m,2m, 3m, 5m, and 10m DCA1-5CNCIIF1 Cable with shielded micro-size (M12) connector (female socket) on one end | OMRON Cable length: 0.5 m, 1 m,2m,3m,5m, and 10m DCA1-5CNCIIH1 Cable with shielded micro-size (M12) connector (male plug) on one end OMRON Cable length: 0.5 m, 1 m,2m, 3m, 5 m, and 10m DCAI-5SCNCICIW5 Cable with shielded connector on both ends (male plug on mini-size end, OMRON Note 1. The product specifications for these cables are identical to the OMRON cable specifications.

2. The cables made by Allen-Bradley are stiffer than the cables made by OMRON and Nihon Wire &

Cable Company Lid., so do not bend the Allen-Bradiey cables as much as the others. Other DeviceNet communications cables are available from the following manufacturers. For details, refer to the product catalogs on the ODVA web site (http:/{www.odva.astem.or.jp/) or contact the manufacturer directly. DeviceNet Connector Model Specifications Manufacturer Screwless type, includes connector set screws FCK2.5/5-STF-5.08AU | For node connection PHOENIX CONTACT

DeviceNet Connection Hardware Appendix C Crimp Terminals for DeviceNet Communications Cables Model Crimper Remarks Manufacturer Al series: ZA3 For single-wire insertion | PHOENIX CONTACT AI-0.5-6WH for Thin Cable (product code: 3200687) Al series: UD6 For two-wire insertion AI-0.25-6BU for Thin Cable (product code: 1204436) | (multi-drop wiring) (product code: 3201291) Terminating Resistors for DeviceNet Network Model Specifications Manufacturer DRS1-T Terminal-block Terminating Resistor, 121 Q +1% 1/4 W OMRON DRS2-1 Shielded Terminating Resistor (male plug), micro-size (M12) DRS2-2 Shielded Terminating Resistor (female socket), micro-size (M12) DRS3-1 Shielded Terminating Resistor (male plug), mini-size A Terminating Resistor can also be connected to a T-branch Tap or a one-branch Power Supply Tap. T-branch Taps One-branch Taps Model Specifications Manufacturer

includes three XW4B-05C1-H1-D parallel connectors with screws (When used on a trunk line, one branch line can be connected.) Connector insertion direction: Horizontal A Terminating Resistor (included as standard) can be connected. OMRON

includes three XW4B-05C1-H1-D parallel connectors with screws (When used on a trunk line, one branch line can be connected.) Connector insertion direction: Vertical A Terminating Resistor (included as standard) can be connected. OMRON

includes three XW4B-05C1-VIR-D orthogonal connectors with screws (When used on a trunk line, one branch line can be connected.) Connector insertion direction: Vertical A Terminating Resistor (included as standard) can be connected. OMRON Three-branch Taps Model Specifications Manufacturer

Includes five XW4B-05C1-H1-D parallel connectors with screws (When used on a trunk line, three branch lines can be connected.) Connector insertion direction: Horizontal A Terminating Resistor (included as standard) can be connected. OMRON

Includes five XW4B-05C1-H1-D parallel connectors with screws (When used on a trunk line, three branch lines can be connected.) Connector insertion direction: Vertical A Terminating Resistor (included as standard) can be connected. OMRON

includes five XW4B-05C1-VIR-D orthogonal connectors with screws (When used on a trunk line, three branch lines can be connected.) Connector insertion direction: Vertical A Terminating Resistor (included as standard) can be connected. OMRON C-2

DeviceNet Connection Hardware Appendix C Shielded T-branch Connectors Model Specifications Manufacturer DCN2-1 One-branch shielded T-branch connectors, three micro-size (M12) connectors OMRON DCN3-11 One-branch shielded T-branch connectors, three mini-size connectors DCN3-12 One-branch shielded T-branch connectors, two mini-size connectors and one micro-size (M12) connector One-branch Power Supply Tap Model Specifications Manufacturer DCN-1P One-branch tap for power supply. Use this tap when connecting a communica- | OMRON tions power supply. Includes two XW4B-05C1-H1-D parallel connectors with screws and two fuses as standard. A Terminating Resistor (included as standard) can be connected. C-3

DeviceNet Connection Hardware Appendix C C-4

Glossary The following table provides a list of commonly used DeviceNet terms. Term Explanation Bus OFF Indicates that the error rate in the network is extremely high. Errors are detected when a fixed threshold is exceeded by the internal error counter. (the internal error counter is cleared when the Master Unit is started or restarted.) CAN CAN is short for Controller Area Network. It is a communications protocol developed as a LAN for use in automobiles. DeviceNet employs CAN technology. Configurator A device for setting the system settings. The Configurator can read ID information, read and write parameters, and display the network configuration. OMRON's DeviceNet Configurator is designed for use with an OMRON Master Unit. Consumed Connection Size Indicates the data size (byte length) received via the connection. ODVA ODVA is short for Open DeviceNet Vendor Association, Inc. lt is a non-profit organization formed by machine vendors with the aim to administer and popularize the DeviceNet specification. Produced Connection Size Indicates the data size (byte length) sent via the connection. Connection This is a logical communication channel for facilitating communications between nodes. Communications are maintained and managed between the master and slaves. Device Profile Standardizes the configuration and behavior (the smallest data configuration and opera- tion that must be supported by the device) of devices of the same type (equipment, etc.). Provides mutual exchangeability between devices of the same type. Also known as a device model. Devices for which device profiles are currently being investigated include sensors, valves, display units, and encoders. Master/Slave A node can be either a master, which collects and distributes data, or a slave, which out- puts and inputs data according to the instructions received from the master. OMRON's DeviceNet products are already provided with either master or slave functions in a pre- defined master/slave connection set. G-1

accumulated ON (RUN) time monitor, 2-5 AT cancel, 4-12 AT execute, 4-12 auto mode, 4-12 auto/manual, 4-12 auxiliary outputs (terminals), 3-12 bank selection, 4-12 bit strobe, A-1

cables communications cables models, C-1 change of state (COS), A-1 cleaning, 7-3 command block, 5-3, 5-5, 5-6 communications cables, C-1 connection example, 1-2 cycle time, 6-3 distance, 1-5 error operation, 2-5 performance, xvii, 6-1 specifications, 1-5 Communications Power Voltage Monitor Error Flag, 4-11 CompoWay/F ASCII commands, 5-3, 5-5 CompoWay/F binary commands, 5-3, 5-5 CompoWay/F commands, 5-4 Configurator operations, 2-3 connections, 2-2 hardware, C-1 connectors attaching, 3-16 models, C-1 control outputs (terminals), 3-11 crimp terminals, 3-16, C-2 models, C-2 current consumption, 1-5 cyclic, A-1

device profiles, A-2 DeviceNet communications cables, C-1 preparing, 3-15 wiring, 3-15 DeviceNet communications connector, 2-2 DeviceNet Communications Unit connector, 3-16 DeviceNet Connector, C-1

inspection, 7-3 installation, 3-4 instance ID, 5-8 insulation blocks, 3-18

network power monitor, 2-4 network status (NS indicator), 3-3 networks with multiple masters, 6-4

One-branch Power Supply Taps, C-3 One-branch Taps, C-2 operation commands, 4-12 OUT Area, 4-3 Output Enable Bts, 4-4, 4-11

panel cutout dimensions, 3-4 part names, 3-2 poll, A-1 potentiometer inputs (terminals), 3-13 power supply (terminals), 3-10 precautions wiring, 3-9 programming samples, 4-13, 4-16 protect level move to, 4-12 pulling out the Controller, 3-5

refresh processing time, 6-3, 6-4 remote 1/0 communications, 1-2, 1-3, 4-1 performance, 6-2 removing Controllers, 3-5 replacing Controllers, 7-4 replacing Units, 7-4 response block, 5-3, 5-5, 5-6

Setting Area 1 move to, 4-12 setup procedure, 2-2 Shielded T-branch Connectors, C-3 slaves maximum number, 1-5 software reset, 4-12 SP mode, 4-12 specifications communications, 1-5 DeviceNet, A-1 general, 1-5 startup time, 6-5 status, 4-3, 4-9 strobe, 4-12, 4-14 supply voltage, 1-5 system startup time, 6-5

T-branch Taps, C-2 terminal arrangement, 3-6 Terminating Resistors, C-2 Three-branch Taps, C-2 transfer outputs (terminals), 3-11 troubleshooting, 1-xvii, 7-1

wiring, 3-10 precautions, 3-9 write mode, 4-12

Revision History A manual revision code appears as a suffix to the catalog number on the front cover of the manual. Cat. No. H124-E1-01 Revision code The following table outlines the changes made to the manual during each revision. Page numbers refer to the previous version. Revision code Date Revised content 1 February 2004 | Original production R-1