- #KEPSERVEREX SIMULATED DEVICE EXAMPLE HOW TO#
- #KEPSERVEREX SIMULATED DEVICE EXAMPLE SOFTWARE#
- #KEPSERVEREX SIMULATED DEVICE EXAMPLE SERIES#
#KEPSERVEREX SIMULATED DEVICE EXAMPLE SERIES#
The Edge Telemetry Processor microservice is responsible for decoding OPC UA PubSub messages received by IoT Hub and provides the data to post processing Azure services like Azure Event Hubs, Azure Data Lake Storage or Azure Time Series Insights for further processing and visualization. It is also used to fail over publishing jobs from one OPC Publisher module to another. The Orchestrator microservice is an internal service responsible for load-balancing publishing jobs across OPC Publisher modules deployed in the same shop floor. It provides a HTTP REST interface to cloud applications. The OPC Publisher microservice is responsible for managing OPC Publisher module subscriptions to OPC UA assets. OPC Publisher Microservice and Orchestrator Microservice The OPC Twin microservice is responsible for accessing OPC UA assets via the OPC Twin edge module and provides a HTTP REST interface to cloud applications. It manages all OPC UA asset endpoints that are stored in the IoT Hub device registry. The Registry microservice is responsible for CRUD commands to the IoT Hub Device Registry as well as providing a HTTP REST interface for cloud applications. When it finds an asset, it queries the assets endpoints (including its security configuration) and registers an IoT Hub device in the IoT Hub Device Registry for each endpoint. The Discovery module runs on Azure IoT Edge and scans the shop floor network for OPC UA-enabled assets. The OPC Twin module runs on Azure IoT Edge and connects to OPC UA-enabled assets, browses their data model, reads and writes ad-hoc data, and calls methods on the asset. It can be configured from the cloud or locally via a configuration file. The OPC Publisher module runs on Azure IoT Edge and connects to OPC UA-enabled assets, reads data from them using OPC UA subscriptions, converts the resulting OPC UA “Data Changed Notifications” into OPC UA PubSub messages, and sends them to the cloud via IoT Edge. The following edge modules are part of the platform: We have also provided easy-to-use deployment scripts that allow one to deploy the entire platform with a single command. The edge and cloud services are leveraging each other and must be used together. For both edge and cloud services, we have provided pre-built Docker containers in the Microsoft Container Registry (MCR), removing this step for the customer. The cloud microservices are implemented as ASP.NET microservices with a REST interface and run on managed Azure Kubernetes Services or stand-alone on Azure App Service. The edge services are implemented as Azure IoT Edge modules and run on-premises.
![kepserverex simulated device example kepserverex simulated device example](https://community.ptc.com/legacyfs/online/thingworx/6887_NotConnect.png)
These adapters are available in the Azure Marketplace.
#KEPSERVEREX SIMULATED DEVICE EXAMPLE SOFTWARE#
For non-OPC UA-enabled assets, we have partnered with the leading industrial connectivity providers and helped them port their OPC UA adapter software to Azure IoT Edge. The OPC UA functionality has been built using Docker container technology for easy deployment and management. Device management capabilities (including security configuration) is also built in. In addition, the platform enables secure access to the shop floor assets via OPC UA from the cloud. There, it stores the telemetry data in a cloud database. The Azure Industrial IoT Platform covers industrial connectivity of shop floor assets (including discovery of OPC UA-enabled assets), normalizes their data into OPC UA format and transmits asset telemetry data to Azure in OPC UA PubSub format.
![kepserverex simulated device example kepserverex simulated device example](https://i.stack.imgur.com/Qdf5m.png)
Specifically, we leverage Azure’s managed Platform as a Service (PaaS) offering, open-source software licensed via MIT license, open international standards for communication (OPC UA, AMQP, MQTT, HTTP) and interfaces (Open API) and open industrial data models (OPC UA) on the edge and in the cloud. These modules and services have fully embraced openness (an open platform, open source, open industrial standards and an open data model is used). The Azure Industrial IoT Platform is a Microsoft suite of modules and services that are deployed on Azure.
![kepserverex simulated device example kepserverex simulated device example](https://docs.microsoft.com/en-gb/azure/iot-central/core/media/howto-connect-sphere/sphere-view.png)
Uses Cases of the Azure Industrial IoT Platform
#KEPSERVEREX SIMULATED DEVICE EXAMPLE HOW TO#
It explains how to set it up, what each of its components do and how to troubleshoot it. The document guides system operators to run the Azure Industrial IoT Platform in production scenarios.