In my previous blog, we learned how to get started with the Azure IoT Edge module named OPC Publisher.
This module makes it possible to extract data from a ‘local’ OPC-UA server and to expose this data to the Azure IoT Hub. The data is sent using the routing feature within Azure IoT Edge so before we sent the data to the cloud, we first can have an insight in the actual data, take actions locally and transform the data.
But the OPC Publisher connects to the OPC-UA server based on local settings. Here is the configuration, taken from my c:\iiot\pn.json file:
"EndpointUrl": "opc.tcp://[IP address]:53530/OPCUA/SimulationServer",
These settings are ‘hardcoded’, the file is on the file system, not in Docker.
Can we change these settings remotely, using the cloud?
Doorgaan met het lezen van “Managing nodes from the cloud in the OPC-UA Publisher Edge”
OPC-UA brings the promise of secure and platform independent M2M communication:
“The OPC Unified Architecture (UA), released in 2008, is a platform-independent service-oriented architecture that integrates all the functionality of the individual OPC Classic specifications into one extensible framework.”
Microsoft invests heavily in OPC-UA by providing several solutions, eg.:
And most of it is open-source!
But it’s hard to get started, what do you need to get data from an OPC-UA Server into the cloud using IoT Edge?
Here is a quick start by using the UPC UA Publisher module.
Doorgaan met het lezen van “Getting started with OPC-UA on Azure IoT Edge”
Microsoft has introduced the possibility to store data at the edge with Azure Blob Storage on IoT Edge.
It is currently in preview. At this moment, that latest version is mcr.microsoft.com/azure-blob-storage:1.0.1-linux-amd64.
Update 2019-08-21: This IoT Edge module is now made generally available.
This local blob storage is another way to persist data locally on the Edge.
Let’s see how we can use this in our projects.
Doorgaan met het lezen van “Introducing Blob storage in Azure IoT on the Edge”