Connections Overview


Overview

Connections can be added to the platform through API, FTP, or direct cell or radio network communication, and can be seen in the Network Page.

This article will cover the following topics:

Connection Types

iTwin IoT Connections can generally be grouped into two categories, file transfer-based and telemetry-based.

File Transfer Connections are typically set up and configured in other software programs. The Connection is then established, and data is transferred from the external software into the iTwin IoT platform, automatically populating sensors. Examples of such connections include Geomos Leica and Spider, Move Solutions sensors, Viotel sensors, Worldsensing sensors, and Kinemetrics Etna2 Accelerographs

Telemetry-based Connections are added directly to the application. These Connections can be further divided into Gateways, which are responsible for aggregation and transmission of data to the iTwin IoT cloud, and Endpoints, which aggregate and then transmit data to Gateways. Examples of Gateway Connections include Worldsensing Threads and Worldsensing G6 Gateways. Examples of Endpoint Connections include Sensemetrics Strands and Geokon Geonets.

Connection Status

The status indicators are located next to the connections in the Connectivity Module

Note: In some cases, API or FTP connection color status may be misleading. Best practice is to verify connection status of these connections by looking at the sensors "Last:" timestamp on the right side of the Connectivity page.

Connection Functions

Connection functions are located either next to the connection or at the top of the connection module.

Please check the proper sections for more information about specific connections such as Threads, Strands, and third-party hardware