Omron SYSMAC CS Series Operation Manual

Programmable Controllers SYSMAC CS Series CS1G/H-CPU_H CS1G/H-CPU_-EV1 OPERATION MANUAL

CS1G/H-CPU@@H, CS1G/H-CPU@@-EV1 Programmable Controllers Operation Manual Revised March 2010

by a qualified operator and only for the purposes described in this manual. The following conventions are used to indicate and classify precautions in this manual. Always heed the information provided with them. Failure to heed pre- cautions can result in injury to people or damage to property. !DANGER Indicates an imminently hazardous situation which, if not avoided, will result in death or serious injury. Additionally, there may be severe property damage. !WARNING Indicates a potentially hazardous situation which, if not avoided, could result in death or serious injury. Additionally, there may be severe property damage. !Caution Indicates a potentially hazardous situation which, if not avoided, may result in minor or moderate injury, or property damage. OMRON Product References All OMRON products are capitalized in this manual. The word “Unit” is also capitalized when it refers to an OMRON product, regardless of whether or not it appears in the proper name of the product. The abbreviation “Ch,” which appears in some displays and on some OMRON products, often means “word” and is abbreviated “Wd” in documentation in this sense. The abbreviation “PLC” means Programmable Controller. “PC” is used, how- ever, in some Programming Device displays to mean Programmable Control- ler. 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.  OMRON, 1999 All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form, or by any means, mechanical, electronic, photocopying, recording, or otherwise, without the prior written permission of OMRON. No patent liability is assumed with respect to the use of the information contained herein. Moreover, because OMRON is con- stantly striving to improve its high-quality products, the information contained in this manual is subject to change without notice. Every precaution has been taken in the preparation of this manual. Nevertheless, OMRON assumes no responsibility for errors or omissions. Neither is any liability assumed for damages resulting from the use of the information contained in this publication.

Unit Versions A “unit version” has been introduced to manage CPU Units in the CS/CJ Series according to differences in functionality accompanying Unit upgrades. This applies to the CS1-H, CJ1-H, CJ1M, and CS1D CPU Units. Notation of Unit Versions on Products The unit version is given to the right of the lot number on the nameplate of the products for which unit versions are being managed, as shown below. • CS1-H, CJ1-H, and CJ1M CPU Units manufactured on or before Novem- ber 4, 2003 do not have a unit version given on the CPU Unit (i.e., the location for the unit version shown above is blank). • The unit version of the CS1-H, CJ1-H, and CJ1M CPU Units, as well as the CS1D CPU Units for Single-CPU Systems, begins at version 2.0. • The unit version of the CS1D CPU Units for Duplex-CPU Systems, begins at version 1.1. • CPU Units for which a unit version is not given are called Pre-Ver. @.@ CPU Units, such as Pre-Ver. 2.0 CPU Units and Pre-Ver. 1.1 CPU Units. Confirming Unit Versions with Support Software CX-Programmer version 4.0 can be used to confirm the unit version using one of the following two methods. • Using the PLC Information • Using the Unit Manufacturing Information (This method can be used for Special I/O Units and CPU Bus Units as well.) Note CX-Programmer version 3.3 or lower cannot be used to confirm unit versions. PLC Information • If you know the device type and CPU type, select them in the Change PLC Dialog Box, go online, and select PLC - Edit - Information from the menus. • If you don't know the device type and CPU type, but are connected directly to the CPU Unit on a serial line, select PLC - Auto Online to go online, and then select PLC - Edit - Information from the menus. In either case, the following PLC Information Dialog Box will be displayed. CS1H-CPU67H CPU UNIT Lot No. 040715 0000 Ver.3.0 OMRON Corporation MADE IN JAPAN CS/CJ-series CPU Unit Product nameplate Lot No. Unit version Example for Unit version 3.0

Unit Manufacturing Information In the IO Table Window, right-click and select Unit Manufacturing informa- tion - CPU Unit. The following Unit Manufacturing information Dialog Box will be displayed. Unit version

online. Using the Unit Version Labels The following unit version labels are provided with the CPU Unit. These labels can be attached to the front of previous CPU Units to differenti- ate between CPU Units of different unit versions. Unit version

In this manual, the unit version of a CPU Unit is given as shown in the follow- ing table. Product nameplate Meaning CPU Units on which no unit version is given Units on which a version is given (Ver. @.@) Designating individual CPU Units (e.g., the CS1H-CPU67H) Pre-Ver. 2.0 CS1-H CPU Units CS1H-CPU67H CPU Unit Ver. @.@ Designating groups of CPU Units (e.g., the CS1-H CPU Units) Pre-Ver. 2.0 CS1-H CPU Units CS1-H CPU Units Ver. @.@ Designating an entire series of CPU Units (e.g., the CS-series CPU Units) Pre-Ver. 2.0 CS-series CPU Units CS-series CPU Units Ver. @.@ Lot No. XXXXXX XXXX OMRON Corporation MADE IN JAPAN Lot No. XXXXXX XXXX Ver. @ @ .@

• Functions Supported for Unit Version 4.0 or Later CX-Programmer 7.0 or higher must be used to enable using the functions added for unit version 4.0. CX-Programmer version 7.2 can be used to enable using additional functions. CS1-H CPU Units User programs that contain functions supported only by CPU Units with unit version 4.0 or later cannot be used on CS/CJ-series CPU Units with unit ver- sion 3.0 or earlier. An error message will be displayed if an attempt is made to download programs containing unit version 4.0 functions to a CPU Unit with a unit version of 3.0 or earlier, and the download will not be possible. If an object program file (.OBJ) using these functions is transferred to a CPU Unit with a unit version of 3.0 or earlier, a program error will occur when oper- ation is started or when the unit version 4.0 function is executed, and CPU Unit operation will stop. Units Models Unit version CS1-H CPU Units CS1@-CPU@@H Unit version 4.0 Unit version 3.0 Unit version 2.0 Pre-Ver. 2.0 CS1D CPU Units Duplex-CPU Systems CS1D-CPU@@H Unit version 1.2 Unit version 1.1 Pre-Ver. 1.1 Single-CPU Systems CS1D-CPU@@S Unit version 2.0 CS1 CPU Units CS1@-CPU@@ No unit version. CS1 Version-1 CPU Units CS1@-CPU@@-V1 No unit version. Function CS1@-CPU@@H Unit version 4.0 or later Other unit versions Online editing of function blocks Note This function cannot be used for simulations on the CX- Simulator. OK --- Input-output variables in function blocks OK --- Text strings in function blocks OK --- New application instructions Number-Text String Conversion Instructions: NUM4, NUM8, NUM16, STR4, STR8, and STR16 OK --- TEXT FILE WRITE (TWRIT) OK --- The ST language can be used in task programs. OK with CX-Programmer version 7.2 or higher --- The SFC language can be used in task programs. OK with CX-Programmer version 7.2 or higher ---

CX-Programmer 5.0 or higher must be used to enable using the functions added for unit version 3.0. CS1-H CPU Units User programs that contain functions supported only by CPU Units with unit version 3.0 or later cannot be used on CS/CJ-series CPU Units with unit ver- sion 2.0 or earlier. An error message will be displayed if an attempt is made to download programs containing unit version 3.0 functions to a CPU Unit with a unit version of 2.0 or earlier, and the download will not be possible. If an object program file (.OBJ) using these functions is transferred to a CPU Unit with a unit version of 2.0 or earlier, a program error will occur when oper- ation is started or when the unit version 3.0 function is executed, and CPU Unit operation will stop. Function CS1@-CPU@@H Unit version 3.0 or later Other unit versions Function blocks OK --- Serial Gateway (converting FINS commands to CompoWay/F commands at the built-in serial port) OK --- Comment memory (in internal flash memory) OK --- Expanded simple backup data OK --- New application instructions TXDU(256), RXDU(255) (support no-protocol communications with Serial Communications Units with unit version 1.2 or later) OK --- Model conversion instructions: XFERC(565), DISTC(566), COLLC(567), MOVBC(568), BCNTC(621) OK --- Special function block instructions: GETID(286) OK --- Additional instruction func- tions TXD(235) and RXD(236) instructions (support no- protocol communications with Serial Communica- tions Boards with unit version 1.2 or later) OK ---

CX-Programmer 4.0 or higher must be used to enable using the functions added for unit version 2.0. CS1-H CPU Units User programs that contain functions supported only by CPU Units with unit version 2.0 or later cannot be used on CS/CJ-series Pre-Ver. 2.0 CPU Units. An error message will be displayed if an attempt is made to download pro- grams containing unit version s.0 functions to a Pre-Ver. 2.0 CPU Unit, and the download will not be possible. If an object program file (.OBJ) using these functions is transferred to a Pre- Ver. 2.0 CPU Unit, a program error will occur when operation is started or when the unit version 2.0 function is executed, and CPU Unit operation will stop. Function CS1-H CPU Units (CS1@-CPU@@H) Unit version 2.0 or later Other unit versions Downloading and Uploading Individual Tasks OK --- Improved Read Protection Using Passwords OK --- Write Protection from FINS Commands Sent to CPU Units via Networks OK --- Online Network Connections without I/O Tables OK --- Communications through a Maximum of 8 Network Levels OK --- Connecting Online to PLCs via NS-series PTs OK OK from lot number 030201 Setting First Slot Words OK for up to 64 groups OK for up to 8 groups Automatic Transfers at Power ON without a Parameter File OK --- Automatic Detection of I/O Allocation Method for Automatic Transfer at Power ON --- --- Operation Start/End Times OK --- New Application Instructions MILH, MILR, MILC OK --- =DT, <>DT, DT, >=DT OK --- BCMP2 OK --- GRY OK OK from lot number 030201 TPO OK --- DSW, TKY, HKY, MTR, 7SEG OK --- EXPLT, EGATR, ESATR, ECHRD, ECHWR OK --- Reading/Writing CPU Bus Units with IORD/IOWR OK OK from lot number 030418 PRV2 --- ---

The following tables show the relationship between unit versions and CX-Pro- grammer versions. Unit Versions and Programming Devices Note 1. As shown above, there is no need to upgrade to CX-Programmer version as long as the functions added for unit versions are not used. 2. CX-Programmer version 7.0 or higher is required to use the upgraded functions for CS/CJ-series CPU Units with unit version 4.0. CX-Program- mer version 7.2 can be used to enable using additional functions. Device Type Setting The unit version does not affect the setting made for the device type on the CX-Programmer. Select the device type as shown in the following table regardless of the unit version of the CPU Unit. CPU Unit Functions CX-Programmer Program- ming Console Ver. 3.3 or lower Ver. 4.0 Ver. 5.0 Ver. 6.0 Ver. 7.0 or higher Ver. 7.2 or higher CS/CJ-series unit Ver. 4.0 Functions added for unit version 4.0 Using new functions --- --- --- OK (See note 2.) OK (See note 2.) No restric- tions Not using new func- tions OK OK OK OK OK CS/CJ-series unit Ver. 3.0 Functions added for unit version 3.0 Using new functions --- --- OK OK OK Not using new func- tions OK OK OK OK OK CS/CJ-series unit Ver. 2.0 Functions added for unit version 2.0 Using new functions --- OK OK OK OK Not using new func- tions OK OK OK OK OK CS1D CPU Units for Single-CPU Systems, unit Ver. 2.0 Functions added for unit version 2.0 Using new functions --- OK OK OK OK Not using new func- tions CS1D CPU Units for Duplex-CPU Systems, unit Ver.1. Functions added for unit version 1.1 Using function blocks --- OK OK OK OK Not using function blocks OK OK OK OK OK Series CPU Unit group CPU Unit model Device type setting on CX-Programmer Ver. 4.0 or higher CS Series CS1-H CPU Units CS1G-CPU@@H CS1G-H CS1H-CPU@@H CS1H-H CS1D CPU Units for Duplex-CPU Systems CS1D-CPU@@H CS1D-H (or CS1H-H) CS1D CPU Units for Single-CPU Systems CS1D-CPU@@S CS1D-S

Problem Cause Solution After the above message is displayed, a compiling error will be displayed on the Compile Tab Page in the Output Window. An attempt was made to down- load a program containing instructions supported only by later unit versions or a CPU Unit to a previous unit version. Check the program or change to a CPU Unit with a later unit version. An attempt was to download a PLC Setup containing settings supported only by later unit ver- sions or a CPU Unit to a previous unit version. Check the settings in the PLC Setup or change to a CPU Unit with a later unit version. “????” is displayed in a program transferred from the PLC to the CX-Programmer. An attempt was made to upload a program containing instructions supported only by higher versions of CX-Programmer to a lower ver- sion. New instructions cannot be uploaded to lower versions of CX-Programmer. Use a higher version of CX-Programmer.

PRECAUTIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii 1 Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxviii 2 General Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxviii 3 Safety Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxviii 4 Operating Environment Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxx 5 Application Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxi 6 Conformance to EC Directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxvi SECTION 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1-1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1-2 CS-series Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1-3 CS1-H CPU Unit Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 1-4 CS1-H CPU Unit Ver. 4.0 Upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 1-5 CS1-H CPU Unit Ver. 3.0 Upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 1-6 CS1-H CPU Unit Ver. 2.0 Upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 1-7 CS1 and CS1-H CPU Unit Comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 1-8 CS-series Function Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 1-9 CS1-H Functions Arranged by Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 1-10 Comparison of CS-series PLCs and C200HX/HG/HE Operation . . . . . . . . . . . . . . . . . . . . 66 1-11 Checking the Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 1-12 Initial Setup for CS1 CPU Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 1-13 Using the Internal Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 SECTION 2 Specifications and System Configuration. . . . . . . . . . . . . . . 77 2-1 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 2-2 CPU Unit Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 2-3 Basic System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 2-4 Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 2-5 Expanded System Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 2-6 Unit Current Consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 2-7 CPU Bus Unit Setting Area Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 2-8 I/O Table Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 SECTION 3 Nomenclature, Functions, and Dimensions . . . . . . . . . . . . . 163 3-1 CPU Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 3-2 File Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 3-3 Programming Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 3-4 Power Supply Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 3-5 Backplanes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 3-6 Basic I/O Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 3-7 C200H High-density I/O Units (Special I/O Units) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 3-8 B7A Interface Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 3-9 Analog Timer Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

SECTION 4 Operating Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 4-1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 4-2 Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 SECTION 5 Installation and Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287 5-1 Fail-safe Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288 5-2 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290 5-3 Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 SECTION 6 DIP Switch Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335 6-1 DIP Switch Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 SECTION 7 PLC Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339 7-1 PLC Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340 7-2 Explanations of PLC Setup Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367 SECTION 8 I/O Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379 8-1 I/O Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 8-2 I/O Allocation Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385 8-3 Allocating First Words to Racks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392 8-4 Allocating First Words to Slots. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395 8-5 Detailed Information on I/O Table Creation Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398 8-6 Data Exchange with CPU Bus Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398 SECTION 9 Memory Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403 9-1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404 9-2 I/O Memory Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405 9-3 Precautions in Using C200H Special I/O Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414 9-4 CIO Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415 9-5 C200H DeviceNet Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421 9-6 CS-series DeviceNet Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422 9-7 PLC Link Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424 9-8 Data Link Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426 9-9 CPU Bus Unit Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427 9-10 Inner Board Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428 9-11 Special I/O Unit Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429 9-12 SYSMAC BUS Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431 9-13 I/O Terminal Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432 9-14 Work Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433

9-15 Holding Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434 9-16 Auxiliary Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435 9-17 TR (Temporary Relay) Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458 9-18 Timer Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459 9-19 Counter Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460 9-20 Data Memory (DM) Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461 9-21 Extended Data Memory (EM) Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463 9-22 Index Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465 9-23 Data Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471 9-24 Task Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473 9-25 Condition Flags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473 9-26 Clock Pulses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476 9-27 Parameter Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477 SECTION 10 CPU Unit Operation and the Cycle Time. . . . . . . . . . . . . . . 481 10-1 CPU Unit Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483 10-2 CPU Unit Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488 10-3 Power OFF Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490 10-4 Computing the Cycle Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495 10-5 Instruction Execution Times and Number of Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514 SECTION 11 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549 11-1 Error Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550 11-2 Error Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551 11-3 Troubleshooting Racks and Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573 SECTION 12 Inspection and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . 577 12-1 Inspections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578 12-2 Replacing User-serviceable Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580 Appendices A Specifications of Basic I/O Units and High-density I/O Units . . . . . . . . . . . . . . . . . . . . . . 591 B Auxiliary Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713 C Memory Map of PLC Memory Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751 D PLC Setup Coding Sheets for Programming Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753 E Connecting to the RS-232C Port on the CPU Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765 F Restrictions in Using C200H Special I/O Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773 G CJ1W-CIF11 RS-422A Converter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785 Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795

This manual describes the installation and operation of the CS-series Programmable Controllers (PLCs) and includes the sections described on the following page. The CS Series and CJ Series are subdivided as shown in the following figure. Please read this manual and all related manuals listed in the following table and be sure you under- stand information provided before attempting to install or use CS1G/H-CPU@@-EV1 or CS1G/H- CPU@@H CPU Units in a PLC System. Name Cat. No. Contents SYSMAC CS Series CS1G/H-CPU@@H, CS1G/H-CPU@@-EV1 Programmable Controllers Operation Manual W339 Provides an outlines of and describes the design, installation, maintenance, and other basic operations for the CS-series PLCs. (This manual) SYSMAC CS/CJ/NSJ Series CS1G/H-CPU@@-EV1, CS1G/H-CPU@@H, CS1D-CPU@@H, CS1D-CPU@@S, CJ1H-CPU@@H-R, CJ1G-CPU@@, CJ1M- CPU@@, CJ1G-CPU@@P, CJ1G/H-CPU@@H Programmable Controllers Programming Manual W394 This manual describes programming and other methods to use the functions of the CS/ CJ-series PLCs. SYSMAC CS/CJ/NSJ Series CS1G/H-CPU@@-EV1, CS1G/H-CPU@@H, CS1D-CPU@@H, CS1D-CPU@@S, CJ1H-CPU@@H-R, CJ1G-CPU@@, CJ1M- CPU@@, CJ1G-CPU@@P, CJ1G/H-CPU@@H Programmable Controllers Instructions Reference Manual W340 Describes the ladder diagram programming instructions supported by CS/CJ-series PLCs. CS1H-CPU@@H CS1G-CPU@@H CS1-H CPU Units CS Series CS1 CPU Units CS1H-CPU@@(-V1) CS1G-CPU@@(-V1) CS1D CPU Units CS1D CPU Units for Duplex Systems CS1D-CPU@@H CS1D CPU Units for Simplex Systems CS1D-CPU@@S CS1D Process-control CPU Units CS1D-CPU@@P CS-series Basic I/O Units CS-series Special I/O Units CS-series CPU Bus Units CS-series Power Supply Units Note: A special Power Supply Unit must be used for CS1D CPU Units. CJ-series Power Supply Units CJ-series CPU Bus Units CJ-series Special I/O Units CJ-series Basic I/O Units CJ1G-CPU@@ CJ1 CPU Units CJ1M CPU Units CJ1M-CPU@@ CJ1H-CPU@@H-R CJ1H-CPU@@H CJ1G-CPU@@H CJ1G -CPU@@P (Loop-control CPU Units) CJ1-H CPU Units CJ Series CJ2H-CPU@@-@@@ CJ2 CPU Units NSJ Series NSJ Controllers NSJ-series Expansion Units NSJ Controllers NSJ5-TQ@@(B)-G5D NSJ5-SQ@@(B)-G5D NSJ8-TV@@(B)-G5D NSJ10-TV@@(B)-G5D NSJ12-TS@@(B)-G5D NSJ5-TQ@@(B)-M3D NSJ5-SQ@@(B)-M3D NSJ8-TV@@(B)-M3D

Section 1 introduces the special features and functions of the CS-series PLCs and describes the dif- ferences between these PLCs and other PLCs. Section 2 provides tables of standard models, Unit specifications, system configurations, and a com- parison between different Units. Section 3 provides the names of components and their functions for various Units. The Unit dimen- sions are also provided. Section 4 outlines the steps required to assemble and operate a CS-series PLC system. SYSMAC CS/CJ/NSJ Series CQM1H-PRO01-E, C200H-PRO27-E, CQM1-PRO01-E Programming Consoles Operation Manual W341 Provides information on how to program and operate CS/CJ-series PLCs using a Program- ming Console. SYSMAC CS/CJ/NSJ Series CS1G/H-CPU@@-EV1, CJ1G/H-CPU@@H, CS1D-CPU@@H, CS1D-CPU@@S, CJ1M-CPU@@, CJ1H-CPU@@H-R, CJ1G- CPU@@, CJ1G-CPU@@, CJ1G-CPU@@P, CJ1G/H-CPU@@H, CS1W-SCB@@-V1, CS1W-SCU@@-V1, CJ1W-SCU@@-V1, CP1H-X@@@@-@, CP1H-XA@@@@-@, CP1H-Y@@@@-@ Communications Commands Reference Manual W342 Describes the C-series (Host Link) and FINS communications commands used with CS/CJ- series PLCs. SYSMAC CS Series CS1D-CPU@@H CPU Units CS1D-CPU@@S CPU Units CS1D-DPL01 Duplex Unit CS1D-PA207R Power Supply Unit Duplex System Operation Manual W405 Provides an outline of and describes the design, installation, maintenance, and other basic operations for a Duplex System based on CS1D CPU Units. SYSMAC WS02-CXPC@-E-V@ CX-Programmer Operation Manual W446 Provides information on how to use the CX- Programmer for all functionality except for function blocks. SYSMAC WS02-CXPC@-E-V@ CX-Programmer Ver. 7.0 Operation Manual Function Blocks (CS1G-CPU@@H, CS1H-CPU@@H, CJ1H-CPU@@H-R, CJ1G-CPU@@H, CJ1H-CPU@@H, CJ1M-CPU@@, CP1H-X@@@@-@, CP1H-XA@@@@-@, CP1H-Y@@@@-@ CPU Units) W447 Describes the functionality unique to the CX- Programmer and CP-series CPU Units or CS/ CJ-series CPU Units with unit version 3.0 or later based on function blocks. Functionality that is the same as that of the CX-Program- mer is described in W446 (enclosed). SYSMAC CS/CJ Series CS1W-SCB@@-V1, CS1W-SCU@@-V1, CJ1W-SCU@@-V1 Serial Communications Boards/Units Operation Manual W336 Describes the use of Serial Communications Unit and Boards to perform serial communica- tions with external devices, including the usage of standard system protocols for OMRON prod- ucts. SYSMAC WS02-PSTC1-E CX-Protocol Operation Manual W344 Describes the use of the CX-Protocol to cre- ate protocol macros as communications sequences to communicate with external devices. CXONE-AL@@C-V4/AL@@D-V4 CX-Integrator Operation Manual W464 Describes operating procedures for the CX- Integrator Network Configuration Tool for CS-, CJ-, CP-, and NSJ-series Controllers. CXONE-AL@@C-V4/AL@@D-V4 CX-One Setup Manual W463 Installation and overview of CX-One FA Integrated Tool Package. Name Cat. No. Contents

System. Be sure to follow the instructions carefully. Improper installation can cause the PLC to mal- function, resulting in very dangerous situations. Section 6 describes the settings of the DIP switch and how they affect operation. Section 7 describes the settings in the PLC Setup and how they are used to control CPU Unit opera- tion. Section 8 describes I/O allocations to Basic I/O Units, Special I/O Units, and CPU Bus Units, and data exchange with Units. Section 9 describes the structure and functions of the I/O Memory Areas and Parameter Areas. Section 10 describes the internal operation of the CPU Unit and the cycle used to perform internal processing. Section 11 provides information on hardware and software errors that occur during PLC operation. Section 12 provides inspection and maintenance information. The Appendices provide Unit specifications, current/power consumptions, Auxiliary Area words and bits, a comparison of CS-series and previous PLCs, internal I/O addresses, and PLC Setup settings. !WARNING Failure to read and understand the information provided in this manual may result in per- sonal injury or death, damage to the product, or product failure. Please read each section in its entirety and be sure you understand the information provided in the section and related sections before attempting any of the procedures or operations given.

Please read and understand this manual before using the product. Please consult your OMRON representative if you have any questions or comments. Warranty and Limitations of Liability WARRANTY OMRON's exclusive warranty is that the products are free from defects in materials and workmanship for a period of one year (or other period if specified) from date of sale by OMRON. OMRON MAKES NO WARRANTY OR REPRESENTATION, EXPRESS OR IMPLIED, REGARDING NON- INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR PARTICULAR PURPOSE OF THE PRODUCTS. ANY BUYER OR USER ACKNOWLEDGES THAT THE BUYER OR USER ALONE HAS DETERMINED THAT THE PRODUCTS WILL SUITABLY MEET THE REQUIREMENTS OF THEIR INTENDED USE. OMRON DISCLAIMS ALL OTHER WARRANTIES, EXPRESS OR IMPLIED. LIMITATIONS OF LIABILITY OMRON SHALL NOT BE RESPONSIBLE FOR SPECIAL, INDIRECT, OR CONSEQUENTIAL DAMAGES, LOSS OF PROFITS OR COMMERCIAL LOSS IN ANY WAY CONNECTED WITH THE PRODUCTS, WHETHER SUCH CLAIM IS BASED ON CONTRACT, WARRANTY, NEGLIGENCE, OR STRICT LIABILITY. In no event shall the responsibility of OMRON for any act exceed the individual price of the product on which liability is asserted. IN NO EVENT SHALL OMRON BE RESPONSIBLE FOR WARRANTY, REPAIR, OR OTHER CLAIMS REGARDING THE PRODUCTS UNLESS OMRON'S ANALYSIS CONFIRMS THAT THE PRODUCTS WERE PROPERLY HANDLED, STORED, INSTALLED, AND MAINTAINED AND NOT SUBJECT TO CONTAMINATION, ABUSE, MISUSE, OR INAPPROPRIATE MODIFICATION OR REPAIR.

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

Product specifications and accessories may be changed at any time based on improvements and other reasons. It is our practice to change model numbers when published ratings or features are changed, or when significant construction changes are made. However, some specifications of the products may be changed without any notice. When in doubt, special model numbers may be assigned to fix or establish key specifications for your application on your request. Please consult with your OMRON representative at any time to confirm actual specifications of purchased products. DIMENSIONS AND WEIGHTS Dimensions and weights are nominal and are not to be used for manufacturing purposes, even when tolerances are shown. PERFORMANCE DATA Performance data given in this manual is provided as a guide for the user in determining suitability and does not constitute a warranty. It may represent the result of OMRON's test conditions, and the users must correlate it to actual application requirements. Actual performance is subject to the OMRON Warranty and Limitations of Liability. ERRORS AND OMISSIONS The information in this manual has been carefully checked and is believed to be accurate; however, no responsibility is assumed for clerical, typographical, or proofreading errors, or omissions.

The information contained in this section is important for the safe and reliable application of Programmable Controllers. You must read this section and understand the information contained before attempting to set up or operate a PLC system. 1 Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxviii 2 General Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxviii 3 Safety Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxviii 4 Operating Environment Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxx 5 Application Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxi 6 Conformance to EC Directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxvi 6-1 Applicable Directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxvi 6-2 Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxvi 6-3 Conformance to EC Directives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxvi 6-4 Relay Output Noise Reduction Methods . . . . . . . . . . . . . . . . . . . . . xxxvii

knowledge of electrical systems (an electrical engineer or the equivalent). • Personnel in charge of installing FA systems. • Personnel in charge of designing FA systems. • Personnel in charge of managing FA systems and facilities. 2 General Precautions The user must operate the product according to the performance specifica- tions described in the operation manuals. Before using the product under conditions which are not described in the manual or applying the product to nuclear control systems, railroad systems, aviation systems, vehicles, combustion systems, medical equipment, amuse- ment machines, safety equipment, and other systems, machines, and equip- ment that may have a serious influence on lives and property if used improperly, consult your OMRON representative. Make sure that the ratings and performance characteristics of the product are sufficient for the systems, machines, and equipment, and be sure to provide the systems, machines, and equipment with double safety mechanisms. This manual provides information for programming and operating the Unit. Be sure to read this manual before attempting to use the Unit and keep this man- ual close at hand for reference during operation. !WARNING It is extremely important that a PLC and all PLC Units be used for the speci- fied purpose and under the specified conditions, especially in applications that can directly or indirectly affect human life. You must consult with your OMRON representative before applying a PLC System to the above-mentioned appli- cations. 3 Safety Precautions !WARNING The CPU Unit refreshes I/O even when the program is stopped (i.e., even in PROGRAM mode). Confirm safety thoroughly in advance before changing the status of any part of memory allocated to I/O Units, Special I/O Units, or CPU Bus Units. Any changes to the data allocated to any Unit may result in unex- pected operation of the loads connected to the Unit. Any of the following oper- ation may result in changes to memory status. • Transferring I/O memory data to the CPU Unit from a Programming Device. • Changing present values in memory from a Programming Device. • Force-setting/-resetting bits from a Programming Device. • Transferring I/O memory files from a Memory Card or EM file memory to the CPU Unit. • Transferring I/O memory from a host computer or from another PLC on a network. !WARNING Do not attempt to take any Unit apart while the power is being supplied. Doing so may result in electric shock.

supplied. Doing so may result in electric shock. !WARNING Do not attempt to disassemble, repair, or modify any Units. Any attempt to do so may result in malfunction, fire, or electric shock. !WARNING Do not touch the Power Supply Unit while power is being supplied or immedi- ately after power has been turned OFF. Doing so may result in electric shock. !WARNING Provide safety measures in external circuits (i.e., not in the Programmable Controller), including the following items, to ensure safety in the system if an abnormality occurs due to malfunction of the PLC or another external factor affecting the PLC operation. Not doing so may result in serious accidents. • Emergency stop circuits, interlock circuits, limit circuits, and similar safety measures must be provided in external control circuits. • The PLC will turn OFF all outputs when its self-diagnosis function detects any error or when a severe failure alarm (FALS) instruction is executed. Unexpected operation, however, may still occur for errors in the I/O con- trol section, errors in I/O memory, and other errors that cannot be detected by the self-diagnosis function. As a countermeasure for all such errors, external safety measures must be provided to ensure safety in the system. • The PLC outputs may remain ON or OFF due to deposition or burning of the output relays or destruction of the output transistors. As a counter- measure for such problems, external safety measures must be provided to ensure safety in the system. • When the 24-V DC output (service power supply to the PLC) is over- loaded or short-circuited, the voltage may drop and result in the outputs being turned OFF. As a countermeasure for such problems, external safety measures must be provided to ensure safety in the system. !Caution Confirm safety before transferring data files stored in the file memory (Mem- ory Card or EM file memory) to the I/O area (CIO) of the CPU Unit using a peripheral tool. Otherwise, the devices connected to the output unit may mal- function regardless of the operation mode of the CPU Unit. !Caution Fail-safe measures must be taken by the customer to ensure safety in the event of incorrect, missing, or abnormal signals caused by broken signal lines, momentary power interruptions, or other causes. Serious accidents may result from abnormal operation if proper measures are not provided. !Caution Execute online edit only after confirming that no adverse effects will be caused by extending the cycle time. Otherwise, the input signals may not be readable.

4 !Caution A CS1-H/CJ1-H/CJ1M/CS1D CPU Unit automatically back up the user pro- gram and parameter data to flash memory when these are written to the CPU Unit. I/O memory (including the DM, EM, and HR Areas), however, is not writ- ten to flash memory. The DM, EM, and HR Areas can be held during power interruptions with a battery. If there is a battery error, the contents of these areas may not be accurate after a power interruption. If the contents of the DM, EM, and HR Areas are used to control external outputs, prevent inappro- priate outputs from being made whenever the Battery Error Flag (A40204) is ON. Areas such as the DM, EM, and HR Areas, the contents of which can be held during power interrupts, is backed up by a battery. If a battery error occurs, the contents of the areas that are set to be held may not be accurate even though a memory error will not occur to stop operation. If necessary for the safety of the system, take appropriate measures in the ladder program whenever the Battery Error Flag (A40204) turns ON, such as resetting the data in these areas. !Caution Confirm safety at the destination node before transferring a program to another node or changing contents of the I/O memory area. Doing either of these without confirming safety may result in injury. !Caution Tighten the screws on the terminal block of the AC Power Supply Unit to the torque specified in the operation manual. The loose screws may result in burning or malfunction. !Caution Be careful when connecting personal computers or other peripheral devices to a PLC to which is mounted a non-insulated Unit (CS1W-CLK1@(-V1), CS1W-CLK5@(-V1), or CS1W-ETN01) connected to an external power sup- ply. A short-circuit will be created if the 24 V side of the external power supply is grounded and the 0 V side of the peripheral device is grounded. When con- necting a peripheral device to this type of PLC, either ground the 0 V side of the external power supply or do not ground the external power supply at all. 4 Operating Environment Precautions !Caution Do not operate the control system in the following locations: • Locations subject to direct sunlight. • Locations subject to temperatures or humidity outside the range specified in the specifications. • Locations subject to condensation as the result of severe changes in tem- perature. • Locations subject to corrosive or flammable gases. • Locations subject to dust (especially iron dust) or salts. • Locations subject to exposure to water, oil, or chemicals. • Locations subject to shock or vibration. !Caution Take appropriate and sufficient countermeasures when installing systems in the following locations: • Locations subject to static electricity or other forms of noise. • Locations subject to strong electromagnetic fields. • Locations subject to possible exposure to radioactivity.

!Caution The operating environment of the PLC System can have a large effect on the longevity and reliability of the system. Improper operating environments can lead to malfunction, failure, and other unforeseeable problems with the PLC System. Be sure that the operating environment is within the specified condi- tions at installation and remains within the specified conditions during the life of the system. 5 Application Precautions Observe the following precautions when using the PLC System. • You must use the CX-Programmer (programming software that runs on Windows) if you need to program more than one task. A Programming Console can be used to program only one cyclic task plus interrupt tasks. A Programming Console can, however, be used to edit multitask pro- grams originally created with the CX-Programmer. • There are restrictions in the areas and addresses that can be accessed in I/O memory of the CS-series CPU Units when using the C200H Special I/O Units in combination with the following functions. (Refer to Appendix F Restrictions in Using C200H Special I/O Units for details.) • There are restrictions in data transfer with the CPU Unit when pro- gramming transfers inside an ASCII Unit using the PLC READ, PLC WRITE, and similar commands. • There are restrictions in data transfer with the CPU Unit for allocated bits and DM area specifications (areas and addresses for source and destination specifications). • The DeviceNet output area for a C200HW-DRM21-V1 DeviceNet Mas- ter Unit (CIO 0050 to CIO 0099) overlaps with the I/O bit area (CIO 0000 to CIO 0319). Do not use automatic allocations for I/O in any sys- tem where allocations to the DeviceNet system will overlap with allo- cations to I/O Units. Instead, use a Programming Device or the CX- Programmer to manually allocate I/O for the DeviceNet devices, being sure that the same words and bits are not allocated more than once, and transfer the resulting I/O table to the CPU Unit. If DeviceNet com- munications are attempted when the same bits are allocated to both DeviceNet devices and I/O Units (which can occur even if automatic al- location is used), the DeviceNet devices and I/O Units may both exhibit faulty operation. • Special bits and flags for PLC Link Units (CIO 0247 to CIO 0250) over- lap with the I/O bit area (CIO 0000 to CIO 0319). Do not use automatic allocations for I/O in any system where allocations to the I/O Units will overlap with allocations to I/O Units. Instead, use a Programming De- vice or the CX-Programmer to manually allocate I/O to I/O Units, being sure that the special bits and flags for PLC Link Units are not used, and transfer the resulting I/O table to the CPU Unit. If operation is attempt- ed when the special bits and flags for PLC Link Units are also allocated to I/O Units (which can occur even if automatic allocation is used), the PLC Link Units and I/O Units may both exhibit faulty operation. !WARNING Always heed these precautions. Failure to abide by the following precautions could lead to serious or possibly fatal injury.

connecting to a ground of 100 Ω or less may result in electric shock. • A ground of 100 Ω or less must be installed when shorting the GR and LG terminals on the Power Supply Unit. • Always turn OFF the power supply to the PLC before attempting any of the following. Not turning OFF the power supply may result in malfunction or electric shock. • Mounting or dismounting Power Supply Units, I/O Units, CPU Units, In- ner Boards, or any other Units. • Assembling the Units. • Setting DIP switches or rotary switches. • Connecting cables or wiring the system. • Connecting or disconnecting the connectors. !Caution Failure to abide by the following precautions could lead to faulty operation of the PLC or the system, or could damage the PLC or PLC Units. Always heed these precautions. • When using a CS1 CPU Unit for the first time, install the CS1W-BAT1 Bat- tery provided with the Unit and clear all memory areas from a Program- ming Device before starting to program. (The Battery is installed in advance for CS1-H CPU Units, so initial Battery installation and the mem- ory clear operation are not required.) • When using the internal clock for a CS1 CPU Unit, turn ON power after installing the battery and set the clock from a Programming Device or using the DATE(735) instruction. The clock will not start until the time has been set. Refer to 1-12 Initial Setup for CS1 CPU Units for details. (The Battery is installed in advance for CS1-H CPU Units, so clock does not need to be set.) • The user program and parameter area data in CS1-H CPU Units is backed up in the built-in flash memory. The BKUP indicator will light on the front of the CPU Unit when the backup operation is in progress. Do not turn OFF the power supply to the CPU Unit when the BKUP indicator is lit. The data will not be backed up if power is turned OFF. • If, when using a CS1-H CPU Unit, the PLC Setup is set to specify using the mode set on the Programming Console and a Programming Console is not connected, the CPU Unit will start in RUN mode. This is the default setting in the PLC Setup. (A CS1 CPU Unit will start in PROGRAM mode under the same conditions.) • When creating an AUTOEXEC.IOM file from a Programming Device (a Programming Console or the CX-Programmer) to automatically transfer data at startup, set the first write address to D20000 and be sure that the size of data written does not exceed the size of the DM Area. When the data file is read from the Memory Card at startup, data will be written in the CPU Unit starting at D20000 even if another address was set when the AUTOEXEC.IOM file was created. Also, if the DM Area is exceeded (which is possible when the CX-Programmer is used), the remaining data will be written to the EM Area. Refer to information on file operations in the CS/CJ Series Programming Manual for details. • Always turn ON power to the PLC before turning ON power to the control system. If the PLC power supply is turned ON after the control power sup- ply, temporary errors may result in control system signals because the

ON when power is turned ON to the PLC. • Fail-safe measures must be taken by the customer to ensure safety in the event that outputs from Output Units remain ON as a result of internal cir- cuit failures, which can occur in relays, transistors, and other elements. • Fail-safe measures must be taken by the customer to ensure safety in the event of incorrect, missing, or abnormal signals caused by broken signal lines, momentary power interruptions, or other causes. • Interlock circuits, limit circuits, and similar safety measures in external cir- cuits (i.e., not in the Programmable Controller) must be provided by the customer. • Do not turn OFF the power supply to the PLC when data is being trans- ferred. In particular, do not turn OFF the power supply when reading or writing a Memory Card. Also, do not remove the Memory Card when the BUSY indicator is lit. To remove a Memory Card, first press the memory card power supply switch and then wait for the BUSY indicator to go out before removing the Memory Card. • If the I/O Hold Bit is turned ON, the outputs from the PLC will not be turned OFF and will maintain their previous status when the PLC is switched from RUN or MONITOR mode to PROGRAM mode. Make sure that the external loads will not produce dangerous conditions when this occurs. (When operation stops for a fatal error, including those produced with the FALS(007) instruction, all outputs from Output Unit will be turned OFF and only the internal output status will be maintained.) • The contents of the DM, EM, and HR Areas in the CPU Unit are backed up by a Battery. If the Battery voltage drops, this data may be lost. Provide countermeasures in the program using the Battery Error Flag (A40204) to re-initialize data or take other actions if the Battery voltage drops. • When supplying power at 200 to 240 V AC, always remove the metal jumper from the voltage selector terminals on the Power Supply Unit (except for Power Supply Units with wide-range specifications). The prod- uct will be destroyed and must be replaced if 200 to 240 V AC is supplied while the metal jumper is attached. Refer to 5-3 Wiring for details. • Always use the power supply voltages specified in the operation manuals. An incorrect voltage may result in malfunction or burning. • Do not apply a force greater than 100 N on the terminal block when tight- ening the terminals. • Take appropriate measures to ensure that the specified power with the rated voltage and frequency is supplied. Be particularly careful in places where the power supply is unstable. An incorrect power supply may result in malfunction. • Install external breakers and take other safety measures against short-cir- cuiting in external wiring. Insufficient safety measures against short-cir- cuiting may result in burning. • Install Units as far as possible away from devices that generate strong, high-frequency noise. • Do not apply voltages to the Input Units in excess of the rated input volt- age. Excess voltages may result in burning. • Do not apply voltages or connect loads to the Output Units in excess of the maximum switching capacity. Excess voltage or loads may result in burning.

nal (GR) on the Power Supply Unit before performing withstand voltage tests or insulation resistance tests. Not doing so may result in burning. • Change the applied voltage gradually using the adjuster on the Tester. If full dielectric strength voltage is applied or turned OFF using the switch on the Tester, the generated impulse voltage may damage the Power Supply Unit. • Install the Units properly as specified in the operation manuals. Improper installation of the Units may result in malfunction. • Be sure that all the Backplane mounting screws, terminal block screws, and cable connector screws are tightened to the torque specified in the relevant manuals. Incorrect tightening torque may result in malfunction. • Leave the label attached to the Unit when wiring. Removing the label may result in malfunction if foreign matter enters the Unit. • Remove the label after the completion of wiring to ensure proper heat dis- sipation. Leaving the label attached may result in malfunction. • Use crimp terminals for wiring. Do not connect bare stranded wires directly to terminals. Connection of bare stranded wires may result in burning. • Wire all connections correctly. • Do not drop the product or subject it to excessive vibration or shock. • Double-check all wiring and switch settings before turning ON the power supply. Incorrect wiring may result in burning. • Mount Units only after checking terminal blocks and connectors com- pletely. • Be sure that the terminal blocks, Memory Units, expansion cables, and other items with locking devices are properly locked into place. Improper locking may result in malfunction. • Check switch settings, the contents of the DM Area, and other prepara- tions before starting operation. Starting operation without the proper set- tings or data may result in an unexpected operation. • Check the user program for proper execution before actually running it on the Unit. Not checking the program may result in an unexpected opera- tion. • Confirm that no adverse effect will occur in the system before attempting any of the following. Not doing so may result in an unexpected operation. • Changing the operating mode of the PLC (including the setting of the startup operating mode). • Force-setting/force-resetting any bit in memory. • Changing the present value of any word or any set value in memory. • Resume operation only after transferring to the new CPU Unit the con- tents of the DM Area, HR Area, and other data required for resuming operation. Not doing so may result in an unexpected operation. • Do not pull on the cables or bend the cables beyond their natural limit. Doing either of these may break the cables. • Do not place objects on top of the cables or other wiring lines. Doing so may break the cables. • Do not use commercially available RS-232C personal computer cables. Always use the special cables listed in this manual or make cables according to manual specifications. Using commercially available cables may damage the external devices or CPU Unit.

Unit to any device other than an NT-AL001, CJ1W-CIF11 Link Adapter, or NV3W-M@20L Programmable Terminal. The external device or the CPU Unit may be damaged. • When replacing parts, be sure to confirm that the rating of a new part is correct. Not doing so may result in malfunction or burning. • Before touching a Unit, be sure to first touch a grounded metallic object in order to discharge any static build-up. Not doing so may result in malfunc- tion or damage. • When transporting or storing circuit boards, cover them in antistatic mate- rial to protect them from static electricity and maintain the proper storage temperature. • Do not touch circuit boards or the components mounted to them with your bare hands. There are sharp leads and other parts on the boards that may cause injury if handled improperly. • Do not short the battery terminals or charge, disassemble, heat, or incin- erate the battery. Do not subject the battery to strong shocks. Doing any of these may result in leakage, rupture, heat generation, or ignition of the battery. Dispose of any battery that has been dropped on the floor or oth- erwise subjected to excessive shock. Batteries that have been subjected to shock may leak if they are used. • UL standards required that batteries be replaced only by experienced technicians. Do not allow unqualified persons to replace batteries. • Dispose of the product and batteries according to local ordinances as they apply. Have qualified specialists properly dispose of used batteries as industrial waste. • Unexpected operation may result if inappropriate data link tables or parameters are set. Even if appropriate data link tables and parameters have been set, confirm that the controlled system will not be adversely affected before starting or stopping data links. • CPU Bus Units will be restarted when routing tables are transferred from a Programming Device to the CPU Unit. Restarting these Units is required to read and enable the new routing tables. Confirm that the system will not be adversely affected before allowing the CPU Bus Units to be reset. • When wiring crossovers between terminals, the total current for both ter- minals will flow in the line. Check the current capacities of all wires before wiring crossovers. • The following precautions apply to Power Supply Units with Replacement Notification. • When the LED display on the front of the Power Supply Unit starts to alternately display “0.0” and “A02” or the alarm output automatically turns OFF, replace the Power Supply Unit within 6 months. • Separate the alarm output cables from power lines and high-voltage lines. • Do not apply a voltage or connect a load to the alarm output that ex- ceeds the rated voltage or load. • Maintain an ambient storage temperature of −20 to 30°C and humidity of 25% to 70% when storing the product for longer than 3 months to

6 keep the replacement notification function in optimum working condi- tion. • Always use the standard installation method. A nonstandard installa- tion will decrease heat dissipation, delay the replacement notification signal, and may degrade or damage the internal elements. • Design the system so that the power supply capacity of the Power Supply Unit is not exceeded. • Do not touch the terminals on the Power Supply Unit immediately after turning OFF the power supply. Electric shock may occur due to the resid- ual voltage. 6 Conformance to EC Directives 6-1 Applicable Directives • EMC Directives • Low Voltage Directive 6-2 Concepts EMC Directives OMRON devices that comply with EC Directives also conform to the related EMC standards so that they can be more easily built into other devices or the overall machine. The actual products have been checked for conformity to EMC standards (see the following note). Whether the products conform to the standards in the system used by the customer, however, must be checked by the customer. EMC-related performance of the OMRON devices that comply with EC Direc- tives will vary depending on the configuration, wiring, and other conditions of the equipment or control panel on which the OMRON devices are installed. The customer must, therefore, perform the final check to confirm that devices and the overall machine conform to EMC standards. Note Applicable EMC (Electromagnetic Compatibility) standards are as follows: EMS (Electromagnetic Susceptibility): EN61131-2 or EN61000-6-2 EMI (Electromagnetic Interference): EN61000-6-4 (Radiated emission: 10-m regulations) Low Voltage Directive Always ensure that devices operating at voltages of 50 to 1,000 V AC and 75 to 1,500 V DC meet the required safety standards for the PLC (EN61131-2). 6-3 Conformance to EC Directives The CS-series PLCs comply with EC Directives. To ensure that the machine or device in which the CS-series PLC is used complies with EC Directives, the PLC must be installed as follows: 1,2,3... 1. The CS-series PLC must be installed within a control panel. 2. You must use reinforced insulation or double insulation for the DC power supplies used for the communications power supply and I/O power sup- plies. 3. CS-series PLCs complying with EC Directives also conform to the Com- mon Emission Standard (EN61000-6-4). Radiated emission characteris- tics (10-m regulations) may vary depending on the configuration of the control panel used, other devices connected to the control panel, wiring,

6 and other conditions. You must therefore confirm that the overall machine or equipment complies with EC Directives. 6-4 Relay Output Noise Reduction Methods The CS-series PLCs conforms to the Common Emission Standards (EN61000-6-4) of the EMC Directives. However, noise generated by relay out- put switching may not satisfy these Standards. In such a case, a noise filter must be connected to the load side or other appropriate countermeasures must be provided external to the PLC. Countermeasures taken to satisfy the standards vary depending on the devices on the load side, wiring, configuration of machines, etc. Following are examples of countermeasures for reducing the generated noise. Countermeasures (Refer to EN61000-6-4 for more details.) Countermeasures are not required if the frequency of load switching for the whole system with the PLC included is less than 5 times per minute. Countermeasures are required if the frequency of load switching for the whole system with the PLC included is more than 5 times per minute. Countermeasure Examples When switching an inductive load, connect an surge protector, diodes, etc., in parallel with the load or contact as shown below. Circuit Current Characteristic Required element AC DC Yes Yes If the load is a relay or solenoid, there is a time lag between the moment the circuit is opened and the moment the load is reset. If the supply voltage is 24 or 48 V, insert the surge protector in parallel with the load. If the supply voltage is 100 to 200 V, insert the surge protector between the contacts. The capacitance of the capacitor must be 1 to 0.5 µF per contact current of 1 A and resistance of the resistor must be 0.5 to 1 Ω per contact voltage of 1 V. These values, however, vary with the load and the characteristics of the relay. Decide these values from exper- iments, and take into consideration that the capacitance suppresses spark discharge when the contacts are separated and the resistance lim- its the current that flows into the load when the circuit is closed again. The dielectric strength of the capacitor must be 200 to 300 V. If the circuit is an AC circuit, use a capacitor with no polarity. CR method Power supply Inductive load

6 When switching a load with a high inrush current such as an incandescent lamp, suppress the inrush current as shown below. No Yes The diode connected in parallel with the load changes energy accumulated by the coil into a current, which then flows into the coil so that the current will be con- verted into Joule heat by the resistance of the inductive load. This time lag, between the moment the cir- cuit is opened and the moment the load is reset, caused by this method is longer than that caused by the CR method. The reversed dielectric strength value of the diode must be at least 10 times as large as the circuit voltage value. The forward current of the diode must be the same as or larger than the load current. The reversed dielectric strength value of the diode may be two to three times larger than the supply voltage if the surge protector is applied to electronic circuits with low circuit voltages. Yes Yes The varistor method prevents the imposi- tion of high voltage between the contacts by using the constant voltage characteris- tic of the varistor. There is time lag between the moment the circuit is opened and the moment the load is reset. If the supply voltage is 24 or 48 V, insert the varistor in parallel with the load. If the supply voltage is 100 to 200 V, insert the varistor between the contacts. --- Circuit Current Characteristic Required element AC DC Diode method Power supply Inductive load Varistor method Power supply Inductive load OUT COM R OUT COM R Countermeasure 1 Countermeasure 2 Providing a limiting resistor Providing a dark current of approx. one-third of the rated value through an incandescent lamp

PLCs and other PLCs. 1-1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1-2 CS-series Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1-2-1 Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1-2-2 Versatile Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1-3 CS1-H CPU Unit Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 1-3-1 High-speed Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 1-3-2 High-speed Structured Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 1-3-3 Function Block (FB). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 1-3-4 More Instructions for Specific Applications. . . . . . . . . . . . . . . . . . . . . . . . 15 1-3-5 Battery-free Operation with Flash Memory . . . . . . . . . . . . . . . . . . . . . . . . 16 1-3-6 Better Compatibility with Other SYSMAC PLCs . . . . . . . . . . . . . . . . . . . 16 1-3-7 Refreshing Timer/Counter PVs in Binary . . . . . . . . . . . . . . . . . . . . . . . . . 16 1-3-8 Features of CS1-H CPU Units Ver. 3.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 1-3-9 Changes to CS-series Operating Specifications . . . . . . . . . . . . . . . . . . . . . 17 1-3-10 Features of CS1-H CPU Units Ver. 2.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 1-4 CS1-H CPU Unit Ver. 4.0 Upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 1-4-1 Online Editing of Function Blocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 1-4-2 Input-Output Variables in Function Blocks . . . . . . . . . . . . . . . . . . . . . . . . 22 1-4-3 Text String Support in Function Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 1-5 CS1-H CPU Unit Ver. 3.0 Upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 1-5-1 Function Blocks (FB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 1-5-2 Serial Gateway (Converting FINS to CompoWay/F Via Serial Port). . . . . 25 1-5-3 Comment Memory (in Internal Flash Memory). . . . . . . . . . . . . . . . . . . . . 26 1-5-4 Simple Backup Data Expanded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 1-5-5 Free Running Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 1-5-6 New Special Instructions and Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . 28 1-5-7 Increased Points for SYSMAC BUS Remote I/O Communications . . . . . 28 1-6 CS1-H CPU Unit Ver. 2.0 Upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 1-6-1 Downloading and Uploading Individual Tasks. . . . . . . . . . . . . . . . . . . . . . 30 1-6-2 Improved Read Protection Using Passwords . . . . . . . . . . . . . . . . . . . . . . . 31 1-6-3 Write Protection from FINS Commands Sent to CPU Units via Networks 36 1-6-4 Online Network Connections without I/O Tables. . . . . . . . . . . . . . . . . . . . 41 1-6-5 Communications through a Maximum of 8 Network Levels . . . . . . . . . . . 43 1-6-6 Connecting Online to PLCs via NS-series PTs . . . . . . . . . . . . . . . . . . . . . 46 1-6-7 Setting First Slot Words . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 1-6-8 Automatic Transfers at Power ON without a Parameter File . . . . . . . . . . . 49 1-6-9 Operation Start/End Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 1-6-10 New Application Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 1-7 CS1 and CS1-H CPU Unit Comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 1-7-1 CS1 and CS1-H CPU Unit Comparison. . . . . . . . . . . . . . . . . . . . . . . . . . . 52 1-7-2 New Functions for Version-1 CS1 CPU Units . . . . . . . . . . . . . . . . . . . . . . 56 1-8 CS-series Function Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 1-8-1 Functions Arranged by Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 1-8-2 Communications Functions (Serial/Network) . . . . . . . . . . . . . . . . . . . . . . 62 1-9 CS1-H Functions Arranged by Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 1-10 Comparison of CS-series PLCs and C200HX/HG/HE Operation . . . . . . . . . . . . . . 66 1-11 Checking the Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 1-12 Initial Setup for CS1 CPU Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 1-13 Using the Internal Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

vide improved programming efficiency by dividing the program into tasks. The CS-series PLCs also feature faster processing, higher capacities, multiple ports supporting protocol macros, improved seamless communications across three network levels, and much more, enabling them to flexibly handle advanced information capabilities as core FA controllers. The CS Series includes both CS1 CPU Units and the high-speed CS1-H CPU Units. Note Where differentiation is required, “CS1 CPU Units” or “CS1-H CPU Units” is specified in this manual. “CS1 CPU Units” includes model numbers CS1@- CPU@@-EV1. “CS1-H CPU Units” includes model numbers CS1@-CPU@@H. CS-series PLC CPU Unit Structured Programming The program is divided into tasks. Symbols can be used in programming. The overall performance of the system is improved by executing only the required tasks. Modification and debugging are simplified. The program arrangement can be changed. Step control and block programming instructions can be used. Comments can be added to make the program easier to understand. Improvements in Basic Performance Faster instruction execution and peripheral servicing Larger memory capacity Faster data exchange between Units and I/O memory access Instruction operands can be specified binary or BCD Programs from earlier PLCs are compatible Memory Card Serial Communications Board Serial Communications Unit Protocol Macro Function Serves Multiple Ports Up to 34 ports can be connected (Serial Communications Boards + Serial Communications Units). Different Protocol Macros can be allocated to each port. Programmable Terminal or other device Programming Console Personal computer General- purpose I/O device Remote Programming, Monitoring and Seamless Links between Networks FINS commands allow communications between nodes in different networks. Remote programming and monitoring can be performed. Full Complement of Versatile Functions Memory Card and file processing functions Simplify programs with specialized instructions such as the table data and text string processing instructions Troubleshooting functions Data tracing function Minimum (fixed) cycle time function I/O refreshing method selection PLC Setup functions Use Windows tools to create multiple environments in a single personal computer.

The CS-series PLCs provide higher speed, greater capacity, and more func- tions in a package as compact as the C200H PLCs. Faster Cycle Times Instruction processing times have been reduced to 0.02 µs min. for basic instructions, 0.06 µs min. for special instructions, and 0.8 µs min. for floating- point calculations for CS1-H CPU Units and to 0.04 µs min. for basic instruc- tions, 0.12 µs min. for special instructions, and 10.2 µs min. for floating-point calculations for CS1 CPU Units. The time required for overseeing (overhead), I/O refreshing, and peripheral servicing has also been reduced dramatically. Extra Capacity for High Value-added Programs With capacity for 250,000 program steps, up to 448,000 words of Data Mem- ory, and up to 5,120 I/O points, there is plenty of memory for complex pro- grams, intricate interfaces, communications, and data processing. Binary Operand Settings Increase Setting Ranges In earlier PLCs, most instruction operands had to be specified in BCD (0 to 9,999), but in the CS-series PLCs they can be specified in binary (0 to FFFF hexadecimal or 0 to 65,535 decimal). As an example, the BLOCK TRANSFER instruction can now transfer data from up to 65,535 words rather than 9,999 words. Also the maximum DM address that can be indirectly addressed is now D32767 rather than the maximum DM address of D09999 in C200HX/HG/HE PLCs. Program Compatibility Programs from earlier OMRON PLCs (such as the C200H, C200HS, C200HX/HG/HE, and CV Series) can be imported into the CS-series PLCs. CS-series and C200H Units Supported High-density CS-series Units, such as the 96-point I/O Units and 8-point Ana- log I/O Units (4 inputs and 4 outputs) can be used together with the wide vari- ety of C200H Units (about 90 models) can be used in a CS-series PLC. CS-series Long-distance Expansion Racks I/O Control Units and I/O Interface Units can be used to create systems con- taining CS-series Long-distance Expansion Racks. Up to two series of Long- distance Expansion Racks can be connected, each measuring up to 50 m, for a total coverage of 100 m. CS-series Long-distance Expansion Racks can be used to create high-speed, low-cost distribution systems without using Com- munications Units. Structured Programming Division of the Program into Tasks When the program is divided into tasks that handle separate functions, control systems, or processes, several programmers can develop these separate tasks simultaneously. There can be up to 32 normal (cyclic) tasks and 256 interrupt tasks. There are four types of interrupts: the Power OFF Interrupt, Scheduled Interrupts, I/O Interrupts, and External Interrupts (interrupts from Special I/O Units or CPU Bus Units).

as tasks to create an entire program. Using Symbols Arbitrary symbols (names up to 32 characters) that are independent of I/O ter- minal allocations can be used in programming. Standard programs created with symbols are more general and easier to reuse as tasks in different pro- grams. Global and Local Symbols Supported I/O names are handled as symbols which can be defined as global symbols, which apply to all of the programs in all tasks, or as local symbols, which apply to just the local task. When the symbols are defined, you can choose to have the local symbols allocated to addresses automatically. Improve Overall System Response Performance The response performance of the system can be improved by dividing the program into a system-management task and tasks used for control and exe- cuting only those control tasks that need to be executed. Simplify Program Modification • Debugging is more efficient when the job of modifying and debugging the tasks can be divided among several individuals. • Program maintenance is easier because only the tasks affected by changes have to be modified when there are changes (such as changes in specifications). • Several consecutive program lines can be modified with online editing. • The amount the cycle time is extended during online editing has been reduced. Earlier program Task Task Task Task Standard programs Program ABC Program ABD Task 1 (A) Task 2 (B) Task 3 (C) Task 1 (A) Task 2 (B) Task 3 (D) Symbols specified for bit address: SW1 VALVE

the task control instructions can be used to switch the program quickly from production of one model to another. Step Control and Block Programming The step control and block programming instructions can be used to control repetitive processes that are difficult to program with ladder programming alone. Comments Several types of comments can be added to the program to make it easier to understand, including Rung comments, and I/O comments. Section Function The section function can be used to make the program easier to visualize (CX-Programmer version 2.0 or higher). Port-specific Protocol Macro Function Create Protocol Functions for All Ports The protocol macro function can be used to create versatile communications functions for any of the PLC’s communications ports. The communications functions can have host link, NT Link, or protocol macro configurations and can be directed to RS-232C and RS-422/485 ports on any of the Units. 1,2,3... 1. One Serial Communications Board can be mounted in the CPU Unit. (A Serial Communications Board has two serial communications ports.) 2. Up to 16 Serial Communications Units can be connected to a CPU Unit. (Each Serial Communications Unit has two serial communications ports.) In total, up to 36 ports can be used. Standard Serial Communications with External Devices Messages can be transferred to and from standard serial devices with the pro- tocol macro function (according to preset parameter settings). The protocol macro function supports processing options such as retries, timeout monitor- ing, and error checks. Symbols that read and write data to the CPU Unit can be included in the com- munications frames, so data can be exchanged with the CPU Unit very easily. OMRON components (such as Temperature Controllers, ID System Devices, Bar Code Readers, and Modems) can be connected to a Serial Communica- tions Board or Serial Communications Unit with the standard system protocol. It is also possible to change the settings if necessary. Note The Serial Communications Board or Serial Communications Unit must be purchased separately to take advantage of this function. PT Programming Device Host Computer Serial Communications Unit CPU Unit Serial Commu- nications Board Up to 36 ports are possible External device with serial port

Different network levels can be connected as shown in the following diagram. The multilevel configuration provides more flexibility in networking from the manufacturing site to production management. In particular, the DeviceNet network makes it very easy to connect devices from other manufacturers. OA Network: Ethernet FA Network: Controller Link DeviceNet*: DeviceNet High-speed ON/OFF bus: CompoBus/S Note *Units that conform to JEMANET standards are also available. Transmit or receive data with just one instruction. External device Ethernet Controller Link CompoBus/S DeviceNet

1,2,3... 1. The host link function can operate through a modem, which allows moni- toring of a distant PLC’s operation, data transfers, or even online editing of a distant PLC’s program by phone. 2. PLCs in a network can be programmed and monitored through the Host Link. 3. It is possible to communicate through 3 network levels even with different types of networks. Communications Across 3 Network Levels Remote programming/monitoring of a PLC on a network up to 3 levels away (including the local network) for the same or different types of networks is pos- sible through Host Link. Note With CS/CJ-series CPU Units Ver. 2.0 or later, remote programming/monitor- ing is possible up to 8 levels away. Refer to 1-6-2 Improved Read Protection Using Passwords for details. Message transfer between PLCs on a network 3 levels away (including the local network) for the same or different types of networks. Remote programming/monitoring of a distant PLC Remote programming/monitoring of a PLC on the network through Host Link Controller Link Network Modem Modem Network 3 Network 2 Network 1 Network 1 Network 3 Network 2

NT Link communications between an NS-series or NT31/NT631-V2 PT and a CS-series PLC are possible at high speed (except for pre-version 1 CS1 CPU Units). 1-2-2 Versatile Functions Memory Card and File Management Functions Transfer Data to and from Memory Cards Data area data, program data, and PLC Setup data can be saved as files on a Memory Card (compact flash memory). Data can be read and written from Programming Devices, instructions in the user program, or host computers. (From the program, only I/O memory can be read and written and it must be read or written as a file.) Convert EM Area Banks to File Memory Part of the EM Area can be converted to file memory to provide file manage- ment capabilities without a Memory Card and with much faster access time than a Memory Card. (I/O comments can also be stored.) Automatic File Transfer at Start-up The PLC can be set up to transfer the program and/or PLC Setup files from the Memory Card when the PLC is turned ON. With this function, the Memory Card provides a flash-ROM transfer. This function can also be used to store and change PLC configurations quickly and easily. I/O Memory Files in CSV and Text Format It is now possible to save production results and other data (hexadecimal) from the CPU Unit I/O memory in a Memory Card in CSV or text format. The data can then be read and edited using personal computer spreadsheet soft- ware by means of a Memory Card Adapter. This function is not supported by pre-version-1 CS1 CPU Units. File Operations (Deleting, Creating Directories, etc.) from Ladder Programs It is possible to format files, delete, copy, change file names, create new direc- tories, and perform similar operations on a Memory Card from the ladder pro- gram during PLC operation. This function is not supported by pre-version-1 CS1 CPU Units. Program Replacement During Operation It is now possible to replace the entire user program in the CPU Unit from the Memory Card during operation. In this way, it is possible to switch PLC opera- tion without stopping the PLC. This function is not supported by pre-version-1 CS1 CPU Units. I/O Memory, program, and parameter areas stored as files. I/O memory data stored in CSV or text format Via Memory Card Adapter Spreadsheet software Memory Card PLC operation .OBJ Replacement

memory) to the Memory Card by pressing the Memory Card power supply switch. In this way, if a malfunction arises, it is possible to back up all data in the CPU Unit at the time without using a Programming Device. This function is not supported by pre-version-1 CS1 CPU Units. Specialized Instructions Simplify Programming Text String Instructions The text string instructions allow text processing to be performed easily from the ladder program. These instructions simplify the processing required when creating messages for transmission or processing messages received from external devices with the protocol macro function. Loop Instructions The FOR(512), NEXT(513), and BREAK(514) instructions provide a very powerful programming tool that takes up little program capacity. Index Registers Sixteen Index Registers are provided for use as pointers in instructions. An Index Register can be used to indirectly address any word in I/O memory. The CS-series PLCs also support the auto-increment, auto-decrement, and offset functions. The Index Registers can be a powerful tool for repetitive processing (loops) when combined with the auto-increment, auto-decrement, and offset func- tions. Index Registers can also be useful for table processing operations such as changing the order of characters in text strings. Table Data Processing Instructions Stack Instructions A region of I/O memory can be defined as a stack region. Words in the stack are specified by a stack pointer for easy FIFO (first-in first-out) or LIFO (last-in first-out) data processing. Table Processing Range Instructions These instructions operate on a specified range of words to find the maximum value or minimum value, search for a particular value, calculate the sum or FCS, or swap the contents of the leftmost and rightmost bytes in the words. Processing of text string data External device with standard serial port Stack region Pointer Range specified in the instruction Data Search, find maximum, find minimum, etc.

table must be defined in advance with DIM(631), which declares the number of words in a record and the number of records in the table. Up to 16 record tables can be defined. Record tables are useful when data is organized in records. As an example, if temperatures, pressures, or other set values for various models have been combined into a table, the record-table format makes it easy to store and read the set values for each model. The SETR(635) can be used to store the first address of the desired record in an Index Register. Index Registers can then be used to simplify complicated processes such as changing the order of records in the record table, search- ing for data, or comparing data. Troubleshooting Functions Failure Diagnosis: FAL(006) and FALS(007) The FAL(006) and FALS(007) can be used to generate a non-fatal or fatal error when the user-defined conditions are met. Records of these errors are stored in the error log just like system-generated errors. Failure Point Detection: FPD(269) Diagnoses a failure in an instruction block by monitoring the time between execution of FPD(269) and execution of a diagnostic output and finding which input is preventing an output from being turned ON. Error Log Functions The error log contains the error code and time of occurrence for the most recent 20 errors (user-defined or system-generated errors). Maintenance Functions The CS-series PLCs record information useful for maintenance, such as the number of power interruptions and the total PLC ON time. Table Record 2 Record 3 Record 2 Set values for model A Temperature setting Time setting Pressure setting User-defined error condition FAL(006) or FALS(007) error Input preventing diagnostic output from going ON FPD

The content of the specified word or bit in I/O memory can be stored in trace memory by one of the following methods: scheduled sampling, cyclic sam- pling, or sampling at execution of TRSM(045). Fixed Cycle Time Function A fixed (minimum) cycle time can be set to minimize variations in I/O response times. I/O Refreshing Methods I/O refreshing can be performed cyclically and immediately by programming the immediate-refreshing variation of the instruction. PLC Setup Functions PLC operation can be customized with PLC Setup settings, such as the maxi- mum cycle time setting (watch cycle time) and the instruction error operation setting, which determines whether instruction processing errors and access errors are treated as non-fatal or fatal errors. Binary Refreshing of Timer/Counter Instruction PVs Present values of timer/counter instructions can now be refreshed in binary, in addition to the existing BCD capability. (Binary refreshing, however, can be specified with only CX-Programmer Ver. 3.0 and higher.) This allows the timer/counter setting time to be expanded to a range of 0 to 65535 (from the existing 0 to 9,999). Also, results calculated by other instructions can be used as is for timer/counter set values. Trace memory Specified address in I/O memory The PLC's initial settings can be customized with the PLC Setup.

monitor other CPU Bus Units on the same bus (CPU Rack or Expansion racks) or other CPU Units on the same network from a serial port on the CPU Unit or a Serial Communications Board. Power Supply Units with Replacement Notification The C200HW-PA204C Power Supply Units with Replacement Notification pro- vide six display levels using a 7-segment display on the front panel of the Unit to indicate the remaining service life of the Power Supply Unit. An alarm out- put also notifies when the estimated remaining service life drops to 6 months or shorter. This function enables Power Supply Unit replacement before the power supply reaches the end of its service life resulting in a system failure. Controller Link Several CPU Bus Units on the same bus or other CPU Units on the same network can be accessed from a single port. CX-Programmer POWER PA204C POWER Years C200HW-PA204C TEST C200HW-PA204C Power Supply Unit with Replacement Notification Alarm output turns OFF when remaining service life is 6 months.

Section 1-3 1-3 CS1-H CPU Unit Features 1-3-1 High-speed Performance Ultra High-speed Cycle Time The CS1-H CPU Units provide a cycle time that is three to four times faster than that of the CS1 CPU Units. For example, a program consisting of 38 Ksteps of only basic instructions with 128 inputs and 128 outputs executes in 1 ms (4.2 ms for the CS1 CPU Units); a program consisting of 20 Ksteps of basic and special instructions in a 1:1 ratio with 128 inputs and 128 outputs executes in 1 ms (2.0 ms for the CS1 CPU Units); and a program consisting of 8 Ksteps of basic and special instructions in a 1:2 ratio with 64 inputs and 64 outputs executes in 0.5 ms (1.0 ms for the CS1 CPU Units). The following factors give the CS1-H CPU Units their high speed. 1,2,3... 1. Instruction execution times: Only about 1/2 the time required for basic in- structions, and only about 1/3 the time required for special instructions. 2. Better bus performance: Data transfers between the CPU Unit and Special I/O or Communications Units is about twice as fast, providing greater over- all system performance. 3. Instruction execution is performed in parallel with peripheral servicing. 4. Other factors, including background execution of text string processing and table data processing instructions. Faster Execution of Common Instructions Extensive research on applications of CS1 CPU Units was used to identify the 20 most commonly used instructions of the more than 400 supported instruc- tions (see below), and execution speed for these instructions was increased by 10 to 20 times previous performance. CPS (SIGNED BINARY COMPARE) JMP (JUMP) CPSL (DOUBLE SIGNED BINARY COMPARE) CJP (CONDITIONAL JUMP) XFER (BLOCK TRANSFER) BCNT (BIT COUNTER) MOVB (MOVE BIT) MLPX (DATA DECODER) MOVD (MOVE DIGITS) BCD (BINARY-TO-BCD) BSET (BLOCK SET) SBS/RET (SUBROUTINE CALL/RETURN) Transfer Speed between CPU Unit and CPU Bus Units Doubled The speed of transferring data between the CPU Unit and CPU Bus Units has been doubled to increase overall system performance. Parallel Processing of Instructions and Peripheral Servicing A special mode is supported that enables parallel processing of instruction execution and peripheral device servicing to support the following types of application. • Extensive data exchange with a host not restricted by the program capac- ity in the CS1-H CPU Unit • Consistently timed data exchange with SCADA software • Eliminating the effects on cycle time of future system expansion or increases in communications

Section 1-3 Less Cycle Time Fluctuation for Data Processing Table data processing and text string processing, which often require time, can be separated over several cycles to minimize fluctuations in the cycle time and achieve stable I/O response. Better Data Link and Remote I/O Refreshing CPU Bus Unit refresh response has been increased both by reductions in the cycle time itself and by the addition of an immediate I/O refresh instruction for CPU Bus Units (DLNK(226)). This instruction will refresh data links, DeviceNet remote I/O, protocol macros, and other special data for CPU Bus Units. The response of a CS1-H CPU Unit is approximately 2.4 times that of a CS1 CPU Unit. And, for a cycle time of approximately 100 ms or higher, the increase in the data link response is comparable to that for the cycle time. Immediate Refreshing for CPU Bus Units Although previously, I/O refreshing for CPU Bus Units was possible only after program executions, a CPU BUS I/O REFRESH instruction (DLNK(226)) has been added to enable immediate I/O refreshing for CPU Bus Units. Data links, DeviceNet remote I/O, an other unique CPU Bus Unit refreshing can be refreshed along with words allocated to the CPU Bus Unit in the CIO and DM Areas whenever DLNK(226) is executed. This is particularly effective for longer cycle times (e.g., 100 ms or longer). (Data exchange for data links, DeviceNet remote I/O, and other network communications are also affected by the communications cycle time, i.e., DLNK(226) refreshes data only between the CPU Bus Units and the CPU Unit, not the data on the individual networks.) 1-3-2 High-speed Structured Programming To further aid standardized programming, program structuring functions have been improved, as has program execution speed. More Cyclic Tasks Tasks provide better efficiency by enabling programs to be separated by func- tion or for development by different engineers. The CS1-H CPU Units support up to 288 cyclic tasks, an incredible increase over the previous maximum of 32 tasks. Common Processing from Multiple Tasks Global subroutines that can be called by any task are now supported. These can be used for common processing from more than one task, for greater standardization. Faster Subroutine Instructions Subroutine instruction are executed approximately 70 times faster to enable greater program modularization without having to be concerned about increasing the cycle time. Shared Index and Data Registers between Tasks Although separate index and data registers can still be used in each task, they have been joined by shared index and data registers that can be used between tasks to reduce the time required to switch between tasks. 1-3-3 Function Block (FB) When using a CPU Unit with unit version 3.0 or later, standard processes can be encapsulated as easily reusable function blocks as long as those pro- cesses only exchange I/O data externally. The function blocks can be written in ladder language or ST (structured text) language. Mathematical processing that is difficult to write in ladder language can be written easily in the ST lan- guage. OMRON function blocks can be written in ladder language or ST (structured text) language, and conform to IEC 61131-3 standards (JIS B3503). The func- tion blocks provide functions for more efficient design and debugging of the user equipment, as well as easier maintenance.

Section 1-3 Smart FB Library The Smart FB Library is a set of function blocks that improve interoperability between OMRON PLC Units and FA components. Since it isn't necessary to create a ladder program to use basic Unit and FA component functions, the user can concentrate on more important work, such as determining how to make the most of device functions. Online Editing of FB Definitions FB definitions can be changed during operation, so FB definitions can be edited quickly during debugging. In addition, FBs can be used with confidence even in equipment that must operate 24 hours/day. (Requires CPU Unit unit version 4.0 or later and CX-Programmer version 7.0 or higher.) Nesting Not only can programs be created with nested OMRON FBs, it is possible to make easy-to-understand, stress-free operations by switching displays under preset conditions and displaying structures in a directory-tree format. (Requires CX-Programmer version 6.0 or higher.) Protecting FB Definitions It is possible to prevent unauthorized manipulation, editing, or misappropria- tion of the program by setting passwords for the function block definitions allo- cated in the project file and protecting the definitions based on their purpose. (Requires CX-Programmer version 6.1 or higher.) Offline Debugging with the Simulator The Simulator enables checking the PLC program's operation on the desktop, so program quality can be improved and verified early on. Both the ladder and ST programming can be executed in the computer application. Variable Support for String Operations (CPU Units with Unit Version 4.0 or Later) The functions that perform string data operations in ST language not only support string variables, they also strengthen the functions used to communi- cate with string data I/O. This feature simplifies the creation of programs that send and receive communications commands. (Requires CPU Unit unit ver- sion 4.0 or later and CX-Programmer version 7.0 or higher.) FB Generation Function Existing PLC programming can be reused by easily converting it to FBs. (Requires CX-Programmer version 7.0 or higher.) 1-3-4 More Instructions for Specific Applications Very specific control can be easily programmed for a much wider range of applications with the many new special instructions added to the CS1-H CPU Units. High-speed Positioning for XY Tables Double-precision floating-point calculations are supported for the CS1-H CPU Units to provide even better precision for position control operations. Convert between Floating Point and Text String Data To display floating-point data on PTs, the CS1-H CPU Units provide conver- sion instructions from floating-point data to text strings (ASCII). Conversion between ASCII and floating-point data is also possible so that ASCII data from serial communications with measurement devices can be used in calcula- tions. Accurate Line Approximations Unsigned 16-bit binary/BCD data, signed 16/32-bit binary data, or single-pre- cision floating-point data can be used for line data, enabling precise (high data resolution) conversions, such as from a level meter (mm) to tank capacity (l) based on the shape of the tank. Realtime Workpiece Data Management When loading and unloading workpieces from conveyor lines, stack instruc- tions can be used to manage workpiece information in realtime in table for- mat.

Section 1-3 PID Autotuning Autotuning is now supported for PID constants with the PID CONTROL instruction. The limit cycle method is used to ensure rapid autotuning. Very effective for multiloop PID control. System Debugging through Error Simulation A specified error status can be created with the FAL/FALS instructions. This can be used effectively when depending systems. For example, errors can be simulated to produce corresponding displays on a PT to confirm that the cor- rect messages are being displayed. Program Simplification with More Specific Basic Instructions Programs that use a high quantity of basic instructions can be simplified though the use of differentiated forms of the LD NOT, AND NOT and OR NOT instructions, and through the use of OUT, SET, and RSET instructions that can manipulate individual bits in the DM or EM Area. Delayed Power OFF Processing for Specified Program Areas The DI and EI instructions can be used to disable interrupts during specific portions of the program, for example, to prevent the power OFF interrupt from being executed until a specific instruction has been executed. 1-3-5 Battery-free Operation with Flash Memory Any user program or parameter area data transferred to the CPU Unit is auto- matically backed up in flash memory in the CPU Unit to enable battery-free operation without using a Memory Card. Note Refer to information on flash memory in the CS/CJ Series Programming Man- ual (W394) for precautions on this function. 1-3-6 Better Compatibility with Other SYSMAC PLCs C200HE/HG/HX PLCs The AREA RANGE COMPARE (ZCP) and DOUBLE AREA RANGE COM- PARE (ZCPl) instructions are supported in the CS1-H CPU Units to provide better compatibility with the C200HE/HG/HX PLCs. CVM1/CV-series PLCs The CONVERT ADDRESS FROM CV instruction allows real I/O memory addresses for the CVM1/CV-series PLCs to be converted to addresses for the CS-series PLCs, enabling programs with CVM1/CV-series addresses to be quickly converted for use with a CS-series CPU Unit. 1-3-7 Refreshing Timer/Counter PVs in Binary In addition to BCD, binary can also be set as the PV refresh method for timer/counter instructions. (This setting is possible, however, only with version 3.0 or higher versions of the CX-Programmer.) This means that the settable time range for timer/counter instructions is increased from 0 to 9999 to 0 to 65,535. It also means that the results of calculations made with other instruc- tions can be used without conversion. 1-3-8 Features of CS1-H CPU Units Ver. 3.0 Encapsulate Programming into Function Blocks Using Ladder Programming or Structured Text When using CX-Programmer Ver. 5.0 or higher, function blocks can be used to encapsulate standard processing that is often reused and for which only I/O data is output externally as the user interface. Function blocks can be written using ladder programming or structured text. Structured text is particularly effective for easily including arithmetic processing that is difficult to write in ladder programming.

Section 1-3 Incorporate CompoWay/F-compatible OMRON Components into FINS Network Via Serial Gateway Using the Serial Gateway mode for the CPU Unit’s serial port enables flexible access to CompoWay/F-compatible OMRON components from devices on the network (e.g., PTs, PLC CPU Units, personal computers) Store Comment/Section Data in CPU Unit’s Flash Memory The CX-Programmer can be used to save I/O comments and other com- ment/section data in the comment memory contained in the CPU Unit’s flash memory. Back Up Comment and Section Data Comment/section data in comment memory can be backed up using the sim- ple backup function. Use No-protocol Communications at Multiple Ports No-protocol communications can be performed via the serial ports of Serial Communications Boards/Units with unit version 1.2 or later. This enables no- protocol communications at multiple ports. Free Running Timer Calculates Intervals without Requiring Timer Instructions The system timers used after the power is turned ON are contained in Auxil- iary Area words A000 and A001. A000 is set to 0000 hex when the power is turned ON and this value is auto- matically incremented by 1 every 10 ms. The value returns to 0000 hex after reaching FFFF hex (655,350 ms), and then continues to be incremented in a ring operation. A001 is set to 0000 hex when the power is turned ON and automatically incre- mented by 1 every 100 ms. The value returns to 0000 hex after reaching FFFF hex (655,350 ms), and then continues to be incremented in a ring oper- ation. Example:The interval can be counted between processing A and processing B without requiring timer instructions. This is achieved by calculating the difference between the value in A000 for processing A and the value in A000 for processing B. The interval is counted in 10 ms units. With unit version 4.0 or later, the free running time is stored in A002 in 1-s increments. Reuse Ladder Programs Created Using C-series CPU Units C-series ladder programs can be easily reused through the newly supported model conversion instructions (XFERC(565), DISTC(566), COLLC(567), MOVBC(568), and BCNTC(621)). 1-3-9 Changes to CS-series Operating Specifications Increased Points for SYSMAC BUS Remote I/O Communications The maximum number of points for SYSMAC BUS remote I/O communica- tions in the operating specifications has been expanded from 800 points (50 words) to 1,280 points (80 words). This change applies to all CS-series CPU Units and Units using SYSMAC BUS remote I/O communications, including previously manufactured Units. For details, refer to 1-5-7 Increased Points for SYSMAC BUS Remote I/O Communications.

Section 1-3 1-3-10 Features of CS1-H CPU Units Ver. 2.0 Easier System Development by Teams Download/Upload Tasks Individually with CX-Programmer Version 4.0 or Higher The CX-Programmer (version 4.0 or higher) can be used to upload or down- load only the required tasks. This enables the member of a development team to work separately and then upload/download tasks after debugging them, helping to eliminate the need for unification work by a manager as well as mis- takes that can easily occur in such work. Many Protection Functions Improved Read Protection Using Passwords with CX-Programmer Version 4.0 or Higher ■ Read Protection for Specific Tasks Passwords can be set to read-protect individual groups of tasks. This enables creating black boxes in the program. ■ Enabling/Disabling Creating File Memory Program Files When read protection is set, an optional setting allows you to enable or dis- able creating program backup files (.OBJ). This setting can be used to prevent programs from being disclosed. ■ Program Write Protection The user program can be protected without using the DIP switch setting. This helps prohibit unauthorized or accidental program changes. Protection for CPU Units from FINS Write Commands Sent via Networks Write operations to a CPU Unit using FINS commands across networks can be enabled for specific nodes and disabled for all other nodes. This can be used to enable monitoring data via networks while eliminating the possibility of accidental mistakes caused by careless writing operations. Easier Network Connections and More-advanced Seamless Network Communications Online Connections via Networks without I/O Tables By using the CS1W-ETN21 Ethernet Unit, online connection is possible to any PLC in the local network from a Programming Device, such as the CX-Pro- grammer, as soon as the network is connected by using automatic I/O alloca- tion at startup. It’s not necessary to create the I/O tables to enable connection. This eliminates the need to use a serial connection to create I/O tables before the CX-Programmer can be connected via Ethernet. Only an Ethernet con- nection is required to go online and create I/O tables. Work Across Up to Eight Networks with CX-Net in CX-Programmer Version 4.0 or Higher FINS commands can be sent across up to 8 network levels (including the local network). This enables a wider range of communications between devices on Ethernet and Controller Link Networks. FINS commands can only be sent across up to 8 network levels when the destination is a CPU Unit. FINS commands can be sent to other destinations up to 3 network levels away. Online Connections to PLCs via NS-series PTs Downloading, uploading, and monitoring of ladder programs or other data is possible to a PLC connected serially to an NS-series PT from the CX-Pro- grammer connected to the NS-series PT by Ethernet.

Section 1-3 Easier Implementation of Explicit Messages with Explicit Message Instructions Special Explicit Message Instructions are now supported to simplify using explicit messages. (Previously, CMND(490) had to be used to send a FINS command of 2801 hex to enable sending explicit messages.) The new instruc- tions include the following: EXPLICIT MESSAGE SEND (EXPLT(720)), EXPLICIT GET ATTRIBUTE (EGATR(721)), EXPLICIT SET ATTRIBUTE (ESATR(722)), EXPLICIT WORD READ (ECHRD(723)), and EXPLICIT WORD WRITE (ECHWR(724)). Of these, EXPLICIT WORD READ (ECHRD(723)) and EXPLICIT WORD WRITE (ECHWR(724)) enable easily reading and writing data in CPU Units on networks with the same type of notation as used for SEND(290) and RECV(298). (Not supported by the C200HX(-Z)/HG(-Z)/HE(-Z) and CV-series PLCs.) Greater Flexibility in I/O Allocations First Word Address Settings for Slots (Using CX-Programmer Version 3.1 or Higher) When editing I/O tables for CS1-H CPU Units, the first word address can be set for up to 64 slots. This can be used, for example, to create fixed starting addresses for Input Units and Output Unit to separate I/O allocations from the program and increase the efficiency of program maintenance. Automatic Power-ON Transfers without a Parameter File (.STD) The user program can be automatically transferred to the CPU Unit at power ON without a parameter file (.STD) if the name of the program file (.OBJ) is changed to REPLACE on the CX-Programmer and the file is stored on a Memory Card. This can be used, for example, to enable transferring a pro- gram to a CPU Unit by creating the program offline and sending it as an email attachment, without a local Programming Device. More Application Instruction with CX-Programmer Version 4.0 or Higher Multiple Interlock Instructions (MILH(517), MILR(518), and MILC(519)) for Nested Interlocks These instruction enable easy creation of nested interlocks. For example, cre- ate one interlock to control the entire program (e.g., for an emergency stop) and then nest other interlocks for separate portions of the program (e.g., con- veyor operation, alarms, etc.). TIME-PROPORTIONAL OUTPUT (TPO(685)) Instruction for Time-proportional Operation with Temperature Controllers or Variable-duty Lighting/Power Control This instruction is used in combination with PID instructions to create a time- proportional output based on the manipulated variable output by the PID instruction. This enables easily connecting an SSR to a Transistor Output Unit to achieve time-proportional operation of a Temperature Controller. Variable- duty pulse outputs can also be created for lighting or power control. Symbol Time Comparison Instructions for Easy Calendar Timers Two times/dates can be compared to continue operation to the next instruction in the ladder program rung when the results of comparison is true. Opposed to normal comparison instructions, comparisons are by byte and the bytes that are compared in the time/date data can be controlled. This enables com- paring built-in clock data with set times/dates to easily create a calendar timer, for example, on the hour (when the minutes is 0) or on a specific date each year).

Section 1-3 GRAY CODE CONVERSION (GRY(474)) for Easy Conversion of Parallel Inputs from Absolute Encoders to Binary, BCD, or Angle Data This instruction converts Gray binary codes to binary, BCD, or angle data. This enables easily handling position or angle data input as parallel signals (2n) from an Absolute Encoder with a Gray code output using a DC Input Unit. EXPANDED BLOCK COMPARE (BCMP2(502)) for Comparison Judgements for Up to 256 Ranges (Upper/Lower Limits) with One Instruction This instruction determines if a value is within any of up to 256 ranges defined by upper and lower limits. When used with the GRAY CODE CONVERSION (GRY(474)) instruction, the same operation as a cam switch can be achieved by determining if an angle input from an Absolute Encoder is in a comparison table. Easier Processing of I/O Devices with Special I/O Instructions Previously many instructions were required to read or write data for external input devices such as digital switches and 7-segment displays connected to Basic I/O Units. Now, I/O processing for these devices can be achieved with a single instruction. These are sometimes call Combination Instructions. These instructions are the same as those supported by the C200HX/HG/HE and CQM1H PLCs, with the exception that more than one of each of these instructions can be executed in a single user program. TEN KEY INPUT (TKY(211)) Sequentially reads numbers input from a ten-key connected to an Input Unit. HEXADECIMAL KEY INPUT (HKY(212)) Sequentially reads numbers input from a hexadecimal keypad connected to an Input Unit and an Output Unit for a maximum of 8 digits. DIGITAL SWITCH INPUT (DSW(213)) Reads numbers input from a digital switch or thumbwheel switch connected to an Input Unit and an Output Unit. Either 4 or 8 digits are read. MATRIX INPUT (MTR(210)) Sequentially reads 64 input points input from a 8 × 8 matrix connected to an Input Unit and an Output Unit. 7-SEGMENT DISPLAY OUTPUT (7SEG(214)) Converts 4-digit or 8-digit values to data for a 7-segment display and outputs the result. Read/Write CPU Bus Unit Memory Areas with IORD(222)/IOWR(223) Although INTELLIGENT I/O READ (IORD(222)) and INTELLIGENT I/O WRITE (IOWR(223)) could previously be used only for Special I/O Units, these instructions can now be used to read and write data for CPU Bus Units. Operation Start/End Times The times that operation is started and ended are automatically stored in memory in the Auxiliary Area (A515 to A517). This enables easier manage- ment of the operating times of the PLC System.

Section 1-3 Power Supply Units with Replacement Notification The C200HW-PA204C Power Supply Units with Replacement Notification pro- vide six display levels using a 7-segment display on the front panel of the Unit to indicate the remaining service life of the Power Supply Unit. An alarm out- put also notifies when the estimated remaining service life drops to 6 months or shorter. This function enables Power Supply Unit replacement before the power supply reaches the end of its service life resulting in a system failure. POWER PA204C POWER Years C200HW-PA204C TEST C200HW-PA204C Power Supply Unit with Replacement Notification Alarm output turns OFF when remaining service life is 6 months.

Section 1-4 1-4 CS1-H CPU Unit Ver. 4.0 Upgrades This section summarizes the upgrades made for CS1-H CPU Units with unit version 4.0. CX-Programmer version 7.0 or higher must be used to enable using the following functions. Functional Upgrades for Unit Version 4.0 1-4-1 Online Editing of Function Blocks Unit Version 3.0 or Earlier Function block definitions could not be changed during operation. Unit Version 4.0 or Later Function block definitions can be changed during operation. This allows func- tion block definitions to be quickly corrected during debugging. It also allows function blocks to be used more easily in systems that operate 24 hours a day. 1-4-2 Input-Output Variables in Function Blocks Unit Version 3.0 or Earlier The data size of parameters that could be passed to and from function blocks was limited to four words maximum. It was thus necessary to separate ele- ments with large data sizes, such as data tables. Unit Version 4.0 or Later Input-output variables can be used to passed large quantities of data, such as table data. 1-4-3 Text String Support in Function Blocks Unit Version 3.0 or Earlier To program text string processing for communications commands and display data in ladder diagrams, it was necessary to know the ladder string instruc- tions and ASCII codes. Also, several instructions had to be combined to con- verted from numbers to text strings or text strings to numbers. Function Section Online Editing of Function Blocks 1-4-1 Online Editing of Function Blocks Input-Output Variables in Function Blocks 1-4-2 Input-Output Variables in Function Blocks Text String Support in Function Blocks 1-4-3 Text String Support in Function Blocks Pattern A Pattern B Pattern C Pattern D Pattern E D100 D101 D102 D103 D104 D100 D101 D102 D103 D104 FB (INT) (INT) Para1i Para1o (INT) (INT) Para2i Para2o (INT) (INT) Para3i Para3o (INT) (INT) Para4i Para4o (INT) (INT) Para5i Para5o D100 D101 D102 D103 D104 Pattern A Pattern B Pattern C Pattern D Pattern E D100 D101 D102 D103 D104 D100 FB (INT)[] Para1 --- Para1 D100

Section 1-5 Unit Version 4.0 or Later Text strings can be used in ST programming to easily create text string pro- cessing programs. 1-5 CS1-H CPU Unit Ver. 3.0 Upgrades The following table shows the functional upgrades for CS1-H CPU Unit Ver. 3.0. Functional Upgrades for CS1-H CPU Unit Ver. 3.0 MOV #426C stBlack[0] MOV #6163 stBlack[1] " Bl" is #426C in ASCII. " ac" is #6163 in ASCII. 06/05/28 Black: 9 White: 18 Blue: 7 Pink: 30 Black White Blue Pink 9 18 7 30 Production log file created. File name LineA.txt FB to Create Date Text FB to Create Production Log File (* Convert black quantity to string *) (* Convert white quantity to string *) (* Convert blue quantity to string *) (* Convert pink quantity to string *) (* Get date text *) (* Create production log LineA.txt *) GetDate(stDay) Name: Generate Date Text Function: To create text data for yy/mm/dd (* Create yymm text *) (* Create ddhh text *) (* Insert / between yy and mm; extract only dd and combine *) Function Section Function blocks (when using CX-Programmer Ver. 5.0 or higher) 1-5-1 Serial Gateway (converting FINS commands to CompoWay/F com- mands at the built-in serial port) 1-5-2 Comment memory (in internal flash memory) 1-5-3 Expanded simple backup data 1-5-4 Free running timer (system timer after power is turned ON) 1-5-5

Section 1-5 Changes to Operating Specifications 1-5-1 Function Blocks (FB) Pre-Ver. 2.0 Earlier Units did not support function blocks (FB). Unit Ver. 3.0 or Later Function blocks (FB) conforming to IEC 61131-3 are supported. Use of func- tion blocks is determined by the user. Note IEC 61131-3 is an international standard for programmable logic controllers (PLC) established by the International Electro-technical Commission (IEC). This standard is divided into seven parts, of which Part 3 Programming Languages (IEC 61131-3) provides reg- ulations for programming PLCs. Function blocks can be created with CX-Programmer Ver. 5.0 or higher by the user and pasted into normal programs. The standard function blocks provided by OMRON in the OMRON FB Library can also be pasted into normal pro- grams. Function blocks enable standard processing to be simply inserted into a program as a single unit. Function blocks provide the following features. • Function block algorithms can be written using ladder programming or structured text (see note). Note Structured text is a high level textual language designed for industrial control (primarily PLCs) stipulated in IEC 61131-3. The structured text supported by CX-Programmer Ver. 5.0 conforms to IEC 61131-1. • A single function block that has been created can be stored in a library for easy reuse of standard processing. • Programs that contain function blocks (ladder programming or structured text), can also be uploaded or downloaded in the same way as normal programs that do not contain function blocks. Tasks that include function blocks, however, cannot be downloaded in task units (although they can be uploaded). • Array (one-dimensional) variables are supported, making it easier to han- dle data specific to an application. New instructions added TXDU(256) and RXDU(255) instructions (sup- port no-protocol communications with Serial Communications Units with unit version 1.2 or later) 1-5-6 Model conversion instructions: XFERC(565), DISTC(566), COLLC(567), MOVBC(568), and BCNTC(621) Special function block instruction: GETID(286) Additional instruc- tion functions TXD(236) and RXD(235) instructions (support no-protocol communications with Serial Com- munications Boards with unit version 1.2 or later) Function Section Maximum number of points expanded for SYSMAC BUS remote I/O communications 1-5-7 Function Section

Section 1-5 1-5-2 Serial Gateway (Converting FINS to CompoWay/F Via Serial Port) Pre-Ver. 2.0 Temperature Controllers, Digital Panel Meters, and other CompoWay/F-com- patible OMRON Components previously could be accessed by sending user- specified CompoWay/F commands from the PLC. This required, however, the use of a Serial Communications Board/Unit protocol macro, execution of the PMCR(260) instruction in the ladder program of the CPU Unit on the same PLC, and implementation of the standard system protocol (CompoWay/F Master). The use of protocol macros prevented access across networks. Note Specific data could be shared without communications instructions if user-specified CompoWay/F commands were not required, however, by using the CJ1W-CIF21 Basic Communications Unit. Unit Ver. 3.0 or Later FINS commands (CompoWay/F commands encapsulated in FINS frames) received by the CPU Unit at the built-in serial port (RS-232C port or peripheral port) are converted automatically into CompoWay/F command frames and transmitted on the serial line. This enables access to CompoWay/F-compati- ble OMRON components that are connected to the CPU Unit’s built-in serial port via either an NS-series Programmable Terminal (PT) or by using the CMND(490) instruction. FINS CompoWay/F FINS System Network Serial Serial Network CMND(490) Network Serial CS/CJ-series CPU Unit with unit version 3.0 or later Protocol conversion CompoWay/F-compatible components can be ac- cessed via the network from personal computers, PTs, or PLCs. CompoWay/F-compatible components

Section 1-5 1-5-3 Comment Memory (in Internal Flash Memory) Pre-Ver. 2.0 Comment data and section data could not be stored in the actual PLC when a project was downloaded from the CX-Programmer to the CPU Unit unless both a Memory Card and EM file memory were available. Unit Ver. 3.0 or Later A comment memory is provided within the CPU Unit’s internal flash memory. Therefore, the following comment/section data can be stored in and read from comment memory even if neither Memory Card nor EM file memory are avail- able. • Symbol table files (including CX-Programmer symbol names and I/O comments) • Comment files (CX-Programmer rung comments and other comments) • Program index files (CX-Programmer section names, section comments, and program comments) When downloading projects using the CX-Programmer Ver. 5.0, either of the following storage locations can be selected as the transfer destination for comment data and section data. • Memory Card • EM file memory • Comment memory (in CPU Unit’s internal flash memory) Note When using CX-Programmer Ver. 4.0 or earlier, this data is stored in either the Memory Card or EM file memory, whichever is available. If neither the Mem- ory Card nor EM file memory is available, the comment/section data cannot be stored in comment memory. 1-5-4 Simple Backup Data Expanded Pre-Ver. 2.0 The simple backup function could not be used to back up comment data or section data. Unit Ver. 3.0 or Later The following files stored in comment memory can be backed up to a Memory Card when a simple backup operation is executed, or the files can be restored to comment memory from the Memory Card. • Symbol table files (including CX-Programmer symbol names and I/O comments) CX-Programmer Ver. 5.0 or later Project Transfer Symbol table file Comment file Program index file CPU Unit Memory Card EM file memory Comment/section data can be stored in this area. Comment/section data can be stored in the actual PLC when downloading projects. Comment memory

Section 1-5 • Comment files (CX-Programmer rung comments and other comments) • Program index files (CX-Programmer section names, section comments, and program comments) This enables backup/restoration of all data in the CPU Unit including I/O com- ments if an error occurs or when adding a CPU Unit with the same specifica- tions without requiring a Programming Device. 1-5-5 Free Running Timer he system timers used after the power is turned ON are contained in the fol- lowing Auxiliary Area words. CPU Unit Simple backup executing Memory Card CS/CJ Series • User program • Parameters • I/O memory Symbol table file (In comment memory) Comment file Program index file These files can also be backed up using simple backup. Name Address Function Access 10-ms Incrementing Free Running Timer A000 This word contains the system timer used after the power is turned ON. 0000 hex is set when the power is turned ON and this value is automat- ically incremented by 1 every 10 ms. The value returns to 0000 hex after reaching FFFF hex (655,350 ms), and then continues to be automati- cally incremented by 1 every 10 ms. (Unit version 3.0 or later) Read-only 100-ms Incrementing Free Running Timer A001 This word contains the system timer used after the power is turned ON. 0000 hex is set when the power is turned ON and this value is automat- ically incremented by 1 every 100 ms. The value returns to 0000 hex after reaching FFFF hex (6,553,500 ms), and then continues to be auto- matically incremented by 1 every 100 ms.(Unit version 3.0 or later) Read-only 1-s Incrementing Free Running Timer A002 This word contains the system timer used after the power is turned ON. 0000 hex is set when the power is turned ON and this value is automat- ically incremented by 1 every sec- ond. The value returns to 0000 hex after reaching FFFF hex (65,535 s), and then continues to be automati- cally incremented by 1 every second. (Unit version 4.0 or later) Read-only

Section 1-5 Note The timer will continue to be incremented when the operating mode is switched to RUN mode. Example: The interval can be counted between processing A and processing B without requiring timer instructions. This is achieved by calculat- ing the difference between the value in A000 for processing A and the value in A000 for processing B. The interval is counted in 10 ms units. CPU Units with unit version 4.0 and later also have a 1-s timer in A002, which is incremented by 1 every 1 s. 1-5-6 New Special Instructions and Functions The following new instructions and instruction functions have been added. For details, refer to the CS/CJ Series Instructions Reference Manual (W340). These new instructions are supported by the CX-Programmer Ver. 5.0 or higher only. • Serial Communications Instructions: Supporting no-protocol communications with Serial Communications Units with unit version 1.2 or later: TXDU(256): TRANSMIT VIA SERIAL COMMUNICATIONS UNIT RXDU(255): RECEIVE VIA SERIAL COMMUNICATIONS UNIT Supporting no-protocol communications with Serial Communications Boards with unit version 1.2 or later: TXD(236): TRANSMIT RXD(235): RECEIVE • Model Conversion Instructions: When using CX-Programmer Ver. 5.0 or higher to convert a C-series lad- der program for use in a CS/CJ-series CPU Unit, the C-series XFER(070), DIST(080), COLL(081), MOVB(082), and BCNT(067) instructions will be automatically converted to the following instructions. The operands do not require editing. XFERC(565) BLOCK TRANSFER DISTC(566) SINGLE WORD DISTRIBUTE COLLC(567) DATA COLLECT MOVBC(568) MOVE BIT BCNTC(621) BIT COUNTER 1-5-7 Increased Points for SYSMAC BUS Remote I/O Communications Earlier Specifications The maximum number of SYSMAC BUS remote I/O points per CPU Unit was 800 points (50 words), which were allocated in the SYSMAC BUS Area (CIO 3000 to CIO 3049). Updated Specifications The maximum number of SYSMAC BUS remote I/O points per CPU Unit has been increased to 1,280 points (80 words), which are allocated in the SYS- MAC BUS Area (CIO 3000 to CIO 3079). The CS Series, including CS1 CPU Units, were designed to have a higher total number of points, the Units were initially released before the higher spec- ification had been fully confirmed, so the official specifications were limited to ensure stable operation. Almost coinciding with release of CPU Units with unit version 3.0, stable oper- ation was confirmed at the higher specification, thereby enabling a change in the official operating specifications. This expansion in the number of points is not related to any upgrade of the Units (CPU Units or SYSMAC BUS Remote I/O Communications Units).

Section 1-5 Therefore, the increase in maximum number of points applies to all CS-series CPU Units, including those that have already been shipped. Refer to the following table for details. Item Before Now Maximum num- ber of points per CPU Unit (total optical/wired points) SYSMAC Bus remote I/O relay area 800 points (50 words) 1,280 points (80 words) Number of Remote I/O Master Units (RM) 2 Units Number of C500 Remote I/O Slave Units (RT) (i.e., Slave Racks)) 2 Units 4 Units C500 Remote I/O Slave Unit (RT) allocated words for 2 unit numbers Up to 20 words in total per Slave Rack. 5 Units 8 Units Slave Rack: Any location, fixed word alloca- tions C200H Special I/O Unit can be connected. Up to 10 words in total per Slave Rack. Maximum points per Remote I/O Master Unit (RM) (Total opti- cal/wired points) SYSMAC BUS Remote I/O Relay Points 512 points (32 words) Maximum number of C500 Remote I/O Slave Units (i.e., Slave Racks) 2 Units 4 Units C500 Remote I/O Slave Unit (RT) allocated words for 2 unit numbers Up to 20 words in total per Slave Rack. Remote I/O Slave Unit’s (RT) unit number cannot be used more than once. Maximum number of C200H Remote I/O Slave Units (RT) (i.e., Slave Racks) 5 Units 8 Units Slave Rack: Any location, fixed word alloca- tions C200H Special I/O Unit can be connected. Up to 10 words in total per Slave Rack. Maximum number of Remote I/O Slaves (Slave Units, I/O Link Units, Remote I/O Units) Optical: 64 Units (Repeater required if num- ber exceeds 32). Wired: Remote Interfaces, Remote Termi- nals: 32 Units total Remote Units: 16 Units.

Section 1-6 1-6 CS1-H CPU Unit Ver. 2.0 Upgrades The following table shows the functional upgrades for CS1-H CPU Unit Ver. 2.0. Functional Upgrades for CS1-H CPU Unit Ver. 2.0 1-6-1 Downloading and Uploading Individual Tasks Previous CPU Units (Pre-Ver. 2.0 CPU Units) With the pre-Ver. 2.0 CPU Units, individual program tasks could not be down- loaded from the CX-Programmer. It was only possible to download the entire user program. For example, if several programmers were developing the program, the project manager had to unify each program after debugging and then down- load the entire user program. Furthermore, the entire user program had to be downloaded even if just a few changes were made. Note It was possible to upload individual program tasks with CS/CJ-series PLCs. Function Reference Downloading and Uploading Individual Tasks 1-6-1 Improved Read Protection Using Passwords 1-6-2 Write Protection from FINS Commands Sent to CPU Units via Networks 1-6-3 Online Network Connections without I/O Tables 1-6-4 Communications through a Maximum of 8 Network Levels 1-6-5 Connecting Online to PLCs via NS-series PTs 1-6-6 Setting First Slot Words 1-6-7 Automatic Transfers at Power ON without a Parameter File 1-6-8 Operation Start/End Times 1-6-9 New Application Instructions 1-6-10 CX-Programmer CX-Programmer CX-Programmer Developer A Developer C Developer B Manager Unification Entire user program Download CS/CJ Series Individual tasks can be uploaded.

Section 1-6 CPU Unit Ver. 2.0 Overview With CPU Unit Ver. 2.0 or later CPU Units, individual program tasks can be uploaded and downloaded from the CX-Programmer. Usage When several programmers are developing a program, it isn't necessary for a project manager to unify the data because just the debugged tasks can be downloaded/uploaded. Also, transferring individual tasks can help avoid mis- takes. Restrictions to Function Block Use Individual tasks cannot be downloaded for programs containing function blocks (unit version 3.0 or later only) (uploading is possible). 1-6-2 Improved Read Protection Using Passwords Read Protection for Individual Tasks Using Passwords Previous CPU Units (Pre- Ver. 2.0 CPU Units) With the pre-Ver. 2.0 CS/CJ-series CPU Units, it was possible to read-protect the entire PLC with a password (referred to as “UM read protection” below), but it was not possible to protect individual tasks. UM read protection prevented anyone from displaying, editing, or uploading the entire user program from CX-Programmer without inputting the correct password. CPU Unit Ver. 2.0 or Later and CX-Programmer Ver. 4.0 or Higher Overview With the CPU Unit Ver. 2.0 or later CPU Units, it is possible to read-protect individual program tasks (referred to as “task read protection” below) or the entire PLC. same password controls access to all of the read-protected tasks. END CX-Programmer END END Individual tasks (programs) Download individual tasks (programs). CS/CJ-series CPU Unit Ver.2.0 or later CX-Programmer CX-Programmer CX-Programmer Developer A Developer C Developer B Edited Unchanged Unchanged Download individual tasks. Just the edited tasks can be downloaded. CS/CJ-series CPU Unit Ver.2.0 or later

Section 1-6 Task read protection prevents anyone from displaying, editing, or uploading the read-protected set of tasks from CX-Programmer without inputting the cor- rect password. In this case, the entire program can be uploaded, but the read- protected tasks cannot be displayed or edited without inputting the correct password. Tasks that are not read-protected can be displayed, edited, or mod- ified with online editing. Note Task read protection cannot be set if UM read protection is already set. How- ever, it is possible to set UM read protection after task read protection has been set. Operating Procedure 1,2,3... 1. Display the Protection Tab of the PLC Properties Window and register a password in the Task read protection Box. 2. Select the tasks that will be password-protected and select the Task read protect Option in the Program Properties Tab. 3. Connect online and execute either step a or b below. a) Transferring the Program and Setting Password Protection: Select PLC - Transfer - To PLC to transfer the program. The tasks reg- istered in step 2 will be password-protected. END CX-Programmer END END Password? Set a password for particular tasks in the project directory. Those tasks cannot be displayed without inputting the password. CS/CJ-series CPU Unit Ver.2.0 or later The entire user program can be uploaded, but password- protected tasks will not be displayed until the password is input. The other tasks can be displayed/edited and are also accessible through online editing. Right-click. Properties Right-click. Properties

Section 1-6 b) Setting Password Protection without Transferring the Program: Select PLC - Protection - Set Password and click the OK button. The tasks registered in step 2 will be password-protected. Usage Apply read protection to tasks when you want to convert those tasks (pro- grams) to “black box” programs. Note 1. If CX-Programmer Ver. 3.2 or an earlier version is used to read a task with task read protection applied, an error will occur and the task will not be read. Likewise, if a Programming Console or the PT Ladder Monitor func- tion is used to read a password protected task, an error will occur and the task will not be read. 2. The entire program can be transferred to another CPU Unit even if individ- ual tasks in the program are read-protected. It is also possible to connect online and create a program file (.OBJ file) with file memory operations. In both cases, the task read protection remains effective for the password- protected tasks. 3. When the CX-Programmer is used to compare a user program in the com- puter's memory with a user program in the CPU Unit, password-protected tasks will be compared too. Restrictions on Function Block Use For programs containing function blocks (unit version 3.0 or later only), func- tion block definitions can be read even if the entire program or tasks are read- protected. Enabling/Disabling Creating File Memory Program Files Previous CPU Units (Pre- Ver. 2.0 CPU Units) With the pre-Ver. 2.0 CS/CJ-series CPU Units, it was possible use file mem- ory operations to transfer a program file (.OBJ file) to a Memory Card even if the program was protected with UM read protection. (Consequently, illegal copies could be made.) CPU Unit Ver. 2.0 or Later and CX-Programmer Ver. 4.0 or Higher Overview When the entire program or individual tasks in a CPU Unit Ver. 2.0 or later are read-protected from the CX-Programmer, an option can be set to enable or disable the creation/backup of.OBJ program files. It will not be possible to cre- ate program files (.OBJ files) with file memory operations if the cre- ation/backup of program files is prohibited with this setting. (This setting prohibits both online transfers to a Memory Card/EM file memory as well as offline storage of PLC data that was uploaded to the CX-Programmer.) Disabling the creation of file memory program files can help prevent illegal copying of the user program. END END END Task 0 Task 1 Task 2 Password applied. Task converted to "black box." Accessable Not accessable Accessable

Section 1-6 Operating Procedure 1,2,3... 1. When registering a password in the UM read protection password Box or Task read protection Box, select the Prohibit from saving into a protected memory card Option. 2. Either select PLC - Transfer - To PLC to transfer the program or select PLC - Protection - Set Password and click the OK button. Usage This option can be used to prevent the program from being transferred out of the PLC using the password. Note 1. The simple backup operation can still be performed when the creation of program files is prohibited, but the backup program file (BACKUP.OBJ) will not be created. 2. The program can be copied when program read protection is not enabled. 3. The setting to enable/disable creating file memory program files will not take effect unless the program is transferred to the CPU Unit. Always trans- fer the program after changing this setting. Enabling/Disabling Write Protection for Individual Tasks Using Passwords Previous CPU Units (Pre-Ver. 2.0 CPU Units) With the pre-Ver. 2.0 CS/CJ-series CPU Units, the CPU Unit's user program memory (UM) can be write-protected by turning ON pin 1 of the CPU Unit's DIP switch. In this case, it is possible to overwrite the user program memory by turning OFF pin 1. CX-Programmer CX-Programmer Password? When a password is being registered for the entire user program or selected tasks, the creation of backup program files (.OBJ files) can be enabled/disabled with an option setting. Online creation of backup program files (.OBJ files) prohibited by option setting. CPU Unit Backup program files (.OBJ files) cannot be created with file memory operations. Uploading of all PLC data is prohibited. Properties Right-click.

Section 1-6 CPU Unit Ver. 2.0 or Later and CX-Programmer Ver. 4.0 or Higher With the CPU Unit Ver. 2.0 and later CPU Units, the CPU Unit's UM area can be write protected by turning ON pin 1 of the CPU Unit's DIP switch. The pro- gram (or selected tasks) can also be write-protected if the write protection option is selected from the CX-Programmer when a password is being regis- tered for the entire program or those selected tasks. The write protection set- ting can prevent unauthorized or accidental overwriting of the program. Note 1. If the selected tasks or program are write-protected by selecting this option when registering a password, only the tasks (program) that are password- protected will be protected from overwriting. It will still be possible to over- write other tasks or programs with operations such as online editing and task downloading. 2. All tasks (programs) can be overwritten when program read protection is not enabled. 3. The setting to enable/disable creating file memory program files will not take effect unless the program is transferred to the CPU Unit. Always trans- fer the program after changing this setting. Operating Procedure 1,2,3... 1. When registering a password in the UM read protection password Box or Task read protection Box, select the Prohibit from overwriting to a protect- ed program Option. 2. Either select PLC - Transfer - To PLC to transfer the program or select PLC - Protection - Set Password and click the OK button. CX-Programmer Password? When a password is being registered for the entire user program or selected tasks, program write-protection can be enabled/disabled with an option setting. The user program cannot be overwritten. CPU Unit Overwriting can be prohibited with password protection, regardless of the DIP switch setting. Memory Card The user program cannot be overwritten. Properties Right-click.

Section 1-6 Auxiliary Area Flags and Bits related to Password Protection 1-6-3 Write Protection from FINS Commands Sent to CPU Units via Networks Previous CPU Units (Pre-Ver. 2.0 CPU Units) With the pre-Ver. 2.0 CS/CJ-series CPU Units, there was no way to prohibit write operations and other editing operations sent to the PLC's CPU Unit as FINS commands through a network such as Ethernet, i.e., connections other than direct serial connections. CPU Unit Ver. 2.0 or Later Summary With the CPU Unit Ver. 2.0 and later CS/CJ-series CPU Units, it is possible to prohibit write operations and other editing operations sent to the PLC's CPU Unit as FINS commands through a network (including write operations from CX-Programmer, CX-Protocol, CX-Process, and other applications using Fin- sGateway). Read processes are not prohibited. FINS write protection can disable write processes such as downloading the user program, PLC Setup, or I/O memory, changing the operating mode, and performing online editing. It is possible to exclude selected nodes from write protection so that data can be written from those nodes. An event log in the CPU Unit automatically records all write processes sent through the network and that log can be read with a FINS command. Name Bit address Description UM Read Protection Flag A09900 Indicates whether or not the PLC (the entire user program) is read-protected. 0: UM read protection is not set. 1: UM read protection is set. Task Read Protec- tion Flag A09901 Indicates whether or not selected program tasks are read-protected. 0: Task read protection is not set. 1: Task read protection is set. Program Write Protection for Read Protection A09902 Indicates whether or not the write protection option has been selected to prevent overwriting of password-protected tasks or programs. 0: Overwriting allowed 1: Overwriting prohibited (write-protected) Enable/Disable Bit for Program Backup A09903 Indicates whether or not a backup program file (.OBJ file) can be created when UM read protec- tion or task read protection is set. 0: Creation of backup program file allowed 1: Creation of backup program file prohibited

Section 1-6 Example: Note This function prohibits writing by FINS commands only, so it has no effect on write operations by functions other than FINS commands, such as data links. Example Write Protection Patterns Computer #1 PLC #1 Network Write operations by FINS com- mands are prohibited from some nodes in the network (in this exam- ple, computer #1, PLC #1, and PLC #2). Network PLC #2 Write access to this PLC is enabled/disabled. Network PLC #3 Computer #2 Write operations by FINS com- mands are not prohibited from selected nodes in the network (in this example, computer #2 and PLC #3). Connection pattern Diagram (example) Write protection From a computer through a direct serial connection Direct connection to PLC Cannot be applied. Gateway connection (Serial-to-net- work) to PLC Can be applied. PLC Computer Write-protection not effective Peripheral port RS-232C port Serial connection (Peripheral bus or host link) RS-232C port or 422A/485 port on a Communications Board/Unit Computer PLC #1 PLC #2 Serial connection (Peripheral bus or host link) Network The CPU Unit in PLC #2 can be write-protected.

Section 1-6 Operation With the CX-Programmer, open the PLC Setup's FINS Protection Tab and select the Use FINS Write Protection Option. When this option is selected, it will not be possible to execute write operations for that CPU Unit with FINS commands sent through a network. To permit write operations from particular nodes, enter network addresses and node addresses for the node under Pro- tection Releasing Addresses. (Up to 32 nodes can be excluded from FINS Write Protection). From a computer through a direct network connection Can be applied. From another PLC in the network Can be applied. Connection pattern Diagram (example) Write protection Computer PLC #1 PLC #2 Network The CPU Unit in PLC #2 can be write-protected. CMND PLC #1 PLC #2 If the CMND instruction is used to send a FINS command (requesting a write operation) to the CPU Unit of PLC #2, the operation is not performed. The CPU Unit in PLC #2 can be write-protected. Network

Section 1-6 PLC Setup Usage The system can be configured so that a PLC can be written only from autho- rized nodes in the network. (For example, use this function when the system's control/monitoring computer is the only node allowed to write to a Controller within a piece of equipment.) By limiting the number of nodes that can write to the PLC, it is possible to pre- vent system problems caused by unintentional overwrites during data moni- toring. Item Address in Programming Console Description Settings Default setting Use FINS Write Protection Word 448, bit 15 Sets whether the CPU Unit is write-protected from FINS com- mands sent through the network. (Does not prohibit FINS com- mands sent through a direct serial connection). 0: Write protection disabled 1: Write protection enabled 0: Write protection disabled Nodes Excluded from Write Protec- tion (Protection Releasing Addresses) Words 449 to 480 This area lists the nodes in the network that are not restricted by FINS write protection. Up to 32 nodes can be specified. Note These settings are effective only when FINS write protection is enabled. Bits 08 to 15 Network address: Network address of the FINS command source 00 to 7F hex Bits 00 to 07 Node address: Node address of the FINS command source 01 to FE hex, or FF hex (FF hex: node address unspecified) Number of Nodes Excluded from FINS Write Protection (Do not set this value. It is automati- cally calculated by the CX-Program- mer.) Word 448, bits 00 to 07 Contains the number of nodes that are not subject to the FINS write protection. If 0 is specified (no nodes excluded from write protection), FINS write commands are prohib- ited from all nodes other than the local node. Note This setting is effective only when FINS write protection is enabled. 0 to 32 (00 to 20 hex) (A value of 0 indi- cates that all nodes are subject to write protection.) 0 (All nodes subject to write protection.)

Section 1-6 Operations Restricted by Network FINS Write Protection FINS Write Commands The following FINS commands are restricted by FINS write protection when sent to the CPU Unit through the network. CS/CJ-series PLC Equipment Network Controller Allowed to write/con- trol PLC Network Network System control/monitoring computer Allowed to write/control Monitoring computer Not allowed to write/control Code Command name Code Command name 0102 hex MEMORY AREA WRITE 2101 hex ERROR CLEAR 0103 hex MEMORY AREA FILL 2103 hex ERROR LOG POINTER CLEAR 0105 hex MEMORY AREA TRANSFER 2203 hex SINGLE FILE WRITE 0202 hex PARAMETER AREA WRITE 2204 hex FILE MEMORY FORMAT 0203 hex PARAMETER AREA FILL (CLEAR) 2205 hex FILE DELETE 0307 hex PROGRAM AREA WRITE 2207 hex FILE COPY 0308 hex PROGRAM AREA CLEAR 2208 hex FILE NAME CHANGE 0401 hex RUN 220A hex MEMORY AREA-FILE TRANSFER 0402 hex STOP 220B hex PARAMETER AREA-FILE TRANSFER 0702 hex CLOCK WRITE 220C hex PROGRAM AREA-FILE TRANSFER 0C01 hex ACCESS RIGHT ACQUIRE 2215 hex CREATE/DELETE DIRECTORY 2301 hex FORCED SET/RESET 2302 hex FORCED SET/RESET CANCEL

Section 1-6 Operations from CX-Programmer (including CX-Net) through the Network The following CX-Programmer (including CX-Net) operations are restricted by FINS write protection when performed on the CPU Unit through the network. Note 1. FINS write protection does not prevent CX-Programmer operations from a computer connected through a direct serial connection. 2. FINS write protection does not prevent the following file memory write operations. • Automatic transfer from the Memory Card at startup • Simple backup function (including backup operations to selected Units/Boards) • Writing files with the FWRIT (WRITE DATA FILE) instruction Operations from Other Support Software FINS write protection also prevents the following operations performed through the network by the CX-Protocol and CX-Process. • Changing the CPU Unit's operating mode, writing memory areas, transferring PLC Setup settings, transferring the I/O table, forced set/reset, and clearing the CPU Unit's error log Operations from Applications That Use FinsGateway FINS write protection prevents all write operations addressed to the CPU Unit from applications that use FinsGateway, such as PLC Reporter and Compo- let. 1-6-4 Online Network Connections without I/O Tables Previous CPU Units (Pre-Ver. 2.0 CPU Units) With the pre-Ver. 2.0 CPU Units, it was not possible to make an online con- nection to other PLCs in the network from CX-Programmer unless the I/O tables had been created (even if the network connections were completed) because the Network Communications Unit itself was not recognized from the CPU Unit. Consequently, it was necessary to connect a Programming Device (CX-Programmer or a Programming Console) to each PLC through a serial connection and create and I/O tables in each PLC in order to make online connections through the network. Operations not allowed through the network when FINS write protection is enabled. • Changing the Operating Mode • Transferring the ladder program to the CPU Unit • Transferring parameter area data (PLC Setup, I/O table, and CPU Bus Unit Setup) to the CPU Unit • Transferring memory area data (I/O memory data) to the CPU Unit • Transferring the variable table, comments, or program index to the CPU Unit • Forced Set/Reset • Changing timer/counter set values • Online editing • Writing file memory • Clearing the error log • Setting the clock • Releasing the access right • Transferring the routing table • Transferring the data link table

Section 1-6 CPU Unit Ver. 2.0 or Later Summary With the CPU Unit Ver. 2.0 and later CS/CJ-series CPU Units, the CPU Unit can recognize a CPU Bus Unit (such as a Network Communications Unit, see note) even if the I/O tables have not been created and there is no registered I/O tables. Note Network Communications Units include Ethernet Units, Controller Link Units, SYSMAC Link Units, and DeviceNet Units. Usage If the nodes are connected to the network, this function allows a computer- based Programming Device (such as the CX-Programmer) to connect online to PLCs in the network even if the I/O tables have not been created. Since a network connection is established with the PLCs, setup operations can be performed such as creating the I/O tables (or editing and transferring I/O tables), transferring the user program, transferring the PLC Setup, and trans- ferring the CPU Bus Unit Setup. This function is particularly useful when connecting the CX-Programmer via Ethernet (using a CS1W-ETN21), because the I/O tables can be created through Ethernet so a serial cable isn't required and it isn't necessary to spend extra time establishing a serial connection. Details • Applicable Units: All CS/CJ-series CPU Bus Units • Applicable computer-based Programming Devices: CX-Programmer and CX-Protocol only • Applicable functions: Online connections from CX-Programmer and CX- Protocol, and online functions of the applicable CPU Units and CPU Bus Units CPU Bus Unit (including Network Communications Units) CS/CJ-series CPU Unit Ver.2.0 or later Network Online connection can be made. CPU Bus Units (including Network Communications Units) can be recognized before an I/O table is created. CX-Programmer Ethernet Ethernet CX-Programmer 1:1 Computer-to-PLC connection 1:N Computer-to-PLC connection Even without an I/O table, it is possible to make an online con- nection, create the I/O table, transfer the program, and per- form other operations. CS/CJ- series CPU Unit Ver.2.0 CS/CJ- series CPU Unit Ver.2.0 CS/CJ- series CPU Unit Ver.2.0 I/O table not registered I/O table not registered I/O table not registered Even without an I/O table, it is possible to make an online connection, create the I/O table, transfer the program, and perform other operations. CS/CJ- series CPU Unit Ver.2.0 I/O table not registered

Section 1-6 Note 1. A non-fatal I/O verification error will occur if a CPU Bus Unit (including a Network Communications Unit) is used without creating I/O tables. 2. With a CPU Unit Ver. 2.0 or later CS1-H CPU Unit, CPU Bus Units can be used even if the I/O tables have not been created, but the purpose of this function is making an online connection through the network with a com- puter-based Programming Device (such as the CX-Programmer). The I/O tables are used to identify the mounted Units and allocate I/O, so always create the I/O tables before operating the PLC. 3. Data can be exchanged between the CPU Unit and CPU Bus Units even if the I/O tables have not been created, but do not perform any online func- tions other than establishing an online connection with a computer-based Programming Device (such as the CX-Programmer). 4. When a CS1W-ETN21 or CJ1W-ETN21 Ethernet Unit is being used, the Ethernet Unit's IP address is automatically set to the default value of 192.168.250.xx, where xx is the FINS node address. After connecting the ethernet cable between the CX-Programmer and PLC (without making a direct serial connection and creating the I/O tables), manually set the com- puter's IP address (Example: 192.168.250.55) in the Windows Local Area Connection Properties. An online connection can be established just by setting the Ethernet Unit's IP address (192.168.250.xx) and node in the CX-Programmer. Note When connecting the computer directly to the Ethernet Unit, use an Ethernet crossover cable. 1-6-5 Communications through a Maximum of 8 Network Levels Previous CPU Units (Pre-Ver. 2.0 CPU Units) With the pre-Ver. 2.0 CPU Units, it was possible to communicate through 3 network levels max. (see note), including the local network. It was not possible to communicate through 4 or more levels. Note 1. This functionality is enabled only after setting routing tables with the CX- Net in CX-Programmer version 4.0 or higher. 2. A Gateway to the network via serial communications was not counted as a level. FINS command source OR Serial connection Network 1 This connection is not counted as a network level. Level count = 1 Network 2 Level count = 2 Network 3 FINS command destination

Section 1-6 CPU Unit Ver. 2.0 or Later Summary With the CPU Unit Ver. 2.0 or later CS/CJ-series CPU Units, it is possible to communicate through 8 network levels max. (see note), including the local network. Note 1. FINS commands can only be sent across up to 8 network levels, however, when the destination is a CPU Unit. FINS commands can be sent to other destinations up to 3 network levels away. 2. CX-Net in CX-Programmer version 4.0 or higher must be used to set rout- ing tables to enable communicating through 8 network levels. 3. A Gateway to the network via serial communications was not counted as a level. Compatible Networks Only the following 2 kinds of networks can be used when communicating through a maximum of 8 networks. The network levels can be combined in any order. • Controller Link • Ethernet Note Communications are restricted to a maximum of 8 networks through DeviceNet and SYSMAC Link networks. Configuration of Compatible Models All of the CPU Units must be CPU Unit Ver. 2.0 or later CS/CJ-series CPU Units. Also, the Gateway Counter Setting must be made with the CX-Net. Internal Structure The Gateway Counter (GCT) is in the FINS header of the FINS com- mand/response frame. This counter value is decremented (−1) each time a network level is crossed. FINS Command Frame FINS command source OR Serial connection This connection is not counted as a network level. Network 1 Network 2 Level count = 1 Level count = 4 Level count = 3 Level count = 2 Network 4 Network 3 Network 8 Network 7 Level count = 7 FINS command destination ICF RSV GCT FINS header Command code Text GCT (Gateway counter: Number of allowed bridge passages) The standard setting is 02 hex when sending, but this value can be user-set up to 07 hex. The count is decremented by one each time a network level is passed.

Section 1-6 Example: Operating Procedure Set the maximum number of network levels that can be crossed by setting the Gateway Counter Setting to 2 or 7. The gateway counter setting can be changed in the routing table settings of the CX-Net in the CX-Programmer Ver.4.0 or higher. Note 1. The gateway counter is the maximum number of levels that can be crossed, i.e., the maximum number of junctions. With earlier CPU Units (Pre-Ver. 2.0 CPU Units), up to 3 network levels were allowed, so the gateway counter was set to 2. With the CPU Unit Ver. 2.0 and later CS/CJ-series CPU Units, up to 8 network levels are allowed, so the maximum gateway counter setting is 7. 2. With CS/CJ-series CPU Units Ver. 2.0 or later, communications are possi- ble for up to 8 network levels simply by setting the normal routing tables. No other operations are required. 3. When using communications only for up to 3 network levels, the CS/CJ-se- ries CPU Units Ver. 2.0 or later can be used together with other CPU Units. When using communications only for up to 4 to 8 network levels, use only CS/CJ-series CPU Units Ver. 2.0 or later. Other CPU Units cannot be used. (Routing error (error codes 0501 to 0504 hex) may occurs in one of the relaying PLCs, preventing a FINS response from being returned. 4. With CS/CJ-series CPU Units with unit version 2.0 or later, the Gateway Counter (GCT: Number of allowed bridges passed) for FINS command/ response frames is the value decremented from 07 hex (variable). (In ear- lier versions, the value was decremented from 02 hex.) With unit version 3.0 or later, the default GCT for FINS command/response frames is the value decremented from 02 hex. CX-Net can be select to used 07 hex as the value from which to decrement. 5. Do not use the Gateway Counter (GCT: Number of allowed bridge passag- es) enclosed in the FINS header of the FINS command/response frame in verification checks performed by user applications in host computers. The GCT in the FINS header is used by the system, and a verification error may occur if it is used to perform verification checks in user applications, partic- ularly when using CS/CJ-series CPU Units with unit version 2.0 or later. FINS command source FINS command Network 1 Network 2 Network 3 FINS command At this point, the gateway counter = 7 hex At this point, the gateway counter = 6 hex FINS command FINS command Network 4 At this point, the gateway counter = 5 hex At this point, the gateway counter = 4 hex FINS command At this point, the gateway counter = 0 hex Network 8 FINS command destination

Section 1-6 1-6-6 Connecting Online to PLCs via NS-series PTs Summary The CX-Programmer can be connected online to a PLC connected via a serial line to an NS-series PT that is connected to the CX-Programmer via Ethernet (see note 2). This enables uploading, downloading, and monitoring the ladder program and other data. Note 1. The NS-series PT must be version 3.0 or higher and the CX-Programmer must be version 3.1 or higher. 2. Connection is not possible through an NS-series PT connected serially to the CX-Programmer. Connection Method In CX-Programmer, open the Change PLC Window and set the Network Type to Ethernet. Click the Settings Button and set the IP address of the NS-series PT on the Driver Tab Page. Also make the following settings on the Network Tab Page. • FINS Source Address Set the local network address of the NS-series PT for the Network (exam- ple network address: 1). • FINS Destination Address Network: Set the address to 111 if the PLC is connected to serial port A on the NS-series PT and to 112 if it is connected to serial port B. Node: Always set to 1 • Frame Length: 1,000 (See note.) • Response Timeout: 2 Note Do not set the frame length higher than 1,000. If any higher value is used, the program transfer will fail and a memory error will occur. CX-Programmer (Example IP address: 192.168.0.1) Ethernet (See note 1.) (Example network address: 1) CS/CJ-series CPU Unit Ver. 2.0 Connect online to PLC #1 to enable programming, monitoring, and other operations. NS-series PT (Example IP address: 192.168.0.22) 1:N NT Link (Example network address: 111) PLC #1

Section 1-6 1-6-7 Setting First Slot Words Previous CPU Units (Pre-Ver. 2.0 CPU Units) With CX-Programmer Ver. 3.0 or earlier, only the first addresses on Racks could be set. The first address for a slot could not be set. CX-Programmer Ver. 3.1 or Higher Summary Starting with CX-Programmer Ver. 3.1, the first addresses for slots can be set when editing the I/O tables for CS/CJ-series CPU Units (CS1-H, CJ1-H, and CJ1M). The first address can be set for up to eight slots. (See note.) Note This function is supported only for CS1-H/CJ1-H CPU Units manufactured on June 1, 2002 or later (lot number 020601@@@@ or later). It is supported for all CJ1M CPU Units regardless of lot number. It is not supported for CS1D CPU Units. 0 1 2 0 1 2 3 4 0 1 2 CX-Programmer Ver. 3.0 or earlier First addresses on Racks Rack No. CPU Rack Rack 1 Rack 2 Rack 3 Rack 4 Rack 5 Rack 6 Rack 7 First address 100 0 200 Example: CPU Rack slot Rack 1 slot Rack 2 slot CIO 0100 CIO 0000 CIO 0200

Section 1-6 Operating Procedure Select Option - Rack/Slot Start Addresses in the PLC IO Table - Traffic Con- troller Window. This command will enable setting both the first Rack addresses and the first slot addresses. This function can be used, for example to allocate fixed addresses to Input Units and Output Units. (With CQM1H PLCs, input bits are from IR 000 to IR 015 and output bits are from IR 100 to IR 115. First slot addresses can be set when replacing CQM1H PLCs with CS/CJ-series PLCs to reduce conver- sion work.) Note The first address settings for Racks and slots can be uploaded/downloaded from/to the CPU Unit. Select Option - Rack/Slot Start. Addresses. Double-click 100 0 102 1 105 5 0 1 2 0 1 2 0 1 2 3 4 CX-Programmer Ver. 3.2 or higher Rack No. CPU Rack CPU Rack Rack 1 Rack 1 Rack 2 Rack 2 Slot No. Slot No. 00 Slot No. 02 Slot No. 00 Slot No. 02 Slot No. 00 Slot No. 01 Example: CPU Rack slot Rack 1 slot Rack 2 slot CIO 0005 CIO 0105 CIO 0001 CIO 0102 CIO 0000 CIO 0100 Up to 8 settings can be made. First slot addresses

Section 1-6 CPU Unit Ver. 2.0 or Later and CX-Programmer Ver. 4.0 or Higher Summary When using CX-Programmer Ver.4.0 or higher with CPU Unit Ver. 2.0 or later, the first address can be set for up to 64 slots. Note This function is supported only for CS1-H, CJ1-H, and CJ1M CPU Units Ver. 2.0 or later. It is not supported for CS1D CPU Units. 1-6-8 Automatic Transfers at Power ON without a Parameter File Previous CPU Units (Pre-Ver. 2.0 CPU Units) Previously with the CS/CJ-series CPU Units, both the program file for auto- matic transfer at power ON (AUTOEXEC.OBJ) and the parameter file for auto- matic transfer at power ON (AUTOEXEC.STD) had to be stored on the Memory Card to enable automatic transfers to the CPU Unit at power ON. Also, the parameter file for automatic transfer at power ON (AUTOEXEC.STD) could not be created without the actual PLC (regardless of whether it was made in online operations from the CX-Programmer or a Programming Con- sole or by using the easy backup operation). 100 0 102 1 105 5 50 0 1 2 0 1 2 0 1 2 3 4 0 1 2 CX-Programmer Ver. 4.0 or higher Rack No. CPU Rack CPU Rack Rack 1 Rack 1 Rack 2 Rack 2 Rack 7 Slot No. Slot No. 00 Slot No. 02 Slot No. 00 Slot No. 02 Slot No. 00 Slot No. 01 Slot No. 01 Example: CPU Rack slot Rack 1 slot Rack 2 slot CIO 0005 CIO 0105 CIO 0001 CIO 0102 CIO 0000 CIO 0100 Up to 64 settings can be made. Rack 7 slot CIO 0050 CIO 0155 CPU Unit Ver. 2.0 or later First slot addresses

Section 1-6 Even if a program file (.OBJ) was created offline without the actual PLC and then sent to a remote PLC as an email attachment, the program file could not be transferred to the CPU Unit without a Programming Device. CPU Unit Ver. 2.0 or Later Summary With CS/CJ-series CPU Unit Ver. 2.0, the user program can be automatically transferred to the CPU Unit at power ON without a parameter file (.STD) if the name of the program file (.OBJ) is changed to REPLACE.OBJ on the CX-Pro- grammer and the file is stored on a Memory Card. If data files are included with the program file using this function, the following data file names are used: REPLACE.IOM, REPLCDM.IOM, [email protected]. Note 1. If the Memory Card contains a REPLACE.OBJ file, any parameter file on the Memory Card will not be transferred. 2. If the Memory Card contains both a REPLACE.OBJ file and a AUTOEX- EC.OBJ file, neither will be transferred. Note With CX-Programmer Ver. 3.0 or higher, a program file (.OBJ) can be created offline and saved on a computer storage media. Select Transfer - To File from the PLC Menu. This enable creating a program file offline without a PLC so that the name can be changed to enable sending the program file. Personal computer Mail Mail Internet Program file (.OBJ) sent as mail attachment. CPU Unit Local site (no Programming Device) Program cannot be transferred (see note). Program file (AUTOEXEC.OBJ) Note: Transfer is not possible because there is no parameter file (AUTOEXEC.STD). Personal computer Mail Mail Internet Program file created on CX- Programmer (see note), file name changed to REPLACE.OJB, and file sent as mail attachment. CPU Unit Remote site (no Programming Device) Program can be transferred (see note). REPLACE.OBJ Note: Transfer is possible even without a parameter file (AUTOEXEC.STD).

Section 1-6 1-6-9 Operation Start/End Times Previous CPU Units (Pre-Ver. 2.0 CPU Units) The time that operation started and the time operation ended were not stored in the CPU Unit. CPU Unit Ver. 2.0 or Later The times that operation started and ended are automatically stored in the Auxiliary Area. • The time that operation started as a result of changing the operating mode to RUN or MONITOR mode is stored in A515 to A517 of the Auxil- iary Area. The year, month, day, hour, minutes, and seconds are stored. • The time that operation stopped as a result of changing the operating mode to PROGRAM mode or due to a fatal error is stored in A518 to A520 of the Auxiliary Area. The year, month, day, hour, minutes, and sec- onds are stored. This information simplifies managing PLC System operating times. 1-6-10 New Application Instructions The following instructions have been added. Refer to the Programming Man- ual (W340) for details. • Multiple Interlock Instructions: MULTI-INTERLOCK DIFFERENTIATION HOLD (MILH(517)), MULTI- INTERLOCK DIFFERENTIATION RELEASE (MILR(518)), and MULTI- INTERLOCK CLEAR (MILC(519)) • TIME-PROPORTIONAL OUTPUT (TPO(685)) • GRAY CODE CONVERSION (GRY(474)) • Combination Instructions: TEN KEY INPUT (TKY(211)), HEXADECIMAL KEY INPUT (HKY(212)), DIGITAL SWITCH INPUT (DSW(213)), MATRIX INPUT (MTR(210)), and 7-SEGMENT DISPLAY OUTPUT (7SEG(214)) • Time Comparison Instructions: =DT, <>DT, DT, >=DT • Explicit Message Instructions: EXPLICIT MESSAGE SEND (EXPLT(720)), EXPLICIT GET ATTRIBUTE (EGATR(721)), EXPLICIT SET ATTRIBUTE (ESATR(722)), EXPLICIT WORD READ (ECHRD(723)), and EXPLICIT WORD WRITE (ECHWR(724)) • EXPANDED BLOCK COMPARE (BCMP2(502)) (This instruction, previ- ously supported by only the CJ1M PLCs, is now supported by the CS1-H and CJ1-H.) • INTELLIGENT I/O READ (IORD(222)) and INTELLIGENT I/O WRITE (IOWR(223)) (These instructions could previously be used only for Spe- cial I/O Units, but they can now be used to read and write data for CPU Bus Units.)

Section 1-7 1-7 CS1 and CS1-H CPU Unit Comparison 1-7-1 CS1 and CS1-H CPU Unit Comparison Item CS1-H CPU Unit (CS1H-CPU6@H, CS1G-CPU4@H) CS1 CPU Unit (CS1H-CPU6@-E, CS1G-CPU4@-E) Instruction executions times Basic instructions LD: 0.02 µs 0.04 µs OUT: 0.02 µs 0.17 µs Special instructions Example XFER: 300 µs (for 1,000 words) 633 µs (for 1,000 words) BSET: 200 µs (for 1,000 words) 278 µs (for 1,000 words) BCD arithmetic: 8.2 µs min. 14 µs min. Binary arithmetic: 0.18 µs min. 0.25 µs min. Floating-point math: 8 µs min. 10 µs min. SBS/RET: 2.1 µs 37 µs EM Area 1 bank (32 Kwords) min. for all models Not supported by all models Overseeing processing time Normal mode: 0.3 ms Parallel mode: 0.2 ms 0.5 ms Execution timing CPU execution processing modes Any of the following 4 modes: Normal (instructions and periph- eral servicing perform consecu- tively) Peripheral Servicing Priority Mode (instruction execution interrupted to service peripherals at a specific cycle and time; consecutive refreshing also performed) Parallel Processing Mode with Syn- chronous Memory Access (instruc- tion executed and peripheral services in parallel while synchro- nizing access to I/O memory) Parallel Processing Mode with Asynchronous Memory Access (instruction executed and periph- eral services in parallel without syn- chronizing access to I/O memory) Either of following 2 modes: Normal (instructions and peripheral servicing perform consecutively) Peripheral Servicing Priority Mode (instruction execution interrupted to service peripherals at a specific cycle and time; consecutive refresh- ing also performed) (Add for CPU Units with lot number No. 001201@@@@ or later.) CPU Bus Unit special refreshing Data links During I/O refresh period or via special CPU BUS UNIT I/O REFRESH instruction (DLNK(226)) During I/O refresh period DeviceNet remote I/O Protocol macro send/receive data Refreshing of CIO and DM Areas words allocated to CPU Bus Unit

Section 1-7 Tasks Cyclic execution of interrupt tasks via TKON instruction (called “extra cyclic tasks”) Supported (Up to 255 extra cyclic tasks, increasing the total number of cyclic tasks to 288 max.) Not supported (No extra cyclic tasks; 32 cyclic tasks max.) Independent/shared specifi- cations for index and data registers Supported The time to switch between tasks can be reduces if shared registers are used. Not supported (only independent registers for each task) Initialization when tasks are started Supported Task Startup Flags supported. Only Task Flag for first execution Starting subroutines from multiple tasks Global subroutines can be defined that can be called from more than one task. Not supported Interrupt task execution tim- ing during instruction exe- cution For instruc- tions other than the fol- lowing ones Any instruction that is being executed is interrupted when interrupt task conditions are met to start the interrupt task. If the cyclic task (including extra cyclic tasks) access the same data area words as the instruction that was interrupted, data may not be concurrent. To ensure data concurrency, the DI and EI instructions must be used to disable and enable interrupts during a specific part of the program. For BIT COUNTER (BCNT) or BLOCK TRANSFER (XFER) instructions Interrupt tasks are started only after execution of the instruction has been completed, ensuring data concurrency even when the same data area words are accessed from the instruction and the interrupt task. Data backup Backup to Memory Cards (simple backup function) In addition to the data listed at the right, data from Units and Boards mounted to the CPU Rack or Expansion Racks can also be backed up to the Memory Card (via pushbutton on front panel). This is very effective when replacing Units. Backup data includes scan lists for DeviceNet Units, protocol macros for Serial Communications Units/Boards, etc. Only the user program parameters, and I/O memory in the CPU Unit Automatic user program and parameter area backup to flash memory Supported (enabling battery-free operation without a Memory Card) The user program and parameter area data are automatically backed up the flash memory whenever they are transferred to the CPU Unit from the CX-Programmer, file mem- ory, etc. Not supported I/O tables Detailed information on I/O table creation errors Detailed I/O table error information is stored in A261 whenever the I/O tables cannot be created for any reason. Not supported Displaying presence of first rack word setting on Program- ming Console It’s possible to confirm if the first rack word has been specified for the system on the Programming Console display. The first rack word is specified from the CX-Programmer, making it pre- viously impossible to confirm the setting from the Programming Con- sole. Not supported Item CS1-H CPU Unit (CS1H-CPU6@H, CS1G-CPU4@H) CS1 CPU Unit (CS1H-CPU6@-E, CS1G-CPU4@-E)

Section 1-7 Sequence instructions Differentiated LD NOT, AND NOT, and OR NOT instruc- tions Supported Not supported (Can be programmed by combining differentiated LD, AND, and OR instructions with the NOT instruction.) OUTB, SETB, and RSTB instructions to manipulate individual bits in DM and EM Area words Supported Not supported Timer/ counter instructions PV refresh method for TIM, TIMH, TMHH, TTIM, TIML, MTIM, CNT, CNTR, CNR, TIMW, TMHW, and CNTW instructions Either BCD or binary can be selected (with CX-Programmer Ver. 3.0 or higher versions) BCD only Special math instructions 32-bit signed data line coordi- nates and X axis starting point specification for APR instruction Supported Not supported Floating- point deci- mal instruc- tions Single-precision calculations and conversions Supported (enabling standard devi- ation calculations) Not supported Conversions between single- precision floating point and ASCII Supported Floating point can be converted to ASCII for display on PTs ASCII text strings from measure- ment devices can be converted to floating-point decimal for use in cal- culations. Not supported Double-precision calculations and conversions Supported (enabling high-preci- sion positioning) Not supported Text string, table data, and data shift instructions Text string and table data pro- cessing instruction execution Data processing can be performed normally or in the background (specified for each instruction) (Using time slices to process instruction over several cycles reduces the effect of these instruc- tions on the cycle time.) Normal processing only Stack insertions/dele- tions/replacements and stack counts with table processing instructions Supported Effective for tracking workpieces on conveyor lines. Not supported Data control instructions PID with autotuning Supported (eliminating the need to turn PID constants) Not supported Subroutine instructions Global subroutines Supported (GSBS, GSBN, and GRET instructions) Enables easier structuring of sub- routines. Not supported Failure diag- nosis instruc- tions Error log storage for FAL Supported FAL can be executed without plac- ing an entry in the error log. (Only system FAL errors will be placed in the error log.) Not supported Error simulation with FAL/FALS Supported Fatal and nonfatal errors can be simulated in the system to aid in debugging. Not supported Data compar- ison instruc- tions AREA RANGE COMPARE (ZCP) and DOUBLE RANGE COMPARE (ZCPL) Supported Not supported Item CS1-H CPU Unit (CS1H-CPU6@H, CS1G-CPU4@H) CS1 CPU Unit (CS1H-CPU6@-E, CS1G-CPU4@-E)

Section 1-7 Index regis- ter real I/O address con- version for CVM1/CV Program and real I/O memory address compatibility with CVM1/CV-series PLCs CVM1/CV-series real I/O memory addresses can be converted to CS- series addresses and placed in index registers or CS-series real I/O memory addresses in index registers can be converted to CVM1/CV-series addresses. Not supported Condition Flag saving and loading Compatibility with CVM1/CV- series PLCs Condition Flag status can be saved or loading using the SAVE CONDI- TION FLAGS (CCS) and LOAD CONDITION FLAGS (CCL) instruc- tions, enabling applications where Condition Flag status must be passed between different program locations, tasks, or cycles. Not supported Startup mode for PLC Setup defaults when no Programming Console is connected RUN mode PROGRAM mode Operation when Unit/Inner Board doesn’t com- plete startup process CPU Unit startup Starting or not starting (standby) the CPU Unit in MONITOR or RUN mode even if a Unit or an Inner Board has not completed startup processing can be specified in the PLC Setup. CPU Unit standby (fixed) Disabling power interruptions in program sec- tions Supported Instructions between DI and EI are executed without performing power OFF processing even if a power interruption has been detected and confirmed. Not supported Condition Flag operation The statuses of the Equals, Nega- tive, and Error Flags are main- tained for execution of the following instructions. TIM, TIMH, TMHH, CNT, IL, ILC, JMP0, JME0, XCHG, XCGL, MOVR, symbol comparison instruc- tions, CMP, CMPL, CPS, CPSL, TST, TSTN, STC, and CLC The Equals, Negative, and Error Flags are turned OFF after executing the following instructions. TIM, TIMH, TMHH, CNT, IL, ILC, JMP0, JME0, XCHG, XCGL, MOVR, symbol comparison instructions, CMP, CMPL, CPS, CPSL, TST, TSTN, STC, and CLC Item CS1-H CPU Unit (CS1H-CPU6@H, CS1G-CPU4@H) CS1 CPU Unit (CS1H-CPU6@-E, CS1G-CPU4@-E)

Section 1-7 1-7-2 New Functions for Version-1 CS1 CPU Units The following functions have been added or improved in the version-1 CS1 CPU Units (CS1G/H-CPU@@-EV1; previous version: CS1G/H-CPU@@-E). Item Function Application Reference Support for CSV and TXT formats in data files The FREAD/FWRIT instructions can be used to read and write hexadecimal I/O memory data in CSV or TXT for- mat. (Previously, only binary format was supported.) Production results from I/O memory in the CPU Unit can be written to a Mem- ory Card in CSV/TXT format, the Mem- ory Card can be used to read the data to a computer via a Memory Card Adapter, and the data can then be used in spreadsheet software on the computer. Spreadsheet data from a computer can also be transferred in CSV/TXT format to the CPU Unit’s I/O memory via Memory Cards. Section 5 File Memory Func- tions in the CS/CJ Series Programming Manual File operations for instructions (format- ting, deleting, etc.) The CPU Unit can send commands to itself using the CMND instruction to perform file operations. (The CPU Unit could previous not send FINS com- mands to itself.) Files can be formatted, deleted, cop- ied, or renamed and directories can be created on Memory Cards using ladder program instructions during operation. Program replace- ments during opera- tion The entire user program can be loaded from a Memory Card to the CPU Unit during operation to replace the pro- gram. (Previously only AUTOEXEC.OBJ could be used at startup to replace the program.) Switching operations while the PLC is running. Replacing the program without using a Programming Device. DM and EM files for automatic transfer at startup DM and EM files can be automatically loaded to the CPU Unit at startup. (Previously only the data file AUTOEXEC.IOM could be used to load the Special I/O Unit and Inner Board areas starting at D20000 to the DM Area. For other parts of the DM Area, the FREAD instruction had to be used, i.e., automatic transfer at startup was not possible.) Storing settings in the DM and EM Areas at startup. Loading data automatically at startup instead of using FREAD. Simple backup func- tion The user program, parameter data, and I/O memory data can be backed up to a Memory Card by pressing the memory card power button if simple backup was specified on the DIP switch. (Previously a write operation from a Programming Device was required to back up all of this data.) All data could be backed up easily and quickly without a Programming Device whenever a problem occurs. High-speed NT Links High-speed 1:N NT Links are sup- ported, enabling faster communica- tions with PTs (Programmable Terminals) than previously possible. Only the following PTs support high- speed NT Links: NT31/NT631-V2 and the NS-series PT. Better realtime performance for setting and monitoring operations on PTs. NT Link System (1:N Mode) under 2-5-2 Sys- tems in this manual and 6-3- 3 NT Link (1:N Mode) in CS/CJ Series Program- ming Manual High-speed online editing Less time is required to change part of the program when performing online editing in MONITOR mode. (Previously each cycle was increased by up to 90 ms, but the maximum increase for version-1 CPU Units is 12 ms.) The effects on the system are reduced when changing the program for main- tenance during operation. 7-2-3 Online Editing in the CS/CJ Series Programming Manual

Section 1-8 1-8 CS-series Function Tables The following tables list functions for the CS-series CPU Units (including both the CS1 CPU Units and the CS1-H CPU Units). 1-8-1 Functions Arranged by Purpose Purpose Function Reference Studying Basic Operations and the System Studying the system configuration SECTION 2 Spec- ifications and Sys- tem Configuration Studying I/O allocations SECTION 8 I/O Allocations Finding the installation dimensions 5-2-4 Mounting Dimensions Finding the installation method 5-2 Installation Setting the DIP switch 3-1-2 Compo- nents Setting the PLC Setup 7-1 PLC Setup Using special flags in the Auxiliary Area Appendix B Auxil- iary Area Studying the cycle time 10-4-2 Cycle Time Overview Troubleshooting 11-2-4 Error Pro- cessing Flowchart Improving Program Structure Standardizing programs as modules. Program with tasks to divide the pro- gram, use function blocks (FBs), specify symbols, and define local and global symbols. Use ST (Structured Text) language. Programming Manual (W394) Developing a program with several programmers working in parallel. Making the program easier to under- stand. Creating step programs. Use the step instructions. Instructions Refer- ence Manual (W340) Using BASIC-like mnemonic instruc- tions to program processes that are difficult to enter in the ladder dia- gram format (such as conditional branches and loops). Use the block programming instruc- tions. Use ST (Structured Text) language. Simplifying the Program Creating looped program sections. Use FOR(512) and NEXT(513) or JMP(004) and JME(005). Instructions Refer- ence Manual (W340) Indirectly addressing DM words. All words in the DM and EM Areas can be indirectly addressed. Programming Manual (W394) Simplifying the program by switching to PLC memory address specifica- tion. Use Index Registers as pointers to indirectly address data area addresses. The Index Registers are very useful in combination with loops, increment instructions, and table data process- ing instructions. The auto-increment, auto-decrement, and offset func- tions are also supported. Consolidating instruction blocks with the same pattern but different addresses into a single instruction block. Use function blocks (FBs). CX-Programmer Operation Man- ual Function Blocks (W438) Use MCRO(099). Instructions Refer- ence Manual (W340)

Section 1-8 Managing the Cycle Time Reducing the cycle time. • Use tasks to put parts of the pro- gram that don’t need to be exe- cuted into “standby” status. • Use JMP(004) and JME(005) to jump parts of the task that don’t need to be executed. • Convert parts of the task to sub- routines if they are executed only under particular conditions. • Disable a Unit’s Special I/O Unit refreshing in the PLC Setup if it isn’t necessary to exchange data with that Special I/O Unit every cycle. • Set sharing index and data regis- ters by all tasks if index and data registers are not being used. Programming Manual (W394) Setting a fixed (minimum) cycle time. • Variations in I/O response times can be eliminated by suppressing processing variations. Set a minimum cycle time in the PLC Setup. Setting a maximum cycle time. (Generating an error for a cycle time exceeding the maximum.) Set a maximum cycle time (watch cycle time) in the PLC Setup. If the cycle time exceeds this value, the Cycle Time Too Long Flag (A40108) will be turned ON and PLC operation will be stopped. 7-1 PLC Setup Reducing the I/O response time for particular I/O points. Use an I/O interrupt task, immediate refreshing, or IORF(097). Programming Manual (W394) Receiving input pulses shorter than the cycle time. Use a quick-response input on a Unit with High-speed Inputs or a High-density I/O Unit (a Special I/O Unit). 3-6-3 Units with High-speed Inputs and 3-7 C200H High-density I/O Units (Special I/O Units) Finding the I/O refresh times for Units 10-4-2 Cycle Time Overview Studying the I/O response times 10-4-6 I/O Response Time Finding the increase in cycle time caused by online editing 10-4-5 Online Editing Cycle Time Extension Using Interrupt Tasks Monitoring operating status at regu- lar intervals • Monitoring operating status at reg- ular intervals. Use a scheduled interrupt task. Programming Manual (W394) Performing interrupt processing when an input goes ON. • Executing processing immediately with an input. Use an I/O interrupt task. Issuing an interrupt to the CPU when data is received through serial communications. Use a Serial Communications Board and external interrupt task or an ASCII Unit. Executing an emergency interrupt program when the power supply fails. Use a power OFF interrupt task. Enable the power OFF interrupt task in the PLC Setup. Studying the interrupt response time 10-4-7 Interrupt Response Times Finding the priority of interrupt tasks Programming Manual (W394) Purpose Function Reference

Section 1-8 Data Process- ing Operating a FIFO or LIFO stack. Use the stack instructions (FIFO(633) and LIFO(634)). Instructions Refer- ence Manual (W340) Performing basic operations on tables made up of 1-word records. Use range instructions such as MAX(182), MIN(183), and SRCH(181). Performing complex operations on tables made up of 1-word records. Use Index Registers as pointers in special instructions. Performing operations on tables made up of records longer than 1 word. (For example, the temperature, pres- sure, and other manufacturing set- tings for different models of a product could be stored in separate records.) Use Index Registers and the record- table instructions (DIM, GETR, etc.) Programming Manual (W394) System Configuration Monitoring several different kinds of devices through the RS-232C port. Multiple serial ports can be installed with Serial Communications Units (protocol macro) and ASCII Units. 2-3 Basic System Configuration Changing protocol during operation (from a modem connection to host link, for example). Use STUP(237), the CHANGE SERIAL PORT SETUP instruction. Instructions Refer- ence Manual (W340) Connecting Programming Devices Connecting a Programming Con- sole. Connect to the peripheral port with pin 4 of the CPU Unit’s DIP switch OFF. 3-3-2 Program- ming Consoles Connecting a Programming Device (e.g., the CX-Programmer). Connect to the peripheral port with pin 4 of the CPU Unit’s DIP switch OFF or with pin 4 ON and the net- work type of the CX-Programmer set to the peripheral bus. Connect to the RS-232C port with pin 5 of the CPU Unit’s DIP switch ON or with pin 5 OFF and the net- work type of the CX-Programmer set to the peripheral bus. 3-3-3 CX-Pro- grammer Connecting a host computer. Connect to the RS-232C port or peripheral port. (Set the communi- cations mode to “host link” in the PLC Setup.) 2-5 Expanded System Configu- ration Connecting a PT. Connect to the RS-232C port or peripheral port. (Set the communi- cations mode to “NT Link” in the PLC Setup.) Set the PT communications settings for a 1:N NT Link. Connecting a standard serial device to the CPU Unit (no-protocol mode). Connect to the RS-232C port. (Set the communications mode to “no-protocol” in the PLC Setup.) Controlling Out- puts Turning OFF all outputs on basic Output Units and High-density Out- put Units (a type of Special I/O Unit). Turn ON the Output OFF Bit (A50015). Programming Manual (W394) Maintaining the status of all outputs on Output Units when PLC operation stops (hot start). Turn ON the IOM Hold BIt (A50012). Purpose Function Reference

Section 1-8 Controlling I/O Memory Maintaining the previous contents of all I/O Memory at the start of PLC operation (hot start). Turn ON the IOM Hold BIt (A50012). Programming Manual (W394) Maintaining the previous contents of all I/O Memory when the PLC is turned on. Turn ON the IOM Hold BIt (A50012) and set the PLC Setup to maintain the status of the IOM Hold Bit at start-up. (IOM Hold Bit Status at Startup) File Memory Automatically transferring the pro- gram, I/O Memory, and PLC Setup from the Memory Card when the PLC is turned on. • Easily replacing the program onsite. • Operating without a battery. Enable the “automatic transfer at start-up” function by turning ON pin 2 of the CPU Unit’s DIP switch and create an AUTOEXEC file. Programming Manual (W394) Creating a library of programs for dif- ferent program arrangements. Memory Card functions (Program Files) Creating a library of parameter set- tings for various PLC Racks and models. Memory Card functions (Parameter Files) Creating a library of data files with settings for various PLC Racks, and CPU Bus Units. Memory Card functions (Data Files) Storing I/O Comment data within the Memory Card. Memory Card functions (Symbol Table Files) Storing operating data (trend and quality data) within the CPU Unit during program execution. EM File Memory Functions and the FREAD(700)/FWRIT(701) instruc- tions Replacing the program without stopping operation. Memory Card functions (Program Replacement during PLC Operation) Reading and writing I/O memory data with a spreadsheet. Read/write data files using instruc- tions in CSV or text format. Creating data that can be read with a text editor. Use the WRITE TEXT FILE instruc- tion (TWRIT(704)). Text string processing Performing string processing at the PLC which was performed at the host computer previously and reduc- ing the program load at the host computer (operations such as read, insert, search, replace, and exchange). • Easily replacing the program onsite • Operating without a battery Combine the Host Link function with the text string processing instruc- tions. Instructions Refer- ence Manual (W340) Performing string processing opera- tions such as rearranging text strings. Replacing the program without stop- ping operation. Use the string comparison instruc- tions and index registers. Receiving data from external devices (such as bar code readers) through serial communications, stor- ing the data in DM, and reading just the required string when it is needed. Use the WRITE TEXT FILE instruc- tion (TWRIT(704)). Combine the protocol macro func- tion with the text string processing instructions. Purpose Function Reference

Section 1-8 Maintenance and Debugging Changing the program while it is being executed. Use the online editing function from a Programming Device. (Several instruction blocks can be changed with CX-Programmer.) Programming Manual (W394) Sampling I/O Memory data. • Periodic sampling • Sampling once each cycle • Sampling at specified times Data trace at regular intervals Data trace at the end of each cycle Data trace each time that TRSM(045) is executed Confirming there are no errors in instruction execution. Set the PLC Setup to specify the desired operating mode at start-up. (Startup Mode) Recording the time that power was turned on, the last time that power was interrupted, the number of power interruptions, and the total PLC on time. Read the Auxiliary Area words containing power supply information. Startup Time: A510 and A511 Power Interruption Time: A512 and A513 Number of Power Interruptions: A514 Replacing the program without stop- ping operation. Reading the time/date when the user program was changed. Reading the time/date when the parameter area was changed. Set the PLC Setup so that instruc- tion errors are treated as fatal errors. (Instruction Error Operation) Programming/monitoring the PLC remotely. • Programming or monitoring a PLC on the network through Host Link. • Programming or monitoring a PLC through modems. Host Link → Network Gateway function Host Link through modems 2-5 Expanded System Configu- ration Programming/monitoring PLCs in other networks Communicate with PLCs up to 2 network levels away through Controller Link or Ethernet. Error Process- ing and Trou- bleshooting Generating a non-fatal or fatal error for user-defined conditions. • Non-fatal errors (Operation contin- ues.) • Fatal errors (PLC operation stops.) • Not recording user-defined alarms and errors in the error log. FAILURE ALARM: FAL(006) SEVERE FAILURE ALARM: FALS(007) Set the PLC Setup so that user- defined FAL errors are not recorded in the error log. Programming Manual (W394) Analyzing time and logic in execu- tion of an instruction block. FAILURE POINT DETECTION: FPD(269) Recording the time/date of errors and error details. Reading recorded error details. Use the error log function. Up to 20 error records can be stored. Other Functions Allocating words in the I/O Area by specifying the first word allocated to Rack. Set the first word allocated to Rack by registering the I/O table from the CX-Programmer. (Words must be allocated to Racks in the order that the Racks are connected.) Programming Manual (W394) Purpose Function Reference

Section 1-8 1-8-2 Communications Functions (Serial/Network) Reducing input chattering and the effects of noise. Specify the input response times for Basic I/O Units in the PLC Setup. (Basic I/O Unit Input Response Time) Allocating words in the I/O Area freely by specifying the word allo- cated to a slot. Set the first word allocated to a slot by registering the I/O tables from the CX-Programmer. 8-4 Allocating First Words to Slots Purpose Protocol: Required Equipment Reference Monitoring from the Host Com- puter RS-232C or RS-422/485 Host Link: Port in the CPU Unit, Serial Commu- nications Board, or Serial Communi- cations Unit 2-5-2 Sys- tems Host Link communications from the PLC Enclose a FINS command with a Host Link header and terminator and issue it from the PLC as a network communications instruction. Network communications through RS-232C or RS-422/485 Controller Link and Ethernet commu- nications are possible through the Host Link. (Enclose a FINS command with a Host Link header and termina- tor and issue it from the PLC as a net- work communications instruction.) Network Control system Controller Link: Controller Link Unit or Controller Link Board 2-5-3 Com- munications Network Sys- tem Information sys- tem Ethernet: Ethernet Unit Connecting to a Standard Serial Device Creating a custom, user-defined pro- tocol Protocol written in BASIC: ASCII Unit 2-5-2 Sys- tems Creating a simple protocol Protocol Macro: Serial Communications Board or Serial Communications Unit High-speed data exchange No protocol No protocol: CPU Unit’s RS-232C port, ASCII Unit, or Protocol Macro Communicating with a PT Direct access NT Link: Port in the CPU Unit, Serial Commu- nications Board, or Serial Communi- cations Unit Data Link between PLCs High capacity or free word allocation Controller Link: Controller Link Unit 2-5-3 Com- munications Network Sys- tem Low capacity and fixed word alloca- tion PLC Link: PLC Link Unit Data Link between PLC and computer Controller Link: Controller Link Unit or Controller Link Board Message communications between PLCs Normal or high capacity Controller Link: Controller Link Unit Information system Ethernet: Ethernet Unit Purpose Function Reference