FieldServer FS-8704-06 - Manual (Page 40)

FS-8704-06 BACnet IP Driver Manual Page 40 of 57
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. Debugging a BACnet connection

If duplicate Object_Instances are configured in the FieldServer, the second call of the Instance will overwrite
the first one. This may cause a BACnet Object to be “lost.”

If the Node Name configured on the BACnet Server Side of the configuration is not being indicated as the
Device Name on the BACnet SCADA system, then the FieldServer is not communicating with the SCADA
system. If the Device Object's name is being indicated, but the Present_Value shows question marks, then it is
likely that the Client side of the FieldServer is not communicating.

Some of the BACnet IP features result in the creation of files (priarray.ini; desc.ini; alarms.ini) on the
FieldServer. Sometimes updates of firmware can result in these files becoming outdated. Deleting these files
will restore configuration defaults and may assist with configuration errors.

Extra memory is required to store Map Descriptors that have the active/inactive text parameters specified. If
the defaults are appropriate, do not specify these parameters. This will save memory and allow more Map
Descriptors to be created

When using the FieldServer as a BACnet Server, ensure the FieldServer’s Subnet Mask matches the Subnet
Mask of the BACnet Client. Otherwise, communications are very slow and eventually stop altogether.
Appendix B.2. COV Configuration

COV only works for BACnet Map Descriptors with length set to 1. If length is not specified, then it defaults to 1,
so this is only a problem where length has been specified as greater than 1.
Appendix B.3. BACnet Specific Statistics
Stat Description Resolution
Link Control
A “who-is” link control message was
send or received.
It is normal to receive a few link control
messages. If the number is higher than the
transmit/receive messages, however, there may
be a problem with lost communications.
Unsupported
Properties A request for an unsupported property
was received
This is not an error. BACnet clients often poll all
properties of a particular object to determine
which properties are supported.
Segmentation
Not Supported
Data was requested but the response
would have exceeded the maximum size
of the APDU and could not be sent using
an un-segmented message.
This is not an error - the BACnet client will use a
different method to read data from the
FieldServer.
Sequence Error
Invoke ID of a reply did not match the
Invoke ID of the poll. You should not see this message. It normally
indicates a configuration error.
Write Access
Denied
A write to an object was denied.
This typically happens when trying to write to an
Input Object that is not Out-Of-Service. It is not
possible to write to Input Objects.
Exception Errors
A BACnet Service was denied because it
is not supported This may be a problem on the Client system.
Consult the PIC statement for supported services.