Hello MohdFhG,
Thank you for posting your question in the Microsoft Q&A forum.
Your understanding on the setup is a practical and effective way to integrate OPC UA data with MQTT-based systems, but it’s not a native implementation of OPC UA over MQTT. Instead, it’s a bridge that enables communication between the two protocols. If you need true OPC UA over MQTT, you will need to look for solutions or configurations that specifically support this standard.
let's clarify the specifics of how Azure IoT Operations handles OPC UA and MQTT.
Data Generation and OPC UA Server:
- Data is generated by industrial assets (e.g., sensors, machines) and sent to an OPC UA server. OPC UA (Open Platform Communications Unified Architecture) is a widely used industrial communication protocol for data exchange.
Azure IoT Edge and MQTT Broker:
- Azure IoT Operations (or Azure IoT Edge) can be configured to connect to the OPC UA server. The OPC UA server's data is then published to an MQTT broker running on the edge device. MQTT (Message Queuing Telemetry Transport) is a lightweight messaging protocol ideal for constrained environments.
Data Flow:
- The MQTT broker on the edge device allows other systems or applications to subscribe to specific topics. These topics correspond to the data streams from the OPC UA server. Subscribers can receive real-time updates from the assets via MQTT.
In your case, the data from the OPC UA server is being republished by an MQTT broker. This is more accurately described as a bridge or gateway between OPC UA and MQTT rather than a native implementation of OPC UA over MQTT. The OPC UA data is being translated or converted into MQTT messages, but it’s not necessarily using the OPC UA over MQTT specification.
If the above answer helped, please do not forget to "Accept Answer" as this may help other community members to refer the info if facing a similar issues.