Great work as always, your visual presentation of things were just *chefs kiss* in this video. If you want to do more awesome animations in your videos, i can highly recommend using Cavalry. On another note: I would love if you could explain the following TwinCAT OOP concepts in a future video. - Properties (Why should we use those over "normal" variables? what's the benefit?) - What is SUPER^ and THIS^ in TwinCAT OOP explained very simply. I've read what it is but can't wrap my head around it and might need to see it used and explained. Would also be cool to take a deep dive into Pragmas and Attributes in TwinCAT. Which ones are handy? and are there some you use in every project?
Hey! Those are all great suggestions for future videos. Properties I generally never use, mostly because the concept of properties doesn't exist in C++ and that's the land I came from. I just see them as syntactic sugar over Getter/Setter-methods. I'll add the "SUPER^" and "THIS^" into my list of subjects for future videos, and pragmas as well. Some pragmas are very handy and that I use very often, such as 'instance-path'. Thanks for supporting my channel!
@@JakobSagatowski My pleasure, your content started my automation career off really well, and i'll forever be grateful. I'll be supporting you for many years to come
Properties are becoming visible in an UML class diagram. But most important they are allowing the transformation of internal and incoming values. Sometimes values are only accessible after the first cycle which can be elegantly hidden in a getter. But most important properties can be used with interfaces hence they are important for dependency injection. This can be done with methods as well but we use methods for questions like isRunning() or everything which has a verb in it
I know the ladder, I use it every day, there are some times when it applies, but if it were up to me I would never use it. My coworkers don't understand another language and use it in the most electric way possible.
Don't waste your time waiting. Checkout my course doing Structured Text programming using TwinCAT 3 instead. Here you go: th-cam.com/play/PLimaF0nZKYHz3I3kFP4myaAYjmYk1SowO.html
So basically, use ST. Ladder isn't well suited for Modularity, Separation of concerns and Automated testing if code. All the architectures you have shown would be a nightmare in Ladder.
Ladder is good option for creating/debugging the machine cycle! It gives you well visualization what's going on. Also it is the most familiar to electrical drawings (control circuits). But at the end the best is what you are most used to 😉 F.e. I never use FBD, ST... - I use ladder. But sometimes I agree with the argument, that ST could be better solution for some applications, especially when you work with data arrays.
Important video. I hope that many will take a look at it.
Thanks Stefan!
Been writing like this for over 25 years I still update and reuse blocks in my library I wrote 20 years ago 😅
Nice video Jakob! Keep it up.
Thanks, will do!
Would be quite interested in how you are handling CI/CD for PLCs, looking forward to more videos.
That's 100% do-able. Checkout my blog or my website, I have several articles regarding CI/CD for PLCs there. Enjoy!
Awesome video Jakob !!! Keep it up. Could not agree more with you. Spot on.
Great work as always, your visual presentation of things were just *chefs kiss* in this video.
If you want to do more awesome animations in your videos, i can highly recommend using Cavalry.
On another note:
I would love if you could explain the following TwinCAT OOP concepts in a future video.
- Properties (Why should we use those over "normal" variables? what's the benefit?)
- What is SUPER^ and THIS^ in TwinCAT OOP explained very simply. I've read what it is but can't wrap my head around it and might need to see it used and explained.
Would also be cool to take a deep dive into Pragmas and Attributes in TwinCAT. Which ones are handy? and are there some you use in every project?
Hey! Those are all great suggestions for future videos. Properties I generally never use, mostly because the concept of properties doesn't exist in C++ and that's the land I came from. I just see them as syntactic sugar over Getter/Setter-methods. I'll add the "SUPER^" and "THIS^" into my list of subjects for future videos, and pragmas as well. Some pragmas are very handy and that I use very often, such as 'instance-path'. Thanks for supporting my channel!
@@JakobSagatowski My pleasure, your content started my automation career off really well, and i'll forever be grateful. I'll be supporting you for many years to come
Properties are becoming visible in an UML class diagram. But most important they are allowing the transformation of internal and incoming values. Sometimes values are only accessible after the first cycle which can be elegantly hidden in a getter. But most important properties can be used with interfaces hence they are important for dependency injection. This can be done with methods as well but we use methods for questions like isRunning() or everything which has a verb in it
@Pixeliria,
I am creating an OOP course for PLCs on the IEC61131-3 standard...
th-cam.com/play/PLEfi_hUmmSjFpfdJ6yw3B9yj7dWHYkHmQ.html
Jakob, you have won the war 😂😂😂
அருமையான பதிவு......
I know the ladder, I use it every day, there are some times when it applies, but if it were up to me I would never use it. My coworkers don't understand another language and use it in the most electric way possible.
SOLID 😊
Great video!
Great video.!
Waiting for your Sysmac Studio Structured Text programming course with live programming in the machine........
Don't waste your time waiting. Checkout my course doing Structured Text programming using TwinCAT 3 instead. Here you go: th-cam.com/play/PLimaF0nZKYHz3I3kFP4myaAYjmYk1SowO.html
So basically, use ST. Ladder isn't well suited for Modularity, Separation of concerns and Automated testing if code. All the architectures you have shown would be a nightmare in Ladder.
Time and place. Time and place.
Always time and place!
SFC (or Stateflow in MatLab/Simulink)
*PromoSM*
crap is a bad word
Ladder is hot flaming garbage.
FBD or CFC is infinitely better.
Ladder is good option for creating/debugging the machine cycle! It gives you well visualization what's going on. Also it is the most familiar to electrical drawings (control circuits).
But at the end the best is what you are most used to 😉 F.e. I never use FBD, ST... - I use ladder. But sometimes I agree with the argument, that ST could be better solution for some applications, especially when you work with data arrays.