BACnet Knowledgebase

Setting up a BACnet Studio project

Abstract

Follow these steps and start building your i4BACnet project using the i4SCADA Studio application.

The purpose of this tutorial is to exemplify how to set up a BACnet Studio project.

  1. Configure the BACnet Connector as described in article Connector Configuration 

  2. As soon as BACnet Connector has been configured, proceed with setting up Alarm Groups, Alarm Types, Alarm Conditions and Alarms, under Alarming section of Studio. More details upon i4SCADA Alarms configuration may be found in this article.

    Alarming_section.jpg

    Alarming section of Studio

  3. Right-click on Alarm Groups node in the tree menu or inside the alarm groups view and select option New.  

    New_Alarm_Group.jpg

    New Alarm Group

  4. Provide name and description for the new Alarm Group, for all languages defined in the system (by default German and English). Translations may be added using the Group Details panel.

    Name_and_description_of_new_Alarm_Group.jpg

    Name and description of new Alarm Group

  5. To store the new Alarm Group click on the Save button. 

  6. Select the Alarm Types node and by means of right-click node, select option New

    New_Alarm_Type.jpg

    New Alarm Type

  7. Name your new alarm type and provide descriptions for all the languages defined in the system (by default German and English). The descriptions translations are added using the Type Details panel.

  8. Enable or disable the Automatic alarm acknowledgment for this type of alarms. If enabled, the alarms will be acknowledged by the system as they appear.

  9. To preserve the changes made for the new Alarm Type, click on button Save

    New_Alarm_Type.jpg

    Save new created Alarm Type

  10. Proceed with creation of Alarm Conditions under the respective node in Alarming tree menu, via right-click and selection of button New.

    aaa.jpg

    New Alarm Condition

  11. Provide Name for the new Alarm Condition

  12. Select the logical condition for triggering the alarm, under Criteria field

  13. Enter a Constant value that will be used in equating the state of the Criteria.

  14. Enter, if required by the selected Criteria, a Constant to value, that will be used in equating the state of range based Criteria.

  15. Select a Signal that will be used in equating the state of certain Criteria that requires another signal value for comparison.

  16. Preserve the changes made by clicking button Save

    Alarm_Condition_Details.jpg

    Alarm Condition Details

  17. Further on, click on the Alarms node in the tree menu or inside the alarm view and select New.

    New_Alarm.jpg

    New Alarm

  18. In the Signal Browser, select the signal that will monitored and will trigger the alarm if the conditions match.

    Signal_Browser.jpg

    Signal Browser

  19. The new alarm will have predefined settings applied. Use the Alarm Details panel to set up the alarm as required for your scenario. 

  20. Press button Save to store the new Alarm.

  21. Switch from Alarming to Logging section. More details upon Logging functionality may be found in this article.

  22. Right-click on the Log Conditions node in the tree menu or inside the log conditions view and select New.

    New_Log_Conditions.jpg

    New Log Conditions

  23. Fill in Name for the new Log Condition

  24. Under Log Conditions details fill in the Log Mode selecting from the drop-down list

  25. Depending on the selected Log Mode, Log Interval, Log Constant, Signal Value 2 and Report Interval may also be defined

  26. Store the changes by pressing button Save

    Log_Condition_details.jpg

    Log Condition details

  27. Right-click on the Logging node in the tree menu or inside the logging view and select New.

    New_Logging.jpg

    New Logging

  28. In the Signal Browser, select the signal that will be logged using this definition.

    Signal_Browser_Logging.jpg

    Signal Browser

  29. Activate the new log so that it's taken into account by the i4SCADA Server.

  30. Name your new log using the Log Tag field.

  31. Enter the number of days to keep the log before purging, using the Max Days option. The first logged value reaching this specified age will be deleted when a new value is stored.

  32. Enter the maximum number of logs to be stored, using the Max Numbers option. Once this number is reached, the oldest logged value will be deleted when a new one is stored.

  33. Enter the name of the database where the logs will be stored, using the Log Database field. If no database is specified, the logs will be stored in the default project database, inside the dedicated table.

  34. Enable the IoT option if this log must be accessed using the IoT Hub.

  35. Preserve the changes by clicking button Save.

    Logging_details.jpg

    Logging details

  36. Switch to Translations section in order to define any necessary translations. More details upon project translations may be found in this article.

    Translations_tree_menu.jpg

    Translations tree menu

  37. Further project settings may be organized under the Settings section. Read more about the potential settings, in the i4SCADA documentation under: i4SCADA Studio Settings area and i4SCADA Studio User Manager.

After following up and organizing all above indicated steps, your Studio Project is prepared for a proper BACnet Connector usage.