For the complete documentation index, see llms.txt. This page is also available as Markdown.

Connect devices with ABB BuildingPro

About this chapter

This chapter describes how to connect external devices to ABB BuildingPro and display data from these devices in ABB BuildingPro.

Procedure

Overview

The first step is to establish a communication connection between ABB BuildingPro and the devices to be connected. In Fig. 1, this is phase "B".

In the second step, the incoming raw data usually has to be decoded. This is because external devices send their transmitted data (payload) encoded or in some other unusable format.

In the third step, finally, the decoded data values are assigned via formats to the individual ↗ attributes of an asset.

The last two steps take place in phase C.

Details

Fig. 1 shows schematically the data flow from an external device to ABB BuildingPro.

Fig. 1 – Data flow from external devices to ABB BuildingPro

Phase A

Phase A takes place entirely outside ABB BuildingPro. In phase A, raw data from individual devices is sent to a server or broker. An example of such a server is ↗ TTN [External link]

The details, e.g. which transmission format is used, vary greatly depending on the manufacturer and device. Phase A is not part of ABB BuildingPro and is not explained in detail in this documentation. Consult the documentation for the external devices or server to learn more about this topic.

For the further steps in this document, it is assumed that you have access to correctly configured external devices and/or access to a server.

Phase B

In phase B, the actual connection of Eliona and the device data takes place. In this phase, a data connection is established between Eliona and the external devices.

Eliona accepts the following interfaces:

Click on a link to jump directly to the guide that describes how to establish a data connection via the corresponding interface.

Phase C

In phase C, the data is processed and made usable within Eliona.

  • The data sent by the external devices and received in Eliona is, in most cases, not directly readable. Depending on the manufacturer, this raw data is encoded or is in a format that cannot be used any further. Therefore, this raw data is Features decoded and converted into a human-readable .json format.

  • The decoded data is assigned to the individual attributes of an asset via ↗ formats of an asset.

Requirements

To connect external devices, the following requirements must be met:

Correctly configured external devices and servers

The devices to be connected must be correctly configured and must send data properly.

Servers and brokers must be correctly configured.

Existing access credentials for servers, brokers and other services

The access credentials for servers and brokers must be known.

Asset Templates

It is assumed that you have created correct asset templates. The asset template must have the necessary asset attributes

Assets

Assets must be created based on the asset template.

Last updated

Was this helpful?