FieldServer FS-8700-40 - Manual (Page 30)

FS-8700-40 SBT FSI Driver Manual Page 30 of 32
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]
Appendix B. TROUBLESHOOTING
Appendix B.1. Checksum Errors
Messages using special characters with ASCII values higher than 127 (e.g. Portugese з, б,у, г, etc), provide a bad
checksum at 7 data bits. This is resolved if 8 data bits are used.
Appendix B.2. Recording Active Events – XLS Panel
When there is an active event in the XLS panel, the FieldServer will report this event in the Driver log of RUInet
(Remote User Interface) regardless of whether there is a Map Descriptor to store the event or not. The report may
state the location of the event as follows:
1^10^0^26^1
This translates to the following: Panel Number ^ Block (Loop) ^ sub-Module ^ Address ^ Component Address
Alternatively the location of the event could be recorded as:
P:L-D
This translates to the following: Panel Number: Block (Loop) - Device
Appendix B.3. Using Trouble Codes
In order to see the trouble codes for incoming troubles it is necessary to use a Uint16 or Int16 data array for the
trouble instead of the normal Bit. When the driver stores a trouble code of for example 15 into a Bit data array, it
will be displayed as 1 since Bit only holds either a zero or a one value. Using a Uint16 or Int16 data array will
ensure the value of 15 is displayed.
The following information is taken from Siemens Fire Safety documentation
MXL/XLS Trouble Codes
These codes are sent in Field 5 of the Trouble in, Trouble out and Trouble Acknowledge messages 24H, 25H and
26H. Each code is sent as up to 3 ASCII bytes. Leading zeros are not sent. The Request Trouble Type message
(43H) can be used to obtain the text strings shown below for each of these codes. The trouble text string is
returned in the Trouble Type message (53H).
Trouble Type Trouble Type Text
0
1 Multiple Response
2 Communication Error
3 Input Dev. Response too low
4 Device Receive Error
5 Dev Detected Waveform Error
6 Not Responding
7 Not Responding
8 Unspecified Dev. Responding
9 Incorrect ID
10 INPUT DE-ISOLATED
11 INPUT ISOLATED
12 Input Disarmed
13 Addressable Relay disarmed
14 Relay Disarmed
15 Signal Circuit Disarmed
Trouble Type Trouble Type Text
16 Solid State Output Disarmed
17 Relay Supervision Failure
18 Signal Circuit Loop Open
19 Loop Disarmed
20 Class A Trouble
21 Relay Driver Inoperative
22 Signal Circuit Shorted
23 ALD Reception Error
24 Coil Open
25 Zone Power Off
26 Power Cycling
27 Short Circuit
28 Open Circuit
29 Voltage Low
30 Zone Power Loss
31 Loop Node