| Key | Issue Type | Summary | Resolution | Note |
|---|---|---|---|---|
| BACN-811 | Improvement | fix camel-case in package.manifest InsertionPathBACNet elements |
Fixed | |
| BACN-797 | Improvement | update devices to needs of BACstack 25.1.2.1 |
Fixed | |
| BACN-793 | Improvement | remove not referenced BACnet library after update device |
Cannot Reproduce | |
| BACN-790 | Improvement | create workaround for BACstack (2) - problem in initialization of BitString with bitCount = 0 |
Cannot Reproduce | [[GENERAL]] Solved with CDS-84809 BACnet: BACstack - update to BACstack V25.1.2.1 |
| BACN-789 | Improvement | adapt to addenda bv, ca, cc, cd, ce and cf (of ANSI/ASHRAE Standard 135-2020) |
Fixed | |
| BACN-787 | Improvement | update to BACstack V24.1.33.1 |
Fixed | |
| BACN-786 | Improvement | fix Libraries Sources / Examples path in package |
Fixed | |
| BACN-784 | Improvement | fix log messages regarding EVT_ names |
Cannot Reproduce | |
| BACN-781 | Improvement | BACnet-Plugin: allow EDE-import to choose BACnet major version 1 vs. 2 |
Fixed | |
| BACN-780 | Improvement | add API to remaining object types |
Fixed | |
| BACN-779 | Improvement | modify property API to use subrange types where needed |
Fixed | |
| BACN-778 | Improvement | bringup Audit Reporter |
Cannot Reproduce | [[GENERAL]] Solved with CDS-84809 BACnet: BACstack - update to BACstack V25.1.2.1 |
| BACN-777 | Improvement | bringup Network Port |
Fixed | |
| BACN-776 | Improvement | BACnet-Plugin: implement update-device to new devdescs |
Fixed | |
| BACN-775 | Improvement | BACnet-Plugin: re-activate Plugin consistency-checks for new devdescs |
Fixed | |
| BACN-773 | Improvement | modify devdesc property defaults to avoid initial "InAlarm" / "Fault" state |
Fixed | |
| BACN-674 | Epic | move up to BACnet protocol revision 25 |
Fixed | [[GENERAL]] CODESYS BACnet 2.0.0.0 supports new functionality standardized in BACnet standard ASHRAE 135-2020 and BACnet "protocol revision 25". [[KNOWN_LIMITATIONS]] Regarding conformance test and BACnet certification of a "protocol revision 25" device there are some constraints in conjunction with CODESYS Runtime (CmpBACnet2) 3.5.19.x, related to bugs in the BACnet-stack (V25.1.5.1) integrated within CmpBACnet2: - Network Port object type: test case 2.1.2 - 7.1.2 will fail because of CDS-87288 - Global Group object type: test cases 3.36.3 - 7.3.2.13.1 / 3.36.3 - 7.3.2.13.2 will fail because of CDS-87207 which both are fixed as with CODESYS Runtime (CmpBACnet2) 3.5.20.0 (BACstack V25.1.38.1). So if a "protocol revision 25" device is going to use this functionality, it will not pass conformance test and BACnet certification without using CODESYS Runtime (CmpBACnet2) 3.5.20.0 instead minimum required CODESYS Runtime (CmpBACnet2) 3.5.19.0. Regarding application functionality of a "protocol revision 25" device there is a constraint in conjunction with CODESYS Runtime (CmpBACnet2) 3.5.19.x, related to a bug in the BACnet-stack (V25.1.5.1) integrated within CmpBACnet2: - Access Door object type doesn't get operational if Audit_Priority_Filter property is used (not configured to be non-existent) because of CDS-87132 which is fixed as with CODESYS Runtime (CmpBACnet2) 3.5.20.0. Also there had been some minor bugs in the BACnet-stack which had been fixed within CODESYS Runtime (CmpBACnet2) > 3.5.19.0. So in general it is recommended to use CODESYS Runtime (CmpBACnet2) 3.5.20.0 to build a "protocol revision 25" BACnet device, nevertheless most of the application functionality is going to work with the minimum required CODESYS Runtime (CmpBACnet2) 3.5.19.0. |
| BACN-207 | Improvement | device description parameters is using std:-types instead of appropriate BACnet-types |
Won't Fix | [[GENERAL]] Fixed with other topics anyway - not needed anymore. |