All Units
Introduction
Core Concepts
Data Connectivity
Dashboard Visualization
Clients
Data Historian
Asset Organization
Alarming & Notifications
Helper Modules
Security
Cloud & IoT
Reporting
Automated Transactions
Business Intelligence
Project Management
Fault Detection & Diagnostics
SPC/SQC Analysis
Energy Analysis
Data Connectivity
Total: ~28 min
Subscribing to JSON Data in an MQTT Broker
Devices may publish data to MQTT brokers in a JSON format. We will explain the format and the required settings in the ICONICS software platform to subscribe to the broker and to turn data into information.
Subscribing to JSON Data in IoT Hub
Devices may publish data to the Azure IoTHub in a JSON format. We will explain the format and the required settings in the ICONICS software platform to subscribe to the hub and to turn data into information.
Subscribing to MQTT Sparkplug Data
Devices may natively support the Sparkplug-B messaging structure. We will explain the Sparkplug-B standard and the required settings in the ICONICS software platform to subscribe to the broker and to automatically discover connected devices.
Subscribing to OPC UA Pub Sub Data
Devices may natively support the OPC UA messaging structure. We will explain the OPC UA PUB SUB standard and the required settings in the ICONICS software platform to subscribe to the broker and to automatically discover connected devices.
Publishing JSON Data to an MQTT Broker
The ICONICS Software platform may be configured to publish data to an MQTT broker. We will explain the possible messaging formats and the required settings to automatically publish data to the broker.
Publishing JSON Data to an AMQP Broker
The ICONICS Software platform may be configured to publish data using the AMQP protocol. We will explain the possible messaging formats, the settings in Microsoft Azure and the ICONICS Workbench.
Options for Publishing via REST connectivity
The ICONICS Software platform may be configured to query data from web services via RESTful APIs and may be configured to publish data to custom web service end points. The 3rd party software developer would implement the appropriate processing of the received data.
English
Czech
German
French
Italian
Japanese
Polish