A programmable Memory PACK function for M580

[Trinxs1]

 Some Customers undergo regular program online modification due to the nature of their business.  This leads to memory fragmentation and need to regularly perform a manual Memory Pack.    For a single PLC this is manageable.  For multiple it becomes an issue. 

An example from Francis Breysach

A customer with a large fleet of PLCs (~150 Quantum && M580 PLCs),

with Object-oriented programming with large DDTs and DFBs Structures (instance size from 1 to ~64 KB) regularly making Online Modifications (F&B domain) encounters more and more problems with the Fragmentation of the application memory, which generates problems with Build Changes mode, instabilities and even CPU crashes.

Our recommendation would be to “regularly” make Build All && Download campaigns.

But this requires a PLC Stop and therefore Production stops.

As the customer is increasingly in production mode 7 days a week, it becomes complicated to manage over time, with the constraint of the size of the PLCs fleet.