Doc¶
- Application Programming Interface
- BACnet objects
- property access and content data memory
- BACnetARRAY[] of vs. BACnetLIST of properties
- property type ANY
- application programming interface conventions for property access
- exceptions from property access naming conventions
- property access and memory (allocation / deallocation) - simple rule of thumb
- STRING / WSTRING exceptions from property access type consistency
- compile options to enable specific logging
- other compile options
- Introduction
- CODESYS BACnet2 - parts and pieces
- migration from CODESYS BACnet (protocol revision 14/15) to CODESYS BACnet2 (protocol revision 25)
- prerequisites for migration from CODESYS BACnet (protocol revision 14/15) to CODESYS BACnet2 (protocol revision 25)
- modifications of application code required by type changes of “event STRUCTs”
- modifications of application code required by API change regarding problematic simultaneous property access
- modifications of application code required by API changes done for consistency cleanup
- API differences between CODESYS BACnet up to version 1.7.*.* and CODESYS BACnet2
- recommended modifications of application code regarding “hooks” / “callbacks” event “event STRUCT” typenames and event-ID’s
- hint regarding BACnetARRAY[N] ordering
- CODESYS BACnet(1) vs. CODESYS BACnet2 artefact names and versions
- functionality of the parts