BACnet Expose - SEAL Script

[StefanLundin]

Introducing the SEAL Script: BACnet Expose

We are excited to share the SEAL Script named BACnet Expose, a collaborative effort by script experts from five countries within our community. Initially created in 2021 and updated in May 2022, this script automates the process of exposing EBO applications on BACnet, addressing the need for open systems and reducing manual, error-prone operations.

Key Features:

• Automation: Converts EBO applications to BACnet, moving functionality and bindings to corresponding BACnet objects.
• Compatibility: Supports various object types like IO, values, and schedules, with some limitations (e.g., alarms, trend logs).
• Flexibility: Designed to handle different standards and structures across countries, though some manual adjustments may be needed.

Limitations:

• Does not support entries on time schedules and calendars.
• Does not support alarms.
• Does not support trend logs.

Important Note: This script is a community-driven project and is not a guaranteed fully functional script. It is not shared as a standard script in the tool due to its collaborative nature and ongoing development. We encourage users to contribute and help improve the script further.

Disclaimer: This script is invasive and will make significant changes to the EBO database. It is therefore critical to make a BACKUP of the EBO server before running this script. It is also strongly recommended to do a dry run to evaluate if changes to EBO can be made to simplify the conversion to BACnet objects.

Usage:

• The script performs a full conversion, creating BACnet objects and moving bindings and contents from EBO objects.
• A dry-run feature is available to report convertible objects before making changes.
• Generates a report on conversion failures for manual adjustments.

For detailed information, please refer to the attached script and manual.

Shoutout: A huge shoutout to the users Morten Enger, Christian Granberg, Enzo Dino Di Gregorio, Johnny Carlsen, Magnus Kennedy, Marcus Gilbert, Mikael Bodereau, and Morten Bjørndal for their incredible contributions to this project!

[Richard_Stark]

Can this script be modified easily to expose all of the same object types to BACnet without the binds translating and keeping them the same on the EBO side?

[MortenEnger]

If you are thinking like checking a box on EBO objects to expose them on BACnet without moving the objects or bind between BACnet and EBO object the answer is no.

This is sadly not supported by EBO.

[Richard_Stark]

I am thinking just mirroring the objects in the BACnet application folder to expose them to a third party or similar, but not moving all the bindings from the EBO objects to the BACnet objects (scripts bindings, etc). Effectively the EBO side stays the same, but a bind is added from the EBO object to the BACnet object in the BACnet application folder. 

[MortenEnger]

If you just want a read-only mirrored copy on BACnet then a SEAL Script could generate those objects and make a one-way binding, but still limited to only a few kind of objects that can support this like variables.

[Richard_Stark]

Excellent. Yes that is fine. I am just thinking of a nice quick way to expose basic variables.