Introduction

The real-time connectors are a set of components which enables Niagara stations to exchange data in real-time to external services (Cloud IoT Platforms, Databases, APIs... ).

There are many features available through the real-time connectors. A third party can:

• Read / Write points
• Read / Write schedules
• Read / Acknowledge alarms
• Read historical data on demand

Connector component

A real-time connector is a component to install in the Btib Service in the appropriate folder. Example with Mongo:

A connector hosts the credentials and defines the general parameters (that you can explore later)

Container / Datapoint

Data points are not transferred directly to the database or cloud platform. They are grouped by a container which can be a device, a Folder, any component in Niagara.

If we take a very simple example with a folder containing two points:

One extension, called a "DeviceExt" must be added from the palette into the data points container. (An InfoSource will popup automatically to provide a unique id to the container)

The DeviceExt is used to define which connector it should be sending data to (You can use several connector of the same type in the station)

Then, we add a PointExt to each data point (an InfoSource is also added automatically to generate a unique id to the point).

The PointExt defines the behaviour for the point changes: when it should send messages to the cloud, there are several options.

On of the most important property is the DeviceQuery. This is where we indicate where is the container (the PointFolder in our case). It can accept absolute Ord, relative Ord, SFormat...

In our example, we want to reach the grand parent of the PointExt (the IconFolder).

Now every time a changes occurs at the point level, either its status or its value, a message will be sent to the database/platform.

A third party can also change data point value.

Some undeniable advantages:

• It doesn't require any additional points in Tridium's license.
• It works seamlessly for reading and writing (no other extension to add)
• DeviceExt and PointExt can be deployed easily on a Niagara station using Program Service or Macros
• Payload (content of a message) can be easily personalized

Deep dive in the documentation

Get started with a specific connector

• Get Started with IoTHub
• Get Started with AWS IoT
• Get started with MQTT and Niagara
• Get Started with Google IoT Core
• Get Started with MongoDb and Niagara