Filter
Top Products
FS-8700-105_National_Time_and_Signal_FACP Manual Page 20 of 25
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
Message Interpretation and Corrective Action
Port_Type the Map Descriptor in the configuration CSV file, but the
parameter value has not been specified.
∗
NATS:#15 Err. <%s> file not
found.
NATS:#16a Err. Diagnostic 1
NATS:#16b Err. Diagnostic 2
This message is normally only printed when the driver is
being tested for QA purposes. If it is printed during
normal operation, take a log and call Technical support.
NATS:#17 Err. Driver cannot
poll. Cache MD Ignored.
FieldServer’s provide ‘write-through-read’ technology but
it has been defeated for this driver because this driver
cannot write to the FACP panel as it is a passive client
driver. When you see this message you know that some
other node (or possibly a ruinet user) has poked a value
into one of the Data Arrays used by the driver. When this
occurs the FieldServer attempts to write the new value to
the FACP. This is not permitted and the message is
printed. You can review the configuration checking to see
if any Data Array areas used by the different drivers
overlap. Or you can check to see that the other
nodes/connections in the configuration are not writing to
the Data Array being used to store panel data.
NATS:#18 Err. Parse: Trouble
String Unknown.
The trouble string in the message is contained in character
positions 28-36. The driver extracted a trouble string
from an incoming message and then compared the string
to a look-up table of trouble strings. There was no match.
Apply one of the following:
Determine if this is a legitimate trouble string. Is the rest
of the message corrupt or valid? Do other messages have
the same trouble string? Does the equipment vendor
confirm that this is a new trouble string? If it is a
legitimate trouble string and the driver does not recognize
it then you need to add the string to the driver’s look-up
table. More information is provided in Appendix A.1 .
Once you have added the new string to the configuration,
reset the FieldServer for the changes to take effect. Now
generate the same event again. This time there should be
no message.
The case sensitivity of the look-up can be controlled.
More information is provided in Appendix A.3
If neither of the previous strategies work and you are sure
this isn’t a rare corrupt message then take a log and call
tech Support.