STL - Better than Ladder or Just job security?

Join Date
Dec 2010
Location
Toronto
Posts
8
I am new in a company which uses only Siemens. All the PLC programs I have uploaded are in statement list and cannot be reverted to ladder (no NOP 0s). Is statement list able to do something ladder cannot, or did someone wipe out all the NOP 0 lines for job security? How often do you guys encounter programmers who prefer STL over Ladder? should I stop programming in ladder and start learning STL?

Any guidance is greatly appreciated.

Mike.
 
I am new in a company which uses only Siemens. All the PLC programs I have uploaded are in statement list and cannot be reverted to ladder (no NOP 0s). Is statement list able to do something ladder cannot, or did someone wipe out all the NOP 0 lines for job security? How often do you guys encounter programmers who prefer STL over Ladder? should I stop programming in ladder and start learning STL?

Any guidance is greatly appreciated.

Mike.

You said "uploaded"
Under the blocks folder, does the created in language say STL?

Are your machines from Europe?

If your answers are yes- then learn STL :)
 
As far as I know its what they are taught
and indirect addressing is only done in STL

Whats the created in language say??
 
It's all created in STL and SCL. I know Omron and AB have similar options (mneumonics) but every machine i ever worked on used ladder. is Siemens the only manufacturer that encourages writing programs in machine type language?
 
It's all created in STL and SCL. I know Omron and AB have similar options (mneumonics) but every machine i ever worked on used ladder. is Siemens the only manufacturer that encourages writing programs in machine type language?
----------------------------------
Well SCL (Structured Control language) is the same as ST or Structured Text
STL (Statement List) is the same as IL or Instruction List
Many manufacturers have this.

I use "same as" kinda loosely

Anyway, if alot of your blocks are SCL and you uploaded your program THEN you will not have the source code. Thus you can only read the code in STL
I hope that makes sense...

The long short of it is- GET THE ORIGINAL CODE FROM YOUR VENDOR
 
Learn SCL

I would use mostly SCL because of the ease of programming. For those things that MUST be fast I would write first in SCL and then optimize the STL code by hand. Writing code in STL is like writing code in assembly language. It is tedious and more error prone than writing it in a higher level language.

There will be some things that still must be done in STL but they can usually be very small functions.

My answer to your question is that writing code in STL provides job security.
 
My answer to your question is that writing code in STL provides job security.

I password is job security.... STL is very fast if you are programming it and have learned it first or with ladder

It like talking on the phone with someone

and pushbutton
and not estop
or stop
= run

Learn it and have fun with it... open another empty block or window and then you can copy and paste the hard ones into the empty project, there you can add your NOP's and convert it into ladder

The long short of it is- GET THE ORIGINAL CODE FROM YOUR VENDOR
:nodi: YES YES YES
 
Your example is trivial

I password is job security.... STL is very fast if you are programming it and have learned it first or with ladder

It like talking on the phone with someone

and pushbutton
and not estop
or stop
= run
You forgot the parentheses around the estop and stop. Oops, have fun chasing that bug down. It is easier to make errors in STL. It is harder to see the program structure since there is no indenting.

In SCL
run:=pushbutton and not ( estop or stop )
 
and pushbutton
and not estop
or stop
= run

Learn it and have fun with it...

^^ (y)

You forgot the parentheses around the estop and stop. Oops, have fun chasing that bug down. It is easier to make errors in STL. It is harder to see the program structure since there is no indenting.

In SCL
run:=pushbutton and not ( estop or stop )

No Peter, above stl (or did you intend to say what it should be?)

Code:
a pushbutton
an estop
o stop
= run
Would be:

Code:
run := (pushbutton and not estop) or stop;
Btw, where ever one could use something like that o_O

STL is hard. I would actually say that concepts behind it that make it superior in some cases, are so hard that not everyone really can understand them. But if one can, he on the way learns S7 inner workings so that it is worth it. If you use another languages you don't need to understand anything about accus, registers etc.
 

Similar Topics

IS it possible to write this on a better way: L #db_Num2 L 121 ==I JNB _02 CALL "CONT_C" , "DB_reg_igla1"...
Replies
3
Views
2,628
Hey, This peace of program in the folowing images is written in STL. Is this well written, is there a better way to write, more structure, norm...
Replies
25
Views
7,349
i am new to simatic manager and i am trying to figure what this part do in the code : A I 5.6 = DB50.DBX 4.6...
Replies
3
Views
132
Hello everyone, can anyone help me with covert the STL code to ladder. Iam using plc s71200. A %DB1.DBX33.7 // angel of vaccum...
Replies
2
Views
208
Hello nice to meet you, im new in here, I'm currently trying to convert code written in STL for a S7-400 to SCL for an S7-1500, because when i run...
Replies
5
Views
317
Back
Top Bottom