Remote Automation Solutions Bristol RTU 3301 AI, DIO, RTD, Thermocouple Input, Frequency Input Modules Owner's Manual

Instruction Manual
C1-3301-01
Issue: 12/92
ÓN
Analog Input Module
Thermocouple Input Module
RTD Input Module
Frequency Input Module
Discrete 1/0 Module
© BRISTOL
© fa ma
® DIG/EV CURRENT
VD DOB/LO RS-232C
(DD || DEFAULT
MD || TRANSMIT
® RECEIVE
D +VS
Фо,
”
Bristol Babcock
CI-3301-01
12/92
FIRST
RTANT - READ
MPOI
This manual includes information useful to several levels of RTU 3301 users. The following sections are
relevant to the user of the RTU 3301 as a component in a Bristol Babcock Network 3000 system. They
describe installation and operation of the RTU 3301. You should read and be familiar with these sections
prior to using the RTU 3301.
User Sections Page Numbe(s)
Introduction 1
Description 2 |
Calibration 7 through 20
Installation 21 through 33
Operation 34 through 55
Maintenance 56
Appendix D
RTU-RTS Option D-1
Appendix E
Modem Connections E-1
The remaining sections of this manual provide much greater detail on communication and protocol. These
sections are intended for engineering custom interfaces to the RTU 3301.
Engineering Sections Page Number
Command Set 34 through 55
Appendix B - Commands
Summary B-1
Appendix C -
Conversion Chart C-1
Related Documents
C1-3301-04 Programmer's Guide
C1-3301-05 Custom Module Interface Manual
CI-3301-01
12/92
Introduction ............e==-..e..=eeexeairnceaoneneeennnan nene ana E NENE anne enaNere nee UUnE nee anecameneenAnnaneanaNUnrNENaOanaNEenneAnancenenenaa. 1
DX 101 (10) JOT SSSE RE STE TRT FEL EER ER 2
PACKAGE EZ Ze 2
Operational CharacteristiCS …….……..….…….….…esnenenecnenene sennennnnnennnnnçnnnnnnnnnnnnnnnnnnnnnnnnn 2
RTU Utility SOftWare..….…...…....…………uscrcsccreccennensenenere eereceen sense secte ere r ane ce rates ces S SEC EEE rc ere ees 3
RTU ASCII Commands ...................e.eeeeeserirrerecerceraare coreo rene recen ee cererane ecran en Sad cent ee N ECC C SCENE 3
[0] (10) 1 J SPP FITS SIP EI LIT 4
Specifications ........................ee eee nene ecer rare eenecreaneenereeeneraneccarenerenenenecenececerenerenene»e 5
Cali AION weeverrerrrereremmmnssassssssssssssrressersssseessenssannnsnnssessasssmnss sn snasssnnssnsssssssssentunnnssassssssnessnssnnsnsssannsssssass 7
Calibration Setup NPP OPP PPP PPR 7
Calibration Procedure ......................e.iveeeeeerereererer erre eee eee eee arse sass ee saab e serbian ss aetna ern ns 0000 13
RTU Configuration ................—.=..eemee eee ene nee Ree ene nceeeen reee nerecenrnecrenercereceneenerees 14
RTU Utility Software ..............ew.....eserevrnecenenoea neones rente nero n nee enan ena nnenvenana case ceneneeaneeenatenaceanennene.s 15
Installing Utility .….....……..….…reurcessecencenennentenseree mener esse cree crane detre caen set cer ce rer cree EE 15
Getting Around in Utility .................—.—....eieererereeree nee eee eee ein e ne en ee nene ren encon 15
Context-Sensitive Help ..................reemmmereeiennn ee e RR RR recrea receneneceraeeceneneneacacanecurece. 16
Configuring the Host in Utility ...................... 2. e..eeeeee eee eee nene n rencor ea eee reaece ner ee 16
Configuring the RTU in Utility ................. es 17
Terminal Emulation in Utility essen r en erkenne nEKERRKKERERREKKKKKKERERERKEEREEREEREEKURKRKKUREUKKEEKELKKEEEEEEEKEKUKEEUM 20
Discrete 1/0 Module Sets rer EEE EEE RRKRRKKRRRERRENKKKKEREEEKEKERKREREERERRKKKERKREEKERKKERGKERUKERKLKERKUEEEUUUNG 20
README.TXT ee RER RRRKERRRRRKRRERERERRKRKEERRERERAERERERERRARUEKEEEARKEEERAEKAEUERAKKEEKERENEREKEUAURKEREURKLEKKEEUUEG 20
QUITTING ULITY «eevee eee ected sess 20
Installation 1ueeererrunsrrerrrrnsnsssirrnsessssssssnsnsssnnsssensssssssssnssssnssssssenssssysnsnssssestsnnnanssssnnsssssnnssnsssshsnnsnusmnennsanss 21
[0 T0T 41 To OE OPPS PSO POPPER APPR 21
Electrical Connections ..............e.....eeeeceeercerererecerecereecercene ron oceneren nica een ene necer enero eneecanenerenrecn vane. 22
RS-485 ConsiderationSs ……………...…..…..…….rrerrensersensen riens ne rrecansenca ne ereceeeerceoenenerrnrerenEnENTe nenes. 22
RS-239C ConsiderationS ………..…....…..……..…..….….……errrrreccsennsnen se er eran erates sass sess benassi aris aae sansa sae sasnsnsanuanns 23
Power Supply Requirements ….…..…..…..….....…errraneenenennenmnennnnnennnnnnnnnnnnnnnnnnnnMnmnnnnnennnnn 25
Sensor Connections for Current, Voltage, and Thermocouple RTU 'S .................... 2. eeneiineneneneneon.. 25
Connection for the Discrete Terminals of Analog RTU S .…........rosrerecrssrerecranence carre ces sren ces ne ce e 25
DiSCrete 1] 0 LF JUSTO P PP EE CE 25
EV ENE COUNT O Ts 25
DIGItAl QUIPULS reece etcetera ees 26
YT 4 JO 1T 11011 JOO SSOP OR PPP 27
Connections for RTD RTU'S ..................eeeerirererrerenvenenneerene eee renenencec rene reren ree receaneren e veccaror enn ecene. 27
Y= Te LEC 1110 L210 [121 [FE OUP SPP PPO PP PT 28
Connections for Frequency RTU “Soccer eee 30
Connections for Discrete RTU 'S ....................eecercerccrrererccener cone cece s reee enero rereee rene nerererenenene 32
(0 oT 7-110] JF Denon ce neenace nene renneneereoneneacea na ennavoneneeenaeneee nene nnnUne nano cante canenenanans 34
The Command/Response Format .......................rreeeeemerereierer Dre reee e ere eee ereer rene eenenTe een. 34
076] 0a 147-1 To I 1111110 Tc JUTSU UOT U PIP PPPPP RPP 36
RTU General Operation COMMAaNGAS ......o.ooeuririiii irene ceiriirrae esses serra erase ssn rasan e ene, 37
C1-3301-01
12/92
DISABLE WRITE PROTECTION - WRITE ENABLE ................eeeeecemmerreneereceareccnncanenenen canon. 37
READ DATA …..…...reccccsersensanrannenasneenrennr ananas en rene sa nen esse eee ce senc are den ete ete ES Ve NES 37
READ NEW DATA ..........eee.ecerrreercerecccccencecerceceracercercerve reee re reeneeren eee sree sata es ness ara es seen n bas 37
READ HIGH ALARM TRIP POINT …...…rrrrrrrerrereereeesensencesnenenrenen scene are n ete ca ne nee s sess na sas 39
READ LOW ALARM TRIP POINT .................e..eenmcerrermeeneeenenccc cenar erce ner nrrrrnercecenen neon scenes anna 39
CLEAR ALARMS .............e..eericecenmecerncecrrecerarrererrerree eee conenertecne ren ereeearocanenecenen acen enonerrecenerra reee 39
READ EVENTS COUNTER ................eenecncecececarrerneneeararrerea en enereren recrear ene nerireneeeno neon sense annans 39
CLEAR EVENTS COUNTER ..............eeeecererrrinereeeeevereccoccunreacarenven nen nconenvecven ero neenenenerreccane nana. 40
TRIM ZERO ...............eeecericcerenocericenecenceraceeerenarrenee rre nee eenenececereeanrrnrrnemeenrnrenar ree na rnrocearanecoccareos 40
READ ZERO SETTING .................mvivecccerereceraceenenreoereceo cen recarererererenerne ere eerrcrce ne recen en anccccaaeceeo. 40
SET DEVIATION OUTPUT ZERO POINT «eects serene nana 41
CLEAR ZERO SETTING ..............e.ee.ereerrrcerererirerneereececrceceerrcace reee enreranererenenenerrorreerenrnecenanenenana 41
TRIM SPAN -..........ececcccerccrenecerneccenee erre e ererereceecane rene ree rere ra areereereracenere ener nerererereenennenecnenaceUenee. 41
READ DISCRETE INPUT ON/OFF STATE «coors nese 41
SET ON/OFF STATE OF DISCRETE OUTPUTS oie riers esterase aaa 42
Reset Module .........................ereeenceererireee e ere eee sear aaas ses ra see essa s ease seta sr hs den en CG VND NES 43
Commands Unique to Discrete RTU’S .......…..….…….……meessmeemeenmenennmenn nas senmenneensennenenena conan anses enen see 44
ACKNOWLEDGE ………..…......…rrecereones rene ne rarenrena rase re rense en re sceau sean ea seen nee n SEE NES rene etc CEE 44
SET I/O — ALL TERMINALES -.............eeeeenereccecicorrerren ener nentrnececeeen erroneo nrrener none nocrenenocaneraaaon.. 46
SET I/O FOR INDIVIDUAL TERMINALS ............eeceeeeneenererenenccrcencercarareenennererene nene ne nene receneacenanoa. 46
READ 1/0 ASSIGNMENTS — ALL TERMINALS ...........e...e.e.e.eerenenenencenecooo eee roecanannanecerenceneneeeee. 47
READ I/O ASSIGNMENTS — INDIVIDUAL TERMINALS .........e..eeeeeneeennmereeneconerneocenreenecccenencano. 48
SET ON/OFF STATE — ALL TERMINALES -...............==...erecriierenecccarrreneeeoereveceree recen en eeonenernennennane 48
SET ON/OFF STATE —- INDIVIDUAL TERMINALES -..............reseeeeeerecnerenerannecen reee nerencen enana 49
READ ON/OFF STATE — ALL INPUTS ............e.eeeeeerenenenceneinecenc enero neeecan rear re ree enn e nene neneceneee. 49
READ ON/OFF STATE — INDIVIDUAL TERMINALES ...............eeeeerereneneencceneooreereccannoneneaneneaenen. 49
SET INITIAL VALUE -................e.r1scevccreveccececceccrroreree reo en ererreca reee era rene necerrenTe rre nene ere rcerrennenenaDene 50
READ INITIAL VALUE ................eevevecccenceracorcnreneneeneoeooceeecenerenonereneneenaneereneeacarecerene nen rerrocaneneneeen. 50
SET THE WATCHDOG TIMER -................eeeeeecececrcenzre reee ere Renee ercer errar seers 50
READ THE WATCHDOG TIMER SETTING ............eccocsesessererenee ser srane nca esse een recense cernes 51
SET MODULE IDENTIFIER ..................eereeeencerreanerecr ee erre rr necern ene end e ere e ne res rence NS 51
READ MODULE IDENTIFICATION -.............e..ee.erecorcccinrnn irene eee e een D ener ce nerreneecen nene ercacenane. 51
READ EVENTS AND CLEAR COUNTER ............. e... eecccecacancacarerenececeoroncenencar rente recee on enennenene ne. 51
Discrete RTU Continuous Mode Operation ...............e=e=ecececccenrnecnnnnenenencanacanecenennencaneneun ana rnenUee 52
SET CHANGE-TRIGGERED CONTINUOUS MODE -..............eeeeeennecerrercerreacanercecenoneonacaneneneeo 52
SET EDGE-TRIGGERED CONTINUOUS MODE -...........e..ee.eneecerrrnrcceceerenecnanenere nene ren ene ece ne 52
SET TIMER-TRIGGERED CONTINUOUS MODE -...............eeeeerecereninencececnencen een ee nencenaneneenee. 53
SET INPUT-TRIGGERED CONTINUOUS MODE ............e.eee.eeeeerereenerecerneneenene neon eneneneneen e 54
SET CONTINUOUS MODE INPUT ADDRESS .…..….......cocerecernreneenerseneneee ren sen een sean ecran en ann see 54
READ CONTINUOUS MODE SETTING .........eeeeeneeerecenenenercccceneececenenenoecenereecenrare nene ncenrneneneene.. 54
READ INPUT ADDRESS .............eeeeenecincccnenrccccccenererrerrrereneee eee rne cera reorenecenrencacen vencen enereneneenena 54
READ CONTINOUS TIMER SETTING............eeeeeeeeerncconeereninircanneceenoeecora carrer rene een reee rcareneennene.. 54
The Continuous Timer and Continuous Mode Operations.............————.e.m=..nnunsnceneonenccanenneconene. 55
DISABLE CONTINUOUS MODE -...............eccecececerenirnarornerneneenceneeceeen rea enanacereeccer renace cer 55
Maintenance .................e.enecannosceaernoeanena Neem ANNAN NNAe DU naRaeece NERO RENO eEEeNUNeNDNERe anenanee rece Une cane aneeeanemenna Ann eNeca Neme. 56
CI-3301-01
12/92
Appendix À - RTU_PRG OV@I VIEW .…..….….…..mmurermeuseaenennnen sss sass ists ssn sas sss ensassnsacssees A-1
The RTU with Modems —-..........e....0eeeriiceecer ren eee e eee neeneerenernerereerenenenenenenarecnenvacenenes A-1
The RTU_PRG -- Overview ....................meancccccenerencecerer ener ee reo cecen eran ncecere nn nanercanereneoaeneneceraeee. A-1
RTU_PRG.BAT LL EEE A-4
Appendix B - CommandS SUMMATY .……………eremeemsenmenmeanenançennnennnennnnnnnnaennnnnnnnnnnnnnnnnnnennnn B-1
Appendix C - Hex-ASCII-Binary CONVEFSION .………………vcccnceecenemmenmnçenssnnnnnnnännnnnnntnanñnnnçtnçnnnennnnnns C-1
Appendix D - RTU-RTS OPTION .…….…—…rmereemenmemnnsnnennnnnnnnMnnnnnnnennnnnnnnÛnnnûnMntMnbfMnmntnnmnmnnennnnünnennns D-1
Appendix E - Modem Connections .........—.-==..en.eseerneceseneeeneeenne Aer n retener ee ncennaeneeo nee nceacco entreno. E-1
Page 1
С!-3301-01
12/92
The RTU 3301 family of remote terminal units
provides cost-effective gathering of remote low point
count I/O. The RTU 3301 communicates with other
Bristol Babcock Network 3000 process controllers via
RS 485, modem, and radio interfaces.
The unit features user-selectable operating param-
eters to accommodate installation under a wide
variety of field conditions.
This is the user's manual for both the standard and
the Programmable RTU. It consists of:
* A description of the RTU's physical and
operational characteristics;
e An overview of Bristol Babcocks” RTU soft-
ware, and the unit operational commands and
options;
о А list of RTU performance and functional
specifications.
e À set of instructions for unit calibration;
e Information pertaining to unit installation;
À description of RTU operation, including a
summary of the unit's Operational Commands.
e À list of items for which to check when trou-
bleshooting the RTU;
* Four appendixes, with information pertaining
specifically to the configuration of RTU's
equipped with PRG Option, quick-reference
tables of RTU Commands, and a Hex-to-
Binary-to-ASCII conversion table, and informa-
tion on RTU's with the Radio Modem Option.
User's Manual Conventions
The text of this manual includes special NOTES and
CAUTIONS. NOTES assist the user in avoiding
inconveniences in the setup and use of the RTU.
CAUTIONS warn against practices that might result
in damage to the unit.
The data acquisition system Host device, “Host” for
the purposes of this manual, is assumed to be a
Bristol Babcock DPC33XX Controller; an IBM PC; or
an IBM-compatible PC clone. Any micro-processor-
based device capable of sending and receiving
ASCII via an asynchronous (serial) communications
port can also be used.
References to “DOS”, as in “DOS commands” and
“DOS operations”, in this manual are to facilities
available in an IBM or IBM-compatible version of the
PC Disk Operating System software package, such
as Microsoft's MS-DOS.
Page 2
C1-3301-01
12/92
The RTU 3301 family of Remote Terminal units is
designed for data acquisition of Remote Low Point
Count 1/O. The RTU 3301 communicates with other
Bristol Babcock Network 3000 controllers via RS 485
modem, and Radio Interfaces. The flexibility of the
RTU 3301 also allows it to easily interface to other
microprocessor based equipment and personal
computers with a standard serial I/O port.
Package
The RTU 3301 is available in a compact ABS plastic
case. All modules are supplied with captive screw
mounting hardware which allows them to be
mounted in virtually any location or position on
panels or DIN rails.
The RTU Connections. Connections for power,
sensor input/output, and data are made using
labeled, removeable, compression-screw terminal
blocks located on the unit front panel.
Mounting Backplanes. The BP-8 and BP-14 are 8
and 14 channel mounting backplanes for RTU
3301s. The backplanes accept any RS-485 analog
input or analog output modules and are designed to
be mounted in standard 19-inch racks. RS-485
modules are used because RS-485 is the preferred
communications standard for high channel count
applications. Although analog modules are used, it
must be noted that every module has some digital |/
O capability. Therefore, the combination of modules
with the backplanes make a cost effective high
density remote analog and digital data acquisition
system.
The BP-8 and BP-14 reduce wiring costs by provid-
ing all common connections on the backplane. Each ~~
backplane includes screw terminals for all inputs,
outputs, power connections, and communications
signals. The backplanes also include swaged thru-
hole standoffs for mounting, a hold-down bar, and
holes for an RS-485 termination resistor.
There are no external or internal controls for the
RTU. All settings and operational trimming adjust-
ments are made using the provided menu-driven
utility software or ASCH commands from a Host.
Configuration and operating parameter settings are
stored in the unit's non-volatile memory; saved even
in the event of a power interruption or loss.
Operational Characteristics
The RTU can be ordered in any of six standard
configurations. Units are referenced according to
which of the six types of signal that they process.
The standard RTU configurations are:
e Voltage Input,
e Current Input,
* Thermocouple (T/C) Input,
* Resistance Bulb, or Resistance Temperature
Detector (RTD) Input,
o Frequency Input,
e Discrete Input/Output.
Additional Input/Output Connections. With the
exception of the RTD Input model, all standard
configurations provide for connection of at least one
discrete input. This capability can be put to use as
an event counter, or in sensing the state of a remote
limiting or safety relay.
All RTU's, except for RTD and Frequency units, also
provide at least two discrete output connections.
These function as open collector, transistor switches
controlled by the Host.
The Operation Section of this manual has more on
the uses and functioning of the available discrete
terminals of the RTU.
Page 3
C1-3301-01
12/92
RTU Communications. Each unit receives com-
mands from, and transmits data to the Host via a
single wire pair, factory-set for either RS-485 or
RS-232C. RS-485 communications are well suited
to multi-drop installations. RS-232C lends itself to
“daisy-chained” arrays. Either type of unit functions
equally well in either single- or multiple-unit settings.
In a system of RS-232C units, it is possible to
connect up to ten “daisy-chained” modules over
distances of two-hundred feet.
In units configured to use RS-485 communications,
multi-drop schemes may be used to connect as
many as thirty-two RTU's, at distances to the Host as
great as ten-thousand feet.
Several types of repeaters, converters, and modems
are available from Bristol Babcock. These compli-
ment the use of RTU's in simple data acquisition
systems by making it possible for as many as one-
hundred-twenty-four units and a single Host to
exchange data and commands over a single commu-
nications link at virtually unlimited distances (using
telephone lines and modems).
NOTE
The number of units, and the distance
separating them in your application, will
depend upon several operational and
environmental factors. These include the
number of units installed, the baud rate
selected, ambient electronic noise, etc.
Refer to the Installation Section and the
RTU Specifications listed in table 1 for
details, or consult your Bristol Babcock
Sales Representative.
Bristol Babcock’s RTU Utility
Software
The RTU 3301 Utility software is an easy to use
program that allows configuration of the RTU. It is
presented in menu format with entries for
configuration parameters such as baud rate,
Address, alarm limits, alarm type, scaling ranges,
etc. based on module type and options.
In addition, the software can be used to provide
dumb terminal communication between the RTU and
the PC through a set of ASCII commands.
One diskette is supplied with each order shipped. It
is not copy protected or licensed per computer. It
may be copied and used by anyone in your
company. Additional copies are also available from
Bristol Babcock on either 3-12" or 5-14" media. The
format is low-density, non-protected, for use with IBM
compatible PCs running under DOS.
RTU ASCII Commands
The RTU 3301 uses a serial ASCII communication
protocol for interfacing to the DPC 3330/DPC 3335
process controllers. Serial ASCII, being a common
and easy to implement protocol, allows the RTU
3301 to interface with many other host devices that
support ASCII.
In order to simplify the communication interface
between the DPC 33XX and RTU 3301, Bristol
Babcock has implemented the protocol in a
DPC33XX communication PROM.
Therefore, knowledge of the ASCII command
language is not required for use in a typical Bristol
Babcock Network 3000 system. The ASCII
commands are useful for testing individual modules
and for writing custom drivers for other host sytems.
NOTE
Technical support related to the operation
of the RTU in any custom programs or
applications is limited to the material
covered in the User's Manual and the
Programmer's Guide only.
Page 4
CI-3301-O1
12/92
Options
The User-Programmable Transfer Function (PRG)
This enables the RTU to be programmed to work
with non-linear sensor data, such as square root, nth
root, nth power, and high-order polynomials. With
RTD and T/C RTU's automatic linearization is
provided as part of the standard unit; the PRG
Option is not necessary.
PRG-equipped units can also scale and convert data
to user-set engineering units, and can be pro-
grammed using real-time input from sensors.
PRG-equipped units are compatible with standard
RTU's. Both PRG- and non-PRG-equipped units
may be configured in any combination in your
application.
Appendix A of this manual consists of a more
detailed description of the PRG-equipped RTU, and
provides information on its configuration and opera-
tion.
Radio Modem Operation
This option is required for applications that call for
the connection of a single analog input ВТО 10 а
radio modem, leased line, or dial-up modem with no
auto-answer capability. The option enables the RTU
to generate a Request to Send (RTS) signal, used by
these devices as a prompt. Appendix D contains
intructions for the use of the Radio Modem Operation
Option.
Continuous Mode Capability
With standard RTU configurations, each unit requires
a prompting command from the Host in order to
transmit any data or operational response. If an
application calls for a unit to provide data without
having to be prompted by the Host, the Continuous
Mode Operations Option, “C”, should be ordered.
With the “C” Option, units begin to send data as soon
as the appropriate triggering input is detected. This
setup is particularly useful in applications calling for
continuous module-to-module communications, such
as when a C-equipped analog input module is
connected to a Continuous Mode configured analog
output module.
Discrete RTU's have Continuous Mode Operations
capability offered as part of the standard unit. To
enable Continuous Mode Operations, the user
selects one of four Continuous Mode types which
control the circumstances under which Discrete units
are triggered.
Page 5
CI-3301-O1
12/92
Table 1. RTU 3301 Performance and Operational Specifications
Characteristic
Unit
Type
Specifications
Input
Voitage
Current
T/C
RTD
Freq.
All
Units
Factory-set range: —100 to 100 mV, —1 to 1 V, —5 to 5 V,
10 to 10 V, and —100 to 100 V, dc.
Protection: to 250 Vac.
Two additional discrete outputs and one additional discrete input
connection available.
Factory-set range: —1 to 1 mA into 1000, —10 to 10 mA into 100,
-100 to 100 mA into 1Q, and 4 to 20 mA into 52.
Voltage Drop +0.1 V, maximum.
Two additional discrete outputs and one additional discrete input
connection available.
Factory-set T/C Type: J, K, T, E, R, S, B, or C. Any span within the
following ranges is user-programmable (Note accuracy specification,
under Performance):
For J-type: —200 to 760 °C (-328 to 1400 °F),
For K-type: —150 to 1250 °C (-238 to 2282 °F),
For T-type: —200 to 400 °C (-328 to 752 °F),
For E-type: —100 to 1000 °C (-148 to 1832 °F),
For R- and S-types: O to 1750 °C (32 to 3182 °F),
For B-type: O to 1820 °C (32 to 3308 °F),
For C-type: O to 2315 °C (32 to 4199 °F).
°C or °F is user-programmable. All units incorporate automatic cold-
junction compensation and automatic linearization.
Two additional discrete input and three additional discrete output
connections available.
Protection: to 250 Vac.
RTD Type: Factory-set as two-, three-, or four-wire, 100Q platinum.
OL = 0.00385 Q/Q/°C.
Any span within —200 to 850 “C (-328 to 1562 °F) range is
programmable, as is °C ог °F.
Protection: to 120 Vac.
One additional discrete output connection available.
Customer-specified range. Any span from 1 Hz to 20 kHz.
Protection: to 250 Vac.
One additional discrete input connection available.
Analog Input: Single Channel, auto-zero (+1 count drift, maximum),
auto-calibrating.
Maximum CMV: 500 V rms, input to output € 60 Hz.
Discrete Inputs: 8-bit CMOS. User-selectable scaling and calibration.
Voltage Limit: +30 V
Up to 15 connections available with Discrete RTU.
Output
. Alarm
Signals
Discrete
Terminals
T/C
All
Units
. HILO Trip Point values user-programmable; stored in unit non-volatile
memory. User-programmable for Latching or Momentary operation.
Open-collector transistor capable of sinking 100 mA (30 mA on analog
modules). Maximum output voltage: 30 V.
Switching: High @ 3.5 V, minimum; Low 1.0 V, maximum.
Open T/C and over range indication.
Factory-set for RS-232C or RS-485 communications.
Up to 32 RTU's may be connected in a multi-drop, RS-485 System.
NOTE: Table continued next page.
Page 6
C1-3301-01
12/92
Table 1. RTU 3301 Performance and Operational Specifications (continued)
Characteristic Unit Specifications
Type
Power All Units 12 to 30 Vdc; 1 Watt, maximum.
Internal switching regulator protects against power supply reversals.
Communication All Units ASCII command/response protocol; User-programmable unit address.
Software scans up to 250 channels per second from host.
Range: Up to 10,000 feet, depending upon selected communications
standard, baud rate, and number of units in system. Greater distances
possible with modems and converters (refer to Installation and Operation
Sections).
Baud Rate: User-programmable; 300, 600, 1200, 2400, 4800, 9600,
19200, or 38400 baud.
Parity: User-programmable; odd, even, or none.
Event Counting All Units” Records 10, 000, 000 positive transitions @ 60 Hz, maximum. Filtered to
prevent switch contact bounce. * NOT AVAILABLE with RTD model.
Performance Analog Resolution: 15-bit measurement, with 8 conversions per second.
Input Leakage Current: <2 pA mms, input to output, @ 115 V rms, 60 Hz.
Discrete Switch Points: High - 3.5 V, minimum; Low - 1.0 V, maximum.
Inputs/ Filtering: User-programmable time constants from 0 to 16 seconds.
Outputs
Voltage Resolution: 0.01% of full-scale (4 digits).
& Accuracy: 10.02% of full-scale, maximum.
Current Common Mode Rejection: 100 dB @ 50/60 Hz.
Inputs Impedance (Voltage): For inputs of ~1 to 1 V or less, 100 MQ.
For inputs of —5 to 5 V or more, 1 MQ.
T/C Resolution: 1 °C or °F.
Inputs Accuracy (error from all sources @ 0 to 40 °C, ambient): +1 °C,
maximum (J, K, T, E); 2.5 °C, maximum (R, S, B, C).
impedance: 100 MQ, minimum.
Lead Resistance Effect: Less than 20 uV per 3500.
RTD Resolution: 0.1°C or °F.
Inputs Accuracy: 30.3 °C.
Excitation Current: 0.25 mA.
Lead Resistance Effect: For three-wire units, 2.5 °C per Q of
unbalance. For four-wire units, negligible.
Freq. Resolution: 0.01 Hz.
Inputs Accuracy: 0.005% of reading, £0.01 Hz.
impedance: 1 MQ.
Switching Level: User-programmable for 0 ог 2.5 М.
Hysteresis: User-programmable for from 10 mV to 1 V.
Environmental Voltage Effect of Temperature: +0.005% of span per °C change, maximum.
Ratings |
9 Current Effect of Temperature: +0.005% of span per °C change, maximum.
RTD Effect of Temperature: +0.002% of span per °C change, maximum.
Freq. Effect of Temperature: +0.002% of span per °C change, maximum.
All Units Ambient Operating Range: —25 to 70 °C (-58 to 158 °F).
Ambient Storage Range: 25 to 85 °C (-58 to 185 °F).
Relative Humidity: 0 to 95%, noncondensing.
NOTE: Refer to Installation Section of this manual for mounting dimensions of the RTU.
Page 7
C1-3301-01
— 12/92
Every RTU manufactured or serviced by Bristol
Babcock is calibrated and tested for compliance with
our strict quality control guidelines. Each unit is
guaranteed to perform according to specification
without requiring any undue adjustment.
A bench check of unit settings and basic operation is
suggested, however, prior to the unit's being placed
into service, so that the existence of any damage to
the unit resulting from mishandling during shipment
may be uncovered.
A bench check also provides the user with the
opportunity to become familiar with or change the
factory's default RTU settings in an environment
isolated from the application.
The calibration of the RTU consists of:
* Connecting the unit in its Default Mode,
e Conducting a basic operations Bench Check,
o Using the Utility program to view or change the
unit communications and operating parame-
ters,
» Checking or changing the Host's communica-
tions parameters.
NOTE
A brief explanation of the Setup com-
mand, $1SU, is included in this manual in
appendix B. This is for those users who
may find it more desirable or efficient to
program the RTU “directly”, bypassing the
Utility program. Additional command-
level information also is provided in the
RTU 3301 Programmer's Guide.
Calibration Setup
It is recommended that the RTU be calibrated at a
technician's bench. In addition to basic terms and
concepts of electronics calibration, persons carrying
out these procedures should be familiar with some of
the basic disk operations of an IBM PC or PC clone,
and the DOS or MS-DOS environment.
Users of Bristol Babcocks RTU 3301 software will
need to know enough about both their Host device
and DOS to enable them to activate a drive/change
to a different drive, copy/“backup” files from the
source diskettes, and to locate and run batch and
other executable files under DOS.
The equipment listed in table 2 will be needed to
perform the RTU Calibration/Bench check.
In order to calibrate the RTU, you will need to be
familiar with the RTU 3301 Utility software described
later in this manual.
Hookups. Figures 1, 2, and 3 show the hookups for
the bench check/calibration of each type of RTU.
Table 3 lists the abbreviations used on the terminal
labeling. When completing the hookups, match the
terminal numbers from the figures to the correspond-
ing terminal numbers in the table.
Figure 1 shows the hookup for RTU's factory-
configured for RS-232C communications, Figure 2
shows the hookup for RS-485 units to a Host РС,
and Figure 3 shows the hookup required for RS-485
units to a non-PC Host device (a “dumb terminal’
using a break-out box, for example). The HP-style
RTU is not depicted in the hookup diagrams, but the
terminal numbers are the same for either type unit.
Page 8
C1-3301-01
12/92
Table 2. RTU Calibration Equipment
Equipment Specification
Host Device ¡BM PC XT, AT, PS2; 100% compatible clone; or compatible “dumb terminal”
running IBM or MS DOS version 2.0 or higher. Unit should also include, a
minimum of: 384K of RAM; monochrome, text-capable monitor (color also
supported); and one asynchronous (serial) communications port (COM1: or COM2).
Microsoft, or compatible mouse is supported, but not required.
Ensure that device is capable of ASCH output to its COM port, either through BASIC
or some comparable application or environment. For communications with RTU's in
the Default Mode, the Host should be set for 300 baud, no parity, no echo. Refer to
the manufacturer's specifications for the device being used for instructions in
configuring the unit as required.
If the Utility software is to be used, Host must include one low-density (360K) or
high-density (720K) floppy drive (5.25 or 3.5 inch, as appropriate).
Interface Cable Standard PC communications cabling with one end terminating in a 9- or 25-pin
connector that is compatible with the port of the Host being used. The other cable
end should terminate in stripped wires that will be inserted into the RTU connection
terminals, or that otherwise can be used with the compression-screw terminals of
the RTU being checked.
Power Supply Calibrated, and capable of stable output between 12 and 30 Vdc.
Screwdriver Slotted type; head width no greater than 2.54 mm (0.1 inch).
Signal Calibrated, adjustable source compatible with the configuration of the RTU to be
Source checked. For example, a source of 4-20 mA for Current RTU rated for 4-20 mA
(Optional™) input, or a calibrated thermocouple simulator of appropriate type and range for a
T/C RTU.
Accuracy of the Signal Source must be at least 10 times the rated accuracy of the
RTU—at least .005% accuracy.
*Required for trimming span or zero.
Before beginning the bench check of the RTU,
determine which of the hookups depicted in the
figures applies to the units in your application, and
complete the connections. Apply power to the
hookup, and allow 5 minutes for stabilization/warm-
up.
The RTU Default Mode. The hookups shown in
figures 1 through 3 depict the RTU in what is referred
to as its “DEFAULT Mode”.
Whenever the DEFAULT terminal of the RTU is
connected to ground in the manner shown in the
figures, the unit will enter DEFAULT Mode, which
over-rides any communication settings stored in the
units memory. This allows the user to communicate
with the unit via a predetermined COM port, at a
preset baud rate and parity setting.
Also when in Default Mode, RTU's respond to any
“legal” address (explained later in this manual).
Normally, when the address, baud rate, and parity
settings are not known and not compatible with the
settings of the Host, the unit will not communicate.
The Default Mode feature is ideal for use with RTU's
when record of configuration data has been lost.
Page 9
CI-3301-01
12/92
Table 3. RTU Terminal Labeling
Type of ;
Left Right
RTUL Terminals Terminals
1 2 3 4 5 6 7 8 9 10 11 12
VOLTAGE XMT RCV
& +IN —IN | DO1/HI) Dio/ | DOO/ | DEF See See +VS GND Not Not
CURRENT EV LO Note 1 | Note 1 Used | Used
XMT RCV
T/C DO2 БН | DO1/HI} Dig/ | DOS/ | DEF See See +VS GND —IN +IN
EV LO Note 1 | Note 1
XMT RCV
RTD C B A D DOO/ | DEF See See +VS GND Not Not
LO Note 1 Note 1 Used Used
XMT RCV
FREQ. IN +2.5V SIG |¡HYSTR| DIO/ DEF See See +VS GND Not Not
XMT RCV BO6
DISCRETE | В©4 ВОЗ BO? BO! ¡BOD/E DEF See See +VS GND BO5 See
у Note 1 | Note 1 Note 2
NOTES: 1. For RS-485 RTUs these terminals are labeled with a wire color code and the word “DATA”,
as in “(Y)DATA” and “(G)DATA”. RS-485 communications are in parallel, and thus do no
require specific Transmit and Receive connections.
2. Discrete RTUs have an additional 10 terminals. Terminals 13 thru 20 are labeled “B@7,
BOS, BO9, BOA, BOB, BAC, BAD,” and “BAD”.
Key to Abbreviations:
DATA - Receive or Transmit to system host. Used on RS-485 RTU's, these terminal designators are accompanied by
abbreviations for the wire colors commonly used in making this type of connection, i.e. standard 4-wire telephone line. The
abbreviations used for the colors are (B) for black, (G) for green, (R) for red, and (Y) for yellow.
DEF — Default. This terminal may be connected to ground to place the unit in its Default Mode of operation.
Di — Discrete Input. -IN — Negative Signal Input.
DI@G/EV— Discrete Input/Event Counter RCV — Data Receive. RS-232C hookups.
DO — Discrete Output. SiG GND — Signal Ground.
DOS/LO- Discrete Output/Low Alarm. A, B, etc. — RTD Sensor Input.
DO1/HI—- Discrete:Output/High Alarm. +VS- "Positive Voltage Source Input.
GND — Power Supply or Discrete Output Ground. XMT — Data Transmit. RS-232C hookups.
HYSTR- Hysteresis +2.5V — Excitation Voltage.
+IN— Positive Signal input.
Page 10
C1-3301-01
12/92
+10 to +30V dc 3
POWER SUPPLY ® LIN
® IN BRISTOL
-Q + ® | | nova BABCOCK
D DIS/EV CURRENT
® DOZ/LO RS-232C
® DEFAULT*
© (> | | TRANSMIT
® RECEIVE
D +VS
$ o ® | [gw
000000000000000
O doo0e60/ O
00000000000000
TO HOST COM PORT CONNECTOR (RS-232C)
+10 to +30V dc | |
POWER SUPPLY O 1 NS A
® HN BRISTOL
- IN
-O + ® DOI BABCOCK
® DIG/EV CURRENT
@® | |poeno RS-232C
ф () | ¡DEFALLT*
a TRANSMIT
O RECEIVE
® +VS
GND
e D | |w
GET)
TO HOST COM PORT CONNECTOR (RS-232C)
Figure 1. RS-232C RTU-to-PC Calibration Hookup, 25-Pin and 9-Pin Connectors
Page 11
C1-3301-01
12/92
+10 to +30V de
POWER SUPPLY
-Q +0
O
O00000006000660
O do00883/ O
O0000000000000
0900000060
1
+iN
- IN
DOVHI
DIO/EV
DOBRO
DEFAULT"
(Y) DATA
(G)DATA*
(R)+VS
(BYGND
10
TO HOST COM PORT CONNECTOR (RS-232C)
+10 to +30V de
POWER SUPPLY
-0 +0
000000008000®9
00000000600085
©
3/0
00000006
1
+IN
- IN
DO 1/HI
DIS/EV
DOB/LO
DEFAULT*
(Y) DATA
(GIDATA*
(R}+VS
(B)GND
10
TO HOST COM PORT CONNECTOR (RS-232C)
BRISTOL
BABCOCK
CURRENT
RS-485
©
BRISTOL
BABCOCK
CURRENT
RS-485
Figure 2. RS-485 RTU-to-PC Calibration Hookup
Page 12
C1-3301-01
12/92
©
HOST DO (0) D om BABCOCK
RS-485 DO (G) D | bey CURRENT
GND (В) ® DOB/LO AS-485
® |} DEFAULT"
® (Y) DATA
M | |(a) DATA"
® | [Rvs
è 6 ® | |® GND
+10 to +30V de - |
POWER SUPPLY
* уме (В)
Figure 3. RS-485 RTU-to-Non-PC Calibration Hookup
When in DEFAULT Mode, every standard RTU will
communicate with the Host using the following
parameters:
» Host's COM1 Port Active
* 300 Baud
e No Parity
* Echo OFF
e Responding to any “legal” address
The only requirements for communicating with an
RTU in Default Mode are that the appropriate
communications format be used (RS-232C or
RS-485), and that the Host's communications
parameters be compatible (300 baud, COM1, etc.)
with the Default Mode parameters listed above.
Page 13
C1-3301-01
12/92
RTU Utility Software Calibration
Procedure — Basic Operations Bench
Check
1. Place Host keyboard in “Caps Lock’. Enter
commands from terminal mode in Utility soft-
ware.
2. With Calibration Setup complete, enter RTU
“Read Settings” command on Host: |
$1RS.
Unit will respond with readout of its Module
Settings Code. The Module Settings Code
portrays the current settings of all the RTU user-
modifiable operating parameters accessible in
the Utility program. Table 4 lists acceptable
Module Settings Codes for standard RTU's as
they are set when shipped from the factory.
For purposes of this bench check, the meaning
of the codes used in the RTU “Read Settings”
command, and the response to $1RS is not
significant. The Operation Section of this manual
provides more information on the RTU Com-
mand/Response format. For now:
3. Note response to the “Read Settings” command
for future reference.
4. Verify that the first character of response is an
asterisk(*).
If it is, skip to step 5 of this procedure. If re-
sponse begins with question mark (“2”), an error
has occurred. Perform the following:
a. Check all connections. Ensure that correct
hookup was used.
b. Make sure Host is using COM1 port at 300
baud, with no parity, and no echo. Set
these Host operating parameters using the
DOS command “MODE”, or refer to the
section in this manual on starting the Utility
program.
c. Ensure that power supply is operating
within specified range (refer to table 2).
Table 4. Factory Settings — Responses to $1RS
Unit Input RTU
Type Range Response
—100
to 310701C2
100 mV
—
to 31070182
1V
Voltage —5
to 31070142
5V
—10
to 31070142
10V
— 100
to 310701C2
100 V
—1
to 31070182
1 mA
~10
to 31070142
Current 10 mA
—100
to 31070102
100 mA
4
to 31070102
20 mA
TIC All 31070142
Types
RTD ~All 31070182
Types
Freq All 310701C0
Types
Discrete All 31070102
Types
Page 14
C1-3301-01
12/92
Calibration
d. Repeat steps 1 and 2 of this procedure.
If problems persist, note the unit model and
serial numbers, and contact Bristol Babcock's
Applications Support Group.
5. Verify that unit is correctly configured according
to the specifications of your order. Match RTU
response noted in step 3 to number in column 3
of table 4. Check the unit's model number
against the data derived from the table. If
response does not match any of the numbers in
table 4, contact the factory.
When steps 1 through 5 of the Basic Operations
Bench Check have been successfully completed, it
may be assumed that the RTU being checked is in
good working order. Optionally, the input/output
terminals may be checked using the following
procedure, or if desired, the user may skip to the
section entitled “Setup for RTU & Host Configuration”
for instruction on setting initial RTU and Host
communications and operating parameters.
Optional Input Terminals Bench Check. The
following steps check for proper RTU
communications between the Host and the input
terminals of the unit.
1. Without disconnecting DEFAULT terminal of
RTU from ground, simulate appropriate signal
source. Refer to table 2 for input signal specifi-
cations.
2. Enter “Read Data” command:
$1RD.-
Unit will respond with appropriate readout of
signal input, +0.02% of rated span.
3. Change level of signal source, keeping within
specified limits.
4. Repeat step 2. Unit again responds with appro-
priate readout of signal input.
5. Disconnect signal input and re-enter “Read Data”
command.
6. Verify that unit responds with over-range read-
out; all zeroes or all nines.
7. lf the RTU does not function as described in this
procedure, e.g. it returns a communications
error, refer to the Troubleshooting Section of this
manual.
Refer to the Operation Section of this manual for
information on zero offset, deviation output setpoints,
and trimming span.
NOTE
Do not dismantle the hookup used in this
portion of the calibration. The same
equipment and hookup can be used to
perform the next phase of
RTU calibration.
RTU Configuration —
The Utility Program
The next step in the calibration of the RTU is setting
the unit's basic operating parameters. This is
accomplished in three steps. First, the Utility pro-
gram is loaded. Next the Host communications
parameters are checked and set. Then the RTU
parameters are viewed and changed.
If desired, the Utility program can also be used to
execute RTU Operational Commands, or to verify
that the settings changes made in the Setup portion
of the program have been down-loaded to unit
memory.
If already familiar with the RTU Module Designator,
the basic Command/Response Format, and the RTU
“Setup” command, skip the following phase of RTU
calibration, and execute/verify changes to unit
operating parameters using the information in
appendix B.
NOTE
To perform the Configuration phase of
ATU Calibration, use the same equip-
ment and hookup from the Basic Opera-
tions Bench Check.
See figures 1, 2, or 3.
Page 15
C1-3301-01
12/92
RTU Utility Software
Installing Utility
RTU 3301 basic operating parameters are set using
the Utility program included with each shipment. The
floppy diskette labeled RTU 3301 “Utility Software”
comprises the Utility batch file, the executable files
invoked by that batch program when it is run, and
additional Auxiliary programs, discussed later.
Make a “working copy” of the Utility software before
loading and using it. Use the copies to complete the
procedures in this section. A hard disk, if available,
is the preferred location for storing and running the
programs. The original diskette should be stored as
a backup copy in a cool, dry place.
CAUTION
Exposing floppy diskettes to electrical or
magnetic fields may result in the loss of
data. Stored diskettes should be kept
away from extremes in heat and mois-
ture, and should be protected against
static discharge and magnetic fields.
Use the DOS command “DISKCOPY” to perform the
backup. Refer to the Reference or User's manuals
of the DOS version being used for more information
on DISKCOPY and other methods of backup.
NOTE
The remainder of this section pertains to
non-PRG RTU's exclusively. For setup
instructions pertaining to RTU's equipped
with the PRG Option, refer to the RTU-
PRG Features section of this manual.
Once the source diskettes have been backed up,
and with the proper Bench Check/Calibration hookup
in place, switch to the drive (or drive partition) where
the working copy of the file “RTU.BAT” is stored, or
insert the appropriate working diskette.
Enter:
RTU.BAT
After briefly displaying a “logo screen” with the
program title and “Bristol Babcock”, the program's
Main Menu window will appear. The program is now
loaded into the Host's RAM.
NOTES
The Utility program is supported by most
color monitors, graphics adapters, and
drivers. A color monitor is not required to
run the program, but some adjustment to the
contrast and brightness setting of mono-
chrome screens, particularly if running the
program on a laptop, may be necessary.
If no other batch programs named “RTU”
are stored on the drive/partition, it is not
necessary to enter the “BAT” extension.
Once loaded, the Utility program activates the Host
device COM1 port, and sets it to 300 baud with no
parity and no echo. This over-rides any setting
effected by the Host's boot program (autoexec.bat or
config.sys), and any setting initiated by use of the
DOS command “MODE”.
Getting Around in Utility
With the program's Main Menu window on the Host's
monitor screen, the version number of the program is
shown in the upper left corner. À bar with the five
available Actions is across the top, and along the
bottom edge, the Help (<F1>) and Navigation Keys
are shown.
NOTE
If your display does not appear as
described here, refer to the Trouble-
shooting Section of this manual.
Making Selections — Pop-ups. There are three
ways to get around in the Utility program; by Mouse,
by mnemonic, or by moving the Selection Highlight
Cursor.
If using a mouse, move the pointer, usually a dia-
mond shape on the screen, to the desired Action,
“and “click”. The appropriate “pop-up” screen will
come up.
NOTE
A mouse is not required to run the Utility
program. Support for most Microsoft-
compatible mouse drivers is incorporated
into the Utility.
Page 16
C1-3301-01
12/92
An alternative to mouse-based selection is the
mnemonic. Press the highlighted first letter of the
desired Action to access it.
“S”. for example, accesses the Address and Model
entry pop-up, which is the security level of the unit
Setup. “M” accesses the Miscellaneous pop-up,
where the Terminal Simulation and the Rx/Tx
Facilities are found. “F” brings up the File functions;
and “Q” is for Quit.
As an alternative to either of these methods, an
Action can be selected by moving the Selection
Highlight cursor, the selection box that appears over
one of the items in the Actions bar when the program
first comes up.
To use the Selection Highlight, press the “number
lock” (“Num. Lock” on some keyboards), then use the
cursor control keys on the number keypad. Or use
the dedicated cursor keys in the manner described in
the Navigation Bar at the bottom of the screen (no
“Num.Lock” required).
On number keypads, 4=<-, 6=—, 8=1, and 2=J.
When the Selector is highlighting the desired Action,
press J to access the desired pop-up (start the
selected “Action”).
NOTE
On the Main Menu window, the UP and
DOWN cursor keys serve the same
function as À
(refer to the preceding paragraph).
Cancelling Selections — Escape. To cancel a pop-
up selection, or to escape from any window to the
Main Menu window, press the Escape key (“Esc.” on
most keyboards), or press the right-most mouse
button.
Context-Sensitive Help
The first item at the left of the Navigation Bar at the
bottom of the screen is “<F1> Help”. This is the
Utility program's “on-line” reference aid. It consists
of brief explanations keyed to the item or action
underway (highlighted) at the time the <F1> (<PF1>
on some terminals) key is pressed.
To use Help, select an item/action as described
above, and press the <F1> function key. A brief
explanation of the selected item will appear. If using
a mouse, click the item, then click on “Help” in the
navigation bar.
When a pop-up is active, press <F1> again, and a
“Table of Contents” for the Help system will pop-up.
Highlight (click) a topic to select it, and press to
access the help text.
Some Help screens contain more information than
can be fit into a single window. Use the Page Down
and Page Up keys to access the other screens of
information.
Quitting Help. Escape from the Help pop-ups at
any time by pressing Escape, or the right-most
mouse button.
“Host” —
Configuring the Host in Utility
The first Action to access when configuring the RTU
is “Host”. If the connected RTU and the system Host
cannot communicate with each other, settings will
not be downloaded to the unit. Remember, when the
RTU's are installed in multi-unit applications, unless
the communications parameters for both the Host
and all connected RTU's are the same, particularly in
daisy-chained systems, as soon as a single unit's
Default Mode is disconnected, all communications
“Will be lost.
In a multi-drop system it is possible to configure each
RTU with a different baud rate. Although it may
seem to provide organizational advantages (one unit
or a group of units configured to respond at one baud
rate, and another unit or group configured to respond
at another) this technique requires careful documen-
tation for all units.
Page 17
Ci-3301-01
12/92
To access the communications parameter settings
for the Host, select “Host” at the Main Menu window.
The Host Communications Parameters pop-up will
appear.
Inputting Data/Getting Around in Host. The menu
bar at the bottom of the pop-up has the instructions
for making changes to the data in the various input
fields in the pop-up. Note that the context-sensitive
Help system is available.
To move from field to field, use the Tab key, —, the
down/up cursor controls, or select the desired field
with the mouse.
If the connected RTU is in its Default Mode, choose
300 Baud, No Parity, and No Echo. These settings
should be selected when the pop-up first appears.
If the connected RTU is not in its Default, pick the
baud rate for the Host that is compatible. The
navigation bar at the bottom of the pop-up describes
how to select the baud rate options.
When all of the Host's parameters have been set,
press Escape (Esc.) to load the input and return to
the Main Menu window.
“Setup” —
Configuring the RTU in Utility
When the Host parameters are set to be compatible
with the connected unit, the next step in calibrating
the RTU is to bring up its basic operating settings in
the “Setup” window of Utility. To access Setup,
select the Setup Action from the Main Menu.
The first pop-up to appear is a security window for
entering the Address and Model Designator of the
connected unit. If the connected RTU is in its Default
Mode, the first input field, the address, is irrelevant
since units in Default Mode respond to any address.
If calibrating the connected module in its actual
operations mode, however, the correct unit address
is required, and if omitted, will result in a TIME-OUT
or COMMUNICATIONS ERROR.
NOTE
If the address of an RTU is unknown,
place the unit in its Default Mode and
access “Setup” in the Utility program.
With the appropriate address showing in the input
field, press |.
The next field is for the Module Designator Code.
Table 5 lists all Module Designator Codes according
to RTU type. Refer to the model descriptor, (i.e.
D1251) on the unit(s) you ordered and enter the
code in the appropriate field of the pop-up (Don't
enter the 'D' prefix).
With the correct data shown in the input fields,
press ed.
If the unit is not connected properly, if the correct
Module Designator Code is not entered, if the unit is
not in Default Mode and an incorrect address was
used, a pop-up with an error message will come up.
Before going on, press Escape (Esc.) to return to the
Main Menu window. Take steps to isolate and
correct the problem before attempting to establish a
Setup session with the unit.
If there are no Error Messages, the program displays
a status pop-up while it reads the basic operational
settings of the connected unit. The next pop-up is
the full screen edit session of those settings.
NOTE
It is possible to enter a Setup session
after encountering an error at this point in
the procedure. Any changes made to the
operating parameters in the session WILL
NOT be down-loaded to the memory of
the unit.
Inputting Data/Getting Around in Setup. The
menu bar at the bottom of the pop-up tells how to
enter new parameters in the input fields of the
settings edit session. The Utility programs on-line
Help system is active here too. Any questions on the
input fields in the session can be answered by
placing the selector on the field and pressing <F1>.
To move from field to field, use the Tab key, 9, the
down/up cursor controls, or click the desired field
with the mouse.
When all input fields reflect the desired operating
parameters, press <F10>. This sends the new setup
data to the connected module, and brings up the
pop-up prompting for a Module Reset.
Page 18
CI-3301-01
12/92
Table 5. RTU Model Designator Codes
input Input Model
Type Range Designator
—100 to 100 mV in RS-232C 1111
—100 to 100 mV in RS-485 1112
—1 Vto 1 Vin RS-232C 1121
—1 V to 1 Vin RS-485 1122
—5 to 5 V in RS-232C 1131
—5 to 5 V in Rs-485 1132
—10 to 10 V in RS-232C 1141
—10 to 10 v in Rs-485 1142
--100 to 100 V in RS-232C 1151
—100 to 100 v in RS-485 1152
Voltage —100 to 100 mV w/PRG Option in RS-232C 2111
—100 to 100 mV w/PRG Option in RS-485 2112
—1 to 1 V w/PRG Option in RS-232C 2121
—1 to 1 V w/PRG Option in RS-485 2122
—5 to 5 V w/PRG Option in RS-232C 2131
—5 to 5 V w/PRG Option in RS-485 2132
—10 to 10 V w/PRG Option in RS-232C 2141
—10 to 10 V w/PRG Option in RS-485 2142
—100 to 100 V w/PRG Option in RS-232C 2151
—100 to 100 V w/PRG Option in RS-485 2152
—10 to 10 MA in RS-232C 1211
—-10 to 10 MA in RS-485 1212
—1 to 1 mAin RS-232C 1221
-1 to 1 mA in RS-485 1222
—100 to 100 mA in RS-232C 1231
—100 to 100 mA in RS-485 1232
—1 to 1 Ain RS-232C 1241
—1 to 1 Ain RS-485 1242
4 to 20 MA in RS-232C 1251
4 to 20 MA in RS-485 1252
Current —1 to 1 mA w/PRG Option in RS-232C 2211
—1 to 1 mA w/PRG Option in RS-485 2212
—10 to 10 MA w/PRG Option in RS-232C 2221
—10 to 10 mA w/PRG Option in RS-485 2222
-100 to 100 mA w/PRG Option in RS-232C 2231
<=21 000100 MAW/PRG Option :in RS5-485 2232
—1 to 1 À wPRG Option in RS-232C 2241
—1 to 1 À w/PRG Option in RS-485 2242
4 to 20 MA w/PRG Option in RS-232C 2251
4 to 20 mA w/PRG Option in RS-485 2252
NOTE: Table continued next page.
Page 19
C1-3301-01
12/92
Table 5. RTU Model Designator Codes (continued)
input input Model
Type Range Designator
J-type in RS-232C 1311
J-type in RS-485 1312
K-type in RS-232C 1321
K-type in RS-485 1322
T-type in RS-232C 1331
T-type in RS-485 1332
T/C E-type in RS-232C 1341
E-type in RS-485 1342
R-type in RS-232C 1351
R-type in RS-485 1352
S-type in RS-232C 1361
S-type in RS-485 1362
B-type in RS-232C 1371
B-type in RS-485 1372
C-type in RS-232C 1381
C-type in RS-485 1382
RTD All input types and ranges in RS-232C 1411
All input types and ranges in RS-485 1412
Frequency 1 Hz to 20 kHz in RS-232C 1601
1 Hz to 20 kHz in RS-485 1602
1 Hz to 20 kHz w/PRG Option in RS-232C 2601
1 Hz to 20 kHz w/PRG Option in RS-485 2602
Discrete In RS-232C 1711
In RS-485 1712
A Module Reset, the “RR” command, sets the new After the Module Reset selection is made, either
baud rate into module memory. When the RTU is “Y I" or “NI”, the program returns to the full screen
removed from its Default Mode, the new baud rate settings edit session window. Another RTU can now
will be placed into effect. be connected, and its parameters viewed and
changed.
NOTE
If performing the Setup routine with the Quitting Setup. When all units have been set, press
ATU's installed, (i.e., not connected in the Escape key (Esc.) to return to the Main Menu
their Default Mode) do not reset any window.
- modules until all of the connected units,
including the Host have the same baud
rate setting. In a daisy-chain installation
(RS-232C), if the baud rate is different for
any unit in the chain, communications
with ALL units will be lost.
Page 20
CI-3301-01
12/92
“Misc.” —
Terminal Emulation in Utility
The Misc Action from the Main Menu window, when
selected, brings up the Terminal Simulator and the
Rx/Tx Facility. These can be used to send RTU
Operational Commands to the connected unit(s) to
verify the settings of RTU’s being calibrated, to check
the status of installed units, or to operate the RTU's.
Discrete I/O Module Setup
There are two fields in the utility setup menu for the
discrete 1/O module used to configure the starting
condition. The field labeled '/O assignments is a 16-
bit field that defines the 15 I/O points as inputs or
outputs. entry into this field is in Hex value. A zero
will configure a point as an input and a one will
configure a point as an output. For example:
Hex Binary 1/0 Configuration
FFFF 111111111111111 All I/O outputs
FFFA 111111111111010 1/0 1 and 3 are inputs
NOTE: all other I/O are outputs
NOTE
Commands in terminal mode are case-
sensitive. Only capital letters are recog-
nized.
Clear To Send (CTS) and Ready to Send (RTS)
support, required for some applications where RTU's
are used with certain types of modem, is disabled
when the Terminal Simulation facility under Misc.
the “dumb terminal”, is active. If CTS support is
required for a radio modem application, use the Rx/
Tx facility only.
“Quit” — Quitting Utility
To quit the Utility program at any time, press Escape
(Esc.) until the Main Menu window comes up, then
select “Quit”. A Yes/No pop-up will ask for confirma-
tion of your request, and if “Y.” is entered, the Host
will return to the last DOS prompt. À "N.” response
returns the program to the Main Menu window.
README.TXT
Additional information is provided in a text file on the
utility disk. You can review or print the file
README.TXT to obtain this information.
Page 21
C1-3301-01
12/92
installation
In most cases, it is more efficient to physically mount
the unit(s) in the application, and then to effect the
electrical and data connections.
Mounting
Figure 4 provides the outline dimensions of the RTU
3301.
Always ensure that the RTU is mounted in an area
that is relatively free of dust, excessive moisture, and
corrosives. Consult your Bristol Babcock Sales
Representative for information on protective enclo-
sures if called for in your application.
When mounting the unit, consider connecting wire
routing and terminal access. Try to ensure that all
pertinent labeling will be conveniently visible for
future reference.
4 3.60" > Leg 1.1 nd
{9 144 em) {2.794 cm)
gn ру mer
{5 842 cm)
| еееессевее | | |
| с бт
(5 020 em)
ANALOG МО MODULE
The RTUs may be individually mounted on a panel
using 6X32 nuts or standoffs. additional modules
may be piggybacked and attached using the captive
screws provided with each unit. Two mounting
backplanes are also avaialble for multiple unit
applications.
The BP-8 and BP-14 are 8 and 14 channel mounting
backplanes for RTU modules. The backplanes
accept any RS-485 RTU analog input or analog
output moduels and are designed to be mounted in
standard 19 inch racks. RS-485 modules are used
because RS-485 is the preferred communications
standard for high channel count applications.
Although analog modules are use it must be noted
that every RTU has some digital I/O capability.
Therefore the combination of RTUs with the
backplanes make a cost effective high density
remote analog an digital data acquisition system.
The BP-8 and BP-14 reduce wiring costs by provid-
ing all common connections on the backplane.
Each backplane includes screw terminals for all
inputs, outputs, power connections and communica-
tions signals. The backplanes also include swaged
thru-hole standoffs for mounting, a hold-down bar,
and holes for an RS-485 termination resistor.
607 > ha $
(9.144 em) {2.794 cm)
fr QU i
(5.842 cm)
[3050000686] С
ЕЕ til E
1112131415 1817181920
2.457
{6 223 cm)
_
1612"
{4 094 cm)
| eeececccoo]|
hz
198"
(5 028 cm)
DISCRETE VO MODULE
NOTE: SPACING FOR MOUNTING SCREWS = 2.700" (6.858 CM).
SCREW THREADS ARE 6X32.
Figure 4. Mounting Dimensions
Page 22
CI-3301-O1
12/92
be 10.000 |
9.5 = «4.75 МАХ >
ct 4.75 a - La
! 1] «фе | З.ВО МАХ вЫ
© JT Je [Js | 4 | JI 197 [Js |p| A A ¡Ml
[12348 {12845 [12345 ]12345 |12945 [12945 [12545 |12345| т
© >
=
22
ed
® ®æ 5.000 БЕ
HS-48 3.7 O
DATA+ 452
DATA- o
+V5 | Rn
GND ©
® Mi M2 Mali Ma || M5 M6 M7 ma | А"
® ® т |
| 16.00 >|
р 15.50 >|
| | 775 — — — — № 5
po nn
© Л Ja | Ja J4 | Js Jo | 47 | Js 59 | эмо | Ji] Jz] día | Jia |£ 4
12345 l12a45 |12345 [ 12245] 12345 | 12345] 12845112345| 12345] 12345] 12344 12344 12345] 12345 ® т
O l
® ® 5.000
RS-485 3.7
DATA+
DATA-
+VS
GND Ri
® M1 Me M3 M4 M5 M6 M7 ME MO MIO Mi Mi2 M13 Mid y
6 Oy
25
Figure 5. Mounting Backplane Dimensions
Electrical Connections
Table 3, the break-out for the RTU labeling, is
repeated in this section for convenience. When
making power, data, and input/output connections to
and from the RTU , use the terminal numbers called
out in the table. The labeling on the unit is explained
in the key.
Figures 6 and 7, on the following pages, illustrate the
hookups for power and data in RS-232C Daisy-Chain
and RS-485 Multi-drop’ RTU=-applications, respec-
tively. The use of twisted pair wiring is strongly
recommended for all data connections.
RS-485 Considerations. As shown in figure 7, data
lines should be terminated at each end with 200 ohm
resistors to minimize unwanted reflections on the
transmission lines. Standard resistor values of 180
or 220 ohms are also acceptable.
Also, for wire runs greater than 500 feet, each end of
the line should be terminated with a 220 ohm resis-
tor, connected between the data line terminals.
During normal operation in a multi-drop application,
there are periods of time where all RS-485 drivers
are off and the communications lines are in an “idle”,
high impedance condition. At these times, the
transmission lines are susceptible to noise pickup.
To prevent this, incorporate 1 kilohm bias resistors
as shown in the figure, so that data lines will be
maintained in a “mark” condition when all drivers are
off. Bristol Babcock also has products that will
provide this termination without discrete components.
See Figure 7a.
Page 23
C1-3301-01
12/92
TO +Vs
+10TO *
+30 VDC
GND
RECEIVE
HOST
RS-232
PORT
TRANSMIT
oi
AND
ЗАВОЗВ
JWNSNYHL
sa
HABBO
AWSNVEL
ONE
SA
ЗАВОВН
HWSNYHL
Figure 6. The RTU in a Daisy-Chain Installation
RS-232C Considerations. The GND wire is used
both as a power connection and the common refer-
ence for the transmission line receivers of the RTU .
In applications that call for distances of 1000 feet or
more between modules on the data bus, voltage
drops in the power leads become an important
consideration.
As a general rule, multiply the number of RTU 'son a
single data bus by the distance between modules. -
The result is a value that, when compared to the
following constants, can be used to make installation
adjustments as appropriate.
e For 18 gauge wiring, the number of RTU ’s in
the application multiplied by the Distance from
Host to RTU should be less than 10,000 feet.
e For 20 gauge wiring, the number of RTU 's in
the application multiplied by the Distance from
Host to RTU should be less than 6,000 feet.
* For 22 gauge wiring, the number of RTU ‘5 п
the application multiplied by the Distance from
Host to RTU should be less than 4,000 feet.
NOTE
Larger gauge wiring may be required in
applications with multiple modules
- - -communicating over long distance.
Consult the factory for details.
To complete electrical connections, use a slotted
head screwdriver (head width no greater than 2.54
mm (0.1 inch) to loosen the compression screws on
the RTU terminal block. Strip a length of connection
wire insulation, and hold the stripped end of the wire
in the appropriate terminal opening while tightening
the compression screw until secure.
Page 24
C1-3301-01
12/92
+5
1 KQ
——
DO (Y) UP TO 10,000 FEET
> —————cd]—
2200 2200
HOST — '
RS-485 DO (6) > ve mn wor y
1 KQ
GND (B)
12 +
TO
12 +
TO 30 VDC
30 VDC e | .
| BI AO Y ARGY === 1 ARG Y
= EARTH GROUND
EARTH GROUND
LEGEND
8 = BLACK
В = НЕО
G = GREEN
Y = YELLOW
Figure 7. The RTU in a Multi-Drop Installation
+24v
| | GND ||
x RS485 Y UP TO 10,00 FEET ——>
2
DPC 33XX 2] 10 DATA ‘
AS 232 || AS232 RS485 < 2200
a EX al conv (6) =
*Q or 15
71 A100 DATA @
12 +
TO
12
TO + 30 VDC
30 VDC © > 'T
| BIRGlY B RiGIY ——— Bi AIG:Y
À EARTH GROUND
EARTH GROUND
LEGEND
B = BLACK
R = RED
G = GREEN
Y = YELLOW
*NOTE: GROUND IS PIN 15 ON DPC 3330
PIN 9 ON DPC 3335
Figure 7a The RTU in a Multi-Drop Installation with DPC 33XX
Page 25
C1-3301-01
12/92
All terminal labels on RTU 's configured for RS-485
communications include designators for the wire
colors typically used by standard 4-wire telephone
cabling. “(B)” is for black, “(R)” is for red, “(G)" for
green, and “(Y)" is for yellow.
Power Supply Requirements. All power supply
specifications are referenced to the RTU connector;
the effects of line voltage drops must be considered
when the RTU is powered remotely.
RTU ’s without sensor excitation capability consume
a maximum of 0.75 watts. Units with excitation
consume 1 watt, maximum. Total power consump-
tion in a multi-unit applications is determined by
multiplying the rated consumption by the number of
units.
For example, in an application with a 24 volt power
supply and four RTU ’s with sensor excitation
capability, the power requirement will be 4 times
1.00, or 4 Watts. The current will be 4 divided by 24,
or 0.167 amps.
For best reliability, RTU ’s should be powered locally.
Consult your Sales Representative for details on
power supplies available from Bristol Babcock.
Sensor Connections for Current,
Voltage, and Thermocouple RTU ’s
The labeling of the terminals of each RTU is shown
in table 3. The sensing equipment outputs should be
connected to the +IN and ~IN terminals of the RTU .
Connection for the Discrete Terminals
of Analog RTU 's
Connections for discrete input and output are shown
in the following three figures. Figure 8.showsthe
hookup for discrete inputs, such as may be used for
events counting (refer to Operation Section of this
manual for information on the RTU Events Counter).
Figure 9 shows discrete output to relays, and figure
10 illustrates the connections to logic.
Refer to the unit model number and the specifica-
tions table to determine the number of available
discrete connections for the type of RTU being used.
Discrete Inputs
Discrete (or digital) inputs are used to sense switch
closures and the state of digital signals. The inputs
are protected to voltages up to +30V and are nor-
mally up to the logic "1" condition. Digital inputs can
be read by the Digital Input (DI) command. Voltage
inputs less than 1 V are read back as "0". Signals
greater than 3.5 V are read as "1". No other com-
mands have any affect on the inputs.
Switch closures can be read by the digital input by
simply connecting the switch between GND terminal
and a digital input. Internal pull-ups are used so
additional parts are unnecessary . (See Figure 8)
The pull-ups supply only 0.5mA; therefore, self-
wiping switches designed for low current operation
should be used. For other types of switches, it may
be necessary to provide extra pull-up current with an
external resistor. The resistor should be tied between
the switch and a +V.
EVENT COUNTER
The event counter input is connected to the Digital
Input O terminal. It can be used to count any low
speed event that occurs on the DIO/EV input. Any of
the interfacing techniques described for Digital Inputs
may be used. The input pulses must meet the
specifications in Figure 8a to avoid missing counts.
Switch inputs are filtered to eliminate contact
bounce.
The Event Counter is read by using the Read Events
(RE) command. The maximum accumulated count is
9,999,999. If the maximum count is reached, count-
ing stops. The Event Counter may be cleared to zero
with the Clear Events (CE) command.
The Event Counter is not nonvolatile and the count
oo ~=will-belost:if power to the module goes down. Upon
power up, the counter is cleared to zero. The Re-
mote Reset (RR) command or a line break will not
affect the counter.
Page 26
C1-3301-01
12/92 installation
AN
10K SE
D10/DN*
e D
DIGITAL
INPUT о
КОЛЕЮ T +5V de +5V de
10K
DIi1/UP*
®
~__
Figure 8. Digital Inputs
Digital Outputs
A digital out put consists of an open-collector transis-
tor controlled by the host, using the Digital Output
(DO) command. The number of digital outputs
implemented depends on the specific RTU model.
Most modules contain two digital outputs. The open-
collector configuration is used to provide maximum
versatility in interfacing to solid state relays (SSR's)
or to standard logic levels such as TTL or CMOS.
Each digital output can sink up to 30mA and can
withstand up to 30V. Power in the transistor must be
limited to 300mW. The emitter of each transistor is
tied to the GND terminal on the input connector.
A typical connection of a digital I/O output is shown
in Figure 9. In this case, a solid state relays is
controlled by the RTU. The SSR can then be used to
control AC power to alarms , heaters, pumps, etc. A
typical connection to a logic input is shown in Figure
10. In some cases, the common-mode voltage of the
GND terminal may be significantly different from the
ground potential of the logic input to be interfaced.
This may occur when the module is powered re-
motely. In this case, an opto-isolator may be used to
eliminate the common-mode voltage. See Figure 10.
In all cases, the current switched by the transistor
may not be more than 30MA.
Only three commands can effect the Digital Output.
The Enable Alarms (EA) and Disable Alarms (DA
commands) select the function of the DOS/LO and
DO1/HI pin outputs. To route digital outputs to these
pins, use the Disable Alarms (DA) command. The
Enable Alarms (EA) command configures these two
pins as alarm outputs.
If the module loses power, the digital outputs are
turned off. The outputs will remain off until switched
by a Digital Output (DO) command. The function of
the shared pins, DOG/LO and Do1/HI is not affected
if power is lost, since this information is stored in
nonvolatile memory.
The digital outputs are not affected by the Remote
Reset (RR) command or a reset caused by a line
break.
+5Vde
+5Vdc
10K
DIG/EV
K O AM V+=2.5V
A
Do
+5V | < >
AN AN >
EV INPUT Мм ———— C 2
50% Duty Cycle Single Pulse Single Pulse
60 Hz Max. 12ms. Min. 15ms. Min.
Figure 8a. Event Counter Logic
Page 27
Ci-3301-01
12/92
+Vs
| o
+Vs O Ri
AN © ` o
DIGITAL Fa 990
INPUT |
JOUTPUT
PORT
* SSRAC
H2 -
DA
DO1/HI
> A TT
R1 & R2 limit current to 30mA Max.
Figure 9. Digital Outputs Used with Relays
—Z
DO 1/HI
DIGITAL a
INPUT
ri
© © |
e
Le
DOS/LO
— A vo current
to 30mA Max.
Figure 10. Digital Outputs Used with Logic
Alarm Outputs
The RTU analog input modules perform HI/LO limit
checking by comparing the sensor input value to
downloaded HI/LO limit values store din memory.
The result of the limit check can be used to control
special HI and LO digital outputs.
ured to be alarm outputs by using the Enable Alarms
(EA) command. After performing an EA command,
the state of the DO@/LO and DO1/HI pins will be
controlled by the alarm setting. The Disable Alarms
(DA) command is used to disconnect the alarms from
the output pins whereupon they are controlled by the
Digital Output (DO) command.
Since the Alarm Outputs share the same circuits with
the Digital Outputs, all electrical interfacing consider-
ations are the same.
Alarm limit values are loaded into the module with
the Low limit (LO) and HI limit (Hl) commands. The
limit values are stored in nonvolatile memory so they
will not be lost when power is removed. The Hi and
LO commands are also used to specify whether the
alarms are momentary or latching. If an alarm is
specified as momentary, the alarm is activated as
long as the alarm condition exists. The alarm output
will turn off when the input is within limits. A Latching
alarm is activated when the specified limit is ex-
ceeded and will remain on even if the input value
returns within limits. A Latching alarm can be turned
off with the Clear Alarms (CA) command. The HI
alarm output is turned on (sinking current) when the
measured sensor input is greater than the high limit
loaded in with the HI command. The LO alarm output
is turned on (sinking current) when the input value is
less than the stored low limit.
The alarm limit values may be read back at any time
using the ReadLow (RL) of Read High (RH) com-
mands.
Connections for RTD RTU ’s
Figures 11, 12, and 13 show the installation hookups
for RTD’s. In each case, the wires to the RTU
should be matched in length and gauged for proper
lead length compensation.
Make sure that the “Special Bit” field in the Setup
window of the Utility program is set to © for 3-wire
units, and to 1 for 4-wire units.
If using the RTD RTU with a 2-wire sensor, during
normal operation the lead resistance is scanned and
filtered by the RTU. This may result in large initial
The DO@/LO and‘Do1/HlI output pins-can“be config- * …e@rrors-if the-RTD is-connected to a powered ВТО.
Connect sensors to the RTU before applying power
to the installation hookup. If this is not possible,
execute a “Module Reset” command, as described in
the Operation Section of this manual.
If the lead resistance of the installation exceeds 50Q,
the RTU will output an over-range indication.
Page 28
C1-3301-01
12/92
Sensor Grounding. The sensor input is electrically
isolated from the power and communications inputs
for common-mode voltage up to 500 volts. If the
sensor requires grounding or shielding, use terminal
#4 of the RTU (labeled “D").
Table 3 (repeated). RTU Terminals Labeling
Type of i
Left Right
RTUL Terminals Terminals
1 2 3 4 5 6 7 8 9 10 11 12
VOLTAGE XMT RCV
& +IN ~IN | DO1/HI| Di@/ | DOO/ | DEF See See +VS GND Not Not
CURRENT EV LO Note 1 | Note 1 Used | Used
XMT RCV
T/C DO2 Di DO1/HI| Dig/ | DOO/ | DEF See See +VS GND —IN +iN
EV LO Note 1 | Note 1
XMT RCV
RTD C B A D DOG/ | DEF See See +VS GND Not Not
LO Note 1 | Note 1 Used | Used
XMT RCV
FREQ. IN +2.5V SIG [HYSTR] DIO/ DEF See See +VS GND Not Not
GND EV Note 1 Note 1 Used Used
XMT RCV BO6
DISCRETE | BO4 BO3 BO? BO! |BOO/E DEF See See +VS GND BO5 See
V Note 1 | Note 1 Note 2
NOTES: ; For RS-485 RTUs these terminals are labeled with a wire color code and the word “DATA”,
as in “(Y)DATA” and “(G)DATA”. RS-485 communications are in parallel, and thus do no
require specific Transmit and Receive connections.
_ Discrete RTUs have an additional 10 terminals. Terminals 13 thru 20 are labeled “BJ7,
B@8, BOY, BOA, BAB, BAC, BAD,” and “BAD”.
Key to Abbreviations:
DATA- Receive or Transmit to system host. Used on RS-485 RTU ’s, these terminal designators are accompanied by
abbreviations for the wire colors commonly used in making this type of connection, i.e. standard 4-wire telephone line. The
abbreviations used for the colors are (B) for black, (G) for green, (R) for red, and (Y) for yellow.
DEF — Default. This terminal may be connected to ground to place the unit in its Default Mode of operation.
DI — Discrete Input. —IN — Negative Signal Input.
DIG/EV— Discrete Input/Event Counter RCV- + Data Receive. RS-232C hookups.
DO vn Discrete Output. SIG GND —Signal Ground.
DO9/LO — Discrete Qutput/Low Alarm. A, B, etc. —RTD Sensor Input.
DO1/HI- Discrete Output/High Alarm. +VS— Positive Voltage Source Input.
GND ~ Power Supply or Discrete Output Ground. XMT — Data Transmit. RS-232C hookups.
HYSTR — Hysteresis +25V— Excitation Voltage.
+IN — Positive Signal Input.
Page 29
C1-3301-01
12/92
Ji, J2 = WIRE JUMPER
J3 = WIRE JUMPER
Figure 12. RTU Installation Hookup with 3-Wire RTD
ALEAD ©)
-| №
Втр -SENSE
RI EAD
Figure 13. RTU Installation Hookup with 4-Wire RTD
Page 30
C1-3301-01
12/92
Connections for Frequency RTU 's
Figures 14 through 17 show the connection of the
RTU to Frequency inputs.
The Frequency Input modules feature a v ersatile
input stage that can be used in a variety of applica-
tions. Figure 14 is a block diagram of the input
signal conditioning.
+IN INPUT
PROTECTION
— ISOLATION E—
OUTPUT TO up
= 1M
COMPARATOR
HYSTR HYSTERESIS
CONTROL
+2,5V
57
GND |
Fiqure 14. Input Signal Conditioning Block Diagram
The input signal is applied to a precision comparator
through the + input. Input protection is provided to
withstand inputs up to 230Vac. The comparator
output is then fed through an opto-isolator to the
module's microprocessor for scaling and formatting.
The input section is completely isolated from the
power and communications lines. The isolation
allows up to 500V of common-mode voltage between
the input ground and the power connections.
The input comparator employs hysteresis to provide
reliable readings with noisy or slow input signals.
The amount of hysteresis may be controlled by
connecting the hysteresis control line (HYSTR) to
ground or the 2.5V terminal through an external
resistor.
Three Installation connections are shown in Figures
15,16 and 17.
The first of these, figure 15, is the most common
installation hookup. It shows the unit used with
unipolar, positive-going frequency inputs. Hysteresis
is centered around a +2.5 volts switching level. К "А"
is left open, the switching levels are +2.5 volts, +/-0.5
volts. With "R" shorted, hysteresis decreases with
resulting switching levels of 2.5V +/- 5mV.
By changing the "R" value, any hysteresis from +/-
5mV to +/-0.5 V may be obtained.
Figure 16 shows the hookup for application of the
RTU for comparisons around zero volts. This
connection is useful for AC of bipolar signals.
The hysteresis control may also be connected to
ground, producing another set of switching levels as
shown in Figure 17.
To measure AC signals super-imposed on a DC
value, the input may be AC-coupled by placing a
capacitor in series with the +IN terminal of the RTU.
The circuitry of the unit includes an internal TMQ
resistor between the +IN and +2.5V terminals for
biasing. Use a 0.01 pF capacitor for frequencies
down to 10 Hz.
Page 31
C1-3301-01
12/92
R V'WITCHING +V VSTERSIS
OPEN 2.5 \у 30.5 \
on 2.5 Y +0.5 mV
@ FOR V ivsTERSIS >5 MY AND <0.5 V.
ЛАВА
МАМ HYSTR R (KQ)= 34 V HYSTERSIS
| 0.5 -V HYSTERSIS
Figure 15. Controlling Hysteresis for Positive-Going Signals
+2.5V
L GND
MY ———— HYSTR
666666606600
Figure 16. Controlling Hysteresis for Bipolar Signals
R VewircHina + Vavstensis
OPEN 2.5 \ 40.5 V
on 1.7 V +05 MV
HYSTR
FOR Y verensis >5 MVAND <0.5 V:
R (KQ)= 34V HYSTERESIS
0.5 -V HYSTERSIS
ceceseecsee
. 14
+ 2.5 17:56
Vewirchine
Figure 17. Controlling Switching Level and Hysteresis
Page 32
CI-3301-01
12/92
Connections for Discrete RTU's
The discrete RTU's provide 15 I/O points
configurable as inputs or outputs on a point by point
basis. While the analog input modules have internal
pullups on the digital (or discrete) inputs, the DIO
modules require external pullups when the point is
configured as a digital input. Allowable input values
range from O to 30V without damage. (see Figure
18).
When the point is configured as a digital output it is
capable of sinking 100 Ma per output with a maxi-
mum voltage of 30V. Note that the digital outputs on
the analog input RTU's are capable of sinking only
30 ma. The maximum total current from all outputs
on the discrete RTU is 1A. If the output is connected
to an electromechanical relay always include a
flyback diode to prevent damage to the output driver.
See Figure 19 for output connections.
Special Notes on Discrete RTU's in Continuous
Mode. Discrete RTU 's can be configured for
providing output to the Host without command
prompting.
One of the ways in which a Discrete unit can be
triggered to read terminals data when in this Con-
tinuous Mode is by the edge of an incoming positive-
going pulse. Refer to the Operation Section of this
manual for details on Continuous Mode Operation
and Edge-Triggered Mode.
RTU 's configured for this type of operation can also
be triggered by an external switch by adding a pull-
up resistor to the installation hookup, as shown in
figure 18.
Page 33
C1-3301-01
12/92
5Vdc
10K
10K 5 Vdc
BOI | D
Figure 18. Installation Hookup for Discrete RTUs in Continuous Mode, Edge-Triggered
R1 AND R2
LIMIT CURRENT
TO 30 MA MAXIMUM
R1
VW
—W
R2
BOS | D
SOLID STATE
ELAY AC
BO | D
be
+VS
Figure 19. Installation Hookup for Discrete RTU 's with Relays.
Page 34
C1-3301-01
12/92
Once calibrated, mounted, and connected according
to the instructions provided in the preceding section,
the RTU can be interrogated from the Host or dumb
terminal.
In response to interrogation or “polling” from the
Host, the RTU provides the appropriate sensor data
from its input terminals, or generates discrete output
at its output terminals, based on the settings loaded
into module memory in the Utility program (refer to
the Calibration Section, earlier in this manual).
This section of the manual documents the
communication command structure of the RTU 3301.
It is useful for understanding the commands used in
the terminal mode and for implementing any custom
ASCII driver.
When the RTU 3301 is integrated into a network
3000 system, the command structure is incorporated
in the DPC 33XX custom PROM. Refer to the Ci-
3301-05 Custom Module Interface Instruction Manual
for details on the operation and use of the custom
module. Knowledge of the commands documented
here, while helpful in understanding RTU 3301
capabilities, is not necessary for operation as a
network 3000 RTU.
This section, RTU Operation, is divided into three
parts. First is an explanation of the RTU Command/
Response syntax and timing parameters, with a
subsection on the use of the RTU Checksum. This is
followed by overviews of the Operational Commands
that are common to all RTU's, the General Operation
Commands. Next is a section on those commands
unique to the operation of Discrete units, including a
subsection on Continuous Mode.
NOTE
If using a Discrete RTU, make sure to
review the material presented in the
Discrete RTU Operation Section. Certain
aspects of unit operation and commands
are unique to Discrete units.
The Command/Response Format
RTU commands must be composed of four parts.
The first is the Prompt Character, which signals to
the RTU that a Host message is to follow. Next is
the Unit Address, the ASCII “label” unique to each
RTU connected in the application. The Unit Address
is followed by the Command Message itself, which
usually consists of a two or three character string, or
a string followed by a numerical value. The final
element necessary to complete an RTU Command is
the carriage return (2).
As an option, a fifth element, a Command Checksum
may be appended to the command (before the
carriage return) to provide for verification of “good”
Host-to-Unit communications. The Checksum for
both commands and RTU responses is explained at
the end of this section.
Command Prompt. There are two valid prompt
characters; a dollar sign, “$”; and the pound or
number sign, “4”. They are operationally inter-
changeable, the difference being the Checksum
facility provided with the RTU response when using
commands that start with “#".
Unit Address. The RTU Address is a single place
printable ASCII character used to distinguish one unit
from another in multi-unit installations. When an
RTU's Default Mode connections are effected, it will
respond to any address, but once installed and
supplied with the appropriate power, units respond
only to the Address set by the user in the Utility
program.
Operation
Page 35
C1-3301-01
12/92
NOTE
In applications calling for the installation
and operation of more than one RTU,
make sure that each unit is configured
with a unique address. Failure to do so
will result in communications collisions
and failure.
Command Message. The RTU Command Message
usually consists of a two or three letter command,
and in some cases numerical values. Refer to the
sections entitled “RTU General Commands” and
“Discrete RTU Commands” for descriptions of the
Command Messages.
NOTE
The letter portion of all RTU Command
Messages must be entered in upper case
(all capital letters). It is suggested that
when entering commands that the Caps
Lock of the Host be used, if available.
Command Checksum. A two character hexadeci-
mal value may be appended to any valid RTU
command, before the carriage return, to “double
check” the command itself for completeness.
It works like this. When an RTU receives a com-
mand from the Host, it looks for the two extra charac-
ters before the carriage return, the Command
Checksum.
If the checksum was not used, the command is
executed normally.
If the checksum was used, the RTU totals the
hexadecimal values of all the ASCII characters used
in the transmitted command, the Command Prompt,
Unit Address, and the Command Message. It then
compares that total to the transmitted Command
Checksum. If the two values are the same, the
transmitted command is executed normally. If there
is disagreement, the RTY aborts the:command, and
responds with the error message:
?BAD CHECKSUM
When determining the Command Checksum, use the
two lowest order (right-most) hex digits of the total
(Command Prompt + Address + Command Mes-
sage) as the Command Checksum. This ensures
that the Command Checksum is a “printable” charac-
ter. Append the two characters to the Command.
For example, to calculate the checksum for the
command #1DOFFOO:
Characters:
# 1 D O FF © O0
Hex values:
23 31 44 4F 46 46 30 30
Sum (hex addition):
23 + 31 + 44 + 4F + 46 + 46 + 30 + 30 = 103
The portion of the checksum to be used is D3 (hex).
The characters D and 3 would be appended to the
end of the message, as in “#1DOFFOOD3".
Always use the “#" Command Prompt when request-
ing the Checksum. If a module is setup to provide
linefeeds, the linefeed characters are not included in
the checksum calculation. Parity bits are never
included in the checksum calculation.
NOTE
The Checksum is used in a somewhat
different way with the Discrete RTU. For
more information, refer to the explanation
of the “ACKNOWLEDGE” command, in
the Discrete RTU General Commands
Section.
The RTU 3301 Programmer's Guide provides more
information on the Command and Response Check-
sum.
Response Format. In much the fashion as the
commands from the Host, the RTU response is
comprised of distinct parts. There are two; the
Response Tag and the Data Message.
The Response Tag. Responses from the RTU start
with one of two characters. An asterisk indicates an
acknowledgement, and immediately precedes either
a line feed or data and a line feed. The question
mark, “?” precedes an Error Message.
If a command is improperly formatted or if it is
otherwise not received by the addressed RTU, the
unit may not respond at all. If this occurs, re-check
for correct command format and send again. If
problems persist, refer to the Troubleshooting
Section of this manual.
Page 36
CI-3301-01
12/92
The Data Message. Most RTU responses represent
analog data. This data is represented as a nine
character string consisting of a positive or negative
sign, five digits, a decimal point, and two more digits,
ie. +00000.00.
Another type of Data Message consists of hex and
decimal numbers that represent the configuration of
the unit being addressed.
The number of significant digits in the Data Message
is controlled by the user in the Utility program.
The specifics regarding both types of RTU Data
Messages can be found in the explanation of the
General and Discrete RTU commands.
The Response Checksum. As with the Command
Checksum, the Response Checksum facility is
optional. It is provided only when the “+” Command
Prompt is used to verify good Unit-to-Host communi-
cation.
The Response Checksum functions in the same
manner as the Command Checksum, except that
when providing the appropriate data or executing the
commanded operation, the addressed RTU echoes
the original command, and bases its calculation of
the Response Checksum on the Response Tag (7),
the echoed command, and the Data Message. Refer
to the next section for examples of this.
Command Timing
When an RTU receives a valid command, it inter-
prets that command, performs the proper function,
and transmits the appropriate response back to the
Host.
Each command has a default delay during which the
module is “busy” performing the command cycle. If
the Host does not receive a response fromthe
addressed RTU at the end of this delay, a communi-
cations TIME OUT error will result, and the command
will have to be re-issued.
The following commands have a default time-out
delay of 5 milliseconds (ms) or less:
ACK, CB, CE, CP, DI, DO, RA, RAB, RAP, RB,
RCM, RD, RIA, RP, RR, SB, SP, and WE.
These commands have a default time-out delay of
15 ms or less:
EC, RE, RWT, RID, RIV, RCT, AIB, AIP, AOB, AQP,
CIA, CMC, CMD, CME, and CMT.
These commands have a default time-out delay of
100 ms or less:
WT, CT, SU, AIO, ID, and IV
In a daisy-chained multi-unit application, all of the
characters of an incoming command must be echoed
down the chain. Upon receiving the command, the
addressed RTU in the chain begins the command
cycle, and stops echoing any commands until the
cycle is complete.
Characters sent to this “busy” RTU will be stored in
the unit's internal receive buffer, and echoed immedi-
ately after the response string.
Command Timing is effected by the number of units
in a daisy-chain installation. The increase in the
delay times is equal to the time necessary to transmit
one character at the baud rate being used by the
modules. The additional time blocks are as follows:
Baud Rate Delay in milliseconds
300 33.3
600 16.7
1200 8.33
2400 4.17
4800 2.08
9600 1.04
One delay block is added for each module in the
chain.
All RTUiypes-configured for. RS-485 communica-
tions are set at the factory to provide two units of
communications delay. This is necessary when
using host computers that transmit a carriage return
(а) as a carriage returr/line feed combination.
Without the delay, the line feed character may collide
with the first transmitted character from the module,
resulting in garbled data. If the Host computer
Page 37
C1-3301-01
12/92
transmits a carriage return as a single character, the
delay may be set to zero to improve the communica-
tions response time.
RTU General Operation Commands
Table 6 lists commands that are common to the
operation of all types of RTU. Refer to the next
section for commands unique to the Discrete RTU.
Use appendix B for a quick reference table of both
Discrete and non-Discrete commands together with
the Configuration Commands which perform the
functions otherwise set and controlled in the Utility
program.
The following paragraphs provide more information
on the commands listed in the table. Use the key
from table 6 when implementing these commands.
In addition to the items in the key, note that the term
“CS” is used to indicate a checksum; “T” is used to
indicate an alarm type.
NOTE
Refer to table 6 when determining which
commands require Write Protection
Disable.
DISABLE WRITE PROTECTION —
WRITE ENABLE
FORMAT: $а\МЕ. |
TYPICAL RESPONSE: *
FORMAT FOR COMMAND WITH CHECKSUM
(FORMAT WH): #aWE
TYPICAL RESPONSE: *aWEF7
Any setting stored in the RTU non-volatile memory is
protected against accidental over-writes. It is not
possible to change any of the operational settings
without first disabling this-write protection.: The
“Write Enable” command disables the protection for
the next command entered.
NOTE
If a syntax or communications error
occurs in the “Write Enable” command, it
must be re-entered. Attempting to make
changes to the RTU protected para-
meters without first disabling the protec-
tion with this command will result in an
error message.
READ DATA
FORMAT: | $aRD.1
TYPICAL RESPONSE: *Snnnnn.nn
FORMAT WH: #aRD.
TYPICAL RESPONSE:
This command is used to read the sensor data in the
output buffer.
*aRDSnnnnn.nnCS
NOTE
As a shortcut for the “Read Data” com-
mand, enter the prompt character, the
desired unit address and À.
READ NEW DATA
FORMAT: $aND.J
TYPICAL RESPONSE: *Snnnnn.nn
FORMAT WH: #aND.
TYPICAL RESPONSE:
This command is used to read data from the RTU. №
differs from the “Read Data” command in that the
addressed RTU will not respond unless the data has
changed since the last time a read was requested.
*aNDnnnnn.nnCS
The RTU acquires analog input data eight times a
second, storing it in the output buffer. The “Read
Data” command simply reads the information in the
buffer, so a fast Host communicating at a high baud
rate could possibly read the same data several
times.
To overcome this, the output data buffer is equipped
with a New Data Flag. This flag is set when the RTU
loads the output buffer with the result of the most
recent data acquisition, and is cleared each time a
“Read Data” or “New Data” command is executed. If
a “New Data” command is received by the RTU
when its flag is cleared, it waits until new data is
present. This may be especially useful when using
the RTU with Hosts that handle communications on
an interrupt basis.
C1-3301-01
Table 6. RTU General Operation Commands
Requires
Execute Response Write
If you want to: the following Format Protection
Command: Disable
$WE
Disable Write Protection " NO
(WRITE ENABLE) $aWE.
Read Data “Snnnnn.nn NO
(Read Current Output Buffer) $aRD.-
Read New Data $aND. | Snnnnn.nn NO
Read High Alarm Trip Point SaRH Snnnnn.nnM NO
Read Low Alarm Trip Point SaRL. Snnnnn.nnL NO
Ciear Alarms $aCA. YES
Read Event Counter SaRE.] nnnnnnn NO
Clear Event Counter GaCE. YES
Trim Zero $aTZSnnnnn.nn YES
Read Zero Setting $aRZ.] Snnnnn.nn NO
Clear Zero Setting $aCZ. YES
Trim Span $aT SSnnnnn.nnl YES
Set Deviation Output Zero Point *
Р $asPSnnnnn.nrd YES
Read Discrete Input ON/OFF State “nnnn NO
or Alarm Status $aDI
Set ON/OFF State Discrete Outputs $DOonnJ NO
Reset Module $aRR. YES
KEY:
a = Appropriate module address.
n = Numeric value, corresponding to actual number, or to HEX value for desired settings (refer to appendix C).
S = Positive or negative sign.
Page 39
Special Note for Frequency RTU's. Frequency
RTU's differ from the other types of unit in that they
must receive an input trigger signal before the data in
the output buffer is replaced. If no trigger is re-
ceived, a “New Data” command will wait indefinitely.
To escape this condition, enter a single “control C”,
i.e., press the “control” and the letter “c” simultane-
ously to abort the New Data command. Upon
receiving the break, the “New Data” command will
output the current data in the output buffer.
NOTE
Using “control C” on an R5-485 system
may create communications errors.
READ HIGH ALARM TRIP POINT
FORMAT: $aRH.J
TYPICAL RESPONSE: *Snnnnn.nnT
FORMAT WH: #aRH.
TYPICAL RESPONSE: *aRHnnnnn.nnTCS
The “Read High Alarm” command shows the value
and the type of the High Alarm setting programmed
into the RTU by the selections made in the Utility
program.
The “T” in the example above represents the type of
alarm operation selected. “M” will show for the
momentary selection, where the alarm condition
clears when the input drops below the setting (out of
the alarm condition). “L” appears if the latching
selection is made; the unit remains in alarm, regard-
less of the input state, until the “Clear Alarms”
command is executed.
READ LOW ALARM TRIP POINT
FORMAT: $aRL.I
TYPICAL RESPONSE: *Snnnnn.nnT
FORMAT WN: #aRL.
TYPICAL RESPONSE: — --*aRLnnnnn.nmmTCS
The “Read Low Alarm” command performs the same
function as the “Read High Alarm” command, except
that its response details the parameters of the Low
Alarm setting.
C1-3301-01
12/92
CLEAR ALARMS
FORMAT: $aCA.
TYPICAL RESPONSE: *
FORMAT WH: #aCA.|
TYPICAL RESPONSE: *aCADF
The “Clear Alarms” command turns both the HI and
LO alarms OFF. Its primary use is in the clearing of
alarms that were configured for latching operation in
the Utility program.
NOTE
This command does not effect the status
of the alarms (enabled/disabled) or their
continuing function (latching/momentary).
In cases where the alarm condition persists after the
“Clear Alarms” command has been given, the RTU
will again “trip” at the end of the very next input data
conversion.
READ EVENTS COUNTER
FORMAT: $aRE.-
TYPICAL RESPONSE: *nnnnnnn
FORMAT WH: #aRE. |
TYPICAL RESPONSE: *aREnnnnnnnCS
The “Read Events” command outputs a seven-digit
decimal number that represents the value in the RTU
Events Counter.
The RTU Events Counter is a facility for keeping
track of the number of low-to-high transitions at the
“DIG/EV” or “B@/EV" terminals. Input at these
terminals is sampled by the unit once every millisec-
ond. If the input is “high” for the time period set in
Utility (Filtering Constants, in the Setup window), a
transition will be added to the count.
The maximum number of events that can be re-
corded is 9999999. When this maximum is reached,
the Counter stops, and will not record any more
events until cleared using the “Clear Events” com-
mand.
NOTE
The Events Counter value is not stored in
RTU memory. If power to the unit is
interrupted, the Counter is reset to zero.
Page 40
CI-3301-01
12/92
NOTE
A “Module Reset” command does not
effect the Counter.
CLEAR EVENTS COUNTER
FORMAT: $aCE..]
TYPICAL RESPONSE: *
FORMAT WH: #2CE
TYPICAL RESPONSE: *aCEE3
The “Clear Events Counter” command resets the
RTU Events Counter to zero.
When the Events Counter reaches 9999999, this
command must be executed in order for the module
to begin counting events.
Debounce Filtering. The RTU features a user-
programmable filter for debouncing the events
counter input. This is very useful when the event
signal is from mechanical contacts such as switches
or relays.
The filter constant is chosen by the user in the Utility
program. Refer to the Help screen for Filtering
Constants in the Setup window of the program for
more information.
TRIM ZERO
FORMAT: $aTZ Snnnnn.nn.-
TYPICAL RESPONSE: *
FORMAT WN: #aTZSnnnnn.nn.
TYPICAL RESPONSE: *alZSnnnnn.nnCS
The “Trim Zero” command is used to compensate for
offsets created by sensors, or to null data to create a
deviation output.
Trimming should only be executed when the RTU is
installed and receiving the actual sensor data. When
the sensor input is at a known zero level, execute a
Read Data, or “New Data".command:
$a.
If the response shows an initial offset, “*+00005.00"
for example, correct it by issuing a “Trim Zero”
command. For example:
$а17500000.00.!
This will compensate for the five unit offset from the
sensor in the example. The “Trim Zero” command
loads the offset into the RTU's Offset Register.
The “Trim Zero” command is most commonly used to
null an output to zero, so that subsequent outputs
show a deviation from a known point in units relative
to zero.
READ ZERO SETTING
FORMAT: $aRZ.J
TYPICAL RESPONSE: *Snnnnn.nn
FORMAT WA: HaRZ.!
TYPICAL RESPONSE:
This command reads the value entered into the
Offset Register by the Trim Zero command.
*aRZnnnnn.nnCS
SET DEVIATION OUTPUT ZERO
POINT
FORMAT: $aSPSnnnnn.nnJ
TYPICAL RESPONSE: *
FORMAT WH: #aSPSnnnnn.nn.
TYPICAL RESPONSE:
The number loaded into the RTU memory by this
command is multiplied by —1 and stored as the
Output Offset Register value. Typically, this value is
then used to provide a mathematical “null” for sensor
input, allowing the user to read data from the unit as
deviation from a chosen point.
*annnnCS
It is possible to load a Deviation Output Zero Point
that is beyond the output range of the sensor. This
guarantees that the user-defined null is reached only
in the case of an overload.
NOTE
The Deviation Output Zero Point over-
writes any Trim Zero setting. Use the
“Read Zero” command to check the value
„ее loaded by.the-$aSP command, and use
the “Clear Zero” command to clear the
Output Offset Register.
Page 41
C1-3301-01
12/92
CLEAR ZERO SETTING
FORMAT: $aCZ.-
TYPICAL RESPONSE: *
FORMAT WH: #aCZ.|
TYPICAL RESPONSE: *aCZF8
The Clear Zero command clears the RTU Output
Offset Register to zero. lt clears any setting adjust-
ments made with the Trim Zero command or in the
selection of a Set Point in Utility.
TRIM SPAN
FORMAT: $aTS Snnnnn.nn..]
TYPICAL RESPONSE: *
FORMAT WH: #aTSSnnnnn.nn.J
TYPICAL RESPONSE: *atSSnnnnn.nnC$S
CAUTION
The Trim Span command is the only
means of effecting changes to the span
of the RTU. There is no provision for
reading the span, or clearing any errors
loaded by this command. Unwarranted
use of the “Trim Span” command may
destroy the calibration of the unit.
The “Trim Span” command loads a calibration factor
into the RTU memory. lt is intended for use in
trimming the full scale output of the signal condition-
ing circuitry of the unit, compensating for long-term
sensor drift.
The “Trim Span” command has a practical effective-
ness of +10% of full scale. The nominal setting is
performed at the factory prior to unit shipment. Do
not use the Trim Span to change the basic transfer
function of the RTU.
READ DISCRETE INPUT ON/OFF
STATE
OR
ALARM INPUT STATUS
NOTE
The following information applies to Non-
Discrete RTU's ONLY. For information
on the DI command when used with
Discrete units, refer to that section, later
in this manual.
FORMAT: $aDI.
TYPICAL RESPONSE: *nnnn
FORMAT WH: HaDI..
TYPICAL RESPONSE: *aDinnnnCS
The Discrete Input command reads the ON/OFF
status of the alarm and discrete inputs connected to
the discrete terminals of Non-Discrete RTU's.
The response to this command is a four character
hex number (and a checksum, if implemented in the
command). The first two digits represent alarm
status, and the next two stand for the status of the
available discrete inputs, ON or OFF.
Alarm Status. The four possible alarm states and
their corresponding hex values as they will be
represented in the response to the Discrete Input
command are:
OO = Both HI and LO alarms are OFF
©1 = Hl is OFF and LO is ON
O2 = Hlis ON and LO is OFF
@3 = Both Hl and LO alarms are ON.
NOTES
This DOES NOT indicate whether the
… @larms.are.enabled or disabled, or
whether the alarms are “tripped”.
Frequency RTU's have no alarm
connections.
Page 42
C1-3301-01
12/92
Discrete Input Status. With the exception of RTD
input model RTU's, all units have at least one
discrete input connection. The second two
characters in the RTU response to the Read Discrete
Inputs command are a hex value that represents
Which of the available connections are ON, and
Which are OFF.
The available combinations are:
FC = DIG is ON and DI1 is ON
FD = DIG is OFF and DI1 is ON
FE = DIG is ON and DM is OFF
FF = DIO is OFF and DI1 is OFF
NOTES
The DI1 terminal is available only on T/C
(and Discrete) RTU's.
RTD units have no discrete input connec-
tions.
SET ON/OFF STATE OF DISCRETE
OUTPUTS
NOTE
The following information applies to Non-
Discrete RTU's ONLY. For information
on the DO command when used with
Discrete units, refer to that section, later
in this manual.
FORMAT: $aDOnn.
TYPICAL RESPONSE: *
This command turns the available discrete output
terminals ON or OFF.
Current and Voltage RTU's have two discrete
outputs, T/C units have three, and RTD units have a
single discrete output terminal available. Frequency
RTU's do not have an extra discrete output connec-
tion terminal. All fifteen of the Discrete units’ termi-
nals can be configured (individually or as a group) for
input or output.
Refer to the section on Discrete Commands for more
information on the Set Discrete Outputs as it applies
to that unit.
In non-Discrete RTU's, the discrete output terminals
are shared with the terminals of the alarm outputs.
To set the discrete terminals ON or OFF, the Alarms
must be disabled. This is accomplished in the Setup
window of the Utility program (refer to the Calibration
Section).
Open collector transistors wired to each output
terminal comprise the discrete output available on
the RTU. When the Set Discrete Output command is
used to set a particular terminal to ON, the corre-
sponding transistor is turned on, sinking current and
limiting output to near zero volts. Using the com-
mand to set a terminal to OFF results in the corre-
sponding terminal's being turned off, and no current
sink.
The available combinations are listed in table 7.
Choose the desired combination of ON/OFF chan-
nels, and enter the two-digit hex number from the
left-most column of the table in the Set Discrete
Output command.
NOTES
The settings entered are not stored in
RTU memory. If a power failure occurs,
all discrete outputs will default to OFF.
There is no way of checking the status of
a Discrete Output. If in doubt as to its
ON/OFF setting, execute the appropriate
Set Discrete Output command.
RESET MODULE
FORMAT: $aRR.
TYPICAL RESPONSE: *
Page 43
C1-3301-01
12/92
FORMAT WH: #aRR.
TYPICAL RESPONSE: *aRRCS
The Reset command allows the Host to perform a
program reset on the RTU. This is necessary if the
unit's internal program is interrupted by static or
other electrical disturbances, or any time the unit's
baud rate is changed.
Once a Reset is received, the RTU re-calibrates
itself. Any command sent during this self-calibration
procedure (approximately two seconds) will return a
NOT READY error.
NOTE
Any changes to unit baud rate settings do
not take effect until a Reset has been
executed. The Utility program can be
used to execute a Reset. Refer to the
Calibration Section, earlier in this manual.
Commands Unique to Discrete RTU’s
Table 7. Discrete Output Options
DOG/LO DO1/HI DO2 (when available)
ok ON OFF ON OFF ON OFF
00 + + +
01 + + +
02 + + +
03 + + +
04 | + + +
05 + + +
06 + + +
07 + + +
Page 44
Ci-3301-01
12/92
Table 8, on the following page, summarizes the
commands that are unique to the operation of the
Discrete RTU.
The following paragraphs provide the supplemental
information necessary to execute the commands that
apply exclusively to the Discrete RTU. Unless
otherwise noted, the commands explained in the
previous section also apply to Discrete units.
ACKNOWLEDGE
FORMAT: $aACK.-
TYPICAL RESPONSE: *
The Acknowledge command is a hand-shaking
element that is used with a command that effects the
discrete outputs, such as the Set Discrete Outputs
command (Discrete units only). It is used to confirm
the data that was sent to the module from the Host,
providing another level of security against transmis-
sion errors.
Using Acknowledge with the Command Checksum.
The Acknowledge command works differently with
the Checksum in the Discrete RTU.
FORMAT WH: #1DOFFFF.
TYPICAL RESPONSE: *1DOFFFFO6
In this example the address “1” is used. In the
command the first pair of F's turns all the discrete
outputs for RTU#1 ON. The second pair of F's is the
checksum for the command.
The response echoes the command, including the
command checksum, and calculates a second
checksum.
More importantly, however, the command itself does
not execute until the Acknowledge command is
executed. Only when the correct response to the
Acknowledge command is returned, *”, can it be
assumed that the DO command has been executed.
If the response data to the original command shows
a discrepancy of some kind, repeat the original
command. For example:
#1DOFFFF.
*I1DOFFFEO5S
In this case the response data does not match the
Command:
Response:
original command, indicating that the module may
have received the command incorrectly due to noise
on the transmission line. However, the erroneous
data does not effect the settings of the unit since the
module must receive an ACK to complete the
command. To correct the error, therefore, simply re-
issue the original command:
H1DOFFFF.]
*1DOFFFFO6
This time the response data is correct, and the DO
command may be completed by sending Acknowi-
edge:
Command:
Response:
Command:
$1АСК..!
Response: *
Discrete RTU commands that when used with a
checksum require ACK handshaking are:
e Assign Input Bit
e Assign Input/Output
* Assign Input Position
ео Assign Output Bit
* Assign Output Position
* Clear Bit
* Clear Position
* Set Discrete Output
o Set Bit
* Set Position
NOTE
The Acknowledge command used without
an associated output command will
generate a COMMAND ERROR.
SET 1/0 — ALL TERMINALS
TYPICAL FORMAT: $aAlOnnnn.
Page 45
CI-3301-01
12/92
Table 8. Discrete RTU Operational Commands
Requires
Execute Response Write
If you want to: the following Format Protection
Command: Disable
SWE
Acknowledge Command Handshaking SaACK ^ NO
Set 1/0 Assignments For All Terminals SaAlOnnnn * YES
Simultaneously
INPUT by label:
$aAlBn..
* INPUT by terminal:
Set 1/O Assignment For Individual Terminal $aAlmn * YES
* QUTPUT by label:
$aAOBnn
* QUTPUT by terminal:
$aAO Pan...
Read 1/0 Assignments for All Terminals at SaRA *nnnn NO
Once
e By label: $ HABind
Read 1/0 Assignment of Individual Terminal y label: $ n NO
* By terminal: fsRAMmn-
Set ON/OFF State of All Teminals at Once
(Terminals set for Inputs ignore this * NO
command) $aDOnnnnd
ON by Label: $aSBnnd
Set ON/OFF State of Individualoutput * ON by terminal #:
Terminal SasPnn * NO
(Specifying Input Terminal generates
ERROR)
OFF by Label: $aCBnn
= OFF by terminal:
$aC Rand
Read ON/OFF. State of All Terminals + SDL - - Ænnnn NO
Read ON/OFF State of Individual Terminals - By label: SéRBnn- "n NO
* By terminal: $aRFn-
NOTE: Table Continued Next Page.
Page 46
CI-3301-01
12/92
Table 8. Discrete RTU Operational Commands (continued)
Requires
Execute Response Write
if you want to: the following Format Protection
Command: Disable
SWE
Set Initial Value $alVnnnn * YES
Read Initial Value $aRIV.] "nnnn NO
Set the Watchdog Timer $ANT+nnnnn.ne * YES
d Watchdog Ti Setti *
Read the Watchdog Timer Setting SaRWT | пло. NO
Set Module Identification $aln............. n * YES
Read Module Identification saRIDJ Acc anncne n NO
Read Events & Clear Counter $aEC. | *-nnnnnnn YES
TYPICAL RESPONSE: * 0000 = All terminals are inputs.
TYPICAL FORMAT WH: #aAlOnnnnCS.
TYPICAL RESPONSE: *aAlOnnnnCS
REQUIRED ACKNOWLEDGE: $aACK.
RESPONSE: *
This command is used to configure all of the Discrete
RTU terminals at once, either for input or output.
The two right-most n's from the example above
control RTU terminals BO/EV through B97. The two
left-most “n's” control terminals B98 through BOE.
FF sets terminals to a logical “1”, designating them
as outputs. À “©” designates a terminal as an input.
The available options are as follows:
FFFF = All-terminalsrare outputs.
FFOO = Terminals BO/EV through BO7
are inputs, BO8 through BOE
are outputs.
OOFF = Terminals B@/EV through BO7
are outputs, BO8 through BOE
are inputs.
SET 1/0 FOR INDIVIDUAL TERMINALS
TYPICAL FORMAT: $aAOB nn.
TYPICAL RESPONSE: *
TYPICAL FORMAT WH: 4+aAOBnnCS.]
TYPICAL RESPONSE: “aAOBnnCS
REQUIRED ACKNOWLEDGE: $aACK.
RESPONSE: *
The Assign 1/0 commands, Assign Input Bit/Assign
Input Position and Assign Output Bit/Assign Output
Position, are used to specify the data direction of
individual RTU terminals. The nn characters from
the examples above refer to the individual terminals
to which the assignment is being made.
The Assign Input commands, AIB and AIP, configure
Page 47
C1-3301-01
12/92
individual terminals to be used as input, reading
external signals. The Output commands, AOB and
AOP, set the addressed terminals to provide discrete
output, which can be used to control external equip-
ment.
Bit and Position. As is the case with all Discrete
RTU commands that function based on Bit or
Position, the type of command used depends only
upon the user's preference for referencing the RTU
terminals. “Bit” commands, as in “Assign Input Bit’
and “Read Bit” reference terminals according to the
actual unit label.
90 =BOIEV 098=B08
@1 = BAA 29 = BO9
02 = BO? OA = BOA
93 = ВОЗ OB = BOB
94 = BO4 OC = ВОС
@5 = BO5 20 = Вер
O6 = BO6 OE = BOE
07 = BO7
The command:
$SIAOBOS.:
for example, designates terminal B@5 of the Discrete
RTU whose address is “3” as an output terminal.
The “Position” command, as in “Assign Output
Position”, reference RTU terminals according to their
ordinal significance. That is, terminals are simply
numbered from © to 14, starting with BO/EV as the
number O.
O = BO/EV 8 = ВОВ
1 = В21 9 = BO9
2 = BO? 10 = BOA
3 = BO3 11 = BOB
4 = BO4 12 = BOC
5 = BO5 13 = BOD
6 = BO6 14 = BOE
7 = BO7
The following command designates terminal “BC”
of RTU “A” as an input terminal:
SAAIP12.:
READ I/O ASSIGNMENTS — ALL
TERMINALS
FORMAT: $aRA.
TYPICAL RESPONSE: *nnnn
FORMAT WH: #aRA
TYPICAL RESPONSE: *aRAnnnnCS
This command may be used to determine how each
terminal was set in the Utility program (under Setup,
the “I/O Assignments” parameter), either for input or
output.
The response is a pair of two-digit hex numbers
whose binary equivalents represent the settings. A
binary “1” represents an output terminal, and a “9”
represents an input.
The right-most two-digit hex number in the response
corresponds to the first eight terminals of the Dis-
crete RTU, BO/EV through B@7. The left-most hex
value reads out the setting for terminals BO8 through
BOE.
Use the hex-to-binary-to-ASCII conversion table in
appendix C to read the unit's configuration, or access
the settings in the Setup window of the Utility pro-
gram (refer to Calibration, earlier in this manual).
Page 48
C1-3301-01
12/92
In the following, for example:
$ZRA..
*1A79
“79”, corresponding to terminals BO/EV through
BO7, represents the binary value 911110091. This
means that:
Command:
Response:
BO/EV is configured as an OUTPUT.
BO1 is configured as an INPUT.
BO? is configured as an INPUT.
B@3 is configured as an OUTPUT.
B@4 is configured as an OUTPUT.
BOS is configured as an OUTPUT.
BOG is configured as an OUTPUT.
B@7 is configured as an INPUT.
From appendix C, we find that “1A” represents
20011010. This indicates the configuration of
terminals B@8 through BOE in a manner similar to
the first eight (the sixteenth terminal reference is
ignored).
READ I/O ASSIGNMENTS —
INDIVIDUAL TERMINALS
FORMAT: $aRABnn.
TYPICAL RESPONSE: *n
The Read I/O Assignment commands, Read Assign-
ment Bit and Read Assignment Position, provide the
user a means of checking whether individual termi-
nals of a Discrete RTU have been configured as
input or output.
The response is a “1” for output and “©” for input.
Refer to the explanation of Bit” and Position” desig-
nators under the “Assign l/O for:Individual Terminals”
command.
Remember:
» The right-most, two-digit hex number in the
response corresponds to terminals B&/EV through
BO7.
e The left-most, two-digit hex number is for BO8
through BOE (reference to the sixteenth terminal is
ignored).
When dealing with the binary numbers, the right-
most digit corresponds to the lowest-numbered
terminal; e.g., the “1” in “92000901” would
represent the (input) setting for terminal “BO/EV".
SET ON/OFF STATE — ALL
TERMINALS
TYPICAL FORMAT: $aDOnnnn.!
TYPICAL RESPONSE: *
TYPICAL FORMAT WN': #aDOnnnnCS..}
TYPICAL RESPONSE: *aDOnnnnCS
REQUIRED ACKNOWLEDGE: $aACK.
RESPONSE: *
This command sets all terminals configured as
outputs either ON or OFF (terminals configured as
inputs ignore this command).
As in Non-Discrete RTU’s the binary equivalents of
the hex values entered are used to set the state.
Use the hex-to-binary-to-ASCII conversion table in
Appendix C to select the desired configuration. A “1”
sets the corresponding terminal ON. “9” sets the
corresponding terminal OFF.
For example, in this command:
$ZDO457A.
“7A” (hex), which represents the binary value
311119010, sets the configuration of terminals BO/
EV through B97 on RTU “Z”. This implements the
following configuration:
BO/EV OFF о
BO1 ON 1
- BO? OFF o
BO3 ON 1
BO4 ON 1
Page 49
C1-3301-01
12/92
BOS ON 1
BO6 ON 1
BO7 OFF o
The left-most hex value, “45”, sets the configuration
of terminals BO8 through BOE (the sixteenth termi-
nal is ignored) in a similar fashion.
NOTE
The number of hex values used in this
command MUST agree with the Word
Length parameter setting made during
Calibration (Utility, under Setup).
If the Word Length for a Discrete unit is set for 1
Byte, and two, two-digit hex values are specified in
the DO command, a SYNTAX ERROR will be
returned.
SET ON/OFF STATE — INDIVIDUAL
TERMINALS
TYPICAL FORMAT: $aCBnn.-
TYPICAL RESPONSE: *
TYPICAL FORMAT WH: #aCBnn.
TYPICAL RESPONSE: *aCBnnCS
REQUIRED ACKNOWLEDGE: $aACK.
RESPONSE: *
The Clear Bit/Clear Position commands turn the
terminals of the Discrete RTU OFF. The Set Bit/Set
Position commands turn individual terminals ON.
For example, the following:
$3CBOB.
turns the terminal BOB of RTU #3 OFF. The com-
mand:
$3CB11.
turns terminal number 11 of RTU #3 OFF.
NOTE
Terminal 11 is labeled BOB on most
Discrete RTU’s. The commands in both
of the preceding examples performed the
same function.
The Clear Bit/Clear Position and Set Bit/Set Position
commands will only work with terminals that have
been designated as outputs (using one of the Assign
commands). Addressing an input terminal with these
commands will return an OUTPUT ERROR.
READ ON/OFF STATE — ALL INPUTS
TYPICAL FORMAT: $а0!. |
TYPICAL RESPONSE: *nnnn
TYPICAL FORMAT WH: #aDIl |
TYPICAL RESPONSE: *nnnnCS
This command reads the ON/OFF state of all of the
terminals of the Discrete RTU. It differs from the
“EDI” command for non-Discrete RTU's in that none
of the response's hex digits correspond to alarms. In
the same manner as its non-Discrete cousins,
however, the Discrete's response to the “$DI”
command breaks out into binary numbers where a
“@" signifies an OFF state, and a “1” represents ON.
NOTE
If desired, the Discrete RTU can be
configured so that only its first eight
terminals, B&/EV through B@7, respond
to the Read Discrete Inputs command.
To accomplish this, set the Word Length
parameter (Utility, under Setup)
to “1 Byte”.
READ ON/OFF STATE — INDIVIDUAL
TERMINALS
FORMAT: $aRBnn.
TYPICAL RESPONSE: *n
FORMAT: $aRP nn.
TYPICAL RESPONSE: *n
. -These.commands,-Read Bit and Read Position,
indicate the logical state of individual terminals.
The response to these commands is either a “17,
indicating ON, or a “@", indicating OFF.
NOTE
Attempting to read a non-existing terminal
will result in a VALUE ERROR.
Page 50
Cl-3301-01
12/92
SET INITIAL VALUE Remember:
FORMAT: $aVnnnn e The right-most hex digits in the response corre-
TYPICAL RESPONSE: * spond to terminals B&/EV through BA7.
FORMAT WH: #alVnnnn.
TYPICAL RESPONSE: *alVnnnnCS
This command sets the ON/OFF state of the output
terminals that the RTU will use at startup. When the
RTU is powered up, it first reads the I/O direction
data, then it reads the Initial Value and performs an
internal “Set ON/OFF State of All Outputs” command
($aDOs) using the hex values set by the Initial Value
command.
The command is intended to function as a “safe”
switch. If power to the RTU is interrupted, the Initial
Value ON/OFF settings for output terminals will be
automatically invoked when power is restored.
The Initial Value may be set in the Setup window of
the Utility program. The IV command is documented
here for convenience. The “nnnn” in the examples
above represent the hex values used to configure the
available output terminals ON or OFF. Refer to the
explanation of the “Set ON/OFF State of All Outputs”
command, above, for the available options.
READ INITIAL VALUE
FORMAT: $aRIV.-
TYPICAL RESPONSE: *nnnn
FORMAT WAX: #aRIV
TYPICAL RESPONSE: *aRIVnnnnCS
This command reads the Initial Value of the RTU
terminals configured as outputs.
The response is a pair of two-digit hex numbers,
whose binary equivalents correspond to the ON/OFF
settings stored as the Initial Value in the memory of
the unit.
Use the table in appendix C to determine the binary
equivalents of the hex values inthesresponse to the
Read Initial Value command.
e The left-most digits are for B&8 through BOE
(reference to the sixteenth terminal is ignored).
e When dealing with the binary numbers, the right-
most digit corresponds to the lowest-numbered
terminal; e.g., the “1” in “90000001” would
represent the (ON) setting for terminal “BO/EV”.
Alternatively, access the Setup Window of the Utility
program, and check the Initial Value data entry field.
SET THE WATCHDOG TIMER
FORMAT: $aWTsnnnnn.nn-
TYPICAL RESPONSE: *
FORMAT WH: #aWTsnnnnn.nn.
TYPICAL RESPONSE:
The Watchdog Timer (WT) command stores a time-
out setting in RTU memory, after which the unit's
terminals automatically configure themselves accord-
ing to the Initial Value settings (refer to the Setup
window of the Utility program, and the “Set or Read
Initial Value” commands, earlier in this manual).
*aWTsnnnnn.nnCS
The data entered with the WT command is the time
scaled in minutes. For example:
$1WT+00010.00.
sets the timer for ten minutes in RTU #1. In this
example, if the module does not receive a valid
command for a period of 10 minutes, the outputs will
automatically default to the Initial Value.
The purpose of the Watchdog Timer is to force the
outputs to a known “safe” value in the event of a host
or communications link failure.
peration
Page 51
C1-3301-01
12/92
NOTES
The Watchdog Timer may be disabled by
setting the timer value to +99999.99.
Setting the Watchdog Timer to less than
+2000. 16 minutes will result in a
VALUE ERROR.
READ THE WATCHDOG TIMER
SETTING
FORMAT: $aRWT.
TYPICAL RESPONSE: *snnnnn.nn
FORMAT WH: #aRWTA
TYPICAL RESPONSE: *aRWTsnnnnn.nnCS
This command reads the value set into RTU memory
with the Enable Watchdog Timer command (WT).
SET MODULE IDENTIFIER
FORMAT: $aiD name
TYPICAL RESPONSE: *
FORMAT WH: #alDname.!
TYPICAL RESPONSE: *alDnameCS
This command allows the user to write a message
into the RTU memory which may be read back (refer
to the Read Identification command) to distinguish a
particular discrete unit from others in an application.
The facility is available in the Setup window of the
Utility program under “ID Register”.
Identifications consisting of any combination of
letters, numbers, and spaces may be used, up to a
length of 16 characters.
Examples:
Command (module location):
$1IDBOILER ROOM.
Command (calibration date):
$11D 12/3/88.
Command (model number):
$11D 31251
NOTE
Since the ID command has a variable
length syntax, checksums cannot be
appended to the command message.
READ MODULE IDENTIFICATION
FORMAT: $aRID..
TYPICAL RESPONSE: *name
FORMAT WH: #aRID.
TYPICAL RESPONSE: *aRIDnameCS
This command reads the Identification Register of
the addressed unit, as set with the ID command, or
in the Utility program's ID Register selection.
READ EVENTS AND CLEAR
COUNTER
$aEC.]
*nnnnnnn
#atC.
*aECnnnnnnnCS
FORMAT:
TYPICAL RESPONSE:
FORMAT WH:
TYPICAL RESPONSE:
This command read the current value in the events
counter buffer, and after the read, immediately clears
the buffer to zero.
This eliminates the potential for lost event counts
between the execution of a Read Events and a Clear
Events command.
Discrete RTU Continuous Mode
Operation
The Continuous Mode of RTU Operation, available
as an option for other units, is part of the standard
Discrete RTU package. Enabling Continuous Mode
programs the RTU to transmit data without its being
prompted by a Host command.
Discrete units-can be set by the user for four types of
Continuous Mode Operation; triggered by a change
in input state, by the edge of an incoming pulse, by
an internal timer, or by the input from another RTU
that has been configured for Continuous Mode.
The format of the data output from a Discrete RTU in
Continuous Mode is the same as that of a Non-
Page 52
C1-3301-01
12/92
Continuous unit prompted with a Read Discrete
Inputs command and checksum:
*aDinnnnCS
Table 9 lists the Continuous Mode commands. It is
followed by detailed explanations and operational
notes on the types of RTU Continuous Mode opera-
tion.
The Continuous Mode Output Trigger Signal. in
order to facilitate daisy-chaining Continuous Mode
RTU's, each module produces an output trigger
signal each time it completes an output data string.
This output trigger is a 5 millisecond low pulse at the
DEFAULT terminal. Remember that the DEFAULT
is normally an input, used to place the module in a
known communications setup. This is still the case
when a module is set for Continuous Mode, however
when a module produces a continuous output, the
DEFAULT terminal momentarily becomes an output
and produces a low-going trigger pulse.
The pulse may be used to trigger another module set
in Edge-Triggered mode, for example, and in this
manner, many modules may be daisy-chained
together.
SET CHANGE-TRIGGERED
CONTINUOUS MODE
Command: $aCMC..!
Response:
This command sets the addressed RTU to respond
to changes in the state of the input data stream. The
module will output a data string that reports the new
state of inputs.
For example, assume “7”, a Discrete RTU, has been
set so that all its terminals are inputs (refer to the
description of the Assign 1/0 command, (AlO). At
power up, all terminals are OFF. When one of the
terminals, terminal BDA for instance, changes state,
the RTU outputs data to the host as though
prompted by a Read Discrete Inputs command and
checksum (#ZDI1 J):
*ZDIO40OD5
After transmitting this data, RTU “Z” immediately
begins scanning the I/O lines. When any other
change of state occurs, another output to the Host is
initiated.
SET EDGE-TRIGGERED
CONTINUOUS MODE
Command: $aCME.]
Response:
This command is used to set the RTU to respond to
an incoming positive-going trigger pulse. The trigger
input should be connected to the BO/EV terminal,
and that terminal should be configured as an input
(refer to the Set I/O for Individual Terminals com-
mand, AlB).
Figure 18, in the Installation Section, shows the
hookup for the RTU in the Edge-Triggered Mode.
With the Edge-Triggered Mode enabled, the RTU will
provide data whenever a trigger pulse is detected at
the BO/EV terminal.
The output format will be as though the unit were
prompted by the Host with a #DI.J command:
*aDinnnnCS
SET TIMER-TRIGGERED
CONTINUOUS MODE
Command: $aCMT..
Response:
This command sets the Discrete RTU to continuously
output data to a host computer or display device
based on the setting of the Continuous Timer in the
Utility program.
NOTE
As with all of the Continuous Mode types,
Page 53
C1-3301-01
12/92
Table 9. Discrete RTU Continuous Mode Commands
Requires
Write
if you want to: Execute Response Protection
the following Format Disable
Command: SWE
Set Change-Triggered Continuous Mode $aCMCH - YES
Set Edge-Triggered Continuous Mode $aCMEJ * YES
Set Timer-Triggered Continuous Mode $aCMT. * YES
Set Continuous Timer $aCT+nnnnn.nn- * YES
Read Continuous Timer Setting $aRCT. *nnnnn.nn NO
Set Input-Triggered Continuous Mode $aCMLI * YES
Read the Continuous Input Address $aRIA nn NO
Read the Type of Continuous Mode being used $aRCM. n NO
Disable Continuous Mode Operations $aCMDI NO
it is not necessary for the Host to poll the $ SaAlOJO00
unit to obtain data. The Host must,
however, have an interrupt-driven serial
input for proper operation.
For example, an application calis for an RTU to
output data every 10 seconds. (Write Protection
Disable commands ($WE) are not shown in this
example).
The unit is set up in the Utility program as usual
(refer to the Calibration Section of this manual), and
the Continuous Timer is.set-for.a 10-second interval:
+00010.00
The unit is installed, and power is applied (refer to
the Installation Section). All terminals are set for
input:
The Timer-Triggered command ($aCMT) is exe-
cuted, and the unit immediately begins to output data
at 10 second intervals. Every 10 seconds, the RTU
will read the status of its МО lines and output the
status of those lines as if it was responding to a
#1D1 command.
As a shortcut to the Utility program, the “Set Continu-
ous Timer” command, $aCT, can be used to specifiy
the interval for Timer-Triggered Mode. The com-
mand is formatted like this:
$aCT+nnnnn.nn..
Where “nnnnn.nn” is the desired timer interval, in
seconds. Ten seconds, for example, would be
expressed as +00010.00.
Timer Mode With Outputs. With the terminals of
the RTU configured for outputs, the Host may
Page 54
Ci-3301-01
12/92
execute DO, SB, CB, or other output commands to
control the discrete outputs in response to the input
data or some other control decision.
It is not necessary to disable Continuous Mode
before issuing the output command. However, to
avoid communications collisions the host command
should be timed to avoid the continuous response
from the unit. Wait for an output string from the
module and then immediately issue the output
command, or disable the Continuous Mode Opera-
tions, execute the “CT” command, and then re-
enable Continuous Mode.
SET INPUT-TRIGGERED
CONTINUOUS MODE
Command: $aCMI.!
Response:
This command enables the addressed RTU to
respond to data transmitted by a second RTU. If the
second unit is configured as a Continuous Output
Module (Change-, Edge-, or Timer-Triggered), the
loop can function entirely without Host intervention.
SET CONTINUOUS MODE INPUT
ADDRESS
FORMAT: $aClAnn.
TYPICAL RESPONSE: *
This command is required when configuring an RTU
to output data to a second unit configured for Con-
tinuous Input (refer to the explanation of the $aCMI
command, above). It is used to specify the input
address of the Continuous Input RTU. The nn in the
examples above is the hex representation of the
ASCII address of the second RTU.
For example, in the command:
$ZCIA41..
RTU Z is set to respond to the input of a second RTU
whose module address is set to the ASCII equivalent
of hex 41, or “A”.
NOTE
An RTU set to respond to a Continuous
Output unit with the same address, as in:
$ZCIA5A.
will result in an ADDRESS ERROR.
READ CONTINUOUS MODE SETTING
FORMAT: $aRCM.!
TYPICAL RESPONSE: *n
This command reads the type of Continuous Mode
operations set into the addressed RTU. The “п” тп
the example above will be replaced, in actual opera-
tions, by a “C” to indicate Change-Triggered Mode,
by an “E” for Edge-Triggered, by an “1” for Input-
Triggered, by a “T” for Timer-Triggered, or by a “D”,
which will indicate that the unit's Continuous Mode
has been turned off.
READ INPUT ADDRESS
Command: $aRIA.
Response: *a
This command reads back the Continuous Input
Address setting stored in non-volatile memory. The
response to the command is the ASCII code of the
Continuous Input Address character.
READ CONTINOUS TIMER SETTING
Command: $aRCT..
Response: *+39905.00
(example)
This command is used to read back the value of the
Continuous Timer. The Timer is set in the Setup
window of the Utility program, or with the Set Con-
tinuous Timer command ($aCT). The value is scaled
in units of seconds. This is not to be confused with
the Watchdog Timer.
Page 55
Ci-3301-01
12/92
The Continuous Timer and
Continuous Mode Operations
The Continuous Timer parameter, set in the Utility
program, establishes a time interval after which the
Discrete RTU issues an unprompted output. The
input field for setting the Timer is found in the Utility
program's Setup window.
The Continuous Timer is particularly useful in limiting
responses from modules in a multi-unit scenario if
triggering input is likely to turn on and off quickly.
Such circumstances can cause a continuous stream
of data in some cases.
Setting the Continuous Timer for a non-zero interval
will implement a delay (in seconds) after a Continu-
ous Mode response. The unit will wait for the
programmed interval before beginning to scan the I/
O terminals for another trigger input.
As an alternative to setting the Continuous Timer
interval in the input field in the Utility program, a
short-cut command, Set Continuous Timer Interval,
may be executed:
a =the RTU address
CT = the Set Continuous Timer command
S = always positive (+)
nnnnn.nn = the number of minutes in the delay
window.
DISABLE CONTINUOUS MODE
FORMAT: $aCMD.
TYPICAL RESPONSE: *
It is not necessary to turn Continuous Mode opera-
tions off to send commands from the Host to the unit.
To avoid communications collisions, the host should
wait for a continuous output response, and then
immediately issue the CMD command.
If, for example, the Continuous Timer has been set
as follows:
SaCT+00010.00.!
(or “90010.0” in the Continuous Timer field of the
Setup window in the Utility program).
The user has ten seconds to issue the CMD com-
mand, so the likelihood of a collision is remote.
It is also possible for the Host to disable Continuous
Mode even if the Continuous Timer is set for O
seconds. The host must issue the CMD command
inmediately after the carriage return from the RTU is
received. When the RTU reads a “$"or “4 character
on the communications line, it will temporarily halt
Continuous Mode output and look for an address
character. If it detects its own address, it will read
and process the rest of the command. Otherwise it
will resume Continuous Mode output.
NOTE
Communications collisions are not
harmful to RS-485 hardware. The host
serial input must, however, be able to
accept framing errors and “noise” charac-
ters when collisions occur.
Page 56
C1-3301-01
12/92
Maintenance
The RTU 3301 is designed so that it will require little
maintenance. A quick, periodic check of connections
at the terminal blocks is all that is suggested.
In installations where the unit may be subjected to
harsh environmental conditions, both the thermoplas-
tic DIN and aluminum hockey-puck housing styles
can be mounted in a variety of enclosures, providing
excellent, maintenance-free protection for the RTU.
Troubleshooting
PROBLEM:
An RTU in the system does not
respond to Host commands.
ACTION:
1.
Check Connections. Make sure all connections
to and from the unit are secure. Refer to the
figures in the Installation Section of this manual,
and verify that the terminals of the RTU are
connected to the appropriate sensor type or
discrete input device, and that the data lines are
properly connected to the communications port
of the Host.
Baud Rate. Check that the baud rate being
used by the Host is the same as that pro-
grammed in the RTU. If the setting of the RTU is
unknown, connect the DEFAULT terminal to
ground as shown in figures 1, 2, or 3 in the
Calibration Section, and run Utility (it may be
necessary to remove the unit from the applica-
tion to accomplish this).
Echo. If the installation incorporates multiple
RTU's in a daisy-chain hookup, make sure that
the ECHO has been turned on in all units. Refer
to the Setup window of the. Utility program.
Address. If the installation incorporates multiple
RTU's in either a daisy-chain or multi-drop
hookup, make sure that each unit was setup with
a unique address.
PROBLEM:
Finally, make sure that the command being
entered is correctly formatted, and that the
checksum, if used, is correctly calculated. If
problems persist, contact Bristol Babcock's
Application Support Group.
An RTU responds with an ERROR
message.
ACTION:
1.
ADDRESS ERROR. There are four ASCII
values that are illegal for use as module ad-
dresses; the NULL character (90 hex), the
carriage return (2D hex), the $ character (24
hex), and the # character (23 hex). Use the
Utility program to set the address of the RTU's
used in the system. The program does not allow
¡legal addresses to be loaded into module
memory.
NOTE
An attempt to use the Continuous Input
Address command to specify an illegal
address or an address identical to the
polling address will cause an error.
SYNTAX ERROR. Command was improperly
formatted. Refer to the explanation and example
of the offending command in the Operation
Section of this manual. Refer to appendix B for a
listing of the correct syntax for all RTU com-
mands.
BAD CHECKSUM. This error message is
returned when the checksum included in the
command does not match the value calculated
by the unit. This can result from noise or other
interference on the data lines. Repeat the
command, and if the error persists, re-calculate
the command checksum. If problems continue,
attempt the command using a lower baud rate.
COMMAND ERROR. This occurs when a
command is not recognized by the RTU. Make
sure that the command is correctly formatted; all
upper-case (capital) letters.
Page 57
C1-3301-01
Maintenance 12/92
5. OUTPUT ERROR. An attempt to use a Clear
Bit, Clear Position, Set Bit or Set Position
command on a Discrete RTU terminal that was
set for input (Assign I/0). Review the configura-
tion of the terminals with one of the Read com-
mands, or re-assign the desired I/O status.
6. PARITY ERROR. Make sure the parity of the
host and all the RTU's in the system are set the
same; even, odd, or none. Random parity errors
are occasionally produced as a result of noise on
the data lines. Attempt a re-issue of the com-
mand to correct this.
7. VALUE ERROR. This error results when an
incorrect character is used as a numerical value.
Remember, hex values range from 0 to 9 and A
to F only. Refer to appendix C to check for the
desired hex value and re-issue the command.
8. WRITE PROTECTED. The command was
aborted because the RTU Write Protection was
not disabled first. Execute a $aWE.! command,
and re-issue the offending command.
PROBLEM: Continuous Mode Producing Erratic
Communications, Inaccurate/Incorrect Re-
sponses.
ACTION:
In some cases, especially if a large number of Edge-
Triggered modules are connected in a daisy-chain,
the amount of data transmitted may overload the
serial port buffer of the Host device.
To remedy this, the incoming data should be slowed
down by increasing the delay programmed by the
Continuous Timer parameter in the Setup window of
the Utility program ($aCT+nnnnn.nn., as an alterna-
tive).
Page A-1
C1-3301-01
12/92
Voltage, Current, and Frequency RTU's are offered
with a Programmable Option, PRG, for performing
user-defined scaling of the PRG-equipped RTU
(RTU-PRG) output, and for calculating non-linear
input-to-output transfer functions.
Operationally, the RTU-PRG is similar to standard
units. A version of the standard units’ Utility pro-
gram, RTU-PRG.BAT, is used to set unit operating
parameters. The commands listed in the Operation
Section of this manual (unless otherwise noted) can
be used to control basic RTU-PRG unit operation.
This appendix provides an overview of RTU-PRG
capabilities, and instructions for use of the RTU-
PRG.BAT program for unit configuration.
Linear Scaling
The RTU-PRG can be set by the user to display
sensor output in application-specific scaled engineer-
ing units. It performs all scaling and conversion of
the sensor input internally, making it simpler to read
the data at the control-room PC.
For example, a typical pressure sensor is hooked to
a Current RTU-PRG. The sensor provides 1-5 V
linear output for pressures from 0 to 1000 psi.
With a standard, Current RTU, the output at the PC
might look like this:
Pressure Sensor Output RTU Read-Out (mV)
0 1V +01000.00
500 3V +03000.00
1000 5V +05000.00
Though the standard RTU faithfully outputs the
sensor voltage, the actual data required from the
application is pressure, not voltage, and the raw
data of the RTU read-outs must therefore be con-
verted in the DPC 3330/3335 using a simple ACCOL
calculator statement for each conversion.
Units equipped with the PRG Option, however, can
be programmed to provide the converted data,
scaled as desired:
Pressure Sensor Output RTU-PRG Read-Out
(in psi)
0 1V +00000.00
500 ЗУ +00500.00
1000 5 \ +01000.00
Or in a percentage scaling scheme, for example (750
psi = full):
RTU-PRG Read-Out
(in % of “full”)
Pressure Sensor Output
0 1.0V +00000.00
375 25V +00050.00
750 4.0V +00100.00
RTU-PRG Resolution. The RTU-PRG is capable of
a read-out range of 50,000 counts. [f programmed
for operation at this resolution, however, the units
digit is relatively susceptable to noise. Though it is
possible to lessen the impact of this by setting large
digital filtering values it is probably more effective to
choose a different resolution.
For example, a RTU-PRG unit is to be used to
provide read-outs of specific gravity based on input
from a millivolt transmitting sensor. The range of
input to the unit is to extend from 0.5 to 2.0 mV.
Probably the most obvious output format is from
+00000.50 to +00002.00, however, this yields an
effective resolution of only 150 counts.
Since the specific gravity of water is defined as “17,
better use of the accuracy of the RTU-PRG would be
gained by programming for read-outs based on
specific gravity of the material in the application as
compared to that of water, a known constant.
Page A-2
C1-3301-01
12/92
The user would then program the RTU-PRG for
read-outs representing the specific gravity of the
material in the application as a “percent of water”,
with “1” as 100%. The sensor data from the
application would then be scaled accordingly for
RTU-PRG read-outs of +00050.00 to +00200.00,
resulting in an effective resolution of 15,000 counts.
Non-linear Transfer Functions
The RTU-PRG is ideal for providing data outputs
from non-linear sensors. The unit uses a linear
“piecing” algorithm to describe the non-linear function
curve. Up to twenty-four segments can be used to
approximate a given curve.
RTU-PRG's may be programmed in the field with
actual sensor inputs when the non-linearity of sensor
input is unknown.
Table A1 is the model incorporated by the unit as the
basis for the non-linear transfer calculations. Fill in
the table values with data from your application, and
use the table as a worksheet in programming the
RTU-PRG with the RTU-PRG.BAT program, de-
scribed later.
Perhaps the two most important points in the table
are the Minimum and Maximum values from the
application. These points specify the endpoints of
the transfer function curve. They are the only points
necessary in programming the RTU-PRG to output
linear sensor data to the host.
The breakpoints are the key to the use of the RTU-
PRG with non-linear sensors. The curve of non-
linear functions is specified in the RTU-PRG by
segments whose endpoints are between the mini-
mum and maximum values. Each of the segment
endpoints is a breakpoint in an approximation of the
application curve.
Up to twenty-four breakpoints can be specified when
defining a “curve”. Figure A1 illustrates the tech-
nique. Figure A2 shows some of the common
applications in which the RTU-PRG:s transfer
function capability can be used.
MAX
MIN
Figure A1. Approximating an Application Curve with
Linear Segments
MAX
|
|
|
L
SINE
Figure A2. Sample Application Curves
Page A-3
C1-3301-01
12/92
Table A1. RTU-PRG Breakpoints Worksheet
Breakpoints Analog Sensor RTU-PRG
input Output
Minimum Хим = YMIN=
Maximum XMAX = YMAX =
00 Xoo = Yoo =
01 Хо1= Уо1 =
02 Xoo = Yoo =
03 Хоз = Уоз =
04 Ход = Yo4 =
05 Xog = Yos =
06 —Xo6s= Y 06 =
07 Xo7 = Yo7 =
08 Хов = Yog =
09 Xog = Yog =
ОА Ход= Yoa =
OB XoB = Yon =
оС Хос = Yoc =
oD Xop = Yop =
OE XoE = YoE =
OF XoF = Yor =
10 X10 = Yio =
11 Х11 = Уи =
12 Х12 = У12 =
13 Х13 = У13 =
14 Х14 = У14 =
75 Rues Yes
16 Xie = Yı6=
Page A-4
CI-3301-01
12/92
Modifying an “Illegal” Curve. If any of the break-
points used in specifying a curve are greater than
either Minimum or Maximum values, the curve is
considered “illegal”. The Minimum or Maximum
value must be modified to compensate for the
offending portion of the application curve.
Figure A3 shows a modified “illegal” curve.
RTU-PRG.BAT —
Programming the RTU-PRG
The RTU-PRG.BAT program is used to set the
Minimum and Maximum values and breakpoints from
the application curve. It may also be used to scale
RTU readouts. Both of these operations can be
performed with or without external excitation.
The program is loaded in the same fashion as the
Utility.bat program for standard units. Refer to the
Calibration Section of this manual for further instruc-
tion.
ILLEGAL
mu begin the program, enter. E AAA
ie so brief logo: screen, , the > program will I bring
me. De on some keyboards) to exit
current screen and load user r selectionte) ir into
RTU- PRG memory:
ap > (Esc. on most keyboards) to exit menu
thout making changes. EE В
© Some input screens, such as the main "Верго-
be gram" screen require the user to enter values,
rather than using the navigation keys. Asa
general rule, try the navigation keys as described
“above, and if the value in the selector highlight
does not change, enter the actual value based
on the data from your ‘application.
MODIFIED
"MAXIMUM
MODIFIED
MINIMUM
Figure A3. Modifying an “illegal” Application Curve
Page A-5
C1-3301-01
12/92
a file tn disk. If an error
‘subsequent programming, the
pr lem ¢ can be fixed.
nce step 3 is complete, choose ew
mM” sub- eng from the Main Menu.
NOTE:
| efer t to the Calibration Section n of this
manual for instruction in hooking up the
re, G for Setup.
he Setup/Ter erm y facil reads the factory settings
onnected module, then brings up an
ditting screen so that the user can make
hanges as necessary. E
Once any changes have been effected, follow
he instructions at the bottom of the s screen do
eturn to hel Main Menu. o
: NOTES TES |
hanging 1 the Baud Rate setting of the
onnected RTU-PRG does not take effect
until the unit’ s Default Mode i is disabled.
: Remember. that changing the Baud
Rate setting for the RTU-PRG without
similarly changing the setting for the Host
“— will cause a communications TIME OUT
ps e “This error cannot be cleared until
in the e settings. are > compatible. ВЕ
5. Thela last t two o sub-r -menus in | the RTU- PRG. BAT
“programe are for setting the Minimum and Maxi-
mum points from the application (#4; ‘Rescale),
and for loading the Breakpoints into the unit
un memory (#5, Reprogram).
| to restore RTU- E т
General Notes
* Use of the RTU-PRG software is REQUIRED
when programing the RTU-PRG without
sources of external excitation. If using a
“dumb” terminal, standard voltage, current, or
frequency excitation sources (as appropriate)
must be used. In such cases, the operational
accuracy of the RTU-PRG is directly propor-
tional to the accuracy of the external excitation
sources.
* The input characteristics of the RTU-PRG
cannot be changed by the user. That is, a
voltage unit cannot be programmed to process
Frequency inputs.
* There is no provision for changing the gain or
offset of the analog processing circuitry.
e Any non-linear function must be totally en-
closed by a rectangular area defined by the
programmed Minimum and Maximum values.
Figure A1 illustrates. Figure A3 shows how the
Minimum and Maximum values can be modi-
fied to compensate for an “illegal” function.
* For each input value, there can be only one
output value. Figure A4 gives two examples of
“illegal” functions that cannot be modified to
work with the RTU.
Page A-6
CI-3301-01
12/92
Figure A4. “Îllegal” Function Curves
Page B-1
C1-3301-01
12/92
Table B1. RTU General Commands Summary
Requires
Response Write
Command: Executes Format Protection
Disable
SWE
$aCA Clear Alarms * YES
saCE | Clear Event Counter * YES
$acz.! Clear Zero Setting * YES
Disable Available Alarm Inputs “ YES
$aDA_} (Configure Alarm Inputs as Discrete Inputs)
Read Discrete Input ON/OFF State * N
$aDI — or Alarm Status nnn ©
$aDOnn Set ON/OFF State Discrete Outputs * NO
$aEA «| Enable Available Alarm Inputs * YES
SaHiSnnnnn.nnT.d Set HI Alarm Trip Point * YES
SaLOSnnnnn.nnT. Set LO Alarm Trip Point * YES
$aND | Read New Data “Snnnnn.nn NO
Read Data *Snnnnn.nn NO
$aRD — (Read Current Output Buffer)
$aRE | Read Event Counter * nnnnnnn NO
$aRH | Read High Alarm Trip Point *Snnnnn.nnM NO
SaRL | Read Low Alam Trip Point *Snnnnn.nnL NO
$aRR + Reset Module * YES
NOTE: Table continued next page.
Page B-2
C1-3301-01
12/92
Table B1. RTU General Commands Summary (continued)
Requires
Response Write
Command: Executes Format Protection
Disable
SWE
$aRS .| Read All Module Settings — *nnnnnnnn NO
Фант. Read Zero Setting Snnnnn.nn NO
Set Deviation Output Zero Point *
$aSPSnnnnn.nnJ Р YES
$aSUnnnnnnnn. Change All Operating Parameters YES
$aTSSnnnnn.nn. Trim Span YES
$aTZSnnnnn.nn.. Trim Zero YES
Disable Write Protection y NO
$а\МЕ (WRITE ENABLE)
The Utility program is the recommended method for
entering the parameters for the RTU, but if needed,
the RTU Programmer's Guide provides information
on the use of the Setup Command.
The RTU Setup Command, $aSUnn nn nn nn),
sets the same basic operating parameters that are
otherwise set with the Utility program, described in
the Calibration Section of this manual.
The command message is comprised of four, two-
digit hex numbers. These set the unit address,
communications parameters, unit-specific special
functions, and the number of displayed digits and
filtering time constants.
Page B-3
C1-3301-01
12/92
Table B2. Discrete RTU Commands Summary
Requires
Response Write
Command: Executes: Format Protection
Disable
$WE
SAACK Acknowledge Command Handshaking y NO
Set I/O Assignments For All Terminals * YES
$aAlQnnnn J Simultaneously
Configures Terminal as INPUT, referencing * YES
$aAlBin..l by LABEL designator
Configures Terminal as INPUT, referencing * YES
Sa Alan. by TERMINAL NUMBER
Configures Terminal as OUTPUT, * YES
$aAOBnn) referencing by LABEL designator
Configures Terminal as OUTPUT, * YES
$aAO Pr referencing by TERMINAL NUMBER
Read I/O Assignments for All Terminals *nnnn NO
$aRA «+ at Once
Read 1/O Assignment of Individual Terminal, n NO
$aRABn- referencing LABEL designator
Read I/O Assignment of Individual Terminal, n NO
$aRAMn) referencing TERMINAL NUMBER
Set ON/OFF State of All Terminals at Once
(Terminals configured as Inputs ignore this * NO
$aDOnnnn-1 command)
Set State of Individual Output Terminal
to ON,
referencing by LABEL designator * NO
$asBnn” (Specifying Input Terminal generates
ERROR)
Set State of Individual Output Terminal
to ON,
referencing by TERMINAL NUMBER * NO
$aSPnn (Specifying Input Terminal generates
. .ERROR)
Set State of Individual Output Terminal
to OFF,
$аСВул.! referencing by LABEL designator * NO
(Specifying Input Terminal generates
ERROR)
NOTE: Table continued next page.
Page B-4
C1-3301-01
12/92
Table B2. Discrete RTU Commands Summary (continued)
Requires
Res e Write
Command: Executes: Format Protection
Disable
SWE
Set State of Individual Output Terminal
to OFF,
referencing by TERMINAL NUMBER * NO
$aC Pan (Specifying Input Terminal generates
ERROR)
фар! 1 Read ON/OFF State of All Terminals *nnnn NO
Read ON/OFF State of Individual Terminal, “n NO
Вол + ;
San referencing by LABEL designator
Read ON/OFF State of Individual Terminal, *n NO
$aRPnn À referencing by TERMINAL NUMBER
SalVnnnn Set Initial Value * YES
SaRIV.] Read Initial Value *nnnn NO
SaNT=0nnnn.nn- Set the Watchdog Timer * YES
SAW Read the Watchdog Timer Setting * nnnnn.nn NO
$aDn nl Set Module Identification * YES
$aRID Read Module Identification “Пенн. п NO
$aEC | Read Events & Clear Counter *+-nnnnnnn YES
Page B-5
C1-3301-01
12/92
Table B3. Discrete RTU Continuous Mode Commands
Requires
Command: Executes: Response Protection
Format Disable
$WE
SaCMC Set Change-Triggered Continuous Mode * YES
$aCME J Set Edge-Triggered Continuous Mode * YES
$aCMT J Set Timer-Triggered Continuous Mode * YES
$&CTsnnnnn.nn À Set Continuous Timer * YES
$aRCT Read Continuous Timer Setting *nnnnn.nn NO
SaCMI J Set Input-Triggered Continuous Mode * YES
SaRIA À Read the Continuous Input Address *nn NO
$aRCM .- Read the Type of Continuous Mode being used *n NO
$aCMD Disable Continuous Mode Operations * NO
Page C-1
CI-3301-01
12/92
Table C1. Hex-ASCII-Binary Conversion
Module Address | Module Address Module Address
Settings: Code/ | Settings: Code/ Settings: Code/
Code Binary ASCII Code Binary ASCH Code Binary ASCII
Field/ Value Value Field/ Value Value Field/ Value Value
Hex (See Hex (See Hex (See
Value Note) Value Note) Value Note)
00 00000000 20 00100000 (space) 40 01000000 @
01 00000001 21 00100001 41 01000001 A
02 00000010 22 00100010 “ 42 01000010 B
03 00000011 23 00100011 Ne 43 01000011 C
04 00000100 24 00100100 и 44 01000100 D
05 00000101 25 00100101 %, 45 01000101 E
06 00000110 26 00100110 a 46 01000110 F
07 00000111 27 00100111 47 01000111 G
08 00001000 28 00101000 48 01001000 H
09 00001001 29 00101001 ) 49 01001001 |
ОА 00001010 2A 00101010 * 4А 01001010 J
OB 00001011 2B 00101011 + 4B 01001011 K
оС 00001100 2C 00101100 4C 01001100 L
OD 00001101 2D 00101101 - 4D 01001101 M
OE 00001110 2E 00101110 ; 4E 01001110 N
OF 00001111 2F 00101111 / 4F 01001111 O
10 00010000 30 00110000 О 50 01010000 Р
11 00010001 31 00110001 1 51 01010001 Q
12 00010010 32 00110010 2 52 01010010 R
13 00010011 33 00110011 3 53 01010011 S
14 00010100 34 00110100 4 54 01010100 T
15 00010101 35 00110101 5 55 01010101 U
16 00010110 36 00110110 6 56 01010110 Vv
17 00010111 37 00110111 7 57 01010111 W
18 00011000 38 00111000 8 58 01011000 X
19 00011001 39 00111001 9 59 01011001 Y
1A 00011010 3A 00111010 : 5A 01011010 Z
1B 00011011 ЗВ 00111011 ; 5B 01011011 [
1C 00011100 3C 00111100 < 5C 01011100 \
1D 00011101 3D 00111101 = 5D 01011101 ]
1E 00011110 3E 00111110 > SE 01011110 A
1F 00011111 3F 00111111 ? 5F 01011111
|
NOTES: 1.Non-printable ASCI characters are not recommended for use as RTU addresses, and are not
shown in this table. | |
2. The ASCII characters for 23, 23, and 7F hex, represented by the symbol “IM ” in the table, are
not to be used.
3. This table is continued on the next page.
Page C-2
C1-3301-01
12/92
Table C1. Hex-ASCII-Binary Conversion (continued)
Module Address | Module Module Module
Settings Code/ ¡Settings Settings Settings
Code Binary ASCII Code Binary Code Binary Code Binary
Field/ Value Value Field/ Value Field/ Value Field/ Value
Hex (See Hex Hex Hex
Value Note) Value Value Value
60 01100000 ‘ 80 10000000 AO 10100000 DO 11010000
61 01100001 a 81 10000001 A1 10100001 D1 11010001
62 01100010 b 82 10000010 A2 10100010 De 11010010
63 01100011 с 83 10000011 AS 10100011 D3 11010011
64 01100100 d 84 10000100 A4 10100100 D4 11010100
65 01100101 e 85 10000101 A5 10100101 D5 11010101
66 01100110 f 86 10000110 Аб 10100110 D6 11010110
67 01100111 g 87 10000111 A7 10100111 D7 11010111
68 01101000 h 88 10001000 A8 10101000 Da 11011000
69 01101001 i 89 10001001 A9 10101001 D9 11011001
6A 01101010 j 8A 10001010 AA 10101010 DA 11011010
6B 01101011 K 8B 10001011 AB 10101011 DB 11011011
6C 01101100 | 8C 10001100 AC 10101100 DC 11011100
6D 01101101 m 8D 10001101 AD 10101101 DD 11011101
6E 01101110 n 8E 10001110 AE 10101110 DE 11011110
SF 01101111 o 8F 10001111 AF 10101111 DF 11011111
70 01110000 p 90 10010000 BO 10110000 ЕО 11100000
71 01110001 q 91 10010001 B1 10110001 Et 11100001
72 01110010 r 92 10010010 B2 10110010 E2 11100010
73 01110011 5 93 10010011 B3 10110011 E3 11100011
74 01110100 t 94 10010100 B4 10110100 E4 11100100
75 01110101 u 95 10010101 B5 10110101 ES 11100101
76 01110110 Vv 96 10010110 B6 10110110 E6 11100110
77 0111011 W 97 10010111 B7 10110111 Е7 11100111
78 01111000 X 98 10011000 B8 10111000 ES 11101000
79 01111001 y 99 10011001 B9 10111001 E9 11101001
7A 01111010 7 9A 10011010 BA 10111010 EA 11101010
78 01111011 { 9B 10011011 BB 10111011 EB 11101011
7C 01111100 | oC 10011100 BC 10111100 EC 11101100
7D 01111101 } aD 10011101 BD 10111101 ED 11101101
7E 01111110 ~ 9E 10011110 BE 10111110 EE 11101110
7F 01111111 E 9F 10011111 BF 10111111 EF 11101111
Co 11000000 FO 11110000
C1 11000001 Fi 11110001
C2 11000010 F2 11110010
C3 11000011 F3 11110011
C4 11000100 F4 11110100
C5 11000101 F5 11110101
C6 11000110 F6 11110110
“C7 11000111 F7 11110111
C8 11001000 F8 11111000
Ca 11001001 F9 11111001
CA 11001010 FA 11111010
CB 11001011 FB 11111011
CC 11001100 FC 11111100
CD 11001101 FD 11111101
CE 11001110 FE 11111110
CF 11001111 FF 11111111
Page D-1
C1-3301-01
12/92
The standard RTU has an average response time of
approximately 10 milliseconds (ms). Most modems
require an RS-232C “key-up” signal to activate their
internal transmitter. There is also a delay associated
with the turn-on of the transmitter itself. Typically,
the total delay ranges from 150 to 500 ms. Referto
the manual for your modem for the total delay time.
The RTS Option is required for RTU use with radio,
leased line, and standard dial-up modems with no
auto-answer capability. RTU's equipped with RTS
provide an RS-232C Request-to-Send (RTS) signal,
and have three, user-programmable time delays for
“holding” and sequencing data until the connected
modem is ready to send (see Figure D1).
NOTE
Depending upon the type of modem used
in the application, certain installations
may also require a separate Radio
Modem Interface unit, available from the
factory (see Figure D2). Consult your
Sales Representative for details.
The RTS Option Commands
There are nine command s that control and read the
operating parameters of the RTS-equipped RTU.
They are:
e Read T1— $aRT1
e Read T2— $aRT2
е Read T3 ~ $aRT3
o *Set Time Delay 1 (T1)- $aTi+nnnnn.nn
o *Set Time Delay 2 (T2) - $aT2+nnnnn.nn
e *Set Time Delay 3 (T3) - $aT3+nnnnn.nn
o *Set RTS Active High — $aRTS+
e *Set RTS Active Low — $aRTS—
e *Disable RTS — $aRTSD
* These commands must be preceded by a
Write Enable command.
Delay Time 1
T1 is the “dead time” interval between the receipt of
a command from the Host and a transmit from the
RTU. The delay begins upon receipt of the carriage
return at the end of a valid RTU command from the
Host.
Command:
Typical Response:
$aTi+nnnnn.nn.]
*
Where “nnnnn.nn’ stands for a time value in milli-
seconds. For example, $2T1+00125.00.1 sets T1 in
ВТУ “2” to 125 ms.
After the T1 interval, the setting for T2 is called, and
that delay interval is begun.
Delay Time 2
This delay provides a time period for the transmitting
of the RTS signal and modem “key up”. The delay is
triggered by the end of the T1 interval.
Command:
Typical Response:
$SaT2+nnnnn.nn
*
The T2 setting, like T1, is also scaled in milli-
seconds.
After the T2 interval, the setting for T3 is caled, and
the final delay period begins.
Page D-2
C1-3301-01
12/92
Delay Time 3
The final delay, T3, is the period of time between the
last character transmitted by the RTU and the trailing
edge of the RTS signal, which is typically used to
turn off the modem (remote transmitter).
Sat3+nnnnn.nnt
*
Command:
Typical Response:
Like the other two delay settings, T3 is scaled in milli-
seconds.
Use the appropriate Read commands, RT1, RT2, or
RT3, to check the settings of these parameters.
Setting the RTS Signal HIGH
This command sets the state of the RTS pin on the
RTU to HIGH. When idle, this pin will be negative.
Command: SaRTS+..]
*
Typical Response:
Use this command when connecting the RTU to
modems that require a positive voltage signal to
enable their transmitting cycle.
Setting the RTS Signal LOW
This command sets the state of the RTS pin on the
RTU to LOW. When idle, this pin will be positive.
Command: SanTs—
*
Typical Response:
Use this command when connecting the RTU to
modems that require a negative voltage signal to
enable their transmitting cycle.
NOTE
Either of the preceding commands over-
rides the setting for an alarm or digital
output on pin 5 of the RTU.
Disable the RTS Signal
This command disables the Option, returning pin 5 of
the RTU to its standard discrete or alarm output
setting.
Command:
$aRTSD.!
Typical Response: *
Connecting the RTS-Equipped RTU
Pin 5 of the RTU, refer to table 3 of this manual, is
used to connect the unit's RTS-associated outputs to
the modem. This pin is labeled “DO@/LO”.
Any setting for this terminal, typically effected in the
Utility program (refer to the Calibration Section), is
over-ridden by the RTS. l.e., the default for pin 5 is
the RTS signal. To use that terminal as a discrete or
alarm output, the RTS Option must be disabled.
NOTE
The delay settings in the RTU serve only
to guarantee a minimum turn-around
time. The actual delay is a function of the
command response time of the RTU and
the amount of time necessary for the
modem’s transmitter to turn off, after the
RTS signal becomes inactive.
Consult the Bristol Babcock for information on
available RS-485-to-RS-232C converters, modems,
and other communications devices.
Page D-3
C1-3301-01
12/92
DPC 3330
ОРС 3335
MODEM
Internal DPC Modem
Private leased phone line
( MODEM )
MODEM ( MODEM )
RS 232
RTU
RTU MODEM
A1400
За 3301 INTERFACE | 1
w/ATS
RS 485
RTU RTU ATU
3301 3301 3301
Figure D1 - Private Leased Line Network
DPC 3330
DPPC 3335
RADIO
RADIO RADIO ( RADIO
RS 232
RTU RADIO
3301 oe MODEM | A1400 _
w/ATS WIRTS ‚ INTERFACE
AS 485
RTU вто
3301 3301 5301
Figure D2 - Radio Network
Page D-4
C1-3301-01
12/92
DPC 3330
DPC 3335
MODEM
AUTO ANSWER
MODEM
RTU ATU RS 232
TRANSMIT ECE
3301 3301 R Е
| | | i
RTU АТО RTU
3301 3301 3301
Figure D-3 Dial-up Network
DPC 3330
ОРС 3335
RS 423
24v POWER SUPPLY, RS 232 TORS 485
| A1100 | CONVERTER, SURGE SUPPRESSION
RS 485
UP TO 4,000 FEET A1300 UP TO 4,000 FEET
REPEATER
RTU he RTU RTU RTU RTU
3301 3301 | — ———]———— 3301 3301 3301
32
NODES
Figure D-4 RS 485 Network
Page E-1
C1-3301-01
12/92
Private Leased Line Connections
As discussed in Appendix D - RTS Option, the RTU 3301 is capable of communicating over private
leased line, dial lines, and radio networks. Whenever the RTU 3301 is to communicate via private
leased lines or radio, an RTS delay is required. Some RTU 3301s have an internal RTS option
available for this purpose, however this is not practical in all cases. The internal RTS option can be
used to allow a single RTU to interface to a single modem, either private leased line or radio modem.
When more than one RTU is to interface to a single modem the RTS delay must be provided in an
external modem interface. You cannot multidrop RTUs with the internal RTU option: Bristol's A1400
modem interface is used for that purpose.
The A1400 modem interface provides variable RTS delay capability for radio and private leased line
applications. It also provides an RS 485 to RS 232 conversion allowing multiple RTUs to be
multidropped into a single modem. Even if only one RTU is to be interfaced to the A1400 modem
interface, the RTU must be RS 485.
Since the internal RTS feature utilizes one of the discrete outputs on the RTU, certain applications
may dictate the use of the A1400 with external RTS.
Bristol's DPC 33xx family of process controllers have optional private and switched network modems
available for use with RTU 3301 networks. Both modems are Bell 3002 compatible. The external
modem at the RTU 3301 must also be Bell 3002 compatible as are the external modems provided by
Bristol Babcock.
When using the RTU 3301 in a dial line network the RTS delay is not required.
Dial line Modems
The RTU 3301 can be used in dial line networks using Vocal 2400 baud Stowaway modems. In this
network, the host DPC 33xx can initiate dialing a number of RTU 3301s located at distant field points.
The modem at the RTU 3301 will auto-answer. Once communication is established, the DPC will poll
the RTUs attached to the remote modem. One or more RTUs may be connected to each remote
modem. When two or more RTUs are connected to the remote modem, the RTUs must be con-
nected in a RS-232 daisy chain with echo mode enabled. Echo mode provides a serial transmission
of all messages from one RTU to the next. The RTU with the target address will respond and send
the response to the next RTU which echoes to the next RTU until the last RTU on the daisy chain
transmits the response to the modem.
With this dial line network, it is also possible for the remote RTUs to autodial the master DPC in the
event of an alarm. In this scenario, the remote modem is normally in an auto answer mode. If the
RTU detects an alarm, the High alarm or Low alarm output will trigger the modem to dial the internally
stored phone number of the: master DRCs modem.--©Once-communication is established, the DPC will
poll the RTU that initiated the dial. If communication cannot be established, the remote modem will
redial every three minutes for thirty minutes in an attempt to connect.
The following modem setups and wiring diagrams are provided for a sample configuration. Refer to
the ACCOL {Il reference manual and RTU 3301 Custom Module Interface Manual C1-3301-05 for
further information.
Page E-2
CI-3301-01
12/92 _
BRISTOL SWITCH NETWORK MODEM SWITCH SETTINGS
SW1-1 OFF | NO PSTN TIME LIMIT
SW1-2 OFF | 8 MS RTS/CTS DELAY
UDS SW1-3 OFF | IGNORE ABSENCE OF LOOP CURRENT
2021 RTU 3301 SW1-4 OFF | NORMAL OPERATION
MODEM RS232
RS232 SW1-5 OFF | INCOMING RING HAS NO EFFECT
LLO © SW1-6 OFF | 8 MS RTS/CTS DELAY
SW1-7 OFF | 8 MS RTS/CTS DELAY
RXD{ 3 (2) SW1-8 OFF | 8 MS RTS/CTS DELAY
SW2-1 OFF | NORMAL OPERATION
SW2-2 OFF | IGNORE LONG SPACE
en (7 @
SW2-3 OFF | RTS CONTROL CARRIER
(5) RTS (Do/LO) SW2-4 OFF | NO LONG SPACE SENT
© SW2-5 OFF | ANTI-STREAMING
4.7K SW2-6 ON | 4-WIRE
(7) TXD SW2-7 OFF | IGNORE LOSS OF CARRIER
OFF | NORMAL OPERATION
RXD ОН
©, SW3-1 BELL STANDARD
SW3-2 OFF |1200 BAUD
(10) + SW3-3 OFF | EQUALIZER
SW3-4 OFF | NORMAL OPERATION
SW3-6 OFF
SW3-7 OFF
SW3-8 OFF
BRISTOL PRIVATE LEASED LINE MODEM SWITCH SETTINGS
SW1-1 ON BELL STANDARDS
SW1-2 ON 1200 BAUD
SW1-3 ON ORIGINATE MODE
SW1-4 OFF | NORMAL OPERATNG MODE
SW1-5 OFF | NORMAL OPERATING MODE
SW1-6 OFF | CONTROLLED CARRIER MODE
SW1-7 OFF | ENABLE ANTISTREAMING TIMER
SW1-8 OFF | NOTUSED
W1 25ms
W2 4-WIRE
UDS 202T JUMPER SETTINGS
RTS/CTS DELAY 219 ms
TRANSMIT CARRIER ON
LOCAL COPY SQUELCH OUT
CALL TURNAROUND SQUELCH OUT
TURNAROUND SQUELCH TIME 8.3 ms
SOFT CARRIER TURN OFF Oms
..CARRIER DETECT LEVEL -30dBm
CARRIER DETECT DELAY 6 ms
TEST GENERATOR BAUD RATE 75 bps
ANTI-STREAMING OPTION OUT
CHassis/SYS/GND OUT
2-WiRE/4-WIRE 4-WIRE
TRANSMIT LEVEL 0
Figure E -1. RTU 3301 Private Leased Line Configuration
Page E-3
C1-3301-01
12/92
ACTIVE PROFILE:
B1 El L2 M1 QU Vi X4 YO 8C9 EDO &EO &GO &JO &lO &PO 2Q0 &НВО &50 &ХО
& YO
500:001 561:000 502:043 503:013 504:010505:008 SO6:002 507:030
508:002 509:006 510:014 512:050 S14:2AH S21:00H S22:76H S23:11H
S25:005 S26:001 S27:40H
STORED PROFILE ©:
B1 El L2 M1 QÍ Vi X4 YO &CO &DO &EO EGO &JO ELO 2PO EQS &RO &SO &XO
с00:201 S14:2AH S21:00H S22:726H $S23:11H S25:005 S26:001 S27:40H
TELEPHONE NUMBERS;
&ZO=
&Z1=
&72=
&L3=
Figure E -2. Master Modem Settings
ACTIVE PROFILE;
B1 ES L2 M1 Q1 Vi X4 YO 3C9 8DO SES &GO &JO ELO APO 82Q0 8RO ESO &8XO
&YO
500:001 501000 SO?:043 SO3:013 SO4:901@0 SO5:008 SO6:OO2 SO7:030
508:002 SO9:006 S10:014 S12:050 S14:ACH S21:30H S22:76H S23:1 1H
S25:005 5S26:001 S27:40H
STORED PROFILE O:
B1 ES L2 Mi Q1 V1 X4 YO &CO &DO &EO &GG &JO &LO &PO &QO 2RO ESO &XO
500:001 Si4:ACH S21:99H S22:76H S23:11H S25:005 S26:001 S27:40H
TELEPHONE NUMBERS:
&70= T3213 : Master's phone number
&Z1=
&72=
&73=
Note: S23 contains the baud rate; here sent for 300 baud.S14 contains Originate/Answer and other
options: bit 7 is set in the Master (originate) and clear in the Slave (Answer).
Figure E-3. Slave Module Settings
Page E-4
Ci-3301-01
12/92
25-PIND
CONNECTOR
TO MODEM
15-P
D CONNECTOR
PC 3330
D
CUSTOM PORT
> O
© (©
@
OÙ
2AVDC
POWER SUPPLY
DPC3330
Figure E-4.
XMT 3301
#1
(3) ©
D CONNECTOR
TO MODEM G) © Go)
(DCE DEVICES)
© O
©
©
(o—e
(Ie
3301
OG
24VDC
POWER SUPPLY
Connection Diagrams
STANDARD 12-MONTH WARRANTY
Instruments described and manufactured by Bristol Babcock are warranted to be free from
defects in material and workmanship for a period of 12 months from date of shipment. Parts
repaired or replaced under this warranty are warranted to be free from defects in material and
workmanship for a period to the end of the original warranty period or ninety (90) days from the
date of shipment of repaired or replacement paris, whichever is later.
Bristol Babcock's sole obligation under this warranty shall be limited to repair or replacement
on a return-to-factory basis, provided Buyer notifies Bristol Babcock in writing within ten (10)
days of discovery by Buyer of such defect. Buyer may request warranty service on an on-site
basis, for which Buyer will be charged standard per diem service rates, plus applicable, travel,
living and overtime expenses incident to the on-site visits of Bristol Babcocks service
personnel. Buyer shall also be responsible for costs of removal, dismantling, reinstallation and
other similar costs.
Bristol Babcock shall have no obligation whatsoever under this warranty with respect to defects
that arise out of or are related to, but not limited to, any of the following:
(a) Goods subject to misuse and/or abuse;
(b) Goods that have been repaired, altered or modified without Bristol Babcock's consent;
(C) Goods which are not installed, maintained and/or operated in accordance with instruc-
tions furnished by Bristol Babcock.
Warranties on goods sold by, but not manufactured by Bristol Babcock are expressly limited by
the terms of the warranties given by the manufacturers of such goods.
In no event shall Bristol Babcock be liable for incidental or consequential damages arising out
of or related to this warranty or any breach thereof. THE WARRANTIES STATED HEREIN
SHALL BE THE ONLY WARRANTIES WITH RESPECT TO THE SUBJECT MATTER
HEREOF AND SHALL BE IN LIEU OF ALL OTHER WARRANTIES, EXPRESSED OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANT-
ABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
Bristol Babcock
1100 Buckingham Street W18453
Watertown, CT 06795
FACTORY REPAIR SERVICE & REPLACEMENT PARTS
Before you can return an instrument for repairs, you must first obtain a return authorization number from us. You may do
this by writing to the address below or by calling (203) 575-3443. Never ship an instrument without advance clearance as
this will cause confusion and delays.
When returning equipment for repair, a copy of this form must be filled out and attached to the instrument for proper
identification. Maintain a copy of the completed form for your reference.
Requests for in-warranty repairs must be checked off below when filling out this form. The warranty conditions are stated
on the opposite side of this page. All return shipments, whether in or out of warranty, must be prepaid by the sender.
There will be a nominal charge for repair estimates. If you agree to proceed with repairs, only the repair costs will apply.
Replacement parts or accessories may be ordered from our address below, attention of: Sales Order Processing
Dept., or by calling (203) 575-3000. Be sure to include the parts description, part number, model number and serial
number. All orders are subject to a minimum billing fee.
REQUIRED INFORMATION FOR FACTORY REPAIRS
Instrument Model No. Serial Number
Return Authorization Number
Return Approved By Customer Purchase Order No.
(Required for all returned equipment)
Date. Requested Return Date . ——— Warranty Repair Request: Yes No
Return Address:
Attn:
Person to contact for additional information:
Name Telephone ( ) Ext
Describe Problem:
Ship prepaid to: Bristo! Babcock
Attn. Instrument Repair Dept.
1100 Buckingham Street
Watertown, CT 06795
W18452 -a-
U.S.A.
Bristol Babcock Inc.
Process Control Group World Headquarters
_ 1100 Buckingham St., Watertown, CT 067985
Telephone: (203) 575-3000
Telex: 96-2417 BRIS BAB WBY
Fax: (203) 575-3170
Bristol Babcock Inc.
Bristol Babcock
U.K. and European Headquarters
Bristol Babcock LTD.
Vale Industrial Estate
Stourport Road, Kidderminster,
Worcestershire, DY11 7QP., England
Telephone: Kidderminster (0562) 820001
Telex: 339586
Canada
Bristol Babcock Canada
234 Attwell Drive
Toronto, Ontario MOW 583
Telephone: (416) 675-3820
France
Bristol Babcock s.a.
31. rue du General Leclerc
60250 Mouy France
Telephone: 44 56 52 08
Telex: 140397 +
Fax: 44 26 43 73
Printed inthe U &
">