accol ii reference manual (d4044) · training courses bristol's training department offers a...

www.EmersonProcess.com/Bristol

Reference Manual D4044 May 2006

ACCOL II Software

ACCOL II Reference Manual

For use with DPC 3330, DPC 3335, RTU 3305, RTU 3310, and 3530-xx series units

BLANK PAGE

SECTION 2 – ODD HEADER

5/2006 i

Getting Additional Information In addition to the information contained in this manual, you may receive additional assistance in using this product from the following sources:

Help Files / Release Notes Many Bristol software products incorporate help screens. In addition, the software typically includes a ‘read me’ release notes file detailing new features in the product, as well as other information which was available too late for inclusion in the manual.

Contacting Bristol Directly The address for our world headquarters is:

Bristol, Inc. a division of Emerson Process Management 1100 Buckingham Street Watertown, Connecticut 06795 USA

Our main phone numbers are: (860) 945-2200

(860) 945-2213 (FAX) Regular office hours are Monday through Friday, 8:00AM to 4:30PM Eastern Time, excluding holidays, and scheduled factory shutdowns. During other hours, callers may leave messages using Bristol's voice mail system.

Telephone / E-Mail Support - Technical Questions During regular business hours, Bristol's Application Support Group can provide telephone/e-mail support for your technical questions.

SECTION 2 – EVEN HEADER

5/2006 ii

Please refer to the table, below, for a list of products, and their associated technical support contact information: Product Support Phone

Number(s): E-Mail Address:

ControlWave series (hardware and software)

(860) 945-2394 (860) 945-2286

[email protected]

Network 3000 hardware except for TeleFlow series

(860) 945-2502 [email protected]

TeleFlow series (3530-xx)

(860) 945-8604. [email protected]

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


OpenEnterprise (OE) software


Radio telemetry services (interfacing Bristol hardware to radios)

(407) 629-9463 (407) 629-9464.

[email protected]

Non-Technical Questions, Product Orders, etc. Questions of a non-technical nature (product orders, literature requests, price and delivery information, etc.) should be directed to the nearest Bristol sales office or to your Bristol-authorized sales representative. Please call the main Bristol number (860-945-2200) or visit our web site, listed below, if you are unsure which office covers your particular area.

Visit our Site on the World Wide Web For general information about Bristol, Inc. and its products, please visit our site on the World Wide Web at: www.EmersonProcess.com/Bristol

Training Courses Bristol's Training Department offers a wide variety of courses in Bristol hardware and software at our Watertown, Connecticut headquarters, and at selected Bristol regional offices, throughout the year. Contact our Training Department at (860) 945-2343 for course information, enrollment, pricing, and schedules.

Who Should Read This Manual? This manual is intended to be used by a System Engineer, or other individual, who will be using the ACCOL II language to program a Bristol Network 3000-series controller. It assumes familiarity with the following subjects.

• Use of personal computers.

• Use of ACCOL Workbench software. See the ACCOL Workbench User Manual (document# D4051) for details. Also see An Introduction to ACCOL (document# D4056).

BLANK PAGE

ContentsWhat's New in ACCOL? .............................................................................. ixHardware and Software Requirements .....................................................xvSummary of ACCOL II Structures ..........................................................xxixAAT ....................................................................................................... AAT-1Abort ................................................................................................... Abort-1AGA3 ................................................................................................. AGA3-1AGA3Dens ................................................................................. AGA3Dens-1AGA3Iter ..................................................................................... AGA3Iter-1AGA3TERM ..............................................................................AGA3Term-1AGA5 ................................................................................................. AGA5-1AGA7 ................................................................................................. AGA7-1AGA8 ................................................................................................. AGA8-1AGA8Detail ............................................................................. AGA8Detail-1AGA8Gross ............................................................................... AGA8Gross-1ANIN/RANIN .................................................................................... ANIN-1ANOUT/RANOUT ......................................................................... ANOUT-1ARC_STORE ......................................................................... ARC_STORE-1ATOOLS.INI (for DOS-based ACCOL Tools) .............................. ATOOLS-1AUDIT/EAUDIT ................................................................................ Audit-1Auto-Dial Modem Interface ........................................................ Auto-Dial-1Averager ....................................................................................... Averager-1BBTI Modules (GBBTI, LBBTI) ........................................................ BBTI-1Break ................................................................................................. Break-1Buffers ............................................................................................. Buffers-1Calculator ................................................................................... Calculator-1Characterize ........................................................................... Characterize-1Command ................................................................................... Command-1Comment ..................................................................................... Comment-1Communication Ports ................................................................Commport-1Comparator ............................................................................. Comparator-1Control Statements .............................................................. Control Stmts-1Counter Modules .......................................................................... Counters-1Custom ........................................................................................... Custom-1Daccumulator ....................................................................... Daccumulator-1Data Arrays ............................................................................. Data Arrays-1Demux/EDemux .............................................................................. Demux-1Differentiator ....................................................................... Differentiator-1Digin/RDigin....................................................................................... Digin-1

ACCOL II Reference ManualPage v

Digout/RDigout ................................................................................ Digout-1Downloading ...........................................................................Downloading-1EAStatus ..................................................................................... EAStatus-1EIntegrator ..............................................................................EIntegrator-1Encode ............................................................................................. Encode-1Error Reporting ..................................................................... Error Report-1ETOT/TRND ......................................................................... ETOT/TRND-1EVP.......................................................................................................EVP-1Expanded Node Addressing .............................................. Expanded Node-1FOR/ENDFOR .................................................................................... FOR-1Formats ......................................................................................... Formats-1FPV ....................................................................................................... FPV-1Function ....................................................................................... Function-1GOTO ............................................................................................... GOTO-1GPA8173 ....................................................................................... GPA8173-1GSV....................................................................................................... GSV-1HCBO ............................................................................................... HCBO-1HILOLIMITER ................................................................. HILOLIMITER-1HILOSELECT ..................................................................... HILOSELECT-1HSANIN ....................................................................................... HSANIN-1HWSTI.............................................................................................HWSTI-1IF/ENDIF/ELSE/ELSEIF ....................................................................... IF-1Integrator ................................................................................... Integrator-1Internet_Protocol .......................................................................... Internet-1IP_Client ..................................................................................... IP_Client-1IP Client / Server Communications ................................... IPClient/Servr-1IP Node Addressing ........................................................................ IPAddr-1IP_Server .................................................................................... IP_Server-1ISO5167 ......................................................................................... ISO5167-1Keyboard ..................................................................................... Keyboard-1LCBO ................................................................................................. LCBO-1Lead/Lag .......................................................................................Lead/Lag-1Liquid_Density ................................................................... Liquid_Density-1Liquid Measurement Guidelines ..................................... Liquid_Measure-1LLANIN/RLLANIN ..................................................................... LLANIN-1Logger ............................................................................................... Logger-1Master/EMaster .............................................................................. Master-1Master/Slave Communications............................................. Master/Slave-1Mux/EMux .......................................................................................... MUX-1Node Addressing .............................................................. Node Addressing1Nodestatus ............................................................................... Nodestatus-1PDM/RPDM......................................................................................... PDM-1PDO/RPDO .......................................................................................... PDO-1

ACCOL II Reference ManualPage vi

PID3TERM ............................................................................... PID3TERM-1Portstatus ................................................................................... Portstatus-1Process I/O ............................................................................... Process I/O-1Questionable Data Bit ............................................................... Ques Data-1RBE ..................................................................................................... RBE-1Redundancy ............................................................................. Redundancy-1Redundancy Concepts ............................................................... Redundcon-1Resume ........................................................................................... Resume-1RIOSTATS ................................................................................. RIOSTATS-1Scheduler ..................................................................................... Scheduler-1Sequencer ................................................................................... Sequencer-1Signals ............................................................................................. Signals-1Signal Lists ...............................................................................Signal Lists-1Slave ................................................................................................... Slave-1Smart ................................................................................................. Smart-1Stepper ........................................................................................... Stepper-1Storage ........................................................................................... Storage-1Suspend ......................................................................................... Suspend-1System ............................................................................................. System-1System Signals ................................................................... System Signals-1System0 ......................................................................................... System0-1SYS_3530.....................................................................................SYS_3530-1Task ..................................................................................................... Task-1TCheck ........................................................................................... TCheck-1Timer ................................................................................................. Timer-1TOT/TRND ............................................................................... TOT/TRND-1Vlimiter ......................................................................................... Vlimiter-1VMux ................................................................................................ VMUX-1WAIT DELAY ............................................................................ Wait Delay-1WAIT DI/RWAIT DI ..................................................................... WAIT DI-1WAIT FOR ................................................................................. WAIT FOR-1WAIT TIME ............................................................................. WAIT TIME-1Watchdog ..................................................................................... Watchdog-1XMTR_Interface...............................................................XMTR_Interface-1

Index

ACCOL II Reference ManualPage vii

BLANK PAGE

What’s New in ACCOL?

ACCOL II Reference ManualPage ix

New Features

New EAUDIT Modes for Protected Mode Users

Users with 386EX Protected Mode PLS/PLX/PES/PEX 04.43 (or newer) firmwarenow have new Modes for the EAUDIT Module, that allow the module to start andstop logging under user control.

Communication Enhancements Added for 186-level firmware

Certain communication enhancements such as dial-up-ack, and immediate responsedelay, which had been included for other platforms, have now been extended to 186-based versions of the DPC 3330, DPC 3335, and RTU 3310. Users require AM.20 (ornewer) firmware and ACCOL Workbench Version 8.3 (or newer) to take advantageof these enhancements.

Support for New High Density High Speed Counter Board

Protected Mode controllers now support the High Density High Speed CounterBoard, allowing up to 8 high speed counter channels. This requires Protected ModePLS/PLX/PES/PEX 04.40 (or newer) firmware. See the ‘Process I/O’ section fordetails.

Encode Module Enhancements

The Encode Module now incorporates two new functions (9 and 10). Function 9takes the elements in a column of a logical array (or logical values from a signallist) and converts them into the equivalent binary integer. Function 10 takes abinary integer and converts it to logical values in a signal list or logical data array.To use these new functions, you must have TeleFlow / TeleRTU firmware TFA01.28/ TRA01.28 (or newer) firmware or Protected Mode PLS/PLX/PES/PEX 04.40 (ornewer) firmware. See the ‘Encode’ section for details.

ISO5167 Module Enhancements

The ISO5167 Module has been enhanced to support an additional method forcalculating the flow rate for orifice plates. The new method uses equations from the1998 edition of the ISO5167 standard. This revision is available in Protected Modecontrollers with PLS/PLX/PES/PEX 04.40 or newer firmware. See the ‘ISO5167’section for details.


ACCOL II Reference ManualPage x

New System Signal - #ONLBAT..

Beginning with Protected Mode firmware PLS/PLX/PES/PEX 04.40, a new systemsignal has been created to allow the user to prevent the on-line RAM backupbattery diagnostics from being performed. See the ‘System Signals’ section fordetails.

Portstatus Module Changes

The Portstatus Module has been changed to support on-line changes in the modebetween Enron Modbus Slave and Gould Modbus Slave. NOTE: These changesrequire TeleFlow/TeleRTU TFA/TFR 01.28 firmware, or Protected ModePLS/PLX/PES/PEX 04.40 firmware with PCP/PCE 04.40 custom firmware. Fordetails on these changes, see the ‘Portstatus’ section, and the ACCOL II CustomProtocols Manual (document# D4066).


1NOTE: The PLS or PES firmware can execute in a controller with the NPX, but the NPXhardware will NOT be used. The PLX or PEX firmware CANNOT execute in a controller that doesNOT include the numeric NPX hardware.

ACCOL II Reference ManualPage xi

ACCOL Firmware/ACCOL Tools Versions

ACCOL firmware may be purchased for several different platforms. Not all featuresare common to all firmware versions. Which version is appropriate depends uponthe Network 3000 controller platform being used.

Firmware Version: Platforms Used With: Recommended revision ofACCOL Workbench forfull compatiblity.

PLS04.43/PLX04.43

PLS is the standardfirmware; PLX isrequired to make use ofthe numeric co-processor(NPX) hardware.1

386EX Protected ModeCPU versions of:

DPC 3330 DPC 3335 RTU 3310

Use ACCOL Workbench8.3 (or newer)

PES04.43/PEX04.43

PES is the standardfirmware; PEX isrequired to make use ofthe numeric co-processor(NPX) hardware.1

386EX Protected ModeCPU with Ethernet boardversions of:

DPC 3330DPC 3335


RMS04.12 386EX Real Mode CPUversions of:

DPC 3330DPC 3335RTU 3310


AM.20 186-based CPU versionsof:

DPC 3330DPC 3335RTU 3310



Firmware Version: Platforms Used With: Recommended revision ofACCOL Workbench forfull compatiblity.

ACCOL II Reference ManualPage xii

LS502.2 RTU 3305 Use ACCOL Workbench8.0 (or newer)

TFA01.30 EGM 3530-10B TeleFlow,EGM 3530-20B TeleFlowPlus


TRA01.30 RTU 3530-15B TeleRTURTU 3530-25B TeleRTUPlus


Notes About Using Older DOS-based ACCOLTools:

For support purposes, the ACCOL II Reference Manual includes many referenceswhich are specific to DOS-based tools (AIC, Toolkit, Taskspy, ABC, REV, ACLINKetc.) Although still available, development on these tools has been frozen at version5.13, and no additional enhancements or releases are contemplated. These tools areINCOMPATIBLE WITH ALL PROTECTED MODE FIRMWARE, AND ALLVERSIONS OF TeleFlow/TeleRTU FIRMWARE. IN ADDITION, THERE ARELIMITS ON DOS-TOOL COMPATIBILITY WITH RTU 3305 FIRMWAREREVISIONS HIGHER THAN LS500.

Users with other platforms (GFC 3308 as well as 186 and 386EX Real Modeversions of the DPC 3330, DPC 3335, and RTU 3310) can still use the DOS-basedtools to create ACCOL loads, however, any features newer than ACCOL Version5.13 will NOT be available.

All users with newer firmware are strongly urged to upgrade to ACCOL Workbench.

Optional Comm Port NOT Available in Protected Mode

The Optional Communication Port (TANO) is NOT available in 386EX ProtectedMode units. Support still exists in 186-based units, and in 386EX Real Mode units.


ACCOL II Reference ManualPage xiii

No Synchronous Communication or Remote I/O (RIO) Supportfor RTU 3310 with 386EX or for any 386EX unit without theEnhanced Communication Board

RTU 3310 controllers with the 386EX CPU engine board, as well as any other386EX unit which does not have an enhanced communication board, DO NOTsupport synchronous communication. RIOR ports will not function, because of thislack of synchronous communication capability. See the ’Communication Ports’section for details.

Flash Program For Installing Field Upgrades of SystemFirmware (For units with FLASH support ONLY)

To install field upgrades of system or custom protocol firmware, a copy of the FlashProgram FLASH.EXE is required. This program is available on diskette, togetherwith the Master Flash File FLASH.MST and the binary system (*.BIN) files neededfor various controller platforms. Information regarding the installation/use of thisprogram is included in a text file on the diskette containing the FLASH program.

BLANK PAGE

Hardware and Software Requirements

ACCOL II Reference ManualPage xv

This chart shows the minimum ACCOL software tools and firmware revisionsnecessary to use a particular ACCOL module or structure on a particular hardwareplatform. For example, to use the AGA3 Module with a 186-based DPC 3330requires ACCOL Tools version 4.0 (or newer) and S (or newer) level firmware.Unless otherwise noted, modules available in a particular software or firmwarerevision remain available in all subsequent revisions.

A check mark ’�’ in the column for the 3350/3380/3385 indicates that a module orstructure is compatible, and has existed since before ACCOL tools version 4.2 and Sfirmware.

All ACCOL Tools versions above Version 6.0 refer to ACCOL Workbench software.

A � filling a particular table cell indicates that the module or structure is NOTsupported for this platform.

ACCOL Moduleor Structure

3350 /3380 / 3385

(SeeNote 1)

3310,3330,3335with 186CPU(SeeNote 2)

3310,3330,3335with386EXRealModeCPU(See Note3)

3310,3330,3335with386EXProtectedModeCPU(See Note4)

3308-10A,3308-30A,3308-10B,3308-30B,3308-50B(See Note 5)

3305 (See Note11)

3530-10B,3530-20B,3530-15B,3530-25B(See Note12)

AAT 8.01PLS04.30

8.01TFA01.26/TRA01.26

ABORT � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500

ACCOL Workbench(RM) 1.1TFA01/TRA01

AGA3 � 4.0S

5.10RMS00

6.0PLS00


AGA3Dens 6.3PLS03

AGA3ITER 5.7AH

5.10RMS00

6.0PLS00

5.7C.01

5.13LS500


AGA3TERM (SeeNote 6)

5.4AE

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500




3350 /3380 / 3385

(SeeNote 1)

3310,3330,3335with 186CPU(SeeNote 2)



3308-10A,3308-30A,3308-10B,3308-30B,3308-50B(See Note 5)

3305 (See Note11)

3530-10B,3530-20B,3530-15B,3530-25B(See Note12)

ACCOL II Reference ManualPage xvi

AGA5 � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


AGA7 � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


AGA8 (1985 version)

5.2AC.20

5.2AC.10

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500

AGA8DETAIL 5.7AH

5.10RMS00

6.0PLS00

5.7C.01

5.13LS500


AGA8GROSS 5.7AH

5.10RMS00

6.0PLS00

5.7C.01

5.13LS500


ANIN � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


ANOUT � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


ARC_STORE 6.0PLS00

ACCOLWorkbench(RM) 1.0LS501


AUDIT 5.1AC.20

5.0AA

5.10RMS00

6.0PLS00

AVERAGER � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


BREAK � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


C (comment) � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


CALCULATOR � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500




3350 /3380 / 3385

(SeeNote 1)

3310,3330,3335with 186CPU(SeeNote 2)



3308-10A,3308-30A,3308-10B,3308-30B,3308-50B(See Note 5)

3305 (See Note11)

3530-10B,3530-20B,3530-15B,3530-25B(See Note12)

* EAudit usage in RTU 3305 with LS501 (or newer) firmware requires ACCOL Workbench software. Older DOS-basedACCOL Tools do NOT support EAudit in the RTU 3305 with any firmware revision newer than LS500.

ACCOL II Reference ManualPage xvii

CHARACTERIZE 5.2AC.20

5.2AC.10

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500

COMMAND � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


COMPARATOR � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


CUSTOM � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


DACCUMULATOR 5.9AK

5.10RMS00

6.0PLS00

5.13LS500


DEMUX � 4.0S

5.10RMS00

6.0PLS00

DIFFERENTIATOR � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


DIGIN � 4.0S

5.10RMS00

6.0PLS00

5.6B.01

5.13LS500


DIGOUT � 4.0S

5.10RMS00

6.0PLS00

5.6B.01

5.13LS500


EASTATUS 5.6AG

5.10RMS00

6.0PLS00

5.6B.01

5.13LS500

EAUDIT 5.4AE

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500 *


EDEMUX 5.4AE

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500




3350 /3380 / 3385

(SeeNote 1)

3310,3330,3335with 186CPU(SeeNote 2)



3308-10A,3308-30A,3308-10B,3308-30B,3308-50B(See Note 5)

3305 (See Note11)

3530-10B,3530-20B,3530-15B,3530-25B(See Note12)

ACCOL II Reference ManualPage xviii

EINTEGRATOR 5.4AE

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


ELSE � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


ELSEIF � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


EMASTER 5.6AG

5.10RMS00

6.0PLS00

5.6B.01

5.13LS500

EMUX 5.4AE

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


ENCODE (SeeNote 7)

� 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


ENDFOR � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


ENDIF � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


ETOT/TRND 5.12AL

5.12RMS02

6.0PLS00

5.13LS500


EVP 7.1PLS04

FOR � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


FPV � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


FUNCTION � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


GBBTI 5.8AJ

5.10RMS00

6.0PLS00



3350 /3380 / 3385

(SeeNote 1)

3310,3330,3335with 186CPU(SeeNote 2)



3308-10A,3308-30A,3308-10B,3308-30B,3308-50B(See Note 5)

3305 (See Note11)

3530-10B,3530-20B,3530-15B,3530-25B(See Note12)

ACCOL II Reference ManualPage xix

GOTO � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


GPA8173 7.1PLS04

GSV 7.1PLS04

HCBO 5.7AH

5.10RMS00

6.0PLS00

HILOLIMITER 5.4AE

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


HILOSELECT 5.4AE

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


HSANIN 5.2AC.10

5.10RMS00

6.0PLS00

HSCOUNT � 4.0S

5.10RMS00

6.0PLS00


HWSTI 5.41AF

5.10RMS00

6.0PLS00

IF � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


INTEGRATOR � 4.0S

5.10RMS00

6.0PLS00


Internet Protocol 6.3PES03

IP_Client 6.3PES03

IP_Server 6.3PES03



3350 /3380 / 3385

(SeeNote 1)

3310,3330,3335with 186CPU(SeeNote 2)



3308-10A,3308-30A,3308-10B,3308-30B,3308-50B(See Note 5)

3305 (See Note11)

3530-10B,3530-20B,3530-15B,3530-25B(See Note12)

ACCOL II Reference ManualPage xx

ISO5167 5.8AJ

5.10RMS00

6.0PLS00

5.8C.02

5.13LS500

KEYBOARD 5.0AA

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


LBBTI 5.8AJ

5.10RMS00

6.0PLS00

LCBO (See Note 8 ) 5.7AH

5.10RMS00

6.0PLS00

LEAD/LAG � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


Liquid_Density 7.1PLS04

LLANIN � 5.0AA

5.10RMS00

6.0PLS00

LOGGER � 4.0S

5.10RMS00

6.0PLS00

5.6B.01

5.13LS500

LSCOUNT � 4.0S

5.10RMS00

6.0PLS00

5.6B.01

5.13LS500

MASTER � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500

MUX � 4.0S

5.10RMS00

6.0PLS00

NODESTATUS 5.5AF

5.10RMS00

6.0PLS00

5.6B.01

5.13LS500

PDM � 4.0S

5.10RMS00

6.0PLS00

5.6B.01

5.13LS500

PDO � 4.0S

5.10RMS00

6.0PLS00

5.6B.01

5.13LS500




3350 /3380 / 3385

(SeeNote 1)

3310,3330,3335with 186CPU(SeeNote 2)



3308-10A,3308-30A,3308-10B,3308-30B,3308-50B(See Note 5)

3305 (See Note11)

3530-10B,3530-20B,3530-15B,3530-25B(See Note12)

ACCOL II Reference ManualPage xxi

PID3TERM � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


PORTSTATUS 5.2AC.20

5.0AA

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


RANIN 5.3AD

5.10 RMS00(See Note9)

6.0 PLS00(See Note9)

RANOUT 5.3AD



RBE 5.5AF

5.10RMS00

6.0PLS00

5.6B.01

5.13LS500

RDIGIN 5.3AD



RDIGOUT 5.3AD



REDUNDANCY 5.2AC.20(SeeNote 10)

5.3AD

5.10 RMS01

6.0PLS00

RESUME � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


RHSCOUNT 5.3AD





3350 /3380 / 3385

(SeeNote 1)

3310,3330,3335with 186CPU(SeeNote 2)



3308-10A,3308-30A,3308-10B,3308-30B,3308-50B(See Note 5)

3305 (See Note11)

3530-10B,3530-20B,3530-15B,3530-25B(See Note12)

ACCOL II Reference ManualPage xxii

RIOSTATS 5.3AD



RLLANIN 5.3AD



RLSCOUNT 5.3AD



RPDM 5.3AD



RPDO 5.3AD



RWAIT DI 5.3AD



RWAIT DIH 5.3AD



RWAIT DIL 5.3AD



SCHEDULER � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500



3350 /3380 / 3385

(SeeNote 1)

3310,3330,3335with 186CPU(SeeNote 2)



3308-10A,3308-30A,3308-10B,3308-30B,3308-50B(See Note 5)

3305 (See Note11)

3530-10B,3530-20B,3530-15B,3530-25B(See Note12)

ACCOL II Reference ManualPage xxiii

SEQUENCER � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500

SLAVE � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


SMART 5.4A.01

STEPPER � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500

STORAGE � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


SUSPEND � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


SYS_3530 ACCOL Workbench(RM) 1.1TFA01/TRA01

SYSTEM � 4.0S

5.10RMS00

5.4A.01

5.13LS500


SYSTEM0 � 4.0S

5.10RMS00

5.4A.01

5.13LS500


TCHECK 5.8AJ

5.10RMS00

6.0PLS00

5.8C.02

5.13LS500

TCOUNT 5.4A.01

5.13LS500

TIMER � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


TOT/TRND � 4.0S

5.10RMS00

6.0PLS00

5.4A.01


VLIMITER 5.4AE

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500




3350 /3380 / 3385

(SeeNote 1)

3310,3330,3335with 186CPU(SeeNote 2)



3308-10A,3308-30A,3308-10B,3308-30B,3308-50B(See Note 5)

3305 (See Note11)

3530-10B,3530-20B,3530-15B,3530-25B(See Note12)

ACCOL II Reference ManualPage xxiv

VMUX 5.4AE

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


WAIT DELAY � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


WAIT DI � 4.0S

5.10RMS00

6.0PLS00

5.6B.01

5.13LS500

WAIT DIH � 4.0S

5.10RMS00

6.0PLS00

5.6B.01

5.13LS500

WAIT DIL � 4.0S

5.10RMS00

6.0PLS00

5.6B.01

5.13LS500

WAIT FOR � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


WAIT TIME � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500


WATCHDOG � 4.0S

5.10RMS00

6.0PLS00

5.4A.01

5.13LS500

XMTR_Interface 6.2PLS02

ACCOLWorkbench(RM) 1.0LS501


NOTES:1) Software and firmware for the RDC 3350, UCS 3380, and CFE 3385 units has not been updated since version 5.2 of the

ACCOL Tools and revision AC.21 firmware. Support for this platform continues up through and including version 5.13 ofthe DOS-based ACCOL Tools.This hardware platform is NOT supported in Windows-based ACCOL Workbench tools.

2) Version 4.0 of the DOS-based ACCOL Tools was the first release to support the 186-based DPC 3330 platform. The firstfirmware release for the DPC 3330 was revision S. The DPC 3335 and RTU 3310 units share the same firmware, but wereadded to the product line at a later date. Version 5.13 was the final release of the DOS-based ACCOL Tools. The 186-basedCPU DPC 3330, DPC 3335, and RTU 3310 units continue to be supported via Windows-based ACCOL Workbench (RM).

3) The first release of DOS-based ACCOL Tools to support the 386EX Real Mode versions of the DPC 3330, DPC 3335 andRTU 3310 was Version 5.10. The first firmware release (which incorporated FLASH memory, instead of PROMs) wasRMS00. Users with firmware more recent than RMS02 should use ACCOL Workbench (RM) instead of DOS-based ACCOLtools.

4) The first release of ACCOL Tools to support the 386EX Protected Mode versions of the DPC 3330, DPC 3335, and RTU 3310was version 6.0, This release uses ACCOL Workbench, and Open BSI Utilities. PLS00 and PLX00 were the first firmwarereleases for the Protected Mode platform; PLS is the standard firmware which uses software math libraries to perform


ACCOL II Reference ManualPage xxv

calculations; PLX performs calculations using the numeric co-processor (NPX) hardware. PES/PEX refer to ProtectedMode units with Ethernet boards installed; PES is the standard firmware for Ethernet; PEX is used with the numeric co-processor (NPX). NOTE: Controllers with the numeric co-processor hardware (NPX) can execute the standard firmware; butcontrollers WITHOUT the numeric co-processor hardware (NPX) CANNOT execute the firmware designed to use the NPX.

5) Firmware revisions beginning with "A" are for -10A, -30A units ONLY. All other firmware revisions shown are for -10B, -30B, and -50B units ONLY. Tools support for these units is available in ACCOL Workbench (RM); C.04 is the most recentfirmware revision.

6) Prior to ACCOL Tools Ver. 5.7 and AH firmware, the AGA3Term Module was named AGAT3.7) Not all functions of the Encode Module are available with all versions.8) From Version 5.5/AF.01 through 5.6/AG, the LCBO Module was named ’CBO’.9) Remote I/O Modules are NOT available in any 386EX version of the RTU 3310. They are available in DPC 3330 and DPC

3335 units only, PROVIDED THAT THOSE UNITS HAVE THE ENHANCED COMMUNICATION BOARD.10) The Redundancy Module for the RDC 3350, UCS 3380, and CFE 3385 platform requires APMC hardware.11) Version 5.13 of the ACCOL Tools was the first release to support the RTU 3305. LS500 was the first firmware release for the

RTU 3305 platform. ACCOL Workbench (RM) also supports the RTU 3305.12) ACCOL Workbench (RM) 1.01Beta was the first release to support the TeleFlow/TeleRTU family of products (EGM 3530-

10B, EGM 3530-20B, RTU 3530-15B, RTU 3530-25B) however, 1.1 is the first full release. In the July, 1997 release of thismanual ’ATS00’ was listed as the first firmware release for the 3530 family, however, TeleFlow/TeleRTU firmware hassince adopted the naming convention TFAxx (for TeleFlow) and TRAxx (for TeleRTU).


ACCOL II Reference ManualPage xxvi

RIO 3331 Compatibility - 186-based units

ACCOL ToolsRevision Level

Firmware (PROMs) in3310/3330/3335

Firmware (PROMs) inattached RIO 3331unit

Result

ACCOL 5.3 through5.8

AD (or newer) A.01 (or newer) COMPATIBLE

ACCOL 5.9 (or newer)without high densityprocess I/O boards inRIO 3331 unit

AD (or newer) A.01 (or newer) COMPATIBLE

ACCOL 5.9 (or newer)with high-densityprocess I/O boards inthe RIO 3331 unit

AJ.10 (or earlier) Any revision level ACCOL LOAD NOTCOMPATIBLE.REJECTED BY3310/3330/3335

ACCOL 5.9 (or newer)with high-densityprocess I/O boards inthe RIO 3331 unit

AK.00 (or newer) B.04 (or earlier) NOT COMPATIBLE; -7 status appears onmodules referencing3331, 128 statusappears onRIOSTATS Module.

ACCOL 5.9 (or newer)with high-densityprocess I/O boards(8AI, 4AO, or 16DIonly) in the RIO 3331unit.

AK.00 (or newer) C.01 (or newer) COMPATIBLE

ACCOL 5.12 (ornewer) with high-density process I/Oboards (8AI, 4AO,16DI, or 16DO) in theRIO 3331 unit.

AL.00 (or newer) RIO 4.0 (or newer) COMPATIBLE


ACCOL II Reference ManualPage xxvii

RIO 3331 Compatibility - 386EX-based units(DPC 3330, DPC 3335 with enhanced communication board ONLY)

ACCOL ToolsRevision Level

Firmware in3330/3335 (Note: RTU3310 with 386EX doesNOT support RIO)

Firmware (PROMs) inattached RIO 3331unit

Result

ACCOL 5.10 (ornewer) without high-density process I/Oboards in RIO 3331unit

RMS00 (or newer) A.01 (or newer) COMPATIBLE

ACCOL 5.10 (ornewer) with high-density process I/Oboards in RIO 3331unit.

RMS00 (or newer) B.04 (or earlier) NOT COMPATIBLE-7 status appears onmodules referencing3331, 128 statusappears onRIOSTATS module.

ACCOL 5.10 (ornewer) with 8AI,4AO, or 16DI high-density process I/Oboards in 3331 unit

RMS00 (or newer) C.01 (or newer) COMPATIBLE

ACCOL 5.11 (ornewer) with 8AI,4AO, 16DI, or 16DOhigh-density processI/O boards in 3331unit

RMS01 (or newer) RIO 4.0 (or newer) COMPATIBLE

BLANK PAGE

Summary of ACCOL II Structures

ACCOL II Reference ManualPage xxix

The following tables summarize fixed structural limits within ACCOL IIsoftware/firmware. In addition to these limits, all ACCOL loads are limited by theamount of available memory.

ACCOL TasksStructure: Limit: Version-specific Notes:

ACCOL Tasks in anACCOL load

127 (ACCOL Tools 5.13and earlier)

1,000 (ACCOL Tools 6.0and newer)

Limit increased becauseof greater amount ofmemory in 386EXProtected Mode units.

Lines allowed in anACCOL Task

9,999 None

Calculator Modules / ExpressionsStructure: Limit: Version-specific Notes:

Number of lines whichmay be entered in theCalculator

9,999 None

Total number of byteswhich may be used by allCalculator Modulescombined

64K (ACCOL Tools 5.12and newer 5.x)

128K (ACCOL Tools 6.0)

ACCOL Version 5.11(and earlier) restrictedthe size of individualCalculator Modules to4,096 bytes.


ACCOL II Reference ManualPage xxx

SignalsStructure: Limit: Version-specific Notes:

Number of ACCOLsignals in load

3,500 (ACCOL Tools 5.13and earlier)

approx. 21,000 (ACCOLTools 6.0 and newer)


Number of unique basenames in load




Number of uniqueextensions in load




Number of uniqueattributes in load




Length of units text foranalog signals

Maximum length: 6characters

None

Length of ON/OFF textfor logical signals

Maximum length: 6characters for ON text, 6characters for OFF text

None

Number of analog signalunits text entries in load

255 None

Number of ON/OFFlogical text pairs in load

255 None


ACCOL II Reference ManualPage xxxi

Signal ListsStructure: Limit: Version-specific Notes:

Number of Signal Listsallowed in ACCOL load

255 None

Number of signals(entries) allowed in Signal Lists

up to 3,999 in a singlelist (ACCOL 5.13 orearlier tools)

up to approx. 32,000entries total among ALLsignal lists (ACCOL 6.0or newer tools)

Limit changed because ofmemory in 386EXProtected Mode units.

FormatsStructure: Limit: Version-specific Notes:

Number of Formats (forASCII communications,e.g. using Logger Module)

999 (ACCOL 5.13 orearlier tools)

9,999 (ACCOL 6.0 ornewer tools)


Maximum size of Format 32,000 bytes None


ACCOL II Reference ManualPage xxxii

Data ArraysStructure: Limit: Version-specific Notes:

Number of Analog DataArrays in load

255 None

Maximum number ofarray elements in AnalogData Array

8,000 elements (ACCOL5.1 through 5.8 tools)

16,000 elements (ACCOLVersion 5.9 through 5.13tools)

(65,535 rows * 65,535columns) in ACCOL 6.0Tools (and newerversions)

None

Number of Logical DataArrays in load

255 None

Maximum number ofarray elements in aLogical Data Array

32,000 elements (ACCOL5.1 through 5.13 tools)

(65,535 rows * 65,535columns) in ACCOL 6.0Tools (and newerversions)

None


ACCOL II Reference ManualPage xxxiii

Expanded Memory (Not applicable to 386EX Protected Mode Units)

Structure: Limit: Version-specific Notes:

Storage Module Rows (64bytes each)

5,120 rows None

Templates (128 byteseach)

500 (ACCOL Version 5.5and earlier tools)

2,000 (ACCOL Version5.6 and newer tools)

None

Audit Trail Events (16bytes each)

4,096 (ACCOL Version5.13 and earlier tools)

Up to 4,096 events and4,096 alarms in ACCOLWorkbench (RM) 1.0 andnewer with RMS04,LS501 or newerfirmware.

Up to 65,535 events and65,535 alarms in ACCOLVersion 6.0 and newer.

Limit increased becauseof greater memory.

AGA8 Calculations 8,000 bytes (fixed) None

Custom RAM 32,000 bytes None


ACCOL II Reference ManualPage xxxiv

Base Memory and Expanded Memory Options (Not applicable to 386EX Protected Mode Units)

Platform: Base Memory: Expanded Memory:

DPC 3330, RTU 3310 with 186-based CPU

64K 0K or64K or320K

DPC 3335 with 186-based CPU

64K 0K or64K or192K

DPC 3330, DPC 3335,RTU 3310 with 386EX Real ModeCPU

64K 444K

GFC 3308 64K 192K

RTU 3305 64K 440K

EGM 3530 or RTU 3530 64K 64K or448K

RDC 3350, UCS 3380,CFE 3385

64K 0K or64K

Memory - 386EX Protected Mode units

DPC 3330, DPC 3335 and RTU 3310 units with the 386EX Protected Mode CPUsupport the following memory configurations:

512 K1.5 MB2.5 MB3.5 MB4.5 MB

AATAuto Adjust Module


Page AAT-1

AAT

The AAT Module performs adjusted volume calculations and self-check calculations for an Invensys (Equimeter) Auto-adjust TurbineMeter (AATM). The module can be used in place of the StandardElectronic Readout (SER) typically used with Auto-adjust meters. Themodule frequency and count inputs are supplied by an ACCOL High-speed Counter module.

The AATM generates pulses from both a Main and Sensor rotor.

The AAT module implements an algorithm designed by Invensys toprovide the following.

· Volume that is corrected back to factory calibration eventhough the meter Main rotor is running slower than itshould because of wear or lack of lubrication.

· A periodic self-check that calculates how much the meterhas deviated from factory calibration and computes a newcorrection factor.

· Status and alarm indications when the self-check indicatesthat the meter has exceeded configured warning and alarmlimits.

· Status indication when the flow of gas is non-steady orwhen rotor pulses have been lost.


Page AAT-2


❏ Module Terminals

FREQ1 Default: None, entry is required. Nocomputation will be performed ifthis terminal is not wired.

Format: Analog signalInput/Output: Input

is the frequency of the Main rotor in Hz (pulses per second).

FREQ2 Default: None, entry is required. Nocomputation will be performed ifthis terminal is not wired.

Format: Analog signal.Input/Output: Input

is the frequency of the Sensor rotor in Hz.

COUNT1 Default: None, entry is required ifCOUNT2 is wired. No adjustedvolume computation will beperformed if only one COUNTterminal is wired.


is the count of Main rotor pulses. This signal should come from theCOUNT terminal of an HSCOUNT module. Note: The AAT modulewill reset this signal to zero after it reads the count value.



Page AAT-3

COUNT2 Default: None, entry is required ifCOUNT1 is wired. No adjustedvolume computation will beperformed if only one COUNTterminal is wired.


is the count of Sensor rotor pulses. This signal should come from theCOUNT terminal of an HSCOUNT module. Note: The AAT modulewill reset this signal to zero after it reads the count value.

LIST1 Default: None, entry is required and thelist must contain only analogsignals.

Format: Analog signal or constantInput/Output: Input

is the number of the list containing the signals holding Auto-adjustcalibration data from the tag located on the meter and user configura-tion settings. These are:

Tag data:

BTSF Blade-tip Sensor Factor (should be 1.0 for slot sen-sors)

KM Main rotor factor

KS Sensor rotor factor

ABAR Average relative adjustment

Configuration data:

ABH Abnormal delta-Abar high limit in percent


Page AAT-4


ABL Abnormal delta-Abar low limit in percent

WBH Normal delta-Abar high limit in percent

WBL Normal delta-Abar low limit in percent

INCR Adjusted and un-adjusted flow total scaling factor.Adjusted and unadjusted volume totalizing is notdone when this value is zero.

Kmo Mechanical output factor. Unadjusted volume totaliz-ing is not done when this value is zero.

LIST2 Default: None – use is optionalFormat: Analog signal or constantInput/Output: Input

Is the number of the list (optional) that contains signals that will holdinternal AAT calculation data and count totals. These are typicallyused to verify that the module is operating properly for establishedconditions. They are:

Vai. Adjusted volume rate in CF per second

Pmavg. The average Main rotor rate in CF per second.

Psavg. The average Sensor rotor rate in CF per second.

Vm. Main rotor adjusted volume

Vs. Sensor rotor adjusted volume.

R60 An internal 60 second timer. This count only incre-ments when Main rotor frequency in Hz is less than 3times the BTSF.

R512. An internal 512 second (8.53 minute) timer. Whenthe Main rotor frequency is below 48 Hz (i.e. more



Page AAT-5

than 512 seconds to accumulate 25000 counts) thissignal will reach 512 and rollover, forcing a check ofthe Sensor rotor frequency, and clearing the C25kvalue.

C25k. The internal count of Main rotor pulses. This countwill rollover at 25000 counts, forcing a Sensor rotorfrequency check and clearing R512.

LIST3 Default: None, entry is required and thelist must contain only analogsignals.


is the number of the list containing signals that will hold the AATcalculation output data. These are:

Rate Adjusted flow rate in CF per hour. When Sensorrotor pulses have been lost this value is theunadjusted rate from the Main rotor only.

Vmi The unadjusted main rotor rate CF per second.

Vsi The unadjusted sensor rotor rate in CF persecond

Delta-Abar The calculated percent deviation of Abar fromcalibration.

Delta-Va The adjusted volume change since the modulelast executed.

TotA The total adjusted volume; it rolls over at avalue of ten million. To obtain total CF multiplyTotA by INCR. If TotA has been accumulatingand INCR is set to zero the TotA will remain atits last value. If INCR is set negative TotA is setto zero. When Sensor rotor pulses are lost TotA


Page AAT-6


is the sum of any previous adjusted volume andthe unadjusted volume from the Main rotor,provided Kmo is greater than zero.

INCR Scale1 110 10100 100

TotM The total un-adjusted volume; it rolls over at avalue of ten million. To obtain total unadjustedCF multiply TotM by INCR. If INCR is setnegative TotM is set to zero. When Sensor rotorpulses are lost this value contains the totalunadjusted volume from the Main rotor, pro-vided Kmo is greater than zero. Subtract thisvalue from the TotA value to obtain the adjustedtotal.

STATUS1 Default: NoneFormat: Analog signalInput/Output: Output

is the module input terminal status and the Non-steady flow status. Itcontains values as follows:

0 Good-1 A required Module terminal is unwired i.e. FREQ1,

FREQ2, LIST1, LIST3 or one of the COUNT termi-nals is wired but the other is not.

-2 List 1 is invalid or contains a non-analog signal orKm, Ks, or Abar is zero.

-3 List 2 is invalid or contains a non-analog signal.-4 List 3 is invalid or contains a non-analog signal.-5 Non-steady flow (NSF)



Page AAT-7


is the Abnormal (ABN) status indication.

0 Good-1 Delta-A is outside the configured normal limits.-2 Delta-A is outside the configured abnormal limits.


is the Alarm (ALM) status indication.

0 Good-1 Delta-A is outside the configured abnormal limits.


is the System (SYS) status indication.

0 Good-1 No flow or loss of both Main and Sensor pulses.-2 Leakage or resonant no-net flow (with ABN = -1).-3 No Main rotor pulses or leakage or resonant no-net

flow.-4 No Sensor rotor pulses.


Page AAT-8


❏ Status Indications

The Status signals indicate a number of different conditions dependingon their values. Multiple error status conditions can exist simulta-neously.

STATUS1 STATUS2 STATUS3 STATUS4NSF ABN ALM SYS Condition

0 0 0 0 Good

-1 0 0 0 A required terminalis unwired.

-2 0 0 0 List 1 is invalid orcontains a non-analog signal.



-5 0 0 0 Non-steady flowalarm.

0 -1 0 0 Delta-Abar isoutside Normallimits

0 -2 -1 0 Delta-Abar isoutside Abnormallimits



Page AAT-9

STATUS1 STATUS2 STATUS3 STATUS4 (Continued)0 0 0 -1 No flow or loss of

both rotor pulses.

0 0 0 -2 Leakage or noresonant net flow

0 0 0 -3 No main rotorpulses

0 0 0 -4 No sensor rotorpulses

❏ Meter ConnectionsThe AATM pulses connect to the 33xx or 35xx physical High-speedcounter inputs. Best operation is obtained when the AATM or Protec-tive barrier is connected in “emitter-follower” fashion, where the High-speed counter input has a 1000 ohm resistor connected to common andthe AATM or barrier drive transistor “pulls up” to the positive supplyrail.

❏ Usage with AGA7 calculationsThe AAT Module generates an “adjusted” output i.e. the rate andadjusted volume has been adjusted to remove the effect of meter wear.To obtain corrected rates and volumes these outputs should be wiredto an AGA7 module. The adjusted rate in CF/hr can be wired to anAGA7 module to generate corrected rate in SCF/hr that can then beintegrated to obtain hourly and daily corrected volume totals.

The AAT delta adjusted volume output can also be wired directly to anAGA7 module. This signal contains the adjusted volume change fromthe previous module execution. When this delta-volume is wired toAGA7 the correction is done only on the newest volume. The output ofAGA7 is then a corrected delta-volume that can be summed to hourlyand daily totals.

BLANK PAGE

AbortAbort Statement


Page Abort-1

The Abort statement, like Suspend and Resume, performs taskcontrol. It is typically used by one task to affect the operation of othertasks in the load. However, it can also be used to affect the operationof the task where it resides.

When a task first receives the Abort signal, it will continue to rununtil the interrupted task line (ACCOL module or control statement)has completed execution. The Aborted task will then terminate execu-tion until its next rate interval, when it will start execution from thefirst module in the task. This statement is chiefly used to terminatesequence-type tasks that have been assigned continuous rate inter-vals.

If the Abort statement references a task that does not exist, no actionwill be taken.

❏ SyntaxABORT task

where:

task identifies the target task. It must be separated from thecommand by a space.

❏ ExampleTo abort the current execution of task number 8 from another task,enter the statement:

ABORT 8

in the other task. Task 8 will then resume execution from the begin-ning at its next scheduled execution time, based on the task rate.

Abort

BLANK PAGE

AGA3American Gas Association Report No. 3 Module

Page AGA3-1


The AGA3 Module performs the gas flow calculations specified by theAmerican Gas Association, Report No.3 (AGA-3) ANSI/API 2530,1985 edition.1 The output of this module is the rate of flow of a gasthrough an orifice plate in thousands of cubic feet per hour (MSCFH).

Module TerminalsDIFF_PRESS(hw)

is the differential pressure across an orifice in inches/water at 60o F.

STAT_PRESS

is the static pressure of the flowing gas in psig.

1. In general, it is recommended that AGA3TERM be used instead of AGA3 because itprovides greater flexibility of use. Users requiring AGA3 calculations based on the Nov.,92 (2nd edition) of the AGA3 report should use the AGA3ITER module.

Default: None, entry requiredFormat: Analog signal or constantInput/Output: Input

PIPE_DIAMORIF_CONST

POINTORIF_DIAM

OUTPUT

TRACK

3ADJ _PRESSDIFF_ PRESSSTAT_ PRESSFLOW_TEMPSPEC_GRAVFPV_INBASE _TEMPBASE _PRESS

Default: None, entry requiredFormat: Analog signal, constantInput/Output: Input

AGA3


Page AGA3-2


ADJ_PRESS

is the average barometric pressure in psia. In the AGA3 Module, thevalue entered as STAT_PRESS is added to ADJ_PRESS to obtainabsolute pressure.

ORIF_DIAM

is the orifice diameter in inches.

PIPE_DIAM

is the inside diameter of the pipe in inches.

ORIF_CONST(K = Fa Fm Fl)

This constant is obtained from the multiplication of three factors. Thethermal expansion factor corrects for the change in the physical sizeof the orifice plate bore due to the flowing temperature effects of thegas. Where a mercury manometer is used, manometer and latitudefactors must also be calculated. (See Combined Orifice Constant inthis section for more details.)

Default: 14.73 psiaFormat: Analog signal or constantInput/Output: Input

Default: None; entry is mandatoryFormat: Analog signal or constantInput/Output: Input

Default: None; entry is mandatoryFormat: Analog signal or constantInput/Output: Input

Default: 1Format: Analog signal or constantInput/Output: Input


Page AGA3-3


BASE_PRESS(Pb)

is the base or contract pressure of the gas in psia. The base pressurespecified here will be used to calculate Fpb which equals 14.73/Pb.

BASE_TEMP(T

b)

is the required (contract) base temperature of the flowing gas indegrees Fahrenheit. T

b is used to calculate the factor F

tb.

FLOW_TEMP(Tf)

is the flowing temperature of the gas in degrees F. It is used to com-pute Ftf.

FPV_IN

is the supercomcompressibility factor of the gas. This signal can beobtained from the FPV Module.

POINT

is a construction code. This entry applies to the pipe tap and flange

Default: 14.73 psiaFormat: Analog signal or constantInput/Output: Input

Default: 600FFormat: Analog signal or constantInput/Output: Input





Page AGA3-4


tap construction described under Base Orifice Factor in this section.

In order to change the value of this terminal while the unit is online, use the following procedure. Change either the PIPE_DIAM orORIF_DIAM value to zero. Enter the new construction code on thePOINT terminal and wait for the task to execute at least once. Set thePIPE_DIAM or ORIF_DIAM back to the original value.

If the value of the POINT terminal is changed off line, manipulation ofthe DIAM terminals as described above is not necessary.

SPEC_GRAV(SG)

is the specific gravity of the flowing gas. This is defined as the ratio ofthe density of the gas to that of dry air at standard conditions.

TRACK

is used to force the gas flow output to zero under certain measurementconditions. It could be used to close a block valve and stop the flow.

If TRACK is an analog value, it will be compared to the value of thedifferential pressure (DIFF_PRESS). As long as TRACK is belowdifferential pressure, the flow-computed output will be furnished tothe OUTPUT terminal. Should the track value exceed the differentialpressure value, the OUTPUT will be set to zero percent of scale. Inthis way, the TRACK signal acts as a cut off limit.

If the TRACK signal is a logical variable, the ON state will allow theflow-computed output to be furnished to the OUTPUT terminal. If the

Default: 0.6Format: Analog signal or constantInput/Output: Input

Default: None, entry is optionalFormat: Analog or logical signalInput/Output: Input


Page AGA3-5


TRACK signal is in an OFF state, the module output will be set tozero percent of scale.

OUTPUT(Qh)

represents the corrected gas flow rate in MSCFH (thousands ofstandard cubic feet per hour).

Gas Flow EquationThe general form of the AGA-3 equation is:

Qh = C’ hw pf

where:

Qh = Quantity rate of flow at base conditions, standard cubic feetper hour (SCFH)

C’ = Orifice flow constanthw = Differential pressure, inches of water at 60oFpf = Absolute static pressure, psia

The orifice flow constant, C’, is composed of various factors, some arefixed by the physical equipment and others vary with the state of theflowing gas. The orifice flow constant is defined as follows:

C’ = Fb Fr Y Fpb Ftb Ftf Fg Fpv K

where:

Default: NoneFormat: Analog signalInput/Output: Output


Page AGA3-6


Fb = Basic orifice factor for a given orifice size and pipe diameterFr = Reynolds number factorY = Expansion factorFpb = Pressure base factorFtb = Temperature base factorFtf = Flowing temperature factorFg = Specific gravity factorFpv = Supercompressibility factorK = Combined orifice constant

Fb is computed using the equations contained in Appendix B of theAGA-3 report.

The term Fr, the Reynolds number correction factor, is calculated

from: b

Fr = 1 + h

w P

f

where b is a constant for a given orifice size and pipe diameter. It iscomputed using equations in Appendix B of the AGA-3 report and iscombined with the linear interpolation of Table 18.

K, the combined orifice constant, is obtained from the expression:

K = Fm Fa Fl

where:

Fm = Manometer factor for mercury-type flowmeters onlyFa = Orifice thermal expansion factorFl = Gravitational correction for mercury manometer factorY, = the expansion factor, is calculated using the equations

described in Appendix B, Section 8 of the AGA-3 report.

These equations are broken up into two factors, one of which dependson the physical equipment, and the other which depends on the stateof the gas.


Page AGA3-7


The other factors are calculated as follows:

14.73Fpb =

Pb

where Pb = contract base pressure

Tb + 459.67

Ftb = 519.67

where Tb is the base temperature in degrees F

519.67Ftf =

Tf + 459.67

Fg is defined by the following expression:

1Fg =

SG

where SG is the specific gravity of the gas.

Combining the various expressions, the basic equation solved by thegas flow block is:

b 14.73 Tb + 459.67 Qh = KFb * 1 + * Y * *

hw Pf Pb 519.67

519.67 hw Pf * Fpv * *

Tf + 459.67 SG


Page AGA3-8


Combined Orifice ConstantThe combined orifice constant is applied to the ORIF CONST terminalto correct for local conditions. For example, it could be calculated fromthe formula:

K = Fm Fa Flwhere:

Fl = latitude factor for mercury manometer/transducers. Specifylatitude in degrees and elevation in feet.

980.665 + ( 0.087*(latitude-45) ) - (9.4x10-5 * elevation) =

980.665

Fm = Manometer factor for mercury manometer/transducers

SG * Fpv2 * Pf

= 1 - 2.699 *844.132 * Ta

where: Ta = ambient temperature, 0F + 460SG = specific gravity of the flowing gasFpv = supercompressibility of the flowing gasPf = absolute pressure of the flowing gas

When mercury manometers are not used, Fl and Fm = 1.

Fa = thermal expansion factor of orifice plate due to the temperature ofthe flowing gas.


Page AGA3-9


For 304 or 316 stainless steel:Fa = 1 + [ 1.85 x 10-5 * (Tf - 68) ]

For SAE carbon steel:Fa = 1 + [ 1.3793 x 10-5 * (Tf - 68) ]

For 430 stainless steel:Fa = 1 + [ 1.1364 x 10-5 * (Tf - 68) ]

(Tf is the temperature of the flowing gas in degrees Fahrenheit.)

Usually these correction factors have minimal effect on the outputsignal. As a result, three different approaches can be taken withrespect to this input of the module:

1. Leave this input signal unwired in which case the calculationoperates as though a default value of 1.0 were used.

2. Compute the value manually and wire a signal with the value to theinput.

3. Compute the value in a Calculator Module and apply that output tothe ORIF_CONST terminal.

Basic Orifice FactorThe AGA3 Module computes a value for the basic orifice factor inter-nally using the orifice diameter, pipe diameter, and a code thatindicates whether pipe or flange taps are used. The pipe diameter andorifice diameter are input signals to the AGA3 Module. Both arespecified in inches. These inputs must be wired to produce a gas flowresult. An integer code value is used at the POINT terminal toindicate the meter construction. The following table shows the code tobe used to indicate tap type and location.


Page AGA3-10


Static Pressure Pipe FlangeMeasured Taps Taps

Upstream 4 2Downstream 3 1

This code affects the calculation of the expansion factor (Y). The basicorifice factor is obtained using a linear interpolation technique basedon the AGA3 tables.

In order to save execution time, parts of the AGA-3 equation affectedby the POINT code, PIPE_DIAM or ORIF_DIAM, are not calculatedevery time the task executes. PIPE_DIAM or ORIF_DIAM values canbe changed on-line and automatic recalculation of the affected param-eters will take place. If the POINT terminal value is the only valuebeing changed you must also change the PIPE_DIAM or ORIF_DIAMvalues as follows:

1. Disable the AGA3 Module OUTPUT via the TRACK signal toprevent erroneous flow rates.

2. Enter the new value on the POINT terminal.

3. Set either the PIPE_DIAM or ORIF_DIAM value to zero.

4. Wait for the task to execute at least once and then set thePIPE_DIAM or ORIF_DIAM back to the original value.

5. Re-enable the module OUTPUT via the TRACK signal.

ACCOL II Reference ManualPage AGA3Dens-1

AGA3DensAmerican Gas Association Report No. 3 - Density Module

The AGA3Dens Module computes mass and volume flow rate for fluids(gases or liquids) in lbs/hour and cubic ft per hour, for orifice plates,with flange taps ONLY, according to the method explained in theAmerican Gas Association (AGA) Report #3 of August, 1992, 3rdEdition (Part 1 and Part 4). This method uses density to perform thecalculations.

Mass flow rate (in pounds per hour at flowing conditions) and Volumeflow rate (in cubic feet per hour at flowing conditions) are calculated.If base density is supplied, the volume rate at base conditions is alsocalculated.

Internal factors used in the calculations can be stored in an ACCOLsignal list for examination.

AGA3Dens


Page AGA3Dens-2


❏ Module EquationThe AGA3Dens Module calculates mass flow rate at flowing condi-tions, per the equation given in the 1992 American Gas Association(AGA) Report #3, Part 4, Equation 4-46a as follows:

qm = Fmass Cd(FT) Y (2 Rhof hw)

where Fmass = Nc Ev (PI * d2) / 4

Y = Expansion factor (set to 1.0 for liquids)

hw = Differential pressure DP.

Cd(FT)= Coefficient of discharge

Rhof = Flowing density

Volume flow rate is calculated: qv = qm / Rhof

If base density is supplied, a base volume rate is calculated:

Qb = qm / Rhob

where

Rhob = Base density

NOTE

This equation is for flange tapped orifice platesONLY.




DIFF_PRESS Default: None, entry requiredFormat: Analog signal or constantInput/Output: Input

is the differential pressure, hw , in inches of water across the orificeplate. Negative input values are clamped at zero, and zero produces azero flow rate.

STAT_PRESS Default: None, entry requiredFormat: Analog signal or constantInput/Output: Input

is the upstream or downstream static pressure, specified in psia.Negative input values are clamped at zero, and zero produces a zeroflow rate. When a downstream pressure is used, the TAP_LOC termi-nal should be a non-zero value.

TAP_LOC Default: OFFFormat: Logical signalInput/Output: Input

indicates the pressure tap location for flange taps. When OFF orunwired, this terminal indicates that the tap location is upstream;when ON this terminal indicates that the tap location is downstream.

When downstream is specified, the differential pressure is convertedto psi and added to the static pressure to obtain an upstream value foruse in calculations. See 'Module Usage Notes.'


Page AGA3Dens-4


ORIF_DIAM Default: None, entry requiredFormat: Analog signal or constantInput/Output: Input

is the orifice bore diameter in inches at the reference temperaturevalue wired to the ORIF_RTEMP terminal. Output of the module willbe zero if the ORIF_DIAM terminal is unwired, or if the value enteredis zero, negative, or larger than 80% of the value on the PIPE_DIAMterminal.

PIPE_DIAM Default: None, entry requiredFormat: Analog signal or constantInput/Output: Input

is the inside diameter of the pipe in inches at the reference tempera-ture value wired to the PIPE_RTEMP terminal. Output of the modulewill be zero if the PIPE_DIAM terminal is unwired, or if the value onthe terminal is zero or negative.

ORIF_COEF Default: 0.00000925Format: Analog signal or constantInput/Output: Input

is the orifice coefficient of thermal expansion in inches per inch-degreeFahrenheit.

PIPE_COEF Default: 0.0000062Format: Analog signal or constantInput/Output: Input

is the pipe coefficient of thermal expansion in inches per inch-degreeFahrenheit.



ORIF_RTEMP Default: 68o FahrenheitFormat: Analog signal or constantInput/Output: Input

is the reference temperature at which the orifice bore was measured.

PIPE_RTEMP Default: 68o FahrenheitFormat: Analog signal or constantInput/Output: Input

is the reference temperature at which the pipe diameter was mea-sured.

FLOW_TEMP Default: 60o FahrenheitFormat: Analog signal or constantInput/Output: Input

is the fluid temperature, Tf , in degrees Fahrenheit.

VISCOSITY Default: 0.010268 centi PoiseFormat: Analog signal or constantInput/Output: Input

is the dynamic viscosity of the fluid at flowing conditions in centiPoise.

ISEN_COEF Default: 0.0Format: Analog signal or constantInput/Output: Input

is the fluid Isentropic exponent. This value is used in the calculation ofthe expansion factor, Y. Positive values from 1.0 to 2.0 are useddirectly; values outside this range are forced to an internal value of


Page AGA3Dens-6


1.3. When the ISEN_COEF terminal is negative or zero, or is unwired,the internal expansion factor Y is set to 1.0 for liquid flow calculations.

FLOW_DENS Default: 0.0Format: Analog signal or constantInput/Output: Input

is the fluid density, in pounds per cubic foot, at flowing conditions. Ifthis terminal is unwired, or wired and zero, the REL_DENS input isexamined for a relative density value.

BASE_DENS Default: 1.0Format: Analog signal or constantInput/Output: Input

is the fluid base density in pounds per cubic foot, at base conditions.

REL_DENS Default: 0.0Format: Analog signal or constantInput/Output: Input

is the density of the liquid being metered relative to water. Thisterminal is used only when FLOW_DENS is unwired, or wired andzero, and the ISEN_COEF indicates a liquid. The input value ismultiplied by the density of water to obtain flowing density for calcu-lations.

TRACK Default: 1.0 or ONFormat: Analog or logical signalInput/Output: Input

is used to force the module output to zero. When a logical signal iswired to this terminal, ON enables calculation, and OFF forces the



output of the module to zero. If an analog signal is wired to thisterminal, it is used as a differential pressure threshold value or 'cutoff'level; calculations cease and the output of the module is forced to zerowhen the DIFF_PRESS terminal value is less than the TRACK value.

MASS_FLOW Default: NoneFormat: Analog signalInput/Output: Output

is the mass flow rate, qm , at flowing conditions in pounds per hour.

VOL_FLOW Default: NoneFormat: Analog signalInput/Output: Output

is the volume flow rate, qv , at flowing conditions in cubic feet perhour.

BASE_FLOW Default: NoneFormat: Analog signalInput/Output: Output

is the volume flow rate, Qb , at base conditions in cubic feet per hour.

LIST Default: NoneFormat: Analog Signal or constantInput/Output: Input

is the number of a signal list into which the factors used in the equa-tion are to be moved. Factors are moved to the list in the followingorder: CD, E, Y, Fmass , FIP , Reynolds number.


Page AGA3Dens-8


❏ Module Usage NotesConditions Which Cause Zero Flow Rate to be output by the Module:

The following conditions can force the flow rate output of theAGA3Dens Module to zero. These are:

a. Negative or zero differential pressure.b. Negative or zero static pressure.c. Negative or zero orifice diameter.d. Negative or zero pipe diameter.e. Orifice diameter larger than 80% of pipe diameter.f. Track terminal conditions are satisfied.g. Negative flowing density.h. Zero flowing density with relative density <=0.

Bounded Inputs:

The isentropic exponent value used internally will be forced to 1.3 ifthe input value is positive but less than 1.0 or larger than 2.0. Theexpansion factor Y used internally will be forced to 1.0 if the inputvalue is negative or zero.

Static Pressure Tap Location:

If the static pressure is from a downstream tap, the TAP_LOC shouldbe non-zero, in which case the differential pressure is converted topsia and added to the static pressure to obtain an upstream pressurefor internal use.



Relative Density Usage:

Relative density can only be used for liquids. The FLOW_DENSterminal must be unwired, or wired and zero, and the ISEN_COEFmust be unwired, or wired and less than or equal to zero. The value onthe REL_DENS terminal is multiplied by the density of water toobtain a flowing density for internal calculations. This terminal isintended for use where a densitometer signal is unavailable but arelative density (Specific Gravity) is available.

BLANK PAGE

ACCOL II Reference ManualPage AGA3Iter-1

AGA3IterAmerican Gas Association Report No. 3 - Iterative Module

The AGA3Iter Module computes natural gas volume flow rate inMSCF/h for orifice plates, with flange taps ONLY, according to thefactors method explained in the American Gas Association (AGA)Report #3 of August, 1992, 3rd Edition (Part 3, Equations 3-B-2 and 3-7). This method retains factors such as Fpb , Fpv , Ext, and othersdescribed in the American Gas Association (AGA) Report #3 of 1985,but provides greater accuracy by using a new equation to calculate thecoefficient of discharge.

PIPE_DIAM

TAP_LOC

POINT

ORIF_DIAM

OUTPUT

TRACK

3ITER

ADJ _PRESS

STAT_ PRESS

FLOW_TEMP

SPEC_GRAV

THERM_COEF1

BASE _TEMPBASE _PRESS

INPUT_1LIST

THERM_COEF2

VISCOSITY

ISEN_COEF

INPUT_2INPUT_3

Z_BASE

Z_FLOWING

DIFF_ PRESS

AGA3Iter


Page AGA3Iter-2


The paragraphs below outline the rules under which the AGA3Iterperforms its computations:

The output volume flow rate is computed in thousands of standardcubic feet per hour (MSCF/h), at base conditions, according to tech-niques described in the 1992 AGA Report #3, Part 3, Equations 3-B-2and 3-7.

The orifice coefficient and slope coefficient are calculated byiteration using the Reader-Harris equation shown in the 1992 AGAReport #3, Part 3. These two factors are combined into a coefficient ofdischarge, CD.

Internal factors used in the calculations can be stored in an ACCOLsignal list for examination. Input terminals to the AGA3Iter Moduleallow the user to substitute factors for CP and Ext, and to specify astandard compressibility, Z

s.

A standard cubic foot is one which exists at the standard pres-sure of 14.73 psia, and a temperature of 60 degrees Fahrenheit. Whencontract base conditions are not standard conditions, the moduleBASE_PRESS (base pressure) and BASE_TEMP (base temperature)terminals should be changed so that flow rate will be computed atbase conditions.

The base compressibility, Zb , is input to the module via the Z_BASEterminal. Zb must come from one of the AGA8 Modules (AGA8Gross,or AGA8Detail) and must have been computed at the same baseconditions specified by the BASE_PRESS and BASE_TEMP terminalsof the AGA3Iter Module.

❏ Module EquationThe equation given in the 1992 American Gas Association (AGA)Report #3, Part 3, Equation 3-B-2 is as follows:



Qv = Fn (Fc + Fsl) Y Fpb Ftb Ftf Fgr Fpv . hw Pf1

Equation 3-B-2 calculates flow rate at standard conditions (14.73 psiaand 600 F).

The AGA3Iter Module calculates flow rate at base conditions, asfollows:

Qb = CP Ext BCF F

m

where Qb

= Flow rate at base conditions

CP = Fn CD Y F

pb F

tb F

tf F

gr F

pv

Ext = hw P

f1

Fm

= additional correction factor on the POINT terminal.

BCF = Base correction (Zb/Zs) for Zb other than AGA report Zs value.

where

Fn = A numeric conversion factor whichincludes Ev the velocity of ap-proach factor.

CD = Orifice coefficient of discharge,which is the sum of the orificecalculation factor, Fc and theorifice slope factor Fsl.

Y = Expansion factor.


Page AGA3Iter-4


Fpb = Pressure base factor.

Ftb = Temperature base factor.

Ftf = Flowing temperature factor.

Fgr = Specific gravity factor.

Fpv = Supercompressibility factor,computed as Z

b / Z

f . The Z

band Zf values MUST come from anAGA8Detail or AGA8Gross calcu-lation.

hw = Differential pressure, in inches ofH

2O.

Pf1 = Absolute static pressure, in psia.

NOTE

This equation is for flange tapped orifice platesONLY. If pipe taps are being used, theAGA3TERM Module must be used.


DIFF_PRESS Default: None, entry requiredFormat: Analog signal or constantInput/Output: Input

is the differential pressure, hw , in inches of water across the orifice



plate. Negative input values are clamped at zero, and zero produces azero flow rate.

STAT_PRESS Default: None, entry requiredFormat: Analog signal or constantInput/Output: Input

is the Upstream or Downstream static pressure, specified in psig.Negative input values are clamped at zero, and zero produces a zeroflow rate. When it is a Downstream pressure, the TAP_LOC terminalshould be non-zero.

TAP_LOC Default: 0Format: Analog signalInput/Output: Input

indicates the pressure tap location for flange taps. A value of 0 on thisterminal indicates that the tap location is Upstream, and a non-zerovalue indicates that the tap location is Downstream.

When Downstream is specified, the differential pressure is convertedto psi and added to the Downstream static pressure to obtain anUpstream value for use in calculations. See 'Module Usage Notes.'

ADJ_PRESS Default: 14.73 psiaFormat: Analog signal or constantInput/Output: Input

is the site barometric pressure in psia. This value is added to thevalue on the STAT_PRESS terminal to obtain absolute pressure.


Page AGA3Iter-6


ORIF_DIAM Default: None, entry requiredFormat: Analog signal or constantInput/Output: Input

is the orifice bore diameter in inches at 68 degrees Fahrenheit. Outputof the module will be zero if this terminal is unwired, or if the valueentered is zero, negative, or larger than 80% of the value on thePIPE_DIAM terminal.

PIPE_DIAM Default: None, entry requiredFormat: Analog signal or constantInput/Output: Input

is the inside diameter of the pipe in inches at 68 degrees Fahrenheit.Output of the module will be zero if this terminal is unwired, or if thevalue on the terminal is zero or negative.

THERM_COEF1 Default: 0.00000925 (stainlesssteel)


is the orifice coefficient of thermal expansion in inches per inch-degreeFahrenheit.

THERM_COEF2 Default: 0.0000062 (carbon steel)Format: Analog signal or constantInput/Output: Input

is the pipe coefficient of thermal expansion in inches per inch-degreeFahrenheit.



BASE_PRESS Default: 14.73 psiaFormat: Analog signal or constantInput/Output: Input

is the base pressure Pb in psia. This value is used to calculate thefactor Fpb.

BASE_TEMP Default: 60o FahrenheitFormat: Analog signal or constantInput/Output: Input

is the base temperature, Tb , of the gas in degrees Fahrenheit. Thisvalue is used to calculate the factor Ftb .

FLOW_TEMP Default: 60o FahrenheitFormat: Analog signal or constantInput/Output: Input

is the temperature, Tf , in degrees Fahrenheit. This value is used tocalculate the factor Ftf .

VISCOSITY Default: 0.0000069 lbm/foot-secondFormat: Analog signal or constantInput/Output: Input

is the dynamic viscosity of the gas at flowing conditions in pound massper foot-second. Viscosity is used to calculate the Reynolds number.This terminal should normally be left unwired unless the gas viscosityis known to be outside the range of .0000059 to .0000079 given in the1992 American Gas Association (AGA-3) Report, Part 3, page 11.


Page AGA3Iter-8


SPEC_GRAV Default: 0.6Format: Analog signal or constantInput/Output: Input

is the specific gravity, Gr, of the gas at standard conditions. This valueis used to calculate the factor Fgr.


is the gas Isentropic exponent. This value is used in the calculation ofthe expansion factor, Y. This terminal should be left unwired unlessthe gas isentropic exponent is known to be other than the 1.3 valuegiven in the 1992 American Gas Association (AGA-3) Report.

Z_FLOWING Default: 1.0Format: Analog signal or constantInput/Output: Input

is the flowing compressibility factor, Zf , generated from an AGA8calculation referenced to the Upstream conditions.

NOTE

When TAP_LOC is non-zero, this module internal-ly adds the DIFF_PRESS (in psia) to theSTAT_PRESS value to calculate Upstream pres-sure for ALL calculations. Any AGA8Detail modulecalculating Zf MUST use an equivalent Upstreampressure.



Z_BASE Default: 1.0Format: Analog signal or constantInput/Output: Input

is the base compressibility factor, Zb , from an AGA8 calculation.

POINT Default: 1.0Format: Analog signal or constantInput/Output: Input

is used internally as the meter correction factor, Fm , to compensatefor external equipment calibration error or local variations in condi-tions such as gravity, or Downstream tap compressibility.

TRACK Default: 1.0 or ONFormat: Analog or logical signalInput/Output: Input

is used to force the module output to zero. When a logical signal iswired to this terminal, ON enables calculation, and OFF forces theoutput of the module to zero. If an analog signal is wired to thisterminal, it is used as a differential pressure threshold value or 'cutoff'level; calculations cease and the output of the module is forced to zerowhen the DIFF_PRESS terminal value is less than the TRACK value.

OUTPUT Default: NoneFormat: Analog signalInput/Output: Output

is the gas flow rate, Qb , at base conditions in MSCF per hour.


Page AGA3Iter-10



is the number of a signal list into which the factors used in the equa-tion are to be moved. Factors are moved to the list in the followingorder: CP, Fn , CD, E, Y, Fpb , Ftb , Ftf , Fgr , Fpv , Fm , Ext, Reyn, andBCF, where Reyn is the pipe Reynolds number computed by iterationas part of the CD calculation. The output list is not written to whenthe CP value factor comes from an input.

INPUT_1 Default: NoneFormat: Analog signal or constantInput/Output: Input

allows the substitution of an alternate value for CP in situationswhere the factor is required to be different and internal calculation ofthat factor is not desired. If this terminal is wired, and its signal valueis not less than zero, the value will be substituted for CP in the equa-tion, and the internal calculation of that factor will not be done. If theterminal is unwired, or has a negative value on it, the factor will becalculated internally.

INPUT_2 Default: NoneFormat: Analog signal or constantInput/Output: Input

allows the substitution of an alternate value for Ext in situationswhere the factor is required to be different and internal calculation ofthat factor is not desired. If this terminal is wired, and its signal valueis not less than zero, the value will be substituted for Ext in theequation, and the internal calculation of that factor will not be done. Ifthe terminal is unwired, or has a negative value on it, the factor willbe calculated internally.



INPUT_3 Default: 0.997971Format: Analog signal or constantInput/Output: Input

is the standard compressibility Zs for the gas composition in use. Zs isused in the calculation of the flow rate correction factor BCF (the ratioof Zb to Zs). A default value of 0.997971 is supplied which correspondsto the set of conditions defined in Appendix 3-C, Section 3-C.2 ofAmerican Gas Association (AGA) Report #3 of August, 1992, 3rdEdition. If this terminal is wired, and its signal value is not less thanzero, the value will be substituted for Zs in the equation, and theinternal default value of that factor will not be used. If the terminal isunwired, it is set to its default value of 0.997971. If the terminal has anegative value on it, the factor is set to 1.0. For most uses, this termi-nal will be wired with a Zs signal.

❏ Module Usage NotesConditions Which Cause Zero Flow Rate to be output by the Module:

The following conditions can force the flow rate output of theAGA3Iter Module to zero. These are:

a. Negative or zero differential pressure.b. Negative or zero static pressure.c. Negative or zero orifice diameter.d. Negative or zero pipe diameter.e. Orifice diameter larger than 80% of pipe diameter.f. Track terminal conditions are satisfied.

Bounded Inputs:

The isentropic exponent value used internally will be forced to 1.3 ifthe input value is less than 1.0 or larger than 2.0. The viscosity valueused internally will be forced to .0000069 if the input value is zero ornegative, or larger than 1.0.


Page AGA3Iter-12


Compressibility:

In cases where both the AGA8Detail and AGA3Iter Modules usestandard conditions (14.73 psia, 600 F) on the BASE_PRESS andBASE_TEMP terminals, only one AGA8Detail module is neededbecause Zb is the same as Zs, and the Zb signal will be wired to theZ_BASE and INPUT_3 terminals.

Where base conditions are other than standard, then an AGA8Detailmodule is used to obtain Z_FLOWING (Zf) and Z_BASE (Zb) signalvalues at base conditions. Another AGA8Detail module will be neededto compute a Zs at standard conditions. This Zs is to be wired toINPUT_3. This Zs comes from the AGA8Detail module Zb output, but itis the same as Zs because the BASE_PRESS and BASE_TEMP termi-nals are set at 14.73 and 600 F.

Static Pressure Tap Location:

If the static pressure is from a downstream tap, the TAP_LOC shouldbe non-zero, in which case the DIFF_PRESS is converted to psia andadded to the STAT_PRESS to obtain an upstream pressure. Usersmust ensure that the static pressure used for the AGA8Detail andAGA8Gross module is the sum of the downstream pressure and thedifferential pressure (in psia) or the Z factors will be incorrect.


Page AGA3Term-1

AGA3TERMAmerican Gas Association Report No. 3 - Terms Module

The AGA3TERM Module1 is identical to the AGA3 module in that itperforms the gas flow calculations for Orifice meters specified by theAmerican Gas Association, Report No.3 (AGA-3) ANSI/API 2530,1985 edition and produces an output flow rate in thousands of cubicfeet per hour (MSCFH). This module differs from the AGA3 module asfollows.

1. The actual AGA-3 factors used in internal calculations can bemoved to a list for verification or comparison.

2. Input terminals allow you to substitute factors as needed.

3. The POINT terminal (construction code) can be changed on-linewithout disturbing module execution.

Module TerminalsDIFF_PRESS(hw)

is the differential pressure across an orifice in inches/water at 60o F.


PIPE_DIAMORIF_CONST

POINTORIF_DIAM

OUTPUT

TRACK

T3

INPUT_nLIST

ADJ _PRESSDIFF_ PRESSSTAT_ PRESSFLOW_TEMPSPEC_GRAVFPVBASE _TEMPBASE _PRESS

1. This module was previously referred to by the names 'AGA3T,' or 'AGAT3.'

AGA3TERM


Page AGA3Term-2


STAT_PRESS(Pf)

is the static pressure of the flowing gas in psig.

ADJ_PRESS

is the average barometric pressure in psia.

ORIF_DIAM

is the orifice diameter in inches. This value can be changed online. Allaffected parameters will be automatically re-calculated.

PIPE_DIAM

is the inside diameter of the pipe in inches. This value can be changedonline. All affected parameters will be automatically re-calculated.

ORIF_CONST(K = Fa Fm Fl)

is a Combined Orifice Constant K. This terminal is typically the Fa


Default: 14.73 psiaFormat: Analog signal, constantInput/Output: Input

Default: None; entry is mandatoryFormat: Analog signal, constantInput\Output: Input

Default: None; entry is mandatoryFormat: Analog signal, constantInput/Output: Input

Default: 1.0Format: Analog signalInput/Output Input


Page AGA3Term-3


value for Orifice Thermal Expansion unless other corrections arerequired.

BASE_PRESS(Pb)

is the base or contract pressure of the gas in psia.

BASE_TEMP(T

b)

is the required (contract) base temperature of the flowing gas indegrees Fahrenheit.

FLOW_TEMP(Tf)

is the flowing temperature of the gas in degrees F.

FPV_IN(Fpv)

is the supercomcompressibility factor of the gas.

POINT

is the pressure tap construction code. This entry applies to the pipetap and flange tap construction described in Basic Orifice Factor

Default: 14.73 psiaFormat: Analog signal, constantInput/Output: Input

Default: 600FFormat: Analog signal, constantInput/Output: Input

Default: 600FFormat: Analog signal, constantInput/Output: Input

Default: 1Format: Analog signal, constantInput/Output: Input



Page AGA3Term-4


under the 'AGA3' section of this manual.

Unlike the AGA3 Module, the POINT terminal in the AGA3TERMModule can be changed while the unit is on-line without first manuallyinhibiting module execution. The module will recalculate any affectedinternal values.

SPEC_GRAV(G)

is the specific gravity of the flowing gas.

TRACK

is used to force the gas flow output to zero under certain measurementconditions.

The TRACK signal may be an analog or logical variable. If it is ananalog value, it will be compared to the value of the differentialpressure (DIFF_PRESS). As long as the differential pressure exceedsthe TRACK value, the computed flow rate will be furnished to theOUTPUT terminal. Should the differential pressure fall below theTRACK value, the OUTPUT will be set to zero. In this way, theTRACK signal acts as a cutoff limit.

If the TRACK signal is a logical variable, the ON state will allow theflow rate output to be furnished to the OUTPUT terminal. If theTRACK signal is in an OFF state, the module output will be set tozero percent of scale.

Default: 0.6Format: Analog signal, constantInput/Output: Input

Default: None, entry is optionalFormat: Analog or logical signalInput/Output: Input


Page AGA3Term-5


OUTPUT (Qh)

is the corrected gas flow rate at base conditions in MSCFH. NOTE: Infirmware prior to AK.00, the OUTPUT would be set to 0.0 when thenumeric ratio of DIFF_PRESS (h

w) to STAT_PRESS (P

f) exceeded 4 to

1, e.g. DIFF_PRESS = 101 inches and STAT_PRESS = 25 psig. Thiswas done because the h

w/P

f ratio in tables 6, 7, 10, and 11 of the 1978

AGA3 report did not contain ratios higher than 4.0. In firmwarerevision AK.00 (and newer) the OUTPUT is set to 0.0 if the ratio of h

wto Pf exceeds 20 to 1.

LIST

is the number of a signal list which contains the factors used in theAGA-3 equation. Factors are moved to the list in the following order:

C', Fb, Fr, Y, Fpb, Ftb, Ftf, Fg, Fpv, K, Ext.

INPUT_n

contain factors of the AGA-3 equation which will be substituted for thecalculated ones.

When INPUT is positive (including zero), it will be substituted in theequation and the internal factor will not be used. Negative INPUTsare ignored and the internal factor is used. If the C' factor is wiredand is zero or positive, no internal factors are calculated at all. If any

Default: NoneFormat: Analog signal

(in thousands of standard cubicfeet per hour)

Input/Output: Output

Default: NoneFormat: Analog signalInput/Output: Input

Default: NoneFormat: Analog signalInput/Output: Input


Page AGA3Term-6


INPUT is incorrectly wired with a logical signal, the value used will be1.0 for signal ON, 0.0 for signal OFF. There is no Fpv or Fa inputbecause these terminals are already provided.

The output list specified on the LIST terminal will always contain thefactor used in calculations whether it comes from an input terminal oris calculated by the module. When the C' factor is supplied externally,the list will contain zero values for all other factors except the Exten-sion.

INPUT_1 C' - Orifice Flow Constant in CFHINPUT_2 F

b- Basic Orifice Factor

INPUT_3 Fr - Reynolds Number FactorINPUT_4 Y - Expansion FactorINPUT_5 Fpb - Pressure Base FactorINPUT_6 F

tb- Temperature Base Factor

INPUT_7 Ftf - Flowing Temperature FactorINPUT_8 F

g- Specific Gravity Factor.

INPUT_9 Ext - Square-root of the product of Differential Pressureand Static Pressure.

EquationsFlow calculations done by the AGA3TERM Module are explainedunder the 'AGA3' section.



Page AGA5-1

The AGA5 Module performs AGA-5 calculations for conversion ofcomputed gas volume to energy equivalents as described in the Ameri-can Gas Association Report No. 5, reference Catalog No. XQ0776.

Module Terminals

VOLUME

represents the metered volume of gas in MSCF or flow rate in MSCFH

BASE_PRESS

is the base pressure of the flowing gas

BASE_TEMPSPEC_GRAV

VOL_%_HEVOL_%_CO

FPV_IN

VOL_CONVERS

ENERGY_CONV

OUTPUT

VOLUMEBASE_PRESS

5

VOL_%_N2VOL_%_O2

VOL_%_CO2

VOL_%_H2OVOL_%_H2S

VOL_%_H2

Default: None, entry is required. Nocomputation will be performed ifthis terminal is not wired.



AGA5


Page AGA5-2



Page AGA5-2






BASE_TEMP

is the base temperature of the flowing gas

FPV_IN

is the supercompressibility factor of the gas. This factor is used inequations when the input volume is an uncorrected metered volume.

Originally, the AGA-5 Report included the FPV factor in its calcula-tions. However, since that time, the report has been found in error. Itis therefore recommended that this terminal not be wired in whichcase the default value of 1.0 is assumed.

SPEC_GRAV


VOL_%

The VOL_% terminals contain the following:

VOL_%_CO2 - the volume % of CO2 present in the gas.VOL_%_N2 - the volume % of N2 present in the gas.VOL_%_O2 - the volume % of O2 present in the gas.VOL_%_HE - the volume % of He present in the gas.VOL_%_CO - the volume % of CO present in the gas.





BASE_TEMP

is the base temperature of the flowing gas

FPV_IN

is the supercompressibility factor of the gas. This factor is used inequations when the input volume is an uncorrected metered volume.

Originally, the AGA-5 Report included the FPV factor in its calcula-tions. However, since that time, the report has been found in error. Itis therefore recommended that this terminal not be wired in whichcase the default value of 1.0 is assumed.

SPEC_GRAV


VOL_%

The VOL_% terminals contain the following:

VOL_%_CO2 - the volume % of CO2 present in the gas.VOL_%_N2 - the volume % of N2 present in the gas.VOL_%_O2 - the volume % of O2 present in the gas.VOL_%_HE - the volume % of He present in the gas.VOL_%_CO - the volume % of CO present in the gas.



Page AGA5-3

VOL_%_H2S - the volume % of H2S present in the gas.VOL_%_H2O - the volume % of H20 present in the gas.VOL_%_H2 - the volume % of H2 present in the gas.

VOL_CONVERS

is a volume conversion factor, that is, a metered volume of cubic feetat 14.73 psi, 600F. If the value on the VOLUME terminal is expressedin terms of MSCF or MSCFH, you may use the default which is1000.0. If VOLUME is expressed in terms of SCFH or SCF, set thisterminal to 1.

ENERGY_CONV

is an energy conversion factor when dekatherms are the desiredenergy units.

OUTPUT

is the desired units of gas energy, normally in dekatherms or dekath-erms/hour. It is the flow rate calculated by the module.

Default: .000001 dekatherm (1 deka-therm = 1,000,000 BTUs)





Page AGA5-4



Page AGA5-4


Module Equations

The equation implemented by this module is taken from Section II ofAGA Report No. 5. This particular equation dovetails the require-ments of the orifice metering approach and the volume meteringapproach. As such, several of the factors are not required for theorifice metered volume to energy conversions. This module is onlyused when a calorimeter signal is not available. It performs thefollowing equation for gas volume-to-energy conversion:

Ue = Uv * Ev * Fuv * Fue

where:

Ue = Desired units of Gas energy, totalized or rate per unit of time.

Uv = Standard volume units, totalized or rate per unit time, i.e.SCFH. Note that Uv is normally calculated by AGA-3 or AGA-7modules in MSCFH.

Ev = Energy-volume ratio, Btu per cubic foot, 14.73 psi, 600F.

Fuv = Volume conversion factor, metered volume to cubic feet at14.73 psi, 600F. Note: Where Standard units are metered inMSCFH, Fuv = 1.

Fue = Energy conversion factor, Btu per cubic foot to desired energyunits. Note: Where dekatherm energy units are required, thisfactor equals one. (One dekatherm = 1 million BTUs)

If a calorimeter signal is available, do not use this module. Instead,use a Calculator Module to solve the following equation:

Ue = Uv Ev (.000001)

The parameters of this formula are defined above. If Uv is expressedin units of MSCFH, change the multiplier in the equation to .001.

Module Equations

The equation implemented by this module is taken from Section II ofAGA Report No. 5. This particular equation dovetails the require-ments of the orifice metering approach and the volume meteringapproach. As such, several of the factors are not required for theorifice metered volume to energy conversions. This module is onlyused when a calorimeter signal is not available. It performs thefollowing equation for gas volume-to-energy conversion:

Ue = Uv * Ev * Fuv * Fue

where:

Ue = Desired units of Gas energy, totalized or rate per unit of time.

Uv = Standard volume units, totalized or rate per unit time, i.e.SCFH. Note that Uv is normally calculated by AGA-3 or AGA-7modules in MSCFH.

Ev = Energy-volume ratio, Btu per cubic foot, 14.73 psi, 600F.

Fuv = Volume conversion factor, metered volume to cubic feet at14.73 psi, 600F. Note: Where Standard units are metered inMSCFH, Fuv = 1.

Fue = Energy conversion factor, Btu per cubic foot to desired energyunits. Note: Where dekatherm energy units are required, thisfactor equals one. (One dekatherm = 1 million BTUs)

If a calorimeter signal is available, do not use this module. Instead,use a Calculator Module to solve the following equation:

Ue = Uv Ev (.000001)

The parameters of this formula are defined above. If Uv is expressedin units of MSCFH, change the multiplier in the equation to .001.



Page AGA5-5

For undiluted hydrocarbon gas mixtures,

Ev = Vg

where:

Vg = (1571.5 * specific gravity) + 144

For gas mixtures containing non-hydrocarbon compounds,

EV = Vg - (Vcd + Vn + Vo + Vhe + Vcm + Vhs + Vw - Vhy)

where:

Vcd = (Volume % CO2) * 25.318V

n= (Volume % N

2) * 16.639

Vo = (Volume % O2) * 18.801Vhe = (Volume % He) * 3.612Vcm = (Volume % CO) * 13.424Vhs = (Volume % H2S) * 13.462Vw = (Volume % H2O) * 11.214Vhy = (Volume % H2) * 0.713

If the input volume is a metered volume, then Standard Volume Unitsare calculated from the metered volume as follows:

Uv = Fp * Ft * Fpv2 * metered volume

where:

Fp = Pressure Factor = PSIA * .067889Ft = Temperature Factor = (519.67 / (459.67 + 0F))Fpv = Supercompressibility Factor

Metered Volume = Volume displaced in units peculiar tometer, at prevailing pressure and temperature conditions.


Page AGA5-6



Page AGA5-6


Since the energy conversion factors only apply to volume units under apressure of 14.73 psi and 600F, the above conversion also provides asecondary volume conversion when the input volume is an orificemetered volume expressed at base conditions other than 14.73 psi and600F. In this case,

519.67Uv = Q * (Pb * 0.067889) *

459.67 + Tb

where:

Q = volume of gas at any other base conditions.Pb = Any other pressure base, psia.T

b= Any other temperature base, 0F.

AGA7American Gas Association Report No.. 7 Module

Page AGA7-1


The AGA7 Module calculates the base volume rate (Qb) as described inthe American Gas Association Report No. 7, reference catalog No.XQ0508. This module computes the base volume rate by implementingthe equations from Section 6, Volumetric Flow Measurement, as wellas the equations from Section 7, Mass Flow Measurement. The spe-cific computation method used is selected by the use of module termi-nals.

Flow rate of the gas is obtained from a HSCOUNT (High SpeedCounter) or LSCOUNT (Low Speed Counter) Module which is typi-cally measured by a turbine flowmeter, positive displacement meter,or vortex shedding meter.

❏ Module TerminalsFLOW_SWITCH Default: OFF (Equation A determines base

volume flow rate)Format: Logical signalInput/Output: Input

if this terminal is OFF, the output flow rate will be in Volume units(Equation A); if this terminal is ON, the output flow rate will be inMass units (Equation B). Equations A and B are described later,under 'Module Equations'.

FLOW_TEMPFLOW_PRESS

FLOW_SWITCHDENS_SWITCH

RATEBASE_TEMPBASE_PRESSFPV_INADJ_PRESSFLOW_DENSBASE_DENSSPEC_GRAVGRAV_TEMP

CALIB_FACTRSPAN

OUTPUT7

GRAV_PRESS

AGA7


Page AGA7-2



Page AGA7-2


DENS_SWITCH Default: OFF (Equation C determines basedensity)

Format: Logical signalInput/Output: Input

if this terminal is wired, and OFF, it specifies that a densitometer issupplying both Flowing Density (Df) and Base Density (Db). The Df andDb values are specified by the values on the FLOW_DENS andBASE_DENS terminals.

If this terminal is ON, it specifies that a Gravitometer is used, andthat the value of D

b will be calculated using Equation C, and the

values on the SPEC_GRAV, GRAV_TEMP, and GRAV_PRESS termi-nals. The calculated value of D

b will then be used in Equation B, along

with the FLOW_DENS value.

FLOW_TEMP (Tf) Default: 600F


represents the temperature of the flowing gas in degrees F.

FLOW_PRESS (Pf) Default: None, entry required whenFLOW_SWITCH is OFF


is the static gauge pressure of the flowing gas measured in psig. IfEquation A is selected via the FLOW_SWITCH and this terminal isnot wired, the OUTPUT will not be updated.

DENS_SWITCH Default: OFF (Equation C determines basedensity)


if this terminal is wired, and OFF, it specifies that a densitometer issupplying both Flowing Density (Df) and Base Density (Db). The Df andDb values are specified by the values on the FLOW_DENS andBASE_DENS terminals.

If this terminal is ON, it specifies that a Gravitometer is used, andthat the value of D

b will be calculated using Equation C, and the

values on the SPEC_GRAV, GRAV_TEMP, and GRAV_PRESS termi-nals. The calculated value of D

b will then be used in Equation B, along

with the FLOW_DENS value.

FLOW_TEMP (Tf) Default: 600F


represents the temperature of the flowing gas in degrees F.

FLOW_PRESS (Pf) Default: None, entry required whenFLOW_SWITCH is OFF


is the static gauge pressure of the flowing gas measured in psig. IfEquation A is selected via the FLOW_SWITCH and this terminal isnot wired, the OUTPUT will not be updated.


Page AGA7-3


RATE (Qf) Default: None, entry required or elseOUTPUT is not updated.


is the uncorrected gas flow (either rate or volume in cu.ft./hr.) asmeasured via the HSCOUNT Module (High Speed Counter) orLSCOUNT Module (Low Speed Counter).

BASE_TEMP (Tb) Default: 600FFormat: Analog signal or constantInput/Output: Input

is the contract base temperature in degrees F.

BASE_PRESS (Pb) Default: 14.73


is the contract base pressure (psia).

FPV_IN (Fpv) Default: 1.0Format: Analog signal or constantInput/Output: Input

is an output signal from the FPV Module.

ADJ_PRESS (Pa) Default: 14.73Format: Analog signal or constantInput/Output: Input

is the atmospheric pressure (that is, the barometric pressure) at thesite and is added to the gauge pressure to produce absolute pressure.


Page AGA7-4



Page AGA7-4


FLOW_DENS (Df) Default: 0.045923 lb/cu.ft. (based on aspecific gravity of 0.6, a tempera-ture of 600F, a pressure of 14.7 psi,and a supercompressibility factorof 1.0.)


is the density of the flowing gas as measured by a densitometer.

BASE_DENS (Db) Default: 0.045923 lb/cu.ft. (based on a

specific gravity of 0.6, 600F tem-perature, 14.7 psi pressure, and asupercompressibility factor of 1.0.)


is the contract base density as measured via a densitometer.

SPEC_GRAV (SG) Default: 0.6Format: Analog signal or constantInput/Output: Input

is the specific gravity of the gas as measured by a gravitometer.

GRAV_TEMP (Tg) Default: 600 FFormat: Analog signal or constantInput/Output: Input

is the temperature at the gravitometer in degrees F.

FLOW_DENS (Df) Default: 0.045923 lb/cu.ft. (based on aspecific gravity of 0.6, a tempera-ture of 600F, a pressure of 14.7 psi,and a supercompressibility factorof 1.0.)


is the density of the flowing gas as measured by a densitometer.

BASE_DENS (Db) Default: 0.045923 lb/cu.ft. (based on a

specific gravity of 0.6, 600F tem-perature, 14.7 psi pressure, and asupercompressibility factor of 1.0.)


is the contract base density as measured via a densitometer.

SPEC_GRAV (SG) Default: 0.6Format: Analog signal or constantInput/Output: Input

is the specific gravity of the gas as measured by a gravitometer.

GRAV_TEMP (Tg) Default: 600 FFormat: Analog signal or constantInput/Output: Input

is the temperature at the gravitometer in degrees F.


Page AGA7-5


GRAV_PRESS (Pg) Default: 14.73Format: Analog signal or constantInput/Output: Input

is the absolute pressure (psia) at the gravitometer.

CALIB_FACTR (C) Default: 1.0Format: Analog signal or constantInput/Output: Input

is an optional calibration factor. This factor is used to correct knownvariations in the measuring equipment.

SPAN (K) Default: 1.0Format: Analog signal or constantInput/Output: Input

is a scale factor to adjust the OUTPUT to the desired units.

OUTPUT (Qb) Default: NoneFormat: Analog signalInput/Output: Output

is the calculated flow rate at base conditions. The units are in MSCFH(thousands of standard cubic feet per hour) unless modified by theSPAN terminal.


Page AGA7-6



Page AGA7-6


❏ Module Equations

The following equation, for base volume rate, is taken from Section 6,Volumetric Flow Measurement:

Qf Pf + Pa 519.67Qb = C * K * * * *

1000 Pb Tf + 459.67

(Tb + 459.67)* Fpv

2 Equation A 519.67

where:

Qb = Calculated flow rate at base conditions (output in MSCFH)C = Calibration factorK = Span scaling factorQf = Flow rate at flowing conditions (cubic feet per hour)Pf = Static gauge pressure psigPa = Atmospheric pressure psiaPb = Base pressure in psiaTf = Flowing temperature in degrees FTb = Base temperature in degrees FFpv = Supercompressibility factor

The following equation, for base volume rate, is taken from Section 7,Mass Flow Measurement:

Qf DfQb = C * K * * Equation B

1000 Db

where all operands are the same as the previous equation except for:

Df = Density of flowing gas as measured by a densitometer

Db = Base density as measured by a densitometer or calculated by Equation C.

❏ Module Equations

The following equation, for base volume rate, is taken from Section 6,Volumetric Flow Measurement:

Qf Pf + Pa 519.67Qb = C * K * * * *

1000 Pb Tf + 459.67

(Tb + 459.67)* Fpv

2 Equation A 519.67

where:

Qb = Calculated flow rate at base conditions (output in MSCFH)C = Calibration factorK = Span scaling factorQf = Flow rate at flowing conditions (cubic feet per hour)Pf = Static gauge pressure psigPa = Atmospheric pressure psiaPb = Base pressure in psiaTf = Flowing temperature in degrees FTb = Base temperature in degrees FFpv = Supercompressibility factor

The following equation, for base volume rate, is taken from Section 7,Mass Flow Measurement:

Qf DfQb = C * K * * Equation B

1000 Db

where all operands are the same as the previous equation except for:

Df = Density of flowing gas as measured by a densitometer

Db = Base density as measured by a densitometer or calculated by Equation C.


Page AGA7-7


Gravitometer temperature and pressure are used to determine thebase density (Db) in the following computation (Equation C):

Pg 492Db = 0.08073 * * * SG * Fpv

2 Equation C14.7 Tg + 459.67

where:

Pg = Absolute pressure (psia) at gravitometerTg = Temperature (in degrees F) at gravitometerSG = Specific gravity as measured by gravitometerFpv = Supercompressibility factor at Pg and Tg

BLANK PAGE



Page AGA8-1

The AGA8 Module uses gas component mole percent information tocompute the base compressibility (Zb), flowing compressibility(Z), and supercompressibility (Fpv= Zb/Z ) for natural gas mix-tures according to the method explained in American Gas AssociationReport Number 8 (AGA-8) of Dec 15, 1985.* Up to 20 gas componentscan be processed by the module, and these can come from a signal listor a data array. For best results, the gas component informationshould come from a chromatograph.

This module does not perform the gas component estimation explainedin the AGA-8 Report. Such estimated gas component information inaccordance with the report can be generated by the ACCOL Charac-terize Module described later in this manual, under 'Characterize'.Alternately, component information can come from a signal list ordata array containing the component percentages. The components inthe list or array must be in the fixed order defined under ComponentOrder and Percent Requirements in this section. If the CharacterizeModule generates the list or array, the components will automaticallybe in the proper order.

If the ENABLE signal is ON, the module checks the entries on itsterminals. Incorrect conditions will be indicated via the ERRORterminal signal and computations will not occur. If all conditions arecorrect, then calculations are initiated.

On subsequent executions of the AGA8 Module, the STATUS terminal

BASE_TEMPBASE_PRESSENABLEPRIORITY

8FLOW_TEMP

ARRAYCOLUMN

LIST

STAT_PRESS

Z_FLOWINGZ_BASEFPV

ERROR

STATUS

* Users requiring the calculation method described in the Nov., 92 (2nd edition) of the AGA8 report should see 'AGA8Detail' or 'AGA8Gross', later in this manual.

AGA8


Page AGA8-2


is updated to indicate the progress of the calculations. The AGA8Module’s output terminals (Z_FLOWING, Z_BASE, and FPV) areupdated only when calculations have been completed.

The AGA8 Module should be used only where the ACCOL FPV Module(NX-19) will not suffice (see 'FPV', later in this manual). This isbecause the AGA8 calculations require signficant amounts of memoryand computation resources, and could result in other ACCOL tasks'slipping' from their normal execution rate (see PRIORITY terminalbelow).


ENABLE Default: None, entry requiredFormat: Logical signalInput/Output: Input

allows calculations to proceed if ON, and no calculations are alreadyin progress. This signal will be set OFF, automatically, when calcula-tions begin.

PRIORITY Default: ACCOL task priority 1; (This cor-responds to system task priority55.)


is the priority at which the system task which performs the AGA8calculations will run. (System tasks are discussed in the section'Task', later in this manual.) Values lower than 1 or larger than 64 onthis terminal will produce an error. Priority will affect system perfor-mance if it is so high that other tasks cannot run. The priority shouldbe kept as low as possible.



Page AGA8-3

FLOW_TEMP Default: None, entry requiredFormat: Analog signalInput/Output: Input

is the flowing gas temperature in degrees Fahrenheit.

STAT_PRESS Default: None, entry requiredFormat: Analog signalInput/Output: Input

is the gas static pressure in psia. If this terminal has a negative value,computations will not be performed.

BASE_TEMP Default: 600FFormat: Analog signalInput/Output: Input

is the gas base temperature in degrees Fahrenheit.

BASE_PRESS Default: 14.73 psiaFormat: Analog signalInput/Output: Input

is the gas base pressure in psia. If the terminal has a negative valueno computations are performed.

LIST Default: None, entry required ifARRAY terminal is not wired


is the number of a list containing the gas component information. Thegas components MUST be placed in the order specified in Component


Page AGA8-4


Order and Percent Requirements, later in this section. If both theLIST and ARRAY terminals are wired, only the LIST terminal will beused.

ARRAY Default: None, entry required if LISTterminal is not wired


is the number of an analog array containing the gas componentinformation. The gas components must be placed in the order specifiedin Component Order and Percent Requirements, later in this section.

One dimensional arrays must be 1 column by N rows, where N can be1 to 20. For cases where the array contains components from multiplegas streams, more columns can be added.

If both the LIST and ARRAY terminals are wired, only the LISTterminal will be used.

COLUMN Default: None, entry required if LISTterminal is unwired.


is the array column containing up to 20 gas components to be used inthe calculation. This signal can be used to perform successive AGA8calculations on multiple gas streams by indexing through the arraycolumns. Invalid column values produce an error and no computationis performed.



Page AGA8-5

ERROR Default: NoneFormat: Analog signalInput/Output: Output

contains one of the following codes. Errors are detected by the moduleprior to the start of calculations.

Code Message

0 No errors -1 Missing ENABLE signal -3 Missing input terminals: FLOW_TEMP or STATIC_PRESS

or both ARRAY and LIST missing -4 Signal in list is not an analog signal -5 Not a valid list -6 Not a valid array -7 Not a valid array column -8 Missing FPV output terminal -9 Invalid PRIORITY (less than 1 or larger than 64)-10 Negative pressure values detected for STATIC_PRESS or

BASE_PRESS

STATUS Default: NoneFormat: Analog signalInput/Output: Output

contains the following status codes:

Code Message

-3 Floating point error detected-2 All input components are zero


Page AGA8-6


Code Message (continued):

-1 No memory available0 Not running, check error terminal for errors

1 Combining components 2 Mixing terms at flowing conditions 3 Calculating density at flowing conditions

4 Mixing at base conditions 5 Calculating density at base conditions

10-19 Calculation complete - final root (includes iteration count)20-23 Calculation complete - approximate root (includes approxi-

mation code)

Z_FLOWING Default: None, entry is optionalFormat: Analog signalInput/Output: Output

is the compressibility at flowing conditions. This terminal will only beupdated if the AGA8 Module is executing, and the value on the STA-TUS terminal is at least 10, i.e., calculations are complete.

Z_BASE Default: None, entry is optionalFormat: Analog signalInput/Output: Output

is the compressibility at base conditions. This terminal will only beupdated if the AGA8 Module is executing, and the value on the STA-TUS terminal is at least 10, i.e., calculations are complete.

FPV Default: None, entry requiredFormat: Analog signalInput/Output: Output

is the supercompressibility ratio Zb/Z. This terminal will only beupdated if the AGA8 Module is executing, and the value on the STA-TUS terminal is at least 10, i.e., calculations are complete.



Page AGA8-7

o Component Order and Percent Requirements

Gas components in lists or array columns must be in the followingorder. The number of components can vary from 1 to 20, but the orderis important and must be followed. The Characterize Module willproduce 15 components in the proper order. You may supply up to 20components. If the list or array is too short (i.e., not enough compo-nents,) the remaining components are assumed to have a value of 0.

Component Name Component Name

1 Nitrogen 11 n-Pentane2 Carbon Dioxide 12 i-Pentane3 Hydrogen Sulphide 13 n-Hexane4 Water 14 n-Heptane5 Helium 15 n-Octane6 Methane 16 n-Nonane7 Ethane 17 n-Decane8 Propane 18 Oxygen9 n-Butane 19 Carbon Monoxide10 i-Butane 20 Hydrogen

The AGA-8 Report specifies the following mole percent ranges forresults within the stated uncertainty limits:

Methane 50 to 100%Nitrogen 0 to 50%Carbon Dioxide 0 to 50%Ethane 0 to 20%Propane 0 to 5%Butanes 0 to 3%Pentanes 0 to 2%Hexanes 0 to 1% (also heavier hydrocarbons)All others 0 to 1%

In addition, the report also indicates what percentage uncertaintiescan be expected for gases with compositions in the above specified


Page AGA8-8


ranges over various pressure and temperature regions.

Region 1:-60 F to 180 F from 0 to 1500 psia 0.1%

Region 2:-60 F to 180 F from 1500 to 2500 psia 0.3%-80 F to -60 F from 0 to 2500 psia 0.3%180 F to 240 F from 0 to 2500 psia 0.3%

Region 3:-80 F to 240 F from 2500 to 10000 psia 0.5%240 F to 400 F from 0 to 10000 psia 0.5%-200 F to -80 F from 0 to 10000 psia 0.5%

Region 4:-200 F to 400 F from 10000 to 20000 psia 1.0%

❏ Using the Module

Place the AGA8 Module in an ACCOL task which has a task priorityof 32 or less. A task rate of 1 second is recommended for efficientmonitoring of the calculations and update of the STATUS and outputsignals. The value on the PRIORITY terminal of the module shouldalso be as low as possible.

When the AGA8 Module executes, if the ENABLE signal is ON and noprevious calculation is active, the input terminals are automaticallychecked for errors. If none are detected, calculations are initiated andthe ENABLE signal is set to OFF.

Setting the ENABLE signal to ON should be controlled by logic in theACCOL program to limit calculation activity to a reasonable levelbased on potential changes of the input information. For example, if achromatograph is used to provide the gas component information, theAGA8 Module ENABLE should be turned on when new componentinformation is available from the chromatograph. A Timer Module



Page AGA8-9

might also be used to enable execution of the AGA8 calculations atsome frequency, e.g. once per minute. It is recommended that theENABLE signal not be set to ON while a previous calculation isactive, i.e. before the STATUS terminal value indicates completion. Inthis case, a new calculation cycle will be started as soon as the currentcycle completes and the output signals are updated, therefore theSTATUS terminal completion status value will not be visible becauseit will immediately change to one of the active status values.

When the AGA8 Module executes, the STATUS terminal is updated. Ifcalculations are active, the STATUS value will show the progress ofthe calculations (values 1 through 5). All of these intermediate valuesmay not be seen, depending on the ACCOL task rate and other activi-ties in the system. In general, STATUS code 5 will not be seen unlessthe methane component is less than 80% or if the base pressureexceeds 16.0 psia because the Z

b value requires a longer computation

in those circumstances.

When calculations are complete, the value of the STATUS terminalsignal is updated, and the output signals Z_FLOWING, Z_BASE, andFPV are updated with the results.

The STATUS value indicates if a final root (STATUS values 10-19) orapproximate root (STATUS values 20-23) was obtained.

If the STATUS value is 10-19, subtract 9 to obtain the iteration count;i.e. the number of passes required to determine the root.

If the STATUS value is 20-23, subtract 10 to get the approximationcode. The approximation codes are:

10 Minimum density used11 Maximum density used12 Root not found; last iteration used13 No bisection convergence; last iteration used

BLANK PAGE

AGA8DetailAmerican Gas Association Report No. 8 Detail Calculation Module


Page AGA8Detail-1

The AGA8Detail Module uses gas component mole percent informa-tion to compute the base compressibility (Zb), flowing compress-ibility (Z), and supercompressibility (Fpv= Zb/Z ) for natural gasmixtures according to the Detail Characterization method explained inAmerican Gas Association Report Number 8 (AGA-8), 2nd edition ofNovember, 1992. Up to 21 gas components can be processed by themodule. For best results, the gas component information should comefrom a chromatograph.

8DETAILZ_FLOWINGZ_BASEFPV

ERROR

STATUS

BASE_TEMPBASE_PRESS

ENABLEPRIORITY

FLOW_TEMPSTAT_PRESS

ARRAYCOLUMN

LIST

The components in the signal list or data array must be in the fixedorder defined under Component Order in this section.


On subsequent executions of the AGA8Detail Module, the STATUSterminal is updated to indicate the progress of the calculations. TheAGA8Detail Module’s output terminals (Z_FLOWING, Z_BASE, andFPV) are updated only when calculations have been completed.

AGA8Detail


Page AGA8Detail-2


AGA8Detail calculations require significant amounts of memory andcomputation resources, and could result in other ACCOL tasks 'slip-ping' from their normal execution rate (see PRIORITY terminalbelow).



allows calculations to proceed if ON, and no calculations are alreadyin progress. This signal will be set OFF, automatically, when calcula-tions begin.



is the priority at which the system task which performs theAGA8Detail calculations will run. (System tasks are discussed in thesection 'Task', later in this manual.) Values lower than 1 or largerthan 64 on this terminal will produce an error. Priority will affectsystem performance if it is so high that other tasks cannot run. Thepriority should be kept as low as possible.





Page AGA8Detail-3


is the static pressure in psia. If this terminal has a negative value,computations will not be performed.

BASE_TEMP Default: 600 FFormat: Analog signalInput/Output: Input

is the gas base temperature in degrees Fahrenheit.


is the gas base pressure in psia. If the terminal has a negative valueno computations are performed.

LIST Default: None, entry required if ARRAYterminal is not wired


is the number of a list containing the gas component information. Thegas components MUST be placed in the order specified in the Compo-nent Order portion of this section. If both the LIST and ARRAYterminals are wired, only the LIST terminal will be used.


Page AGA8Detail-4


ARRAY Default: None, entry required if LISTterminal is not wired


is the number of an analog array containing the gas componentinformation. The gas components must be placed in the order specifiedin the Component Order portion of this section.

One dimensional arrays must be 1 column by N rows, where N can be1 to 21. For cases where the array contains components from multiplegas streams, more columns can be added.

If both the LIST and ARRAY terminals are wired, the ARRAY termi-nal is ignored.

COLUMN Default: None, entry required if LISTterminal is unwired


is the array column containing up to 21 gas components to be used inthe calculation. This signal can be used to perform successiveAGA8Detail calculations on multiple gas streams by indexing throughthe array columns. Invalid column values produce an error and nocomputation is performed.


displays one of the following codes. Errors are detected by the moduleprior to the start of calculations.



Page AGA8Detail-5

Code Message

0 No errors -1 Missing ENABLE signal -3 Missing input terminals: FLOW_TEMP or STAT_PRESS or

both ARRAY and LIST missing. -4 Signal in list is not an analog signal -5 Not a valid list -6 Not a valid array -7 Not a valid array column -8 Missing FPV output terminal -9 Invalid PRIORITY (less than 1 or larger than 64) -10 Negative pressure detected for STAT_PRESS or

BASE_PRESS


contains one of the following status codes:

Code Message

10 Calculation complete4 Calculating compressibility at flow conditions3 Calculating density at flow conditions2 Calculating gas characterization1 Calculating compressibility at base conditions0 Not running, check error terminal for errors

-1 No memory available-2 No positive inputs in the component list or array-3 Floating point error detected

-11 No convergence-12 Root not bounded-13 Negative square root-14 Pressure has a negative density derivative-15 Maximum number of iterations exceeded


Page AGA8Detail-6



is the compressibility at flowing conditions. This terminal will only beupdated if the AGA8Detail Module is executing, and if the value onthe STATUS terminal is 10; i.e. calculations are complete.


is the compressibility at base conditions. This terminal will only beupdated if the AGA8Detail Module is executing, and if the value onthe STATUS terminal is 10; i.e. calculations are complete.


is the supercompressibility ratio ( Zb/Z ). This terminal will only beupdated if the AGA8Detail Module is executing, and if the value onthe STATUS terminal is 10; i.e. calculations are complete.

❏ Component Order

Gas components in lists or array columns must be in the followingorder. The number of components can vary from 1 to 21, but the orderis important and must be followed. If the list or array is short; i.e., lessthan 21 components, the remaining undefined components will begiven a default value of 0.



Page AGA8Detail-7

Component Name Component Name

1 Methane 11 i-Butane2 Nitrogen 12 n-Butane3 Carbon Dioxide 13 i-Pentane4 Ethane 14 n-Pentane5 Propane 15 n-Hexane6 Water 16 n-Heptane7 Hydrogen Sulfide 17 n-Octane8 Hydrogen 18 n-Nonane9 Carbon Monoxide 19 n-Decane10 Oxygen 20 Helium

21 Argon

❏ Using the ModulePlace the AGA8Detail Module in an ACCOL task which has a taskpriority of 32 or less. A task rate of 1 second is recommended forefficient monitoring of the calculations and update of the STATUS andoutput signals. The value on the PRIORITY terminal of the moduleshould also be as low as possible.

When the AGA8Detail Module executes, if the ENABLE signal is ONand no previous calculation is active, the input terminals are auto-matically checked for errors. If none are detected, calculations areinitiated and the ENABLE signal is set to OFF.

Setting the ENABLE signal to ON should be controlled by logic in theACCOL program to limit calculation activity to a reasonable levelbased on potential changes of the input information. For example, if achromatograph is used to provide the gas component information, theAGA8Detail Module ENABLE should be turned on when new compo-nent information is available from the chromatograph. A TimerModule might also be used to enable execution of the AGA8Detail


Page AGA8Detail-8


calculations at some frequency, e.g. once per minute. It is recom-mended that the ENABLE signal not be set to ON while a previouscalculation is active, i.e. before the STATUS terminal value indicatescompletion. In this case, a new calculation cycle will be started as soonas the current cycle completes and the output signals are updated,therefore the STATUS terminal completion status value will not bevisible because it will immediately change to one of the active statusvalues.

When the AGA8Detail Module executes, the STATUS terminal isupdated. If calculations are active, the STATUS value will show theprogress of the calculations (values 1 through 4). All of these interme-diate values may not be seen, depending on the ACCOL task rate andother activities in the system.

When calculations are complete as indicated by the STATUS value,the output signals Z_FLOWING, Z_BASE, and FPV are updated withthe results.


Page AGA8Gross-1

AGA8GrossAmerican Gas Association Report No. 8 Gross Calculation Module

The AGA8Gross Module uses heating value, relative density, andnitrogen and carbon dioxide mole percent information to compute thebase compressibility (Zb), flowing compressibility (Z), andsupercompressibility (Fpv= Zb/Z ) for natural gas mixtures accord-ing to the Gross Characterization method explained in American GasAssociation Report Number 8 (AGA-8), 2nd edition, of November,1992.

BASE_TEMPBASE_PRESS

ENABLEPRIORITY

8GROSS

FLOW_TEMPMODE

STAT_PRESS

Z_FLOWINGZ_BASEFPV

ERROR

STATUS

REF_P_HVREL_DENS

HEAT_VALUEREF_T_HV

MOLE_%_N2MOLE_%_CO2

REF_T_RDREF_P_RD

MOLE_%_H2MOLE_%_CO


On subsequent executions of the AGA8Gross Module, the STATUSterminal is updated to indicate the progress of the calculations. TheAGA8Gross Module’s output terminals (Z_FLOWING, Z_BASE, andFPV) are updated only when calculations have been completed.

AGA8Gross


Page AGA8Gross-2


AGA8Gross calculations require significant amounts of memory andcomputation resources, and could result in other ACCOL tasks 'slip-ping' from their normal execution rate (see PRIORITY terminalbelow).



allows calculations to proceed if ON and no calculations are already inprogress. This signal will be set OFF automatically when calculationsbegin.



is the priority at which the system task which performs theAGA8Gross calculations will run. (System tasks are discussed in thesection 'Task', later in this manual.) Values lower than 1 or largerthan 64 will produce an error. Priority will affect system performanceif it is so high that other tasks cannot run. The priority should be keptas low as possible.

MODE Default: 1Format: Analog signalInput/Output: Input

selects one of two Gross calculation methods. If 1 is entered on this


Page AGA8Gross-3


terminal, the module calculates using the inputs of volumetric grossheating value, relative density, and the mole fraction of carbon diox-ide. If 2 is entered on the MODE terminal, the module calculatesusing inputs of relative density, and the mole fractions of nitrogen andcarbon dioxide. If the MODE terminal value is anything other than 2,it will default to mode 1.




is the gas static pressure in psia. If this terminal has a negative value,computations will not be performed.

BASE_TEMP Default: 600 FFormat: Analog signalInput/Output: Input

is the base temperature in degrees Fahrenheit.


is the base pressure in psia. If the terminal has a negative value nocomputations are performed.


Page AGA8Gross-4


HEAT_VALUE Default: None, entry required (MODE 1only)


is the volumetric gross heating value in BTU/FT3.

REF_T_HV Default: 600 F (MODE 1 only)Format: Analog signalInput/Output: Input

is the reference temperature of the volumetric heating value in de-grees Fahrenheit.

REF_P_HV Default: 14.73 psia (MODE 1 only)Format: Analog signalInput/Output: Input

is the reference pressure of the volumetric heating value in psia.

REL_DENS Default: None, entry requiredFormat: Analog signalInput/Output: Input

is the relative density of gas (specific gravity).

REF_T_RD Default: 600 F (MODE 1 only)Format: Analog signalInput/Output: Input

is the reference temperature of the relative density in degrees Fahren-heit.


Page AGA8Gross-5


REF_P_RD Default: 14.73 psiaFormat: Analog signalInput/Output: Input

is the reference pressure of the relative density in psia.

MOLE_%_N2 Default: 0 (MODE 2 only)Format: Analog signalInput/Output: Input

is the nitrogen mole fraction composition. This terminal is optional.

MOLE_%_CO2 Default: 0Format: Analog signalInput/Output: Input

is the carbon dioxide mole fraction composition. This terminal isoptional.

MOLE_%_H2 Default: 0Format: Analog signalInput/Output: Input

is the hydrogen mole fraction composition. This terminal is optional.

MOLE_%_CO Default: 0Format: Analog signalInput/Output: Input

is the carbon monoxide mole fraction composition. This terminal isoptional.


Page AGA8Gross-6



displays one of the following codes. Errors are detected by the moduleprior to the start of calculations.

Code Message

0 No errors -1 Missing ENABLE signal -3 Missing input terminals -8 Missing FPV output terminal -9 Invalid PRIORITY (less than 1 or larger than 64)-10 Negative pressure values detected for STAT_PRESS or

BASE_PRESS


contains one of the following status codes:

Code Message

10 Calculation complete 4 Calculating compressibility at flow conditions 3 Calculating density at flow conditions 2 Calculating gas characterization 1 Calculating compressibility at base conditions 0 Not running, check error terminal for errors -1 No memory available -3 Floating point error detected-11 No convergence-12 Root not bounded-13 Negative square root


Page AGA8Gross-7



is the compressibility at flowing conditions. This terminal will only beupdated if the AGA8Gross Module is executing, and if the value on theSTATUS terminal is 10; i.e. calculations are complete.


is the compressibility at base conditions. This terminal will only beupdated if the AGA8Gross Module is executing, and if the value on theSTATUS terminal is 10; i.e. calculations are complete.


is the supercompressibility ratio ( Zb/Z ). This terminal will only beupdated if the AGA8Gross Module is executing, and if the value on theSTATUS terminal is 10; i.e. calculations are complete.


Page AGA8Gross-8


CAUTION

The AGA8Gross Module, as implemented in the AH.00PROM set, has a small discrepancy between the module'sZ_FLOWING output value, and the tables (B.6-3 and B.6-4) in the 1992 American Gas Association (AGA-8) Report.

Users with this PROM set revision level should upgradetheir PROMs to version AH.01 (or later revision) whichcorrects this known discrepancy.

❏ Using the ModulePlace the AGA8Gross Module in an ACCOL task which has a taskpriority of 32 or less. A task rate of 1 second is recommended forefficient monitoring of the calculations and update of the STATUS andoutput signals. The value on the PRIORITY terminal of the moduleshould also be as low as possible.

When the AGA8Gross Module executes, if the ENABLE signal is ONand no previous calculation is active, the input terminals are auto-matically checked for errors. If none are detected, calculations areinitiated and the ENABLE signal is set to OFF.

Setting the ENABLE signal to ON should be controlled by logic in theACCOL program to limit calculation activity to a reasonable levelbased on potential changes of the input information. For example, if achromatograph is used to provide the gas component information, theAGA8Gross Module ENABLE should be turned on when new compo-nent information is available from the chromatograph. A TimerModule might also be used to enable execution of the AGA8Grosscalculations at some frequency, e.g. once per minute. It is recom-mended that the ENABLE signal not be set to ON while a previous


Page AGA8Gross-9


calculation is active, i.e. before the STATUS terminal value indicatescompletion. In this case, a new calculation cycle will be started as soonas the current cycle completes and the output signals are updated,therefore the STATUS terminal completion status value will not bevisible because it will immediately change to one of the active statusvalues.

When the AGA8Gross Module executes, the STATUS terminal isupdated. If calculations are active, the STATUS value will show theprogress of the calculations (values 1 through 4). All of these interme-diate values may not be seen, depending on the ACCOL task rate andother activities in the system.

When calculations are complete as indicated by the STATUS value,the output signals Z_FLOWING, Z_BASE, and FPV are updated withthe results.

BLANK PAGE


ANINRANIN

Analog Input and Remote Analog Input Modules

Page ANIN-1

The Analog Input Modules take electrical inputs from the AI fieldterminals and convert them to ACCOL software signals which may beused by other modules within the ACCOL load.

There are two types of analog input modules: ANIN and RANIN.ANIN (ANalog INput) Modules receive analog input data from processI/O boards which reside within that controller. RANIN (RemoteANalog INput) Modules also receive analog input data from process I/O boards, but only from those boards which reside in an RIO 3331Remote I/O Rack.

Electrical Input

SPAN

ZERO

INPUT

DEVICE

INITIAL

Electrical Input

SPAN

ZERO

INPUT

DEVICE

INITIAL STATUS

R

RANINModuleSymbol

ANINModuleSymbol

See also: Questionable Data Process I/O

ANIN/RANIN


Page ANIN-2

ANINRANINAnalog Input and Remote Analog Input Modules

Three terminals are provided for each field input. The INPUT termi-nal names an ACCOL analog signal and the ZERO and SPAN termi-nals scale it to the proper engineering units. Each set of terminals fora given input is numbered to allow for proper identification.

❏ Module TerminalsDEVICE (ANIN) Default: 0 (null device) When the module

executes with this default, a deviceerror will be reported and nosignal processing will occur.

Format: ConstantInput/Output: Input

is the slot number in the card cage where the Process I/O Boards areinstalled. The board installed in this slot accepts analog input signalsfrom the field. The entry at this terminal must be a number from 1 to12 depending on your unit and the number of boards installed. To findout the number of boards which may be installed in a particularcontroller type, see the 'Process I/O' section.

The board number entered in the DEVICE field will be verified withthe Process I/O Menu (if you’re using the AIC) or the *PROCESS-I/Osection (if you’re using the ABC or ACCOL Workbench). This boardmust be capable of accepting analog input signals. If no board is foundin the specified slot or if the board is the wrong type, an error messagewill be generated.


ANINRANIN


Page ANIN-3

DEVICE (RANIN) Default: 0 (null device) When the module isexecuted with this default, adevice error will be reported andno signal processing will occur.


is a three digit number which identifies the RIO 3331 process I/Oboard which is being referenced by this module. There can be up to tenRIO 3331 nodes connected to each communication port of a 3310/3330/3335 controller, and each RIO 3331 can hold up to ten process I/O boards - therefore up to 100 boards can be referenced through agiven communications port.

The total number of RIO 3331 nodes (from all communications portscombined) connected to any 3310/3330/3335 controller must not exceedten (10). In addition, although you are allowed to have up to 100 RIOprocess I/O boards among the RIO 3331 units, as well as the boards inthe 3310/3330/3335 unit, that total number of boards may not besupported by your particular system configuration. Task rates, pollperiods, as well as the number and types of boards, and number of I/Opoints on them, all affect system performance. Users are urged to testtheir desired system configuration to verify that it provides adequateperformance.

Valid DEVICE values range from 100 through 499. Use the followingrules to generate a number for the DEVICE terminal.

The first digit indicates the serial port on the 3310/3330/3335 control-ler which is accepting data from the RIO 3331 node.

Port First DigitA 1B 2C 3D 4


Page ANIN-4


The second digit must be one less than the RIO 3331 node addresswhere the board resides. It must range from 0 through 9. (Seconddigit = 0 for node address 1. Second digit = 9 for node address 10.)

The third digit must be one less than the board slot. It must rangefrom 0 through 9 (Third digit = 0 for slot 1. Third digit = 9 for slot10.)

Examples:

Process I/O board 200 is the first board of the first RIO 3331 nodewhich communicates to port B of the 3310/3330/3335 controller.

Process I/O board 317 is the eighth board of the second RIO 3331node which communicates to port C of the 3310/3330/3335 con-troller.

The number entered on the DEVICE terminal will be verified with theProcess I/O Menu (if you’re using the AIC) or the *PROCESS-I/Osection (if you’re using the ABC or ACCOL Workbench). This boardmust be capable of accepting analog input signals. If no board is foundin the specified slot or if the board is the wrong type, an error messagewill be generated.

INITIAL Default: 1Format: ConstantInput/Output: Input

is the number of the field wiring terminal that will be assigned to thefirst set of module terminals. All subsequent terminals entered on thismenu will be sequenced from the initial number. For example, if 2were the INITIAL entry, then terminal set #1 would correspond tofield terminal AI2 of the device and terminal set #2 would correspondto field terminal AI3.


ANINRANIN


Page ANIN-5

STATUS (RANIN) Default: None, entry optionalFormat: Analog signalInput/Output: Output

assumes one of the module execution codes listed below.

Code Meaning 0 Module executed successfully-1 Invalid remote device ID-2 Communication failed with remote unit-3 Remote board is missing-4 Remote board is of the wrong type-5 The remote board failed diagnostic tests-6 AI data not ready-7 RIO Rack firmware incompatible with process I/O

configured in load. (C.01 or newer firmware should beinstalled in the RIO 3331.)

INPUT Default: None, entry requiredFormat: Analog signalInput/Output: Output

is the output of the module. Its value is proportional to the electricalinput on the AI field wiring terminal.

When SPAN and ZERO values are specified, the units of INPUT areconverted to engineering units. If SPAN and ZERO are not specified,the INPUT value ranges from 0 to 1. In this case, 0.0 represents 0 %of the input range, 1.0 represents 100 % of the input range.


Page ANIN-6


ZERO Default: 0.0Format: Analog signal or constantInput/Output: Input

is equivalent to the 0% value of the input range. For example, if theoutput covers a range from -5 to 5 units, the entry for ZERO is -5.

SPAN Default: 1.0Format: Analog signal or constantInput/Output: Input

is the total span of the input range. If the output covers a range from -5 to 5 units, SPAN will be 10 units.

❏ Questionable DataFor information on questionable data for analog input signals, see thesection 'Questionable Data' later in this manual.

ANOUTRANOUT

Analog Output and Remote Analog Output Modules


Page ANOUT-1

The Analog Output Modules convert ACCOL analog signals to electri-cal outputs that are applied to the field wiring terminals of the processcontroller.

There are two types of analog output modules: ANOUT and RANOUT.ANOUT (ANalog OUTput) Modules send analog output data to pro-cess I/O boards which reside within that controller.

RANOUT (Remote ANalog OUTput) Modules also send analog outputdata to process I/O boards, but only to those boards which reside in anRIO 3331 Remote I/O Rack. The RANOUT Modules may only be used

ANOUT ModuleSymbol

OUTPUTto Process

TRACK

RESET

I/O Boards

SPAN

ZERO

DEVICE

INITIAL

OUTPUTto Process

TRACK

RESET

I/O Boards

SPAN

ZERO

DEVICE

INITIAL

R

STATUS

RANOUT ModuleSymbol

ANOUT/RANOUT


Page ANOUT-2

ANOUTRANOUTAnalog Output and Remote Analog Output Modules

in ACCOL loads which run in 3310/3330/3335 controllers because onlythose controllers are equipped to communicate directly with an RIO3331.

Five terminals are provided for each analog output signal: ZERO,SPAN, TRACK, RESET, and OUTPUT. Each set of terminals for agiven analog output is numbered to allow for proper identification.

The OUTPUT terminal names an ACCOL analog signal and the ZEROand SPAN terminals will scale it to the proper engineering units.TRACK indicates whether the AO has gone out of range, and RESETtracks the output.

❏ Module TerminalsDEVICE (ANOUT) Default: 0.0; If the module executes with

the default, a device error isreported and no signal processingoccurs.


is the slot number in the card cage where the Process I/O Boards areinstalled. The board installed in the slot specified here generatesanalog output signals. The entry at this terminal must be a numberfrom 1 to 12 depending on your unit model and the number of boardsinstalled. To find out the number of boards which may be installed ina particular controller type, see the 'Process I/O' section.

The board referenced in this field will be verified with the Process I/OMenu (if you’re using the AIC) or the *PROCESS-I/O section (if you’reusing the ABC or ACCOL Workbench). This board must be capable ofsending analog output signals. If no board is found in the specified slotor if the board is the wrong type, an error message will be generated.

ANOUTRANOUT



Page ANOUT-3

DEVICE (RANOUT) Default: 0.0; If the module executes withthe default, a device error is re-ported and no signal processingoccurs


is a three digit number which identifies the RIO 3331 process I/Oboard which is being referenced by this module. There can be up to tenRIO 3331 nodes connected to each communication port of a 3310/3330/3335 controller, and each RIO 3331 can hold up to ten process I/Oboards - therefore up to 100 boards can be referenced through a givencommunications port.


Valid DEVICE values may range from 100 through 499. Use thefollowing rules to generate a number for the DEVICE terminal.

The first digit indicates the serial port on the 3310/3330/3335 control-ler which is communicating with the RIO 3331 node:



Page ANOUT-4


The second digit must be one less than the RIO 3331 node addresswhere the board resides. It must range from 0 through 9. (Seconddigit = 0 for node address 1. Second digit = 9 for node address 10.)

The third digit must be one less than the board slot. It must rangefrom 0 through 9. (Third digit = 0 for slot 1. Third digit = 9 for slot10.)

Examples:

Process I/O board 200 is the first board of the first RIO 3331 nodewhich communicates with port B of the 3310/3330/3335 controller.

Process I/O board 317 is the eighth board of the second RIO 3331node which communicates with port C of the 3310/3330/3335controller.

The number entered on the DEVICE terminal will be verified withthe Process I/O Menu (if you’re using the AIC) or the *PROCESS-I/Osection (if you’re using the ABC or ACCOL Workbench). This boardmust be capable of generating analog output signals. If no board isfound in the specified slot or if the board is the wrong type, an errormessage will be generated.

INITIAL Default: 1.0Format: ConstantInput/Output: Input

is the number of the field wiring terminal that will be assigned to thefirst OUTPUT terminal of the module. Terminal assignments for otherOUTPUT signals will be automatically sequenced from this initialnumber. For example, if number 3 was entered, then terminal set #1would connect to field terminal AO3 of the device and terminal set #2would connect to field terminal AO4.

ANOUTRANOUT



Page ANOUT-5

STATUS (RANOUT) Default: None, entry optionalFormat: Analog signalInput/Output: Output

will assume one of the module execution codes listed below:

Code Meaning 0 Module executed successfully-1 Invalid remote device ID-2 Communication failed with remote unit-3 Remote board is missing-4 Remote board is of the wrong type-5 The remote board failed diagnostic tests-7 RIO Rack firmware incompatible with process I/O configured

in load. (C.01 or newer firmware should be installed in theRIO 3331.)

OUTPUT Default: None, entry requiredFormat: Analog signal or constantInput/Output: Input

is an ACCOL analog signal or constant whose value is converted to anelectrical output at the corresponding field wiring terminal.

If the signal value is below 0% (or above 100%) of the normal operat-ing range as defined by the ZERO and SPAN terminals, the valueapplied to the field wiring terminal output will be set to 0% (or 100%)and the TRACK signal will be turned ON.

If the unit is equipped with an AO Manual Panel and the AO fieldterminal is being manually controlled by that panel, the OUTPUTsignal from the module will have no effect on the field terminal. Note:Only the RDC 3350, UCS 3380, and CFE 3385 controllers supportmanual panels.


Page ANOUT-6


ZERO Default: 0.0Format: Analog signal or constantInput/Output: Input

is equivalent to the 0% value of the output range. For example, if theoutput range is 5 to 105 units, the entry for ZERO would be 5.

SPAN Default: 1.0Format: Analog signal or constantInput/Output: Input

is equivalent to the total span of the output range. If the range is 5 to105 units, the span would be 105 - 5 = 100 units.

TRACK Default: NoneFormat: Logical signalInput/Output: Output

The signal named on this terminal is turned ON by the module when-ever the value of the OUTPUT terminal is out of range, that is, below0% or above 100% as defined by the ZERO and SPAN terminals. It isturned OFF when OUTPUT is within the normal operating range.

If an AO Manual Panel is used, the TRACK signal will be ON when-ever the field terminal is being manually controlled at that panel.Note: Only the RDC 3350, UCS 3380, and CFE 3385 controllerssupport manual panels.

RESET Default: NoneFormat: Analog signalInput/Output: Output

tracks the output of the module or, if the field terminal is in ManualMode, it tracks the actual value at the field terminal.

ANOUTRANOUT



Page ANOUT-7

In AUTO mode, if TRACK is ON, the module output is limited to 0%(when OUTPUT is underrange) or 100% (when OUTPUT is over-range).

Both TRACK and RESET terminals are commonly wired to theTRACK and RESET terminals of the PID3TERM Module, when usedin a control loop application to prevent reset windup of a processduring start-up, or when transfers are made between manual and autocontrol.

BLANK PAGE

ACCOL II Reference ManualPage ARC_STORE-1

ARC_STOREArchive Storage Module

The ARC_STORE module allows signal values to be stored in histori-cal archive files. The archive data may be retrieved via UOI com-mands, or via the Open BSI Data Collector or DataView utilities.Depending upon the type of controller you are using, the ARC_STOREmodule can also perform various calculations on the data, and storethe results of those calculations in the archive file.

ARC_STORE

ARCHIVE

PARAMETER_n(n=1 to 8)

MODE STATUS

Archive files reside within the 33xx controller, and are identified by aunique archive file name (1 to 8 alpha-numeric characters) and anarchive file ID number from 1 to 65,535.

Historical archive files are similar to data arrays, except that eachcolumn is directly associated with a particular ACCOL signal, andeach column has a descriptive title. The first column of each rowcontains a time stamp, and the remaining columns in a given row arethe signal values (or results of calculations based on signal values)collected at the time specified by the time stamp. The data occupyinga particular row is referred to as a record; a record index is kept,which points to the row containing the current record.

Two other pieces of information are always associated with eachrecord: A Local Sequence Number and a Global Sequence Num-ber. These numbers can range from 0 to 65,535 and are used inter-nally by the module to show the relative order in which records havebeen stored - - i.e. the higher the Sequence Number the more recentthe data. (This assumes the two sequence numbers being comparedare in the same cycle of sequence numbers, i.e. a lower numberedrecord could potentially be newer than a higher numbered record ifthe lower numbered record was stored after the sequence numberrange has wrapped around).

ARC_STORE


Page ARC_STORE-2


The Local Sequence Number shows the relative order in which recordshave been stored within this archive file.

The Global Sequence Number is similar, except it is shared among allArchive Files, and other structures as well, such as the EAudit Mod-ule. It therefore represents the relative ordering among all ArchiveFiles and Audit Trail buffer entries.

The valid range of sequence numbers is 0 to 65,535, however, thesubset of this range in use at any one time will vary depending uponhow many records are being stored in an Archive File. For example, ifonly 72 records are being stored in an Archive File, the Local Se-quence Numbers of those records would be from 0 to 71 at one mo-ment in time; at some other moment in time, that data would havebeen overwritten, and the Sequence Numbers for the file might befrom 101 to 172 or 60,001 to 60,072. Eventually, the Sequence Num-bers will wrap around and be re-used.

Importance of Sequence Numbers in RTU 3305 and in Pro-tected Mode DPC 3330, DPC 3335, RTU 3310:

From a user's point of view, sequence numbers are mainly of use if youare using an RTU 3305 or a 386EX Protected Mode controller. Inthese units, when a particular record is stored in the Archive File, itssequence numbers can be retrieved by executing the ARC_STOREModule in Mode 2. Once these sequence numbers are known, theymay be used in Mode 3 to access the actual data for the record andretrieve it for storage in a signal list. (See MODE terminal).

❏ Archive File DefinitionsThe Archive File(s) must be defined in the ACCOL source (*.ACC) file,using ACCOL Workbench. The structure of the Archive definitionvaries, somewhat, depending upon which type of controller is beingused.



RTU 3305 & 386EX Protected Mode - Archive Files

The data in archive files for 386EX Protected Mode controllers, or theRTU 3305, consists of 'snapshots' of selected signal values, at a giventimestamp. The 'snapshots' are triggered by executing theARC_STORE Module in either modes 0, 1, or 4. No calculations areperformed on the data by the ARC_STORE Module.

3530-series - Archive Files

The rows in 3530-series Archive Files consist of one or more calculateddata values based on 'snapshots' of selected signals over a specifiedinterval of time. The temporary calculations are updated with a newset of 'snapshots' each time the ARC_STORE Module executes. Whenan executing ARC_STORE Module determines that a user-specifiedtime interval has elapsed, the temporary calculations are finalized andarchived, and the ARC_STORE Module advances to the next row. Thechoice of calculations performed over the time interval is specified inthe ACCOL source file, and includes:


Page ARC_STORE-4


� instantaneous value (no calculation, just 'snapshot')� minimum value� maximum value over a given time interval� accumulated value� straight average (using specified weight factor)� average (using specified weight factor)� square root average (using specified weight factor)� square of the square root average (using specified weight factor)� integration (using specified weight factor)



NOTE

For a full description of Archive File definition syntax, and an expla-nation of of how the aformentioned calculations are performed, see theACCOL Workbench User Manual (document# D4051).

❏ Module TerminalsARCHIVE Default: None

Format: Analog Signal or ConstantInput/Output: Input

specifies the archive file ID number. The archive file ID number mustbe an integer from 1 to 65535, and uniquely identifies a particulararchive file.

The archive file must have been previously defined in the ACCOLsource file, using ACCOL Workbench. See the ACCOL WorkbenchUser Manual (document# D4051) for details on defining the archivefile.

MODE Default: 0Format: Analog or Logical SignalInput/Output: Input

determines the mode of operation of the ARC_STORE module, when itexecutes. Normally, an analog signal should be used for MODE; if alogical signal is used, OFF will specify Mode 0, and ON will specifyMode 1.


Page ARC_STORE-6


Modes 0 through 5 (386EX Protected Mode/3305 ONLY)*

Mode: Description:

0 Store Data in Next Available Row. When theARC_STORE module is executed in this mode, it willstore, in the archive file, the current values of speci-fied signals. The actual signals will NOT be altered.(The choice of which signals to be stored is made inthe Archive File Definition section. See the ACCOLWorkbench User Manual (document# D4051) fordetails.) NOTE: Once all archive file rows have beenfilled, the module will overwrite old data, startingagain from row 1.

1 Store Data in Next Available Row, Re-initializeSignals Which Provided the Data. When theARC_STORE module is executed in this mode, it willstore, in the archive file, the current values of speci-fied signals, and then re-initialize those signals totheir default initial values. This mode could be usefulfor re-setting hourly total signals to 0, for example, sothey can re-accumulate data for the next hour.NOTE: Once all archive file rows have been filled, themodule will overwrite old data, starting again fromrow 1.

2 Retrieve Archive Sequence Numbers. When theARC_STORE module is executed in this mode, it willretrieve three different sequence numbers and storethe sequence number values on PARAMETER_nterminal signals. The Archive Sequence Numbers maythen be used (via Mode 3) to read archive data out ofthe archive file.

*Modes 2 through 5 are NOT available in ACCOLWorkbench (PM) 6.1 or earlier, or in PLS01/PLX01 orearlier firmware.



Sequence numbers are retrieved as follows:

The Local Sequence Number for the oldest record inthe archive file is stored in the PARAMETER_1signal.

The Local Sequence Number for the current record inthe archive file is stored in the PARAMETER_2signal.

The current value of the Global Sequence Number isstored in the PARAMETER_3 signal. This value mayor may not relate to a record in the Archive file, sincethe Global Sequence Number is shared with otherACCOL structures such as the Audit/EAudit buffers.

3 Retrieve Archive Data and Store in a SignalList. When the ARC_STORE module is executed inthis mode, archive data will be retrieved, usingArchive Sequence numbers, and stored for useraccess in the signal list designated by the PARAM-ETER_2 signal.

This list must be defined as follows:

Signal 1 - Time stamp signal (Julian)*Signal 2 - Local Sequence NumberSignal 3 - Global Sequence NumberSignal 4 - Column 1 signalSignal 5 - Column 2 signal

.

.Signal n - Column n signal

where n equals number of columns in archive file.

*The seconds portion of the Julian time stamp presentedhere is only accurate to the nearest 4 seconds. If you needa more accurate representation of the seconds value, usethe PARAMETER_8 signal in Mode 3.


Page ARC_STORE-8


The Local Sequence Number of the record to beretrieved must be specified on the PARAMETER_1signal. (The Local Sequence Number used in Mode 3must be obtained by executing the ARC_STOREModule in Mode 2, prior to entering Mode 3.) Inaddition, if wired, Julian time stamp data (year,month, day, hour, minute, and second) for the recordwill be reported in the PARAMETER_3 throughPARAMETER_8 terminals, respectively. NOTE:Depending upon the size of the Archive File, and thenumber of Archive Records which have been addedbetween the time a particular record is stored and thetime you attempt to retrieve it, the record you requestmay NOT be available, because the file has 'wrappedaround' and overwritten the desired data. If thisoccurs, a (-8 or -10) error will be reported on theSTATUS signal when you attempt to retrieve thedata.

4 Store Data in Current Archive Row withoutAdvancing to the Next Row. When theARC_STORE module is executed in this mode, it willtemporarily store the current values of specifiedsignals in the current record row of the archive file,but it will not fully archive the values or assignsequence numbers until Mode 5 is executed. Just asin Mode 0, in Mode 4, the signals for which data isstored are NOT re-initialized.

In Mode 4, the module DOES NOT ADVANCE TOTHE NEXT ARCHIVE ROW, therefore subsequentexecutions of the module will overwrite the recordoccupying the current row, thereby erasing thetemporary values.

If a signal containing a Julian time stamp value iswired to the PARAMETER_1 terminal, its value willbe used for the time stamp during each execution in



Mode 4. If PARAMETER_1 is NOT wired, then thetime stamp used will be the current value of the#TIME.000. system signal.

Mode 4 is useful in situations where the user wantsto include ACCOL logic to check the data before it isarchived. These temporary values will NOT beaccessible to other programs (i.e. DataView, DataCollector, UOI, or even to signal lists via Mode 2 and3) until the ARC_STORE Module has been executedin Mode 5, thereby 'sealing' the record and advancingthe record index to the next row.

Another possible use for Mode 4 is to hold temporarydata during a power failure. Important data, forexample, could be stored and frequently updatedusing Mode 4. Assuming the unit has a workingbackup battery, this important temporary data canbe retained, via Mode 4, and then when power isrestored, the ARC_STORE Module can be executed inMode 5 to archive the data.

5 Archive temporary data (from Mode 4) andadvance to the next available Archive Row.When the ARC_STORE module is executed in thismode, the current temporary storage of values in thecurrent row (performed via Mode 4) is archived,thereby 'sealing' the record and advancing the recordindex to the next row. Sequence numbers are as-signed as the archiving occurs. NOTE: Once allarchive file rows have been filled, the module willoverwrite old data, starting again from row 1.


Page ARC_STORE-10


Modes 10 through 13 (3530-series TeleFlow / TeleRTU ONLY)*

10 Automatic Logging: Periodically update data orintermediate calculations, then at a user speci-fied interval, archive data and advance to nextavailable Archive Row. In this mode, each time theARC_STORE Module executes, it will temporarilystore data or intermediate calculations. The type ofcalculations performed may include totals, runningaverages, etc. and are based on entries in the ACCOLsource file for weight factors, characteristics, etc. Ifthe ARC_STORE Module detects, during this execu-tion, that the user-specified interval (hour, minute,etc.) has elapsed, the intermediate calculations forthis interval will be finalized and archived, and themodule will advance to the next available ArchiveRow, and continue logging. This is the default modefor TeleFlow users, and need never be changed formost applications. If archiving is desired at sometime other than the specified interval, Mode 11 or 12must be activated, and then the module must bereturned to Mode 10 to continue logging. NOTE: Onceall archive file rows have been filled, the module willoverwrite old data, starting again from row 1.

11 Archive Current Row (including most recentpiece of intermediate data) and Advance to theNext Row. In this mode, the data or intermediatecalculations (collected via Mode 10) are finalized andarchived (including the final piece of intermediatedata) and the ARC_STORE Module will advance tothe next row. This archiving occurs as soon as themodule is executed in Mode 11; not according to thespecified interval. To continue with additional datacollection/archiving, the user must return the moduleto Mode 10.

*Modes 10 through 13 are NOT available prior to ACCOLWorkbench (RM) Version 1.1, and TFA01/TRA01 firm-ware.



The time stamp on the row depends upon the user'sselection of timestamp methods in the Archive Filedefinition: If the timestamp at start method is se-lected, the saved timestamp is assigned to the row,and the current time is used for the next row, and thefirst row will have the timestamp of system initializa-tion. If the storage time method is selected, the rowwill be assigned the timestamp from when the rowwas archived. NOTE: Once all archive file rows havebeen filled, the module will overwrite old data,starting again from row 1.

12 Archive Current Row (leaving out most recentpiece of intermediate data) and Advance to theNext Row. In this mode, the intermediate data orcalculations (collected via Mode 10) are completedand archived (however the final (most recent) piece ofintermediate data is excluded from the calculationsfor this row). The ARC_STORE Module will thenadvance to the next row, using the final piece ofintermediate data as the first piece of data for thenext row. This archiving occurs as soon as the moduleis executed in Mode 12; not according to the specifiedinterval. To continue with additional data collection/archiving, the user must return the module to Mode10.

The time stamp on the row depends upon the user'sselection of timestamp methods in the Archive Filedefinition: If the timestamp at start method is se-lected, the saved timestamp is assigned to the row,and the current time is used for the next row, and thefirst row will have the timestamp of system initializa-tion. If the storage time method is selected, the rowwill be assigned the timestamp from when the rowwas archived. NOTE: Once all archive file rows havebeen filled, the module will overwrite old data,starting again from row 1.


Page ARC_STORE-12


13 Disable ARC_STORE Module. In this mode, allARC_STORE Module operations are stopped, until avalid mode is selected. Mode 13 should only be used ifall intermediate data has already been archived viamode 10, 11, or 12.

STATUS Default: NoneFormat: Analog SignalInput/Output: Output

reports the status of module execution. Valid status codes are:

0 Successful execution-1 Invalid file number. Must be integer from 1 to

65535.-2 Missing entry on ARCHIVE terminal.-3 Invalid mode value. Must be integer from 0 to 5

or 10 to 13.-4 Archive not active. The required archive struc-

tures have not been defined in the ACCOL file.-5 File not found.-6 Valid list for output not specified.When module

is executed in Mode 3, the PARAMETER_2signal must specify a valid signal list.

-7 No signals have been specified in the output list.-8 Requested sequence number is not within the

bounds of the current range of sequence num-bers in the archive.

-9 The number of data columns in the archive doesnot match the number of signals in the outputlist.

-10 Search index calculation failure. Sequencenumber is no longer within bounds of thecurrent range of sequence numbers in thearchive.



-101 to -120 Signal type in archive does not match thatspecified in the output list. The position of themismatched entry can be identified by takingthe absolute value of the error code, and sub-tracting 100.

NOTE:Usage of the following PARAMETER signals varies depending uponthe MODE value. For a summary, see the charts in the 'ModuleOperation' sub-sections.

PARAMETER_1 Default: NoneFormat: Analog SignalInput/Output: Input or Output (depending on

MODE value)

varies depending upon the MODE in use:

In Mode 2, the PARAMETER_1 signal is used to hold the LocalSequence Number of the oldest record in the archive.

In Mode 3, the PARAMETER_1 signal is used to specify the LocalSequence Number of whichever record is to be retrieved.

In Mode 4, the PARAMETER_1 signal is used to specify a time stampfor the data temporarily stored in the current archive row, or ifunwired, the current value of #TIME.000. is used.

In Mode 10, 11, or 12 the PARAMETER_1 signal is used to specify thenumber of a signal list. This signal list will be used to hold a copy ofthe most recent archive row stored, (e.g. previous hour's data orprevious day's data.)

This terminal is unused in Modes 0, 1, 5, and 13.


Page ARC_STORE-14


PARAMETER_2 Default: NoneFormat: Analog or Logical SignalInput/Output: Input or Output (depending on

MODE value)

varies depending upon the value of MODE:

In Mode 2, the PARAMETER_2 signal must be analog and is used tohold the Local Sequence Number of the current record in the archivefile.

In Mode 3, the PARAMETER_2 signal must be analog and is used todesignate a signal list which will be used to hold data for the currentarchive record. The signals in this list must be of signal types corre-sponding to the signals in each column of the archive file.

In Modes 10, 11, and 12, the PARAMETER_2 signal may be analog orlogical and is used as a flag to report the storage of a new ArchiveRow. If logical, the PARAMETER_2 signal will be set ON when a newArchive Row is stored. If analog, its value will be incremented by 1when a new Archive Row is stored.

The PARAMETER_2 signal is unused in Mode 0, 1, 4, 5, and 13.

PARAMETER_3 Default: NoneFormat: Analog SignalInput/Output: Output

varies depending upon the value of MODE:

In Mode 2, the PARAMETER_3 signal is used to hold the GlobalSequence Number of the current record in the archive.

In Mode 3, the PARAMETER_3 signal displays the Year value fromthe Julian time stamp of the current archive record.



In Mode 10, the PARAMETER_3 signal may be used to specify aContract Hour for 'gas day' logging. The default contract hour is 12:00AM (midnight).

This signal is unused in Modes 0, 1, 4, 5, 11, 12, and 13.


is used only in Mode 3. It displays the Month value from the Juliantime stamp of the current archive record.


is used only in Mode 3. It displays the Day value from the Julian timestamp of the current archive record.


is used only in Mode 3. It displays the Hours value from the Juliantime stamp of the current archive record.


is used only in Mode 3. It displays the Minutes value from the Juliantime stamp of the current archive record.


Page ARC_STORE-16



is used only in Mode 3. It displays the Seconds value from the Juliantime stamp of the current archive record.

❏ Module Operation - (386EX Protected Mode / 3305 Users only)

Each Archive file must be separately pre-defined in the ACCOL sourcefile, as described in the ACCOL Workbench User Manual (document#D4051). The figure shows a typical archive file definition in theACCOL source file.

The ARC_STORE module must be placed in an executing task.* DoNOT place ARC_STORE modules in Task 0 or they will not execute.

When the ARC_STORE module executes, its operation is governed bythe value of the MODE terminal. The table on the next page shows theusage of the Parameter signals in various modes. NOTE: ALL Param-eter signals are unused in Modes 0, 1, and 5.

In Mode 0, the ARC_STORE module stores a set of signal values('snapshots' of data) in the next available archive file row.

*To avoid file conflicts, all ARC_STORE modules whichaccess the same archive file should be placed in the sametask.

*ARCHIVE 7 NAME: GASFLOW NUM_RECS: 24COLUMN TITLE: TIME SIGNAL: #TIME.000.COLUMN TITLE: DIFF PRESS SIGNAL: COMPRSR1.DIFF.PRESCOLUMN TITLE: TEMP SIGNAL: COMPRSR1.TEMP.

Archive ID Number(Must be entered onARCHIVE terminal of the ARC_STORE Module)

Archive File Name

Number of rows in Archive File

Column 3 TitleColumn 2 Title

Column 1 Title

Signal for Column 1Signal for Column 2

Signal for Column 3



Mode 0,Mode 1,Mode 5

Mode 2 Mode 3 Mode 4

PARAMETER_1 UnusedOutput: LocalSequence Numberof oldest record

Input: LocalSequence Numberof record to beretrieved.

Input: Specify atimestamp for thedata in the currentarchive row. Ifunwired, the currentvalue of #TIME.000is used.

PARAMETER_2 Unused

Output: LocalSequence Numberof the currentrecord

Input: Signal listnumber to holdarchive record data.

Unused

PARAMETER_3 Unused

Output: GlobalSequence Numberof the currentrecord

Output: Year valuefrom Julian timestamp of therequested archiverecord

Unused

PARAMETER_4 Unused Unused

Output: Monthvalue from Juliantime stamp of therequested archiverecord

Unused


Output: Day valuefrom Julian timestamp of therequested archiverecord

Unused


Output: Hour valuefrom Julian timestamp of therequested archiverecord

Unused


Output: Minutesvalue from Juliantime stamp of therequested archiverecord

Unused


Output: Secondsvalue from Juliantime stamp of therequested archiverecord

Unused


Page ARC_STORE-18


If Mode 1 has been selected, operation is identical to Mode 0 except thesignals which provided the data will be reset to default initial values.

If Mode 2 has been selected, the PARAMETER_1, PARAMETER_2,and PARAMETER_3 signals (if wired) will be used to retrieve theLocal Sequence Number of the oldest record in the archive, the LocalSequence Number of the current record in the archive, and the cur-rent value of the Global Sequence Number.

If Mode 3 has been selected, the PARAMETER_1 signal must beassigned the value of a valid Local Sequence Number (obtained viaMode 2). This number is used to retrieve the Archive record matchingthat number. Data for the record is stored in the signal list designatedby the PARAMETER_2 signal; Julian time stamp data for the recordis stored in the PARAMETER_3 through PARAMETER_8 signals.

If Mode 4 has been selected, signal values ('snapshots' of data) will betemporarily stored in the current row, without advancing to the nextrow. Each subsequent execution in this mode will overwrite the datain the current row. The PARAMETER_1 signal may be used to assigna time stamp to the row.

If Mode 5 has been selected, any temporary data stored via Mode 4 isarchived, and tagged with the current value of the Global SequenceNumber, and the record index will advance to the next available row.

Retrieving Archive Data:

The archive data may be retrieved via Mode 3, and stored in a signallist, making it accessible to other elements of the ACCOL load. Alter-natively, UOI commands, the Open BSI DataView or Data Collectorutilities, and the Open BSI Scheduler may be used to retrieve thearchive data directly from the Archive file.



❏ Module Operation - (3530-series TeleFlow / TeleRTU Users only)

Each Archive file must be separately pre-defined in the ACCOL sourcefile, as described in the ACCOL Workbench User Manual (document#D4051). The figure, below, shows a typical archive file definition in theACCOL source file. It shows the same signal being used in threeseparate columns, because three different calculations are beingperformed (instantaneous, minimum, and maximum).

The ARC_STORE module must be placed in an executing task.* DoNOT place ARC_STORE modules in Task 0 or they will not execute.

Depending upon the type of calculations to be performed, the task ratemay be critical. The ARC_STORE module may need to run severaltimes during the user specified interval in order to collect a sufficientnumber of data points for a valid calculation. For example, if hourlyaveraging is to be performed, the user should typically put theARC_STORE module in a task which runs at least once a minute, toallow for at least 60 data values to be averaged.

When the ARC_STORE module executes, its operation is governed bythe value of the MODE terminal. The table on the next page shows theusage of the Parameter signals in various modes.

*To avoid file conflicts, all ARC_STORE modules whichaccess the same archive file should be placed in the sametask.


Page ARC_STORE-20


NOTE: Only PARAMETER_1, PARAMETER_2 and PARAMETER_3may be used with 3530-series units; all other PARAMETER signalsare unused. ALL Parameter signals are unused in Mode 13.

If in Mode 10 (automatic logging), each time the ARC_STORE moduleexecutes it temporarily stores a set of signal values (or intermediatecalculations based on signal values such as running totals, averages,etc.) in the current archive file row. If, during its execution, theARC_STORE module detects that a user-specified time interval haselapsed, the intermediate data or calculations are finalized and theresulting data is archived in the current archive file row, and themodule will advance to the next archive file row.

Mode 10 Mode 11 Mode 12 Mode 13

PARAMETER_1

Input: Signal listnumber used to holdmost recent row ofArchived data, e.g.Previous day,Previous hour, etc.



Unused

PARAMETER_2

Output: Flag toindicate new archiverow has been stored.If analog, value isincremented by 1, iflogical, signal isturned ON.



Unused

PARAMETER_3Input: Contract hour.Default is 12:00 AM(midnight)

Unused Unused Unused

PARAMETER_4 Unused Unused Unused Unused







If Mode 11 has been selected, temporary values or intermediatecalculations based on data collected in Mode 10 are finalized (includ-ing the most recent data collected) and the data/results are archivedin the current row. The module then uses the next available row forsubsequent storage. This Mode differs from Mode 10 in that it onlyfinalizes calculations and archives data; no collections of new dataoccur in Mode 11. Also, the archiving occurs as soon as the module isexecuted in Mode 11; without regard to any user-defined interval.

If Mode 12 has been selected, temporary values or intermediatecalculations based on data collected in Mode 10 are finalized (exclud-ing the most recent data collected) and the data/results are archivedin the current row. The module then uses the next available row forsubsequent storage, and uses the excluded data from the previous rowas the first data for the new row. This Mode differs from Mode 10 inthat it only finalizes calculations and archives data; no collections ofnew data occur in Mode 11. Also, the archiving occurs as soon as themodule is executed in Mode 12; without regard to any user-definedinterval.

If Mode 13 has been selected, ARC_STORE module operations aredisabled. If used, this mode should be selected only after any interme-diate data or calculations has been archived either via Mode 10, 11, or12.

Retrieving Archive Data:

UOI commands, the Open BSI DataView or Data Collector utilities,and the Open BSI Scheduler may be used to retrieve the archive datadirectly from the Archive file. In addition, if a valid signal list isspecified by the user on the PARAMETER_1 terminal, data stored inthe previous archive row (last archived data) may be retrieved inModes 10, 11, or 12.

BLANK PAGE

ACCOL II Reference ManualPage ATOOLS-1

ATOOLS.INI (for DOS-based ACCOL Tools)Tool Initialization File (ACCOL Version 5.6 through 5.13 ONLY)

Certain characteristics of AIC, TOOLKIT, TASKSPY, DIAG, UOI, andNETTOP may, if desired, be set using an initialization file called‘ATOOLS.INI’, which resides in the \ACCOL sub-directory on thePC.* This file can be used to set such parameters as:

The default baud rateThe default PC PortThe type of modemThe type of sign-on prompt which will appearUOI setup menu characteristicsUOI error/status message reporting characteristics

The ATOOLS.INI file allows you to customize certain AIC, TOOLKIT,TASKSPY, DIAG, and UOI system menus and reduces the need forthe operators to alter default parameters in the setup menus eachtime they start these programs.

The following entries may be included in the ATOOLS.INI file; por-tions in bold type should be entered exactly as shown (though capitalletters are not necessary). Each entry should begin in column 1 of thefile. Any quotation marks ‘ ‘ shown surrounding an entry choice areNOT part of the entry, and should NOT BE TYPED in the file. Detailson entries which are used only with UOI are found in the UOI Con-figuration Manual, (document# D5074).

File Entry Explanation

PORT=comn: Used with:AIC, TOOLKIT, TASKSPY, DIAG,and UOI.

Description:sets the default communicationport, where ‘comn:’ is replacedwith either ‘COM1:’ or ‘COM2:’NOTE: If this entry is omitted,‘COM1:’ will be chosen as thedefault.

* ACCOL Version 5.9 (or newer) software uses the ATOOLS.INI file in the directory in which the software is invoked; if no ATOOLS.INI file is found in that directory, the ATOOLS.INI file in the /ACCOL directory is used.

ATOOLS.INI (for DOS-based ACCOL Tools)


Page ATOOLS-2


BAUDRATE=x Used with:AIC, TOOLKIT, TASKSPY, DIAG,and UOI.

Description:sets the default BAUD rate forthis port. Valid entries for xinclude: ‘150’, ‘300’, ‘600’, ‘1200’,‘4800’, ’9600', ‘19200’, or ’19.2k’.NOTE: If this entry is omitted,9600 will be used as the defaultBAUD rate.

MODEM=modem_type Used with:AIC, TOOLKIT, TASKSPY, DIAG,and UOI.

Description:declares the type of modem whichwill be used. Valid entries formodem_type are: 'BBI_FSK', forthe Bristol FSK modem, 'Hayes'for a Hayes modem, or 'UDS' for aUDS modem. NOTE: The FSKModem is required when using theinfrared interface (headband) witha GFC 3308. NOTE: If this entryis omitted, no modem will bedefined.

COLOR=nnn Used with:AIC, TOOLKIT, TASKSPY, DIAG,UOI, and NETTOP.

Description:specifies whether a color or mono-chrome monitor is being used.‘nnn’ should be replaced with ‘YES’to indicate a color monitor is beingused, or ‘NO’ toindicate that a



monochrome monitor is beingused.

SKIP_BANNER=nnn Used with:AIC, TOOLKIT, TASKSPY, DIAG,UOI, and NETTOP

Description:specifies that the Start-up Menuwill not appear. Users will godirectly to the sign-on menu (orthe File Selection Menu inNETTOP.) ‘nnn’ should be re-placed with ‘YES’ or ‘NO’.

TIMEOUT=seconds Used with:AIC, TOOLKIT, TASKSPY, DIAG,and UOI.

Description:specifies the maximum expectedtime (in seconds) that AIC,TOOLKIT, TASKSPY, DIAG, andUOI will wait for the 33XX torespond to a poll. Replace secondswith the maximum expectedtimeout value. If not specifiedhere, this is defined on the Com-munications Setup Menu.

A number of error messages are built into AIC, TOOLKIT, TASKSPY,DIAG, and UOI. They appear along the bottom of the CRT screen.Sometimes these messages scroll by too quickly to be read. In somecases, it may be useful to activate WAIT_ON_ERROR mode, whichhalts scrolling of error messages (to allow them to be read) andprompts the user to press any key to cause processing to continue.


Page ATOOLS-4


WAIT_ON_ERROR=nnn Used with:AIC, TOOLKIT, TASKSPY, DIAG,and UOI.

Description:controls waiting whenever an errormessage is displayed. The use ofthis command is recommended,particularly when the system isbeing set up by the system man-ager. ‘nnn’ is replaced with ‘YES’or ‘NO’.

SYSTEM_WAIT=nnn Used with:AIC, TOOLKIT, TASKSPY, DIAG,and UOI.

Description:controls waiting whenever anymessage along the bottom of thescreen is displayed. This commandis useful only to Bristol personnel.‘nnn’ is replaced with ‘YES’ or‘NO’.

It is sometimes necessary to alter the initialization sequence sent to aHayes modem before a phone number is dialed. Normally, the set-upstream is initialized to “Q0E0V0X4”, a standard Hayes modem stream.The following two keywords are available to modify the stream:

TOT_INIT_MODEM=string Used with:AIC, TOOLKIT, TASKSPY, DIAG,and UOI.

Description:will replace the current set-upstream, with string. For example,if the set-up stream is“Q0E0V0X4”, and



TOT_INIT_MODEM=ABCDE isincluded in the ATOOLS.INI file,the set-up stream will now be“ABCDE”.

CAT_INIT_MODEM=string Used with:AIC, TOOLKIT, TASKSPY, DIAG,and UOI.

Description:will concatenate string to the endof the current set-up stream. Forexample, if the set-up stream is“Q0E0V0X4”, andCAT_INIT_MODEM=ABCDE isincluded in the ATOOLS.INI file,the set-up stream will now be“Q0E0V0X4ABCDE”.

If a Hayes or UDS modem is specified via the 'MODEM=' keyword, thefollowing keywords may be used:

PHONE=phone_number Used with:TOOLKIT, TASKSPY, DIAG, andUOI.

Description:when used with a Hayes or UDSmodem, this keyword will causethe number specified byphone_number to be dialed.

DIAL=dialing_mode Used with:


Page ATOOLS-6


TOOLKIT, TASKSPY, DIAG, andUOI.

Description:specifies the type of dialing tech-nique to be used for modemdialing. Valid entries fordialing_mode are either 'TONE' or'PULSE'.

For some applications, it may be necessary to alter the default securitylevels which allow operator access to the control inhibit/enable (CI) bitfor a signal and the manual inhibit/enable (MI) bit for a signal. Twostatements to accomplish this are included in ACCOL software Ver-sion 5.8 (or newer revision). They allow security levels of either 4 or 5to be used:

CI_SECURITY=level Used with:TOOLKIT, TASKSPY, and UOI.

Description:specifies the security level re-quired in order to change thesetting of the control inhibit/enablebit. level must be either 4 or 5.

MI_SECURITY=level Used with:TOOLKIT, TASKSPY, and UOI.

Description:specifies the security level re-quired in order to change thesetting of the manual inhibit/enable bit. level must be either 4or 5.

POLL_RATE=rate Used with:



AIC, TOOLKIT, TASKSPY, DIAG,and UOI.

Description:specifies the rate in seconds atwhich the PC will issue a poll fordata from the 33xx unit. rate mustbe one of the following values:0.15, 0.2, 0.25, 0.3, 0.4, 0.5, or 1.0.The default is 0.3 seconds. Thisentry requires UOI Version 3.0 (ornewer revision software) orACCOL Version 5.9 (or newerrevision software.)

The following two keywords are provided to allow certain communica-tion parameters, which normally would be entered by the operator onthe Communications Setup Menu, to be pre-defined.

ADDRESS=address Used with:AIC, TOOLKIT, TASKSPY, DIAG,and UOI.

Description:identifies, for the program, thelocal address of the 33xx controllerwith which communication is tooccur. (Note: The local address isdetermined by hardware switcheson the 33xx and must be declaredin the NETTOP files. See themanual for the 33xx device, andthe NETTOP and NETBC UserManual, (document# D4057) fordetails. This command requiresUOI Version 3.0 (or newer), orACCOL Version 5.10 (or newer).

GROUP=number Used with:AIC, TOOLKIT, TASKSPY, and


Page ATOOLS-8


UOI.*Description:

identifies, for the program, theexpanded node addressing groupnumber of the 33xx controller withwhich communication is to occur.(See 'Expanded Node Addressing'later in this manual. This com-mand requires UOI Version 3.0 (ornewer), or ACCOL Version 5.9 (ornewer).

TSNRT_ENABLED=nnn Used with:AIC, DIAG, TOOLKIT, TASKSPY,and UOI.

Description:provides the ability to disable thetransmission, from the PC to a3xxx node, of a Node RoutingTable (NRT). When nnn is YES, aNode Routing Table will be sent inresponse to a time-sync requestfrom a 3xxx controller. When nnnis NO, this transmission is pre-vented. The ability to disable thistransmission requires UOI Version3.1 (or newer), or ACCOL Version5.9 (or newer).

DOWNLOAD_LEVEL=n Used with:AIC, DIAG, TOOLKIT, TASKSPY,and UOI.

Description:provides the ability to specify adefault security level for down-loading. n can range from 1 to 6.

The following ATOOLS.INI statements may be used only in conjuction

Although the DIAG program accepts this parameter anddisplays it, other restrictions prohibit it from using anygroup number other than 0.

*



with the UOI program. See the Universal Operator Interface (UOI)Configuration Manual, (document# D5074) for details on the usage ofthese keywords.

BATCH_MODE=nnnNAME=usernamePASSWORD=accesscodeSCRIPTS level1 level2 level3 level4 level5 level6SECURITY=prompt3308_NODE_TYPE=typeUOI=NO_COMM_MENUUOI=NO_DOWNLOAD :UOI=NO_UMS_CHOICEUOI=OFFLINEXMT_FACTORY_SETTINGS=nnnXMT_SCALECHANGE=nnn

A sample ATOOLS.INI file is illustrated below:

PORT=COM2:BAUDRATE=9600COLOR=YESWAIT_ON_ERROR=YES

BLANK PAGE


Page Audit-1

AuditEAudit

Audit Trail and Extended Audit Trail Modules

The Audit Trail/EAudit Modules provide a history of alarms andsignificant events. This history is stored in a portion of memory knownas the Alarm/Event Buffer and can be displayed at a later time by aserial device such as a Hand Held Terminal or printer. In a redundantsystem, the history is also maintained in the back-up processor. Onlyone of these modules may exist in an ACCOL load.

The EAudit Module provides two additional terminals that count thenumber of alarms and events since the last time the terminals werereset. Audit CANNOT be used with the GFC 3308, RTU 3305 or EGM3530. EAudit must be used with these units.

MODE

LIST

STATUS

FULL_ALARM

A

Audit Trail Module

MODE

LIST

STATUS

FULL_ALARM

AOUTPUT_1

OUTPUT_2

Extended Audit Trail Module

AUDIT/EAUDIT


Page Audit-2

AuditEAuditAudit Trail and Extended Audit Trail Modules

For all alarm signals in the controller, the Audit Trail Module gener-ates a one-line message when the alarm signal goes into its alarmstate, or when it returns to normal after having been in alarm. (ForEnterprise Server and TTVAX Users: The Audit Trail Module does notinterfere with normal Alarm Data Collection.)

An event message is generated for signals which are included in aspecial signal list. (NOTE: Do not confuse "event" with the alarmpriority known as event.) When the signals in the list change theirstatus or value, or their inhibit/enable bits are altered by a sourceoutside of the ACCOL load (such as DataView, Toolkit, etc. but NOTCalculator module statements) an event message is created and storedin the event buffer. In addition, even if the #TIME signals are NOT inthe list, an event message is automatically generated for a systemdate/time change (for example, via a Time Sync/NRT message).

If the unit is part of a redundant pair, upon failover, the newly activeunit will continue to collect alarm and event messages. If failoveroccurs during a logger output or while the active processor is transfer-ring messages to the back-up processor, some entries may be lost.

The number of alarms and events which may be stored varies depend-ing upon the amount of available memory in the controller, the firm-ware revision, as well as restrictions in the ACCOL Tools software:

ACCOL Version 5.0 thru 5.13 up to 4,096 alarms and eventscombined.

ACCOL Workbench (RM) 1.0 or up to 4,096 alarms and newer RM version, 7.0 or newer up to 4,096 events

ACCOL Workbench 6.0, 6.1, or up to 65,535 alarms andACCOL Workbench (PM) 6.2 or up to 65,535 eventsnewer PM version, 7.0 or newer


Page Audit-3

AuditEAudit


❏ Module TerminalsMODE Default: None, entry required


indicates the type of information that will be logged, and in somecases, when the logging will commence.

Mode Description

0 All alarms, as well as any signal value changes for signalsin the signal list (called events) are logged. Logging beginson system startup.

1 Only alarms are logged. Logging begins at system startup.

2 Only events are logged. Logging begins at system startup.

NOTE: Modes 3 through 5 (and Mode -1) are only supported inProtected Mode controllers with PLS/PLX/PES/PEX04.43.00 firmware or newer. They require a signal (insteadof a constant) and they are NOT supported for otherplatforms.

3 When MODE signal initialized to this value, the EAuditmodule will automatically go to MODE -1, on startup. Ifthe program (or user) then changes the MODE signal to 3(or any other positive MODE value) both alarms andevents will be logged.

4 When MODE signal initialized to this value, the modulewill automatically go to MODE -1, on startup. If theprogram (or user) then changes the MODE to 4 (or any


Page Audit-4


other positive MODE value) only alarms will be logged.

5 When MODE signal initialized to this value, the modulewill automatically go to MODE -1, on startup. If theprogram (or user) then changes the MODE to 5 (or anyother positive MODE value), only events will be logged.

-1 All logging suspended. To resume logging, set the MODEto the original MODE value (0 to 5).

NOTE: For any firmware types other than Protected Mode PLS/PLX/PES/PEX 04.43 (or newer), the value on the MODE termi-nal should not be changed while the ACCOL load is running.Depending upon which firmware version you are using, such achange will either be ignored, or result in inconsistent loggingresults.

FULL_ALARM Default: Wrap-around mode if unwiredFormat: Analog or logical signalInput/Output: Input/Output

The FULL_ALARM terminal is used to specify how the module shouldoperate when the Alarm/Event buffer is full, and to provide an indica-tion of when this condition has occurred.

IMPORTANT

In ACCOL Workbench (RM) 1.0 or newer RMversion with LS501, TFA01/TRA01 (or newer)firmware, or in ACCOL Version 6.0 (or newer PMversion), or in ACCOL Workbench 7.0 or newer,with PLS00/PLX00 (or newer) firmware, Wrap-Around Mode is always used, and Stop-On-FullMode DOES NOT EXIST. Users should remove theFULL_ALARM terminal from the source file.Wiring the terminal will generate errors.


Page Audit-5

AuditEAudit


Wrap-Around ModeIf the FULL_ALARM terminal is left unwired, the module will operatein wrap-around mode. This means that if the Alarm/Event buffer isfull, a new message will overwrite the oldest message in the buffer.If you have AE.0, or newer level firmware, wrap-around mode mayalso be selected by putting an analog or logical signal on theFULL_ALARM terminal. NOTE: These signals must be properlyinitialized before the load is downloaded into a controller. They cannotbe changed on-line.

If using an analog signal, set its initial value to a negative number.After the load has been downloaded, the signal on this terminal willautomatically be set to 0, and from that moment on, it will maintain acurrent count of the number of entries in the Alarm/Event buffer.

If you are using a logical signal, set its initial value to ON. After theload has been downloaded, the signal on this terminal will automati-cally be set to OFF. From that moment on, the signal will show ON ifa new entry has caused the Alarm/Event buffer to be full, or OFF ifthe buffer is not full.

Stop-on-Full ModeThe FULL_ALARM terminal may also be used to select stop-on-fullmode. If the Alarm/Event buffer is full, stop-on-full mode will causeany new messages coming in to be discarded, thereby preserving olderentries. To select stop-on-full mode, initialize the FULL_ALARMsignal to 0 (if it is an analog signal), or OFF (if it is a logical signal). Ifan analog signal is used, then after the load is downloaded, theFULL_ALARM signal will indicate the number of messages in theAlarm/Event buffer. If, instead, a logical signal is used, theFULL_ALARM signal will show ON when the buffer is full, and OFFwhen it is not full.


Page Audit-6


LIST Default: None, entry required unlessALARMS ONLY mode

Format: List number or analog signalInput/Output: Input

is the number of the signal list that contains the event signals thatwill be monitored for value changes. An event message will be gener-ated when any signal in the list changes value or status. The signallist cannot contain string signals. If string signals are included in thelist, they are ignored. Never include signals associated with themodule such as the FULL_ALARM or OUTPUT_1 and OUTPUT_2signals in the list. Also, unless you are using Mode 2, you should notinclude alarm signals in the list (since they are collected automati-cally, and so would cause duplicate messages in the Alarm/Eventbuffer. See below).

The MODE terminal can specify three different modes of operation forthe module. If either mode 0 (alarms and events) or mode 2 (eventsonly) is in effect, the signals in the list specified by the LIST terminalwill be recognized as events for which messages must be saved. Ifusing mode 2, alarm signals may be included in the list, however,alarm conditions for those signals are not recorded, only signal valuechanges. If mode 1 (alarms only) is specified on the MODE terminal,then leave the LIST terminal unwired.

Note: On-line modifications to the signal list are not detected once themodule begins to execute.


will display status codes defined below. Negative values indicate anerror condition. If an error occurs, no alarm or event logging willoccur.


Page Audit-7

AuditEAudit


Code Meaning 0 Initialization successful-1 Invalid signal in the signal list-2 Invalid signal list number-3 Invalid entry on MODE terminal, or terminal unwired-4 Invalid FULL_ALARM terminal-5 No Alarm/Event Buffer memory allocated-6 Invalid OUTPUT_1 terminal (EAudit only)-7 Invalid OUTPUT_2 terminal (EAudit only)-8 DOS-based ACCOL Tools incompatible for this firmware

version; use ACCOL Workbench instead.

OUTPUT_1 Default: None, optional signal(EAudit Only) Format: Analog signal


is incremented each time an alarm entry is placed in the Alarm/EventBuffer. This count will continue until cleared by the user.

Beginning with firmware version PLS/PLX/PES/PEX 04.10, thisterminal has an alternate usage. In this case, a negative value (-1 to -255) placed on this terminal can be used to specify an ACCOL Listnumber. This list can be used for enhanced control of audit logging.This list must never be edited during on-line operation, nor can thelist number be changed on-line. For details on the list, see 'Configur-ing the Output_1 List' later in this section.

OUTPUT_2 Default: None, optional signal(EAudit Only) Format: Analog signal


is incremented each time an event entry is placed in the Alarm/EventBuffer. This count will continue until cleared by the user.

NOTE: If the OUTPUT_1 terminal is configured with a negative value(Output_1 list number) then the OUTPUT_2 terminal is ignored.


Page Audit-8


ACCOLTools Vers:

RMSxx.xx , LS500, Ax.xxand earlier firmware

LS501, TFA01, TRA01and newer firmware

PLS00/PLX00 and newerfirmware

5.0 to 5.13

Alarms and events arestored in expandedmemory in a combinedAlarm / Events buffer.Syntax in ACCOL sourcefile *MEMORY section is"Events n" where ’n’ isthe total number ofentries. If Wrap-aroundmode is used, reserve 1extra buffer entry thannormally required. Up to4096 total buffer entriesallowed

TOOLS ANDFIRMWARE AREINCOMPATIBLE FORAUDIT TRAIL USAGE

TOOLS ANDFIRMWARE AREINCOMPATIBLE

ACCOLWorkbench(RM) 1.0

(or newerRMversion)

Same as above exceptsupports syntax of either"Audit_Events n" orsimply "Events n".Either will cause asingle Alarm/Eventbuffer to be created.

Events and alarms arestored in two separatebuffers. Syntax inACCOL source file*MEMORY section is"Audit_Events n""Audit_Alarms m" where’n’ and ’m’ are the totalnumber of events andalarms, respectively, tobe stored. If sufficientRAM, up to 4096 alarmsand 4096 events may bestored. FULL_ALARMmust be left unwired.


ACCOLWorkbenchVersion6.0, 6.1or ACCOLWorkbench(PM) 6.2(or newerPMversion)



Events and alarms arestored in two separatebuffers. Syntax inACCOL source file*MEMORY section is"Audit_Events n""Audit_Alarms m" where’n’ and ’m’ are the totalnumber of events andalarms, respectively,which are to be stored.Up to 65,535 alarms and65,535 events may bestored. FULL_ALARMmust be left unwired.


Page Audit-9

AuditEAudit


❏ Configuring the Audit Trail ModuleTo record and display alarm and event messages using an Audit/EAudit module in conjunction with a LOGGER module, follow thesteps below. (Note: If entries are to be output using a custom protocolsuch as Enron Modbus, or Allen-Bradley PLC-2 Slave, see the ACCOLII Custom Protocols Manual, document# D4066, for further informa-tion. If entries are to be output using UOI commands see the UOIConfiguration Manual document# D5074 for details. If entries are toretrieved using Open BSI Utilities, or the Open BSI Harvester, seethe Open BSI Utilities Manual, document# D5081, or the Open BSIHarvester Manual, document# D5120.)

Step 1: Reserve memory

Memory must be allocated for storage of Event and Alarm messages.Before you use this module, verify that your controller containssufficient memory. The table, on the previous page, summarizescertain aspects of reserving memory for audit trail messages. Formore details, see the ACCOL II Interactive Compiler Manual (docu-ment# D4042) if you are using AIC, or the ACCOL Workbench UserManual (document# D4051) if you are using ACCOL Workbench.

Step 2: Select the Logging Mode and Identify Event Signals

If you select mode 1 for logging alarms, all alarms in the controllerwill be logged automatically, beginning at controller startup; leavethe LIST terminal unwired and continue to the next step. If youwant to log alarm and event messages, beginning at controllerstartup, select mode 0, and create a signal list and enter the listnumber on the LIST terminal. The list must contain those signalswhich should be monitored for value or status changes. Do notinclude alarms in the list. If you want to log events only, beginning


Page Audit-10


*Unless the nEN Format descriptor is used, oncemessages are read from memory, they cannot be reportedagain.

at controller startup, select mode 2. Again, a signal list must becreated, and the LIST terminal filled in. Alarm signals may beincluded in the list when using mode 2, though alarm messages willnot be recorded -- only status/value changes.

Modes 3 through 5 (and Mode -1) are only available for ProtectedMode controllers with PLS/PLX/PES/PEX 04.43.00 (or newer).Modes 3, 4, and 5 are equivalent to Modes 0, 1, and 2, respectively,except logging does NOT start automatically on startup. If theMODE terminal is initialized to 3, 4, or 5, on System startup, theEAudit Module will go into Mode -1 (logging suspended). Loggingwill then only be started if the program (or user) changes the MODEsignal value to a MODE value other than -1. When that happens, thelogging mode will be based on whatever the initial value of theMODE terminal was, prior to its change to MODE -1.

NOTE: No matter which mode you are using, be selective whenchoosing signals for logging by the Audit/EAudit module. If you logsignals which fluctuate rapidly (for example, process I/O signals),your event buffer space will be used up quickly, and you may end upwith a history which is not particularly useful to you.

Step 3: Configure the terminals on the Audit Trail Module

The Audit Trail Module should be defined in Task 0. There can onlybe one Audit Trail Module in the ACCOL load. This single modulemay be either the Audit Module or the EAudit Module. Make theproper entries for the module terminals according to the instructionsin this section.

Step 4: Set up a Format and Logger Module

Create a LOGGER format that includes one of the descriptors forAudit Trail message retrieval (EA, nEL, or nEN).* Format descrip-tors are described in the section on 'Formats' in this manual.Create a LOGGER module and define a LOGGER port. In thefollowing sample application, the LOGGER port connects to a Hand


Page Audit-11

AuditEAudit


Held Terminal. It can also be connected to a printer or other termi-nal device. If a LOGGER output error occurs, or the printer or otherterminal device is disconnected, any subsequent event or alarmmessages will be lost. The number of the Format created aboveshould be assigned as the signal value or constant at the LOGGERmodule Format terminal. See the 'Logger' section for more informa-tion.

❏ Configuring the OUTPUT_1 ListThe signal list number for the OUTPUT_1 list is specified by puttingthe negative of the list number on the OUTPUT_1 terminal.

The OUTPUT_1 list provides EAudit users more control of, andinformation about, the status of the alarm / event buffers. Failure todefine this list as described will result in an error, and the EAuditModule will be disabled.

The signals in the OUTPUT_1 list are shown below. (Signal namesmay be changed at the user's discretion.)

Signal1 TOTAL.ALARMS. This analog signal is incrementedevery time an entry is logged into the Alarm buffer.The EAudit Module never resets this signal, however,the user can reset it, if desired. This signal is typicallyinitialized to 0.

Signal2 TOTAL.EVENTS. This analog signal is incrementedevery time an entry is logged into the Event buffer. TheEAudit Module never resets this signal, however, theuser can reset it, if desired. This signal is typicallyinitialized to 0.

Signal3 LOG.CNTRL.MODE - This analog signal can be set toany one of the modes shown below. The mode applies to


Page Audit-12


ALL ports using the Audit system. NOTE: The modeCANNOT be changed on-line.

0 Wrap Around Mode: In this mode, the module firstupdates the TOTAL.ALARMS, TOTAL.EVENTS listentries, and STATUS terminal. Newer entries in theAlarm and Event buffers overwrite older entries, ifthe buffer is full.

1 Stop-On Full Mode. In this mode, the module willfirst update the TOTAL.ALARMS, TOTAL.EVENTSlist entries, and STATUS terminal, but if the Log-ging Master Port (described later) detects that theAlarm or Event buffer is full, all logging will bestopped. Logging will not resume until one or moreentries have been deleted from the full buffer.

2 Stop on Full and Lock Events Mode. In this mode themodule will update TOTAL.ALARMS,TOTAL.EVENTS list entries, and STATUS terminal,but if the Logging Master Port detects that theAlarm or Event buffer is full, all logging will bestopped. Once logging has stopped ANY CHANGESTO EVENT SIGNALS ARE LOCKED OUT. Alarmsignals can still change, but their changes will NOTbe logged when logging is stopped. Logging will notresume, and event signals will not be changeable,until one or more entries have been deleted from thefull buffer. NOTE: Even while logging has stopped, itis possible that buffers may not appear full whenviewed by ports other than the Logging Master Port.The Logging Master Port is the only port whichphysically deletes entries from the Alarm and Eventbuffers; all other ports simply view a subset of thebuffers, and deletions are only from the subset beingviewed by the port, not the actual buffers. The usermust ensure that software communicating through


Page Audit-13

AuditEAudit


the Logging Master Port retrieves and deletes alarmsand events from the buffers to allow for more entriesto be saved in the buffer.

Users should exercise care when selecting thismode, since the locking of event signals couldhave an adverse effect on the ACCOL load,communications (RDB), report by exception(RBE) and other sub-systems. Failures at thelogging master could result in serious problems,since the Logging Master is responsible fordeleting entries from the Alarm and Eventbuffers.

Signal4 CURRENT.STATE. This analog signal displays thecurrent logging state as follows:

0 Logging is active.

1 Logging is stopped.

2 Logging is stopped, event signals are locked.

Signal5 LOG.MASTER.ID This analog signal identifies whichport will serve as the Logging Master Port. The com-puter connected to this RTU through the LoggingMaster Port is the only user of the Audit system whichcan physically delete entries from the alarm and eventbuffers; all other ports can only delete entries fromtheir particular view of the audit buffers. If an invalidvalue for LOG.MASTER.ID is specified, and theLOG.CNTRL.MODE is 1 or 2, the Logging Master Portdefaults to 10 - Network (Slave) Port. The LoggingMaster Port is identified as follows:

10 Network (slave) port in load


Page Audit-14


11 1st Pseudo Slave Port in load12 2nd Pseudo Slave Port in load13 3rd Pseudo Slave Port in load14 4th Pseudo Slave Port in load15 5th Pseudo Slave Port in load16 6th Pseudo Slave Port in load17 7th Pseudo Slave Port in load18 8th Pseudo Slave Port in load

Port order to determine the 1st, 2nd, etc. numberingof the Pseudo Slaves in the ACCOL load is as follows:BIP1, BIP2, Port A, Port B, Port C, Port D, Port G,Port H, Port I, Port J. For example, if Pseudo SlavePorts are defined on BIP1, Port A, and Port D, thenBIP1 would be the 1st Pseudo Slave Port (enter 11 ifchoosing it as the Logging Master Port), Port Awould be the 2nd Pseudo Slave Port (enter 12 ifchoosing it as the Logging Master Port) and Port Dwould be the 3rd Pseudo Slave Port in the load(enter 13 if choosing it as the Logging Master Port).

NOTE: Users with Real mode firmware can onlyhave a maximum of two Pseudo Slave ports; userswith Protected mode firmware can have a maximumof eight Pseudo Slave ports.

If the Logging Master Port is a Custom Port, codesfor ports are fixed as follows:

51 Custom on Port A52 Custom on Port B53 Custom on Port C54 Custom on Port D55 Custom on BIP 156 Custom on BIP 257 Custom on Port G58 Custom on Port H


Page Audit-15

AuditEAudit


59 Custom on Port I60 Custom on Port J

For each user (Audit Port defined) a set of five signals is created. Thefirst set of signals (Signal6 to Signal9) are always for the LoggingMaster Port, all remaining sets are assigned on a first-come-first-servebasis to other ports requesting Audit data. NOTE: For TeleFlow /TeleRTU users, only the first set of signals (for the Logging MasterPort) are used.

Signal6 AUDIT.USER.ID1 - This analog signal outputs one ofthe following pre-defined user IDs:

10 Network (slave) port in load11 1st Pseudo Slave Port in load12 2nd Pseudo Slave Port in load13 3rd Pseudo Slave Port in load14 4th Pseudo Slave Port in load15 5th Pseudo Slave Port in load16 6th Pseudo Slave Port in load17 7th Pseudo Slave Port in load18 8th Pseudo Slave Port in load51 Custom on Port A52 Custom on Port B53 Custom on Port C54 Custom on Port D55 Custom on BIP 156 Custom on BIP 257 Custom on Port G58 Custom on Port H59 Custom on Port I60 Custom on Port J

Signal7 ALARM.COUNT1. - This analog signal reports the totalnumber of alarms in the Alarm buffer, for this user'sview. This increases as more entries are logged, and


Page Audit-16


decreases when the user deletes entries from thebuffer. The value of this signal can range from 0 to oneless than the capacity of the Alarm buffer.

Signal8 ALARM.FULL.1 - This is a logical signal which theEAudit Module turns ON when the Alarm Buffer isfull, and turns OFF, when the Alarm Buffer has spacefor at least one more entry.

Signal9 EVENT.COUNT.1 - This analog signal reports the totalnumber of events in the Event buffer, for this user'sview. This increases as more entries are logged, anddecreases when the user deletes entries from thebuffer. The value of this signal can range from 0 to oneless than the capacity of the Event buffer.

Signal10 EVENT.FULL.1 - This is a logical signal which theEAudit Module turns ON when the Event Buffer is full,and turns OFF, when the Event Buffer has space for atleast one more entry.

Signal11 through Signal15Set of signals for 2nd Audit user: (AUDIT.USER.ID2,ALARM.COUNT.2, ALARM.FULL.2,EVENT.COUNT.2, EVENT.FULL.2)

Signal16 through Signal20Set of signals for 3rd Audit user: (AUDIT.USER.ID3,ALARM.COUNT.3, ALARM.FULL.3,EVENT.COUNT.3, EVENT.FULL.3)::

(A similar set of signals should be created for each Audit user.)

NOTE: The first set is always reserved for the Logging MasterPort; all other sets are assigned on a first-come-first-servebasis as requests for audit data come in from the ports. If


Page Audit-17

AuditEAudit


not enough sets of signals are created, the later auditrequests will still be processed, but buffer counts, andbuffer full statuses will NOT be reported for those users(ports).

❏ Sample ApplicationThe figure on the following page summarizes the ACCOL structuresneeded to send event and alarm messages. In this example, messagesare sent through Port B to a Hand Held Terminal. The Format speci-fies that up to seven messages can be displayed. Each message will beplaced on a separate line. The oldest messages will be shown first. Ifthe signal TANK5.SETPT changes value, the Hand Held Terminalscreen may look like this:

Event and Alarm Messages:

12:01:05 08/12/88 #LINE.004. ON C-ALARM13:04:10 08/12/88 TANK5.SETPT. 10.50 to 20.00 psi value change


Page Audit-18


MODE = 0

LIST = 3

STATUS = TRAIL.STAT

FULL_ALARM = FILL.001 Signal List #3

001 TANK5.SETPT002

MODE = #OFF

LIST = (not used)

FORMAT = 5

LOGGER

PORT = 2

Format #5

10 18 x, " Event and Alarm Message ", //20 7 EL

13:04:10 08/12/88 TANK5.SETPT. 10.50 TO 20.00 PSI VALUE CHANGE12:01:05 08/12/88 #LINE.004. ON C-ALARM

Messages:

ACCOL load

controller

A

Port B


Page Audit-19

AuditEAudit


Inte

rpre

ting A

larm

&

E

vent M

essages a

s p

rinte

d v

ia L

OG

GE

R m

odule

Analo

g V

alu

e C

hange M

essage

hh :

mm

: ss

dd-

mm

m-y

y b

bbbb

bbb.

eeee

ee.a

aaa

svv

vvv

. vv

TO

svv

vvv

. vv

uuu

uuu

VA

LUE

CH

NG

Tim

e1D

ate1

Sig

nal

Nam

eO

ld V

alue

New

Val

ueU

nits

hh :

mm

: ss

dd-

mm

m-y

y b

bbbb

bbb.

eeee

ee.a

aaa

t t

t t t

t T

O

t t t

t t t

ST

AT

US

CH

AN

GE

Tim

e1D

ate1

Sig

nal

Nam

eO

ld S

tatu

s2N

ew S

tatu

s2

Dig

ital V

alu

e C

hange M

essage

Analo

g A

larm

M

essage

hh :

mm

: ss

dd-

mm

m-y

y b

bbbb

bbb.

eeee

ee.a

aaa

svv

vvv

. vv

uu

uuuu

R

ET

UR

N T

O N

OR

MA

L

hh :

mm

: ss

dd-

mm

m-y

y b

bbbb

bbb.

eeee

ee.a

aaa

svv

vvv

. vv

uu

uuuu

xx

xx y

- A

LAR

M (

svv

vvv

. vv

)

Tim

e1D

ate1

Sig

nal

Nam

eV

alue

Uni

ts

Ala

rm T

ype3

Ala

rm P

riorit

y4

Ala

rm L

imit

Dig

ital A

larm

M

essage

hh :

mm

: ss

dd-

mm

m-y

y b

bbbb

bbb.

eeee

ee.a

aaa

t t t

t t t

y

- A

LAR

M

hh :

mm

: ss

dd-

mm

m-y

y b

bbbb

bbb.

eeee

ee.a

aaa

t t t

t t t

y

- R

ET

UR

N T

O N

OR

MA

L

Tim

e1D

ate1

Sig

nal

Nam

eS

tatu

s2A

larm

Prio

rity4

Not

es:

1.

Tim

e a

nd D

ate

- T

his

is t

he t

ime

and

dat

e th

at t

he a

larm

or

sig

nal

chan

ge o

ccur

red.

2.

Sta

tus

- T

his

fiel

d w

ill s

how

the

ON

/ O

FF

tex

t as

sign

ed t

o th

e s

igna

l.3.

A

larm

Typ

e -

One

of

four

cod

es w

ill a

ppea

r h

ere

: H

IGH

, H

IHI,

LO

W,

AN

D L

OLO

.

Exa

mpl

es:

12:0

1:05

12-A

UG

-88

#

LIN

E.0

04O

NC

-ALA

RM

4.

Ala

rm P

riorit

y:C

= c

ritic

alN

= n

on-c

ritic

alO

= o

pera

tor

guid

eE

= e

vent

13:0

4:10

12-A

UG

-88

TA

NK

5.S

ET

PT

.10

.50

TO

20.

00P

SI

V

ALU

E C

HA

NG

E

BLANK PAGE

Auto-Dial Modem InterfaceAuto-Dial Modem Interface

ACCOL II Reference ManualPage Auto-Dial-1

❑ Auto-Dial Modem InterfaceThe Auto-Dial Modem Interface allows a Network 3000 controller tocommunicate with another Network 3000 controller via the publictelephone system.* Each controller must be equipped with either aninternal or external modem. One controller will dial out over the publictelephone system to reach the other controller.

The auto-dial capability is intended to support user-controlled, lowfrequency, special applications, therefore the implementation of theauto-dial network is a combination of system level and applicationlevel software with most of the control for the modem being the re-sponsibility of the user. This provides maximum flexibility of use.

Note that there is no “automatic” auto-dial, e.g. the requirement totransmit a message to a slave (which is only accessible via theswitched network) will not automatically cause a master to dial thatslave node.

Dialing is handled differently based on port type (master, slave, orpseudo slave). As far as BSAP is concerned, the ports do not change.Only a slave port will request or accept a Node Routing Table/TimeSync message (the message is discarded by a pseudo slave port). Aslave or pseudo slave port can initiate a dial to establish a connectionto the master or pseudo master device, but they cannot initiate com-munications. They must be polled by the master or pseudo masterdevice in order to transfer any messages.

Several system signals, one for each of the serial and built-in I/O ports,control the use of the auto-dial facilities. Each signal will hold thenumber of the Dial Control Signal List, or Enhanced Slave DialControl Signal List for their respective lines. #DIAL.nnn will beused as a general reference to any one of these system signals.

Whenever the switched network is being used, there are several waysthat the modem can force a disconnect. The modem may disconnect if aloss of carrier is detected, a break signal is detected, or a timeoutperiod has elapsed.

Auto-Dial Modem Interface

*The public telephone system is sometimes referred to by theterm ‘switched network’.



❑ Modems Supported

Bristol Hayes-Compatible Modems:

Currently, Bristol offers two Hayes-compatible auto-dial modems* foruse with its Network 3000 product lines:

● 1200 Baud PSTN/PL Modem. Must be set to use PSTN.See CI-1200 for details.

● 9600 Baud PSTN Modem. See CI-9600 for details.

These modems are shipped from Bristol with modem profile settingsprogrammed for use with Bristol equipment. DO NOT ALTER THEFACTORY DEFAULTS UNLESS YOU ARE KNOWLEDGEABLEABOUT ITS EFFECT ON BRISTOL COMMUNICATIONS.

Other Hayes-Compatible Modems:

Because of the large number of modems available on the market, it isNOT possible for Bristol to test and support non-Bristol modems.Bristol’s Application Support Group, however, has successfully testedcurrent Bristol equipment with two other commercially availablemodems, and has modem profile information for setting them up towork with Bristol equipment. These modems are:

● Hayes Accura 144 Modem

● U.S. Robotics Sportster Modem, (14.4K FAX Modem V.32 bis with V.42 bis)

There is NO GUARANTEE that other Hayes-compatible modems youpurchase will be compatible with Bristol equipment. If you want to tryto use another modem, it must have the following characteristics:

● it must go to Command mode when Data Terminal Ready (DTR)is off for 50 milliseconds

*Bristol’s older model SNM Modem is no longer available. Ifyou are using an SNM Modem, see the ‘Notes on using the OldBristol SNM’ sub-section for information.



● it must use a Carriage Return code of 13 (0DH)

● Data compression must be DISABLED.

● Error correction must be DISABLED.

● Auto-baud must be DISABLED. Bristol controllers do NOTprovide auto-baud or automatic ‘fall back’ to slower baud rates.

❑ ❑ ❑ ❑ ❑ ACCOL Software Interface

Control of the auto-dial interface for a particular port is accomplishedin ACCOL using the #DIAL system signal for that port, and a user-configured signal list referenced via the #DIAL value.

These #DIAL signals and their associated ports are:

Port A #DIAL.000 BIP_2 #DIAL.005Port B #DIAL.001 Port G #DIAL.006Port C #DIAL.002 Port H #DIAL.007Port D #DIAL.003 Port I #DIAL.008BIP_1 #DIAL.004 Port J #DIAL.009

Each of these signals are analog, and default to a value of 0. This valuemust be changed to reference the number of the signal list used for dialcontrol of the corresponding port.

If the value of the #DIAL signal is a positive number, that numberdirectly specifies the Dial Control Signal List. For example, if#DIAL.003. has a value of 23, then signal list 23 must contain dialparameters for Port D. Port D could be either a Master Port, a SlavePort, or a Pseudo Slave Port.

If the value on the #DIAL signal is a negative number, the absolutevalue of the number specifies the Enhanced Slave Dial Control Signal



List. For example, if #DIAL.001. has a value of -15, then signal list 15must contain Enhanced Slave Dial parameters for Port B. In this case,Port B must be a Slave Port. Enhanced Slave dial parameters cannotbe used with Master Ports.

The next sub-sections describe the signals in the Dial Control SignalList or Enhanced Slave Dial Control Signal List:

Dial Control Signal List

The structure of a dial control signal list is as follows:

The minimum valid dial control signal list consists of the first fourentries and would have a Phone #/Command Select value of 1, select-ing the first entry in the Phone #/Command List. The choice of signalnames used is that of the user.

DIAL ENABLE this signal controls the dialing and the disconnect-ing of the modem. It also controls the issuance ofSpecial Command strings to the modem. If thevalue of this signal is zero (or OFF), then dialingis disabled. If a previous connection is active, it isterminated and the modem returns to Commandmode).



When this signal is non-zero (or ON) it enablesdialing or a Special Command sequence, asdetailed below.

For a Master Port, operation is enabled when thissignal goes from zero to non-zero (or OFF to ON).An active connection will be terminated when itgoes from non-zero to zero (or ON to OFF). Theuser must also set this signal to zero following adial or command failure in order to be able toinitiate a retry. The signal is scanned at a 1second rate, therefore it must be off for a mini-mum of 1 second prior to re-enabling it.

For a Slave or Pseudo Slave port this signal alsoserves to define the maximum connection time inseconds and should therefore be an analog signal.Operation is disabled if the signal is zero. Opera-tion is enabled whenever the signal is non-zero(there is no transition required). Once a successfulconnection is established, the DIAL ENABLEvalue is used to control the connection time. Whenthe time expires, or if DIAL ENABLE is set tozero, the modem will be disconnected from thetelephone line and return to Command mode). Seethe ‘Slave Line Dialing’ and ‘Pseudo Slave LineDialing’ sub-sections for details.



DIAL STATUS is an analog signal that reflects the status of theauto-dial controls and operation. The possiblestatus codes are:

StatusCode Description2 Dialing or Special Command completed

successfully

1 Dialing or Special Command in progress

0 Phone hung up

-1 Dialing complete but line was Busy

-2 Dialing failed (no dial tone when required,no answer, or no response from modem)

—Or—Special Command failed (no response frommodem or unrecognized response frommodem)

NOTE:Up to 100 seconds are allowed for themodem to respond to a dial or commandoperation. During this time subsequent I/O requests to that port will be queued,including a Hang-Up operation generatedin response to DIAL ENABLE beingturned off. The dial or command operationmust complete before a subsequent re-quest can be honored.

For a dial operation, this error mayindicate that you have an invalid tele-phone number in the selected signal.



StatusCode Description (continued)

-2 (continued)It may also occur if a Busy condition isencountered and the modem does notreturn a unique ‘Busy’ indication. (Somemodems require a special command inorder to return a unique ‘Busy’ indication.See the examples in the ‘Special Com-mands’ sub-section.)

For a command operation, this error mayindicate that you have included a requestfor modem data in the string, e.g. a &Vcommand. The return of data from themodem is not supported by the firmware.

-3 Dialing not possible

-4 Special Command failed (“ERROR”response from modem)

-5 Invalid dial control signal list

-6 Invalid PHONE #/COMMAND SELECT(value=0 or > number of entries in Phone#/Command list)

-7 Invalid PHONE #/COMMAND (signal nota String)

-8 Invalid PHONE #/COMMAND length(String is NULL or > 32 characters)

PHONE #/COMMANDSELECT this signal provides an offset into the list of Phone



Numbers/Special Commands and designateswhich entry is to be used for the current opera-tion. The minimum value is ‘1’ which selects thefirst entry.

PHONE #/COMMANDsignals 1 to n each of these String Signals hold either a tele-

phone number in the form required by the modem,or Special Command strings. A Special Commandstring is indicated to the 3310/3330/3335 firmwareby an exclamation point (‘!’) in the first characterposition.

Enhanced Slave Dial Control Signal List(RMS04, LS501, PLS03/PLX/PES/PEX03, AM.20 or newer firmwareONLY; AM.20 also requires ACCOL Workbench 8.3 or newer)

The Enhanced Slave Dial Control Signal List may be used instead ofthe Dial Control Signal List, for Slave Port dialing only. In addition tothe types of entries in the standard list, it allows the user to specify adelay in disconnecting if the slave runs out of data to send, and a dial-up acknowledgment signal.

When standard Slave dialing is used, a slave node dials into its Mas-ter. The Master has no way of knowing which slave is dialing in,therefore, it begins polling all of its slaves, one by one, until it polls theslave dialing in, which can then answer. This is equivalent to thesituation of hearing a ‘knock’ on your door, but the person knockingcannot speak until you call out their name. The only way you can findout who it is, then, is to call out the names of everyone you know, untilyou reach the name of the person doing the knocking, who can thenanswer, as in ‘Is that you Alice?’, ‘Is that you Bob?’, ‘Is that you Carol?’,and continuing this until you say ‘Is that you Margaret?’ and Margaretanswers ‘Yes it’s me!’ Depending upon the number of acquaintancesyou have, this could take a long time.



Enhanced Slave dialing is a much more efficient method. In thissituation, when the Master begins to poll its first slave node, the slavedialing in will answer (even if it is not the first slave) and the Masterwill then accept its data immediately, rather than polling its otherslaves. To follow the previous analogy, when you hear a knock on thedoor, and start asking ‘Is that you Alice?’, the person knocking willanswer ‘No! it’s not Alice, it’s Fred’ (or whatever their name is). Nowyou can say ‘Hi Fred, what do you have for me?’ and Fred responds.

This enhanced method, which uses the DIAL_UP_ACK enable signal,greatly increases throughput in a system with many slave nodes, byeliminating extraneous polling to nodes that aren’t dialing in.

The figure, below, shows the organization of the Enhanced Slave DialControl Signal List. It is similar to the Dial Control Signal List exceptit has some additional signals which include the Empty TransmitQueue disconnect time signal, and the DIAL_UP_ACK enable signal.



For example, if #DIAL.003. is set to ‘-5’, an Enhanced Slave DialControl Signal List must be created, similar to the list shown below.The choice of signal names is entirely up to the user.

*LIST 510 PORTD.ENABLE.DIAL20 PORTD.STATUS.DIAL30 POSITION.OFSEL.SIG40 MAXEMPTY.QUEUE.TIME50 PORTD.DIALUP.ACK60 PORTD.PHONE.SEL70 PHONENUM.CALL.RTU180 PHONENUM.CALL.RTU290 PHONENUM.CALL.RTU3

The Enhanced Slave Dial Control Signal List has the following ele-ments:

DIAL ENABLE (see description under Dial Control Signal List)

DIAL STATUS (see description under Dial Control Signal List).

POSITION ofSELECT this analog signal specifies the position in the list

of the PHONE#/COMMAND SELECT signal. (Theposition of this signal has been made variable toallow for special purpose signals to be added tothe list, such as the Empty Transmit QueueDisconnect signal, the DIAL_UP_ACK Enablesignal, and any signals related to future enhance-ments.)

In List 5, shown, on the next page,POSITION.OFSEL.SIG is the POSITION ofSELECT signal.



*LIST 510 PORTD.ENABLE.DIAL20 PORTD.STATUS.DIAL30 POSITION.OFSEL.SIG40 MAXEMPTY.QUEUE.TIME50 PORTD.DIALUP.ACK60 PORTD.PHONE.SEL70 PHONENUM.CALL.RTU180 PHONENUM.CALL.RTU290 PHONENUM.CALL.RTU3

It In this case, it should be set to 6 because thereare two special purpose signals(MAXEMPTY.QUEUE.TIME andPORTD.DIALUP.ACK) which pushes thePHONE#/COMMAND SELECT signal(PORTD.PHONE.SEL) to position 6.

If there are no special purpose signals to beincluded in the list, this signal should be set to ‘4’.

EMPTY TRANSMITQUEUE DISCONNECTTIME this is an analog signal which specifies how long,

in seconds, a connection should be maintainedafter the slave node’s transmit queue becomesempty, i.e. the slave has no more data messages tosend to its master. If this signal is not included, isof the wrong type, or its entry is less than or equalto zero, the default disconnect time will be 10seconds.

DIAL_UP_ACKEnable this is a logical signal. When set ON, it allows the

Slave node to acknowledge the first poll messageissued by its Master, whether or not the poll is for



this slave. This allows the slave node dialing in toimmediately send data to the master, rather thanwait for the master to poll all of its nodes until itreaches the correct slave node. This featuresignificantly increases throughput on Slave dial-up.

PHONE#/COMMAND SELECT signal (see description under Dial Control Signal List).

PHONE#/COMMAND signals 1 to n (see description under Dial Control Signal List).

Phone Number Strings

A Phone # string should contain only digits and selected charactersrecognized by the modem as controls. Hyphens ‘-’ may be included forreadability but are not sent to the modem. A maximum of 32 charac-ters, excluding hyphens, is permitted.

NOTE:The 3310/3330/3335 firmware automatically sends the ATprefix and D dial command code to the modem beforesending the user’s Phone Number string. The characters‘W’ or ‘w’ within the string are automatically converted tocommas (‘,’). The required terminating Carriage Return(13 or 0DH) is automatically appended. The pre-dial querysequence automatically sets up the modem for Tonedialing and a 4-second delay for a comma (‘,’).

Characters allowed in a phone number string:

a. Digits 0-9

b. W - Wait for 4 seconds and proceed



c. T - Change to Touch Tone dialing

d. P - Change to Pulse dialing. The initial query sequenceby the firmware sets the modem for Tone dialing,therefore, Pulse mode remains in effect only for a singledialing sequence.

e. - The dash or hyphen is optional to provide for readabil-ity. They are not sent to the modem.

EXAMPLE: T-9-555-1212

Special Command Strings

The user can issue one or more modem commands by placing them in astring signal with an exclamation point (‘!’) in the first characterposition. The 3310/3330/3335 firmware examines the first character ofthe user string. If it is an ‘!’ indicating a Special Command, the balanceof the string will be sent to the modem and the required terminatingCarriage Return (13 or 0DH) will automatically be appended. With theexception of the initial ‘!’ which is not sent to the modem, and theterminating CR which is automatically inserted, the user string is sentto the modem with no translations or editing. This string may containa Dial command and telephone number.

The possible status values include:

Dial Status Modem Response

2 “OK” or “CONNECT”

-1 “BUSY”

-2 No modem response, orunrecognized data

-4 “ERROR”



EXAMPLE 1:For some modems, the Special Command string, below, causes themodem to hang-up and go to Command state on an On-to-Off transi-tion of DTR; to ignore RTS and assume CTS; to answer on the firstring, and to save storable configuration parameters as user profile 0.

!AT &D2 &R1 S0=1 &W0

EXAMPLE 2:Some modems may require that a command be issued in order torespond with a unique result code for ‘Busy’. Otherwise a Busycondition results in a DIAL STATUS of -2 instead of a -1.

The example string, below, causes return of “BUSY” for a Busycondition with certain types of modems:

!AT X3

❑ Application NotesThe following sections detail set-up and recommended user softwareprocedures at each end of a dial-up line. In each case, it is assumedthat the port is dedicated to the switched network operations (auto-dial or auto-answer or both).

The following dial-up scenarios will be considered:

Case 1: Master node dials out to its slave nodes.Configure each of the slave nodes as described under ‘Slave LineAuto-Answer’.

Configure the Master node controller as described under ‘Master LineDialing’. Exceptions to this rule: If the Master node is not a control-ler, but an Open BSI workstation, follow the dial-up instructions inthe Open BSI Utilities Manual (document# D5076). If the Master



node is a PC Workstation running UOI, or older DOS-based ACCOLTools (On-line AIC, Toolkit, Taskspy), dialing is configured via the BBICommunications Setup Menus.

NOTE: Also see the ‘Pseudo Slave Line Auto-Answer’ sub-section.

Case 2: Slave node controllers dial into the Master controller.Configure each of the Slave nodes as described under ‘Slave LineDialing’.

Configure the Master node controller as described under ‘Master LineAuto-Answer’.

If you have Open BSI Version 2.1 (or newer) the Master node couldalso be an Open BSI Workstation, provided that the Enhanced SlaveDial Control List with Dial_Up_Ack is configured in each Slave node.

NOTE: Only Open BSI supports slave nodes dialing in; the DOS-basedACCOL Tools and UOI DO NOT SUPPORT THIS METHOD.

NOTE: Also see the ‘Pseudo Slave Line Dialing’ sub-section.

Case 3: Master Controller Dials Out to Slaves and Slaves Dial IntoMaster ControllerThis is a combination of Case 1 and Case 2. See the ‘Master and SlaveDialing’ sub-section.



Master Line Dialing

Master line dialing allows the master to select a slave node to commu-nicate with via the switched network.

NOTE

See the ‘Slave Line Auto Answer’ sub-section for recommended modemset-up at each of the slave node(s) which the Master will dial.

This feature allows the application software to control the auto-dialmodem to achieve low frequency communication (for example, fourtimes a day) with remote nodes via the public telephone network.

In order to use Master line dialing, the modem should be set to defaultto COMMAND mode. The system signal #DIAL.nnn must hold thenumber of a valid Dial Control Signal List otherwise dialing will not beenabled for that port. Also, if the DIAL ENABLE signal in that list iszero, then dialing will be suppressed as well.

Because any slave node which is to be dialed can only respond afterthe master has established the connection, polling should normally beturned off for these nodes via the node polling array (#NDARRAY) andspecifically turned on as part of the dialing sequence. If polling isalways enabled for these nodes they will typically be in the master’sDead List, thus consuming polling time, and the associated#NODE.nnn alarm signals will be turned ON. The line alarm for theport (#LINE.nnn) will also be turned on if all nodes are in the DeadList. When the master calls a slave and it responds, the #NODE.nnnalarm signal associated with that slave will return to normal and the#LINE.nnn alarm will return to normal, but both signals will return tothe alarm state when the line is disconnected and the slave no longerresponds. The user may also choose to alarm inhibit these signals.Their ON/OFF state may still be monitored by the ACCOL program.



Typical master dialing scenario:

1. Polling for slave nodes (of the Master Port which will dial) shouldhave their polling turned off via the node polling array (#NDARRAY)in the Master node. This prevents polling of non-target nodes (if any)while connected to the switched network line and provides a con-trolled environment for the dial-up sequence.

2. Set #DIAL.nnn to select the Dial Control Signal List. This may be setup during initialization. If entries in the list are changed at runtime,up to 10 seconds will be required for the master port task to detectthe change.

3. Select the number to dial using the PHONE # SELECT signal in thelist. This may be set up during initialization.

4. Enable dialing using the DIAL ENABLE signal in the list.

5. Wait for a connection or a dialing error by monitoring DIAL STA-TUS. (It takes a minimum of 15 seconds to establish a connection; amaximum of 110 seconds to report a failure).

6.a. If a successful connection is made (DIAL STATUS=2), initiate trans-missions by enabling polling for the dialed node in the node pollingarray (#NDARRAY). Allow enough time for at least 4 poll periods toexecute, then verify that the target node is communicating by testingthe associated #NODE.nnn alarm signal for OFF (if the node fails torespond in three successive poll periods its node alarm will be turnedON). For example, if the master port poll period is 3 seconds, afterenabling polling for the dialed node, delay 12 seconds before testingthe #NODE.nnn signal. If it is ON, indicating that the node is notresponding, turn off polling in #NDARRAY, terminate the connectionby setting DIAL ENABLE to zero (or OFF), and go to Step 8.

If the #NODE.nnn signal is OFF and collection of specific data fromthe node is to be done, e.g. reading signal or array values via an



ACCOL Master Module, the Master Module should be executed atthis point.

6.b. If the DIAL STATUS does not indicate a successful connection, do notenable polling or execute the ACCOL Master Module; set DIALENABLE to zero (or OFF) and go to Step 8. Errors -1 through -3indicate that dialing was attempted but failed. Errors -5 through -8indicate that the control structures are not properly set up; no dialingwill be initiated.

7. On completion of the user-allotted communication time, turn offpolling for the dialed node in #NDARRAY, then set DIAL ENABLEto zero (or OFF).

NOTE:It is the user’s responsibility to allocate enough time toallow the slave to report any alarms or to return re-quested data.

8. Monitor the DIAL STATUS signal for completion of the disconnectoperation (STATUS=0). If dialing failed (STATUS = -1, -2 or -3) andyou want to retry, delay for at least 1 second, then go to Step 4.

Slave Line Auto Answer

Slave Line auto-answer allows the slave node to answer automaticallywhen it detects an incoming call from the master node. This feature isenabled by using modem commands.

NOTESee the ‘Master Line Dialing’ sub-section for the necessary set-up atthe Master node, which will dial into this slave.

Set the modem for auto-answer mode and set appropriate disconnectfeature(s) to allow the slave to detect when a master has “hung up” the



line. No other action is required. The slave will now answer anyincoming call and begin communication if it receives messages ad-dressed to it.

The poll period for a slave line with auto answer should be set basedon the expected frequency at which the master will call. When the pollperiod expires (no communications from the master within the speci-fied time), the slave’s transmit queue is flushed and the #LINE.nnnalarm signal is turned on indicating that the line is dead. No alarmmessages will be placed on the slave’s queue while the #LINE.nnnalarm is ON. In order to reset the #LINE.nnn alarm signal, a poll orother message must be received from the node’s master, or it can bereset from the ACCOL program. The modem should be set to default toCOMMAND mode. After the #LINE.nnn alarm is reset, it takes up to15 seconds for any pending alarm report message to be queued fortransmission. Note that if alarms are being received at this node fromnodes below it in a network, and the node is unable to report thealarms because the master does not call it, the node will stop acceptingalarms from its slaves until this condition is cleared. Alarms will notbe discarded, but may not be reported in a timely fashion in such aconfiguration.

Typical set-up for slave line auto answer:

1. Configure the modem for auto answer with an appropriatedisconnect feature.

2. The slave line is now ready to accept incoming calls from amaster.

3. When a call is received the modem will answer.

4. When the master initiates communication by polling the slave ortransmitting a message, the slave will respond.

5. When communication with the master is terminated (the masteror the modem terminates the connection) the slave modem will goback into its idle mode with auto answer enabled.



Master Line Auto Answer

Master Line auto-answer allows the master to answer automaticallywhen it detects an incoming call from a slave node.

NOTESee the section on ‘Slave Line Dialing’ for recommended set-up at theslave node(s) which will dial into this master.

This feature is enabled by using modem commands. The auto-answerat the master can be used to answer a call from a slave node whichwants to report an alarm or has a message to transfer.

Set the modem for auto-answer mode and set appropriate disconnectfeature(s) to allow the master to detect when a slave has “hung up” theline.

IMPORTANT

A common problem when using Master Line Auto-Answer is that theMaster modem will answer the dial from the Slave, but then ‘hang up’when the Master node begins to poll, because it interprets the pollmessage as a command string. To avoid this problem, you must pre-vent polling until Carrier Detect at the Master Modem has beenturned ON.

To do this, configure a Master Poll Control Signal List, as describedunder #NDARRAY in the ‘System Signals’ section of this manual, andmake sure the Data Carrier Detect Enable signal in the list is turnedON. This will prevent poll messages from being sent until the modem’scarrier detect is ON.

To use Master Line Auto Answer, all nodes which might dial in musthave polling enabled in the node polling array (#NDARRAY). This willcause all selected nodes to be polled via the dead list polling technique,i.e. by sending a Node Routing Table/Time Sync message instead of a



standard poll message. Any node which dials in, for which polling isenabled and which remains connected long enough to be polled, willthen receive a NRT/Time Sync and be able to transfer alarms or othermessages to the master.

In addition to using the Data Carrier Detect Enable signal in theMaster Poll Control List, another signal in the list, called the Idle PollEnable signal, should also be turned ON. The Idle Poll Enable allowsadditional polling to occur to any node which has its Dial_Up_Acksignal ON, and can improve system performance.

Note that because polling is enabled for all nodes, but they typicallywill not respond, the #NODE.nnn alarm signals for the affected nodeswill be turned ON. The signals will return to normal when the slavedials in and responds to a poll or message from the master, but willthen return to the alarm state after the line is disconnected and theslave does not respond to subsequent polls. To prevent these alarmsthe user should set the #NODE.nnn signals associated with dial-inslaves to the Alarm Inhibited (AI) state.

Similarly, if all nodes on a port which are enabled for polling aremarked “Dead”, the line will be considered dead and the #LINE.nnnalarm signal will be turned ON. The signal will return to normal whenany slave dials in and responds to a poll or message from the master,but will then return to the alarm state after the line is disconnected ifno slave responds to subsequent polls. To prevent these alarms theuser should set the #LINE.nnn signal for the Master Auto AnswerLine to the Alarm Inhibited (AI) state.

Typical set-up for master line auto-answer:

1. Configure the modem for auto answer with an appropriate disconnectfeature. If not already done, command recognition, data compression,error correction, and auto-baud must be DISABLED.

2. Turn ON the Data Carrier Detect enable signal in the Master Poll



Control Signal List.

3. Turn ON the Idle Poll Enable signal in the Master Poll ControlSignal List.

4. Enable polling in #NDARRAY for all nodes that may dial in.

5. The master line is now ready to accept incoming calls from a slave.

6. When a call is received the modem will answer.

7. When the master transmits a message to the slave which dialed in,the slave will respond. The first message from the master will be aNode Routing Table/Time Sync if the master has a valid one and thenode is in the “Dead List”.

8. When communications with the slave are complete (i.e. the slave’smaximum connect time has elapsed or its transmit queue remainsempty for a specified time) the slave modem will hang up. Themodem at the master will return to idle state with auto answerenabled.



Slave Line Dialing

Slave line dialing allows the user to allocate specific amounts of timefor slave communications when switched network communications arebeing used. When a message (this could be an alarm or any other typeof message) is queued to go up and slave line dialing is enabled, theslave will initiate dialing to its master. Typically, a slave has a singlephone number to dial. Once the slave has established the connection toits master it will maintain the connection until the user specifiedconnect time expires (DIAL ENABLE signal) or until the transmitqueue becomes empty for a period equal to the Empty Transmit QueueDisconnect Time signal, whichever comes first. If the Empty QueueDisconnect Time signal is not configured properly in the EnhancedSlave Dial Control Signal List, a default period of 10 seconds will beused for the Empty Queue Disconnect Time. The line may also beterminated from either side based on modem time limit settings. Anycommunication in progress when the line is terminated will be aborted.

If the slave transmit queue is not empty when the line is disconnectedthe slave will redial (assuming the user-specified controls have notbeen changed). The elapsed time before a redial depends on thefollowing conditions:

1. If there was no communication for this node from the masterduring the previous connection, redial will occur after approxi-mately 4-5 seconds. This could indicate that polling is not en-abled for the node or that the connection time is not long enough.

2. If there was communication with the master, dialing will bereenabled when the slave line poll period expires. The poll periodis restarted every time a message is received for the node, there-fore it was restarted when the last poll or data message wasreceived during the previous connection. See the notes below onthe special use of the poll-period for a dial-up slave port.



CAUTION:If the message queued to go up is an alarm report, themaster device must poll for alarms in order for the reportto be transmitted(see Network 3000 CommunicationsApplication Programmer’s Reference, document# D4052).In a stand-alone system, i.e., one which has no PC-basedMMI software which accepts alarms, polling for alarmswill stop at all levels of the network. A dial-up slave unitwhich is unable to transmit alarms will then dial outcontinuously. For this case the user should put all alarmsignals in nodes below the dial-up slave, as well as thosewithin the dial-up slave into the Alarm Inhibited (AI)state.

NOTE: On-Line AIC and Toolkit do not poll for alarms.

While the slave can establish a connection to its master, it cannotinitiate actual message transfers. It must receive a either a poll ordata message (including NRT/Time Sync), before it can transmitanything to the master.

NOTESee the ‘Master Line Auto Answer’ section, for the necessary set-up atthe master end of the line to ensure that the slave which has dialed inwill be polled.

Typical slave line dialing scenario:

1. Set #DIAL.nnn to select the Enhanced Slave Dial Control List orin the Dial Control Signal List (whichever list you are using).This may be set up during initialization. If you are using theEnhanced Slave Dial Control Signal List, turn ON theDIAL_UP_ACK enable signal, as well.



IMPORTANT

If your firmware supports the Enhanced Slave Dial ControlSignal List, it is strongly recommended that you use it, becausethis offers potentially greater throughput via turning on theDIAL_UP_ACK enable signal.

2. Select the number to dial using the PHONE # SELECT signal inthe Enhanced Slave Dial Control Signal List (or in the DialControl Signal List). Typically a slave line will only dial onenumber, its master, therefore this signal will be set to 1. Thismay be set up during initialization.

3. Set the maximum connect time using the DIAL ENABLE signalin the Enhanced Slave Dial Control Signal List (or in the DialControl Signal List). This may be set up during initialization.The maximum connect time should generally be set from 1.5 to 3times the poll period at the associated master. If that master isservicing many nodes, the maximum connect time may have tobe increased in order to ensure that the slave which dialed in willbe polled while it is on the line. If DIAL_UP_ACK is enabled (viathe Enhanced Slave Dial Control Signal List) and Idle PollEnable is active in the master unit’s Master Poll Control List, thismay not be a problem.

4. Whenever a message is queued to go up, dialing will be initiatedif there has been no communication from the master within thetime defined by the slave line poll period (#POLLPER.nnn). Seethe notes below on the special use of the poll period for a dial-upslave port.

5. The DIAL STATUS signal in the Enhanced Slave Dial ControlSignal List (or Dial Control Signal List) will reflect the status ofthe slave dial controls and operation. Errors -5 through -8 indi-cate that the dial control structures are not properly set up. Nodialing will be initiated.



If DIAL STATUS = -1, -2 or -3, it indicates a dialing failure. Thedial operation will be automatically retried after a minimumdelay of 30 seconds, assuming the other conditions controllingdial-up have not changed. Consecutive dialing failures cause theretry interval to be extended by 30 seconds each time, to amaximum of 120 seconds, plus the node's local address. If dialingfails again after the maximum retry interval, the slave transmitqueue will be flushed and the retry interval reinitialized to 30seconds. When the queue is flushed, alarm messages are re-turned to the Alarm Task which will requeue after a delay.

NOTE:The retry delay for alarm reports is 15 seconds in versionAD.00 and earlier firmware; it is 1 second in AE.00 andlater firmware.

Any alarm message which has not been successfully transmitted viaeither a slave or pseudo slave port is retried, thus no unreportedalarms are ever discarded. Other messages may be discarded and thebuffers will be returned to the communications buffer pool. Thismechanism prevents a node from becoming blocked because all com-munications buffers are queued to a dead line. Note that dialing willrecur following such a failure sequence whenever an unreported alarmor other message is again placed on the queue and dialing remainsenabled.

NOTES:

1. When a slave port is enabled by the user as an auto-dial port i.e.,#DIAL.nnn designates a valid Enhanced Slave Dial Control SignalList or Dial Control Signal List, the poll period has a special use:

1a. Whenever a poll or other message is received from the master,slave dial will be internally disabled and the poll period timerwill be restarted. When the poll period expires, (no communica-tion from the master within the time defined by the poll period),slave dial will be internally enabled and the poll period timer willbe restarted.



This mechanism enables slave dial when there have been nocommunications for a specified length of time, and also preventsthe slave unit from initiating a dial during communicationsinitiated from the master.

This is useful when using auto-dial on both ends of a switchednetwork line with the master dialing the slave to collect specificdata or at specific times, and the slave dialing the master toreport alarms.

1b. The #LINE.nnn alarm signal for a slave auto-dial port will bedisabled, i.e. there will be no line alarm generated when the pollperiod (#POLLPER.nnn) expires.

2. For Peer-to-Peer communications, placing a Master Module in a dial-up slave requires special consideration. In order to queue a MasterModule request directed to Node 0 (node’s master), the node musthave previously received a valid Node Routing Table (NRT). This isnormally supplied via either a request from the slave node or as apolling mechanism to dead nodes. If the master unit does not supplyan NRT in response to the initial request from the dial-up slave, andno subsequent alarm activity occurs in the slave node to cause it todial out, execution of a Master Module will result in a status of -23(NRT not yet initiated) at the Master Module STATUS_2 terminal.The user should test for this status via ACCOL and set an alarmsignal if this error occurs. This will cause the node to dial its masterto report the alarm; the master will poll with an NRT because thisnode is in its “dead list”. Subsequent executions of the Master Modulewill be able to queue requests for transmission to the master node.

3. Issuing Special Commands is subject to the same conditions asactivating a dial operation, i.e. there must be a message queued to goup and the user-specified connect time (DIAL ENABLE) must benon-zero. This may require generation of an alarm in order to havesomething on the transmit queue.

A successful command sequence will then remain “active” until theuser-specified connect time expires. Because no actual communica-tions will occur in connection with a non-dial operation, the same



command will be reissued repeatedly as long as the message remainson the queue and the user controls are not changed.

It is therefore suggested that the user set the DIAL ENABLE signalvalue (connect time) to 0 after a successful command sequence (DIALSTATUS=2) to terminate the active state and prevent repeating thecommand sequence. DIAL ENABLE should be left at 0 until the userwants to issue another command or initiate a dial operation.

The user may want to combine any special commands needed by themodem with the Dial command and telephone number in a singleSpecial Command string (subject to the limit of 32 characters) so thatthe normal Slave line dialing logic works without intervention.

❑❑❑❑❑ Master And Slave Dialing

This is a special case where it is desired to initiate dialing on a particu-lar line from either the Master or Slave nodes, for example to have theMaster dial the slave node(s) periodically to collect particular data, andto have the slave node(s) dial the master if an alarm occurs.

For this to work properly, Master nodes must be set according to the‘Master Line Dialing’ sub-section, and slave nodes must be set accord-ing to the ‘Slave Line Dialing’ sub-section, with the following excep-tions:

The Master node MUST have the Data Carrier Detect Enable signal inthe Master Poll Control Signal List turned ON. This is essential.

All slave nodes which can dial in at any time must always be enabledin #NDARRAY as described in the ‘Master Line Auto-Answer’ sub-section, but with Idle Poll Enable turned on, no port activity will occurunless modem carrier is detected.



When the Data Carrier Detect Enable signal indicates a connection hasbeen made, the #POLLPER.nnn signal must be set to the desiredpolling frequency. Up to 5 seconds may be required for the change ofthe #POLLPER signal to be recognized and for polling to start.

❑ ❑ ❑ ❑ ❑ Pseudo Slave Line Auto Answer

Pseudo Slave Line auto-answer allows the pseudo slave port to answerautomatically when it detects an incoming call from the pseudo masterdevice (PC Workstation). This feature requires configuration usingmodem commands.

Set the modem for auto-answer mode and set appropriate disconnectparameters. No other action is required. The pseudo slave will nowanswer any incoming call and begin communication when the pseudomaster talks to it.

CAUTION:Use of Pseudo Slave Line Dialing or Auto Answer on aPseudo Slave port with Alarms is not recommendedbecause of the effects on the flow of alarm traffic throughthe node when the line is only intermittently active. Forthese cases, it is important that the poll period for thepseudo slave port be set to a reasonable time-out value.When the poll period expires, the #LINE.nnn alarm signalwill be turned ON, any alarm message queued to that portas long as the #LINE.nnn signal remains active. Thisenables the free flow of alarm reports to the networkmaster via the slave port. If the Pseudo Slave Port withAlarms has a poll period with an unreasonably largevalue, or if it is set to zero, transmission of all alarms willstop when an alarm message is queued to the pseudoslave port but the line is not connected.



❑ ❑ ❑ ❑ ❑ Pseudo Slave Line DialingPseudo slave line dialing allows the user to allocate specific amounts oftime for communications on a pseudo slave port when switched net-work communications are being used. Whenever dialing is enabled bythe user (#DIAL.nnn points to a valid dial control signal list and DIALENABLE is not zero), the pseudo slave port will initiate a dial se-quence. Once it has established a connection, it will maintain theconnection until the user- specified connect time expires.

If dialing fails (STATUS = -1, -2, or - 3), dialing will be automaticallyretried after a minimum delay of 30 seconds, assuming the user hasnot disabled dialing. Consecutive dialing failures cause the retryinterval to be extended by 30 seconds each time, to a maximum of 120seconds, plus the node’s local address. Retry will continue at themaximum interval until a successful connection is made, or dialing isdisabled by the user.

Dialing is not conditioned on having messages on the pseudo slave portqueue or on expiration of the poll period as is done for a slave port,therefore it is up to the user to use the DIAL ENABLE signal to onlyenable dialing when it is appropriate, otherwise the pseudo slave portwill continually dial out. The pseudo slave port poll period has itsnormal function. When it expires (no communications from the pseudomaster device within the defined period), the #LINE.nnn alarm signalis turned ON indicating that the line is dead. Any messages on thetransmit queue for the port are flushed. If the port is a Pseudo slavePort with Alarms, no subsequent alarm reports will be queued to theport until the #LINE.nnn signal returns to normal (message receivedfrom the pseudo master device).

In order to transfer messages the pseudo master device which answersthe call must initiate data read/write requests and poll for responsesfrom the pseudo slave port. In order to transfer alarm reports, thepseudo master device must poll for alarms.



❑ Notes on Using the Old Bristol SNM:The Bristol Switched Network Modem (SNM) is NO LONGER AVAIL-ABLE. This Universal Data Systems (UDS) modem performed eitherswitched network or private line communications at either 300 or 1200baud.

Here are some items to be aware of, if you are using this modem:

● ACCOL firmware will automatically detect that you are using thismodem. It is fully compatible with BSAP.

● The Bristol SNM is NOT Hayes-compatible. It does NOT supportthe Hayes command set.

● The Bristol SNM defaults to private line mode when the switchedline auto-dial or auto-answer facilities are not being used. Whenused in this mode, the private line network behaves like amultidrop line.

● The Bristol SNM uses an implied wait for dial tone if not immedi-ately preceded by a W). The default dialing mode of the SNM isTone.

● Do NOT attempt to send Special Commands to a Bristol SNM. Ifa ‘-2’ error appears on the DIAL STATUS signal, it indicates thatyou have sent Special Commands.

● Any unrecognized characters in a phone number string areignored.

● Modem settings are performed via switches or jumpers.

BLANK PAGE


Page Averager-1

AveragerAverager Module

The Averager Module computes the time-average and integral of ananalog or logical input signal. Loads compiled prior to AIC 5.4/AEfirmware use single-precision floating point computations. Newer loadversions perform double-precision floating point computations.

❏ Module TerminalsINPUT Default: None, entry required

Format: Analog or logical signal or con-stant

Input/Output: Input

is the signal that will be averaged. For logical signals, the ON state isequivalent to 1.0, while the OFF state is equivalent to 0.0 for allcalculations.

RESET Default: OFFFormat: Logical signalInput/Output: Input

will reset the Averager. When it is ON, the OUTPUT_1 terminal is setto the INPUT value multiplied by the SPAN value; the OUTPUT_2terminal and the accumulated internal totals are set to zero.* When itis OFF, the module performs the averaging calculations as controlledby the TRACK terminal.

INPUT

SPAN

OUTPUT_2

OUTPUT_1TRACK

TIME

RESET

AVERAGER

* In firmware versions prior to AL.00, RMS02, andPLS00 / PLX00, the OUTPUT_1 terminal was set to 0when the RESET terminal was ON.

Averager


Page Averager-2


The module should be executed once with RESET ON before averag-ing of an input begins.

TRACK Default: ONFormat: Logical signalInput/Output: Input

will inhibit calculations. When it is ON, the module performs averag-ing calculations. When it is OFF, the values on the OUTPUT_1,OUTPUT_2, and TIME terminals are frozen and the module will notperform the calculations.

SPAN Default: 1Format: Analog signal or constantInput/Output: Input

will scale the input into other units if required. For example, an inputrepresenting 500 gallons per minute becomes 500 gallons per secondwhen the span is 1/3600, and the resulting average is gallons persecond.

OUTPUT_1 Default: None, entry is optionalFormat: Analog signalInput/Output: Output

is the average value of the scaled input for periods after the last resetfor which the TRACK signal was ON.

OUTPUT_2 Default: None, entry is optionalFormat: Analog signalInput/Output: Output

is the integral of the scaled input value for periods after the last resetfor which the TRACK signal was ON.


Page Averager-3


TIME Default: None, entry is optionalFormat: Analog signalInput/Output: Output

contains the total time in seconds for which the TRACK signal was ONsince the module was last reset.

❏ Equation

Averaging is done according to the following equation:

tINPUT * SPAN * dt

0OUTPUT= =

t dt

0

NOTE: Beginning with PLS00, PLX00, RMS02, and AL.00 levelfirmware revisions, if the value on the SPAN terminal changes, thenew SPAN value will only be applied to new INPUT values; anyprevious INPUT value which had not yet been averaged will be scaledbased on the previous SPAN value.

cumulative-scaled averageof input at any time (t)where t is in seconds


Page Averager-4


The following figure illustrates the output of an Averager Module witha flow rate signal (gallons-per-second) input that is sampled everysecond for 60 seconds. The top line indicates an input signal levelwhich changes quickly. The second line is a plot of the integral (sum-mation) of input signal values, while the third line is a plot of theintegral of time in seconds. The bottom line is a plot of the output ofthe module, the averaged input value.

10 30 40 60 seconds

2

1

0.5

Input Flow RateGals/Sec

Input dtt

0

dtt

0

Input dtt

0

dtt

0

80

40

60

20

Gals/Sec

2

1.33

1.5

1.33


Page BBTI-1

BBTI Modules (GBBTI, LBBTI) Bristol Teletrans Interface Modules (GBBTI, LBBTI)

The Bristol TeletransTM Interface (BBTI) Modules allow 33XX-seriescontrollers, with the BBTI process I/O board installed, to collect datafrom the Bristol TeletransTM Model 3508 Transmitter.

The data which may be collected from the transmitter includes:

● Differential or Gauge Pressure● Static Pressure● RTD Temperature● Estimated Sensor Temperature● Transmitter Status Information

In addition, the BBTI Modules may be used to control thetransmitter's 4-20 mA current loop output.

Required Hardware and Software

The following controllers may use the BBTI Module to collect datafrom the 3508 transmitter, provided they have the BBTI board in-stalled:

● RTU 3310● DPC 3330● DPC 3335

Each of these 33XX controllers requires ACCOL version 5.8 (or laterrevision level) software, and AJ (or later revision level) firmware tocommunicate with the 3508 transmitter via the BBTI board.

If the 33XX controller does not have the BBTI board, the MasterModule and TCheck Module may be used to collect and process datafrom 3508 transmitters configured as slave nodes on a Master Port,however, significantly more user-defined ACCOL logic is required. Seethe TCheck section, later in this manual, for details.

BBTI Modules (GBBTI, LBBTI)


Page BBTI-2

BBTI Modules (GBBTI, LBBTI)Bristol Teletrans Interface Modules (GBBTI, LBBTI)

Number of Transmitters Connected to the BBTI Board

Each BBTI board contains 8 channels, each of which can communicatewith a separate 3508 transmitter. This allows up to 8 transmitters tocommunicate with a single BBTI board. More than one BBTI boardmay reside in the 33XX controller; allowing one controller to communi-cate with more than 8 transmitters. The practical upper limit on thenumber of transmitters which may be connected to a single 33XXcontroller is strictly determined by whether or not enough RAMmemory exists to support the required modules, signals, and ACCOLlogic, and whether there are enough available slots in the 33XXcontroller.

Each transmitter channel on the BBTI board is configured by a dedi-cated BBTI Module in the ACCOL load. If there are 8 transmittersconnected to the board, 8 such modules must be defined in the load.Two types of modules exist: LBBTI (Local) and GBBTI (Global). All 8modules for a given BBTI board must be the same type; either all localor all global. If there is more than one BBTI board in the 33XX control-ler, there may be a mixture of GBBTI and LBBTI modules in theACCOL load, but those which share a particular BBTI board must stillbe of the same type.

GBBTI (Global) and LBBTI (Local)

The designation 'Global' or 'Local' refers to the Smartkit access methodfor transmitter configuration and calibration. Smartkit may always beconnected directly to the transmitter's current loop for 'Local' access*;'Global' access allows network commmunication with the transmitters.The various advantages of local/global communication are outlinedbelow:

The GBBTI Module must be used if the BBTI process I/O board is tofunction globally, i.e., if Smartkit communication with the attachedtransmitters is to occur via the network. When the global communica-tion method is used, the user must be aware of how the 33XX control-ler containing the BBTI boards fits into the overall communicationsnetwork. In addition, the user must plan the assignment of anyMaster Ports, and be aware of the BBTI process I/O board slot posi-

* 'Local' access requires Smartkit be invoked using the 'Tele-Tap' procedure. See the Smartkit manual, CI-3508-99B.


Page BBTI-3


tions, and transmitter addresses. In this configuration each BBTIboard must be declared as GLOBAL BBTI, and the transmittersconnected to the BBTI board must be defined in the network as slavenodes to the 33XX unit where the BBTI board is installed. GlobalSmartkit communications with an individual transmitter may then beperformed, by referencing the transmitter's node name. (See 'Assign-ing a Transmitter's Node Address,' later in this section, for details onassigning transmitter node addresses. See the NETTOP and NETBCManual, document# D4057, for information on defining nodes in thenetwork.) When the BBTI board functions globally, communicationstatistics for the individual transmitters may also be collected usingthe Nodestatus Module. (See Nodestatus, later in this manual.)

Global communication to GBBTI transmitters is also possible usingthe UOI-based AccuRate Menu System (AMS). In this case, the AMStarget node is the 33XX in which the GLOBAL BBTI board is in-stalled. Communication with a transmitter is activated via the Trans-mitter Calibration Menus. Other functions of AMS are not generallyapplicable when using 3310/3330/3335 controllers.

NOTE

The GBBTI global functions are limited to 3508 transmittermessages; all other message types sent to a transmitter via

this method, including peer-to-peer requests, will result in anerror or timeout.

The LBBTI Module is used if the BBTI process I/O board is config-ured to function locally, i.e. support for global Smartkit communicationto the transmitters is not needed. In this configuration, the BBTIboard must be declared as LOCAL BBTI. This is a simpler configura-tion where the attached transmitters are not configured as nodes inthe network and there are no special transmitter node address re-quirements, however, local connection of Smartkit at the transmitter'scurrent loop is the only method available for performing transmitterconfiguration/calibration. Collection of communication statistics using


Page BBTI-4


the Nodestatus module is also not available when this method ofcommunication is used.

❏ Declaring the BBTI BoardOnce the BBTI board has been properly installed in the 33XX control-ler, it must be declared in the ACCOL load as either a LOCAL BBTIboard, or a GLOBAL BBTI board, depending upon the Smartkitcommunication method which will be used. Chapter 6 of the ACCOL IIInteractive Compiler (AIC) Manual (document# D4042) containsgeneral instructions for using the Process I/O Menu to define process I/O boards. If you are editing the ACCOL source (.ACC) file, rather thanthe AIC, see the ACCOL II Batch Compiler Manual (document#D4055) or the ACCOL Workbench Manual (document# D4051) forinformation on the syntax used when declaring process I/O boards.

Assigning A Transmitter's Node Address

If you are using the LBBTI Module, there are no special requirementsfor assigning transmitter local node addresses. Each local BBTI boardcommunicates with up to eight transmitters using the special nodeaddress of 127, to which all 3508 transmitters respond. Because theBBTI board channels are point-to-point, there is no interferencebetween transmitters.

If you are using the GBBTI Module, each transmitter must be config-ured with a unique local node address, according to the rules discussedbelow. Addresses can range from 1 to 127. If the required address isnot set at the transmitter, the module STATUS terminal will indicate -8, which indicates a bad transmitter address. The local node addressat the transmitter and the local node address defined in the NETTOPfiles for that transmitter must match. Also, the maximum number ofnodes defined for the network level immediately below the 33XX unitmust accomodate the assigned transmitter addresses.


Page BBTI-5


Rules for Assigning Transmitter Local Addresses

If: Then the First TransmitterLocal Address Should Be:

There are no master or exp.master ports in the ACCOL load. 1

There are master or exp. master High Slave Address of the highestports in the ACCOL load. master/exp. master port plus 1

In addition to rules in the table above, the user must be aware ofrestrictions related to board slot order. Each BBTI board configuredfor global operation is assigned a set of 8 consecutive transmitter nodeaddresses for Channels 1 through 8, respectively. The full set of eightaddress values are reserved for that board, even if all the channels arenot used. The lowest numbered slot position which contains a globalBBTI board receives the first set of eight consecutive addresses; thenext lowest numbered slot position which contains a global BBTIboard receives the next eight consecutive addresses, and so on. Themaximum local address allowed is 127. If, because of board placement,certain BBTI board channels correspond to addresses above 127, thoseboard channels are disabled, and the module STATUS terminal willindicate -5, which means no transmitter was detected.

In the figure on the next page, an RTU 3310 controller has four slotsfor process I/O boards. Slot 1 and Slot 3 contain BBTI boards config-ured for global operation. Port A of the controller is configured as aMaster Port, and has two 33XX slave nodes below it. It is anticipatedthat in a future system expansion, an additional three 33XX slavenodes will be added. In addition, there are sixteen channels (eight oneach of the two global BBTI boards) which may each be connected to aTeletransTM Model 3508 transmitter.


Page BBTI-6


Port A -

33XX controllers on the master port( controllers at addresses 3 through 5to be installed in a future expansion )

1 2 3 4 5High Slave Address = 5

These transmitters must have addresses 6 through 13

These transmitters must have addresses 14 through 21

(transmitters at addresses 11, 12, not yet installed)

Master Port

RTU 3310I/O Slots

1 2 3 4

GBBTI

6 7 8 9 10 11 12 13

14 15 16 17 18 19 20 21

GBBTILLAI AO2


Page BBTI-7


In order to leave room for the additional three 33XX slave nodes, thehigh slave address for Port A is set to 5. That means that Channels 1to 8 on the global BBTI board in Slot 1 will communicate with trans-mitters configured with local addresses 6 through 13, respectively, andthe global BBTI board in Slot 3 will communicate with transmittersconfigured with local addresses 14 through 21.

In addition to assigning local addresses properly, it is important tocarefully assign board slots, and addresses to accomodate any futuresystem expansion. Failure to plan for system expansion can result insignificant future re-work.

Planning Ahead For Future Expansion Needs

Master ports and associated slave node addresses should be deter-mined before assigning any transmitter addresses. Positions for futureexpansion should be defined at the port, and set off-line using the#NDARRAY (see System Signals, later in this manual, for informationon #NDARRAY.) Otherwise, if a Master Port or additional slave nodesare added to a 33XX containing global BBTI boards, transmitteraddressing and NETTOP files will be affected.

BBTI boards configured for global operation should be assigned to thelowest slot positions possible, especially if more global BBTI boardsare to be added in the future. In this way, as boards are added, thenext set of 8 transmitter node addresses can be assigned withoutdisturbing the existing configuration. Otherwise, if a new global BBTIboard is added at a lower slot position than an already functioningglobal BBTI board, transmitter addresses must be changed, or theACCOL load's process I/O configuration must be reorganized.


Page BBTI-8


❏❏❏❏❏ Module OperationAt system startup, the GBBTI or LBBTI module enters ConfigurationChecking mode, to check for the presence of the transmitter, as desig-nated by the DEVICE and CHANNEL module terminals. During thismode, the transmitter's configuration is also compared to the moduleterminal entries. During this comparison, questionable data status isset for each of the signals on the DGP, SP, RTDT, and EST outputterminals.* Questionable data status is then cleared for each indi-vidual signal only if no mismatch is detected, and if valid data hasbeen obtained from the transmitters, for that signal. If errors ormismatches are detected, they are reported on the STATUS andCFGSTAT terminals.

The module then enters Normal mode, and data is collected from the3508 transmitter. The collected data is reported on the DGP, SP,RTDT, and EST output terminals. If applicable, the value on theOUTPUT terminal is sent to the transmitter to control its 4-20 mAcurrent loop.

Under normal operating conditions, data should be available from thetransmitter at least once per second. The latest data is processed, andsent to the output terminals (DGP, SP, RTDT, and EST) whenever themodule executes, as determined by the task rate. If transmitter data isnot updated within 5 seconds (12 seconds during start-up and powerfailure recovery) from the last successful module execution, an updatetimeout error is reported on the STATUS terminal, and the lastvalues received from the transmitter will be maintained on the outputterminals, with questionable data status set active for the affectedoutput terminal signals. If the update timeout error persists, the boardis automatically reset, and start-up actions are repeated.

In the event there is a hardware failure reported by the transmitterwhich affects one or more of the process variables (differential/gaugepressure, static pressure, RTD temperature, or estimated sensortemperature) the values which appear on the affected output terminals(DGP, SP, RTDT, or EST) are determined based on the values of othermodule terminals. See 'Substitution Processing', for details.

* Depending upon the transmitter type, and system requirements, some of these output terminals may be unused.


Page BBTI-9


Substitution Processing*

During a transmitter hardware failure, the module output terminalswhich are affected by the failure have their values set based on thevalue of the ERRORCNT terminal signal, and the values of the signalson the substitution terminals (DGPSUB, SPSUB, RTDTSUB, andESTSUB.)

If the ERRORCNT value is set to greater than 0, the last valid valuefrom the transmitter is maintained on the output terminal, and thequestionable data status is set on. If the failure clears before thenumber of module executions defined by the ERRORCNT value, themodule accepts new data from the transmitter, and clears the ques-tionable data status. If the failure is not corrected within the numberof module executions specified by the ERRORCNT value, and a substi-tution signal value is defined on the associated substitution terminal(DGPSUB, SPSUB, RTDTSUB or ESTSUB), the substitution value isreported on the associated output terminal (DGP, SP, RTDT, or EST,)and questionable data status remains on. If no substitution value hasbeen defined, i.e. the substitution terminal is unwired, the last validvalue is maintained, and questionable data status remains on.

If the failure is cleared after the number of module executions definedby ERRORCNT, the value on the output signal, along with the ques-tionable data status, is maintained for one additional module execu-tion. The module then resumes accepting data from the transmitter,and clears the questionable data status, provided no new failures arereported. This means that the module must receive two consecutivevalid values from the transmitter, before it will begin reporting newtransmitter data.

If the ERRORCNT value is set to 0, substitution processing occurs inthe same way as when it is set to greater than 0, except that thesubstitution occurs on the first occurrence of a hardware failure. If,however, the required substitution terminal is unwired, the last validvalue is maintained. As before, two consecutive module executionswithout transmitter-reported failures must occur before new data fromthe transmitter is accepted and reported, and questionable data statusis cleared.

* Only transmitter-reported hardware failures will trigger substitution processing; errors in communications, the BBTI board or BBTI modules DO NOT cause substitution processing.


Page BBTI-10


❏❏❏❏❏ Module Terminals

DEVICECHANNEL

DGPUDGPSUB

SPUSPSUBRTDTU

RTDTSUBESTU

ESTSUBTAG

OUTPUT

MODE

DGPSPRTDTESTTRACKALARMSTATUSCFGSTAT

ERRORCNT

GBBTI /LBBTI

The following terminals apply to both the GBBTI and LBBTI modules:

DEVICE Default: 0 (NULL)Format: ConstantInput/Output: Input

is the slot number in the 33XX controller where the BBTI Process I/OBoard is installed. The number of available slots varies dependingupon which type of controller is used. See the Process I/O section,later in this manual, for information on the number of slots availablein different 33XX controller models.

The slot number is verified with the process I/O defined for theACCOL load to ensure that a BBTI board of the correct configuration,either Global or Local, is specified for the slot.


Page BBTI-11


A value of 0 on this terminal will generate a task runtime error (errorcode of -10 in the #ERARRAY, if the error array is defined) and adevice error on the STATUS terminal (status code of -1).

CHANNEL Default: 0Format: ConstantInput/Output: Input

is the channel number to be used by this module. The entry for thisterminal must be a number from 1 to 8. The combination of values forDEVICE and CHANNEL must be unique for each BBTI module.

A value of 0 on this terminal will generate a task runtime error (errorcode of -120 in the #ERARRAY, if the error array is defined) and achannel error on the STATUS terminal (status code of -10).

MODE Default: None, entry requiredFormat: Analog SignalInput/Output: Input and Output

is a required signal which selects the operating mode of the module,either Normal or Configuration Checking. A value of 0 selects Normaloperating mode and a value of 1 selects Configuration Checking mode.If this terminal is unwired or invalid, an error status of -4 is reportedon the STATUS terminal and all of the module’s process variableoutput signals are held at previous values with questionable datastatus active.

In Normal mode, the module’s process variable output terminals(DGP, SP, RTDT, and EST) are updated using the most recent datafrom the transmitter. Also the value on the OUTPUT terminal is sentto the transmitter to control its current loop output.

In Configuration Checking mode, the transmitter’s engineering unitsand tag name are checked against the signal values on the DGPU,SPU, RTDTU, ESTU, and TAG module terminals. The transmitter’sfirmware revision level is also checked for compatibility with the BBTI


Page BBTI-12


Process I/O Board. Errors detected as a result of this checking arereported on the STATUS and CFGSTAT terminals.

The MODE terminal is set to Normal at the conclusion of the configu-ration check, whether or not errors are detected. The module doesautomatic configuration checking at system startup, after a powerfailure, after 'hot' card replacement (DPC 3335 only), after an updatetimeout on transmitter data, and after a configuration/calibrationchange at the transmitter.

DGP Default: None, entry requiredFormat: Analog SignalInput/Output: Output

is a signal which represents the most recent value of the transmitter’sdifferential or gauge pressure process variable. The engineering unitsare as specified by the DGPU terminal, unless a mismatch or othererror condition is indicated on the STATUS terminal.

The DGP signal is held at its previous value and its questionable datastatus is set active if an update timeout occurs on the transmitterdata. If a configuration/calibration change has occurred at the trans-mitter, the DGP terminal holds its last value and questionable datastatus is set active, pending the result of automatic configurationchecking. If a mismatch is detected between the transmitter’s engi-neering units for this variable and the units indicated by the DGPUterminal, the DGP terminal is updated with the data from the trans-mitter but questionable data status is set active.

In the event the transmitter reports a hardware failure which affectsthis process variable, substitution processing may be activated. See thediscussion on 'Substitution Processing,' earlier in this section, as wellas the DGPSUB and ERRORCNT module terminal descriptions, fordetails.

If the DGP terminal is unwired, a -9 value is reported on the STATUSterminal and the values of the SP, RTDT and EST terminals are heldat previous values with questionable data status set active.


Page BBTI-13


DGPU Default: Transmitter’s DGP unitsFormat: Analog Signal or ConstantInput/Output: Input

is an optional signal used to indicate the engineering units assumedfor the differential or gauge pressure process variable at the transmit-ter. This terminal is used for mismatch detection and is only examinedif the DGP terminal is wired, otherwise, it is ignored. Valid values areshown below:

Engineering Unit Codes for Pressure

0 PSI 4 inches H2O 8 bar1 kilopascal 5 mm Hg 9 g/cm2

2 megapascal 6 inches Hg 10 kg/cm2

3 mm H2O 7 millibar 11 userspecified

If the DGPU terminal is unwired when Configuration Checking isdone, the transmitter’s engineering units are assumed to be correct,and no mismatch condition for this terminal is reported. If thisterminal’s value is invalid, an error is reported, and the DGPU signal’squestionable data status is set. The CFGSTAT terminal string signalis set to indicate that the value is invalid:

DGPU=I

If the value is valid, but does not match the transmitter’s differentialor gauge pressure engineering units, an error is reported, and theCFGSTAT terminal string signal is set to:

DGPU=M; X=nn

where M=Mismatch and nn is the encoded value for engineering unitsreturned from the transmitter.


Page BBTI-14


DGPSUB Default: NoneFormat: Analog Signal or ConstantInput/Output: Input

is an optional signal or value which specifies the value to substituteinto the signal on the DGP terminal when a hardware failure at thetransmitter affects the differential/gauge pressure process variabledata. The substitution of the DGPSUB value during a failure occursonly after the number of module executions specified on theERRORCNT terminal. See 'Substitution Processing,' earlier in thissection for details.

SP Default: NoneFormat: Analog SignalInput/Output: Output

is an optional signal representing the most recent value of thetransmitter’s static pressure variable. The engineering units are asspecified by the SPU terminal, unless a mismatch or other errorcondition is indicated on the STATUS terminal. This signal is held atits previous value and its questionable data status is set active if anupdate timeout occurs on transmitter data. If a configuration/calibra-tion change has occurred at the transmitter, this terminal holds itslast value and questionable data status is set active, pending theresult of automatic configuration checking. If a mismatch is detectedbetween the transmitter’s engineering units for this variable and theunits indicated by the SPU terminal, this terminal is updated with thedata from the transmitter but questionable data status is set active.

In the event the transmitter reports a hardware failure which affectsthis process variable, substitution processing may be activated. See thediscussion on 'Substitution Processing,' earlier in this section, as wellas the SPSUB and ERRORCNT module terminal descriptions, fordetails.

When static pressure readings are not supported by the transmitter, aspecial value is returned by the transmitter, -107. No error status is


Page BBTI-15


returned by the transmitter in this case. Based on the special valuebeing returned and no errors being reported, the user specified substi-tute value (SPSUB terminal) is used. If no substitute is specified, theoutput retains its current value, either 0.0, or the load initializedvalue. In both cases the questionable data status is set active.

It is recommended that this terminal be unwired if static pressurereadings are not supported by the transmitter.

SPU Default: Transmitter’s SP unitsFormat: Analog Signal or ConstantInput/Output: Input

is an optional signal used to indicate the engineering units assumedfor the static pressure variable at the transmitter. This terminal isused for mismatch detection and is only examined if the SP terminal iswired, otherwise it is ignored. Valid values are the same as thoseshown for the DGPU terminal, earlier in this section.

If the terminal is unwired when Configuration Checking is done, thetransmitter’s engineering units are assumed to be correct; no mis-match condition for this terminal is generated. If the value is invalid,an error is reported, and the SPU signal’s questionable data status isset. The CFGSTAT terminal string signal is set to indicate that thevalue is invalid:

SPU= I

If the value is valid but does not match the transmitter’s static pres-sure engineering units, an error is reported, and the CFGSTAT termi-nal string signal is set to:

SPU= M;X= nn

where M=Mismatch and nn is the encoded value for engineering unitsreturned from the transmitter.


Page BBTI-16


SPSUB Default: NoneFormat: Analog Signal or ConstantInput/Output: Input

is an optional signal or value which specifies the value to substituteinto the signal on the SP terminal when a hardware failure at thetransmitter affects the static pressure process variable data. Thesubstitution of the SPSUB value during a failure occurs only after thenumber of module executions specified on the ERRORCNT terminal.See 'Substitution Processing,' earlier in this section for details.

RTDT Default: NoneFormat: Analog SignalInput/Output: Output

is an optional signal representing the most recent value of thetransmitter’s RTD temperature variable. The engineering units are asspecified by the RTDTU terminal, unless a mismatch or other errorcondition is indicated on the STATUS terminal. This signal is held atits previous value and its questionable data status is set active if anupdate timeout occurs on transmitter data. If a configuration/calibra-tion change has occurred at the transmitter, this terminal holds itslast value and questionable data status is set active, pending result ofthe automatic configuration checking. If a mismatch is detectedbetween the transmitter’s engineering units for this variable and theunits indicated by the RTDTU terminal, this terminal is updated withthe data from the transmitter, but questionable data status is setactive.

In the event the transmitter reports a hardware failure which affectsthis process variable, substitution processing may be activated. See thediscussion on 'Substitution Processing,' earlier in this section, as wellas the RTDTSUB and ERRORCNT module terminal descriptions, fordetails.

When RTDT readings are not supported by the transmitter, a specialvalue is returned, +10048, however no error status is indicated. Basedon the special value being returned, and no errors being reported, the


Page BBTI-17


user specified substitute value (RTDTSUB terminal) is used. If nosubstitute is specified, the output retains its current value (either 0.0or the load-initialized value). In both cases the questionable datastatus is set active.

It is recommended that this terminal be unwired if RTD temperaturereadings are not supported by the transmitter.

RTDTU Default: Transmitter’s RTDT unitsFormat: Logical SignalInput/Output: Input

is an optional signal used to indicate the engineering units assumedfor the RTD temperature process variable at the transmitter. Thisterminal is used for mismatch detection and is only examined if theRTDT terminal is wired, otherwise it is ignored. Valid values are:

OFF = degrees Celsius or CentigradeON = degrees Fahrenheit

If this terminal is unwired when Configuration Checking is done, thetransmitter’s engineering units are assumed to be correct; no mis-match condition for this terminal is generated. If this terminal’s valuedoes not match the transmitter’s engineering units, an error is re-ported, and the CFGSTAT terminal string signal is set to:

RTDTU=M;X=n

where M=Mismatch and n is the state returned from the transmitter,0 for degrees Celsius or 1 for degrees Fahrenheit.


Page BBTI-18


RTDTSUB Default: NoneFormat: Analog Signal or ConstantInput/Output: Input

is an optional signal or value which specifies the value to substituteinto the signal on the RTDT terminal when a hardware failure at thetransmitter affects the RTD temperature process variable data. Thesubstitution of the RTDTSUB value during a failure occurs only afterthe number of module executions specified on the ERRORCNT termi-nal. See 'Substitution Processing,' earlier in this section for details.

EST Default: NoneFormat: Analog SignalInput/Output: Output

is an optional signal representing the most recent value of thetransmitter’s estimated sensor temperature process variable. Theengineering units are as specified by the ESTU terminal, unless amismatch or other error condition is indicated on the STATUS termi-nal. This signal is held at its previous value and its questionable datastatus is set active if an update timeout occurs on transmitter data. Ifa configuration/calibration change has occurred at the transmitter, thisterminal holds its last value and questionable data status is set active,pending result of the automatic configuration checking. If a mismatchis detected between the transmitter’s engineering units for this vari-able and the units indicated by the ESTU terminal, this terminal isupdated with the data from the transmitter but questionable datastatus is set active.

In the event the transmitter reports a hardware failure which affectsthis process variable, substitution processing may be activated. See thediscussion on 'Substitution Processing,' earlier in this section, as wellas the ESTSUB and ERRORCNT module terminal descriptions, fordetails.


Page BBTI-19


ESTU Default: Transmitter’s EST unitsFormat: Logical SignalInput/Output: Input

is an optional signal used to indicate the engineering units assumedfor the estimated sensor temperature process variable at the transmit-ter. This terminal is used for mismatch detection and is only examinedif the EST terminal is wired, otherwise it is ignored. Valid values are:

OFF = degrees Celsius or Centigrade ON = degrees Fahrenheit

If this terminal is unwired when Configuration Checking is done, thetransmitter’s engineering units are assumed to be correct; no mis-match condition for this terminal is generated. If this terminal’s valuedoes not match the transmitter’s engineering units, an error is re-ported and the CFGSTAT terminal string signal is set to:

ESTU=M;X=n

where M=Mismatch and n is the state returned from the transmitter,0 for degrees Celsius or 1 for degrees Fahrenheit.

ESTSUB Default: NoneFormat: Analog Signal or ConstantInput/Output: Input

is an optional signal or value which specifies the value to substituteinto the signal on the EST terminal when a hardware failure at thetransmitter affects the estimated sensor temperature process variabledata. The substitution of the ESTSUB value during a failure occursonly after the number of module executions specified on theERRORCNT terminal. See 'Substitution Processing,' earlier in thissection for details.


Page BBTI-20


TAG Default: NoneFormat: String SignalInput/Output: Input

is an optional 8-character string signal used to indicate the 3508transmitter’s tag name. This signal is used for mismatch detection.

If this terminal is unwired when Configuration Checking is done, thetransmitter’s tag name is assumed to be correct; no mismatch condi-tion for this terminal is generated. If the value does not match thetransmitter’s tag name, an error is reported and the CFGSTAT termi-nal string signal is set to:

TAG=M;X=string

where M=Mismatch and string is the tag name returned from thetransmitter.

OUTPUT Default: NoneFormat: Analog Signal or ConstantInput/Output: Input

is an optional signal used to specify the current loop control value forthe transmitter’s 4 to 20 mA loop current. The output is specified as apercent-of-scale thus the valid range is 0 through 100. If the value isout of range low, the default value of 0 percent-of-scale is sent to thetransmitter. Likewise, if the value is over range, a maximum 100percent-of-scale value is sent. If the terminal is unwired, no outputdata is sent to the transmitter.

The mode at the transmitter, configured via Smartkit, must be set forexternal control in order for the output value to have effect. If thetransmitter is not configured for external output control, the TRACKsignal, if wired, is set ON.


Page BBTI-21


TRACK Default: NoneFormat: Logical SignalInput/Output: Output

is an optional signal that is turned ON by the module whenever theOUTPUT signal is out of range, that is, below 0 percent-of-scale orabove 100 percent-of-scale. The signal is turned OFF when the value isin range. This signal is also turned ON when the module attempts tosend loop control data to the transmitter, and that feature is disabledin the transmitter.

ALARM Default: NoneFormat: Logical SignalInput/Output: Output

is an optional signal used to indicate that a configuration or calibrationchange has occurred at the transmitter which may affect correctinterpretation of the transmitter’s process variable data. For example,the differential pressure engineering units may have been changedfrom inches H2O to PSI, causing the transmitter to use different spanand zero parameters when calculating the pressure value returned.This may in turn affect correct usage of the differential pressure valuein the ACCOL load program.

Automatic configuration checking is activated when this change at thetransmitter is reported. Any mismatch of the transmitter’s configura-tion parameters when compared to those specified on the moduleterminals will be reported. The ALARM signal will remain ON, evenwhen configuration and/or calibration have been completed, andnormal processing has resumed. User-defined logic in the ACCOLload, or operator action, is required to turn the ALARM signal OFF.


is an optional signal which will be set to indicate the result of module


Page BBTI-22


execution. If there are multiple errors, the most severe error will beindicated. A list of status codes is shown below, see the CFGSTATterminal description for the corresponding messages.

Code Description

-10 CHANNEL invalid. The value on the CHANNELterminal must range from 1 to 8.

-9 DGP terminal is unwired. -8 Transmitter address wrong (GBBTI only.) The node

address is incorrectly defined. See 'Assigning aTransmitter's Node Address,' earlier in this section.

-7 Incompatible transmitter firmware version. (Must beversion 'F' or higher.)

-6 Smartkit locally attached. Communication betweenthe BBTI board and the 3508 transmitter must besuspended when a PC running the Smartkit programis connected locally to the current loop of the trans-mitter. Note: When connecting Smartkit to a 3508transmitter connected to a BBTI board, the special'Tele-Tap' procedure should be used to invokeSmarkit on the PC to provide for proper detection ofSmartkit by the BBTI board. See the Smartkitmanual CI-3508-99B.

-5 No transmitter detected. The transmitter has beenincorrectly connected, or is disconnected. This codemay also appear if no valid address is available forthe GBBTI channel, because more than 127 nodeshave been defined.

-4 MODE configuration error. The MODE terminalmust be wired, and the value must be 0 or 1.

-3 Update timeout. The board memory has not beenupdated with transmitter data in the last 5 seconds.(Note: This 5 second limit is extended to 12 secondsduring load initialization, power fail recovery, andhot card replacement.)

-2 (Reserved for future use.) -1 DEVICE error. This can be caused by no board being

defined on the DEVICE terminal, no board, or


Page BBTI-23


Code Description (continued)incorrect board type in the 33XX controller’s I/O slot,or an incompatible firmware revision in the BBTIboard.

0 No errors detected. 1 Configuration Checking active. The DGPU, SPU,

RTDTU, ESTU, and TAG terminals of the BBTImodule are checked against the correspondingtransmitter values. Transmitter firmware compatibil-ity with the BBTI board is also checked.

2 Module units invalid or mismatch detected. The unitcode defined on the DGPU, SPU, RTDTU, or ESTUterminal does not match the corresponding transmit-ter unit value, or the TAG name doesn't match thetag defined at the transmitter. The CFGSTATterminal contains more detailed information on thiscondition.

3 One or more process variables is being held at lastvalue, or the substitution value is being used, be-cause of a transmitter-reported hardware failure. See'Module Operation,' earlier in this section, as well asthe DGPSUB, SPSUB, RTDTSUB, ESTSUB, andERRORCNT terminal descriptions.

4 Request received, but has not completed processingor cannot be processed yet. Will be processed whenresources are available. The module must be re-executed at least once to complete.

CFGSTAT Default: NoneFormat: String SignalInput/Output: Output

is an optional string signal used to provide additional informationabout status or errors shown on the STATUS terminal. For example, amajor error such as a bad transmitter address (-8 on the STATUSterminal) will result in the message 'XMIT Address Wrong' beingstored in the CFGSTAT string signal. If there are no errors, theCFGSTAT signal is set to the 'null' string. If there are no major errors,


Page BBTI-24


however, there are mismatches between module and transmitter unitvalues or tag names, or invalid entries on certain terminals, this isreported in the CFGSTAT string. The text string lists the names of themodule terminals with a code indicating whether the terminal value isinvalid or mismatched.

Code: Meaning:

I InvalidM Mismatched with the transmitter value.

The corresponding value from the transmitter is indicated as X=nn,preceded by a semicolon.

These conditions are listed in module terminal order. Multiple condi-tions are separated by spaces. The length of this string signal may bedefined at up to 64 characters, and the signal will hold as manyconditions as will fit in its defined length.

DGPU=I;X=10 SPU=M;X=10 RTDTU=M;X=1 ESTU=M;X=1TAG=M;X=XMTR_024

The above string indicates that the DGPU terminal has an invalidvalue and that the transmitter units are kg/cm2; that the SPU termi-nal value does not match the transmitter units which are kg/cm2; thatthe RTDTU terminal does not match the transmitter units which arein degrees Fahrenheit; and that the ESTU terminal does not matchthe transmitter units which are in degrees Fahrenheit. Also the TAGterminal value does not match the transmitter tag which isXMTR_024.

ERRORCNT Default: 5.0Format: Analog Signal or ConstantInput/Output: Input

is an optional signal or value which specifies the number of consecu-tive module executions that are allowed to occur with a transmitter-reported error status before substitution values are used to replace


Page BBTI-25


process variable values sent by the transmitter. Until the ERRORCNTvalue expires, or the transmitter error is cleared, the affected processvariable output(s) are held at their last valid value and questionabledata status is set. See 'Module Operation' and the DGPSUB, SPSUB,RTDTSUB, and ESTSUB terminal descriptions, earlier in this section.

IMPORTANT

It is recommended that the ERRORCNT value never begreater than 20. This ensures that for a persistent trans-mitter hardware failure, the affected data from thetransmitter will not be used until two consecutive goodreadings are obtained, thus reducing any effect of thefailure on the transmitter's internal averaging.

Only hardware failures reported by the transmitter which affect thetransmitter's data will cause the ERRORCNT and substitution termi-nals to be used. For errors associated with the GBBTI or LBBTImodule, the BBTI board, or transmitter communications, no substitu-tions will take place.

BLANK PAGE

BreakBreak Statement


Page Break-1

The Break Command allows unconditional exit from a FOR loop. It isequivalent to a GOTO command in that it transfer control to the linefollowing the terminating ENDFOR statement.

SyntaxBREAK

Example

210 FOR 2., 14., 3., CT.111212 IF (A==B)214 BREAK216 ENDIF218 CALCULATOR220 ANIN222 ENDFOR

Note that spaces are required after conditional commands for entriesmade on the Task Structure Menu.

Break

BLANK PAGE

ACCOL II Reference Manual Page Buffers-1

Buffers

Buffers are pre-allocated blocks of memory which are reserved for spe-cific purposes. Two types of buffers are user-configurable: I/O Buffers,and Alarm Timestamp Buffers.

I/O BuffersIf an ACCOL load will be performing significant communication duties,additional I/O buffers should be allocated either on the CommunicationsConfiguration Menu in AIC, or in the *COMMUNICATIONS section ofthe ACCOL source file.

The system automatically allocates a certain number of I/O buffers basedon the configuration of the I/O ports. Additional I/O buffers can be as-signed by the ACCOL programmer if the node is expected to perform alarge number of communications activities. This would be true with a top-level node, for example.

When load configuration is complete, it is recommended that additionalI/O buffers be assigned based on the amount of RAM memory thatremains. Assigning more buffers than is needed will not degrade systemperformance. However, should you wish to modify this load in the futureand find there is not enough memory space for the modification, you canalways decrease the number of I/O buffers.

Each additional I/O buffer requires 275 bytes of base RAM memory (orsimply RAM if this is a Protected Mode controller). If you are using theAIC, you can determine the amount of extra buffers that can be accom-modated by checking the amount of spare memory shown on the PROM/RAM Totals Display. If you are using ACCOL Workbench, the amount ofspare memory can be determined by using the File Documentationfeature, and looking at the FREE MEMORY number in the TargetMemory Usage section of the LST file.

When adding buffers, be sure to leave some spare RAM memory toaccomodate on-line edits, and future load modifications.

If no additional I/O buffers are specified, the number of I/O buffers willbe equal to the number automatically assigned by the system.

Buffers

ACCOL II Reference ManualPage Buffers-2

Buffers

Alarm Time Stamp BuffersWhen a signal goes into alarm, the time of the occurrence is saved in an 8byte alarm time stamp buffer. Between 4 and 32 alarm time stampbuffers are generated automatically when an ACCOL load is created;approximately 1 for every 4 alarm signals defined in the load. Eachbuffer, however, can only hold a single time stamp for a single alarmsignal. If more than one fourth of the alarm signals in the load go into analarm state within a short period of time, none of the alarm messagesthemselves will be lost, but some of their time stamps will be reported asquestionable because not enough buffers were available to hold the timestamps.

Whenever the processing of an alarm message is completed (so it can bereported to the operator), a buffer is made available. The frequency atwhich this processing occurs is user-configurable through the#ALARM.LIM system signal.*

If it is possible that more than one fourth of the alarm signals in yourload might go into an alarm state within a short period of time you maychoose to increase the number of alarm time stamp buffers by 1 bufferper additional alarm.

If the frequency of alarm processing is slow, you may also want to in-crease the number of alarm time stamp buffers, so that enough areavailable to compensate for the slow frequency.

Adding Alarm Time Stamp Buffers

Buffers are added by specifying the number of additional buffers eitheron the Communications Configuration Menu in AIC, or in the *COMMU-NICATIONS section, if you are using ACCOL Workbench or the ACCOLBatch Compiler (ABC). A maximum of 255 alarm time stamp buffers maybe defined. NOTE: The number of Alarm Time Stamp Buffers is user-configurable only if you have ACCOL Tools software Version 5.41 (orlater).

* This system signal is available beginning with ACCOL Tools software version 5.6.

Calculator Module

Calculator

ACCOL II Reference ManualPage Calculator-1

The Calculator Module executes analog and logical equations usingACCOL signals or values as operands.

❏ Single Equation StatementsA single-line equation may be entered in a Calculator Module asshown in the following example.

53 CALCULATOR A101=B+C-.35

The name 'CALCULATOR' must be separated from the equation byone space. If this space is not provided, the statement is invalid. Theterms and operators of the equation do not require separation.

In the sample equation above, A101, B and C are analog signals, while.35 is an analog value.

❏ Block Equation StatementsWhile the above single-line Calculator Module statement is useful forentering a single equation, it cannot be used for a long series ofequations. For these situations, the Calculator statement may beentered on a task line, without an equation on the same line, andequations are entered on lines below it (or on the Calculator Modulemenu, if you are using AIC).

Inputs Outputs

Calculator


Page Calculator-2

CalculatorCalculator Module

For example, on task line 111, a calculator statement appears:

111 CALCULATOR

A block of equations, with line numbers independent of those for thetask, are entered below the calculator statement (or on the CalculatorModule Menu, if you are using the AIC):

10 GBY.23 = N.101+N.102-(L.312+L.313)*.998+(K11/Q60+:COS(N.103))+N.105

20 GBX.101=A*B/D*(E+F)*(-G+H)*(K(L/M))*258-P-Q

Since the equation on line 10 is too large to be contained on one line,an extension line was created. If you are using the AIC, this is done bypressing the [RETURN] key. If you are using the ABC or ACCOLWorkbench, this is done by adding an '@' symbol to the end of the linewhich is being extended. Except for one exception, the terms of theequation can be broken off at any point without affecting any of theoperations.* Up to 8 lines may be used for a single equation.

The equation on line 20 fits on one line and does not need an extensionline.

Possible causes of errors in Calculators include signal incompatibility,misplaced operands, and unbalanced parenthesis.

❏ Destination and Expression FieldsAn equation is divided into a destination field and an expression field.That part of a statement to the left of the equal sign is the destinationfield, while that to the right of the sign is the expression field. Bothfields are illustrated in the following sample equation:

*String constants should generally be limited to a single line. See the discussion on string constants, later in this section, for details.

Calculator Module

Calculator


PRESS.102.OUT = A * B - (C+D)/E

destination field expression field(5 operands)

(spaces inserted for clarity only)

When this statement is executed, the operations indicated in theexpression field are performed and the result is then placed in thelocation identified in the destination field.

Analog Constants

Analog values can be expressed as a floating point decimal or withan exponential component. The letter “E” appearing after a wholenumber identifies the exponential component.

Exponential Values Equivalent Syntax

20 X 102 20E26 X 10-6 6E-61 X 102 1E+23 X 103 3E3

Logical Constants

The states of a logical signal are represented as ON and OFF. Alogical signal in an equation cannot have its status defined as anumerical constant (1 or 0). There are two logical system signalswhich may be used as logical constants, #ON, and #OFF.

String Constants

In AIC, a string constant within a control statement, CalculatorModule equation, or Format block consists of up to 64 characters oftext, enclosed within double quotes. For example:


Page Calculator-4


"THIS STRING CONSTANT IS 37 CHARACTERS"

is a valid string constant. Note: Initial string values for stringsignals are in single quotes ' ' within the ACCOL source file (.ACC).Therefore, if you are using the ACCOL Batch Compiler (ABC) orACCOL Workbench, single quotes should be used.

Note: In general, users should avoid using the '@' continuationcharacter within a string constant. Using this character results inthe insertion of one or more blank characters in the resultingstring.

Order of Operations & Nesting

All terms of an equation are executed in standard order of opera-tions starting at the left, with multiplication and division per-formed first, followed by addition and subtraction. Any termscontained within parenthesis are performed first; those termswithin parenthesis follow the same rules of operation as thoseoutside the group. For expressions having several parenthesisnested within another, the expression contained in the innermostgroup will be performed first, then those in the next innermostgroup will be performed next. Expressions may be nested up toeight deep.

Note that all nested groups must be balanced with an equal num-ber of parenthesis on each side of the expression. If the parenthesisare out of balance, an error message will appear on the screenwhen an entry is attempted. An example of a Calculator equationwith multiple nesting is as follows:

CALCULATOR T=(G+F)*(E*(D-C+(A/B)))

❏ Data Array Expressions

Data arrays function as cross-reference tables where data may be readfrom, or written to a specific table location. Arrays are identified by

Calculator Module

Calculator


number (1 through 255). A maximum of 255 analog arrays and 255logical arrays may be assigned within the available memory space.Arrays are common to all tasks of a load.

A data array expression contains the elements shown below. The firstelement of the expression specifies the type of array (analog or logi-cal), while the second element identifies the array by number. Thecolumn and row numbers are contained in braces, with the commaacting as the separator.

The example below is a two dimensional data array.

#ADATA 7 [ 10, 12 ]

Type of array Row number#ADATA = Analog Column number#LDATA = Digital

Identifier number (whole number from 1 to 255 or analog signalname whose value ranges from 1 to 255)

An expression for a single-dimensional array will have only a rownumber entry as follows:

#LDATA 19[28]

Data arrays are used in Calculator equations. In the sample below,the data array is placed in the expression field. Used in this applica-tion, the array is typically a read only type whereby the value con-tained in column 3, row 5 of the array is placed into the destination,signal F.

CALCULATOR F=#ADATA 10[3,5]

Data may be written into a read/write array using the sample type ofequation shown below. In this equation, the result of the expressionG*H-K is written into column 4, row 22 of the array.

CALCULATOR #ADATA 5[4,22]=G*H-K

The column and/or row indices of a data array can also be an analog


Page Calculator-6


signal. In the example below, signal FLOW.19 serves as the rowindices for a read/write array.

CALCULATOR #ADATA 2[6,FLOW.19]

A data array expression can also make reference to another dataarray. In these situations, data arrays may be nested up to four levels.The following example illustrates this point.

CALCULATOR B=#ADATA 25[4,(GB*[#ADATA 16[5,5])]

Array indices can be any valid analog constant, or valid analog expres-sion that evaluates to an analog result. When an array index does notevaluate to an exact integer, the truncated value will be used to indexthe array. If an indexed value is outside the range of the array, thevalue returned will be zero. For indices to be valid, they must be inthe range of 1 to n, where n is the declared size of the dimension. A“bound” violation will give an error and return a value of 0.0.

When numbers are applied to indices of analog data arrays thatexceed the size of the data field, the spillover portion will be automati-cally truncated.

❏ Types of Operators

A statement can employ several types of operators in the expressionfield. They may be dyadic, monadic, cast and single-signal operators.This section defines each operator category.

Dyadic Operators

Dyadic operators perform arithmetic and boolean operations. A listof dyadic operators is given in the following table.

The “Operand Type” column specifies what type of operand (analogor logical) is necessary to obtain the proper resultant in the “ResultType” column. Improper operand types will produce error messages

Calculator Module

Calculator


when an entry is attempted in AIC, or when a build operation isattempted in ACCOL Workbench.

The “Priority” column denotes the order of priority that one opera-tor sign has over another when solving an equation. (1 is thehighest priority.) Care should be taken to properly position opera-tors in an expression and to set off parts of an expression withparenthesis where required.

The equal sign is used as an assignment operator. Data entered tothe right of the sign represents the expression field, while that tothe left represents the destination field.

The dyadic operators >, <, >=, <=, != and == are employed to checkthe conditions stated in the table. The operand to the right of theoperator is checked against the operand to the left of the operator.Expressions using these operators are always a part of a controlstatement. All operands contained in an expression with theseoperators will be analog signals, while the result of the completecontrol statement will be a logical condition (ON or OFF).

Dyadic Operators

Result Operand ResultOperator Function Type Type Priority

+ Add Analog Analog 4- Subtract Analog Analog 4* Multiply Analog Analog 3/ Divide Analog Analog 3** Power Analog Analog 2 *> Greater than Analog Logical 5< Less than Analog Logical 5= Put result into destination Any Operand

Type**

* Only positive numbers can be raised to a power. (For example, A = -1**2 is not acceptable.)Entering a negative value will result in a run-time error and the output value of the equation(A, in our example) will not be updated.

** Result may require casting to match type of the destination. See 'Cast Operators' later in this section.


Page Calculator-8


Dyadic Operators (continued)

== Equal to Analog Logical 5(equivalency test)

:EQ: Equal to String Logical(parity check)

!= Not equal Analog Logical 5:NE: Not equal String Logical> = Greater than Analog Logical 5

or equal to< = Less than Analog Logical 5

or equal to& AND Logical Logical 6^ EXCL OR Logical Logical 7| INCL OR Logical Logical 8:CON: Concatenation String String

Monadic OperatorsOperand Result

Operator Function Type Type Priority - Negative Analog Analog 1+ Positive Analog Analog 1~ Logical NOT Logical Logical 1:INT( ) Integer truncated Analog Analog:ABS( ) Absolute value Analog Analog:LOG( ) Log Base (e) Analog Analog:EXP( ) Exponential (e) Analog Analog:SQR( ) Square root Analog* Analog:RND( ) Integer rounded*** Analog Analog:SIN( ) Sine Analog** Analog:COS( ) Cosine Analog** Analog:TAN( ) Tangent Analog** Analog

* Positive values only should be used with the SQR( ) operator. Attempting to take thesquare root of a negative value will result in a run-time error.** Operands used with the :SIN( ), :COS( ), and :TAN( ) operators must be in radians.***Values greater than or equal to .5 are rounded up, other values are rounded down.

Calculator Module

Calculator


Monadic Operators

Monadic operators are shown in the table above. The monadicoperators assign positive or negative casts to an analog signal,value or expression; they can also assign a NOT sign to a logicalsignal or expression. Other monadic operators can be applied to ananalog value or expression to perform logs, square roots, expo-nents, etc.

In the sample analog equation shown below, operands B and C,contained in parenthesis, are assigned monadic operators.

CALCULATOR A=(-B)+(-C)

A sample logical equation using the NOT sign (tilde) is expressedas follows:

CALCULATOR R=~(S|T&U)

An exponential used in an equation uses the form, :EXP( ). Thesignal/s or value to be used as the exponential is placed in paren-thesis as follows:

CALCULATOR L=:EXP(A+B)CALCULATOR BX.112=:EXP(7)

The square root and round operators take the forms, :SQR( ) and:RND( ). Some samples are as follows:

CALCULATOR L=M+:SQR(A+B)CALCULATOR J=H*:RND(A)*:INT(P*K)/T

Both string signals and string constants can be concatenated usingthe :CON: operator. The text of the signal specified to the right ofthe operator will be appended to the text of the signal specified tothe left. The resulting string will be stored in the destinationsignal, limited by the defined maximum string length of thatsignal. An example of concatenating the string "ERROR NO. " and


Page Calculator-10


the string "01" is shown below:

String signal: STRING.01 Length: 2 Text: "01"String signal: STRING.ERR Length: 10 Text: "ERROR NO. "String signal: STAT.TXT Length: 64

Calculator Statement:

CALCULATOR STAT.TXT=STRING.ERR:CON:STRING.01

After executing the calculator, the resulting STAT.TXT string willbe:

"ERROR NO. 01"

Cast Operators

A Calculator equation can contain analog and logical operands orcharacter strings. Normally, these operands would not be inter-mixed in the same statement. However, for some applications itmay be desirable to cast the result of an analog expression as alogical output, or cast the result of a logical expression as an analogoutput, etc. For these situations, the ACCOL programmer canassign a special “cast” operator to change the type of the expres-sion. The “cast” operators are defined in the table below.

Cast Operators

Operand ResultSign Function Type Type

:A( ) Analog Cast Any Analog:L( ) Logical Cast Any Logical:S( ) String Any String

The results of changing the cast of an expression follow these rules:

Calculator Module

Calculator


Analog to Logical - If the analog input is greater than 0.0, thelogical output will be ON. If the analog input becomes less than,or equal to 0.0, the logical output will be OFF.

Logical to Analog - If the logical input is OFF, the analog outputwill be 0.0. If the logical input is ON, the analog output will be1.0.

Analog to String - Not a valid conversion; the result will always bean empty string.

String to Analog - The result will always be the number of charac-ters in a string.

Logical to String - Not a valid conversion; the result will always bean empty string.

String to Logical - The logical output will be OFF if the stringcontains no characters (zero). If the string contains characters,the result will be ON.

Samples of Calculator equations with cast expressions are shownbelow in proper syntax. The part of the expression to the left of theequal sign (=) identifies the destination of the resultant, while thatpart in parenthesis is “casted.”

Sample Analog Cast Expressions

CALCULATOR C=:A(B|A)CALCULATOR F501=:A((A&C)|~(D&E))

Sample Logical Cast Expressions

CALCULATOR A=:L(B+C)CALCULATOR G110=:L((LM5*RM2)/(X+Z))


Page Calculator-12


Sample String Cast Expressions

CALCULATOR TB=:S(RB+VB) {TB = empty string}CALCULATOR RT11=:S(H|J) {RT11 = empty string}

The expressions above are basic examples. Each expression may alsouse single-signal operators, data array references, constants, monadicoperators, dyadic operators and parentheses.

Single Signal Operators

Single Signal Operators are used to read or write the status of asignal. The operators shown in the following table may be em-ployed in the expression or destination fields of a statement.However, not all operators can be used in the destination field.

When used in the expression field, single-signal operators can readthe alarm status, inhibit status, or questionable data status of thesignal, as defined by the selected operator. When used in thedestination field, they can set or write the questionable data statusor the alarm acknowledge or inhibit status.

The table lists the mnemonic names of the operators, their func-tions, the type of results, and signal types. The “Operand Types”column indicates that all resulting operands are logical. The“Signal Type” column indicates the signal types for which theoperator is valid.

Single-Signal operator mnemonics are set off by colons and fol-lowed by the signal name. It is important to remember that onlycertain operators can be used in the destination field. The usableoperators for destination fields are as follows:

:CI: :MI: :AI: :AK: :HK: :LK: :HHK: :LLK: :Q:

Calculator Module

Calculator


Single-Signal Operators

Output InputMnemonic Function Operand Signal Type1.

:CI: Control Inhibit Logical A, AA, L, LA, S:MI: Manual Inhibit Logical A, AA, L, LA, S:AI: Alarm Inhibit Logical AA, LA:AS: Alarm Set Logical AA, LA:HS: High Alarm Set Logical AA:HHS: High/High Alarm Set Logical AA:LS: Low Alarm Set Logical AA:LLS: Low/Low Alarm Set Logical AA:AK: Alarm Acknowledge2 Logical LA:HK: High Alarm Ackn.2 Logical AA:HHK: High/High Alarm Ackn.2 Logical AA:LK: Low Alarm Ackn.2 Logical AA:LLK: Low/Low Alarm Ackn.2 Logical AA:Q: Questionable Data Bit Logical A, AA

The following statement contains a single-signal operator in theexpression field. If A1 is ON or B1 is ON or F501.PT is in the highalarm state, then the logical signal T11.02 is set ON.

T11.02 = A1 | B1 | :HS : F501.PT

DestinationOperand (signal)

Operand (signal)Single Signal Operator (SSO)

SSO Signal

1. Definition of Signal Types:A = Analog SignalAA = Analog Alarm SignalL = Logical SignalLA = Logical Alarm SignalS = String Signal

2. ON indicates that the alarm status is notacknowledged.


Page Calculator-14


A sample statement containing single-signal operators in both thedestination and expression fields is shown below. When the statementexecutes, the control inhibit status for signal F101 will be set if logicalsignal F104 is ON and analog signal F501.PT is control inhibited.

:CI: F101 = F104 & :CI: F501.PT

Single SignalDestination

Operand (signal)SSO Signal (read status)Single Signal Operator (SSO)

The sample Calculator Module statement shown below will test for anunacknowledged alarm condition and then acknowledge the alarm.

:IF(:AK:LALM.01):AK:LALM.01=#OFF:ENDIF

❏ Control Statements

Control statements provide conditional, unconditional, delay andinterrupt functions. The legal control commands for the CalculatorModule are IF, ENDIF, ELSE, and ELSEIF. These commands mustalways be preceded by a colon. As an example,

:IF :ELSE:ENDIF :ELSEIF

FOR, GOTO and all WAIT statements CANNOT be used in Calcula-tors. Entering these statements in AIC will cause the message 'Ex-pression syntax error: invalid token' to be generated. Entering thesestatements in ACCOL Workbench will generate errors during a buildoperation.

Calculator Module

Calculator


❏ Comment StatementsA comment statement is a message that appears in a Task, but is notan executable command. Comment statements within calculators arepreceded by the command, “:C.” It is placed at the beginning of a lineas follows:

211 :C MAINTAIN BATCH TEMP BELOW 110 DEGF

❏ Control Statement Code Letters (AICusers only)

In AIC, various types of code letters will appear at the left of a line todenote the status of a control statement. These letters will remain inplace until the statement is properly concluded. The code letters havethe following meanings:

T = Conditional initiator. No terminator for statementI = Unconnected conditional terminator -no initiator

BLANK PAGE


Page Characterize-1

CharacterizeCharacterize Module

The Characterize Module computes the alternate gas characterizationmethod as described in American Gas Association Report Number 8(AGA-8).

This module should only be used when a complete gas analysis is notavailable and the AGA8 Module is used to calculate thesupercompressibility (FPV) of the gas. The output of this module iscompatible with the input structures required by the AGA8 module.



specifies which Alternate Gas Characterization method to use. Thefollowing methods are available:

1 - Gravity, Heating Value, Carbon Dioxide Method.2 - Gravity, Heating Value, Carbon Dioxide, Nitrogen Method.3 - Gravity, Carbon Dioxide, Nitrogen Method.4 - Heating Value, Carbon Dioxide, Nitrogen Method.5 - Gravity, Methane, Carbon Dioxide, Nitrogen Method.

MODE

CHEAT_VALUE

ARRAYCOLUMN

LIST

SPEC_GRAV

ERROR

STATUS

MOLE_%_CO2MOLE_%_N2

MOLE_%_METH

Characterize


Page Characterize-2


HEAT_VALUE Default: None, entry required if MODE 1,2, or 4 is selected


is the real gas gross heating value per unit volume, HV, at 600F and14.73 psia (in the units BTU/cubic ft).

SPEC_GRAV Default: None, entry required if MODE 1,2, 3, or 5 is selected


is the specific gravity of the gas.

MOLE_%_CO2 Default: 0Format: Analog signal or constantInput/Output: Input

is the carbon dioxide content in mole percent (%).

MOLE_%_N2 Default: 0Format: Analog signal or constantInput/Output: Input

is the nitrogen content in mole percent (%).

MOLE_%_METH Default: 0Format: Analog signal or constantInput/Output: Input

is the methane content in mole %.


Page Characterize-3


LIST Default: NoneFormat: Analog signal or constantInput/Output: Input

is the number of a signal list where the output data will be stored. Ifthis signal is wired, all Gas Characterization data is directed to thesignals contained in this list. If this signal specifies an invalid signallist, no output is performed.

ARRAY Default: NoneFormat: Analog signal or constantInput/Output: Input

is the number of an analog data array where the output data will bestored. The Gas Characterization data is directed to the array if, andonly if, the LIST terminal is unwired. If this signal specifies an invaliddata array, no output is performed.

COLUMN Default: 1Format: Analog signal or constantInput/Output: Input

is the column in the designated data array where the output data isstored. If the column selected is out of range for the designated dataarray, no data is written to the data array.

ERROR Default: 0Format: Analog signalInput/Output: Output

assumes one of the following error codes:


Page Characterize-4


Code Message

0 Module executed successfully-1 The MODE terminal is unwired.-2 Invalid Mode selection.-3 Required input terminal is missing.-4 Invalid List entry detected. (List entries must be analog.)-5 Invalid List selection.-6 Invalid Data Array selection.-7 Invalid Data Array Column selected.-8 Required output terminal is missing.

(List or Data Array terminal must be wired.)


indicates the sum of the gas component mole percents before normali-zation.

❏ Alternate Gas Characterization Methods

When a complete compositional analysis for the natural gas is notavailable, the AGA-8 Report offers five alternate methods which maybe used to estimate the mole percent of methane and other importanthydrocarbons in the natural gas. In addition, these five methodsestimate the mole percent for certain diluents other than carbondioxide and nitrogen, however, estimates for water vapor and hydro-gen sulfide are not included. The following gas properties are utilizedin various combinations by the five gas characterization methods:

1 Real gas relative density (specific gravity), at 600F and 14.73 psia.2 Real gas gross heating value per unit volume at 600F and14.73 psia

(in the units Btu/ft3).


Page Characterize-5


3 Mole fraction of carbon dioxide.4 Mole fraction of nitrogen.5 Mole fraction of methane.

The gas characterization methods generate estimates of mole percentfor the following gas components:

1 Methane2 Ethane3 Propane4 Normal Butane5 Isobutane6 Sum of Pentanes7 Sum of Hexanes8 Sum of diluents other than Nitrogen and Carbon Dioxide

❏ Using the ModuleThe Characterize Module uses one of five alternate gas characteriza-tion methods, as described in AGA-8 Report, to generate mole percentestimates for the various gas components. The MODE terminal is usedto indicate which of the five methods will be used. If the requiredterminals for the selected method are not wired properly, an error willbe generated and no computation will be performed.

The output generated by the Characterize Module may be stored ineither a List or an Analog Data Array. If a Data Array is used, theColumn terminal may be used to specify a particular column withinthe Data Array where the output is stored. If a Data Array is used andthe Column terminal is not wired, column 1 of the Data Array will beused.

The output stored in the List or Data Array is structured such thatthe List or Data Array may be utilized as input to an AGA8 Module tocompute supercompressibility. In order to provide this compatibility,the output List and Data Array must be able to handle entries for


Page Characterize-6


those gas components estimated by the alternate gas characterizationmethods as well as additional gas components which the AGA8 mod-ule can accommodate. The output List or Data array is formatted asfollows:

Entry # Component Entry # Component(Mole Percent) (Mole Percent)

1 Nitrogen 8 Propane 2 Carbon Dioxide 9 N-Butane 3 Hydrogen Sulfide 10 Iso-Butane 4 Water 11 N-Pentane 5 Helium 12 Iso-Pentane 6 Methane 13 N-Hexane 7 Ethane 14 N-Heptane15 N-Octane

CommandCommand Module


Page Command-1

The Command Module provides a flexible start-up control for a widerange of equipment such as motors, valves or pumps. This moduleinitiates a programmable delay period between an input and outputchange. The output will not respond to an off-to-on change of inputstatus until the delay period times out.

Module TerminalsCOMMAND

comes from a control source and is used to initiate the module. An off-to-on transition starts the output delay timing cycle. At the end of thisdelay cycle, the OUTPUT signal is turned ON. An on- to-off transitionturns off the OUTPUT without delay.

OUTPUT

tracks the Command terminal and is used to drive the external device.The state of the OUTPUT terminal trails the COMMAND terminaloff-to-on transition by the number of seconds entered at the DELAYterminal, but the OUTPUT follows an on-to-off transition withoutdelay.

Default: NoneFormat: Logical signalInput/Output: Input

Default: NoneFormat: Logical signalInput/Output: Output

COMMAND

DELAY

TRANSITION

ON_LIM_SW

OFF_LIM_SW

OUTPUT

STATUS

RUN_TIME

RESET

Command

Command


Page Command-2


DELAY

is the time in seconds that determines the delay period applied to theOUTPUT terminal.

TRANSITION

is the allowable time period in seconds for the hardware device torespond to a status change at the OUTPUT terminal. Discrepancytests are not performed during the transition periods. The STATUSterminal is set to TRUE if a discrepancy exists, and FALSE if there isnone.

ON_LIM_SW

indicates the external hardware is on or open when this signal is ON.

OFF_LIM_SW

indicates the external hardware is off or closed when this signal is ON.

Default: 0.0Format: Analog signal or valueInput/Output: Input

Default: 0.0, if unwired or set to a negativevalue


Default: Defaults to the opposite value ofthe OFF_LIM_SW terminal.


Default: Defaults to the opposite value ofthe ON_LIM_SW terminal.




Page Command-3

If both the ON_LIM_SW and OFF_LIM_SW terminals are not wired,both will default to OFF. Also, the STATUS terminal will be set TRUE(discrepancy case) except when the testing is inhibited at the TRANSI-TION terminal.

STATUS

is OFF when normal conditions are detected during the discrepancytest, or testing is inhibited at the TRANSITION terminal. This signalturns ON in the event that tests indicate a fault.

RUN_TIME

is the accumulated run time (in hours) of the associated device.* Timeis accumulated only when the ON_LIM_SW terminal is ON. Time isupdated by successive rate executions of the module.

RESET

resets the RUN_TIME terminal value to zero when set ON.

Default: 0.0Format: Logical signalInput/Output: Output

Default: 0.0Format: Analog signal or valueInput/Output: Output

Default: OFFFormat: Logical signalInput/Output: Input

*In firmware revisions PLS00/PLX00 (or newer) this value isstored as a double-precision number. Non-protected modefirmware revisions store this as a single-precision number.


Page Command-4


Module Operation

The Command terminal of the module functions as the input. Thisterminal connects to a logical signal from a control source. The controlsource could be the output of another module or an external DI.

When the status of the Command terminal changes from FALSE toTRUE as noted in the timing chart in the figure, a delay count inseconds is initiated. Once the delay has timed out, the OUTPUT willbe switched from FALSE to TRUE, therefore activating the externaldevice. When the external operation is completed, the Commandsignal changes from TRUE to FALSE, causing the OUTPUT to do thesame. In this situation, the OUTPUT signal tracks the Commandsignal without delay, as noted in the figure.

The OFF_LIM_SW and ON_LIM_SW terminals can be used to providephysical feedback information from the controlled device. For thisapplication, the external devices contain limit switches that report theexecution of the output commands to the module. Switch contacts onthe external device will be actuated as the device travels through thelimits of its control cycle. The external contacts can represent theliquid level of a tank, the movement of a mechanical slider, or theposition of a valve.

The status of the signals at the ON_LIM_SW and OFF_LIM_SWterminals is tested for consistency with the OUTPUT terminal value.The results of this test are available at the STATUS terminal. During

COMMAND

OUTPUT

Test ActiveTest Inactive

delay

transition transition



Page Command-5

transitions, the limit position may not be correct. In this situation, a“no test” period can be specified.

The TRANSITION terminal allows the user to set up a time period, inseconds, where the physical feedback information is ignored. TheTRANSITION period is initiated when the OUTPUT signal changesfrom FALSE to TRUE, and again when the OUTPUT signal changesfrom TRUE to FALSE. If a test fails outside the TRANSITION period,the signals at the OFF_LIM_SW and ON_LIM_SW terminals indicatethat the external apparatus has not performed its task and a logicaloutput signal at the STATUS terminal will turn “on” to indicate thediscrepancy.

A running time count of the on-time of the external device is alsoprovided at the RUN_TIME terminal. The count progresses only whenthe signal at the ON_LIM_SW terminal is in an ON state. Calculationof accumulated run time is limited based on IEEE floating pointprecision.

BLANK PAGE

CommentComment Statement


Page Comment-1

A comment statement is a message that appears in the task but is notan executable command.

The comment statement is preceded by the command, “C.” It is placedat the beginning of a line as follows:

❏ SyntaxC place your comment here

❏ Example10 C MAINTAIN BATCH TEMP BELOW 110DEGF

❏ Comments Within Calculator ModulesComments function identically within Calculator modules, except the"C" must be preceded with a colon ":". See 'Calculator' module.

Comment

BLANK PAGE

Communication Ports

ACCOL II Reference Manual Page Commport-1

The communication ports on a 33xx-series controller allow data to betransferred to other 33xx controllers in the network, as well as toforeign devices, printers, and supervisory computers.

In AIC, they are defined on the Communications Configuration Menu,and selections are made using the [JOG] key.

If you are using ACCOL Workbench, or the ACCOL II Batch Compiler(ABC), communication ports are defined in the *COMMUNICATIONSsection of the ACCOL source file.*

In either case, the number and type of ports to be defined depends onthe type of controller you are using, and the requirements of yourapplication. The pages that follow describe the different types of portswhich may be defined.

❏ ❏ ❏ ❏ ❏ Aux1 and Aux2 Ports (CFE 3385/ UCS 3380 only)

The auxiliary communication ports are associated with the followinghardware and port assignments:

Position Port Type Hardware Req'd Unit Limits

Aux1 only CFE(Slave) IEEE 488 I/F Board 3385 No other slaveports

Aux2* LIU Master LIU I/F Board 3385 Up to 63 slavenodes

Aux1/Aux2* LIU Slave LIU I/F Board 3380 No other SlavePort

Aux1/Aux2* LIU Master LIU I/F Board 3380 Up to 63 Slaves

* Physical hardware requires installed Aux1 for Aux2 addition

The Auxiliary ports are only applicable to the CFE 3385 and UCS3380. The default assignment for both ports is UNUSED. They shouldbe set to UNUSED when building a load for an RDC 3350.

*See the ACCOL Workbench User Manual (D4051), or theACCOL II Batch Compiler Manual (D4055) for informationon syntax required in the *COMMUNICATIONS section.

Communication Ports

ACCOL II Reference ManualPage Commport-2

Communication Ports

The IEEE 488 Interface Board provides the connection between a CFE3385 and a VAX Computer. Only Aux1 can be assigned as a CFE port.Because the CFE port functions as a slave port, the CFE cannot beconfigured if another port is currently assigned as a slave. NOTE: Seealso the later discussion on Serial CFE for information on connectingto a VAX computer without using the IEEE 488 I/F Board.

The LIU Interface Board provides the connections into an LIU DataHighway local area network. The Data Highway can be either a singlelink or a dual-redundant configuration (dual communication links). AData Highway can have a maxiumum of 64 nodes, i.e. 1 Master and upto 63 Slave nodes. An individual node can function as a slave node ononly one port, therefore an LIU Slave cannot be defined if another portis currently assigned as a slave. An individual node can function as aslave on one LIU port and as a master on the other LIU port (assignedin either order), but can function as a master on only one LIU port.

The LIU Master option requires that a High Slave Adr (High SlaveAddress) be specified. The High Slave address defines the range ofaddresses (Low to High) for the connected slave nodes. Low is animplied value -- 1 for the first master port and 1 greater than theprevious master port High for the other master port(s). The specifiedvalue for the High Slave Adr defines High for that master port. Themaximum number of slave nodes on an LIU Master port is 63, there-fore 063 is the maximum High Slave Adr value which can be enteredfor an LIU Master port. (The Low Slave Address for the next masterport would then be 064.)

A load can contain up to four master ports, including an LIU masterport, and master/expanded master ports defined on Serial ports Athrough D. If more than one master port is assigned to a unit, thevalues entered in the High Slave Adr fields must appear in ascendingorder going from the top to the bottom of the *COMMUNICATIONSsection, or the Communications Configuration Menu. The total num-ber of slave nodes which can be configured immediately below amaster node through all of the master ports combined is 127. NOTE:See the section 'Expanded Node Addressing' for details on addressingmore than 127 nodes using Expanded Addressing Master port(s).

Communication Ports


❏❏❏❏❏ Serial Ports: Ports A, B, C, and D

The serial ports are intended for communications among Bristol 3xxxcontrollers, and with supervisory computers. Communication withforeign devices such as non-Bristol controllers, and printers may alsobe accomplished through these ports. Ports A and B are standard andPorts C and D are optional. Port D is not available on the EGM 3530and on some models of the GFC 3308. Ports A and B are not supportedin 386EX Protected Mode versions of the DPC 3335 with Ethernetsupport. Serial communication in the RTU 3305 is only supported onPorts B, C, and D.

There are several configuration options available for Ports A throughD, though not all options are available for all controller models: Slave,Pseudo Slave, Pseudo Slave with Alarms, Master, Logger, Serial CFE,RIOR, VSAT Slave, and Expanded Addressing Master. There are alsothree special communications options. They are called Optional Com-munications, Columbia Natural Gas (CNG), and Custom. All specialcommunication functions are non-standard and may require specialfirmware. A description of configuration options is included later inthis section.

Although ACCOL Workbench allows users to specify the INTERNETPROTOCOL (IP) PORT, this IS NOT YET SUPPORTED FOR SE-RIAL PORTS.

❏❏❏❏❏ Serial Ports: Ports G, H, I, and J*Ports I and J are available for DPC 3330 and DPC 3335 units with the386EX Protected Mode CPU, and Ports G and H are available for DPC3330 units only with the 386EX Protected Mode CPU. ACCOL 6.0 (ornewer) software tools are required to use these ports, and PLS00/PLX00 (or newer) firmware is required. Like Ports A through D, theyare intended for communications among Bristol controllers, and withsupervisory computers, foreign devices, and printers. NOTE: Ports Gand H are NOT available for the DPC 3335.

*Ports K, L, M, N, O, and P, which may appear on certainmenus in ACCOL Workbench, do NOT EXIST, and arereserved for possible future use.


Communication Ports

These ports support the following configuration options: Slave, PseudoSlave, Pseudo Slave with Alarms, Master, Logger, Serial CFE, VSATSlave, Expanded Addressing Master, and Custom.

NOTE: Ports H and J do NOT support synchronous communication,therefore they may not use synchronous baud rates of 187,500, 1MEG,or RASCL.

NOTE: Synchronous communication is supported on Ports G and I,however, only at 187,500 and 1MEG; RASCL is NOT supported.

Although ACCOL Workbench allows users to specify the INTERNETPROTOCOL (IP) PORT, this IS NOT YET SUPPORTED FOR SE-RIAL PORTS.

❏ ❏ ❏ ❏ ❏ Built-In Ports: BIP 1, BIP 2

DPC 3330, DPC 3335, and RTU 3310 units containing the 32-bit386EX CPU Engine Board are equipped with 2 built-in ports (BIP), inaddition to the standard serial ports. Use of these ports requiresACCOL software version 5.10 (or newer) and remote firmware RMS00,PLS00, PLX00 (or newer).

These ports support the following configuration options: Master,Expanded Addressing Master, Slave, Pseudo Slave, Pseudo Slave withAlarms, VSAT Slave and Serial CFE. In addition, if the 386EX CPUEngine Board supports Protected Mode (PLS00/PLX00 firmware ornewer), configuration options for Custom, and Logger are also avail-able. Each of these options is described later in this section.

NOTE: The Built-In Ports (BIP 1, and BIP 2) support asynchronous(serial) communication rates ONLY; 187500 sync, 1MEG sync, and1MEG RASCL ARE NOT AVAILABLE FOR THESE PORTS.

Although ACCOL Workbench allows users to specify the INTERNETPROTOCOL (IP) PORT, this IS NOT YET SUPPORTED FOR BIPPORTS.

Communication Ports


❏❏❏❏❏ Ethernet Port

This port is only available for certain 386EX Protected Mode versionsof the DPC 3330 and DPC 3335. In addition, to make use of theEthernet Port requires PES03/PEX03 or newer level firmware.

This port currently supports only one configuration option, theInternet Protocol (IP).

Syntax in ACCOL Workbench for configuring this port is as follows:

*COMMUNICATION PORTS . . ETHRNT IP

No other configuration is necessary within ACCOL Workbench,however, additional configuration may be required via the RTUConfigure Mode option in LocalView or NetView. For a full discussionof the usage of Internet Protocol with Bristol equipment, see the OpenBSI Utilities Manual (Ver 3.x) (document# D5081).

❏❏❏❏❏ Serial / BIP Configuration OptionsNote: Some configuration options are NOT available on certain ports.See the charts at the end of this section for details.

SLAVE PORT

Slave Ports transmit data only when polled by a master. All timesynchronization and node routing table information is received onlythrough slave ports.

On the AIC Communications Configuration Menu, a port that is


Communication Ports

assigned as a slave may appear like this:

Port A: >> Slave Baud 9600 Async

Entries in the ACCOL source file for ABC or ACCOL Workbench userswould appear as shown below:

*COMMUNICATIONS PORT_A SLAVE 9600

Baud rates should be specified according to the chart at the end of thissection. Slave Ports can be configured for either asynchronous orsynchronous communication, however BIP 1 &2, and Port H, and PortJ do NOT support synchronous communication; therefore they mustuse only asynchronous baud rates.

Among all ports, there can only be one slave port assigned per 3xxxunit. This includes LIU Slaves, as well as CFE or Serial CFE portswhich configure a unit as a slave to a VAX computer. Pseudo Slaveand Pseudo Slave with Alarms Ports are not counted in this restric-tion, however. If you are using an EGM 3530 controller, either Port Bor C may be used as a Slave Port.

PSEUDO SLAVE PORT

A pseudo slave port is used to communicate with a PEI or NetworkMonitor which is acting as a pseudo master device. A device connectedto this port can read and write information to any node in an activenetwork if it has the correct node routing table files.

A Pseudo Slave Port, as it would appear in the AIC, is shown below.

Port B: >> Pseudo Slave Baud 9600 Async

Communication Ports



*COMMUNICATIONS PORT_B P-SLAVE 9600

Baud rates should be specified according to the chart at the end of thissection.

Pseudo Slave Ports can be configured for either asynchronous orsynchronous communication, however BIP 1 &2, and Port H, and PortJ do NOT support synchronous communication, therefore they must bespecified as asynchronous, and use only asynchronous baud rates.

Users with the 386EX Protected Mode CPU can specify up to eightPseudo Slave ports, however, only one of them can be a Pseudo Slavewith Alarms Port (see below). Users with earlier firmware versions canspecify two Pseudo Slave Ports, one of which may be a Pseudo Slavewith Alarms Port.

If you are using an EGM 3530 controller, any of its ports can beconfigured as a Pseudo Slave Port.

PSEUDO SLAVE WITH ALARMS PORT

This option is identical to the Pseudo Slave option described aboveexcept that it allows alarm information to be reported to the pseudomaster device connected to this port. The total number of PseudoSlave Ports which may be defined varies depending upon the firmwarerevision level being used (see above), however, in all cases, only onepseudo slave with alarms port may be defined.

A Pseudo Slave with Alarms Port, as it would appear in the AIC, isshown below:

Port A: >> Pseudo Slave - Alarms Baud 9600 Async


Communication Ports


*COMMUNICATIONS PORT_A P-SLAVE-ALM 9600


Pseudo Slave with Alarms Ports can be configured for either asynchro-nous or synchronous communication, however BIP 1 &2, and Port H,and Port J do NOT support synchronous communication, thereforethey must be specified as asynchronous, and use only asynchronousbaud rates.

VSAT SLAVE PORT*

The VSAT Slave Port allows a 33xx controller to communicate withthird-party master software via radio/satellite links.

A VSAT Slave Port, as it would appear in the AIC, is shown below.

BIP 1: VSATSLV __BAUD 9600Min Response Time: _5 Max Response Time: _10


*COMMUNICATIONS BIP_1 VSATSLV 9600 5 10


Synchronous communication is not supported on VSAT Slave Ports.

Specify the minimum and maximum response times. The 33xx mustrespond to a 'request for data' message some time between the mini-

*There is NO VSAT Master Port available in Network 3000-series controllers. Open BSI workstations with Open BSIUtilities version 2.1 (or newer) can serve as VSAT Masterdevices, however.

Communication Ports


mum and maximum response times. These values can range from 1 to255, and are in units of 0.1 seconds.

Minimum response time is the amount of time, from when a requestfor data is received, that the 33xx will wait before responding to therequest. The response will never be sent prior to the expiration of theminimum response time. If the minimum response time is set to 0, aresponse will be sent sometime between 0 and the maximum responsetime.

0 0.1 0.2 0.3 0.4 0.5 0.6 0.7

0.3 seconds

Max response time 0.7 secondsRequest

for

data

rece

ived,

timin

g b

egin

s

No responseswill be sent priorto expiration of

min response time.

Response must be sentby the time max responsetime expires.

Min response time

Must

resp

ond, eve

n if

only

to

ack

now

ledge r

ece

ipt of data

request

.

Maximum response time is the maximum amount of time the 33xx canwait before responding to a request for data. If the maximum responsetime is 0, or less than or equal to the minimum response time, thisvalue will be ignored. If no data is ready by the time the maximumresponse time has expired, an acknowledgement of the request will be


Communication Ports

sent, but the data will have to be retrieved by another request mes-sage.

The drawing, above, illustrates the use of the minimum and maximumresponse times for a given data request. In this example, the responseto the request must be sent between 0.3 and 0.7 seconds from whenthe request was received.

MASTER PORT

With the exception of Protected Mode Units (386EX CPU with PLS00/PLX00 or newer firmware) only four master/expanded addressingmaster ports can be defined in the ACCOL load. On a UCS 3380 / CFE3385, this total of four would include a Master LIU port assignment onthe Aux ports, in addition to the master port designations for Ports Athrough D. For 186-based and 386EX Real Mode DPC 3330, DPC3335, and RTU 3310 units, the limit on four master/expanded address-ing master ports applies whether or not the units have BIP 1 and 2, inaddition to Ports A through D.

A port assigned as a master gives the node the ability to communicatewith slave nodes directly below it in the network. Data can be passedbetween the master and slave nodes, or network communications canbe routed to and through them. Alarm information from slave nodes iscollected via the master port. The node then stores this data until it ispolled by its own master device. An example of a master port assign-ment, as it would appear in AIC, appears below:

Port B: >> Master Baud 187500 __ SyncHigh Slave Adr: 7 Timeout: 5

Entries in the ACCOL source file for ABC and ACCOL Workbenchusers would appear as shown below:

*COMMUNICATIONS PORT_B MASTER 187500 7 5

Communication Ports



Master Ports can be configured for either asynchronous or synchronouscommunication, however BIP 1 &2, and Port H, and Port J do NOTsupport synchronous communication, therefore they must be specifiedas asynchronous, and use only asynchronous baud rates.

If more than one Master, EAMaster, LIU Master port is to exist in aparticular ACCOL load, the Master port slave address ranges must bedefined in ascending order and CANNOT overlap. The order of defini-tion is: BIP_1, BIP_2, Port_A, Port_B, Port_C, Port_D, Port_G,Port_H, Port_I, Port_J.

The High Slave Adr (High Slave Address) specifies the highest slaveaddress allowed for slave nodes connected to the port. The Low slaveaddress is not entered, but is an implied value. For the very firstMaster-type port defined, the Low address for the port's address rangeis 1. For the second Master-type port defined in the load, the Lowaddress is one more than the High Slave Address of the first Master-type port. For the third Master-type port, the Low address is one morethan the High Slave Address for the second Master-type port, and soon. This prevents slave address ranges from different Master-typeports from overlapping. For example, if BIP_2 is the first Master Portto be defined in the load, and it is specified with a High Slave Addressof 6, and Port_C is the second Master Port in the load, and it has aHigh Slave Address of 18, then the valid slave address ranges are 1 to6 for BIP_2, and 7 to 18 for Port_C. The maximum number of slavenodes which can be configured at the next level down in the network(immediately below a master node) through all of the Master, LIUMaster, or EAMaster ports combined is 127.

The value specified for the Timeout is the length of time the node willwait for the beginning of a response from any slave on this port. Thisallows for any delays inherent in processing at the slaves, and in thetransmission method (e.g. modem delays). The value can range from 1to 250 and is in units of tenths of a second. For example, to specify a 1second timeout, enter a 10. The default is 5, which is a 0.5 secondtimeout.


Communication Ports

EXPANDED ADDRESSING MASTER (EAMASTER) PORT

With the exception of Protected Mode units (386EX CPU with PLS00/PLX00 or newer firmware) only four master / expanded addressingmaster ports can be assigned in a load.

A port assigned as an expanded addressing master gives the node theability to communicate with more than 127 slave nodes below it in thenetwork. For this to work there must be an intermediate level in thenetwork topology which contains virtual nodes; i.e. there is no actualphysical controller. The slave nodes are on the level below the virtualnodes. (See ‘Expanded Node Addressing’, later in this manual, forinformation on creating virtual nodes.)

An example of an expanded addressing master port assignment, as itwould appear in the AIC, is shown below:

Port B: >> Exp. Master __Baud 9600 Timeout: _5High Slave Adr: 2 High EASlave Adr: 125


*COMMUNICATIONS PORT_B EMASTER 9600 2 125 5


NOTE: Synchronous communication is NOT supported on ExpandedAddressing Master ports.

The High Slave Adr (High Slave Address) must be specified accordingto the rules used for Master ports. For the Expanded AddressingMaster port type, however, the virtual nodes are counted as part of thelimit of 127 nodes which can report to a single node through all of itsMaster/EAMaster ports.

Communication Ports


The High EASlave Adr must be set to the address used by the nodewith the highest address under any of the virtual nodes.

The Timeout is the length of time the node will wait for the beginningof a response from any slave on this port. This allows for any delaysinherent in processing at the slave, and in the transmission method(e.g. modem delays). The value can range from 1 to 250 and is in unitsof tenths of a second. For example, to specify a 1 second timeout,specify a Timeout of 10. The default is 5, which is a 0.5 secondtimeout.

SERIAL CFE PORT

A port designated Serial CFE allows RDC 3350, UCS 3380, DPC 3330,RTU 3310, and DPC 3335 controllers to perform the same templatedata collection and management functions as a CFE 3385. In this waya serial controller can act as the top-level node without the require-ment of having the IEEE 488 interface hardware. This option is foruse with Enterprise Server software only. Serial CFEs require aminimum of 64K of expanded RAM memory (if expanded RAM issupported in the unit.) Trolltalk-VAX does not support serial CFEs.

An example of a Serial CFE port assignment, as it would appear inAIC, appears below:

Port B: >> Serial CFE Baud 9600 Async


*COMMUNICATIONS PORT_B CFE 9600


Communication Ports

LOGGER PORT

When a port is assigned as a logger port, the Logger Module is used tosend and/or receive formatted ASCII data on this port. This permitsthe node to communicate directly with an external ASCII I/O devicesuch as a printer or display terminal.

A Logger Port definition, as it would appear in the AIC, appearsbelow:

Port B: >> Logger _Baud 9600 _Half Duplex _No CTS_7 Bits _2 Stop Bits _Even Parity


*COMMUNICATIONS PORT_B LOGGER 9600 PARITY_E SBIT_2 BIT_7 H_DPLX NO_CTS

Several parameters must be entered/selected when defining theLogger Port:

Baud Baud rates should be selected based on the chart at theend of this section.

Terminal Type (Half Duplex or TTY) This Terminal Typedetermines how the input characters will be processed. Theselected type has no effect on the output. The choices forTerminal Type are Half Duplex and TTY.

Half Duplex is the default. This selection has the followingcharacteristics:

● The “M” field descriptor of the Logger module Formatis used to specify the “start” and “end” delimitercharacters of a sequence of input characters. A “start”or “end” character with the value of zero indicatesnone. The default is no “start” or “end” character.

Communication Ports


● If there are no “start” or “end” characters, all inputcharacters are accepted and processed by the Logger.No “start” or “end” characters are transmitted onoutput.

● If a “start” character is used, input characters areignored until the “start” character is received. Then,subsequent characters are accepted and processeduntil the end character is received. On output, the“start” character precedes the first character of themessage.

● If an “end” character is used, any input charactersthat follow will not be accepted until another “start”character is received. On output, the “end” character isappended to the output message.

● The “start” and “end” delimiting characters are notprocessed by the Logger. Only those characters inbetween are used.

TTY has the following characteristics:

● Only printable characters, backspace, delete andcarriage return characters are valid.

● Valid characters are buffered and not processed untila carriage return is received.

● All buffered characters are echoed to the device.

● A backspace or delete character will cause the previ-ous character to be deleted from the buffer and thesequence “backspace, space, backspace”, will beechoed back to the device. The device must move onecharacter position to the left in response to a back-space character for proper operation.


Communication Ports

● A carriage return is echoed only as a carriage return.No line-feed character is sent to the device.

● The “start of message” and “end of message” charac-ters that are specified via the M field descriptor areignored and not used.

CTS/No CTS This selection specifies the desired communicationsinterface. The choices are No CTS, CTS or XON-XOFF. Thesecontrols apply only to the output and have no effect on theinput. If No CTS (No Clear To Send) is selected, then nosignal protocol is specified. If CTS (Clear To Send) is speci-fied, the characters will be transmitted only when the CTSsignal is active. If the XON-XOFF option is chosen, thereceived characters will be checked for the presence of XON-XOFF characters. If an XOFF is received, the output will besuspended until an XON character is received. These charac-ters only apply during the output phase of a log. The XONstate is assumed at the beginning of a log and at the time thatthe log switches from input to output.

NOTE

Whenever characters are transmitted during anoutput and TTY echo, the “Request To Send”signal is turned on. Whenever characters arereceived during an input and output using theXON-XOFF selection, the “Data Terminal Ready”signal is turned on.

Communication Ports


NOTE

There are special considerations to be aware ofwhen using CTS/No CTS with the Logger Port onan RS485 communication line. If CTS is chosen onan RS485 line, the output functions correctly onlywhen the Logger's associated Format statement isONLY used for output. If the Format statementincludes a direction change from output '<' toinput '>', then the last character will NOT betransmitted successfully. To solve this problem,add one NULL '#0' character in the format state-ment before the direction change to '>' input.Alternatively, you could use separate Formatstatements for output and input (i.e. use the sameLogger Module, but alternate Format statements,or use two Logger Modules, one for the outputfollowed by another one for the input.)

If you choose NO_CTS in RS485 mode, add oneNULL '#0' character in the Logger's Formatstatement.

Width sets the length of a character. The choices are 6, 7 or 8bits. The default is 7 bits. Both the input and output charac-ters are truncated if the character exceeds the specifiedlength. NOTE: If you are using PLC-type format codes (BIT,BYT, WRD, LBF, HBF, VL, VSn, VUn, BCDn, CST1:0,CST2:0, CST3:0, or CST4:0), you MUST set the length of acharacter to 8 instead of the default of 7.

Stop Bits This selection defines the number of stop bits used byeach channel. The choices are 2 , 1 or 1-1/2 Stop Bits.

Parity This selection determines whether Even Parity, OddParity or No Parity options are used for each character. If Oddor Even is specified, a parity bit is generated for transmittedcharacters and checked for received characters.


Communication Ports

OPTIONAL COMMUNICATION PORT (TANO)

The optional communication port configures the remote node for theTANO special communication protocol. This protocol is proprietaryand is only issued per special sales order and requires special firm-ware.

The Optional Communication Port definition, as it would appear in theAIC, appears below:

Port A Optional Comm BAUD 1200

Entries in the ACCOL source file for ABC users would appear asshown below:

*COMMUNICATIONS PORT_A OPT_COMM 1200

NOTE: Optional Communication Ports ARE NOT SUPPORTED forPLS00/PLX00 (or newer) Protected Mode firmware.

COLUMBIA NATURAL GAS (CNG) PORT

This port provides for a gas industry communication format thatconforms to standards specified by the Columbia Natural Gas Corp.Either slave or master mode may be selected. This protocol is onlyissued per special sales order and requires special firmware.*

A Columbia Natural Gas Port definition, as it would appear in theAIC, appears below:

Port A Columbia Natural Gas _ BAUD 9600 _ Slave

* See the ACCOL II Custom Protocols Manual (D4066) for additional information on the Columbia Natural Gas Protocol.

Communication Ports


Entries in the ACCOL source file for ABC users would appear asshown below: *COMMUNICATIONS PORT_A CNG 9600 SLAVE

Columbia Natural Gas Ports ARE NOT SUPPORTED for ProtectedMode firmware EARLIER THAN PCP03.

CUSTOM PORT*

A Custom port provides a mechanism for supporting a variety ofcustom interfaces. The type of interface used is specified via the Modeselection. Each Custom port can support one type of custom interface.

A Custom Port, as it would appear in AIC, is shown below:

Port A: >> Custom __Baud 1200 Mode: 1 P1: 0 P2: 0 7 Bits 2 Stop Bits Odd Parity


*COMMUNICATIONS PORT_A CUSTOM 1200 PARITY_O SBIT_2 BIT_7 PARAM: 1 0 0

Several parameters must be entered/selected when defining theCustom Port:

Baud Baud rates should be selected based on the chart at theend of this section. The default rate is 1200 baud.

Mode The Mode value determines the type of custom protocolwhich will be used for the port. Several custom protocols aresupported by the standard firmware, while others are issuedper special sales order and require a special order fromBristol. Refer to the ACCOL II Custom Protocols Manual(document# D4066) for details on specific protocols.

*If you have an EGM 3530, only ports B and C canserve as Custom Ports, and they may only be usedfor Modbus custom applications.


Communication Ports

P1 is a mode specific parameter. The P1 value varies dependingupon the specific custom interface being used. Refer to theACCOL II Custom Protocols Manual (document# D4066) fordetails.

P2 is also a mode specific parameter. The P2 value varies de-pending upon the specific custom interface being used. Referto the ACCOL II Custom Protocols Manual (document#D4066) for details.

Width sets the length of the transmission character. Values of 7, 8or 6 bits may be selected. Both the input and output charac-ters are truncated if the character exceeds the specifiedlength. Default is 7 Bits. Valid selections are mode specific.

Stop Bits sets the number of stop bits used by each channel. Thechoices are 2, 1 and 1-1/2 stop bits. Default is 2 Stop Bits.Valid selections are mode specific.

Parity determines whether Even Parity, Odd Parity, or No Parityis used. If Odd or Even is specified, a parity bit is generatedfor transmitted characters and checked for received charac-ters. The parity bit is appended to the number of bits specifiedunder Width. The default is Odd Parity. Valid selections aremode specific.

RIOR PORT

An RIOR port is used by the 3330/3335/3310 controllers which arecommunicating with an RIO 3331 Remote I/O Rack.

IMPORTANT

RTU 3310 units with the 386EX CPU, as well asany 386EX unit without the Enhanced Communi-cation Board, CANNOT be used with an RIO 3331Remote I/O Rack.

Communication Ports


No more than ten RIO 3331 units (total from all RIOR ports combined)should be communicating with a single 3310/3330/3335 master unit,and no more than ten RIO 3331 units can be used on a single RIORport. RIOR is only supported on Ports A through D.

An RIOR port, as it would appear in AIC, is shown below:

Port D: RIOR __BAUD 187500 SyncMax RIOR Node Adr this Port: _5


*COMMUNICATIONS PORT_D RIOR 187500 5

Baud rates should be selected based on the chart at the end of thissection. Only synchronous communication is supported.

The highest node address for the RIO 3331 units attached to this portmust also be specified. For example, if you have five RIOR nodesattached to this port with addresses from 1 to 5, enter 5.

NOTE:

In contrast to the rules for assigning slave nodeson multiple master ports (where slave numberingmust be in ascending order, and individual slavenode numbers cannot be duplicated), RIOR nodesare different. Each RIOR port should start RIOnode addressing at address 1, and assign ad-dresses in consecutive order for the remainingnodes on that port up to the maximum address.Skipping RIO node numbers on a port addsoverhead in communications and should beavoided.


Communication Ports

❏ ❏ ❏ ❏ ❏ Baud RatesThe charts that follow summarize the minimum software and firmware revision levelsrequired in order to define various types of ports, and which baud rates are available forthem. Unless otherwise noted, options introduced in a given revision are available in allsubsequent revisions, i.e. if available in Real Mode, it will also be in Protected Mode.

BUILT-IN PORT (BIP 1 & 2) BAUD RATE:CONFIGURATION OPTION:

110 150 to 1200 to38400 19200

Slave 5.10RMS00

Pseudo Slave 5.10RMS00

Pseudo Slave with Alarms 5.10RMS00

VSAT Slave 5.10RMS00

Master 5.10RMS00

Expanded Addressing Master 5.10RMS00

Serial CFE 5.10RMS00

Custom 6.0 6.0 PLS00 PLS00

Logger 6.0 6.0 PLS00 PLS00

Available BAUD rates from 150 to 38400 are: 150, 300, 600, 1200, 2400, 4800, 9600,19200, and 38400.

If PLS00 firmware is shown, PLX00 firmware is also applicable.

Communication Ports


110

150

to 9

600

1200

on

ly

1920

0

3840

0

1875

00 S

ync

1 M

EG

Syn

c

1 M

EG

RA

SC

L

Slave ✓ 5.0 5.0 5.0 5.3 5.4AA AA AA AD AE

Pseudo Slave ✓ 5.0 5.0 5.0 5.3 5.4AA AA AA AD AE

Pseudo Slave with Alarms ✓ 5.0 5.0 5.0 5.3 5.4AA AA AA AD AE

Master ✓ 5.0 5.0 5.0 5.3 5.4AA AA AA AD AE

Logger ✓ ✓ 5.0 5.0AA AA

Optional Communications ✓

** CNG 6.3

Custom ✓ ✓ 5.0 5.0 AA AA

Serial CFE 5.2 5.2 5.2 5.2 5.3 5.4 AC.1 AC.1 AC.1 AC.1 AD AE

RIOR (386EX units 5.3 5.3 5.4 require enhanced comm brd) AD AD AE

Expanded Address. Master 5.6 5.6 5.6 AG AG AG

VSAT Slave 5.8 AJ

SERIAL PORT (A-D) CONFIG. OPTION:

BA

UD

RA

TE

:

(Available BAUD rates from 150 to 19200 are: 150, 300, 600, 1200, 2400, 4800, 9600,19200)✓ = indicates has been available since before ACCOL 5.0/AA PROMS

300

to

9600

1200

to

1920

0PLS03

** Optional Communication Ports are NOT available inProtected Mode (PLS00/PLX00 or newer) firmware.


Communication Ports

SERIAL PORT (G, I) CONFIG. OPTION:

BA

UD

RA

TE

:

(Available BAUD rates from 150 to 19200 are: 150, 300, 600, 1200, 2400, 4800, 9600, 19200)

110

150

to 9

600

1920

0

3840

0

1875

00 S

ync

1 M

EG

Syn

c

Note: If PLS00 is shown, PLX00 firmware also applies.

1200

to

1920

0

Slave 6.0 6.0 6.0 6.0 6.0PLS00 PLS00 PLS00 PLS00 PLS00

Pseudo Slave 6.0 6.0 6.0 6.0 6.0PLS00 PLS00 PLS00 PLS00 PLS00

Pseudo Slave with Alarms 6.0 6.0 6.0 6.0 6.0PLS00 PLS00 PLS00 PLS00 PLS00

Master 6.0 6.0 6.0 6.0 6.0PLS00 PLS00 PLS00 PLS00 PLS00

Logger 6.0 6.0 6.0 6.0PLS00 PLS00 PLS00 PLS00

Custom 6.0 6.0 6.0 6.0PLS00 PLS00 PLS00 PLS00

Serial CFE 6.0 6.0 6.0 6.0 6.0PLS00 PLS00 PLS00 PLS00 PLS00

Expanded Address. Master 6.0 6.0 6.0PLS00 PLS00 PLS00

VSAT Slave 6.0PLS00

Communication Ports


SERIAL PORT (H,J) CONFIG. OPTION:

BA

UD

RA

TE

:

(Available BAUD rates from 150 to 19200 are: 150, 300, 600, 1200, 2400, 4800, 9600, 19200)

Note: If PLS00 is shown, PLX00 firmware also applies.

Slave 6.0 6.0 6.0PLS00 PLS00 PLS00

Pseudo Slave 6.0 6.0 6.0PLS00 PLS00 PLS00

Pseudo Slave with Alarms 6.0 6.0 6.0PLS00 PLS00 PLS00

Master 6.0 6.0 6.0PLS00 PLS00 PLS00

Logger 6.0 6.0 6.0 6.0PLS00 PLS00 PLS00 PLS00

Custom 6.0 6.0 6.0 6.0PLS00 PLS00 PLS00 PLS00

Serial CFE 6.0 6.0 6.0PLS00 PLS00 PLS00

Expanded Address. Master 6.0 6.0 6.0PLS00 PLS00 PLS00

VSAT Slave 6.0PLS00

110

150

to 9

600

1920

0

3840

0

1200

to

1920

0


Communication Ports

SERIAL PORT (A,B,C) CONFIG. OPTION:

BA

UD

RA

TE

:

Slave on Port B or C 1.1 1.1 1.1 1.1 1.1TFA01 TFA01 TFA01 TFA01 TFA01

Pseudo Slave on Port A, B 1.1 1.1 1.1 1.1 1.1or C (w or w/o alarms) TFA01 TFA01 TFA01 TFA01 TFA01

Custom on Port B 1.1 1.1 1.1 1.1 1.1or C (Modbus usage only) TFA01 TFA01 TFA01 TFA01 TFA01

2400

4800

9600

1920

0

3840

0

EGM / RTU 3530

NOTE: For the 3530, the version of ACCOL Tools shown (for example,1.1) refers to the version of ACCOL Workbench (RM).

NOTE: For the RTU 3530, the firmware version used must be TRAxxinstead of TFAxx.

Communication Ports


DPC 3330,DPC 3335

RTU 3310 RTU 3305EGM /RTU3530

GFC 3308

Slave OK OK OKOn Port Bor C ONLY

OK

Pseudo Slave OK OK OK OK OK

Pseudo Slavewith Alarms

OK OK OK OK OK

VSAT Slave OK OK OKNOTALLOWED

OK

Master OK OK OKNOTALLOWED

OK

ExpandedAddressingMaster

OK OK OKNOTALLOWED

NOTALLOWED

Serial CFE OK OKNOTALLOWED

NOTALLOWED

NOTALLOWED

Custom OK OK OKMODBUSON B, CONLY

OK

Logger OK OK OKNOTALLOWED

OK

Opt Comm

NOTsupported inProtectedMode units.

NOTsupported inProtectedMode units.

OKNOTALLOWED

NOTALLOWED

CNG PortNot allowedin PLS00 toPLS02

Not allowedin PLS00 toPLS02

OKNOTALLOWED

NOTALLOWED

RIOR Port

386EX unitsrequireEnhancedCommunicat-ion Board.

NOTSUPPORTEDIN ANY386EXUNITS.

NOTALLOWED

NOTALLOWED

NOTALLOWED

InternetProtocol (IP)Port

ONLY IFETHERNETSUPPORTED

NOTALLOWED

NOTALLOWED

NOTALLOWED

NOTALLOWED

❏ Controllers and Supported Port Types


Communication Ports

❏ Synchronous CommunicationSynchronous communication is supported on ports A through D, G,and I. Synchronous communication is NOT supported on either BIP 1,BIP 2, Port H, or Port J.

Not all controller models support synchronous communication. Differ-ences are noted below:

DPC 3330, DPC 3335 with 186-based CPU

Ports B and D support synchronous communication. The DPC 3330and DPC 3335 Enhanced Communication Board (ECB) supportssynchronous communication on both ports A and B (slot 1) and / orports C and D (slot 2). This board is supported in the AD.00 (and later)PROM set. The DPC 3330 and DPC 3335 support synchronous commu-nication at 187,500 and 1MEG beginning with ACCOL 5.3 and theAD.00 PROM set, and 1MEG RASCL (Redundant Automatic Switch-ing Communication Link) beginning with ACCOL 5.4 and the AE.00PROM set. In order to support the 1MEG speed, the communicationsboard must include the 16 MHz crystal and selection jumpers.

DPC 3330, DPC 3335 with 386EX-based CPU

The DPC 3330 and DPC 3335 with the 386EX-based CPU supportsynchronous communication on Ports A and B (slot 1) and /or Ports Cand D (slot 2) ONLY if these units have the Enhanced CommunicationBoard. 386EX-based units with the standard communications boardDO NOT SUPPORT SYNCHRONOUS COMMUNICATION.

Additionally, 386EX Protected Mode units (PLS00/PLX00 or newerfirmware) support synchronous communication on Ports G and I at187,500 and 1MEG. They DO NOT support RASCL (RedundantAutomatic Switching Communication Link).

Ports H and J DO NOT support synchronous communication.

Communication Ports


RTU 3310

RTU 3310 units with the 186 CPU board support synchronous commu-nication at 187,500 on Ports B and D only. RTU 3310 units with the386EX CPU board do NOT support synchronous communication.

RTU 3305

Synchronous communication is not available for the RTU 3305.

GFC 3308

Synchronous communication is not available for the GFC 3308.

EGM 3530 / RTU 3530

Synchronous communication is not available for the EGM/RTU 3530.

CFE 3385, RDC 3350, UCS 3380

Ports B and D support synchronous communication except on redun-dant RDC 3350, UCS 3380, and CFE 3385 units. In those cases,only port B can be synchronous (187,500 Baud only.)

BLANK PAGE

ComparatorComparator Module


Page Comparator-1

The Comparator Module compares two analog signals (INPUT andSETPOINT) and provides a set of three outputs (OUTPUT 1, 2 & 3).These outputs may be used as analog or logical outputs as required byyour application.

The function of the three outputs depends on the mode of operation. Inthe Normal Mode, they operate as high-select, low-select, and differ-ence outputs. In the Raise/Lower Mode, the first two outputs operateas raise and lower command outputs and the third output is not used.The operating conditions for both modes are shown in the tables at theend of this section.

Module TerminalsMODE

sets the operating mode of the module. When this signal is set ON, themodule is in the Normal Mode. When it is OFF, the module is inRaise/Lower Mode.

Default: ON (Normal Mode)Format: Logical signalInput/Output: Input

INPUTSETPOINTDEADBAND

OUTPUT_1OUTPUT_2OUTPUT_3

MODE

Comparator


Page Comparator-2


INPUT

is the input to the module. This value is compared to the setpoint.

SETPOINT

is the reference to which the INPUT signal is compared.

DEADBAND

is added to or subtracted from the difference between INPUT andSETPOINT. It establishes a zone whereby the differential is not ofsufficient magnitude to cause a change of status at the OUTPUTterminals. The DEADBAND is always evaluated as an absolute value.

A zero deadband entry allows the OUTPUTS to respond rapidly tochanges of the INPUT signal. Values greater than zero widen thedeadband and delay output transitions.

OUTPUT_1

The function of this terminal depends on the setting of the MODEterminal and the type of signal (analog or logical) specified on thisterminal.




Default: NoneFormat: Analog or logical signalInput/Output: Output



Page Comparator-3

Normal Mode (High Select)MODE terminal is ONAnalog signal on OUTPUT_1

Whenever the absolute value of the INPUT minus the SETPOINT isgreater than DEADBAND, OUTPUT_1 is set equal to INPUT orSETPOINT, whichever is higher, i.e.

OUTPUT_1 = MAX(INPUT, SETPOINT) when:� INPUT - SETPOINT � > DEADBAND

Normal Mode (High Select)MODE terminal is ONLogical signal on OUTPUT_1

Whenever the absolute value of the INPUT minus the SETPOINT isgreater than the DEADBAND:

OUTPUT_1 is set ON if INPUT is greater than SETPOINT

� INPUT - SETPOINT � > DEADBAND and (INPUT > SETPOINT) then turn OUTPUT_1 ON.

OUTPUT_1 is set OFF if INPUT is less than SETPOINT

|INPUT-SETPOINT | > DEADBAND and (INPUT < SETPOINT) then turn OUTPUT_1 OFF

In Normal Mode, whenever the absolute value of the differencebetween the INPUT and SETPOINT is less than the DEADBAND,the module holds OUTPUT_1 and OUTPUT_2 at their currentvalues/states. No output changes will occur until the absolute valueof the difference between the INPUT and SETPOINT signalsexceeds the DEADBAND.


Page Comparator-4


Raise/Lower Mode (Lower function)MODE terminal is OFFLogical signal on OUTPUT_1 (Note: Analog signals not valid for thismode)

OUTPUT_1 is set ON whenever:

INPUT > SETPOINT + DEADBAND

Otherwise it is set to OFF.

OUTPUT_2


Normal Mode (Low Select)MODE terminal is ONAnalog signal on OUTPUT_2

Whenever the absolute value of INPUT minus SETPOINT exceedsthe DEADBAND, OUTPUT_2 is set equal to either INPUT orSETPOINT, whichever is lower.

OUTPUT_2 = MIN( INPUT, SETPOINT )

Default: NoneFormat: Analog or logical signalInput/Output: Output



Page Comparator-5

when: � INPUT - SETPOINT � > DEADBAND

Normal Mode (Low Select)MODE terminal is ONLogical signal on OUTPUT_2

Whenever the absolute value of the INPUT minus the SETPOINT isgreater than the DEADBAND:

OUTPUT_2 is set ON if INPUT is less than SETPOINT

� INPUT - SETPOINT � > DEADBAND and (INPUT < SETPOINT), OUTPUT_2 is turned ON.

OUPUT_2 is set OFF if INPUT is greater than SETPOINT

|INPUT - SETPOINT| > DEADBAND and (INPUT > SETPOINT), OUTPUT_2 is turned OFF

In Normal mode, whenever the absolute value of the differencebetween the INPUT and SETPOINT is less than the DEADBAND,the module holds OUTPUT_1 and OUTPUT_2 at their currentvalues/states. No output changes will occur until the absolute valueof the difference between the INPUT and SETPOINT signalsexceeds the DEADBAND.

Raise/Lower Mode (Raise function)MODE terminal is OFFLogical signal on OUTPUT_2 (Note: Analog signals not valid for thismode)

OUTPUT_2 is set to ON whenever:

INPUT < SETPOINT - DEADBAND

Otherwise, it is set to OFF.


Page Comparator-6


OUTPUT_3 Default: NoneFormat: Analog or logical signalInput/Output: Output


Normal Mode (High/Low Select)MODE terminal is ONAnalog signal on OUTPUT_3

OUTPUT_3 is set equal to the absolute value of the differencebetween the INPUT and SETPOINT values or:

� INPUT - SETPOINT �

Normal Mode (High/Low Select)MODE terminal is ONLogical signal on OUTPUT_3

OUTPUT_3 is set ON whenever the absolute value of the differencebetween INPUT and SETPOINT values is less than or equal toDEADBAND, otherwise it is set to OFF

� INPUT - SETPOINT � < DEADBAND, then OUTPUT_3 is ON

� INPUT - SETPOINT �� DEADBAND, then OUTPUT_3 is OFF

Raise/Lower ModeMODE terminal is OFFLogical signal on OUTPUT_3 (Note: analog signals not valid in thismode)

In this mode OUTPUT_3 is not used and it is always set to OFF.



Page Comparator-7

Normal Mode Signal Conditions

OUTPUT_1 OUTPUT_2 OUTPUT_3High Select Low Select (Input-Setpoint)

Condition Analog Logical Analog Logical Analog Logical

� IN-SP � > DB IN ON SP OFF � IN-SP � OFF& IN > SP

� IN-SP � > DB SP OFF IN ON � IN-SP � OFF& IN < SP

� IN-SP � < DB NC NC NC NC � IN - SP � ON

Key:

IN = Input ValueSP = Setpoint ValueDB = Deadband ValueNC = No change


Page Comparator-8


Raise/Lower Mode Signal Conditions

Condition OUTPUT_1 OUTPUT_2 OUTPUT_3

Lower Output:IN > SP + DB ON OFF Not Used

Raise Output:IN < SP - DB OFF ON Not Used

Hold Output:(SP - DB) < IN < (SP+DB) OFF OFF Not Used

Key:

IN = Input ValueSP = Setpoint ValueDB = Deadband Value


Page Control Stmts-1

Control Statements

Control statements provide conditional, unconditional, delay andinterrupt functions. These statements may be used with both analogand logical expressions, in the ACCOL Task. The IF, ENDIF, ELSE,and ELSEIF statements may also be used within a Calculator module.(See 'Calculator'). Sample statements a, b and c shown below are inthe proper format for various control statements in ACCOL tasks.

100 IF (Z==N&H) a) Conditional w/ logical expression101 GOTO 10 Unconditional command

102 ENDIF Command terminator

196 WAIT DELAY 2 S b) Delay command, 2 seconds

211 SUSPEND c) Interrupt command212 RESUME 101 Interrupt terminator

For more details on control statements see the following sections:

ABORTELSE (See 'IF')ELSEIF (See 'IF')ENDIF (See 'IF')FORIFGOTORESUMERWAIT DI (See 'WAIT DI')RWAIT DIH (See 'WAIT DI')RWAIT DIL (See 'WAIT DI')SUSPENDWAIT DELAYWAIT DIWAIT DIHWAIT DILWAIT FORWAIT TIME

Control Statements


Page Control Stmts-2

Control Statements

If you're using the ACCOl Interactive Compiler, any line that isincomplete or incorrect will produce an error code to the left of theline. The code will disappear when the entry is properly completed.

Code Message

T Improper or incomplete terminator for present commandinitiator

I Invalid terminator or no command initiatorO Number of conditional levels has been exceeded. Maximum of

16 levels is permitted.C Error present in Calculator blockG Invalid target for GOTO statement

Counter ModulesHSCount, LSCount, TCount, RHSCount, RLSCount


Page Counters-1

The Counter Modules accept a pulse count input and calculate fre-quency and a totalized count.

There are five types of counter modules:

High Speed Counter (HSCount)Low Speed Counter (LSCount)Remote High Speed Counter (RHSCount)Remote Low Speed Counter (RLSCount)Timer 1 Counter (TCount).

The HSCount Module obtains counts from 16-bit counters on HSCprocess I/O boards which reside within that controller. The LSCountModule obtains counts via interrupts from a discrete I/O board in thecontroller. The TCount obtains count information from the 16-bitTimer 1 in the 80186 CPU of the GFC 3308 Gas Flow Computer, andthe RTU 3305.

Counter Module Symbol Remote Counter Module Symbol

COUNTCOUNT ZEROCOUNT SPAN

FREQUENCYFREQ. ZEROFREQ. SPAN

INITIALDEVICE

ElectricalInput

RESETSTATUS

R

COUNTCOUNT ZEROCOUNT SPAN

FREQUENCYFREQ. ZEROFREQ. SPAN

INITIALDEVICE

ElectricalInput

RESET

Counter Modules


Page Counters-2


The remote counter modules RHSCount and RLSCount obtain countsfrom 16-bit counters on HSC or DI process I/O boards which reside inan RIO 3331 Remote I/O Rack (RIOR). Remote counter modules,therefore, may only be used in RTU 3310, DPC 3330, and DPC 3335controller loads because those are the only controllers equipped tocommunicate directly with an RIOR.

The table below summarizes the frequency ranges of the five countermodules and the type of 33xx unit which holds the process I/O boardcontaining the counter inputs.

33xx Unit containing process I/O board

Frequency Range: with counter inputs: Use This Module:

10 kHz or less1. 3310/30/35, 3350/80/85 HSCount

3331 RHSCount

300 Hz or less 2.

3310/30/35/05 LSCount10 Hz or less3.

3331 RLSCount

100 Hz or less 4.

3350/80/85 LSCount10 Hz or less 5.

10 kHz or less 3308/3305 TCount

1. High Speed Counter HSC input board required for 3310/30/31/35. Mixed I/O boardrequired for 3350/80/85.

2. Discrete Input I/O board must be specified with 1 milli-second filter. Also, in each 3310/30/31/35 unit, the sum of the frequencies for all low speed counter channels must be 800 Hzor less. In the 3305, there are 8 DI's with 1 milli-second filters.

3. (Continued on next page)



Page Counters-3

Counter input signal specifications for 33xx controllers may be foundin the following documents: DPC 3330 (document CI-3330); DPC 3335and RIO 3331 (document CI-3335); RDC 3350 (document D4040); UCS3380 and CFE 3385 (document D4050); GFC 3308 (document CI-3308).Application notes for each type of counter appear at the end of thissection. Module terminals are described below:

❏ Module TerminalsDEVICE(HSCount)(LSCount)

is the slot number in the card cage where the process I/O board whichprovides the counter input is installed.

High speed counter inputs in a 3350/80/85 controller are on the mixedI/O board. High speed counter inputs on a 3310/3330/3335 controlleruse a High Speed Counter board. The GFC 3308 gas flow computer,and the RTU 3305 controller have one set of counter terminals.

Low speed counter inputs in a 3350/80/85 controller could be on amixed I/O board, or a digital I/O board. Low speed counter inputs on a3310/3330/3335 controller require a digital input board. Low speedcounter inputs on the 3305 are located on the multi-function I/O board.

The DEVICE entry can be a number from 1 to 12, depending on thetype of controller. To find out the number of boards which may beinstalled in a particular controller type, see the 'Process I/O' section.

3. Discrete Input I/O board must be specified with 30 milli-second filter. Also, in each 3305/10/30/31/35 unit, the sum of the frequencies for all low speed counter channels must be lessthan 800 Hz. In the 3305 there are 6 DI's with 30 milli-second filters.

4. Discrete Input or Mixed I/O board must be specified with 3 milli-second filter.

5. Discrete Input or Mixed I/O board must be specified with 30 milli-second filter.

Default: 0 (null device)Format: ConstantInput/Output: Input


Page Counters-4


DEVICE(RHSCount)(RLSCount)

is a three digit number which identifies the RIO 3331 process I/Oboard which is being referenced by this module.

There can be up to ten RIO 3331 nodes connected to a communicationport of a 3310/3330/3335 controller, and each RIO 3331 can hold up toten process I/O boards - therefore up to 100 boards can be referencedthrough a given communications port.



The first digit indicates the serial port on the 3310/3330/3335 control-ler which is accepting data from the RIO 3331 node.


The second digit must be one less than the RIO 3331 node addresswhere the board resides. It must range from 0 to 9. (Second digit = 0




Page Counters-5

for node address 1. Second digit = 9 for node address 10.)

The third digit must be one less than the board slot. It must be aninteger from 0 to 9. (Third digit = 0 for slot 1. Third digit = 9 for slot10.)

Examples:


Process I/O board 317 is the eighth board of the second RIO 3331node which communicates to port C of the 3310/3330/3335 control-ler.

The number entered on the DEVICE terminal will be verified with theProcess I/O Menu (if you’re using the AIC) or the *PROCESS-I/Osection (if you’re using the ABC or ACCOL Workbench). This boardmust be capable of accepting counter input signals. If no board isfound in the specified slot or if the board is the wrong type, an errormessage will be generated.

INITIAL

is the number of the field wiring terminal that will be assigned to thefirst COUNT terminal. All field wiring terminal assignments forsubsequent COUNT signals entered on the module menu will auto-matically be sequenced from the initial number.

For example, if the I/O board referenced in the DEVICE field is aDigital I/O Board and the INITIAL terminal is 2, then the signalreferenced in the COUNT 1 terminal in the module menu wouldappear at the field terminal number DI2 and the signal referenced inthe COUNT_2 terminal would be referenced to DI3.

Default: 1Format: constantInput/Output: Input


Page Counters-6


STATUS(RHSCount)(RLSCount)

is set to one of the codes below based on the RHSCount or RLSCountmodule execution status.

0 Module executed successfully-1 Invalid remote device ID-2 Communication failed with remote unit-3 Remote board is missing-4 Remote board is of the wrong type-5 Remote board failed diagnostic tests -7 RIO Rack firmware incompatible with process I/O


Each counter channel has its own numbered set of module terminals.Each of these sets includes a COUNT, COUNT_ZERO,COUNT_SPAN, RESET, FREQUENCY, FREQ_ZERO, andFREQ_SPAN terminal. Note: TCOUNT has only one counter channel,and, therefore, only one set of terminals.

COUNT

is the total number of scaled input pulses counted and is added to anyinitial ‘zero’ value. When the module executes, the number of pulses(COUNTnew) since the last execution is multiplied by the COUNT_SPAN and added to the previously accumulated count (COUNTprev)(which includes the value of COUNT_ZERO).

count = countprev + ( countnew * count span )


Default: None, entry is optionalFormat: Analog signalInput/Output: Output



Page Counters-7

The COUNT_SPAN value defines the engineering units of the COUNToutput (see COUNT_SPAN below). When the COUNT_SPAN terminalis unwired it defaults to 1.0, giving COUNT, and COUNTprev units of‘pulses’.

The number of COUNT terminals on a module menu varies dependingupon what type of process I/O board contains the counter input sig-nals.

COUNT_ZERO

defines the initial COUNT value when the module is Reset. WhenCOUNT_ZERO is not 0.0 the engineering units of COUNT_ZERO andCOUNT_SPAN must be the same.

COUNT_SPAN

changes the number of pulses counted to engineering units. Forexample, if a flowmeter is providing the pulse input and each pulseequals 10 cubic feet the COUNT_SPAN would be 10.0 to make theCOUNT be in cubic feet.

RESET

halts counting and sets the COUNT output to an initial value. Whenthe signal is ON, the value of COUNT will be set equal to the value atthe COUNT_ZERO terminal. When the signal is turned OFF, thecounting will proceed from the initial value.





Page Counters-8


FREQUENCY

is the frequency of the input signal in units defined by FREQ_SPANwith an offset defined by FREQ_ZERO.

number of pulses sincetask last executed

FREQ = * freq span + freq zerotime in seconds sincetask last executed

When FREQ_SPAN is unwired, FREQUENCY is in units of pulses persecond. Otherwise, the units are determined by the FREQ_SPAN.

FREQ_ZERO

is the minimum FREQUENCY output value when the input pulse rateis zero. FREQ_ZERO must have the same engineering units asFREQ_SPAN.

FREQ_SPAN

converts the input frequency into engineering units, for example,gallons per second or cubic feet per second. If the input frequencycomes from a flowmeter with a maximum frequency of 500 pulses persecond and 10 gallons per pulse, FREQ_SPAN would be set to 10(gallons per pulse) to make the correct FREQUENCY output of 5000gallons per second.






Page Counters-9

❏ High Speed Counter Modules: (HSCount, TCount and RHSCount)

The High Speed Counter Modules count pulses at rates up to 10 kHz.

The High Speed Counter Modules receive count information from HighSpeed Counter (HSC) hardware located on the process I/O board.When the task containing the High Speed Counter Module executes,the number of pulses counted since the last task execution is deter-mined along with the time in seconds since the last execution. Thisinformation is used to compute both a totalized count output and afrequency output. During any single execution of this module, theremay be up to a +4 millisecond discrepancy apparent in the reportedcounts; this discrepancy is accounted for during the next moduleexecution.

These modules are typically used to count the pulses from turbineflowmeters; the module outputs are then used to generate correctedflow volume and flow rate.

Warning

The High Speed Counters are implemented using 16-bitcounters which roll over after 65535 counts; the task ratemust be less than the roll over time at the maximumfrequency. For example, at 10 kHz, the counter rolls overin 6.5536 seconds, therefore a task rate of 5 seconds orless would be appropriate.

Each Mixed I/O Board in the RDC 3350, UCS 3380, or CFE 3385 hastwo high speed counters. HSC Boards in an RTU 3310, DPC 3330,DPC 3335, or RIO 3331 have four counters. Each counter is an indi-vidual count channel, and the HSCount and RHSCount Module Menuscontain a set of terminals for each channel. Separate modules may beassigned for each counter, however, no single module should specifynon-contiguous counters. The TCount Module has only one counterand thus only one set of terminals. It also does not have DEVICE orINITIAL terminals.


Page Counters-10


❏ Low Speed Counters: (LSCount and RLSCount)

The LSCount and RLSCount modules may be used for applicationssuch as rain gauge measurements, viscous flow or pulse counting.

Restrictions apply on low speed counters in the 3310/30/31/35/05 units.For each 3310/30/31/35/05 the sum total of all maximum input fre-quencies must be 800 Hz or less. For example, if one channel willreceive a maximum frequency of 300 Hz and another channel 200 Hz,then either one 300 Hz channel or three 100 Hz channels could beadded, giving 800 Hz total.

The Low Speed Counter Modules contain a count location whichincrements when an interrupt occurs from the Discrete Inputs locatedon the DI process I/O board. When the module executes it reads thenumber of pulses (interrupts) counted since the last module executionand then computes the count total and frequency output.

To ensure correct frequency values at low input rates the task inwhich the LSCount or RLSCount Module is entered should have atask execution time longer than the period (1/Frequency) of theslowest input frequency expected.

The number of Low Speed Counter signals which can be entered on aLow Speed Counter module menu varies depending upon the type ofprocess I/O card which is receiving the digital inputs. A Low SpeedCounter module running in a 3350/80/85 controller could accept up to48 low speed counter signals from a digital input board. A Low SpeedCounter module referencing a digital input board in a 3310/30/31/35/05 could receive up to 8 low speed counter signals. Each counter signalis a separate channel that is processed individually. For the RTU3305, up to 8 low speed counter signals are supported, using DI points7 through 14.

CustomCustom Module


Page Custom-1

The Custom Module allows the user to configure a Bristol controller tocommunicate with other manufacturer’s programmable logic control-lers and networks. Communication with these other devices andnetworks is governed by means of a communications protocolwhich converts ACCOL signal data into a format which can be under-stood by the foreign device or network. The Custom Module allows theACCOL programmer to select which protocol should be used. For adescription of the custom communication protocols that are available,as well as other configuration information necessary for enabling theprotocols, see the ACCOL II Custom Protocols Manual (document#D4066).


Configuring the Custom Module requires only three terminal assign-ments. Terminal entries are defined in more detail in the descriptionof each protocol in the ACCOL II Custom Protocols Manual (D4066).

The MODE terminal specifies one of the interfaces listed in theaforementioned manual.

The LIST terminal specifies the number of a signal list to be used bythe Custom Module.

The STATUS terminal indicates the status of the module. A value of -1.0 indicates that the selected mode is not supported by the set offirmware being used. All other status values are explained in theACCOL II Custom Protocols Manual (D4066), or in separate docu-mentation.

❏ Port AssignmentsWhen you use the Custom Module you must also assign a Customport. The Custom port is discussed in the 'Communication Ports'section of this manual.

Custom

BLANK PAGE


Page Daccumulator-1

DaccumulatorDouble-precision Accumulator Module

The Daccumulator Module allows a set of restricted arithmetic opera-tions (addition, subtraction, multiplication, and division) to be per-formed on double-precision floating point numbers. Double-precisionarithmetic operations are useful for certain specialized flow calcula-tions, and applications.

❏ When should double-precision be used?All digital computers represent numbers as a series of 0's and 1's. Each'0' or '1' is referred to as a 'bit'. ACCOL analog (floating point) signalsin Bristol's Network 3000-series controllers use 32 such bits, and thesebits are organized according to the single-precision IEEE floating pointstandard. This industry standard provides compatibility and thenecessary degree of accuracy for most applications.

Single-precision floating point numbers, however, cannot accuratelyrepresent an arithmetic operation if the difference between the expo-nent of the most significant digit in the operands of the expression,and the exponent of the least significant digit in the operands of theexpression, is greater than 7.

Here are some examples to clarify this rule:

MODESCALE

Double-precision Internal Accumulator (Daccum)

INPUT_HIGHINPUT_LOW OUTPUT_HIGH

OUTPUT_LOW

Daccumulator


Page Daccumulator-2

Double-Precision Accumulator Module

Daccumulator

Say a metering station is recording accumulated flow totals in ananalog signal. The current total number of gallons is 623.71. A newreading of 12.274 gallons is to be added to the total.

The most significant digit in the larger number is the 6 in 623.71.Shown in exponential notation it is 6 * 102. Similarly the least signifi-cant digit in the smaller number is the 4 in 12.274 or 4 * 10-3. Thedifference between the exponents is 5, i.e. 2 - (-3) = 5. Since this is notgreater than 7, there is no difficulty in representing the result of635.984.

As a second example, say we have a station accumulating the amountof natural gas flowing in a pipeline. The accumulated total for themonth is 8,384,983.0 cubic feet. An additional 25.443 cubic feet mustbe added to the total.

The most significant digit in the larger number is the leftmost 8 in8,384,983.0. Shown in exponential notation it is 8 * 106. The leastsignificant digit in the smaller number is the 3 in 25.443 or 3 * 10-3.The difference between the exponents is 9, i.e. 6 - (-3) = 9. Since this isgreater than 7, the smaller number will lose some precision, and willbe added as 25.375, causing the result to be 8,385,008.375.

The loss of the smaller number's least significant digits is unavoidableunder the IEEE single precision floating point standard. When thesmaller number is scaled, bits 'drop off the end' of the scaled result.

If the magnitude of the larger number exceeds that of the smallernumber by 16,777,216 then the smaller number will be zero afterscaling, and it will not add to the accumulation at all. So adding 1.0 to16,777,216 will fail, as will adding 2 to 33,554,432, or 0.25 to4,194,304.

The problem is inherent in any computer using this format to repre-sent numbers, from your hand-held calculator, to a large mainframesystem.


Page Daccumulator-3


For most applications, however, this is not a major concern, sincemany instruments cannot support such precise measurements, andmany industrial applications frequently do not require such precision.

In certain cases, however, particularly in the natural gas pipelineindustry, greater precision is sometimes required. The double-preci-sion floating point system, used by the Daccumulator Module, in-creases the number of bits available for representing numbers.

The Daccumulator Module uses two terminals, INPUT_HIGH andINPUT_LOW, to hold the double precision value being used by themodule. Each of these terminals uses a single-precision ACCOL signalto hold a part of the double-precision number. Values are loaded intothe module's own internal accumulator (called daccum), and theoperation to be performed is chosen by the MODE terminal. TheSCALE terminal specifies a power of 10 by which the INPUT_HIGHterminal value is multiplied. Two output terminals, OUTPUT_HIGHand OUTPUT_LOW are used to hold the result of the module's arith-metic operations. The equations below summarize how the module'sinputs and outputs are handled.

daccum value = (daccum previous value) [choice of: +, -, *, /] ((INPUT_HIGH * 10scale) + INPUT_LOW)

OUTPUT_HIGH = integer ((daccum value) / 10scale)

OUTPUT_LOW = (daccum value) - (10scale * OUTPUT_HIGH)

❏ Module TerminalsINPUT_HIGH Default: 0

Format: Analog SignalInput/Output: Input (and output in MODE 0)

is an optional analog signal containing the most significant digits ofthe value to be loaded into, added to, subtracted from, multiplied by,


Page Daccumulator-4


Daccumulator

or divided into the value in the internal accumulator of the module(daccum.) Immediately after a load operation occurs (MODE 0), theINPUT_HIGH terminal will be cleared, and set to its default value of0. The MODE value will then be set to its default value of 1 (addition).

Any fractional portion entered on this terminal is carried into theinternal accumulator. The value on the INPUT_HIGH terminal ismultiplied by the power of 10 specified by the SCALE terminal, beforeit is used in the internal accumulator.

For example, if 5.5 is on the INPUT_HIGH terminal, and SCALE isset to 6 (106 = 1 million) then a value of 5,500,000 is used by theinternal accumulator.

INPUT_LOW Default: NoneFormat: Analog SignalInput/Output: Input (and Output in MODE 0)

is an analog signal containing the least significant digits of the valueto be loaded into, added to, subtracted from, multiplied by, or dividedinto the value in the internal accumulator of the Daccumulator Mod-ule.

Immediately after a load operation occurs (MODE 0) this terminal iscleared, and set to a value of 0.The MODE value is then set to itsdefault value of 1 (addition).

MODE Default: 1Format: Analog SignalInput/Output: Input (and Output in MODE 0)

is an optional signal used to specify which module operation should beperformed. The following are valid values for the MODE:


Page Daccumulator-5


0 Load the internal accumulator with the valueson the INPUT_HIGH and INPUT_LOWterminals. This is done as follows: daccumvalue = (INPUT_HIGH * 10scale) +INPUT_LOW. The MODE signal is then set to1 to facilitate later additions when the moduleis used to accumulate totals.

1 Add the INPUT_HIGH and INPUT_LOWterminal values to the value currently in theinternal accumulator, and store the result inthe OUTPUT_HIGH and OUTPUT_LOWterminals.

2 Subtract the INPUT_HIGH and INPUT_LOWterminal values from the value currently in theinternal accumulator, and store the result inthe OUTPUT_HIGH and OUTPUT_LOWterminals.

3 Multiply the INPUT_HIGH and INPUT_LOWterminal values by the value currently in theinternal accumulator, and store the result inthe OUTPUT_HIGH and OUTPUT_LOWterminals.

4 Divide the value currently in the internalaccumulator by the INPUT_HIGH andINPUT_LOW terminal values, and store theresult in the OUTPUT_HIGH andOUTPUT_LOW terminals.


Page Daccumulator-6


Daccumulator

SCALE Default: 6Format: Analog SignalInput/Output: Input

is an optional signal used to specify the power of 10 by which theINPUT_HIGH value is multiplied, prior to storage in the internalaccumulator.

This is also the same power of 10 by which the value in the internalaccumulator is divided, in order to store the most significant digits ofthe result on the OUTPUT_HIGH terminal. This SCALE value mustbe an integer value from -3 to 9.

OUTPUT_HIGH Default: NoneFormat: Analog SignalInput/Output: Output

is an analog signal containing the most significant digits of the resultof a load, addition, subtraction, multiplication, or division using theinternal accumulator value (daccum value). The equation used to putthe most significant digits on this terminal is shown below, the scalevalue is set using the SCALE terminal.

OUTPUT_HIGH = integer ((daccum value) / 10scale)

OUTPUT_LOW Default: NoneFormat: Analog SignalInput/Output: Output

is an analog signal containing the least significant digits of the resultof a load, addition, subtraction, multiplication, or division using theinternal accumulator value (daccum value). The equation used to putthe least significant digits on this terminal is shown below, the scalevalue is set using the SCALE terminal.


Page Daccumulator-7


OUTPUT_LOW = (daccum value) - (10scale * OUTPUT_HIGH)

NOTE: Although the internal accumulator of the module maintainsthe double-precision value, ACCOL signals, including the signal on theOUTPUT_LOW terminal are single-precision numbers; therefore theoutput on this terminal is rounded to the nearest single-precisionfloating point value.

❏ Example - Using DaccumulatorIn our previous discussion (see 'When Should Double-Precision BeUsed?') we wanted to add a value of 25.433 to an accumulated value of8,384,983.0. Using a single-precision signal, we saw that the .433portion of the result was "lost." We can prevent this loss by using theDaccumulator Module.

To perform this operation, it is necessary to carefully choose theSCALE value. If this value is too large, output values will not showthe proper degree of precision.

In this case, a SCALE value of 3 is chosen, representing a multiplier of103 (1,000). With this choice, the INPUT_HIGH and OUTPUT_HIGHterminals will show thousands of cubic feet, and the INPUT_LOW,and OUTPUT_LOW terminals will show hundreds, tens, and units ofcubic feet.

Before the module executes, the 8,384,983.0 value is in the internalaccumulator. The OUTPUT_HIGH terminal holds the result of theprevious execution, i.e. 8,384. The OUTPUT_LOW terminal holds theremainder of 983.0.

The additional 25.433 cubic feet of gas to be added to the total is puton the INPUT_LOW terminal, and the INPUT_HIGH terminal is setto 0. The MODE value is also set to the default of 1 (addition).


Page Daccumulator-8


Daccumulator

When the module executes, the result of 8385008.443 is stored in theinternal accumulator. This value is represented by a value of 8385 onthe OUTPUT_HIGH terminal, and 8.443 on the OUTPUT_LOWterminal.


Page Data Arrays-1

Data Arrays

❏ What are data arrays?Data arrays are tables that are indexed to store and retrieve data.They may be analog or logical arrays. Analog arrays hold floatingpoint numerical values and logical data arrays hold on/off status data.

❏ Read Only and Read/Write ArraysWhen an array is created, it is designated as a 'read only' or 'read/write' array.

Read only arrays are initialized with values by the ACCOL program-mer when the ACCOL load is constructed off-line. Once the ACCOLload is running, these values may be read by ACCOL modules. TheACCOL modules cannot, however, write new values into a read onlyarray.

Read/write arrays may not be initialized by the ACCOL programmerwhen constructing the load off-line. They may be manually changed(written to) on-line either using PEI software or through CALCULA-TOR statements in the ACCOL load.

Arrays may be one dimensional (1 column by n number of rows) ortwo-dimensional (n columns by m rows).

Array numbers may be placed in statements and equations. Arraysare referenced by type (analog or logical) and number (1 through 255)and are common to all tasks in the load.

❏ Array Size LimitationsUp to 255 analog data arrays, and 255 logical data arrays can becreated, assuming there is available memory space for each type ofarray. Each analog array element requires four bytes. Eight logical

Data Arrays


Page Data Arrays-2

Data Arrays

array elements require one byte. For ACCOL 5.3, all read only or allread/write arrays are limited to one segment, or 64 K bytes ofmemory. For ACCOL 5.4 and later versions, the total memory used forread only and read/write arrays is limited only by the availablememory in your controller.

In addition to the memory limitations in your controller, in any onearray, the number of rows multiplied by the number of columns (thatis, the number of array elements) cannot exceed the numbers given inthe table below:

Maximum No. of Elements For:ACCOL Software Version Level Analog Array Logical Array

5.1 through 5.8 8000 32,000

5.9 (and newer 5.x versions) 16,000 32,000

6.0 (and newer) 65,535 * 65,535 65535 * 65,535

oÿEntering Array Statements

Examples of how to enter data array statements in the CalculatorModule within the ACCOL II Interactive Compiler (AIC) are includedin the 'Calculator' section.

Examples of data array syntax in the ACCOL source file are includedin the ACCOL Workbench User Manual (document# D4051) or in theACCOL II Batch Compiler Manual, (document# D4055).

oÿEntries in Read-only Analog ArraysIf you are using the AIC, very large, or very small numbers entered asinitial values in analog read-only arrays are automatically convertedto exponential form.

colsrows rows cols


Page Demux-1

DemuxEDemux

Demultiplexer amd Extended Demultiplexer Modules

DINPUT

SELECT

OUTLIST

to signal list EDINPUT

SELECT

OUTLISTto signal list

OUTPUT_n

The Demux and EDemux Modules accept input signals and write themto the signal list specified by the OUTLIST terminal. The EDemuxModule can also write to its OUTPUT_n terminals. The destination inthe signal list or OUTPUT_n terminals is determined by the SELECTterminal.

Demux Module Symbol EDemux Module Symbol

Module TerminalsINPUT

is the module input which is applied to the signal list specified on theOUTLIST terminal. For the EDemux Module, this input can also beapplied to an OUTPUT_n terminal.

SELECT

determines the destination of the INPUT signal in the OUTLISTsignal list. For the Edemux Module, SELECT will indicate a location

Default: None, entry requiredFormat: Constant or analog, logical, or

string signalInput/Output: Input

Default: None, entry requiredFormat: Analog signal, logical signal, or

constantInput/Output: Input

Demux/EDemux


Page Demux-2

DemuxEDemuxDemultiplexer and Extended Demultiplexer Modules

in the OUTLIST signal list when the OUTLIST terminal is wired or itwill indicate one of the OUTPUT_n terminals.

If SELECT is an analog signal, its value determines the location in thesignal or terminal list. For example, if the value ranges from 1 to1.99999, the INPUT is written to the first location in the signal list orto OUTPUT_1. If SELECT is a value from 3 to 3.99999, INPUT iswritten to the third position in the list or to OUTPUT_3.

When SELECT is a logical signal and it is OFF, INPUT is written tothe first location in the list or OUTPUT_1. When SELECT is ON,INPUT is written to the second list location or OUTPUT_2.

OUTLIST

is the signal list that will receive the data from INPUT.

OUTPUT_n(EDemux)

will receive data from INPUT. When both the OUTLIST andOUTPUT_n terminals are wired, the OUTLIST takes precedence.

Default: None, entry required for DemuxModule


Default: OUTPUT_1, if OUTLIST is alsounwired

Format: Analog, logical, or string signalInput/Output: Output


Page Differentiator-1

DifferentiatorDifferentiator Module

The Differentiator Module samples an analog input signal and calcu-lates an output that is the rate of change of the input signal.

Module Terminals

INPUT

is the value to be differentiated.

RESET

resets the module. When the signal is ON, the output will be zero.When it is OFF, the module output will be the differentiated input.The module should execute with RESET turned ON before the loadbegins to execute for the first time.

SPAN

is a multiplier for conversion to other units.




RESET

OUTPUTINPUT

SPAN

Differentiator


Page Differentiator-2

DifferentiatorDifferentiator Module

OUTPUT

is the differentiated output signal. This signal represents the rate ofchange of the input signal.

Module Operation

Each time the module is executed within its rate and priority chain,the current value of the input signal is saved. The output of themodule is the difference between the previous input value and thecurrent input value, divided by the rate of execution or:

OUTPUT = x Span

Default: None, entry requiredFormat: Analog signalInput/Output: Output

Current Input Value - Previous Input Value

Sampling Interval

DiginRDigin

Digital Input and Remote Digital Input Modules


Page Digin-1

The Digital Input Modules accept discrete input signals from the DIfield wiring terminals and make these signals available to otherACCOL modules.

There are two types of digital input modules: DIGIN and RDigin andthey are very similar to each other, except, in the way they receivedata from process I/O boards.

DIGIN (DIGital INput) Modules receive digital input data from

ElectricalInputs

(hardware)

DEVICE

INITIAL

(software -digital Input signals)INPUT

ElectricalInputs

(hardware)

R

DEVICE

INITIAL

(software -digital Input signals)INPUT

STATUS

Digin Module Symbol

RDigin Module Symbol

See also: Process I/O

Digin/RDigin


Page Digin-2

DiginRDiginDigital Input and Remote Digital Input Modules

process I/O boards which reside within that controller.

RDigin (Remote DIGital INput) modules also receive digital input datafrom process I/O boards, but only from those boards which reside in anRIO 3331 Remote I/O Rack.

❏ Module TerminalsDEVICE (DIGIN) Default: 0 (null device) When the module

executes with this default, a deviceerror will be reported and nosignal processing will occur.


is the slot number in the card cage where the process I/O boards areinstalled. The board installed in the slot specified here accepts digitalinput signals from the field.

The entry at this terminal must be a number from 1 to 12 dependingon your unit model and the number of boards installed. To find out thenumber of boards which may be installed in a particular controllertype, see the 'Process I/O' section.

The board referenced in this field will be verified with the Process I/OMenu (if you’re using the AIC) or the *PROCESS-I/O section (if you’reusing the ABC or ACCOL Workbench). This board must be capable ofaccepting digital input signals. If no board is found in the specified slotor if the board is the wrong type, an error message will be generated.

DiginRDigin



Page Digin-3

DEVICE (RDigin) Default: 0 (null device) When the moduleexecutes with this default, a deviceerror will be reported and nosignal processing will occur.


is a three digit number which identifies the RIO 3331 process I/Oboard which is being referenced by this module. There can be up to tenRIO 3331 nodes connected to each communication port of a 3310/3330/3335 controller, and each RIO 3331 can hold up to ten process I/O boards - therefore up to 100 boards can be referenced through agiven communications port.



The first digit of the DEVICE indicates the communications port onthe 3310/3330/3335 which is accepting data from the RIO 3331 node:



Page Digin-4

DiginRDiginDigital Input and Remote Digital Input Modules

The second digit must be one less than the RIO 3331 node addresswhere this board resides. It must range from 0 through 9 (Second digit= 0 for node address 1. Second digit = 9 for node address 10.)

The third digit must be one less than the board slot number. It mustrange from 0 through 9 (Third digit = 0 for slot 1. Third digit = 9 forslot 10.)

Examples:



The number entered on the DEVICE terminal will be verified with theProcess I/O Menu (if you’re using the AIC) or the *PROCESS-I/Osection (if you’re using the ABC or ACCOL Workbench). This boardmust be capable of accepting digital input signals. If no board is foundin the specified slot or if the board is the wrong type, an error messagewill be generated.


is the number of the DI field wiring terminal that will be assigned asthe first INPUT terminal on the module menu. All subsequent signalsentered on this menu will automatically be sequenced from the initialnumber. For example, if the number 2 was entered, then INPUT_1corresponds to field terminal DI2 and INPUT_2 corresponds to fieldterminal DI3.

DiginRDigin



Page Digin-5

STATUS (RDigin) Default: None, entry is optionalFormat: Analog signalInput/Output: Output

is set based on the RDigin Module execution status according to thecodes listed below:

Status Code Meaning

0 module executed successfully-1 invalid remote device ID-2 communication failed with remote unit-3 remote board is missing-4 remote board is of the wrong type-5 the remote board failed diagnostic tests-7 RIO Rack firmware incompatible with process I/O


INPUT Default: None, entry requiredFormat: Logical signalInput/Output: Output

is the output of the module and the input to the next software connec-tion point, typically another module. The value of INPUT correspondsto a DI field wiring terminal.

A number of digital input (DI) signals can be entered on one of thedigital input module menus. Each INPUT terminal in the menu ispreceded by a number to identify the proper DI.

BLANK PAGE


Page Digout-1

DigoutRDigout

Digital Output and Remote Digital Output Modules

The Digital Output Modules take ACCOL digital signals and convertthem to electrical outputs that are applied to field wiring terminals ofthe process controller.

There are two types of digital output modules: DIGOUT and RDigoutand they are very similar to each other, except, in the way they specifyprocess I/O boards for data outputs.

OUTPUT

DEVICE

INITIAL

(software)

TRACKRESET

Electrical Output(hardware)

Digout Module Symbol

RDigout Module Symbol

OUTPUT

DEVICE

INITIAL

(software)Electrical Output

(hardware)

STATUS

R


Digout/RDigout


Page Digout-2

DigoutRDigoutDigital Output and Remote Digital Output Modules

DIGOUT (DIGital OUTput) Modules send digital output data toprocess I/O boards which reside within that controller.

RDigout (Remote DIGital OUTput) modules also send digital outputdata to process I/O boards, but only to those boards which reside in anRIO 3331 Remote I/O Rack. The RDigout modules may only be used inACCOL loads which run in 3310/3330/3335 controllers because onlythose controllers are equipped to communicate directly with an RIOR.

Three terminals are provided for each digital output on the process I/O board: OUTPUT, TRACK, and RESET. Each set of terminals ispreceded by a number to identify the proper signal grouping.

❏ Module TerminalsDEVICE (DIGOUT) Default: 0.0; If the module executes with

this default, no signal processingoccurs.


is the slot number in the card cage where the Process I/O Boards areinstalled. The board installed in the slot specified here generatesdigital output signals.

The entry at this terminal must be a number from 1 to 12 dependingon your unit model and the number of boards installed. To find thenumber of boards which may be installed in a particular controllertype, see the 'Process I/O' section.

The board referenced in this field will be verified with the Process I/OMenu (if you’re using the AIC) or the *PROCESS-I/O section (if you’reusing the ABC or ACCOL Workbench). This board must be capable of


Page Digout-3

DigoutRDigout


generating digital output signals. If no board is found in the specifiedslot or if the board is the wrong type, an error message will be gener-ated.

DEVICE (RDigout) Default: 0.0; If the module executes withthis default, no signal processingoccurs.


is a three digit number which identifies the RIO 3331 process I/Oboard which is being referenced by this module. There can be up to tenRIO 3331 nodes connected to each communication port of a 3310/3330/3335 controller, and each RIO 3331 can hold up to ten process I/Oboards - therefore up to 100 boards can be referenced through a givencommunications port.



The first digit indicates the communications port on the 3310/3330/3335 which is communicating with the RIO 3331 node:


Page Digout-4



The second digit must be one less than the RIO 3331 node addresswhere the board resides. It must range from 0 through 9 (Seconddigit = 0 for node address 1. Second digit = 9 for node address 10.)

The third digit must be one less than the board slot. It must rangefrom 0 through 9. (Third digit = 0 for slot 1. Third digit = 9 for slot10.)

Examples:



The number entered on the DEVICE terminal will be verified with theProcess I/O Menu (if you’re using the AIC) or the *PROCESS-I/Osection (if you’re using the ABC or ACCOL Workbench). This boardmust be capable of generating digital output signals. If no board isfound in the specified slot or if the board is the wrong type, an errormessage will be generated.

INITIAL Default: 1.0Format: ConstantInput/Output: Input

is the number of the DO field wiring terminal that will be assigned as


Page Digout-5

DigoutRDigout


the first OUTPUT terminal. All subsequent signals entered on thismenu will automatically be sequenced from the initial number. Forexample, if number 2 was entered as the INITIAL, then OUTPUT 1would correspond to field terminal DO2 and OUTPUT 2 would corre-spond to field terminal DO3.

STATUS (RDigout) Default: None, entry optionalFormat: Analog signalInput/Output: Output

is set to one of the following codes based on the RDigout moduleexecution status.

0 module executed successfully-1 invalid remote device ID-2 communication failed with remote unit-3 remote board is missing-4 remote board is of the wrong type-5 the remote board failed diagnostic tests-7 RIO Rack firmware incompatible with process I/O configured

in load. (C.01 or newer firmware should be installed in the RIO3331.)

OUTPUT Default: None, entry requiredFormat: Logical signalInput/Output: Input

is the ACCOL signal which is converted to an electrical output at thecorresponding DO field wiring terminal.

If a unit is equipped with a DO Manual Panel and the DO field termi-nal is being manually controlled with that panel, the OUTPUT signalhas no effect on the DO field wiring terminal.


Page Digout-6


Note: Only the RDC 3350, UCS 3380, and CFE 3385 controllerssupport manual panels.

TRACK (DIGOUT) Default NoneFormat: Logical signalInput/Output: Output

is set by the DIGOUT Module. When this signal is OFF, it indicatesthat the DO is being automatically controlled by the ACCOL softwareprogram. When this signal is ON, the DO is being manually controlledat the DO Manual Panel. If the unit is not equipped with a DOManual Panel, this signal will be set to OFF.

RESET (DIGOUT) Default: None, entry optionalFormat: Logical signalInput/Output: Output

tracks the state of the DO field wiring terminal in both automatic(TRACK=0) and manual (TRACK=1) modes.


Page Downloading-1

DownloadingDownloading an ACCOL Load into the 33xx Controller

There are two ways to install an ACCOL load into a 33xx-seriescontroller.* In 186-based units (except for the RTU 3305 or EGM3530-xx), an ACCOL load can be “burned into” an eraseable program-mable memory chip, called an EPROM. The EPROM is then physicallyinstalled in the unit. Information on using this method is discussed inthe Hex File Generator (HEXGEN) Manual, (document# D4084).

The other method, available for both 186 and 386EX-based units, isreferred to as downloading. Downloading is the process of transfer-ring an ACCOL load file (*.ACL file), via a communication port, intothe memory of a 33xx-series controller. All 186 and 386EX controllerssupport downloading into RAM memory; some models also supportdownloading into FLASH memory.

Global vs. LocalThere are two downloadmethods. Local download-ing means you are download-ing directly from the PC (orother supervisory computer,such as a VAX runningEnterprise Server®) into the33xx-series controller.

Global downloading meansthat the downloaded filepasses through one or morelevels of the network before itreaches the desired 33xxcontroller. The ultimatedestination of the downloadedfile is referred to as thetarget node.

*A third way in which an ACCOL load is sent to a 33xx-seriescontroller is through a sideload to a redundant backupcontroller. This process is discussed under ‘RedundancyConcepts’ later in this manual.

Downloading


Page Downloading-2

Downloading an ACCOL Load into the 33xx controller

Downloading

Global downloads require that the NETTOP or NETDEF files areaccessible.

Cold Start vs. Warm Start

In addition to the method used for downloading, it is also important toknow the condition of the controller which will receive the download.

A cold start refers to a 33xx controller which, when started, executesdiagnostics, and then sits empty, i.e. it has no ACCOL load running init, and is simply in a reset condition, waiting for a download (indicatedby its watchdog LED being ON.) This occurs if the unit is powered upfor the first time, and so has never been downloaded before, if the unithas experienced a failure, or if the unit has been manually reset (bypressing the reset button).

By default, a unit which starts up cold should be downloaded at 9,600baud, on ports A, C, G, I, or BIP 1.* Alternatively, downloading mayalso be performed through ports B, D, H, J, or BIP 2 provided theswitches on the unit are properly set. (Switch block 1, switches 2through 4). Additional restrictions may be imposed if you are down-loading to a node which utilizes expanded node addressing. (See‘Expanded Node Addressing’ later in this manual for details.) NOTE:If this is an IP node, cold start parameters must be specified viaLocalView / NetView using the RTU Configure option.

Warm start refers to a 33xx-series controller which, when started,executes an ACCOL load which was previously loaded. Provided it hasa functioning backup battery, a 33xx controller which is running anACCOL load, will save the ACCOL load, and its data, when power isturned OFF. When power is restored, the unit will resume executingthe ACCOL load running from exactly where it was, when it wasturned OFF. To download a new ACCOL load into a warm unit (whichwill overwrite the current ACCOL load, and data) the ACCOL load

*Not all units support all port types.


Page Downloading-3


currently executing in the unit must have a slave, pseudo-slave, orpseudo-slave with alarms port already defined. The baud ratedefined for this port must be the baud rate used in the download.

Once the download is complete, the port definitions of the unit will bedictated by the port definitions of the newly downloaded ACCOL load.NOTE: If the port through which the download occurred does not havethe same definition (port type, baud rate, etc.) in the new ACCOLload, as in the previous ACCOL load, communication with the unitthrough that port may not be possible; communication setup param-eters would need to be altered to conform to the new port definition, orthe communication cable may need to be moved to a different port,which is appropriately defined.

Prerequisites to DownloadingBefore attempting to download, you must have created an ACCOLobject file (.ACO) and ACCOL load file (.ACL) by using either ACCOLWorkbench, or by using a combination of other ACCOL tools such asAIC and ACLINK, or ABC, ACLINK, and a text editor.

Downloading is accomplished via any of the following programs:

Toolkit *Taskspy *AIC * (on-line mode only)DIAG (for download of diagnostic ACCOL loads only)UOI (via AccuRate Menu System, Corrector Menu

System, or user-defined menus)Downloader (available with Open BSI Utilities software)RDL * (available with Enterprise Server or Trolltalk

VAX software)

The user documentation accompanying these programs includesinstructions for starting the download operation. Before attempting to

*These tools are not available for Protected Mode 386EX(PLS00 /PLX00 firmware, or newer) or 3530 units.


Page Downloading-4


Downloading

download, however, verify that the following items have been com-pleted:

1. If global downloading will be performed, network communicationsmust already have been established, and the NETTOP or NETDEFfiles must already have been created, and released.

2. The supervisory computer must be connected (via a cable, radiointerface, modem, etc.) to the target node (for a local download) orhave a path to the master node of the target node. The connectionshould be from the appropriate port of the supervisory computer(e.g. COM1:, COM2:, etc.) to a Slave, Pseudo-Slave, or Pseudo Slavewith Alarms port on the target node, or to a node which has a pathto the master of the target node.

3. Communication setup parameters must be defined within thesoftware which will perform the download (see the CommunicationSetup Menus within the ACCOL tools software, the CommunicationLine Parameters Menu of the Open BSI Setup Tool (Open BSI 2.xand earlier users only), the COMMPORT.TXT file on EnterpriseServer, or NetView (Open BSI 3.x and newer users). These param-eters include, among other things, the port definition for the down-load port on the supervisory computer, and its baud rate.

Other menus, files, etc. in these programs may require you todefine information such as the local address of the target node, itsexpanded node addressing group number, and the target node’sname (as defined in NETTOP or NetView).

4. Switch settings (either soft switches or hardware switches/jumpers)on the target 33xx node must be adjusted correctly for the down-load, if the default port and baud rates (discussed previously) willNOT be used. See the hardware documentation accompanying each33xx device for details on these switches.*

If this is a 186-based controller, the PROM/RAM switch (SwitchBank 1, Switch #6) must be in the RAM position (RIGHT or ON).

*If your unit is a 386EX Protected Mode unit with anEthernet board, IP address and cold download parametersare initially set using the LocalView utility.


Page Downloading-5


If this is an EGM 3530 unit, the download enable/inhibit jumpermust be enabled.

If this is a 386EX-based controller or an RTU 3305, the position ofthe PROM/RAM switch depends upon how you intend to configurethe unit. This is discussed, below:

Downloading into RAM or FLASH (Units which supportFLASH)

Most 33xx controllers which support FLASH memory allow a choice ofdownloading the ACCOL load into either RAM memory* or FLASHmemory. This choice is determined based on the position of thePROM/RAM switch.

The following units support FLASH memory:

� DPC 3330, DPC 3335, and RTU 3310 with 386EX Real Mode CPUand RMS01 (or newer) firmware.

� DPC 3330, DPC 3335, and RTU 3310 with 386EX Protected ModeCPU

� RTU 3305 (requires software switch configuration instead ofphysical hardware switches)

� EGM 3530 / RTU 3530 (no PROM/RAM switch; these units alwaysstore the ACCOL load in FLASH)

RAM Option: (not applicable to 3530)Downloading into RAM on a FLASH-based unit, is accomplishedthe same way as downloading to any other 33xx unit. The PROM/RAM switch on the controller (Switch Bank 1, Switch #6) must bein the RAM position (RIGHT or ON).

FLASH Option:Downloading into FLASH is useful because although FLASH-basedunits do NOT support removable EPROMs, the download intoFLASH option allows the same cold start functionality as an

*RAM in this case refers to the load image area and dynamicworking space area; (which are both RAM) as described inChapter 7 of the AIC Manual, (document# D4042)


Page Downloading-6


Downloading

EPROM: If an ACCOL load has been downloaded into FLASH, theload file is saved, even after a watchdog or reset (cold start). Whenthe cold start occurs, the load is automatically copied from FLASH,into RAM and the load automatically starts executing.

To enable downloading into FLASH, the PROM/RAM switch on thecontroller (Switch bank 1, switch #6) must be set to the PROMposition (LEFT or OFF).*

NOTE

Because of the time required to erase the FLASH, an initialglobal download attempt may result in an error message. Asa result, it may be necessary to download twice. This isunnecessary if Open BSI Downloader (Version 3.0 or newer)is used to download.

Once the ACCOL load has been downloaded into FLASH, it may beprotected from accidental erasure (via another download) by utilizingthe LOCK option. Attempts to download to a unit which has the LOCKoption active will generate an error message, and the ACCOL loadcurrently running will be unaffected, except in the case of RTU 3305units with firmware prior to LS502. (RTU 3305 units with firmwareprior to LS502 only preserve the ACCOL load, not its associated data.)

When the PROM/RAM switch is in the PROM position, then thepreceding switch (Switch Bank 1, Switch #5) is defined as LOCK/UNLOCK. If set to the LEFT or OFF position (LOCK), the FLASHarea is protected from being overwritten by a new download. If set tothe RIGHT or ON position, a new download will overwrite the load inFLASH with the load being downloaded.

The lock option is available in 386EX Real Mode units with RMS02 ornewer firmware, and as a soft switch in RTU 3305 units. It is NOT

* 3530 units do NOT have a PROM /RAM switch.


Page Downloading-7


supported in 386EX Protected Mode units with firmware earlier thanPES03/PEX03.

For those Protected Mode units which support it (PES03/PEX03 ornewer) the LOCK option will function if and only if FLASH param-eters have been pre-configured.

Although EGM/RTU 3530 units do NOT include a LOCK switch, theydo have a download inhibit/enable jumper setting to accomplish thesame function. When in download inhibit mode, this jumper preventsaccidental erasure of the ACCOL load in FLASH. This jumper, JP4, isdescribed in section 2.2 of the CI-3530-xx manual.

Notes:When the PROM/RAM switch is in the RAM position, switch #5 isundefined.

If the PROM/RAM switch is set to PROM, but there is NOT a validload in the FLASH area, the unit will wait for download after areset. This is also true if the LOCK option is active. The LOCK onlyapplies after a valid load has already been stored in FLASH.

The maximum size for a Real Mode ACCOL load to be stored inFLASH is 112K. The maximum size for a Protected Mode ACCOLload to be stored in FLASH is 624K. The maximum size for a 3530ACCOL load to be stored in FLASH is 64K.

If you perform on-line edits, via ACCOL Workbench, the changeswill only be made to the ACCOL load in RAM; any ACCOL loadresiding in FLASH memory will remain unchanged. If the unit isthen reset, the original ACCOL load (from FLASH without anychanges) will be loaded into memory. Such a situation will causeyour changes to be lost.


Page Downloading-8


Downloading

IMPORTANT

Be sure the PROM/RAM switch is set to the position whichreflects your desired system configuration. In order for thecold start functionality described previously to work, theswitch must also be in the PROM position (LEFT or OFF) atthe time when the cold start occurs. If, for example, youchange the switch position in order to download a diagnosticload into RAM, during system debugging, be sure to returnthe switch to its original position, before resetting the unit,or else it will be unable to use the load residing in FLASH,and will sit idle, waiting for a download.

Similarly, be sure that if you intend to download into RAM,that the PROM/RAM switch is in the RAM position (RIGHTor ON).

If you want to prevent the accidental overwriting of the loadalready in FLASH, use the LOCK feature (if your unitsupports it.)

Also, be careful about leaving one load running in RAM, andhaving a second load, residing in the FLASH area. If the unitloses power, and recovers (warm start) the RAM load willresume executing. If a watchdog occurs, or the unit resets(cold start) the RAM load will be lost, and either the FLASHload will be copied in RAM, or the unit will come up idle,depending upon the switch position, therefore:

IT IS RECOMMENDED THAT YOU EXERCISE EXTREMECARE WHEN CHANGING THE SETTING OF THE PROM/RAM SWITCH. SETTING IT IMPROPERLY COULD LEADTO ACCIDENTAL DESTRUCTION OF THE ACCOL LOAD,OR COULD LEAD TO THE WRONG LOAD BEING EX-ECUTED AT START-UP.


Page Downloading-9


The table, which follows, summarizes the differences between down-loading into RAM and downloading into FLASH. It also shows, forpurposes of comparision, the use of removable EPROMs, however,these are NOT downloadable.

Loading Method: Units WhichSupport thismethod:

Effect of a Resetor Watchdog(Cold Start)

Effect of aPower FailureRecovery(Warm Start)

Effect of a NewDownload(WarmDownload)

ACCOL load downloadedinto RAM memory.PROM/RAM switch mustbe in RAM position(RIGHT or ON.)

RDC 3350, UCS 3380,CFE 3385,GFC 3308, DPC 3330,DPC 3335, RTU 3310,RTU 3305

Any running ACCOLload is lost, and anyaccumulated data is lost.Unit executes self-test,and then must be re-downloaded.

Provided that thebackup battery isfunctioning, theACCOL load restartsfrom where it leftoff, no accumulateddata is lost.

Unit resets but does notperform self-test. Anyrunning load andaccumulated data arelost. The unit waits forcompletion of the newdownload.

ACCOL load "burnedinto" removable EPROM.PROM/RAM switch mustbe in PROM position(LEFT or OFF.)

RDC 3350, UCS 3380,CFE 3385, GFC 3308, and186-based versions ONLYof: RTU 3310, DPC 3330,and DPC 3335

Unit performs self-test.The ACCOL load thenrestarts, and anyaccumulated data is lost.

Same as above Unit resets but does notperform self-test. TheACCOL load isrestarted, however anyaccumulated data is lost.

ACCOL load downloadedinto FLASH memory.PROM/RAM switch (ifsupported) must be inPROM position (LEFT orOFF.) Also, if supported,the LOCK / UNLOCKswitch (or downloadinhibt/enable jumper for3530) must be in theUNLOCK (downloadenable) position.

RTU 3305, 3530-series and386EX-based versonsONLY of: RTU 3310,DPC 3330, DPC 3335.

Requires RMS01 /LS500/TFA01/TRA01PLS00/ PLX00 (or newer)firmware.

Same as above. Same as above Unit resets but does notperform self-test. Theexisting load and anyaccumulated data is lost.The unit will wait forcompletion of the newdownload.

BLANK PAGE

EAStatusExpanded Addressing Status Module


Page EAStatus-1

The EAStatus Module is required when using the Expanded Address-ing feature. (See 'Expanded Addressing', later in this manual.) It isused to turn communications on-line/off-line with individual slavenodes on an EAMaster port. It may also be used to report on the dead/alive status of these nodes.

An EAStatus Module must be defined for each Expanded AddressingMaster port in a load. The Expanded Addressing Master Port to whichthe module applies is specified on the PORT terminal. If no EAStatusModule with the correct port number is present in the load for anExpanded Addressing Master port, the #LINE.nnn logical alarmsystem signal for the port will be set to ON. No communications willoccur on the port.

This module is non-executing and should be placed in ACCOL Task 0.

PORT

NODE_ARRAY

LIST

ARRAYEAStatus STATUS

❏ On-line/Off-line ControlEach slave node on a Master or Expanded Addressing Master portcan be set to either On-line or Off-line. No messages are transmittedto an Off-line node. Typically a node would be set to Off-line if it hasbeen configured in the network design, but has not yet been physicallyconnected.

A node might also be set to Off-line if it has been temporarily taken

EAStatus


Page EAStatus-2


out of service. Setting such nodes Off-line prevents unnecessarymessage traffic and use of processing resources, and makes communi-cations with active nodes more efficient.

For an Expanded Addressing Master port the standard logical nodearray, designated via the #NDARRAY system signal, applies to theOn-line/Off-line status of the virtual nodes. Setting a virtual node Off-line stops communications with all slave nodes associated with it. Thisprovides a quick mechanism to take an entire group of ExpandedAddressing Slave nodes Off-line.

A second logical node data array, assigned on the NODE_ARRAYterminal of the EAStatus module, is required to control the On-line/Off-line status of each individual slave node below the virtual nodes.This second logical data array is required in order for the ExpandedAddressing Master port to function.

❏ Dead/Alive Status

Each slave node on a Master or Expanded Addressing Master porthas a status of either Dead or Alive. A node is classified as Dead after3 consecutive response timeouts. A Dead node is polled periodically,and is reclassified as Alive if it responds, however, normal polling andmessage transmissions (other than Download) do not apply to a Deadnode. See the Network 3000 Communication User’s Guide (document#D4052) for details of the BSAP polling algorithm.

For an Expanded Addressing Master port the #NODE.nnn systemsignals apply to the virtual nodes. The #NODE.nnn signal for a virtualnode is turned ON whenever an Expanded Addressing Slave nodeassociated with that virtual node is changed from Alive to Dead, i.e. itindicates that one or more of its EASlave nodes is Dead. The#NODE.nnn signal is turned OFF whenever an On-line node goesfrom Dead to Alive and all other On-line nodes below that virtual nodeare also Alive.



Page EAStatus-3

While the #NODE.nnn signal for a virtual node can report that someEASlave node of a virtual node is Dead, it does not indicate which onehas failed. To allow determination of which EASlave has failed, a listof logical signals, or a second logical node array may be configured.

This second set of logical signals, assigned on the LIST terminal of theEAStatus module (or a second read/write logical data array, assignedon the ARRAY terminal of the EAStatus module) may optionally beconfigured to indicate the Dead/Alive status of all EASlave nodesbelow all virtual nodes.

NOTE

If the user sets all Dead node(s) associated with a virtualnode to Off-line, the user should also set the #NODE.nnnsignal for the virtual node to OFF.


PORT Default: None, entry requiredFormat: ConstantInput/Output: Input

is the number of the Expanded Addressing Master port for which thismodule will control on-line/off-line status of EAslave nodes. Enter oneof the following numbers to identify the Expanded Addressing Masterport:

1 = Port A 7 = Port G2 = Port B 8 = Port H3 = Port C 9 = Port I4 = Port D 10 = Port J5 = BIP 16 = BIP 2


Page EAStatus-4


NODE_ARRAY Default: None, entry requiredFormat: Analog signal or constantInput/Output: Input

is the number of the logical data array to be used as the On-line/Off-line node array for the EASlave nodes on the port indicated at thePORT terminal. This array is required. If the terminal is unwired, ordoes not specify a valid logical data array, all slave nodes on the portare considered to be Off-line. The #LINE.nnn logical alarm signal forthe port will be set to ON, and the STATUS terminal of the EAStatusModule (if not unwired) will be set to -1. No communications will occuron the port.

This array must be sized based on the number of virtual nodes and themaximum number of nodes configured below each virtual node:

No. of VN’s X High EASlave Address = Total Array Elements

Note that High EASlave Address is the value specified on the Commu-nications Configuration Menu of AIC, or in the *COMMUNICATIONSsection of the ACCOL source file. The number of virtual nodes can bederived from the High Slave Address value for the Expanded Address-ing Master port and its position relative to other Master or ExpandedAddressing Master ports in the load.

For example in the port configuration shown below:

Port A: Master High Slave Adr: 4Port B: Exp. Master High Slave Adr: 6

High EASlave Adr: 32Port C: Exp. Master High Slave Adr: 8

High EASlave Adr: 127

The number of virtual nodes on Port B is 2 (node addresses 5 and 6),and the High EAslave Address is 32. The array size required is there-fore:

2 X 32 = 64 elements



Page EAStatus-5

The number of virtual nodes on Port C is 2 (node addresses 7 and 8),and the High EASlave Address is 127. The array size required istherefore:

2 X 127 = 254 elements

The standard ACCOL array processing method proceeds from row 1,column 1, across the entire row, before proceeding to column 1 of row2.

For ease of reference, it is suggested that the array be set up as HighEASlave Address No. of Columns X No. of virtual nodes Rows. Withthis setup, each row corresponds to a group (Row 1 = Group 0, Row 2= Group 1, etc.) Also, each column position directly correlates to anEASlave node address, i.e. column 1 corresponds to the node withlocal address 1, column 2 corresponds to the node with local address 2,etc. The figure, below, illustrates a typical array:

Group 0

Group 1

Addr 1 Addr 2 Addr 3 Addr 127. . .

. . .

Column 1 Column 2 Column 3 Column 127

Row 1

Row 2

ON

OFF

ON

OFF

OFF OFF

OFFON

If it is set up as a single dimension array, then the Row for a particu-lar node must be calculated using the following formula:

(Group No. X High EASLave Address) + Node No.

where group numbering always starts at 0 for the first virtual node onan Expanded Addressing Master Port.


Page EAStatus-6


For our example Port C shown earlier, if a single dimension arraywith 254 Rows and 1 Column were used, then to set node 50 under thesecond virtual node to either On-line (1) or Off-line (0), its Row wouldbe calculated as:

(Group # X High EASlave) + Node ( 1 X 127) + 50 = Row 177

Any node beyond the range of the array will be considered to be Off-line. For example, if an array having only 200 elements were assignedfor Port C above, the last 54 nodes under the second virtual nodewould be considered to be Off-line.


is the number of a Signal List containing a logical signal for each slavenode on the Expanded Addressing Master port. These signals are theequivalent of the #NODE.nnn signals and will be set ON to indicatethat the corresponding slave node is “Dead”, and will be set OFF toindicate that the slave node is “Alive”. These signals can be logicalalarm signals. If a non-logical signal is in the list, or if there are notenough signals in the list, no status for the corresponding node will beset.

This list must be sized based on the number of virtual nodes and themaximum number of nodes configured below each virtual node:

No. of VN’s X High EASlave Address = Total List Elements

See the examples above under NODE_ARRAY.

This list is optional. If the LIST terminal is unwired, or if no listexists, or if the specified list is empty, the ARRAY terminal will beexamined.



Page EAStatus-7

If both LIST and ARRAY are either unwired or invalid, a warningstatus of 1 will be reported on the STATUS terminal.

ARRAY Default: NoneFormat: Analog signal or constantInput/Output Input

is the number of a read/write logical data array containing an elementfor each slave node on the Expanded Addressing Master port. TheARRAY terminal is only examined if the LIST terminal is unwired ordoes not specify a valid list. The array must be read/write; a read-onlyarray will be considered invalid. The elements in this array will be setON to indicate that the corresponding slave node is “Dead”, and willbe set OFF to indicate that the slave node is “Alive”.

This array must be sized based on the number of virtual nodes and themaximum number of nodes configured below each virtual node:

No. of VN’s X High EASlave Address = Total Array Elements

See the examples above under NODE_ARRAY. If there are not enoughelements in the array, no status for the corresponding node will be set.

This array is optional. If both LIST and ARRAY are either unwired orinvalid, a warning status of 1 will be reported on the STATUS termi-nal.


is set to one of the following status codes:


Page EAStatus-8


Code Description

1 No Valid Dead/Alive Status List or Array(Warning Only)

0 No Errors or Warnings -1 No On-line/Off-line Array (Fatal Error) -2 Expanded Memory structures missing or

invalid (Fatal Error). NOTE: The -2 errorshould never occur. These structures areautomatically allocated when the ACCOLload is created. This error would indicatea corrupted load.


Page EIntegrator-1

EIntegratorExtended Integrator Module

This module computes an integral approximation using the trapezoi-dal technique.

The integral value can be reset via the RESET terminal, and a ZEROinput allows an initial value to be established prior to starting integra-tion. The module performs all internal accumulations in double-precision floating-point and then converts the accumulation to single-precision before moving it to the OUTPUT signal. The accumulation isthus limited in size only by the resolution of the maximum double-precision floating point number.

Module Terminals

INPUT

is the analog signal to be integrated

RESET

will initialize the output and the internal integral when set ON.

Default: None, entry requiredFormat: Analog signalInput/Output: Input


SPANZERO

OUTPUTINPUT

RESET

E

EIntegrator


Page Eintegrator-2


When RESET is first set ON, the internal integrator is set equal to theZERO terminal, but the OUTPUT is updated with the newest integralso that no data is lost. Save the newest output and turn RESET OFFbefore the module executes again.

If RESET is held ON for two or more module executions, OUTPUTwill be set equal to the ZERO terminal and integration will not occur.

ZERO

is used to specify the initial accumulation and output value when themodule is reset.

SPAN

is used to scale the INPUT signal so that integration occurs in thecorrect engineering units. For example, if the input signal representsa flow rate value ranging from 100 to 900 gallons per hour and theEintegrator is sampling the input every second, then the SPAN shouldbe 1/3600 (hours per second) to make each sample in units of gallons.If the input is in units of gallons per day, however, the SPAN would be1/86400 (days per second).

OUTPUT

is the integral (sum) of all the input samples

Default: 0.0Format: Analog signalInput/Output: Input




Page EIntegrator-3


Module Operation

The EIntegrator approximates the following integral:

tOUTPUT = ( SCALED INPUT) dt

tr

where: tr is time of last reset

The output of the EIntegrator is expressed by the equation:

Last INPUT + INPUTOUTPUT = Last OUTPUT + �TIME * SPAN *

2

where �TIME is the time in seconds since the last module execution.This may not be the same as the assigned task rate if the system isbusy enough to experience task rate slippage.

On each execution this module computes the average of two inputsignal readings, multiplies by the time in seconds since the modulelast executed, multiplies again by a scaling factor, and adds the resultto an accumulating sum of previous scaled readings. The module thusapproximates an integral, with the degree of fineness controlled by therate of execution.

The very first execution of the module uses a 'Last INPUT' of 0, unlessthe RESET terminal is turned ON during the first execution only, inwhich case 'Last INPUT' will use whatever value is entered on theZERO terminal. Users should take this under consideration if they donot want an initial 0 included in the above calculation.

The figure on the next page illustrates the output of the module overtime with a fixed signal value of 1.0 applied to the input. The verticalaxis is the output (1 to 5 units), and the horizontal axis is the time


Page Eintegrator-4


period (1 to 6 seconds). The module executes every second.

In the lower left corner of the graph the initial output is zero and thetime is zero. After one second, the integral is 0.5 and thus the moduleoutput is 0.5. With the second execution, the average input value 1.0 isadded to the integral value of 0.5 giving an output of 1.5 units. At thethird execution the input value 1 is again added to the integral givingan output value of 2.5. Each execution the integral value will increaseby 1.0 until the module is reset.

The module output increases every second in stair-step fashion; alinear output plot is obtained by connecting each step. The input willonly be sampled when the module executes; if it is a time-varyingsignal the execution rate must be set to sample fast enough to notmiss important data.

5

4

3

2

1Input =1 unit

units

1 2 3 4 5 6

Plotted

Integrated Output

Output

time


Page Encode-1

EncodeEncode Module

The Encode Module is a general purpose, multifunction unit. Itsfunction is determined by the value of the SELECT terminal. Validentries for the module terminals will vary depending on the functionselected.

This module will do the following:

- Convert a string signal to analog values- Convert analog values to a string signal- Convert packed Julian date/time to analog values- Convert analog values to packed Julian Date/Time- Convert system date/time to analog values- Convert analog values to system date/time- Check external battery status (GFC 3308 or RTU 3305 only)- Shift rows or columns of an analog read/write array- Convert sequences of logical signals in lists or arrays into an equiva-

lent decimal value.- Convert a decimal value into logical on/off state sequences in a list of

logical signals or a logical array row or column.

Each function is described in detail on the pages that follow:

LISTARRAY

TYPE

INDEXINPUT_n

STATUS

SELECT

EncodeMODE

Encode


Page Encode-2

EncodeEncodeEncode Module

Function 1: Convert string signal to analog values

When function 1 is indicated on the SELECT terminal, the EncodeModule converts each character in the string signal named on theINPUT_1 terminal to its equivalent decimal floating point value. (Seethe ASCII/analog conversion table at the end of this section.)

The analog values are stored in either the signal list named on theLIST terminal or the analog read/write data array named on theARRAY terminal. When the ARRAY terminal is used, the destinationrow or column is specified with the MODE and INDEX terminals.

SELECT Default: None, entry requiredFormat: Analog signal or constantInput/Output: Input

is a function code. Must be equal to 1 to execute Function 1.

LIST Default: ARRAY is used if LIST is unwired orinvalid; LIST is used if both LIST andARRAY are wired.


is the number of a signal list which is the destination for the string-to-analog conversion. It must contain only analog signals.

The minimum number of signals should be one more than the numberof characters in the string to allow for the string terminator which is0.0. If the list is shorter than this, the string data will be truncated atthe right.

Translation stops when the result of the string-to-analog conversion is0.0.


Page Encode-3

EncodeEncode Module

Function 1 (Continued)

ARRAY Default: ARRAY is used if LIST is unwired orinvalid; LIST is used if both LIST andARRAY are wired.


is the number of an analog read/write array which is the destinationfor the string-to-analog conversion.

The minimum number of rows (if column mode is selected) or columns(if row mode is selected) should be one more than the number ofcharacters in the string signal to allow for the string terminator whichis 0.0. If the row or column is shorter than this, the string data will betruncated at the right.

Translation stops when the result of the string-to-analog conversion is0.0.

TYPE Default: OFFFormat: Logical signalInput/Output: Input

is the type of the data array referenced by the ARRAY terminal. AFALSE or OFF state indicates an analog array will be used. OFF isthe only valid entry for this terminal when using Function 1.

MODE Default: OFFFormat: Logical signalInput/Output: Input

is the access mode of the data array referenced by the ARRAY termi-nal. FALSE or OFF indicates row, while TRUE or ON indicatescolumn.


Page Encode-4



INDEX Default: 1Format: Analog signal or constantInput/Output: Input

is the number of the row or column in the data array (specified by theARRAY terminal) where the analog values will be stored.

STATUS Default: None, entry optionalFormat: Analog signalInput/Output: Output

is a status code which corresponds to one of the following:

0 = Successful module execution.1 = the SELECT terminal is 0, unwired, or references an

undefined function.2 = Both the LIST and ARRAY terminals are unwired or reference

unknown structures.3 = Invalid input signal or array type for selected function or one or

more required signals are unwired.4 = Attempt to write to a read-only data array or to a control

inhibited signal.5 = INDEX <0 or > selected array dimension.6 = Invalid data: Data not consistent with signal type.

INPUT Default: None, entry requiredFormat: String signalInput/Output: Input

INPUT_1 is the source string signal. INPUT_2 through INPUT_255are not used by Function 1, and will be ignored.


Page Encode-5

EncodeEncode Module

Function 2: Convert analog values to string signal

When Function 2 is indicated, the Encode Module converts a series ofanalog signals or values to ASCII code, and stores them in an ACCOLstring signal. This may be useful when you wish to reconstruct astring after editing its parts.

The Encode Module performs the conversion on a series of analogvalues from the signal list named on the LIST terminal or from theanalog data array named on the ARRAY terminal. The resultantstring of characters is stored in the string signal named at the INPUT_1 terminal.

Analog values outside the range of 0 to 255 are converted to an integervalue and then truncated to the least significant 8-bits. Analog valuesoutside the range of printable ASCII characters (less than 32 orgreater than 126) are considered invalid and will cause the STATUSterminal to be set to 6 (invalid data), however the value is stored inthe string and the conversion will continue.

See the table at the end of this section for the hexadecimal and deci-mal values of the ASCII character codes and their equivalent analogvalues.


Must be equal to 2 to execute Function 2.



is the number of a signal list which is the source of data for the


Page Encode-6



analog to string conversion. It must contain only analog signals.

The conversion is terminated when all elements in the signal list havebeen processed, or the maximum defined length of the target stringhas been reached, whichever occurs first.



is the number of an analog data array which is the source of data forthe analog to string conversion.

The conversion is terminated when all elements in the row or columnhave been processed, or the maximum defined length of the targetstring has been reached, whichever occurs first.


is the type of the data array referenced by the ARRAY terminal. AFALSE or OFF state indicates an analog array will be used. OFF isthe only valid selection for this terminal when using Function 2.




Page Encode-7

EncodeEncode Module



is the row or column in the data array referenced by the ARRAYterminal to be processed by the module.



0 = Successful module execution.1 = The SELECT terminal is 0 or unwired, or references an




inhibited signal.5 = Index error: The INDEX terminal value is less than or equal to

zero or is greater than the selected array dimension.6 = Invalid data: Data not consistent with signal type.

INPUT_1 Default: None, entry requiredFormat: String signalInput/Output: Output

INPUT_1 is the destination string signal. INPUT_2 through IN-PUT_255 are not used by Function 2, and will be ignored.


Page Encode-8


Function 3: Convert packed Julian date/time toanalog values

When the SELECT terminal value is set to 3, the Encode Moduleconverts the Julian Date/Time signal named on the INPUT 1 terminalto six analog floating point values. The results of the translation arestored in either a signal list named on the LIST terminal or an analogread/write data array named on the ARRAY terminal. Data willappear in the following order: year, month, day, hours, minutes, andseconds.

The LIST terminal will be used by the module if it is wired to a validsignal list. If neither of these conditions is true, the ARRAY terminalwill be used if it is valid. If both the LIST and ARRAY terminals arevalid, the module will default to the LIST terminal.

You must have AC PROMS (or later) to use this function.


Must be 3 to execute Function 3.



is the number of a signal list which is the destination for the packedJulian to analog date/time conversion. It must contain only analogsignals.

The list should contain six signals. The first signal will contain the


Page Encode-9

EncodeEncode Module


year. Subsequent signals will contain the month, day, hours, minutesand seconds respectively. The module can, however, operate withfewer than six signals but some conversion data will be lost.



is the number of an analog read/write array which is the destinationfor the packed Julian to date/time conversion.

Six data cells are required in the data array. The first cell will containthe year. The second and subsequent cells will contain the month, day,hours, minutes and seconds respectively. The module can, however,operate with fewer than six cells, but some conversion data will belost.


is the type of the data array referenced by the ARRAY terminal. AFALSE or OFF state indicates an analog array will be used. OFF isthe only valid selection for this terminal when using Function 3.




Page Encode-10




is the number of the row or column which will contain the results ofthe conversion.








zero or is greater than the selected array dimension.

INPUT Default: None, entry requiredFormat: Analog signalInput/Output: Input

INPUT_1 is the source packed Julian analog signal. INPUT_2 throughINPUT_255 are not used by Function 3 and will be ignored.


Page Encode-11

EncodeEncode Module

Function 4: Convert analog values to packed Juliandate/time

When the SELECT terminal is set to 4, the Encode Module converts aseries of analog values to the equivalent packed Julian value. Theanalog values to be converted are obtained from the signal list namedat the LIST terminal, or from the analog data array named at theARRAY terminal. The results of the conversion are stored in theanalog signal named on the INPUT_1 terminal.

You must have AC PROMS (or later) to use this function.





is the number of a signal list which is the source data for the analogdate/time to Julian conversion. It must contain only analog signals.

There must be at least six signals in the list and they must convert toa valid date/time or no conversion will take place, and STATUS code 6will be returned. If the entry in the signal list references a date priorto January 1, 1978, the conversion will not take place, and STATUScode 6 will be returned.


Page Encode-12





is the number of an analog data array which is the source data for theanalog to Julian conversion.

There must be at least six entries in the array and they must convertto a valid date/time or no conversion will take place, and STATUScode 6 will be returned. If the entry in the array references a dateprior to January 1, 1978, the conversion will not take place, andSTATUS code 6 will be returned.


is the type of the data array referenced by the ARRAY terminal. AFALSE or OFF state indicates an analog array, which is the only validentry for this terminal when using Function 4.




Page Encode-13

EncodeEncode Module



is the number of the row or column in the data array referenced by theARRAY terminal.





unkown structures.3 = Invalid input signal or array type for selected function or one or



zero or is greater than the selected array dimension.6 = Invalid data: Data not consistent with selected function, e.g.

month is less than 1 or greater than 12.

INPUT_1 Default: None, entry requiredFormat: Analog signalInput/Output: Output

is the destination for the packed Julian analog signal. INPUT_2through INPUT_255 are not used by function 4 and will be ignored.


Page Encode-14


Function 5: Convert system date/time to analogvalues

When the SELECT terminal value is set to 5, the Encode Moduleconverts the system date and time in the order year, month, day,hour, minute, and second to floating point numbers. The floating pointvalues are stored in either the signal list named on the LIST terminal,the data array named on the ARRAY terminal, or the list of moduleinterleaved signals on the INPUT terminal.

You must have AD.00 PROMS (or later) to use this function.



LIST Default: If LIST is not wired, ARRAY is used.When ARRAY and LIST are not wired orare not valid, INPUT is used.


is the number of a signal list which is the destination for the systemdate and time values. The first six signals in the list are set to thevalue of the system date and time. The signals in the list must beanalog.

If a valid signal list or data array is not specified, the results of theconversion are stored in the INPUT terminals.


Page Encode-15

EncodeEncode Module


ARRAY Default: None; if LIST is unwired or invalid,ARRAY is used. If both ARRAY andLIST are unwired or invalid, INPUT isused.


is the number of an analog read/write array which is the destinationfor the system date and time values. The first six cells in the selectedrow or column (indicated by MODE and INDEX) are set to the value ofthe system date and time.


is the type of the data array referenced by the ARRAY terminal. AFALSE or OFF state indicates an analog array which is the only validselection for this terminal when using Function 5.




is the number of the row or column to be processed in the data arrayreferenced by the ARRAY terminal.


Page Encode-16







unknown structures, and there are no INPUT signals.3 = Invalid input signal or array type for selected function or one or



zero or is greater than the selected array dimension.

INPUT Default: None, when ARRAY and LIST are notwired or are not valid, INPUT is used.

Format: Analog signalsInput/Output: Output

INPUT_1 through INPUT_6 are the destination for the system dateand time values. The first six INPUT terminals are set to the value ofthe system date and time. These signals must be analog. INPUT_1must be wired. If any of the INPUT_2 through INPUT_6 terminals areleft unwired, portions of the date/time associated with the unwiredterminals will not be stored.


Page Encode-17

EncodeEncode Module

Function 6: Convert analog values to systemdate/time

This function resets the system date/time with values provided by sixanalog signals or array cell values which represent the year, month,day, hour, minute, and second, in that order. If you’re using analogsignals for the source of the date and time, they must be included inthe signal list named on the LIST terminal, or in the module's inter-leaved signals on the INPUT terminals. If you’re using an array, thearray must be specified on the ARRAY terminal; the type of array isspecified using the TYPE terminal, and the row or column is specifiedon the MODE and INDEX terminals.

You must have AD.00 PROMS (or later) to use this function.

If a valid list is specified with the LIST terminal, the signal values inthat list are used to create the system date and time. If no valid list isspecified, and a valid data array is specified on the ARRAY and TYPEterminals, then the system date and time will be created from thevalues in that data array. If neither a list nor an array is specified, theINPUT terminals are used to make the system date and time. If anyof the date/time values are missing (for example, the list or array istoo short or if all the required INPUT terminals have not been filledin) any missing value will default to the current system date/timevalue. NOTE: The year value must range from 1978 to 2077. (If theyear is after 2077 - it’s time you upgraded your software!)




Page Encode-18



LIST Default: If LIST is not wired, ARRAY is used.When ARRAY and LIST are not wired orare not valid, INPUT is used.


is the number of a signal list which is the source for setting the systemdate and time. The first six signals in the list must be analog andrepresent the year, month, day, hour, minute, and second.

Missing values default to the original system date/time values.

ARRAY Default: If LIST is unwired, ARRAY is used. IfARRAY and LIST are unwired or in-valid, INPUT is used.


is the number of an analog read/write array which is the source forsetting the system date and time. The first six cells in the selected rowor column represent the year, month, day, hour, minute, and second.

Missing values default to the original system date/time values.


is the type of the data array referenced by the ARRAY terminal. AFALSE or OFF state indicates an analog array will be used. An analogarray is the only valid selection when using Function 6.


Page Encode-19

EncodeEncode Module





is the number of the row or column to be processed in the data arrayreferenced by the ARRAY terminal.



0 = Successful module execution.1 = The SELECT terminal is 0 or unwired, or references an undefined

function.2 = Both the LIST and ARRAY terminals are unwired or reference

unknown structures, and there are no valid INPUT signals.3 = Invalid input signal or array type for selected function or one or

more required signals are unwired.4 = Attempt to write to a read-only data array or to a control inhibited

signal.5 = Index error: The INDEX terminal value is less than or equal to

zero or is greater than the selected array dimension.6 = Invalid data: Data not consistent with selected function, e.g.

month=13, or hour=29.


Page Encode-20



INPUT Default: None. When ARRAY and LIST areunwired, or are invalid, input is used.

Format: Analog signalInput/Output Input

INPUT_1 through INPUT_6 are used as the source for the systemdate and time. The first six INPUT signals must be analog signals andcontain the system date and time in the following order: year, month,day, hour, minute, and second. Missing values will default to theoriginal system date/time values.


Page Encode-21

EncodeEncode Module

Function 7: Check input power status (GFC 3308 orRTU 3305 only)

When Function 7 is selected, the Encode Module checks the status ofthe flow computer's external battery. The result of this check isreported on the INPUT_1 terminal.

This function is supported only in the GFC 3308 and the RTU 3305. Ifthis function is selected in any other controller it will cause an errorvalue of 1 to appear on the STATUS terminal.

SELECT Default: None, entry is requiredFormat: Analog signal or constantInput/Output: Input

must be 7.

LIST

This terminal is not applicable to Function 7.

ARRAY


TYPE


MODE


INDEX



Page Encode-22



STATUS Default: None, entry is optionalFormat: Analog signalUsage: Output

The value of this signal is set to reflect the status of the moduleexecution.

0 = Successful module execution.

1 = The SELECT terminal is 0, the SELECT terminal is unwired,Function 7 is not supported in this controller, or an undefinedfunction is referenced.

3 = Unwired or invalid signal on INPUT_1.

INPUT_1 Default: None, entry is requiredFormat: Analog or Logical signalInput/Output Output

When INPUT_1 is a logical signal, On indicates the external power isabove a predetermined level. OFF indicates it is below that level.

When INPUT_1 is an analog signal, 1.0 indicates the input voltage isabove a predetermined level and 0.0 indicates the input power isbelow a predetermined level.


Page Encode-23

EncodeEncode Module

Function 8: Shift Rows/Columns of an Analog Array

When Function 8 is indicated on the SELECT terminal, the EncodeModule shifts the rows or columns of an analog read/write array. Thisfunction provides an efficient way of moving array data on a row orcolumn basis.

The entire array contents can be shifted or a limited number of rowsor columns can be shifted, depending on the INDEX terminal.

Note: This function is not supported by redundant controllers,if selected in a redundant controller, error code 1 will appearon the STATUS terminal.

Note: 3310/30/35 PROMS prior to AJ.00 will return error code 1when function 8 is selected.

SELECT Default: None, entry is requiredFormat: Analog signal or constantInput/Output: Input

must be equal to 8.

LIST


ARRAY Default: OFFFormat: Analog Signal or constantInput/Output: Input

is the number of the data array to be manipulated by the EncodeModule. It must be an analog read/write array.


Page Encode-24




determines the direction of the shift.

When the TYPE is OFF, the following conditions apply:

1. Depending on the value of the MODE terminal, either rows orcolumns are shifted.

2. All data beginning with row/column 1, through to the row/column specified on the INDEX terminal, is shifted forward 1row/column. Special case: If the value on the INDEX terminal iszero, every row/column except the last one in the array is shifted.

3. When the shift occurs, data in row/column (INDEX+1) isoverwritten. Special case: If the value on the INDEX terminal iszero, the data in the last row/column of the array is overwritten.

4. When the shift occurs, data in row/column 1 is initialized to 0.0

1 2 3 4 5 1 2 3 4 51 2.3 4.6 7.4 1.9 6.2 1 0.0 2.3 4.6 1.9 6.22 9.1 8.7 2.5 4.3 1.2 2 0.0 9.1 8.7 4.3 1.23 7.8 3.3 5.9 2.2 9.4 3 0.0 7.8 3.3 2.2 9.4

In the drawing above, data in columns 1 and 2 of the array on theleft is shifted forward 1 column, overwriting the data in column 3and causing column 1 to be initialized to zero. The shifted versionis shown on the right. To perform this shifting, the INDEXterminal must have a value of 2, MODE must be ON, and TYPEmust be OFF.


Page Encode-25

EncodeEncode Module

Function 8 (continued)

1) Depending on the value of the MODE terminal, either rows or

columns are shifted.

2) All data beginning with row/column 2, through to the row/column specified on the INDEX terminal, is shifted back 1 row orcolumn. Special case: If the value on the INDEX terminal is 0,every row/ column except row/column 1 is shifted.

3) When the shift occurs, data in the row/column specified by theINDEX terminal is initialized to 0.0. Special Case: If the value onthe INDEX terminal is zero, data in the last row/column of thearray is initialized to 0.0.

4) When the shift occurs, data in row/column 1 is overwritten.

When type is ON, the following conditions apply:

1 2 3 4 5 1 2 3 4 5

1 2.3 4.6 7.4 1.9 6.2 1 4.6 7.4 1.9 0.0 6.2 2 9.1 8.7 2.5 4.3 1.2 2 8.7 2.5 4.3 0.0 1.2 3 7.8 3.3 5.9 2.2 9.4 3 3.3 5.9 2.2 0.0 9.4

In the drawing above, data in columns 2,3, and 4 of the array isshifted backward 1 column, overwriting the data in column 1 andcausing column 4 to be initialized to zero. The shifted version isshown on the right. To perform this shifting, the INDEXterminal must have a value of 4, MODE must be ON, and TYPEmust be ON.


Page Encode-26


MODE Default OFFFormat: Logical signalInput/Output: Input

determines if the shift is performed on the row or column basis.

When this terminal is OFF or unwired, the module shifts all elementsof a row into the adjacent row, according to the direction specified onthe TYPE terminal.

When this terminal is ON, the module shifts all elements of a columninto an adjacent column, according to the direction specified on theTYPE terminal.


specifies the limiting row or column for the shift operation.

For a forward shift (TYPE=OFF), INDEX specifies the number of thehighest row or column of a group of rows/columns that are to beshifted to the next higher numbered position. If the default of 0 is usedon this terminal, all rows/columns except the last one are shifted, andthe last row/column is overwritten.

For a backward shift (TYPE=ON), INDEX specifies the number of thehighest row/column of a group of rows/columns that are to be shiftedto the next lower numbered position. If the default of 0 is used on thisterminal, every row/column except row/column 1 is shifted, and row/column 1 is overwritten.



Page Encode-27

EncodeEncode Module


STATUS Default: None, entry optional Format: Analog signal Input/Output: Output

is a code which indicates the status of module execution.

0 = Successful module execution.

1 = The SELECT terminal is 0 or unwired, an undefined function isreferenced, or a function not supported by this controller has beenselected.

2 = ARRAY terminal is unwired or the specified array is not defined.

3 = INDEX terminal value is not valid for the operation selected bythe TYPE and MODE terminals. When this occurs, the module

will operate as if the default INDEX value of 0 had been chosen.

4 = The analog array is read-only.

INPUT



Page Encode-28


ASCII/Analog Value Conversions

ASCII HEX Decimal Analog ASCII Hex Decimal Analog

SP 20 32 32.0 O 4F 79 79.0 ! 21 33 33.0 P 50 80 80.0 “ 22 34 34.0 Q 51 81 81.0 # 23 35 35.0 R 52 82 82.0 $ 24 36 36.0 S 53 83 83.0 % 25 37 37.0 T 54 84 84.0 & 26 38 38.0 U 55 85 85.0 ‘ 27 39 39.0 V 56 86 86.0 ( 28 40 40.0 W 57 87 87.0 ) 29 41 41.0 X 58 88 88.0 * 2A 42 42.0 Y 59 89 89.0 + 2B 43 43.0 Z 5A 90 90.0,(comma) 2C 44 44.0 [ 5B 91 91.0-(minus) 2D 45 45.0 \ 5C 92 92.0.(period) 2E 46 46.0 ] 5D 93 93.0 / 2F 47 47.0 ^ 5E 94 94.0 0 30 48 48.0 _ 5F 95 95.0 1 31 49 49.0 ‘ 60 96 96.0 2 32 50 50.0 a 61 97 97.0 3 33 51 51.0 b 62 98 98.0 4 34 52 52.0 c 63 99 99.0 5 35 53 53.0 d 64 100 100.0 6 36 54 54.0 e 65 101 101.0 7 37 55 55.0 f 66 102 102.0 8 38 56 56.0 g 67 103 103.0 9 39 57 57.0 h 68 104 104.0 : 3A 58 58.0 i 69 105 105.0 ; 3B 59 59.0 j 6A 106 106.0 = 3D 61 61.0 l 6C 108 108.0 > 3E 62 62.0 m 6D 109 109.0 ? 3F 63 63.0 n 6E 110 110.0

Note: Character number 95 is an underscore, not a dash or minussign.


Page Encode-29

EncodeEncode Module

ASCII/Analog Value Conversions (Continued)

ASCII HEX Decimal Analog ASCII Hex Decimal Analog

@ 40 64 64.0 o 6F 111 111.0 A 41 65 65.0 p 70 112 112.0 B 42 66 66.0 q 71 113 113.0 C 43 67 67.0 r 72 114 114.0 D 44 68 68.0 s 73 115 115.0 E 45 69 69.0 t 74 116 116.0 F 46 70 70.0 u 75 117 117.0 G 47 71 71.0 v 76 118 118.0 H 48 72 72.0 w 77 119 119.0 I 49 73 73.0 x 78 120 120.0 J 4A 74 74.0 y 79 121 121.0 K 4B 75 75.0 z 7A 122 122.0 L 4C 76 76.0 { 7B 123 123.0 M 4D 77 77.0 | 7C 124 124.0 N 4E 78 78.0 } 7D 125 125.0

~ 7E 126 126.0


Page Encode-30


Function 9: Convert logical signal sequences into adecimal value.

This function is useful when multiple logical values representingsystem status have to be encoded into a single analog value for report-ing or historical storage. The logical signal sequences in a list or arrayrow or column are treated as a binary number and are converted intoan equivalent decimal value. To use this function, your controllerfirmware must be Protected Mode PLS/PLX/PES/PEX 04.40 or newer,or TeleFlow/TeleRTU TFA/TRA01.28 or newer.

When the SELECT terminal is 9 the module operates as follows.

Logical signal sequences in a signal list or in the row or column of alogical array are converted into the decimal equivalent of a binarynumber by assigning place-weights to each logical value position andsumming those that are ON in an analog signal.

Lists can have 1 to 23 logical signals. The first signal in the list isconsidered the 2^0 weighted signal holding the Least-significant-bit(LSB) of a binary number. A list with 5 signals would be encoded as s1* 2^0 + s2 * 2^1 + s3 * 2^3 + s4 * 2^4 + s5 * 2^5 and with all bits onthe decimal result would be 63.

A logical array row (or column) can have from 1 to 23 elements. Thelowest numbered element in an array row (or column) is consideredthe 2^0 weighted element holding the least-significant-bit (LSB) of abinary number.

An array 5 columns wide would be encoded as c[1,1] * 2^0 + c[1,2] *2^2 + c[1,3] * 2^3 + c[1,4] * 2^4 + c[1,5] * 2^5 and with all arrayelements ON the analog result would be 63.

List length and array size is limited to 23 elements because the sum ofall binary weights from 2^0 ( element 1 = 1) to 2^22 ( element 23 =4,194,304) is 8,388,607, a value that can be represented in an analogsignal without loss of bits.


Page Encode-31

EncodeEncode Module


This function is not supported by redundant controllers, if selected ina redundant controller, error code 1 will appear on the STATUSterminal.

Note: 3310/30/35 PROMS prior to AJ.00 will return error code 1 whenfunction 9 is selected.

SELECT Default: NoneFormat: Analog Signal or ConstantInput/Output: Input

must be set to 9.

LIST Default: NoneFormat: Analog Signal or ConstantInput/Output: Input

The number of a signal list of logical signals. When a list has morethan 23 signals only the first 23 are used. If this terminal is unwiredor has a value of zero the ARRAY terminal is used.

ARRAY Default: NoneFormat: Analog Signal or ConstantInput/Output: Input

The number of a read/write logical array of dimensions N rows by 1 to23 columns or N columns by 1 to 23 rows. This terminal is used if theLIST terminal is unwired or has a value of zero. When an array rowor column has more than 23 signals only the first 23 are used.


Page Encode-32




Not used.


Specifies access across a selected row when OFF or unwired (i.e.,columns will be summed), and access down a selected column whenON (i.e., rows will be summed). This terminal is only used if the LISTterminal is unwired or has a value of zero.


Selects one array column or row from a multi-dimensional array to beconverted. This terminal is only used if the LIST terminal is unwiredor has a value of zero.


indicates the status of module execution.

0 = Successful module execution.1 = The SELECT terminal is 0 or unwired, an

undefined function is referenced, or a functionnot supported by this controller has beenselected.


Page Encode-33

EncodeEncode Module


2 = Both the LIST and ARRAY terminals areunwired.

3 = INPUT_1 is unwired or is the wrong signaltype or is zero or negative or exceeds8,388,607.

4 = The list was not found or contains an invalidsignal or (when an array is used) the arraywas not found or is not a read/write array.

5 = The INDEX value is the wrong signal type orlarger than the array row or column size.

6 = The INPUT_1 value is too large for the list orarray.

7 = The MODE signal is the wrong type.

INPUT Default: NoneFormat: Analog signalInput/Output: Output

Input_1 is the analog output signal containing the decimal number.


Page Encode-34


Function 10: Convert a decimal value into logicalsignal sequences in signal list orlogical array row or column.

This function is useful when an analog signal that is the decimalequivalent of a binary number must be converted into logical on/offsequences in a signal list or array row or column. To use this function,your controller firmware must be Protected Mode PLS/PLX/PES/PEX04.40 or newer, or TeleFlow/TeleRTU TFA/TRA01.28 or newer.

When the SELECT terminal is 10 the following occurs.

An analog value from 1 to 8,388,607 representing the decimal equiva-lent of a binary number is converted into ON or OFF logical signalsequences in a signal list or in a row or column of a logical array. Theanalog value must be greater than or equal to 1.0 and less than8,388,608. Analog values are converted so that values that lie betweenexact powers of 2 are truncated to the next lowest power of 2. Forexample, 1.1 to 1.9 are truncated to 1.0, 16.1 to 16.9 are truncated to16, and so on.

A list can have 1 to 23 signals, with the first signal considered theleast-signicicant-bit (LSB) of a binary number. An decimal value of 62(binary 11110) would be decoded "down-the-list" as s1 = OFF, s2 = ON,s3 = ON, s4 = ON and s5 = ON.

An array can have any valid number of rows with 1 to 23 columns perrow or any valid number of columns with 1 to 24 rows; the lowestnumbered element in a row or column is considered the least-signifi-cant-bit (LSB) element. An analog value of 62 is decoded as c[1,1]=0,c[1,2]=1, c[1,3]=1, c[1,4]=1 and c[1,5]=1 in the row elements for aresult of 01111 or OFF, ON, ON, ON, ON.

This function is not supported by redundant controllers, if selected ina redundant controller, error code 1 will appear on the STATUSterminal. Note: 3310/30/35 PROMS prior to AJ.00 will return errorcode 1 when function 10 is selected.


Page Encode-35

EncodeEncode Module


SELECT Default: NoneFormat: Analog Signal or ConstantInput/Output: Input

must be set to 10.

LIST Default: NoneFormat: Analog Signal or ConstantInput/Output: Input

The number of a signal list of logical signals; the list can have morethan 23 signals but only the first 23 are used. If this terminal isunwired or has a value of zero the ARRAY terminal is used.

ARRAY Default: NoneFormat: Analog Signal or ConstantInput/Output: Input

The number of a logical read/write array of dimensions N rows by 1 to24 columns or N columns of 1 to 24 rows. This terminal is only used ifthe LIST terminal is unwired or has a value of zero.

TYPE Default: OFFFormat: Logical signalInput/Output:Input

Not used.


Page Encode-36




Specifies access across a selected array row when OFF or unwired,and access down a selected column when ON. This terminal is onlyused if the LIST terminal is unwired or has a value of zero.


Selects a column or row from a multi-dimensional array to hold theconverted result.

This terminal is only used if the LIST terminal is unwired or has avalue of zero.


indicates the status of module execution.

0 = Successful module execution.1 = The SELECT terminal is 0 or unwired, an

undefined function is referenced, or a functionnot supported by this controller has beenselected.

2 = Both the LIST and ARRAY terminals areunwired.

3 = INPUT_1 is unwired or is the wrong signaltype or is zero or negative or exceeds8,388,607.


Page Encode-37

EncodeEncode Module


4 = The list was not found or contains an invalidsignal or (when an array is used) the arraywas not found or is not a read/write array.

5 = The INDEX value is the wrong signal type oris larger than the array row or column size.

6 = The INPUT_1 value is too large for the list orarray.

7 = The MODE signal is the wrong type.

INPUT Default: NoneFormat: Analog signalInput/Output: Input

Input_1 is the analog input signal (values 1 to 8,388,607 only) to beconverted.

BLANK PAGE

Error ReportingSystem and Module Error Reporting


Page Error Report-1

Error and status codes for system communications and module execu-tion appear in several places.

❏ Error ArraysArithmetic errors, for example, an attempt by a module to divide byzero, are registered in the read-write analog array designated by the#ERARRAY system signal. See 'System Signals' for information oninterpreting the error codes appearing in the #ERARRAY.

On-line diagnostic failures are registered in the read-write logicalarray designated by the #DIAG.002 system signal. See 'System Sig-nals' for more information on the #DIAG signals.

❏ System SignalsOther system signals are used to indicate other error conditions:

#ERRCT.nnn Count of errors for task #IPSTAT.. Status of IP communications

#LINE.nnn Communication line failures.#LINKx.nnn LIU and RASCL communication

link errors#NODE.nnn Slave node failures#OCTIME.ERROR Time discrepancy between master

and slave nodes#RCNT.nnn Task rate slippage errors#RDN.. Redundancy status and errors

The #RDN.. signals are discussed under 'Redundancy'. Information onthe other system signals is included in the 'System Signals' section ofthis manual.

Error Reporting


Page Error Report-2

Error ReportingSystem and Module Error Reporting

❏ Module Status/Error Terminals

Many ACCOL modules include STATUS or ERROR terminals whichdisplay error and status codes. Consult the section on the module youare interested in for details.

❏ Status Modules

Four special modules exist to report error and status information.

EAStatus - provides information on EASlave nodes on anExpanded Addressing Master port. See'EAStatus'.

Nodestatus - provides information on individual slave nodes ona BSAP Master port, an Expanded AddressingMaster Port, or for transmitters connected to aGBBTI board. See 'Nodestatus'.

Portstatus - provides information on the ports. See'Portstatus'.

RIOSTATS - provides information on remote I/O nodes. See'RIOSTATS'.


Page ETOT/TRND-1

ETOT/TRNDEnhanced Totals/Trend Module

The ETOT/TRND Module reads an analog or logical input signal,multiplies it by a scaling factor and totalizes (sums) the readings forone hour, 8 hours (a work shift), 24 hours (daily) and one month.Current and previous totals are available for all four time intervals.

The module also computes the slope of the input over a time intervalspecified on the TIME terminal. (See Trend Function in this sectionfor more details.)

If the 33xx controller is taken out of service and then reset, an opera-tor can adjust the accumulated total of the module using the TRACKsignal and RESET signal(s).

o Module TerminalsINPUT Default: None, entry required

Format: Analog or logical signalInput/Output: Input

is the input signal. If an analog signal is used for the INPUT, ittypically represents a flow measurement. The total flow for the periodsince the last module execution is calculated each time the module

ETOT/TRND


Page ETOT/TRND-2


executes, based on the INPUT value, the delta-time in seconds, andthe SPAN terminals. This total is then added to the accumulated totalfor each of the four current time intervals: Hour, Shift, Day, andMonth.

INPUT can also be a logical signal. This is useful, for example, whencalculating accumulated runtime for a piece of equipment. When thesignal is in an ON state, a value of 1.0 is used to perform the totalizingfunction; otherwise a value of 0.0 is used.

START_HOUR Default: 00:00 (midnight)START_MIN Format: Analog signal or constant

Input/Output: Input

define the hour and minute at which the first hour and first 8-hourshift of the work day begin. When the internal real time clock minutematches the START_MIN value, the CUR_T_HOUR total is shifted tothe PREV_HOUR signal, and the CUR_T_HOUR signal is reset tozero. The internal real time clock hour is then compared toSTART_HOUR, and, if necessary, the following updates are per-formed:

If following condition Exists: This Action Is Taken:

Hour=START_HOUR CUR_T_SHIFT value copiedor any 8-hour interval to PREV_SHIFT signal;multiple since the CUR_T_SHIFT reset to 0.0START_HOUR

Hour=START HOUR CUR_T_DAY value copiedto PREV_DAY signal;CUR_T_DAY reset to 0.0

Hour=START_HOUR CUR_T_MONTH value copiedand day of the month=1 to PREV_MONTH signal;

CUR_T_MONTH reset to 0.0


Page ETOT/TRND-3


TIME Default: None, entry required for trendcalculation. If no value is entered,the trend calculation is not done.

Format: Analog signal or constantInput/Ouput: Input

defines the period in seconds over which the slope of the INPUT willbe computed.

HOUR_SPAN Default: 1.0SHIFT_SPAN Format: Analog signal or constantDAY_SPAN Input/Ouput: InputMONTH_SPAN

modify the input value in the calculation of the total. They similarlymodify the reset value used when TRACK is ON.

The module assumes that your INPUT value (or your RESET value,when TRACK is ON) is in engineering units per second. If thesevalues are NOT in engineering units per second, then the value usedon each SPAN terminal must include a factor which converts thevalue to engineering units per second. Additional factors may then beincluded as desired.

For example, if the INPUT signal is in gallons per minute, it must beconverted to gallons per second:

Gallons 1 minute 1 Gallons ----------- * ----------- = ----- * ------------- Minute 60 seconds 60 Seconds

So, in this case, the value on each of the SPAN terminals must includea factor of (1/60) or 0.0166667. Additional multipliers may also beincluded, as desired.

) (


Page ETOT/TRND-4


Suppose, for example, that your input value is in gallons per minute,but you want your hourly, shift, day, and monthly totals to be inbarrels per day. To get the units converted to barrels per day, youmust still include the factor of (1/60) as part of each SPAN calculationin order to convert gallons per minute to gallons per second.

You must then include whichever additional factors are needed for thedesired result.

To get barrels per day, assuming one barrel of a particular liquid is 42gallons, perform the following calculation:

1 Gallons Barrels 86,400 seconds Barrels * * * = 60 second 42 Gallons Day Day

So if your input is in gallons per minute, and you want to have yourhour, shift, day, and month totals in barrels per day, enter (1/60)*(86,400/42) i.e. approximately 34.28 on your HOUR_SPAN,SHIFT_SPAN, DAY_SPAN, and MONTH_SPAN terminals.

If the SPAN terminals are left unwired, the default span of 1.0 willbe used, which causes the INPUT or RESET values to be used 'as is'.If the INPUT or RESET is already in engineering units per second,the SPAN terminals may be left unwired, unless the user desiresdifferent engineering units on the total signals.

PREV_HOUR Default: NonePREV_SHIFT Format: Analog signalPREV_DAY Input/Ouput: OutputPREV_MONTH

contain the totals for the previous hour, previous shift, previous dayand the previous month. These signals change when new values arereceived from the CUR total terminals at the end of each time inter-val. In order to get valid data on the PREV total signals, the corre-sponding CUR total terminals MUST be wired. These signals will beset to 0.0 if the corresponding CUR total terminals are unwired.


Page ETOT/TRND-5


CUR_T_HOUR Default: NoneCUR_T_SHIFT Format: Analog SignalCUR_T_DAY Input/Output: OutputCUR_T_MONTH

contain the totals for the current hour, current shift, current day andcurrent month. At the conclusion of its time period, the value of eachCUR total terminal is transferred to its corresponding PREV totalterminal and then reset to zero. The MONTH total is transferred atthe start of the workday on the first day of the month.

Any changes to these signals will be overwritten at the next moduleexecution.

Note: These signals are required if you intend to receive data for thePREV_HOUR, PREV_MONTH, PREV_SHIFT, or PREV_DAY signals.

DERIVATIVE Default: None. If unwired, slope is notcomputed.

Format: Analog SignalInput/Output: Output

is the computed best-fit linear trend (slope) of INPUT over the timeperiod. For the slope of the INPUT to be computed, the value at theTIME terminal must be greater than the module execution rate. IfINPUT remains at the same value over the time interval the slope willbe zero.

TRACK Default: OFFFormat: Logical SignalInput/Output: Input/Output

when set ON, adds the scaled value from the RESET terminal(s) tothe module's currently accumulated total signals (CUR_T_HOUR,CUR_T_SHIFT, CUR_T_DAY, CUR_T_MONTH). Once this additionhas been performed, the TRACK terminal automatically turns OFF.When set OFF, this terminal has no effect on module calculations.


Page ETOT/TRND-6


RESET_HOUR Default: NoneRESET_SHIFT Format: Analog SignalRESET_DAY Input/Output: InputRESET_MONTH

these signals (RESET_HOUR, RESET_SHIFT, RESET_DAY,RESET_MONTH) hold values which are scaled by the appropriateSPAN terminals, and then added to the currently accumulated totalsin the CUR_T_HOUR, CUR_T_SHIFT, CUR_T_DAY, andCUR_T_MONTH, respectively, whenever the TRACK signal is turnedON. These signals are useful in situations in which a controller hasbeen taken out-of-service, and then returned to service, and theoperator needs to adjust the accumulated total of the module in orderfor calculations to come out correctly. These signals are only availablein ACCOL Workbench (RM) 1.0 (or newer) or ACCOL Workbench(PM) 6.2 (or newer). In addition, they are NOT available in AL,LS500, C.04, RMS03, PLS01, or earlier firmware revisions.

In those earlier firmware revisions which included the ETOT/TRNDModule, there existed a single RESET terminal, which, when theTRACK was turned ON, was scaled and added to all four currentlyaccumulated totals. If an ACCOL load is created with newer tools(discussed above) and installed in a unit with these older firmwareversions, the RESET_HOUR terminal will be treated as a singleRESET terminal, and its value will be added to all four currentlyaccumulated totals when TRACK is turned ON.

If you want to use the RESET values 'as is' i.e. without scaling via theSPAN terminals, include logic in your load which sets the SPANterminals to 1 whenever TRACK is ON.


Page ETOT/TRND-7


❏ Totalizing Function

The ETOT/TRND Module totalizes (sums) an input signal value. Thisinput value is scaled into elapsed time (in seconds), since the lastmodule execution. The totalizing function begins from the very firstmodule execution.

Either an analog or logical signal may serve as an input to the module.The input is sampled and running totals are calculated each time themodule executes. For a logical input signal, a value of 1.0 is used torepresent the ON state, and a value of 0.0 is used to represent theOFF state.

Totals are accumulated over four fixed time intervals (hour, shift, day,and month) and stored in four current total signals wired to theCUR_T_HOUR, CUR_T_SHIFT, CUR_T_DAY and CUR _T_MONTHterminals. Initially, all totals are set to zero. When the module ex-ecutes, the input is multiplied by the delta-time (in seconds) since thelast module execution in order to calculate the total over that period oftime. For each fixed time interval (hour, shift, day, month) the total isthen multiplied by the value of the SPAN, and the result is added tothe current total.

The default start time for the hour, shift, and day is midnight. At theend of each time interval (hour, shift, etc.) the current total is trans-ferred to the corresponding previous signal (PREV_HOUR,PREV_SHIFT, PREV_DAY or PREV_MONTH), and the currentsignals (CUR_T_HOUR, CUR_T_SHIFT, etc.) are reset to 0.0.

The CUR_T_HOUR value is transferred whenever the real time clockminute equals the start time minute (every 60 minutes); theCUR_T_SHIFT is transferred every 8 hours; the CUR_T_DAY istransferrred every 24 hours; and the CUR_T_MONTH is transferredat the start of the work day on the first of the month.

For a particular application, the current hour, shift, and day totalsmay need to be reset at a specific hour and minute which is the start


Page ETOT/TRND-8


of the first hour of the first shift of the work day. The start of the workday is defined using the START_HOUR and START_MIN terminals.

If necessary, the accumulated total may be modified by using theTRACK and RESET terminals.

❏ Trend FunctionThe ETOT/TRND Module will compute the slope of the INPUT signalover the interval specified on the TIME terminal and write the slopeto the DERIVATIVE terminal. The slope is computed using the leastsquares method over the time interval specified. The value of theTIME terminal specifies the interval in seconds over which slope iscomputed.

For example, if TIME is 60 seconds and the module executes every 10seconds, then the DERIVATIVE will be computed for the 6 inputsamples obtained during the 60 second interval. For a more accuratecomputation, the module could be executed once per second giving 60samples to use in calculating the slope.

ACCOL II Reference ManualPage EVP-1

EVPLiquid Equilibrium Vapor Pressure Module

This Module calculates the Equilibrium Vapor Pressure (Pevp) for aliquid and verifies that the fluid being measured is entirely in a liquidstate. Calculations are based on the American Petroleum Institute(API) Manual of Petroleum Measurement Standards, Chapter 11 -Physical Properties Data, Addendum to Section 2, Part 2 - Compress-ibility Factors For Hydrocarbons, Correlation of Vapor Pressure forCommercial Natural Gas Liquids. The calculations are liquid depen-dent. The liquid type is selected via the LIQUIDTYPE terminal. Pevp isreported on the COMPVAPORPRESS terminal, and the fluid state(i.e. whether or not the fluid is completely in the liquid state) isreported on the COMPLIQSTATE terminal.

EVP


Page EVP-2


❏ Module TerminalsLIQUIDTYPE Default: None, entry required


is a value representing the liquid on which calculations will be per-formed (e.g. Liquid Petroleum Gas (LPG) =1). Currently 1 is the onlysupported liquid type.


is the temperature, in degrees Fahrenheit, of the liquid at flowingconditions. In the case of LPG, the valid range for temperature isbetween -50o Fahrenheit and 140o Fahrenheit.

FLOW_PRESS Default: None, entry requiredFormat: Analog signalInput/Output: Input

is the pressure of the liquid, in psia, at flowing conditions.

REL_DENS Default: None. Must be wired ifABS_DENS terminal is not used.


is the Relative Density of the liquid at (600 F / 600 F). In the case ofLPG, the valid range for density is between 0.490 and 0.676.



ABS_DENS Default: If wired, REL_DENS terminalmust not be wired.


is the Absolute Density, lbm/gal at 60o F. If this terminal is wired, thenthe value will be converted to units of Relative Density at (600 F/600 F),which are needed for internal calculations by this module.

THRESMULTI Default: None, 1.25 if unwiredFormat: Analog signalInput/Output: Input

is a threshold multiplier used in the calculation of whether or not afluid is entirely in the liquid phase, which is required in order for ameasurement to be performed according the American PetroleumInstitute (API) standards. The API standards consider that conditionto be true when Pmeasured>threshold_multiplier*Pevp+ X, wherethreshold_multiplier=1.25 and X is the lesser of 2 times the MeterPressure Drop or the vapor pressure at maximum operating flow.

METERPRESSDROP Default: None. EitherMETERPRESSDROP orVAPORPRESSMAX must bewired.


is the manufacturer’s value for pressure drop (psia) across the flowmeter.


Page EVP-4


VAPORPRESSMAX Default: None. EitherMETERPRESSDROP orVAPORPRESSMAX must bewired.


is the vapor pressure (psia) at maximum operating flow.

VAPORPRESS100 Default: NoneFormat: Analog signalInput/Output: Input

selects which correlation equation will be used. To select the moreaccurate correlation equation, wire this terminal with an experimen-tally determined value for the Equilibrium Vapor Pressure (psia) at100 0F. If this terminal is unwired, the less accurate correlationequation will be used.

COMPVAPORPRESS Default: NoneFormat: Analog signalInput/Output: Output

is the computed Equilibrium Vapor Pressure (psia).

COMPLIQSTATE Default: 0.0Format: Analog signalInput/Output: Output

is a value representing the computed liquid state. If 1, then the fluidmeets the criteria for being entirely in a liquid state. IfCOMPLIQSTATE is any value other than 1, the fluid is NOT entirelyin a liquid state, and so calculations CANNOT be performed.




indicates the status of EVP Module operation. Negative values typi-cally indicate configuration errors. Valid codes are as follows:

0 Calculations completed successfully-1 Invalid dynamic module control block (MCB). Note:

This is an internal firmware error.-2 LIQUIDTYPE terminal unwired.-3 LIQUIDTYPE terminal is not an analog signal.-4 Invalid fluid type selected.-5 FLOW_TEMP terminal unwired.-6 FLOW_TEMP terminal is not an analog signal.-7 Invalid temperature.-8 Both density terminals wired.-9 Neither of the two density terminals wired.

-10 REL_DENS terminal is not an analog signal.-11 ABS_DENS terminal is not an analog signal.-12 Density value is out of bounds.-13 VAPORPRESS100 terminal is not an analog signal.-14 COMPVAPORPRESS terminal is not an analog

signal.-15 FLOW_PRESS terminal unwired.-16 FLOW_PRESS terminal is not an analog signal.-17 THRESMULTI terminal is not an analog signal.-18 METERPRESSDROP terminal is not an analog

signal.-19 VAPORPRESSMAX terminal is not an analog

signal.-20 Neither METERPRESSDROP nor

VAPORPRESSMAX terminals are wired.-21 COMPLIQSTATE terminal is not an analog signal.-22 Invalid ABS_DENS value.


Page EVP-6


❏ Module OperationBefore using this module, please review the 'Liquid MeasurementGuidelines' section, later in this manual.

To measure equilibrium vapor pressure for Liquid Petroleum Gas(LPG), set the LIQUIDTYPE Terminal to 1.

The user may select from either of the two correlation equationsdetailed in the API standard to perform the Pevp calculation. The moreaccurate correlation equation is selected by wiring theVAPORPRESS100 terminal with an analog signal containing anexperimentally determined vapor pressure for the designated liquid,at 100o Fahrenheit. If the VAPORPRESS100 terminal is unwired, theless accurate correlation equation is used.

Both equations require that the relative density at base conditions, beprovided, either via a measured source, or via a calculated source. Theuser may supply relative density either by wiring the REL_DENSTerminal with density at (600 F/600 F) or by providing the AbsoluteDensity at 600 F which will be converted to relative density units, bywiring the ABS_DENS Terminal.

In addition, each correlation equation requires the flowing tempera-ture be provided via the FLOW_TEMP terminal.

❏ Correlation EquationsCorrelation equation #1 (VAPORPRESS100 terminal unwired):

ln (Pevp) = (A0 + A1 * G) + (B0 + B1 * G)/(t+C)

where:

Pevp = Vapor pressure at t(psia)



t = Temperature(0F)G = Relative Density (60 0F/60 0F)C = A constant. For all ranges C = 443.0 0FA0, A1, B0, B0= Values for different correlation ranges are given

below Units are Ln(psia).

Correlation equation #2 (VAPORPRESS100 terminal wired):

ln (Pevp) = ln (P100)+(B0+B1*G)*(100.0-t)(D*(t+C))

where:

Pevp = Vapor pressure at t (psia)

P100 = Vapor pressure at 100 0F

t = Temperature(0F)

G = Relative Density (60 0F/60 0F)

C = A constant. For all ranges C = 443.0 0F

D = A constant. For all ranges D = 543.0 0F

B0 , B1 = Values for different correlation ranges are givenbelow. Units are in Ln(psia).


Page EVP-8


Table of Correlation ConstantsApplicable Range A0 A1 B0 B1

��

��

��

��

��

ACCOL II Reference ManualPage Expanded Node-1

Expanded Node Addressing

The Bristol Synchronous / Asynchronous Protocol (BSAP) enforces anabsolute limit on the number of nodes (remote process controllers)which may be addressed on the level below a given node. That limit,from all master ports combined, is 127 nodes. Certain applications,however, particularly those involving large numbers of radio remotesoperating on the same frequency, may require larger numbers of nodesto be addressed through the same port.

In order to address greater than 127 nodes through a given master, yetstill not violate the BSAP limit, a technique called expanded address-ing (also known as expanded BSAP or EBSAP) must be used.

Expanded addressing allows the creation of virtual nodes, below agiven master node, and each of these virtual nodes can address up to127 actual nodes. The virtual node, itself, exists only as a softwarestructure in the node above it; there is no additional physical remoteprocess controller involved. The presence of the virtual node, however,introduces an intermediate level into the network which allows up to127 actual physical nodes to be addressed below it, while only onenode, the virtual one, is counted on the intermediate level.

Since a real, physical remote process controller on level n of thenetwork can address 127 nodes below it (all on level n+1), if each ofthese nodes were virtual nodes, and each virtual node had 127 real,physical nodes below it (on level n+2) expanded addressing wouldtheoretically allow 127 groups of slave nodes, with each group contain-ing up to 127 nodes, all addressed by a single master node. In fact,they could all be on the same master port. That’s 127 X 127, or 16,129nodes! (It should be pointed out that although the expanded address-ing scheme theoretically allows 16,129 nodes, other practical limita-tions, such as running out of memory in the master node, limitationson the number of data collection templates in Enterprise Server, aswell as the unacceptable length of time required to poll so many nodeswould rule out such a large number of nodes.) On some systems withradio remotes, where very long polling rates (several minutes, at least)are acceptable, it may be practical to use expanded addressing. Inother time-critical applications, even fifty nodes (far fewer than 127,and thereby not requiring expanded addressing) may be too many tosupport fast data updates.

See also: Master/EMaster, EAStatus, andMaster/Slave Communication



Page Expanded Node-2


THE SIZE AND COMPOSITION OF A NETWORK, AND THEDECISION TO USE EXPANDED ADDRESSING MUST BE MADEONLY AFTER YOU HAVE MADE A CAREFUL EXAMINATION OFYOUR SYSTEM REQUIREMENTS, AND HAVE FULLY CONSID-ERED HOW EXPANDED ADDRESSING MAY IMPACT NETWORKPERFORMANCE.

❏ Concept of Expanded Addressing

The following figure shows a portion of a BSAP network which doesnot use expanded addressing. It has a single master node (on level n)with fifty slave nodes below it (on level n+1). These slave nodes uselocal addresses 1 through 50.*

Bristol Babcock

DPC 3330

level n

Bristol Babcock

DPC 3330Bristol Babcock

DPC 3330

Bristol Babcock

DPC 3330

Loc. Addr: 1 Loc. Addr: 2 Loc. Addr: 50

(local addresses 3 to 49 not shown)

Slave portSlave port Slave port

Master port

level n + 1

Dial-up or radio link

Because of new system requirements, it is decided that 90 additionalslave nodes must be addressed through this master node, for a total of140 slave nodes. This presents a problem because with fifty slavenodes already present, only 77 additional nodes could normally beadded (50 + 77 = 127).

To get around this limitation, expanded addressing will be used (seethe next figure). A virtual node, with a local address of 51, will beadded to the network (on level n+1). The virtual node can address the90 new real, physical nodes on the level below it (level n+2). These are

* For information on defining a BSAP network, see the NETTOPManual (document# D4057), or if you have Open BSI 3.0 or newer,see 'Using NetView' in the Open BSI Utilities (Ver 3.x) Manual(document# D5081).



called Expanded Addressing Slave (EASlave) nodes. Since the virtualnode is really a phantom controller, existing only in software, theexpanded addressing scheme has allowed a single master node at leveln, to address 140 nodes; 23 more than would normally be allowed.

Bristol Babcock

DPC 3330

level n

Bristol Babcock


DPC 3330

Bristol Babcock

DPC 3330


(local addresses

3 to 49


Master port

level n + 1

Dial-up or radio link

Bristol Babcock


DPC 3330

Bristol Babcock

DPC 3330



Expanded Master (EAMASTER) Port

level n + 2

not shown)

(local addresses

3 to 89not shown)

Loc. Addr: 51

VIRTUAL NODE

EASlave nodes

❏ General Requirements for ExpandedAddressing:

1. Before you begin, make a block diagram on paper describing thenetwork topology. Be sure to take into account all system require-ments and performance restrictions cited in this section; make surewhat you are doing is feasible from both a technical and practicalstandpoint.

2. The following controllers may serve as Expanded Addressing Masternodes: DPC 3330, DPC 3335, RTU 3310, and RTU 3305. Each ofthese controllers requires at least:




● a minimum of 64K of expanded memory (128K totalmemory).*

● An ACCOL software load created with ACCOL toolsVersion 5.6 (or newer)

● Version AG.00 (or newer level) firmware

One or more Expanded Addressing Master Ports (EAMaster ports)must be defined in each Expanded Addressing Master node.

A logical node array should be created in each Expanded AddressingMaster node, and it should be referenced by the ACCOL systemsignal #NDARRAY. This array will be used to turn communicationwith slave nodes (including virtual slave nodes) on-line or off-line. Ifthe logical node array is not defined, all slave nodes (including virtualslaves) default to on-line. If the array is defined, but does not includeall nodes, those nodes not included default to off-line. See the 'SystemSignals' section of this manual for more information on #NDARRAY.

An EASTATUS module must be configured for each EAMaster port,and an array (similar to the #NDARRAY logical node array) must becreated to turn on-line/off-line communication with the slave nodesbelow the virtual nodes. See the 'EAStatus' section, earlier in thismanual, for details.

If more than one Master/EAMaster port is defined in the node’sACCOL load, and they use radio links, each port must have a sepa-rate radio frequency.

3. Expanded addressing slave (EASlave) nodes which are below the firstvirtual node on an EAMaster port can be any device which uses theBristol Synchronous Asynchronous Protocol (BSAP) and can bedefined as a node in the network. This first group of nodes is referredto as Group 0. (Nodes which are slaves of the second virtual node onan EAMaster port are referred to as Group 1, etc.) NOTE: If you havemore than one EAMaster Port, each EAMaster Port has its ownGroup 0, Group 1, etc.

*The concept of expanded memory does not apply to ProtectedMode units (PLS00/PLX00 or newer). These units havesufficient total memory to support expanded node addressing.



There are certain restrictions regarding EASlave nodes which must beobserved, and certain configuration activities which must be per-formed, based on the firmware revision level in the node, and thegroup which the node is assigned to. This information is covered inTable 1, below:

Table 1 - Restrictions on Firmware Level / Group Definition

4. The ACCOL loads running in any EAslave node need not have version5.6 (or newer revisions) of the ACCOL tools unless features in newerrevisions of the tools other than expanded addressing are required.

G r o u p#

A n y B S A Pd e v i c e n o tc o v e r e d b y t h ec o l u m n s a tr i g h t .

D P C 3 3 3 0 ,D P C 3 3 3 5 ,R T U 3 3 1 0w i t h A Gt h r o u g h A J . 1 0P R O M s , o rG F C 3 3 0 8w i t h B . 0 1t h r o u g h C . 0 2 AP R O M s

D P C 3 3 3 0 ,D P C 3 3 3 5 ,R T U 3 3 1 0w i t h A J . 1 0 ,R M S 0 1 ,P L S 0 0 / P L X 0 0( o r n e w e r )f i r m w a r e

G F C 3 3 0 8w i t h C . 0 3 ( o rn e w e r ) l e v e lP R O M s

R T U 3 3 0 5

0A n y s u c hd e v i c e c a n b ei n G r o u p 0 .

S w i t c h b a n k 1 ,s w i t c h # 8m u s t b e O N .

S w i t c h b a n k 1 ,s w i t c h # 8m u s t b e O N .

S w i t c h n o ta p p l i c a b l e ;g r o u p n u m b e rd e f a u l t s t o 0 .

S w i t c h n o ta p p l i c a b l e ;g r o u p n u m b e rd e f a u l t s t o 0 .

1

C a n n o t b eu s e d ; d e v i c e sn o t i n g r o u p 0m u s t b e f r o mt h e o t h e rc o l u m n s o ft h i s t a b l e .

S w i t c h b a n k 1 ,S w i t c h # 8m u s t b e O F F .

S w i t c h b a n k 1 ,S w i t c h # 8m u s t b e O F F .

G r o u p n u m b e rm u s t b ed e f i n e d v i aU O I ( U O Iv e r s i o n 3 . 0 o rn e w e r )

G r o u p n u m b e rm u s t b ed e f i n e d v i aF l a s hC o n f i g u r a t i o np r o g r a m .

2 t o1 2 7

C a n n o t b eu s e d ; d e v i c e sn o t i n g r o u p 0m u s t b e f r o mt h e o t h e rc o l u m n s o ft h i s t a b l e .

S w i t c h b a n k 1 ,S w i t c h # 8m u s t b e O F F .C u s t o mE P R O M( o r d e r e d f r o mB r i s t o lB a b c o c k ) w i t hg r o u p n u m b e rm u s t b ei n s t a l l e d .

S w i t c h b a n k 1 ,S w i t c h # 8m u s t b e O F F .G r o u p n u m b e rm u s t b ed e f i n e d v i aU O I v e r s i o n3 . 0 o r n e w e r( 4 . 0 o r n e w e rf o r p r o t e c t e dm o d e ) O R b yi n s t a l l i n gc u s t o mE P R O M o rf l a s h w a r e .

G r o u p n u m b e rm u s t b ed e f i n e d v i aU O I ( U O Iv e r s i o n 3 . 0 o rn e w e r )

G r o u p n u m b e rm u s t b ed e f i n e d v i aF l a s hC o n f i g u r a t i o nP r o g r a m .




5. All nodes, whether master, slave, or virtual, must be defined in thecurrent NETTOP or NETDEF file. All slaves on an EAMaster port,which are on the level immediately below the node containing theport, must be virtual nodes. All slaves of the virtual nodes must bereal remote process controllers; i.e. a virtual node cannot have avirtual slave.

6. Master/slave (peer to peer) communication of signal lists and dataarrays is supported between:

● A MASTER or EMASTER module in one EAslave node, and aSLAVE module in another EAslave node which is in the samegroup; i.e. both nodes are defined immediately below the samevirtual node. (See the 'Master/EMaster' section, later in thismanual.) NOTE: Peer to peer communication is NOT allowedbetween nodes that are not in the same group.

● A SLAVE module in a node containing an EAMaster port, and aMASTER or EMASTER module residing in an EASlave nodeaddressed by that same port.

● An EMASTER module in a node containing an EAMaster port,and a SLAVE module residing in an EASlave node addressed bythat same port.

NOTE: An EMASTER module supports all the functions of theoriginal MASTER module, plus the new capability describedabove. See the 'Master/EMaster' section, later in this manual.

7. Poll periods and timeout values must be carefully set in all nodes.

8. It is recommended, but not required in all cases, that the node withlocal address 127 in each group of nodes be left unused. This isbecause DPC 3330 redundant systems using RASCL, as well as 3350/80 redundant systems, use this address for other purposes.

9. If you are using Open BSI 3.0 or newer (NetView instead of NETTOP,etc.), you may ONLY define your virtual nodes on Level 1.



❏ Example - Configuring A Network ForExpanded Addressing

A particular remote process controller, named RPC7, currently ad-dresses 123 slave nodes (R1 through R123) on a single master port.System requirements have changed, and now an additional 6 slaveprocess controllers are being added below this controller. It is requiredthat all of the 6 new slave nodes communicate via a single radiofrequency. Since the frequency will be shared, all of the new nodesmust be addressed through the same port.

1. For this example, an EAMaster port must be added to the masternode, and three virtual nodes below it, with addresses 124, 125, and126 must be created. The virtual node names will be VN1, VN2, andVN3. Each of the virtual nodes will have 2 EASlave nodes. (NOTE:Normally, all 6 of the new EASlave nodes would be put under a singlevirtual node, however, we have used 3 virtual nodes to illustratebetter the concept of ‘groups’.) The new EASlave nodes are named S1through S6. A portion of the block diagram for this new network isshown below:

RPC7

R1 R2 R123 VN1 VN2 VN3

S1 S2 S3 S4 S5 S6

Master Port EAMaster Port

Group 0 Nodes Group 1 Nodes Group 2 Nodes

Locaddr 1 Locaddr 2 Locaddr 123

Locaddr 1

Locaddr 124 Locaddr 125 Locaddr 126

Locaddr 1 Locaddr 2 Locaddr 1 Locaddr 2 Locaddr 1 Locaddr 2

LEVEL N

LEVEL N+1

LEVEL N+2EASlave nodes




2. Define the network in NETTOP or (if you have Open BSI 3.0 ornewer) NetView. A portion of a sample NETTOP file dealing with thenew nodes is shown below.

EXP.NET 14-APR-1993 16:06 Page 1

Node Information

RPC7 File: RPC7 Description: EXPANDED ADDRESSING MASTER NODEType: 3330 - 5.x Alarm Zone: 1 Off Scan / ON SCAN ScanPredecessor: VAX Level: 1 Local Adr: 1 Global Adr: 0800 hexSlaves Defined: 126

—————————————————————————————————————

R123 File: R123 Description: REMOTE STATION 123Type: 3330 - 5.x Alarm Zone: 1 Off Scan / ON SCAN ScanPredecessor: RPC7 Level: 2 Local Adr: 123 Global Adr: 0fb0 hexSlaves Defined: 0

VN1 File: NONE Description: VIRTUAL NODE - NO HARDWAREType: 3330 - 5.x Alarm Zone: 1 Off Scan / ON SCAN ScanPredecessor: RPC7 Level: 2 Local Adr: 124 Global Adr: 0fc0 hexSlaves Defined: 2

VN2 File: NONE Description: VIRTUAL NODE - NO HARDWAREType: 3330 - 5.x Alarm Zone: 1 Off Scan / ON SCAN ScanPredecessor: RPC7 Level: 2 Local Adr: 125 Global Adr: 0fd0 hexSlaves Defined: 2

VN3 File: NONE Description: VIRTUAL NODE - NO HARDWAREType: 3330 - 5.x Alarm Zone: 1 Off Scan / ON SCAN ScanPredecessor: RPC7 Level: 2 Local Adr: 126 Global Adr: 0fe0 hexSlaves Defined: 2

—————————————————————————————————————

S1 File: S1 Description: EXPANDED ADDRESSING SLAVE NODEType: 3330 - 5.x Alarm Zone: 1 Off Scan / ON SCAN ScanPredecessor: VN1 Level: 3 Local Adr: 1 Global Adr: 0fc1 hexSlaves Defined: 0

S2 File: S2 Description: EXPANDED ADDRESSING SLAVE NODEType: 3330 - 5.x Alarm Zone: 1 Off Scan / ON SCAN ScanPredecessor: VN1 Level: 3 Local Adr: 2 Global Adr: 0fc2 hexSlaves Defined: 0

S3 File: S3 Description: EXPANDED ADDRESSING SLAVE NODEType: 3330 - 5.x Alarm Zone: 1 Off Scan / ON SCAN ScanPredecessor: VN2 Level: 3 Local Adr: 1 Global Adr: 0fd1 hexSlaves Defined: 0



EXP.NET 14-APR-1993 16:06 Page 2

Node Information

S4 File: S4 Description: EXPANDED ADDRESSING SLAVE NODEType: 3330 - 5.x Alarm Zone: 1 Off Scan / ON SCAN ScanPredecessor: VN2 Level: 3 Local Adr: 2 Global Adr: 0fd2 hexSlaves Defined: 0

S5 File: S5 Description: EXPANDED ADDRESSING SLAVE NODEType: 3330 - 5.x Alarm Zone: 1 Off Scan / ON SCAN ScanPredecessor: VN3 Level: 3 Local Adr: 1 Global Adr: 0fe1 hexSlaves Defined: 0

S6 File: S6 Description: EXPANDED ADDRESSING SLAVE NODEType: 3330 - 5.x Alarm Zone: 1 Off Scan / ON SCAN ScanPredecessor: VN3 Level: 3 Local Adr: 2 Global Adr: 0fe2 hexSlaves Defined: 0

3. Create an EAMaster port in the ACCOL load of the master controllerRPC7. Instructions on modifying port types are discussed in thesection 'Communication Ports', earlier in this manual, and in theACCOL II Interactive Compiler Manual (document# D4042). The portdefinition as it would appear on the AIC screen appears below. If youare using ACCOL Workbench, ports must be defined in the *COM-MUNICATIONS section of the ACCOL source file. See the ACCOLWorkbench User Manual (document# D4051) for details.

Port A: ■ Master ■ BAUD 9600 ■ AsyncHigh Slave Adr: 123 Timeout: 5

Port B: ■ Exp. Master ■ BAUD 9600 Timeout: 5High Slave Adr: 126 High EASlave Adr: 2

4. A logical node array, designated by the #NDARRAY system signal,should be defined in the Expanded Addressing Master node, RPC7.This is used to turn communications on-line/off-line with the nodes onthe next level of the network, including all virtual nodes. If#NDARRAY is not defined, all virtual nodes will default to on-line. If#NDARRAY is defined but not all virtual nodes are included, those




not included will default to off-line. NOTE: If a virtual node is turnedoff, communication with all EASlave nodes below it will be turned off.This provides a quick method for placing an entire group of nodes off-line. Information on #NDARRAY is included in the section 'SystemSignals', later in this manual.

5. An EASTATUS module must be defined for each EAMaster port inthe master node. Since RPC7 has only one EAMaster port, only oneEASTATUS module must be defined. This module must also have anassociated on-line/off-line node data array (similar to #NDARRAY)which will turn communications on/off line for the EASlave nodes. Seethe section 'EAStatus', earlier in this manual for details.

6. The two EASlave nodes under the first virtual node, VN1, are inGroup 0. Any BSAP device can be in Group 0, however, it is requiredthat any 3310/3330/3335 series nodes, with AG.00 (or later) levelfirmware, or GFC 3308 nodes with B.01 through C.02A level firmwaremust have switches set properly based on the group they are in. SeeTable 1, earlier in this section, for details on switch settings.

7. The two DPC 3330 nodes under the second virtual node, VN2, are inGroup 1. Again, switches must be set according to the information inTable 1.

8. The two DPC 3330 nodes under the third virtual node, VN3, are inGroup 2. See Table 1 for information about defining the group num-ber.

9. If peer-to-peer communication (transfer of signal lists and data arrayvalues between nodes) is required, MASTER or EMASTER module(s)and matching SLAVE module(s) must be defined in the ACCOL loadsof the relevant nodes. If communication is to originate from a nodewith an EAMaster port to an EASlave node on that port, anEMASTER module would be required in the load containing theEAMaster port. See the 'Master/EMaster' section, later in thismanual, for details.

10. Carefully set the poll periods for all nodes. Recommendations on



setting poll periods are included in the Network 3000 CommunicationUsers Guide (document# D4052), or contact Bristol ApplicationSupport.

❏ Rules For Downloading, Port Usage

EASlave nodes in Group 0:

These nodes follow the same port usage and download rules as astandard BSAP node: Cold download* defaults to 9600 baud on PortsA, C, G, I, and BIP 1; it uses Switch Block 1, Switches 2-4 for Ports B,D, H, J and BIP 2. Warm download** uses the port and baud ratethrough which the new download was requested; i.e., if a downloadrequest is received through Port B which is a Slave Port at 19.2KB,the warm download will be done on Port B at 19.2KB. Note: BIP 1and BIP 2, and well as Port H and Port J do not support synchronouscommunication, therefore if the cold download switch is set for syn-chronous, these ports will default to 9600 baud asynchronous for colddownload.

EASlave nodes in Group 1 and above:

These nodes follow the same rules as nodes in Group 0, except for thefollowing differences:

● The slave port on the EASlave node must be associated with anExpanded Addressing Master port in the master node, or mustbe connected to an external interface, e.g. Toolkit, Open BSI,etc. which supports expanded BSAP and which has been set upfor the unit's group number and local address.

● All other ports on the EASlave node function as normal BSAPports.

* Cold download refers to a download into a reset, empty unit which presently contains no load.** Warm download refers to a download into a unit which is already running an ACCOL load.




Cold Download (Group 1 and above)

● If you do not know a unit's group number, or you have pre-5.9ACCOL tools, the only way to perform a download using stan-dard BSAP communications is to use Port A or BIP 1 at 9600baud, locally.

● To download locally through any other port, ACCOL 5.9 (ornewer) tools must be used. Alternatively, the download must beglobal and the node must be connected to an Expanded Address-ing Master Port in the master node. The EASlave node must bedefined in the currently released Nettop files. Ports C, G, and Idefault to 9600 baud; Ports B, D, H, J and BIP 2 use the baudrate specified on Switch Block 1, switches 2-4. Note: Synchro-nous download does not apply to expanded node addressing.)

Warm Download

A warm download uses the port and baud rate through whichthe new download was requested. In addition, if the downloadrequest is received on the slave port, expanded BSAP communi-cation will be used; if it is received on a Pseudo-slave port,standard BSAP communication will be used.


Page For-1

FORENDFOR

FOR, ENDFOR Statements

All statements between the FOR and ENDFOR commands are exe-cuted sequentially. The FOR command initiates the loop. When theENDFOR statement is reached, the loop may be repeated, dependingon the conditions set in the FOR statement.

Each time the statements between the FOR and ENDFOR statementsare executed, the signal named in the FOR statement is incrementedor decremented, depending on the other factors in the FOR statement.This looping will continue until the signal equals or exceeds some finalvalue.

❏ Syntax

FOR initial, final, step, signal

where:

signal is a signal which determines if looping will continue. When thissignal equals or exceeds final, control is transferred to the state-ment below ENDFOR.

initial is the initial value of signal.

final is the final value or stopping point

step determines the amount of incrementing or decrementing whichwill take place for each pass of the loop. To increment toward ahigher humber, step must be a positive number. To decrement, usea negative number. Each time the FOR statement is executed, stepis added to signal. Looping will continue if signal has not yetreached final. When choosing the step value, it must be chosensuch that adding the first step to the signal value will result in an

FOR/ENDFOR


Page For-2

FORENDFORFOR, ENDFOR Statements

incremental or decremental movement closer to, but not exceed-ing, the final value. If this is NOT the case, the loop will NOTexecute.

The user should NOT attempt to write changes to the FOR loopsignals (initial, final, step, signal) within the FOR loop.

❏ Example

210 FOR 2., 14., 3., CT.111220 CALCULATOR A=B/CT.111230 ENDFOR

In the example, signal CT.111 will start at an initial value of 2 andwill be incremented to 14 in steps of 3. Therefore, the FOR commandwill be executed six times and the CT.111 signal will be set to thefollowing values:

CT.111

1st pass 22nd pass 2 + 3 = 53rd pass 5 + 3 = 84th pass 8 + 3 = 115th pass 11 + 3 = 146th pass End of loop

The FOR statement is followed by a Calculator Module on line 220that performs the expression A=B/CT.111. In this expression signal Bwill be repeatedly divided by signal CT.111, which is being incre-mented by the FOR statement. The ENDFOR statement is the end ofthe loop.


Page For-3

FORENDFOR

FOR, ENDFOR Statements

An additional command which can be used to halt the FOR statementat any point is the BREAK command. This command allows an uncon-ditional exit from a loop. The BREAK command, used in this applica-tion, is equivalent to a GOTO command which transfers control to theline following the next ENDFOR statement. A BREAK statementplaced outside a FOR loop will transfer control to the end of the task.

Note that in the example, below, a space is required between theconditional command IF and the condition being tested (A==B).

210 FOR 2., 14., 3., CT.111212 IF (A==B)214 BREAK216 ENDIF218 CALCULATOR220 ANIN222 ENDFOR

When entering a FOR statement, it is not necessary to insert decimalpoints at the end of whole numbers or to put spaces after commas.These will be inserted automatically. Additional decimal places will beautomatically added to whole or decimal numbers as required.

BLANK PAGE


Page Formats-1

FormatsASCII Communications Formats

Formats allow a process controller to communicate with an ASCIIdevice such as keyboard, printer or CRT monitor. An input-typeFormat converts ASCII messages into the appropriate ACCOL data,while an output-type Format converts and arranges ACCOL data intoan ASCII message format.

A Format specification will determine how a signal will be displayed.It will also set the spacing and location of data displayed on printedcopy or a CRT.

Special Format commands allow repeats, skips, termination and resetsof format elements. Data array descriptors activate arrays for process-ing data. Special input control descriptors permit looping of signal orarray data. Additional commands allow Subformats, time and date,and message commands to be specified.

❏ Formats, Loggers And Signal ListsEach Format is associated with a Logger Module and a signal list asshown in next figure. The signal list, which may be an I/O LIST or anOUTLIST, contains the signals that will be formatted. The LoggerModule selects signals for formatting and also performs the communi-cations interface with the external ASCII device. See ‘Logger’ for moredetails.

Statements that describe the Format must follow the rules of syntaxdescribed later in this section. Formats may be entered directly in theACCOL source file (if you are using the ACCOL Workbench, or theACCOL II Batch Compiler) or they are entered on the Format Struc-ture Menu of the AIC as shown in next figure.

Signal lists can also be employed with the Logger Module. The Loggerselects signals from the list in ascending order, but certain formattingcommands can change the order of execution. Signal names are en-tered in a signal list.

Formats


Page Formats-2


Communication Links

Communications to the external ASCII device can be made throughLogger Ports (see 'Logger' section). If you are using the AIC, theseports are defined on the Communications Configuration Menu (shownon the opposite page.) If you are using ACCOL Workbench, these portsare defined in the *COMMUNICATIONS section (see the ACCOLWorkbench User Manual, document# D4051 for details).

The selected port should be configured as an RS423. An RS423 link iscompatible with RS232 ports provided that line lengths do not exceed15 feet. See the appropriate 33XX controller manual for details.

I / O LOGGER

Format #n

SignalList#n

INLIST

Internal Signals(maximum list length is 3,999 entries)

LOGGER

Format #n

SignalList#n

OUTLIST

(maximum list length

Internal Signals

is 3,999 entries)

Logger as I/O Device

Logger as Output Device


Page Formats-3


BIP 1: __ Unused

BIP 2: __ Unused

Port A: __ Slave _ Baud 9600

Port B: >> Logger _ Baud 9600 _ Half Duplex _ No CTS _ 7 Bits _ 2 Stop Bits _ Even Parity

Port C: >> Logger _ Baud 4800 _ TTY _ XON-XOFF _ 6 Bits _ 1 Stop Bits _ Odd Parity

Port D: __ Unused

Additional I/O Buffers __0

Communications Configuration Menu (AIC users ONLY)

FORMAT 1 Delete Format

10 30X,”gas station no. 3",///

20 3X,”differential pressure:”,6X,F4.1,1X,U6,6X,”stn3.10.dp”,

6X,”alarm:”,L3,///

30 17X,”pressure:”,6X,F6.2,1X,U4,6X,”stn3.11.pr”,6X,”alarm:”

,1X,L3,///

40 14X,”temperature:”,6X,I2,1X, U5,9X,”stn3.12.te”,6X,”alarm:”

,L3,///

50 16X,”flow rate:”,6X,I6,1X,U5,5X,”stn3.13.fr”1X,L3,/

60

Format Structure Menu With Sample Format (AIC users ONLY)


Page Formats-4


gas station no. 3

differential pressure: 51.3 in/h20 stn3.10.dp alarm:off

pressure: 128.19 psig stn3.11.pr alarm:off

temperature: 50 deg.f stn3.12.te alarm:off

flow rate: 200000 mscfh stn3.13.fr alarm:off

Equivalent Formatted Display


Page Formats-5


❏ Numeric And Text Descriptors

Both numerical and text descriptors are provided. The numeric de-scriptors (F, I and E) allow formatting of fixed point, integer, andexponential values; their output fields are displayed as right justified.Their input fields are terminated by either the field width, a trailingspace, or a carriage return.

The text descriptors (L, T, N, U, K and M) structure the display of textassociated with logical and string signals, signal names, signal units,conditional formats and messages; their output fields are displayed asleft justified.

Fixed Point (F)

The descriptor, F, denotes that all analog values contained in a list,whether inputs or outputs, will be converted to a fixed decimal pointformat. The fixed point descriptor has the following elements:

Fw.d

where:

F = Fixed point descriptor

w = Width of field. A value that specifies the total number ofcharacters in a field including decimal point, numerals andnegative signs.

d = Decimal place. The number of characters to be positionedto the right of the decimal point.

The value represented by “w” must always be greater than or equal tod+1. If the value to be formatted already contains a decimal point, itwill be overridden by the format specifiers. If the value does notcontain a decimal point, one will be furnished. If a value is too large or


Page Formats-6


too small for the field width, it will appear as a series of asterisksequivalent to the size (w) of the field. Blank spaces will also be in-serted where needed to maintain consistency of the format.

For example, assume that the format specification is entered as F5.2,which means the value will have a total of 5 characters, with thedecimal point positioned two characters from the right or: nn.nn.Using this format, some sample numbers would be affected as follows:

Number Format Value Notes

45.7897 45.79 Rounded22 22.00 Zeros added3 3.00 Blank & zeros added-3 -3.005000 ***** Too large.0062 0.01

Integer (I)

The descriptor, I, denotes that all analog values contained in a list,whether inputs or outputs, will be converted to integer format(straight number without decimal point). This descriptor has thefollowing construction:

Iw

where:

I = Integer descriptor

w = Width of field. A value that specifies the total number ofcharacters in a field.

If a value is too large or too small for the field width, it will appear asa series of asterisks equivalent to the size (w) of the field. Blankspaces will also be inserted where necessary to maintain consistency of


Page Formats-7


the format.

For example, assume that the format specification is entered as I4,which means the value will have a total 4 characters or: nnnn. Usingthis format, some sample values of numbers would appear as follows:

Number Format Value Notes

1000 1000 No change22 22 Blanks added38.79 39 Rounded156788 **** Too large.6976 1 Rounded

Exponential (E)

The descriptor, E, signifies that all analog values contained in a listwill be converted to the exponential format. This descriptor has thefollowing elements:

Ew.d

where:

E = Exponential descriptor

w = Width of field. A value equivalent to the total number ofcharacters in the field including the 4-character exponentin the form:

E+nn

where nn represents a 2-digit integer that is the exponent.

d = Decimal place. A value equivalent to the number of digits tothe right of the decimal point. The third digit to the right isrounded up or down.


Page Formats-8


The value of w should be greater than or equal to d+7 to accommodateany negative signs, zero-type characters, decimal points and expo-nents. A number that is too large for the field width will appear as aseries of asterisks.

For example, if an output format specification is entered as E10.3, thefield will consist of a total of 10 characters that includes the exponentand decimal point. The decimal point will be positioned three charac-ters from the right, excluding the negative sign, and exponentialcharacters. Some sample values of numbers would appear in thefollowing formats:

Number Format Value

1101766 0.110E+0735872220.75 0.358E+08-1023458.99 -0.102E+075 0.500E-01

The “E” command field will display a zero to the left of the decimalpoint. All significant digits are displayed to the right of the decimalpoint.

Logical (L)

The descriptor, L, denotes that the text assigned for the current statusof any logical signal in an OUTLIST will be printed or displayed. Thisdescriptor has the following elements:

Ln

where:

L = Logical descriptor


Page Formats-9


n = Width of the field. A value that specifies the total number ofcharacters in a field. If no number is entered, the default is6.

Examples: Some sample output format specifications are as follows:

Descriptor Text

L2 ONL3 OFFL6 FLOWONL6 CLOSED

String (T)

The T descriptor typically formats a string signal to print or displaythe signal’s text at the location of the cursor. This descriptor has thefollowing elements:

Tn

where:

T = String descriptor

n = The number of characters in the string signal that will bedisplayed. (String signals may not more than 64 charac-ters). If no number is entered, n will default to the stringlength.



Page Formats-10


Descriptor Text

T8 STAND BYT19 PRESSURE #8 FALLINGT17 CHECK TEMP ON T12

Signal Name (N)

The N descriptor is typically used to specify the format of a signalname (base.extension.attribute) entered on an ASCII keyboard device.This descriptor, in conjunction with a subspecifier letter, allowsvarious parts or combinations of a signal name to be used. This de-scriptor has the following elements:

Nxn

where:

N = Signal name descriptor

x = Subspecifier that identifies the desired elements of thesignal name. The subspecifier letters are A, B, D, N, X orT. These letters are defined below.

n = Width of field. A value that specifies the total number ofcharacters in the signal name or its desired elements.

Subspecifiers:

A = Base.extension.attribute and descriptive text. Default widthis 47 characters.

B = Base only. Default width is 8 characters.

D = Descriptive text only. Default width is 24 characters.

N = Base.extension.attribute. Default width is 22 characters.


Page Formats-11


X = Extension only. Default width is 6 characters.

T = Attribute only. Default width is 4 characters.


Descriptor Text

NA15 SIG.34.PV INPUTNB3 SIGND5 INPUTNN9 SIG.34.PVNT2 PV

Signal Units (U)

This descriptor causes the “Units Text” for the selected signal to bedisplayed or printed. It contains the following elements:

Uw

where:

U = Signal units descriptor

n = Width of field. A value that specifies the total number ofcharacters. The default is 6 characters.

Examples: Some sample format specifications are as follows:

Descriptor Units Text

U6 FT/LBSU5 MSCFHU3 PSIU5 DEG C


Page Formats-12


True/False Conditional Format Descriptor (K)

K is a conditional format. It can produce one of two outcomes, depend-ing on the condition that you specify.

The K format has three forms. They are:

Kx(format1 if true):(format2 if false)Kx(format if true)Kx:(format if false)

In each case, the letter K must appear first, followed by a one or twoletter code which indicates the condition you’re testing. These will bediscussed shortly. In the first form, if condition x is true, the formatwithin the first parenthesis will be executed. If it is false, the format inthe second parenthesis is used.

The second and third forms have only one condition. For Kx(format),the format within parenthesis is executed if condition x is true. Other-wise, the K descriptor is ignored. In the statement Kx:(format), theformat is executed if condition x is false.

The false condition is assumed if the condition being tested is notapplicable to the next signal or array cell. The following list containsvalid entries for x.

x True Conditions

A Alarm has been acknowledged. If the signal has more than onealarm state defined (low and low low, for example) the truecondition is defined as a situation when all alarm limits havebeen acknowledged. The KA condition is judged to be false ifany alarms have not been acknowledged.)

C Signal is control inhibitedD Data is questionable. (In the true state, the questionable data

bit has been set. In the false state, the signal value is consid-ered valid.)

H Signal is in high alarm state


Page Formats-13


x True Conditions

HH Signal is in high high alarm stateI Signal is alarm inhibitedL Signal is in low alarm stateLL Signal is in low low alarm stateM Signal is set for manual inhibitS Signal is in alarmTA Signal is an analog signalTL Signal is a logical signalTS Signal is a string signalV (value) Analog or logical signal is not equal to zero. (The false

condition is when an analog or logical signal is equal to zero.)W Low low alarm has been acknowledgedX Low alarm has been acknowledgedY High alarm has been acknowledgedZ High high alarm has been acknowledged

In the example below, the word ALARM will be printed if the signal isin alarm. If it is not in alarm, the word NORMAL is printed.

KS(‘ALARM’):(‘NORMAL’)

The next example tests whether or not the signal has been acknowl-edged.

KA(‘ACKNOWLEDGED’):(‘NOT ACK.’)

Key Code Conditional Format Field Descriptor(KK)

The key code conditional field descriptor allows the selection of aspecific section of format based on a particular key code being theinput. The ASCII code for the next character input from the port iscompared to the codes specified with the field descriptor. If no keymatches, the default format is used. Any number of key codes can betested. The default format is optional. The forms of the key code


Page Formats-14


conditional are as follows:

KKx(fx):y(fy) . . . :z(fz):(fd)KKx(fx):y(fy) . . . :z(fz)

where:

x, y & z = ASCII key codes in decimalfx = format if input key code equals xfy = format if input key code equals yfz = format if input key code equals zfd = format if input key code does not match

Example:

The following format will select subformat 1 if the ‘1’ key is the inputand will select subformat 2 if any other key is the input.

KK49(SF1):(SF2)

The following format will alarm inhibit a signal if the ‘A’ key is theinput, or manual inhibit a signal if the ‘B’ key is the input, or donothing if neither ‘A’ nor ‘B’ are inputs.

KK65(SAI):66(SMI)

Message Command (M)

The descriptor, M, specifies the start and end characters for a block ofcharacters that comprise the message. The message is sent out so thatthe start character precedes the first character of each block and theend character follows the last character of each block. The output blocksize is determined by way of the SB field descriptor. This specifier hasthe following form:

M n:m


Page Formats-15


where:

M = Message command descriptor

n = This entry defines the start character of the message indecimal form.

m = This entry defines the end character of the message indecimal form.

A value of 0 (zero) for n and/or m will indicate that no start or endcharacter processing is required for the indicated field. Therefore, 0 isnot a valid start or stop character.

Format Command (Q)

The Q command converts a data array or list element, either analog orlogical, to an ASCII-type format appended with a checksum for dataintegrity checks. The “Q” protocol provides faster transfer of dataalong with improved security. This command allows a Bristol RDC3350/3380 to communicate with UCS 3000 systems, or any otherdevices that conform to the Q format protocol.

nQ

where:

Q = Format command descriptorn = An optional number to designate the repeat factor when one

or “n” array or list elements will be used.

Audit Trail Messages (nEL, EA, nEN)*

These commands will display alarm or events messages stored by theAudit Trail/EAudit Module:

nEN descriptor requires ACCOL 5.11 tools and RMS01firmware (or newer) for 386EX Real Mode;ACCOL 5.12 andAL (or newer) for 186 units; and ACCOL 6.0 and PLS00/PLX00 (or newer) for 386EX Protected Mode Units.

*


Page Formats-16


nEL displays n number of messages (messages deleted after read)

EA displays all messages (messages deleted after read)

nEN displays n number of newest messages (messages NOT deleted after read)

Each message occupies one line and is terminated by a carriage returnor line feed.

❏ Data Array Descriptors

The value of a data array cell may be formatted for output and a cell’svalue can be set by an input format if the array is not read only. Whena data array is defined, array mode becomes active which causesseveral field descriptors to act on the array’s cells rather than signalsin the I/O list. Field descriptors CE, CL, CR, JD, JT, E, F, I, KTA,KTL, KV and Q will use the defined data array if array mode is active.Each use of the data array will cause the next cell to be used unlesscell repeat mode is active. If the array is two dimensional, all columnsof a row are used before incrementing to the next row.

Define Analog Array (DA)

The value of the current signal in the I/O list is used to define thenumber of the analog data array. The signal’s type must be analog.The array is set to the first cell (row 1, column 1), cell repeat mode iscancelled, and cell wrap around is cancelled.

Define Logical Array (DL)

The value of the current signal in the I/O list is used to define thenumber of the logical data array. The signal’s type must be logical. Thearray is set to the first cell, cell repeat mode is cancelled, and cell wraparound is cancelled.


Page Formats-17


End Array Mode (DE)

Array mode is cancelled. Field descriptors will return to using signalsin the I/O list.

Continue Array Mode (DC)

Array mode is set back to active. Processing continues at the point inthe array when DE was executed. A data array must have beenpreviously defined via the DA or DL field descriptors.

Set Cell Repeat Mode (DR)

Cell repeat mode is set active which disables the automatic incrementof the current row and column when an array cell is used to allowrepeated use of a cell.

Cancel Cell Repeat Mode (DN)

Cell repeat mode is cancelled and the current array row and columnare incremented to the next cell. A data array must have been previ-ously defined via the DA or DL field descriptors.

Skip Array Cell (DS)

The current array row and column are incremented to the next cell. Adata array must have been previously defined via the DA or DL fielddescriptors.


Page Formats-18


Skip Array Cell Backwards (DSB)

The current array row and column are decremented to the previouscell. A data array must have been previously defined via the DA or DLfield descriptors.

Jump to First Cell (DJ)

The current array row and column are set to the first cell.

Set Cell Wrap Around Mode (DW)

Cell wrap around mode is set active which causes the first array cell tobe used following the use of the last array cell. The DSB field descrip-tor will skip to the last array cell if currently at the first array cell.

Display Current Cell’s Row (DY)

The current array row is output as an integer value. The value is rightjustified in the field. If the value does not fit in the specified fieldwidth, asterisk characters will fill the field. A data array must havebeen previously defined via the DA or DL field descriptors. The form ofthe display row field descriptor is as follows:

DYw

where w = number of character positions in the field.


Page Formats-19


Display Current Cell’s Column (DX)

The current array column is output as an integer value. The value isright justified in the field. If the value does not fit in the specified fieldwidth, asterisk characters will fill the field. A data array must havebeen previously defined via the DA or DL field descriptors. The form ofthe display column field descriptor is as follows:

DXw

where w = number of character positions in the field.

❏ Special DescriptorsThe descriptor, S, allows special formatting functions to be performed.This descriptor includes a specifier to indicate which special functionwill be performed. Each is described in the subsections that follow.

Element Repeat (SR)

This command causes the next signal list element to be repeated untilan SE, SS or SJ command is encountered.

Element Skip (SS)

This command skips the current signal in the list and executes thenext signal. It does not affect the repeat mode. The format is asfollows:

nSSwhere:

n = Specifies an optional repeat count.SS= Skip command descriptor


Page Formats-20


Terminate Repeat (SE)

This command cancels the SR command and returns to the normalorder of signal list execution.

Element Reset (SJ)

This command stops the execution of the list at a selected point andresumes executing from the top of the list. This command does notaffect the repeat mode.

Signal Skip Backwards (SSB)

The current signal in the I/O list is skipped and the previous signal inthe I/O list becomes the current signal.

Signal Wrap Around Mode (SW)

Signal wrap around mode is set active which causes the first signal inthe I/O list to be used following the use of the last signal in the I/Olist. The SSB field descriptor will skip to the last signal in the I/O listif currently at the first signal in the I/O list.

Set Alarm Inhibit (SAI)

The current signal’s alarm inhibit status is set.

Set Alarm Enable (SAE)

The current signal’s alarm enable is set.


Page Formats-21


Set Control Inhibit (SCI)

The current signal’s control inhibit status is set.

Set Control Enable (SCE)

The current signal’s control enable status is set.

Set Manual Inhibit (SMI)

The current signal’s manual inhibit status is set.

Set Manual Enable (SME)

The current signal’s manual enable status is set.

Time Specifier (ST)

This specifier may be used as input or output. As an input, it willcause the system time value to be changed to the entered value. Thereis also no coordination with the handling of the communication timesynchronization messages. The entered time will not automaticallypropagate to slave nodes in a hierarchical network.

The time is entered in the following form:

HH:MM:SS

where:

HH = Hours (01 to 23)MM = Minutes (01 to 59)


Page Formats-22


SS = Seconds (01 to 59)

Date Specifier (SD)

This specifier may be used as either input or output. As an input, thisdescriptor will cause the system date value to be changed to theentered value. There is also no coordination with the handling of thecommunication time synchronization messages. The entered date willnot automatically propagate to slave nodes in a hierarchical network.

This commands used to express the date are as follows:

DD-mmm-YY (may be used as input or output)

MM/DD/YY (may only be used as input)

where:

DD = Day of month (01 to 31)MM = Month (01 to 12)mmm = Three-character abbreviation for month (JAN - DEC)YY = Year (01 to 99)

Execute Subformat (SF)

This command specifies a nested format number and causes thedesignated subformat to be accessed as a subroutine. The commandhas the form:

SFn

where:SF = Execute subformat commandn = A number that identifies the subformat to be executed.


Page Formats-23


One subformat can be made to reference another subformat, etc. Amaximum of five subformats may be nested within the command.

A subformat can be any format. There is no difference between first-level formats and subformats. However, care must be exercised toavoid recursive subformat references which will exceed the nestinglevel limit of five.

Block Size (SB)

This command is used to specify the output message block size. Theblock size indicates the number of characters bound between the start-of and end-of-message characters specified via the M field descriptor.If no block size is entered, the default is zero which prevents the startand end characters from providing an output. The form of the blocksize field descriptor is as follows:

SBn

where:

SB = Block size commandn = A number that specifies the message block size (1-255)

❏ Special Input Field DescriptorsThe special input allows looping within a section of the format andconcurrent input of a signal or array cell value while outputting. Thecurrent data row and column, along with the system date and time,can also be inputs. The special input is used to periodically update adisplay while allowing an operator to enter a value or conditional keycode. A special input is only valid for the output mode. The section offormat to be looped may contain any valid output field descriptorexcept may also contain the KK field descriptor which allows condi-tional formatting within the loop based on an input key code.


Page Formats-24


Define Special Input Mode (CI)

The CI field descriptor defines the length of a data entry field that isused to buffer and display characters that are input while looping. Italso defines the loop repetition rate and the section of format to beincluded in the loop. The forms of the special input field descriptorsare as follows:

CIn:r[..format to be looped..]CIn[..format to be looped..]

where:

n = the number of characters in the data entry field (1-64)r = repetition rate of the loop in units of .1 seconds (0-255).

The default value is 0 which results in continuous output.[ = beginning of loop delimiter] = end of loop delimiter

The special input operates as follows. The looped output format isprocessed normally. All characters that are input during the loop areinternally buffered until the end of the loop is encountered, at whichtime they are processed.

The characters are processed in the following manner. If there is a KKfield descriptor in the loop, all input keys other than CTRL-C are firstcompared to the KK field descriptor’s key codes. If the input keymatches, it is used to select the conditional format and is discarded. Ifthe key does not match, it is available for use in the data entry field. Ifthere are more than one KK field descriptors in the loop, only the firstone encountered in the loop is used. All others will be handled asthough no keys matched.

If there are no KK field descriptors in the loop, or the input key doesnot match any of the KK field descriptor’s key codes, the input keysare compared to several key codes that perform special functions.


Page Formats-25


The input keys are handled as follows. Printable (non-ASCII control)characters are put in the data entry field. If the entry field is full, themost recent characters are discarded.

A Delete or Backspace character causes the most recent characterplaced in the data entry field to be erased and discarded.

A CTRL-C character causes the special input loop to be terminated.The data entry field is erased. The field descriptor following the end ofa loop delimiter is processed next. The CTRL-C character alwaysterminates the loop even if a KK descriptor defines the key code.

The carriage return key causes the content of the data entry field to bestored as the current signal or cell value. If the signal or cell is analog,the content of the entry field is converted to a floating point value andstored. If the signal or cell is logical, a value of false is stored if theentry field contains a zero value, and a value of true is stored if theentry field contains a non-zero value. If the signal is a string, theliteral content of the entry field is stored as the signal’s value. Asignal’s value is not stored if it is manually inhibited. If the content ofthe entry field is valid and stored, it is erased. If the entry field isinvalid, an error message is put into the entry field which is erasedwhen the next key is put in the entry field. Error messages too long forthe entry field are truncated.

After the input keys have been processed, the content of the data entryfield is output beginning at the current cursor position. The cursorwould typically be positioned where data entry echo is desired justprior to the end of the loop delimiter. Output formatting continues atthe beginning of the loop after the loop repetition time expires or a keyis input.

Backspace Data Entry Field (CB)

The most recent character put in the data entry field is erased anddiscarded.


Page Formats-26


Clear Data Entry Field (CC)

The entire data entry field is erased and all data entry characters arediscarded.

Enter Data Entry Value (CE)

The content of the data entry field is stored as the current signal orcell value. It performs the same function as the carriage return de-scribed above.

Set System Date (CD)

The content of the data entry field is interpreted as the current systemdate. The system date signals and the internal system date values arechanged to the entered value. The form of the date is the same as forthe SD field descriptor when used for input.

Set System Time (CT)

The content of the data entry field is interpreted as the current systemtime. The system time signals and the internal system time values arechanged to the entered valued. The form of the time is the same as forthe ST field descriptor when used for input.

Raise Current Signal or Cell Value by a Percent-age (CR)

If the current signal or cell is analog, its value is increased by a speci-fied percentage. If the current signal or cell is logical, its value is set totrue. A signal’s value is not changed if it is manually inhibited. Theform of the raise value field descriptor is:


Page Formats-27


CRp

where p = the percentage to increase an analog value (1-255)

Lower Current Signal or Cell Value by a Percent-age (CL)

If the current signal or cell is analog, its value is decreased by aspecified percentage. If the current signal or cell is logical, its value isset to false. A signal’s value is not changed if it is Manually inhibited.The form of the lower value field descriptor is:

CLp

where p = the percentage to decrease an analog value (1-255)

Set Data Array Row (CY)

The current data array row is set to the value in the data entry field. Adata array must have been previously defined via the DA or DL fielddescriptors.

Set Data Array Column (CX)

The current data array column is set to the value in the data entryfield. A data array must have been previously defined via the DA orDL field descriptors.

Terminate Special Input Loop (CQ)

The special input loop is terminated. It performs the same function asCTRL-C described previously.


Page Formats-28


Special Input Error Messages

The data entry error messages are as follows:

BAD VALUE - indicates the content of the data entry field is not avalid analog or logical value.

READ ONLY - indicates a data array is a read only type and cannot bechanged.

MANUAL INHIB - indicates a signal is manually inhibited and maynot be changed.

CONSTANT - identifies the signal as a constant that cannot bechanged.

TRUNCATED - indicates the content of the data entry field is longerthan the string signal’s value field. The extra characters in the entryfield are truncated.

BAD DATE - indicates the content of the data entry field is not a validtime value.

BAD ROW/COL - indicates the content of the data entry field is not avalid data array row or column for the currently defined data array.

ARRAY UNDEFINED - indicates that the current data array row orcolumn cannot be set because a data array has not been defined.

Special Input Example

The following format demonstrates the use of the special input. SignalRepeat mode and Signal Wrap Around modes are set active so thatevery signal in the I/O list can be displayed and changed one at a time.The data entry field is 8 characters long and the loop repetition rate is0.5 second. At the beginning of the loop, the cursor is positioned to row


Page Formats-29


1 and column 1 on a Digital Equipment Corp., Model VT52 compatibleterminal.

The current signal’s name and value are followed by a carriage returnand line feed when displayed. If the ‘N’ key is the input, signal skipcauses the next signal in the I/O list to become the current signal. Thecharacters in the data entry field are displayed on the line below thesignal’s name and value. If the carriage return is the input, the valuein the data entry field is stored as the signal’s value.

SR,SW,CI8:5[P1:1,NN10,’ = ‘,I8,/,KK78(SS)],PV

❏ Julian Date/Time Value DescriptorsThese descriptors are used to output the date or time based on ananalog value that has the same form as the system signal #TIME.000.

Display Julian Date (JD)

The date is output based on the value of the current signal or dataarray cell. The signal or cell must be analog. The form of the output isthe same as the SD field descriptor when it is the output.

Display Julian Time (JT)

The time is output based on the value of the current signal or dataarray cell. The signal or cell must be analog. The form of the output isthe same as the ST field descriptor when it is the output.


Page Formats-30


❏ Cursor Positioning Descriptors

The cursor positioning field descriptors allow moving the cursor to aspecific location on devices that support cursor position commands.The position cursor field descriptor will use a VT52 or ANSI typecursor command depending on the current terminal type. The terminaltype defaults to VT52 mode but can be changed via the PA and PVfield descriptors.

Position Cursor (P)

A position cursor command is the output to the device with the speci-fied row and column values. Either a VT52 type command or an ANSItype command is the output, depending on the current terminal type.The form of the position cursor field descriptor is as follows:

Pr:c

where:

r = Row number (1-25)c = Column number (1-80)

Set Terminal Type to ANSI (PA)

The current terminal type is set to ANSI. The ANSI standard cursorposition commands will be used.

Set Terminal Type to VT52 (PV)

The current terminal type is set to VT52. The VT52 type cursorpositioning commands will be used.


Page Formats-31


❏ Signal Indirection Descriptor (*)

A string signal or constant value may be used to identify the signal tobe used for either input or output. This is referred to as signal indirec-tion. The string value is interpreted as the name of the desired signal.If array mode is not active and the current signal in the I/O list is astring where indirection has been indicated, the signal whose namematches the string value will be used instead of the current signal inthe I/O list. Signal indirection is indicated by immediately preceding afield descriptor with a ‘*’ character. Only those field descriptors thatreference the I/O list make use of indirection. Indirection is mostuseful during special input mode where the ability exists to access anysignal without having it in the I/O list.

If there is no signal with a name matching the string value, an error isindicated. If special input mode is not active, the error causes theformat to be aborted and the Logger completion code is set to indicatethat the indirect signal name is invalid. If the Special Input mode isactive, the format continues but the output fields are filled withasterisks, the conditional field descriptors assume a false conditionand data entry for the signal is ignored.

The following field descriptors will make use of signal indirection ifthey are preceded by an asterisk character (*).

CE, CL DA, DL, E, F, I, JD, JT, KA, KD, KC, KH, KHH, KI, KL, KLL,KM, KS, KTA, KTL, KTS, KV, KW, KX, KY, KZ, L, NA, NB, ND, NN,NT, Q, SAE, SAI, SCE, SCI, SME, SMI, T, and U.

Positioning And Structuring Commands

These commands control the positioning and structuring of datadisplayed on a screen or printer. They are described as follows:


Page Formats-32


I/O Directional Commands

A Logger Module can function as an input or output device. The initialdirection of signal flow is set at the MODE terminal on the LoggerModule Menu; the choices for this terminal are set to input or outputmode. However, if a Logger is used to conduct both input and outputsignal traffic, directional commands will be required. These com-mands, which must precede the descriptor, set the direction of allsignals that follow it until the next directional command is encoun-tered. The command symbols are:

< set input mode> set output mode

Separators

Separation between commands are blank spaces or commas. If there isno ambiguity between the end of one command and the start of thenext, separators are not necessary. In general, the only time ambiguitycan exist is when two numbers of two different commands are adja-cent. For example, F201.13X would be interpreted as the following twocommands: F201.13 and X. If you intended the two commands to beF201 and 3X, then use commas as shown below.

F201.1,3X

Nest Delimiters

Parenthesis are used to contain items such as repeat count specifica-tions and expressions. Up to five levels of parenthesis may be used forboth inputs and outputs.

( ) =Used for group repeat count specifications and expressions.


Page Formats-33


End of Line Indicator

The slash (/) functions as an end-of-line indicator and causes a carriagereturn [CR], null, and line feed [LF] to be sent to the external device.Some external devices require a time delay between a [CR] and [LF]and the start of the next line of characters. In these cases, the slashmust be followed by a number of null characters, such as quotationmarks.

Example: /””

The number of null characters required will depend upon the mechan-ics of the device and the baud rate used in transmission.

Text Delimiters

A set of single or double quotation marks (‘ or “) function as textdelimiters. They may be used to enclose text in a format that will beprinted or displayed on the ASCII device. As an example, “POWERUPMODE” or `POWERUP MODE’ will appear as POWERUP MODE.Text delimiters should always be used in pairs to provide the neces-sary End-of-Format detection.

Space Command

This command inserts spaces between text or value characters. Whenused in an output statement, this command transmits a specifiednumber of blank spaces to the printer or CRT. When used in an inputstatement, it specifies the subsequent number of characters receivedfrom the input device that will be skipped. This command has thefollowing format:

nX


Page Formats-34


where:

n = This number specifies the number of spaces to be skipped.

X= Space command character

Example A

Internal values are: 7.93212 PSIFormat specification is: F3.1,1X,U3Equivalent output is: 7.9-PSI {Dash signifies 1 space}

Example B

Input values are: 76.4123 and 796.59Format specification is: F4.2,6X,I3Internal values are: 76.41———797 {Dashes signify 6 spaces}

ASCII Control Characters

The pound sign (#) is used to specify the transmission of nonprintingASCII keyboard functions such as carriage return, tab, space, control,etc. The format is:

#n

where:

# = ASCII control charactern = is a decimal number representing the ASCII character.

Example: 9=TAB and 13=CR


Page Formats-35


❏ PLC-Type Format Descriptors(Available only in PLS/PLX/PES/PEX 04.20 firmware or newer)

IMPORTANT: The PLC-type format descriptors require that theLogger Port be declared with 8 data bits per character instead of thestandard 7 bits per character in ASCII mode. As a result, when for-mats are intermixed, it is the user's responsibility to verify that theLogger generates intended results.

BIT - Bit alignment mode is set active. This means that the data in amessage is processed in units of bits. Lower order bits of a byteor word are processed before higher order bits. Bit alignmentmode is used to access single bit logical values and sub-fieldswithin a byte or word. If WRD alignment mode was previouslyactive, any remaining bits of the current word are used beforethe next data byte is processed.

BYT - Byte alignment mode is set active. This means that the data ina message is processed in units of 8-bit bytes. Each field beginswith the low order bit of the next byte. Values are treated asbeing right justified within the byte (low bit on the right). IfWRD alignment mode was previously active and the high orderbyte of the word was not used, the high byte is processed beforethe next data byte.

WRD - Word alignment mode is set active. This means that the data ina message is processed in units of 16-bit words. The LBF (LowByte First) and HBF (High Byte First) format codes are used tospecify the byte order in the word. HBF and word alignmentmodes are the default for register values.

LBF - Low Byte First mode is set active. WRD alignment mode willtreat the first of two data bytes as the low order byte of the 16-bit word.


Page Formats-36


HBF - High Byte First mode is set active. WRD alignment mode willtreat the first of two data bytes as being the high order byte ofthe 16-bit word.

VL - This descriptor is used for input or output of logical values. Itoperates on either single bits, full bytes, or full words dependingon the alignment mode. In BIT mode, each bit in the datacorresponds to an ACCOL signal in the I/O list (or elements inthe I/O data array); in BYT mode, 8 bits corresponds to onesignal (or data array element) and in WRD mode, 16 bits corre-sponds to one signal (or data array element). Therefore, depend-ing on the mode, the data bit, byte, or word is tested as a singleunit for zero; a zero is treated as OFF, non-zero as ON, and thesignal in the I/O list (or element in the I/O data array) is set tothe detected state. Analog signals in the I/O list (or analog valuesin the data array) are set to 0.0 for OFF and 1.0 for ON. Stringsignals are invalid.

For output, the value in the I/O List or array is tested and thetransmitted value is set ON or OFF as required. Analog valuesproduce OFF for 0.0 and ON for non-zero. The next I/O listsignal or I/O data array element becomes current after each useof this descriptor.

VSn - This descriptor is used for input or output of signed (2’s comple-ment) binary values with a field width of n bits. If BIT mode isactive, the next n bits in the message are converted to a signedn-bit value. If BYT mode is active, 8 bits are converted; if WRDmode is active, 16 bits are converted. If n is larger than 8 in BYTmode, then n/8 bytes will be converted. If n is larger than 16 inWRD mode, then n/16 bytes will be converted. The value of nmay range from 2 to 32. The default if nothing is specified for nis 2 for BIT mode, 8 for BYT mode, and 16 for WRD mode.

For input, the current signal in the I/O list (or the currentelement in the data array) is set to the converted value of thedata field. Logical signals or array elements are set to OFF if the


Page Formats-37


value is zero and set to ON if the value is non-zero. Stringsignals are invalid. The next signal in the I/O list becomescurrent after each use of this descriptor (or the next element inthe data array becomes current if array mode is active).

VUn - This descriptor is the same as VSn with the following excep-tions: The binary value is unsigned and n may range from 1 to32. Negative values are converted to zero. The maximum valuein a 32 bit field is limited to a 31 bit number for both input andoutput.

BCDn - This descriptor is used for input or output of Binary CodedDecimal (BCD) values with a field width of n BCD digits of 4 bitsper digit. If BIT mode is active, the next n*4 bits in the messageare used with the first digit treated as the highest order digit.The value of n may range from 1 to 39. The default value for n ifnot specified is 1 for BIT mode, 2 for BYT mode, and 4 for WRDmode.

For input, the current signal in the I/O list or the current arrayelement in the data array is set to the value of the field. Logicalsignals or array elements are set to OFF if the value is zero andset to ON if the value is non zero. String signals are invalid.

For output, the value of the current signal or array element isput in the message. Logical signal or array elements of OFF areequivalent to 0 and values of ON are equivalent to 1. Stringsignals are invalid.

The next signal in the I/O list or the next array element in thedata array becomes current after each use of this descriptor.

CST1:0 This field treats the next 4 data bytes as an IEEE floatingpoint format value when converting. The next signal in the I/Olist (or element in the I/O data array) becomes current after thisdescriptor is used.


Page Formats-38


CST2:0 This field treats the next 4 data bytes as a Whipple floatingpoint format value when converting. The next signal in the I/Olist (or element in the I/O data array) becomes current after thisdescriptor is used.

CST3:0 This field performs the same function as CST1:0 for IEEEfloating point format values except that it is used only when datais sent/received in Intel order.

CST4:0 This field performs the same function as CST2:0 for Whipplefloating point format values except that it is used only whendata is sent/received in Intel order.

FPVSupercompressibility Factor (FPV) Module


Page FPV-1

The FPV Module computes the supercompressibility factor (Fpv) of agas measured in accordance with the American Gas AssociationReport No. NX-19.

The Fpv calculation makes pressure and temperature adjustments inorder to reach standard measurement conditions. The calculationsrequire that the measured gas does not exceed a specific gravity of0.750, and/or a diluent content of 15 mole percent for carbon dioxide,and/or 15 mole percent for nitrogen. This method of measurement is,therefore, limited to natural gas mixtures that do not contain largeconcentrations of heavier hydrocarbons.

Module TerminalsFLOW_TEMP(FT)

is the flowing temperature of the gas in degrees F.

STAT_PRESS

is the static pressure of the gas in psig.



FLOW_TEMP

STAT_PRESS

SPEC_GRAV

NMOLE

OUTPUTFPV

CO2_MOLE

FPV


Page FPV-2




SPEC_GRAV(Fg)

is the specific gravity of the gas.

CO2_MOLE(Mc)

is the carbon dioxide content mole in percent (%).

NMOLE(M

n)

is the nitrogen content mole in percent (%).

OUTPUT(Fpv)

is the computed supercompressibility factor.

Supercompressibility Factor Equations

The FPV Module is implemented using equations rather than tables.With reference to the American Gas Association, Report NX-19,equations E1, E2, E3, E4, E5a, E5b, E5c, and E6 are implemented.This gives proper values for adjusted temperature and pressure overthe following ranges.





Page FPV-3

E1: 850F < adj. temperature < 2400F0 psia < adj. pressure < 2000 psia

E2: -400F < adj. temperature < 850F0 psia < adj. pressure < 1300 psia

E3: -200F < adj. temperature <850F1300 psia < adj. pressure 2000 psia

E4: -400F < adj. temperature -200F

1300 psia < adj. pressure 2000 psia

E5a: -400F < adj. temperature -200F2000 psia < adj. pressure 5000 psia

E5b

: -200F < adj. temperature 850F2000 psia < adj. pressure 5000 psia

E5c: 850F < adj. temperature 2000F2000 psia < adj. pressure 5000 psia

E6: 2000F < adj. temperature 2400F2000 psia < adj. pressure 5000 psia

If inputs to this module fall outside these ranges, the value for E willbe forced to 1.0.

Calculating Adjusted Temperature and Pressure

The parameters required to determine the adjusted pressures andtemperatures are: specific gravity, carbon dioxide, nitrogen content,gauge pressure, and absolute flowing temperature. The basic equa-tions of NX-19 are rearranged to those shown below. These rearrange-ments speed up calculations, especially when a default specific gravityis used.


Page FPV-4


The adjusted pressure is obtained by multiplying the gauge pressureof the flowing gas by the pressure adjusting factor, Fp. This factor isequal to:

Fp =

where:

DG = Specific gravity of flowing gas -0.6Mc = Mole percent carbon dioxideMn = Mole percent nitrogen

The adjusted absolute temperature is obtained by multiplying theabsolute temperature of the flowing gas by the temperature adjustingfactor, F

T. This factor is defined as follows:

FT =

Appendix B, Section 13 of the AGA-3 report contains details on rear-rangements of the AGA-3 equations that produced those shown above.

(160.8 + Mc - 7.22 * DG - 0.392 * Mn)

156.47

226.29

99.15 + 211.9 * DG - Mc - 1.681 * Mn

FunctionFunction Module


Page Function-1

The Function Module is used to look up values in an analog dataarray. The analog data array number is indicated by the ARRAYterminal. The array element is indicated by the ROW and COLUMNterminals. The value of that array element is then assigned to a signalwhich is named by the OUTPUT terminal.

❏ Module TerminalsARRAY Default: None, entry required


is an analog array.

ROW Default: 1 (first or top-most row)Format: Analog signal or constantInput/Output: Input

defines the row of the array by naming the first value in the row.

COLUMN Default: 1 (first or left-most column)Format: Analog signal or constantInput/Output: Input

defines the column of the array by naming the first value in thecolumn.

ROW

COLUMN

ARRAY

OUTPUT

XXXXXXXX

Function

Page Function-2



OUTPUT Default: None, entry requiredFormat: Analog signalInput/Output: Output

is an array element or an interpolated value.

❏ Referencing an Array ElementArray elements are referenced by naming two values: the arrayelement at the top of the column and the element to the extreme left ofthe row.

In the following example, the first row represents temperatures of 0,20, 40, 60, 80 and 100 degrees. The first column represents pressuresof 0, 50, 100 and 150 psi. Values between this row and column areyour data values. When the ROW terminal is 50 and the COLUMNterminal is 40, the value on the OUTPUT terminal will be 75.

-10 0 20 40 60 80 100 First row

0 0 55 65 75 85 95 Temperature indices50 0 65 75 85 95 105 0 to 100 Degrees

100 0 75 85 95 105 115150 0 85 95 105 115 125

First column

Pressure Indices0 to 150 psi



Page Function-3

In general, the data array element in the first row and first columnshould be a number that is lower than the lowest value to be meas-ured. Since the lowest measurement in the above array is taken at 0degrees and 0 psi, the first element in the first row and column wasmade a negative value (-10). The negative value prevents the arrayfrom using the pressure values in the first column as outputs when-ever the selected temperature is 0 degrees.

When the value on the ROW or COLUMN terminal cannot be found,the Function Module calculates a value using interpolation. Interpola-tion is first performed on the row and then on the column. In theexample above, if COLUMN input is 70 and the ROW input is 50, thevalue on the OUTPUT terminal would be 90.

If any values exceed the range of the array, the boundary value will beused as the output.

❏ Setting Up the Analog DataCare must be taken when setting up the array. An indexing columnand row like the temperature and pressure in the previous examplemust be entered.* The figure on the next page shows an analog arrayfor the previous example, as it would appear in the AIC.

The smallest data array that can beused is a two column array. In thisspecial case, the first column containsindexing values and the second columncontains your data values.

In the array shown to the right, whenthe ROW terminal is 2, the value of thesignal named in the OUTPUT terminalis 77. In this case, COLUMN should be1 or left blank.

0 55

1 66

2 77

3 88

4 99

*If you use the AIC to create the array, be aware that themenu for creating data arrays has additional indexingnumbers; these are not used by the Function Module.

Page Function-4



Also, in order for interpolation to be accurate, values in the first rowand column must be in ascending order.

Analog RO Data Array: 1Press Renumber to change the base column

1 2 3 4

1 -10.0000000 0.0000000 20.0000000 40.00000002 0.0000000 0.0000000 55.0000000 65.00000003 50.0000000 0.0000000 65.0000000 75.00000004 100.0000000 0.0000000 75.0000000 85.00000005 150.0000000 0.0000000 85.0000000 95.0000000

Analog RO Data Array Menu

GOTOGO TO Statement


Page GOTO-1

The unconditional GOTO command provides branching to a specifiedline in the task.

SyntaxGOTO n

where n is a line number. It must be separated from the command bya line or a space.

Example

10 GOTO 60

When statement 10 in the above example is executed, statementnumber 60 will be executed next and all the statements between 10and 60 will be skipped.

GOTO

BLANK PAGE

ACCOL II Reference ManualPage GPA8173-1

GPA8173GPA8173 Volumetric Flow Measurement Module

The GPA8173 Module converts the mass of natural gas liquids toequivalent liquid volumes at base conditions, in either CustomaryEnglish units (60o F, 14.696 psia) or Standard International (SI) units(288.15 K, 101.3250Pa(abs)). The conversion is performed according tothe Gas Processor's Association Standard 8173-94. The GPA8173Module is useful when the flow rate is measured with a Mass Meter(e.g. Orifice Meter). This module requires a constituent breakdown(Mole Percent analysis) of the liquid.

❏ Module TerminalsMETERMASS Default: None, entry required


is the measured mass of natural gas liquids or vapors, at flowingconditions, to be converted to equivalent liquid volume(s). Typically,the source for METERMASS is the output from a mass meter (e.g.Orifice Meter). If Customary English is chosen for the UNITS, themeasured mass must be in LB Mass. If Standard International ischosen for the UNITS, the measured mass must be in Kilograms.

GPA8173


Page GPA8173-2


UNITS Default: 1.0Format: Analog signalInput/Output: Input

selects the units which will be used for the METERMASS,EQUIVVOLSTRUCT and EQUIVVOL terminals. The choices for unitsare:

1 Customary English units2 Standard International (SI) units

The base temperature conditions of these two unit types are slightlydifferent.

NUMMOLETYPE Default: None, entry requiredFormat: Analog signalInput/Output: Input

is the total number of constituent molecule types composing the liquid.This number CANNOT exceed 40.

STRUCTMODE Default: 1.0 (Signal List) if unwiredFormat: Analog signalInput/Output: Input

selects which type of structure will be used for the SPECIDSTRUCT,MOLEFRACTSTRUCT, and EQUIVVOLSTRUCT terminals. Thechoices of structures are:

1 Signal List2 Analog Data Array (1-dimensional)

SPECIDSTRUCT Default: None, entry requiredFormat: Analog signalInput/Output: Input

identifies the number of the structure, of size NUMMOLETYPE,



which specifies the set of molecular specie making up the liquid orvapor of interest. The user populates the structure, with specie IDcodes drawn from the BBMSCT Table and optionally, by the impliedSpecies codes of the ACCOL Array specified by the CUSTCONSTARRYterminal. The Specie ID codes identify to the Module which constantsin the BBMSCT Table, and in the CUSTCONSTARRY, are to be usedin computing the Equivalent Volume results. NOTE: If you mistakenlyenter a particular specie ID code more than once, the result will beincorrect.

MOLEFRACTSTRUCT Default: None, entry requiredFormat: Analog signalInput/Output: Input

identifies the number of the structure, of size NUMMOLETYPE,which contains the mole fraction values (as percentages), one perstructure element, for the constituents making up the liquid of inter-est. The sum of the mole fractions of the set of NUMMOLETYPEelements must add up to exactly 100.0. The elements of this structureparallel those in the SPECIDSTRUCT. For example, if the thirdelement of the SPECIDSTRUCT contains the Specie id code corre-sponding to Methane, then the third element of theMOLEFRACTSTRUCT must be populated with the value of Methane’sMole Fraction in the liquid.

CUSTCONSTARRY Default: NoneFormat: Analog signalInput/Output: Input

allows the user to add additional molecular specie for use in thecalculations. The CUSTCONSTARRY terminal identifies a Read-OnlyAnalog Array called the User Specified Molecular Specie ConstantsTable (USMSCT). Unlike the BBMSCT Table which comes pre-definedwith a select set of commonly encountered molecular specie, theUSMSCT is filled entirely with constants entered by the user. TheUSMSCT is necessary whenever the fluid to be measured includes


Page GPA8173-4


specie outside the set defined in the BBMSCT. The USMSCT is usedto add the additional specie(s). In addition, the USMSCT may used tooverride constant values in the BBMSCT, to conform to the user’straditional (legacy) values.

EQUIVVOLSTRUCT Default: NoneFormat: Analog signalInput/Output: Output

identifies the number of the structure, of size NUMMOLETYPE,which contains the individual calculated equivalent volumes at baseconditions, one per structure element, for the constituents making upthe liquid or vapor of interest. The elements of this structure parallelthose in the MOLEFRACTSTRUCT. These volumes will be in gallonsif Custom English is chosen for the UNITS; if Standard Internationalis chosen for the UNITS, these volumes will be in cubic meters (m3).

EQUIVVOL Default: NoneFormat: Analog signalInput/Output: Output

is the number of the calculated equivalent volume for the mass valueentered at the METERMASS terminal. That is, the sum of theNUMMOLETYPE elements found in the EQUIVVOLSTRUCT struc-ture. This volume will be in gallons if Custom English is chosen for theUNITS; if Standard International is chosen for the UNITS, thisvolume will be in cubic meters (m3).

RERESOLVE Default: NoneFormat: Logical signalInput/Output: Input/Output

forces recalculation of initial conditions. To save computational re-sources and increase speed, the structures containing mole fractions,molecular weight data, and absolute densities, are only opened and



validated the first time the Module executes. If the user choosesto alter the contents of any of these structures, after the Module hasstarted running, then the RERESOLVE terminal MUST be turnedON. The module will then re-evaluate the structures and then set theRERESOLVE terminal OFF.


reports status codes related to module operation. Negative codestypically indicate configuration errors. Valid status codes include:

0 Calculation completed successfully.-1 MOLEFRACTSTRUCT terminal unwired.-2 SPECIDSTRUCT terminal unwired.-3 METERMASS terminal unwired.-4 METERMASS terminal not an analog value.-5 Invalid mass value.-6 Invalid dynamic Module Control Block (MCB).

This is an internal firmware error.-7 Number of specie terminals unwired.-8 Invalid number of species.-9 Invalid structure number.

-10 Invalid structure mode.-11 Invalid mole fraction-12 Invalid molecular weight-13 Sum of individual mole fractions does not equal

100%.-14 Missing molecular weight for a specie.-15 Invalid CUSTCONSTARRY.-16 Invalid UNITS.-17 Invalid Specie ID.-18 Internal and external data types are different.-19 List item is not an analog.-20 Unable to write analog array element.


Page GPA8173-6


❏ Choosing Module Molecular Specie Constants

Required by Liquid Flow Calculations.

The GPA8173 Module and some of the calculations in theLiquid_Density Module, each require constants specific to each of themolecular specie contained in the fluid for which the Module is makinga calculation. A select set of Molecular Specie and their associatedconstants has been built into the ACCOL firmware for use by thesemodules - - it is referred to as the Bristol Molecular Specie ConstantsTable (BBMSCT). The ACCOL user can draw upon these constants byspecifying the number of species in a particular fluid on theNUMMOLETYPE terminal, and then specifying the number(s) of thedesired specie constants within the SPECIDSTRUCT list or array.

If one or more of the molecular species defined in the BBMSCT areconstituent parts of the fluid to be measured, but the constant valuesin the BBMSCT are unsatisfactory for the user's application, -orif theuser wants to add additional molecular species, not included in theBBMSCT, user defined definitions of those particular molecularspecies can be defined in the User Specified Molecular Specie ConstantTable (USMSCT), which is configured through the CUSTCONSTARRYterminal.



Bristol Molecular Specie Constants Table (BBMSCT)

This is a table embedded in the ACCOL firmware. Each molecularspecie resides in a row with 8 Columns. These columns are: MolecularSpecies, BBI Molecular Specie Code, Molecular Weight, RelativeDensity @60 oF and 14.696 psia, Relative Density @ 288 oK and101.3250 kPa(abs), Characteristic Volume, Acentric Constant andCritical Temperature. The contents of this table are printed on thenext page. Each Molecular Specie in the table is identified by a codewhich is a positive number corresponding to its row position in thetable.

The entries in the BBMSCT come from two sources:

Entries for Molecular Weight, Relative Density, and Critical Tempera-ture are drawn from GPA Standard 2145-96, Table of Physical Con-stants of Paraffin Hydrocarbons and other Components of NaturalGas.

Entries for Characteristic Volume and Acentric Constant are drawnfrom Risdon W. Hankinson and George H. Thomson, AICHE Journal(Vol. 25, No. 4) July, 1979, Table 6.

NOTE: The GPA8173 Module only requires the molecular weight andrelative density columns to be populated.


Page GPA8173-8


BBMSCT

Molecular Specie Molecular Relative Relative Charac- Acentric Critical

Species Code Weight (gm- Density Density @ teristic Constant Temp.mole) @60 deg F, 288.15 def K, Volume - deg F

14.696 psia 101.3250

kPa (abs)

Methane 1 16.0430 0.3 0.3 0.09939 0.0074 -116.66

Ethane 2 30.0700 0.35619 0.35808 0.14580 0.0983 90.07

Nitrogen 3 28.0134 0.80940 0.80933 0.09012 0.0358 -232.49

Propane 4 44.0970 0.50698 0.50776 0.20010 0.1532 205.92

Iso-Butane 5 58.1230 0.56286 0.56349 0.25680 0.1825 274.41

n-Butane 6 58.1230 0.58402 0.58459 0.25440 0.2008 305.51

Iso-Pentane 7 72.1500 0.62441 0.62491 0.30960 0.24 368.96

n-Pentane 8 72.1500 0.63108 0.63157 0.31130 0.2522 385.70

Carbon Dioxide 9 44.0100 0.81801 0.82268 0.09384 0.2373 87.73

n-Hexane 10 86.1770 0.66404 0.66449 0.36820 0.3007 451.80

n-Heptane 11 100.2040 0.68805 0.68846 0.43040 0.3507 510.90

n-Octane 12 114.2310 0.70678 0.70718 0.49040 0.3998 563.50

n-Nonane 13 128.2580 0.72193 0.72231 0.55290 0.4478 610.80

n-Decane 14 142.2850 0.73417 0.73452 0.61920 0.4916 652.20

Hydrogen Sulfide 15 34.0800 0.80143 0.80262 0.09941 0.1039 212.40

Oxygen 16 31.9988 1.1421 1.1420 0.07382 0.0298 -181.41

Air 17 28.9625 0.87475 0.87469 0.08747 0.0031 -221.30

Water 18 18.0153 1.00000 1.0000 0.43570 0.3852 705.11



User Specified Molecular Specie Constant Table (USMSCT).

The User Specified Molecular Specie Constant Table (USMSCT) allowsthe user to provide constants for additional species not provided in theBBMSCT Table. This table also provides a mechanism to substitutedifferent specie constants for molecular species defined in theBBMSCT.

The USMSCT resides in an ACCOL analog data array. To create anduse the USMSCT, the user creates an empty analog array. The num-ber of the analog array must be specified on the CUSTCONSTARRYterminal.

The analog array must have the same number of rows as species to beincluded in the table, and six columns. These 6 columns includeMolecular Weight, Relative Density (Customary English Units),Relative Density (SI), Characteristic Volume, Acentric Constant andCritical Temperature.

The user then populates each row, starting at row 1, contiguously,with the constants associated with a particular molecule. The order ofconstants must follow the order given in the paragraph above.

The specie code is implied by its row position. All specie codes associ-ated with molecular species in the USMSCT table must have a minussign in front of them, to distinguish them from BBMSCT specie codes.Therefore, when referencing USMSCT species in the SPECIDSTRUCTstructure, the specie in Row 1 of the USMSCT must be entered asspecie code -1, row 2 of the USMSCT is entered as specie code -2, etc.

The Modules’s UNITS terminal is used to select the value of density,for use in internal calculations, from one of the relative density col-umns in the USMSCT.


Page GPA8173-10


USMSCT Table

Molecular Specie Molecular Relative Relative Charac- Acentric Critical

Species Code Weight (gm- Density Density @ teristic Constant Temp.mole) @60 deg F, 288.15 def K, Volume - deg F

14.696 psia 101.3250

kPa (abs)

Trichloro- user user user user user usertrifluoroethane -1 value value value value value value

Ethane -2 user user user user user uservalue value value value value value

| |These two columns are NOT part of the USMSCT array; they are shown for information only.

Note the Specie codes in the above table for Trichlorotrifluoroethaneand Ethane. Trichlorotrifluoroethane is not in the BBMSCT table,whereas Ethane is. Use of these codes in the SPECIDSTRUCTstructure will result in these user supplied constants for Trichloro-trifluoroethane and Ethane being used in the Module’s calculations.

WARNING

The GPA8173 Module assumes that for each specie in the table, theuser is providing a Molecular Weight and two Relative Densities. TheGPA8173 does not check for multiple occurrences of any specie code. Ifthe same Specie code is used multiple times, only the propertiesassociated with the last declaration of the Specie Code in the structurewill be used. An error will probably result, due to the fact that themole fraction value will be counted more than once.




In order to perform volumetric calculations, the dynamic inputs (e.g.flowing temperature, flowing pressure, etc.) must be sampled at leastevery 5 seconds.

The GPA8173 Module requires that the user provide a constituentbreakdown (Mole Percent analysis) of the liquid for which volume is tobe calculated.

The mass of the liquid, for example, as measured by an orifice meter,should be entered on the METERMASS signal.

If you want the units to be in Lb-mass and gallons, choose CustomaryEnglish for the UNITS, if you want the units to be in Kilograms andcubic meters, choose Standard International for the UNITS. NOTE:Base conditions differ by 0.5o C between the two possible sets of units.

Specify the total number of constituent molecular species in the liquidon the NUMMOLETYPE terminal.

Create a species ID structure. (The SPECIDSTRUCT can be either asignal list or a data array; the choice is determined by theSTRUCTMODE terminal.)

If the constants for a particular molecular specie in your liquid, asdefined in the BBMSCT table, are adequate for your application, enterthe specie ID for that molecular specie in the SPECIDSTRUCT struc-ture.

If the constants for a particular specie in the BBMSCT table are notusable for your liquid application, or if you want to define a differentmolecular specie, not included in the BBMSCT, create an analog array


Page GPA8173-12


(referred to as the USMSCT) containing a row for each such species.The array number must be entered on the CUSTOMCONSTARRYterminal. Each row of the USMSCT consists of six required constantsfor that specie (molecular weight, relative density (Customary Englishunits), relative density (Standard International units), characteristicvolume, acentric constant, and critical temperature. Enter the specieID for each such molecule in the SPECIDSTRUCT. (The specie ID fora specie in the USMSCT is the row number in the USMSCT, precededby a minus '-' sign.Create either a signal list or array and enter its number on theMOLEFRACTSTRUCT terminal. (The choice of signal list or array isdetermined by the STRUCTMODE terminal.) The MOLEFRACTSTRUCTstructure contains mole fraction values for each of the correspondingentries in the SPECIDSTRUCT. The mole fraction values must mirrorthe order used in the SPECIDSTRUCT, for example, the first elementin the MOLEFRACTSTRUCT corresponds to the first entry in theSPECIDSTRUCT.

Optionally, create another structure, which holds the same number ofelements as the MOLEFRACTSTRUCT, and identify it on theEQUIVVOLSTRUCT terminal.

When the GPA8173 module is executed, volumes will be calculated foreach molecular specie, and, if configured, will be stored in theEQUIVVOLSTRUCT structure. The sum of the individual volumes isreported on the EQUIVVOL terminal.

❏ ExampleAssume that we have a liquid made up of 5 species (Set the ModuleTerminal NUMMOLETYPE to 5), which include: Methane, Ethane,Propane, n-Hexane and Trichlorotrifluoroethane. In the BBMSCTTable, on page 8 of this section, we observe that the Specie ID code forthe first four are respectively 1, 2, 4 and 10.



Trichlorotrifluoroethane does NOT appear in the BBMSCT Table,however, so we will have to construct a USMSCT (analog data array#34, as referenced on the CUSTCONSTARRY terminal). Also, let'sassume that for our application, we want to use a Critical Tempera-ture of 205.3 for Propane, instead of 205.92. Propane, therefore, mustalso be included in our USMSCT.

Construct a two row USMSCT Table, (as shown in the figure on theopposite page) which includes data for Trichlorotrifluoroethane andPropane. Include the molecular weight, relative densities in bothCommon English and Standard International untis, the characteristicvolume, acentric constant, and critical temperature for each.

These two molecular specie will be referenced in the SPECIDSTRUCT(signal list #21). Negative values representing the rows they occupy inthe USMSCT are used as the specie ID. The specie IDs for the otherthree constituent components of the fluid (n-hexane, methane, andethane) are also included. For these three, the specie IDs refer to theirlocations in the BBMSCT (see page 8).

The mole fractions for each of the constituent components are enteredin the MOLEFRACT structure (signal list #22). The sum of all of themole percentages MUST ADD UP TO 100.

The GPA8173 Module will calculate the equivalent volume for eachmole fraction, and store it in the EQUIVVOL structure (signal list#23).

Finally, the module will calculate the equivalent volume for the entirefluid, and store it in the the EQUIVVOL signal.


Page GPA8173-14


IMPORTANT: The values entered in array #34 of the example, above,are fictitious, and are NOT meant to represent the actual physicalconstants of a real fluid. In addition, the choice of signal names in thisexample is arbitrary, however, ordering MUST MATCH between thevarious structures.

ACCOL II Reference ManualPage GSV-1

GSVGross Standard Volume Module

The GSV Module calculates the Gross Standard Volume (GSV) over asampling period for a fluid that is entirely in a liquid state. Alsocalculated are the Net Standard Volume (NSV), Combined CorrectionFactor (CCF), and the Fiscal Correction for sediment and water(CSW). To perform a Volumetric Flow Measurement, the user selectsa liquid type and then supplies values for base density, flowing tem-perature, flowing pressure, equilibrium pressure of the liquid atflowing conditions, Meter Factor, and percent sediment and water(S&W). For liquid petroleum gas (LPG), the calculations performedare based on standards which include the American Petroleum Insti-tute - Manual of Petroleum Measurement Standards, Chapter 21,Section 2.

❏ Module TerminalsLIQUIDTYPE Default: None, entry required


is a value representing the liquid on which calculations will be per-formed:

GSV


Page GSV-2


Liquid Petroleum Gas (LPG) = 1

LIQUIDVALID Default: None, entry requiredFormat: Analog signalInput/Output: Input

indicates whether the fluid being measured is entirely in a liquidstate. In the case of LPG, this determination can be made by wiringthis terminal to the signal on the COMPLIQSTATE output terminal ofthe EVP Module.

If, for any reason, LIQUIDVALID is a value other than 1.0 (i.e., notentirely in the liquid state), the GSV Module will not perform anyfluid flow calculations and will not update any output terminals,except for the STATUS terminal. The STATUS terminal will be set tothe “not a liquid” success code and internal registers will not beupdated.

BASE_DENS Default: None, entry requiredFormat: Analog signalInput/Output: Input

is the Density Value of the measured liquid at base conditions of14.696 psia(101.325 kPa) and 60.00F(15.560C). Units are set via theUNITS Terminal.

TCMUSED Default: OFF, if unwiredFormat: Logical signalInput/Output: Input

when set to ON indicates that the temperature was measured with aTemperature Compensated Meter. The module will calculate the GSVwith the Correction for the Temperature effect on the Liquid (CTL) setto 1.0.



PCMUSED Default: OFF, if unwiredFormat: Logical signalInput/Output: Input

when set to ON indicates that the pressure was measured with aPressure Compensated Meter. The module will calculate the GSV withthe Correction for the Pressure effect on the Liquid (CPL) set to 1.0.


is the temperature, in degrees Fahrenheit, of the liquid at flowingconditions.

FLOW_PRESS Default: None, entry requiredFormat: Analog signalInput/Output: Input

is the pressure of the liquid, in psia or psig, at flowing conditions.Note: Units for FLOW_PRESS and EQVAPRPRESS must be thesame.

EQVAPRPRESS Default: None, entry requiredFormat: Analog signalInput/Output: Input

is the Equilibrium Vapor Pressure, in units of psia or psig, of theliquid at flowing conditions. Note: Units for FLOW_PRESS andEQVAPRPRESS must be the same. In the case of LPG, theEQVAPRESS can be obtained from the COMPVAPORPRESS outputterminal of the EVP Module.


Page GSV-4


METERFACTOR Default: 1.0, if unwiredFormat: Analog signalInput/Output: Input

is the Meter Factor (MF) or Combined Meter Factor (CMF), multiplierdeveloped at meter proving time.

METERROLLOVER Default: 65,535Format: Analog signalInput/Output: Input

is set to the maximum value that the Flow meter is capable of regis-tering. When reaching this number, the internal software will roll overto zero on the next increment, and compute volume differences accord-ingly. The largest number that may be submitted to this terminal isthe Single Precision maximum value (i.e. 3.402823e+38).

CURMETERVAL Default: none, entry required if CCF is notwired


is the current value registered by the Flow meter. The largest numberthat may be submitted to this terminal is the Single Precision maxi-mum value (i.e. 3.402823e+38).

IVMULTI Default: 1.0, if unwiredFormat: Analog signalInput/Output: Input

is a factor which is multiplied by the difference of the current meterreading minus the previous meter reading. IVMULTI is intended forapplications in which the input is a pulse count, which needs to bemultiplied by a conversion factor before use.



SEDANDWATER Default: 0.0, if unwiredFormat: Analog signalInput/Output: Input

is the total combined percent of Sediment and Water (S&W).SEDANDWATER must be between 0.0 and 100.0 percent.

INIT Default: None, entry required.Format: Logical signalInput/Output: Input

must be set ON to initiate flow measurement and calculation. WhenINIT is ON, the value of CURMETERVAL is set as the zero referencepoint for all further internal calculations. This terminal will be setOFF immediately after the start of flow measurement and calculation.

UNITS Default: 1.0Format: Analog signalInput/Output: Input

selects which engineering units will be used for the BASE_DENSterminal. Valid choices are:

1.0 Relative Density2.0 gm/cm3

3.0 lb/gal4.0 Degrees API (oAPI)


Page GSV-6


ACOEFF Default: NoneFormat: Analog signalInput/Output: Output

performs different calculations depending upon the choice ofLIQUIDTYPE. For LIQUIDTYPE of LPG, this terminal outputs thecalculated A coefficient in the LNG/LPG’s compressibility relationshipF=1/(A+Dp*B).

BCOEFF Default: NoneFormat: Analog signalInput/Output: Output

outputs the calculated B coefficient in the LNG/LPG’s compressibilityrelationship F=1/(A+Dp*B) whenever the LIQUIDTYPE is LPG.

CTL Default: NoneFormat: Analog signalInput/Output: Output

is the Correction for the effect of Temperature on Liquid . This value issupplied for use in the Quantity Transaction Record (QTR) describedin the American Petroleum Institute - Manual of Petroleum Measure-ment Standards, Chapter 21, Section 2, paragraph 9.2.3.3.

CPL Default: NoneFormat: Analog signalInput/Output: Output

is the Correction for the effect of Pressure on Liquid . This value issupplied for use in the Quantity Transaction Record (QTR) describedin the American Petroleum Institute - Manual of Petroleum Measure-ment Standards, Chapter 21, Section 2, paragraph 9.2.4.4.



CCF Default: NoneFormat: Analog signalInput/Output: Output

calculates the Combined Correction Factor for the liquid (i.e.CCF=MF(orCMF)*CTL*CPL).

RHOOTHER Default: NoneFormat: Analog signalInput/Output: Output

calculates �other=�BASE_DENS*CTL*CPL. If LIQUIDTYPE is LPG, thenunits are gm/liter. Units will be consistent with the BASE_DENSterminal units.

GSV Default: NoneFormat: Analog signalInput/Output: Output

calculates the Gross Standard Volume (i.e. GSV=IV*CCF). Units arethose associated with the product of CURMETERVAL and IVMULTI.

CSW Default: NoneFormat: Analog signalInput/Output: Output

calculates the Fiscal Correction for sediment and water (S&W). Thiscalculation is: [1 - (%S&W / 100) ].


Page GSV-8


NSV Default: NoneFormat: Analog signalInput/Output: Output

calculates the Net Standard Volume (i.e. NSV=GSV*CSW). Units arethose associated with the product of CURMETERVAL and IVMULTI.

SWV Default: NoneFormat: Analog signalInput/Output: Output

calculates the Sediment and Water value (i.e. SWV=GSV-NSV). Unitsare those associated with the product of CURMETERVAL andIVMULTI.


indicates the status of GSV Module operation. Negative status codestypically indicate configuration errors. Valid status codes include:

0 Calculation completed successfully.-1 Dynamic Module Control Block (MCB) not allocated. This

is an internal firmware error.-2 Percent sand and water out of bounds.-3 Calculation has not been initialized.-4 Fluid is not entirely in a liquid state.-5 Invalid fluid type selected on LIQUIDTYPE terminal.-6 Negative volume computed.-7 INIT value is not a logical.-8 Division by zero.-9 Incorrect UNITS selected.

-10 CTL calculation to base conditions of 15 degrees Celsius isnot supported.



-24 Bad density conversion.-40 LIQUIDTYPE terminal unwired.-41 LIQUIDVALID terminal unwired.-42 BASE_DENS terminal unwired.-45 FLOW_TEMP terminal unwired.-46 FLOW_PRESS terminal unwired.-47 EQVAPRPRESS terminal unwired.-50 CURMETERVAL terminal unwired.-53 INIT terminal unwired.

❏ Module Operation

Before using this module, please review the 'Liquid MeasurementGuidelines' section, later in this manual.

The GSV Module, as well as the modules providing its inputs e.g.ANIN, must be placed in an ACCOL task with a task rate of fiveseconds, or less, to ensure that inputs are updated frequently enoughfor valid calculations.

The GSV Module requires that the CURMETERVAL terminal changeby at least one unit for each module execution, or else GSV and NSVvalues will be reported as 0 for that execution cycle. The user must beaware of this when using calculations from this module.

Users must select the appropriate LIQUIDTYPE for the fluid they aremeasuring, and must provide values for the BASE_DENS,METERFACTOR, FLOW_TEMP, FLOW_PRESS, EQVAPRPRESS,and SEDANDWATER terminals.

If you are using a temperature compensated meter, set TCMUSED toON, and the temperature correction factor CTL will be set to 1 (i.e. notemperature correction).

If you are using a pressure compensated meter, set PCMUSED to ON,and the pressure correction factor CPL will be set to 1 (i.e. no pressure


Page GSV-10


correction).

The fluid must be entirely in a liquid state. (For LPG, this can bedetermined using the COMPLIQSTATE terminal of the EVP Module.)

During no-flow or 'not totally a liquid' conditions, input variables maycontinue to be sampled and displayed for monitoring purposes, butthey do not have an effect on averages used in volume calculations.

To start GSV module calculations, ACCOL logic must turn ON theINIT signal. GSV calculations require at least two module executionsfor a valid result.

❏ Module EquationsUnless otherwise noted, GSV Module equations are based on stan-dards which include the American Petroleum Institute - Manual ofPetroleum Measurement Standards, Chapter 21, Section 2.

GSV Calculation:

The GSV Module calculates the Gross Standard Volume (GSV), for agiven sampling period as follows:

GSV=IVm*CTL*CPL*MF

where:

IVm is the Indicated Volume on the meter.

CTL is the Correction for the effect of Tem-perature on liquid



CPL is the Correction for the effect of Pressureon liquid

MF is the Meter Factor developed at meterproving time.

The product of CTL and CPL, for use in the equation rf =rb*CTL*CPL, may be obtained at the CCF terminal by setting both theMETERFACTOR and LIQUIDVALID terminals to 1.

CTL Calculation For LPG Liquids:

CTL is calculated using the equations and implementation proceduresin the Gas Processor's Association (GPA) Technical Publication TP-25,Temperature Correction for the Volume of Light Hydrocarbons Tables24E and 23E, September, 1998.

CPL Correlation For LPG Liquids:

(from API Manual of Petroleum Measurement Standards, Chapter11.2.2.4)

CPL will be calculated from the following equation, which is valid for aRelative Density(60 0F/60 0F) range of 0.350-0.637, with a meteringtemperature range of -50.0 0F to 140 0F.

��

��

��

��

��

��

��


Page GSV-12


��

��

��

��

��

��

�

��

��

��

��

�� !��"��#��$��%��&��'�� !�$��

�� (�� $��

�� !��!� ��

�)�*�� +��,-./0�1�-)��2��.33,40*1�.)��)��

��*.*+�401�.)��2+�/4+,,/�1�3)��)��

�*�0.,0.0401*23�+0**--+1�/)��)��

�+�33-04,41�3)��4)�,2*�*4-,./4/1*)��)��

�*�*.��*�./1*)��)�2*�**30..+01*)��20��4��,0�*1*)�

)�*�� -�*4.3--31��*)��2+�+��+-3/1�-)��)��

2*�***//4/,1*)��*�**+*,*�-1*)��

�� "��$��-*�5�-*�5�



16� � �� 6��

�(7��$�� $�� (�� !��

��

BLANK PAGE

HCBOHost Check Before Operate

ACCOL II Reference ManualPage HCBO-1

qÿÿÿ EquipmentDPC-3330, DPC-3335, or RTU-3310 controller

CBO I/O Board (this item plugs into any I/O slot in the above units.)

CBO Relay Module

q Module OperationThe Host Check Before Operate (HCBO) module is a non-executingmodule, used to define certain parameters related to the CBO board whenit is controlled via external host messaging software, such as that avail-able with the Honeywell CLM system. HCBO module status information ispassed back to the external messaging software. The HCBO moduleshould be placed in Task 0 of the ACCOL load.

Each field output on the CBO board has a numbered pair of moduleterminals, TRACK and PULSE.

NOTE: This module is not supported by Enterprise Server.

DEVICEINITIAL

DELAYTIMEOUT

ERROR_CLEAR

RESTORE

POWERFAIL

TRACK [1..8]

PULSE [1..8]

HCBO

HCBO



qÿÿÿ Module Terminals

DEVICE Default: 0Format: ConstantInput/Output: Input

is the slot number in the 33XX controller into which the CBO board isinstalled. See 'Process I/O' later in this manual for information on howmany boards a particular 33XX controller can hold.


is the number of the CBO board field wiring terminal which will be as-signed to the first pair of TRACK/PULSE module terminals. All subse-quent TRACK/PULSE module terminal pairs will be sequenced from thisinitial number. For example, if 2 were the initial number, the first pair ofterminals would correspond to field wiring terminal DO2 of the CBOboard and the second pair of terminals would correspond to field wiringterminal DO3. NOTE: Only one (1) HCBO Module is allowed to access aparticular CBO board, therefore, if the INITIAL terminal value is greaterthan 1, any lower-numbered I/O points on the board will be inaccessible.

DELAY Default: 25 msFormat: Analog Signal or ConstantInput/Output: Input

is an analog signal or constant which, if wired, provides a time delay inmilliseconds. This time delay allows the relays to settle after an operationbefore the Operate-Check is performed. The DELAY value may range



from 0 to 65,535 milliseconds. If the terminal is unwired or out of thisrange, the default of 25 milliseconds will be used.

TIMEOUT Default: 60 secondsFormat: Analog Signal or constantInput/Output: Input

is an analog signal used to specify the maximum time, in seconds, to beallowed for receipt of the Operate message following successful completionof a Select-Check operation. If the Operate message is not received withinthis time, the previous Select operation is cancelled. Subsequent receipt ofthe Operate message results in an error status being returned to the hostsystem. The valid range for this terminal is 1 to 65,535.

ERROR_CLEAR Default: OFFFormat: Logical SignalInput/Output: Input and Output

is a logical signal used to clear errors on the CBO board. It is read beforeeach valid Select-Check operation is performed; if the signal is ON, everyerror status for the CBO board is cleared, the signal is automatically setOFF, and the Select-Check operation proceeds. If the signal is OFF, anycurrent error status at the CBO board may prevent the Select-Checkoperation.

RESTORE Default: OFFFormat: Logical SignalInput/Output: Input

is a logical signal used, in conjunction with the POWERFAIL terminal, tocontrol restoration of outputs to their previous state following a power



failure. If RESTORE is ON when power is restored, and the power-downtime does not exceed the time specified on the POWERFAIL terminal, theoutputs on the board for which TRACK signals are wired will be restoredto the states they had before the power failure occurred. If pulsed outputswere ON when the power failure occurred, upon restoration, they will beturned ON for a period of time equal to however much of the pulse lengthhad not elapsed at the moment of the power failure. For either pulsed orlatched outputs, If RESTORE is OFF, no restoration action is taken.

POWERFAIL Default: 0.0 secondsFormat: Analog Signal or constantInput/Output: Input

is an analog signal which specifies, in seconds, the maximum duration of apower failure for which restoration of outputs should be attempted. Thisvalue can range from 0 to 65,535 seconds. If power is restored within thetime specified, and the RESTORE terminal is ON, the outputs on theboard for which TRACK signals are wired will be restored to the statesthey had before the power failure occurred. If the power-down timeexceeds the period specified, no restoration action is taken.


is a logical signal which tracks the state of the CBO DO field wiringterminal. There are 8 TRACK signals, one for each field output on theboard. The TRACK signal is updated following a valid CBO cycle. See thesection below on 'Relationship of Pulse to TRACK Signal.'



PULSE Default: 0.0 (latched output)Format: Analog SignalInput/Output: Input

is an analog signal which determines if the output at the CBO DO fieldwiring terminal is latched or pulsed, and, if pulsed, it specifies the pulselength in seconds. There are 8 PULSE terminals, one for each field outputon the board. If the terminal is unwired, or if the signal value is 0.0 oroutside of the valid pulse range, the output will be latched. It will retainthe state indicated in the HCBO message until it is changed either by asubsequent HCBO message, or via LCBO module control.

For a pulsed output, the signal specifies the ON time of the pulse inseconds. A value of 0.1 specifies the minimum pulse of 1/10 of a second, or100 milliseconds. The maximum pulse is 1310.7 seconds. A pulsed outputis set ON, then automatically set OFF when the pulse period expires.

Note: The pulse length only applies to the ON state. A host message to seta point (or points) on the CBO board OFF, defaults to latched.

A pulsed output can be cancelled by a CANCEL message from the hostsoftware.

Note: A pulsed output originated by the host software can be affected onlyby a CANCEL message from the host, or by LCBO module activity for adifferent point which results in a reset of the board.

o Relationship of PULSE and TRACK Signals

The TRACK signal(s) are set following a successsful Operate-Check (at theend of the relay delay period) for a latched output, or for both the leading



edge and trailing edge of a pulsed output. Because of the relay delay time,the state at the TRACK signal will trail the actual field output by a timewhich is within the relay delay period. A pulsed output is illustrated in thefollowing figure.

Field Output

TRACK

PULSE

CBO board

Relay responds, actual field output turned ON

’Operate’ Command to activate point on CBO board, timing of pulse begins

’Operate-Check’ performed; if successful, TRACK turned ON

Pulse timer expires, ’Operate’ command

Relay responds, field

’Operate-Check’ performed;

2

1

3

4

5

6

DELAY period

Period between ’Operate’ and ’Operate-check’(as defined on DELAY terminal). Relay responds at somemoment within this delay period

TRACK turned OFF

to turn off point on board issued

output turned OFF

if check successful,

relay

HILOLIMITERHigh Low Limiter Module


Page HILOLIMITER-1

The HILOLIMIT Module compares the signal on the INPUT terminalagainst the high and low limits defined on the HIGH_LIMIT andLOW_LIMIT terminals. The signals on the OUTPUT_1, OUTPUT_2,and OUTPUT_3 terminals are then set according to the outcome ofthe comparisons.


is the input signal which is compared against the high and low limits.

HIGH_LIMIT

is the high limit which is compared against the value of the INPUTterminal for the high limit test.

If HIGH_LIMIT is less than LOW_LIMIT, then error code -114 isrecorded in the #ERARRAY and the OUTPUT terminals are notchanged.


Default: None, entry is optional; when thisterminal is not wired, high limittesting will not be done.


INPUTHIGH_LIMITLOW_LIMIT

OUTPUT_1OUTPUT_2OUTPUT_3

HILOLIMITER


Page HILOLIMITER-2


LOW_LIMIT

is the low limit value which is compared to the value of the INPUTterminal for the low limit test.

If LOW_LIMIT is greater than HIGH_LIMIT, then the error code -114(minus 114) is recorded in the #ERARRAY and the OUTPUT termi-nals are not changed.

OUTPUT_1

is set equal to the high limit when INPUT exceeds HIGH_LIMIT or itis set to LOW_LIMIT when INPUT is less than the low limit. Whenthe value of INPUT is between the high and low limits, OUTPUT_1assumes the value on the INPUT terminal.

OUTPUT_2

is set ON when INPUT exceeds HIGH_LIMIT. Otherwise, this signalis set to OFF.

OUTPUT_3

is set ON when INPUT is less than LOW_LIMIT. If not, it is set OFF.

Default: None, entry is optional; when thisterminal is not wired, low limittesting will not be done.



Default: None, entry is optionalFormat: Logical signalInput/Output: Output




Page HILOLIMITER-3

Module Operation

The following tests are performed by the HILOLIMITER Module.

If INPUT is greater than HIGH_LIMIT, then OUTPUT_1 is set toHIGH_LIM, OUTPUT_2 is set TRUE, and OUTPUT_3 is set FALSE.

If INPUT is less than LOW_LIMIT, then OUTPUT_1 is set toLOW_LIMIT, OUTPUT_2 is set FALSE, and OUTPUT_3 is set TRUE.

If neither of the these cases is true, then OUTPUT_1 is set equal toINPUT, and OUTPUT_2 and OUTPUT_3 are set FALSE.

outcome of OUTPUT_1 OUTPUT_2 OUTPUT_3comparison: equals set to: set to:

INPUT > high limit high limit true false

INPUT < low limit low limit false true

INPUT is betweenhigh and low limits INPUT false false

BLANK PAGE


Page HILOSELECT-1

HILOSELECTHigh Low Select Module

This module selects the largest and smallest values from a list ofsignals. These signals can be contained in the signal list named on theINLIST terminal or each signal can be named on an INPUT terminal.

The highest value in the list is written on the OUTPUT_1 terminaland the smallest value is written on the OUTPUT_2 terminal.

SELECT_1 and SELECT_2 indicate which terminal from the list wasselected as the largest and smallest. If the SELECT signals areanalog, their value will range from 1 to n, where there are n elementsin the signal list or n number of INPUT terminals. If the SELECTsignals are logical, then they are FALSE if the first element in the listis selected, otherwise the value is TRUE.

Module Terminals

OUTPUT_1

is equal to the highest value found in the list of signals

OUTPUT_2

is equal to the lowest value in the list of signals



INLISTINPUT nSELECT_1

OUTPUT_1

OUTPUT_2SELECT_2

HILOSELECT


Page HILOSELECT-2


Default: None, entry is optionalFormat: Analog or logical signalInput/Output: Output


SELECT_1

is the position of the highest value in the specified list of signals whenthe signal on this terminal is an analog signal. If the signal is logical,then the signal is set FALSE if the first element in the list is thehighest value. Otherwise, it is set TRUE.

SELECT_2

is the position of the lowest value in the specified list of signals whenthis signal is an analog signal. If the signal is logical, then the signal isset FALSE if the lowest value is the first element in the list. Other-wise, it is set TRUE.

INLIST

is the signal list that contains the input signals. Only analog signalsin the list are considered in the module's algorithm. Logical and stringsignals are ignored.

INPUT n

are the input signals for this module. From the entries on all theINPUT terminals, the highest and lowest values are chosen and

Default: None, entry is optional; when thisterminal is unwired, inputs aretaken from the INPUT terminals


Default: None, entry is optionalFormat: Analog signal or constantInput/Output: Input


Page HILOSELECT-3


written to the OUTPUT terminals. Unused positions are ignored. Upto 255 input signals are allowed.

Error codes

The following error codes may be found in the #ERARRAY after themodule executes.

-111 Signal list named on the INLIST terminal does not exist-114 Fatal error; No analog input signals were found for this module.

BLANK PAGE


Page HSANIN-1

HSANINHigh Speed Analog Input Module

The HSANIN Module is used in data acquisition applications whereanalog signals must be read at a high rate. The HSANIN Module isuseful for batch mode data acquisition or discontinuous processcontrol. Typical applications include gas pipeline compressor engineanalysis, on-line engine diagnostics, and engine efficiency and torquecontrol.

Module Terminals

DEVICE

is the slot number in the 33XX controller where the HSAI board isinstalled. The number of available slots varies depending upon whichtype of controller is used. For allowable entries see the Process I/Osection in this manual.


ZEROSPAN

DEVICEINITIAL

RATEDONE

STATUS

STATUS_1

ARRAYROW

RESOLUTIONFREQUENCYINDEX

STROBE

HSANIN

HSANIN


Page HSANIN-2


Default: NoneFormat: ConstantInput/Output: Input

INITIAL

is a number from 1 to 8 which selects which one of the four inputchannels on the HSAI board this module will use and also indicatesthe conversions per revolution supported by the HSAI board hard-ware. A value of 1 to 4 selects the specified channel and indicates thatthe hardware does 360 point conversions per revolution. A value of 5to 8 selects channel 1 to 4, respectively, and indicates that the hard-ware does 1440 point conversions per revolution. Values 1 to 4 cannotbe intermixed with values 5 to 8 on modules for the same I/O slot(DEVICE); the conversions per revolution is the same for all fourchannels of an HSAI board.

Example:

If the degree input to the I/O board generates 360 points per revolu-tion then the INITIAL value terminal should be set at 1 to 4. If thedegree input to the I/O board generates 1440 points per revolutionthen the INITIAL terminal value should be set at 5 to 8.

If a value of 5 to 8 is used for a board having an input of 360 pointsper revolution a runtime underrange error (status code = -253) willoccur, and if a value of 1 to 4 is used for an input of 1440 points perrevolution a runtime overrange error (status code = -255) will occur.

(Experienced ACCOL users please note: Although ANIN and otherI/Omodules also have INITIAL terminals, INITIAL is defined differentlyfor this module.)

ARRAY

is the number of a read/write analog array. Data from temporarystorage on the HSAI Board is passed to this array when the moduleexecutes.

Default: NoneFormat: Analog signal or constantInput/Output: Input


Page HSANIN-3


If INITIAL is specified as 1 to 4 and you want to collect all 360 datapoints for each cycle of the process variable, make an array with 360columns. If INITIAL is specified as 5 to 8 and you want to collect all1440 data points for each cycle of the process variable, make an arraywith 1440 columns.The array can contain any number of rows, de-pending on the amount of data you wish to store.

The values collected in this array are the output of the module. Whenthe SPAN and ZERO values are specified, the units of the arrayelements are the same as the units specified by the SPAN and ZEROterminals. If SPAN and ZERO are not specified, the value of the datawill range from 0 to 1, where 0.0 represents 0% of the input rangeand 1.0 represents 100% of the input range.

ROW

is the row number in the array that accumulates data from the HSAIBoard.

If the value of the ROW terminal doesn’t change, new data will over-write older data in the array. If you want to save several generationsof data, create an array with several rows and increment the ROWterminal each time the module executes.

ZERO

is the 0% value of the analog data points. For example, if the inputranges from 0 to 1000 PSIG, ZERO must be set to 0. If the inputranges from 50 to 150 PSIG, ZERO must be set to 50.




Page HSANIN-4


SPAN

is the total span of the input range for the analog data points. Forexample, if the input ranges from 0 to 1000 PSIG, SPAN must be 1000(1000 minus 0). If the input range is 50 to 150 PSIG, SPAN must beset to 100 (150 minus 50).

STROBE

is a logical signal which when TRUE enables execution of theHSANIN Module.

STROBE can be used to cycle HSANIN Modules in the same taskby sequentially turning the STROBE terminals ON and OFF for eachmodule. For example, as the first module begins to execute, turn itsSTROBE terminal OFF. When DONE in the first module is ON,(because data transfer is complete), turn the STROBE terminal in thenext HSANIN Module to ON (so it will be the next HSANIN Module toexecute).

Before an HSANIN board is removed from a running unit, set theSTROBE signal(s) to OFF, and verify that no HSANIN modules areactive by checking that their STATUS signals are not equal to 1.

FREQUENCY Default: 1 (no averaging) Format: Analog signal or constant Input/Output: Input

is the number of data samples at each point in the cycle to be aver-aged. Acceptable entries range from 1 to 256. (See also 'SelectivelyCollecting Data' later in this section.)


Default: None, entry requiredFormat: Logical signalInput/Output: Input


Page HSANIN-5


INDEX

is a starting offset. Units for this terminal are in data points perrevolution. When INDEX is 1, data is transferred to the HSANINModule array beginning with the first data point. If, for example,INDEX is set to 30, the 30th data point is the first data point to betransferred to the data array. For INITIAL terminal values of 1 to 4,acceptable INDEX terminal values are from 1 to 360. For INITIALterminal values of 5 to 8, acceptable INDEX terminal values are from1 to 1440.

RESOLUTION

is a filter in the event that you don’t want to transfer all data pointsfrom the HSAI Board storage area to the module data array. WhenRESOLUTION equals some number N, every Nth element of the 360(or 1440) data points will be sent to the array. The default is 1. (See'Selectively Collecting Data' later in this section.). For INITIALterminal values of 1 to 4, acceptable values for the RESOLUTIONterminal are from 1 to 360. For INITIAL terminal values of 5 to 8,acceptable values for the RESOLUTION terminal are from 1 to 1440.

STATUS

indicates the status of the HSANIN Module. Normally, when themodule begins to execute, STATUS assumes a value of 1. If no errorsoccur and data is successfully transferred to the data array, STATUSwill return to 0 (See DONE terminal description for additional info-rmation).

The STATUS signal may also assume one of the following codes.For all negative values array data is invalid.





Page HSANIN-6


2 Board in use by another HSANIN module, tested at modulelevel.

1 HSANIN module has executed and HSAI Board has begun tocapture data.

0 HSANIN Module idle.-1 Time out failure (no data or incomplete data from the HSAI

board).-4 RESOLUTION less than 1 or greater than 360 (or 1440).-5 INDEX less than 1 or greater than 360 (or 1440).-6 FREQUENCY less than 1 or greater than 256.-7 ROW less than 1 or greater than number of rows in array;

number of columns in array less than ((360-INDEX)/RESOLUTION)+1 or ((1440-INDEX)/RESOLUTION)+1.

-8 Array signal unwired or array not Read/Write type.-9 Board active by another HSANIN Module, tested at task level.

-10 Board active w/o HSANIN Module request.-11 HSAI Board restarted because of board failure.-12 Sequence failure detected by HSA task.-13 MCB address in RW IOB area incorrect. -21 First Block Transfer failed for 360 or 1440 point. -22 Second Block Transfer failed for 360 or 1440 point. -23 Third Block Transfer failed for 1440 point. -24 Fourth Block Transfer failed for 1440 point. -25 Fifth Block Transfer failed for 1440 point. -26 Sixth Block Transfer failed for 1440 point. -27 Seventh Block Transfer failed for 1440 point. -28 Eighth Block Transfer failed for 1440 point.-250 Interrupt circuitry not active during block digitization.-251 Interrupt signal not cleared.-252 Channel selected > 8 for INITIAL terminal value.-253 Less than 360 (or 1440) pulses detected during HSA block

digitization (underrange error).-254 TDC pulses not occurring; engine stopped.-255 More than 360 (or 1440)1 pulses detected during HSA block

digitization (overrange error).

1. 360 pulses for INITIAL terminal value set at 1 to 4.1440 pulses for INITIAL terminal value set at 5 to 8.


Page HSANIN-7


DONE

When the module is executing, this signal is set to OFF or FALSEand the STATUS signal is set to 1. When the module completesexecution, or terminates due to an error, the DONE signal is turnedON or TRUE and the STATUS signal is updated to indicate eithersuccessful completion (0) or an error condition.

Before using the data from the data array, you may want to check thatthe DONE signal is 1 and STATUS is 0. In this way you can ensurethat the module executed without error and data transfer is finished.

RATE

is the engine speed in units of pulses per minute. For engine applica-tions, this terminal represents revolutions per minute.

STATUS_1

is the number of data points which are marked as questionable data inthe data array. Data samples are marked questionable when the HSAIBoard detects an out-of-range condition.





Page HSANIN-8


Module Operation

The HSANIN Module receives its input from the HSAI Board. Thisboard accepts four analog signals from the process and two digitalsignals.

When the HSANIN Module executes, the HSAI Board begins tocapture data from one of the analog inputs from the process and storesit temporarily in on-board memory. When data collection is complete,the data is transferred to a data array. The array elements of the dataarray are the output of the HSANIN module. When SPAN and ZEROvalues are specified, the units of the array elements are the same asthe units specified by the ZERO and SPAN terminals. If the ZEROand SPAN terminals are not specified, the array elements will havevalues ranging from 0 to 1, where 0.0 represents 0% of the input rangeand 1.0 represents 100% of the input range.

The board will also calculate the average of the data samples overseveral revolutions or cycles at the request of the HSANIN Modulebefore data is transferred to the data array (See FREQUENCYterminal description in the Module Terminal section).

The HSAI Board reads two digital signals from the process. They areused to synchronize input sampling. One digital signal indicates whenthe engine is at top dead center and is used to begin the input cycle.(This signal comes into the board through the terminal block markedT) The other signal, marked D, is a sample sync input. Analog inputsamples will be taken in sync with this signal, either 360 times or1440 times per revolution.

When the HSANIN Module executes, the HSAI Board begins tocapture data for the channel specified on the INITIAL terminal. (The


Page HSANIN-9


STROBE terminal must be ON before the module will execute.) Whendata collection is complete, data is passed from temporary storage onthe board into an array specified by the ARRAY terminal. The data isconverted to engineering units using SPAN and ZERO, if specified,otherwise the data represents percent of scale readings directly fromthe board. Data is sent to the row specified by the ROW terminal.Each piece of data is written to subsequent columns in that same row.Data in the array is then available to other modules for furthercalculations.

The module also provides engine speed on the RATE terminal.

Each HSAI Board has four analog input channels. For each analoginput channel, the HSAI Board reads 360 or 1440 points. This read-ing is based on the INITIAL terminal value and the input datasamples for each revolution of the compressor or engine.

Each HSANIN Module indicates which channel it will use by theINITIAL terminal. Up to four HSANIN Modules can access one HSAIBoard, each module using a different channel. Since only one modulecan use the board at one time, you must use caution when specifyingthe frequency of each HSANIN Module and task rate. If one moduletries to access the board often enough, the other modules which usethe same board may not be able to access their channels.

For the HSANIN Module to operate correctly, it must be placed in anACCOL task with a priority of 31 or less.

Selectively Collecting Data

Data is collected by the HSAI Board either 360 or 1440 times for eachrevolution. By using the INITIAL, INDEX and RESOLUTION termi-nals, you can choose to pass on only some of that data to the modulearray.


Page HSANIN-10


The INDEX terminal acts as a starting offset. For each revolution, nodata values will be sent between top dead center and the point speci-fied by INDEX. Suppose INDEX is set to 30. Each sample of data from30 to 360 (or 1440) is sent for each rotation. This means 330 (or 1410)data points will be sent for each rotation.

The RESOLUTION terminal acts as a filter. It reduces the number ofsamples. When RESOLUTION is set to some number n, every nthdata value will be transferred to the module array. If n = 2 (andINDEX is set to the default) every other value will be transferred.Since there are a total of 360 (or 1440) sampling points in each cycle,180 (or 720) values are sent to the module array for each cycle. WhenRESOLUTION is 1, every data sample is sent to the data array.

As a last example, suppose INITIAL is 1 to 4 (360 samples per revol-ution), INDEX is 180 and RESOLUTION is 10. Only the data collectedat the last half of the revolution between 180 and 360 degrees will besent to the module array. Of these data points, every tenth value willsent. For example, data for 1800, 1900, 2000, and 2100 until 3600. In all,19 values are sent to the data array.

The HSAI Board will also calculate averages on the input data overseveral cycles of the process variable. Running averages are calculatedfor each of the 360 (or 1440) points in the cycle.

Averaging is specified on the FREQUENCY terminal of the HSANINModule. Suppose this terminal is set to 5. Five cycles of data sampleswill be collected at the HSAI board before data is transferred to thedata array. Averaging is done separately at each sampling point inthe cycle. Specifically, five data values, each sampled at the firstsampling point, are averaged2 together. The five data points that weremeasured at the next sampling point are averaged3. In the end, therewill be up to 360 data values (INITIAL = 1 to 4) or up to 1440 datavalues (INITIAL = 5 to 8). Each value is an average for one spot in

2 and 3. The average calculated is the running average.


Page HSANIN-11


the cycle. Up to 256 cycles can be averaged. When the board process-ing completes, only the results of the averaging are passed to thearray, not all the samples. The number of averaged sampling pointsstored in the array is affected by INDEX and RESOLUTION terminalvalues, as previously explained.

BLANK PAGE

Honeywell Smartline Transmitter Interface

HWSTI

ACCOL II Reference ManualPage HWSTI-1

❑ Equipment

Honeywell Smartline Transmitters:

• ST3000 for differential, gauge, and absolute pressuremeasurements.

• STT 3000 for temperature measurements

• MagneW 3000 for flow measurements

Honeywell Smart Field Communicator (SFC):

• HWSTI Process I/O Module

❑ References• PM/Smartline Transmitter Integration Manual PM12-310

NOTE: Familiarize yourself with the SmartLine Transmitterbefore attempting to perform any of the procedures describedin this manual.

❑ Module OperationThe HWSTI (Honeywell Smartline Transmitter Interface) moduleprovides an interface between a 3310/3330/3335 remote processcontroller and a Honeywell Smartline Transmitter via an HWSTIprocess I/O board. It allows configuration parameters to be down-loaded and uploaded to and from the transmitter and detects andreports any mismatch between the transmitter’s parameter valuesand the module’s parameter values. It also provides conversion of theprocess variable to engineering units and optionally provides thesecondary variable. Each HWSTI module supports a single transmit-

HWSTI

HWSTIHoneywell Smartline Transmitter Interface


ter (channel) on a particular HWSTI process I/O board.A command terminal is used to set the operating mode of the moduleand to issue commands to the transmitter. A status terminal is used toindicate the current state of the module and to indicate completion oftransmitter commands.

A bad process variable (PV) value is represented by a Not a Number(NAN) value. Any time NAN is stored as a signal’s value, the signal’sQuestionable Data bit is also set.

The HWSTI process I/O board is not used for alarm detection. Alarmdetection and reporting is provided using the ALARM SYSTEM bywiring alarm signals to the module’s terminals. The HWSTI process I/O board is not used for PV Source selection. This capability is pro-vided by using the Control Inhibit status for the signal representingthe PV parameter.

The HWSTI module is used to configure the Smartline transmitterand support the following commands to the transmitter:

• Upload the transmitter data base to the 3310/3330/3335remote process controller.

- The following transmitter parameters will be uploaded:

STISWVER software revision numberSERIALNO PROM identification numberURL and LRL Upper/Lower Range LimitsSENSRTYP Sensor typeSTITAG Transmitter identificationDECONF DE Configuration ModeURV and LRV Upper/Lower Range ValuesPVCHAR PV Characterization OptionDAMPING DampingPIUOTDCF Open T/C DetectFREQ6050 Power Filter


HWSTI


CJTACT Internal Cold Junction TemperatureS1(PARTIAL) Scratch Pad and transmitter status

• Download the transmitter data base from the 3310/3330/3335remote process controller

- The following transmitter parameters will be downloaded:

STITAG Transmitter identificationDECONF DE Configuration ModeURV and LRV Upper/Lower Range ValuesPVCHAR PV Characterization OptionDAMPING DampingPIUOTDCF Open T/C DetectFREQ6050 Power FilterCJTACT Internal Cold Junction TemperatureURL Upper Range Limit

• Set the Lower Range Value to the current value of input

• Set the Upper Range Value to the current value of input

• Correct the Lower Range Value

• Correct the Upper Range Value

• Correct the zero point

• Set all input calibration parameters to their factorydefault values



The HWSTI module, using the 6-byte DE communications mode(DECONF terminal value = '3' or '4'), will perform data base mis-match detection. The following parameters are checked for data basemismatches between the 3310/3330/3335 remote process controllerand the transmitter:

STITAG Transmitter identificationDECONF DE Configuration ModeURV and LRV Upper/Lower Range ValuesPVCHAR PV Characterization OptionDAMPING DampingPIUOTDCF Open T/C DetectFREQ6050 Power FilterCJTACT Internal Cold Junction TemperatureURL Upper Range LimitSENSRTYP Sensor Type

The PV processing consists of the:

• Base Engineering Units Conversion. Engineering unitsconversion is performed by the HWSTI module. It uses theconfigured signals LRV, URV, and STIEU to calculate engi-neering units for the transmitted PV which is between 0 and1 and proportional to percent of:

��

100%URV/URL STIEU

PV IN BASE ENGINEERINGUNITS

PV in %

LRV/URL 0%

Bargraph


HWSTI


• PV Characterization. This function is performed by thetransmitter in terms of linear or square-root characterization,and for temperature transmitters, thermocouple or RTDcharacterization.

• PV Filtering. PV filtering is performed by the transmitter.

• PV Source Selection. PV source selection will be controlledby the Control Enable/Manual Enable bits associated with thePV signal of the HWSTI module.

• Bad PV Processing. Bad PV processing will cause thequestionable bit to be set on the PV and an alarm will occur ifalarming is set up and enabled.

Bad PV processing can occur in the HWSTI module as theresult of the following:

- Transmitter failure

- Inconsistency in the transmitter data base parameters



❑ Module Terminals

DEVICECHANNEL

COMMANDPOWERFAIL

STIEUSENSRTYPDECONF

DAMPINGPVCHARCJTACT

PIUOTDCFSTITAG

FREQ6050URVLRVURL

Transmitter

DONESTATUSPVSECVARMISMATCHCFGSTATLRLSERIALNOSTISWVERSCRATCHPADXMITSTATCOMERRS

HWSTI

Module

DEVICE Default: 0 (NULL DEVICE)Format: ConstantInput/Output: Input

is the slot number in the card cage where the HWSTI process I/Oboard is installed. The entry for this terminal must be a number from1 to 12.

The slot number is verified with the Process I/O Menu (if you areusing AIC) or the *PROCESS-I/O section (if you are using ABC or theACCOL Workbench) to ensure that an HWSTI process I/O board isspecified for the slot. A value of '0' will generate a task run time errorand module status '32'. An error code of '-10' will be stored in the#ERARRAY, if defined.

NOTE: Other reasons for device error are no board in I/O slot; wrongboard type in slot; or incompatible version of HWSTI board in I/O slot.


HWSTI


CHANNEL Default: 0*Format: ConstantInput/Output: Input

is the channel number on the HWSTI process I/O board for the trans-mitter to be used by this module. The entry for this terminal must bea number from 1 to 8. The combination of values for DEVICE andCHANNEL must be unique for each HWSTI module. The defaultvalue is 0, which will generate a task runtime error and module status'32'.* 0 generates error code '-120' in #ERARRAY.

COMMAND Default: None - Signal RequiredFormat: Analog Signal or ConstantInput/Output: Input

is an analog signal used to specify the module’s operating mode and toissue commands to the transmitter. If left unwired, or invalid, errorstatus '28' is reported on the STATUS terminal and PV and SV are setto NAN and the Questionable Data bit is set. The analog value is aunique code representing a particular mode or command. The com-mand codes are as follows:

Code Mode / Command 0 Process mode 1 Download transmitter parameters 2 Upload transmitter parameters 3 Set the Lower Range value 4 Set the Upper Range value 5 Correct the Lower Range value 6 Correct the Upper Range value 7 Correct the zero point for the PV value 8 Set calibration parameters to default values 9 Configure mode

10 Process mode, Inhibit configuration signals 11 Configure mode, Enable configuration signals 99 Test mode, imaging transmitter data



Codes 0 and 10 are called Process mode. In Process mode, the PV andSECVAR terminal signal values are updated using the most recenttransmitter values. Also, the transmitter’s configuration parametervalues are checked for a mismatch with the module’s terminal values.This is the normal operating mode for the module. The SECVARterminal is updated only if the transmitter’s DECONF parameter hasa value of 2 or 4 and parameter mismatch occurs only if the module’sDECONF parameter has a value of 3 or 4. Refer to the MISMATCHterminal for a description of parameter mismatch.

Code 10 performs the same function as code 0 but also sets Manualand Control Inhibit status for the STEIU terminal and all terminalsignals corresponding to read/write configuration parameters. Thisprevents operator and ACCOL initiated changes to the configurationvalues.

Code 99 performs a test function which is equivalent to the Processmode combined with continuous Upload commands but the datapresented at the module’s terminal signals is the transmitter’s datawithout engineering unit conversions. The signals PV, SECVAR,SENSRTYP, DECONF, DAMPING, PVCHAR, CJTACT, PIUOTDCF,STITAG, FREQ6050, URV, LRV, URL, LRL, SERIALNO,STISWVER, SCRATCHPAD, and XMITSTAT are updated with thetransmitter’s data. The PV value is a fraction representing percent ofrange. The URV, LRV, URL, and LRL values represent thetransmitter’s base units.

Codes 9 and 11 are called Configure mode. In Configure mode, the PVand SECVAR terminal signal values are set to Not a Number (NAN)and Questionable Data status is set for both signals. This mode is usedto disable updates of the PV and SECVAR while changes are made toconfiguration parameter values. This mode also checks parametervalues for mismatch in order to indicate which parameters will beaffected by a Download or an Upload of the Honeywell SmartlineTransmitter.


HWSTI


Code 11 performs the same function as code 9 but also sets Manualand Control Enable status for the STEIU terminal and all terminalsignals corresponding to read/write configuration parameters. Thisallows operator and ACCOL initiated changes to the configurationvalues.

Codes 1 through 8 are transmitter commands. When a transmittercommand is specified, the PV and SECVAR terminal signal values areset to NAN and Questionable Data status is set for both signals. Themodule ignores changes to the COMMAND terminal value while acommand is in progress. At the completion of a command, the modulewill not issue the same command again until the module recognizes achange to the COMMAND value. If the same command is wanted, theCOMMAND value can be changed to Configure mode and then back tothe command value. Parameter values are checked for mismatch atthe completion of a command.

Some configuration parameters must be restricted to a range of valuesin order to ensure correct transmitter operation. If any configurationparameters are invalid, the signals representing the invalid param-eters will have Questionable Data status set and the CFGSTATterminal will show the invalid parameters. If a Download command isspecified while invalid parameters exist, the Download command willbe rejected and the STATUS terminal will indicate the rejection.

Certain transmitter parameters can be read and written. With theexception of SENSRTYP, the terminal signal values corresponding tothese parameters are sent to the transmitter when a Downloadcommand is issued. These signal values are set by the module at thecompletion of an Upload or other transmitter command (exceptDownload, or if TEST mode is active) to reflect the values contained inthe transmitter.



The following terminals are the read/write parameters:

SENSRTYPDECONFDAMPINGPVCHARCJTACTPIUOTDCFSTITAGFREQ6050LRVURVURL

Certain transmitter parameters are read only. The terminal signalvalues corresponding to these parameters are set by the modulewhenever a new data base is obtained from the transmitter. Themodule will ignore any changes to these signal values by othersources. The following terminals are the read only parameters:

LRLSERIALNOSTISWVERSCRATCHPADXMITSTAT

The STATUS terminal should be used to verify that the module hasacted on changes to the COMMAND terminal value in order to ensurecorrect operation. The COMMAND terminal value is seen by themodule only during periodic execution. Multiple changes that occurbetween module executions will not be recognized by the module. Onlythe most recent change will be seen by the module.

A hardware failure is assumed if a transmitter command does notcomplete within 16 minutes and there hasn't been a power failure.


HWSTI


DONE Default: NoneFormat: Logical SignalInput/Output: Output

is an optional logical signal that indicates completion of a transmittercommand. The signal value is set to False at the beginning of a com-mand and is set to True when the command completes. It is used onlywith COMMAND values of 1 through 8.


is an analog signal used to indicate the state of the module. Theanalog value is set to a unique code to indicate the operating mode,command status, and error conditions. The status codes are as follows:

Code Description 0 Process mode

1 Process mode with invalid and/ormismatched parameter(s)

2 Configure mode 3 Download rejected due to invalid parameters 4 Download command in progress 5 Download completed OK 6 Download failed 7 Upload command in progress 8 Upload completed OK 9 Upload failed 10 Set Lower Range command in progress 11 Set Lower Range completed OK 12 Set Lower Range failed 13 Set Upper Range command in progress 14 Set Upper Range completed OK 15 Set Upper Range failed



Code Description (continued) 16 Correct Lower Range command in progress 17 Correct Lower Range completed OK 18 Correct Lower Range failed 19 Correct Upper Range command in progress 20 Correct Upper Range completed OK 21 Correct Upper Range failed 22 Correct Zero Point command in progress 23 Correct Zero Point completed OK 24 Correct Zero Point failed 25 Set Calibration Defaults command in progress 26 Set Calibration Defaults completed OK 27 Set Calibration Defaults failed 28 Invalid COMMAND value 29 Command failed due to a power failure 30 Transmitter is not operating (PV timeout) 31 Interface (I/O board) hardware failure 32 Invalid DEVICE and/or CHANNEL specified 99 Test mode, imaging transmitter data

PV Default: NoneFormat: Analog SignalInput/Output: Output

is an analog signal representing in Process Mode, the most recentvalue of the transmitter’s Process Variable (PV) in engineering unitsas specified by the STIEU terminal. In Test Mode (COMMAND='99'),the value is a fraction representing a percent of the range.

The PV signal’s Questionable Data status is set when the transmitteris in the Output mode. Output mode indicates that an SFC has substi-tuted the PV value.


HWSTI


The PV signal value is set to NAN and the signal’s Questionable Datastatus is set for the following conditions:

- The module is not in Process or Test mode. (COMMAND valueis not 0, 10, or 99)

- One or more configuration parameters are invalid or mismatch

- The transmitter’s data base has not been received since systemstartup or power failure

- An SFC write was detected

- The transmitter is not operating (PV update timeout)

- A hardware failure was detected

A non-operating transmitter is assumed if a new PV value is notreceived from the transmitter within 1.25 seconds. This time limit isextended to 2.75 seconds for the first value received following systemstartup or a power failure. Communication errors with the transmit-ter may be the cause of a PV update timeout. Examining the value ofthe COMERRS signal is useful for isolating the cause of the fault.

STIEU Default: Transmitter's Base Eng. UnitsFormat: Analog SignalInput/Output: Input/Output

is an analog signal used to specify the Base Engineering Unit codewhich selects the units of measurement for the PV, LRL, LRV, URL,and URV terminal values. The analog value is a unique code repre-senting a particular unit of measurement.

Valid values for the STIEU terminal are based on the transmitter typespecified with the SENSRTYP terminal. If the STIEU value is invalidor not used, STIEU defaults to the transmitter’s base units and theSTIEU signal’s Questionable Data status is set.



If the STIEU value is invalid when a transmitter command completes(COMMAND code '1-8'), and SENSRTYP is valid, the STIEU signal isset to the code for the transmitter's base engineering units and theQuestionable Data status is cleared. The default Base EngineeringUnits based on transmitter type are listed below:

Transmitter Type Default Base Engineering UnitsPressure InH2O (Inches of water)Temperature Deg_C (Degrees Centigrade)Flow CM_Hr (Cubic meters per hour)

The Base Engineering Unit codes for a Pressure transmitter(SENSRTYP equals 8, 9, or 10) are listed below:

Code Base Engineering Units 0 InH2O (Inches of water) 1 MMHG (Millimeters of mercury) 2 PSI (Pounds per square inch) 3 KPA (Kilopascals) 4 MPA (Millipascals) 5 MBar (Millibars) 6 Bar (Bars) 7 G_SqCM (Grams per square centimeter) 8 KG_SqCM (Kilograms per square centimeter) 9 MMH2O (Millimeters of water) 10 InHG (Inches of mercury)

The Base Engineering Unit codes for a Temperature transmitter(SENSRTYP equals 11) are listed below:

Code Base Engineering Units11 Deg_C (Degrees Centigrade)12 Deg_F (Degrees Fahrenheit)13 Deg_K (Degrees Kelvin)14 Deg_R (Degrees Rankine)15 MV (Millivolts)16 V (Volts)17 Ohms (RTD Ohms)


HWSTI


The Base Engineering Unit codes for a Magnetic Flow transmitter(SENSRTYP equals 12) are as follows:

Code Base Engineering Units 18 CM_Hr (Cubic meters per hour) 19 Gal_Hr (Gallons per hour) 20 Lit_Hr (Liters per hour) 21 CC_Hr (Cubic centimeters per hour) 22 CM_Min (Cubic meters per minute) 23 Gal_Min (Gallons per minute) 24 Lit_Min (Liters per minute) 25 CC_Min (Cubic centimeters per minute) 26 CM_Day (Cubic meters per day) 27 Gal_Day (Gallons per day) 28 KGal_Day (Thousands of gallons per day) 29 Brl_Day (Barrels per day) 30 CM_Sec (Cubic meters per second)

SECVAR Default: NoneFormat: Analog SignalInput/Output: Output

is an optional analog signal representing the most recent value of thetransmitter’s Secondary Variable.

The signal value is updated in Process mode only if the transmitter isconfigured to send the Secondary Variable (SV). The transmitter’sDECONF parameter must have a value of 2 or 4 in order to send theSV.



The SECVAR signal value is set to NAN and the signal’s QuestionableData status is set for the following conditions:

- The module is not in Process or Test mode. (COMMANDvalue is not 0, 10, or 99)

- The transmitter is not configured to send the SecondaryVariable (DECONF value is not 2 or 4)

- One or more configuration parameters are invalid ormismatch

- The transmitter’s data base has not been received sincesystem startup or a power failure

- An SFC write was detected

- The transmitter is not operating (PV update timeout)

- A hardware failure was detected

MISMATCH Default: NoneFormat: Logical SignalInput/Output: Output

is an optional logical signal that indicates that at least one configura-tion parameter in the transmitter does not match the terminal signalvalue representing the parameter. The signal value is set to False ifno parameters mismatch and is set to True if a mismatch exists.Invalid configuration parameters are treated as an implicit mismatchsince it is not possible for the transmitter to have an invalid param-eter value.Mismatch detection occurs only if the DECONF terminal has a valueof 3 or 4. The transmitter’s DECONF parameter must also have avalue of 3 or 4 in order for the transmitter to broadcast its data base.A mismatch condition is assumed at system startup, after a power orhardware failure, after a PV update timeout, and when an SFC writeoccurs. This condition persists until a data base update is receivedfrom the transmitter or a Download or Upload command is issued.


HWSTI


After the transmitter’s data base has been obtained, all configurationparameters are compared for mismatch.

If the transmitter is not configured to broadcast its data base(DECONF value is 1 or 2), a Download or Upload command must beissued in order to clear an assumed mismatch condition.

Questionable Data status is set only for analog signals with a mis-match condition. This applies to the STIEU, SENSRTYP, DECONF,DAMPING, PVCHAR, URV, LRV, and URL signals.

The LRV, URV, and URL parameters may differ by as much as.02441406 percent without causing a mismatch.

CFGSTAT Default: NoneFormat: String SignalInput/Output: Output

is an optional string signal used to indicate which configurationparameters are invalid or mismatch. The signal value is set to a textstring listing the names of the parameters along with a fault typeindication. The text string for each parameter has the followingformat:

parameter_name=fault_codewhere: ‘parameter_name’ is the name of the parameter’s terminal.‘fault_code’ is a letter code indicating the type of fault (I indicates

Invalid and M indicates Mismatch).

Multiple parameters are separated by spaces. All invalid parametersare listed before mismatch parameters. This string signal may be ofany length. As many parameter fault indicators as possible are storedin the signal.

An assumed mismatch caused by system startup, a power or hardwarefailure, or a PV update timeout is indicated with the text string“No_XDB”. This special text string indicates that a data base has not



been received from the transmitter since occurrence of the event.An assumed mismatch caused by an SFC write is indicated with thetext string “SFC_Write”. This special text string indicates that a database update has not been received from the transmitter since an SFCwrite was detected.

The following example indicates an invalid DAMPING parameter andmismatched CJTACT and STITAG parameters:

� ��

SENSRTYP Default: None - Signal RequiredFormat: Analog SignalInput/Output: Input/Output

is an analog signal used to specify the Smartline Transmitter type.The analog value is a unique code representing a particular transmit-ter type.

This is a read/write configuration parameter and a read only transmit-ter parameter. Several configuration parameters are dependent on thetransmitter type and therefore the SENSRTYP terminal value mustbe valid in order to calculate the PV.

The transmitter type codes are listed below:

Code Transmitter Type 8 ST3000 differential pressure 9 ST3000 gauge pressure 10 ST3000 absolute pressure 11 STT3000 temperature 12 MagneW3000 magnetic flow


HWSTI


DECONF Default: None - Signal RequiredFormat: Analog SignalInput/Output: Input/Output

is an analog signal used to specify the Digitally Enhanced Configura-tion mode. The analog value is a unique code representing a particularconfiguration mode. This is a read/write transmitter parameter.The mode codes are listed below:

��Code DE Configuration Mode 1 Process Variable (PV) Only 2 PV and Secondary Variable (SV) 3 PV and transmitter data base 4 PV, SV, and transmitter data base

Codes '1' and '2' use the 4-byte DE mode, and codes '3' and '4' use the6-byte DE mode for communications with the transmitter.

DAMPING Default: NoneFormat: Analog SignalInput/Output: Input/Output

is an analog signal used to select the first order PV filtering option forthe transmitter. The analog value is a unique code representing aparticular filtering option. This is a read/write transmitter parameter.The damping constant selected is based on the DAMPING terminalvalue and the transmitter type specified with the SENSRTYP termi-nal. The damping constants based on the DAMPING value and trans-mitter type are shown in the table following:

Transmitter type:DAMPING Value Pressure Temperature Flow

0 0.0 0.0 0.01 0.16 0.3 0.52 0.32 0.7 1.03 0.48 1.5 2.0



Transmitter type:DAMPING Value Pressure Temperature Flow

4 1.0 3.1 3.05 2.0 6.3 4.06 4.0 12.7 5.07 8.0 25.5 10.08 16.0 51.1 50.09 32.0 102.3 100.0

PVCHAR Default: None - Signal RequiredFormat: Analog SignalInput/Output: Input/Output

is an analog signal used to specify the PV Characterization option.This is a read/write transmitter parameter.

Valid values for the PVCHAR terminal are based on the transmittertype specified with the SENSRTYP terminal.

The Characterization codes for a Pressure transmitter (SENSRTYPequals 8, 9, or 10) are as follows:

Code Characterization12 LINEAR_ValChar13 SQRROOT_ValChar (SPT DP Only)

The Characterization codes for a Temperature transmitter(SENSRTYP equals 11) are as follows:

Code Characterization 0 JTHERM_ValChar 1 KTHERM_ValChar 2 ETHERM_ValChar 3 TTHERM_ValChar 4 BTHERM_ValChar 5 STHERM_ValChar


HWSTI


6 RTHERM_ValChar 8 DINRTD_ValChar 9 JISRTD_ValChar 10 NICKLRTD_ValChar 12 LINEAR_ValChar 14 NTHERM_ValChar 15 PT200RTD_ValChar 16 PT500RTD_ValChar 17 CU10RTD_ValChar 18 CU25RTD_ValChar 19 RHRAD_ValChar 20 W5W26TC_ValChar 21 W3W25TC_ValChar 22 NINIMOTC_ValChar 23 RTDOHMS_ValChar

The Characterization code for a Magnetic Flow transmitter(SENSRTYP equals 12) is listed below:

Code Characterization 12 LINEAR_ValChar

CJTACT Default: None*Format: Logical SignalInput/Output: Input/Output

is a logical signal indicating if the transmitter’s internal cold junctionreference is used. A value of False indicates that an external referenceis used and a value of True indicates the internal reference is used.This is a read/write transmitter parameter.

* This terminal is used only for Temperature transmitters(SENSRTYP value is 11), and a signal is required for use with them.

Code Characterization (continued)



PIUOTDCF Default: None*Format: Logical SignalInput/Output: Input/Output

is a logical signal indicating if Open Thermocouple Detection is en-abled. A value of False indicates that open thermocouples are notdetected and a value of True indicates that open thermocouple condi-tions are detected. This is a read/write transmitter parameter.* This terminal is used only for Temperature transmitters(SENSRTYP value is 11) and a signal is required for use with them.

STITAG Default: None - Signal RequiredFormat: String SignalInput/Output: Input/Output

is a string signal representing the Tag Name used to identify a trans-mitter to the system. This is a read/write transmitter parameter. Thisstring signal must be at least 8 characters in length. If its value isshorter than 8 characters, the value is padded with spaces beforecomparing for a mismatch and before issuing a Download command. Ifthe value is longer than 8 characters, all characters past the eighthcharacter must be spaces.

FREQ6050 Default: None*Format: Logical SignalInput/Output: Input/Output

is a logical signal used to specify the line filter used. False indicates 60Hz and True indicates 50 Hz. This is a read/write transmitter param-eter.

* This terminal is used only for Temperature transmitters(SENSRTYP value is 11) and a signal is required for use with them.


HWSTI


URV Default: None - Signal RequiredFormat: Analog SignalInput/Output: Input/Output

is an analog signal representing the value of the upper end of theoperating range for the transmitter’s PV value. The value is in unitsspecified with the STIEU terminal. A value of NAN is invalid. This isa read/write transmitter parameter.

LRV Default: None - Signal RequiredFormat: Analog SignalInput/Output: Input/Output

is an analog signal representing the value of the lower end of theoperating range for the transmitter’s PV value. The value is in unitsspecified with the STIEU terminal. A value of NAN is invalid. This isa read/write transmitter parameter.

URL Default: None - Signal RequiredFormat: Analog SignalInput/Output: Input/Output

is an analog signal representing the Upper Range limit of the PV atthe transmitter. The value is in units specified with the STIEUterminal. A value of NAN is invalid. This is a read/write transmitterparameter.

LRL Default: NoneFormat: Analog SignalInput/Output: Output

is an optional analog signal representing the Lower Range limit of thePV at the transmitter. The value is in units specified with the STIEUterminal. This is a read only transmitter parameter.



SERIALNO Default: NoneFormat: String SignalInput/Output: Output

is an optional string signal representing the Serial Number of thetransmitter. The string signal should be 8 characters in length. This isa read only transmitter parameter.

STISWVER Default: NoneFormat: String SignalInput/Output: Output

is an optional string signal representing the Software Revision Levelof the transmitter. The string signal should be 8 characters in length.This is a read only transmitter parameter.

SCRATCHPAD Default: NoneFormat: String SignalInput/Output: Output

is an optional string signal representing the content of thetransmitter’s scratch pads. The string signal should be 32 charactersin length. This is a read only transmitter parameter.

XMITSTAT Default: NoneFormat: String SignalInput/Output: Output

is an optional string signal representing the transmitter’s detailedstatus. The string signal should be 64 characters in length. This is aread only transmitter parameter.


HWSTI


COMERRS Default: NoneFormat: Analog SignalInput/Output: Output

is an optional analog signal representing a count of transmittercommunication errors detected by the HWSTI process I/O board. Thecounter is maintained by the process I/O board and is modulo 256.The count of transmitter communication errors is reset to zero when apower failure occurs.

POWERFAIL Default: 0Format: Analog SignalInput/Output: Input

is an optional analog signal used to specify the maximum duration of apower failure that is to be ignored. The value is in units of seconds.Power failures with a duration of less than the time specified with thisterminal do not cause an assumed parameter mismatch condition.Refer to the MISMATCH terminal for a description of parametermismatch. Power failure durations are measured with a resolution of1 second.

BLANK PAGE

IF, ENDIFELSE, ELSEIF

IF, ENDIF, ELSE, and ELSEIF Commands


Page IF-1

In a simple IF to ENDIF loop, the module and statements between IFand ENDIF are executed if the condition specified in the IF statementis true. If the condition is false, control is passed out of the loop to thestatement below ENDIF.

SyntaxIF ( condition )..ENDIF

simple IF/ENDIF loop

ELSEIF and ELSE provide alternate instructions should the conditionin the IF statement be false.

If the condition in the IF statement is false and the condition in theELSEIF command is true, the statements between ELSEIF andENDIF are executed. (If the IF/ENDIF loop contains other ELSEIF orELSE statements, the statements that are executed lie betweenELSEIF and the first ELSE or ENDIF or next ELSEIF.

Syntax

IF (condition 1)..ELSEIF (condition 2)..ENDIF

ELSEIF is added to the IF/ENDIF loop

IF/ENDIF/ELSE/ELSEIF


Page IF-2

IF, ENDIFELSE, ELSEIFIF, ENDIF, ELSE, and ELSEIF Commands

When the IF/ENDIF loop contains an ELSE statement, the statementsbetween ELSE and ENDIF are executed when both the conditions inthe IF and ELSEIF statements are false.

SyntaxIF (condition 1)..ELSEIF (condition 2)..ELSE..ENDIF

Loop includes IF, ELSEIF, ELSE, and ENDIF commands

Example132 IF (B&C)133 CALCULATOR M=P/R134 ELSEIF (~(B&S))135 CALCULATOR M=P*R136 ELSE137 PID3TERM138 ENDIF

If the expression B&C on line 132 is TRUE, then the Calculatorequation M=P/R on line 133 is performed and control is passed belowline 138. If, on the other hand, the expression on line 132 is FALSE,

IF, ENDIFELSE, ELSEIF

IF, ENDIF, ELSE, and ELSEIF Commands


Page IF-3

then line 133 is skipped and the condition on line 134 is tested. If thiscondition is TRUE, the Calculator on line 135 is executed and controlis passed outside the loop, below line 138.

If the condition in line 134 is also FALSE, then line 136 is the next toexecute. Line 137 is executed when the conditions on lines 132 and134 are both FALSE. ENDIF on line 138 completes the IF expressionstarted on line 132 and also terminates the ELSEIF and ELSE com-mands.

If you are using the ACCOL II Batch Compiler (ABC), or ACCOLWorkbench, you may add indentation, as needed, for readabilitypurposes. If you are using AIC, indentation for the IF, ELSEIF andELSE commands occurs automatically as they are entered in the AIC.Any incomplete or incorrect statement will produce an alpha errorcharacter at the left margin of the line as they are entered. The alphacharacter will disappear as each line is properly entered. Errorcharacters are discussed in 'Control Statements'.

ELSEIF may be repeated within the IF/ENDIF loop. However, ELSEcan only be used once since it is a condition of last resort. It must bethe last entry preceding the ENDIF terminator.

Each IF, ELSEIF and ELSE command must conform to a specifichierarchy of initiator and terminator commands as follows:

Initiator Terminator

IF ENDIF or ELSE or ELSEIFELSEIF ENDIF or ELSEELSE ENDIF

The hierarchy of these constructs permits nesting up to a depth of 16.Conditional commands do not permit the transfer of control from onetask to another.

BLANK PAGE


Page Integrator-1

IntegratorIntegrator Module

This module adds an input value to a building accumulation and thusperforms an integration.

The integral accumulation can be reset via the RESET terminal, and aZERO input allows an initial value to be established prior to startingintegration. The accumulation is limited in size by the resolution ofthe maximum floating point number.


is the analog signal to be integrated

RESET

will reset the module to the value on the ZERO terminal at fixed timeintervals when set ON.

The ACCOL programmer should turn this signal ON prior to theexecution of the module in the last second of the time interval over



SPAN

ZERO

OUTPUTINPUT

RESET

Integrator


Page Integrator-2


which integration is done. For example, if the input is being integratedfor 1 hour at a sample rate of 1 second, RESET should be set ON inthe 60th second prior to module execution. Turn RESET off prior tomodule execution in the next second. When RESET is held ON forlonger than one module execution the output will remain steady at thevalue specified by the ZERO terminal and integration will not occur.

ZERO

is used to specify the initial accumulation and the value on the OUT-PUT terminal when the module is reset via the RESET terminal.

SPAN

is used to scale the INPUT signal so that integration occurs in thecorrect engineering units. Since the Integrator's time base is seconds,it is assumed that the input rate is "per second." If the input rate isdifferent, for example, gallons per hour, then the SPAN would be setto 1/3600 (gallons per hour), so that the OUTPUT would be correct.This is independent of the task rate, since the Integrator keeps trackof the amount of time which has elapsed since the last execution.

OUTPUT

is the integral (sum) of all the input samples





Page Integrator-3


Module Operation

The Integrator executes the following equation:

tOUTPUT = ( SCALED INPUT) dt

tr

where: tr is time of last reset

The accumulative output of the Integrator is expressed by the equa-tion:

Last INPUT + INPUTOUTPUT = Last OUTPUT + �TIME * SCALE *

2

where �TIME is the elapsed time in seconds since the last moduleexecution. This may not be the same as the assigned task rate if thesystem is busy enough to experience task rate slippage.

On each execution this module reads the value of its input signal,multiplies the value by the elapsed time in seconds since the modulelast executed, multiplies again by a scaling factor, and adds the resultto an accumulating sum of previous scaled readings. The module thusacts as an integrator, with the degree of resolution controlled by therate of execution.

The figure below illustrates the output of the module over time with afixed signal value of 1.0 applied to the input. The vertical axis is theoutput (1 to 5 units), and the horizontal axis is the time period (1 to 6seconds). The module executes every second.

In the lower left corner of the graph the initial output is zero and thetime is zero. After one second, the integral is 0.5 and thus the moduleoutput is 0.5. With the second execution, the average input value 1.0 isadded to the integral value of 0.5 giving an output of 1.5 units. At the


Page Integrator-4


third execution the input value 1 is again added to the integral givingan output value of 2.5. Each execution the integral value will increaseby 1.0 until the module is reset.

The module output increases every second in stair-step fashion; alinear output plot is obtained by connecting each step. The input willonly be sampled when the module executes; if it is a time-varyingsignal the execution rate must be set to sample fast enough to notmiss important data.

5

4

3

2

1Input =1 unit

units

1 2 3 4 5 6

Plotted

Integrated Output

Output

time

ACCOL II Reference ManualPage Internet-1

Internet_ProtocolInternet Protocol Module

The Internet Protocol Module allows the user to monitor IP communi-cation operation, and where necessary, adjust certain IP communica-tion parameters. The Internet Protocol Module is NOT required for IPcommunication to function.


MODE Default: 0.0 (No operations)Format: Analog Signal or ConstantInput/Output: Input

specifies whether the module should be used to monitor parameters(read operation) or to adjust parameters (write operation).

The possible values for MODE are as follows:

0 No operation (default)1 Monitor parameters (read operation)2 Adjust parameters (write operation)

The type of parameters which are monitored or adjusted are specifiedvia the TYPE terminal.

TYPE Default: 0.0Format: Analog Signal or ConstantInput/Output: Input

specifies which type of parameters are to be monitored or adjusted.Possible values for TYPE are:

0 IP system parameters1 Alarm system parameters2 IBP connection defaults

Internet_Protocol


Page Internet-2


STATUS Default: None, entry requiredFormat: Analog SignalInput/Output: Output

indicates the status of read or write operations. Possible status valuesare listed below:

0 Operation performed successfully-1 Invalid mode specified-2 Invalid type specified-3 List not found in RTU-4 List too short, or signal unwired-5 Signal in list is not analog

LIST Default: None, entry requiredFormat: Analog SignalInput/Output: Input

specifies the number of an ACCOL signal list. The signals in thespecified list are used to monitor/change parameters. The compositionof the list varies depending on the value of the TYPE terminal.

If TYPE=0, the list consists of IP system parameters, primarilyrelated to measuring timestamp differences between an NHP and itsRTUs.

To determine whether its time is 'in sync' with its NHP, each RTU willperform measurements of estimated time differences using messageswhich travel back and forth to its NHP. If the average estimated timedifference is less than TS.LARGE.START, and the difference inmeasurements is also less than TS.CLOSE.DIFF, the RTU'stimestamp will be adjusted based on the average estimated timedifference.

If the average estimated time difference is greater thanTS.LARGE.START, and the measured time difference is less than



TS.LARGE.DIFF, the RTU's timestamp will be adjusted based on theaverage estimated time difference.

If none of these cases are true, the measurements are consideredinvalid and the measuring process continues until valid measurementsare obtained (and the timestamp can be adjusted) or until the numberof measurements specified by TS.RETRY.SWCH has been performed,in which case the RTU will attempt to communicate with a differentNHP.

Each entry in the signal list must be an analog signal, and must bemade in the order shown, below, however, the choice of signal namesis entirely that of the user.

Signal: Description:MESSAGE.TMO Time out (in seconds) for message ex-

changes.

TS.CLOSE.DIFF Maximum difference (in milliseconds)between time measurements, whencalculated time delta is less thanTS.LARGE.STRT.

TS.LARGE.STRT Specifies a boundary (in milliseconds)which determines whetherTS.CLOSE.DIFF or TS.LARGE.DIFF willbe used to measure time discrepancies.

TS.LARGE.DIFF Maximum difference (in milliseconds)between time measurements, whencalculated time delta is greater thanTS.LARGE.STRT.

TS.ERROR.STRT Maximum timestamp difference (inmilliseconds). If this difference is ex-ceeded, it allows the timestamp to beadjusted even though no valid measure-ments can be obtained.


Page Internet-4


Signal: Description:TS.MEAS.CNT Number of measurement attempts for

good tolerance.

TS.RETRY.PASS Number of NHPs to try for time synch.

TS.RETRY.SWCH Number of attempts before switching to adifferent NHP.

If TYPE=1, the list consists of Alarm system parameters. Each entryin the signal list must be an analog signal, and must be made in theorder shown, below, however, the choice of signal names is entirelythat of the user.

Signal: Description:ALM.ACT.RET Retries before alarm host is in HOLD to

allow for slower re-transmissions.

ALM.ACT.TRNS The time between retransmission of analarm report, when Host is ACTIVE.

ALM.HOLD.MIN The minimum re-transmission time for ahost when an ACK has not been receivedfor an alarm (HOLD).

ALM.HOLD.MAX The maximum re-transmission time(HOLD).

ALM.HOLD.INCR Time added after each re-transmissionuntil ALM.HOLD.MAX has expired.

ALM.OFFL.MIN The minimum retransmission time for thehost, when the host is not acceptingalarms (no alarm processor) (OFFLINE).



Signal: Description:ALM.OFFL.MAX Maximum retransmission time

(OFFLINE).

ALM.OFFL.INCR The time added after each retransmissionuntil ALM.OFFL.MAX has expired.

If TYPE=2, the list consists of IBP (Internet Bristol Protocol) defaultconnection parameters. These are used at connection startup; ifcommunicating with an Open BSI workstation (instead of another IPRTU), the workstation will use its own defaults once the data link hasbeen started, instead of those specified here. Each entry in the signallist must be an analog signal, and must be made in the order shown,below, however, the choice of signal names is entirely that of the user.

Signal: Description:IBP.ACK.TMO The number of milliseconds within which

an IBP acknowledgment must be received.

IBP.ACK.RTRY The maximum number of attempts whichwill be made to send a message before it isdiscarded. Any particular attempt isdeemed a failure if an acknowledgment isnot received within the time specified byIBP.ACK.TMO.

IBP.WRITE.DLAY This is a packing delay (in milliseconds)between messages transmissions.

IBP.THROTL.DLAY This is a delay (in milliseconds) betweenmessage transmissions, when throttlemode is active.

IBP.INACTV.PURG This is the time (in milliseconds) after thelast receipt of a message, that the systemwill wait before starting to purge anypending out-going messages.


Page Internet-6


❏ Module OperationThe Internet Protocol Module must be placed in an executing task. DoNOT place it in Task 0.

At each task execution, the module will examine the MODE terminalto determine whether parameters are to be adjusted (written to) orsimply monitored (read from). The module will also examine the TYPEterminal to see which parameters are to be accessed (IP or alarm).

The parameters are then read from or written to via the signals in thesignal list specified by the LIST terminal.

At the completion of module execution, the STATUS terminal will beupdated.

ACCOL II Reference ManualPage IP_Client-1

IP_ClientIP Client Module

The IP_Client Module, working in combination with the IP_ServerModule, allows ACCOL signal or array values to be transferredbetween two IP-capable remote process controllers.

NOTECurrently, the only IP-capable RTU's are 386EX ProtectedMode versions of the DPC 3330 and DPC 3335, with PES/PEX03 or newer firmware.

The IP_Client Module can read the following types of data from anIP_Server Module in another IP-capable controller (this controller isreferred to as the target RTU):

� Rows of Analog array values (up to an entire array)� Rows of Logical array values (up to an entire array)� Signal values for consecutive signals in a signal list (up to an entire

list)

IP_Client


Page IP_Client-2


The IP_Client Module can write to the following types of ACCOLstructures in the target RTU:

� Rows of Analog array values (up to an entire array)� Rows of Logical array values (up to an entire array)� Consecutive signal values in a signal list (up to an entire list)

The IP_Server Module in the target RTU is responsible for facilitatingthe read/write requests of the IP_Client Module.


REMOTE Default: None, entry requiredFormat: String SignalInput/Output: Input

identifies the IP address or IP node name of the target RTU whichdata will be read from or written to. The target RTU must include anIP_Server Module in order for communication to occur.

If an IP address string is provided, it must be entered in dotted-decimal format, for example:

210.55.41.3

If an IP node name string is used, it must be the node name defined inthe NETDEF file at the Network Host PC (NHP), and the NHP mustbe accessible in order to resolve the IP node name into an IP address.The IP node name can be up to 16 characters in length; an examplenode name string is shown below:

PUMP_STATION_3



RESOLV_NAME Default: 0.0Format: Analog SignalInput/Output: Input

provides a way to re-resolve an IP address for the target RTU fromthe node name provided on the REMOTE terminal. When set to 1.0,the module initiates communications with the NHP to resolve theREMOTE name to an IP address. The RESOLV_NAME terminal willthen automatically be reset to 0.0. This terminal should be usedsparingly, because of the communications overhead involved. Nomatter what value this terminal is, a resolution will always occur thefirst time the module is executed.

SERVR_ID Default: 1.0Format: Analog Signal or ConstantInput/Output: Input

identifies the number of the IP_Server Module in the target RTUwhich will respond to this IP_Client Module. Currently this must beset to 1.

ACCESS_MODE Default: 1.0 (DBREAD)Format: Analog SignalInput/Output: Input

specifies whether data will be read from, or written to, the targetRTU. It also allows the user to cancel a pending read/write request.The following are valid entries for ACCESS_MODE:

1 = DBREAD (read data from the target RTU)2 = DBWRITE (write data to the target RTU)3 = DBABORT (cancel pending read/write request)

If access mode 3 (DBABORT) is used, the ACCOL program (or user)must check the STATUS terminals to determine whether or not acancellation request has been completed.


Page IP_Client-4


RESP_TMO Default: 1200.0, if unwiredFormat: Analog Signal or ConstantInput/Output: Input

specifies the Response Timeout value (in units of 0.1 seconds). Thisvalue determines how many seconds the IP_Client Module will waitfor a response from the IP_Server in the target RTU, before abandon-ing the request, and reporting a timeout error message. This valuemust range from 0.0 to 15,000.0 (0 to 25 minutes), otherwise theRESP_TMO will automatically be set to 1200.0 (2 minutes). When thetimeout occurs, an error is reported. If the target RTU was part of aredundant pair, the backup RTU will be tried before reporting theerror.

NOTE: After failing to the redundant backup unit, the timeout is resetto the RESP_TMO value. The user must take this additional periodunder consideration when testing for completion.

NOTE: The system will not allow the RESP_TMO value to be lessthan the timeout used by the 'transport level'. The transport leveltimeout is obtained by multiplying together the IBP.ACK.TMO andIBP.ACK.RTRY entries (defined in the Internet_Protocol Module).

STRUCT_TYPE Default: 1.0 (Signal list) if unwired, or 0.0Format: Analog Signal or ConstantInput/Output: Input

specifies the type of ACCOL structure referenced by theSERVR_STRUCT_NO and CLNT_STRCT_NO terminals. The struc-ture types on both these terminals must match. Valid values forSTRUCT_TYPE are:

1 = Signal List2 = Analog Data Array3 = Logical Data Array

4-7 = (Internal structures; do NOT use)



SERVR_STRUCT_NO Default: None, entry requiredFormat: Analog Signal or ConstantInput/Output: Input

identifies the number of the structure (Logical Data Array number,Analog Data Array number, or Signal List number) which is to beaccessed via the IP_Server Module in the target RTU. For example, toaccess Analog Data Array number 36, enter 36 on this terminal.

If the CLNT_STRCT_NO terminal is unwired, its value will default tothe value of SERVR_STRUCT_NO.

SERVR_INDEX Default: 1.0Format: Analog Signal or ConstantInput/Output: Input

corresponds to a position in the structure specified by theSERVR_STRUCT_NO terminal. This position is the first position inthe signal list, or the first row in the data array, which will hold thedata to be sent to (or received from) the client structure. The totalnumber of items requested may be modified by the CLNT_COUNTterminal. If the CLNT_INDEX terminal is not wired, then its valuewill default to that given by this terminal.

ACCESS_TYPE Default: 1.0, if unwired or not one of thechoices below


specifies the method by which data will be read (or written to) speci-fied structures in the target RTU.


Page IP_Client-6


For Signal Lists:ACCESS_TYPE = 1 Process only signal values (default)

For Data Arrays:ACCESS_TYPE=1 Access by rows - all columns of

each applicable row (default)

SERVR_SELECT Default: 1.0Format: Analog Signal or ConstantInput/Output: Input

this terminal is used to select the column number for a two-dimen-sional array at the server. The array is still accessed by the row,except that this terminal specifies the starting column of the selectedrow.

CLNT_STRCT_NO Default: Value specified bySERVR_STRUCT_NO


If the CLNT_STRCT_NO terminal is unwired, its value will default tothe value of SERVR_STRUCT_NO.

CLNT_INDEX Default: Value specified by SERVR_INDEXFormat: Analog Signal or ConstantInput/Output: Input

corresponds to a position in the structure specified by theCLNT_STRCT_NO terminal. The specified position is either the firstposition in a signal list, or first row in a data array, which will holddata read from (or to be written to) the server. The total number ofitems requested may be modified by the CLNT_COUNT terminal. Ifthe CLNT_INDEX terminal is not wired, then its value will default tothat given by the SERVR_INDEX terminal.



CLNT_SELECT Default: Value of SERVR_SELECTFormat: Analog Signal or ConstantInput/Output: Input

this terminal is used to select the column number for a two-dimen-sional array at the client. The array is still accessed by row exceptthat this terminal specifies the starting column of the selected row.

CLNT_COUNT Default: 0.0 (complete structure)Format: Analog Signal or ConstantInput/Output: Input

specifies the number of elements to be processed. Entering 0.0 orleaving the CLNT_COUNT terminal unwired will cause the entirearray or signal list to be transferred.

Specifiying a positive non-zero value of n will cause n number ofelements (array elements or signal list entries) to be transferred. Ifyou specify a CLNT_INDEX value other than 1, the total number ofelements sent may be smaller than n.

If the value of n exceeds the structure size, a warning code will bereported on the STATUS_2 terminal, and the request will be can-celled.

STATUS_1 Default: None, entry is optionalFormat: Analog or Logical SignalInput/Output: Output

indicates the completion of communications. If an analog signal isspecified on this terminal, its value is incremented by 1 upon comple-tion of a transmission. If a logical signal is specified on this terminal,its status is set to OFF when the IP_Client initiates communications,and is turned ON when communications are completed.


Page IP_Client-8


STATUS_2 Default: None, entry is optionalFormat: Analog SignalInput/Output: Output

reports status codes concerning the completion or error status ofIP_Client Module operation. This value is set upon completion of allcommunications.

A list of possible values for STATUS_2 appears below:

StatusValue Description10 NHP resolution request transmission required

9 Bypass code8 Access granted to tested structure7 The next packet of a multi-packet message has been trans-

mitted6 Unable to allocate response buffer warning5 Busy. Previous client request being processed4 Acknowledgement packet3 Acknowledgement packet2 Signal was control inhibited0 Successful completion

-1 Invalid mode specified (must be 1, 2, or 3)-20 Internal structure error-22 Signal could not be updated-33 Zero length server list-37 Invalid outgoing array number-39 Invalid list or unwired-40 Index exceeds the number of entries in the structure-41 RESP_TMO value out of bounds-42 Invalid server ID specified-43 Invalid ACCESS_TYPE specified-44 Invalid ACCESS_MODE specified-45 Invalid STRUCT_TYPE specified-46 SERVR_STRUCT_NO unwired or invalid-47 SERVR_INDEX unwired or invalid



StatusValue Description

-48 CLNT_INDEX unwired or invalid-49 Unknown format identifier received in element header-51 The number of data items in the packet exceeds the number

expected-52 Client module has exceeded the number of allowed requests-53 Invalid count value-54 Types are mismatched-55 Orphan packet received and discarded-56 An earlier request is still being processed-57 Incorrect count for items processed-58 Unable to get connection to designated IP address-59 Invalid structure requested from server-60 Invalid ACCESS_MODE detected at server-61 Unable to write to array element-62 IP terminals configured incorrectly in IP_Client Module-63 Incorrectly formatted IP address presented-64 Response timeout error from a client or server-65 Unsupported data type-66 NHP unable to resolve REMOTE terminal node name

string into one or more IP addresses-67 There is no NHP available to translate the node string

name on the REMOTE terminal-68 Value(s) specified on SERVR_INDEX, SERVR_SELECT,

CLNT_INDEX or CLNT_SELECT terminal(s) are out ofbounds

-69 The requesting node is not authorized to request datatransactions on the server node

-70 The requesting node is not authorized to access the re-quested structure in the server node


Page IP_Client-10


StatusValue Description-71 The requested structure is not available on the server node-72 Invalid access mode-73 Unable to access specified protection array-74 Invalid protection structure-75 Message buffer queue between module and IP sub-processor

is full-76 No server module has been detected on the target node-77 RESOLV_NAME terminal is invalid-78 Problem translating at least one string node name in the

server's KNOWN_IP_NODES list-79 A packet from an NHP has sent an unknown string node

name-80 Pending request aborted by user-81 Several attempts to allocate communications buffers for

pending transmissions have failed

❏ Module OperationThe IP_Client Module must be placed in an executing task. Do NOTplace it in Task 0. The IP_Client Module can only initiate communica-tions with another IP-capable controller (the target RTU) which isconfigured with an IP_Server Module. Users who want to transferdata between an IP-capable controller and a BSAP controller must usethe standard Master/EMaster and Slave modules, instead.

Only the IP_Client Module can initiate requests for data transfer tooccur; the IP_Server Module in the target RTU then responds to thoserequests.

Three possible modes of operation may be selected via theACCESS_MODE terminal:

DBREAD allows the IP_Client to read signal list or data array datafrom the target RTU.



BLANK

DBWRITE allows the IP_Client to write (send/change) data in signallists and data arrays in the target RTU.

DBABORT allows the IP_Client to cancel any pending read/writerequests. This may be useful if there is significant time being ex-pended waiting for a response from the IP_Server in the target RTU.

IMPORTANT

No matter which access mode you are using, the operations performedmay take more than one task execution to complete. Because of this,users must always verify that these operations are complete beforeusing data resulting from the operations, otherwise the data may beincorrect. The completion status of these operations is reported via theSTATUS_1 and STATUS_2 terminals.

The type of data being collected (array or signal list) is specified usingthe STRUCT_TYPE terminal.

The client RTU's arrays or lists used to send/receive data must matchthe size and type of their counterparts in the target RTU.

The target RTU must be identified on the REMOTE terminal via astring signal representing either the IP address of the target RTU indotted decimal format, e.g. 120.45.20.3 or the node name of the targetRTU as defined in the current NETDEF file at the Network Host PC(NHP). If a node name is entered, when the IP_Client first executes, itwill automatically contact the NHP to obtain an IP address for thegiven node. If, for any reason, the IP address of the target RTUchanges (even though the node name is the same) theRESOLV_NAME signal must be turned on via user-controlled logic toobtain the new IP address from the NHP.

NOTE: This operation consumes excess communications overhead andshould be used sparingly.


Page IP_Client-12


If the target RTU is part of a redundant pair, both RTU's in theredundant pair must be given the same node name. When theIP_Client Module initiates communications, the NHP will provide twoIP addresses (one for each unit in the redundant pair). Then, duringsubsequent communication transactions, if a failure occurs with thetarget RTU, the IP_Client will attempt to communicate with thebackup unit, using the second IP address.

For additional information on communication between IP-capablecontrollers, see the 'IP Client/Server Communication' section, and the'IP_Server Module' section. For a description of IP addressing andsub-net masking, see the 'IP Node Addressing' section.

ACCOL II Reference ManualPage IPClient/Servr-1

IP Client / Server CommunicationsIP Client / Server Communications

IP Client / Server communications allows data from ACCOL struc-tures such as signal lists and data arrays to be transferred from oneIP-capable remote process controller to another IP-capable remoteprocess controller

NOTECurrently, the only IP-capable RTU's are 386EX ProtectedMode versions of the DPC 3330 or DPC 3335, with PES03/PEX03 or newer firmware.

The IP_Client Module initiates all such communication transactionsby contacting an IP_Server Module in another IP-capable controller(the target RTU). The IP_Client Module requests either read-only, orread-write access to various arrays, signal lists, etc. in the targetRTU. The IP_Server can grant those requests for access, or denythem, based on how its module terminals are configured.

The IP_Client Module can request access to entire structures (anentire data array, or an entire signal list) or it can request access toonly a set of contiguous signals in the signal list, or contiguous ele-ments in a data array based on the entries in its SERVR_INDEX andCLNT_COUNT terminals.

The IP_Server Module in the target RTU can restrict access to thestructures under its control using its LIST_DB, AARRAY_DB andLARRAY_DB terminals. It can also restrict access to IP_Clients whosenode names or addresses appear in the KNOWN_IP_NODES list; anyunlisted nodes will be denied access by the IP_Server.

❏ Example #1 - Copying Signal List Data

There are two remote process controllers, with IP node addresses of120.0.0.1, and 120.0.0.3, respectively. The user wants to read the firstthree entries of Signal List #5 in the 120.0.0.3 unit (the server), intopositions 8, 9, and 10 of Signal List #3 of the 120.0.0.1 unit (the client).

IP Client / ServerCommunications


Page IPClient/Servr-2


The example, below, outlines the configuration required to performthis data transfer.

Configuring the IP_Client Module:

When configuring the IP_Client Module, the target RTU for whichaccess is desired must be identified on the REMOTE terminal signal.In this case, the target RTU will be identified by its address of120.0.0.3.

Because read access to that RTU is required, the ACCESS_MODEsignal must be set to 1 (DBREAD).

Because the type of structure being read is a signal list, theSTRUCT_TYPE signal must be set to 1 (Signal List).

Since data must be read from Signal List #5 in the target RTU, theSERVR_STRUCT_NO terminal signal must be set to 5. Since only thefirst 3 entries in Signal List #5 are to be read, then theSERVR_INDEX terminal signal must be set to 1 (i.e. start with thefirst position in the list), and the CLNT_COUNT terminal signal mustbe set to 3 (i.e. read only the first 3 entries of the list).

In addition, the signal list data being copied in from the target RTU isto be stored in positions 8, 9, and 10 of Signal List #3. Therefore, theCLNT_STRCT_NO must be set to 3 (for Signal List #3), andCLNT_INDEX must be set to 8 (because position 8 is the first positionwhere data must be stored).

Configuring the IP_Server Module

IP_Server configuration is somewhat simpler. If the LIST_DB andKNOWN_IP_NODES terminals were left unwired, there would bealmost no configuration. To illustrate how the IP_Server Moduleallows restrictions to be placed on access, these terminals will bewired.




The LIST_DB terminal will specify an analog data array which willidentify which signal lists are to be made accessible to IP_Clients. Inthis case, we must include Signal List #5 in that array, and specifythat it will be available for read access.

The KNOWN_IP_NODES terminal will specify a signal list which willcontain signals that identify the RTU's which will be granted accessvia IP_Client requests. In this case, we must identify the RTU withaddress 120.0.0.1.

❏ Example #2 - Changing Array Values

There are two remote process controllers, with IP node addresses of210.3.2.1, and 210.3.2.2, respectively. The user wants to take row #3of data array values from analog array #7 in the first controller (theclient), and write those values to row #6 in analog array #26 of thesecond controller (the server). There are 4 entries in each row of botharrays. The example, below, outlines the configuration required toperform this data transfer.

Configuring the IP_Client Module:

When configuring the IP_Client Module, the target RTU for whichaccess is desired must be identified on the REMOTE terminal signal.In this case, the target RTU will be identified by its address of210.3.2.2.

Because write access to that RTU is required, the ACCESS_MODEsignal must be set to 2 (DBWRITE).

Because the type of structure being written to is an analog data array,the STRUCT_TYPE signal must be set to 2 (Analog Data Array).



Since data must be written to Analog Array #26 in the target RTU,the SERVR_STRUCT_NO terminal signal must be set to 26. Since therow to be written to is row 6, the SERVR_INDEX terminal signalmust be set to 6. Since only a single row (4 elements) will be writtento, the CLNT_COUNT terminal signal must be set to 4.

In addition, the array row being transmitted comes from row 3 ofanalog array #7 in the Client RTU. Therefore, theCLNT_STRUCT_NO must be set to 7 (for analog array #7), andCLNT_INDEX must be set to 3 (for row #3).

Configuring the IP_Server Module

IP_Server configuration is somewhat simpler. If the AARRAY_DB andKNOWN_IP_NODES terminals were left unwired, there would bealmost no configuration. To illustrate how the IP_Server Moduleallows restrictions to be placed on access, these terminals will bewired.

The AARRAY_DB terminal will specify an analog data array whichwill identify which analog data arrays are to be made accessible toIP_Clients. In this case, we must include Analog array #26, andspecify that it will be available for write access.

The KNOWN_IP_NODES terminal will specify a signal list which willcontain signals that identify the RTU's which will be granted accessvia IP_Client requests. In this case, we must identify the RTU withaddress 210.3.2.2.

ACCOL II Reference ManualPage IPAddr-1

IP Node AddressingInternet Protocol Node Addressing

Any Bristol controller which supports IP communications will bereferred to as an IP node.* Each IP node must be configured with atleast one network connection called an IP port which will allowcommunications via Ethernet.

Each IP port has an associated IP address. Because a particular IPnode can have more than one IP port, it can also have more than oneIP address.

Each IP node also has an associated sub-net mask which is used incommunications routing decisions. These subjects will be explainedlater.

There is no hierarchical structure enforced in a pure IP network; allnodes may be on the same level.

An IP network can, however, have multiple sub-networks, includingBSAP sub-networks; the BSAP portions of which, must follow thestandard BSAP concept of network levels. There are numerous otherpossible IP configurations including routers, multiple networks, etc.,however, these will not be discussed here.

IP Node Addressing

*Currently, only the 386EX Protected Mode versions of theDPC 3330 and DPC 3335 with PES03/PEX03 or newerfirmware, support IP communication.


Page IPAddr-2


Information on the IP addresses for a given section of the Bristol IPnetwork is stored in a Network Definition File (NETDEF) at a specialOpen BSI workstation called the Network Host PC, which is abbre-viated as NHP. A program called NetView is used to create theNETDEF file.

If an IP node or an Open BSI workstation needs to communicate withanother IP node or Open BSI workstation, and it doesn’t know theaddress of the IP Port for that node or workstation, it obtains thenecessary addresses and routing information from the NETDEF file atthe NHP.

What is the Format of IP Addresses?Each network connection from an IP node or workstation has an IPaddress which is unique within the network. It is important to notethat the IP address is associated with the network connection (IP Port),NOT the node itself. This allows a single IP node to have more thanone IP port, and consequently, more than one IP address.

IP addresses consist of 32 bits (1’s and 0’s) which are divided up into 4groups of 8 bits each. A period is used to separate each group. Eachgroup of 8 bits is then converted from binary to a decimal number from0 to 255. The resulting IP address is said to be in dotted decimalnotation.

Each of the numbers in the address 120.0.210.1 generally have aspecific meaning. The IP address is typically divided up into a net-



work portion which must be common to each node in the network,and a local portion which must be unique to a particular node.

How Is An RTU's IP Address Assigned?

An RTU's IP address must be initially configured using the LocalViewutility, available with Open BSI Utilities version 3.0 (or newer). Forinformation on LocalView, see the Open BSI Utilities (Ver 3.x) Manual(document# D5081). Once communications have been established,NetView can be used to change the IP address, if necessary.

How is the Specific Meaning of EachPart of the Address Defined?

Addresses must be assigned to be consistent with whatever conven-tions have been established for your system. For example, if thisnetwork has connections outside the plant (i.e. a connection to theexternal world-wide Internet), then the choice of this network numberis assigned by an Internet governing body called the Network Informa-tion Center (NIC) or whatever Internet service provider you are using.In addition, there are certain rules to defining addresses, which will bediscussed later.

The specific meaning of each part of the address is defined in some-thing called the sub-net mask. The sub-net mask is simply anotherset of 32 bits (which must also be converted to dotted decimal nota-tion.) Each bit in the sub-net mask corresponds to a bit in the IPaddress.

If a bit in the sub-net mask is set to 1 (ON), then the corresponding bitin the IP address is considered to be part of the network portion ofthe IP address. The network portion can be ignored (or ‘masked’) whenperforming communications to nodes in the same network, because by


Page IPAddr-4


definition, all nodes in the same network have identical networkportions. Any bit in the sub-net mask which is 0 (OFF) is considered tobe part of the local addressing scheme.

The figure, below, shows the IP address and corresponding sub-netmask for an IP address of 120.0.210.1, and a sub-net mask of255.0.0.0.

As we said before, a '1' in the sub-net mask indicates that the corre-sponding bit in the IP address is part of the network portion of theaddress. Because the first part of the IP address '01111000.' has acorresponding sub-net mask of '11111111' we know that '01111000'(120 in decimal) is the network portion of the address.

The remaining parts of the IP address ‘00000000.11010010.00000001’have a corresponding sub-net mask of ‘00000000.00000000.00000000’.These bits are used as part of the local communications addressingscheme.



Rules For Creating A Local AddressingScheme

When you are creating your IP address, the network portion of theaddress must appear first. For example, if the network portion is 120,you CANNOT define an IP address as 0.120.210.1. The networkportion must appear first. This means that when creating the sub-netmask, the masked portion (i.e. all 1’s) must appear first.

The organization of the remaining bits can follow any local communi-cations scheme you choose to devise, except that each group of bitsthat represents something must be contiguous.

For example, let’s say the first 16 bits have been ‘masked out’ to definethe network address, i.e. there is a sub-net mask of:

11111111 . 11111111 . 00000000 . 00000000

which in dotted decimal format is:

255 . 255 . 0 . 0

That leaves 16 bits (indicated by the 0’s) for devising a local communi-cations scheme.

You might want to use the first 8 bits to indicate a section or areanumber for a section of your network. 8 bits will allow up to 256sections to be defined. Another 8 bits (remaining out of the 16 avail-able) can be used to indicate a node number, allowing up to 256 IPcontrollers (RTUs) and Open BSI workstations in a given section.

section#Network identification Node#

ssssss.nnxxxxxxxx.xxxxxxxx.ss nnnnnn


Page IPAddr-6


Sub-Net Masks Determine Which NodesAre Reachable From This Node:

So far, we have been talking about the mechanics of creating IPaddresses and sub-net masks. The aspect we have not discussed is whyIP addresses and sub-net masks are so important.

A node's IP address, and its sub-net mask, define the range of accept-able addresses with which the node can communicate. For example, ifone node has an IP address of 4.3.2.1 and another node has an IPaddress of 100.100.0.1, there is no common network portion betweenthe two addresses. For that reason, there is NO way these two nodescan communicate with each other directly - - they are each part ofdifferent networks. Any messages between these nodes would have topass through one or more router computers. For two nodes to commu-nicate directly, the network portion of their addresses (as specified bythe sub-net mask) must match exactly.

To illustrate this concept,look at the figure, at right.The network shown has oneNetwork Host PC (NHP)called NHP1, and 3 control-lers (RTUs) namedOAK_STREET,ELM_STREET, andWALNUT_AVE.

The table, on the next page,however, reveals a problemwith the configured sub-netmasks.

Network Host PC NHP1

IP address: 100.22.49.1Subnet Mask: 255.255.255.0

ELM_STREET IP address: 100.22.51.14Subnet Mask: 255.255.0.0

WALNUT_AVE IP address: 100.22.49.178Subnet Mask: 255.255.0.0

OAK_STREET IP address: 100.22.50.33Subnet Mask: 255.255.0.0

EthernetCable



Based on their specified IP addresses and sub-net masks,OAK_STREET, ELM_STREET, and WALNUT_AVE can all communi-cate with each other. They can also send messages to NHP1.

There is a problem, however.NHP1 has a sub-net maskwhich specifies that it canonly send messages to nodeswith addresses 100.22.49.nnnwhere nnn is an integer from0 to 255. The only node whichit can send messages to,therefore, is WALNUT_AVE.To remedy this situation,NHP1's sub-net mask shouldbe changed to 255.255.0.0 sothat it can also send messagesto OAK_STREET andELM_STREET. The correctedsub-net mask is reflected inthe figure at right.

Network Host PC NHP1

IP address: 100.22.49.1Subnet Mask: 255.255.255.0

ELM_STREET IP address: 100.22.51.14Subnet Mask: 255.255.0.0

WALNUT_AVE IP address: 100.22.49.178Subnet Mask: 255.255.0.0

OAK_STREET IP address: 100.22.50.33Subnet Mask: 255.255.0.0

EthernetCable

Corrected Subnet Mask: 255.255.0.0

BLANK PAGE

ACCOL II Reference ManualPage IP_Server-1

IP_ServerIP Server Module

The IP_Server Module, working in combination with the IP_ClientModule, allows ACCOL structure data to be transferred between twoIP-capable remote process controllers.

The IP_Server Module's function is to respond to requests for dataaccess from an IP_Client Module in another IP-capable controller.

NOTECurrently, the only IP-capable RTU's are 386EX ProtectedMode versions of the DPC 3330 or DPC 3335 with PES/PEX03 or newer firmware.


SERVR_ID Default: 1.0Format: Analog Signal or ConstantInput/Output: Input

identifies the number of this IP_Server Module. Currently this mustbe set to 1.

IP_Server


Page IP_Server-2


LIST_DB Default: All lists accessible if unwired or 0Format: Analog Signal or ConstantInput/Output: Input

identifies the number of a two-dimensional analog data array, which istwo columns wide by n number of rows, where n represents the totalnumber of signal lists in this controller which you would like to makeavailable for IP Client/Server communication. The IP_Client can begranted either read only access, or both read and write access.

To specify access for a particular signal list, enter its number incolumn 1 of the array, and enter the type of access in column 2 of thearray. The type of access is either '1' for read-only access, or '2' forboth read and write access.

As an example, the array at right, shows a setof 6 different signal lists which are to be madeavailable for IP Client/Server communication.

Signal Lists 4, 14, 100, 125, and 255 will beavailable for read-only access by IP_ClientModules in other IP-capable controllers.

Signal List 6 will be available for read/writeaccess by IP_Client Modules in other IP-capable controllers.

NOTE: Although Signal List 6 is available forread/write access, there will be no writeaccessibility for signals in the list which arecontrol-inhibited.

Once the LIST array is configured, only signallists declared in this array will be availablefor IP_Client access; any other signal listswill be inaccessible.



It is suggested that extra rows be reserved in the LIST array, so thatadditional entries may be made via on-line editing.

NOTE

If the LIST array is NOT defined (LIST terminal leftunwired), or if the array specified by LIST does not exist,ALL SIGNAL LISTS IN THIS CONTROLLER WILL BEACCESSIBLE FOR IP_CLIENT ACCESS.

AARRAY_DB Default: All analog arrays accessible ifunwired or 0


identifies the number of a two-dimensionalanalog data array, which is two columns wideby n number of rows, where n represents thetotal number of analog arrays in this control-ler which you would like to make available forIP Client/Server communication. TheIP_Client can be granted either read onlyaccess, or both read and write access.

To specify access for a particular analog dataarray, enter its number in column 1 of thearray, and enter the type of access in column 2of the array. The type of access is either '1' forread-only access, or '2' for both read and writeaccess.

As an example, the array referenced byAARRAY_DB, at right, shows a set of 5different analog data arrays which are to bemade available for IP Client/Server communi-cation.


Page IP_Server-4


Analog data arrays 1, 4, and 10 will be available for read-only accessby IP_Client Modules in other IP-capable controllers, and analog dataarray numbers 8 and 25 will be available for read-write access.

NOTE: Although analog data arrays 8 and 25 are available for read/write access, these arrays must be defined, in the ACCOL load file, asanalog read-write arrays; if they are specified as analog read-onlyarrays, there will be no write accessibility for IP_Client Modules, orany other modules.

Once the AARRAY_DB array is configured, only analog data arraysdeclared in this array will be available for IP_Client access; any otheranalog data arrays will be inaccessible.


NOTE

If the AARRAY_DB array is NOT defined (AARRAY_DBterminal left unwired), or if the array specified byAARRAY_DB does not exist, ALL ANALOG DATA AR-RAYS IN THIS CONTROLLER WILL BE ACCESSIBLEFOR IP_CLIENT ACCESS.

LARRAY_DB Default: All logical arrays accessible ifunwired or 0


identifies the number of a two-dimensional analog data array, which istwo columns wide by n number of rows, where n represents the totalnumber of logical arrays in this controller which you would like to



make available for IP Client/Server commu-nication. The IP_Client can be grantedeither read only access, or both read andwrite access.

To specify access for a particular logicaldata array, enter its number in column 1 ofthe array, and enter the type of access incolumn 2 of the array. The type of access iseither '1' for read-only access, or '2' for bothread and write access.

As an example, the array referenced byLARRAY_DB, at right, shows a set of 5different logical data arrays which are to bemade available for IP Client/Server commu-nication.

Logical data array 24 will be available for read-only access byIP_Client Modules in other IP-capable controllers, and logical dataarray numbers 21, 22, 23, and 25 will be available for read-writeaccess.

NOTE: Although logical data arrays 21, 22, 23, and 25 are availablefor read/write access, these arrays must be defined, in the ACCOLload file, as logical read-write arrays; if they are specified as logicalread-only arrays, there will be no write accessibility for IP_ClientModules, or any other modules.

Once the LARRAY_DB array is configured, only logical data arraysdeclared in this array will be available for IP_Client access; any otherlogical data arrays will be inaccessible.



Page IP_Server-6


NOTE

If the LARRAY_DB array is NOT defined (LARRAY_DBterminal left unwired), or if the array specified byLARRAY_DB does not exist, ALL LOGICAL DATA AR-RAYS IN THIS CONTROLLER WILL BE ACCESSIBLEFOR IP_CLIENT ACCESS.

ARCHIVE_DB Default: NoneFormat: Analog Signal or ConstantInput/Output: Input

reserved for future use.

KNOWN_IP_NODES Default: None, entry is optionalFormat: Analog Signal or ConstantInput/Output: Input

allows the accessibility of this module for IP Client/Server communica-tions to be restricted to only a certain list of IP nodes. The value ofKNOWN_IP_NODES specifies a signal list number.

Each entry in this signal list must consist of a string signal whosevalue identifies an IP node which contains an IP_Client Module whichshould be allowed access to this IP_Server Module. The node may beidentified by its IP node address (in dotted decimal format), or its IPnode name. If an IP node name is given, that node name must exist inthe NETDEF file at the Network Host PC (NHP), and the NHP mustbe available in order to resolve the name.



For example, in theKNOWN_IP_NODES signallist shown at right, there areseven nodes listed whichinclude IP_Clients whichwill be allowed access to thisIP_Server Module. Six of theentries listed are given as IPnode addresses, the seventhentry, 'CASTLEHILL' isgiven as an IP node name,because it represents eitherunit in aredundant pair of nodes.

NOTE

If the KNOWN_IP_NODES signal list is NOT defined(KNOWN_IP_NODES terminal is left unwired), or if thesignal list specified by KNOWN_IP_NODES does not exist,ANY IP NODE WITH AN IP_CLIENT MODULE WILL BEALLOWED ACCESS TO THIS IP_SERVER MODULE.

STATUS_1 Default: None, entry is optionalFormat: Analog or Logical SignalInput/Output: Output

indicates the completion of communications. If an analog signal isspecified on this terminal, its value is incremented by 1 upon comple-tion of a transaction with the IP_Client. If a logical signal is specifiedon this terminal, its status is set to OFF when the IP_Client initiatescommunications with this IP_Server, and is turned ON when commu-nications are completed.


Page IP_Server-8


STATUS_2 Default: None, entry is optionalFormat: Analog SignalInput/Output: Output

reports status codes concerning the completion or error status ofIP_Server Module operation. This value is set upon completion of allcommunications.

A list of possible values for STATUS_2 appears in the 'IP_Client'section.

RESOLV_NAME Default: 0.0Format: Analog SignalInput/Output: Input

provides a way to re-resolve IP addresses for RTUs, identified by nodename only, in the KNOWN_IP_NODES signal list. It also re-examinesthe LIST_DB, LARRAY_DB, and AARRAY_DB terminals to deter-mine which structures should be accessible. When set to 1.0, themodule initiates communications with the NHP to resolve node namesin the KNOWN_IP_NODES signal list. The RESOLV_NAME terminalwill then automatically be reset to 0.0. This terminal should be usedsparingly, because of the communications overhead involved. Nomatter what value this terminal is, a resolution will always occur thefirst time the module is executed.


The IP_Server Module must be placed in an executing task. Do NOTplace it in Task 0. The IP_Server responds to requests for data baseaccess from IP_Client Modules in other RTUs.



The SERVR_ID terminal must be set to the ID number of theIP_Server Module, to distinguish it from other IP_Server Modules inthis ACCOL load.

Since only one IP_Server Module per load is supported by currentfirmware, the SERVR_ID should always be set to 1.

The KNOWN_IP_NODES, LIST_DB, AARRAY_DB, and LARRAY_DBterminals allow the user to restrict IP_Client access to certain ACCOLstructures in the controller, and to limit access to only specifiedIP_Clients. It these terminals are unwired, there are no limitations onaccess other than those inherent in the ACCOL load: Control inhibitedsignals and read-only arrays cannot be written to by IP_Clients.

Success of communication transactions with the IP_Client are re-ported via the STATUS_1 and STATUS_2 terminals.

BLANK PAGE


Page ISO5167-1

ISO5167International Standard ISO 5167 Module

The ISO5167 Module calculates flow rate for Orifice plates, Nozzles,Venturi tubes, and Venturi-nozzle Primary Devices as specified in theInternational Organization for Standardization's International Stan-dard ISO 5167-1980 (E), 1980 edition. Beginning with ACCOL firm-ware PLS04.40, the ISO5167 module was revised to provide a choiceof either the 1980 calculation method or calculations per the ISO-5167Amendment of 1998. Flow rate is calculated in mass units of kilogramsper hour (kg/h) or in volume units of cubic-meters per hour (m3/h) andit can be scaled into other engineering units if that is necessary. Theinternal factors used in the calculation (CD, Ev, Y, A, EXT, REYN)can be moved to a list for verification or comparison.

PIPE_DIAM

POINT

ORIF_DIAM

OUTPUT

TRACK

ISO5167

ADJ _PRESSSTAT_ PRESS

FLOW_TEMP

STAT_P2

THERMAL_COEF1

DENSITYBASE _DENS

LIST

THERMAL_COEF2

VISCOSITY

ISEN_COEF

DEVICE2DEVICE

DIFF_ PRESS

ISO5167


Page ISO5167-2


To accomodate all Primary device types the allowed range of Beta(Orifice diameter/pipe diameter) is 0.1 to 0.8 even though the ISO5167 standard specifies narrower limits for some devices. Users mustbe aware of the usage limits for devices. Beta values less than 0.1 orgreater than 0.8 produce a zero output rate.

❏ Module EquationThe gas flow rate is calculated using the following equation:

Qx = CD Ev Y A Ext 3600 (1/rhob) SF

where,

Qx = Flow rate in kilograms per hour (kg/h) orcubic meters per hour (m3/h).

CD = Coefficient of discharge for the PrimaryDevice.

Ev = Velocity of Approach factor.

Y = Gas Expansion factor.

A = Area of device throat or orifice bore =PI d2/4.

Ext = (2 hw rhof)1/2

hw = Differential pressure, Pascals.

rhof = Gas density in kg/cubic meter at flowingconditions

rhob = Gas density in kg/cubic meter at baseconditions.


Page ISO5167-3


3600 = conversion factor for a per hour rate.

SF = Scale factor to convert to other units.

Flow rate, Qx is a mass rate in kilograms per hour if Base Density(rhob) and Scale Factor (SF) are both 1.0. Flow rate is a volume ratein cubic-meters per hour if Base Density is other than 1.0 and ScaleFactor is 1; Scale Factor can be used to scale the flow rate into otherunits.

The Coefficient of Discharge (CD), varies with the physical devicegeometry, and pipe Reynolds number. The Reynolds number, in turn,varies with flow rate, thus CD and Reynolds number are computed byiteration. In the original version of the ISO5167 Module, CD is calcu-lated using the ISO-5167 (1980) method (the Stoltz equation.) InACCOL firmware PLS04.40 (or newer), the ISO5167 Module useseither the 1980 method, or the 1998 method, depending on the user-specified DEVICE value.


DIFF_PRESS Default: None, entry required(hw) Format: Analog signal or constant

Input/Output: Input

is the differential pressure, hw, in Pascals, across the Primary device.If this terminal is unwired the output rate will be zero. Negative inputvalues are clamped at zero.

STAT_PRESS Default: 0 PaFormat: Analog signal or constantInput/Output: Input

is the gauge static pressure in Pascals upstream of the Primarydevice. Static pressure is added to the Barometric pressure to obtainabsolute pressure which is then used to compute the Expansion factor


Page ISO5167-4


Y. If absolute Static pressure is zero then Y will be zero and theoutput rate will be zero. Negative input values are clamped at zero. Ifthis terminal is unwired the output rate will be zero.

ADJ_PRESS Default: 101325 Pa (14.73 psia)Format: Analog signal or constantInput/Output: Input

is the Absolute Barometric pressure in Pascals. This value is added tothe value on the STAT_PRESS terminal to obtain absolute pressure.

ORIF_DIAM Default: None, entry required(d) Format: Analog signal or constant

Input/Output: Input

is the orifice bore diameter or device throat diameter in millimeters at20 degrees C. Output of the module will be zero if this terminal isunwired, or if the value entered is zero. Negative inputs are clampedat zero. The output of the module will also be zero if the Orificediameter is less than 10% of or more than 80% of the value on thePIPE_DIAM terminal.

PIPE_DIAM Default: None, entry required(D) Format: Analog signal or constant

Input/Output: Input

is the inside diameter of the pipe in millimeters at 20 degrees Centi-grade. Output of the module will be zero if this terminal is unwired, orif the value on the terminal is zero or negative.

THERMAL_COEF1 Default: 0.0000167Format: Analog signal or constantInput/Output: Input


Page ISO5167-5


is the Primary device coefficient of thermal expansion in millimeterper millimeter-degree Centigrade (mm/mm-C).

THERMAL_COEF2 Default: 0.0000112Format: Analog signal or constantInput/Output: Input

is the pipe coefficient of thermal expansion in millimeter per millime-ter-degree Centigrade (mm/mm-C).

DEVICE Default: 1.0Format: Analog signal or constantInput/Output: Input

is the type code for the Primary device. Valid type codes are:

1 = Orifice Plate (1980 method)2 = Nozzle3 = Venturi4 = Venturi-nozzle5 = Orifice Plate (1998 method)

Invalid codes cause an output rate of zero. When codes 2, 3, or 4 areused a downstream pressure must be provided; see the STAT_P2terminal description.

DEVICE2 Default: 1.0Format: Analog signal or constantInput/Output: Input

is the code for tap type when the Primary device is an Orifice plate.For other Primary devices this code indicates the device category.

Valid Tap type codes are:

1 = Flange tap, 2 = Corner tap, 3 = D/2 tap.


Page ISO5167-6


Valid device category codes are:

Nozzle: 1 = ISA1932, 2 = Long radiusVenturi: 1 = Rough cast, 2 = Machined, 3 = Rough weldedVenturi-nozzle: Not required

Invalid codes cause an output rate of zero.

FLOW_TEMP Default: 20o CentigradeFormat: Analog signal or constantInput/Output: Input

is the gas temperature in degrees Centigrade.

VISCOSITY Default: 0.010268 centiPoise (cP)(mu) Format: Analog signal or constant

Input/Output: Input

is the dynamic viscosity of the gas at flowing conditions in centiPoise(cP). This value is used in calculating the Reynolds number (Reyn).


is the gas Isentropic exponent. Previously the Input range allowed was1.0 to 2.0; with values outside this range replaced with 1.3. Beginningwith ACCOL firmware PLS04.40, the ISO5167 Module allows a valueof -1.0 to be used; this value is interpreted as specifying a liquid andthe Gas Expansion Factor Y is set to 1.0.


Page ISO5167-7


DENSITY Default: 10.0 kg/m3

(rhof) Format: Analog Signal or constantInput/Output: Input

is rhof, the gas density in kilograms per cubic meter (kg/m3) at flowingconditions. Negative values are clamped at zero.

BASE_DENS Default: 1.0 kg/m3

(rhob) Format: Analog Signal or constantInput/Output: Input

is the gas density in kilograms per cubic meter at base conditions. Ifthis value is greater than zero the computed mass flow rate at flowingconditions is divided by this value to produce a volume flow rate incubic meters per hour (m3/h) at base conditions at the OUTPUTterminal. Negative values are clamped at zero.

STAT_P2 Default: 0 PascalsFormat: Analog signal or constantInput/Output: Input

is the static pressure in Pascals downstream of the Primary device.The Barometric pressure (ADJ_PRESS) is added to this value to makeit an absolute pressure. The ratio of downstream to upstream absolutepressure is used for the calculation of the Expansion factor Y when thePrimary device code is 2, 3, or 4. If the absolute pressure downstreamis less than 75% of, or more than 100% of the absolute pressureupstream, the Y value is set to zero and the output rate will be zero.


Page ISO5167-8


POINT Default: 1.0(SF) Format: Analog signal or constant

Input/Output: Input

Supplies the Scale Factor (SF). The computed rate is multiplied bythis value to change it to other units before it appears at the OUTPUTterminal.

TRACK Default: ON or 0.0Format: Logical or Analog signalInput/Output: Input

is a signal used to force the module output to zero. When it is a logicalsignal, an ON state enables calculations, an OFF forces the output tozero. When this signal is an analog signal it is treated as a Differentialpressure threshold value or 'cutoff' level; calculations cease and theoutput is forced to zero when the DIFF PRESS terminal value is lessthan the value on the TRACK terminal.

OUTPUT Default: None(Qx) Format: Analog signal


is the computed mass flow rate, Qx , in kilograms per hour or volumerate in cubic-meters per hour or in other units depending on theBASE_DENS (rhob) and the POINT (Scale Factor) terminal values.


is the number of a signal list into which the factors used internally


Page ISO5167-9


will be moved. The six values moved to the list are CD, Ev, Y, A, Ext,and Reyn in that order. These values represent:

CD Computed Coefficient of Discharge for the PrimaryDevice

Ev Velocity of Approach factorY Gas Expansion factorA Orifice or throat area in square metersExt The square root of (2 hw rhof)Reyn Computed pipe Reynolds number,

Reynolds number is calculated as follows:

Reyn = 4000 Qx/(mu * PI * D)

❏ Application Notes - Liquid Flow RatesThe ISO5167 Module can be used to calculate the flow rate of incom-pressible fluids if the flow rate calculated by the module is divided bythe Y (Expansibility) factor used by the module. Beginning withPLS04.40 firmware, the ISO5167 Module allows ISEN_COEF to be setto -1 to indicate liquid, and the flow rate needs no correction.

The module computes flow rate using the equation

Rate = CD * Ev * Y * Ext

For any single module execution, the Ev, Y, and Ext factors are con-stants, but CD and Rate are variables.

The final flow rate is obtained by starting with a 'trial' CD value anditerating until the CD value is stable, at which point both the CD andflow rate are known. When the DEVICE terminal is 1 to 4, CD is


Page ISO5167-10


b

computed using the 1980 method (Stoltz equation); when the DEVICEis 5 the 1998 Amendment method is used.

When the original version of the ISO5167 Module was used for liquidmeasurement, there was no way to make the module use 1.0 for Y, sothe module calculated a flow rate on the OUTPUT (Qx) terminal thatwas INCORRECT for liquids by the value of the Y factor. The Yfactor was accessible to the user, however, because the CD, Ev, Y, andExt factors are stored by the module in a user specified signal list.

Correct liquid flow rate could be determined by dividing the final flowrate (as reported by the module on the OUTPUT (Qx) terminal) by thevalue of Y. The division correction could be performed using a Calcula-tor Module statement.

Beginning with PLS04.40 ACCOL firmware, the ISO5167 Moduleallows ISEN_COEF to be set to -1 in which case the Y factor is set to1.0 internally.

In summary, to use the older revision ISO5167 (pre-PLS04.40 firm-ware) to calculate liquid flow rate, the user must:

1) Leave the ISEN_COEF terminal unwired.2) Provide a valid signal list number on the LIST terminal.3) Provide a valid signal in this list to hold the value of the Y

factor.4) In a Calculator Module, divide the value of the OUTPUT

(Qx) terminal by the value of the Y factor to obtain thecorrect liquid flow rate.

With PLS04.40 (or newer) ACCOL firmware, you can calculate liquidflow rate using the ISO5167 Module by wiring the ISEN_COEFterminal and setting it to a value of -1.0 (valid for 1980 and 1998methods).


Page Keyboard-1

KeyboardKeyboard Module

The Keyboard Module allows control over a keypad or LCD displaydevice, such as those offered as options on the DPC 3330, RTU 3305,and GFC 3308 controllers. Depending upon which type of device issupported by a given controller, an operator may be able to changesignal data, or instead, may be limited to scrolling through lists ofsignal data. For details on available keypad/display options for a givencontroller, see the controller’s manual (document# CI-3330, CI-3305,or CI-3308-B for the DPC 3330, RTU 3305, or GFC 3308, respectively).DPC 3330 users should also consult the Display/Keypad Manual(document# D4085).

NOTE: The Keyboard Module should be placed in Task 0.

❏ Module TerminalsSELECT (1, 2, and 3) Default: None, entry required

Format: String signalInput/Output: Input

are string signals which provide text for the initial display. Thisdisplay is referred to as the Identifier Display if you are using theDPC 3330 keypad, or the Main Display if you are using the GFC 3308or RTU 3305. The text is defined for the display is defined via string

PASSWORD_WTPASSWORD_RD

TIMELISTSELECT_3SELECT_2SELECT_1

STATUSSTATE

FAIL_STATE

to Keypad& Display

INPUT n

3308 LCDor

Keyboard


Page Keyboard-2


signals. The value of the string signal entered on the SELECT 1terminal provides the text for the first line of the display; the value ofthe string signal entered on the SELECT2 terminal provides the textfor the second line of the display. For the DPC 3330, the value of thestring signal entered on the SELECT3 terminal provides the text forthe third line of the display; SELECT3, however, is NOT used by theGFC 3308 or RTU 3305. The maximum string length (including spaceand punctuation characters) varies depending upon the characterwidth of the display device. Some devices support 16 characters; otherdevices support 20 characters.

An example of using the SELECT terminals is shown below:

If the SELECT_1 terminal is 'wired' to a string signal namedKEYBOARD.SELECT.1, with a value of:

"WETWELL STATION1"

and the SELECT_2 terminal is 'wired' to a string signal namedKEYBOARD.SELECT.2, with a value of:

"ELM STREET"

then the first two lines of the initial display will appear as:

WETWELL STATION1ELM STREET

LIST Default: None, entry requiredFormat: Analog signal or constantInput/Output: Input

specifies the number of the ACCOL signal list which will serve as theScroll List/Scroll Display. When scrolling is activated for the keypador LCD display, the current data for each signal in this list (includingvalue and inhibit status) will be presented in order, one signal at atime. The period of time for which each signal's data will be displayedon the screen is determined by the value of the TIME terminal.


Page Keyboard-3


NOTE: If signal names are longer than can be supported on thedisplay device, the names will be truncated.

TIME Default: 2.0 secondsFormat: Analog signal or constantInput/Output: Input

is the amount of time in seconds that each signal in the Scroll List/Scroll display will appear on the display, when scrolling is active. Thevalue or signal name entered here should not be less than one second.

PASSWORD_RD Default: None, entry requiredFormat: Analog signal or constantInput/Output: Input

is the password for ‘read-only’ access. The password cannot exceed 6digits. This terminal does not apply to the GFC 3308. It alsodoes not apply to certain older versions of the RTU 3305.

PASSWORD_WT Default: None, entry requiredFormat: Analog signal or constantInput/Output: Input

is the password for read/write access. The password cannot exceed 6digits. This terminal does not apply to the GFC 3308 or certainolder versions of the RTU 3305. NOTE: The user will be logged offif the keyboard is inactive for a period of 20 consecutive minutes.

STATE Default: NoneFormat: Logical alarm signalInput/Output: Output

performs different functions depending upon which type of controlleris being used.


Page Keyboard-4


For the DPC 3330, DPC 3335, RTU 3310, and newer versions of theRTU 3305, the STATE terminal is set ON when a valid password isentered and set OFF when the operator has signed off. It is also setOFF if the keyboard is not used for a period of 20 consecutive minutes,while an operator is signed on.

For the older RTU 3305 units which do not support keyboards, or theGFC 3308 (with C.03 or later firmware) the STATE terminal is set ONwhenever an operator activates one of the buttons on the LiquidCrystal Display. If, after this signal is ON, neither button is pressedfor a period of 20 minutes, it is automatically turned OFF, and what-ever mode the LCD display device is in will remain active. For ex-ample, if scrolling was in progress, it will continue. This signal mayalso be turned OFF manually, for example, via Toolkit, or via ACCOLlogic.

NOTE: This terminal does not apply to GFC 3308 models with firm-ware earlier than C.03.

FAIL_STATE Default: NoneFormat: Logical alarm signalInput/Output: Output

is set ON after three invalid passwords have been entered consecu-tively and is turned OFF when the user signs off. In each case, analarm will be reported. This terminal does not apply to the GFC3308 or certain older versions of the RTU 3305.


assumes one of the status codes listed on the next page:


Page Keyboard-5


Code Meaning

-1.0 For 3330 - No display/keypad hardware detectedFor 3308 - LCD controller chip failureFor 3305 - No display device or BOTH display types detected

2.0 Waiting for a key press (or sensor input)3.0 Waiting for key press (or sensor input) or timeout4.0 Writing to display5.0 Writing to display6.0 Clearing LCD display

INPUT n Default: NoneFormat: Analog signal or constantInput/Output: Input

is a set of up to 255 terminals which may be used to define the ListMenu. The List Menu is activated at the display using the MENUoption. The user can then scroll through the names/numbers of signallists and choose individual lists to be displayed. The order seen at thedisplay is the order entered on the INPUT terminals.

Each INPUT terminal can contain a signal list number (Constant), ora signal name. If a signal name is used, the signal name will serve asthe title of the list, and the value of the signal is the ACCOL signal listnumber, e.g. signal name = CONFIG.LIST and the signal value = 10,means a title of 'CONFIG.LIST' will be used for signal list 10.

INPUT terminals should be used consecutively, that is, unwiredterminals should appear only after the last used INPUT terminal.Unwired terminals between wired terminals will use memory spaceand the message 'unwired input' will appear when that menu positionis displayed.

The individual signal lists defined in the List Menu can be of variablelengths and can contain any mixture of signal types.

BLANK PAGE

LCBOLocal Check Before Operate

ACCOL II Reference ManualPage LCBO-1

o EquipmentDPC-3330, DPC-3335, or RTU-3310 controller

CBO I/O Board (this item plugs into any I/O slot in the above units)

CBO Relay Module

o Module OperationThe Local Check Before Operate (LCBO) Module1 provides a reliabilitycheck on a single discrete output, either latched or pulsed, both going toand coming from the CBO board. Essentially an I/O module option, theLCBO Module accomplishes reliability checking for one of eight CBODiscrete Outputs using the associated feedback loops provided betweenthe CBO Board, the Relay hardware module, and the relay outputs.

Unlike typical I/O boards, the CBO I/O board has an intermediate step ofwriting the output state (ON/OFF) to the board rather than automaticallyoutputting it to the relays. This intermediate step, permits checking of theinternal board logic as well as the ribbon cable connecting the I/O boardand the CBO hardware relay module, prior to operating the relays.

The LCBO Module has 4 modes of operation—which affect automatic retryand automatic reset after errors. These are discussed in ‘Modes’, later inthis section.

In order to prevent conflicts between multiple LCBO modules, only onemodule can have access to a particular I/O point on a CBO board at anyone time. (This is also true if the other CBO-type module, HCBO, attemptsto access the point.) If another module attempts to access the point, it willnot be allowed access until the first module has either finished updatingthe I/O point, or has terminated with an error. If several CBO-type mod-ules are waiting to access the same point on the board, they are allowedaccess in a first-come, first-served order, except in

1. This module used to be called CBO prior to ACCOL version 5.7.

LCBO



the case of HCBO modules, which are given priority access over LCBOmodules.

As a further safeguard, during the reliability checking period (describedlater, under 'LCBO Reliability Checking'), the CBO I/O board may onlybe accessed by one CBO-type module; other modules attempting to accessthe board are locked out, and allowed access only in the order describedearlier.

When an LCBO Module executes, control will not be passed to the nextACCOL module in its task until it has either:

a) gained immediate access to the board and updated the desired I/Opoint,

b) determined that another CBO-type module already has access to theboard, i.e., it is temporarily locked out, or

c) the module terminates with an error.

NOTEIf an LCBO Module attempts to access the CBO I/O board,but is locked out by another module, the desired I/O pointupdate will occur in the first-come first-serve order, whetheror not the LCBO Module is executed again. If the module isnot executed again, however, the STATUS terminal will stillindicate that the module is waiting for access to the board(STATUS = 5), and the TRACK signal may not reflect thecurrent state of the hardware, even though the desired I/Opoint update has already occurred. To prevent this discrep-ancy, it is recommended that the LCBO Module be executedperiodically in order to ensure current values on its outputterminals.



oÿLCBO Reliability CheckingTwo separate operations called ‘Select-Check’ and ‘Operate-Check’ providereliability checking as described below:

A. Select-Check

This is the first phase of the LCBO reliability checking. It verifies theintegrity of logic on both the I/O board and the Hardware Relaymodule, as well as the connecting cable between them. First, thestate, as determined from the LCBO Module’s OUTPUT terminal, iswritten to the specified point in the Select DO Latch hardware. Thisoperation includes the current state of the other hardware pointsmerged with the latest state for the module’s point. The data justwritten to the hardware is then compared to the corresponding dataread back from the Select DO Feedback Buffer. If there is no dis-crepancy, the operation proceeds to Step ‘B’ (see Operate-Check).

If the CBO I/O system task detects a discrepancy between the datawritten and the data read back, it reports a Select DO Readbackerror (-8 on the STATUS terminal) and an LCBO Module error ( code= -130) via the system error array. Depending on the LCBO ModuleMODE (see section on Modes), the CBO I/O system task may auto-matically reset the I/O board. The reset turns off all outputs and de-energizes the relays. Following a Select DO Readback Error, futureaccess to the I/O board from this module is inhibited until specificactions occur, discussed later under Modes. Note that the Select-Check relates to all 8 points on the CBO board.



B. Operate-Check

This is the second phase of the LCBO reliability checking and onlytakes place after successful completion of the Select-Check phase.This part of the reliability checking uses feedback from the relaycontacts and relates to only the status of the point being controlledby the active module.

In Operate-Check, the CBO I/O system task ensures that the voltageenable to the relays is on and activates the hardware to write theoutput state from the Select DO Latch on the I/O board to the Oper-ate DO Latch on the Hardware Relay module. From there, theoutputs are routed to the relay drivers to control the relay positions.After a delay for the relays to settle (the delay period defaults to 25milliseconds, or is user-configurable using the DELAY terminal), theCBO I/O system task reads the Relay Contact Feedback Buffer andcompares the state for the module’s output point to the desiredoutput state. If there is no discrepancy and the output is latched, therequest completes successfully and the CBO board is released foraccess by other users. If the output is pulsed, all points on the CBOboard are released, except for the point being pulsed. The LCBOmodule continues to monitor the status of the output until the pulsecompletes and the output is returned to its previous state, or until aCANCEL command is executed.

If the CBO I/O system task detects a discrepancy between the statewritten and the state read back, it reports a Relay Contact Feedbackerror (-9 on the STATUS terminal) and an LCBO Module error (errorcode = -130) via the system error array. Depending on the LCBOModule MODE (see section on 'Modes' ), the module may automati-cally reset the I/O board. The reset turns off all outputs anddeenergizes the relays. Following a Relay Contact Feedback Error,



future access to the I/O board from this module is inhibited untilspecific actions occur, discussed later under 'Modes'. As statedearlier, the Operate-Check relates to a single point on the CBOboard.

NOTE:The delay for settling of the relays will default to 25 ms if theDELAY terminal is unwired, or invalid.

oÿModesThe concepts of 'Retry' and 'Reset' must be understood before proceedingto the discussion of the four modes:

Retry

Once an LCBO Module encounters one of the errors listed below, it isinhibited from future access to the CBO board until specific actionsoccur. The actions which are inhibited include updating the module’soutput point, as well as issuance of a RESET command. The specificactions which cause access to the board to be retried are:

1) A power failure or board replacement occurs and automatic RE-TRY is enabled (MODE = 1 or 3).

2) A CLEAR ERROR command is issued (COMMAND terminal = 5).

The term RETRY in the MODE truth table (described later in this sec-tion) therefore refers to automatic re-execution of an LCBO Modulefollowing a power failure, or board replacement when the module is in oneof the following error states.



Code Meaning-3 Device Error

-6 Reset Command Executed by this Module

-8 Select-Check Error

-9 Operate-Check Error

-14 Power Lost or Board Replaced/Removedbetween the Select and Operate functions

See the STATUS terminal description for more details on the individualerrors.

When automatic RETRY is not enabled (MODE = 2 or 4), the only way tore-execute following one of the above errors is to issue the CLEAR ERRORcommand.

Reset

Reset refers to disabling the CBO hardware which includes turningall points OFF and de-energizing the relays. A reset can be done byissuing a RESET Command (COMMAND Terminal = 4) or can bedone automatically when certain errors are detected (MODE=1 or 2).The term RESET in the MODE truth table therefore refers toautomatic disabling of the CBO hardware in conjunction with detec-tion of one of the following errors:

Code Meaning

-8 Select-Check Error

-9 Operate-Check Error

-14 Power Lost or Board Replaced/Removedbetween the Select and Operate functions



When automatic RESET is not enabled (MODE=3 or 4 on all LCBOModules for a CBO board), the only way to reset the board is to issue theRESET command. However, the RESET command can only be executed if:

1) The LCBO Module has not encountered one of the errors listed aboveunder RETRY.

2) The LCBO Module has one of the errors but automatic RETRY isenabled (MODE=3) and a power failure or board replacement occurs.

Effect of Reset on other LCBO Modules for the Same Board

Whenever a board is reset, either by command or automatically because ofan error, the point associated with the reset is flagged internally as failed.As long as this failure condition exists, all other LCBO Modules for pointson the same board will be blocked from access to the hardware and willreport a Status of -15.

To clear this failure condition and re-enable the voltage to the relays, theLCBO Module for the failed point must re-execute successfully. Re-execution when certain error conditions are present is controlled byMODE or by COMMAND (see the section on RETRY above).

oÿMODE DescriptionsRefer to the truth table and text which follows to learn about the fourpossible LCBO Module modes.



LCBO MODE TRUTH TABLE

Mode Retry Reset

1 YES YES

2 NO YES

3 YES NO

4 NO NO

MODE 1 - AUTOMATIC RETRY AND AUTOMATIC RESET

In this mode, the LCBO Module will automatically re-execute following apower failure or board replacement, if it is in one of the error conditionsdescribed previously under RETRY. It will also re-execute if the CLEARERROR command is issued. In this mode, the LCBO Module will alsoautomatically reset the CBO board following detection of one of the errorconditions described previously under RESET. Once an inhibiting errorcondition is present, a reset command will only be executed following apower failure or board replacement.



MODE 2 - NO RETRY AND AUTOMATIC RESET

In this mode, the LCBO Module will only re-execute after encounteringone of the errors described previously under RETRY if a CLEAR ERRORcommand is issued. In this mode, the LCBO Module will automaticallyreset the CBO board following detection of one of the error conditionsdescribed previously under RESET. It will not execute a RESET commandif an inhibiting error condition is present.

MODE 3 - AUTOMATIC RETRY AND NO RESET

In this mode, the LCBO Module will automatically re-execute following apower failure or board replacement, if it is in one of the error conditionsdescribed previously under RETRY. It will also re-execute if the CLEARERROR command is issued. In this mode, the LCBO Module will notautomatically reset the CBO board following detection of one of the errorconditions described previously under RESET. It will only do a reset if theRESET command is issued. Once an inhibiting error condition is present,a RESET command will only be executed following a power failure orboard replacement.

MODE 4 - NO RETRY AND NO RESET

In this mode, the LCBO Module will only re-execute after encounteringone of the errors described previously under RETRY if a CLEAR ERRORcommand is issued. In this mode, the LCBO Module will only do a reset ifthe RESET command is issued and no inhibiting error condition ispresent.

CHOOSING LCBO MODES

In general, all points on a single CBO board should be set for the samemode. The selection of the mode value depends on the application. Forexample, if you want all 8 relays to go to their deenergized state if any



one relay fails, use a mode with automatic RESET on all 8 modules. If all8 outputs are independent applications and you do not want failure of anyone relay to affect the others, use a mode with NO RESET on all 8 mod-ules.

Note: A hardware failure resulting in a Select-Check errorwill affect all associated modules because the check includesthe state of all 8 points.

Mixing mode values on LCBO Modules which access the same board canaffect execution of the different modules. For example, if only one of themodules is set for automatic RESET on error, an error on that point willblock access to the board by the other modules until the point that failed iscorrected, even if the other modules experienced no errors and the modeswere set for NO RESET.

Selection of RETRY or NO RETRY again depends on your application. Theusual correction of a CBO hardware error would be replacement of theCBO I/O board, or the hardware relay module, and/or the connectingcable. If you want the LCBO Module to begin controlling the state of itsoutput as soon as the new board is installed and the unit is powered up,set the mode for RETRY. If you want the output to remain OFF until youissue a CLEAR ERROR command, use a mode with NO RETRY.

The NO RETRY modes allow you to make any adjustments to your appli-cation or external process prior to reenabling automatic control aftercorrecting a CBO hardware failure.



Note: HCBO activity may affect the above mode operations,particularly if the RESET option (mode 1 or 2) or the RESETcommand is used to shut down the board. HCBO activitynever resets a CBO I/O board, but always automaticallyclears any previous error status for the point(s) being selectedby HCBO. It can also, under control of its ERROR_CLEARterminal, clear all errors at a CBO I/O board. An LCBOModule which resulted in a RESET (either by command orAuto-Reset on error mode) will operate as previously de-scribed, however the I/O board can be reactivated and re-execution of other LCBO Modules normally inhibited by thisstate (other LCBO Module status = -15) can occur based onHCBO actions.

oÿModule Terminals

DEVICEPOINTMODECOMMANDENABLEOUTPUTDELAYTIMEOUT

LCBO TRACK

STATUS


is the slot number into which the board is installed. See 'Process I/O' later



in this manual for information on how many boards a particular 33XXcontroller can hold.

POINT Default: 1Format: ConstantInput/Output: Input

is the digital output point on the CBO board selected. Valid values rangefrom ‘1’ through ‘8’.

MODE Default: 1 (Automatic Retry & Reset)Format: Analog Signal or ConstantInput/Output: Input

is an analog signal or constant used to set the operating mode of thismodule. If unwired, the module will operate in Mode 1.

The possible values for ‘MODE’ are 1-4 as described in the earlier sectionon 'Modes'.

COMMAND Default: None - Signal RequiredFormat: Analog SignalInput/Output: Input/Output

is an analog signal used to override the normal operation of the module.The terminal will be automatically set to zero after the command isexecuted. If the COMMAND and/or OUTPUT terminal is unwired, themodule does not execute (status = -12).



The COMMAND codes are as follows:

Code Meaning

0 No Special Operation

3 Dequeue/Cancel Removes the module from thequeue if it is waiting to acquire access to the CBOI/O board, or cancels an active pulse.

4 Reset command. Shuts down all outputs on theCBO board. This operates at the board level. All 8points are reset. This action will be reflected inthe status of all associated LCBO Modules. TheReset command can only be executed if no errorshave been detected, or if the mode is 1 or 3(Automatic RETRY). See the section 'Reset' in'Modes'.

5 Clear error in LCBO Module. This will cause themodule to re-execute after certain errors havebeen reported. See the section 'Retry' in 'Modes'.

ENABLE Default: ON (Enabled) if UnwiredFormat: Logical SignalInput/Output: Input

is a logical signal used to selectively enable or disable the execution of themodule. If it is unwired the default is enabled. If disabled (value ‘OFF’) themodule will not access the board or be put on the queue. If the module isalready on the queue it will stay on the queue until it has control of theCBO board and will then exit and be removed from the queue withoutaccessing the board.



OUTPUT Default: None - Signal RequiredFormat: Logical SignalInput/Output: Input

is a logical signal used to control the CBO DO field wiring terminaldefined by the POINT terminal. The possible values are ‘OFF’ and ‘ON’. Ifthe OUTPUT and/or COMMAND terminal is unwired, the module doesnot execute (status = -12).


is an optional logical signal which tracks the state of the CBO DO fieldwiring terminal.

DELAY Default: 25 msFormat: Analog Signal or ConstantInput/Output: Input

is an analog signal or constant which, if wired, provides a time delay, inmilliseconds, to allow the relays to settle after an operation before theOperate-Check is performed. If unwired (or <0 or >65,535) a default timeof 25 ms will be used.

PULSE Default: 0.0 (latched output)Format: Analog SignalInput/Output: Input

is an analog signal which determines if the output at the CBO DO fieldwiring terminal is latched or pulsed, and specifies the pulse length inseconds. If the terminal is unwired, or if the signal value is 0.0 or outsideof the valid pulse range, the output will be latched. It will retain the stateindicated on the OUTPUT terminal until it is changed by a subsequent



LCBO Module execution, or by HCBO activity.

For a pulsed output, the signal specifies the ON time of the pulse inseconds. A value of 0.1 specifies the minimum pulse of 1/10 of a second, or100 milliseconds. The maximum pulse is 1310.7 seconds. A pulsed outputis set ON then automatically set OFF when the pulse period expires.

Note: The pulse length only applies to the ON state. When theOUTPUT terminal state is OFF, the output at the CBO DOfield wiring terminal defaults to latched.

A pulsed output originated by an LCBO Module can be cancelled bysetting the signal at the COMMAND terminal of that module to 3(dequeue/cancel).

Note: A pulsed output can be affected only by a CANCELcommand from the originating module, or by LCBO Moduleactivity for a different point which results in a reset of theboard.


is an analog signal which provides module status and error indications.The successful completion of a LCBO Module is indicated by a 0 value. Anerror is indicated by a negative number.

The LCBO Module MUST be executed periodically for the STATUS signalto be updated.

The possible STATUS values are as follows:



Code Meaning

5 Module is queued and waiting for access to theboard

4 Module gained access to board

3 Select Check complete

2 Relay Delay Active (Operate Command com-pleted; waiting to do Operate-Check)

1 Pulse active (applies to pulsed outputs only)

0 Module completed successfully

-3 No board, or wrong board, in slot selected byDEVICE

-4 Invalid mode selected (not = 1-4)

-6 Reset command executed

-8 Select DO Readback error

-9 Relay Contact Feedback Error

-10 Module canceled by user (Removed from queue)

-12 Invalid terminal configuration (OUTPUT orCOMMAND terminal unwired)

-14 Power was lost or a board replaced during moduleexecution

-15 Another module has an error and has reset theCBO board

-16 Invalid command selected

-17 Point is disabled from ENABLE terminal



oÿRelationship of PULSE to TRACK SignalThe TRACK signal is set following a successsful Operate-Check (at the endof the relay delay period) for a latched output, or for both the leading edgeand trailing edge of a pulsed output. Because of the relay delay time, thestate at the TRACK signal will trail the actual field output by a timewhich is within the relay delay period. A pulsed output is illustrated in thefollowing figure.

Field Output

TRACK

PULSE

CBO board

Relay responds, actual field output turned ON

’Operate’ Command to activate point on CBO board, timing of pulse begins

’Operate-Check’ performed; if successful, TRACK turned ON

Pulse timer expires, ’Operate’ command

Relay responds, field

’Operate-Check’ performed;

2

1

3

4

5

6

DELAY period

Period between ’Operate’ and ’Operate-check’(as defined on DELAY terminal). Relay responds at somemoment within this delay period

TRACK turned OFF

to turn off point on board issued

output turned OFF

if check successful,

relay

BLANK PAGE


Page Lead/Lag-1

Lead/LagLead/Lag Module


The Lead/Lag Module adds a controlled delay effect to an input signaleach time it changes value. The module utilizes a derivative timeentry to achieve a lead-type output correction, and an integral timeentry to achieve a lag-type output correction. It is typically used forapplications such as filtering, feed forward control, or process model-ing.

Module Terminals

INPUT

is an analog signal or value to which a lead or lag function will beapplied.

DERIVATIVE

is the amount of lead time in minutes for the correction to occur aftera change of input.

INPUT

INTEGRAL

DERIVATIVE

OUTPUT

RESET

LL


Lead/Lag


Page Lead/Lag-2


INTEGRAL

is the lag time (in minutes) required for the correction to occur after achange of input. The lag time must always be greater than the rateexecution interval of the module. For example, if the module is ex-ecuted every 6 seconds, the lag time entry must be greater than0.10000000 minute. (0.1 minute = 6 seconds).

A value for this terminal must be specified for any lead/lag operationto take place. If, instead, INTEGRAL is left at zero, the value of themodule OUTPUT terminal will be set equal to the value of the moduleINPUT terminal. This is equivalent to turning on the RESET termi-nal.

RESET

can disable the lead/lag function. When this signal is turned OFF, themodule provides lead/lag capabilities. When turned ON, the feature isdisabled and the module output always equals the module input.

OUTPUT

is the output of the module.





Page Lead/Lag-3


Principles of Operation

This module acts upon a change of the input variable in such a waythat it delays the rate of output adjustment as shown by the graphs inthe following figure. The top part of this illustration shows the moduleterminals utilized for a lead function. In this configuration, an analogvalue is applied to the DERIVATIVE terminal to assign the amount oflead time correction (in minutes) that will be applied to the inputvariable.

The Input Change graph for the LEAD function shows the inputchange over a period of 6 minutes. From 0 to 2 minutes, the inputlevel remains at 5 units. At the 2-minute mark, the input variableexperiences a step change from approximately 5 to 15 units andremains at that level for the 6- minute duration.

The lead effect applied to this signal produces the curve shown on theOutput Change graph at the right. Initially, the output tracks theinput since the input has not changed value. However, when the stepinput change occurs at 2 minutes, the output jumps sharply fromapproximately 5 to 25 units. From this peak, the output decays gradu-ally over time until, at 6 minutes, it is at the 15-unit level. The outputwill remain at that level until the next input change occurs.

Should another input change occur before the output has been cor-rected, the module output will respond to the new change accordinglyfrom any point in the decay curve.

It will be noted that the output change from 5 to 25 units is muchgreater than the 5 to 15 unit input change that caused it. This is dueto the value of DERIVATIVE time applied to the module. The longerthis time period is, the greater will be the output peak when a stepchange occurs. This initial increase in output is required because themodule output can only decay from a value that is greater than thechange that produced it.


Page Lead/Lag-4


The graphs and module configuration for the LAG function are shownbelow the LEAD function in the figure. For ease of comparison, theInput Change graph for this function has the identical step change (5to 15 units) as shown above for the LEAD function. However, whenthe lag effect is applied to this signal change, it produces the outputcurve shown at the right.

15

30

2 4 6

15

30

2 4 60time (min)

OUTPUT CHANGE

INPUT

DERIVATIVE

OUTPUTLL

LEAD FUNCTION

INPUT CHANGE

0

15

30

2 4 6

15

30

2 4 60time (min)

OUTPUT CHANGE

INPUT OUTPUTLLLAG FUNCTION

INPUT CHANGE

0

INTEGRAL

time (min)

time (min)


Page Lead/Lag-5


Initially, the output tracks the input for a period of 2 minutes. Whenthe step input change occurs at the 2-minute mark, the output beginsto rise at a slower rate over the period from 2 to 5 minutes. At thispoint, the output has caught up to the input value (15 units) and thecurve levels off. The output will remain at that level until the nextinput change occurs. Note that the longer the time entered at theINTEGRAL terminal, the more gradual the slope will rise.

Should an input change occur before the output has risen to the inputlevel, the module output will respond to the new change accordinglyfrom any point within the curve.

The equation performed by the Lead/Lag Module is as follows:

where:INPUT = Change of input signalTlead = Lead time (DERIVATIVE terminal)Tlag = Lag time (INTEGRAL terminal)t = Time periode = ExponentialOUTPUTt = Change at output

OUTPUTt = INPUT * 1 +

-t Tlag* e

Tlead - Tlag

Tlag

BLANK PAGE

ACCOL II Reference ManualPage Liquid_Density-1

Liquid_DensityLiquid Density Calculation Module

The Liquid_Density Module calculates the density of a liquid atflowing conditions. Several different methods for calculating thedensity are supported. The choice of method is made via the MODEterminal.


This Module contains several alternate methods to calculate liquiddensity. The intent is to provide multiple methods so that the user canselect the most appropriate for the particular application.

For the purposes of your ACCOL memory space utilization, pleasenote that ACCOL Workbench will allocate a 1024 byte space in anytask that contains a Liquid_Density Module. Only one space per taskis generated, no matter how many Liquid_Density Modules are withinthe task.

Use the MODE terminal to select which type of density calculationshould be performed. Based on the value for MODE, create a signallist referenced by the INPUT_LIST terminal which contains all of theinputs required by the chosen calculation method. Then create an-other signal list which is referenced by the OUTPUT_LIST terminal;the signals in the OUTPUT_LIST will store the results of the densitycalculation.

Liquid_Density


Page Liquid_Density-2




selects the method to calculate density. Descriptions of each method(mode) are included later in this section. The available methods areshown below:

��

INPUT_LIST Default: None, entry requiredFormat: Analog signalInput/Output: Input

is the number of the signal list that contains the input signals used bythis module to control the density calculation function identified bythe MODE Terminal. See the discussion of the particular MODE youchoose for information about what signals to include in the signal listreferenced by INPUT_LIST.

OUTPUT_LIST Default: None, entry requiredFormat: Analog signalInput/Output: Output

is the number of the signal list that contains the output signals gener-ated by the density calculation function identified by the MODETerminal. See the discussion of the particular MODE you choose, forinformation about what signals to include in the signal list referencedby OUTPUT_LIST.




indicates status and error conditions. Typically, negative valuesindicate configuration errors. Valid STATUS values include:

0 Calculation completed successfully.-1 Invalid mole fraction structure.-2 Invalid specie ID structure.-3 Bad structure number, array does not exist, or

array index out of bounds.-4 Invalid INPUT_LIST.-5 Invlaid OUTPUT_LIST.-6 Invalid dynamic module control block (MCB).

NOTE: This is an internal firmware error.-7 Invalid number of molecular species.-8 Invalid structure number.-9 Only array and list are valid selections.

-10 Attempt to take a square root of a negative number.-11 Calculated critical temperature is out of bounds.-12 Invalid units.-13 Attempt to divide by zero.-14 Invalid mole fraction sum.-15 Invalid molecular weight or negative characteristic

volume.-16 Unsupported calculation requested.-17 Too few singals in INPUT_LIST.-18 Invalid specie ID code.-19 MODE terminal unwired.-20 INPUT_LIST terminal unwired.-21 OUTPUT_LIST terminal unwired.-22 List item not an analog signal.-24 Bad density conversion.-25 Density is out of bounds.-26 Fluid is not entirely in liquid phase.-27 No answer exists using selected inputs.-28 Calculation is unable to converge.




-29 Invalid temperature.-30 Invalid number of terms.

-71 to -80 One or more signals in either INPUT_LIST orOUTPUT_LIST are of the wrong type.

-116 Divide by zero in TP-25 CTL calculation.-117 Temperature out of bounds in TP-25 CTL calcula-

tion.-118 Density out of bounds in TP-25 CTL calculation.-119 Fluid is not entirely in a liquid state.

❏ Mode 1 - COSTALD Method

If measured densities are not available, then the COSTALD*

(COrresponding STAtes Liquid Density) method may be employed tocalculate a density. COSTALD is an integrated method for estimatingdensities of nonpolar and slightly polar liquids and mixtures. Using aconstituent analysis of the flowing liquid, three constants per constitu-ent (known values for Characteristic Volume, Acentric Factor andCritical Temperature), and a measured temperature, COSTALD willcalculate an absolute density at Saturation Pressure. For the constitu-ent molecules described, COSTALD covers a reduced temperaturerange of 0.25< TR < 0.95. This correlation has shown a 0.446 averageabsolute percent error for 6,338 data points for nonpolar liquids,2.57% error for 1352 data points for polar and quantum liquids,0.369% error for 319 data points for LNG/LPG mixtures, and 1.61%for all mixtures tested. The COSTALD Method contains an allowancefor shrinkage which occurs when LNG/LPG components are mixedtogether to form LPG blends.

INPUT_LIST entries for MODE 1:

For MODE 1 (COSTALD), the INPUT_LIST signal list must beorganized as follows:

*G.H. Thomson, K.R. Brobst, R.W. Hankinson, "An ImprovedCorrelation for Densities of Compressed Liquids and LiquidMixtures," AICHEJ, 28(4) (1982) pp. 671-675.



Signal 1


is the temperature, in degrees Fahrenheit (Centigrade), of the liquidat flowing conditions.

Signal 2

NUMMOLETYPE Default: None, entry required (maximum of40)


is the total number of constituent molecule types composing the liquid.

Signal 3

STRUCTMODE Default: None, entry required.Format: Analog signalInput/Output: Input

selects whether the structures identified in the following terminals aresignal lists or data arrays.

1 Signal Lists2 Data Arrays (single-dimensional)




Signal 4


identifies the structure, of size NUMMOLETYPE, which specifies theset of molecular specie making up the liquid of interest. The userpopulates the structure, with specie ID codes (listed in the 'GPA8173Module' section) drawn from the BBIMSCT Table and optionally, bythe implied Species codes of the ACCOL Array specified by theCUSTCONSTARRY terminal. The Specie ID codes identify, for theModule, which constants in the BBIMSCT Table and in theCUSTCONSTARRY are to be used in computing the COSTALDresults.

Signal 5

MOLEFRACTSTRUCT Default: None, entry requiredFormat: Analog signalInput/Output: Input

identifies the structure, of size NUMMOLETYPE, which contains themole fraction values, one per structure element, for the constituentsmaking up the liquid of interest. The sum of the mole fractions of theset of NUMMOLETYPE elements must add up to exactly 1.0. Theelements of this structure parallel those in the SPECIDSTRUCT. Forexample, if the third element of the SPECIDSTRUCT contains theSpecie id code corresponding to Methane, then the third element ofthe MOLEFRACTSTRUCT must be populated with the value ofMethane’s Mole Fraction in the liquid.



identifies a read-only array which is populated with constants sup-plied by the user. This array is used to define molecular specie otherthan those defined in the BBMSCT (see 'GPA8173 Module' section).The CUSTCONSTARRY can also be used to specify different constants(e.g. legacy values) for molecular specie which are already defined inthe BBMSCT.

OUTPUT_LIST entries for MODE 1:

Signal 1

SATD_MOLAR_VOLUME Default: NoneFormat: Analog signalInput/Output: Output

is the calculated saturated liquid molar volume (l/mole), for the liquidof interest.

Signal 6

UNITS Default: None, entry requiredFormat: Analog signalInput/Output: Input

selects either Customary English or Standard International (SI) Unitsfor the FLOW_TEMP, SATD_PRESSURE and ABS_DENS terminals.

Customary English 1Standard International 2

Signal 7





Signal 2

SATD_PRESSURE Default: NoneFormat: Analog signalInput/Output: Output

is the calculated saturated pressure (psia or bar abs) for the liquid ofinterest.

Signal 3

ABS_DENS Default: NoneFormat: Analog signalInput/Output: Output

is the calculated saturated density (lbm/gal or kg/m3) for the liquid ofinterest, at flowing temperature and bubble point pressure.

❏ Mode 2 - Enhanced COSTALD MethodThe Enhanced COSTALD Method* , will predict the densities for 40“LNG-like” mixtures to an average absolute percent error of 0.078percent. The enhanced method is similiar to the original COSTALDcalculation, but includes “interaction parameters” in the calculation ofthe Mixture Reduced Temperature.


Signal 1, Signal 2, Signal 3 - These entries are identical to theSignal 1, 2, and 3 entries for MODE 1. See MODE 1 description forthese entries.

*Petroleum Measurement Manual, Part XII, Static and DynamicMeasurement of Light Hydrocarbon Liquids, Section 1, Calcula-tion Procedures, Page 24, Institute of Petroleum, U.K.



Signal 4


identifies the structure, of size NUMMOLETYPE, which specifies theset of molecular specie making up the liquid of interest. The userpopulates the structure, with specie ID codes (listed in the 'GPA 8173Module' section) drawn from the BBIMSCT Table and optionally, bythe implied Species codes of the array specified by theCUSTCONSTARRY terminal. The Specie ID codes identify, for theModule which constants in the BBIMSCT Table and in theCUSTCONSTARRY are to be used in computing the COSTALDresults.

The first nine entries of the Species Structure must be wired with thefollowing species and they must be in contiguous order. If any of thefollowing species are absent in the liquid of interest, set the value ofits Mole Fraction to zero.

��

� �� !��" �#�$%��& $%��' �#�$ ��( $ ��) ��*��

Signal 5 - This entry is identical to the Signal 5 entry for MODE 1.See MODE 1 description for this entry.




Signal 6


identifies a read-only array which is populated with constants sup-plied by the user. This array is used to define molecular specie otherthan those defined in the BBMSCT (see 'GPA8173 Module' section).The CUSTCONSTARRY can also be used to specify different constantsfor molecular specie which are already defined in the BBMSCT. NOCHANGES should be made, however, to the first nine entries in theSPECIDSTRUCT. (See Signal 4 description for details.)


These entries are identical to the OUTPUT_LIST entries for MODE 1.See the description for MODE 1.

❏ Mode 3 - GPA TP-25 Table 23EThis mode implements the Table 23E Standard as published in theGas Processor Association, Technical Publication TP-25 (September,1998). This Standard takes two inputs, the observed temperature (oF)of a fluid and the relative density at that temperature. It generatesthe relative density of the fluid at 60 oF. The Standard covers a 60 oFrelative density range of 0.3500 to 0.6880. The temperature range ofthis standard is -50.0 to 200 oF. At all conditions, the pressure isassumed to be at saturation conditions.



If a Glass Hydrometer was used to perform the observed relativedensity measurement, then this mode permits the user to apply acorrection to the observed relative density, for the effect of tempera-ture on the Glass Hydrometer. The method is described in the Stan-dard.


Signal 1


is the temperature, in degrees Fahrenheit, of the liquid at flowingconditions, within the range -50 to 200.

Signal 2

RD_AT_FLOW Default: None, entry requiredFormat: Analog signalInput/Output: Input

is the observed relative density in the range 0.3500 to 0.6880.

Signal 3

GLASS_CORRECTION Default: OFF, correction not requiredFormat: Logical signalInput/Output: Input

is used when observed densities are determined by a glass hydrom-eter. Glass hydrometers require correction for the effect of tempera-ture on the instrument. If wired and set ON, a correction will beapplied to the RD_AT_FLOW value.





There is only 1 entry in the OUTPUT_LIST for MODE 3.

Signal 1

RD_AT_60F Default: None.Format: Analog signalInput/Output: Input

is the calculated relative density at 60 degrees Fahrenheit.

ACCOL II Reference ManualPage Liquid_Measure-1

Liquid Measurement GuidelinesGuidelines For Using the Liquid Measurement Module Suite

The liquid measurement module suite consists of five (5) differentmodules. Those modules are:

Module Name DescriptionAGA3Dens American Gas Association Report Number 3 Density

ModuleEVP Liquid Equilibrium Vapor Pressure ModuleGPA8173 Gas Processor’s Association Standard 8173-94

Volumetric Flow Measurement ModuleGSV Gross Standard Volume ModuleLiquid_Density Liquid Density Calculation Module

Details on using these modules are included in their associated sec-tions, elsewhere in this manual. In addition to the information inthese other sections, various restrictions and caveats should be ob-served when using these modules:

� The calculations of many of these modules are based on ‘best fit’correlations of experimental data derived from select sets of liquids.Select sets are employed, as it is impractical to experimentallycharacterize all the possible combinations of molecule types andtheir respective concentrations that could be present in a liquidmixture. If the select set(s) are chosen carefully, then a workingassumption is made that liquid mixtures containing similar, but notexactly the same, molecules and concentrations may be character-ized by these correlations. The user is strongly cautioned that thismay not be a correct presumption, and that the user’s liquid mayshow significant deviations along part or all of the “best fit” line. Itis the user’s responsibility to take these factors into account whendeciding whether the liquid to be measured can be characterizedaccurately by these correlations. It is strongly recommended thatthe user calibrate the flow measurements reported by these ACCOLmodules against known standards.

� When measuring the flow of a fluid, the user must ensure that thefluid is entirely in a liquid state.

� All sensors and transmitters, at a minimum, are to meet the cali-

Liquid Measurement Guidelines


Page Liquid_Measure-2

Liquid Measurement GuidelinesGuidelines For Using the Liquid Measurement Module Suite

bration specifications set forth in the Manual of Petroleum Measure-ment Standards, Chapter 21, Flow Measurement Using ElectronicMetering Systems, Section 2, Electronic Liquid Volume Measure-ment Using Positive Displacement and Turbine Meters, First Edi-tion, June 1998. The uncertainty calculations in this chapter arebased on secondary inputs (e.g. transmitters) sampled at a mini-mum of once every five seconds.

� For volumetric calculations, the dynamic inputs (e.g. flowingtemperature, flowing pressure, etc.) must be sampled at least every5 seconds.

� During no-flow conditions, and conditions where a fluid is notentirely in a liquid state, input variables may continue to besampled, and displayed for monitoring purposes, but the usershould not include these values in calculations (e.g. accumulations,averages, etc.)

� To maximize calculation precision, wherever possible, internalnumerical calculations are performed, and carried in double preci-sion. Calculation results are converted to single precision numberswhen output by the module.

LLANINRLLANIN

Low Level Analog Input and Remote Low Level Analog Input Modules


Page LLANIN-1

The Low Level Analog Input Module accepts input signal data from aLow Level Analog Input (LLAI) Board within the controller andmakes these signals available to other ACCOL modules. The inputsignals of the LLAI board are called “low level” because they comefrom electrical devices with low voltage levels such as thermocouplesand resistance temperature devices.

LLANIN Module Symbol

RLLANIN Module Symbol

Input from the Low Level

SPAN

ZERO

INPUTAnalog Input Board

(% of scale or C)0LLANIN

DEVICE

INITIAL

Input from the Low Level

SPAN

ZERO

INPUTAnalog Input Board

(% of scale or C)0RLLANIN

STATUS

DEVICE

INITIAL

See also: Questionable Data Process I/O

LLANIN/RLLANIN

LLANINRLLANINLow Level Analog Input and Remote Low Level Analog Input Modules


Page LLANIN-2

The RLLANIN (Remote Low Level ANalog INput) Modules alsoreceive data from LLAI boards, but only from those boards whichreside within an RIO 3331 Remote I/O Rack.

Terminal assignments for the LLANIN and RLLANIN Modulesdepend on the type of input received by the LLAI Board. ZERO andSPAN terminals modify or scale the signals coming from the LowLevel AI Board. For thermocouples and RTD inputs, the board sendsthe module a signal whose value is in units of degrees Celsius. TheZERO and SPAN terminals of the LLANIN or RLLANIN Module canthen be used to convert the signal to other temperature scales. Forvoltage inputs, the input signal is a value from 0.0 to 1.0 and repre-sents a percentage of scale. It can be converted to engineering units bythe ZERO and SPAN terminals.

❏ Module TerminalsDEVICE (LLANIN) Default: 0 (null device) Specifying DEVICE

0 will result in a device error beingreported when the module isexecuted; no signal processing willoccur.


is the slot number of the Process I/O Board where the low level AIsignals reside. The entry at this terminal will be a number from 1 to12, depending on the type of the target node and the number of boardsinstalled in it.

If you are using the AIC, the Process I/O Board Menu must define aLow Level AI Board before this entry will be accepted. (This menu isexplained in the ACCOL II Interactive Compiler Manual, D4042.) Ifyou’re using the ABC, or ACCOL Workbench, a Low Level AI Boardmust be defined in the *PROCESS-I/O section.

LLANINRLLANIN



Page LLANIN-3

DEVICE (RLLANIN) Default: 0 (null device) Specifying DEVICE0 will result in a device error beingreported when the module isexecuted; no signal processing willoccur.


is a three digit number which identifies the RIO 3331 process I/Oboard. There can be up to ten RIO 3331 nodes connected to a commu-nication port of a 3310/3330/3335 controller, and each RIO 3331 canhold up to ten process I/O boards — therefore up to 100 boards can bereferenced through a given communications port.


Valid DEVICE values range from 100 through 499. Use the followingrules to generate a number for the DEVICE terminal.

The first digit indicates the serial port on the 3310/3330/3335 control-ler which is receiving inputs from RIO 3331 node.




Page LLANIN-4

The second digit must be one less than the RIO 3331 node addresswhere the board resides. It must range from 0 to 9. (Second digit = 0for node address 1. Second digit = 9 for node address 10.)

The third digit must be one less than the board slot. It must rangefrom 0 through 9. (Third digit = 0 for slot 1. Third digit = 9 for slot 10.)

Examples:



The number entered on the DEVICE terminal will be verified with theProcess I/O Menu (if you’re using the AIC) or the *PROCESS-I/Osection (if you’re using the ABC or ACCOL Workbench). This boardmust be capable of accepting low level analog input signals. If noboard is found in the specified slot or if the board is the wrong type, anerror message will be generated.


is the number of the field wiring terminal that will be assigned to thefirst set of LLANIN or RLLANIN Module terminals. All subsequentterminals entered on this menu will automatically be sequenced fromthe initial number. For example, if 2 is the INITIAL entry, thenterminal set #1 corresponds to field terminal LAI2 of the device andterminal set #2 corresponds to field terminal LAI3.

LLANINRLLANIN



Page LLANIN-5

STATUS (RLLANIN) Default: None, entry is optionalFormat: Analog signalInput/Output: Output

assumes one of the module execution codes specified below.

Code Meaning0 Module executed successfully

-1 Invalid remote device ID-2 Communication failed with remote unit-3 Remote board is missing-4 Remote board is of the wrong type-5 The remote board failed diagnostic tests-6 Remote board not ready-7 RIO Rack firmware incompatible with process I/O configured


INPUT Default: None, entry requiredFormat: Analog signalInput/Output: Output

is the output of this module which other modules can reference. Itrepresents the low level analog signal as modified by the Low Level AIBoard and this LLANIN or RLLANIN Module.

ZERO Default: 0Format: Analog signal or constantInput/Output: Input

scales the output. For the Low Level Board voltage type inputs, this isequivalent to the 0% value of the input range. For example, for a +10mV signal that corresponds to a 0 to 1000 rpm range, set the ZEROterminal to 0.



Page LLANIN-6

For the Low Level Board temperature type inputs (thermocouples orRTD), the output will be in degrees Celsius if ZERO and SPAN are notspecified. To convert to degrees Fahrenheit, ZERO should be set equalto 32. For other temperature scales, enter a value here which corre-sponds to 00C.


represents the 100% value of the input range. The output of thismodule which appears on the INPUT terminal will be equal to theinput signal value from the Low Level AI Board times the span plusthe value on the ZERO terminal. In other words, INPUT = (boardinput * SPAN) + ZERO

For example, for a +10 mV signal that corresponds to a 0 to 1000 rpmrange, set SPAN equal to 1,000.

To convert a temperature signal to 0F, set SPAN equal to 1.8.

❏ Process I/OFor each signal from the LLAI Board, the LLANIN or RLLANINModule contains a set of three terminals: INPUT, ZERO, and SPAN.If more LLAI signals are required that can fit on a single module,another RLLANIN or LLANIN Module can be defined. It is notrecommended that separate modules be created for each LLAI input.Doing so will create unnecessary modules and slow down the opera-tion of the system. Assigning all LLAI signals from an LLAI Board toa single LLANIN or RLLANIN Module provides the most efficient useof execution time.

Before this module will function properly, you must have defined the

LLANINRLLANIN



Page LLANIN-7

type of input signals for the board. This is accomplished from the LowLevel AI Menu (if you are using AIC) or the *LOW-LEVEL section (ifyou are using ABC or ACCOL Workbench). Keep in mind as youdefine the input signals that low voltage and high voltage signalsshould not be intermixed. For more details on LLAI wiring, see theappropriate controller hardware manual.

The following table summarizes the types of signals that the LowLevel AI Board will accept. These include a resistance temperaturedevice (RTD), thermocouples, and voltage inputs.

For RDC 3350, UCS 3380, DPC 3330, DPC 3335, RIO 3331 andRTU3310 units:

Thermocouple Inputs: Type R -50 0C to +17200CType S -50 0C to +17600CType J -210 0C to +12000CType E -270 0C to +10000CType K -270 0C to +13700CType T -270 0C to +4000C

RTD: -2200C to +8500C

Voltage Inputs: -10 mV to +10 mV

For the RDC 3350 and UCS 3380 only:

Voltage Inputs -100 mV to +100 mV-1 V to +1 V-10 V to +10 V+1 V to +5 V

For the DPC 3330, DPC 3335, RIO 3331, and RTU 3310 only:

Thermocouple Inputs: Type B 1000C to +18200C



Page LLANIN-8

❏ Questionable DataFor information on questionable data for low level analog inputsignals, see the section 'Questionable Data' later in this manual.


Page Logger-1

LoggerLogger Module

The Logger Module allows the node to communicate with an externalASCII device. When it is used as an input/output device, the Loggerreceives and sends ASCII-coded messages via a CRT keyboard, termi-nal or similar device. When used as an output device, the Loggertypically sends formatted ASCII messages to a printer or CRT display.

❏ Module TerminalsPORT Default: None, entry required


is the port that will communicate with the external ASCII device. Useone of the codes below to indicate the appropriate port.

1 = Port A 6 = BIP 22 = Port B 7 = Port G3 = Port C 8 = Port H4 = Port D 9 = Port I5 = BIP 1 10 = Port J

Note: Ports BIP1, BIP2, G, H, I, and J may only be used as LoggerPorts if you have Protected Mode firmware (PLS00/PLX00 or newer).

MODETIMEOUT_INP

TIMEOUT_OUTLIST

FORMATDONE

STATUS

LOGGER

PORT


Page Logger-2

LoggerLogger Module

TIMEOUT_OUT Default: 0.0 (no timeout)Format: Analog signal or constantInput/Output: Input

is the timeout period in seconds to complete an output request. Thisnumber must be an integer. Fractional values are ignored. Values lessthan one are interpreted as zero which implies no timeout.

TIMEOUT_INP Default: 0.0 (no timeout)Format: Analog signal or constantInput/Output: Input

is the timeout period in seconds to complete an input request. Thisnumber must be an integer. Fractional values are ignored. Values lessthan one are interpreted as zero which implies no timeout.


sets the initial direction of module communications as shown below.

TRUE/ON = Set module to receive ASCII input dataFALSE/OFF = Set module to send ASCII output data

For Loggers performing I/O communications, the direction of signaltraffic is changed by directional commands appearing in formatstatements. If no directional commands are included in the Format, allsignal traffic will flow in the direction set at this terminal.

FORMAT Default: None, entry requiredFormat: Analog signal or constantInput/Output: Input

is the number of the associated Format. When it is created, a Formatmust be assigned a number for identification purposes. The number of


Page Logger-3

LoggerLogger Module

Formats available varies depending upon the amount of memory inyour unit, as well as the software and firmware versions you are using.

LIST Default: None, entry optionalFormat: Analog signal or constantInput/Output: Input

is the number of the associated signal list. (Leave this terminalunwired for event and alarm messages collected by the Audit TrailModule.)

DONE Default: NoneFormat: Analog or logical signalInput/Output: Output

indicates the completion of the format processing. If this terminalcontains an analog signal, its value will be incremented by 1 uponcompletion or termination of the format. If it is a logical signal, itsvalue will be set to FALSE/OFF when the format is initiated, and setto TRUE/ON when it is completed.

STATUS Default: None, entry is optionalFormat: Analog signalInput/Output: Output

provides a status code according to the following table. Zero indicatessuccessful completion of a format and a negative number indicates anerror. Warnings or comments are displayed as positive numbers.

Code Message

0 Format completed successfully1 Input signal is control inhibited2 Input signal is a constant3 Input string signal value truncated


Page Logger-4

LoggerLogger Module

4 Input data array is “read only”5 Conditional field descriptor does not apply to current signal

or cell.6 Signal is not an alarm signal

-1 Invalid logger device number-2 Invalid Format number selected-3 Invalid I/O Signal List selected-4 Attempt to use signal beyond end of list-5 Unsupported field descriptor-6 Too many levels of parenthesis-7 Unmatched right parenthesis-8 Subformat number does not exist-9 Too many levels of subformats

-10 Field descriptor invalid for input -11 Output signal type must be analog -12 Output signal type must be logical -13 Output signal type must be string -14 Output signal type must be analog or logical -15 Input signal type must be analog or logical -16 Input signal type must be string -17 Numerical field input invalid -18 Unexpected input signal store failure -19 Output I/O timed out -20 Input I/O timed out -21 Input I/O buffer overflowed -22 Input I/O parity error -23 Input I/O overrun error -24 Input I/O break detected -25 Input I/O framing error -26 Unexpected I/O failure -27 Q Format input value/signal type mismatch-28 Q Format input value bad or checksum error -29 Date input is invalid -30 Time input is invalid -31 Field descriptor is not valid for data array -32 Invalid data array selected -33 A data array has not been defined -34 Attempt to use cell beyond end of data array


Page Logger-5

LoggerLogger Module

-35 Special input mode may not be nested -36 Special input mode is not active -37 Special input mode is invalid for input mode -38 Indirect signal name is invalid-39 Audit Module event buffer empty (nEL, nEN, or EA de-

scriptors) at the start of the operation

SPARE

is an unused terminal.

❏ Signal Storage and FormattingThe input data received by the Logger Module may be stored in signalsor data arrays defined in the ACCOL load. Data contained in signals,data arrays, or the Audit Trail message area may be sent as outputdata by the Logger Module. A Format statement and Signal List areused to control the actual conversion of data to/from the externaldevice.

A Signal List can contain a maximum of 3,999 signals with eachsignal’s position identified by a number (1-3,999).* During operation,the Logger Module will sequentially access each signal in the list forprocessing. The order of selection is in ascending order, going from thelowest to highest position number.

Each Logger Module must be assigned a Format to specify source anddestination structures and to translate messages between the nodeand the ASCII device. Formats are created either on the FormatStructure Menu (if you are using AIC) or in a *FORMAT section of theACCOL source file (if you are using the ABC or ACCOL Workbench.Formats are implemented via coded descriptors, commands andspecifiers. See the'Formats' section, earlier in this manual, for details.

*Protected Mode units (PLS00/PLX00 or newer firmware)support longer signal lists.


Page Logger-6

LoggerLogger Module

When Logger Modules are entered in the ACCOL Task, they willtypically be part of an IF or WAIT statement so that execution willoccur as a result of a conditional test or time delay. If a Logger moduleis entered as an independent statement, it will execute at the taskrate. However, if a previous I/O transaction initiated by this module isstill active, no new transaction will be initiated. If the module termi-nals are being modified (e.g. to indicate a different list or format) theuser should also test for completion of any previous transaction toensure that the new values are processed.

The Logger interfaces with the ASCII device via the communicationports. These ports, which should be configured for RS423 communica-tions, are suitable for use with RS232 links as long as the line is keptunder a 15-foot length. The Logger can also be used on RS485 linkshowever there are special considerations which the user must beaware of when doing this. For more information on configuring LoggerPorts, see the 'Communication Ports' section.


Page Master-1

MasterEMaster

Master Module and Enhanced Master Module

Master and EMaster Modules initiate peer-to-peer communicationswith a Slave Module in another controller (node). This allows thetransfer of signal lists, and data arrays, from one node to another.

POINT

INTYPEOUTTYPEINDEXINLISTOUTLIST

MODE

REMOTE

Master

STATUS_1

STATUS_2

to Slave Module

POINT

INTYPEOUTTYPEINDEXINLISTOUTLIST

MODE

NODE_1

EMaster

STATUS_1

STATUS_2

NODE_2

ADDRESS

to Slave Module

The Enhanced Master (EMASTER) Module includes all the functionsof the MASTER Module and can be substituted for it. EMASTERsupports two features not available in the standard MASTER Module:

1) Using the NODE_1 and NODE_2 terminals, EMASTER allowspeer-to-peer communication through a standard Master Port tobe initiated with a SLAVE Module two levels below the nodecontaining the EMASTER module. This allows the EMASTER tocommunicate with the 'slave of a slave'. When using an ExpandedAddressing Master Port, this same feature allows a

See also: Master/Slave CommunicationsNode Addressing, Slave Module

Master/EMaster


Page Master-2

MasterEMasterMaster Module and Enhanced Master Module

master node to communicate with an EASlave node. (See 'Ex-panded Node Addressing', earlier in this manual.

2) EMASTER also displays, via the ADDRESS terminal, a stringrepresentation of the target node address, which may be eitherlocal or global. This allows the user to verify that the correct nodeis being accessed. (This is especially useful when using expandednode addressing.)

❏ Module TerminalsREMOTE Default: None, entry required(Master only) Format: Analog signal or constant

Input/Output: Input

is the local address of the controller containing the Slave Modulewhich will communicate with this Master Module. This number mustbe in the range of -127 to +127.

If the address entered is: Then node containing theslave module is:

0 The master node to thecurrent node.

1 to 127 A slave node of the currentnode.

-1 to -127 A sibling node of the currentnode; i.e., it shares the samemaster.


Page Master-3

MasterEMaster


NODE_1 Default: None, entry required(EMaster only) Format: Analog signal or constant

Input/Output: Input

is the local address of the controller containing the Slave Modulewhich will communicate with this EMaster Module. When theNODE_2 terminal is unwired or set to 0, then the NODE_1 terminalfunctions identically to the REMOTE terminal discussed above.

When the NODE_2 terminal is not 0, then NODE_1 must be a positivevalue in the range of 1 to 127 and it designates a node two levels belowthe current node in the network configuration (NETTOP file). See theNODE_2 description below.

NODE_2 Default: 0, if unwired(EMaster only) Format: Analog signal or constant

Input/Output: Input

is, when non-zero, the local address of a node between the currentnode and the node containing the Slave Module. This intermediatenode can be:

1) a virtual node associated with an Expanded Addressing Masterport on the current node. In this case, NODE_1 contains the localnode address of an Expanded Addressing Slave node configuredbelow the virtual node.

or

2) a slave node associated with a standard Master port on thecurrent node. In this case, NODE_1 contains the local nodeaddress of a slave node configured immediately below theNODE_2 node.

This number must be in the range of 1 to 127. Negative values are notvalid.


Page Master-4


ADDRESS Default: None(EMaster only) Format: String (min. length = 4)


is a string signal which will be set to the address of the destinationnode when communications are initiated. This node address will belocal (physical node address value 1 to 7F Hex) for Master Modulecommunication with a node at the next level below it via a standardMaster port. For all other cases this node address will be global andcan be checked against the NETTOP documentation file.

The string signal is cleared when the EMaster Module executes (i.e.,no previous communications are active). It is set to the destinationnode address only when communications are actually initiated, i.e. ifmodule detected errors prevent initiation of communications, thestring will remain cleared. Once communications are started, thestring will retain the destination node address as long as communica-tions are active. When communications are complete and the STA-TUS terminals are updated, the signal will again be cleared the nexttime the module executes.

POINT Default: None, entry requiredFormat: Analog signal or constantInput/Output: Input

identifies the Slave Module in the remote controller. The value mustbe in the range of 0 to 255. If the Master Module is being used tocommunicate with a TeleCorrector unit running a fixed "C" load, youmust enter the desired "C" load signal list number on this terminal.

MODE Default: 0Format: Analog signal or constantInput/Output: Input

is a code which represents the mode of communication. 0 = Send, 1 =Poll, and 2 = Send/Poll.


Page Master-5

MasterEMaster


For users with AJ.10 (C.03 for the GFC 3308) or newer level PROMs,the MODE value can also be configured with a number from 3 to 255.In this case, the MODE value indicates the number of a signal list,which must be defined in this ACCOL load, which is called the MODETimeout List. It is useful for applications which require the timeoutvalue to be other than the default value of 2 minutes. If this option isused, the MODE Timeout list must be defined as follows:

Signal 1- Analog signal which must indicate the MODE. This canbe one of the following:

0 Send1 Poll2 Send/Poll

Signal 2- Response Timeout value (in units of 0.1 minutes) If theMaster/EMaster Module does not receive a responsefrom a Slave Module by the time defined for this value,a timeout is reported. This analog signal value canrange from 0 to 255. If the value is less than or equal to0, or greater than 255, the response timeout will defaultto 20 (2 minute timeout.)

INTYPE Default: 0Format: Analog signal or constantInput/Output: Input

is a code which indicates the type of data structure specified on theINLIST terminal.



Page Master-6


OUTTYPE Default: 0Format: Analog signal or constantInput/Output: Input

is a code which indicates the type of data structure specified on theOUTLIST terminal.



is the signal in the list that will be sent. The number will correspondto a signal position in the list. Although signal lists may contain morethan 255 entries, INDEX cannot reference an individual signal posi-tion above 255. If 0 (zero) is entered, however, the entire list will besent. NOTE: Even if only a single signal is sent, the signal list sizes (#of signals in list) at both the Master/EMaster Module and SlaveModule must match.

INLIST Default: None, entry requiredFormat: Analog signal or constantInput/Output: Input

is the number of the signal list or data array which will receive therequested data from the Slave Module.


Page Master-7

MasterEMaster


OUTLIST Default: None, entry requiredFormat: Analog or constantInput/Output: Input

is the number of the signal list or data array which will be selected fortransmission to the Slave.

STATUS_1 Default: None, entry is optionalFormat: Analog or logical signalInput/Output: Output

indicates the completion of communications. If an analog signal isnamed, it is incremented by 1 upon completion. If a logical signal isused, it is cleared when the Master Module initiates communications,and set ON when the communications are complete.

STATUS_2 Default: None, entry is optionalFormat: Analog signalInput/Output: Output

is a status code which represents the completion or error status of therequested operation. This status is set upon completion of all commu-nications.

The following table lists the possible error conditions that can bedetected by the Master and Slave Modules. Positive number codesindicate warnings or informational messages, while negative numbercodes indicate errors which inhibit proper execution of the modules.

Along with each message, a letter indicates whether the error isdetected by a module routine (R), or a module task (T), and whether itis reported to the Master/EMaster Module (M) or the Slave (S), orboth. Whenever an error is detected by any component, the task ormodule will set the STATUS terminal of the module with the errorcode.


Page Master-8


Coded Error Messages

Code Detect Report Description

2 T M,S Signal was control inhibited or stringwas truncated

1 T M Slave has more data to send0 R,T M,S Successful completion

-1 R M,S Invalid mode (must be 0, 1 or 2). Thiscode may also appear if attempts aremade to communicate with pre-Sfirmware, or an incompatible device.

-2 R M Invalid slave node number. If NODE_1value is x and NODE_2 value isunwired, or zero, this error occursbecause of one or more of the followingreasons: a) x is not in the valid range of-127 to +127 b) x is positive, andgreater than the High Slave Addressconfigured for this node c) x is negativeand its absolute value is equal to thisnodes's address, or its absolute value isgreater than the maximum number ofnodes allowed at this level inNETTOP.If NODE_1 value is x and NODE_2value is y, this error occurs because ofone or more of the following reasons: a)x and/or y not in valid range of 1 to 127b) y is greater than the high slaveaddress configured for this node c) x isgreater than the maximum nodesallowed at the NETTOP level 2 levelsbelow the current level.

-3 R M Invalid output list index-4 R M Invalid master input structure number-5 R M Invalid master output structure


Page Master-9

MasterEMaster


Coded Error Messages (continued)

Code Detect Report Description

-6 R M,S Invalid slave input structure-7 R M,S Invalid slave output structure number-8 R,T M No matching slave for number on

POINT terminal.-9 T M Slave module is disabled

-12 T M,S Both input and output slave errors-13 T M,S Implicit type conversion attempted-14 T M Comm. error (unable to send request)-15 T M Comm. error (Time Out On Response)-16 T S Comm. error (unable to send response)-17 R M,S Invalid structure type -must be 0, 1,

or 2-18 R M Master has a zero length I/O structure-19 T M,S Slave has a zero length I/O structure

-22 T M,S Signal, list, or array could not beupdated because it was write protected,or a constant, or control inhibited, or astructure size mismatch occurred

-23 R M Node routing table not yet received-24 R M Missing or empty MODE timeout list


Page Master-10


❏ Module OperationThe Master/EMaster Module initiates communication with a corre-sponding Slave Module in another node. These modules use signallists or data arrays to read or transfer signal values from one node toanother.* The Master/EMaster Module can send or request the entiresignal list or data array, or optionally, it can send a single item from asignal list. Both modules also provide status information that monitorpeer-to-peer exchanges.

Signal lists contain any mix of analog, logical, or string signals whichare identified by numerical assignment; signals are processed inascending order starting at the lowest numerical assignment.

The master/slave communication system does not allow implicit typeconversions between signals. For example, any attempt to store alogical status as an analog signal will result in an error. As a conse-quence, storing and transfering data will be aborted and the errorstatus signals in the Master/EMaster and Slave Modules will be set.String signals also bear the same restriction.

A Master/EMaster Module is executed as part of an ACCOL task. Inorder for the module to operate correctly, it must be placed in a taskwith a priority of 32 or less.

Each time a Master/EMaster Module is executed, it attempts tocommunicate with its Slave Module unless previous communicationsare still in progress. Once communications have been completed, itsets associated output status values to indicate success or failure.

All Slave Modules are executed asynchronously whenever a commandor poll is received from their Master/EMaster.

* Only signal value/status is sent; other information such as the signal name, descriptortext, questionable data bit, and manual, control, and alarm inhibit bits ARE NOTtransferred.


Page Master/Slave-1

Master/Slave-Communications

The Master/EMaster and Slave Modules provide peer-to-peer commu-nications between nodes in the network. These modules use signallists or data arrays to read or transfer data from one node to another.These modules also provide status information that monitors peer-to-peer exchanges.

A Master/EMaster Module is executed as part of an ACCOL task. Inorder for the Master/EMaster Module to operate correctly, it must beplaced in a task with a priority of 32 or less.

A Master/EMaster Module sends data to, or receives data from, anassociated Slave Module in another remote node. Slave Modules areexecuted asynchronously whenever a message is received that speci-fies that Slave Module's POINT value.

Masters and Slaves can send or receive a complete signal list or dataarray. Signal lists are lists of analog, logical, or string signals whichare identified by numerical assignment; signals are processed inascending order starting at the lowest numerical assignment. Thelength of time required to send an entire list or array varies depend-ing upon its size, and several other factors discussed in the Network3000 Communication User's Guide (D4052).

The master/slave communication system does not allow implicit typeconversions between signals. As an example, any attempt to store alogical status as an analog signal (or vice-versa) will result in an error.As a consequence, the storage and transfer of data will be aborted andthe error status signals in both the Master/EMaster and Slave Mod-ules will be set. String signals also bear the same restriction.

❏ Communication ModesCommunications between a Master/EMaster and its associated SlaveModule can take place in one of three modes: SEND, POLL andSEND/POLL. In the SEND mode, the Master/EMaster Module sends

See also: Master ModuleSlave Module

Master/Slave Communications


Page Master/Slave-2


one or more data items from its OUTLIST to the Slave Module’sINLIST as shown in the first diagram in the following figure. In thisapplication, data stored in the signal list of RTU1 is transferred by theMaster/EMaster Module to the signal list contained in RTU2. The lineconnecting the two nodes represents the communication line. Whenthe modules are used in this manner, the transfer of data from Mas-ter/EMaster to Slave is initiated by the Master/EMaster. At the


Page Master/Slave-3


conclusion of the transfer, the Slave sends a message to the Master toreport if the data was properly received. When used in the POLLmode as shown in the middle diagram in the previous figure, theMaster initiates a request for data from the Slave. The Slave respondsto this request by taking the data stored in its OUTLIST and sendingit to the Master/EMaster INLIST.

The SEND/POLL mode configuration is shown in the bottom diagramin the previous figure. This is essentially a full-duplex arrangementwhere data flows in both directions. The upper path is identical to thePOLL mode while the lower path is identical to the SEND mode. Theupper path allows the Master/EMaster to receive data from theSlave’s OUTLIST, and store it in its own INLIST. Similarly, the lowerpath allows the Master/EMaster to send data from its OUTLIST to theSlave’s INLIST.

In each of the three modes, the status of communication transactionsis reported on the STATUS_2 terminal of the Master/EMaster andSlave modules.

BLANK PAGE

MuxEMux

Multiplexer and Extended Multiplexer Modules


Page MUX-1

Default: None, entry required for MuxModule


Default: INPUT_1 if INLIST is also unwiredFormat: Analog, logical, or string signalInput/Output: Input

INLIST

SELECT

OUTPUTM

The Mux and EMux Modules accept one of the input signals andapplies it to the OUTPUT terminal. The source of the input signals forthe Mux Module is a signal list. The Emux Module can also acceptinput signals from its INPUT terminals. An input signal is chosenfrom the signal list or INPUT terminals based on the value of theSELECT terminal.

Multiplexer Module Symbol EMux Module Symbol

Module TerminalsINLIST

is the signal list to be multiplexed. Signals in the list may be analog,logical, or string types.

INPUT_n(EMux Only)

is the input to be multiplexed. When both INLIST and INPUT termi-nals are wired, INLIST takes precedence.

INLIST

SELECT

OUTPUTINPUT_n EM

Mux/EMux


Page MUX-2

MuxEMuxMultiplexer and Extended Multiplexer Modules

SELECT

determines which signal in the INLIST signal list or the INPUTterminals will be applied to OUTPUT.

If SELECT is an analog signal, its value determines the location in thesignal or terminal list. For example, if the value ranges from 1 to1.99999, the INPUT is taken from the first location in the list, or fromterminal INPUT_1. If SELECT is a value from 3 to 3.99999, INPUT istaken from the third position in the list, or from INPUT_3. The validanalog range for the SELECT terminal is 1 to n where n is the numberof items in the INLIST, or, if the INPUT_n terminal is used, 1 to 255.

When SELECT is a logical signal, INPUT is taken from the firstlocation in the signal list or the first INPUT terminal when SELECTis OFF. INPUT is taken from the second list location or the secondINPUT terminal when SELECT is ON.

OUTPUT

is the multiplexed output of the module. Note: If the format of thesignal specified on the OUTPUT terminal differs from that of themultiplexed value selected (using the SELECT, and INLIST orINPUT_n terminals) the multiplexed value will be converted to theformat of the OUTPUT signal using the appropriate cast operation.See the section on the 'Calculator' module for information on signalcasts.

Default: None, entry requiredFormat: Analog, logical, or string signalInput/Output: Output

Default: None, entry requiredFormat: Analog or logical signal, or constantInput/Output: Input


Page Node Addressing-1

Node AddressingNode Addressing in a BSAP Network

A BSAP (Bristol Synchronous/Asynchronous Protocol) communicationsnetwork has a hierarchical or tree structure as shown in the followingfigure. In order to simplify node addressing in Master/Slave Modulesat the user level, the set of nodes that can communicate via thesemodules is restricted in the following manner: A Master Modulewithin any node (X) can communicate with a Slave Module in any ofX’s slave nodes, the master node of X, or any node whose master is thesame as that of X (any of X’s siblings).

The nodes are addressed in the ACCOL II source program by numbersin the range of -127 to +127, where positive node numbers denote theslave nodes, 0 denotes the master node, and negative numbers denotesibling nodes. The figure illustrates the addressing of nodes from agiven node containing a Master Module.

Master/Slave Communication Hierarchy

The Enhanced Master Module (EMaster) extends the addressingcapability to one additional level below the node containing theEMaster Module. This is needed to communicate with a Slave Modulein an Expanded Addressing Slave (EASlave) node on an ExpandedAddressing Master Port, but can also be used in a standard network.See the sections 'Expanded Node Addressing' and 'Master/EMaster' ,in this manual, for details.

Slave 0

Master Slave -nSlave -2

Slave nSlave 2

. . .

. . .Slave 1

See also: Master/Slave CommunicationsSlave Module

Node Addressing

BLANK PAGE

ACCOL II Reference ManualPage Nodestatus-1

NodestatusNodestatus Module

❑ Module OperationThe Nodestatus Module collects communications statistics for:

� a single slave node on a BSAP Master Port

� a single Expanded Addressing slave node on a BSAP Ex-panded Addressing Master Port

� a group of Expanded Addressing slave nodes configured belowa single “Virtual Node”

(See the section in this manual on 'Expanded Node Address-ing' for an explanation of the above terms.)

� a single 3508 Teletrans transmitter on a Global BBTI Board

(See 'BBTI Modules' earlier in this manual for details.)

The target node and the ACCOL structures are specified using theNodestatus Module input terminals. This module differs from thePortstatus Module which collects Master or Expanded AddressingMaster port statistics for all nodes on a port.

The Nodestatus Module provides the following actions (in the ordershown) when it is executed in an ACCOL task:

a. Detects any change in the Target Node specification (asspecified on the NODE_1 and NODE_2 terminals).

b. Validates the Target Node and destination structure specifi-cations.

c. Co-ordinates changes with the system tasks (Master Port task

Nodestatus



or GBBTI task). Changes include:

1. Idle-to-Active - Target Node specification changed from 0to non-zero and no errors detected.

2. Active-to-Idle - Target Node specification changed fromvalid non-zero value to 0.

3. Active Node Change - Target Node specification changedand no errors detected.

4. Any State-to-Idle - Target Node specification changed anderrors were detected.

d. Updates the STATUS terminal to indicate module status(Idle, Active, Change Pending), or specification errors.Change Pending status always occurs first in any sequencewhere the module status changes. The only case whereChange Pending will not be seen is if the module is Idle whenthe Target Node specification is changed, but an error isdetected; for this case the status reflects the error.

e. Resets statistics in the user structure (list or array) undercontrol of the RESET terminal; the RESET signal is auto-matically set to OFF following detection that it is ON. TheRESET terminal is examined only if:

1. Collection is currently active using a previously validatedTarget Node and destination structure.

2. A change of Target Node specification has been detectedand no module errors were detected during validation.



f. Processes active statistics maintained internal to the moduleinto the previously validated user structure (list or array).With the exception of "Consecutive Response Timeouts", allstatistics are processed by adding active non-zero counts tothe previously accumulated totals and clearing the activecounts. The internal counts are also cleared whenever collec-tion starts for a different node.

The following restrictions should be taken into consideration whenconfiguring a Nodestatus Module:

1. Only one Nodestatus Module can be configured per ACCOLload.

2. The Nodestatus Module should succeed the module(s) doingthe changes to the input terminals (e.g. Calculator, Mux etc.)in the same ACCOL task.

3. At any point in time, active collection of communicationstatistics applies to a single slave node (or a single group ofslave nodes on an Expanded Addressing Master Port).



q Module Terminals

NODESTATUS

NODE_1NODE_2LISTARRAYARY_ACCESSROWCOLUMNRESET

STATUS

The NODE_1 and NODE_2 terminal values are combined to fullyspecify the target node. For nodes on a standard BSAP Master port,the NODE_2 terminal must be 0 or unwired.

NODE_1 Default: None, entry required Format: Analog signal or constant Input/Output: Input

Identifies the target node by its physical node address. Valid valuesrange from 0 to 127. A value of 0 indicates no target node.

When the NODE_2 terminal is unwired or set to 0, the NODE_1 valuetargets a slave node on a standard Master Port, a "Virtual Node" onan Expanded Addressing Master Port, or a 3508 Teletranstransmitter on a Global BBTI board. The statistics for the "VirtualNode" include the communications transactions for all of the slavenodes in its group.

When the NODE_2 terminal is wired and specifies a valid “VirtualNode” on an Expanded Addressing Master Port, the NODE_1 valuetargets a specific slave node in the group associated with that “VirtualNode”.



NODE_2 Default: 0*Format: Analog signal or constantInput/Output: Input

Required for collecting statistics for a slave node connected to anExpanded Addressing Master port. It identifies, by its “physical” nodeaddress, the “Virtual Node” configured immediately above the targetnode in the network configuration files. Valid values range from 0 to127.

* If unwired, or if NODE_1 is not = 1-127, this terminal defaults to 0.


Is the number of the signal list which will receive the target node'scommunication statistics. The statistics will be stored beginning at thesignal list entry specified on the ROW terminal (the default is the firstentry). The list must contain only analog signals between the startingentry and the last entry used to store a set of node statistics. Theremust be at least 23 signals to capture all of the data. If the number ofentries available is shorter the module will provide as many statisticsas possible. No error will be reported for a short list.

ARRAY Default: NoneFormat: Analog signal or constantInput/Output: Input

Is the number of the analog read/write data array which will receivethe target node communication statistics. In order to write to this dataarray, the LIST terminal must be unwired, or a non-existent or emptylist should be specified. The statistics will be stored beginning at the



Row and Column coordinates specified on the ROW and COLUMNterminals, respectively. Storage will be done across the specified row(row mode) or down the specified column (column mode), based on theARY_ACCESS terminal described below. There must be at least 23elements within the row for row mode, or within the column forcolumn mode, to capture all of the data. If the number of elementsavailable is shorter the module will provide as many statistics aspossible. No error will be reported for a short row or column.

ARY_ACCESS Default: OFF (column mode)Format: Logical signalInput/Output: Input

Specifies the array access method. If this signal is not wired or OFF,data will be stored beginning at the row and column specified, pro-ceeding down the column to sequentially higher row numbers until all23 values have been stored, or until the last entry is used, whicheveroccurs first. If this signal is ON, data will be stored beginning at therow and column specified, proceeding across the row to sequentiallyhigher column numbers until all 23 values have been stored or untilthe last entry is used, whichever occurs first.

ROW Default: 1Format: Analog signal or constantInput/Output: Input

Specifies the entry in the signal list, or the row number in the dataarray, where the first statistic will be stored. If the number entered isbeyond the range of the structure, no data is stored and an error isreturned on the STATUS terminal.




Applies to data arrays only. Specifies the column number in the dataarray where the first statistic will be stored. If the number entered isbeyond the range of the data array, no data is stored and an error isreturned on the STATUS terminal.

RESET Default: OFFFormat: Logical signalInput/Output: Both

When this signal is ON and collection is active, or successful valida-tion has just occurred for a target node change, the elements withinthe destination structure statistics area are set to 0.0. The signal isthen set to OFF. For example, if the destination structure is a dataarray using row mode, beginning at row 5, column 25 and extending torow 5, column 47, the 23 array elements within that area will be set to0.0. If the destination is a signal list having 8 entries, beginning withthe first entry, all 8 signals will be set to 0.0. When collection is active,the internal active counts are also cleared on a RESET.If the Target Node is 0, or if the status indicates an error was de-tected, the RESET terminal has no effect. Its state is not examinednor changed.




Is set to one of the status codes listed below each time the moduleexecutes.

Code Meaning

0 Idle

1 Collection Active

2 Change Pending

-1 Invalid Node Terminal Value (valid values = 0-127)

-2 Invalid Node Specification (node not configured inload).

This error is returned if: NODE_2 is unwiredor 0, and the NODE_1 value is greater than themaximum High Slave Address specified for theMaster/Expanded Addressing Master port(s), orgreater than the 3508 Transmitter address forChannel 8 of the global BBTI board in the highestnumbered slot position.

This error could also be returned if the value ofNODE_2 is not equal to 0, and the NODE_2 valuedoes not specify a 'virtual node' on an ExpandedAddressing Master Port or the NODE_1 value isgreater than the High EASlave Address specified forthat Expanded Addressing Master Port.



-3 Invalid Signal List Index (ROW terminal value)

-4 Invalid Signal in List (analog signals required)

-5 Invalid Data Array Row No.

-6 Invalid Data Array Column No.

-7 No Valid Structure (both LIST and ARRAY unwiredor invalid)

qÿ Module ModificationsControl of collection using the Nodestatus Module can be done by theACCOL program, or by changing module inputs from an externalsource, e.g. Toolkit.

FROM ACCOL - The module(s) doing the changes(e.g. CALCULATOR or MUX)should precede the NodestatusModule in the same task. Thestatus from the NodestatusModule should be verified to beCollection Active (status = 1)before using the data from thedestination structure.

FROM EXTERNAL SOURCE The Target Node should always beset to 0 (set NODE_1 terminal to0.0) to place the module in the Idlestate before changing other inputs.The structure inputs



(cont'd)

FROM EXTERNAL SOURCE (Signal List or Array number, etc.)should then be established, andthe RESET terminal set to ON ifdesired, prior to setting the TargetNode value. When specifying anode on an Expanded AddressingMaster port, the NODE_2 termi-nal should also be establishedbefore changing the NODE_1terminal from 0 to the target nodeaddress.

STATUS SEQUENCE The initial execution of theNodestatus Module following achange of Target Node will resultin a status of either change pend-ing (status=2) or a negative errorcode. On the subsequent executionof the module, usually the nextone, the change pending statuswill change to:

Collection Active (Target Node non-zero and no errors, status=1)

Idle (Target Node=0, status=0)

Error Code (previously active collection cancelled because of errordetected on change of Target Node specification, status = negative)

NOTE: This change of status can be delayed in the case where collec-tion was previously active and an I/O transaction is currently inprogress for the previous target node. The pending change cannot beput in effect until the I/O transaction completes.



❑ Statistics CollectedStatistics are maintained on an individual transaction basis, i.e.success or failure is accounted for on each transaction in contrast tothe BSAP port statistics which reflect results after retries, if any, havebeen exhausted.

Up to 23 categories of information may be collected by the NodestatusModule. The first eight are the same for all node types, including the3508 Teletrans transmitter connected to a Global BBTI board. Theremaining categories vary as detailed below. The first eight categoriesare the same as those available using Toolkit or the Portstatus Modulefor a BSAP Master or Expanded Addressing Master Port:

Messages ReceivedData and Poll Messages TransmittedResponse TimeoutsConsecutive Response TimeoutsNaks ReceivedCRC ErrorsMessage Discarded Acks ReceivedProtocol, Overflow or Serial Number Errors

For the Global BBTI/3508 Teletrans, two additional categories areavailable (a total of 10 statistics):

GBBTI Board State ErrorGBBTI Board Access Failure

The Board State Error is incremented if the board is accessed, but it isnot collecting statistics. Collection of statistics for the selected



transmitter is then restarted. The Board Access Failure is incremen-ted if the task is unable to access the board to read the statistics. Thiscould be because there is no board installed, the wrong board type isinstalled, or the board was busy with normal functions which takepriority over statistics collection.

For BSAP Master/Expanded Addressing Master Ports, the next 11categories provide new information (indicated by an (*)), or a moredetailed breakdown of the first 8 categories. The charts on the nextpages show the relationships of the various categories.

Poll Messages Transmitted (Includes NRT/TimeSync.Messages)

Data Messages Transmitted

(*)Data Message Transmit Retries

(*)Msg. Xmt. Not Attempted (Node Offline or Dead)

(*)NRT Needed (Slave needs NRT-Gbl.Xmt.Not Sent)

(*)NRT Requests Received



Sequence Error (Response from Wrong Node, Invalid Length,or Wrong Msg. Type)

Overflow Error (Response Overflow)

Serial No. Error (Response Serial No. Error)

(*)NRT Mismatch (Gbl.Rcv.NRT Vers.Mismatch)

(*)Exchange Error (Error processing received message)

The final 4 categories are for RASCL 1MB Synchronous links only;these categories do not apply to Expanded Addressing Master Portswhich can be Asynchronous only:

Link 1 Xmt. Error

Link 2 Xmt. Error

Link 1 Rcv. Error

Link 2 Rcv. Error



Nodestatus Module Statistics

Note:Items with asterisks in the following figures are standard categoriesfor both Master and Expanded Addressing Master Ports, i.e. they arethe 8 statistics available using the Portstatus Module, or displayed onthe Toolkit Communications Statistics screen.

Transmissions

TRANSMISSIONS

XMT NOT ATTEMPTED DATA & POLL MSGs TRANSMITTED DATA MSG RETRIES

POLL MSGS XMT DATA MSGS XMT

NRT NEEDED(GLOBAL MSG NOT SENT)

*

* STANDARD STATISTICS

Data Msgs.Xmt.- NRT Needed = Actual Data Msgs.Xmt.

Retry counts are additional, i.e. a message which requires 1 retry willbe represented by 1 count in the Data Msgs.Xmt. category and 1count in the Data Msg.Retries category.



Transmit Errors

TRANSMIT ERRORS(RASCL PORTS ONLY)

LINK 1 XMT ERROR * LINK 2 XMT ERROR *

Responses

DATA MSGS RCVD

RESPONSES

*

NRT REQUESTS RCVDNRT MISMATCH (MSG DISCARDED)

EXCHANGE ERRORS (MSG DISCARDED)



Response Errors

RESPONSE ERRORS

TIMEOUTS* NAKS* CRC*

CONS.TO* SEQUENCE OVRFL SER#

PROTOCOL/OVR/SER#*MSG DISC ACKS *

Naks and Msg.Disc.Acks apply to transmission of Data Messages only.Sequence Errors consist of messages from the wrong node, invalidlength (less than minimum msg. size), and inappropriate messagetype.

Receive Errors

RECEIVE ERRORS(RASCL Ports Only)

Link 1 Rcv. Error* Link 2 Rcv. Error*


Page PDM-1

PDMRPDM

Pulse Duration and Remote Pulse Duration Modules

The Pulse Duration Modulation Modules receive pulse durationsignals and make these signals available to other ACCOL modules.The source of these signals may be a timed contact closure in the fieldlike that produced by the Bristol METAMETER transmitter or anydevice producing a variable length pulse that indicates a value.

There are two types of Pulse Duration Modulation Modules: PDM andRPDM. They are very similar to each other, except in the way theyspecify process I/O boards for digital input signals.

PDM Module Symbol

RPDM Module Symbol

INITIALTYPE

INPUT

SPANZERO

STATE

DEVICE

TRACKElectrical Input

TIME

DEADBAND

INITIALTYPE

INPUT

SPANZERO STATE

DEVICE

TRACKElectrical Input

TIMEDEADBAND

STATUS

R


PDM/RPDM


Page PDM-2

PDMRPDMPulse Duration and Remote Pulse Duration Modules

PDM (Pulse Duration Modulation) Modules receive pulse durationsignals from process I/O boards which reside within that controller.RPDM (Remote Pulse Duration Modulation) modules also receivepulse duration signals from process I/O boards, but only from thoseboards which reside in an RIO 3331 Remote I/O Rack.

Each electrical input signal is associated with a set of several termi-nals: INPUT, ZERO, and SPAN. For the RPDM Module, the STATEterminal is also included in this set. Each set of terminals is numberedfor identification purposes.

Placing the PDM or RPDM Module in an ACCOL task separate fromother modules will allow you to more easily adjust the task rate. Thismay be useful, for example, if system resources are low; performancemay be improved by setting the task rate for the task containing thePDM or RPDM Module longer than the period of the input signal.

❏ Module TerminalsDEVICE (PDM) Default: 0 (null device) Specifying the

default will generate an errorwhen the module executes and nosignal processing will occur.


is the slot number of the Process I/O Board where the PDM signalsreside. The board installed in the slot specified here must be capable ofreceiving digital input signals; otherwise an error message will begenerated.



Page PDM-3

PDMRPDM


DEVICE (RPDM) Default: 0 (null device) Specifying thedefault will generate an errorwhen the module executes and nosignal processing will occur.


is a three digit number which identifies the RIO 3331 process I/Oboard where the input signals reside. There can be up to ten RIO 3331nodes connected to each communication port of a 3310/3330/3335controller, and each RIO 3331 can hold up to ten process I/O boards -therefore up to 100 boards can be referenced through a given commu-nications port.



The first digit indicates the communications port on the 3310/3330/3335 which is accepting data from the RIO 3331 node:



Page PDM-4


The second digit must be one less than the RIO 3331 node addresswhere the board resides. It must range from 0 through 9 (Second digit= 0 for node address 1. Second digit = 9 for node address 10.)


Examples:



The number entered on the DEVICE terminal will be verified with theProcess I/O Menu (if you’re using the AIC) or the *PROCESS-I/Osection (if you’re using the ABC or ACCOL Workbench). This boardmust be capable of accepting digital input signals. If no board is foundin the specified slot or if the board is the wrong type, an error messagewill be generated.


is the number of the field wiring terminal that will be assigned to thefirst set of PDM or RPDM Module terminals. All subsequent terminalsentered on this menu will automatically be sequenced from the initialnumber. For example, if 3 is the INITIAL entry, then the INPUT 1terminal corresponds to field wiring terminal DI3 and INPUT 2corresponds to field wiring terminal DI4.


Page PDM-5

PDMRPDM


TYPE

is a one-digit numerical code that identifies the type of input comingfrom the field.

Instrument TYPE Pulse characteristics

Metameter 15 second period 1 3 sec pulse = 0%12 sec pulse = 100%

Metameter 5 second period 2 1 sec pulse = 0%4 sec pulse = 100%

BIF 15 second period 3 no pulse = 0%13.3 sec pulse = 100%

BIF 60 second period 4 no pulse = 0%53.3 sec pulse = 100%

5 Series of variable lengthpulses. Maximum pulselength is 65.532

In certain special applications, for example, tank level control, thepulse duration signal originating at the transmitter is inverted. Tohandle this situation, specify the TYPE as a negative number. Forexample, in the table above, -1 would be used for a 15 second Metame-ter.

Default: 1Format: ConstantInput/Output: Input


Page PDM-6


TIME

specifies a period of time in units of seconds. The meaning depends onthe type of input signal specified on the TYPE terminal.

Type Meaning

1-4 When no valid pulses are received during the time periodspecified on this terminal, the signal named on the STATEterminal is turned ON. This value must be an integer. Frac-tional seconds are ignored.

The default depends on the device specified on the TYPEterminal. The default is equal to four times the maximumperiod as shown below.

60 for 15 second Metameter20 for 5 second Metameter60 for 15 second BIF240 for 60 second BIF

5 The time specified with this terminal is the maximum lengthof a valid pulse. If pulse length is greater than this value, thepulse is ignored and the signal named on the STATE termi-nal is turned ON.

The value may range from .004 to 65.532 seconds. If thevalue is out of range, the value will be limited to either .004or 65.532.

Default: (See below)Format: Analog signal or constantInput/Output: Input


Page PDM-7

PDMRPDM


DEADBAND

Type Meaning

1-4 The value is the amount by which the period can deviate andstill be considered acceptable.

DEADBAND must be a number from 1 to 100. It is convertedto a percentage by the module and is multiplied by thedifference between the maximum and minimum pulse widths.This result is called the tolerance. If the input pulse is lessthan the minimum value but by not more than the tolerance,the input is assumed to be zero.

If the input pulse is greater than the maximum value butdoes not exceed the tolerance value, the input is assumed tobe 100%. Input pulses outside the tolerance zone are notaccepted.

The default is 3 percent of full scale:270 msec for 15 sec Metameter90 msec for 5 second Metameter400 msec for BIF 15 second1600 msec for BIF 60 second

5 The value specifies the minimum length of a valid pulse inunits of seconds. ON or OFF pulses with a length shorterthan this value are ignored. It is used to filter out spuriouspulses caused by noise.

The value may range from .004 to 65.532 seconds. If thevalue is out of range, the value will be limited to either .004or 65.532. If the terminal is not used, the DEADBANDdefaults to .004.

Default: 3 percent of full scale (see below)Format: Analog signal or constantInput/Output: Input


Page PDM-8


TRACK

The function of the TRACK terminal depends on the setting of theTYPE terminal.

TYPE Meaning

1-4 TRACK is the amount by which a measurement may differfrom the previous accepted measurement and be consideredvalid. It is used to filter out spurious measurements causedby noise.

Like DEADBAND, TRACK is expressed as a percentage. It ismultiplied by the difference between the maximum andminimum pulse width to obtain the tolerance.

If the absolute difference between the current acceptedmeasurement and the previous accepted measurement is notmore than the tolerance, the measurement is consideredvalid. Otherwise, it is considered invalid.

The default is the same as the DEADBAND terminal. Ifneither is wired, TRACK is 3% of the span as shown aboveunder DEADBAND.

5 TRACK disables the module when it is equal to 0.0. Anyother value will enable the module. If the terminal is notused, the module defaults to enabled.

When the module is enabled, pulses are measured andaccumulated and the signals named on the INPUT andSTATE terminals are updated. When the module is disabled,pulses are ignored and INPUT and STATE are not updated.



Page PDM-9

PDMRPDM


INPUT

is the output of the module. Its function depends on the setting of theTYPE terminal.

TYPE Meaning

1-4 It represents the most recent valid measurement. WhenSPAN and ZERO terminals are not specified, INPUT willtake on values of 0 to 1 which represents percent of full scale.When SPAN and ZERO are specified, INPUT is expressed interms of engineering units. It is calculated as shown below.

INPUT = (last valid measurement * SPAN) + ZERO

5 INPUT is an accumulation of the pulse lengths measured onthe input signal. The total length of all pulses measured sincethe previous execution of the module is added to the signalnamed on the INPUT terminal after being adjusted by theSPAN and ZERO terminals, as shown in the equation below.The pulse lengths are measured in seconds. The SPAN andZERO terminals convert time to engineering units.

INPUT = INPUT + ((pulses * SPAN) + ZERO)

The total length of all pulses measured since the previousexecution of the module is limited to 65.534 seconds. If thislimit is exceeded i.e an overflow has occurred, a total pulselength of 65.534 seconds is used in the above calculation.

The questionable data status will indicate a questionablepulse measurement. It is set when an overflow conditionoccurs or a power failure occurs while a pulse is in progress.



Page PDM-10


ZERO Default: 0.0Format: Analog signal or constantInput\Output: Input

sets the zero value in terms of engineering units.

SPAN Default: 1.0Format: Analog signal or constantInput\Output: Output

defines the full scale range of the input signal in terms of engineeringunits.

STATE Default: None, entry is optionalFormat: Logical signalInput\Output: Output

indicates the validity of the input line. Its function depends on theTYPE terminal.

TYPE Meaning

1-4 If a valid measurement is not obtained within the timespecified by the TIME terminal, the STATE signal is turnedON to indicate a line fault. Also, INPUT remains at the valueof the last valid measurement. The next time a valid meas-urement is obtained, the state signal is reset to OFF.

5 If the length of a measured pulse is greater than the maxi-mum specified by the TIME terminal, the STATE signal isturned ON to indicate an invalid pulse. The next time a validpulse is measured, the STATE signal is reset to OFF.


Page PDM-11

PDMRPDM


STATUS(RPDM)

assumes one of the module execution codes specified below:

Code Meaning0 Module executed successfully

-1 Invalid remote device ID-2 Communication failed with remote unit-3 Remote board is missing-4 Remote board is of the wrong type-5 The remote board failed diagnostic tests-7 RIO Rack firmware incompatible with process I/O configured

in load. (C.01 or newer firmware should be installed in the RIO3331.)

❏ Module OperationPulse duration signals are initially received by either a Digital I/O orMixed I/O Board (depending upon which type of controller you areusing). System software measures the duration of pulses as thechange-of-state events arrive at the 33XX controller. When the taskwhich contains the Pulse Duration Modulation module executes, theduration of the latest pulse measured by system software is passed onto the module. The Pulse Duration Modulation module then makesthis information available to other ACCOL modules. For input types 1thru 4, this value is in terms of a percentage of full scale or can beconverted by the module to engineering units. For type 5, it is thepulse ON time in seconds.



Page PDM-12


System signals #PDM.000 through #PDM.008, if activated, provideinformation about the characteristics of the measured signal. Forexample, #PDM.004 indicates the duration of the pulse in the lastperiod. (See 'System Signals'.) For input type 5 only #PDM.004 isupdated. #PDM.005 thru #PDM.008 are not used. A value of -1.0 onthe #PDM.004 indicates that a pulse did not complete within themaximum valid time as specified by the time terminal.

❏ Process I/OOne PDM or RPDM Module can receive a number of PDM signals fromdifferent field devices, however, these devices must all be of the sametype (See TYPE terminal).

The number of field signals that can be processed by a PDM or RPDMModule is limited by the number of digital inputs provided on theProcess I/O Board. See 'Process I/O', for more details.


Page PDO-1

Pulse Duration Output and Remote Pulse Duration Output Modules

PDORPDO

With the Pulse Duration Output Modules, you can produce pulses ofvariable width at the digital output (DO) field wiring terminals. Thesemodules can be used in applications requiring the conversion of ananalog signal into a pulse-duration output signal for external commu-nications, or in applications that use an analog control signal toprovide raise and lower output signals to drive a bi-directional motor-ized valve or similar device.

RPDO Module Symbol

PDO Module Symbol

OUTPUT

MIN_ TIME

MAX _TIME

DEVICEINITIAL

RESOLUTIONMODE

RPDO INPUT

HIGH_LIMIT

LOW_LIMITSPAN

raise & lower signals}

STATUSTRACKRESET

ENABLE

OUTPUT

MIN_ TIME

MAX _TIME

DEVICEINITIAL

RESOLUTIONMODE

TRACKRESET

ENABLE

PDOINPUT

HIGH_LIMIT

LOW_LIMITSPAN

raise & lower signals}


PDO/RPDO


Page PDO-2

PDORPDOPulse Duration Output and Remote Pulse Duration Output Modules

There are two types of Pulse Duration Output Modules: PDO andRPDO. PDO (Pulse Duration Output) Modules send pulse durationsignals to process I/O boards which reside within that controller.RPDO (Remote Pulse Duration Output) Modules also send pulseduration signals to process I/O boards, but only to those boards whichreside in an RIO 3331 Remote I/O Rack.

Note that the output of a PDO or RPDO Module is directed to thedigital output (DO) terminals and does not require a DIGOUT orRDIGOUT Module to achieve the interface. All DOs available at thecontroller terminals are furnished as standard open collectors oroptional relay contacts. The former arrangement can be used withmoderate, non-isolated loads, while the latter must be used for heavyloads.

❏Module TerminalsDEVICE (PDO) Default: 0 (null device) Specifying the

default will generate an errorwhen the module executes and nosignal processing will occur.


is the slot number of the Process I/O Board where the PDO signalsreside. The board installed in the slot specified here must be capable ofgenerating digital output signals or an error message will be gener-ated.



Page PDO-3


PDORPDO

DEVICE (RPDO) Default: 0 (null device) Specifying thedefault will generate an errorwhen the module executes and nosignal processing will occur.


is a three digit number which identifies the RIO 3331 process I/Oboard which is being referenced by this module. There can be up to tenRIO 3331 nodes connected to each communication port of a 3310/ 3330/3335 controller, and each RIO 3331 can hold up to ten process I/Oboards - therefore up to 100 boards can be referenced through a givencommunications port.



The first digit indicates the serial port on the 3310/3330/3335 control-ler which is receiving inputs from this board.



Page PDO-4


The second digit must be one less than the RIO 3331 node addresswhere the board resides. It must range from 0 through 9 (Second digit= 0 for node address 1. Second digit = 9 for node address 10.)


Examples:



The number entered on the DEVICE terminal will be verified withthe Process I/O Menu (if you’re using the AIC) or the *PROCESS-I/O section (if you’re using the ABC or ACCOL Workbench). Thisboard must be capable of generating digital output signals. If noboard is found in the specified slot or if the board is the wrong type,an error message will be generated.

INITIAL Default: 1Format: Analog signal or constantInput/Output: Input

is the number of the first of a pair of adjacent DO field wiring termi-nals that will be assigned to the first set of PDO or RPDO Moduleterminals. Each succeeding set of module terminals will be assignedthe next corresponding pair of DO field wiring terminals in sequence.For example, if the value 3 is assigned for this terminal, OUTPUT #1of this module will use DO3 for “Raise” or positive direction pulses,


Page PDO-5


PDORPDO

and DO4 for negative-going pulses. Similarly, OUTPUT 2 will useDO5 for “Raise” or positive-going pulses, and DO6 for “Lower” ornegative-going pulses.

IMPORTANT NOTE FOR RPDO USERS:

In general, no more than a maximum of 2 remotePDO pairs (4 DO points) should be used in anysingle RPDO module. If more pairs are necessary,spread them across more RPDO modules or tasks.Failure to follow this rule may result in interferencewith the RIO 3331 clock. In RIO 4.1 and newerfirmware, this interference is indicated via a statuscode on the RIOSTATS module.

RESOLUTION Default: 1Format: ConstantInput/Output: Input

specifies the number of 20 millisecond time periods that comprise onetick of the PDO or RPDO Module’s clock. This clock is used to time theoutput pulses. One clock tick is equal to:

Resolution * 20 msec

The value of this terminal may range from 1 to 255.

STATUS (RPDO) Default: None, entry is optionalFormat: Analog signalInput/Output: Output

assumes one of the module execution codes specified below:

Code Meaning 0 Module executed successfully-1 Invalid remote device ID


Page PDO-6


-2 Communication failed with remote unit-3 Remote board is missing-4 Remote board is of the wrong type-5 The remote board failed diagnostic tests-7 RIO Rack firmware incompatible with process I/O configured


There is one of each of the remaining terminals for each Pulse Dura-tion Output signal in the module. The terminals for an individualoutput signal share the same number.


selects the operating mode of the PDO or RPDO Module output withwhich it is associated. The mode choices are 0, 1, 2 or 3. The defaultvalue is 0. This terminal will accept values other than those given.However, numbers that are not legal will cause the output pulse to beinhibited. 3530-series units DO NOT SUPPORT modes 1, 2 or 3.

OUTPUT Default: None, entry requiredFormat: Analog signalInput/Output: Output

is the output of this module which is determined in part by the valuereceived on the OUTPUT terminal. If OUTPUT is unwired, the outputpulse will be inhibited. This terminal is used differently depending onthe Mode selected.

For Mode 0:

This value represents the length of the output pulse in terms of the


Page PDO-7


PDORPDO

number of PDO or RPDO clock ticks. The length of the pulseproduced by this module is defined by the following equations:

clock tick = RESOLUTION * 20 msec

duration of output pulse = OUTPUT * clock tick

OUTPUT may range from -32,767 to +32,767. If the value is out ofrange, the maximum value with the same sign will be used. WhenOUTPUT is a positive number, the first DO in the pair is activated.When OUTPUT is negative, the second DO is activated.

For Modes 1, 2 & 3:

OUTPUT represents the desired valve position in terms of percentof full-scale of travel. The value may range from 0 (fully closed) to100 (fully open). If the value is out of range, the respective limitvalue (0 or 100) will be used.

The length of the pulse produced by this module is defined by thefollowing equations:

OUTPUT - present positionpulse width = ____________________________ * SPAN

100

The length of the output pulse as calculated by the above equation isconverted to PDO or RPDO clock ticks as described in paragraph'Factors Affecting Pulse Length'. If the desired position is greater thanthe present position, the first DO of the pair associated with theOUTPUT terminal will be activated (the “Raise” pulse), otherwise thesecond DO or “lower” pulse will be activated.


Page PDO-8


ENABLE Default: ONFormat: Logical signalInput/Output: Input

will enable or inhibit the output pulse. When the signal is FALSE, theoutput pulse will be inhibited, the TRACK terminal will be set toFALSE, and the RESET terminal will not be updated. If the signal onthe ENABLE terminal is TRUE, the output pulse will be enabled.

MIN_TIME Default: None, entry is optionalFormat: Analog signal or constantInput/Output: Input

specifies the minimum pulse length allowed. If the specified or calcu-lated output pulse length is less than the value of this terminal, nopulse will be generated and the pulse length will be set to zero. If thisterminal is not used, no minimum limit will be placed on the outputpulse other than the limit imposed by the PDO or RPDO clock tickresolution. The units of this terminal depend on the mode selected.

For Mode 0:

This option represents the minimum number of clock ticks for apulse. It is calculated by dividing the desired minimum duration ofa pulse by the duration of one clock tick. (Recall that clock ticks aredefined by the RESOLUTION terminal.)

For Modes 1, 2 & 3:

These options represent the minimum pulse length in units ofseconds. This will be converted to the nearest integer multiple ofclock ticks. See ‘Factors Affecting Pulse Length’.


Page PDO-9


PDORPDO

MAX_TIME Default: None, entry is optionalFormat: Analog signal or constantInput/Output: Input

specifies the maximum pulse length allowed. If the specified or calcu-lated output pulse length is greater than the value of MAX_TIME,then the output pulse length is determined using MAX_TIME. If thisterminal is not used, no maximum limit will be placed on the length ofthe output pulse. The units of this terminal depend on the setting ofthe MODE terminal.

For Mode 0:

This value represents the maximum pulse length in terms of thenumber of PDO or RPDO clock ticks. It is calculated by dividing thelongest pulse length by the duration of one clock tick. (Recall thatclock tick is defined by the RESOLUTION terminal.)

For Modes 1, 2 and 3:

This value represents the maximum pulse length in units of sec-onds. This will be converted to the nearest integer multiple of PDOor RPDO clock ticks.


specifies the number of seconds it takes for the valve to travel fromfully opened to fully closed. This terminal is not used for Mode 0.


Page PDO-10


INPUT Default: NoneFormat: Analog signal or constantInput/Output: Input

is used in Mode 3 to indicate to the module the actual position of thecontrolled device in terms of percent of full scale of travel. This valuemay range from 0 to 100. If the value is out of range, the respectivelimit value (0 or 100) will be used. This terminal is only used forMODE terminal selection 3. If this terminal is not used and theMODE terminal is set for 3, the output pulse will be inhibited.

HIGH_LIMIT Default: OFFFormat: Logical signalInput/Output: Input

is used in Mode 1 to indicate to the module that the controlled deviceis at the high limit of its position range. A value of TRUE indicatesthat the position is 100% of full scale.

LOW_LIMIT Default: OFFFormat: Logical signalInput/Output: Input

is used in Mode 1 to indicate to the module that the controlled deviceis at its low limit of its position range. A value of TRUE indicates thatthe position is at 0% of full scale. This terminal is only used for MODE1.


is set by the module to indicate that some limit condition has been


Page PDO-11


PDORPDO

reached. TRACK is set to FALSE if the output pulse is inhibited.

For Mode 0:

TRACK is set to TRUE if the absolute value of the OUTPUTterminal is greater than 32,767, greater than the value at the MAXTIME terminal, or less than the value at the MIN TIME terminal.Otherwise TRACK is set to FALSE.

For Modes 1 & 2:

TRACK is set to TRUE if the value at the OUTPUT terminal is lessthan 0 or greater than 100. Otherwise, TRACK is set to FALSE.

For Mode 3:

TRACK is set to TRUE if the value at the INPUT terminal is lessthan 0 or greater than 100. Otherwise, TRACK is set to FALSE.

RESET Default: NoneFormat: Analog signalInput/Output: Output

is set by the module to provide feedback. The signal’s value is notupdated when the output pulse is inhibited. The use of this terminal isdependent on the selected mode at the MODE terminal as follows:

For Mode 0:

The signal’s value is set equal to the number of PDO or RPDO clockticks used in the output pulse.

For Modes 1 & 2:

The signal’s value represents the estimated valve position. It is


Page PDO-12


equal to the value at the OUTPUT terminal after being limited tothe 0 to 100% range.

For Mode 3:

The signal’s value represents the actual valve position. It is equalto the value at the INPUT terminal after being limited to the 0-100% range.

❏Modes of OperationEach of the PDO or RPDO module outputs may be assigned to one ofthe four operating modes. The same modes apply to both the PDO andRPDO modules, and are summarized below.

MODE 0: Pulse Duration Output

This mode converts an ACCOL analog signal into a pulse durationoutput. The duration of the pulse is proportional to the absolute valueof the analog signal received on the OUTPUT terminal. A positivevalue will activate the first DO of the pair assigned to the moduleoutput, while a negative value will activate the second DO. When themodule receives a zero, both DOs are in the low or OFF state.

Mode 0, Pulse Duration Output - RPDO shown

digital

terminalsoutput

OUTPUT

MIN TIME

MAX TIME

DEVICEINITIAL

RESOLUTIONMODE

TRACKRESET

ENABLE

RPDOMODULE

raise

lower

onoff

onoff

METAMETERPD RECEIVER

ArrestorsLightning

DCSupply

12 V max

+

45 mamax

FALSE = PDO offTRUE = PDO on

(not used)

RPDO clockticks

Provides range limit statusTRUE = < MIN TIME or > MAX TIMEFALSE = normal

CalculatorModule

control signalInput

value equals numberof RPDO clock ticks

STATUS


Page PDO-13


PDORPDO

A sample application is shown in the previous figure. When themodule is used in this mode to transmit pulse duration signals over atwo-wire line to a device such as a Bristol METAMETER Pulse Dura-tion Receiver, the first digital output of the pair should be used. Thesecond DO is not applicable to this application.

Controllers furnished with standard open-collector DO terminals, canbe wired to METAMETER PD loops powered by an external dc supply(12 V dc maximum). For this application, the loop current must notexceed a maximum of 45 mA. A relay contact output is recommendedfor PD loops requiring higher current levels.

Using the PDO or RPDO Module To Operate Motorized Valves

Three modes are available for operating motorized valves. Mode 2provides raise and lower signals when no feedback is available fromthe valve. In Mode 1, feedback comes from two limit switches thatindicate the valve is either fully opened or fully closed. Mode 3 is usedwhen the valve provides continuous feedback over the entire range oftravel of the valve.

In Modes 1, 2, and 3, the PDO or RPDO Module receives an analogcontrol signal which specifies a desired valve position in terms ofpercentage of range. Based on the present position of the valve, themodule must determine if the valve stem should be raised or loweredand by how much. If the valve needs to be opened, the first DO will beactivated. To close the valve, the second DO is activated. The length ofthe output pulse is calculated using the difference between the desiredposition (as received on the OUTPUT terminal) and the presentposition (obtained from feedback or calculated by the module). If thedesired position is greater than the present position, the pulse is sentout on the first DO. If the desired position is less than the presentposition, the pulse is sent out on the second DO. The present positionis obtained from feedback from the valve (Modes 1 and 3) or fromcalculations (Mode 2).


Page PDO-14


MODE 1: Raise/Lower Output With Range Limit Feedback

In this mode, there is feedback of position information from the devicewhen it is at the limits of its range (0% or 100%). A typical applicationof this mode is the operation of a motorized control valve as shown inthe figure below.

Feedback from the valve is received by this module on theLOW_LIMIT and HIGH_LIMIT terminals. Present position is as-sumed to be 0% (closed) if the LOW LIMIT terminal is True, or 100%(open) if the HIGH LIMIT terminal is True. If neither of these termi-nals is True, or if they are unwired, the present position is estimatedas follows: on start-up the estimated position is 0% or closed, thereaf-ter the estimated position is based on assumed completion of the mostrecent operation. The value of the signal at the OUTPUT terminal(limited from 0-100%), which indicates the desired position, is savedand referenced as the estimated present position at the next rateexecution of the PDO or RPDO Module.

RPDOMODULE

Provides range limit statusTRUE = < 0 % or > 100 %FALSE = 0 - 100 %

raise

lower

motorized

valve

SPANHIGH_ LIMIT

LOW_ LIMIT

RDIGINModule

terminals

MIN_TIME

MAX_TIME

ENABLE

control

OUTPUT

RANIN

PID 3 input

setpoint

processsensor

AIterminals

RESET

TRACK

control signal

TRUE = PDO onFALSE = PDO off

Tracks output level0 - 100 %

DEVICE

INITIAL

RESOLUTION

MODE

Module

DOterminals

DI

valve

switcheslimit

STATUS

Mode 1, Raise/Lower Output With Range Limit Feedback


Page PDO-15


PDORPDO

MODE 2: Raise/Lower Output

This mode is identical to Mode 1 except that no feedback on actualvalve position is available. The present position is assumed to be 0%(closed) at start-up. Thereafter, present position is calculated byassuming that previous output pulses have been sent out and thevalve has successfully achieved the desired position. See the figurebelow.

Mode 2, Raise/Lower Output

RPDOMODULE


raise

lower

motorized

valve

SPAN

MIN_TIME

MAX_TIME

ENABLE

control

OUTPUT

RANIN ModulePID3 TERM

input

setpoint

processsensor

AIterminals

RESET

TRACK

control signal



DEVICE

INITIAL

RESOLUTION

MODE

Module

DOterminals

STATUS


Page PDO-16


MODE 3: Raise/Lower Output With Valve Position Feedback

In Mode 3, the module receives feedback of the actual valve positionon the INPUT terminal. The value on this terminal is the valve’spresent position.

The figure below illustrates an application which uses a slidewirecircuit. The slidewire contact arm mechanically tracks the valveposition and provides a corresponding electrical output signal. Thevalue of this signal is proportional to the valve opening.

Mode 3, Raise/Lower Output With Valve Position Feedback

RPDOMODULE


raise

lower

motorized

valve

SPAN

terminal

MIN_TIME

MAX_TIME

ENABLE

control

OUTPUT

RANIN ModulePID3 TERM

input

setpoint

processsensor

AIterminals

RESET

TRACK

control signal



DEVICE

INITIAL

RESOLUTION

MODE

Module

DOterminals

AI

valve

signalposition

INPUT(feedback)

RANINModule

STATUS


Page PDO-17


PDORPDO

❏ Factors Affecting Pulse Length

A. Clock Tick Resolution

Pulse length is ultimately controlled in terms of an integer mul-tiple of PDO (or RPDO) clock ticks. The minimum pulse lengthwhich can be generated is 1 clock tick. The length of the PDO orRPDO clock tick is determined by the user via the RESOLUTIONterminal and is comprised of an integer multiple of 20 millisecondtime periods. The minimum clock tick is 1 time period or 20 msec.;the maximum clock tick is 255 time periods or 5.1 seconds. Thesame resolution applies to all outputs of a PDO or RPDO Module.

B. Minimum Pulse Length

If the MIN TIME terminal is unwired and the length of thespecified or calculated output pulse is less than 1 PDO or RPDOclock tick, no pulse is generated. The output pulse length is savedand added to the output pulse length specified or calculated at thenext rate execution of the PDO or RPDO module. A pulse lengthgreater than 1 PDO or RPDO clock tick is rounded to the nearestinteger multiple of a clock tick.

If the MIN TIME terminal is used and the length of the specifiedor calculated output pulse is less than the MIN TIME value, nopulse is generated. The output pulse length is saved and added tothe output pulse length specified or calculated at the next rateexecution of the module. Pulse lengths equal to or greater than theMIN TIME value are rounded to the nearest integer multiple of aPDO or RPDO clock tick. Note that for Modes 1, 2, and 3, a pulselength equal to or greater than the MIN TIME value in secondsmay result in no pulse if it converts to less than 1 clock tick, ormay result in a pulse duration less than the MIN TIME specified,if the MIN_TIME value represents less than 1.5 times the time


Page PDO-18


period represented by an integer multiple of the clock tick.

C. Maximum Pulse Length and Task Rate

The output pulse direction and length are determined each timethe PDO or RPDO Module executes at its rate interval. The newinformation is applied to the output states at the next tick of thePDO or RPDO clock following module execution. Any previouspulses still in progress are superseded by the new calculations andmay be terminated. A new output pulse length replaces anyremaining time for a previous pulse in the same direction; a newoutput pulse direction and length terminates any previous pulse inthe opposite direction. If no output pulse is to be generated, anyprevious output pulse is terminated.

The above factors are critical when determining the rate intervalfor the module, especially when using Modes 0, 1, or 2. Becausethese modes have no feedback, or only partial feedback, correctoperation of the module depends on full completion of previouslyspecified or calculated outputs. The rate interval for a task con-taining a PDO or RPDO Module should therefore never be lessthan the time represented by the maximum tick count to begenerated for the application, plus 1. For example, if the RESO-LUTION is 100 making the module Tick = 2 seconds, and themaximum pulse duration for the application is 12 seconds or 6Ticks, the rate interval for the module should never be less than 7Ticks or 14 seconds.


Page PDO-19


PDORPDO

D. Power Failure

For PDO Module Only:

A power failure at the controller will terminate any pulse that isin progress unless the state is latched via a manual panel or otherexternal logic. When power is restored, the outputs may or maynot be updated, depending upon controller switch settings madeduring hardware configuration. See the appropriate controllerhardware manual for details.

For RPDO Module Only:

A power failure in the 3310/3330/3335 will not terminate the pulsein progress generated in the RIO 3331 Remote I/O Rack. Whethermore pulses are generated depends on RIO 3331 switch settings.See document CI-3335 for information. A power failure in the RIO3331, itself, will terminate the pulse. When power is restored tothe RIO 3331 the outputs may or may not be updated, again,depending upon Remote I/O Rack switch settings.

E. Redundant Switchover

Outputs active when a switchover occurs will continue normallyuntil completion or until updated by the first execution of the PDOor RPDO Module after the switchover, whichever occurs first. Notethat for Modes 1 and 2 a switchover could affect the calculation ofestimated position.

BLANK PAGE

PID3TERM PID Control Module

ACCOL II Reference Manual Page PID3TERM-1

DERIVATIVEINTEGRALPROPORTION

SETPOINT

INPUT

ERROR

OUTPUT

DEADBANDTRACKRESET

The PID3TERM Module provides a process control algorithm which allows proportional (P), proportional/integral (PI) or proportional / integral / derivative (PID) modes.

‘ Module Terminals

INPUT Default: None, entry required Format: Analog signal Input/Output: Input represents the measured variable (MV). SETPOINT Default: 0.0 Format: Analog signal or constant Input/Output: Input is the desired control point (setpoint) at which the measured variable should be held.

PID3TERM

PID Control Module


DEADBAND Default: 0.0 Format: Analog signal or constant Input/Output: Input must be a positive number. If the absolute difference between the newly calculated output and the present output is less than DEADBAND, then the OUTPUT terminal is not changed. When the difference exceeds the DEADBAND the OUTPUT terminal will be OUTPUT = OLD + (NEW - DEADBAND). When the newly calculated output is less than the last OUTPUT minus DEADBAND, the OUTPUT terminal value is OUTPUT = OLD - (NEW - DEADBAND). These calculations make OUTPUT lag behind the calculated output by the DEADBAND amount. Its purpose is to eliminate disturbances smaller than the deadband. PROPORTION Default: None. If left unwired, PROPORTION

and OUTPUT will be 0.0. Format: Analog signal or constant Input/Output: Input determines the amount of output change that will be produced by a change of error. The higher the number at this terminal, the higher the module gain. A value of 1.0 provides unity gain. When the PROPORTION value is positive, the module provides reverse-acting control i.e., the module output will decrease when the MV goes above the setpoint. When the PROPORTION value is negative, the module provides direct-acting control i.e., the module output will increase when the MV is above setpoint.



INTEGRAL Default: 0.0 Format: Analog signal or constant Input/Output: Input establishes the ‘reset’ rate in ‘repeats-per-minute’, for example, a value of 1.0 provides one ‘repeat’ per minute. A value of zero turns off integral action. Note: For proper operation of the PID3TERM module, when making use of the INTEGRAL terminal, the polarity of the value assigned to this terminal MUST be positive, regardless of the polarity of the PROPORTIONAL value. DERIVATIVE Default: 0.0 Format: Analog signal or constant Input/Output: Input establishes a scale factor to determine how much the rate-of-change of the MV (not error) affects the module output. The numerical entry for this terminal represents the amount of rate correction in minutes. The greater this number, the greater the correction. A value of zero will turn off derivative action. Note: For proper operation of the PID3TERM module when making use of the DERIVATIVE terminal, any value other than zero MUST have a negative polarity assigned to it, regardless of the polarity of the PROPORTIONAL value. RESET Default: None, entry is optional Format: Analog signal or constant Input/Output: Input (See explanation under ‘TRACK’.)

PID3TERM

PID Control Module


TRACK Default: None, entry is optional Format: Logical signal Input/Output: Input The RESET and TRACK terminals force the module output to a known value. They are used to prevent “reset windup” of the module output, to establish initial output values, and to provide transitions without ‘bumps’ when changing from manual to automatic mode. The TRACK signal is a logical input which, when set ON, forces the module output to follow the RESET terminal input value. It is used to gain control of the module output when conditions warrant it. The RESET and TRACK signals can come from any source as required. However, when the PID3TERM output is connected to an ANOUT module, these terminals are usually connected to the corresponding terminals on the ANOUT module. This usage provides automatic setting of TRACK and RESET if the output attempts to exceed 100% or 0%. Typical wiring for usage with an ANOUT module is shown below. Where manual control is desired other selection logic would be placed between the modules, as needed, to allow control of the RESET and TRACK signals.

DERIVATIVEINTEGRALPROPORTION

SETPOINT

INPUT

OUTPUT

DEADBAND

TRACK (ON)RESET

SPANZERO

ElectricalOutput

Control Wiring for Anti-Reset Windup



OUTPUT = K E - 60 K d (input)dt

t

tr

K x K60

(E)dt + Ip

p

pd

d

i

i

o

o

+

where:

E = Error (SETPOINT - INPUT)K = Proportional constant (gain)K = Integral time in repeats per minuteK = Derivative rate constant in minutest = Length of time that TRACK has been OFFtr = Time when TRACK signal went to OFFI = Initial value of the OUTPUT term when t=tr

OUTPUT Default: None, entry is optional Format: Analog signal Input/Output: Output is the calculated output value of the module after DEADBAND is applied. It is usually wired to the OUTPUT terminal of an ANOUT module as shown in the figure above. Initial OUTPUT values are established using TRACK and RESET. ERROR Default: None, entry is optional Format: Analog signal Input/Output: Output is the input error (SETPOINT - INPUT) of the module multiplied by -1.0.

‘PID Control Algorithm The PID3TERM Module performs the following process control equation:

PID3TERM

PID Control Module


‘ Module Operation

The module subtracts a measured variable input (MV) from a setpoint(SP) to obtain an error (difference) signal (E). The error is processed by the module to adjust an output signal which is used to control the external process. The module will adjust its output to drive the error towards zero. The MV input typically comes from a process sensor, and the SP from an internal signal; the module output is used to position an external control element. Should the MV deviate above or below the setpoint, the developed error signal (E) produces a change in Module output which adjusts the external process until input balance is restored and (E) is near zero. Output changes can be proportional to the error E, the integral of E over time, and the rate-of-change of E. The PROPORTION input establishes the ‘gain’ of the module, i.e., the amount that the output will change for a given input error E. The INTEGRAL input establishes a scaling factor for the integration of E (reset) in repeats-per-minute. A value of 1.0 provides one ‘repeat’ per minute, 2.0 provides two per minute, etc. A value of 0.1 provides a ‘repeat’ every 6 minutes. The DERIVATIVE input establishes a scaling factor for ‘rate’ correction in minutes; the factor determines how much the module output responds to the rate-of-change of the MV, not the error E. (Use of MV and not error E prevents changes to SETPOINT from causing large output swings when this input is non-zero.)

‘ Initial PID Process Settings

The Zeigler/Nichols method below provides a way to determine the closed-loop Proportional, Integral and Derivative settings for a process. It assumes that the final control element (process valve)



operates in a linear fashion and has been correctly sized for the process. This procedure will only provide initial settings. Final adjustments to achieve uniform control must be obtained by experimentation and user experience. Some processes may exhibit unstable or dangerous conditions which, if allowed to run out of control, could result in damage to property or injury to persons. Exercise caution during the tune-up procedure and use additional safety devices or manual backup equipment to keep the process under safe control. 1. Connect a chart recorder across the AO field wiring terminals

that represent the controller output. 2. Using the PEI (computer), enter an INTEGRAL setting of 0, and a

DERIVATIVE setting of 0. The initial Deadband value should be 0.

3. Determine whether the module should be direct or reverse acting.

If the module output should decrease when MV is above SETPOINT, reverse-action is required; direct-action is required otherwise. The PROPORTION value must be positive for a reverse-acting module, negative for a direct-acting module. If no previous startup values are available, a PROPORTION setting of 1.0 (+ or - as required) is recommended.

4. Bring the process up to setpoint manually, then switch to

automatic control. With the process operating, observe the tracings of the chart recorder. The output trace should be oscillating on both sides of the setpoint. If necessary, enter different PROPORTION values until one is found that produces oscillation.

5. Once the process oscillations stabilize, experiment with higher

and lower PROPORTION values and note the effect on the trace. If necessary, change the SETPOINT value by a small amount to initiate a process disturbance, thereby forcing the process to cycle.

PID3TERM

PID Control Module


6. If the PROPORTION value is too high, the output trace will have

steep edges and clipped peaks where it tries to go off-chart; if the value is too low, the trace will be of low amplitude and sluggish. Try to achieve a setting that produces a uniform, constant oscillation as the process stabilizes.

7. Once the oscillation cycles are uniform and steady, note the time

duration of one oscillation cycle on the chart. This measurement is defined as the time period (Pt) in minutes. Calculate the initial values for integral time and derivative rate using Pt as follows:

INTEGRAL (max) = 2 / Pt (min) DERIVATIVE (max) = - ( Pt (min) / 8 )

If the process is highly responsive, the derivative rate may not be required.

8. Once the INTEGRAL and DERIVATIVE values have been

entered, reduce the PROPORTIONAL setting to 1/2 of the value required to sustain oscillations.

9. If required, enter the desired DEADBAND value. A large

DEADBAND number produces a wide uncontrolled zone on either side of the setpoint. A zero value eliminates DEADBAND and provides instant process control reaction.

10.The above settings provide a starting point. Obtain the final

settings by experimentation.

Portstatus Module

Portstatus


Page Portstatus-1

The Portstatus Module may be used to perform two major functions. Itcan:

1) Collect on-line communication statistics for a port, and storethe collected information in a signal list or data array.

2) Adjust certain characteristics of a port, on-line.

BAUD_RATE

STOP_BITS

WORD_LENGTH

PARITY

DUPLEX

HANDSHAKE

CUSTOM_1

CUSTOM_2

TIMEOUT

PORTMODE

LISTARRAYCOLUMN

(statistics written tolist or array)

(port characteristicsread or changed)

STATUS

Communication Statistics

The Portstatus Module will collect on-line statistics for the followingport types:

● BSAP Master/Expanded Addressing Master● LIU Master● BSAP Slave/VSAT Slave/Serial CFE● LIU Slave● IEEE CFE

Portstatus


Page Portstatus-2

PortstatusPortstatus Module

● BSAP Pseudo-slave/Pseudo-slave with alarms● RIOR● Internet Protocol (IP)

The statistics collected are a function of the port being monitored andare the same as those which are available through the Toolkit Com-munications Statistics Display, or the Remote Communication Statis-tics Tool for Open BSI users. See 'Interpreting Port Statistics,' later inthis section, for details. Collection of statistics is also supported forsome Custom Port types. See the ACCOL II Custom Protocols Manual(D4066) for details.*

Adjusting Port Characteristics

The Portstatus Module supports reconfiguration of BAUD rate, andcertain other parameters for Logger Ports and Custom Ports.** Userswith AJ.10, C.03, or newer level firmware can also use the PortstatusModule to control DTR on a Slave or Pseudo Slave Port. Control ofDTR provides the ability to enable/disable communications on theassociated Slave or Pseudo Slave Port. (The system default at "coldstart" or system reset is to enable communications on all Slave orPseudo Slave Ports.)

Custom Port configurations which allow some adjustment in param-eter values are:

● Allen-Bradley PLC-2 Master● Allen-Bradley PLC-2 Slave● Enron Modbus Slave● Gould Modbus Master / Slave● HP 48000 Slave● Teledyne Geotech Slave

See 'Configuration', later in this section for details on using thePortstatus Module with a Logger Port. See the ACCOL II CustomProtocols Manual (D4066) for details on which parameters thePortstatus Module can change for a given custom port type.

* Custom port statistics are NOT available through Toolkit.��

��

Portstatus Module

Portstatus


Page Portstatus-3


PORT Default: None, entry requiredFormat: Analog signal or constantInput/Output: Input

identifies a predefined port. The value must be a number from 1 to 16:

Code: Port: Code: Port:1 Port A 6 Aux Port 2 or BIP_22 Port B 7 Port G3 Port C 8 Port H4 Port D 9 Port I5 Aux Port 1 or BIP_1 10 Port J

16 Internet Protocol (IP)

MODE Default: 0 (collect statistics)Format: Analog signalInput/Output: Input/Output

specifies the mode of operation. Valid mode values range from 0 to 9and indicate the function of the Portstatus Module. If an invalid modevalue is specified, an error will be reported. The mode signal is resetto 0 each time the module finishes executing.

Mode 0: Collect Statistics (Default Mode)

Statistics are collected for the port indicated by the PORT terminal.Statistics are stored in the signal list or data array named on theLIST or ARRAY terminal. Port types which maintain statistics arelisted at the beginning of this section. Statistics for other port typeswill be all zeros.

Mode 1: Read Characteristics

The port configuration characteristics are read from the portindicated by the PORT terminal, and stored in signals named onthe following terminals: BAUD_RATE, STOP_BITS,


Page Portstatus-4


WORD_LENGTH, PARITY, DUPLEX, HANDSHAKE, CUSTOM_1,and CUSTOM_2. Mode 1 applies only to Logger Ports, certainCustom Ports, and in Protected Mode 04.30 (or newer): BSAPasynchronous Master, EAMaster, Slave, Pseudo Slave, and PseudoSlave with Alarms Ports. Other port types, or Custom Ports whichdo not support Mode 1, will result in a -12 on the STATUS termi-nal.

Mode 2: Write Port Characteristics

The port configuration characteristics are obtained from the termi-nals listed above (BAUD_RATE, etc.) and are written to the portindicated by the PORT terminal. If any of the terminals contain aninvalid entry, an error will be reported and the port characteristicswill not be written. Mode 2 applies only to Logger Ports and certainCustom Ports. Other port types, or Custom Ports which do notsupport Mode 2, will result in a -12 on the STATUS terminal.(NOTE: Mode 2 requires that the STATUS terminal be wired.)

For those characteristics which you do not wish to change, or whichdo not apply to the port type, you may leave the terminals unwired.The port will retain the characteristics assigned in the originalACCOL load for positions which are unwired. Also, the characteris-tics which may be modified vary with the port type. For example, aparticular Custom protocol may allow you to change theBAUD_RATE but not the WORD_LENGTH or PARITY. In thesecases, those terminals will be ignored and the port will retain thecharacteristics assigned in the original ACCOL load, or which arefixed by the protocol definition, for those positions.

NOTE: Beginning with Protected Mode firmware PLS /PLX /PES/PEX 04.30, BAUD_RATE can be changed on-line for BSAP asyn-chronous Master, EAMaster, Slave, Pseudo Slave, and PseudoSlave with Alarms Ports.

Mode 3: Reset Port Characteristics

The configuration characteristics of the port indicated by the PORTterminal are reset to those contained in the original ACCOL load.

Portstatus Module

Portstatus


Page Portstatus-5

Mode 3 applies only to Logger Ports and certain Custom Ports.Other port types, or Custom Ports which do not support Mode 3,

will result in a -12 on the STATUS terminal. (NOTE: Mode 3requires that the STATUS terminal be wired.)

Mode 4: Clear Statistics

Communications statistics for the indicated port are reset to zero.

Mode 5: Turn DTR ON (Requires AJ.10, C.03 or newer PROMs)

This mode will cause DTR on the selected Slave or Pseudo SlavePort to be turned ON. This enables the communication port toaccept and process messages from the master device. If this mode isselected when DTR is already ON for the selected port, then noaction is performed, and the STATUS terminal is set to "nochange." See STATUS.

Mode 6: Turn DTR OFF (Requires AJ.10, C.03 or newer PROMs)

This mode will cause DTR on the selected Slave or Pseudo SlavePort to be turned OFF. This terminates any active communicationon this port, and disables the communication port. DTR will remainOFF, and communications on the associated Slave or Pseudo SlavePort will remain disabled, until re-enabled by the user (see Mode 5)or a system reset (cold start) occurs. Warm initialization following apower-off/power-on sequence, however, will not change the status ofDTR. If this mode is selected when DTR is already OFF for theselected port, then no action is performed, and the STATUS termi-nal is set to "no change." See STATUS.

Mode 7: Report DTR Status (Requires AJ.10, C.03 or newer PROMs)

This mode will cause the DTR ON/OFF state to be reported ascodes on the STATUS terminal. See STATUS.


Page Portstatus-6


Mode 8: Set Enron Modbus

This forces an on-line mode change to the slave port from a GouldModbus Slave to an Enron Modbus Slave. This mode requires PLS/PLX/PES/PEX04.40 or newer firmware and PCP/PCE04.40 customfirmware or TeleFlow/TeleRTU 01.28 firmware, or newer.

Mode 9: Set Gould Modbus

This forces an on-line change to the slave port from an EnronModbus Slave to a Gould Modbus Slave. This mode requires PLS/PLX/PES/PEX04.40 or newer firmware and PCP/PCE04.40 customfirmware or TeleFlow/TeleRTU 01.28 firmware, or newer.

LIST Default: None, if unwired or invalid, theARRAY terminal is used.


is the number of the signal list which will receive port communicationsstatistics when the MODE terminal is 0. Listed below is the minimumnumber of signals in the signal list (or rows for a data array) you willneed to capture all the data. If the list is shorter than recommendedbelow, the module will provide as many statistics as possible. No errorwill be reported for a short list or array. The number in brackets isthe size required if the port is a 3330/3335 RASCL port.

Signals SignalsPort or Rows Port or RowsMaster 8 [16] LIU Slave 16Exp. Master 8 IEEE CFE 8LIU Master 16 Pseudo-Slave 6 [16]Pseudo-Slave w Alarms 6 [16] Slave 6 [16]Serial CFE 6 [16] VSAT Slave 6RIOR 8 [16] LIU Slave 16

‘Interpreting Port Statistics’ describes the contents of the signal list ordata array for each type of port.

Portstatus Module

Portstatus


Page Portstatus-7

ARRAY Default: None, if LIST is unwired orinvalid, ARRAY is used.


is the number of the analog read/write data array which will receivecommunications statistics when the mode is set to 0. In order to writeto this data array, the LIST terminal must be unwired or contain aninvalid entry.

Follow the guidelines above under LIST to create the correct numberof rows in the data array. When the array contains more than onecolumn, the statistics will be written to the first column unless indi-cated otherwise by the COLUMN terminal. ‘Interpreting Port Statis-tics’ will show you how to interpret the contents of the data array foreach type of port.


specifies the column in the data array which will receive communica-tions statistics. If an invalid column number is entered, no data iswritten to the array.

The following terminals are used to read or change port characteris-tics, depending on the setting of the MODE terminal. Note that forMODE 1, 'Read Characteristics', these terminals must be analogsignals, not constants.

BAUD_RATE Default: NoneFormat: Analog signal or constantInput/Output: Input/Output

Valid entries include 110, 150, 300, 600, 1200, 2400, 4800, 9600, 19200(12 or 20 Mhz units only), 38400 (12 or 20 Mhz units only).


Page Portstatus-8


STOP_BITS Default: NoneFormat: Analog signal or constantInput/Output: Input/Output

Valid entries are 1, 1.5, and 2 stop bits.

WORD_LENGTH Default: NoneFormat: Analog signal or constantInput/Output: Input/Output

Valid word lengths include 6, 7, or 8 bits.

PARITY Default: NoneFormat: Analog signal or constantInput/Output: Input/Output

Enter 0 for no parity, 1 for odd parity, or 2 for even parity.

DUPLEX Default: NoneFormat: Analog signal or constantInput/Output: Input/Output

This terminal is valid for a Logger Port only and specifies the inputprocessing mode. A value of 1 indicates TTY mode. 0 indicates halfduplex. (See 'Communication Ports', in this manual, for details.)

HANDSHAKE Default: NoneFormat: Analog signal or constantInput/Output: Input/Output

specifies the output handshaking technique and is used only for aLogger Port. 0 indicates no handshaking, 1 indicates hardware hand-shaking (RTS/CTS), and 2 indicates software handshaking (XON/XOFF). (See 'Communication Ports', in this manual for details.)

Portstatus Module

Portstatus


Page Portstatus-9

CUSTOM_1 Default: NoneCUSTOM_2 Format: Analog signal or constant

Input/Output: Input/Output

represent parameters P1 and P2 for the Custom Port. The valid rangefor CUSTOM_1 is 0 - 255, and the valid range for CUSTOM_2 is 0 -65,535. Values outside of these ranges will be ignored. The actual useof these parameters is dependent on the type of interface. See 'Cus-tom' in this manual, and the ACCOL II Custom Protocols Manual,document# D4066.

TIMEOUT

This terminal is not available for use at this time.


displays a status code which is set each time the module executes.NOTE: because the module automatically defaults to MODE 0 aftereach execution, the STATUS code for other modes must be examinedbefore the next execution of the module, or the code will be lost.

Code Meaning-14 Invalid baud rate for 6 Mhz CPU-13 Timeout occurred on a Mode 2, 3, 5, 6 or 7 operation.-12 Mode value out of range, or invalid mode for port selected, or

port busy. Enter correct mode value, or retry if port was busy.-11 Not a valid list number-10 Signal list contains no signal names -9 Invalid column selected on COLUMN terminal

-8 Array not valid (Does not exist, or wrong type)-7 Invalid entry on HANDSHAKE terminal

-6 Invalid entry on DUPLEX terminal -5 Invalid entry on PARITY terminal

-4 Invalid entry on STOP_BITS terminal


Page Portstatus-10


Code Meaning (continued)-3 Invalid character length on WORD_LENGTH terminal-2 Invalid baud rate on BAUD_RATE terminal-1 Invalid port code on PORT terminal

0 Statistics collection completed 1 Port characteristics have been read (Mode 1)

2 Write port operation completed (Mode 2) 3 Port characteristics have been reset (Mode 3) 4 Statistics have been cleared (Mode 4)

5 DTR ON request is successfully processed (Mode 5) 6 DTR OFF request is successfully processed (Mode 6) 10 No statistics collected (ARRAY and LIST terminals both

unwired) 11 DTR is ON 12 DTR is OFF 13 Requested DTR state already exists. No change made (Mode 5

or 6)

❏ ConfigurationIn order for the Portstatus Module to work, the ACCOL load mustdefine the communication ports before the load is placed in the con-troller. Once the load is running, the Portstatus Module cannot makeport assignments. For example, if you created the load, and left Port Aundefined, the Portstatus Module cannot change it to a Slave Portwhen the load is running in the controller.

Also, once the port type has been assigned, it cannot be changed bythe Portstatus Module. For example, the Portstatus Module cannotchange a Master Port to a Slave Port.

Port assignments are made on the Communications ConfigurationMenu (if you’re using the ACCOL II Interactive Compiler) or in the*COMMUNICATIONS section of the ACCOL source file (if you’reusing the ACCOL Workbench, or the ACCOL Batch Compiler).

Portstatus Module

Portstatus


Page Portstatus-11

Collecting Statistics

To collect statistics from a port, follow these steps to set up thePortstatus Module. The port types which maintain statistics are listedat the beginning of this chapter.

Step 1. Specify the port you want to monitor on the PORT terminal,or enter a signal name on this terminal if you want to usethe same module to collect statistics from different ports.

Step 2. Enter a signal name on the MODE terminal. The module'sdefault mode is 0 (collect statistics.) Mode 4 clears allstatistics to zero for the port selected on the PORT terminal.

Step 3. Create a signal list or analog R/W data array which willreceive the statistics, then indicate the signal list number ordata array number on the ARRAY or LIST terminal.

Step 4. If you’re collecting statistics in a data array, you may specifythe column on the COLUMN terminal. This is useful whenyou’re using the same data array to collect statistics fromseveral ports. When you change the PORT assignment on-line (either manually with Toolkit or DataView, or automati-cally via ACCOL logic), you can change the COLUMNterminal to the appropriate column.

Step 5. Enter a signal name on the STATUS terminal that will storestatus and error codes.

Changing Port Characteristics

To change port characteristics for a Logger port, a Custom port, or oneof the BSAP ports*, follow the instructions outlined below. Note: Notall Custom port types support on-line reconfiguration. See the ACCOLII Custom Protocols Manual (document# D4066) for details.

�� !�� "�#� ��"�#� ��"�#��"� ��$��""��%&'(�)!��#��


Page Portstatus-12


Step 1. Specify the port you want to configure on the PORT termi-nal, or enter a signal name on this terminal if you want touse the same module to reconfigure different ports.

Step 2. Enter a signal name on the MODE terminal. The module'sdefault mode is 0 (collect statistics.) Modes 1,2, and 3 are seton-line (either manually with Toolkit or DataView, orautomatically through ACCOL programming) to read, write,or reset a port's characteristics.

Step 3. Enter a signal name on the STATUS terminal. This isrequired for Modes 2 and 3 to function.

Step 4. Enter signal names on the following terminals, as needed:

For a Logger port, the BAUD_RATE, DUPLEX, HAND-SHAKE, STOP_BITS, WORD_LENGTH, and PARITYterminals apply.

For a Custom port, the BAUD_RATE, STOP_BITS,WORD_LENGTH, PARITY, CUSTOM_1, and CUSTOM_2terminals apply.

For one of the BSAP ports*, the BAUD_RATE terminalapplies.

In Mode 1, the value of these signals will be automaticallyset to the current port characteristics when the moduleexecutes.

If you want to change any or all of these characteristics,change the signal value of the appropriate terminal(s), thenset the Mode to 2. To avoid status errors, make sure allterminals contain valid values or, for those characteristicsyou do not wish to change, or which do not apply, you mayleave the terminals unwired. Note also that Custom Portapplications are individually defined and the characteristicswhich may be changed on-line may vary. To reset the portcharacteristics back to their settings as defined in the

�� !�� "�#� ��"�#� ��"�#��"� ��$��""��%&'(�)!��#��

Portstatus Module

Portstatus


Page Portstatus-13

original ACCOL load, set the Mode to 3.

After executing Mode 2 or Mode 3, set the Mode to 1 to readback and verify the port's current settings.

❏ Interpreting Port Statistics

This section will help you interpret the statistics that are collectedthrough Mode 0.

Below is listed the meaning of each entry in the signal list or each rowin the data array. The first entry in the list below corresponds to thefirst signal in the signal list or the first row in the data array. If you’vespecified a data array on the ARRAY terminal and you have entered anumber other than 0 or 1 on the COLUMN terminal, each column inthe data array represents a separate port. If you’ve specified a listthat contains logical signals, the signal will be set to OFF if theassociated statistic is 0, otherwise the signal will be set to ON.

Master/Expanded Master Port (Entries 9 to 16 apply to RASCLMaster Ports only)

Signal no.or row no. Message1 Messages Received2 Data and Poll Messages Transmitted3 Response Timeouts4 Consecutive Response Timeouts5 Naks Received6 CRC Errors


Page Portstatus-14


Signal no.or row no. Message (continued)7 Message Discarded Acks Received8 Protocol, Overflow or Serial Number Errors9 Transmit Link1 Errors10 Transmit Link2 Errors11 Receive Link1 Errors12 Receive Link2 Errors13, 14 Not Used15 Link1 Errors (receive and transmit)1.

16 Link2 Errors (receive and transmit)2.

LIU Master

Signal no.or row no. Message1 Messages Received2 Data and Poll Messages Transmitted3 Timeouts due to No Ack4 Consecutive Response Timeouts5 Poll Timeout Errors6 Frame Check Errors7 Transmit Underruns8 Transmit Link 1 Errors9 Transmit Link 2 Errors10 Receive Overruns11 Receive Aborts12 Receive Buffer Overflows13 Receive Link 1 Errors14 Receive Link 2 Errors15 Link1 Errors (Receive & Transmit)1.

16 Link2 Errors (Receive & Transmit)2.

1. System signal #LINKE.001 or #LINKF.001 may be specified in this position when thePORT terminal specifies Aux Port 1 or Aux Port 2, respectively, or a RASCL Port isspecified. See 'System Signals' for more details.

2. System signal #LINKE.002 or LINKF.002 may be specified in this position when thePORT terminal specifies Aux Port 1 or Aux Port 2, respectively, or a RASCL Port isspecified. See 'System Signals' for more details.

Portstatus Module

Portstatus


Page Portstatus-15

Slave, VSAT Slave, Serial CFE, Pseudo Slave, and Pseudo Slave WithAlarm Ports (Entries 7 to 16 apply to RASCL ports only; RASCL doesnot apply to VSAT Slave.)

Signal no.or row no. Message

1 Messages Received2 Messages Transmitted3 Polls Received4 Messages Aborted for Transmit Queue5 Naks Issued6 Message Discarded Acks Issued7 Transmit Link1 Error8 Transmit Link2 Error9 Receive Link1 Error10 Receive Link 2 Error11-14 Not Used15 Link1 Errors (Receive and Transmit)1.

16 Link2 Errors (Receive and Transmit)2.

CFE (IEEE Interface)


1 Messages Received2 Messages Transmitted3 Polls Received4 Naks Issued5 Messages Discarded Acks Issued6 CRC Errors7 Timeout Hardware Resets8 Out of Memory Errors

1., 2. See notes on previous page.


Page Portstatus-16


LIU Slave


1 Messages Received2 Message Transmitted3 Polls Received4 Messages Aborted for Transmit Queue5 Transmit Underruns6 No Acknowledges7 Transmit Link 1 Errors8 Transmit Link 2 Errors9 Receive Frame Check Errors10 Receive Overruns11 Receive Aborts12 Receive Buffer Overflows13 Receive Link 1 Errors14 Receive Link 2 Errors15 Link1 Errors (Receive & Transmit)3.

16 Link2 Errors (Receive & Transmit)4.

3. System signal #LINKE.001 or #LINKF.001 may be specified in this position when thePORT terminal specifies Aux Port 1 or Aux Port 2, respectively, or a RASCL port isspecified. See 'System Signals' for more details.

4. System signal #LINKE.002 or LINKF.002 may be specified in this position when thePORT terminal specifies Aux Port 1 or Aux Port 2, respectively, or a RASCL port isspecified. See 'System Signals'.

Portstatus Module

Portstatus


Page Portstatus-17

RIOR Port (Entries 9 to 16 apply to RASCL RIOR ports only)


1 Transaction Attempts2 Successful Completions3 CRC Events4 CRC Errors5 Overflow Events6 Overflow Errors7 Timeout Events8 Timeout Errors9 Transmit Link1 Errors10 Transmit Link2 Errors11 Receive Link1 Errors12 Receive Link2 Errors13-14 Not Used15 Link1 Errors (receive and transmit)3.

16 Link2 Errors (receive and transmit)4.

3, 4. See notes on previous page.


Page Portstatus-18


b

Internet Protocol (IP) Port


1 Packets Received (Unicast) - The number of non-broad-cast packets received at the current port. NOTE: Packetsreceived includes both invalid packets (see RCV errorsbelow), and packets being routed through the RTU.

2 Packets Sent (Unicast) - The number of non-broadcastpackets sent from the current port.

3 Characters Received - The number of characters receivedat the port. This includes all protocol characters, andcharacters included within badly formed packets.

4 Packets Received (Multi) - The number of broadcastpackets received. These are mostly found on LANs suchas Ethernet, and are information requests, such aslocating a specific IP address.

5 Rcv Messages Discarded - The number of packets dis-carded due to frame-check errors (such as invalid check-sums).

6 Rcv Messages (Errors) - A catch-all error for invalidframes, which have been discarded.

7 Rcv Messages (Bad Protocol) - The number of messages,with valid format and checksums, which have beendiscarded due to containing an invalid protocol.

8 Characters transmitted. The number of characters sentout the port. This includes all protocol characters.

9 Packets sent (Multi) - The number of broadcast packetssent. These are mostly found on LANs such as Ethernet.

10 Send Messages (Bad Protocol) - Should always be 0.11 Send Errors - A catch-all error for invalid send frames.

These frames are discarded. Errors in this type includeattempting to send a packet which is too large.

Page Process I/O-1


Process I/O

Input and output modules, like ANIN and RANIN, contain severalterminals that specify the type and number of field I/O signals.

The DEVICE terminal identifies the slot number in the 33xx unitwhere the Process I/O Board is installed. INPUT and OUTPUTterminals in the ACCOL modules contain signals whose values will besent to/received from the process I/O board referenced on the DEVICEterminals.

The table below indicates the maximum number of process I/O boardsallowed in each type of 33xx unit:

33xx Controller/Device: Maximum number of boards allowed:

CFE 3385 /UCS 3380 4

DPC 3330 6 or 12 depending upon model used

DPC 3335 9 or 10 depending upon model used

GFC 3308 Varies depending upon model used

RDC 3350 3

RIO 3331 10

RTU 3310 4

3530 (EGM or RTU) I/O options vary; up to 5 slots specified.

RTU 3305 All I/O resides on a single multi-functionboard, although it is referred to as 4 slots.

The type and number of ACCOL signals on the INPUT or OUTPUTmodule terminals must match the number and type of signals on theProcess I/O Board.*

Process I/O

* Beginning with Protected Mode 04.30 firm-ware, these restrictions have been loosened forcertain boards. See page 4 of this section.


Page Process I/O-2

Process I/O

The tables that follow list the available boards for each controller:

DPC 3330, DPC 3335, RIO 3331, RTU 3310Board Type Maximum Number

of I/O SignalsFor This Board

MinimumRequirements

Analog InputBoard

4 analog inputs

Analog InputBoard

8 analog inputs ACCOL 5.7 and AHPROMs (ornewer); RIO 3331users requireC.01 PROMs (ornewer)*

Analog OutputBoard

2 analog outputs

Analog OutputBoard

4 analog outputs Requires ACCOL5.7 with AHPROMs (ornewer); RIO 3331users requireC.01 PROMs (ornewer)*

Check BeforeOperate

8 relay discreteoutputs

Requires ACCOL5.5 with AFPROMs (ornewer); NotAvailable forRIO 3331

Discrete InputBoard

8 5-volt, or 812-volt, or 824-volt, or 4120-volt AC/DC

* RIO 3331 users using this board must have ACCOL 5.9 and AK PROMs in their 3310/ 3330/3335.

Page Process I/O-3


Process I/O

DPC 3330, DPC 3335, RIO 3331, RTU 3310 (continued)

* RIO 3331 users using this board must have ACCOL 5.9 and AK PROMs in their 3310/ 3330/3335.

Board Type Maximum Numberof I/O SignalsFor This Board

MinimumRequirements

Discrete InputBoard

16 5-volt, or 1612-volt, or 16 24-volt, or 16 24-volt AC/DC

Requires ACCOL5.9 with AKPROMs (ornewer); RIO3331 usersrequire C.01PROMs (ornewer)*

Discrete OutputBoard

8 open collectoror 4 relay

Discrete OutputBoard

16 open drain Requires ACCOL5.11 withAL.00/ RMS01(or newer)firmware. RIO3331 usersrequire RIO 4.0firmware (ornewer).

High SpeedAnalog InputBoard

4 channels Requires ACCOL5.1 with AC.1PROMs (ornewer); Notavailable withRIO 3331

High SpeedCounter

4 counters

High DensityHigh SpeedCounter Board

8 counters RequiresProtected ModePLS 04.40 (ornewer); notavailable forRIO 3331


Page Process I/O-4

Process I/O

Board Type Maximum Numberof I/O SignalsFor This Board

MinimumRequirements

Honeywell SmartTransmitterInterface

8 channels Requires ACCOL5.5 with AFPROMs (ornewer); Notavailable withRIO 3331

Low Level AnalogInput

4 channels Requires ACCOL5.0 (or newer)

Bristol TeletransInterface (BBTI)Board

8 channels(board must bedefined asGlobal BBTI orLocal BBTI)

Requires ACCOL5.8 with AJPROMs (ornewer); Notavailable withRIO 3331

DPC 3330, DPC 3335, RIO 3331, RTU 3310 (continued)

Beginning with Protected Mode 04.30 firmware, boards defined inACCOL software as high density (8AI / 4AO / 16DI / 16DO) canreference all physical I/O points on low density hardware (4AI / 2AO /8DI / 8DO), respectively. Conversely, I/O points on high densityhardware (8AI / 4AO / 16DI, 16DO) can be referenced by boards inACCOL software defined as low-density (4AI / 2AO / 8DI / 8DO),respectively; only the I/O points encompassed by the low densitysoftware definition can be referenced, however.

��

Page Process I/O-5


Process I/O

The following table lists the available I/O options for the GFC 3308.Not all models of the GFC 3308 support all configurationoptions1.

GFC 3308

Analog Input: 1 analog input (optional on Power Supplyboard)

I/O Process Board: 3 analog inputs1 analog output1 RTD input

Discrete I/O Board: Any combination of up to 6 discreteinputs or outputs and optional Port Dinterface

High Speed Counter: 1 High Speed Counter (on the(HSC) Power Supply board)

1. For details on configuration options see the CI-3308 and CI-3308-Bmanuals.

RDC 3350, UCS 3380, CFE 3385

Board Maximum number of I/O signals

Mixed I/O Board 8 analog input, 4 analog output,32 digital input, 16 digital output,2 high speed counter channels

Digital I/O Board 48 digital input, 32 digital output

Analog I/O Board 24 analog input, 8 analog output


Page Process I/O-6

Process I/O

Board Type

Maximum Number of

I/O Signals For This

Board

Minimum

Requirements

Digital Input (in Slot 1;all slots refer to asingle Multi-FunctionI/O Board. 8 DI’s (#7through #14) are alwayspresent, each of theremaining 6 points (#1through #6) arehardware-selectable aseither DI’s or DO’s)

8 to 14 depending uponnumber of DO signalsdefined in Slot 2.NOTE: Only points #7through #14 supportinterrupts, which arenecessary when usingfeatures such as PDM,LSCOUNT, or WAITDI’s.

ACCOL 5.13 tools,LS500 firmware

Digital Output (in Slot2; all slots refer to asingle Multi-FunctionI/O Board. 2 DO’s (#7and #8) are alwayspresent, each of theremaining 6 points (#1through #6) arehardware-selectable aseither DI’s or DO’s.)

2 to 8 signals,depending upon numberof DI signals defined inSlot 1.

ACCOL 5.13 tools,LS500 firmware

Analog Input (in Slot 3;all slots refer to asingle Multi-FunctionI/O board.)

4 signalsACCOL 5.13 tools,LS500 firmware

Analog Output (in Slot4; all slots refer to asingle Multi-FunctionI/O board.)

2 signalsACCOL 5.13 tools,LS500 firmware

RTU 3305

Page Process I/O-7


Process I/O

EGM 3530-series TeleFlow

Board Name - EGM 3530-seriesTeleFlow

Maximumnumber ofI/O signalsfor this board

Minimum Requirements

3530 - Digital Input board: 2 points to 10points

2 DI’s (#1 and #2) are always present; eachof the remaining 8 points are softwareselectable (via ACCOL module usage) aseither DI’s or DO’s. They are shared with theboard in Slot 2. Do NOT specify a point tobe BOTH a DI and a DO because results areindeterminant.

Only allowed in Slot 1

2 to 10 ACCOL Workbench (RM)1.1 or newer

TFA01 or newer firmware

3530 - Digital Output board: 2 points to 10points

2 DO’s (#1 and #2) are always present; eachof the remaining 8 points are softwareselectable (via ACCOL module usage) aseither DO’s or DI’s. They are shared with theboard in Slot 1. Do NOT specify a point tobe BOTH a DO and a DI because results areindeterminant.




3530 - Analog Input board: 1 point or 5points


1 or 5 ACCOL Workbench (RM)1.1 or newer


3530 - High Speed Counter board: 1 point or2 points




3530 - Analog Output board: 1 point


1 ACCOL Workbench (RM)1.1 or newer



Page Process I/O-8

Process I/O

RTU-3530-series TeleRTUBoard Name - RTU 3530-seriesTeleRTU

Maximumnumber ofI/O signalsfor this board

Minimum Requirements

3530 - Digital Input board: 2 pointsor 10 points

2 DI’s (#1 and #2) are alwayspresent; each of the remaining 8points are software selectable (viaACCOL module usage) as either DI’sor DO’s. They are shared with theboard in Slot 2. Do NOT specify apoint to be BOTH a DI and a DObecause results are indeterminant.



TRA01 or newer firmware

3530 - Digital Output board: 2 pointsto 10 points

2 DO’s (#1 and #2) are alwayspresent; each of the remaining 8points are software selectable (viaACCOL module usage) as eitherDO’s or DI’s. They are shared withthe board in Slot 1. Do NOT specifya point to be BOTH a DO and a DIbecause results are indeterminant.




3530 - Analog Input board: 4 pointsor 8 points




3530 - High Speed Counter board: 2points or 3 points




3530 - Analog Output board: 1 point


1 ACCOL Workbench (RM)1.1 or newer


Questionable-DataQ Data

Page Ques Data-1


❑❑❑❑❑ Questionable Data Bit

There is a Questionable Data bit associated with every ACCOL analogsignal. This bit is set to indicate that the data value of the signal maynot be valid. The state of the Questionable Data bit is automaticallycontrolled for certain analog signals associated with the ACCOLProcess I/O Modules listed below. This bit is also accessible using theCALCULATOR Module :Q: operator for read, write, and test opera-tions. If you are using On-Line AIC, the status of this bit appears onthe AIC Online Signal Menu as “Questionable Data” if the bit is set, or“Valid Data” if the bit is not set. The state of the bit can be controlledfrom that menu.

Display of the Questionable Data Bit is also supported from otherexternal interfaces e.g. Toolkit, Enterprise Windows, and DataView.

The Questionable Data bit is set or cleared automatically for certainanalog signals to warn of possible invalid data. In some cases, detailedbelow, the hardware also imposes limits to provide input circuitprotection against overranging. The ACCOL modules which supportautomatic control of Questionable Data status are:

ANIN Analog Input Module

RANIN Remote I/O Analog Input Module

LLANIN Low Level Analog Input Module

RLLANIN Remote I/O Low Level Analog Input Module

PDM Pulse Duration Modulation Module

RPDM Remote I/O Pulse Duration Modulation Module

HWSTI Honeywell Smart Transmitter Interface Module

BBTI Bristol Teletrans Interface Modules (GBBTI, LBBTI)

Questionable Data Bit


Page Ques Data-2


❑❑❑❑❑ ANIN/RANIN Modules

Although the AI input circuitry is designed to accept a high commonmode overload without damage, the 33XX input circuits are clamped atlevels of 105% for maximum range, and -5% for minimum range. Forexample, for a 0 to 10 V input signal, these limits are 10.496 V formaximum range and -0.5 V for minimum range. Therefore the inputsignal, relative to the internal circuitry cannot extend beyond theselimits during an overrange or underrange condition.

An overrange or underrange condition is also detected in software.These limits occur at 2.5% above and below normal operating range toprovide limits at 102.5% and -2.5%, respectively to set the Question-able Data bit. The ACCOL analog signal associated with an analoginput on ANIN or RANIN Modules will have its Questionable Data bitcleared when the input is within the above limits and set if the input isin violation of these limits.

The RANIN Module also sets the Questionable Data bit if:

1) Communication fails with the RIO unit

2) RIO status indicates that the AI board is not ready—this canoccur immediately after a reset of the RIO unit

For both of these cases the signal’s data value is not modified; itretains its current value.


Page Ques Data-3


❑❑❑❑❑ LLANIN/RLLANIN Modules

Thermocouples and RTDs

Underrange and overrange conditions for the thermocouples and RTDinput signals are detected on the Low Level AI Board. When the boarddetermines that the signal is below an acceptable range, it will sendthe module a value which is equal to the lowest acceptable value less5% times the span. Take, for example, a Type E thermocouple whoserange of operation is -2700C to +10000C. The span of this device is 1000- (-270) or 1270 degrees. When the board detects an underrangecondition, it sends the module a value which equals -270 less 5% ofspan. In other words,

(lowest value) - (span * 0.05) = -270 - (1270 * 0.05) = -333.5

The LLANIN or RLLANIN Module recognizes that -333.5 is below thenormal range for this type of thermocouple and sets the questionabledata bit. The module will continue to process this input as usual,multiplying this value by the SPAN and adding the value of the ZEROterminal. The result will be placed on the INPUT terminal of themodule. Notice that for all underrange conditions, the Low Level AIBoard will always send the module a value which is below the lowestnormal range by 5% times the span of the device.

For an overrange condition in the thermocouples and RTDs, the valuethat the module receives is the highest acceptable value plus 5% of thespan. In the case of the Type E thermocouple, this will be 1000 + (1270* 0.05) or 1,063.50C. When this value is received by the module, thequestionable data bit is set and the value is processed using the valuesentered on the SPAN and ZERO terminals.


Page Ques Data-4


Voltage Inputs

Detecting out of range conditions for the voltage inputs is done differ-ently. Any underrange or overrange condition which is less than 1% isignored. If the input is more than 1% above or 1% below the normaloperating range, that value is sent to the module. However, this valuewill not exceed 2.5%, since that is the maximum deviation that can bedetected by the Low Level AI Board. When this value is received bythe module, the questionable data bit is set and calculations involvingthe ZERO and SPAN terminal values are performed.

The RLLANIN module also sets the Questionable Data bit if:

1) Communication fails with the RIO unit

2) RIO status indicates that the LAI board is not ready (this canoccur immediately after startup (e.g., as a result of reset of theRIO unit or download of the Host Unit).

For both of these cases, the signal's data value is not modified; itretains its current value.

❑❑❑❑❑ PDM/RPDM Modules

For Input Type 5 - Variable Length Pulse Accumulation, the Question-able Data bit will be set to indicate a questionable measurement if anoverflow occurs (the total length of all pulses since the previous moduleexecution exceeds 65.534 seconds), or if a power failure occurs duringpulse measurement.

Any user action on QD must be taken before the next execution of themodule. A valid reading at the next execution will clear the QD flagand add the new reading to the previously-accumulated total, whichcould contain bad data.


Page Ques Data-5


❑❑❑❑❑ HWSTI Module

The Honeywell Smart Transmitter Interface Module sets the Question-able Data bit for the Process Variable (PV) and Secondary Variable(SECVAR), as well as various configuration parameter signals. See the'HWSTI' section for details.

❑❑❑❑❑ BBTI Modules (GBBTI, LBBTI)

The Bristol Teletrans Interface Modules (GBBTI and LBBTI) set theQuestionable Data bit for errors in process variable data (differentialpressure, static pressure, RTD, or estimated sensor temperature) fromthe transmitter. The Questionable Data bit is also set for variousconfiguration error conditions. See the 'BBTI Modules' section fordetails.

❑❑❑❑❑ :Q: Operator in the CalculatorThe Questionable Data bit is accessible via the “:Q:” operator. Thisoperator can be included in Calculator Module calculations to read,write, or test the state of the Questionable Data bit for any analogsignal. The operator’s function is determined by its location in thedestination or expression field.

For a read or fetch operation, the :Q: operator is placed in the expres-sion field preceding the name of the signal whose Questionable Datastatus will be carried. The destination field will contain the name ofthe logical signal or logical entity which will receive the status.


Page Ques Data-6


Examples:

LOGIC.STROBE = :Q:ANI.TEM.1

#LDATA 3[2,1] = :Q:ANI.TEM.1

For a write or store operation, the :Q: operator precedes the signalname in the destination field. The desired bit state, or the logicalentity/expression which is the source of the bit state, is indicated in theexpression field. In the third example below, the Questionable Datastatus of the signal ANA.SIG will be cleared if the signal’s value isbetween 0.0 and 100.0 or set if the value is above or below that range.

Examples:

:Q:ANI.TEM.1 = #OFF

:Q:ANI.QD.STAT = :Q:ANI.TEM.1

:Q:ANA.SIG = ((ANA.SIG > 100.0)|(ANA.SIG < 0.0))

For a test operation, the :Q: operator precedes the signal name in acontrol statement. The result of the test is then used to control theexecution of subsequent statements. In the following example, if theQuestionable Data bit for the signal ANA.SIG is True (that is, if thesignal data is invalid), the logical signal LOGIC.STROBE will be set toTrue.

Example::IF(:Q:ANA.SIG)

LOGIC.STROBE=TRUE:ENDIF

RBE

Report By Exception

ACCOL II Reference ManualPage RBE-1

❑ Report By ExceptionCentral data collection systems, such as Enterprise Server’s TemplateData Collection system, collect data from all global signals in a 33XXremote process controller, whether or not they have changed. If thereare several 33XX controllers in a network, and each controller has manysignals which change infrequently, there may be a significant waste ofcommunication resources in repeatedly collecting data, most of whichhas not changed since the previous collection.

In order to reduce the burden on network communications, any ACCOLanalog or logical signals which change infrequently, and are not ofcritical importance, should be designated for Report By Exception(RBE). Data from such signals (referred to as RBE signals) is collectedonly when the signals are said to be “in exception”. An RBE signal isconsidered to be in exception when:

● its status changes from ON to OFF or from OFF to ON (logicalRBE signals only)

● its value changes from its last reported value by more than a pre-configured RBE deadband (analog RBE signals only)

● its manual, control, or alarm enable/inhibit bits have beenchanged

Each remote process controller configured for Report By Exception mustinclude an RBE Module and 1 or more ACCOL signals designated forRBE. These RBE signals (with deadbands for analog signals) are auto-matically stored in the RBE Data Base. The RBE Data Base is periodi-cally checked to see if any RBE signals have gone into exception. If theyhave, a message containing the changed data, called an exceptionreport, is sent to a program at the network central called the RBEManager.

RBE

RBE

Report By Exception


The RBE Manager is responsible for distributing the data to otherprograms at the central. In the case of Enterprise Server, for example,the RBE Manager sends the changed data to the Enterprise Real TimeData Base.

RBE

Report By Exception


❑ Requirements for Using RBEIn order to use RBE for a particular remote process controller, thefollowing requirements must be met:

1. Each controller using RBE must be a 3305/3308/3310/3330/3335series controller using ACCOL version 5.5 (or newer tools, asappropriate) and AF.00/C.01/LS500 (or newer) firmware.

2. The RBE Module must be included in the controller’s ACCOLload. Usually it is placed in Task 0, since it is a non-executingmodule. Depending upon the initialization mode used, certainmodule terminals need not be configured.

3. One or more signals for which the Report by Exception function isdesired must be configured as RBE signals. This is done when thesignals are created in the AIC, ABC, or ACCOL Workbench. Seethe manuals for these software tools for details. Also review'Choosing Signals for RBE', later in this section.

4. The controller must have expanded memory to hold the RBEData Base, or it must be a 386EX Protected Mode unit. A basicallocation of 64 bytes (32 bytes PROMable and 32 bytes RAM) isautomatically made when the RBE Module is declared. As RBEsignals are declared, more memory is allocated, as needed, in 16-byte increments. The memory usage for each RBE signal is:

PROM RAM TOTALAnalog RBE Signal 8 6 14Logical RBE Signal 4 2 6

5. An adequate number of I/O buffers must be defined. The numberneeded varies, depending upon total system requirements.

RBE

Report By Exception


❑ Choosing Signals for RBEIn general, all signals which require data collection should be configuredas RBE signals except for the cases outlined below:

● Signals which are critically important should be madeAlarm signals, rather than RBE signals. This is becausealarm signals are checked constantly and are reported immedi-ately upon detection of an alarm condition, whereas RBE signalsare only scanned periodically for changes. If an RBE signalchanges momentarily, between scans, the change will not bepicked up. Also, alarms are always reported before any otherdata is transferred, therefore RBE changes will not be sent untilafter any pending alarms. Such a delay may be unacceptable fortime-critical signals.

Generally, signals which are defined as alarm signals should notbe declared as RBE signals because there is a danger that thelatest value reported by the alarm report may be followed by anearlier value for the same signal in an Exception Report Message.This can happen as the higher priority alarm message with thelatest value may pass the Exception Report Message with anolder value while it is in transit.

● Enterprise Server Users who have a specific requirementfor collecting all data (whether or not it has changed) at aspecific rate may choose to use Template Data Collection, how-ever, this may not be as efficient as using RBE.

● #TIME system signals are NOT reported via RBE. If youneed to collect time information via RBE, use a CalculatorModule to set the value of a user-created analog signal equal to a#TIME signal, then designate the user-created analog signal forcollection via RBE.

RBE

Report By Exception


❑ Choosing RBE Deadbands● Analog RBE signals may be assigned an associated RBE dead-

band. The value of a deadband is an absolute value which definesa range of signal change within which no Exception Report willbe generated. For example, a deadband of '1.0' indicates that allsignal changes within a + 1.0 range of the last reported value arenot to be reported. The deadband value eliminates unnecessaryException Reports for a signal that fluctuates by performing adampening function. RBE won't generate a report if the signalfluctuations are insignificant, i.e., within the deadband.

● The RBE deadband is defined from the analog or analog alarmSignal Menu (if you're using AIC), from the settings portion ofthe Define New Signal / Edit Signal dialog boxes (if you're usingACCOL Workbench), or from the *SIGNALS section (if you'reusing the ACCOL Batch Compiler. If the deadband signal isunwired (not assigned) then the RBE signal is reported everytime it is written to, regardless of whether its current value is thesame or different from its last reported value.

● The deadband should be defined as an ACCOL signal, ratherthan a constant, to allow on-line changes to the deadband.

● Multiple analog RBE signals can refer to a common deadbandsignal.

Note Any on-line AIC edit which replaces the deadband signal name, withanother signal name, will be ignored by the RBE system.

RBE

Report By Exception


❑ Module Terminals

All module terminals are optional. If an input terminal is unwired, adefault value will be used.

There are three types of RBE Module terminals. The first is the MODEterminal. If the MODE value is 0 (or if unwired), RBE initializationparameters will only come from the RBE Manager, and values enteredon most of the RBE Module input terminals are ignored, and eventuallyoverwritten by values from the RBE Manager. If the MODE value is 1,

RBE

Report By Exception


first time initialization parameters come from RBE Module terminalentries. The value of the MODE terminal is not changeable on-line.

The second type of RBE Module terminals are the input terminals.These are the SCANRATE, SCANSLICE, FORMAT, STOPXMIT, andTIMEOUT. Values entered on these terminals may or may not be usedfor initialization parameters, depending on the value of MODE asexplained earlier. In either mode, if new values are received from theRBE Manager, they will overwrite the current values on these termi-nals.

The third type of RBE Module terminals are the output terminals. Themost important of these is the STATUS terminal which contains statusand error codes. The others are the TOTAL_1-4 terminals, theSEQ_NUM_1-2 terminals, ACTIVE_1-2 terminals, SCANTIME, andMESSAGE terminals. All of these terminals provide statistical informa-tion that is useful during communication trouble-shooting and debug-ging periods. If these terminals are unwired, the corresponding statusand statistical information will be unavailable.

Appendix C of the Network 3000 Communications ApplicationProgrammer's Reference (D4052) contains underlying details on RBEcommunication which may be helpful when examining these statistics.

Descriptions of all RBE Module terminals appear below:

RBE

Report By Exception


MODE Default: 0.0 ('wait for initialization')Format: Analog Signal or ConstantInput/Output: Input

is used to select the RBE mode of operation when the controller per-forms a cold-start following a download. The mode cannot be changedon-line.

Two modes are possible:

a. Wait for Initialization - Value 0.0: When this mode is selected,the RBE module waits for initialization from the RBE Manager(at the Enterprise Server or other network central). Any user-configured values assigned to the SCANRATE, SCANSLICE,FORMAT, and STOPXMIT terminals are ignored, and overwrit-ten by initialization values from the RBE Manager. The value onthe TIMEOUT terminal, however, is used until overwritten bythe RBE Manager.

b. Go Active - Value 1.0: When this mode is selected, the RBEModule uses values assigned to the SCANRATE, SCANSLICE,FORMAT, and STOPXMIT terminals (or defaults if the terminalsare unwired). The value on the TIMEOUT terminal is not useduntil a standby controller of a redundant system becomes active.

SCANRATE Default: 36000 (1 hour)Format: Analog SignalInput/Output: Input/Output

determines the rate at which RBE signals are examined to see if excep-tions have occurred. If exceptions are detected, then exception reportsare sent to the RBE Manager at the central.

RBE

Report By Exception


SCANRATE values are in tenths of seconds. Values may range from 1.0(0.1 second) to 65535.0 (6553.5 seconds).

The SCANRATE value must be small (fast) so that potential exceptionsaren’t missed.

However, if the SCANRATE value is small (too fast), it may causescanning to occur continuously and interfere with other ACCOL userand system tasks. If this occurs, consider increasing the SCANRATEvalue, and using slicing (See SCANSLICE terminal).

SCANSLICE Default: 1.0Format: Analog SignalInput/Output: Input/Output

is a number used to break down RBE scanning and reporting into anumber of equal time periods called ‘slices’. It should be used when RBEactivity is interfering with other tasks which have a priority of 120(priority of the RBE system) or less. See 'Task' section, later in thismanual for a list of task priorities.

Slicing allows a pause(s) within a scan so that affected equal or lowerpriority tasks can gain processing time. This is noticed when ACCOLtasks show slippage and/or performance of other system tasks, e.g. RDB,is degraded.

Slicing should be used only after the SCANRATE value has been set aslarge (slow) as possible and no improvement in performance has re-sulted.

Values for the SCANSLICE terminal may range from 1 to 255. A valueof 1 effectively turns off slicing since all RBE scanning and reporting isperformed within a single slice of time, equivalent to the SCANRATEvalue.

RBE

Report By Exception


Scan slicing is also turned off if the value entered on the SCANSLICEterminal is greater than the value on the SCANRATE terminal, or theSCANSLICE terminal is unwired or set to 0.

An example of scan slicing follows:

By examining the SEQ_NUM_1 terminal we determine that 12exception reports were generated during the last scanning period(which in this case is 8 seconds as specified by SCANRATE). Wecan use slicing to break up the 8 second scanning period into 4slices (the number of slices can range between 2-8 slices; we areusing 4 slices in this example. For a detailed description ofslicing, refer to Appendix C of the Network 3000 CommunicationsApplication Programmer's Reference (D4052). We can calculatethe length of time for each slice by simply dividing SCANRATEby SCANSLICE.

Slice Time = SCANRATE = 80.0 = 20.0 = 2 secondsSCANSLICE 4

(Note: remember that SCANRATE is expressed in tenths ofseconds, i.e. 80.0 = 8 seconds)

Num. messages in last scan = 12 = 3 messages per sliceSCANSLICE 4

If we determine, by observation, that our average of 3 messagescannot be handled within a 2 second period, then we need toincrease the SCANRATE value.

SCANSLICE serves also to limit the number of RBE messagesthat can be lost in the event of network failure. There should be adirect relationship between the reliability of the network and thislimit-- with more reliable networks having higher limits, and lessreliable networks having lower limits. See the Network 3000Communications Application Programmer's Reference (D4052) fordetails.

RBE

Report By Exception


SCANTIME Default: NoneFormat: Analog SignalInput/Output: Output

is used to display the processing time used (in milliseconds) during theprevious scanning period. Slicing has no effect on this measurement.

FORMAT Default: 1.0 (Short Format)Format: Analog SignalInput/Output: Input/Output

is used to specify the format for all Exception Reports. Values can beeither '1.0' (Short Format) or '2.0' (Long Format). See the Network 3000Communications Application Programmer's Reference (D4052) fordetails on exception report formats.

STOPXMIT Default: 1.0 (one report/one acknowledgment)

Format: Analog SignalInput/Output: Input/Output

is used to specify the number of Exception Reports to send beforewaiting for an acknowledgment from the RBE Manager. The value canrange from 1.0 to 127, or 0.0 (= never wait for a acknowledge responsefrom the RBE Manager).

The default is '1.0', meaning wait for an acknowledge response from theRBE Manager for every Exception Report sent before sending the nextone.

RBE

Report By Exception


TIMEOUT Default: 36000.0 (3600 seconds)Format: Analog SignalInput/Output: Input/Output

is a value that specifies the period in tenths of seconds at which torepeat the 'waiting for initialization' message to the RBE Manager if avalid initialization response is not received. The value can range from3000 (30.0 seconds) to 65535 (6553.5 sec.). Values less than 300 will usea value of 300. Values greater than 65535 will use the default. TheTIMEOUT terminal is not generally used in MODE 1, except as de-scribed earlier under 'MODE'.

TOTAL_1 Default: NoneFormat: Analog SignalInput/Output: Output

is set to the count of Analog RBE signals in the ACCOL load.


is set to the count of Logical RBE Signals in the ACCOL load.


is incremented every time an Exception Report is generated for ananalog RBE signal. This count is not reset automatically. If this signalmust be reset, it must be done so when the STATUS terminal is set to 5,i.e. when the RBE is idle.

RBE

Report By Exception



is incremented every time an Exception Report is generated for aLogical RBE signal. This count is not reset automatically. If this signalmust be reset, it must be done so when the STATUS terminal is set to 5,i.e. when the RBE is idle.

ACTIVE_1 Default: NoneFormat: Analog SignalInput/Output: Output

is set to the count of active Analog RBE signals. Initially, after a coldstart, all signals are active. Subsequently, the RBE Manager controlswhether or not an RBE signal is active. See the Network 3000 Commu-nications Application Programmer's Reference (D4052) for details onactive/inactive RBE signals.

ACTIVE_2 Default: NoneFormat: Analog SignalInput/Output: Output

is set to the count of active Logical RBE Signals. Initially, after a coldstart, all signals are active. Subsequently, the RBE Manager controlswhether or not an RBE signal is active. See the Network 3000 Commu-nications Application Programmer's Reference (D4052) for details onactive/inactive RBE signals.

RBE

Report By Exception


SEQ_NUM_1 Default: NoneFormat: Analog SignalInput/Output: Output

is set to the Report Sequence Number (RSN) of the last Report Messagesent to the RBE Manager. See the Network 3000 CommunicationsApplication Programmer's Reference (D4052) for details on reportsequence numbers.

SEQ_NUM_2 Default: NoneFormat: Analog SignalInput/Output: Output

is set to the Report Sequence Number (RSN) received in the last ac-knowledge response from the RBE Manager. See the Network 3000Communications Application Programmer's Reference (D4052) fordetails on report sequence numbers.

MESSAGE Default: NoneFormat: String SignalInput/Output: Output

is set to the ASCII equivalent text of the most recently received RBEManager message. If wired, the required length of this signal is 64characters. Messages received from the RBE Manager are convertedfrom hex to ASCII equivalent and output to this string signal. A maxi-mum of 32 hex bytes (64 ASCII characters) will be displayed.


is used to report the current state, status, and/or error codes. Possiblestatus and error codes are listed below:

RBE

Report By Exception


Code Meaning

1.0 Init State: RBE is in the 'Wait for Initialization' state(MODE = '0.0') following a cold start . It is waitingfor an initialization request from the RBE Manageror currently processing the received initializationrequest from the RBE Manager. May be waiting foran acknowledgment message to an Init ReportMessage.

2.0 Init State: Same as above except that this state isentered after a redundancy switchover occurs.

3.0 Reinitialization State: Error during processing of aninitialization message. Waiting for a new initializa-tion message. May also be waiting for an acknowl-edgment message to an Init Report Message.

4.0 Inactive State: All RBE signals are in an inactivestate. The RBE Manager must send a valid activa-tion request message to activate one or more signals.Reloading the controller will also make all RBEsignals active.

5.0 Active Idle State: RBE is Active and waiting for theSCANRATE timeout to occur. In an error-freerunning unit, the STATUS should alternate between'5.0' and '6.0' once for each SCANRATE period.

6.0 Actively Scanning State: RBE is active and in itsscanning/reporting mode. This status is set for thefull scanning cycle including delays betweenSCANSLICE periods, or when waiting for the ac-knowledgment message after the STOPXMIT limit isreached.

7.0 Processing Activate / Deactivate request. May be

RBE

Report By Exception


waiting for an acknowledgment in response to anactive report message. The RBE Manager may send astatus query request message to verify this.

8.0 Processing Demand Request: A request for reportingof selected RBE signals is being processed, or iswaiting for an acknowledgment in response to aDemand Report Message. The RBE Manager maysend a status query request message to verify this.

The following error codes are displayed at the RBE Module statusterminal and may be useful for debugging purposes or for developmentof RBE Data Manager software. Some of these errors may be visibleonly for a brief period as the STATUS terminal is also used to reflect thecurrent status of the RBE system.

Code Meaning

-1.0 RBE is not defined. This usually indicates that thereare no RBE signals defined in the load. Problem withthe ACCOL load or firmware.

-2.0 Can't allocate dedicated communication buffers.Problem with the ACCOL load or firmware.

-3.0 Can't queue I/O requests to the system. Problem withthe ACCOL load or firmware.

-9.0 Bad Message. A local RBE message was received.Only global messages are supported. Request isrejected.

-10.0 Bad Function Code. The Function Code in thereceived RBE message is not valid. Request isrejected, and an error response is generated.

-11.0 Bad Sub Function Code. The Sub Function code in

Code Meaning (continued)

RBE

Report By Exception


the received RBE message is not valid. Request isrejected, and an error response is generated.

-12.0 Bad Scan Rate. The SCANRATE Value in the initial-ization message is 0. Valid SCANRATE values arebetween 1.0 and 65535.0, representing tenths ofseconds. Request is rejected, an error response isgenerated, a 'waiting for initialization' message issent, and a new initialization request is expected.

-13.0 Bad STOPXMIT limit. The STOPXMIT limit value inthe initialization message is > 127. Valid limits rangefrom 0.0-127.0. Request is rejected, an error responseis generated, a 'waiting for initialization' message issent, and a new initialization request is expected.

-14.0 Bad Report Format Type. The Report Format Typein the initialization request is not 1.0 or 2.0. Validtypes are 1.0 (Short Format) or 2.0 (Long Format).Request is rejected, an error response is generated, a'waiting for initialization' message is sent, and a newinitialization request is expected.

-15.0 Bad parameter. The 'Number of Entries' field in anActivate/Deactivate message is incorrect. Validvalues are 1 - 65. Request is rejected, an errorresponse is generated.

-16.0 Bad parameter. The Operation Code in an Activate/Deactivate message is incorrect. Valid values are 1.0(Activate) or 2.0 (Deactivate). Request is rejected, anerror response is generated.

-17.0 Bad entry in the Activate/Deactivate message. Eitherthe Operation Code or the signal address of an entryin this request is invalid. The erroneous entry isreturned in the RBE response message, other entries

RBE

Report By Exception


are processed.

-18.0 Bad Report Sequence Number (RSN) in a request toreport all RBE signals. Valid values range from 0 to127. Request is rejected, an error response is gener-ated.

-19.0 Bad RSN in acknowledge response. The receivedRSN in the acknowledge response is not equal to thecurrent RSN or it is not between the last RSNacknowledged and the current RSN. Acknowledg-ment response is rejected, an error response isgenerated.

-20.0 After a redundant switchover the RBE System hasdetected a mismatch between the Value of theACTIVE_n terminal and the actual number of activeRBE signals. This is just a warning.

-21.0 Bad Port. An RBE message was received through aPseudo Slave port. RBE does not support communi-cation over this type of port.

-1XX.0 Internal communication error code. Contact Bristol.

Code Meaning (continued)

Page Redundancy-1


RedundancyRedundancy Module

The Redundancy Module activates and monitors 33XX redundancy.The module collects and stores statistics for the redundancy interface,identifies which unit is in control, and notifies when a switchoveroccurs. It also monitors the backup unit’s status, and forces aswitchover on command.

The Redundancy Module is required in a redundant load. A redundantload is one in which at least one ACCOL task has a non-zero redun-dancy frequency. If no Redundancy Module is present, the load willexecute, but redundant transfers and other redundant operations willnot occur.

The Redundancy Module may be placed in any ACCOL task, but it ismost efficient to keep it in Task 0.

❏ Module TerminalsThe ACCOL Interactive Compiler (AIC) and ACCOL Batch Compiler(ABC) automatically assign pre-defined system signals (#RDN..) to theRedundancy Module terminals. These default #RDN names are listedin this section. These Module terminals must use the #RDN signals;the signals MUST NOT BE RENAMED.

LIST

ARRAY

FAIL_OPTION

RESET

STATUS_1

STATUS_2

Redundancy


Page Redundancy-2


STATUS_1 Default: #RDN.ONLINE.UNITFormat: Logical change-of-state alarm sig-

nalInput/Output: Output

indicates which of the redundant units is in control. The text for theON state is ‘A’ and the text for the OFF state is ‘B’. The signal is setand an alarm is automatically generated on system startup following adownload, and when a redundant switchover occurs.

For RDC 3350, UCS 3380, CFE 3385:

Proper functioning of this mechanism requires that Switch 7 ofBank 4 on the APMC board be set to opposite states on the twounits. The switch should be to the left for the ‘A’ unit, and to theright for the ‘B’ unit.

For DPC 3330:

Proper functioning of this mechanism requires that Switch 7 ofBank 1 on the 3330 CPU engine be set to opposite states on the twounits. The switch should be to the left for the ‘A’ unit, and to theright for the ‘B’ unit.

STATUS_2 Default: #RDN.BACKUP.STATFormat: Analog alarm signalInput/Output: Output

represents the status of redundancy including, where applicable, thecurrent state of the backup unit. The signal is set to one of the follow-ing values:

0 = load is not redundant (no task has a non-zero redundancyfrequency)

1 = Backup unit is loaded and ready2 = Backup unit is being sideloaded3 = Backup unit has failed or is not communicating

Page Redundancy-3



4 = Backup memory configuration is not valid for the load. APMCredundancy uses this code for all configuration mismatcheswhich could be any of the following:

✲Insufficient RAM in backup unit.✲ Firmware PROM checksums do not agree; (revision levels

must be equal.)✲ CUSTOM PROM checksums do not agree or one unit has a

CUSTOM PROM, and the other unit does not.✲ ACCOL load in PROM load versions must match.

5 = No redundancy hardware present on the on-line unit

The following values appear when using 3330 units only:

6 = Firmware PROM checksums do not agree; (revision levels mustbe equal.)

7 = CUSTOM PROM checksums do not agree or one unit has aCUSTOM PROM, and the other unit does not.

8 = Communication board usage is not consistent between units. Thesame number of communication boards must be in each unit,and they must be identical in slot location. Example: If unit 1has a Standard Communication Board in Slot 1 (Ports A/B) andan Enhanced Communication Board in Slot 2 (Ports C/D), thenunit 2 must be the same. Clock speed selection for each portmust be the same in each unit. Example: If the port B clock inthe on-line unit is set for 16 MHz (1MEG synchronous) then theport B clock in the backup unit must also be set for 16 MHz(1MEG synchronous).

9 = The redundancy hardware is not in the same slot in both units.In the event that both slots in each unit contain EnhancedCommunication Boards with redundancy hardware, only slot 1will be used for redundant transfers.


Page Redundancy-4


10 = If either unit has the load in PROM, the other unit (whether it’sin PROM or not) must use the same ACCOL load version.

11 = The load is configured for local process I/O. No redundantoperations are performed.

12 = The load contains non-supported ACCOL modules. No redun-dant operations are performed. (PROM upgrade necessary tosupport new modules)

13 = One unit is configured as an EASlave (Group 1 and above) andthe other is not. (See Switch bank 1, switch 8 on the unit)

The High Limit for the alarm is specified with the analog signal#RDN.BKSTAT.HILM which defaults to a value of 2.

LIST Default: #RDN.LIST.NUMFormat: Analog signalInput/Output: Output

specifies the signal list that is used to store the redundancy statisticaldata. This signal defaults to 0 and must be set by the ACCOL pro-grammer to a valid signal list number. There should be a sufficientnumber of analog signals in the list for the data values. (See ‘Redun-dancy Statistics'.)

ARRAY Default: #RDN.ARRAY.NUMFormat: Analog signalInput/Output: Output

specifies the read/write analog data array that is used to store theredundancy statistical data. This terminal is only used if the listterminal is invalid. This signal defaults to 0 and must be set by theuser to the data array number. There should be a sufficient number ofrows in the data array for the data values which will always be storedin Column 1. (See ‘Redundancy Statistics'.)

Page Redundancy-5



RESET Default: #RDN.RESET.DATAFormat: Logical signalInput/Output: Input

clears the redundancy statistical data. If this signal state is ON whenthe data is updated, the data will be zeroed and the signal will be setto OFF.

FAIL_OPTION Default: #RDN.SWITCH.OVERFormat: Logical signalInput/Output: Output

forces the backup unit to become the controlling unit. If this signalstate is ON and the backup unit is loaded and ready(#RDN.BACKUP.STAT = 1), the current Online unit will Watchdog,causing an automatic switchover to the other unit where the signalwill be set to OFF. If this signal state is ON and the backup unit is notloaded and ready (#RDN.BACKUP.STAT is not equal to 1),#RDN.SWITCH.OVER will remain ON, and the switchover will occurautomatically, as soon as the backup unit is loaded and ready.

❏ Redundancy StatisticsStatistical data pertaining to the interface between the controllingunit and the backup unit is collected. This data can be stored in eithera Signal List or a R/W Analog Data Array. The following is a list of thecollected data ordered as it appears in the list or array.


Page Redundancy-6


Signal number Statistics Collectedor row number

1 The number of data transfers successfullycompleted (ACKs)

2 The number of timeout errors3 The number of checksum/parity errors (NAKs)1.

4 The number of sideload starts5 The number of buffer errors6 The number of control/backup switchovers7 The Julian timestamp when the last switchover

occurred2.

8 The total time in seconds for the sideload9 The wait time during sideload for synchronization

with the ACCOL tasks10 The time in seconds for the dynamic portion of

the sideload

Statistic 1 includes sideload data as well as normal runtime updates.The size of the data transfers varies. The maximum sideload block is2000 bytes (32,000 in a 3330 unit), while the maximum runtimeupdate buffer is 255 bytes.

Statistics 2 and 3 represent errors which are automatically retried.Each data transfer is retried 2 times if it results in a timeout or if thebackup unit reports a NAK, for a total of 3 attempts to transfer anindividual block of data. After 3 attempts, the backup unit is declaredfailed (#RDN.BACKUP.STAT=3 generates a High Alarm), and a newsideload is started in an attempt to recover the backup unit.

Statistic 4 indicates the number of times sideload was started sincethe current online unit took control. If this number is greater than 1,it may indicate a hardware problem. Examination of the error statis-tics can help to identify the problem area.

1. Parity errors are detected in DPC 3330 units only.

2. See the section on the Encode module for details on decoding the Julian timestamp.

Page Redundancy-7



Statistic 6 indicates the total number of switchovers which haveoccurred since the statistics were last reset using#RDN.RESET.DATA. Statistic 7 is a Julian timestamp in the sameform as #TIME.000 which indicates when the switchover occurred.NOTE: The ENCODE Module Function 3 can be used to translatethis Julian timestamp into separate analog signals or array elementsfor Year/Month/Day/Hour/Min/Sec.

Statistics 8 through 10 indicate the elapsed time in seconds (# 4 msec)required for the most recent sideload to the current backup unit. Thisdata is only stored if the Signal List or Array have at least 10 entries.The total time, minus the wait time and dynamic time, indicates thetime to transfer the fixed or prommable part of the ACCOL load. Thedynamic portion of the load is transferred only after all ACCOL tasksare synchronized at a module boundary. The wait time indicates howlong this portion of the sideload was delayed.

BLANK PAGE

Page Redundancy-1



The Redundancy Module activates and monitors 33XX redundancy.The module collects and stores statistics for the redundancy interface,identifies which unit is in control, and notifies when a switchoveroccurs. It also monitors the backup unit’s status, and forces aswitchover on command.

The Redundancy Module is required in a redundant load. A redundantload is one in which at least one ACCOL task has a non-zero redun-dancy frequency. If no Redundancy Module is present, the load willexecute, but redundant transfers and other redundant operations willnot occur.

The Redundancy Module may be placed in any ACCOL task, but it ismost efficient to keep it in Task 0.

❏ Module TerminalsThe ACCOL Interactive Compiler (AIC) and ACCOL Batch Compiler(ABC) automatically assign pre-defined system signals (#RDN..) to theRedundancy Module terminals. These default #RDN names are listedin this section. These Module terminals must use the #RDN signals;the signals MUST NOT BE RENAMED.

LIST

ARRAY

FAIL_OPTION

RESET

STATUS_1

STATUS_2

Redundancy


Page Redundancy-2


STATUS_1 Default: #RDN.ONLINE.UNITFormat: Logical change-of-state alarm sig-

nalInput/Output: Output

indicates which of the redundant units is in control. The text for theON state is ‘A’ and the text for the OFF state is ‘B’. The signal is setand an alarm is automatically generated on system startup following adownload, and when a redundant switchover occurs.

For RDC 3350, UCS 3380, CFE 3385:

Proper functioning of this mechanism requires that Switch 7 ofBank 4 on the APMC board be set to opposite states on the twounits. The switch should be to the left for the ‘A’ unit, and to theright for the ‘B’ unit.

For DPC 3330:

Proper functioning of this mechanism requires that Switch 7 ofBank 1 on the 3330 CPU engine be set to opposite states on the twounits. The switch should be to the left for the ‘A’ unit, and to theright for the ‘B’ unit.

STATUS_2 Default: #RDN.BACKUP.STATFormat: Analog alarm signalInput/Output: Output

represents the status of redundancy including, where applicable, thecurrent state of the backup unit. The signal is set to one of the follow-ing values:

0 = load is not redundant (no task has a non-zero redundancyfrequency)

1 = Backup unit is loaded and ready2 = Backup unit is being sideloaded3 = Backup unit has failed or is not communicating

Page Redundancy-3



4 = Backup memory configuration is not valid for the load. APMCredundancy uses this code for all configuration mismatcheswhich could be any of the following:

✲Insufficient RAM in backup unit.✲ Firmware PROM checksums do not agree; (revision levels

must be equal.)✲ CUSTOM PROM checksums do not agree or one unit has a

CUSTOM PROM, and the other unit does not.✲ ACCOL load in PROM load versions must match.

5 = No redundancy hardware present on the on-line unit

The following values appear when using 3330 units only:

6 = Firmware PROM checksums do not agree; (revision levels mustbe equal.)

7 = CUSTOM PROM checksums do not agree or one unit has aCUSTOM PROM, and the other unit does not.

8 = Communication board usage is not consistent between units. Thesame number of communication boards must be in each unit,and they must be identical in slot location. Example: If unit 1has a Standard Communication Board in Slot 1 (Ports A/B) andan Enhanced Communication Board in Slot 2 (Ports C/D), thenunit 2 must be the same. Clock speed selection for each portmust be the same in each unit. Example: If the port B clock inthe on-line unit is set for 16 MHz (1MEG synchronous) then theport B clock in the backup unit must also be set for 16 MHz(1MEG synchronous).

9 = The redundancy hardware is not in the same slot in both units.In the event that both slots in each unit contain EnhancedCommunication Boards with redundancy hardware, only slot 1will be used for redundant transfers.


Page Redundancy-4


10 = If either unit has the load in PROM, the other unit (whether it’sin PROM or not) must use the same ACCOL load version.

11 = The load is configured for local process I/O. No redundantoperations are performed.

12 = The load contains non-supported ACCOL modules. No redun-dant operations are performed. (PROM upgrade necessary tosupport new modules)

13 = One unit is configured as an EASlave (Group 1 and above) andthe other is not. (See Switch bank 1, switch 8 on the unit)

The High Limit for the alarm is specified with the analog signal#RDN.BKSTAT.HILM which defaults to a value of 2.

LIST Default: #RDN.LIST.NUMFormat: Analog signalInput/Output: Output

specifies the signal list that is used to store the redundancy statisticaldata. This signal defaults to 0 and must be set by the ACCOL pro-grammer to a valid signal list number. There should be a sufficientnumber of analog signals in the list for the data values. (See ‘Redun-dancy Statistics'.)

ARRAY Default: #RDN.ARRAY.NUMFormat: Analog signalInput/Output: Output

specifies the read/write analog data array that is used to store theredundancy statistical data. This terminal is only used if the listterminal is invalid. This signal defaults to 0 and must be set by theuser to the data array number. There should be a sufficient number ofrows in the data array for the data values which will always be storedin Column 1. (See ‘Redundancy Statistics'.)

Page Redundancy-5



RESET Default: #RDN.RESET.DATAFormat: Logical signalInput/Output: Input

clears the redundancy statistical data. If this signal state is ON whenthe data is updated, the data will be zeroed and the signal will be setto OFF.

FAIL_OPTION Default: #RDN.SWITCH.OVERFormat: Logical signalInput/Output: Output

forces the backup unit to become the controlling unit. If this signalstate is ON and the backup unit is loaded and ready(#RDN.BACKUP.STAT = 1), the current Online unit will Watchdog,causing an automatic switchover to the other unit where the signalwill be set to OFF. If this signal state is ON and the backup unit is notloaded and ready (#RDN.BACKUP.STAT is not equal to 1),#RDN.SWITCH.OVER will remain ON, and the switchover will occurautomatically, as soon as the backup unit is loaded and ready.

❏ Redundancy StatisticsStatistical data pertaining to the interface between the controllingunit and the backup unit is collected. This data can be stored in eithera Signal List or a R/W Analog Data Array. The following is a list of thecollected data ordered as it appears in the list or array.


Page Redundancy-6


Signal number Statistics Collectedor row number

1 The number of data transfers successfullycompleted (ACKs)

2 The number of timeout errors3 The number of checksum/parity errors (NAKs)1.

4 The number of sideload starts5 The number of buffer errors6 The number of control/backup switchovers7 The Julian timestamp when the last switchover

occurred2.

8 The total time in seconds for the sideload9 The wait time during sideload for synchronization

with the ACCOL tasks10 The time in seconds for the dynamic portion of

the sideload

Statistic 1 includes sideload data as well as normal runtime updates.The size of the data transfers varies. The maximum sideload block is2000 bytes (32,000 in a 3330 unit), while the maximum runtimeupdate buffer is 255 bytes.

Statistics 2 and 3 represent errors which are automatically retried.Each data transfer is retried 2 times if it results in a timeout or if thebackup unit reports a NAK, for a total of 3 attempts to transfer anindividual block of data. After 3 attempts, the backup unit is declaredfailed (#RDN.BACKUP.STAT=3 generates a High Alarm), and a newsideload is started in an attempt to recover the backup unit.

Statistic 4 indicates the number of times sideload was started sincethe current online unit took control. If this number is greater than 1,it may indicate a hardware problem. Examination of the error statis-tics can help to identify the problem area.

1. Parity errors are detected in DPC 3330 units only.

2. See the section on the Encode module for details on decoding the Julian timestamp.

Page Redundancy-7



Statistic 6 indicates the total number of switchovers which haveoccurred since the statistics were last reset using#RDN.RESET.DATA. Statistic 7 is a Julian timestamp in the sameform as #TIME.000 which indicates when the switchover occurred.NOTE: The ENCODE Module Function 3 can be used to translatethis Julian timestamp into separate analog signals or array elementsfor Year/Month/Day/Hour/Min/Sec.

Statistics 8 through 10 indicate the elapsed time in seconds (# 4 msec)required for the most recent sideload to the current backup unit. Thisdata is only stored if the Signal List or Array have at least 10 entries.The total time, minus the wait time and dynamic time, indicates thetime to transfer the fixed or prommable part of the ACCOL load. Thedynamic portion of the load is transferred only after all ACCOL tasksare synchronized at a module boundary. The wait time indicates howlong this portion of the sideload was delayed.

BLANK PAGE


Page Redundcon-1

Redundancy-Concepts

DPC 3330B

Side loadDPC 3330

A

on-line

DPC 3330B

DPC 3330A

Download

The unit which is designatedto be on-line receives anACCOL load.

After downloading, on-lineunit A performs a side load tounit B.

Unit B becomes the backup.

Introduction to Redundancy

The DPC 3330, RDC 3350, UCS 3380, and CFE 3385controllers support the redundant processor architec-ture. In a redundant configuration, there are twoidentical controllers with the same ACCOL load. Atany one time, however, only one of the controllers ison-line, controlling the system. The other controlleroperates in a hot backup status, ready to take over ifthe on-line unit fails.

Initially, the on-line and backup units are designatedby a switch on a control panel. This control panel istypically referred to as the Redundancy SwitchoverPanel or simply the Redundancy Control Panel. Whenboth units are started up cold, the unit designated on-line waits for an ACCOL load to be downloaded into it.

Once the on-line unit receives the download and startsrunning its ACCOL load, it side loads all its data intothe other unit. The other unit then becomes thebackup unit. In this way, the ACCOL loads in both theon-line and the backup controllers are identical. Theon-line unit, however, is the only unit actually control-ling the process.

Redundancy Concepts


Page Redundcon-2

Redundancy-Concepts

The on-line unit, in addition to performing its controlfunctions, is responsible for maintaining consistencybetween its data base, and the data base in the backupunit. As changes occur in the on-line unit, it updatesthe backup unit with status information for each taskin the ACCOL load, data changes, and other system-level information. This ensures that both units con-tinue to have identical ACCOL loads. This updatingprocess is discussed in more detail later in this section.

If the on-line unit detects a failure in the backup unit,the on-line unit will check it periodically, to see if ithas returned to service.

When the backup unit becomes available again, the on-line unit sideloads the backup unit with the currentcontents of the data base. During the sideload opera-tion, the on-line unit will continue to execute itsACCOL load. The sideload typically takes less thanone second to perform; there is no significant impacton normal operations. Once the sideload is completed,the backup unit is again standing by, ready to takeover if necessary.

DPC 3330A

on-line

DPC 3330B

connection broken

failed

The on-line unit continuallyupdates the backup unit toensure consistency between thetwo units.

DPC 3330B

DPC 3330A

backupon-line

Continuousdataupdates

When the backup unit fails, orcommunications is broken, theon-line unit monitors the line.


Page Redundcon-3

Redundancy-Concepts

A sideload is also performed when the on-line unitreceives a warm download (a download while it isalready running). In this case, when the on-line unitdetects the download it tells the backup unit to reset.Once the download is complete, the on-line unitsideloads the backup unit.

When the on-line unit determines that the backup unitis again operating properly, it updates the backup unitcontinuously. The backup unit stands by, waiting totake over from the on-line unit.

If the on-line unit fails, the backup unit becomes theon-line unit. Once the switchover to the backup occurs,it automatically assumes the role of the on-line unit.Switchover to the backup is almost instantaneous. Inmost cases, this allows for uninterrupted control of theprocess.

When the failed unit is returned to service, it receivesa sideload, and now serves as the backup unit.

on-line

DPC 3330A

DPC 3330B

failure corrected

side load

DPC 3330B

on-linefailed

popsizzle

DPC 3330B

on-line

DPC 3330A

backup

side load Once the failure in Unit A iscorrected, Unit B side loadsUnit A. Unit A then becomesthe backup unit.

When Unit B is repaired, itwill receive a side load fromUnit A.

Switchover occurs. Unit Bbecomes the on-line unit.DPC 3330

A


Page Redundcon-4

Redundancy-Concepts

There are certain unavoidable instances, where a momentary discrep-ancy can occur between the two units during switchover. For example,if the on-line unit successfully performs some operation (say output-ting an event buffer) and then fails while it is in the midst of tellingthe backup unit what it did, the backup unit will take over withoutknowing that the event buffer was output, and will output it again.

Redundancy Configuration Guidelines

Redundancy Module

In a redundant configuration, each ACCOL load contains a Redun-dancy Module and at least one ACCOL task which is assigned aRedundancy Frequency greater than 0. Typically, the RedundancyModule is placed in Task 0. The Redundancy Module is used forcontrolling redundancy, for updating the system signals on the moduleterminals, and also for monitoring the performance of the redundantsystem. (See ‘Redundancy Module’ for details.)

Automatic Updates and User-Controlled Updates

In a redundant system, changes in the on-line unit’s ACCOL load aresent to the backup unit. Some changes are sent automatically whenthey occur. Others - specifically those generated by ACCOL tasks - aresent at a rate based on the redundancy frequency chosen by theACCOL programmer.

Automatic Updates

The table below lists all changes that are sent automatically from theon- line unit to the backup unit. These changes are sent as they occur(provided that the load is declared redundant and the backup unit isfunctioning).


Page Redundcon-5

Redundancy-Concepts

Changes Automatically Sent to BACKUP unit

� Node Routing Table/ Time Synchronization Information

� AUDIT module event buffer data and controls

� RIO Task Information and RIOSTATS module signals

� Input data from RPDM I/O points

� Initialization data for RHSCOUNT, RLSCOUNT modules

� Alarm System actions (for example, acknowledgement)

� Signal or other changes to the running load made from outsidethe controller. These changes can come from:

- Operator/Engineer modifying signal data through Enter-prise Windows dialog boxes

- On-line menus in AIC, Toolkit, Taskspy, or other programswhich access the Remote Data Base (RDB).

- 3330 Keypad/display device- Data received through the SLAVE module- Data received through CUSTOM module MODBUS slave, El

Paso Gas Slave, etc. except for Teledyne Geotech slave.

User Controlled Updates

Changes generated by execution of ACCOL tasks are sent to thebackup unit under control of the redundancy frequency assigned to theindividual ACCOL tasks by the ACCOL programmer. These are listedbelow.


Page Redundcon-6

Redundancy-Concepts

Changes Sent According to Redundancy Frequency

� Any updates to ACCOL signals, data array elements, or otherstructures, that are caused by the execution of an ACCOLmodule.

� 3350/80/85 process I/O data

� Remote I/O module (RANIN, RDIGOUT etc.) terminal data

� Alarm inhibit/enable status and alarm limits when generatedwithin an ACCOL module.

� Communications transactions initiated by execution of anACCOL module such as the LOGGER Module, MASTER Module,or CUSTOM Modules where the unit functions as a master (e.g.MODBUS Master or Allen-Bradley mode)

� Communications transactions associated with the CUSTOMModule Teledyne-Geotech protocol

Setting Redundancy Frequency

Redundancy Frequency is an application-dependent parameter as-signed when tasks are created using the ACCOL II Interactive Com-piler, ACCOL II Batch Compiler, or ACCOL Workbench.

A careful analysis of your ACCOL tasks must be made when deter-mining the redundancy frequency. Unless such an analysis for yourapplication indicates otherwise, it is recommended that all ACCOLTasks be assigned a redundancy frequency of 1. This ensures that allchanges in the on-line unit are also made in the backup unit and thattask execution following a switchover continues from the last com-pleted module. The following cases, in particular, should use a redun-dancy frequency of 1:


Page Redundcon-7

Redundancy-Concepts

Use Redundancy Frequency of 1 when:

� Unit is a 3350/80/85 and the task contains Process I/O modulesor affects signal values which control process I/O points

� Unit is a 3330 and the task contains Remote I/O modules oraffects signal values which control process I/O points

� Task contains modules which will initiate communications wheredata changes will be received (LOGGER using Input Mode,MASTER using Poll Mode, CUSTOM Teledyne-Geotech mode,etc.)

� Task contains modules which do time-based calculations, e.g.INTEGRATOR, AVERAGER, etc.

� Task updates signals or data arrays which are used by otherACCOL tasks

� Task updates alarm signals

� Task updates signal controls such as Manual Inhibit/Enable

There may be special cases where you can use a Redundancy Fre-quency other than 1 without losing data integrity for your application.You will have to determine this when designing your ACCOL load fora redundant system. All of the above factors should be considered.

The paragraphs below summarize the effects of different redundancyfrequencies:

Redundancy Frequency of 0 - Data changes generated by the modulesof this task are never sent to the backup unit. If a switchoveroccurs, the new on-line unit begins execution of this task at the firstmodule. Signal and other data values generated by this task maynot be current. Process I/O could be affected adversely.


Page Redundcon-8

Redundancy-Concepts

Redundancy Frequency of 1 - All data changes generated by themodules of this task are sent to the backup unit. In addition, thebackup unit is informed of the position within the task as modulesare executed. If a switchover occurs while this task is active, thenew on-line unit continues execution of this task from the mostrecently completed module boundary. Signal and other data valuesgenerated by this task are current.

Redundancy Frequency n (n > 1) - Data changes done by the modulesof this task are only sent to the backup unit every ‘nth’ time thetask executes. For example, if Redundancy Frequency is 5, the taskwould execute four times without updating the backup unit, thenone time (5th execution) with all changes which occur during thatexecution sent to the backup unit; the changes which occurredduring the intervening four executions are never sent. Because aswitchover can occur at any time, the effect would vary dependingon when the last updates were made.

For example, if a master module initiates communications during aparticular task execution, the response data will be copied to thebackup unit only if that particular task execution was the ‘nth’ one(as described above).

CAUTION

Users with a redundant system should onlyuse a redundancy frequency greater than 1 ifthey fully understand the possible conse-quences, described above.

ACCOL Controlled Switchovers

The ACCOL program can force a switchover from the on-line to thebackup unit using the #RDN.SWITCH.OVER signal. (See ‘Redun-dancy Module’). This would normally be done based on detection bythe ACCOL program of some error condition in the on-line unit whichmight be eliminated by switching to the other unit until the problem is


Page Redundcon-9

Redundancy-Concepts

corrected. A good example would be the detection of a Process I/Oboard on-line diagnostic failure in a 3350/80/85 redundant unit.Because the backup unit has a duplicate set of Process I/O boards, it isvery likely that switching to that unit would eliminate any immediateproblem and the faulty board could be replaced in the now backupunit.

When constructing the switching logic of the ACCOL program, caremust be taken to avoid generating a situation where the units continu-ally switch back and forth because of either a real or perceived prob-lem in both units. To avoid this situation, it is recommended that theunit ID contained in the #RDN.ONLINE.UNIT signal be used. Inorder for this logic to work, the A/B switch position on the CPU boardmust be in opposite positions for the two units (see #RDN.ONLINE.UNIT under ‘Redundancy Module’ for details). In the followingexample we have decided that Unit A is our first choice as the on-lineunit, but that for some ACCOL detected condition we will force aswitchover to Unit B. We will never force a switchover from Unit Bback to Unit A for this same error condition unless the operatormanually changes a signal to indicate that Unit B is the first choice asthe on-line unit.

1. Let’s say we have a particular error condition, call it Error #1, thatwe have decided should cause a forced switchover to the normallybackup unit. When the conditions determining this error aredetected, a logical signal ERROR.001 is turned ON.

2. We have a second logical signal, PRIMARY.UNIT, which has aninitial value of ON and is both Control Inhibited and ManualInhibited. When this signal is ON it indicates that Unit A is ourfirst choice as the on-line unit; when it is OFF it indicates Unit B isour first choice. This signal will serve as an ‘Enable’ for a forcedswitchover.


Page Redundcon-10

Redundancy-Concepts

3. When the error condition occurs, before forcing a switchover wetest to see if it is OK to switch by requiring that thePRIMARY.UNIT and #RDN.on-line.UNIT signals match. If theydo, it indicates we have an error condition in our Primary unit andwant to switch to the backup. If they do not match, it indicates weare already running in the normally backup unit and do not wantto switch.

The following sample ACCOL code illustrates the logic:

.

. (error detection logic which either sets

. or clears the ERROR.001 logical signal)

.

.50 IF (ERROR.001)60 CALCULATOR

10 :IF (PRIMARY.UNIT & #RDN.ONLINE.UNIT)20 #RDN.SWITCH.OVER=#ON30 :ENDIF40 :IF (~PRIMARY.UNIT & ~#RDN.ONLINE.UNIT)50 #RDN.SWITCH.OVER=#ON60 :ENDIF

70 WAIT DELAY 2 S80 ENDIF90 CALCULATOR #RDN.SWITCH.OVER=#OFF

The Calculator Module and WAIT DELAY in the previous programsegment are only executed if the error condition is true. Theswitchover control signal is only turned on if we are executing in theunit indicated by the PRIMARY.UNIT logical signal. The WAITDELAY allows time for the Redundancy Task to detect that#RDN.SWITCH.OVER is ON and to take the required action (1 secondscan rate). Finally, we turn off the switchover control signal to cover


Page Redundcon-11

Redundancy-Concepts

the case where the Redundancy Task found that the backup unit wasnot available and therefore did not force a switchover.

If the switchover occurs before the Calculator Module completes (e.g.between Line 30 and Line 60), the Calculator Module will be reex-ecuted in the new on-line unit, but the PRIMARY.UNIT and#RDN.ONLINE.UNIT signals will not match, therefore the switchovercontrol signal will not be turned on. On the next execution of the Task,the error detection logic will clear the ERROR.001 signal if the errorcondition has been eliminated. Even if an error condition is detected,no further program forced switchovers will occur without operatorintervention to change the PRIMARY.UNIT selection.

Note that this discussion relates to ACCOL program forced switchoveronly; manual switchover by an operator, or automatic failover to arunning backup if the on-line unit watchdogs are not affected.

BLANK PAGE


Page Resume-1

ResumeResume Command

The Resume Command reactivates a task which has been stopped by aSuspend Command.

SyntaxRESUME task

task identifies the target task. It must be separated from the com-mand by a space.

Example

RESUME 80

Resume

BLANK PAGE


Page RIOSTATS-1

RIOSTATSRIO Status Module

The RIOSTATS Module monitors communication and diagnosticfailures between a single RIOR port on a 3310/30/35 controller and theRemote I/O Racks (RIO 3331s) which communicate with that port.

The RIOR port being monitored is specified on the PORT terminal.Only one module per port should be defined in the ACCOL load. Ifmore than one module is defined in the load for a given port, only theSTATUS terminal signals in the first module will be updated. Each ofup to ten STATUS terminals (1 for each Remote I/O Rack) present astatus value that is the sum of error codes from its associated RemoteI/O Rack. This module is non-executing and may be placed in anyACCOL Task, however it is most efficient to keep it in ACCOL Task 0.


PORT

is the RIOR port on the DPC 3330, DPC 3335, or RTU 3310 which thismodule will monitor for status values from the Remote I/O Racks.Enter one of the following numbers to identify the RIOR port:

Default: None, entry requiredFormat: ConstantInput/Output: Input

STATUS(1-10)

RIOSTATSPORT

RIOSTATS


Page RIOSTATS-2


1 = Port A2 = Port B3 = Port C4 = Port D

STATUS_n

is set based on RIO communication and module execution statusaccording to the codes listed below.

Error Code Conditions at the Remote I/O Rack:

-1 Communications have failed0 Communications are O.K. and no other failures1 One or more boards failed diagnostics.2 One or more boards is of the wrong type.4 At least one board is missing.8 Real-time clock calibration failure. (RLSCOUNT and

RHSCOUNT accuracy may be degraded.)16 Backup battery warning (battery low or failed)32 AI not ready (AF.xx PROM set only); AI and/or LLAI

not ready (AG or later PROM set)64 Real-time clock battery failure. Restoration of out-

puts after power failure will not occur. (RIO firm-ware B.04 or later)

128 RIO Rack firmware incompatible with process I/Oconfigured in load. (C.01 or newer firmware shouldbe installed in the RIO 3331.)

256 RPDO interfering with clock at RIO rack. In general,no more than a maximum of 2 PDO pairs (4 DOpoints) should be used in any single RPDO module. Ifnecessary, re-configure RPDO points across moremodules or tasks. Reset the RIO 3331, or cycle poweron and off to clear the error. (Reporting of this erroronly available with RIO 4.1 and newer firmware.)



Page RIOSTATS-3


Ten STATUS terminals are provided. The signal on the STATUS_1terminal will hold the status value for the Remote I/O Rack withaddress 1. The signal on the STATUS_2 terminal will hold the statusvalue for the Remote I/O Rack with address 2, and so on. Note: Thestatus signal addresses are acquired during load initialization; subse-quent on-line edits of the module terminals are ignored.

The status value is a sum of the various error codes which come froma Remote I/O Rack.

For example, if the value on the STATUS terminal is 5.0, then theerror conditions 1 and 4, from the previous table, exist at the RemoteI/O Rack. Hence, one or more boards failed diagnostics and at leastone board is missing in the Remote I/O Rack, but communications arestill functioning.

If a communications failure has occurred with the Remote I/O Rack,the STATUS terminal is set to -1.0, and no other status codes can bereceived.

BLANK PAGE

SchedulerScheduler Module

Page Scheduler-1




The Scheduler Module is used to equalize the elapsed running time ofa number of external devices. It provides a device work list that can bescheduled by one of four algorithms that determine the sequence ofoperation. Devices may be added to, or removed from the work list atany time without disturbing scheduling of the other devices.


STROBE

enables or inhibits the next scheduled output during its transitionfrom OFF to ON, depending on the value of the STATE terminal.

STATE

determines whether the next scheduled device will be turned on or offwhen the module is enabled at the STROBE terminal. When thissignal is set to ON, the module turns the next scheduled output on.When this signal is OFF, the module turns the next scheduled outputoff.

UNAVAILABLE n

FAIL_STATE n

RANK n

MODE

RESET

STROBE

OUTPUT n

TRACK

STATE

Scheduler

Scheduler


Page Scheduler-2


RESET

resets all OUTPUT terminals to OFF when RESET is ON. At thesame time it also resets each sequence number for each OUTPUT tozero and resets the TRACK signal to OFF. Any transitions at theSTROBE terminal are ignored during a RESET. When the RESETterminal is set to the OFF state, the module’s logic is processednormally.

MODE

selects the type of scheduling as shown in the following table. Validentries are integers from 1 to 4. Decimal entries will be rounded. Forusers with PLS04.10 firmware (or newer), integers from -1 to -4 arealso supported. The only difference between positive and negativeMODE entries concerns the OUTPUT terminals, discussed later.

1 or -1 = First On, Last Off Selection Sequence2 or -2 = First On, First Off Selection Sequence3 or -3 = By rank: Lowest-to-Highest going on;

Highest-to-Lowest going off.4 or -4 = By rank: Lowest-to-Highest going on;

Lowest-to-Highest going off.

If any MODE terminal entry is anything other than the values listedabove, the module will default to mode 1. The MODE can be changedat any time during operation.


Default: 1Format: Analog signalInput/Output: Input


Page Scheduler-3



is ON when the last available external device has been enabled.TRACK is returned to the OFF state when one or more OUTPUTs(devices) are available or when a RESET occurs.

UNAVAILABLE Default: OFFFormat: Logical signalInput/Output: Input

indicates that the device associated with this terminal is not availablefor scheduling when this signal is ON. The OFF state indicates avail-ability. Sixty four UNAVAILABLE terminals are provided and eachexternal device should be assigned to a separate terminal.

FAIL_STATE Default: OFFFormat: Logical signalInput/Output: Input

indicates that the external device has failed and is not available forscheduling when this terminal is ON. An OFF state indicates that thedevice is functioning normally. Sixty four FAIL_STATE terminals areprovided and each external device should be assigned to a separateterminal.

RANK Default: 0Format: Analog signalInput/Output: Input

indicates a user-defined rank or priority for the device. RANK can be


Page Scheduler-4


a fixed value (when the terminal is assigned a numerical entry) or acomputed value (when a signal is assigned to this terminal) represent-ing the accumulated run time of the device. This signal may be ob-tained from an Integrator or Command Module.

Sixty four RANK terminals are provided and each external deviceshould be assigned to a separate terminal.

OUTPUT Default: NoneFormat: Logical signalInput/Output: Output

indicates that the external device has been scheduled (operating)when set to the ON state. When the signal at this terminal is OFF, itindicates that the external device is not scheduled. For MODES 1 to 4,if a scheduled device is unavailable or it has failed, the associatedOUTPUT will be turned OFF.

For MODES -1 to -4, if a scheduled device has failed, the associatedOUTPUT will be turned OFF.

For MODES -1 to -4, if a scheduled device is unavailable, but has notfailed, the associated OUTPUT will NOT be changed.

Sixty four OUTPUT terminals are provided and each external deviceshould be assigned to a separate terminal.

❏ Module OperationOne application for the Scheduler Module is to use several pumps tomaintain the level of a liquid in a tank. In this application, the pumpsserve as the devices, while an equivalent number of float levelswitches serve as actuators. Depending upon how fast that liquid isdrawn from the tank, the float level actuators will turn on one or morepumps to maintain the liquid at the desired level. Because each pump


Page Scheduler-5


operates below a specific level, some pumps will operate more thanothers and have a higher rate of wear. Used in this application, theScheduler Module will schedule the operation of each pump so thatthe running time is equally distributed among all pumps.

Each external device is represented by three input terminals. Theseterminals, called UNAVAILABLE, FAIL STATE, and RANK, providestatus information for each device. The UNAVAILABLE terminal,when ON, indicates that the applicable device is removed from theschedule, perhaps due to intervention by the on-site operator. TheFAIL STATE terminal, when ON, indicates that the device is out ofservice due to a failure. And the RANK terminal, which is assigned anumber of any value, is used to designate a priority of operation forthe device. In an alternate configuration, this terminal can also be ananalog signal that represents the accumulated run time of the pump.

The STROBE terminal requires a logical control signal, that enablesor inhibits the scheduling of a device. This terminal operates inconjunction with the STATE terminal. If the STATE terminal isturned ON and the STROBE terminal is enabled (OFF-to-ON transi-tion), the next available device will be scheduled to turn ON If theSTATE is OFF when the STROBE terminal is enabled, the nextselected device will be turned OFF and removed from the schedule.

The Scheduler can be operated in one of eight algorithms via theMODE terminal. MODE 1 (and MODE -1) is the First On, Last Offsequence. In this sequence the device that was turned on at the startof the schedule, will be the last to be turned off when the schedule hasbeen completed. Assuming a four- pump control application, pumps 1,2, 3 and 4 will be turned on in numerical sequence (1-2-3-4) in order tobring the liquid in the tank up to a desired level. As this level isapproached, the pumps will be turned off in reverse sequence (4-3-2-1). The only difference between MODE 1 and MODE -1 is that inMODE -1, the UNAVAILABLE signal has no effect on the value of theOUTPUT.


Page Scheduler-6


MODE 2 (and MODE -2) provides the First On, First Off sequence inwhich the devices are turned on and off in the same sequence. Usingthe previous four-pump control application, the pumps will be turnedon in a 1-2-3-4 sequence and turned off in the same 1-2-3-4 sequence.The only difference between MODE 2 and MODE -2 is that for MODE-2, the UNAVAILABLE signal has no effect on the value of the OUT-PUT.

Rather than sequence the devices in an assigned order, modes 3, -3and 4, -4 do it by rank. A device’s rank may be determined by itsaccumulated run time or some other accumulative function. MODE 3and -3 provides lowest-to-highest rank going on, and highest-to-lowestrank going off. MODE 4 and -4 provides lowest- to- highest rank goingeither on or off.

As an example, assume that four pumps have respective run times of25, 11, 40 and 3 hours. For MODE 3, these pumps would be turned onin a 3-11-25-40 sequence and turned off in a 40-25-11-3 sequence aseach objective is reached. For MODE 4, these same pumps would beturned on in 3-11-25-40 sequence, and also be turned off in the same3-11-25-40 sequence.

Again, the only difference between MODE 3 and MODE -3, andMODE 4, and MODE -4, is that in the negative MODEs, the UN-AVAILABLE signal has no effect on the value of the OUTPUT.

The RESET terminal is used to clear the module and set all OUT-PUTS (1-255) to zero. After a RESET, the module will start a freshsequence.

The TRACK terminal is a logical output signal that lets the user orthe system know when all external devices are turned on and operat-ing. If all available devices are running, the TRACK signal turns onand all sequencing commands are ignored. As soon as a device be-comes available, the TRACK signal goes off.


Page Sequencer-1

SequencerSequencer Module

The Sequencer Module is used in applications where a number ofoperations must be performed on a repetitive or sequential basis. Themodule accepts a maximum of 255 status input signals and provides acorresponding number of outputs.

Module TerminalsSTROBE

is a timing signal that, when switched from an OFF-to-ON state,advances the sequential selection of the INPUT signals. The STROBEis inhibited when the sequencer locates an INPUT signal that is in theON state.

STATE

identifies the selected OUTPUT terminal which is currently in an ONstate.



12

3

4

255

12

3

4

255

Input Output

OutputInput

Strobe State

Sequencer


Page Sequencer-2


INPUT

is the status of an external device. This module provides 255 INPUTterminals.

OUTPUT

is the output of the module. Each of the 255 OUTPUT terminalscorrespond to an INPUT terminal.


Default: OFFFormat: Logical signalInput/Output: Output

1

2

3

4

5

6

Implementing a four-stepsequence using a six-stepmodule. There are twospare steps.

In this example, sixvalves are opened andclosed in a rotatingsequence.

One valve at a time isopened for 2 minutes.

12

3

4

5

6

One pulse everytwo minutes

V1V2V3V4V5V6

DO


Page Sequencer-3


Principles of Operation

The module operation is dependent upon the status of its input sig-nals. For example, if all INPUT terminals are left unwired, they willdefault to their OFF state. As such, all corresponding OUTPUTS willalso be in an OFF state, except the one that is selected. When a timingsignal is connected to the STROBE terminal, the module will advanceone step for each OFF-to- ON transition. Initially, the module willstart counting from the lowest to the highest-numbered INPUTterminal (from 1 to 255).

During sequencing, each input that is selected will have its OUTPUTterminal turned ON for the strobed period. When the module ad-vances to the next INPUT, the corresponding OUTPUT terminal willbe turned ON and the previous terminal will be turned OFF, etc. Afterthe highest-numbered input is selected (#255), the sequencing actionreloops back to the lowest input (#1) and the cycle continues.

When status signals are wired to the INPUT terminals, the sequenc-ing operation of the module is affected. As long as all INPUTS are inan OFF state, the sequencing action operates as previously described.However, when an INPUT is found to be in an ON state, the STROBEis inhibited and sequencing is stopped. The corresponding OUTPUT isthen forced ON and remains so until the selected INPUT is turnedOFF. Once this occurs, the strobe is enabled and the module resumescounting upward toward the next highest-numbered INPUT. Asbefore, sequencing continues until the module encounters the nextINPUT terminal that is in an ON state. In situations where two ormore INPUTS are in an ON state, the one having the nearest numberin sequence will be selected first.

BLANK PAGE


Page Signals-1

Signals

❏ Signal TypesACCOL signals can be analog, logical or string signals.

Analog Signals

Analog signals are stored as 4-byte floating point numbers instandard IEEE format. The normalized non-zero numerical valueof a signal can range from

+1.175494 x 10-38 to +3.402823 x 1038

Logical Signals

Logical signals are bi-state, discrete signals that are assigned anON or OFF state. Each state of a logical signal is defined below.

TRUE = ON = 1FALSE = OFF = 0

String Signals

A string signal is a message composed of a group of characters orwords that is associated with a signal name. The string signal hasno numerical value or logical status. Its value is equal to its mes-sage. In the example below, the signal named ST10.LL.21 functionsas a carrier for a message about the water level in tank 10.

ST10.LL.21 = TANK 10 WATER LEVEL BELOW NORMAL

The text of the string signal can be up to 64 characters in length,including spaces between words. String signals are typically usedon certain modules to output readable status messages. Certainsupervisory systems can also make use of string signals.

There are also functions provided for string manipulation within the

Signals


Page Signals-2

Signals

Calculator Module. These functions include checking whether a stringsignal's value is equal to another string, and concatenation of twostrings.

❏ Signal Names

A signal name functions as a place holder for a value. The value of asignal may be constant or it can be changed manually by the ACCOLprogrammer or changed automatically by an ACCOL module.

A signal name should be chosen to convey its purpose. For instance,the signal PRESS.VLV3.OUT is the pressure of the third output valve.

A signal name is an alphanumeric code consisting of three elementscalled base, extension, and attribute. Each element is separated by aperiod, without spaces, in the following order:

CONTROL.882.OUT

base extension attribute

The base can be 1 to 8 characters in length. The first character mustbe a letter (A through Z), while the remaining ones may be any mix ofletters and numbers. Any lower-case keyboard entries (a-z) are con-verted to upper case letters by the ACCOL tools, either as they areentered, or during the file compilation process.

The extension and attribute are optional. The extension can be up to 6characters long. The attribute can be up to 4 characters long. Any mixof letters and numbers is permitted.


Page Signals-3

Signals

o Signal Name Variations

A signal name can have several variations. All signals must have abase. For consistency purposes, if the attribute is omitted, the periodfollowing the extension should be included. Likewise, if the extensionand attribute are omitted, two periods should be included after thebase. If the extension is omitted, but the attribute is used, bothperiods must always be included. Up to 255 attributes and 255 exten-sions can be entered in a load. Signals are common to all tasks withinthe load.

Some examples of legal signal names are shown below.

PRESSURE.VALVE3.OUT (base.extension.attribute)PRESS.VLV3.OUT (base.extension.attribute)PRESS.V3OUT. (base.extension)PV3.. (base only)P.. (base only)PRESS..OUT (base..attribute)

❏ÿMaximum Number of SignalsProvided you have enough memory available in your ACCOL load, thefollowing number of signals may be defined:

ACCOL Version Max. Signals

6.0 (or newer) 21,000 (Approximate)5.9 (or newer) 35005.8 (or earlier) 2500


Page Signals-4

Signals

❏ Signal Characteristics

Initial State - This is the value the signal will assume when theprogram is initially loaded. The signal will remain in this state untilit is changed manually by the operator or by the system.

Manual Enable/Inhibit - By marking a signal manual inhibited, youcan prevent accidental changes by the operator/user. To change asignal on-line, the signal must first be deliberately set to manualenable before the value or status can be modified by the operator/user. The default for all user-created signals is manual enable.

Control Enable/Inhibit - The value or status of a signal can also bechanged by ACCOL modules if the signal is set to control enable. Ifthe signal is control inhibited, no ACCOL module can change thevalue or status of the signal. The default for all user-created signalsis control enable.

Manual/Control Enable/Inhibit Settings

Signal Characteristic Signal’s value (or status) determined by:_____________________ _________________________________

manual inhibit and automatic control by system onlycontrol enable

manual enable and manual on-line entry by the operator onlycontrol inhibit

manual enable and system and operator both can modify,control enable however system can override operator

changes

manual inhibit and initial or last value. The signal's valuecontrol inhibit is frozen.


Page Signals-5

Signals

On/Off Text - ACCOL assigns a specific text to a logical signal whenthe signal is in the ON state, and another text when the signal is inthe OFF state. Usually, the words ON and OFF are used but whenthis is not appropriate, other text can be assigned. The default textis ON/OFF. Both the ON text and OFF text can be up to 6 charac-ters in length.

Read Priority - This number is the minimum security level required bya person in order to read this signal value. The default for all user-created signals is 1. Read priorities can range from 1 to 4.

Write Priority - This number is the minimum security level requiredby a person in order to change the signal value or status. Thedefault for all user-created signals is 3. Write priorities can rangefrom 1 to 4.

Base name text refers to a descriptive text that can be associated withthe base part of the signal name. When assigned to a particularbase, this descriptive text, called the base name text, will then beassociated with every signal that has that same base in its name.The base name text can be 1 to 64 characters in length.

The base name text can be defined in two ways: The first way is todefine the base name text as a string constant. If you are using AIC,the text is entered directly in the appropriate field of the AIC signalmenu; if you are using the ABC or ACCOL Workbench, it is enteredin the *BASENAMES section of the ACCOL source file. The secondmethod is to name a string signal. The base name text is then thevalue of the string signal. The base name text is called constant textwhen the first method is used and indirect text when a string signalis used. If the base name text is indirect text, it can be changed on-line, while the controller is executing your program. When the basename text is constant text, it can only be changed off-line, before theload is downloaded to the controller.

Base name text is visible in alarm messages when the SystemSignal #ALARM.FORMAT is set ON. See 'System Signals' later inthis manual.


Page Signals-6

Signals

Local and global are used by the Data Base Builder (DBB) program inthe Enterprise Server. When a signal is marked GLOBAL, DBB willassign that signal a location in the Real Time Data Base. WhenEnterprise configuration is complete, these signals will be periodi-cally polled and deposited in that data base.

Signals which are not to be built in the RTDB should be markedlocal. Remember that all signals can be accessed from the Enter-prise workstation using SignalView, whether or not the signal ismarked local or global in the ACCOL load.

If the signals are to be displayed or logged at the Network Monitoror if there is no Network Monitor or Enterprise Server in yournetwork, it doesn’t matter if the signal is marked local or global.

The default for all signals is local.

Initial state value - the normalized non-zero numerical range of ananalog signal is + 1.175494x10-38 to + 3.402823x1038. In some cases,the ACCOL software will convert very large or very small initialvalue entries to exponential form.

Units text - This text is meant as a label for your use. Changing thistext will not cause an automatic conversion of the engineering unitsfor the signal. Examples of units text include counts, errors, hours,mins, and secs. Units text can be up to 6 characters in length.

Alarm signals will have the following characteristics.

Logical alarm type - The alarm state for a logical alarm signal can bedefined to be one of three conditions: 1) An alarm state exists whenthe signal is in the ON state. 2) An alarm state exists when thesignal is in the OFF state. 3) An alarm state exists when the signalchanges state. In this last situation, the signal goes into alarm everytime the signal goes from ON to OFF or from OFF to ON. The


Page Signals-7

Signals

default for all user-created signals is that an alarm state existswhen the logical alarm signal is ON.

Alarm Priority - There are four alarm priorities in ACCOL: critical,non-critical, operator guide, and event. These priorities indicate therelative importance of the alarm, with critical priority being themost important and event being the lowest priority.

These priorities are provided for the convenience of the operator.They are not used by the ACCOL software and are merely passedalong to the Network Monitor or Enterprise Workstation. Depend-ing on the programming of these computers, alarm priorities maydetermine the color of the alarm message, cause audible alarms tosound or require acknowledgement from the operator.

The following are provided as guidelines.

� Critical - indicates danger to personnel or equipment. Thispriority requires immediate operator acknowledgement andaction.

� Non-critical - requires operator action, but not necessarilyimmediate action.

� Operator Guide - provides the operator with information, such asthe initiation or result of a control operation.

� Event - provides information on other low priority events.

The default for all user-created alarm signals is critical.

Alarm enable/inhibit - When alarm inhibit is indicated, global mes-sages that are ordinarily generated by an alarm condition will besuppressed. This setting will only inhibit out going messages. Evenwhen set to alarm inhibit, alarm information is still available toother modules within the load. The default for all signals is enabled.


Page Signals-8

Signals

If a signal is changed on-line from alarm inhibit to alarm enableand that signal was in alarm at that time, a new global alarmmessage is generated for the alarm condition.

An analog alarm signal can have as many as four separate alarmsassociated with it. They are low, low-low, high, and high-high. Eachcan be assigned its own priority.

Deadbands are available for high and low alarms. These values repre-sent offsets from the high and low alarm limits. If an analog signalgoes into alarm, it must return past the limit adjusted by thedeadband value before the alarm can be cleared. For example, if thehigh limit is 100 and the deadband is 10, the signal will go intoalarm when it goes above 100, but it will not clear until it goes backbelow 90 (100-10). This arrangement will prevent the signal fromturning on and off too quickly if the signal oscillates at the thresholdof the alarm limit.

The high deadband affects the high and high-high alarms independ-ently. The high-high alarm will clear when the signal drops belowhigh-high limit minus the deadband, and the high alarm will clearseparately when the signal drops below the high limit minus thedeadband.

Similarly, the low deadband affects the low and low-low alarmswhich are cleared when the signal rises above the respective alarmlimit plus the deadband.

RBE (Report By Exception) allows a signal to be designated for datacollection only when it has changed in such a way that it is said tobe 'in exception.' Analog signals designated for RBE also have anassociated RBE deadband. See the 'RBE' section for details.

❏ÿSignal OperatorsArithmetic and logical operators which may be used on signals arediscussed in the section 'Calculator', earlier in this manual.


Page Signal Lists-1

Signal Lists

What are signal lists?

Signal lists are lists of ACCOL signals. Signal lists are used by certainmodules such as the Master, Slave, Mux, and Demux Modules where alarge number of signals are sequentially selected for communicationsor processing. Signal lists are assigned to modules at module termi-nals and cannot be used in statements or equations.

Signal lists are common to all tasks of a load.

Notes

Each signal list is assigned a number from 1 to 255. Signals within thesignal list are referenced by their position in the list. Each list cancontain any mixture of analog, analog alarm, logical, logical alarm, orstring signals. For information on the number of entries in lists, see'Summary of ACCOL II Structures'.

Signal Lists

BLANK PAGE


Page Slave-1

SlaveSlave Module

When a node receives a message from a Master Module, it locates andexecutes the Slave Module with the corresponding point number in anasynchronous fashion, along with any of the ACCOL tasks within thenode. For this reason, Slave Modules should be kept in task 0. If aSlave module is executed in any regular task, it will still operate in anasynchronous manner but will not perform any operation other thanto go on to the next item in the task. While it is not an error to executeSlave Modules at rate, it is more efficient to keep them in a nonex-ecuting task.

Module TerminalsPOINT

is the point number of the Slave Module in the node. When a Mastercommand/request is received, this terminal is examined to find thematching Slave Module for the Master.

ENABLE

will inhibit the Slave Module when it is set to OFF. Any commands orrequests received when the Slave Module is inhibited will cause anerror code to be returned to the Master Module.

ENABLE

INTYPEOUTTYPE

INLISTOUTLIST

POINT

Slave

STATUS_1

STATUS_2


Default: ON (enabled)Format: Logical signalInput/Output: Input

See also: Master/Slave CommunicationsNode Addressing, Master Module

Slave


Page Slave-2

SlaveSlave Module

INTYPE

defines the type of data contained in the INLIST and can assume oneof the following codes:


OUTTYPE

is the type of data contained in the OUTLIST and can assume one ofthe following codes:


INLIST

identifies the number of the signal list or data array to receive datasent from the Master Module. Received data is stored according toparameters set in the Master Module. No default value is applied tothis terminal.

Default: 0 (signal list)Format: Analog signal or constantInput/Output: Input

Default: 0 (signal list)Format: Analog signal or constantInput/Output: Input



Page Slave-3

SlaveSlave Module

OUTLIST

is the signal list or data array from which data will be selected inresponse to a poll from a Master Module. The entire list or array isreturned during transmission.

STATUS_1

indicates the completion of a poll response. If an analog signal is used,it is incremented by 1 upon completion. If a logical signal is used, it isset when the poll/response is completed. It is the responsibility of theuser to reset this signal when required.

STATUS_2

represents the completion or error status of communications. Status isset upon completion of the message. See the table included with theSTATUS_2 terminal description in the 'Master Module' section (ear-lier in this manual) for a list of possible error codes.




BLANK PAGE


Page Smart-1

SmartSmart Module

The Smart Module provides read/write access to the memory in the3508 TeleTrans Transmitter in a GFC 3308 unit. NOTE: Wheneverpossible, users should use the XMTR_Interface Module instead of theSmart Module.


REMOTE Default: 1Format: Analog signal or constantInput/Output: Input

is the remote node address of the TeleTrans Transmitter. Valid rangefor this terminal is 1 to 127. Node address 0 is reserved for communi-cation with a master; it is never a valid transmitter node address.

Node address 127 is the transmitter's broadcast address. This addressshould NOT be used in a multi-drop configuration because ALLtransmitters will respond.

MODE Default: 1 (Read)Format: Analog signal or constantInput/Output: Input

is the mode of operation. Enter 1 for Read or 2 for Write.

REMOTEFORMATCOUNT

STATUS_1

Smart

STATUS_2

LISTADDRESS

to TeleTrans Transmitter

INDEXMODE

Smart


Page Smart-2

SmartSmart Module

FORMAT Default: None, entry is requiredFormat: Analog signal or constantInput/Output: Input

is the type of I/O request. Valid entries are integers from 0 to 4.

TerminalValue I/O Request

0 Logical Byte access. Each bit in a data byte in the messagemaps to the eight consecutive logical signals in the LIST start-ing from the offset defined by INDEX. The first logical signalmaps to byte Bit 7 and the eighth signal maps to Bit 0.

1 Unsigned Integer Byte access. Bytes in the message map to theanalog signals in the LIST starting from the offset defined bythe INDEX terminal. Integer values are converted to floatingpoint values during read access and from floating point tointeger during write access.

2 Signed Integer Byte access. Bytes in the message map to theanalog signals in the LIST starting from the offset defined bythe INDEX terminal. Integer values are converted to floatingpoint values during read access and from floating point tointeger during write access.

3 Unsigned Integer Word access. Words in the message map tothe analog signals in the LIST starting from the offset definedby the INDEX terminal. Integer values are converted to floatingpoint values during read access and from floating point tointeger during write access.

4 Signed Integer Word access. Words in the message map to theanalog signals in the LIST starting from the offset defined bythe INDEX terminal. Integer values are converted to floatingpoint values during read access and from floating point tointeger during write access.


Page Smart-3

SmartSmart Module

COUNT Default: 8 for Format 0, 1 for Formats 1through 4


is the number of data elements (bits, bytes, or words) to be trans-ferred. The range is 8 to 160 bits (in multiples of 8 bits ONLY) whenFORMAT=0. The range is 1 to 20 for byte requests when FORMAT = 1or 2. The range is 1 to 10 for word requests when FORMAT = 3 or 4.

INDEX Default: 1 (first signal in the list)Format: Analog signal or constantInput/Output: Input

is the offset into the signal list specified on the LIST terminal. INDEXmust be less than or equal to the number of signals in the list. A 0 or 1entry is interpreted as the first signal in the list.


is the number of a signal list. Signals in this list are the source ordestination of data during read or write operations, respectively. TheINDEX terminal defines the offset into this list.

ADDRESS Default: None, entry requiredFormat: Analog signal or constantInput/Output: Input

is the address in the TeleTrans Transmitter memory where therequested data transfer takes place. Valid address range:

Read-Req.: 19 and 52 Write-Req: 19 and 5246,592-46,693 46,592-46,693

57,344 and 57,345


Page Smart-4

SmartSmart Module

STATUS_1 Default: NoneFormat: Analog signal or logical signalInput/Output: Output

indicates that communication is complete. If this terminal contains alogical signal, then it is turned OFF when the Smart Module initiatescommunications and set ON when communications are complete. If itis analog, then it is incremented by 1 following a successful messagetransmission.

STATUS_2 Default: NoneFormat: Analog signalInput/Output: Output

is a transaction completion code which is set upon completion ofmodule execution.

Code Description

00 Successful completion-01 Dynamic structures for the module are missing-02 Invalid slave node number (must be 1 to 127)-03 Invalid mode (must be 1 or 2)-04 Invalid request type (must be between 0-4)-05 Invalid LIST value, or LIST terminal unwired-06 LIST is an empty list (No signals defined in list)-07 INDEX number is out of range (index must be < no. of

signals)-08 Invalid value specified on COUNT terminal.-09 Transmitter memory address is incorrect (allowed ranges

are: 19, 52, 46592 to 46693, or 57344 to 57345)-10 Invalid number of elements (FORMAT=0, i.e. bits) but

COUNT is not a multiple of 8.-11 LIST overflow (not enough room in list for requested number

of elements)-12 LIST signal is not logical-13 LIST signal is not analog


Page Smart-5

SmartSmart Module

-14 Signal could not be updated (control inhibited)-15 Mode in transmitter response does not match with mode in

the request that was transmitted-16 Address in transmitter response does not match with the

address in the request that was transmitted-17 Transmitter sent fewer elements than requested

-101 Communication error during request send-102 Communication timeout error-103 Couldn’t allocate a communication buffer

❏ Module OperationThe Smart Module is very similar to the ACCOL Master Module. Itcommunicates with the TeleTrans Transmitter through the Masterport defined within the GFC 3308 Gas Flow Computer.

This module is presently available in the GFC 3308 Gas Flow Comput-ers only.

The Smart Module supports the following functions:

a. Read/Write a logical byte value. Each bit of the logical byte valuemaps to the eight logical signals in the LIST.

b. Read/Write 1-n bytes. Each byte represents “unsigned” integer valueand maps to the analog signals in the LIST starting at the offsetdefined by the INDEX terminal. Integer values are converted to/

MasterPortSmart

Module

Gas Flow Computer TeleTrans Transmitter


Page Smart-6

SmartSmart Module

from the floating point values.

c. Read/Write 1-n bytes. Each byte represents “signed” integer valueand maps to the analog signals in the LIST starting at the offsetdefined by the INDEX terminal. Integer values are converted to/from the floating point values.

d. Read/Write 1-n words. Each word represents “unsigned” integervalue and maps to the analog signals in the LIST starting at theoffset defined by the INDEX terminal. Integer values are convertedto/from the floating point values.

e. Read/Write 1-n words. Each word represents “signed” integer valueand maps to the analog signals in the LIST starting at the offsetdefined by the INDEX terminal. Integer values are converted to/from the floating point values.

CAUTION

Wherever possible, users should utilizethe XMTR_Interface Module (with FOR-MAT values of 10 or above) instead of theSmart Module, because theXMTR_Interface Module allows access torelevant user information without therequirement to specify addresses. Users ofthe Smart Module, must be extremelyfamiliar with transmitter internals beforeattempting to Read/Write data from it.Novice users could potentially corrupttransmitter memory.


Page Stepper-1

StepperStepper Module

The Stepper Module performs a series of sequential operations on anumber of outputs (1-255). It is particularly useful in applicationswhere external equipment must be activated in sequence for certainfixed time periods, such as during water filter backwash operations.

Module TerminalsSTROBE

makes the module advance to the next row of the data array when thissignal makes an OFF-to-ON transition. At that time, the values in therow are written to their respective OUTPUT terminals.

HOLD_OFF

prevents the execution of a step when the next OFF-to-ON transitionoccurs at the STROBE terminal when this signal is turned ON. Thelast STROBE terminal transition is remembered during a “hold off.”When the HOLD OFF terminal is returned to the OFF state, theretained strobe transition initiates a step change. Multiple off-to-on


Default: NoneFormat: Logical signalInput/Output: Input

OUTPUT_nTIME

STEPTRACK

STROBE HOLD_OFF

ARRAYDIRECTIONINDEXRESET_INDEXRESETTRACK_INDEX

STEPPER

Stepper


Page Stepper-2


strobe transitions occurring during a “holdoff” will only result in theoccurrence of a single step change. That step is defined by the statusof signals at the DIRECTION and INDEX terminals at the time ofexecution, when HOLDOFF is turned OFF and not at the time whenHOLDOFF is ON.

DIRECTION

set the direction. When this terminal is set ON, the module executeseach row in a forward direction (lowest to highest numbered row).When set OFF, the module executes in a reverse direction (highest tolowest numbered row). The predecessor of the first row (row 1) isitself, while the successor of the last row is itself, in other words,wrap-around will not occur.

INDEX

references a specific row index of the data array. When this value ischanged on-line, the module proceeds to the designated row and stopsthe stepping action. The module will remain in this mode until a zeroor negative value is entered at this terminal. The next STROBE pulsewill then index the module to the next row in sequence based on theDIRECTION the module is sequencing in.

If an analog variable (stepped signal) is wired to this terminal, it willcause the module to execute a different sequence of steps. This allowsthe user to use several different row sequences without rearrangingthe data array.

Default: ON (forward)Format: Logical signalInput/Output: Input



Page Stepper-3


RESET

interrupts normal sequencing and resets to the row indicated on theRESET INDEX terminal when RESET terminal is ON.

RESET_INDEX

identifies a particular row of the data array. This row will be activatedwhen the RESET terminal is ON.

If left unwired and sequencing is occuring in the forward DIREC-TION, this terminal defaults to a value of 1 and the first row of thedata array is referenced when RESET is activated. If this terminal isunwired and sequencing is occuring in the reverse DIRECTION, thisterminal defaults to whatever data array row is last and the last rowof the data array would be referenced when RESET is activated.

TRACK

will turn ON whenever the STEP (row) number equals the TRACKINDEX, and will be turned OFF for all other steps. The TRACK signalmay be used by other modules to initiate a particular action or set ofactions when a particular step in the sequence is reached.

TRACK_INDEX

designates the step to be tracked. When the value of the selected step


Default: (See below)Format: Analog signalInput/Output: Input




Page Stepper-4


is the same as the value of the active step, the TRACK terminal is setto an ON state.

If left unwired, the TRACK signal is processed as if the TRACKINDEX signal were equal to 1 when the DIRECTION terminal isturned OFF, and as if the TRACK INDEX signal were equal to thehighest row index when the DIRECTION terminal is turned ON. Inother words, when this terminal is unwired, TRACK is turned ONwhen the module sequences to the limit of the data array, dependingon which direction it is sequencing in.

STEP

identifies the row of the data array which is currently active. (Thecurrently active row becomes active as a result of a STROBE or aRESET).

TIME

specifies the total period of time, in seconds, since an off-to-on transi-tion of the STROBE terminal or a RESET has occured. Becausestrobes and resets normally generate a step to a new row, TIMEindicates how long the currently active row (as indicated on the STEPterminal) has been active. This terminal may be monitored to detectexcessive time in any one step. A condition like this might occur ifsome external action necessary for a strobe to occur fails to take place(such as a pump not starting or a valve not opening).




Page Stepper-5


ARRAY

indicates the number of the data array which holds the output valuesto be used by the module. A negative value indicates a logical array,while a positive number indicates an analog array.

OUTPUT

is the output of this module and is wired to the process to be con-trolled. These terminals receive their values from a selected row of theanalog or logical data array. The row used for the OUTPUT values ischanged when the module is strobed or reset via the STROBE andRESET terminals. The number of signals corresponds to the numberof columns in the data array.

A maximum of 255 output signals are available to be connected toexternal devices. Output 1 corresponds to column #1, Output 2 corre-sponds to column #2 and so on. If there are more signals than col-umns, the extra signals will be ignored. If there are fewer signals thancolumns, then the extra columns will be ignored.

All data conversions are standard. Analog values not equal to zero areconsidered TRUE, while values of zero and below are consideredFALSE. Logical signals in a TRUE state are considered equal to 1.0,while those in a FALSE state are equal to zero.

Default: None, entry required. Module willnot execute if terminal does notreference valid data array.


Default: None, entry requiredFormat: Analog or Logical signalInput/Output: Output


Page Stepper-6


Module Operation

At each step in the sequence, the output of the Stepper Module ischanged according to a pattern defined by the ACCOL programmer.The pattern is stored as data in an analog or logical data array.

Each column of the array is associated with a specific output signalwhile each row corresponds to a step in the sequence. Therefore, ateach specific column and row position in the array, a data value isstored which represents the value of a specific output signal at aparticular step in the sequence. In other words, an entire row of thedata array contains the value of each of the output signals during aspecific step of the sequence.

Movement from one step to another is controlled by the STROBEsignal, and the time between “strobes” determines how long a particu-lar step in the sequence remains in effect.

Example:

The Stepper Module will be used to provide a series of 6 operations on7 external, on-off, electrically actuated valves. An output that is ONindicates an open valve, while one that is OFF indicates a closedvalve. This problem can be solved by constructing a 7 x 6 logical dataarray as shown on the following page.

COLUMNS (Outputs)

1 2 3 4 5 6 7 ROWS(Sequence Step) 1 on on off off off off off

2 on on off on on off off3 off off off off off on on4 off off on on off off off5 off off on off off off off6 off off off off off off off


Page Stepper-7


For the first step (row 1), outputs 1 and 2 are turned “on,” whileoutputs 3 to 7 are kept “off.” For the second step (row 2), outputs 1, 2,4 and 5 are placed “on,” while outputs 3, 6 and 7 are “off.” When step6 (row 6) is reached, all outputs (1-7) are turned OFF to complete thesequence.

The ARRAY terminal of the module designates the data array contain-ing the values to produce the desired operations, while the OUTPUTterminals (1- 255) identify the outputs which will be controlled by thesequencing.

The Stepper Module also provides stepping in both the forward orreverse directions. This selection is made at the DIRECTION termi-nal, and requires the INDEX terminal to be unwired, or set to a valuewhich is less than or equal to zero.

The INDEX terminal allows the user or system to enter a specific rownumber of the data array which, when a strobe occurs, will cause thearray to index that row of the array. The module will then providethat row as outputs until either the value at the INDEX terminal ischanged, or the Stepper module is RESET. An index of 1 correspondsto the first row of the data array; an index of 2 corresponds to thesecond row of the data array, and so on.

The module can be made to break the normal sequencing operationvia the RESET terminal, and output a target row identified at theRESET INDEX terminal. That row will continue to provide themodule outputs as long as the RESET terminal is on. After the RE-SET terminal is turned off, sequencing will continue on subsequentstrobes based on the INDEX and DIRECTION terminals.

The Stepper Module can indicate the completion of a selected row. Thetargeted row is entered at the TRACK INDEX terminal and read viathe TRACK terminal. When the active row number is equal to theTRACK INDEX value, the TRACK terminal will be turned “on.”

The total period of time for each step in the sequence is tracked by themodule. The time, in seconds, is indicated at the TIME terminal. The


Page Stepper-8


TIME is reset to zero each time the module is strobed or reset. InPROMS sets earlier than S3 or AC.xx, the TIME terminal was onlyzeroed out when a STROBE occurred.


Page Storage-1

StorageStorage Module

The Storage Module is essentially a track/hold device that stores andretrieves data. Data can be transferred between a signal list and dataarray or between the module’s INPUT terminals and the data array.Also, in lieu of a data array, data can be stored expanded memory.

❏ Module TerminalsRESET Default: OFF


resets all elements of a read/write data array to zero when RESETmakes an OFF-to-ON transition.

This signal cannot be used to reset a read only data array since thesearrays contain fixed data.

This terminal must be left unwired when using the Historical DataStorage function, or module read/write operations will not execute.

ARRAY

TYPE

COLUMN

INDEX

STORAGE

LIST

INPUT_n

STATUS

RESET

READWRITE

Storage


Page Storage-2


READ Default: OFFFormat: Logical signalInput/Output: Input

makes the module read data from the data array or expanded memoryand writes signal values into the specified signal list when this termi-nal is ON.

WRITE Default: OFFFormat: Logical signalInput/Output: Input

causes the module to write data from the specified signal list into thedata array or expanded memory when the WRITE terminal is in theON state.

The module will not execute if signals at the READ and WRITEterminals are both in the ON state, or are both in the OFF state, orleft unwired.

COLUMN Default: FALSE (row index)Format: Logical signalInput/Output: Input

selects access by row index or column index for the data array func-tion. FALSE indicates row index, while TRUE indicates column index.

When using Historical Data Storage, this terminal must be leftunwired or the module will not execute.


Page Storage-3


INDEX Default: None, entry requiredFormat: Analog signalInput/Output: Input

specifies the row/column of the data array or the row (record) inexpanded memory to access. The module will not execute if thisterminal is less than or equal to zero, is larger than the data array’srow/column dimension or is larger than the maximum row supportedby the expanded memory,

ARRAY Default: None. If unwired, the HistoricalData Storage is assumed.


identifies a data array. The data array must be a read/write array.

TYPE Default: FALSEFormat: Logical signalInput/Output: Input

specifies the type of the data array. FALSE indicates analog, while theTRUE state indicates logical. When using Historical Data Storage thisterminal must be left unwired or the module will not execute.

STATUS Default: None, entry requiredFormat: Analog signalInput/Output: Output

indicates the execution status of the module according to the followinglist of the status messages:


Page Storage-4


0 = Successful module execution.1 = Non-executable mode specification:

a) the READ and WRITE signals are both ONb) the READ and WRITE signals are both OFF or UNWIREDc) Expanded Memory is to be used (ARRAY signal is UN-

WIRED) and the RESET, COLUMN, and/or TYPE signalsare not also UNWIRED.

2 = The ARRAY value is invalid. Examples: An ARRAY value of 5has been entered but the available arrays are only 1, 2 and 3.Or, array #5 exists as an analog array but the TYPE signalindicates a logical array. In systems which do not supportHistorical Data Storage, status message 2 may also indicatethat the ARRAY terminal is UNWIRED.

3 = Attempt to reset or write to a Read-Only data array.

4 = The INDEX terminal is UNWIRED, the value is less than orequal to zero, or the value exceeds the array’s row or columndimension (or maximum row supported by the expandedmemory).

5 = The LIST terminal is UNWIRED or references an emptysignal list and there are no signals named at the INPUTterminals.

6 = Invalid Signal Type - e.g. String signal in signal list whenexecuting the data array function.

7 = Expanded Memory not allocated for this function.

8 = Expanded Memory data not consistent with target signal type.

9 = One or more string signal lengths did not match when writingto the Master Signal Directory. The shortest length controlsthe operation.

10 = Overrun - the limit of the Expanded Memory was reachedprior to completing the requested operation.


Page Storage-5


LIST Default: See terminal description belowFormat: Analog signal or constantInput/Output: Input

identifies an ACCOL signal list. If this terminal is unwired or if thespecified signal list does not exist or is empty, the module will use theINPUT terminals.

The types of signals that are valid depends on the function beingexecuted.

INPUT Default: NoneFormat: Analog or Logical signalInput/Output: Input and output

A maximum of 255 terminals are provided for input and outputsignals. The signals may be entered here in lieu of placing them in asignal list. The INPUT signals automatically become active if the LISTterminal is left UNWIRED or specifies a nonexistent or empty list.

Note that string signals may not be wired to the INPUT terminals.

❏ Data Array Function

This function is available in any controller configuration that supportsthe Storage Module, including redundant configurations.

When a valid data array is specified on the ARRAY terminal and theREAD terminal is ON, this module retrieves logical and analog signalvalues from the array and writes these values to a signal list or theINPUT terminals. When READ is OFF and the WRITE terminal isON, the module reads signal values from a signal list or the INPUTterminals and stores these values in the array.


Page Storage-6


The data array can be processed in either row or column mode, witheach execution of the module processing one row or one column, asspecified by the COLUMN and INDEX terminals. The data array typemay be specified as either analog or logical via the TYPE terminal.Both read only and read/write arrays can be used depending on thedirection of transfer.

Data conversion will be performed automatically by the module whenthe signal type and data array type are not the same, following stan-dard ACCOL conventions. Analog values not equal to zero are consid-ered TRUE, while a zero value is considered FALSE. Logical valuesthat are TRUE are considered equal to 1.0, while those that areFALSE are considered equal to 0.0. Unwired INPUT terminals pre-ceding the last wired INPUT terminal will be processed as if theywere control-inhibited logical signals set to the OFF or FALSE state.For example, when accessed as a source, they will result in a logicalOFF or analog 0.0 value being stored in the target data array. Whenaccessed as a destination, the unwired list entry and its correspondingdata array element will be passed over and processing will continuewith the next list entry and data array element.

The dimensions of the rows or columns in the data array place a limiton the number of usable signals in the signal list or INPUT terminals.If there are more signals than the data array row or column canaccommodate, the extra signals will be ignored. If the data array rowor column has more capacity than the list of signals can supply, thenthe extra row or column entries will be ignored.

The entire data array may be reset, or cleared, using the RESETterminal if the array is of the read/write type.


Page Storage-7


❏ Historical Data Storage Function

If you’re planning to use the Storage Module for historical data stor-age, your controller must contain expanded memory.* If you haveACCOL 5.0 or later versions, you must also indicate the size of thedata array used by the Storage Module. This can be done on theMemory Configuration Menu (if you are using the ACCOL II Interac-tive Compiler) or in the *MEMORY section (if you are using theACCOL II Batch Compiler or ACCOL Workbench). The StorageModule’s historical data function is not supported in redundantconfigurations.

To collect historical data, the Storage Module uses expanded memoryto store selected groups of logical, analog, and/or string signal valuesat the local controller. These groups of values may be retrieved at alater time and restored to the original signals, or be written to othersignals of the same type.

The expanded memory is viewed by the Historical Data Storagefunction as a two-dimensional byte array having a fixed columndimension of 64 bytes. The user addresses the expanded memory as aseries of sequential 64-byte rows numbered 1 through ‘N’ where ‘N’ iscalculated by dividing the total bytes available by 64. This organiza-tion can also be viewed as a single track mass storage device with ‘N’records and a fixed physical record size of 64 bytes. The element sizeof 64 bytes is strictly a mechanism to provide for user addressing at agranularity that will make efficient use of the space available. It is notused to restrict the storage of data which is stored sequentially begin-ning at a 64-byte boundary without regard to subsequent boundarycrossings. Partitioning of the expanded memory and maintenance ofindex values (starting row number) for particular blocks of data is auser responsibility. Synchronization of processes storing data andprocesses retrieving data is also a user responsibility.

*The exception to this rule is if you have a controller with the386EX Protected Mode CPU, with PLS00/PLX00 (or newer)firmware. The concept of expanded memory does not apply tothese units.


Page Storage-8


Expanded Memory Access

Access to the expanded memory is controlled through the StorageModule. This feature is activated by leaving the ARRAY terminalUNWIRED.

The user specifies the Starting Row Number via the INDEX terminal,the direction of transfer via the READ terminal or WRITE terminal,and the source or destination signals by either an external signal list(LIST terminal) or the module internal INPUT terminals. If a signallist is used, string signals may be included as well as analog andlogical signals; string signals may not be specified for the internalINPUT terminals. Note that inclusion of string signals in a signal listfor this application is not compatible with signal lists used for Net-work Monitor Historical Data Collection.

Writing to the Expanded Memory (WRITE Active)

Data will be stored sequentially beginning at the first byte of theindicated Row or Record and continuing until the entire list of signalshas been processed, or until there is insufficient memory available tostore the current data entity. Unused bytes in the last 64-byte recordof a block will be written to all ones (0FFH) to avoid being read asvalid data. If there are more signals to be processed when the end ofthe expanded memory is detected, execution will be terminated anderror code 10 will be stored in the Storage Module STATUS signal.The size of the memory block is determined by the length of the signallist and the types of signals it contains. Record boundaries andmemory segment boundaries occurring within the block do not affectthe storage of data; a particular data entity may cross a record bound-ary, depending on the organization of the source list. If this occurs atthe last record in a 64K-byte segment, the data entity and the block inwhich it is contained will also cross the segment boundary; this will betransparent to the user of the Storage Module.

There will be no data conversion: a logical signal will be stored as a 1-


Page Storage-9


byte value of either zero (FALSE or OFF) or one (TRUE or ON); ananalog signal will be stored as a 4-byte IEEE Std. format floatingpoint number with a 1-byte type identifier prefix of 02; a string signalwill be stored as a series of up to 64 ASCII characters null terminatedwith a 2-byte prefix containing a type identifier of 03 and the stringlength. See Table 3-11 for a listing of the data formats.

Any unwired INPUT terminals preceding the last wired INPUTterminal will be processed as if they were logical signals in the OFF orFALSE state and a single byte of zero will be stored. Having unwiredentries in such a list is not recommended since it can lead to dataerrors when the data is retrieved if the corresponding target list entryis not either unwired or a logical signal.

The string length defined by the user when the ACCOL program iscreated will be used to control the string length copied to the ex-panded memory. At runtime, the string text and/or actual length maybe modified; however, the original length still applies as a maximumsize for the particular string signal. By utilizing this length whenstoring a string in the expanded memory, the use of a particularsignal list will always generate the same size block in the expandedmemory even though the actual string texts may be changing. Thisarrangement allows the user to control block size and expandedmemory partitioning. When interpreting the string, the first nullcharacter (00) encountered determines the current length; the remain-ing portion of the string data does not apply.

The content and organization of the signals is a user responsibility(e.g. inclusion of a time stamp, other identifying information, orgrouping of signal types).

Reading from the Expanded Memory (READ Active)

Reading the data from the expanded memory returns the stored signalvalues to dynamic signals in the local controller Master Signal Direc-tory. Reading requires that the signal list specified (or the sequence ofsignals wired to the Storage Module INPUT terminals) have an


Page Storage-10


identical sequence of signal types to that used when the data wasstored. The module will proceed item by item through the list, access-ing data beginning at the indicated Row or Record and writing thevalue found to the Master Signal Directory if the data is consistentwith the target signal type. If the data is not consistent (the storedtype identifier does not agree with the target signal type or, for logicalsignals, the stored data is not a zero or a one) execution will terminateand error code 8 will be stored in the module STATUS Signal. If theend of the expanded memory is detected before the entire list isprocessed execution will terminate and error code 10 will be stored inthe module STATUS signal.

If the module internal signal list is being used and an unwired entry isencountered, the corresponding data element in the expanded memorymust be a logical value (single byte of zero or one). If it is, executionwill continue with the next data element and next INPUT terminal. Ifit is not, execution will terminate and error code 8 will be stored in themodule STATUS signal.

When retrieving string signals, the stored length must agree with thetarget’s maximum string length as stored in the Master Signal Direc-tory (MSD); if it does not, the shorter length will be used to copy thestring into the MSD. Execution will continue, but a special code of 9will be stored in the module STATUS signal indicating that one ormore strings had lengths that did not match; therefore, the string textmay have been truncated.

Note that the data does not have to be restored to the original signals,but to signals of the same type. The number of signals to be processedon a Read should in general match that used to do the Write to corre-spond to the stored block size. A smaller number of signals mayalways be used to read back one or more signal values at the begin-ning of a block. Signals within the block do not necessarily begin onRow (Record) boundaries and therefore cannot be retrieved individu-ally. Also, if there is unused space in the last record of a block, thedata fill pattern will result in detection of inconsistent data if anattempt is made to read beyond the end of the block.


Page Storage-11


A restored signal list may be processed using other ACCOL functionssuch as the Logger Module or Master/Slave Communications Modulesas appropriate.

NOTE

If a destination signal is a constant or is control inhibited, it will notbe modified. Module execution will continue with the next signal andnext data element; there will be no special status stored to inform theuser of this occurrence.

Historical Data Storage Formats

Signal Type # of bytes Expanded Memory Content

Logical 1 00 01

Analog 5 Type: 02IEEE FormatFlt. Pt.: XX XX XX XX

String 3-67 Type: 03

BLANK PAGE


Page Suspend-1

SuspendSuspend Command

Suspend, like the Abort and Resume commands perform task control.Suspend statement will stop a task from executing. This statementcontains no target task field since it is only used to halt the issuingtask. Once the issuing task is suspended, it can only be reactivatedthrough a Resume statement placed in another task.

SyntaxSUSPEND

ExampleSUSPEND

Suspend

BLANK PAGE


Page System-1

SystemSystem Module

The System Module Menu displays four system signals that areassociated with the currently-selected task. System signals are over-head signals supplied by the system. These signals cannot be edited ordeleted by the user.

In addition, in the on-line mode the System Module Menu shows taskerrors associated with each of these signals. These values are dis-played to the right of the highlighted terminals as shown in thefollowing figure.

This module is not entered or accessed from the module menu likeother ACCOL modules. It is solely used to access the task signals anddisplay task errors.

Four system signals are displayed in the System Module Menu whichis accessed via the “System Signal Access” poke point of the TaskMenu of the ACCOL Interactive Compiler (AIC). They are: taskpriority, task rate, task rate count slippage and task error count.These signal names contain pound sign (#) to make it unique fromregular ACCOL signals as well as a base and extension. The extensionis a three-digit number that identifies the task (001 to 127). Systemsignals can not be edited or deleted from the load.

System ACCOL task 1 Line number 0

PRIORITY #PRI.001. 28.0000000RATE #RATE.001. 5.0000000SLIPPAGE #RCNT.001. 0.0000000ERROR COUNT #ERRCT.001. 0.0000000

This display can also be accessed from the Module Types Menu in thesame manner as any other module. See the ACCOL InteractiveCompiler Manual, D4042, for details.

System

BLANK PAGE

System Signals

Page System Signals-1


System signals are automatically created for every load. These signalscan be used to read dynamic system values or to perform certainfunctions within a load. System signals include parameters such asalarm limits, errors, timing, node failure, date and time. In addition,constants such as pi, e, ON and OFF are available for your conven-ience.

❏ Description

For AIC users, system signals may be viewed through the System0(System Zero) Module. This module can be accessed from the Task0menu of the AIC in the same manner as other ACCOL modules. Thesignal names appearing on the System0 Module Menu can be accessedvia poke point selection to display the corresponding Signal Menu.

ACCOL Workbench users can view system signals by accessing the*SIGNALS section of the ACCOL source file.

When examined on-line (via Toolkit, DataView, etc.) a system signalmay be manually-enabled to have its value set by the operator.

All system signal names are preceded by the # sign. Some samplesignal names are as follows:

#ERRCT.LIM.#TIME.000.#PWRUP.000.

The following system signals ARE NOT AVAILABLE in the EGM3530-20B ACCOL TeleFlow: #DIAG.001, #DIAG.002, #DIAG.003,#LINKE.001, #LINKE.002, #LINKE.LIM, #LINKF.001, #LINKF.002,#LINKF.LIM, #NDARRAY.., #NODE.nnn, #PDM.nnn, #RDN..,#RDNERR.., #RDNLIM..

System Signals



System Signals

This chapter lists all system signals in alphabetical order. Refer to thefollowing table for abbreviations and codes.

Abbreviations and Codes

Menu Option Description

Initial State: The initial state of an analog signal will be given as anumerical value, while that for a logical signal will be given as anON/OFF status.

Control Inhibit:

CE = Control EnableCI = Control InhibitME = Manual EnableMI = Manual Inhibit

Alarm Inhibit:

AE = Alarm EnableAI = Alarm Inhibit

Local/Global: All non-alarm signals will default to “Local” mode. The“Global” mode is used in conjunction with network systems.

Read/Write Priority - The default for the read priority is “1” for allsignals. The default for the write priority is “4” for all signals.

Alarm Type: An analog alarm signal may be configured with High,Low, High-High, and Low-Low alarm limits. Only the active alarmlimit with its alarm priority will be listed. As an example, for thesignals #ERRCT.nnn,

High Limit Alarm: #ERRCT.LIM. Critical

System Signals



❏ System Signals

#ALARM.FORMAT. Type: LogicalInitial State: OFFInhibit Status: MI, CI.

This signal selects a short or long form for alarm messages. The longform includes the base name descriptive text associated with thesignal, while the short form omits the base name descriptive text.

Set this signal ON for the long form or set it OFF for the short form.Also see #ALARM.FORMAT.001 described below.

#ALARM.FORMAT.001 Type: LogicalInitial State: OFFInhibit Status: MI, CI

When this signal is set to OFF, the alarm format is controlled only bythe #ALARM.FORMAT signal described above. When#ALARM.FORMAT.001 is set to ON, an extended alarm format isused. This extended format includes the manual, control, and alarminhibit bits for the signal. Also, both the questionable data bit, and thealarm limit which was exceeded to cause the alarm, will be includedfor analog alarm signals. The extended format will include the basename descriptive text associated with the signal only if the#ALARM.FORMAT signal is also set to ON. (See #ALARM.FORMATabove). NOTE: To use this system signal, you must have AE.0 (orlater) level firmware, ACCOL version 5.4 (or later) and EnterpriseSoftware Version 2.0 (or later).

#ALARM.LIM. Type: AnalogInitial Value: 0.0000000 SECSInhibit Status: MI, CI

This system signal allows you to alter the scan rate of the Alarm Time



System Signals

Stamp Buffers. The scan rate affects how quickly an alarm message isgenerated after one or more entries are made to the Alarm TimeStamp Buffers. This signal is initialized to zero which forces the scanrate to default to one tenth of a second. Valid values for this signal arefrom 0.1 to 6553.5 seconds. If a value below 0.1 seconds is entered thescan rate will default to 0.1 seconds, and if a value over 6553.5 isentered the scan rate will use 6553.5 seconds. The scan rate has a 0.1second resolution. This signal is checked every four seconds and if ithas changed any pending local alarms are processed and the new scanrate then takes effect. #ALARM.LIM replaces the previous analogsignal #SPARE.002 and it requires ACCOL version 5.6 andAG.00 (or later) level firmware.

If a slow scan rate is chosen, the user should also consider increasingthe number of the Alarm Time Stamp Buffers so that more entries canbe held between processing cycles. If there are not enough Alarm TimeStamp Buffers to hold all the time stamps, alarms are not lost, how-ever the time stamps for alarms which could not be placed in theAlarm Time Stamp Buffers will be flagged as questionable when theyare reported. Memory for additional Alarm Time Stamp Buffers can beallocated on the AIC Communications Configuration Menu or in the*MEMORY section of the ACCOL source file.

#CUSTID.. Type: String (length 64)Initial Status: Firmware initializes after

download with customfirmware version codes.

Inhibit Status: MI, CI

this system signal is only available in Protected Mode firmwareversions PLS04 / PLX04 / PES04 / PEX04 or newer. The string isinitialized by the firmware after download as follows:

CharacterPosition: Description:

00-01 Number of protocols in this Custom firmware (00-99)

System Signals



02-03 Custom firmware version04-05 firmware link date - day (1-31)06-07 firmware link date - month (1-12)08-23 firmware ID (up to 16 ASCII characters)24-27 firmware checksum28-29 number (in Hexadecimal) indicating how many

entries fit in this signal.30-31 MODE value (from Custom Module) for first proto-

col in this firmware (in Hexadecimal)32-33 MODE value (from Custom Module) for second

protocol (if present) in this firmware (in Hexadeci-mal)

: :: :62-63 MODE value (from Custom Module) for 17th proto-

col (if present) in this firmware (in Hexadecimal).NOTE: If there are more than 17 protocols in thisfirmware, only the first 17 will be reported.

#DIAG.001. Type: Logical AlarmInitial Status: OFFInhibit Status: MI, CI, AELogical Alarm Type: Alarm ON

This is an alarm signal for on-line diagnostics. It is turned ON when-ever on-line diagnostics detects a failure related to the locally installedProcess I/O Boards (for Remote I/O on-line diagnostic status, see‘RIOSTATS Module’). Failure information is then stored in a logicaldata array. The number of this array is equal to the value of thesystem signal #DIAG.002.

This signal is also turned ON to indicate a low battery condition forthe RAM backup battery located on the CPU engine board or the DPC3330 256K RAM Expansion board. The battery test is performed once



System Signals

a day at 8:00 a.m. as indicated by the #TIME signals. (NOTE: If yourunit is an older model RDC 3350 or UCS 3380, this test may notapply.)

Beginning with the AF.00 firmware, the definition of local Process I/Ofailures has been extended to include the reporting of missing orincorrect board types at load initialization, “hot card replacement”(3335 only), and power fail recovery. In order to enable this feature theuser must define a larger logical data array (see details under#DIAG.002 'Creating the Data Array (3305/3308/3310/3330/3335)'later in this section).

Beginning with the AF.01 firmware, the reporting of local Process I/Ofailures has been further extended to include a Board Type Code in the#DIAG.002 data array. In order to enable this feature the user mustdefine a larger logical data array (see details under #DIAG.002 'Creat-ing the Data Array (3305/3308/3310/3330/3335)'. When this featureis enabled, it automatically includes the reporting of missing or incor-rect board types as described above. In addition, the following twoactions are enabled:

1) Automatic clearing of the #DIAG.001 alarm signal and theentire data array on “hot card replacement” (3335 only), andpower fail recovery, prior to checking for missing or incorrectboard types.

2) Setting of the error flag associated with the reporting ofmissing or incorrect board types whenever a board fails theon-line diagnostics. This is in addition to the storing of failureinformation in columns 1-8 of the data array and setting the#DIAG.001 alarm signal to on.

Except as noted below, once #DIAG.001 is turned on, it will remain onuntil it is reset by the user either manually or via ACCOL program-ming. Therefore, this signal should first be set to manual and controlenabled.

System Signals



NOTE

When the 3305/3308/3310/3330/3335 feature for reporting missingor incorrect board types is enabled (see above), the #DIAG.001signal will automatically be toggled to OFF, then ON, whenever amissing or incorrect board type is reported during power failrecovery or "hot card replacement." This guarantees the reportingof an alarm for these conditions (e.g. removal of a board) even ifthe #DIAG.001 signal is already on.

#DIAG.002. Type: AnalogInitial Value: 0.0000000Inhibit Status: MI, CI

This signal contains the number of the read/write logical data arraythat will be used to store Process I/O failure information.

Before this information can be collected, a data array number must beassigned and a logical read/write data array created. Assign the dataarray number in the “Initial Value” field of the signal menu for systemsignal #DIAG.002. Create a logical data array in accordance with theinstructions below based on your 33XX unit type. Defining data arraysis explained in detail in the ACCOL II Interactive Compiler Manual(document# D4042) or the ACCOL Workbench User Manual (docu-ment# D4051).

Once a data array element has been turned on to report a failurerelated to local Process I/O, it will remain on until it is reset by theuser, either manually or via ACCOL programming. The only excep-tions to this are:

1) When the reporting of missing or incorrect board types isenabled, Column 9 is either turned on to report an error, orturned off if the correct board type is present in the slot.

2) When the storing of the Board Type Code is enabled, theentire data array is cleared following power fail recovery or“hot card replacement” (3335 only), prior to checking for



System Signals

missing or incorrect board types. Any failures detected duringthis check, or by subsequent execution of the on-line diagnos-tics, will store new failure information in the data array.

Creating the Data Array(RDC 3350, UCS 3380, and CFE 3385 units only)

When creating the data array, make the number of rows equal to thehighest numbered Process I/O board configured in your ACCOL load.Each row will contain failure information for one board. The first rowis assigned to the board in the first card slot and subsequent rows areassigned to the remaining boards in numerical order.

If there are empty card slots between I/O boards, the data array mustcontain a row for the empty slots.

The maximum number of columns required is 96. You may need fewerbased on the types of I/O boards configured in your unit as explainedand illustrated below. Each data array element in the row will be setequal to 1 or 0 depending on the board type and the outcome of thediagnostic test. Some elements correspond to specific input and outputterminal points. Other elements refer to general tests on the boarditself. These are summarized below:

Columns 1 through 32 will collect information for up to 32 digitaloutputs and Columns 33 through 80 will collect information for upto 48 digital inputs. The data array elements in these columnswill be set to 1 when a failure is detected from the internalloopback tests for that digital output or input point.

Columns 81 through 88 are used for analog outputs. These dataarray elements will be set to 1 whenever the corresponding analogoutput fails the DA/DAC or AO/DAC test.

Columns 89 through 92 are used for analog inputs. Unlike theprevious columns where each array element corresponded to aninput or output point on a board, columns 89 through 92 repre-

System Signals



sent the results of diagnostic tests done on the board amplifierlogic. Any failures will set the corresponding data array elementto 1.

Column 89 40:1 amplifier offset failureColumn 90 40:1 amplifier gain failureColumn 91 100:1 amplifier offset failureColumn 92 100:1 amplifier gain failure

Columns 91 through 96 are used for the Low Level AI Board. Thereference voltages are checked and the results of these tests arerecorded in columns 91 through 96 as listed below. Any failureswill set the corresponding data array element to 1. NOTE: Col-umns 91 and 92 are used by both analog inputs and low levelanalog inputs; each board’s information is in its own row of thedata array.

Column 91 - 2.5V (Monitor Input 3)Column 92 - 10 V (Monitor Input 4)Column 93 - 5 V (Monitor Input 5)Column 94 - 0 V (Monitor Input 6)Column 95 - 3 V (Monitor Input 7)Column 96 - 2 V (Monitor Input 8)

Though each row contains 96 elements, not every data array elementwill be used. Suppose that a Digital Board is installed in the first slotof an RDC 3350. Row 1 of the data array will be reserved for thatboard. Since there are 32 digital outputs and 48 digital inputs on thisboard, only columns 1 through 80 will be used in this row. The otherdata array elements will remain unused. This is illustrated below. Thecheck marks indicate the data array element fields which are used foreach board type.

1-32 33-80 81-88 89-92 93-96Digital Board ✓ ✓

Analog Board ✓ ✓

Mixed I/O Board ✓ ✓ ✓ ✓

Low Level AI Board ✓ Col.91-96



System Signals

Creating the Data Array (3305/3308/3310/3330/3335 units)

Creating the data array for these units is a similar procedure to thatdescribed above for the 3350/80/85. The number of rows must be equalto the highest numbered Process I/O Board configured in the ACCOLload for your unit.

The number of columns in the data array enables the following fea-tures:

No. of Columns Description

1 to 8 On-line diagnostic failure information

9 Adds reporting of missing or incorrectboard type on load initialization, powerfail recovery, or “hot card replacement”(3335 only). Requires AF.00 or later firmware (B.01or later for the GFC 3308.)

10 to 16 Includes the Column 9 feature and adds storage ofthe Board Type Code as a binary encoded value inColumns 10-16 (right-justified 7-bit value inmemory).

Also enables clearing of the #DIAG.001 alarm signaland the entire data array on power fail recovery, or“hot card replacement” (3335 only), and setting ofColumn 9 when an on-line diagnostic failure occurs.Requires AF.01 or later firmware (B.01 or later forthe GFC 3308.)

Board type codes, as displayed in columns 10 through 16 of the arrayare shown in the following table:

System Signals



Binary Code Board Type Code Board TypeColumns:10 11 12 13 14 15 16

0 0 0 0 0 0 1 1 Digital Input-4 0 0 0 0 0 1 0 2 Digital Input-8 0 0 0 0 0 1 1 3 Digital Output-4 0 0 0 0 1 0 0 4 Digital Output-8 0 0 0 0 1 0 1 5 Analog Input-4 0 0 0 0 1 1 0 6 Analog Output-2 0 0 0 0 1 1 1 7 High Speed Counter 0 0 0 1 0 0 0 8 Low Level Analog

Input 0 0 0 1 0 0 1 9 High Speed Analog 0 0 0 1 0 1 0 10 HW Smart Transmit-

ter I/F 0 0 0 1 0 1 1 11 Check-Before-Operate 0 0 0 1 1 0 0 12 Bristol

Teletrans I/F board 0 0 0 1 1 0 1 13 Digital Input-6 (3308

only) 0 0 0 1 1 1 0 14 Digital Output-6

(3308 only) 0 0 0 1 1 1 1 15 Analog Input-8 0 0 1 0 0 0 0 16 Analog Output-4 0 0 1 0 0 0 1 17 Digital Input-16 0 0 1 0 0 1 0 18 Digital Output-16 0 0 1 0 0 1 1 19 Digital Input-14

(3305 only) 0 0 1 0 1 0 0 20 Digital Output-8

(3305 only) 0 0 1 0 1 0 1 21 Analog Input-4

(3305 only)

Some board types do not use all positions within the first eight col-umns to report on-line diagnostic failures. For the Digital Input-4 andDigital Input-8 (or Output) Board, columns 1 through 4 correspond todigital input (or output) terminal points 1 through 4. If there are morethan four points on the board, then columns 5 through 8 will corre-



System Signals

spond to terminal points 5 through 8. A 1 (or ON) in a particularcolumn indicates that the corresponding terminal point failed diagnos-tics, for example, a 1 in column 3 for a Digital Input Board means thatDI point number 3 on the board failed diagnostics.

When the row corresponds to a Digital Input-16 Board or a DigitalOutput-16 Board, a 1 (or ON) in columns 1 through 8 indicates thatone or both of a pair of specified terminal points on the board hadfailed diagnostics. For example, if a 1 appears in column 1 for a DigitalInput-16 Board, then either DI point 1 or DI point 9 has failed diag-nostics, or they both have failed. To determine which of the two pointshas failed, further testing is required. This testing is performed byrunning off-line diagnostics using the DIAG program. See the 33XXDiagnostics Manual, document# D4041 for details.

Columns: Status1 2 3 4 5 6 7 8

1 0 0 0 0 0 0 0 Point 1 or Point 9 failure, or both failed0 1 0 0 0 0 0 0 Point 2 or Point 10 failure, or both failed0 0 1 0 0 0 0 0 Point 3 or Point 11 failure, or both failed0 0 0 1 0 0 0 0 Point 4 or Point 12 failure, or both failed0 0 0 0 1 0 0 0 Point 5 or Point 13 failure, or both failed0 0 0 0 0 1 0 0 Point 6 or Point 14 failure, or both failed0 0 0 0 0 0 1 0 Point 7 or Point 15 failure, or both failed0 0 0 0 0 0 0 1 Point 8 or Point 16 failure, or both failed

When the row corresponds to an Analog Input Board, the first columnwill be set to 1 (or ON) when an amplifier offset failure is detected.The second column will be set to 1 upon amplifier gain failure. Theother columns will be zero.

The following board types store encoded patterns in the array to reportspecific failures. Over time, if more than one type of failure occurs thepatterns will be combined.

System Signals



When the row corresponds to a Low Level AI Board, columns 1through 8 may take on the following patterns:


1 0 0 0 0 0 0 0 Board self test active or timeout1 0 0 0 0 0 0 1 Register Failure1 0 0 0 0 0 1 0 EPROM Failure1 0 0 0 0 0 1 1 Internal RAM Failure1 0 0 0 0 1 0 0 External RAM Failure1 0 0 0 0 1 0 1 Zero Ref. Failure1 0 0 0 0 1 1 0 Gain Ref. Failure1 0 0 0 0 1 1 1 Cold Ref. Failure0 1 0 0 1 0 0 0 Input Channel 1 Failure0 1 0 0 0 1 0 0 Input Channel 2 Failure0 1 0 0 0 0 1 0 Input Channel 3 Failure0 1 0 0 0 0 0 1 Input Channel 4 Failure0 0 1 0 0 0 0 0 Calibration Mode Active

When the row corresponds to a High Speed AI Board, columns 1through 8 may take on the following patterns:


1 0 0 0 0 0 0 0 Board self test active or timeout0 1 0 0 0 0 0 0 Register Failure1 1 0 0 0 0 0 0 EPROM Failure0 0 1 0 0 0 0 0 Internal RAM Failure1 0 1 0 0 0 0 0 External RAM Failure0 1 1 0 0 0 0 0 Zero Ref. Failure1 1 1 0 0 0 0 0 Gain Ref. Failure0 0 0 1 0 0 0 0 DAC Failure1 0 0 1 0 0 0 0 Calibration Mode Active



System Signals

When the row corresponds to a Honeywell Smart Transmitter Inter-face Board, columns 1 through 8 may take on the following patterns:


1 0 0 0 0 0 0 0 HWSTI Board Power-Up Failure1 0 0 0 0 0 0 1 DE Processor Init. Failure1 0 0 0 0 0 1 0 DE Processor Reset Failure1 0 0 0 0 0 1 1 DE Processor Timeout Failure0 1 0 0 0 0 0 1 IP PROM Checksum Failure0 1 0 0 0 0 1 0 IP Local RAM Contents Failure0 1 0 0 0 0 1 1 IP Local RAM Address Lines Failure0 1 0 0 0 1 0 0 IP Dual Port RAM Contents Failure0 1 0 0 0 1 0 1 IP Dual Port RAM Address Lines Failure0 1 0 0 0 1 1 0 IP Shared RAM Contents Failure0 1 0 0 0 1 1 1 IP Shared RAM Address Lines Failure

When the row corresponds to a Check-before-Operate (CBO) Board,columns 1 through 3 may take on the following patterns; columns 4through 8 should always be zero.


1 0 0 0 0 0 0 0 Select Error (board select logic does not matchlast select data written)

0 1 0 0 0 0 0 0 Output Error (board feedback logic does notmatch last output data written)

0 0 1 0 0 0 0 0 Board Reset (CBO Module action)

System Signals



When the row corresponds to a Bristol Teletrans Interface (BBTI)board, columns 1 thru 8 may take on the following patterns:


1 0 0 0 0 0 0 0 BBTI Board Power-Up Failure OR MCU(board processor) failed to start, OR unknownfailure

0 0 0 1 0 0 0 0 Dual Port RAM Address Failure0 0 0 0 1 0 0 0 Dual Port RAM Contents Failure0 0 0 0 0 1 0 0 MCU Local RAM Address Failure0 0 0 0 0 0 1 0 MCU Local RAM Contents Failure0 0 0 0 0 0 0 1 MCU PROM Checksum Failure0 1 0 0 0 0 0 1 MCU Halted - task stack pointer = 00 1 0 0 0 0 1 0 MCU Halted - this timer task block already in

chain0 1 0 0 0 1 0 0 MCU Halted - this block already hooked0 1 0 0 1 0 0 0 MCU Halted - attempt to hook a timer block

located at 00 1 0 1 0 0 0 0 MCU Halted - Unknown External Interrupt

The 3310/3330/3335 Analog Output and High Speed Counter (HSC)Boards have no on-line diagnostic capability. Columns 1 through 8 ofcorresponding rows in the data array will therefore remain zeros.Though no on-line diagnostic tests are done on the Analog Output orHigh Speed Counter (HSC) Boards, a row must be reserved in the dataarray for those boards, if they are present in the unit.

#DIAG.003. Type: AnalogInitial Value: 60.0000000 SECSInhibit Status: MI, CI

This signal contains the execution frequency, in seconds, of the on-linediagnostics. The I/O Board positions are processed on a rotating



System Signals

basis, with each pass processing a single board position. For the RDC3350, UCS 3380, and CFE 3385, each correctly configured Process I/OBoard will be tested once every 4 X #DIAG.003 seconds regardless ofthe number of boards installed. For the 3305/3308/3310/3330/3335, thefrequency is 12 times #DIAG.003 seconds.

If this signal is set to 0.0, the on-line process I/O diagnostics will notexecute. However, the RAM battery backup check will be done once aday (in those units where this check applies), regardless of the value ofthis signal.

The 3305/3308/3310/3330/3335 features for reporting of missing orincorrect board types and for storage of board type codes are alsoindependent of the value of this signal. These features execute at loadinitialization, “hot card replacement” (3335 only), and power failrecovery.

When the #DIAG.003 value is changed, it will take up to n seconds forthe change to be recognized, (where n = the previous value of thesignal). If the previous value of the signal was 0.0, it will take up to 10seconds for the change to be recognized.

#DIAL.000. Type: AnalogInitial Value: 0.0000000Inhibit Status: MI,CI

This signal enables the auto dial feature for port A and specifies thelist number to be used for the Standard Dial Control Signal List. If anegative value is entered, the absolute value of the number specifiesthe list number to be used for the Enhanced Slave Dial Control List.If the signal value is 0.0 the auto dial feature is disabled. This featureis not available in the GFC 3308. See the 'Auto-Dial Modem Interface'section for more information.

System Signals



#DIAL.001. Type: AnalogInitial Value: 0.0000000Inhibit Status: MI, CI

This signal enables the auto dial feature for port B and specifies thelist number to be used for the Standard Dial Control Signal List. If anegative value is entered, the absolute value of the number specifiesthe list number to be used for the Enhanced Slave Dial Control List.If the signal value is 0.0 the auto dial feature is disabled. Thisfeature is not available in the GFC 3308. See the 'Auto-Dial ModemInterface' section for more information.


This signal enables the auto dial feature for port C and specifies thelist number to be used for the Standard Dial Control Signal List. If anegative value is entered, the absolute value of the number specifiesthe list number to be used for the Enhanced Slave Dial Control List.If the signal value is 0.0 the auto dial feature is disabled. Whenusing this feature with an internal modem in a GFC 3308, Port Cmust be used. See the 'Auto-Dial Modem Interface' section for moreinformation.


This signal enables the auto dial feature for port D and specifies thelist number to be used for the Standard Dial Control Signal List. If anegative value is entered, the absolute value of the number specifiesthe list number to be used for the Enhanced Slave Dial Control List.If the signal value is 0.0 the auto dial feature is disabled. See the'Auto-Dial Modem Interface' section for more information.



System Signals


This signal enables the auto dial feature for built-in port (BIP) 1 andspecifies the list number to be used for the Standard Dial ControlSignal List. If a negative value is entered, the absolute value of thenumber specifies the list number to be used for the Enhanced SlaveDial Control List. If the signal value is 0.0 the auto dial feature isdisabled. This signal replaces #SPARE.003 and requires ACCOL 5.10(or newer) tools, and RMS00 (or newer) firmware. See the 'Auto-DialModem Interface' section for more information.


This signal enables the auto dial feature for built-in port (BIP) 2 andspecifies the list number to be used for the Standard Dial ControlSignal List. If a negative value is entered, the absolute value of thenumber specifies the list number to be used for the Enhanced SlaveDial Control List. If the signal value is 0.0 the auto dial feature isdisabled. This signal replaces #SPARE.004 and requires ACCOL 5.10(or newer) tools, and RMS00 (or newer) firmware. See the 'Auto-DialModem Interface' section for more information.


This signal enables the auto dial feature for Port G and specifies thelist number to be used for the Standard Dial Control Signal List. If anegative value is entered, the absolute value of the number specifiesthe list number to be used for the Enhanced Slave Dial Control List.If the signal value is 0.0 the auto dial feature is disabled. This signalrequires ACCOL 6.0 (or newer) tools, and PLS00/PLX00 (or newer)

System Signals



firmware. See the 'Auto-Dial Modem Interface' section for moreinformation.


This signal enables the auto dial feature for Port H and specifies thelist number to be used for the Standard Dial Control Signal List. If anegative value is entered, the absolute value of the number specifiesthe list number to be used for the Enhanced Slave Dial Control List.If the signal value is 0.0 the auto dial feature is disabled. This signalrequires ACCOL 6.0 (or newer) tools, and PLS00/PLX00 (or newer)firmware. See the 'Auto-Dial Modem Interface' section for moreinformation.


This signal enables the auto dial feature for Port I and specifies thelist number to be used for the Standard Dial Control Signal List. If anegative value is entered, the absolute value of the number specifiesthe list number to be used for the Enhanced Slave Dial Control List.If the signal value is 0.0 the auto dial feature is disabled. This requiresACCOL 6.0 (or newer) tools, and PLS00/PLX00 (or newer) firmware.See the 'Auto-Dial Modem Interface' section for more information.


This signal enables the auto dial feature for Port J and specifies thelist number to be used for the Standard Dial Control Signal List. If anegative value is entered, the absolute value of the number specifies



System Signals

the list number to be used for the Enhanced Slave Dial Control List.If the signal value is 0.0 the auto dial feature is disabled. This signalrequires ACCOL 6.0 (or newer) tools, and PLS00/PLX00 (or newer)firmware. See the 'Auto-Dial Modem Interface' section for moreinformation.

#DIAL.010 through #DIAL.015

These system signals are reserved for future use.

#E.. Type: AnalogInitial Value: 2.7182817Inhibit Status: MI, CI

This signal is equal to the value of the exponential (e) which is thebase for natural logarithms.

#ERARRAY.. Type: AnalogInitial Value: 0.0000000 (array number)Inhibit Status: MI, CI

This signal contains the number of the read/write analog array used tostore task error information.* This array must have four columns. Thenumber of rows must equal the highest numbered task in the ACCOLload. If the tasks have been numbered in numerical order,the number of rows will equal the number of tasks. If not, you mustremember to create an array where the number of rows equals thehighest numbered task. For example, if you’ve created Tasks 1, 2, 4,and 5, the number of rows must be equal to 5. Since there is no Task3, row 3 will remain unused.

* If you are using ACCOL Workbench (RM) 1.0 or newer orACCOL Workbench (PM) 6.2 or newer, an Error Array Windowis available for viewing the data in the #ERARRAY.

System Signals



Line number which contains errorExpression in error (CalculatorModule only)

Error codeType of moduleor command

Task 1 60 12 4 24

Task 2 34 0 -10 5

Task 3 0 0 0 0(not created)Task 4 5 4 3 24

Task 5 24 5 255 24

Read/Write Array For Error Codes

If multiple errors are being reported for a given task, the array willalways contain the most recent error detected.

A zero in all four columns means there are no errors.

Error Array (#ERARRAY) Contents

Column 1 Line number in errorColumn 2 Expression in error (Calculator Module only; other-

wise always 0)Column 3 Error Status Code:

0 No error1 Floating Point: Not-A-Number or Invalid Opera-

tion3 Array boundary error (Calculator Module)4 Floating Point: Divide by Zero (from NPX hard-

ware in AJ.10 or earlier)



System Signals

Column 3 Error Status Code (continued)8 Floating Point: Overflow (or divide by zero)

10 Watchdog Module time out occurred16 Floating Point: Underflow

255 Fatal Calculator Module error (exits CalculatorModule)

-10 Invalid device (process I/O module)-20 Invalid analog input-30 Invalid analog output-40 Module not supported by PROM set-50 Invalid discrete input-60 Invalid discrete output-70 Invalid counter input-80 Invalid low-level input type-90 Invalid high speed analog input

-100 RIO Module error (see specific module StatusTerminal for detail)

-110 SELECT out of range of list-111 LIST signal references unknown list-112 Selected signal unwired-113 Signal in list is incorrect type-114 User input causes module error (for example,

required signal is missing)-120 Invalid HWSTI/BBTI Module channel number-130 CBO Module error (see status terminal in 'LCBO'

section)

If any of the floating point errors (i.e. error status codes 1,4,8,16) occur during executionof a Calculator Module, the result of the calculation is not stored in the destination signaland the Calculator continues at the next expression. If more than one floating point erroroccurs, the error code will be the sum of the floating point error codes, for example, iffloating point error codes 1 and 8 occur, a 9 will be displayed.

If a floating point error occurs in an :IF statement, the condition will be processed asFALSE, and execution will resume at the statement following the :ENDIF.

System Signals



Column 4 Module and Command Codes:0 ANIN Module 1 ANOUT Module2 Comparator Module 3 (not used)4 DEMUX Module 5 DIGIN Module6 DIGOUT Module 7 Encode Module8 Function Module 9 HSCOUNT Module10 Custom Module 11 Integrator Module12 Lead/Lag Module 13 Logger Module14 LSCOUNT Module 15 Master Module16 Multiplexer Module 17 PID3TERM Module18 (not used) 19 Slave Module20 Audit Trail Module 21 Watchdog Module22 Abort Command 23 Break Command24 Calculator Module 25 Else Command26 Elseif Command 27 Endfor Command28 Endif Command 29 For Command30 Goto Command 31 If Command32 Resume Command 33 Suspend Command34 Wait Time Command 35 Wait Delay Command36 Wait For Command 37 Wait DI Command38 Wait DI High Command 39 Wait DI Low Command40 System Module 41 System0 Module42 AGA3 Module 43 FPV Module44 TOT/TRND Module 45 Averager Module46 Differentiator Module 47 Sequencer Module48 Timer Module 49 CIM Module (Tano)50 Comment Command 51 PDM Module52 AGA5 Module 53 AGA7 Module54 Scheduler Module 55 Command Module56 Stepper Module 57 Storage Module58 CNG Master Module 59 CNG Slave Module60 PDO Module 61 LLANIN Module62 Portstatus Module 63 Keyboard Module64 AGA8 Module 65 Characterize Module66 Redundancy Module 67 HSANIN Module68 RANIN Module 69 RANOUT Module70 RDIGIN Module 71 RDIGOUT Module72 RLLANIN Module 73 RWAITDI Command



System Signals

74 RWAITDI High Command 75 RWAITDI Low Command76 (reserved) 77 RHSCOUNT Module78 RLSCOUNT Module 79 RPDM Module80 RPDO Module 81 RIOSTATS Module82 EMux Module 83 EDemux Module84 Smart Module 85 VMux Module86 VLimiter Module 87 HILOLIMITER Module88 EAudit Module 89 AGAT3 Module90 TCount Module 91 HILOSELECT Module92 EIntegrator Module 93 HWSTI Module94 RBE Module 95 LCBO Module96 NODESTATUS Module 97 EASTATUS Module98 EMASTER Module 99 (reserved)100 HCBO Module 101 AGA8Detail Module102 AGA8Gross Module 103 AGA3Iter Module104 AGA3TERM Module 105 ISO5167 Module106 GBBTI Module 107 LBBTI Module108 TCheck Module 109 Daccumulator Module110 ARC_STORE Module 111 ETOT/TRND Module112 XMTR_Interface Module 113 SYS_3530 Module114 Internet_Protocol Module 115 AGA3Dens Module116 IPClient Module 117 IPServer Module118 Liquid_Density Module 119 GPA8173 Module120 EVP Module 121 GSV Module122 AAT Module

#ERRCT.000. Type: Analog AlarmInitial Value: 0.0000000 ERRORSInhibit Status: MI, CI, AEHigh Limit Alarm: #ERRCT.LIM. Critical.

This signal is unused, and is unavailable in ACCOL 5.12 (and newer).

System Signals



#ERRCT.nnn. Type: Analog AlarmInitial Value: 0.0000000 ERRORSInhibit Status: MI, CI, AEHigh Limit Alarm: #ERRCT.LIM. Critical

This signal represents the error counter for the rate task numberidentified in the extension (nnn). The error counter is incrementedwhenever an error is detected. Error information will be stored in theappropriate row of the analog array pointed to by signal #ERARRAY,if the array is defined by the user.

This signal should be manually reset once the errors have been cor-rected.

#ERRCT.LIM. Type: AnalogInitial Value: 0.0000000 ERRORSInhibit Status: MI, CI

This signal is the high alarm limit for the error counter alarm signals.

#FRMWRID.. Type: String (length 64)Initial Status: Firmware initializes after

download with versioncodes.

Inhibit Status: MI, CI

this system signal is only available in Protected Mode firmwareversions PLS04 / PLX04 / PES04 / PEX04 or newer. The string isinitialized by the firmware after download as follows:

CharacterPosition: Description:

00-03 MSD Version number04-07 PEI Version number (in general MSD and PEI are

identical. If they are not, it indicates an on-line edithas been made, or the file is corrupt.)



System Signals

08-09 Runtime system version number 110-11 Runtime system version number 2 (Firmware ID

load/firmware coordination value. Must matchversion number 1.)

12-13 List version number (used by network monitor)14-15 AIC version number (version of ACCOL Tools)16-17 Features identifier (coordination value for ACCOL

Tools and/or firmware.)18-19 Firmware link date day (01-31)20-21 Firmware link date month (01-12)22-24 Product designation (Pxx).25-26 Major revision aa27-28 Update revision bb29-30 Beta revision cc31-40 Currently unused (spaces)41-42 Boot PROM version link date day (01-31)43-44 Boot PROM version link date month (01-12)45-47 Boot PROM product designation (Pxx).48-49 Boot PROM Major revision aa50-51 Boot PROM Update revision bb52-53 Boot PROM Beta revision cc54-62 Currently unused (spaces)63 Flag for whether this ACCOL load expects a math

co-processor (NPX) to be present in the hardware. A'1' indicates an NPX load; a '0' indicates that this isnot an NPX load.

#IPSTAT.. Type: AnalogInitial Value: 0.0000000Inhibit Status: MI, CI

This signal reports error and status information for the InternetProtocol (IP) system task. It requires PLS03/PLX03/PES03/PEX03 ornewer firmware.

The following are valid error codes:

0 IP communication system startup was successful

System Signals



-1 Memory error during port processing (fatal error)-2 Memory error setting packets and pool (fatal

error)-3 Run-time memory pool too small.-4 Error allocating alarm pools.-5 Could not initialize IP Task message exchange.-6 Error allocating RBE structures-7 Error allocating IP Client structures-8 Error allocating IP Server structures

-101 Invalid protocol (Port A)-102 Invalid protocol (Port B)-103 Invalid protocol (Port C)-104 Invalid protocol (Port D)-105 Invalid protocol (BIP 1)-106 Invalid protocol (BIP 2)-107 Invalid protocol (Port G)-108 Invalid protocol (Port H)-109 Invalid protocol (Port I)-110 Invalid protocol (Port J)-111 Invalid protocol (Reserved for future use)-112 Invalid protocol (Reserved for future use)-113 Invalid protocol (Reserved for future use)-114 Invalid protocol (Reserved for future use)-115 Invalid protocol (Reserved for future use)-116 Invalid protocol (Reserved for future use)-126 Invalid protocol (Port A)-127 Invalid protocol (Port B)-128 Invalid protocol (Port C)-129 Invalid protocol (Port D)-130 Invalid protocol (BIP 1)-131 Invalid protocol (BIP 2)-132 Invalid protocol (Port G)-133 Invalid protocol (Port H)-134 Invalid protocol (Port I)-135 Invalid protocol (Port J)-136 Invalid protocol (Reserved for future use)-137 Invalid protocol (Reserved for future use)-138 Invalid protocol (Reserved for future use)-139 Invalid protocol (Reserved for future use)



System Signals

-140 Invalid protocol (Reserved for future use)-141 Invalid protocol (Reserved for future use)-150 Error installing default gateway-151 Non-fatal memory allocation error

#LINE.nnn. Type: Logical AlarmInitial Status: OFFInhibit Status: MI, CI, AELogical Alarm Type: Alarm ONAlarm Priority: Critical

These signals indicate a communications line failure for one of thecommunication ports. Not all controllers support all ports. The signalsin this group are identified as follows:

#LINE.000 Port A #LINE.006 Port G#LINE.001 Port B #LINE.007 Port H#LINE.002 Port C #LINE.008 Port I#LINE.003 Port D #LINE.009 Port J#LINE.004 Aux 1 / BIP 1 #LINE.010 to #LINE.014 reserved#LINE.005 Aux 2 / BIP 2 #LINE.015 Ethernet

For BSAP Master and Expanded Addressing Master ports, the signalis turned ON when all nodes on the line are classified as dead and thesignal is turned OFF when at least one node is alive. For ExpandedAddressing Master ports the signal is also turned ON if the requiredEASTATUS Module for the port is not present, or if the required On-line/Off-line Array is not assigned on the module's NODE_ARRAYterminal.

For BSAP Slave and Pseudoslave ports, the signal is turned ON if nopoll or data messages are received within the time indicated by the#POLLPER signal associated with that port and the signal is turnedOFF when poll or data messages are received.

For IP (Internet Protocol) Ports, the #LINE signal is turned ON ifthere is no communication traffic of any kind received within the timeindicated by the #POLLPER signal associated with this port.* NOTE:IP is NOT YET SUPPORTED FOR SERIAL PORTS.

*For IP Ports: If one half of the #POLLPER interval has passed with no traffic received, the node will attempt to contact Network Host PC (NHPs).

System Signals



#LINKE.001. Type: Analog AlarmInitial Value: 0.0000000 ERRORSInhibit Status: MI, CI, AEHigh Limit Alarm: LINKE.LIM. Critical

This signal is available for collecting LINK1 error statistics for a dualredundant high-speed highway connected to Aux Port 1, or a 3330/3335 RASCL port connected to Port B. In this application, thePortstatus Module must be configured in the following manner.#LINKE.001 must be specified in position 15 of the signal list refer-enced by the LIST terminal of the Portstatus Module. The Port termi-nal of the Portstatus Module must be set to 5 for Aux Port 1, or 2 forPort B. Instructions for properly setting the other terminals on thismodule can be found under 'Portstatus' in this manual.

Statistics will be collected at the task rate. #LINKE.001 is reset whenthe Portstatus Module mode is 4.

Before this signal will collect statistics, it must be set to control enable.

#LINKE.002. Type: Analog AlarmInitial Value: 0.0000000 ERRORSInhibit Status: MI, CI, AEHigh Limit Alarm: LINKE.LIM. Critical

This signal is available for collecting LINK2 error statistics for a dualredundant high-speed highway connected to Aux Port 1, or a 3330/3335 RASCL port connected to Port B. In this application, thePortstatus Module must be configured in the following manner.

#LINKE.002 must be specified in position 16 of the signal list refer-enced by the LIST terminal of the Portstatus Module. The Port termi-nal of the Portstatus Module must be set to 5 for Aux Port 1, or2 for Port B. See 'Portstatus' for instructions on properly setting thismodule.



System Signals

Statistics will be collected at the task rate. #LINKE.002 is reset whenthe Portstatus Module mode is 4.


#LINKE.LIM. Type: AnalogInitial Value: 20.0000000 ERRORSInhibit Status: MI, CI

This is the alarm limit for the Aux 1 highway or Port B RASCL linkerror count.

#LINKF.001. Type: Analog AlarmInitial Value: 0.0000000 ERRORSInhibit Status: MI, CI, AEHigh Limit Alarm: #LINKF.LIM. Critical

This signal is similar to #LINKE.001 described above. However, withthis system signal, the high-speed data highway is connected to AuxPort 2, or the RASCL port is connected to Port D. The Port terminal onthe Portstatus Module must be set to 6 for Aux Port 2, or 4 for Port D.


#LINKF.002. Type: Analog AlarmInitial Value: 0.0000000 ERRORSInhibit Status: MI, CI, AEHigh Limit Alarm: #LINKF.LIM. Critical

This signal is similar to #LINKE.002 described above. However, withthis system signal, the high-speed data highway is connected to AuxPort 2, or the RASCL port is connected to Port D.

System Signals



The Port terminal on the Portstatus Module must be set to 6 for AuxPort 2, or 4 for Port D.


#LINKF.LIM. Type: AnalogInitial Value: 20.0000000 ERRORSInhibit Status: MI, CI

This signal is the alarm limit for the Aux 2 highway or Port D RASCLlink error count.

#LOAD.. Type: StringInitial Value: Date and time of ACO file

generationInhibit Status: MI, CI

This signal contains an ASCII string that indicates the date and timethe ACO file was generated as well as the file name and versionnumber.* The signal is updated each time the ACO file is linked oredited in a way that invalidates the previous ACL file.

#NDARRAY.. Type: AnalogInitial Value: 0.0000000 (array number)Inhibit Status: MI, CI

This signal identifies the logical node array used to control the On-line/Off-line status of slave nodes configured on the master port(s). Foran Expanded Addressing Master port it controls the status of thevirtual nodes configured on that port. No messages, including pollmessages are transmitted to an Off-line node. In the case of an Off-linevirtual node, no messages are transmitted to any of the slave nodesconfigured below the virtual node.

*The file name was not included in this string, prior toACCOL Version 5.12.



System Signals

Master Poll ControlSignal List Entry

Type ofsignal

ValidRange ofvalues

Purpose

NODE ARRAY Analog 1 to 255Specifies the node polling array number (normallydone via a positive value on #NDARRAY..)

SET SIZE Analog 1 to 7Specifies the number of configuration signals in aset for each Master / EAMaster Port.

RESPONSE TIMEOUT Analog

1 to65,535milliseco-nds

Specifies the amount of time this Master/EAMasterPort will wait for a given Slave node to begintransmission of a response to a poll message. Ifvalid, this disables the standard response timeoutdefined for the Master Port.

POLL MSG ATTEMPTS Analog1 to 255(Default:1)

Specifies the number of times the Master/EAMasterPort will attempt to send a poll message.

DATA MSG ATTEMPTS Analog1 to 255(Default:1)

Specifies the number of times the Master/EAMasterPort will attempt to send a data message.

IDLE POLL ENABLE LogicalON orOFF

When ON, forces the Master/EAMaster Port toperform additional polling after normal pollingactivity is completed. This is useful if Slave NodeDial into the Master. Requires DIAL_UP_ACK tobe active in the Slave (see 'Auto-Dial ModemInterface' section.)

DATA CARRIERDETECT ENABLE

LogicalON orOFF

when ON, prevents the Master/EAMaster Port fromsending poll messages until the modem's carrierdetect is ON.

RASCL LINKAnalogorLogical

Analog:1 or 2Logical:ON orOFF

For RASCL users only: Indicates which RASCLLink (1 or 2) is active. For logical signals,OFF=Link1, ON=Link2; For Analog signals,1=Link1, 2=Link2.

RASCL SELECT Analog

1,2 (anyothervalueallowsautomaticRASCLcontrol)

For RASCL users only: Specifies manual selectionof RASCL link. 1 selects Link1; 2 selects Link2.Any other value allows automatic selection of linkby the system. After each task execution, this willrevert to automatic selection (0). IF LINK IS TO BEMAINTAINED IN MANUAL MODE, SIGNALMUST BE CONTROL-INHIBITED.

System Signals



The array should have an element for each possible slave or virtualnode (maximum of 127). If a single dimension array is used (1 columnx No. of Node rows), then each row position corresponds to the nodehaving that local address. If the element for a slave node is ON, thenode is On-line and will be polled; if the element of the virtual node isON, the On-line/Off-line status of individual slave nodes associatedwith it will determine message activity (see 'EAStatus' earlier in thismanual). If the element for a slave node is OFF, the node is Off-lineand will not be polled; if the element for a virtual node is OFF, allindividual slave nodes associated with it will be Off-line. If this signaldoes not specify a valid array, all slave and/or virtual nodes areconsidered to be On-line.

Configuring Advanced Polling Parameters (RMS04, LS501,PLS03/PLX03/PES03/PEX03

or newer ONLY, or AM.20 with ACCOL Workbench 8.3 or newer)

Certain advanced polling parameters available for Master/EAMasterPorts are accessible by assigning a negative value to the #NDARRAYsignal.

In that case, the absolute value of this signal value specifies a signallist (called the Master Poll Control Signal List). For example, if ' -8 ' isentered for the value of #NDARRAY, then signal list 8 will be used.

The set of configuration signals for each port in this list is examined bythe system during each task execution, therefore dyamic changes arepossible. The configuration signals are: RESPONSE TIMEOUT, POLLMSG ATTEMPTS, DATA MSG ATTEMPTS, IDLE POLL ENABLE,DATA CARRIER DETECT ENABLE, RASCL LINK, and RASCLSELECT.

The entries in the Master Poll Control Signal List must appear in theorder shown in the table on the previous page. The choice of signalnames is that of the user. For more details on this subject, see theNetwork 3000 Communications Configuration Guide (document#D5080).



System Signals

#NODE.nnn. Type: Logical alarmInitial Value: OFFInhibit Status: MI, CI, AELogical Alarm Type: Alarm OnAlarm Priority: Critical

These signals are used to indicate communication failures for indi-vidual nodes configured on the master port(s). These signals areautomatically generated based on the maximum value specified in theHigh Slave Address field for master-type port(s). The extension, nnn,corresponds to the number of the node (001-127). The #NODE.nnnsignal for a slave node on a Master port is turned ON when the node isclassified as Dead (after 3 consecutive timeouts). It is turned OFFwhenever the node responds (i.e. the node is Alive). The #NODE.nnnsignal for a virtual node on an Expanded Addressing Master Port isturned ON when any node associated with the virtual node is classi-fied as Dead, i.e. it indicates that one or more of the slave nodes inthat group is Dead. It is turned OFF whenever any previously Deadnode responds (i.e. a node goes from Dead to Alive) and all other On-line nodes in the same group are also alive.

#NODEADR.. Type: AnalogInitial Value: 0.0000000Inhibit Status: MI, CI

This signal is automatically set to the node's local network address asset via the node address hardware switches. This signal is not includedin ACCOL versions prior to 5.0.

#NRT.INH. Type: LogicalInitial Value: OFFInhibit Status: MI, CE

when ON, this signal causes the 33xx controller to discard the date/time portion of any incoming time synch messages, as well as any timechange requests from the 3330 Keypad, Encode Module, or EnronModbus device. The node routing table portion of the message IS acted

System Signals



upon, however. This signal is not included in ACCOL versions prior to5.12, and firmware versions AL.00 / RMS02.

#NRT.REQ. Type: LogicalInitial Value: OFFInhibit Status: MI, CE

when ON, this signal requests a time synch message through the 33xxcontroller's slave port. Receipt of the time synch message will auto-matically turn this signal OFF. This signal is not included in ACCOLversions prior to 5.12.

#OCTIME.. Type: Logical AlarmInitial State: OFFInhibit Status: MI, CI, AELogical Alarm Type: Alarm OnAlarm Priority: Critical

This signal is unused, and is unavailable in ACCOL 5.12 (and newer).

#OCTIME.ERROR. Type: Logical AlarmInitial State: OFFInhibit Status: MI, CI, AELogical Alarm Type: Alarm OnAlarm Priority: Critical

Operator's Console Error signal. This signal indicates when the timereceived from the master node differs from local time by more thanfour seconds.

#OFF.. Type: LogicalInitial State: OFFInhibit Status: MI, CI

This signal is used to indicate a logical off.



System Signals

#ON.. Type: LogicalInitial State: ONInhibit Status: MI, CI

This signal is used to indicate a logical on.

#ONLBAT.. Type: LogicalInitial State: OFFInhibit Status: MI, CI

When ON, the online RAM backup battery diagnostics will not be runand the #DIAG.001 system signal will not be updated to report thebattery status. Warning: Turning this signal ON will eliminate anywarning of RAM battery power loss, thereby risking loss of all RAMdata and a cold start on power-up. Requires PLS04.40 or newerfirmware.

#PDM.000. Type: AnalogInitial Value: 0.0000000Inhibit Status: ME, CI

This signal is a Pulse Duration Module parameter that indicates thedevice selected for calibration. The value is the same as would bespecified for the PDM or RPDM Modules.

#PDM.001. Type: AnalogInitial Value: 0.0000000Inhibit Status: ME, CI

This signal is a Pulse Duration Module parameter that indicates theselected input for calibration.

System Signals



#PDM.002. Type: LogicalInitial State: OFFInhibit Status: ME, CI

This signal is a Pulse Duration Module parameter to indicate thatcalibration is “enabled.”

#PDM.003. Type: LogicalInitial State: OFFInhibit Status: MI, CE

This signal is a Pulse Duration Module parameter that indicates thecurrent state of the discrete input.

#PDM.004. Type: AnalogInitial Value: 0.0000000Inhibit Status: MI, CE

This signal is a Pulse Duration Module parameter that indicates theprevious “on” time in seconds.


This signal is a Pulse Duration Module parameter that indicates theprevious “off” time in seconds.


This signal is a Pulse Duration Module parameter that indicates theprevious period in seconds.



System Signals


This signal is a Pulse Duration Module parameter that indicates theunfiltered percent of full scale.


This signal is a Pulse Duration Module parameter that indicates theunfiltered value in engineering units.

#PI.. Type: AnalogInitial Value: 3.1415927Inhibit Status: MI, CI

This signal is included for the user’s convenience. It contains the valueof “pi” which is the ratio between the circumference and diameter of acircle.

#POLLPER.nnn. Type: AnalogInitial Value: 20.0000000 SECSInhibit Status: MI, CI

These signals are associated with the communication ports. Theextension appended to this signal corresponds to the associated port asfollows:

.000 = Port A .005 = Aux 2 / BIP 2

.001 = Port B .006 = Port G

.002 = Port C .007 = Port H

.003 = Port D .008 = Port I

.004 = Aux 1 / BIP 1 .009 = Port J

.010 through .014 reserved for future use

.015 = Ethernet

System Signals



Poll Period for Master/Expanded Addressing Master Ports:

When a port is configured as a Master or Expanded Addressing Masterport this signal determines the frequency at which an individual slavenode on the port will be polled, assuming sufficient time is provided tocomplete all required polling activities during each cycle (poll eachAlive node once, and n Dead nodes, where n=1 for a standard Masterport and n=No. of virtual nodes for an Expanded Addressing Masterport).

The minimum poll period value is 0.1 seconds. The resolution is inhundredths of a second (0.15, for example). Residual fractional valuesbeyond the hundredths place are truncated. Values entered that aresmaller then 0.1 seconds (but not 0) will be treated as 0.1 seconds. Avalue of 0 turns off polling.If the poll period defines a frequency which cannot be attained i.e. itspecifies 0.1 seconds, but it takes 0.5 seconds on average to completethe required polling activities on the port, activity on the port will becontinuous and no Preferred Polling will occur. If the poll period isgreater than the time to complete required polling activities, the extratime between poll periods is used for Preferred Polling of nodes whichpreviously responded with data (and for an Expanded AddressingMaster port, of nodes which were previously sent a data request), andfor polling of Dead nodes, if any (see the Network 3000 Communica-tions Application Programmer's Reference, document# D4052, for moredetails).

Poll Period for Slave/Pseudo-slave Ports:

When a port is configured as a Slave or Pseudo-slave, all messagesawaiting transmission (except alarms) are discarded if no polls arereceived within the given period (i.e. this period is used to determinewhen the line has failed). It’s recommended that you set#POLLPER.nnn to approximately three poll periods of the associatedmaster. The minimum poll period value for a slave/pseudo-slave portis 0.1 seconds. Note that the smaller the number on the #POLLPERterminal, the shorter the poll period will be, therefore the slave isexpecting to be polled at a faster rate. The resolution is in hundredthsof a second (0.15, for example). Residual fractional values beyond the



System Signals

b

hundredths place are truncated. Values entered that are smaller than0.1 seconds, but not 0, will be treated as 0.1 seconds. A value of 0disables the timeout mechanism and should not be used.

Poll Period for RIOR Ports:

RIOR ports automatically poll for all data from every Remote I/O Rack(RIOR) on the port once every second. This automatic data request iscalled the heartbeat, and it operates independently of the#POLLPER.nnn signal. If the one second rate is adequate for yourneeds, just set the #POLLPER.nnn signal to 1 second.

Additional (more frequent) polling for a particular Remote I/O Rackmay be activated based on the #POLLPER.nnn signal when (1) youput an RWAIT DI (DIH, DIL) statement anywhere in the ACCOLload, which references that RIOR, or when (2) a remote input module(RANIN, RDIGIN, RLLANIN, RLSCOUNT, RHSCOUNT, or RPDM)referencing that RIOR is currently executing. Depending upon whethercase (1) or (2) exists, the #POLLPER.nnn signal has a different effect.

(seconds)0.0 1.0 2.00.5 1.5

heartbeat heartbeat heartbeatpoll poll poll

Once per second heartbeat poll

Case 1 - If your load contains an RWAIT DI (DIH, DIL) statement inany task, #POLLPER.nnn indicates how often the 3310/3330/3335requests data from the Remote I/O Rack which contains thatparticular DI. The poll period can be set as fast as 0.02 seconds(which is the recommended speed). This means that every 0.02seconds (20 milliseconds) the RIOR port will poll for all data fromthat Remote I/O Rack.*

* Other RIO 3331 Remote I/O Racks on the RIOR portwhich do not have a DI board referenced by an RWAITDI statement will only be polled as described in case 2.

System Signals



This polling is in addition to the once per second heartbeat, whichstill occurs in that node. If you enter a faster poll period than 0.02seconds it will be treated as if you chose 0.02 seconds. If you entera poll period which is greater than 1 second, the poll period willdefault to the heartbeat rate of 1 second. The figure, below, showsa 0.2 second poll period for an RWAIT DI statement.

Case 2 - If your load is currently executing a remote input module,(RANIN, RDIGIN, RHSCOUNT, RLSCOUNT, RLLANIN, RPDM)the #POLLPER.nnn signal indicates the maximum data age. Inother words, when a remote input module executes, it will only pollits associated Remote I/O Rack if the data from the last time itpolled is older than the maximum data age specified on#POLLPER.nnn. If it is, the current data in memory is discarded,and a new data request is made.

(seconds)0.0 1.0 2.00.5 1.5

heartbeat heartbeat heartbeat

indicates a poll is occurring at this point in time.

Note: For illustration purposes, we show the poll for the RWAIT DIto be

periodseconds. The recommended poll period for an RWAIT DI

is 10 times faster than that -- 20 milliseconds (0.02 seconds).

At 0.0, 1.0, and 2.0 seconds, the heartbeat poll occurs. This is

0.2

Note:

indicates the heartbeat poll is occurring at this point in time.

poll poll poll

equivalent to the other polls, the only distinction is that it occursonce per second.

0.2 second poll period with RWAIT DI in load

If, for example, a RANIN Module executes and the data collectedduring the last communication with the Remote I/O Rack itreferences is older than the time specified by #POLLPER.nnn, the



System Signals

existing data is discarded and a new request for all data from thatRIOR occurs. Polling for that RIOR then continues at the heart-beat rate, only, until another remote process I/O module executesand references boards in that RIOR.

If, instead, a RANIN Module is executing and the data collectedduring the last heartbeat or remote input module execution is notolder than the time specified by #POLLPER.nnn, a data requestwill not be made because the current data in memory is stillconsidered fresh.

Note that you can set the data age to be as low as 0.02 seconds(20 milliseconds.) If you enter a value smaller than that, it will betreated as if you entered 0.02 seconds. If you enter a data agewhich is greater than 1 second, it will default to the 1 secondheartbeat. It’s recommended that you set the data age to be aslow as possible (0.02 seconds) unless that value causes task rateslippage. If slippage occurs, it may be necessary to increase thedata age.

The next figure shows cases where data requests are, and are notmade, based on data age. The poll period shown in the figure is0.3 seconds. Since there are no RWAIT DI’s in the ACCOL load,this means that when a remote input module executes (RANIN,RDIGIN, etc.) the Remote I/O Rack that it references will bepolled only if its data is older than 0.3 seconds.

System Signals



(seconds)0.0 1.0 2.00.5 1.5

heartbeat heartbeat heartbeatRANIN m

odule ex

ecutes

RDIGIN

mod

ule ex

ecutes

RANIN m

odule ex

ecutes

RDIGIN

mod

ule ex

ecutes

poll

poll period is 0.3 secs.0.7 is greater than 0.3so have to poll here.

RDIGIN

mod

ule ex

ecutes

(no po

ll nec

essa

ry)

(no po

ll nec

essa

ry)

0.5 is greater than0.3, so have to poll

poll

(no po

ll nec

essa

ry)

poll poll poll

The RANIN Module in the figure executing at 0.25 seconds intothe timeline doesn’t require a poll because it hasn’t been morethan 0.3 seconds since the last poll (which was the heartbeat.) TheRDIGIN Module at 0.7 seconds into the timeline does require apoll because it has been more than 0.3 seconds since the last poll.The RDIGIN Module executing at 1.15 seconds into the timelineneeds no poll because it has only been 0.15 seconds since the lastpoll (which was the heartbeat.) The RANIN Module executing at1.5 seconds into the timeline requires a poll because the last pollwas 0.5 seconds before (which is greater than 0.3) so the data istoo old. The RDIGIN Module executing at 1.75 seconds into thetimeline does not require a poll because a poll occurred 0.25seconds before (for the RANIN Module at 1.5 seconds on thetimeline) so data is still younger than 0.3 seconds.

Note: When both case 1 and case 2 occur for a particular RIOR, itsdata is always fresh because of the constant polling of the RWAIT DI.

0.3 second poll period (data age)



System Signals

RIOR Application Note:

For maximum RIOR polling efficiency, it is recommended that all RIOinput modules referencing a particular remote I/O rack be groupedtogether at the beginning of a single ACCOL task, and any other codethat references them should appear later on in that task. This ar-rangement optimizes RIOR efficiency because a single RIO poll fordata elicits a response with all RIO data for the remote I/O rack. Whenthe RIO modules are grouped together, this gives the best chance of allRIO requests being satisfied through a single poll for the first RIOinput module, whereas spreading the input modules throughout thetask could require multiple requests if the data age is exceeded.

IP (Internet Protocol Ports): (PES03/PEX03 or newer firmware only)

For serial IP ports, or the Ethernet port, the #POLLPER signalindicates a timeout period after which the IP line is considered 'dead'.If one half of the timeout period has expired, with no traffic receivedon the line, the IP controller will attempt to communicate with Net-work Host PCs (NHPs).

Using Advanced Poll Period Parameters: (RMS04, LS501, PLS03/PLX03/PES03/PEX03 or

newer ONLY, or AM.20 with ACCOL Workbench 8.3 or newer.)

Certain advanced poll period parameters are available by assigning anegative value to the #POLLPER.nnn. signal. In that case, the abso-lute value of the signal's value specifies a signal list. For example, if ' -47 ' is entered for the value of #POLLPER, then signal list 47 will beused. The entries in this signal list are examined by the system duringeach task execution, therefore dyamic changes are possible.

The table, below, shows the required order of entries in the signal list.The choice of signal names is entirely that of the user. For moredetails on this subject, see the Network 3000 Communications Con-figuration Guide (document# D5080).

System Signals



#PRI.nnn. Type: AnalogInitial Value: Priority 1.0Inhibit Status: MI, CI

Identifies the priority of a task indicated by the extension nnn.

#PWRUP.000. Type: Logical AlarmInitial State: OFFInhibit Status: MI, CI, AELogical Alarm Type: Alarm ONAlarm Priority: Critical

This signal is turned ON following a power recovery or download. Theuser’s ACCOL configuration should turn this signal OFF if notice ofsubsequent power recoveries is desired.

Signal ListEntry

Type ofSignal

ValidRange ofValues

Purpose

POLLPERIOD

AnalogMinimumof 0.1seconds

To set the appropriate poll period forthis Master/EAMaster or Slave Port.Normally, this would be done directlyvia the #POLLPER.nnn signal.

386 DELAYTIME

Analog0 to65.535seconds

Specifies a delay time to allow a386EX-based controller to compensatefor message turn-around time in a 186-based controller. May be used in a386EX Master node (with a 186 Slave)or a 386EX Slave node (with a 186Master).

IMMEDIATERESPONSEDELAY

Analog0 to 2.55seconds

Used on Slave Ports ONLY. Thisspecifies a delay time during which theSlave Port will wait before respondingto a request for data from its master.



System Signals

#PWRUP.001. Type: AnalogInitial Value: 0.0000000Inhibits: MI, CI

This signal will be set after a warm start (power fail recovery) toindicate how long the unit was powered down, in seconds. Themaximum time which can be measured is 65,535 seconds or 18hours, 12 minutes, 15 seconds.

This signal will be set to 0 after a cold start, new download, orredundant switchover.

#PWRUP.001 replaces the previous logical #SPARE.001. It requiresACCOL version 5.5 and AF.00 (or later) level firmware (B.01 or laterfor the GFC 3308.)

Beginning with AG.00 firmware (B.01 for the 3308) a negative valueon this signal (-65,535 or -6.5535E+4) will be used to indicate that theinternal battery in the Real Time Clock chip* has failed and thereforethe system date and time (#TIME.nnn signals) immediately followinga warm start (power fail recovery) are questionable. For this case thesystem date and time will retain the values in place before power waslost.

NOTE: For a unit with a BSAP Slave port, the system date and timewill be corrected when a Time Sync/NRT message is received. The unitrequests a Time Sync/NRT after a warm start.

#RATE.nnn. Type: AnalogInitial Value: 0.0000000Inhibit Status: MI, CI

is the task rate (in seconds) of Task nnn.

* Applicable to units using the Dallas Semiconductor DS1287 RTC. As of thiswriting this includes the RTU 3305, GFC 3308, RTU 3310, and the latest hardwarefor the DPC 3330/35 and RIO 3331. Failure of the RTC battery is also reported byselftest and Off-line Diagnostics (requires 5.6 (or later) DIAG on the PEI).

System Signals



#RCNT.nnn. Type: Analog AlarmInitial Value: 0.0000000 countsInhibit Status: MI, CI, AELow limit = EventLow low limit = EventHigh limit = Critical (#RCNT.LIM)High High Limit = Event

This signal is a slippage counter for the task number indicated in theextension. It is incremented by 1 every time the task execution is late.It should be manually reset once slippages have been corrected.

#RCNT.LIM. Type: AnalogInitial Value 20.0000000 COUNTSInhibit Status: MI, CI

This signal functions as a task slip counter alarm limit.

#RDB.MODE. Type: LogicalInitial Value OFF (186 or 386EX Real mode)

ON (386EX Protected Mode)

Inhibit Status: MI, CI (186 or 386EX Real mode)

ME,CE (386EX Protected Mode)

when OFF, no new incoming requests for data will be processed,unless transmission of outgoing responses for previous messages havebeen completed. When ON, incoming request processing occurs inde-pendently of outgoing transmissions. This signal is NOT availableprior to ACCOL 5.12 tools. NOTE: If you are NOT using protectedmode firmware (PLS00/PLX00 or newer) the #RDB.MODE. signalshould generally NOT be left ON continuously, because under heavycommunication traffic, it could potentially prevent lower priority tasksfrom executing.



System Signals

#RDN..

A series of system signals with the basename #RDN are created whenthe ACCOL load is defined as a redundant load. These signals aredescribed in complete detail under 'Redundancy Module'.

#RDNERR.. Type: Analog AlarmInitial Value: 0.0000000Inhibit Status: MI, CI, AEHigh Limit Alarm: #RDNLIM.. Critical

This signal exists only in ACCOL version 4.2 or earlier.

#RDNLIM.. Type: AnalogInitial Value: 10.0000000Inhibits: MI, CI

This signal exists only in ACCOL version 4.2 or earlier.

#RTTIME.000. Type: AnalogInitial Value: 0.0000000Inhibit Status: ME, CI

The value entered for this signal is used to select a rate timing modewhose measurement is the value of signal RTTIME.001.

If the value of this signal (RTTIME.000.) is zero, the timing option isnot active. If the value of this signal is positive, the execution time ofthe corresponding ACCOL rate task is measured.If the entered value is a negative number, the total system idle time ismeasured. The absolute value is taken as the period over which themeasurement is to take place, in seconds. For example, a -50 entryindicates that a 50-second period will be used. This period specificationmust range from 1 to 255 seconds. It is recommended that a period ofsufficient length be selected to allow all of the tasks to run severaltimes; this will provide a better estimate of the idle time.

System Signals



#RTTIME.001. Type: AnalogInitial Value: 0.0000000Inhibit Status: MI, CI

The value of this signal is a function of the mode selection enteredunder signal #RTTIME.000. As such, signal #RTTIME.001 mayindicate the execution time of one task, or the idle time of the entiresystem.

For the task timing case, the value of this signal represents theelapsed time required to execute the task. If higher priority tasks arerunning during the timing of a specific task, erroneous values will bedisplayed for this signal. To obtain correct results, the higher prioritytasks should be turned off.

For the idle time case, this signal value represents the time, in sec-onds, that the processor is idle; i.e. no tasks are active and no othersystem activities are active. For example, if the #RTTIME.000 signalis set to -50 (seconds) and the value of the #RTTIME.001 signal is 30(seconds), the processor is considered 40% loaded by the tasks in thesystem. The processor load can be computed by the following equation:

- #RTTIME.000 - #RTTIME.001= 100

- #RTTIME.000

% ofprocessor load



System Signals

* For information on decoding the packed Julian format, see 'Encode'.

#TIME.nnn. Type: Analog SignalsInitial Value: 0.0000000Inhibit Status: MI, CI

A group of nine signals are used to carry date and time information.

These signals have the following names and functions:

#TIME.000 A packed format, Julian, date and time signal.*

#TIME.001. The value indicates the seconds from midnight.#TIME.002. The value indicates the year.#TIME.003. The value indicates the month.#TIME.004. The value indicates the day.#TIME.005. The value indicates the hour.#TIME.006. The value indicates the minute.#TIME.007. The value indicates the second.#TIME.008. This value is the number of Julian days since 12:00

midnight on Friday, December 31, 1976. On Satur-day, January 1, 1977, for example, #TIME.008.would be 1. This signal requires ACCOL Version 5.12(or newer).

Note: For units using AG.00 firmware (B.01 for the GFC 3308) orlater: The #PWRUP.001 signal will be used to report if the date andtime are questionable after a warm start (power fail recovery).

Note: Users should NOT designate #TIME signals for collection viareport by exception (RBE) because they will be ignored by the RBEsystem, i.e. they will not be reported. Users wanting to collect timedata via RBE should use a Calculator Module and save the #TIMEvalue into a regular user-created analog signal, then designate thatsignal for RBE collection.


Page System0-1

System0System0 Module

The System0 Module contains a list of system signals which areautomatically generated by the ACCOL software. These signalsidentify parameters such as errors, limits, time date, diagnostics, line,link, and node failures. The numerical value of “pi” and the exponen-tial “e” are also included.

The System0 Module is only useful for on-line AIC users; it cannot beused in conjunction with 386EX Protected Mode units (PLS00/PLX00firmware, or newer.)

The System0 Module is not accessed or entered on the Task StructureMenu of AIC. It is strictly a storage area for system signals and isaccessed from a poke-point on the task-level menu for Task 0.

System signals can neither be edited nor deleted by the user. How-ever, they can be used in the load to provide functions such as timing,limits, real time, and mathematical constants.

❏ System Signal SyntaxSystem signals are identified by signal names which can consist ofonly a base, or a base and extension. The base is always an alphadesignation, while the extension can be alpha or numeric. All systemsignals are also preceded by the pound sign (#) to assist in positiveidentification. Some sample system signal names are as follows:

#ERARRAY.. #TIME.000#ERRCT.LIM #PWRUP.000

❏ Menu FunctionsThe System0 Menu (shown in the next figure) displays the signaldescription in the first column and the signal name in the second

System0


Page System0-2

System0System0 Module

column. Both of these columns will appear on the menu whether it isoperating off or on line. The three columns at the right will onlyappear when the menu is on line. The first on-line column gives thestatus of a logical signal, the second gives the value of an analogsignal, and the third gives the units text.

Although system signals can appear to be edited on this menu, theoriginal text will be replaced the moment that the ENTER key ispressed. These signals are permanently embedded in the AIC and arewrite protected.

Each signal appearing on the System0 Menu is associated with asignal menu. This menu can be accessed by positioning the cursor nextto the desired signal name and pressing the NEXT DISPLAY key.System signals can be assigned alarms, inhibits, values, or options likeany other signal in the load. Signal Menu selections are described inChapter 4 of the ACCOL II Interactive Compiler Manual, document#D4042.

System0 ACCOL task 0 line number 0

ALARM FORMAT #ALARM.FORMATOUTLIST #DIAL.000 0.0000000SLIP LIMIT #RCNT.LIM 20.0000000 COUNTSERROR LIMIT #ERRCT.LIM 0.0000000 ERRORSERROR COUNT #ERRCT.000 9.0000000TK ER ARRAY #ERARRAYNO OC TIME #OCTIME OFFTIME ERROR #OCTIME.ERROR OFFPACKED TIME #TIME.000 0.0000000SEC ELAPSED #TIME.001 981.0000000 SECSYEAR #TIME.002 84.0000000MONTH #TIME.003 6.0000000DAY #TIME.004 3.0000000HOURS #TIME.005 14.3400000 HOURS


Page SYS_3530-1

SYS_35303530-series System Parameters Module

The SYS_3530 Module provides user access to a set of system param-eter signals which are available only for the 3530-series TeleFlow/TeleRTU.

These signals are used to define or indicate various system character-istics of the ACCOL 3530-series unit. Some of the parameters areintended to be changed dynamically by the user, and are identified asOperator Entry fields; other parameter signals are intended only toreport information. Although ACCOL will allow you to alter fieldswhich are NOT Operator Entry fields, the entries you make will NOTbe read by the 3530, only in ACCOL. Because of this, you should onlychange fields designated as Operator Entry fields.

These system parameter signals must be defined in a group of signallists. Signal names are entirely the choice of the user, however, theentries in each list must be made in a specific order.

The SYS_3530 Module is a non-executing module, and so should beplaced in Task 0.

SYS_3530


Page SYS_3530-2



PARAM_LIST1 Default: 0Format: Analog signal or constantInput/Output: Input

is the number of a signal list. Signals in this list indicate certaincharacteristics for communications Port A of the EGM/RTU 3530. Thislist must include the following items, in the order shown:

Operator Entry

Entry Signal Type Field? Description

1 Local Port Baud Rate Analog YES Used to set or read baud rate.

2 Local Port Active Indicator Logical NO Turned ON when local port connec-tion is made.


is the number of a signal list. Signals in this list indicate certaincharacteristics for communications port B of the EGM/RTU 3530. Thislist must include the following items, in the order shown:

Operator Entry


1 Network Port Baud Rate Analog YES Used to set or read baud rate.

2 RTS/CTS Delay Mode Logical YES Used to select whether Timer orCTS should be used. Timer=OFF ;CTS=ON

3 RTS/CTS Transmit Delay Analog YES Used to set or read the CTS delay.(in Milliseconds)


Page SYS_3530-3



is the number of a signal list. Signals in this list indicate certaincharacteristics for communications port C of the EGM/RTU 3530. Thislist must include the following items, in the order shown:

Operator Entry


1 Expanded Port Baud Rate Analog YES Used to set or read baud rate.

2 RTS/CTS Delay Mode Logical YES Used to select whether Timeror CTS should be used.Timer=OFF ; CTS=ON

3 RTS/CTS Transmit Delay Analog YES Used to set or read the CTSdelay (in milliseconds).


is the number of a signal list. Signals in this list define certain radiocontrol parameters for the EGM/RTU 3530. Radio control can be viamanual control (Local Mode), fast radio sensing (Demand Mode) or viaHourly Scheduling. NOTE: With Hourly Radio Scheduling, the follow-ing formula is used to determine radio Turn ON time (i.e. when theradio is turned ON):

Turn ON Time = [((Poll Time Per Node)*(Local Address - 1))+(Poll Time Per Group *Group Number) + Start Offset Past Hour]

For more on the subject of radio Turn ON time, see the examplesincluded at the end of this section.

PARAM_LIST4 must include the following items, in the order shown:


Page SYS_3530-4


Operator Entry


1 Auxiliary Power Default ON/OFF Logical YES Determines if the 3530'sAuxiliary Power Output is setON or OFF when power isinitially applied to the 3530.This allows radios to bepowered up initally and thenturned OFF after a 'no comm'interval.

2 Hourly Radio SchedulingEnable/Disable Logical YES Enables/disables the Hourly

Radio Scheduling function.When enabled, causes the3530 to automatically turn onthe radio (via the auxiliarypower output) once per hour.

3 Demand PollingEnable/Disable Logical YES Enables/disables the radio

sensing (fast radio) function.Radio sensing allows the userto activate the radio for veryshort time intervals (specifiedin milliseconds underDemand Radio ON time)every so many seconds(specified in seconds underDemand Listen Interval) tosense a valid BSAP messageon the radio's carrierfrequency. If a message is notdetected, the radio isdeactivated. If a message isdetected, the radio is leftactivated until it responds,after which it remains ON foranother Demand ListenInterval. If no more validmessages are detected, theradio returns to 'sense' mode.


Page SYS_3530-5


Operator Entry


3 (continued) This mode allows the systemto use as little energy aspossible to detect trafficthroughout the day. Energyusage depends on theactivation time and rate.Assuming a 1 watt radio thena 200 milliseond listeningperiod every 5 seconds isequivalent to 0.04 watts.

4 Local RadioEnable/Disable Logical YES Set this ON to immediately

turn on the radio. The signalwill then be reset to thedisable state. The localduration and local timeoutvalues control radio on time.

5 Radio Shutdown Logical YES Used to force the radio to turnoff manually when HourlyRadio Scheduling is enabled.When this command is issued,the radio will be kept on justlong enough to reply back tothe master. This command isused to save battery power atthe 3530, and is the lastcommand that can be sent toit.

6 Hourly Radio SchedulingStart Minutes Analog NO This signal specifies (in

minutes) the Hourly RadioScheduling Start Offset PastHour, i.e. how many minutesinto the hour before the radioturns on. See Hourly RadioScheduling Start Offset PastHour.


Page SYS_3530-6


Operator Entry


7 Hourly Radio SchedulingStart Seconds Analog NO This signal specifies (in

seconds) the Hourly RadioScheduling Start Offset PastHour, i.e. how many secondsinto the minute before theradio turns ON. See HourlyRadio Scheduling Start OffsetPast Hour.

8 Hourly Radio SchedulingListen Duration Analog YES Specifies the amount of time

(in seconds) that the radio willstay on every 'listen interval'when Hourly Radio Schedul-ing is active.

9 Hourly Radio SchedulingCommunication Timeout Analog YES The amount of time (in

seconds) that must passwithout a message beingreceived before the radioshuts OFF. If a messagecomes in before expiration ofthis time, the radio willremain active.

10 Start Poll Hour Analog YES Specifies the hour of the day(0 to 23) at which HourlyRadio Scheduling starts. Thissignal is used together withStop Poll Hour to define aspecific time frame (such asdaylight or normal officehours) each day during whichHourly Radio Scheduling isactive. This can save power bypreventing Hourly RadioScheduling during other hoursof the day.

11 Stop Poll Hour Analog YES The hour of the day (0 to 23)at which Hourly RadioScheduling stops. See StartPoll Hour.


Page SYS_3530-7


Operator Entry


12 Local RadioListen Duration Analog YES If Local Radio is enabled, this

specifies the amount of time(in secs) the radio stays on,while there is message traffic.

13 Local RadioCommunicationTimeout Analog YES The amount of time (in secs)

that must pass without amessage being received,before the radio shuts off.

14 Poll Time per Node Analog YES Specifies the time (in seconds)allocated for communicationwith a node. This is one of thefactors used in the calculationof radio on time.

15 Poll Time per Group Analog YES Specifies the time (in seconds)allocated for communicationwith an expanded nodeaddressing group. This is oneof the factors used in thecalculation of radio 'on time'

16 Hourly Radio SchedulingStart Offset Past Hour Analog YES Specifies an offset into the

hour (0 to 3600 seconds)which is used as one of thefactors to calculate radio turnon time, when RadioScheduling is enabled. Thisvalue is converted to HourlyRadio Scheduling StartMinutes and Hourly RadioScheduling Start Seconds foreasier reading. (See above).

17 Demand Listen Interval Analog YES The interval (in seconds) atwhich power is applied to theradio when 'fast radio'(demand polling) is active.


Page SYS_3530-8


Operator Entry


18 DemandRadio ON Time Analog YES The amount of time that the radio

has power applied (in milliseconds)when Demand Polling (fast radiomode) is active.

19 DemandPoll Start Analog YES The hour (0 to 23) at which 'fast

radio' intervals begin each day.

20 DemandPoll End Analog YES The hour (0 to 23) at which 'fast

radio' intervals stop each day.

21 Maximum Dialouts Analog YES Regardless of the number of alarmsthat have occurred, the system willnot attempt to call out each hourmore than the value of MaximumDialouts (with a maximum of threetries per attempt). This number isused to manage the energy drainfrom a battery powered system bylimiting the number of times perhour that the modem can be'awakened' to its full power mode.Set this low to reduce powerconsumption.


is the number of a signal list. Signals in this list define power regula-tion control parameters for the EGM/RTU 3530. This list must includethe following items, in the order shown:


Page SYS_3530-9


Operator Entry


1 Power System, 6/12 Volts Logical NO Indicates the system voltage in use. 6

volts = OFF; 12 volts = ON. This variesdepending on the type of batteryinstalled in the TeleFlow.

2 Power Input #1 Analog NO The voltage reading (in volts) on theMain power connector.

3 Power Input #2 Analog NO The voltage reading (in volts) on theSecondary power connector.

4 System Power Analog NO The voltage reading (in volts) of thevoltage in use on the circuit board.

5 Backup Battery Analog NO The voltage reading (in volts) of theRAM backup battery on the board.

6 Low BackupBattery Indicator Logical NO When ON, indicates that the RAM

backup battery is low.

7 PC Board Temp Analog NO The temperature in degrees F of asensor on the circuit board. NOTrelated to the external RTD.

8 Battery Overcharge Indicator Logical NO Indicates that the battery charger has

detected an overcharge condition.

9 Charge RegulatorEnable/Disable Logical YES Used to enable/disable the charge

regulator.

10 Regulator Active Time Analog YES Used to set a time limit (in seconds) for

charging.


Page SYS_3530-10


Operator Entry


11 Regulator Limit @ 77 F Analog YES The maximum allowable voltage (in volts),

as specified by the battery manufacturer;used by the charger.

12 Temp Coefficient Analog YES The battery temperature coefficient (inmillivolts per degrees F); used by thecharger.


is the number of a signal list. Signals in this list define certain systemcharacteristics of the EGM/RTU 3530. This list must include thefollowing items, in the order shown:

Operator Entry


1 Alarm Display Enable Logical YES This indicates whether or notalarms should appear on theLCD display.

2 Sensor Checksum Error Logical NO Incorrect checksum on the sensorcompensation EEPROM.

3 Spare (currently unused)

4 Spare (currently unused)

5 Self-Check Failure orFirmware Memory ChecksumError Logical NO TeleFlow system error detected.

Either: 1) stack overflow; 2) RAMtest failure; 3) firmware memorychecksum error.


Page SYS_3530-11


Operator Entry


6 Program PROM Logical NO Firmware checksum haschanged.

Checksum Error

7 SPARE (currently unused)

8 SPARE(currently unused)



11 Configuration Change Logical NO An ACCOL signal's value, state,or inhibit/enable status waschanged

12 Extended BSAP enable Logical YES Enables expanded BSAP on aPseudo Slave port only. Thissignal is only available infirmware release TFACCOL1.24 or later.

❏ Examples for Calculating Radio TurnON Time

There are two ways to determine radio Turn ON time:

1) User Determined Start Times

In this example, we have a 5 radio system, and radios are to start at10 minute intervals. Set the Poll Time Per Node and Poll Time PerGroup signals to zero. Set Radio Scheduling to start at 8 (8AM) andstop at 20 (8PM). Set each TeleFlow to a Start Offset Past Hour of 0,


Page SYS_3530-12


600, 1200, 1800, 2400 seconds respectively. The Hourly Start Minutewill show 0, 10, 20, 30, 40 and the Hourly Start Seconds will show 0.Every hour the radios will turn ON at 0, 10, 20, 30, and 40 minutespast the hour respectively. Listen time is controlled by the Durationand Timeout settings.

2) Address Determined Start Times with Fixed Listen Intervals

In this example, we have 5 radios. Set the Start Offset Past Hour tozero, set the Poll Time per Node to 60 (seconds) and Poll Time PerGroup to 0. Assuming node addresses of 1,2,3,4,5 the firmware willcalculate start time offsets of (address - 1) * (Time per Node) = 0, 60,120, 180, and 240 seconds. The Hourly Start Minute will show 0, 1, 2,3, 4 and the Hourly Start Seconds will show 0. Every hour the radioswill turn on at 0, 1, 2, 3, and 4 minutes past the hour respectively.Listen time is controlled by the Poll Time per Node setting. The StartOffset Past Hour signal can be used to adjust the calculated starttimes. More compliecated systems can use the Poll Time per Group.


Page Task-1

TaskACCOL Task

A load file contains ACCOL tasks and system tasks. ACCOL tasks arethose associated with the user’s configuration. A load file can containone or more ACCOL tasks to perform various control functions.System tasks are associated with system functions such as communi-cations, redundancy, polling and diagnostics. The ACCOL tasks areassigned execution rates and priorities by the ACCOL programmer,while those for the System Tasks are fixed by the system.

❏ ACCOL TasksAll ACCOL tasks and system tasks in a load must share executiontime. For an ACCOL task, the user assignment of task rate (frequencyof execution) and task priority combine to determine its place in themulti-tasking environment.

The task rate can be set within the range of 0.02 seconds (50 millisec-onds) to 5400 seconds (90 minutes), or can be set to 'C' for continuousexecution. An important factor to consider when setting the task rateis the time required to execute one full pass of the task from the firstmodule through to the last module. (See #RTTIME.000 and#RTTIME.001 under 'System Signals', earlier in this manual, forinformation on measuring the execution time for a task.)

For example, if it takes 0.5 seconds to execute a task, then its rateshould be set to a value greater than 0.5 seconds. If you have twoACCOL tasks, each of which requires 0.5 seconds to execute one fullpass, then the rate on each should be set to greater than 1 second. AnACCOL task always executes to completion, even if the task rate hasexpired. It then starts re-execution and indicates that the task execu-tion is 'late' by incrementing the slippage count on the task's#RCNT.nnn signal. (See 'System Signals' for details.)

Task priority also affects the execution of tasks. ACCOL task prioritycan be assigned ranging from 1 to 64, with 64 being the highestpriority. When more than one task is ready to execute at the sametime, the one with the highest priority is scheduled; the other tasksare scheduled based on their priorities whenever execution time is

Task


Page Task-2

TaskACCOL Task

available. Tasks having the same priority will share execution time ona rotating basis. The ACCOL task priority relative to the priority ofsystem tasks must also be considered, and is discussed later.

If an ACCOL task rate is set to 'Continuous' and it contains no controlstatements such as WAIT FOR, WAIT DELAY, etc., to permit lowerpriority tasks to execute, its priority MUST BE lower than all otherACCOL or system tasks; otherwise the lower priority task WILLNEVER EXECUTE.

❏ System Tasks

All loads contain System Tasks that provide functions such as power-up, communications, redundancy, and diagnostics. Some SystemTasks also perform special duties for particular ACCOL modules.These tasks have pre-assigned task priorities shown in the table onthe next page, center column. The ACCOL programmer must decidewhether certain ACCOL Tasks will have priority over System Tasks.To see the relationship between ACCOL task priorities and systemtask priorities, find the ACCOL task priority appearing in the righthand column of the table, and compare it to the system task priority inthe center column. Care should be exercised, not to place certainACCOL modules in ACCOL tasks which have greater priorities thanthe system tasks which support those modules. The HSANIN Module,for example, should never be placed in an ACCOL task with a prioritygreater than 31. That is because a higher ACCOL task priority, 32, isequivalent to a system task priority of 112. 112 is the priority of theHSANIN system task, therefore there will be a conflict. Similarly, aMASTER Module must always be placed in an ACCOL task with apriority less than 33 since an ACCOL task priority of 33 is equivalentto a system task priority of 139. By examining the table, it can be seenthat 139 is greater than the Master Module communications systemtask priority of 120. The table on the next page shows the relationshipof all system and ACCOL Tasks and their priorities.


Page Task-3

TaskACCOL Task

System ACCOLSystem Task Task Priority Task Priority

Power Up 200System Command Task 199On-Line Diagnostics 199CBO I/O Task1. 198PDO Module Task 198Redundancy2. 198Custom Module Task 197RIOR Task3. 197

181-196 49-64139-154 33-48

Pseudo Slave Task 129Alarm Report Task 127Slave Communications Task 126IP Communications Task6. 126RBE (Report By Exception)4. 120RDB (Data Collection Responses) 120Alarm Acknowledge 120Master Module Task 120Slave Module Task 120Template Manager Task (CFE) 119AGA8 Module Task5. 119HCBO Module Task1. 119(continued on next page)

1. Available only in ACCOL version 5.7 (or later) with AH.00 (or later) PROM set.2. For ACCOL versions earlier than 5.0, task priority for redundancy is set at 197.3. RIOR only available in ACCOL version 5.3 (or later) with the AD.00 (or later) PROM set.4. Available only in ACCOL version 5.5 (or later) with AF.00 (or later) PROM set.5. Priority can be changed from module terminals.6. Available only in Protected Mode PLS03/PLX03/PES03/PEX03 or newer firmware.


Page Task-4

TaskACCOL Task

System ACCOLSystem Task (continued) Task Priority Task Priority

Communications Poll Task 115Master Communications Task 114Expanded Addr. Master Task7. 114GBBTI Smartkit Interface Task10. 114Logger Module Task 113DPC 3330 Keyboard Module Task8. 113HSANIN Module Task9. 112

97-112 17-32Off-Line Diagnostics 71

55-70 1-16

7. Available only in ACCOL version 5.6 (or later) with AG.00 (or later) PROM set.8. Available only in ACCOL 5.0 and later versions.9. Available only in ACCOL version 5.2 (or later) with AC.10 (or later) PROM set.10.Available only in ACCOL version 5.8 (or later) with AJ.00 (or later) PROM set.

❏ Elements of ACCOL TasksOnce a task is created, the ACCOL programmer adds various modulesto the task, and configures them for the specific user application.

If you are using the AIC, this occurs on the Task Structure Menu.Instructions for using this display are contained in Chapter 3 of theACCOL II Interactive Compiler Manual, document# D4042.

If you are using the ABC, or ACCOL Workbench, this occurs in the*TASK section of the ACCOL source file. See the ACCOL II BatchCompiler Manual, document# D4055, or the ACCOL Workbench UserManual, document# D4051, for details.


Page TCheck-1

TCheckTeletrans Check Module

The TCheck Module may be used to provide status checking and dataprocessing for TeletransTM Model 3508 Transmitter inputs which havebeen collected via the Master Module. In this usage, the transmittermust be configured as a slave node on a BSAP Master Port. TheTCheck Module examines the transmitter status and, if errors arereported which affect the transmitter's data, either holds the last validvalue or uses a user-defined substitution value for the affected processvariables.

The Master Module and TCheck Modules are not used to collecttransmitter data when the transmitters are connected to the BristolTeletransTM Interface (BBTI) Board. When the BBTI board is used, theBBTI Modules (GBBTI, LBBTI) perform similar status and processvariable processing. See BBTI Modules earlier in this manual.

❏❏❏❏❏ Module OperationThe Master Module collects process variable and status informationfrom the 3508 transmitter, and stores this information in an ACCOLsignal list. This signal list is referenced on the INLIST terminal of theTCheck Module. Upon execution, the TCheck Module examines thetransmitter status (fifth entry in the INLIST) to check for transmitter-reported failures which affect the data.

If no failures are reported, the first four entries in the INLIST arecopied, unchanged, to the first four signals in the signal list defined bythe OUTLIST terminal; the data is then available for use by othermodules in the ACCOL load. Questionable data status is cleared.

If failure(s) are reported by the transmitter which affect one or more ofthe process variables (differential/gauge pressure, static pressure, RTDtemperature, or estimated sensor temperature,) the values on theoutput signals are determined based on the value of the ERRORCNTsignal, and the substitution terminals (DGPSUB, SPSUB, RTDTSUB,and ESTSUB) as described below, under 'Substitution Processing.'

TCheck


Page TCheck-2


The status of TCheck Module operation is reported on the STATUSterminal. Substitution of process variables, or the holding of the lastvalid value of process variables, is indicated by a 1 on this terminal.

Substitution Processing*

During a transmitter hardware failure, the signals in the OUTLISTwhich are affected by the failure have their values set based on thevalue of the ERRORCNT terminal signal, and the values of the signalson the substitution terminals (DGPSUB, SPSUB, RTDTSUB, andESTSUB.)

If the ERRORCNT value is set to greater than 0, and a transmitter-reported hardware failure affects transmitter data, the last valid valuefrom the transmitter is maintained on the affected signal in theOUTLIST, and the questionable data status is set on. If the failureclears before the number of module executions defined by theERRORCNT value, the module accepts new data from the transmitter,and clears the questionable data status. If the failure is not correctedwithin the number of module executions specified by the ERRORCNTvalue, and a substitution signal value is defined on the associatedsubstitution terminal (DGPSUB, SPSUB, RTDTSUB or ESTSUB), thesubstitution value is reported on the affected signal in the OUTLIST,and questionable data status remains on. If no substitution value hasbeen defined, i.e. the substitution terminal is unwired, the last validvalue is maintained, and questionable data status remains on.

If the failure is cleared after the number of module executions definedby ERRORCNT, the value on the affected signal in the OUTLIST,along with the questionable data status, is maintained for one addi-tional module execution. The module then resumes accepting datafrom the transmitter, and clears the questionable data status, pro-vided no new failures are reported. This means that the module mustreceive two consecutive valid values from the transmitter, before it willbegin reporting new transmitter data.

* Only transmitter-reported hardware failures will trigger substitution processing; errors in communications, or the TCheck module DO NOT cause substitution processing.


Page TCheck-3


If the ERRORCNT value is set to 0, substitution processing occurs inthe same way as when it is set to greater than 0, except that thesubstitution occurs on the first occurrence of a hardware failure. If,however, the required substitution terminal is unwired, the last validvalue is maintained. As before, two consecutive module executionswithout transmitter-reported failures must occur before new data fromthe transmitter is accepted and reported, and questionable data statusis cleared.

❏❏❏❏❏ Module Terminals

TCHECKDGPSUBSPSUB

ESTSUBRTDTSUB

INLIST

OUTLISTERRORCNT

STATUS

data sent to list specifiedby OUTLIST

INLIST Default: NoneFormat: Analog Signal or constantInput/Output: Input

is an analog signal or value which specifies the ACCOL list numberwith the signals containing the transmitter’s process variable data andstatus as reported by the Master Module. This list must have fiveanalog signals in the first five positions; one for each process variableand a fifth for the returned status value. The five signals, in order,represent:

● Differential/Gauge Pressure● Static Pressure● RTD Temperature● Estimated Sensor Temperature● Status


Page TCheck-4


If the transmitter does not support either static pressure or RTDtemperature, the list must still contain an entry for those processvariables.

OUTLIST Default: NoneFormat: Analog Signal or constantInput/Output: Input

is an analog signal or value which specifies the ACCOL list numberwith the signals into which the filtered process variable data is depos-ited. This list must have at least four analog signals in the first fourpositions; one for each process variable. The four signals must followthe same order as in INLIST. If the transmitter does not supporteither static pressure or RTD temperature, the list must still containan entry for those process variables.

If the INLIST and OUTLIST terminals reference the same signal list,the data will be processed in place. This configuration is NOT recom-mended, however, because when there are failures, the data in the listwill constantly be toggled back and forth between the transmittervalues reported by the Master Module and the substituted valuesreported by the TCheck Module.


is set to reflect the status of module execution.

Code Description

-13 EST in OUTLIST (entry 4) does not reference a validanalog signal.

-12 RTDT in OUTLIST (entry 3) does not reference avalid analog signal.

-11 SP in OUTLIST (entry 2) does not reference a validanalog signal.


Page TCheck-5


Code Description (continued)

-10 DGP in OUTLIST (entry 1) does not reference a validanalog signal.

-9 EST in INLIST (entry 4) does not reference a validanalog signal.

-8 RTDT in INLIST (entry 3) does not reference a validanalog signal.

-7 SP in INLIST (entry 2) does not reference a validanalog signal.

-6 DGP in INLIST (entry 1) does not reference a validanalog signal.

-5 STATUS in INLIST (entry 5) does not reference avalid analog signal.

-4 OUTLIST does not contain enough signal entries. -3 INLIST does not contain enough signal entries. -2 OUTLIST is unwired or references an unknown list

structure. -1 INLIST is unwired or references an unknown list

structure. 0 No transmitter errors. INLIST values copied to

OUTLIST. 1 One or more values in the OUTLIST is being held at

its last valid value, or the substitution value is beingused, because of a transmitter-reported hardwarefailure.

DGPSUB Default: NoneFormat: Analog Signal or ConstantInput/Output: Input

is an optional signal or value which specifies the value to substituteinto the differential/gauge pressure signal (first signal in theOUTLIST) when a hardware failure at the transmitter affects thedifferential/gauge pressure process variable data. The substitution ofthe DGPSUB value during a failure occurs only after the number ofmodule executions specified on the ERRORCNT terminal. See 'Substi-tution Processing,' earlier in this section for details.


Page TCheck-6


SPSUB Default: NoneFormat: Analog Signal or ConstantInput/Output: Input

is an optional signal or value which specifies the value to substituteinto the static pressure signal (second signal in the OUTLIST) when ahardware failure at the transmitter affects the static pressure processvariable data. The substitution of the SPSUB value during a failureoccurs only after the number of module executions specified on theERRORCNT terminal. See 'Substitution Processing,' earlier in thissection for details.

RTDTSUB Default: NoneFormat: Analog Signal or ConstantInput/Output: Input

is an optional signal or value which specifies the value to substituteinto the RTD temperature signal (third signal in the OUTLIST) whena hardware failure at the transmitter affects the RTD temperatureprocess variable data.* The substitution of the RTDTSUB value duringa failure occurs only after the number of module executions specifiedon the ERRORCNT terminal. See 'Substitution Processing,' earlier inthis section for details.

ESTSUB Default: NoneFormat: Analog Signal or ConstantInput/Output: Input

is an optional signal or value which specifies the value to substituteinto the estimated sensor temperature signal (fourth signal in theOUTLIST) when a hardware failure at the transmitter affects theestimated sensor temperature process variable data. The substitutionof the ESTSUB value during a failure occurs only after the number ofmodule executions specified on the ERRORCNT terminal. See 'Substi-tution Processing,' earlier in this section for details.

*In AL.00, RMS02, and PLS00/PLX00 or newer firmwarerevisions, substitution processing for RTD is also triggeredwhen the RTD value falls below -500.


Page TCheck-7


ERRORCNT Default: 5.0Format: Analog Signal or ConstantInput/Output: Input

is an optional signal or value which specifies the number of consecu-tive module executions that are allowed to occur with a transmitter-reported error status before substitution values are used to replaceprocess variable values sent by the transmitter. Until the ERRORCNTvalue expires, or the transmitter error is cleared, the affected processvariable output(s) are held at their last valid value and questionabledata status is set. See 'Module Operation' and the DGPSUB, SPSUB,RTDTSUB, and ESTSUB terminal descriptions, earlier in this section.

IMPORTANT

It is recommended that the ERRORCNT value never begreater than 20. This ensures that for a persistent trans-mitter hardware failure, the affected data from thetransmitter will not be used until two consecutive goodreadings are obtained, thus reducing any effect of thefailure on the transmitter's internal averaging.

Only hardware failures reported by the transmitter which affect thetransmitter's data will cause the ERRORCNT and substitution termi-nals to be used. For errors associated with the TCheck module, ortransmitter communications, no substitutions will take place.

❏ Application ExampleA sample partial ACCOL load file is used to illustrate the use of theTCheck Module to process 3508 transmitter data and status from aMaster Module input list.


Page TCheck-8


Notes About the Example:

In this example, we assume 3 transmitters on Port B, multi-dropped(RS-485), communicating at 9600 Baud. Task 1 contains the MasterModules and TCheck Modules for each transmitter. Task 1 executescontinuously at a relatively high priority level, but is limited to theactual communications rate by the WAIT FOR statements associatedwith each of the three sets of transmitter data. Use of thetransmitter’s process variables (DGP.OUT.nnn, SP.OUT.nnn,RTDT.OUT.nnn, and EST.OUT.nnn is assumed to be handled by otherACCOL tasks.

The handling of transmitter data for the case of communicationsfailure (e.g. a Master Module response timeout) is NOT shown in thisexample. The user may wish to implement actions similar to theTCheck Module, e.g. set Questionable Data on the output signals, oruse substitution values.

In this example, substitution values are not shown on the TCheckModule substitution signals; these will vary with the particular trans-mitter type, transmitter configuration, and application.

The signal names used are for illustration purposes only; differentnames may be used in your particular application.

Example ACCOL load - (not all parts shown)

*COMMUNICATIONSPORT_A PSLAVE 9600PORT_B MASTER 9600 3 10PORT_C SLAVE 9600PORT_D UNUSEDBUFFERS 20*TASK 1 RATE: C PRI: 10*TASK 2 RATE:*TASK 3 RATE:10 * C *********TASK 1 COLLECTS 3508 TRANSMITTER DATA**************20 * C30 * C START-UP AND POWER FAIL LOGIC (NOT SHOWN)40 *....


Page TCheck-9


..100 *110 * C POLL FOR 3508 DATA - WAIT FOR I/O COMPLETION120 * MASTER REMOTE 1.0000000 POINT 1.0000000 MODE 1.0000000 INLIST 36.0000000 STATUS_1 MASTER.DONE.001 STATUS_2 MASTER.STATUS.001130 * MASTER REMOTE 2.0000000 POINT 1.0000000 MODE 1.0000000 INLIST 40.0000000 STATUS_1 MASTER.DONE.002 STATUS_2 MASTER.STATUS.002140 * MASTER REMOTE 3.0000000 POINT 1.0000000 MODE 1.0000000 INLIST 44.0000000 STATUS_1 MASTER.DONE.003 STATUS_2 MASTER.STATUS.003150 * WAIT FOR (MASTER.DONE.001) 0.1, 1. S,160 * CALCULATOR 10 XMTR.COMM.FAIL=(MASTER.STATUS.001!=0)170 * IF(~XMTR.COMM.FAIL)180 * TCHECK INLIST 36.0000000 OUTLIST 38.0000000 STATUS TCHK.STATUS.001 DGPSUB TCHK.DGPSUB.001 SPSUB TCHK.SPSUB.001 RTDTSUB TCHK.RTDSUB.001 ESTSUB TCHK.ESTSUB.001 ERRORCNT TCHK.ERRCNT.001190 * ELSE200 * C COMMUNICATION FAILED TO TRANSMITTER 1210 * C (LOGIC NOT SHOWN)220 * C230 * ENDIF250 * WAIT FOR (MASTER.DONE.002) 0.1, 1. S,260 * CALCULATOR 10 XMTR.COMM.FAIL=(MASTER.STATUS.002!=0)270 * IF(~XMTR.COMM.FAIL)280 * TCHECK INLIST 40.0000000 OUTLIST 42.0000000


Page TCheck-10


STATUS TCHK.STATUS.002 DGPSUB TCHK.DGPSUB.002 SPSUB TCHK.SPSUB.002 RTDTSUB TCHK.RTDSUB.002 ESTSUB TCHK.ESTSUB.002 ERRORCNT TCHK.ERRCNT.002290 * ELSE300 * C COMMUNICATION FAILED TO TRANSMITTER 2310 * C (LOGIC NOT SHOWN)320 * C330 * ENDIF350 * WAIT FOR (MASTER.DONE.003) 0.1, 1. S,360 * CALCULATOR 10 XMTR.COMM.FAIL=(MASTER.STATUS.003!=0)370 * IF(~XMTR.COMM.FAIL)380 * TCHECK INLIST 44.0000000 OUTLIST 46.0000000 STATUS TCHK.STATUS.003 DGPSUB TCHK.DGPSUB.003 SPSUB TCHK.SPSUB.003 RTDTSUB TCHK.RTDSUB.003 ESTSUB TCHK.ESTSUB.003 ERRORCNT TCHK.ERRCNT.003390 * ELSE400 * C COMMUNICATION FAILED TO TRANSMITTER 3410 * C (LOGIC NOT SHOWN)420 * C430 * ENDIF*LIST 36 10 XMTR.DGP.001 20 XMTR.SP.001 30 XMTR.RTDT.001 40 XMTR.EST.001 50 XMTR.ERROR.001*LIST 38 10 DGP.OUT.001 20 SP.OUT.001 30 RTDT.OUT.001 40 EST.OUT.001*LIST 40 10 XMTR.DGP.002 20 XMTR.SP.002 30 XMTR.RTDT.002 40 XMTR.EST.002 50 XMTR.ERROR.002*LIST 42


Page TCheck-11


10 DGP.OUT.002 20 SP.OUT.002 30 RTDT.OUT.002 40 EST.OUT.002*LIST 44 10 XMTR.DGP.003 20 XMTR.SP.003 30 XMTR.RTDT.003 40 XMTR.EST.003 50 XMTR.ERROR.003*LIST 44 10 DGP.OUT.003 20 SP.OUT.003 30 RTDT.OUT.003 40 EST.OUT.003

BLANK PAGE

TimerTimer Module


Page Timer-1

The Timer Module generates timed outputs which can be used tocontrol other actions in the system. Three outputs are provided:

1. A timed triggered output (OUTPUT_1 terminal)2. A delayed output (OUTPUT_2 terminal)3. A remaining time output (TIME terminal)

The timing interval is set by the value (in seconds) of an analogSETPOINT signal. The timing interval starts when the signal on theINPUT terminal makes an OFF-to-ON transition. Additional OFF-to-ON transitions of the INPUT will restart the timing interval, if it hasnot finished.

Timing resolution is always determined by the rate at which themodule executes, i.e., a Timer Module in a task executing everysecond has one second resolution; for finer timing resolution the taskrate must be faster.

❏ Module TerminalsINPUT Default: None, entry required


is used to start the Timer timing. An OFF-to-ON transition on thisterminal turns the OUTPUT_1 signal ON, turns the OUTPUT_2signal OFF, and sets the TIME signal equal to the SETPOINT value.

INPUT

SETPOINT

RESET

OUTPUT_1

OUTPUT_2

TIME

Timer


Page Timer-2

TimerTimer Module

If the INPUT signal goes OFF and then ON again before the timinginterval has expired, a new interval will be started.

SETPOINT Default: None, entry requiredFormat: Analog signal or constantInput/Output: Input

specifies the time interval (in seconds) for OUTPUT_1 to remain ON.While OUTPUT_1 is ON, OUTPUT_2 will be OFF.

RESET Default: ON, entry is optionalFormat: Logical signalInput/Output: Input

resets the Timer. When the RESET signal is OFF, the timer is reset tozero and both OUTPUTS are turned OFF. Any OFF-to-ON transitionsat the INPUT terminal will be ignored. When the RESET signal isON, the module is enabled and waiting for an OFF-to-ON transitionon the INPUT terminal signal.

TIME Default: NoneFormat: Analog signalInput/Output: Output

specifies the remaining time (in seconds) before OUTPUT_1 will be setto OFF and OUTPUT_2 set to ON. When an OFF-to-ON transition onthe INPUT terminal occurs, the TIME terminal value is set equal tothe SETPOINT value. On each module execution the TIME valuedecreases until it reaches zero at the end of the time interval.

OUTPUT_1 Default: None, entry is optionalFormat: Logical signalInput/Output: Output

is set ON when the INPUT signal makes an OFF-to-ON transition

TimerTimer Module


Page Timer-3

(and RESET is ON) and remains on for the number of seconds definedby the SETPOINT terminal. If RESET goes OFF before the timeinterval elapses, this output is set to OFF. If the INPUT is set OFFand then makes another OFF-to-ON transition before the timinginterval has expired, OUTPUT_1 remains ON from the time of thenew OFF-to-ON transition, and stays on for the duration of anotherfull SETPOINT time interval

OUTPUT_2 Default: None, entry is optionalFormat: Logical signalInput/Output: Output

is turned OFF when the INPUT signal makes an OFF-to-ON transi-tion, and turns ON when the time interval defined on the SETPOINTterminal has expired. OUTPUT_2 remains ON until the RESET signalis set to OFF, or the INPUT signal makes another OFF-to-ON transi-tion.

❏ Principles of Operation

Assume that the Timer Module is in a task executing once per second,and has a value of 21 seconds on the SETPOINT terminal. Alsoassume that the module has been reset and that the RESET signal isnow ON (enabled) and the INPUT signal is OFF. Both the OUTPUT_1and OUTPUT_2 signals are also OFF.

Before the module executes again a system condition sets the INPUTto ON. When the module executes, the OFF-to-ON transition of theINPUT is detected. OUTPUT_1 is set to ON, OUTPUT_2 remainsOFF, and the TIME signal is set to 21.

At the 1 second task rate, OUTPUT_1 will remain ON for 21 seconds(the SETPOINT value). Each time the timer executes during thisperiod, the TIME terminal will be decremented to show how muchtime remains on the timer. When 21 seconds has expired, OUTPUT_1will turn OFF, at which time, OUTPUT_2 will turn ON. OUTPUT_2


Page Timer-4

TimerTimer Module

TIM

E

TS

PEdg

e 3

occu

rs b

efor

etim

er ti

mes

out

.E

xten

ds d

elay

by

SP

.

INP

UT

12

3

RE

SE

T

ON

OF

F

OU

T 1

ON

OF

FT

SP

OU

T 2

TS

P

ON

OF

F

tsp

= ti

min

gse

tpoi

nt v

alue

TimerTimer Module


Page Timer-5

will remain ON until the RESET terminal is turned OFF, or theINPUT goes OFF and then makes another OFF-to-ON transition,which would restart the timing interval.

The relationship of the INPUT, RESET, OUTPUT and TIME signalsare shown graphically in the figure on the previous page.

❏ Timer Applications

The Timer Module is commonly used as a delay or holdoff timer; theoutputs are used to control other actions within the system. In thefirst example, below, the RESET terminal is wired to the INPUTterminal so that the outputs are set OFF when the INPUT goes toOFF. When the Timer is started and the time interval established bythe SETPOINT has elapsed, OUTPUT_2 is set ON. Either outputcould be used to enable another action in the system. The timingwaveforms for this application are shown in the figure.

Timer Application Example 1 - Delay Timer

INPUTSETPOINT

RESET

OUTPUT_ 2

TIME

input/reset

OUTPUT_1

OUTPUT_2

TIME

setpoint


Page Timer-6

TimerTimer Module

The second example (see figure below) uses only the OUTPUT_1signal. In this case, the OUTPUT_1 signal is used to hold an externaldevice ON for a fixed period of time. The corresponding waveformsappear at the right of the figure.

Timer Application Example 2 - hold external device ON for specified time

INPUT

SETPOINT

OUTPUT_ 1

TIME

INPUT

OUTPUT_1

TIME

10 seconds


Page TOT/TRND-1

TOT/TRNDTotals/Trend Module

The TOT/TRND Module reads an analog or logical input signal,multiplies it by a scaling factor and totalizes (sums) the readings forone hour, 8 hours (a work shift), 24 hours (daily) and one month.Current and previous totals are available for all four time intervals.

The module also computes the slope of the input over a time intervalspecified on the TIME terminal. (See Trend Function in this sectionfor more details.)

Beginning with firmware release AE.00 the module will detect theACCOL software version used to compile the load and use single-precision floating point arithmetic for loads compiled prior to version5.4 and double-precision for loads compiled by version 5.4 or newersoftware.

o Module TerminalsINPUT Default: None, entry required

Format: Analog or logical signalInput/Output: Input

is the input signal. If an analog signal is used for the INPUT, ittypically represents a flow measurement. The total flow for the periodsince the last module execution is calculated each time the moduleexecutes, based on the INPUT value, the delta-time in seconds, and

TOT/TRND


Page TOT/TRND-2


the SPAN terminals. This total is then added to the accumulated totalfor each of the four current time intervals: Hour, Shift, Day, andMonth.

INPUT can also be a logical signal. This is useful, for example, whencalculating accumulated runtime for a piece of equipment. When thesignal is in an ON state, a value of 1.0 is used to perform the totalizingfunction; otherwise a value of 0.0 is used.

START_HOUR Default: 00:00 (midnight)START_MIN Format: Analog signal or constant

Input/Output: Input

define the hour and minute at which the first hour and first 8-hourshift of the work day begin. When the internal real time clock minutematches the START_MIN value, the CUR_T_HOUR total is shifted tothe PREV_HOUR signal, and the CUR_T_HOUR signal is reset tozero. The internal real time clock hour is then compared toSTART_HOUR, and, if necessary, the following updates are per-formed:

If following condition Exists: This Action Is Taken:

Hour=START_HOUR CUR_T_SHIFT value copiedor any 8-hour interval to PREV_SHIFT signal;multiple since the CUR_T_SHIFT reset to 0.0START_HOUR

Hour=START HOUR CUR_T_DAY value copiedto PREV_DAY signal;CUR_T_DAY reset to 0.0

Hour=START_HOUR CUR_T_MONTH value copiedand day of the month=1 to PREV_MONTH signal;

CUR_T_MONTH reset to 0.0


Page TOT/TRND-3


TIME Default: None, entry required for trendcalculation. If no value is entered,the trend calculation is not done.

Format: Analog signal or constantInput/Ouput: Input

defines the period in seconds over which the slope of the INPUT willbe computed.

HOUR_SPAN Default: 1.0SHIFT_SPAN Format: Analog signal or constantDAY_SPAN Input/Ouput: InputMONTH_SPAN

modify the input value in the calculation of the total.

The module assumes that your INPUT value is in engineering unitsper second. If your INPUT value is NOT in engineering units persecond, then the value used on each SPAN terminal must include afactor which converts the input to engineering units per second.Additional factors may then be included as desired.

For example, if the INPUT signal is in gallons per minute, it must beconverted to gallons per second:

Gallons 1 minute 1 Gallons ----------- * ----------- = ----- * ------------- Minute 60 seconds 60 Seconds

So, in this case, the value on each of the SPAN terminals must includea factor of (1/60) or 0.0166667. Additional multipliers may also beincluded, as desired.

Suppose, for example, that your input value is in gallons per minute,but you want your hourly, shift, day, and monthly totals to be inbarrels per day. To get the units converted to barrels per day, you

) (


Page TOT/TRND-4


must still include the factor of (1/60) as part of each SPAN calculationin order to convert gallons per minute to gallons per second.

You must then include whichever additional factors are needed for thedesired result.

To get barrels per day, assuming one barrel of a particular liquid is 42gallons, perform the following calculation:

1 Gallons Barrels 86,400 seconds Barrels * * * = 60 second 42 Gallons Day Day

So if your input is in gallons per minute, and you want to have yourhour, shift, day, and month totals in barrels per day, enter (1/60)*(86,400/42) i.e. approximately 34.28 on your HOUR_SPAN,SHIFT_SPAN, DAY_SPAN, and MONTH_SPAN terminals.

If the SPAN terminals are left unwired, the default span of 1.0 willbe used. If the INPUT is already in engineering units per second, theSPAN terminals may be left unwired, unless the user desires differentengineering units on the total signals.

PREV_HOUR Default: NonePREV_SHIFT Format: Analog signalPREV_DAY Input/Ouput: OutputPREV_MONTH

contain the totals for the previous hour, previous shift, previous dayand the previous month. These signals change when new values arereceived from the CUR total terminals at the end of each time inter-val. In order to get valid data on the PREV total signals, the corre-sponding CUR total terminals MUST be wired. These signals will beset to 0.0 if the corresponding CUR total terminals are unwired.


Page TOT/TRND-5


CUR_T_HOUR Default: NoneCUR_T_SHIFT Format: Analog SignalCUR_T_DAY Input/Output: Output (also Input for pre-5.4CUR_T_MONTH loads)

contain the totals for the current hour, current shift, current day andcurrent month. At the conclusion of its time period, the value of eachCUR total terminal is transferred to its corresponding PREV totalterminal and then reset to zero. The MONTH total is transferred atthe start of the workday on the first day of the month.

Note: For pre-5.4 loads, these signals also serve as inputs for thesingle-precision totalizing function; any changes to these terminalswill affect subsequent calculations. For 5.4 (and later) loads, anychanges to these signals will be overwritten at the next module execu-tion.

Note: These signals are required if you intend to receive data for thePREV_HOUR, PREV_MONTH, PREV_SHIFT, or PREV_DAY signals.

DERIVATIVE Default: None. If unwired, slope is notcomputed.

Format: Analog SignalInput/Output: Output

is the computed best-fit linear trend (slope) of INPUT over the timeperiod. For the slope of the INPUT to be computed, the value at theTIME terminal must be greater than the module execution rate. IfINPUT remains at the same value over the time interval the slope willbe zero.


Page TOT/TRND-6


❏ Totalizing Function

The TOT/TRND Module totalizes (sums) an input signal value. Thisinput value is scaled into elapsed time (in seconds), since the lastmodule execution. The totalizing function begins from the very firstmodule execution.

Either an analog or logical signal may serve as an input to the module.The input is sampled and running totals are calculated each time themodule executes. For a logical input signal, a value of 1.0 is used torepresent the ON state, and a value of 0.0 is used to represent theOFF state.

Totals are accumulated over four fixed time intervals (hour, shift, day,and month) and stored in four current total signals wired to theCUR_T_HOUR, CUR_T_SHIFT, CUR_T_DAY and CUR _T_MONTHterminals. Initially, all totals are set to zero. When the module ex-ecutes, the input is multiplied by the delta-time (in seconds) since thelast module execution in order to calculate the total over that period oftime. For each fixed time interval (hour, shift, day, month) the total isthen multiplied by the value of the SPAN, and the result is added tothe current total.

The default start time for the hour, shift, and day is midnight. At theend of each time interval (hour, shift, etc.) the current total is trans-ferred to the corresponding previous signal (PREV_HOUR,PREV_SHIFT, PREV_DAY or PREV_MONTH), and the currentsignals (CUR_T_HOUR, CUR_T_SHIFT, etc.) are reset to 0.0.

The CUR_T_HOUR value is transferred whenever the real time clockminute equals the start time minute (every 60 minutes); theCUR_T_SHIFT is transferred every 8 hours; the CUR_T_DAY istransferrred every 24 hours; and the CUR_T_MONTH is transferredat the start of the work day on the first of the month.

For a particular application, the current hour, shift, and day totalsmay need to be reset at a specific hour and minute which is the start


Page TOT/TRND-7


of the first hour of the first shift of the work day. The start of the workday is defined using the START_HOUR and START_MIN terminals.

❏ Trend Function

The TOT/TRND Module will compute the slope of the INPUT signalover the interval specified on the TIME terminal and write the slopeto the DERIVATIVE terminal. The slope is computed using the leastsquares method over the time interval specified. The value of theTIME terminal specifies the interval in seconds over which slope iscomputed.

For example, if TIME is 60 seconds and the module executes every 10seconds, then the DERIVATIVE will be computed for the 6 inputsamples obtained during the 60 second interval. For a more accuratecomputation, the module could be executed once per second giving 60samples to use in calculating the slope.

BLANK PAGE


Page VLimiter-1

VLimiterVelocity Limiter Module

The VLimiter Module transfers the value of the INPUT terminal tothe OUTPUT_1 terminal. However, before the transfer takes place,the rate of change of the OUTPUT_1 value is checked to see that itdoes not exceed a specified velocity. If this velocity limit would beexceeded, then the transfer is spread out over multiple executions ofthe module, limiting the rate of change of the output while changingthe output to the value of the input.

This module functions as an increasing velocity limiter or a decreasingvelocity limiter, depending upon whether the required change requiresan increase or decrease to the OUTPUT_1 terminal. The limiting slopefor the increasing case is the value of the RATE_UP terminal; thelimiting slope for the decreasing case is the RATE_DOWN terminal.In either of these modes, the rate terminals must have positive values.

When the TRACK signal is ON, OUTPUT_1 tracks the INPUT valueimmediately; no velocity limiting is performed. When TRACK is OFF,OUTPUT_1 is increased or decreased according to the rates specifiedon the RATE_UP or RATE_DOWN terminals, respectively.

Two extended modes of operation are also possible. For these modes,the module only functions in one direction, that is, exclusively as anincreasing rate limiter, or exclusively as a decreasing rate limiter. Toforce the extended increasing mode, set the RATE_DOWN terminal toa negative value. To force the extended decreasing mode, set theRATE_UP terminal to a negative value. If both rates are negative, themodule does not execute. For further explanation of these extendedcases, see the rate terminal descriptions and the module operationsection.

OUTPUT_1

TRACK

OUTPUT_2

INPUT

RATE_UP

RATE_DOWN

Vlimiter


Page VLimiter-2


Module Terminals

INPUT

is the analog value to which OUTPUT_1 is to be set

TRACK

When ON, OUTPUT_1 is set to the input with no ramping. WhenOFF, or if unwired, OUTPUT_1 is ramped to the input over time. SeeModule Operation in this section for more details.

RATE_UP

is the rate in units per second at which the OUTPUT_1 terminalincrease will be limited.

If RATE_UP is negative, then the module only functions as a decreas-ing rate limiter. As long as INPUT is less than OUTPUT_1, OUT-PUT_1 decreases at a rate defined by the RATE_DOWN terminal.Once OUTPUT_1 reaches the value of INPUT, the module goes intoextended mode. In this mode, OUTPUT_1 will continue to decreasebelow the INPUT value. The rate of this continuing decrease is equalto RATE_DOWN or the absolute value of the negative RATE_UPterminal, whichever is smaller.


Default: Off, entry is optionalFormat: Logical signalInput/Output: Input



Page VLimiter-3


RATE_DOWN

is the rate in units per second at which the OUTPUT_1 terminaldecrease is to be limited.

If this value is negative, then the module only functions as an increas-ing rate limiter. The module functions normally as long as INPUT isgreater than OUTPUT_1. Once OUTPUT_1 is reached, the modulegoes into extended mode. In this mode, OUTPUT_1 will continue toincrease above the INPUT value. The rate used for this continuingincrease will be the minimum of the RATE_UP terminal, and theabsolute value of the negative RATE_DOWN terminal.

OUTPUT_1

The value of the OUTPUT_1 terminal is ramped to the value of theINPUT terminal. In extended modes of operation, it can be rampedbeyond the value of the INPUT terminal.

OUTPUT_2

is set ON when INPUT equals or exceeds OUTPUT_1. If not, it is setOFF.





Page VLimiter-4


Module Operation

TRACK is ON

When TRACK is ON, OUTPUT_1 assumes the valueof INPUT when the module executes.

TRACK is OFFRATE_UP and RATE_DOWN are positive

When OUTPUT_1 is less than INPUT, OUTPUT_1increases at a rate limited by the RATE_UP terminaluntil OUTPUT_1 = INPUT.

OUTPUT_1 is not allowed to overshoot INPUT.

When OUTPUT_1 = INPUT, OUTPUT_2 is turnedON.

INPUT

OUTPUT_1

OUTPUT_2 turned ON

OUTPUT_2 is OFFRate = RATE_UP

INPUT

OUTPUT_1

Module executes

OUTPUT_2 turned ON


Page VLimiter-5


TRACK is OFFRATE_UP and RATE_DOWN are positive

When OUTPUT_1 is greater than INPUT, OUTPUT_1decreases at a rate defined by the RATE_DOWNterminal until OUTPUT_1 = INPUT.

OUTPUT_1 is not allowed to overshoot INPUT.

When OUTPUT_1 = INPUT, OUTPUT_2 is turnedON.

INPUT

OUTPUT_1

OUTPUT_2 is OFF

OUTPUT_2 turned ON

Rate = RATE_DOWN


Page VLimiter-6


Extended Mode:

TRACK is OFFRATE_UP is positive and RATE_DOWN is negative

If RATE_UP is positive and RATE_DOWN is negative,then the module is in 'increasing' mode. OUTPUT_1increases at a rate defined by RATE_UP. WhenOUTPUT_1 is equal to or greater than the INPUT,OUTPUT_1 will continue to increase at a rate which isequal to RATE_UP or the absolute value ofRATE_DOWN, whichever is less.

When OUTPUT_1 is greater than or equal to theINPUT, then OUTPUT_2 is set ON; otherwise, OUT-PUT_2 is OFF.

INPUT

OUTPUT_1

OUTPUT_2 turned ON

OUTPUT_2 is OFFRate = RATE_UP

Rate = minimum of RATE_UPor RATE_DOWN


Page VLimiter-7


TRACK is OFFRATE_UP is negative and RATE_DOWN is positive.

If RATE_UP is negative and RATE_DOWN is positive,then the module is in decreasing mode. OUTPUT_1decreases at a rate defined by RATE_DOWN. WhenOUTPUT_1 is equal to or less than the INPUT, OUT-PUT_1 will continue to decrease at a rate which isequal to RATE_DOWN or the absolute value ofRATE_UP, whichever is less.

When OUTPUT_1 is less than or equal to the INPUT,then OUTPUT_2 is set ON; otherwise, OUTPUT_2 isOFF.

When either RATE_UP or RATE_DOWN is negativeand the value of OUTPUT_1 reaches the INPUT valuebetween executions of the module, then the absolutevalue of the negative rate is applied to OUTPUT_1 forthat portion of time that remains after the input levelhas been reached. For example, if the module isexecuting at a 5 second rate, and OUTPUT_1 wouldequal the input after 3 seconds of ramping at theRATE_UP value, then the absolute value of theRATE_DOWN value is applied to the output for 2seconds.

If both rates are negative, the module does not exe-cute.

INPUT

OUTPUT_1 Rate = RATE_DOWN

OUTPUT_2 turned ON

Rate = minimum of RATE_UPor RATE_DOWN

OUTPUT_2 is OFF

BLANK PAGE


Page VMUX-1

VMuxVelocity Multiplexer Module

INLIST

SELECT

OUTPUT

INPUT_n

RATETRACK

The VMUX Module selects one value from a group of inputs andmodifies the OUTPUT terminal until OUTPUT equals the input.

Input signals and values for this module are contained in the signallist named on the INLIST terminal or they can be defined on theINPUT terminals of this module.

A new input is chosen by changing the value on the SELECT terminal.If the selected input is different from the value on the OUTPUTterminal, OUTPUT is changed in the following manner. When TRACKis ON, OUTPUT assumes the value of input immediately, withoutramping. When TRACK is OFF, step changes are made to the OUT-PUT each time the module executes. The algorithm for changingOUTPUT is explained in Module Operation in this section.

Module Terminals

TRACK

causes OUTPUT to be set equal to the selected input immediatelywhen TRACK is ON. If TRACK is OFF or unwired, the modulefunctions with the rate calculation, ramping OUTPUT to the selectedinput.


VMux


Page VMUX-2




Default: INPUT_1Format: Analog or logical signal or constantInput/Output: Input

RATE

defines the rate in units per second at which OUTPUT will change asit moves toward the selected input. This value is always converted to apositive number, and then used to reduce the difference betweenthe input and OUTPUT to zero over time.

NOTE: If your application requires a rate for each input, wire theoutput of the EMUX Module to the RATE terminal of the VMUXModule and use the same SELECT signal with both modules.

OUTPUT

is the current input less the current difference. The difference isinitialized whenever SELECT changes. It is set to the differencebetween the new input and the current OUTPUT. If SELECT has notchanged, then the difference is calculated as follows:

DIFF = DIFF - (TIMEelapsed * RATE)

where TIMEelapsed is the number of seconds since the last time themodule executed.

SELECT

determines which signal in the INLIST or which INPUT_n terminalwill be used.

This terminal functions exactly like the SELECT terminal in theEMUX Module. When SELECT is a logical signal and it is FALSE, the


Page VMUX-3


first signal in the signal list or INPUT_1 is used. If SELECT is TRUE,the second signal in the signal list or INPUT_2 is used.

If SELECT is an analog signal, the value of the signal indicates theposition in the signal or terminal list. (For example, when SELECT is2, the second value in the signal list or INPUT_2 is selected.)

INLIST

is the signal list which provides input signals. If this terminal isunwired, then the inputs are taken from the INPUT terminals.Signals in the signal list must be analog signals. If the signal is notanalog, then error -113 is stored in the #ERARRAY error array.

INPUT_n

are the input signals for this module. When one of these inputs isselected via the SELECT terminal, it becomes the value to whichOUTPUT will be ramped. Up to 255 input signals are allowed.

Default: None, entry is optional; If unwired,inputs are taken from the INPUTterminals.


Default: INPUT_1, if INLIST is also un-wired



Page VMUX-4


Module Operation

When TRACK is ON, OUTPUT assumes the value of INPUT immedi-ately, without ramping.

When TRACK is OFF, step changes are made to the OUTPUT eachtime the module executes according to the following rules:

If SELECT changes, then initialize DIFF:

DIFF = INPUT - OUTPUT

Then every execution of the module, update DIFF:

DIFF = DIFF - (TIMEelapsed * RATE)

If DIFF<0, DIFF = 0

OUTPUTend = INPUT - DIFF

In this way, the difference between INPUT and OUTPUT is reduceduntil they are equal. The following example illustrates the calcula-tions:

A B C D E F G2

time SELECT INPUT_1 INPUT_2 RATE OUTPUTstart DIFF OUTPUTend

(sec)

0 1 100 500 75 100 0 100 1 2 100 500 75 100 3251 175 2 2 100 500 75 175 250 250 3 2 100 300 75 250 175 125 4 2 100 300 75 125 100 200 5 2 100 300 75 200 25 275 6 2 100 300 75 275 0 300 7 2 100 300 75 300 0 300


Page VMUX-5


Notes:

1. Difference = At Time 1, SELECT changes, so a new difference iscalculated:

DIFF = 500 - 100 = 400

then the normal difference calculation is performed.

2. OUTPUTend

= (B or C) - F; B or C is used depending if SELECT is 1 or2.

Error Messages

The following errors are detected at run time. The following errorcodes may be found in the #ERARRAY error array.

-110 Out of range for list or INPUT terminals-111 The list identified by INLIST terminal does not exist.-112 The selected INPUT terminal is unwired-113 The list element is not the correct signal type.-114 Fatal error; for this module, the signal was unwired.

BLANK PAGE


Page WAIT DELAY-1

WAIT-DELAYWAIT DELAY Command

This command will delay an operation of the task by a specific timeperiod. Once a specified time period has lapsed, normal task executionwill resume.

Syntax

WAIT DELAY time units

where:

time is an analog signal or constant and is the amount of the delay.

units is a code for the appropriate unit for time. Valid entries include:

H for hoursM for minutesS for seconds

The default is milliseconds. A space is required between the command,the time and the units fields.

ExampleWAIT DELAY PUMP.DELAY.TIME M

WAIT DELAY

BLANK PAGE


Page WAIT DI-1

WAIT DIRWAIT DI

WAIT DI and REMOTE WAIT DI Commands

The WAIT DI and RWAIT DI statements will stop task execution untila designated discrete input makes a transition from high-to-low orlow-to-high. (A “high-to-low” transition is equivalent to saying that thediscrete input changed state from ON to OFF. A “low-tohigh” transi-tion is equivalent to saying that the discrete input changed state fromOFF to ON.) Once the expected type of transition occurs the taskexecution is resumed.

The WAIT DI and RWAIT DI statements are very similar except withrespect to the location of the discrete input that the task executionwaits for. WAIT DI waits for an input change from a DI in a processI/O board in the same controller in which this ACCOL load is running.RWAIT DI waits for an input change from a DI in a process I/O boardthat resides in a Remote I/O Rack.

❏ SyntaxWAIT DI device di timeout units flagWAIT DIL device di timeout units flagWAIT DIH device di timeout units flag

RWAIT DI device di timeout units flagRWAIT DIL device di timeout units flagRWAIT DIH device di timeout units flag

where:

WAIT DI, WAIT DIL, and WAIT DIH (and similarly RWAIT DI,RWAIT DIL, and RWAIT DIH) specify the type of transition thatwill be tested. WAIT DI or RWAIT DI commands signify that thestatement will act on any transition of the designated DI, eitherhigh-to-low or low-to-high. Similarly, the commands, WAIT DIH orRWAIT DIH respond only to a low-to-high transition of the DI,while the commands WAIT DIL or RWAIT DIL respond only to ahigh-to-low transition of the DI.

WAIT DI/RWAIT DI


Page WAIT DI-2

WAIT DIRWAIT DIWAIT DI and REMOTE WAIT DI Commands

device is a process I/O board ID number where the digital input signalresides. For example, a 1 in this field means DI1. For the WAIT DIcommands, this number may range from 1 to 12, depending uponwhich type of controller you are using. For the RWAIT DI com-mands, the board number may range from 100 to 499. For furtherdetails on specifying the device, refer to the explanation of theDEVICE terminal in the ‘DIGIN Module’ section.

di is the number of the DI wiring terminal for the designated DI onthe process I/O board.

timeout is an optional analog signal or constant that represents theperiod for which it is desired to prevent the task from executing.

units accepts a mnemonic to specify the timeout period. Use H forhours, M for minutes, and S for seconds. The default is millisec-onds. When the specified timeout period has lapsed, task executionwill resume even if the transition that you’re waiting for has notoccurred.

flag is a logical signal which is set ON if a timeout occurred due to aWAIT DI command. Otherwise it is set OFF. This field is optional.

For RWAIT DI statements, flag is an analog signal that returns thefollowing status values:

1 Specified transition has occurred 0 Waiting, or execution successful-1 Invalid remote device ID-2 Communication failed with remote unit-3 Remote board is missing-4 Remote board is of the wrong type-5 The remote board failed diagnostic tests-6 Timeout has occurred-7 RIO Rack firmware incompatible with process I/O configured in

load. (C.01 or newer PROMs should be installed in the 3331.)


Page WAIT DI-3

WAIT DIRWAIT DI

WAIT DI and REMOTE WAIT DI Commands

Note: When an RWAIT DI statement is waiting for a transition of aDI, and the transition occurs, notification of the change of state willnot reach the 3310/3330/3335 controller until the Remote I/O Rack hasbeen polled for data. Because of this delay, it is recommended that pollperiods for the RIOR ports should be set as fast as possible which is0.02 seconds (20 milliseconds). See #POLLPER.nnn under ‘SystemSignals’ for more information.

Each field is separated by a single space. Commas are placed whereindicated.

❏ ExampleWAIT DIL 1, 2, 3.6 M, T502

RWAIT DIH 101, 2, 3.6 M, T503

BLANK PAGE

WAIT FORWAIT For Command


Page WAIT FOR-1

The WAIT FOR command will stop execution of the task and wait fora logical expression to become TRUE before continuing.

Syntax

WAIT FOR (expression) resolution, timeout units, flag

where:

expression is a logical expression which when TRUE resumes execu-tion of the task. The expression must be surrounded by parenthesis.This expression can be the name of a logical signal or it can beseveral logical signals arranged in an expression. The task will notexecute until this field is TRUE.

resolution is an analog value which determines the rate in seconds atwhich the expression is evaluated (0.1 seconds minimum). A commamust follow this field.

timeout is an optional analog signal or constant that represents theperiod of time in which the task is prevented from executing. Whenthe timeout period has lapsed, task execution will resume even ifthe expression field has not become TRUE.

units is a code for timeout. Use H for hours, M for minutes, and S forseconds. The default is milliseconds. A comma must follow thisfield.

flag is a logical signal which is set ON when a timeout has occurred.Otherwise, it is set OFF.

Each field is separated by a single space. Commas must be placedwhere indicated. The resolution field must be present.

The expression field shown above checks for a logical state. The datato be placed in this field must be encased in parenthesis. This data can

WAIT FOR


Page WAIT FOR-2

WAIT FORWAIT FOR Command

be the name of a logical signal or it can be several logical signalsarranged in an expression. The task will not execute until this fieldchecks TRUE.

The Resolution field determines the rate, in seconds, at which theexpression is evaluated by the system (the minimum rate is 0.1second). This field requires an analog constant as an entry.

The optional Timeout field is an analog value or signal that representsthe period for which it is desired to prevent the task from executing.The Units field that follows accepts a mnemonic to specify the timeoutperiod in hours, minutes, seconds or milliseconds. When the specifiedtimeout period has lapsed, task execution will resume even if the if theExpression field has not turned TRUE.

The optional Flag field at the end of this statement accepts the nameof a logical signal. This signal will be set ON if a timeout to hasoccurred. Otherwise it is set OFF.

Example

WAIT^FOR^(TANK5.LEVEL.==5)^1,^CONTINUE.AFTER.^M,^FLAG..

In the example, above, TANK5.LEVEL., CONTINUE.AFTER., andFLAG.. are all ACCOL signals. Each '^' character indicates that ablank space must be typed.


Page WAIT TIME-1

WAIT TIMEWAIT TIME Statement

The WAIT TIME statement is used if you want to execute a particulartask ONLY during a particular hour of the day.

The WAIT TIME statement suspends execution of the entire task untila specified time of day. At six second intervals, the WAIT TIME willbe checked to see if the specified time has been reached. When thespecified hour and minute are reached, the task will resume normalexecution, beginning with the next module in the task, and continue atthe normal task rate. Task execution is suspended again once the hourvalue changes, and remains suspended until the specified hour isreached again on the next day.

❏ SyntaxWAIT TIME hh:mm

where:

hh:mm is the hour (0-23) and minute (0-59) at which normalexecution of this task will resume. A space is requiredbetween the command and the time field.

❏ ExampleWAIT TIME 18:25

This statement will cause the task to be executed beginning at 18:25every day. At 19:00 (i.e. when the hour value is no longer 18) taskexecution will be suspended until 18:25 is reached again on the nextday.

WAIT TIME

BLANK PAGE


Page Watchdog-1

WatchdogWatchdog Timer Module

Watchdog Timer Modules can be used in pairs to time an operationwithin a task, or to time a complete task. If the operation has not beencompleted at the conclusion of its time period, a designated DO can bechanged or a selective action can be taken to affect the remainingexecution of the task. The module input is a logical signal thatchanges state at the start of the timed operation, while the moduleoutput is a logical signal that is applied to a DO field wiring terminalto indicate a normal or watchdog condition.

NOTE

Users should not confuse the Watchdog TimerModule with the hardware watchdog failurecondition in 33xx units. They are completelyunrelated to one another.

Watchdog Modules are only appropriate forcertain limited applications in which a DOoutput is required after a Watchdog timertimes out. WAIT DELAY and ABORT state-ments are more useful for most applications.

Watchdog Modules should always be operated in pairs. The WatchdogModules in a pair must utilize one of 3 watchdog timers which areshared among all tasks of the ACCOL load. This means that there can

ENABLEFAIL_STATEFAIL_OPTIONMAX_TIMEMIN_TIMEMODE

DEVICECHANNEL

STATUS

ERRORWatchdog

Watchdog


Page Watchdog-2


be a maximum of 3 different pairs of Watchdog Modules active at anyone time in an ACCOL load. A pair of Watchdog Modules operatingtogether must exist in the same ACCOL task, and must utilize thesame watchdog timer, selected via the MODE terminal. The sameWatchdog timer CANNOT be simultaneously used by WatchdogModules in different tasks.



is the slot number of the I/O Board where the DO output of the Watch-dog Module will be applied.

DEVICE can range from 1 to 12, depending on which I/O board isbeing referenced, and which type of controller is being used. Zeroindicates that no DO output will be used, but the STATUS terminalwill still indicate the watchdog failure condition.

Note: To indicate a watchdog condition at a DO output in a Remote I/O Rack, the DEVICE terminal must be set to zero and then theACCOL signal on the STATUS terminal can be used as the OUTPUTof an RDIGOUT module.

CHANNEL Default: 1Format: ConstantInput/Output: Input

represents the DO field wiring terminal that will be assigned as theoutput of the module. This entry is only valid if a number has beenassigned for the DEVICE terminal.


Page Watchdog-3



is an integer from 0 to 3 which indicates the type of time check desiredas shown below.

0 = Window-type watchdog using Watchdog Timer 2.1 = Limit-type watchdog using Watchdog Timer 1.2 = Limit-type watchdog using Watchdog Timer 2.3 = Limit-type watchdog using Watchdog Timer 3.

ENABLE Default: NoneFormat: Logical signalInput/Output: Input

initiates or stops the timing action. The ENABLE should be turnedON when timing is to begin. Once timing is underway, the WatchdogModule should NOT be re-executed again until it is time to turn OFFthe timing action, with ENABLE set to OFF. Re-executing the Watch-dog Module while timing is underway with ENABLE ON will re-setthe module, and re-start timing.

MAX_TIME Default: NoneFormat: Analog signal or constantInput/Output: Input

specifies the duration of the selected watchdog timer in seconds. If theevent being timed is not completed by the expiration of MAX_TIME, aWatchdog failure has occurred.


Page Watchdog-4


MIN_TIME Default: NoneFormat: Analog signal or constantInput/Output: Input

is the minimum time for the time window check facility. If the eventbeing timed completes before expiration of MIN_TIME, or afterexpiration of MAX_TIME, the watchdog failure has occurred. Thisterminal is only used for MODE 0.

FAIL_OPTION Default: NoneFormat: Analog signal or constantInput/Output: Input

specifies the action to be taken when the watchdog times out. Thisaction is contingent upon the execution of the task rate which, in turn,executes the Watchdog Module.

The options are:

0 = Allow task to continue its rate execution.1 = Abort current task execution. Task will restart from the

beginning, at the next scheduled time, according to task rate.

If the value is not 0 or 1, a -6 status error (unsupported value onFail_OPTION) is generated. (NOTE: The analog signal or value isconverted from floating point to integer (modulo 256) before determin-ing which ‘failed option’ has been selected. Hence, an analog signal orvalue other than 0.0 and 1.0 may generate a ‘failed option’ of 0 or 1.)

FAIL_STATE Default: NoneFormat: Logical signalInput/Output: Input

specifies the state of the signal at the CHANNEL terminal when thewatchdog times out. This terminal is only active when a number has


Page Watchdog-5


been entered at the DEVICE terminal. Make sure that the DO is setto its initial state before the Watchdog Module is invoked. WhenFAIL_STATE is set to ON, it indicates that the DO will go ON whenSTATUS is ON. When FAIL_STATE is set to OFF, it indicates thatthe DO will go OFF when STATUS is ON.

STATUS Default: NoneFormat: Logical signalInput/Output: Output

indicates the watchdog failure condition. The ON state corresponds toa watchdog failure, while the OFF state corresponds to normal operat-ing conditions. You must construct the program so that a watchdogcondition can be initialized and reset; the STATUS terminal does NOTturn OFF automatically after the Watchdog condition clears. In theevent of a watchdog failure, the #ERRCT.xxx system signal for thetask is incremented, and if the #ERARRAY exists in this load, a 10will appear in the array row for this task.


provides information about the module routines. In general, negativevalues indicate an error condition without any corrective action beingtaken. A value of zero indicates no errors have been detected. Theerror codes are as follows:

0 = Successful completion-1 = MAX_TIME terminal entry is out of range or unwired.-2 = MIN_TIME terminal entry is out of range or unwired.-3 = The desired watchdog timer is in use.-4 = The board is not installed.-5 = Entry for CHANNEL terminal is out of range for the DEVICE

installed.


Page Watchdog-6


-6 = Entry for FAIL_OPTION terminal is out of range.-7 = Entry for MODE terminal is out of range.-8 = ENABLE terminal is unwired.

❏ Module OperationThere are three watchdog timers available for use by WatchdogModules in the ACCOL load. Once started, these watchdog timers run'in the background'.

Watchdog Modules should be used in pairs, as shown in the example,below, in which both modules in the pair use the same watchdogtimer.

Example -

A particular industrial process uses a series of valves which open andclose in particular sequences. Whenever VALVE1 is open, VALVE2 issupposed to automatically open within 30 seconds, or else a failure hasoccurred and a klaxon must sound to alert the operator on duty.

The klaxon which will serve as an alarm for the operator must bephysically connected to the digital output DO specified by the DEVICEand CHANNEL terminals.

The task on the next page shows how to set up the pair of WatchdogModules.

NOTE: The ENABLE terminal is only checked when the WatchdogModule is executed, however, we don't want to execute the firstWatchdog Module with the ENABLE signal ON more than once,because each time it executes with ENABLE ON, it resets the module,therefore, we have included a signal called MONITOR.VALVES thatmakes sure the first Watchdog Module is only executed once whenVALVE1 is open.


Page Watchdog-7


The choice of watchdog timer is governed by the MODE terminal. Inthis case, both Watchdog Modules use watchdog timer 1.Specify 30 as the value for the MAX_TIME terminal, and set theFAIL_STATE to ON, indicating that when a failure occurs, the STA-TUS terminal should be turned ON, thereby activating the DO associ-ated with the klaxon.

*TASK 1 RATE: 1.000000 PRI: 11 * C WHENEVER VALVE 1 IS OPENED, VALVE 2 MUST OPEN2 * C WITHIN 30 SECONDS OR THERE IS A FAILURE3 * C4 * C10 * IF (VALVE1.OPENED&MONITOR.VALVES.)20 * WATCHDOG

DEVICE 1CHANNEL 4MODE 1ENABLE #ONMAX_TIME MAX.TIME.FAIL_OPTION FAIL.OPTION.WDOGFAIL_STATE FAIL.STATE.WDOGSTATUS KLAXON.TURN.ONERROR WATCHDOG.ERROR.

30 * CALCULATOR MONITOR.VALVES=#OFF ;To prevent re-init of Watchdog40 * ENDIF50 * IF (VALVE2.OPENED) ;The valve opened in time; shut off timer60 * WATCHDOG

DEVICE 1CHANNEL 4 MODE 1ENABLE #OFFMAX_TIME MAX.TIME.FAIL_OPTION FAIL.OPTION.WDOGFAIL_STATE FAIL.STATE.WDOGSTATUS KLAXON.TURN.ONERROR WATCHDOG.ERROR.

70 * CALCULATOR MONITOR.VALVES=#ON

80 * ENDIF

BLANK PAGE


Page XMTR_Interface-1

XMTR_InterfaceTransmitter Interface Module

The XMTR_Interface Module provides read/write access to thememory of a TeleTrans Transmitter, or other compatible device. Thetransmitter may be accessed either via the BBTI process I/O board, orvia Master Port communications.

❏ Module TerminalsDEVICE Default: 0


is the process I/O slot number in the Network 3000 controller contain-ing the BBTI board. Valid slot numbers are integers from 1 to 12.

If this terminal and the CHANNEL terminal are both set to 0, themodule assumes that Master Port communications, instead of BBTIboards, are used to communicate with the transmitter.

If a valid slot number is specified, but no board exists, or if the boardis of the wrong type, or has incompatible firmware, a device error (-10)will be stored in the #ERARRAY (if configured) when theXMTR_Interface Module is executed.

XMTR_Interface

DEVICE

CHANNEL

REMOTE

MODE

FORMAT

ADDRESS

COUNT

LIST

INDEX

STATUS_!

STATUS_2

XMTR_Interface




CHANNEL Default: 0Format: Analog signal or constantInput/Output: Input

is the channel number on the BBTI process I/O board which corre-sponds to the transmitter to be accessed by the XMTR_InterfaceModule. Valid channel numbers are integers from 1 to 8.

If, instead of using a BBTI board, communications with the transmit-ter is performed using a Master Port, CHANNEL must be set to 0.

An invalid setting for the CHANNEL will generate a channel errorwhen the XMTR_Interface Module is executed. This error will appearas ( -120) in the #ERARRAY, if it has been configured.

REMOTE Default: 0Format: Analog signal or constantInput/Output: Input

is the remote node address of the TeleTrans Transmitter. Valid rangefor this terminal is 1 to 127. Node address 0 is reserved for communi-cation with a master; it is never a valid transmitter node address.

Node address 127 is the transmitter's broadcast address. This addressshould NOT be used in a multi-drop configuration because ALLtransmitters will respond.

The REMOTE terminal is only used when Master Port communicationis used to communicate with the transmitter, it is ignored if either theDEVICE or CHANNEL terminals are NOT 0.

MODE Default: 1Format: Analog signalInput/Output: Input/Output

is the mode of operation of the module. A value of 0 indicates themodule is idle. A value of 1 activates READ mode, allowing data to be




read from the transmitter. A value of 2 activates WRITE mode,allowing data to be written to the transmitter. Once the module hasbeen executed in mode 1 or 2, it will return to mode 0. NOTE: WRITEmode is appropriate only for certain FORMAT codes. See FORMATterminal.

FORMAT Default: 0Format: Analog signal or constantInput/Output: Input

is the type of data to be read or written. Valid entries are integersfrom 0 to 4. Codes which support data writes include an asterisk (*) inthe description.

Code: Description:0 Logical Byte access. Each bit in a byte of data in the mes-

sage maps to the eight consecutive logical signals in theLIST, starting from the offset defined by the INDEX termi-nal. The first logical signal maps to byte Bit 7 and theeighth signal maps to Bit 0.*

1 Unsigned Integer Byte access. Bytes in the message map tothe analog signals in the LIST starting from the offsetdefined by the INDEX terminal. Integer values are con-verted to floating point values during READ mode, andfrom floating point values to integers during WRITE mode.*

2 Signed Integer Byte access. Bytes in the message map tothe analog signals in the LIST starting from the offsetdefined by the INDEX terminal. Integer values are con-verted to floating point values during READ mode, andfrom floating point values during WRITE mode.*

3 Unsigned Integer Word access. Words in the message mapto the analog signals in the LIST starting from the offsetdefined by the INDEX terminal. Integer values are con-verted to floating point values during READ mode, andfrom floating point values during WRITE mode.*

4 Signed Integer Word access. Words in the message map tothe analog signals in the LIST starting from the offset




Code: Description (continued):defined by the INDEX terminal. Integer values are con-verted to floating point values during READ mode and fromfloating point to integer during WRITE mode.*

10 Transmitter type code.11 DP data ranges.12 SP data ranges.13 DP Unit value, returned as an analog (see table, below).*14 SP Unit value, returned as an analog (see table, below).*15 RTD Temp Unit value, returned as analog: 0 = oC; 1 = oF.*+16 Est Temp Unit value, returned as analog: 0 = oC; 1 = oF.* +17 DP Unit value, returned as a string.*18 SP Unit value, returned as a string.*19 RTD Temp Unit value, returned as a string C/F.* +20 Est Temp Unit value, returned as a a string C/F.* +21 Tag name.*22 DP Zero setpoint.23 SP Zero setpoint.24 Current Loop Zero setpoint.25 DP Span setpoint.26 SP Span setpoint.27 Current Loop Span setpoint.28 External current loop control (ON/OFF).*29 Node's Local Address (Station #) *30 Transmitter Real-time data and status information (DP, P,

T, Board temperature, and Error status). This data iscomparable to data contained in the 3508's peer-to-peer List#1. NOTE: This code only applies to 3530-series users.

* may be written to, as well as read.+ when either RTD or EST units are changed, both are set to the

same units (oC or oF).




Table of Engineering Unit Codes For Pressure(Important: Units must be entered exactly as shown)

0 psi 1 kPa2 MPa 3 mm H2O4 inch H2O 5 mm Hg6 inch Hg 7 mbar8 bar 9 g/cm2

10 kg/cm2 11 unknown

ADDRESS Default: 0Format: Analog signal or constantInput/Output: Input

is the memory address in the transmitter which should be accessed. Ifthe FORMAT terminal is NOT set set to read/write bytes or words(FORMATs 0 through 4) then the ADDRESS terminal is ignored.Valid address ranges are as follows:

Read Request: Write Request:19 and 52 19 and 5246592-46693 46592-4669357344-57345

CAUTION

Users should be extremely familiar withtransmitter internals before attempting toRead/Write data from it using the AD-DRESS terminal (FORMAT values 0through 4). Novice users could potentiallycorrupt transmitter memory. SinceFORMAT values 10 through 28 allowaccess to relevant user information,without using the ADDRESS terminal,most users need not use this terminal.




COUNT Default: 0Format: Analog signal or constantInput/Output: Input

is the number of data elements (bits, bytes, or words) to be trans-ferred. This signal only applies when FORMAT ranges from 0 to 4.The range is 8 to 160 bits (in multiples of 8 bits ONLY) when FOR-MAT=0. The range is 1 to 20 for byte requests when FORMAT = 1 or2. The range is 1 to 10 for word requests when FORMAT = 3 or 4.


is the offset into the signal list specified on the LIST terminal. INDEXmust be less than or equal to the number of signals in the list. A 0 or 1entry is interpreted as the first signal in the list.

LIST Default: 0Format: Analog signal or constantInput/Output: Input

is the number of a signal list. Signals in this list are the source ordestination of data during read or write operations, respectively. TheINDEX terminal defines the offset into this list. The value of theFORMAT terminal defines the minimum size of the list.

Value of FORMAT # of signals Signal Type0 8 * COUNT Logical1 COUNT Analog2 COUNT Analog3 COUNT Analog4 COUNT Analog

10 1 Analog11 1 Analog12 1 Analog




Value of FORMAT # of signals Signal Type13 1 Analog14 1 Analog15 1 Analog16 1 Analog17 1 String18 1 String19 1 String20 1 String21 1 String22 1 Analog23 1 Analog24 1 Analog25 1 Analog26 1 Analog27 1 Analog28 1 Logical29 1 Analog30 5 Analog

STATUS_1 Default: NoneFormat: Analog signal or logical signalInput/Output: Output

indicates the status of communication activity between the controllerand the transmitter. If wired to a logical signal, STATUS_1 is turnedOFF when the XMTR_Interface Module initiates communications, andturned ON when communication is complete. If wired to an analogsignal, STATUS_1 is incremented by 1 following successful transmis-sion of a message.




STATUS_2 Default: NoneFormat: Analog signalInput/Output: Output

indicates the status of the module's operation:

Code Description2 Request message sent, awaiting reply1 Request message waiting at BBTI process I/O board RAM

buffer.0 No errors detected, completed successfully.

-1 Dynamic structures for module are missing.-2 Invalid slave node number (must be 1 to 127).-3 Invalid MODE (must be 0, 1, or 2).-4 Invalid request type (must be 0-4 or 10-28).-5 Invalid LIST value or LIST terminal unwired.-6 LIST is empty; no signals are defined in list.-7 INDEX number is out of range; must be < number of

signals.-8 Invalid value specified on COUNT terminal.-9 Transmitter memory address incorrect, allowed ranges are:

19, 52, 46592 to 46693, or 57344 to 57345.-10 Invalid number of elements, FORMAT=0, but COUNT is

not a muliple of 8.-11 LIST overflow; not enough room in list from requested

number of elements.-12 LIST signal is not a logical signal.-13 LIST signal is not an analog signal.-14 Signal could not be updated, it is control inhibited.-15 Mode in transmitter response does not match with mode in

the request that was transmitted.-16 Address in transmitter response does not match with the

address in the request that was transmitted.-17 Transmitter sent fewer elements than requested.-18 LIST signal is not a string signal.-19 Invalid data to be written to transmitter, i.e. pressure

units, temperature units, or local address not in validrange. Also occurs in Protected Mode controllers if anattempt is made to change the Station # of a transmitter




Code Descriptionwhich is attached to a BBTI board.

-101 Communication error during request send.-102 Communication timeout error.-103 Could not allocate a communication buffer.-104 Device error - BBTI board is missing or failed.


The XMTR_Interface Module communicates with a transmitter eithervia the BBTI process I/O board, or via a Master Port. If the DEVICEand CHANNEL terminals specify valid board and channel numbers,the XMTR_Interface Module uses the BBTI process I/O board. If bothDEVICE and CHANNEL are set to 0, communications are via theMaster Port according to the node address on the REMOTE terminal.

The XMTR_Interface Module can read data from the transmitter(MODE terminal set to 1) or write data into the transmitter (MODEterminal set to 2).

The FORMAT terminal determines how data is read or written.FORMAT values of 0 through 4 allow actual bytes or words to beaccessed, according to the address specified via the ADDRESS termi-nal, and the value of the COUNT terminal.

CAUTIONUsers should be extremely familiar withtransmitter internals before attempting toRead/Write data from it using the AD-DRESS terminal (FORMAT values 0through 4). Novice users could potentiallycorrupt transmitter memory. Since FOR-MAT values 10 through 28 allow access torelevant user information, without usingthe ADDRESS terminal, most users neednot use this terminal.




blank

Other FORMAT values (10 through 28) allow transmitter attributessuch as ranges to be read. NOT all FORMAT values allow writing tothe transmitter.

The source for data being written to the transmitter, or the destina-tion for data being read from the transmitter are signals in the signallist specified by the LIST terminal. The INDEX terminal specifies anoffset into the list to determine which signal is to be used.

The STATUS_1 and STATUS_2 terminals provide indications on theoperation of the module.

ACCOL II Reference Manual Page Index-1

Index

Symbols#ALARM.FORMAT. system signal System

Signals-3#ALARM.FORMAT.001 system signal System

Signals-3#ALARM.LIM. system signal System Signals-3#DIAG.001. system signal System Signals-5#DIAG.002. system signal System Signals-7#DIAG.003. system signal System Signals-15#DIAL.000. system signal System Signals-16#DIAL.001. system signal System Signals-17#DIAL.002. system signal System Signals-17#DIAL.003. system signal System Signals-17#DIAL.004. system signal System Signals-18#DIAL.005. system signal System Signals-18#DIAL.006. system signal System Signals-18#DIAL.007. system signal System Signals-19#DIAL.008. system signal System Signals-19#DIAL.009. system signal System Signals-19#E.. system signal System Signals-20#ERARRAY.. system signal System Signals-20#ERRCT.000. system signal System Signals-24#ERRCT.LIM. system signal System Signals-25#ERRCT.nnn. system signals System Signals-25#IPSTAT.. system signal System Signals-26#LINE.000. system signal System Signals-28#LINE.001. system signal System Signals-28#LINE.002. system signal System Signals-28#LINE.003. system signal System Signals-28#LINE.004. system signal System Signals-28#LINE.005. system signal System Signals-28#LINE.006. system signal System Signals-28#LINE.007. system signal System Signals-28#LINE.008. system signal System Signals-28#LINE.009. system signal System Signals-28#LINKE.001. system signal System Signals-29#LINKE.002. system signal System Signals-29#LINKE.LIM. system signal System Signals-30#LINKF.001. system signal System Signals-30#LINKF.002. system signal System Signals-30#LINKF.LIM. system signal System Signals-31#LOAD.. system signal System Signals-31#NDARRAY..

using with Expanded NodeAddressing Expanded Node-4

#NDARRAY.. system signal System Signals-31#NODE.nnn. system signals System Signals-34#NODEADR.. system signal System Signals-34#NRT.INH. system signal System Signals-34#NRT.REQ. system signal System Signals-35#OCTIME.. system signal System Signals-35#OCTIME.ERROR. system signal System

Signals-35

#OFF.. system signal System Signals-35#ON.. system signal System Signals-36#PDM.000. system signal System Signals-36#PDM.001. system signal System Signals-36#PDM.002. system signal System Signals-36#PDM.003. system signal System Signals-36#PDM.004. system signal System Signals-37#PDM.005. system signal System Signals-37#PDM.006. system signal System Signals-37#PDM.007. system signal System Signals-37#PDM.008. system signal System Signals-37#PI.. system signal System Signals-38#POLLPER.nnn. system signals System Signals-

38#PRI.nnn. system signal System Signals-44#PWRUP.000. system signal System Signals-45#PWRUP.001. system signal System Signals-45#RATE.nnn. system signals System Signals-46#RCNT.LIM. system signal System Signals-46#RCNT.nnn. system signals System Signals-46#RDB.MODE. system signal System Signals-46#RDN.ARRAY.NUM system signal Redundancy-

4#RDN.BACKUP.STAT system

signal Redundancy-2#RDN.BKSTAT.HILM system

signal Redundancy-4#RDN.LIST.NUM system signal Redundancy-4#RDN.ONLINE.UNIT system

signal Redundancy-2#RDN.RESET.DATA system signal Redundancy-

5#RDN.SWITCH.OVER system

signal Redundancy-5#RDNERR.. system signal System Signals-47#RDNLIM.. system signal System Signals-47#RTTIME.000. system signal System Signals-47#RTTIME.001. system signal System Signals-48#TIME.nnn. system signals System Signals-493308_NODE_TYPE keyword

in ATOOLS.INI file. See UOI ConfigurationManual (D5074)

AAARRAY_DB terminal

in IP_Server Module IP_Server-3AAT Module AAT-1ABORT Statement Abort-1ABS_DENS terminal

in EVP Module EVP-3Absolute Value ':ABS' operator

in Calculator Module equations Calculator-8ACCESS_MODE terminal

in IP_Client Module IP_Client-3

ACCOL II Reference ManualPage Index-2

ACCESS_TYPE terminalin IP_Client Module IP_Client-5

ACCOL Tools Initialization File. See ATOOLS.INIACOEFF terminal

in GSV Module GSV-6ACTIVE_1 terminal

in RBE Module RBE-13ACTIVE_2 terminal

in RBE Module RBE-13Add '+' operator

in Calculator Module equations Calculator-7ADDRESS keyword

in ATOOLS.INI ATOOLS-7ADDRESS terminal

in EMaster Module Master-4in Smart Module Smart-3in XMTR_Interface Module XMTR_Interface-

5Addressing. See Expanded Node Addressing,

Node Addressing; IP Node AddressingADJ_PRESS terminal

in AGA3 module AGA3-2in AGA3Iter module AGA3Iter-5in AGA3TERM module AGA3Term-2in AGA7 module AGA7-3in ISO5167 Module ISO5167-4

AGA3 Module AGA3-1AGA3Dens Module AGA3Dens-1AGA3Iter Module AGA3Iter-1AGA3TERM Module AGA3Term-1AGA5 Module AGA5-1AGA7 Module AGA7-1

using with AAT Module AAT-9AGA8 Module AGA8-1

reasons to use the FPV Module instead ofthe AGA8-2

setting priority of the AGA8 SystemTask AGA8-2

using with the CharacterizeModule Characterize-1

AGA8 system task priority Task-3AGA8Detail Module AGA8Detail-1

setting priority of the AGA8 SystemTask AGA8Detail-2

using with AGA3Iter Module AGA3Iter-2, AGA3Iter-4, AGA3Iter-8, AGA3Iter-12

AGA8Gross Module AGA8Gross-1setting priority of the AGA8 System

Task AGA8Gross-2using with AGA3Iter Module AGA3Iter-

2, AGA3Iter-4, AGA3Iter-12Alarm messages

#ALARM.FORMAT.001 system signal SystemSignals-3

Alarm Acknowlege ':AK:' operatorin Calculator Module equations Calculator-13

Alarm acknowlege system task priority Task-3Alarm enable

format descriptor for setting Formats-20Alarm inhibit

format descriptor for setting Formats-20Alarm inhibit ':AI:' operator

in Calculator Module equations Calculator-13Alarm inhibit/enable Signals-7Alarm Messages

#ALARM.FORMAT. system signal SystemSignals-3

Alarm OFF alarm type Signals-6Alarm ON alarm type Signals-6Alarm Priority Signals-7Alarm set ':AS' operator

in Calculator Module equations Calculator-13Alarm System Task priority Task-3ALARM terminal

in GBBTI and LBBTI modules BBTI-21Alarm Timestamp Buffers Buffers-2

scan rate of System Signals-3Alarms

collecting via Audit Trail modules Audit-1Allen-Bradley PLC Master and Slave

Interfaces. See ACCOL II Custom ProtocolsManual (document# D4066)

American Gas Association Modules. See GasModules

Analog cast ':A' operatorin Calculator Module equations Calculator-10

Analog constants Calculator-3Analog I/O Board Process I/O-5Analog input boards Process I/O-2Analog Inputs. See ANINAnalog Output Board Process I/O-2Analog Outputs. See ANOUTAnalog read/write data array

shifting columns of ausing the Encode Module Encode-23

Analog signalsvalid range for IEEE Signals-1

Analog valuesconverting to packed Julian date/time

using the Encode Module Encode-11converting to string characters

using Encode Module Encode-5converting to system date/time

using Encode Module Encode-17AND ' & ' operator

in Calculator Module logicalexpressions Calculator-8

ANIN Module ANIN-1questionable data for Ques Data-2

ANOUT Module ANOUT-1ARC_STORE Module ARC_STORE-1Archive files for historical data ARC_STORE-1ARCHIVE terminal

in ARC_STORE module ARC_STORE-5ARCHIVE_DB terminal

in IP_Server Module IP_Server-6ARRAY terminal

in AGA8 module AGA8-4in AGA8Detail module AGA8Detail-4in Characterize Module Characterize-3in EASTATUS Module EAStatus-7in Encode Module Encode-3, Encode-

6, Encode-9, Encode-12, Encode-15, Encode-18, Encode-23


in Function Module Function-1in HSANIN Module HSANIN-2in Nodestatus Module Nodestatus-5in Portstatus Module Portstatus-7in Redundancy Module Redundancy-4in Stepper Module Stepper-5in Storage Module Storage-3

Arrays. See Data ArraysARY_ACCESS terminal

in Nodestatus Module Nodestatus-6ASCII/analog value conversions

in Encode Module Encode-28ATOOLS.INI ATOOLS-1Audit Module Audit-1Audit Trail messages

nEL, EA, nEN format descriptors forretrieving Formats-15

Auto adjust turbine meter. See AAT ModuleAuto-dial Modem Interface

#DIAL.000. System Signals-16#DIAL.001. System Signals-17#DIAL.002. System Signals-17#DIAL.003. System Signals-17#DIAL.004. System Signals-18#DIAL.005. System Signals-18#DIAL.006. System Signals-18#DIAL.007. System Signals-19#DIAL.008. System Signals-19#DIAL.009. System Signals-19

Autodial interface for Pseudo Master(NETPROBE). See ACCOL II CustomProtocols Manual (document# D4066)

Aux1 and Aux2 Ports Commport-1Averager Module Averager-1

BBackspace data entry field (CB) format

descriptor Formats-25Base name text for ACCOL signals Signals-5BASE_DENS terminal

in AGA3Dens Module AGA3Dens-6in AGA7 module AGA7-4in GSV Module GSV-2in ISO5167 Module ISO5167-7

BASE_FLOW terminalin AGA3Dens Module AGA3Dens-7

BASE_PRESS terminalin AGA3 module AGA3-3in AGA3Iter module AGA3Iter-7in AGA3TERM module AGA3Term-3in AGA5 module AGA5-1in AGA7 module AGA7-3in AGA8 module AGA8-3in AGA8Detail module AGA8Detail-3in AGA8Gross module AGA8Gross-3

BASE_TEMP terminalin AGA3 module AGA3-3in AGA3Iter module AGA3Iter-7in AGA3TERM module AGA3Term-3in AGA5 module AGA5-2

in AGA7 module AGA7-3in AGA8 module AGA8-3in AGA8Detail module AGA8Detail-3in AGA8Gross module AGA8Gross-3

BATCH_MODE keywordin ATOOLS.INI. See UOI Configuration

Manual (D5074)Battery low/fail indication

in RIO 3331 RIOSTATS-2Battery power status

in GFC 3308, RTU 3305checking using the EncodeModule Encode-21

Baud ratedefault settings for ACCOL Tools on

PC ATOOLS-2Baud rates for Network 3000

Controllers Commport-22BAUD_RATE terminal

in Portstatus Module Portstatus-7BAUDRATE keyword

in ATOOLS.INI file ATOOLS-2BBMSCT table GPA8173-7BBTI Board Process I/O-5BBTI Modules BBTI-1

questionable data for Ques Data-5BCOEFF terminal

in GSV Module GSV-6Block size (SB) format descriptor Formats-23Boolean operators. See Calculator ModuleBREAK statement Break-1Bristol Molecular Specie Constants Table

( GPA8173-7Buffers Buffers-1

Alarm Timestamp Buffers-2I/O Buffers-1

Built-in Ports (BIP 1 & BIP 2) Commport-4

CCalculator Module Calculator-1

questionable data bit and the Ques Data-5CALIB_FACTR terminal

in AGA7 module AGA7-5Cancel cell repeat mode (DN) format

descriptor Formats-17Cast operators - logical, analog, and string

in Calculator Modules Calculator-10CAT_INIT_MODEM keyword

in ATOOLS.INI file ATOOLS-5CBO Board Process I/O-2CBO I/O system task priority Task-3CCF terminal

in GSV Module GSV-7CFE Port

error statistics reported for IEEE interfacein Portstatus Module Portstatus-15

CFGSTAT terminalin GBBTI and LBBTI modules BBTI-23in HWSTI Module HWSTI-17

Change of state alarm type Signals-6


CHANNEL terminalin GBBTI and LBBTI modules BBTI-11in HWSTI Module HWSTI-7in Watchdog Module Watchdog-2in XMTR_Interface Module XMTR_Interface-

2Characterize Module Characterize-1

using with AGA8 AGA8-1, AGA8-7CI_SECURITY keyword

in ATOOLS.INI ATOOLS-6CIM Module (TANO Slave). See ACCOL II

Custom Protocols Manual (document#D4066)

CJTACT terminalin HWSTI Module HWSTI-21

Clear Data Entry Field (CC) formatdescriptor Formats-26

CLNT_COUNT terminalin IP_Client Module IP_Client-7

CLNT_INDEX terminalin IP_Client Module IP_Client-6

CLNT_SELECT terminalin IP_Client Module IP_Client-7

CLNT_STRUCT_NO terminalin IP_Client Module IP_Client-6

Clock failure, Real Timein RIO 3331 RIOSTATS-2

CNG Port. See Columbia Natural Gas PortCNGMASTER Module. See ACCOL II Custom

Protocols Manual (document# D4066)CNGSLAVE Module. See ACCOL II Custom

Protocols Manual (document# D4066)CO2_MOLE terminal

in FPV Module FPV-2Cold Start Downloading-2COLOR keyword

in ATOOLS.INI ATOOLS-2Columbia Natural Gas Modules. See ACCOL II


Columbia Natural Gas Port Commport-18COLUMN terminal

in AGA8 module AGA8-4in AGA8Detail module AGA8Detail-4in Characterize Module Characterize-3in Function Module Function-1in Nodestatus Module Nodestatus-7in Portstatus Module Portstatus-7in Storage Module Storage-2

COM1: or COM2: setting for ACCOLTools ATOOLS-1

COMERRS terminalin HWSTI Module HWSTI-25

COMMAND Module Command-1COMMAND terminal

in Command Module Command-1in HWSTI Module HWSTI-7in LCBO Module LCBO-12

Comment 'C' Statement Comment-1Comment statements

in Calculator Modules Calculator-15Communication

using Logger Module Logger-1Communication buffers. See BuffersCommunication Ports Commport-1

#DIAL.nnn. system signals System Signals-16

#LINKE.nnn. and #LINKF.nnn. systemsignals System Signals-29

#NDARRAY.. system signal System Signals-31

#NODE.nnn failure for slaves on a MasterPort System Signals-34

#POLLPER.nnn. system signals SystemSignals-38

and the Portstatus Module Portstatus-1collecting statistics on operation of. See

Portstatus ModuleFailure indication via #LINE.nnn. system

signals System Signals-28notes about Expanded Node Addressing

and Expanded Node-11setting a default PC port for ACCOL tools to

use ATOOLS-1Communication protocols

using Custom Module Custom-1Communications

node addressing Node Addressing1using Master/EMaster and Slave

modules Master/Slave-1using Master/EMaster Modules Master-1using Slave Module Slave-1

Communications poll system task priority Task-4Comparator Module Comparator-1COMPLIQSTATE terminal

in EVP Module EVP-4Component order

in AGA8Detail module AGA8Detail-6Component order and percent requirements

for AGA8 module AGA8-7COMPVAPORPRESS terminal

in EVP Module EVP-4Concatenation ':CON:' operator for strings

in Calculator Module Calculator-8Constants Calculator-3Continue Array Mode (DC) format

descriptor Formats-17Control inhibit ':CI:' operator

in Calculator Module equations Calculator-13Control inhibit/enable Signals-4Control Statements Control Stmts-1

ABORT Abort-1BREAK Break-1ELSE IF-1ELSEIF IF-1ENDFOR FOR-1ENDIF IF-1FOR FOR-1GOTO GOTO-1IF IF-1RESUME Resume-1RWAIT DI WAIT DI-1RWAIT DIH WAIT DI-1RWAIT DIL WAIT DI-1


SUSPEND Suspend-1WAIT DELAY Wait Delay-1WAIT DI WAIT DI-1WAIT DIH WAIT DI-1WAIT DIL WAIT DI-1WAIT FOR WAIT FOR-1WAIT_TIME WAIT TIME-1

Cosine ':COS' operatorin Calculator Module equations Calculator-8

COUNT terminalin Counter Modules Counters-6in Smart Module Smart-3in XMTR_Interface Module XMTR_Interface-

6COUNT_SPAN terminal

in Counter Modules Counters-7COUNT_ZERO terminal

in Counter Modules Counters-7COUNT1 terminal

in AAT Module AAT-2COUNT2 terminal

in AAT Module AAT-3Counter Modules Counters-1CPL terminal

in GSV Module GSV-6Critical Alarm priority Signals-7CSW terminal

in GSV Module GSV-7CTL terminal

in GSV Module GSV-6CUR_T_DAY terminal

in ETOT/TRND Module ETOT/TRND-5in TOT/TRND Module TOT/TRND-5

CUR_T_HOUR terminalin ETOT/TRND Module ETOT/TRND-5in TOT/TRND Module TOT/TRND-5

CUR_T_MONTH terminalin ETOT/TRND Module ETOT/TRND-5in TOT/TRND Module TOT/TRND-5

CUR_T_SHIFT terminalin ETOT/TRND Module ETOT/TRND-5in TOT/TRND Module TOT/TRND-5

CURMETERVAL terminalin GSV Module GSV-4

Cursor positioning descriptors Formats-30CUSTCONSTARRY terminal

in GPA8173 Module GPA8173-3Custom Module Custom-1Custom Module system task priority Task-3Custom Port Commport-19

changing characteristics ofusing Portstatus Module Portstatus-11

CUSTOM_1 terminalin Portstatus Module Portstatus-9

CUSTOM_2 terminalin Portstatus Module Portstatus-9

DDaccumulator Module Daccumulator-1DAMPING terminal

in HWSTI Module HWSTI-19Data Arrays Data Arrays-1

and the Storage Module Storage-5expressions in Calculator

Modules Calculator-4Format descriptors for Formats-27Format descriptors for retrieving data

from Formats-16referencing using the Function

Module Function-2shifting columns of a

using Encode Module Encode-23Data specifier (SD) format descriptor Formats-22Date

format descriptor for setting Formats-26SD format descriptor Formats-22

Date (#TIME.nnn) system signals SystemSignals-49

Date ACO file generated#LOAD.. system signal System Signals-31

Date/Timeconverting packed Julian date and time

to analog values using EncodeModule Encode-8

Date/Time, packed Juliancreating from analog values

using the Encode Module Encode-11Date/Time, system

converting to analog valuesusing Encode Module Encode-14

specifying using analog valueswith the Encode Module Encode-17

DAY_SPAN terminalin ETOT/TRND Module ETOT/TRND-3in TOT/TRND Module TOT/TRND-3

DEADBAND terminalin Comparator Module Comparator-2in PDM/RPDM modules PDM-7in PID3TERM Module PID3TERM-2

Deadbands for alarms Signals-8DECONF terminal

in HWSTI Module HWSTI-19Defaults

for ACCOL Tools operation. See ATOOLS.INIDefine analog array (DA) format

descriptor Formats-16Define Logical Array (DL) format

descriptor Formats-16Define special input mode (CI) format

descriptor Formats-24DELAY terminal

in Command Module Command-2in HCBO Module HCBO-2in LCBO Module LCBO-14

DEMUX Module Demux-1DENS_SWITCH terminal

in AGA7 module AGA7-2DENSITY terminal

in ISO5167 Module ISO5167-7DERIVATIVE terminal

in ETOT/TRND Module ETOT/TRND-5in Lead/Lag Module Lead/Lag-1


in PID3TERM Module PID3TERM-3in TOT/TRND Module TOT/TRND-5

DEVICE terminalin ANIN module ANIN-2in ANOUT module ANOUT-2in DIGIN Module Digin-2in DIGOUT Module Digout-2in GBBTI and LBBTI modules BBTI-10in HCBO Module HCBO-2in HSANIN Module HSANIN-1in HSCOUNT, LSCOUNT modules Counters-

3in HWSTI Module HWSTI-6in ISO5167 Module ISO5167-5in LCBO Module LCBO-11in LLANIN Module LLANIN-2in PDM Module PDM-2in PDO Module PDO-2in RANIN module ANIN-3in RANOUT module ANOUT-3in RDIGIN Module Digin-3in RDIGOUT Module Digout-3in RHSCOUNT/RLSCOUNT

modules Counters-4in RLLANIN Module LLANIN-3in RPDM Module PDM-3in RPDO Module PDO-3in Watchdog Module Watchdog-2in XMTR_Interface Module XMTR_Interface-

1DEVICE2 terminal

in ISO5167 Module ISO5167-5DGP terminal

in GBBTI and LBBTI modules BBTI-12DGPSUB terminal

in GBBTI and LBBTI modules BBTI-14in TCheck Module TCheck-5

DGPU terminalin GBBTI and LBBTI modules BBTI-13

Diagnostic arrays System Signals-5DIAL keyword

in ATOOLS.INI ATOOLS-6Dial string

setting a default phone number inATOOLS.INI ATOOLS-5

Dial-up feature. See Auto-dial Modem InterfaceDialing mode (tone or pulse)

setting default in ATOOLS.INI ATOOLS-6DIFF_PRESS terminal

in AGA3 Module AGA3-1in AGA3Dens Module AGA3Dens-3in AGA3Iter module AGA3Iter-4in AGA3TERM module AGA3Term-1in ISO5167 Module ISO5167-3

Differentiator Module Differentiator-1DIGIN Module Digin-1Digital Inputs. See DIGIN ModuleDigital outputs. See DIGOUT ModuleDigitial I/O board Process I/O-5DIGOUT Module Digout-1DIRECTION terminal

in Stepper Module Stepper-2

Discrete Input Board Process I/O-2Discrete inputs. See DIGIN ModuleDiscrete Output Board Process I/O-3Discrete outputs. See DIGOUT ModuleDisplay current cell's column (DX)

format descriptor Formats-19Display current cell's row (DY) format

descriptor Formats-18Display Julian date (JD) format

descriptor Formats-29Display Julian Time (JT) format

descriptor Formats-29Divide '/' operator

in Calculator Module equations Calculator-7DONE terminal

in HSANIN Module HSANIN-7in HWSTI Module HWSTI-11in Logger Module Logger-3

Double-precision floating pointnumbers Daccumulator-1

DOWNLOAD_LEVEL keywordin ATOOLS.INI ATOOLS-8

Downloadingan ACCOL load file into the

controller Downloading-1notes about Expanded Node Addressing

and Expanded Node-11specifying a default security level required

for ATOOLS-8DTR ON/OFF control

using Portstatus Module Portstatus-5DTR status

using Portstatus Module Portstatus-6DUPLEX terminal

in Portstatus Module Portstatus-8Dyadic operators

in Calculator Module equations Calculator-7

EEAMaster Port Commport-12, Expanded Node-4


Setting Poll Period for System Signals-38EASTATUS Module EAStatus-1

in Expanded Node Addressing ExpandedNode-4

EAStatus Moduleusing with Expanded Node

Addressing Expanded Node-4EAudit Module Audit-1EDEMUX Module Demux-1EIntegrator Module EIntegrator-1Element repeat (SR) format descriptor Formats-

19Element reset (SJ) format descriptor Formats-20Element skip (SS) format descriptor Formats-19ELSE statement IF-1ELSEIF statement IF-1EMaster Module Master-1EMUX Module MUX-1


ENABLE terminalin AGA8 module AGA8-2in AGA8Detail module AGA8Detail-2in AGA8Gross module AGA8Gross-2in LCBO Module LCBO-13in PDO/RPDO modules PDO-8in Slave Module Slave-1in Watchdog Module Watchdog-3

Encode Module Encode-1End Array Mode (DE) format

descriptor Formats-17ENDFOR statement FOR-1ENDIF statement IF-1ENERGY_CONV terminal

in AGA5 module AGA5-3Enron Modbus Slave Interface. See ACCOL II


Enter data entry value (CE) formatdescriptor Formats-26

Equality ':EQ:' string operatorin Calculator Module equations Calculator-8

Equals '==' operatorin Calculator Module equations Calculator-8

Equation for Averager module Averager-3Equation for EIntegrator Module EIntegrator-3Equation for Integrator Module Integrator-3Equation for ISO5167 Module ISO5167-2Equation for Lead/Lag Module Lead/Lag-5Equation for PID3TERM Module PID3TERM-5Equations

creating using the CalculatorModule Calculator-1

Equations for AGA3 gas flow AGA3-5Equations for AGA3Iter Module AGA3Iter-3Equations for AGA5 module AGA5-4Equations for AGA7 module AGA7-6Equations for FPV Module FPV-2Equipment run time

and the Scheduler Module Scheduler-1EQUIVVOL terminal

in GPA8173 Module GPA8173-4EQUIVVOLSTRUCT terminal

in GPA8173 Module GPA8173-4EQVAPRESS terminal

in GSV Module GSV-3Error Reporting Error Report-1ERROR terminal

in AGA8 module AGA8-5in AGA8Detail module AGA8Detail-4in AGA8Gross module AGA8Gross-6in Characterize Module Characterize-3in PID3TERM Module PID3TERM-5in Watchdog Module Watchdog-5

ERROR_CLEAR terminalin HCBO Module HCBO-3

ERRORCNT terminalin GBBTI and LBBTI modules BBTI-24in TCheck Module TCheck-7

ErrorsCommunication Line (#LINE...) system

signals System Signals-28

Communication Link System Signals-29in communication from slave nodes

reported via #NODE.nnn systemsignals System Signals-34

in Process I/O Boards. See Process I/Opausing system in order to view ATOOLS-4

EST terminalin GBBTI and LBBTI modules BBTI-18

ESTSUB terminalin GBBTI and LBBTI modules BBTI-19in TCheck Module TCheck-6

ESTU terminalin GBBTI and LBBTI modules BBTI-19

ETOT/TRND Module ETOT/TRND-1Event alarm priority Signals-7Events

collecting via Audit Trail Modules Audit-1in Audit Trail usage

defined Audit-2EVP Module EVP-1Exclusive OR 'EXCL OR' operator


Execute subformat (SF) formatdescriptor Formats-22

Expanded Addressing system task priority Task-4

Expanded BSAP. See Expanded Node AddressingExpanded Memory

amount required for Expanded NodeAddressing Expanded Node-4

Expanded Node Addressing Expanded Node-1and the EASTATUS Module EAStatus-1EAMaster Port Commport-12Poll periods and System Signals-38restrictions on defining the group

number Expanded Node-5setting default group # in

ATOOLS.INI ATOOLS-8Exponential (#E..) system signal System Signals-

20Exponential (Ew.d) format descriptor Formats-7Exponential ':EXP' operator

in Calculator Module equations Calculator-8

FFAIL_OPTION terminal

in Redundancy Module Redundancy-5in Watchdog Module Watchdog-4

FAIL_STATE terminalin Keyboard Module Keyboard-4in Scheduler Module Scheduler-3in Watchdog Module Watchdog-4

Failover. See Redundancy ModuleFixed point (Fw.d) format descriptor Formats-5Floating point - single or double

in Averager module Averager-1Floating point numbers

using Daccumulator to work withdouble-precision Daccumulator-1


FLOW_DENS terminalin AGA3Dens Module AGA3Dens-6in AGA7 module AGA7-4

FLOW_PRESS terminalin AGA7 module AGA7-2in EVP Module EVP-2in GSV Module GSV-3

FLOW_SWITCH terminalin AGA7 module AGA7-1

FLOW_TEMP terminalin AGA3 module AGA3-3in AGA3Dens Module AGA3Dens-5in AGA3Iter module AGA3Iter-7in AGA3TERM module AGA3Term-3in AGA7 module AGA7-2in AGA8 module AGA8-3in AGA8Detail module AGA8Detail-2in AGA8Gross module AGA8Gross-3in EVP Module EVP-2in FPV Module FPV-1in GSV Module GSV-3in ISO5167 Module ISO5167-6

FOR statement FOR-1using a BREAK to exit from a Break-1

Format descriptorsCB backspace data entry field Formats-25CC clear data entry field Formats-26CD set system date Formats-26CE enter data entry field Formats-26CI define special input mode Formats-24CL lower current signal or cell value by

percent. Formats-27CQ terminate special input loop Formats-27CR Raise current signal or value by

percentage Formats-26CT set system time Formats-26cursor positioning commands Formats-30CX set array column Formats-27CY set data array row Formats-27DA define analog array Formats-16DC continue array mode Formats-17DE end array mode Formats-17DJ jump to first cell Formats-18DL define logical array Formats-16DN cancel cell repeat mode Formats-17DR set cell repeat mode Formats-17DS skip array cell Formats-17DSB skip array cell backwards Formats-18DW set cell wrap around mode Formats-18DX display current cell's column Formats-19DY display current cell's row Formats-18EA audit trail Formats-15Ew.d Exponential Formats-7Fw.d fixed point Formats-5Iw Integer Formats-6JD display Julian date Formats-29JT display Julian time Formats-29KKx(fx).. key code Formats-13Kx conditional Formats-12Ln Logical Formats-8M n:m Message command Formats-14nEL audit trail Formats-15

nEN audit trail Formats-15nQ Q format Formats-15Nxn signal name Formats-10P position cursor Formats-30PA set terminal type to ANSI Formats-30PV set terminal type to VT52 Formats-30SAE set alarm enable Formats-20SAI set alarm inhibit Formats-20SB block size Formats-23SCE set control enable Formats-21SCI set control inhibit Formats-21SD date specifier Formats-22SE terminate repeat Formats-20SF execute sub-format Formats-22signal indirection descriptors Formats-31

ASCII control characters Formats-34end of line indicate Formats-33I/O directional commands Formats-32nest delimiters Formats-32positioning and structuringcommands Formats-31separators Formats-32space command Formats-33text delimiters Formats-33

SJ element reset Formats-20SME set manual enable Formats-21SMI set manual inhibit Formats-21Special Input Error Messages Formats-28SR element repeat Formats-19SS element skip Formats-19SSB signal skip backwards Formats-20ST time specifier Formats-21SW signal wrap around mode Formats-20Tn String Formats-9Uw signal units Formats-11

FORMAT terminalin Logger Module Logger-2in RBE Module RBE-11in Smart Module Smart-2in XMTR_Interface Module XMTR_Interface-

3Formats

for ASCII data Formats-1using with Audit Trail modules Audit-9

FPV Module FPV-1reasons to use instead of AGA8 AGA8-2using with AGA3 Module AGA3-3

FPV terminalin AGA8 module AGA8-6in AGA8Detail module AGA8Detail-6in AGA8Gross module AGA8Gross-7

FPV_IN terminalin AGA3 module AGA3-3in AGA3TERM module AGA3Term-3in AGA5 module AGA5-2in AGA7 module AGA7-3

FREQ_SPAN terminalin Counter Modules Counters-8

FREQ_ZERO terminalin Counter Modules Counters-8

FREQ1 terminalin AAT Module AAT-2


FREQ2 terminalin AAT Module AAT-2

FREQ6050 terminalin HWSTI Module HWSTI-22

Frequency rangesof Counter Modules Counters-2

FREQUENCY terminalin Counter Modules Counters-8in HSANIN Module HSANIN-4

FULL_ALARM terminalin Audit/EAudit modules Audit-4

Function Module Function-1

GGas Modules

AGA3 AGA3-1AGA3Dens AGA3Dens-1AGA3Iter AGA3Iter-1AGA3Term AGA3Term-1AGA5 AGA5-1AGA7 AGA7-1AGA8 AGA8-1AGA8Detail AGA8Detail-1AGA8Gross AGA8Gross-1Characterize Characterize-1FPV FPV-1ISO5167 ISO5167-1

GBBTI Module BBTI-1questionable data for Ques Data-5

GBBTI Smartkit system task priority Task-4Global characteristic for ACCOL signals Signals-

6Global downloading Downloading-1GOTO statement GOTO-1Gould Modbus Master/Slave Interface. See

ACCOL II Custom Protocols Manual(document# D4066)

GPA8173 Module GPA8173-1GRAV_PRESS terminal

in AGA7 module AGA7-5GRAV_TEMP terminal

in AGA7 module AGA7-4Greater than '>' operator

in Calculator Module equations Calculator-7Greater than or equal to '>=' operator

in Calculator Module equations Calculator-8GROUP keyword

in ATOOLS.INI file ATOOLS-8Group number. See Expanded Node AddressingGSV Module GSV-1GSV terminal

in GSV Module GSV-7

HHANDSHAKE terminal

in Portstatus Module Portstatus-8HCBO Module HCBO-1HCBO system task priority Task-3HEAT_VALUE terminal

in AGA8Gross module AGA8Gross-4in Characterize Module Characterize-2

High Alarm Acknowledge ':HK:' operatorin Calculator Module equations Calculator-13

High Alarm Set ':HS:' operatorin Calculator Module equations Calculator-13

High High Alarm Acknowledge ':HHK:' operatorin Calculator Module equations Calculator-13

High High Alarm Set ':HHS' operatorin Calculator Module equations Calculator-13

High Speed Analog Input Board Process I/O-3High Speed Counter Board Process I/O-3HIGH_LIMIT terminal

in HILOLIMITER Module HILOLIMITER-1in PDO/RPDO modules PDO-10

HILOLIMITER Module HILOLIMITER-1HILOSELECT Module HILOSELECT-1Historical data

and the Storage Module Storage-7collecting using ARC_STORE

module ARC_STORE-1using Audit Trail Modules to collect alarms/

events Audit-1HOLD_OFF terminal

in Stepper Module Stepper-1Honeywell Smartline Transmitter Interface. See

HWSTI ModuleHoneywell Smartline XMTR Interface

Board Process I/O-5HOUR_SPAN terminal

in ETOT/TRND Module ETOT/TRND-3in TOT/TRND Module TOT/TRND-3

HSANIN Module HSANIN-1HSANIN system task priority Task-4HSCOUNT Module Counters-1

using with AGA7 Module AGA7-1, AGA7-3HWSTI Module HWSTI-1

questionable data for Ques Data-5

II/O. See Process I/O or Communication PortsI/O Buffers Buffers-1IEEE 488 Interface Commport-2IEEE floating point numbers Daccumulator-1IF statement IF-1Inclusive OR 'INCL OR' operator


INDEX terminalin Encode Module Encode-4, Encode-


in HSANIN Module HSANIN-5in Master/EMaster modules Master-6in Smart Module Smart-3in Stepper Module Stepper-2in Storage Module Storage-3in XMTR_Interface Module XMTR_Interface-

6INIT terminal


in GSV Module GSV-5Initial state of ACCOL signal Signals-4INITIAL terminal

in ANIN/RANIN modules ANIN-4in ANOUT/RANOUT modules ANOUT-4in Counter Modules Counters-5in DIGIN, RDIGIN modules Digin-4in DIGOUT, RDIGOUT modules Digout-4in HCBO Module HCBO-2in HSANIN Module HSANIN-2in LLANIN/RLLANIN modules LLANIN-4in PDM/RPDM modules PDM-4in PDO/RPDO modules PDO-4

Initialization file. See ATOOLS.INIInitialization strings for modems ATOOLS-4INLIST terminal

in HILOSELECT Module HILOSELECT-2in Master/EMaster modules Master-6in MUX/EMUX modules MUX-1in Slave Module Slave-2in TCheck Module TCheck-3in VMUX Module VMUX-3

INPUT n terminalsin the Keyboard Module Keyboard-5

INPUT terminalin ANIN/RANIN modules ANIN-5in Averager Module Averager-1in Comparator Module Comparator-2in DEMUX, EDEMUX modules Demux-1in Differentiator Module Differentiator-1in DIGIN, RDIGIN modules Digin-5in EIntegrator Module EIntegrator-1in Encode Module Encode-4, Encode-


in ETOT/TRND Module ETOT/TRND-1in HILOLIMITER Module HILOLIMITER-1in Integrator Module Integrator-1in Lead/Lag Module Lead/Lag-1in LLANIN/RLLANIN modules LLANIN-5in PDM/RPDM modules PDM-9in PDO/RPDO modules PDO-10in PID3TERM Module PID3TERM-1in Sequencer Module Sequencer-2in Storage Module Storage-5in Timer Module Timer-1in TOT/TRND Module TOT/TRND-1in VLIMITER Module Vlimiter-2

INPUT_1 terminalin AGA3Iter module AGA3Iter-10



INPUT_HIGH terminalin Daccumulator Module Daccumulator-3

INPUT_LIST terminalin Liquid_Density Module Liquid_Density-2

INPUT_LOW terminalin Daccumulator Module Daccumulator-4

INPUT_n terminalsin AGA3TERM module AGA3Term-5

in EMUX Module MUX-1in HILOSELECT Module HILOSELECT-2in VMUX Module VMUX-3

Integer (Iw) format descriptor Formats-6Integer ':INT' truncate operator

in Calculator Module equations Calculator-8INTEGRAL terminal

in Lead/Lag Module Lead/Lag-2in PID3TERM Module PID3TERM-3

Integrator Module Integrator-1Internet_Protocol Module Internet-1INTYPE terminal

in Master/EMaster modules Master-5in Slave Module Slave-2

IP Node Addressing IPAddr-1IP_Client Module IP_Client-1IP_Server Module IP_Server-1ISEN_COEF terminal

in AGA3Dens Module AGA3Dens-5in AGA3Iter module AGA3Iter-8in ISO5167 Module ISO5167-6

ISO5167 Module ISO5167-1IVMULTI terminal

in GSV Module GSV-4

JJulian Date/Time

format descriptors for displaying Formats-29Julian date/time, packed


Jump to first cell (DJ) formatdescriptor Formats-18

KKey code KKx(fx):y(fy)..

conditional format descriptor Formats-13Keyboard Module Keyboard-1Keyboard Module system task priority Task-4KNOWN_IP_NODES terminal

in IP_Server Module IP_Server-6

LLARRAY_DB terminal

in IP_Server Module IP_Server-4LBBTI Module BBTI-1

questionable data for Ques Data-5LCBO Module LCBO-1Lead/Lag Module Lead/Lag-1Less than '<' operator

in Calculator Module equations Calculator-7Less than or equal to '<=' operator

in Calculator Module equations Calculator-8Line errors, communication System Signals-28Link errors, communication System Signals-29Liquid flow rates

calculating using the ISO5167


Module ISO5167-9Liquid Measurement

Guidelines Liquid_Measure-1Liquid Measurement Modules

AGA3Dens AGA3Dens-1EVP EVP-1GPA8173 GPA8173-1GSV GSV-1Liquid_Density Liquid_Density-1

Liquid_Density Module Liquid_Density-1LIQUIDTYPE terminal

in EVP Module EVP-2in GSV Module GSV-1

LIQUIDVALID terminalin GSV Module GSV-2

LIST terminalin AGA3Dens Module AGA3Dens-7in AGA3Iter module AGA3Iter-10in AGA3TERM module AGA3Term-5in AGA8 module AGA8-3in AGA8Detail module AGA8Detail-3in Audit/EAudit modules Audit-6in Characterize Module Characterize-3in EASTATUS Module EAStatus-6in Encode Module Encode-2, Encode-


in Internet_Protocol Module Internet-2in ISO5167 Module ISO5167-8in Keyboard Module Keyboard-2in Logger Module Logger-3in Nodestatus Module Nodestatus-5in Portstatus Module Portstatus-6in Redundancy Module Redundancy-4in Smart Module Smart-3in Storage Module Storage-5in XMTR_Interface Module XMTR_Interface-

6LIST_DB terminal

in IP_Server Module IP_Server-2LIST1 terminal

in AAT Module AAT-3LIST2 terminal

in AAT Module AAT-4LIST3 terminal

in AAT Module AAT-5Lists. See Signal ListsLIU Master Port Commport-1

error statistics reported in PortstatusModule Portstatus-14

LIU Slave Port Commport-1error statistics reported in Portstatus

Module Portstatus-16LLANIN Module LLANIN-1

questionable data for Ques Data-3Local address

#NODEADR.. system signal System Signals-34

specifying default for ACCOL toolsin ATOOLS.INI ATOOLS-7

Local characteristic for ACCOL signals Signals-6Local downloading Downloading-1

Logarithm ':LOG' operator inCalculator Module equations Calculator-8

Logger Module Logger-1using with Audit Trail modules Audit-9using with Formats Formats-1

Logger Module system task priority Task-4Logger Port Commport-14

changing characteristics ofusing Portstatus Module Portstatus-11

Logical (Ln) format descriptor Formats-8Logical alarm type Signals-6Logical cast ':L' operator

in Calculator Module equations Calculator-10Logical constants Calculator-3Logical NOT '~' operator for logical signals

in Calculator Module expressions Calculator-8

Logical Signals Signals-1Low Alarm Acknowledge ':LK:' operator

in Calculator Module equations Calculator-13Low Alarm Set ':LS:' operator

in Calculator Module equations Calculator-13Low Level Board Process I/O-5Low Low Alarm Acknowledge ':LLK:' operator

in Calculator Module equations Calculator-13Low Low Alarm Set ':LLS:' operator

in Calculator Module equations Calculator-13Low-Level Board input types LLANIN-7LOW_LIMIT terminal

in HILOLIMITER Module HILOLIMITER-2in PDO/RPDO modules PDO-10

Lower current value by percentage (CL)format descriptor Formats-27

LRL terminalin HWSTI Module HWSTI-23

LRV terminalin HWSTI Module HWSTI-23

LSCOUNT Module Counters-1using with AGA7 Module AGA7-1, AGA7-3

MManual enable

format descriptor for setting Formats-21Manual inhibit

format descriptor for setting Formats-21Manual inhibit ':MI:' operator

in Calculator Module equations Calculator-13Manual inhibit/enable Signals-4Manual panels for 3350/3380/3385 ANOUT-

5, ANOUT-6, Digout-6MASS_FLOW terminal

in AGA3Dens Module AGA3Dens-7Master communications system task

priority Task-4Master Module Master-1

using with TCheck Module TCheck-1Master Module system task priority Task-3Master Port Commport-10



#NODE.nnn errors from slave nodes SystemSignals-34

Error statistics reported in PortstatusModule Portstatus-13

Setting Poll Period for System Signals-38Master/Slave Communications Master/Slave-1

node addressing Node Addressing1Setting Poll Periods System Signals-38Slave Module Slave-1

Mathematical modulesAverager Averager-1Calculator Calculator-1Comparator Comparator-1Daccumulator Daccumulator-1Differentiator Differentiator-1EIntegrator EIntegrator-1ETOT/TRND ETOT/TRND-1Function Function-1HILOLIMITER HILOLIMITER-1HILOSELECT HILOSELECT-1Integrator Integrator-1

MAX_TIME terminalin PDO/RPDO modules PDO-9in Watchdog Module Watchdog-3

MemoryAdding additional communication

buffers Buffers-1downloading an ACCOL load into FLASH or

RAM Downloading-5Message M n:m format descriptor Formats-14MESSAGE terminal

in RBE Module RBE-14METERFACTOR terminal

in GSV Module GSV-4METERMASS terminal

in GPA8173 Module GPA8173-1METERPRESSDROP terminal

in EVP Module EVP-3METERROLLOVER terminal

in GSV Module GSV-4MI_SECURITY keyword

in ATOOLS.INI ATOOLS-6MIN_TIME terminal

in PDO/RPDO modules PDO-8in Watchdog Module Watchdog-4

MISMATCH terminalin HWSTI Module HWSTI-16

Mixed I/O Board Process I/O-5Modbus Interface (Enron, Gould). See ACCOL II


MODE terminalin AGA8Gross module AGA8Gross-2in ARC_STORE module ARC_STORE-5in Audit/EAudit Modules Audit-3in Characterize Module Characterize-1in Comparator Module Comparator-1in Daccumulator Module Daccumulator-4in Encode Module Encode-3, Encode-


in GBBTI and LBBTI modules BBTI-11

in Internet_Protocol Module Internet-1in LCBO Module LCBO-12in Liquid_Density Module Liquid_Density-2in Logger Module Logger-2in Master/EMaster modules Master-4in PDO/RPDO modules PDO-6in Portstatus Module Portstatus-3in RBE module RBE-8in Scheduler Module Scheduler-2in Smart Module Smart-1in Watchdog Module Watchdog-3in XMTR_Interface Module XMTR_Interface-

2MODEM keyword

in ATOOLS.INI ATOOLS-2Modems

initialization strings forin ATOOLS.INI file ATOOLS-4

setting a default phone number inATOOLS.INI ATOOLS-5

setting dial or pulse mode inATOOLS.INI ATOOLS-6

Modules#ERARRAY.. for reporting errors in

tasks System Signals-20AAT AAT-1AGA3 AGA3-1AGA3Dens AGA3Dens-1AGA3Iter AGA3Iter-1AGA3TERM AGA3Term-1AGA5 AGA5-1AGA7 AGA7-1AGA8 AGA8-1AGA8Detail AGA8Detail-1AGA8Gross AGA8Gross-1ANIN ANIN-1ANOUT ANOUT-1ARC_STORE ARC_STORE-1Audit Audit-1Averager Averager-1Calculator Calculator-1Characterize Characterize-1CIM. See See ACCOL II Custom Protocols

Manual (D4066)CNGMaster. See See ACCOL II Custom

Protocols Manual (D4066)CNGSlave. See See ACCOL II Custom

Protocols Manual (D4066)Command Command-1Comparator Comparator-1Custom Custom-1Daccumulator Daccumulator-1DEMUX Demux-1Differentiator Differentiator-1DIGIN Digin-1DIGOUT Digout-1EASTATUS EAStatus-1EAudit Audit-1EDEMUX Demux-1EIntegrator EIntegrator-1EMaster Master-1EMUX MUX-1


Encode Encode-1ETOT/TRND ETOT/TRND-1EVP EVP-1FPV FPV-1Function Function-1GBBTI BBTI-1GPA8173 GPA8173-1GSV GSV-1HCBO HCBO-1HILOLIMITER HILOLIMITER-1HILOSELECT HILOSELECT-1HSANIN HSANIN-1HSCOUNT Counters-1HWSTI HWSTI-1Integrator Integrator-1Internet_Protocol Internet-1IP_Client IP_Client-1IP_Server IP_Server-1ISO5167 ISO5167-1Keyboard Keyboard-1LBBTI BBTI-1LCBO LCBO-1Lead/Lag Lead/Lag-1Liquid_Density Liquid_Density-1LLANIN LLANIN-1Logger Logger-1LSCOUNT Counters-1Master Master-1MUX MUX-1Nodestatus Nodestatus-1PDM PDM-1PDO PDO-1PID3TERM PID3TERM-1Portstatus Portstatus-1RANIN ANIN-1RANOUT ANOUT-1RBE RBE-1RDIGIN Digin-1RDIGOUT Digout-1Redundancy Redundancy-1RHSCOUNT Counters-1RIOSTATS RIOSTATS-1RLLANIN LLANIN-1RLSCOUNT Counters-1RPDM PDM-1RPDO PDO-1Scheduler Scheduler-1Sequencer Sequencer-1Slave Slave-1Smart Smart-1Stepper Stepper-1Storage Storage-1SYS_3530 SYS_3530-1System System-1System0 System0-1TCheck TCheck-1TCOUNT Counters-1Timer Timer-1TOT/TRND TOT/TRND-1VLIMITER Vlimiter-1VMUX VMUX-1Watchdog Watchdog-1

XMTR_Interface XMTR_Interface-1MOLE_%_CO terminal

in AGA8Gross module AGA8Gross-5MOLE_%_CO2 terminal

in AGA8Gross module AGA8Gross-5in Characterize Module Characterize-2

MOLE_%_H2 terminalin AGA8Gross module AGA8Gross-5

MOLE_%_METH terminalin Characterize Module Characterize-2

MOLE_%_N2 terminalin AGA8Gross module AGA8Gross-5in Characterize Module Characterize-2

MOLEFRACTSTRUCT terminalin GPA8173 Module GPA8173-3

Monadic operatorsin Calculator Module Calculator-9

Monitorcolor defaults for ACCOL tools ATOOLS-2

MONTH_SPAN terminalin ETOT/TRND Module ETOT/TRND-3in TOT/TRND Module TOT/TRND-3

Multi-function I/O board Process I/O-6Multiply ' * ' operator

in Calculator Module equations Calculator-7MUX Module MUX-1

NNAME keyword

in ATOOLS.INI. See UOI ConfigurationManual (D5074)

Negative ' - ' operator for analog signalsin Calculator Module equations Calculator-8

NETPROBE pseudo master autodialinterface. See ACCOL II Custom ProtocolsManual (document# D4066)

Network 3000 series controllersnumber of process I/O boards in Process I/O-1which can serve as Expanded Node Addressing

Master Expanded Node-3NMOLE terminal

in FPV Module FPV-2Node addressing Node Addressing1

#NODEADR.. system signal System Signals-34

Node Array (#NDARRAY..) System Signals-31Node errors

from slavesreported via #NODE.nnn systemsignals System Signals-34

Node Routing Tablepreventing transmission from PC to 33xx of

a ATOOLS-8, System Signals-34NODE_1 terminal

in EMaster Module Master-3in Nodestatus Module Nodestatus-4

NODE_2 terminalin EMaster Module Master-3in Nodestatus Module Nodestatus-5

NODE_ARRAY terminal


in EASTATUS Module EAStatus-4Nodestatus Module Nodestatus-1Non-critical alarm priority Signals-7NOT '~' operator

in Calculator Module equations Calculator-8Not equal ':NE:' string operator

in Calculator Module equations Calculator-8Not equal to ' != ' operator

in Calculator Module equations Calculator-8NRT. See Node Routing TableNSV terminal

in GSV Module GSV-8NUMMOLETYPE terminal

in GPA8173 Module GPA8173-2

OOff-line diagnostics system task priority Task-4OFF_LIM_SW terminal

in Command Module Command-2On-line diagnostics system task priority Task-3ON/OFF text for ACCOL signals Signals-5ON_LIM_SW terminal

in Command Module Command-2Operator Guide alarm priority Signals-7Operators

mathematical Calculator-6Optional Comm Port Commport-18ORIF_COEF terminal

in AGA3Dens Module AGA3Dens-4ORIF_CONST terminal

in AGA3 module AGA3-2in AGA3TERM module AGA3Term-2

ORIF_DIAM terminalin AGA3 module AGA3-2in AGA3Dens Module AGA3Dens-4in AGA3Iter module AGA3Iter-6in AGA3TERM module AGA3Term-2in ISO5167 Module ISO5167-4

ORIF_RTEMP terminalin AGA3Dens Module AGA3Dens-5

Orifice factorfor AGA3 module AGA3-9

OUTLIST terminalin DEMUX, EDEMUX modules Demux-2in Master/EMaster modules Master-7in Slave Module Slave-3in TCheck Module TCheck-4

OUTPUT terminalin AGA3 module AGA3-5in AGA3Iter module AGA3Iter-9in AGA3TERM module AGA3Term-5in AGA5 module AGA5-3in AGA7 module AGA7-5in ANOUT/RANOUT modules ANOUT-5in Command Module Command-1in Differentiator Module Differentiator-2in DIGOUT, RDIGOUT modules Digout-5in EIntegrator Module EIntegrator-2in FPV Module FPV-2in Function Module Function-2

in GBBTI and LBBTI modules BBTI-20in Integrator Module Integrator-2in ISO5167 Module ISO5167-8in LBCO Module LCBO-14in Lead/Lag Module Lead/Lag-2in MUX/EMUX modules MUX-2in PDO/RPDO modules PDO-6in PID3TERM Module PID3TERM-4in Scheduler Module Scheduler-4in Sequencer Module Sequencer-2in Stepper Module Stepper-5in VMUX Module VMUX-2

OUTPUT_1 terminalin Averager module Averager-2in Comparator Module Comparator-2in EAudit module Audit-7in HILOLIMITER Module HILOLIMITER-2in HILOSELECT Module HILOSELECT-1in Timer Module Timer-2in VLIMITER Module Vlimiter-3

OUTPUT_2 terminalin Averager module Averager-2in Comparator Module Comparator-4in EAudit module Audit-7in HILOLIMITER Module HILOLIMITER-2in HILOSELECT Module HILOSELECT-1in Timer Module Timer-3in VLIMITER Module Vlimiter-3

OUTPUT_3 terminalin Comparator Module Comparator-6in HILOLIMITER Module HILOLIMITER-2

OUTPUT_HIGH terminalin Daccumulator Module Daccumulator-6

OUTPUT_LIST terminalin Liquid_Density Module Liquid_Density-2

OUTPUT_LOW terminalin Daccumulator Module Daccumulator-6

OUTPUT_n terminalsin EDEMUX modules Demux-2

OUTTYPE terminalin Master/EMaster modules Master-6in Slave Module Slave-2

PPARAM_LIST1 terminal

in SYS_3530 module SYS_3530-2PARAM_LIST2 terminal




in SYS_3530 module SYS_3530-10PARAMETER_1 terminal

in ARC_STORE Module ARC_STORE-13PARAMETER_2 terminal

in ARC_STORE Module ARC_STORE-14PARAMETER_3 terminal

in ARC_STORE Module ARC_STORE-14


PARAMETER_4 terminalin ARC_STORE Module ARC_STORE-15





PARITY terminalin Portstatus Module Portstatus-8

PASSWORD keywordin ATOOLS.INI file. See UOI Configuration

Manual (D5074)PASSWORD_RD terminal

in Keyboard Module Keyboard-3PASSWORD_WT terminal

in Keyboard Module Keyboard-3Pausing system

in order to view messages ATOOLS-4PCMUSED terminal

in GSV Module GSV-3PDM Module PDM-1

#PDM.nnn. system signals System Signals-36questionable data for Ques Data-4

PDO Module PDO-1PDO system task priority Task-3PHONE keyword

in ATOOLS.INI file ATOOLS-5Pi

#PI.. system signal System Signals-38PID3TERM Module PID3TERM-1

using with ANOUT ANOUT-7PIPE_COEF terminal

in AGA3Dens Module AGA3Dens-4PIPE_DIAM terminal

in AGA3 module AGA3-2in AGA3Dens Module AGA3Dens-4in AGA3Iter module AGA3Iter-6in AGA3TERM module AGA3Term-2in ISO5167 Module ISO5167-4

PIPE_RTEMP terminalin AGA3Dens Module AGA3Dens-5

PIUOTDCF terminalin HWSTI Module HWSTI-22

POINT terminalin AGA3 module AGA3-3in AGA3Iter Module AGA3Iter-9in AGA3TERM module AGA3Term-3in ISO5167 Module ISO5167-8in LCBO Module LCBO-12in Master/EMaster modules Master-4in Slave Module Slave-1

Poll period system signals System Signals-38POLL_RATE keyword

in ATOOLS.INI ATOOLS-7PORT keyword

in ATOOLS.INI file ATOOLS-1PORT terminal

in EASTATUS Module EAStatus-3in Logger Module Logger-1

in Portstatus Module Portstatus-3in RIOSTATS Module RIOSTATS-1

Ports. See Communication PortsPortstatus Module Portstatus-1Position cursor (P) format descriptor Formats-30Positive '+' operator for analog signals

in Calculator Module equations Calculator-8Power failure in RIO 3331 RIOSTATS-2Power status

of battery in RTU 3305 or GFC 3308checking using the EncodeModule Encode-21

Power up (#PWRUP) system signals SystemSignals-45

Power up system task priority Task-3POWERFAIL terminal

in HCBO Module HCBO-4in HWSTI Module HWSTI-25

Powers '**' operatorin Calculator Module equations Calculator-7

PREV_DAY terminalin ETOT/TRND Module ETOT/TRND-4in TOT/TRND Module TOT/TRND-4

PREV_HOUR terminalin ETOT/TRND Module ETOT/TRND-4in TOT/TRND Module TOT/TRND-4

PREV_MONTH terminalin ETOT/TRND Module ETOT/TRND-4in TOT/TRND Module TOT/TRND-4

PREV_SHIFT terminalin ETOT/TRND Module ETOT/TRND-4in TOT/TRND Module TOT/TRND-4

Priority AGA8Detail-2of AGA8 system task AGA8-2, AGA8Detail-2of task containing AGA8 module AGA8-

8, AGA8Gross-8of task containing AGA8Detail

module AGA8Detail-7of task containing Master/EMaster

modules Master/Slave-1of tasks set via #PRI.nnn system

signals System Signals-44PRIORITY terminal

in AGA8 module AGA8-2in AGA8Detail module AGA8Detail-2in AGA8Gross module AGA8Gross-2

Process I/O Process I/O-1#DIAG.001. array for reporting board

errors System Signals-5#DIAG.002. array for storing process I/O

failure info. System Signals-7#DIAG.003. system signal for setting frequency

of System Signals-15Low-Level Board input types LLANIN-7

Process I/O ModulesANIN ANIN-1ANOUT ANOUT-1DIGIN Digin-1DIGOUT Digout-1HCBO HCBO-1HSANIN HSANIN-1HSCOUNT Counters-1


HWSTI HWSTI-1LCBO LCBO-1LLANIN LLANIN-1LSCOUNT Counters-1PDM PDM-1PDO PDO-1RANIN ANIN-1RANOUT ANOUT-1RDIGIN Digin-1RDIGOUT Digout-1RHSCOUNT Counters-1RLLANIN LLANIN-1RLSCOUNT Counters-1RPDM PDM-1RPDO PDO-1TCOUNT Counters-1

PROPORTION terminalin PID3TERM Module PID3TERM-2

Pseudo Master Autodial interface(NETPROBE). See ACCOL II CustomProtocols Manual (document# D4066)

Pseudo Slave Port Commport-6error statistics reported in Portstatus

Module Portstatus-15Setting Poll Period for System Signals-39

Pseudo Slave system task priority Task-3Pseudo Slave with Alarms Port Commport-7


Pulse or tone dialing modesetting default in ATOOLS.INI ATOOLS-6

PULSE terminalin HCBO Module HCBO-5in LCBO Module LCBO-14

PV terminalin HWSTI module HWSTI-12

PVCHAR terminalin HWSTI Module HWSTI-20

QQ format descriptor Formats-15Questionable Data

time and date via #PWRUP.001. systemsignal System Signals-49

Questionable Data Bit Ques Data-1setting in a Calculator Module Ques Data-5

Questionable Data Bit ':Q:' operatorin Calculator Module equations Calculator-13

RRaise current value by a percentage (CR)

format descriptor Formats-26Raise/Lower Mode

in Comparator Module Comparator-8RANIN Module ANIN-1

questionable data for Ques Data-2RANK terminal

in Scheduler Module Scheduler-3RANOUT Module ANOUT-1

RASCL#LINKE and #LINKF system signals System

Signals-29Rate

of a Task (#RATE.nnn.) System Signals-46RATE terminal

in AGA7 module AGA7-3in HSANIN Module HSANIN-7in VMUX Module VMUX-2

RATE_DOWN terminalin VLIMITER Module Vlimiter-3

RATE_UP terminalin VLIMITER Module Vlimiter-2

RBE Module RBE-1RBE signals Signals-8RBE system task priority Task-3RDB mode System Signals-46RDB system task priority Task-3RDIGIN Module Digin-1RDIGOUT Module Digout-1Read Priority for ACCOL signals Signals-5READ terminal

in Storage Module Storage-2Read-only arrays Data Arrays-1Read/Write Arrays Data Arrays-1Redundancy

an explanation of the concept of Redundcon-1forcing a switchover

using ACCOL logic Redundcon-8setting redundancy frequency Redundcon-6

Redundancy Module Redundancy-1Redundancy system task priority Task-3REF_P_HV terminal

in AGA8Gross module AGA8Gross-4REF_P_RD terminal

in AGA8Gross module AGA8Gross-5REF_T_HV terminal

in AGA8Gross Module AGA8Gross-4REF_T_RD terminal

in AGA8Gross module AGA8Gross-4REL_DENS terminal

in AGA3Dens Module AGA3Dens-6in AGA8Gross module AGA8Gross-4in EVP Module EVP-2

Remote Process I/OPoll periods for RIOR ports System Signals-

39Remote Process I/O Modules

RANIN ANIN-1RANOUT ANOUT-1RDIGIN Digin-1RDIGOUT Digout-1RHSCOUNT Counters-1RIOSTATS RIOSTATS-1RLLANIN LLANIN-1RLSCOUNT Counters-1RPDM PDM-1RPDO PDO-1

REMOTE terminalin IP_Client Module IP_Client-2in Master Module Master-2in Smart Module Smart-1


in XMTR_Interface Module XMTR_Interface-2

Report by exception. See RBE ModuleRERESOLVE terminal

in GPA8173 Module GPA8173-4RESET terminal

in ANOUT/RANOUT modules ANOUT-6in Averager module Averager-1in Command Module Command-3in Counter Modules Counters-7in Differentiator Module Differentiator-1in DIGOUT Module Digout-6in EIntegrator Module EIntegrator-1in Integrator Module Integrator-1in Lead/Lag Module Lead/Lag-2in Nodestatus Module Nodestatus-7in PDO/RPDO modules PDO-11in PID3TERM Module PID3TERM-3in Redundancy Module Redundancy-5in Scheduler Module Scheduler-2in Stepper Module Stepper-3in Storage Module Storage-1in Timer Module Timer-2

RESET_DAY terminalin ETOT/TRND Module ETOT/TRND-6

RESET_HOUR terminalin ETOT/TRND Module ETOT/TRND-6

RESET_INDEX terminalin Stepper Module Stepper-3

RESET_MONTH terminalin ETOT/TRND Module ETOT/TRND-6

RESET_SHIFT terminalin ETOT/TRND Module ETOT/TRND-6

RESOLUTION terminalin HSANIN Module HSANIN-5in PDO/RPDO modules PDO-5

RESOLV_NAME terminalin IP_Client Module IP_Client-3, IP_Server-8

RESP_TMO terminalin IP_Client Module IP_Client-4

RESTORE terminalin HCBO Module HCBO-3

Result ' = ' operatorin Calculator Module equations Calculator-7

RESUME statement Resume-1RHOOTHER terminal

in GSV Module GSV-7RHSCOUNT Module Counters-1RIOR Port Commport-20


Setting Poll Periods for System Signals-39RIOR system task priority Task-3RIOSTATS Module RIOSTATS-1RLLANIN Module LLANIN-1

questionable data for Ques Data-3RLSCOUNT Module Counters-1Round to integer ':RND' operator

in Calculator Module equations Calculator-8ROW terminal

in Function Module Function-1in Nodestatus Module Nodestatus-6

inHSANIN Module HSANIN-3RPDM Module PDM-1

#PDM.nnn. system signals System Signals-36questionable data for Ques Data-4

RPDO Module PDO-1RTD input types

for Low Level Board LLANIN-7RTDT terminal

in GBBTI and LBBTI modules BBTI-16RTDTSUB terminal


RTDTU terminalin GBBTI and LBBTI modules BBTI-17

RUN_TIME terminalin Command Module Command-3

RWAIT DI statement WAIT DI-1RWAIT DIH statement WAIT DI-1RWAIT DIL statement WAIT DI-1

SSCALE terminal

in Daccumulator Module Daccumulator-6SCANRATE terminal

in RBE Module RBE-8SCANSLICE terminal

in RBE Module RBE-9SCANTIME terminal

in RBE Module RBE-11Scheduler Module Scheduler-1SCRATCHPAD terminal

in HWSTI Module HWSTI-24SCRIPTS keyword

in ATOOLS.INI file. See UOI ConfigurationManual (D5074)

SecurityCI_SECURITY keyword ATOOLS-6for downloading ATOOLS-8MI_SECURITY keyword ATOOLS-6PASSWORD_RD and PASSWORD_WT for

Keyboard Module Keyboard-3Read priority for ACCOL signals Signals-5Write Priority for ACCOL signals Signals-5

SECURITY keywordin ATOOLS.INI file. See UOI Configuration

Manual (D5074)SECVAR terminal

in HWSTI Module HWSTI-15SEDANDWATER terminal

in GSV Module GSV-5SELECT terminal

in DEMUX, EDEMUX modules Demux-1in Encode Module Encode-2, Encode-

5, Encode-8, Encode-11, Encode-14, Encode-17, Encode-21, Encode-23

in MUX/EMUX modules MUX-2in VMUX Module VMUX-2

SELECT terminalsin Keyboard Module Keyboard-1

SELECT_1 terminal


in HILOSELECT Module HILOSELECT-2SELECT_2 terminal

in HILOSELECT Module HILOSELECT-2SENSRTYP terminal

in HWSTI Module HWSTI-18SEQ_NUM_1 terminal

in RBE Module RBE-14SEQ_NUM_2 terminal

in RBE Module RBE-14Sequencer Module Sequencer-1Serial CFE Port Commport-13


Serial Portson Network 3000 controllers Commport-3

SERIALNO terminalin HWSTI Module HWSTI-24

SERVR_ID terminalin IP_Client Module IP_Client-3in IP_Server Module IP_Server-1

SERVR_INDEX terminalin IP_Client Module IP_Client-5

SERVR_SELECT terminalin IP_Client Module IP_Client-6

SERVR_STRUCT_NO terminalin IP_Client Module IP_Client-5

Set alarm enable (SAE) formatdescriptor Formats-20

Set Alarm Inhibit (SAI) formatdescriptor Formats-20

Set cell repeat mode (DR) formatdescriptor Formats-17

Set Cell Wrap Around Mode (DW) formatdescriptor Formats-18

Set control enable (SAE) formatdescriptor Formats-21

Set control inhibit (SCI) formatdescriptor Formats-21

Set Data Array column (CX) formatdescriptor Formats-27

Set data array row (CY) formatdescriptor Formats-27

Set manual enable (SME) formatdescriptor Formats-21

Set manual inhibit (SMI) formatdescriptor Formats-21

Set system date (CD) format descriptor Formats-26

Set system time (CT) format descriptor Formats-26

Set terminal type to ANSI (PA) formatdescriptor Formats-30

Set Terminal Type to VT52 (PV) formatdescriptor Formats-30

SETPOINT terminalin Comparator Module Comparator-2in PID3TERM Module PID3TERM-1in Timer Module Timer-2

SHIFT_SPAN terminalin ETOT/TRND Module ETOT/TRND-3in TOT/TRND Module TOT/TRND-3

Signal indirection format descriptors Formats-31

Signal Lists Signal Lists-1Signal name (Nxn) format descriptor Formats-10Signal Units (Uw) format descriptor Formats-11Signal wrap around mode (SW) format

descriptor Formats-20Signals Signals-1

mathematical operations on Calculator-6maximum number allowed in ACCOL

load Signals-3naming conventions Signals-2operators for. See Calculator Module

Sine ':SIN' operatorin Calculator Module equations Calculator-8

Single Precision floating pointnumbers Daccumulator-1

Single signal operatorsin Calculator Module equations Calculator-12

Skip array cell (DS) format descriptor Formats-17

Skip array cell backwards (DSB) formatdescriptor Formats-18

Skip signal backwards (SSB) formatdescriptor Formats-20

Slave communication task priority Task-3Slave Module Slave-1

identifying using Master Module POINTterminal Master-4

Slave Module system task priority Task-3Slave Port Commport-5


setting Poll Period for System Signals-39Slippage of ACCOL Tasks System Signals-46Smart Module Smart-1Smartkit

notes about using with GBBTI andLBBTI BBTI-2

SP terminalin GBBTI and LBBTI modules BBTI-14

SPAN terminalin AGA7 module AGA7-5in ANIN/RANIN modules ANIN-6in ANOUT/RANOUT modules ANOUT-6in Averager module Averager-2in Differentiator Module Differentiator-1in EIntegrator Module EIntegrator-2in HSANIN Module HSANIN-4in Integrator Module Integrator-2in LLANIN/RLLANIN modules LLANIN-6in PDM/RPDM modules PDM-10in PDO/RPDO modules PDO-9

SPARE terminalin Logger Module Logger-5

SPEC_GRAV terminalin AGA3 module AGA3-4in AGA3Iter module AGA3Iter-8in AGA3TERM module AGA3Term-4in AGA5 module AGA5-2in AGA7 module AGA7-4in Characterize Module Characterize-2in FPV Module FPV-2

SPECIDSTRUCT terminal


in GPA8173 Module GPA8173-2SPSUB terminal


SPU terminalin GBBTI and LBBTI modules BBTI-15

Square root ':SQR' operatorin Calculator Module equations Calculator-8

START_HOUR terminalin ETOT/TRND Module ETOT/TRND-2in TOT/TRND Module TOT/TRND-2

START_MIN terminalin ETOT/TRND Module ETOT/TRND-2in TOT/TRND Module TOT/TRND-2

Startup commands for tools. See ATOOLS.INISTAT_P2 terminal

in ISO5167 Module ISO5167-7STAT_PRESS terminal

in AGA3 module AGA3-1in AGA3Dens Module AGA3Dens-3in AGA3Iter module AGA3Iter-5in AGA3TERM module AGA3Term-2in AGA8 module AGA8-3in AGA8Detail module AGA8Detail-3in AGA8Gross module AGA8Gross-3in FPV Module FPV-1in ISO5167 Module ISO5167-3

STATE terminalin Keyboard Module Keyboard-3in PDM/RPDM modules PDM-10in Scheduler Module Scheduler-1in Sequencer Module Sequencer-1

STATUS terminalin AGA8 module AGA8-5in AGA8Detail module AGA8Detail-5in AGA8Gross module AGA8Gross-6in ARC_STORE module ARC_STORE-12in Audit/EAudit modules Audit-6in Characterize Module Characterize-4in Command Module Command-3in EASTATUS Module EAStatus-7in Encode Module Encode-4, Encode-

7, Encode-10, Encode-13, Encode-16, Encode-19, Encode-22, Encode-27

in EVP Module EVP-5in GBBTI and LBBTI modules BBTI-21in GPA8173 Module GPA8173-5in GSV Module GSV-8in HSANIN Module HSANIN-5in HWSTI Module HWSTI-11in Internet_Protocol Module Internet-2in Keyboard Module Keyboard-4in LCBO Module LCBO-15in Liquid_Density Module Liquid_Density-3in Logger Module Logger-3in Nodestatus Module Nodestatus-8in Portstatus Module Portstatus-9in RANIN module ANIN-5in RANOUT module ANOUT-5in RBE Module RBE-14in RDIGIN Module Digin-5in RDIGOUT Module Digout-5

in RHSCOUNT/RLSCOUNTmodules Counters-6

in RLLANIN Module LLANIN-5in RPDM Module PDM-11in RPDO Module PDO-5in Storage Module Storage-3in TCheck Module TCheck-4in Watchdog Module Watchdog-5

STATUS_1 terminalin HSANIN Module HSANIN-7in IP_Client Module IP_Client-7in IP_Server Module IP_Server-7in Master/EMaster modules Master-7in Redundancy Module Redundancy-2in Slave Module Slave-3in Smart Module Smart-4in XMTR_Interface Module XMTR_Interface-

7STATUS_2 terminal

in IP_Client Module IP_Client-8in IP_Server Module IP_Server-8in Master/EMaster modules Master-7in Redundancy Module Redundancy-2in Slave Module Slave-3in Smart Module Smart-4in XMTR_Interface Module XMTR_Interface-

8STATUS_n terminals

in RIOSTATS Module RIOSTATS-2STATUS1 terminal

in AAT Module AAT-6STATUS2 terminal



in AAT Module AAT-7STEP terminal

in Stepper Module Stepper-4Stepper Module Stepper-1STIEU terminal

in HWSTI Module HWSTI-13STISWVER terminal

in HWSTI Module HWSTI-24STITAG terminal

in HWSTI Module HWSTI-22Stop-On-Full Mode

in Audit Trail Modules Audit-4STOP_BITS terminal

in Portstatus Module Portstatus-8STOPXMIT terminal

in RBE Module RBE-11Storage Module Storage-1String (Tn) format descriptor Formats-9String cast ':S' operator

in Calculator Module equations Calculator-10String constants Calculator-3String Signals Signals-1

converting characters to floating point valuesusing Encode Module Encode-2

STROBE terminalin HSANIN Module HSANIN-4


BLANK

in Scheduler Module Scheduler-1in Sequencer Module Sequencer-1in Stepper Module Stepper-1

STRUCT_TYPE terminalin IP_Client Module IP_Client-4

STRUCTMODE terminalin GPA8173 Module GPA8173-2

Subtract ' - ' operatorin Calculator Module equations Calculator-7

SUSPEND statement Suspend-1Switchover. See Redundancy ModuleSWV terminal

in GSV Module GSV-8Synchronous Communication Commport-28SYS_3530 Module SYS_3530-1System command task priority Task-3System date/time

converting to analog valuesusing the Encode Module Encode-14

creating using analog valueswith the Encode Module Encode-17

format descriptor for setting date Formats-26format descriptor for setting time Formats-26

System Module System-1System Signals System Signals-1

#ALARM.FORMAT. System Signals-3#ALARM.FORMAT.001 System Signals-3#ALARM.LIM. System Signals-3#DIAG.001. System Signals-5#DIAG.002. System Signals-7#DIAG.003. System Signals-15#DIAG.006. System Signals-18#DIAL.000. System Signals-16#DIAL.001. System Signals-17#DIAL.002. System Signals-17#DIAL.003. System Signals-17#DIAL.004. System Signals-18#DIAL.005. System Signals-18#DIAL.006. System Signals-18#DIAL.007. System Signals-19#DIAL.008. System Signals-19#DIAL.009. System Signals-19#E.. System Signals-20#ERARRAY.. System Signals-20#ERRCT.000. System Signals-24#ERRCT.LIM. System Signals-25#ERRCT.nnn. System Signals-25#IPSTAT.. System Signals-26#LINE.000. System Signals-28#LINE.001. System Signals-28#LINE.002. System Signals-28#LINE.003. System Signals-28#LINE.004. System Signals-28#LINE.005. System Signals-28#LINE.006. System Signals-28#LINE.007. System Signals-28#LINE.008. System Signals-28#LINE.009. System Signals-28#LINKE.001. System Signals-29#LINKE.002. System Signals-29#LINKE.LIM. System Signals-30#LINKF.001. System Signals-30

#LINKF.002. System Signals-30#LINKF.LIM. System Signals-31#LOAD.. System Signals-31#NDARRAY.. System Signals-31#NODE.nnn. System Signals-34#NODEADR.. System Signals-34#NRT.INH. System Signals-34#NRT.REQ. System Signals-35#OCTIME.. System Signals-35#OCTIME.ERROR. System Signals-35#OFF.. System Signals-35#ON.. System Signals-36#PDM.000. System Signals-36#PDM.001. System Signals-36#PDM.002. System Signals-36#PDM.003. System Signals-36#PDM.004. System Signals-37#PDM.005. System Signals-37#PDM.006. System Signals-37#PDM.007. System Signals-37#PDM.008. System Signals-37#PI.. System Signals-38#POLLPER.nnn. System Signals-38#PRI.nnn. System Signals-44#PWRUP.000. System Signals-45#PWRUP.001. System Signals-45#RATE.nnn. System Signals-46#RCNT.LIM. System Signals-46#RCNT.nnn. System Signals-46#RDB.MODE. System Signals-46#RDN.ARRAY.NUM Redundancy-4#RDN.BACKUP.STAT Redundancy-2#RDN.BKSTAT.HILM Redundancy-4#RDN.LIST.NUM Redundancy-4#RDN.ONLINE.UNIT Redundancy-2#RDN.RESET.DATA Redundancy-5#RDN.SWITCH.OVER Redundancy-5#RDNERR.. System Signals-47#RDNLIM. System Signals-47#RTTIME.000. System Signals-47#RTTIME.001. System Signals-48#TIME.nnn. System Signals-49

System Taskfor AGA8 calculations AGA8-2, AGA8Detail-

2, AGA8Gross-2System Tasks

Priority relative to ACCOL Tasks Task-2SYSTEM_WAIT keyword

in ATOOLS.INI ATOOLS-4System0 Module System0-1

TTAG terminal

in GBBTI and LBBTI modules BBTI-20Tangent ':TAN' operator

in Calculator Module equations Calculator-8Tano Port Commport-18TANO Slave interface. See ACCOL II Custom

Protocols Manual (document# D4066)TAP_LOC terminal


in AGA3Dens Module AGA3Dens-3in AGA3Iter module AGA3Iter-5

Target Nodedownloading to the Downloading-1

Task control statements. See Control StatementsTasks Task-1

#PRI.nnn system signals System Signals-44Aborting execution of Abort-1control statements for Control Stmts-1delaying execution for a specific time period

using WAIT DELAY statement WaitDelay-1

Error array (#ERARRY..) for System Signals-20

Error count (#ERRCT.nnn) systemsignals System Signals-25

Error counter alarm limit (#ERRCT.LIM.)system signal System Signals-25

measuring the execution time of SystemSignals-47

Ratesetting via #RATE.nnn systemsignals System Signals-46

restarting using RESUMEstatement Resume-1

Slippage counter for System Signals-46starting execution at a particular time of day

using WAIT TIME statement WAIT TIME-1

stopping execution until a condition becomesTRUEusing WAIT FOR statement WAIT FOR-1

stopping execution until transition of logical sigusing WAIT DI/RWAIT DIstatements WAIT DI-1

stopping execution using SUSPENDstatement Suspend-1

TCheck Module TCheck-1TCMUSED terminal

in GSV Module GSV-2TCOUNT Module Counters-1Teledyne Geotech Slave Interface. See ACCOL II


TeleFlow/TeleRTUcommunication port options in

the Commport-26process I/O options Process I/O-7system signals used with SYS_3530-1

TeleTransand the Smart Module Smart-1and the TCheck Module TCheck-1and the XMTR_Interface

Module XMTR_Interface-1rules for assigning local addresses BBTI-5

TeleTrans Board Process I/O-5TeleTrans modules

GBBTI and LBBTI BBTI-1Template manager system task priority Task-3Terminate repeat (SE) format

descriptor Formats-20Terminate special input loop (CQ)

format descriptor Formats-27THERM_COEF1 terminal

in AGA3Iter module AGA3Iter-6THERM_COEF2 terminal

in AGA3Iter module AGA3Iter-6THERMAL_COEF2 terminal

in ISO5167 Module ISO5167-5THERMAL_COEFF1 terminal

in ISO5167 Module ISO5167-4Thermocouple input types

for Low Level Board LLANIN-7THRESMULTI terminal

in EVP Module EVP-3Time

ST format descriptor Formats-21Time (#TIME.nnn) system signals System

Signals-49Time ACO file generated

#LOAD.. system signal System Signals-31Time specifier (ST) format descriptor Formats-21Time Stamp

Alarm Timestamp Buffers Buffers-2Time synch messages

enabling System Signals-35preventing System Signals-34preventing transmission from the PC to 33xx of

a ATOOLS-8TIME terminal

in Averager module Averager-3in ETOT/TRND Module ETOT/TRND-3in Keyboard Module Keyboard-3in PDM/RPDM modules PDM-6in Stepper Module Stepper-4in Timer Module Timer-2in TOT/TRND Module TOT/TRND-3

Time/Date, packed Julianconverting to analog values

using the Encode Module Encode-8Time/Date, system


specifiying using analog valueswith the Encode Module Encode-17

TIMEOUT terminalin HCBO Module HCBO-3in Portstatus Module Portstatus-9in RBE Module RBE-12

TIMEOUT_INP terminalin Logger Module Logger-2

TIMEOUT_OUT terminalin Logger Module Logger-2

Timer Module AGA8Detail-7, AGA8Gross-8, Timer-1

using to trigger AGA8 execution AGA8-8using to trigger AGA8Detail

execution AGA8Detail-7using to trigger AGA8Gross

execution AGA8Gross-8Tone or pulse dialing mode

setting default in ATOOLS.INI ATOOLS-6Tools initialization file. See ATOOLS.INITOT/TRND Module TOT/TRND-1


TOT_INIT_MODEM keywordin ATOOLS.INI file ATOOLS-4

TOTAL_1 terminalin RBE Module RBE-12




TRACK terminalin AGA3 module AGA3-4in AGA3Dens Module AGA3Dens-6in AGA3Iter module AGA3Iter-9in AGA3TERM module AGA3Term-4in ANOUT/RANOUT modules ANOUT-6in Averager module Averager-2in DIGOUT Module Digout-6in ETOT/TRND Module ETOT/TRND-5in GBBTI and LBBTI modules BBTI-21in HCBO Module HCBO-4in ISO5167 Module ISO5167-8in LCBO Module LCBO-14in PDM/RPDM modules PDM-8in PDO/RPDO modules PDO-10in PID3TERM Module PID3TERM-3in Scheduler Module Scheduler-3in Stepper Module Stepper-3in VLIMITER Module Vlimiter-2in VMUX Module VMUX-1

TRACK_INDEX terminalin Stepper Module Stepper-3

TRANSITION terminalin Command Module Command-2

Transmitters. See TeleTransTrigonometric functions

in Calculator Module Calculator-8True/False (Kx) conditional format

descriptor Formats-12Truncate floating point number

in Calculator Module equations Calculator-8TSNRT_ENABLED keyword

in ATOOLS.INI ATOOLS-8turbine meter. See AAT ModuleTYPE terminal

in Encode Module Encode-3, Encode-6, Encode-9, Encode-12, Encode-15, En-code-18, Encode-24

in Internet_Protocol Module Internet-1in PDM/RPDM modules PDM-5in Storage Module Storage-3

UUNAVAILABLE terminal

in Scheduler Module Scheduler-3UNITS terminal

in GPA8173 Module GPA8173-2in GSV Module GSV-5

Units text for ACCOL signals Signals-6UOI=NO_COMM_MENU keyword


UOI=NO_DOWNLOAD keywordin ATOOLS.INI. See UOI Configuration

Manual (D5074)UOI=OFFLINE keyword


URL terminalin HWSTI Module HWSTI-23

URV terminalin HWSTI Module HWSTI-23

VVAPORPRESS100 terminal

in EVP Module EVP-4VAPORPRESSMAX terminal

in EVP Module EVP-4Virtual node

definition of a Expanded Node-1VISCOSITY terminal

in AGA3Dens Module AGA3Dens-5in AGA3Iter module AGA3Iter-7in ISO5167 Module ISO5167-6

VLIMITER Module Vlimiter-1VMUX Module VMUX-1VOL_%_CO terminal

in AGA5 module AGA5-2VOL_%_CO2 terminal

in AGA5 module AGA5-2VOL_%_H2 terminal

in AGA5 module AGA5-3VOL_%_H20 terminal

in AGA5 module AGA5-3VOL_%_H2S terminal

in AGA5 module AGA5-3VOL_%_HE terminal

in AGA5 module AGA5-2VOL_%_N2 terminal

in AGA5 module AGA5-2VOL_%_O2 terminal

in AGA5 module AGA5-2VOL_CONVERS terminal

in AGA5 module AGA5-3VOL_FLOW terminal

in AGA3Dens Module AGA3Dens-7Voltage Input types

for Low Level Board LLANIN-7VOLUME terminal

in AGA5 module AGA5-1VSAT Slave Port Commport-8


WWAIT DELAY statement Wait Delay-1WAIT FOR statement WAIT FOR-1WAIT TIME statement WAIT TIME-1WAIT_DI statement WAIT DI-1


WAIT_DIH statement WAIT DI-1WAIT_DIL statement WAIT DI-1WAIT_ON_ERROR keyword

in ATOOLS.INI file ATOOLS-4Warm Start Downloading-2Watchdog Module Watchdog-1WORD_LENGTH terminal

in Portstatus Module Portstatus-8Wrap-around mode

in Audit Trail buffer Audit-4Write Priority for ACCOL signals Signals-5WRITE terminal

in Storage Module Storage-2

XXMITSTAT terminal

in HWSTI Module HWSTI-24XMT_FACTORY_SETTINGS keyword


XMT_SCALECHANGEin ATOOLS.INI. See UOI Configuration

Manual (D5074)XMTR_Interface Module XMTR_Interface-1

ZZ_BASE terminal

in AGA3Iter module AGA3Iter-9in AGA8 module AGA8-6in AGA8Detail module AGA8Detail-6in AGA8Gross module AGA8Gross-7

Z_FLOWING terminalin AGA3Iter module AGA3Iter-8in AGA8 module AGA8-6in AGA8Detail module AGA8Detail-6in AGA8Gross module AGA8Gross-7

ZERO terminalin ANIN/RANIN modules ANIN-6in ANOUT/RANOUT modules ANOUT-6in EIntegrator Module EIntegrator-2in HSANIN Module HSANIN-3in Integrator Module Integrator-2in LLANIN/RLLANIN Modules LLANIN-5in PDM/RPDM modules PDM-10

BLANK PAGE

Reference Manual

D4044 May 2006

ACCOL II Software

The information in this document is subject to change without notice. Every effort has been made to supply complete and accurate information. However, Bristol, Inc. assumes no responsibility for any errors that may appear in this document. If you have comments or questions regarding this manual, please direct them to your local Bristol sales representative, or direct them to one of the addresses listed at left. Bristol, Inc. does not guarantee the accuracy, sufficiency or suitability of the software delivered herewith. The Customer shall inspect and test such software and other materials to his/her satisfaction before using 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. ACCOL is a trademark and Bristol is a registered trademark of Bristol Inc. The Emerson logo is a trade mark and service mark of Emerson Electric Co. Other trademarks or copyrighted products mentioned in this document are for information only, and belong to their respective companies, or trademark holders.

Emerson Process Management Bristol, Inc. 1100 Buckingham Street Watertown, CT 06795 Phone: +1 (860) 945-2262 Fax: +1 (860) 945-2525 www.EmersonProcess.com/Bristol Emerson Electric Canada, Ltd. Bristol Canada 6338 Viscount Rd. Mississauga, Ont. L4V 1H3 Canada Phone: 905-362-0880 Fax: 905-362-0882 www.EmersonProcess.com/Bristol Emerson Process Management BBI, S.A. de C.V. Homero No. 1343, 3er Piso Col. Morales Polanco 11540 Mexico, D.F. Mexico Phone: (52-55)-52-81-81-12 Fax: (52-55)-52-81-81-09 www.EmersonProcess.com/Bristol Emerson Process Management Bristol Babcock, Ltd. Blackpole Road Worcester, WR3 8YB United Kingdom Phone: +44 1905 856950 Fax: +44 1905 856969 www.EmersonProcess.com/Bristol Emerson Process Management Bristol, Inc. 22 Portofino Crescent, Grand Canals Bunbury, Western Australia 6230 Mail to: PO Box 1987 (zip 6231) Phone: +61 (8) 9725-2355 Fax: +61 (8) 8 9725-2955 www.EmersonProcess.com/Bristol

accol ii reference manual (d4044) · training courses bristol's training department offers a...

Documents