SiteSentinel Automated Monitoring System Model 2 and Model 3. Operator Manual Software Version 1.12CUS

SiteSentinel

MEASUREMENT UNITS

US (feet, gallons,

Metric (centimeters,

fahrenheit degrees)

liters, Celsius degrees)

EVENT HISTORY BUFFER

Wrap Around

Enabled

Disabled

STATUS GRAPH SETUP (MODEL II ONLY)

Smart Module Display Feature

Enabled

Disabled

Graph Type

Tank

Probe

Both

Sensor Status Display

Text

Bar

Both

I/O Module Display Feature

Enabled

Disabled

RED LIGHT/BUTTON & BUZZER SETUP

Light Term

Days: ______ Hours: ______ Minutes: ______ Seconds: ______

Buzzer Term

Days: ______ Hours: ______ Minutes: ______ Seconds: ______

Button Terminates

Light

Buzzer

Both

Neither

SENSOR & PROBE ASSIGNMENTS

POSITION

134

Appendix B - Modem Use

B.1 Overview

The SiteSentinel system can be polled and programmed remotely using a pair

is at the SiteSentinel site; the "remote" modem is located at the distant location.

Set baud rate as follows.

Baud Rate Setup

PV235 DIP Switch Position:

Rate

110

OPEN

330

CLOSED

OPEN

600

OPEN

CLOSED

OPEN

1200

CLOSED

OPEN

2400

OPEN

CLOSED

4800

CLOSED

OPEN

CLOSED

9600

OPEN

CLOSED

19,200

CLOSED

Switch Position #4, Word Length:

OPEN

7-bit word, even parity

CLOSED

8 bit word length, NO parity*

* Always use this setting for international systems

Switch Positions #5 - #7:

Always OPEN

Switch Position #8:

Always CLOSED.

143

SiteSentinel

Set switches BEFORE power-up or reset! The switches are only "read" at power up.

Refer to the Installation Manual for more information.

IMPORTANT

Word length and parity must match for the

COMM port, the local modem and the

remote modem.

The communication parameters can only

be changed with the system OFF!

DCD. A signal from the modem which tells the SiteSentinel a call has been received

DTR. A signal from the SiteSentinel to the modem which allows the modem to answer.

B.2 Local Modem Configuration

The modem connected to the SiteSentinel controller must have an "answer only" configuration. The following

parameters must be set for any type of modem used locally with the SiteSentinel. Refer to your modem

documentation for more information on setting the parameters.

Parameter

Command

Answers on 1st ring

ATS0=1

Monitors DCD

AT&C1

Result codes not returned

ATQ1

Reset when DTR is off

AT&D2

After entering the commands listed above for a Hayes® modem, enter `AT&W' to store the configuration

permanently.

B.3 Remote Modem Configuration

For a PC-programmable Hayes® (or 100% compatible) modem, use `AT&F' command to load factory

configuration. Refer to your modem documentation for more information on setting the parameters.

B.4 Calling a Site

The SiteSentinel system must be in the "idle" mode; that is, no one must be programming the system or

requesting data from the controller or from another terminal or computer. When the call to the remote

modem is successful, the SiteSentinel prompts for the type of terminal (or terminal emulation) you are

using. Enter `1' for WYSE 50, `2' for VT100, or `3' for VT52. The MAIN MENU should display.

To terminate modem operation, enter `Q' (for quit) at the MAIN MENU. If you enter `4' for the type of

terminal ("none of the above"), you will not be able to access the SiteSentinel. Refer to Appendix E for

information about terminal emulation.

144

Appendix C - EPROM Replacement Procedure

C.1 Overview

Two EPROM chips on the Model II PV235 controller board or the Model III PV271 controller

board contain the operating system for the SiteSentinel controller. The location of these chips is

shown in your Site Sentinel Installation Manual.

The operating system for each Smart Module is contained in one microcontroller chip on the PV242

board. The location of this chip is also in your Site Sentinel Installation Manual.

CAUTION

Be very careful when handling the EPROM and microcontroller chips. Avoid applying

excessive pressure when inserting a chip into its socket. The chips are also sensitive to

electrostatic discharge and should be handled in only a static-free environment.

C.2 Controller EPROM Replacement

The controller software version is identified by both a number and a letter code; for example, 1.12A.

Replacement procedure depends on whether the entire number changed, or if only the letter changed.

C.2.1 New EPROM Number

If replacing EPROMs with an entirely new version number (for example, replacing a “1.12" with a

“1.13"), make sure the site and system data are written down. When the EPROMs are replaced, this

information will be lost and must be reentered.

1. Turn controller power OFF: In Model II, flip the switch inside the cabinet. In Model III, unplug

the power pack from the back of the controller.

2. Using a chip replacement tool (or a small screwdriver), carefully remove the old chips.

3. Carefully plug the new chips into their sockets. The notch on the chip must face the socket screw.

Make sure all metal contacts are properly inserted.

4. Power up the controller.

5. Perform the cold start procedure described on Page 165.

C.2.2 New EPROM Letter ONLY

Follow the same procedure, but MAKE SURE THE INTERNAL BATTERY in either the Model II

or III is plugged in and operational. As long as the battery is connected and you are only updating

with a new letter version of EPROM, data is retained.

145

Appendix D - Liquid Sensor Drying Procedure

D.1 Overview

When a Petro Vend hydrocarbon liquid sensor (interstitial or liquid phase) comes in contact with

a liquid hydrocarbon product, the sensor must be allowed to dry completely before it can be

returned to normal operation.

D.2 Gasoline Activation

When the hydrocarbon liquid sensor comes in contact with gasoline, it should be removed from its

operating environment and exposed to the air to facilitate the drying process. This process usually

requires less than an hour. Do not return the sensor to a contaminated location.

D.3 Activation by Other Petroleum Products

Because denser petroleum products, such as diesel fuel, do not evaporate as readily as gasoline, a

hydrocarbon liquid sensor that comes in contact with such a product must be cleaned with VM&P

Naphtha. This is a paint solvent and additive that is available at most hardware and painting supply

stores. To clean a sensor with VM&P Naphtha, please follow these steps:

1. Turn off the power to the Smart Module to which the sensor is connected.

2. Disconnect the sensor wires from the module and remove the sensor from its operating

environment.

To return the Smart Module to normal operation, turn its power back on at this point.3.Obtain

a container made of a material that does not react with naphtha and that is large enough to hold

the entire sensor.

4. In a well ventilated room, fill the container with naphtha and submerge the sensor for at least 12

hours.

If the sensor has been thoroughly contaminated, this time should be extended.

5. Remove the sensor and allow it to dry for at

least 12 hours.

DANGER!

Naphtha is extremely flammable.

6. After cleaning and drying, return the sensor

to its operating environment; do not return

Follow the safety precautions on

the sensor to a contaminated location.

the container.

7. Turn off power to the Smart Module and

reconnect the sensor wires. Turn on power

to the module.

147

Appendix E - PC Connections

E.1 Introduction

These instructions explain how to connect an IBM® compatible personal computer ("PC") to the

SiteSentinel. Also explained is the terminal emulation software your PC needs in order to talk with

the SiteSentinel.

See Appendix K, Computer Access, on Page 189 for information on writing programs to control the

system by external computer.

E.2 Local Vs. Remote

There are two ways a SiteSentinel can be installed.

Local. If the distance between the controller and the PC is less than 50 feet, the controller is wired

to a junction box located near the PC ("direct connection").

Remote. When the distance is greater than 50 feet, modems are required and telephone lines are used

to connect the two units. The following two sections describe connections for each of these types

of installation. Follow the section which is appropriate for your system.

CAUTION

Before making any connections, be sure your computer and equipment (printer, converter,

modem, etc.) are OFF.

E.3 Local Connection

Use a cable with a 25-pin connector. This cable plugs into the serial port of your PC. This port, also

known as the Communications Adapter Connector (CAC), is usually on the back of the PC.

If the serial port is not clearly labeled, refer to the PC system reference guide; there may be other 25-

pin sockets on the PC that are not the serial port and can not be used for communication.

If your serial port is a 9-pin socket, you will need to purchase a 25- to 9-pin converter plug

(available at computer supply stores). Make sure the plug is securely in place.

If you are already using the serial port, you can purchase an additional serial port card for the PC

at most computer supply stores. The card is a small circuit board that plugs into a slot inside the

PC.

You are now ready to power up the PC and begin setting up the emulation software.

149

SiteSentinel

E.4 Modem Connection

A modem converts computer data into a format that can be sent over standard telephone lines. A

second modem at the receiving site converts the data back to a computer format. A Hayes® modem,

also available from Petro Vend, is preferred for the PC site. Because the SiteSentinel uses Hayes®

commands, you must use Hayes® (or 100% compatible) modems.

Most modems have four sockets: (1) a wide 25-pin socket to connect to the PC, (2) a square 4-pin

socket to connect to the telephone line, (3) a square 4-pin socket to connect to a telephone and (4)

a 2-wire socket for the AC power adapter. The modem should have come with the cables you need

to make the following connections.

(If not, you can purchase what you need at most computer

supply stores.)

Connect the 25-pin socket to the socket for the serial port of your PC. This socket, also known as

the "Communications Adapter Connector," is located on the back of most PCs. Make sure the plug

is securely in place.

Connect the 4-wire "line" socket to the telephone jack. The cable plugs should snap into position and

fit snugly.

If you want the PC to share its line with a telephone, connect the 4-wire "phone" socket to the

telephone. Note that you must use the telephone and computer alternately, not simultaneously.

Plug the power adapter into its socket on the modem and into a standard 115 VAC wall socket. You

are ready to power up the PC and modem and to begin setting up your terminal emulation software.

E.5 Emulation Software

In order for a PC to communicate with the SiteSentinel, you must run a terminal emulation

program such as ProComm®.

If you are using direct connection, you will need to set the software to "go local". If you are using

a modem, you will need to set its program switches. You will also need to enter the telephone

number of the SiteSentinel site.

IMPORTANT

The terminal emulator program must must

be set for the same communication

parameters (baud rate, word size, etc) as

the SiteSentinel controller.

150

Appendix F - Report Protocols & Data Formats

IMPORTANT

The information in this appendix applies only to a system that is connected to an IBM®-

compatible personal computer ("PC") or other system capable of ASCII transmissions.

To facilitate the creation of interface software for external computer systems (which

automatically execute SiteSentinel commands), the menu structures and command names

are identical in both SiteSentinel Models II and III. However, the menus and commands are

subject to change in future software versions.

F.1 Introduction

Report data from the SiteSentinel can be downloaded to an external computer in a concise format.

The SiteSentinel setup information also can be transmitted to an external computer where it can be

stored for safekeeping. The setup data can be restored to the SiteSentinel from which it was obtained

or to another similar system .

See Appendix K, Computer Access, on Page 189 for information on writing programs to control the

system by external computer.

The SiteSentinel can use any of five protocols when transferring data. The proprietary Petro Vend

("PV") protocol is described below; this protocol is used by other Petro Vend products. The

protocol for transferring data in straight ASCII files is explained in the next section.

The Data Formats section of this appendix explains how numbers, logical values, times and dates are

represented in the computer format. The remaining sections indicate the various computer report

formats.

Refer to Page 55 for information on setting up the computer protocol (input flow control, type of

protocol, and file name). Refer to Page 111 for information about report formats. Refer to Page 107

for information about the backup and restore features.

F.2 Petro Vend File Transfer Protocol

This protocol is line oriented; each line is sent with `/[CHK][CHK][CR][LF]' appended at the end

(where `[CHK][CHK]' indicates the "checksum." The checksum is a two-digit number that is

calculated by adding the decimal values of the ASCII characters in a data string, adding 47, and

truncating the sum. (Table F:1 lists the decimal values of standard ASCII characters.)

For example, in the data string `ABCD', the decimal values for each character are: A = 65, B = 66,

C = 67, and D = 68. Their sum is 266. 266 + 47 = 313. Truncating the sum means removing all but

the last two digits. In this case, the truncated sum is 13. The complete data line that would be is sent

by the SiteSentinel (when using the PV protocol) is: `ABCD/13[CR][LF]'.

151

Appendices

F.3 Decimal Values of Standard ASCII Characters

Decimal

ASCII

Decimal

ASCII

Decimal

ASCII

Decimal

ASCII

Value

Character

Value

Character

Value

Character

Value

Character

032

(space)

056

080

104

033

057

081

105

034

058

082

106

035

059

;

083

107

036

060

084

108

037

061

085

109

038

062

086

110

039

063

087

111

040

(

064

088

112

041

)

065

089

113

042

066

090

114

043

067

091

[

115

044

068

092

116

045

069

093

]

117

046

070

094

118

047

071

095

119

048

072

096

120

049

073

097

121

050

074

098

122

051

075

099

123

{

052

076

100

124

053

077

101

125

}

054

078

102

126

055

079

103

153

SiteSentinel

F.4 ASCII Protocol for File Transfer

The ASCII protocol is intended for use only when another protocol is unavailable.

When ASCII is selected, the SiteSentinel sends reports to the external computer as a straight ASCII

file. The computer can control the flow using either hardware ('RTS') or software handshaking (`XON'

and `XOFF').

For the 'RESTORE' command, the SiteSentinel displays a message requesting the file using ASCII.

It then waits up to one minute for the external computer to start sending data.

Once the computer has started sending data, either hardware handshaking (`CTS'), or software

handshaking (`XON' and `XOFF') must be used to prevent the SiteSentinel from losing data.

A pause of at least 10 seconds or a `CTRL-Z' in the data indicates to the SiteSentinel that the

computer has reached the end of the file.

If software handshaking is to be used, it must be enabled on the SiteSentinel.

F.5 Data Formats

F.5.1 Number Format

The SiteSentinel reports probe and sensor measurements using "floating point numbers." Floating

point numbers are rounded to three decimal digits and are assigned fields that are ten characters in

width.

Negative values are preceded by a minus sign (`-').

If the value is too large for this field, digits to the right of the decimal (and the decimal point itself)

are rounded as necessary. If the value is still too large, a blank field is assigned. See the following

table:

ACTUAL VALUE

COMPUTER FORMAT

12345.12

12345.123

-12345.12

-12345.123

1234567.89

12345678.90

12345678.9

123456789.01

123456789

1234567890.12

1234567890

12345678900.12

F.5.2 Logical Values

Logical values are represented by a `T' (for true) or an `F' (for false).

154

SiteSentinel

F.6 Report Formats

F.6.1 General Report Format

GENERAL LINE FORMAT FOR REPORTS

ttt/<field 1>/<field 2>/.../<field n-1>/<field n>

ttt

Report or Line Title: always 3 characters exactly

Data Field Separator: "forward slash" character

Data Field: the quantity and type of fields included depend on the particular

line type; note that fields of the same type are always the same size, but

different field types may have different sizes

STANDARD FIELD TYPES FOR REPORTS

ttt

Report Title:

INV - Tank Inventory Report or Sensor Levels Report

WRN - Warnings in Progress Report

ALR - Saved Event Report (sensor, probe, input, hardware failures,

& individual)

Line Title:

M01 - Inventory Measurement Header Line

M02 - Inventory Measurement Data Line #1 (individual tank)

M03 - not implemented

M04 - Inventory Measurement Data Line #1 (manifold group)

M05 - Inventory Measurement Data Line #2 (individual tank)

M06 - Inventory Measurement Data Line #2 (manifold group)

M07 - not implemented

M08 - not implemented

M09 - Inventory Measurement Data Line (sensor levels)

M10 - Volume Change Measurement Data Line

M11 - Leak Test Measurement Data Line

WR1 - Warning Header Line

MSG - Alarm Header Line

mmddyyyy

Date of an Event: month, day, year

hhmmss

Time of an Event: hours, minutes, seconds

Units of Measure: F = U.S.; T = Metric

tnk/m/ps

Device Identification:

Tank Number (0 to 999) - label only

Smart Module (1 to 8) - specific hardware installation

Module Position (1 to 16) - specific hardware installation

sen

Device Type:

0 - none

1 - Generic Sensor

7 - Freon Sensor

2 - Probe

8 - Hydrocarbon Liquid Sensor

3 - Vapor Sensor

9 - Water Sensor

4 - Liquid Sensor

200 - SiteSentinel Controller

5 - Sump Sensor

201 - Smart Module

6 - Reservoir Sensor

202 - Manifolded Group

203 - I/O Module

ffffffff

Flags: not implemented

dddddd.ddd

Measured & Calculated Data: floating point value; decimal point is explicit;

if the value is too large for the field, digits to the right of the decimal point are

rounded as necessary

156

Appendices

F.6.2 Individual Tank Summary Report

MEASUREMENT HEADER LINE

M01/u/tnk/m/ps/sen/ffffffff/mmddyyyy/hhmmss

M01

Line Title

Units of Measurement: F = U.S.; T = Metric

tnk/m/ps/sen

Device Identification & Type: tank number (0 to 999) / smart module (1 to 8) / module

position (1 to 16) / device type

ffffffff

Flags: not defined

mmddyyyy/hhmmss

Date & Time of Measurement: month, day, year / hours, minutes, seconds

MEASUREMENT LINE #1

M02/dddddd.ddd/dddddd.ddd/dddddd.ddd/dddddd.ddd/dddddd.ddd/dddddd.ddd

M02

Line Title

dddddd.ddd

Net Corrected Tank Volume

dddddd.ddd

Gross Measured Tank Volume

dddddd.ddd

Volume Left in Tank (ullage)

dddddd.ddd

Product Level

dddddd.ddd

Average Product Temperature (average of temperature sensors which are currently

submersed in product)

dddddd.ddd

Water Level

MEASUREMENT LINE #2

M05/dddddd.ddd/dddddd.ddd

M05

Line Title: always 3 characters exactly

dddddd.ddd

Net Corrected Product Volume

dddddd.ddd

Gross Water Volume

VOLUME CHANGE MEASUREMENT DATA LINE

M10/dddddd.ddd/dddddd.ddd/dddddd.ddd/dddddd.ddd/dddddd.ddd/

M10

Line title

dddddd.ddd

Net Corrected Tank Volume Change

dddddd.ddd

Gross Measured Tank Volume Change

dddddd.ddd

Net Corrected Product Volume Change

dddddd.ddd

Gross Measured Water Volume Change

dddddd.ddd

Estimated Delivery Temperature

157

SiteSentinel

LEAK TEST MEASUREMENT DATA LINE

M11/dddddd.ddd/dddddd.ddd/dddddd.ddd/dddddd.ddd/dddddd.ddd/

M11

Line title

dddddd.ddd

Net Corrected Leak Rate

dddddd.ddd

Water Volume Rate Of Change

dddddd.ddd

Test Duration in Minutes

dddddd.ddd

Temperature Change

dddddd.ddd

Leak Alarm Threshold

SAMPLE DATA STREAM

DESCRIPTION

DATA LINE

(`/' = data separator;

`.' = explicit decimal;

`-'

= blank space;

`[CR][LF]' - carriage return & line feed)

Report Header

INV/01021993/123456[CR][LF]

Measurement Header

MO1/F/--1/1/-1/--2/FFFFFFFF/01021993/120000[CR][LF]

Measurement Line #1

MO2/123456.123/123456.123/123456.123/123456.123/123456.123/123456.123[CR

][LF]

Measurement Line #2

MO5/123456.123/123456.123[CR][LF]

Measurement Header

MO1/F/--2/1/-2/--2/FFFFFFFF/01021993/120000[CR][LF]

Measurement Line #1

MO2/123456.123/123456.123/123456.123/123456.123/123456.123/123456.123[CR

][LF]

Measurement Line #2

MO5/123456.123/123456.123[CR][LF]

Measurement Header

MO1/F/--3/1/-2/--2/FFFFFFFF/01021993/120000[CR][LF]

Measurement Line #1

MO2/123456.123/123456.123/123456.123/123456.123/123456.123/123456.123[CR

][LF]

Measurement Line #2

MO5/123456.123/123456.123[CR][LF]

158

Appendices

F.6.3 Tank Summary Manifolded Group Report

MEASUREMENT HEADER LINE

M01/u/tnk/m/ps/sen/ffffffff/mmddyyyy/hhmmss

M01

Line Title

Units of Measurement: F = U.S.; T = Metric

tnk/m/ps/sen

Device Identification & Type: tank number (0 to 999) / smart module (1 to 8) / module

position (1 to 16) / sensor type

ffffffff

flags: not defined

mmddyyyy/hhmmss

Date & Time of Measurement: month, day, year / hours, minutes, seconds

MEASUREMENT DATA LINE #1

(`-'

= blank space)

M04/dddddd.ddd/dddddd.ddd/dddddd.ddd/----------/dddddd.ddd/----------

M04

Line Title

dddddd.ddd

Net Corrected Tank Volume

dddddd.ddd

Gross Measured Tank Volume

dddddd.ddd

Volume Left in Tank (ullage)

----------

Blank: product level does not exist

dddddd.ddd

Average Product Temperature (average of temperature sensors which are currently

submersed in product)

----------

Blank: water level does not exist

MEASUREMENT DATA LINE #2

M06/dddddd.ddd/dddddd.ddd

M06

Line Title: always 3 characters exactly

dddddd.ddd

Net Corrected Product Volume

dddddd.ddd

Gross Water Volume

159

SiteSentinel

SAMPLE DATA STREAM

DESCRIPTION

DATA LINE

(`/' = data separator;

`.' = explicit decimal;

`-'

= blank space;

`[CR][LF]' = carriage return & line feed)

Report Header

INV/01021993/123456[CR][LF]

Measurement Header

MO1/F/--1/1/-1/--2/FFFFFFFF/01021993/123456[CR][LF]

(Individual Tank)

Measurement Line #1

MO2/123456.123/123456.123/123456.123/123456.123/123456.123/123456.123[CR

][LF]

Measurement Line #2

MO5/123456.123/123456.123[CR][LF]

Measurement Header

MO1/F/--2/1/-2/--2/FFFFFFFF/01021993/123456[CR][LF]

(Individual Tank)

Measurement Line #1

MO2/123456.123/123456.123/123456.123/123456.123/123456.123/123456.123[CR

][LF]

Measurement Line #2

MO5/123456.123/123456.123[CR][LF]

Measurement Header

MO1/F/--3/1/-3/--2/FFFFFFFF/01021993/123456[CR][LF]

(Individual Tank)

Measurement Line #1

MO2/123456.123/123456.123/123456.123/123456.123/123456.123/123456.123[CR

][LF]

Measurement Line #2

MO5/123456.123/123456.123[CR][LF]

Measurement Header

MO1/F/--0/1/-1/202/FFFFFFFF/01021993/123456[CR][LF]

(Manifold Group)

Measurement Line #1

MO4/123456.123/123456.123/123456.123/----------/123456.123/----------[CR][LF]

Measurement Line #2

MO6/123456.123/123456.123[CR][LF]

Note that an Inventory Report data stream for a manifolded group includes both data for the individual tanks and for

the group as a whole.

160

Appendices

F.6.4 Sensor Levels Report

MEASUREMENT HEADER LINE

M01/u/tnk/m/ps/sen/ffffffff/mmddyyyy/hhmmss

M01

Line Title

Units of Measurement: F = U.S.; T = Metric

tnk/m/ps/sen

Device Identification & Type: tank number (0 to 999) / smart module (1 to 8) / module

position (1 to 16) /device type

ffffffff

Flags: not defined

mmddyyyy/hhmmss

Date & Time of Measurement: month, day, year / hours, minutes, seconds

SENSOR DATA LINE

M09/dddddd.ddd/dddddd.ddd/dddddd.ddd/dddddd.ddd/dddddd.ddd

M09

Line Title: always 3 characters exactly

dddddd.ddd

Measured Sensor Values; up to 4 values, depending on type of sensor; floating

point number

SAMPLE DATA STREAM

DESCRIPTION

DATA LINE

(`/' = data separator;

`.' = explicit decimal;

`-'

= blank space;

`[CR][LF]' = carriage return & line feed)

Report Header

INV/010293/120000[CR][LF]

Measurement Header

MO1/F/--1/1/-4/--1/FFFFFFFF/010293/120000[CR][LF]

Sensor Data

MO9/123456.123[CR][LF]

Measurement Header

MO1/F/--2/1/-5/--3/FFFFFFFF/01021993/120000[CR][LF]

Sensor Data

MO9/123456.123[CR][LF]

Measurement Header

MO1/F/--3/1/-6/--4/FFFFFFFF/01021993/120000[CR][LF]

Sensor Data

MO9/123456.123[CR][LF]

Measurement Header

MO1/F/--4/1/-7/--5/FFFFFFFF/01021993/120000[CR][LF]

Sensor Data

MO9/123456.123[CR][LF]

161

SiteSentinel

F.6.5 Warnings In Progress Report

WARNING HEADER LINE

WR1/typ/tnk/m/ps/sen/mmddyyyy/hhmmss

WR1

Line Title

typ

Message Type: (see table below)

tnk/m/ps/sen

Device Identification & Type: tank number (0 to 999) / smart module (1 to 8) /

module position (1 to 16) / device type

mmddyyyy/hhmmss

Starting Date & Time of Warning: month, day, year / hours, minutes, seconds

MESSAGE TYPES

SYMBOL

DEFINITION

SYMBOL

DEFINITION

HPL

High Product Level

LSL

Low Sensor Level

LPL

Low Product Level

IO1

External Input #1

HWL

High Water Level

IO2

External Input #2

TMP

Temperature

PRB

Probe Failure

TFT

Theft

MOD

Smart Module Failure

DEL

Delivery

PRN

Printer Failure

SAL

Sale

POW

Power Failure

TLT

Timed Leak Test

INV

Saved Inventory

HSL

High Sensor Level

IOM

I/O Module Input CLOSED

IOF

I/O Module Failure

SAMPLE DATA STREAM

DESCRIPTION

DATA LINE

(`/' = data separator;

`.' = explicit decimal;

`-'

= blank space;

[CR][LF] = carriage return & line feed)

Report Header

WRN/010293/120000[CR][LF]

Warning

WR1/HPL/--1/1/-1/--1/01021993/090000[CR][LF]

Warning

WR1/LPL/--2/2/-2/--1/01021993/100000[CR][LF]

Warning

WR1/SAL/--3/3/-3/--1/01021993/110000[CR][LF]

162

Appendices

F.6.6 Sensor, Probe, or Input Failure Report

ALARM HEADER LINE

MSG/typ/tnk/m/ps/sen/mmddyyyy/hhmmss/mmddyyyy/hhmmss

MSG

Line Title

typ

Message Types: (see table below)

tnk/m/ps/sen

Device Identification & Type: tank number (0 to 999) / smart module (1 to 8) /

module position (1 to 16) / sensor type

mmddyyyy/hhmmss

Starting Date & Time of Alarm:

mmddyyyy/hhmmss

Ending date & time of alarm

MESSAGE TYPES

SYMBOL

DEFINITION

SYMBOL

DEFINITION

HPL

High Product Level

LSL

Low Sensor Level

LPL

Low Product Level

IO1

External Input #1

HWL

High Water Level

IO2

External Input #2

TMP

Temperature

PRB

Probe Failure

TFT

Theft

MOD

Smart Module Failure

DEL

Delivery

PRN

Printer Failure

SAL

Sale

POW

Power Failure

TLT

Timed Leak Test

INV

Saved Inventory

HSL

High Sensor Level

IOM

I/O Module Input CLOSED

IOF

I/O Module Failure

SAMPLE DATA STREAM

DESCRIPTION

DATA LINE

(`/' = data separator;

`.' = explicit decimal;

`-'

= blank space;

`[CR][LF]' = carriage return & line feed)

Report Header

ALR/01051993/120000[CR][LF]

Alarm Header

MSG/DEL/--1/1/-3/--1/01021993/040000/01021993/050000[CR][LF]

Measurement Header

MO1/F/--3/1/-3/--2/FFFFFFFF/01021993/060000[CR][LF]

Measurement Line #1

MO2/123456.123/123456.123/123456.123/123456.123/123456.123/123456.123[CR][LF]

Measurement Line #2

MO5/123456.123/123456.123[CR][LF]

Measurement Header

MO1/F/--3/1/-3/--2/FFFFFFFF/01021993/070000[CR][LF]

Measurement Line #1

MO2/123456.123/123456.123/123456.123/123456.123/123456.123/123456.123[CR][LF]

Measurement Line #2

MO5/123456.123/123456.123[CR][LF]

Delivery Data

M10/123456.123/123456.123/123456.123/123456.123/123456.123/123456.123[CR][LF]

Alarm Header

MSG/HSL/--1/1/-4/--1/12111992/080000/12151992/090000[CR][LF]

Measurement Header

MO1/F/--1/1/-4/--1/FFFFFFFF/01021993/120000[CR][LF]

Sensor Data

MO9/123456.123[CR][LF]

Alarm Header

MSG/IO1/--0/0/-0/200/12111992/090000/12151992/100000[CR][LF]

Alarm Header

MSG/PRB/--1/1/-1/--2/12111992/100000/12151992/110000[CR][LF]

Alarm Header

MSG/POW/--0/0/-0/200/12151992/110000/12151992/120000[CR][LF]

163

Appendix G - Cold Starting the System

The SiteSentinel II or III is "cold started" when it has no setup or report data. This usually occurs

only when the system is first installed.After the SiteSentinel has been set up, you can clear the system

memory and initiate a cold start with the following steps:

WARNING!

The following procedure erases all setup and report data from the system. The data can not be

recovered after the cold start has been initiated.

Model II

(1)

Disconnect the controller battery. This battery is located inside the controller cabinet, near the reset

switch.

(2)

Turn the power off and then on again. The following message displays:

BATTERY LOW OR DISCONNECTED!

(3)

Press the red button to cold start.

This will clear RAM!

...or wait 20 seconds for a normal startup.

If you do not press the red button after this message appears, the system waits 20 seconds and then

automatically continues with a normal startup (that is, the current data are retained).

(4)

To initiate the cold start, press the red button. The following message displays:

RAM HAS BEEN CLEARED! Connect battery if applicable. Press reset button to restart.

(5)

Reconnect the backup battery.

(6)

Press the reset button. The system is ready to be reprogrammed.

If you do not press the reset button after reconnecting the backup battery, the system waits 10 seconds and

then automatically resets.

Model III

(1)

Disconnect the controller backup battery. This battery is located inside the controller box.

(2)

While holding in the SILENCE button, turn the power off and then on again. A “C” appears on the

STATUS indicator.

(3)

Reconnect the backup battery.

(4)

Press the RESET button.

Your Model III is now ready for reprogramming.

165

Appendix H - Troubleshooting

H.1 Probe/Sensor

Troubleshooting

The probe measures product levels and temperatures in a tank and sends the data to the controller.

Using the programmed tank and product information (size, density, etc.), the controller converts the

measured data into temperature-corrected volumes. The probe also monitors water levels in the tank.

Various sensors are available to measure hydrocarbon vapors, water, freon, etc. All probes and

sensors connect to an intrinsically safe barrier in a Smart Module.

The SiteSentinel reports the probe and data in several ways. The gross and corrected product volumes

are reported in the Quick Sale, Quick Delivery, and Tank Inventory Reports. Product and water levels

are also included. Sensor data appears in the Sensor Level Report (Page 119).

To view present measurements from probes and sensors, view the Tank & Sensor Data Report (see Page

94) This is part of the Smart Module data.

You can program the SiteSentinel to automatically monitor the probes and sensors. The system can

trigger an alarm (buzzer, light, etc.) and/or to print a message when a failure occurs (also see Page 119):

PROBE FAILURE

STATUS CODES: 10P2 5W2 0T0 0D0

MODULE : 1

POSITION : D

PROBE # : 2

DESCRIPTION: NORTHWEST

PRODUCT

: DIESEL

START

: FEB 13, 1993

1:13 AM

END

: IN PROGRESS

HARDWARE FAILURE EVENTS REPORT

If you are using a Model II, you can program the Idle Mode Status Graph to automatically monitor

operation and to report a failure on the controller display.

H.1.1 Procedure

Problems usually result from one or more of the following:

(1)

Improper Setup

(2)

Incorrect Cable & Conduit Installation

(3)

Hardware Failure

167

SiteSentinel

The following sections explain how to analyze these features of the SiteSentinel.

H.1.2 Setup

Incorrect sales, delivery, and inventory data are usually the result of an incorrect probe setup.

Incorrect level data is caused by an incorrect sensor setup. The setup information must be precise

for the report data to be accurate.

To check probe setup, display the PROBE & SENSOR CONFIGURATION MENU (Page 63).

Although an absence of any data usually indicates a hardware problem, it can also occur when the

module position for the device was not installed.

To check the status of a Smart Module or module position, use the INSTALL/REMOVE MODULE

POSITIONS MENU (Page 58).

168

SiteSentinel

SITE SENTINEL

FEB 1, 1995

8:36 AM

DIAGNOSTIC PROBE & SENSOR DATA

1.Module & Position: 1A PROBE

2.Continuous, 4 Second Updates

Tank #: 1

Tank Description:

Product:

DIAGNOSTIC LEVEL 1

STATUS: INFO:

PRODUCT LEVELS

0D0

Rough:

77.5206 IN

6P2

Fine:

77.5209 IN

WATER LEVEL:

3.7194 IN

4W2

0T0

PROBE SENSOR TEMPS

Head:

78.9150 F

Top:

74.4083 F

Middle 3:

74.5590 F

Middle 2:

76.2366 F

Middle 1:

82.4999 F

Bottom:

78.6533 F

PROBE DIAGNOSTIC: PRODUCT & WATER MISSING

H.1.4 Sample Probe and Sensor Diagnostic Printouts

SITE SENTINEL

FEB 1, 1995

8:36 AM

DIAGNOSTIC PROBE & SENSOR DATA

1.Module & Position: 1A PROBE

2.Continuous, 4 Second Updates

Tank #: 1

Tank Description:

Product:

DIAGNOSTIC LEVEL 1

STATUS: INFO:

PRODUCT LEVELS

0D0

Rough:

77.5206 IN

0P0

Fine:

77.5209 IN

WATER LEVEL:

3.7194 IN

0W0

0T0

PROBE SENSOR TEMPS

Head:

78.9150 F

Top:

74.4083 F

Middle 3:

74.5590 F

Middle 2:

76.2366 F

Middle 1:

82.4999 F

Bottom:

78.6533 F

PROBE DIAGNOSTIC: NORMAL

170

Appendices

SITE SENTINEL

FEB 1, 1995

8:36 AM

DIAGNOSTIC PROBE & SENSOR DATA

1.Module & Position: 1A PROBE

2.Continuous, 4 Second Updates

Tank #: 1

Tank Description:

Product:

DIAGNOSTIC LEVEL 1

STATUS: INFO:

PRODUCT LEVELS

0D0

Rough:

77.5206 IN

0P0

Fine:

77.5209 IN

WATER LEVEL:

3.7194 IN

1W2

0T0

PROBE SENSOR TEMPS

Head:

78.9150 F

Top:

74.4083 F

Middle 3:

74.5590 F

Middle 2:

76.2366 F

Middle 1:

82.4999 F

Bottom:

78.6533 F

PROBE DIAGNOSTIC: WATER MISSING

SITE SENTINEL

FEB 1, 1995

8:36 AM

DIAGNOSTIC PROBE & SENSOR DATA

1.Module & Position: 1A PROBE

2.Continuous, 4 Second Updates

Tank #: 1

Tank Description:

Product:

DIAGNOSTIC LEVEL 1

STATUS: INFO:

PRODUCT LEVELS

15D2

Rough:

77.5206 IN

5P1

Fine:

77.5209 IN

WATER LEVEL:

3.7194 IN

0W0

1T2

PROBE SENSOR TEMPS

Head:

78.9150 F

Top:

74.4083 F

Middle 3:

74.5590 F

Middle 2:

76.2366 F

Middle 1:

82.4999 F

Bottom:

78.6533 F

PROBE DIAGNOSTIC: NO DATA BEING RECEIVED

171

SiteSentinel

H.1.5 Cable/Conduit Problems

The recommended cable to connect the probe to the Smart Module is Belden #88760 or Alpha

#55371. This type of cable is available from Petro Vend.

Note the following cable and conduit installation restrictions:

(1)

Only probe cables and sensor wiring may share the same conduit to the Smart Module

junction boxes and to the Smart Modules.

(2)

Improper cables, wiring, and/or conduit allows electronic "noise" to interfere with the

probe/sensor measurement data. This can cause measurement readings at the Controller that

resemble hardware failure.

(3)

The ground wire must be properly installed for the operation of the noise filtering circuitry.

Do not rely on the conduit for the operation of the ground.

H.1.6 Other Hardware Problems

To isolate a hardware problem, rewire the device (probe or sensor) to a different terminal in the

Smart Module; configure the probe in the usual manner.

If the device responds properly at the new terminal, check the setup, connections and voltages for

the Smart Module and the Controller (see Section H.2).

WARNING!

DO NOT violate the intrinsically-safe area!

172

SiteSentinel

H.2.2 Model II Controller PC Board Overview

Use Figure H1 below (Controller PC board) to assist in troubleshooting the unit. Note the location

of test points and LEDs; they are referenced later in this appendix. Drawings of the Smart Module's

PC board and the I/O Module PC board appear elsewhere in this appendix.

SW3

RESET

U23

U28

GRN RED

DISPLAY

PASS FAIL

CONN

SW1

(BAUD

U25

RATE)

U24

PRINTER

PAL

COMM

CHIP

MODEM

RED

PRINTER

GRN

CONN

PWR

ALARM

CONN

CR24

22 32 41 35

CR31

23 37 39 40

YELLOW

GRN

KEYBD

PHONE JACK CONN

CONN

POWER

PV235

CONN

250 BD CONN

P.N.

CONN

Figure H1 - CONTROLLER BOARD (PV235)

When the red Model II light button or Model III LED is programmed for the duration of an alarm

condition, use option #7 of the SYSTEM COMMANDS MENU to turn it OFF.

174

SiteSentinel

H.2.6 Smart Module Device Diagnostics

To check the devices attached to a Smart Module, use the Module Device Level Summary screen.

Access this screen as follows:

1. From the Main menu, press [7] to display the Module Data menu.

2. From Module Data menu, press [1] to display the Tank, Probe, & Sensor Data menu.

3. Press [5] from the Tank, Probe, & Sensor Data menu.

These measurements include a position letter for each device attached to the Smart Module, the

current level being generated by the device, and the net quantity being measured by the device (if

programmed to display this attribute).

H.2.7 Smart Modules & Positions

An absence of all data usually indicates a hardware problem, though it can also indicate a module

position for a device that was not installed.

To check the installation status of a Smart Module or module position, use the Install/Remove

Modules & Positions menu, accessed as follows:

1. From the Main menu, press [6] to display the System Setup menu.

2. From the System Setup menu, press [2] to display the Sensor, Probe, and Tank Setup menu.

3. Press [5] to display the Install/Remove Modules & Positions menu.

H.2.8 Power Supply Checklist

G Check the power switch inside both the Smart Module and the Controller's cabinets

G Check that the power supply for both units has the proper voltage transformer installed (either 120

or 240V).

G The ground wire must be properly installed for noise filtering circuitry to operate properly. Do

not rely on metal conduit to act as a ground.

G The Controller must have a dedicated power circuit.

For PC board and sensor voltage ratings, see Section H.3, Test Voltages.

178

Appendices

H.3 Test Voltages

The following tables give test voltages for the Model II controller's PV235 board, the Smart Module's

PV242 board, the Smart Module's probe/sensor terminal strip, sensor voltages, and the I/O module's

PC board.

H.3.1 Model II Controller

PV235 Voltages

Use the following table, and the illustration in Section H.2.2, to check voltages on the Controller PC

board.

CONTROLLER PV235 BOARD VOLTAGES

MEASURE: Transformer Terminals on PV235 Board

PRINTER

ORANGE to ORANGE

18.6 VAC

LOGIC

RED to RED

18.6 VAC

PETRO-NET

BROWN to BROWN

8 VAC

The Model II controller xformer has two orange wires, two red wires, and two brown wires.

179

SiteSentinel

H.3.2 Smart Module

PV242 Voltages

Use the following table, and the illustration in Section H.2.4, to check voltages on the Smart Module

PC board.

SMART MODULE PV242 PC BOARD VOLTAGES

MEASURE: Transformer Terminals on PV242 Board

RED to RED

8 VAC

BROWN to BROWN

8 VAC

YELLOW to YELLOW

16 VAC

The Smart Module transformer has two red wires, two brown wires, and two yellow wires.

H.3.3 Smart Module Probe/Sensor Terminal Voltages

Use the following table, and the illustration in Section H.2.3, to check voltages on the device

connection terminal strip. Proper sensor voltages are given in the next section, H.3.4.

The wire colors in the following table are the colors of the wires coming directly off the probe.

SMART MODULE PROBE BARRIER VOLTAGES

MEASURE: Device Terminal in Smart Module

PROBE CONNECTED

WHITE to GREEN

10.8 VDC

BLACK to GREEN

O VDC

NO PROBE CONNECTED

POWER to GROUND

12 VDC

SIGNAL to GROUND

2.4 VDC

180

Appendices

H.3.4 Sensor Voltages

Use the following table to see if the sensors attached to the Smart Module's terminal strip are

functional.

SENSOR TYPE

WIRE COLOR

VOLTAGE

(VDC)

Liquid Phase

Hydrocarbon

Red-Black

6.7

Water

Red-White

6.5

Interstitial

Hydrocarbon

Red-Black

6.4

Water

Red-White

6.9

Sump

Red-Black

Not Activated

Activated

6.9

Reservoir

Red-Black

Activated HIGH

7.6

Activated LOW

7.6

Not Activated

MSA Liquid

White-Black

9.5

Red-Black

2.2

MSA Vapor

White-Black

6.7

Red-Black

4.8

The wire colors in the following table are the colors of the wires coming directly off the sensor.

H.3.5 I/O Module Voltages

Use the table below, and the illustration in Section H.2.4, to check that I/O module voltages are OK.

Place the voltmeter probe on the LEFT side of the indicated diodes.

I/O MODULE VOLTAGES

MEASURE: Left side of component on board

F2 to D4

8 VAC

F3 to D8

8 VAC

F4 to D12

12 VAC

. The voltage across pins #20 (ground) and #40 of the microprocessor should be 5 VDC.

. With the power off, you can check the fuses located at F2, F3, and F4.

181

SiteSentinel

H.4 LED Indicators

This section explains the function of the LEDs on the two different controller boards and the Smart

Module board. The SiteSentinel is assumed to be in normal operating mode.

H.4.1 Controller LEDs

The following table explains what the various states of the LEDs on the PV235 board. For LED

location, see Section H.2.2.

MODEL II Controller - PV235 Board LEDs

Label

Color

Status

Purpose

Label

Color

Status

Function

CR22

Red

flashing

Petro-Net Transmit

CR36

Red

off

not used

CR23

Green

flashing

Petro-Net Receive

CR37

Green

off

Modem Receive

CR24

Green

flashing

DIR Direction Comm

CR38

Green

off

not used

CR26

Yellow

off

68000 Microprocessor Status

CR39

Green

off

Passthrough Port Receive

CR31

Yellow

off

Reset

CR40

Green

off

Terminal Receive

CR32

Red

off

Modem Transmit

CR41

Red

off

Passthrough Port

Transmit

CR35

Red

off

Terminal Transmit

MODEL III Controller - PV271 Board LEDs

Label

Color

Function

CR31

Yellow

Reset

CR23

Red

RS-485 Petro-Net Transmit

CR22

Green

RS-485 Petro-Net Receive

CR24

Yellow

RS-485 Petro-Net TX Enable

CR81

Red

RS-232 Terminal Transmit

CR86

Green

RS-232 Terminal Receive

CR36

Red

RS-232 AUX 3 Transmit

CR38

Green

RS-232 AUX 3 Receive

CR32

Red

RS-232 Printer Transmit

CR37

Green

RS-232 Printer Receive

CR80

Red

RS-232 Modem Transmit

CR85

Green

RS-232 Modem Receive

CR35

Red

RS-232 AUX 1 Transmit

CR40

Green

RS-232 AUX 1 Receive

CR41

Red

RS-232 AUX 2 Transmit

CR39

Green

RS-232 AUX 2 Receive

182

Appendix I - Model II Printer Paper Replacement

Figure I-1 - PRINTER PAPER REPLACEMENT

The printer for the SiteSentinel II requires a 4.5" x 3" roll of plain paper. The paper at the end of

the roll is pink. The paper out switch (next to the roll) is how the system knows when the paper is

gone.

Before replacing the paper roll, note the way in which the paper feeds into the printer (see Figure

above). Then, do the following:

1. Cut the paper on the old roll just before it feeds into the printer. Pull the remaining paper through

the printer, away from the roll.

2. Remove the remaining roll but do not throw away the paper roller.

3. Place the new paper roll on the old roller and set into position. The "paper out" switch activator

may need to be moved. If so, push the activator (its a small piece of metal near the roller holder)

down and to the right.

4. Keeping the paper tight on the roll, carefully slide the leading edge into the printer slot. The paper

should feed in about an inch before stopping.

5. Press and hold the paper advance button (located just to the left of the paper holder) to advance

185

SiteSentinel

the paper. It may be necessary to continue feeding the paper manually for the first few inches.

Note that the paper must be positioned between the ribbon and the metal plate. The printer head does

not come in direct contact with the paper.

Test the printer as follows:

a. Press both the paper advance and system reset buttons simultaneously.

b. Release the reset button while continuing to hold the paper advance button.

After about five seconds, the printer should begin printing. Release the paper advance button after

printing begins.

For more printer troubleshooting information, refer to Appendix H.

186

SiteSentinel

Model III Cable Assembly Instructions (Illustration on previous page)

1. Strip 3/8 of an inch of insulation jacket from one end of the cable, exposing the wires. Be careful

not to nick the wires inside. Remove all strings and plastic covering from the inner wires.

2. Strip 1/8 inch of insulation from each end of each wire. Crimp a terminal on each wire.

3. Fold the stranded ground wire over the cable jacket.

4. Align all pins and insert them into the shield housing so that no bare conductor is visible beyond

the housing. MAKE SURE ALL PINS "SEAT" THEMSELVES FULLY.

5. Slide ferrule over ground wire and shield housing until the ferrule stops.

6. Slide the cord guard over the housing.

188

Appendix K - Computer Access

K.1 Overview

This section describes how you can create programs that automatically execute SiteSentinel

commands.

The information in this appendix applies only to a system connected to an IBM®-compatible PC, or

other system capable of ASCII transmissions.

Note that menus and commands are subject to change in future software versions.

Report data from SiteSentinel can be downloaded to an external computer. System setup information

can also be transmitted to an external computer for safe storage, and then restored to the same (or

similar) system.

The SiteSentinel can use one of five protocols when transferring data. Each protocol is described in

Section K.2, beginning on the following page.

The Data Formats section of this appendix explains how numbers, logical values, times and dates are

represented in the computer format.

The remaining sections indicate the various computer report formats.

RELATED MATERIAL

The following topics can be found on the indicated pages.

G Setting up the computer protocol - input flow control, type of protocol, and file name. Page 55.

G Generating a report in the computer format. Page 151.

G Backup and restore features. Page 107.

G Modem operation. Page 143.

G PC connections and terminal emulation. Page 149.

G Computer report protocols and data formats. Page 151.

189

SiteSentinel

K.2 Computer Report Protocols

The SiteSentinel can use any of five protocols when transferring data. The proprietary Petro Vend

("PV") protocol is described below; this protocol is used by other Petro Vend products.

Xmodem and two versions of Kermit (7-bit, even parity; and 8-bit, no parity) are also available; at

least one of these protocols can be used with most terminal emulation software packages. The 8-bit

version of Kermit interfaces with some communication programs that incorrectly switch to 8-bit/NO

PARITY for file transfer.

The choice of a protocol is usually a tradeoff between reliability and availability. (in other words,

chose the most reliable protocol available). Kermit and Xmodem are the most reliable, followed by

the PV protocol. If none are available, data can be transferred as straight ASCII files.

K.2.1 PV PROTOCOL

Petro Vend protocol is line oriented; each line is sent with `/[CHK][CHK][CR][LF]' appended at the end

(where `[CHK][CHK]' indicates the "checksum," `[CR]' indicates "carriage return," and `[LF]' indicates "line

feed."

The checksum is a two-digit number calculated by adding the decimal values of the ASCII characters in a data

string, adding 47, and truncating the sum. Table 1 on Page lists the decimal values of standard ASCII

characters.

For example, in the data string `ABCD', the decimal values for each character are: A = 65, B = 66, C = 67,

and D = 68. Their sum is 266. 266 + 47 = 313.

Truncating the sum means removing all but the last two digits. In this case, the truncated sum is 13.

The complete data line that would be sent by SiteSentinel (when using PV protocol) is therefore:

`ABCD/13[CR][LF]'.The following is an IBM® BASIC program that determines the checksum for a line of

data:

010 CHKSUM% = 0

020 TRANSACTION$ = "LINE OF DATA 0123456789"

030 NUMCHARS% = LEN(TRANSACTION$)

040 FOR INDEX% = 1 TO NUMCHARS%

050 SINGLECHAR$ = MID$(TRANSACTION$,INDEX%,1)

060 CHKSUM% = CHKSUM% + ASC(SINGLECHAR$)

070 NEXT INDEX%

080 CHKSUM% = CHKSUM% + 47

090 TEMP$ = STR$(CHKSUM%)

100 TEMP$ = RIGHT$(TEMP$,2)

110 PRINT TEMP$

120 END

K.2.2 KERMIT PROTOCOL

The Kermit protocol was developed to transfer files between a large variety of mainframe, mini, and

micro-computers.

Since its introduction, Kermit has been extended to (1) implement common system commands in a

portable way, (2) improve reliability, and (3) speed up file transfers.

It is not necessary to put the SiteSentinel into SERVER mode to receive Kermit server mode

commands. The SiteSentinel automatically recognizes Kermit server mode commands, selects the

Kermit protocol, and places itself into server mode for the duration of the command. After the server

command has been processed, the SiteSentinel returns to the mode it was in before the command.

190

Appendices

The commands beginning on the next page are presented as if they were typed at the Kermit

command line on a PC using MS-DOS Kermit version 3.11.

The PC program sends the command and data packets to the SiteSentinel following the Kermit

protocol. It is these command and data packets that are recognized by the SiteSentinel.

SEND file name

This command sends either a <command file> or backup file to the SiteSentinel.

RECEIVE

This command lets your PC receive reports from the SiteSentinel. Reports can be requested either

from the command line, or from the Computer Format Reports menu. Also use RECEIVE to receive

backup data.

REMOTE HOST command line

The PC sends a single <command line> to the SiteSentinel and waits for an acknowledgement, report,

or error. If it receives a report, it normally is displayed on the computer's screen using the computer

format.

REMOTE TYPE file name

This is equivalent to GET <file name>, except the report is displayed on-screen and not stored in a file.

GET file name

This command requests a report from the SiteSentinel, and then to receive the requested report. The

SiteSentinel scans this file name for an embedded report name. The SiteSentinel then sends the report

with the same <file name> that was requested.

Report names are scanned for starting with the longest report name ("INVP" is scanned before

"INV"). Be careful not to use file names that may contain more than one report name of the same

length, such as "QINVP.1" (QINV or INVP) or "INV.BCK" (INV or BCK).

The entire <file name> sent to the SiteSentinel is scanned, including the disk, directory, and extension.

This command enters the privileged mode. The <user name> is ignored. The <password> is

compared with either the restricted or privileged passwords and the privilege level is set accordingly.

191

SiteSentinel

BYE

LOGOUT

These two commands disconnect the SiteSentinel and hang up the modem.

FINISH

This command is accepted but not needed.

The SiteSentinel supports the following:

9 8-bit prefixing (8-bit characters are not currently used)

9 Run-length encoding

9 The use of one-, two-, or three-character block-checks.

These features are negotiated between the two protocol drivers at the start of each session.

If there is an error while Kermit protocol is used, an error packet is sent containing error numbers and

an error message for the user.

Kermit server commands are accepted at the following prompts:

9 `enter terminal type:' prompt

9 Any `enter menu selection:' prompt

9 The command line prompt.

When using Kermist server commands, you can protect the entire session from being corrupted by

line noise by using the protocol. This includes all commands and data from when the immediately

after connection with the SiteSentinel up until the moment of disconnection.

FILE NAMES & Kermit

File names are used with the Kermit protocol. References to file names should be ignored when using

Xmodem, Petro Vend, or ASCII protocols.

When the SiteSentinel sends a report or receives a <command file>, it is sent with a file name.

For reports requested from a menu, the command line, or within a command file, the SiteSentinel uses

the default file name from the computer protocol setup menu. This can also be accessed with

PROTO.

Reports requested with the Kermit REMOTE HOST command are not accompanied by a file name,

and display on the screen.

192

Appendices

For reports requested with the Kermit GET <file name> command, the <file name> is the same as

was used in the GET command.

The maximum length of the <file name> is 80 characters.

See the section on the Kermit GET command for how the <file name> is interpreted.

On <command files>, the file name is ignored. The content of the file determines if it is a backup file

(along with the type of backup) or a regular command file.

A <file name> can be made up of any 7-bit ASCII characters, except CR and LF. If entered at a

menu, only characters that appear on the keypad can be used.

Most operating systems require a certain format for the file name.

K.2.3 XMODEM PROTOCOL

Xmodem was created in the late

1970s to provide reliable file transfers between CP/M

microcomputers over communication lines. It is included with many communication programs and

function libraries.

Since its introduction, the protocol has been extended in order to improve the reliability and speed

of file transfers.

The only extension supported by the SiteSentinel is XMODEM-CRC where the eight bit checksum

has been replaced by a CRC.

K.2.4 ASCII PROTOCOL

The ASCII protocol is intended for use only if another protocol is unavailable. A table of ASCII

values is on Page 153.

When selected, SiteSentinel sends reports to the computer as “straight” ASCII text. The computer

controls the flow using either hardware handshaking ('RTS') or software handshaking (`XON' and

`XOFF').

With a RESTORE, the SiteSentinel displays a message requesting the file using ASCII and then waits

up to one minute for the computer to start sending data.

Once the computer is sending data, either hardware handshaking (`CTS'), or software handshaking

(`XON' and `XOFF') must be used to prevent SiteSentinel from losing data.

A pause of at least 10 seconds or a control Z in the data indicates to the SiteSentinel that the

computer has reached the end of the file. If software handshaking (`XON' and `XOFF') is used, it must

be enabled.

193

SiteSentinel

For reports, the receiving computer should look for one of the following:

9 A command line prompt (`[CR][LF]>') when the command line mode is used

9 An error message

9 An `ESC' (0x1b) which indicates the SiteSentinel is redrawing the menu screen.

K.3 Command Line Format

K.3.1 INTRODUCTION

There is both a menu interface and a command line interface for the SiteSentinel. Use the command

line interface for all computer control.

Menu interfaces may change from one software version to the next, changing the keystrokes

necessary to execute a command or request a report.

You can request a format report or send a command or information to the SiteSentinel in several

ways:

O Go to the computer format reports menu and request a report;

O Enter command line mode and type a <command line>;

O On the host computer, use a Kermit REMOTE HOST <command line> command;

O On the host computer, use a Kermit SEND <file name> to send a <command file> containing

one or more <command line>'s requesting the report or reports.

O On the host computer, use a Kermit GET <file name> command;

O Go to the backup/restore menu and request a system backup;

O Go to the backup/restore menu and "restore" a command file;

The `RESTORE' command is described on Page 107 as accepting a file produced by the `BACKUP'

command. The backup file is really a <command file> containing a single <command line> followed

by the data that was backed up.

194

Appendices

K.3.2 COMMAND FILES

A command file is a text file stored on another computer containing SiteSentinel line mode

commands. When this file is sent to the SiteSentinel using one of the file transfer protocols, the

SiteSentinel interprets the commands contained in the file. This is done while the file is being sent.

<command file>:

<command line>[<CR><command file>]

<command line>:

'REM '{any text}

'SET '[<range>]<variable>[<range>]'='<value>

'SETV '[<range>]<variable>[<range>]'='<value>

'SHOW '[<range>]<variable>[<range>]

<report name> [<range>]

<command name> [<range>]

Variables require a <range> sufficient to specify the particular variable. If the <range> is more than

sufficient, the additional information is ignored; that is, if a <variable> is associated with a <module>,

and a <modpos> or <group> is given, the module portion is used.

Also, if an <index> is specified for a <variable> and is not needed, it is ignored. If a <range> is

specified, only the first location in the <range> is used.

A <command name>, <report name>, or <variable> is a short name, or anagram representing a

command, report, or variable. It can not be abbreviated and case is ignored.

195

SiteSentinel

K.3.3 RANGE SPECIFICATION

Many

included in a report.

<range>:

' '<range specifier>[<range>]

<range specifier>:

The <modpos range>, <index range>, and <event group> specifiers can be combined in any order.

<modpos range>:

'P'<mod><pos>['-'<mod><pos>]

'M'<mod>['-'<mod>]

'G'<mod><grp>['-'<mod><grp>]

The <modpos range> specifiers ('P', 'M', and 'G') are mutually exclusive and cannot be combined with one

another. If multiple <modpos range> specifiers are used in a single <range>, only the last <modpos range>

specifier is used.

<mod>:

'1'-'8'

<pos>:

'A'-'P'

<grp>:

'1'-'8'

<index range>:

'I'<index>['-'<index>]

<event group>:

<event>

'SPIF'

(all spi and hfe events)

'SPI'

(all spi events)

'HFE'

(all hfe events)

<event>:

‘SIN’ is Saved Inventory Report

<spi events>:

'HPL' | 'LPL' | 'HWL' | 'TMP' | 'TFT' |

'DEL' | 'SAL' | 'TLT' | 'HSL' | 'LSL' |

'I01' | 'I02'

<hfe events>:

'PRB' | 'MOD' | 'PRN' | 'POW'

<event> and <event group> specifiers are mutually exclusive and can not be combined with one another.

196

Appendices

K.3.4 COMMAND TYPES

Comm

Reports

A report is data generated by the SiteSentinel. When requested, the SiteSentinel generates the report based

on the data in memory while the report is being sent to the user. You can request reports in several ways,

as shown below (further explained in Chapter 6):

Report Name

Description

INVP

Tank inventory

INVS

Sensor levels

INV

Combined tank

inventory & sensor

levels

QINV

Quick inventory report

WARN

Warnings in progress

EVENT

Combined events

BCK

System configuration

backup

Setting or Showing Configuration Data (variables)

Variables store setup data, and can be modified either from the menus or from the command line using a

SET or SETV command. Examine them either from the menus or from the command line with the with the

SHOW command.

The data format required depends on the specific variable. Typically the same format printed in computer

format could be entered. If a value is outside of the allowable range, an error is sent.

The SHOW command produces a computer format report containing the data in the variable. Each instance

of a variable produces a separate line. Currently only one instance of a variable can be shown in a report,

producing a single line report.

Miscellaneous

This category is a catch-all for commands that are not reports and do not show or modify configuration data.

197

SiteSentinel

K.4 Report Data Formats

K.4.1 INTRODUCTION

Reports consist of one or more lines. Each line consists of a <line title> followed by one or more

data fields.

In general, by looking at the <line title>, the software parses the rest of the line assuming fixed field

widths and data types. The fields are separated by slashes ('/').

K.4.2 FORMAT DESCRIPTION

Computer format reports generated by the SiteSentinel are generally sent as a separate file using one

of the file transfer protocols (PV, Xmodem, Kermit, or ASCII). Each report starts with a report

header line followed by zero or more data lines. The end of the file defines the end of the report.

The reports are described with the following syntax:

On the first line of the syntax description block is the syntax type followed by one or two colons (":"

or "::").

One colon indicates that any of the following lines may be included, two colons indicate that all of

the following lines in the block are included in the indicated order.

Then, a set of indented lines indicating text or further syntax types. Each of these indented lines

represents text included in the report. The syntax "<<type> line>" represents a data line with a line

title of <type>.

Sections within braces ("{", "}") may be repeated one or more times.INV, INVP, and INVS reports

These reports are subsets of the INV report, limited to module positions that are programmed as

either probes (INVP) or sensors (INVS).

The INV report is limited to modules and positions that are installed (variables MOD 1= INST, and

POS 1=INST), and <modpos>'s that fall within range (as specified on the command line or in the RPT

variable).

If a group range was specified, only the group measurements within the <range> are included in the

report; individual inventory measurements are not included.

QINV report

The QINV report is designed for a quick turnaround where the computer is continuously polling the

SiteSentinel in order to update a graphics screen.

198

SiteSentinel

Sample EVENT Report

<INV report>::

(report header line)

{

(repeated for each module)

{

(repeated for each position)

(individual)

}

{

(repeated for each group)

(group)

}

<QINV report>::

(Quick inventory report)

{

(repeated for each module)

{

(repeated for each position or group)

}

<measurement>:

<position measurement>:

<quick measurement>:

(for sensor postions)

(for probe positons or groups)

<probe measurement>::

<sensor measurement>::

<group measurement>::

<WARN report>::

(report header line)

{

(repeated for each module)

{

(repeated for each position)

{

(repeated for each event type)

}

<EVENT report>:

(report header line)

{

(repeated for each event)

(event data header line)

(only if there is additional data)

}

<EVENT data>:

(HPL, LPL, HWL, HSL, LSL)

(TFT, DEL, SAL)

(INV)

(TLT)

(TMP, I01, I02,

PRB, MOD, PRN, POW)

200

SiteSentinel

REPORT LINE FORMATS (Not all apply to both Model II and III)

GENERAL LINE FORMAT FOR REPORTS

ttt/<field 1>/<field 2>/.../<field n-1>/<field n>

ttt

Report or Line Title: always 3 characters exactly

Data Field Separator: "forward slash" character

Data Field: the quantity and type of fields included depend on the particular

line type; note that fields of the same type are always the same size, but

different field types may have different sizes

REPORT HEADER LINE

ttt/mmddyyyy/hhmmss

ttt

Line Title: always 3 characters exactly

INV - Tank Inventory Report or Sensor Levels Report

WRN - Warnings in Progress Report

ALR - Saved Event Report (sensor, probe, input, hardware failures, &

individual)

mmddyyyy/hhmmss

Date & Time of Report: month, day, year / hours, minutes, seconds

MEASUREMENT HEADER LINE

M01/u/tnk/m/ps/sen/ffffffff/mmddyyyy/hhmmss

M01

Line Title

Units of Measurement: F = English; T = Metric

tnk/m/ps/sen

Device Identification: tank number (0 to 999) / smart module (1 to 8) /

module position (1 to 16) / device type

ffffffff

Flags: not defined

mmddyyyy/hhmmss

Date & Time of Measurement: month, day, year / hours, minutes, seconds

MEASUREMENT LINE #1 (individual tanks)

M02/dddddd.ddd/dddddd.ddd/dddddd.ddd/dddddd.ddd/dddddd.ddd/dddddd.ddd

M02

Line Title

dddddd.ddd

Net Corrected Tank Volume

dddddd.ddd

Gross Measured Tank Volume

dddddd.ddd

Volume Left in Tank (ullage)

dddddd.ddd

Product Level

dddddd.ddd

Average Product Temperature (average of temperature sensors which are

currently submersed in product)

dddddd.ddd

Water Level

RESERVED

M03

Line Title

202

Appendices

MEASUREMENT DATA LINE #1 (manifolded tanks)

M04/dddddd.ddd/dddddd.ddd/dddddd.ddd/----------/dddddd.ddd/----

------

M04

Line Title

dddddd.ddd

Net Corrected Tank Volume

dddddd.ddd

Gross Measured Tank Volume

dddddd.ddd

Volume Left in Tank (ullage)

----------

Blank: product level does not exist

dddddd.ddd

Average Product Temperature (average of temperature sensors which are currently

submersed in product)

----------

Blank: water level does not exist

MEASUREMENT LINE #2

M05/dddddd.ddd/dddddd.ddd

M05

Line Title

dddddd.ddd

Net Corrected Product Volume

dddddd.ddd

Gross Water Volume

MEASUREMENT DATA LINE #2

M06/dddddd.ddd/dddddd.ddd

M06

Line Title

dddddd.ddd

Net Corrected Product Volume

dddddd.ddd

Gross Water Volume

QUICK INVENTORY REPORT LINE (sensors)

M07/u/tnk/m/ps/sen/mmddyyyy/hhmmss/dddddd.ddd/dddddd.ddd

M07

Line Title

Units of Measurement: F = English; T = Metric

tnk/m/ps/sen

Device Identification: tank number (0 to 999) / smart module (1 to 8) / module

position (1 to 16) / device type

mmddyyyy/hhmmss

Date & Time of Measurement: month, day, year / hours, minutes, seconds

dddddd.ddd

Measured Sensor Voltage; floating point number

dddddd.ddd

Reserved for additional measurement

203

SiteSentinel Automated Monitoring System Model 2 and Model 3. Operator Manual Software Version 1.12CUS - part 3