4/12/2021 2:53 PM | |
Joined: 10/14/2020 Last visit: 2/20/2022 Posts: 2 Rating: (1) |
Hi Siemens community, I am in a problem situation and need help on how to recover. I will describe what I did, the current problem I see, and would like advice on how to recover from this issue. What I did: I was trying to add some blocks in CFC. They are in OB1. However when thinking about the problem I want to solve I originally wanted to put these blocks into OB36 for a fixed scan time. In the runtime editor I right clicked OB36 and selected "Insert runtime group", and then did nothing. I can't say if the window for "Insert runtime group" opened or not. It may have been open in the background but I did not notice it. OB36 was highlighted green. Then going back to thinking about the problem I was trying to solve I realized having these blocks in OB1 would be fine. I then decided to try a compile. But 68 errors and 3 warnings came. Then I went back and checked for anything strange but couldn't find anything. Then trying to compile again, it would not start saying "Block folder not found. Please insert a block folder." What I currently see: Currently, all the blocks are somehow gone in the 'blocks' folder of this PLC... not sure how this could happen with a bad compile. What should I do: What is required to recover the project? I checked and the PLC looks fine, PCS7 only did that first bad compile but did not download to PLC so it is fine. The problem is the offline project all the blocks are somehow deleted. How do I make the offline project match whats running in the PLC? Should I do an upload from PLC, or restore from an old backup and do a full download? Please help is appreciated. AttachmentBad compile, no blocks in offline project.docx (100 Downloads) |
Last edited by: jmajerovic at: 04/12/2021 14:59:18 |
|
4/16/2021 2:43 PM | |
Posts: 198 Rating: (60) |
Hello,
Using OB1 in PCS7 is not recommended as it has a variable cycle time. Depending on the load, the time can be as high as 6000ms in PCS7. Hence, the ideal method of configuration is in defined cyclic interrupts using runtime groups.
"Insert runtime group" will help you to create a runtime group in the desired OB. However, you will have to move blocks manually into this runtime group. Ideally, when you add a CFC and place a block in the chart, it will automatically create a runtime group in the OB which is defined as 'Predecessor for next insert position' (green color).
As mentioned above, OB1 is not recommended for PCS7 configurations. Here is a detailed explanation for the same and why it would be appropriate to use cyclic interrupt OBs for your logic: https://support.industry.siemens.com/tf//WW/en/posts/set-ob1-as-default-organization-bloc-in-pcs7/211497?page=0&pageSize=10#:~:text=OB1%20has%20the%20disadvantage%20that,cycle%20time%20is%20always%20consistent. I think the compile errors are due to incorrect configuration or placement of your blocks. You can check or troubleshoot further by following the normal nomenclature for block and CFC configuration which is available in this manual. CFC Manual Link (Section 10.11 in specific) You can also troubleshoot the SCL source code for errors where E: LXXXXX C XXXXX is mentioned (provided you had selected 'Generate SCL source' during previous compiles - if yes, SCL source will be available in the SOurce folder under program folder) Considering it tough to troubleshoot or fix your project with a single error screenshot, it might need further investigation of your CFCs in the project. If you are unable to reorganize the project based on the above inputs, it better to take the support of Siemens Technical Support Request by raising a ticket. Technical Support Request Link Hope this helps |
Last edited by: Jen_Moderator at: 04/19/2021 07:49:24Optimized link. |
|
This contribution was helpful to1 thankful Users |
Follow us on