Steve Karg
4326128e72
* Refactored and secured BACnetActionCommand codec into bacaction.c module for command object and added to bacapp module encode/decode with define for enabling and pseudo application tag for internal use. * Simplified bacapp_data_len() and moved into bacdcode module as bacnet_enclosed_data_len() function. * Secured ReadProperty-REQUEST and -ACK decoding. * Removed deprecated Keylist_Key() functions from usage. * Removed pseudo application datatypes from bacapp_data_decode() which only uses primitive application tag encoded values. * Defined INT_MAX when it is not already defined by compiler or libc. * Deprecated bacapp_decode_application_data_len() and bacapp_decode_context_data_len() as they are no longer used in any code in the library. * Added BACnetScale to bacapp module. Improved complex property value decoding. Refactored bacapp_decode_known_property() function. * Refactored and improved the bacapp_snprintf() function for printing EPICS. * Fixed Lighting Output WriteProperty to handle known property decoding.
BACnet MS/TP on Atmel XMEGA-A3BU XPLAINED evaluation board. An RS-485 add-on board (daughterboard, shield) was designed to handle the RS-485 interface and some LEDs. See rs485-shield/ folder for EAGLE CAD design files. Use the Configuration "Debug-XPLAINED" and not in "Debug" or "Release". "CONF_BOARD_ENABLE_RS485_XPLAINED" is defined and used in led.c, rs485.c, and main.c for specific board I/O. When it is not defined, the I/O is either removed (i.e. led.c, main.c) or altered (rs485.c). There are other defines in the "Debug-XPLAINED" Configuration which include other parts of the XPLAINED platform code. For your own board, you could just change rs485.c, main.c, and led.c to use the I/O that you want to use, and not worry about the "CONF_BOARD_ENABLE_RS485_XPLAINED". Or you can leave the "CONF_BOARD_ENABLE_RS485_XPLAINED" in the files so that you can always test on the XPLAINED platform with Debug-XPLAINED, and use "Debug" or "Release" for your project.