You could consider coding in Step7 {TIA} and then export as text file to Stepo7 V5.7. That might solve quite a few problems. -- and perhaps create some new ones. You choose the lesser evil.

Or avoid SCL all together. 

Thx for advices!

I already know LAD and STL very well, but some says that SCL is the future in term of programming PLC`s. 

Automation_lover

Thx for advices!

I already know LAD and STL very well, but some says that SCL is the future in term of programming PLC`s. 

For sure there are advantages on having SCL. Porting over from one CPU to another, even over different brands is a bit more easy. Mass coding techniques given by text editors (Vim / VS Code / Notepad++) is also a huge plus.

SCL in Step7 Classic is not friendly. So only you have the power to decide which pros and cons have more weight.

Automation_lover

Omg, that`s right. This program it`s awful in showing what it is wrong. He was leading me to the line 20 (END_FUNCTION) and I was stucked trying to see what`s wrong at that line. 

The error position is correct, as the semicolon is not expected immediately after the END_IF. Spaces or line breaks are allowed, you could also place the semicolon right before the END_FUNCTION.

In the parsing process the sourcecode is first tokenized where all spaces and linebreaks are removed, as they are outside from string literals not neccessary. So the tokenizer has only tokens like "END_IF", "SEMICOLON", "END_FUNCTION". The syntax check expects after the "END_IF" token a "SEMICOLON" token an nothing different. So the error first occurs when it sees the wrong "END_FUNCTION" token.

See the Step7 SCL help, it has a very good formal language description.