The applications I worked earlier are too complex to be taught in a one day session.
does this mean that you only have ONE day for the training? ... yikes! ...
but anyway, my favorite way of handling the problem is to take one semi-simple programming project and then work through the program in all four of the programming methods ... so ...
(1) “here’s how it looks in ladder logic” ...
(2) “here’s how it looks in function block” ...
(3) “here’s how it looks in structured text” ...
(4) “here’s how it looks in sequential function chart” ...
using the same project over and over makes it easier to concentrate on the programming method - without getting needlessly bogged down in how the machinery functions ... pointing out how each programming method is “similar” to the others - and “different” from the others - has always been the best plan of attack for me ...
action plan: pick a project that will translate (at least moderately well) into all four programming methods ...
if the objective of the class is to demonstrate the similarities and the differences between the different programming methods, then I personally wouldn’t worry too much about which is the “best” way to tackle any particular project ... once the students have a grasp of what makes each programming method “tick” then they shouldn’t have much trouble determining which method would work best with their future projects ...