> For the complete documentation index, see [llms.txt](https://enless.gitbook.io/centre-aide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enless.gitbook.io/centre-aide/ressources/ressources-en/lora-easy-receivers/firmware-update/changelogs/rx-bacnet-500-312.md). # RX BACNET 500-312 {% updates format="full" %} {% update date="2025-12-25" tags="ameliorations,correction-de-bugs" %} ## Version 2.02.8932 {% hint style="warning" %} This firmware is only compatible with receivers whose serial number starts with 413. {% endhint %} Changes: * Improved MSTP communication, especially with Tridium JACE controllers. * Optimization of the BACnet stack for better stability. * Display of a clear pop-up restart notification when the MSTP address is changed. * Improved consistency of configuration export/import. * Removal of the 24-hour interval from the periodicity drop-down list. * Bug fixes and stability improvements. File name\ [Enless\_LoRaBacRx\_EN413\_V2.02.8932\_NA\_NA\_NA\_0.upg](/centre-aide/ressources/ressources-en/lora-easy-receivers/firmware-update/firmware-files.md) {% endupdate %} {% update date="2025-07-29" tags="ameliorations,nouvelles-fonctionnalites,correction-de-bugs" %} ## Version 2.02.8922 {% hint style="warning" %} This firmware is only compatible with receivers whose serial number starts with 413. {% endhint %} Changes: * Support for the new transmitters in the Room Control range:\ o 600-050\ o 600-051\ o 600-052\ o 600-053\ o 600-062\ o 600-065 * Improvements to the firmware update process. * Evolution of the BACnet stack:\ o Development and integration of new properties on BACnet objects supported by the receiver to ensure compliance with the BACnet standard.\ o Implementation of new error, reject, and abort codes on the receiver to ensure compliance with the BACnet standard. * Removal of the "BBMD+MSTP" mode from the RX Config page. * Correction of the upper limit of the MSTP address value range in device and object modes. * Changes made to the receiver's TX Config page:\ o Updated list of transmitter names and labels.\ o Updated list of transmission periodicities.\ o Default activation of the "Update Config" feature when adding and configuring transmitters.\ o Correction of the display of negative temperature thresholds. * Bug fixes and stability improvements. File name\ Enless\_LoRaBacRx\_EN413\_V2.02.8922\_NA\_NA\_NA\_0.upg {% endupdate %} {% update date="2024-11-04" tags="ameliorations,correction-de-bugs" %} ## Version 2.02.8904 {% hint style="warning" %} This firmware is only compatible with receivers whose serial number starts with 413. {% endhint %} Changes: * Improved compatibility with Siemens controllers. * Bug fixes and stability improvements. File name: \ Enless\_LoRaBacRx\_EN413\_V2.02.8804\_NA\_NA\_NA\_0.upg {% endupdate %} {% update date="2024-07-31" tags="ameliorations,correction-de-bugs" %} ## Version 2.02.8896 {% hint style="warning" %} This firmware is only compatible with receivers whose serial number starts with 413. {% endhint %} Changes: * Addition of pop-up messages for settings that require a restart to take effect:\ o Serial settings: baud rate, parity, data bits, and stop bits\ o IP address settings: IP, gateway, and subnet\ o Changes to DHCP mode\ o Changes to BACnet mode\ o Changes to the UDP port • Bug fixes and stability improvements. File name: \ Enless\_LoRaBacRx\_EN413\_V2.02.8896\_NA\_NA\_NA\_0.upg {% endupdate %} {% update date="2024-05-28" tags="ameliorations,correction-de-bugs" %} ## Version 2.02.8890 {% hint style="warning" %} This firmware is only compatible with receivers whose serial number starts with 413. {% endhint %} Changes: * Improved compatibility with the Distech APEX controller. * Addition of a "Clear all" button on the TX CONFIG page. * Unconfigured transmitters will not be displayed on the network page. * Addition of an information pop-up window "Update config". * Change of relay object type to binary outputs. * Bug fixes and stability improvements. File name: \ Enless\_LoRaBacRx\_EN413\_V2.02.8890\_NA\_NA\_NA\_0.upg {% endupdate %} {% update date="2023-09-28" tags="ameliorations" %} ## Version 2.02.8875 {% hint style="warning" %} This firmware is only compatible with receivers whose serial number starts with 413. {% endhint %} Changes: * The firmware version of transmitters can now exceed 16 (the previous limit was 15). This affects the red/green status on the TX Config page. * The BACnet vendor ID is set to 1361. * The RX-BACnet Binary\_Input object is now updated for Contact transmitters. File name: \ Enless\_LoRaBacRx\_EN413\_V2.2.8875\_NA\_NA\_NA\_0.upg {% endupdate %} {% update date="2023-09-01" tags="ameliorations,correction-de-bugs,nouvelles-fonctionnalites" %} ## Version 2.02.8872 {% hint style="warning" %} This firmware is only compatible with receivers whose serial number starts with 413. {% endhint %} Changes: * First public release. * Text and translation adjustments. * Bug fixes and stability improvements. * Addition of anti-bounce function for pulse transmitters (works only with transmitters using firmware version 11 or higher). * Addition of TX IO support. File name: \ Enless\_LoRaBacRx\_EN413\_V2.2.8872\_NA\_NA\_NA\_0.upg {% endupdate %} {% endupdates %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://enless.gitbook.io/centre-aide/ressources/ressources-en/lora-easy-receivers/firmware-update/changelogs/rx-bacnet-500-312.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.