11/10/2009 4:00 PM | |
Joined: 11/10/2009 Last visit: 8/26/2022 Posts: 11 Rating:
|
Hello I've got some strange problem with one program. I uploaded it to my PC from the S7-300 PLC installed in one machine. Then I tried to open blocks to diagnose what is responsible for not good functioning. I tried to open OB1 block, unfortunately instead of familiar window with block's code I saw two following messages: (34:40) Compiler information type conflict and then: (30:1) Unable to open the block I thought that there is a problem with version of Step 7 so I upgraded it up to SP5 but without any good result. I thought that maybe I would be able to see OB1 online but again I saw the above two messages. All other blocks I am able to open. OB1 has no KNOW_HOW_PROTECTION. Simatic Managers displays that it was created in LAD and when online it informs that OB1 is in EPROM. I thought that there is some conflict with language or Regional Settings but I am able to see other blocks. I've attached compressed program. Do you have any ideas how to solve my problem? AttachmentProgram.zip (107 Downloads) |
11/10/2009 4:47 PM | |
Posts: 2348 Rating:
|
Also a question - can you upload OB1 to your PG (copy from online view or via upload whole station)? |
11/16/2009 11:50 PM | |
Joined: 11/10/2009 Last visit: 8/26/2022 Posts: 11 Rating:
|
Hi there I attached OB1.zip file. It contains listings of OB1 block both in STL and LAD format exported to pdf files. AttachmentOB1.zip (124 Downloads) |
11/17/2009 1:05 AM | |
Joined: 10/7/2005 Last visit: 5/29/2023 Posts: 2965 Rating:
|
Hello Morpher the problem is that your uploaded OB1 has an OUT variable which is most likely caused by using the word "RET_VAL" for a TEMP variable of OB1 (when programmed with S7 for Windows) and the reason that Step 7 (quite rightly) complains now! S7 for Windows is (fortunately or unfortunately, depending which way you look at it) less strict when it comes to these things and does allow youto use the word "RET_VAL" for a temp variable in an OB (and converts it to an OUT and has no problems with this either). Anyway, attached is pic that shows the problem and the fix is simple: Use S7 for Windows to change the name of "RET_VAL" to something else,remove the "OUT" declaration" from itand attach it to the RET_VAL of the SFC20 call in NW1. You can then use Step 7 to open OB1 Ihope this helps P.S: If you have S5 left on site that were programmed with S5 for Windows watch out for PB's that have jumps and/or any other "advanced" S5 commandsin it (S5 for Windows allows this in PB's, Step 5 does only allow this in FB's and FX's). |
Cheers |
|
This contribution was helpful to
1 thankful Users |
Follow us on