Warning!! V13 SCL code compiled wrong. IF Statement + Sliced acess.

Hi,
I Want to warn you as i had a serious problem with this!!

I reported this problemto Siemens, and it wassend to development.
The answerfrom development was thatthey found a bug in the SCLcompilerin V13 causing this problem. This will be corrected in V13 + UPD2. (I first saw it happen online on a S71513-1PN).

The problem is using sliced acess within a IF statenent, see below code.

----

MyTempWord:= 0;
If MyBool Then
MyTempWord.X0:= TRUE; // any logic setting the slice.
MyTempWord.X1:= TRUE;
End_IF;
OutWord:=MyTempWord.

---

Thiscode was not working. Although, MyBool = 1 and the if statement is executed.
OutWord is still 0. You can test it and you will see it happen.

Do not use sliced acess within an IF statment until the problem is fixed, (They Say UPD2).
Meanwhile use temp within the if and then set the sliced acess after the IF statement.

Tip To check all your code:

Wecompiled all ourSCL code into a big source file.(in portal view you can sort blocks on language type). We did it by copy all SCL blocks into a new folder and then select all blocks andgenerate source from blocks.After this we could eseally searched for IF together with sliced access, in the genrated source file.Having all places identified wechange the code to get rid of the allIF+sliced acessstatements.

//Mattias.

SIMATIC-Team

Dear Mr. Lindh,

we are very pleased to inform you, that the described behavior is fixed with the recently released TIA Portal-Update:

Updates for STEP 7 V13 and WinCC V13

With best regards
SIMATIC-Team