side efects of one controller memory full.
what are the side efects of one controller almost full of memory.
is it possible that controller colapse and the program is erased?
or what could it happen?
is it possible that controller colapse and the program is erased?
or what could it happen?
Voted best answer
5
AC 800M?
Warm download requires some free memory space so that the old and new version of the application can fit together while the variable content is copied, after which the new version is started and the old version is disposed of. The time for the controller to perform this is called Stop Time and is measured per application (with multiple applications, you need a SystemDiagnostics function block per application to measure the Stop Time).
Splitting up a single large application into smaller pieces (applications) may help with memory management and reduction of Stop Time as you seldom need to download warm to all of the applications at the same time. With a single application you need 50% free memory to make warm download and Stop Time will be large (also depending on numbers of variables). With three smaller applications you can utilize more than 50% memory while still being able to make warm download to one or even two of those applications.
Lack of free memory forces cold download.
Memory "leaking" over time will eventually become a problem for an AC 800M (same as with most computers and operating systems). The effects of running out of RAM are hard to predict, but sometimes its better to halt or restart than not being able to perform your duties. Stay on recent and updated versions and contact your regional support team if you see memory increase over time for no good reason.
Use the AC800MFingerPrint.exe tool shipped with Control Builder M to collect data for the support team to analyze. If possible, create a 'baseline' shortly after the controller has been reset and cold downloaded, then create a few more as free memory drops.
Obviously, if the controller log is filled with errors and warnings you should attempt to address them. Not too seldom, the handling of abnormal situations involve less tested/proven code compared to smooth cruising without errors. There may be known issues and workarounds posted as bulletins at ABB Library. Stay connected, stay updated!
Warm download requires some free memory space so that the old and new version of the application can fit together while the variable content is copied, after which the new version is started and the old version is disposed of. The time for the controller to perform this is called Stop Time and is measured per application (with multiple applications, you need a SystemDiagnostics function block per application to measure the Stop Time).
Splitting up a single large application into smaller pieces (applications) may help with memory management and reduction of Stop Time as you seldom need to download warm to all of the applications at the same time. With a single application you need 50% free memory to make warm download and Stop Time will be large (also depending on numbers of variables). With three smaller applications you can utilize more than 50% memory while still being able to make warm download to one or even two of those applications.
Lack of free memory forces cold download.
Memory "leaking" over time will eventually become a problem for an AC 800M (same as with most computers and operating systems). The effects of running out of RAM are hard to predict, but sometimes its better to halt or restart than not being able to perform your duties. Stay on recent and updated versions and contact your regional support team if you see memory increase over time for no good reason.
Use the AC800MFingerPrint.exe tool shipped with Control Builder M to collect data for the support team to analyze. If possible, create a 'baseline' shortly after the controller has been reset and cold downloaded, then create a few more as free memory drops.
Obviously, if the controller log is filled with errors and warnings you should attempt to address them. Not too seldom, the handling of abnormal situations involve less tested/proven code compared to smooth cruising without errors. There may be known issues and workarounds posted as bulletins at ABB Library. Stay connected, stay updated!
Add new comment