PLC software documentation, flowcharts and state diagrams

Random thoughts…

Just found this basic yet interesting article on my rss feed: https://www.controldesign.com/articles/2019/how-to-document-a-plc-program/

It highlight the fact that in real life documenting a PLC software is still considered a simplified version of the “real software documentation” process, unfortunately.

But during reading the referred article https://www.controldesign.com/articles/2017/how-to-write-a-plc-step-sequence-program we should also remember that 61131-3 standard defines an SFC programming language dedicated to step sequence programming https://en.wikipedia.org/wiki/Sequential_function_chart.

Going one step further, i’ve been practicing recently with a very interesting system implementing a complete State Charts Diagram editor as part of a more complex embedded UML editor. Yes, when i mention State Charts I’m talking about this http://www.inf.ed.ac.uk/teaching/courses/seoc/2005_2006/resources/statecharts.pdf

Finally…!!!

What’s wrong with PLC editors, seriously?

If you don’t use Git you’re ugly and stupid.

Tech Talk: Linus Torvalds on git, 2007

After so many years most of us PLC software developers are still ugly and stupid people, wasting our time and our employers’ money fiddling around with zip files with weird names, duplicated content and a software delivery process which is generally very slow and inaccurate.

But it’s not (exclusively) our fault!

Customers, decision makers and stakeholders in general, when choosing your next PLC system, don’t forget asking your vendor a very basic question: is your programming environment Git-compliant?

Otherwise, you are all ugly and stupid at least as me.