FieldServer FS-8700-74 Release note

ASierraMonitorCompany
APPLICABILITY & EFFECTIVITY
Effective for all systems manufactured after May 1, 2001
Driver Manual
(Supplement to the FieldServer Instruction Manual)
FS-8700-74 Veeder-Root
Driver Version: 1.01
Document Revision: 3

FS-8700-74 Veeder Root Driver Manual Table of Contents
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [email protected]
TABLE OF CONTENTS
1. Veeder-Root Driver Description..........................................................................................3
2. Driver Scope of Supply........................................................................................................4
2.1. Supplied by FieldServer Technologies for this driver ...................................................4
2.2. Provided by the Supplier of 3
rd
Party Equipment..........................................................4
2.2.1. Required 3
rd
Party Hardware.....................................................................................4
3. Hardware Connections ........................................................................................................5
4. Configuring the FieldServer as a Veeder-Root Client.......................................................6
4.1. Data Arrays...................................................................................................................6
4.2. Client Side Connections ...............................................................................................7
4.3. Client Side Nodes.........................................................................................................8
4.4. Client Side Map Descriptors.........................................................................................8
4.4.1. FieldServer Specific Map Descriptor Parameters .....................................................8
4.4.2. Driver Specific Map Descriptor Parameters..............................................................9
4.4.3. Timing Parameters....................................................................................................9
4.4.4. Map Descriptor Example 1 - Alarms........................................................................10
4.4.5. Map Descriptor Example 2 - Inventory....................................................................11
4.4.6. Map Descriptor Example 3 – Most Recent Delivery Report....................................12
5. Configuring the FieldServer as a (Veeder-Root Driver) Server......................................13
Appendix A. Advanced Topics............................................................................................14
Appendix A.1. Data Type and Required Lengths .................................................................14
Appendix A.2. Supported Functions.....................................................................................15
Appendix A.3. Alarm Types..................................................................................................16
Appendix A.4. Security Codes..............................................................................................20
Appendix B. Trouble Shooting and Driver Error Messages .............................................21
Appendix B.1. Driver Stats....................................................................................................24
Appendix B.2. Table of Module Types..................................................................................25
Appendix C. Advanced Map Descriptor Examples............................................................26
Appendix C.1. Advanced Example 1 – Polling for Tank / Sensor / Input / Relay / Device
Status 26
Appendix C.2. Advanced Example 2 – Resetting Remote Alarms .......................................27
Appendix C.3. Advanced Example 3 – System Configuration..............................................27
Appendix C.4. Advanced Example 4 – System Diagnostics.................................................28
Appendix C.5. Advanced Example 5 – System Revision Level Report................................29
Appendix C.6. Advanced Example 6 – System Revision Level Report II.............................30
Appendix C.7. Advanced Example 7 – Stick Height Report ................................................31
Appendix C.8. Advanced Example 8 – Active Alarm Report................................................31
Appendix C.9. Advanced Example 9 – Cleared Alarm Report .............................................32

FS-8700-74 Veeder Root Driver Manual Page 3 of 33
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [email protected]
1. Veeder-Root Driver Description
The Veeder-Root Serial Driver allows the FieldServer to transfer data to and from devices over
either RS-232 or RS-485 ports using Veeder-Root protocol as defined in Veeder Root
Document 576013-635 Revision J.
The FieldServer emulates a Client.
The Veeder-Root Serial Driver is a poll response driver. Only one query or command can be
processed at a time.
A limited set of the queries and commands defined in the protocol specification have been
implemented. The reason for the limitation is two-fold. Firstly, not all commands/queries will
have any meaning to a downstream device as they are principally defined to configure the
Veeder-Root Device. Secondly some commands return very complex data sets which cannot
be processed in a method suitable for loading into the FieldServer’s Data Arrays.
The driver is capable of exposing its communications statistics. This can be useful if you wish
to monitor them using a downstream device. In this way you can ensure that you are using
valid data and can generate alarms if communication problems arise.

FS-8700-74 Veeder Root Driver Manual Page 4 of 33
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [email protected]
2. Driver Scope of Supply
2.1. Supplied by FieldServer Technologies for this driver
FieldServer Technologies
PART # Description
FS-8915-10 UTP cable (7 foot) for RS-232 use
FS-8917-01 RJ45 to DB25M connection adapter
FS-8700-74 Driver Manual.
2.2. Provided by the Supplier of 3
rd
Party Equipment
2.2.1. Required 3
rd
Party Hardware
PART # DESCRIPTION
Veeder-Root Panel

FS-8700-74 Veeder Root Driver Manual Page 5 of 33
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [email protected]
3. Hardware Connections
The FieldServer is connected to the Veeder-Root Panel as shown below.
Configure the Veeder-Root Panel according to manufacturer’s instructions.
DATE: 1/17/02
BY: MN
(408)-262-2299
BASE NAME:
FILE NAME: FS-T28700-74 .VSD
VEEDER ROOT
CONNECTION DIAGRAM
P4P1
Rx
P2 P3
Tx Rx Tx TxRx Rx P7P5 P6 Tx Rx Tx TxRx Rx P8 R1 Tx Rx Tx Rx Tx
R2 Ne t 1
TxRx RxTx Con
Net 2
Sys
Com
Tx Rx Con
Act Run Pwr
RS485
RS232 10 Base T
ETHERNET
P1 P7 R1P2 R2
P3 P4 P5 P6 P8 N1 N2
8917-07
FieldServer
FIELDSERVER
FUNCTION FROM TO COLOR
RX RJ45-01 DB25M-02 WHITE
CTS RJ45-02 DB25M-05 BROWN
DSR RJ45-03 DB25M-08 YELLOW
GND RJ45-04 DB25M-07 GREEN
DTR RJ45-06 DB25M-20 BLACK
RTS RJ45-07 DB25M-06 ORANGE
TX RJ45-08 DB25M-03 BLUE
TLS-350
8917-07 WIRE LIST
RJ45 CAT 5 Cable
Connect to
RS232 port P1-P8

FS-8700-74 Veeder Root Driver Manual Page 6 of 33
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [email protected]
4. Configuring the FieldServer as a Veeder-Root Client
For a detailed discussion on FieldServer configuration, please refer to the FieldServer
Configuration manual. The information that follows describes how to expand upon the factory
defaults provided in the configuration files included with the FieldServer.
This section documents and describes the parameters necessary for configuring the FieldServer
to communicate with a Veeder-Root Device.
The configuration file tells the FieldServer about its interfaces, and the routing of data required.
In order to enable the FieldServer for Veeder-Root Driver communications, the driver
independent FieldServer buffers need to be declared in the “Data Arrays” section, the
destination device addresses need to be declared in the “Client Side Nodes” section, and the
data required from the Servers needs to be mapped in the “Client Side Map Descriptors”
section. Details on how to do this can be found below.
Note that in the tables, * indicates an optional parameter, with the bold legal value being the
default.
4.1. Data Arrays
Section Title
Data_Arrays
Column Title Function Legal Values
Data_Array_Name Provide name for Data Array Up to 15 alphanumeric
characters
Data_Format Provide data format. Each Data
Array can only take on one format.
FLOAT, BIT, UInt16, SInt16,
Packed_Bit, Byte,
Packed_Byte, Swapped_Byte
Data_Array_Length
Number of Data Objects. Must be
larger than the data storage area
required for the data being placed in
this array.
1-10,000
Example
// Data Arrays
//
Data_Arrays
Data_Array_Name, Data_Format, Data_Array_Length
DA_AI_01, UInt16, 200
DA_AO_01, UInt16, 200
DA_DI_01, Bit, 200
DA_DO_01, Bit, 200

FS-8700-74 Veeder Root Driver Manual Page 7 of 33
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [email protected]
4.2. Client Side Connections
Section Title
Connections
Column Title Function Legal Values
Port Specify which port the device is
connected to the FieldServer P1-P8, R1-R2
1
Baud* Specify baud rate 300 – 9600, standard baud rates
only – Vendor limitation.
Parity* Specify parity Even, Odd, None
Data_Bits* Specify data bits 7, 8
Stop_Bits* Specify stop bits 1, 2
Protocol Specify protocol used Vroot, Veeder
Handshaking* Specify hardware handshaking None
Poll Delay* Time between internal polls 0-32000 seconds, 1 second
Example
// Client Side Connections
Connections
Port, Baud, Parity, Protocol, Handshaking, Poll_Delay
P1, 9600, None, Vroot, None, 0.100s
1
Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction
manual for details of the ports available on specific hardware.

FS-8700-74 Veeder Root Driver Manual Page 8 of 33
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [email protected]
4.3. Client Side Nodes
Section
Title
Nodes
Column
Title Function Legal Values
Node_Name Provide name for node Up to 32 alphanumeric
characters
Node_ID This commonly used parameter is not required for this driver.
Protocol Specify protocol used Vroot, Veeder
Port
Specify which port the device is connected
to the FieldServer
Only one node per port.
P1-P8, R1-R2
2
*Route
This parameter is only required if security
is enabled on the Veeder-Root device.
In this case the route must be set to
contain the 6 digits that form the security
code.
Example. If the security code is 556741
then enter route as
5.5.6.7.4.1
a.b.c.d.e.f
a,b,c,d,e,f must be decimal
digits in the range 0 to 9.
Example
// Client Side Nodes
Nodes
Node_Name, Protocol, Port
VR_Node1 , Vroot , P1
4.4. Client Side Map Descriptors
4.4.1. FieldServer Specific Map Descriptor Parameters
Column Title Function Legal Values
Map_Descriptor_Name Name of this Map Descriptor Up to 32 alphanumeric
characters
Data_Array_Name Name of Data Array where data is to be stored in the
FieldServer
One of the Data Array names
from “Data Array” section
above
Data_Array_Location Starting location in Data Array 0 to maximum specified in
“Data Array” section above
Function Function of Client Map
Descriptor RDBC, WRBC, WRBX
2
Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction
manual for details of the ports available on specific hardware.

FS-8700-74 Veeder Root Driver Manual Page 9 of 33
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [email protected]
4.4.2. Driver Specific Map Descriptor Parameters
Column
Title Function Legal Values
Node_Name Name of Node to fetch data from One of the node names specified in “Client Node
Descriptor” above
Data_Type Data type
System, Tank, Liquid Sensor,
Vapor Sensor, Input,
Volumetric Line, Groundwater
Sensor, Type-B Sensor,
Universal Sensor, Auto-Dial,
Mech. Dispenser, Elec.
Dispenser, Product, Press.
Line, External, WPLLD
*Address
¥
The address is used to specify the
Tank/Sensor/Input /Relay … Number to
be used in the poll. For some data
types the address has no meaning and
should be set to 1.
Veeder-Root Tanks / Sensors … are
numbered from 1. The maximum tank
number is 12 and the maximum sensor
number if 64.
When zero is used as the value of the
address then (in most cases) the driver
polls for all Tanks/ Sensors belonging
to that data type. This is discussed in
the Advanced Topics Section.
0, 1, 2, 3…
Length
¥
Length of Map Descriptor
The length is used to tell the driver how
many elements of the Data Array are
under the control of the Map Descriptor.
This is important because the driver
uses the length to, for example, clear
Data Array elements when a
Tank/Sensor has no alarms.
1 - 1000
4.4.3. Timing Parameters
Column Title Function Legal Values
Scan_Interval Rate at which data is polled >0.1s
¥
See Appendix A.1 for Data Type, Address and Length Limitations.

FS-8700-74 Veeder Root Driver Manual Page 10 of 33
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [email protected]
4.4.4. Map Descriptor Example 1 - Alarms.
This example provides one Map Descriptor to poll for alarm data and many Map Descriptors to store the response from the poll. One
Map Descriptor is required for each tank/sensor/input/device defined for the system. The address of each of these passive Map
Descriptors must correspond to the tank/sensor/input/device number. For example, where 5 tanks are defined as tanks 1,2,3,6,7
then 5 Map Descriptors with the data type ‘Tank’ are required and the address of each of these 5 Map Descriptors must be set to
1,2,3,6,7. The length parameter tells the driver how much array space is reserved for each tank/sensor… for storing alarms.
Map_Descriptors
Map_Descriptor_Name, scan_interval, Data_Array_Name, Data_Array_Offset, Function, node_name, Address, Length, Data_Type,
Poller 1.0s , DA_101 , 0 , rdbc , Node_A , 1 , 30 , System Status
Map_Descriptors
Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset Function, node_name, Address, Length, Data_Type
Sys_alms01 , DA_S1 , 0 , passive , Node_A , 1 , 30 , System
Tank_Alms1 , DA_T1 , 0 , passive , Node_A , 1 , 30 , Tank
LiqSensor_Alm1, DA_L1 , 0 , passive , Node_A , 1 , 30 , Liquid Sensor
VaporSens_Alm1, DA_V1 , 0 , passive , Node_A , 1 , 30 , Vapor Sensor
Input_Alm1 , DA_I1 , 0 , passive , Node_A , 1 , 30 , Input
VolLine_Alm1 , DA_O1 , 0 , passive , Node_A , 1 , 30 , Volumetric Line
GWater_Alms1 , DA_G1 , 0 , passive , Node_A , 1 , 30 , Groundwater Sensor
TypeB_SensALm1 , DA_B1 , 0 , passive , Node_A , 1 , 30 Type-B Sensor
Univ_SensAlm1 , DA_U1 , 0 , passive , Node_A , 1 , 30 , Universal Sensor
AutoDial_Alms1 , DA_F1 , 0 , passive , Node_A , 1 , 30 , Auto-Dial
MechDisp_Alm1 , DA_M1 , 0 , passive , Node_A , 1 , 30 , Mech. Dispenser
ElecDisp_Alm1 , DA_E1 , 0 , passive , Node_A , 1 , 30 , Elec. Dispenser
Product_Alms1 , DA_P1 , 0 , passive , Node_A , 1 , 30 , Product
PressLine_Alm1 , DA_R1 , 0 , passive , Node_A , 1 , 30 , Press. Line
External_Alm1 , DA_X1 , 0 , passive , Node_A , 1 , 30 , External
WPLLD_Alms1 , DA_W1 , 0 , passive , Node_A , 1 , 30 , WPLLD
Only the Map
Descriptor used to
generate the poll
requires a scan
interval.
These Map
Descriptors are
passive because
they do not
generate
messages. They
are used to store
data returned by
the system status
poll.
The address must
correspond to the
tank/sensor/input/device
number.
One Map Descriptor
required for each
tank/sensor/input/device.
The length parameter tells the driver how much array space must be reserved
for storing alarms for a given tank/sensor/input/device.
When an alarm occurs for tank 1 the driver stores the alarm type by setting
the array position corresponding to the alarm type to a non-zero value as well
as setting the first element of the reserved space non-zero as a summary.
See Table 6.3 for alarm type numbers and descriptions.
Example: Tank 1 has two alarms
02 = Tank Leak Alarm
05 = Tank Low Product Alarm
The driver sets array DA_T1 as follows
Index=0 : Value=1 (Summary)
Index=2 : Value=2 (Leak)
Index=5 : Value=5
(
Product
)

FS-8700-74 Veeder Root Driver Manual Page 11 of 33
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [email protected]
4.4.5. Map Descriptor Example 2 - Inventory
This example illustrates how you can poll for Tank Inventory Data. You need one Map Descriptor for each tank. Change the address
to correspond to the tank number. The Length parameter DOES NOT tell the driver how many tanks to process but it does tell the
driver how much storage space to reserve for storing the inventory data. The inventory data is stored as follows.
Index Contents
0. Product Code (Example Array value = 49 indicates product code = ASCII ‘1’)
1. Tank Status (Bit 1 - (LSB) Delivery in Progress, Bit 2 - Leak Test in Progress, Bit 3 - Invalid Fuel Height Alarm (MAG Probes Only))
2. Volume
3. TC Volume
4. Ullage
5. Height
6. Water
7. Temperature
8. Water Volume
.
Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset Function, Scan_Interval, node_name, Address, Length, Data_Type
InventoryPoll1, DA_INVENTORY , 0 , rdbc , 1.0s , Node_A , 1 , 10 , In-Tank Inventory
Reading the
inventory requires
an active Map
Descriptor.
Set the address equal to the
tank number. One Map
Descriptor per tank.
This is the minimum number of Data
Array elements required to store
inventory data.
Tanks 1’s data will be stored in the
array DA_INVENTORY starting at the
zero’th element (offset=0) and 10
elements of the array are reserved for
this data.
Setting the data type
generates the
correct poll. Ensure
that spelling,
periods, hyphens in
exactly the same as
this example.

FS-8700-74 Veeder Root Driver Manual Page 12 of 33
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [email protected]
4.4.6. Map Descriptor Example 3 – Most Recent Delivery Report
This example illustrates how you can poll for Tank Delivery Data. You need one Map Descriptor for each tank. Change the address
to correspond to the tank number. The Length parameter DOES NOT tell the driver how many tanks to process but it does tell the
driver how much storage space to reserve for storing the delivery data. The delivery data is stored as follows. (This function
corresponds to the function 20C in the Veeder-Root protocol specification.)
Index Contents
0. Product Code
1. Number of Deliveries
2. Start Time
3. Stop Time
4. Starting Volume
5. Starting TC Volume
6. Starting Water
7. Starting Temp
8. Ending Volume
9. Ending TC Volume
10. Ending Water
11. Ending Temp
12. Starting Height
13. Ending Height
.
Map_Descriptor_Name Data_Array_Name Data_Array_Offset Function Scan_Interval node_name Address Length Data_Type
DeliveryPoll01 DA_DELIVERY 0 rdbc 1.0s Node_A 1 30 In-Tank Delivery

FS-8700-74 Veeder Root Driver Manual Page 13 of 33
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [email protected]
5. Configuring the FieldServer as a (Veeder-Root Driver) Server
The server functionality of this driver was developed for testing the Client. Its features are not
documented and not intended for end-users. It may be possible to extend and document the
server at the request of an end-user.

FS-8700-74 Veeder Root Driver Manual Page 14 of 33
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [email protected]
Appendix A.Advanced Topics
Appendix A.1. Data Type and Required Lengths
The following table provides a list of possible values for the data type parameter as well as
the minimum value that the length parameter should be set to for each Map Descriptor of
that data type.
Data Type Length Parameter Setting
Normal 1
System 30
Tank 30
Liquid Sensor 30
Vapor Sensor 30
Input 30
Volumetric Line 30
Groundwater Sensor 30
Type-A Sensor 30
Type-B Sensor 30
Universal Sensor 30
Auto-Dial 30
Mech. Dispenser 30
Elec. Dispenser 30
Product 30
Press. Line 30
WPLLD 30
External 30
Relay 30
Configuration 1
In-Tank Inventory 10
Misc 20
In-Tank Delivery 100
System Reset 20
Clear Power Reset 20
Remote Alarm Reset 20
Confirm Clear 20
Clear Delivery Reports 20
Start In-Tank Leak Detect Test 20
Stop In-Tank Leak Detect Test 20
Delete CSLD Rate Table 20
Start P-Line Leak Detect Test 20
Stop P-Line Leak Detect Test 20
Start WPLLD Leak Detect Test 20
Stop WPLLD Leak Detect Test 20
System Status 1

FS-8700-74 Veeder Root Driver Manual Page 15 of 33
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [email protected]
Appendix A.2. Supported Functions
The Veeder-Root protocol specification defines a large number of enquiries and commands
that may be sent to a Veeder-Root device. This driver supports a limited set of the functions.
The revision number indicates the minimum Veeder-Root firmware revision required for
support of the function.
Function_ Revision_ Description
SYSTEM REPORTS (7.2.1)
101 1System Status Report
102 1System Configuration Report
113 14Active Alarm Report
114 19Cleared Alarm Report
IN-TANK REPORTS (7.2.2)
201 1In-Tank Inventory Report
202 1In-Tank Delivery Report
203 1In-Tank Leak Detect Report
204 1In-Tank Shift Inventory Report
205 1In-Tank Status Report
20C 15In-Tank Most Recent Delivery Report
20D 15In-Tank Stick Height Report
SENSOR REPORTS (7.2.3)
301 1Liquid Sensor Status Report
306 1Vapor Sensor Status Report
311 1Groundwater Sensor Status Report
341 2Type A (2 Wire CL) Sensor Status Report
346 2Type B (3 Wire CL) Sensor Status Report
34B 4Universal Sensor Status Report
LINE LEAK REPORTS (7.2.4)
381 7Pressure Line Leak Status
386 10WPLLD Line Leak Status
I/O DEVICE REPORTS (7.2.6)
401 1Input Status Report
406 1Relay Status Report
SYSTEM DIAGNOSTIC REPORTS (7.4.1)
901 1Self Test Results Report
902 1System Revision Level Report
905 15System Revision Level Report II
CONTROL FUNCTIONS (7.1)
1 1System Reset
2 1Clear Power Reset Flag
3 1Remote Alarm Reset
31 10Confirm Clear Function
51 1Clear In-Tank Delivery Reports
52 1Start In-Tank Leak Detect Test
53 1Stop In-Tank Leak Detect Test
54 5Delete CSLD Rate Table
81 7Start Pressure Line Leak Test (3.0 GPH only in V18)
82 7Stop Pressure Line Leak Test
83 10Start WPLLD Line Leak Test (3.0 GPH only in V18)
84 10Stop WPLLD Line Leak Test

FS-8700-74 Veeder Root Driver Manual Page 16 of 33
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [email protected]
The function numbers in Appendix A.1are hexadecimal numbers. If you specify them in the
CSV file using the Veed_Function parameter then either convert them to decimal or
specify them in the CSV file using the notation 0xnnn where nnn is the function number.
Example:
…..,Veed_Function, ….
….., 0x901 ,….
Appendix A.3. Alarm Types
Category Alarm Type & Description
1 System 1 Printer out of Paper
1 System 2 Printer Error
1 System 3 EEPROM Configuration Error
1 System 4 Battery Off
1 System 5 Too Many Tanks
1 System 6 System Security Warning
1 System 7 ROM Revision Warning
1 System 8 Remote Display Communications Error
1 System 9 Autodial Error
1 System 10Software Module Warning
1 System 11Tank Test Shutdown Warning
1 System 12Protective Cover Alarm
1 System 13BIR Shift Close Pending
1 System 14BIR Daily Close Pending
1 System 15PC(H8) Revision Warning
1 System 16System Self Test Error
1 System 17System Clock Incorrect Warning
1 System 18System Device Poll Timeout
2 Tank 1 Tank Setup Data Warning
2 Tank 2 Tank Leak Alarm
2 Tank 3 Tank High Water Alarm
2 Tank 4 Tank Overfill Alarm
2 Tank 5 Tank Low Product Alarm
2 Tank 6 Tank Sudden Loss Alarm
2 Tank 7 Tank High Product Alarm
2 Tank 8 Tank Invalid Fuel Level Alarm
2 Tank 9 Tank Probe Out Alarm
2 Tank 10Tank High Water Warning
2 Tank 11Tank Delivery Needed Warning
2 Tank 12Tank Maximum Product Alarm
2 Tank 13Tank Gross Leak Test Fail Alarm
2 Tank 14Tank Periodic Leak Test Fail Alarm
2 Tank 15Tank Annual Leak Test Fail Alarm
2 Tank 16Tank Periodic Test Needed Warning
2 Tank 17Tank Annual Test Needed Warning
2 Tank 18Tank Periodic Test Needed Alarm
2 Tank 19Tank Annual Test Needed Alarm
2 Tank 20Tank Leak Test Active
2 Tank 21Tank No CSLD Idle Time Warning
2 Tank 22Tank Siphon Break Active Warning
2 Tank 23Tank CSLD Rate Increase Warning
2 Tank 24Tank AccuChart Calibration Warning
2 Tank 25Tank HRM Reconciliation Warning
2 Tank 26Tank HRM Reconciliation Alarm

FS-8700-74 Veeder Root Driver Manual Page 17 of 33
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [email protected]
Category Alarm Type & Description
2 Tank 27Tank Cold Temperature Warning
2 Tank 28Tank Missing Delivery Ticket Warning
2 Tank 29Tank/Line Gross Leak Alarm
3 Liquid Sensor Alarm 2 Sensor Setup Data Warning
3 Liquid Sensor Alarm 3 Sensor Fuel Alarm
3 Liquid Sensor Alarm 4 Sensor Out Alarm
3 Liquid Sensor Alarm 5 Sensor Short Alarm
3 Liquid Sensor Alarm 6 Sensor Water Alarm
3 Liquid Sensor Alarm 7 Sensor Water Out Alarm
3 Liquid Sensor Alarm 8 Sensor High Liquid Alarm
3 Liquid Sensor Alarm 9 Sensor Low Liquid Alarm
3 Liquid Sensor Alarm 10Sensor Liquid Warning
4 Vapor Sensor Alarm 2 Sensor Setup Data Warning
4 Vapor Sensor Alarm 3 Sensor Fuel Alarm
4 Vapor Sensor Alarm 4 Sensor Out Alarm
4 Vapor Sensor Alarm 5 Sensor Short Alarm
4 Vapor Sensor Alarm 6 Sensor Water Alarm
4 Vapor Sensor Alarm 7 Sensor Water Out Alarm
4 Vapor Sensor Alarm 8 Sensor High Liquid Alarm
4 Vapor Sensor Alarm 9 Sensor Low Liquid Alarm
4 Vapor Sensor Alarm 10Sensor Liquid Warning
5 Input 1 Input Setup Data Warning
5 Input 2 Input Normal
5 Input 3 Input Alarm
6 Volumetric Line Leak 1 VLLD Setup Data Warning
6 Volumetric Line Leak 2 VLLD Self Test Alarm
6 Volumetric Line Leak 3 VLLD Shutdown Alarm
6 Volumetric Line Leak 4 VLLD Leak Test Fail Alarm
6 Volumetric Line Leak 5 VLLD Selftest Invalid Warning
6 Volumetric Line Leak 6 VLLD Continuous Handle On Warning
6 Volumetric Line Leak 7 VLLD Gross Line Test Fail Alarm
6 Volumetric Line Leak 8 VLLD Gross Line Selftest Fail Alarm
6 Volumetric Line Leak 9 VLLD Gross Pump Test Fail Alarm
6 Volumetric Line Leak 10VLLD Gross Pump Selftest Fail Alarm
6 Volumetric Line Leak 11VLLD Periodic Test Needed Warning
6 Volumetric Line Leak 12VLLD Annual Test Needed Warning
6 Volumetric Line Leak 13VLLD Periodic Test Needed Alarm
6 Volumetric Line Leak 14VLLD Annual Test Needed Alarm
6 Volumetric Line Leak 15VLLD Periodic Line Test Fail Alarm
6 Volumetric Line Leak 16VLLD Periodic Line Selftest Fail Alarm
6 Volumetric Line Leak 17VLLD Periodic Pump Test Fail Alarm
6 Volumetric Line Leak 18VLLD Periodic Pump Selftest Fail Alarm
6 Volumetric Line Leak 19VLLD Annual Line Test Fail Alarm
6 Volumetric Line Leak 20VLLD Annual Line Selftest Fail Alarm
6 Volumetric Line Leak 21VLLD Annual Pump Test Fail Alarm
6 Volumetric Line Leak 22VLLD Annual Pump Selftest Fail Alarm
6 Volumetric Line Leak 23VLLD Pressure Warning
6 Volumetric Line Leak 24VLLD Pressure Alarm
6 Volumetric Line Leak 25VLLD Gross Test Fault Alarm
6 Volumetric Line Leak 26VLLD Periodic Test Fault Alarm
6 Volumetric Line Leak 27VLLD Annual Test Fault Alarm
6 Volumetric Line Leak 28VLLD Fuel Out Alarm

FS-8700-74 Veeder Root Driver Manual Page 18 of 33
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [email protected]
Category Alarm Type & Description
7 Groundwater Sensor Alarm2 Sensor Setup Data Warning
7 Groundwater Sensor Alarm3 Sensor Fuel Alarm
7 Groundwater Sensor Alarm4 Sensor Out Alarm
7 Groundwater Sensor Alarm5 Sensor Short Alarm
7 Groundwater Sensor Alarm6 Sensor Water Alarm
7 Groundwater Sensor Alarm7 Sensor Water Out Alarm
7 Groundwater Sensor Alarm8 Sensor High Liquid Alarm
7 Groundwater Sensor Alarm9 Sensor Low Liquid Alarm
7 Groundwater Sensor Alarm10Sensor Liquid Warning
8 Type-A Sensor Alarm 2 Sensor Setup Data Warning
8 Type-A Sensor Alarm 3 Sensor Fuel Alarm
8 Type-A Sensor Alarm 4 Sensor Out Alarm
8 Type-A Sensor Alarm 5 Sensor Short Alarm
8 Type-A Sensor Alarm 6 Sensor Water Alarm
8 Type-A Sensor Alarm 7 Sensor Water Out Alarm
8 Type-A Sensor Alarm 8 Sensor High Liquid Alarm
8 Type-A Sensor Alarm 9 Sensor Low Liquid Alarm
8 Type-A Sensor Alarm 10Sensor Liquid Warning
12Type-B Sensor Alarm 2 Sensor Setup Data Warning
12Type-B Sensor Alarm 3 Sensor Fuel Alarm
12Type-B Sensor Alarm 4 Sensor Out Alarm
12Type-B Sensor Alarm 5 Sensor Short Alarm
12Type-B Sensor Alarm 6 Sensor Water Alarm
12Type-B Sensor Alarm 7 Sensor Water Out Alarm
12Type-B Sensor Alarm 8 Sensor High Liquid Alarm
12Type-B Sensor Alarm 9 Sensor Low Liquid Alarm
12Type-B Sensor Alarm 10Sensor Liquid Warning
13Universal Sensor Alarm 2 Sensor Setup Data Warning
13Universal Sensor Alarm 3 Sensor Fuel Alarm
13Universal Sensor Alarm 4 Sensor Out Alarm
13Universal Sensor Alarm 5 Sensor Short Alarm
13Universal Sensor Alarm 6 Sensor Water Alarm
13Universal Sensor Alarm 7 Sensor Water Out Alarm
13Universal Sensor Alarm 8 Sensor High Liquid Alarm
13Universal Sensor Alarm 9 Sensor Low Liquid Alarm
13Universal Sensor Alarm 10Sensor Liquid Warning
14Auto-Dial 1 Autodial Setup Data Warning
14Auto-Dial 2 Autodial Failed Alarm
14Auto-Dial 3 Autodial Service Report Warning
14Auto-Dial 4 Autodial Alarm Clear Warning
14Auto-Dial 5 Autodial Delivery Report Warning
18Elec. Dispenser 2 DIM Disabled Alarm
18Elec. Dispenser 3 DIM Communication Failure Alarm
18Elec. Dispenser 4 DIM Transaction Alarm
20Product Alarm 1 BIR Setup Data Warning
20Product Alarm 2 BIR Threshold Alarm
20Product Alarm 3 BIR Close Shift Warning
20Product Alarm 4 BIR Close Daily Warning
21Pressure Line Leak 1 PLLD Setup Data Warning
21Pressure Line Leak 2 PLLD Gross Test Fail Alarm

FS-8700-74 Veeder Root Driver Manual Page 19 of 33
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [email protected]
Category Alarm Type & Description
21Pressure Line Leak 3 PLLD Annual Test Fail Alarm
21Pressure Line Leak 4 PLLD Periodic Test Needed Warning
21Pressure Line Leak 5 PLLD Periodic Test Needed Alarm
21Pressure Line Leak 6 PLLD Sensor Open Alarm
21Pressure Line Leak 7 PLLD High Pressure Alarm (Obsolete V19)
21Pressure Line Leak 8 PLLD Shutdown Alarm
21Pressure Line Leak 9 PLLD High Pressure Warning (Obsolete V19)
21Pressure Line Leak 10PLLD Continuous Handle On Warning (Obsolete V19)
21Pressure Line Leak 11PLLD Periodic Test Fail Alarm
21Pressure Line Leak 12PLLD Annual Test Needed Warning
21Pressure Line Leak 13PLLD Annual Test Needed Alarm
21Pressure Line Leak 14PLLD Low Pressure Alarm
21Pressure Line Leak 15PLLD Sensor Short Alarm (Obsolete V19)
21Pressure Line Leak 16PLLD Continuous Handle On Alarm
21Pressure Line Leak 17PLLD Fuel Out Alarm
21Pressure Line Leak 18PLLD Line Equipment Alarm
26Wireless PLLD 1 WPLLD Setup Data Warning
26Wireless PLLD 2 WPLLD Gross Test Fail Alarm
26Wireless PLLD 3 WPLLD Periodic Test Fail Alarm
26Wireless PLLD 4 WPLLD Periodic Test Needed Warning
26Wireless PLLD 5 WPLLD Periodic Test Needed Alarm
26Wireless PLLD 6 WPLLD Sensor Open Alarm
26Wireless PLLD 7 WPLLD Communications Alarm
26Wireless PLLD 8 WPLLD Shutdown Alarm
26Wireless PLLD 9 WPLLD Continuous Handle On Warning (Obsolete V19)
26Wireless PLLD 10WPLLD Annual Test Fail Alarm
26Wireless PLLD 11WPLLD Annual Test Needed Warning
26Wireless PLLD 12WPLLD Annual Test Needed Alarm
26Wireless PLLD 13WPLLD High Pressure Warning (Obsolete V19)
26Wireless PLLD 14WPLLD High Pressure Alarm (Obsolete V19)
26Wireless PLLD 15WPLLD Sensor Short Alarm (Obsolete V19)
26Wireless PLLD 16WPLLD Continuous Handle On Alarm
26Wireless PLLD 17WPLLD Fuel Out Alarm
26Wireless PLLD 18WPLLD Line Equipment Alarm
99Externally Detected Alarm 1 Externally Detected Communication Alarm
99Externally Detected Alarm 2 Communications - Data Reception Timeout
99Externally Detected Alarm 3 Communications - Failed Checksum
99Externally Detected Alarm 4 Communications - Parity Error
99Externally Detected Alarm 5 Modem - Line Busy
99Externally Detected Alarm 6 Modem - No Answer
99Externally Detected Alarm 7 Modem - No Carrier
99Externally Detected Alarm 8 Modem - No Dial Tone
99Externally Detected Alarm 9 Modem - Modem Error
99Externally Detected Alarm 10Modem - Modem Not Responding
99Externally Detected Alarm 11Modem - Port Not Available
99Externally Detected Alarm 12Polling - Could Not Update Queue
99Externally Detected Alarm 13Polling - Invalid Data Type Requested

FS-8700-74 Veeder Root Driver Manual Page 20 of 33
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [email protected]
Appendix A.4. Security Codes
The RS-232 security code is an optional six-digit code used to limit external serial access to
the system for security purposes. It can be set to any unique set of characters using either
the front panel switches or the external communication interface setup commands. The
system will not respond to a command without the proper security code, if the DIP switch is
set to enable RS-232 security.
A four-position DIP switch is located on the CPU board, which is mounted in the right-back
of the console printer compartment. The DIP switch is next to the battery switch. The DIP
switch enables the security code and the switch positions are assigned as follows:
Switch
1 Front Panel Setup Security Enable
2 RS-232 Security Enable
3, 4 Unused
If RS-232 security is enabled then the Route parameter must be specified for the node. Set
the route parameter equal to the security code. Use a period to separate each digit of the
code.
Example: Security Code=234419
Set Route = 2.3.4.4.1.9
Special Note for security codes with alphabetic characters : Alphabetic characters cannot be
directly specified in the route field. They need to be specified as ASCII values.
Example : Security Code = 123abc
Set Route = 1.2.3.97.98.99
If the security feature has been disabled on the panel the set the route to zero as illustrated
in the following CSV file fragment.
Nodes
Node_Name, Port, Protocol, Route
Node_A , P1 , VEEDER , 0