What are the differences between BACnet firmware 1.10.50 and 1.16.77?

FAQ #101598

 

Changes between BACnet firmware version 1.16.75 and 1.16.77 (January 2013)

• Correction for simultaneously COV and COV-P subscriptions to Output objects with Prio Array
  

Remark
Please note that the BACnet 1.16.77 is to be used together with the PCD firmware 1.16.69 (or a more recent 1.16.xx firmware) in order to work correctly.

---

Changes between BACnet firmware version 1.16.73 and 1.16.75 (November 2012)

• BACnet Properties were not correctly updated after a Restart of the PCD
  
• In some cases the PCD sent a Whois each 5 sec. without reason
  

Remark
Please note that the BACnet 1.16.75 is to be used together with the PCD firmware 1.16.69 (or a more recent 1.16.xx firmware) in order to work correctly.

---

Changes between BACnet firmware version 1.16.67 and 1.16.73 (August 2012)

• Media Update (Mapping) was too slow --> corrected
  
• Download over Ethernet was slow --> corrected
• Several corrections for the Priority Array and "Out of service" handling
• Update of "Program state" property was not working
• Trendlog Objects "Total record count" could be wrong
  

Remark
Please note that the BACnet 1.16.73 is to be used together with the PCD firmware 1.16.69 (or a more recent 1.16.xx firmware) in order to work correctly.

---

Changes between BACnet firmware version 1.16.64 and 1.16.67 (V9, May 2012)

• If there was an invalid BACnet trendlog buffer in the file system the BACnet stack did not start up
• The Binary Input Object was not work correctly if the Polarity was set to 1
• The COV-P on the program status of a program object was not working

Remark
Please note that the BACnet 1.16.67 is to be used together with the PCD firmware 1.16.57 (or a more recent 1.16.xx firmware) in order to work correctly.

---

Changes between BACnet firmware version 1.16.59 and 1.16.64 (V8, May 2012)

• The change of polariy of a BI object was not working in versions before 1.16.64
• Improved memory allocation method (with BACnet firmware 1.16.xx up to 1.16.64 the BACnet task could run out of memory if COV subscriptions were used)
• If a persistent value was written over BACnet, the property "Unsolicited COV" got lost and thus the COV-U was no longer configured on next power up 

Remark
Please note that the BACnet 1.16.64 is to be used together with the PCD firmware 1.16.57 (or a more recent 1.16.xx firmware) in order to work correctly.

---

Changes between BACnet firmware version 1.16.55 and 1.16.59 (V6, February 2012)

• The amount of memory used by BACnet (in relation to the maximum amount of memory available) is monitored on the PCD status page
• In case the "PCD input reference" is used and a persistent value has been stored over BACnet, the configuration could no longer be read on next power up, see FAQ 101712

Remark
Please note that the BACnet 1.16.59 is to be used together with the PCD firmware 1.16.57 (or a more recent 1.16.xx firmware) in order to work correctly.

---

Changes between BACnet firmware version 1.16.41 and 1.16.55 (V5, WSPCert certified, January 2012)

• The timezone format has been updated to be compatible with the format used by PG5 2.0. 
  The previously used format is still supported by the firmware
• In case the "PCD input reference" is used and a persistent value has been stored over BACnet, the configuration could no longer be read on next power up, see FAQ 101712

Remark
Please note that the BACnet 1.16.55 is to be used together with the PCD firmware 1.16.55 (or a more recent 1.16.xx firmware) in order to work correctly.

 

---

Changes between BACnet firmware version 1.14.26 and 1.16.41

 

(V4, July 2011)

• Conforms to BACnet Standard 2008 (rev. 5)
• BACnet BitStrings can now be mapped to Flag arrays:
  
• Added "PCD Input Reference" in order to improve Out-of-Service behaviour:
  The "PCD input reference" is copied to the Present Value as long as the Out-of-Service is false; if it is true, the Present Value can be written over BACnet and this value will be copied to the PCD media linked to the Present Value.
• Corrected the performance issues which were present in firmware 1.14.26
• In some cases (depending on the size of the project) it was not possible to download a project (and a NAK response was returned)
• With a specific project a Bus Error could have happened with BACnet firmware 1.10.62.

For more information about the changes, please refer to the online help of the BACnet Configurator distributed with PG5 2.0.200 or later.

---

Changes between BACnet firmware version 1.10.50 and 1.14.26 (April 2011)

• Improved the speed of searching if the configuration has a dynamically configured program object or not.
• Loop object has been enhanced so that it can be specified whether the built-in PID calculation algorithm or the DDC Suite FBox PID calculation algorithm shall be used.
• COVs were sporadically not generated in a system with high load and many IOs changing at the same time. 

Remark
Please note that the BACnet 1.16.41 is to be used together with the PCD firmware 1.16.27 (or a more recent 1.16.xx firmware) in order to work correctly.