2/27/2016 10:02 PM | |
Joined: 11/29/2011 Last visit: 9/24/2024 Posts: 1359 Rating: (232) |
Hi, Maybe you should try to rethink/restructure your application. In the compendium bellow you find guide for this. (See the manual SIMATIC Process Control System PCS 7 Compendium Part B - Process Safety (V8.1) chapter "5.1.3 Cyclic interrupts ")
I hope I could help! |
Last edited by: MicroMan at: 2/29/2016 9:46:55 AM- What you read here, please check with manuals and your requirements. |
|
9/9/2016 5:55 AM | |
Posts: 30 Rating: (0) |
Exactly same problem I am facing. Is their any solution for that???? Thanks |
9/9/2016 7:16 AM | |
Joined: 3/14/2008 Last visit: 9/25/2024 Posts: 2097 Rating: (938)
|
Hello guys, You can follow the steps in the document I enclosed. Let me know if that is the solution! AttachmentHow do you clear the message Maximum code length of code area reached.pdf (920 Downloads) |
If I could help you, you can use the RATE button. Thank you. |
|
9/10/2016 5:46 PM | |
Posts: 30 Rating: (0) |
Hi Please refer the attached error snap. Thanks |
9/10/2016 11:57 PM | |
Joined: 11/29/2011 Last visit: 9/24/2024 Posts: 1359 Rating: (232) |
Hi, It is hard to say from the limited info we know about your code, but It sounds like that too many "F-Module drivers" is being generated in one Runtime Group. See SIMATIC Industrial Software S7 F/FH Systems - Configuring and Programming manual under chapter "6.2 Generating F-Module drivers" Have you considered to split the code into more F-Shutdown groups? I hope I could help! |
Last edited by: MicroMan at: 9/11/2016 11:30:52 AM- What you read here, please check with manuals and your requirements. |
|
1/17/2018 4:04 PM | |
Joined: 3/2/2007 Last visit: 9/18/2024 Posts: 935 Rating: (5) |
Kindly how did you solve this problem ? " Maximum length of code area reached (max. 64 Kbytes) "
|
... thank you ... |
|
1/17/2018 7:48 PM | |
Joined: 11/29/2011 Last visit: 9/24/2024 Posts: 1359 Rating: (232) |
Hi, Have a look at the FAQ, as above posted already (This is a good way find the reason of the problem): How do you clear the message "Maximum length of code area reached (max. 64 Kbytes)"? Also see the bellow FAQ for understanding what is happening: Basically a "runtime group" getting bigger than it suppose to be. If you still having issues let us known! |
Last edited by: MicroMan at: 1/18/2018 6:47:19 PM- What you read here, please check with manuals and your requirements. |
|
3/2/2019 2:01 PM | |
Posts: 10 Rating: (0) |
I'm facing the exact same issue with 12 redundant Rack. If you found a solution please help me. |
3/5/2019 1:58 PM | |
Joined: 11/29/2011 Last visit: 9/24/2024 Posts: 1359 Rating: (232) |
Hi, As discussed above: Structure the code better. Too many things are getting compiled into one Run time group. Apply common sense! For example: Do you have charts with high number of Block Instances? -> Make smaller charts... A little guide how to structure your code better in SIMATIC Process Control System PCS 7 Compendium Part B - Process Safety (V9.0) "6.1.3 Cyclic interrupts". If you have further questions please attach your compilation log. |
- What you read here, please check with manuals and your requirements. |
|
3/5/2019 2:07 PM | |
Posts: 1 Rating: (0) |
I face the same problem, due to non-disclosure issues I cannot take screenshots, hope my instructions will be useful, I asked an expert in the company and tell me to do this: 1. Using the SCL editor find out which CFC is giving you troubles (download the PDF instructions previously sent)
2. Search for the CFC the SCL editor tell you as TITLE = 3. Look out for the CFC in the Plant View 4. Open the CFC and open any block by double clicking in the runtime number to locate the CFC folder in the Run Sequence editor 5. The folder must be too long, create a second folder and move part of the blocks to that folder, half of them could be a good start, but try to avoid dividing blocks that are working together 6. Recompile and must be solved Hope it helps |
3/5/2019 3:22 PM | |
Posts: 10 Rating: (0) |
My problem is about redundancy, I have 50 redundant modules, with 48 redundant modules there is no compile error, after making the last 2 modules redundant compile error comes back. while I have only one CFC with one F_CH_DI. I already checked SCL source and : //-- Beginning: Runtime group @OB1_@(7)_(1) FUNCTION FC765 :VOID TITLE = '@OB1_@(7)_(1) ' AUTHOR: ES_MAP NAME: GROUP this runtime is source of error and it contains 50 blocks of OR_M_8C, OR_M_16C, OR_M_32C
AttachmentAS_ESD_22_Compile.txt (183 Downloads) |
3/5/2019 3:23 PM | |
Posts: 10 Rating: (0) |
Here my Hardware Config export
Attachmentas_esd_22.cfg.txt (160 Downloads) |
3/5/2019 6:36 PM | |
Posts: 10 Rating: (0) |
And here is successful compile log after removing redundancy of 2 DO modules.
AttachmentAS_ESD_22_Compile_OK.txt (194 Downloads) |
Follow us on