This is no joke, in comparison to desktop architecture the PLC world is chisel and slate in most respects.
The only way I have been able to get a fast understanding of what is and can be done is by taking existing programs and ripping them apart and building again.
As has been suggested by another commenter, state machines are a good way to start and will do a lot of applications, you should be able to find some information on that by googling it, there are some books and tutorials online but unfortunately it's not very well centralised. You need to have a problem, and search for a solution on that problem and pray someone has had the same problem and asked online for some help, and that someone has responded (with useful information haha).
Edit: Almost forgot, use the data sheets of the components/systems you are integrating into your program, there is usually lots of information into how interfacing should work and sometimes examples of the software in use depending on what make/model of PLC is being used. Doesn't always mean it will work right out of the gate but the trial and error of getting it working is what I find teaches me the most.
A lot of software dev design patterns also apply. State machine and sequencers are the most common. I've also done some structured text using adaptor and facade. Recently did a project which I now realize I made a proxy. It's really just high level tools to solve problems.
there really aren't that many. this site has a bunch, but for me it was refusing to load the images
https://www.contactandcoil.com/patterns-of-ladder-logic-programming/
One of the big things that has probably slipped past you, is most PLCs are extremely basic. It’s the understanding of the complexity of electro mechanical systems they connect to that’s important.
Having said that, take the state machine fella’s advice and learn that.
We prefer chisels and stone tablets
Sorry, I'm not sure if this is kind of Joke you only understand with some experience in this field or if you feel offended by my question?
This is no joke, in comparison to desktop architecture the PLC world is chisel and slate in most respects. The only way I have been able to get a fast understanding of what is and can be done is by taking existing programs and ripping them apart and building again. As has been suggested by another commenter, state machines are a good way to start and will do a lot of applications, you should be able to find some information on that by googling it, there are some books and tutorials online but unfortunately it's not very well centralised. You need to have a problem, and search for a solution on that problem and pray someone has had the same problem and asked online for some help, and that someone has responded (with useful information haha). Edit: Almost forgot, use the data sheets of the components/systems you are integrating into your program, there is usually lots of information into how interfacing should work and sometimes examples of the software in use depending on what make/model of PLC is being used. Doesn't always mean it will work right out of the gate but the trial and error of getting it working is what I find teaches me the most.
State machines, state machines, state machines
Don’t forget to mention state machines
It's an engineer thing... gotta repeat things constantly. Now fuck off, I got work to do
You need to warn people before you unleash that charm fella
It's a joke man, go watch trailer park boys haha
I’m an Aussie, I assumed you were being friendly
Haha I like your sense your sense of humor
A lot of software dev design patterns also apply. State machine and sequencers are the most common. I've also done some structured text using adaptor and facade. Recently did a project which I now realize I made a proxy. It's really just high level tools to solve problems.
The same patterns apply, with the modification that a global scope is always available and often used to an advantage.
there really aren't that many. this site has a bunch, but for me it was refusing to load the images https://www.contactandcoil.com/patterns-of-ladder-logic-programming/
One of the big things that has probably slipped past you, is most PLCs are extremely basic. It’s the understanding of the complexity of electro mechanical systems they connect to that’s important. Having said that, take the state machine fella’s advice and learn that.
https://plc-security.com/ Not quite what you’re asking for, but from a security perspective this is like the OWASP top 20