Table of Contents
Advertisement
FS-8704-06 BACnet IP Driver Manual
Appendix C. Troubleshooting Tips
Appendix C.1.
If duplicate object instances are accidentally 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 "Virtual_BCU_..." is not being indicated as the device description for the FieldServer on the
•
BACnet SCADA system, then the FieldServer is not communicating with the SCADA system. If
the Present_Value's name is being indicated, but the Present_Value shows question marks, then
it is most likely that the Client side of the FieldServer is not communicating.
Polling BACnet addresses that are not configured for Liebert systems may cause the connection
•
to fail in older versions of Liebert. Please contact your Liebert supplier for more information.
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.
memory and allow more Map Descriptors to be created
McQuay Units are shipped with a default Device instance of the last 6 digits of the McQuay
•
Serial number.
Trane Specific Tips
When new points are added to the FieldServer it is important to restart Summit Workstation or
•
BCU, otherwise these new points may not be seen by the FieldServer.
Disconnect the FieldServer from the BACnet network when transferring images to the BCU.
•
Appendix C.2.
Stat
Link Control
Unsupported
Properties
Segmentation
Not Supported
Sequence Error
Write Access
Denied
Exception
Errors
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
Debugging a BACnet connection
BACnet Specific Statistics
Description
A "who-is" link control message
was send or received.
A request for an unsupported
property was received
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.
Invoke ID of a reply did not match
the Invoke ID of the poll.
A write to an object was denied.
A BACnet Service was denied
because it is not supported
Resolution
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..
This is not an error. BACnet clients often
poll all properties of a particular object to
determine which properties are supported.
This is not an error - the BACnet client will
use a different method to read data from
the FieldServer.
You should not see this message. It
normally indicates a configuration error.
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.
This may be a problem on the Client
system. Consult the PIC statement to
determine what services are supported.
Page 21 of 24
This will save
Advertisement
Table of Contents
