Why does the BACnet "Upload/Merge" not work on very busy IP networks?

FAQ #101417

Firmware versions before the version 1.10.51 were not supporting retries during the "Upload/Merge" process of the BACnet configurator. In case a telegram got lost during upload of the BACnet configuration (from the PCD to the PC) the transfer was been aborted.


During an Upload (for the function "Upload/Merge" of the BACnet configurator) all of the sudden the transfer of the configuration stops. This phenomenon is observed when a telegram is lost. This telegram loss is random, dependent on the network load.

Firmware versions before the version 1.10.51 were expecting a communication without telegram losses. In case a telegram was lost (due to network problems) the transfer was interrupted by the PCD firmware. Because of the interruption the BACnet firmware was not notified, but it remained in a state of waiting for the completion of the upload process.

The firmware version 1.10.51 (for the PCD3 or the PCD2.M5) together with the BACnet firmware 1.10.50 are more robust and can cope with telegram losses during the upload of the BACnet configuration. Please update the firmware of your PCD and the one on your PCD7.R56x to the mentioned (or later) firmware versions.

Please note that the firmware version of both, he PCD and the BACnet module must be updated.





Local FAQ Deutschland / Add on Tools

Communication / BACnet

PG5 1.x / Add on Tools

Last update: 30.05.2015 04:27

First release: 06.05.2010 17:12

Views: 41055

The requested software / document is no longer marketed by Saia-Burgess Controls AG and without technical support. It is an older software version which can be operated only on certain now no longer commercially available products.