5/25/2011 1:48 PM | |
Joined: 10/7/2005 Last visit: 10/9/2024 Posts: 3024 Rating: (1054)
|
Hello de_stal this is normal behaviour, keep on downloading and you will eventually automatically beprompted to "compress" the PLC memory which will then free up the no longer used memory again. You can also manually itin Simatic Manager via the "Compress" button in the "Memory" tab of your online CPU Module information. I hope this helps |
Last edited by: fritz at: 5/25/2011 1:50 PMfixed typos Cheers |
|
5/26/2011 11:26 AM | |
Posts: 261 Rating: (42) |
In addition with fritz and Krish I have the following views (As per Krish” So I suggest you look for other things”) A)Load memory: i)Load Memory intergraded: RAM with battery backup. ii)Load Memory external: RAM with battery backup or non volatile flash memory. B)Work Memory: i)Work Memory Code: RAM with battery backup. For process image I/O (both central and distributed) and diagnostics buffer. ii)Work memory Data: RAM with battery backup. For local data stack. System memory: RAM with battery backup. For contains Bit memories, Timers counters (managed by operating system), Block stack and interrupt stack. Load memory contains: i)The user program ii)The system data. The work memory contains: i)Logic blocks ii)Communication job iii)Process Image input iv)Process Image Output v)Diagnostics buffer. Your Load memory depends upon your programming part and H/W configuration which you can monitor from your program. ( Giving you pain) Your work memory depends upon your load memory (Logic blocks) + process image I/Os + Diagnostics buffer and communication jobs. ( Not a problem for you) You can monitor your program size from your offline backup and can generate a view from it. Or maybe you had downloaded some blocks and forgot to delete from on line (Which are not present in offline) which cause your load memory bottle neck. Comments from fritz is always valuable and informatics for us. |
This contribution was helpful to1 thankful Users |
Follow us on