-
A Sierra Monitor Company
Driver Manual
(Supplement to the FieldServer Instruction Manual)
FS-8700-112 FCI 7100 Series Serial Driver
APPLICABILITY & EFFECTIVITY
Effective for all systems manufactured after May 1, 2001
Driver Version:
1.01
Document Revision: 1
Download from Www.Somanuals.com. All Manuals Search And Download.
FS-8700-112 FCI 7100 Series Driver Manual
Page 3 of 24
1.
FCI 7100 Series Serial Driver Description
The FCI 7100 Series System Control Units are manufactured by Fire Control Instruments. A
7100 with an enabled serial port can transmit data to a FieldServer which can, in turn, make the
data available to other devices including those which communicate using different protocols
(e.g. BACnet)
This passive Client driver does not poll for data, nor does it send data or commands to the
7100. Messages received from the 7100 are ignored or stored on the FieldServer depending on
the status of the panel. The method of message processing and location on the FieldServer is
determined in the FieldServer configuration file. Once stored in the FieldServer the data is
available to be read or written using other protocols such as BACnet.
No automatic panel data synchronization technique exists. The data in the FieldServer and the
panel status have to be synchronized manually. This typically requires a panel reset.
Since the driver cannot send data or commands to the 7100 it cannot be used to acknowledge,
silence or reset alarms and other events.
The driver can process the single line messages sent from 7100 firmware versions earlier than
2.20 and 3 line messages produced in firmware versions 2.20 and later. Processing of 3 line
messages requires the 20 character System ID label to be defined.
The driver can process messages from networked panels. The driver connects to the main
panel. Subsidiary panels are configured to send event data to the main panel which then sends
messages to the FieldServer. If the panel is configured to send 3 line messages then the
source node information is sent in the line preceding the event and the driver uses this to
determine the panel at which the event originated and to store data appropriately.
The driver provides both client and server emulation. The server side of the driver is intended to
support FieldServer’s Quality Assurance program and is not intended to provide complete
emulation of a 7100 and is thus not fully documented. Should you require the Server side
functionality to be documented and enhanced, please contact FieldServer’s sales group.
Max Nodes Supported
FieldServer Mode
Nodes
Comments
1 Node per serial port. If there is more than one alarm
panel they can be networked and configured to send event
data to the primary panel. The driver can process
messages which identify the node of origin.
1 Node per serial port
Client
1
1
Server
Download from Www.Somanuals.com. All Manuals Search And Download.
FS-8700-112 FCI 7100 Series Driver Manual
Page 4 of 24
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 Ethernet connection
RJ45-RJ11/12 Cable assembly for FS connection to FCI
panel.
23069
-FS-8700-110
Driver Manual.
2.2.
2.2.1.
Provided by the Supplier of 3rd Party Equipment
Required 3rd Party Hardware
FCI Panel must be equipped with a RS-232 Serial Printer Port.
FCI Panel must be equipped with a PTRN module for isolation of the serial port.
2.2.2.
Required 3rd Party Software
Required 3rd Party Configuration
Optional Items
None
2.2.3.
None known.
2.2.4.
None.
Download from Www.Somanuals.com. All Manuals Search And Download.
FS-8700-112 FCI 7100 Series Driver Manual
Page 5 of 24
3.
Hardware Connections
The FieldServer is connected to the FCI panel as shown in the connection drawing.
3 Wire Cable (Tx, Rx, Gnd)
One Panel per Port
FieldServer provide a pre-fabricated cable.
FCI 7100 Series Panel
6
5
4
3
2
1
1
2
3
4
5
6
7
8
(408)-262-2299
FCI
Panel
RJ45
FIELDSERVER
FCI 7100
FieldServer
CONNECTION DIAGRAM
In this view the RJ12 and RJ45 converter
clips are facing away from the viewer and
are not visible.
BASE NAME:
FILE NAME:
DATE: 3/1/05
BY: MF
Download from Www.Somanuals.com. All Manuals Search And Download.
FS-8700-112 FCI 7100 Series Driver Manual
Page 6 of 24
Top right hand side of
board.
Connector J3 – label on
right.
Download from Www.Somanuals.com. All Manuals Search And Download.
FS-8700-112 FCI 7100 Series Driver Manual
Page 7 of 24
4.
Configuring the FieldServer as a FCI 7100 Series Serial Driver Client
For a detailed di7100ssion 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 (See “.csv” sample files
provided with the FieldServer).
This section documents and describes the parameters necessary for configuring the FieldServer
to communicate with a FCI 7100 Series 7100.
4.1.
Data Arrays/Descriptors
The configuration file tells the FieldServer about its interfaces, and the routing of data
required. In order to enable the FieldServer for FCI 7100 Series Serial 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.
Section Title
Data_Arrays
Column Title
Function
Legal Values
Up to 15 alphanumeric
characters
Data_Array_Name
Provide name for Data Array
Float, Bit, UInt16, SInt16,
Provide data format. Each Data Packed_Bit,
Byte,
Data_Array_Format
Data_Array_Length
Array can only take on one format.
Packed_Byte,
Swapped_Byte
Number of Data Objects. Must be
larger than the data storage area
required by the Map Descriptors for
the data being placed in this array.
1-10,000
Example
// Data Arrays
Data_Arrays
Data_Array_Name,
DA_AI_01,
DA_AO_01,
DA_DI_01,
Data_Array_Format,
Data_Array_Length
UInt16,
UInt16,
Bit,
200
200
200
200
DA_DO_01,
Bit,
Download from Www.Somanuals.com. All Manuals Search And Download.
FS-8700-112 FCI 7100 Series Driver Manual
Page 8 of 24
4.2.
Client Side Connection Descriptions
Section Title
Connections
Column Title
Function
Legal Values
P1-P8, R1-R21
Specify which port the device is
connected to the FieldServer
Port
FCI_7100, FCI_7100_series,
FCI7100
Protocol
Specify protocol used
Baud*
Parity*
Data_Bits*
Stop_Bits*
Specify baud rate
Specify parity
Specify data bits
Specify stop bits
1200 – Vendor Limitation
None – Vendor Limitation.
8 – Vendor Limitation
1 – Vendor Limitation
Handshaking* The 7100 series panels do not support hand shaking.
Poll _Delay*
This commonly used parameter has no meaning for this driver.
Example
// Client Side Connections
Connections
Port,
P8,
Protocol,
FCI_7100,
Baud,
1200
Parity
None
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.
Download from Www.Somanuals.com. All Manuals Search And Download.
FS-8700-112 FCI 7100 Series Driver Manual
Page 9 of 24
4.3.
Client Side Node Descriptors
Section Title
Nodes
Column Title
Node_Name
Function
Provide name for node
Legal Values
Up to 32 alphanumeric characters
This parameter only has meaning The protocol is node-less - the
for this driver when multiple messages do not contain
panels are networked in an FCI information identifying a unique
network. In this case the source and/or destination node
Node_ID
Protocol
NODE_ID is the panel number. address. Thus this parameter need
Set the Node_ID of the local panel not be specified if only one 7100 is
to zero, and create one node connected per FieldServer serial
descriptor for each panel setting port. In networked configurations,
the Node_ID to the panel number. specify whole numbers 0,1,2,3 …
FCI_7100,
FCI7100
FCI_7100_series,
Specify protocol used
Only required for networked
configurations.
This parameter tells the driver
what to do with ‘Reset’ messages.
When not specified or set to
‘Reset_by_any_Node ‘ then the
driver will reset the data array
FCI_Reset_Acti points associated with the given Reset_by_any_Node,
on_Option*
node irrespective of the reset Reset_by_this_Node_Only
message’s origin.
When
set
to
‘Reset_by_this_Node_Only’ then
the driver only resets the data
associated with the given node if
the reset originated from the same
node.
Specify which port the device is
connected to the FieldServer
Connection
P1-P8, R1-R21
Example
// Client Side Nodes
Nodes
Node_Name,
Panel-01,
Protocol,
FCI_7100,
Connection
P8
Download from Www.Somanuals.com. All Manuals Search And Download.
FS-8700-112 FCI 7100 Series Driver Manual
Page 10 of 24
4.4.
4.4.1.
Client Side Map Descriptors
FieldServer Related Map Descriptor Parameters
Column Title
Function
Legal Values
Name of this Map Up to 32 alphanumeric
Map_Descriptor_Name
Data_Array_Name
Descriptor
characters
Name of Data Array
where data is to be
One of the Data Array
names from “Data Array”
section above
stored
in
the
FieldServer
Starting location in Data 0 to maximum specified in
Data_Array_Offset
Function
Array
“Data Array” section above
Function of Client Map
Descriptor.
Server, Passive_Client
4.4.2.
Driver Related Map Descriptor Parameters
Function
Column Title
Legal Values
One of the node
names specified
in Section 4.3
Node_Name
Event Type
Name of Node to fetch data from
This driver uses this parameter to determine
the suitability of a Map Descriptor when
looking for a location to store data from an
incoming message.
Any, Other, Fault,
Alarm, Trouble
A Map Descriptor may be defined to store
only ‘Alarm’, ‘Fault’, ‘Trouble’ or ‘Other events.
Alternatively, specify “Any”
A table of events vs. categories is provided in
Appendix A.1
This driver uses this parameter to determine
the suitability of a Map Descriptor when
looking for a location to store data from an
incoming message.
Zone,
Loop,
Module, Panel
Relay,
Sensor,
Point Type
Ignored when the Point Type is ‘Panel’
Point Type = Relay 1..255
Relay/Loop/Zone Point Type = Zone 1..8
Whole Numbers
1, 2 , etc
Number
Point Type = Loop 1..2
Point Type = Module 1..2
Point Type = Sensor 1..2
Each Map Descriptor defines storage
locations for a series of addresses. This
parameter specifies the length of the series.
1,2,3 .etc
Whole numbers
Length
Download from Www.Somanuals.com. All Manuals Search And Download.
FS-8700-112 FCI 7100 Series Driver Manual
Page 11 of 24
Column Title
Function
Legal Values
This parameter is only considered for those
Map Descriptors whose ‘Event Type’ is
Module or Sensor. It specifies the starting
Address
1..99
module or sensor number.
The length
parameter the determines the range of the
sensor/module numbers
By default the driver stores using the ‘Index
Value’ Method.
Set this parameter to ‘Bit’ to have the driver
Store As
use the primary Data Array to store using the Bit, Index_Value
‘Bit Storage’ Method.
These methods are described in Appendix
A.3
If the default ‘Store As’ is specified or if the
parameter is omitted then you can specify a
One of the Data
secondary array using this parameter - the
Array names from
DA_Bit_Name
driver will store event data as ‘Bit Storage’ in
“Data
Array”
the secondary array (and as ‘Index Values’ in
section above
the primary array.)
These methods are
described in Appendix A.3
If a reset if received you can prevent the
driver resetting the Data Array Points
associated with the Map Descriptor by
specifying this parameter.
Clear on Reset*
Yes, No
Download from Www.Somanuals.com. All Manuals Search And Download.
FS-8700-112 FCI 7100 Series Driver Manual
Page 12 of 24
4.5.
Map Descriptor Example 1 – Sensor / Module Events
If messages from Loop 1, Module 1 to 99 are received then the MD in this example will be used for storage. If you have modules on
more than one loop then you will need one MD for each loop. In this example the event type was set to ‘Alarm’. This means that
only ‘Alarm’ events will be stored using this MD. This could be useful if you are only interested I one category of events. If you want
all events stored then change the ‘Event Type’ to ‘Any’.
Example:
F.S.E.C.
FIRST ALARM:
:[CR][LF]
UP STAIRS N. ENT
Manual Station L1M21 00:37:28 01/01/99[CR][LF]
// Client Side Map Descriptors
Map_Descriptors
Event
Type,
Point
Type,
Relay/Loop/Zone
Number,
Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function,
Node_Name,
Address, Length, Clear_on_reset
ModuleData1,
DA_MODULE,
0,
Passive_Client, Panel-01,
Alarm, Module 1,
1,
99,
Yes,
It
is
Tell the driver
the Data Array
The
listens
passively
messages from
the Panel. It
cannot poll for
data.
driver
for
The name of
the Node
defined in the
Node
In this example,
The
specifies
address
the
Change this to
recommended
that
allocate unique
MD names.
only
Alarm
‘Sensor’
sensors.
for
you
name
and
events will be
stored.
starting Module
number and the
Length tells the
driver the range
of Modules.
starting location
that data should
be stored.
Descriptor
Messages
reporting other
events will be
ignored unless
other MD’s are
defined.
In this example:
Module 1 to 99
Download from Www.Somanuals.com. All Manuals Search And Download.
FS-8700-112 FCI 7100 Series Driver Manual
Page 13 of 24
4.6.
Map Descriptor Example 2 – Bit Storage
This example defines storage location for Relay Point events. The example would work for all other point types. In the example, both
primary and secondary storage Data Arrays have been specified. The driver stores index values in the primary array. Each new
event for a particular relay will overwrite the value stored previously. In the Bit Array, the driver sets the bit corresponding to the
event, leaving other bits unchanged – thus the 2ndary storage can be used to determine if more than one event is active at a time.
// Client Side Map Descriptors
Map_Descriptors
Event
Type,
Any,
Point
Type,
Relay,
Relay/Loop/Zone
Number,
1,
Map_Descriptor_Name,
RelayData,
Data_Array_Name,
DA_RELAY,
Data_Array_Offset,
0,
DA_Bit_Name,
DB_Relay,
Function,
Node_Name,
Panel-01,
Address,
-,
Length,
4,
Clear_on_reset
Yes
Passive_Client,
MD’s for storing Relay,
Loop, Zone and Panel
do not need the address
specified.
Data_Array_Name is where the primary DA is specified. Index values are
stored here.
DA_Bit_Name is where secondary storage is defined. Events are stored
by setting appropriate bits.
Remember that 2 elements per Relay, Module, Sensor, Loop are used.
Download from Www.Somanuals.com. All Manuals Search And Download.
FS-8700-112 FCI 7100 Series Driver Manual
Page 14 of 24
5.
Configuring the FieldServer as a FCI 7100 Series Serial Driver Server
The server side of the driver is intended to support FieldServer’s Quality Assurance program
and is not intended to provide complete emulation of a 7100 and is thus not fully documented.
Should you require the Server side functionality to be documented and enhanced, please
contact FieldServer’s sales group.
Download from Www.Somanuals.com. All Manuals Search And Download.
FS-8700-112 FCI 7100 Series Driver Manual
Page 15 of 24
Appendix A. Advanced Topics
Appendix A.1. 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.
Index
1
2
3
4
5
6
7
8
Category
Event
"Fault"
"Short"
"Disconnect"
"Comm Fault"
"Config Err"
"Eeprom Bad"
"Reset"
2
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
3
1
1
1
1
1
1
1
1
1
1
1
1
1
4
1
1
"Silence"
9
"Cross Zone"
"Acknwldgd"
"Walk Test"
"Alarm Test"
"SPVSN Test"
"Fault Test"
"Fire Drill"
"Batt Test"
"PRGM Mode"
"Action"
"Loop Break"
"Alarm"
"P.A.S."
"Off-Normal"
"RZA Fault"
"Verify"
"CM SHort"
"Test Fail"
"Alert"
"Dirty"
"Very Dirty"
"Missing"
"Wrong Type"
"Extra Addr"
"Clock Err"
"Trouble"
"MLT Events"
"Alrm Ackd"
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
Download from Www.Somanuals.com. All Manuals Search And Download.
FS-8700-112 FCI 7100 Series Driver Manual
Appendix A.2. Extending the Event Table
Page 16 of 24
New event causes may be added to the Event Table and the index value or category of
existing event causes modified by adding a section to the configuration CSV file. The
examples below illustrate this:
Example 1: Index value of 'Trouble' is updated to a new value of 100
Driver_Table
Event_Type_Description, Event_Type_Index_Value, Event_Type_Category ,
TROUBLE, 100, 4,
Protocol
FCI_7200
Example 2: New Entry is added
Since it has been added as category=3, only MD's with 'Event Type' set to Alarm or ANY
will capture messages with this event description
Driver_Table
Event_Type_Description,
DESTROYED,
Event_Type_Index_Value,
51,
Event_Type_Category,
3,
Protocol
FCI_7200
For categories use the following values
'Other' = 1
'Fault' = 2
'Alarm' = 3
'Trouble' = 4
Appendix A.3. How Data is stored
All messages less than 102 characters long are discarded. All other messages are
processed as follows:
•
The driver determines if the message is a Zone, Relay, Loop, Sensor, Module or Panel
message.
•
•
•
The driver finds all Map Descriptors with matching ‘Point Type’ parameters.
The event category is determined.
Map Descriptor selection is refined based on whether the ‘Event Type’ matches or has
been defined as “Any:
•
The driver determines the Loop. Relay, Zone, Sensor and Module numbers from the
message and refines its selection of Map Descriptors by selecting those that match the
values determined from the message.
•
•
The selected Map Descriptors are now used to determine a data array and offset at
which to store the data.
Finally the driver checks the ‘Store As’ parameter. If it hasn’t been specified then ‘Index
Value’ storage is assumed. If it has been specified as ‘Bits’ then the driver will perform
‘Bit Storage’. In cases where the Map Descriptor has both a primary and secondary
Data Array, the driver will use ‘Index Value’ storage using the primary data array and ‘Bit
Storage’ using the secondary array.
Download from Www.Somanuals.com. All Manuals Search And Download.
FS-8700-112 FCI 7100 Series Driver Manual
Example:
Page 17 of 24
The following fragment is part of a Map Descriptor definition; some parameters have been omitted for the purposes of clarity.
Map_Descriptors
Data_Array_Name, Data_Array_Offset, Event Type, Point Type, Relay/Loop/Zone Number, Address, Length, Clear_on_reset, DA_Bit_Name
DA_MODU
,
0,
0,
0,
0,
0,
ANY,
Module,
Module,
Module,
Module,
Module,
1,
1,
1,
1,
1,
1,
1,
1,
1,
1,
99,
99,
99,
99,
99,
Yes,
Yes,
Yes,
Yes,
Yes,
DB_MODU
DA_MODU_A,
DA_MODU_F,
DA_MODU_T,
ALARM,
FAULT,
TROUBLE,
OTHER,
DB_MODU_A
DB_MODU_F
DB_MODU_T
DB_MODU_O
DA_MPODU_O,
Message = “FAULT:
AC Power
7100
0:00:04 1/01/92”
•
This message does not report the status of a Zone, Relay, Loop, Sensor or Module and is therefore assumed to be a panel
message. Since there is no MD with “Point Type” Panel, the message is ignored.
Message = “TROUBLE:
QZUb L1M22 << Chief's Office >>
5:24:00 3/03/93”
•
This message reports status for Loop 1 Module 22. Since all the MD’s in the example have a ‘Point Type’=‘Module’, they are all
considered for storage.
•
The driver looks in the Event Table and finds it has an index value of 34 and a category of 4 (Trouble). Only the MD’s with “Event
Type” set to “Any” and “Trouble” are now considered.
•
•
Since the value of the ‘Relay/Loop/Zone’ parameter matches the Loop number in the message, these MD’s remain in contention.
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 MD’s 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 MD and the Module number relative to the MD’s address:
MD Offset = 0
MD 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.
Seconday storage has been defined using the ‘DA_Bit_Name’ Data Array. The driver doubles the offset as two locations are used
for each address. Then the driver reads the value found in the Data_Array, modifies it and writes it back. As the index value is 34
the driver modifies the 34th bit – or expressed another way, the driver modifies the 2nd bit (34-32) at offset+1.
Thus, driver calculates the offset for Bit Storage as 2 x 21 = 42. The driver sees that bit 34 is 2 2nd 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. This using the Bit Storage method, a single Module (or sensor…) can keep track of
multiple events.
•
•
Download from Www.Somanuals.com. All Manuals Search And Download.
FS-8700-112 FCI 7100 Series Driver Manual
Appendix A.4. Panel Synchronization
Page 18 of 24
Manual synchronization is required. Push the reset button on the panel. This transmits a
reset message to the FieldServer, which clears the data in the FieldServer. After a reset the
panel sends messages to report all abnormal states. When all these messages have been
processed the FieldServer and panel will be synchronized. This process can be repeated at
any time.
Appendix A.5. What happens when the panel sends a Reset Message
When a panel sends a reset message the driver processes every single Map Descriptor,
looking at the ‘Clear on Reset’ parameter (See section 4.4.2). If the parameter is set to yes,
then the driver sets all the Data Array elements referenced by the Map Descriptor to zero by
looking up the DA Name, the Data Array offset and the length. The driver also clears the
relevant sections of a Data Array specified with the DA_Bit_Name parameter.
The process can take some time. For this reason, it is suggested that you take care not to
set MD length to a value larger than necessary.
Additional considerations apply when panels are connected together in an FCI network. See
section ??????????????
Appendix A.6. Networked Panels.
The driver can processes messages and store data from multiple panels provided that:
•
The panels are connected in an FCI network and the panels are configured to report
their events to the main panel
•
The main panel is configured to send the node of origin in a message preceding the
event message. Consult with FCI for information on how to achieve this.
Example of message sent by a panel that is networked. The driver is dependent on seeing
the node of event origin included in parenthesis before each event message.
F.S.E.C. (Node02):
MISSING:
PROJ MANG OFFICE
Thermal Det
L1S02 00:40:18 01/01/99
00:40:18 01/01/99
F.S.E.C.
RESET:
(Local):
The main panel is identified as ‘(Local)’. The driver interprets this as Node_ID=0.
To capture events from multiple networked panels you need one Node Descriptor for each
panel with the appropriate Node_ID. Each node requires a set of Map Descriptors.
Download from Www.Somanuals.com. All Manuals Search And Download.
FS-8700-112 FCI 7100 Series Driver Manual
Appendix B. Driver Error Messages.
Page 19 of 24
Message
Description
FCI7100:#1 FYI. Use a DA called <%s> to expose
diagnostic info., FCI_7100_STATS_DA )
FCI7100:#2 FYI. Added Event Desc=<%s>
Refer to Appendix B.1
Index=%d Categ=%d
new_event_desc_index_value
new_event_desc_categ ) ;
,
new_event_desc , Printed for your info only. No action
, required if it confirms your expectations.
FCI7100:#3 Err. No space. Reject Event
Desc=<%s> Index=%d
new_event_desc , There is only space for 60 event types.2
new_event_desc_index_value ) ;
,
You are adding an event type that
FCI7100:#4 FYI. Duplicate Event Desc=<%s>. , already exists. If you are updating the
new_event_desc ) ;
category, ignore the message. Otherwise
correct the configuration file.2
You are adding an event type that
FCI7100:#5 FYI. Duplicate Event Desc=<%s>. , already exists. If you are updating the
new_event_desc ) ;
index value, ignore the message.
Otherwise correct the configuration file.2
If the event index is greater than 64 then
the data cannot be stored as bits as only
64 bits are reserved for events.
FCI7100:#6 Err. Event Index=%d. Too big to set
bit., drv_bd->event_index )
FCI7100:#7a Err. DA=%s too short. Rqd=%d, dt- The MD in question has a length and
>buffer_name , offset );
FCI7100:#7b Err. DA=%s too short. Rqd=%d,
possible_md->data->buffer_name , offset );
offset which makes it run past the end of
the Data Array. Message 7b is printed
when data is being stored as bits.2
FCI7100:#8 FYI. Reset was rcvd and processed! Printed for your info only. No action
Stamped %s %s , drv_bd->time , drv_bd->date )
required.
This message is printed when a reset
was received but for one or more reason
the driver could not reset any data. Have
you set 'Clear_on_Reset' to 'no' on all
MD's ?
FCI7100:#9 Err. Reset was ignored.
FCI7100:#10 FYI. Reset of DA=%s Off=%d
Len=%d,
possible_md->data->buffer_name
, Printed for your info only. No action
, required..
possible_md->bxi_data_buffer_offset
possible_md->data_length );
FCI7100:#11 Err. Cant reset DA=%s len=%d
rqd=%d,
da_get_length_in_items
possible_md->data
>data_length+possible_md-
>bxi_data_buffer_offset );
possible_md->data->buffer_name
,
The MD in question has a length and
(
,
(DAH_TYP)
possible_md-
offset which makes it run past the end of
)
the Data Array.2
2 Correct the configuration file, download to the FieldServer and restart the FieldServer for the changes to
take effect.
Download from Www.Somanuals.com. All Manuals Search And Download.
FS-8700-112 FCI 7100 Series Driver Manual
Message
Page 20 of 24
Description
FCI7100:#12a Err. No MD's to store message A message arrived and the driver could
data.
not find a place to store the data.
Perhaps you were not expecting this type
of event/this loop/sensor. If you are not
interested in the data then ignore the
FCI7100:#12b Err. No MD's to store message
data."
FCI7100:#13 Err. Msg was ignored. MD Required
for Storage.
message.
Otherwise
update
the
configuration file. 3
FCI7100:#13a Err. Diagnostic 1);
FCI7100:#13b Err. Diagnostic 2);
FCI7100:#13c Err. Diagnostic 3);
Take a log. Try and repeat the event that
caused the message to be printed. Then
contact tech support.
FCI7100:#14 Err. <%s> file not found., md-
>mapdesc_name ) ;
If this error is repeated often it is possible
that a FCI firmware update as made the
driver unusable. Take a log and contact
tech support.
FCI7100:#15 Err. Event Type=<%s> Not
recognized." , drv_bd->event_desc )
FCI7100:#16 Err. Point Type='%c'(%#x) Not
recognized. , drv_bd->point_identifier[0] , drv_bd-
>point_identifier[0] ) ;
This message should only be printed if a
FCI7100:#17 Err. Loop=%d < 1. Rejected. , byte in a message has been corrupted. If
drv_bd->loop )
you notice it more than once then take a
log and contact tech support.
If this error is repeated often it is possible
that a FCI firmware update as made the
driver unusable. Take a log and contact
tech support.
FCI7100:#18 Err. Loop Type='%c'(%#x) Not
recognized. , drv_bd->point_identifier[2] , drv_bd-
>point_identifier[2] )
FCI7100:#19 Err. Relay=%d < 1. Rejected. , This message should only be printed if a
drv_bd->relay
FCI7100:#20 Err. Zone=%d < 1. Rejected. ,
drv_bd->zone"
FCI7100:#21 Err. Point Type not recognized
FCI7100:#22 Err. Undefined Point Type"
FCI7100:#23 Err. Event Type not recognized
FCI7100:#24 Err. Undefined Event Type
FCI7100:#25a Err. Address+Length>99. Length
Truncated
byte in a message has been corrupted. If
you notice it more than once then take a
log and contact tech support.
Valid Point Types are listed in section
4.4.23
Valid Event Types are listed in section
4.4.23
The maximum value for a sensor/module
is 99. The combination of address and
length specified produce a number > 993
FCI7100:#25b Err. Address+Length>99. Length
Truncated
FCI7100:#26 Err. Invalid Module number.
Expected 1..99
FCI7100:#27a Err. Invalid Loop number. Expected
1..10
FCI7100:#27b Err. Invalid Loop number. Expected
1..10
Correct the configuration file3
FCI7100:#27c Err. Invalid Loop number. Expected
1..10
3 Correct the configuration file, download to the FieldServer and restart the FieldServer for the changes to
take effect.
Download from Www.Somanuals.com. All Manuals Search And Download.
FS-8700-112 FCI 7100 Series Driver Manual
Page 21 of 24
Message
Description
FCI7100:#28 Err. Invalid Sensor number.
Expected 1..99
FCI7100:#29 Err. Invalid Zone number. Expected
1..255
Correct the configuration file. 4
FCI7100:#30 Err. Invalid Relay number. Expected
1..255
Valid Point Types are listed in Section
4.4.24
FCI7100:#31 Err. Point Type Invalid.
You must specify the 'length' of each Map
Descriptor. Refer to Section 4.4.244
The driver can only listen passively for
message from the panel. Remove any
active Map Descriptors from the
configuration file.
FCI7100:#32 Err. No MD Length. Default to 1
FCI7100:#33 Err. Driver cant poll or write.
An event message is less than 80 bytes
long. If this error is repeated often it is
possible that a FCI firmware update as
made the driver unusable. Take a log and
contact tech support.
FCI7100:#36 Err. Too Short. Bytes=%d , conn-
>ux_iptr"
4
Correct the configuration file, download to the FieldServer and restart the FieldServer for the
changes to take effect.
Download from Www.Somanuals.com. All Manuals Search And Download.
FS-8700-112 FCI 7100 Series Driver Manual
Appendix B.1. Driver Stats Exposed.
Page 22 of 24
In addition to the standard FieldServer operating statistics the driver exposes certain key
stats in a Data Array if required. An upstream device can then monitor these stats.
Add the following to your configuration file to activate these stats.
// Expose Driver Operating Stats.
Data_Arrays
Data_Array_Name,
fci-7100-stats,
Data_Format,
UINT32,
Data_Array_Length
200
The driver exposes stats based on a port handle. The offset specified in the table below
must be added to the handle number multiplied by 100. i.e. for port whose handle is 1 then
the driver will store the 1st stat at 1+100*1=101.
Stat
Offset Description
Increments each time point data
is received but there is no Map
Descriptor to store the data
(any)
#define FCI_7100_STAT_NO_PLACE_TO_STORE
1
Increments each time point data
is received but there is no Map
Descriptor to store Zone data
Increments each time point data
is received but there is no Map
Descriptor to store Relay data
Increments each time point data
is received but there is no MD to
store the Loop data
Increments each time point data
is received but there is no MD to
store the Sensor data
Increments each time point data
is received but there is no MD to
store the Module data
#define
2
3
4
5
6
7
FCI_7100_STAT_NO_PLACE_TO_STORE_ZONE
#define
FCI_7100_STAT_NO_PLACE_TO_STORE_RELAY
#define
FCI_7100_STAT_NO_PLACE_TO_STORE_LOOP
#define
FCI_7100_STAT_NO_PLACE_TO_STORE_SENSOR
#define
FCI_7100_STAT_NO_PLACE_TO_STORE_MODULE
Number of times that a message
line was was zero bytes long
(excluding the terminator)
#define FCI_7100_STAT_EMPTY_MSG
Number of times that a message
line was was too short probably
a system id tag line
Increments each time a reset
was rcvd but no DA was reset
Increments each time point data
is received but there is no MD to
store data that cannot be
attributed to a zone, relay, loop,
sensor, module
#define FCI_7100_STAT_SHORT_MSG
#define FCI_7100_STAT_NO_RESET
8
9
#define
10
11
FCI_7100_STAT_NO_PLACE_TO_STORE_PANEL
Increments
each
time
a
#define FCI_7100_STAT_RCVD_MSGS
message is received
Download from Www.Somanuals.com. All Manuals Search And Download.
FS-8700-112 FCI 7100 Series Driver Manual
Page 23 of 24
Stat
Offset Description
Increments
each
time
a
character is recieved from the
panel. The bytes are only added
when a message terminator is
received. Thus this count is
equiv to the byte count in all
FCI_7100_STAT_RCVD_MSGS
#define FCI_7100_STAT_RCVD_BYTES
12
Increments
each
time
a
#define
message is parsed without
13
FCI_7100_STAT_PARSED_NO_ERRS_EXCLD_RESET
errors.
Excludes
Reset
Messages
Increments each time a reset
message is parsed without
errors.
#define FCI_7100_STAT_PARSED_NO_ERRS_RESET 14
Increments
each
time
a
message is parsed with no
errors but the nature of the
message doesnt require data to
be stored. (eg empty msg lines)
#define FCI_7100_STAT_PARSED_NO_ACTION
#define FCI_7100_STAT_PARSED_WITH_ERRS
15
16
Increments
each
time
a
message produces an error
when parsed.
Set to
altogether
Set to 1 to inhibit resets from
clearing arrays
Set to 1 to inhibit reset function
from looping thru MD's
1
to inhibit resets
#define FCI_7100_STAT_INHIBIT_RESET
17
18
19
#define FCI_7100_STAT_INHIBIT_RESET_DA_PUT
#define FCI_7100_STAT_INHIBIT_RESET_WHILE
Increments
each
time
a
#define FCI_7100_STAT_NODE_INFO_MSG
20
message with node information
is received
Increments each time an event
needs to be stored, the event
contains node info and the node
cannot be found so there is no
match and the message was
discarded.
#define
21
FCI_7100_STAT_NO_PLACE_TO_STORE_NODE
Download from Www.Somanuals.com. All Manuals Search And Download.
FS-8700-112 FCI 7100 Series Driver Manual
Page 24 of 24
THIS PAGE INTENTIONALLY LEFT BLANK
Download from Www.Somanuals.com. All Manuals Search And Download.
|