If you enjoyed this video you will also find my free newsletter valuable. Join 2500+ subscribers to get weekly actionable tips on the architecture and development of IIoT solutions. → SUBSCRIBE HERE: www.industry40.tv
Only caveat with UDP multicast is that your routers and switches need to allow it and it can't be transmitted over internet. But for very small devices it has least overhead, because there is no tcp handshake. (correct me if not correct)
If neither publishers or subscribers need to be opcua servers or clients, how is this an opcua exchange anymore? Doesn't this completely undermine how the opcua foundation is helping industries standardize opcua communication from asset to high level applications? Essentially I'm hearing that opcua pub sub is a two part plan. Use the opcua information model... if you want. And then go get any message broker you want and use that.
Thanks for your comment, Terrance. Ideally, you want at least one of your network participants being an OPC UA publisher. OPC UA PubSub is still pretty much in the early stages of its development as a lot of its core functionality is still being added. Infact, much of the features I described in the video concerning MQTT topic trees and information model integration will only come out with the next version of OPC PubSub Spec, due in this quarter.
![How OPC UA Client Server Communication Works [5 of 11]](http://i.ytimg.com/vi/vgE9P6KNC7g/mqdefault.jpg)
![How OPC UA Client Server Communication Works [5 of 11]](/img/tr.png)
If you enjoyed this video you will also find my free newsletter valuable. Join 2500+ subscribers to get weekly actionable tips on the architecture and development of IIoT solutions.
→ SUBSCRIBE HERE: www.industry40.tv
The whole course is really great. Thank you. :)
Will you be posting the rest of the 8th to 11th videos in this series?
Awesome!! Global Brother, Thanks from Hyderabad, INDIA!
Thank You Kudzai!
Mr the information that you show to us is very inpirational thanks a lot!
Very useful, thanks.
Thank you Kudzai for the good work.
Great work. Thank You!
thanks a lot , quite useful
Thanks Kudzie. I wanna learn more.
Thank you for your feedback, Samson I really appreciate it. More content is coming!
Thanks
Only caveat with UDP multicast is that your routers and switches need to allow it and it can't be transmitted over internet. But for very small devices it has least overhead, because there is no tcp handshake. (correct me if not correct)
thank you!!
Thank you, Onur.
If neither publishers or subscribers need to be opcua servers or clients, how is this an opcua exchange anymore? Doesn't this completely undermine how the opcua foundation is helping industries standardize opcua communication from asset to high level applications? Essentially I'm hearing that opcua pub sub is a two part plan. Use the opcua information model... if you want. And then go get any message broker you want and use that.
Thanks for your comment, Terrance. Ideally, you want at least one of your network participants being an OPC UA publisher. OPC UA PubSub is still pretty much in the early stages of its development as a lot of its core functionality is still being added. Infact, much of the features I described in the video concerning MQTT topic trees and information model integration will only come out with the next version of OPC PubSub Spec, due in this quarter.