How it Works
Omron
Loading...
CJ1M-CPU21
Getting Started Guide [nl]
23 pgs511.09 Kb0
Operation Manual
363 pgs4.81 Mb0
Operation Manual
267 pgs3.66 Mb0
Operation Manual [de]
266 pgs4.58 Mb0
Operation Manual [es]
65 pgs1.45 Mb0
Operation Manual [fr]
265 pgs4.57 Mb0
Table of contents
Loading...

Omron CJ1M-CPU21, CJ1M-CPU22, CJ1M-CPU23 Operation Manual

Download
Cat. No. W372-E1-11
SYSMAC CS/CJ Series WS02-LCTC1-EV5
CX-Process Tool Ver. 5.2
OPERATION MANUAL

WS02-LCTC1-EV5 CX-Process Tool Ver. 5.2

Operation Manual
Revised November 2007
iv

Notice:

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 precautions can result in injury to people or dam­age to property.
DANGER Indicates an imminently hazardous situation which, if not avoided, will result in death or
!
serious injury. Additionally, there may be severe property damage.
WARNING Indicates a potentially hazardous situation which, if not avoided, could result in death or
!
serious injury. Additionally, there may be severe property damage.
Caution Indicates a potentially hazardous situation which, if not avoided, may result in minor or
!
moderate injury, or property damage.
OMRON Product References
All OMRON products are capitalized in this manual. The word “Unit” is also capitalized when it refers to an OMRON product, regardless of whether or not it appears in the proper name of the product.
The abbreviation “Ch,” which appears in some displays and on some OMRON products, often means “word” and is abbreviated “Wd” in documentation in this sense.
The abbreviation “PLC” means Programmable Controller. “PC” is used, however, in some Program­ming Device displays to mean Programmable Controller.
Visual Aids
The following headings appear in the left column of the manual to help you locate different types of information.
Note Indicates information of particular interest for efficient and convenient operation
of the product.
1, 2, 3... 1. Indicates lists of one sort or another, such as procedures, checklists, etc.
Copyrights and Trademarks
Windows is a registered trademark of the Microsoft Corporation.
Other system and product names that appear in this manual are the trademarks or registered trade­marks of the respective company.
OMRON, 2000
All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form, or by any means, mechanical, electronic, photocopying, recording, or otherwise, without the prior written permis­sion of OMRON.
No patent liability is assumed with respect to the use of the information contained herein. Moreover, because OMRON is constantly striving to improve its high-quality products, the information contained in this manual is subject to change without notice. Every precaution has been taken in the preparation of this manual. Nevertheless, OMRON assumes no responsibility for errors or omissions. Neither is any liability assumed for damages resulting from the use of the informa­tion contained in this publication.
v

About Loop Controllers

oop
p
Loop Control Types, Functional Elements, and Versions
Loop Controller Types
There are two types of CS/CJ-series Loop Controller: Separate Loop Control­lers and Loop Controllers Pre-installed in CPU Units
Loop
Controller
type
Separate Separate
Pre-installed in CPU Unit
Type name Product name Model PLC series and Unit type
Loop Controller
CPU Unit with Pre-installed Loop Controller
Loop Control Unit CS1W-LC001 CS-series CPU Bus Unit Loop
Loop Control Board
Loop Control Board with Gradient Temperature Controller
Process-control CPU Unit
Loop-control CPU Unit
Loop-control CPU Unit with Gradient Temperature Controller
Loop Controller Functional Elements
• Separate Loop Controllers consist of only the Loop Controller functional ele­ment (i.e., the Loop Controller element).
• CPU Units with Pre-installed Loop Controller consists of a CPU Unit functional element (i.e., the CPU Unit element) and the Loop Controller functional ele­ment (i.e., the Loop Controller element).
Controller
CS1W-LCB01/05 CS-series Inner Board Loop Controller
CS1W-LCB05-GTC CS-series Inner Board Loop Controller
CS1D-CPUP
CJ1G-CPUP
CJ1G-CPUP-GTC
A one-Unit Loop Controller consisting of an Inner Board pre-installed in a CS-series CS1D-H CPU Unit
An Inner Board Loop Controller integrated into a CS-series CJ1-H CPU Unit
An Inner Board Loop Controller integrated into a CJ-series CJ1-H CPU Unit
Versions
The functional elements (i.e., the CPU Unit element and Loop Controller ele­ment) have versions.
Model Numbers and Functional Elements
The following table lists the Loop Controller product model numbers, the func­tional element names for the CPU Unit elements and Loop Controller elements, and the versions of the functional elements.
vi
Product Product model
t
p
CPU
p
name number of the
Loop Control Unit
Loop Control Board
Loop Control Board with Gradient Temperature Controller
Process­control Unit
Loop-control CPU Unit
Loop-control CPU Unit with Gradient Temperature Controller
CS1W-LC001 Pre-Ver. 2.0 --- LC001 Ver. 2.5
CS1W-LCB01
CS1W-LCB05
CS1W-LCB05­GTC
CS1D-CPU65P
CS1D-CPU67P CS1D-CPU67H Ver. 1.0 or later LCB05D Ver. 1.0
CJ1G-CPU42P
CJ1G-CPU43P CJ1G-CPU43H Ver. 3.0 or later LCB03 Ver. 2.0 or later
CJ1G-CPU44P CJ1G-CPU44H Ver. 3.0 or later LCB03 Ver. 2.0 or later
CJ1G-CPU45P CJ1G-CPU45H Ver. 3.0 or later LCB03 Ver. 2.0 or later
CJ1G-CPU45P­GTC
Unit version
produc
model
(See note.)
Ver. 2.0 or later
Ver. 3.0 or later
---
---
Ver. 3.0 or later
Configuration
CPU unit element Loop Controller element
CPU Unit
model with
same
functionality
---
--- LCB05-GTC Ver. 3.0 or later
CS1D-CPU65H Ver. 1.0 or later LCB05D Ver. 1.0
CJ1G-CPU42H Ver. 3.0 or later LCB01 Ver. 2.0 or later
CJ1G-CPU45H Ver. 3.0 or later LCB05-GTC Ver. 3.0 or later
Functional
element unit
version
Functional
element
name
LCB01 Ver. 2.0 or later
LCB05 Ver. 2.0 or later
Functional
element
Note Only Separate Loop Controllers have a unit version for the product model. CPU
Units with Pre-installed Loop Controllers do not have a unit version for the prod­uct model.

Notation in this Manual

This manual uses the following notation.
• “Loop Controller” is used as a generic term to refer to the Loop Controllers in general.
• “LCB” is used to refer to specific Loop Controller functional elements. For example, the Loop Controller function element in a CS1W-LCB05 Loop Con­trol Board is the LCB05, so “LCB05” is used to refer to the Loop Controller func­tional element. The Loop Controller function element in a CJ1G-CPU44P Loop-control CPU Unit is the LCB03, so “LCB03” is used to refer to the Loop Controller functional element.
• Model numbers are used to refer to specific Loop Controller models.
In the CX-Process Tool Operation Manual for version 3.2 or earlier, functional element names (LCB) are given as “Loop Control Board.” In the CX-Process Tool Operation Manual for version 4.0 or higher, simply “LCB” is used.
vii

Unit Version Notation on Products

Loop Control Boards
A “unit version” has been introduced to manage CPU Units, Special I/O Units, and Inner Boards in the CS/CJ Series according to differences in functionality accompanying upgrades. This system applies to Units manufactured since Oc­tober 1, 2003. The unit version code is provided on the nameplate of the product for which unit versions are being managed, as shown below for the Loop Control Board.
Loop Control Board
Product nameplate
Unit version Example for unit version 1.5
The CX-Process Tool can be used to confirm the unit versions of Loop Control Boards in the Monitor Run Status Window. After connecting the CX-Process Tool online, select Operation – Monitor Run Status from the Execute Menu. Confirm the unit version in ITEM099 (MPU/FROM version display) under from the System Common Block (Block Model 000) in the Monitor Run Status Win­dow.
ITEM Data name Data
099 MPU/FROM version indication V1.50
Version V1.50 and onwards must be indicated.
Functional Element Name and Version Code for Process-control CPU Units and Loop-control CPU Units
The functional element name and functional element version code for Process­control CPU Units and Loop-control CPU Units are provided on the nameplate as shown in the following diagrams.
viii
Process-control CPU Units
Note CPU Unit elements for which no version code is provided are pre-Ver. 2.0 CPU
Units.
Nameplate on left side of Unit
Loop-control CPU Units
Product model and functional element name
Process-control CPU Unit
Functional element name for Loop Controller element
Functional element version code for Loop Controller element
Loop-control CPU Unit
Product nameplate
Product nameplate
Functional element name for CPU Unit element
Functional element version code for the CPU Unit element
Unit model number
Functional element version code for Loop Controller ele­ment
Functional element version code for CPU unit element
Recommended location for attaching version label
Lot No.
Confirming CPU Unit Element Versions with Support Software
CX-Programmer version 4.0 can be used to confirm the unit version using either of the following two methods.
• Using the PLC Information
• Using the Unit Manufacturing Information (This method can also be used for
Special I/O Units and CPU Bus Units.)
Note CX-Programmer version 3.3 or lower cannot be used to confirm unit versions.
PLC Information
1, 2, 3... 1. 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 do not 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.
2. In either case, the following PLC Information Dialog Box will be displayed.
Functional element version code for Loop Controller element
ix
Functional element name for CPU Unit element
Functional element version code for CPU Unit element
Use the above display to confirm the unit version of the CPU Unit that is con­nected online.
Unit Manufacturing Information
1, 2, 3... 1. In the I/O Table Window, right-click and select Unit Manufacturing In-
formation – CPU Unit.
2. The following Unit Manufacturing Information Dialog Box will be displayed.
x
Functional element version


code for CPU Unit element
Use the above display to confirm the unit version of the CPU Unit connected online.
Functional Element Versions and Programming Devices
The Programming Device that supports the functional element version code must be used to enable all the functions in the corresponding functional element.
Note Upgrading versions is not necessary if only the basic functions of the CPU Unit
element are required.
CPU Unit Element
Loop Controller Programming Device
Functional
element name
CS1G/H-CPUH
CS1D-CPUH CJ1G-CPUH
Functional
element version
Pre-Ver. 2.0
Ver. 2.0 Ver. 4.0 or higher
Ver. 3.0 Ver. 5.0 or higher
Ver. 1.1 Ver. 4.0 or higher
Ver. 3.0 Ver. 5.0 or higher
Ver. 4.0 Ver. 7.0 or higher
CX-Process Tool CX-Programmer
(See note.)
---
---
xi
Loop Controller Element
Loop Controller Programming Device
Functional
element name
LCB01
LCB05
LCB05-GTC Ver. 3.0 Ver. 5.1 or higher LCB03
LCB03-GTC Ver. 3.0 Ver. 5.1 or higher
LCB05D Ver. 1.0 Ver. 3.1 or higher
Functional
element version
Ver. 1.0 Ver. 3.0 or higher
Ver. 1.5 Ver. 3.2 or higher
Ver. 2.0 Ver. 4.0 or higher
Ver. 3.0 Ver. 5.0 or higher
Ver. 3.5 Ver. 5.2 or higher
Ver. 1.0 Ver. 3.0 or higher
Ver. 1.5 Ver. 3.2 or higher
Ver. 2.0 Ver. 4.0 or higher
Ver. 3.0 Ver. 5.0 or higher
Ver. 3.5 Ver. 5.2 or higher
Ver. 2.0 Ver. 4.0 or higher
Ver. 3.0 Ver. 5.0 or higher
Ver. 3.5 Ver. 5.2 or higher
CX-Process Tool CX-Programmer
(See note.)
---
xii

TABLE OF CONTENTS

PRECAUTIONS xxiii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 Intended Audience xxiv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 General Precautions xxiv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 Safety Precautions xxiv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 Application Precautions xxvi. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SECTION 1
Introduction 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-1 CX-Process Tool 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-2 Relationship with CX-Process Monitor 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-3 CX-Process Tool Specifications 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-4 Version Improvements 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-5 Function Blocks/ITEMs Incompatible with Earlier Versions 25. . . . . . . . . . . . . . . . . . . . . .
1-6 Connecting to the PLC 31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-7 Basic Operating Procedures 36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-8 Operations 44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SECTION 2
Preparations to Create Function Blocks 49. . . . . . . . . . . . .
2-1 Installing and Uninstalling the Software 50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-2 Overview of User Interface 69. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SECTION 3
Creating Function Blocks 97. . . . . . . . . . . . . . . . . . . . . . . . .
3-1 Creating Function Block 99. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-2 Using the CX-Process Monitor 132. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-3 Using the CX-Process Monitor Plus 138. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-4 Using SCADA Software 141. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-5 User Link Tables 159. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-6 Creating User-defined Blocks 173. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-7 Creating Step Ladder Program Instructions 180. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-8 Creating Sequence Tables 195. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-9 Displaying and Setting in Engineering Units 207. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-10 Displaying Loop Controller Memory Maps 212. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-11 Printing 216. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-12 Setting Options 224. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SECTION 4
Online Operation 235. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-1 Overview of Online Functions 236. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-2 Initial Settings for Online Connections 238. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-3 Downloading, Uploading and Comparing Data 251. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-4 Run/Stop Command 264. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-5 Monitor Run Status 266. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-6 Operation Check 270. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-7 Tuning 294. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-8 Backup and Recovery 306. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-9 Transferring Tag and Comment Data 309. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-10 Clear All 313. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-11 Controlling the CPU Unit 314. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-12 Password Protection 315. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SECTION 5
Troubleshooting 317. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-1 Troubleshooting 318. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-2 Error Codes 319. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xiii
TABLE OF CONTENTS
Appendices
A Table of LC Type Changes 323. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B ITEM Notation in Block Diagrams 325. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C Setting Segment Programs 329. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D Sequence Table Design Sheet 337. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Revision History 339. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xiv

About this Manual:

This manual describes the installation and operation of the WS02-LCTC1-EV5 CX-Process Tool software package and includes the sections described below. The CX-Process Tool is used to create and test func­tion blocks for the CS1W-LC001 Loop Control Unit, the CS1W-LCB01, CS1W-LCB05, and CS1W-LCB05-GTC Loop Control Boards, the CS1D-CPUP Process-control CPU Units, and the CJ1G-CPUP and CJ1G-CPUP-GTC Loop-control CPU Units.
In this manual, the WS02-LCTC1-EV5 CX-Process Tool software package is generally referred to as sim­ply the “CX-Process Tool.”
Please read this manual carefully and be sure you understand the information provided before attempting to install and operate the CX-Process Tool. Please read the following manuals carefully and be sure you understand the information provided before setting up or using an application for a Loop Control Unit/ Board.
xv
Product Manual name Cat. No. Contents
WS02-LCTC1-EV5 CX-Process Tool
CXONE-ALC-EV 2/ALD-EV2 CX-One Ver. 2.0 FA Integrated Tool Package
WS02-LCTC1-E CX-Process Monitor
WS02-LCMC1-E CX-Process Monitor Plus
CS1W-LC001 Loop Control Unit
CS1W-LCB01/05 Loop Control Boards, CS1D-CPUP Process-control CPU Units, and CJ1G-CPUP Loop-control CPU Units
CS1W-LC001 Loop Control Unit
CS1W-LCB01/05 Loop Control Boards, CS1D-CPUP Process-control CPU Units, and CJ1G-CPUP Loop-control CPU Units
CS1W-LCB05-GTC Loop Control Board with Gradient Temperature Controller CJ1G-CPU45P-GTC Loop-control CPU Unit with Gradient Temperature Controller
CX-Process Tool Operation Manual
CXONE-ALC-EV 2/ALD-EV2 CX-One Ver. 2.0 FA Integrated Tool Package Setup Manual
CX-Process Monitor Operation Manual
CX-Process Monitor Plus Operation Manual
Loop Control Unit Operation Manual
Loop Control Board Operation Manual
Loop Control Unit Function Block Reference Manual
Loop Control Board Function Block Reference Manual
Loop Control Board with Gradient Temperature Controller User’s Manual
W372 (this manual)
W463 Provides an overview of the
W373 Installation and operation
W428 Installation and operation
W374 Installation and operation
W406 Installation and operation
W375 Detailed information on function
W407 Detailed information on function
W460 Provides information required
Installation and operation procedures for the CX-Process Tool.
CX-One and describes the installation procedures for CX-One software.
Refer to this manual when installing the CX-Integrator from the CX-One.
procedures for the CX-Process Monitor.
procedures for the CX-Process Monitor Plus.
procedures for the Loop Control Unit (except for function blocks).
procedures for the Loop Control Boards (except for function blocks).
blocks for Loop Control Units.
blocks for Loop Control Boards
when using the gradient temperature control functions. For information not related to the gradient temperature control functions, please refer to the Loop Control Board Operation Manual (Cat. No. W406).
xvi
For details on procedures for installing the CX-Process Tool from the CX-One FA Integrated Tool Pack­age, refer to the CX-One Ver. 2.0 Setup Manual provided with CX-One.
Cat. No. Model Manual name Contents
W463
CXONE-ALC-EV 2/ALD-EV2
CX-One Ver.2.0 Setup Manual
Installation and overview of CX-One FA Integrated Tool Package.
Section 1 introduces the operations of the CX-Process Tool and connections to the PLC.
Section 2 describes installing the CX-Process Tool and provides an overview of the user interface.
Section 3 describes how to create and manipulate function blocks.
Section 4 describes online operations for uploading, downloading, and testing function block data.
Section 5 describes errors that can occur while using the CX-Process Tool.
!
WARNING Failure to read and understand the information provided in this manual may result in
personal injury or death, damage to the product, or product failure. Please read each section in its entirety and be sure you understand the information provided in the section and related sections before attempting any of the procedures or operations given.
xvii
xviii
Read and Understand this Manual
Á
Á
Á
Á
Á
Á
Á
Á
Á
Á
Á
Á
Á
Á
Á
Please read and understand this manual before using the product. Please consult your OMRON representative if you have any questions or comments.
Warranty and Limitations of Liability

WARRANTY

OMRON’s exclusive warranty is that the products are free from defects in materials and workmanship for
БББББББББББББББББББББББББББББББ
a period of one year (or other period if specified) from date of sale by OMRON.
БББББББББББББББББББББББББББББББ
OMRON MAKES NO WARRANTY OR REPRESENTATION, EXPRESS OR IMPLIED, REGARDING
БББББББББББББББББББББББББББББББ
NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR PARTICULAR PURPOSE OF THE
БББББББББББББББББББББББББББББББ
PRODUCTS. ANY BUYER OR USER ACKNOWLEDGES THAT THE BUYER OR USER ALONE HAS
БББББББББББББББББББББББББББББББ
DETERMINED THAT THE PRODUCTS WILL SUITABLY MEET THE REQUIREMENTS OF THEIR INTENDED USE. OMRON DISCLAIMS ALL OTHER WARRANTIES, EXPRESS OR IMPLIED.
БББББББББББББББББББББББББББББББ
БББББББББББББББББББББББББББББББ
LIMITATIONS OF LIABILITY
OMRON SHALL NOT BE RESPONSIBLE FOR SPECIAL, INDIRECT, OR CONSEQUENTIAL DAMAGES, LOSS OF PROFITS OR COMMERCIAL LOSS IN ANY WAY CONNECTED WITH THE
БББББББББББББББББББББББББББББББ
PRODUCTS, WHETHER SUCH CLAIM IS BASED ON CONTRACT, WARRANTY, NEGLIGENCE, OR
БББББББББББББББББББББББББББББББ
STRICT LIABILITY.
БББББББББББББББББББББББББББББББ
In no event shall the responsibility of OMRON for any act exceed the individual price of the product on
БББББББББББББББББББББББББББББББ
which liability is asserted.
БББББББББББББББББББББББББББББББ
IN NO EVENT SHALL OMRON BE RESPONSIBLE FOR WARRANTY, REPAIR, OR OTHER CLAIMS
БББББББББББББББББББББББББББББББ
REGARDING THE PRODUCTS UNLESS OMRON’S ANALYSIS CONFIRMS THAT THE PRODUCTS
БББББББББББББББББББББББББББББББ
WERE PROPERLY HANDLED, STORED, INSTALLED, AND MAINTAINED AND NOT SUBJECT TO
БББББББББББББББББББББББББББББББ
CONTAMINATION, ABUSE, MISUSE, OR INAPPROPRIATE MODIFICATION OR REPAIR.
xix
Application Considerations
Á
Á
Á
Á
Á
Á
Á
Á
Á
Á
Á
Á
Á
Á
Á
Á
Á
Á
Á
Á
Á
Á
SUITABILITY FOR USE
OMRON shall not be responsible for conformity with any standards, codes, or regulations that apply to
БББББББББББББББББББББББББББББББ
the combination of products in the customer’s application or use of the products.
БББББББББББББББББББББББББББББББ
At the customer’s request, OMRON will provide applicable third party certification documents identifying
БББББББББББББББББББББББББББББББ
ratings and limitations of use that apply to the products. This information by itself is not sufficient for a
БББББББББББББББББББББББББББББББ
complete determination of the suitability of the products in combination with the end product, machine,
БББББББББББББББББББББББББББББББ
system, or other application or use.
БББББББББББББББББББББББББББББББ
The following are some examples of applications for which particular attention must be given. This is not
БББББББББББББББББББББББББББББББ
intended to be an exhaustive list of all possible uses of the products, nor is it intended to imply that the
БББББББББББББББББББББББББББББББ
uses listed may be suitable for the products:
БББББББББББББББББББББББББББББББ
• Outdoor use, uses involving potential chemical contamination or electrical interference, or conditions
БББББББББББББББББББББББББББББББ
or uses not described in this manual.
БББББББББББББББББББББББББББББББ
• Nuclear energy control systems, combustion systems, railroad systems, aviation systems, medical
БББББББББББББББББББББББББББББББ
equipment, amusement machines, vehicles, safety equipment, and installations subject to separate
БББББББББББББББББББББББББББББББ
industry or government regulations.
БББББББББББББББББББББББББББББББ
• Systems, machines, and equipment that could present a risk to life or property.
БББББББББББББББББББББББББББББББ
Please know and observe all prohibitions of use applicable to the products.
БББББББББББББББББББББББББББББББ
БББББББББББББББББББББББББББББББ
NEVER USE THE PRODUCTS FOR AN APPLICATION INVOLVING SERIOUS RISK TO LIFE OR
БББББББББББББББББББББББББББББББ
PROPERTY WITHOUT ENSURING THAT THE SYSTEM AS A WHOLE HAS BEEN DESIGNED TO ADDRESS THE RISKS, AND THAT THE OMRON PRODUCTS ARE PROPERLY RATED AND
БББББББББББББББББББББББББББББББ
INSTALLED FOR THE INTENDED USE WITHIN THE OVERALL EQUIPMENT OR SYSTEM.
БББББББББББББББББББББББББББББББ
БББББББББББББББББББББББББББББББ
PROGRAMMABLE PRODUCTS
OMRON shall not be responsible for the user’s programming of a programmable product, or any
БББББББББББББББББББББББББББББББ
consequence thereof.
xx
Disclaimers
Á
Á
Á
Á
Á
Á
Á
Á
Á
Á
Á
Á
Á
CHANGE IN SPECIFICATIONS
БББББББББББББББББББББББББББББББ
Product specifications and accessories may be changed at any time based on improvements and other reasons.
БББББББББББББББББББББББББББББББ
БББББББББББББББББББББББББББББББ
It is our practice to change model numbers when published ratings or features are changed, or when significant construction changes are made. However, some specifications of the products may be
БББББББББББББББББББББББББББББББ
changed without any notice. When in doubt, special model numbers may be assigned to fix or establish
БББББББББББББББББББББББББББББББ
key specifications for your application on your request. Please consult with your OMRON representative
БББББББББББББББББББББББББББББББ
at any time to confirm actual specifications of purchased products.
БББББББББББББББББББББББББББББББ
DIMENSIONS AND WEIGHTS
Dimensions and weights are nominal and are not to be used for manufacturing purposes, even when tolerances are shown.
БББББББББББББББББББББББББББББББ
PERFORMANCE DATA
Performance data given in this manual is provided as a guide for the user in determining suitability and
БББББББББББББББББББББББББББББББ
does not constitute a warranty. It may represent the result of OMRON’s test conditions, and the users
БББББББББББББББББББББББББББББББ
must correlate it to actual application requirements. Actual performance is subject to the OMRON
БББББББББББББББББББББББББББББББ
Warranty and Limitations of Liability.
БББББББББББББББББББББББББББББББ
The information in this manual has been carefully checked and is believed to be accurate; however, no responsibility is assumed for clerical, typographical, or proofreading errors, or omissions.
БББББББББББББББББББББББББББББББ
ERRORS AND OMISSIONS
xxi
xxii

PRECAUTIONS

This section provides general precautions for using the CX-Process Tool, CS/CJ-series Programmable Controllers (PLCs), and related devices.
The information contained in this section is important for the safe and reliable application of Programmable Control­lers. You must read this section and understand the information contained before attempting to set up or operate a PLC system.
1 Intended Audience xxiv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 General Precautions xxiv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 Safety Precautions xxiv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 Application Precautions xxvi. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xxiii

1 Intended Audience

This manual is intended for the following personnel, who must also have knowl­edge of electrical systems (an electrical engineer or the equivalent) and instru­mentation systems (a process 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 specifications 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, amusement ma­chines, safety equipment, petrochemical plants, and other systems, machines, and equipment 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 Loop Con­troller. Be sure to read this manual before attempting to use the Loop Controller and keep this manual close at hand for reference during operation.

3Safety Precautions

WARNING It is extremely important that a PLC and all PLC Units/Boards be used for the
!
specified 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 applications.
3 Safety Precautions
WARNING Check the following items before starting to run the LCB:
!
• Do not allow the bank of the EM Area with the number specified for allocation to the HMI (human-machine interface) data to be used by the CPU Unit or other Units for any other purpose. The block allocated for the HMI is specified in ITEM 050 (EM Area Bank Allocated for HMI Memory = 0 to 12) of the System Common block. If areas overlap, the system may operate in an unexpected fashion, which may result in injury.
• Do not allow the area to which user link table data is written to be used by the CPU Unit or other Units for any other purpose. If areas overlap, the system may operate in an unexpected fashion, which may result in injury.
• Analog Input/Output Units used in combination with the LCB must be mounted correctly, and the unit number set on the front panel of the Analog Input/Output Unit must match the unit number set on the Field Terminal block. If the unit numbers do not match, input/output (read/write) is performed on the data of another Special I/O Unit (i.e., the one whose unit number is set on the Field Terminal block).
• The defaults of the System Common block on the LCB must be set correct- ly.
xxiv
WARNING Check the following items before starting Loop Controller operation:
!
Do not allow the area to which user link table data is written to overlap with any other area used by the CPU Unit or other Units. If areas overlap, the system may operate in an unexpected manner, which may result in injury.
When using a user link table to write bit data to I/O memory in the CPU Unit. Never allow ladder programming or communications processes in the CPU Unit to write to any bits in the words in which bits are written from a user link table. Depending on the timing, any attempts to write to these words from ladder pro­gramming or communications processes may be ignored. Example: If tag A in a user link table writes to bit 00 of W000 and an OUT instruction in the ladder pro­gram in the CPU Unit write to bit 01 of W000, the write from the ladder program may be ignored.
Analog I/O Units used in combination with the Loop Controller must be mounted correctly.
The unit number set on the front panel of the Analog I/O Unit must be the same as the unit number set on the Field Terminal Function Block. If the unit numbers are not the same, I/O (read/write) will be performed on the data for another Spe­cial I/O Unit (i.e., the one whose unit number is set in the Field Terminal Function Block).
The initial settings of the System Common Block in the Loop Controller must be set correctly. In particular, make sure that words in the Data Memory used for the Node Terminals in the CPU Unit controlling the Loop Controller are not used for other applications on the PLC.
When writing data to the I/O memory in the CPU Unit with function blocks (e.g., using Send All Blocks, Expanded DO/AO Terminal to CPU Unit, or DO/AO Ter­minal to CPU Unit), be sure that the words written to in I/O memory are not being used for any other purpose. If I/O memory words are allocated to more than one purpose, the PLC system may act unexpectedly and cause injury.
3Safety Precautions
WARNING Always stop the operation of the LCB before converting any of the EM Area
!
to file memory. If any part of the EM Area that is being used by the LCB for the HMI is converted to file memory during Board operation, the system may operate in an unexpected fashion, which may result in injury.
WARNING Do not perform processing in such a way that the Loop Controller and CPU Unit
!
write to identical I/O memory words allocated to a contact output or analog output of an external Unit. If the same words are written to, the externally connected loads may act unexpectedly and cause injury.
WARNING When the calibration function is executed, the MV (manipulated variable) will
!
change due to changes in the PVs (present values) input to the control block. Therefore, set pseudo-input values to confirm safety when the MW changes before executing the calibration function. Devices may perform unexpected operations, resulting in serious accidents.
Caution Before transferring function block data (initial setting data or operation data) to
!
the Loop Controller, confirm that the destination for the data is correct and also confirm the overall safety of the system (including the Loop Controller). Not do­ing so may result in unexpected operation.
Caution Before performing Validate Action, be sure to perform Compare on currently
!
opened function files and the Loop Controller’s function block data. If there are inconsistencies in the registered function blocks (block address vs. block mod­el), it will not be possible to perform Validate Action correctly.
xxv
Before forcing changes of analog signals or contact signals using Validate Ac­tion, confirm the safety of the instrumentation system as a whole. Not doing so
may result in unexpected operation.
Caution When downloading a sequence table for the LCB (unit ver. 1.5 or later) that
!
has been edited online with the CX-Process Tool version 3.2 or higher, confirm that the system will operate normally with the edited sequence. If the sequence is not suitable for operation, unexpected operation may result.
Caution Confirm in advance the conditions at any node for which the sequence table is
!
being edited over a Controller Link or Ethernet network. Not doing so may result in unexpected operation.
Caution Confirm the status of connected devices before transferring the setting for the
!
MV tight shut function and MV analog output reverse function to the Loop Con­troller. Devices and equipment may perform unexpected operations if the data destination is mistaken.
Caution When the calibration function is executed, the MV (manipulated variable) will
!
change due to changes in the PVs (present values) input to the control block. Therefore, set pseudo-input values to confirm safety when the MW changes be­fore executing the calibration function. Devices may perform unexpected opera­tions, resulting in serious accidents.

4Application Precautions

4 Application Precautions
Observe the following precautions when using CX-Process Tool and Loop Con­troller.
Caution If the power supply is turned OFF while function block data is being backed up
!
from RAM to flash memory, the backup will not be completed normally. If the power supply is turned back ON within 24 hours, however, the super capacitor will have held the RAM data. The backup operation will restart when power is turned ON and operation will start when the backup has been completed. If the power supply is turned OFF for more than 24 hours, however, RAM data will be lost and operation will be started with the data that was previously saved to flash memory. If this happens, the Cold Start Auto-execution Flag (A35807) will turn ON to show that the previous data has been used. Use this bit in programming to take whatever steps are necessary, such as downloading the most recent func­tion block data. (For LCB only)
Caution Loop Control Unit data is monitored and operated using CX-Process Monitor or
!
CX-Process Monitor Plus based on the monitor tag files created using CX-Pro­cess Tool. When creating monitor tag files using CX-Process Tool, CX-Process Monitor must be installed on the same computer.
Caution Before using function block data in actual operation, confirm operation by moni-
!
toring run status (to check the load rate; select Execute/Operation/Monitor Run Status) and validating actions (select Validate Action/Start) with CX-Pro-
cess Tool. In particular, be sure to confirm that the load rate will be less than 60%. (For details on the load rate, refer to the Operation Manual for the Loop Control­ler.)
xxvi
Caution When uploading the Loop Controller’s function block data, observe the following
!
precautions.
When performing Upload New for Loop Control Units of version 1.5 or earlier, data on the Edit Block Diagram Screen (function block information) will be lost, and the block diagram showing the connections between function blocks will not be displayed.
When performing Upload Previous, if the data in the source file currently opened using the CX-Process Tool and the Loop Controller’s function block data does not match the registered function blocks or the data on the Edit Block Dia­gram Screen, the data currently opened may change to illegal data.
Caution The Loop Controller can read and write I/O memory in the CPU Unit using the
!
Field Terminal Function Blocks or CPU Terminal Blocks independent of the user program (Step Ladder Program) in the CPU Unit. Do not write to the same I/O memory words from both the Loop Controller and the CPU Unit.
Caution To hold an analog output or contact output at a specific value (for example, the
!
maximum value or minimum value) when the Loop Controller stops running, create a Step Ladder Program in the CPU Unit so that the corresponding output bit allocated to Analog Output Unit or Contact Output Unit is set to the desired value using an NC condition of the Loop Controller Running Flag (bit 00 in allo­cated CIO word “n”) as an input condition.
4Application Precautions
Caution If a fatal error occurs in the CPU Unit (including fatal errors created by execution
!
of a FALS instruction), the Loop Controller will also stop running. To hold analog outputs to the previous values before the stop occurred, and to set analog out­puts to either the minimum value or maximum value, use the output hold function of the Analog Output Unit or Analog I/O Unit.
Caution Before turning ON the power to the PLC, make sure that the facilities are safe.
!
The analog output values and contact outputs from the Loop Controller are up­dated when the power to the PLC is turned ON regardless of the operating mode of the CPU Unit (including in the PROGRAM mode). (Internally, the analog out­put values and contact outputs are sent from the CPU Unit to Basic I/O Units and Analog Output Units.)
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, mo­mentary power interruptions, or other causes.
Caution Confirm that no adverse effect will occur in the system before attempting any of
!
the following:
• 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 or any set value in memory
Caution Be sure that all mounting screws, terminal screws, and cable connector screws
!
are tightened to the torque specified in the user manuals. Incorrect tightening torque may result in malfunction.
xxvii
Caution In the event of system or power failure, CX-Process function files (extension
!
“.ist”) may not be saved. It is recommended that function files are saved regular­ly.
Caution 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.
4Application Precautions
xxviii
This section introduces the operations of the CX-Process Tool and connections to the PLC.
1-1 CX-Process Tool 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-1-1 Overview 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-1-2 Project Workspace 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-1-3 Files Created with CX-Process Tool 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-1-4 Relationships between Tag Files 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-1-5 Operating Conditions of CX-Process Tool 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-2 Relationship with CX-Process Monitor 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-2-1 Overview of the CX-Process Monitor and CX-Process Monitor Plus 9. . . . . . . . .
1-2-2 Settings Required on the CX-Process Tool 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-3 CX-Process Tool Specifications 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-4 Version Improvements 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-4-1 Version 1.20 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-4-2 Version 1.50 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-4-3 Version 2.00 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-4-4 Version 2.50 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-4-5 Version 3.00 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-4-6 Version 3.1 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-4-7 Version 3.2 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-4-8 Version 4.0 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-4-9 Version 4.1 22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-4-10 Version 5.0 23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-4-11 Version 5.1 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-4-12 Version 5.2 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-5 Function Blocks/ITEMs Incompatible with Earlier Versions 25. . . . . . . . . . . . . . . . . . . . . . .
1-5-1 Incompatibility with Versions Earlier than Version 1.20 25. . . . . . . . . . . . . . . . . . . .
1-5-2 Incompatibility with Versions Earlier than Version 1.50 25. . . . . . . . . . . . . . . . . . . .
1-5-3 Incompatibility with Versions Earlier than Version 2.00 26. . . . . . . . . . . . . . . . . . . .
1-5-4 Incompatibility with Versions Earlier than Version 2.50 28. . . . . . . . . . . . . . . . . . . .
1-5-5 Incompatibility with Versions Earlier than Version 3.2 29. . . . . . . . . . . . . . . . . . . . .
1-5-6 Incompatibility with Versions Earlier than Version 4.0 30. . . . . . . . . . . . . . . . . . . . .
1-5-7 Incompatibility with Versions Earlier than Version 5.0 30. . . . . . . . . . . . . . . . . . . . .
1-5-8 Incompatibility with Versions Earlier than Version 5.2 30. . . . . . . . . . . . . . . . . . . . .
1-6 Connecting to the PLC 31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-6-1 Features of FinsGateway and CX-Server 31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-6-2 Selecting the Communications Driver 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-6-3 Using FinsGateway 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-6-4 Connecting Cables 35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-7 Basic Operating Procedures 36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-8 Operations 44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-8-1 Creating Function Blocks 44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-8-2 Online Operations 46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SECTION 1
Introduction
1

1-1 CX-Process Tool

1-1-1 Overview
The CX-Process Tool supports the following functions for Loop Controllers.
In this manual, the WS02-LCTC1-EV5 CX-Process Tool software package is generally referred to as simply the “CX-Process Tool.”
• Creating function blocks, including the following functions
1-1SectionCX-Process Tool
• Setting the Step Ladder Program Block (block 000), including the follow­ing: System common operation cycle, Loop Control Unit number (Loop Control Unit only), start mode, first address of data memory of node termi­nal (Loop Control Unit only)
• Registering function blocks (allocating block addresses)
• Connecting function blocks with analog and accumulator signals
• Setting ITEMs in function blocks
• Editing sequence tables (Block 302) and the Step Ladder Program Block
(Block 302) (See note.)
Note Editing sequence tables is supported only by the CS1W-LCB05 Loop
Control Board (00-LCB05) and CS1D-LCB05D Loop Control Board (00-LCB05D).
• Settings tags for CX-Process Monitor (Loop Control Unit only) or CX-Pro­cess Monitor Plus software or setting CSV tags for SCADA software (Tag Names and Analog Signals) and creating monitor tag files (Loop Control Unit only, CX-Process Monitor must be already installed), or CSV tag files.
• Downloading function block data to Loop Controllers
• Uploading data from Loop Controllers
• Comparing function block data with data in a Loop Controller or Function Block
File
• Sending Run/Stop Commands to Loop Controller
• Monitoring status (including System Common Block Settings, Load Rate per
Operation Cycle Group, and Execution Errors)
• Monitoring actions of Loop Controllers (including operation checks on function block diagrams and ladder diagrams)
• Tuning parameters such as PID constants in function blocks (Control Blocks)
• Backing up function block data from the Loop Controller’s RAM to flash
memory and restoring that function block data from flash memory back to RAM
• Initializing function block data in Loop Controllers
Note To create monitor tag files using the CX-Process Tool with the CX-Process Moni-
tor or CX-Process Monitor Plus software, both the CX-Process Tool, and CX­Process Monitor or CX-Process Monitor Plus, must be installed on the same computer.
2
1-1-2 Project Workspace
Project Workspace can be used to access the data created in memory with the CX-Process Tool. Data can be created for up to 32 CPU Units and 96 Loop Con­trol Units (3 Loop Control Units each for 32 CPU Units) or 32 LCBs (1 LCB each for 32 CPU Units). The data has the following configuration.
1-1SectionCX-Process Tool
LCU/LCB Elements (one for each Loop
Function Block File for Each Node (.ist)
Node01.ist
Node02.ist
Project Workspace
Node32.ist
Project file (.mul)
Controller)
00-LCB03
00-LCB01
00-LCB05
00-LCB05D
01-LC001
02-LC001
03-LC001
Project Workspace data is stored in one folder called the project folder. Project folders are created for the following commands.
• File – New
When a new project is created, the project name will be used as the folder name.
• File – Save As
When a project is saved under a new name, the new project name will be used as the folder name.
1-1-3 Files Created with CX-Process Tool
Function Block Groups
System common
Field terminals
Block diagrams
Function Blocks
Basic PID
Project File (.mul)
The CX-Process Tool creates a folder with the project name in the data folder under the default installation folder for the CX-Process Tool, and then creates the following files inside the project folder.
The project file consists of administrative data for the Project Workspace.
Files File name
extension
Function block files .ist
Block diagram information files .mtbd
Mnemonics/Ladder diagram information files
Comment files .cmt
CSV tag setting files project_name.csv
CX-Server configuration files .cdm Only when CX-Server is
Job information files .sjb
Loop Controller configuration files
Data files of user link tables LnkTable.csv
Data files of sequence tables .stbl
.mtld
selected as the communications driver
.lcb
Remarks
The project file (.mul) can be specified when opening files so that the above re­lated files will be all read at the same time. The project file is created by selecting New from the File Menu and specifying the project name. The file name will be the same as the project name.
3
1-1SectionCX-Process Tool
Function Block Files (.ist)
A function block file consists of the data for the function blocks of a single CPU Unit (i.e., for up to three LCU elements and/or one LCB element). This file is created by selecting Settings – Insert. The file will be automatically named “Node XX,” where XX denotes the node number between 01 and 32.
The following data is contained in a function block file.
Item Data name Description
Function block data for one Loop Controller
Initial settings (S) Data on registered function blocks
(block address allocations), analog/accumulator signal software connections, and initial settings of each function block.
Operation data (O) Operation data for each function block
The contents of the function block file (.ist) are used to compare download data and upload data. Initial settings (S), operation data (O), or initial settings and op­eration data together can be set in the function block file.
Note 1. The function block file does not include mnemonic data for Step Ladder Pro-
gram Blocks. The mnemonic data is stored in the mnemonics/ladder dia­gram information file. Refer to Mnemonics/Ladder Diagram Information File
(.mtld) Created by System
below.
2. Function block files (.ist) created for the CX-Process Tool can be imported to the Project Workspace data by selecting Add Function Block File from the File Menu.
Block Diagram Information Files (.mtbd)
Mnemonics/Ladder Diagram Information Files (.mtld)
The block diagram information file consists of graphic data that shows the soft­ware connections.
The system will automatically store this file with the function block file (.ist) in the same folder whenever a block diagram is edited. The user does not normally need to access the block diagram information file directly.
Note 1. When backing up or changing the storage location of this file, the file must be
backed up or moved together with the node function block files because these files must always be in the same folder. The block diagram information files are named as shown below.
File name and extension: Name of function block file   .mtbd
Function block group
LCU/LCB number (04 for LCB)
2. The block diagram information file (.mtbd) is not used for downloading, uploading, or comparing data, but the block diagram information between function blocks (i.e., ITEM data) is uploaded and downloaded if the Loop Control Unit is version 2.00 or later or an LCB is used. Thus, newly uploaded data will have connection diagrams displayed between function blocks. (This is not actually the same as the connection diagram information file, and even though connections themselves will be restored, complex connections will be normalized for display.)
A mnemonics/ladder diagram information file consists of mnemonic data and ladder diagram data for sequence instructions in step ladder programs.
The system will automatically store this file with the function block file (.ist) in the same folder whenever a Step Ladder Program Block is registered. The user does not normally need to access the mnemonics/ladder diagram information file directly.
Note 1. When backing up or changing the storage location of this file, the file must be
backed up or moved together with the node function block files because
4
CX-Process Monitor Tag Files (with Fixed File Name without Extension)
CX-Process Monitor Plus Tag Files (monitor.csv) (CX-Process Tool Ver. 3.2 or Higher)
CSV Setting File (project_name.csv)
1-1SectionCX-Process Tool
these files must always be in the same folder. The mnemonics/ladder dia­gram information files are named as shown below.
File name and extension: Name of function block file   .mtld
Block address
LCU/LCB number (04 for LCB)
2. The mnemonic data in the mnemonics/ladder diagram information file (.mtld) is used in downloading, uploading, or comparing data but the ladder diagram data is not.
A CX-Process Monitor tag file consists of monitor tag data (binary data) for a single CPU Unit (with a maximum of three Loop Control Units).
CX-Process Monitor tag data consists of tag names, tag comments, corre­sponding ITEM numbers or block addresses, and analog signal scaling data. By reading the tag file with the CX-Process Monitor, the block address or ITEM number in function block data corresponding to the CX-Process Monitor tag on each screen can be specified.
The CX-Process Monitor tag file is created by selecting Create Tag File – Moni- tor Tag from the Execution Menu.
Note 1. It is necessary to install the CX-Process Monitor on the same computer be-
fore creating monitor tag files.
2. Monitor tag files are stored by default in the following folder with fixed file names. Folder: Omron\CX-Process Monitor\ (The underlined part is the folder of CX-Process Monitor.)
File names: mtagmst and mtagsubmst You can change the folder in which monitor tag files are stored using the Monitor Software from the Setup Dialog Box.
3. CX-Process Monitor tag files are not used when comparing, downloading, or uploading data.
A CX-Process Monitor Plus tag file contains the CX-Process Monitor Plus tag data for a single CPU Unit (with a maximum of three Loop Control Units).
CX-Process Monitor Plus tag data consists of tag names, tag comments, corre­sponding ITEM numbers or block addresses, and analog signal scaling data. By reading the tag file with the CX-Process Monitor Plus, the block address or ITEM number in function block data corresponding to the CX-Process Monitor tag on each screen can be specified.
The CX-Process Monitor tag file is created by selecting Create Tag File – Moni- tor Plus Tag from the Execution Menu. If the CX-Process Monitor Plus is then started and the Start Button is pressed, the monitor tag files mtagmst and mtag- submst will be automatically generated. If the monitor tag files are read from the CX-Process Monitor, the block addresses or ITEM numbers in the function block data corresponding to the monitor tag names pasted on the screen can be se­lected.
Note 1. It is necessary to install the CX-Process Monitor Plus on the same computer
before creating monitor tag files.
2. CX-Process Monitor tag files are stored by default in the following folder with fixed file names. Folder: Omron\CX-Process Monitor Plus\
3. CX-Process Monitor Plus tag files are not used when comparing, download­ing, or uploading data.
The CSV setting file contains the CSV tag settings required to output a CSV tag file for SCADA software. This data is automatically generated in advance by the system. It can be edited by the user using Excel or another editor.
db
db
5
1-1SectionCX-Process Tool
The file contains the tag names, tag comments, scaling upper limits, scaling low­er limits, scaling decimal point, units, and other settings for each function block. The data is comma delimited.
Note This file does not contain the tags for individual ITEMs in function block or ad-
dress allocations for CPU Unit I/O memory. (These are stored in the CSV tag files for SCADA software after the CSV tags have been compiled.)
This file is automatically generated after CSV tag settings have been made after selecting Settings – Tag Setting – CSV Tag or (for CX-Process Tool software version 3.1 or higher) when function blocks are saved in function block files after selecting the automatic CSV tag registration option when registering function blocks.
This file is saved in the data project folder under the CS-Process installation folder as project_name.csv.
The CSV automatic tag registration function can be used with version 3.1 or higher to automatically save CSV tag settings in this file when function blocks are registered. The tag name will be Tag + block address, the scaling upper limit will be 1,000, and the scaling lower limit will be 0.
If this file is edited with Excel or another editor and overwritten, the new settings will be read when the project is opened.
CSV Tag Files for SCADA Software (.csv, Default File Name: TagList.csv)
Tag Files for RS View (.csv, User-set File Name)
A CSV tag file can contain CSV tag data for up to 32 CPU Units (i.e., up to 96 Loop Control Units and 32 LCBs).
CSV tag data consists of comma-delimited test data containing tag names, num­bers, tag comments, block addresses, tag ITEMs, and allocated I/O memory ad­dresses (in CPU Unit).
The CSV tag file can be read from SCADA software via an OMRON OPC Server to specify block addresses and ITEM numbers in the function block data of the Loop Controller.
Settings – Tag Setting – CSV Tag is used to set CSV tags for each function block, and Execute/Create Tag File/CSV Tag is used to allocate I/O memory ad- dresses in the CPU Unit and compile a CSV tag file.
Note 1. CSV tag files are not downloaded, uploaded, or compared.
2. Basically speaking, CSV tag files are imported to SCADA software through an OMRON OPC server.
An RS View tag file can contain CSV tag data for up to 32 CPU Units (i.e., up to 96 Loop Control Units and 32 LCBs) for direct importing into RS View 32. Any file name can be specified.
The RS View tag file can be directly imported using the RS View import utility. This file is created together with the SCADA CSV tag file when the RS View CSV tags are compiled using Execute/Create Tag File/RS View Tag. When this file is imported into the RS View 32 using the import utility, the ITEMs and tags speci­fied with CSV tag settings are registered in the tag database in the RS View 32 project.
Comment Files (.cmt)
CX-Server Settings File (.cdm)
6
Note 1. RS View tag files are not downloaded, uploaded, or compared.
2. The SYSMAC OPC Server Version 2.40 or higher is required to generate an RS View tag file from the CX-Process Tool.
A comment file contains of the tag data attached to a function block connection diagram or step ladder diagram.
The file name is automatically set to the same name as the project.
This file contains the communications settings for communications with the PLC when CX-Server is being used as the communications driver.
The file name is automatically set to the same name as the project.
1-1SectionCX-Process Tool
Job Information Files (.sjb)
The job information file consists of data on the registration of jobs for Project Workspace.
The file name is automatically set to the same name as the project.
Loop Controller Configuration Files (.lcb)
Data Files of User Link Tables (CSV Format) (LnkTable.csv) (LCB Only)
Data Files of Sequence
The Loop Controller configuration file is a system file that includes data on the existence of Loop Controllers in the project.
The data file of user link table consists of user link table data that can be edited by the user. If this file is edited using Excel, for example, the editing results will be reflected in the user link table when the project is opened or when the active node is switched.
The data file of sequence table consists of sequence table data.
Tables (.stbl)
1-1-4 Relationships between Tag Files
The relationships between the tag files created by the CX-Process Tool and the HMI applications that use these files are shown below. The HMI applications that use the tag files include NS-series PTs, SCADA software, the CX-Process Moni­tor, and the CX-Process Monitor Plus.
Imported Imported
NS Face Plate Auto Builder
NS project file (.ipp, binary)
Outputs CSV tag file.
Execute/Create Tag File/CSV Tag
CSV tag file for SCADA software (Taglist.csv)
SYSMAC OPC Server
RS View tag file (***.csv)
Manually exported.
Automatically generated.
OPC tag settings file (.sdb, binary)
CX-Process Tool
Outputs RS View tag file.
Execute/Create Tag File/RS View Tag
CSV tag file for SCADA software (Taglist.csv)
SYSMAC OPC Server version 2.4 or higher
RS View tag file (***.csv)
(CX-Process Tool version
3.2 or higher)
Automatically generated.
Automatically generated.
Outputs CX-Process Monitor tag file.
Execute/Create Tag File/Monitor Tag
CX-Process Monitor Plus tag file (monitor.csv)
CX-Process Monitor Plus tag file automatically generated when Start Button is clicked.
(CX-Process Tool version
3.2 or higher)
Outputs CX-Process Monitor Plus tag file.
Execute/Create Tag File/Monitor PlusTag
CX-Process Monitor tag file (mtagmst, mtagsubmst)
NS-series PT
Imported using import utility.
RS View
Imported using import utility.
CS-Process Monitor Plus
CS-Process Monitor
7
1-1-5 Operating Conditions of CX-Process Tool
As shown below, the CX-Process Tool uses a FinsGateway (Embedded), Ver­sion 2003, or CX-Server communications driver to communicate with the PLC (Programmable Controller) to which a Loop Controller is mounted. It is thus nec­essary to install the FinsGateway (Embedded), Version 2003, or CX-Server software in the personal computer that will be used.
Note When the CX-Process Tool starts up, a dialog box is displayed to select whether
FinsGateway or CX-Server will be used as the communications driver.
1-1SectionCX-Process Tool
Using FinsGateway
The following FinsGateway (Embedded) communications drivers are available.
• Serial Unit Driver
• CLK (PCI) Driver
• Controller Link Driver
• ETN_UNIT Driver
The software configuration is shown below.
CX-Process Tool CX-Process Monitor
Software
FinsGateway (Embedded)
Hardware
RS-232C port
Controller Link Support Board (PCI or ISA)
Ethernet Board
Note 1. If FinsGateway (Embedded) has not been installed, it will not be possible to
set FinsGateway as the communications driver and start the CX-Process Tool. Likewise, if CX-Server has not been installed, it will not be possible to set CX-Server as the communications driver and start the CX-Process Tool.
2. The CX-Process Tool cannot use FinsGateway version 1 as the commu­nications driver. Use FinsGateway version 3 or later.
3. If any other Support Software (e.g., the CX-Programmer, CX-Protocol, or CX-Motion) is connected over the CX-Server or an application using the dedicated serial driver is connected, the same COM port cannot be initial­ized for online Host Link serial communications for the CX-Process Tool. Disconnect the other Support Software or the application using the dedi­cated serial driver offline, and then go online with the CX-Process. (While the CX-Process Tool is connected online, no other Support Software can communicate via the CX-Server.)
4. The CX-Process Tool and FinsGateway Version 1 cannot be installed on the same computer.
5. The CX-Process Tool runs on Windows NT 4.0 (with Service Pack 6a or higher).
6. FinsGateway version 3 and FinsGateway 2003 (Embedded) are bundled to­gether with the CX-Process Tool. If the FinsGateway Runtime version 3 has been already installed, there is no need to install the FinsGateway em­bedded version.
Using CX-Server
8
The CX-Server is a communications driver shared by the following OMRON Tools:
• CX-Programmer
• CX-Protocol
• CX-Motion
The CX-Server has the following advantages:
• If the CX-Server is being used, one of the three Tools listed above can be started at the same time as the CX-Process Tool and simultaneous online con­nections can be established with the same PLC through the same COM port on
1-2SectionRelationship with CX-Process Monitor
the personal computer. The simultaneous online connections make it unnec­essary to switch between communications drivers or switch the Tools between online/offline operation.
• If the CX-Server is being used, Peripheral Bus mode can be used as a serial communications mode. The Peripheral Bus mode provides even faster com­munications than Host Link mode.
Note The CX-Process Monitor software is not compatible with the CX-Server; it is
compatible with the FinsGateway only. The following diagram shows the soft­ware configuration.
CX-Process Tool
Software
Hardware
CX-Programmer
RS-232C port
CX-Server
CX-Protocol
FinsGateway NSB Driver (See note.)
Controller Link, Ethernet
CX-Motion, etc.
Note The CX-Server can be connected to other networks, such as Controller Link and
Ethernet, through the FinsGateway NSB driver.

1-2 Relationship with CX-Process Monitor

1-2-1 Overview of the CX-Process Monitor and CX-Process Monitor Plus
The CX-Process Monitor is used to monitor function blocks in Loop Controllers. The CX-Process Monitor does not support the LCBs. The CX-Process Mon­itor Plus is used to monitor function blocks in LCBs. A connection can be made through Host Link, Controller Link, or Ethernet so that the data can be monitored on the Control Screens (like on-site instruments), Trend Screens, Graphic Screens, or Annunciator Screens. The CX-Process Monitor and CX­Process Monitor Plus are used in combination with the CX-Process Tool.
The CX-Process Monitor and CX-Process Monitor Plus have the following three main functions.
Monitoring Status of Function Blocks in Loop Controllers
Control Block PVs, SPs, MVs, analog signals, and contact signals can be moni­tored.
Loop Controllers can be started and stopped. The status of the CPU Unit, such as the operating mode, can be displayed.
Manipulating Function Blocks in Loop Controllers
In Control Blocks, settings can be changed, automatic or manual operation can be selected, manual control is possible, and PID constants can be adjusted.
It is possible to stop the processing of specific Control Blocks on a Tuning Screen.
Monitoring Alarms in Function Blocks in Loop Controllers
Alarms from Control and Alarm Blocks can be displayed and alarm logs can be saved.
Note The CX-Process Monitor and CX-Process Monitor Plus use FinsGateway as the
communications driver for connections with the PLC. When using the CX-Pro­cess Monitor or CX-Process Monitor Plus, always set FinsGateway as the com­munications driver for the CX-Process Tool. If the CX-Server is set, the CX-Pro­cess Monitor or CX-Process Monitor Plus will not be able to go online with the PLC.
1-2-2 Settings Required on the CX-Process Tool
The CX-Process Monitor and CX-Process Monitor Plus use tag names set on the CX-Process Tool to read and write data in Loop Control Units through func-
9
CX-Process Monitor
1-2SectionRelationship with CX-Process Monitor
tion blocks for data exchange with the monitor software. Before using the CX­Process Monitor or CX-Process Monitor Plus, the following settings must be made with the CX-Process Tool.
Set Network Address, Node Address, and Unit Address.
Register Function Blocks for Data Exchange.
Set Tag Names.
Create a Monitor Tag File for CX-Process Monitor.
The CX-Process Monitor uses the network address, node address, and unit ad­dress set using the CX-Process Tool (Setting – Network Settings or Setting – Change PLC) for communications with the PLC. The communications settings for the CX-Process Monitor Plus are thus made from the CX-Process Tool.
Create a Send Terminal to Computer Function Block or certain other function blocks (with a block model between 401 and 404) with the CX-Process Tool to specify the function block, the analog signals (including parameters), or the con­tact signals (including parameters) as the source for data exchange with the computer. Also, create AO Terminal Settings from Computer or DO Terminal Settings from Computer Function Block to enable receiving analog signals or contact signals from the computer.
Using the CX-Process Tool, set tag names for the function blocks, analog sig­nals (including parameters), or contact signals (including parameters) specified as sources. Also, set tag names for the analog or contact outputs of the AO Ter­minal Settings from Computer or DO Terminal Settings from Computer Function Blocks. It is also necessary to set the zero point, span point, decimal place, and scaling of engineering units.
Create the monitor tag file to transfer the created tag data to the CX-Process Monitor. The CX-Process Monitor must be installed before creating the monitor tag file.
Download Function
Download the function blocks.
Block Data to Loop Control Unit.
CX-Process Monitor Plus
Set Network Address, Node Address, and Unit Address.
Register and Connect Function Blocks To Exchange Data with CX-Process Monitor Plus.
Item Loop Control Unit
Function block data to exchange
Contact signals to exchange Contact Distributor (Block Model 201) or Internal Switch (Block Model 209)
Analog signals to exchange Input Selector block (Block Model 162) and Constant Generator block (Block Model 166)
The CX-Process Monitor Plus uses the network address, node address, and unit address set using the CX-Process Tool (Setting – Network Settings or Setting – Change PLC) for communications with the PLC. The communications set­tings for the CX-Process Monitor Plus and thus made from the CX-Process Tool.
The function blocks used to exchange data with the CX-Process Monitor Plus must be registered and connected. Register the following blocks for the items to be monitored.
LCB
Send All Blocks block (Block Model 462) and Receive All Blocks block (Block Model 461)
HMI settings in the System Common block (Block Mode 000)
10
1-2SectionRelationship with CX-Process Monitor
Block to input analog signals from the CX-Process Monitor Plus.
Blocks to monitor function block ITEM tags from the CX­Process Monitor Plus.
Set CSV Tags and Tags for CX-Process Monitor Plus.
1, 2, 3... 1. Register the Send All Blocks block (Block Model 642) and Receive All
Main function blocks Block to output analog signals to
Blocks to manipulate or display contacts from the CX-Process Monitor Plus.
the CX-Process Monitor Plus.
Loop Control Units
Blocks block (Block Model 641).
2. Set tags as follows:
• Function block data: Set CSV tags.
• Individual contact signals: Set CX-Process Monitor Plus tags for the con-
tacts in the Internal Switch block (Block Model 209).
• Individual analog signals from LCB element to computer: Set CX-Process Monitor Plus tags for the analog signals in the Input Selection block (Block Model 162).
• Individual analog signals from computer to LCB element: Set CX-Process Monitor Plus tags for the analog signals in the Constant Generator block (Block Model 166).
s
LCB
1, 2, 3... 1. Make the settings for the HMI in the System Common block (Block Model
000).
2. Set tags as follows:
• Function block data: Set CSV tags.
• Individual contact signals: Set CX-Process Monitor Plus tags for the con-
tacts in the Internal Switch block (Block Model 209).
• Individual analog signals from LCB element to computer: Set CX-Process Monitor Plus tags for the analog signals in the Input Selection block (Block Model 162).
• Individual analog signals from computer to LCB element: Set CX-Process Monitor Plus tags for the analog signals in the Constant Generator block (Block Model 166).
Note For any Loop Controller, the following function blocks must be
created and connected separately to enable monitoring and setting individual contact signals and individual analog signals (i.e., other than function block data).
11
1-2SectionRelationship with CX-Process Monitor
• To monitor and set individual contact signals, contact signals must be input/output using the Contact Distributor block (Block Model 201) and Internal Switch block (Block Model 209).
• To monitor individual analog signals, analog signals must be output from the Input Selection block (Block Model 162).
• To set individual analog signals, analog signals must be input to the Constant Generator block (Block Model 166).
Generate CX-Process Monitor Plus Tag File.
Download Function
Generate the CX-Process Plus tag file using Execute – Create Tag File – Moni­tor Plus Tag.
Download the function blocks.
Block Data to Loop Controller.
Compile the Monitor Tag Files.
Start the CX-Process Monitor Plus and click the Start Button or the Setup But­ton. The monitor tag files (mtagmst and mtagsubmst) will be automatically gen­erated based on the CX-Process Monitor Plus tag file (monitor.csv).
Setting Initial Data ITEMs
The CX-Process Tool is normally used to set initial data S and the CX-Process Monitor is normally used to set operation data O.
Data
classification
Initial settings S Initial setting parameter
Operation data O Operation parameters
Type ITEM Example: PID Block CX-Process
for each function block
for each function block
Note Initial settings S and operation data O classifications are displayed on ITEM Set-
ting Screens of the CX-Protocol Tool. For details on the ITEMs set in each func­tion block, refer to the Function Block Reference Manual.
Forward/Reverse direction, SP setting method, compensation method, etc.
Example: PID Block SP, alarm settings, PID constants, etc.
CX-Process
Tool
Set Cannot be
Set in special cases
Monitor
set
Set
12
Example
ITEM type ITEM Contents
Parameter 004 Operation cycle (s) R/W (S) ---
Parameter
Parameter
008 High/Low alarm R/W (O) R/W
012 Hysteresis set value R/W (S) ---
023 Local SP set value R/W (O) R/W
024 SP set method (Initial setting)
0: Local, 1: Remote/Local
R: Read, W: Write,
R/W: Read/write,
---: R/W disabled
r, t/w: CX-Process Tool
operation monitor/Operation
monitor read and write
(S): Initial setting,
(O): Operation data
CX-Process
Tool
R/W (S) R
CX-Process
Monitor
Note Analog values are normally set with the CX-Process Monitor. They can be set
with the CX-Process Tool provided that they are in percentage increments be­tween 0% and 100%. Scaling engineering units cannot be set with the CX-Pro­cess Tool.

1-3 CX-Process Tool Specifications

pp
CX-Process Tool Specifications
Item Specification
Product name CX-Process Tool
Model WS02-LCTC1-EV5
Applicable PLCs CS/CJ-series PLCs
Applicable Units/Boards Loop Control Units, Loop Control Boards, Process-control CPU Units, Loop-control
CPU Units
1-3SectionCX-Process Tool Specifications
Applicable computer
Software that must be installed with the CX-Process Tool
Connecting method
Computer IBM PC/AT or compatible
CPU Intel CPU (Core, Pentium, or Celeron family)
OS Microsoft Windows Vista Ultimate or Business, XP Professional (up to Service Pack
Supported languages
Memory For Windows Vista: 1 GB min.
Hard disk space Min. required: 350 Mbytes of free space, Recommended: 450 Mbytes or more of free
Monitor Min. required: XGA, 256 colors; Recommended: SXGA, 65,536 colors min.
CD-ROM drive At least one
Mouse Recommended: Microsoft mouse or compatible pointing device
Connection with CPU Unit (or Serial Communications Board/Unit)
Connection via Controller Link
Connection via Ethernet
For Windows Vista: 1 GHz min. For any other OS: 333 MHz min. required, 1 GHz min. recommended
2), 2000 Professional (Service Pack 3 or higher), ME, NT Workstation (Service Pack 6a or higher), 98 SE (See note 1.)
English
For any other OS: 256 MB min. required, 512 MB min. recommended
space
(including approx. 280 Mbytes used by communications middleware)
CX-Server or FinsGateway
Using FinsGateway Serial Unit Driver
Using CX-Server Communications protocol with PLC: Host Link or Peripheral
Using FinsGateway CLK (PCI) Driver
Using FinsGateway Controller Link Driver or CX-Server
Using FinsGateway ETN_UNIT Driver or CX-Server
Communications protocol with PLC: Host Link (A peripheral bus (toolbus) connection cannot be used.)
• Connect the computer to the peripheral port or built-in RS-232C port of the CPU Unit, or the RS-232C port of a Serial Communications Unit/Board.
• Connecting cable:
When connecting to the CPU Unit peripheral port: CS1W-CN (2 m, 6 m)
When connecting to the CPU Unit’s RS-232C port: XW2Z-- (2 m, 5 m)
(For details on model numbers, see 1-6-4 Connecting Cables)
Bus
(The compatible connecting cables are the same as the ones shown above for the FinsGateway connection.)
Install the driver in a computer equipped with a Controller Link Support Board (PCI slot) to support communications between the computer and PLCs equipped with a Controller Link Unit.
Install the driver in a computer equipped with a Controller Link Support Board (ISA slot) to support communications between the computer and PLCs equipped with a Controller Link Unit.
Install the driver in a computer equipped with an Ethernet to support communications between the computer and PLCs equipped with an Ethernet Unit.
13
1-3SectionCX-Process Tool Specifications
Item Specification
Files that are created The following files are created in the project folder.
• Multi-node files (.mul) for Project Workspace: Created by user.
• Function block files (.ist) consisting of initial set data and operation data: Created by
the system.
• Block diagram information files (.mtbd): Created by the system.
• Mnemonics/ladder diagram information files (.mtld): Created by the system.
• Monitor tag files (with fixed file name without extension): Created by user.
• Job information files (.sjb): Created by the system.
• Comment files (.cmt): Created by the system.
• CX-Server Settings file (.cdm): Created by the system.
• CSV tag settings file (project_name.csv): Created by system; can be edited by user.
• CSV tag files (.csv) for SCADA software: Created by user.
• Files for Loop Controllers (.lcb): Created by the system.
• User link table files in CSV format (LinkTable.csv): Created by the user.
• Sequence table files (.sbl): Created by the system.
• User-defined block files (User-defined_block_name.ucb): Created by the user.
• Sequence table operation validation and online editing/elements (timers and count-
ers) set value change and present value display files
Offline operation functions • Setting of function block ITEM data (including System Common block settings)
• Software wiring of analog signals
• Displaying or printing the arbitrary text (tags) attached to block connection diagrams
and ladder diagrams
• Displaying connection maps (showing the I/O relationships of a function block)
• Editing user link tables
• Creating sequence tables
• Description of Step Ladder Program block commands
• Setting of tags for CX-Process Monitor (on block designated as the source in the Send
to Computer block, contacts and analog signals)
• Backing up function block data from RAM to flash memory or restoring function block data from flash memory to RAM.
• Converting LCU/LCB element data between different models of Loop Controller.
Online operation functions Downloading of function block data (download/upload to and from Loop Controllers)
Comparing between node function block files (including mnemonics) and Loop Controllers
Run/stop command for Loop Controllers (all function blocks)
System monitor run status: Monitoring/manipulation of System Common block (Block Model 000) (including monitoring of load rate of function blocks in each operation cycle group)
• Loop Controller monitor run status: Confirmation of function block wiring operation (in­cluding operation stop/stop cancel on each function block), confirmation of Step Lad­der Program operation
Changing SPs and tuning parameters such as PID constants in function blocks (Control Blocks)
• Initializing RAM in the Loop Controller.
• Backing up function block data from RAM to flash memory in the Loop Controller block
and restoring the data to RAM.
• Creating I/O tables (online only)
• Setting the PLC Setup
• Changing the CPU Unit’s operating mode
14
Note The Windows Vista 64-bit version and Windows XP x64 Edition are not sup-
ported.

1-4 Version Improvements

g
1-4-1 Version 1.20
The improvements made from version 1.00 to version 1.20 of the CX-Process Tool are listed in the following table.
Item Ver. 1.00 Ver. 1.20
Maximum number of function data nodes (CPU Racks) that can be created
File creation Function files (.ist) and
Location of created files User-set Limited to the project folder in CX-Process\data
Project tree In order: Project Work-
Conditions in which monitor tag compilation is possible
Function blocks that can be created Not compatible with
Printing units
Downloading separate function blocks while Loop Control Unit is operating
Changing block address for registered function blocks
Block diagrams 1 block diagram 1 or all registered block diagrams
Step ladder diagrams 1 step ladder diagram 1 or all registered step ladder diagrams
1 node 31 nodes max.
Multi-node files (.mul) and related files (node
related files
space-LCU/LCB ele­ment-function block group-function block
Not possible with Windows 95/98
Loop Control Unit Ver.
1.20
Not possible (you must stop the Loop Control Unit to download)
Not possible Possible (you can also add 1)
function files (.ist), etc.) (See note.)
In order: Project Workspace-node function file
-LCU/LCB element-function block group
-function block
Possible with Windows 95/98
Compatible with creation of the following new Ver. 1.20 Loop Control Unit function block: 2-position ON/OFF (Block Model 001), 3-position ON/OFF (Block Model 002), Blended PID (Block Model 013), 3-input Selector (Block Model 163), 3-output Selector (Block Model
164), Batch Data Collector (Block Model 174), DI Terminal from Expanded CPU Unit (Block Model 455), DO Terminal from Expanded CPU Unit (Block Model 456), AI Terminal from Expanded CPU Unit (Block Model 457), AO Terminal from Expanded CPU Unit (Block Model 458)
Possible
1-4SectionVersion Improvements
Note You can also import block files (.ist) created using Ver. 1.00.
15
1-4-2 Version 1.50
The improvements made from version 1.20 to version 1.50 of the CX-Process Tool are as follows:
Item Ver. 1.20 Ver. 1.50
Function blocks that can be created
Printing functions Except for function
Monitor tag list display function
Search function None Possible (searches for block address or monitor software tag
Version check function None Possible (checks for version compatibility between the Loop
Not compatible with Loop Control Unit Ver.
1.50
blocks, only open block diagrams, ladder diagrams, and cross-references can be printed.
None Possible (displays the monitor software tag information that has
Compatible with the creation of following new function blocks with the Ver. 1.50 Loop Control Units: Segment Program 2 (Block Model 157), Accumulated Value Input Adder (Block Model 182), Accumulated Value Input Multiplier (Block Model 183), Constant Comparator (Block Model 202), Variable Comparator (Block Model 203), Clock Pulse (Block Model 207), ON/OFF Valve Manipulator (Block Model 221), Motor Manipulator (Block Model
222), Reversible Motor Manipulator (Block Model 223), Motor Opening Manipulator (Block Model 224)
Compatible with the following new Loop Control Unit Ver. 1.50 ITEM creations: AT (auto-tuning) functions of Basic PID block (Block Model 011) and Advanced PID (Block Model 012), and wait function and additional steps (step numbers 8 to 15) of the Ramp Program block (Block Model 155)
• You can print block diagrams, ladder diagrams, and cross-refer­ences by LCU element or node, even if they are not open.
• You can print monitor tag lists.
• You can print all data by LCU element or node.
been set)
name, and moves the cursor to the matching function block)
Control Unit connected online and CX-Process Tool in use)
1-4SectionVersion Improvements
16
1-4-3 Version 2.00
The improvements made from version 1.50 to version 2.00 of the CX-Process Tool are listed in the following table.
Item Ver. 1.50 Ver. 2.00
New function blocks Does not support Loop Control
Unit version 2.00
Editing block diagrams
Editing ladder diagrams Cut, copy, and paste not
Undo Not supported. The previously executed operation can be undone.
Compiling CSV tags for SCADA software
Function block data backup and recovery
ITEM List Monitoring Not supported. ITEM data for a specified function block can be monitored
Find Loop Control Unit Not supported. Loop Control Units on networks connected to the PLC to
Download, upload, and compare
Lines disappear when pasted function blocks are moved.
Lines must be deleted individually.
Block connection diagrams cannot be copied.
supported.
Not supported. CSV tags can be set for function blocks and CSV tags can
Not supported. Function blocks in RAM in the Loop Control Unit can be
Block diagram information files (extension: .mtbd) cannot be uploaded or downloaded.
ES100X Controller Terminal (Block Model 045), 4-point Warning Indicator (Block Model 110), Arithmetic Operation (Block Model 126), Time Sequence Data Statistics (Block Model 153), Receive All Blocks (Block Model 461), and Send All Blocks (Block Model 462).
ITEMs added for other function blocks. Refer to the Loop Control Unit Operation Manual for details.
Lines do not disappear when pasted function blocks are moved.
All the lines connected to specified function blocks or ITEMs can be deleted at the same time.
Block connection diagrams can be copied and registered to new Loop Control Unit nodes.
Cutting, copying, and pasting are possible for symbols, areas, and lines.
be compiled, saved, and displayed accordingly.
backed up in flash memory in the Loop Control Unit or the data in flash memory can be restored to RAM.
in a list.
which the CX-Process Tool is connected can be found and addresses can be set in node function block files.
Block diagram information files (extension: .mtbd) can be uploaded or downloaded.
1-4SectionVersion Improvements
17
1-4-4 Version 2.50
The improvements made from version 2.00 to version 2.50 of the CX-Process Tool are listed in the following table.
Item Ver. 2.00 Ver. 2.50
New function blocks Does not support Loop
Control Unit version 2.50
Communications drivers FinsGateway only FinsGateway or CX-Server can be selected as the
Tuning Screen Not supported. Added the Tuning Screen that could previously be used with
Download individual ITEM data
Annotations (comments) Not supported. It is now possible to insert comments at any point in the diagram
Copy function block Not supported. Function block units can be copied/cut/pasted in the Project
Automatic assembly and disassembly of step ladder programs
Not supported. When the CX-Process Tool is online and a function block’s ITEM
Not supported. Step ladder programs (Block Model 301) can be automatically
Fuzzy Logic (Block Model 016), Range Conversion (Block Model
127), Ramped Switch (Block Model 167), Level Check (Block
Model 210), AI4 Terminals (DRT1-AD04) (Block Model 588), AO2 Terminals (DRT1-DA02) (Block Model 589)
communications driver.
When CX-Server is selected, both CX-Programmer and the CX-Process Tool can be started simultaneously (sharing the communications driver CX-Server). Also, the computer can be connected through the PLC’s Peripheral Bus.
CX-Process Monitor only in lower versions.
This screen allows parameters such to be adjusted from the CX-Process Tool. For example, PID constants and SPs can be adjusted in the Basic PID Block. Also, the Fuzzy Logic Block can be displayed only in this version of the CX-Process Tool.
has been set, it is possible to download just that ITEM’s data (operation data only) to the Loop Control Unit by clicking the Download Button.
For example, this function can be used for the AT command (autotuning) from the Basic PID Block or Advanced PID Block.
when operating in Block Diagram Edit Mode or Ladder Diagram Edit Mode. This function allows user-set names to be displayed and printed (useful for schematic diagrams) next to commands in function blocks or step ladder programs.
Workspace.
assembled (converted from ladder diagram to mnemonic code) when they are downloaded and automatically disassembled (converted from mnemonic code to ladder diagram) when they are uploaded. (The Mnemonic Flag specifies whether a program can be converted to ladder diagram format.)
1-4SectionVersion Improvements
18
1-4-5 Version 3.00
Note The improvements made from version 2.50 to version 3.00 of the CX-Process
Tool are listed in the following table.
Item Ver. 2.50 Ver. 3.00
Applicable Units/Boards Loop Control Units Loop Control Units and Loop Control Boards
New functions for Loop Control Boards
New function blocks --- Sequence Table (Block Model 302) and Ao
Function block registration methods Registering function
Connection maps Not supported. Supported
Conversion of LCU/LCB element data between Loop Controller models
Downloading block diagram information Not supported. When downloading individual function blocks,
Controlling CPU Unit operation Not supported. If the CX-Server is specified as the
Data monitoring refresh cycle for PVs, SPs, alarms, and other data on Tuning Screens
Connection specifications on block diagrams other than software connections (Right-clicking blue ITEMs and inputting addresses)
User link tables Not supported. Supported, along with the following.
Automatic registration of Field Terminals to user link tables
Copying and pasting software links for user link table function blocks
Outputting user link table tags in CSV format (attached to HMI data tags)
Importing local symbol tables from the CX-Programmer
Sequence tables (Block Model 302)
Not supported. Supported (Operation can also be validated.)
Terminal (PMV02) (Block Model 565) (Supported by the CS1W-LCB05 Loop Control Board only.)
In addition to the V2.50 method, function blocks blocks with the Function Block Navigator and then pasting them
Not supported. CS1W-LCB01 Loop Control Board data can be
1 s only Either 1 s or 200 ms can be selected. (A red
Input only of block addresses and ITEM numbers (BBBIII)
can also be specified and pasted directly on the
block diagrams. (Function blocks can be
specified after right-clicking on the block
diagram.)
A diagram of the I/O relationships for one block
can be displayed after selecting the block.
converted to CS1W-LCB05 Loop Control Board
data.
CS1W-LC001 Loop Control Unit data can be
converted to CS1W-LCB01 or CS1W-LCB05
Loop Control Board data.
layout information for the block from the block
diagram can also be downloaded.
communications driver, I/O tables can be
created, the PLC Setup can be set, and the
CPU Unit’s operating mode can be controlled.
warning display will appear when the data
could not be refreshed within the specified
cycle.)
In addition to block addresses and ITEM
numbers (BBBIII), the connection destination
can be specified from a pull-down menu when
using a Loop Control Board.
1-4SectionVersion Improvements
19
1-4-6 Version 3.1
q
The improvements made from version 3.0 to version 3.1 of the CX-Process Tool are listed in the following table.
Item Ver. 3.0 Ver. 3.1
Unit/Board support CS1W-LC001 Loop Control Unit and
CS1W-LCB01/05 Loop Control Boards
Data conversion Conversion from LCU element to LCB
element data
CSV tag settings Manually only (making settings
individually in the CSV Tag Settings Dialog Box)
Backup during operation Not supported. Supported.
CS1D-CPUP Process-control CPU Units (in addition to CS1W-LC001 Loop Control Unit and CS1W-LCB01/05 Loop Control Boards)
Conversion of data created for the CS1W-LCB05 to CS1D-CPUP Process-control CPU Unit (in addition to conversion from LCU element to LCB element data)
Automatically creating CSV tag settings when registering function blocks (CSV tag setting function) and editing in Excel or other editor before loading to the project (in addition to manual setting)
1-4SectionVersion Improvements
1-4-7 Version 3.2
The improvements made from version 3.1 to version 3.2 of the CX-Process Tool are listed in the following table.
Item Ver. 3.1 Ver. 3.2
User-defined block Not supported. Supported. (Registers a group of function
blocks as a single user-defined function block.)
RS View tag files (.csv) Not supported. (The
CSV tag file must be imported to an OPC server and then the RS View tag file (.csv) has to be created manually.)
OPC server direct access tag output Not supported. Supported.
HMI memory map CSV output Not supported. Supported.
Tuning screens
Setting of number of communications retries
Sequence table
Multiple screens Not supported. (Only
one screen can be open.)
Data logging (saved to CSV file)
Online editing Not supported. Supported.
Displaying PV and changing set value for timers and counters
Not supported. Supported. (Logging is started when the tuning
Not supported. Supported.
Not supported. Supported.
Supported. (The RS View tag file (.csv) can be
automatically and directly generated.)
ITEMs other than HMI data can be output for
OPC server direct access when the CSV tags
are compiled. (Applies only to the following:
Ramp Program (Block Model 155), Segment
Program (Block Model 156), and Segment
Program 2 (Block Model 157).
The allocations of HMI memory can be output
to a CSV file. The file shows which words in the
EM Area are allocated to tags and tag ITEMs.
Supported. (Up to four screens can be open.)
screen is opened and continues until the tuning
screen is closed.)
20
Item Ver. 3.2Ver. 3.1
Monitor software CX-Process Monitor
(CX-Process Monitor Plus cannot be used.)
1-4-8 Version 4.0
The improvements made from version 3.2 to version 4.0 of the CX-Process Tool
are listed in the following table.
Item Details
1-4SectionVersion Improvements
CX-Process Monitor or
CX-Process Monitor Plus
Support for CJ1G-CPUP Loop-control CPU Units and LCB01/05 version 2.0
Displaying Loop Controller memory map
Backing up to and recovering from Memory Card project comments, annotations, tags, and connection data
The following new functions are supported:
Simple backup of the Loop Controller’s function block data to the Memory Card
Selecting the step to restart Segment Program 2 (Block Model 157) to match the first or second reference input
Synchronization of Segment Program 2 (Block Model 157)
Setting hot start time
Reset wind up protection of secondary loop of cascade control
Setting range 0.00% to 100.00% for input signals in Split Converter (Block Model
169)
Addition of Field Terminal Blocks (Ai4 terminal (PTS51/52), Ai8 terminal (PTS55/56), Ao2 terminal (DA021), and Ai4/Ao2 terminal (MAD42)
The status showing how the Loop Controller is using CPU Unit memory can be displayed as a list.
Comments, annotations, tags, and connection data, which previously could not be saved in the Loop Controller, can now be saved in the Memory Card installed in the CPU Unit. This enables comments, annotations, tags, and connection data included in function block data to be uploaded from the Loop Controller.
Support for SYSMAC OPC Server version 2.6 scaling functions
Starting the NS Faceplate Auto Builder The Faceplate Auto-Builder for NS can be
The scaling functions from SYSMAC OPC Server version 2.6 have been expanded. The expanded scaling information for CSV tags can be exported to the SYSMAC OPC Server version 2.6.
executed in the sequence of operations when compiling CSV tags from the CX-Process Tool. Using this method, the folder for the created CSV tag file will be automatically specified in the parameter setting screen that is displayed when the Faceplate Auto-Builder for NS starts.
21
1-4-9 Version 4.1
The improvements made from version 4.0 to version 4.1 of the CX-Process Tool are listed in the following table.
Item Ver. 4.0 Ver. 4.1
Installation method CX-Process Tool could
be installed as a single entity only.
Startup method From the Start Menu
only
Folder for creating/saving projects Fixed location under
data folder in the installation folder
1-4SectionVersion Improvements
CX-Process Tool can be installed from the CX-One FA Integrated Tool Package as one function.
If the CX-Process Tool is installed from the CX-One, a dialog box to select the communications driver will not be displayed when the CX-Process is started and the CX-Server will be used automatically as the communications driver.
Startup can be performed by right-clicking on any of the following Loop Controllers under the I/O Table Window of CX-Programmer that was installed from the CX-One, and selecting Start Special Application.
• CS1W-LCB01 (Loop Control Board)
• CS1W-LCB05 (Loop Control Board)
• CS1D-LCB05D (Loop Control Board)
• CS1W-LC001 (Loop Control Unit)
• CJ1W-LCB01 (Loop Controller Element built into CPU
Unit)
• CJ1W-LCB03 (Loop Controller Element built into CPU Unit)
Note If Start with Settings Inherited is selected,
CX-Server will be used automatically as the communications driver. The node’s Function Block File will also be automatically created.
The user can specify the folder for creating/saving projects.
Select File – New from the menu bar and specify the destination in the Browse for Folder Dialog Box.
22
1-4-10 Version 5.0
ab es
The improvements made from version 4.1 to version 5.0 of the CX-Process Tool are listed in the following table.
Item Ver. 4.1 Ver. 5.0 (See note.)
Support for LCB01/05 and supports for Loop-control CPU Units (CJ1G-CPUP) Ver. 3.0
Free positioning of block diagrams
Increase in the number of blocks that can be registered in function block groups
Transferring tag comment data to flash memory
Wireless debugging Not supported. A fixed value can be input as a pseudo-input to
User link tables
Table reference function for sequence tables
Step ladder timer instructions Not supported. Timer commands (TIM) can be used in Step Ladder
MV tight shut function
MV analog output reversal function
Copying/pasting Not supported. Entries in user link tables can be copied and pasted.
EM bank specification
Pulse output Not supported. Pulse output writing (ON for one refresh cycle) is
Only Ver. 2.0 or earlier were supported.
Not supported (positioning was possible only at fixed locations)
Only 16 blocks could be registered in each function block group.
Not supported. (Transfer was possible to a Memory Card in the CPU Unit.)
Not supported. Tight shut outputs to I/O memory in the CPU Unit are
Not supported. Reversing outputs to I/O memory in the CPU Unit are
Not supported. (Only the current bank could be used.)
Not supported. Results of conditions set in other tables can be
The following functions are supported for LCB01/05 and supports for Loop-control CPU Units (CJ1G-CPUP) Ver. 3.0:
• Switch Instrument (Block Model 225), AI 2-point Termi­nal (Block Model 571), and AI 16-point Terminal (Block Model 582)
• Switching the adjustment operation direction for Basic PID (Block Model 011) and Advanced PID (Block Model
012)
• Switching RUN/STOP for Basic PID (Block Model 011) and Advanced PID (Block Model 012)
• Tight shunt function and analog output reversal function for analog output terminals.
Positioning is possible anywhere in the block diagram.
Up to 64 blocks can be registered in each function block group.
The following data can be transferred to flash memory in the Loop Controller: block diagram data, tags, comments, annotations, etc. (Data cannot be transferred to a Memory Card for Loop Control Board version 3.0.)
adjustment block PVs in a new calibration mode.
supported.
supported.
EM0 to EMC can be specified.
possible to I/O memory in the CPU Unit when a specified ITEM turns ON.
referenced from Sequence Table (Block Model 302) suing TBL commands.
Program (Block Model 301)
1-4SectionVersion Improvements
Note These functions are supported only for Loop Control Boards and Loop-control
CPU Units with unit version 3.0 or later.
23
1-4-11 Version 5.1
CX-Process Tool version updated from 5.0 to 5.1. The improvements made from version 5.0 to version 5.1 of the CX-Process Tool are listed in the following table.
Item Ver. 5.0 Ver. 5.1
Function blocks for gradient temperature control (Gradient PV Mode Converter (Block Model 021), Gradient SP Mode Converter (Block Model 022), Gradient PID (Block Model 024), Gradient Precompensator (Block Model 023))
Not supported Supported.
1-4-12 Version 5.2
The improvements made from version 5.1 to version 5.2 of the CX-Process Tool are listed in the following table.
Item Previous (Version 5.1) Updated (Version 5.2)
Support for LCB01/05 version 3.5 and CJ1G-CPUP Loop-control CPU Unit version 3.5
Engineering unit display Analog values could be set
Output window display Data, such as verification
Improved sequence for creating new function block data
Improved method for adding function blocks
Support was provided only up to version 3.0.
only as percentages.
results, was displayed in fixed dialog boxes.
Only an empty project workspace was created.
Function blocks could be added from only from the menus.
1-4SectionVersion Improvements
10-point control/group for up to 4 groups (when a Loop Controller with gradient temperature control is used.) Note: For details on gradient temperature control, refer to the Loop Controller with Gradient Temperature Control Operation Manual (Cat. No. W460).
The following new blocks are supported:
• Segment Program 3 (Block Model 158)
• Isolated Ai4 Terminal (PH41U, Block Model 572)
• Isolated Ai4 Terminal (AD04U, Block Model 573)
• Ai4 Terminal (ADG41, Block Model 581)
The following new functions are supported:
• Search area number specifications for Segment Program 2 (Block Model 157)
• Easy parameter setting for Segment Program 2 (Block Model 157) and Segment Program 3 (Block Model 158)
An ITEM can be displayed and set in engineering units, based on scaling information (CSV tag information) for individual function blocks.
Data, such as verification results, is displayed in special windows. The following functions are supported.
• Jumping to the relevant location from the displayed results
• Copying results to the clipboard
When a new project is created, all operations from inserting the Loop Controller to displaying the block diagram are executed automatically.
Function blocks can be added from a function block toolbar in the block diagram display.
24
1-5SectionFunction Blocks/ITEMs Incompatible with Earlier Versions

1-5 Function Blocks/ITEMs Incompatible with Earlier Versions

1-5-1 Incompatibility with Versions Earlier than Version 1.20
The following function blocks can be used only when Loop Control Unit CS1W-LC001 Ver.1.20 and onwards and CX-Process Tool Ver.1.20 and on­wards are used:
• The following function blocks can be registered on CX-Process Tool when
Loop Control Unit Ver.1.0 and CX-Process Tool Ver1.20 or onwards are used. If the data of these function blocks is downloaded to the Loop Control Unit by LCU element when these function blocks are registered on CX-Pro­cess Tool, however, an error occurs, and the download is canceled. (Other function blocks also are not downloaded.)
• The following function blocks cannot be registered on CX-Process Tool when Loop Control Unit Ver.1.20 and onwards and CX-Process Tool Ver.1.00 are used. For this reason, these function blocks cannot also be downloaded to the Loop Control Unit. If the following function blocks already exist on the Loop Control Unit and are uploaded to CX-Process Tool, only the following function blocks are not uploaded. (When a new upload is performed, these blocks be­come empty.)
2-position ON/OFF (Block Model 001), 3-position ON/OFF (Block Model
002), Blended PID (Block Model 013), 3-input Selector (Block Model
163), 3-output Selector (Block Model 164), Batch Data Collector (Block Model 174), DI Terminal from Expanded CPU Unit (Block Model 455), DO Terminal from Expanded CPU Unit (Block Model 456), AI Terminal from Expanded CPU Unit (Block Model 457), AO Terminal from Expand­ed CPU Unit (Block Model 458)
Note The version of the Loop Control Unit can be verified in the Monitor Run Status
Screen (Execution, Operation, Monitor run status) on CX-Process Tool. When the above function blocks are used, check in the Check System Operation screen on CX-Process Tool beforehand that the content of ITEM 099 onwards in the System Common block (Block Model 000) is as follows:
ITEM Data name Data
099 MPU/FROM version indication V1.20
Version V1.20 and onwards must be indicated.
1-5-2 Incompatibility with Versions Earlier than Version 1.50
The following function blocks described in this manual can be used only when Loop Control Unit CS1W-LC001 Ver.1.50 and onwards and CX-Process Tool Ver.1.50 and onwards are used:
• The following function blocks can be registered on CX-Process Tool when ver­sions of Loop Control Unit earlier than Ver.1.50 (Ver.1.0 or Ver.1.20) and CX­Process Tool Ver1.50 or onwards are used. However, if the data of these func­tion blocks is downloaded to the Loop Control Unit by LCU element (data for one Loop Control Unit) when these function blocks are registered on CX-Pro­cess Tool, an error occurs, and only those function blocks are not downloaded. (Other function blocks are downloaded successfully.)
• The following function blocks cannot be registered on CX-Process Tool when Loop Control Unit Ver.1.50 and onwards and versions of CX-Process Tool low­er than Ver.1.50 (Ver.1.00 or Ver. 1.20) are used. For this reason, these func­tion blocks cannot also be downloaded to the Loop Control Unit. If the following function blocks already exist on the Loop Control Unit and are
25
1-5SectionFunction Blocks/ITEMs Incompatible with Earlier Versions
uploaded to CX-Process Tool, only the following function blocks are not uploaded. (When a new upload is performed, these blocks become empty.)
Segment Program 2 (Block Model 157), Accumulated Value Input Adder (Block Model 182), Accumulated Value Input Multiplier (Block Model
183), Constant Comparator (Block Model 202), Variable Comparator (Block Model 203), Clock Pulse (Block Model 207), ON/OFF Valve Ma­nipulator (Block Model 221), Motor Manipulator (Block Model 222), Re­versible Motor Manipulator (Block Model 223), Motor Opening Manipula­tor (Block Model 224)
Likewise, the following functions can be used only when Loop Control Unit CS1W-LC001 Ver.1.50 and onwards and CX-Process Tool Ver.1.50 and on­wards are used:
• The following ITEMs can be set on CX-Process Tool when versions of Loop Control Unit earlier than Ver.1.50 (Ver.1.0N or Ver.1.20) and CX-Process Tool Ver.1.50 or onwards are used. However, if the data of these ITEMs is downloaded to the Loop Control Unit when these ITEMs are set on CX-Pro­cess Tool, only those ITEMs are not downloaded. (Other ITEMs are down­loaded successfully.)
• The following ITEMs cannot be set on CX-Process Tool when Loop Control Unit Ver.1.50 or onwards and versions of CX-Process Tool lower than Ver.1.50 (Ver.1.00 or Ver. 1.20) are used. For this reason, these ITEMs cannot also be downloaded to the Loop Control Unit. If a download in major item units (Loop Control Units) or a download in function blocks units including initial setting data is performed, the respective defaults are set to the following ITEMs on the Loop Control Unit. If the following ITEMs are already set on the Loop Control Unit and are uploaded to the CX-Process Tool, only the following ITEMs are not uploaded.
AT (auto-tuning) functions of Basic PID block (Block Model 011) and Ad­vanced PID (Block Model 012), and wait function and additional steps (step numbers 8 to 15) of the Ramp Program block (Block Model 155)
Note 1. For details on which actual ITEM this restriction applies to, refer to the ITEM
list for the relevant function block in the Function Block Reference Manual.
2. The version of the Loop Control Unit can be verified in the Monitor Run Sta­tus Screen (Execution, Operation, Monitor Run Status) on CX-Process Tool. When the above function blocks are used, check in the Check System Op­eration screen on CX-Process Tool beforehand that the content of ITEM 099 onwards in the System Common block (Block Model 000) is as follows:
ITEM Data name Data
099 MPU/FROM version indication V1.50
Version V1.50 and onwards must be indicated.
1-5-3 Incompatibility with Versions Earlier than Version 2.00
The following function blocks described in this manual can be used only when Loop Control Unit CS1W-LC001 Ver. 2.00 and onwards and CX-Process Tool Ver. 2.00 and onwards are used:
• The following function blocks can be registered on CX-Process Tool when ver-
sions of Loop Control Unit earlier than Ver. 2.00 (Ver. 1.0, Ver. 1.20, or Ver.
1.50) and CX-Process Tool Ver 1.50 or onwards are used. However, if the data of these function blocks is downloaded to the Loop Control Unit in major item units (units of Loop Control Unit) when these function blocks are registered on
26
1-5SectionFunction Blocks/ITEMs Incompatible with Earlier Versions
CX-Process Tool, an error occurs, and only those function blocks are not downloaded. (Other function blocks are downloaded successfully.)
• The following function blocks cannot be registered on CX-Process Tool when Loop Control Unit Ver. 2.00 and onwards and versions of CX-Process Tool low­er than Ver. 2.00 (Ver. 1.0 Ver. 1.20, or Ver. 1.50) are used. For this reason, these function blocks cannot also be downloaded to the Loop Control Unit. If the following function blocks already exist on the Loop Control Unit and are uploaded to CX-Process Tool, only the following function blocks are not uploaded. (When a new upload is performed, these blocks become empty.)
ES100X Controller Terminal (Block Model 045), 4-point Warning Indicator (Block Model 110), Arithmetic Operation (Block Model 126), Time Se­quence Data Statistics (Block Model 153), Receive All Blocks (Block Model 461), Send All Blocks (Block Model 462)
Likewise, the following functions can be used only when Loop Control Unit CS1W-LC001 Ver. 2.00 and onwards and CX-Process Tool Ver. 2.00 and on­wards are used:
• The following ITEMs can be set on CX-Process Tool when versions of Loop Control Unit earlier than Ver. 2.00 (Ver. 1.0 Ver. 1.20, or Ver. 1.50) and CX- Process Tool Ver. 2.00 or onwards are used. However, if the data of these ITEMs is downloaded to the Loop Control Unit when these ITEMs are set on CX-Process Tool, only those ITEMs are not downloaded. (Other ITEMs are downloaded successfully.)
• The following ITEMs cannot be set on CX-Process Tool when Loop Control Unit Ver. 2.00 or onwards and versions of CX-Process Tool lower than Ver.
2.00 (Ver. 1.0 Ver. 1.20, or Ver. 1.50) are used. For this reason, these ITEMs cannot also be downloaded to the Loop Control Unit. If a download in major item units (units of Loop Control Unit) or a download in function blocks units including initial setting data is performed, the respective defaults are set to the following ITEMs on the Loop Control Unit. If the following ITEMs are already set on the Loop Control Unit and are uploaded to the CX-Process Tool, only the following ITEMs are not uploaded.
MV Output Retrace Time for PV Error has been added to 2-position ON/ OFF (Block Model 001), 3-position ON/OFF (Block Model 002), Basic PID (Block Model 011), and Advanced PID (Block Model 012). High MV Limit Arrival Output and Low MV Limit Arrival Output have been added to Basic PID (Block Model 011), Indication and Operation (Block Model 032), and Ratio Setting (Block Model 033). MV Error Input and MV Error Display have been added to Batch Flowrate Capture (Block Model 014), Indication and Operation (Block Model 032), and Ratio Setting (Block Model 033). PV Error Input and PV Error Display have been added to Indication and Setting (Block Model 031), Indication and Operation (Block Model 032), Ratio Setting (Block Model 033), and Indicator (Block Model 034). Inputs X1 to X8 have been added to Constant Comparator (Block Model
202). Inputs X1 to X8 and Comparison Input R1 to R8 have been added to Variable Comparator (Block Model 203) Contact Inputs S33 to S224 have been added to Internal Switch (Block Model 209).
Note 1. For details on which actual ITEM this restriction applies to, refer to the ITEM
list for the relevant function block in the Function Block Reference Manual.
2. The version of the Loop Control Unit can be verified in the Monitor run status screen ([Execute]–[Run]–[Monitor run status]) on CX-Process Tool. When the above function blocks are used, check in the Check System Op-
27
eration screen on CX-Process Tool beforehand that the content of ITEM 099 onwards in the System Common block (Block Model 000) is as follows:
ITEM Data name Data
099 MPU/FROM version indication V2.00
Version V2.00 and onwards must be indicated.
1-5-4 Incompatibility with Versions Earlier than Version 2.50
1-5SectionFunction Blocks/ITEMs Incompatible with Earlier Versions
Function Blocks Incompatible with Earlier Versions
The following function blocks can be used only with version 2.50 or later versions of the CS1W-LC001 Loop Control Unit and version 2.50 or higher versions of the CX-Process Tool.
Fuzzy Logic (Block Model 016), Range Conversion (Block Model 127), Ramped Switch (Block Model 167), Level Check (Block Model 210), AI4 Terminals from DRT1-AD04 Unit (Block Model 588), and AO2 Terminals from DRT1-DA02 Unit (Block Model 589)
• If an earlier version of the Loop Control Unit is used with CX-Process Tool ver­sion 2.50 or higher, these function blocks can be registered but the data for the function blocks won’t be downloaded to the Loop Control Unit when LCU ele­ment data is downloaded. (The supported function blocks will be downloaded normally.)
• If Loop Control Unit version 2.50 or later is used with a lower version of the CX­Process Tool, these function blocks cannot be registered in the CX-Process Tool, so they cannot be downloaded to the Loop Control Unit. If these function blocks have been downloaded to the Loop Control Unit al­ready, the data for these function blocks won’t be uploaded from the Loop Con­trol Unit. The supported function blocks will be uploaded normally. (If Upload New is selected, the unsupported function blocks will be empty.)
28
1-5SectionFunction Blocks/ITEMs Incompatible with Earlier Versions
ITEMs Incompatible with Earlier Versions
The following ITEMs can be used only with version 2.50 or later versions of the CS1W-LC001 Loop Control Unit and version 2.50 or higher versions of the CX­Process Tool.
• Block Registration Flag (ITEM039) and Toolbar Version (ITEM110) in Sys­tem Common (Block Model 000)
• Warning Limit (ITEM020) in the following Blocks: Basic PID (Block Model 011), Advanced PID (Block Model 012), 2-position ON/OFF (Block Model 001), 3-position ON/OFF (Block Model 002), In­dication and Setting (Block Model 031), Indication and Operation (Block Model 032), Ratio Setting (Block Model 033), Indicator (Block Model 034), and 4-point Warning Indicator (Block Model 110)
• SP Rate-of-change Limit Time Unit (ITEM030) in Advanced PID (Block Model 012)
• The following ITEMs in Batch Flowrate Capture (Block Model 014): Local SP Setting, Upper 4 Digits (ITEM024), Remote SP Setting, Upper 4 Digits (ITEM028), Current SP, Upper 4 Digits (ITEM030), Preset Value (ITEM061), and Batch Accumulated Value, Upper 4 Digits (ITEM065)
• Time Units (ITEM013) in Rate-of-change Limiter (Speed Response) (Block Model 143)
• Reference Input Disable Switch (ITEM020) in Segment Program 2 (Block Model 157)
• Output Type (ITEM006) in Contact Distributor (Block Model 201)
• Individual I/O Range Settings in the following Blocks:
AI Terminal from CPU Unit (Block Model 453), AO Terminal from CPU Unit (Block Model 454), AI4 Terminal (Block Model 561), PI4 Terminal (Block Model 562), and AI8 Terminal (Block Model 564)
• Receive Stop Switch (ITEM225) in the following Blocks: DI Terminal from Expanded CPU Unit (Block Model 455) and AI Terminal from Expanded CPU Unit (Block Model 457)
• Send Stop Switch (ITEM225) in the following Blocks: DO Terminal from Expanded CPU Unit (Block Model 456) and AO Termi­nal from Expanded CPU Unit (Block Model 458)
Note 1. For details on which actual ITEM this restriction applies to, refer to the ITEM
list for the relevant function block in the Function Block Reference Manual.
2. The version of the Loop Control Unit can be verified in the Monitor Run Sta­tus Screen (Execution, Operation, Monitor Run Status) on CX-Process Tool. When the above function blocks are used, check in the Check System Op­eration screen on CX-Process Tool beforehand that the content of ITEM 099 onwards in the System Common block (Block Model 000) is as follows:
ITEM Data name Data
099 MPU/FROM version indication V2.50
Version V2.50 and onwards must be indicated.
1-5-5 Incompatibility with Versions Earlier than Version 3.2
Function Blocks Incompatible with Earlier Versions
The following function blocks can be used only with LCB01/LCB05 version 1.5 or later, or LCB03, together with the CX-Process Tool version 3.20 or higher.
Ai4 Terminal (PTS51), Ai8 Terminal (PTS55), Ai4 Terminal (PTS52), Ai8 Terminal (PTS56), Ai8 Terminal (PDC55), Ao2 Terminal (DA021), Ai4/Ao2 Terminal (MAD42)
29
• If an earlier version of the Loop Control Board is used with CX-Process Tool version 3.20 or higher, these function blocks can be registered but the data for the function blocks won’t be downloaded to the Loop Control Unit when LCU element data is downloaded. (The supported function blocks will be down­loaded normally.)
• If Loop Control Board version 1.20 or later is used with a lower version of the CX-Process Tool, these function blocks cannot be registered in the CX-Pro­cess Tool, so they cannot be downloaded to the Loop Control Unit. If these function blocks have been downloaded to the Loop Control Unit al­ready, the data for these function blocks won’t be uploaded from the Loop Con­trol Unit. The supported function blocks will be uploaded normally. (If Upload New is selected, the unsupported function blocks will be empty.)
1-5-6 Incompatibility with Versions Earlier than Version 4.0
1-5SectionFunction Blocks/ITEMs Incompatible with Earlier Versions
Function Blocks Incompatible with Earlier Versions
The following function blocks can be used only with LCB01/LCB05 version 2.0 or later, or LCB03, together with the CX-Process Tool version 4.0 or higher.
Ai4 Terminal (PTS51/52) (Block Model 590), Ao2 Terminal (DA021) (Block Model 591), Ai4/Ao2 Terminal (MAD42) (Block Model 592)
• If an earlier version of LCB is used with a lower version of the CX-Process Tool, these function blocks cannot be registered in the CX-Process Tool, so they cannot be downloaded to the LCB.
1-5-7 Incompatibility with Versions Earlier than Version 5.0
Function Blocks Incompatible with Earlier Versions
The following function blocks can be used only with LCB03 and only if LCB03 is used together with CX-Process Tool version 5.1 or higher. If used with a lower version of the CX-Process Tool, the following function blocks cannot be regis­tered and, therefore, cannot be downloaded to the Loop Control Board.
Gradient PV Mode Converter (Block Model 021), Gradient SP Mode Converter (Block Model 022), Gradient PID (Block Model 024), Gradient Precompensator (Block Model 023)
The following function blocks can be used only with LCB01/LCB05 version 3.0 or later, or LCB03 version 3.0 or later, together with the CX-Process Tool version
5.0 or higher.
• The following function blocks cannot be registered if LCB01/LCB05 version
3.0 or later, or LCB03 version 3.0 or later, is used together with a version of CX-Process Tool lower than version 5.0. For this reason, these function blocks cannot be downloaded to the Loop Controller
AI16 Terminal (AD161), AI2 Terminal (PTS15/16, PDC15), Switch Instru­ment (Block Model 225)
• The following settings cannot be used if LCB01/LCB05 version 3.0 or later, or LCB03 version 3.0 or later, is used together with a version of CX-Process Tool lower than version 5.0.
Switch action direction command (ITEM 053), RUN/STOP switch (ITEM
093), and MV at stop (ITEM 094) in Basic PID (Block Model 011) or Advanced PID (Block Model 012)
Note For details on which actual ITEM this restriction applies to, refer to the ITEM list
for the relevant function block in the Function Block Reference Manual.
1-5-8 Incompatibility with Versions Earlier than Version 5.2
Function Blocks Incompatible with Earlier Versions
30
The following function blocks cannot be registered on the CX-Process Tool when LCB01/05 version 3.5 or later or LCB03 version 3.5 or later is used with
CX-Process Tool version 5.1 or earlier. Therefore they cannot be down­loaded to the Loop Controller.
Isolated Ai4 Terminal (PH41U, Block Model 572), Isolated Ai4 Terminal (AD04U, Block Model 573), Ai4 Terminal (ADG41, Block Model 581), Segment Program 3 (Block Model 158)
Similarly, the following ITEMs can be used only when LCB01/05 version 3.5 or later, LCB03 version 3.5 or later, and CX-Process Tool version 5.2 or later are used.
Search Area Specification Wait (ITEM189), Search Area Number (ITEM194), and Reference Input Search Method (ITEM190) for Segment Program 2 search area specification
For details on particular ITEMs, refer to the Function Block Reference Manu-
Note
al.

1-6 Connecting to the PLC

Either one of the following communications drivers can be selected to support the connection with a PLC (Programmable Controller):
• FinsGateway
• CX-Server
Selection is also possible when CX-Process Tool is started from the Start Menu, or when Start Only is selected from the I/O Table Window using CX-Program­mer that was installed from the CX-One only.
When using the CX-Process Tool installed from the CX-One, the default setting is to not display the dialog box for selecting the communications driver.
1-6SectionConnecting to the PLC
Note If Start with Setting Inherited is selected from the I/O Table Window using CX-
Programmer that was installed from the CX-One, CX-Server will be used auto­matically as the communications driver.
1-6-1 Features of FinsGateway and CX-Server
The following table compares the special features of the communications driv­ers.
Item
FinsGateway CX-Server
Serial communications modes for serial connections
Network communications through a serial connection
Direct network connection Supported Supported
Node address setting range 1 or higher (cannot be set to 0) Must be set to 0 when the computer is
Other features • The same COM port can be used for si-
Host Link (SYSWAY-CV) Host Link or Peripheral Bus
Supported Supported
multaneous online connections with ap­plications using FinsGateway (such as PLC Reporter and SYSMAC OPC Serv­er).
Note The PLC’s node address must be set to 0 when using CX-Server and connecting
directly to the PLC in a 1:1 or 1:N connection. (The 1:N connection is possible with Host Link communications only.) On the other hand, the node address can­not be set to 0 when connecting to the PLC through FinsGateway; the node ad­dress must be 1 or higher. If CX-Server was selected as the communications driver and a Function Block
Communications driver
connected directly to the PLC
• The same COM port can be used for si­multaneous online connections with Tools such as CX-Programmer, CX-Protocol, and CX-Motion.
• Supports high-speed Peripheral Bus com­munications.
31
File (.ist) was created for node address 0 with filename “Node00” in that project,
co u ca o s
po a os
the project (multi-node file) cannot be opened if FinsGateway is selected later.
1-6-2 Selecting the Communications Driver
The following dialog box is displayed by default when the CX-Process Tool is started from the Start Menu if the CX-Process Tool was installed from the individ­ual product CD-ROM.
Note 1. This dialog box is not displayed by default if the CX-Process Tool was
installed from the CX-One.
2. The above dialog box will be displayed when the CX-Process Tool is started while File – Show Drive Select Dialog – Display is selected. It will not be displayed if File – Show Drive Select Dialog – Hide is selected. To change the communications driver, select File – Show Drive Select Dialog – Dis- play and then start the CX-Process by selecting Start Only from the Start Menu or I/O tables. If the CX-Process was installed as part of the CX-One (not independently), the above dialog box will not be displayed (i.e., File – Show Drive Select Dialog – Hide will be selected) and the CX-Server will automatically be used as the communications driver. To switch to the Fins­Gateway, select File – Show Drive Select Dialog – Display and then select FinsGateway at startup.
Using FinsGateway
Using CX-Server
Select FinsGateway as the communications driver.
Select CX-Server as the communications driver.
1-6SectionConnecting to the PLC
1-6-3 Using FinsGateway
Regardless of the connection method, use FinsGateway (embedded) as the communications driver.
Communications network FinsGateway
communications driver
Serial communications
Controller Link Network
Ethernet Network ETN_UNIT Driver Connecting through the Ethernet Board to a PLC
Host Link Network (See note 1.)
Peripheral bus (See note 2.)
Serial Unit Driver Connecting to the PLC’s peripheral or RS-232C
port via Host Link.
CLK (PCI slot) Driver
(Not supported by FinsGateway Version 2)
Controller Link Driver
Connecting through the Controller Link Support Board to a PLC with a Controller Link Unit mounted.
with an Ethernet Unit mounted.
Note 1. Host Link communications use FINS commands enclosed in a header and
terminator data (i.e., SYSWAY-CV for FinsGateway). Host Link communica­tions (SYSMAC WAY) is set for the PLC.
2. FinsGateway Version 2003 only.
Connecting via Serial Communications
The personal computer uses the FinsGateway Serial Unit Driver to connect to
Host Link (SYSMAC WAY)
the PLC’s peripheral or RS-232C port via Host Link communications.
Contents
32
1-6SectionConnecting to the PLC
Peripheral Bus
The personal computer uses the FinsGateway (Version 2003) Serial Unit Driver to connect to the PLC’s peripheral or RS-232C port via the peripheral bus.
Connections to the Peripheral Port of the CPU Unit
CX-Process Tool
IBM PC/AT or compatible (9-pin male)
CS1W-CN226 or CS1W-CN626 Connecting Cable
Loop Control Unit
CS1 CPU Unit
Peripheral port
Connections to the RS-232C port of the CPU Unit or Serial Communications Board or Unit
CX-Process Tool
IBM PC/AT or compatible (9-pin male)
XW2Z-200S-CV Connecting Cable
Note The FinsGateway Serial Unit Driver must be installed to enable connecting the
PLC via Host Link communications.
Connecting through a Controller Link Support Board
The personal computer can be connected to the PLC through a Controller Link Network using the FinsGateway CLK (PCI slot) Driver or a FinsGateway version 2 or higher Controller Link Driver.
Loop Control Unit
CS1 CPU Unit
RS-232C Port
Controller Link Unit Models
CX-Process Tool (IBM PC/AT or compatible)
Loop Control Unit Controller Link Unit
Controller Link Support Board
Loop Control Unit Controller Link Unit
Controller Link Network
Note The Controller Link Driver (FinsGateway CLK (PCI slot) Driver or the FinsGate-
way version 2 or higher Controller Link Driver) must be installed in order to con­nect to the PLC via a Controller Link Network.
Controller Link
Unit
CS1W-CLK21-V1
CS1W-CLK23
CS1W-CLK12-V1
CS1W-CLK13
CS1W-CLK52-V1
CS1W-CLK53
CJ1W-CLK21-V1
CJ1W-CLK23
PLC Unit Type Transmission
path
CS
CPU Bus Unit
Wired Twisted-pair cable
Series
Optical H-PCF Optical
fiber cable
Optical GI Optical fiber
cable
CJ
CPU Bus Unit Wired Twisted-pair cable
Series
33
1-6SectionConnecting to the PLC
(PCI slot)
(y
tibl
oS3Cpo
Controller Link Support Boards
Connections via Ethernet
Controller Link Support Board
3G8F7-CLK12-V1
3G8F7-CLK13
3G8F7-CLK52-V1
3G8F7-CLK53
3G8F7-CLK21-V1
3G8F7-CLK23
3G8F5-CLK11-V1 Optical fiber cable
3G8F5-CLK21-V1 Wire
Transmission
medium
Optical fiber cable (ring configuration)
Wire
Computer FinsGateway Driver
IBM PC/AT or compatible
IBM PC/AT or compa (ISA slot)
e
CLK (PCI slot) Driver
(FinsGateway Version 2 cannot be used.)
Controller Link Driver
The personal computer can be connected to the PLC through an Ethernet Net­work using the FinsGateway ETN_UNIT Driver.
CX-Process Tool IBM PC/AT or compatible
Loop Control Unit
Ethernet Unit
Ethernet
Ethernet Board
Loop Control Unit
Ethernet Unit
Ethernet Unit Model
Using CX-Server
Communications
network
Peripheral Bus (Toolbus)
Host Link (SYSMAC WAY)
Note The FinsGateway ETN_UNIT Driver must be installed in order to connect to the
PLC via an Ethernet Network.
Model PLC Unit Ethernet
CS1W-ETN01
CS1W-ETN11
CS1W-ETN21 100Base-TX
CJ1W-ETN11
CJ1W-ETN21
CS Series
CJ Series
CPU Bus Unit
CPU Bus Unit
10Base-5
10Base-T
10Base-T
100Base-TX
The following two methods can be used to connect to the PLC.
Network type specified
in dialog box
Select Toolbus. Special high-speed communications
protocol for Programming Devices
Select SYSMAC WAY. Standard protocol for
general-purpose host computers
Usage Cable connection
Connect to the PLC’s peripheral or RS-232C port.
34
1-6SectionConnecting to the PLC
pp p
(
)
p
(Toolbus)
p
The connections shown in the following diagram can be used with either Periph­eral Bus or Host Link connections.
Connections to the Peripheral Port of the CPU Unit
CX-Process Tool
IBM PC/AT or compatible (9-pin male)
CS1W-CN226 or CS1W-CN626 Connecting Cable
Loop Controller
CS1 CPU Unit
Peripheral port
1-6-4 Connecting Cables
The following table lists the Connecting Cables that can be used for Peripheral Bus and Host Link connections. All of the cables connect to a male 9-pin D-Sub serial port on an IBM PC/AT or compatible computer.
Unit Port location Serial Commu-
nications Mode
CPU Unit Built-in peripheral port Host Link
(SYSMAC WAY)
Built-in RS-232C port Female 9-pin D-SUB
Serial Communica-
RS-232C port
tions Board or UnitpMale 9-pin D-SUB (SYSMAC WAY)
or Peripheral Bus
Toolbus
Host Link
Connections to the RS-232C port of the CPU Unit or Serial Communications Board or Unit
CX-Process Tool
IBM PC/AT or compatible (9-pin male)
XW2Z-200S-CV Connecting Cable
Loop Controller
CS1 CPU Unit
RS-232C port
Note The Peripheral Bus connection cannot
be used with a Serial Communications Board or Unit.
Model Length Remarks
CS1W-CN226 2.0 m
---
CS1W-CN626 6.0 m
XW2Z-200S-CV 2 m
Anti-static connector
XW2Z-500S-CV 5 m
XW2Z-200S-CV 2 m
Anti-static connector
XW2Z-500S-CV 5 m
Note Touch a grounded metal to discharge all static electricity from your body before
connecting any of the above cable connectors to the RS-232C port of the PLC. The XW2Z-S-CV Cable uses the anti-static XM2S-0911-E Connector Hood. For safety sake, however, discharge all static electricity from your body before touching the connector.
The following components are used to connect RS-232C cable to the peripheral port. Connect to a male 9-pin D-Sub serial port on an IBM PC/AT or compatible computer.
Unit Port location Serial Commu-
nications Mode
CPU Unit Built-in peripheral port Host Link
(SYSMAC WAY) or Peripheral Bus (Toolbus)
The following components are available for connecting the CQM1-CIF01 or CQM1-CIF02 Cable to the peripheral port. Connect to a male 9-pin D-Sub serial port on an IBM PC/AT or compatible computer.
Unit Port on Unit Serial Communica-
tions Mode
CPU Unit Built-in peripheral port Host Link
(SYSMAC WAY)
Model Length Remarks
CS1W-CN118 + XW2Z-200S-CV
0.1 m + (2 or 5 m)
The XW2Z-S- CV is an anti-static connector.
CS1W-CN118 +
---
XW2Z-200S-V
Model Length Remarks
CS1W-CN114 +
0.5 m + 3.3 m ---
CQM1-CIF02
35
1-7SectionBasic Operating Procedures
p
The following components are available for connecting the IBM PC/AT or com­patible over RS-232C. Connect to a male 9-pin D-Sub serial port.
Unit Port on Unit Serial Communica-
tions Mode
CPU Unit Built-in RS-232C port
Female 9-pin D-SUB (SYSMAC WAY)
Serial Communica­tions Board or Unit Female 9-pin D-SUB
RS-232C Port
Host Link

1-7 Basic Operating Procedures

The following steps are needed to use a Loop Controller.
Step: 1 Design
1, 2, 3... 1. Prepare function drawings.
2. Determine the PLC configuration.
3. Select the function blocks.
4. Determine the configuration of the function blocks.
5. Determine the data to be monitored or operated in the CX-Process Monitor.
6. Install the CX-Process Tool, the CX-Process Monitor, and the communica­tions driver.
Model Length Remarks
XW2Z-200S-V 2 m
XW2Z-500S-V 5 m
XW2Z-200S-V 2 m
XW2Z-500S-V 5 m
---
Step 2: Creating Function Blocks
Starting from the Start Menu or Selecting Start Only from the I/O Tables
1, 2, 3... 1. Start the CX-Process Tool.
The following dialog box will be displayed by default when the CX-Process Tool is started.
Select the communications driver to use (FinsGateway or CX-Server).
This dialog box will not be displayed when starting by selecting Start Only from the CX-Programmer’s I/O tables. The CX-Server will automatically be selected as the communications driver.
36
Note (1) When using the CX-Process Monitor or CX-Process Monitor Plus, always
set FinsGateway as the communications driver. CX-Server is not supported as the communications driver for the CX-Process Monitor or CX-Process Monitor Plus.
1-7SectionBasic Operating Procedures
(2) For details on starting the CX-Process Tool, refer to 2-1-9 Starting the CX-
Process Tool.
2. Create a new project in the Project Workspace.
3. Go to step 3, below, and set the System common block.
Starting by Selecting Start with Settings Inherited from the I/O Tables
1, 2, 3... 1. Right-click the Loop Control Board or Unit in the I/O Table Window, and se-
lect Start Special Application - Start with Settings Inherited.
Example: Right-click on the Loop Control Board (e.g., CS1W-LCB05).
Select Start Special Application.
Select Start with Settings Inherited.
37
1-7SectionBasic Operating Procedures
2. The CX-Process Tool will start and a new project will be created. The Num­ber-Model setting (e.g., 00-LCB05) will be automatically selected based on the Loop Control Board/Unit model in the I/O tables.
The node is inserted automatically.
The Insert LCB/LCU Dialog Box will be displayed.
The Number-Model (e.g., 00-LCB05) is set automatically, based on the Unit/Board model in the I/O Table Window.
3. Set the System Common Block.
4. Register the function block.
Note (1) For details on setting the System Common Block, refer to 3-1-5 Making Sys-
tem Common Block Initial Settings.
For details on registering function blocks, refer to 3-1-6 Registering
(2)
Function Blocks.
38
1-7SectionBasic Operating Procedures
5. Set the software connections between function blocks with analog and ac­cumulator signals (using Edit – Block Diagram from the Settings Menu).
6. Set the ITEMs in all function blocks (and set user link tables or create se­quence tables or step ladder programs as needed).
Note a) User link tables are supported by LCBs only.
b) Sequence tables are supported by LCB05 and LCB05D (LCB ele-
ments 00-LCB05 and 00-LCB05D) only.
7. Go to step 8 in one of the following sections.
Note (1) For details on editing block diagrams, refer to 3-1-8 Editing Block Diagrams.
(2) For details on editing function block ITEMs, refer to 3-1-9 Editing Function
Block ITEMs.
Using CX-Process Monitor (Supported Only for Loop Control nits)
8.Set the function block for data exchange with CX-Process Monitor, i.e., the Block Send Terminal to Computer Function Blocks.
9.Create the monitor tag file (using Tag Settings – Monitor Tag from the Set- tings Menu).
10.Create the monitor tag file (using Create Tag File – Monitor Tag from the Execution Menu).
39
Using CX-Process Monitor Plus
1-7SectionBasic Operating Procedures
Note Install the CX-Process Monitor on the same personal computer be-
fore creating monitor tag files.
The procedure depends on whether a Loop Control Unit or Loop Control Board (LCBs) is being used.
Loop Control Units
8.Register and connect the function blocks to exchange data with the CX-Pro­cess Monitor Plus.
Items to
monitor
Function block data
Contact signals
Analog signals
Registrations and
connections
Only register the function blocks.
Register and connect the function blocks.
Register and connect the function blocks.
Loop Control Unit
Send All Blocks block (Block Model 462) and Receive All Blocks block (Block Model 461)
Contact Distributor (Block Model 201) or Internal Switch (Block Model 209)
Input Selector block (Block Model 162) and Constant Generator block (Block Model 166)
9.Set CSV tags and tags for the CX-Process Monitor Plus as follows:
• Function block data: Set CSV tags.
• Individual contact signals: Set CX-Process Monitor Plus tags for the con-
tacts in the Internal Switch block (Block Model 209).
• Individual analog signals from LCU element to computer: Set CX-Process
Monitor Plus tags for the analog signals in the Input Selection block (Block Model 162).
• Individual analog signals from computer to LCU element: Set CX-Process
Monitor Plus tags for the analog signals in the Constant Generator block (Block Model 166).
10.Generate the CX-Process Monitor Plus tag file (Execute – Create Tag File – Monitor Plus Tag).
11.Start the CX-Process Monitor Plus and click the Start Button.
s
LCB
8.Register and connect the function blocks to exchange data with the CX-Pro­cess Monitor Plus.
40
Items to
monitor
Function block data
Contact signals
Analog signals
Registrations and
connections
Only register the function blocks.
Register and connect the function blocks.
Register and connect the function blocks.
LCBs
HMI settings in the System Common block (Block Mode 000)
Contact Distributor (Block Model 201) or Internal Switch (Block Model 209)
Input Selector block (Block Model 162) and Constant Generator block (Block Model 166)
9.Set CSV tags and tags for the CX-Process Monitor Plus as follows:
• Function block data: Set CSV tags.
• Individual contact signals: Set CX-Process Monitor Plus tags for the con-
tacts in the Internal Switch block (Block Model 209).
• Individual analog signals from LCB element to computer: Set CX-Process
Monitor Plus tags for the analog signals in the Input Selection block (Block Model 162).
• Individual analog signals from computer to LCB element: Set CX-Process
Monitor Plus tags for the analog signals in the Constant Generator block (Block Model 166).
10.Generate the CX-Process Monitor Plus tag file (Execute – Create Tag File – Monitor Plus Tag).
Using SCADA Software
1-7SectionBasic Operating Procedures
11.Start the CX-Process Monitor Plus and click the Start Button.
Note For all Loop Controllers, the following function blocks must be
created and connected separately to enable monitoring and setting individual contact signals and individual analog signals (i.e., other than function block data).
• To monitor and set individual contact signals, contact signals must be input/output using the Contact Distributor block (Block Model 201) and Internal Switch block (Block Model 209).
• To monitor individual analog signals, analog signals must be output from the Input Selection block (Block Model 162).
• To set individual analog signals, analog signals must be input to the Constant Generator block (Block Model 166).
Note (1) For details on the CX-Process Monitor, refer to 3-2 Using the CX-Process
Monitor.
(2) For details on the CX-Process Monitor, refer to 3-3 Using the CX-Process
Monitor Plus.
8.Set the Send All Blocks or Receive All Blocks Function Blocks (and if neces­sary, Expanded CPU Unit Terminal and CPU Unit Terminal Function Blocks). (Required only for Loop Control Unit; not required for LCB.
9.Set the CSV tags (using Tag Settings – CSV Tag from the Settings Menu). If using CX-Process Tool version 3.1 or higher, automatically register the CSV tags and then edit the CSV tag settings file in Excel.
10.Output the CSV tag file (using Create Tag File – CSV Tags from the Execu­tion Menu).
11.Import the CSV tag file for SCADA software into the SYSMAC OPC Server.
12.Manually export the RS View tag file from the SYSMAC OPC Server.
13.Import the RS View tag file to the RS View 32 using the import utility in the RS View 32.
Using the RS View 32
Step 3: Save the Project Workspace Data
Step 4: Unit Setup
1, 2, 3... 1. Mount the Units and wire the Analog I/O Units.
8.For a Loop Control Unit, register Send All Blocks and Receive All Blocks
blocks. (This is not necessary for LCB.)
9.Set the CSV tags (using Tag Settings – CSV Tag from the Setting Menu).
10.Output the CSV tag file (using Create Tag File – RS View Tags from the Execution Menu).
11.Import the RS View tag file directly to the RS View 32 using the import utility in the RS View 32.
Note For details on SCADA Software and RS View, refer to 3-4 Preparations for Using
SCADA Software.
Using Save from the File Menu
The Loop Controller does not need any wiring.
2. Set each Unit to a unique unit number.
3. Connect the Programming Device.
Note With CS1D CPU Units (using the CS1D-CPUP), connect to the
active CPU Unit.
4. Turn ON the PLC.
41
1-7SectionBasic Operating Procedures
5. Create the I/O tables with the Programming Device.
6. Set the PLC Setup serial communications port settings with the Program­ming Device if needed.
7. Set the allocated DM area of the Analog I/O Unit with the Programming De­vice.
Step 5: Transfer Created Function Block Data to Loop Controller
1, 2, 3... 1. Turn OFF the PLC.
The following steps are used when connected to the PLC via Host Link commu­nications.
2. Set the DIP switch on the front panel of the CPU Unit. Set pin 4 to ON to use the peripheral port and set pin 5 to OFF to use the RS-232C port. With a CS1D Duplex System, set the DIP switch on the front panel of the Duplex Unit. Turn ON PRPHL to use the peripheral port or turn ON COMM to use the RS-232C port.
3. Connect the CPU Unit to the personal computer (CX-Process Tool).
4. Turn ON the PLC.
5. If FinsGateway is being used:
With the CX-Process Tool, set the network address to between 0 and 127, the node address to 01, and the unit address to the unit number plus 10 hex­adecimal (input in decimal) (using Network Settings from the Settings Menu). (See section 4-2-2.)
6. If FinsGateway is being used:
Connect the CX-Process Tool via Host Link communications (using Acti- vate Serial Port Driver from the File Menu). (See section 4-2-2.)
7. Download the function block data from the CX-Process Tool (using Trans- fer to LC – Selected from the Execution Menu). (See section 4-3-1.)
8. Start operation from the CX-Process Tool (using Operation – Run/Stop Command from the Execution Menu) or turn the PLC OFF and ON. (See section 4-4.)
Note Check the following items before operating the Loop Controller.
a) Make sure the Analog I/O Units used with the Loop Control Unit/Board
are properly mounted.
b) Make sure the unit numbers on the front panel of the Analog I/O Units
coincide with the unit numbers set in the Field Terminal Function Blocks. Data for another Special I/O Unit will be read and written if an incorrect unit number is used.
c) Make sure the initial settings in the System Common Block in the Loop
Controller are correct. Check that the DM Area words for the Node Termi­nal Function Block in the CPU Unit of the Loop Controller will not be used for any other purpose.
d) When writing data to the I/O memory in the CPU Unit with function blocks
(e.g., using Send All Blocks, Expanded DO/AO Terminal to CPU Unit, or DO/AO Terminal to CPU Unit), be sure that the words written to in the I/O memory are not being used for any other purpose. If I/O memory words are allocated to more than one purpose, the PLC system may act unex­pectedly and cause injury.
9. Check the indicators on the front of the from panel of the Loop Controller: On the Loop Control Unit, the RUN indicator should be lit and the ERC indicator not lit. On the LCB, the EXEC indicator should be lit.
Note With the CS1D-CPUP, approximately 2 minutes is required after
power is turned ON for duplex initialization before the standby Loop Controller will start operation. The EXEC indicator and the DPL STA-
42
Step 6: Trial Operation
1, 2, 3... 1. Start operation from the CX-Process Tool (using
1-7SectionBasic Operating Procedures
TUS indicator on the Duplex Unit will flash for 40 seconds before light­ing.
Operation – Run/Stop
Command from the Execution Menu) or turn the PLC OFF and ON. (See
section 4-4.)
2. Monitor status with the CX-Process Tool (using Operation – Monitor Run Status from the Execution Menu) and check the load rate, for example. (See section 4-5.)
3. Check the connections with the CX-Process Tool (using Start from the Vali- date Action Menu). (See section 4-6-3.)
4. Tune parameters such as PID constants and make SP settings with the CX­Process Tool.
43
Editi
Step 7: Actual Operation
1, 2, 3... 1. Make any necessary settings and adjustments such as PID tuning with the
CX-Process Tool, SCADA software, the CX-Process Monitor, or the CX­Process Monitor Plus.
2. Monitor the PV and all alarms from SCADA software, the CX-Process Moni­tor, or the CX-Process Monitor Plus.
Note The CX-Process Monitor can be used for the Loop Control Units only.
It cannot be used for the LCBs.

1-8 Operations

1-8-1 Creating Function Blocks
Item Menu item Section
Creating a new Project Workspace New from the File Menu 3-1-3
Registering function blocks 1. Select the function block group folder.
2. Select Insert – Insert Function Block from the Settings Menu, or right-click on the block diagram and select
Register – Field Terminal/Sequence Control/Control Block.
Creating software connection between function blocks
Settings ITEMs 1. Double-click the function block registered on the
Registering elements in the user link table
Registering from the User Link Table
ng Screen
Creating software links by pasting user link tables in a block diagram
Registering elements individually
Registering elements in groups with same tag name and serial numbers (CX-Process Tool Ver. 3.2 or higher)
1. Select the folder for block diagram 1.
2. Select Edit – Block Diagram from the Settings Menu.
3. Select the function block to be pasted.
4. Click the right mouse button at the pasting position. Select Paste Function Block from the pop-up menu.
5. Select the block and change the position.
6. Click the start point of the connection and double-click the end point.
Project Workspace Screen.
2. Double-click each ITEM.
3. Set the data in the Setting Dialog Box.
1. Select Edit – User Link Table from the Settings Menu.
2. Right-click and select Register.
1. Select Edit – User Link Table from the Settings Menu.
2. Right-click and select Block Set.
1. Right-click and select Register – User Link Table
– Link input (Read from CPU Memory) or select Register – User Link Table – Link output (Write to CPU Memory) from the pop-up menu.
2. Right-click and select Register – User Link Table – Register Block Cell and then select a tag or
input a new tag.
3. Software link.
3-1-6
3-1-8
3-1-9
3-5-2
3-5-2
1-8SectionOperations
44
Item SectionMenu item
Attaching user-defined comments (annotations) to function blocks and step ladder diagrams, displaying/printing comments
Settings tags for CX-Process Monitor (Loop Control Unit only)
Compiling tags for Monitor Software (Loop Control Unit only)
Checking tags for Monitor Software settings (Loop Control Unit only)
Settings tags for CX-Process Monitor Plus (CX-Process Tool Ver. 3.2 or higher)
Compiling tags for CX-Process Monitor Plus (CX-Process Tool Ver. 3.2 or higher)
Checking tags for CX-Process Monitor Plus settings (CX-Process Tool Ver. 3.2 or higher)
Creating (compiling) the CSV tag file for SCADA software
Creating (compiling) an RS View tag file (.csv) 1. Select the function block and select Tag Settings
Creating sequence tables (LCB05/05D only) 1. Select the sequence table block.
In the Function Block Connection Diagram, click the right mouse button to display the pop-up menu and select Annotations/Insert.
Click the Annotation icon in Ladder Diagram Edit Mode.
1. Select the Send Terminal to Computer folder (block models between 401 and 404) or the Send Terminal to All Nodes (block models between 407 and 410).
2. Select Tag Settings – Monitor Tags from the Settings Menu.
1. Select Create Tag File – Monitor Tags from the Execution Menu.
2. Click the Start Button
1. Select Show Tag List – Monitor Tag from the Execution Menu.
1. Select the function blocks and select Tag Settings – CSV Tags from the Setting Menu, or select function blocks for data exchange with the CX-Process Monitor Plus and select Tag Settings – Monitor Plus Tags from the Setting Menu. or Select the option to automatically register CSV tags when registering function blocks and edit the CSV tag file in Excel or other editor.
1. Select Create Tag File – Monitor Plus Tag from the Execution Menu.
2. Click the Start Button on the main window of the CX-Process Monitor Plus.
1. Select Show Tag List – Monitor Plus Tag from the Execution Menu.
1. Select the function block and select Tag Settings – CSV Tags from the Settings Menu to set the CSV tags. or Select the option to automatically register CSV tags when registering function blocks and edit the CSV tag file in Excel or other editor.
2. Compile the CSV tag file by selecting Create Tag
File – CSV Tags from the Execution Menu.
– CSV Tags from the Settings Menu to set the
CSV tags. or Select the option to automatically register CSV tags when registering function blocks and edit the CSV tag file in Excel or other editor.
2. Compile the RS View tag file by selecting Create Tag File – RS View Tags from the Execution Menu.
2. Select Edit – Sequence Table from the Settings Menu.
3. Right-click on the sequence table and select Edit
Mode – Enable.
4. Double-click the sequence table and input the data into the Signal Dialog Box.
1-8SectionOperations
3-7-1
3-2-1
3-2-1
3-2-2
3-3
3-3
3-3
3-4-1
3-4-1
3-8-1
45
Item SectionMenu item
Inputting step ladder programs as ladder diagrams
1. Select the Step Ladder Program Block.
2. Select Edit – Ladder Program from the Settings Menu.
3. Select the icon and move it onto the ladder diagram and click the left mouse button.
4. Double-click the left mouse button on the ladder symbol. Input the data into the Data Setting Dialog Box.
1-8SectionOperations
3-7-1
Inputting step ladder programs in mnemonics 1. Select the Step Ladder Program Block.
2. Select Edit – Ladder Program from the Settings Menu.
3. Select Mnemonics from the Manipulate Ladder Menu.
4. Click the Insert Row Button.
5. Input the instructions.
Printing function blocks, block diagrams, etc. 1. Select Print from the File Menu, then select each
data type.
1-8-2 Online Operations
Item Menu item Section
Connecting via serial communications 1. Activate and select the folder of the function block file.
2. Select Network Settings from the Settings Menu.
3. Input the network address.
4. Set the node address to 01.
5. Select the LCU/LCB element (by default set to LC001-1).
6. Select Network Settings from the Settings Menu.
7. Input the unit address.
8. Select Activate Serial Port Driver from the File Menu.
9. Click the OK Button.
3-7-2
3-11
4-2-2
Downloading function block data 1. Activate the folder of the function block file and select the
LCU/LCB element (default: LC001-1).
2. Select Transfer to LC – Selected from the Execution Menu. When the version is different from the Loop Controller element version, a warning dialog will be displayed. Click the OK Button and continue.
3. Click the OK Button.
4. If a step ladder program is included, click the OK Button for Convert Ladder To Mnemonics per LCU/LCB element.
5. Click the OK Button.
6. Set the objective item and start downloading the data.
Downloading each ITEM’s data (Transferring to LC)
1. Select Monitor/ITEM List from the Execution Menu to display the ITEM list, or double-click the function block registered on the Project Workspace Screen.
2. Double-click each ITEM.
3. Set the desired value and click the Transfer to LC Button.
46
4-3-1
4-3-1
Item SectionMenu item
gy
Uploading function block data (Transferring from LC)
Comparing function block file
Starting a Loop Controller 1. Activate the folder of the function block file and select the
Checking system operation of Loop Controller
Wireless Debug Select the function block that performs the pseudo-input from the
With another function block file
With function block data in a Loop Controller
Load rate check
Block address with execution error
1. Activate the folder of the function block file and select the LCU/LCB element (default: LC001-1).
2. Select Transfer from LC – New or Transfer from LC – Previous from the Execution Menu.
3. Click the OK Button or Start Button.
4. Check and click the OK Button.
5. Click the Start Button or OK Button.
1. Activate and select the folder of the function block file.
2. Select Compare from the Execution Menu.
3. Select the function block file and select the level.
4. Select Compare.
1. Activate the folder of the function block file and select the LCU/LCB element (default: LC001-1) or function block.
2. Select Compare from the Execution Menu.
3. Select the function block file and select the level.
4. Select Compare.
LCU/LCB element (default: LC001-1).
2. Select Operation – Run/Stop Command from the Execute Menu.
3. Select HOT START or COLD START.
4. Select Execute.
1. Activate the folder of the function block file and select the LCU/LCB element (default: LC001-1).
2. Select Operation – Monitor Run Status from the Execute Menu.
block diagram and then select Wireless Debug from the right-click menu.
1-8SectionOperations
4-3-2
4-3-3
4-3-3
4-4
4-5
4-6-4
47
Preparations to Create Function Blocks
This section describes installing the CX-Process and provides an overview of the user interface.
2-1 Installing and Uninstalling the Software 50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-1-1 Software That Must Be Installed 50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-1-2 Preparations for Installation 51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-1-3 Precautions for Installation 52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-1-4 Installing the CX-Process the CX-Server 52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-1-5 Installing FinsGateway 56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-1-6 Installing FinsGateway Embedded Version 58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-1-7 Uninstalling the CX-Process Tool 65. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-1-8 Uninstalling the CX-Server 66. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-1-9 Starting the CX-Process Tool 68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-2 Overview of User Interface 69. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-2-1 Project Workspace Tree 71. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-2-2 Output Window 71. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-2-3 Menus 73. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SECTION 2
49

2-1 Installing and Uninstalling the Software

2-1-1 Software That Must Be Installed
The following software must be installed on the same computer to use the CX­Process Tool.
1, 2, 3... 1. CX-Process Tool
2. CX-Server (the communications driver) or FinsGateway Embedded Ver­sion 3 or higher
2-1SectionInstalling and Uninstalling the Software
Types of CX-Programmer
The CX-Process Tool is available both on an independent CD-ROM and on the CX-One FA Integrated Tool Package. The contents of the CX-Process Tool are the same in either case.
The installation procedure for the independent CD-ROM is provided here. Refer to the CX-One Ver. 2.0 Setup Manual (W463, provided with the CX-One) for the installation procedure for the CX-One.
Cat. No. Model Manual name Contents
W463
Selecting Communications Drivers
Select the communications driver to be installed (CX-Server or FinsGateway). The following table shows the selection criteria.
Yes: Supported No: Not supported
• Communications Method
Communica-
tions driver
CX-Server Ye s No Ye s
FinsGateway Ver. 3
FinsGateway Ver. 2003
CXONE-ALC-E V2/ALD-EV2
Toolbus Duplex Ethernet at
No No No
Yes Ye s No
CX-One Ver. 2.0 Setup Manual
Communications method
personal computer
An overview of the CX-One FA Integrated Tool Package and the CX-One installation procedure
Simultaneous online
(serial) connection
with CX-Programmer
50
• Compatible Applications
Communica-
tions driver
CX-Server No No No
FinsGateway Ver. 3
FinsGateway Ver. 2003
CX-Process
Monitor
Yes Ye s Yes
NO Ye s Yes
Application
CX-Process
Monitor Plus
SYSMAC OPC
Server
The CX-Process Tool Setup Disk contains each of the communications drivers. The following .exe files are required for setup.
• CX-Server (See note.)
<CD-ROM drive>:\CX-Process Tool\CX-Server\setup.exe
Note The CX-Server will be installed at the same time as the CX-Process Tool.
• FinsGateway Ver. 3
<CD-ROM drive>:\Fgwv3\FGW3ee\Serial\disk1\SETUP.EXE <CD-ROM drive>:\Fgwv3\FGW3ee\ETN\disk1\SETUP.EXE <CD-ROM drive>:\Fgwv3\FGW3ee\CLK(PCI)\disk1\SETUP.EXE <CD-ROM drive>:\Fgwv3\FGW3ee\CLK\disk1\SETUP.EXE
• FinsGateway Ver. 2003 <CD-ROM drive>:\Fgw2003\Fgw2003\Disk Images\Embed\setup.exe
2-1-2 Preparations for Installation
Note If the CX-Process Tool was previously installed from the CX-One and it is neces-
sary to update it from the individual CX-Process Tool CD-ROM, always uninstall the CX-Process Tool using the following CX-One uninstall procedure before installing it from its individual CD-ROM.
2-1SectionInstalling and Uninstalling the Software
Uninstalling the Previous Version of CX-Process Tool
1, 2, 3... 1. Start Add/Remove Programs (or Add/Remove Applications) from the
Always uninstall the previous version of the CX-Process Tool before installing the new version.
control panel.
2. Select CX-Process Tool from the dialog box.
3. Click the Change/Remove Button. The CX-Process Tool will be uninstalled.
Uninstalling the CX-Server PLC Tools
If CX-Server PLC Tools is installed, then uninstall it.
51
Note Do not uninstall the CX-Server Driver Management Tool or the CX-Server from
the control panel. Doing so may make it impossible to use certain Units.
2-1-3 Precautions for Installation
• Close all programs running on Windows before starting the installation proce-
dure.
• Do not stop the setup process in the middle. Copied files may remain in the
installation folder.
• Do not turn OFF or reset the computer in the middle of the installation process.
Computer data may become corrupted.
• On Windows NT 4.0, 2000, XP, or Vista, the administrator or a user with admin-
istrator rights must perform the installation. Other users will not have sufficient write permission and access errors will occur.
Note Internet Explorer version 5.0 or higher must be installed in advance to use the
CX-Server Installer. Install Internet Explorer version 5.0 in advance if it is not al­ready installed.
2-1SectionInstalling and Uninstalling the Software
2-1-4 Installing the CX-Process the CX-Server
1, 2, 3... 1. Place the CX-Process installation disk (CD-ROM) into the disk drive.
2. Double-click the Setup.exe Icon in the CX-Process Tool\Disk1 folder in the CD-ROM from Windows Explorer or other software.
A dialog box indicating that setup preparations are in progress will be dis­played and then the InstallShield Wizard will be displayed. Click the Next Button.
52
3. The License Agreement Dialog Box will be displayed.
Read the license agreement completely and if you accept all of the terms, select the I accept the terms of the license agreement Option and click the Next Button.
4. The User Information Dialog Box will be displayed.
2-1SectionInstalling and Uninstalling the Software
The default names registered in the computer will be entered for the user name and company name. Enter the license number and click the Next But- ton. The license number is given on the Software License/Registration Card provided with the product.
5. The Choose Destination Location Dialog Box will be displayed.
53
Select the destination location and click the Next Button. By default, the CX­Process Tool will be installed in the following location: C:\Program Files\OMRON\CX-One\CX-Process Tool\.
6. The Setup Type Dialog Box will be displayed.
2-1SectionInstalling and Uninstalling the Software
Select the Complete or Custom Option and click the Next Button.
7. The Select Features Dialog Box will be displayed if Custom was selected.
Note The above dialog box will not be displayed if Complete is selected.
Proceed to step 8.
Select the features to be installed and click the Next Button.
54
Options
Note Only the CX-Server can be installed at the same time as the CX-Process Tool. To
use FinsGateway as the communications server, refer to 2-1-5 Installing Fins­Gateway.
8. The Select Program Folder Dialog Box will be displayed.
Specify the location to add a shortcut in the program folder of the Windows Start Menu and click the Next Button.
9. The Ready to Install the Program Dialog Box will be displayed.
2-1SectionInstalling and Uninstalling the Software
Click the Install Button.
The Installer will start the installation.
To check the installation settings, click the Back Button.
To cancel installation, click the Cancel Button.
10. If the CX-Server is already installed on the computer, the Installer will auto­matically check the CX-Server version and driver and update them as re­quired. Depending on the version of CX-Server that was already installed, and confirmation dialog box may be displayed.
55
2-1SectionInstalling and Uninstalling the Software
11. The following dialog box will be displayed when the Installer completes the installation. Click the Finish Button.
Note It might be necessary to restart Windows after completing the installation. If nec-
essary, restart Windows according to the message from the Installer.
12. The Readme.txt file will be displayed after the computer is restarted.
13. The Online Registration Dialog Box will be displayed when the Readme.txt file is closed.
A wizard will be started and will connect to the OMRON CX-One Web if the
Register Button is clicked. (See notes.)
Note a) If the Exit Button is clicked to cancel registration, the Online Reg-
istration Dialog Box will be displayed every time the CX-One Con­figuration Tool is started.
b) Online installation will not be possible if the computer is not con-
nected to the Internet. Enter the required information on the regis­tration card and mail it in.
This completes installation of the CX-Programmer.
2-1-5 Installing FinsGateway
One of the following communications drivers must be installed in the computer to enable using the CX-Process Tool.
• CX-Server (Installed at the same time as the CX-Process Tool.)
• FinsGateway Version 3 or higher
FinsGateway Version 3 or FinsGateway 2003 Embedded Version is bundled with the CX-Process Tool. Install one of the to use FinsGateway as the commu­nications driver.
The FinsGateway Runtime Version can also be used. If the FinsGateway Run­time Version is already installed, it is not necessary to install an embedded ver­sion.
Preparations before Installing FinsGateway
• If FinsGateway Version 2 or lower is already installed, perform Step 1: Backing
Up the FinsGateway Settings first.
56
Installing FinsGateway
Step 1: Backing Up the FinsGateway Settings
Note If FinsGateway is removed (uninstalled) without backing up the setting data, the
1, 2, 3... 1. Execute the Backup/Restore FinsGateway Setting Data program on the
2-1SectionInstalling and Uninstalling the Software
• If FinsGateway is being installed for the first time, start the procedure from Step
4: Internet Explorer Installation.
If necessary, back up the previous FinsGateway settings, as follows:
previous setting data will all be lost.
CD.
<CD-ROM drive>:\Fgwv3\FgwUtils\SettingSalvage.exe
Step 2: Removing the Previous FinsGateway
Step 3: System Restart
Step 4: Internet Explorer Installation
Step 5: Updating ComCtl32.dll
Step 6: Updating the HTML Help Runtime Component
2. Select the Backup to File option, and click OK.
Remove the previous version of FinsGateway by referring to that manual for de­tails.
Note If the FinsGateway reinstallation process fails, execute the following program
from the CD-ROM to remove all the files and registry data used by FinsGateway.
<CD–ROM drive>:\Fgwv3\FgwUtils\FgwRemover3.exe
After removing FinsGateway, restart the computer. If the following steps are per­formed without restarting the computer, the installation will not be completed properly.
If Internet Explorer is not already installed, or if the version is old, the FinsGate­way installation will display a warning to update it. Update Internet Explorer.
Microsoft Internet Explorer is not included on the CD-ROM. Refer to the
Microsoft website for details, and install the newest version.
If the program is not correctly displayed or does not operate correctly when using Windows NT 4.0, then update the ComCtl32.dll file. This is not necessary when using Windows 2000 or XP.
Use 401comupd.exe to update the ComCtl32.dll file. The 401comupd.exe file is an update program provided by Microsoft Corporation.
If the HTML Help runtime component is not already installed, or if the version is old, the FinsGateway installation will display a warning to update it. Update the HTML Help runtime component as follows:
1, 2, 3... 1. Execute the following program from the CD-ROM:
<CD-ROM drive>:\Fgwv3\Update\hhupd.exe
2. Update the HTML Help runtime component according to the instructions displayed on the screen.
3. The program will suggest a system restart when it finishes. Do not proceed to the next step without restarting the computer. If the instal-
57
lation is continued without restarting the computer, the FinsGateway will not operate properly.
2-1-6 Installing FinsGateway Embedded Version
The CX-Process Tool cannot be used if it is installed alone. Either the FinsGate­way Embedded Version or CX-Server must be installed on the same computer as the communications driver.
The CX-Process Tool comes with FinsGateway Embedded Version 3 and 2003. Install either version. FinsGateway Runtime Version can also be used. If the Runtime Version has been already installed, there is no need to install the Embedded Version.
Using FinsGateway Version 3
The FinsGateway Update 3.12 software must be installed after the FinsGate­way Embedded Version 3 software.
Installation of FinsGateway Version 3
1, 2, 3... 1. Select one of the following folders from within the Fgwv3/FGW3ee folder.
(Select the folder corresponding to the communications method being used in the PLC.)
2-1SectionInstalling and Uninstalling the Software
Folder
name
Clk Select this folder when connecting the PLC and personal computer
(the CX-Process Tool and the CX-Process Monitor) via Controller Link using a Controller Link Support Board (ISA bus) installed in an ISA slot in the computer.
Clk (PCI) Select this folder when connecting the PLC and personal computer
(the CX-Process Tool and the CX-Process Monitor) via Controller Link using a Controller Link Support Board installed in the computer’s PCI slot.
Etn Select this folder to connect the personal computer (the CX-Process
Tool and the CX-Process Monitor) to the PLC via Ethernet.
Serial Select this folder to connect the personal computer (the CX-Process
Tool and the CX-Process Monitor) to the PLC via the Host Link.
Details
The following procedure uses Host Link as an example.
58
2-1SectionInstalling and Uninstalling the Software
2. Using Windows Explorer or any other appropriate method, open Serial in the CD-ROM, and double-click the following icon inside the disk1 folder.
The following screen will appear.
3. Click the Next Button. The User Registration Dialog Box will appear.
4. Input the user name and the organization name and click the OK Button.
The following Confirmation Dialog Box will appear.
59
2-1SectionInstalling and Uninstalling the Software
5. Click the Yes Button. The following Choose Destination Location Dialog Box will appear.
6. Click the Yes Button. The following Select Program Folder Dialog Box will appear.
60
7. Check the installation folder and click the Next Button.
Installation of the program will start. The following dialog box will appear when the installation has been completed.
8. Click the Finish Button.
Installing FinsGateway Version 3 Update 3.12
1, 2, 3... 1. Using Windows Explorer or any other appropriate method, open the
Fgwv3/FgwUpdate folder in the CD-ROM, and double-click the following icon.
2. The following screen will appear.
2-1SectionInstalling and Uninstalling the Software
3. Click the Next Button. The following Information Dialog Box will appear.
61
2-1SectionInstalling and Uninstalling the Software
4. Check the installation folder and click the Next Button. The Start Copying Files Dialog Box will appear.
5. Check the installation folder and click the Next Button.
Installation of the program will start. The following dialog box will appear when the installation has been completed.
62
6. Click the Finish Button.
Installing FinsGateway Version 2003
1, 2, 3... 1. Double-click setup.exe in the Fgw2003 folder in the CD-ROM.
The following screen will appear.
2-1SectionInstalling and Uninstalling the Software
2. Click the Next Button to display the following screen.
3. Input the user name and company name, and then click the Next Button.
63
2-1SectionInstalling and Uninstalling the Software
4. Select the communications drivers that are required to run the CX-Process Tool.
5. Click the Next Button.
6. Specify the installation folder. Unless a particular folder is required, use the default location and click the Next Button.
7. The following window will be displayed. Click the Install Button to begin installation.
64
2-1SectionInstalling and Uninstalling the Software
8. The following screen will be displayed when installation has been com­pleted. Click the Finish Button and restart the personal computer.
Installation is now completed.
2-1-7 Uninstalling the CX-Process Tool
Use the following procedure to delete the CX-Process Tool from the computer.
1, 2, 3... 1. Select Settings - Control Panel - Add/Remove Programs or Settings -
Control Panel - Add/Remove Applications from the Windows Start Menu.
2. Select CX-Process Tool from the dialog box.
3. Click the Change/Remove Button.
65
2-1SectionInstalling and Uninstalling the Software
4. The CX-Process Tool Installation Wizard will be displayed. Select the Re­move Option and click the Next Button.
5. If deleting the CX-Process Tool completely is selected, the following dialog box will be displayed. Click the Yes Button to start the Uninstaller that will delete the CX-Process Tool.
6. When the uninstallation has been completed, the following dialog box will be displayed.
2-1-8 Uninstalling the CX-Server
Note (1) The Installer manages the version and driver for the CX-Server. If the CX-
Server installed on the computer is old, the Installer will automatically up­date the CX-Server. If the CX-Server Driver Management Tool or the CX­Server is uninstalled from the control panel, it may no longer be possible to use certain Units. Do not uninstall the CX-Server Driver Management Tool or the CX-Server from the control panel.
(2) Do not uninstall the CX-Server if there are Programming Devices (such as
the CX-Programmer) that use it as the communications driver. If the CX­Server is uninstalled, it will no longer be possible to use these other pro­grams.
66
2-1SectionInstalling and Uninstalling the Software
(3) Do not uninstall the CX-Server while other programs that use it as the com-
munications driver are running on the computer, e.g., the CX-Motion. The CX-Server may not uninstall properly if other programs are using it.
(4) Always uninstall the CX-Server Driver Management Tool before uninstalling
the CX-Server. If the CX-Server is uninstalled first, it may no longer be pos­sible to uninstall the CX-Server Driver Management Tool properly.
1, 2, 3... 1. Select Settings - Control Panel - Add/Remove Programs or Settings -
Control Panel - Add/Remove Applications from the Windows Start Menu.
2. Select CX-Server Driver Management Tool from the dialog box.
3. Click the Change/Remove Button.
Note Always close the Control Panel before uninstalling the CX-Server Driver Man-
agement Tool from Windows 98 or Windows NT 4.0. The CX-Server Driver Man­agement Tool cannot be uninstalled while the Control Panel is open.
4. A confirmation dialog box will be displayed. Click the Yes Button.
The CX-Server Driver Management Tool will be uninstalled.
67
2-1SectionInstalling and Uninstalling the Software
5. When the uninstallation has been completed, the following dialog box will be displayed. Click the Finish Button. The Add/Remove Programs Dialog Box will be displayed again.
6. In the same way, select CX-Server from the Add/Remove Programs Dialog Box, click the Change/Remove Button, and uninstall the CX-Server follow- ing the messages that appear on the screen.
7. Reboot the computer.
2-1-9 Starting the CX-Process Tool
1, 2, 3... 1. Select Program - OMRON - CX-One - CX-Process Tool - CX-Process
Tool from the Windows Start Menu. The following dialog box will appear to
select the communications driver.
68
2-2SectionOverview of User Interface
2. Select either FinsGateway or CX-Server as the communications driver and click the OK Button. The following screen will appear.
3. Refer to 3-1 Creating Function Block to continue.
Note The CX-Process Tool will not start with FinsGateway as the selected commu-
nications driver unless the FinsGateway Embedded Version 3 or higher has been installed in the computer. CX-Process Tool cannot be started using CX­Server if CX-Server is not installed.

2-2 Overview of User Interface

The CX-Process Tool consists of the following three basic panes (windows).
Project Workspace
Displays a data hierarchy tree.
Output Window
Displays execution results and error information, such as comparisons, tag error checks, and program transfers.
Contents Window
Displays the following contents:
• In Edit Block ITEM Mode, the contents of ITEMs in function blocks selected in the Project Workspace area on the left are displayed.
• In Edit Block Diagram Mode, function block connections in the block diagram selected in the Project Workspace area on the left are displayed.
• In Edit Step Ladder Diagram Mode, the ladder diagram for the Step Ladder Program Block selected in the Project Workspace area on the left is displayed.
• In Edit Sequence Table Mode, the sequence table for the Sequence Table Block selected in the Project Workspace area on the left is displayed.
Note Folders selected from the Project Workspace area are opened and function
blocks selected from the Project Workspace area are all highlighted.
69
2-2SectionOverview of User Interface
Operation via Menu and Toolbars
Functions, such as basic Windows operations, creating function blocks, and transfer operations, are available in the menu bar and the toolbar.
Menu bar
Toolbar
Project folder
Node function block folder
LCU/LCB
Project Workspace Area (Hierarchy)
The folder type of the function blocks is displayed. The folder that open here is the one presently selected.
The block addresses and names of function blocks registered under the folders are displayed.
Output Window
The name of the operation being executed, project information, and the execution results are displayed.
Names of project folder and active function block file
Annotation (User-set comments)
Contents Window
Contents of the various windows are displayed, such function block ITEMs, block diagrams, and step ladder programs. blocks selected in the Project Workspace area are displayed.
70
2-2-1 Project Workspace Tree
The Project Workspace tree shows the function block files, LCU/LCB elements, function block groups, and function blocks.
Function Block File
• Active: Red Inactive: White
• Node 01 to 32 (Node names cannot be changed.)
Project Workspace
• Pink folder
• Project folder name
• Each node corresponds to one CPU Unit. (You can create up to three LCU elements and one LCB
element under a node.)
• You can create up to 32 nodes in one Project Workspace.
• Displays the CPU Unit model for Loop-control CPU Units when FinsGateway is used as the commu-
nications driver.
LCU/LCB Element
• Yellow folders
• Set by default to LCB01, LCB05, LCB05D, or LC001-1 (Names can be changed.)
• “Not registered” will be displayed if no unit address has been set.
• The network address, node address, and unit address will be displayed after the unit address
is set.
Function Block Group (Classified by the CX-Process Tool)
• Sky-blue folder
• Only block diagrams can be created.
• The name will be displayed after the function block group number.
(Block diagram names can be changed.)
2-2SectionOverview of User Interface
Note To restore the original Project Workspace display (i.e., the display up to the func-
2-2-2 Output Window
Function Blocks
• Icons indicating data (Selected: Red; Not selected: Blue)
• The function block names will be displayed after the block address.
Name Description Example
Project Workspace Data consisting of up to 32 function
Equipment A block files. The same data capacity as a project folder.
Function block files Data for a single PLC (CPU Unit).
Node 01 Consisting of up to three Loop Control Units and one LCB.
Loop Controller Data for a single Loop Controller LC001-1
Function block groups
Classifications, such as block diagrams, determined by the CX-Process Tool.
Block diagram 1
Function blocks Individual function blocks Basic PID
tion block file), right-click on the Project Workspace, and then select Initialize Workspace Display from the pop-up menu.
The execution results of operations are displayed in the Output Window.
Project Information Display
The names of operations being executed are displayed, along with project information.
Results List Display
The execution results of operations shown in the Output Window are dis­played.
71
Jumping
2-2SectionOverview of User Interface
Descriptions of Items
Output Window Contents Example
Project Information Display
Results List Display Execution results are displayed for the
• Double-clicking on an error message causes the display to jump to the relevant location.
Executed operations and related project information are displayed.
following operations:
• Comparisons
• CX-Process Monitor, CSV, and CX-Pro-
cess Monitor checks
• Step ladder program assembly and re­verse assembly
• Sequence table error checks
• User-defined block exporting and im-
porting
• Program transfers (displayed only when an error occurs)
Result of model number conversion:
LCB05GTC V3.0 to LCB05 V3.0
Block Number 021 cannot be converted (Block Number 001).
Copying
• Pressing the F4 Key causes the display to jump to the relevant location for the next error message.
Note The display does not jump to the relevant display message location in the follow-
ing cases:
• When the node file, LCB or LCU element, function block group, or function block at the specified jump destination does not exist.
• When the specified jump destination is not an active node.
1, 2, 3... 1. Select Copy All from the pop-up menu in the Output Window. (Right-click to
display the pop-up menu.)
2. Select Paste to paste the contents of the Output Window display into a spreadsheet, such as one created with Excel.
72
Note To clear the display, select Clear from the pop-up menu.
2-2-3 Menus
Menus in Edit Block ITEM Mode
Main Menus
Menu Submenu/
Command
File
New Creates a Project Workspace and project.
Open Opens a multi-node file in the current project folder. All
related files are opened automatically. Close Closes the current Project Workspace.
Save Saves the current Project Workspace and overwrites the
previous one in the project folder. Save As Saves the current Project Workspace in a different project
folder. Add IST File Imports a function block file (.ist) created in version 1.00
into the current Project Workspace.
Note If the active function block file has been changed, it
Sort
Page Settings
Print
Recent File Displays up to the four files most recently used.
Activate Serial Port Driver
Find LCU Displays the serial (Host Link), Controller Link, or Ethernet
Manual Sorts function block files in order of node numbers.
Auto If checking is enabled, function block files are read in
order of node numbers when Add IST File or Open is
selected.
Block Diagram
Function Block
Block Diagram
Cross­Refer­ence
Se­quence Control
All Prints all of the above.
Monitor Tag List
CSV Tag List
Monitor Plus Tag List
User Link table
Connec­tion Map
Used to select one of the following page formats when
printing block diagrams.
A4 landscape, A4 portrait, A3 landscape, A3 portrait
(The printing size must also, however, be matched to the
setting.)
Prints a list of registered function blocks and a list of all
ITEMs.
Prints block diagrams.
Prints cross-references.
Prints sequence tables.
Prints the monitor tag list.
Prints a list of CSV tags.
Prints a list of CX- Process Monitor Plus tags.
Prints user link tables.
Prints a connection map.
Connects to the PLC via Host Link.
Link networks of the PLC to which the CX-Process Tool is
connected and searches for Loop Controllers. It gets the
network addresses, node addresses, and unit address of
all Loop Controllers found and sets them in the currently
active node function block file.
2-2SectionOverview of User Interface
Description Conditions for
selection
---
must be saved before executing the above.
---
When an LCU or LCB element is selected
73
2-2SectionOverview of User Interface
co ued
e
Ceee s
gU
Menu Conditions for
Command
File, continued
View
Settings
Show Driver Select Dialog
Exit Exits the CX-Process Tool.
Toolbar Displays or hides the toolbar.
Project Workspace Displays or hides the Project Workspace area.
Output Window Displays or hides the Output Window. Engineer-
ing Unit Mode
Activate Function Block File
Network Settings Sets the network address, node address, and unit
Change PLC Makes initial settings for online connections such as the
Ta g Setting
Show The Communications Driver Dialog Box will be displayed
when the CX-Process Tool starts.
Hide The Communications Driver Dialog Box will not be
displayed when the CX-Process Tool starts.
View Toggles between Engineering Unit mode and Percentage
Mode.
Assert Rounding Errors
Monitor Tag (Loop Control Unit only)
CSV Tag Sets CSV tags for each function block for output to
Monitor Plus Tag
Toggles between displaying and hiding the Engineering
Unit Assert Rounding Errors Dialog Box.
Activates the selected function block file so that the file
can be edited or operated online. When the file is
activated, the function block file on the tree will turn red.
Note If the current function block file has been changed, it
must be saved before executing this command.
address.
PLC model and network type settings when connecting
online with CX-Server.
Sets tags for CX-Process Monitor (with the tag names, tag
comments, scaling, and units).
SCADA software. Tags include the tag name, tag
comment, scaling, unit, etc.
Note The tag names are representative tags. The ITEM
tags under the tags are predetermined and fixed for each function block. These can be saved in CSV for­mat as CSV tag files.
Sets tags for CX-Process Monitor Plus (with the tag
names, tag comments, scaling, and unit).
DescriptionSubmenu/
selection
When an LCU or LCB element is selected
---
When a function block file is selected
When a function block file or LCU/LCB element is selected
When a function block file is selected
When a Block Send Terminal to Computer or Area to Send to All Nodes Function Block is selected
When a function block file is selected
When a Send All Blocks, Receive All Blocks, Contact Distributor, Internal Switch, Input Selector, or Constant Generator block is selected
74
Loading...
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use