Map Descriptor Example 1 - Alarms - FieldServer FS-8700-74 Driver Manual

Table of Contents

Advertisement

FS-8700-74 Veeder Root Driver Manual
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,
Poller
1.0s
,
Map_Descriptors
Map_Descriptor_Name,
Data_Array_Name,
Sys_alms01
,
DA_S1
Tank_Alms1
,
DA_T1
LiqSensor_Alm1,
DA_L1
VaporSens_Alm1,
DA_V1
Input_Alm1
,
DA_I1
VolLine_Alm1 ,
DA_O1
GWater_Alms1 ,
DA_G1
TypeB_SensALm1 ,
DA_B1
Univ_SensAlm1 ,
DA_U1
AutoDial_Alms1 ,
DA_F1
MechDisp_Alm1 ,
DA_M1
ElecDisp_Alm1 ,
DA_E1
Product_Alms1 ,
DA_P1
PressLine_Alm1 ,
DA_R1
External_Alm1 ,
DA_X1
WPLLD_Alms1 ,
DA_W1
These Map
Only the Map
Descriptors are
Descriptor used to
passive because
generate the poll
they do not
requires a scan
generate
interval.
messages. They
are used to store
data returned by
the system status
poll.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: (408) 262-2299 Fax: (408) 262-9042 Toll_Free: 888-509-1970 email: support@fieldserver.com
Data_Array_Name,
Data_Array_Offset,
DA_101
,
0
Data_Array_Offset
Function,
,
0
,
passive ,
,
0
,
passive ,
,
0
,
passive ,
,
0
,
passive ,
,
0
,
passive ,
,
0
,
passive ,
,
0
,
passive ,
,
0
,
passive ,
,
0
,
passive ,
,
0
,
passive ,
,
0
,
passive ,
,
0
,
passive ,
,
0
,
passive ,
,
0
,
passive ,
,
0
,
passive ,
,
0
,
passive ,
The address must
correspond to the
tank/sensor/input/device
number.
One Map Descriptor
required for each
tank/sensor/input/device.
Page 10 of 33
Function,
node_name,
,
rdbc
,
Node_A ,
node_name,
Address,
Node_A ,
1
,
Node_A ,
1
,
Node_A ,
1
,
Node_A ,
1
,
Node_A ,
1
,
Node_A ,
1
,
Node_A ,
1
,
Node_A ,
1
,
Node_A ,
1
,
Node_A ,
1
,
Node_A ,
1
,
Node_A ,
1
,
Node_A ,
1
,
Node_A ,
1
,
Node_A ,
1
,
Node_A ,
1
,
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)
Address,
Length,
Data_Type,
1
,
30 ,
System Status
Length,
Data_Type
30
,
System
30
,
Tank
30
,
Liquid Sensor
30
,
Vapor Sensor
30
,
Input
30
,
Volumetric Line
30
,
Groundwater Sensor
30
Type-B Sensor
30
,
Universal Sensor
30
,
Auto-Dial
30
,
Mech. Dispenser
30
,
Elec. Dispenser
30
,
Product
30
,
Press. Line
30
,
External
30
,
WPLLD

Advertisement

Table of Contents
loading

Table of Contents