In my Udemy course on Classic OPC, one of the demonstrations involves a client that supports HDA but a server that does not. It is used to advise the viewer to ensure that they check which of the DA, HDA, A&E specs the clients and servers support in order to avoid a "mismatch". Whilst this is a relatively easy thing to check for in Classic OPC, it's not as easy in OPC UA as UA has many more considerations. I really appreciate how you gave a view into the structure of the OPC Foundation. I never knew it was structured like that but it clears up a lot. That being said, I think Classic OPC was an amazing thing in the 90's. It lead to so many benefits. But you are quite correct about the trajectory. Something went a little awry. Thanks once again for this contribution!
damn, thanks man. i have been working in a Iiot project in my company as a cloud support team and never really understood why they use kepware server and what is the drawback of opc ua and all , this video is such a gem of information's thanks for creating and contributing to this channel love from India.
In the 90's when I was working for the steel industry automation, we had an open and modular communication system known as Oracle Remote Data Transfer to interoperate Simatic PLCs with supervisory control systems. Cant find it any longer.
What about Apache PLC4X in comparision? As the project aims to do exactly that but Opensource? Especially their Mspec format makes these protocols really readible for everyone.
Thank you for a great intro to OPC UA. General discussion on overall architecture helped to grasp concept, general example for applications and compare/contrast to see why there is a discrepancy on its role in IIOT. 👍
OMG Last time I set up a network OPC connection was in the late 90s. I'm trying to set up one where the client box is a new VM and the server only had local connections. I forgot about DCOM. I can't believe there isn't a quick tool by now to configure DCOM. This is nuts.
Thank you so much for this amazing video. I am struggling with some fundamental. Is the main idea for OPC-UA is data collection or is also for real time control. e.g. controlling a motor , synchronization between industrial controllers, turning on/off actuators, etc ? I mean is it a replacement to existing protocols as Ethernet/IP, Modbus,etc ?
No it isn't for real-time control. Generally OPC goes 'up' from the PLC to an HMI or SCADA system, not 'down' from the PLC to your field devices like sensors and actuators. OPCUA and EtherNET/IP are apples and oranges. ETHERNET/IP and EtherCAT for example are more apples and apples. Modbus...I don't know exactly but I think its like a turkey
Please to be clear, does OPC mean Open Platform Communication or OLE for Process Control. Because these variations slightly confuse me. Another thing i want to say is, the OPC foundation are just making more money from manifacturers and organizations. Before i watched this video, i thought it was an open communication protocol that could allow all industrial devices to communicate with each other. But now i see it's only if you belong that you have the chances (likely, only if your devices use the same part of the standard) of communicating. Crazy how the world works, so crazy
OPC in OPC Foundation originally stood for OLE for Process Control. OLE refers to Object Linking and Embedding, a Microsoft technology for inter-process communication. Over time, OPC has evolved beyond its original meaning and now represents a suite of standards for exchange of data in industrial automation and other industries.
@@4.0Solutions Thanks for th answer! I am a 3rd year student in EE and I find these very helpful. With regards to MTConnect, I am not sure what role it plays. Is it comparable to what SparkplugB aims to do?
Jay -- thank you. I recommend you learn all three. In our mentorship program at iiot.university, we have all of the mentees learn SQL, Python and Ignition MQTT and OPC-UA during step 1. Its hard to get the complete picture of Industrial communications and IT/OT convergence without them all. Blessings to you.
follow you in several you tube`s,one question:mqtt can be used instead of iec61850 (goose),excuse me ,this is not the way for discuss this topic,thanks in advance
I am told OPC-UA and TSN is the future for all deterministic control and will replace all industrial fieldbuses in the future........I will believe it when I see it :)
Watch Part II Here!
👉 ua-cam.com/video/6Fns92nrrYM/v-deo.html
In my Udemy course on Classic OPC, one of the demonstrations involves a client that supports HDA but a server that does not. It is used to advise the viewer to ensure that they check which of the DA, HDA, A&E specs the clients and servers support in order to avoid a "mismatch". Whilst this is a relatively easy thing to check for in Classic OPC, it's not as easy in OPC UA as UA has many more considerations. I really appreciate how you gave a view into the structure of the OPC Foundation. I never knew it was structured like that but it clears up a lot. That being said, I think Classic OPC was an amazing thing in the 90's. It lead to so many benefits. But you are quite correct about the trajectory. Something went a little awry. Thanks once again for this contribution!
Thank you Emile!
One of the best youtube channels/videos I have ever seen on my youtube watching history. Keep up the good work !
Wow, thanks!
FINALLY BACK TO THE WHITEBOARD!!!! Classic Walker content right here!!
Thank you!
@@4.0Solutions huge fan of everything you all do. Dont mind me, I'm just getting nostalgic.
This channel is truly great. It is Straightforward to the important part!
This is pure gold! Can't wait for part 2!
It's ready to go!
Great great content, I always learn with your videos, this OPC series is exciting. Greetings from Cuba
Thank you Erick!
damn, thanks man.
i have been working in a Iiot project in my company as a cloud support team and never really understood why they use kepware server and what is the drawback of opc ua and all , this video is such a gem of information's
thanks for creating and contributing to this channel love from India.
Thanks for the comment!
Great content guys, I’m really excited about this new OPC series
Glad you enjoy it!
In the 90's when I was working for the steel industry automation, we had an open and modular communication system known as Oracle Remote Data Transfer to interoperate Simatic PLCs with supervisory control systems. Cant find it any longer.
What about Apache PLC4X in comparision? As the project aims to do exactly that but Opensource? Especially their Mspec format makes these protocols really readible for everyone.
We answered this in this live stream! ua-cam.com/video/-bJgtMP6N9k/v-deo.html
This is exactly what I needed. Thank you, good sir!
Glad I could help!
Thank you for a great intro to OPC UA. General discussion on overall architecture helped to grasp concept, general example for applications and compare/contrast to see why there is a discrepancy on its role in IIOT. 👍
Glad it was helpful!
Love your valuable content 💪🏼👍🏻
Thank you
Very good explanation. Thank you
You are welcome!
Keep up the good work! Really interested in OPC ua protocol and it’s integration into different systems
Thank you for sharing! Wait till you learn about MQTT!
I absolutely loved the explanation. Very detailed and with some bits of humor here and there
Glad you enjoyed it! Thank you for watching!
OMG Last time I set up a network OPC connection was in the late 90s. I'm trying to set up one where the client box is a new VM and the server only had local connections. I forgot about DCOM. I can't believe there isn't a quick tool by now to configure DCOM. This is nuts.
Thank you, Shannon! Totally agree!
This video is amazing!
Glad you liked it! What part did you like best?
Will you cover / add opinion on Umati? Thanks
That's an interesting looking PLC on the table next to the white board. ;-)
Wait till you see what’s next 😎
Very good historical background guys. More power to you
We appreciate it.
Thanks, good explanation! A bit over edited, less jump cuts would make it easier to watch imo
Thanks for the feedback! We will take this into account.
Thank you so much for this amazing video. I am struggling with some fundamental. Is the main idea for OPC-UA is data collection or is also for real time control. e.g. controlling a motor , synchronization between industrial controllers, turning on/off actuators, etc ? I mean is it a replacement to existing protocols as Ethernet/IP, Modbus,etc ?
No it isn't for real-time control. Generally OPC goes 'up' from the PLC to an HMI or SCADA system, not 'down' from the PLC to your field devices like sensors and actuators. OPCUA and EtherNET/IP are apples and oranges. ETHERNET/IP and EtherCAT for example are more apples and apples. Modbus...I don't know exactly but I think its like a turkey
@@adamrohde3513 Thank you Adam. Very Helpful.
Does reasons 1 and 2 for OPC-UA not been the future of automation still valid since OPC-UA PA-DIM and OPC-UA FX companion specs release?
Great content. I would really appreciate getting rid of the backgroung music.
Thanks for the feedback! We will take this into account.
11:40 The OPC Foundation definitely needs a UI/UX designer for creating a stunning front-end web design lol.
😂
I did not even know that OPC UA was intended as an IOT protocol by the OPC foundation. I always used it between PLC and SCADA layers.
No, but the foundation seems to want you to think that. Or rather that it's good for collecting data for integrated/shared IT-OT information uses.
Please to be clear, does OPC mean Open Platform Communication or OLE for Process Control. Because these variations slightly confuse me.
Another thing i want to say is, the OPC foundation are just making more money from manifacturers and organizations. Before i watched this video, i thought it was an open communication protocol that could allow all industrial devices to communicate with each other. But now i see it's only if you belong that you have the chances (likely, only if your devices use the same part of the standard) of communicating.
Crazy how the world works, so crazy
OPC in OPC Foundation originally stood for OLE for Process Control.
OLE refers to Object Linking and Embedding, a Microsoft technology for inter-process communication.
Over time, OPC has evolved beyond its original meaning and now represents a suite of standards for exchange of data in industrial automation and other industries.
What do you think about MT Connect?
It's great!
@@4.0Solutions Thanks for th answer! I am a 3rd year student in EE and I find these very helpful. With regards to MTConnect, I am not sure what role it plays. Is it comparable to what SparkplugB aims to do?
wonderful explanation 👏🏻
Glad you liked it
Starts from the real beginning : DDE
Well said👌
Thanks Bryn!
Walker .. god damn you are a great presenter. I am new to OPC UA, am I wasting my time learning it and should I go learn SQL and MQTT?
Jay -- thank you. I recommend you learn all three. In our mentorship program at iiot.university, we have all of the mentees learn SQL, Python and Ignition MQTT and OPC-UA during step 1. Its hard to get the complete picture of Industrial communications and IT/OT convergence without them all. Blessings to you.
So a spec originally intended to improve interoperability now proliferates confusion.
🤔
Hi from ZMS Technology Germany
Welcome to the Industry 4.0 Community! ♥️
follow you in several you tube`s,one question:mqtt can be used instead of iec61850 (goose),excuse me ,this is not the way for discuss this topic,thanks in advance
Someone just asked that in the discord the other day! Was that you? - Zack
@@4.0Solutions was me
I am told OPC-UA and TSN is the future for all deterministic control and will replace all industrial fieldbuses in the future........I will believe it when I see it :)
LOL!
Nice
Thank you!
thanks Hank
nice
Thanks!
hi to all
Welcome!
Bro u sound and look like Hank Schrader ngl😅
He does look a bit like him doesn’t he 😅
Hmm... Exposes the SELFISH MOTIVES of OPC... !
nice
Thanks