|
| Page 21 of 22 |
|
|
|
|
|
|
|
|
|
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 | The FieldServer got a recognized |
|
|
|
|
|
|
| ||||||||||||
Port<%d> | Node<%u> | message on this particular port, Node, | To capture this data, add a new Map | |||||||||||||||||
Loop<%d> |
|
| loop, Address_Type and Address but | Descriptor with the required parameters. | ||||||||||||||||
Data_Type<%s> |
| did not find a defined Map Descriptor. |
|
|
|
|
|
|
| |||||||||||
Address<%d> |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |||
|
|
|
|
|
|
|
|
|
|
|
| |||||||||
|
|
|
| This driver keeps track of all |
|
|
|
|
|
|
| |||||||||
|
|
|
| memory locations per Map Descriptor. | If the error occurs during installation or | |||||||||||||||
#2 | Err. Reset/Normal | When the track queue is full, the oldest | testing, it | can be ignored. | If the error | |||||||||||||||
offset is overwritten with the latest | occurs during field operation, configure the | |||||||||||||||||||
queue<%d> | full | on | ||||||||||||||||||
one. | This could | be | a problem | on | Map | Descriptor | with | required | address | |||||||||||
MD<%s> |
|
| ||||||||||||||||||
|
| System_Reset and System_Normal | ranges only and keep the Map Descriptor | |||||||||||||||||
|
|
|
| |||||||||||||||||
|
|
|
| where memory locations get cleared as | length smaller than the queue length. | |||||||||||||||
|
|
|
| per this queue. |
|
|
|
|
|
|
|
|
|
|
|
|
| |||
|
|
|
|
|
|
|
|
|
|
| ||||||||||
#3 | FYI. Event<%s> | not | The |
| FieldServer | received |
| an | If the error occurs continuously, check that | |||||||||||
unrecognized | event | or | corrupted | connection | parameters | match | with panel | |||||||||||||
Supported. |
|
| ||||||||||||||||||
|
| message. |
|
|
|
|
|
| port settings. |
|
|
|
| |||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
| |||||||
|
|
|
|
|
|
|
|
|
|
|
| |||||||||
#4 Err. Unknown Node | The | FieldServer | received | a | Node | If this | error occurs continuously | and you | ||||||||||||
Trouble | event |
| not | listed | under | need | this | new | trouble status, | contact | ||||||||||
Trouble <%s> |
|
| ||||||||||||||||||
| Appendix A.2 or a corrupted message. | FieldServer. |
|
|
|
| ||||||||||||||
|
|
|
|
|
|
|
| |||||||||||||
|
|
|
|
|
|
|
|
|
|
|
| |||||||||
|
|
|
| The FieldServer received a message |
|
|
|
|
|
|
| |||||||||
#5 | Err. Unknown | OFF | that | a | Node | either | connected | or |
|
|
|
|
|
|
| |||||
disconnected from the network, but no | Call Tech support. |
|
|
|
| |||||||||||||||
NETWORK Node <%s> |
|
|
|
| ||||||||||||||||
Node number was received - it is likely |
|
|
|
|
|
|
| |||||||||||||
|
|
|
|
|
|
|
|
|
|
| ||||||||||
|
|
|
| that the message was corrupted |
|
|
|
|
|
|
|
|
| |||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408)