TLL Manual PDF

Taylor™ Ladder Logic (TLL) User’s Guide
(Supports AdvaBuild® Versions 2.7 to 3.3)

Taylor™ Ladder Logic (TLL) User’s
Guide
(Supports AdvaBuild® Versions 2.7 to 3.3)
NOTICE
The information in this document is subject to change without notice and should not be
construed as a commitment by ABB Inc. ABB Inc. assumes no responsibility for any er-
rors that may appear in this document.
In no event shall ABB Inc. be liable for direct, indirect, special, incidental or consequential
damages of any nature or kind arising from the use of this document, nor shall ABB Inc.
be liable for incidental or consequential damages arising from use of any software or
hardware described in this document.
This document and parts thereof must not be reproduced or copied without written per-
mission from ABB Inc., and the contents thereof must not be imparted to a third party nor
used for any unauthorized purpose.
The software or hardware described in this document is furnished under a license and
may be used, copied, or disclosed only in accordance with the terms of such license.
This product meets the requirements specified in EMC Directive 89/336/EEC and in Low
Voltage Directive 72/23/EEC.
Copyright © 2002 ABB Inc.

All rights reserved.
Release: July 2002
Document number: 3BUR001981R0201
TRADEMARKS
Registrations and trademarks used in this document include:
Advant, AdvaBuild, AdvaCommand, and AdvaInform are registered trademarks of ABB

Inc.
VAX/VMS is a trademark of Digital Equipment Corporation.
HP and all HP products are registered trademarks of Hewlett Packard Company.

Microsoft, and Windows are registered trademarks of Microsoft Corporation.
MOD 300, Batch 300, and Taylor are trademarks of ABB Inc.
PROFIBUS is a trademark of PROFIBUS International (P.I.).

All other brand or product names are trademarks or registered trademarks of their
respective companies or organizations.
TABLE OF CONTENTS
About This Book

General ............................................................................................................................15
Use of Warning, Caution, Information, and Tip ..............................................................15
Document Conventions ...................................................................................................16
Related Documentation ...................................................................................................17
Section 1 - Introduction
General Information ........................................................................................................19
TLL Overview .................................................................................................................20
TLL Executes in Turbo Nodes and Controllers ...................................................20
Backup Controllers..............................................................................21
Node that Contains TLL Configuration ...............................................................23
TLL Data Processor Resident Displays ...............................................................23
CCF and TCL Standard Displays.........................................................................24
TLL Console Resident Displays ..........................................................................24
Steps to Implement TLL in Your System.............................................................25
Section 2 - Configuration Requirements for TLL

General Information ........................................................................................................27
TLL Message Configuration ...........................................................................................28
Message Routing on the Configuration Area Templet.........................................28
Defining Units for the TLL Messages..................................................................29
TEMPLET NAME Field .....................................................................32
RECIPE DEVICE NAME Field .........................................................32
UNIT DESCRIPTOR Field.................................................................33
DEVICE NAME Field ........................................................................33
3BUR001981R0201 5
Table of Contents
RELATIVE DEVICE NAME Field.................................................... 33

Defining Units for TLL Load Error Messages .................................................... 33
How to Configure Access to TLL Device Directory....................................................... 34
Configuring Access on a Multibus-based Console .............................................. 34
Configuring Access on an Advant Station Operator Station ............................... 35
Templets for Nodes/Controllers That Execute TLL........................................................ 36
Ladder Logic Device Templet.............................................................................. 36
TEMPLET NAME Field..................................................................... 37
SCAN RATE IN MSEC Field ............................................................ 37
MAXIMUM # OF SEGMENTS Field ............................................... 38
AUTO LOAD DEVICE Field............................................................. 38
Ladder Logic I/O Templet ................................................................................... 39
EXPORT Field .................................................................................... 40
NAME Field ...................................................................................... 40
VENDOR Field................................................................................... 40
LAN Field ...................................................................................... 41
BLOCK Field...................................................................................... 41
CH# Field ...................................................................................... 41
DESCRIPTION Field ......................................................................... 41
TYPE Field ...................................................................................... 41
INITOUT Field ................................................................................... 42
Ladder Logic Templets for S800 and PROFIBUS I/O ........................................ 42
Ladder Logic I/O Group Templet ........................................................................ 42
Ladder Logic I/O_2 Templet ............................................................................... 43
EXPORT Field .................................................................................... 44
VENDOR Field................................................................................... 44
CHANNEL PATH Field ..................................................................... 45
6 3BUR001981R0201
Table of Contents
TYPE Field ......................................................................................45

INITIAL OUTPUT Field ....................................................................45
Ladder Logic Timer Templet ...............................................................................45
EXPORT Field ....................................................................................46
TIMER NAME Field ..........................................................................47
DESCRIPTION Field..........................................................................47
TIME BASE Field...............................................................................47
PRESET Field .....................................................................................47
UP OR DOWN Field...........................................................................48
Ladder Logic Counter Templet ............................................................................48
EXPORT Field ....................................................................................49
NAME Field ......................................................................................49
PRESET Field .....................................................................................49
Ladder Logic Register Templet............................................................................50
EXPORT Field ....................................................................................51
REGISTER NAME Field....................................................................51
INITIAL VALUE Field .......................................................................51
Ladder Logic Message Templet ...........................................................................52
MESSAGE NUMBER Field ...............................................................53
MESSAGE TEXT Field ......................................................................53
UNIT ID Field.....................................................................................53
PRIORITY Field .................................................................................53
Ladder Logic File Templet ...................................................................................54
ITEM Field ......................................................................................55
VALUE Field ......................................................................................55
3BUR001981R0201 7
Table of Contents
DESC Field ...................................................................................... 55

Ladder Logic Sequences ...................................................................................... 56
Entries for the Ladder Logic Sequence Templet................................. 56
Entries for the Ladder Logic Seq I/O Templet.................................... 57
STEP NUMBER Field........................................................................ 57
ITEM Field ...................................................................................... 58
I/O POINT NAME Field .................................................................... 58
CCF Templet........................................................................................................ 58
How to Access TLL Variables from CCF FCMs ............................................................ 58
Console Configurator ...................................................................................................... 59
How to Put TLL Information Onto Standard Runtime Displays ......................... 59
How to Put TLL Display Callup Blocks on Overview Displays/PSAPs ............. 59
User Security for TLL Runtime Displays............................................................ 60
Section 3 - Program Structure and Program Instructions

General Information ........................................................................................................ 61
Program Structure ........................................................................................................... 61
TLL Data Structures........................................................................................................ 67
I/O Points ............................................................................................................ 67
Counters ............................................................................................................ 68
Timers ............................................................................................................ 69
Registers ............................................................................................................ 70
Messages ............................................................................................................ 70
Files ............................................................................................................ 71
Sequencers ........................................................................................................... 71
TLL Program Instructions............................................................................................... 73
Relay Instructions ................................................................................................ 73
-] [- Examine On ................................................................................ 73
-]/[- Examine Off ............................................................................... 73
-( )- Output Energize.......................................................................... 74
8 3BUR001981R0201
Table of Contents
-(L)- Output Latch..............................................................................74

-(U)- Output Unlatch..........................................................................74
Data Manipulation Instructions............................................................................75
-[G]- Get ......................................................................................75
-[GET]- Get Data Base.......................................................................75
-[PUT]- Put ......................................................................................75
-[=]- Compare Equal ..........................................................................76
-[<]- Compare Less Than ...................................................................76
-[>]- Compare Greater Than ..............................................................77
-[<=]- Compare Less Than or Equal To .............................................77
-[>=]- Compare Greater Than or Equal To ........................................77
Math Instructions .................................................................................................78
-(+)- Add ......................................................................................78
-(-)- Subtract ......................................................................................78
-(X)- Multiply.....................................................................................79
-(:)- Divide ......................................................................................79
BCD -> BIN ......................................................................................80
GRAY -> BIN .....................................................................................80
Timer Instructions ................................................................................................81
-(TON)- Timer On..............................................................................81
-(RTO)- Retentive Timer On ..............................................................82
-(RTR)- Retentive Timer Reset ..........................................................83
Counter Instructions .............................................................................................83
-(CTU)- Count Up..............................................................................83
-(CTD)- Count Down .........................................................................84
-(CTR)- Counter Reset .......................................................................85
-(CTP)- Counter Preset ......................................................................85
File Instructions....................................................................................................86
Register to File Move ..........................................................................86
File to Register Move ..........................................................................87
File to File Move .................................................................................87
Sequencer Instructions .........................................................................................88
3BUR001981R0201 9
Table of Contents
Sequencer Input .................................................................................. 88

Sequencer Output................................................................................ 88
Sequencer Load................................................................................... 89
Miscellaneous Instructions .................................................................................. 89
-(MCR)- Master Control Reset and -(NCR)- End of Master Control Reset
90
-(ZCL)- Zone Control Last State and -(NCL)- End of Zone Control Last
State.............................................................................. 90
-(MSG)- Message .............................................................................. 91
Section 4 - Interface to Other Applications

Interface with CCF .......................................................................................................... 93
Interface with the Console Configurator ......................................................................... 93
Interface with TCL .......................................................................................................... 93
Interface with Display Builder ........................................................................................ 94
Appendix A - Multibus-based Program Development and

Maintenance
Device Directory Display................................................................................................ 98
Device Directory Callup Procedure ................................................................... 100
Information on the Device Directory Display ................................................... 100
CREATE - How to Add Items to Device Directory Display ............................. 101
LIB - How to Call up a Segment Library........................................................... 101
SEG DISPLY - How to Call up a Segment Display .......................................... 101
DELETE - How to Remove Item from Device Directory Display .................... 102
LOAD LIST - How to Create Auto Load List for Node/Controller .................. 102
Segment Library Display .............................................................................................. 104
Segment Library Callup Procedure.................................................................... 104
Information on the Segment Library Display .................................................... 106
Performing Function Through the Segment Library ......................................... 106
To Select a Segment.......................................................................... 106
10 3BUR001981R0201
Table of Contents
To Display Additional Information ...................................................107

To Exit from the Segment Library Display .......................................107
EDIT SEG - How to Modify an Existing Segment ............................................107
PRINT SEG - How to Print a Segment ..............................................................107
FILES - How to Access Softkeys.......................................................................108
DELETE - How to Delete a Segment ................................................................108
CREATE - How to Create a New Segment ........................................................108
COPY - How to Duplicate Segment...................................................................109
SAVE - How to Save (Backup) Segments..........................................................110
Softkeys Available when Saving Segments.......................................112
How to Load (Restore) a Segment .....................................................................112
Softkeys Available when Loading Segments .....................................................115
Ladder Logic Editor ......................................................................................................116
Ladder Logic Editor Callup Procedure ..............................................................117
Editing Functions ...............................................................................................118
Softkey Sets of the Ladder Logic Editor ............................................................118
How to Insert TLL Elements..............................................................................118
How to Add a Rung to a Diagram.....................................................118
How to Add a Branch to a Rung .......................................................119
How to Add an Instruction to a Line.................................................121
How to Put Comments into the Ladder Diagram ..............................121
How to Insert a Blank Line into the Segment ...................................122
MODIFY - How to Modify an Existing Element ..............................................122
How to Access Keysets for Inserting Elements .................................................122
QUIT EDITOR - How to Exit Editor with No Save ..........................................123
SAVE - How to Save, Compile and Locate Errors.............................................123
COPY How to Copy Portion of Segment...........................................................125
CUT - How to Move Information to Paste Buffer..............................................125
PASTE - How to Paste Information into Ladder Diagram.................................126
BACKWARD/FORWARD - Setting the Search Direction ................................126
Relay Softkeys....................................................................................................126
Data Softkeys .....................................................................................................127
3BUR001981R0201 11
Table of Contents
Math Softkeys .................................................................................................... 129

Timer/Counter Softkeys ..................................................................................... 130
Extended Softkeys ............................................................................................. 131
Cursor/Display Movement in Ladder Logic Editor ........................................... 133
Editing Functions of the Ladder Logic Editor ................................................... 134
Appendix B - Multibus-based TLL Console Support

General Information ...................................................................................................... 137
Common Features of the TLL Displays........................................................................ 138
User Security...................................................................................................... 139
How to Access the TLL Displays ...................................................................... 140
Function Targets on the Operations Displays ................................... 140
Bottom Line Entry ............................................................................ 140
Overviews, PSAPs, and Page Links.................................................. 142
Viewing Information on the TLL Displays........................................................ 142
Screen Targets ................................................................................... 142
Keyboard Keys.................................................................................. 142
Segment Display ........................................................................................................... 143
Segment Display Features.................................................................................. 144
Information on the Segment Display ................................................................. 144
Function Targets on the Segment Display ......................................................... 145
How to Access Data Structure Display for Program Element ........................... 146
Expansion Windows........................................................................................... 147
I/O Point Expansion Window ........................................................... 147
Forcing I/O Points............................................................................. 148
Timer Expansion Window ................................................................ 148
Counter Expansion Window ............................................................. 149
Register Expansion Window............................................................. 149
Message Expansion Window ............................................................ 150
TLL Device Data Base Summary Displays .................................................................. 150
Operator Changes are Logged ........................................................................... 152
Function Targets on the TLL Device Data Base Summary Displays ................ 152
Register Display................................................................................................. 153
12 3BUR001981R0201
Table of Contents
VALUE Field ....................................................................................153

Counter Display .................................................................................................153
VALUE Field ....................................................................................153
PRESET Field ...................................................................................154
Timer Display.....................................................................................................155
PRESET Field ...................................................................................156
VALUE Field ....................................................................................156
ENABLE Field ..................................................................................156
I/O Point Display................................................................................................156
STATUS Field ...................................................................................158
FORCED Field..................................................................................158
File Display ........................................................................................................158
Sequencer Display..............................................................................................160
TLL Items on CCF and TCL Displays ..........................................................................162
INDEX
3BUR001981R0201 13
Table of Contents
14 3BUR001981R0201
About This Book
General
Use this book as a reference tool for TLL development guidelines and syntax. Refer
to the AdvaBuild for Windows 2000 TLL Builder User’ Guide for instructions on
using the Ladder Logic Editor provided by the TLL Builder as used on a Windows-
based Engineering Station. Instructions for using the Multibus-based Ladder Logic
Editor are included in the appendix of this book for reference by HP-UX users.
This book is not intended as the sole source of instruction for TLL. It is
recommended that those people involved in TLL development attend the applicable
courses offered by ABB Automation, Inc.
Use this section as a guide to the conventions and terminology used throughout this
book. For a list of documentation related to TLL, see Related Documentation on
page 17.
Use of Warning, Caution, Information, and Tip

This publication includes Warning, Caution, and Information where appropriate
to point out safety related or other important information. It also includes Tip to
point out useful hints to the reader. The corresponding symbols should be
interpreted as follows:
Warning indicates the presence of a hazard which could result in
personal injury.
Caution indicates important information or warning related to the

concept discussed in the text. It might indicate the presence of a
hazard which could result in corruption of software or damage to
equipment/property.
3BUR001981R0201 15
Document Conventions
Information alerts the reader to pertinent facts and conditions.
Tip indicates advice on, for example, how to design your project or
how to use a certain function.
Although Warning hazards are related to personal injury, and Caution hazards are
associated with equipment or property damage, it should be understood that
operation of damaged equipment could, under certain operational conditions, result
in degraded process performance leading to personal injury or death. Therefore,
comply fully with all Warning and Caution notices.
Document Conventions
The following conventions are used for the presentation of material:
• The words in names of screen elements (for example, the title in the title bar of
a window, the label for a field of a dialog box) are initially capitalized.
• Capital letters are used for the name of a keyboard key if it is labeled on the
keyboard. For example, press the ENTER key.
• Lowercase letters are used for the name of a keyboard key that is not labeled on
the keyboard. For example, the space bar, comma key, and so on.
• Press CTRL+C indicates that you must hold down the CTRL key while
pressing the C key (to copy a selected object in this case).
• The names of push and toggle buttons are boldfaced. For example, click OK.
• The names of menus and menu items are boldfaced. For example, the File
menu.
– The following convention is used for menu operations: MenuName >
MenuItem > CascadedMenuItem. For example: choose File > New >
Type.
– The Start menu name always refers to the Start menu on the Windows
Task Bar.
16 3BUR001981R0201
Related Documentation
• System prompts/messages are shown in the Courier font, and user

responses/input are in the boldfaced Courier font. For example, if you enter a
value out of range, the following message is displayed:
Entered value is not valid. The value must be 0 to30.
You may be told to enter the string TIC132 in a field. The string is shown as
follows in the procedure:
TIC132
Variables are shown using lowercase letters.
sequence name
The following books provide information regarding the development of TLL
programs:
• Configurable Control Functions (CCF) User’s Guide
• Data Base Tables
• AdvaBuild TCL Builder User's Guide (HP-UX)
• AdvaBuild for Windows 2000 TLL Builder User’s Guide
• Operate IT Operation with MOD 300 Connect
• Operate IT Configuration with MOD 300 Connect
This book is available as on-line documentation on the installation CD. After you
install the AdvaBuild documentation (and Acrobat Reader if necessary), you can
access it from the Windows task bar by choosing Start > ABB Industrial IT >
Control IT > AdvaBuild > Documentation > Document.
3BUR001981R0201 17
18 3BUR001981R0201
Section 1 Introduction
General Information
Taylor Ladder Logic (TLL) is a software package that implements industry standard
ladder logic functionality. It can be used in place of a gateway and Programmable
Logic Controllers (PLCs) when ladder logic control is required. TLL segments
execute in Turbo Nodes and controllers. TLL applications run independent of, or in
conjunction with Configurable Control Functions (CCF) and Taylor Control
Language (TCL) functions.
CCF configuration is required for TLL, but it must have a slower

scan rate.
TCL is not required, but can run in the same node as TLL.
There are three platforms for TLL segment development:
• a Multibus-based TLL development node (data processor) in conjunction with
a console subsystem for runtime displays
• a HP-UX Engineering Station in conjunction with a HP-UX Operator Station
for runtime displays
• a Windows-based Engineering Station running AdvaBuild TLL Builder for
Windows 2000® software in conjunction with a Windows-based Operator
Station for runtime displays
You configure the database objects (devices, registers, timers, counters, sequencers,
messages, and so on) that support TLL execution via the Configurator on Multibus-
based nodes, via the Structure Builder on HP-UX Advant Stations (ES or OS/ES),
and via the Control Builder on the Windows-based Engineering Station as described
in Section 2, Configuration Requirements for TLL. On all three platforms, TLL
segment creation and management are supported by Device and Segment Libraries
and the Ladder Logic Editor. HP-UX Advant Stations use RDP emulated Multibus
3BUR001981R0201 19
TLL Overview Section 1 Introduction
Device and Segment Libraries and Ladder Logic Editor displays (that is, Multibus
displays running in the Unix environment). The libraries and editor of the Multibus-
based node and HP-UX Advant Station are described in Appendix A, Multibus-
based Program Development and Maintenance. On the Windows-based
Engineering Station, the Device and Segment Libraries and the Ladder Logic Editor
of the TLL Builder have similar functions but a different appearance as described in
the AdvaBuild for Windows 2000 TLL Builder User’s Guide. At runtime, the
console resident Segment Display and TLL Device Summary Displays (Counter
Display, File Display, I/O Point Display, Register Display, Sequencer Display, and
Timer Display) are used to monitor TLL segments and data structures on all three
platforms. HP-UX Operator Stations use RDP emulated Multibus Segment and TLL
Device Summary Displays which are described in Appendix B, Multibus-based
TLL Console Support. On the Windows-based Operator Station, the Segment and
TLL Device Summary Displays have similar functions but a different appearance as
described in the Operate IT Operation with MOD 300 Connect.
The Multibus-based Ladder Logic Editor is not supported on the

Windows-based Engineering Station platform. If you want to use
the Windows-based Engineering Station for TLL development, you
must use the AdvaBuild TLL Builder.
TLL Overview
This section describes the structure of the TLL package. Figure 1 is a functional
block diagram that shows how the parts are interrelated.
TLL Executes in Turbo Nodes and Controllers

The TLL program in a Turbo Node or controller is broken down into smaller
modules called segments. You produce the segments with the Ladder Logic Editor
and load them into the Turbo Node or controller with either the Auto Load List
Display or the Segment Display. Each segment has a segment number which
determines the execution order. At the beginning of a scan, the segment with the
lowest number is scanned first, followed by the segment with the next larger
number, and so on.
TLL uses the digital I/O that is connected to the Turbo Node or controller. It can be
either direct I/O or remote I/O from the TRIO modules. Direct I/O for a controller
20 3BUR001981R0201
Section 1 Introduction TLL Executes in Turbo Nodes and Controllers
can supply up to 40 regular digital channels and eight interrupting contact input
channels. The number of points provided by direct I/O for a Turbo Node depends on
the number of digital I/O boards in the node. The number of points provided by
TRIO depends on the number and type of TRIO modules. The maximum for a
controller is 960.
TLL can execute in nodes that are simultaneously running CCF and TCL. TLL runs
faster and at a higher priority than the other two packages.
TLL can send out messages to consoles, loggers, and historical recorders as it
executes. When you configure the system, you can specify the text of these
messages.
Backup Controllers
When TLL is in a redundant controller, the segments and data base relations are
fully backed up. Counters, timers and the status of contact outputs are backed up at
CCF base rate intervals. Contact input status and scan location in the program are
not backed up. The scan begins at the first rung upon a switchover.
3BUR001981R0201 21
TLL Executes in Turbo Nodes and Controllers Section 1 Introduction
Multibus
Data Processor Console, Console Resident
Resident Displays HP-UX Displays
Operator TLL Structure Displays
Archive Device Directory Station, or Counter Displays
Segment Library Windows-based Timer Displays
Disk Ladder Logic Editor Sequence Displays
Operator Station File Displays
CCF & TLL I/O Point Displays
Runtime Segment Display
Displays
Turbo Node,
HP-UX Advant Station OS/ES, or
Windows-based Engineering Station
that contains configuration software
TLL Development Software
Ladder Logic Editor (Multibus)
TLL Builder (Windows-based
Engineering Station)
Controller
Configuration Templets
System Configurator (Multibus) Segments
Structure Builder (HP-UX OS/ES)
n1 TLL db Backup
Control Builder (Windows-based CCF Controller
Engineering Station) n2
n3 TCL
Console Configuration n4 CCF db
Console Configurator (Multibus) n5
Environment Builder (HP-UX OS/ES)
Display Builder
Display Builder (Multibus) Turbo Node,
AdvaBuild Display Builder (HP-UX OS/ES)
HP-UX OS/ES
Digital I/O TLL Runtime with RTAB, or
Messages Windows-based
Engineering
Station with RTAB
that executes TLL
Consoles Loggers Historical
Recorders
Figure 1. TLL Functional Block Diagram
22 3BUR001981R0201
Section 1 Introduction Node that Contains TLL Configuration
Node that Contains TLL Configuration

The structures that TLL requires are produced by system-building software that
usually resides in either a Turbo Node that contains the Configurator, a HP-UX
Advant Station that contains Structure Builder software, or an Windows-based
Engineering Station that contains Control Builder software. This software has
several major parts.
• Configuration Templets - Several templets are required for TLL. They define
the basic parameters such as the scan rate for program execution. They also
define data structures such as files, registers, and timers that are required to
support program execution.
• Console Configurator - There are a number of TLL-related items in the
console environments that you build with the Console Configurator software.
– Groups - TLL data structures can be made part of groups. This allows
their parameters to be displayed on the Group, Area and Unit Displays.
– Display Call Ups - You can put blocks on Overview Displays and buttons
on Page Selector, Alarm Panels (PSAPs) that can call up the TLL
Displays.
– User Access Rights - You can use the User Access Authority Display to
determine which classes of users have the right to enter changes to the
TLL Displays.
• Display Builder - User displays built with the Display Builder can access the
parameters of the TLL data structures. These displays can also have page links
to the TLL Displays.
TLL Data Processor Resident Displays

The Data Processor Resident Displays are used to develop and maintain TLL
programs (segments) on Turbo or Advant OCS nodes.
• Device Directory - Lists the nodes and controllers that execute TLL. It can call
up the Auto Load Display that is used to specify which segments are
automatically loaded into a node or controller upon downloading. It can also
specify whether TLL processing starts automatically upon downloading or if it
waits for the operator to start the processing via a command from the Segment
Display.
3BUR001981R0201 23
CCF and TCL Standard Displays Section 1 Introduction
• Segment Library - Lists the segments (ladder program modules) that are in a
node or controller and provide a means to:
– Create new segments
– Delete segments
– Call up the Ladder Logic Editor
– Print the contents of a segment
– Make duplicate copies of segments with new segment names
– Copy segments to other disk devices
– Load segments from other disk devices
• Ladder Logic Editor - Is used to build and modify Ladder Logic segments.
CCF and TCL Standard Displays

TLL parameters can be displayed on standard TCL and CCF Displays. This is
accomplished by assigning TLL counters, timers, registers, and I/O points to groups
when you configure an environment with the Console Configurator.
TLL messages can be displayed on the Sequence Detail, Unit Message, and Unit
Detail Displays.
TLL Console Resident Displays

The Console Resident Displays of Turbo and Advant OCS nodes are used for the
runtime display of TLL data:
• Segment Display - Is used to monitor the TLL execution in nodes and
controllers. It can also be used to turn TLL execution on and off and load and
remove segments.
• TLL Device Data Base Summary Displays - Which include such things as
Counter Displays, File Displays, and so on that are used to view and change
parameters of the data structures.
Refer to the AdvaBuild for Windows 2000 TLL Builder User’s Guide for
information about the runtime display of TLL data on an Windows-based Operator
Station. See Appendix B, Multibus-based TLL Console Support for HP-UX.
24 3BUR001981R0201
Section 1 Introduction Steps to Implement TLL in Your System
Steps to Implement TLL in Your System

The procedures that build the TLL structures are flexible and can be performed in
several different sequences. The steps below are one possible sequence:
1. Become familiar with the TLL software features as described in:
TLL Overview on page 20: Overview of the TLL package
Section 3, Program Structure and Program Instructions: Description of TLL
data structures and program instructions
Section 4, Interface to Other Applications: Description of information
exchange between TLL and other software packages
2. Plan the system. Make lists of items such as files, sequencers, registers, timers,
and counters that you need to support the instructions. Plan the I/O aspects of
your system.
3. Configure the data base. In this process, you build the required files,
sequencers, registers, timers, and counters as described in Section 2,
Configuration Requirements for TLL.
4. Call up the Device Directory Display. Put an entry on it for each controller or
Turbo Node that is to execute TLL.
5. Use the Segment Library and Ladder Logic Editor to build the segments
(program modules) you need.
6. Use the Device Directory Display to create a load list for each node. On the
load list, specify whether the processing is to start automatically upon
download or if it is to wait for commands from the console.
7. Download the nodes and controllers.
8. Use the Segment Display and the I/O forcing feature to debug the segments.
3BUR001981R0201 25
Steps to Implement TLL in Your System Section 1 Introduction
26 3BUR001981R0201
Section 2 Configuration Requirements
for TLL
General Information
Your MOD 300 data base must contain several templets to support TLL execution.
These templets are specified to the system when you perform the system
configuration and console configuration. This section presents information you must
know to decide what values to enter into the data base. Instructions for accessing
and configuring these and other data base templets are provided in the System
Configurator User's Guide and Console Configurator User's Guide (for Multibus-
based configurator), AdvaBuild Basic Functions User's Guide (for HP-UX Advant
Station-based configurator), and AdvaBuild for Windows 2000 Control Builder
User’s Guide (for Windows-based configurator). (Templets are referred to as data
base objects when configuring with the AdvaBuild Structure Builder on the HP-UX
platform or Control Builder on the Windows 2000 platform.)
Note that the figures for templets in this section are those seen on
the HP-UX Advant Station. The templets seen on the Multibus
platform or Windows-based Engineering Station look different, but
they contain the same fields which may have slightly different
labels.
This section is divided into the following topics:
• TLL Message Configuration on page 28 describes entries you must make to
Configuration Area templets so that messages from TLL programs can be sent
to consoles, loggers, and historical recorders. This section also describes how
to configure a unit for TLL load error messages.
• How to Configure Access to TLL Device Directory on page 34 describes
entries you must make to Console Library Configurator templets so that you
can access displays to build and maintain the TLL segments.
3BUR001981R0201 27
TLL Message Configuration Section 2 Configuration Requirements for TLL
• Templets for Nodes/Controllers That Execute TLL on page 36 describes the

templets you must configure for each node or controller that executes TLL.
These templets define the basic parameters such as the scan rate for program
execution. They also define data structures such as files, registers, and timers
that are required to support program execution.
• How to Access TLL Variables from CCF FCMs on page 58 describes the
entries that are needed on Configurable Control Functions (CCF) FCM
templets so CCF can access values of TLL items.
• Console Configurator on page 59 describes the entries you must make to the
Console Configurator to put TLL status information on the Runtime Group,
Area, and Unit Displays. This information allows the operator to monitor and,
in some cases, modify TLL execution. TLL Display call ups and user access
rights to the TLL Displays are also discussed.
TLL Message Configuration

TLL allows ladder programs to send messages to designated messages receivers.
This section describes templets that support this feature.
Message Routing on the Configuration Area Templet

When you complete a Configuration Area templet (AREA), Figure 2, you use its
Message Ctr edit area to specify destinations for TLL messages that originate in the
configuration area.
The system treats TLL messages as if they were Taylor Control Language (TCL)
billboard messages. To send TLL messages to a message destination, all you must
do is specify that TCL billboard messages are sent to that destination.
The possible destinations for the TLL messages are console displays, historical
recorders and loggers. When messages are sent to a console, they can be displayed
on the Sequence Detail, Unit Message, and Unit Detail Displays.
The example of a Message Ctr edit area in Figure 2 shows entries that send TLL
messages to each type of destination, with LOGGER1 and HISTORY1 being the
templet names of their respective items. TLL messages are also sent to any message
receiver that is specified to receive message type TCL_BOTH.
28 3BUR001981R0201
Section 2 Configuration Requirements for TLL Defining Units for the TLL Messages
Figure 2. TLL Message Routing Entries on a Configuration_Area Templet
Defining Units for the TLL Messages

When you configure the data base of a node or controller that is to run TLL, you can
specify the text for messages you want TLL to send to consoles, loggers, and
historical recorders during runtime. In addition, you must assign each of these
messages to a unit. This gives the software a means to sort and store the messages.
For example, when the historical recorder receives a message, it stores it with other
messages assigned to the unit as described in Ladder Logic Message Templet on
page 52. If a message is sent to a console, it is displayed when information about the
unit is requested via the Sequence Detail, Unit Message, and Unit Detail Display.
Besides configuring the messages, you must configure the units required by the
message feature. Some systems use a set of units to support TCL or historical
recording. If your system has that type of unit, you may want to use them for your
TLL messages also. If not, you can use the Unit Master templets (UNITMAST) to
configure units specifically for TLL use. These templets are children of either the
Controller templet or the Generic DPSS templet.
Figure 3 and Figure 4 show a unit configured for TLL messages.
3BUR001981R0201 29
Defining Units for the TLL Messages Section 2 Configuration Requirements for TLL
Figure 3. Unit_Master Templet, Upper Portion
30 3BUR001981R0201
Section 2 Configuration Requirements for TLL Defining Units for the TLL Messages
Figure 4. Unit_Master Templet, Middle Portion
3BUR001981R0201 31
Defining Units for the TLL Messages Section 2 Configuration Requirements for TLL
Figure 5. Unit_Master Templet, Lower Portion
Note that several fields do not require entries. Entries to the following fields are
required:
TEMPLET NAME Field

The entry to this field becomes the name of the unit. It can have up to 12 characters
and must be unique system-wide. This name is used to reference this unit. Although
the configurator allows you to begin the templet name with a number, it is
recommended that the first character be a letter. This is for compatibility with other
applications in the system.
RECIPE DEVICE NAME Field

The entry to this field must be the parent name that appears in the PARENT NAME
field of this templet.
32 3BUR001981R0201
Section 2 Configuration Requirements for TLL Defining Units for TLL Load Error Messages
UNIT DESCRIPTOR Field

You can use this field to specify a descriptor for the unit. An entry is not mandatory.
DEVICE NAME Field

The entry to this field must be the parent name that appears in the PARENT NAME
field of this templet. Note that, when you are configuring via the AdvaBuild Templet
Builder, this field is on page 10 of 11 of the Unit Master templet.
RELATIVE DEVICE NAME Field

Enter a string of up to 21 characters. A compilation error occurs if there is no entry
in this field. Note that, when you are configuring via the AdvaBuild Templet
Builder, this field is on page 10 of 11 of the Unit Master templet.
Defining Units for TLL Load Error Messages

TLL load error messages are a special case of TLL message. You do not specify the
text for a load error message. Load error messages have a predefined text based on
the error that occurred and are handled in a manner similar to other TLL messages.
You can configure a TCL unit for the load error messages as described in Defining
Units for the TLL Messages on page 29, or you can use a unit that has already been
defined. To assign error messages to a unit, use the method described in Ladder
Logic Message Templet on page 52. When you assign the message number, use
message number 0 to define the unit for TLL load error messages.
3BUR001981R0201 33
How to Configure Access to TLL Device Directory Section 2 Configuration Requirements for TLL
How to Configure Access to TLL Device Directory

You must configure a means for users to access the TLL Device Directory Display.
There are two methods, depending on whether you want to access the display on a
Multibus-based console, or the Advant Station Operator Station.
Configuring Access on a Multibus-based Console

The standard means to access the TLL Device Directory display on a Multibus
console is through the console libraries. To allow for this you must configure an
entry for TLL on the Console Library Configurator templet of each console that you
want to be used to develop TLL programs. This entry is usually in the form:
LADDERLOGIC LADDERLOGIC templet name 0
where:
The first LADDERLOGIC identifies the program to be called up. This is a
standard entry and must be LADDERLOGIC.
The second LADDERLOGIC in the entry defines the descriptor that appears on
the library for calling up this program. This field is your choice. You can enter
whatever descriptor you want for your display.
The third field must contain the name assigned to the subsystem that contains
the TLL editor via the templet name field of its GENERIC_DPSS templet.
The fourth field should be left at 0.
The Console Library Configurator templet is described in the Configurator User's
Guide (for Multibus-based configurator), and in the appropriate AdvaBuild
Engineering Methods for Systems with MOD 300 Software (for HP-UX Advant
Station-based configurator) or AdvaBuild for Windows 2000 Engineering Methods
(for Windows-based configurator) user’s guides.
You cannot build TLL programs until you can access the Device Directory Display.
If you want to develop these programs before your final data base is downloaded
and you do not have a LADDERLOGIC entry on your console library, you should
reconfigure your Console Library Configurator templet, recompile the console node,
then install and download the node.
34 3BUR001981R0201
Section 2 Configuration Requirements for TLL Configuring Access on an Advant Station Operator
When you place a callup entry for TLL on the Console Library
Configurator templet, you are effectively stating that you intend to
use the TLL software. You must read the software license prior to
making the entry. You must also be willing to abide by the terms
and conditions of the license.
Configuring Access on an Advant Station Operator Station

To provide access to the TLL Device Directory display on an Advant Station
Operator Station, you must add an external display in the AdvaBuild Environment
Builder.
To configure external display access for the TLL Device Directory, the following
entries are required in the External Display Access Add dialog box:
External Display Name For External Display Name, enter: LadderLogic

Class For Class, choose: Engineer
Display Type For Display Type, choose: RDP
Definition For Definition, enter: LadderLogic, CDP address
where TLL is configured
For further information on how to configure external display access, refer to the
AdvaBuild Environment Builder User’s Guide.
3BUR001981R0201 35
Templets for Nodes/Controllers That Execute TLL Section 2 Configuration Requirements for TLL
Templets for Nodes/Controllers That Execute TLL

Figure 6 shows the templet hierarchy for the TLL portion of the SC controller or
Turbo Node data bases. The templets are explained in the sections that follow.
Controller or
Generic DPSS
Other Templets for the

Turbo Node or Controller CCF (and its children) Ladder Logic Device
Ladder Ladder Ladder Ladder Ladder Ladder Ladder

Logic Logic Logic Logic Logic Logic Logic
I_O Counter Register Message Timer File Sequence
Ladder
Logic
Seq_I_O
Figure 6. Templet Hierarchy for the TLL Templets
Ladder Logic Device Templet

The Ladder Logic Device templet (LL_DEV), Figure 7, defines the basic
parameters for TLL execution in a node or controller. It is the top templet for TLL;
the other TLL related templets are its children.
36 3BUR001981R0201
Section 2 Configuration Requirements for TLL Ladder Logic Device Templet
Figure 7. Ladderlogic_Device Templet
Entries to the following fields are required:
TEMPLET NAME Field

Give the templet a name that contains up to 12 characters. The name must be unique
system-wide. It becomes the name of the TLL package in the node. Although the
configurator allows you to begin the templet name with a number, it is
recommended that the first character be a letter. This is for compatibility with other
applications in the system.
When you create a Device Directory for TLL, you use this name to identify TLL
processing in this node or controller.
SCAN RATE IN MSEC Field

This field specifies the scan (processing) rate for the TLL segments. All TLL
segments in the node or controller are processed periodically at the scan rate. When
a scan begins, the segment with the lowest segment number is scanned first,
followed by the other segments in segment number order. At the beginning of the
next scan interval, the process repeats.
Valid entry is:
3BUR001981R0201 37
Ladder Logic Device Templet Section 2 Configuration Requirements for TLL
n a number of milliseconds. The fastest possible scan rate is 20 mSec.

The slowest is 1000. The entry must be a multiple of 10, that is, 20,
30, 40, and so on. (Default value: 50)
MAXIMUM # OF SEGMENTS Field

This field specifies the highest segment number that you can use when you create a
segment. This value also determines the maximum number of segments allowed in
the node or controller at any one time (provided that you number the segments
contiguously).
Valid entry is:
n an integer number. (Default value: 100)
AUTO LOAD DEVICE Field

This field specifies the name of the Turbo Node from which segments are loaded
into this node or controller. This is the node in which TLL development software
resides. It is usually in the node that contains the Configurator. However, TLL can
be loaded into a different Turbo Node in your system.
This loading includes both operator loading and auto loading.
The auto load list specifies the segments automatically downloaded to this node or
controller upon bootup. You create this list through the Device Directory Display.
On this list, you can specify whether TLL processing starts automatically or if the
processing must be started from the Segment Display.
Valid entry is:
The templet name of the Generic_DPSS templet of the Turbo Node where the
TLL development software resides. (There is no default, an entry must be
made)
38 3BUR001981R0201
Section 2 Configuration Requirements for TLL Ladder Logic I/O Templet
Ladder Logic I/O Templet

The Ladder Logic I/O templet (LL_I_O), Figure 8, specifies the I/O points from
MOD 300 Controllers, Multibus I/O, Taylor Remote I/O (TRIO), and PLCs that are
used by the ladder programs in the node or controller. The templets for defining
S800 and PROFIBUS I/O for TLL are described in Ladder Logic Templets for S800
and PROFIBUS I/O on page 42.
A description of I/O points and their use in programs is provided in TLL Data
Structures on page 67.
For ladder logic I/O points that use PLC functionality, only inputs
are supported. PLC outputs are not supported by TLL.
Each input or output point must be specified by one row of entries in the NAME,
VENDOR, LAN, BLOCK, CH #, DESCRIPTION, TYPE, and INITOUT fields. Up
to 16 points can be specified on one templet. If you need more than 16 points, use
additional templets.
Figure 8. Example of a Ladderlogic_I_O Templet
3BUR001981R0201 39
Ladder Logic I/O Templet Section 2 Configuration Requirements for TLL
Entries for the fields are described below.
TEMPLET NAME Field

system-wide. The following characters ARE NOT allowed: single quote (‘), double
quote (“), backslash (\), comma (,), period (.), and a space.
EXPORT Field
This field is only used if you are using multiple configurators and items in other
configurator domains reference this unit. The entry to this field is a string of
numbers listing the higher order bits of the configurator data processors to receive
the export data. For example, the entry
EXPORT: 125B
specifies the data is to go to configurators at addresses 11, 21, 51, and B1.
On Multibus Turbo Nodes, the templet information goes into the Export Source File
when you select the EXPORT SAVE softkey.
A description of the Export feature is provided in the System Configurator's User’s
Guide (for Multibus Turbo Nodes), the AdvaBuild Basic Functions User’s Guide
(for HP-UX Advant Stations), or the AdvaBuild for Windows 2000 Control Builder
User’s Guide (for Windows-based Engineering Stations).
Each I/O point is specified by parameters in the following fields:
NAME Field
Assign an identifier to the point through this field. You use this name to refer to the
point on other templets or in programs. For instance, this is the name you use in the
I/O Point Name field of the Sequence I/O templet (Entries for the Ladder Logic Seq
I/O Templet on page 57). The name can have a maximum of 12 characters and must
be unique system-wide.
VENDOR Field
This field identifies the source of the I/O. Possible entries are:
40 3BUR001981R0201
Section 2 Configuration Requirements for TLL Ladder Logic I/O Templet
CONTROLLER Controller direct I/O

BURR/BROWN Multibus I/O
PLC I/O Programmable controller inputs
REMOTE I/O TRIO
CUSTOM I/O Special applications
LAN Field
When the VENDOR entry is either CUSTOM, REMOTE I/O or S100 I/O, you use
this field to specify the Local Area Network (Field Bus) number of the module that
contains the point. It can be 1 or 2 for a controller or 1 to 6 for a Turbo Node.
BLOCK Field
When the VENDOR entry is either CUSTOM, REMOTE I/O or S100 I/O, you use
this field to specify the TRIO module containing the point. Modules are numbered
from 1 to 30.
CH# Field
This field specifies the channel number of the I/O point. The I/O point must be
referenced by only one ladder logic point.
DESCRIPTION Field
This field allows you to enter a descriptor of up to 20 characters for the point.
TYPE Field
The possible entries are:
COIL Output point
CONTACT Input point
3BUR001981R0201 41
Ladder Logic Templets for S800 and PROFIBUS I/O Section 2 Configuration Requirements for TLL
INITOUT Field
This field specifies the commands to be sent to the coils (outputs) upon
downloading. Possible entries are:
ON
OFF
NONE
Ladder Logic Templets for S800 and PROFIBUS I/O

Two template types are required to support S800 and PROFIBUS I/O for TLL. They
are the Ladder Logic I/O Group templet (Ladder Logic I/O Group Templet on page
42) and Ladder Logic I/O 2 templet (Ladder Logic I/O_2 Templet on page 43).
Ladder Logic I/O Group Templet

The Ladder Logic I/O Group templet (LLIO_GRP), Figure 9, is the parent object
for the templets that represent individual S800 and PROFIBUS I/O channels
(LL_I/O_2 templets). You can insert up to 32 LL_I/O_2 templets under one I/O
Group templet. Therefore, one I/O Group templet is required for every 32 S800 I/O
channels.
Figure 9. Ladder Logic I/O Group Templet
42 3BUR001981R0201
Section 2 Configuration Requirements for TLL Ladder Logic I/O_2 Templet
TEMPLET NAME Field

DESCRIPTION Field
You can use this field to enter an optional description.
Ladder Logic I/O_2 Templet

One Ladder Logic I/O_2 templet (LL_I_O_2), Figure 10, is required for each S800
and PROFIBUS I/O channel. These templets are children of a Ladder Logic Group
I/O templet (up to 32 per group).
Figure 10. Ladder Logic I/O_2 Templet
The following subsections describe the entries for the fields of the Ladder Logic
I/O_2 templet.
3BUR001981R0201 43
Ladder Logic I/O_2 Templet Section 2 Configuration Requirements for TLL
TEMPLET NAME Field

Note that the templet name is used to refer to the point on other templets or in
programs. For instance, this is the name you use in the I/O POINT NAME field of
the Sequence I/O templet (Entries for the Ladder Logic Seq I/O Templet on page
57).
EXPORT Field
EXPORT: 125B
DESCRIPTION Field
You can enter an optional descriptor of up to 20 characters for the point.
VENDOR Field
This field identifies the source of the I/O. The only valid entries are:
S800 I/O S800 I/O
PROFIBUS I/O PROFIBUS I/O. This vendor type is only available for
Advant Controller 460 subsystems configured on the
44 3BUR001981R0201
Section 2 Configuration Requirements for TLL Ladder Logic Timer Templet
Windows platform using the AdvaBuild Control

Builder version 3.2 or higher software.
CHANNEL PATH Field

For S800 I/O, use this field to specify the LAN, station, cluster, position, and
channel of the I/O point. Each part of the path is separated by a period. For example,
1.10.0.4.10 is LAN 1, station 10, cluster 0, position 4, channel 10.
For PROFIBUS I/O, use this field to specify the LAN, device, module, and channel
of the I/O point. Each part of the path is separated by a period. For example, 1.2.5.1
is LAN 1, device 2, module 5, channel 1.
TYPE Field
The possible entries are:
COIL Output point
CONTACT Input point
INITIAL OUTPUT Field

This field specifies the commands to be sent to the coils (outputs) upon
downloading. Possible entries are:
ON
OFF
NONE No command
Ladder Logic Timer Templet

The Ladder Logic Timer templet (LL_TIMER), Figure 11, is used to configure up
to 25 timers for the ladder programs in the node or controller. If more than 25 timers
are needed, you can generate multiple templets.
A description of timers and their use in programs is provided in TLL Data
3BUR001981R0201 45
Ladder Logic Timer Templet Section 2 Configuration Requirements for TLL
Figure 11. Example of a Ladderlogic_Timer Templet
TEMPLET NAME Field

EXPORT Field
EXPORT: 125B
46 3BUR001981R0201
Section 2 Configuration Requirements for TLL Ladder Logic Timer Templet

Each timer is specified by parameters in the following fields:
TIMER NAME Field

Assign an identifier to the timer through this entry. You use this name to refer to the
timer in programs. The name can have a maximum of 12 characters and must be
unique system-wide.
DESCRIPTION Field
This field allows you to enter a timer descriptor of up to 20 characters.
TIME BASE Field

This field defines the resolution of the timer in seconds. Increments to the timer are
performed in terms of this time base. The possible entries are:
1.0
0.1
0.01
PRESET Field
This field specifies a preset value. Be sure that it is within the resolution of the
TimeBase entry.
Down timers start at the preset value and time down to 0. Up timers time from 0 to
the preset value.
The number you enter must be an integer. The system treats it as a multiple of the
time base. For example, if the time base field contains 0.01, and you want the preset
time to be 20 seconds, you must enter 2000 into the PRESET field.
3BUR001981R0201 47
Ladder Logic Counter Templet Section 2 Configuration Requirements for TLL
UP OR DOWN Field
Use the words UP or DOWN to specify the type of timer.
Ladder Logic Counter Templet

The Ladder Logic Counter templet (LL_CNTR), Figure 12, is used to configure up
to 25 counters for the ladder programs in the node or controller. If more than 25
counters are needed, you can generate multiple templets.
A description of counters and their use in programs is provided in TLL Data
Figure 12. Example of a Ladderlogic_Counter Templet
Entries for the fields of the Ladder Logic Counter templet are described below.
48 3BUR001981R0201
Section 2 Configuration Requirements for TLL Ladder Logic Counter Templet
TEMPLET NAME Field

EXPORT Field
EXPORT: 125B
Each counter is specified by parameters in the following fields:
NAME Field
Assign an identifier to the counter through this entry. You use this name to refer to
the counter in programs. The name can have a maximum of 12 characters and must
be unique system-wide.
DESCRIPTION Field
This field allows you to enter a counter descriptor of up to 20 characters.
PRESET Field
This field specifies a preset value that the counter either counts up to or down from.
3BUR001981R0201 49
Ladder Logic Register Templet Section 2 Configuration Requirements for TLL
Ladder Logic Register Templet

The Ladder Logic Register templet (LL_REG), Figure 13, is used to configure up to
25 registers that can be used by the ladder programs in the node or controller. If
more than 25 registers are needed, you can generate multiple templets.
A description of registers is provided in TLL Data Structures on page 67. Registers
are either required for, or provide optional features for math, file, and sequencer
instructions.
Figure 13. Example of a Ladderlogic_Register Templet
Entries for the fields of the Ladder Logic Register templet are described below.
TEMPLET NAME Field

50 3BUR001981R0201
Section 2 Configuration Requirements for TLL Ladder Logic Register Templet
EXPORT Field
EXPORT: 125B
Each register is specified by parameters in the following fields:
REGISTER NAME Field

You assign an identifier to the register through this entry. You use this name to refer
to the register in programs. The name can have a maximum of 12 characters and
must be unique system-wide.
DESCRIPTION Field
This field allows you to enter a descriptor of up to 20 characters for the register.
INITIAL VALUE Field

This field specifies an initial value for the register. It goes into effect when the
system is downloaded.
3BUR001981R0201 51
Ladder Logic Message Templet Section 2 Configuration Requirements for TLL
Ladder Logic Message Templet

The Ladder Logic Message templet (LL_MSG), Figure 14, is used to configure up
to 25 messages to be used by the ladder programs in the node or controller. If more
than 25 messages are needed, you can generate multiple templets.
A description of messages appears in TLL Data Structures on page 67. Messages
are sent out by TLL programs when a message instruction is executed.
Figure 14. Example of a Ladderlogic_Message Templet
Entries for the fields of the Ladder Logic Message templet are described below.
TEMPLET NAME Field

Each message is specified by parameters in the following fields:
52 3BUR001981R0201
Section 2 Configuration Requirements for TLL Ladder Logic Message Templet
MESSAGE NUMBER Field

An index number that can be in the range of 0 to 65535. It is used to identify which
message a message instruction is to send.
Use message number 0 to define the unit for TLL load error messages.
MESSAGE TEXT Field

Up to 40 characters of message text
UNIT ID Field
This field assigns the message to a unit. This allows the message to be stored and
displayed with other messages that are assigned to the unit. The entry must be the
templet name of the Unit Master templet that created the unit. The Unit Master
templet is described in Defining Units for the TLL Messages on page 29.
PRIORITY Field
This field assigns a priority to the message. The priority level appears on message
displays and logs. Possible values are:
STANDARD
MEDIUM
HIGH
3BUR001981R0201 53
Ladder Logic File Templet Section 2 Configuration Requirements for TLL
Ladder Logic File Templet

The Ladder Logic File templet (LL_FILE), Figure 15, defines a file for use by the
programs in the node or controller. A file is a one-dimension array with up to 128
values.
A description of files is provided in TLL Data Structures on page 67.
Figure 15. Example of a Ladderlogic_File Templet
TEMPLET NAME Field

Each item in the file is specified by parameters in the following fields:
54 3BUR001981R0201
Section 2 Configuration Requirements for TLL Ladder Logic File Templet
ITEM Field
This is an index number for the value. It can be from 1 to 128.
VALUE Field
The value for the item. The entry can be made in the form of a base 10 integer, from
0 to 4,294,967,295. During TLL execution, the sequencer instructions translate the
entry into a bit pattern to load into or compare with I/O points.
DESC Field
This field allows you to enter a descriptor of up to 20 characters for the item. It is for
your convenience only. It appears on templet listings, but does not become part of
the data base.
If you are using the AdvaBuild Templet Builder on the HP-UX

platform to configure your database, note that the ITEM, VALUE,
and DESCRIPTION entries comprise one field. When you enter an
item number, you must use the spacebar to make the first character
of the value line up with the V in the VALUE header. Pressing the
Tab key will start a new line for the next item.
3BUR001981R0201 55
Ladder Logic Sequences Section 2 Configuration Requirements for TLL
Ladder Logic Sequences

A sequence can contain as many as 128 steps. Each step is a list of up to 32 I/O
points. When a sequencer instruction is executed, the I/O points listed in a
sequencer step are manipulated in one way or another. A description of sequences is
provided in TLL Data Structures on page 67.
To define a sequence, you first produce one Ladder Logic Sequence templet
(LL_SEQ), Figure 16, to create and name the sequence. Then you make as many as
128 Ladder Logic Seq I/O templets to define the steps of the sequence. There can be
more than one sequence in a node or controller.
Figure 16. Example of a Ladderlogic_Sequence Templet
Entries for the Ladder Logic Sequence Templet

There are two entries for the Ladder Logic Sequence templet.
TEMPLET NAME Field

DESCRIPTION Field
This field allows you to enter a descriptor for the sequence.
56 3BUR001981R0201
Section 2 Configuration Requirements for TLL Ladder Logic Sequences
Entries for the Ladder Logic Seq I/O Templet

Each Ladder Logic Sequence I/O templet (LL_SEQIO), Figure 17, defines one step
for the sequence. You may use as many of these as you need to define the sequence.
The step numbers must be contiguous; do not leave gaps. You can configure the
templets in any order as long as you have one for each step.
Figure 17. Example of a Ladderlogic_Seq_I_O Templet
TEMPLET NAME Field

system-wide.
STEP NUMBER Field

This field specifies the step number that is being defined by the templet.
The I/O points that make up the step are specified in the edit window of the templet.
Each point requires entries to the following fields:
3BUR001981R0201 57
CCF Templet Section 2 Configuration Requirements for TLL
ITEM Field
This entry is the item number for the I/O points. It can be from 1 to 32. During
runtime the points are manipulated in this order. The item numbers do not have to
be contiguous. You can leave gaps if you want.
I/O POINT NAME Field

This entry identifies the I/O point. The name that is entered into this field must be
the name assigned to the point on the Ladder Logic I/O templet. The points must be
local to the node or controller.
CCF Templet
A CCF templet is required in the Turbo Node or controller that executes TLL for
proper internal functioning of TLL. Be sure to configure this templet even if CCF is
not going to execute in this node or controller.
How to Access TLL Variables from CCF FCMs

During runtime, CCF FCMs and Device Loop input sources can acquire the values
of the AC attribute of TLL I/O points, timers, counters, and registers.
The referencing is specified when CCF is configured. To make a TLL item the
source of a variable for an FCM, make an entry to the proper input source field of
the FCM templet in the format:
tag.LL
where tag is the name given to the TLL item when it was configured and LL
specifies that it is a TLL tag.
Example:
INPUT SOURCE 1 CNT1.LL
INPUT SOURCE 2 CNT2.LL
Since LL is reserved as a keyword to indicate TLL, do not use LL as an FCM name.
When the input source is an I/O point, the value of both the AC and the DQ (Data
Quality) attributes are accessed. The FCM uses these values in the standard manner.
58 3BUR001981R0201
Section 2 Configuration Requirements for TLL Console Configurator
Specifically, the AC is used in the FCM calculation. The DQ is checked and used by
the Bad Inputs Accepted feature.
Console Configurator
When you configure an environment with the Console Configurator, there are a
number of ways in which you specify how users can interact with the TLL
structures. This section describes those items.
How to Put TLL Information Onto Standard Runtime Displays

Information for TLL I/O points, counters, timers, and registers can be put onto the
standard CCF and TCL Runtime Displays. This is accomplished when you
configure the console groups. A TLL item is assigned to a group by entering the
name of the item into one of the controller (C) blocks on the Group Definition
Display. For Multibus nodes, see the Console Configurator User's Guide for details,
and for HP-UX Advant Stations see the AdvaBuild Environment Builder User’s
Guide for details. For Windows-based Operator Stations, see the Operate IT
Operation Manual Add-On for Advant OCS with MOD 300.
During runtime, information for the TLL items appears in the status blocks on the
Group and Unit Displays. Some information also appears on the Area Status
Display and the Group Status Display.
How to Put TLL Display Callup Blocks on Overview Displays/PSAPs

The console configurator allows you to configure Overview Display blocks and
PSAP buttons to call up TLL Displays.
If you want a block on an overview that can be used to call up the Device Directory,
choose the RDP menu when you configure the block. Then enter the name
LADDERLOGIC into the NAME field on the menu. No parameters are required.
You can also configure a block to call up any one of the following types of Console
Resident TLL Displays:
Runtime Segment Counter Displays Sequencer Displays
I/O Point Display Register Displays
Timer Displays Data File Displays
3BUR001981R0201 59
User Security for TLL Runtime Displays Section 2 Configuration Requirements for TLL
The procedures required to accomplish this are provided in the Console

Configurator User’s Guide (for Multibus nodes), the AdvaBuild Environment
Builder User’s Guide (for HP-UX Advant Stations), and the Operate IT Operation
Manual Add-On for Advant OCS with MOD 300 (for Windows-based Operator
Stations).
User Security for TLL Runtime Displays

When you configure an environment, you can specify which categories of users can
make entries to the different types of TLL Displays. Each of the classes of TLL
Displays that are named in How to Put TLL Display Callup Blocks on Overview
Displays/PSAPs on page 59 appear on the appropriate Runtime Authority Display
(Multibus-based node), Authority Definition dialog (HP-UX Advant Station), or
Security tab of the System Definition object (Windows-based Operator Station)
with a default authority of Engineer. If you leave a display category at this default,
only engineers can make entries to the display. If you change the authority to
Supervisor, both supervisors and engineers can make entries. If you change the user
category to Operator, all three user classes are allowed to make changes.
The procedures to accomplish this are provided in the Console Configurator User’s
Guide (for Multibus consoles), the AdvaBuild Environment Builder User’s Guide
(for HP-UX Advant Stations), and the Operate IT Configuration Manual Add-On
for Advant OCS with MOD 300 (Windows-based Operator Stations).
60 3BUR001981R0201
Section 3 Program Structure and Program
Instructions
General Information
This section describes the format of the programs, data structures, and program
instructions used by TLL. You should be familiar with the information in this
section before attempting to configure the system or write ladder segments.
Program Structure
When you produce the TLL program for a node or controller you do it by creating a
group of smaller program units called segments. Figure 18 shows part of a segment.
Each segment has a segment number which determines the execution order. When
the scan starts, the segment with the lowest segment number is executed first,
followed by the segment with the next lowest number. The process continues until
all segments have been executed. It repeats at the next scan.
You have a great deal of flexibility in determining the contents of the segments. You
may write some segments that execute one limited task, or you may decide to make
some segments more complicated.
A segment is a sequence of rungs. Figure 19 gives the details of a single line rung.
The rung starts and ends at the power rails. It contains up to eight elements
identified by IN1 through IN7 and OUT. The element at position eight, OUT, has
special constraints. It must always be present and it must contain an output-type
instruction. Position eight is the only place that output type instructions are allowed.
3BUR001981R0201 61
Program Structure Section 3 Program Structure and Program Instructions
REG_1 REG_2
[G] (PUT)
REG_1 REG_2 DAMPER_1

[G] [>] ()

[G] [=] ()
DI1 DI2
][ ]/[
Figure 18. Example of Ladder Structure
IN1 IN2 IN3 IN4 IN5 IN6 IN7 OUT
B1 B2 B3 B4 B5 B6 B7 B8
Power rail Power rail
Figure 19. Details of a Single Line Rung
The power flow (execution order) in a rung is always from left to right. Rungs are
processed in sequence from top to bottom.
For clarity, the diagrams in the remainder of this manual do not attempt to show all
eight positions.
62 3BUR001981R0201
Section 3 Program Structure and Program Instructions Program Structure
You can think of the elements in positions IN1 to IN7 of a rung as a logical AND
expression that determines if the output function in the position eight element
(OUT) is performed or not. For example, in the rung

[G] [>] ()
the instructions
REG_1 REG_2
[G] [>]
make up the logical AND, while
DAMPER_1
()
is an output type instruction. When the AND evaluates to 1, the output function is
performed. When the AND evaluates to 0, it is not performed. In either case, power
flow goes to the next rung in the sequence.
It is possible to have multi-line rungs as Figure 20 demonstrates. This structure is
called a branch.

[G] [=] ()
DI1 DI2
][ ]/[
Figure 20. A Multi-Line Rung
3BUR001981R0201 63
The lines in a branch act as a logical OR. For example, in the following branch:
REG_1 REG_2
[G] [=]
DI1 DI2
][ ]/[
the system passes on a logical 1 from the branch if either the logic in the upper line
REG_1 REG_2
[G] [=]
or the logic in the lower line
DI1 DI2
][ ]/[
evaluates to 1.
Branches must end before the eighth element. The valid positions on a rung where a
branch may begin or end are identified as B1 through B8 in Figure 19. There can be
more than two lines in a branch. The maximum number of lines in a branch is 19.
Figure 21 and Figure 22 illustrate the valid and invalid branch configurations.
64 3BUR001981R0201
Section 3 Program Structure and Program Instructions Program Structure
Figure 21. Valid Branch Configurations
3BUR001981R0201 65
Figure 22. Non-Valid Branch Configurations
66 3BUR001981R0201
Section 3 Program Structure and Program Instructions TLL Data Structures
TLL Data Structures

TLL programs make use of several types of data structures such as timers and
registers. The structures are initially set up when you configure the system. They are
manipulated by the TLL program elements during runtime. They can interact with
other software structures in several ways:
• You can monitor and change their values via the TLL Data Device Data
Summary Displays.
• You can access their values from CCF loops. Instructions are in How to Access
TLL Variables from CCF FCMs on page 58.
• You can access their parameters from TCL programs. Instructions are in
Interface with TCL on page 93.
• You can place their values on standard TCL and CCF Runtime Displays.
Instructions are in How to Put TLL Information Onto Standard Runtime
Displays on page 59. Instructions for manipulating these values through the
standard Multibus-based displays are in TLL Items on CCF and TCL Displays
on page 162.
• You can put their values on User Displays built with the Display Builder.
Instructions are in Interface with Display Builder on page 94.
I/O Points
TLL uses digital input (contact) and output (coil) points that are local to the
controller or node. For a coil, you can configure an initial output to be in effect upon
bootup. You must define the I/O points for your TLL package via the Ladder Logic
I/O templet as described in Ladder Logic I/O Templet on page 39. The data base
contains the following attributes for each I/O point:
NAME As assigned through the Ladder Logic I/O templet
DESC Descriptor for the point
AC I/O value:
0 open for a contact, off for a coil
nonzero closed for a contact, on for a coil
3BUR001981R0201 67
Counters Section 3 Program Structure and Program Instructions
FORCE Whether the I/O is being forced:

0 not forced
1 forced, user at console is allowed to change
the state (AC value) of the point. This affects
the value in the program only. The real value in
the field is not changed.
TYPE Type of I/O point:
0 input
1 output
DQ Data quality of point:
0 bad
1 good
For ladder logic I/O points that use PLC functionality, only inputs
are supported. PLC outputs are not supported by TLL.
Counters
TLL counters can count by increments of one. Instructions in the programs can
cause them to count up or down, reset, or go to their configured preset values.
Counters can count as high as 2,147,483,647.
You can define counters via the Ladder Logic Counter templet as described in
Ladder Logic Counter Templet on page 48. Counters are required by a number of
instructions such as file instructions and sequencer instructions.
The data base contains the following attributes for each counter:
NAME As assigned through the Ladder Logic Counter
templet
DESC Descriptor for the counter
AC Current value of the count
PR Preset value. Down counting starts at PR and is finished
when AC = 0. Up counting starts at 0 and is finished
when AC = PR.
68 3BUR001981R0201
Section 3 Program Structure and Program Instructions Timers
EN Counter enable:
0 disabled
1 enabled
DN Count indicator:
0 count not complete
1 count complete
Timers
TLL timers can time with a configurable time base that can be either 1.0, 0.1, or
0.01 seconds. The timers are under program control and can be started, stopped and
reset by program instructions. They can time to values as large as 999 hours. When
you configure a timer, you determine whether it times up or down. You can define
timers via the Ladder Logic Timer templet as described in Ladder Logic Timer
Templet on page 45.
The data base contains the following attributes for each timer:
NAME As assigned through the Ladder Logic Timer
templet
DESC Descriptor for the timer
AC Timer value in time base units
PR Timer preset value in time base units. Up timers start at
0 and are timed out when AC = PR. Down timers start at
PR and are timed out when AC = 0.
EN Timer enable:
0 disabled
1 enabled
T_BASE Time base:
0 1.0 seconds
1 0.1 seconds
2 0.01 seconds
3BUR001981R0201 69
Registers Section 3 Program Structure and Program Instructions
UPDOWN Up or down indicator:

0 up
1 down
DN Timing indicator:
0 timing not complete
1 timing complete
Registers
TLL registers are places in memory that are used to store values. They are used in
several types of program instructions which include:
• Data manipulation instructions
• Math instructions
• File instructions
• Sequencer instructions
You can define registers via the Ladder Logic Register templet as described in
Ladder Logic Register Templet on page 50.
The data base contains the following attributes for each register:
NAME As assigned through the Ladder Logic Register
templet
DESC Descriptor
AC Current value in register
Messages
TLL allows you to configure a set of messages that can be sent to consoles, loggers,
and historical recorders during runtime. Each time a TLL program executes a
message instruction, a selected message is sent to the message receivers. A message
can contain up to 40 characters of text and is assigned to a particular unit. When the
message arrives at a message receiver, it is grouped and processed with other
messages for the unit.
70 3BUR001981R0201
Section 3 Program Structure and Program Instructions Files
For example, the console can display either all messages or the most recently
arrived messages for a unit on the Unit Message, Sequence Detail, and Unit Detail
Displays. Similarly, the historical recorder groups messages by units when it stores
them on disk.
The text for the messages is configured on the Ladder Logic Message templet as
described in Ladder Logic Message Templet on page 52. The loggers, consoles, and
historical recorders receiving the messages are specified on the Configuration Area
templets as described in TLL Message Configuration on page 28. The message
instruction is described in Miscellaneous Instructions on page 89.
Files
A TLL file is a one-dimensional array with 128 values. These values are held as
base 10 integers; however, some program instructions translate these integers into
bit patterns. For example, a sequencer output instruction translates the values in a
file into bit patterns to be output to the I/O points. If item 10 in the file contains 21,
the 21 is treated as 10101 when it is output to the I/O.
You define files via the Ladder Logic Files templet as described in Ladder Logic
File Templet on page 54.
Sequencers
A sequencer is a series of up to 128 steps. Each step is a list of as many as 32 I/O
points. The I/O points listed in a sequencer step are manipulated in one way or
another by sequencer program instructions. One type of sequencer instruction
causes the values of input points to be read into a file. Another instruction causes the
values in a file to be sent to output points. The details of the sequencer instructions
appear in Sequencer Instructions on page 88.
You define sequencers via the Ladder Logic Sequence templet and Ladder Logic
Sequence I/O templet as described in Ladder Logic Sequences on page 56. Each
sequencer is assigned items such as those that appear in the example of a three-step
sequencer in Figure 23. You assign a name to the sequencer via the TEMPLET
NAME field of its Ladder Logic Sequence templet.
You can also assign a descriptor to the sequencer. The sequencer in Figure 23
required three Ladder Logic Seq I/O templets, one for each of its steps. Each step
3BUR001981R0201 71
Sequencers Section 3 Program Structure and Program Instructions
has a step number and a list of up to 32 I/O points. The names that appear for the I/O
points are the names you assigned them via the Ladder Logic I/O templet.
NAME: RUN_SEQ1
DESCRIPTOR: UNIT_1_SEQUENCE
STEP 1
1 UN1-COIL1
2 UN1-COIL2
3 UN1-COIL3
4 UN1-COIL4
5 UN1-COIL5
STEP 2
1 UN2-COIL1
2 UN2-COIL2
3 UN2-COIL3
4 UN2-COIL4
5 UN2-COIL5
6 UN2-COIL6
7 UN2-COIL7
8 UN2-COIL8
STEP 3
1 UN3-COIL6
2 UN3-COIL7
3 UN3-COIL8
4 UN3-COIL9
5 UN3-COIL10
6 UN3-COIL11
Figure 23. Sequencer Example
72 3BUR001981R0201
Section 3 Program Structure and Program Instructions TLL Program Instructions
TLL Program Instructions

A TLL segment consists of a series of instructions that manipulate the data
structures that are described in the previous section. TLL contains a complete set of
the instructions to implement ladder functions. These instructions are described in
this section. For information on building programs from these instructions see the
AdvaBuild for Windows 2000 TLL Builder User’s Guide or Appendix A, Multibus-
based Program Development and Maintenance
Relay Instructions
The relay instructions are used to energize, latch, or examine the status of outputs,
examine the status of inputs, and to provide branch paths in the ladder logic rungs.
-] [- Examine On
The Examine On instruction tests that a input or output is energized, Figure 24. If it
is energized, the instruction produces a TRUE value which affects the way the rest
of the rung or branch line is scanned. When you enter this instruction into a
program, you choose what is displayed with the symbol during runtime. If you
choose AC, you see whether the contact is On or Off. If you choose DQ, you see
whether the data quality of the input is Good or Bad.
G_VALVE_L ESD DAMPER_1

][ ]/[ ()
Figure 24. Example of Examine On Instruction
-]/[- Examine Off

The Examine Off instruction tests that an input or output is de-energized. If it is de-
energized, the instruction produces a TRUE value which affects the way the rest of
the rung or branch line is scanned.
3BUR001981R0201 73
Relay Instructions Section 3 Program Structure and Program Instructions
-( )- Output Energize
The Output Energize instruction energizes or turns on the referenced output if the
rung condition is TRUE, otherwise it de-energizes the output. This is an output-type
instruction which must appear in the element 8 position on the rung.
-(L)- Output Latch

The Output Latch instruction energizes and latches the referenced contact output if
the rung condition is TRUE, otherwise it takes no action. This is an output-type
instruction which must appear in the element 8 position on the rung, Figure 25.
DAMPER_1 DAMPER_2 G_VALVE

][ ][ (L)
DAMPER_3
][
Figure 25. Example of Output Latch Instruction
-(U)- Output Unlatch

The Output Unlatch instruction de-energizes and unlatches the referenced output if
the rung condition is TRUE, otherwise it takes no action. This is an output-type
DAMPER_1 G_VALVE
]/[ (U)
Figure 26. Example of Output Unlatch Instruction
74 3BUR001981R0201
Section 3 Program Structure and Program Instructions Data Manipulation Instructions
Data Manipulation Instructions

The data manipulation instructions allow the ladder logic program to access the
values of AC or PR in registers, timers, or counters and use them in relational
comparisons to determine continued execution of a rung. The records that are
required by these instructions are described in TLL Data Structures on page 67.
-[G]- Get
The Get instruction fetches the contents of the referenced record for use by
subsequent instructions of the rung, Figure 27.
REG_1 REG_2
[G] (PUT)
Figure 27. Example of Get Instruction
-[GET]- Get Data Base

The Get Data Base instruction fetches the contents of the referenced data base
variable, Figure 28. The variable must be in the controller or turbo node that
executes the TLL segment. The value is converted to integer, if it is not already in
integer format.
TI101 REG_2 DAMPER_1

[GET] [>=] ()
MEASURE
Figure 28. Example of Get Data Base Instruction
-[PUT]- Put
The Put instruction puts the value obtained from the previous get or get data base
instruction into the referenced register. This is an output-type instruction which
must appear in the element 8 position on the rung, Figure 29.
3BUR001981R0201 75
Data Manipulation Instructions Section 3 Program Structure and Program Instructions
REG_1 REG_2
[G] (PUT)
Figure 29. Example of Put Instruction
-[=]- Compare Equal

The Compare Equal instruction compares the value from the preceding get or get
data base instruction with the value in the referenced register, Figure 30. If they are
equal, the instruction produces a TRUE for subsequent processing on this rung of
the program.

[G] [=] ()
Figure 30. Example of Compare Equal Instruction
-[<]- Compare Less Than

The Compare Less Than instruction compares the value from the preceding get or
get data base instruction with the value in the referenced register, Figure 31. If the
get value is less than the register value, the instruction produces a TRUE for
subsequent processing on this rung of the program.

[G] [<] ()
Figure 31. Example of Compare Less Than Instruction
76 3BUR001981R0201
Section 3 Program Structure and Program Instructions Data Manipulation Instructions
-[>]- Compare Greater Than

The Compare Greater Than instruction compares the value from the preceding get
or get data base instruction with the value in the referenced register, Figure 32. If
the get value is greater than the register value, the instruction produces a TRUE for
subsequent processing on this rung of the program.

[G] [>] ()
Figure 32. Example of Compare Greater Than Instruction
-[<=]- Compare Less Than or Equal To

The Compare Less Than or Equal To instruction compares the value from the
preceding get or get data base instruction with the value in the referenced register,
Figure 33. If the get value is less than or equal to the register value, the instruction
produces a TRUE for subsequent instructions on this rung of the program.

[G] [<=] ()
Figure 33. Compare Less Than or Equal To Instruction
-[>=]- Compare Greater Than or Equal To

The Compare Greater Than or Equal To instruction compares the value from the
preceding get or get data base instruction with the value in the referenced register,
Figure 34. If the get value is greater than or equal to the register value, the
instruction produces a TRUE for subsequent processing on this rung of the program.
3BUR001981R0201 77
Math Instructions Section 3 Program Structure and Program Instructions
TI101 REG_2 DAMPER_1

[GET] [>=] ()
MEASURE
Figure 34. Example of Compare Greater Than or Equal To Instruction
Math Instructions
The math instructions perform the basic math operations of addition, subtraction,
multiplication, and division of integer numbers. The numbers used by the operations
come from the two previous get or get data base instructions on the rung. The
answer is stored in a register you name when you enter the instruction. If there is an
error such as an overflow, underflow, divide by zero, and so on, the instruction
returns the largest possible integer value (2,147,483,647). The registers required by
these instructions are described in TLL Data Structures on page 67.
-(+)- Add
The Add instruction adds the values of the two preceding get instructions and places
the answer in the referenced register. This is an output-type instruction which must
appear in the element 8 position on the rung, Figure 35.
REG_1 REG_2 REG_3

[G] [G] (+)
Figure 35. Example of Add Instruction
-(-)- Subtract
The Subtract instruction requires two get instructions. The value of the second get
instruction is subtracted from the value of the first get instruction. The answer is
placed in the referenced register. This is an output-type instruction which must
78 3BUR001981R0201
Section 3 Program Structure and Program Instructions Math Instructions
REG_1 REG_2 REG_3

[G] [G] (-)
Figure 36. Example of Subtraction Instruction
-(X)- Multiply
The Multiply instruction multiplies the values of the two preceding get instructions
and places the answer in the referenced register. This is an output-type instruction
which must appear in the element 8 position on the rung, Figure 37.
REG_1 REG_2 REG_3

[G] [G] (x)
Figure 37. Example of Multiplication Instruction
-(:)- Divide
The Divide instruction divides the value of the first get instruction by the value of
the get instruction that immediately precedes the division instruction. The answer is
placed in the referenced register. This is an output-type instruction which must
REG_1 REG_2 REG_3

[G] [G] (:)
Figure 38. Example of Division Instruction
3BUR001981R0201 79
Math Instructions Section 3 Program Structure and Program Instructions
BCD -> BIN

The BCD -> BIN instruction allows up to eight BCD digits in a file to be changed to
a binary number and stored in a register. One sequence for using this instruction is:
1. A sequencer instruction loads as many as 32 digital inputs from the I/O into a
file. These inputs can represent up to 8 BCD digits.
2. The BCD to binary instruction fetches the BCD value from the file as indexed
by the counter, converts it to a binary number in the range 0 to 99,999,999, and
stores the number in a register. If any BCD digit has a value greater than 9, the
conversion is stopped and the largest positive integer value (2147483647) is
stored in the register.
You must ensure that the BCD digits are stable when the sequencer load instruction
reads them. This can be accomplished by conditioning the read with a contact that
represents a “data-ready” strobe or by the addition of latching hardware. This is an
output-type instruction which must appear in the element 8 position on the rung,
Figure 39.
LS_1
][ BCD TO BIN
CNT: C1
REG: REG3
FILE: FL33
Figure 39. Example of BCD -> BIN Instruction
GRAY -> BIN

The GRAY -> BIN instruction allows up to eight gray digits in a file to be changed
to a binary number and stored in a register.
1. A sequencer load instruction loads as many as 32 digital inputs from the I/O
into a file. These inputs can represent up to eight gray digits.
2. The BCD to gray instruction fetches the value from the file as indexed by the
counter, converts it to a binary number in the range -1,879,048,193 to
2,147,483,647, and stores the number in a register.
80 3BUR001981R0201
Section 3 Program Structure and Program Instructions Timer Instructions
If the inputs come from TRIO, you must ensure that the BCD digits are stable when
the sequencer load instruction reads them. This can be accomplished by
conditioning the read with a contact that represents a “data-ready” strobe or by the
addition of latching hardware. This is an output-type instruction which must appear
in the element 8 position on the rung, Figure 40.
LS_1
][ GRAY TO BIN
CNT: C1
REG: REG9
FILE: FL38
Figure 40. Example of GRAY -> BIN Instruction
Timer Instructions
Timer instructions allow the program to keep track of timed intervals. The
instructions perform actions based on transitions (that is, FALSE to TRUE) of the
rung conditions. The timers manipulated by these instructions are described in TLL
Data Structures on page 67.
-(TON)- Timer On
The Timer On instruction turns on a timer. After the timer runs, its accumulated
value is retained as long as the rung condition remains TRUE.
When the rung condition is TRUE:
EN =1 Timer enabled
AC Accumulator incremented with the value of the time base
DN Done indicator set to 1 when the time has timed out, that is, AC =
PR for up timers, AC = 0 for down timers
When the rung condition is FALSE:
EN = 0 Timer disabled
AC = 0 Accumulator reset
3BUR001981R0201 81
Timer Instructions Section 3 Program Structure and Program Instructions
DN = 0 Timer not timed out

This is an output-type instruction which must appear in the element 8 position on
the rung, Figure 41.
TIM1 TIM1
]/[ (TON)
EN
Figure 41. Example of Timer On Instruction
-(RTO)- Retentive Timer On

The Retentive Timer On instruction starts a timer. After the timer runs, it retains its
accumulated value.
EN = 1 Timer enabled
AC Accumulator incremented with the value of the time base
DN Done indicator set to 1 when the time has timed out, that is, AC =
PR for up timers, AC = 0 for down timers
AC Accumulator maintains its current value
LS_1 TIM3
]/[ (RTO)
Figure 42. Example of Retentive Timer On Instruction
82 3BUR001981R0201
Section 3 Program Structure and Program Instructions Counter Instructions
-(RTR)- Retentive Timer Reset

The Retentive Timer Reset instruction resets the accumulated value of a timer to 0
for an up timer or PR for a down timer.
When the rung condition becomes TRUE:
AC = 0 for an up timer, or PR for a down timer
DN = 0 Timer not timed out
No action taken
LS_1 TIM3
]/[ (RTR)
Figure 43. Example of Retentive Timer Reset Instruction
Counter Instructions
Counter instructions allow the ladder logic to keep track of counted events. The
instructions perform actions based on transitions (that is, FALSE to TRUE) of the
rung conditions. The counters manipulated by these instructions are described in
TLL Data Structures on page 67.
-(CTU)- Count Up
The Count Up instruction increments a counter.
EN = 1 Counter enabled
AC = AC + 1 Accumulator incremented by 1
3BUR001981R0201 83
Counter Instructions Section 3 Program Structure and Program Instructions
DN Done indicator set to 1 when the counter has finished, that is, AC =
PR
EN =0 Timer disabled
LS_1 CT_1
]/[ (CTU)
Figure 44. Example of Count Up Instruction
-(CTD)- Count Down

The Count Down instruction starts a downward count.
EN = 1 Counter enabled
AC = AC - 1 Accumulator decremented by 1
DN Done indicator set to 1 when the counter has finished, that is, AC =
0
EN =0 Timer disabled
LS_1 CT_2
]/[ (CTD)
Figure 45. Example of Count Down Instruction
84 3BUR001981R0201
Section 3 Program Structure and Program Instructions Counter Instructions
-(CTR)- Counter Reset

The Counter Reset instruction resets the accumulated value of a counter to 0.
EN = 0 Counter disabled
AC = 0 Accumulator reset
DN = 0 Counter not done
No action taken
CT_1 CT_1
]/[ (CTR)
DN
Figure 46. Example of Counter Reset Instruction
-(CTP)- Counter Preset

The Counter Preset instruction sets a counter to its preset value. This instruction is
usually used before starting a downward count.
EN = 0 Counter disabled
AC = PR Accumulator set to PR value
DN = 0 Counter not done
No action taken
3BUR001981R0201 85
File Instructions Section 3 Program Structure and Program Instructions
CT_1 CT_1
]/[ (CTP)
DN
Figure 47. Example of Counter Preset Instruction
File Instructions
File instructions allow the ladder logic to transfer data from registers to files, files to
registers, and from one file to another. Each instruction must have a counter
associated with it to provide an index into a file for a particular element. The
counters have to be incremented or decremented by the ladder logic to provide the
proper index for the register to file move and file to register move instructions. The
entire contents of a file is moved by the file to file move instruction. The files,
counters, and registers manipulated by these instructions are described in TLL Data
Register to File Move

The Register to File Move instruction transfers one value from the register to the
file. When the rung condition becomes TRUE, the value in the register is transferred
to the position in the file that is indexed by the present value of the counter. For
example, if the counter contains eight, the value is transferred to position 8 in the
file. When the transfer is complete, the DN indicator of the counter is set to 1 and
remains set as long as the rung is TRUE. This is an output-type instruction which
must appear in the element 8 position on the rung, Figure 48.
CT_3
][ REG TO FILE MOVE
CNT: CTR_3
REG: REG_1
FILE: DF_7
Figure 48. Example of Register to File Move Instruction
86 3BUR001981R0201
Section 3 Program Structure and Program Instructions File Instructions
File to Register Move

The File to Register Move instruction transfers one value from the file to the
register. When the rung condition becomes TRUE, the value in the position of the
file indexed by the present value of the counter is transferred to the register. For
example, if the counter contains 72, the value in position 72 of the file is transferred
to the register. When the transfer is complete, the DN indicator of the counter is set
to 1 and remains set as long as the rung is TRUE. This is an output-type instruction
which must appear in the element 8 position on the rung, Figure 49.
CT_3
][ FILE TO REG MOVE
CNT: CTR_4
REG: REG_2
FILE: DF_7
Figure 49. Example of File to Register Move Instruction
File to File Move

The File to File Move instruction transfers the entire contents of the source file to
the destination file. When the transfer is complete, the DN indicator of the counter is
set to 1 and remains set as long as the rung is TRUE. This is an output-type
CT_4
][ FILE TO FILE MOVE
CNT: CTR_5
SOURCE FILE: DF_7
DEST FILE: DF_12
Figure 50. Example of File to File Move Instruction
3BUR001981R0201 87
Sequencer Instructions Section 3 Program Structure and Program Instructions
Sequencer Instructions
Sequencer instructions allow the ladder logic to transfer data to and from the files
and the process I/O. The sequencers, counters, registers, and files manipulated by
these instructions are described in TLL Data Structures on page 67.
Sequencer Input
The Sequencer Input instruction is used to compare values from the process input
with a value in a file, Figure 51. When the rung condition becomes TRUE, the
values from the input points listed in the step of the sequencer that is indexed by the
current value of the counter are read in. These values are ANDed with the value in
the mask register and the result is compared with the value in the position of the file
indexed by the counter. If the values are equal, a TRUE rung condition is produced.
If not equal, a FALSE condition is produced.
For example, when the counter contains 9, the values of the input points listed in
step 9 of the sequencer are read in and ANDed with the contents of the register. The
result of the AND is compared with the value in position 9 of the file. If the values
are equal, a TRUE condition is produced.
SEQ INPUT SEQ OUTPUT

SEQ: SEQ_2 SEQ: SEQ_3
CNT: CT_4 CNT: CT_4
MASK: REG_1 MASK: REG_2
FILE: DF_1 FILE: DF_2
Figure 51. Example of Sequencer Input Instruction
Sequencer Output
The Sequencer Output instruction is used to output values to the field. When the
rung condition becomes TRUE, the value from the position of the file indexed by the
present value of the counter is ANDed with the value in the mask register and the
result is sent to the output points listed in the step of the sequence that is referenced
by the counter value.
88 3BUR001981R0201
Section 3 Program Structure and Program Instructions Miscellaneous Instructions
For example, when the counter contains 7, the value in the seventh position of the
file is ANDed with the contents of the register. The result of the AND is output to
the points that are listed in the seventh step of the sequence.
After the output, the EN indicator of the counter is set to 1. If the last step of the
sequencer was transferred, the DN indicator of the counter is set to 1 and remains
set as long as the rung is TRUE. This is an output-type instruction which must
appear in the element 8 position on the rung.
Sequencer Load
The Sequencer Load instruction is used to load values from the process input into a
file. When the rung condition becomes TRUE, the values from the input points
listed in the step of the sequencer that is indexed by the current value of the counter
are read into the position of the file specified by the current value of the counter. For
example, when the counter contains 9, the values of the input points listed in step 9
of the sequencer are read into position 9 of the file.
After the output, the EN indicator of the counter is set to 1. If the last step of the
sequencer was transferred, the DN indicator of the counter is set to 1 and remains
set as long as the rung is TRUE. This is an output-type instruction which must
appear in the element 8 position on the rung.
LS_4
][ SEQ LOAD
SEQ: SEQ_1
CNT: CT_3
FILE: DF_7
Figure 52. Example of Sequencer Load Instruction
Miscellaneous Instructions
The following instructions provide for conditional execution of portions of the
ladder and allow pre-configured messages to be sent to message receivers such as
loggers, consoles, and historical recorders.
3BUR001981R0201 89
Miscellaneous Instructions Section 3 Program Structure and Program Instructions
-(MCR)- Master Control Reset and -(NCR)- End of Master Control Reset
The Master Control Reset and End of Master Control Reset instructions allow a
portion of the ladder to be conditionally executed. If the rung condition is TRUE,
the statements between the MCR and NCR are executed normally. Otherwise, the
rungs are not executed and all non-retentive outputs in those rungs are de-energized.
Both MCR and NCR are output-type instructions which must appear in the element
8 position on the rung, Figure 53.
LS_1
][ (MCR)
TIM1 TIM1
]/[ (TON)
EN
TIM1 02
][ (MSG)
DN
(NCR)
Figure 53. Example of Master Control Reset and

End of Master Control Reset Instructions
-(ZCL)- Zone Control Last State and -(NCL)- End of Zone Control Last State
The Zone Control Last State and End of Zone Control Last State instructions allow
a portion of the ladder to be conditionally executed. If the rung condition is TRUE,
the statements between the ZCL and NCL are executed normally. Otherwise, the
rungs are not executed and all outputs in those rungs remain in their previous state.
Both ZCL and NCL are output-type instructions which must appear in the element 8
position on the rung, Figure 54.
90 3BUR001981R0201
Section 3 Program Structure and Program Instructions Miscellaneous Instructions
LS_2
][ (ZCL)
TIM1 TIM1
]/[ (TON)
TIM1 02
][ (MSG)
DN
(NCL)
Figure 54. Example of Zone Control Last State, Message, and

End of Zone Control Last State Instructions
-(MSG)- Message
Message instructions allows messages to be sent to the message receivers. When
you enter an MSG instruction into a ladder program, you are prompted to enter the
Message Number of the message. The messages are sent to all message receivers
that have been configured to receive TCL billboard messages from this node or
controller. This configuration is performed through the Configuration Area templet
as described in TLL Message Configuration on page 28. This is an output-type
3BUR001981R0201 91
Miscellaneous Instructions Section 3 Program Structure and Program Instructions
92 3BUR001981R0201
Section 4 Interface to Other Applications
General Information
This section describes how the other application software packages of the MOD 300
System can acquire TLL information.
Interface with CCF

CCF loops and FCMs can acquire the values of the AC attribute of TLL I/O points,
timers, counters, and registers. This access is specified in the Configurator and is
described in detail in How to Access TLL Variables from CCF FCMs on page 58.
Interface with the Console Configurator

The Console Configurator software has an extensive interface with TLL that is
described in
• How to Put TLL Information Onto Standard Runtime Displays on page 59
• How to Put TLL Display Callup Blocks on Overview Displays/PSAPs on page
59
Interface with TCL

TCL programs can acquire the values of attributes of ladder logic I/O points, timers,
counters, and registers.
The format for referencing a TLL data structure is:
%tag-type.attribute
where:
% signifies that it is a TLL element
3BUR001981R0201 93
Interface with Display Builder Section 4 Interface to Other Applications
tag is the name assigned to the item

type is the type of item
I_O I/O point
TIM timer
CNT counter
REG register
attribute is the mnemonic for the attribute. TLL Data Structures on page 67
describes the attributes and lists their mnemonics.
Example:
TEMPVAR := %TRIPCOUNT-CNT.AC;
The data base acquisition, VARTAG, and SET/FETCH mechanisms act in the same
manner as they do for CCF tags.
Ladder Logic execution does not perform event limit checks.

Therefore, database attribute values that are changed by ladder logic
execution do not trigger TCL events.
Interface with Display Builder

The syntax for database reference of TLL information on user-defined displays
using Windows is described in Operate IT Process Portal B1.0 for MOD 300
Connect 2.1 Configuration.
The Display Builder can put information for TLL I/O points, counters, timers, and
registers on user-defined displays. The format is $'tag'.attribute. The Display
Builder for Multibus nodes is described in the Display Builder User's Guide, and
the Display Builder for HP-UX Advant Stations is described in the AdvaBuild
Display Builder User’s Guide. The TLL data structures and their attributes are
described in TLL Data Structures on page 67.
The user-built displays can also contain page links to TLL displays. When you set
up one of these page links, you need to enter a keyword to identify the type of page,
and either one or two parameters.
94 3BUR001981R0201
Section 4 Interface to Other Applications Interface with Display Builder
Example:
A display link to LLIOPOINT, DEV1 would access the I/O Point Display for the
node or controller with the TLL package name DEV1. The page would come up
with the first I/O point in the top position.
A display link to LLIOPOINT, DEV1, CONTACT33 would access the same I/O
Point Display, but it would initially come up with the page scrolled so that
information for CONTACT33 is on the display. The data entry for CONTACT33
will be at the top of the display, unless the data is on the last page of information. In
that case, the complete last page of information is displayed. The two parameter
option cannot be used for the Segment Display.
The keywords for page links are:
Keyword Display Type
LLSEGDISP Segment Display
LLIOPOINT I/O Point Display
LLTIMER Timer Display
LLCOUNTER Counter Display
LLREGISTER Register Display
LLDATAFILE File Display
LLSEQUENCER Sequencer Display
3BUR001981R0201 95
Interface with Display Builder Section 4 Interface to Other Applications
96 3BUR001981R0201
Appendix A Multibus-based Program
Development and Maintenance
General Information
This section describes the Data Processor Resident Displays used to build and
maintain ladder logic segments (that is, Device Directory Display, Segment Library
Display, and Ladder Logic Editor). These displays are usually restricted so only
users in the Engineer category have the right to make entries to them. However, you
can grant user rights to Supervisors and Operators via the User Access Authority
Display on Multibus-based nodes, via the Environment Builder’s Authority
Definition dialog on HP-UX Advant Stations, and via the Security tab of the System
Definition object on the Windows-based Operator Station. The procedures to
accomplish this are provided in the Console Configurator User’s Guide (for
Multibus consoles), the AdvaBuild Environment Builder User’s Guide (for HP-UX
Advant Stations), and the Operate IT Configuration Manual Add-On for Advant
OCS with MOD 300 (Windows-based Operator Stations).
Note that the figures for the data processor resident displays in this
section are those seen on the Multibus console and emulated on the
HP-UX Advant Station. The data processor resident displays seen
on the Windows-based Engineering Station look different, but they
contain the same information. Refer to the AdvaBuild for Windows
2000 TLL Builder User’s Guide for information about the Device
and Segment Libraries and Ladder Logic Editor used on the
Windows-based Engineering Station.
3BUR001981R0201 97
Device Directory Display Appendix A Multibus-based Program Development and Maintenance
Device Directory Display

The Device Directory Display, Figure 55, contains a list of the turbo nodes and
controllers that contain ladder logic programs.
The display can be used to:
• Access the Segment Display to monitor program execution.
• Access the Segment Libraries to create, edit, backup, and load segments from
backup disks.
• Create an auto load list to specify which segments are automatically
downloaded into a node or controller and whether the segments are to
automatically start executing upon download.
98 3BUR001981R0201
Appendix A Multibus-based Program Development and Maintenance Device Directory Display
MOD 300 LADDER LOGIC PAGE 1
DEVICE DIRECTORY
TLL DEVICE DESCRIPTION
[*] EDIT TESTS STEVE’S TEST

[*] LLBULK1 TURBO SEGMENTS
[*] LLCONT1 SC CONTROLLER TESTS
[*] TEST1
[*] TEST_PROC TEST PROCEDURE SEGS
LAST FETCH
PAGE MSG ALARM
01 AUG 89 12:23:08
SEG LOAD PAGE PAGE LADDER LOGIC
LIB DISPLAY CREATE DELETE LIST FORW BACK QUIT
DEVICE DIRECTORY
Figure 55. Device Directory Display
3BUR001981R0201 99
Device Directory Callup Procedure Appendix A Multibus-based Program Development and
Device Directory Callup Procedure

There are a number of methods that can be used to access this display. This display
is usually called up from the Console Library Display.
1. Press the LIBRARY key to access the Console Library Display.
2. Select the line labeled LADDERLOGIC. (The person who configured your
Console Library Display may have chosen a different label for this line).
You can also call it up by bottom line entry. To do so,
1. Press the DISP REQ key.
2. Type LADDERLOGIC.
3. Press the ENTER key.
Your system may also be able to call it up by blocks on Overview Displays, buttons
on PSAPs, and/or page links on user graphics.
Information on the Device Directory Display

The Device Directory Display lists the nodes and controllers that contain ladder
segments. Each line contains a target in the form of a bracketed asterisk [*] that is
used to select the line and the following information:
TLL DEVICE Name for TLL in that controller or node. It is the same as
the name of the Ladder Logic Device templet of the
node.
DESCRIPTION A short descriptor for the device.
When you initially set up your system, you have to place the names of your nodes
and controllers that execute TLL on the Device Directory Display. Information for
doing this is provided in CREATE - How to Add Items to Device Directory Display
on page 101.
100 3BUR001981R0201
Appendix A Multibus-based Program Development and Maintenance CREATE - How to Add Items
CREATE - How to Add Items to Device Directory Display

When you first build the software structures for your system, you must place the
TLL items on the Device Directory Display. This must be done before you can build
the Ladder Logic Segments. After that, it may be necessary to add new TLL
applications as your system grows. The procedure for putting an item on the Device
Directory is:
1. Press the CREATE softkey.
2. An entry field appears on the screen with the prompt “enter new device name”.
Type the name that you gave to the Ladder Logic Device templet for the node
or controller. Press the ENTER key.
3. An entry field opens and requests a description for the entry. Type a descriptor
with a maximum of 24 characters and press the ENTER key.
LIB - How to Call up a Segment Library

Each node or controller that runs TLL has a Segment Library which is used to build
and maintain segments. These libraries are accessed from the Device Directory
Display by the following procedure.
1. Select the target for the required node or controller.
2. Press the LIB softkey. The Segment Library for the node or controller comes to
the screen.
Instructions for using this display are provided in Segment Library Display on page
104.
SEG DISPLY - How to Call up a Segment Display

Each node or controller that runs TLL has a runtime Segment Display that can be
used to monitor program execution. These displays are accessed from the Device
Directory Display. To do so,
2. Press the SEG DISPLY softkey. The Segment Display for the node or
controller comes to the screen.
Instructions for using this display are provided in Segment Display on page 143.
3BUR001981R0201 101
DELETE - How to Remove Item from Device Directory DisplayAppendix A Multibus-based Program
DELETE - How to Remove Item from Device Directory Display

To remove an item from the Device Directory, the procedure is:
2. Press the DELETE softkey.
3. You are prompted to verify the request by pressing the DELETE softkey a
second time.
LOAD LIST - How to Create Auto Load List for Node/Controller

Each node and controller can have an auto load list which specifies the segments
that are to be automatically loaded when the controller or node is downloaded. You
can also specify if TLL execution is to start automatically upon the download, or if
it is to wait for a command from the Segment Display. The procedure is:
2. Press the LOAD LIST softkey. The Auto-Load Segment List Display,
Figure 56, comes to the screen.
3. On the top portion of the screen, there is a field labeled START SCAN AFTER
LOAD?. It initially contains NO. If it is left at NO, the segments do not start
executing until directed to from the Segment Display. If you enter YES, the
scan starts automatically upon downloading.
4. There are 100 fields on the display which are defaulted to 0. To assign a
segment to the list, select a field and type the segment number. You do not have
to enter the segments in order.
5. When you have finished assigning segments, press the SAVE key to store the
list on disk.
If you decide that you do not want to keep the changes that you made to the
display, do not press SAVE. Instead press QUIT to be returned to the Device
Directory Display.
102 3BUR001981R0201
Appendix A Multibus-based Program Development and Maintenance LOAD LIST - How to Create
MOD 300 LADDER LOGIC

AUTO-LOAD SEGMENT LIST
START SCAN AFTER LOAD? NO
SELECT FIELD AND ENTER SEGMENT NUMBER FOR AUTO-LOAD
0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0
LAST FETCH
PAGE MSG ALARM
01 AUG 89 12:23:08
SAVE QUIT AUTO-LOAD LIST
DEV: LLCONT1
Figure 56. Auto-Load Segment List Display
3BUR001981R0201 103
Segment Library Display Appendix A Multibus-based Program Development and Maintenance
Segment Library Display

The Segment Library Display for a node or controller, Figure 57, lists all TLL
programs on a node or controller.
The Segment Library provides the means to:
• Create new segments
• Delete segments
• Call up the Ladder Logic Editor
• Print the contents of a segment
• Make duplicate copies of segments with new segment names
• Copy segments to other disk devices
• Load segments from other disk devices
Segment Library Callup Procedure

This display is called up from the Device Directory.
1. Select the target for the TLL device whose Segment Library you want to
access.
2. Press the LIB softkey.
104 3BUR001981R0201
Appendix A Multibus-based Program Development and Maintenance Segment Library Callup
MOD 300 LADDER LOGIC PAGE 1
SEGMENT LIBRARY
SEGMENT # DESCRIPTION TYPE COMPILED SIZE SCAN
[*] 1 JOHN’S TEST LADDER NO 0 0

[*] 2 CONTROLLER DIVIDE TS LADDER NO 0 0
[*] 3 JON’S CONTROLLER TST LADDER YES 2942 64
[*] 4 BILL’S CONVERSION TS LADDER YES 1516 24
[*] 5 BCO TEST LADDER YES 1996 37
[*] 6 BILL’S 3 TIMERS LADDER YES 1252 27
[*] 8 DC3 RUNG AGAIN LADDER YES 864 16
[*] 10 SEQUENCER OUTPUT LADDER YES 2020 393
[*] 11 SEQ O/P W DOWN TIMER LADDER YES 2020 393
[*] 12 50 RUNGS LADDER YES 15366 400
[*] 13 50 MORE (100 ELEM) LADDER YES 15366 400
[*] 14 50 MORE LADDER YES 15366 400
[*] 15 50 MORE LADDER YES 15366 400
[*] 16 50 MORE LADDER YES 15366 400
[*] 17 50 MORE LADDER YES 15366 400
LAST FETCH
PAGE MSG ALARM
01 AUG 89 12:23:08
EDIT PRINT PAGE PAGE DEVICE SEGMENT LIBRARY
FILES SEG SEG FORW BACK LIB DEV: LL CONT1
Figure 57. Segment Library Display
3BUR001981R0201 105
Information on the Segment Library Display Appendix A Multibus-based Program Development and
Information on the Segment Library Display

The display contains the following information for each segment:
SEGMENT # The segment number as assigned to the segment when

it was created.
DESCRIPTION A short descriptor for the segment.
TYPE The type of segment; either LADDER or FUNC.
COMPILED Either YES or NO to indicate if it can be loaded into the
node or controller.
SIZE The size of the segment in bytes.
SCAN The amount of time in microseconds required to scan
the segment.
Performing Function Through the Segment Library

The functions of the Segment Library are generally accomplished by selecting a
segment and pressing the appropriate softkeys. The display initially contains the
softkeys that are shown in Figure 58. Other sets of softkeys are automatically
accessed as you perform functions through this display.
LAST FETCH
PAGE MSG ALARM
01 AUG 89 12:23:08
PAGE PAGE SEGMENT LIBRARY
DELETE CREATE COPY SAVE LOAD FORW BACK QUIT
DEV: LLCONT1
Figure 58. Second Level Softkey Set of the Segment Library Display
To Select a Segment
Move the cursor to the target that is displayed next to the segment number, and press
the SELECT key. The segment remains selected until the function being performed
is completed, or until you select another segment.
106 3BUR001981R0201
Appendix A Multibus-based Program Development and Maintenance EDIT SEG - How to Modify an
To Display Additional Information

When the segment list contains more information than can be displayed at any one
time, additional information can be accessed by pressing the PAGE FORW or PAGE
BACK softkey.
To Exit from the Segment Library Display

Pressing the DEVICE LIB softkey while the main softkey set is displayed, causes
the Segment Library to exit and the Device Directory Display to come to the screen.
Pressing the QUIT softkey while another softkey set is displayed causes the main
softkey set to be displayed.
EDIT SEG - How to Modify an Existing Segment

To access the editor to edit a segment, select the name of the segment and press the
EDIT SEG softkey. A full range of functions are supported for segment editing.
These functions are described in Ladder Logic Editor on page 116. Editing
functions for the AdvaBuild TLL Builder installed on the Windows-based
Engineering Station are described in the AdvaBuild for Windows 2000 TLL Builder
User’s Guide.

must use the AdvaBuild TLL Builder.
PRINT SEG - How to Print a Segment

To print a hardcopy facsimile of a segment:
1. Select the segment.
2. Press the PRINT SEG softkey. If you have not selected a segment, you will be
prompted to make the choice.
3. An input field is created containing the name of the printer that is to print the
hardcopy. If this is not the printer that you want, press the next choice key.
Another printer name is displayed. If necessary, continue pressing NEXT
CHOICE until the proper name appears in the field.
3BUR001981R0201 107
FILES - How to Access Softkeys Appendix A Multibus-based Program Development and
4. Press ENTER to start printing.
FILES - How to Access Softkeys

By pressing the FILES softkey, you access the second level of softkeys, Figure 58.
These softkeys are used to either perform or initiate procedures to create, delete,
save to disk, or copy segments. These procedures are described in DELETE - How
to Delete a Segment on page 108 to How to Load (Restore) a Segment on page 112.
DELETE - How to Delete a Segment

To delete a segment from the library:
1. If the DELETE softkey is not currently displayed on the screen, press the
FILES softkey.
2. Select the segment to be deleted.
3. Press the DELETE softkey.
4. You will be prompted to press DELETE a second time to verify that you want
the segment deleted.
CREATE - How to Create a New Segment

To create a new segment:
1. If the CREATE softkey is not currently displayed on the screen, press the
FILES softkey.
2. Press the CREATE softkey.
3. An input field appears on the screen and you are prompted for a segment
number for the new segment. Type an integer number in the range of 1 to
65,535 and press the ENTER key. This number must be less than or equal to
the value specified in the MAX # OF SEGMENTS field on the Ladder Logic
Device templet. Also, segments should be numbered contiguously if you
expect to create as many segments as specified by the MAX # OF SEGMENTS
field. Remember that the loaded segments are executed in segment number
order during runtime.
4. Another input field appears which is defaulted to LADDER. Press ENTER to
make the choice LADDER.
108 3BUR001981R0201
Appendix A Multibus-based Program Development and Maintenance COPY - How to Duplicate
The other possible choice for the field is FUNCTION BLK. This feature was
not implemented in early versions of the software.
5. An input field opens and you are requested to assign a descriptor to the new
segment. Type a descriptor of up to 24 characters and press the ENTER key.
6. The new segment name now appears on the Segment Library. To build the
segment, select it and press the EDIT SEG softkey. This accesses the editor;
instructions for which appear in Ladder Logic Editor on page 116.
COPY - How to Duplicate Segment

You can build a new segment by duplicating an existing segment and giving it a new
name.
1. If the COPY softkey is not currently displayed on the screen, press the FILES
softkey.
2. Select the segment to be duplicated.
3. Press the COPY softkey.
4. A prompt and an input field appear on the screen. The prompt requests the
name for the Destination Directory. The input field contains the name of the
present directory (Segment Library). If you want the new segment to appear in
this library, press the ENTER key. If you want it to appear on another Segment
Library, type the name of TLL Library in that node or controller and press the
ENTER key.
5. A series of prompts appear that request the following:
SEGMENT # Type a segment number and press ENTER.

TYPE Select LADDER and press ENTER
DESCRIPTOR Type a descriptor and press ENTER.
When the last entry is made, the new segment appears on the Segment Library
where it can be accessed for editing.
3BUR001981R0201 109
SAVE - How to Save (Backup) Segments Appendix A Multibus-based Program Development and
SAVE - How to Save (Backup) Segments

You can make backup copies of either all segments of the library or selected
segments by following these instructions.
1. If the SAVE softkey is not currently displayed on the screen, press the FILES
softkey.
2. Press the SAVE softkey.
The softkey set shown in Figure 59 comes to the screen. There is also a field
that becomes visible at the bottom of the screen containing the name of the
current backup disk drive. It initially contains FD00 for the floppy disk drive.
LAST FETCH
PAGE MSG ALARM
CURRENT BACK-UP MEDIA: FD00
01 AUG 89 12:23:08
SAVE SAVE LIST LIST FORMAT PAGE PAGE SEGMENT LIBRARY
SEGMNT ALL BACKUP LIBRARY FD00 FORW BACK QUIT
DEV: TEST PROC
Figure 59. SAVE Softkey Set of the Segment Library Display
3. If you are using a different backup disk drive than FD00, enter its designation
into the BACKUP MEDIA field. Do this by selecting the field and using the
NEXT CHOICE key. The other possible drives are FD01 and WC01.
4. Insert a formatted flexible disk, if necessary, into the disk drive.
Follow the instructions in Step 5 if you want to save one segment. Follow the
instructions in Step 6 if you want to save all segments.
5. Save an individual segment by selecting it and pressing the SAVE SEGMNT
softkey. If the segment cannot fit on the disk, a message is displayed.
If the segment already exists on the backup disk, the softkey set shown in
Figure 60 is displayed.
110 3BUR001981R0201
Appendix A Multibus-based Program Development and MaintenanceSAVE - How to Save (Backup)
LAST FETCH
PAGE MSG ALARM
01 AUG 89 12:23:08
OVER SKIP
WRITE COPY
Figure 60. Softkeys Displayed if Segment Already Exists
If you press:
SKIP COPY the segment will not be copied.

OVER WRITE the copy continues with the old segment on the backup
disk being overwritten by the new one.
6. Save all segments by pressing the SAVE ALL softkey. The softkey set shown
in Figure 61 is displayed.
LAST FETCH
PAGE MSG ALARM
01 AUG 89 12:23:08
VERIFY OVER
QUIT
MODE WRITE
Figure 61. Softkeys Displayed After Pressing the SAVE ALL Softkey
If you press:
QUIT the Save procedure aborts.
3BUR001981R0201 111
How to Load (Restore) a Segment Appendix A Multibus-based Program Development and
OVER WRITE all segments are copied whether or not there is an

existing copy of any segment on the backup disk.
VERIFY MODE The system starts the procedure. If a segment is not on
the backup disk, it is automatically copied. If a segment
is already on the backup disk, the system displays the
set of softkeys that appear in Figure 60 so that you can
decide to either overwrite or skip copying that segment.
The system then continues to the next segment.
If the disk becomes full, you are prompted to insert a second disk.
Softkeys Available when Saving Segments

The following softkeys of the SAVE softkeys set, Figure 59, provide functions you
can use when saving segments.
LIST BACKUP displays a list of the segments on the backup disk.

LIST LIBRARY used when the screen is on the segment list of the
backup disk. It returns the Segment Library of the
primary device to the screen.
FORMAT FD00 if you need to format a floppy disk, you can do so by
inserting it into the floppy disk drive and pressing the
FORMAT FD00 softkey. Formatting a disk erases all
information that is currently stored on it. Be sure to verify
that the disk is blank or that its current information is not
needed before formatting.
How to Load (Restore) a Segment

You can load backup copies of segments from a backup disk by following these
instructions.
1. If the LOAD softkey is not currently displayed on the screen, press the FILES
softkey.
2. Press the LOAD softkey.
112 3BUR001981R0201
Appendix A Multibus-based Program Development and Maintenance How to Load (Restore) a
The softkey set shown in Figure 62 comes to the screen. A field labeled
CURRENT BACKUP MEDIA becomes visible. It initially contains FD00 for
the floppy disk drive.
LAST FETCH
PAGE MSG ALARM
CURRENT BACK-UP MEDIA: FD00
01 AUG 89 12:23:08
LOAD LOAD LIST LIST PAGE PAGE SEGMENT LIBRARY
FORW BACK QUIT
SEGMNT ALL BACKUP LIBRARY DEV: TEST PROC
Figure 62. LOAD Softkey Set of the Segment Library Display
3. If you are using a different backup disk drive than FD00, enter its designation
into the BACKUP MEDIA field. Do this by selecting the field and using the
NEXT CHOICE key. The other possible drives are FD01 and WC01.
4. If you are loading from a floppy, insert it into the flexible disk drive.
5. Press the LIST BACKUP softkey to display a list of the segments on the
backup disk.
Follow the instructions in Step 6 if you want to load one segment. Follow the
instructions in Step 7 if you want to load all segments from the backup disk.
6. Load an individual segment by selecting it and pressing the LOAD SEGMNT
softkey.
If the segment already exists on the primary disk, the softkey set shown in
Figure 63 is displayed.
3BUR001981R0201 113
How to Load (Restore) a Segment Appendix A Multibus-based Program Development and
LAST FETCH
PAGE MSG ALARM
01 AUG 89 12:23:08
OVER SKIP
WRITE COPY
Figure 63. Softkeys Displayed if Segment Already Exists
If you press:
SKIP COPY the segment will not be copied.

OVER WRITE the copy continues with the old segment on the primary
disk being overwritten by the new one.
7. Load all segments by pressing the LOAD ALL softkey. The softkey set shown
in Figure 64 is displayed.
LAST FETCH
PAGE MSG ALARM
01 AUG 89 12:23:08
VERIFY OVER
QUIT
MODE WRITE
Figure 64. Softkeys Displayed After Pressing the LOAD ALL Softkey
If you press:
QUIT the Load procedure aborts.
114 3BUR001981R0201
Appendix A Multibus-based Program Development and Maintenance Softkeys Available when
OVER WRITE all segments are copied whether or not there is an

existing copy of any segment on the primary disk.
VERIFY MODE The system starts the procedure. If a segment is not on
the primary disk, it is automatically copied. If a segment
is already on the primary disk, the system displays the
set of softkeys that appear in Figure 63 so that you can
decide to either overwrite or skip copying that segment.
The system then continues to the next segment.
Softkeys Available when Loading Segments

The LOAD softkeys set, Figure 62, provides additional functions you can use when
loading segments.
LIST BACKUP displays a list of the segments on the backup disk.

LIST LIBRARY returns the Segment Library of the primary device to the
screen.
3BUR001981R0201 115
Ladder Logic Editor Appendix A Multibus-based Program Development and Maintenance
Ladder Logic Editor

The Ladder Logic Editor Display, Figure 65, is used to build and modify Ladder
Logic Segments. You should be familiar with TLL segment structure and
instructions as they are described in Section 3, Program Structure and Program
Instructions before using the procedures in this section.

must use the AdvaBuild TLL Builder. Instructions for using the
AdvaBuild TLL Builder for TLL development on the Windows-
based Engineering Station are provided in the AdvaBuild for
Windows 2000 TLL Builder User’s Guide.
Building a segment involves making a graphic representation of the required ladder.
The diagram starts as two vertical power strips. You then use the softkeys to insert
rungs with their associated instruction symbols. The left power rail has short
horizontal lines attached to it as shown by call out 1 in Figure 65. These are the rung
targets that you use when you want to insert a rung into the diagram.
Call out 2 shows short horizontal targets that you select when you want to insert an
instruction. When you insert an instruction symbol, the system prompts you for any
additional information it needs for the instruction. Call out 3 shows dots that you
select when you want to insert a vertical line for a branch.
When you save the diagram, it is automatically compiled and you are told if there
are any errors that will prevent the segment from being loaded into the node or
controller.
116 3BUR001981R0201
Appendix A Multibus-based Program Development and Maintenance Ladder Logic Editor Callup
LADDER LOGIC EDITOR

DEVICE: TEST_PRO
LINE SEGMENT# 4
PHASE FOUR: TIMER TESTS
1 [REM]
PHASE FOUR
3 [G] [-] [ZCL]
TEST 1: ‘TIMER RESET’ AND ‘RETENTIVE TIMER ON’ [REM]

4
FOR AN ‘UP’ TIMER
TIM_UP TIM_UP
5 ]/[ [RTR]
EN
2
3
LAST FETCH
PAGE MSG ALARM
INSERT RELAY DATA MATH TIMER/ EXTDED 01 AUG 89 12:23:08
MODIFY MORE PLCEDITOR
RUNG KEYS KEYS KEYS COUNTR KEYS
Figure 65. Example of a Ladder Logic Editor Display Showing the First Level of Main Softkeys
Ladder Logic Editor Callup Procedure

This display is called up from the Segment Library Display.
1. Select the name of the file to be edited.
2. Press the EDIT SEG softkey.
3BUR001981R0201 117
Editing Functions Appendix A Multibus-based Program Development and Maintenance
Editing Functions
There are several keys on the alphanumeric keyboard you can use to move the
cursor and perform other editing functions when you produce a segment. These keys
are described in Cursor/Display Movement in Ladder Logic Editor on page 133 and
Editing Functions of the Ladder Logic Editor on page 134. The track ball and mouse
can also be used to move the cursor in this editor.
Softkey Sets of the Ladder Logic Editor

The Ladder Logic Editor has several softkey sets you can use to perform its
functions. The main softkey set has two levels. The first level, Figure 65, appears
when you initially access the editor. The second level appears when you press the
MORE softkey on the first level. You can return to the first level by pressing the
MORE softkey on the second level. The remainder of this section describes the
functions of these softkeys.
How to Insert TLL Elements

This section describes how to put the main structures into your ladder diagram.
How to Add a Rung to a Diagram

You add a rung to the diagram with the INSERT RUNG softkey from the main
softkey set. The procedure is:
1. Select the point on the left power rail where you want the rung inserted.
2. Press the INSERT RUNG softkey.
The rung is given the proper number as determined by its rung position. If the
cursor is placed on an existing rung, that rung and any that follow it are moved
downwards and renumbered.
3. The last element position on the rung is highlighted when the rung first
becomes visible. You must enter an output-type element on that rung before
you can enter elements in other positions.
Example:
To add a rung at rung position 6 on the ladder, select the left power rail at the
position 6 level as shown in Figure 66.
118 3BUR001981R0201
Appendix A Multibus-based Program Development and Maintenance How to Insert TLL Elements
TIM_UP
5 (RTO)
6
START HERE
Figure 66. Inserting a Rung
Press the INSERT RUNG softkey and the rung is displayed as shown in Figure 67.
TIM_UP
5 (RTO)
Figure 67. Inserted Rung
Insert an output type element at element position 8.
How to Add a Branch to a Rung

You add a branch to a rung with the BRANCH softkey which is on the Relay
softkey set. The procedure is:
1. Access the Relay softkey set if it is not currently displayed by pressing the
RELAY KEYS softkey.
2. Place the cursor at the point on the line where you want the left side of the
branch to appear and press SELECT.
3. Press the BRANCH softkey.
4. Select the point on the line where you want the right side of the branch and
press Select.
3BUR001981R0201 119
How to Insert TLL Elements Appendix A Multibus-based Program Development and Maintenance
The system draws the branch.

Example:
A branch is to be added to an existing rung. Its starting point is represented by
point 2 in Figure 68. It is to end at point 3.

[G] [>] ()
1 2 3
Figure 68. Inserting a Branch
First you place the cursor on point 2. Then you press the BRANCH softkey. Then
you select point 3.
The system draws the branch as shown in Figure 69.

[G] [>] ()
1 2 3
Figure 69. Inserted Branch
You can now insert program elements on the horizontal targets on the branch.
A branch can be inserted in front of an existing branch by selecting the vertical lines
of the existing branch. A larger branch can be inserted in front of an existing branch.
For example, if you selected dot 1 and line 3 in the previous branch diagram, a
branch that started at 1 and ended at 3 would be inserted before the existing branch.
Remember that you must follow the rules for valid branch configurations as
described in Program Structure on page 61.
120 3BUR001981R0201
Appendix A Multibus-based Program Development and Maintenance How to Insert TLL Elements
A segment can have a maximum of 255 rungs.
How to Add an Instruction to a Line

Several sets of softkeys on the Ladder Logic Editor display are used to enter the
instructions into the programs. When you press a key for a symbol, you are
prompted for the necessary information. When you have entered it, the symbol for
the instruction is placed at the cursor position in the display
For example, to place an examine on instruction into a segment:
1. Press the RELAY KEYS softkey to access the Relay softkey set.
2. Move the cursor to the horizontal element target at the position at which the
instruction is to appear and press the SELECT key. The position changes to a
red color.
3. Press the -] [- XON softkey to specify that you want an examine on instruction.
4. The system then asks you to enter the name of the contact that is to be
examined. Type the tag name and press ENTER.
5. A second entry field opens and you are asked which attribute you want. It is
defaulted to AC. You can use the NEXT CHOICE key to step through the other
possibilities for the field which are PR, EN, DN, and DQ.
It is your responsibility to choose an attribute that is valid for the instruction.
Information about the instructions appears in Section 3, Program Structure and
Program Instructions. The AC and the DQ attributes are the two valid choices
for the examine on instruction. You must choose one of these two.
The system draws the symbol after you answer the last prompt.
How to Put Comments into the Ladder Diagram

The REMARK KEY softkey on the second level of the main softkey set allows you
to enter a comment. The comment appears in the source code and is not compiled
into the program. To insert a comment as shown in Figure 70:
1. Select a position on the left power rail at the point you want the comment
inserted.
2. Insert a rung.
3BUR001981R0201 121
MODIFY - How to Modify an Existing Element Appendix A Multibus-based Program Development
3. Press the REMARK KEY softkey.

4. An entry field opens. Type the text of the remark and press the ENTER key.
The entry can have one or two lines with up to 50 characters per line.
TEST 1 : ‘TIMER RESET’ AND ‘RETENTIVE TIMER ON’

4 FOR AN ‘UP TIMER’ (REM)
Figure 70. Inserting a Comment
How to Insert a Blank Line into the Segment

To insert a blank line into the segment, select a position on the left power rail and
press the INSERT LINE key on the alphanumeric keyboard.
MODIFY - How to Modify an Existing Element

You start the procedure to modify an existing element with the MODIFY softkey
which is on the first level of the main softkey set.
1. Select the element you want to modify.
2. Press the MODIFY softkey.
3. The system prompts for the information that you may want to change. The
prompts are different for different elements. Each time you want to enter new
information, type the information and press the ENTER key. If you do not want
the information specified in the prompt to be changed, press the ENTER key.
How to Access Keysets for Inserting Elements

The first level of the main softkey set contains keys for accessing other softkey sets.
These keys are:
RELAY KEYS Accesses the softkeys that insert relay instructions. The
BRANCH key which is used to add branches to a rung is
part of this softkey set.
DATA KEYS Accesses the softkeys that insert data manipulation
instructions.
122 3BUR001981R0201
Appendix A Multibus-based Program Development and Maintenance QUIT EDITOR - How to Exit
MATH KEYS Accesses the softkeys that insert math instructions.

TIMER/COUNTR Accesses the softkeys that insert timer instructions and
counter instructions.
EXTDED KEYS Accesses the softkeys that insert register to file transfer,
file to file, sequencer, zone control, and message
instructions.
QUIT EDITOR - How to Exit Editor with No Save

To exit the editor without performing a Save, press the QUIT EDITOR softkey
which is on the second level of softkeys, Figure 71. A YES and a NO softkey appear
on the screen and you are asked if you want to quit the editor. If you answer YES,
the program exits and all edits performed since the previous Save are lost.
LAST FETCH
PAGE MSG ALARM
01 AUG 89 12:23:08
QUIT BACK- REMARK PLCEDITOR
EDITOR SAVE COPY CUT PASTE WARD KEY MORE
Figure 71. Second Level of Main Softkeys on the Ladder Logic Editor
SAVE - How to Save, Compile and Locate Errors

You save and compile the segment with the SAVE softkey on the second level of the
main softkey set. This procedure overwrites whatever was previously stored for this
segment. The procedure is:
1. Press the SAVE softkey. This starts the compiler.
2. When the compiler is finished, the segment is saved to disk and you are told
whether or not the segment has errors. If the segment has errors, they are also
saved to disk. A YES and a NO softkey appear on the screen and you are asked
if you want to quit the editor. If you select NO, the system begins showing you
where errors are in the segment.
3BUR001981R0201 123
SAVE - How to Save, Compile and Locate Errors Appendix A Multibus-based Program
3. Rungs that contain errors have a flashing red indicator in their element 1
positions as shown by call out 1 in Figure 72.
TIM_UP ZERO TEST1

6 ][ [>]
DN
1
TIM_UP
7 [RTR]
LAST FETCH
LAST
PAGE MSG ALARM
FETCH
PAGE MSG ALARM
01 AUG 89 12:23:08
INSERT RELAY DATA MATH TIMER/ EXTDED 01 AUG 89 12:23:08
PLCEDITOR
SAVE MODIFY MORE
QUIT PLCEDITOR
Figure 72. Error Indicator for a Rung
When you select an indicator, an error message appears that describes the
problem on the rung. Figure 73 shows an example of such an error message.
You can correct the error and go on to the next one. The error indicators remain
on the screen until you perform a Save.
TIM_UP ZERO TEST1

6 ][ [>]
DN
TIM_UP
7 [RTR]
LAST FETCH
LAST
PAGE MSG ALARM
FETCH
ERROR: MUST BE PRECEDED BY GET MSG
PAGE ALARM
01 AUG 89 12:23:08
INSERT RELAY DATA MATH TIMER/ EXTDED 01 AUG 89
PLCEDITOR 12:23:08
SAVE MODIFY QUIT
MORE PLCEDITOR
Figure 73. Message for Selected Error Indicator
124 3BUR001981R0201
Appendix A Multibus-based Program Development and MaintenanceCOPY How to Copy Portion of
You can use the search feature to find errors. Press the FIND key located on the
alphanumeric keyboard, type the word ERROR and press the ENTER key. The
system searches for the next error. When it finds an error, it stops, selects the
error, and displays the error message. Once the word ERROR is in the Find
Buffer, you can find the next error by pressing the NEXT FIELD key.
4. When you have corrected all errors, press the SAVE softkey to compile and
save the segment.
COPY How to Copy Portion of Segment

The COPY softkey on the second level of the main softkey set is used to copy
information into the paste buffer. The original information remains in place.
1. Select the beginning of the information to be copied.
2. Press the COPY softkey.
3. Select the end of the information. The system then copies the information or
tells you why a copy is not possible.
The information can then be pasted into another part of the ladder diagram. If you
wish, you can paste this information into multiple positions on the diagram. It
remains in the paste buffer until another item is copied or cut.
CUT - How to Move Information to Paste Buffer

The CUT softkey on the second level of the main softkey set is used to remove
information from the screen and place it into the paste buffer.
1. Select the beginning of the information to be cut.
2. Press the CUT softkey.
3. Select the end of the information. The system then cuts the information or tells
you why a cut is not possible.
The information can then be pasted into another part of the ladder diagram. If you
wish, you can paste this information into multiple positions on the diagram. It
remains in the paste buffer until another item is copied or cut.
3BUR001981R0201 125
PASTE - How to Paste Information into Ladder Diagram Appendix A Multibus-based Program
PASTE - How to Paste Information into Ladder Diagram

The PASTE softkey on the second level of the main softkey set is used to insert the
contents of the paste buffer into the segment.
1. Select the position where you want the beginning of the pasted information to
appear.
2. Press the PASTE softkey. The system then pastes in the information or tells you
why a paste cannot be performed at that position.
BACKWARD/FORWARD - Setting the Search Direction

There is a softkey on the second level of softkeys that reverses the direction in which
the search function acts. When the search mode is forward, the softkey is labeled
BACKWARD. It can be used to change the mode to backward. When the mode is
backward, the key is labelled FORWARD.
Relay Softkeys
The Relay softkey set, Figure 74, is accessed by pressing the RELAY KEYS
softkey on the main softkey set. Descriptions of the Relay softkeys follow.
LAST FETCH
PAGE MSG ALARM
01 AUG 89 12:23:08
QUIT -] [- -]/[- -( )- -(L)- -(U)-
XON XOFF OUTPUT LATCH UNLTCH BRANCH
Figure 74. Relay Softkey Set of the Ladder Logic Editor
-] [- XON prompts for the name of the contact and what you want
displayed with the symbol during runtime. Then prompts
for an attribute. Then draws an Examine On symbol.
-]/[- XOFF prompts for the name of the contact. Then prompts for
an attribute. Then draws an Examine Off symbol.
126 3BUR001981R0201
Appendix A Multibus-based Program Development and Maintenance Data Softkeys
-( )- OUTPUT prompts for the name of the contact. Then draws an

Output Energize symbol.
-(L)- LATCH prompts for the name of the contact. Then draws an
Output Latch symbol.
-(U)- UNLTCH prompts for the name of the contact. Then draws an
Output Unlatch symbol.
BRANCH inserts a branch onto a line. Instructions for this task
appear in How to Insert TLL Elements on page 118.
Data Softkeys
The Data softkey set, Figure 75, is accessed by pressing the DATA KEYS softkey
on the main softkey set. Descriptions of the Data softkeys follow.
LAST FETCH
PAGE MSG ALARM
01 AUG 89 12:23:08
QUIT -[G]- -[P]- -[GET]- -[=]- -[<]- -[>]-
LT GT MORE
GET PUT GET DB EQUAL
Figure 75. First Level Data Softkey Set of the Ladder Logic Editor
-[G]- GET prompts for the name of the source register. Then
prompts for an attribute. Then draws a Get symbol.
-[P]- PUT prompts for the name of the destination register. Then
draws a Put symbol.
-[GET]- GET DB prompts for the name of the tag that contains the
required attribute. You enter a tag for a loop level
variable or a tag-fcm name for an FCM variable. The
software prompts for the name of the attribute. You must
type in the name of the attribute and press ENTER.
Then draws a Get Data Base symbol.
3BUR001981R0201 127
Data Softkeys Appendix A Multibus-based Program Development and Maintenance
-[=]- EQUAL prompts for the name of a register. Then prompts for the
name of the attribute. Then draws a compare Equal
symbol. The value of the get instruction that precedes
this instruction is compared with the value in the register.
-[<]- LT prompts for the name of a register. Then prompts for the
name of the attribute. Then draws a compare Less Than
symbol. The value of the get instruction that precedes
this instruction is checked to see if it is less than the
value in the register.
-[>]- GT prompts for the name of a register. Then prompts for the
name of the attribute. Then draws a compare Greater
Than symbol. The value of the get instruction that
precedes this instruction is checked to see if it is greater
than the value in the register.
MORE accesses the second level of Data softkeys, Figure 76.
LAST FETCH
PAGE MSG ALARM
01 AUG 89 12:23:08
QUIT -[<=]- -[>=]-
MORE
LTEQ GTEQ
Figure 76. Second Level Data Softkey Set of the Ladder Logic Editor
128 3BUR001981R0201
Appendix A Multibus-based Program Development and Maintenance Math Softkeys
-[<=]- LTEQ prompts for the name of a register. Then prompts for the
name of the attribute. Then draws a compare Less Than
or Equal To symbol. The value of the get instruction that
precedes this instruction is checked to see if it is less
than or equal to the value in the register.
-[>=]- GTEQ prompts for the name of a register. Then prompts for the
name of the attribute. Then draws a compare Greater
Than or Equal To symbol. The value of the get
instruction that precedes this instruction is checked to
see if it is greater than or equal to the value in the
register.
MORE accesses the first level of Data softkeys.
Math Softkeys
The Math softkey set, Figure 77, is accessed by pressing the MATH KEYS softkey
on the main softkey set. Descriptions of the Math softkeys follow.
LAST FETCH
PAGE MSG ALARM
01 AUG 89 12:23:08
QUIT -(+)- -(-)- -(X)- -(÷)- BCD-> GRAY->
ADD SUB MULT DIV BINARY BINARY
Figure 77. Math Softkey Set of the Ladder Logic Editor
QUIT returns to main softkeys.

-(+)- ADD prompts for the name of a register in which to store the
sum. Then draws an Add symbol. It adds the results of
two previous get instructions.
3BUR001981R0201 129
Timer/Counter Softkeys Appendix A Multibus-based Program Development and Maintenance
-(-)- SUB prompts for the name of a register in which to store the
result. Then draws a Subtract symbol. It subtracts the
result of the previous get instruction from the get that
preceded it.
-(X)- MULT prompts for the name of a register in which to store the
product. Then draws a Multiply symbol. It multiplies the
results of two previous get instructions.
-(÷)- DIV prompts for the name of a register in which to store the
quotient. Then draws a Divide symbol. It divides the
result of the previous get instruction into the result of the
get that preceded it.
BCD -> BINARY prompts for the names of a counter, register and file.
Then draws a BCD to Binary symbol.
GRAY -> BINARY prompts for the names of a counter, register and file.
Then draws a Gray to Binary symbol.
Timer/Counter Softkeys
The Timer/Counter softkey set, Figure 78, is accessed by pressing the
TIMER/COUNTR softkey on the main softkey set. Descriptions of the
Timer/Counter softkeys follow.
LAST FETCH
PAGE MSG ALARM
01 AUG 89 12:23:08
QUIT (TON) (RTO) (RTR) (CTU) (CTD) (CTR) (CTP)
ON RET ON RESET UP DOWN RESET PRESET
Figure 78. Timer/Counter Softkey Set of the Ladder Logic Editor

(TON) ON prompts for the name of a timer. Then draws a Timer On
symbol.
130 3BUR001981R0201
Appendix A Multibus-based Program Development and Maintenance Extended Softkeys
(RTO) RET ON prompts for the name of a timer. Then draws a Retentive
Timer On symbol.
(RTR) RESET prompts for the name of a timer. Then draws a Retentive
Timer Reset symbol.
(CTU) UP prompts for the name of a counter. Then draws a Count
Up symbol.
(CTD) DOWN prompts for the name of a counter. Then draws a Count
Down symbol.
(CTR) RESET prompts for the name of a counter. Then draws a
Counter Reset symbol.
(CTP) PRESET prompts for the name of a counter. Then draws a
Counter Preset symbol.
Extended Softkeys
The Extended softkey set, Figure 79, is accessed by pressing the EXTDED KEYS
softkey on the main softkey set. Descriptions of the Extended softkeys follow.
LAST FETCH
PAGE MSG ALARM
01 AUG 89 12:23:08
QUIT REG-> FILE-> FILE-> SEQNCR SEQNCR SEQNCR MORE
FILE REG FILE OUTPUT INPUT LOAD
Figure 79. First Level Extended Softkey Set of the Ladder Logic Editor

REG -> FILE prompts for a counter name, register name, and
destination file name. Then draws a Register to File
Move symbol.
3BUR001981R0201 131
Extended Softkeys Appendix A Multibus-based Program Development and Maintenance
FILE -> REG prompts for the counter name, register name, and
source file name. Then draws a File to Register Move
symbol.
FILE -> FILE prompts for the counter name, source file name, and
destination file name. Then draws a File to File Move
symbol.
SEQNCR OUTPUT prompts for the sequencer name, counter name, mask
register name, and file name. Then draws the
Sequencer Output symbol.
SEQNCR INPUT prompts for the sequencer name, counter name, mask
register name, and file name. Then draws the
Sequencer Input symbol.
SEQNCR LOAD prompts for the sequencer name, counter name, and file
name. Then draws the Sequencer Load symbol.
MORE accesses the second level of Extended softkeys,
Figure 80.
LAST FETCH
PAGE MSG ALARM
01 AUG 89 12:23:08
QUIT (MCR) (NCR) (ZCL) (NCL) (MSG) MORE
MCONT EXCONT ZONE EXZONE MESG
Figure 80. Second Level Extended Softkey Set of the Ladder Logic Editor

(MCR) MCONT draws the Master Control Reset symbol.
(NCR) EXCONT draws the End of Master Control Reset symbol.
(ZCL) ZONE draws the Zone Control Last State symbol.
(NCL) EXZONE draws the End of Zone Control Last State symbol.
132 3BUR001981R0201
Appendix A Multibus-based Program Development and Maintenance Cursor/Display Movement in
(MSG) MESG prompts for the reference number of the message to be

sent. Then draws the Message symbol.
MORE accesses the first level of Extended softkeys.
Cursor/Display Movement in Ladder Logic Editor

The Ladder Logic Editor is designed so that the mouse and track ball can be used to
move the cursor. In addition, several alphanumeric keyboard keys and display
softkeys can be used to either move the cursor or scroll the display to additional
information.
The cursor moves forward or backward, depending on which direction has been
selected via the BACKWARD/FORWARD softkey. Once a direction has been
selected, the cursor continues to move in that direction until set to move the opposite
way by either the BACKWARD/FORWARD softkey or another cursor control
function.
Other editing functions are affected by the direction in which the cursor is set to
move. For example, if FIND is being used, and the cursor direction is forward, the
search is forward toward the end of the file; if the cursor direction is backward, the
search is backward toward the beginning of the file.
There are several keys used to move the cursor.
Press the UP ARROW key to move the cursor in the direction of the element in the
line above.
Press the DOWN ARROW key to move the cursor in the direction of the element in
the line below.
Press the LEFT ARROW key to move the cursor in the direction of the preceding
element.
The RIGHT ARROW key is used to move the cursor in the direction of the next
element.
The EOL key moves the cursor to and selects the output element when the cursor is
on a rung.
The BOL key moves the cursor to the beginning rung position and selects it when
the cursor is on a rung.
The PAGE DOWN key moves the display forward by one half page.
3BUR001981R0201 133
Editing Functions of the Ladder Logic EditorAppendix A Multibus-based Program Development and
The PAGE UP key moves the display back by one half page.
The PAGE FWD softkey moves the display forward by one page.
The PAGE BACK softkey moves the display back by one page.
The TOP key moves the cursor to the first rung of the file and sets the cursor mode
to forward.
The BOT key moves the cursor to the last element of the file and sets the cursor
mode to backward.
The SCROLL DOWN key scrolls the page down one line.
The SCROLL UP key scrolls the page up one line.
Editing Functions of the Ladder Logic Editor

The INSERT key inserts a blank rung space if it is pressed when the cursor is on a
rung target.
Each time a delete operation is performed, the material that was just deleted is
placed in the undelete buffer. The undelete buffer stores the material until another
delete operation occurs. At this time, the contents of the buffer is cleared, and the
newly deleted material is placed in it. The contents of the buffer may be used in
other editing operations (for example, it may be reinserted, moved to a new position,
and so on).
The DEL LINE key deletes items:
• If the selected position is on a rung, the entire rung is deleted.
• If the selected position is on a branch line, that line is deleted.
• If the selected position is on the left power rail position of a blank line, the
blank line is deleted.
After the deletion, the remaining lines are scrolled upward and the lines are
renumbered.
The DEL CHAR and DEL WORD keys act only on elements. If you delete an
output, you must add an output. You can delete any of the other elements from a line
without having to replace them.
The DEL EOL deletes from the current cursor position to the end of the line.
134 3BUR001981R0201
Appendix A Multibus-based Program Development and Maintenance Editing Functions of the
• If the selected position is on a rung line, it will not delete the output element
unless the rung target was chosen.
• If the selected position is on a branch start, the whole branch is deleted. If the
cursor was elsewhere in the branch, it will delete up to the branch end.
The UN DEL is used to insert information that was deleted by the previous delete
function. It inserts the previously deleted information at the cursor position if there
are enough blank elements. If the deleted material was a rung or branch, it creates a
new rung or branch.
The FIND and NEXT FIELD keys work together. When you press FIND, a prompt
requests the character string to search for. When you press NEXT FIELD, the
system searches for the next field that matches the instruction tag in the FIND
buffer. The search takes places in the cursor mode direction. The character string
turns solid red when it is found.
3BUR001981R0201 135
Editing Functions of the Ladder Logic EditorAppendix A Multibus-based Program Development and
136 3BUR001981R0201
Appendix B Multibus-based TLL Console
Support
General Information
This section describes displays used to monitor TLL execution and interact with the
TLL data structures.
The console runtime software contains a complete set of displays that are used to
monitor TLL execution and interact with TLL data structures. These TLL runtime
displays include:
• Segment Display - which is used to monitor the TLL execution in nodes and
controllers. It is described in Common Features of the TLL Displays on page
138 and Segment Display on page 143.
• TLL Device Data Base Summary Displays - which include such things as
Counter Displays, File Displays, and so on, are used to view and change the
data structures. They are described in Common Features of the TLL Displays
on page 138 and TLL Device Data Base Summary Displays on page 150.
TLL status blocks and status lines that appear on the CCF and TCL Runtime
Displays are described in TLL Items on CCF and TCL Displays on page 162.
Note that the figures for the TLL runtime displays in this section are
those seen on the Multibus console. The runtime displays seen on
the HP-UX Advant Station and Windows-based Engineering
Station look different, but they contain the same information. Refer
to the AdvaCommand Basic Functions User’s Guide for the TLL
runtime displays on the HP-UX Advant Station. Refer to the
Operate IT Operation Manual Add-On for Advant OCS with MOD
300 for the TLL runtime displays on the Windows-based Operator
Station.
3BUR001981R0201 137
Common Features of the TLL Displays Appendix B Multibus-based TLL Console Support
Common Features of the TLL Displays

TLL contains a series of Console Resident Displays that are used to monitor TLL
segments and data structures at runtime. Figure 81 is an example of one of these
displays. Table 1 lists them and gives some call up keywords. This section describes
the features that these displays have in common. Their specific characteristics are
described in Segment Display on page 143 and TLL Device Data Base Summary
Displays on page 150.
LL DEVICE: LLCONT1
TIMER NAME DESCRIPTION PRESET VALUE ENABLE

TIM1 TIMER1 0000:00:10.00 0000:00:00.00 NO
TIM2 TIMER2 0000:00:00.02 0000:00:00.02 NO
TIM3 TIMER3 0000:00:00.30 0000:00:00.00 NO
TIM_DN DOWN TIMER 0000:00:00.30 0000:00:00.00 NO
UNIT OVER LOGIC GO TO GO TO FIND FIND LAST FETCH

OVER VIEW DISPS TOP BOT ELEM NEXT PAGE MSG ALARM
01 AUG 89 12:23:08
LLTIMER
Figure 81. Example of a TLL Runtime Display
138 3BUR001981R0201
Appendix B Multibus-based TLL Console Support User Security
Table 1. TLL Displays
Function Target on Bottom Line Entry

Display
Operation Displays Keyword
Segment Display SEGMT DISP LLSEGDISP
Device Data Base Summary Displays
I/O Point Display IO_PT DISP LLIOPOINT
Counter Display CNTR DISP LLCOUNTER
Timer Display TIMER DISP LLTIMER
Register Display REGTR DISP LLREGISTER
File Display FILE DISP LLDATAFILE
Sequencer Display SEQNC DISP LLSEQUENCER
User Security
When you configure an environment, you can specify which categories of users can
use the different types of TLL Displays. Each of the classes of TLL Displays named
in Table 1 appear on the appropriate Runtime Authority Display (Multibus-based
node), Authority Definition dialog (HP-UX Advant Station), or Security tab of the
System Definition object (Windows-based Operator Station) with a default authority
of Engineer. If you leave a display category at this default, only engineers can make
entries to the display. If you change the authority to Supervisor, both supervisors
and engineers can make entries. If you change the user category to Operator, all
three user classes are allowed to make changes. All users can view the displays,
even if they are not in a user category that can make changes to them.
The procedures to accomplish this are provided in the Console Configurator User’s
Guide (for Multibus consoles), the AdvaBuild Environment Builder User’s Guide
(for HP-UX Advant Stations), and the Operate IT Configuration Manual Add-On
for Advant OCS with MOD 300 (Windows-based Operator Stations).
3BUR001981R0201 139
How to Access the TLL Displays Appendix B Multibus-based TLL Console Support
How to Access the TLL Displays

There are a number of methods by which the TLL Displays can be accessed.
Function Targets on the Operations Displays

All standard console resident displays of all software packages have a set of
function targets that can be used to access the TLL Displays. These targets are
shown in Figure 82 and listed in Table 1. The position of these targets on the display
depends on the type of displays. They are the second level of targets on the TLL
displays, which means you can access them by using the More arrow on the first
level of targets. They are the third level of function targets on the CCF and TCL
Displays, which means you use the More arrow twice to access them.
UNIT OVER IO_PT TIMER CNTR REGTR FILE SEQNC SEGMT LAST FETCH
OVER VIEW DISP DISP DISP DISP DISP DISP DISP PAGE MSG ALARM
01 AUG 89 12:23:08
LLIOPOINT
Figure 82. Function Targets on Operation Displays for Calling Up TLL Runtime Displays
Bottom Line Entry

You can use bottom line entry, Figure 83, to request the displays. The procedure for
this is:

LLIOPOINT, TURB1, CON41 01 AUG 89 12:23:08
LLDATAFILE
Figure 83. Bottom Line Entry Example
140 3BUR001981R0201
Appendix B Multibus-based TLL Console Support How to Access the TLL Displays
1. Press the DISP REQ key on the keyboard. This clears the bottom line and
places the cursor there.
2. Type in the display request and press the ENTER key to access the display. The
display request consists of a Bottom Line Entry keyword from Table 1 and, in
some cases, parameters as follows.
Option 1 Keyword, no parameters
When you use a keyword and no parameters, the system accesses one example
of the requested display. For example, the display request
LLCOUNTER
results in the screen going to a randomly chosen Counter Display.
Option 2 Keyword, first parameter only
When you use a keyword with one parameter, the system displays the specific
display for a node or controller. For example, the display request
LLSEGDISP, LAD1
results in the screen going to the Segment Display for the node or controller in
which TLL is named LAD1.
Option 3 Keyword, both parameters
When you use a keyword with two parameters, the system displays the specific
display for a node or controller scrolled to the point where the data entry for the
second parameter is visible. This data entry will be at the top of the display,
unless the data is on the last page of information. In that case, the complete last
page of information is displayed. For example, the display request
LLTIMER, LAD1, T41
results in the screen going to a page of the Timer Display that has information
for timer T41.
Option 4 Keyword, second parameter only
This option works in exactly the same manner as entries with two parameters.
Be sure to use commas to show that only the second parameter is being used.
For example:
LLTIMER, , T41
3BUR001981R0201 141
Viewing Information on the TLL Displays Appendix B Multibus-based TLL Console Support
works exactly like

LLTIMER, LAD1, T41
Overviews, PSAPs, and Page Links

Your system may be configured to call up TLL Displays via blocks on the Overview
Displays or keys on the Page Selection and Alarm Panels (PSAPs). Information
about configuring these blocks and buttons appears in the Console Configurator
User’s Guide (for Multibus nodes) and the AdvaBuild Environment Builder User’s
Guide (for HP-UX Advant Station Operator Stations). You can put page links to
these displays on the user built displays as described in Interface with Display
Builder on page 94.
Viewing Information on the TLL Displays

The Runtime Displays often contain more information than can appear on the screen
at one time. There are a number of screen targets and keys on the alphanumeric
keyboard that allow you to view the additional information. In general, they work in
the manner described below.
Screen Targets
GO TO TOP moves the screen to the beginning of the information.
GO TO BOT moves the screen to the end of the information.
Keyboard Keys
PAGE-FWD accesses the next page of information.
PAGE BACK accesses the previous page of information.
SCROLL UP moves the screen one line up.
SCROLL DOWN moves the screen one line down.
The keys function in a slightly different manner for the File and Sequencer Displays
as described in their respective sections.
142 3BUR001981R0201
Appendix B Multibus-based TLL Console Support Segment Display
Segment Display
The Segment Display, Figure 84, is used to monitor and control TLL execution in a
node or controller. The Segment Display can be used to:
• Load and remove segments.
• Turn TLL scanning on and off.
• Debug segments by forcing the I/O points to specified conditions.
• Access displays for the TLL Data Structures (timers, counters, and so on)
LL DEVICE: LLCONT1
SEG NO: SCAN: ON OFF FORCE I/O: OFF
TIM2 TIM2
101 ]/[ [RTO]
ON YES
TIM2 CTR3
102 ][ [CTU]
ON YES ON
TIM2 SEQ OUTPUT NO
103 ][ SEQ: SF1
ON YES CNT: CTR3
STEP: 2/15
MASK: REG3
FILE: DF1
CTR3
104 [CTU]
ON
TIM2 TIM2
105 ][ [RTR]
DN YES ON
UNIT OVER LOGIC SGMT SGMT GO TO GO TO FIND FIND LAST FETCH

OVER VIEW DISPS LOAD READY TOP BOT ELEM NEXT PAGE MSG ALARM
01 AUG 89 12:23:08
LLSEGDISP
Figure 84. TLL Segment Display
3BUR001981R0201 143
Segment Display Features Appendix B Multibus-based TLL Console Support
Segment Display Features

This display has the standard call up, user security, and information viewing
features that are described in Common Features of the TLL Displays on page 138. It
can also be called up by the SEG DISPLY softkey on the Device Directory Display.
Information on the Segment Display

The following describes the fields at the top of the Segment Display
.
LL DEVICE: LLCONT1 The LL DEVICE field gives the name of TLL in the
node or controller that contains the segments. It is a
discrete field that can be used to call up the display
for other nodes or controllers. You do this by entering
the name of TLL in the node or controller that you
want and pressing the ENTER key. The NEXT
CHOICE key can be used to scroll through the valid
entries for the field.
SCAN: ON OFF The SCAN field is used to toggle the scan on and off.
You do this by moving to either the ON or OFF box
and pressing SELECT. The choice that is not
selected appears in a subdued color.
FORCE I/O: ON The FORCE I/O field indicates if any I/O point in the
segments is being forced to a user specified
condition. You can force a point to specific condition
via the I/O point Expansion Window which is
described in Expansion Windows on page 147.
The body of the display is a ladder logic diagram. In the left margin, there is an
indication of the segment number and the rung number of each ladder rung. The
power rails are displayed in red because they always are powered. The rungs and
branches are displayed in red if they have power or white if they do not. The
elements are labeled with the name that was entered for them when the segment was
built. Examine On symbols show either the state of the contact or the data quality of
the input. Timers and counters show either their enable/disable condition or whether
they are still running.
144 3BUR001981R0201
Appendix B Multibus-based TLL Console Support Function Targets on the Segment Display
Function Targets on the Segment Display

When you first access the Segment Display, it has the following function targets.
UNIT OVER Calls up the Unit Overview Display which is used to

monitor TLL and TCL units. It is described in the
Operator's Guide (for Turbo Nodes).
OVER VIEW Calls up the Overview Display which is used to call up
displays, start report processing and change TCL
program statuses. It is described in the Operator's Guide
(for Turbo Nodes).
LOGIC DISPS Calls a second level of function targets to the screen.
Most of these targets are used to call up Runtime
Displays such as the Counter Display and are described
in How to Access the TLL Displays on page 140. The
DETAIL target of this target group is used to get detailed
information about a TLL element and is described in
How to Access Data Structure Display for Program
Element on page 146.
The MORE arrow has the same function as the LOGIC
DISPS target.
GO TO TOP Moves screen to start of segments.
GO TO BOT Moves screen to end of segments.
SGMT LOAD This target is used to add segments to the node or
controller. When the target is selected, an entry field
such as the one below appears on the display.
SEG NO:
You type the number of the segment as it appears on the
Segment Library and press ENTER. The segments must
already exist in a loadable form on the Segment Library
for the node or controller.
The information on the screen does not change after the
load unless the elements on the screen are associated
with the newly loaded segment. Otherwise, you must
use the cursor positioning keys to view the newly loaded
segment.
3BUR001981R0201 145
How to Access Data Structure Display for Program Element Appendix B Multibus-based TLL
SGMT REMOV This target is used to remove segments from the node or
controller. When the target is selected, an entry field
appears on the display. You type the number of the
segment as it appears on the Segment Library and
press ENTER.
FIND ELEM This target is used to specify an element for a search.
When the target is selected, an entry field such as the
one below appears on the display.
SEARCH FOR:
You type the name of the element that you want and
press the ENTER key. If you do not know the full name,
type as much of the name as you know. After you press
the ENTER key, the system searches for the desired
element.
The item you put into the Search buffer stays there until
you replace it with a new item. The system automatically
searches for this item whenever you select the FIND
NEXT target.
FIND NEXT When you select this target, the system searches for the
element that is in the Search buffer. To put an element in
this buffer, select FIND ELEM and answer the prompt.
How to Access Data Structure Display for Program Element

The DETAIL function target, Figure 85, on the second level of function targets can
be used to access the Data Structure Display that contains detailed information for a
ladder element. The general procedure to call up a display is to select DETAIL, then
select the program element.
146 3BUR001981R0201
Appendix B Multibus-based TLL Console Support Expansion Windows
UNIT OVER IO_PT TIMER CNTR REGTR FILE SEQNC DETAIL LAST FETCH
OVER VIEW DISP DISP DISP DISP DISP DISP PAGE MSG ALARM
01 AUG 89 12:23:08
LLSEQDISP
Figure 85. DETAIL Function Target on the Segment Display
Expansion Windows
When you select an element on the Segment Display, an expansion window
containing detailed information for the element appears.
Each expansion window has some items that are changeable. The NEXT FIELD key
on the alphanumeric keyboard can be used to move the cursor from one changeable
field to the next. If the field has discrete entries, the NEXT CHOICE key can be
used to step through the valid entries.
I/O Point Expansion Window

You can change the entry in the DESC, FORC, and AC fields of the I/O point
expansion window, Figure 86.
IO POINT EXPANSION
NAME: BD18
DESC: CONTACT8
AC: OFF
CHAN: 8
TYPE: INPUT
FORC: NOT FORCED
Figure 86. I/O Point Expansion Window
3BUR001981R0201 147
Expansion Windows Appendix B Multibus-based TLL Console Support
Forcing I/O Points

This expansion window allows you to debug segments by specifying states for the
AC parameter of I/O points. However, if you want to change AC, you must first put
the I/O point into a FORCED state. You do this by selecting the FORC field and
changing its value to FORCED. You can now select the AC field and change its
value between ON and OFF. When a point is forced, you determine the value it has
in the segment only. The actual condition of the point in the field is not modified.
The display indicates all points that are forced. For example a point that is not
forced appears as shown in Figure 87.
DI1
103 ][
ON
Figure 87. Example of I/O Point that is not Forced
A point that is forced has a small F displayed with it and appears as shown in
Figure 88.
DI1
103 ][
F ON
Figure 88. Example of Forced I/O Point
Forcing can also be performed via the I/O Point Display which is described in I/O
Point Display on page 156.
Timer Expansion Window

You can change the entries in the DESC, AC, PR, and EN fields of the timer
expansion window, Figure 89. The format for making time entries to the AC and PR
fields is described in TLL Items on CCF and TCL Displays on page 162.
148 3BUR001981R0201
Appendix B Multibus-based TLL Console Support Expansion Windows
TIMER EXPANSION
NAME: TIM2
DESC: TIMER2
AC: 000:00:00.02
PR: 000:00:00.00
EN: ENABLED
DN: DONE
BASE: 0.1 SEC
UPDN: UP
Figure 89. Time Expansion Window
Counter Expansion Window

You can change the entries in the DESC, AC, PR, and EN fields of the counter
expansion window, Figure 90.
COUNTER EXPANSION
NAME: CTR3
DESC: COUNTER3
AC: 2
PR: 15
EN: DISABLED
DN: IN PROG
Figure 90. Counter Expansion Window
Register Expansion Window

You can change the entries in the DESC and AC fields of the register expansion
window, Figure 91.
3BUR001981R0201 149
TLL Device Data Base Summary Displays Appendix B Multibus-based TLL Console Support
REGISTER EXPANSION
NAME: REG3
DESC: REGISTER3
AC: 000:00:00.03
Figure 91. Register Expansion Window
Message Expansion Window

A message expansion window shows the text of the message.
TLL Device Data Base Summary Displays

TLL contains a number of displays that summarize the data structures in the data
base for a device. Each data structure has its own type of display, that is, there are
counter displays, register displays, and so on. Figure 92 shows an example of a
Register Display. This section describes the items these displays have in common.
Register Display on page 153 to Sequencer Display on page 160 describe the
specific characteristics of each of these displays.
LL DEVICE: LLCONT1 Each device data base summary display has an

LL DEVICE field that gives the name of TLL in the
node or controller that contains the data structures. It
is a discrete field that can be used to call up the
corresponding display for other nodes or controllers.
You do this by entering the name of TLL in the node
or controller that you want and pressing the ENTER
key. The NEXT CHOICE key can be used to scroll
through the valid entries for the field.
150 3BUR001981R0201
Appendix B Multibus-based TLL Console Support TLL Device Data Base Summary Displays
LL DEVICE: LLCONT1
REGISTER NAME DESCRIPTION VALUE

REG1 SEQ1 MASK REG 115

01 AUG 89 12:23:08
LLREGISTER
Figure 92. Register Display
3BUR001981R0201 151
Operator Changes are Logged Appendix B Multibus-based TLL Console Support
Operator Changes are Logged

There are several changes that can be made to items on the data base summary
displays. These items are listed in Register Display on page 153 to Sequencer
Display on page 160. Almost all of these changes are loggable. For example, if your
system is configured with a logging printer, a typical message would be:
REG1 SEQ1 MASK REGISTER AC CHANGED FROM 115 TO 315
Function Targets on the TLL Device Data Base Summary Displays

The TLL Device Data Base Summary Displays have roughly the same user interface
which is described in this section. The Sequencer Display has some slightly
different functions. They are described in Sequencer Display on page 160.
UNIT OVER Calls up the Unit Overview Display which is used to

monitor TLL and TCL units. It is described in the
Operator's Guide (for Turbo Nodes).
OVER VIEW Calls up the Overview Display which is used to call up
displays, start report processing and change TCL
program statuses. It is described in the Operator's Guide
(for Turbo Nodes).
LOGIC DISPS Calls a second level of function targets to the screen.
Most of these targets are used to call up Runtime
Displays such as the Counter Display and are described
in How to Access the TLL Displays on page 140.
The MORE arrow has the same function as the LOGIC
DISPS target.
GO TO TOP Moves screen to start of segments.
GO TO BOT Moves screen to end of segments.
152 3BUR001981R0201
Appendix B Multibus-based TLL Console Support Register Display
FIND ELEM This target is used to specify an element for a search.

When the target is selected, an entry field such as the
one below appears on the display.
SEARCH FOR:
You type the name of the element that you want and
press the ENTER key. If you do not know the full name,
type as much of the name as you know. After you press
the ENTER key, the system searches for the desired
element.
The item you put into the Search buffer stays there until
you replace it with a new item. The system automatically
searches for this item whenever you select the FIND
NEXT target.
FIND NEXT When you select this target, the system searches for the
element that is in the Search buffer. To put an element in
this buffer, select FIND ELEM and answer the prompt.
Register Display
The Register Display, Figure 92, contains a list of the registers in the device. Fields
that allow changes are:
VALUE Field
You can change the value in a register by selecting the VALUE field for the register,
typing the new value, and pressing the ENTER key. This is a loggable change.
Counter Display
The Counter Display, Figure 93, contains a list of the counters in the device.
Changes are permitted to the following fields:
VALUE Field
You can change the value of a counter by selecting the VALUE field for the counter,
typing the new value, and pressing the ENTER key. This is a loggable change.
3BUR001981R0201 153
Counter Display Appendix B Multibus-based TLL Console Support
PRESET Field
You can change the preset of a counter by selecting the PRESET field for the
counter, typing the new value, and pressing the ENTER key. This is a loggable
change.
LL DEVICE: LLCONT1
COUNTER NAME DESCRIPTION PRESET VALUE

CTR1 COUNTER1 5 0
CTR2 COUNTER2 10 0
CTR3 COUNTER3 15 2

01 AUG 89 12:23:08
LLCOUNTER
Figure 93. Counter Display
154 3BUR001981R0201
Appendix B Multibus-based TLL Console Support Timer Display
Timer Display
The Timer Display, Figure 94, contains a list of the timers in the device.
LL DEVICE: LLCONT1
TIMER NAME DESCRIPTION PRESET VALUE ENABLE

TIM1 TIMER1 0000:00:10.00 0000:00:00.00 NO
TIM2 TIMER2 0000:00:00.02 0000:00:00.02 NO
TIM3 TIMER3 0000:00:00.30 0000:00:00.00 NO
TIM_DN DOWN TIMER 0000:00:00.30 0000:00:00.00 NO

01 AUG 89 12:23:08
LLTIMER
Figure 94. Timer Display
3BUR001981R0201 155
I/O Point Display Appendix B Multibus-based TLL Console Support
Changes are allowed to the following three fields:
PRESET Field
VALUE Field
The PRESET and VALUE fields are displayed to the hundredth place. For example,
001:20:15.25 is one hour, twenty minutes, fifteen and twenty five hundredths
seconds. The format for making time entries is described in TLL Items on CCF and
TCL Displays on page 162. Your entry should be within the resolution of the time
base. If it is not, the system automatically rounds it to the nearest multiple of the
time base. The changes are logged.
ENABLE Field
This field is used to enable and disable the timer. The possible entries are YES and
NO. The changes are logged.
I/O Point Display

The I/O Point Display, Figure 95, contains a list of the I/O points of the node or
controller.
156 3BUR001981R0201
Appendix B Multibus-based TLL Console Support I/O Point Display
LL DEVICE: LLCONT1
POINT DESCRIPTION STATUS FORCED

DI1 CONTACT1 CLOSED NO
DI4 CONTACT4 OPEN NO
DO1 COIL1 OFF NO
DO2 COIL2 OFF NO
DO3 COIL3 ON NO
DO4 COIL4 OFF NO
DO5 COIL5 OFF NO
DO6 COIL6 OFF NO
DO7 COIL7 OFF NO
DO8 COIL8 OFF NO

01 AUG 89 12:23:08
LLIOPOINT
Figure 95. I/O Point Display
3BUR001981R0201 157
File Display Appendix B Multibus-based TLL Console Support
The changeable fields are:
STATUS Field
The STATUS field gives the current value of the AC parameter of the point. It can be
either Open or Closed for a contact, or On or Off for a coil. When FORCED = YES
status changes are not sent to the actual I/O point. Changes to the status are
loggable.
FORCED Field
When the FORCED field for a point contains YES, you can determine the value of
its status as it affects the segment. The status change is not sent to the actual I/O
point. This is used to run TLL in simulation mode.
FORCED = NO is the normal state. When the FORCED field contains NO, I/O
changes are sent to the actual I/O point. Changes to this field are not logged.
File Display
Each file in the device has a File Display which lists its items, Figure 96. These
displays have a slightly different interface from the other data summary displays.
You can switch to the display for the next file in the device by pressing the PAGE
FORW key on the keyboard. Similarly, the PAGE BACK key takes you to the
previous file.
You can also move from file to file with the FIND ELEM target. When you select it,
the following field appears.
DATA FILE NAME:
Type the name of the file that you want and press the ENTER key.
You can change the values of the items in the file. All changes are logged. The
NEXT FIELD key can be used to move the cursor from one item to the next.
158 3BUR001981R0201
Appendix B Multibus-based TLL Console Support File Display
LL DEVICE: LLCONT1
DATA FILE: DF1 DESCRIPTION: DATA FILE 1
ITEM VALUE ITEM VALUE ITEM VALUE ITEM VALUE

1 1 33 0 65 0 97 1
2 5 34 0 66 0 98 5
3 14 35 0 67 0 99 14
4 222 36 0 68 0 100 222
5 3412 37 0 69 0 101 3412
6 867 38 0 70 0 102 867
7 900 39 0 71 0 103 900
8 65555 40 0 72 0 104 65555
9 5643 41 0 73 0 105 5643
10 55 42 0 74 0 106 55
23 6 55 0 87 0 119 6
24 0 56 0 88 0 120 0
25 0 57 0 89 0 121 0
26 0 58 0 90 0 122 0
27 0 59 0 91 0 123 0
28 0 60 0 92 0 124 0
29 0 61 0 93 0 125 0
30 0 62 0 94 0 126 0
31 0 63 0 95 0 127 0
32 0 64 0 96 0 128 0

01 AUG 89 12:23:08
LLDATAFILE
Figure 96. File Display
3BUR001981R0201 159
Sequencer Display Appendix B Multibus-based TLL Console Support
Sequencer Display
Sequencer Displays, Figure 97, have multiple pages with one page for each step in
the sequencer. These displays have a slightly different interface from the other data
summary displays. The SCROLL UP key takes the screen to the next step of the
sequencer. The Scroll DOWN takes it to the previous step. You can switch to the
display for the next sequencer in the device by pressing the PAGE FORW key on the
keyboard. Similarly, the PAGE BACK key takes you to the previous sequencer.
You can also move from sequencer to sequencer with the FIND ELEM target. When
you select it, the following fields appear.
SEQUENCER NAME: STEP NO:
Enter the required information into the fields and press the ENTER key.
160 3BUR001981R0201
Appendix B Multibus-based TLL Console Support Sequencer Display
LL DEVICE: LLCONT1
ITEM I/O POINT NAME ITEM I/O POINT NAME

1 DO4 17
2 DO3 18
3 DO2 19
4 DO1 20
5 21
6 22
7 23
8 24
9 25
10 26
11 27
12 28
13 29
14 30
15 31
16 32

01 AUG 89 12:23:08
LLSEQUENCER
Figure 97. Sequencer Display
3BUR001981R0201 161
TLL Items on CCF and TCL Displays Appendix B Multibus-based TLL Console Support
TLL Items on CCF and TCL Displays

The values of the parameters of TLL counters, timers, I/O points, and registers can
appear in the group status blocks on the standard CCF and TCL displays as shown
by Figure 98.
FC110 TC115
BC-R101 FLOW R101 FO TEMP
#/HR DEGC
SP 5000.0L SP 100.00L
MV 9156.0 MV H124.10
OP 10.500A OP 73.900A
FC112 PM116
X-101 FLOW PUMP 116
#/HR COM OFF
SP 9900.0L MODE AUTO
MV 13563 STATE OFF
OP 55.800A
COIL3 F_COUNT_2
OUT1-SEG4 REC2_COUNT
OUTPUT ON P 106
C 99
EN DN
SEQ2_TIM1 MASK_REG4
ELAP_TIME SEQ4_REG
P 000:01:24.00 R 94
T 000:01:23.15
DISAB
UNIT OVER AREA GROUP ALARM TREND STATUS GRAPH DETAIL LAST FETCH
OVER VIEW PAGE MSG ALARM
14 SEP 89 14:22:39
GROUP TREND
Figure 98. Group Trend Display that Contains TLL Information
162 3BUR001981R0201
Appendix B Multibus-based TLL Console Support TLL Items on CCF and TCL Displays
You can use the DETAIL target to get further information about these data
structures. For example, if you selected the DETAIL target and then selected the
block for counter F_COUNT_2, a Counter Display that contains information for
F_COUNT_2 comes to the screen. The Counter Display and the other TLL Device
Data Base Summary Displays are described in TLL Device Data Base Summary
Displays on page 150.
You can also change the parameters of the TLL items by bottom line entry. For
example if you select the block for timer SEQ2_TIM1, the bottom line shown in
Figure 99 appears.
SEQ2_TIM1 LAST FETCH

ELAP_TIME PAGE MSG ALARM
TIME ENAB PR 14 SEP 89 14:22:39
000:01:23.15 DISAB 000:01:24.00 CLEAR GROUP TREND
Figure 99. Changing TLL Parameters by Bottom Line Entry
You can enable or disable the timer by choosing the appropriate target. This change
is sent to the system as soon as you make the selection. You can also change the
time value and the preset value. You do this by selecting the field, typing the new
value, and pressing the ENTER key. Changes to numeric parameters do not go into
effect until ENTER is pressed.
3BUR001981R0201 163
TLL Items on CCF and TCL Displays Appendix B Multibus-based TLL Console Support
Time entries can be made in the following formats:

One colon preceded by one or two digits means minutes and seconds.
Examples:
30:05 30 minutes 5 seconds
12:4 12 minutes 40 seconds
One colon preceded by three digits means hours and minutes.
Example:
010:15 10 hours 15 minutes
Two colons indicate hours and minutes.
Examples:
8:07: 8 hours, 7 minutes
12:16:10.2 12 hours, 16 minutes, 10.2 seconds
A period indicates seconds.
Examples:
6. 6 seconds
.5 .5 seconds
164 3BUR001981R0201
INDEX
Symbols load procedure 114

-( )- OUTPUT softkey 127 save procedure 111
-(-)- SUB softkey 130 accessing
-(+)- ADD softkey 129 Data softkey set 127
-(÷)- DIV softkey 130 Data Structure Display for element 146
(CTD) DOWN softkey 131 expansion window for element 147
(CTP) PRESET softkey 131 Extended softkey set 131
(CTR) RESET softkey 131 first level of Data softkeys 129
(CTU) UP softkey 131 first level of Extended softkeys 133
-(L)- LATCH softkey 127 ladder logic editor 107
(MCR) MCONT softkey 132 ladder logic editor from Segment Library
(MSG) MESG softkey 133 Display 117
(NCL) EXZONE softkey 132 Math softkey set 129
(NCR) EXCONT softkey 132 Overview Display from Segment Display 145
(RTO) RET ON softkey 131 Overview Display from TLL Device Data Base
(RTR) RESET softkey 131 Summary Displays 152
(TON) ON softkey 130 Relay softkey set 126
-(U)- UNLTCH softkey 127 second level function targets on Segment
-(X)- MULT softkey 130 Display 145
(ZCL) ZONE softkey 132 second level function targets on TLL Device
-[<=]- LTEQ softkey 129 Data Base Summary Displays 152
-[<]- LT softkey 128 second level of Data softkeys 128
-[=]- EQUAL softkey 128 second level of Extended softkeys 132
-[>=]- GTEQ softkey 129 Segment Display from Device Directory
-[>]- GT softkey 128 Display 144
-[G]- GET softkey 127 softkeys for inserting elements into ladder 122
-[GET]- GET DB softkey 127 softkeys for segment creation, deletion,
-[P]- PUT softkey 127 duplication, and loading 108
-] [- XON softkey 121, 126 softkeys to insert counter instructions 123
-]/[- XOFF softkey 126 softkeys to insert data manipulation
instructions 122
A softkeys to insert file to file transfer
aborting instructions 123
3BUR001981R0201 165
Index
softkeys to insert math instructions 123 BLOCK field 41

softkeys to insert message instructions 123 bottom line entry 140
softkeys to insert register to file transfer branch 63
instructions 123 adding 119
softkeys to insert relay instructions 122 deleting 135
softkeys to insert sequencer transfer BRANCH softkey 119, 127
instructions 123
softkeys to insert timer instructions 123 C
softkeys to insert zone control instructions 123 calling up
Timer/Counter softkey set 130 Segment Display 101
TLL displays 140 Segment Library 101
TLL displays via bottom line entry 140 Segment Library from Device Directory 104
TLL displays via function targets 140 CCF Standard Displays 24
TLL displays via Overview Displays 142 CCF templet 58
TLL displays via page links 142 CH# field 41
TLL displays via PSAPs changing parameters of TLL items on CCF or TCL
TLL variables from CCF FCMs 58 display 163
Unit Overview Display from Segment CHANNEL PATH field 45
Display 145 coil 67
Unit Overview Display from TLL Device Data Compare Equal instruction 76
Base Summary Displays 152 Compare Greater Than instruction 77
Add instruction 78 Compare Greater Than or Equal To instruction 77
Add symbol 129 Compare Less Than instruction 76
adding Compare Less Than or Equal To instruction 77
branch to rung 119 Configuration Area templet 28, 71
comment to rung 121 configuring
instructions to rung 121 access to Device Directory display on Advant
items to the Device Directory Display 101 Station Operator Station 35
rung to diagram 118 access to Device Directory display on Multibus
segments to node or controller 145 console 34
AREA, see Configuration Area templet 28 access to TLL Device Directory Display 34
AUTO LOAD DEVICE field 38 Console Library Configurator templet 34 to 35
Auto Load Display 23 Console Resident Displays 24
contact 67
B Controller templet 29
backing up segments to another disk 110 COPY softkey 109, 125
BACKWARD softkey 126, 133 copying
BCD -> BIN instruction 80 portion of segment into paste buffer 125
BCD -> BINARY softkey 130 segment 109
BCD to Binary symbol 130 Count Down instruction 84
166 3BUR001981R0201
Index
Count Down symbol 131 -[>=]- GTEQ softkey 129

Count Up instruction 83 -[>]- GT softkey 128
Count Up symbol 131 -[G]- GET softkey 127
Counter Display 24, 153 -[GET]- GET DB softkey 127
counter expansion window 149 -[P]- PUT softkey 127
counter instructions 83 MORE softkey 128 to 129
Count Down 84 defining
Count Up 83 units for the TLL messages 29
Counter Preset 85 units for TLL error messages 33
Counter Reset 85 DELETE softkey 102, 108
Counter Preset instruction 85 deleting
Counter Preset symbol 131 blank line 134
Counter Reset instruction 85 branch line 134
Counter Reset symbol 131 elements other than output from line 134
counters 68 entire rung 134
CREATE softkey 101, 108 from the current cursor position to end of
creating line 134
auto load list for node or controller 102 item from Device Directory Display 102
new segment 108 segment from library 108
cursor movement in ladder logic editor 133 whole branch 135
CUT softkey 125 DESC field 55
cutting portion of segment to paste buffer 125 DESCRIPTION field 41, 43 to 44, 47, 49, 51, 56
DETAIL target 146, 163
D Device Directory 23
DATA FILE NAME field 158 Device Directory Display 25, 34, 98
DATA KEYS softkey 122, 127 DEVICE LIB softkey 107
data manipulation instructions 75 DEVICE NAME field 33
Compare Equal 76 digital input 67
Compare Greater Than 77 display movement in ladder logic editor 133
Compare Greater Than or Equal To 77 displaying
Compare Less Than 76 additional information on Segment Library
Compare Less Than or Equal To 77 Display 107
Get 75 detailed information for TLL item on CCF or
Get Data Base 75 TCL display 163
Put 75 Divide symbol 130
Data Processor Resident Displays 23 Division instruction 79
Data softkey set 127 Documentation, On-line 17
-[<=]- LTEQ softkey 129
-[<]- LT softkey 128 E
-[=]- EQUAL softkey 128 EDIT SEG softkey 107, 117
3BUR001981R0201 167
Index
editing segment 107 file instructions 86

ENABLE field 156 File to File Move 87
End of Master Control Reset instruction 90 File to Register Move 87
End of Master Control Reset symbol 132 Register to File Move 86
End of Zone Control Last State instruction 90 File to File Move instruction 87
End of Zone Control Last State symbol 132 File to File Move symbol 132
Equal symbol 128 File to Register Move instruction 87
Examine Off instruction 73 File to Register Move symbol 132
Examine Off symbol 126 FILES softkey 108, 112
Examine On instruction 73 FIND ELEM target 146, 153, 158, 160
Examine On symbol 126 FIND NEXT target 146, 153
execution order 62 FORCE I/O field 144
exiting FORCED field 158
ladder logic editor without saving changes 123 forcing I/O points 148
Segment Library Display 107 FORMAT FD00 112
EXPORT field 40, 44, 46, 49, 51 formatting floppy disk 112
EXTDED KEYS softkey 123, 131 FORWARD softkey 126, 133
Extended softkey set 131 function targets 140
(MCR) MCONT softkey 132
(MSG) MESG softkey 133 G
(NCL) EXZONE softkey 132 Generic DPSS templet 29
(NCR) EXCONT softkey 132 Get Data Base instruction 75
(ZCL) ZONE softkey 132 Get Data Base symbol 127
FILE -> FILE softkey 132 Get instruction 75
FILE -> REG softkey 132 Get symbol 127
MORE softkey 132 to 133 GO TO BOT target 142, 145, 152
QUIT softkey 131 to 132 GO TO TOP target 142, 145, 152
REG -> FILE softkey 131 GRAY -> BIN instruction 80
SEQNCR INPUT softkey 132 GRAY -> BINARY softkey 130
SEQNCR LOAD softkey 132 Gray to Binary symbol 130
SEQNCR OUTPUT softkey 132 Greater Than or Equal To symbol 129
External Display Access Add dialog 35 Greater Than symbol 128
F I
file 71 I/O Point Display 156
FILE -> FILE softkey 132 I/O point expansion window 147
FILE -> REG softkey 132 I/O POINT NAME field 44, 58
File Display 24, 158 Implementing TLL 25
DATA FILE NAME field 158 INITIAL OUTPUT field 45
FIND ELEM target 158 INITIAL VALUE field 51
168 3BUR001981R0201
Index
INITOUT field 42 TYPE field 41

INSERT RUNG softkey 118 VENDOR field 40
inserting Ladder Logic I/O_2 templet 43
blank line into segment 122 CHANNEL PATH field 45
blank rung 134 DESCRIPTION field 44
ITEM field 55, 58 EXPORT field 44
INITIAL OUTPUT field 45
L TEMPLET NAME field 44
Ladder Logic Counter templet 48, 68 TYPE field 45
DESCRIPTION field 49 VENDOR field 44
EXPORT field 49 Ladder Logic Message templet 52, 71
NAME field 49 MESSAGE NUMBER field 53
PRESET field 49 MESSAGE TEXT field 53
TEMPLET NAME field 49 PRIORITY field 53
Ladder Logic Device templet 36 TEMPLET NAME field 52
AUTO LOAD DEVICE field 38 UNIT ID field 53
MAXIMUM # OF SEGMENTS field 38 Ladder Logic Register templet 50, 70
SCAN RATE IN MSEC field 37 DESCRIPTION field 51
TEMPLET NAME field 37 EXPORT field 51
Ladder Logic Editor 25, 107 INITIAL VALUE field 51
Ladder Logic Editor Display 116 REGISTER NAME field 51
Ladder Logic File templet 54 TEMPLET NAME field 50
DESC field 55 Ladder Logic Sequence I/O templet 44, 57, 71
ITEM field 55 I/O POINT NAME field 44, 58
TEMPLET NAME field 54 ITEM field 58
VALUE field 55 STEP NUMBER field 57
Ladder Logic Files templet 71 TEMPLET NAME field 57
Ladder Logic I/O 2 templet 42 Ladder Logic Sequence templet 56, 71
Ladder Logic I/O Group templet 42 DESCRIPTION field 56
DESCRIPTION field 43 TEMPLET NAME field 56
TEMPLET NAME field 43 Ladder Logic support for
Ladder Logic I/O templet 39, 67 PROFIBUS I/O 42 to 44
BLOCK field 41 S800 I/O 42 to 44
CH# field 41 Ladder Logic Timer templet 45, 69
DESCRIPTION field 41 DESCRIPTION field 47
EXPORT field 40, 44 EXPORT field 46
INITOUT field 42 PRESET field 47
LAN field 41 TEMPLET NAME field 46
NAME field 40 TIME BASE field 47
TEMPLET NAME field 40 TIMER NAME field 47
3BUR001981R0201 169
Index
UP OR DOWN field 48 Subtraction 78

LAN field 41 MATH KEYS softkey 123, 129
Less Than or Equal To symbol 129 Math softkey set 129
Less Than symbol 128 -(-)- SUB softkey 130
LIB softkey 101, 104 -(+)- ADD softkey 129
LIST BACKUP softkey 112 to 113, 115 -(÷)- DIV softkey 130
LIST LIBRARY softkey 112, 115 -(X)- MULT softkey 130
listing segments on backup disk 112 to 113, 115 BCD -> BINARY softkey 130
LL DEVICE field 144, 150 GRAY -> BINARY softkey 130
LL_CNTR, see Ladder Logic Counter templet QUIT softkey 129
LL_DEV, see Ladder Logic Device templet MAXIMUM # OF SEGMENTS field 38
LL_FILE, see Ladder Logic File templet message expansion window 150
LL_I_O, see Ladder Logic I/O templet message instructions 91
LL_I_O_2, see Ladder Logic I/O_2 templet MESSAGE NUMBER field 53
LL_MSG, see Ladder Logic Message templet Message routing 28
LL_REG, see Ladder Logic Register templet Message symbol 133
LL_SEQ, see Ladder Logic Sequence templet MESSAGE TEXT field 53
LL_SEQIO, see Ladder Logic Sequence I/O templet messages 70
LL_TIMER, see Ladder Logic Timer templet MODIFY softkey 122
LLIO_GRP, see Ladder Logic I/O Group templet modifying existing element 122
LOAD ALL softkey 114 MORE (arrow) target 145, 152
LOAD LIST softkey 102 MORE softkey 118, 128 to 129, 132 to 133
LOAD SEGMNT softkey 113 moving
LOAD softkey 112 cursor to beginning rung position and selecting
loading it 133
all segments 114 cursor to element in line above 133
individual segment 113 cursor to element in line below 133
segment from another disk 112 cursor to end of segments on Segment
segments to node or controller 145 Display 145
LOGIC DISPS target 145, 152 cursor to end of segments on TLL Device Data
Base Summary Display 152
M cursor to first rung of file and setting cursor
Master Control Reset instruction 90 mode forward 134
Master Control Reset symbol 132 cursor to last element of file and setting cursor
math instructions 78 mode backward 134
Add 78 cursor to next element 133
BCD -> BIN 80 cursor to output element and selecting it 133
Division 79 cursor to preceding element 133
GRAY -> BIN 80 cursor to start of segments on Segment
Multiplication 79 Display 145
170 3BUR001981R0201
Index
cursor to start of segments on TLL Device Data PASTE softkey 126

Base Summary Display 152 pasting information from buffer into ladder 126
display back by one half page 134 position eight 61
display back by one page 134 power rails 61
display forward by one half page 133 PRESET field 47, 49, 154, 156
display forward by one page 134 PRINT SEG softkey 107
display to beginning of information 142 printing segment 107
display to end of information 142 PRIORITY field 53
multi-line rung 63 PROFIBUS I/O 42 to 44
multiple configurators 40, 44 PSAPs, see Page Selection and Alarm Panels
Multiplication instruction 79 Put instruction 75
Multiply symbol 130 Put symbol 127
putting
N TLL display callup blocks on Overview
NAME field 40, 49 displays and PSAPs 59
TLL information on standard runtime
O displays 59
On-line Documentation 17
output 67 Q
Output Energize instruction 74 QUIT EDITOR softkey 123
Output Energize symbol 127 QUIT softkey 107, 111, 114, 129 to 132
Output Latch instruction 74 quitting
Output Latch symbol 127 load procedure 114
Output Unlatch instruction 74 save procedure 111
Output Unlatch symbol 127
OVER VIEW target 145, 152 R
OVER WRITE softkey 111 to 112, 114 to 115 RECIPE DEVICE NAME field 32
Overview Displays 142 REG -> FILE softkey 131
overwrite Register Display 153
all segments while loading 115 register expansion window 149
all segments while saving 112 REGISTER NAME field 51
existing segment while loading 114 Register to File Move instruction 86
existing segment while saving 111 Register to File Move symbol 131
registers 70
P RELATIVE DEVICE NAME field 33
PAGE BACK softkey 107 relay instructions 73
PAGE FORW softkey 107 Examine Off 73
page links 142 Examine On 73
Page Selection and Alarm Panels 142 Output Energize 74
PARENT NAME field 32 Output Latch 74
3BUR001981R0201 171
Index
Output Unlatch 74 page up one line 134

RELAY KEYS softkey 119, 122, 126 SEARCH FOR field 146, 153
Relay softkey set searching
-( )- OUTPUT softkey 127 for character string 135
-(L)- LATCH softkey 127 for element 146, 153
-(U)- UNLTCH softkey 127 for next instance of element 146, 153
-] [- XON softkey 126 SEG DISPLY softkey 101, 144
-]/[- XOFF softkey 126 SEG NO. field 145
BRANCH softkey 127 segment 61
REMARK softkey 121 copying 109
removing creating new 108
item from Device Directory Display 102 editing 107
segments from node or controller 146 printing 107
restoring segment from another disk 112 Segment Display 24 to 25, 137, 143
Retentive Timer On instruction 82 DETAIL target 146
Retentive Timer On symbol 131 fields 144
Retentive Timer Reset instruction 83 FIND ELEM target 146
Retentive Timer Reset symbol 131 FIND NEXT target 146
returning to main softkeys 129 to 132 GO TO BOT target 145
returning to Segment Library Display 112, 115 GO TO TOP target 145
rung 61 LOGIC DISPS target 145
adding 118 MORE (arrow) target 145
adding comment 121 OVER VIEW target 145
adding instruction 121 SEARCH FOR field 146
SEG NO. field 145
S SGMT LOAD target 145
S800 I/O 42 to 44 SGMT REMOV target 146
SAVE ALL softkey 111 UNIT OVER target 145
SAVE SEGMNT softkey 110 Segment Library 24 to 25
SAVE softkey 110, 123 Segment Library Display 104
saving displaying additional information 107
all segments 111 exiting 107
individual segment 110 selecting segment 106
segments to another disk device 110 selecting segment on Segment Library Display 106
saving, compiling and locating errors in SEQNCR INPUT softkey 132
segment 123 SEQNCR LOAD softkey 132
SCAN field 144 SEQNCR OUTPUT softkey 132
SCAN RATE IN MSEC field 37 Sequence Detail Display 24, 29
scrolling sequencer 71
page down one line 134 Sequencer Display 160
172 3BUR001981R0201
Index
FIND ELEM target 160 Timer On instruction 81

SEQUENCER NAME field 160 Timer On symbol 130
STEP NO. field 160 Timer/Counter softkey set 130
Sequencer Input instruction 88 (CTD) DOWN softkey 131
Sequencer Input symbol 132 (CTP) PRESET softkey 131
sequencer instructions 88 (CTR) RESET softkey 131
Sequencer Input 88 (CTU) UP softkey 131
Sequencer Load 89 (RTO) RET ON softkey 131
Sequencer Output 88 (RTR) RESET softkey 131
Sequencer Load instruction 89 (TON) ON softkey 130
Sequencer Load symbol 132 QUIT softkey 130
SEQUENCER NAME field 160 TIMER/COUNTR softkey 123, 130
Sequencer Output instruction 88 timers 69
Sequencer Output symbol 132 TLL Device Data Base Summary Displays 24, 137,
setting search direction 126 150
SGMT LOAD target 145 Counter Displays 137
SGMT REMOV target 146 File Displays 137
skip FIND ELEM target 153
copying segment while loading 114 FIND NEXT target 153
copying segment while saving 111 GO TO BOT target 152
SKIP COPY softkey 111, 114 GO TO TOP target 152
STATUS field 158 logging operator changes 152
STEP NO. field 160 LOGIC DISPS target 152
STEP NUMBER field 57 MORE (arrow) target 152
Subtract symbol 130 OVER VIEW target 152
Subtraction instruction 78 SEARCH FOR field 153
UNIT OVER target 152
T TLL items on CCF Displays 162
TCL billboard messages 28 TLL items on TCL Displays 162
TCL Standard Displays 24 TYPE field 41, 45
TEMPLET NAME field 32, 37, 40, 43 to 44, 46, 49
to 50, 52, 54, 56 to 57 U
TIME BASE field 47 undeleting previously deleted rung, branch or
Timer Display 155 element 135
timer expansion window 148 UNIT DESCRIPTOR field 33
timer instructions 81 Unit Detail Display 24, 29
Retentive Timer On 82 UNIT ID field 53
Retentive Timer Reset 83 Unit Master templet 29
Timer On 81 DEVICE NAME field 33
TIMER NAME field 47 PARENT NAME field 32
3BUR001981R0201 173
Index
RECIPE DEVICE NAME field 32

RELATIVE DEVICE NAME field 33
TEMPLET NAME field 32
UNIT DESCRIPTOR field 33
Unit Message Display 24, 29
UNIT OVER target 145, 152
UNITMAST, see Unit Master templet
UP OR DOWN field 48
user security 60, 139
V
VALUE field 55, 153, 156
VENDOR field 40, 44
VERIFY MODE softkey 112, 115
verifying
overwriting or skipping segment while
loading 115
overwriting or skipping segment while
saving 112
viewing information on TLL Displays 142
Z
Zone Control Last State instruction 90
Zone Control Last State symbol 132
174 3BUR001981R0201
3BUR001981R0201 Litho in U.S.A. July 2002
Copyright © 2002 by ABB. All Rights Reserved
® Registered Trademark of ABB.
™ Trademark of ABB.
http://www.abb.com/control
Automation Technology Products Automation Technology Products Automation Technology Products

Wickliffe, Ohio, USA Västerås, Sweden Mannheim, Germany
www.abb.com/processautomation www.abb.com/processautomation www.abb.de/processautomation
email: industrialitsolutions@us.abb.com email: processautomation@se.abb.com email: marketing.control-products@de.abb.com

TLL Manual PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

TLL Manual PDF

Încărcat de

Drepturi de autor:

Formate disponibile

Taylor™ Ladder Logic (TLL) User’s Guide

(Supports AdvaBuild® Versions 2.7 to 3.3)

Copyright © 2002 ABB Inc.

Advant, AdvaBuild, AdvaCommand, and AdvaInform are registered trademarks of ABB

VAX/VMS is a trademark of Digital Equipment Corporation.

HP and all HP products are registered trademarks of Hewlett Packard Company.

PROFIBUS is a trademark of PROFIBUS International (P.I.).

About This Book

Section 2 - Configuration Requirements for TLL

RELATIVE DEVICE NAME Field.................................................... 33

TYPE Field ......................................................................................45

DESC Field ...................................................................................... 55

Section 3 - Program Structure and Program Instructions

-(L)- Output Latch..............................................................................74

Sequencer Input .................................................................................. 88

Section 4 - Interface to Other Applications

Appendix A - Multibus-based Program Development and

To Display Additional Information ...................................................107

Math Softkeys .................................................................................................... 129

Appendix B - Multibus-based TLL Console Support

VALUE Field ....................................................................................153

Use of Warning, Caution, Information, and Tip

Caution indicates important information or warning related to the

Information alerts the reader to pertinent facts and conditions.

• System prompts/messages are shown in the Courier font, and user

CCF configuration is required for TLL, but it must have a slower

The Multibus-based Ladder Logic Editor is not supported on the

TLL Executes in Turbo Nodes and Controllers

Figure 1. TLL Functional Block Diagram

Node that Contains TLL Configuration

TLL Data Processor Resident Displays

CCF and TCL Standard Displays

TLL Console Resident Displays

Steps to Implement TLL in Your System

• Templets for Nodes/Controllers That Execute TLL on page 36 describes the

TLL Message Configuration

Message Routing on the Configuration Area Templet

Figure 2. TLL Message Routing Entries on a Configuration_Area Templet

Defining Units for the TLL Messages

Figure 3. Unit_Master Templet, Upper Portion

Figure 4. Unit_Master Templet, Middle Portion

Figure 5. Unit_Master Templet, Lower Portion

TEMPLET NAME Field

RECIPE DEVICE NAME Field

UNIT DESCRIPTOR Field

DEVICE NAME Field

RELATIVE DEVICE NAME Field

Defining Units for TLL Load Error Messages

How to Configure Access to TLL Device Directory

Configuring Access on a Multibus-based Console

Configuring Access on an Advant Station Operator Station

External Display Name For External Display Name, enter: LadderLogic

Templets for Nodes/Controllers That Execute TLL

Other Templets for the

Ladder Ladder Ladder Ladder Ladder Ladder Ladder

Figure 6. Templet Hierarchy for the TLL Templets

Ladder Logic Device Templet

Figure 7. Ladderlogic_Device Templet

Entries to the following fields are required:

TEMPLET NAME Field

SCAN RATE IN MSEC Field

n a number of milliseconds. The fastest possible scan rate is 20 mSec.

MAXIMUM # OF SEGMENTS Field