OMRON EJ1 DeviceNet Communications Unit Operation Manual
Below you will find brief information for EJ1 DeviceNet Communications Unit. The DeviceNet Communications Unit enables a DeviceNet master to communicate with multiple EJ1 Temperature Controllers through the DeviceNet to monitor their process values, write parameters, and control operation. It allows you to communicate with up to 16 temperature controllers simultaneously and can be used to share I/O by using remote I/O communications, without requiring special programming. You can also use a configurator to set specific data for communications with the master, and even manipulate more than 100 words of parameters by using expansion remote I/O. Finally, you can send explicit messages to the DeviceNet Communications Unit to perform various operations.
advertisement
Cat. No. H155-E1-03
TM
DeviceNet Communications Unit for EJ1 Temperature Controllers
OPERATION MANUAL
NOTE
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 constantly 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.
Trademarks
• ODVA, CIP, CompoNet, DeviceNet, and EtherNet/IP are trademarks of ODVA.
Other company names and product names in this document are the trademarks or registered trademarks of their respective companies.
Copyrights
Microsoft product screen shots reprinted with permission from Microsoft Corporation.
DeviceNet Communications Unit for EJ1 Temperature Controllers
Operation Manual
Revised July 2015
iv
Preface:
OMRON products are manufactured for use according to proper procedures by a qualified operator and only for the purposes described in this manual.
This manual contains information on the functions, performance, and operating procedure for the
DeviceNet Communications Unit. Be sure to heed the following points when using the DeviceNet Communications Unit.
• The DeviceNet Communications Unit must be handled by personnel who have a sufficient knowledge of electrical systems.
• Please read this manual carefully and be sure that you understand the information provided before attempting to operate the DeviceNet Communications Unit.
• Keep this manual close at hand for reference during operation.
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.
v
Terms and Conditions Agreement
Warranty, Limitations of Liability
Warranties
● Exclusive Warranty
● Limitations
● Buyer Remedy
Omron’s exclusive warranty is that the Products will be free from defects in materials and workmanship for a period of twelve months from the date of sale by Omron (or such other period expressed in writing by Omron). Omron disclaims all other warranties, express or implied.
OMRON MAKES NO WARRANTY OR REPRESENTATION, EXPRESS OR
IMPLIED, ABOUT NON-INFRINGEMENT, MERCHANTABILITY OR FIT-
NESS FOR A PARTICULAR PURPOSE OF THE PRODUCTS. BUYER
ACKNOWLEDGES THAT IT ALONE HAS DETERMINED THAT THE PROD-
UCTS WILL SUITABLY MEET THE REQUIREMENTS OF THEIR INTENDED
USE.
Omron further disclaims all warranties and responsibility of any type for claims or expenses based on infringement by the Products or otherwise of any intellectual property right.
Omron’s sole obligation hereunder shall be, at Omron’s election, to (i) replace
(in the form originally shipped with Buyer responsible for labor charges for removal or replacement thereof) the non-complying Product, (ii) repair the non-complying Product, or (iii) repay or credit Buyer an amount equal to the purchase price of the non-complying Product; provided that in no event shall
Omron be responsible for warranty, repair, indemnity or any other claims or expenses 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. Return of any Products by Buyer must be approved in writing by Omron before shipment. Omron Companies shall not be liable for the suitability or unsuitability or the results from the use of Products in combination with any electrical or electronic components, circuits, system assemblies or any other materials or substances or environments. Any advice, recommendations or information given orally or in writing, are not to be construed as an amendment or addition to the above warranty.
Limitation on
Liability; Etc
See http://www.omron.com/global/ or contact your Omron representative for published information.
OMRON COMPANIES SHALL NOT BE LIABLE FOR SPECIAL, INDIRECT,
INCIDENTAL, OR CONSEQUENTIAL DAMAGES, LOSS OF PROFITS OR
PRODUCTION OR COMMERCIAL LOSS IN ANY WAY CONNECTED WITH
THE PRODUCTS, WHETHER SUCH CLAIM IS BASED IN CONTRACT,
WARRANTY, NEGLIGENCE OR STRICT LIABILITY.
Further, in no event shall liability of Omron Companies exceed the individual price of the Product on which liability is asserted.
vi
Application Considerations
Suitability of Use
Programmable
Products
Omron Companies shall not be responsible for conformity with any standards, codes or regulations which apply to the combination of the Product in the
Buyer’s application or use of the Product. At Buyer’s request, Omron will provide applicable third party certification documents identifying ratings and limitations of use which apply to the Product. This information by itself is not sufficient for a complete determination of the suitability of the Product in combination with the end product, machine, system, or other application or use.
Buyer shall be solely responsible for determining appropriateness of the particular Product with respect to Buyer’s application, product or system. Buyer shall take application responsibility in all cases.
NEVER USE THE PRODUCT FOR AN APPLICATION INVOLVING SERIOUS
RISK TO LIFE OR PROPERTY WITHOUT ENSURING THAT THE SYSTEM
AS A WHOLE HAS BEEN DESIGNED TO ADDRESS THE RISKS, AND
THAT THE OMRON PRODUCT(S) IS PROPERLY RATED AND INSTALLED
FOR THE INTENDED USE WITHIN THE OVERALL EQUIPMENT OR SYS-
TEM.
Omron Companies shall not be responsible for the user’s programming of a programmable Product, or any consequence thereof.
Disclaimers
Performance Data
Data presented in Omron Company websites, catalogs and other materials 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 user must correlate it to actual application requirements. Actual performance is subject to the Omron’s Warranty and Limitations of Liability.
Change in
Specifications
Product specifications and accessories may be changed at any time based on improvements and other reasons. It is our practice to change part numbers when published ratings or features are changed, or when significant construction changes are made. However, some specifications of the Product may be changed without any notice. When in doubt, special part numbers may be assigned to fix or establish key specifications for your application. Please consult with your Omron’s representative at any time to confirm actual specifications of purchased Product.
Errors and Omissions
Information presented by Omron Companies has been checked and is believed to be accurate; however, no responsibility is assumed for clerical, typographical or proofreading errors or omissions.
vii
■ Notation and Definitions for Precautionary Information
The following notation is used in this manual to provide precautions required to ensure safe usage of the DeviceNet Communications Unit. The safety precautions that are provided here are extremely important to safety. Always read and heed information provided in all safety precautions.
The following notation is used.
Definitions of Warning and Caution
WARNING
Indicates a potentially hazardous situation which, if not avoided, is likely to result in slight or moderate injury or occasionally, death or serious injury. And serious property damage may occur as well.
CAUTION
Indicates a potentially hazardous situation which, if not avoided, is likely to result in minor or moderate injury or property damage.
■ Symbols
Caution
Symbol Meaning
General Caution
Indicates non-specific general cautions, warnings, and dangers.
Electrical Shock Caution
Indicates possibility of electric shock under specific conditions.
Prohibition
Mandatory
Caution
General Prohibition
Indicates non-specific general prohibitions.
General Caution
Indicates non-specific general cautions, warnings, and dangers.
viii
Warnings and Cautions
WARNING
Never use the product without installing protective circuit in network.
Doing so may possibly cause abnormal operation, and result in serious injury, property damage, or accident. To operate your total system safely even if any equipment failure occurs, or any trouble is caused by an external element, be sure to configure an external-control-circuit that consists of emergency stop, interlock and limit circuits to provide double or triple safeguard.
CAUTION
Do not touch the terminals while power is being supplied.
Doing so may occasionally result in minor injury due to electric shock.
Use a power supply unit that complies with the reinforced insulation specified in IEC 60604 for the EJ1. If non-compliant power supply units are used, electric shock may occasionally result in minor injury.
Do not allow pieces of metal, wire clippings, or fine metallic chips generated during installation to enter the product. Doing so may occasionally result in electric shock, fire, or malfunction.
Do not use the product where subject to flammable or explosive gas. Otherwise, minor injury from explosion may occasionally occur.
Never disassemble, modify, or repair the product or touch any of the internal parts. Minor electric shock, fire, or malfunction may occasionally occur.
If screws are loosened, fire may occasionally occur. Tighten the fixing screws for connector with the torque of 0.25 to 0.30 N·m as specified.
When changing the program by using online edit, an unexpected actuation may occasionally result in minor or moderate injury or property damage. Make sure that the product is not affected by prolonged cycle time on DeviceNet before using online edit.
When transferring a program to another node, or changing I/O memory, an unexpected actuation may occasionally result in minor or moderate injury or property damage. Before doing these operations, make sure that the node to be changed is in appropriate status.
ix
Precautions for Safe Use
1) The product is designed for indoor use only. Do not use the product outdoors or in any of the following locations.
• Places directly subject to heat radiated from heating equipment.
• Places subject to splashing liquid or oil atmosphere.
• Places subject to direct sunlight.
• Places subject to dust or corrosive gas (in particular, sulfide or ammonia gas)
• Places subject to intense temperature change.
• Places subject to icing or condensation.
• Places subject to vibration or strong shocks.
2) Use and store the product within the rated temperature and humidity ranges. Provide forced-cooling if required.
3) To allow heat to escape, do not block the area around the temperature controller. Also, do not block its ventilation holes.
4) Be sure to wire properly with correct polarity of terminals.
5) Use crimped terminals of specified sizes (M3, width: 5.8 mm or less) for wiring. To connect bare wires to the terminal block, use wires with a gage of AWG22 to AWG14 (cross-sectional area: 0.326 mm
2
to
2.081 mm
2
). For wirings other than power supply, use wires with a gage of AWG28 to AWG14 (crosssectional area: 0.081 mm
2
to 1.309 mm
2
). (The stripping length: 6 to 8 mm).
6) Do not wire terminals that do not have an identified use.
7) Secure as much space as possible between the product and devices that generates a strong highfrequency or surge. Separate the high-voltage or large-current power lines from other lines, and avoid parallel or common wiring with the power lines when you are wiring to the terminals.
8) Use the product within the rated load and power supply voltage.
9) Make sure that the rated voltage is attained within 2 s of turning ON the power.
10) The switch or circuit breaker must be located within an easy reach of the operator, and must be marked as a disconnecting means for this unit.
11) Do not use paint thinner or similar chemical to clean with. Use standard grade alcohol.
12) Never touch the electric components, connectors, or patterns in the product with bare hands. Always hold the product by its enclosure. Inappropriate handling of the product may occasionally damage internal components due to static electricity.
13) Use a switch, relay, or other device for turning OFF the power supply quickly. Gradually lowering the voltage of the power supply may result in incorrect outputs or memory errors.
14) Connect only the specified number of products in only a specified configuration.
15) Mount the product to a DIN Rail mounted vertically to the ground.
16) Always turn OFF the power before wiring, replacing the product, or changing the configuration.
17) Before installing the product, attach the enclosed cover seal to the connector opening on the left end of the product.
18) Make sure that the data transfer distance for DeviceNet is within the specified range, and use the specified cable only. Also, refer to this manual for specifications including appropriate data transfer distance and cable.
19) Do not bend or pull data transfer cable for DeviceNet forcibly.
20) Turn OFF the DeviceNet before connecting/disconnecting connectors. Not doing so may result in equipment failure or malfunction.
x
Precautions for Correct Use
● Installation
1) Connect the DeviceNet Communications Unit to the left side of a Basic Unit or an End Unit.
2) The EJ1 cannot be used linked to a CJ-series PLC.
● Service Life
1) Use the product within the following temperature and humidity ranges.
Temperature:
−10 to 55°C (with no icing or condensation)
Humidity: 25% to 85%
When the Temperature Controller is incorporated in a control panel, make sure that the controller’s ambient temperature and not the panel’s ambient temperature does not exceed 55
°C.
2) The service life of electronic devices like the Temperature Controller is determined by the service life of internal electronic components. Component service life is affected by the ambient temperature: the higher the temperature, the shorter the service life and the lower the temperature, the longer the service life.
Therefore, the service life can be extended by lowering the temperature of the Temperature Controller.
3) Mounting two or more Temperature Controllers side by side, or mounting Temperature Controllers above each other may cause heat to build up inside the Temperature Controllers, which will shorten their service life. If the Temperature Controllers are mounted above each other or side by side, use forced cooling by fans or other means of air ventilation to cool down the Temperature Controllers. However, be sure not to cool only the terminals. Doing so will result in measurement errors.
● Precautions for Operation
1) It takes a certain amount of time for the outputs to turn ON from after the power supply is turned ON. Due consideration must be given to this time when designing control panels, etc.
2) It takes 30 minutes from the time the product is turned ON until the correct temperature is indicated.
Always turn ON the power supply at least 30 minutes before starting temperature control.
3) Avoid using the Temperature Controller near a radio, television set, or other wireless device. Its use would result in reception disturbance.
xi
Preparations for Use
Be sure to thoroughly read and understand the manual provided with the product, and check the following points.
Timing Check point
Purchasing the product Product appearance
Setting the Unit
Wiring
Product model and specifications
Product installation location
Terminal wiring
Power supply inputs
Operating environment Ambient temperature
Vibration and shock
Foreign particles
Details
After purchase, check that the product and packaging are not dented or otherwise damaged. Damaged internal parts may prevent optimum control.
Make sure that the purchased product meets the required specifications.
Provide sufficient space around the product for heat dissipation. Do not block the vents on the product.
Do not subject the terminal screws to excessive stress (force) when tightening them.
Make sure that there are no loose screws after tightening terminal screws to the specified torque of 0.25 to 0.30 N·m.
Be sure to confirm the polarity for each terminal before wiring the terminal block and connectors.
Wire the power supply inputs correctly. Incorrect wiring will result in damage to the internal circuits.
The ambient operating temperature for the product is
−10 to 55°C (with no condensation or icing). To extend the service life of the product, install it in a location with an ambient temperature as low as possible.
In locations exposed to high temperatures, if necessary, cool the products using a fan or other cooling method.
Check whether the standards related to shock and vibration are satisfied at the installation environment. (Install the product in locations where the conductors will not be subject to vibration or shock.)
Install the product in a location that is not subject to liquid or foreign particles entering the product. If sulfide, chlorine, or other corrosive gases are present, remove the source of the gas, install a fan, or use other countermeasures to protect the product.
■ EC Directives
• EMC Directives
• Low Voltage Directive
Concepts
EMC Directives
OMRON devices that comply with EC Directives also conform to the related
EMC standards so that they can be more easily built into other devices or 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 Directives 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.
xii
Conformance to EC Directives
The EJ1 DeviceNet Communications Unit complies 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,2,3...
1.
The Unit must be installed within a control panel.
1,2,3...
2.
You must use reinforced insulation or double insulation for the DC power supplies used for the communications power supply, internal power supply, and I/O power supplies.
3.
Units complying with EC Directives also conform to the Common Emission
Standard (EN50081-2). Radiated emission characteristics (10-m regulations) 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.
4.
The Unit is a Class A product (products for industrial environments). In residential environment areas it may cause radio interference, in which case the user may be required to take adequate measures to reduce interference.
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 Unit.
30 mm 33 mm
13 mm 29 mm
Ferrite Core (Data Line Filter): 0443-164151 (manufactured by Fair-Rite Products Co., Ltd.)
Impedance specifications
25 MHz: 105
Ω
100 MHz: 190
Ω
30 mm
13 mm
29 mm
33 mm
2.
Wire the control panel with as thick and short electric lines as possible and ground to 100
Ω min.
3.
Keep DeviceNet communications cables as short as possible and ground to 100
Ω min.
xiii
Related Manuals
■ EJ1
The manuals related to the EJ1 DeviceNet Communications Unit are configured as shown in the following tables. Refer to these manuals as required.
Name
EJ1
EJ1N-HFU @-DRT
DeviceNet
Communications Unit Operation Manual
EJ1
EJ1N-TC2 @
EJ1N-TC4 @
EJ1C-EDU @
Modular Temperature Controllers User's Manual
CX-Thermo Ver. 4.
EST2-2C-MV4
@ (online help)
Cat. No.
H155 (This manual)
H142
---
(Available only as online help.)
Contents
Describes the following information on the
DeviceNet Communications Unit.
• Overview and features
• System configuration
• Mounting and wiring
• Troubleshooting
Describes the following information on the EJ1.
• Overview and features
• System configuration
• Mounting and wiring
• Troubleshooting
Describes how to set parameters and adjust devices (i.e., components such as Temperature
Controllers) using the CX-Thermo.
■ DeviceNet Master Unit
Name
DeviceNet
Operation Manual
Cat. No.
W267
DeviceNet
Master Units
Operation Manual
CS/CJ Series DeviceNet
Unit Operation Manual
W379
W380
Contents
Describes the configuration and construction of a
DeviceNet network, including installation procedures and specifications for cables, connectors, and other connection devices, as well as information on the communications power supply.
Describes the models, specifications, functions, and application methods of C200HX/HG/HE,
CVM1, and CV-series DeviceNet Master Units.
Describes the models, specifications, functions, and application methods of the CS1-series
DeviceNet Unit.
■ G3ZA Multi-channel Power Controller Manual
Name
G3ZA
G3ZA-4H203-FLK-UTU
G3ZA-4H403-FLK-UTU
G3ZA-8H203-FLK-UTU
G3ZA-8H403-FLK-UTU
Multi-channel Power Controller User's Manual
Cat. No.
Z200
Contents
Provides an outline of and describes the features, installation, wiring, RS-485 serial communications settings, and basic function for the G3ZA Multichannel Power Controller.
xiv
■ G3PW Power Controller Manual
Name
G3PW-A220EC-C-FLK
G3PW-A230EC-C-FLK
G3PW-A245EC-C-FLK
G3PW-A260EC-C-FLK
G3PW-A220EC-S-FLK
G3PW-A230EC-S-FLK
G3PW-A245EC-S-FLK
G3PW-A260EC-S-FLK
Power Controller User's Manual
■ CS/CJ-series PLC Manuals
Name
SYSMAC CJ Series
CJ2H-CPU6 @-EIP
CJ2H-CPU6 @
CJ2M-CPU @@
CPU Unit Hardware Manual
SYSMAC CJ2- Series
CJ2H-CPU6 @-EIP
CJ2H-CPU6 @
CJ2M-CPU @@
CPU Unit Software Manual
SYSMAC CJ Series
CJ1H-CPU @@H-R
CJ1G/H-CPU @@H
CJ1G-CPU @@P
CJ1G-CPU @@
CJ1M-CPU @@
Programmable Controllers Operation Manual
SYSMAC CS/CJ Series
CS1G/H-CPU @@-EV1, CS1G/H-CPU@@H, CS1D-CPU@@H,
CS1D-CPU @@S, CJ1H-CPU@@H-R, CJ1G-CPU@@,
CJ1G/H-CPU
@@H, CJ1G-CPU@@P, CJ1M-CPU@@,
NSJ @-@@@@(B)-G5D, NSJ@-@@@@(B)-M3D
Programmable Controllers Programming Manual
SYSMAC CS/CJ Series
CJ2H-CPU6 @-EIP, CJ2H-CPU6@, CJ2M-CPU@@,
CS1G/H-CPU
@@H, CS1G/H-CPU@@-EV1, CS1D-CPU@@H,
CS1D-CPU @@S, CJ1H-CPU@@H-R, CJ1G/H-CPU@@H,
CJ1G-CPU @@P, CJ1M-CPU@@, CJ1G-CPU@@,
NSJ
@-@@@@(B)-G5D, NSJ@-@@@@(B)-M3D
Programmable Controllers Instructions Reference Manual
SYSMAC CS Series
CS1G/H-CPU @@H
Programmable Controllers Operation Manual
Cat. No.
Z280
Contents
Provides an outline of and describes the features, installation, wiring, RS-485 serial communications settings, and basic function for the G3PW Power Controller.
Cat. No.
W472
Contents
Provides an outlines of and describes the design, installation, maintenance, and other basic operations for the CJ-series
PLCs.
W473
W393
W394
W474
W339
Describes programming and other methods to use the functions of the CJ-series
PLCs.
Provides an outlines of and describes the design, installation, maintenance, and other basic operations for the CJ-series
PLCs.
Describes programming and other methods to use the functions of the CS/CJseries PLCs.
Describes the ladder diagram programming instructions supported by CS/CJseries PLCs.
Provides an outlines of and describes the design, installation, maintenance, and other basic operations for the CS-series
PLCs.
■ Support Software Manuals
Name
DeviceNet
Configurator Ver. 2.@ Operation Manual
CXONE-AL @@C-V4/AL@@D-V4
CXONE-LT @@C-V4
CX-One FA Integrated Tool Package Setup Manual
Cat. No.
W382
W463
Contents
Describes the operating procedures of the
DeviceNet Configurator.
Installation and overview of CX-One FA
Integrated Tool Package.
xv
Name
CXONE-AL @@C-V4/AL@@D-V4
CX-Integrator Ver. 2.
@ Operation Manual
CXONE-AL @@C-V4/AL@@D-V4
CX-Programmer Operation Manual
Cat. No.
W464
W446
Contents
Describes operating procedures for the CX-
Integrator Network Configuration Tool for
CS-, CJ-, CP-, and NSJ-series Controllers.
Provides information on how to use the CX-
Programmer for all functionality except for function blocks.
xvi
Meanings of Abbreviations and Terms
The following abbreviations and terms are used in this manual.
Abbreviation or term
AT
EDU
EU
HB
HS
LBA
LSP
OC
PV
RSP
SP
TC4/TC2
Meaning
Autotuning
EJ1 End Unit
Engineering unit (See note.)
Heater burnout
Heater short
Loop burn alarm
Local SP
Heater overcurrent
Process value
Remote SP
Set point
EJ1 Basic Unit
• TC4: Four-channel Basic Unit
• TC2: Two-channel Basic Unit
EJ1 Basic Unit listed above (TC4 or TC2) Temperature
Controller
Configurator word (CIO) channel (ch) communications unit number unit number as a CPU Bus Unit
Device to perform system setup and other functions. Includes functions for reading ID data, reading and writing parameters, and displaying network configurations. The DeviceNet Configurator and the CX-Integrator (with the same screen configuration as the DeviceNet Configurator) are available for
Units manufactured by OMRON.
Words allocated in the CIO Areas of the CPU Unit of the PLC.
Number of control loops for a Temperature Controller.
An identification number for a Temperature Controller connected to a
DeviceNet Communications Unit. (Set using both rotary switch 1 and DIP switch pin 2.)
The unit number of a DeviceNet Master Unit in the PLC. (Unit numbers are used as identification numbers for CPU Bus Units.)
Note “EU” stands for Engineering Unit. EU is used as the minimum unit for engineering units such as
°C, m, and g. The size of EU varies according to the input type.
For example, when the input temperature setting range is –200 to +1300
°C, 1 EU is 1°C, and when the input temperature setting range is –20.0 to +500.0
°C, 1 EU is 0.1°C.
For analog inputs, the size of EU varies according to the decimal point position of the scaling setting, and 1 EU becomes the minimum scaling unit.
xvii
xviii
TABLE OF CONTENTS
SECTION 1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1
SECTION 2
Operating Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15
SECTION 3
Parts, Installation, and Wiring . . . . . . . . . . . . . . . . . . . . . . .
21
SECTION 4
Remote I/O Communications . . . . . . . . . . . . . . . . . . . . . . . .
35
SECTION 5
Operations from the Configurator . . . . . . . . . . . . . . . . . . . .
83
SECTION 6
Explicit Message Communications . . . . . . . . . . . . . . . . . . . . 103
xix
xx
TABLE OF CONTENTS
SECTION 7
Communications Performance . . . . . . . . . . . . . . . . . . . . . . . 125
SECTION 8
Troubleshooting and Maintenance . . . . . . . . . . . . . . . . . . . . 137
Appendices
B Allocation Numbers for Configurators Manufactured by Other Companies . . . . . . . . . . . .
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
About this Manual:
This manual describes the installation and operation of the EJ1 DeviceNet Communications Unit for
EJ1 Temperature 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 the EJ1 DeviceNet Communications Unit. Be sure to read the precautions provided in the following section.
Precautions provides general precautions for using the EJ1 DeviceNet Communications Unit, Programmable Controller, and related devices.
Section 1 introduces the features and system configuration of the EJ1 DeviceNet Communications
Unit, the types of EJ1 Temperature Controller that can be used, and other basic information.
Section 2 outlines the basic operating procedures of the EJ1 DeviceNet Communications Unit.
Section 3 describes the methods used to install and wire the EJ1 DeviceNet Communications Unit and the EJ1 Temperature Controller. The settings of DeviceNet Communications Unit switches are also described.
Section 4 describes the input (IN) areas and output (OUT) areas that EJ1 DeviceNet Communications
Units can use for remote I/O communications. The methods to allocate data for master communications are also described.
Section 5 describes the DeviceNet Configurator operations that can be used for the EJ1 DeviceNet
Communications Unit except for allocation procedures, which are described in SECTION 4 Remote I/O
Section 6 describes how to send explicit messages to the EJ1 DeviceNet Communications Unit, including how to send CompoWay/F commands using explicit messages. CompoWay/F commands are supported by the EJ1 Temperature Controller.
Section 7 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.
Section 8 describes error processing, periodic maintenance operations, and troubleshooting procedures needed to keep the DeviceNet Network operating properly. Details on resetting replaced Units 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 handling methods for EDS setting files required for multivendor environments, the device profile of the EJ1 DeviceNet Communications Unit, and information on related products.
!WARNING
Failure to read and understand the information provided in this manual may result in personal 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.
xxi
xxii
SECTION 1
Overview
This section introduces the features and system configuration of the EJ1 DeviceNet Communications Unit, the types of EJ1
Temperature Controller that can be used, and other basic information.
1-1-2 Overview of Unit Communications Functions . . . . . . . . . . . . . . . . .
1-1-3 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-2-1 DeviceNet Communications Specifications . . . . . . . . . . . . . . . . . . .
1-2-2 Function and Performance Specifications . . . . . . . . . . . . . . . . . . . .
1-2-3 General Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-3 Connecting Temperature Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-3-1 Temperature Controller ID and Number of Connectable Units . . . .
1-3-2 Temperature Controller Communications . . . . . . . . . . . . . . . . . . . .
1-3-3 Temperature Controller Models . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-3-4 Temperature Controller Power Supply . . . . . . . . . . . . . . . . . . . . . . .
1-3-5 Temperature Controller Registration . . . . . . . . . . . . . . . . . . . . . . . .
1
Features and System Configuration
Section 1-1
1-1 Features and System Configuration
1-1-1 Features
The DeviceNet Communications Unit enables a DeviceNet master to communicate with multiple EJ1 Temperature Controllers through the DeviceNet to monitor their process values, write parameters, and control operation.
Using DeviceNet Functions
Simultaneously Managing
Multiple Temperature
Controllers from the
Master
Up to 16 Temperature Controllers can be connected to a single DeviceNet
Communications Unit. The DeviceNet Communications Unit is connected to the master as a DeviceNet slave. Up to 63 slaves can be connected to a single master, so multiple DeviceNet Communications Units and other types of slaves can be managed as part of the same system.
Remote I/O
Communications
The master and DeviceNet Communications Units can share I/O by using remote I/O communications. Data in the EJ1 Temperature Controllers, such as process values (PVs) and set points (SPs), can be allocated for communications with the master to enable sending and receiving the allocated data via remote I/O communications, without requiring special programming.
• Remote I/O Communications without a Configurator
Using the DeviceNet Communications Unit, basic Temperature Controller data can be allocated for communications with the master, such as process values (PVs) and set points (SPs), without requiring a Configurator.
This is called “simple I/O allocation.” Simple I/O allocation can be easily set from the DIP switch of the DeviceNet Communications Unit.
• User-set Data Allocations with a Configurator
The specific data required for communications with the master can also be allocated by using I/O allocations from the Configurator.
Expansion Remote I/O to
Enable Using More Than
100 Words of Parameters
Explicit Message
Communications
Setting, Monitoring, and
Operating the
Temperature Controller from the Configurator
Expansion remote I/O can be used to read and write parameters. Specific parameters allocated in I/O memory of the master can be switched to a variety of parameters by using memory operations. This function enables manipulating more than 100 words of parameters. Even if the number of parameters to be read and written increases, modifications can be handled simply by changing operations in the memory of the master.
By executing commands from the PLC, various operations can be performed, including reading/writing specific 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.
The Configurator (Ver. 2.2 or higher) or CX-Integrator (Ver. 2.2 or higher) can be used to create the device parameters for the DeviceNet Communications
Unit, including settings for the DeviceNet Communications Unit and setting for the Temperature Controllers. The Configurator can then be used to download the parameters together to the DeviceNet Communications Unit and Temperature Controllers. (See note.)
The Configurator can also be used to monitor Temperature Controller process values, and execute operation commands for the Temperature Controllers.
The Configurator can be used to copy parameters between Temperature Controller channels, allowing the initial parameters of Temperature Controllers requiring the same or similar parameters to be easily set.
2
Features and System Configuration
Section 1-1
Automatically Detects
Baud Rate
Previously, the baud rate had to be set for each slave, but the DeviceNet Communications Unit automatically detects and matches 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 DeviceNet Communications
Unit and then turn it ON again.)
Wide Range of Maintenance Functions
Copy Function (Uploading or Downloading
Temperature Controller
Parameters)
Parameters for all Temperature Controllers connected to the DeviceNet Communications Unit can be uploaded or downloaded together. (The parameters that have been read are stored in the DeviceNet Communications Unit except for bank parameters and G3ZA and G3PW parameters.) When Temperature
Controllers are replaced, the new Controllers can be easily reset onsite without using a Configurator.
Monitoring Network Power
Voltage
Monitoring the Unit
Conduction Time
Unit Comments
Setting Temperature
Controller Comments
Monitoring
Communications Error
History
Monitoring Temperature
Controller Power Status
Monitor Temperature
Controller Conduction
Time and RUN Time
The DeviceNet network communications power voltage values (present value, peak value, and bottom value) can be stored in the DeviceNet Communications Unit, and the recorded voltages can be read from the Configurator. By setting the voltage monitor value in the DeviceNet Communications Unit, notification will be sent to the master if the voltage level drops below the monitor value.
The conduction time of the DeviceNet Communications Unit's internal circuit power supply can be recorded. The recorded conduction time can be read from the Configurator or using explicit messages. By setting a monitor value for the conduction time in the DeviceNet Communications Unit, notification will be sent to the master when the total time exceeds the monitor value.
Any name can be set for a DeviceNet Communications Unit and recorded in the Unit. Specifying names enables the user to easily differentiate the applications of the DeviceNet Communications Units when setting and monitoring them from the Configurator.
A name can be set for each Temperature Controller channel connected to the
DeviceNet Communications Unit and recorded in the DeviceNet Communications Unit. Specifying names enables the user to easily differentiate the function of each channel when setting and monitoring them from the Configurator.
The error status for the last four communications errors (the causes and communications power voltage when the communications error occurred) can be recorded in the DeviceNet Communications Unit. The recorded communications error history can be read from the Configurator.
The power supply to the Temperature Controllers can monitored to confirm that power is ON and send notification of the status to the master. (The power status can be checked for Temperature Controllers connected to the
DeviceNet Communications Unit only.) The power status of the Temperature
Controllers can be read from the Configurator or using explicit messages.
The conduction time of the Temperature Controller's internal circuit power supply or the RUN time of the Temperature Controller can be totaled and recorded. (Select whether to total the conduction time or RUN time by setting the monitor mode.) The recorded total time can be read using the Configurator or explicit messages. By setting a monitor value in the DeviceNet Communications Unit, notification will be sent to the master if the Unit conduction time exceeds the monitor value.
3
Features and System Configuration
Section 1-1
1-1-2 Overview of Unit Communications Functions
Remote I/O
Communications
DeviceNet Communications Unit data is shared with the master's IN Area and
OUT Area through DeviceNet. Up to 100 words (200 bytes) each can be used as the IN Area and OUT Area for the DeviceNet Communications Unit. (The first word (two bytes) of the OUT Area is always allocated for the OUT Enable
Bit).
The IN Area is allocated for data such as the communications status and the process values of the Temperature Controller channels and the OUT Area is allocated for the set points of the channels and other data.
When using a CS/CJ-series DeviceNet Unit as the master, the IN Area can be divided into two areas. One is normally used for input data (such as Temperature Controller process values), and the other can be used for reading status
(such as Temperature Controller status). Even when the IN Area is divided into two areas, however, the total number of words that can be used for the IN
Area is still 100 words (200 bytes).
DeviceNet Communications Unit
CPU Unit
Remote I/O communications output area
Output Enable Bit
Read parameter setting
Write parameter setting
PLC
Unit 0, ch 1 SP
Unit 0, ch 2 SP
Unit 1, ch 1 SP
Input Area
Output Completed Flags
Read parameter monitor
Unit 0, ch 1 PV
Unit 0, ch 2 PV
Unit 1, ch 1 PV
Remote I/O communications
DeviceNet
DeviceNet Communications Unit
Unit 0 Unit 1
Temperature Controllers
4
Features and System Configuration
Explicit Message
Communications
Section 1-1
Explicit message commands can be sent from the master to the DeviceNet
Communications Unit to read or write the parameters of the connected Temperature Controllers. CompoWay/F communications commands that were previously used for Temperature Controllers can also be sent (in explicit message format).
The DeviceNet Communications Unit's own parameters can also be read or written.
DeviceNet Unit CPU Unit
PLC
Ladder program
CMND or other communications instruction
Explicit message communications
DeviceNet
DeviceNet Communications Unit
Unit 0 Unit 1
Temperature Controllers
5
Features and System Configuration
Section 1-1
Transferring, Monitoring, and Operating from the Configurator
Any of the Temperature Controller parameters can be read or written from a personal computer using the Configurator (Ver. 2.44 or higher) or CX-Integrator (Ver. 2.2 or higher) and then saved as a file.
The setup parameters for each Temperature Controller channel can be copied, allowing the same or similar settings to be easily set for multiple Temperature Controllers.
DeviceNet Configurator
EJ1
CS/CJ-series DeviceNet Unit
PLC
Serial connection
Setting, monitoring, and executing operation commands for the
Temperature Controllers using the Configurator.
• Setting Temperature Controller settings and downloading them.
• Monitoring Temperature Controller process values and target values.
• Executing Temperature Controller operation commands.
DeviceNet
DeviceNet Communications Unit
Unit
0
Unit
1
DeviceNet Slave
Temperature Controllers
6
Features and System Configuration
1-1-3 System Configuration
Basic Configuration
DeviceNet Configurator
CS/CJ-series DeviceNet Unit
PLC
Serial connection
(setting, monitoring, and operating)
Explicit messages
DeviceNet
Section 1-1
Connect to port B
Distributed placement of 16th Temperature Controller
DeviceNet slave
10
NODE
ADR
1
MAX
No.
2 3
9 8 7 6
2
3
9 8 7 6
23
567
EJ1N
DRT
MS
NS
TS
COPY
NO
UP/DN
TC2/4
MODE
DeviceNet Communications Unit
Temperature Controllers (up to
16 Controllers) (See note.)
EDU
RS-485 (CompoWay/F)
Note: Up to 16 Temperature Controllers can be connected to one
DeviceNet Communications Unit. Use distributed placement via RS-485 for the 16th Temperature Controller.
Connect the master to the DeviceNet Communications Unit, and connect the
DeviceNet Communications Unit to the Temperature Controllers.
The DeviceNet Communications Unit shares I/O with the master as a
DeviceNet slave, and can send data to and receive data from the master using explicit messages.
Up to 63 slaves can be connected to a single master. Up to 16 Temperature
Controllers can be connected to a single DeviceNet Communications Unit.
Note Always connect the DeviceNet Communications Unit to the Temperature Con-
trollers on the left end of the block.
7
Features and System Configuration
Distributed Placement
DeviceNet Configurator
CS/CJ-series DeviceNet Unit
PLC
Serial connection
(setting, monitoring, and operating)
Explicit messages
DeviceNet
10
NODE
ADR
1
2 3
9 8 7 6
2 3
9 8 7 6
EJ1N
DRT
MS
NS
MAX
No.
23 4 567
TS
COPY
NO
EDS
UP/DN
TC2/4
MODE
DeviceNet Communications
Unit
DeviceNet slave
RS-485 communications cable
(length: 500 m max.)
Connect to port
B on the EDU
Section 1-1
Connect to port
B on the EDU
Temperature Controllers (up to
16 Controllers)
Connect to port
B on the EDU
Connect to port
B on the EDU
Connect the master and DeviceNet Communications Unit to port B (RS-485) of each End Unit.
The total cable length for RS-485 communications can be up to 500 m, so
Temperature Controllers located at a distance can be operated using a single
DeviceNet Communications Unit.
Up to 63 slaves can be connected to a single master. Up to 16 Temperature
Controllers total for all blocks can be connected to a single DeviceNet Communications Unit.
8
Specifications
Section 1-2
Terminating resistance of 100 to 125
Ω (1/2 W) must be connected to both ends of the RS-485 communications transmission path.
Note Connect the DeviceNet Communications Unit to the Temperature Controllers
on the left end of any one of the blocks.
1-2 Specifications
1-2-1 DeviceNet Communications Specifications
Item
Communications protocol
Communications functions
Remote I/O communications
Simple I/O allocation
Conforms to DeviceNet
Specifications
• Master-slave connections (polling, COS, or cyclic)
• Conform to DeviceNet specifications.
• Allocates I/O data using switch settings only, without a Configurator.
• I/O is allocated for Temperature Controller status, process values, set points, alarm output status, and other basic data only.
• One block for IN Area, up to 86 words (words are allocated through the unit number set in the highest communications unit number setting)
• One block for OUT Area, up to 74 words (words are allocated through the unit number set in the highest communications unit number setting)
I/O allocations from the Configurator
• Can be used to allocate any I/O data from the Configurator.
• Can be used to allocate any data, such as parameters specific to the
DeviceNet Communications Unit and the Temperature Controller variable area.
• Up to 2 blocks for the IN Area, up to a total of 100 words. (See note 1.)
• One block for OUT Area 1 block, up to 100 words (the first word is always allocated to the OUT Enable Bit). (See note 2.)
I/O allocation sizes 1 channel/parameter (2 bytes/parameter)
Message communications
Setting, monitoring and controlling operations from the Configurator
• Explicit message communications
• CompoWay/F communications commands can be sent (commands are sent in explicit message format).
Supported by DeviceNet Configurator (using the Edit Parameters and Device
Monitor functions of the DeviceNet Communications Unit and Temperature Controllers).
• Used to set and monitor the DeviceNet Communications Unit.
• Used to register connection configurations, make initial settings (see note 3), change settings, and monitor the Temperature Controllers.
• Use to allocates data for master communications.
• Used to allocates word in the IN and OUT Areas for specific data.
• Used to sends operation commands to the Temperature Controllers.
Connection format
Baud rate
Communications media
Communications distance
Combination of multidrop and T-branch connections (for trunk and drop lines)
DeviceNet: 500, 250, or 125 kbps, or automatic detection of master baud rate
Special 5-wire cable (2 signal lines, 2 power lines, and 1 shield line)
Baud rate Network length Drop line length Total drop line length
500 kbps
250 kbps
100 m max.
(100 m max.)
250 m max.
(100 m max.)
6 m max.
6 m max.
39 m max.
78 m max.
125 kbps 500 m max.
(100 m max.)
6 m max.
The values in parentheses apply when Thin Cables are used.
156 m max.
Communications power supply
Maximum number of nodes that can be connected
11 to 25 VDC
64 (includes Configurator when used.)
9
Specifications
Section 1-2
Item
Maximum number of slaves that can be connected
Error control
Power supply
63
Specifications
CRC error detection
Power supplied from DeviceNet communications connector (DeviceNet communications power supply and DeviceNet Communications Unit internal circuit power supply)
Note
1.
When a CS/CJ-series DeviceNet Unit is used as the master, two blocks can be used for the IN Area (the connections can also be set). When a
CVM1, CV-series, or C200HX/HG/HE DeviceNet Master Unit is used, the
IN Area must be in 1 block, and up to 100 words (200 bytes) are allocated.
(Only polling connections can be used.)
2.
When a CVM1, CV-series, or C200HX/HG/HE DeviceNet Master Unit is used, up to 32 words can be allocated in the master for a single node.
3.
The set points, alarm setting values, PID constants, and other Temperature Controller parameters can be set together.
1-2-2 Function and Performance Specifications
Item
Maximum number of Temperature
Controllers that can be connected
Applicable Temperature Controllers
Power supply
Copying
Specifications
16
Note Up to 15 Units can be connected side by side. The 16th Unit is connected using distributed placement by using an End Unit.
(TC4)
• EJ1N-TC4A-QQ
• EJ1N-TC4B-QQ
(TC2)
• EJ1N-TC2A-QNHB
• EJ1N-TC2B-QNHB
• EJ1N-TC2A-CNB
• EJ1N-TC2B-CNB
Power is supplied via the terminal block of the End Unit (power supply for communications between the DeviceNet Communications Unit and Temperature Controllers and power supply for internal circuits of the Temperature Controllers).
The parameters of a connected Temperature Controller can be uploaded or downloaded as a batch by using the DeviceNet Communications Unit’s DIP switch or an explicit message. The bank, G3ZA, and G3PW parameters are not copied.
The uploaded parameters are stored in the DeviceNet Communications Unit.
10
Connecting Temperature Controllers
Section 1-3
1-2-3 General Specifications
Item
Supply voltage
Allowable voltage range
External input power supply
Power consumption (at maximum load)
Current consumption (DeviceNet power supply)
Vibration resistance
20.4 to 26.4 VDC
1 W max.
45 mA max. (24 VDC)
Shock resistance
Dielectric strength
Insulation resistance
Ambient temperature
Ambient humidity
Storage temperature
Enclosure rating
Dimensions
Memory protection
Weight
Specifications
DeviceNet power supply
External input power supply
DeviceNet power supply
24 VDC (internal circuit)
24 VDC (for RS-485 communications circuit/ Temperature Controllers)
11 to 25 VDC
Electromagnetic environment
10 to 55 Hz, 10m/s
2
for 2 hours each in X, Y, and Z directions
150m/s
2
max. 3 times each in 3 axes, 6 directions
600 VAC 50 or 60 Hz 1min
20 M
Ω min. (at 100 VDC)
−10 to 55°C (with no condensation or icing)
25% to 85%
−25 to 65°C (with no condensation or icing)
IP20
20
× 90 × 65 mm (W × H × D)
EEPROM, 100,000 write operations (backup data)
70 g max.
Industrial electromagnetic environment (EN/IEC 61326-1 Table 2)
1-3 Connecting Temperature Controllers
1-3-1 Temperature Controller ID and Number of Connectable Units
A DeviceNet Communications Unit is connected as shown in the following diagram.
1
2 3
9 8 7 6
4
10
NODE
ADR
1
2
3
1
9 8 7 6
4
MAX
No.
EJ1N
DRT
MS
23
4567
NS
TS
NO
COPY
EDS
UP/DN
TC2/4
MODE
DeviceNet
Communications Unit
Temperature Controllers
The DeviceNet Communications Unit differentiates each of the connected
Temperature Controllers according to communications unit numbers (0 to F: 0 to 15 decimal). The Temperature Controllers can be connected in any order.
The communications unit number of each Temperature Controller is set using the rotary switch on the front panel of the Temperature Controller. Always set a unique communications unit number for each Temperature Controller.
Up to 15 Temperature Controllers can be connected side by side. By using an
End Unit, however, up to 16 Temperature Controller can be connected using distributed placement.
11
Connecting Temperature Controllers
Section 1-3
Note There is no priority between operation commands and settings for DeviceNet
communications from the master, and operation commands and settings from the Configurator. Do not change the same data or send different operation commands more than one source at the same time.
1-3-2 Temperature Controller Communications
The DeviceNet Communications Unit communicates through port B on the
Temperature Controllers. The DeviceNet Communications Unit will automatically set the communications settings. You do not need to set them. If you mistakenly change the settings, use the CX-Thermo to restore the default settings and then reset the DeviceNet Communications Unit.
1-3-3 Temperature Controller Models
Refer to EJ1 Temperature Controllers on page 171 for information on the
Temperature Controller models.
1-3-4 Temperature Controller Power Supply
Power is supplied to the Temperature Controllers through the End Unit. For details, refer to the EJ1 Modular Temperature Controllers User's Manual (Cat.
No. H142).
1-3-5 Temperature Controller Registration
The connected Temperature Controllers must be registered in the configuration in the DeviceNet Communications Unit. The DeviceNet Communications
Unit automatically verifies that the registered the Temperature Controllers match the Temperature Controllers currently able to communicate. If the unit numbers do not match in the verification process, the Temperature Controllers will be determined to have an error, causing the following status.
• The TS indicator will flash red.
• The Communicating Flag will turn OFF and the Communications Error
Flag will turn ON for each Temperature Controller that is not communicating but is registered as being connected to the DeviceNet Communications Unit.
The method used to register the connection configuration depends on the method of remote I/O allocation.
1,2,3...
1.
Allocation from the Configurator
With DIP switch pin 1 set to OFF, turn ON the power supply, and register the configuration using the Configurator or an explicit message.
2.
Allocation Using Simple Allocation
Turn DIP switch pin 1 to ON, set DIP switch pin 2 to the model to be connected, and set the highest communications unit number setting to the highest communications unit number of the Temperature Controllers that are connected.
12
Initial Temperature Controller Settings
Section 1-4
1-4 Initial Temperature Controller Settings
The following four methods are provided for setting the EJ1 Temperature Controllers.
Transferring Temperature Controller Parameters Together
Set each of the Temperature Controller parameters in the Edit Device Parameters Window from the DeviceNet Configurator, and then transfer them together via the DeviceNet network.
Configurator
Edit device parameters
Edit Unit parameters
Proportional band
Target value
CS/CJ-series DeviceNet Unit
PLC
Temperature
Controller parameters
DeviceNet
Setting with Explicit
Messages
PLC
DeviceNet
Communications Unit
Set the initial settings from the PLC with the master by sending an explicit message.
CMND
CMND
(1) Execute a STOP command.
(Operation command 30 05, command code 0B, related data FF)
(2) Execute an AUTO command.
(Operation command 30 05, command code 0D, related data FF)
(3) Make initial settings.
(VARIABLE AREA WRITE 01 02, variable type E0 to F2)
DeviceNet
Communications Unit
13
Initial Temperature Controller Settings
Section 1-4
14
SECTION 2
Operating Procedures
This section outlines the basic operating procedures of the EJ1 DeviceNet Communications Unit.
2-2-1 Simple I/O Allocation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-2-2 I/O Allocation Using the Configurator . . . . . . . . . . . . . . . . . . . . . . .
15
Setup Procedure
Section 2-1
2-1 Setup Procedure
Use the following procedure to prepare the DeviceNet Communications Unit for use. Refer to the reference pages provided for detailed information on each step.
1
2
3
4
5
6
7
Step
Connect the DeviceNet Communications Unit and the Temperature
Controllers.
Mount the connected DeviceNet
Communications Unit and the Temperature Controllers to the DIN
Rail.
Connect the RS-485 communications cable (only for distributed placement).
Item
Connect the power supply
Details Reference page
Connect the DeviceNet Communications Unit to the
Temperature Controllers. Attach the seal supplied with the End Unit to the hole on the side of the DeviceNet
Communications Unit.
Mount the joined DeviceNet Communications Unit and the Temperature Controllers to the DIN Rail. To ensure secure mounting, always attach an End Plate to each end.
When using a multiblock configuration for the Temperature Controllers connected to the DeviceNet Communications Unit, connect the RS-485 communications cable to port B on the End Unit for each block.
Connect a 24-VDC power supply to the power supply terminals of the End Unit.
Note
Do not turn ON the power supply at this time. This power supply is used as the internal circuit power supply of the Temperature Controllers and the communications power supply between the
DeviceNet Communications Unit and the Temperature Controllers.
---
Wire the Temperature Controllers.
Wire the Temperature Controller temperature inputs and control outputs.
Note
Do not turn ON the power supply at this time.
Set the communications unit numbers of the Temperature Controllers.
Set the communications unit number of each Temperature Controllers using the rotary switch and DIP switch on the Temperature Controller. Set a unique communications unit number for each Temperature Controller.
---
---
Set the DeviceNet node address.
Set the DeviceNet node address (0 to 63) of the
DeviceNet Communications Unit. Set the ten’s digit using the
×10 rotary switch, and the one’s digit using the ×1 rotary switch. Set a unique node address for each slave connected to the same master.
16
Startup Procedure
Section 2-2
2-2 Startup Procedure
2-2-1 Simple I/O Allocation
Use this method in the following situations.
• To allocate words in the master only for basic data, such as the set points
(SPs), process values (PVs), and alarm outputs for each Temperature
Controller.
• To use the DeviceNet Communications Unit without a Configurator (when allocating only fixed I/O in the master).
8
9
10
11
12
13
14
Step Item Details Reference page
Set the I/O allocation method.
Set the highest unit number of the connected Temperature Controllers.
Set simple I/O allocation as the method for allocating I/O data in the IN and OUT Areas used by the DeviceNet
Communications Unit. Turn ON pin 1 of the DIP switch.
Set DIP switch pin 2 to the model of the Temperature
Controller connected.
Set the highest communications unit number of the Temperature Controllers connected to the DeviceNet Communications Unit using the rotary switch (Max. No.) of the Unit. This setting will determine the size of the IN and
OUT Areas.
Connect the DeviceNet communications connector to the
DeviceNet Communications Unit.
Connect the DeviceNet communications connectors.
Note
Do not turn ON the communications power supply at this time.
This power supply is also used as the internal circuit power supply of the DeviceNet Communications Unit.
Turn ON the power to the End Unit. Turn ON the power connected to the End Unit.
Note
The Temperature Controllers will start.
---
Turn ON the DeviceNet communications power
(V+, V
−).
Check the indicators on the
DeviceNet Communications Unit.
Operate from the Configurator (if user-set allocation is used at the master).
Note
This also applies if 11 or more TC4 Units are connected.
Turn ON the communications power supply to the
DeviceNet Communications Unit. (See note.)
Note
The DeviceNet Communications Unit will start.
---
Check that the status of each indicator on the DeviceNet
Communications Unit is as follows:
MS: Operating normally when lit green.
NS: Operating normally when lit green. (DeviceNet online or communications connected)
TS: Communicating with Temperature Controllers when lit green.
With the Configurator online, open the master's Edit
Device Parameters Window and allocate the IN and OUT
Areas used by DeviceNet in the master. Click the Master
I/O Allocations Tab, specify the first words for allocation input 1 and allocation output 1, and download the parameters to the master.
Note
When fixed allocations are used, I/O is allocated automatically.
17
Startup Procedure
Section 2-2
15
16
17
Step Item Details Reference page
--Start remote I/O communications.
Enable the master's scan list and change the PLC to
RUN Mode.
Remote I/O communications will start, and the contents of the IN and OUT Areas in the master and DeviceNet
Communications Unit will be synchronized.
Using explicit message communications
Set the initial settings or monitor the Temperature Controller.
Send explicit messages from the master.
Explicit messages can be used to perform control and monitoring that cannot be achieved using the IN and
OUT Areas alone, by sending explicit messages to the
DeviceNet Communications Unit.
With the Configurator online, perform Temperature Controller initial settings or monitoring from the Edit Device
Parameters Window for the DeviceNet Communications
Unit.
Upload the parameters of the Temperature Controller to the
DeviceNet Communications Unit.
When the system has started normally, upload (backup) all the parameters to the DeviceNet Communications
Unit in case of Temperature Controller malfunction. Creating a backup copy of the parameters will allow parameters to be easily reset onsite after a Temperature
Controller has been replaced, without requiring a Configurator.
Procedure: Turn OFF pin 3 of the DIP switch of the
DeviceNet Communications Unit, turn ON pin 6 (1 to
5 s), and then turn it OFF again.
Note When changing the baud rate of the master after starting the DeviceNet Com-
munications Unit, turn ON the communications power supply of the DeviceNet
Communications Unit again, and restart the Unit.
2-2-2 I/O Allocation Using the Configurator
Use this method for any of the following situations.
• To select any parameters (such as PID constants) or status information, apart from the Temperature Controller set points (SPs), process values
(PVs), or alarm outputs, and allocate words for them in the master (up to
100 words each in the IN Area and OUT Area).
• To allocate data in any order.
• To use remote I/O communications to allocate only data that is always required in the master and not allocate unnecessary data.
Note Up to 100 words each can be allocated in the IN Area and OUT Area for
remote I/O communications. To read and write larger amounts of data, use the following procedure.
• Use expansion remote I/O.
• Use explicit message communications. Also write data using explicit message communications for data that is written only when required.
• Use multiple DeviceNet Communications Units and distribute the number of Temperature Controllers connected to each DeviceNet Communications Unit.
18
Startup Procedure
Section 2-2
8
9
10
11
12
13
Step Item
Set the method for allocating I/O.
Details Reference page
Set to the Configurator as the method for allocating I/O data in the IN and OUT Areas used by the DeviceNet
Communications Unit. Turn OFF pin 1 of the DIP switch of the Unit.
Connect the DeviceNet communications connector to the
DeviceNet Communications Unit.
Connect the DeviceNet communications connector.
Note
Do not turn ON the communications power at this time.
This power supply is also used as the internal circuit power supply of the DeviceNet Communications Unit.
Turn ON the power to the End Unit. Turn ON the power supply connected to the End Unit.
Note
The Temperature Controller will start.
Turn ON the DeviceNet communications power supply (+V,
−V)
Turn ON the communications power supply to the
DeviceNet Communications Unit. (See note.)
Note
The DeviceNet Communications Unit will start.
Check the indicators on the
DeviceNet Communications Unit.
---
---
Check that the status of each indicator on the DeviceNet
Communications Unit is as follows:
MS: Operating normally when lit green. (When the power is turned ON for the first time when allocating I/O from the Configurator, the connection configuration of the Temperature Controllers will not be registered, so the indicator will flash green.)
NS: Operating normally when lit green. (DeviceNet online or communications connected.)
Operate from the Configurator.
TS: Not lit.
(1) With the Configurator online, register the connection configuration of the Temperature Controllers in the Edit Device Parameters Window for the
DeviceNet Communications Unit.
(2) Use the following method to allocate I/O in the IN and OUT Areas from the Parameters Window for the DeviceNet Communications Unit.
a. Select the data to be allocated from the available allocation data.
b. With the Configurator online, download the data to the DeviceNet Communications Unit.
(3) To divide the IN Area used by the DeviceNet Communications Unit into two blocks, select the
DeviceNet Communications Unit in the Edit Device
Parameters Window for the master, and click
Advanced to set the connections.
Dividing the IN Area into two blocks allows, for example, RUN parameters such as set points (SP) and process values (PV) to be allocated as DM words in IN Area 1 and status information to be allocated as CIO words in IN Area 2.
(4) When using the Configurator to allocate user-set
I/O, allocate the IN and OUT Areas used by
DeviceNet in the master from the Edit Device
Parameters Window for the master. Click the Master I/O Allocations Tab, specify the first words of the
IN Area 1, IN Area 2, and OUT Area 1, and download the parameters to the master.
Note
When fixed allocations are used, I/O is allocated automatically.
19
Startup Procedure
Section 2-2
14
Step
15
16
Item Details Reference page
--Start remote I/O communications.
Enable the master's scan list and change the PLC to
RUN Mode.
Remote I/O communications will start, and the contents of the IN and OUT Areas in the master and DeviceNet
Communications Unit will be synchronized.
When using explicit message communications
Set the initial settings or monitor the Temperature Controller.
Send explicit messages from the master.
Explicit messages can be used to perform control and monitoring that cannot be achieved using the IN and
OUT Areas alone by sending explicit messages to the
DeviceNet Communications Unit.
With the Configurator online, execute Temperature Controller operation commands or perform monitoring from the Edit Device Parameters Window for the DeviceNet
Communications Unit.
Upload the Temperature Controller parameters to the DeviceNet Communications Unit.
When the system has started normally, upload (backup) all the parameters to the DeviceNet Communications
Unit in case of Temperature Controller malfunction. This will allow parameters to be easily reset onsite without using a Configurator after replacing a Temperature Controller.
Procedure: Turn OFF pin 3 of the DIP switch on the front panel of the DeviceNet Communications Unit, turn ON pin 6 (1 to 5 s), and then turn it OFF again.
Note When changing the baud rate of the master after starting the DeviceNet Com-
munications Unit, turn ON the communications power supply of the DeviceNet
Communications Unit again, and restart the Unit.
20
SECTION 3
Parts, Installation, and Wiring
This section describes the methods used to install and wire the EJ1 DeviceNet Communications Unit and the EJ1
Temperature Controller. The settings of DeviceNet Communications Unit switches are also described.
3-2-1 Installing the DeviceNet Communications Unit and
Temperature Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-2-2 Mounting to DIN Rail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-3 DeviceNet Communications Cables Wiring . . . . . . . . . . . . . . . . . . . . . . . . . .
3-3-1 Preparing DeviceNet Communications Cables. . . . . . . . . . . . . . . . .
3-3-2 Attaching the DeviceNet Communications Unit Connector. . . . . . .
21
Part Names and Functions
3-1 Part Names and Functions
3-1-1 Part Names
Node Address
Set the node address for the
DeviceNet slave.
Highest Communications Unit Number
When using simple I/O allocation, set the highest communication unit number that is used by the connected Temperature Controllers.
Setting DIP Switches
DIP Switches
6 (COPY)
5
4 (EDS)
3 (UP/DN)
Descriptions
Executes UpLoad/DownLoad
OFF
→
ON (For 1 to 5 sec)
→
OFF
Not in use
OFF OMRON Configurator is used.
ON Other manufacturer's configurator is used.
OFF UpLoad (from Temperature Controller to EJ1-DRT)
ON DownLoad (from EJ1-DRT to Temperature Controller)
OFF Simple assignment of I/O for TC2
2 (TC2/4)
---
---
1 (MODE)
ON Simple assignment of I/O for TC4
OFF Simple assignment of I/O given by Configurator
ON Simple assignment of I/O
Section 3-1
Front Panel
10
NODE
ADR
1
1
2
3
9 8 7 6
4
1
2
3
9 8 7 6
4
MAX
No.
EJ1N
DRT
MS
EF
01
23
C
4567
ABD
NS
TS
COPY
NO
EDS
UP/DN
TC2/4
MODE
Indicators
DeviceNet Communications Connector
This connector connects the DeviceNet network communications cable.
The DeviceNet communications power is also supplied through this connector.
The required FCK2.5/5-STF-5.08AU connector
(Phoenix Contact) is provided with the Unit.
External Dimensions
20
82.2
65
(Unit: mm)
22
Part Names and Functions
3-1-2 Indicators
Section 3-1
The indicators show the status of the DeviceNet Communications Unit, the
DeviceNet Network, and the status of communications with the Temperature
Controllers.
Indicator
MS
NS
Module status
Name
Network status
(DeviceNet)
Color Status
Green ON
Red
Flashing
ON
Meaning (main errors)
The Unit condition is normal. (DeviceNet
Communications Unit is normal.)
The Unit is not set (when I/O allocation is set from the Configurator).
• The connection configuration has not been set.
• I/O allocations have not been set.
Fatal error
• Watchdog timer error
• RAM error
Flashing
---
Green ON
Red
---
OFF
Flashing
ON
Flashing
OFF
Non-fatal error
• EEPROM sum error
• EEPROM hardware error
No power is being supplied.
• Power is not being supplied to the
DeviceNet Communications Unit.
• The Unit is being reset.
• Waiting for initialization to start.
Online/communications established (normal network status)
Online/communications established (waiting for communications to be established with master)
Fatal communications error (The Unit has detected an error that does not allow communications through the network.)
• Node address duplication error
• Bus Off error detected
Non-fatal communications error
• Communications timeout
Offline or power supply is OFF
• Waiting for completion of the master's node address duplication check.
• Power is not being supplied to the
DeviceNet Communications Unit.
23
Part Names and Functions
Section 3-1
Indicator
TS
Name
Temperature Controller communications status
Color Status
Green ON
Meaning (main errors)
Communicating with the Temperature
Controllers
The copy operation is being performed.
Flashing
Red Flashing
--OFF
• Communications error with a Temperature Controller (a communications error has occurred with at least one of the
Temperature Controllers registered in the
DeviceNet Communications Unit)
• The copy operation failed. (Flashes for
10 s, then returns to prior status.)
• Waiting to communicate with Temperature Controllers (until communications start after the power supply is turned ON or the Unit is reset.)
• The Power is OFF.
• The connection configuration has not been set.
Normal Indicator
Display
The MS, NS, and TS indicators are all lit green when the status of all Units and the Network are normal.
3-1-3 Switch Settings
Note The DeviceNet Communications Unit automatically detects and matches the
baud rate of the master, so the baud rate does not require setting.
Front Rotary Switches
Use these switches to set the node address as a slave in the DeviceNet network between 00 and 63 (node addresses 64 to 99 cannot be used).
Set the ten's digit with the upper rotary switch, and the one's digit with the lower rotary switch.
Any node address within the specified range can be set, as long as each node in the Network (master, slaves, Configurator) has a different node address.
×10
NODE
ADR
×1
9
1
2 3 4
6
78
9
1
2 3 4
78
6
DeviceNet node address setting
Note
1.
Always turn OFF the DeviceNet communications power supply and EDU power supply before setting the Unit.
2.
The factory setting is 00.
3.
If two or more nodes are set with the same node address, a node address duplication will occur and the nodes will not be able to participate in communications.
Copy Function
The DeviceNet Communications Unit can read and save the parameters of the connected Temperature Controllers, allowing the parameters to be copied to the Temperature Controllers when required.
24
Part Names and Functions
Section 3-1
Use the following procedure to operate the front panel DIP switch and perform
copy operations. For details on the copy mode, refer to Reading/Writing Tem-
perature Controller Settings Using Copy Mode in 8-2-3 Replacing Units.
COPY
Starts the copy operation.
UP/DN
Sets copy mode.
NO
Copy Mode Setting (Pin 3)
Copy Start (Pin 6)
Specify the copy mode operation according to the following table.
Pin 3
OFF
ON
Copy mode operation setting
Upload (from Temperature Controller to DeviceNet Communications Unit)
Download (from DeviceNet Communications Unit to Temperature Controller)
Note Pins 3 and 6 of the DIP switch are OFF as the factory setting.
The copy operation is performed according to the copy mode set using pin 3, by operating this pin as follows:
OFF
→ ON (1 s min., 5 s max.) → OFF
Note Pins 3 and 6 of the DIP switch are OFF as the factory setting.
I/O Allocations
I/O Allocation Setting
Switch (DIP Switch Pin 1)
TC2/4
MODE
Model setting
I/O allocation setting
NO
The Temperature Controller connection configuration and I/O allocations can be set using simple I/O allocations or I/O allocations from the Configurator.
DIP switch pin 1
OFF
ON
I/O allocation setting switch
Setting I/O Allocation from the Configurator.
Use the Configurator to set the DeviceNet Communications
Unit connection configuration and I/O allocation. The settings are saved in the non-volatile memory in the DeviceNet Communications Unit, so the same settings can be used once they have been made. (By default, the connection configuration and I/O allocation are not set.)
Simple I/O Allocation Setting
Connection configuration is made and I/O allocation is automatically performed according to the settings made on the highest communications unit number switch (rotary switch) and the model switch (DIP switch pin 2).
With the simple I/O allocation setting, the system checks the communications status of Temperature Controllers up to the communications unit number set as the highest communications unit number when the DeviceNet Communications Unit is started. (Power must also be supplied to the End Unit). As a result, the Temperature Controllers with which communications can be performed normally are registered to the connection configuration. Also, input and output areas are obtained for Temperature Controllers up to the highest communications unit number.
25
Part Names and Functions
Section 3-1
For details on setting I/O allocations from the Configurator and simple I/O allocations,
refer to SECTION 4 Remote I/O Communications.
Model Setting (DIP Switch
Pin 2)
Note
Set the model of the Temperature Controllers to be connected to the
DeviceNet Communications Unit. This setting is enabled if DIP switch pin 1 is set to ON (simple I/O allocations).
Model setting DIP switch pin 2
OFF
ON
TC2 connected.
TC4 connected.
1.
Refer to page 64 and page 68 for information on data allocations when
both TC2 and TC4 Units are connected to a DeviceNet Communications
Unit.
2.
Always turn OFF the DeviceNet communications power supply and turn
OFF the End Unit power supply before making this setting.
3.
When DIP switch pin 1 is set to OFF (I/O allocations with Configurator), the
MS indicator will flash green if the connection configuration is not registered. When the connection configuration is set from the Configurator, the
DeviceNet Communications Unit will automatically be reset, and after starting normally, the MS indicator will be lit green.
4.
By default, DIP switch pins 1 and 2 are set to OFF.
Setting the Highest
Communications Unit
Number
MAX
No.
EF
01
23
4567
ABD
C
Highest communications unit number
Note
Use this switch to set the highest communications unit number (0 to F: 0 to 15 decimal) of the connected Temperature Controllers. This setting is enabled only when DIP switch pin 1 is set to ON (simple I/O allocations). Set the communications unit numbers on the other Temperature Controllers using the following settings 0 to F (0 to 15 decimal).
■ Setting Communications Unit Number Switch for Temperature Controllers
1
SW2
2 0 1 2 3 4 5 6
SW1
7 8 9 A B C D E F
OFF OFF 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15
1.
Refer to the EJ1 Modular Temperature Controllers User’s Manual (Cat. No.
H142
) for details.
2.
Always turn OFF the DeviceNet communications power supply and turn
OFF the End Unit power supply before making this setting.
3.
Always set the communications unit number for each Temperature Controller to between 0 and F (0 and 15 decimal).
4.
If simple I/O allocations are used, do not use a Temperature Controller that has a communications number higher than the highest communications number set here.
5.
I/O data is also allocated automatically according to this setting.
6.
The default setting is 1.
26
Installation
Setting the Support
Software
Section 3-2
EDS
Support Software switch
NO
Use this pin to select the Support Software to be used.
DIP switch pin 4
OFF
ON
Details
Use the OMRON Configurator.
Use another company’s configurator.
Other Settings
Reserved for system use (always OFF)
NO
DIP switch pin 5 is reserved for the system. Keep it set to OFF.
3-2 Installation
Connect the Temperature Controllers to the right side of the DeviceNet Communications Unit. If distributed placement is used, connect the End Units of each block to each other using communications cables.
Up to 16 Temperature Controllers can be connected to a single DeviceNet
Communications Unit.
Note Do not connect DeviceNet Communications Units to communications cables
or disconnect them from the cables while the DeviceNet Network is operating.
Abnormal communications may result from short-circuited DeviceNet cables, loose contacts, or from changing the location of terminating resistance
(DeviceNet) due to changes in the node configuration.
27
Installation
Section 3-2
3-2-1 Installing the DeviceNet Communications Unit and Temperature
Controllers
1,2,3...
1.
Align the connectors and connect the Units to each other.
DeviceNet Communications Unit
Temperature Controller
EDU
Connect the End Unit to the right end and connect the DeviceNet Communications Unit to the left end.
2.
Slide the yellow sliders on the top and bottom of the Units until they click into place.
Slider
Lock
3.
Attach the cover seal to the connector on the Unit on the left end of the
EJ1.
Seal
3-2-2 Mounting to DIN Rail
Mounting Bracket
Mount the DeviceNet Communications Unit and Temperature Controllers to the DIN Rail.
Use screws to attach the DIN Rail to the control panel in at least three places.
28
Installation
PFP-50N (50 cm)/PFP-100N (100 cm) DIN Rail
Section 3-2
PFP-M End Plates (
×2)
Mounting Direction
The mounting direction of the Temperature Controllers is fixed. Position the
DIN Rail vertical to the ground, as shown in the following diagram.
Mounting the Unit
Vertical: OK Horizontal: NG
Pull down the hooks on the bottoms of the Units, and then catch the hooks on the tops of the Units onto the DIN Rail and press the Units onto the DIN Rail until they lock into place.
2. Catch the upper hooks onto the DIN Rail.
3. Press in on the Units.
1. Pull down the hooks.
4. Make sure the Units are locked into place.
29
DeviceNet Communications Cables Wiring
Removing the Unit
Section 3-3
Use a flat-blade screwdriver to pull down the DIN Rail mounting hooks, and then lift up the Units.
Flat-blade screwdriver
(unit: mm)
Mounting End Plates
Flat-blade screwdriver
Always mount end plates to both ends to keep the Units connected together.
Hook the bottom of the end plate onto the DIN Rail (1), hook the top, and then pull down (2). Secure the end plate screws.
2
1
10
NODE
ADR
1
1
2 3
1
2 3
MAX
No.
EJ1N
DRT
MS
NS
23 5678
TS
COPY
NO
EDS
UP/DN
TC2/4
MODE
Note Always use two End Plates to clamp the Units together from both ends.
3-3 DeviceNet Communications Cables Wiring
The methods for preparing DeviceNet communications cables connected to the DeviceNet Communications Unit, and attaching communications connectors are explained here.
For details on supplying the DeviceNet communications power and grounding the DeviceNet Network, refer to the DeviceNet Operation Manual (Cat. No.
W267).
3-3-1 Preparing DeviceNet Communications Cables
Use the following procedure to prepare and connect the communications cables to the connectors.
1,2,3...
1.
Remove about 30 to 80 mm of the cable covering, being careful not to damage the shield mesh underneath. Do not remove too much covering or a
30
DeviceNet Communications Cables Wiring
short circuit may result.
Approx. 30 to 80 mm
(Remove as little as possible.)
Section 3-3
2.
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
3.
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 proper length for the crimp terminals. Twist together the wires of each of the signal and power lines.
Strip to match the crimp terminals.
4.
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 Communications Unit is equipped with screwless connectors, so the cables do not need to be secured with screws as with previous
DeviceNet communications connectors. With the orange tab pushed down, insert each of the lines into the back of the holes.
Release the orange tab and gently tug on each line to check that it is connected properly.
Red (+V)
White (CAN high)
Shield
Blue (CAN low)
Black (
−V)
31
DeviceNet Communications Cables Wiring
Section 3-3
Colored stickers that match the colors of the lines to be inserted are provided on the Master Unit and slaves. Use these stickers to check that the lines are wired correctly. The colors correspond to the signal lines as follows:
Red
White
Color
---
Blue
Black
Signal
Power line, positive voltage (+V)
Communications line, high (CAN high)
Shield
Communications line, low (CAN low)
Communications cable, negative voltage (
−V)
• We recommend the following crimp terminals.
Phoenix Contact AI-series Crimp Terminals: AI-0.5-8WH-B (product code
3201369)
Crimp terminal Line
Insert the line and crimp.
The following crimp tool is also available.
Phoenix Contact ZA3 Crimp Tool
Note For the DeviceNet power supply, always use an EN/IEC-approved power supply with reinforced or double insulation.
3-3-2 Attaching the DeviceNet Communications Unit Connector
Align the DeviceNet Communications Unit connector with the cable connector, and insert the cable connector fully into the DeviceNet Communications Unit connector.
Tighten the set screws to a torque between 0.25 and 0.30 N·m to secure the connector.
10
NODE
ADR
1
1
2 3
1
2 3
MAX
No.
EJ1N
DRT
MS
NS
23 5678
TS
COPY
NO
EDS
UP/DN
TC2/4
MODE
32
Wiring the Temperature Controllers
Section 3-4
• 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 using 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
Phoenix Contact
Model: AI-TWIN2
×0.5-8WH (product code
3200933)
Crimp tool
Phoenix Contact
Model: UD6 (product code 1204436)
3-4 Wiring the Temperature Controllers
For information on wiring the Temperature Controllers, refer to the EJ1 Modu-
lar Temperature Controllers User’s Manual (Cat. No.
H142
).
Insert a noise filter (MXB-1206-33 manufactured by Densei-Lamda or equivalent product) on the End Unit power supply line within 25 cm of the Unit in order to satisfy standards for EN 61326 Class A noise terminal voltage and electromagnetic radiation interference.
33
Wiring the Temperature Controllers
Section 3-4
34
SECTION 4
Remote I/O Communications
This section describes the IN Area and OUT Area that a EJ1 DeviceNet Communications Unit can use for remote I/O communications. The methods to allocate data for master communications are also described.
4-1-2 Allocation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-2-1 Setting Allocation Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-2-2 Simple I/O Allocation Area Configuration. . . . . . . . . . . . . . . . . . . .
4-2-3 Allocating Data in the Master. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-3-1 Setting Allocation Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-3-2 Creating Allocation Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-3-3 Parameters for Which Allocation Is Possible . . . . . . . . . . . . . . . . . .
4-3-5 Output Data Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-4-1 What Is Expansion Remote I/O? . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-4-2 Procedure for Reading Parameters . . . . . . . . . . . . . . . . . . . . . . . . . .
4-4-3 Procedure for Writing Parameters . . . . . . . . . . . . . . . . . . . . . . . . . .
4-5-2 User-set Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-6-1 RUN/STOP Programming Examples . . . . . . . . . . . . . . . . . . . . . . . .
4-6-2 Change SP Programming Example . . . . . . . . . . . . . . . . . . . . . . . . .
4-6-3 Change MV Upper Limit/Lower Limit Programming Example . . .
35
Allocation Method Overview
Section 4-1
4-1 Allocation Method Overview
This section provides an overview of allocation methods for performing remote I/O communications from the master through the DeviceNet Communications Unit.
4-1-1 Overview
The DeviceNet Communications Unit can be used to allocate I/O memory in the master to the following Temperature Controller parameters.
• Operation command/status parameters
• Monitor parameters
• Parameters that can be changed during operation
The DeviceNet Communications Unit can be used to select data from the
Temperature Controllers and DeviceNet Communications Unit and specify the words to allocate to that data.
Data is automatically exchanged between the master and DeviceNet Communications Unit, allowing Temperature Controllers to be controlled and monitored from the master without requiring special communications programming.
DeviceNet Master
CPU Unit
Master CPU Unit I/O memory
IN Area
Process values, etc.
DeviceNet
OUT Area
Set points, etc.
DeviceNet
Communications
Temperature
Controllers
Unit
0
Unit
1
---
Allocated data
IN Area
Process values, etc.
OUT Area
Set points, etc.
Use either of the following two methods to allocate DeviceNet Communications Unit I/O in the master.
36
Allocation Method Overview
1. Simple I/O
Allocation
Section 4-1
I/O can be allocated simply by setting the highest communications unit number of Temperature Controllers connected to the DeviceNet Communications
Unit using the rotary switch. Basic data only, such as Temperature Controller set points (SPs) and process values (PVs), will be allocated consistently and automatically in unit number/channel order according to the configuration of connected Temperature Controllers.
DeviceNet Master
Specify allocation destination
Data is allocated in the master using fixed or user-set allocations.
DeviceNet
DeviceNet
Communications
Unit
Automatic allocation from connection configuration
Unit
0
Unit
1
---
Allocation data
IN Area
Unit 1,ch1 PV
Unit 1,ch2 PV
:
Continues in
Unit/ch order.
OUT Area
Unit 1, ch1 SP
Unit 1, ch2 SP
:
Continues in
Unit/ch order.
Select data for allocation
Note: The above allocation data is automatically allocated according to the connection configuration.
37
Allocation Method Overview
2. User-set
Allocations from the
Configurator
Section 4-1
The Configurator can be used to edit the device parameters and select any data from the list of allocation parameters for the Temperature Controller and
DeviceNet Communications Unit, and then allocate the data in a user-set destination.
DeviceNet Configurator
(Ver. 2.44 or higher) or
CX-Integrator (Ver. 2.2 or higher)
DeviceNet Master
Destination
Data is allocated the master using fixed or user-set allocations.
DeviceNet
DeviceNet
Communications
Unit
Unit
0
Unit
1
---
Available allocation data
:
:
Unit 1, ch1 PV
Unit 1, ch1 SP
Unit 2, ch1 proportional band
Unit 2, ch1 integral time
Select and allocate
Allocation data
IN Area
:
:
Unit 1, ch1 PV
OUT Area
Unit 1, ch1 SP
Unit 2, ch2 proportional band
:
Data for allocation
Note: Create the above allocation data using the
Configurator's Edit Device Parameters and then download to the DeviceNet Communications Unit.
38
Allocation Method Overview
Section 4-1
4-1-2 Allocation Procedure
Follow the two steps below to allocate I/O for remote communications between the master and DeviceNet Communications Unit.
Step 1: Set the Slaves
Set in the DeviceNet Communications Unit which Temperature Controller data or DeviceNet Communications Unit data to allocate in the Master. Use either of the following two methods (1 or 2) to set the data allocation method.
Contents Applications Method for setting allocation data
1) Simple I/O allocation
ON
DIP switch pin 1
2) I/O allocations from the Configurator
OFF
The predetermined set of parameters is automatically set.
The Configurator is used to select any data for allocating in the master from the list of parameters.
Used to allocate in the master basic data only, such as the Temperature Controller SPs, PVs, and alarm outputs.
• Used to allocate parameters and statuses in the master other than the Temperature Controller SPs,
PVs, and alarm outputs.
• Used to allocate data in any order.
• Used to allocate in the master only the data that is always required for remote I/O communications, without allocating data that is not required.
• To divide the IN Area into two areas for allocating data (see note 1).
Note
1.
When a CS/CJ-series DeviceNet Unit is used, 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 selected and allocated in each area. (For example, operation data and status data can be separated and allocated into different locations.) To use this function, however, set two connection methods between the master and DeviceNet Communications Unit under User Setup in the Edit Device Parameters Window for the master. For details, refer
to Setting Connections when Dividing IN Area in Two on page 75.
2.
The size of allocated data is determined according to the allocation method used, as shown in the following table.
Setting method
Simple I/O allocation
I/O allocations from the Configurator
Number of allocated blocks
IN Area: 1 block
OUT Area: 1 block
IN Area: 1 or 2 blocks
OUT Area: 1 block
Size of allocated data
• TC2 Selected (DIP switch pin 2 OFF):
IN Area: 16 to 46 words (32 to 92 bytes)
(= 16 + n × 2 words)
OUT Area: 8 to 38 words (16 to 76 bytes)
(= 8 + n × 2 words)
• TC4 Selected (DIP switch pin 2 ON):
IN Area: 26 to 86 words (52 to 172 bytes)
(= 26 + n × 4 words)
OUT Area: 14 to 74 words (28 to 148 bytes)
(= 14 + n × 4 words) n: The value set as the highest communications unit number (0 to F hex: 0 to 15 decimal).
IN Area: 0 to 100 words (0 to 200 bytes)
OUT Area: 0 to 100 words (0 to 200 bytes)
(Depends on the quantity of allocation data selected.)
Step 2: Allocate Data in the Master
Specify the I/O memory of the master (CPU Unit) to allocate for the data determined in step 1. Whether the setting for allocating data in the master is set to simple I/O allocation or allocation from the Configurator, either of the following two methods can be used.
• Fixed allocations
39
Simple I/O Allocation
Section 4-2
• User-set allocations
Procedure Overview
Steps
Step 1 Set the allocation data.
Step 2 Allocate the data in the master.
Simple I/O allocation
• Turn ON pin 1 of the DIP switch.
• Use DIP switch pin 2 to set the model of the Temperature Controller to be connected.
• Set the highest communications unit number.
I/O allocations from the Configurator
Turn OFF pin 1 of the DIP switch.
IN Area: 1 block
OUT Area: 1 block
IN Area: 2 blocks
OUT Area: 1 block
Using the Configurator, create the allocation data in the Edit Device Parameters Window for the DeviceNet Communications Unit.
Fixed allocations
Fixed allocations cannot be used if
11 or more TC4
Units are used.
User-set allocations
Using the Configurator, allocate I/O from the Edit Device Parameters Window for the
Master Unit under I/O
Allocations, or I/O Allo-
cations through Allo-
cated DM words.
---
Fixed allocations
Using the Configurator, set the connections using user definitions in the Edit
Device Parameters Window for the Master Unit.
User-set allocations
Using the Configurator, allocate I/O from the Edit
Device Parameters Window for the Master Unit under I/O Allocations, or
I/O Allocations through
Allocated DM words.
Note The sizes of slave I/O data allocated in the master is listed below. Allocate I/O
correctly within the maximum allocation sizes.
DeviceNet Communications Unit allocation sizes:
IN Area: Up to 200 bytes (100 words)
OUT Area: Up to 200 bytes (100 words)
CS/CJ-series Master Unit allocation sizes:
IN Area: Up to 200 bytes (100 words)
OUT Area: Up to 200 bytes (100 words)
CVM1/CV-series, C200H, C200HX/HG/HE Master Unit allocation sizes:
IN Area: Up to 64 bytes (32 words)
OUT Area: Up to 64 bytes (32 words)
4-2 Simple I/O Allocation
4-2-1 Setting Allocation Data
Simple I/O allocation is used to allocate I/O in the master without using a Configurator, and to allocate in the master the Temperature Controller set points
(SP), process values (PV), alarm output status, and other basic data only.
Set simple I/O allocation by turning ON pin 1 of the DIP switch of the
DeviceNet Communications Unit.
Memory is allocated to data, such as SP and SV, in the order of unit numbers and channels of the Temperature Controllers up to the Temperature Controller with the highest communications unit number set on the front of the Unit (MAX
No.). It is assumed that there are no Temperature Controllers with communications unit numbers higher than this value.
• TC2 Selected (DIP switch pin 2 OFF):
IN Area: 16 to 46 words (= 16 + n
× 2 words)
OUT Area: 8 to 38 words (= 8 + n
× 2 words)
40
Simple I/O Allocation
Section 4-2
Note
• TC4 Selected (DIP switch pin 2 ON):
IN Area: 26 to 86 words (= 26 + n
× 4 words)
OUT Area: 14 to 74 words (= 14 + n
× 4 words)
1.
Data that is not included in the allocation data can be controlled and monitored using explicit messages.
2.
When simple I/O allocation is used, the type of data allocated and the allocation order cannot be changed. To add or change types of data, or to specify the allocation order, allocate I/O from the Configurator.
4-2-2 Simple I/O Allocation Area Configuration
The configuration of the IN Area and OUT Areas for simple I/O allocations is shown here for the TC2 and TC4. (The process values (PVs) and set points
(SPs) have the same contents as the PV and SP settings in the Temperature
Controller variable area.)
Simple I/O Allocations with TC2 Selected
(DIP switch pin 2 OFF)
Address
First word + 0 OUT Enable Bit
OUT Area IN Area
(See note 1.) Communications Status ---
First word + 1 Cannot be used.
(See note 1.) Communications Error Status ---
First word + 2 RUN/STOP (TC2: #00
−#07)
(See note 1.) RUN/STOP (TC2: #00
−#07)
(See note 1.)
First word + 3 RUN/STOP (TC2: #08
−#15)
(See note 1.) RUN/STOP (TC2: #08
−#15)
(See note 1.)
First word + 4 AT Execute/Cancel (TC2: #00
−#07) (See note 1.) AT Execute/Cancel (TC2: #00−#07) (See note 1.)
First word + 5 AT Execute/Cancel (TC2: #08
−#15) (See note 1.) AT Execute/Cancel (TC2: #08−#15) (See note 1.)
First word + 6 #0 ch1 Present Bank Set Point (See note 2.) Alarm 1 (TC2: #00
−#07)
(See note 1.)
First word + 7
First word + 8
First word + 9
First word + 10
First word + 11
First word + 12
First word + 13
#0 ch2 Present Bank Set Point
#1 ch1 Present Bank Set Point
#1 ch2 Present Bank Set Point
#2 ch1 Present Bank Set Point
#2 ch2 Present Bank Set Point
#3 ch1 Present Bank Set Point
#3 ch2 Present Bank Set Point
(See note 2.) Alarm 1 (TC2: #08
−#15)
(See note 2.) Alarm 2 (TC2: #00
−#07)
(See note 2.) Alarm 2 (TC2: #08
−#15)
(See note 2.) Alarm 3 (TC2: #00
−#07)
(See note 2.) Alarm 3 (TC2: #08
−#15)
(See note 2.) HB Alarm (TC2: #00
−#07)
(See note 2.) HB Alarm (TC2: #08
−#15)
(See note 1.)
(See note 1.)
(See note 1.)
(See note 1.)
(See note 1.)
(See note 1.)
(See note 1.)
First word + 14 #4 ch1 Present Bank Set Point (See note 2.) #0 ch1 Process Value (See note 2.)
First word + 15 #4 ch2 Present Bank Set Point
First word + 16 #5 ch1 Present Bank Set Point
First word + 17 #5 ch2 Present Bank Set Point
(See note 2.) #0 ch2 Process Value
(See note 2.) #1 ch1 Process Value
(See note 2.) #1 ch2 Process Value
(See note 2.)
(See note 2.)
(See note 2.)
First word + 18 #6 ch1 Present Bank Set Point
First word + 19 #6 ch2 Present Bank Set Point
First word + 20 #7 ch1 Present Bank Set Point
First word + 21 #7 ch2 Present Bank Set Point
First word + 22 #8 ch1 Present Bank Set Point
First word + 23 #8 ch2 Present Bank Set Point
First word + 24 #9 ch1 Present Bank Set Point
First word + 25 #9 ch2 Present Bank Set Point
(See note 2.) #2 ch1 Process Value
(See note 2.) #2 ch2 Process Value
(See note 2.) #3 ch1 Process Value
(See note 2.) #3 ch2 Process Value
(See note 2.) #4 ch1 Process Value
(See note 2.) #4 ch2 Process Value
(See note 2.) #5 ch1 Process Value
(See note 2.) #5 ch2 Process Value
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
First word + 26 #10 ch1 Present Bank Set Point
First word + 27 #10 ch2 Present Bank Set Point
First word + 28 #11 ch1 Present Bank Set Point
First word + 29 #11 ch2 Present Bank Set Point
First word + 30 #12 ch1 Present Bank Set Point
(See note 2.) #6 ch1 Process Value
(See note 2.) #6 ch2 Process Value
(See note 2.) #7 ch1 Process Value
(See note 2.) #7 ch2 Process Value
(See note 2.) #8 ch1 Process Value
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
41
Simple I/O Allocation
Section 4-2
Address OUT Area
First word + 31 #12 ch2 Present Bank Set Point
First word + 32 #13 ch1 Present Bank Set Point
First word + 33 #13 ch2 Present Bank Set Point
First word + 34 #14 ch1 Present Bank Set Point
First word + 35 #14 ch2 Present Bank Set Point
First word + 36 #15 ch1 Present Bank Set Point
First word + 37 #15 ch2 Present Bank Set Point
First word + 38 ---
First word + 39 ---
First word + 40 ---
First word + 41 ---
First word + 42 ---
First word + 43 ---
First word + 44 ---
First word + 45 ---
Note
---
---
---
---
---
---
---
---
(See note 2.) #8 ch2 Process Value
(See note 2.) #9 ch1 Process Value
(See note 2.) #9 ch2 Process Value
IN Area
(See note 2.) #10 ch1 Process Value
(See note 2.) #10 ch2 Process Value
(See note 2.) #11 ch1 Process Value
(See note 2.) #11 ch2 Process Value
#12 ch1 Process Value
#12 ch2 Process Value
#13 ch1 Process Value
#13 ch2 Process Value
#14 ch1 Process Value
#14 ch2 Process Value
#15 ch1 Process Value
#15 ch2 Process Value
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
1.
Individual bits will be enabled only through those allocated to the highest communications unit number.
2.
Words will be allocated only through those for the highest communications unit number.
Example:
If the highest communications unit number is set to 10, then the OUT Area will be the 28 words, i.e., from the first word to the first word + 27.
Simple I/O Allocation with TC4 Selected
(DIP switch pin 2 ON)
Address OUT Area IN Area
First word + 0 OUT Enable Bit --Communications Status (See note 1.)
First word + 1 Cannot be used.
--Communications Error Status (See note 1.)
First word + 2 RUN/STOP (TC4: #00
−#03)
First word + 3 RUN/STOP (TC4: #04
−#07)
(See note 1.) RUN/STOP (TC2: #00
−#03)
(See note 1.) RUN/STOP (TC2: #04
−#07)
(See note 1.)
(See note 1.)
First word + 4 RUN/STOP (TC4: #08
−#11)
First word + 5 RUN/STOP (TC4: #12
−#15)
(See note 1.) RUN/STOP (TC2: #08
−#11)
(See note 1.) RUN/STOP (TC2: #12
−#15)
(See note 1.)
(See note 1.)
First word + 6 AT Execute/Cancel (TC4: #00
−#03) (See note 1.) AT Execute/Cancel (TC4: #00−#03) (See note 1.)
First word + 7 AT Execute/Cancel (TC4: #04
−#07) (See note 1.) AT Execute/Cancel (TC4: #04−#07) (See note 1.)
First word + 8 AT Execute/Cancel (TC4: #08
−#11) (See note 1.) AT Execute/Cancel (TC4: #08−#11) (See note 1.)
First word + 9 AT Execute/Cancel (TC4: #12
−#15) (See note 1.) AT Execute/Cancel (TC4: #12−#15) (See note 1.)
First word + 10
First word + 11
#0 ch1 Present Bank Set Point
#0 ch2 Present Bank Set Point
(See note 2.) Alarm 1 (TC4: #00
−#03)
(See note 2.) Alarm 1 (TC4: #04
−#07)
(See note 1.)
(See note 1.)
First word + 12
First word + 13
First word + 14
First word + 15
#0 ch3 Present Bank Set Point
#0 ch4 Present Bank Set Point
#1 ch1 Present Bank Set Point
#1 ch2 Present Bank Set Point
(See note 2.) Alarm 1 (TC4: #08
−#11)
(See note 2.) Alarm 1 (TC4: #12
−#15)
(See note 2.) Alarm 2 (TC4: #00
−#03)
(See note 2.) Alarm 2 (TC4: #04
−#07)
(See note 1.)
(See note 1.)
(See note 1.)
(See note 1.)
First word + 16
First word + 17
First word + 18
First word + 19
#1 ch3 Present Bank Set Point
#1 ch4 Present Bank Set Point
#2 ch1 Present Bank Set Point
#2 ch2 Present Bank Set Point
(See note 2.) Alarm 2 (TC4: #08
−#11)
(See note 2.) Alarm 2 (TC4: #12
−#15)
(See note 2.) Alarm 3 (TC4: #00
−#03)
(See note 2.) Alarm 3 (TC4: #04
−#07)
(See note 1.)
(See note 1.)
(See note 1.)
(See note 1.)
42
Simple I/O Allocation
Address OUT Area
First word + 20 #2 ch3 Present Bank Set Point
First word + 21 #2 ch4 Present Bank Set Point
First word + 22 #3 ch1 Present Bank Set Point
First word + 23 #3 ch2 Present Bank Set Point
First word + 24 #3 ch3 Present Bank Set Point
First word + 25 #3 ch4 Present Bank Set Point
First word + 26 #4 ch1 Present Bank Set Point
First word + 27 #4 ch2 Present Bank Set Point
First word + 28 #4 ch3 Present Bank Set Point
First word + 29 #4 ch4 Present Bank Set Point
First word + 30 #5 ch1 Present Bank Set Point
First word + 31 #5 ch2 Present Bank Set Point
First word + 32 #5 ch3 Present Bank Set Point
First word + 33 #5 ch4 Present Bank Set Point
First word + 34 #6 ch1 Present Bank Set Point
First word + 35 #6 ch2 Present Bank Set Point
First word + 36 #6 ch3 Present Bank Set Point
First word + 37 #6 ch4 Present Bank Set Point
First word + 38 #7 ch1 Present Bank Set Point
First word + 39 #7 ch2 Present Bank Set Point
First word + 40 #7 ch3 Present Bank Set Point
First word + 41 #7 ch4 Present Bank Set Point
First word + 42 #8 ch1 Present Bank Set Point
First word + 43 #8 ch2 Present Bank Set Point
First word + 44 #8 ch3 Present Bank Set Point
First word + 45 #8 ch4 Present Bank Set Point
First word + 46 #9 ch1 Present Bank Set Point
First word + 47 #9 ch2 Present Bank Set Point
First word + 48 #9 ch3 Present Bank Set Point
First word + 49 #9 ch4 Present Bank Set Point
First word + 50 #10 ch1 Present Bank Set Point
First word + 51 #10 ch2 Present Bank Set Point
First word + 52 #10 ch3 Present Bank Set Point
First word + 53 #10 ch4 Present Bank Set Point
First word + 54 #11 ch1 Present Bank Set Point
First word + 55 #11 ch2 Present Bank Set Point
First word + 56 #11 ch3 Present Bank Set Point
First word + 57 #11 ch4 Present Bank Set Point
First word + 58 #12 ch1 Present Bank Set Point
First word + 59 #12 ch2 Present Bank Set Point
First word + 60 #12 ch3 Present Bank Set Point
First word + 61 #12 ch4 Present Bank Set Point
First word + 62 #13 ch1 Present Bank Set Point
First word + 63 #13 ch2 Present Bank Set Point
First word + 64 #13 ch3 Present Bank Set Point
First word + 65 #13 ch4 Present Bank Set Point
First word + 66 #14 ch1 Present Bank Set Point
First word + 67 #14 ch2 Present Bank Set Point
First word + 68 #14 ch3 Present Bank Set Point
(See note 2.) Alarm 3 (TC4: #08
−#11)
(See note 2.) Alarm 3 (TC4: #12
−#15)
(See note 2.) #0 ch1 Process Value
IN Area
(See note 2.) #0 ch2 Process Value
(See note 2.) #0 ch3 Process Value
(See note 2.) #0 ch4 Process Value
(See note 2.) #1 ch1 Process Value
(See note 2.) #1 ch2 Process Value
(See note 2.) #1 ch3 Process Value
(See note 2.) #1 ch4 Process Value
(See note 2.) #2 ch1 Process Value
(See note 2.) #2 ch2 Process Value
(See note 2.) #2 ch3 Process Value
(See note 2.) #2 ch4 Process Value
(See note 2.) #3 ch1 Process Value
(See note 2.) #3 ch2 Process Value
(See note 2.) #3 ch3 Process Value
(See note 2.) #3 ch4 Process Value
(See note 2.) #4 ch1 Process Value
(See note 2.) #4 ch2 Process Value
(See note 2.) #4 ch3 Process Value
(See note 2.) #4 ch4 Process Value
(See note 2.) #5 ch1 Process Value
(See note 2.) #5 ch2 Process Value
(See note 2.) #5 ch3 Process Value
(See note 2.) #5 ch4 Process Value
(See note 2.) #6 ch1 Process Value
(See note 2.) #6 ch2 Process Value
(See note 2.) #6 ch3 Process Value
(See note 2.) #6 ch4 Process Value
(See note 2.) #7 ch1 Process Value
(See note 2.) #7 ch2 Process Value
(See note 2.) #7 ch3 Process Value
(See note 2.) #7 ch4 Process Value
(See note 2.) #8 ch1 Process Value
(See note 2.) #8 ch2 Process Value
(See note 2.) #8 ch3 Process Value
(See note 2.) #8 ch4 Process Value
(See note 2.) #9 ch1 Process Value
(See note 2.) #9 ch2 Process Value
(See note 2.) #9 ch3 Process Value
(See note 2.) #9 ch4 Process Value
(See note 2.) #10 ch1 Process Value
(See note 2.) #10 ch2 Process Value
(See note 2.) #10 ch3 Process Value
(See note 2.) #10 ch4 Process Value
(See note 2.) #11 ch1 Process Value
(See note 2.) #11 ch2 Process Value
(See note 2.) #11 ch3 Process Value
Section 4-2
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 1.)
(See note 1.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
43
Simple I/O Allocation
Section 4-2
Address OUT Area
First word + 69 #14 ch4 Present Bank Set Point
First word + 70 #15 ch1 Present Bank Set Point
First word + 71 #15 ch2 Present Bank Set Point
First word + 72 #15 ch3 Present Bank Set Point
First word + 73 #15 ch4 Present Bank Set Point
First word + 74 ---
First word + 75 ---
First word + 76 ---
First word + 77 ---
First word + 78 ---
First word + 79 ---
First word + 80 ---
First word + 81 ---
First word + 82 ---
First word + 83 ---
First word + 84 ---
First word + 85 ---
Note
---
---
---
---
---
---
---
---
---
---
IN Area
(See note 2.) #11 ch4 Process Value
(See note 2.) #12 ch1 Process Value
(See note 2.) #12 ch2 Process Value
(See note 2.) #12 ch3 Process Value
(See note 2.) #12 ch4 Process Value
---
---
#13 ch1 Process Value
#13 ch2 Process Value
#13 ch3 Process Value
#13 ch4 Process Value
#14 ch1 Process Value
#14 ch2 Process Value
#14 ch3 Process Value
#14 ch4 Process Value
#15 ch1 Process Value
#15 ch2 Process Value
#15 ch3 Process Value
#15 ch4 Process Value
1.
Individual bits will be enabled only through those allocated to the highest communications unit number.
2.
Words will be allocated only through the highest communications unit number.
Example:
If the highest communications unit number is set to 10, then the IN Area will be the 66 words, i.e., from the first word to the first word + 65.
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
(See note 2.)
4-2-3 Allocating Data in the Master
Data is allocated in the master in the same way as other slaves using either fixed allocations or user-set allocations.
Note The sizes of the IN and OUT Areas allocated to the DeviceNet Communica-
tions Unit are larger than for other slaves, so make sure that the allocated words are within the DeviceNet Area and do not overlap with words used by other slaves.
Fixed Allocations
When fixed allocations are used, the location for allocated data is automatically determined according to the node address of the DeviceNet Communications Unit. Fixed allocations can be set without the Configurator.
With fixed allocations, however, each node address is allocated one word.
Therefore, the node addresses allocated to the DeviceNet Communications
Unit cannot be used by other nodes, as shown below.
TC2
TC4 (See note.)
IN Area
OUT Area
IN Area
OUT Area
Allocated 16 to 46 words, therefore, uses 16 to 46 node addresses.
Allocated 8 to 38 words, therefore, uses 8 to
38 node addresses.
Allocated 26 to 86 words, therefore, uses 26 to 86 node addresses.
Allocated 14 to 74 words, therefore, uses 14 to 74 node addresses.
44
Allocating I/O from the Configurator
User-set Allocations
Note
Section 4-3
Note Fixed allocations cannot be used if 11 or more TC4 Units are used.
Use user-set allocations.
With user-set allocations, the Configurator can be used to allocate I/O to the
DeviceNet Communications Unit in any location of the CPU Unit's I/O memory area.
The configuration of the DeviceNet Communications Unit's allocation data is fixed, so the data can be used by merely allocating it in the master. For actual
allocating methods, refer to 4-5 Allocating Data in the Master.
1.
When performing user-set allocations from a DeviceNet Configurator, use
Ver. 2.44 or higher. When using the CX-Integrator, use Ver. 2.2 or higher.
2.
When using a CS/CJ-series DeviceNet Unit as the master, the location and size of the DeviceNet Area can be specified through the allocated DM Area words, without using the Configurator. For slaves, however, I/O is allocated in the DeviceNet Area in node-address order. For details, refer to the
CS/CJ-series DeviceNet Unit Operation Manual (Cat. No. W380).
4-3 Allocating I/O from the Configurator
4-3-1 Setting Allocation Data
Use the Configurator to allocate data other than the process values and set points (such as PID constants), or to allocate only that data that is required.
Turn OFF pin 1 of the DIP switch of the DeviceNet Communications Unit to enable I/O to be allocated from the Configurator.
Create the allocation data by selecting any data from the list of parameters using the Configurator. Download the allocation data that has been edited using the Configurator to the DeviceNet Communications Unit.
Any allocation size can be set within the following range according to the number of allocation parameters that have been selected.
• IN Area: 0 to 100 words
• OUT Area: 0 to 100 words
Note If too many allocation data parameters are selected, the area available for
other slaves may not be sufficient, or the Network may become overloaded.
Therefore, restrict the data to those parameters that require relatively frequent reading or writing, and use explicit messages to read and write other data.
4-3-2 Creating Allocation Data
Allocation data is specified using the Configurator and then downloaded to the
DeviceNet Communications Unit. Any data can be selected from the list of parameters, and then allocated freely in the IN Area (up to 100 words) and
OUT Area (up to 100 words).
45
Allocating I/O from the Configurator
Section 4-3
When a CS/CJ-series DeviceNet Unit is used, the IN Area can be divided into two separate blocks by using two connection methods. This function is used to allocate IN data in different areas.
Edit device parameters for the DeviceNet
Communications Unit (I/O Allocations Tab)
Parameters
Configurator Unit 1, ch 1 PV
Select and allocate
Allocated Area 1
Unit 1, ch 1 PV
Slave device parameters
(allocation data, etc.)
DIP switch pin 1: OFF
Unit Unit
0 1
---
Note The maximum allocation size for the IN and OUT Areas (100 words) applies to
the DeviceNet Communications Unit, and does not apply to the size of allocations in the Master Unit. For details on allocation sizes in the Master Unit, refer to the operation manual for the Master Unit being used.
Creating Data from the DeviceNet Configurator (Ver. 2.44 or Higher) (or CX-Integrator
Ver. 2.2 or higher)
If problems occur in the connection with the Configurator, change the master settings. Problems will occur if the master's message timeout time is too short or the I/O size allocated in the master is different from that allocated in the
DeviceNet Communications Unit. For details on setting methods, refer to 5-2-
1 Preparing the Configurator Connection.
1,2,3...
1.
Select the DeviceNet Communications Unit in the Network Configuration
Window, and double-click, or right-click and select Parameters and Edit to display the Edit Device Parameters Window.
46
Allocating I/O from the Configurator
2.
Select the General Tab.
Section 4-3
■ Uploading the Real Configuration Online
3.
With the Configurator online, click the Upload Real Configuration Button.
The real configuration will be uploaded, and the configuration of the Temperature Controllers that are currently connected to the DeviceNet Communications Unit and all the parameters for these Temperature Controllers will be read.
Note a) Click the Upload Button to read the connection configuration recorded in the DeviceNet Communications Unit and all the parameters for the Temperature Controllers that are registered in the configuration. The window display will refresh at the same time.
b) Click the Download Button to instantly write all the settings that have been set using the Configurator to the DeviceNet Communications Unit and the Temperature Controllers. The Temperature
Controllers that have been written to will be reset automatically to enable the settings. (The status of the Temperature Controllers will be the same as if the power had been turned OFF and ON again.) c) Click the Compare Button to compare the parameters set from the Configurator with the parameters set in the DeviceNet Communications Unit and in all the Temperature Controllers.
■ Editing the Connection Configuration Offline
Edit the Temperature Controller connection configuration (Unit configuration) in the General Tab Page. Click the Button beside the communications unit number under Unit Configuration, and specify the type of Temperature Controller for the selected communications unit number.
47
Allocating I/O from the Configurator
Section 4-3
Leave the field blank for unit numbers that are not allocated to Temperature
Controller.
Note Click the Set Button to display the Edit Unit Parameters Window and then edit the parameters of the corresponding Temperature
Controller (refer to page 93). Click the Operation Button to display
the Operation Commands for Units Window, and control the corre-
sponding Temperature Controller (refer to page 91).
Click the Copy Button to copy parameters between Temperature
Controllers simply by specifying the copy source and destination.
4.
Create Allocation Data for the OUT Area
Create the allocation data for the OUT Area in the I/O Allocations (OUT)
Tab Page. Select the data to be allocated from the list in the Parameters field (top half of window), and drag the corresponding word to one of the
Allocation Areas (bottom half of window).
Alternatively, select the parameter to be allocated and click the Allocate
Button to display the I/O Allocations Dialog Box. Specify the allocation destination and click the OK Button.
Note a) The number of words from the first word is shown as +
@, where the box indicates the number.
48
Allocating I/O from the Configurator
Section 4-3
b) To delete an allocated parameter, select the parameter in the Allocation Area field, and click the Release Button. To delete all the allocated items, click the Release All Button. The Allocated Area field will become blank.
Icon
(Gray)
(Pink)
Description
Allocation not possible
(parameter for unit number not in configuration or
OUT Enable Bit).
Allocation possible
(parameter for unit number in configuration).
Reserved (for OUT
Enable Bit).
(Green) Parameter for unit number in configuration and not yet assigned.
(Blue) Parameter for unit number not in configuration.
Note a) The first word of the allocation area is for the OUT Enable Bit. This allocation cannot be changed. If any data is assigned to the second word or higher, the OUT Enable Bit will be assigned automatically.
b) Do not assign the same parameter more than once.
c) No processing will be performed for parameters for unit numbers that are not in the configuration.
49
Allocating I/O from the Configurator
Section 4-3
5.
Create Allocation Data for the IN Area
Create the allocation data for the IN Area in the IN Allocations Tab Page.
Select the parameters to be allocated from the list in the Parameters field
(top half of window), and drag to the corresponding word in the Allocation area areas (bottom half of window). Allocations can also be performed using the Allocate Button in the same way as for the OUT Area.
Icon
(Gray)
(Pink)
Description
Allocation not possible
(parameter for unit number not in configuration or
OUT Enable Bit).
Allocation possible
(parameter for unit number in configuration).
Reserved (for OUT
Enable Bit).
(Green) Parameter for unit number in configuration and not yet assigned.
(Blue) Parameter for unit number not in configuration.
Note a) When using a CS/CJ-series DeviceNet Unit as the master, the IN
Area can be divided into two separate areas. When allocating data, drag the parameter to either the IN Area field on the left or right
(Allocation Area 1 or Allocation Area 2). To create these two areas, however, two connections must be defined by the user between the master and DeviceNet Communications Unit on the Edit De-
vice Parameters Window for the master. For details, refer to Set-
ting Connections when Dividing IN Area in Two under 4-5-2 User-
b) Do not assign the same parameter more than once.
c) No processing will be performed for parameters for unit numbers that are not in the configuration.
6.
Return to the General Tab, and click the Download Button. The device parameters (connection configuration, allocation data) will be registered in the DeviceNet Communications Unit.
7.
Always click the OK Button to exit the Edit Device Parameters Window.
50
Allocating I/O from the Configurator
Description of Windows: Edit DeviceNet Parameter WIndow
General Tab Page
Section 4-3
Item
Comment
Network Power Voltage
Unit Conduction
Time Monitor Value
Last Maintenance
Time
Default Setting Button
Unit Configuration
Description
Input a comment for the Temperature Controller.
Input the monitor value for the power supply voltage. Input a value from 11.0 to 25.0 VDC.
Input the monitor value for the unit conduction time (i.e., the time that communications power is supplied).
Use the pull-down menu to specify the last date on which maintenance was performed.
Click the Default Setting Button to initialize all settings in the
DeviceNet Communications Unit to the defaults. The Configurator display, however, will not return to the defaults. Press the
Upload Button to read the settings again.
Note The message monitor timer must be changed to use this
function. Refer to page 107 for details.
Set the models of Temperature Controllers connected to the
DeviceNet Communications Unit.
51
Allocating I/O from the Configurator
Item
Set Buttons
Section 4-3
Description
Click a Set Button to display the Edit Unit Parameters Menu, and then set the Temperature Controller parameters. Doubleclick the parameter name to set a value.
Operation Buttons
Copy Buttons
Click an Operation Button to send an operation command to the Temperature Controller. The Temperature Controller can be controlled in the Operation Commands for Units Window.
For details, refer to 5-2-8 Sending Operation Commands to the
Click a Copy Button to copy parameters form one Temperature Controller to an other. Select the channel number to be copied from and then select the channel of the unit number to be copied to.
52
Upload Button
Upload Real Configuration Button
Download Button
Click the Upload Button to read the DeviceNet Communications Unit settings, registered unit configuration, and Temperature Controller parameter settings.
Click the Upload Real Configuration Button to read the
DeviceNet Communications Unit settings, real unit configuration, and Temperature Controller parameter settings.
Click the Download Button to write the settings in the Configurator to the DeviceNet Communications Unit and Temperature
Controllers.
Allocating I/O from the Configurator
Section 4-3
Item
Compare Button
Reset Button
Description
Click the Compare Button to compare the settings in the Configurator with the settings in the Units.
Click the Reset Button to reset the DeviceNet Communications Unit and the Temperature Controllers (in the same way as when the power is cycled). Temperature Controllers, however, will not be reset during operation.
I/O Allocation (OUT) Tab
Page and I/O Allocation
(IN) Tab Page
Note The I/O Allocation (OUT) Tab Page and I/O Allocation (IN) Tab Page have the
same format.
53
Allocating I/O from the Configurator
Section 4-3
Item Description
Allocate Button Select the parameter and click the Allocate Button. The following I/O Allocation Window will be displayed. Select the allocation area and allocation position.
Unit Allocate Button Select the unit number icon of the Temperature Controller and click the Unit Allocate Button. The Unit I/O Allocation Window will be displayed. Select the parameter to be allocated and the allocation position.
Up Button
Down Button
Copy Button
Moves the selected parameter up.
Moves the selected parameter down.
Copies the selected parameter.
Paste Button Pastes the copied parameter.
Release All Button Clears all allocations.
Release
Default setting Button
Clears the selected parameter.
Returns allocations to the defaults.
Note Individual parameters can be selected by pressing the Ctrl Key while selecting
the parameters. Ranges of parameters can be selected by pressing the Shift
Key while selecting a second parameter.
4-3-3 Parameters for Which Allocation Is Possible
Broadly speaking, there are three types of parameters that can be assigned to memory: operation command and status parameters, monitor parameters, and parameters that can be changed during operation. The numbers given in the tables for monitor parameters and parameters that can be changed during operation are allocation numbers, and are used when operating with expansion remote I/O. For information on how to use each parameter, refer to the
EJ1 Modular Temperature Controllers User’s Manual (Cat. No. H142).
Operation Command and Status
Parameters
These parameters are for write processing, operation commands, reading status, and expansion remote I/O for Temperature Controllers. These parameters are managed by the DeviceNet Communications Unit and are not in the variable area of the Temperature Controllers.
54
Allocating I/O from the Configurator
TC2
Note
Section 4-3
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
Assigned to IN
Area
Yes
Assigned to
OUT Area
No
Yes
Yes
Yes
Yes
Yes
No
No
No
No
Yes
Yes
Yes
No
No
No
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
Yes
Yes
No
No
No
No
No
No
No
No
No
No
No
No
Parameter name
Output Completed Flags
Read Parameter Monitor (See note 2.)
OUT Enable Bit (See note 1.)
Read Parameter (See note 2.)
Write Parameter (See note 2.)
Communications Status
Communications Error Status
Unit Status
Alarm 1 (TC2: #00
−#07)
Alarm 1 (TC2: #08
−#15)
Alarm 2 (TC2: #00
−#07)
Alarm 2 (TC2: #08
−#15)
Alarm 3 (TC2: #00
−#07)
Alarm 3 (TC2: #08
−#15)
HB Alarm (TC2: #00
−#07)
HB Alarm (TC2: #08
−#15)
HS Alarm (TC2: #00
−#07)
HS Alarm (TC2: #08
−#15)
OC Alarm (TC2: #00
−#07)
OC Alarm (TC2: #08
−#15)
Input Error (TC2: #00
−#07)
Input Error (TC2: #08
−#15)
Run/Stop (TC2: #00
−#07)
Run/Stop (TC2: #08
−#15)
AT Execute/Cancel (TC2: #00
−#07)
AT Execute/Cancel (TC2: #08
−#15)
Auto/Manual (TC2: #00
−#07)
Auto/Manual (TC2: #08
−#15)
Software Reset
#0 ch1 Specified Parameters (See note 2.)
#0 ch2 Specified Parameters (See note 2.)
#1 ch1 Specified Parameters (See note 2.)
---
#15 ch2 Specified Parameters (See note 2.)
1.
Always allocate the first word of the OUT Area to the OUT Enable Bit.
2.
These parameters are for expansion remote I/O.
TC4
No
No
Yes
Yes
Allocated in IN
Area
Yes
Yes
No
No
No
Allocated in
OUT Area
Yes
Yes
Yes
No
No
Parameter name
Output Completed Flags
Read Parameter Monitor (See note 2.)
OUT Enable Bit (See note 1.)
Read Parameter (See note 2.)
Write Parameter (See note 2.)
Communications Status
Communications Error Status
55
Allocating I/O from the Configurator
Section 4-3
Monitor Parameters
(TC4 and TC2)
Note
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Allocated in IN
Area
Yes
Yes
Yes
Yes
No
No
Allocated in
OUT Area
No
No
No
Yes
Yes
Yes
No
No
No
No
No
No
No
No
No
No
No
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Parameter name
Unit Status
Alarm 1 (TC4: #00
−#03)
Alarm 1 (TC4: #04
−#07)
Alarm 1 (TC4: #08
−#11)
Alarm 1 (TC4: #12
−#15)
Alarm 2 (TC4: #00
−#03)
Alarm 2 (TC4: #04
−#07)
Alarm 2 (TC4: #08
−#11)
Alarm 2 (TC4: #012
−#15)
Alarm 3 (TC4: #00
−#03)
Alarm 3 (TC4: #04
−#07)
Alarm 3 (TC4: #08
−#011)
Alarm 3 (TC4: #012
−#15)
Input Error (TC4: #00
−#03)
Input Error (TC4: #04
−#07)
Input Error (TC4: #08
−#11)
Input Error (TC4: #12
−#15)
Run/Stop (TC4: #00
−#03)
Run/Stop (TC4: #04
−#07)
Run/Stop (TC4: #08
−#11)
Run/Stop (TC4: #12
−#15)
AT Execute/Cancel (TC4: #00
−#03)
AT Execute/Cancel (TC4: #04
−#07)
AT Execute/Cancel (TC4: #08
−#11)
AT Execute/Cancel (TC4: #12
−#15)
Auto/Manual (TC2: #00
−#03)
Auto/Manual (TC2: #04
−#07)
Auto/Manual (TC2: #08
−#11)
Auto/Manual (TC2: #12
−#15)
Software Reset
#0 ch1 Specified Parameters (See note 2.)
#0 ch2 Specified Parameters (See note 2.)
#0 ch3 Specified Parameters (See note 2.)
#0 ch4 Specified Parameters (See note 2.)
#1 ch1 Specified Parameters (See note 2.)
---
#15 ch4 Specified Parameters (See note 2.)
1.
Always allocate the first word of the OUT Area to the OUT Enable Bit.
2.
These parameters are for expansion remote I/O.
These parameters are for monitoring PV, SP, and other data of the Temperature Controller.
Allocated in IN
Area
Yes
Yes
Allocated in OUT
Area
No
No
Parameter name
Device A Status
Configuration Error A Status
Allocation number for expansion remote
I/O
1 (1 hex)
3 (3 hex)
56
Allocating I/O from the Configurator
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Allocated in IN
Area
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
Allocated in OUT
Area
No
No
No
Parameter name
Configuration Error B Status
Internal Communications Error Status
I/O Error Status
I/O Alarm A Status (See note 1.)
I/O Alarm B Status (See note 1.)
I/O Notification A Status (See note 1.)
Error Channel A Status
Basic Unit/Expand Unit Error
Basic Unit/Expand Unit Alarm
Output Status
Device B Status
No
No
No
No
No
Process Value
Channel Status
Channel Alarm Status
Internal SP
Local SP Monitor
Remote SP Monitor
Bank No. Monitor
MV Monitor (Heating)
MV Monitor (Cooling)
Decimal Point Monitor
Heater Current Value Monitor
(See note 1.)
Leakage Current Value Monitor
(See note 1.)
G3ZA CH1 Control Variable Monitor
G3PW Output Variable Monitor
(See note 2.)
G3ZA CH2 Control Variable Monitor
(See note 2.)
G3ZA CH3 Control Variable Monitor
(See note 2.)
G3ZA CH4 Control Variable Monitor
(See note 2.)
No
No
No
No
No
G3ZA CH5 Control Variable Monitor
(See note 2.)
G3ZA CH6 Control Variable Monitor
(See note 2.)
G3ZA CH7 Control Variable Monitor
(See note 2.)
G3ZA CH8 Control Variable Monitor
(See note 2.)
G3ZA CH1 Status (See note 2.)
G3PW Status
G3ZA CH2 Status (See note 2.)
G3ZA CH3 Status (See note 2.)
G3ZA CH4 Status (See note 2.)
G3ZA CH5 Status (See note 2.)
G3ZA CH6 Status (See note 2.)
68 (44 hex)
69 (45 hex)
70 (46 hex)
71 (47 hex)
72 (48 hex)
73 (49 hex)
74 (4A hex)
75 (4B hex)
76 (4C hex)
77 (4D hex)
78 (4E hex)
79 (4F hex)
80 (50 hex)
Section 4-3
Allocation number for expansion remote
I/O
4 (4 hex)
5 (5 hex)
6 (6 hex)
7 (7 hex)
8 (8 hex)
9 (9 hex)
10 (A hex)
11 (B hex)
12 (C hex)
13 (D hex)
14 (E hex)
15 (F hex)
16 (10 hex)
17 (11 hex)
18 (12 hex)
19 (13 hex)
20 (14 hex)
21 (15 hex)
22 (16 hex)
23 (17 hex)
24 (18 hex)
25 (19 hex)
26 (1A hex)
67 (43 hex)
57
Allocating I/O from the Configurator
Section 4-3
Parameters That Can
Be Changed during
Operation (TC4 and
TC2)
Note
Allocated in IN
Area
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Allocated in OUT
Area
No
No
No
Parameter name
G3ZA CH7 Status (See note 2.)
G3ZA CH8 Status (See note 2.)
G3ZA CH1 Heater ON Current Monitor
G3PW Current Monitor (See note 2.)
No
No
No
No
No
No
No
G3ZA CH2 Heater ON Current Monitor
(See note 2.)
G3ZA CH3 Heater ON Current Monitor
(See note 2.)
G3ZA CH4 Heater ON Current Monitor
(See note 2.)
G3ZA CH1 Heater OFF Current Monitor
(See note 2.)
G3ZA CH2 Heater OFF Current Monitor
(See note 2.)
G3ZA CH3 Heater OFF Current Monitor
(See note 2.)
G3ZA CH4 Heater OFF Current Monitor
(See note 2.)
Allocation number for expansion remote
I/O
81 (51 hex)
82 (52 hex)
83 (53 hex)
84 (54 hex)
85 (55 hex)
86 (56 hex)
87 (57 hex)
88 (58 hex)
89 (59 hex)
90 (5A hex)
1.
Can be used with TC2, but not with TC4.
2.
Monitoring can be performed for up to four G3ZA or G3PW Power Controllers per Temperature Controller. Each channel of the Temperature Controller corresponds to one G3ZA or G3PW Power Controller. (Example: ch1
→
G3ZA1)
These parameters, such as the SP, PID, and alarm values, can be changed during operation of the Temperature Controller.
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Allocated in IN
Area
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Allocated in OUT
Area
Yes
Yes
Parameter name
Present Bank Set Point
Present Bank Proportional Band
Present Bank Integral Time
Present Bank Derivative Time
Present Bank SP Ramp Rise Value
Present Bank SP Ramp Fall Value
Present Bank Manual Reset Value
Present Bank Cooling Coefficient
Present Bank Dead Band
Allocation number for expansion remote
I/O
27 (1B hex)
28 (1C hex)
29 (1D hex)
30 (1E hex)
31 (1F hex)
32 (20 hex)
33 (21 hex)
34 (22 hex)
35 (23 hex)
Present Bank Alarm Value 36 (24 hex)
Present Bank Alarm Upper Limit Value 1 37 (25 hex)
Present Bank Alarm Lower Limit Value 1 38 (26 hex)
Present Bank Alarm Value 2 39 (27 hex)
Present Bank Alarm Upper Limit Value 2 40 (28 hex)
Present Bank Alarm Lower Limit Value 2 41 (29 hex)
Present Bank Alarm Value 3
Input Digital Filter
42 (2A hex)
Present Bank Alarm Upper Limit Value 3 43 (2B hex)
Present Bank Alarm Lower Limit Value 3 44 (2C hex)
45 (2D hex)
58
Allocating I/O from the Configurator
Section 4-3
4-3-4 Input Data
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Allocated in IN
Area
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Allocated in OUT
Area
Yes
Yes
Yes
Yes
Yes
Yes
Input Value for Input Correction
Input Shift 1
Alpha
Parameter name
Input Value 2 for Input Correction
Input Shift 2
MV at PV Error
MV at Stop
MV Upper Limit
MV Lower Limit
Hysteresis (Heating)
Hysteresis (Cooling)
Manual MV
SP Upper Limit
SP Lower Limit
Disturbance Gain
Disturbance Time Constant
Disturbance Rectification Band
Disturbance Judgement Width
Heater Burnout 1 Detection (See note.)
Allocation number for expansion remote
I/O
46 (2Ehex)
47 (2F hex)
48 (30 hex)
49 (31 hex)
50 (32 hex)
51 (33 hex)
52 (34 hex)
53 (35 hex)
54 (36 hex)
55 (37 hex)
56 (38 hex)
57 (39 hex)
58 (3A hex)
59 (3B hex)
60 (3C hex)
61 (3D hex)
62 (3E hex)
63 (3F hex)
64 (40 hex)
HS Alarm 1 (See note.)
Heater Overcurrent 1 Detection
(See note.)
Proportional Band (Cooling, Current
Bank)
Integral Time (Cooling, Current Bank)
65 (41 hex)
66 (42 hex)
91 (5B hex)
92 (5C hex)
Derivative Time (Cooling, Current Bank) 93 (5D hex)
Note Can be used with TC2, but not with TC4.
Input data that is specific to the DeviceNet Communications Unit and that is not allocated in the Temperature Controller variable area is described here.
TC4 and TC2
Output Completed Flags
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Bit
(2) 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (1)
Number
(1)
(2)
Description
ON: Writing to the OUT Area has been completed. (After the OUT
Enable Bit is turned ON, this flag (bit 00) turns ON when writing is completed, even if an error occurs during writing.)
OFF: Writing to OUT Area is stopped. (After the OUT Enable Bit turns
OFF and the OFF status is received, this flag (bit 00) turns OFF. This flag (bit 00) also turns OFF when the power supply is turned OFF.)
ON: An error occurred during writing to the OUT Area. (This flag (bit 15) turns OFF when the Output Enable Bit turns OFF.)
OFF: Writing to the OUT Area has completed normally.
59
Allocating I/O from the Configurator
Section 4-3
Note The word containing the Output Completed Flags will be 0001 hex if writing is ends normally or 8001 hex if writing ends in an error.
Read Parameter Monitor
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Bit
When the Read Parameter is designated for expansion remote I/O, the allocation number set for the Read Parameter is stored here after the specified parameter has been read. The Read Parameter Monitor cannot be used with simple I/O allocations.
Communications Status
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Bit
Unit Unit Unit Unit Unit Unit Unit Unit Unit Unit Unit Unit Unit Unit Unit Unit
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
ON: The DeviceNet Communications Unit is communicating with the Temperature Controller registered in the connection configuration for the specified communication unit number.
OFF: A communications error has occurred in communications with the Temperature Controller registered in the connection configuration, or the communications unit number belongs to a Temperature Controller that is not registered in the connection configuration.
These bit always show the status of communications with the Temperature
Controllers registered in the connection configuration. When a Temperature
Controller with a communications error returns to normal communications, the corresponding bit will automatically turn ON.
Communications Error
Status
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Bit
Unit Unit Unit Unit Unit
15 14 13 12 11
Unit Unit Unit Unit Unit Unit
10 9 8 7 6 5
Unit Unit Unit Unit Unit
4 3 2 1 0
ON: A communications error has occurred in communications with the Temperature Controller registered in the connection configuration for the specified communication unit number.
OFF: The DeviceNet Communications Unit is communicating with the Temperature Controller registered in the connection configuration for the specified communication unit number or the communications unit number belongs to a
Temperature Controller that is not registered in the connection configuration.
These bits always show the status of communications with the Temperature
Controllers registered in the connection configuration. When an error occurs in communications with a Temperature Controller registered in the connection configuration, the corresponding bit will turn ON. The bit will automatically turn
OFF when communications return to normal.
60
Allocating I/O from the Configurator
Section 4-3
Unit Status
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
0 0 0 0 0 0 0 0 0 0 0 0
Bit
Temperature Controller Maintenance Flag
OFF: Within range (less than monitor value for all channels of all Units)
ON: Outside range (monitor value or higher for at least one channel)
Temperature Controller Power Status Flag
OFF: Power is ON
ON: Power is OFF
Network Power Voltage Monitor Error Flag
OFF: Normal (higher than monitor value)
ON: Error (monitor value or lower)
Unit Maintenance Flag
OFF: Within range (less than monitor value)
ON: Outside range (monitor value or higher)
• The Temperature Controller Power Status Flag indicates the status of the power supplied to the End Unit.
• The Communications Power Voltage Monitor Error Flag indicates the status of the power being supplied through the DeviceNet communications
cables. For details, refer to 5-2-4 Setting Network Power Voltage Monitor.
• The Unit Maintenance Flag turns ON when the conduction time for the
DeviceNet Communications Unit exceeds the specified monitor value. For
details, refer to 5-2-5 Setting the Unit Conduction Time Monitor.
• The Temperature Controller Maintenance Flag turns ON when the Unit conduction time or total RUN time of one or more channel of the Temperature Controllers registered in the connection configuration exceeds the
specified monitor value. For details, refer to 5-2-11 Setting Temperature
Controller Monitor Mode and Monitor Values.
TC2
Alarms 1, 2, and 3 and HB,
HS, and OC Alarms
Bit
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Units 00 to 07 Unit 7 Unit 6 Unit 5 Unit 4 Unit 3 Unit 2 Unit 1 Unit 0 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1
Units 08 to 15 Unit 15 Unit 14 Unit 13 Unit 12 Unit 11 Unit 10 Unit 9 Unit 8 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1
ON: There is an alarm and the Temperature Controller is communicating normally.
OFF: There is no alarm and the Temperature Controller is communicating normally, or the communications unit number belongs to a Temperature
Controller that is not communicating normally.
Input Error
Bit
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Units 00 to 07 Unit 7 Unit 6 Unit 5 Unit 4 Unit 3 Unit 1 Unit 1 Unit 0 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1
Units 08 to 15 Unit 15 Unit 14 Unit 13 Unit 12 Unit 11 Unit 10 Unit 9 Unit 8 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1
ON: An input error has occurred and the Temperature Controller is communicating normally.
61
Allocating I/O from the Configurator
Section 4-3
OFF: No input error has occurred and the Temperature Controller is communicating normally, or the communications unit number belongs to a Temperature Controller that is not communicating normally.
RUN/STOP
Bit
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Units 00 to 07 Unit 7 Unit 6 Unit 5 Unit 4 Unit 3 Unit 1 Unit 1 Unit 0 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1
Units 08 to 15 Unit 15 Unit 14 Unit 13 Unit 12 Unit 11 Unit 10 Unit 9 Unit 8 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1
ON: The corresponding Temperature Controller is communicating normally and is running.
OFF: The corresponding Temperature Controller is communicating normally and is stopped, or the communications unit number belongs to a Temperature Controller that is not communicating normally.
AT Execute/Cancel
Bit
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Units 00 to 07 Unit 7 Unit 6 Unit 5 Unit 4 Unit 3 Unit 1 Unit 1 Unit 0 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1
Units 08 to 15 Unit 15 Unit 14 Unit 13 Unit 12 Unit 11 Unit 10 Unit 9 Unit 8 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1
ON: Autotuning is being executed for the corresponding Temperature Controller and the corresponding Temperature Controller is communicating normally.
OFF: Autotuning is stopped for the corresponding Temperature Controller and the corresponding Temperature Controller is communicating normally, or the communications unit number belongs to a Temperature Controller that is not communicating normally.
Auto/Manual
Bit
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Units 00 to 07 Unit 7 Unit 6 Unit 5 Unit 4 Unit 3 Unit 1 Unit 1 Unit 0 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1
Units 08 to 15 Unit 15 Unit 14 Unit 13 Unit 12 Unit 11 Unit 10 Unit 9 Unit 8 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1
ON: The corresponding Temperature Controller is communicating normally and is being operated manually.
OFF: The corresponding Temperature Controller is communicating normally and is being operated automatically, or the communications unit number belongs to a Temperature Controller that is not communicating normally.
62
Allocating I/O from the Configurator
TC4
Alarms 1, 2, and 3
Input Error
Section 4-3
Bit
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Units 0 to 3 Unit 3 Unit 2 Unit 1 Unit 0 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
Units 4 to 7 Unit 7 Unit 6 Unit 5 Unit 4 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
Units 8 to 11 Unit 11 Unit 10 Unit 9 Unit 8 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
Units 12 to
15
Unit 15 Unit 14 Unit 13 Unit 12 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
ON: One of the specified alarms has occurred and the corresponding Temperature Controller is communicating normally.
OFF: The specified alarms have not occurred and the corresponding Temperature Controller is communicating normally, or the communications unit number belongs to a Temperature Controller that is not communicating normally.
Bit
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Units 0 to 3 Unit 3 Unit 2 Unit 1 Unit 0 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
Units 4 to 7 Unit 7 Unit 6 Unit 5 Unit 4 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
Units 8 to 11 Unit 11 Unit 10 Unit 9 Unit 8 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
Units 12 to
15
Unit 15 Unit 14 Unit 13 Unit 12 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
ON: There is an alarm and the Temperature Controller is communicating normally.
OFF: There is no alarm and the Temperature Controller is communicating normally, or the communications unit number belongs to a Temperature
Controller that is not communicating normally.
RUN/STOP
Bit
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Units 0 to 3 Unit 3 Unit 2 Unit 1 Unit 0 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
Units 4 to 7 Unit 7 Unit 6 Unit 5 Unit 4 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
Units 8 to 11 Unit 11 Unit 10 Unit 9 Unit 8 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
Units 12 to
15
Unit 15 Unit 14 Unit 13 Unit 12 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
ON: The corresponding Temperature Controller is communicating normally and is running.
63
Allocating I/O from the Configurator
Section 4-3
OFF: The corresponding Temperature Controller is communicating normally and is stopped, or the communications unit number belongs to a Temperature Controller that is not communicating normally.
AT Execute/Cancel
Bit
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Units 0 to 3 Unit 3 Unit 2 Unit 1 Unit 0 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
Units 4 to 7 Unit 7 Unit 6 Unit 5 Unit 4 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
Units 8 to 11 Unit 11 Unit 10 Unit 9 Unit 8 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
Units 12 to
15
Unit 15 Unit 14 Unit 13 Unit 12 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
ON: Autotuning is being executed for the corresponding Temperature Controller and the corresponding Temperature Controller is communicating normally.
OFF: Autotuning is stopped for the corresponding Temperature Controller and the corresponding Temperature Controller is communicating normally, or the communications unit number belongs to a Temperature Controller that is not communicating normally.
Auto/Manual
Bit
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Units 0 to 3 Unit 3 Unit 2 Unit 1 Unit 0 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
Units 4 to 7 Unit 7 Unit 6 Unit 5 Unit 4 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
Units 8 to 11 Unit 11 Unit 10 Unit 9 Unit 8 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
Units 12 to
15
Unit 15 Unit 14 Unit 13 Unit 12 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
ON: The corresponding Temperature Controller is communicating normally and is being operated manually.
OFF: The corresponding Temperature Controller is communicating normally and is being operated automatically, or the communications unit number belongs to a Temperature Controller that is not communicating normally.
Combining TC2 and
TC4 Units
Simple I/O Allocation
Operation will be as follows if simple I/O allocation is used and both TC2 and
TC4 Units are connected to a DeviceNet Communications Unit or if the Configurator is used to allocate I/O for both TC2 and TC4 Units.
• If a TC4 Unit is used and simple I/O allocation is performed for TC2 Units
(i.e., with DIP switch pin 2 turned OFF), channel 1 and channel 2 data will be used for channel 1 and channel 2 of the TC4 Unit.
• If a TC2 Unit is used and simple I/O allocation is performed for TC4 Units
(i.e., with DIP switch pin 2 turned ON), channel 1 and channel 2 data will be used for channel 1 and channel 2 of the TC2 Unit.
64
Allocating I/O from the Configurator
Section 4-3
Allocating I/O from the
Configurator
TC2 data
TC4 data
If data is allocated for both TC2 and TC4 Units, the data will be allocated according to unit number in each allocated area, regardless of whether the
Units are TC2 or TC4 Units. This may result in the same data in two different places for the same unit numbers for the channels that are available.
Example: The data in the shaded areas of the following table will be used if a
TC2 Unit set as unit 0 and a TC4 Unit set as unit 1 are connected to a DeviceNet Communications Unit.
Unit 7 Unit 6 Unit 5 Unit 4 Unit 3 Unit 2 Unit 1 Unit 0 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1
Unit 3 Unit 2 Unit 1 Unit 0 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
4-3-5 Output Data Details
The output data is divided into the OUT Enable Bit, operation commands, setting data, and expansion remote I/O. This section describes the OUT Enable
Bit and operation commands specific to DeviceNet communications that are not allocated in the variable areas of the Temperature Controller.
Note
1.
The output data will not be valid for Temperature Controllers with which a communications error has occurred, or which have a communications unit number that is not registered in the connection configuration.
2.
Depending on the Temperature Controller status (e.g., RUN/STOP), some data may not be valid even if it is written to the OUT Area. For details, refer to the EJ1 Modular Temperature Controllers User’s Manual (Cat. No.
H142).
3.
Operation commands are executed only after sending the setting data.
The setting data and operation commands are sent or executed in the order that they are allocated in the OUT Area.
TC2 and TC4
OUT Enable Bit
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Bit
Note
Description
0 to not 0: All parameters in the OUT Area are transferred to the Temperature Controller. (They are transferred only once each time the bit changes from 0 to not 0.).
Not 0: Only parameters that are changed in the OUT Area are transferred to the Temperature Controller.
OFF: Parameters in the OUT Area are not transferred to the Temperature Controller.
Note The Output Completed Flags will show the results of processing for the OUT Enable Bit.
The OUT Enable Bit must be changed to a value other than 0 to enable the output data set in the output area. If the OUT Enable Bit is OFF, no data will be transferred to the Temperature Controller even if the output data is written to the OUT Area.
1.
The first word of the OUT Area is allocated to the OUT Enable Bit. If the
Configurator is used to allocate I/O and the second or higher words in the
OUT Area are allocated to parameters, the first word will automatically be allocated for the OUT Enable Bit.
2.
Always change the OUT Enable Bit to 0 when downloading setting parameters to the Temperature Controllers using the Configurator. If the OUT En-
65
Allocating I/O from the Configurator
Section 4-3
able Bit is not changed 0 before downloading data, the set values allocated as I/O and the set values downloaded using the Configurator will compete with each other, causing the set values allocated as I/O to be enabled. For details on downloading set values to the Temperature Controllers using the
Configurator, refer to SECTION 5 Operations from the Configurator.
3.
Even when the OUT Enable Bit is turned OFF, data can be written using explicit messages.
Read Parameter
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Bit
• This parameter is used for expansion remote I/O.
• Allocate the Read Parameter in the OUT Area, and then specify the allocation number of the parameter to be read, e.g., using the ladder pro-
gram. For the allocation numbers, refer to 4-3-3 Parameters for Which
Write Parameter
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Bit
• This parameter is used for expansion remote I/O.
• Allocating the Write Parameter in the OUT Area, and then specify the allocation number of the parameter to be written, e.g., using the ladder pro-
gram. For the allocation numbers, refer to 4-3-3 Parameters for Which
Software Reset
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Bit
Unit Unit Unit Unit Unit
15 14 13 12 11
Unit Unit Unit Unit Unit Unit
10 9 8 7 6 5
Unit Unit Unit Unit Unit
4 3 2 1 0
OFF to ON: Software reset command. (Executed only once when the bit is turned ON.)
ON to OFF: No processing is performed.
TC2
RUN/STOP
Bit
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Units 0 to 7 Unit 7 Unit 6 Unit 5 Unit 4 Unit 3 Unit 1 Unit 1 Unit 0 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1
Units 8 to 15 Unit 15 Unit 14 Unit 13 Unit 12 Unit 11 Unit 10 Unit 9 Unit 8 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1
ON: Run command (starts control). (Executed while the bit is ON.)
OFF: Stop command (stops control). (Executed while the bit is OFF.)
AT Execute/Cancel
Bit
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Units 0 to 7 Unit 7 Unit 6 Unit 5 Unit 4 Unit 3 Unit 1 Unit 1 Unit 0 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1
66
Allocating I/O from the Configurator
Section 4-3
Units 8 to 15 Unit 15 Unit 14 Unit 13 Unit 12 Unit 11 Unit 10 Unit 9 Unit 8 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1
OFF to ON: 100% autotuning execution command. (Executed only once each time the bit is turned ON.)
OFF: Autotuning cancel command (Executed while the bit is OFF.)
Note Always allocate AT Execute/Cancel after RUN/STOP or Auto/Manual. If it is
allocated before, AT execution and RUN or Auto will not be performed at the same time.
Auto/Manual
Bit
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Units 0 to 7 Unit 7 Unit 6 Unit 5 Unit 4 Unit 3 Unit 1 Unit 1 Unit 0 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1
Units 8 to 15 Unit 15 Unit 14 Unit 13 Unit 12 Unit 11 Unit 10 Unit 9 Unit 8 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1
ON: Manual mode command. (Executed while the bit is ON.)
OFF: Auto mode command. (Executed while the bit is OFF.)
TC4
RUN/STOP
Bit
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Units 0 to 3 Unit 3 Unit 2 Unit 1 Unit 0 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
Units 4 to 7 Unit 7 Unit 6 Unit 5 Unit 4 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
Units 8 to 11 Unit 11 Unit 10 Unit 9 Unit 8 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
Units 12 to
15
Unit 15 Unit 14 Unit 13 Unit 12 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
ON: RUN command (starts control). (Executed while the bit is ON.)
OFF: Stop command (stops control). (Executed while the bit is OFF.)
AT Execute/Cancel
Bit
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Units 0 to 3 Unit 3 Unit 2 Unit 1 Unit 0 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
Units 4 to 7 Unit 7 Unit 6 Unit 5 Unit 4 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
Units 8 to 11 Unit 11 Unit 10 Unit 9 Unit 8 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
Units 12 to
15
Unit 15 Unit 14 Unit 13 Unit 12 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
67
Expansion Remote I/O
Section 4-4
OFF to ON: 100% autotuning execution command. (Executed only once each time the bit is turned ON.)
OFF: Autotuning cancel command. (Executed while the bit is OFF.)
Note Always allocate AT Execute/Cancel after RUN/STOP or Auto/Manual. If it is
allocated before, AT execution and RUN or Auto will not be performed at the same time.
Auto/Manual
Bit
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Units 0 to 3 Unit 3 Unit 2 Unit 1 Unit 0 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
Units 4 to 7 Unit 7 Unit 6 Unit 5 Unit 4 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
Units 8 to 11 Unit 11 Unit 10 Unit 9 Unit 8 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
Units 12 to
15
Unit 15 Unit 14 Unit 13 Unit 12 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
ON: Manual mode command. (Executed while the bit is ON.)
OFF: Auto mode command. (Executed while the bit is OFF.)
Combining TC2 and
TC4 Units
Simple I/O Allocation
Operation will be as follows if simple I/O allocation is used and both TC2 and
TC4 Units are connected to a DeviceNet Communications Unit or if the Configurator is used to allocate I/O for both TC2 and TC4 Units.
• If a TC4 Unit is used and simple I/O allocation is performed for TC2 Units
(i.e., with DIP switch pin 2 turned OFF), channel 1 and channel 2 data will be used for channel 1 and channel 2 of the TC4 Unit.
• If a TC2 Unit is used and simple I/O allocation is performed for TC4 Units
(i.e., with DIP switch pin 2 turned ON), channel 1 and channel 2 data will be used for channel 1 and channel 2 of the TC2 Unit.
Allocating I/O from the
Configurator
TC2 data
TC4 data
If data is allocated for both TC2 and TC4 Units, the data will be allocated according to unit number in each allocated area, regardless of whether the
Units are TC2 or TC4 Units. This may result in the same data in two different places for the same unit numbers for the channels that are available.
Example: The data in the shaded areas of the following table will be used if a
TC2 Unit set as unit 0 and a TC4 Unit set as unit 1 are connected to a DeviceNet Communications Unit.
Unit 7 Unit 6 Unit 5 Unit 4 Unit 3 Unit 2 Unit 1 Unit 0 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1 ch2 ch1
Unit 3 Unit 2 Unit 1 Unit 0 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1 ch4 ch3 ch2 ch1
4-4 Expansion Remote I/O
4-4-1 What Is Expansion Remote I/O?
Expansion remote I/O is a function reading and writing parameters. Specific parameters allocated in I/O memory of the master can be switched to a variety of parameters by using memory operations. This function enables manipu-
68
Expansion Remote I/O
Section 4-4
lating more than 100 parameters. Even if the number of parameters to be read and written increases, modifications can be handled simply by changing operations in the memory of the master.
Address
PLC Memory IN Area m+0 m+1 m+2 m+3 m+4 m+5 m+6
Output Completed Flags
Read Parameter Monitor
---
Unit 0, ch1 parameter
Unit 0, ch2 parameter
:
Unit 1, ch1 parameter
Unit 1, ch2 parameter
PLC Memory OUT Area
Address n+0 n+1 n+2 n+3 n+4 n+5 n+6
OUT Enable Bit
Read Parameter
Write Parameter
Unit 0, ch1 parameter
Unit 0, ch2 parameter
:
Unit 1, ch1 parameter
Unit 1, ch2 parameter
The parameter set in the
Read Parameter can be read.
The parameter set in the Write
Parameter can be written.
Note a) The parameters that can be specified are the ones that can be changed during operation.
b) Expansion remote I/O cannot be used with simple I/O allocations.
4-4-2 Procedure for Reading Parameters
This section describes how to read parameters using expansion remote I/O.
Allocating Expansion
Remote I/O
Parameters
Allocate the following parameters in I/O memory by using the Configurator.
For information on allocation methods, refer to 4-3-2 Creating Allocation Data.
Area
OUT Area
IN Area
Parameter
Read Parameter
Description
Used to the allocation number of the parameter to be read. Always allocate memory to this parameter.
Read Parameter Monitor Used to confirm that reading has been completed. Always allocate memory to this parameter.
Parameters for specified unit numbers and channels
The values of the parameters corresponding to the specified allocation number will be set.
Allocate memory for the required unit numbers and channels.
Reading Parameters by Using Memory
Operations
1,2,3...
Note There are no restrictions on the locations for allocations.
Use the following procedure to read parameters by using ladder programming.
1.
Set the Read Parameter to the allocation number of the parameter to be
read. For the allocation numbers, refer to the Allocation number for expan-
sion remote I/O column in the table in 4-3-3 Parameters for Which Alloca-
Example: Allocation number for the set point = 18 (0012 hex)
2.
Check that the allocation number specified in step 1 is set in the Read Parameter Monitor. If the same allocation number is set as in step 1, then the specified parameter has been read normally. FFFF hex will be set in the following cases.
• The Read Parameter is 0 at startup.
• There is no parameter that corresponds to the allocation number.
69
Expansion Remote I/O
Section 4-4
• Communications cannot be performed with the unit number registered in the configuration.
Note No processing will be performed and reading will be completed normally if a parameter is allocated for a unit number that is not registered in the configuration.
3.
Check the parameters that were read. The parameter specified in step 1 will be read for each unit number and channel that has been allocated. If the Read Parameter Monitor is set to FFFF hex, the parameters for individual unit numbers and channels will maintain the previous values.
Set to 0012 hex.
Example:
Address m+0 m+1 m+2 m+3 m+4 m+5 m+6
PLC Memory IN Area
Output Completed Flags
Read Parameter Monitor
---
Unit 0, ch1 parameter
Unit 0, ch2 parameter
Unit 1, ch1 parameter
Unit 1, ch1 parameter
Address n+0 n+1 n+2 n+3 n+4 n+5 n+6
Values read.
PLC Memory OUT Area
OUT Enable Bit
Read Parameter
Write Parameter
Unit 0, ch1 parameter
Unit 0, ch2 parameter
Unit 1, ch1 parameter
Unit 1, ch2 parameter
Set 0012 hex (set point).
Programming
Example for Reading
Parameters
Operation
The program uses CIO 3200 to CIO 3263 as the OUT Area and CIO 3300 to
CIO 3363 as the IN Area for an OMRON CS/CJ-series DeviceNet Unit.
• The set point of a TC2 Unit (unit number 0, ch1) is read.
• The allocation number of the set point (18 (0012 hex)) is set in the Read
Parameter allocated in CIO 3201.
• If reading is completed normally, allocation number of the set point (18
(0012 hex)) is set in the Read Parameter Monitor allocated in CIO 3301.
• The set point is stored in the Unit 0 Ch1 Parameter allocated in CIO 3302 and then the value is transferred to D0100.
Example of Ladder
Programming
000000
0000
Execution condition
0004
0007
000001
=
3301
#0012
MOV(021)
#0012
3201
CIO 3201 (Read Parameter) is set to #0012
(allocation number for set point).
ASL(025)
0000
When CIO 3301 (Read Parameter Monitor) is set to #0012
(allocation number for set point), the content of CIO 0000 is shift one bit to the left (CIO 000001 turns ON).
MOV(021)
3302
D0100
CIO 3302 is set to the set point for channel 1 of unit 0 and this value is transferred to D0100.
ASL(025)
0000
The content of CIO 0000 is shifted one bit to the left
(CIO 000002 turns ON).
END(001)
70
Expansion Remote I/O
Section 4-4
4-4-3 Procedure for Writing Parameters
This section describes how to write parameters using expansion remote I/O.
Allocating Expansion
Remote I/O
Parameters
Allocate memory to the following parameters to I/O by using the Configurator.
For information on allocation methods, refer to 4-3-2 Creating Allocation Data.
Area
OUT Area
IN Area
Parameter
OUT Enable Bit
Write Parameter
Parameters for specified unit numbers and channels
Output Completed Flags
Description
Used to enable writing.
Always allocate the first word of the OUT Area to this parameter.
Used to set the allocation number of the parameter to be written. Always allocate memory to this parameter.
Set the values to write to the parameters corresponding to the specified allocation number. Allocate memory for the required unit numbers and channels.
Used to check that writing has been completed. Always allocate memory to this parameter.
Writing Parameters by
Using Memory
Operations
1,2,3...
Note There are no restrictions on the locations for allocations except for the OUT Enable Bit.
Use the following procedure to write parameters by using ladder programming.
1.
Turn OFF the OUT Enable Bit.
First, always turn OFF the OUT Enable Bit. After the OUT Enable Bit is turned OFF, the word that contains the Output Completed Flags will be
0000 hex.
2.
Check that the word that contains the Output Completed Flags is 0000 hex.
3.
Set the Write Parameter to the allocation number of the parameter to be
written. For the allocation numbers, refer to the Allocation number for ex-
pansion remote I/O column in the table in 4-3-3 Parameters for Which Al-
Example: Allocation number for the set point = 27 (001B hex)
4.
Set the values to write in the parameters for the unit numbers and channels for the allocation number specified in step 3.
5.
Turn ON the OUT Enable Bit. Writing will be performed when this bit turns
ON.
6.
Check that the word containing the OUT Completed Flags is 0001 hex.
If the word is 0001 hex, then writing has been completed normally, and if it is 8001 hex, an error has occurred in writing. If an error occurs, check the following points.
• There are no parameters that corresponds to the allocation number.
• The write value in step 4 is outside the setting range.
• Communications cannot be performed with a unit number registered in the configuration.
71
Expansion Remote I/O
Section 4-4
Note If memory is allocated to the parameter for a unit number that is not registered in the configuration, no processing will be performed, and writing will completed normally.
2. Set to 0000 hex.
6. Set to 0001 hex.
1. Turn OFF.
5. Set value other than 0
(e.g., 0001 hex).
Example:
Address m+0 m+1 m+2 m+3 m+4 m+5 m+6
PLC Memory IN Area
Output Completed Flags
Address n+0
Read Parameter Monitor n+1
---
3. Set 001B hex (set point).
Unit 0, ch1 parameter n+2 n+3
PLC Memory OUT Area
OUT Enable Bit
Read Parameter
Write Parameter
Unit 0, ch1 parameter
Unit 0, ch2 parameter
Unit 1, ch1 parameter n+4 n+5 n+6
Unit 0, ch2 parameter
Unit 1, ch1 parameter
Unit 1, ch2 parameter
(value written as the
set point).
Programming
Example for Writing
Parameters
Operation
Note Always change the OUT Enable Bit to 0 before attempting to write parameters
using expansion remote I/O. If writing is attempted while the bit is not 0, writing may be performed while the allocation number or write values are being set, and unintended values may be written.
The program uses CIO 3200 to CIO 3263 as the OUT Area and CIO 3300 to
CIO 3363 as the IN Area for an OMRON CS/CJ-series DeviceNet Unit.
• The set point of a TC2 Unit (unit number 0, ch1) is written.
• The OUT Enable Bit (bit 320000) to which CIO 3200 is allocated is turned
OFF.
• When bit 00 of the Output Completed Flags, to which CIO 3300 is allocated, is reset, the Write Parameter, to which CIO 3202 is allocated, is set to allocation number 27 (001B hex) to specify the set point, and the unit number and channel parameter, to which CIO 3203 is allocated, is set to
100
°C (0064 hex).
• The OUT Enable Bit is turned ON (CIO 320000).
• Writing is performed. When writing has been completed normally, the word that contains the OUT Enable Bit will be 0001 hex (bit 00 ON, bit 15
OFF).
72
Allocating Data in the Master
Section 4-5
Example of Ladder
Programming
000000
000000
Execution condition
=
3300
#0000
Checking the Output Completed Flags
RSET
320000
CIO 320000 (OUT Enable Bit) is turned OFF.
MOV(021)
#001B
3202
MOV(021)
#0064
3203
ASL(025)
0000
When bit 00 of CIO 3300 (Output Enable Bit) turns
OFF, CIO 3202 (Write Parameter) is set to
001B hex (allocation number for set point), and
CIO 3203 (Unit 0, ch1 set point) is set to
0064 hex (100
°C).
The content of CIO 0000 is shifted one bit to the left.
000001
000006
000010
SET
320000
=
3300
#0001
Checking the Output Completed Flags
ASL(025)
0000
END(001)
CIO 320000 (Output Enable Bit) is turned ON.
When CIO 3300 (OUT Enable Bit) is
0001 hex, the content of CIO 0000 is shifted one bit to the left.
END
4-5 Allocating Data in the Master
The created allocation data can be allocated in the master using fixed or userset allocations.
4-5-1 Fixed Allocations
When fixed allocations are used, the location for allocated data is automatically determined according to the node address of the DeviceNet Communications Unit.
Note
1.
When I/O is allocated from the Configurator, up to 100 words can be allocated in the IN Area and OUT Area, but only up to 64 words can be used for the IN Area and OUT Area if fixed allocations are used (the maximum number of words may be even less depending on the DeviceNet Unit and
PLC being used). Consider the number of words that can be used before allocating data.
2.
When fixed allocations are used, each node address is allocated one word.
The node addresses allocated in the words that are allocated to the DeviceNet Communications Unit cannot be used by other nodes.
4-5-2 User-set Allocations
With user-set allocations, the Configurator can be used to allocate DeviceNet
Communications Unit data anywhere within the specified DeviceNet area.
Note
1.
When performing user-set allocations from a DeviceNet Configurator, use
Ver. 2.44 or higher.
2.
When the IN Area is divided into two blocks, the total number of words that can be used for allocating data in the IN Area is still 100 words.
73
Allocating Data in the Master
Section 4-5
3.
When using a CS/CJ-series DeviceNet Unit as the master, the location and size of the DeviceNet Area can be specified through the allocated DM Area words, without using the Configurator. For slaves, however, I/O is allocated in the DeviceNet Area in node-address order. For details, refer to the
CS/CJ-series DeviceNet Unit Operation Manual (Cat. No. W380).
Allocating Data in the Master
Setting from the DeviceNet Configurator
1,2,3...
1.
Double-click the icon of the Master Unit in the Network Configuration Window, or select Device, Parameters, and Edit to display the Edit Device Parameters Window for the master.
2.
Click the Register Device Button in the master's General Tab Page, and register the DeviceNet Communications Unit. Alternatively, in the Network
Configuration Window, drag and drop the DeviceNet Communications Unit icon in the Master Unit icon to register it. Once registered, the DeviceNet
Communications Unit will be added to the Register Device List field. By registering the DeviceNet Communications Unit, the allocation data created in the slave's Edit Device Parameters Window will be registered in the master.
Register Device Button
3.
Select the I/O Allocation (OUT) and I/O Allocation (IN) Tab, and check that the allocation data created in the Edit Device Parameters Window for the DeviceNet Communications Unit parameters is registered in the master's allocated area (memory block 1 or 2).
74
Allocating Data in the Master
Section 4-5
4.
Click the Edit Button, and edit any of the I/O allocations.
Set where to allocate the master's IN and OUT Areas in the Allocated field.
When the master's IN and OUT Areas consist of two blocks, specify in which block to allocate the data.
5.
Click the OK Button, and return to the master's Edit Device Parameters
Window. The DeviceNet Communications Unit data can be registered anywhere in the memory block fields in the lower half of the window.
6.
Return to the General Tab for the master, click the Download Button, and write the set I/O memory allocations to the master.
Note Always click the OK Button to exit the master's Edit Device Parameters Win-
dow. If the Cancel Button or Button are pressed, the setting contents will be invalid.
Setting Connections when Dividing IN Area in Two
When a CS/CJ-series DeviceNet Unit is used as the master, the IN Area can be divided into two areas by setting connections. This function is enabled by setting two connection types at the same time for a single DeviceNet Communications Unit using the user-defined settings.
When a DeviceNet Communications Unit is used, one connection type can be used to exchange data from IN Area 1 and OUT Area 1, and another connection can be used to exchange data from IN Area 2.
The default connections and connection paths are shown in the following table.
Allocated Area
IN Area 1
OUT Area 1
IN Area 2
Connection type used
Poll
Poll
None
Connection path used
IN Area 1
OUT Area 1
None
By setting the following connections as user-defined settings, the IN Area can be divided into two areas.
Allocated Area
IN Area 1
OUT Area 1
IN Area 2
Connection type used
Poll
Poll
COS or Cyclic
Connection path used
IN Area 1
OUT Area 1
IN Area 2
Setting from the DeviceNet Configurator
1,2,3...
1.
Right-click the icon for the DeviceNet Communications Unit and select
Properties. The EJ1N-HFUB-DRT Property Window will be displayed.
75
Allocating Data in the Master
Section 4-5
2.
Click the I/O Information Tab and click the Edit Button. The Change I/O
Size Window will be displayed.
3.
Change the output size and input size for the COS or Cyclic connection to be used. Set the output size to the same value as the output size of the Poll connection and set the input size to the size used for allocation area 2 of on the I/O Allocation (IN) Tab Page for the DeviceNet Communications
Unit.
4.
Select the Unit from the General Tab Page for the master in the Edit Device
Parameters Window of the master, and then click the Advanced Setup
Button. The Connection Tab Page will be displayed.
76
Allocating Data in the Master
Section 4-5
5.
Select User Setup, and select Use Poll Connection for one connection, the same as the default setting. Then select the connection path from the pull-down menu as OUT area 1 for the OUT side, and IN area 1 for the IN side.
For the second connection, select either Use COS Connection or Use
Cyclic Connection, then select IN area 2 as from the pull-down menu on the IN side as the connection path. For the connection path on the OUT side, always set the same connection path as specified for the Poll connection.
Example: When Use COS Connection is selected.
Note The output for the Poll connection and the output for the COS or Cyclic con-
nection are sent in the same frame. Therefore, the same output size must be set for both connections when using a Poll and COS combination, or a Poll and Cyclic combination. When a COS or Cyclic connection are used, always set a dummy output size, and set the same connection path that is used for the Poll connection.
6.
Click the OK Button, and return to the master's Edit Device Parameters
Window. The following dialog box will be displayed when master I/O allocation is performed before the connection is set.
Edit the I/O allocation on the master’s I/O Allocation (IN) Tab Page. Allocation words can be set for each connection in the Edit I/O Allocation Window.
77
Ladder Programming Examples
Section 4-6
7.
Click the OK Button, and return to the master's Edit Device Parameters
Window.
8.
Select the General Tab, and click the Download Button to write the set I/O memory allocations to the master.
Note Always click the OK Button to exit the master's Edit Device Parameters Win-
dow. If the Cancel Button or the Button is clicked, the settings will be invalid.
4-6 Ladder Programming Examples
4-6-1 RUN/STOP Programming Examples
The ladder programming example here is for the following execution conditions.
• Using simple I/O allocation to allocate data in the fixed allocation area 1 of a CS/CJ-series DeviceNet Unit (OUT Area = CIO 3200 to CIO 3263, IN
Area = CIO 3300 to CIO 3363).
Operation
• Executes RUN or STOP for the TC2 (Unit 0, ch1).
• The bit in the first word + 2 words of the OUT Area is allocated by default to the RUN/STOP Bit (CIO 320200).
• RUN is executed when the RUN/STOP Bit (CIO 320200) turns ON for the execution condition 000000, after which the OUT Enable Bit turns ON.
When the RUN/STOP Confirmation Flag (CIO 330200) turns ON, the
OUT Enable Bit turns OFF.
• STOP is executed when the RUN/STOP Bit (CIO 320200) turns OFF for the execution condition 000100, after which the OUT Enable Bit turns ON.
Then, when the RUN/STOP Confirmation Flag (CIO 330200) turns OFF, the OUT Enable Bit turns OFF.
78
Ladder Programming Examples
Programming Example
0 00000
00 0000
Execution condition
000001
000003
3302 00
0000 02
RUN/STOP Confirmation Flag
000007
00 0100
0 00010
00 0013
Execution condition
00 0101
3 30200
0 00102
RUN/STOP Confirmation Flag
0000 17
0000 20
SET
32 0200
ASL(025)
0000
SET
32 0000
ASL(025)
0000
RSET
320000
ASL( 025)
0000
R SET
3 20200
ASL(025 )
0 001
S ET
3 20000
ASL(025 )
0 001
RSET
3200 00
A SL(025)
0 001
END(001)
Turns ON CIO 320200 (RUN/STOP).
Shifts the contents of CIO 0000 one bit to the left. (CIO 000001 ON)
Turns ON CIO 320000 (Output Enable Bit)
Shifts the contents of CIO 0000 one bit to the left. (CIO 000002 ON)
Turns OFF CIO 320000 (Output Enable Bit).
Shifts the contents of CIO 0000 one bit to the left. (CIO 000003 ON)
Turns OFF CIO 320200 (RUN/STOP).
Shifts the contents of CIO 0001 one bit to the left. (CIO 000101 ON)
Turns ON CIO 320000 (Output Enable Bit).
Shifts the contents of CIO 0001 one bit to the left. (CIO 000102 ON)
Turns OFF CIO 320000 (Output Enable Bit).
Shifts the contents of CIO 0001 one bit to the left. (CIO 000103 ON)
END
Section 4-6
4-6-2 Change SP Programming
Example
The ladder programming example here is for the following execution conditions.
• Using simple I/O allocation to allocate data in the fixed allocation area 1 of a CS/CJ-series DeviceNet Unit of CS/CJ-series DeviceNet Unit (OUT
Area = CIO 3200 to CIO 3263, IN Area = CIO 3300 to CIO 3363).
Operation
• Writes the SP to the TC2 (SP = 150 hex, destination = Unit 0, ch1).
• Writes the SP to the first word + 6 words of the default allocated OUT
Area (CIO 3206).
• The SP is first set in D1000, and then transferred to CIO 3206 at the start of the ladder program when the execution condition (CIO 000000) turns
ON. The OUT Enable Bit will then turn ON, and the SP will be refreshed.
79
Ladder Programming Examples
Section 4-6
Programming Example
A20011
000000
First Scan Flag
000000
000002
Execution condition
MOV(021)
0150
D1000
MOV(021)
D1000
3206
ASL(025)
0000
Sets 0150 in D1000.
Moves D1000 (0150) to CIO 3206.
(Transfers to channel in which SP is allocated.)
Shifts the contents of CIO 0000 one bit to the left. (CIO 000001 ON)
000001
000005
SET
320000
Turns ON the OUT Enable Bit (CIO 320000).
000008
ASL(025)
0000
Shifts the contents of CIO 0000 one bit to the right. (CIO 000002 ON)
END(001)
END
4-6-3 Change MV Upper Limit/Lower Limit Programming Example
The ladder programming example here is for the following execution conditions.
• Using the Configurator to allocate I/O in the fixed allocation area 1 of a
CS/CJ-series DeviceNet Unit (OUT Area = CIO 3200 to CIO 3263, IN
Area = CIO 3300 to CIO 3363).
Operation
• This programming example writes the MV upper limit/lower limit to the
TC2 (Unit 0, ch1) (upper limit: 50 hex, lower limit 20 hex).
• MV upper limit/lower limit cannot be used with simple I/O allocations, so the Configurator is used to allocate memory. In this programming example, the MV upper limit is allocated in CIO 3218, the MV lower limit in CIO
3219, and the Output Completed Flags in CIO 3300.
• The MV upper limit is set in D1000 and the MV lower limit is set in D1001 at the start of the ladder program, and then they are transferred to CIO
3218 and CIO 3219 when the execution condition, CIO 000000, turns ON.
Next, the upper and lower limits are refreshed when the OUT Enable Bit turns ON. If the data is transferred normally, the Output Completed Flags turn ON, and then OUT Enable Bit turns OFF.
80
Ladder Programming Examples
Programming Example
000000
A20011
First Scan Flag
000003
000000
Execution condition
000007
000001
000010
000002 330000
Checks Output Completed Flags
(If CIO 330000 is ON, output has been completed.)
000014
Section 4-6
MOV(021)
#0050
D1000
MOV(021)
#0020
D1001
MOV(021)
D1000
3218
MOV(021)
D1001
3219
ASL(025)
0000
SET
320000
ASL(025)
0000
RSET
320000
ASL(025)
0000
END(001)
Sets 0050 in D1000.
Sets 0020 in D1001.
Sets D1000 (0050) in CIO 3218.
(Moves data to the word in which MV upper limit value is allocated.)
Sets D1001 (0020) in CIO 3219.
(Moves data to the word in which MV lower limit value is allocated.)
Shifts the contents of CIO 0000 one bit to the left. (Turns ON CIO 000001.)
Turns ON the OUT Enable Bit.
Shifts the contents of CIO 0000 one bit to the left. (Turns ON CIO 000002.)
Turns OFF the OUT Enable Bit.
Shifts the contents of CIO 0000 one bit to the left. (Turns ON CIO 000003.)
END
81
Ladder Programming Examples
Section 4-6
82
SECTION 5
Operations from the Configurator
This section describes the DeviceNet Configurator operations that can be used for the EJ1 DeviceNet Communications Unit
except for allocation procedures, which are described in SECTION 4 Remote I/O Communications.
5-1 List of Operations from the Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-2 Operations from the Edit Device Parameters Window . . . . . . . . . . . . . . . . . .
5-2-1 Preparing the Configurator Connection . . . . . . . . . . . . . . . . . . . . . .
5-2-2 Edit Device Parameters Window . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-2-3 Setting DeviceNet Communications Unit Comment . . . . . . . . . . . .
5-2-4 Setting Network Power Voltage Monitor . . . . . . . . . . . . . . . . . . . . .
5-2-5 Setting the Unit Conduction Time Monitor . . . . . . . . . . . . . . . . . . .
5-2-6 Setting Last Maintenance Date. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-2-7 Copying Temperature Controller Parameters . . . . . . . . . . . . . . . . . .
5-2-8 Sending Operation Commands to the Temperature Controllers. . . .
5-2-9 Editing Temperature Controller Parameters . . . . . . . . . . . . . . . . . . .
5-2-10 Setting Temperature Controller Comment . . . . . . . . . . . . . . . . . . . .
5-2-11 Setting Temperature Controller Monitor Mode and Monitor Values
5-3-1 Maintenance Mode Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-3-2 Maintenance Information Window . . . . . . . . . . . . . . . . . . . . . . . . . .
5-4 DeviceNet Communications Unit Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . .
83
List of Operations from the Configurator
Section 5-1
5-1 List of Operations from the Configurator
This section describes the settings and operations performed by the Configu-
rator apart from those operations explained in SECTION 4 Remote I/O Com-
munications. Various setting and operation procedures are possible from the
Configurator, and only examples are provided here.
Note Always use Ver. 2.44 or higher of the Configurator or CX-Integrator Ver. 2.2 or
higher for setting and monitoring the DeviceNet Communications Unit.
Master's Edit Device Parameters Window
Registering DeviceNet Communications Unit in the master
Setting DeviceNet Communications Unit connections
Allocating data in the master
DeviceNet Communications Unit's Edit Device Parameters Window
General Tab
Setting details of DeviceNet Communications Unit
Setting Network power voltage monitor value
Setting DeviceNet Communications Unit conduction time monitor value
Setting last maintenance date
Operation commands
Setting details of Temperature Controllers
Setting Temperature Controller monitor mode (Total ON or RUN time)
Setting Temperature Controller monitor value (Total ON or RUN time monitor value) 95
Editing Temperature Controller parameters
I/O Allocations (OUT) Tab
Item
Allocating allocation data in the OUT Area
I/O Allocations (IN) Tab
Allocating allocation data in the IN Area
Monitor Device Window
Maintenance Information Window (accessed from the Maintenance Mode Window)
General Tab
Displaying DeviceNet Communications Unit comment
---
---
---
---
Reference page
---
Displaying last maintenance date
Displaying DeviceNet Communications Unit Conduction Time
Displaying Network power voltage PV
Displaying Network power voltage peak value
Displaying Network power voltage bottom value
Displaying Unit status
(Temperature Controller power voltage status, communications power voltage monitor status, DeviceNet Communications Unit Conduction time monitor status, Temperature
Controller total ON/RUN time monitor status)
Unit Tab
Displaying the Temperature Controller comment
Displaying the Temperature Controller total ON/RUN time
Temperature Controller total ON/RUN time monitor value status
Error History Tab
Displaying the communications error history
---
---
---
84
Operations from the Edit Device Parameters Window
Section 5-2
5-2 Operations from the Edit Device Parameters Window
5-2-1 Preparing the Configurator Connection
If problems occur in the connection with the Configurator, change the settings for the master. Problems will occur if the master's message timeout time is too short or the I/O size allocated in the master is different from that allocated in the DeviceNet Communications Unit.
Configurator Connected Using a DeviceNet Interface Board (Card)
1,2,3...
1.
Right-click the icon for the master, then select Monitor to display the Monitor Device Window.
2.
Click the Stop Remote I/O Communication Button to stop remote I/O communications with the DeviceNet Communications Unit.
Note This operation is not required if no error has occurred in the master node.
Master Connected using Serial Line
1,2,3...
1.
Double-click the icon for the master to display the Edit Device Parameters
Window and click the Message Timer Tab.
2.
Double-click the unit number of the DeviceNet Communications Unit, set
5,000 ms in the Setup Message Timer Window, and click the OK Button.
3.
Click the Download Button on the General Tab Page in the Edit Device Parameters Window to execute the download.
5-2-2 Edit Device Parameters Window
1,2,3...
1.
Turn ON the power to the DeviceNet Communications Unit and master, and then put the Configurator online, and select Upload from the Network
Menu.
The configuration of Units connected in the Network will be read and displayed in the Network Configuration Window.
85
Operations from the Edit Device Parameters Window
Section 5-2
2.
Double-click the icon for the DeviceNet Communications Unit in the Network Configuration Window, or right-click and select Parameter and Edit to display the Edit Device Parameters Window for the DeviceNet Communications Unit.
Note
1.
Click the Upload Button to read the Unit configuration registered in the DeviceNet Communications Unit.
2.
Click the Upload Real Configuration Button to read the configuration of the
Temperature Controllers currently connected to the DeviceNet Communications Unit at that time.
3.
Click the Reset Button to reset the DeviceNet Communications Unit. The status of the Unit will be the same as if the power had been turned OFF and ON again. Temperature Controllers, however, will not be reset during operation.
4.
Click the Default Setting Button to initialize all the DeviceNet Communications Unit settings, and return them to the factory setting status. The Configurator screen will not return to factory setting status, however, so click the Upload Button to read the settings again. The message monitor timer
must be changed to use this function. For details, refer to page 107.
!Caution Always change the OUT Enable Bit to 0 when using the Configurator to download the parameters set in the Temperature Controller. If the OUT Enable Bit are not 0 when downloading, the set values allocated with I/O and the set values downloaded with the Configurator will compete, causing the set values
allocated using I/O to be enabled. For details on OUT Enable Bit, refer to OUT
5-2-3 Setting DeviceNet Communications Unit Comment
A name can be assigned to the DeviceNet Communications Unit and recorded in the Unit. The name can be entered using up to 32 standard characters. The comment for the registered DeviceNet Communications Unit is
86
Operations from the Edit Device Parameters Window
Section 5-2
used in the Configurator display, such as in the Maintenance Mode Window
Note The DeviceNet Communications Unit comment is stored even when the
power is turned OFF.
Setting Method
1,2,3...
In the DeviceNet Communications Unit's Edit Device Parameters Window, click the General Tab, and enter a comment in the Comment field at the top of the Tab Page.
Note Comments can also be set by right-clicking the DeviceNet Communications
Unit in the Network Configuration Window and selecting Change Device
Comment.
After setting a comment, right-click and select Parameter and Download to write the comment to the DeviceNet Communications Unit.
5-2-4 Setting Network Power Voltage Monitor
With the Network power voltage monitor, the present value, bottom (minimum) value, and peak (maximum) value are recorded in the DeviceNet Communications Unit, and when the voltage drops below the set monitor value, the Network Power Voltage Error Flag in the Unit Status Area will be turned ON.
The PV, bottom value, and peak value of the network power supply, and the
Unit Status Area can be checked from the Maintenance Mode Window.
Note
1.
The range of the network power voltage for the DeviceNet Communications Unit is 11 to 25 V, so if the network power voltage drops below 11 V, the operation for reading the measured voltage value may not function properly.
• The default monitor value for the network power voltage is set to
11.0 V.
• The network power supply monitor value is held even when the power is turned OFF.
2.
The present, bottom, and peak values for the network power voltage are cleared when the network power is turned OFF.
87
Operations from the Edit Device Parameters Window
Setting Method
Section 5-2
1,2,3...
Open the Edit Device Parameters Window for the DeviceNet Communications
Unit, select the General Tab, and enter the desired value in the Network
Power Voltage field.
5-2-5 Setting the Unit Conduction Time Monitor
The DeviceNet Communications Unit can record the conduction time (time that communications power is supplied to the Unit), and when the value exceeds the set monitor value, the Unit Maintenance Bit in the Unit Status
Area will be turned ON.
This function provides a guideline for when to replace the Unit.
Measuring unit: 0.1 h (On the Configurator, however, the display unit will be 1 h.)
Measured time: 0 to 429496729.5 h
(stored data: 00000000 to FFFFFFFF hex)
Monitor value setting range: 0 to 429496729 hours (specify as an integer)
The present value for conduction time and the Unit Status Area can be checked in the Maintenance Information Window when using Maintenance
Mode.
Note The present value and monitor value for the conduction time are held even
when the power is turned OFF.
Setting Method
1,2,3...
Open the Edit Device Parameters Window for the DeviceNet Communications
Unit, select the General Tab, and enter the desired value in the Unit Conduc-
tion Time field.
88
Operations from the Edit Device Parameters Window
Section 5-2
5-2-6 Setting Last Maintenance Date
With DeviceNet Communications Units, the last date on which maintenance was last performed can be written to the Unit. This means that the timing for future maintenance can be judged more easily. The recorded date can be checked from the Maintenance Mode Window.
Note The present value and monitor value for the conduction time are held even
when the power is turned OFF.
Setting Method
1,2,3...
Open the Edit Device Parameters Window for the DeviceNet Communications
Unit, click the General Tab, and select the applicable date from the calendar in the pull-down menu in the Last Maintenance Date field.
89
Operations from the Edit Device Parameters Window
Section 5-2
5-2-7 Copying Temperature Controller Parameters
Parameters of the Temperature Controllers connected to the DeviceNet Communications Unit can be easily copied between Temperature Controllers by simply specifying the copy source and destination. The all the parameters for one channel of the Temperature Controller are copied, so multiple Temperature Controllers requiring the same settings can be easily set.
Setting Method
1,2,3...
1.
Open the Edit Device Parameters Window for the DeviceNet Communications Unit, select the General Tab, and click the Copy Button of the Temperature Controller unit number under Unit Configuration from which the parameters are to be copied.
2.
The Copy Parameters Window will be displayed.
90
Operations from the Edit Device Parameters Window
Section 5-2
3.
Select the channel from which to copy, specify the unit number and channel as the copy destination, and then click the OK Button. The parameters will be copied and the display will return to the Edit Device Parameters
Window for the DeviceNet Communications Unit.
4.
From the Edit Device Parameters Window, select the General Tab, and click the Download Button to write all the parameters copied from the Temperature Controller.
5-2-8 Sending Operation Commands to the Temperature Controllers
The Configurator can be used to send operation commands to each of the
Temperature Controllers through the DeviceNet Communications Unit.
The following operation commands can be executed from the Configurator.
• RUN/STOP
• Alarm latch cancel
• Auto/manual
• Initialize settings
• AT execute/cancel
• Software reset
• LSP/RSP switching
• Clear error
• Write mode
Operating Method
1,2,3...
1.
Open the Edit Device Parameters Window for the DeviceNet Communications Unit, select the General Tab, and click the Operation Button for the
Temperature Controller unit number in the Unit Configuration field.
91
Operations from the Edit Device Parameters Window
Section 5-2
2.
The window for sending operation commands to the specified Temperature
Controller will be displayed.
3.
Select the Tab Page for the channel that will be sent the command, and click the button of the operation to be executed.
Note The message monitor timer must be changed to initialize settings.
For details, refer to page 107.
4.
After the operation command is executed, click the Close Button.
The display will return to the Edit Device Parameters Window for the DeviceNet Communications Unit.
Note Use the following procedure to change a manual manipulated variable.
1,2,3...
1.
Click the Manual Button.
2.
Change the manipulated variable in the Edit Unit Parameters Window, and click the Download can be changed during operation Button.
Note Use the following procedure to initialize the Temperature Controller.
1,2,3...
1.
Click the Parameter Initialization Button and then the Save RAM Data 2
Button.
2.
Click the Reset Button in the Edit Device Parameters Window.
92
Operations from the Edit Device Parameters Window
Section 5-2
5-2-9 Editing Temperature Controller Parameters
The Configurator can be used to edit the parameters of each connected Temperature Controller through the DeviceNet Communications Unit.
1,2,3...
1.
Open the Edit Device Parameters Window for the DeviceNet Communications Unit, click the General Tab and click the Set Button next to the Temperature Controller unit number under Unit Configuration.
2.
A window for editing the unit parameters of the corresponding Temperature
Controller will be displayed.
Note a) This icon indicates parameters that are shared by ch1 to ch4.
If a value for any channel is changed, the other value will also change.
93
Operations from the Edit Device Parameters Window
Section 5-2
This icon indicates a parameter that is read only.
b) The Temperature Controller parameters are stored even if the power is turned OFF.
3.
Select the tab page of the channel for which the parameters are to be edited, and edit the parameters.
4.
Click the parameter to be edited, and change the contents.
94
Note a) Click the Download Button to download all parameters. When this operation is performed, the Unit will be reset, so do not use this operation while the Unit is in RUN mode.
b) By clicking the Button in the Parameter Group field, the displayed parameters can be changed as follows:
• All parameters
• Parameters that can be changed during operation
• Parameters that can be changed when operation is stopped.
c) Click the Default Setting Button to return parameters to the factory settings.
d) Click the Upload, Download, Compare, and Default Setting Buttons in the Edit Unit Parameters Window to perform operations on the parameters for the specified channel only.
e) Use the Download can be changed during operation Button to download parameters that can be changed during operation. The
Unit will not be reset.
5.
Click the OK Button.
The display will return to the Edit Device Parameters Window for the DeviceNet Communications Unit.
Note All the new settings will be canceled if the Cancel Button or Button is clicked to exit the window. Always exit the window by clicking the OK Button.
6.
To continue editing the parameters of other Temperature Controllers, repeat the procedure from step 1.
Operations from the Edit Device Parameters Window
Section 5-2
5-2-10 Setting Temperature Controller Comment
Names can be assigned to each of the Temperature Controllers, and recorded in the DeviceNet Communications Unit. Each name can be entered using up to 32 standard characters.
The registered Temperature Controller comments are used in the Configurator, such as in the Monitor Window and Maintenance Mode Window.
Note The comments set for Temperature Controllers are stored even when the
power is turned OFF.
Setting Method
7.
After editing the parameters of each Temperature Controller, return to the
General Tab Page and click the Download Button to download the set pa-
rameters to the DeviceNet Communications Unit in a batch.
1,2,3...
1.
Open the Edit Device Parameters Window for the DeviceNet Communications Unit, select the General Tab Page, and click the Set Button.
The Edit Unit Parameters Window will be displayed.
2.
Enter the name or other comment in the Comment field.
3.
Click the OK Button to return to the Edit Device Parameters Window.
Note If the window is exited by clicking the Cancel Button or Button, all the new settings will be canceled. Always click the OK Button to exit the window.
4.
To continue setting comments for other Temperature Controllers, repeat the procedure from step 1.
5.
After entering comments for each Temperature Controller, return to the
General Tab Page and click the Download Button to write the comments
to the DeviceNet Communications Unit in a batch.
5-2-11 Setting Temperature Controller Monitor Mode and Monitor Values
A conduction time monitor and total RUN time monitor can be used to calculate the conduction time or RUN (control) time of connected Temperature
Controllers and record the time in the DeviceNet Communications Unit. When
95
Operations from the Edit Device Parameters Window
Section 5-2
the total time exceeds the set monitor value, the Temperature Controller Maintenance Bit in the Unit Status Area will be turned ON.
These monitors provide a guideline for when to replace the Temperature Controllers.
Set whether to total the Unit conduction time or RUN time using the MONI-
TOR mode.
Measuring unit: 0.1 h (The Configurator display is in 1-h units.)
Measured time: 0 to 429496729 h
(stored data: 00000000 to FFFFFFFF hex)
Monitor value setting range: 0 to 429496729 hours
The present values for the conduction time or RUN time, and the Unit status can be checked from the Maintenance Mode Window.
Note
1.
The present values and monitor values for conduction time or RUN time are stored even when the power is turned OFF.
2.
The conduction time monitor and total RUN time monitor cannot be used at the same time for a single channel.
3.
The total time is not calculated when the communications power to the DeviceNet Communications Unit is turned OFF.
4.
The DeviceNet Communications Unit checks the ON/RUN status of the specified Temperature Controller approximately every 0.1 hour (6 minutes). Depending on the measurement timing, the accurate may not be obtained due to the timing interval, as shown in the following examples.
Example 1: Using the Unit conduction time monitor when communications power is turned ON and
OFF for three minutes each (A)
Calculates ON time every 6 min approx.
ON
OFF
3 min
In the above diagram, the actual conduction time is 3 minutes
× 3 = 9 minutes, but the status is ON only once at the time the measurement is taken, so the conduction time is calculated as 6 minutes.
Example 2: Using the Unit conduction time monitor when communications power is turned ON and
OFF for three minutes each (B)
Calculates ON time every 6 min approx.
ON
OFF
3 min
In the above diagram, the actual conduction time is 3 minutes
× 3 = 9 minutes, but the status is ON only twice at the time the measurement is taken, so the conduction time is calculated as 12 minutes.
Example 3: Using the Unit conduction time monitor when communications power is turned ON for 9 minutes, OFF for 3 minutes, and ON for 9 minutes
Calculates ON time every 6 min approx.
ON
OFF
9 min
96
Maintenance Mode Window
Section 5-3
In the above diagram, the actual conduction time is 9 minutes
× 2 = 18 minutes, but the status is ON four times when the measurement is taken, so the conduction time is calculated as 24 minutes.
Setting Method
1,2,3...
1.
Open the Edit Unit Parameters Window, select the monitor mode to be used, Conduction Time or RUN Time, under the Detection Mode, and enter the monitoring time in the Value field.
2.
Click the OK Button to return to the Edit Device Parameters Window.
Note All the settings will be cleared if the Cancel Button or Button is used to exit the window. Always click the OK Button to exit the window.
3.
To continue setting monitor values for other Temperature Controllers, repeat the procedure from step 1.
4.
After setting monitor values for each Temperature Controller, return to the
General Tab Page and click the Download Button to write the monitor val-
ues for all the Temperature Controllers to the DeviceNet Communications
Unit in a batch.
5-3 Maintenance Mode Window
5-3-1 Maintenance Mode Window
The Maintenance Mode Window is different from the Main Window and is used to easily monitor the Network status and the status of each node.
In the Network Configuration Window of the Maintenance Mode Window, when an error is detected in a node, a yellow warning icon is displayed next to the corresponding node icon, enabling errors to be checked immediately.
By double-clicking on a node in the Network Configuration Window of the
Maintenance Mode Window, the Maintenance Information Window is displayed, and the status of the node can be checked.
The Maintenance Mode Window is displayed with a pale blue background.
Maintenance Mode
Window Display
Use either of the following two procedures to switch between the Main Window and the Maintenance Mode Window.
97
Maintenance Mode Window
Section 5-3
Switching from the Icons in the Toolbar
1,2,3...
1.
From the Main Window, click the icon in the Configurator Toolbar to switch to the Maintenance Mode Window.
2.
Click the icon to return to the Main Window.
Switching from the View Menu
1,2,3...
1.
From the menu bar, select View and Large Icons (Maintenance Mode) to switch to the Maintenance Mode Window.
2.
From the menu bar, select View and Large Icons to return to the Main
Window.
Note
1.
2.
This icon indicates that the Network power supply is low.
This icon indicates that the Maintenance Bit is ON.
98
Maintenance Mode Window
Section 5-3
5-3-2 Maintenance Information Window
General Tab Page
1,2,3...
From the Maintenance Mode Window, double-click the icon for the DeviceNet
Communications Unit in the Network Configuration Window. The following
Maintenance Information Window for the DeviceNet Communications Unit will be displayed.
Note
The following information can be checked from the General Tab Page.
Comment
Item Description
Displays the comment set using the comment setting function of the DeviceNet Communications Unit.
Last Maintenance Date Displays the last maintenance date set in the DeviceNet
Communications Unit.
Unit Conduction Time Displays the present value for the conduction time of the
DeviceNet Communications Unit.
Network Power Voltage Displays the present value for the communications power voltage being supplied to the DeviceNet Communications
Unit.
Network Peak Power
Voltage
Displays the peak communications power voltage supplied to the DeviceNet Communications Unit since startup.
Network Bottom Power
Voltage
Displays the bottom communications power voltage supplied to the DeviceNet Communications Unit since startup.
Unit Status (See note 1.)
Network Power
Voltage Drop
Unit Maintenance
Time
Temperature Controller Power Error
Temperature Controller Maintenance Time
Selected if the power supply for the Temperature Controller is OFF (Temperature Controller Power Status Flag).
Selected if the conduction time of the DeviceNet Communications Unit exceeds the setting (Maintenance Flag).
Selected if the power supply for the Temperature Controller is OFF (Temperature Controller Power Status Flag).
Selected if the total ON/RUN time exceeds the setting.
1.
The content of Unit Status is the same as that for Unit Status in allocation
data. (For information, refer to Unit Status in 4-3-4 Input Data.
99
Maintenance Mode Window
Section 5-3
2.
Click the Refresh Button to read the maintenance information, error history, and Temperature Controller maintenance information from the DeviceNet Communications Unit and display the most recent values.
3.
Click the Save Maintenance Counter Button to save the Unit conduction time and Temperature Controller maintenance counter values in the DeviceNet Communications Unit's internal non-volatile memory.
4.
Even if the Save Maintenance Counter Button is not clicked, the values will normally be saved in the non-volatile memory once every six minutes.
Unit Tab Page
1,2,3...
1.
From the Maintenance Mode Window, double-click the icon for the DeviceNet Communications Unit in the Network Configuration Window.
2.
The Maintenance Information Window for the DeviceNet Communications
Unit will be displayed. Select the Unit Tab.
3.
When the present values for the Unit conduction time or total RUN time exceed the monitor value set in the total ON/RUN time monitor, a warning icon will be displayed beside the corresponding unit number in the #ch column.
The following information can be confirmed for each of the Temperature Controllers connected to the DeviceNet Communications Unit.
Item
Comment
Maintenance
Counter
Details
Displays the Temperature Controller comment set using the comment function.
Displays the present value for the Unit conduction time or total
RUN time measured using the total ON/RUN time monitor.
Note Click the Clear Maintenance Counter Button to clear the contents of the
maintenance counter.
Error History Tab Page
1,2,3...
1.
From the Maintenance Mode Window, double-click the icon for the DeviceNet Communications Unit in the Network Configuration Window.
2.
The Maintenance Information Window for the DeviceNet Communications
Unit will be displayed. Select the Error History Tab.
100
Maintenance Mode Window
Section 5-3
3.
The Error History Tab Page displays the error status information (communications error code, communications power voltage when the error occurred) that is recorded in the DeviceNet Communications Unit for the last four communications errors that occurred.
Note
1.
When four communications errors are already recorded in the error history and a new communications error occurs, the earliest error will be deleted and the most recent communications error will be recorded.
2.
Click the Clear Button to clear the communications error history in the DeviceNet Communications Unit. The display in the Error History Tab Page will also be cleared.
101
DeviceNet Communications Unit Monitor
Section 5-4
5-4 DeviceNet Communications Unit Monitor
The monitor lists various status information for the DeviceNet Communications Unit.
Displaying the Monitor
1,2,3...
1.
Select Network and Connection, and put the Configurator online.
2.
Right-click the icon of the DeviceNet Communications Unit, and select
Monitor. The following Monitor Device Window will be displayed.
102
Item
Communications
Status
Status
Table Status
EEPROM Status
Results of Backup
Unit Status
Details
Displays the communications status of the Temperature Controllers connected to the Communications Unit.
(Blue) Communicating normally.
(Red) A communications error has occurred.
Displays the Communications Unit's present operating status.
Displays the status of the Communications Unit's setup table.
Displays the status of the Communications Unit's non-volatile memory (EEPROM).
Displays the results of the backup operation.
Displays the Temperature Controller process value (PV), and set value (SP).
The details for the Temperature Controller that is positioned under the cursor are displayed on the right of the Tab Page.
Note The Monitor Device Window will respond slowly if many Temperature Control-
lers are connected. Operation can be improved by selecting Setup Monitor
Refresh Timer in the Options Menu and setting a value of 3 s or higher.
SECTION 6
Explicit Message Communications
This section describes how to send explicit messages to the EJ1 DeviceNet Communications Unit, including how to send
CompoWay/F commands using explicit messages. CompoWay/F commands are supported by the EJ1 Temperature
Controller.
6-1 Overview of Explicit Message Communications . . . . . . . . . . . . . . . . . . . . . .
6-1-1 Explicit Message Communications . . . . . . . . . . . . . . . . . . . . . . . . .
6-1-2 Explicit Messages Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-1-3 Explicit Messages Basic Format. . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-1-4 Initializing the DeviceNet Communications Unit or
Temperature Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-2 Sending CompoWay/F Commands to a Temperature Controller . . . . . . . . . .
6-2-1 CompoWay/F Binary Commands . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-2-2 CompoWay/F ASCII Commands . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-2-3 List of FINS-mini Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-3 Examples Using CompoWay/F Commands . . . . . . . . . . . . . . . . . . . . . . . . . .
6-4 Example of Sending Explicit Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-5-1 Reading General Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-5-2 Setting and Monitoring the Unit Conduction Time . . . . . . . . . . . . .
6-5-3 Writing Maintenance Mode Information . . . . . . . . . . . . . . . . . . . . .
6-5-4 Setting and Monitoring Temperature Controller Channels . . . . . . .
103
Overview of Explicit Message Communications
Section 6-1
6-1 Overview of Explicit Message Communications
6-1-1 Explicit Message Communications
Explicit message communications is a communications protocol for sending commands from the master as explicit messages, and receiving explicit messages as responses from the nodes that receive the commands.
Explicit messages can be sent from the master to the DeviceNet Communications Unit to read and write the Temperature Controller variable area, send operation commands, and read and write various other functions supported by the DeviceNet Communications Unit.
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 Temperature Controller Variable Area Data and Sending Operation Commands
Send Compoway/F communications commands to Temperature Controllers by embedding them in explicit messages.
Reading/Writing Maintenance Information for the DeviceNet Communications Unit and Temperature
Controllers
Send explicit messages to the DeviceNet Communications Unit.
DeviceNet Unit CPU Unit
Master
(PLC)
IOWR or
CMND instruction
CompoWay/F communications command sent to Temperature
Controller (embedded in explicit message)
Explicit message sent to DeviceNet
Communications Unit
Slave Slave
Temperature Controller
DeviceNet Communications Unit
Conversion
Unit
0
Unit
1
CompoWay/F communications command
Note This manual describes the contents of explicit messages that can be sent to
DeviceNet Communications Units. For details on the methods of sending explicit messages, refer to the operation manual for the DeviceNet Unit being used as the master.
104
Overview of Explicit Message Communications
Section 6-1
6-1-2 Explicit Messages Types
The explicit messages sent to the DeviceNet Communications Unit can be divided into two types, as follows:
Sending CompoWay/F Communications Commands to Temperature Controllers
The master can send CompoWay/F communications commands to the Temperature Controllers by sending to the DeviceNet Communications Unit as explicit messages data.
The DeviceNet Communications Unit automatically converts the explicit messages to CompoWay/F communications commands and sends them to the
Temperature Controllers. The responses from the Temperature Controllers are converted into explicit messages and returned to the master. Compo-
Way/F commands are used to read from and write to the Temperature Controller variable area and to execute operation commands.
CompoWay/F commands consist of binary commands and ASCII commands.
CompoWay/F Binary
Commands
CompoWay/F ASCII
Commands
CompoWay/F binary commands are CompoWay/F communications commands expressed in hexadecimal, and are easy to execute from ladder programs. CompoWay/F communications commands that include ASCII data, however, cannot be sent or received. Therefore, Read Controller Attribute (05
03) and broadcasting (communications unit number = XX) cannot be used.
CompoWay/F ASCII commands are CompoWay/F communications commands expressed in ASCII, so numerical values must be converted to ASCII when executing these commands from a ladder program. All CompoWay/F communications commands can be sent and received, including Read Controller Attribute (05 03) and broadcasting (unit number = XX), which cannot be used with CompoWay/F binary commands.
Sending Explicit Messages to the DeviceNet Communications Unit
The master can send explicit messages to the DeviceNet Communications
Unit to control various operations supported by the DeviceNet Communications Unit and to read settings and status information.
Explicit messages are used to read and write various maintenance data for the DeviceNet Communications Unit and Temperature Controllers.
6-1-3 Explicit Messages Basic Format
The basic format of explicit message commands and responses is as follows:
Command Block
Destination Node Address
Service Code, Class ID,
Instance ID, Attribute ID
Destination node address
Service code
Class ID
Instance
ID
Attribute
ID
Data
This parameter specifies the node address of the DeviceNet Communications
Unit to which the explicit messages (commands) will be sent in single-byte (2digit) hexadecimal.
These parameters specify the command type, processing target, and processing details.
When sending explicit messages to the DeviceNet Communications Unit, specify the target Temperature Controller in the Instance ID. (Specify the Temperature Controller's communications unit number and channel number).
The Attribute ID does not need to be specified for some commands.
105
Overview of Explicit Message Communications
Section 6-1
Data
Response Block
Source Node Address
Service Code
Data
Specifies the details of the commands and set values. The data section is not required for read commands.
Note The number of digits used for the Class ID, Instance ID, and Attribute 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
• The following format is used when a normal response is returned for the sent explicit message.
No. of bytes received
Source node address
Service code Data
Number of Bytes Received
• The following format is used when an error response is returned for the sent explicit message.
No. of bytes received
0004 hex, fixed
Source node address
Service code
Error code
(2 bytes, fixed)
The number of data bytes received from the source node address is returned in hexadecimal. When an error response is returned for the explicit message, the contents is always 0004 hex.
The address of the node that sent the response is returned in hexadecimal.
For normal responses, the value for when the most significant bit (bit 07) of the service code specified in the command turns ON is returned. (When the service code of the command is 0E hex, the service code of the response will be 8E hex.) When an error response is returned for the explicit message, the contents is always 94 hex.
Read data is included only when a read command is executed.
106
Overview of Explicit Message Communications
Section 6-1
Error Code
The following table shows the error codes for explicit messages.
Error code
Error name Cause
08FF Service not supported The service code is incorrect.
09FF Invalid Attribute Value The specified attribute value is not supported. The data written is out of the data range.
0CFF Object State Conflict There is a error in the communications between the
DeviceNet Communications Unit and the Temperature Controller.
Another explicit message was received while a previous explicit message was being processed.
10FF Device State Conflict
The copy function is being executed.
0EFF Attribute Cannot Be Set A write service code was sent for a read-only attribute ID.
An attempt was made to access a Temperature Controller that does not exist.
13FF Not Enough Data
There is an error in the EEPROM.
The data string is shorter than the specified size.
14FF Attribute Not Supported The specified attribute is not supported.
15FF Too Much Data The data string is longer than the specified size.
16FF Object Does Not Exist The specified instance ID is not supported.
19FF Store Operation Failure There is an error in the EEPROM of the DeviceNet
Communications Unit.
6-1-4 Initializing the DeviceNet Communications Unit or Temperature
Controllers
Set the DeviceNet message monitor timer for the DeviceNet Communications
Unit to 5 s or longer using the following procedure.
CS/CJ-series DeviceNet Unit
1,2,3...
1.
Using the Configurator, select Connection from the Network Menu to switch to online operation.
2.
Double-click the icon for the master, and then click the Message Timer
Tab in the Edit Device Parameters Window.
3.
Double-click the icon for the DeviceNet Communications Unit, set the timer to 5000 ms in the Setup Message Timer Dialog Box, and then click the OK
Button. (In this example, the node address of the DeviceNet Communications Unit is 00.)
107
Sending CompoWay/F Commands to a Temperature Controller
Section 6-2
4.
Click the General Tab in the Edit Device Parameters Window, and then click the Download Button. The parameters will be downloaded and the value for the message monitor timer of the DeviceNet Communications
Unit will be changed.
C2000HE/HG/HX, CVM1, or CV-series DeviceNet Master Unit
Set the response monitoring time to 5,000 ms when sending the explicit message using an IOWR instruction. (The message timer cannot be set from the
Configurator.)
6-2 Sending CompoWay/F Commands to a Temperature
Controller
The master can send CompoWay/F command frames to the DeviceNet Communications Unit by embedding them in explicit message commands, and receive CompoWay/F response frames that are embedded in explicit messages responses.
When the DeviceNet Communications Unit receives the explicit message command, a CompoWay/F command frame is created by adding STX, ETX, and BCC to the command frame data, from the communications unit number to the FINS-mini command text, after which it is sent to the Temperature Controller. The Temperature Controller returns a CompoWay/F response.
When the DeviceNet Communications Unit receives the CompoWay/F response returned from the Temperature Controller, the STX, ETX, and BCC values are deleted, and then the data is converted to an explicit message response in either hexadecimal or ASCII format, before it is sent to the master. (The DeviceNet Communications Unit performs a BCC check.)
108
Sending CompoWay/F Commands to a Temperature Controller
DeviceNet Unit
Master
(PLC)
Section 6-2
Explicit message header
CompoWay/F command frame data
(unit number to FINS-mini command text)
Slave
Explicit message header
CompoWay/F response frame data
STX
Add
ETX/BCC
Add
Remove explicit header
STX
ETX/BCC
ETX/BCC for
CompoWay/F command
STX for CompoWay/F command
STX
ETX/BCC
ETX/BCC
STX
Explicit header
Note The CompoWay/F frames can be expressed in binary (hexadecimal) (Compo-
Way/F binary commands) or ASCII (CompoWay/F ASCII commands).
Generally, CompoWay/F binary commands are used to minimize the number of operations. Always use CompoWay/F ASCII commands, however, when broadcasting or executing using a Read Controller Attribute (05 03).
The format of explicit messages used for CompoWay/F commands is explained here. For details on CompoWay/F frames, refer to the EJ1 Temper-
ature Controllers User’s Manual (Cat. No. H142).
6-2-1 CompoWay/F Binary Commands
CompoWay/F binary commands use hexadecimal values for the Compo-
Way/F frames, and not ASCII. Therefore, the data volume is about half of
CompoWay/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 “XX” used for the communications unit number when broadcasting is
ASCII, and therefore cannot be specified.
The following command and response formats are used when executing
CompoWay/F binary commands from an OMRON Master.
109
Sending CompoWay/F Commands to a Temperature Controller
Section 6-2
Command Block
Destination node address
Service
Code
Class ID Instance ID
36 hex bytes
0086 hex fixed 0001 hex fixed
Data (CompoWay/F command frame data)
1 byte 1 byte 2 bytes 2 bytes
Specified in binary (hexadecimal).
(See following example.)
Communications Unit
No. (See note.)
Subaddress
SID
00 hex fixed
00 hex fixed
FINS-mini command text
Communications Unit number
01 hex
Sub-address
00 hex
Note Broadcasting cannot be specified.
Example: Communications Unit number = 01, FINS-mini command text = 01
01 C0 0000 00 0001 (Executes Read from Variable Area (01 01), to read one element for ch1 PV (C0 0000)
SID FINS-mini command text
00 hex 01 hex 01 hex C0 hex 00 hex 00 hex 00 hex 00 hex 01 hex
Response Block
Normal Response
No. of received bytes
Source node address
Service
Code
Data (CompoWay/F response frame data)
2 bytes
B6 hex fixed
1 byte 1 byte Responds in binary (hexadecimal)
Communications
Sub-
Unit No.
address
End code
00 hex fixed
00 hex fixed
FINS-mini response text
6-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 converted to ASCII, so 52 is specified as 3532 in ASCII). When CompoWay/F
ASCII commands are used, all CompoWay/F communications commands supported by Temperature Controllers can be used. (Read Controller Attribute
(0503) and broadcasting can be specified.)
The following command and response formats are used when the commands are executed from an OMRON Master Unit.
110
Sending CompoWay/F Commands to a Temperature Controller
Section 6-2
Command Block
Destination node address
Service
Code
Class ID
Instance ID Data (CompoWay/F command frame data)
37 hex fixed
0086 hex fixed
0001 hex fixed
1 byte 1 byte 2 bytes 2 bytes Specified in ASCII code
(See following example.)
Communications Unit No.
(See note.)
Sub-address SID FINS-mini command text
[00]= 3030 hex fixed
[0]= 30 hex fixed
Note For broadcasting, specify XX (58 hex 58 hex ASCII)
Example: Unit number = 01, FINS-mini command text = 01 01 C0 0000 00
0001 (Executes Read from Variable Area (01 01), to read one element for ch1
PV (C0 0000).)
Communications
Unit No.
Sub-address SID FINS-mini command text
30 hex 31 hex 30 hex 30 hex 30 hex 30 hex 31 hex 30 hex 31 hex 43 hex 30 hex
FINS-mini command text
30 hex 30 hex 30 hex 30 hex 30 hex 30 hex 30 hex 30 hex 30 hex 31 hex
Response Block
Normal Response
No. of receive bytes
Source node address
Service
Code
Data (CompoWay/F response frame data)
2 bytes
B7 Hex fixed
1 byte 1 byte Returns in ASCII code
Communications
Unit No.
Sub-address
[00]=
3030 Hex fixed
End code
FINS-mini response text
6-2-3 List of FINS-mini Commands
The following table lists the FINS-mini commands that can be sent to the Temperature Controllers. For details on commands and the variable area, refer to the EJ1 Temperature Controllers User’s Manual (Cat. No. H142).
MRC SRC
01
01
01
01
01
01
02
04
13
10
Service name Description
Read from Variable Area
Write to Variable
Area
Composite Read from Variable Area
Composite Write to Variable Area
Composite Registration Read
Reads a set value.
Writes a set value.
Reads more than one non-consecutive set value.
Writes more than one non-consecutive set value.
Reads in order the contents of addresses specified for composite read registration of set values.
CompoWay/F binary commands
MRC, SRC notation
CompoWay/F ASCII commands
01 hex 01 hex 30 hex 31 hex 30 hex 31 hex
01 hex 02 hex 30 hex 31 hex 30 hex 32 hex
01 hex 04 hex 30 hex 31 hex 30 hex 34 hex
01 hex 13 hex 30 hex 31 hex 31 hex 33 hex
01 hex 10 hex 30 hex 31 hex 31 hex 30 hex
111
Examples Using CompoWay/F Commands
Section 6-3
MRC SRC
01
01
05
06
08
30
11
12
03
01
01
05
Service name
Composite Read
Registration
Composite Read
Registration Confirmation
Controller Attribute
Read
Controller Status
Read
Echoback Test
Operation Command
Description
Specifies the addresses to be read for a composite read of set values.
Reads the contents of the registration for composite read of set values.
Reads the model and communications buffer size.
Reads the operating status.
Performs an echoback test.
Executes RUN/STOP, AT execute/AT cancel, and other operations.
CompoWay/F binary commands
MRC, SRC notation
CompoWay/F ASCII commands
01 hex 11 hex 30 hex 31 hex 31 hex 31 hex
01 hex 12 hex 30 hex 31 hex 31 hex 32 hex
05 hex 03 hex
06 hex 01 hex
08 hex 01 hex
30 hex 05 hex
30 hex 35 hex 30 hex 33 hex
30 hex 36 hex 30 hex 31 hex
30 hex 38 hex 30 hex 31 hex
33 hex 30 hex 30 hex 35 hex
Note
1.
Read Controller Attribute (05 03) cannot be executed using CompoWay/F binary commands. Use CompoWay/F ASCII commands to execute this service.
2.
To write setting data to the variable area for initial settings (variable type
C3) when using EJ1 Temperature Controllers (Write to Variable Area 01
02, variable type C3), first execute Move to Setting Area 1 (Operation Commands 30 05, command code 07).
6-3 Examples Using CompoWay/F Commands
The following example shows the FINS-mini commands, Write to Variable
Area and Read from Variable Area, executed from a CS1W-DRM21 using
CompoWay/F binary commands (embedded in explicit messages).
Operation 1 (Writing
SP)
00 hex 36 hex
• This example writes the SP to TC2 (unit number 0, ch1). (The SP is 240.)
The FINS-mini command writes 000240 hex as the SP data for ch1 with the write start address = 0003 hex, MRC = 01 hex, SRC = 02 hex (Write to Variable Area), variable type = C1 hex, and write start address = 0003 hex.
• The data is written using the EXPLICIT MESSAGE SEND command
(2801).
• The command data is written in words starting from D01000 in the CPU
Unit's memory, and the response data is stored in DM words starting from
D01200.
• If the command does not end normally, the end code is stored in D01106 and the send command is re-executed.
Explicit Message Command
Destination node address
Service code
Class ID Instance
ID
Communications
Unit No.
Subaddress
0086 hex 0001 hex 00 hex 00 hex
SID
00 hex
MRC
01 hex
SRC
02 hex
FINS-mini command text
Variable type
Address Bit position
94 hex 0100 hex 00 hex
No. of elements
Write data
0001 hex 0240 hex
Explicit Message Response
No. of bytes received
Source node address
Service code
Communications
Unit No.
Subaddress
09 hex 00 hex B6 hex 00 hex 00 hex
End code
00 hex
FINS-mini command text
MRC
01 hex
SRC
02 hex
Response code
0000 hex
112
Examples Using CompoWay/F Commands
Command Details
Section 6-3
[CMND S D C]
S
D
C
D01000+0: 2801 hex Command code
+1: 0036 hex DeviceNet Communications Unit node address = 00
Service code = 36 hex
+2: 0086 hex Class ID = 0086 hex
+3: 0001 hex Instance ID = 01 hex
+4: 0000 hex TC2 communications unit number = 00 hex, subaddress (fixed) = 00 hex
+5: 0001 hex SID (fixed) = 00 hex MRC = 01 Hex
+6: 02C1 hex SRC = 02 hex, variable type = 94 hex
+7: 0003 hex Write start address = 0100 hex (2 bytes)
+8: 0000 hex Bit position (fixed) = 00 hex, No. of elements = 00 hex (2 bytes)
+9: 0100 hex No. of elements = 01 hex, Data = 02 hex (4 bytes)
+10: 4000 hex Data = 04 hex (lower byte (00 hex) is not relevant.)
D01200: First response storage word
D01100+0: 0015 hex No. of command data bytes
+1: 000F hex No. of response data bytes
+2: 0000 hex Remote (destination) network address = 0
+3: 3FFE hex Remote (destination) node address = 3F hex
Remote (destination) Unit address = FE hex (10 hex also possible)
+4: 0000 hex Response required, communications port No.0, No. of retries = 0 hex
+5: 0064 hex Response monitoring time
Response (Operation1)
D01200+0: 2801 hex Command code
+1: 0000 hex End code (FINS)
+2: 0009 hex No. of bytes received
+3: 00B6 hex Node address = 00 hex, Service code = B6 hex
+4: 0000 hex TC2 communications unit number = 00 hex, Sub-address
(fixed) = 00 hex
+5: 0001 hex End code (CompoWay/F) = 00 hex, MRC = 01 hex
+6: 0200 hex SRC = 02 hex, End code (FINS-mini) = 00 hex (2 bytes)
+7: 0000 hex End code (FINS-mini) = 00 hex (Lower byte (00 hex) is not relevant.)
113
Examples Using CompoWay/F Commands
Program Example (Operation 1)
A20011
000000
First Scan
Flag ON
Section 6-3
MOV(021)
0294
D1006
MOV(021)
0100
D1007
MOV(021)
0000
D1008
MOV(021)
0102
D1009
MOV(021)
0400
D1010
BSET(071)
0000
D1000
D1209
MOV(021)
2801
D1000
Sets 0000 in D1000 to D1209.
Sets 2801 in D1000. (Command code = 2801)
Sets 0036 in D1001.
(Slave node address = 00, ServiceCode = 36)
MOV(021)
0036
D1001
MOV(021)
0086
D1002
MOV(021)
0001
D1003
MOV(021)
0000
D1004
Sets 0086 in D1002. (ClassID = 86)
Sets 0001 in D1003. (InstanceID = 01)
Sets 0000 in D1004.
(TC2 Communications Unit No. = 00, sub-address = 00)
Sets 0001 in D1005. (SID = 00, MRC = 01)
MOV(021)
0001
D1005
Sets 0294 in D1006. (SRC= 02, variable type =94)
Sets 0100 in D1007. (Write address = 0003)
Sets 0000 in D1008.
(Bit position = 00, No. of elements = 00)
Sets 0102 in D1009. (No. of elements = 01. data = 00)
Sets 4000 in D1010. (data = 4000)
114
Examples Using CompoWay/F Commands
0 00013
A20011
First Scan
Flag ON
000020
0000 00 A 20200 151100
Execution condition
Network
Enabled
Flag
Online Flag
(Word n + 11, bit00)
0000 25
00 0001
A20200
A21900
Execution condition
Network
Enabled
Flag
Network
Execution
Error Flag
00 0030
Section 6-3
MO V(021)
# 0015
D1100
MO V(021)
# 000F
D1101
MO V(021)
# 0000
D1102
MO V(021)
# 3FFE
D1103
MO V(021)
# 0000
D1104
MO V(021)
# 0064
D1105
CMND(490)
D100 0
D120 0
D1 100
ASL(02 5)
0 000
MOV(02 1)
A203
D1 106
ASR( 026)
0000
END( 001)
Sets 0015 in D1100.
(No. of command data bytes =21)
Sets 000F in D1101.
(No. of response data bytes = 15)
Sets 0000 in D1102.
(Destination network address = 00)
Sets 3FFE in D1103.
(Destination node address = 3F, destination unit address = FE)
Sets 0000 in D1104.
(Response required, communications port No. = 0,
No. of retries = 0)
Sets 0064 in D1105.
(Response monitoring time = 10.0 s)
Sends 21 bytes of command data starting from D1000 to destination node address 00, and stores 16 bytes of response data in D1200 of the local node (D1100 or controller data)
Shifts the contents of CIO 0000 one bit to the left. (Turns ON CIO
000001.)
Stores A203 (network communications response code) in D1106.
Shifts the contents of CIO 0000 one bit to the right, and retries in the next cycle. (Turns ON CIO 000000.)
END
Operation 2 (Reading
PV)
• Reads the PV for TC2 unit number 0, ch1.
FINS-mini command: Reads the PV of ch1. MRC = 01 hex, SRC = 01 hex
(Read from Variable Area), variable type 00 hex, and read start address =
0000 hex.
• The data is read using the EXPLICIT MESSAGE SEND command (2801).
• The command data is written in DM words starting from D01020 in the
CPU Unit's memory, and the response data is stored in DM words starting from D01220.
• If the command does not end normally, the end code is stored in D01126 and the send command is re-executed.
Explicit Messages Command
Destination node address
00 hex
Service code
36 hex
Class ID Instance
ID
Communications
Unit No.
0086 hex 0001 hex 00 hex
Subaddress
00 hex
SID
00 hex
MRC
01 hex
SRC
01 hex
FINS-mini command text
Variable type
Address Bit position
84 hex 0000 hex 00 hex
No. of elements
0001 hex
Explicit Messages Response
No. of bytes received
Source node address
Service code
Communications
Unit No.
0B hex 00 hex B6 hex 00 hex
Subaddress
End code
00 hex 00 hex
MRC
01 hex
FINS-mini command text
SRC Response code
Read data
01 hex 0000 hex (Example)
000240 hex
115
Examples Using CompoWay/F Commands
Section 6-3
Command Details
(Operation 2)
[CMND S D C]
S
D
C
D01020+0: 2801 hex Command code
+1: 0036 hex DeviceNet Communications Unit node address = 00 hex
Service code = 36 hex
+2: 0086 hex Class ID = 0086 hex
+3: 0001 hex Instance ID = 01 hex
+4: 0000 hex TC2 communications unit number = 00 hex, subaddress (fixed) = 00 hex
+5: 0001 hex SID (fixed) = 00 hex, MRC = 01He x
+6: 01C0 hex SRC = 01 hex, variable type = C0 hex
+7: 0003 hex Read address = 0000 hex (2 bytes)
+8: 0000 hex Bit position (fixed) = 00 hex, No. of elements = 00 hex (2 bytes)
+9: 0100 hex No. of elements = 01 hex
D01220: First response storage word
D01120+0: 0013 hex No. of command data bytes
+1: 0013 hex No. of response data bytes
+2: 0000 hex Remote (destination) network address = 0
+3: 3FFE hex Remote (destination) node address = 3F hex
Remote (destination) Unit address FE hex (10 hex is also possible)
+4: 0000 hex Response required, communications port No. = 0,
No. of retries = 0 hex
+5: 0064 hex Response monitoring time
Response Details (Operation 2)
D01220+0: 2801 hex Command code
+1: 0000 hex End code (FINS)
+2: 000D hex No. of bytes received
+3: 00B6 hex Node address = 00 hex, service code = B6 hex
+4: 0000 hex TC2 communications unit number = 00 hex, sub-address
(fixed) = 00 hex
+5: 0001 hex End code (CompoWay/F), MRC = 01 hex
+6: 0100 hex SRC = 01 hex, end code (FINS-mini) = 00 hex (2 bytes)
+7: 0000 hex End code (FINS-mini) = 00 hex, read data = 00 hex
(4 bytes)
+8: 0002 hex Read data = 0002 hex
+9: 4000 hex Read data = 40 hex (rightmost 00 hex is ignored)
116
Examples Using CompoWay/F Commands
Program Example (Operation 2)
0 00000
A 20011
First Scan
Flag ON
Section 6-3
BSET(07 1)
# 0000
D1 020
D1229
MO V(021)
# 2801
D1020
MO V(021)
# 0036
D1021
MO V(021)
# 0086
D1022
MO V(021)
# 0001
D1023
MO V(021)
# 0000
D1024
MO V(021)
# 0001
D1025
MOV(021 )
# 01C0
D1 026
MOV(021 )
# 0000
D1 027
MOV(021 )
# 0000
D1 028
MO V(021)
# 0100
D1029
Sets 0000 (clears) in D1020 to D1229.
Sets 2801 in D1020. (Command code = 28 01)
Sets 0036 in D1021.
(Slave node address = 00, service code = 36)
Sets 0086 in D1022. (Class ID = 86)
Sets 0001 in D1023. (Instance ID = 01)
Sets 0000 in D1024.
(TC2 communications Unit No. = 00, sub-address = 00)
Sets 0001 in D1025. (SID = 00, MRC = 01)
Sets 01C0 in D1026.
(SRC = 01, variable type = C0)
Sets 0000 in D1027. (Read address = 0000)
Sets 0000 in D1028
(Bit position = 00, No. of elements = 00)
Sets 0100 in D1029. (Number of elements = 01)
117
Example of Sending Explicit Messages
A20011
First Scan
Flag ON
0 00029
00 0100 A20200 1511 00
Execution condition
Network
Enabled
Flag
Online Flag
(Word n+11, bit 00)
0 00101
A20200
A219 00
Execution condition
Network
Enabled
Flag
Network
Execution
Error Flag
Section 6-4
M OV(021)
# 0013
D1120
M OV(021)
# 0011
D1121
M OV(021)
# 0000
D1122
M OV(021)
# 3FFE
D1123
M OV(021)
# 0000
D1124
M OV(021)
# 0064
D1125
CMND(490 )
D1 020
D1 220
D1120
ASL( 025)
0001
MOV( 021)
A2 03
D 1126
AS R(026)
0001
EN D(001)
Sets 0013 in D1120.
(No. of command data bytes = 19)
Sets 0011 in D1121.
(No. of response data bytes = 17)
Sets 0000 in D1122.
(Destination network address = 00)
Sets 3FFE in D1123.
(Destination node address = 3F, destination Unit address = FE)
Sets 0000 in D1124.
(Response required, communications port No. = 0,
No. of retries = 0)
Sets 0064 in D1125.
(Response monitoring time = 10.0 s)
Sends 19 bytes of command data from D1020 to the destination node address 00, and stores 17 bytes of response data in D1220 of the local node. (D1120 or Controller)
Shifts the contents of CIO 0001 one bit to the left. (Turns ON CIO 000101.)
Stores A203 (network communications response code) in D1126.
Shifts the contents of CIO 0001 one bit to the right, and retries in next cycle. (CIO 000100 ON).
EN D
6-4 Example of Sending Explicit Messages
The following example shows when an explicit message is sent to the
DeviceNet Communications Unit from a CS1W-DRM21 Master Unit to read general status information for the DeviceNet Communications Unit.
DeviceNet Master Unit
(unit number 0, node address 04)
Using
CMND(490) instruction
PLC
Operation
Explicit message
General Status Read
DeviceNet Communications Unit
(node address 09)
• Reads the Unit status of the DeviceNet Communications Unit.
• Status information is read using the EXPLICIT MESSAGE SEND command (28 01).
• The information for the read results is as follows:
Temperature Controller Power Voltage Status Flag (bit 00) = 1 (Power
118
Sending Explicit Messages
Section 6-5
OFF), Communications Power Voltage Monitor Error Flag (bit 01) = 0
(normal), Unit Maintenance Flag (bit 03) = 0 (within range), Temperature
Controller Maintenance Flag (bit 07) = 0 (within range).
Explicit Message Command
Destination node address
09 hex
Service code
0E hex
Class ID
0095 hex
Instance ID
0001 hex
Attribute ID
65 hex
Explicit Message Response
No. of bytes received
03 hex
Source node address
09 hex 8E hex
Service code
01 hex
Data
• The command data is written in DM words starting from D01000 in the
CPU Unit memory, and the response data is stored in DM words starting from D02000.
• If the command does not end normally, the end code is stored in DM words D00006, and the send command is re-executed.
Command Details
[CMND S D C]
S
D
C
D01000+0: 2801 hex Command code
+1: 090E hex DeviceNet Communications Unit node address
Service code = 0E hex
+2: 0095 hex Class ID = 0095 hex
+3: 0001 hex Instance ID = 0001 hex
+4: 6500 hex Attribute ID = 65 hex
D02000: First response storage word
D00000+0: 0009 hex No. of command data bytes
+1: 0009 hex No. of response data bytes
+2: 0001 hex Remote (destination) network address = 1
+3: 04FE hex Remote (destination) node address = 4
Remote (destination) Unit address = FE hex (10 hex is also possible)
+4: 0000 hex Response required, communications port No. = 0,
No. of retries = 0 hex
+5: 003C hex Response monitoring time = 6 s
Response
D02000+0: 2801 hex Command code
+1: 0000 hex End code (FINS)
+2: 0003 hex No. of bytes received
+3: 098E hex Node address = 09 hex, service code = 8E hex
+4: 0100 hex Node address = 01 hex (rightmost 00 hex is ignored)
6-5 Sending Explicit Messages
The following list shows explicit messages that can be sent to the DeviceNet
Communications Unit. These messages are used to read and write maintenance information (such as Unit conduction time or total RUN time) for the
DeviceNet Communications Unit and Temperature Controllers.
For details on sending explicit messages from an OMRON Master PLC, refer to the corresponding DeviceNet Master Unit operation manual.
119
Sending Explicit Messages
Section 6-5
Note The number of digits used for Class ID, Instance ID, and Attribute 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
6-5-1 Reading General Status
Explicit message
General
Status
Read
Read
/write
Function
Read Reads the Unit status bits of the DeviceNet
Communications Unit
(8 bits). (Refer to
Command
Service code
Class ID Instance
0E hex 95 hex
ID
01 hex
Attribute
ID
65 hex ---
Data size
Response
1 byte
6-5-2 Setting and Monitoring the Unit Conduction Time
Explicit message
Unit Maintenance Bit
Read
/write
Read Reads the monitor status of the Communications Unit conduction time.
Function
Unit Maintenance Set
Value
Unit Maintenance
Present
Value
Read Reads the set value
(monitor value) for the
DeviceNet Communications Unit conduction time (unit: 0.1 h).
Write Writes the set value
(monitor value) for the
DeviceNet Communications Unit conduction time (unit: 0.1 h).
Read Reads the PV for the
DeviceNet Communications Unit conduction time (unit: 0.1 h).
Service code
Class ID Instance
0E hex 95 hex
Command
ID
01 hex
Attribute
ID
73 hex ---
Data size
10 hex
0E hex
0E hex
95 hex
95 hex
95 hex
01 hex
01 hex
01 hex
73 hex
71 hex
72 hex ---
Response
4 bytes
00000000 to
FFFFFFFF hex (0 to
4294967295)
---
4 bytes
00000000 to
FFFFFFFF hex
(0 to
4294967295)
---
4 bytes
00000000 to
FFFFFFFF hex
(0 to
4294967295
1 byte
00 hex: Within range
01 hex: Out of range (monitor value exceeded)
6-5-3 Writing Maintenance Mode Information
Explicit message
Maintenance
Counter
Save
Read
/write
Function
Save Records the maintenance counter (PV of total ON/RUN time for all Temperature Controllers) in the
DeviceNet Communications Unit's memory.
Service code
16 hex
Command
Class ID Instance
ID
Attribute
ID
95 hex 01 hex 75 hex ---
Data size
---
Response
120
Sending Explicit Messages
Section 6-5
6-5-4 Setting and Monitoring Temperature Controller Channels
Explicit message
Temperature Controller
Channel
Maintenance Information
Monitor
Mode
Set Value for Unit
Conduction
Time or
Total RUN
Time
Read
/write
Function
Read Reads the monitor mode for maintenance information of the Temperature Controller unit number and channel
(see note 1) specified by the Instance ID (1 to
64).
Write Writes the monitor mode for maintenance information of the Temperature Controller unit number and channel
(see note 1) specified by the Instance ID (1 to
64).
Read Reads the set value
(monitor value) for the
Unit conduction time or total RUN time (unit: s) of the Temperature
Controller unit number and channel (see note
1) specified by the
Instance ID (1 to 64).
Command
Service code
Class ID Instance
ID
0E hex 7A hex 01 to 40 hex
Attribute
ID
65 hex ---
Data size
10 hex 7A hex 01 to 40 hex
0E hex 7A hex 01 to 40 hex
65 hex
68 hex
1 byte
00 hex: Unit conduction time mode
01 hex: Total
RUN time mode
---
68 hex
1 byte
00 hex: Unit conduction time mode
01 hex: Total
RUN time mode
---
4 bytes
00000000 to
FFFFFFFF hex
(0 to
4294967295)
4 bytes
00000000 to
FFFFFFFF hex (0 to
4294967295)
---
Response
Unit Conduction
Time or
Total RUN
Time Read
Monitor
Status of
Unit Conduction
Time or
Total RUN
Time Read
Write Writes the set value
(monitor value) for the
Unit conduction time or total RUN time (unit: s) of the Temperature
Controller unit number and channel (see note
1) specified by the
Instance ID (1 to 64).
Read Reads the PV for the
Unit conduction time or total RUN time (unit: s) of the Temperature
Controller unit number and channel (see note
1) specified by the
Instance ID (1 to 64).
Read Reads the monitor status for the Unit conduction time or total RUN time (unit: s) of the
Temperature Controller unit number and channel (see note 1) specified by the
Instance ID (1 to 64).
10 hex 7A hex 01 to 40 hex
0E hex 7A hex 01 to 40 hex
0E hex 7A hex 01 to 40 hex
66 hex
67 hex
---
---
4 bytes
00000000 to
FFFFFFFF hex
(0 to
4294967295)
1 byte
00 hex: Within range
01 hex: Out of range (monitor value exceeded)
121
13 (0D hex)
14 (0E hex)
15 (0F hex)
16 (10 hex)
17 (11 hex)
18 (12 hex)
19 (13 hex)
20 (14 hex)
21 (15 hex)
22 (16 hex)
23 (17 hex)
24 (18 hex)
25 (19 hex)
26 (1A hex)
27 (1B hex)
28 (1C hex)
29 (1D hex)
30 (1E hex)
31 (1F hex)
32 (20 hex)
Instance ID
01 (01 hex)
02 (02 hex)
03 (03 hex)
04 (04 hex)
05 (05 hex)
06 (06 hex)
07 (07 hex)
08 (08 hex)
09 (09 hex)
10 (0A hex)
11 (0B hex)
12 (0C hex)
Sending Explicit Messages
Section 6-5
Note The following table shows the relationship between the Instance IDs (01 to 64)
and the Temperature Controller communications unit numbers (0 to 15) and channels (1 to 4).
Unit 3, ch1
Unit 3, ch2
Unit 3, ch3
Unit 3, ch4
Unit 4, ch1
Unit 4, ch2
Unit 4, ch3
Unit 4, ch4
Unit 5, ch1
Unit 5, ch2
Unit 5, ch3
Unit 5, ch4
Unit 6, ch1
Unit 6, ch2
Unit 6, ch3
Unit 6, ch4
Unit 7, ch1
Unit 7, ch2
Unit 7, ch3
Unit 7, ch4
Unit No., channel
Unit 0, ch1
Unit 0, ch2
Unit 0, ch3
Unit 0, ch4
Unit 1, ch1
Unit 1, ch2
Unit 1, ch3
Unit 1, ch4
Unit 2, ch1
Unit 2, ch2
Unit 2, ch3
Unit 2, ch4
45 (2D hex)
46 (2E hex)
47 (2F hex)
48 (30 hex)
49 (31 hex)
50 (32 hex)
51 (33 hex)
52 (34 hex)
53 (35 hex)
54 (36 hex)
55 (37 hex)
56 (38 hex)
57 (39 hex)
58 (3A hex)
59 (3B hex)
60 (3C hex)
61 (3D hex)
62 (3E hex)
63 (3F hex)
64 (40 hex)
Instance ID
33 (21 hex)
34 (22 hex)
35 (23 hex)
36 (24 hex)
37 (25 hex)
38 (26 hex)
39 (27 hex)
40 (28 hex)
41 (29 hex)
42 (2A hex)
43 (2B hex)
44 (2C hex)
Unit 11, ch1
Unit 11, ch2
Unit 11, ch3
Unit 11, ch4
Unit 12, ch1
Unit 12, ch2
Unit 12, ch3
Unit 12, ch4
Unit 13, ch1
Unit 13, ch2
Unit 13, ch3
Unit 13, ch4
Unit 14, ch1
Unit 14, ch2
Unit 14, ch3
Unit 14, ch4
Unit 15, ch1
Unit 15, ch2
Unit 15, ch3
Unit 15, ch4
Unit No., channel
Unit 8, ch1
Unit 8, ch2
Unit 8, ch3
Unit 8, ch4
Unit 9, ch1
Unit 9, ch2
Unit 9, ch3
Unit 9, ch4
Unit 10, ch1
Unit 10, ch2
Unit 10, ch3
Unit 10, ch4
122
Sending Explicit Messages
Section 6-5
6-5-5 Copy Function
Explicit message
Read/ write
Function Command
Service code
Class
ID
Instance
ID
10 hex 95 hex 01 hex
Attribute
ID
COPY Write Uploads or downloads settings of the Temperature Controller connected to the
DeviceNet Communications Unit. (Refer to
STATUS Read Reads the operating status of the copy function.
0E hex 71 hex 01 hex 66 hex ---
Data size
C6 hex 1 byte
00 hex: Upload
01 hex: Download
---
Response
6 bytes (Bit 1 of the leftmost byte is the operating status. The rightmost byte is the results.)
1,2,3...
Use the following procedure to execute the copy function.
1.
Send the COPY command.
2.
After receiving the response, wait for processing to be completed (approx.
10 s per Temperature Controller).
3.
Read the status to confirm that the copy function is stopped. If bit 1 of the leftmost byte is ON, the copy function is still being executed. If it is OFF, the copy function is stopped.
4.
Read the status again and confirm the results (rightmost byte). The meaning of each bit of the rightmost byte is as follows:
Bit 0: ON for a normal end. (OFF for an error end or when the copy function has not been executed.)
Bit 1: OFF
Bit 2: ON if a communications error occurred when starting the upload or download.
Bit 3: ON if an EEPROM hardware error or checksum error occurred when starting the upload or download.
Bit 4: ON if a communications error occurred when executing the upload or download.
Bit 5: ON if there was no backup data to download.
Bit 6: ON if the backup data configuration does not match the actual configuration for an upload or download.
Bit 7: OFF
123
Sending Explicit Messages
Section 6-5
124
SECTION 7
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.
7-1 Remote I/O Communications Characteristics. . . . . . . . . . . . . . . . . . . . . . . . .
7-1-1 I/O Response Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-1-2 CompoWay/F Communications Cycle Time and Refresh Time . . .
7-1-3 More than One Master in Network . . . . . . . . . . . . . . . . . . . . . . . . . .
7-1-4 System Startup Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-2 Message Communications Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-2-1 Message Communications Time. . . . . . . . . . . . . . . . . . . . . . . . . . . .
125
Remote I/O Communications Characteristics
Section 7-1
7-1 Remote I/O Communications Characteristics
This section describes the characteristics of DeviceNet remote I/O communications when OMRON Master and Slave Units are being used. Use this section for reference when planning operations that require precise I/O timing.
The equations provided here are valid under the following conditions:
• The Master Unit is operating with the scan list enabled.
• All of the required slaves are participating in communications.
• No errors are being indicated at the Master Unit.
• Messages are not being produced in the Network (from another company's configurator, for example).
Note The values provided by these equations may not be accurate if another com-
pany's master or slave is being used in the Network.
7-1-1 I/O Response Time
The I/O response time is the time it takes from the reception of an input signal at an Input Slave to the output of the corresponding output signal at an Output
Slave after being processed by the ladder program at the master.
CVM1- and CV-series PLCs (Asynchronous Mode)
Minimum I/O Response
Time
The minimum I/O response time occurs when the DeviceNet Master Unit refreshing is executed just after the input signal is received by the master and instruction execution is completed within one peripheral servicing cycle.
Instruction execution cycle time
PLC cycle (instruction execution cycle)
Instruction execution
PLC cycle (peripheral servicing cycle)
Peripheral servicing cycle time
Master Unit processing
Input
Output
T
IN
T
RT-IN
T
PLC2
T
RT-OUT
T
OUT
T
IN
:
T
OUT
:
The Input Slave's ON (OFF) delay (Minimum value: 0)
The Output Slave's ON (OFF) delay (Minimum value: 0)
T
RT-IN
: The Input Slave's communications time/slave
T
RT-OUT
: The Output Slave's communications time/slave
T
PLC2
: The PLC's peripheral servicing cycle time
126
Remote I/O Communications Characteristics
Section 7-1
Maximum I/O Response
Time
Note Refer to the information on each slave for details on Input and Output Slaves'
ON and OFF delay times. Refer to 7-1-2 CompoWay/F Communications
Cycle Time and Refresh Time and the Operation Manual for the PLC being
used for details on the PLC's peripheral servicing cycle time.
The minimum I/O response time (T
MIN
) is the total of the following terms:
T
MIN
= T
IN
+ T
RT-IN
+ T
PLC2
+ T
RT-OUT
+ T
OUT
The maximum I/O response time occurs with the I/O timing shown in the following diagram.
PLC cycle (instruction execution cycle)
Instruction execution cycle time
Instruction execution
Instruction execution
PLC cycle (peripheral servicing cycle)
Peripheral servicing cycle time
Master Unit processing
Input
Output
T
IN
T
RM
T
PLC2
T
PLC1
T
PLC2
T
IN
: The Input Slave's ON (OFF) delay
T
OUT
: The Output Slave's ON (OFF) delay
T
RM
T
OUT
T
RM
:
The whole Network's communications cycle time (Refer to page 131.)
T
PLC1
: The PLC's instruction execution cycle time
T
PLC2
: The PLC's peripheral servicing cycle time
Note Refer to the information on each slave for details on Input and Output Slaves'
ON and OFF delay times. Refer to 7-1-2 CompoWay/F Communications
Cycle Time and Refresh Time and the Operation Manual for the PLC being
used for details on the PLC's peripheral servicing cycle time.
The maximum I/O response time (T
MAX
) is the total of the following terms:
T
MAX
= T
IN
+ 2 × T
RM
+ T
PLC1
+ 2 × T
PLC2
+ T
OUT
127
Remote I/O Communications Characteristics
Section 7-1
CVM1- and CV-series PLCs (Synchronous Mode)
Minimum I/O Response
Time
The minimum I/O response time occurs with the I/O timing shown in the following diagram.
Cycle time
PLC
Peripheral servicing
Instruction execution
Peripheral servicing
Instruction execution
Peripheral servicing
Instruction execution
Master Unit
Input
Output
T
IN
T
RT-IN+
T
PLC0
T
PLC0
T
RT-OUT
T
OUT
T
IN
:
T
OUT
:
The Input Slave's ON (OFF) delay (Minimum value: 0)
The Output Slave's ON (OFF) delay (Minimum value: 0)
T
RT-IN
: The Input Slave's communications time/slave
T
RT-OUT
: The Output Slave's communications time/slave
T
PLC0
: The PLC's cycle time (instruction execution + peripheral servicing)
Note Refer to the information on each slave in SECTION 5 to SECTION 7 for
details on Input and Output Slaves' ON and OFF delay times. Refer to 7-1-2
CompoWay/F Communications Cycle Time and Refresh Time and the Opera-
tion Manual for the PLC being used for details on the PLC's cycle time.
The minimum I/O response time (T
MIN
) is the total of the following terms:
T
MIN
= T
IN
+ T
RT-IN
+ 2 × T
PLC0
+ T
RT-OUT
+ T
OUT
128
Remote I/O Communications Characteristics
Maximum I/O Response
Time
Section 7-1
The maximum I/O response time occurs with the I/O timing shown in the following diagram.
PLC
Cycle time
Peripheral servicing
Instruction execution
Peripheral servicing
Instruction execution
Peripheral servicing
Instruction execution
Peripheral servicing
Instruction execution
Master Unit
Input
Output
T
IN
T
IN
:
T
RM+
T
PLC0
T
PLC0
The Input Slave's ON (OFF) delay
T
PLC0
T
RM
T
OUT
T
OUT
: The Output Slave's ON (OFF) delay
T
RM
: The whole Network's communications cycle time (Refer to
T
PLC0
: The PLC's cycle time (instruction execution + peripheral servicing)
Note Refer to the information on each slave for details on Input and Output Slaves'
ON and OFF delay times. Refer to 7-1-2 CompoWay/F Communications
Cycle Time and Refresh Time and the Operation Manual for the PLC being
used for details on the PLC's instruction execution and peripheral servicing cycle times.
The maximum I/O response time (T
MAX
) is the total of the following terms:
T
MAX
= T
IN
+ 2 × T
RM
+ 3 × T
PLC0
+ T
OUT
129
Remote I/O Communications Characteristics
Section 7-1
CS, CJ, C200HX/HG/HE (-Z), and C200HS PLCs
Minimum I/O Response
Time
The minimum I/O response time occurs when the DeviceNet Slave I/O refreshing is executed just after the input signal is received by the master and
I/O is refreshed for the slave first in the next I/O refresh cycle.
T
PLC
T
RF
PLC
Instruction execution
Master Unit
Input
Output
T
IN
T
RT-IN
(T
PLC
− T
RF
) T
RT-OUT
T
OUT
T
IN
: The Input Slave's ON (OFF) delay (Minimum value: 0)
T
OUT
: The Output Slave's ON (OFF) delay (Minimum value: 0)
T
RT-IN
: The Input Slave's communications time/slave
T
RT-OUT
: The Output Slave's communications time/slave
T
PLC
: The PLC's cycle time
T
RF
: The PLC's DeviceNet Unit refresh time
Note Refer to the information on each slave for details on Input and Output Slaves'
ON and OFF delay times. Refer to 7-1-2 CompoWay/F Communications
Cycle Time and Refresh Time and the Operation Manual for the PLC being
used for details on the PLC's cycle time.
The minimum I/O response time (T
MIN
) is the total of the following terms:
T
MIN
= T
IN
+ T
RT-IN
+ (T
PLC
− T
RF
) + T
RT-OUT
+ T
OUT
130
Remote I/O Communications Characteristics
Maximum I/O Response
Time
PLC
Section 7-1
The maximum I/O response time occurs with the I/O timing shown in the following diagram.
Instruction execution
Instruction execution
Instruction execution
Master Unit
Input
Output
T
IN
T
RM
T
PLC
T
PLC
T
RF
T
RM
T
IN
:
T
RM
:
The Input Slave's ON (OFF) delay
T
OUT
: The Output Slave's ON (OFF) delay
The whole Network's communications cycle time
T
PLC
: The PLC's cycle time
T
RF
: The PLC's DeviceNet Unit refresh time
T
OUT
Note Refer to the information on each slave for details on Input and Output Slaves'
ON and OFF delay times. Refer to 7-1-2 CompoWay/F Communications
Cycle Time and Refresh Time and the Operation Manual for the PLC being
used for details on the PLC's cycle time.
The maximum I/O response time (T
MAX
) is the total of the following terms:
T
MAX
= T
IN
+ 2 × T
RM
+ 2 × T
PLC
+ T
RF
+ T
OUT
7-1-2 CompoWay/F Communications Cycle Time and Refresh Time
This section explains the communications cycle time and refresh processing time required to calculate various processing times for DeviceNet.
Communications
Cycle Time
Communications Cycle
Time Reference Values
The communications cycle time is the time from the completion of a slave's
I/O communications processing until I/O communications with the same slave are processed again. The communications cycle time of the DeviceNet Communications Unit is the maximum CompoWay/F communications cycle time
T
IN
+ T
OUT
.
Reference values for CompoWay/F communications cycle time are given below.
Total communications cycle time = IN communications cycle time + OUT communications cycle time.
TIN TOUT
1
8
No. of Temperature
Controllers
16
100 ms
400 ms
900 ms
100 ms
700 ms
1,200 ms
131
Remote I/O Communications Characteristics
Section 7-1
Note The measurement conditions are as follows:
Baud rate: 500 kbps
I/O allocation: Same as simple I/O allocation
Temperature Controller: TC2
The values above are reference values, not maximum values. The communications cycle time depends on the number of Temperature Controllers connected and the type or number of the parameters allocated to I/O.
Refresh Time
The refresh time is the time required for I/O data to be exchanged between the PLC's CPU Unit and the DeviceNet Master Unit. The PLC's cycle time is increased when a Master Unit is mounted, as shown below.
Note Refer to the PLC's Operation Manual for more details on the refresh time and
the PLC's cycle time.
Master Unit for CV-series
PLCs
The PLC's cycle time (CPU Bus Unit servicing) is increased by the amount shown in the following table when a Master Unit is mounted to the PLC.
Process Processing time
CPU Bus Unit servicing DeviceNet Unit refreshing: 1.1 ms
Master Unit for CS/CJseries, C200HX/HG/HE (-
Z), and C200HS PLCs
The PLC's cycle time (I/O refreshing) is increased by the amount shown in the following table when a Master Unit is mounted to the PLC.
Process
I/O refreshing
Processing time
DeviceNet Unit I/O refreshing:
Using Master Unit for CS/CJ-series, and C200HX/HG/HE
(-Z) PLCs
1.72 + 0.022 × number of words (ms) (See note.)
Using Master Unit for C200HS PLCs
2.27 + 0.077 × number of words (ms) (See note.)
Note The number of words refreshed is the total number of words in the I/O Area
that are allocated to the slaves, including any unused words between those words actually used by the slaves.
For example, if there are only two Input Slaves with node addresses 1 and 5, the 5 input words for nodes 1 through 5 would be refreshed even though the input words for nodes 2, 3, and 4 are unused.
If message communications are being performed, just add the number of words used in message communications to the above number of words for whenever messages are being processed.
7-1-3 More than One Master in Network
The following equation shows the communications cycle time (T
RM
) when there is more than one master in the Network.
An example for two Master Units is shown here.
132
Remote I/O Communications Characteristics
Section 7-1
First, the Network is divided into two groups: Master A and the slaves in remote I/O communications with it, and Master B and the slaves in remote I/O communications with it.
Group A
Group B
Master A
Master B
Slave a Slave b
Slave c
Slaves in remote I/O communications with Master A
Slave d
Slave e
Slave f
Slaves in remote I/O communications with Master B
Note Although in the above diagram the slaves are separated into two separate
groups for each master for convenience, the actual physical positions of the slaves in the Network are irrelevant.
Next, refer to 7-1-2 CompoWay/F Communications Cycle Time and Refresh
Time and calculate the communications cycle time for each group as if they
were separate Networks.
Group A Group B
Master A Master B
Slave a
Slave b
Slave c Slave d
Slave e
Slave f
Communications cycle time for
Group A: T
RM-A
Communications cycle time for
Group B: T
RM-B
In Networks with two masters, the communications cycle time for the entire
Network will be the sum of the communications cycle times for both groups.
T
RM
= T
RM-A
+ T
RM-B
Although this example shows only two masters in the Network, the total communications cycle time for any Network with more than one master can be calculated by dividing it into groups performing remote I/O communications and adding the communications cycle times of all the groups.
7-1-4 System Startup Time
This section describes the system startup time for a Network, assuming that the scan list is enabled and that remote I/O 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 I/O communications 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
NS indicator is OFF or flashing green. 11 s The master is started immediately after slave startup.
133
Message Communications Characteristics
Section 7-2
Condition
The master only is restarted.
The slaves only are restarted.
Slave's indicator status System startup time
8 s
-
NS indicator is flashing red or green while the master is OFF.
11 s
Program Example
As shown in the preceding table, it takes time for DeviceNet communications to start up. This programming uses flags in the Master Status Area to prevent the slaves' I/O processing from being performed until the Master Unit and remote I/O communications have started up.
Note Refer to the operation manual of the Master Unit being used for details on the
Master Unit Status Area.
The following program example is for a CS/CJ-series PLC and a Master Unit with a unit number of 00.
2001
15
2001
14
(004)
JMP #0001
I/O Data
Communications
Flag
Error/
Communications
Stopped Flag
Slave's I/O processing
(005)
JME #0001
7-2 Message Communications Characteristics
7-2-1 Message Communications Time
The message communications time is the time required from the time a Master Unit starts to send a message over the Network to another node until the
Master Unit completes sending the message (SEND/RECV instructions to send/receive data and CMND/IOWR instructions to execute FINS commands).
Note If the CPU Unit attempts to send another message or receives a message
from another node before the message communications time has finished, the response message being sent or the message being received from another node may be destroyed. Always perform message communications at intervals longer than the message communications time and use message instructions (SEND, RECV, CMND, and IOWR). Never send messages to any one node at intervals less than the message communications time.
If send or receive messages are destroyed, the error record will be placed in the error history of the Master Unit. If an error occurs, read the error history using the FINS command or monitor the error history from the Configurator.
The following equation can be used to calculate the approximate message communications time.
Message communications time = Communications cycle time
× ((No. of message bytes + 15) ÷ 6 + 1)
134
Message Communications Characteristics
Section 7-2
The number of message bytes is the number of data bytes following the FINS command code. The communications cycle time depends on whether remote
I/O communications are being used.
Message Communications Only (Remote I/O Communications Not Used)
Message communications time = 2 (see note) + 0.11 × T
B
+ 0.6 (ms)
T
B
: Baud rate (500 kbps: T
B
= 2; 250 kbps: T
B
= 4; 125 kbps: T
B
= 8)
Note The communications cycle when remote I/O communications are not being
used is 2 ms.
Message Communications with Remote I/O Communications
Communications cycle time = (Communications cycle time for remote I/O communications only) + 0.11 × T
B
+ 0.6 (ms)
T
B
: Baud rate (500 kbps: T
B
= 2; 250 kbps: T
B
= 4; 125 kbps: T
B
= 8)
Note The above equations can be used to find the approximate message communi-
cations time, but not the maximum time. The message communications time will depend on the frequency of the message communications, the load on the remote node, the communications cycle time, and other factors. For any one
Master Unit, the message communications time may be greatly increased due to heavy loads.
135
Message Communications Characteristics
Section 7-2
136
SECTION 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 Units 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.
137
Indicators and Error Processing
Section 8-1
8-1 Indicators and Error Processing
The following table lists the indicator status when errors occur, the probable causes and processing.
Indicator status
MS: OFF
NS: OFF
MS: Flashing green
NS: No change
MS: Flashing red
NS: No change
Probable cause
The power is not being supplied to the Unit.
The power voltage is not within the permitted range.
Remedy
Supply communications power from the DeviceNet Communications connector.
Use a power supply voltage within the permitted range.
The Unit is faulty.
The Temperature Controller connection configuration is not registered.
A sum error has occurred in the parameters registered in
EEPROM.
A EEPROM hardware error has occurred.
The Unit is faulty
Replace the Unit.
If I/O allocations are to be set using the Configurator, register the Temperature Controller connection configura-
tion. (Refer to pages 45 to 68).
Use the Configurator’s device monitor to check the parameters with the sum error or logic error, and reset the parameters.
Replace the Unit.
Replace the Unit.
MS: ON red
NS: OFF
MS: ON green
NS: Flashing green
MS: ON green
NS: ON red
MS: ON green
NS: Flashing red
Waiting to connect to
DeviceNet communications.
The Unit is faulty.
The DeviceNet is in Bus
Off status.
Check the following items and restart the Unit.
• 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?
Replace the Unit.
Check the following items and restart the Unit.
• 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?
Reset node addresses correctly.
Node addresses duplicated.
The Unit is faulty.
A communications timeout has occurred.
The Unit is faulty.
Replace the Unit.
Check the following items and restart the Unit.
• 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?
Replace the Unit.
138
Maintenance
Section 8-2
Indicator status
TS: OFF
TS: Flashing red
TS: Flashing red
(Flashes for 10 s only.)
Probable cause
Communications with the Temperature Controllers have stopped.
The Unit is faulty.
One or more of the connected Temperature
Controllers is faulty.
Remedy
Set the Temperature Controller connection configuration.
Replace the Unit.
Replace the faulty Temperature Controllers. Check the communications status and communications error status to detect which Temperature Controller is faulty.
One or more of the connected Temperature
Controllers has been disconnected.
The communications unit number of one or more Temperature Controllers registered in the connection configuration is incorrect.
Pin 1 of the DIP switch is set incorrectly.
Connect the Temperature Controllers correctly. Check the communications status and communications error status to detect which Temperature Controller is disconnected.
Change the communications unit number of the Temperature Controller or register the connection configuration correctly.
Power is not being supplied to the End Unit.
The Unit is faulty.
Set correctly as follows:
Pin 1 ON: Simple I/O allocation
Pin 1 OFF: I/O allocation using the
Configurator
Supply 24-VDC power to the End
Unit.
Replace the Unit.
A communications error occurred with the Temperature Controller when copy was executed.
The settings downloaded for a Temperature Controller configuration that is different from that used when uploading.
• Check whether the Units are connected together properly. Refer to the EJ1 User’s Manual (Cat. No.
H142).
• If distributed placement is used, check the connection of port B on the End Unit.
Use the same Temperature Controller configuration for downloading that was used when uploading.
8-2 Maintenance
This section describes the routine cleaning and inspection recommended as regular maintenance. Handling methods when replacing Units are also explained here.
8-2-1 Cleaning
Clean the DeviceNet Units regularly as described below in order to keep the
Network in its optimal operating condition.
• Wipe the Unit 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 Unit.
• Smudges may remain on the Unit from gum, vinyl, or tape that was left on for a long time. Remove these smudges when cleaning.
139
Maintenance
Section 8-2
Note Never use volatile solvents, such as paint thinner or benzene, or chemical
wipes to clean the Unit. These substances may damage the surface of the
Unit.
8-2-2 Inspection
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 frequently if the system is used in high-temperature, humid, or dusty conditions.
Inspection Equipment
Prepare the following equipment before inspecting the system.
Equipment Required for
Regular Inspection
A flat-blade and a Phillips screwdriver, a screwdriver for connecting communications connectors, a tester (or a digital voltmeter), industrial alcohol, and a clean cloth are required for routine inspection.
Other Equipment that May
Be Required
A synchroscope, oscilloscope, thermometer, or hygrometer may be required.
Inspection Procedure
Check the items in the following table and correct any condition that is below standard by adjusting the Unit or improving the environmental conditions.
Inspection item
Environmental conditions
Installation conditions
Details
Are ambient and cabinet temperatures correct?
Are ambient and cabinet humidity correct?
Has dust or dirt accumulated?
−
Standard
10 to +55
°
C
25% to 85%
No dust or dirt
Are the Units installed securely?
Are the connectors of the communications cables fully inserted?
No looseness
No looseness
Are the external wiring screws tight?
No looseness
Are the connecting cables undamaged?
No external damage
Equipment
Thermometer
Hygrometer
Visual inspection
Phillips screwdriver
Phillips screwdriver
Phillips screwdriver
Visual inspection
8-2-3 Replacing Units
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.
Precautions
Observe the following precautions when replacing a faulty Unit.
• After replacement make sure that there are no errors with the new Unit.
• When a Unit is being returned for repair, attach a sheet of paper detailing the problem and return the Unit to your OMRON dealer
• If there is a faulty contact, try wiping the contact with a clean, lint-free cloth dampened with alcohol.
Note Before replacing a Unit, always stop Network communications and turn OFF
the power to all the nodes in the Network.
Settings after
Replacing a Unit
Note
After replacing a Unit, set the new Unit's switches to the same settings that were on the old Unit. Connect the same model of DeviceNet Communications
Unit to the Temperature Controllers as the previous Unit.
1.
By backing up the settings of the DeviceNet Communications Unit and the
Temperature Controllers, the settings can be reset in a batch. For details
140
Maintenance
Reading/Writing
Temperature
Controller Settings
Using Copy Mode
Note
Read Setting Parameters
(Upload)
Section 8-2
on the device parameters upload and download functions, refer to the De-
viceNet Configurator Ver. 2@ Operation Manual (Cat. No. W382).
2.
When replacing a Temperature Controller, the DeviceNet Communications
Unit copy mode can be used to easily reset the Temperature Controller onsite without requiring the Configurator. For details, refer to Reading/Writing
Temperature Controller Settings Using Copy Mode below.
The DeviceNet Communications Unit has a copy function that can read or write the setting parameters of all the Temperature Controllers connected to the Unit in a batch (the read setting parameters are recorded in the DeviceNet
Communications Unit).
When a Temperature Controller has been replaced, the copy function allows the Temperature Controller to be easily reset onsite without using a Configurator.
1.
The parameters of the G3ZA and G3PW are not backed up. If backup is required, use the CX-Thermo to back up the parameters.
2.
Once a system using a DeviceNet Communications Unit is operating properly, it is recommended to read the Temperature Controller parameters using the copy function at the same time as the device parameters are saved using the Configurator.
3.
The copy function can be used with explicit messages also. For details, re-
Use this function to upload the setting parameters from the Temperature Controllers to the DeviceNet Communications Unit.
Uploading
10
NODE
ADR
1
MAX
No.
2 3
9 8 7 6
23
2 3
9 8 7 6
MS
NS
TS
COPY
EDS
UP/DN
NO
DeviceNet
Communications
Unit
Temperature Controllers
1,2,3...
■ Execution Condition
There can be no communications error (TS indicator is not flashing red).
■ Procedure
1.
Turn OFF pin 3 (UP/DN) of the DIP switch of the DeviceNet Communications Unit.
2.
Toggle pin 6 of the of the DIP switch of the DeviceNet Communications
Unit from OFF to ON (leave ON for 1 to 5 seconds) and then turn OFF again (while pin 6 is ON, the TS indicator will be lit green). The data will start uploading and the TS indicator will flash green. (Approx. 10 s is required for each Temperature Controller.)
141
Maintenance
Section 8-2
Start copying
Copy operation mode setting
NO
Turn OFF pin 3
TS
Indicators
Lit green
NO
Leave pin 6 ON for 1 to 5 s
TS
Lit green
NO
TS
Flashing green
Write Setting Parameters
(Download)
Note
■ Execution Results
• If the uploading completes normally, the TS indicator status will return to be lit green.
• If the upload operation ends abnormally, after error completion, the TS indicator will flash red for 10 seconds.
1.
For the upload operation, when pin 6 (copy) is turned ON, and then OFF again, the TS indicator will flash green. Check that the TS indicator is flashing green during the upload operation.
2.
To cancel an upload operation, leave pin 6 (copy) ON for at least 5 seconds, and then turn OFF again.
Use this function to download the setting parameters from the DeviceNet
Communications Unit to the Temperature Controllers.
Downloading
10
NODE
ADR
1
2
3
9 8 7 6
MAX
No.
2 3
9 8 7 6
MS
NS
23
4 567
TS
COPY
EDS
UP/DN
NO
DeviceNet
Communications
Unit
Temperature Controllers
Note While downloading, refresh processing of I/O data will stop, and the data
immediately before being copied will be held in the IN Area of the DeviceNet
Communications Unit. Explicit message communications will stop, so a timeout error may occur.
An error will occur for explicit message communications except for the STA-
TUS explicit message.
■ Execution Condition
• Data for the same connection configuration (model, unit number) has been uploaded to the DeviceNet Communications Unit.
• There can be no communications error (TS indicator is not flashing red).
■ Procedure
1,2,3...
1.
Turn ON pin 3 (UP/DN) of the DIP switch of the DeviceNet Communications Unit.
142
Maintenance
Section 8-2
2.
Toggle pin 6 of the of the DIP switch of the DeviceNet Communications
Unit from OFF to ON (leave ON for 1 to 5 seconds) and then turn OFF again (while pin 6 is ON, the TS indicator will be flashing green). The data will start downloading and the TS indicator will flash green. (Approx. 10 s is required for each Temperature Controller.)
Start copying
Copy operation mode setting
Indicators
NO
Turn ON pin 3
TS
NO
Leave pin 6 ON for 1 to 5 s
TS
NO
TS
Lit green Flashing green Flashing green
Note
■ Execution Results
• When the download completes normally, the TS indicator status returns to be lit green.
• When the download operation ends abnormally, after error completion, the TS indicator will flash red for 10 s.
1.
For the download operation, when pin 6 (copy) is turned ON, the TS indicator will flash green (indicating download standby). Check that the TS indicator is flashing green before turning OFF pin 6 (copy) again.
2.
To cancel a download operation, leave pin 6 (copy) ON for at least 5 seconds, and then turn OFF again.
3.
Check that data is downloading by confirming that the TS indicator flashes green after pin 6 (copy) is turned OFF.
143
Maintenance
Section 8-2
144
Appendix A
Connecting to a Master from Another
Company
This appendix explains how to operate the DeviceNet Communications Unit when it is connected to a master manufactured by another company.
Using a Configurator Manufactured by Another Company
This section explains how to use an EDS file with a Configurator manufactured by another company.
Setting the DeviceNet Communications Unit
Set DIP switch pin 4 on the DeviceNet Communications Unit to ON (to use a Configurator manufactured by another company).
Support Software selector
NO
Turn ON DIP switch pin 4.
Installing an EDS File
Download the EDS file for the DeviceNet Communications Unit from the product guide on the following website and install it in the configurator manufactured by another company. For the installation procedure, refer to the manual of the configurator you are using.
http://www.odva.org/
Note This EDS file cannot be used with the OMRON Configurator. For the OMRON Configurator, always
install the expansion module.
Settings
Settings are divided into the following groups.
Unit
Group name
IN1 Area
IN2 Area
OUT Area
#00 ch1
#00 ch2
---
#15 ch4
General setting
Description
Sets the model of Temperature Controller connected to the DeviceNet Communications Unit.
Sets the allocation items for the IN1 Area. (See note 1.)
Sets the allocation items for the IN2 Area. (See note 1.)
Sets the allocation items for the OUT Area. (See note 1.)
Makes settings for Unit 0, channel 1
Makes settings for Unit 0, channel 2.
---
Makes settings for Unit 15, channel 4.
Makes settings for the DeviceNet Communications Unit.
Note 1.
pendix B Allocation Numbers for Configurators Manufactured by Other Companies on page 151. In
the first word of OUT Area 1 (OUT Data 1) must always be allocated to 31998 (i.e., the OUT Enable
Bit).
145
Connecting to a Master from Another Company
Appendix A
2.
The default assignments is the 111 (ch3 Control Output (Heating)) for control output 3 and 143 (ch4
Control Output (Heating)) for control output 4. Change these assignments as required when using a
TC2 Unit.
3.
When settings are read, data read for non-existing Temperature Controllers are not dependable. Do not change the Temperature Controller configuration when reading or writing settings.
Data Size and Connection Types
The DeviceNet Communications Unit supports both simple I/O allocation and I/O allocations set from the Configurator when the Unit is connected to another company’s master, but the data size of the IN and OUT Areas of the DeviceNet Communications Unit must be set. The size of the DeviceNet Communications Unit’s data
If the connection type can be set when another company’s configurator is being used, select a connection supported by the DeviceNet Communications Unit.
The following table shows the connection types and data sizes for OMRON DeviceNet Communications Units.
Model
DeviceNet
Communications Unit
EJ1N-HFUB-
DRT
Yes
Poll
Supported connections
Bit strobe Change of state (COS)
No Yes Yes
Cyclic
Data size (bytes)
IN OUT
1 to 200
(See note.)
1 to 200
(See note.)
Note The size of the IN/OUT Areas depends on the setting.
DeviceNet I/O communications support the following types of connections.
Connection type
Poll
Change of state
(COS)
Cyclic
Details
Used to exchange data between the master and individual slaves by sending and receiving commands and responses. (Output data is allocated for commands and input data is allocated for responses).
Normally, input and output data are sent by master 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.
Masters and slaves send output or input data at regular cycles.
---
Remarks
By setting a long cycle interval, the Network will not be loaded with communications for minor data changes, thereby improving the overall efficiency of the Network.
---
More Detailed DeviceNet Specifications
The following device profiles contain more detailed DeviceNet specifications for the DeviceNet Communications Unit if more information needs to be registered in the scan list.
Device Profiles
General data Compatible DeviceNet Specifications
Vendor name
Device profile name
Manufacturer catalog number
Manufacturer revision
Volume I, Release 1.3
Volume II, Release 1.3
OMRON Corporation
Slaves: Communications
Adapter
H155
1.01
Vendor ID = 47
Profile number = 12
146
Connecting to a Master from Another Company
Appendix A
Physical conformance data
Communications data
Network current consumption
Connector type
Physical layer insulation
Supported indicators
MAC ID setting
Default MAC ID
Baud rate setting
Supported baud rates
80 mA max.
Open plug
No
Module, Network
Rotary switch
0
None (automatic recognition)
125 kbps, 250 kbps, and 500 kbps
Predefined Master/Slave connection set
Dynamic connection support (UCMM)
Group 2 only server
No
Explicit message fragmentation support Yes
Object Mounting
Identity Object (01 hex)
Object class Attribute
Service
Not supported
Not supported
Object instance
Attribute ID
1
2
3
6
7
4
5
8
Service
05
0E
Contents
Vendor Yes
Device type
Product code
Yes
Yes
Revision Yes
Status (bits supported) Yes
Serial number
Product name
Yes
Yes
State
DeviceNet service
No
Reset No
Get_Attribute_Single No
Message Router Object (02 hex)
Object class
Object instance
Attribute
Service
Attribute
Service
Vendor specification addition
Not supported
Not supported
Not supported
Not supported
None
DeviceNet Object (03 hex)
Object class Attribute
Service
Not supported
Not supported
No
No
No
No
No
No
No
No
Value
47
12
315
1.1
Bit 00 only
Unique for each Unit
EJ1N-HFUB-DRT
Parameter option
147
Connecting to a Master from Another Company
Object instance
Attribute ID
1
2
3
6
7
4
5
8
9
Service
0E
4B
4C
Contents
MAC ID
Baud rate
BOI
Bus Off counter
Allocation information
MAC ID switch changed
Baud rate switch changed
MAC ID switch value
Baud rate switch value
Yes
No
DeviceNet service
Get_Attribute_Single None
Allocate_Master/
Slave_Connection_Set
Release_Master/
Slave_Connection_Set
None
None
Yes
Yes
Yes
Yes
Yes
Yes
No
Assembly Object (04 hex)
Object class Attribute
Service
Not supported
Not supported
Object instance
100: IN Area 1
101: IN Area 2
110: OUT Area 1
Attribute ID
1
2
3
Service
0E
10
Contents
Number of members in list No
Member list
Data
No
Yes
DeviceNet service
Get_Attribute_Single None
Set_Attribute_Single None
Connection Object (05 hex)
Object class Attribute
Service
Maximum number of active connections
Not supported
Not supported
1
Appendix A
Value
No
No
No
No
No
No
No
00 (hexadecimal)
No
No
Parameter option
No
No
Yes
Parameter option
Value
148
Connecting to a Master from Another Company
Appendix A
Object instance 1
Object instance 2
Section Information Maximum number of instances
Instance type
Explicit Message 1
Production trigger
Cyclic
Transport type Server
Transport class
3
Attribute ID
1
2
5
6
3
4
State tics
Contents
Instance type
Transport class trigger
Initial comm. characteris-
Yes
Yes
Yes
Produced connection ID Yes
Consumed connection ID Yes
Yes
No
No
No
No
No
No
Value
00 (hexadecimal)
83 (hexadecimal)
21 (hexadecimal)
Service
7
8
9
Produced connection size Yes
Consumed connection size
Yes
Expected packet rate
DeviceNet service
Yes
Reset None
No
No
Yes
0176 (hexadecimal)
Parameter option
05
0E
10
Get_Attribute_Single None
Set_Attribute_Single None
Section Information Maximum number of instances
Instance type
Polled I/O 1
Production trigger
Cyclic
Transport type Server
Transport class
2
Attribute ID
1
2
3
4
5
6
7
8
State
Contents
Instance type
Transport class trigger
Yes
Yes
Yes
Produced connection ID Yes
Consumed connection ID Yes
Initial comm. characteristics
Yes
Produced connection size Yes
No
No
No
No
No
No
No
No
Value
01 (hexadecimal)
82 (hexadecimal)
01 (hexadecimal)
Service
9
05
0E
10
Consumed connection size
Expected packet rate
DeviceNet service
Reset
Yes
Yes
None
Get_Attribute_Single None
Set_Attribute_Single None
Yes
Parameter option
1.
Produced Connection Path
IN Area 1: 20_04_24_64_30_03
IN Area 2: 20_04_24_65_30_03
2.
Consumed Connection Path
OUT Area: 20_04_24_6E_30_03
149
Connecting to a Master from Another Company
Appendix A
Object instance 4
Section
Instance type
COS Cyclic
Information
Production trigger
Cyclic
Transport type Server
Transport class
2
Attribute ID
1
2
3
State
Contents
Instance type
Transport class trigger
1
Yes
Yes
Yes
Service
4
7
8
5
6
9
05
0E
10
Produced connection ID Yes
Consumed connection ID Yes
Initial comm. characteristics Yes
Produced connection size Yes
Consumed connection size Yes
Expected packet rate
DeviceNet service
Yes
Reset None
Get_Attribute_Single None
Set_Attribute_Single None
Note Produced Connection Path
IN Area 1: 20_04_24_64_30_03
IN Area 2: 20_04_24_65_30_03
Maximum number of instances
No
No
No
Value
01 (hexadecimal)
12 (hexadecimal)
No
No
No
No
No
01 (hexadecimal)
Yes
Parameter option
150
Appendix B
Allocation Numbers for Configurators
Manufactured by Other Companies
Operation Command/Status Parameters
TC2
Allocated in IN
Area
Allocated in OUT Area Parameter name
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
No
Yes
No
No
Yes
Yes
Yes
Yes
No
No
No
No
Yes
Yes
Yes
No
No
No
No
No
No
No
No
No
No
No
No
Yes
Yes
Yes
No
Output Completed Flags
Read Parameter Monitor
(See note 2.)
OUT Enable Bit (See note 1.)
Read Parameter (See note 2.)
Write Parameter (See note 2.)
Communications Status
Communications Error Status
Unit Status
Alarm 1 (TC2: #00
−#07)
Alarm 1 (TC2: #08
−#15)
Alarm 2 (TC2: #00
−#07)
Alarm 2 (TC2: #08
−#15)
Alarm 3 (TC2: #00
−#07)
Alarm 3 (TC2: #08
−#15)
HB Alarm (TC2: #00
−#07)
HB Alarm (TC2: #08
−#15)
HS Alarm (TC2: #00
−#07)
HS Alarm (TC2: #08
−#15)
OC Alarm (TC2: #00
−#07)
OC Alarm (TC2: #08
−#15)
Input Error (TC2: #00
−#07)
Input Error (TC2: #08
−#15)
Run/Stop (TC2: #00
−#07)
Run/Stop (TC2: #08
−#15)
AT Execute/Cancel (TC2: #00
−#07)
AT Execute/Cancel (TC2: #08
−#15)
Auto/Manual (TC2: #00
−#07)
Auto/Manual (TC2: #08
−#15)
Software Reset
Note 1.
Always allocate the first word of the OUT Area to the OUT Enable Bit.
2.
These parameters are for expansion remote I/O.
Allocation number for configurator manufactured by other company
31486
31742
40190
40446
40958
41214
42750
43006
44542
44798
46334
46590
47870
35838
36094
37630
37886
39166
39422
39678
39934
31998
32510
32766
33022
33278
33534
34046
34302
151
Allocation Numbers for Configurators Manufactured by Other Companies
Appendix B
TC4
Allocated in IN
Area
Allocated in OUT
Area
Parameter name
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
No
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
Yes
Yes
No
No
No
No
No
No
No
No
Yes
Yes
Yes
Yes
Yes
Yes
No
No
No
No
No
No
No
No
Yes
Yes
Yes
No
No
Yes
Yes
No
No
Output Completed Flags
Read Parameter Monitor
(See note 2.)
OUT Enable Bit (See note 1.)
Read Parameter (See note 2.)
Write Parameter (See note 2.)
Communications Status
Communications Error Status
Unit Status
Alarm 1 (TC4: #00
−#03)
Alarm 1 (TC4: #04
−#07)
Alarm 1 (TC4: #08
−#11)
Alarm 1 (TC4: #12
−#15)
Alarm 2 (TC4: #00
−#03)
Alarm 2 (TC4: #04
−#07)
Alarm 2 (TC4: #08
−#11)
Alarm 2 (TC4: #12
−#15)
Alarm 3 (TC4: #00
−#03)
Alarm 3 (TC4: #04
−#07)
Alarm 3 (TC4: #08
−#11)
Alarm 3 (TC4: #12
−#15)
Input Error (TC4: #00
−#03)
Input Error (TC4: #04
−#07)
Input Error (TC4: #08
−#11)
Input Error (TC4: #12
−#15)
Run/Stop (TC4: #00
−#03)
Run/Stop (TC4: #04
−#07)
Run/Stop (TC4: #08
−#11)
Run/Stop (TC4: #12- #15)
AT Execute/Cancel (TC4: #00
−#03)
AT Execute/Cancel (TC4: #04
−#17)
AT Execute/Cancel (TC4: #08
−#11)
AT Execute/Cancel (TC4: #12
−#15)
Auto/Manual (TC4: #00
−#03)
Auto/Manual (TC4: #04
−#07)
Auto/Manual (TC4: #08
−#11)
Auto/Manual (TC4: #12
−#15)
Software Reset
Note 1.
Always allocate the first word of the OUT Area to the OUT Enable Bit.
2.
These parameters are for expansion remote I/O.
Allocation number for configurator manufactured by other company
31486
31742
42238
43262
43518
43774
44030
45054
45310
45566
37118
38142
38398
38654
38910
41470
41726
41982
31998
32510
32766
33022
33278
33534
34558
34814
35070
35326
36350
36606
36862
45822
46846
47102
47358
47614
47870
152
Allocation Numbers for Configurators Manufactured by Other Companies
Appendix B
Parameters for Expansion Remote I/O (for TC4 and TC2)
Parameter name
Parameter specification ch1 ch2
Unit 0 ch3 ch4 ch1 ch2
Unit 1 ch3 ch4 ch1 ch2
Unit 2 ch3 ch4 ch1 ch2
Unit 3 ch3 ch4
47872 47873 47874 47875 47888 47889 47890 47891 47904 47905 47906 47907 47920 47921 47922 47923
Unit 4 Unit 5 Unit 6 Unit 7 ch1 ch2 ch3 ch4 ch1 ch2 ch3 ch4 ch1 ch2 ch3 ch4 ch1 ch2 ch3 ch4
47936 47937 47938 47939 47952 47953 47954 47955 47968 47969 47970 47971 47984 47985 47986 47987 ch1 ch2
Unit 8 ch3 ch4 ch1 ch2
Unit 9 ch3 ch4 ch1
Unit 10 ch2 ch3 ch4 ch1
Unit 11 ch2 ch3 ch4
48000 48001 48002 48003 48016 48017 48018 48019 48032 48033 48034 48035 48048 48049 48050 48051
Unit 12 Unit 13 Unit 14 Unit 15 ch1 ch2 ch3 ch4 ch1 ch2 ch3 ch4 ch1 ch2 ch3 ch4 ch1 ch2 ch3 ch4
48064 48065 48066 48067 48080 48081 48082 48083 48096 48097 48098 48099 48112 48113 48114 48115
Monitor Parameters (for TC4 and TC2)
Units 0 to 3
Parameter name
Device A Status
Configuration Error A
Status ch1 ch2
Unit 0 ch3
256
768 ch4 ch1 ch2
Unit 1
272
784 ch3 ch4 ch1 ch2
Unit 2
288
800 ch3 ch4 ch1 ch2
Unit 3
304
816 ch3 ch4
Configuration Error B
Status
Internal Communications Error Status
I/O Error Status
I/O Alarm A Status
(See note 3.)
I/O Alarm B Status
(See note 3.)
I/O Notification A Status (See note 3.)
Error Channel A Status
Basic Unit/Expand
Unit Error
1024
1280
1536
1792
2048
2304
2560
2816
1040
1296
1552
1808
2064
2320
2576
2832
1056
1312
1568
1824
2080
2336
2592
2848
1072
1328
1584
1840
2096
2352
2608
2864
Basic Unit/Expand
Unit Alarm
Output Monitor
3072 3088 3104 3120
Device B Status
Process Value
Channel Status
Channel Alarm Status
Internal SP
Local SP Monitor
3840
4096
4352
3841
4097
4353
3328
3584
3842
4098
4354
3843
4099
4355
3856
4112
4368
3857
4113
4369
3344
3600
3858
4114
4370
3859
4115
4371
3872
4128
4384
3573
4129
4385
3360
3616
3874
4130
4386
3875
4131
4387
3888
4144
4400
3889
4145
4401
3376
3632
3890
4146
4402
3891
4147
4403
4608 4609 4610 4611 4624 4625 4626 4627 4640 4641 4642 4643 4656 4657 4658 4659
4864 4865 4866 4867 4880 4881 4882 4883 4896 4897 4898 4899 4912 4913 4914 4915
Remote SP Monitor
Bank No. Monitor
5120 5121 5122 5123 5136 5137 5138 5139 5152 5153 5154 5155 5168 5169 5170 5171
5376 5377 5378 5379 5392 5393 5394 5395 5408 5409 5410 5411 5424 5425 5426 5427
MV Monitor (Heating) 5632 5633 5634 5635 5648 5649 5650 5651 5664 5665 5666 5667 5680 5681 5682 5683
MV Monitor (Cooling) 5888 5889 5890 5891 5904 5905 5906 5907 5920 5921 5922 5923 5936 5937 5938 5939
6144 6145 6146 6147 6160 6161 6162 6163 6176 6177 6178 6179 6192 6193 6194 6195 Decimal Point Monitor
Heater Current Value
Monitor (See note 3.)
Leakage Current
Value Monitor (See note 3.)
6400
6656
6401
6657
6402
6658
6403
6659
6416
6672
6417
6673
6418
6674
6419
6675
6432
6688
6433
6689
6434
6690
6435
6691
6448
6704
6449
6705
6450
6706
6451
6707
153
Allocation Numbers for Configurators Manufactured by Other Companies
Appendix B
Parameter name
G3ZA1 CH1 Control
Variable Monitor
G3PW Output Variable Monitor
(See note 4.)
G3ZA1 CH2 Control
Variable Monitor (See note 4.)
G3ZA1 CH3 Control
Variable Monitor (See note 4.)
G3ZA1 CH4 Control
Variable Monitor (See note 4.)
G3ZA1 CH5 Control
Variable Monitor (See note 4.)
G3ZA1 CH6 Control
Variable Monitor (See note 4.)
G3ZA1 CH7 Control
Variable Monitor (See note 4.)
G3ZA1 CH8 Control
Variable Monitor (See note 4.)
G3ZA1 CH1 Status
G3PW Status
(See note 4.)
G3ZA1 CH2 Status
(See note 4.)
G3ZA1 CH3 Status
(See note 4.)
G3ZA1 CH4 Status
(See note 4.)
G3ZA1 CH5 Status
(See note 4.)
G3ZA1 CH6 Status
(See note 4.)
G3ZA1 CH7 Status
(See note 4.)
G3ZA1 CH8 Status
(See note 4.)
G3ZA1 CH1 Heater
ON Current Monitor
G3PW Current Monitor (See note 4.)
G3ZA1 CH2 Heater
ON Current Monitor
(See note 4.)
G3ZA1 CH3 Heater
ON Current Monitor
(See note 4.)
G3ZA1 CH4 Heater
ON Current Monitor
(See note 4.)
G3ZA1 CH1 Heater
OFF Current Monitor
(See note 4.)
G3ZA1 CH2 Heater
OFF Current Monitor
(See note 4.)
G3ZA1 CH3 Heater
OFF Current Monitor
(See note 4.)
G3ZA1 CH4 Heater
OFF Current Monitor
(See note 4.)
Unit 0 Unit 1 Unit 2 Unit 3 ch1 ch2 ch3 ch4 ch1 ch2 ch3 ch4 ch1 ch2 ch3 ch4 ch1 ch2 ch3 ch4
17152 17153 17154 17155 17168 17169 17170 17171 17184 17185 17186 17187 17200 17201 17202 17203
17408 17409 17410 17411 17424 17425 17426 17427 17440 17441 17442 17443 17456 17457 17458 17459
17664 17665 17666 17667 17680 17681 17682 17683 17696 17697 17698 17699 17712 17713 17714 17715
17920 17921 17922 17923 17936 17937 17938 17939 17952 17953 17954 17955 17968 17969 17970 17971
18176 18177 18178 18179 18192 18193 18194 18195 18208 18209 18210 18211 18224 18225 18226 18227
18432 18433 18434 18435 18448 18449 18450 18451 18464 18465 18466 18467 18480 18481 18482 18483
18688 18689 18690 18691 18704 18705 18706 18707 18720 18721 18722 18723 18736 18737 18738 18739
18944 18945 18946 18947 18960 18961 18962 18963 18976 18977 18978 18979 18992 18993 18994 18994
19200 19201 19202 19203 19216 19217 19218 19219 19232 19233 19234 19235 19248 19249 19250 19251
19456 19457 19458 19459 19472 19473 19474 19475 19488 19489 19490 19491 19504 19505 19506 19507
19712 19713 19714 19715 19728 19729 19730 19731 19744 19745 19746 19747 19760 19761 19762 19763
19968 19969 19970 19971 19984 19985 19986 19987 20000 20001 20002 20003 20016 20017 20018 20019
20224 20225 20226 20227 20240 20241 20242 20243 20256 20257 20258 20259 20272 20273 20274 20275
20480 20481 20482 20483 20496 20497 20498 20499 20512 20513 20514 20515 20528 20529 20530 20531
20736 20737 20738 20739 20752 20753 20754 20755 20768 20769 20770 20771 20784 20785 20786 20787
20992 20993 20994 20995 21008 21009 21010 21011 21024 21025 21026 21027 21040 21041 21042 21043
21248 21249 21250 21251 21264 21265 21266 21267 21280 21281 21282 21283 21296 21297 21298 21299
21504 21505 21506 21507 21520 21521 21522 21523 21536 21537 21538 21539 21552 21553 21554 21555
21760 21761 21762 21763 21776 21777 21778 21779 21792 21793 21794 21795 21808 21809 21810 21811
22016 22017 22018 22019 22032 22033 22034 22035 22048 22049 22050 22051 22064 22065 22066 22067
22272 22273 22274 22275 22288 22289 22290 22291 22304 22305 22306 22307 22320 22321 22322 22323
22528 22529 22530 22531 22544 22545 22546 22547 22560 22561 22562 22563 22576 22577 22578 22579
22784 22785 22786 22787 22800 22801 22802 22803 22816 22817 22818 22819 22832 22833 22834 22835
23040 23041 23042 23043 23056 23057 23058 23059 23072 23073 23074 23075 23088 23089 23090 23091
Note 1.
Only the IN Area can be allocated to monitor parameters.
2.
TC2 Units cannot use allocations for channel 3 or channel 4.
3.
Can be used with TC2 Units, but not TC4 Units.
154
Allocation Numbers for Configurators Manufactured by Other Companies
Appendix B
4.
Monitoring can be performed for up to four G3ZA or G3PW Power Controllers for each Temperature
Controller. Each channel of Temperature Controller corresponds to one G3ZA or G3PW Power Controller. (Example: ch1
→ G3ZA1)
155
Allocation Numbers for Configurators Manufactured by Other Companies
Appendix B
Units 4 to 7
Parameter name
Device A Status
Configuration Error A
Status
Configuration Error B
Status
Internal Communications Error Status
I/O Error Status
I/O Alarm A Status
(See note 3.) ch1 ch2
Unit 4 ch3
320
832
1088
1344
1600
1856 ch4 ch1 ch2
Unit 5
336
848
1104
1360
1616
1872 ch3 ch4 ch1 ch2
Unit 6
352
864
1120
1376
1632
1888 ch3 ch4 ch1 ch2
Unit 7
368
880
1136
1392
1648
1904 ch3 ch4
I/O Alarm B Status
(See note 3.)
I/O Notification A Status (See note 3.)
Error Channel A Status
Basic Unit/Expand
Unit Error
Basic Unit/Expand
Unit Alarm
2112
2368
2624
2880
3136
2128
2384
2640
2896
3152
2144
2400
2656
2912
3168
2160
2416
2672
2928
3184
Output Monitor
Device B Status
Process Value
Channel Status
Channel Alarm Status
Internal SP
Local SP Monitor
3904
4160
4416
3905
4161
4417
3392
3468
3906
4162
4418
3907
4163
4419
3920
4176
4432
3921
4177
4433
3408
3664
3922
4178
4434
3923
4179
4435
3936
4192
4448
3937
4193
4449
3424
3680
3938
4194
4450
3939
4195
4451
3952
4208
4464
3953
4209
4465
3440
3696
3954
4210
4466
3955
4211
4467
4672 4673 4674 4675 4688 4689 4690 4691 4704 4705 4706 4707 4720 4721 4722 4723
4928 4929 4930 4931 4944 4945 4946 4947 4960 4961 4962 4963 4976 4977 4978 4979
Remote SP Monitor
Bank No. Monitor
5184
5440
5185
5441
5186
5442
5187
5443
5200
5456
5201
5457
5202
5458
5203
5459
5216
5472
5217
5473
5218
5474
5219
5475
5232
5488
5233
5489
5234
5490
5235
5491
MV Monitor (Heating) 5696 5697 5698 5699 5712 5713 5714 5715 5728 5729 5730 5731 5744 5745 5746 5747
MV Monitor (Cooling) 5952 5953 5954 5955 5968 5969 5970 5971 5984 5985 5986 5987 6000 6001 6002 6003
Decimal Point Monitor
6208 6209 6210 6211 6224 6225 6226 6227 6240 6241 6242 6243 6256 6257 6258 6259
6464 6465 6466 6467 6480 6481 6482 6483 6496 6497 6498 6499 6512 6513 6514 6515 Heater Current Value
Monitor (See note 3.)
Leakage Current
Value Monitor (See note 3.)
G3ZA1 CH1 Control
Variable Monitor
G3PW Output Variable Monitor
(See note 4.)
G3ZA1 CH2 Control
Variable Monitor (See note 4.)
G3ZA1 CH3 Control
Variable Monitor (See note 4.)
G3ZA1 CH4 Control
Variable Monitor (See note 4.)
6720
17216
17472
17728
17984
6721
17217
17473
17729
17985
6722
17218
17474
17730
17986
6723
17219
17475
17731
17987
6736
17232
17488
17744
18000
6737
17233
17489
17745
18001
6738
17234
17490
17746
18002
6739
17235
17491
17747
18003
6752
17248
17504
17760
18016
6753
17249
17505
17761
18017
6754
17250
17506
17762
18018
6755
17251
17507
17763
18019
6768
17264
17520
17776
18032
6769
17265
17521
17777
18033
6770
17266
17522
17778
18034
6771
17267
17523
17779
18035
G3ZA1 CH5 Control
Variable Monitor (See note 4.)
G3ZA1 CH6 Control
Variable Monitor (See note 4.)
G3ZA1 CH7 Control
Variable Monitor (See note 4.)
G3ZA1 CH8 Control
Variable Monitor (See note 4.)
18240 18241 18242 18243 18526 18527 18528 18529 18272 18273 18274 18275 18288 18289 18290 18291
18496
18752
19008
18497
18753
19009
18498
18754
19010
18499
18755
19011
18512
18768
19204
18513
18769
19205
18514
18770
19206
18515
18771
19207
18528
18784
19040
18529
18785
19041
18530
18786
19042
18531
18787
19043
18544
18800
19056
18545
18801
19057
18546
18802
19058
18547
18803
19059
156
Allocation Numbers for Configurators Manufactured by Other Companies
Appendix B
Parameter name
G3ZA1 CH1 Status
G3PW Monitor
(See note 4.)
G3ZA1 CH2 Status
(See note 4.)
G3ZA1 CH3 Status
(See note 4.)
G3ZA1 CH4 Status
(See note 4.)
G3ZA1 CH5 Status
(See note 4.)
G3ZA1 CH6 Status
(See note 4.)
G3ZA1 CH7 Status
(See note 4.)
G3ZA1 CH8 Status
(See note 4.)
G3ZA1 CH1 Heater
ON Current Monitor
G3PW Current Monitor (See note 4.)
G3ZA1 CH2 Heater
ON Current Monitor
(See note 4.)
G3ZA1 CH3 Heater
ON Current Monitor
(See note 4.)
G3ZA1 CH4 Heater
ON Current Monitor
(See note 4.)
G3ZA1 CH1 Heater
OFF Current Monitor
(See note 4.)
G3ZA1 CH2 Heater
OFF Current Monitor
(See note 4.)
G3ZA1 CH3 Heater
OFF Current Monitor
(See note 4.)
G3ZA1 CH4 Heater
OFF Current Monitor
(See note 4.)
Unit 4 Unit 5 Unit 6 Unit 7 ch1 ch2 ch3 ch4 ch1 ch2 ch3 ch4 ch1 ch2 ch3 ch4 ch1 ch2 ch3 ch4
19264 19265 19266 19267 19280 19281 19282 19283 19296 19297 19298 19299 19312 19313 19314 19315
19520 19521 19522 19523 19536 19537 19538 19539 19552 19553 19554 19555 19568 19569 19570 19571
19776 19777 19778 19779 19792 19793 19794 19795 19808 19809 19810 19811 19824 19825 19826 19827
20032 20033 20034 20035 20048 20049 20050 20051 20064 20065 20066 20067 20080 20081 20082 20083
20288 20289 20290 20291 20304 20305 20306 20307 20320 20321 20322 20323 20336 20337 20338 20339
20544 20545 20546 20547 20560 20561 20562 20563 20576 20577 20578 20579 20592 20593 20594 20595
20800 20801 20802 20803 20816 20817 20818 20819 20832 20833 20834 20835 20848 20849 20850 20851
21056 21057 21058 21059 21072 21073 21074 21075 21088 21089 21090 21091 21104 21105 21106 21107
21312 21313 21314 21315 21328 21329 21330 21331 21344 21345 21346 21347 21360 21361 21362 21363
21568 21569 21570 21571 21584 21585 21586 21587 21600 21601 21602 21603 21616 21617 21618 21619
21824 21825 21826 21827 21840 21841 21842 21843 21856 21857 21858 21859 21872 21873 21874 21875
22080 22081 22082 22083 22096 22097 22098 22099 22112 22113 22114 22115 22128 22129 22130 22131
22336 22337 22338 22339 22352 22353 22354 22355 22368 22369 22370 22371 22384 22385 22386 22387
22592 22593 22594 22595 22608 22609 22610 22611 22624 22625 22626 22627 22640 22641 22642 22643
22848 22849 22850 22851 22864 22865 22866 22867 22880 22881 22882 22883 22896 22897 22898 22899
23104 23105 23106 23107 23120 23121 23122 23123 23136 23137 23138 23139 23152 23153 23154 23155
Note 1.
Only the IN Area can be allocated to monitor parameters.
2.
TC2 Units cannot use allocations for channel 3 or channel 4.
3.
Can be used with TC2 Units, but not TC4 Units.
4.
Monitoring can be performed for up to four G3ZA or G3PW Power Controllers for each Temperature
Controller. Each channel of Temperature Controller corresponds to one G3ZA or G3PW Power Controller. (Example: ch1
→ G3ZA1)
157
Allocation Numbers for Configurators Manufactured by Other Companies
Appendix B
Units 8 to 11
Parameter name
Device A Status
Configuration Error A
Status
Configuration Error B
Status
Internal Communications Error Status
I/O Error Status
I/O Alarm A Status
(See note 3.) ch1 ch2
Unit 8 ch3
384
896
1152
1408
1664
1920 ch4 ch1 ch2
Unit 9
400
912
1168
1424
1680
1936 ch3 ch4 ch1
Unit 10 ch2
416
928
1184
1440
1696
1952 ch3 ch4 ch1
Unit 11 ch2
432
944
1200
1456
1712
1968 ch3 ch4
I/O Alarm B Status
(See note 3.)
I/O Notification A Status (See note 3.)
Error Channel A Status
Basic Unit/Expand
Unit Error
Basic Unit/Expand
Unit Alarm
2176
2432
2688
2944
3200
2192
2448
2704
2960
3216
2208
2464
2720
2976
3232
2224
2480
2736
2992
3248
Output Monitor
Device B Status
Process Value
Channel Status
Channel Alarm Status
Internal SP
Local SP Monitor
3968
4224
4480
3969
4225
4481
3456
3712
3970
4226
4482
3971
4227
4483
3984
4240
4496
3985
4241
4497
3472
3728
3986
4242
4498
3987
4243
4499
4000
4256
4512
4001
4257
4513
3488
3744
4002
4258
4514
4003
4259
4515
4016
4272
4528
4017
4273
4529
3504
3760
4018
4274
4530
4019
4275
4531
4736 4737 4738 4739 4752 4753 4754 4755 4768 4769 4770 4771 4784 4785 4786 4787
4992 4993 4994 4995 5008 5009 5010 5011 5024 5025 5026 5027 5040 5041 5042 5043
Remote SP Monitor
Bank No. Monitor
5248
5504
5249
5505
5250
5506
5251
5507
5264
5520
5265
5521
5266
5522
5267
5523
5280
5536
5281
5537
5282
5538
5283
5539
5296
5552
5297
5553
5298
5554
5299
5555
MV Monitor (Heating) 5760 5761 5762 5763 5776 5777 5778 5779 5792 5793 5794 5795 5808 5809 5810 5811
MV Monitor (Cooling) 6016 6017 6018 6019 6032 6033 6034 6035 6048 6049 6050 6051 6064 6065 6066 6067
Decimal Point Monitor
6272 6273 6274 6275 6288 6289 6290 6291 6304 6305 6306 6307 6320 6321 6322 6323
6528 6529 6530 6531 6544 6545 6546 6547 6560 6561 6562 6563 6576 6577 6578 6579 Heater Current Value
Monitor (See note 3.)
Leakage Current
Value Monitor (See note 3.)
G3ZA1 CH1 Control
Variable Monitor
G3PW Output Variable Monitor
(See note 4.)
G3ZA1 CH2 Control
Variable Monitor (See note 4.)
G3ZA1 CH3 Control
Variable Monitor (See note 4.)
G3ZA1 CH4 Control
Variable Monitor (See note 4.)
6784
17280
17536
17792
18048
6785
17281
17537
17793
18049
6786
17282
17538
17794
18050
6787
17283
17539
17795
18051
6800
17296
17552
17808
18064
6801
17297
17553
17809
18065
6802
17298
17554
17810
18066
6803
17299
17555
17811
18067
6816
17312
17568
17824
18080
6817
17313
17569
17825
18081
6818
17314
17570
17826
18082
6819
17315
17571
17827
18083
6832
17328
17584
17840
18096
6833
17329
17585
17841
18097
6834
17330
17586
17842
18098
6835
17331
17587
17843
18099
G3ZA1 CH5 Control
Variable Monitor (See note 4.)
G3ZA1 CH6 Control
Variable Monitor (See note 4.)
G3ZA1 CH7 Control
Variable Monitor (See note 4.)
G3ZA1 CH8 Control
Variable Monitor (See note 4.)
18304 18305 18306 18307 18320 18321 18322 18323 18336 18337 18338 18339 18352 18353 18354 18355
18560
18816
19072
18561
18817
19073
18562
18818
19074
18563
18819
19075
18576
18832
19088
18577
18833
19089
18578
18834
19090
18579
18835
19091
18592
18848
19104
18593
18849
19105
18594
18850
19106
18595
18851
19107
18608
18864
19120
18609
18865
19121
18610
18866
19122
18611
18867
19123
158
Allocation Numbers for Configurators Manufactured by Other Companies
Appendix B
Parameter name
G3ZA1 CH1 Status
G3PW Status
(See note 4.)
G3ZA1 CH2 Status
(See note 4.)
G3ZA1 CH3 Status
(See note 4.)
G3ZA1 CH4 Status
(See note 4.)
G3ZA1 CH5 Status
(See note 4.)
G3ZA1 CH6 Status
(See note 4.)
G3ZA1 CH7 Status
(See note 4.)
G3ZA1 CH8 Status
(See note 4.)
G3ZA1 CH1 Heater
ON Current Monitor
G3PW Current Monitor (See note 4.)
G3ZA1 CH2 Heater
ON Current Monitor
(See note 4.)
G3ZA1 CH3 Heater
ON Current Monitor
(See note 4.)
G3ZA1 CH4 Heater
ON Current Monitor
(See note 4.)
G3ZA1 CH1 Heater
OFF Current Monitor
(See note 4.)
G3ZA1 CH2 Heater
OFF Current Monitor
(See note 4.)
G3ZA1 CH3 Heater
OFF Current Monitor
(See note 4.)
G3ZA1 CH4 Heater
OFF Current Monitor
(See note 4.)
Unit 8 Unit 9 Unit 10 Unit 11 ch1 ch2 ch3 ch4 ch1 ch2 ch3 ch4 ch1 ch2 ch3 ch4 ch1 ch2 ch3 ch4
19328 19329 19330 19331 19344 19345 19346 19347 19360 19361 19362 19363 19376 19377 19378 19379
19584 19585 19586 19587 19600 19601 19602 19603 19616 19617 19618 19619 19632 19633 19634 19635
19840 19841 19842 19843 19856 19857 19858 19859 19872 19873 19874 19875 19888 19889 19890 19891
20096 20097 20098 20099 20112 20113 20114 20115 20128 20129 20130 20131 20144 20145 20146 20147
20352 20353 20354 20355 20368 20369 20370 20371 20384 20385 20386 20387 20400 20401 20402 20403
20608 20609 20610 20611 20624 20625 20626 20627 20640 20641 20642 20643 20656 20657 20658 20659
20864 20865 20866 20867 20880 20881 20882 20883 20896 20897 20898 20899 20912 20913 20914 20915
21120 21121 21122 21123 21136 21137 21138 21139 21152 21153 21154 21155 21168 21169 21170 21171
21376 21377 21378 21379 21392 21393 21394 21395 21408 21409 21410 21411 21424 21425 21426 21427
21632 21633 21634 21635 21648 21649 21650 21651 21664 21665 21666 21667 21680 21681 21682 21683
21888 21889 21890 21891 21904 21905 21906 21907 21920 21921 21922 21923 21936 21937 21938 21939
22144 22145 22146 22147 22160 22161 22162 22163 22176 22177 22178 22179 22192 22193 22194 22195
22400 22401 22402 22403 22416 22417 22418 22419 22432 22433 22434 22435 22448 22449 22450 22451
22656 22657 22658 22659 22672 22673 22674 22675 22688 22689 22690 22691 22704 22705 22706 22707
22912 22913 22914 22915 22928 22929 22930 22931 22944 22945 22946 22947 22960 22961 22962 22963
23168 23169 23170 23171 23184 23185 23186 23187 23200 23201 23202 23203 23216 23217 23218 23219
Note 1.
Only the IN Area can be allocated to monitor parameters.
2.
TC2 Units cannot use allocations for channel 3 or channel 4.
3.
Can be used with TC2 Units, but not TC4 Units.
4.
Monitoring can be performed for up to four G3ZA or G3PW Power Controllers for each Temperature
Controller. Each channel of Temperature Controller corresponds to one G3ZA or G3PW Power Controller. (Example: ch1
→ G3ZA1)
159
Allocation Numbers for Configurators Manufactured by Other Companies
Appendix B
Units 12 to 15
Parameter name
Device A Status
Configuration Error A
Status
Configuration Error B
Status
Internal Communications Error Status
I/O Error Status
I/O Alarm A Status
(See note 3.) ch1
Unit 12 ch2 ch3
448
960
1216
1472
1728
1984 ch4 ch1
Unit 13 ch2
464
976
1232
1488
1744
2000 ch3 ch4 ch1
Unit 14 ch2
480
992
1248
1504
1760
2016 ch3 ch4 ch1
Unit 15 ch2
496
1008
1264
1520
1776
2032 ch3 ch4
I/O Alarm B Status
(See note 3.)
I/O Notification A Status (See note 3.)
Error Channel A Status
Basic Unit/Expand
Unit Error
Basic Unit/Expand
Unit Alarm
2240
2496
2752
3008
3264
2256
2512
2768
3024
3280
2272
2528
2784
3040
3296
2288
2544
2800
3056
3312
Output Monitor
Device B Status
Process Value
Channel Status
Channel Alarm Status
Internal SP
Local SP Monitor
4032
4288
4544
4033
4289
4545
3520
3776
4034
4290
4546
4035
4291
4547
4048
4304
4560
4049
4305
4561
3356
3792
4050
4306
4562
4051
4307
4563
4064
4320
4576
4065
4321
4577
3552
3808
4066
4322
4578
4067
4323
4579
4080
4336
4592
4081
4337
4593
3568
3824
4082
4338
4594
4083
4339
4595
4800 4801 4802 4803 4816 4817 4818 4819 4832 4833 4834 4835 4848 4849 4850 4851
5056 5057 5058 5059 5072 5073 5074 5075 5088 5089 5090 5091 5104 5105 5106 5107
Remote SP Monitor
Bank No. Monitor
5312
5568
5313
5569
5314
5570
5315
5571
5328
5584
5329
5585
5330
5586
5331
5587
5344
5600
5345
5601
5346
5602
5347
5603
5360
5616
5361
5617
5362
5618
5363
5619
MV Monitor (Heating) 5824 5825 5826 5827 5840 5841 5842 5843 5856 5857 5858 5859 5872 5873 5874 5875
MV Monitor (Cooling) 6080 6081 6082 6083 6096 6097 6098 6099 6112 6113 6114 6115 6128 6129 6130 6131
Decimal Point Monitor
6336 6337 6338 6339 6352 6353 6354 6355 6368 6369 6370 6371 6384 6385 6386 6387
6592 6593 6594 6595 6608 6609 6610 6611 6624 6625 6626 6627 6640 6641 6642 6643 Heater Current Value
Monitor (See note 3.)
Leakage Current
Value Monitor (See note 3.)
G3ZA1 CH1 Control
Variable Monitor
G3PW Output Variable Monitor
(See note 4.)
6848
17344
6849
17345
6850
17346
6851
17347
6864
17360
6865
17361
6866
17362
6867
17363
6880
17376
6881
17377
6882
17378
6883
17379
6896
17392
6897
17393
6898
17394
6899
17395
17600 17601 17602 17603 17616 17617 17618 17619 17632 17633 17634 17635 17648 17649 17650 17651 G3ZA1 CH2 Control
Variable Monitor (See note 4.)
G3ZA1 CH3 Control
Variable Monitor (See note 4.)
G3ZA1 CH4 Control
Variable Monitor (See note 4.)
G3ZA1 CH5 Control
Variable Monitor (See note 4.)
G3ZA1 CH6 Control
Variable Monitor (See note 4.)
G3ZA1 CH7 Control
Variable Monitor (See note 4.)
G3ZA1 CH8 Control
Variable Monitor (See note 4.)
17856
18112
18368
18624
18880
19136
17857
18113
18369
18625
18881
19137
17858
18114
18370
18626
18882
19138
17859
18115
18371
18627
18883
19139
17872
18128
18384
18640
18896
19152
17873
18129
18385
18641
18897
19153
17874
18130
18386
18642
18898
19154
17875
18131
18387
18643
18899
19155
17888
18144
18400
18656
18912
19168
17889
18145
18401
18657
18913
19169
17890
18146
18402
18658
18914
19170
17891
18147
18403
18659
18915
19171
17904
18160
18416
18672
18928
19184
17905
18161
18417
18673
18929
19185
17906
18162
18418
18674
18930
19186
17907
18163
18419
18675
18931
19187
160
Allocation Numbers for Configurators Manufactured by Other Companies
Appendix B
Parameter name
G3ZA1 CH1 Status
G3PW Status
(See note 4.)
G3ZA1 CH2 Status
(See note 4.)
G3ZA1 CH3 Status
(See note 4.)
G3ZA1 CH4 Status
(See note 4.)
G3ZA1 CH5 Status
(See note 4.)
G3ZA1 CH6 Status
(See note 4.)
G3ZA1 CH7 Status
(See note 4.)
G3ZA1 CH8 Status
(See note 4.)
G3ZA1 CH1 Heater
ON Current Monitor
G3PW Current Monitor (See note 4.)
G3ZA1 CH2 Heater
ON Current Monitor
(See note 4.)
G3ZA1 CH3 Heater
ON Current Monitor
(See note 4.)
G3ZA1 CH4 Heater
ON Current Monitor
(See note 4.)
G3ZA1 CH1 Heater
OFF Current Monitor
(See note 4.)
G3ZA1 CH2 Heater
OFF Current Monitor
(See note 4.)
G3ZA1 CH3 Heater
OFF Current Monitor
(See note 4.)
G3ZA1 CH4 Heater
OFF Current Monitor
(See note 4.)
Unit 12 Unit 13 Unit 14 Unit 15 ch1 ch2 ch3 ch4 ch1 ch2 ch3 ch4 ch1 ch2 ch3 ch4 ch1 ch2 ch3 ch4
19392 19393 19394 19395 19408 19409 19410 19411 19424 19425 19426 19427 19440 19441 19442 19443
19648 19649 19650 19651 19664 19665 19666 19667 19680 19681 19682 19683 19696 19697 19698 19699
19904 19905 19906 19907 19920 19921 19922 19923 19936 19937 19938 19939 19952 19953 19954 19955
20160 20161 20162 20163 20176 20177 20178 20179 20192 20193 20194 20195 20208 20209 20210 20211
20416 20417 20418 20419 20432 20433 20434 20435 20448 20449 20450 20451 20464 20465 20466 20467
20672 20673 20674 20675 20688 20689 20690 20691 20704 20705 20706 20707 20720 20721 20722 20723
20928 20929 20930 20931 20944 20945 20946 20947 20960 20961 20962 20963 20976 20977 20978 20979
21184 21185 21186 21187 21200 21201 21202 21203 21216 21217 21218 21219 21232 21233 21234 21235
21440 21441 21442 21443 21456 21457 21458 21459 21472 21473 21474 21475 21488 21489 21490 21491
21696 21697 21698 21699 21712 21713 21714 21715 21728 21729 21730 21731 21744 21745 21746 21747
21952 21953 21954 21955 21968 21969 21970 21971 21984 21985 21986 21987 22000 22001 22002 22003
22208 22209 22210 22211 22224 22225 22226 22227 22240 22241 22242 22243 22256 22257 22258 22259
22464 22465 22466 22467 22480 22481 22482 22483 22496 22497 22498 22499 22512 22513 22514 22515
22720 22721 22722 22723 22736 22737 22738 22739 22752 22753 22754 22755 22768 22769 22770 22771
22976 22977 22978 22979 22992 22993 22994 22995 23008 23009 23010 23011 23024 23025 23026 23027
23232 23233 23234 23235 23248 23249 23250 23251 23264 23265 23266 23267 23280 23281 23282 23283
Note 1.
Only the IN Area can be allocated to monitor parameters.
2.
TC2 Units cannot use allocations for channel 3 or channel 4.
3.
Can be used with TC2 Units, but not TC4 Units.
4.
Monitoring can be performed for up to four G3ZA or G3PW Power Controllers for each Temperature
Controller. Each channel of Temperature Controller corresponds to one G3ZA or G3PW Power Controller. (Example: ch1
→ G3ZA1)
161
Allocation Numbers for Configurators Manufactured by Other Companies
Appendix B
Parameters That Can Be Changed during Operation
(TC4 and TC2)
Units 0 to 3
Parameter name ch1 ch2
Unit 0 ch3 ch4 ch1 ch2
Unit 1 ch3 ch4 ch1 ch2
Unit 2 ch3 ch4 ch1 ch2
Unit 3 ch3 ch4
6912 6913 6914 6915 6928 6929 6930 6931 6944 6945 6946 6947 6960 6961 6962 6963 Present Bank Set
Point
Present Bank Proportional Band
Present Bank Integral
Time
Present Bank Derivative Time
Present Bank SP
Ramp Rise Value
Present Bank SP
Ramp Fall Value
Present Bank Manual
Reset Value
Present Bank Cooling Coefficient
Present Bank Dead
Band
Present Bank Alarm
Value 1
Present Bank Alarm
Upper Limit Value 1
Present Bank Alarm
Lower Limit Value 1
Present Bank Alarm
Value 2
Present Bank Alarm
Upper Limit Value 2
7168
7424
7680
7936
8192
8448
8704
8960
9216
9472
9728
9984
10240
7169
7425
7681
7937
8193
8449
8705
8961
9217
9473
9729
9985
10241
7170
7426
7682
7938
8194
8450
8706
8962
9218
9474
9730
9986
10242
7171
7427
7683
7939
8195
8451
8707
8963
9219
9475
9731
9987
10243
7184
7440
7696
7952
8208
8464
8720
8976
9232
9488
9744
10000
10256
7185
7441
7697
7953
8209
8465
8721
8977
9233
9489
9745
10001
10257
7186
7442
7698
7954
8210
8466
8722
8978
9234
9490
9746
10002
10258
7187
7443
7699
7955
8211
8467
8723
8979
9235
9491
9747
10003
10259
7200
7456
7712
7968
8224
8480
8736
8992
9248
9504
9760
10016
10272
7201
7457
7713
7969
8225
8481
8737
8993
9249
9505
9761
10017
10273
7202
7458
7714
7970
8226
8482
8738
8994
9250
9506
9762
10018
10274
7203
7459
7715
7971
8227
8483
8739
8995
9251
9507
9763
10019
10275
7216
7472
7728
7984
8240
8496
8752
9008
9264
9520
9776
10032
10288
7217
7473
7729
7985
8241
8497
8753
9009
9265
9521
9777
10033
10289
7218
7474
7730
7986
8242
8498
8754
9010
9266
9522
9778
10034
10290
7219
7475
7731
7987
8243
8499
8755
9011
9267
9523
9779
10035
10291
Present Bank Alarm
Lower Limit Value 2
Present Bank Alarm
Value 3
Present Bank Alarm
Upper Limit Value 3
Present Bank Alarm
Lower Limit Value 3
Input Digital Filter
Input Value 1 for
Input Correction
Input Shift 1
Input Value 2 for
Input Correction
10496
10752
11008
11264
11520
11776
12032
12288
10497
10753
11009
11265
11521
11777
12033
12289
10498
10754
11010
11266
11522
11778
12034
12290
10499
10755
11011
11267
11523
11779
12035
12291
10512
10768
11024
11280
11536
11792
12048
12304
10513
10769
11025
11281
11537
11793
12049
12305
10514
10770
11026
11282
11538
11794
12050
12306
10515
10771
11027
11283
11539
11795
12051
12307
10528
10784
11040
11296
11552
11808
12064
12320
10529
10785
11041
11297
11553
11809
12065
12321
10530
10786
11042
11298
11554
11810
12066
12322
10531
10787
11043
11299
11555
11811
12067
12323
10544
10800
11056
11312
11568
11824
12080
12336
10545
10801
11057
11313
11569
11825
12081
12337
10546
10802
11058
11314
11570
11826
12082
12338
10547
10803
11059
11315
11571
11827
12083
12339
Input Shift 2
MV at PV Error
MV at Stop
MV Upper Limit
12544 12545 12546 12547 12560 12561 12562 12563 12576 12577 12578 12579 12592 12593 12594 12595
12800 12801 12802 12803 12816 12817 12818 12819 12832 12833 12834 12835 12848 12849 12850 12851
13056 13057 13058 13059 13072 13073 13074 13075 13088 13089 13090 13091 13104 13105 13106 13107
13312 13313 13314 13315 13328 13329 13330 13331 13344 13345 13346 13347 13360 13361 13362 13363
MV Lower Limit 13568 13569 13570 13571 13584 13585 13586 13587 13600 13601 13602 13603 13616 13617 13618 13619
Hysteresis (Heating) 13824 13825 13826 13827 13840 13841 13842 13843 13856 13857 13858 13859 13872 13873 13874 13875
Hysteresis (Cooling) 14080 14081 14082 14083 14096 14097 14098 14099 14112 14113 14114 14115 14128 14129 14130 14131
Alpha 14336 14337 14338 14339 14352 14353 14354 14355 14368 14369 14370 14371 14384 14385 14386 14387
Manual MV
SP Upper Limit
SP Lower Limit
Disturbance Gain
Disturbance Time
Constant
Disturbance Rectification Band
Disturbance Judgement Width
14592 14593 14594 14595 14608 14609 14610 14611 14624 14625 14626 14627 14640 14641 14642 14643
14848 14849 14850 14851 14864 14865 14866 14867 14880 14881 14882 14883 14896 14897 14898 14899
15104 15105 15106 15107 15120 15121 15122 15123 15136 15137 15138 15139 15152 15153 15154 15155
15360 15361 15362 15363 15376 15377 15378 15379 15392 15393 15394 15395 15408 15409 15410 15411
15616 15617 15618 15619 15632 15633 15634 15635 15648 15649 15650 15651 15664 15665 15666 15667
15872
16128
15873
16129
15874
16130
15875
16131
15888
16144
15889
16145
15890
16146
15891
16147
15904
16160
15905
16161
15906
16162
15907
16163
15920
16176
15921
16177
15922
16178
15923
16179
162
Allocation Numbers for Configurators Manufactured by Other Companies
Appendix B
Parameter name
Heater Burnout 1
Detection (See note
3.)
HS Alarm 1 (See note 3.)
Heater Overcurrent
Detection (See note
3.)
Proportional Band
(Cooling, Current
Bank)
Integral Time (Cooling, Current Bank)
Derivative Time
(Cooling, Current
Bank)
Unit 0 Unit 1 Unit 2 Unit 3 ch1 ch2 ch3 ch4 ch1 ch2 ch3 ch4 ch1 ch2 ch3 ch4 ch1 ch2 ch3 ch4
16384 16385 16386 16387 16400 16401 16402 16403 16416 16417 16418 16419 16432 16433 16434 16435
16640 16641 16642 16643 16656 16657 16658 16659 16672 16673 16674 16675 16688 16689 16690 16691
16896 16897 16898 16899 16912 16913 16914 16915 16928 16929 16930 16931 16944 16945 16946 16947
23296 23297 23298 23299 23312 23313 23314 23315 23328 23329 23330 23331 23344 23345 23346 23347
23552 23553 23554 23555 23568 23569 23570 23571 23584 23585 23586 23587 23600 23601 23602 23603
23808 23809 23810 23811 23824 23825 23826 23827 23840 23841 23842 23843 23856 23857 23858 23859
Note 1.
Both the IN Area and the OUT Area can be allocated to parameters that can be changed during operation.
2.
TC2 Units cannot use allocations for channel 3 or channel 4.
3.
Can be used with TC2 Units, but not TC4 Units.
163
Allocation Numbers for Configurators Manufactured by Other Companies
Appendix B
Units 4 to 7
Parameter name ch1 ch2
Unit 4 ch3 ch4 ch1 ch2
Unit 5 ch3 ch4 ch1 ch2
Unit 6 ch3 ch4 ch1 ch2
Unit 7 ch3 ch4
6976 6977 6978 6979 6992 6993 6994 6995 7008 7009 7010 7011 7024 7025 7026 7027 Present Bank Set
Point
Present Bank Proportional Band
Present Bank Integral
Time
Present Bank Derivative Time
Present Bank SP
Ramp Rise Value
Present Bank SP
Ramp Fall Value
Present Bank Manual
Reset Value 1
Present Bank Cooling Coefficient
Present Bank Dead
Band
Present Bank Alarm
Value
Present Bank Alarm
Upper Limit Value 1
Present Bank Alarm
Lower Limit Value 1
Present Bank Alarm
Value 2
Present Bank Alarm
Upper Limit Value 2
7232
7488
7744
8000
8256
8512
8768
9024
9280
9536
9792
10048
10304
7233
7489
7745
8001
8257
8513
8769
9025
9281
9537
9793
10049
10305
7234
7490
7746
8002
8258
8514
8770
9026
9282
9538
9794
10050
10306
7235
7491
7747
8003
8259
8515
8771
9027
9283
9539
9795
10051
10307
7248
7504
7760
8016
8272
8528
8784
9040
9296
9552
9808
10064
10320
7249
7505
7761
8017
8273
8529
8785
9041
9297
9553
9809
10065
10321
7250
7506
7762
8018
8274
8530
8786
9042
9298
9554
9810
10066
10322
7251
7507
7763
8019
8275
8531
8787
9043
9299
9555
9811
10067
10323
7264
7520
7776
8032
8288
8544
8800
9056
9312
9568
9824
10080
10336
7265
7521
7777
8033
8289
8545
8801
9057
9313
9569
9825
10081
10337
7266
7522
7778
8034
8290
8546
8802
9058
9314
9570
9826
10082
10338
7267
7523
7779
8035
8291
8547
8803
9059
9315
9571
9827
10083
10339
7280
7536
7792
8048
8304
8560
8816
9072
9328
9584
9840
10096
10352
7281
7537
7793
8049
8305
8561
8817
9073
9329
9585
9841
10097
10353
7282
7538
7794
8050
8306
8562
8818
9074
9330
9586
9842
10098
10354
7283
7539
7795
8051
8307
8563
8819
9075
9331
9587
9843
10099
10355
Present Bank Alarm
Lower Limit Value 2
Present Bank Alarm
Value 3
Present Bank Alarm
Upper Limit Value 3
Present Bank Alarm
Lower Limit Value 3
Input Digital Filter
Input Value 1 for
Input Correction
Input Shift 1
Input Value 2 for
Input Correction
Input Shift 2
MV at PV Error
MV at Stop
MV Upper Limit
10560
10816
11072
11328
11584
11840
12096
12352
10561
10817
11073
11329
11585
11841
12097
12353
10562
10818
11074
11330
11586
11842
12098
12354
10563
10819
11075
11331
11587
11843
12099
12355
10576
10832
11088
11344
11600
11856
12112
12368
10577
10833
11089
11345
11601
11857
12113
12369
10578
10834
11090
11346
11602
11858
12114
12370
10579
10835
11091
11347
11603
11859
12115
12371
10592
10848
11104
11360
11616
11872
12128
12384
10593
10849
11105
11361
11617
11873
12129
12385
10594
10850
11106
11362
11618
11874
12130
12386
10595
10851
11107
11363
11619
11875
12131
12387
10608
10864
11120
11376
11632
11888
12144
12400
10609
10865
11121
11377
11633
11889
12145
12401
10610
10866
11122
11378
11634
11890
12146
12402
10611
10867
11123
11379
11635
11891
12147
12403
12608 12609 12610 12611 12624 12625 12626 12627 12640 12641 12642 12643 12656 12657 12658 12659
12864 12865 12866 12867 12880 12881 12882 12883 12896 12897 12898 12899 12912 12913 12914 12915
13120 13121 13122 13123 13136 13137 13138 13139 13152 13153 13154 13155 13168 13169 13170 13171
13376 13377 13378 13379 13392 13393 13394 13395 13408 13409 13410 13411 13424 13425 13426 13427
MV Lower Limit 13632 13633 13634 13635 13648 13649 13650 13651 13664 13665 13666 13667 13680 13681 13682 13683
Hysteresis (Heating) 13888 13889 13890 13891 13904 13905 13906 13907 13920 13921 13922 13923 13936 13937 13938 13939
Hysteresis (Cooling) 14144 14145 14146 14147 14160 14161 14162 14163 14176 14177 14178 14179 14192 14193 14194 14195
Alpha 14400 14401 14402 14403 14416 14417 14418 14419 14432 14433 14434 14435 14448 14449 14450 14451
Manual MV
SP Upper Limit
SP Lower Limit
Disturbance Gain
Disturbance Time
Constant
Disturbance Rectification Band
Disturbance Judgement Width
Heater Burnout 1
Detection (See note
3.)
HS Alarm 1 (See note 3.)
14656
14912
15168
15424
15680
15936
16192
16448
16704
14657
14913
15169
15425
15681
15937
16193
16449
16705
14658
14914
15170
15426
15682
15938
16194
16450
16706
14659
14915
15171
15427
15683
15939
16195
16451
16707
14672
14928
15184
15440
15696
15952
16208
16464
16720
14673
14929
15185
15441
15697
15953
16209
16465
16721
14674
14930
15186
15442
15698
15954
16210
16466
16722
14675
14931
15187
15443
15699
15955
16211
16467
16723
14668
14944
15200
15456
15712
15968
16224
16480
16736
14669
14945
15201
15457
15713
15969
16225
16481
16737
14670
14946
15202
15458
15714
15970
16226
16482
16738
14671
14947
15203
15459
15715
15971
16227
16483
16739
14704
14960
15216
15472
15728
15984
16240
16496
16752
14705
14961
15217
15473
15729
15985
16241
16497
16753
14706
14962
15218
15474
15730
15986
16242
16498
16754
14707
14963
15219
15475
15731
15987
16243
16499
16755
164
Allocation Numbers for Configurators Manufactured by Other Companies
Appendix B
Parameter name
Heater Overcurrent
Detection (See note
3.)
Proportional Band
(Cooling, Current
Bank)
Integral Time (Cooling, Current Bank)
Derivative Time
(Cooling, Current
Bank)
Unit 4 Unit 5 Unit 6 Unit 7 ch1 ch2 ch3 ch4 ch1 ch2 ch3 ch4 ch1 ch2 ch3 ch4 ch1 ch2 ch3 ch4
16960 16961 16962 16963 16976 16977 16978 16979 16992 16993 16994 16995 17008 17009 17010 17011
23360 23361 23362 23363 23376 23377 23378 23379 23392 23393 23394 23395 23408 23409 23410 23411
23616 23617 23618 23619 23632 23633 23634 23635 23648 23649 23650 23651 23664 23665 23666 23667
23872 23873 23874 23875 23888 23889 23890 23891 23904 23905 23906 23907 23920 23921 23922 23923
Note 1.
Both the IN Area and the OUT Area can be allocated to parameters that can be changed during operation.
2.
TC2 Units cannot use allocations for channel 3 or channel 4.
3.
Can be used with TC2 Units, but not TC4 Units.
165
Allocation Numbers for Configurators Manufactured by Other Companies
Appendix B
Units 8 to 11
Parameter name ch1 ch2
Unit 8 ch3 ch4 ch1 ch2
Unit 9 ch3 ch4 ch1
Unit 10 ch2 ch3 ch4 ch1
Unit 11 ch2 ch3 ch4
7040 7041 7042 7043 7056 7057 7058 7059 7072 7073 7074 7075 7088 7089 7090 7091 Present Bank Set
Point
Present Bank Proportional Band
Present Bank Integral
Time
Present Bank Derivative Time
Present Bank SP
Ramp Rise Value
Present Bank SP
Ramp Fall Value
Present Bank Manual
Reset Value
Present Bank Cooling Coefficient
Present Bank Dead
Band
Present Bank Alarm
Value 1
Present Bank Alarm
Upper Limit Value 1
Present Bank Alarm
Lower Limit Value 1
Present Bank Alarm
Value 2
Present Bank Alarm
Upper Limit Value 2
7296
7552
7808
8064
8320
8576
8832
9088
9344
9600
9856
10112
10368
7297
7553
7809
8065
8321
8577
8833
9089
9345
9601
9857
10113
10369
7298
7554
7810
8066
8322
8578
8834
9090
9346
9602
9858
10114
10370
7299
7555
7811
8067
8323
8579
8835
9091
9347
9603
9859
10115
10371
7312
7568
7824
8080
8336
8592
8848
9104
9360
9616
9872
10128
10384
7313
7569
7825
8081
8337
8593
8849
9105
9361
9617
9873
10129
10385
7314
7570
7826
8082
8338
8594
8850
9106
9362
9618
9874
10130
10386
7315
7571
7827
8083
8339
8595
8851
9107
9363
9619
9875
10131
10387
7328
7584
7840
8096
8352
8608
8864
9120
9376
9632
9888
10144
10400
7329
7585
7841
8097
8353
8609
8865
9121
9377
9633
9889
10145
10401
7330
7586
7842
8098
8354
8610
8866
9122
9378
9634
9890
10146
10402
7331
7587
7843
8099
8355
8611
8867
9123
9379
9635
9891
10147
10403
7344
7600
7856
8112
8368
8624
8880
9136
9392
9648
9904
10160
10416
7345
7601
7857
8113
8369
8625
8881
9137
9393
9649
9905
10161
10417
7346
7602
7858
8114
8370
8626
8882
9138
9394
9650
9906
10162
10418
7347
7603
7859
8115
8371
8627
8883
9139
9395
9651
9907
10163
10419
Present Bank Alarm
Lower Limit Value 2
Present Bank Alarm
Value 3
Present Bank Alarm
Upper Limit Value 3
Present Bank Alarm
Lower Limit Value 3
Input Digital Filter
Input Value 1 for
Input Correction
Input Shift 1
Input Value 2 for
Input Correction
Input Shift 2
MV at PV Error
MV at Stop
MV Upper Limit
10624
10880
11136
11392
11648
11904
12160
12416
10625
10881
11137
11393
11649
11905
12161
12417
10626
10882
11138
11394
11650
11906
12162
12418
10627
10883
11139
11395
11651
11907
12163
12419
10640
10896
11152
11408
11664
11920
12176
12432
10641
10897
11153
11409
11665
11921
12177
12433
10642
10898
11154
11410
11666
11922
12178
12434
10643
10899
11155
11411
11667
11923
12179
12435
10656
10912
11168
11424
11680
11936
12192
12448
10657
10913
11169
11425
11681
11937
12193
12449
10658
10914
11170
11426
11682
11938
12194
12450
10659
10915
11171
11427
11683
11939
12195
12451
10672
10928
11184
11440
11696
11952
12208
12464
10673
10929
11185
11441
11697
11953
12209
12465
10674
10930
11186
11442
11698
11954
12210
12466
10675
10931
11187
11443
11699
11955
12211
12467
12672 12673 12674 12675 12688 12689 12690 12691 12704 12705 12706 12707 12720 12721 12722 12723
12928 12929 12930 12931 12944 12945 12946 12947 12960 12961 12962 12963 12976 12977 12978 12979
13184 13185 13186 13187 13200 13201 13202 13203 13216 13217 13218 13219 13232 13233 13234 13235
13440 13441 13442 13443 13456 13457 13458 13459 13472 13473 13474 13475 13488 13489 13490 13491
MV Lower Limit 13696 13697 13698 13699 13712 13713 13714 13715 13728 13729 13730 13731 13744 13745 13746 13747
Hysteresis (Heating) 13952 13953 13954 13955 13968 13969 13970 13971 13984 13985 13986 13987 14000 14001 14002 14003
Hysteresis (Cooling) 14208 14209 14210 14211 14224 14225 14226 14227 14240 14241 14242 14243 14256 14257 14258 14259
Alpha 14464 14465 14466 14467 14480 14481 14482 14483 14496 14497 14498 14499 14512 14513 14514 14515
Manual MV
SP Upper Limit
SP Lower Limit
Disturbance Gain
Disturbance Time
Constant
Disturbance Rectification Band
Disturbance Judgement Width
Heater Burnout 1
Detection (See note
3.)
HS Alarm 1 (See note 3.)
14720
14976
15232
15488
15744
16000
16256
16512
16768
14721
14977
15233
15489
15745
16001
16257
16513
16768
14722
14978
15234
15490
15746
16002
16258
16514
16769
14723
14979
15235
15491
15747
16003
16259
16515
16770
14736
14992
15248
15504
15760
16016
16272
16528
16784
14737
14993
15249
15505
15761
16017
16273
16529
16785
14738
14994
15250
15506
15762
16018
16274
16530
16786
14739
14995
15251
15507
15763
16019
16275
16531
16787
14752
15008
15264
15520
15776
16032
16288
16544
16800
14753
15009
15265
15521
15777
16033
16289
16545
16801
14754
15010
15266
15522
15778
16034
16290
16546
16802
14755
15011
15267
15523
15779
16035
16291
16547
16803
14768
15024
15280
15536
15792
16048
16304
16560
16816
14769
15025
15281
15537
15793
16049
16305
16561
16817
14770
15026
15282
15538
15794
16050
16306
16562
16818
14771
15027
15283
15539
15795
16051
16307
16563
16819
166
Allocation Numbers for Configurators Manufactured by Other Companies
Appendix B
Parameter name
Heater Overcurrent
Detection (See note
3.)
Proportional Band
(Cooling, Current
Bank)
Integral Time (Cooling, Current Bank)
Derivative Time
(Cooling, Current
Bank)
Unit 8 Unit 9 Unit 10 Unit 11 ch1 ch2 ch3 ch4 ch1 ch2 ch3 ch4 ch1 ch2 ch3 ch4 ch1 ch2 ch3 ch4
17024 17025 17026 17027 17040 17041 17042 17043 17056 17057 17058 17059 17072 17073 17074 17075
23424 23425 23426 23427 23440 23441 23442 23443 23456 23457 23458 23459 23472 23473 23474 23475
23680 23681 23682 23683 23696 23697 23698 23699 23712 23713 23714 23715 23728 23729 23730 23731
23936 23937 23938 23939 23952 23953 23954 23955 23968 23969 23970 23971 23984 23985 23986 23987
Note 1.
Both the IN Area and the OUT Area can be allocated to parameters that can be changed during operation
2.
TC2 Units cannot use allocations for channel 3 or channel 4.
3.
Can be used with TC2 Units, but not TC4 Units.
167
Allocation Numbers for Configurators Manufactured by Other Companies
Appendix B
Units 12 to 15
Parameter name ch1
Unit 12 ch2 ch3 ch4 ch1
Unit 13 ch2 ch3 ch4 ch1
Unit 14 ch2 ch3 ch4 ch1
Unit 15 ch2 ch3 ch4
7104 7105 7106 7107 7120 7121 7122 7123 7136 7137 7138 7139 7152 7153 7154 7155 Present Bank Set
Point
Present Bank Proportional Band
Present Bank Integral
Time
Present Bank Derivative Time
Present Bank SP
Ramp Rise Value
Present Bank SP
Ramp Fall Value
Present Bank Manual
Reset Value
Present Bank Cooling Coefficient
Present Bank Dead
Band
Present Bank Alarm
Value 1
Present Bank Alarm
Upper Limit Value 1
Present Bank Alarm
Lower Limit Value 1
Present Bank Alarm
Value 2
Present Bank Alarm
Upper Limit Value 2
7360
7616
7872
8128
8384
8640
8896
9152
9408
9664
9920
10176
10432
7361
7617
7873
8129
8385
8641
8897
9153
9409
9665
9921
10177
10433
7362
7618
7874
8130
8386
8642
8898
9154
9410
9666
9922
10178
10434
7363
7619
7875
8131
8387
8643
8899
9155
9411
9667
9923
10179
10435
7376
7632
7888
8144
8400
8656
8912
9168
9424
9680
9936
10192
10448
7377
7633
7889
8145
8401
8657
8913
9169
9425
9681
9937
10193
10449
7378
7634
7890
8146
8402
8658
8914
9170
9426
9682
9938
10194
10450
7379
7635
7891
8147
8403
8659
8915
9171
9427
9683
9939
10195
10451
7392
7648
7904
8160
8416
8672
8928
9184
9440
9696
9952
10208
10464
7393
7649
7905
8161
8417
8673
8929
9185
9441
9697
9953
10209
10465
7394
7650
7906
8162
8418
8674
8930
9186
9442
9698
9954
10210
10466
7395
7651
7907
8163
8419
8675
8931
9187
9443
9699
9955
10211
10467
7408
7664
7920
8176
8432
8688
8944
9200
9456
9712
9968
10224
10480
7409
7665
7921
8177
8433
8689
8945
9201
9457
9713
9969
10225
10481
7410
7666
7922
8178
8434
8690
8946
9202
9458
9714
9970
10226
10482
7411
7667
7923
8179
8435
8691
8947
9203
9459
9715
9971
10227
10483
Present Bank Alarm
Lower Limit Value 2
Present Bank Alarm
Value 3
Present Bank Alarm
Upper Limit Value 3
Present Bank Alarm
Lower Limit Value 3
Input Digital Filter
Input Value 1 for
Input Correction
Input Shift 1
Input Value 2 for
Input Correction
Input Shift 2
MV at PV Error
MV at Stop
MV Upper Limit
10688
10944
11200
11456
11712
11968
12224
12480
10689
10945
11201
11457
11713
11969
12225
12481
10690
10946
11202
11458
11714
11970
12226
12482
10691
10947
11203
11459
11715
11971
12227
12483
10704
10960
11216
11472
11728
11984
12240
12496
10705
10961
11217
11473
11729
11985
12241
12497
10706
10962
11218
11474
11730
11986
12242
12498
10707
10963
11219
11475
11731
11987
12243
12499
10720
10976
11232
11488
11744
12000
12256
12512
10721
10977
11233
11489
11745
12001
12257
12513
10722
10978
11234
11490
11746
12002
12258
12514
10723
10979
11235
11491
11747
12003
12259
12515
10736
10992
11248
11504
11760
12016
12272
12528
10737
10993
11249
11505
11761
12017
12273
12529
10738
10994
11250
11506
11762
12018
12274
12530
10739
10995
11251
11507
11763
12019
12275
12531
12736 12737 12738 12739 12752 12753 12754 12755 12768 12769 12770 12771 12784 12785 12786 12787
12992 12993 12994 12995 13008 13009 13010 13011 13024 13025 13026 13027 13040 13041 13042 13043
13248 13249 13250 13251 13264 13265 13266 13267 13280 13281 13282 13283 13296 13297 13298 13299
13504 13505 13506 13507 13520 13521 13522 13523 13536 13537 13538 13539 13552 13553 13554 13555
MV Lower Limit 13760 13761 13762 13763 13776 13777 13778 13779 13792 13793 13794 13795 13808 13809 13810 13811
Hysteresis (Heating) 14016 14017 14018 14019 14032 14033 14034 14035 14048 14049 14050 14051 14064 14065 14066 14067
Hysteresis (Cooling) 14272 14273 14274 14275 14288 14289 14290 14291 14304 14305 14306 14307 14320 14321 14322 14323
Alpha 14528 14529 14530 14531 14544 14545 14546 14547 14560 14561 14562 14563 14576 14577 14578 14579
Manual MV
SP Upper Limit
SP Lower Limit
Disturbance Gain
Disturbance Time
Constant
Disturbance Rectification Band
Disturbance Judgement Width
Heater Burnout 1
Detection (See note
3.)
HS Alarm 1 (See note 3.)
14784
15040
15296
15552
15808
16064
16320
16576
16832
14785
15041
15297
15553
15809
16065
16321
16577
16833
14786
15042
15298
15554
15810
16066
16322
16578
16834
14787
15043
15299
15555
15811
16067
16323
16579
16835
14800
15056
15312
15568
15824
16080
16336
16592
16848
14801
15057
15313
15569
15825
16081
16337
16593
16849
14802
15058
15314
15570
15826
16082
16338
16594
16850
14803
15059
15315
15571
15827
16083
16339
16595
16851
14816
15072
15328
15584
15840
16096
16352
16608
16864
14817
15073
15329
15585
15841
16097
16353
16609
16865
14818
15074
15330
15586
15842
16098
16354
16610
16866
14819
15075
15331
15587
15843
16099
16355
16611
16867
14832
15088
15344
15600
15856
16112
16368
16624
16880
14833
15089
15345
15601
15857
16113
16369
16625
16881
14834
15090
15346
15602
15858
16114
16370
16626
16882
14835
15091
15347
15603
15859
16115
16371
16627
16883
168
Allocation Numbers for Configurators Manufactured by Other Companies
Appendix B
Parameter name
Heater Overcurrent
Detection (See note
3.)
Proportional Band
(Cooling, Current
Bank)
Integral Time (Cooling, Current Bank)
Derivative Time
(Cooling, Current
Bank)
Unit 12 Unit 13 Unit 14 Unit 15 ch1 ch2 ch3 ch4 ch1 ch2 ch3 ch4 ch1 ch2 ch3 ch4 ch1 ch2 ch3 ch4
17088 17089 17090 17091 17104 17105 17106 17107 17120 17121 17122 17123 17136 17137 17138 17139
23488 23489 23490 23491 23504 23505 23506 23507 23520 23521 23522 23523 23536 23537 23538 23539
23744 23745 23746 23747 23760 23761 23762 23763 23776 23777 23778 23779 23792 23793 23794 23795
24000 24001 24002 24003 24016 24017 24018 24019 24032 24033 24034 24035 24048 24049 24050 24051
Note 1.
Both the IN Area and the OUT Area can be allocated to parameters that can be changed during operation.
2.
TC2 Units cannot use allocations for channel 3 or channel 4.
3.
Can be used with TC2 Units, but not TC4 Units.
169
Allocation Numbers for Configurators Manufactured by Other Companies
Appendix B
170
Appendix C
List of Connectable Devices
DeviceNet Communications Unit
Model
EJ1N-HFUB-DRT
Specifications
DeviceNet Communications Unit for EJ1 Temperature Controllers
EJ1 Temperature Controllers
Model
Terminal form Control outputs
Specifications
Auxiliary outputs
Functions
Manufacturer
OMRON
Number of control points
Manufacturer
OMRON
OMRON
EJ1N-TC4A-QQ M3 terminals
EJ1N-TC4B-QQ Screw-less clamp terminals
EJ1N-TC2A-
ONHB
M3 terminals
EJ1N-TC2B-
QNHB
Screw-less clamp terminals
EJ1N-TC2A-CNB M3 terminals
EJ1N-TC2B-CNB Screw-less clamp terminals
EJ1C-EDUA-
NFLK
EJ1C-EDUC-
NFLK
M3 terminals
Connector
Voltage outputs (for driving SSR): 4
----4
Voltage outputs (for driving SSR): 2
Transistor outputs: 2 (sinking)
Current outputs: 2
Transistor outputs: 2 (sinking)
---
---
---
Transistor output: 2
Heater burnout alarms: 2
Event inputs: 2
2
Event inputs: 2
-----
DeviceNet Communications Cables
Specifications Model
DCA2-5C10
DCA1-5C10
DVN18-10G
Thick Cable: 5 wires, 100 m
Thin Cable: 5 wires, 100 m
Thick Cable: 5 wires, 10 m
DVN18-30G Thick Cable: 5 wires, 30 m
DVN18-50G
DVN18-100G
DVN18-300G
DVN18-500G
DVN24-10G
Thick Cable: 5 wires, 50 m
Thick Cable: 5 wires, 100 m
Thick Cable: 5 wires, 300 m
Thick Cable: 5 wires, 500 m
Thin Cable: 5 wires, 10 m
OMRON
OMRON
OMRON
OMRON
OMRON
OMRON
Manufacturer
OMRON
OMRON
Nihon Wire & Cable
(See note 1.)
Nihon Wire & Cable
(See note 1.)
Nihon Wire & Cable
(See note 1.)
Nihon Wire & Cable
(See note 1.)
Nihon Wire & Cable
(See note 1.)
Nihon Wire & Cable
(See note 1.)
Nihon Wire & Cable
(See note 1.)
171
List of Connectable Devices
Appendix C
Model
DVN24-30G
DVN24-50G
DVN24-100G
DVN24-300G
DVN24-500G
1485C-P1-A50
1485C-P1-C150
DCA1-5CN @@W1
DCA1-5CN @@F1
DCA1-5CN @@H1
DCA1-5CN @@W5
DCA2-5CN @@W1
DCA2-5CN @@F1
DCA1-5CN @@H1
Thin Cable: 5 wires, 30 m
Thin Cable: 5 wires, 50 m
Thin Cable: 5 wires, 100 m
Thin Cable: 5 wires, 300 m
Thin Cable: 5 wires, 500 m
Thick Cable: 5 wires, 50 m
Thin Cable: 5 wires, 150 m
Specifications
Cable with shielded micro-size (M12) connectors on both ends (female socket and male plug)
Cable length: 0.5 m, 1 m, 2 m, 3 m, 5 m, and 10 m
Cable with shielded micro-size (M12) connector (female socket) on one end
Cable length: 0.5 m, 1 m, 2 m, 3 m, 5 m, and 10 m
Cable with shielded micro-size (M12) connector (male plug) on one end
Cable length: 0.5 m, 1 m, 2 m, 3 m, 5 m, and 10 m
Cable with shielded connector on both ends (male plug on mini-size end, female socket on micro-size end)
Cable length: 1 m, 2 m, 5 m, and 10 m
Cable with shielded mini-size connectors on both ends (female socket and male plug)
Cable length: 1 m, 2 m, 5 m, and 10 m
Cable with shielded mini-size connector on one end (female socket)
Cable length: 1 m, 2 m, 5 m, and 10 m
Cable with shielded mini-size connector on one end (male plug)
Cable length: 1 m, 2 m, 5 m, and 10 m
OMRON
OMRON
OMRON
OMRON
OMRON
OMRON
Manufacturer
Nihon Wire & Cable
(See note 1.)
Nihon Wire & Cable
(See note 1.)
Nihon Wire & Cable
(See note 1.)
Nihon Wire & Cable
(See note 1.)
Nihon Wire & Cable
(See note 1.)
Allen-Bradley (See note 2.)
Allen-Bradley (See note 2.)
OMRON
Note 1.
The cables made by Nihon Wire & Cable Company Ltd. are sold through the OMRON 24 Service Co.,
Ltd. The product specifications 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 Ltd., so do not bend the Allen-Bradley 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.org/) or contact the manufacturer directly.
DeviceNet Communications Connector
Model Specifications Manufacturer
PHOENIX CONTACT
Screwless type, includes connector set screws
172
List of Connectable Devices
Appendix C
Crimp Terminals for DeviceNet Communications Cables
AI series:
Model Crimper
ZA3
AI-0.5-8WH-B for Thin Cable
(product code: 3201369)
AI series:
AI-TWIN2×0.5-8WH for Thin Cable
(product code: 3200933)
UD6
(product code: 1204436)
For single-wire insertion PHOENIX CONTACT
For two-wire insertion
(multi-drop wiring)
Terminating Resistors for DeviceNet Network
Model
DRS1-T
DRS2-1
DRS2-2
DRS3-1
Specifications
Terminal-block Terminating Resistor, 121
Ω ±1% 1/4 W
Shielded Terminating Resistor (male plug), micro-size (M12)
Shielded Terminating Resistor (female socket), micro-size (M12)
Shielded Terminating Resistor (male plug), mini-size
Manufacturer
OMRON
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
DCN1-1C
DCN1-2C
DCN1-2R
Specifications
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.
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.
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.
Three-branch Taps
Model
DCN1-3C
DCN1-4C
DCN1-4R
Specifications
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.
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.
Includes five XW4B-05C1-H1-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.
Manufacturer
OMRON
OMRON
OMRON
Manufacturer
OMRON
OMRON
OMRON
173
List of Connectable Devices
Appendix C
Shielded T-branch Connectors
Model
DCN2-1
DCN3-11
DCN3-12
Specifications
One-branch shielded T-branch connectors, three micro-size (M12) connectors
One-branch shielded T-branch connectors, three mini-size connectors
One-branch shielded T-branch connectors, two mini-size connectors and one micro-size (M12) connector
Manufacturer
OMRON
One-branch Power Supply Tap
Model
DCN-1P
Specifications
One-branch tap for power supply. Use this tap when connecting a communications 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.
Manufacturer
OMRON
174
A
attribute ID
B
baud rate
,
automatic detection
C
cables communications cables models
,
class ID
,
cleaning
command block
commands sending to Temperature Controllers
,
communications cycle time
DeviceNet remote I/O
,
distance
explicit messages
,
functions
media
,
message communications time
,
performance
power supply
refresh time
specifications
timing
Communications Cables
,
Communications Connectors
Communications Unit comment setting
,
CompoWay/F
,
command examples
sending commands
,
Configurator
connecting
I/O allocations
,
procedures
connectors
,
attaching
,
models
,
copy operation
DIP switch
,
Index
crimp terminals
models
,
D
decimal point position
destination node address
device profiles
,
DeviceNet Communications Unit
dimensions
,
DIN Rail mounting
,
E
EMC Directives
End Plates removing
,
error codes
,
error control
,
error history
explicit messages
,
basic format
,
communications time
error codes
,
example
,
General Status Read
Maintenance Counter Save
overview
sending
,
Set Value for Unit Conduction Time or Total RUN Time
,
Temperature Controller Channel Maintenance Information Monitor Mode
,
types
,
Unit Conduction Time or Total RUN Time Read
Unit Maintenance Bit
,
Unit Maintenance Present Value
,
Unit Maintenance Set Value
,
F
features
FINS-mini commands
,
fixed allocations
175
176
I
I/O allocations
,
data configuration
master
,
procedure
,
remote I/O communications
,
simple allocation
,
simple allocations
,
using the Configurator
I/O response time
,
IN area
dividing in two
,
indicators
,
troubleshooting
,
input data
inspection
,
installation
,
instance ID
,
L
Last Maintenance Date setting
,
Low Voltage Directive
,
M
maintenance
,
functions
information
,
replacing Units
Maintenance Counter
message communications time
model numbers
module status indicator
,
Monitor Mode setting
,
monitoring
,
mounting
MS indicator
,
multivendor connections
,
MV Upper Limit/Lower Limit changing
,
Index
N
Network Power Voltage Monitor setting
,
network status indicator
,
node address setting
,
NS indicator
Number of Bytes Received
O
One-branch Power Supply Taps
,
One-branch Taps
,
operation
,
procedures
ordering information
,
OUT area
P
parameters copying
,
editing
,
reading and writing
,
part names
,
PFP-100N
,
PFP-50N
,
PFP-M
,
power supply
products
,
programming examples
,
PV reading
,
R
refresh time
,
remote I/O communications
,
replacing Units
,
response block
RUN/STOP Bits
,
S
service code
,
setup
monitoring
parameters
,
procedure
Temperature Controller Parameters
,
using explicit messages
,
Shielded T-branch Connectors
,
Source Node Address
,
SP changing
,
writing
specifications
,
DeviceNet
,
startup time
,
switches
settings
,
system configuration
,
T
T-branch Taps
,
models
Temperature Controller Comments setting
Temperature Controller IDs
,
Temperature Controllers
,
communications status indicator
,
editing parameters
,
initial settings
,
number
,
registration
,
sending commands
Terminating Resistors
,
models
Three-branch Taps
troubleshooting
,
TS indicator
,
U
Unit Conduction Time Monitor setting
Unit status
,
user-set allocations
Index
177
178
Index
Revision History
A manual revision code appears as a suffix to the catalog number on the front cover of the manual.
Cat. No. H155-E1-03
Revision code
The following table outlines the changes made to the manual during each revision. Page numbers refer to the previous version.
Revision code
01
01A
Date
January 2008
March 2008
02
02A
03
July 2008
July 2008
July 2015
Revised content
Original production
Pages 2, 19, 37, and 39: Removed reference to the rear panel in descriptions of the simple I/O allocation function.
Page 36: Corrected missing lines in PLC illustration.
Added numbers for parameters added for a functional upgrade. These parameters can be used with version 1.2 or higher.
Added the G3PW Power Controller. The G3PW can be used with Temperature Controllers with version 1.1 or higher.
Pages 55, 151, and 152: Removed table rows for OUT Enable Bit 2.
Cover: Added trademark symbol.
Front matter: Added information before title page and replaced information on NOTE, Trademarks, and Copyrights page.
Page v: Removed information from the bottom of the page.
Pages vi and vii : Replaced information.
Pages I and II: Replaced information.
Page xiv: Added trademark symbol and changed name of W380 manual.
Page xv: Updated manual names.
Page 9: Added specifications on I/O allocation data sizes.
Page 11: Added electromagnetic environment specifications to bottom of table.
Pages 41 and 42: Changed “Not used” to “Cannot be used.”
Pages 65 and 66: Changed parts of OUT Enable Bit section.
Page 72: Changed callout and note after figure.
Page 86: Changed wording of caution.
Pages 145 and 172: Changed ULR.
179
180
Revision History
OMRON Corporation
Industrial Automation Company
Kyoto, JAPAN
Contact: www.ia.omron.com
Regional Headquarters
OMRON EUROPE B.V.
Wegalaan 67-69, 2132 JD Hoofddorp
The Netherlands
Tel: (31)2356-81-300/Fax: (31)2356-81-388
OMRON ELECTRONICS LLC
2895 Greenspoint Parkway, Suite 200
Hoffman Estates, IL 60169 U.S.A.
Tel: (1) 847-843-7900/Fax: (1) 847-843-7787
Authorized Distributor:
OMRON ASIA PACIFIC PTE. LTD.
No. 438A Alexandra Road # 05-05/08 (Lobby 2),
Alexandra Technopark,
Singapore 119967
Tel: (65) 6835-3011/Fax: (65) 6835-2711
OMRON (CHINA) CO., LTD.
Room 2211, Bank of China Tower,
200 Yin Cheng Zhong Road,
PuDong New Area, Shanghai, 200120, China
Tel: (86) 21-5037-2222/Fax: (86) 21-5037-2200
© OMRON Corporation 2008 All Rights Reserved.
In the interest of product improvement, specifications are subject to change without notice.
Cat. No. H155-E1-03
0715
advertisement
Key Features
- Remote I/O Communications
- Explicit Message Communications
- Configurator Support
- Automatic Baud Rate Detection
- Wide Range of Maintenance Functions
- Simultaneously Managing Multiple Temperature Controllers
- Expansion Remote I/O