Maximum length of code area reached (max. 64 Kbytes)

Hi all,

My safety system has total 24 redundant racks, when I tried to compile with 24 racks, I received an error like that. But when I tried with only 12 redundant racks, there was no error at all. Now I know that the error is generated because one chart @ named @11 has too many function blocks (all these function blocks are related to IO Module Driver) and this CFC exceed 64Kbytes

I've read some topics about this error, but my case is different. I can move these function blocks to a new group which I create in "Runtime Group" (to reduce size of CFC), but after compilation of CFC, all function blocks automatically move to @11 like before and error still exists.

Hope somebody has faced this problem and solved it before.

Thanks,

hi,

i am also facing exactly same problem.Can anyone help to resolve this issue

desperado211

Hi all,

My safety system has total 24 redundant racks, when I tried to compile with 24 racks, I received an error like that. But when I tried with only 12 redundant racks, there was no error at all. Now I know that the error is generated because one chart @ named @11 has too many function blocks (all these function blocks are related to IO Module Driver) and this CFC exceed 64Kbytes

I've read some topics about this error, but my case is different. I can move these function blocks to a new group which I create in "Runtime Group" (to reduce size of CFC), but after compilation of CFC, all function blocks automatically move to @11 like before and error still exists.

Hope somebody has faced this problem and solved it before.

Thanks,

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 ")

• The issue is caused by built in function of F-Systems. See the SIMATIC Process Control System PCS 7 Compendium Part B - Process Safety (V8.1) , under chapter "6.2.4 Run sequence of F-blocks" . In paragraph "Correct run sequence of F-blocks"  you can read:
  "The sequence of the F-blocks within the F-shutdown group is relevant. The number of Fruntime groups the F-shutdown group has been split into is of no relevance. Essentially, the correct run sequence of the various F-block types is as follows:
  1. Placed automatically:
  – F module driver for F-signal modules with inputs or with inputs and outputs..."
  
  
• Have you considered to split your F-Shutdown group? See the SIMATIC Industrial Software S7 F/FH Systems - Configuring and Programming manual under "A.2.7.6 F_PSG_M: Marker block for F-Shutdown groups ".

I hope I could help!

Exactly same problem I am facing. Is their any solution for that????

Thanks

Thanks for your valuable reply. But still I am in problem.

This is because the above manual will help when I am making charts or blocks programmed by me. But the problem which I am facing is in fresh project with nothing programmed, Only hardware configuration done in it with redundant module and rack.Just compling hardware this exceed error is coming.

And one thing what I noticed is when I remove redundancy of Digital input card as I tried for(Most number of DI we have in our system), The error is gone. This means The compiler is generating error for redundant configuration exceed. On this behalf I tried to reduce the number of rack to 20 i.e. 10 redundant rack, again the error is gone. So concludes the excess is the IO only and no problem in configuration. 

Now I am in doubt that my CPU-414-5H can handle 96 DP slaves then why this error is coming. I would like to inform I am using safety blocks in complete configuration.

Is it a CPU IO handling capacity issue??? or what

Thanks

Hi,

Make a screenshot of the error. We need to see what is the issue. 

Hi

Please refer the attached error snap.

Thanks

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!