ControlLogix: Ladder vs. Structured Text

Ron thanks for that. I must say I have never run into the issue you mentioned but see how it can be a problem. My Structured Text is all based on CoDeSys which does not have the [:=] operator.
 
Ron thanks for that. I must say I have never run into the issue you mentioned but see how it can be a problem. My Structured Text is all based on CoDeSys which does not have the [:=] operator.

Agree, I've never bumped into something like that in the Siemens world, either. You don't need to worry about everything being retentive, you can choose what is or isn't. Chalk it up to needing understand the specifics of your system vs the generic language.

Great tip, Ron!
 
Most of these examples are completely academic and non-realistic.

If you intend to start and stop a motor with push buttons you have a lot more to think about.

For instance for a direct start motor you have a circuit breaker, a contactor, overload relay and likely an additional relay (if your PLC output has a transistor output).

Done right you have inputs to your PLC from the circuit breaker, from the contactor and from the overload relay. Because you need to know if the circuit breaker has tripped, if the motor is overloaded or if there is a problem with the contactor.

In a lot of cases you also have an isolator switch so the motor can turned off locally and locked in is off position for maintenance. You also have an input from the isolator switch to your PLC.

You might also have a sensor that senses the rotation of the motor or conveyor or whatever it is driving.

And then you probably have an emergency stop and if it's a machine you might have guards, light curtains and what not that would prevent the motor from running.

If it's some kind of process system you might have process dependent interlocks as well.

Safety issues for humans like emergency stops are controlled by safety circuits like safety relays or safety PLCs. There might also be process safety systems involved if you deal with chemical industry, oil and gas or similar.

Besides this you also have to figure out what state you want the system to be at power startup, after an emergency stop etc etc like mentioned in earlier posts.

In reality when you have a PLC you often control start and stop automatically as well so any push buttons might be just for manual control under certain operating conditions. Also physical push buttons might coexist with HMI and SCADA systems so start and stop commands might originate from multiple sources.

The best option in those case is to NOT use a start and a stop push button and instead use a start/stop button (toggle function) that's illuminated so it shows if the motor is running or not. It takes less real estate and feedback of motor status is important.

To discuss how one line of ladder or structured text looks like to start a motor is like looking at the problem through a keyhole where you see about 5% of the whole picture.
 
Last edited:
well, to be honest, I was trying hard to come up with a short simple example that would clearly illustrate a specific facet of the PLC code's operation which few people know about - and which is seldom if ever discussed ...

I apologize - and I'm sorry to have wasted your time ... I'll try to contact a moderator and have my ridiculous post removed - before anyone else is forced to waste their time in reading it ...

best regards ...
 
Last edited:
well, I was trying to come up with a short simple example that would clearly illustrate a facet of operation which few people know about - and which is seldom if ever discussed ...

I apologize - and I'm sorry to have wasted your time ... I'll try to contact a moderator and have my ridiculous post removed - before anyone else has to waste their time in reading it ...

best regards ...

Dripping with irony but I wasn't really talking about your post. You emphasized an important issue - status after PLC in program - which we could extend to status after power on, e-stop etc.

I'm just saying we need to look at the whole picture and every issue. Start and stop of a motor in real life isn't solved by one line of ladder logic or structured text.
 
Last edited:
I apologize - and I'm sorry to have wasted your time ... I'll try to contact a moderator and have my ridiculous post removed - before anyone else is forced to waste their time in reading it ....

:ROFLMAO: Boy I have wasted a lot of time on this site but it was never reading one of your post... thank you for taking the time and explaining the way you do PLEASE keep up the great help Ron
 

Similar Topics

Is it possible to export a routine programmed in structured text and import it into a ladder routine?
Replies
2
Views
2,881
I created a new program task under that I created 2 ladder files. My first ladder does not have the 1 flag in the ladder icon designating it is...
Replies
8
Views
4,215
Hi all, Is there a equivalent function block that do the same as MOV function in ladder? Thanks.
Replies
5
Views
2,328
I am making some changes in a control logix PLC program that an engineering programmed for my company. In the program they have used the same I/O...
Replies
15
Views
7,414
Hi everybody, Until now I worked only with ladder logic. Now I have a program with function blocks. It looks more complicate, e.g. you have to...
Replies
4
Views
3,059
Back
Top Bottom