Application Builder Software User’s Guide

for MODCELLTM
and MOD 30MLTM

2006S Version 5
 ABB INSTRUMENTATION
BS EN ISO 9001 Rochester USA - Stonehouse -
St Neots - Certificate No. Certificate No. Certificate No. 0255
Q5907 AQ-8618
Stonehouse - Certificate
No. FM 21106

The Company Use of Instructions

ABB Instrumentation is an established world force in the de- Warning. An instruction that draws attention to
sign and manufacture of instrumentation for industrial pro- the risk of injury or death.
cess control, flow measurement, gas and liquid analysis and
environmental applications.
We are committed to teamwork, high quality manufacturing, ! Caution. An instruction that draws attention to
advanced technology and unrivaled service and support. the risk of the product, process or surroundings.

The quality, accuracy and performance of the Company's

products result from over 100 years experience, combined * Note. Clarification of an instruction or additional
with a continuous program of innovative design and develop- information.
ment to incorporate the latest technology.
The NAMAS Calibration Laboratory No. 0255(B) is just one i Information. Further reference for more detailed
of the ten flow calibration plants operated by the Company, information or technical details.
and is indicative of ABB Instrumentation's dedication to qual-
ity and accuracy.
As a part of ABB, a world leader in process automation Although Warning hazards are related to personal injury,
technology, we offer customers application expertise, service and Caution hazards are associated with equipment or
and support worldwide. property damage, it must be understood that operation of
damaged equipment could, under certain operational
conditions, result in degraded process system performance
Health and Safety leading to personal injury or death. Therefore, comply fully
with all Warning and Caution notices.
To ensure that our products are safe and without risk to
health, the following points must be noted:
Information in this manual is intended only to assist our
1. The relevant sections of these instructions must be read customers in the efficient operation of our equipment. Use of
carefully before proceeding. this manual for any other purpose is specifically prohibited
2. Warning Labels on containers and packages must be and its contents are not to be reproduced in full or part
observed. without prior approval of the Technical Communications,
3. Installation, operation, maintenance and servicing must ABB Instrumentation.
only be carried out by suitably trained personnel and in
accordance with the information given or injury or death
could result. Licensing, Trademarks and Copyrights
4. Normal safety procedures must be taken to avoid the MODCELL™, MOD 30ML™ and PC-30™ are trademarks of
possibility of an accident occurring when operating in Asea Brown Boveri, Inc.
conditions of high pressure and/or temperature. IBM®, and IBM PCAT are trademarks of International Busi-
5. Chemicals must be stored away from heat, protected ness Machines Corp.
from temperature extremes and powders kept dry. SentinelPro™ is a trademark of Rainbow Technologies, Inc.
Normal safe handling procedures must be used. Microsoft® is a registered trademark of Microsoft Corp.
AutoCAD™ is a trademark of Autodesk, Inc.
6. When disposing of chemicals, ensure that no two
chemicals are mixed.
Safety advice concerning the use of the equipment de-
scribed in this manual may be obtained from the Company
address on the back cover, together with servicing and
spares information. P.O. Box 20550
Rochester, NY 14602-0550
(716) 292-6050
Printed in U.S.A. © 1997, ABB Instrumentation Inc
 Application Builder
CONTENTS

CONTENTS
Page
SECTION 1 - INTRODUCTION
1.1 PURPOSE OF DOCUMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.2 ORGANIZATION OF DOCUMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.3 OVERVIEW OF PRODUCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
1.3.1 Application Builder Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
1.3.2 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1.3.3 Communication Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1.4 EXPLANATION OF CATALOG NUMBER . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
1.5 RELATED DOCUMENTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

SECTION 2 - INSTALLATION
2.1 SOFTWARE INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2.2 CABLE CONNECTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

SECTION 3 - USER BASICS

3.1 GENERAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.2 STARTING APPLICATION BUILDER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.3 DISPLAY CHARACTERISTICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.4 USING YOUR KEYBOARD AND MOUSE . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3.4.1 Mouse Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3.4.2 Keyboard Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
3.4.3 Accepting Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
3.5 MESSAGE POSTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
3.6 FUNCTION BLOCK EDIT DISPLAYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
3.7 SUGGESTED NAMING CONVENTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
3.8 NAVIGATING THROUGH STRATEGY . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
3.9 COMPOUNDING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
3.9.1 Grouping and Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
3.9.2 Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
3.9.3 Execution Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
3.9.4 Saving and Loading Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
3.10 MAKING CONNECTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
3.11 INPUT CONVENTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13

SECTION 4 - TOOLBAR REFERENCE

4.1 GENERAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.2 EXIT SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.3 LOAD DATABASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.4 SAVE DATABASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

i
Application Builder
CONTENTS

CONTENTS (Cont’d)
Page
4.5 SERIAL PORT SETUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
4.6 INSTRUMENT FUNCTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
4.6.1 Compile Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
4.6.2 Download Database (and Communication Setup) . . . . . . . . . . . . . . . . . . . 4-7
4.6.3 Upload Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
4.6.4 Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
4.6.5 Status of Instrument Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
4.6.6 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
4.6.7 LCP Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
4.7 ERASE (Delete) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
4.8 MOVE TO CLIPBOARD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
4.9 COPY TO CLIPBOARD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
4.10 PASTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
4.11 QUERY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
4.11.1 Example of Block Query at System Level . . . . . . . . . . . . . . . . . . . . . . . . 4-14
4.11.2 Example of Connection Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
4.12 FIND TAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
4.13 REPORT OPTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
4.13.1 Database Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
4.13.2 Export to DXF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
4.13.3 Screen Dump to Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
4.14 PREFERENCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
4.14.1 View Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
4.14.2 Execution Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
4.14.3 Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
4.14.4 Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
4.15 ZOOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
4.16 LIBRARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
4.17 SELECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
4.18 SCREEN REFRESH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
4.19 HELP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
4.20 ABOUT THIS SOFTWARE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
4.21 CHECK DATABASE EXECUTION ORDER . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
4.22 I/O GRAPHIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
4.23 COMPOUND OPERATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
4.24 CONNECTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
4.25 WIRELESS CONNECTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34

ii
 Application Builder
CONTENTS

CONTENTS (Cont’d)
Page
SECTION 5 - CONFIGURATION
5.1 GENERAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
5.2 CONFIGURATION PROCEDURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
5.3 SYSTEM BLOCKS (INSTRUMENT LIBRARY) . . . . . . . . . . . . . . . . . . . . . . 5-4
5.4 I/O AND COMMUNICATION MODULE BLOCKS . . . . . . . . . . . . . . . . . . . . . 5-6
5.4.1 Communications Module Block Selection . . . . . . . . . . . . . . . . . . . . . . . . 5-6
5.4.2 Example of Defining Parameters for ICN Module Block . . . . . . . . . . . . . . 5-7
5.4.3 Input/Output Module Block Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
5.4.4 Remote Input/Output Module Block Selection . . . . . . . . . . . . . . . . . . . . . 5-9
5.5 LOOP AND FUNCTION BLOCKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
5.5.1 Loop Block Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
5.5.2 Tables Block Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
5.5.3 Input Function Block Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
5.5.4 Algorithm Block Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
5.5.5 Sequencer Block Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
5.5.6 Advanced Block Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
5.6 SPECIAL BLOCKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
5.6.1 Compounding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
5.6.2 List Connected Compound . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
5.6.3 Direct Connected Compound . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
5.6.4 Description Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
5.7 CONNECT BLOCKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
5.8 CREATE AND CONNECT LIST BLOCKS . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
5.9 COMPILE DATA BASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
5.9.1 Using TIF Files in PC-30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
5.10 DOWNLOAD DATA BASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
5.11 INSTRUMENT STATUS DISPLAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22

APPENDIX A - DOS CONFIGURATION FILENAME EXTENSIONS

iii
Application Builder
CONTENTS

ILLUSTRATIONS
2-1 Interconnecting Cabling Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
3-1 Untitled - [Root] Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3-2 Select Active Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3-3 Display Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
3-4 Navigating Through Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
4-1 Toolbars, Root and Instrument Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
5-1 Instrument Level Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
5-2 Interface (IF) Block Edit Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
5-3 Example, ICN Communication (ICN), Block Edit Display, Page 1 . . . . . . . . . . 5-8

TABLES
4-1 Printer Drivers and Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
5-1 Special Connections for Modules and Lists . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
5-2 Status Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22

iv
 Application Builder
INTRODUCTION

SECTION 1
INTRODUCTION

1.1 PURPOSE OF DOCUMENT

This document describes how to use the Application Builder Software to set up
the data base of MODCELL and MOD 30ML instruments. The Application
Builder operates as an independent configuration tool or as an integral part of a
complete PC based system, such as PC-30, by sharing configuration data.
Detailed information on the instrument data base exists in related documents
(see Section 1.5). How to set up the Application Builder Software for the
user’s personal computer and a description of the user interface is included in
this document.

1.2 ORGANIZATION OF DOCUMENT

The information in this document is organized as follows:

SECTION 1 – INTRODUCTION provides a general description of the software,

and equipment requirements. A list of appropriate reference books is provided.

SECTION 2 – INSTALLATION gives set up and loading information for the

Application Builder and describes how to connect instruments to your computer.

SECTION 3 – USER BASICS tells you how to gain access to the Application
Builder and how to work with the tools offered for your use.

SECTION 4 – TOOLBAR REFERENCE presents the purpose, characteristics

and use of each user tool and includes instructions for using the downloader,
export utilities, compiler, and other extended user activities.

SECTION 5 – CONFIGURATION includes instructions for using the Application

Builder to configure an instrument and describes supporting application blocks.
Suggested techniques for building a data base are offered. Also, use of
compounding is described as it supports building specific application sets.

APPENDIX A – FILENAME EXTENSIONS lists the filename extensions used by

this software package and those assigned when files are written to disk.

1-1
Application Builder
INTRODUCTION

1.3 OVERVIEW OF PRODUCT

The Application Builder is for use with a suitably equipped personal computer
system. Connection of the instruments and a printer completes the system for
support of download and document activities. The interface file of a compiled
data base may then be used with the workstation software for supervisory
control and data acquisition (TIF files support PC-30, MIF files can support other
software packages).

1.3.1 Application Builder Software

The Application Builder software is a graphics based configuration package.
Users are presented with a work area and icons that represent various activities
that can be performed. This interface offers the greatest amount of flexibility in
defining structures for the instruments’ configuration. The software is delivered
on two DOS compatible 3.5-inch disks. The Application Builder includes the
following features:
• Icon based user tools
• Copy, paste and cut (delete) activities
• Libraries of instruments and instrument functions
• Save and load strategy and compound files to disk
• Compounding used to combine function blocks into tasks and applications
• Graphic based connections between functions
• Loop execution order configuration control
• Password protection of strategy, compounds, and instruments
• View controls (grid, gravity, tag, database size, zoom, etc.)
• Export utilities for database reports, AutoCAD (DXF), and graphic printer
• Fill-in-the-blank type configuration fields with defaults and error checking
• On-line instrument status analysis
• Strategy compile and download
• Context-sensitive help screens
• All configured instrument parameters, including tags, ranges and alarm
limits, available to the PC-30 Strategy Builder or other software packages

1-2
 Application Builder
INTRODUCTION

1.3.2 System Requirements

The computer used to run the Application Builder requires an 80286 or greater
processor (80386 or greater is recommended for speed) with IBM PC AT
compatibility. The computer must be equipped with the following components
to run the software.
• A Hard Disk Drive with at least 10 megabytes available hard disk space.
• A 3.5-inch Flexible Disk Drive (high density 1.44 MB)
• 4 megabytes of RAM. All RAM above the first megabyte must be
configured as extended memory.
• Two Serial Communication Ports (COM1, COM2, COM3, or COM4)
• A Color Display (VGA, SVGA)
• A keyboard and mouse (two or three button)
• DOS Version 3.3 or higher.
• A Math Coprocessor is recommended but not required.
A printer (Section 4.14.4) is required to perform utilities such as making a hard
copy record of the data base.

1.3.3 Communication Requirements

The Application Builder requires a communication link for ICN communications
or a RS-232 or RS-485 interface for Extended Modbus communications to
import, download or check the status of a data base.

The Instrument Communications Network (ICN) interface between the computer

and the instruments can have as many as eight ICNs connected to the
computer via the 1720N Communication Link. One or two ICNs may be
connected using the 1731N Mini Link Board for AT Style PCs or the 1733N Mini
Link External. The 1720N Communication Link is connected to the computer
via an RS-232C serial port.

RS-232 is implemented when the distance between devices is 50 ft (15 m) or

less. RS-422 or RS-485 is used when the distance between devices is greater
than 50 ft (15 m) up to a maximum distance of 4000 ft (1200 m).

1-3
Application Builder
INTRODUCTION

1.4 EXPLANATION OF CATALOG NUMBER

This product is identified with a number that helps identify specific features.
The general format of this number is described below. Specific identification
information concerning various options may or may not be currently available.
Options and combinations are subject to change.

Sample Catalog No. 2006S Z 02 0 05 A

Base Number
Unused Character
Features
Unused Character
Software Version
Model (Design Level)

BASE NUMBER 2006S Application Builder

UNUSED CHARACTER Z Unused Character

FEATURES 02 MODCELL Multiloop Processor Configuration

03 MOD 30ML Configuration
04 MODCELL and MOD 30ML Configuration

UNUSED CHARACTER 0 Unused Character

SOFTWARE VERSION 01 Version 1.01

02 Version 2 (Sequencer introduction)
03 Version 3 (Remote I/O introduction)
04 Version 4 (MOD 30ML introduction)
05 Version 5 (Log. 6, Adv. 3, ML 2 Release)

MODEL A Model A

Sample Number 2006SZ02005A

1-4
 Application Builder
INTRODUCTION

1.5 RELATED DOCUMENTATION

See the documentation for your computer for specifics on its use. Reference
information for instrument data base structure and configuration parameters are
provided in the following publications.

For instrument installation instructions consult:

• IB-23C600 - Installation, MODCELL Multiloop Processor
• IB-1800R-INS - Installation, MOD 30ML Multiloop Controller
• IB-1800R-M30 - Installation, MOD 30ML Replacement for MOD 30

For instrument data base reference information consult:

• IB-23G600 - Data Base Reference for System, Logic I/O and
Communication Functions
• IB-23G601 - Data Base Reference for Advanced Control Functions
• IB-23G602 - Data Base Reference for Algorithms, Sequencers and Table
Functions
• IB-1800R-APP - Data Base Reference for MOD 30ML Functions

For the Workstation Software consult:

• The appropriate vendor User's Guide for Workstation Software
• IB-23H100 - User’s Guide for PC-30 Workstation Software

Reference information on installing ICN/Link communications between the

computer and the instruments for use with this software can be found in the
following documents.
• IB-23C001 ICN Communication Link Instruction Book for 1720N
• IB-23C003 ICN Mini Link Board Instruction Book for 1731N, 1732N
• IB-23C004 ICN Mini Link External Instruction Book for 1733N, 1732N

1-5
Application Builder
INTRODUCTION

1-6
 Application Builder
INSTALLATION

SECTION 2
INSTALLATION

2.1 SOFTWARE INSTALLATION

Install the Application Builder software on a computer already loaded with DOS
version 3.3 or later and with the copy protection key installed in the parallel
printer port. See Section 1.3.2 for system requirements. Make any cable
connections between the computer and associated equipment either before or
after installing the software (see Section 2.2).

The configuration software is provided on two high density 3.5-inch distribution

disks. The disks are used to install the software on the fixed disk and are not
used to run the software.
NOTE: It is recommended that a backup copy of the software distribution disks
be made prior to installing the software. Consult the instructions in your
DOS Reference Book for details on the Diskcopy command.

Copy the contents of the distribution disks onto the fixed disk as described
below. Included in the steps below is an example showing an installation from
drive A to the APPBLD directory on drive C. This is only intended as an
example, and you may specify the disk drives and directory name of your
choice.

1. Insert Disk No. 1 into disk drive A (your 3.5-inch drive may be B).

2. Make drive A (the one with the installation disk) the default drive.
Type: A: and press the Enter key.

3. Type INSTALL and press the Enter key.

A drive selection window appears to permit selection of the drive to
which the program is to be installed. The default destination drive is C.

4. Use the spacebar to select a different destination drive, if you wish, then
press Enter.
A directory selection window appears showing the default directory
name \APPBLD.

2-1
Application Builder
INSTALLATION

5. Type a new directory name, if you wish, and press Enter.

Installation begins and the display indicates progress as files are copied.
When Disk No. 1 is finished the following prompt appears:
Insert disk 2 and press a key or press Esc to quit.
6. Remove Disk No. 1 from its drive and insert Disk No. 2, then press any
key.
The installation of the remaining files in the Application Builder program
begins and the display indicates progress as files are copied from Disk
No. 2. When the process is complete, you are asked to install each of
the three supplementary files. The supplementary files are:
• Windows Icon
• Sample Compounds
• Printer Utility
7. Type Y (yes) in response to the prompt for each file you wish to install or N
(No) for any file you do not need.
8. Press Esc to exit the message window indicating that installation of the
Application Builder program is complete.
Read the message window for important notices. This inforrmation is
also copied as a readme.txt file to your install directory.
9. Remove Disk No. 2.
10. Edit your AUTOEXEC.BAT file to include the destination path name
specified in Steps 4 and 5. See the DOS manual for more information on
the PATH command.
• If the PATH command is not already specified in your AUTOEXEC.BAT
file, include the line:
Example: PATH C:\APPBLD;
• If the PATH variable is already specified in your AUTOEXEC.BAT file,
then include the directory path name among those path names already
listed:
Example: PATH C:\;C:\BIN;C:\APPBLD;
11. Reboot the computer by pressing and holding the Ctrl, Alt, and Del keys
simultaneously, and then releasing all three keys. The changes made to
the AUTOEXEC.BAT file will not take effect until the computer is rebooted.
NOTE: The Application Builder uses the environment variable LIBPATH to
search for DLLs (not the DOS PATH). Do not use LIBPATH as
an environment variable. The Application Builder will fail to load.

2-2
 Application Builder
INSTALLATION

2.2 CABLE CONNECTIONS

Cable requirements for terminal peripherals are shown in Figure 2-1. Make
cable connections as described below.
1. Connect the protection key that came with the software to the parallel
connector.
NOTE: The copy protection key provides protection from duplication. If a key
is not found when the system is starting you are allowed to place a key
on the computer and try again or to start up in evaluation mode. If you
start up in the evaluation mode, you cannot save or download a
database. There is no restriction in the full system.
2. If a printer is required, connect one end of the printer connection cable to
the protection key and the other end to the printer.
3. Connect the color display and mouse to the appropriate computer ports.
4. If ICN communication is being used, connect the communication link to the
computer, as shown in Figure 2-1 for external type links, using one of the
following methods:
a. If the distance between the communication link and the computer is 50
ft (15 m) or less, use the 1753F or 1774F cable (depends on computer
type). Connect one end of the cable to the computer and the other to
the communication link.
b. If the distance between the communication link and the computer is
greater than 50 ft (15 m) and up to 4000 ft (1200 m), use an RS-422
interface. See the communication link documentation for details.
5. If Extended Modbus communication is being used, connect the computer
directly to the instrument using one of the following methods:
a. For point to point communication with a maximum cable length of 50
feet, an RS-232 interface can be used. The computer functions as the
Modbus master and a 2033N RS-232 Communication Module in the
instrument functions as the slave. See Modbus Network Connections in
the instrument installation book for details.
b. For point to point or point to multipoint networks with cable lengths as
long as 4000 feet, an RS-485 interface is required. The computer
functions as the Modbus master and a 2034N RS-485 Communication
Module in the instrument functions as the slave. See Modbus Network
Connections in the instrument installation book for details.

2-3
Application Builder
INSTALLATION

Cable Cable Connections ICN No. 1

Catalog Cable Type
No. From To
Communication
1753F RS-232 (25-pin) IBM PS/2 1720N, 1733N Link
ICN No. n
1774F RS-232 (9-pin) IBM PC AT 1720N, 1733N
1768F RS-422 (9-pin) IBM PC AT 1720N, 1733N

ICN
Communication

Parallel
Software Printer
Protection
Key Color
Display

Mouse

Extended
Modbus
Personal Computer Communication
(80286 or better)

Figure 2-1. Interconnecting Cabling Diagram

2-4
 Application Builder
USER BASICS

SECTION 3
USER BASICS

3.1 GENERAL
After the Application Builder software is installed, you can start the software.
Before beginning, you may find it helpful to know how some basic tasks are
implemented so you can work in the graphical environment of the Application
Builder. These tasks are essential to building and entering instrument
configuration data and building application compounds. The tools you will use
are described in Section 4. Instructions for using the instrument configuration
icons and for building the data base are provided in Section 5.

3.2 STARTING APPLICATION BUILDER

To start the Application Builder,

1. Access the DOS prompt for the drive and directory where the Application
Builder resides (if you put this directory in your path statement, you could
start this software from anywhere). If the Application Builder resides in the
APPBLD directory, a typical DOS prompt might be:

C:\APPBLD>

2. To start the Application Builder, enter the following at the DOS prompt:

strategy <CR>

You will enter the Application Builder unless a software protection key,
Figure 2-1, is not installed. If no key is installed, you can enter the
Application Builder in the evaluation mode. Naturally, you have the
option of creating a batch file that calls the strategy executable. For
example, if you want to start the software using the command
STARTAB, create a batch file called startab.bat and use the command
STRATEGY as the only line in the file.

3-1
Application Builder
USER BASICS

3.3 DISPLAY CHARACTERISTICS

You first enter the Application Builder with the display shown in Figure 3-1. The
symbols along the toolbar are icons that perform specific functions when
selected (see Toolbar Reference). The configuration icons are system library
resources you use to build your database (see Configuration) by placing them
in your workspace and editing and connecting them to create a process
strategy. Icons are selected using the mouse as a point and click device.
Move the mouse to move the cursor over an icon (points to icon). Press the
left mouse button once (click on icon) to select the icon (image changes color),
drag onto workspace (dotted line) and drop into place.
Library ‘configuration File Name Level Toolbar
resource’ icons

Workspace

Tag Name Display Mouse Cursor Status Bar Activity Display Status Display

Figure 3-1. Untitled - [Root] Display

3-2
 Application Builder
USER BASICS

3.4 USING YOUR KEYBOARD AND MOUSE

Your keyboard and two or three button mouse are required to use this software.
The mouse controls the cursor which indicates the current position on the
display where you can select an icon, make an entry or invoke some activity.
The keyboard is used to enter alphanumeric information and data.

3.4.1 Mouse Activities

Select Mode
The select mode is active when the cursor icon in the toolbar is highlighted,
Figure 3-2. In this mode, the mouse cursor is used to select, move and place
configuration icons on a display. An icon or object is selected with the left
mouse button, and if it is a configuration resource object, dragged onto the
workspace where it can be placed with another click of the left mouse button.
You return to the select mode by clicking the right mouse button or selecting
the icon after placing an object. To move an object after it is placed in the
workspace, select it with the left mouse button, pause and then click and hold
the left button while dragging. Place it by letting go of the button.

Highlighted Toolbar Cursor = Select Active

Select Activity (selected name appears here)

Figure 3-2. Select Active Indication

Selecting Multiple Objects

A single object is selected with the left mouse button. Multiple objects are
selected by clicking each object with the right mouse button. Multiple objects
can also be selected by dragging a box around them using the left mouse
button. If the ctrl key is held down while selecting blocks (or compounds) by
one of the above methods, all connections to and from the objects will also be
selected.

3-3
Application Builder
USER BASICS

Using Two or Three Button Mouse

The difference between the two and three button mouse appears when
adjusting the grid or zoom area. With the two button mouse, press the shift key
and the left mouse button to simulate the middle mouse button of the three
button mouse.

Select Fields
When a field is selected, it is indicated as a highlighted entry field in a menu. A
character cursor appears as a line underneath the selected character in an
entry field. If you are editing a character in a field that requires keyboard entry,
use your mouse to select the specific character or use the left ( ) or right ( )
arrow keys to move to the specific character.

Some fields have a predefined set of valid entries that can be scrolled and
examined, one entry at a time, using the left mouse button to scroll forward or
the right mouse button to scroll back.

3.4.2 Keyboard Keys

Editing
Use the alphanumeric keys to make entries for fields that do not have a
predefined set of valid entries. The alphanumeric keys may be operated in
either the normal or insert mode. In the Normal entry mode, existing characters
are replaced (written over) as new characters are entered. The normal mode is
active unless the user selects the insert mode by pressing the Insert key. In
the Insert mode, existing characters are shifted to the right and new characters
are inserted in front of them as new text is entered. The insert mode is only
active while in the field being edited. The Delete and Backspace keys delete
single characters.

Keyboard Shortcuts
Your Enter and Esc keys perform the same as the display buttons when they
appear. The Tab key can be used to move through edit fields; however, an
unchecked box field causes the Tab key to return to the Enter button after
pressing Tab again. Page Up scrolls up in a scroll field and Page Down
scrolls down through a list. You can move the character cursor in a field with
the left ( ) or right ( ) arrow keys. An unchecked box can be marked using
the space bar. The Home and End keys can be used to move to the
beginning or end of long fields.

3-4
 Application Builder
USER BASICS

3.4.3 Accepting Entries

Entries in configurable fields are checked when moving the cursor to the next
field. A keyboard entry is considered invalid if the entry reverts back to its
original value, or when you get an error message. When all fields are properly
edited, select the enter button or press the Enter key.
NOTE: Not all conditions can be checked in the edit displays. Certain
information is checked during compile time.

3.5 MESSAGE POSTING

Errors, comments, and informational messages are common to all displays and
can be posted to the screen (message can be a maximum of 120 characters).
Help messages are context sensitive.

Information Messages
Information messages describe a condition that should have
been met. For example, you need to select an item before
selecting copy in order to make a copy.

Error Messages
Error messages advise you of a problem or a condition that
cannot be met. You need to change the error condition, i.e.
enter a proper tag name when trying to find a tag, to fix the
problem.

Exclamation Messages
Exclamation messages let you know when a successful task has
completed, such as when a good compile finishes. It may also
stress some important condition, such as when a tag name
exists.

Query Messages
Query messages ask you if you want to take some alternate
action when your current action is going to change some critical
work such as when loading a new strategy over an existing one
or when exiting the system.

3-5
Application Builder
USER BASICS

3.6 FUNCTION BLOCK EDIT DISPLAYS

Each edit display has designated areas called entry fields, where data can be
entered or where data are presented for examination, editing, or selection. The
edit displays are interactive and support various activities through a fill-in-the-
blank format, Figure 3-3. Entry fields on the displays are used to enter data to
be downloaded into the instrument data base.

Keyboard Entry Equivalent Keyboard Block << (Previous Page)

Character Cursor Field (Active) Keys also work. Specific Help >> (Next Page)

Scroll Fields.
Use the LEFT
mouse button or the
Page Down key to
move down through
a list. Use the
RIGHT mouse
button or the Page
UP key to move up
through a list.

Local Input Selec-

tion Box (X in box
means local data is
desired, otherwise it
is none.)

Figure 3-3. Display Fields

When a display requires more fields than can fit on the display screen at one
time, the display is divided into multiple pages. The darkened arrows indicate
that the display has more previous (<<) or following (>>) pages. Moving
from page to page in a multiple page display is accomplished by clicking on the
appropriate arrows. Scroll fields allows you to step through a list of valid
entries. Use the description field to enter information concerning the function of
the block (up to 41 characters displayed). This description is not part of the
data base downloaded to the instrument. Also, it does appear on database
report printouts.

3-6
 Application Builder
USER BASICS

3.7 SUGGESTED NAMING CONVENTIONS

As you create blocks, compounds, loops, and instruments in the Application
Builder, give them meaningful tag names (default names such as #001 are not
very meaningful and make confusing paths such as #001.#002 etc.). You may
want to use a naming convention such as using the block name and slot
number (e.g., DIM1 for a digital input module in slot 1) or using normal process
control loop names for loop compounds (e.g., FIC-101). You should not use
any characters in your tag names that you cannot use in a DOS file name. See
Section 4.4, Save Database, for a list of characters to avoid.

Although in the Application Builder tag names are case sensitive (i.e., DIM1 is
not the same as dim1), keep in mind that some tag names will be saved as
DOS file names during certain operations. DOS is not case sensitive, so
names that differ only in case are considered to be the same. In general, be
careful not to duplicate instrument, loop, or compound names (Note: the limit
of 8 characters is not checked when pasting with a wildcard). Some operations
that create DOS files are listed below. Refer to Appendix A for a complete list-
ing of filenames and extensions assigned by the Application Builder.
• Saving compounds and loops (uses the compound or loop tag name as the
DOS file name)
• Compiling (uses the instrument tag name)
• Exporting to DXF (may use the strategy name, instrument tag name(s), or
loop and compound tag name(s) depending on which export options you
select).

You may want to use the Find Tag menu (Section 4.12) to navigate through
your strategy to check your file names. Also, the .CRF file created when you
compile (Sections 4.6.1 & 5.9) lists all of the tag names used in your strategy.

3.8 NAVIGATING THROUGH STRATEGY

The Application Builder graphics based representation of your data base is
divided into multiple levels. Your strategy contains a system level and can
contain instrument levels, loop levels, and compound sublevels. The system
(root) level is the top level of your strategy where you place instrument blocks.
Inside each instrument you configure is the instrument level where you create
blocks, loops, and compounds.

To move down into the instrument level from the system level double click with
the left mouse button on an instrument block. From the instrument level, you

3-7
Application Builder
USER BASICS

can move down into any configured loops or other compounds by double
clicking on the appropriate compound. See Figure 3-4 for an example of
moving through different levels.

From any level except the system level (which is the top level), you can move
up one level by clicking on the diamond shaped icon in the upper left corner of
the screen. An effective way to navigate through your strategy is using the
Find Tag feature (Section 4.12) to locate the tag in any level and then zoom to
the designated block. Find Tag is especially useful in a complex strategy where
you need to move up and down multiple levels at a time. With Find Tag, you
do not need to wait for the screen to redraw at each level between your current
location and your destination.

SYSTEM LEVEL
aaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaa
aaaaaaaa
aaaaaaaaaaaaaaaa
aaaaaaaa
aaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaa

Instrument

**
INSTRUMENT LEVEL
aaaaaaaaaaaa
aaaaaaaa
aaaa
aaaaaaaaaaaaa
aaaaaaaaaaaaa
aaaaa

aaaaaaaaa
aaaaaaaaa
aaaaaaaaa
aaaaaaaaa
aaaaaaaa
aaaaa
aaaaaaaaa

aaaaaaaa
aaaaaaaaa
aaaaaaaaa
aaaaaaaaa
aaaaaaaa
aaaaa
aaaaaaaaa

Direct- List-
Connected Connected IF Block SE Block Loop
a
a
a
a
a
a
a
aa
a
aa

aa
aa
aa
aa
aaaa

aa
aa
aaaa
aaaa

“State”
a
a
a
a
a
a
a
aa
a
aa
aa

aa
aa
aa
aa
a
a

aa
aa
a
a
a

“CPD” Compound
a
a
a
a
a
a
a
aa
a
aa

aa
aa
aa
aa
a
a

aa
aa
a
a
a
a
a
a
a
a
a
a
aa
a
aa
aa

a
a
a
a
a
a

a
a
a
a
a

Compound Compound
a
a
a
a
a
a
a
aa
a
aa
a
a
a
a
a
a
a
a
a
a
a

** ** **
INSTRUMENT SUBLEVEL LOOP LEVEL
aa
a
a
a
a
a
a
a
a
aaaaaa a
aaaaaaa
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a

Compound LP Block
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
aaa
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a

* * = Double mouse click

**
LOOP SUBLEVEL
S-3035-3

Figure 3-4. Navigating Through Strategy

3-8
 Application Builder
USER BASICS

3.9 COMPOUNDING
Compounding is a convenient way of organizing groups of blocks and other
compounds into logical groups. You may make application groups or states
according to process functions or areas or organize individual blocks within a
compound to become a logical structure or a custom algorithm that can be
saved and used to construct other databases.

3.9.1 Grouping and Levels

Compounding can be further logically structured through the use of multiple
layering. The same rules apply to the lower level compounds as apply to the
upper levels. Generally, the instrument level compound is a good place for
logically grouped blocks and functions. The loop level is the place to integrate
sequence, logic and continuous control. A maximum of 10 levels are allowed
(system is level 1 and instrument is level 2).

3.9.2 Types
The types of compounds are:
2 List Connected Compound (STATE). The list connected
LC-CPD1 compound is placed using the special STATE resource at the
STATE
instrument or loop levels and then built (Section 5.6.2) or a
group of objects is selected and then made into a compound
(Section 4.23). Tag Lists are used to connect into and out of
this compound.

1 Loop Compound (LP CPD). The loop compound is a state

LP1 type compound that contains the loop algorithm set allowing
MR2LP control functions to be built. This compound can only have
one loop block and functions within the block become part of
that loops scan group. It is created from your instrument level
system resources (Section 5.5) and is built by placing the
compound and then entering and connecting other functions.

3 Direct Connected Compound (CPD). The direct connected

a
a
a
a
a
a
a
a
a
a
a
aaaaaaaa
aaaaaaaaa a
a
a
a
a
a
a
a
a
a
a
a
a

DC-CPD1 compound offers the ability to define a connection interface.

a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a

CPD This compound is placed, the desired blocks added and

a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
aaa
a
a
a
a
a
a
a
a
a
a

connections defined and named (Section 5.6.3). The

a
a
a
a
a
a
a
a
a
a
a
a

compound is then connected like other blocks with input and

output attribute lists instead of tag lists.

3-9
Application Builder
USER BASICS

3.9.3 Execution Order

Compounds are assigned an execution order number (number at upper right
position) when they are placed (see Section 4.14.2 for execution order
preferences). Like blocks, this order can be changed as a result of connections
or using the check database execution order icon (Section 4.21). As a general
rule, you should place compounds in the order you want them executed. If this
is not practical, save your compounds and then load them in order. To make
sure that loops are executed consecutively, they must be assigned the same
scan group number (see Section 5.5).

3.9.4 Saving and Loading Rules

When a compound is saved, the name of its algorithm set is saved with it.
When the compound is loaded, the name of the current algorithm set is
compared to the algorithm set being loaded to determine what action to take.
Naturally, if the names match the load is allowed. If there is an obvious
mismatch (i.e. instrument level algorithm set being loaded into a loop level), the
load is not allowed. Otherwise, the compound to be loaded is searched for any
blocks that are not allowed in the current algorithm set. If any are found, the
load is not allowed, otherwise, the load is allowed. If necessary, lower block
versions are upgraded to match the higher version algorithm set.

Examples:
• Loading a Regulatory Controller 1.0 with a PID block into a Logic Controller
2.0 would be rejected because of the PID block.
• Loading a Logic Controller 2.0 with a version 2 TI block into a Logic
Controller 1.0 would be rejected because of the Logic Controller 1.0
supports version 1 of the block only.
• Loading a Logic Controller 3.0 with version 1 blocks only into a Logic
Controller 1.0 would be allowed.
• Loading a Logic Controller 1.0 with version 1 blocks into a Logic Controller
3.0 would be allowed and any TI, TIM, VCIM, LN, and EX blocks would
have their versions upgraded to 2.

3-10
 Application Builder
USER BASICS

3.10 MAKING CONNECTIONS

Connections are made between an appropriate source and destination attribute
pair while in the Connect Mode. Connections can be visible or wireless as
described in Section 4.24 and Section 4.25. The process of selecting
connection points depends upon the type of connection you are using and
where you are in your strategy in relationship to the points being connected.
Connections are made between readable (source) and writable (destination)
attributes (see Section 5.7 for a description of special connections and rules
for all block inputs). The examples below illustrate some typical connection
processes.

Making a Visible Connection Between Two Blocks at the Same Level

This example assumes you can see both blocks.
1. Select Visible Connect icon.
2. Select source block.
3. Select attribute from source block.
4. Select destination block.
5. Select attribute from destination
block.

Attribute list displays up to 32 attributes.

Use PREV and NEXT to move through menu.

Making a Visible Connection Between Two Blocks at Different Levels

This example assumes you can see one block and the other block is within a
compound you can also see.
1. Select Visible Connect icon.
2. Select source block.
3. Select attribute from source block.
4. Select destination compound.
5. Select destination block (or compound) from Tag List.
If there is no valid destination connection in selected destination, the
connect process will have to be restarted at step 2.
6. Select attribute from destination block.

3-11
Application Builder
USER BASICS

Making a Wireless Connection Between Two Blocks at the Same Level

This example assumes both blocks are at your current level.
1. Select Wireless Connect icon.
2. Select source block from Tag List.
3. Select attribute from source block.
4. Select destination block from Tag List.
5. Select attribute from destination block.

Tag list displays blocks and compounds.

Double click compound to move into it.

Making a Wireless Connection Between Two Blocks at Different Levels

This example assumes you can see one block and the other block is within a
compound.
1. Select Wireless Connect icon.
2. Select source block from Tag List.
3. Select attribute from source block.
4. Select destination compound from Tag List.
5. Select destination block (or next compound) from Tag List.
If there is no valid destination connection in selected destination, the
connect process will have to be restarted at step 2.
6. Select attribute from destination block.

Note: As a general rule you should always try to minimize your connection
path. Making a connection between two blocks within a compound
while outside the compound can be done; however, three connection
arrows are used instead of one. The best connection is the most direct
one.

3-12
 Application Builder
USER BASICS

3.11 INPUT CONVENTIONS

Several conventions are used throughout the edit block displays. Typically:
• "Gray" data is viewable only.
• Data with a checkbox next to it is dynamic.
To enter data, click on the checkbox. This will enable the associated data
field(s) for user entry. To disable, click on the checkbox again.
• Other data may be dynamic, that is, enabled by entries from other fields.
• Data entry fields are either "Keyed" (data is entered through the keyboard),
or "Scrolled" (data is selected by scrolling through a list with the mouse).

Most blocks allow one or more inputs. An input can be:

• A remote input. This is a connection arrow from some other block.
• A local input. This is data entered directly in the block menu.
• NONE (no input). No remote input and no local input.

Most inputs can be remote, local, or NONE:

• Specify a remote input by making a connection to the appropriate block
attribute.
• Specify a local input by enabling the checkbox in the block menu and
entering local data.
• Specify NONE by making no connection and disabling the checkbox in the
block menu.

Some inputs can be remote only:

• Specify a remote input by making a connection to the appropriate block
attribute.
• There's no checkbox or local data field in the block menu.

Some inputs can be remote or local, but not NONE:

• Specify a remote input by making a connection to the appropriate block
attribute.
• Specify a local input by entering local data in the block menu.
• There's no checkbox to disable for indicating NONE.

3-13
Application Builder
USER BASICS

Block input precedence rules:

1. An input is considered remote if a connection is made, even if local data has
been specified.
2. An input is considered local if no connection is made and local data has been
specified.
3. An input is considered NONE if no connection is made and no local data has
been specified.

3-14
 Application Builder
TOOLBAR REFERENCE

SECTION 4
TOOLBAR REFERENCE

4.1 GENERAL
The icons along the toolbar, Figure 4-1, serve as your working tools throughout
the Application Builder. As you progress into your configuration, additional
icons appear on the toolbar from those presented at the root (first) level. This
section describes each of these tools starting with the tools at the root level
(from left to right) and picking up the additional icons at the lower levels.
Certain tools have extended utilities associated with them and are also
described in detail in this section.

Exit

Load Redraw Serial Port Erase Paste Find Tag Save

Preferences Library Help
Setup
Inst. Move (to Copy (to Report
Query About
Funct. Zoom Select
clipboard) clipboard) Options Software

File Path of Current Level

Saved File
Click
here to
move up
a level

Check Execution I/O Graphic Instrument Visible Wireless

Compound
Order Placement Functions Connection Connection

Figure 4-1. Toolbars, Root and Instrument Levels

4-1
Application Builder
TOOLBAR REFERENCE

4.2 EXIT SYSTEM

Select the Exit System icon to close the Application Builder and return to your
operating system. Before exiting the system, the Application Builder checks to
see if the strategy has changed. If it has, you are asked if you wish to save it.
If you say yes, you can save the database as described in Section 4.4.
Otherwise, you can elect to exit the system or remain using the response
screen as shown below.

YES closes the Application Builder

without saving and returns you to
your operating system prompt.

NO cancels the exit.

4.3 LOAD DATABASE

Select the Load Database icon to load previously saved strategies into the
current workspace. You may select one of the files listed (only files with the
extension .CDB are listed) or you may enter a valid configuration file name in
the File Name box. If a file was saved with its own extension (i.e. .SAV for
backup purposes), the optional extension must also be specified. If an existing
strategy is already loaded, you will be asked if you want to save it. Select NO
to load the new strategy. Select YES to get the Save Database menu.
Canceling the save loads the new strategy. If a file is not valid, the strategy
load will fail. If a file is not present in the selected path, you are notified that
the file does not exist. If the strategy is password protected, you must enter a
correct password to load the file.

4-2
 Application Builder
TOOLBAR REFERENCE

Currently selected filename or enter a valid

filename with optional extension.

File Path shows two lines, 22 characters

per line.

Select a strategy once to put in file name

box or double click to start load.

To move up a level from the current

directory, double click here.

To move down a level into a subdirectory,

double click an appropriate directory.

Double click on bracketed letters to

change logical drives.

Use scroll arrows to move through the

displayed list.

4.4 SAVE DATABASE

Select the Save Database icon to write the strategy currently on your
workspace to disk. The Save Database menu is similar to the Load menu.
Use the menu to enter or select a file name you want to give the strategy.
Only the first eight characters are used for the filename (see note). The
extension .CDB is assumed if no extension is entered (the first three characters
after the period are considered the extension, see Appendix A to prevent
conflicts). After you have named the file, select OK. The file is saved unless
you get an error message. If a file of the same name exists, you are given the
choice of overwriting it or not.

NOTES: Set up subdirectories in DOS. The save utility does not create them.
DO NOT USE a space or characters such as [ ] + = , : ; ” < > / ?
| \ or * in any filename. Characters such as ! @ # $ % & ( ) _ - { } ’
` ~ can be used but should be avoided.
Save your database often during development of a strategy.

4-3
Application Builder
TOOLBAR REFERENCE

4.5 SERIAL PORT SETUP

Select the Serial Port Setup icon to establish the type of communication used
between your personal computer and the instruments. The setup display
allows for independent configuration of four communication ports.

1. Select the the

communication port
your wish to use.

Communication
parameters are saved
in the file SIO.DAT,
which is created if it
does not exist. At this
time, the software
attempts to determine
the base address of
each communication
port.

In most cases the address (Hex number) can be left unchanged. A zero
will appear if the software cannot determine the address. Enter the
correct address if a zero appears or if your computer uses a different
address than that determined through the software check of your
computer’s BIOS.
2. Select the baud rate, data bits, parity, and stop bits that match the device
with which you are communicating.

Comm Data Stop

Link Baud Parity
Type Bits Bits
19200, 9600, 4800, 2400,
1720N 8 1, 2 None, Even, Odd
1200
ICN 1731N 19200, 9600 8 1 None
19200, 9600, 4800, 2400,
1733N 8 1 None
1200, 600, 300
38400,19200, 9600, 4800,
Modbus None 8 1,2 None, Even, Odd
2400, 1200, 600, 300,150

4-4
 Application Builder
TOOLBAR REFERENCE

4.6 INSTRUMENT FUNCTIONS

Select the Instrument Functions (ABB) icon to access instrument functions
shown below. The LCP Utility appears at the instrument level only. Use the
Cancel icon to exit from the submenu. The ABB icon appears only at the
system (root) and instrument levels, not at the loop level.

4.6.1 Compile Database

Select the Compile icon to create an instrument database file that can be
downloaded to an instrument. Each communications module (ICN or MSC) can
have two interface files (there can be up to three modules). The files selected
in the Compile Setup menu are produced only after the database compiles
without error. A Cross Reference File (CRF) and a compiler Error file (ERR)
are always built and saved as a part of this process. See Appendix A for a
description of files.

Check the appropriate

boxes to produce TIF,
MIF, MRF and WDF files
(TIF and MIF are pro-
duced for each commu-
nication module). A TIF
file is needed to build a
PC-30 strategy.

Check this box to make

variable names compati-
ble with PC-30 strategies
that were created using
TIF’s produced by 1706S
Configuration Software.
When this box is not
checked, variables are
given their full path name.

4-5
Application Builder
TOOLBAR REFERENCE

Produce TIF's - Each line represents a communications module. Mark the

checkbox to build the associated TIF. If a line is blank, it means that no
communications module was found, and no TIF will be built, even if the
checkbox is marked.
Block Name - This is the block type and occurrence number of the module.
This is a read-only field.
Tag Name - This is the tag name of the module. This is a read-only field.
File Name - This is the name to be given to the interface file. You may enter
any valid file name. The file will have extension ".TIF".
Use block & occurrence for names - Variables are normally given their full
path name (e.g. MCELL.LOOPA.TIMER.TIME) or an alias. Check this box to
name each variable in the TIF by block type and occurrence number (e.g.
TM6.TIME). This checkbox applies to all TIF's. This is done to remain
compatible with PC-30 Strategies that were created using TIF's produced by
our 1706S Configuration Software, or if you simply prefer to name variables in
this way.
Produce MIF's - This is similar to the production of TIF's, except that each file
will have extension ".MIF". The production of MIF files is not supported when
configuring Logic versions 1 - 4, Regulatory versions 1 - 3, or Batch version 1.
Produce MRF - Check this box to create a Modbus Reference File, which
indicates, for each Serial Communication block, the database attributes that are
associated with each Modbus register.
Produce WDF - Check this box to create a Wiring Description File, which
contains, for each I/O module block, the tag name, block type and occurrence
number, block description, wiring description, and slot number(s).
Reassign occurrence numbers - Normally the compiler assigns occurrence
numbers to blocks when they are first created and doesn't change them in
subsequent compiles. Check this box to direct the compiler to reassign all block
occurrence numbers. CHANGING NUMBERS MAY INVALIDATE ANY
EXISTING PC-30 STRATEGIES OR LCP DISPLAYS. DO NOT REASSIGN
NUMBERS UNLESS YOU ARE SURE THAT IS WHAT IS DESIRED. The only
reason to reassign numbers is to save space in the database. For example, if
blocks EX1 and EX42 are the only Expression blocks in the database, tables will
be created for 42 Expression blocks, wasting database space. Reassigning
numbers will change these blocks to EX1 and EX2. However, PC-30 Strategies
and LCP displays may have to be rebuilt.

4-6
 Application Builder
TOOLBAR REFERENCE

4.6.2 Download Database (and Communication Setup)

Select the Download icon to send a complete database to an instrument.

Scroll to select either Communication Links or Extended Modbus.

For links, specify the ICN (0-7)

and instrument (0-15) numbers
of the target instrument.
For Modbus, specify the target
instrument address (1-247).
Scroll to select your computer
communication port.
The Log File is used to capture
communication messages to a
disk file (*.LOG). This file helps
determine the source of any
communication problems during
download and status activities.
Leave log file setup at NO (YES will slow any communication activities).

Informational Only, Download can only be to main database and state before
download is being configured.
The state after download is the state the instrument should go to, and the
startup type the instrument should use, after the database has been
downloaded. Choose from RUN or HOLD state, with a COLD or WARM start.
The DEFAULT state means run the default instrument database.
Applies to Status Page only (Section 4.6.5).
Select OK to download. Cancel will abort the download.

4.6.3 Upload Database

Select the Upload icon from the system level to get a database from an
instrument. Assign a valid filename and then setup communications as
described above. Upload will get all blocks and connections from the
instrument database and write the file to disk as filename.ID1. Loop
compounds will be restored. All other compounds and description blocks are
not restored. The data base version created is the same as for Import.

4-7
Application Builder
TOOLBAR REFERENCE

4.6.4 Import
Select the Import icon to read an instrument database file (ID1) and create an
instrument resource icon on your strategy workspace. This is typically used to
bring in files created using the 1706S configurator. Loop compounds will be
restored. All other compounds and description blocks are not restored. The
data base version created depends upon the declared version (if ok) then the
minimum calculated version. Import fails otherwise.

4.6.5 Status of Instrument Database

Select the Status icon to read or write the main, default, current or memory
module data base of a specified instrument through the Instrument Status
display (see Section 5.11 for the display). Use the communication setup
menu (the same as shown in Section 4.6.2) to define communication
parameters. No selection is required for the log file or state after download
fields. Select either the main, default, current or memory module data base for
reading.

Initiate reading and writing by typing a command (see Section 5.11 for the
commands) in the CMD field at the bottom of the display and press enter to
send the command. The response to the command sent to the instrument is
displayed at the bottom of the response area and is scrolled up through 15
lines by additional commands.

4.6.6 Reports
Select the Report icon to view the reports produced during the compile activity.
Select the specific report file to be viewed from the Read Report menu. Refer
to Appendix A for a description of the files.
Select OK to view the information for the
selected file. Note that the MRF and WDF
files exist only if produced as specified during
compile setup (Section 4.6.1).

4-8
 Application Builder
TOOLBAR REFERENCE

4.6.7 LCP Utility

Select the LCP Utility icon to upload a data base from a 2021W Local Control
Panel (LCP) that is at Version 4 or later or load it from a file and download to a
LCP or save it to a file. LCP versions prior to 4.0 do not have the upload/
download capability. The LCP uses the ICN for communication as indicated in
this menu.
Database Name: The name of
the currently loaded database.
This is the name of the database
on disk. If the database has not
yet been saved to disk, the name
will be UNTITLED.

Database Label, Size & Version:

The label, size and version as
determined from the database
header. These are read-only
fields. They are not configurable
using this utility.

ICN and Instrument Number: Enter the ICN (0-7) and instrument (0-15)
numbers of the target instrument. Only Link communications is supported.
The LCP does not support Extended Modbus communications.
Serial Port: Select the computer serial port used with the LCP.
Database to Upload: Select which database is to be uploaded, either the
MAIN database, or the BACKUP database (if present).
Log File: This is normally NO. Select YES to produce a log file of all
communication messages, which is used for debugging.
Load: Loads a database from disk.
Save: Saves the currently loaded database to disk (without verification).
Download: Downloads the currently loaded database to an LCP and makes it
the current file resident configuration. You can download the MAIN database
only. The BACKUP database cannot be downloaded. Specify the ICN and
Instrument numbers before attempting a download.
Upload: Uploads a database from an LCP. Specify the ICN and Instrument
numbers, and indicate which database to upload, before attempting an upload.
Help: Displays this help information.
Cancel: Exits the LCP Utility.

4-9
Application Builder
TOOLBAR REFERENCE

4.7 ERASE (Delete)

The Erase icon deletes selected blocks and/or connections, or your whole
strategy. Undo restores an erased block and/or connection. Use the Left
mouse button to select the erase icon and immediately delete all selected
blocks and connections. Use the right mouse button to perform other erase
operations. Use the Cancel icon to exit from the submenu.

Erase All Selected Blocks and Interconnections.

Select blocks, select erase icon with right button, use Block
icon to delete selected blocks and their interconnections. Undo
will restore blocks and the connections coming directly into or
out of the block. Connections to another compound are not
restored and partial connections can remain at the destination.

Erase Selected Connections.

Select connections (blocks not affected if selected), select
erase icon with right button, use Connect icon to delete
selected connections only. Undo will restore connections.

Erase All Selected Blocks and All Selected Connections.

Select blocks and connections, select erase icon with right
button, use All icon to delete selected blocks and connections.
Undo will restore blocks and connections. This operation is the
default operation provided when selecting the Erase icon with
the left mouse button.

Erase Entire Strategy.

Select erase icon with right button, then use Strategy icon to
request that the entire strategy be deleted. Answering YES
deletes your strategy. Undo will not restore your strategy.
Strategy data is reset to the root compound and the workspace
is ready to create a new database (the strategy name remains).

Restore Erased Blocks and Connections.

Undo restores the strategy to the state prior to the last delete
operation. The undo operation works until a block or connec-
tion is added to the database or you change compound levels.

4-10
 Application Builder
TOOLBAR REFERENCE

4.8 MOVE TO CLIPBOARD

Select the Move to Clipboard icon to delete a selected piece of your strategy
and place it into the clipboard (a memory buffer) where it can be recreated
using the paste icon. The previous contents of the clipboard are lost when you
move or copy to clipboard. You cannot copy or move and paste parts of your
strategy that belong to one algorithm set to places where another algorithm set
is being used (e.g., the IF block cannot be copied into a loop compound).

4.9 COPY TO CLIPBOARD

Select the Copy to Clipboard icon to place a selected piece of your strategy
into the clipboard (a memory buffer) where it can be recreated using the paste
icon. The previous contents of the clipboard are lost when you move or copy
to clipboard. You cannot copy parts of your strategy that belong to one
algorithm set to places where another algorithm set is being used (e.g., the IF
block cannot be copied into a loop compound).

4-11
Application Builder
TOOLBAR REFERENCE

4.10 PASTE
Select the Paste icon to paste a piece of your strategy that has been copied or
cut to the clipboard. The pasted piece is placed over and slightly offset from
its original location when in the same level. The Tag Wildcard menu lets you
determine how the pasted piece is to be named. Remember: The first 8
characters of tag names are used to determine file names. Do not duplicate!

Wildcard option not used

If you do not mark the wildcard option box, then a sequential number is
assigned to the original tag name each time it is pasted. For example, DIM1 is
pasted as DIM1#1 for the first paste and DIM1#2 for the second.

Wildcard option is used

The wild card naming feature is enabled by selecting the wildcard check box in
the menu and using a Tag Wildcard as follows (disabled without a wildcard).
• Use of * with text
Use a “*” wildcard to prefix or append text. To place TEXT before or after
the current tag in the system, specify *TEXT or TEXT*. For example, if the
tag wildcard is *TEXT, DIM1 is pasted as DIM1TEXT. This option has
precedence over use of the #.
• Use of # with Number
Use a “#” wildcard to replace the
first number in the original tag with
the number in the number field.
For example, if # is placed in the
tag wildcard field and the number
is 4, DIM3 would paste as DIM4
(unless there is an existing DIM4
in which case it would paste as
DIM4#1). If the original tag was
3DIM, then the pasted tag name
would be 4DIM.

4-12
 Application Builder
TOOLBAR REFERENCE

4.11 QUERY
Select the query icon to:
• Open a connection menu which displays the source and destination of a
control connection and optionally allows the connection to be deleted
• Open a menu associated with a block or compound for editing

Select a group of block(s)

and/or connection(s) to be
queried (hold down left
mouse button and drag a
box around blocks and
connections).

Use the left mouse button

to query blocks or the right
mouse button to query
either blocks or connections
(block and connection
choices display when right
button is used).

The first block or connection to be queried will be highlighted. You will be

prompted to use:
- the left mouse button to query the selection,
- the right mouse button to skip the selection and go to the next block or
connection, or
- press Esc (escape key) to quit the query.

Notes: A double click on a block will also query the block.

See the Configuration section for use of function block edit displays.
A compound must be queried using the Query icon. A double click
will open a compound.

4-13
Application Builder
TOOLBAR REFERENCE

4.11.1 Example of Block Query at System Level

Block Tag:
Use up to 8 charac-
ters that make a valid
DOS filename.
Description:
Use up to 30 charac-
ters.
Password:
Select field and enter
up to 8 characters.
Change Password:
If you change the
password, you must
enter the ‘old’ pass-
Type:
word for authorization.
Scroll to get Eurocard or Flush Mount
(determines slot layout on I/O graphic display).

4.11.2 Example of Connection Query

Control Connection:
Complete path name
of source and destina-
tion is shown.

Cut Connection:
Select Cut Connection
to erase (delete) the
connection identified
in the Control Connec-
tion Menu.

4-14
 Application Builder
TOOLBAR REFERENCE

4.12 FIND TAG

Select the find tag icon to bring up the find tag menu. From this menu you
can:
• Use the tag name field to type in a tag name and search through the
current level only for the tag. You cannot use wildcards and the name is
case sensitive.
• Use the tag name list, which contains sorted tag names for your current
level in the compound path, to navigate through your strategy. If an
instrument or compound is password protected, you will have to enter the
password to enter that level.

Select OK to process your data entry field and zoom to that block. The find
tag feature is your best way for navigating through a complex strategy with
different levels.

To find a tag name:

Use a single click in the list box
to select that tag and put it in the
data entry field. Select OK to
zoom to the block or compound
with that tag name. Alternately, if
the tag name is a block you can
double click to do the same.
To navigate through strategy:
Use a double click in the list box
to select a compound that takes
you down into its tag list or dou-
ble click on the backup button (..)
to move up a level. When you
are at the root compound, there
is no backup button.

4-15
Application Builder
TOOLBAR REFERENCE

4.13 REPORT OPTIONS

Select the Report Options icon to display the different report options icons.
The choices available are Database report, Export to DXF, and Screen dump to
printer (Graphic icon). Use the Cancel icon to exit from the submenu.

4.13.1 Database Reports

Select the Database Reports icon to get the report options menu. Select the
type of report you want (Database Blocks and/or Control Connection Lists). If
you choose both of these, the options previously disabled (By Block and By
Compound) will become available. These allow you to choose whether the
connections are printed on a per block basis or at the end of all the blocks on a
per compound basis. Also available are the options of sending the report to
the printer and/or a disk file. The file name defaults to the strategy name with
a ".RPT" extension in the current directory path. To set up your preferences,
select the preferences button.

NOTE: Any instrument, block or compound that is password protected will

report tag name and description only unless you are in the compound
and report from current compound and below.

4-16
 Application Builder
TOOLBAR REFERENCE

Select the preferences button in the report options menu to get the report
preferences menu. The preferences menu contains a file path button that
allows you to change the file name and the path name through a “Save As”
menu that is similar to the Save Database menu.

The blocks can be reported by:

• Block id – the order the blocks were put in the strategy (this is the default
when no sort is selected)
• Sorted alphabetically by tag name
• Sorted by execution order

You can select how much of the strategy you would like to report. The choices
are: from the strategy root and below, the current compound and below or the
current compound only. If you select the “Current Compound Only” choice,
you can also select which block type you would like to report. The default is all
block types. Because the lists of possible algorithm types can change at each
compound level, the block type list box is available only when the current
compound only choice is selected.

4-17
Application Builder
TOOLBAR REFERENCE

4.13.2 Export to DXF

Select the export to DXF icon to export a graphical representation of your
strategy to DXF files for use with AutoCAD. Each compound creates its own
DXF file. The preferences menu allows you to determine the following.

Attributes
Prompt for Compound File Names
Use this option to create a DXF file for all compounds using the
strategy name as the default file name (no box selected) or prompt for
compound names. If you prompt for compounds you will get a menu
where you can report the compound and assign a unique filename, skip
a particular compound and all levels below it, or cancel any further
AutoCAD reporting.
Print Connection Names
Select this box if you want to print the connection names on the
connections.
Start Reporting From...
You can report from the strategy root and below, the current compound
and below, or the current compound only.
File Path
As with the other reporting menus, you can change the file name and
path with the file path button.

The report name

file path displays
21 characters.
You can view
more using the
arrow keys, End
key or Home
key.

4-18
 Application Builder
TOOLBAR REFERENCE

4.13.3 Screen Dump to Printer

Select the Graphic icon to make a graphic printout of your screen to the printer
selected in the Preferences icon. The screen dump to printer dumps the
current contents of the database window to a printer. The system will work with
an Epson compatible 24 Pin Black and White printer when the EPSLQ24 driver
is selected. Additional drivers are provided using the printer options selections
under strategy preferences. See Section 4.14.4 for a description of the printer
options.

4-19
Application Builder
TOOLBAR REFERENCE

4.14 PREFERENCES
Select the Preferences icon to get the Strategy Preferences menu. Use this
menu to set the following preferences.
• View preferences (saved with Save Preferences)
• Execution Order preferences (saved with Save Preferences)
• Password (saved with the strategy)
• Printer preference (saved with Save Preferences)

4.14.1 View Preferences

Select the view preferences icon to set your view options. The choices are as
follows (X in box = enabled):
Grid: Use to set the display state of the grid.
Gravity: Use to make blocks and connections snap to the vertices of
the grid upon placement on the user screen.
Magnify Tag: Use to turn on or off the display of the tag name in the left
most field of the status bar. The tag name is displayed when
the mouse cursor goes over the block or compound.

Load with Preview:

Use to enable or
disable the preview
mode when loading
compounds.
Backup Database:
Create a backup
database when saving.
Right Angle Conn.:
Enable drawing at right
angles.
Save Preferences
Select this to save
your strategy
preferences to the
PREF.CFG file.

4-20
 Application Builder
TOOLBAR REFERENCE

4.14.2 Execution Order

Execution order determines the sequence of block execution. Use the strategy
preferences to determine execution order. In addition, the check execution
order icon (see Section 4.21) is also used to determine execution order. The
basic order scheme is based on the following criteria:
• Parent to Child Connection (Parent must execute before Child)
• Order of creation when no block connection exists
• User interaction when a control loop is detected

Select the strategy preferences icon in the tool bar and then select the Exec
Order button to set the execution order scheme for the strategy. The
execution order choices are (X in box = enabled):
On The Fly: This determines the execution order every time a new
connection is made. If the order of the source block is
greater than the order of the destination block then the blocks
are reordered.
Loop Detection: If a loop is detected between the source and destination
blocks, then you are prompted with the loop order window.
Display Order: Turns on or off the display of the execution order in the upper
right corner of the algorithm block.

4-21
Application Builder
TOOLBAR REFERENCE

4.14.3 Password
Select the password icon from the strategy preferences menu to get the
strategy password menu. Use this password to protect your strategy from
being loaded without special authorization. Your strategy password is in effect
after saving the strategy and when trying to load it.

This menu appears when trying to

load a strategy that is password
protected. If you enter an
incorrect password when loading
a protected strategy, the strategy
will not load and the current
workspace is cleared.

To change or delete a password:

1. Select the strategy preferences icon.
2. Select the password icon to get the strategy password menu.
3. Select password field.
4. Press space bar once to clear (delete) the password or change it as you
wish.
5. Select OK.
6. Save the strategy (Save Database).

4-22
 Application Builder
TOOLBAR REFERENCE

4.14.4 Printers
Select the Printers icon from the strategy preferences menu to get the printer
options menu. Scroll through the printer driver list using the up and down
arrows to display the printer driver you require (see Table 4-1 on next page for
a description of drivers) and select the appropriate driver. The selected driver
displays in the Driver field. To set up the configuration for the selected printer,
select the Configure Printer button.

Select driver from list.

See table on next
page for description of
drivers. Use the
mouse to select a
printer driver. Scroll
through the list using
the scroll bar or the
up and down
keyboard arrows.

Select the Configure

Printer button in the
Printer Options menu
to get the Printer
Configuration menu.
Examine the default
entries for the printer
you selected and
make changes as
required for your
application (-1 is a
printer default).

4-23
Application Builder
TOOLBAR REFERENCE

Table 4-1. Printer Drivers and Descriptions

Driver Description
CALCOMP CalComp ColorView 5913
CANBJ10 Canon Bubble Jet BJ10
CANBJC Canon Bubble Jet BJC Color
CANON Canon LBP-8 and 8III
DESKJET Hewlett Packard DeskJet
DICONX Kodak Diconix 150 Plus
EPS3500 Epson GQ-3500
EPSCLR24 Epson Compatible 24-Pin Color
EPSCLR8 Epson Compatible 8-Pin Color
EPSESCP2 Epson ESC/P2
Epson Compatible 24-Pin B/W Printers, Fujitsu DL2400,
EPSLQ24
Panasonic KX-P1524, Epson LQ Series (24-Pin B/W)
EPSLQ36 Epson LQ 36
Epson Compatible 8-Pin B/W Printers, Fujitsu DL2400,
EPSLQ8
Panasonic KX-P1524, Epson JX-80 B/W, Epson LQ Series (8-Pin B/W)
HP500C Hewlett Packard DeskJet 500C Color Inkjet
HP550C Hewlett Packard DeskJet 550C Color Inkjet
HPJET300 Hewlett Packard PaintJet 300C Color Inkjet
HPJETXL Hewlett Packard PaintJet XL
HPLASRJT Hewlett Packard LaserJet + and Series II and Compatible
HPLSRJT4 Hewlett Packard LaserJet 4
HPPNTJT Hewlett Packard PaintJet
KYFS850 Kyocera FS850
LASRMST LaserMaster LX6/K, LXPK, LXMK (DO NOT USE. UNSTABLE!)
MITS500 Mitsubishi G-500
OKI192 Okidata Microline 192 Plus and 193 Plus
PAN4450 Panasonic KX-P4450 Laser Printer
PAN8543 Panasonic
PAN8543I Panasonic
PAN8543M Panasonic
POSTSCPT PostScript Color 2.0+ (parallel)
PSTSCPAR PostScript B/W 1.0+ (parallel)
PSTSCSER PostScript B/W 1.0+ (serial)
RICH6000 Ricoh PC Laser 6000
SEIK5504 Seiko CH-5504
SHP720 Sharp JX-720
SHP730 Sharp JX-730
TEK4693 Tektronix 4693D and 4693DX
TEK4696 Tektronix 4696
TEK4697 Tektronix ColorQuick 4697
TOSH1351 Toshiba P1351 and P351
XER4020 Xerox 4020

4-24
 Application Builder
TOOLBAR REFERENCE

4.15 ZOOM
Select the Zoom icon to display the choices for moving about in your strategy
workspace and for adjusting your grid size. Either mouse button opens the
zoom icons and puts you in the view mode as described below. Use the
cancel icon to exit from the view mode submenu.

Flexible Grid
Select the Flex Grid icon and move cursor to workspace. Use
left mouse button to place grid, adjust the grid (vertically and/or
horizontally) with the middle button (3-button mouse) or use the
shift key and the left button (2-button mouse), or use the right
mouse button to cancel operation. This enables the grid option
in the view preferences. Turn the grid off in view preferences.
Full Zoom
This icon defines an area of the overall strategy to view. Select
Full Zoom, then select the area to view (zoom into) with the left
mouse button, or size the zoom in area with the middle button (3-
button mouse) or the shift key and the left button (2-button
mouse) before selecting the view area, or return to the select
mode with the right mouse button. You can continue to zoom in
from full zoom until you return to the select mode.
Zoom In
This icon defines an area of the current strategy to view. Select
the view area using your mouse like you do with full zoom.

Pan
Select Pan to move the image around in the workspace. Hold
down the left mouse key, move the hand the distance and
direction you wish the image to move, then release the key. The
new location is offset by the distance the icon was moved. Click
the right mouse key to return to the select mode.
Home
Select the Home icon to return to the central strategy view. This
is the view you are in when creating a new strategy. It
represents a small portion of the entire world your strategy may
exist in and is located in the center of that world.

4-25
Application Builder
TOOLBAR REFERENCE

4.16 LIBRARY
Select the Library icon to list the types of devices and functions you can place
in your workspace. The System Library is available from the root directory
level. Choose MODCELL or MOD 30ML (if available) to get the appropriate
instrument group. When in the instrument level, the Library icon is used to
display the Instrument Library. Similarly, when in a loop, the Loop Library is
displayed. See Configuration for details on the functions provided in each of
the library groups.

The System, Instrument and Loop

library levels represent different
algorithm sets (sets of resources)
that can be placed in your strategy
at the level where they are designed
to exist. For example, an instrument
cannot contain an instrument or a
loop compound another loop
compound or loop functions that
must execute as part of a loop
cannot be at the instrument level.

Selecting a library item causes the

functions associated with that group
to be displayed along the left side of
the workspace.

4-26
 Application Builder
TOOLBAR REFERENCE

4.17 SELECT
Select the Select icon to enter the Select Mode and pick other icons. You can
return to the Select Mode from a connect mode by pressing the right mouse
button. This icon will display with a dark background when you are in the
select mode.

4.18 REFRESH SCREEN

Select the Refresh Screen icon to regenerate the current workspace image.
The refresh function assures that all image details are valid. For example,
garbled images of connection arrows can be cleaned up by a refresh.

4.19 HELP
Select the Help icon as an aid in remembering toolbar functions, conventions,
what to do in different levels and for other general usage considerations.
Additional help is available when you are configuring different blocks by
selecting the ? button in the function block edit displays. The edit display help
screens list database mnemonics and describe entry fields. The options
available under the help icon are:

Toolbar Reference Help

Select the Toolbar icon to display a representation of each icon
along the toolbar and a description of the icon. The system
level icons are described when you are in the system level and
the instrument level icons are described when you are in the
instrument level.

General Help
Select the General icon to get help for system, instrument and
loop level usage, how to use compounds, status page, and
different blocks. General help is level specific like the toolbar
help.

4-27
Application Builder
TOOLBAR REFERENCE

4.20 ABOUT THIS SOFTWARE

Select the About icon to display information about your software. You should
know your version number when talking to us about this software. Select OK
to leave this menu.

4-28
 Application Builder
TOOLBAR REFERENCE

4.21 CHECK DATABASE EXECUTION ORDER

Select the Check Database icon to manually or automatically establish a
database execution order for selected blocks or for the compound you are in.
Connected blocks are ordered based upon the source and destination of the
connection where the source is executed first. Since an order cannot be
automatically determined from control loop connections, a loop order window is
used to request the order you want.

Manually Order Selected Blocks

Select the Manual icon to get the Execution/Occurrence display.
Change execution order and block occurrence numbers by
editing the Exec and Occur fields. Select enter to modify the
order. Select Esc to leave numbers unchanged.

Automatically Order Selected Blocks

The Auto icon allows the software to automatically establish a
database execution order for selected blocks or for the
compound you are in through the order select and order
compound icons.

4-29
Application Builder
TOOLBAR REFERENCE

Order Selected Blocks

The Order Selection icon is contained under the check
database icon of the main toolbar. Selecting this icon causes
the blocks contained within the selection to be ordered. For
each unique loop contained in the selection the user is
prompted with the loop order window.

Order Compound
The Order icon is contained under the check database icon of
the main toolbar. Selecting this icon causes the blocks
contained within the current compound to be ordered. For each
unique loop contained in the compound the user is prompted
with the loop order window.

Loop Order Window

The loop order window is
displayed when loop or-
dering is enabled and you
encounter a control loop.
The window is broken into
two sections.

The first section contains a graphical representation of the loop.

The blocks found in the control loop are displayed in this
section. You may select blocks from within this section with the
left mouse key. The second section of the execution order
window is the status window. The status window contains the
block tag name and the block order for the selected tag. To
select which block should be first in the execution order chain,
make your selection and then select OK. Alternately, you may
select the choice with a double left key operation and the
selection will be automatically made.

NOTE: Changing execution order and occurrence numbers can

cause problems with a strategy already implemented. Be
sure to consider your previous work if you make a
change.

4-30
 Application Builder
TOOLBAR REFERENCE

4.22 I/O GRAPHIC

Select the I/O Graphic icon to edit the placement of I/O modules on a graphical
representation of the I/O module slots. The slot layout displayed can be either
the eurocard format or the flush mount format depending upon the instrument
type specified when the instrument is selected and identified at the start of the
configuration procedure; see Section 5.2.

The boxes representing the modules are color coded as follows:

DIM Gray
DOM,DDOM,WDOM Teal
VCIM - Volts, mV White
VCIM Current Pale Yellow
VCIM Current - 2-Wire Yellow
TIM, CJIM Bright Red
RIM, WRIM Bright Blue
AOM Light Green
ICN, MSC Light Blue
RIO Light Gray

4-31
Application Builder
TOOLBAR REFERENCE

Configured I/O modules, for which a slot has been specified, appear on the
display in their assigned slot locations. When more than one module is
assigned to a slot, the modules appear stacked up in the assigned slot. As
many as five modules can appear in a stack in any slot. For example, if the
default configuration of slot 1 is accepted for all the modules in an instrument,
the modules appear stacked up in slot 1. When there are more than 5 modules
assigned to a slot, the excess modules do not appear until the number in the
stack is reduced. As modules are moved from the stack to assigned slot
locations, they are replaced by any modules which have not appeared.

This display supports the following activities:

Move An individual module can be moved by pressing the left mouse
key with the cursor over the active region of the module,
dragging the resulting icon to the required slot, and releasing
the key to place the module in the slot. The active region is
anywhere within the box representing the module. If the
module is in a stack, the active region is the visible portion of
the box. The software checks slot assignments and generates
an error message if an invalid location is chosen. New slot
locations are entered into the data base when Enter is selected
to exit the I/O Graphic display. Selecting Esc leaves the data
base unchanged unless a block has been changed (see below).
Query An individual slot can be queried by clicking the right mouse
key on the slot number. A window appears listing the tag name
and type of each module occupying that slot. Close the window
by clicking on the red diamond in the upper left corner.
Block Edit An individual module can be edited by clicking the right mouse
key with the cursor in the active region of the module. The I/O
module block edit display appears, and the block configuration
can be edited in the usual manner; see Section 3.6. Changes
in the module configuration are entered into the data base when
Enter is selected to exit the edit display. The I/O Graphic
display returns, and the module location reflects any change
entered on the edit display.
Power Use Total current consumption for the configured modules is
displayed in the status bar. The user must keep track of the
instrument current consumption limit based upon the power
supply rating. If it is exceeded, modules must be deleted to
bring the current consumption within the required limit.

4-32
 Application Builder
TOOLBAR REFERENCE

4.23 COMPOUND OPERATIONS

Select the compound operations icon to make, break, save, load or load with
preview, or password protect a compound. Select objects that are to be
compounded before compounding. Use the left mouse button to make a
compound. Use the right mouse button to display the additional choices in the
compound icon submenu. Use the cancel icon to exit from the submenu.

Make List Connected Compound

Make is the default operation provided when selecting the
compound icon with the left mouse key. The make operation
takes selected blocks and compounds them and creates a
compound object which contains the objects.

Break Compound
The break icon takes a currently selected list compound and
breaks it into its component parts (password requested if used).
External connections made to the compound will be wired to the
compounds component parts. Directed connected and loop
compounds (CPD) cannot be broken.
or
Load or Load with Preview Compound
The load icon allows the user to load previously saved
compounds into the current strategy. When Load with preview
is selected in your view preferences, your load menu includes a
graphic window of the contents of the selected compound.

Save Compound
The save icon allows the user to save a selected compound to
disk (.CSM file). The compound is saved as an independent
item and can be loaded into another strategy or into another
compound in the current strategy.

Password Protect Compound

The password icon allows the user to assign a password to the
compound. The password is required when entering the
compound. The user can change a password by selecting this
icon and then providing the old password.

4-33
Application Builder
TOOLBAR REFERENCE

4.24 CONNECTIONS
Select the Connect icon to make connections between blocks and compounds.
After selecting the connection arrow, select the block or compound icon that
you want to make a connection from. If you select a compound, a Tag List
menu is displayed. If you select a block, select the attribute from the attribute
list. Next, select the block you want to make a connection to. In a similar
manner, select your attribute. The connection arrow takes precedence over
any local input data specified in the block menu.

Tag list displays blocks and compounds.

Double click compound to move into it.

Attribute list displays up to 32 attributes.

Use PREV and NEXT to move through menu.

4.25 WIRELESS CONNECTIONS

Select the Wireless Connect icon to make connections between blocks that do
not clutter the screen with lines. After selecting the wireless connection arrow,
select the block or compound that you want to make a connection from using
the tag list menu and then the attribute list as shown above. Next, select the
block or compound you want to make a connection to in the same manner.
The connection arrow takes precedence over any local input data specified in
the block menu. You will automatically return to the select mode after using
the wireless connect mode.

4-34
 Application Builder
CONFIGURATION

SECTION 5
CONFIGURATION

5.1 GENERAL
A System Library Instrument group is used to define or edit data base
parameters for a particular version of an instrument type. This section describes
how to configure a data base by placing instrument and other supporting blocks
onto your workspace, editing those blocks and connecting them to make a
strategy. See Section 4, Toolbar Reference if you wish to load an existing
data base or save your configured data base.

5.2 CONFIGURATION PROCEDURE

When entering the Application Builder, you are presented with a blank
workspace, some tools and some instrument resources. This is the root (or
system) level of your strategy. You obtain instrument resources at this level.
Before proceeding, you may wish to set your view and execution order
preferences and size your grid.
The recommended order of steps for configuring a new data base is:
1. Select instrument identity and version, position it on the workspace and
place it by clicking the left mouse button. Click right button to return to the
select mode.
You can configure multiple instruments using one root strategy; however,
only one instrument can be compiled and downloaded at a time. The
compiler uses the instrument tag name to name the instrument data base
files. In general, your computer will run faster, especially loads and
saves, if you configure only one instrument per strategy.
2. Select and identify the instrument and the type (Eurocard or Flushmount for
MODCELL) using the Query activity. A password may be entered.
3. Double click on the instrument to open it. Enter password if used.
One Interface block (IF) and System Event block (SE) is required for
each MODCELL instrument. These blocks are automatically placed in the
first instrument level as shown in Figure 5-1. In addition, a MOD 30ML
instrument will include a State Table block (ST) and a Display Interface
block (DIF).

5-1
Application Builder
CONFIGURATION

Figure 5-1. Instrument Level Display

4. Define parameters for Interface and System Event blocks (Section 5.3).

NOTE: The data for any configurable field is described in the data base
reference book and a database report can be sent to your printer as
described in Section 4.13.1.

5. Make I/O and communication module block selection choices and configure
block displays (Section 5.4).

I/O and communication module blocks are not part of a loop scan group.
I/O module blocks can be placed anywhere in an instrument strategy.
The ICN and MSC communication module blocks are available outside of
loop compounds only and are placed somewhere at the instrument level.
When assigning tag names, it may be helpful to use the slot number in
the I/O block names (e.g., DIM1).

5-2
 Application Builder
CONFIGURATION

6. Create loop compounds for the instrument, query each loop compound and
identify it, double click on loop compound to enter it, configure the loop
block, make function block choices, and configure blocks (Section 5.5).
Take the time to assign meaningful tag names.

7. Compound function blocks as necessary to make application groups or

states (Section 5.6).
A strategy segment saved as a compound can be loaded for use
elsewhere in your strategy or in another instrument as long as the
functions are at an equivalent level. For example, a compound built
using loop level functions can only be placed in another loop.

8. Make connections (Section 5.7).

9. Connect to list blocks. For reports, open list blocks after all connections
are made so the block can “find” its connections (Section 5.8).
A list block requires the existence of the source blocks to make a
connection. A configured list may contain other configured lists unless
it is used to collect Modbus data. If the block with data base reports
connections is not opened and entered after connections are made the
connections will be reported as NONE.

10. Compile data base configuration and make fixes if required (Section 5.9).
A database that is successfully compiled can be downloaded to an
instrument and/or used to build a strategy for your PC based operator
displays. Compile as you build to check your work.

11. DOWNLOAD data base configuration to instrument (Section 5.10). Make

sure your serial ports are set up properly (Section 4.5).

12. Make a text file of database and print hard copy if desired (Section 4.13).

13. Optionally, make a backup copy of database configuration, using the Save
Database activity and specify an extension such as .SAV (Section 4.4).

14. Exit Application Builder (Section 4.2).

At this point you can configure your operator interface strategy. For
PC-30, use the TIF file created after a successful compile to build a
strategy (third party software is supported by the MIF file).
Any old data files can be deleted from disk while out of the Application
Builder. See Appendix A for a description of data files generated.

5-3
Application Builder
CONFIGURATION

5.3 SYSTEM BLOCKS (INSTRUMENT LIBRARY)

System blocks, at the instrument level, contain the overall instrument related
information and functionality that does not logically fall within any loop or
function block. These blocks exist as resources through the System choice on
the Library icon. Only one interface and system event block is supported as
part of the instrument configuration. These blocks are automatically made
available with each instrument. Other system resources at the instrument level
are the loop compound, the configured list and Modbus list blocks as described
below.

IF Interface Block. Reference IB-23G600 Section 3.3. The Interface

Block edit display, Figure 5-2, is used to specify up to five
independent function block groupings for a database. Loops are
included in a group by specifying the desired group number in each
loop block. The group scan intervals set the rate at which each group
will be executed when the instrument is in the RUN state.

SE System Event Block. Reference IB-23G600 Section 3.4. This block

stores a configurable number of time stamped event codes for the
diagnostic points and events reported by the data base blocks.
These codes are translated into messages for operator display or
logging.

LP CPD Loop Compound. The loop compound block is a list connected

compound that contains a Loop Block. Any function block placed in
this compound becomes part of the loop block scan group.
Reference IB-23G600 Section 3.5 for information on the loop block.
As a compound, this resource can be saved and loaded for use
elsewhere. Loop library resources are available within this compound.

CL Configured List. Reference IB-23G600 Section 3.6. This block is

used to define data base attributes to be collected as a foreground list
for a ICN or MSC module block, or as a Modbus list for a MSC
module block or solely to specify data to be included in interface files
(TIF or MIF). List blocks are configured as described in Section 5.8.

ML Modbus List. Reference IB-23G600 Section 3.7. A Modbus List is

used to specify data that is to be converted into pure Modbus data (a
2-byte positive value). It is connected through a MSC block. List
blocks are configured as described in Section 5.8.

5-4
 Application Builder
CONFIGURATION

DISP Display block. Reference IB-1800R-APP. Multiple DISP blocks are

supported by the MOD 30ML. Each block defines a user display.

DIF Display Interface block. Reference IB-1800R-APP. One DIF block is

supported by the MOD 30ML. This block defines the user display list
and controls display presentation.

ST State Table block. Reference IB-1800R-APP. One ST block is

supported by the MOD 30ML. It is home to all state tables.

TL Tune List block. Reference IB-1800R-APP. Multiple TL blocks are

supported by the MOD 30ML. It defines a set of tunable parameters.

Select field and enter data, or Use page forward and backward
click on field to scroll through to move through pages
data choices.

Each loop
is as-
signed to
a group
scan inter-
val that
must be
some non-
zero time.

Figure 5-2. Interface (IF), Block Edit Display

5-5
Application Builder
CONFIGURATION

5.4 I/O AND COMMUNICATION MODULE BLOCKS

I/O and communication module blocks are not part of a loop scan group. I/O
module blocks can be placed anywhere in an instrument strategy as a
convenience to the user. The ICN and MSC communication module blocks are
available outside of loop compounds only and are placed somewhere at the
instrument level.

Place your I/O modules either in a loop with their associated input functions
(connection made at same level) or together at the instrument level so they can
service different input functions (requires more connections through CIB blocks
at different levels). If you decide to place your I/O modules in a direct
connected compound (Section 5.6), you can treat the CPD block as a
centralized I/O connection source. Use the MODOUT connection of each input
module to create a connection to MODIN of a matching input function. Use the
output module INPUT connection as you logical source pointer. There are 32
available module slots that can be filled on a MODCELL Multiloop Processor
(use the I/O module layout icon to assign slots).

5.4.1 Communications Module Block Selection

From the instrument level Library Display, select Communication to make the
Communication modules available as resources. The Communications
modules types are:

ICN Instrument Communication Network Module. Reference IB-23G600

Section 3.7. This block links configured lists, input and output
communications blocks, notification message blocks and supervisory
message blocks to other devices on the ICN through the ICN module.
The 2030N ICN Communication module can be located in the following
slot pairs (ICN numbers based upon assigned occurrence in .CRF file).
Slots: ICN1 31-32; ICN2 28-29, 29-30; ICN3 25-26, 26-27, 27-28

MSC MOD Serial Communication Module. Reference IB-23G600 Section

3.26. This block links Modbus lists to Modbus devices through an
RS232 or RS485 module. The MSC module can be located in the
following slots.
2033N RS232, 2034N RS485 Communication Module (two slots)
Slots: MSC1 31-32; MSC2 28-29, 29-30; MSC3 25-26, 26-27, 27-28
2032N RS485 Communication Module
Slots: MSC1 32; MSC2 29, 30; and MSC3 26, 27, 28

5-6
 Application Builder
CONFIGURATION

5.4.2 Example of Defining Parameters for ICN Module Block

Double click on the block icon to open the block edit display. Edit any fields
that require new values. Section 3.6 describes edit block displays. Bypass
any field whose default value is appropriate for the application at hand (if ICN
module location is set correctly, the defaults will allow ICN comunication).
Move between pages of a multiple page display as required.

For example, select ICN from the Communication library display, place it and
open it to the edit block display for the ICN Communication block as shown in
Figure 5-3. Use the planning forms to organize parameter entry. Refer to the
data base reference book for detailed descriptions of the data base parameters.

Inst Type:
All Devices
SLU = Sequence and Logic Unit
PC30 = PC-30 Software
MOD 300
1180M = Accuray 1180M
MODCELL

Enable/Disable: ICN Addr:

ANY = Any authorized source ICN address switch setting for
(Source 1 only, ICN interface board (board that
remaining entries the instrument ICN is
ignored) connected to). The range of
valid addresses is 0-15.

Figure 5-3. Example, ICN Communication (ICN), Block Edit Display, Page 1

One parameter of particular importance is the Authorized Computer Sources

parameter. This parameter is used to establish control devices for the
instrument being configured. For example, entering PC30 as the device type
allows an operator to control the instrument through the PC-30 runtime displays.

5-7
Application Builder
CONFIGURATION

5.4.3 Input/Output Module Block Selection

From the Library Display, select Input/Output to make the I/O modules available
as resources. The different types and their associated hardware modules are:
DIM Digital Input Module. Reference IB-23G600 Section 5.2. This block
links MODOUT for the following modules to a DI block (MODIN).
2004A Solid State Relay Input,
2006A Unconditioned Digital Input
DOM Digital Output Module. Reference IB-23G600 Section 5.3. This block
has a discrete attribute INPUT link for the following modules.
2005A Solid State Relay Output,
2007A Unconditioned Digital Output
WDOM Wide Digital Output Module. Reference IB-23G600 Section 5.3. This
block has a discrete attribute INPUT link for the following module.
2011A Mechanical Relay Output – Single Form C Type (two slots)
DDOM Dual Digital Output Module. Reference IB-23G600 Section 5.3. This
block has two discrete attribute INPUT links for the following module.
2011A Mechanical Relay Output – Dual SPST Type (two slots)
VCIM Voltage/Current Input Module. Reference IB-23G600 Section 5.4. This
block links MODOUT for the following modules to a VCI, TTI or RTTI
block (MODIN).
2001A Voltage Input Module, 2002A Current Input Module,
2012A Current Input with 2-Wire Transmitter Power
CJIM Cold Junction Input Module. Reference IB-23G600 Section 5.4. This
block links MODOUT for the following module to a CJI (MODIN) or TIM
block (CJCIN).
2010A Cold Junction Sensor
TIM Thermocouple Input Module. Reference IB-23G600 Section 5.4. This
block links MODOUT for the following module to a TI block (MODIN).
2013A Thermocouple Input with Upscale Burnout Detection
RIM Resistance Input Module. Reference IB-23G600 Section 5.4. This
block links MODOUT for the following module to a RI or RTI block
(MODIN) or a TIM block (CJCIN).
2009A RTD Input (2 Wire)
WRIM Wide Resistance Input Module. Reference IB-23G600 Section 5.4.
This block is like RIM block except it links the following module.
2009A RTD Input (3 Wire)
AOM Analog Output Module. Reference IB-23G600 Section 5.5. This block
has a floating pt. attribute INPUT link for the following module.
2003A Current Output

5-8
 Application Builder
CONFIGURATION

AIN Built-in Analog Input (MOD 30ML). Reference IB-1800R-APP. One of

two available, this block connects its field data using MODOUT to
MODIN of any analog input function block.

AOUT Built-in Analog Output (MOD 30ML). Reference IB-1800R-APP. One of

two available, this block connects an analog outout of some other block
to the field.

5.4.4 Remote Input/Output Module Block Selection

From the Library Display, select Remote Input/Output to make the Remote I/O
modules available as resources. The different types and their associated
hardware modules are:
RIO Remote I/O Communication Module. Reference IB-23G600 Section
6.2. This module plugs into the instrument and serves as the interface
between it and a CS31 bus. The database must have one RIO block
for each RIO module on the instrument. The RIO module uses CS31
bus address 0.
A connection is required from MODOUT of this block to MODIN of
each remote I/O block in the database that uses this block as the
interface to a CS31 bus. For each of the following, indicate that a
particular channel is used by marking the check box to the left of the
channel number. Enter the bus address of the remote CS31 module
providing the inputs or outputs.
RDIM Remote Digital Input Module. Reference IB-23G600 Section 6.3. This
block represents one or more digital input channels at an address (1-
31) on a CS31 remote I/O bus. Connect MODOUT of the RIO block to
MODIN of this block. Modules with remote digital inputs are:
ICSI 08 D1 (8 non-isolated 24Vdc input channels)
ICSI 08 E1 (8 isolated 24Vdc input channels)
ICSI 08 E3 (8 isolated 120Vac input channels)
ICSI 16 D1 (16 non-isolated 24Vdc input channels)
ICSI 16 E1 (16 isolated 24Vdc input channels)
ICSK 20 F1 (12 non-isolated 24VDC input channels)
ICSC 08 L1 (8 channels for 24VDC input))

5-9
Application Builder
CONFIGURATION

RDOM Remote Digital Output Module. Reference IB-23G600 Section 6.4.

This block represents one or more digital output channels at an
address (1-31) on a CS31 remote I/O bus. Connect MODOUT of the
RIO block to MODIN of this block. Note that a summary page displays
the source or local data for this channel. Pressing the CfgPg button
displays the full configuration page. Modules with remote digital
outputs are:
ICSO 08 R1 (8 relay output channels 2A)
ICSO 08 Y1 (8 transistor output channels 24Vdc 2A)
ICSK 20 F1 (8 isolated relay output channels)
ICSC 08 L1 (8 channels for 24VDC 500mA transistor output)

5.5 LOOP AND FUNCTION BLOCKS

Function blocks (those blocks that execute the logic) cannot operate
independently in the instrument data base. Groups of related function blocks
must be organized into loops. To create a loop, a loop compound block must
be established. Select the loop compound system resource icon from the
Instrument Library.

The execution order of blocks is indicated by the number in the upper right
corner of the block if enabled to do so in the preferences section.

NOTE: The execution order alone does not guarantee that loops are executed
consecutively. To guarantee that loops are executed consecutively,
they must also be assigned to the same scan group number. Consult
the data base reference book for further information on scan groups.

5.5.1 Loop Block Selection

Loop function blocks can only be placed in a loop compound. The loop block
is available in the loop library group as a system resource and is automatically
placed in a new loop compound. Only one Loop block is allowed in a loop
compound.

LP Loop Block. Reference IB-23G600 Section 3.5. This block provides

master loop control for the function blocks found between it and the
next loop block in the database. This includes write access for a
controlling source and group control of function block execution.

5-10
 Application Builder
CONFIGURATION

5.5.2 Tables Block Selection

The piecewise table function block can only be placed in a loop compound.

PW Piecewise Table Block. Reference IB-23G602 Section 9. This block is

a data block that supports 60 pairs of X,Y floating point coordinates for
user defined linearizations or recipe data. Linearization data is sent to
the LN block using the TABLEOUT connection. Recipe data is available
on a per point basis.

5.5.3 Input Function Block Selection

Input function blocks can only be placed in a loop compound. The input
function block types are:

Input Function Block Types:

DI Digital Input Block. Reference IB-23G600 Section 7.3. This block links
a Digital Input Module (DIM) block to a loop.

VCI Voltage/Current Input Block. Reference IB-23G600 Section 7.2. This

block links a Voltage/Current Module (VCIM) block to a loop.

CJI Cold Junction Input Block. Reference IB-23G600 Section 7.2. This
block links a Cold Junction Input Module (CJIM) block to a loop.

TI Thermocouple Input Block. Reference IB-23G600 Section 7.2. This

block links a Thermocouple Module (TIM) block to a loop. It also gets
a compensation input from a RIM, WRIM, or CJIM module.
TTI Thermocouple Transmitter Input Block. Reference IB-23G600
Section 7.2. This block links a Voltage/Current Module (VCIM) block to
a loop.
RI Resistance Input Block. Reference IB-23G600 Section 7.2. This block
links a Resistance Input Module (RIM) or a Wide Resistance Input
Module (WRIM) block to a loop.
RTI RTD Input Block. Reference IB-23G600 Section 7.2. This block links
a RTD input from a Resistance Input Module (RIM) or a Wide
Resistance Input Module (WRIM) block to a loop.
RTTI RTD Transmitter Input Block. Reference IB-23G600 Section 7.2. This
block links a Voltage/Current Module (VCIM) block to a loop.

5-11
Application Builder
CONFIGURATION

5.5.4 Algorithm Block Selection

Algorithm blocks can only be placed in a loop compound. The algorithm types
are:
Algorithm Types:
EX Expression Block. Reference IB-23G602 Section 8.2. This block
evaluates a user specified expression each time it executes. The
result is discrete or floating point depending on the final operation. An
auxiliary result can be used to convert to other data types.
IC Input Communications Block. Reference IB-23G602 Section 8.3. This
block receives data from an Output Communications Block in another
instrument.

OC Output Communications Block. Reference IB-23G602 Section 8.4.

This block transmits data to an Input Communications Block in another
instrument.

LN Linearization Block. Reference IB-23G602 Section 8.5. This block

produces a linearized value of a floating point input.

PA Process Alarm Block. Reference IB-23G602 Section 8.6. This block

produces a discrete signal to advise of an irregular process condition.

TM Timer Block. Reference IB-23G602 Section 8.7. This block is used to

perform timing functions such as delayed start/stop or periodic reset.

NM Notification Message Block. Reference IB-23G602 Section 8.8. This

block sends a message over the ICN and can request a response.

SM Supervisory Message Block. Reference IB-23G602 Section 8.9. This

block reads, writes, sets, tunes or configures an attribute over the ICN
or internally. When SET is selected, all message destination fields are
disabled except for the Attribute field. To make a connection with SET
enabled, start from the target block and connect to this blocks
SETENTRY (signal flow is actually from this block to the selected
attribute). Like configured list connections, the target attribute can be
assigned an alias; however, it is not used with PC-30. A connection to
SETENTRY is ignored for all message types other than SET.
PAD Process Alarm Display Block. Reference IB-1800R-APP. This block
produces a discrete signal to advise of an irregular process condition
and provides an alarm display.

5-12
 Application Builder
CONFIGURATION

TOT Totalizer Block. Reference IB-23G602 Section 8.10. This block is used
to count an analog input signal. Features include: Threshold, Up, Down,
Wrap, Scale Factor, Predetermined Count 1 & 2 and Limit Status.

5.5.5 Sequencer Block Selection

Sequencer blocks can only be placed in a loop compound. The sequencer
blocks support batch control for the instrument. There are three types of
sequencer blocks, all providing the same batch control functions. They differ
only in their input, output, and step capacities. Reference IB-23G602.

Sequencer Block Types:

DVC Device Block. This block provides for 6 inputs, 4 outputs, and 10
steps.

SSEQ Small Sequencer Block. This block provides for 30 inputs, 15 outputs,
and 20 steps.

LSEQ Large Sequencer Block. This block provides for 100 inputs, 30
outputs, and 80 steps

5.5.6 Advanced Algorithm Block Selection

Advanced algorithm blocks can only be placed in a loop compound. The types
are:

PID Regulatory Control Block (Proportional, Integral, Derivative). Reference

IB-23G601 Section 2. This block supports regulatory control for the
instrument.

RSK Ramp/Soak Profile Block. Reference IB-23G601 Section 3. This block

supports up to 36 ramp or soak segments. Functions supported
include: Repeat, Tracking, Guaranteed ramps or soaks, four segment
event states, Reset, Stop, Run, Hold and Skip. This block is typically
used as a remote setpoint input to a PID block.

5-13
Application Builder
CONFIGURATION

5.6 SPECIAL BLOCKS

Your resource of special blocks is available at the instrument and loop levels
through the library icon. These blocks allow you to build different types of
compounds, or add description blocks to your strategy.

5.6.1 Compounding
Compounding of function blocks allows you to make application groups or
states according to process functions or areas. Individual blocks within a
compound become a logical structure or a custom algorithm that can be saved
and used to construct other databases. The state compound is the same type
of compound as offered from the toolbar. Both the state (list) and CPD (direct)
compounds are resources that are placed on the workspace, identified, and
then opened before building items into the compound. Also, these compounds
are dependent on your strategy level. A compound built and saved at the loop
level cannot be used at the instrument level. The opposite is also true.

Compounding can be further logically structured through the use of multiple

layering. The same rules apply to the lower level compounds as apply to the
upper levels. Generally, the instrument level compound is a good place for
logically grouped blocks such as an I/O module group. The loop level is the
place to integrate sequence, logic and continuous control. A maximum of 10
levels are allowed (system is level 1 and instrument is level 2).

5.6.2 List Connected Compound

The state compound is a list connected compound and appears as a green
oval. Any connections made from this compound are made using the tag list
menu of existing tag names and attributes. Connections are made using a tag
list to another block. The other block may be in another compound. In this
way, compounds may be connected together as shown below.

HEAT EMERGENCY

IDLE

CONVERSION
COOL

5-14
 Application Builder
CONFIGURATION

5.6.3 Direct Connected Compound

The direct connected compound (blue rectangle) allows you to develop a
strategy group with its own uniquely named inputs and outputs. Your direct
connection list is created from within the compound. Connections to the
connection interface block (CIB) are presented as outputs. Connections from
the CIB are presented as inputs. Lists expand as the number of connections
increases. Connections are presented in the order they are created. Deleting
a connection also deletes it from the list.

Notes: Names can be duplicated. Do not undo a cut connection since it is not
added back into the connection list.

Enter a connection name of up to 8

characters. Name entered here is
used in connection list (sample list
with two-letters only shown).

Set status as required (shown as

red on connection list) or as
optional (shown as blue on
connection list).

A red or blue name indicates an

available connection (some can be
used more than once). A gray name
indicates a connection that is used.
Input and output lists are separate.

5.6.4 Description Block

The description block allows you to place a description in your strategy any-
where within an instrument. Up to 30 characters are displayed. Additional
characters are saved but not displayed.

5-15
Application Builder
CONFIGURATION

5.7 CONNECT BLOCKS

Blocks are connected using the visible connection (Section 4.24) or the
wireless connection (Section 4.25) method. The visible connection can start
by selecting a block or compound to connect from. The wireless connection
always uses the tag list. Attributes are listed in the data base reference books.
Special connections for modules and lists are given in Table 5-1.

The rules for all block inputs are given in Section 3.11.

Table 5-1. Special Connections for Modules and Lists

Source Block.Attribute* Destination Block.Attribute

input module.MODOUT matching input function.MODIN
RIO.MODOUT remote input or output
module.MODIN
CJIM.MODOUT TIM Block Version 1.CJCIN
CJIM or RIM or WRIM.MODOUT TIM Block Version 2.CJCIN
CL.LISTOUT ICN.FGLISTIN
ICN.BGLISTIN
MSC.FGLISTIN
MSC.BGLISTIN
CL.LISTOUT CL.ENTRYn (n = 1 to 99)
ML.LISTOUT MSC.DRWIN1 . . . DRWIN5
DROIN1 . . . DROIN5
SRWIN1 . . . SRWIN5
SROIN1 . . . SROIN5
MRWIN1 . . . MRWIN5
MROIN1 . . . MROIN5
PW.TABLEOUT LN.TABLEIN
any writable attribute** SM.SETENTRY
* A source can connect to multiple destinations.
** Signal flow is actually from SETENTRY to target attribute. Connection is
made from target attribute to SM.SETENTRY.

5-16
 Application Builder
CONFIGURATION

5.8 CREATE AND CONNECT LIST BLOCKS

Define parameters for configured and Modbus lists blocks and then connect
attributes using visible or wireless connections to the block. A configured list
block is used to specify and/or collect data that is of interest to an external
system. If a block or connection to a list is deleted after a connection is made,
the list field will return to NONE. The Configured List block “finds” its
connections after they are made by opening and entering the block.

Configured List or Modbus List Variable Entry

Connect the desired attribute of some block to one of 99 inputs of this block.
The block tag name and attribute name for all current connections are shown.
Enter an alias or delete a connection as shown below. An alias is used to
shorten the name of an attribute being included in an interface file ("TIF" or
"MIF"). To include another list in this list, connect the "LISTOUT" attribute of
the desired list to an input of this list. Note that if this list is used to collect
Modbus data, it cannot include another list.
Configured List Collect Data
If this list, or any included list, is used as a foreground list for a ICN or MSC
module block, or as a Modbus list for a MSC module block, then you must
enter YES. If this list is used solely to specify data to be included in an
interface file ("TIF" or "MIF"), then buffer space can be saved by entering NO.

Select field to Enter an alias if you wish or delete the connection.

get attribute
path list.

5-17
Application Builder
CONFIGURATION

5.9 COMPILE DATA BASE

To compile your completed data base configuration, select the ABB icon to
access the compile icon and then select the compile function. While compile is
working the icon appears indented as shown.

If there are compile errors, you will get a message indicating there are errors
and only the error messages (.ERR) and data base reference files (.CRF) are
written to disk (if the ID1 file existed for this instrument, it is renamed with the
BAK extension). Make fixes as required before compiling again. The validity of
the I/O configuration to the actual physical I/O cannot be checked during com-
pile. This check is performed by the instrument.

When the data base is successfully compiled, an instrument data base file
(.ID1) and optional files (.TIF, .MIF, .MRF, .WDF) are generated in addition to
the reference (.CRF) and error files (.ERR). The ID1 file is used to download
your data base to the instrument. The TIF file data, as generated from the con-
figured list blocks, is used to pass attributes to a PC-30 strategy and its asso-
ciated PC based operator displays. If a backup ID1 file existed, it is deleted
after the successful compile.

NOTES: Tag names are case sensitive. The tag name MCELL is different
from mcell. However, DOS file names are not case sensitive.
Because of this, MCELL and mcell will produce the same files
during compile.

See Appendix A for a description of the files produced during

compile.

5.9.1 Using TIF Files in PC-30

Data points are addressed by a logical source pointer (LSP). The TIF file built
during the compile activity contains the full path name (or alias) and the corre-
sponding LSP for each data point to be made visible to PC-30. PC-30 strate-
gies and displays are then built using this TIF file.

If you enter the Application Builder and change the database so that a different
data point is now associated with a path name (or alias) already appearing in
the TIF file, the PC-30 Strategy Builder will not recognize this change.

5-18
 Application Builder
CONFIGURATION

If such a change is made, enter the PC-30 Strategy Builder, delete the data
point, and reenter it immediately. This forces the Strategy Builder to reread the
description of the data point from the TIF file and thereby associate it with the
correct LSP.

If you must change several data points, delete the first point and reenter it, de-
lete the second point and reenter it, and so on. Do not delete several points
consecutively and then reenter them. Also, a data point must be changed dur-
ing a single Strategy Builder session. Do not delete a point, save the strategy,
and then reenter the data point at some later time.

5-19
Application Builder
CONFIGURATION

5.10 DOWNLOAD DATA BASE

Select the ABB icon to access and select the download function to get the
Download menu. Make sure your serial port is set properly (Section 4.5).

DOWNLOAD each complete data

base configuration to its respective
instrument. You must specify the
target instrument and the state after
download. For links, specify the ICN
(0-7) and instrument (0-15). For
Modbus, specify an address of 1-
247). The state after download is the
state the instrument should go to, and
the startup type the instrument should
use, after the database has been
downloaded. Choose from RUN or
HOLD state, with a COLD or WARM
start. The DEFAULT state means run
the default instrument database.

In general, a configured database can only be run on the instrument type for
which it was configured (the declared version). However, certain mixes of
database and instrument types/versions are allowed based upon the minimum
calculated database version (instrument contains only those blocks used in an
earlier version instrument). The declared and minimum instrument versions are
stored in the .ID1 file at compile.

For example, a version 2 logic controller can run a database configured for a
version 1 logic controller. Conversely, a version 1 logic controller can run a
database configured for a version 2 logic controller if the database as
configured does not require any version 2 functionality (i.e. no RIM block is
configured).

During configuration downloads, the database will be accepted or rejected as

follows.

5-20
 Application Builder
CONFIGURATION

MODCELL Revision Level Compatibility (Current Versions are bold)

Target Minimum Calculated Database Version
Inst. Logic Logic Logic Logic Logic Logic Reg Reg Reg Batch Adv Adv
Version 1 2 3 4 5 6 1 2 3 1 2 3
LOGIC 1 A R R R R R R R R R R R
LOGIC 2 A A R R R R R R R R R R
LOGIC 3 A A A R R R R R R R R R
LOGIC 4 A A A A R R R R R R R R
LOGIC 5 A A A A A R R R R * R R
LOGIC 6 A A A A A A R R R * R R
REG 1 A A R R R R A R R R R R
REG 2 A A A R R R A A R R R R
REG 3 A A A A R R A A A R R R
Batch 1 A A A A R R A A A A R R
ADV 2 A A A A A R A A A A A R
ADV 3 A A A A A A A A A A A A
Release a b c d e f b c d d e f

where
A= Accept. The database is valid and is downloaded.
R= Reject. The database cannot be downloaded.
*= A database whose minimum version is Batch 1 will run on a Logic 5
instrument provided the database contains no PID blocks.

After the start of a download, the specified instrument becomes unconfigured.

A message indicates downloading. A download finished message appears on
the bottom line and a pop-up menu with OK or CANCEL appears if the
download was successful. If the download was unsuccessful, a download
aborted message appears.

When the configuration is downloaded to the instrument, an end-of-configuration

check is run by the instrument. This test may detect errors that were not
detected by the compile check. If configuration errors are detected during the
download, it will be necessary to correct the errors, compile the data base, and
download again.

5-21
Application Builder
CONFIGURATION

5.11 INSTRUMENT STATUS DISPLAY

Select the ABB icon to access and select the status function. If no communi-
cations data file (sio.dat) exists a message noting that sio.dat not found is dis-
played. Make sure your serial port is set properly (Section 4.5).
The instrument status display, below, allows the user to read or write the cur-
rent, main, default or memory module data base of a specified instrument.
When reading or writing a specific block, use the block and occurrence number
listed in the .CRF file for your database (see Appendix A), NOT the block Tag
Name. The response to the command sent to the instrument is displayed at
the bottom of the response area and is scrolled up through 15 lines by addi-
tional commands. Table 5-2 lists the commands supported by this display.
Click on Setup to get
Communication menu
and to select
appropriate data.
Use Command field
to read and write
selected instrument.
Scroll through
commands sent with
arrows.
View Cross
Reference File or
Print screen with
these buttons.

Table 5-2. Status Commands

Command Description R/W Info
ACK_SD Acknowledge shutdown fault W IF1,CMD 1
UP_MOD Upload to module W IF1,CMD 2
DOWN_MOD Download from module W IF1,CMD 3
SET_WP Set module write protect W IF1,CMD 4
CLR_WP Clear module write protect W IF1,CMD 5
DEL_MAIN Delete main data base W IF1,CMD 6
RES_MAIN Restore main data base W IF1,CMD 7
RESET Restart instrument after task completes W IF1,CMD 8
KILL Restart instrument before completing task W IF1,CMD 9
CLR_MT Clear maximum execution times W IF1,CMD 10

5-22
 Application Builder
CONFIGURATION

Table 5-2. Status Commands (Cont’d)

Command Description R/W Info
CLR_Q Clear event queue W SE1,CLRQCMD 1
ACK_ALL Ack all diagnostics, PA alarms and NM msgs W SE1,GLBACK 1
ACK_DIAGS Ack all diagnostics W SE1,DGACK 1
ACK_ALMS Ack all PA alarms W SE1,PAACK 1
R TIME Read instrument time of day (Time includes R IF1,TIMEDAY
Date and Day or they can issued separately)
R DATE Read instrument calendar date R IF1,DATE
R DAY Read instrument day of week R IF1,DAY
R IOLOCK Read instrument I/O Lock status R IF1,IOLOCK
R COMMLOCK Read instrument communication lock status R IF1,COMMLOCK
R STATE Read instrument state R IF1,INSTATE
R XTIMES Read execution times R IF1 of attributes:
INT1-9, XTIME1-9,
FTIME1-9, MTIME1-9,
SCANTIME,IDLETIME
W TIME data Write instrument time of day W IF1,TIMEDAY data
W DATE data Write instrument calendar date W IF1,DATE data
W DAY data Write instrument day of week W IF1,DAY data
W IOLOCK data Write instrument I/O Lock status W IF1,IOLOCK data
W COMMLOCK data Write instrument communication lock status W IF1,COMMLOCK
data
W STATE data Write instrument state W IF1,NXTISTAT data
R FG Read Minimum Foreground (Link message)
R FGO lsp Read Foreground offset of attribute (Link message)
R BLOCK blkocc# Read block and display bytes in hex (Link message)
R VERSION 1 Read instrument version (Link message)
RQ2 Read instrument event queue (Link message)
R SD type 3 Read instrument shutdown area type (Link message)
R DIAGS type 4 Read specified instrument diagnostic type (Link message)
R lsp Read specified attribute block,attribute
R lsp type 5 Read Byte Before attribute block,attribute
RS lsp Read specified string attribute (RS IF1,USRTAG) block,attribute
RS lsp type 5 Read Byte Before string attribute (RS EX1,13 H) block,attribute
W lsp data Write specified attribute block,attribute
W lsp data type 5 Write Byte Before attribute block,attribute
ACK blkocc# diag# 6 acknowledge diagnostic point (e.g. ACK IF1 9) (Link message)

5-23
Application Builder
CONFIGURATION

NOTES 1. R VERSION command applies to any instrument on the ICN and is returned
as follows (current versions are bold):

Description Return Data

1701R Controller XL Version 3 CxB_X3xxxxxxx
1701R Controller XL Version 2 CxA_X2xxxxxxx
1701R Controller XL Version 1 Cx__X1xxxxxxx
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
1700R Controller Version 5 Cx____5xxxxxx
1700R Controller Version 4 Cx____4xxxxxx
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
1700J Recorder Version 7 RxA__7xxxxxxx
1700J Recorder Version 6 RxA__6xxxxxxx
1700J Recorder Version 5 RxA___5xxxxxx
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
1700N Math Unit Version 5 Ax___5xxxxxxx
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
1710 Sequence and Logic Unit Version 6 SxA___6xxxxxx
1710 Sequence and Logic Unit Version 5 SxA___5xxxxxx
1710 Sequence and Logic Unit Version 4 Sx____4xxxxxx
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
2001P MODCELL Logic Controller Version 6 BxA__6xxxxxxx
" (Versions 1, 2, 3, 4, 5 follow in same fashion) BxA__...
2002P MODCELL Regulatory Controller Version 3 DxA__3xxxxxxx
" (Versions 1, 2 follow in same fashion) DxA__...
2004P MODCELL Advanced Controller Version 3 GxA__3xxxxxxx
" (Version 2 follows in same fashion) GxA__...
2004P MODCELL Batch Controller Version 1 GxA__1xxxxxxx
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
1800P MOD 30ML Controller Functions Version 2 IxA__2xxxxxxx
" (Version 1 follows in same fashion) IxA__1...

2. READ Q returns the most recent event first. The screen displays up to 15
events and a prompt to continue appears if necessary.
3. R SD type is an engineering debug tool command that calls specific
instrument registers as displayed on the Shutdown Information page. Type
indicates which shutdown information to read. Type may be:
I = instrument information (default if type is not specified)
MP = module information at power up
M = module information
Be sure to write protect the memory module if the memory module is being
placed on another instrument to examine the shutdown information. Failure
to write protect the module will cause the shutdown information area to be
written over by the instrument when it powers up.

5-24
 Application Builder
CONFIGURATION

4. R DIAGS type returns the specified diagnostics. The screen displays up to

15 diagnostics of the specified type and a prompt to continue appears if
necessary. The specified types may be:
AB Read abnormal diagnostics - Return points that are active or
unacknowledged (default if type is not specified)
ABQ Read abnormal or quality - Return points that are active,
unacknowledged, or have bad status qualities
UAK Read unacked - Return points that are unacknowledged
UAKQ Read unacked or quality - Return points that are unacknowledged
or have bad unacknowledged status quality
ACT Read active - Return points that are active
ACTQ Read active or quality - Return points that are active or have bad
active status quality
SUP Read suppressed - Return points that are suppressed
ALL Read all points - Return all diagnostic points
5. Type commands (R lsp type, RS lsp type, W lsp data type and WS lsp data
type) are used with BYTE BEFORE data. A BYTE BEFORE attribute has a
configurable data type. For example, to write a BYTE BEFORE attribute of
an Expression Block input, the command might be: W EX1,I1 $AAFF H.
The specified types may be:
C: count D: discrete
S: short state L: long state
DA: date F: floating point
M: msec time A: ascii
H: hex
Data is the data to be written, expressed as follows:
count: 0-65535 discrete: 0-1
short state: 0-15 long state: 0-255
date: D,dd/mm/yy or M,mm/dd/yy floating pt: Floating point number
msec time: hh:mm:ss.sss ascii: “Text string in quotes.”
hex: Hexadecimal number (preceded by $)
6. ACK blkocc# diag# (acknowledge diagnostic point command) is used to
acknowledge a diagnostic point. The read diagnostic command displays

5-25
Application Builder
CONFIGURATION

the block/occurrence and diagnostic code for each diagnostic point, which
can then be used as parameters for this command.

5-26
 Application Builder
APPENDIX A

APPENDIX A
DOS CONFIGURATION FILENAME EXTENSIONS

The following are the filename extensions assigned by the Application Builder
when the save and compile activities are invoked. The filename, as described
below, is the tag name you assign during configuration.

Extension Description of Extensions

Filename.CDB = Configurator data base file for the strategy after the SAVE
DATABASE activity is invoked. Filename = Strategy
Name.
Filename.ID1 = Instrument data base file after the COMPILE activity is
completed successfully (file is used for download to
instrument). The exact configured data base size is
displayed after a successful compile on the bottom line or it
can be determined by checking the size of this DOS file.
Filename = Instrument Tag Name.
Filename.ID2 = LCP data base file name.
Filename.BAK = At the start of compile, the ID1 file, if it exists, is renamed
with the BAK extension. If the compile is successful, a new
ID1 file is produced and the BAK file is deleted. If the
compile is unsuccessful, the BAK file is retained as a
backup. The BAK file is retained until the next successful
compile. Filename = Instrument Tag Name.
Filename.TIF = Tagged interface file. After the COMPILE activity is
completed successfully, you are given the option of creating
this file. This file is used with PC-30. Filename =
Instrument Tag Name.
Filename.MIF = MOD interface file (Version 3 or later). After the COMPILE
activity is completed successfully, you are given the option
of creating this comma separated text file that can be used
with any third party software that is able to interpret the
MIF. Filename = Instrument Tag Name.
Filename.ERR = Error file after the COMPILE activity is completed with or
without errors. This file lists the latest compile errors,
warnings and informational messages such as current
consumption. Filename = Instrument Tag Name.

A-1
Application Builder
APPENDIX A

Filename.CRF = Cross reference data base file for the strategy after the
COMPILE activity is completed with or without errors. This
is an ASCII file of the block occurrence number assigned
during compile and the block tag entered during
configuration. This file is produced in execution order. You
can use the DOS sort command or your other favorite utility
to arrange this file in some other sorted order. Filename
= Instrument Tag Name.
Filename.MRF = Modbus reference data base file for the strategy after the
COMPILE activity is completed without errors. This is an
ASCII file of the register, data type and attributes specified
in ML blocks and sent to an MSC block.
Filename = Instrument Tag Name.
Filename.CSM = Compound submenu data base file for a selected
compound after the SAVE COMPOUND activity is invoked.
Filename = Compound Tag Name.
Filename.RPT = Report data base file when a database report is written to
disk. Filename = Strategy Name.
Filename.DXF = AutoCAD data base file when an Export to DXF report is
written to disk. Filename = Strategy Name at system level,
instrument name at instrument level, loop name at loop
level and compound name at compound level.
Filename.LOG = A log file of all communication messages produced during
any PC to link or Extended Modbus communications if the
log file option is YES in the communication setup menu.
This is a readable file and is mainly for engineering debug
use. Filename = Instrument Tag Name.
Filename.SD1 = Shutdown information file produced when shutdown
information is read from the status page and when the log
file option is YES. As of version 4.00 this is a readable file
(not readable before) and is mainly for engineering debug
use. Filename = Instrument Tag Name.
PREF.CFG = Strategy preference file after saving preferences.
Filename.WDF = Wiring Description file which contains the tag name, block
type and occurrence number, block description, wiring
description and slot number(s) for each I/O module block.
Filename = Instrument Tag Name.

A-2
 Application Builder

INDEX

INDEX

A
AB, diagnostic type . . . . . . . . . . . . . . 5-25 C
ABQ, diagnostic type . . . . . . . . . . . . . 5-25 Cabling . . . . . . . . . . . . . . . . . . . . . . . 2-3
ACTQ, diagnostic type . . . . . . . . . . . . 5-25 CALCOMP, printer driver . . . . . . . . . . 4-24
AIN Block . . . . . . . . . . . . . . . . . . . . . 5-9 CANBJ10, printer driver . . . . . . . . . . . 4-24
Algorithm, custom compounds . . . . . . 5-14 CANBJC, printer driver . . . . . . . . . . . 4-24
Algorithm, standard types . . . . . . . . . . 5-12 CANON, printer driver . . . . . . . . . . . . 4-24
Algorithm set, loop . . . . . . . . . . . . . . 3-9 CDB, filename extension . . . 4-2-4-3, A-1
Algorithm set, copy or move . . . . . . . . 4-11 CFG, filename extension . . . . . . 4-20, A-2
Algorithm set, reporting . . . . . . . . . . . 4-17 CfgPg . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Algorithm set, resource library . . . . . . 4-26 CH-5504, printer driver . . . . . . . . . . . 4-24
Alias . . . . . . . . . . . . . . . . . 4-6, 5-12, 5-17 Change Levels . . . . . . . . . . 3-7-3-8, 4-15
ASCII, data type . . . . . . . . . . . . . . . . 5-25 Checkbox . . . . . . . . . . . . . . . . . 3-13, 4-6
ASCII, reference files . . . . . . . . . . . . . A-2 CIB Block . . . . . . . . . . . . . . . . . 5-6, 5-15
AOM, module block . . . . . . . . . . 4-31, 5-8 CJI Block . . . . . . . . . . . . . . . . . 5-8, 5-11
AOUT Block . . . . . . . . . . . . . . . . . . . 5-9 CJIM Block . . . . . . . . 4-31, 5-8, 5-11, 5-16
Authorization, password . . . . . . 4-14, 4-22 CJCIN, block connection . . . . . . 5-8, 5-16
AutoCAD . . . . . . . . . . . . . . 1-2, 4-18, A-2 CL, block . . . . . . . . . . . . . . . . . 5-4, 5-16
AutoCAD (See DXF) Clipboard . . . . . . . . . . . . . 4-1, 4-11-4-12
AUTOEXEC.BAT . . . . . . . . . . . . . . . . 2-2 CMD field, status display . . . . . . . . . . . 4-8
Color Display . . . . . . . . . . . . . . . . . . . 1-3
B Communication Link . . . . . . . 1-3, 2-3, 2-4
Backup database . . . . . . . . . 5-3, 5-18, A-1 Communication Ports . . . . . . . . . . . . . 1-3
Backup database, load . . . . . . . . . . . . 4-2 Communications Setup . . . . . . . 4-7, 5-22
Backup database, LCP upload . . . . . . 4-9 Compatibility . . . . . . . . . . . . . . . 1-3, 5-21
Backup database, preference . . . . . . . 4-20 Compile (See Database Compile)
Backup disks . . . . . . . . . . . . . . . . . . 2-1 Compile, extensions . . . . . . . . . A-1-A-2
Backup, move up . . . . . . . . . . . 3-8, 4-15 Compiler, tag names . . . . . . . . . . . . . . 5-1
Batch File . . . . . . . . . . . . . . . . . . . . . 3-1 Compounding . . . 1-1-1-2, 3-9, 4-33, 5-14
Batch controller . . . . . 4-6, 5-13, 5-21, 5-24 Compounds
Baud . . . . . . . . . . . . . . . . . . . . . . . . 4-4 Create DXF file . . . . . . . . . . . . . . . 4-18
BGLISTIN . . . . . . . . . . . . . . . . . . . . . 5-16 List Connected . . . . . 3-9, 5-4, 5-6, 5-14
BIOS . . . . . . . . . . . . . . . . . . . . . . . . 4-4 Loading . . . . . . . 3-10, 4-20, 4-22, 4-33
Block Edit Displays . . . . . . . . 3-6, 5-2, 5-5 Magnify tag . . . . . . . . . . . . . . . . . . 4-20
Block id . . . . . . . . . . . . . . . . . . . . . . 4-17 Operations . . . . . . . . . . . . . 4-33-4-34
Block, move, copy . . . . . . . . . . . . . . . 4-11 Saving . . 3-7, 3-10, 4-2, 4-22, 4-33, A-2
Break Compound . . . . . . . . . . . . . . . 4-33 Connections
Byte Before . . . . . . . . . . . . . . 5-23, 5-25 Cable Connections . . . . . . . . . 2-3-2-4

I–1
Application Builder

INDEX

Control Connection . . . . . . . . 4-14, 4-16 Description block . . . . . . . . . . . . . . . 5-15

Drawing right angle preference . . . 4-20 DI Block . . . . . . . . . . . . . . . . . . 5-8, 5-11
Erase . . . . . . . . . . . . . . . . . . . . . 4-10 Diagnostics . . . . . . 5-4, 5-23, 5-25-5-26
Execution order . . . . . . . . . . . . . . 4-29 Diamond Icon, move up a level . 3-8, 4-32
Query . . . . . . . . . . . . . . . . . 4-13, 4-14 Digital blocks . . . . . . . . . . . 5-8-5-9, 5-11
Reports . . . . . . . . . . . . . . . . 4-16, 4-18 DI Block . . . . . . . . . . . . . . . . . . . . . . 5-11
Status . . . . . . . . . . . . . . . . . . . . . 5-15 DIF Block . . . . . . . . . . . . . . . . . . . . . . 5-5
Visible Connection 3-11-3-12, 4-1, 4-34 DIM Block . . . . . . . . . . . . . . . . . . . . . 5-8
Wireless Connection 3-11-3-12, 4-1, 4-34 DISP Block . . . . . . . . . . . . . . . . . . . . . 5-5
CPD blocks . 3-8-3-9, 4-33, 5-4, 5-6, 5-14 Direct Connected Compound . . . 3-9, 5-15
CRF, filename extension . . . 3-7, 4-5, 5-6, Disk Drive
5-18, 5-22, A-2 Flexible . . . . . . . . . . . . . 1-2-1-3, 2-1
CS31 . . . . . . . . . . . . . . . . . . . . . . . . 5-9 Hard . . . . . . . . . . . . . . . . 1-3, 2-1, 5-3
CSM, filename extension . . . . . . . 4-33, A-2 Diskcopy . . . . . . . . . . . . . . . . . . . . . . 2-1
Convention . . . . . . . . . . . . . . . . . . . . 3-7 Distribution Disk . . . . . . . . . . . . . 2-1-2-2
Cursor . . . . . . . . . . . . 3-2-3-6, 4-20, 4-25 DL2400, printer driver . . . . . . . . . . . . 4-24
DDOM block . . . . . . . . . . . . . . . 4-31, 5-8
D DOM Block . . . . . . . . . . . . . . . . 4-31, 5-8
Dat file . . . . . . . . . . . . . . . . . . . . . . . 4-4 DOS . . . . . . . . . . 1-2-1-3, 2-1-2-2, 3-1,
Data Base 3-7, 4-3, 4-14, 5-18, A-1
Compile . . . . . . . . . . 1-2, 3-4-3-5, 3-7, Download (See Database)
4-5, 5-3, 5-18, 5-21, A-1-A-2 DROIN1 . . . . . . . . . . . . . . . . . . . . . . 5-16
Delete Main . . . . . . . . . . . . . . . . . 5-22 DRWIN1 . . . . . . . . . . . . . . . . . . . . . 5-16
Download . . . . . . . . . . . . . . . 1-2, 2-3, Dump screen to printer . . . . . . . . . . . 4-19
4-5, 4-7, 4-9, 5-3, 5-10, 5-20-5-22, A-1 DVC Block . . . . . . . . . . . . . . . . . . . . 5-13
Import Database . . . . . . . . . . . . . . . 4-8 DXF (AutoCAD) . 1-2, 3-7, 4-16, 4-18, A-2
Load Database . . . . . . . . . . . . . . . . 4-2
Restore Main . . . . . . . . . . . . . . . . 5-22 E
Save Database . 3-7, 4-2-4-3, 4-14, 5-3 Edit Display (see Block Display)
Upload Database . . . . . . . . . . . . . . 4-7 EPS3500, printer driver . . . . . . . . . . . 4-24
Data Base Reference . . . . . . . . . 1-5, 5-2, EPSCLR24, printer driver . . . . . . . . . . 4-24
5-7, 5-10, 5-16, 5-18 EPSCLR8, printer driver . . . . . . . . . . 4-24
Database Size . . . . . . . . . . . . . . 1-2, 4-17 EPSESCP2, printer driver . . . . . . . . . 4-24
DDOM Block . . . . . . . . . . . . . . . . . . . 5-8 EPSLQ24, printer driver . . . . . . . 4-19, 4-24
Debug log file . . . . . . . . . . . . . . 4-9, A-2 EPSLQ36, printer driver . . . . . . . . . . . 4-24
Debug status page tool . . . . . . . . . . . 5-24 EPSLQ8, printer driver . . . . . . . . . . . . 4-24
Defining Parameters . . . . . . . 2-2, 3-4, 3-6, Equipment Requirements . . . . . . . 1-1, 1-3
4-11, 4-24, 5-1, 5-4-5-5, 5-7 Erase . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Delete (Cut) Icon 1-2, 3-4, 4-1, 4-10-4-11 ERR file extension . . . . . . . 4-5, 5-18, A-1
Delete connection . . . . . . . . . . 4-14, 5-17 Eurocard . . . . . . . . . . . . . 4-14, 4-31, 5-1
Delete password . . . . . . . . . . . . . . . 4-22 Evaluation Mode . . . . . . . . . . 1-4, 2-3, 3-1
DESKJET, printer driver . . . . . . . . . . 4-24 EX Block . . . . . . . . . . . . . . . . . 3-10, 5-12

I–2
 Application Builder

INDEX

Execution Order . . . 3-10, 4-1, 4-20-4-21 ID1 File . . . . . . . . . . . 4-8, 5-18, 5-20, A-1
Exit . . . . . . . . . . . . . . . . . . . . . . 3-5, 4-9 ID2 File (LCP) . . . . . . . . . . . . . . . . . . A-1
Exporting . . . . . . . . . . . . . . . . . . . . . 3-7 IF block . . . . . . . . . . . . . . . . . . . 5-4, 5-5
Extensions . . . . . . . . . . . . . . . . . 3-7, A-1 Import Database . . . . . . . . . . . . . . . . . 4-8
Extensions (see filename extensions) Input conventions . . . . . . . . . . . . . . . 3-13
Inputs, remote I/O . . . . . . . . . . . . . . . . 5-9
F Instrument Status . . . . . . . . . . . 1-2, 5-22
Filename Extensions . . . . . . . 1-1, 3-7, A-1 Instrument . . . . . . . . . . . . . . . . . . . . . 3-7
Filenames . . . . . . . . . . 3-7, 4-3, 4-14, 4-18 Interconnections ............... 4-10
Fill-in-the-blank . . . . . . . . . . . . . . 1-2, 3-6
FGLISTIN . . . . . . . . . . . . . . . . . . . . . 5-16 J
Flexible Grid . . . . . . . . . . . . . . . . . . . 4-25 JX-720, printer driver ............ 4-24
Flushmount . . . . . . . . . . . . . . . . . . . . 5-1 JX-730, printer driver ............ 4-24
FS850, printer driver . . . . . . . . . . . . . 4-24 JX-80, printer driver ............ 4-24

G K
Grid . . . . . . . . . . 1-2, 3-4, 4-20, 4-25, 5-1 Keyboard . . . . . . . 1-3, 3-3-3-4, 3-6, 4-23
G-500, printer driver . . . . . . . . . . . . . 4-24 KT Icon . . . . . . . . . . 4-5, 5-18, 5-20, 5-22
GQ-3500, printer driver . . . . . . . . . . . 4-24 KX-P1524, printer driver ......... 4-24
KX-P4450, printer driver ......... 4-24
H KYFS850, printer driver .......... 4-24
Hard Disk Drive . . . . . . . . . . . . . . . . . 1-3
Hardware Requirements . . . . . . . . . . . 1-3 L
Hex address . . . . . . . . . . . . . . . 4-4, 5-25 LASRMST, printer driver ......... 4-24
HP500C, printer driver ........... 4-24 Layering compounds . . . . . . . . . 3-9, 5-14
HP550C, printer driver ........... 4-24 LBP-8, printer driver ............ 4-24
HPJET300, printer driver ......... 4-24 LCP . . . . . . . . . . . . . . . . . 4-5-4-6, 4-9
HPJETXL, printer driver .......... 4-24 List Connected Compound . 3-9, 4-30, 5-14
HPLASRJT, printer driver . . . . . . . . . 4-24 LISTIN . . . . . . . . . . . . . . . . . . . . . . . 5-16
HPLSRJT4, printer driver ......... 4-24 LISTOUT . . . . . . . . . . . . . . . . 5-16-5-17
HPPNTJT, printer driver . . . . . . . . . . 4-24 LN Block . . . . . . . . 3-10, 5-10, 5-14, 5-16
LP Block . . . . . . . . . . . . . . . . . 3-8, 5-10
I LP CPD Block . . . . . . . . . . . . . . 3-9, 5-4
IC Block . . . . . . . . . . . . . . . . . . . . . . 5-14 LSEQ Block . . . . . . . . . . . . . . . . . . . 5-13
ICN . . . . . . 1-4, 5-6, 5-8, 5-12, 5-16, 5-24 LSP . . . . . . . . . . 5-18-5-19, 5-23, 5-25
ICN (Network) . 1-5, 2-3, 4-6, 5-6, 5-7, 5-20 LQ, printer driver .............. 4-24
ICN Block . . . . . . . 5-2, 5-4, 5-6, 5-7, 5-16 LX6, printer driver .............. 4-24
Icon . . . . . . . . . . . . . . . 1-2, 3-1-3-3, 5-1 LXMK, printer driver ............ 4-24
ICSC, remote I/O . . . . . . . . . . . . . . . . 5-9 LXPK, printer driver . . . . . . . . . . . . . 4-24
ICSI, remote I/O . . . . . . . . . . . . . . . . 5-9
ICSK, remote I/O . . . . . . . . . . . . . . . . 5-9 M
ICSO, remote I/O . . . . . . . . . . . . . . . 5-9 Magnify Tag . . . . . . . . . . . . . . . . . . . 4-20

I–3
Application Builder

INDEX

Messages Loop Order Window . . . . . . . 4-21, 4-30

Error Messages . . . . . . . . . . . 3-5, 5-18 On The Fly . . . . . . . . . . . . . . . . . . 4-21
Event Messages . . . . . . . . . . . . . . . 5-4 Order Compound . . . . . . . . . . . . . 4-30
Posted Messages . . . . . . . . . . . . . . 3-5 Order Selected Blocks . . . . . . . . . . 4-29
MIF files . . . . . . . 1-2, 5-4-5-5, 4-5-4-6, Outputs . . . . . . . . . . . . . . 5-9, 5-13, 5-15
5-17-5-18, A-1
Mini Link . . . . . . . . . . . . . . . 1-3, 1-5, 4-4 P
Minimize .................... 3-12 P1351, printer driver . . . . . . . . . . . . . 4-24
Mismatch . . . . . . . . . . . . . . . . . . . . . 3-10 P2, printer driver . . . . . . . . . . . . . . . . 4-24
MITS500, printer driver . . . . . . . . . . . 4-24 P351, printer driver . . . . . . . . . . . . . . 4-24
ML block . . . . . . . . . . . . . . 5-4, 5-16, A-2 PA alarms . . . . . . . . . . . . . . . . . . . 5-23
Mnemonics . . . . . . . . . . . . . . . . . . . 4-27 PA Block . . . . . . . . . . . . . . . . . . . . . 5-12
Modbus . . . . . 1-3, 2-3, 4-4, 4-6-4-7, 4-9, PAD Block . . . . . . . . . . . . . . . . . . . . 5-12
5-4, 5-6, 5-17, 5-20, A-2 PAN4450, printer driver . . . . . . . . . . . 4-24
MODIN . . . . . . . . . . . . 5-6, 5-8-5-9, 5-16 PAN8543, printer driver . . . . . . . . . . . 4-24
MODOUT . . . . . . . . . . 5-6, 5-8-5-9, 5-16 PAN8543I, printer driver . . . . . . . . . . . 4-24
Mouse PAN8543M, printer driver . . . . . . . . . . 4-24
Connection . . . . . . . . . . . . . . . . . . 2-3 Parity . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Cursor . . . . . . . . . . . . . . 3-2, 4-20, 4-27 Password . . . . . . . . 1-2, 4-2, 4-14-4-16,
Requirements . . . . . . . . . . . . . . . . . 1-3 4-20, 4-22, 4-33, 5-1
Usage . . . 3-2-3-4, 3-6-3-8, 4-25, 5-1 Password Protection . . . . . . . . . . . . . . 1-2
MRF file . . . . . . . 4-5-4-6, 4-8, 5-18, A-2 Paste . . . . . . . . . . . . . . 1-2, 3-7, 4-1, 4-12
MROIN1, MSC attribute . . . . . . . . . . 5-16 PATH Command . . . . . . . . . . . . . 2-1-2-2
MRWIN1, MSC attribute . . . . . . . . . . 5-16 PC-30 . . . . . . . . . . . . . . . 1-1-1-2, 1-5,
MSC Block . 4-5, 4-31, 5-4, 5-6, 5-16, A-2 4-5-4-6, 5-3, 5-7, 5-12, 5-18-5-19
mV . . . . . . . . . . . . . . . . . . . . . . . . . 4-31 PC-Link . . . . . . . . . . . . . . . . . . . . . . A-2
Peripherals . . . . . . . . . . . . . . . . . . . . . 2-3
N PID Block . . . . . . . . . . . . 3-10, 5-13, 5-21
Naming Conventions . . . . . . . . . . . . . . 3-7 Piecewise . . . . . . . . . . . . . . . . . . . . . 5-10
Navigating, find tag . . . . . . . 3-7-3-8, 4-15 Planning Forms . . . . . . . . . . . 1-5, 5-2, 5-7
Networks . . . . . . . . . . . . . . . . . . . . . . 2-3 POSTSCPT, printer driver . . . . . . . . . 4-24
NM Block . . . . . . . . . . . . . . . . 5-12, 5-23 Precedence . . . . . . . . . . 3-14, 4-12, 4-34
notification . . . . . . . . . . . . . . . . . 5-6, 5-12 Preferences 3-10, 4-1, 4-16-4-23, 5-1, A-2
NXTISTAT . . . . . . . . . . . . . . . . . . . . 5-23 Printer
Connections . . . 1-2, 1-3, 2-1-2-3, 4-23
O Export Graphic . . . . . . . . . . . 1-2, 4-16
OC Block . . . . . . . . . . . . . . . . . . . . . 5-12 Export Report . . . . . . . . . . . . . . . . 4-16
Occurrence . . . . . . . . . . . . . . . . 4-29, 5-6 Printer Preferences . . . . . . . . 4-20, 4-23
OKI192, printer driver . . . . . . . . . . . . 4-24 Printer Drivers . . . . . . . . . . . . 4-23, 4-24
Ordering Printouts . . . . . . . . . . . . . . . . . . . . . . 3-6
Display Order . . . . . . . . . . . . . . . . 4-21 Protection Key . . . . . . . . . . 1-4, 2-1-2-2
Loop Detection . . . . . . . . . . . . . . . 4-21 PSTSCPAR, printer driver . . . . . . . . . 4-24

I–4
 Application Builder

INDEX

PSTSCSER, printer driver . . . . . . . . . 4-24 SIO file . . . . . . . . . . . . . . . . . . 4-4, 5-24

PW Block . . . . . . . . . . . . . . . . 5-10, 5-16 SM block . . . . . . . . . . . . . . . . . 5-12, 5-16
SPST . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Q SROIN1 . . . . . . . . . . . . . . . . . . . . . . 5-16
Query . 3-5, 4-1, 4-13-4-14, 4-32, 5-1, 5-3 SRWIN1 . . . . . . . . . . . . . . . . . . . . . . 5-16
SSEQ block . . . . . . . . . . . . . . . . . . . 5-13
R ST block . . . . . . . . . . . . . . . . . . . . . 5-12
RAM . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Startup . . . . . . . . . . . . . . . . . . . 4-7, 5-20
RDIM block . . . . . . . . . . . . . . . . . . . . 5-9 State compound, list connected . . . . . 5-14
RDOM block . . . . . . . . . . . . . . . . . . . 5-10 Status Bar . . . . . . . . . . . . . . . . 3-2, 4-20
Reassign occurrence numbers . . . . . . 4-6 Strategies . . . . . . . . . . 4-2, 4-5-4-6, 5-18
Redraw Screen . . . . . . . . . . 3-8, 4-1, 4-27 Sublevels . . . . . . . . . . . . . . . . . . . . . . 3-7
Remote I/O blocks . . . . . . . . . . . . . . . 5-9 Subdirectory . . . . . . . . . . . . . . . . . . . . 4-3
Rename . . . . . . . . . . . . . . . . . . . . . . 4-33 Submenu . . . . . 4-5, 4-10, 4-16, 4-25, 4-33
Report Preferences . . . . . . . . . 4-16-4-17
Restore . . . . . . . . . . . . . . . . . . . . . . 4-10 T
RI Block . . . . . . . . . . . . . . . . . . 5-8, 5-11 Tab . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
RIO block . . . . . . . . . . . . . . . . . 5-9, 5-16 TABLEIN . . . . . . . . . . . . . . . . . . . . . 5-16
RICH6000, printer driver . . . . . . . . . . 4-24 TABLEOUT . . . . . . . . . . . . . . . 5-10, 5-16
RIM Block . . . . . . . . . . . . . 5-8, 5-11, 5-16 Tags
RIO Block . . . . . . . . . . . . . . . . . 4-31, 5-9 Cross Reference . . . . . . . . . . . . . . . 4-5
RPT extension . . . . . . . . . . . . . 4-16, A-2 File Names . . . . . . . . . . . . . . A-1-A-2
RS-232 . . . . . . . . . . . . . . . . 1-3, 2-3, 5-6 Finding . . . . . . . . . . . . . . . 3-8, 4-1, 4-9
RS-422 . . . . . . . . . . . . . . . . . . . 1-3, 2-3 Magnify . . . . . . . . . . . . . . . . . . . . 4-20
RS-485 . . . . . . . . . . . . . . . . 1-3, 2-3, 5-6 Query . . . . . . . . . . . . . . . . . . . . . 4-13
RSK (Ramp/Soak) block . . . . . . . . . . 5-13 Report Preferences . . . . . . . . . . . . 4-17
RTD block . . . . . . . . . . . . . . . . 5-8, 5-11 Suggested Names . . . . . . 3-7, 5-1, 5-18
RTI block . . . . . . . . . . . . . . . . . 5-8, 5-11 Tag List . . 3-11-3-12, 4-34, 5-14, 5-16
RTTI block . . . . . . . . . . . . . . . . 5-8, 5-11 Tag Name Display . . . . . . . . . . . . . . 3-2
Wildcard . . . . . . . . . . . . . . . . . . . . 4-12
S TEK4693, printer driver . . . . . . . . . . . 4-24
SD1 extension . . . . . . . . . . . . . . . . . A-2 TEK4696, printer driver . . . . . . . . . . . 4-24
SE Block . . . . . . . . . . . . . . . 3-8, 5-1, 5-4 TEK4697, printer driver . . . . . . . . . . . 4-24
SEIK5504, printer driver . . . . . . . . . . . 4-24 Thermocouple . . . . . . . . . . . . . 5-8, 5-11
SHP720, printer driver . . . . . . . . . . . . 4-24 TI Block . . . . . . . . . . . . . . 3-10, 5-8, 5-11
SHP730, printer driver . . . . . . . . . . . . 4-24 TIF file . . . . . 1-2, 4-5, 5-3, 5-17-5-19, A-1
SSEQ Block . . . . . . . . . . . . . . . . . . . 5-13 TIM Block . . . . 3-10, 4-31, 5-8, 5-11, 5-16
Select . . . . . . . . . . . . . . . . . . . . 3-3, 3-4 TIMER . . . . . . . . . . . . . . . . . . . 4-6, 5-12
Serial Communication Ports . . . . . . . . 1-3 TL block . . . . . . . . . . . . . . . . . . . . . . 5-15
SETENTRY . . . . . . . . . . . . . . 5-12, 5-16 TM Block . . . . . . . . . . . . . . . . . . . . . 5-12
Setup . . . . . . . . . . 4-1, 4-4-4-5, 4-7-4-8 Toolbar . . . . . . . . . . . . 1-1, 3-2-3-3, 4-1,
Shortcuts . . . . . . . . . . . . . . . . . . . . . 3-4 4-27, 4-30, 5-1, 5-14

I–5
Application Builder

INDEX

TOSH1351, printer driver . . . . . . . . . 4-24

TOT (Totalizer) Block . . . . . . . . . . . . 5-13
TTI Block . . . . . . . . . . . . . . . . . . 5-8, 5-11

U
Unchecked . . . . . . . . . . . . . . . . . . . . 3-4
Undo . . . . . . . . . . . . . . . . . . . . 4-10, 5-15
Upgraded, versions . . . . . . . . . . . . . . 3-10
Upload Database . . . . . . . . . . . . . . . . 4-7
Upload LCP . . . . . . . . . . . . . . . . . . . . 4-9
Upload Module Command . . . . . . . . . 5-22
User Interface . . . . . . . . . . . . . . . . . . 1-1
Utilities . . . . . . . . . . . . . . . . . . . . . . . 4-1
Utility . . . . . . . . . . . . . . . . . 4-3, 4-5, 4-9

V
VCI block . . . . . . . . . . . . . . . . . . 5-8, 5-11
VCIM block . . . . . . . 3-10, 4-31, 5-8, 5-11
View Preferences
Preferences Menu 4-20, 4-25, 4-33, 5-1
Save Preferences . . . . . . . . . . . . . 4-20

W
WDF file . . . . . . . 4-5-4-6, 4-8, 5-18, A-2
WDOM Block . . . . . . . . . . . . . . . 4-31, 5-8
Wildcard . . . . . . . . . . . . . . 3-7, 4-12, 4-15
Workspace . . . . . . . . . . . . 1-2, 3-2-3-3,
4-2-4-3, 4-8, 4-10,
4-22, 4-25-4-27, 5-1, 5-14
Workstation . . . . . . . . . . . . . . . . . 1-2, 1-5
WRIM . . . . . . . . . . . 4-31, 5-8, 5-11, 5-16

X
XER4020, printer driver . . . . . . . . . . . 4-24
XL, printer driver . . . . . . . . . . . . . . . 4-24

Z
Zoom ...... 1-2, 3-4, 3-8, 4-1, 4-15, 4-25

I–6
 PRODUCTS AND SERVICING

A Comprehensive Instrumentation Range Servicing

Sensors, transmitters and related instruments for flow, ABB Instrumentation provides a comprehensive
temperature, pressure, level and other process after sales service via a Worldwide Service
variables Organization. Contact one of the following
Flowmeters offices for details on your nearest Service and
electromagnetic, ultrasonic, turbine, differential pressure, Repair Center.
Wedge, rotary shunt, coriolis, vortex.
Differential Pressure transmitters United Kingdom
electronic and pneumatic. London
Temperature ABB Kent-Taylor Limited
sensors and transmitters, fiber optic systems. Tel: (1480) 470781
FAX: (1480) 470787
Pressure transmitters
Level United States of America
sensors and controllers. Rochester, New York
Tank gauging systems ABB Instrumentation Inc.
Cable-length measuring systems
Tel: (716) 292-6050
Fax: (716) 273-6207
Indicators, recorders, controllers and process Italy
management systems Lenno (Como)
ABB Kent-Taylor SpA
Recorders Tel: (0344) 58111
circular and strip-chart types - single and multi-point - for Fax: (0344) 56278
temperature, pressure, flow and many other process
measurements.

Controllers
digital display, electronic, pneumatic. Discrete single-loop
and multi-loop controllers which can be linked to a common
display station, process computer or personal computer.

Pneumatic panel or rack-mounted display and control

instrumentation

Liquid and gas monitors and analyzers for on-line and

laboratory applications
Sensors
pH, redox, selective ion, conductivity dissolved oxygen and
turbidity.

Monitors and Analyzers

for water quality monitoring in environmental, power
generation and general industrial applications.

Packaged analytical instrumentation laboratories

Gas analyzers
Zirconia, paramagnetic, infrared, thermal conductivity.
 IB-23H141 Issue 7
4.97

ABB Kent-Taylor Ltd ABB Instrumentation Inc ABB Kent-Taylor SpA

Howard Road, St. Neots 1175 John Street P.O. Box 20550 22016 Lenno
Cambs. Rochester, New York 14602-0550 Como
England, PE19 3EU USA Italy
Tel: (44-1480) 475321 Tel: (716) 292-6050 Tel: (0344) 58111
Fax: (44-1480) 217948 Fax: (716) 273-6207 Fax: (0344) 56278