Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
OPC UA PubSub 1.04 Compliance
See original GitHub issueThe Readme.md file states:
This reference implementation demonstrates how Azure IoT Edge can be used to connect to existing OPC UA servers and publishes JSON encoded telemetry data from these servers in OPC UA “Pub/Sub” format (using a JSON payload) to Azure IoT Hub.
It requires that the message created by:
IotHubMessaging.CreateJsonMessageAsync(OpcPublisher.OpcMonitoredItem.MessageData)
has to be compliant with the specification:
My concern is what is the reason to create the message following this specification. As far as I understand this encoding. i.e. the JSON based message mapping allows OPC UA Applications to interoperate with web and enterprise software that use this format. Is there any plan to:
- make the Azure IoT Edge OPC UA PubSub JSON encoding aware
- compliant with OPC UA PubSub Application and offer the Subscriber role.
Issue Analytics
- State:
- Created 5 years ago
- Comments:13 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@barnstee, it is great. I only assumed that the “sprint a set period of time during which specific tasks must be completed” but not tightly coupled version number". Thanks, I will watch it. Let me know if there is something I can do to help.
You are making a lot of assumptions here! We just removed the milestone since we’re not sure yet if we call the next version 2.8 or 3.0. This work is actually scheduled for our current sprint! 😃