Omron CJ1G/H-CPU, CJ1M-CPU, CJ1G-CPU Operation Manual

Cat. No. W393-E1-07

SYSMAC CJ Series

CJ1G/H-CPU䡺䡺H, CJ1G-CPU䡺䡺P
CJ1M-CPU䡺䡺, CJ1G-CPU䡺䡺

OPERATION MANUAL

Programmable Controllers

SYSMAC CJ Series

CJ1G/H-CPU@@H, CJ1G-CPU@@P,
CJ1M-CPU@@

, CJ1G-CPU@@

Programmable Controllers

Operation Manual

Revised July 2004

Certain Terms and Conditions of Sale

1. Offer; Acceptance. These terms and conditions (these "Terms") are deemed
part of all catalogs, manuals or other documents, whether electronic or in writ­ing, relating to the sale of goods or services (collectively, the "Goods
Omron Electronics LLC and its subsidiary companies ("Seller
objects to any terms or conditions proposed in Buyer's purchase order or other
documents which are inconsistent with, or in addition to, these Terms. Please
contact your Omron representative to confirm any additional terms for sales
from your Omron company.

2. Prices.

3. Discounts.

4. Orders.

5. Governmental Approvals.

6. Taxes.

7. Financial.

8. Cancellation; Etc.

9. Force Majeure.

10. Shipping; Delivery. Unless otherwise expressly agreed in writing by Seller:

11. Claims.

All prices stated are current, subject to change without notice by

Seller. Buyer agrees to pay the price in effect at time of shipment.

invoices sent to Buyer after deducting transportation charges, taxes and
duties, and will be allowed only if (i) the invoice is paid according to Seller's
payment terms and (ii) Buyer has no past due amounts owing to Seller.

costs involved in, obtaining any government approvals required for the impor­tation or sale of the Goods.

real property and income taxes), including any interest or penalties thereon,
imposed directly or indirectly on Seller or required to be collected directly or
indirectly by Seller for the manufacture, production, sale, delivery, importation,
consumption or use of the Goods sold hereunder (including customs duties
and sales, excise, use, turnover and license taxes) shall be charged to and
remitted by Buyer to Seller.

to Seller, Seller reserves the right to stop shipments or require satisfactory
security or payment in advance. If Buyer fails to make payment or otherwise
comply with these Terms or any related agreement, Seller may (without liability
and in addition to other remedies) cancel any unshipped portion of Goods sold
hereunder and stop any Goods in transit until Buyer pays all amounts, includ­ing amounts payable hereunder, whether or not then due, which are owing to it
by Buyer. Buyer shall in any event remain liable for all unpaid accounts.

unless Buyer indemnifies Seller fully against all costs or expenses arising in
connection therewith.

resulting from causes beyond its control, including earthquakes, fires, floods,
strikes or other labor disputes, shortage of labor or materials, accidents to
machinery, acts of sabotage, riots, delay in or lack of transportation or the
requirements of any government authority.

a. Shipments shall be by a carrier selected by Seller;
b. Such carrier shall act as the agent of Buyer and delivery to such carrier

c. All sales and shipments of Goods shall be FOB shipping point (unless oth-

d. Delivery and shipping dates are estimates only.
e. Seller will package Goods as it deems proper for protection against normal

Goods occurring before delivery to the carrier must be presented in writing to
Seller within 30 days of receipt of shipment and include the original transporta­tion bill signed by the carrier noting that the carrier received the Goods from
Seller in the condition claimed.

Cash discounts, if any, will apply only on the net amount of

Seller will accept no order less than $200 net billing.

All taxes, duties and other governmental charges (other than general

If the financial position of Buyer at any time becomes unsatisfactory

Seller shall not be liable for any delay or failure in delivery

shall constitute delivery to Buyer;

erwise stated in writing by Seller), at which point title to and all risk of loss of
the Goods shall pass from Seller to Buyer, provided that Seller shall retain a
security interest in the Goods until the full purchase price is paid by Buyer;

handling and extra charges apply to special conditions.

Any claim by Buyer against Seller for shortage or damage to the

Buyer shall be responsible for, and shall bear all

Orders are not subject to rescheduling or cancellation

"). Seller hereby

") by

12. Warranties.
Goods will be free from defects in materials and workmanship for a period of
twelve months from the date of sale by Seller (or such other period expressed
in writing by Seller). Seller disclaims all other warranties, express or implied.
(b) Limitations.
EXPRESS OR IMPLIED, ABOUT NON-INFRINGEMENT, MERCHANTABIL­ITY OR FITNESS FOR A PARTICULAR PURPOSE OF THE GOODS.
BUYER ACKNOWLEDGES THAT IT ALONE HAS DETERMINED THAT THE
GOODS WILL SUITABLY MEET THE REQUIREMENTS OF THEIR
INTENDED USE. Seller further disclaims all warranties and responsibility of
any type for claims or expenses based on infringement by the Goods or other­wise of any intellectual property right. (c) Buyer Remedy.
tion hereunder shall be to replace (in the form originally shipped with Buyer
responsible for labor charges for removal or replacement thereof) the non­complying Good or, at Seller's election, to repay or credit Buyer an amount
equal to the purchase price of the Good; provided that in no event shall Seller
be responsible for warranty, repair, indemnity or any other claims or expenses
regarding the Goods unless Seller's analysis confirms that the Goods were
properly handled, stored, installed and maintained and not subject to contami­nation, abuse, misuse or inappropriate modification. Return of any goods by
Buyer must be approved in writing by Seller before shipment. Seller shall not
be liable for the suitability or unsuitability or the results from the use of Goods
in combination with any electrical or electronic components, circuits, system
assemblies or any other materials or substances or environments. Any
advice, recommendations or information given orally or in writing, are not to be
construed as an amendment or addition to the above warranty.

13. Damage Limits; Etc.
RECT OR CONSEQUENTIAL DAMAGES, LOSS OF PROFITS OR PRODUC­TION OR COMMERCIAL LOSS IN ANY WAY CONNECTED WITH THE
GOODS, WHETHER SUCH CLAIM IS BASED IN CONTRACT, WARRANTY,
NEGLIGENCE OR STRICT LIABILITY. Further, in no event shall liability of
Seller exceed the individual price of the Good on which liability is asserted.

14. Indemnities.
its employees from and against all liabilities, losses, claims, costs and
expenses (including attorney's fees and expenses) related to any claim, inves­tigation, litigation or proceeding (whether or not Seller is a party) which arises
or is alleged to arise from Buyer's acts or omissions under these Terms or in
any way with respect to the Goods. Without limiting the foregoing, Buyer (at
its own expense) shall indemnify and hold harmless Seller and defend or settle
any action brought against Seller to the extent that it is based on a claim that
any Good made to Buyer specifications infringed intellectual property rights of
another party.

15. Property; Confidentiality.
the exclusive property of Seller and its affiliates and Buyer shall not attempt to
duplicate it in any way without the written permission of Seller. Notwithstand­ing any charges to Buyer for engineering or tooling, all engineering and tooling
shall remain the exclusive property of Seller. All information and materials
supplied by Seller to Buyer relating to the Goods are confidential and propri­etary, and Buyer shall limit distribution thereof to its trusted employees and
strictly prevent disclosure to any third party.

16. Miscellaneous.
and no course of dealing between Buyer and Seller shall operate as a waiver
of rights by Seller. (b) Assignment.
without Seller's written consent. (c) Amendment.
entire agreement between Buyer and Seller relating to the Goods, and no pro­vision may be changed or waived unless in writing signed by the parties.
(d) Severability.
provision shall not invalidate any other provision. (e) Setoff.
no right to set off any amounts against the amount owing in respect of this
invoice. (f) As used herein, "including

(a) Exclusive Warranty. Seller's exclusive warranty is that the

SELLER MAKES NO WARRANTY OR REPRESENTATION,

Seller's sole obliga-

SELLER SHALL NOT BE LIABLE FOR SPECIAL, INDI-

Buyer shall indemnify and hold harmless Seller, its affiliates and

The intellectual property embodied in the Goods is

(a) Waiver. No failure or delay by Seller in exercising any right

Buyer may not assign its rights hereunder

If any provision hereof is rendered ineffective or invalid, such

" means "including without limitation".

These Terms constitute the

Buyer shall have

Certain Precautions on Specifications and Use

1. Suitability of Use. Seller shall not be responsible for conformity with any stan­dards, codes or regulations which apply to the combination of the Good in the
Buyer's application or use of the Good. At Buyer's request, Seller will provide
applicable third party certification documents identifying ratings and limitations
of use which apply to the Good. This information by itself is not sufficient for a
complete determination of the suitability of the Good 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 this Good,
nor is it intended to imply that the uses listed may be suitable for this Good:
(i) Outdoor use, uses involving potential chemical contamination or electrical

interference, or conditions or uses not described in this document.

(ii) 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.

(iii) Systems, machines and equipment that could present a risk to life or

property. Please know and observe all prohibitions of use applicable to

this Good.
NEVER USE THE PRODUCT FOR AN APPLICATION INVOLVING SERIOUS
RISK TO LIFE OR PROPERTY WITHOUT ENSURING THAT THE SYSTEM
AS A WHOLE HAS BEEN DESIGNED TO ADDRESS THE RISKS, AND THAT
THE SELLER'S PRODUCT IS PROPERLY RATED AND INSTALLED FOR
THE INTENDED USE WITHIN THE OVERALL EQUIPMENT OR SYSTEM.

2. Programmable Products.
gramming of a programmable Good, or any consequence thereof.

3. Performance Data.
guide for the user in determining suitability and does not constitute a warranty.
It may represent the result of Seller's test conditions, and the user must corre­late it to actual application requirements. Actual performance is subject to the
Seller's Warranty and Limitations of Liability.

4. Change in Specifications.
changed at any time based on improvements and other reasons. It is our prac­tice to change part numbers when published ratings or features are changed,
or when significant construction changes are made. However, some specifica­tions of the Good may be changed without any notice. When in doubt, special
part numbers may be assigned to fix or establish key specifications for your
application. Please consult with your Seller's representative at any time to con­firm actual specifications of purchased Good.

5. Errors and Omissions.
checked and is believed to be accurate; however, no responsibility is assumed
for clerical, typographical or proofreading errors, or omissions.

Seller shall not be responsible for the user's pro-

Performance data given in this catalog is provided as a

Product specifications and accessories may be

The information in this catalog has been carefully

Notice:

r
f

OMRON products are manufactured for use according to proper procedures
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.

!WARNING Indicates a potentially hazardous situation which, if not avoided, could result in death or

serious injury.

!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

© OMRON, 2001

All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form, o
by any means, mechanical, electronic, photocopying, recording, or otherwise, without the prior written permission o
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.

The following headings appear in the left column of the manual to help you
locate different types of information.

Note Indicates information of particular interest for efficient and convenient opera-

tion of the product.

1,2,3... 1. Indicates lists of one sort or another, such as procedures, checklists, etc.

v

Unit Versions of CS/CJ-series CPU Units

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

CS/CJ-series CPU Unit

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.

Product nameplate

CS1H-CPU67H

CPU UNIT

Lot No.

Lot No. 040715 0000 Ver.3.0

OMRON Corporat ion MADE IN JAPA N

Unit version
Example for Unit version 3.0

• CS1-H, CJ1-H, and CJ1M CPU Units (except for low-end models) manu­factured on or before November 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.

vi

Unit version

Use the above display to confirm the unit version of the CPU Unit.

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.

vii

Unit version

Use the above display to confirm the unit version of the CPU Unit connected
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.

viii

Unit Version Notation

In this manual, the unit version of a CPU Unit is given as shown in the follow­ing table.

Product nameplate

Meaning

Designating individual
CPU Units (e.g., the
CS1H-CPU67H)

Designating groups of
CPU Units (e.g., the
CS1-H CPU Units)

Designating an entire
series of CPU Units
(e.g., the CS-series CPU
Units)

CPU Units on which no unit version is

given

Lot No. XXXXXX XXXX

OMRON Corporation MADE IN JAPAN

Pre-Ver. 2.0 CS1-H CPU Units CS1H-CPU67H CPU Unit Ver. @.@

Pre-Ver. 2.0 CS1-H CPU Units CS1-H CPU Units Ver. @.@

Pre-Ver. 2.0 CS-series CPU Units CS-series CPU Units Ver. @.@

Units on which a version is given

Lot No. XXXXXX XXXX

(Ver. @.@)

Ver. @ @ .@

ix

Unit Versions and Lot Numbers

Series Model Data of manufacture

Earlier Sept. 2003 Oct. 2003 Nov. 2003 Dec. 2003 Jun. 2004 Later

CS
Series

CS1 CPU Units CS1@-

CPU@@

No unit version

CJ
Series

CS1-V1 CPU
Units

CS1-H CPU Units CS1@-

CS1D
CPU
Units

CJ1 CPU Units CJ1G-

CJ1-H CPU Units CJ1@-

CJ1M CPU Units
except low-end
models

CPU
Units for
Duplex­CPU
System

CPU
Units for
Single­CPU
System

CS1@-
CPU@@-V1

CPU@@H

CS1D­CPU@@H

CS1D­CPU@@S

CPU@@

CPU@@H

CJ1M­CPU@@

No unit version

Pre-Ver. 2.0 CPU Units

Pre-Ver. 1.1 CPU Units

Pre-Ver. 2.0 CPU Units

Pre-Ver. 2.0 CPU Units

Pre-Ver. 2.0 CPU Units

CPU Units Ver. 2.0
(Lot No.: 031105 on)

CPU Units Ver.1.1
(Lot No.: 031120 on)

CPU Units Ver. 2.0
(Lot No.: 031215 on)

CPU Units Ver. 2.0
(Lot No.: 031105 on)

CPU Units Ver. 2.0
(Lot No.: 031105 on)

CPU Units Ver.

3.0 (Lot No.:
040622 on)

CPU Units Ver.

3.0 (Lot No.:
040623 on)

CPU Units Ver.

3.0 (Lot No.:
040624 on)

Sup­port
Soft­ware

x

CJ1M CPU Units,
low-end models

CX-Programmer WS02-

CJ1M­CPU11/21

CXPC1­EV@

Unit Ver. 2.0
(Lot No.: 031002 on)

Ver.3.2 Ver.3.3 Ver.4.0 Ve r.5 .0

CPU Units Ver.

3.0 (Lot No.:
040629 on)

Function Support by Unit Version

CJ1-H/CJ1M CPU Units

Function CJ1-H CPU Units

(CJ1@-CPU@@H)

Pre-Ver. 2.0

CPU Units

Downloading and Uploading
Individual Tasks

Improved Read Protection
Using Passwords

Write Protection from FINS
Commands Sent to CPU Units
via Networks

Online Network Connections
without I/O Tables

Communications through a
Maximum of 8 Network Levels

Connecting Online to PLCs via
NS-series PTs

Setting First Slot Words --- OK --- OK OK
Automatic Transfers at Power

ON without a Parameter File
Automatic Detection of I/O Allo-

cation Method for Automatic
Transfer at Power ON

Operation Start/End Times --- OK --- OK OK
New

Applica­tion
Instruc­tions

MILH, MILR, MILC --- OK --- OK OK
=DT, <>DT, <DT,

<=DT, >DT, >=DT
BCMP2 --- OK OK OK OK
GRY OK from lot

TPO --- OK --- OK OK
DSW, TKY, HKY,

MTR, 7SEG
EXPLT, EGATR,

ESATR, ECHRD,
ECHWR

Reading/Writing
CPU Bus Units with
IORD/IOWR

PRV2 --- --- --- OK, but only for

--- OK --- OK OK

--- OK --- OK OK

--- OK --- OK OK

OK, but only if
I/O table alloca­tion at power
ON is set

OK for up to 8
groups

OK from lot
number 030201

--- OK --- OK OK

--- OK --- OK OK

--- OK --- OK OK

number 030201

--- OK --- OK OK

--- OK --- OK OK

--- OK --- OK OK

CPU Units Ver.

2.0

OK OK, but only if

I/O table alloca­tion at power
ON is set

OK for up to 64
groups

OK OK from lot

OK OK from lot

OK for up to 8
groups

number 030201

number 030201

CJ1M CPU Units,

except low-end models

(CJ1M-CPU@@)

Pre-Ver. 2.0

CPU Units

CPU Units Ver.

OK OK

OK for up to 64
groups

OK OK

OK OK

models with
built-in I/O

2.0

CJ1M CPU

Units, low-end

models

(CJ1M-

CPU11/21)

CPU Units Ver.

2.0

OK for up to 64
groups

OK, but only for
models with
built-in I/O

xi

Functions Supported by Unit Version 3.0 or Later

CJ1-H/CJ1M CPU Units (CJ1@-CPU@@H, CJ1G-CPU@@P, C J 1 M - C P U @@)

Function Unit version

Pre-Ver. 2.0, Ver. 2.0 Ver. 3.0

Function blocks (supported for CX-Programmer Ver. 5.0 or higher) --- OK
Serial Gateway (converting FINS commands to CompoWay/F com-

mands at the built-in serial port)
Comment memory (in internal flash memory) --- OK
Expanded simple backup data --- OK
New Applica-

tion Instructions

Additional
instruction func­tions

TXDU(256), RXDU(255) (support no-protocol
communications with Serial Communications
Units with unit version 1.2 or later)

Model conversion instructions: XFERC(565),
DISTC(566), COLLC(567), MOVBC(568),
BCNTC(621)

Special function block instructions: GETID(286) --- OK
PRV(881) and PRV2(883) instructions: Added

high-frequency calculation methods for calculat­ing pulse frequency. (CJ1M CPU Units only)

--- OK

--- OK

--- OK

--- OK

xii

Unit Versions and Programming Devices

CX-Programmer version 4.0 or higher must be used to enable using the func­tions added for CPU Unit version 2.0.

CX-Programmer version 5.0 or higher must be used to enable using function
blocks added for CPU Unit version 3.0.

The following tables show the relationship between unit versions and CX-Pro­grammer versions.

Unit Versions and Programming Devices

CPU Unit Functions CX-Programmer Program-

CJ1M CPU Units,
low-end models,
unit Ver. 2.0

CS1-H, CJ1-H,
and CJ1M CPU
Units except low­end models, unit
Ver. 2 .0

CS1D CPU Units
for Single-CPU
Systems, unit Ver.

2.0
CS1D CPU Units

for Duplex-CPU
Systems, unit
Ver.1 .

CS/CJ-series unit
Ver. 3 .0

Functions added
for unit version

2.0
Functions added

for unit version

2.0

Functions added
for unit version

2.0

Functions added
for unit version

1.1

Function block
functions added
for unit version

3.0

Ver. 3.2

or lower

Using new functions --- --- OK OK No
Not using new functions --- OK OK OK

Using new functions --- --- OK OK
Not using new functions OK OK OK OK

Using new functions --- --- OK OK
Not using new functions OK

Using new functions --- --- OK OK
Not using new functions OK OK OK OK

Using function blocks --- --- --- OK
Not using function blocks OK OK OK OK

Ver. 3.3 Ver. 4.0 Ver. 5.0

or higher

ming Con-

sole

restrictions

Note As shown above, there is no need to upgrade to CX-Programmer version 4.0

as long as the functions added for unit version 2.0 or unit version 1.1 are not
used.

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.

Series CPU Unit group CPU Unit model Device type setting on

CS Series CS1-H CPU Units

CS1D CPU Units for Duplex-CPU Systems
CS1D CPU Units for Single-CPU Systems

CJ Series CJ1-H CPU Units

CJ1M CPU Units

CS1G-CPU@@H CS1G-H

CS1H-CPU@@H CS1H-H

CS1D-CPU@@H CS1D-H (or CS1H-H)
CS1D-CPU@@S CS1D-S
CJ1G-CPU@@H CJ1G-H

CJ1H-CPU@@H CJ1H-H

CJ1M-CPU@@ CJ1M

CX-Programmer Ver. 4.0 or higher

xiii

Troubleshooting Problems with Unit Versions on the CX-Programmer

Problem Cause Solution

After the above message is displayed, a compiling
error will be displayed on the Compile Tab Page in the
Output Window.

“????” is displayed in a program transferred from the
PLC to the CX-Programmer.

An attempt was made using CX­Programmer version 4.0 or higher
to download a program contain­ing instructions supported only by
CPU Units Ver. 2.0 or later to a
Pre-Ver. 2.0 CPU Units.

An attempt was made using CX­Programmer version 4.0 or higher
to download a PLC Setup con­taining settings supported only by
CPU Units Ver. 2.0 or later (i.e.,
not set to their default values) to a
Pre-Ver. 2.0 CPU Units.

CX-Programmer version 3.3 or
lower was used to upload a pro­gram containing instructions sup­ported only by CPU Units Ver. 2.0
or later from a CPU Unit Ver. 2.0
or later.

Check the program or change
the CPU Unit being down­loaded to a CPU Unit Ver. 2.0
or later.

Check the settings in the PLC
Setup or change the CPU Unit
being downloaded to a CPU
Unit Ver. 2.0 or later.

The new instructions cannot
be uploaded using CX-Pro­grammer version 3.3 or lower.
Use CX-Programmer version

4.0 or higher.

xiv

Loop-control CPU Units

Overview Loop-control CPU Units are CPU Units with a pre-installed Loop Controller

functional element.

Note The Loop Controller functional element is an inseparable part of the CPU Unit

and cannot be removed.

Model Numbers,
Functional Elements,
and Versions

Product name Product model

Loop-control
CPU Units

number

CJ1G-CPU42P CJ1G-CPU42H Ver. 3.0 or higher LCB01 Ver. 2.0
CJ1G-CPU43P CJ1G-CPU43H Ver. 3.0 or higher LCB03 Ver. 2.0
CJ1G-CPU44P CJ1G-CPU44H Ver. 3.0 or higher LCB03 Ver. 2.0
CJ1G-CPU45P CJ1G-CPU45H Ver. 3.0 or higher LCB03 Ver. 2.0

Note A single unit version for the Loop-control CPU Unit as a whole is not provided.

Differences between
CJ1G-CPU@@H and
CPU Unit Elements

Note The functions added in the version upgrade for unit version 3.0 and later are

The CJ1G-CPU@@P Loop-control CPU Unit is comprised of a CPU Unit ele­ment with the same functionality as a CJ1G-CPU@@H CPU Unit with version

3.0 or later (see note) and a Loop Controller element. The following table lists
the model numbers for CJ1G Loop-control CPU Units, the types of CPU Unit
element, Loop Controller element, and the functional element version codes.

Configuration

CPU Unit element Loop Controller element

CPU Unit model

with same function-

ality

Functional ele-

ment unit ver-

sion

Functional ele-

ment name

Functional ele-

ment version

The unit versions for the CJ1-H CPU Unit with unit version 3.0 or later and the
functional element version code.

The differences between the CPU Unit element in the Loop-control CPU Unit
and the CJ1G-CPU@@H CPU Unit are shown here. The two types of CPU
Unit are otherwise the same.

also the same.

Additional Auxiliary Area
Flags and Bits

Loop-control CPU Units can use the following Auxiliary Area flags and bits,
which are not supported for CJ1G-CPU@@H CPU Units.

Address Name

Word Bit

A424 00 Inner Board WDT Error Flag (fatal error)

01 Inner Board Bus Error Flag (fatal error)
02 Cyclic Monitor Error Flag (fatal error)
03 Flash Memory Data Error Flag (fatal error)
04 Incompatible CPU Unit Error Flag (non-fatal error)
08 Loop Controller High Load Flag (non-fatal error)
11 Backup Data (Flash Memory) Error Flag

12 Specified EM Bank Unusable Error Flag
A608 00 Inner Board Restart Bit
A609 01 Start Mode at Power ON: Hot Start
A609 02 Start Mode at Power ON: Cold Start

For details on the Auxiliary Area bits and flags, refer to the section on SYS-

MAC CS/CJ Series Loop Control Boards, Process-control CPU Units, Loop­control CPU Units Operation Manual (W406).

xv

Loop-control CPU Unit
Dimensions

Product name and model W

CJ1G-CPU45P/44P/43P/42P
Loop-control CPU Unit

CJ1G-CPU45H/44H/43H/42H
CJ1-H CPU Unit (reference)

2.7

(mm)H(mm)

D (mm)

69 90 65 (not including connector)

73.9 (including connector)

62

Indicators

LCB03

EXEC

RDY

65

90

2.7

SYSMAC
CJ1G-CPU44P

PROGRAMMABLE
CONTROLLER

OPEN

MCPWR

BUSY

RUN

ERR/ALM

INH
PRPHL
COMM

PERIPHERAL

PORT

INNER LOOP CONTROLLER

69 73.9

RDY

EXEC

Indicator Name Color Status Description

RDY Ready Green Not lit The Loop Control Board is not operating for one of the fol-

lowing reasons:

• A Fatal Inner Board Error occurred (A40112 ON.)

• Initialization is not completed yet.

• A fatal error occurred.

• The flash memory backup data is invalid.

• The Loop Control Board is initializing.

• A hardware failure occurred in the Loop Control Board.

• Power is not being supplied from the Power Supply Unit.

• A Loop Control Board WDT error occurred.
Flashing • A WDT error occurred in the CPU Unit.
Lit The Loop Control Board is ready for operation.

xvi

Indicator Name Color Status Description

EXEC Running Green Not lit The system is stopped for one of the following reasons:

Current Consumption and
Weight

Common Processing Time
(Overhead Time)

• The Loop Control Board is initializing.

• A hardware failure occurred in the Loop Control Board.

• Power is not being supplied from the Power Supply Unit.

• A Loop Control Board WDT error occurred.

• The Loop Control Board is not running.

• Data is being written to flash memory.

Flashing
(at 0.5-s
intervals)

Flashing
(0.2-s
intervals)

Lit The Loop Control Board is not running.

Product name and model Current consumption Weight

CJ1G-CPU45P/44P/43P/42P
Loop-control CPU Unit

CJ1G-CPU45H/44H/43H/42H
CJ1-H CPU Unit (reference)

Product name and model Common processing time

CJ1G-CPU45P/44P/43P/42P
Loop-control CPU Unit

CJ1G-CPU45H/44H/43H/42H
CJ1-H CPU Unit (reference)

Erasing flash memory.

Backup operation to function block flash memory in
progress

1.06 A 220 g max.

0.91 A 190 g max.

0.8 ms max.

0.3 ms

Battery Backup Time At 25

whether or not power is supplied to the CPU Unit while the battery is installed.
This is the same as for CJ1G-CPU@@H CPU Units. The following table shows
the approximate minimum lifetimes and typical lifetimes for the backup battery
(total time with power not supplied).

CJ1G-CPU45P/44P/43P/42P
Loop-control CPU Unit

CJ1G-CPU45H/44H/43H/42H
CJ1-H CPU Unit (reference)

Note The minimum lifetime is the memory backup time at an ambient temperature

of 55
ature of 25

°C, the battery life (maximum service life) for batteries is five years

Model Approx.

maximum

lifetime

5 years 5,600 hours

5 years 6,500 hours

Approx.

minimum

lifetime

(See note.)

(approximately

0.64 years)

(approximately

0.75 years)

Typ ical lifetime

(See note.)

43,000 hours
(approximately 5
years)

43,000 hours
(approximately 5
years)

°C. The typical lifetime is the memory backup time at an ambient temper-

°C.

xvii

Programming Devices

Loop Controller Element Using CX-Process Tool Ver. 4.0 or later, select the Loop-control CPU

Unit/Process-control CPU Unit from the LC Type field in the LCB/LC001 Dia-
log Box. Then select either CJ1G-CPU42P, CJ1G-CPU43P, CJ1G-CPU44P,
orCJ1G-CPU45P, from the Number-Model pull-down list in the Unit Informa-
tion field.

CPU Unit Element Use CX-Programmer Ver. 5.0 or later. The CPU Unit functions are the same

as the CJ1G-CPU@@H, except for the differences provided in the previous
table. Therefore, select CJ1G-H as the device type when using CX-Program­mer.

1,2,3... 1. Select New from the File Menu.

2. Select one of the following CPU Unit types in the Change PLC Dialog Box.

Loop-control CPU Unit Device type CPU Unit type

CJ1G-CPU42P CJ1G-H CPU42
CJ1G-CPU43P CPU43
CJ1G-CPU44P CPU44
CJ1G-CPU45P CPU45

Reference Manuals • The CPU Unit functions are the same as the CJ1G-CPU@@H, except for

the differences provided in the previous table. Therefore, for details on the
CPU Unit functions, refer to the SYSMAC CJ Series Programmable Con-

trollers Operation Manual (W393), SYSMAC CS/CJ Series Programmable
Controllers Programming Manual (W394), SYSMAC CS/CJ Series Pro­grammable Controllers Instructions Reference Manual (W340), and Com­munications Commands Reference Manual (W342).

• For details on the Loop Controller functions (LCB@@ functional element)

refer to the section on SYSMAC CS/CJ Series Loop Control Boards, Pro-

cess-control CPU Units, Loop-control CPU Units Operation Manual

(W406).

xviii

TABLE OF CONTENTS

PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv

1 Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi

2 General Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi

3 Safety Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi

4 Operating Environment Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxviii

5 Application Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxix

6 Conformance to EC Directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxii

SECTION 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1-1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

1-2 CJ-series Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1-3 CJ1-H and CJ1M CPU Unit Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

1-4 CJ1-H/CJ1M CPU Unit Ver. 3.0 Upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

1-5 CJ1-H/CJ1M CPU Unit Ver. 2.0 Upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

1-6 CJ1 and CJ1-H CPU Unit Comparison. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

1-7 Function Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

1-8 CJ1-H Functions Arranged by Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

1-9 CJ1M Functions Arranged by Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

1-10 Comparison to CS-series PLCs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

SECTION 2

Specifications and System Configuration. . . . . . . . . . . . . . . 77

2-1 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

2-2 CPU Unit Components and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

2-3 Basic System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

2-4 I/O Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

2-5 Expanded System Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

2-6 Unit Current Consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

2-7 CPU Bus Unit Setting Area Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

2-8 I/O Table Settings List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

SECTION 3

Nomenclature, Functions, and Dimensions . . . . . . . . . . . . . 135

3-1 CPU Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

3-2 File Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

3-3 Programming Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153

3-4 Power Supply Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

3-5 I/O Control Units and I/O Interface Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

3-6 CJ-series Basic I/O Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

3-7 B7A Interface Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

xix

TABLE OF CONTENTS

SECTION 4

Operating Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

4-1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

4-2 Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

SECTION 5

Installation and Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

5-1 Fail-safe Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

5-2 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

5-3 Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

SECTION 6

DIP Switch Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

6-1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

6-2 Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

SECTION 7

PLC Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

7-1 PLC Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

7-2 Explanations of PLC Setup Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305

SECTION 8

I/O Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315

8-1 I/O Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316

8-2 Creating I/O Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

8-3 Reserving I/O Words for Expected Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326

8-4 Allocating First Words to Racks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

8-5 Allocating First Words to Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

8-6 Detailed Information on I/O Table Creation Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

8-7 Data Exchange with CPU Bus Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

SECTION 9

Memory Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339

9-1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340

9-2 I/O Memory Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341

9-3 I/O Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349

9-4 Data Link Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355

9-5 CPU Bus Unit Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356

9-6 Special I/O Unit Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358

9-7 Serial PLC Link Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359

9-8 DeviceNet Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360

xx

TABLE OF CONTENTS

9-9 Internal I/O Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361

9-10 Holding Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362

9-11 Auxiliary Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363

9-12 TR (Temporary Relay) Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391

9-13 Timer Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392

9-14 Counter Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394

9-15 Data Memory (DM) Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394

9-16 Extended Data Memory (EM) Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396

9-17 Index Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397

9-18 Data Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403

9-19 Task Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404

9-20 Condition Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405

9-21 Clock Pulses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407

9-22 Parameter Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408

SECTION 10

CPU Unit Operation and the Cycle Time. . . . . . . . . . . . . . . 411

10-1 CPU Unit Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413

10-2 CPU Unit Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417

10-3 Power OFF Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419

10-4 Computing the Cycle Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424

10-5 Instruction Execution Times and Number of Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437

SECTION 11

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473

11-1 Error Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474

11-2 Error Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475

11-3 Troubleshooting Racks and Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497

SECTION 12

Inspection and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . 501

12-1 Inspections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502

12-2 Replacing User-serviceable Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504

Appendices

A Specifications of Basic I/O Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509

B CJ1M CPU Unit Built-in I/O Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565

C Auxiliary Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569

D Memory Map of PLC Memory Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613

E PLC Setup Coding Sheets for Programming Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615

F Connecting to the RS-232C Port on the CPU Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631

G CJ1W-CIF11 RS-422A Converter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641

xxi

TABLE OF CONTENTS

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647

Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657

xxii

About this Manual:

This manual describes the installation and operation of the CJ-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 table.

Unit CS Series CJ Series

CPU Units CS1-H CPU Units: CS1H-CPU@@H

CS1 CPU Units: CS1H-CPU@@-EV1

CS1D CPU Units:
CS1D CPU Units for Duplex-CPU System:
CS1D-CPU@@H
CS1D CPU Units for Single-CPU System:
CS1D-CPU@@S
CS1D Process CPU Units:
CS1D-CPU@@P

Basic I/O Units CS-series Basic I/O Units CJ-series Basic I/O Units
Special I/O Units CS-series Special I/O Units CJ-series Special I/O Units
CPU Bus Units CS-series CPU Bus Units CJ-series CPU Bus Units
Power Supply Units CS-series Power Supply Units CJ-series Power Supply Units

CS1G-CPU@@H

CS1G-CPU@@-EV1

CJ1-H CPU Units: CJ1H-CPU@@H

CJ1G-CPU@@H
CJ1G-CPU@@P

CJ1 CPU Units: CJ1G-CPU@@-EV1
CJ1M CPU Units: CJ1M-CPU@@

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 CJ-series CPU Units CPU Units in a PLC
System.

Name Cat. No. Contents

SYSMAC CJ Series
CJ1G-CPU@@, CJ1M-CPU@@, CJ1G-CPU@@P,
CJ1G/H-CPU@@H
Programmable Controllers Operation Manual

SYSMAC CS/CJ Series
CS1G/H-CPU@@-EV1, CS1G/H-CPU@@H,
CS1D-CPU@@H, CS1D-CPU@@S, CJ1G-CPU@@,
CJ1M-CPU@@, CJ1G-CPU@@P, CJ1G/H-CPU@@H
Programmable Controllers Programming Manual

SYSMAC CJ Series
CJ1M-CPU21/22/23
Built-in I/O Operation Manual

SYSMAC CS/CJ Series
CS1G/H-CPU@@-EV1, CS1G/H-CPU@@H,
CS1D-CPU@@H, CS1D-CPU@@S, CJ1G-CPU@@,
CJ1M-CPU
Programmable Controllers Instructions Reference Manual

SYSMAC CS/CJ Series
CQM1H-PRO01-E, C200H-PRO27-E, CQM1-PRO01-E
Programming Consoles Operation Manual

@@, CJ1G-CPU@@P, CJ1G/H-CPU

@@H

W393 Provides an outlines of and describes the design,

installation, maintenance, and other basic opera­tions for the CJ-series PLCs. (This manual)

W394 This manual describes programming and other

methods to use the functions of the CS/CJ-series
PLCs.

W395 Describes the functions of the built-in I/O for

CJ1M CPU Units.

W340 Describes the ladder diagram programming

instructions supported by CS/CJ-series PLCs.

W341 Provides information on how to program and

operate CS/CJ-series PLCs using a Programming
Console.

xxiii

Name Cat. No. Contents

SYSMAC CS/CJ Series
CS1G/H-CPU@@-EV1, CS1G/H-CPU@@H,
CS1D-CPU@@H, CS1D-CPU@@S, CJ1G-CPU@@,
CJ1M-CPU@@, CJ1G-CPU@@P, CJ1G/H-CPU@@H,
CS1W-SCB21-V1/41-V1, CS1W-SCU21-V1,
CJ1W-SCU21-V1/41-V1
Communications Commands Reference Manual

SYSMAC WS02-CXP@@-E
CX-Programmer Operation Manual Version 3.@

SYSMAC WS02-CXP@@-E
CX-Programmer Operation Manual Version 4.@

SYSMAC WS02-CXP@@-E
CX-Programmer Operation Manual Version 5.@

SYSMAC WS02-CXP@@-E
CX-Programmer Operation Manual Function Blocks

SYSMAC CS/CJ Series
CS1W-SCB21-V1/41-V1, CS1W-SCU21-V1,
CJ1W-SCU21-V1/41-V1
Serial Communications Boards/Units Operation Manual

SYSMAC WS02-PSTC1-E
CX-Protocol Operation Manual

W342 Describes the C-series (Host Link) and FINS

communications commands used with CS/CJ­series PLCs.

W414 Provide information on how to use the CX-Pro-

grammer, a programming device that supports the

W425

W437

W438 Describes specifications and operation methods

W336 Describes the use of Serial Communications Unit

W344 Describes the use of the CX-Protocol to create

CS/CJ-series PLCs, and the CX-Net contained
within CX-Programmer.

related to function blocks. This information is
required only when using function blocks with the
combination of CX-Programmer Ver. 5.0 and
CS1-H/CJ1-H/CJ1M CPU Unit Ver. 3.0. Refer to

CX-Programmer Operation Manual Version 5.@
(W437) for details on other operations for CX-Pro-

grammer Ver. 5.0.

and Boards to perform serial communications
with external devices, including the usage of stan­dard system protocols for OMRON products.

protocol macros as communications sequences
to communicate with external devices.

This manual contains the following sections.

Section 1 introduces the special features and functions of the CJ-series PLCs and describes the dif­ferences between these PLCs and the earlier CS-series and C200HX/HG/HE PLCs.

Section 2 provides tables of standard models, Unit specifications, system configurations, and a com­parison between different Units.

Section 3 provides names of Unit components and their functions. Dimensions are also provided.

Section 4 outlines the steps required to assemble and operate a CJ PLC system.

Section 5 describes how to install a PLC System, including mounting and wiring Units. Follow instruc-

tions carefully. Improper installation can cause the PLC to malfunction, resulting in very dangerous sit­uations.

Section 6 describes DIP switch settings.

Section 7 describes initial hardware and software settings in the PLC Setup.

Section 8 describes I/O allocation to Basic I/O Units, Special I/O Units, and CPU Bus Units, as well as

and data exchange with CPU Bus Units.

Section 9 describes the structure and functions of the I/O Memory Areas and Parameter Areas.

Section 10 describes the internal operation of CPU Units and the cycle used for internal processing.

Section 11 provides information on hardware and software errors that occur during PLC operation.

Section 12 provides information on hardware maintenance and inspections.

The Appendices provide Unit specifications, current/power consumptions, Auxiliary Area words and
bits, internal I/O addresses, and PLC Setup settings, and information on RS-232C ports,.

xxiv

PRECAUTIONS

This section provides general precautions for using the CJ-series Programmable Controllers (PLCs) and related devices.

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

2 General Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi

3 Safety Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi

4 Operating Environment Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxviii

5 Application Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix

6 Conformance to EC Directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxii

6-1 Applicable Directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxii

6-2 Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxii

6-3 Conformance to EC Directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxiii

6-4 Relay Output Noise Reduction Methods . . . . . . . . . . . . . . . . . . . . . xxxiii

xxv

Intended Audience 1

1 Intended Audience

This manual is intended for the following personnel, who must also have
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

xxvi

so may result in electric shock.

Safety Precautions 3

!WARNING Do not touch any of the terminals or terminal blocks while the power is being

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.
As a countermeasure for 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
Programming Device. Otherwise, the devices connected to the output unit
may malfunction 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.

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

xxvii

Operating Environment Precautions 4

!Caution A CJ1-H or CJ1M CPU Unit automatically back up the user program 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 written to
flash memory. The DM, EM, and HR Areas can be held during power interrup­tions 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 inappropriate 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 con­tents 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 Bat­tery Error Flag (A40204) turns ON, such as resetting the data in these areas.

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.

• Locations close to power supplies.

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

xxviii

Application Precautions 5

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.

!WARNING Always heed these precautions. Failure to abide by the following precautions

could lead to serious or possibly fatal injury.

• Always connect to a ground of 100
connecting to a ground of 100

• A ground of 100
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, 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.

• A CJ-series CPU Unit is shipped with the battery installed and the time
already set on the internal clock. It is not necessary to clear memory or
set the clock before application, as it is for the CS-series CPU Units.

• The user program and parameter area data in CJ1-H/CJ1M CPU Units is
backed up in the internal 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 CJ-series 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.

Ω or less must be installed when shorting the GR and LG

Ω or less when installing the Units. Not

Ω or less may result in electric shock.

xxix

Application Precautions 5

• 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
output terminals on DC Output Units and other Units will momentarily turn
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.

• Always use the power supply voltages specified in the operation manuals.
An incorrect voltage may result in malfunction or burning.

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

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

• Separate the line ground terminal (LG) from the functional ground termi­nal (GR) on the Power Supply Unit before performing withstand voltage
tests or insulation resistance tests. Not doing so may result in burning.

• Install the Units properly as specified in the operation manuals. Improper
installation of the Units may result in malfunction.

xxx

Application Precautions 5

• Be sure that all the terminal screws, and cable connector screws are tight­ened 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.

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

• Do not connect pin 6 (+5 V power supply line) of the RS-232C port on the
CPU Unit to any external device except the CJ1W-CIF11 RS-422A
Adapter or NT-AL001 RS-232C/RS-422A Adapter. Doing so may damage
the external device or CPU Unit.

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

xxxi

Conformance to EC Directives 6

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

• After connecting Power Supply Units, CPU Units, I/O Units, Special I/O
Units, or CPU Bus Units together, secure the Units by sliding the sliders at
the top and bottom of the Units until they click into place. Correct opera­tion may not be possible if the Units are not securely properly. Be sure to
attach the end cover provided with the CPU Unit to the rightmost Unit. CJ­series PLCs will not operate properly if the end cover is not attached.

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

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:

xxxii

Conformance to EC Directives 6

EMS (Electromagnetic Susceptibility): 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 CJ-series PLCs comply with EC Directives. To ensure that the machine or
device in which the CJ-series PLC is used complies with EC Directives, the
PLC must be installed as follows:

1,2,3... 1. The CJ-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. CJ-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,
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 CJ-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.

xxxiii

Conformance to EC Directives 6

a
v

r

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

CR method

Power
supply

Diode method

Power
supply

Varistor method

Power
supply

Yes Yes If the load is a relay or solenoid, there is

a time lag between the moment the cir­cuit is opened and the moment the load
is reset.

If the supply voltage is 24 or 48 V, insert

Inductive

load

the surge protector in parallel with the
load. If the supply voltage is 100 to
200 V, insert the surge protector
between the contacts.

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 converted into Joule heat by the

Inductive

load

resistance of the inductive load.
This time lag, between the moment the

circuit is opened and the moment the
load is reset, caused by this method is
longer than that caused by the CR
method.

Yes Yes The varistor method prevents the impo-

sition of high voltage between the con­tacts by using the constant voltage
characteristic of the varistor. There is
time lag between the moment the cir-

Inductive

load

cuit 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 con­tacts.

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 experi­ments, and take into consideration that
the capacitance suppresses spark dis­charge when the contacts are sepa­rated and the resistance limits 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.

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.

---

xxxiv

When switching a load with a high inrush current such as an incandescent
lamp, suppress the inrush current as shown below.

Countermeasure 1 Countermeasure 2

OUT

R

COM

Providing a dark current of

pprox. one-third of the rated

alue through an incandescent

lamp

OUT

COM

Providing a limiting resisto

R

SECTION 1

Introduction

This section introduces the special features and functions of the CJ-series PLCs and describes the differences between these
PLCs and the earlier C200HX/HG/HE PLCs.

1-1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

1-2 CJ-series Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1-2-1 Special Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

1-2-2 Versatile Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1-3 CJ1-H and CJ1M CPU Unit Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

1-3-1 CJ1-H CPU Unit Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

1-3-2 High-speed Structured Programming. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

1-3-3 More Instructions for Specific Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

1-3-4 Battery-free Operation with Flash Memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

1-3-5 Better Compatibility with Other SYSMAC PLCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

1-3-6 CJ1M CPU Unit Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

1-3-7 Features of CJ1-H/CJ1M CPU Units Ver. 2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

1-3-8 Upgrades for CJ1M CPU Unit Ver. 2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

1-4 CJ1-H/CJ1M CPU Unit Ver. 3.0 Upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

1-4-1 Function Blocks (FB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

1-4-2 Serial Gateway (Converting FINS to CompoWay/F Via Serial Port). . . . . . . . . . . . . . 23

1-4-3 Comment Memory (in Internal Flash Memory). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

1-4-4 Simple Backup Data Expanded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

1-4-5 Free Running Timer (System Timer after Power ON) . . . . . . . . . . . . . . . . . . . . . . . . . 26

1-4-6 New Special Instructions and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

1-5 CJ1-H/CJ1M CPU Unit Ver. 2.0 Upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

1-5-1 Downloading and Uploading Individual Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

1-5-2 Improved Read Protection Using Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

1-5-3 Write Protection from FINS Commands Sent to CPU Units via Networks. . . . . . . . . 34

1-5-4 Online Network Connections without I/O Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

1-5-5 Communications through a Maximum of 8 Network Levels. . . . . . . . . . . . . . . . . . . . 41

1-5-6 Connecting Online to PLCs via NS-series PTs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

1-5-7 Setting First Slot Words . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

1-5-8 Automatic Transfers at Power ON without a Parameter File . . . . . . . . . . . . . . . . . . . . 46

1-5-9 Operation Start/End Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

1-5-10 Automatic Detection of I/O Allocation Method for Automatic Transfer at Power ON 48

1-5-11 New Application Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

1-6 CJ1 and CJ1-H CPU Unit Comparison. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

1-7 Function Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

1-7-1 Functions Arranged by Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

1-7-2 Communications Functions (Serial/Network) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

1-8 CJ1-H Functions Arranged by Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

1-9 CJ1M Functions Arranged by Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

1-9-1 High-speed Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

1-9-2 Controlling Pulse Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

1-9-3 Receiving Pulse Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

1-9-4 Serial PLC Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72

1-9-5 Comparison with the CJ1W-NC Pulse Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

1-10 Comparison to CS-series PLCs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

1

Overview Section 1-1

1-1 Overview

The CJ-series PLCs are very small-sized Programmable Controllers that fea­ture high speed and advanced functions with the same architecture as the
CS-series PLCs.

• Only 90 x 65 mm (H x D) for mounting in small spaces in machines and
on the same DIN Track as components, contributing to machine downsiz­ing, increased functionality, and modularization.

• Basic instructions executed at 0.02 µs min. and special instructions at

0.06 µs min (for the CJ1-H CPU Units).

• Support the DeviceNet open network and protocol macros (for serial com­munications) to enable information sharing in machines. Machine-to­machine connections with Controller Link and host connections with
Ethernet are also supported for even more advanced information sharing,
including seamless message communications across Ethernet, Controller
Link, and DeviceNet networks.

Same Advanced

CJ-series PLC

Performance as CS­series PLCs

Basic instructions: 0.02 µs
Special instructions: 0.06 µs
Same high-speed CPU bus
as CS Series.
Large data memory:
256 Kwords
Program compatibility with
CS-series PLCs

PA205R

POWER

L1

AC100-240V

INPUT

L2/N

RUN

OUTPUT

AC240V
DC24V

Protocol Macro Function Serves
Multiple Ports

Up to 32 ports can be connected (Serial
Communications Units).
Different Protocol Macros can be allocated to
each port.

Personal
computer

CPU Unit

RUN

SYSMAC

ERR/ALM

CJ1G-CPU44

INH

PROGRAMMABLE

PRPHL

CONTROLLER

COMM

OPEN

MCPWR

BUSY

PERIPHERAL

PORT

Memory Card

Programmable
Terminal or
other device

Other Units

Structured Programming

The program is divided into tasks. Symbols
can be used in programming.
The overall performance of the system is im­proved by executing only the required tasks.
Modification and debugging are simplified.
The program arrangement can be changed.
Step control and block programming instruc-

tions can be used.

Comments can be added to make the pro­gram easier to understand.

Program

Task

Task

Task

Remote Programming, Monitoring
and Seamless Links between Net­works

FINS commands allow communications be­tween nodes in different networks: Ethernet,
Controller Link, and DeviceNet

Remote programming and monitoring can be
performed.

Programming
Console

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

2

General­purpose I/O
device

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.

CJ-series Features Section 1-2

The CJ-series PLCs support the same task-based programming structure,
instructions, high-speed instruction execution, I/O memory, functionality, and
message communications as the CS-series PLCs. The main differences of
the CJ-series in comparison to the CS-series PLCs are as follows (refer to
page 68 for details):

• No Backplanes are required.

• Screw mounting is not supported (only DIN Track mounting).

• Smaller size (30% to 35% in terms of volume).

• Inner Boards are not supported.

• I/O interrupt tasks and external interrupt tasks are not supported by CJ1
CPU Units. (They are supported by CJ1-H CPU Units.)

• C200H Special I/O Units are not supported (e.g., SYSMAC BUS Remote
I/O Units).

• It is not necessary to create I/O tables unless desired, i.e., I/O tables can
be created automatically when power is turned ON.

• The startup mode when a Programming Console is not connected is RUN
mode (rather than PROGRAM mode, as it is for CS1 CPU Units).

• Only version 2.04 or higher versions of CX-Programmer can be con­nected for CJ1 CPU Units, version 2.1 or higher for CJ1-H CPU Units,
and version 3.0 or higher for CJ1M CPU Units.

1-2 CJ-series Features

1-2-1 Special Features

Improvements in Basic Performance

The CJ Series provides high speed, high capacity, and more functions in
micro-size PLCs.

Only 30% to 35% of the
Volume of CS-series PLCs

Mount to DIN Track The CJ-series PLCs can be mounted to DIN Track along with power supplies

Faster Instruction
Execution and Peripheral
Servicing

Ample Programming
Capacity

Program and PLC Setup
Compatibility with CS­series CPU Units

At 90 x 65 mm (height x depth), the CJ-series Units have on 70% the height
and half the depth of CS-series Units, contributing to machine downsizing.

and other components when there is limited installation space in a machine
(e.g., limited space between top and bottom ducts).

The cycle time has been greatly reduced as a result of faster instruction exe­cution (

0.06, 0.12, or 0.15 µs min.; and floating-point instructions: 8.0, 10.2, or

13.3 µs min. for CJ1, CJ1-H, or CJ1M CPU Units)

overhead, I/O refreshes, and peripheral servicing.

With up to 250 Ksteps of program capacity, 256 Kwords of DM Memory, and
2,560 I/O points, there is sufficient capacity for added-value programs includ­ing machine interfaces, communications, data processing, etc.

There is almost 100% compatibility with CS-series CPU Units for program­ming and internal settings (PLC Setup).

basic instructions: 0.02, 0.08, or 0.10 µs min.; special instructions:

and faster processing for

Note Because of physical differences in the CJ-series PLCs, they do not

support all of the features of the CS-series PLC.

No Backplanes for Greater
Space Efficiency

A flexible system configuration that requires less space is made possible
because Backplanes are not required for CJ-series PLCs.

3

CJ-series Features Section 1-2

Up to 3 Expansion Racks
and 40 Units

By connecting an I/O Control Unit to the CPU Rack and I/O Interface Units to
Expansion Racks, up to three Expansion Racks (but only one for CJ1M CPU
Units) can be connected. The CPU Rack can contain up to 10 Units, as can
each of the three Expansion Racks, enabling a total of up to 40 Units.

Two I/O Allocation
Methods

The need for Backplanes was eliminated, enabling the following two methods
for allocating I/O.

1. Automatic I/O Allocation at Startup
I/O is allocated to the connected Units each time the power is turned ON
(same as CQM1H PLCs).

2. User-set I/O Allocation
If desired, the user can set I/O tables in the same way as for the CS-series
PLCs.

The default setting is for automatic I/O allocation at startup, but the user can
set the PLC to automatically use I/O tables to enable checking for Unit con­nection errors or to allocate unused words.

Allocate Unused Words The CX-Programmer can be used to allocate unused words in I/O tables for

transfer to the CPU Unit. This enables keeping words unallocated for future
use or to enable system standardization/modularization.

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 regular (cyclically executed) tasks and 256 interrupt
tasks. There are two types of interrupts: Power OFF Interrupts and Scheduled
Interrupts.

Task

Earlier program

Task

Task

Task

When a new program is being created, standard programs can be combined
as tasks to create an entire program.

Standard programs

Program ABC

Task 1 (A)

Task 2 (B)

Task 3 (C)

Program ABD

Task 1 (A)

Task 2 (B)

Task 3 (D)

4

CJ-series Features Section 1-2

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.

Symbols specified for bit address:

SW1 VALVE

Global and Local Symbols
Supported

Improve Overall System
Response Performance

Simplify Program Modification

Change Program
Arrangement Easily

Step Control and Block
Programming

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.

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.

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

When separate tasks have been programmed for different production models,
the task control instructions can be used to switch the program quickly from
production of one model to another.

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.

5

CJ-series Features Section 1-2

Port-specific Protocol Macros

Create Protocol Macros
for All Ports

Protocol macros 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.

All together, a CPU Unit can support a maximum of 32 ports. In addition, up to
16 ASCII Units can be connected. The ASCII Units can be used to create pro­tocol functions with BASIC programs.

Host Computer Programming Device

CPU Unit

Up to 32 ports are possible

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 Unit with the standard system protocol. It is also possible to change the
settings if necessary.

Serial Communications
Unit

External device
with serial port

PT

Note The Serial Communications Unit must be purchased separately to take

advantage of this function.

Transmit or receive data with just one instruction.

External device

6

CJ-series Features Section 1-2

Multilevel Network Configurations

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.

OA network: Ethernet
FA network: Controller Link
Open network: DeviceNet

Message communications
possible among Ethernet,
Controller Link, and DeviceNet.

Ethernet

CJ-series PLC

CJ-series PLC

Controller Link

I/O Terminal

Remote Monitoring and Programming

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.

Remote programming/monitoring
of a distant PLC

CS-series PLC

DeviceNet

CJ-series PLC

Robot, etc.Temperature

Controller

Remote programming/monitoring of a
PLC on the network through Host Link

Modem Modem

Controller Link Network

7

CJ-series Features Section 1-2

Remote programming/monitoring of a PLC on a network up to
3 levels away (including the local net-work) for the same or
different types of networks is possible through Host Link.

Network 3

Network 1

Network 2

Message transfer between PLCs on a network 3 levels away (including
the local network) for the same or different types of networks.

Network 3

Network 1

Network 2

Seamless message communications are possible across Ethernet, Controller Link, and DeviceNet networks,
enabling easy information integration on machine, machine-to-machine, and machine-to-host levels.

Note 1. With CS/CJ-series CPU Units Ver. 2.0 or later, remote programming/mon-

itoring is possible up to 8 levels away. Refer to

tection Using Passwords

2. NT Link communications between an NT31/NT631-V2 PT and a CJ-series
PLC are now possible at high speed.

1-2-2 Versatile Functions

Memory Card and File Management Functions

Tran sfer Data to and from
Memory Cards

Convert EM Area Banks to
File Memory (CJ1-H and
CJ1 CPU Units Only)

Automatic File Transfer at
Start-up

Data area data, program data, and PLC Setup data can be transferred as files
between the Memory Card (compact flash memory) and a Programming
Device, program instructions, a host computer, or via FINS commands.

I/O Memory, program,
and parameter areas
stored as files.

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. (The EM Area can be very useful for storing data such
as trend data as files.)

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.

1-5-2 Improved Read Pro-

for details.

8

CJ-series Features Section 1-2

I/O Memory Files in CSV
and Text Format

File Operations (Format,
Delete, etc.) from Ladder
Programs

Program Replacement
During Operation

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.

I/O memory data stored
in CSV or text format

FWRIT

Via Memory Card Adapter

Memory Card

Spread sheet software

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.

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.

PLC operation

.OBJ

Replacement

Easy Backups It is now possible to back up all data (user programs, parameters, and I/O

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.

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.

Processing of text string
data

External device with
standard serial port

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

9

CJ-series Features Section 1-2

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.

Stack region

Pointer

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.

Range specified
in the instruction

Data

Search, find maximum,
find minimum, etc.

Record-table Instructions

Record-table instructions operate on specially defined data tables. The record
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

Table

Record 2

Record 3

Record 2
Set values for model A

Temperature setting

Pressure setting

Time setting

Failure Diagnosis:
FAL(006) and FALS(007)

10

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.

User-defined
error condition

FAL(006) or FALS(007) error

CJ-series Features Section 1-2

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.

FPD

Input preventing
diagnostic output
from going 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 CJ-series PLCs record information useful for maintenance, such as the

number of power interruptions and the total PLC ON time.

Other Functions

Data Trace Function 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).

Trace memory

Specified address
in I/O memory

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.

Peripheral Servicing
Priority Mode

The CPU Unit can be set to execute peripheral servicing periodically and
more than once in each cycle. Up to five items can be set for priority servicing,
including the RS-232C port, peripheral port, CPU Bus Units, and Special I/O
Units. This feature supports applications that require giving priority to servic­ing peripheral devices over program execution, such as for host monitoring
systems for process control where response speed is important.

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.

The PLC’s initial settings can be
customized with the PLC Setup.

11

CJ1-H and CJ1M CPU Unit Features Section 1-3

Binary Refreshing of
Timer/Counter Instruction
PVs

Windows-based Support
Software

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 exist­ing 0 to 9,999). Also, results calculated by other instructions can be used as is
for timer/counter set values.

The single-port multiple-access (SPMA) function can be used to program and
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.

Programming Device

Several CPU Bus Units on the same
bus or other CPU Units on the same
network can be accessed from a

Controller Link

single port.

1-3 CJ1-H and CJ1M CPU Unit Features

1-3-1 CJ1-H CPU Unit Features

Ultra High-speed Cycle
Time

1,2,3... 1. Instruction execution times: Only about 1/2 the time required for basic in-

The CJ1-H CPU Units provide a cycle time that is three to four times faster
than that of the CJ1 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.9 ms for the CJ1 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.7 ms for the CJ1
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.4 ms for the CJ1 CPU Units).

The following factors give the CJ1-H CPU Units their high speed.

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.

12

CJ1-H and CJ1M CPU Unit Features Section 1-3

Faster Execution of
Common Instructions

System Bus Speed
Doubled

Parallel Processing of
Instructions and
Peripheral Servicing

Extensive research on applications of CJ1 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)

The speed of transferring data between the CPU Unit and CPU Bus Units has
been doubled to increase overall system performance.

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 CJ1-H CPU Unit

• Consistently timed data exchange with SCADA software

• Eliminating the effects on cycle time of future system expansion or
increases in communications

Less Cycle Time
Fluctuation for Data
Processing

Better Data Link and
Remote I/O Refreshing

Immediate Refreshing for
CPU Bus Units

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.

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 CJ1-H CPU Unit is approximately 2.4 times that of a CJ1
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.

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

13

CJ1-H and CJ1M CPU Unit Features Section 1-3

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 CJ1-H CPU Units support
up to 288 cyclic tasks, an incredible increase over the previous maximum of
32 tasks.

Common Processing from
Multiple Tasks

Faster Subroutine
Instructions

Shared Index and Data
Registers between 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.

Subroutine instruction are executed approximately 9 or 17 times faster to
enable greater program modularization without having to be concerned about
increasing the cycle time.

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 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 CJ1-H CPU
Units.

High-speed Positioning
for XY Tables

Convert between Floating
Point and Text String Data

Double-precision floating-point calculations are supported for the CJ1-H CPU
Units to provide even better precision for position control operations.

To display floating-point data on PTs, the CJ1-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

Realtime Workpiece Data
Management

PID Autotuning Autotuning is now supported for PID constants with the PID CONTROL

System Debugging
through Error Simulation

Program Simplification
with More Specific Basic
Instructions

Unsigned 16-bit binary/BCD data, signed 16/32-bit binary data, or 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.

When loading and unloading workpieces from conveyor lines, workpiece infor­mation can be managed in realtime in table format.

instruction. The limit cycle method is used to ensure rapid autotuning. Very
effective for multiloop PID control.

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.

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.

14

CJ1-H and CJ1M CPU Unit Features Section 1-3

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-4 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-5 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 CJ1-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
CJ-series PLCs, enabling programs with CVM1/CV-series addresses to be
quickly converted for use with a CJ-series CPU Unit.

1-3-6 CJ1M CPU Unit Features

Built-in I/O

General-purpose I/O

Interrupt Inputs

The CJ1M CPU Units are high-speed, advanced, micro-sized PLCs equipped
with built-in I/O. The built-in I/O have the following features.

■ Immediate Refreshing

The CPU Unit's built-in inputs and outputs can be used as general-purpose
inputs and outputs. In particular, immediate I/O refreshing can be performed
on the I/O in the middle of a PLC cycle when a relevant instruction is exe­cuted.

■ Stabilizing Input Filter Function

The input time constant for the CPU Unit's 10 built-in inputs can be set to 0 ms
(no filter), 0.5 ms, 1 ms, 2 ms, 4 ms, 8 ms, 16 ms, or 32 ms. Chattering and
the effects of external noise can be reduced by increasing the input time con­stant.

■ High-speed Interrupt Input Processing

The CPU Unit's 4 built-in inputs can be used for high-speed processing as
regular interrupt inputs in direct mode or interrupt inputs in counter mode. An
interrupt task can be started at the interrupt input's rising or falling edge (up or
down differentiation.) In counter mode, the interrupt task can be started when
the input count reaches the set value (up-differentiated or down-differentiated
transitions.)

High-speed Counters

■ High-speed Counter Function

A rotary encoder can be connected to a built-in input to accept high-speed
counter inputs.

15

CJ1-H and CJ1M CPU Unit Features Section 1-3

■ Trigger Interrupts at a Target Value or in a Specified Range

Interrupts can be triggered when the high-speed counter’s PV matches a tar­get value or is within a specified range.

■ Measure the Frequency of High-speed Counter Inputs

The PRV(881) instruction can be used to measure the input pulse frequency
(one input only.)

■ Maintain or Refresh (Selectable) High-speed Counter PVs

The High-speed Counter Gate Bit can be turned ON/OFF from the ladder pro­gram to select whether the high-speed counter PVs will be maintained or
refreshed.

Pulse Outputs

Fixed duty ratio pulses can be output from the CPU Unit's built-in outputs to
perform positioning or speed control with a servo driver that accepts pulse
inputs.

■ CW/CCW Pulse Outputs or Pulse + Direction Outputs

The pulse output mode can be set to match the motor driver's pulse input
specifications.

■ Automatic Direction Selection for Easy Positioning with Absolute
Coordinates

When operating in absolute coordinates (origin defined or PV changed with
the INI(880) instruction), the CW/CCW direction will be selected automatically
when the pulse output instruction is executed. (The CW/CCW direction is
selected by determining whether the number of pulses specified in the
instruction is greater than or less than the pulse output PV.)

■ Triangular Control

Triangular control (trapezoidal control without a constant-speed plateau) will
be performed during positioning executed by an ACC(888) instruction (inde­pendent) or PLS2(887) instruction if the number of output pulses required for
acceleration/deceleration exceeds the specified target pulse Output Amount.
Previously, an error would have occurred under these conditions and the
instruction would not have been executed.

■ Change Target Position during Positioning (Multiple Start)

When positioning was started with a PULSE OUTPUT (PLS2(887)) instruc­tion and the positioning operation is still in progress, another PLS2(887)
instruction can be executed to change the target position, target speed, accel­eration rate, and deceleration rate.

■ Switch from Speed Control to Positioning (Fixed Distance Feed Interrupt)

A PLS2(887) instruction can be executed during a speed control operation to
change to positioning mode. This feature allows a fixed distance feed interrupt
(moving a specified amount) to be executed when specific conditions occur.

■ Change Target Speed and Acceleration/Deceleration Rate during
Acceleration or Deceleration

When trapezoidal acceleration/deceleration is being executed according to a
pulse output instruction (speed control or positioning), the target speed and
acceleration/deceleration rate can be changed during acceleration or deceler­ation.

16

CJ1-H and CJ1M CPU Unit Features Section 1-3

■ Use Variable Duty Ratio Pulse Outputs for Lighting, Power Control, Etc.

The PULSE WITH VARIABLE DUTY RATIO instruction (PWM(891)) can be
used to output variable duty ratio pulses from the CPU Unit's built-in outputs
for applications such as lighting and power control.

Origin Search

■ Use a Single Instruction for Origin Search and Origin Return Operations

A precise origin search can be executed with one instruction that uses various
I/O signals, such as the Origin Proximity Input Signal, Origin Input Signal,
Positioning Completed Signal, and Error Counter Reset Output.

Also, an origin return operation can be performed to move directly to the
established origin.

Quick-response Inputs

■ Receive Input Signals Shorter than the Cycle Time

With quick-response inputs, inputs to the CPU Unit's built-in inputs (4 inputs
max.) with an input signal width as short as 30
regardless of the cycle time.

µs can be received reliably

Serial PLC Link Function

Data links (9 max.) can be set up between PLCs using the CPU Unit’s RS­232C port. NT Link (1:N connection) can also be incorporated in a Serial PLC
Link network, allowing the existing NT Link (1:N mode) and the Serial PLC
Link to be used together.

Note 1: PTs are included in the number of links.
Note 2: The Serial PLC Link cannot be used for PT data links.

Scheduled Interrupt Function Used as High-precision Timer

Scheduled interrupts in units of 0.1 ms have been added for CJ1M CPU Units.
An internal PV reset start function for scheduled interrupts has also been
added, so it is possible to standardize the time to the first interrupt without
using the CLI instruction. It is also possible to read the elapsed time from
either a scheduled interrupt start or from the previous interrupt. This allows
the interval timer (STIM instruction) in the CQM1H Series to be easily used for
the CJ Series.

Features of CJ1-H.CJ1M 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.

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 comment/
section data in the comment memory contained in the CPU Unit’s flash mem­ory.

17

CJ1-H and CJ1M CPU Unit Features Section 1-3

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

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

Improved Functions for PRV(881) and PRV2(883) (CJ1M Only)

High-frequency calculation methods have been added to the pulse frequency
calculation methods for PRV(881) (HIGH-SPEED COUNTER PV READ) and
PRV2(883) (PULSE FREQUENCY CONVERT) instructions (minimizes the
error in high frequencies of 1 kHz or higher). PRV(881) can also be used to
read the pulse output frequency.

1-3-7 Features of CJ1-H/CJ1M 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

18

Passwords can be set to read-protect individual groups of tasks. This enables
creating black boxes in the program.

CJ1-H and CJ1M CPU Unit Features Section 1-3

■ 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

Online connection is possible to any PLC in the local network from a Program­ming Device, such as the CX-Programmer, as soon as the network is con­nected. It’s not necessary to create the I/O tables to enable connection;
automatic I/O allocation at startup is used. This eliminates the need to use a
serial connection to create I/O tables before the CX-Programmer can be con­nected via Ethernet. Only an Ethernet connection through a CJ1W-ETN21
Ethernet Unit 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.

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). (Does not apply to C200HX/
HG/HE 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 CJ1-H/CJ1M CPU Units, the first word address
can be set for up to 64 slots. This can be used, for example, to create fixed

19

CJ1-H and CJ1M CPU Unit Features Section 1-3

starting addresses for Input Units and Output Unit to separate I/O allocations
from the program and increase the efficiency of program maintenance.

Automatic Transfer at Power ON

Automatic Tra nsfers at Power ON 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.

Automatic Detection of I/O Allocation Method for Automatic Transfer at Power ON
(CJ1-H and CJ1M CPU Units Ver. 2.0 or Later)

The method used to create the parameter file (AUTOEXEC.STD) for auto­matic transfer at power ON (automatic I/O allocation at startup or user-set I/O
allocation) is recorded. When an automatic transfer at power ON is executed
from the Memory Card, the recorded method is automatically detected and
used to create the I/O tables.

For example, this method can be used to create files for automatic transfer at
power ON in an office where Units are not mounted yet. The files can be
stored in a Memory Card, which can then be taken and installed in a CJ­series CPU Unit at the remote site. When automatic transfer at power ON is
executed, the I/O will be allocated by the CPU Unit according to the method
recorded in the Memory Card.

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

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

n

) from an Absolute Encoder with a Gray code output using a DC Input Unit.

(2

20

CJ1-H and CJ1M CPU Unit Features Section 1-3

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

1-3-8 Upgrades for CJ1M CPU Unit Ver. 2.0

This section describes the upgrades accompanying Ver. 2.0 of the CJ1M CPU
Units.

Pulse Outputs

S-curve Accelerations/
Decelerations

S-curves can be specified for the acceleration/deceleration rates for Pulse
Output Instructions with accelerations/decelerations (ACC(888), PLS2(883),
and ORG(889)). When there is leeway in the maximum allowable speed, S­curve accelerations/decelerations will help control shock and vibration by
reducing the initial acceleration rate in comparison with linear acceleration/
deceleration.

21

CJ1-H/CJ1M CPU Unit Ver. 3.0 Upgrades Section 1-4

Expanded Acceleration/
Deceleration Rate Setting

Duty Ratios Set in 0.1%
Increments

Wider Range of
Applications for CW/CCW
Limit Inputs

The upper limit of the acceleration/deceleration rate has been increased from
2,000 Hz to 65,535 Hz for Pulse Output Instructions with accelerations/decel­erations (ACC(888), PLS2(883), and ORG(889)).

The duty ratio for PWM(891) can now be set in 0.1% increments. The duty
ratio was set in 1% increments for the previous version.

Pulse outputs will stop when the CW/CCW limit input signals (reflected in
A54008, A54009, A54108, and A54109) turn ON. For the previous version,
the CW/CCW limit input signals were used only by ORG(889). With CPU Unit
Ver. 2.0, these signals can now be used with pulse output functions other than
origin searches. A new setting is also available for all functions that use the
CW/CCW limit input signals to specify whether the origin will remain estab­lished or be undefined when a limit input signal turns ON.

Pulse Inputs

Pulse Frequency
Conversions

The pulse frequency input to high-speed counter 0 can be converted to a rota­tional speed (r/min.) or the PV of the counter can be converted to the total
number of rotations.

High-speed Counters

Count Direction Flag The Count Direction Flag enables monitoring whether the count of the high-

speed counter is currently being incremented or decremented. The count in
the current cycle is compared with the count in the previous cycle to deter­mine whether it is being incremented or decremented.

Continued Comparisons
when Resetting Counters

The comparison operation can be set to stop or continue when a high-speed
counter is reset. This enables applications where the comparison operation
can be restarted from a counter PV of 0 when the counter is reset. For the
previous version, the comparison operation stopped when the counter was
reset, requiring that the comparison operation be restarted from the ladder
program whenever resetting the counter.

1-4 CJ1-H/CJ1M CPU Unit Ver. 3.0 Upgrades

The following table shows the functional upgrades for CJ1-H/CJ1M CPU Unit
Ver. 3 .0.

Functional Upgrades for CJ1-H/CJ1M CPU Unit Ver. 3.0

Function Section

Function blocks (when using CX-Programmer Ver. 5.0 or higher) 1-4-1
Serial Gateway (converting FINS commands to CompoWay/F com-

mands at the built-in serial port)
Comment memory (in internal flash memory) 1-4-3
Expanded simple backup data 1-4-4
Free running timer (system timer after power is turned ON) 1-4-5

1-4-2

22

CJ1-H/CJ1M CPU Unit Ver. 3.0 Upgrades Section 1-4

Function Section

New instructions
added

Additional instruc­tion functions

TXDU(256) and RXDU(255) instructions (sup­port no-protocol communications with Serial
Communications Units with unit version 1.2 or
later)

Model conversion instructions: XFERC(565),
DISTC(566), COLLC(567), MOVBC(568), and
BCNTC(621)

Special function block instruction: GETID(286)
TXD(236) and RXD(235) instructions (support

no-protocol communications with Serial Com­munications Boards with unit version 1.2 or
later)

1-4-6

1-4-1 Function Blocks (FB)

Unit Ver. 2.0 or Earlier 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.

1-4-2 Serial Gateway (Converting FINS to CompoWay/F Via Serial Port)

Unit Ver. 2.0 or Earlier 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.

23

CJ1-H/CJ1M CPU Unit Ver. 3.0 Upgrades Section 1-4

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 System

Network

CMND(490)

Serial

Serial

Network

FINS

Network

CompoWay/F-compatible
components can be ac­cessed via the network from
personal computers, PTs,
or PLCs.

CS/CJ-series CPU Unit with
unit version 3.0 or later

Protocol
conversion

CompoWay/F

Serial

CompoWay/F-compatible
components

1-4-3 Comment Memory (in Internal Flash Memory)

Unit Ver. 2.0 or Earlier 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)

24

CJ1-H/CJ1M CPU Unit Ver. 3.0 Upgrades Section 1-4

• Program index files (CX-Programmer section names, section comments,
and program comments)

CX-Programmer Ver. 5.0 or later

Comment/section data can be stored in the actual PLC

Project

when downloading projects.

Transfer

Symbol table file

Comment file

Program index file

CPU Unit

EM file memory

Memory Card

Comment
memory

Comment/section data can be stored in this area.

CX-Programmer Ver. 5.0 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)

CX-Programmer Ver. 4.0 or
Earlier

When using CX-Programmer Ver. 4.0 or earlier, 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 is stored
in comment memory (in CPU Unit’s internal flash memory).

1-4-4 Simple Backup Data Expanded

Unit Ver. 2.0 or Earlier 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)

• Comment files (CX-Programmer rung comments and other comments)

25

CJ1-H/CJ1M CPU Unit Ver. 3.0 Upgrades Section 1-4

• Program index files (CX-Programmer section names, section comments,
and program comments)

Simple backup executing

Memory Card

CS/CJ Series

CPU Unit

• User program

• Parameters

• I/O memory

(In comment memory)

Symbol table file

Comment file

Program index file

These files can also be backed up using simple backup.

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-4-5 Free Running Timer (System Timer after Power ON)

Unit Ver. 2.0 or Earlier The system did not provide a timer function that did not require instructions.

Unit Ver. 3.0 or Later The system timers used after the power is turned ON are contained in the fol-

lowing Auxiliary Area words.

Name Address Function Access

10-ms Incrementing
Free Running Timer

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

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.

Read-only

Read-only

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.

26

CJ1-H/CJ1M CPU Unit Ver. 2.0 Upgrades Section 1-5

1-4-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

• Special Function Block Instruction:
GETID(286) GET VARIABLE ID
This instruction is for use with function blocks.

• High-speed Counter/Pulse Output Instructions (CJ1M Only):
High-frequency calculation methods have been added to the pulse fre­quency calculation methods for PRV(881) (HIGH-SPEED COUNTER PV
READ) and PRV2(883) (PULSE FREQUENCY CONVERT) instructions.
PRV(881) can also be used to read the pulse output frequency.

1-5 CJ1-H/CJ1M CPU Unit Ver. 2.0 Upgrades

Functional Upgrades for CJ1-H/CJ1M CPU Unit Ver. 2.0

Downloading and Uploading Individual Tasks 1-5-1
Improved Read Protection Using Passwords 1-5-2
Write Protection from FINS Commands Sent to CPU Units via Networks 1-5-3
Online Network Connections without I/O Tables 1-5-4
Communications through a Maximum of 8 Network Levels 1-5-5
Connecting Online to PLCs via NS-series PTs 1-5-6
Setting First Slot Words 1-5-7
Automatic Transfers at Power ON without a Parameter File 1-5-8
Operation Start/End Times 1-5-9
Automatic Detection of I/O Allocation Method for Automatic Transfer at Power ON 1-5-10
New Application Instructions 1-5-11

The following table shows the functional upgrades for CJ1-H/CJ1M CPU Unit
Ver. 2 .0.

Function Reference

27

CJ1-H/CJ1M CPU Unit Ver. 2.0 Upgrades Section 1-5

1-5-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.

Developer A

Developer B

Developer C

CX-Programmer

CX-Programmer

CX-Programmer

Manager

Unification

Individual tasks can be uploaded.

Entire user program

CS/CJ Series

Download

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.

CX-Programmer

Individual tasks (programs)

28

END

END

END

Download individual tasks (programs).

CS/CJ-series
CPU Unit Ver.2.0 or higher

CJ1-H/CJ1M CPU Unit Ver. 2.0 Upgrades Section 1-5

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.

Developer A

Developer B

Developer C

Restrictions to Function
Block Use

CX-Programmer

Edited

Just the edited tasks can be downloaded.

CX-Programmer

Unchanged

CX-Programmer

Unchanged

Upload individual tasks.

Individual tasks cannot be downloaded for programs containing function
blocks (unit version 3.0 or later only) (uploading is possible).

1-5-2 Improved Read Protection Using Passwords

Read Protection for Individual Tasks Using Passwords

CS/CJ-series
CPU Unit Ver.2.0 or later

Previous CPU Units (Pre­Ver. 2.0 CPU Units)

CPU Unit Ver. 2.0 or Later
and CX-Programmer
Ver. 4.0 or Higher

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.

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.

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.

29

CJ1-H/CJ1M CPU Unit Ver. 2.0 Upgrades Section 1-5

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.

CX-Programmer

Set a password for particular tasks in the project directory.

Password?

Those tasks cannot be displayed without inputting the password.

CS/CJ-series CPU Unit Ver.2.0 or higher

END

END

END

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.

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.

Right-click

Properties

2. Select the tasks that will be password-protected and select the Ta s k r ea d
protect Option in the Program Properties Ta b .

30

Right-click

Properties

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.

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.

CJ1-H/CJ1M CPU Unit Ver. 2.0 Upgrades Section 1-5

Usage

Apply read protection to tasks when you want to convert those tasks (pro­grams) to “black box” programs.

Task 0

Accessable

END

Note 1. If CX-Programmer Ver. 3.2 or a lower version is used to read a task with

Restrictions to Function
Block Use

Task 1

Not accessable

Task 2

Accessable

Password applied.

Task converted to "black box."

END

END

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.

Function block definitions can be read even if the entire program or individual
tasks in a program containing function blocks (CPU Unit Ver. 3.0 or later only)
are read-protected.

Enabling/Disabling Creating File Memory Program Files

Previous CPU Units (Pre­Ver. 2.0 CPU Units)

CPU Unit Ver. 2.0 or Later
and CX-Programmer
Ver. 4.0 or Higher

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

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
create program files (.OBJ files) with file memory operations if the creation/
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 stor­age of PLC data that was uploaded to the CX-Programmer.)

31

CJ1-H/CJ1M CPU Unit Ver. 2.0 Upgrades Section 1-5

Disabling the creation of file memory program files can help prevent illegal
copying of the user program.

CX-Programmer

When a password is being registered for the entire user program or

Password?

Online creation of backup program files
(.OBJ files) prohibited by option setting.

selected tasks, the creation of backup program files (.OBJ files) can be
enabled/disabled with an option setting.

CX-Programmer

CPU Unit

Backup program files (.OBJ files) cannot be
created with file memory operations.

Uploading of all PLC
data is prohibited.

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.

Properties

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

Enabling/Disabling Write Protection for Individual Tasks Using Passwords

Previous CPU Units (Pre­Ver. 2.0 CPU Units)

32

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.

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.

CJ1-H/CJ1M CPU Unit Ver. 2.0 Upgrades Section 1-5

CPU Unit Ver. 2.0 or Later
and CX-Programmer
Ver. 4.0 or Higher

Note 1. If the selected tasks or program are write-protected by selecting this option

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.

CX-Programmer

When a password is being registered for the entire user

Password?

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.

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.

Properties

2. Either select PLC - Transfer - To PLC to transfer the program or select
PLC - Protection - Set Password and click the OK button.

33

CJ1-H/CJ1M CPU Unit Ver. 2.0 Upgrades Section 1-5

Auxiliary Area Flags and Bits related to Password Protection

Name Bit

UM Read Protection
Flag

Task Read Protec­tion Flag

Program Write Pro­tection for Read Pro­tection

Enable/Disable Bit
for Program Backup

address

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.

A09901 Indicates whether or not selected program tasks

are read-protected.
0: Task read protection is not set.
1: Task read protection is set.

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)

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

Description

1-5-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.

34

CJ1-H/CJ1M CPU Unit Ver. 2.0 Upgrades Section 1-5

Example:

Computer #1

PLC #1

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

Computer #2

PLC #3

Network

Write access to this PLC
is enabled/disabled.

Network

Write operations by FINS com­mands are not prohibited from
selected nodes in the network
(in this example, computer #2
and PLC #3).

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

Connection pattern Diagram (example) Write

From a com­puter through
a direct serial
connection

Direct con­nection to
PLC

Gateway con­nection
(Serial-to-net­work) to PLC

Computer

Serial connection
(Peripheral bus or
host link)

Computer

Write-protection not effective

Peripheral port

PLC

RS-232C port

RS-232C port or 422A/485 port
on a Communications Board/Unit

The CPU Unit in PLC #2
can be write-protected.

protection

Cannot be
applied.

Can be
applied.

Serial connection
(Peripheral bus
or host link)

PLC #1 PLC #2

Network

35

CJ1-H/CJ1M CPU Unit Ver. 2.0 Upgrades Section 1-5

Connection pattern Diagram (example) Write

From a computer through a
direct network connection

From another PLC in the net­work

Computer

PLC #1 PLC #2

Network

If the CMND instruction is used to send

CMND

PLC #1 PLC #2

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.

The CPU Unit in PLC #2
can be write-protected.

protection

Can be
applied.

Can be
applied.

Network

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

36

CJ1-H/CJ1M CPU Unit Ver. 2.0 Upgrades Section 1-5

PLC Setup

Item Address in

Use FINS Write Pro­tection

Nodes Excluded
from Write Protec­tion (Protection
Releasing
Addresses)

Number of Nodes
Excluded from FINS
Write Protection
(Do not set this
value. It is automati­cally calculated by
the CX-Program­mer.)

Description Settings Default setting

Programming

Console

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

Words 449 to
480

Bits 08 to 15Network address:

Bits 00 to 07Node address:

Word 448, bits
00 to 07

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 pro­tection is enabled.

Network address of the FINS com­mand source

Node address of the FINS com­mand source

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: Write protection
disabled

1: Write protection
enabled

00 to 7F hex

01 to FE hex, or FF
hex
(FF hex: node
address unspecified)

0 to 32
(00 to 20 hex)

(A value of 0 indi­cates that all nodes
are subject to write
protection.)

0: Write protection
disabled

0
(All nodes subject to
write protection.)

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

37

CJ1-H/CJ1M CPU Unit Ver. 2.0 Upgrades Section 1-5

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.

System control/monitoring computer

Allowed to
write/control PLC

Equipment

Network

Monitoring computer

Controller

Allowed to
write/con­trol PLC

Not allowed to
write/control PLC

Operations Restricted by
Network FINS Write
Protection

Network

CS/CJ-series PLC

FINS Write Commands

The following FINS commands are restricted by FINS write protection when
sent to the CPU Unit through the network.

Network

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

38

CJ1-H/CJ1M CPU Unit Ver. 2.0 Upgrades Section 1-5

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.

Operations not
allowed through the
network when FINS
write protection is
enabled.

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 op­erations.

• 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

• 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

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.

39

CJ1-H/CJ1M CPU Unit Ver. 2.0 Upgrades Section 1-5

1-5-4 Online Network Connections without I/O Tables

Summary With 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 as a result of using auto­matic I/O allocation at startup.

CPU Bus Unit
(including Network Communications Units)

CS/CJ-series CPU Unit Ver.2.0 or higher

Network

Online connection
can be made.

CPU Bus Units (including Network Communications Units)
can be recognized before I/O tables are created (I/O allo­cation at startup is used).

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

1:1 Computer-to-PLC connection 1:N Computer-to-PLC connection

CX-Programmer

CX-Programmer

CS/CJ­series
CPU Unit

Ethernet

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.

Ver.2.0

I/O table not
registered

40

CS/CJ­series
CPU Unit
Ver.2.0

I/O table not registered I/O table not registered I/O table not registered

Ethernet

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

CS/CJ­series
CPU Unit
Ver.2.0

• Applicable Units: All CS/CJ-series CPU Bus Units

• Applicable computer-based Programming Devices: CX-Programmer and
CX-Protocol only

CJ1-H/CJ1M CPU Unit Ver. 2.0 Upgrades Section 1-5

• Applicable functions: Online connections from CX-Programmer and CX­Protocol, and online functions of the applicable CPU Units and CPU Bus
Units

Note 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 eth­ernet cable between the CX-Programmer and PLC (without making a direct
serial connection and creating the I/O tables), manually set the computer's IP
address in the Windows Local Area Connection Properties (example:

192.168.250.55). 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-5-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 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

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

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 when the

destination is a CPU Unit. FINS commands can be sent to other destina­tions up to 3 network levels away.

2. This functionality is enabled only after setting routing tables with the CX­Net in CX-Programmer version 4.0 or higher.

3. A Gateway to the network via serial communications was not counted as a
level.

41

CJ1-H/CJ1M CPU Unit Ver. 2.0 Upgrades Section 1-5

p

x

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 3 networks through

DeviceNet and SYSMAC Link networks.

Configuration of Compatible Models

All of the CPU Units must be CPU Unit Ver. 2.0 and later CS/CJ-series CPU
Units. Also, the Gateway Counter Setting must be made with the CX-Net.

FINS command
source

Serial
connection

OR

Level
count = 1

Network 2

Level
count = 2

Level
count = 3

Network 4

Level
count = 4

Network 7

Level
count = 7

FINS command
destination

This connection is not counted as a network level.

Network 1

Network 3

Network 8

Internal Structure The Gateway Counter (GCT) is in the FINS header of the FINS command/

response frame. This counter value is decremented (

−1) each time a network

level is crossed.

FINS Command Frame

FINS header Command code Text

ICF RSV GCT

GCT (Gateway counter: Number of allowed bridge passages)

The standard setting is 02 hex when sending, but this value can be
user-set from 07 hex.
The count is decremented by one each time a network level is passed.

Example:

FINS command
source

At this point, the gateway counter = 6 hex

Network 2

FINS command

At this point, the gateway counter = 4 hex

Network 4

FINS command

FINS command
destination

FINS command

Network 1

At this point, the gateway counter = 7 hex

Operating Procedure There is no special procedure that must be performed for CS/CJ-series CPU

Note 1. When using communications only for up to 3 network levels, the CS/CJ-se-

42

FINS command

Network 3

At this

oint, the gateway counter = 5 hex

At this point, the gateway counter = 0 he

FINS command

Network 8

Units Ver. 2.0 or later. Just set normal routing tables to enable communicating
across up to 8 network levels.

ries CPU Units Ver. 2.0 or later can be used together with other CPU Units.

CJ1-H/CJ1M CPU Unit Ver. 2.0 Upgrades Section 1-5

When using communications for to 4 to 8 network levels, use only CS/CJ­series CPU Units Ver. 2.0 or later. Other CPU Units cannot be used. Rout­ing errors (error codes 0501 to 0504 hex) may occur in the relaying PLCs,
preventing a FINS response from being returned.

2. With CS/CJ-series CPU Units with unit version 2.0 or later, the Gateway
Counter (GCT: Number of allowed bridge passes) for FINS command/re­sponse frames is the value decremented from 07 hex (variable). (In earlier
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 used to select 07 hex as the val­ue from which to decrement.

3. Do not use the Gateway Counter (GCT: Number of allowed bridge passes)
enclosed in the FINS header of the FINS command/response frame in ver­ification 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.

1-5-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.

CX-Programmer
(Example IP address: 192.168.0.1)

Connect online to PLC #1 to enable
programming, monitoring, and other operations.

NS-series PT

(Example IP address:

192.168.0.22)

PLC #1

CS/CJ-series
CPU Unit Ver. 2.0

1:N NT Link

Ethernet (See note 1.)
(Example network address: 1)

(Example network address: 111)

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

43

CJ1-H/CJ1M CPU Unit Ver. 2.0 Upgrades Section 1-5

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.

1-5-7 Setting First Slot Words

Previous CPU Units (Pre-Ver. 2.0 CPU Units)

With CX-Programmer Ver. 3.0 or lower, only the first addresses on Racks
could be set. The first address for a slot could not be set.

First addresses on Racks

Example:

CX-Programmer
Ver. 3.0 or earlier

Rack No.
CPU Rack
Rack 1
Rack 2
Rack 3
Rack 4
Rack 5
Rack 6
Rack 7

First address
100
0
200

CPU Rack slot

Rack 1 slot

Rack 2 slot

0 1 2

01 234

01 2

CIO 0100

CIO 0000

CIO 0200

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 (CS1D CPU Units for
Single-CPU Systems, and CS1-H, CJ1-H, and CJ1M CPU Units). 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 for Duplex CPU Systems.

44

CJ1-H/CJ1M CPU Unit Ver. 2.0 Upgrades Section 1-5

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.

Select Option - Rack/Slot Start Addresses.

Double-click

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

First slot addresses

Example:

CX-Programmer
Ver. 3.2 or higher

CPU Rack slot

Rack 1 slot

Rack 2 slot

0

12

2

01

01 2

Rack No.
CPU Rack
CPU Rack
Rack 1
Rack 1
Rack 2
Rack 2

34

Slot No.
Slot No. 00
Slot No. 02
Slot No. 00
Slot No. 02
Slot No. 00
Slot No. 01

CIO 0100
CIO 0000

CIO 0102
CIO 0001

CIO 0105
CIO 0005

100
0
102
1
105
5

Up to 8 settings
can be made.

45

CJ1-H/CJ1M CPU Unit Ver. 2.0 Upgrades Section 1-5

Note The first address settings for Racks and slots can be uploaded/downloaded

from/to the CPU Unit.

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 for Duplex-CPU Sys­tems.

First slot addresses

CX-Programmer
Ver. 4.0 or higher

Example:

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

100
0
102
1
105
5

Up to 64 settings
can be made.

CPU Unit Ver. 2.0
or higher

CPU Rack slot

0

12

Rack 7

Slot No. 01

CIO 0100

50

CIO 0000

Rack 1 slot

01

2

34

CIO 0102

CIO 0001

Rack 2 slot

01 2

CIO 0105
CIO 0005

Rack 7 slot

01 2

CIO 0155
CIO 0050

1-5-8 Automatic Tra n sfers 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).

46

CJ1-H/CJ1M CPU Unit Ver. 2.0 Upgrades Section 1-5

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.

Personal
computer

Mail

Mail

Program file (.OBJ) sent
as mail attachment.

Internet

Local site (no Programming Device)

CPU Unit

Program cannot be transferred
(see note).

Program file
(AUTOEXEC.OBJ)

Note: Transfer is not possible because

there is no parameter file
(AUTOEXEC.STD).

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, REPLCE@.IOM.

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.

Personal
computer

Mail

Mail

Program file created on CX­Programmer (see note), file name
changed to REPLACE.OJB, and
file sent as mail attachment.

Internet

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.

Remote site (no Programming Device)

CPU Unit

Program can be transferred
(see note).

REPLACE.OBJ

Note: Transfer is possible even

without a parameter file
(AUTOEXEC.STD).

47

CJ1-H/CJ1M CPU Unit Ver. 2.0 Upgrades Section 1-5

1-5-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-5-10 Automatic Detection of I/O Allocation Method for Automatic

Transfer at Power ON

Previous CPU Units (Pre-Ver. 2.0 CPU Units)

Previously with the CJ-series CPU Units, when a parameter file for automatic
transfer at power ON (AUTOEXEC.STD) was recorded in a Memory Card, the
user-set I/O allocation method was automatically used when an automatic
transfer at power ON was executed from the Memory Card, and I/O was allo­cated according to the parameter file for automatic transfer at power ON. As a
result, the following case occurred:

1,2,3... 1. In an office where Units were not mounted, the CX-Programmer was con-

nected online to just the CPU Unit, and files for automatic transfer at power
ON were created (without creating/transferring I/O tables).

2. These files for automatic transfer at power ON were then saved in the
Memory Card, which was then taken to the remote site where automatic
transfer at power ON was executed.

3. When automatic transfer at power ON was executed, I/O tables were cre­ated based on the parameter file for automatic transfer at power ON saved
in the Memory Card (i.e., the file created when Units were not mounted to
the PLC). As a result, the registered I/O tables did not match the Units ac­tually mounted in the CPU Unit, causing an I/O setting error.

48

CJ1-H/CJ1M CPU Unit Ver. 2.0 Upgrades Section 1-5

Office

Create program files for automatic
transfer at power ON
(AUTOEXEC.OBJ) and parameter
files for automatic transfer at
power ON (AUTOEXEC.STD).

CX-Programmer

Mail

Program file for automatic
transfer at power ON
(AUTOEXEC.OBJ)

Parameter file for automatic
transfer at power ON
(AUTOEXEC.STD)

CPU Unit Ver. 2.0 or Later

Overview

Remote site

Units are mounted

I/O not allocated according to settings in mounted Units

User-set I/O allocation

Program file for automatic
transfer at power ON
(AUTOEXEC.OBJ)

Memory Card

CJ-series CPU Unit

Automatic I/O allocation at startup

Units not mounted.

Mis-match
(See note.)

Note: The parameter file for automatic transfer

Parameter file for automatic
transfer at power ON
(AUTOEXEC.STD)

at power ON (AUTOEXEC.STD) is
present, and this file is used to allocated
I/O instead of the I/O allocations in the
mounted Units.

With CJ-series CPU Unit Ver. 2.0 or later, the I/O allocation method that was
used (automatic I/O allocation at startup or user-set I/O allocation) is recorded
in the parameter file for automatic transfers at power ON (AUTOEXEC.STD),
and when automatic transfer at power ON is executed from the Memory Card,
the recorded method is automatically detected and used to create the I/O
tables.

• When the parameter file for automatic transfer at power ON is created
using automatic I/O allocation at startup, the I/O tables in the parameter
file for automatic transfer at power ON in the Memory Card are disabled,
and I/O is allocated using automatic I/O allocation at startup from the
actual mounted Units.

• When the parameter file for automatic transfer at power ON is created
using user-set I/O allocation, the I/O tables in the parameter file for auto­matic transfer at power ON in the Memory Card is enabled, and the regis­tered I/O tables are transferred to the CPU Unit.

Office Remote site

Create program files for automatic transfer
at power ON (AUTOEXEC.OBJ) and
parameter files for automatic transfer
at power ON (AUTOEXEC.STD).

CX-Programmer

Program file for automatic
transfer at power ON
(AUTOEXEC.OBJ)

Parameter file for automatic
transfer at power ON
(AUTOEXEC.STD)

Units not mounted.

Units mounted.

Match
(See note.)

Memory Card

CJ1-H, CJ1M CPU Unit
with Unit Ver. 2.0 or higher.

Automatic I/O allocation at startup

I/O is allocated according to settings in mounted Units.

CJ1-H, CJ1M CPU Unit with Unit Ver. 2.0 or higher.

Parameter file for automatic transfer at power ON
(AUTOEXEC.STD)

Note: The parameter file for automatic transfer at power ON
(AUTOEXEC.STD) is present, but I/O is allocated by the I/O
allocations in the mounted Units.

Program file for automatic
transfer at power ON
(AUTOEXEC.OBJ)

Parameter file for automatic
transfer at power ON
(AUTOEXEC.STD)

Automatic I/O
allocation at
startup

49

CJ1 and CJ1-H CPU Unit Comparison Section 1-6

As a result, in the above diagram for example, files for automatic transfer at
power ON are created in an office where the Units are not mounted. The files
are then saved in a Memory Card, which is taken and installed in a CJ-series
CPU Unit at the remote site, where automatic transfer at power ON is exe­cuted and I/O is allocated according to the I/O allocations in the mounted Unit
using the method recorded in the Memory Card.

1-5-11 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))

• COUNTER FREQUENCY CONVERT (PRV2(883)) (CJ1M CPU Unit only)

• 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, >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.)

1-6 CJ1 and CJ1-H CPU Unit Comparison

Item CJ1-H CPU Unit

Instruc­tion exe­cutions
times

Overseeing processing time Normal mode: 0.3 ms

50

Basic instructions LD: 0.02 µsLD: 0.10 µs 0.08 µs

Special instructions Examples

(CJ1H-CPU6@H)

OUT: 0.02 µsOUT: 0.35 µs 0.21 µs

XFER: 300 µs (for 1,000
words)

BSET: 200 µs (for 1,000
words)

BCD arithmetic: 8.2 µs
min.

Binary arithmetic: 0.18 µs
min.

Floating-point math: 8 µs
min.

SBS/RET: 2.1 µs SBS/RET: 3.8 µs37 µs

Parallel mode: 0.2 ms

CJ1M CPU Unit

(CJ1M-CPU@2/CPU@3)

XFER: 650 µs (for 1,000
words)

BSET: 400 µs (for 1,000
words)

BCD arithmetic: 18.9 µs
min.

Binary arithmetic: 0.30 µs
min.

Floating-point math: 13.3
µs min.

0.5 ms 0.5 ms

XFER: 633 µs (for 1,000
words)

BSET:278 µs (for 1,000
words)

14 µs min.

0.37 µs min.

10 µs min.

(CJ1G-CPU4@)

CJ1 CPU Unit

CJ1 and CJ1-H CPU Unit Comparison Section 1-6

Execu­tion timing

Item CJ1-H CPU Unit

CPU execution pro­cessing modes

CPU Bus
Unit spe­cial
refresh­ing

Refreshing of CIO and
DM Areas words allo­cated to CPU Bus Unit

Data links During I/O refresh period
DeviceNet

remote I/O
Protocol

macro
send/
receive
data

(CJ1H-CPU6@H)

Any of the following four
modes:

Normal (instructions and
peripheral servicing per­formed consecutively)

Peripheral Servicing Prior­ity Mode (instruction exe­cution interrupted to
service peripherals at a
specific cycle and time;
consecutive refreshing
also performed)

Parallel Processing Mode
with Synchronous Memory
Access (instruction exe­cuted and peripheral ser­vices in parallel while
synchronizing access to I/
O memory)

Parallel Processing Mode
with Asynchronous Mem­ory Access (instruction
executed and peripheral
services in parallel without
synchronizing access to I/
O memory)

or via special CPU BUS
UNIT I/O REFRESH
instruction (DLNK(226))

CJ1M CPU Unit

(CJ1M-CPU@2/CPU@3)

Either of following two
modes:

Normal (instructions and
peripheral servicing per­formed consecutively)

Peripheral Servicing Prior­ity Mode (instruction exe­cution interrupted to
service peripherals at a
specific cycle and time;
consecutive refreshing
also performed)

During I/O refresh period
or via special CPU BUS
UNIT I/O REFRESH
instruction (DLNK(226))

CJ1 CPU Unit

(CJ1G-CPU4@)

Either of following two
modes:

Normal (instructions and
peripheral servicing per­formed consecutively)

Peripheral Servicing Prior­ity Mode (instruction execu­tion interrupted to service
peripherals at a specific
cycle and time; consecutive
refreshing also performed)
(Add for CPU Units with lot
number No.

@@@@ or later.)

001201

During I/O refresh period

51

CJ1 and CJ1-H CPU Unit Comparison Section 1-6

Item CJ1-H CPU Unit

Tasks Cyclic execution of

interrupt tasks via
TKON instruction
(called “extra cyclic
tasks”)

Independent/shared
specifications for
index and data regis­ters

Initialization when
tasks are started

Starting subroutines
from multiple tasks

Scheduled interrupt
interval for scheduled
interrupt tasks

Debug­ging

Interrupt
task exe­cution
timing
during
instruc­tion exe­cution

Backup to Memory
Cards (simple backup
function)

Automatic user pro­gram and parameter
area backup to flash
memory

For instruc­tions other
than the
following
ones

For BIT
COUNTER
(BCNT) or
BLOCK
TRANS­FER
(XFER)
instruc­tions

(CJ1H-CPU6@H)

Supported.
(Up to 256 extra cyclic
tasks, increasing the total
number of cyclic tasks to
288 max.)

Supported.
The time to switch between
tasks can be reduced if
shared registers are used.

Supported.
Task Startup Flags sup­ported.

Global subroutines can be
defined that can be called
from more than one task.

1 ms to 9,999 ms, or 10 ms
to 99,990 ms, in units of 1
ms or 10 ms.

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.

Interrupt tasks are started only after execution of the
instruction has been completed, ensuring data concur­rency even when the same data area words are
accessed from the instruction and the interrupt task.

In addition to the data
listed at the right, data from
Units 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 Commu­nications Units, etc.

Supported (enabling bat­tery-free operation without
a Memory Card)

The user program and
parameter area data are
automatically backed up
the flash memory when­ever they are transferred to
the CPU Unit from the CX­Programmer, file memory,
etc.

CJ1M CPU Unit

(CJ1M-CPU@2/CPU@3)

Supported.
(Up to 256 extra cyclic
tasks, increasing the total
number of cyclic tasks to
288 max.)

Supported.
The time to switch between
tasks can be reduced if
shared registers are used.

Supported.
Task Startup Flags sup­ported.

Global subroutines can be
defined that can be called
from more than one task.

In addition to the previ­ously supported intervals
(1 ms to 9,999 ms, or 10
ms to 99,990 ms, in units
of 1 ms or 10 ms), an inter­val of 0.5 ms to 999.9 ms in
units of 0.1 ms is also sup­ported.

In addition to the data
listed at the right, data from
Units 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 Commu­nications Units, etc.

Supported (enabling bat­tery-free operation without
a Memory Card)

The user program and
parameter area data are
automatically backed up
the flash memory when­ever they are transferred to
the CPU Unit from the CX­Programmer, file memory,
etc.

CJ1 CPU Unit

(CJ1G-CPU4@)

Not supported.
(No extra cyclic tasks; 32
cyclic tasks max.)

Not supported.
(Only independent registers
for each task.)

Only Task Flag for first exe­cution.

Not supported.

1 ms to 9,999 ms, or 10 ms
to 99,990 ms, in units of 1
ms or 10 ms.

Only the user program
parameters, and I/O mem­ory in the CPU Unit.

Not supported.

52

CJ1 and CJ1-H CPU Unit Comparison Section 1-6

Item CJ1-H CPU Unit

I/O tables Detailed information

on I/O table creation
errors

Displaying presence
of first rack word set­ting on Programming
Console

Sequence
instruc­tions

Timer/
counter
instruc­tions

Special
math
instruc­tions

Floating­point deci­mal
instruc­tions

Differentiated LD NOT,
AND NOT, and OR
NOT instructions

OUTB, SETB, and
RSTB instructions to
manipulate individual
bits in DM and EM
Area words

Format for updating
PVs for TIM, TIMH,
TMHH, TTIM, TIML,
MTIM, CNT, CNTR,
CNR, TIMW, TMHW,
CNTW instructions

32-bit signed data line
coordinates and X
axis starting point
specification for APR
instruction

Single-precision cal­culations and conver­sions

Conversions between
single-precision float­ing point and ASCII

Double-precision cal­culations and conver­sions

(CJ1H-CPU6@H)

Detailed I/O table error
information is stored in
A261 whenever the I/O
tables cannot be created
for any reason.

It’s possible to confirm if
the first rack word has
been specified for the sys­tem on the Programming
Console display.

The first rack word is speci­fied from the CX-Program­mer, making it previously
impossible to confirm the
setting from the Program­ming Console.

Supported. Supported. Not supported.

Supported. Supported. Not supported.

Either BCD or binary can
be selected (with CX-Pro­grammer Ver. 3.0 or
higher).

Supported. Supported. Not supported.

Supported (enabling stan­dard deviation calcula­tions).

Supported.
Floating point can be con-

verted to ASCII for display
on PTs.

ASCII text strings from
measurement devices can
be converted to floating­point decimal for use in cal­culations.

Supported (enabling high­precision positioning).

CJ1M CPU Unit

(CJ1M-CPU@2/CPU@3)

Detailed I/O table error
information is stored in
A261 whenever the I/O
tables cannot be created
for any reason.

It’s possible to confirm if
the first rack word has
been specified for the sys­tem on the Programming
Console display.

The first rack word is speci­fied from the CX-Program­mer, making it previously
impossible to confirm the
setting from the Program­ming Console.

Either BCD or binary can
be selected (with CX-Pro­grammer Ver. 3.0 or
higher).

Supported (enabling stan­dard deviation calcula­tions).

Supported.
Floating point can be con-

verted to ASCII for display
on PTs.

ASCII text strings from
measurement devices can
be converted to floating­point decimal for use in cal­culations.

Supported (enabling high­precision positioning).

CJ1 CPU Unit

(CJ1G-CPU4@)

Not supported.

Not supported.

(The same results can be
achieved by combining dif­ferentiated LD, AND, and
OR instructions with the
NOT instruction.)

BCD only.

Not supported.

Not supported.

Not supported.

53

CJ1 and CJ1-H CPU Unit Comparison Section 1-6

Text
string,
table
data, and
data shift
instruc­tions

Data con­trol
instruc­tions

Subrou­tine
instruc­tions

Failure
diagnosis
instruc­tions

Data com­parison
instruc­tions

Index reg­ister real
I/O
address
conver­sion for
CVM1/CV

Condition
Flag sav­ing and
loading

Item CJ1-H CPU Unit

Text string and table
data processing
instruction execution

Stack insertions/dele­tions/replacements
and stack counts with
table processing
instructions

PID with autotuning Supported (eliminating the

Global subroutines Supported (GSBS, GSBN,

Error log storage for
FAL

Error simulation with
FAL/FAL S

AREA RANGE COM­PARE (ZCP) and
DOUBLE RANGE
COMPARE (ZCPL)

Program and real I/O
memory address com­patibility with CVM1/
CV-series PLCs

Compatibility with
CVM1/CV-series
PLCs

(CJ1H-CPU6@H)

Data processing can be
performed normally or in
the background (specified
for each instruction).

(Using time slices to pro­cess instruction over sev­eral cycles reduces the
effect of these instructions
on the cycle time.).

Supported.
Effective for tracking work-

pieces on conveyor lines.

need to adjust PID con­stants).

and GRET instructions)
Enables easier structuring
of subroutines.

Supported.
FAL can be executed with­out placing an entry in the
error log. (Only system
FAL errors will be placed in
the error log.)

Supported.
Fatal and nonfatal errors
can be simulated in the
system to aid in debug­ging.

Supported. Supported. Not supported.

CVM1/CV-series real I/O
memory addresses can be
converted to CJ-series
addresses and placed in
index registers or CJ­series real I/O memory
addresses in index regis­ters can be converted to
CVM1/CV-series
addresses.

Condition Flag status can
be saved or loading using
the SAVE CONDITION
FLAGS (CCS) and LOAD
CONDITION FLAGS
(CCL) instructions,
enabling applications
where Condition Flag sta­tus must be passed
between different program
locations, tasks, or cycles.

CJ1M CPU Unit

(CJ1M-CPU@2/CPU@3)

Data processing can be
performed normally or in
the background (specified
for each instruction).

(Using time slices to pro­cess instruction over sev­eral cycles reduces the
effect of these instructions
on the cycle time.).

Supported.
Effective for tracking work-

pieces on conveyor lines.

Supported (eliminating the
need to adjust PID con­stants).

Supported (GSBS, GSBN,
and GRET instructions)
Enables easier structuring
of subroutines.

Supported.
FAL can be executed with­out placing an entry in the
error log. (Only system
FAL errors will be placed in
the error log.)

Supported.
Fatal and nonfatal errors
can be simulated in the
system to aid in debug­ging.

CVM1/CV-series real I/O
memory addresses can be
converted to CJ-series
addresses and placed in
index registers or CJ­series real I/O memory
addresses in index regis­ters can be converted to
CVM1/CV-series
addresses.

Condition Flag status can
be saved or loading using
the SAVE CONDITION
FLAGS (CCS) and LOAD
CONDITION FLAGS
(CCL) instructions,
enabling applications
where Condition Flag sta­tus must be passed
between different program
locations, tasks, or cycles.

CJ1 CPU Unit

(CJ1G-CPU4@)

Normal processing only.

Not supported.

Not supported.

Not supported.

Not supported.

Not supported.

Not supported.

Not supported.

54

CJ1 and CJ1-H CPU Unit Comparison Section 1-6

Item CJ1-H CPU Unit

Opera­tion when
Unit
doesn’t
complete
startup
process

Disabling power interruptions in
program sections

Condition Flag operation The statuses of the Equals,

Built-in I/O Not supported. CJ1M-CPU2@ Not supported.
Serial PLC Link Not supported. Supported. Not supported.

0.1-ms scheduled interrupts Not supported. Supported. Not supported.
Battery CPM2A-BAT01 CJ1W-BAT01 CPM2A-BAT01

CPU Unit startup Starting or not starting

(CJ1H-CPU6@H)

(standby) the CPU Unit in
MONITOR or RUN mode
even if a Unit has not com­pleted startup processing
can be specified in the
PLC Setup.

Supported.
Instructions between DI
and EI are executed with­out performing power OFF
processing even if a power
interruption has been
detected and confirmed.

Negative, and Error Flags
are maintained for execu­tion of the following instruc­tions.

TIM, TIMH, TMHH, CNT,
IL, ILC, JMP0, JME0,
XCHG, XCGL, MOVR,
input comparison instruc­tions, CMP, CMPL, CPS,
CPSL, TST, TSTN, STC,
and CLC.

CJ1M CPU Unit

(CJ1M-CPU@2/CPU@3)

Starting or not starting
(standby) the CPU Unit in
MONITOR or RUN mode
even if a Unit has not com­pleted startup processing
can be specified in the
PLC Setup.

Supported.
Instructions between DI
and EI are executed with­out performing power OFF
processing even if a power
interruption has been
detected and confirmed.

The statuses of the Equals,
Negative, and Error Flags
are maintained for execu­tion of the following instruc­tions.

TIM, TIMH, TMHH, CNT,
IL, ILC, JMP0, JME0,
XCHG, XCGL, MOVR,
input comparison instruc­tions, CMP, CMPL, CPS,
CPSL, TST, TSTN, STC,
and CLC.

CJ1 CPU Unit

(CJ1G-CPU4@)

CPU Unit standby (fixed)

Not supported.

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, input com­parison instructions, CMP,
CMPL, CPS, CPSL, TST,
TSTN, STC, and CLC.

55

Function Tables Section 1-7

1-7 Function Tables

The following tables list functions for the CJ-series CPU Units (including the
CJ1, CJ1M, and CJ1-H CPU Units).

1-7-1 Functions Arranged by Purpose

Purpose Function Manual Reference

Basic Opera­tion and Sys­tem Design

Structured
Programming

Studying system configura­tion

Studying I/O allocations --- SECTION 8

Installation size --- 5-2-3

Installation methods --- 5-2 Installa-

Setting DIP switches --- 3-1-2 Com-

Setting the PLC Setup --- 7-1 PLC

Using Auxiliary Bits --- Appendix B

Studying the cycle time --- Parallel

Troubleshooting --- 11-2-5 Error

Standardizing programs as
modules.

Developing a program with
several programmers work­ing in parallel.

Making the program easier
to understand.

Creating step programs. Use the step instructions. Instructions

Using BASIC-like mne­monic instructions to pro­gram processes that are
difficult to enter in the lad­der diagram format (such
as conditional branches
and loops).

--- Operation

Program with tasks to divide the pro­gram, specify symbols, and define
local and global symbols.

Use the block programming instruc­tions.

Manual

Programming
Manual

(W394)

Reference
Manual

(W340)

SECTION 2
Specifica­tions and
System
Configura­tion

I/O Alloca­tions

Assembled
Appear­ance and
Dimensions

tion

ponents

Setup

CJ1M CPU
Unit Built-in
I/O Specifi­cations and
9-11 Auxil­iary Area

Processing
Mode (CJ-H
CPU Units
Only)

Messages

4-1 Tasks

Step Pro­gramming
Instructions

Block Pro­gramming
Instructions

56

Function Tables Section 1-7

Purpose Function Manual Reference

Simplifying
the Program

Creating looped program
sections.

Indirectly addressing DM
words.

Simplifying the program by
switching to PLC memory
address specification.

Consolidating instruction
blocks with the same pat­tern but different addresses
into a single instruction
block.

Use FOR(512) and NEXT(513) or
JMP(004) and JME(005).

All words in the DM and EM Areas can
be indirectly addressed.

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 functions
are also supported.

Use MCRO(099). Instructions

Instructions
Reference
Manual

(W340)

Programming
Manual

(W394)

Reference
Manual

(W340)

Sequence
Control
Instructions

6-2 Index
Registers

MCRO(099)
in the Sub­routine
Instructions

57

Function Tables Section 1-7

Purpose Function Manual Reference

Managing the
Cycle Time

Reducing the cycle time. • Use tasks to put parts of the pro-

Setting a fixed (minimum)
cycle time.

Setting a maximum cycle
time.
(Generating an error for a
cycle time exceeding the
maximum.)

Reducing the I/O response
time for particular I/O
points.

Finding I/O refresh times
for individual Units

Studying the I/O response
time

Finding the increase in the
cycle time for online editing

Giving peripheral servicing
priority over instruction exe­cution

gram that don’t need to be executed
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 subrou­tines 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 a minimum cycle time in the PLC
Setup.

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.

Use immediate refreshing or
IORF(097).

--- Operation

--- 10-4-6 I/O

--- 10-4-5

Use the Peripheral Servicing Priority
Mode

Programming
Manual

(W394)

Operation
Manual

Programming
Manual

(W394)

Manual

Programming
Manual

(W394)

6-1 Cycle
Time/High­speed Pro­cessing

7-1 PLC
Setup

6-1 Cycle
Time/High­speed Pro­cessing

Parallel
Processing
Mode (CJ-H
CPU Units
Only)

Response
Time

Online Edit­ing Cycle
Time Exten­sion

6-6 Periph­eral Servic­ing Priority
Mode

58

Function Tables Section 1-7

Purpose Function Manual Reference

Using Inter­rupt Tasks

Data Pro­cessing

System
Configura­tion and
Serial Com­munications

Monitoring operating sta­tus at regular intervals.

Issuing an interrupt to the
CPU when data is received
through serial communica­tions.

Performing interrupt pro­cessing when an input
goes ON.

Executing an emergency
interrupt program when the
power supply fails.

Studying the interrupt
response time

Knowing the priority of
interrupt tasks

Operating a FIFO or LIFO
stack.

Performing basic opera­tions on tables made up of
1-word records.

Performing complex opera­tions on tables made up of
1-word records.

Performing operations on
tables made up of records
longer than 1 word.

(For example, the tempera­ture, pressure, and other
manufacturing settings for
different models of a prod­uct could be stored in sepa­rate records.)

Monitoring several differ­ent kinds of devices
through the RS-232C port.

Changing protocol during
operation (from a modem
connection to host link, for
example).

Use a scheduled interrupt task. Programming

Use a Serial Communications Units
and external interrupt task.

Use an I/O interrupt task.

Use a power OFF interrupt task.
Enable the power OFF interrupt task

in the PLC Setup.

--- Operation

--- Programming

Use the stack instructions (FIFO(633)
and LIFO(634)).

Use range instructions such as
MAX(182), MIN(183), and
SRCH(181).

Use Index Registers as pointers in
special instructions.

Use Index Registers and the record­table instructions.

Multiple serial ports can be installed
with Serial Communications Units
(protocol macros).

Use STUP(237), the CHANGE
SERIAL PORT SETUP instruction.

Manual

(W394)

Manual

Manual

(W394)

Instructions
Reference
Manual

(W340)

Programming
Manual
(W394)

Operation
Manual

Instructions
Reference
Manual

(W340)

4-3 Inter­rupt Tasks

10-4-7 Inter­rupt
Response
Times

4-3-2 Inter­rupt Task
Priority

Table Pr o ­cessing
Instructions

6-2 Index
Registers

2-5
Expanded
System
Configura­tion

Serial Com­munica­tions
Instructions

59

Function Tables Section 1-7

Purpose Function Manual Reference

Connecting
Program­ming Devices

Controlling
Outputs

Controlling
I/O Memory

Connecting a Programming
Console.

Connecting a Programming
Device (e.g., the CX-Pro­grammer).

Connecting a host com­puter.

Connecting a PT. Connect to the RS-232C port or

Connecting a standard
serial device to the CPU
Unit (no-protocol mode).

Turning OFF all outputs on
basic Output Units and
High-density Output Units
(a type of Special I/O Unit).

Maintaining the status of all
outputs on Output Units
when PLC operation stops
(hot start).

Maintaining the previous
contents of all I/O Memory
at the start of PLC opera­tion (hot start).

Maintaining the previous
contents of all I/O Memory
when the PLC is turned on.

Connect to the peripheral port with pin
4 of the CPU Unit’s DIP switch OFF.

Connect to the peripheral port with pin
4 of the CPU Unit’s DIP switch OFF or
with pin 4 ON and the communica­tions mode set to “peripheral bus”
under Peripheral Port settings in the
PLC Setup.

Connect to the RS-232C port with pin
5 of the CPU Unit’s DIP switch ON or
with pin 5 OFF and the communica­tions mode set to “peripheral bus”
under RS-232C Port settings in the
PLC Setup.

Connect to the RS-232C port or
peripheral port. (Set the communica­tions mode to “host link” in the PLC
Setup.)

peripheral port. (Set the communica­tions mode to “NT Link” in the PLC
Setup.)

Set the PT communications settings
for a 1:N NT Link.

Connect to the RS-232C port.
(Set the communications mode to “no­protocol” in the PLC Setup.)

Turn ON the Output OFF Bit
(A50015).

Turn ON the IOM Hold BIt (A50012). 6-4-1 Hot

Turn ON the IOM Hold BIt (A50012). Programming

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)

Operation
Manual

Programming
Manual

(W394)

Manual

(W394)

3-3 Pro­gramming
Devices

2-5
Expanded
System
Configura­tion

6-4-2 Load
OFF Func­tions

Start/Hot
Stop Func­tions

6-4-1 Hot
Start/Hot
Stop Func­tions

60

Function Tables Section 1-7

Purpose Function Manual Reference

File Memory Automatically transferring

Text string
processing

the program, I/O Memory,
and PLC Setup from the
Memory Card when the
PLC is turned on.

Creating a library of pro­grams for different pro­gram arrangements.

Creating a library of param­eter settings for various
PLC Racks and models.

Creating a library of data
files with settings for vari­ous PLC Racks and CPU
Bus Units.

Storing I/O Comment data
within the Memory Card.

Storing operating data
(trend and quality data)
within the CPU Unit during
program execution.

Switching PLC operation. Memory Card functions (Program

Reading and writing I/O
memory data with a
spreadsheet.

Performing string process­ing at the PLC which was
performed at the host com­puter previously and reduc­ing the program load at the
host computer (operations
such as read, insert,
search, replace, and
exchange).

Performing string process­ing operations such as
rearranging text strings.

Receiving data from exter­nal devices (such as bar
code readers) through
serial communications,
storing the data in DM, and
reading just the required
string when it is needed.

Enable the “automatic transfer at
start-up” function by turning ON pin 2
of the CPU Unit’s DIP switch and cre­ate an AUTOEXEC file.

Memory Card functions (Program
Files)

Memory Card functions (Parameter
Files)

Memory Card functions (Data Files)

Memory Card functions
(Symbol Table Files)

EM File Memory Functions and the
FREAD(700)/FWRIT(701) instructions

Replacement during PLC Operation)
Read/write data files using instruc-

tions in CSV or text format.

Combine the Host Link function with
the text string processing instructions.

Use the string comparison instructions
and index registers.

Combine the protocol macro function
with the text string processing instruc­tions.

Programming
Manual

(W394)

Instructions
Reference
Manual

(W340)

SECTION 5
File Memor y
Functions

Text String
Processing
Instructions

61

Function Tables Section 1-7

Maintenance
and Debug­ging

Error Pro­cessing and
Troubleshoot­ing

Purpos

Changing the program
while it is being executed.

Sampling I/O Memory data.

• Periodic sampling

• Sampling at the end of

• Sampling at execution of

Specifying the start-up
operating 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.

Stopping the program for
instruction execution
errors.

Programming/monitoring
the PLC remotely.

• Programming or monitor-

• Programming or monitor-

Programming/monitoring
PLCs in other networks

Generating a non-fatal or
fatal error for user-defined
conditions.

• Non-fatal errors (PLC

• Fatal errors (PLC opera-

Analyzing time and logic in
execution of an instruction
block.

Record information about
errors, including user­defined errors, in the error
log.

e Function Manual Reference

each cycle

TRSM(045)

ing a PLC on the network
through Host Link.

ing a PLC through
modems.

operation continues.)

tion stops.)

Use the online editing function from a
Programming Device.

(Several instruction blocks can be
changed with CX-Programmer.)

Data trace at regular intervals
Data trace at the end of each cycle
Data trace each time that TRSM(045)

is executed

Set the PLC Setup to specify the
desired operating mode at start-up.
(Startup Mode)

These items are recorded automati­cally in the Auxiliary Area.

Set the PLC Setup so that instruction
errors are treated as fatal errors.
(Instruction Error Operation)

Host Link → Network Gateway func­tion

Host Link through modems

Communicate with PLCs up to two
network levels away through Control­ler Link or Ethernet.

FAILURE ALARM: FAL(006)
SEVERE FAILURE ALARM:

FALS(007)

FAILURE POINT DETECTION:
FPD(269)

Use the error log function. Up to 20
error records can be stored.

Programming
Manual

(W394)

Operation
Manual

Programming
Manual

(W394)

7-2-3 Online
Editing

7-2-4 Data
Tracing

6-4 Startup
Settings an d
Mainte­nance

6-4-5 Clock
Functions

2-3-3
Checking
Programs

2-5
Expanded
System
Configura­tion

6-5 Diag­nostic and
Debugging
Functions

62

Function Tables Section 1-7

Purpose Function Manual Reference

Other Func­tions

Protecting the program. Write-protect the user program mem-

Allocating words in the I/O
Area by specifying the first
word allocated to each
Rack.

Reducing input chattering
and the effects of noise.

ory.

Set the first word allocated to each
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.)

Specify the input response times for
Basic I/O Units in the PLC Setup.
(Basic I/O Unit Input Response Time)

Programming
Manual

(W394)

6-4 Startup
Settings an d
Mainte­nance

6-7 Other
Functions

1-7-2 Communications Functions (Serial/Network)

Purpose Protocol: Required Equipment Reference

Monitoring from
the Host Com­puter

Connecting to a
Standard Serial
Device

Communicating
with a PT

Data Link
between PLCs

Data Link between PLC and computer Controller Link:

Message
communications
between PLCs

Message
communications
between PLC
and computer

RS-232C or RS-422/485 Host Link:

Host Link communications from the
PLC

Network communications through
RS-232C or RS-422/485

Network Control system Controller Link:

Information sys­tem

Creating a simple protocol Protocol Macros:

High-speed data exchange

No protocol No protocol:

Direct access NT Link:

High capacity or free word allocation Controller Link: Controller Link Unit

Normal or high capacity Controller Link: Controller Link Unit

Information system Ethernet: Ethernet Unit

Control system Controller Link:

Information system Ethernet: Ethernet Unit

Port in the CPU Unit or Serial Com­munications Unit

Enclose a FINS command with a
Host Link header and terminator and
issue it from the PLC as a network
communications instruction.

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

Controller Link Unit
Ethernet: Ethernet Unit

Serial Communications Unit

CPU Unit’s RS-232C port, or Protocol
Macro

Port in the CPU Unit or Serial Com­munications Unit

Controller Link Unit

Controller Link Unit

2-5 Expanded
System Con­figuration

63

Function Tables Section 1-7

Purpose Protocol: Required Equipment Reference

Remote I/O
between PLC
and Slaves

High-density I/O DeviceNet:

Free word allocation

Multi-vendor capability

Analog I/O capability

Multi-level architecture

High-speed Remote I/O CompoBus/S:

DeviceNet Master Unit and required
Slave Units

CompoBus/S Master Unit and
required Slave Units

2-5-3 Com­munications
Network Sys­tem

64

CJ1-H Functions Arranged by Purpose Section 1-8

1-8 CJ1-H Functions Arranged by Purpose

Purpose Function

Increas­ing
speed

Increasing the speed of both the instruction
execution cycle and peripheral servicing.

• Fast large-scale data exchange with the
host is needed even though the PLC pro­gram is very large.

• Consistently timed data exchange with
SCADA software is needed.

• Faster message communications and con­trol is needed between distributed PLCs.

• It is necessary to minimize the effects on
the cycle time of future system expansion
or increases in communications.

Maintaining concurrency in the I/O mem­ory data accessed for instruction execution
and for peripheral servicing (for data larger
than one word).

Not necessarily maintaining concurrency
in the I/O memory data accessed for
instruction execution and for peripheral
servicing (for data larger than one word).

Giving priority to peripheral servicing over
the instruction execution cycle (For example,
to give priority to the read/write response of
CPU Unit data from SCADA software for
process control).

Specifying where index and data registers
are used independently by task for shared
by tasks.

Minimizing cycle time fluctuations and main­taining consistent I/O response even when
extensive table data and text string data is
being processed.

Improving data link response with a long
cycle time.

Improving DeviceNet remote I/O response. The CPU BUS UNIT I/O REFRESH instruction (DLNK(226)) can

Improving the response of protocol macro
data transfers for Serial Communications
Units.

Immediately refreshing status data and
other words allocated to CPU Bus Units in
the CIO Area whenever necessary (includ­ing Ethernet Units, Serial Communications
Units, Controller Link Units, etc.).

Use the Parallel Processing Mode with Synchronous Memory
Access or Parallel Processing Mode with Asynchronous Memory
Access.

Using parallel processing enables the following savings.
For example, if the program consists of basic instructions with a

cycle time of approximately 10 ms and one Ethernet Unit is being
used, the cycle time will be reduced to approximately 90% of the
time for the normal mode. and the peripheral servicing time will be
reduced to approximately 40% of the time for the normal mode.

Use the Parallel Processing Mode with Synchronous Memory
Access.

Use the Parallel Processing Mode with Asynchronous Memory
Access.

The response of peripheral servicing can be adjusted by using the
following modes (listed in order from highest response):

Parallel Processing Mode with Asynchronous Memory Access,
Peripheral Servicing Priority Mode (with a long instruction execu­tion cycle), Parallel Processing Mode with Synchronous Memory
Access, Normal Mode

Set the program properties from the CX-Programmer to indepen­dent (default) or shared registers.

Table data processing and text string processing, which often
require time, can be set in the PLC Setup so that they are pro­cessed in the background. The default is for no background exe­cution. (For background execution, time slicing is used to
separate processing over several cycles.)

If background execution is used, the effect on the cycle time can
be limited to 4% or less (PLC Setup default setting).

The CPU BUS UNIT I/O REFRESH instruction (DLNK(226)) can
be used at one or more locations in the ladder program. This
enables refreshing data links for specified Controller Link or SYS­MAC LINK Units, whenever necessary, as well as during the I/O
refresh period. (The actual data that is refreshed depends on the
communications cycle time.)

be used at one or more locations in the ladder program. This
enables refreshing remote I/O for DeviceNet Units, whenever nec­essary, as well as during the I/O refresh period. (The actual data
that is refreshed depends on the communications cycle time.)

The CPU BUS UNIT I/O REFRESH instruction (DLNK(226)) can
be used at one or more locations in the ladder program. This
enables refreshing data transferred for protocol macros executed
by Serial Communications Units, whenever necessary, as well as
during the I/O refresh period. (The actual data that is refreshed
depends on the communications cycle time.)

The CPU BUS UNIT I/O REFRESH instruction (DLNK(226)) can
be used at one or more locations in the ladder program. This
enables refreshing words allocated to CPU Bus Units in the CIO
Area (25 words) whenever necessary, in the same way that the
IORF instruction is used for other Units.

65

CJ1-H Functions Arranged by Purpose Section 1-8

Purpose Function

Increas­ing
struc­ture

Special
applica­tions

Using more tasks. Define interrupt tasks as cyclic tasks (called “extra cyclic tasks”).
Reducing the cycle time even with structured

programs using many tasks.
Using the same index or data registers in dif-

ferent tasks without saving and loading reg­ister contents.

Initializing processing when a task is started. Use the Task Start Flags.
Using standard processing shared by more

than one task.
Standardization and program structure

based on subroutines.

Displaying floating-point decimal data on a
PT.

Using text string data from measurement
devices in calculations.

Performing high-precision positioning, e.g.,
for XY tables.

Managing information on workpieces flowing
on a conveyer in realtime in table form, e.g.,
when workpieces are added or removed
from the conveyor during processing.

Performing high-precision linear approxima­tions, e.g., converting a level meter reading
in mm to a capacity value in liters according
to the shape of a tank.

Autotuning PID constants (particularly to
automatically tune PID constants and start
the system faster when using multiloop PID).

Saving and loading execution results (e.g.,
from comparison instructions) at different
locations in a task or in different tasks.

Using a CVM1/CV-series program contain­ing real I/O memory addresses in a CJ­series CPU Unit.

Using I/O memory tables containing CVM1/
CV-series real I/O memory addresses (e.g.,
to return the data to a CVM1/CV-series CPU
Unit after processing by the CJ-series CPU
Unit).

Disabling power interruptions during specific
regions of the program.

Use shared index and data registers.

Use a global subroutine (GSBN to GRET) in interrupt task num­ber 0.

Increase speed using subroutine instructions (SBS, SBN, and
RET) and global subroutine instructions (GSBS, GSBN, and
GRET)

Use the FLOATING- POINT TO ASCII instruction.

Use the ASCII TO FLOATING-POINT instruction.

Use the Double-precision Floating-point instructions.

Use the stack instructions.
STACK DATA READ, STACK DATA OVERWRITE, STACK DATA

INSERT, and STACK DATA DELETE (Operate on a specified ele­ment in the stack.)

STACK SIZE READ (Counts the number of elements in the
stack.)

Use the ARITHMETIC PROCESS instruction (unsigned 16-bit
binary/BCD data, signed 16/32-bit binary data, or single-precision
floating-point data can be used for line data).

Use the PID CONTROL WITH AUTO TUNING instruction.

Use the SAVE CONDITION FLAGS (CCS) and LOAD CONDI­TION FLAGS (CCL) instructions to save the current status of the
Condition Flags or load the previous status.

Use the CONVERT ADDRESS FROM CV (FRMCV) instruction.

Use the CONVERT ADDRESS TO CV (TOCV) instruction.

Create program sections for which power interrupts have been
disabled with the DI and EI instructions (set A530 to A5A5 hex).

66

CJ1-H Functions Arranged by Purpose Section 1-8

Purpose Function

Debug­ging
and
mainte­nance

Not including user-defined FAL errors in the
error log, e.g., when monitoring errors on a
PT. (System FAL errors will be included.)

Simulating errors in the CPU Unit when
debugging the system, e.g., to check error
messages displayed on a PT.

Backing up data from Units other than the
CPU Unit, e.g., DeviceNet Units, Serial
Communications Units, etc.

Finding errors occurring when creating I/O
tables.

Using battery-free operation (ROM opera­tion) without a Memory Card.

Starting CPU Unit operation without waiting
for Units with long startup times to complete
startup processing.

Set the PLC Setup to not include user-defined FAL errors in the
error log.

Use FAL/FALS to simulate fatal and nonfatal system errors.

Use the simple backup operation, which includes data from spe­cific Units (including device parameters from DeviceNet Units,
protocol macro data from Serial Communications Units, etc.).

Use the detailed error information for I/O table creation stored in
the AR Area.

Use the automatic program/parameter area backup function to
flash memory in the CPU Unit.

Use the startup condition settings (allowing the CPU Unit to star­tup immediately in RUN or MONITOR mode even when startup
processing has not been completed for other Units).

67