Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

SCL editor bug for S7-1200

Created by: shwetha at: 4/10/2013 2:35 PM (4 Replies)

Rating (1)

Thanks 0

5 Entries

4/10/2013 2:35 PM	Rate (0)
shwetha Posts: 23 Rating: (0)	I am using SCL editor on TIA portal professional V11 SP2 for S7-1200 programming. SCL editor keeps hanging frequently. It is very annoying. I have to delete the function block and create new eveyrtime the problem occurs. Attached is the snap shot of the error. Could anyone let me if there is any fix for that? Attachment Error.jpg (438 Downloads)
shwetha Posts: 23 Rating: (0)
Suggestion To thank Quote Answer

4/10/2013 2:39 PM	Rate (0)
TomDeWou Platinum Expert Joined: 11/15/2006 Last visit: 5/7/2021 Posts: 1319 Rating: (174)	Do you have latest Upd5 for V11 SP2 installed?
	Have Fun! TomDeWou
Suggestion To thank Quote Answer

4/10/2013 2:46 PM	Rate (0)
shwetha Posts: 23 Rating: (0)	Yes. I have installed Update5
shwetha Posts: 23 Rating: (0)
Suggestion To thank Quote Answer

4/10/2013 3:51 PM	Rate (1)
0_Einstein Diamond Expert Joined: 7/7/2010 Last visit: 11/27/2024 Posts: 15441 Rating: (2452)	I have found with SCL editing on S7-1200, there seems to be an unwritten nesting limitation for the compiler to actually compile properly. I basically have to compile / rebuild all, but this may result in crashes, so I have to reduce nesting or manually compile the lowest level scl FBs/FCs, then move up a level in nesting, and then I can compile the highest level SCLs. Sometimes we think the scl will properly change data types in an embedded call and in the s7-300 world the code works just fine and the documentation states it should work. However, more often than not, adding the conversion everywhere often improves compiler performance (without crashing). If a single scl line has more than 3 levels of nesting, it seems to cause problems. I just create as many intermediate stages as needed to reduce nesting to 3 or less. Maybe those implied conversions, like word->int, take up one of those nesting levels, and simply making it more obvious really helps. Perhaps you could post your troublesome scl code that always crashes. If you comment out the entire fb and it still crashes during compiling, you now know it isn't your code, but some other scl code artifact (bug) from perhaps the last scl block compiled carrying over some bad result. [Yes, I have seen this]
	science guy
Suggestion To thank Quote Answer

4/12/2013 6:35 AM	Rate (0)
Jakeway Posts: 3 Rating: (0)	I've found huggy_d1's comment to be very true with the SCL editor. I just sent in a help ticket to Siemens support on this issue. The response back from Siemens is that there is an issue with this type of nesting with the SCL language and that V12 will fix it... take that for what it's worth. My problems came when I've nested SCL functions calls at the lowest levels of the program during ladder sequencing events. It does seem that in V11 you really can't take a large SCL function any lower than three or four levels deep. It's a pretty lame bug, and the way that I've moved around it (if I don't want to re-write everything in ladder...) is to set a bit that will call the SCL functions from OB1 (or a similar higher level program). Good luck.
Jakeway Posts: 3 Rating: (0)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on