Filter
Top Products
FS-8700-130 Notifier NCA2/NFS-3030 Manual Page 21 of 22
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: support@fieldserver.com
Appendix C. Error Messages
Most error messages are associated with errors in parsing an incoming message from the Notifier panel. The most
likely cause is a mismatch in expected message format. The driver will flag one of the following error messages
and continue. In most cases the message currently being processed by the driver will also be printed so that any
problems can be easily diagnosed.
Two screens ‘System Errors’ and ‘Driver Messages’ exist for displaying errors.
The System Error Screen displays the error number and the Driver messages screen displays the error number,
description and the message received from the NCA/NCA2 Panel.
In debug mode the System Error screen will also include Driver messages.
The following Error Messages appear upon the ‘System Errors’ Screen
• %d means numeric number
• %s means string
Messages number 1, 3, 4 and 5 will be displayed just once if generated after rebooting or power cycling the
FieldServer.
Error Description Action
#1 FYI. Incoming data is
being abandoned on
Port<%d> Node<%u>
Loop<%d>
Data_Type<%s>
Address<%d>
The FieldServer got a recognized
message on this particular port, Node,
loop, Address_Type and Address but
did not find a defined Map Descriptor.
To capture this data,
add a new Map
Descriptor with the required parameters.
#2 Err. Reset/Normal
que
ue<%d> full on
MD<%s>
This driver keeps track of all non-zero
memory locations per Map Descriptor.
When the track queue is full, the oldest
offset is overwritten with the latest
one.
This could be a problem on
System_Reset and System_Normal
where memory locations get cleared as
per this queue.
If the error occurs during installation or
testing, it can be ignored. If the error
occurs during field operation, configure the
Map Descriptor with required address
ranges only and keep the Map Descriptor
length smaller than the queue length.
#3 FYI. Event<%s> not
Supported.
The FieldServer received an
unrecognized event or corrupted
message.
If the error occurs continuously, check that
connection parameters match with panel
port settings.
#4 Err. Unknown Node
Trouble <%s>
The FieldServer received a Node
Trouble event not
listed under
Appendix A.2 or a corrupted message.
If this error occurs continuously and you
need this new trouble status, contact
FieldServer.
#5 Err. Unknown OFF
NETWORK Node <%s>
The FieldServer received a message
that a Node either connected or
disconnected from the network, but no
Node number was received - it is likely
that the message was corrupted
Call Tech support.