beautypg.com

Appendix c.2. events and event categories – FieldServer Gamewell FCI E3 Series User Manual

Page 15

background image

FS-8700-132 Gamewell FCI-E3 Driver Manual

Page 15 of 20

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com

Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]

The Module number of 22 is compared with the MD’s Address and Length Parameters. The Address is the starting
number and the length defines the range. Both Map Descriptors have addresses of 1 and length of 99 and thus
both are still selected because the Module of 22 falls in this range.

The driver calculates an offset based on the offset specified in the Map Descriptor and the Module number relative
to the Map Descriptor address:

Map Descriptor Offset = 0

Map Descriptor Address = 1

Message Module = 22

Module 1’s data is stored at offset 0 and hence Module 22’s data will be stored at offset 21. The driver stores the
value 34 at offset 21 overwriting any data previously stored at that location. This is ‘Index Value’ Storage.

Secondary storage has been defined using the ‘DA_Bit_Name’ Data Array. The driver doubles the offset as two
locations are used for each address. The driver then reads the value found in the Data_Array, modifies it and
writes it back. Since the index value is 34 the driver modifies the 34

th

bit – or expressed another way, the driver

modifies the 2

nd

bit (34-32) at offset+1.

Thus, the driver calculates the offset for Bit Storage as 2 x 21 = 42. The driver sees that bit 34 is 2 2

nd

bit in the next

offset and so the driver reads DB_MODU:43, modifies the value by setting the 2nd bit on and then writing the
modified value back. During the modification all other bits are left intact. Thus using the Bit Storage method, a
single Module (or sensor…) can keep track of multiple events.

Appendix C.2. Events and Event Categories

The driver reports the event cause using the matching index value. There are 4 event categories:

1 = Other, 2 = Fault, 3 = Alarm, 4 = Trouble

The message category must match the ‘Event Type’ parameter specified on a Map Descriptor before that Map
Descriptor can be considered for storage of the message data. User defined events can be added to this table.
Refer to Appendix A.1

Index

Category

Event

1

FCI_EVENT_TYPE_FAULT

"Fault"

2

FCI_EVENT_TYPE_OTHER "Short"

3

FCI_EVENT_TYPE_OTHER "Disconnect"

3

4

FCI_EVENT_TYPE_OTHER "Comm Fault"

5

FCI_EVENT_TYPE_OTHER "Config Err"

6

FCI_EVENT_TYPE_OTHER "Eeprom Bad"

7

FCI_EVENT_TYPE_OTHER "Reset"

8

FCI_EVENT_TYPE_OTHER "Silence"

9

FCI_EVENT_TYPE_OTHER "Cross Zone"

3

10

FCI_EVENT_TYPE_OTHER "Acknwldgd"

3

Not defined in the spec

This manual is related to the following products: