Remote Automation Solutions Bristol ACCOL Workbench User Manual Manuals & Guides

sto

abcock

ACCOL Workbench

User Manual

Bri

Version: 8.3 D4051 – September, 2004

l B

NOTICE

The information in this document is subject to change without notice.
Every effort has been made to supply complete and accurate information.
However, Bristol Babcock assumes no responsibility for any errors that
may appear in this document.

Bristol Babcock does not guarantee the accuracy, sufficiency or suitability
of the software delivered herewith. The Customer shall inspect and test
such software and other material s to his/her satisfaction before u sing them
with important data.

There are no warranties, expressed or implied, including those of
merchantability and fitness for a particular purpose, concerning the
software and other materials delivered herewith.

Additional copies of instruction manuals may be ordered from the address
below per attention of the Sales Order Processing Department. List the
instruction book numbers or give the complete mod el, serial or software
version number. Furnish a return add ress that includes the name of the
person who will receive the material. Billing for extra copies will be
according to current pricing schedules.

ACCOL is a trademark and Bristol is a registered trademark of Bristol
Babcock. Other trademarks or copyrighted products mentioned in this
document are for information only, and belong to their respective
companies, or trademark holders.

Copyright (c) 2004, Bristol Babcock, 1100 Buckingham St., Watertown,
CT 06795. No part of this manual may be reproduced in any form without
the express written permission of Bristol Babcock.

SECTION 2 – ODD HEADER

A Few Words About Bristol Babcock

For over 100 years, Bristol has been pro viding innovative solutions for the measurement and
control industry. Our product lines range from simple analog chart recor der s, to so phisticated
digital remote process contr ollers and flow computers, all the way to turnkey SCADA systems.
Over the years, we have become a leading supplier to t he electro nic gas measurement, water
purification, and wastewat er treatment industries.

On off-shore oil platforms, on natural gas pipelines, and maybe even at yo ur local water company,
there are Bristo l Babcock instruments, cont r ollers, and systems running year-in and year-out to
provide accurate and timely data to our customers.

Getting Additional Information

In addition to the info r mation contained in this manual, you may receive additional assistance in
using t his product from the following sources:

Help Files / Release Notes

Many Bristo l Babcock softwar e pr oducts incorporate help screens. In addit ion, t he so ftwar e
t ypically include s a ‘read me ’r elease note s file detailing ne w fe ature s in the p rod uct, as well as
o th er info rma tion which w as available too late for inclusio n in the manual.

Contacting Bristol Babcock Directly

The address for our world headquarters is:

Bristol Babcock
1100 Buckingham Street
Watertown, Connecticut 06795 USA

Our main phone numbers are: [phone]

[phone] (FAX)

Regular office hours are Monday through Friday, 8:00AM to 4:30PM Eastern Time, excluding
holidays, and scheduled facto r y shutdowns. Dur ing other ho ur s, callers may leave messages using
Bristol's voic e mail system.

Telephone / E-Mail Support - Technical Questions

During regular business hours, Bristol Babcock's Application Suppor t Group can provide
telephone/e-mail support for your technical questions.

i

2/2004

SECTION 2 – EVEN HEADER

Please refer t o the table, below, for a list of products, and their associated technical support
contact information:

Product Support Phone

Number(s):

Contr olWave series (hardware a nd software) [phone]

[phone]
Network 3000 hardware except for TeleFl ow
series

TeleFlow series (3530-xx) [phone].

ACCOL, Open BSI, U OI, all other software
except for ControlWave and OE.

OpenEnterprise (OE) software [phone]

Radio telemetry services (interfacing Bristol
Babcock hardware to radios)

[phone]

[phone]

[phone]

[phone].

E-Mail Address:

[e-mail]

[e-mail]

[e-mail]

[e-mail]

[e-mail]

[e-mail]

The Application Support Group also maintains an area for registered users of our web site that
includes technical support information. Go to: www.bristolbabcock.com/services/

Telephone / E-Mail Support - Non-Technical Questions, Product Orders, etc.

Questions of a non-technical nature (p r oduct o r der s, literature r equests, price and delivery
information, etc.) should be directed to t he nearest sales office (listed on the back cover of this
manual) or to your Bristol-aut ho r ized sales representative. Please call the main Bristol Babcock
number (860-945-2200) if you ar e unsure which office covers your particular area.

Visit our Site on the World Wide Web

For general information about Bristol Babcock and its products, please visit our site on the World
Wide Web a t: www.bristolbabcock.com

Tra ining Courses

Bristol Babco ck ’s Tr aining D epar tment offers a wide variety of co urse s in B ris tol hardware and
software at our Watertown, Connecticut headquarters, and at selected Bristol regional offices,
throughout the year. Contact o ur T r aining Department at [phone] for cour se information,
enrollme nt , pricing, and sche du les.

2/2004 ii

Who Should Read This Manual?

This manual is intended for the ACCOL programmer, who will be using ACCOL
Workbench to create an ACCOL source file.

It assumes familiarity with the following subjects:

!

!

!

The ACCOL II programming language. See An Introduction to ACCOL
(document# D4056) and the ACCOL II Referen ce Manua l (document# D4044)
for details.

Use of personal computers, the DOS operating system, and the Windows™
user-environment. Users should be familiar with how to point and click with
a mouse, how to dou ble-cli ck, how to en ter data i n dia log box es, and how to
use scroll bars, list boxes, pull down menus, etc. See your Windows™
documentation fo r details o n these subjects.

Open BSI Utilities software, which is necessary for downloading, and on-line
communication. See the Open BSI Utilities Manual (document# D5081) for
details.

Variations between Windows™ Versions

The screens presented in this manual may appear slightly different
depending upon which version of Microsoft® Windows™ you are using. For
example:

1) Titles, and names in title bars, may appear centered,
instead of left justified.

2) Certain Windows dialog boxes for opening files, etc. may
have slightly different names, and may have different
labels on push buttons, for example [OK] instead of
[Open].

There may be other minor variations; in general, the differences should be
self-explanatory.

iii

BLANK PAGE

Table of Contents

Chapter 1 - Introduction - W ha t is ACCOL Wor k b enc h?........................................................1-1

What is a n ACCO L Sour c e F il e?..................................................................................1-1

Summary of F i l es G ener a ted By ACCOL Wor kbench......................................1-2

Chapter 2 - Ins talling ACCOL Workb enc h on the PC.............................................................2-1

Chapter 3 - Starting ACCO L W or k b enc h................................................................................3-1

Methods For Cr ea ting An ACCOL Sourc e F i le............................................................3-2

Chapter 4 - Quickstart For Experienced Users.......................................................................4-1

Chapter 5 - Cr ea ting, Editing, and Sa vi ng A N ew ACCO L Sour c e F il e..................................5-1

ACCOL Source Fil e Sec t i ons........................................................................................5-2

Editing the Source Code Directly.....................................................................5-3

Typing In New Text .........................................................................................5-4

Cutting, Copying, and Pasting Text.................................................................5-4

Finding and/or Replacing Text.........................................................................5-5

Editing the Properties of the Section...............................................................5-6

Saving the N ew ACCO L Sour c e Fi l e ...........................................................................5-7

Saving Subsequent Changes........................................................................................5-8

Deleting A Sec tion of the ACCOL Sour c e F il e .............................................................5-8

Opening An Exis ting ACCOL Sourc e F il e ...................................................................5-8

Closing An ACCOL Sour c e F i le a nd Ex i ting ACCOL Workbench ...............................5-9

Chapter 6 - Specifying the Target Node Type (*TARGET section).........................................6-1

Editing the *TARGET section properties (Edit Properties Mode) ...............................6-1

Editing the Source Code Directly (Edit Code Mode)....................................................6-1

Chapter 7 - Defining Passwords (*SECURITY-CODES section) ............................................7-1

Password Encryption...................................................................................................7-2

Changing Passwords in Edit Properties Mode ............................................................7-3

Chapter 8 - Defining Communication Ports (*COMMUNICATIONS Section) .......................8-1

General Instruc tions for Editing the Properties of the *COMMUN ICATIONS Sect ion

(Edit Properties Mode).....................................................................................8-1

Editing the Source Code Directly (Edit Code Mode)....................................................8-2

Defining A Master Port In Edit Properties Mode........................................................8-3

Defining A Master Port in Edit Code Mode.................................................................8-4

Defining An Expanded Addressing Master Port in Edit Properties Mode ..................8-5

Defining An Expanded Addressing Master Port in Edit Code Mode...........................8-6

Defining A Serial CFE Port in Edit Properties Mode .................................................8-8

Defining A Serial CFE Port in Edit Code Mode...........................................................8-8

Defining A Slave, Pseudo-Slav e, or Pseudo- Slave with Al arms Port in Edit P roperties

Mode.................................................................................................................8-9

Defining A Slave, Pseudo-Slave, or Pseudo-Slave with Alarms Port in Edit

Code Mode........................................................................................................8-9

Defining A VSAT Slave Port...................................................................................... 8-11

Defining A VSAT Slave Port in Edit Code Mode.......................................................8-11

Defining An RIOR Port in Edit Properties Mode.......................................................8-12

Defining An RIOR Port in Edit Code Mode ...............................................................8-13

v

Defining A Logger Port in Edit Properties Mode.......................................................8-14

Defining A Logger Port in Edit Code Mode ...............................................................8-14

Defining A Custom Port in Edit Properties Mode.....................................................8-16

Defining A Custom Port in Edit Code Mode..............................................................8-16

Defining An Optional Comm (TANO) Port in Edit Properties Mode......................... 8-18

Defining An Optional Comm (TANO) Port in Edit Code Mode.................................8-18

Defining A Columbia Natural Gas Port in Edit Properties Mode.............................8-19

Defining A Columbia Natural Gas Port in Edit Code Mode......................................8-19

Defining An Internet Protocol (IP) Port in Edit Properties Mode.............................8-21

Defining An Internet Protocol (IP) Port in Edit Code Mode......................................8-21

Defining Additional Buffers in Edit Properties Mode................................................8-22

Defining Additional Buffers in Edit Code Mode ........................................................8-22

Defining Parameters For An IP Custom Protocol in Edit Properties Mode .............. 8-23

Defining Parameters For An IP Custom Protocol in Edit Code Mode.......................8-25

Chapter 9 - Specifying Memory Requirements (*MEMORY section)......................................9-1

Specifying Mem or y i n Ed i t Properties Mode
Specifying Mem or y i n Ed i t Properties Mode

(386EX Protected Mode Units ONLY).............9-1

(186 & 386EX Real Mode U nits ONLY)...........9-3

Specifying Memory in Edit Code Mode ( 386EX Protected Mod e Units ONLY) .....................9-5

Specifying Memory in Edit Code Mode ( 186 & 386EX Real Mode Units ONLY )...................9-8

Chapter 10 - Declaring Process I/O Boards (*PROCESS-I/O Section).................................. 10-1

Declaring Process-I/O Boards in Edit Properties Mode.............................................10-1

Declaring Process I/O Boards in Edit Code Mode......................................................10-2

Chapter 1 1 - D ef ini ng Low - L ev el Boa r d Inputs ( *LO W - L EVEL Sec tion).............................11-1

Creating the *Low-Level Section...............................................................................11-1

Chapter 12 - Creating ACCOL Signals (*SIGNALS section) ...............................................12-1

Signal Names.............................................................................................................12-1

Signal Characteristics...............................................................................................12-2

Defining New ACCO L Sig na ls...................................................................................12-2

Settings for Logical Signals ...........................................................................12-3

Settings for Logical Alarm Signals................................................................12-6

Settings for Analog Signals ...........................................................................12-8

Settings for Analog Alarm Signals .............................................................. 12-10

Settings for String Signals ..........................................................................12-13

Editing Signal Characteristics.................................................................................12-15

Creating New Signals From Existing Signals.........................................................12-16

Deleting An ACCOL Si gna l .....................................................................................12-16

Defining Base Name Text For Signals.....................................................................12-18

Chapter 13 - Defining Signal Lists........................................................................................13-1

Chapter 1 4 - Cr ea ting An ACCOL Tas k (*TASK Sect i on) ....................................................14-1

Editing the Task Characteristics Line (Edit Properties Mode).................................14-1

Editing the Task Characteristics Line (Edit Code Mode)..........................................14-1

Inserting Modules In The Task .................................................................................14-3

Entering Signal Names..............................................................................................14-4

Getting Help on Configuring A Particular Module....................................................14-5

Customizing the Module Menu to Include Frequently Used Modules.......................14-6

Re-sequencing the Line Numbers For Modules in the Task...................................... 14-7

vi

Going to a Particular Line of the File........................................................................14-8

Searching for Items Throughout the Entire Source File............................................14-8

Undoing the Last Keystroke(s)..................................................................................14-9

Deleting Text From the Current Cursor Position to the End of the Line................14-10

Removing Unused Module Terminals...................................................................... 14-10

Defining A Signal’s Type From Within A Module or Task (Check-in Feature) .......14-11

Chapter 1 5 - D ef i ning D a ta Arrays ( *A- ARRAY and *L-ARRAY sections)...........................15-1

Read Write Arrays..................................................................................................... 15-2

Read-Only Arrays......................................................................................................15-2

Example 1 - Initializing An Entire Read-Only Array...............................................15-3

Example 2 - Initializing Individual Cells In A Read-Only Array.............................15-4

Modifying Arrays In Edit Code Mode........................................................................15-4

Chapter 16 - Defining Communication FORMATS (*FORMAT Section)..............................16-1

Chapter 1 7 - D ef ini ng Ar c hiv e F il es ( *ARCHIVE Sec tion).................................................... 17-1

Archive Definition in 3305 and 386EX PM Units......................................................17-1

Archive Definition in 3530-series Units.....................................................................17-4

Archive Calculation Formulas...................................................................................17-7

Chapter 18 - Using the BUILD Command to Generate ACO and ACL Files ....................... 18-1

Using the Batch Build Feature..................................................................................18-3

Chapter 19 - Using the DOCUMENT Command to Generate an LST File .......................... 19-1

Signal Cross-Reference..............................................................................................19-1

Load Statistics...........................................................................................................19-1

Memory Usage and Memory Map..............................................................................19-2

Chapter 20 - Rever s e Com p iling a n ACO F ile to Get an ACC File .......................................20-1

Performing A Batch Reverse.....................................................................................20-1

Chapter 2 1 - O perating ACCO L W or kbench in On-L i ne Mod e............................................21-1

Activating the Downloader........................................................................................21-2

Starting Debug Mode.................................................................................................21-2

Exiting Debug Mode..................................................................................................21-2

Determining the Ed iting Capabilities F or the Current ACCOL Loa d.......................21-3

Summary of Debugging Techniques..........................................................................21-3

Using Deb ug gi ng F la g s i n a n ACCO L T a s k ..............................................................21-6

Accessing the ACCOL Tas k ............................................................................21-7

Setting a Breakpoint......................................................................................21-8

Setting an Abort.............................................................................................21-9

Setting a Skip...............................................................................................21-10

Using Step Mode..........................................................................................21-11

Clearing All Debug Flags in a Task.............................................................21-12

Viewing, Setting, and Clearing Debug Flags...............................................21-12

Viewing the Error Array Window............................................................................21-14

Viewing and Changing Data On-Line.....................................................................21-16

Methods for Changing Data.........................................................................21-16

Using the Watch Window.............................................................................21-17

Using the Change Signal Value Dialog Box.................................................21-20

Toggling Signal Inhibit/Enable Bits............................................................. 21-20

Conducting A Signal Search.........................................................................21-21

vii

Using the Signal Detail Window..................................................................21-21

Changing Values in a Read/Write Data Array .............................................21-22

Changing the Floating Point Format of Data ..............................................21-23

Toggling t he F i r s t Column of an Arr a y Between Analog and

Timestamp Data ...............................................................................21-23

Keeping Column 1 Visible While Scrolling Through an Array.....................21-23

Editing ACCO L Loa d Struct ur es O n- L ine..............................................................21-24

Changing Values in a Read-Only Data Array.............................................21-25

Editing Titles and Signals in an Archive Definition....................................21-26

Editing A Format......................................................................................... 21-27

Editing A Signal List....................................................................................21-28

Editing Module Terminals and Calculator Equations in a Task ................. 21-29

Updating Initia l Val ues i n Your ACCOL Source F il e ..................................21-30

Saving Changes to the Source File on the Hard Disk..................................21-30

Appendix A - Upgrad ing ACCO L Sour c e F il es f r om P r ev i ous Ver s i ons

or Using Files in different CPU Platforms......................................................A-1

Appendix B - L i s ting of ACCOL Mod ules & Control Statements ..........................................B-1

Appendix C - Keyboard Shortcuts ..........................................................................................C-1

Appendix D - Customizing the User Environment.................................................................D-1

Viewing Open BSI Setup Parameters.........................................................................D-1

Turning On/Off the Tool Bar ......................................................................................D-1

Turning On/Off the Status Bar................................................................................... D-1

Opening/Closing the Output Window.........................................................................D-1

Opening/Closing the Watch Window..........................................................................D-2

Re-Arranging the Windows on the Desktop................................................................D-2

Using the Workspace Settings Dialog Box.................................................................D-2

Setting File and Backup Parameters..............................................................D-2

Setting the Line Numb er s i n ACCO L Ta sks...................................................D-4

Specifying Parameters For On-Line Operation..............................................D-5

Specifying Refresh Rates For On-Line Windows............................................D-6

Changing the F onts Used i n ACCO L Wor kbench Code Windows...................D-7

Choosing Which Warning Messages Should Be Displayed .............................D-8

Using Filters To Limit Which Signals Are Displayed in Signals Window................D-10

Sorting Signals Alphabetically in the Signals Window............................................D-12

Turning ON/OFF Signal Filtering............................................................................D-12

Restoring A Backup File...........................................................................................D-12

Appendix E - Using Initial Value Scan - Valscan...................................................................E-1

Appendix F - *DEFINE and *INCLUDE Statements............................................................F-1

Text Substitution Using *DEFINE.............................................................................F-3

Text Insertion Using *INCLUDE............................................................................... F-4

Glossary.................................................................................................................................. G-1

viii

Notational Conventions In Syntax Boxes

This manual includes numerous syntax boxes which define the syntax rules for
editing particular sections of the ACCOL source file. The notational conventions
within syntax boxes are different from those in the rest of the text.

Syntax Rules - *PROCESS-I/O Section

Within the syntax box, the following notational conventions apply:

bold text should be entered exactly as shown
italic text indicates a place where the ACCOL programmer must

substitute a particular value, or entry. Possible entries for
this value are then listed.

[text in brackets] indicates optional fields, which need not be entered,

unless that particular option is required. DO NOT type
the brackets.

ix

Chapter 1 - Introduction: What is ACCOL Workbench?

ACCOL Workbench is a Windows™-based software tool that allows you to create,
modify, and document an ACCOL source file, and to build an ACCOL lo ad file . If
your Network 3000-series controller model supports it, you can also perform on-line
operations through ACCOL Workbench includin g downloading, deb ugging, and on­line changes to d ata and ACCOL structures.

What is an ACCOL Source File?

The ACCOL source file defines the programming instructions which will be used by
a Bristol Babcock Network 3000-series remote process controller.

The ACCOL programmer chooses whichever specific programming instructions
(ACCOL modules, signals, control statements, etc.) are necessary for the intended
user application, and enters them in the ACCOL source file, using ACCOL
Workbench, or any ASCII text editor.

The source file, when completed, is
compiled and linked using the ACCOL
Workbench "Build" command.

The build process translates the
programmer's instructions into an
intermediate ACCOL Object File and a
final ACCOL Load File. The ACCOL
Load File contains the original
programming instructions in a machine­readable format which can be executed by
the Network 3000-series controller. In
order for the controller to execute the
instructions, however, the ACCOL Load
File must be downloaded into the
controller's memory using the Open BSI
Downloader.

Any errors detected during the build process are reported, within ACCOL
Workbench, and in a listing fi le. ACCOL Workbench allows the programmer to go
directly to the line which caused the error. Once the p rogrammer has corrected the
errors, the "Build" command can be initiated again.

ACCOL Workbench User Manual Introduction1-1

A summary of the diff erent types of f iles used by ACCOL Workbench is presen ted
in the table below. The f iles created by ACCOL Workbench use the file extensions
listed in the table.

Summary of Files Gene rated By ACCOL Workbench

File

Description
Extension
.ACC

This extension indicates an ACCOL s ource file. An ACCOL source

file is in ASCII format, and may be edited, according to pre-defined

syntax rules, by any ASCII text editor, or by ACCOL Workbench.

The ACCOL programmer defines, within the ACC file, the ACCOL

modules, signals, statements, and structures which will be used to

program the Network 3000-series controller for its intended

application. The ACC file cannot be used directly by the Network

3000 controller, therefore, it must be compiled and linked to

generate an ACCOL Object file, and an ACCOL Load fi le.

Backups of ACCOL source f iles, when the Backup feature has been

activated through the Workspace Settings dialog box, are named

using the file base name, with the add ition of an underscore ’ _’ a nd

a 3 digit version number. The same file extension (.ACC) is used . For

example, if there is an ACC file named MYFILE.ACC, its first

backup file would be named MYFILE_001.ACC.

NOTE: These backup files are for previous versions of the source fi le.

Users should always save a cop y of thei r curren t ACCOL source fi les

on a separate diskette to guard against a hard disk failure.
.ACO

This extension indicates an ACCOL object file. An ACO file is

created when a "Build" command is issued from within ACCOL

Workbench, and is an intermediate step in the creation of an

ACCOL load file. The ACO file is used by the Open BSI Utilities for

various purposes, and shares the same file base name as the ACC

file it was created from.
.ACL

This extension indicates an ACCOL load file. It contains, in a

machine-readable format, the ACCOL modules, statements, and

structures defined in the ACC file. The ACL fil e is the final output of

the "Build" command. It is downloaded into the memory of the

Network 3000-series controller using the Open BSI Downloader.

Once in memory, the modules and statements in the ACL file are

executed by the Network 3000-series controller.
.LIS This extension indicates a listing file. The listing file contains any

error or status messages which occur as a result of executing the

"Build" command. If the listing option is active, this file may also

include a tabulated listing of the ACCOL source file (.ACC). If the

cross-reference option is active, this file may also include a simple

cross-reference of the signals used in the file.

Introduction ACCOL Workbench User Manual1-2

File

Description
Extension
.LST This extension indicates a documentation file, which contains a

complete listing of the ACCOL source, as well as a signal cross

reference, and various load statistics. It is crea ted by executing the

"Document" command.

ACCOL Workbench User Manual Introduction1-3

BLANK PAGE

Chapter 2 - Installing ACCOL Workbench on the PC

ACCOL Workbench software is installed as part of the standard Open BSI Utilities
installation. Select the "ACCOL Workbench" option when running the installer
from the Open BSI CD ROM. See Chapter 2 of the Open BSI Utilities Manual
(document# D5081) for details.

NOTE: ACCOL Workbench is generally NOT backward-compatible, i.e. once you

edit an .ACC file in a given version of ACCOL Workbench, structures may
change such that it CANNOT be readily edited within an earlier version of
ACCOL Workbench.

ACCOL Workbench User Manual Installation

2-1

BLANK PAGE

Chapter 3 - Starting ACCOL Workbench

L



1

To start ACCOL Workbench, click as follows:

StartÅ ProgramsÅ OpenBSI T oolsÅ Workbench.

Once started, a window, with the words ’Accol Workbench’ in the title bar, will
appear on the screen.

7

WOHEDU

0HQXEDU

7RROEDU

6WDWXV

EDU

IMPORTANT: If this is the very first time ACCOL Workbench has been
started on this particular computer, you will be prompted to register the
software. Otherwise, the software can only be used for a maximum of 30
days. For m ore information on t he registration process, see Chapter 2 of
the Open BSI Utilities Manual (document# D5081).

ACCOL Workbench fu nctions can be activated by clickin g on the menu bar items,
and selecting choices from pull-down menus. Some items are also accessible by
clicking the right mouse button, and choosing from p op-up menus.

In addi tion to access f rom the me nus, certain opti ons may also be selected from the

1

If you are using Open BSI 3.0 (or newer), you can also start ACCOL workbench by clicking on the icon
for a particular RTU in NetView, pressing the right mouse button, and choosing “RTU” and then
“Workbench” from the pop-up menus.

ACCOL Workbench User Manual Starting ACCOL Workbench3-1

tool bar. Positioning the mouse over a particular tool bar icon will cause a label to
be displayed, indicating the function of that tool bar icon. Click on the icon to
activa te the function.

Finally, keyboard shortcuts are available for th e most common fu nction s. Th ese are
discussed in Appendix C.

ACCOL Workbench status messages appear, pe riodically, in the Status Ba r.

2

ACCOL Workbench allows you to have mul tip le windows open, allowing you to view
different sections of the same ACCOL source file, or more than one ACCOL source
file, simultaneously, and to switch between them quickly.

Methods For Creating An ACCOL Source File

There are two basic methods availab le to create an ACCOL source file.
Method 1: Open an existing ACCOL source (ACC) file, and save it under a

different na me. Then edit the ACCOL source fil e to fit your particular
application, either with ACCOL Workbench, or with any ASCII text
editor.

NOTE: If you intend to modify an ACC file from an earlier version of ACCOL Tools
(Version 5.13 or earlier), this may generate syntax or parsi ng errors when brough t
into ACCOL Workbench. Please review the instructions in ’Appendix A - Upgrading
Old ACCOL Source Files’ for details.

Method 2: Create an all n ew ACCOL source file using ACCOL Workbench . This

process is discussed in detail in the sections that follow. Experienced
ACCOL programmers may wish to read the ’Quickstart For
Experienced Users’ (Chapter 4) which provides a quick overview of
using ACCOL Workbench. Other users who are unfamiliar with the
syntax rules for ACCOL source files should start with ’Creating,
Editing, and Saving A New ACCOL Source File’ (Chapter 5). That
chapter, and the chap ters that follow i t, describe in detail the synta x
rules for each p art of the ACCOL Source File.

IMPORTANT NOTE FOR EITHER METHOD

The output files (.ACO, .ACC) created by ACCOL Workbench ARE
INCOMPATIBLE with DOS-based version s of the ACCOL Tools (AIC5, ABC5,
REV5, etc.)

2

If desired, either the Tool Bar, Status Bar, or both, may be removed from the screen by de-selecting
them on the View pull down menu.

Starting ACCOL Workbench ACCOL Workbench User Manual3-2

Chapter 4 - Quickstart For Experienced Users

This section assumes that ACCOL Workbench software, and Open BSI standard
utilities software, have already been installed on the PC Workstation.

The next few pages a re in tend ed to g et you started ; if you run i nto p robl ems wi th a
particular step, refer to other sections of the manual for more detailed explanations.

As you navigate through the ACCOL Workbench software, you can
access on-line help via the "Help" menu bar item. There is also
context-sensitive help, in which you point at the item for which you
need help. Context-sensitive help is accessible through the icon shown
at left. You can also obtain context-sensitive help, for the currently
selected item or dialog box, by pressing the [F1] key.

Step 1 - Start ACCOL Workbench

Click on StartÅProgramsÅOpenBSI T oolsÅWorkbench

1

Step 2 - Open A New ACCOL Source File

Click on FileÅNew, -OR- click on the new file icon, shown at left.

A dialog box will appear which
requires you to choose whether your
Network 3000-series controller is a
Real Mode unit, or a Protected Mode
unit. (This depends upon the type of
CPU board installed in the controller.)
Choose the appropriate controller
type, and click on [OK], and a new
ACCOL source file will be opened.

1

For information on installation of ACCOL Workbench, see Chapter 2. For information about Open BSI
Utilitie s software, see the Open BSI Utilities Manual (docu m ent# D5081).

ACCOL Workbench User Manual Quickstart for Experienced Users4-1

The new file will be called ACCOL.ACC and will include either a ’PM’ for Protected
Mode, or an ’RM’ for Rea l Mode in the ti tle bar. (You sh ould rename it later, wh en
you save the file.)

You’ll noti ce that the file comes with certain sections pre- defined, each of whi ch is
represented by an icon. There are icons for the target node type, memory,
communication ports, security codes, process I/O, signals, base names, and Task 0.
Additional sections for tasks, low-level I/O, formats, archive files, data arrays, and
signal lists can be added as necessary. (We will discuss this in step 5).

In general, a section can be edited in one of two ways:
a) double-click on the icon for the section; this will call up a dialog box, or a

window, in which you can make selections or enter data for the section. This
is called ’editing the properties’ of the section.

b) click on the icon for the section; then click on EditÅCode. This calls up a

window with the actual ACCOL source code for th e section. This source code
follows a strict set of syntax rules which are discussed later in this manual.
This method of editing is called ’editing the code’ of the section.

NOTE: You also have the option of clicking on ce on the icon for a section, and then
pressing the right mouse key. A pop-up menu will allow you to choose whether you
want to edit the code, or the properties, of the selected section.

IMPORTANT

Whichever of these editing methods you use, it is important to remember that ACCOL

Workbench DOES N OT VALIDATE the source cod e you create; it on ly checks f or basic

syntactic errors. Other errors may only be detected during a "Build" operation.

Quickstart for Experienced Users ACCOL Workbench User Manual4-2

Step 3 - Define Communication Ports, Memory, and Process-I/O Boards

Each of these sections are accessed
by double-clicking on the
appropriate icon, and entering
values in dialog boxes or windows.
For purposes of this explanation we
will show how to define process I/O
boards; the basic methods for
defining communication ports and
memory are similar.

Double-click on the Process I/O icon, shown at left. The dialog box
shown above will appear.

Next, select the kind of board which resides in the f irst slot from the " Boa rd Type "
list box.

Click on the [Insert] push button, and the board will be added to the list of boards.
Repeat this process for each and every board. Boards should be defined in

ascending order based on their slot number in the Network 3000 controller.
To change the definition of a board in the list, click on the board en try in the list,

make any n ecessa ry cha ng es to th e "Board ID" and "Board Ty pe" fields, and click
on the [Modify] pu sh button.

To delete a board def inition, cl ick on the bo ard entry in the list, th en click on the
[Remove] push button. You will be prompted to confirm deletion of the board
definition. Click on [Yes] to proceed, or [No] to cancel the deletion request.

When you are finished editing, click on [OK] to exit the dialog box.
If desired, the resulting source code may be viewed and edited by clicking on the

’Process-I/O’ icon, then clicking on Edit Å Code, -OR- by clicking on the ’Edit Code’
icon (the pencil).

ACCOL Workbench User Manual Quickstart for Experienced Users4-3

The actual source code for the *PROCESS-I/O section, as currently defined, will
appear on the screen, and may be directly edited accord ing to ACCOL syntax rules,
defined elsewhere in this manual.

*PROCESS-I/O

1 8DI
24AI
32AO
48DO

Close the window, when finished editing.

Step 4 - Create ACCOL Signals

It is recommended that signals either be explicitly defined first in the *SIGNALS
section, before they are used in signal lists or module templates, or that they be
‘checked in’ when entered in a module or task through the Check-in feature (see
Chapter 1 4.) This i s becau se si gnal s ente red in modu le templa tes ( see Step 5) or in
signal lists, are assigned their signal type (logical, logical alarm, analog, analog
alarm, or string) during the "Build" process based on the context in which the
signal is used. If the type of signal required cannot be determined by its usage, it
will be defined as a logical signal, which may not be the desired signal type for your
particular application. An advantage of defining signals first in the *SIGNALS
section is that they may be dragged from the *SIGNALS window, directly to a
module terminal, or signal list, thereby reducing the need to re-type signal names.

To create a new ACCOL signal,
double-click on the signals icon.
The Specify Signal Filter window
will appear.

Click on [OK], an empty signal
window will appear.

Quickstart for Experienced Users ACCOL Workbench User Manual4-4

Next, click on Edit Å Insert (Or press the right mouse bu tton, and select "Add
Signal" from the pop-up menu.) In either case, the Signal Properties dialog box

will appear.
Type the signal base name in

the "Base Name" field, the
signal extension (if used) in
the "Extension" field, and the
signal attribute (if used) in
the "Attribute" field.

The type of signal (analog,
analog alarm, logical, logical
alarm, or string) is selected
from the "Type" list box.

To specify a different security
level for operator read access
to this si gnal, en ter a number
(from 1 to 4) in the "Read
Security" field.

To specify a di fferent security leve l for operator access to cha nge (i.e write to) thi s
signal, enter a number (from 1 to 4) in the "Write Security" field.

To manually enable the signal, the "Manual Enable" check box must be selected
(which is the d ef au lt ch oi ce) . To man u al ly in h ib it th e sig na l , th is ch e ck b ox mus t be
de-selected.

To control enable the signal, the "Control Enable" check box must be selected
(which i s the default choi ce). To control inhibi t the signal, this ch eck box must be
de-selected.

Click on the "Settings" tab to specify other characteristics of the signal, such as its
initial value, units or ON/OFF text, etc. The settings required vary somewhat
depending upon the type of signal being defined.

When finished defining the signal, click on [OK] to exit the Signal Properties di alog
box.

If multipl e sig na ls are to b e d ef in ed wh i ch sh are the sa me ch ara cteri sti cs, the y ma y
be created using the Duplicate feature, which is available via the Edit pull down
menu.

ACCOL Workbench User Manual Quickstart for Experienced Users4-5

Step 5 - Insert New Sections For Tasks, Lists, Arrays, etc.

To insert a new section, close the section
you are currently editing first. New
sections must be explicitly created for each
data array, archive file, signal list, task,
format, or low-level board. For purposes of
illustration, we will show how to add a new
ACCOL task to the source file. New
sections are added by clicking on Edit

Å

Insert. In the list box, select ’Task’ as the
type of section to be added, and click on
[OK].

A Configure Task dialog box will be
displayed which allows you to
configure the first line of the task.
Specify a task rate, priority, and, if
applicable, a redundancy frequency.
Click on [OK].

The Task Window will now be opened,
showing the first line, as you just
configured it.

To insert ACCOL modules into the task, p osition the cursor on the lin e where you
would like to add the module.

Click on ModulesÅInsert. The Select Module dialog box will appear.
Use the scroll bar to view the different

module names. Click on the name of the
module you would like to insert. If you are
choosing an I/O module with interleaved
terminals such as INPUT 1, INPUT 2
INPUT 3, etc. enter the number of sets of
interleaved terminals in the “N umber of
Terminals” field.

Quickstart for Experienced Users ACCOL Workbench User Manual4-6

(For detailed information on individual modules, consult the ACCOL II Reference
Manual (document# D4044).)

Click on [OK]. A template for the module will be inserted at the current line of the
source file.

The module name will be preceded by the next sequential line number for this task.
(Task line numbers must be in ascending order).

The modu le temp late i nclu des th e mod ule te rmina ls, wi th de scripti ons o f th e l ike ly
signal type required for each terminal. If the module includes interleaved
terminals, the number of terminal sets you specified in the Select Module dialog box
will be created. The descriptions must be replaced with the actual signal names or
constants which will be used by the module.

There are two ways to enter the signal names, you can either:

1) Manually type the signal names in place of the existing descriptions.

-OR-

2) Drag the signal name from the *SIGNALS section to the desired module

terminal. To do this, open a Signal window, as described in Step 4. With the
window for the Task also in view, position the cursor on the desired signal.
Depress and HOLD the left mouse key. While continuing to hold the left
mouse key, move the cursor to the desired module terminal in the other
window; an outline box of the signal being copied will appear to help you
position it correctly. When you are on the proper terminal, release the mouse
key. The signal name will now appear on the terminal in the module
template. This method is called drag and drop, and greatly reduces the

2

amount of typing required.

This method only works, of course, if you had

previously defined the desired signals, as recommended in Step 4.

2

This same ’drag and drop’ method may be used in the creation of signal lists.

ACCOL Workbench User Manual Quickstart for Experienced Users4-7

In the figure, below, a copy of the signal name STATION1.HUMID.PCNT is
dragged from the *SIGNALS se ction to the INPUT terminal of an ANIN module.

Use either of these methods to define signals, as required, for each module
terminal.

Call up the Select Module dialog box, as previously described, and repeat the entire
process for each module to be added to the task. If you copy and paste modules in
different locations, make sure task lines are in ascending order. When finished,
close the window. A new icon will appear for this task.

Step 6 - Save the ACCOL Source File

When you have fin ished making ed its, click on the Save icon, -OR- click
on FileÅSave or FileÅSave As from the menu bar. The File Save As
dialog box will appear. Select a drive, directory and file name (other
than ACCOLn) and use the extension of (.ACC). Click on [OK].

Quickstart for Experienced Users ACCOL Workbench User Manual4-8

Step 7 - Issue a "Build" Command

To initiate a "Build" command on the curren tly open ACCOL source file,
click on the "Build" icon (the hammer, shown at left), - OR - click on
ActionsÅBuild. ACCOL Workbench will commence building an
ACCOL Object (.ACO) file, and an ACCOL Load (.ACL) file. As the
building operation proceeds, various messages will appear on the status
line, indicating the progress of the build.

If the operation is successful, a message similar to the one below will be displayed.
Skip to Step 9.

If errors are detected du ring the build p rocess, they must be corrected. Correcting
errors is discussed in Step 8.

Step 8 - Correct Any Errors and Re-Build

Unless the ACCOL source file is syntactically perfect, some errors will be detected.
In the figure, below, there are two errors which need to be corrected.

ACCOL Workbench User Manual Quickstart for Experienced Users4-9

In some cases, if the location of the error is identifiable, you can double-click on the
error line, and go d irectly to the sou rce of th e error. Dou ble -cli ckin g on Error 61, for
example, calls up a source code window for the task showing the location where
ACCOL Workbench first id entified there was an error.

In this case, both errors were caused by an improper line number in a Calculator
Module; the line "135 :ENDIF" should have a line number greater than 140 and
less than 160, instead of 135.

You can make corrections right in th e source code window, then save the changes,
and issue a "Build" command again (see Step 7). If there are numerous errors in
the file, you can jump from error to error by clicking from the menu bar on
ViewÅNext Error or ViewÅPrevious Error. Repeat the building and error
correcting process un til no errors occur, an d the ’Compil ation S uccessfu l’ and ’Link
Successful’ messages are generated. These messages mean that .ACO and .ACL
files have been successfully created.

Step 9 - Download the Completed File Using the Downloader

Once an ACCOL load file has been successfully created, it can be
downloaded into the Network 3000-series controller. There, the ACCOL
programming instructions in the load file are executed, in order to
measure and/or control the particular user process.

For users with firmware and ACCOL Workbench versions which support on-line
Workbench operation, the Open BSI Downloader can be activated from within
Workbench by clicking on the icon (shown above) or by clicking on
ActionsÅDownload. For users with older Workbench versions which do NOT
support on-line operation, the Downloader must be started from within Open BSI
Utilities. For instructions on starting Open BSI communications, and downloading,
see the Open BSI Utilities Manual (document# D5081).

Step 10 - Perform Debugging, Make On-Line Edits
(ONLY FOR Versions of ACCOL Workbench which support On-line operation)

If errors exist, debugging, and on-line editing may be performed by
activating Debug Mode. This is done by clicking on the Debug icon.

ACCOL Tasks may be viewed, along with the signal values associated with each
module in the task. Signals may also be edited via the Change Signal Value dialog
box.

Quickstart for Experienced Users ACCOL Workbench User Manual4-10

There are three types of debugging flags which can be set to help isolate problem
areas in an ACCOL task. They may on ly be placed on numbered task lines.

Breakpoint flags stop task execution at a certain point, and allow it to
continue, one task line at a time, by clicking on the single step icon.

Task lines containing skip flags are ’skipped over’ and so do NOT execute.

Task lines containing abort flags, and all task lines following them are
ignored. Task execution resumes from the beginning of the task.

These flags may be set by clicking on the numbered task line where the flag should
be placed, and then clicking on the icon associated with the flag (shown above).

Debug flags may also be set and
cleared using the Debug Flags for
Load dialog box, which is accessible by
clicking as follows: View Å Node

Information Å Debug Flags.

ACCOL Workbench User Manual Quickstart for Experienced Users4-11

For more information on debugging, see ’Using Debugging Flags in an ACCOL
Task’ in Chapter 21.

Performing On-Line Edits to Data ONLY

Edits to signal values, read/write data array entries and signal inhibit/enable bits
may be made simply by clicking on the appropriate field (signal value, array value,
or inhibit flag) in any on-line window, and using the resulting dialog box to change
the data. Each of these types of changes aff ect data only; they do NOT change the
structure of the ACCOL load.

Performing On-Line Edits Which Affect the Structure of the Load File

Read-Only data arrays, formats, arch ive entries, module termin als, and calculator
equations may also be edited on-line. Each of these types of changes, however,
change the structure of the ACCOL load, and so must be explicitly sent to the
controller, and saved in the ACC file on disk at the conclusion of the debugging
session.

The basic procedure for performing on-line edits to these structures is to click on
the section to be edited, then click on EditÅChange On-Line.

An Edit Code window (or dialog box in the case of arch ives or read only arrays) will
appear in which changes may be made. Once changes are complete, they must be
explicitly sent to the controller either by clicking on the [Commit Changes] button
(if one is provided) or by clickin g on EditÅCommit Changes.

To exit debugging mode, click on the icon (shown at left) or click on
ActionsÅStop Debugging. You will be prompted to save changes to the
ACC file on the hard di sk, if you have not already done so.

Quickstart for Experienced Users ACCOL Workbench User Manual4-12

Chapter 5 - Creating, Editing, and Saving A New

ACCOL Source File

Start ACCOL Workbench, as described in Chapter 3.

Next, click on the ’New’ icon, shown at left, -OR- click on FileÅNew.

A dialog box will appear which
requires you to choose whether your
Network 3000-series controller is a
Real Mode unit, or a Protected Mode
unit. (This depends upon the type of
CPU board installed in the controller.)
Choose the appropriate controller
type, and click on [OK], and a new
ACCOL source file will be opened.

The new file will be called ACCOL.ACC and will include either a ’PM’ for Protected
Mode, or an ’RM’ for Rea l Mode in the ti tle bar. (You sh ould rename it later, wh en
you save the file.) A window containing several icons, with the label ’Accoln’ in the
title bar, will appear on the screen.

1

Each of the icons ( Tar get, Se curi ty, Memory , Co mmun i cati on s, B ase n a mes, Pro cess
I/O, Task 0, and Signals) corresponds to one of the sections of the ACCOL source
file. Some other sections, besides those shown, will need to be added later. A
complete list of ACCOL source file sections is sh own in the following tab le.

1

Each time a new ACCOL source file is opened in ACCOL W or kbe n ch, the file is assigned a ’PM n’ or
’RM n’ number to differentiate it from other open files. ’n’ is a number which starts at 1 and is
incremented based on the number of source files open. For example, the first real mod e file opened has
an RM1 in its title bar, second real mode file opened has an R M2 in its title bar, etc.

ACCOL Workbench User Manual Creating/Editing/Saving the File5-1

ACCOL Source File Sec tions

Section Name Purpose of Section

*TARGET Defines the type of Network 3000 controller which

will receive the downloaded file. This section also
includes a user-defined version number for the ACO
file. Only one *TARGET section is allowed.

*SECURITY-CODES Specifies the security codes for security levels 1

through 6. The encryption feature may also be
activated in this section. Only one *SECURITY­CODES section is allowed.

*COMMUNICATIONS Defines the usage of communication ports (e.g.

Master Port, Slave Port, Logger Port, etc.) in the
Network 3000 unit. Also included here are the
number of additional communication buffers, and
the number of Alarm Timestamp buffers. Only one
*COMMUNICATIONS section is allowed.

*MEMORY Defines the amount of memory installed in the

controller. The size of the ACCOL load cannot
exceed this amount. This section also defines the
amount of memory required for certain ACCOL
structures. Only one *MEMORY section is allowed.

*PROCESS-I/O Defines the process I/O boards installed in your

controller, or in a ttached remote I/O racks. Only one
*PROCESS-I/O section is allowed.

*LOW-LEVEL Defines the input types for the Low-Level Analog

Input Board, if it is included in this unit, or in a
Remote I/O Rack attached to this unit. Multiple
*LOW-LEVEL sections are allowed.

*TASK Defines overall task cha racteristics (e.g. Task Rate,

Task Priority, Redundancy Frequency) and includes
all ACCOL modules and control statements for this
task. Multiple *TASK sections are allowed. Note:
ACCOL Workbench automatically creates a special
non-executing task called Task 0. This task is
generally reserved for special non-executing
modules.

*BASENAMES Defi nes the base n ame text for ACCOL sign al base

names. Only one *BASENAMES section is allowed.

*SIGNALS Defines and initializes user-created signals. Only

one *SIGNALS section is allowed. Also defines
system signals based on entries in other sections.
Note: System signals are automatically defined by
ACCOL Workbench; the user does NOT create
them.

*LIST Defines signal lists. Multiple *LIST sections are

allowed.

Creating/Editing/Saving the File ACCOL Workbench User Manual5-2

Section Name Purpose of Section

*A-ARRAY Defines analog data arrays. Multiple *A-ARRAY

sections are allowed

*L-ARRAY Defines logical data arrays. Multiple *L-ARRAY

sections are allowed.

*FORMAT Defines ASCII communication Formats. Multiple

*FORMAT sections are allowed.

*ARCHIVE Defines the archive files. Multiple *ARCHIVE

sections are allowed.

Editing the Source Code Directly

There are basically two ways to edit most sections of the ACCOL source file. One
way to edit the ACCOL source file is to edit the actual text (also called the source
code) in the file. (The other way to edit the file will be discussed, later.)

To edit the source code, click on the icon
corresponding to the section you would like to
edit, so it is highlighted (as the Memory icon is
highlighted, in the picture, at right.) Next, click
on the ’Edit code’ icon (the pencil icon, shown
above) - OR - click on EditÅCode -OR- p ress
the right mouse button and choose " Edit Code"
from the pop-up menu.

A new window will appear, showing the exact text of this section of the ACCOL
source file. For example, if you click on the Memory icon, and then click on the ’Edit
Code’ pencil icon, you will see a window similar to the one shown below:

You may e dit the text in the window, as described, below:

ACCOL Workbench User Manual Creating/Editing/Saving the File5-3

Typing In New Text

Once you are in Edit Code mode, you can enter n ew text. To do this, position the
cursor at the location in the window where you would like to enter new text, and
click the left mouse button, then type the new text. (Note: Information on the
syntax rules for each particular section of the source file is included later in this
manual.)

In addition to simply typing in new text, you can cut, copy, and paste text as
described below. (Note: You must be in Edit Code mode to use any of the functions
below.)

Cutting, Copying, and Pasting Text
Cut

Copy

To cut text, position the cursor immediately before the text you would
like to cut. Click and hold the left mouse button down while dragging
the cursor in order to highlight the desired text. Release the mouse
button, then click on the scissors (the ’Cut’) icon ( - OR - click on Edit

Å

Cut ), (- OR - d epres s the ri ght mou se bu tton, and select "Cut" from the
pop-up menu). The selected text will disappear from the window and
will be temporarily copied to the Windows™ Clipboard. If you would like
to move the text to another lo cation, wheth er in this fi le, or in ano ther
ACCOL source file, use the paste function immediately, otherwise, the
text in the Clipboard will be over-written by the next copy/cut operation.

To copy text, posi tion the curso r immediatel y before the te xt you woul d
like to copy. Click and hold the left mouse button down, while dragging
the cursor in order to highlight the desired text. Release the mouse
button, then click on the 'Copy' icon ( - OR - click on Edit ÅCopy ), ­OR - dep res s th e ri gh t mou se bu tton , a n d s el ect "Copy" from the pop-up
menu. The selected text will remain on the screen, and will be
temporarily copied to the Windows™ Clipboard. If you would like to
copy the text to another location, whether in this file, or in another
ACCOL source file, use the paste function immediately, otherwise, the
text in the Clipboard will be over-written by the next copy/cut operation.

Paste

To paste text, which has been stored in the Clipboard via a previous
Cut/Copy command, position the cursor at the location where you would
like to paste the text, and click. Then click on the 'Paste' icon ( - OR ­click on EditÅPaste), - OR - d ep res s th e ri gh t mou se b u tton , a nd se le ct
"Paste" from the pop-up menu. The selected text will be copied from the
Windows™ Clipboard to the new location.

Creating/Editing/Saving the File ACCOL Workbench User Manual5-4

Finding and/or Replacing Text

You can also search in the Edit Code mode for particular text strings, and/or replace
them with new text.

Find To find a particular string of characters, click on EditÅFind, (-OR

depress the right mouse button, and click on "Find" in the pop-up
menu.)

The Find dialog box will appear, as shown above. Enter the text string
you would like to locate in the "Find What" field. If you want the text
to match exactly with regard to upper and lower case letters, make
sure the "Match Case" box is checked. Click on [Find Next] to
initiate the search. The first occurrence of the string, in the specified
Direction, from the current location in the file, will be highlighted. If
desired, click on [Find Next] again, to continue the search, and locate
the next occurrence. If you would like to change the direction of the
search, you can do th is by clickin g on the opp osite "Direction" button
from what is currently selected. The "Down" direction button causes
the search to start from the current position, and end when it reaches
the end of the file. The "Up" direction bu tton ca uses th e search to start
from the current position, and end when it reaches the beginning of
the file. When you are finished with the Find dialog box, click on
[Cancel] to exit.

Replace To find a particular string of characters, and replace it with a different

string of characters, click on EditÅReplace (-OR- depress the right
mouse button and click on "Replace" in the pop-up menu.)

ACCOL Workbench User Manual Creating/Editing/Saving the File5-5

The Replace dialog box will appear, as shown above. Enter the text you
would like to locate in the "Find What" field. This is called the search
string. Enter the new text (which will replace the text you are
searching for) in the "Replace With" field. This is called the
replaceme nt string. If you want the search string to match exactly with
regard to upper and lower case letters, make sure the "Match Case"
box is checked. Click on [Find Next] to initiate the search. The first
occurrence of the search string, past the current location in the file,
will be highlighted. Click on [Replace] to replace the highlighted text
in the fil e with the text in the "Replace With" field, or click on [Find
Next] again, to continue the search and locate th e next occurrence of
the search string. Continue this process until you have made all
desired chan ges. If you wan t to change every occu rrence of the search
string, rather than ch an gin g each in di vi du al occu rrence, one a t a time,
you can click on [Replace All]. The [Replace All] push button causes
all occurrences of the search string to be replaced with the replacement
string. When you are finished with the Replace dialog box, click on
[Cancel] to exit.

Editing the Properties of the Section

Although most sections of the ACCOL source file may be edited directly in Edit
Code mode, in some cases, it may be easier, in terms of the number of keystrokes, to
edit a section in Edit Properties mode. Edit Properties Mode activates a window or
dialog box for editing, in which the user makes selections, or types entries.

To enter Edit Properties mode, double-click on
the icon corresponding to the section you would
like to edit, - OR - click on the icon so it is
highlighted (as the Memory icon is highlighted,
in the picture, at right), and then either click
on the Edit Properties icon (shown above) or
press the right mouse button and choose
"Properties" from the pop-up menu.

Another way to enter Edit Properties mode is
to click on the icon, then click on Edit
Properties.

Å

The picture at right shows the window which
appears in Edit Properties mode for Memory.
The appearance of the window, of course, will
vary depending upon which section is being
edited.

Creating/Editing/Saving the File ACCOL Workbench User Manual5-6

When editing in the window is completed, close it, in order to exit Edit Properties
mode.

NOTE:

The *BASENAMES, *FORMAT, *LOW-LEVEL, *LIST, and *TASK sections do
not have selectable entries in Edit Properties mode, therefore, a window for
editing the source code (similar to Edit Code mode) will appear, instead.

IMPORTANT

Whether you use Edit Code mode, Edit Properties mode, or a mixture of the two,
you must make sure that the entries you make follow the syntax ru les of ACCOL.
The sections which follow discuss these rules.

Saving the New ACCOL Source File

If you are saving an ACCOL source file which is new (i.e. it has never been
previously saved under its current name,) or if you want to re-name an existing
ACCOL source file, click on FileÅSave As. The Windows™ File Save As dialog box
will appear.

Specify the path for you r ACCOL source fi les (w hich must not in clud e spaces) ; then
type a f ile n ame in th e "File Name" field . Names mu st start with a lette r, an d be
followed by alp hanumeric cha racters, with no spaces. A fil e extension of '.ACC' will
be appended. Click on [Save] to save the ACCOL source file. The file will be saved,
and the ACCOL source file name will appear in the title bar of windows in ACCOL
Workbench.

ACCOL Workbench User Manual Creating/Editing/Saving the File5-7

Saving Subsequent Changes

Once the ACCOL source file has been named, any subsequent changes to it are
saved by clicking on the Save icon, shown above, - OR - by clicking on FileÅSave.

Deleting A Section of the ACCOL Source File

To delete a section of the ACCOL source file, click on ce on the icon for the section
you would like to delete, so it is highlighted. Click on EditÅDelete. You will be
prompted to confirm th at you wan t to delete the section. If y ou clic k on the [Yes]
push button, the section will be deleted. NOTE: Only those sections which the user
specifically adds to the file (Tasks, Arrays, Formats, Archive, Low-Level, and Lists)
can be deleted.

Opening An Ex isting ACCOL Source File

If you want to open an existing ACCOL source file for modification, click on

2

FileÅOpen from the menu bar

- OR - click on the ’Open’ icon, shown above.

2

If the particular ACCOL source file is one of th e last four you edit e d , its name will appe ar in the File
pull down menu, and you can click on it directly to open it; otherwise you must use the Open File dialog
box.

Creating/Editing/Saving the File ACCOL Workbench User Manual5-8

In the Windows™ Open File dialog box, select the drive and directory in which the
ACCOL source file resides, then double-click on the ACCOL source file name. The
file will then be opened for modifications.

Closing An ACCOL Source File and Exiting ACCOL Workbench

To close an ACCOL source file, click on FileÅClose. You will be prompted whether
or not you wish to save changes.

Click on [Yes] to save changes, - OR - click on [No ] to abandon any changes made
since the last time the file was saved, - OR - click on [Cancel] to abandon the close
operation, and return to editing the source file.

Once the file is closed, you may exit ACCOL Workb e nch by clicking on FileÅExit.
The same prompt for save, shown above, will appear if you click on FileÅExit,

without having previously saved the source file.

ACCOL Workbench User Manual Creating/Editing/Saving the File5-9

BLANK PAGE

Chapter 6 -Specifying the Target Node Type (*TARGET section)

The *TARGET section specifies the type of Network 3000-series controller which
this ACCOL load file will be downloaded into.

NOTE

If you need to convert a Real Mod e ACCOL load to a
Protected Mode load, or vice-versa, you MUST edit the
target section manually in an ASCII text editor, PRIOR
to opening it in ACCOL Workbench.

Editing the *TARGET section properties (Edit Properties Mode)

Access the *TARGET section by double-clicking on the ’Target’ icon, or by one of the
other methods discussed in Chapter 5 under ’Editing the Properties of the Sectio n’.

Choose the type of Network 3000-series controller this ACCOL load will reside in,
from the "Target" list box. If you select ‘3530’ you will be prompted whether or not
to include the SYS_3530 Module in Task 0.

The ACC file version number starts at 1, and stays at that value until explicitly
changed by the user. If desired, the versio n nu mber of the ACC f ile may be ch an ged
by manually entering a new number in the "Version" field. Click on [OK] to exit
the Target dialog box.

Editing the Source Code Directly (Edit Code Mode)

Click on the '*TARGET' icon, then click on the 'Edit Code' icon (the pencil). The
actual source code for the *TARGET section, as currently defined, will appear on
the screen. A typical *TARGET section definition appears below.

*TARGET 33XX-386EXPM VERS: 1

ACCOL Workbench User Manual Specifying the Target Node Type6-1

Syntax Rules - *TARGET Section:

*TARGET target_name [VERS:nnnn]

where target_name is one of the following:

386EXPM for 386EX Protected Mode units
33XX-386EX for 386EX Real Mode units
3330 for 186-based DPC 3330, DPC 3335

3308 for GFC 3308-x units
3305 for RTU 3305 units
3530 for EGM 3530/RTU 3530 units

nnnn is the version number of this

or RTU 3310

ACCOL source f i le.

Specifying the Target Node Type ACCOL Workbench User Manual6-2

Chapter 7 - Defining Passwords (*SECURITY-CODES section)

ACCOL supports 6 possible security levels (1 to 6), with 6 being the high est level.
Each level has, associated with it, a password. Any operator using ACCOL
Workbench, Open BSI Utilities, or certain other programs, to communicate on-line
with a particular Network 3000-series controller, must sign-on with one of the
controller’s passwords. Once signed-on, the Operator is then allowed access to any
signal or system function which accepts a security level less than or equal to the
security level of the password entered. For example, an operator signing on with the
security level 4 password has access to all functions requiring level 1 to 4, but is
prohibited from accessing functions requiring security level 5 or 6.

Passwords are defined in the *SECURITY-CODES section of the ACCOL source
file. There is one password for each of the 6 possible security levels.

Passwords consist of any combination of 1 to 6 u ppe rcase letters or n u mbers (a lp ha ­numeric characters) excluding spaces and any punctuation marks. Lowercase
letters entered are automatically converte d to uppercase.

When creating a new ACCOL sou rce fi le, ACCOL Workb ench a utomaticall y assign s
a default initial password for each security level, as shown in the table, below. It is
recommended that users ch ange the password for each l evel to some thing d ifferen t
from the default, or else anyone reading this manual will know the passwords for
your system.

Security Level:

1 111111
2 222222
3 333333
4 444444
5 555555
6 666666

IMPORTANT

Bristol Babcock CANNOT assist you in accessing a file or
function if you forget your password.

Default Initial Password:

ACCOL Workbench User Manual Defining Passwords7-1

Password Encryption

1

Passwords in the ACCOL source file are stored in an encrypted fo rmat. They appear
as 12 strings of 6 scrambled alpha-numeric characters (even though the actual
password entered is 6 characters or less). Casual users viewing the scrambled
characters would be unable to easily determine the actual password.

Although you may view the scrambled characters in Edit-Code mode, do not
attempt to edit the codes.

IMPORTANT

DO NOT ATTEMPT TO EDIT PASSWORDS IN EDIT
CODE MODE. Doing so will further scramble the saved
password, and will result in your passwords becoming
unusable.

In addition to being encrypted
within the ACCOL source file
(ACC), passwords can also be
encrypted in the ACCOL Object file
(ACO) and ACCOL Load file (ACL)
by selecting the "Encrypt
Passwords" option in Edit
Properties Mode.

To turn OFF encryption for
ACO/ACL files, de-select the
"Encrypt Passwords" option. You
will be forced to provide the Level 6
password in order to do this.

ACCOL Workbench (PM) 6.2 (or newer PM version), or ACCOL Workbench 7.0 (or newer). In addition,
the following minim u m firmware revisions ar e r equired: RMS04, AM, LS501, TFA01/TRA01,
PLS02/PLX02 (or newer).

Defining Passwords ACCOL Workbench User Manual7-2

1

Password encryption requires ACCOL Workbench (RM) 1.0 (or newer RM version) -OR-

Changing Passwords in Edit Properties Mode:

Access the *SECURITY-CODES section by
double-clicking on the ’Security’ icon, or by one of
the other methods discussed in Chapter 5 under
’Editing the Properties of the Section’.

Click on the [Change Level n] push button in
which n corresponds to the security level for
which you would like to change the password.
(For example, to change the password for Security
Level 5, click on the [Change Level 5] push
button.) The password dialog box will appear.

To change the password, first type the current
password in the "Old Pas sword" field. (If this is
an all new ACCOL source file, use the default
initial password, discussed previously in this
chapter.) Next type the new password in the
"New Password" field, and type the same new
password in the "Verify Password" field.

In all cases, asterisks (*) will be shown in the field instead of the actual password.
Click on the [OK] push bu tton to save the revised password, or the [Cancel] push

button to abandon the modification.
Repeat this procedure, for any other security level passwords you want to change,

beginning from the [Change Level n] push button.

ACCOL Workbench User Manual Defining Passwords7-3

BLANK PAGE

Chapter 8 - Defining Communication Ports (*COMMUNICATIONS Section)

A Network 3000-series controller communicates to other Network 3000 controllers,
and to other d evices (th e PC workstati on, printers, etc.) throu gh its commun ication
ports. There are many different conf iguration options for the communication ports,
and these must be specified in the *COMMUNICATIONS section of the ACCOL
source file. The section may be edited either via Edit Properties Mode - OR- via Edit
Code Mode, as described, below:

IMPORTANT: Informa tion on the usage an d restrictions which ap ply to each p ort
type is included in the ’Communication Ports’ section of the ACCOL II Reference
Manual (document# D4044).

General Instructions for Editing the Properties of the *COMMUNICATIONS
Section (Edit Properties Mode)

Access the *COMMUNICATIONS section by double-clicking on the
’Communications’ icon, or by one of the other methods discussed in Chap ter 5 under

’Editing the Properties of the Section’.

When the Communications window first appears, all ports will be shown as unused.
Ports should be defined from top-to-bottom in the list box. Click on the port to be
configured, and then click on the [Change Type] push button.

ACCOL Workbench User Manual Defining Communication Ports8-1

Select the desired port type
from the Change Type dialog
box, and click on [OK].

1

A dialog box will appear for
editing port characteristics,
such as the baud rate. Details
of the dialog box vary,
depending upon the type of port
being defined. See the port­specific sections which follow.

When editing is completed, click on the [OK] pu sh button to exit th e port s ettings
dialog box. If you want to change the settings for a particular port, double-click on
the port -OR- click on the port, then click on the [Edit] push button. The dialog box
for editing the port will appear.

Click on the [OK] p ush button to exit the Communications window.

Editing the Source Code Directly (Edit Code Mode)

Click on the ’Communications’ icon, then click on the ’Edit Code’ icon (the pencil).
The actual source code for the *COMMUNICATION S section, as cu rrently defin ed,
will appear on the screen.

All port definitions appear under a single *COMMUNICATIONS section header. A
typical *COMMUNICATIONS section definition appears below:

*COMMUNICATIONS

BIP_1 PSLAVE_ALM 9600
BIP_2 PSLAVE 9600
PORT_A SLAVE 9600
PORT_B MASTER 9600 20 10
PORT_C MASTER 9600 30 10
PORT_D UNUSED
TSBUFFERS 10
BUFFERS 50

Specific syntax rules for the *COMMUNICATIONS section, and for each type of
port, are on the next several pages. Make any necessary edits followin g those ru les,
and close the window, when finished.

1

This dialog box may also be accessed from "Change Type" push buttons within dialog boxes used to set
port characteristics.

Defining Communication Ports ACCOL Workbench User Manual8-2

Syntax Rules - *COMMUNICATIONS Section

*COMMUNICATIONS

[port definition]
[port definition]
[port definition]
[port definition]
[port definition]

.
.

.
[port definition]
[comm buffers defini tion]
[timestamp buffers definition]

where [port definition] defines the characteristics for

each configured port in the following order, top­to-bottom (BIP_1, BIP_2, ETHRNT, PORT_A,
PORT_B, ..., PORT_J). The rules for a
particular port type are discussed in the section
on each port.

[comm buffers d efinition] defines the number of
additional communication buffers, and is
discussed later.

[timestamp buffers definition] defines the
number of additional alarm timestamp buffers,
and is discussed later.

Note: Unused ports need not be defined.

Defining A Master Port In Edit Properties Mode

In the Communications window, select the port to be configured, and click on the
[Change Type] push button. Click on ’Master’ in the Change Type di alog box, then
click on [OK]. The Master Settings dialog box will appear.

ACCOL Workbench User Manual Defining Communication Ports8-3

Choose the appropriate baud rate
from the "Baud Rate" list box.
Enter the highest local address,
from among the slave nodes on this
master port, in the "High Slave

Addr" field, and enter a
"Timeout" value in tenths of

seconds. Click on [OK] to save th e
changes.

Defining A Master Port in Edit Code Mode

Click on the ’Communications’ icon, then click on the ’Edit Code’ icon (the pencil).
The actual source code for the *COMMUNICATION S section, as cu rrently defin ed,
will appear on the screen. In the example, below, ports BIP_1, C, and D are defined
as Master Ports. Note that, as required, their high slave addresses are defined in
ascending order, from top-to-bottom, i.e. BIP 1’s valid slave address range would be
1 to 20, Port C’s valid slave address range would be 21 to 30, and Port D’s valid
slave address range would be 31 to 40.

*COMMUNICATIONS

BIP_1 MASTER 9600 20 10
PORT_C MASTER 9600 30 10
PORT_D MASTER 9600 40 10

Make any necessary edits following the syntax rules, below, and close the window,
when finished.

Defining Communication Ports ACCOL Workbench User Manual8-4

Syntax Rule s - Master Ports
PORT_x MASTER baud_rate high_slave_addr time_out

- OR -

BIP_y MASTER baud_rate high_slave_addr time_out
where x is one of the following port names:

A, B, C, D, G, H, I, J (Note: K, L, M, N, and O are

reserved for FUTURE USE)

y is one of the following built-in ports:

1, 2

baud_rate is one of the following allowable baud rates:

150, 300, 600, 1200, 2400, 4800, 9600, 19200, 38400. 187500,
1MEG, or RASCL. Note: 187500 and 1MEG are only
supported on Ports A, B, C, D, G or I, and RASCL is only
supported on Ports A, B, C, or D.

high_slave_addr is the highest local address from among all the
slave n odes reporting to this master port. This must be an integer
from 1 to 127. Note: The range of local addresses for slave nodes of
a given Master/Expanded Master Port must be higher than those
on the port preceding it; e.g. if both Port A and C are Master Ports,
and Port A’s slaves ha ve loca l ad dresses from 1 to 25 , resul ting i n a
high slave address of 25, Port C’s lowest slave address cannot be
less than 26.

time_out is the length of time (in tenths of seconds) th at this master
node will wait for the beginning of a response message to be sent.
This value must be an integer from 1 to 250.

Defining An Expanded Addressing Master Port in Edit Properties Mode

In the Communications window, select the port to be configured, and click on the
[Change Type] push button. Click on ’Expanded Master’ in the Change Type
dialog box, then click on [OK]. The Expanded Master Settings dialog box will
appear.

ACCOL Workbench User Manual Defining Communication Ports8-5

Choose the appropriate baud rate from the "Baud Rate" list box . Ente r the h ighe st
local address from among the slave nodes on this master port in the "High Slave
Addr" field. Enter the highest local address from among the nodes on the level
below the virtual nodes on this port2 in the "Exp. High Slave Addr" field. Next,
enter a "Timeout" value in tenths of seconds. Click on [OK] to save the changes.

Defining An Expanded Addressing Master Port in Edit Code Mode

Click on the ’Communications’ icon, then click on the ’Edit Code’ icon (the pencil).
The actual source code for the *COMMUNICATION S section, as cu rrently defin ed,
will appear on the screen.

In the example, below, Built-In Port 1 (BIP 1), and Port B have been configured as
Expanded Addressing Master Ports, and have been defined with baud rates of 9600
and 19200 respectively; the highest slave addresses are 20 and 40, and both have
timeout values of 10 seconds. The hi ghest expanded addressing slave addresses for
the ports are 5 and 15, respectively.

*COMMUNICATIONS

BIP_1 EMASTER 9600 20 5 100

PORT_B EMASTER 19200 40 15 100

2

See the ’Expanded Node Addressing’ section of the ACCOL II Reference Manual ( document#

D4044) for details on th is subject.

Defining Communication Ports ACCOL Workbench User Manual8-6

Make any necessary edits following the syntax rules, below, and close the window,
when finished.

Syntax Rules - Expanded Add ressing Master Ports
PORT_x EMASTER baud_rate high_slave_addr exp_high_slave_addr time_out

- OR -

BIP_y EMASTER baud_rate high_slave_addr exp_high_slave_addr time_out
where x is one of the following port names: A, B, C, D, G, H, I, J

(Note: K, L, M, N, or O are reserved for FUTURE USE)

y is one of the following built-in ports: 1, 2
baud_rate is one of the following allowable baud rates:

150, 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 187500,
1MEG, or RASCL. Note: 187500 and 1MEG are only
supported on Ports A, B, C, D, G or I, and RASCL is only
supported on Ports A, B, C, or D.

high_slave_addr is the highest local address from among all the
slave n odes reporting to this master port. This must be an integer
from 1 to 127. Note: The range of local addresses for slave nodes of
a given Master/Expanded Master Port must be higher than those
on the port preceding it; e.g. if both Port A and B are Master Ports
and Port A’s slaves ha ve loca l ad dresses from 1 to 25 , resul ting i n a
high slave address of 25, Port B’s lowest slave address cannot be
less than 26.

exp_high_slave_addr is the highest local address from among all
the nodes below the virtual nodes on this port. This must be an
integer from 1 to 127. These slaves must follow the same rules as
discussed under high_slave_addr.

time_out is the length of time (in tenths of seconds) th at this master
node will wait for the beginning of a response message to be sent.
This value must be an integer from 1 to 250.

ACCOL Workbench User Manual Defining Communication Ports8-7

Defining A Serial CFE Port in Edit Properties Mode

In the Communications window, select the port to be configured, and click on the
[Change Ty pe] push button. Click on ’Serial CFE’ in the Change Type dialog box,
then click on [OK]. The Serial CFE Settings dialog box will appear.

Choose the appropriate baud rate
from the "Baud Rate" list box.
Click on [OK] to save the changes.

Defining A Serial CFE Port in Edit Code Mode

Click on the ’Communications’ icon, then click on the ’Edit Code’ icon (the pencil).

Syntax Rule s - Serial CFE Ports
PORT_x CFE baud_rate

- OR -

BIP_y CFE baud_rate
where x is one of the following port names:

A, B, C, D, G, H, I, J (Note: K, L, M, N, or O are reserved

for FUTURE US E)

y is one of the following built-in ports:

1, 2

baud_rate is one of the following allowable baud rates:

150, 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 187500,
1MEG, or RASCL. Note: 187500 and 1MEG are only
supported on Ports A, B, C, D, G or I, and RASCL is only
supported on Ports A, B, C, or D.

Note: Only one Serial CFE Port can be defined i n an ACCOL source file, and
there cannot be a Slave Port, or a VSAT Slave Port in the same source file.

Defining Communication Ports ACCOL Workbench User Manual8-8

The actual source code for the *COMMUNICATION S section, as cu rrently defin ed,
will appear on the screen.

In the example, below, Port A has been configured as a Serial CFE port, running at
9600 baud.

*COMMUNICATIONS

PORT_A CFE 9600

Make any necessary edits following the syntax rules, on the previous page, and
close the window, when finished.

Defining A Slave, Pseudo-Slave, or Pseudo-Slave with Alarms Port in
Edit Properties Mode

In the Communications window,
select the port to be configu red, and
click on the [Change Type] push
button. Click on ’Slave’, ’Pseudo
Slave’ or ’Pseudo Slave-Alarms’ in
the Change Type dialog box, then
click on [OK].

The Slave Settings dialog box will appear. Choose the appropriate baud rate from
the "Baud Rate" list box. Click on [OK] to save the changes .

Defining A Slave, Pseudo-Slave, or Pseudo-Slave with Alarms Port in
Edit Code Mode

Click on the ’Communications’ icon, then click on the ’Edit Code’ icon (the pencil).
The actual source code for the *COMMUNICATION S section, as cu rrently defin ed,
will appear on the screen.

In the following example, BIP 1 has been configured as a Pseudo-Slave with Alarms
Port running at 1200 baud; Port A has been configured as a Slave Port, running at
9600 baud, and Port B has been configured as a Pseudo-Slave Port running at 9600
baud.

*COMMUNICATIONS

BIP_1PSLAVE_ALM 1200
PORT_A SLAVE 9600
PORT_B PSLAVE 9600

ACCOL Workbench User Manual Defining Communication Ports8-9

Make any necessary edits following the syntax rules, below, and close the window,
when finished.

Syntax Rules - Slave, Pseudo Slave, or Pseudo Slave with Alarms Ports
PORT_x slave_port_type baud_rate

-OR-

BIP_y slave_port_type baud_rate
where x is one of the following port names: A, B, C, D, G, H, I, J

(Note: K, L, M, N, or O are reserved for FUTURE USE)

y is one of the following built-in ports: 1, 2
slave_port_type is one of the following:

SLAVE to denote a slave port

PSLAVE to denote a pseudo-slave port,

PSLAVE_ALM to denote a pseudo-slave wi th ala rms port

baud_rate is one of the following allowable baud rates:

150, 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 187500,
1MEG, or RASCL. Note: 187500 and 1MEG are only
supported on Ports A, B, C, D, G or I, and RASCL is only
supported on Ports A, B, C, or D.

Note: Only one Slave Port can be defined in an ACCOL source file, and there
cannot be a Serial CFE Port, or a VSAT Slave Port in the same source file.

Note: Up to 8 Pseudo-Sl ave ports may be defined in the same ACCOL source file,
one of which can be a Pseudo-Slave with Alarms Port.

Defining Communication Ports ACCOL Workbench User Manual8-10

Defining A VSAT Slave Port

In the Communications window, select the port to be configured, and click on the
[Change Type] push button. Click on ’VSAT Slave’ in the Change Type dialog box,
then click on [OK]. The VSAT Slave Settings dialog box will appear.

Choose the appropriate baud
rate from the B aud Rate li st box ,
and enter the minimum and
maximum response times in
tenths of seconds. Make sure all
entries follow the syntax rules
defined in the syntax box, below.
Click on [OK] to save the
changes.

Defining A VSAT Slave Port in Edit Code Mode

Click on the ’Communications’ icon, then click on the ’Edit Code’ icon (the pencil).
The actual source code for the *COMMUNICATION S section, as cu rrently defin ed,
will appear on the screen.

In the example, below, BIP 1 has been configured as a VSAT Slave Port running at
9600 baud. Its minimum response time is 5, and its maximum response time is 10.

*COMMUNICATIONS

BIP_1 VSATSLV 9600 5 10

Make any necessary edits following the syntax rules, below, and close the window,
when finished.

ACCOL Workbench User Manual Defining Communication Ports8-11

Syntax Rules - VSAT Slave Ports
PORT_x VSATSLV baud_rate min_resp_time max_resp_time

-OR-

BIP_y VSATSLV baud_rate min_resp_time max_resp_time
where x is one of the following port names: A, B, C, D, G, H, I, J

(Note: K, L, M, N, or O are reserved for FUTURE USE)

y is one of the following built-in ports: 1, 2
baud_rate is one of the following allowable baud rates:

1200, 2400, 4800, 9600, 19200.

min_resp_time is the minimum amount of time, from when a
request for data is received, that the Network 3000 controller will
wait before responding. This value must be an integer from 1 to
255, and is in units of tenths of seconds.

max_resp_time is th e maximum amount of time the control ler can
wait before responding to a request for data. This value must be an
integer from 1 to 255, and is in units of tenths of seconds.

Note: Only one VSAT Slave Port can be defined in a n ACCOL source file, and
there cannot be a Serial CFE Port, or a Slave Port in the same source file .

Defining An RIOR Port in Edit Properties Mode

In the Communications window, select the port to be configured, and click on the
[Change Ty pe] push button. Click on ’Remote I/O’ in the Change Type dialog box,
then click on [OK]. The Remote I/O Rack Settings dialog box will appear.

Choose the appropriate
baud rate f rom the "Baud
Rate" list box, and enter
the maximum address of
the Remote I/O Racks on
this port in the "Max.

Address" field. Click on
[OK] to save the cha nges.

Defining Communication Ports ACCOL Workbench User Manual8-12

Defining An RIOR Port in Edit Code Mode

Click on the ’Communications’ icon, then click on the ’Edit Code’ icon (the pencil).
The actual source code for the *COMMUNICATION S section, as cu rrently defin ed,
will appear on the screen.

In the example, below, Port B has been configured as an RIOR Port running at
187500 baud. The maximum address of Remote I/O racks on this port is 3.

*COMMUNICATIONS

PORT_B RIOR 187500 3

Make any necessary edits following the syntax rules, below, and close the window,
when finished.

Syntax Rules - RIOR Ports
PORT_x RIOR baud_rate max_rio_addr
where x is one of the following port names: A, B, C, D

baud_rate is one of the following allowable baud rates:

187500, 1MEG, or RASCL

max_rio_addr is the maximum remote I/O rack address on this
port, which must be an integer from 1 to 10.

ACCOL Workbench User Manual Defining Communication Ports8-13

Defining A Logger Port in Edit Properties Mode

In the Communications
window, select the port to
be configured, and click on
the [Change Type] push
button. Click on ’Logger’
in the Change Type dialog
box, then click on [OK].
The Logger Settings
dialog box will appear.

Choose the appropriate baud rate from the "Baud Rate" list box. Choose the
number of stop bits from the "Stop Bi ts" list box, and select odd, even , or no parity
from the "Parity" list box. The data width is selected from the "Data Bi ts" list box,
and either half duplex or TTY mode is selected from the "Duplex" list box.
Handshaking option s are selected from the "Handshaking" list box. Click on [OK]
to save th e changes.

Defining A Logger Port in Edit Code Mode

Click on the ’Communications’ icon, then click on the ’Edit Code’ icon (the pencil).
The actual source code for the *COMMUNICATION S section, as cu rrently defin ed,
will appear on the screen.

In the example, below, Port C has been configured as a Logger Port running at 1200
baud, with even parity, 1 stop bit, 7 bit width, CTS, and half duplex.

*COMMUNICATIONS

PORT_C LOGGER 1200 PARITY_E SBIT_1 BIT_7 CTS H_DPLX

Make any necessary edits following the syntax rules, below, and close the window,
when finished.

Defining Communication Ports ACCOL Workbench User Manual8-14

Syntax Rules - Logger Po rts
PORT_x LOGGER baud_rate parity stop_bits width duplex handshake

-OR­BIP_y LOGGER baud_rate parity stop_bits width duplex handshake

where x is one of the following port names: A, B, C, D, G, H, I, J

(Note: K, L, M, N, or O are reserved for FUTURE USE)

y is one of the following built-in-ports: 1, 2
baud_rate is one of the following allowable baud rates:

110, 150, 300, 600, 1200, 2400, 4800, 9600, 19200, and 38400

parity is one of the following:

PARITY_O to indicate odd parity
PARITY_E to indicate even parity
PARITY_N to indicate n o parity

stop_bits is one of the following:

SBIT_1 to indicate 1 stop bit
SBIT_1.5 to indicate 1 1/2 stop bits
SBIT_2 to indicate 2 stop bits

width is one of the following:

BIT_6to indicate 6 bits
BIT_7to indicate 7 bits
BIT_8to indicate 8 bits

duplex is one of the following:

H_DPLX to indicate half duplex
TTY to indicate TTY mode

handshake is one of the following:

NO_CTS to indicate no output control needed
CTS to indicate clear to sen d
XON_XOFF to indicate line turn-on/off with special

characters

ACCOL Workbench User Manual Defining Communication Ports8-15

Defining A Custom Port in Edit Properties Mode

In the Communications window,
select the port to be configured,
and click on the [Change Type]
push button. Click on ’Custom’ in
the Change Type dialog box, then
click on [OK]. The Custom
Settings dialog box will appear.

Choose the appropriate baud rate from the "Baud Rate" list box. Choose the
number of stop bits from the "Stop Bi ts" list box, and select either odd, even or no
parity f rom the "Parity" list box. The data width is selected from the "D ata Bits"
list box. The "Mode", "P1", and "P2" values vary depending on which particular
interface is used (see the ACCOL II Custom Protocols Manual, document# D4066
for information.) Click on [OK] to sa ve the changes.

Defining A Custom Port in Edit Code Mode

Click on the ’Communications’ icon, then click on the ’Edit Code’ icon (the pencil).
The actual source code for the *COMMUNICATION S section, as cu rrently defin ed,
will appear on the screen.

In the example, below, Port D has been configured as a Custom Port running at
1200 baud, with even parity, 1 stop bit, 7 bit width, using mode 17, a P1 value of 1,
and a P2 value of 813.

*COMMUNICATIONS

PORT_D CUSTOM 1200 PARITY_E SBIT_1 BIT_7 PARAM: 17 1 813

Make any necessary edits following the syntax rules, below, and close the window,
when finished.

Defining Communication Ports ACCOL Workbench User Manual8-16

Syntax Rules - Custom Ports
PORT_x CUSTOM baud_rate parity stop_bits width PARAM: mode p1 p2

-OR­BIP_y CUSTOM baud_rate parity stop_bits width PARAM: mode p1 p2

where x is one of the following port names: A, B, C, D, G, H, I, J

(Note: K, L, M, N, or O are reserved for FUTURE USE)

y is one of the following built-in-ports: 1, 2
baud_rate is one of the following allowable baud rates:

110, 150, 300, 600, 1200, 2400, 4800, 9600, 19200, and 38400

parity is one of the following:

PARITY_O to indicate odd parity
PARITY_E to indicate even parity
PARITY_N to indicate n o parity

stop_bits is one of the following:

SBIT_1 to indicate 1 stop bit
SBIT_1.5 to indicate 1 1/2 stop bits
SBIT_2 to indicate 2 stop bits

width is one of the following:

BIT_6to indicate 6 bits
BIT_7to indicate 7 bits
BIT_8to indicate 8 bits

mode is an integer ranging from 0 to 255
p1 is an integer ranging from 0 to 255
p2 is an integer ranging from 0 to 65535

Note: The mode, p1, and p2 values are specified based on the type of interface
you are using; see the ACCOL II Custom Protocols Manual (document# D4066)
for details.

ACCOL Workbench User Manual Defining Communication Ports8-17

Defining An Optional Comm (TANO) Port in Edit Properties Mode

The Optional Comm (TANO) Port is only for use with the TANO proprietary
protocol. Although available for use with 186-based and 386EX Real Mode
firmware, this port type is NOT SUPPORTED BY PROTECTED MODE
FIRMWARE.

In the Communications window, select the port to be configured, and click on the
[Change Ty pe] push button. Click on ’Optional Comm’ in the Change Type dialog
box, then click on [OK]. The port will automatically be configured for 1200 baud,
since this is the only baud rate available for an Optional Communications port.

Defining An Optional Communications (TANO) Port in Edit Code Mode

The Optional Comm (TANO) Port is only for use with the TANO proprietary
protocol. Although available for use with 186-based and 386EX Real Mode
firmware, this port type is NOT SUPPORTED BY PROTECTED MODE
FIRMWARE.

Click on the ’Communications’ icon, then click on the ’Edit Code’ icon (the pencil).
The actual source code for the *COMMUNICATION S section, as cu rrently defin ed,
will appear on the screen.

In the example, below, Port A has been configured as an Op tional Communications
(TANO) Port:

*COMMUNICATIONS

PORT_A OPT_COMM 1200

Make any necessary edits following the syntax rules, below, and close the wind ow.

Syntax Rules - Optional Communication (TANO) Ports
PORT_x OPT_COMM 1200

-OR­BIP_y OPT_COMM 1200

where x is one of the following port names: A, B, C, D, G, H, I, J

(Note: K, L, M, N, or O are reserved for FUTURE USE)
y is one of the following built-in-ports: 1, 2

Note: Only 1 OPT_COMM port may be defined in an ACCOL source file.

Defining Communication Ports ACCOL Workbench User Manual8-18

Defining A Columbia Natural Gas Port in Edit Properties Mode

A Columbia Natural Gas (CNG) Port can be configured either for Master operation
or Slave operation . (This port type is NOT SU PPORTED BY PROTECTED MODE
CUSTOM FIRMWARE PRIOR TO PCP03 .)

In the Communications window,
select the port to be configured,
and click on the [Change Type]
push button. Click on ’Columbia
Natural Gas’ in the Change Type
dialog box, then click on [OK]. The
Columbia Natural Gas Settings
dialog box will appear.

Choose the appropriate baud rate from the "Baud Rate" list box, and choose
whether this will be a Columbia Natural Gas Master Port, or a Columbia Natural
Gas Slave Port in the "Type" list box.

Click on [OK] to save the changes.

Defining a Columbia Natural Gas Port in Edit Code Mode

A Columbia Natural Gas (CNG) Port can be configured either for Master operation
or Slave operation . (This port type is NOT SU PPORTED BY PROTECTED MODE
CUSTOM FIRMWARE PRIOR TO PCP03 .)

Click on the ’Communications’ icon, then click on the ’Edit Code’ icon (the pencil).
The actual source code for the *COMMUNICATION S section, as cu rrently defin ed,
will appear on the screen.

In the example, below, Port G has been configured as a Columbia Natural Gas
Slave Port running at 1200 baud.

*COMMUNICATIONS

PORT_G CNG 1200 SLAVE

Make any necessary edits following the syntax rules, below, and close the wind ow.

ACCOL Workbench User Manual Defining Communication Ports8-19

Syntax Rules - Columbia Natural Gas Ports
PORT_x CUSTOM baud_rate mode

-OR­BIP_y CUSTOM baud_rate mode

where x is one of the following port names: A, B, C, D, G, H, I, J

(Note: K, L, M, N, or O are reserved for FUTURE USE)

y is one of the following built-in-ports: 1, 2
baud_rate is one of the following allowable baud rates:

300, 600, 1200, 2400, 4800 or 9600

mode is one of the f ollowing:

SLAVE to indicate this is a CNG Slave Port
MASTER to indicate thi s is a CNG Master Port

Defining Communication Ports ACCOL Workbench User Manual8-20

Defining An Internet Protocol (IP) Port in Edit Properties Mode

(Open BSI Utilities Version 3.0 and newer only)
In the Communications window, select the ’ETHRNT’ port, and click on the

[Change Type] push button. Click on ’Internet Protocol’ in the Change Type dialog
box, then click on [OK], then click on [OK] again. No additional configuration is
required within ACCOL Workbench for this port.

NOTE: Additional configuration for this port may be required using the LocalView
tool in Open BSI Utilities.

NOTE: The [IP Custom] push button, shown in the Communications window, is
currently non-functional, and is reserved for future use.

IMPORTANT:

Although ACCOL Workbench allows you to speci fy the seri al or bu ilt-i n p orts as
the Internet Protocol (IP) Port, currently, the hardware Ethernet port IS THE
ONLY PORT WHICH MAY BE U SED FOR TH IS PU RPOS E. In fu ture re lea ses
of the product, other ports may be con fig ura ble f or IP usa ge, h owev er, cu rrently ,
only the Ethernet port may be used.

Defining An Internet Protocol (IP) Port in Edit Code Mode

(Open BSI Utilities Version 3.0 and newer only)
Click on the ’Communications’ icon, then click on the ’Edit Code’ icon (the pencil).

The actual source code for the *COMMUNICATION S section, as cu rrently defin ed,
will appear on the screen.

Make any necessary edits following the syntax rules, below, and close the window,
when finished. There is no other confi guration within ACCOL Workbench.

*COMMUNICATIONS

.
.
ETHRNT IP

NOTE: Additional configuration for this port may be required using the LocalView
tool in Open BSI Utilities.

Syntax Rules - Ethernet Port

ETHRNT IP

ACCOL Workbench User Manual Defining Communication Ports8-21

Defining Additional Buffers in Edit Properties Mode

Besides defining ports, the *COMMUNICATIONS section also defines bu ffers.
Although each ACCOL load has a certain default number of buffers, the

Communications window allows you to allocate memory for additional
Communications and/or Alarm Timestamp buffer space.

To specify additional Communications or Alarm Timestamp buffers, enter the
number of additional buffers in the "Communications" or "Timestamp" fields in
the Communications window.

Click on [OK] to save the changes.

Defining Additional Buffers in Edit Code Mode

Click on the ’Communications’ icon, then click on the ’Edit Code’ icon (the pencil).
The actual source code for the *COMMUNICATION S section, as cu rrently defin ed,
will appear on the screen.

In the example, below, 100 additional communication buffers, and 50 additional
alarm timestamp buffers have been defined.

*COMMUNICATIONS

BUFFERS 100
TSBUFFERS 50

Make any necessary edits following the syntax rules, below, and close the window,
when finished.

Defining Communication Ports ACCOL Workbench User Manual8-22

Syntax Rules - Buffers

BUFFERS comm_buffers
TSBUFFERS timestamp_buffers

where comm_buffers is an integer from 0 to 255 indicating the number

of additional communications buffers
timestamp_buffers is an integer from 0 to 255 indicating the

number of additional alarm timestamp buffers.

Defining Parameters For An IP Custom Protocol in Edit Properties
Mode

If you are using a particular custom communication protocol which has been
implemented to communicate using Internet Protocol (IP), you must identify certain
parameters for it in the IP Custom dialog box. This dialog box is accessible f rom the
[IP Custom] push button in the Communications window.

Parameter information should be entered as follows:
Mode indicates a protocol number which is used to select which protocol

should be enabled at the RTU for use with the Custom Module. The
followin g modes are currently su pported:

51 Gould Modbus Slave

ACCOL Workbench User Manual Defining Communication Ports8-23

52 Enron Modbus Slave
53 Modbus Master (Gould or Enron)

Param 1 is a protocol-specific value (P1) which may be utilized at RTU

initialization. Its value defaults to 0 when there is no value for
“Mode”. When a value is included for “Mode”, the “Param 1” value
is defined as follows:

When Mod e is : Param 1 is : With a de fault of:

51 TCP Port Number 502
52 TCP Port Number 502
53 TCP/IP Connection ‘Time to

120
Live’ in seconds. If no activity
within this period, the
connection is shut down.

Param 2 is a second protocol-specific value (P2) which may be utilized at RTU

initialization. Its value defaults to 0.

Enter values in the fields, then click on the [Insert] push button to enter the
parameters. Click on [OK] to save the changes.

Defining Communication Ports ACCOL Workbench User Manual8-24

Defining Parameters For An IP Custom Protocol in Edit Code Mode

Click on the ’Communications’ icon, then click on the ’Edit Code’ icon (the pencil).
The actual source code for the *COMMUNICATION S section, as cu rrently defin ed,
will appear on the screen.

In the example, below, a custom IP application will use mode 78; its P1 parameter
will be 1, and its P2 parameter will be 5.

*COMMUNICATIONS
:
:
IPCUSTOM Param: 78 1 5

Make any necessary edits following the syntax rules, below, and close the window,
when finished.

Syntax Rul e s - IP Custom

IPCUSTOM Param: mode p1 p2

where mode is a protocol number used to identify internal tables at the

RTU. Current modes supported are 51, 52, and 53.

p1 is a protocol-specific value which may be used at RTU

initialization. Depends on choice of mode.

p2 is a protocol-specific value which may be used at RTU

initialization.

ACCOL Workbench User Manual Defining Communication Ports8-25

BLANK PAGE

Chapter 9 - Specifying Memory Requirements (*MEMORY section)

The *MEMORY section specifies the total amount of memory in the Network 3000­series controller, as wel l as how much of th e available memory shou ld be reserved
for certain structures.

The *MEMORY section differs, somewhat, depending u pon which type of controller
you are using. If you are using a 186-based controller, or a 386EX Real Mode
controller, your unit has 64K (65,536 bytes) of base memory. Most units also
include some amount of expanded memory for holding certain special ACCOL
structures. The base/expanded concept does NOT apply, however, if you are u sing a
386EX Protected Mode controller.

Specifying Memory in Edit Properties Mode (386EX Protected Mode Units ONLY)

Access the *MEMORY section either by double-clicking on th e Memory icon, or by
one of the other methods discussed in Chapter 5 un der ’Edit in g th e Propert ies of th e

Section’.

Specify the amount of memory in your controller using the "Total RAM" list box.
NOTE: Entries in the remaining fields only need to be made if the particular

structure involved is used in this ACCOL source file.
If you are using a Custom application (using the Cu stom Port, and/or the Custom

Module) which requires memory to be specifically allocated, enter the number of
bytes required, in the "Custom Size" field. Alternatively, custom applications,
which have been specifically designed to do so, can use the number of K bytes
specified in the "Global St or age" area.

ACCOL Workbench User Manual Specifying Memory Requirements9-1

If you are using the Audit/EAudit Module to hold alarms and events, enter the
number of Alarms and/or Events to be saved in the "Audit Alarms" and "Audit
Events" fields.

If you are using the Storage Module to hold historical data, enter the number of
storage rows required in the "Storage Rows" field.

If this Network 3000 controller has a Serial CFE Port, enter the number of
templates which Enterprise Server will require in the "Templates" field.

An approximation of the number of templates can be calculated by the following
formula; the result should be rounded up to the nearest integer, and it is
recommended that some additional templates be added as spares.

templates = A + L + (5 * R)

38 49
where A = the total number of analog signals in this controller, and

in all nodes below it in the network.

B = the total number of logical signals in this controller, and

in all nodes below it in the network.

R = the total number of Network 3000-series nodes which

send data to Enterprise Server through this node,

including this node itself.
If you will NOT be using IP communication, click on [OK] to save the change s.
If you will be using IP

communica tio n, cli ck o n th e
’IP’ tab, and enter
parameters o n the IP pa ge,
as described, below:

For IP communication "Global Storage" is used for one of two purposes: If you
have created your own custom (non-standard) data link, you can allocate additional
RAM for it here. Alternatively, this area can be used to provide additional RAM for
the IP system. NOTE: If you are experiencing memory allocation failures (as
reported by #IPSTAT..) increasing global storage may solve the problem.

Specifying Memory Requirements ACCOL Workbench User Manual9-2

"Packets" refers to the maximu m n u mber o f IP co mmun i cati on pa cke ts mai n tai ne d
for pending communication work. Each packet uses 1,500 bytes of RAM. A
guideline for setting this value is:

10 + (3 * (maximum number of simultaneous active IP connections))

"Connections" consists of the maximum number of PCs or controllers (RTUs)
which can communicate w ith th is controll er simultaneously. If this value is set too
small, communications will be extremely degraded. Generally, it should be set to
between 20 and 30.

"Pending Requests" consi sts of the maximum n umber of requests to this n ode, or
a node below this node, that will be tracked. If this value is set too small,
communications will be extremely degraded. Generally, it should be set to between
100 and 200. (Pending requests refers to RDB requests which enter this node in IP
format and must be con verted to BSAP message formats i n ord er to be p assed on to
other BSAP nodes.)

"Alarm Report(ARM)" is the max imu m n umb er o f a la rm rep orts to be mai nta i ne d
by the IP system, for transmission to any one destination.

When finished ed iting, click on [OK] to save the changes.

Specifying Memory in Edit Properties Mode (186 & 386EX Real Mode Units ONL Y )

Access the *MEMORY section either by double-clicking on th e Memory icon, or by
one of the other methods discussed in Chapter 5 un der ’Edit in g th e Propert ies of th e

Section’.

ACCOL Workbench User Manual Specifying Memory Requirements9-3

Specify the amount of expanded memory in your controller using the "Expanded
Memory" list box. The structures using expanded memory must also be specified

on the ’Location’ page of the dialog box, discussed later.
NOTE: Entries only need to be made in the remaining fields if the particular

structure involved is used in this ACCOL source file.
If you are using a Custom application (using the Cu stom Port, and/or the Custom

Module) which requires memory to be specifically allocated, enter the number of
bytes required, in the "Cus t om S ize" field.

If you are using the Audit/EAudit Module to hold alarms and events, you must
specify the number of alarms and events to be stored. If your controller firmware
stores events and alarms together, in a combined buffer, sp ecify the total number of
alarms and events in the "Audit Combined" field. If, conversely, the firmware
stores alarms and events in separate buffers, enter the number of alarms to be
saved in the "Audit Alarms" field, and the number of events to be saved in the
"Audit Events" field. To f ind out whi ch versions of con troller firmware use which
buffer storage scheme, see the ’Audit/EAudit’ section of the ACCOL II Reference
Manual (document# D4044).

If you are using the Storage Module to hold historical data, enter the number of
storage rows required in the "Storage Rows" field.

If this Network 3000-series controller has a Serial CFE Port, enter the number of
templates which Enterprise Server will require in the "Templates" field.

An approximation of the number of templates can be calculated by the following
formula; the result should be rounded up to the nearest integer, and it is
recommended that some additional templates be added as spares.

templates = A

+ L + (5 * R)

38 49
where A = the total number of analog signals in this controller, and

in all nodes below it in the network.

B = the total number of logical signals in this controller, and

in all nodes below it in the network.

R = the total number of Network 3000-series nodes which

send data to Enterprise Server through this node,

including this node itself.
Click on the "Locations" file tab to go to the second page of the dialog box. The

’Locations’ page of the dialog box allows you to specify which ACCOL structures
should be stored in base memory, and which should be stored in expanded memory.

Specifying Memory Requirements ACCOL Workbench User Manual9-4

(For certain controller models there are restrictions concerning where structures
may be stored.)

By default, all structures are stored in base memory. To make use of the expanded
memory, and thereby free up space in base memory, you must explicitly choose
which structures should be moved to the expanded memory.

The structures which may be moved from base to expanded memory are: "Read-

Only Arrays", "Read/Write Arrays", "AGA8" calculations, Calculator
"Equations", Signal "Lists", and "Signals". To do this, choose either ’Base’ or

’Expanded’ from the list box next to each type of ACCOL structure.

When finished ed iting, click on [OK] to save the changes, and exit the dialog box.

Specifying Memory Requirements in Edit Code Mode

(386EX Protected M o de Units ONLY)

Click on the ’Memory’ icon, then click on the ’Edit Code’ icon (the pencil). The actual
source code for the *MEMORY section, as currently defined, will appear on the
screen. Here is samp le source code for the *MEMO R Y section.

*MEMORY

TOTAL_RAM 512K
CUSTOM_SIZE 20
STORAGE_ROWS 52
AUDIT_EVENTS 320
AUDIT_ALARMS 320
TEMPLATES 50
GLOBAL_STORE 32
IP_GLOBAL_STORE 0
IP_PACKETS 13
IP_CONNECTIONS 10
IP_PENDREQS 32
IP_ARMS 5

ACCOL Workbench User Manual Specifying Memory Requirements9-5

Make any necessary edits following the syntax rules, below, and close the wind ow,
when finished.

Syntax Rules for the *MEMORY Section (386EX Protected Mode Users ONLY)

*MEMORY

TOTAL_RAM size
CUSTOM_SIZE bytes
STORAGE_ROWS rows
AUDIT_EVENTS events
AUDIT_ALARMS alarms
TEMPLATES templates
GLOBAL_STORE global_bytes
IP_GLOBAL_STORE global_i p
IP_PACKETS packets
IP_CONNECTIONS connections
IP_PENDREQS requests
IP_ARMS max_alarms

where: bytes is the number of bytes of memory to be reserved for use

by certain Custom applications. This value must be an
integer between 0 and 32,000.

size represents the total amount of RAM memory a vailable

rows is the number of Storage rows used by the Storage

events is the number of Audit Trail / EAud it Module events to

alarms is the n umber of Audit Trail / EAudit Module alarms to

(Continued on next page)

in this Network 3000-series controller. Valid entries
are: 512K, 1.5MB, 2.5MB, 3.5MB or 4.5MB.

Module. Each row uses 64 bytes of memory. This
value must be an integer from 0 to 5120.

be stored. If wrap-around mode is used, reserve 1 more
than the number of events. The extra space is used by
the system for buffer management. This value must be
an integer from 0 to 65,535.

be stored. If wrap-around mode is used, reserve 1 more
than the number of events. The extra space is used by
the system for buffer management. This value must be
an integer from 0 to 65,535.

Specifying Memory Requirements ACCOL Workbench User Manual9-6

Section (Syntax Rules for the *MEMORY 386EX Protected Mode Users ONLY)
(Continued)

where: templates if this controller has a Serial CFE Port, this is the

number of templates which will be sent from
Enterprise Server. This value must range from 0 to

2000.

global_bytes is the number of K bytes of global storage RAM to be

used. The global storage area may be used, instead of
the Custom area, by Custom applications, specifically
designed to use it.

global_ip is the number of K bytes of additional RAM to be

available for one of two purposes: If you have created
your own custom (non-standard) data link, you can
allocate additional RAM for it here. Alternatively, this
area can be used to provide additional RAM for the IP
system. NOTE: If you are experiencing memory
allocation failures ( as reported by #IPSTAT..)
increasing the global_ip value may solve the problem.

packets is the maximum number of IP communication packe ts

maintained for pen ding communication work. Each
packet uses 1,500 bytes of RAM. A guideline for setting
this value is:

10 + (3* (max. number of simultaneous active IP connections))

connections is the maximum number of PCs or controllers (RTUs)

which ca n communicate w ith this controller
simultaneously. If this value is set too small,
communications will be extremely degraded.
Generally, it should be set to between 20 and 30.

requests consists of the maximum number of requests to this

node, or a node below this node, that will be tracked. If
this value is set too small, communications will be
extremely degraded. Generally, it should be set to
between 100 and 200.

max_alarms is the maximum number of a larm reports to be

maintained by the IP system, for transmission to a ny
one destination.

ACCOL Workbench User Manual Specifying Memory Requirements9-7

Specifying Memory Requirements in Edit Code Mode

(186 and 386EX Real M od e Un its ONLY)

Click on the ’Memory’ icon, then click on the ’Edit Code’ icon (the pencil). The actual
source code for the *MEMORY section, as currently defined, will appear on the
screen.

Here is sample source code for the *MEMORY secti on.
*MEMORY

EXPANDED_MEM 320K
RO_ARRAY_LOC EXP
EQUATION_LOC BASE
RW_ARRAY_LOC BASE
AGA8_LOC BASE
LIST_LOC EXP
SIGNAL_LOC EXP
CUSTOM_SIZE 40
STORAGE_ROWS 24
TEMPLATES 50
AUDIT_EVENTS 100 OR specify EVENTS 200
AUDIT_ALARMS 100 if the firmware uses a combined

buffer

Make any necessary edits following the syntax rules, on the next page, and close
the window, when finished.

Specifying Memory Requirements ACCOL Workbench User Manual9-8

Syntax Rules for the *MEMORY Section (186 & 386EX Real Mode Users ONLY)

*MEMORY

EXPANDED_MEM size
RO_ARRAY_LOC location
EQUATION_LOC location
RW_ARRAY_LOC location
AGA8_LOC location
LIST_LOC location
SIGNAL_LOC location
CUSTOM_SIZE bytes
STORAGE_ROWS rows
TEMPLATES templates
AUDIT_ALARMS alarms
AUDIT_EVENTS events

-OR­EVENTS combined

where: location is either BASE for base memory or EXP for expanded

memory.

bytes is the number of bytes of memory to be reserved for use

by certain Custom applications. This value must be an
integer between 0 and 32,000.

size represents the total amount of expanded memory

available in this Network 3000-series controller. Valid
entries are: 0K, 64K, 192K, 320K, 440K, 444K, 448K.

rows is the number of Storage rows used by the Storage

Module. Each row uses 64 bytes of memory. This
value must be an integer from 0 to 5120.

alarms is the n umber of Audit Trail / EAudit Module alarms to

be stored. If wrap-around mode is used, reserve 1 more
than the number of alarms. This value must be an
integer from 0 to 4,096.

events is the number of Audit Trail / EAud it Module events to

be stored. If wrap-around mode is used, reserve 1 more
than the number of events. This value must be an
integer from 0 to 4,096.

combined This option is supported for backward compatibility

purposes ONLY. If your controller firmware stores
events and alarms together in a single buffer, specify
the total number of alarms and events, and omit the
AUDIT_EVENTS and AUDIT_ALARMS lines.

ACCOL Workbench User Manual Specifying Memory Requirements9-9

Syntax Rules for the *MEMORY Section (186 & 386EX Real Mode Users ONLY)
(Continued)

where: templates if this controller has a Serial CFE Port, this is the number

of templates which will be sent from Enterprise Server.

This value must range from 0 to 2000.

Specifying Memory Requirements ACCOL Workbench User Manual9-10

Chapter 10 - Declaring Process I/O Boards (*PROCESS-I/O Section)

Process I/O boards allow the Network 3000-series controller to communicate with
external instruments such as flowmeters, pressure transmitters and level
transmitters.

Each installed process I/O board occupies a numbered slot, either in the controller
itself, or in one or more attached RIO 3331 Remote I/O Racks.

Declaring Process-I/O Boards in Edit Properties Mode

Access the *PROCESS-I/O
section either by double­clicking on the Process-I/O
icon, or by one of the other
methods discussed in Chapter
5 under ’ Editin g the Properti es

of the Sectio n’.

Defining A Board

Choose the slot number for the
board to be defined in the
"Board ID" field. Next, select
the kind of board which resides
in the slot from the "Board
Type" list box.

Click on the [Insert] push button, and the board will be added to the list of boards.
Repeat this process for each and every board. Boards should be defined in

ascending order.
To change the definition of a board in the list, click on the board entry in the list,

make any n ecessary cha ng es to the "Board ID" and "Board Ty pe" fields, and click
on the [Modify] push button.

To delete a board def inition, cl ick on the bo ard entry in th e list, the n click on the
[Remove] push button. You will be prompted to confirm deletion of the board
definition. Click on [Yes] to proceed, or [No] to cancel the deletion request.

ACCOL Workbench User Manual Declaring Process I/O Boards10-1

Declaring Process I/O Boards in Edit Code Mode

Click on the ’Process-I/O’ icon, then click on the ’Edit Code’ icon (the pencil). The
actual source code for the *PROCESS-I/O section, as currently defined, will appear
on the screen.

Here is sample source code for the *PROCESS-I/O section:

*PROCESS-I/O

1 4AI
24DI
34AO
44DO

Make any necessa ry edits following the syntax rules, below, and close the window,
when finished.

Syntax Rules - *PROCESS-I/O Section:

*PROCESS-I/O

board_ID board_type
board_ID board_type

.
.

board_ID board_type

where each board_ID is the number of the slot in the Network 3000-

series device which contains this particular process I/O board.
board_type is a code which identifies the type of process I/O

board. See the tables, on the pages that follow, for valid board
type codes.

Note: The number of board definitions, number of slots, and types of boards

available vary depending on the type of Network 3000-series device. See
the ACCOL II Reference Manual (document# D4044) for details.

NOTES ABOUT MIXING LOW DENSITY BOARD DEFINITIONS WITH
HIGH DENSITY HA RDW A RE A ND VICE VERSA:

Beginning with ACCOL Protected Mode firmware PLS/ PLX/ PES/ PEX 04.30,
boards defined in ACCOL Workbench software as high density (8AI, 4AO, 16DI,
16DO), can reference all I/O points on the physical low-density hardware (4AI, 2AO,
8DI, 8DO, respectively) without generating an error. Similarly, boards defined in
ACCOL Workbench as low density (4AI, 2AO, 8DI, 8DO) can reference their defined
number of physical I/O points on high density I/O hardware (8AI, 4AO, 16DI, 16DO,
respectively.)

Declaring Process I/O Boards ACCOL Workbench User Manual10-2

Board Names used in DPC 3330, DPC
3335, RTU 3310, RIO 3331

Use with
These
Module(s)

Number
of
Signals

Board
Type
Code

Digital Input board: 4 points DIGIN,

RDIGIN,
PDM, RPDM,
LSCOUNT,
RLSCOUNT

Digital Input board: 8 points DIGIN,

RDIGIN,
PDM, RPDM,
LSCOUNT,
RLSCOUNT

Digital Input board: 16 points DIGIN,

RDIGIN,
PDM, RPDM,
LSCOUNT,
RLSCOUNT

Digital Output board: 4 points DIGOUT,

RDIGOUT,
WATCHDOG,
PDO, RDPO

4 signals 4DI

8 signals 8DI

16 signals 16DI

4 signals 4DO

Digital Output board: 8 points DIGOUT,

RDIGOUT,
WATCHDOG,
PDO, RPDO

Digital Output board: 16 points DIGOUT,

RDIGOUT,
WATCHDOG,
PDO, RPDO

Analog Input board: 4 points ANIN, RANIN 4 signals 4AI

Analog Input board: 8 points ANIN, RANIN 8 signals 8AI

Analog Output board: 2 points ANOUT,

RANOUT

Analog Output board: 4 points ANOUT,

RANOUT

High Speed Cnt r board: 4 points (High speed counter )

HSCOUNT,
RHSCOUNT

8 signals 8DO

16 signals 16DO

2 signals 2AO

4 signals 4AO

4 signals HSC

ACCOL Workbench User Manual Declaring Process I/O Boards10-3

Board Names used in DPC 3330, DPC
3335, RTU 3310, RIO 3331

Use with
These
Module(s)

Number
of
Signals

Board
Type
Code

Low Level AI board: 4 points (Low Level Analog
Input)

High Speed Analog board: 4 points (High Speed
Analog Input)

Check Before Oper at e: 8 points HCBO, LCBO 8 signals CBO

Honeywell Transmitter: 8 points (Honeywell
Smartline Transmitter Interface)

GLOBAL BBTI: 8 points (Bristol Babcoc k TeleTrans
Interface)

LOCAL BBTI: 8 poi n t s (Br i s tol Babcock TeleTrans
Interface)

High Density HSC board: 8 points HSCOUNT 8 signals 8HSC

Board Name used in GFC 3308-xx Use with

LLANIN,
RLLANIN

HSANIN 4 signals HSA

HWSTI 8 channels HWT

GBBTI 8 channels 8GT

LBBTI 8 channels 8LT

These
Module(s)

HSCOUNT,
RHSCOUNT

Number
of
Signals

4LL

Board
Type
Code

Analog Input board: 1 point (in Slot 1) ANIN 1 signal 1AI

Analog Input board: 4 points (in Slot 2 - requires slot
4, 5 to be unused)

Analog Output board: 2 points (in Slot 3 - requires slot
4, 5 to be unused)

Digital Input board: 6 points (in Slot 4 - requires slot
2, 3 to be unused; DI/DO points shared with DO board
in Slot 5)

Digital Output board: 6 points (in Slot 5 - requires
slot 2, 3 to be unused; DI/DO points shared with DI
board in Slot 4)

ANIN 4 sig nals 4AI

ANOUT 2 signals 2AO

DIGIN, PDM,
LSCOUNT

DIGOUT,
PDO,
WATCHDOG

6 signals
(total among
slot 4, 5)

6 signals
(total among
slot 4,5)

6DI

6DO

Declaring Process I/O Boards ACCOL Workbench User Manual10-4

Board Name used in RTU 3305 Use with

These
Module(s)

Number
of
Signals

Board
Type
Code

3305 - Digital Input board: 14 points (in Slot 1; all
slots refer to a single Multi-Function I/O Board. 8
DI’s (#7 through #14) are always present, each of the
remaining 6 points (#1 through #6) are hardware­selectabl e a s ei t her DI’s or DO’s.

3305 - Digital Output board: 8 points (in Slot 2; all
slots refer to a single Multi-Function I/O Board. 2
DO’s (#7 and #8) are always present, each of the
remaining 6 points (#1 through #6) are hardware­selectabl e a s ei t her DI’s or DO’s.

3305 - Analog Input board: 4 points (in Slot 3; all slots
refer to a single Multi-Function I/O board.)

3305 - Analog Output board: 2 points (in Slot 4; all
slots refer to a single Multi-Function I/O board.)

DIGIN, PDM,
LSCOUNT

DIGOUT,
PDO,
WATCHDOG

ANIN 4 sig nals 4AI

ANOUT 2 signals 2AO

8 to 14
signals,
depending
upon
number of
DO signals
defined in
slot 2.

2 to 8
signals,
depending
upon
number of
DI signals
defined in
Slot 1.

14DI

8DO

Board Names u sed in EGM 3530 TeleFlow

3530 - Digital Input board: 2 points to 10 points
Only allowed in Slot 1

2 DI’s (#1 and #2) are always present; each of the
remaining 8 points are software selectable (via
ACCOL module u s ag e) as ei t h er DI’s or DO’s. They
are shared with the board in Slot 2. Do NOT specify a
point to be BOTH a DI and a DO because results are
indeterminant.

3530 - Digital Output board: 2 points to 10 points

Only allowed in Slot 2

2 DO’s (#1 and #2) are always present; each of the
remaining 8 points are software selectable (via
ACCOL module u s ag e) as ei t h er DO’s or DI’s. They
are shared with the board in Slot 1. Do NOT specify a
point to be BOTH a DO and a DI because results are
indeterminant.

Use with
These
Module(s)

DIGIN 2 to 10

DIGOUT 2 to 10

Number
of
Signals

signals,
depending
upon the
number of
DO points
referenced
by DIGOUT
modules on
the board in
Slot 2.

signals,
depending
upon the
number of
DI points
referenced
by DIGIN
modules on
the board in
Slot 1.

Board
Type
Code

DI2
or
DI10

DO2

or

DO10

ACCOL Workbench User Manual Declaring Process I/O Boards10-5

Board Names u sed in EGM 3530 TeleFlow

3530 - Analog Input board: 1 point or 5 points
Only allowed in Slot 3

Use with
These
Module(s)

ANIN 1 or 5

Number
of
Signals

signals

Board
Type
Code

AI1
or AI5

3530 - High Speed Counter board: 1 point or 2 points

Only allowed in Slot 4

3530 - Analog Output board: 1 point

Only allowed in Slot 5

Board Na m es u sed i n RTU 3530 - TeleRTU

3530 - Digital Input board: 2 points to 10 points
Only allowed in Slot 1

2 DI’s (#1 and #2) are always present; each of the
remaining 8 points are software selectable (via
ACCOL module u s ag e) as ei t h er DI’s or DO’s. They
are shared with the board in Slot 2. Do NOT specify a
point to be BOTH a DI and a DO because results are
indeterminant.

HSCOUNT 1 or 2

signals

ANOUT 1 signal AO1

Use with
These
Module(s)

DIGIN 2 to 10

Number of
Signals

signals,
depending
upon the
number of
DO points
referenced
by DIGOUT
modules on
the board in
Slot 2.

HSC1 or
HSC2

Board
Type
Code

DI2
or
DI10

3530 - Digital Output board: 2 points to 10 points

Only allowed in Slot 2

2 DO’s (#1 and #2) are always present; each of the
remaining 8 points are software selectable (via
ACCOL module u s ag e) as ei t h er DO’s or DI’s. They
are shared with the board in Slot 1. Do NOT specify a
point to be BOTH a DO and a DI because results are
indeterminant.

3530 - Analog Input board: 4 points or 8 points

Only allowed in Slot 3
3530 - High Speed Counter board: 2 points or 3 points

Only allowed in Slot 4

3530 - Analog Output board: 1 point

Only allowed in Slot 5

DIGOUT 2 to 10

signals,
depending
upon the
number of
DI points
referenced
by DIGIN
modules on
the board in
Slot 1.

ANIN 4 or 8

signals

HSCOUNT 2 or 3

signals

ANOUT 1 signal AO1

DO2

or

DO10

AI4 or
AI8

HSC2 or
HSC3

Declaring Process I/O Boards ACCOL Workbench User Manual10-6

Notes about setting DEVICE and INITIAL terminals on
I/O modules when utilizing fixed I/O boards (3305, 3530
TeleFlow/TeleRTU)

Setting the DEVICE value:
For most Network 3000-series controllers, the choice of slot for an I/O board is

entirely at the discretion of the user; the board could be placed in any open I/O slot.
The DEVICE terminal on the I/O module (ANIN, ANOUT, DIGIN, DIGOUT, etc.)
referencing that board would be set to the number of that slot. The INITIAL
terminal would then typically be set to 1, to reference the first I/O point on the
board.

In the case of con trollers which use f ixed slots however, this is N OT the case. The
RTU 3305, TeleFlow series, and TeleRTU series use boards which reside in fixed
slots. In some cases, a single multi-function I/O board contains ALL the I/O.

While we still refer to the term ’slot’ in these cases, the I/O actually might reside all
on one physical fixed board. To use I/O modules (ANIN, DIGIN, etc.) with these
types of controllers, the just re member that the DEVICE terminal for a given type of
I/O module will always be the same.

RTU 3305
If you want to use this type of I/O
Module…

DIGIN, PDM, LSCOUNT 1

DIGOUT, PDO, WATCHDOG 2

ANIN 3

ANOUT 4

3530 series - TeleFlow / TeleRTU
If you want to use this type of I/O
Module…

DIGIN 1

DIGOUT 2

ANIN 3

HSCOUNT 4

ANOUT 5

Setting the INITIAL value:

Its DEVICE terminal should always be
set to thi s value:

Its DEVICE terminal should always be
set to thi s value:

DIGIN and DIGOUT are the only modules where you are likely to set INITIAL
values other than 1.

ACCOL Workbench User Manual Declaring Process I/O Boards10-7

• For the RTU 3305, 8 digital inputs (DIs 7 through 14) are always present, and 2

digital outputs (DOs 7 and 8) are always present. Another 6 digital I/O points (1
through 6) are each individually selectable as either DI or DO.

• For the 3530 series (TeleFlow / TeleRTU), 2 digital inputs (DIs 1 and 2) are

always present, and 2 digital outputs (DOs 1 and 2) are always present. Another
8 digital I/O p oints (3 through 10) are each individually selectable as either DI or
DO.

Example

:

A user wants to configure a RTU 3305 with 10 digital inputs and 6 digital outputs.
One possible configuration that meets this requirement is shown below:

2DO, 2DI, 2DO, 8DI, 2DO

To configure this in ACCOL Workbench, DIGIN and DIGOUT modules would be
configured as follows:

10 * DIGOUT

20 * DIGIN

30 * DIGOUT

40 * DIGIN

50 * DIGOUT

DEVICE 2 ; in the 3305, DEVICE should always be 2 for a DIGOUT
INITIAL 1 ; the 1st and 2nd DI/DO selectable points are used as DO
OUTPUT 1 DO.1.
TRACK 1 DO.1.TRAK
RESET 1 DO.1.RSET
OUTPUT 2 DO.2.
TRACK 2 DO.2.TRAK
RESET 2 DO.2.RSET

DEVICE 1 ; in the 3305, DEVICE should always be 1 for a DIGIN
INITIAL 3 ; the 3rd and 4th DI/DO selectable points are used as DI
INPUT 1 DI.1.
INPUT 2 DI.2.

DEVICE 2 ; in the 3305, DEVICE should always be 2 for a DIGOUT
INITIAL 5 ; the 5th and 6th DI/DO selectable points are used as DO
OUTPUT 1 DO.3.
TRACK 1 DO.3.TRAK
RESET 1 DO.3.RSET
OUTPUT 2 DO.4.
TRACK 2 DO.4.TRAK
RESET 2 DO.4.RSET

DEVICE 1 ; in the 3305, DEVICE should always be 1 for a DIGIN
INITIAL 7 ; these are the fixed DIs which are always present
INPUT 1 DI.3.
INPUT 2 DI.4.
INPUT 3 DI.5.
INPUT 4 DI.6.
INPUT 5 DI.7.
INPUT 6 DI.8.
INPUT 7 DI.9.
INPUT 8 DI.10.

DEVICE 2 ; in the 3305, DEVICE should always be 2 for a DIGOUT
INITIAL 7 ; these are the fixed DOs which are always present
OUTPUT 1 DO.5.
TRACK 1 DO.5.TRAK
RESET 1 DO.5.RSET
OUTPUT 2 DO.6.
TRACK 2 DO.6.TRAK
RESET 2 DO.6.RSET

Declaring Process I/O Boards ACCOL Workbench User Manual10-8

Chapter 11 - Defining Low-Level Board Inputs (*LOW-LEVEL Section)

For each Low-Level An alog Inpu t board defi ned in the * PROCESS-I/O secti on, the
input types on the low-level board must be defined in a separate *LOW-LEVEL
section.

NOTE:

A complete list of LOW-LEVEL board i np ut types i s i ncl ud ed in the
’LLANIN/RLLANIN’ section of the ACCOL II Reference Manual
(document# D4044).

Creating the *Low-Level Section

By default, the Low-Level icon does n ot appear wh en creatin g a new ACCOL sou rce
file. The *Low-Level section must be explicitly created, according to the following
procedure:

From the ACCOL Workbench main
window, click on EditÅInsert.
(Note: If the Insert option does not
appear in the pull down menu, it
means you are still in Edit Code
Mode or Edit Properties Mode.)

Click on ’Low-Level’ in the New Section dialog box; an Edit Code window will
appear. Make necessary edits following the syntax rules on the next page, and close
the window, when finished.

In the sample source code, shown below, there are two low-level sections, each of
which must be created separately. One was created for a low-level board that
resides in a 3310/3330/3335 (board slot 4) and a second is for a board that resides in
an RIO 3331 remote I/O rack (board 101).

*LOW-LEVEL 4
B B B B
*LOW-LEV EL 101
B J K B

ACCOL Workbench User Manual Defining Low-Level Board Inputs11-1

Syntax Rules - *LOW-LEVEL section:

*LOW-LEVEL board_ID
num1 num2 num3 num4

where board_ID is the slot number in the Network 3000-

series device which contains this Low Level board.
(The Low Level board must have been previously
defined in the *PROCESS- I/O section.)

num1 through num4 are the input typ e codes f or each
of the four inputs on the board residing in a DPC3330,
DPC 3335, RTU 3310, or RIO 3331. Valid input type
codes are: B, E, J, K, R, S, T, RTD, and 10MV.

See the ’LLANIN/RLLANIN’ section of the ACCOL II Reference

Manual (document# D4044) for a description of each input type.

Defining Low-Level Board Inputs ACCOL Workbench User Manual11-2

Chapter 12 - Creating ACCOL Signals (*SIGNALS section)

ACCOL user-created signals are defined in the *SIGNALS section.1 Each ACCOL
signal in the section has associated with it, a signal name, and a set of signal
characteristics. The signal characteristics vary depe nding upon the type of signal.

Signal Names

All ACCOL signal names must conform to the convention, shown in the box, below.

Syntax Rules - ACCOL Signal Names

basename.extension.attribute

where basename is from 1 to 8 characters in length. The first

character must be a letter, and the remaining characters can
be any mix of letters or numbers. As shown, above, the

basename must be immediately followed by a period.
extension is from 0 to 6 characters in length. The extension

can consist of any mix of letters and numbers. As shown,
above, the extension must be immediately followed by a
period, even if the extension is 0 characters in length.

attribute is from 0 to 4 characters in length. The attribute can
consist of any mix of letters and numbers.

Here are some examples of valid signal names:

STATION1.TEMP.HIGH
S3..
PT23.004.2
TANK2.LEVEL.
F127..ON

Note that S3.. has a basename, which is always required, but has no extension or
attribute. TANK2.LEVEL. has no attribute, and F127..ON has no extension.

1

System signals are also defined in the *SIGNALS section, however, ACCOL Workbench generates them
automatically. Some are created when the file is opened; others are created later based on other entries
in the file. Syste m signals are distinguished from other signals by the pound sign ’#’ at the start of the
basename.

ACCOL Workbench User Manual Creating ACCOL Signals12-1

Signal Characteristics

Signal characteristics vary depending upon the type of signal being defined. There
are five types of signals: Logical Signals, Logical Alarm Signals, Analog Signals,
Analog Alarm Signals, and String Signals. The syntax for each of these signal types
will be discussed individually, in the discussion of defining new signals.

Defining New ACCOL Signals

To create a new ACCOL signal, double­click on the signals icon, to open up the
*SIGNALS section for editing. The
Specify Signal Filter dialog box will
appear.

2

Click on the [OK] p ush button.

An empty signal window will appear.
NOTE: This is NOT an Edit Code
Window, signals must be edited via
dialog box.

Next, click on EditÅInsert (OR press
the right mouse b u tton , a nd ch oos e "Add
Signal" from the pop-up menu). The
Signal Properties dialog box will appear.

Type the signal b ase name in the "Base
Name" field, the signal extension (if
used) in the "Extension" field, and the
signal attribute (if used) in the
"Attribute" field.

2

The Specify Signal Filter dialog box is discussed, in greater detail, in Appendix D. Once the Signals
Window is displayed, you can re-call the Signal Filter dialog box by pressing the right mouse button,
and choosing "Set F i lter" from the pop-up menu.

Creating ACCOL Signals ACCOL Workbench User Manual12-2

The type of signal (analog, analog alarm, logical, logical alarm, or string) is selected
from the "Type" list box.

To specify a di fferent security level for op erator read access to this signal, en ter a
number (from 1 to 4) in the "Read Security" field.

To specify a di fferent security level for operator access to chan ge (i.e wri te to) this
signal, enter a number (from 1 to 4) in the "Write Security" field.

To manually enable the signal, the "Manual Enable" check box must be selected
(which is the d ef au lt ch oi ce) . To man u al ly in h ib it th e si gn a l, thi s ch eck bo x mu st be
de-selected.

To control enable the signal, the "Control Enable" check box must be selected
(which is the default ch oice). To control inhib it the signal, thi s check box mu st be
de-selected.

Click on the "Settings" tab to specify other characteristics of the signal, such as its
initial value, units or ON/OFF text, etc. The settings required vary somewhat
depending upon the type of signal being defined.

Settings for Logical Signals

Enter ON/OFF text in the "On Text"
and "Off Te xt" list boxes, -or- choose an
existing ON/OFF text pair from the
"On/Off Pairs " list box.

If this logical signal should be initially
ON when the ACCOL load starts up,
click on the "Initially On" check box. If
this is a global signal, select "Mark as

Global". If this is an RBE signal, select
"Report By Exception".

Click on [OK] to save these settings, or
click on the "General" tab to return to
the first page of the Signal Properties
dialog box.

3

3

See the ’RBE’ section of the ACCOL II Reference Manual ( document# D4044) for information on
Report by Exception.

ACCOL Workbench User Manual Creating ACCOL Signals12-3

Syntax - Logical Signals:
name L [read_security] [write_security][ce][me][rbe][l/gl][initial][text]

where name is the signal name

L indicates this is a logical signal
read_security is the security level an operator needs to

read this signal’s value. This is expressed
as the le tter R immedi ately follo wed b y a
number from 1 to 4. The default is R1.

write_security is the security level an operator needs to

change this signal’s value. This is
expressed as the letter W immediately
followed by a number from 1 to 4. The
default is W3.

ce is the initial state of the control enable /

control inhibit bit for this signal. CE
specifies control enabled; CI specifies
control inhibited; the default is CE.

me is the initial state of the manual enable /

manual inhibit bit for this signal. ME
specifies manual enabled; MI specifies
manual inhibited; the default is ME.

rbe the word RBE designates this to be an

RBE signal; by default, signals are not
RBE signals.

Creating ACCOL Signals ACCOL Workbench User Manual12-4

Syntax - Logical Signals (continued)

l/gl indicates local or global. Enter GLB to

initial is the initial value of this signal. Specify

text is ON/OFF text of the signal. The default

indicate a global signal or LOC to
indicate a local signal. The default is
local.

0 (OFF) or 1 (ON). The default is 0.

is ON and OFF, however both the OFF
text and the ON text may be changed to
other text which is up to 6 characters
long, for example ’OPENED’ and
’CLOSED’. To change the text, use two
six character fields, separated by a blank,
with ON text appearing first, and OFF
text appearing second. If not all six
characters are used, blanks must used to
pad the field. If the text for a particular
state is to be all blanks, enter the word
BLANKS.

Sample Logical Signal Definition

ACCOL Workbench User Manual Creating ACCOL Signals12-5

Settings for Logical Alarm Signals

These settings are identical to
those for logical signals, excep t
for the following differences:

The "Mark As Global" option
does not appear because
alarms are automatically
considered global.

Select the "Alarm Enable"
check box to enable this alarm,
otherwise the signal is alarm
inhibited. The default is alarm
enabled.

In the "Alarm Type" list box
choose either:

’Alarm on True’ if the signal shoul d generate an al arm message when
the signal is ON, or

’Alarm on False’ if the signal should generate an alarm message when
the signal is OFF, or

’Alarm on Change of State’ if the signal should generate an alarm
message an y time the signal transition s from ON to OFF or from O FF
to ON.

In the "Alarm Priority" list box choose either ’Critical’, ’Non-Critical’, ’Operator
Guide’, or ’Event’.

Sampl e Logical Alarm Si gnal Definition

Creating ACCOL Signals ACCOL Workbench User Manual12-6