Double-clicking the “POU Locations” object in the device tree of the controller opens the editor. At first, it gets only the entry “<application>”. After a code generation, all program blocks of the application are displayed with the respective object type, current location in the memory, and code size.
In the “Configured Location” column, you can set one of the memory areas other than the “Current Location” for each POU or library.
In order to move the POUs to the recently configured memory locations, you first have to “Clean” and then “Generate Code” again.
Note the messages in the category “POU Locations”. This is also shown when a code POU cannot be moved as expected.
“Clean” |
Deletion of the compile information for the application Corresponds to the “Build Clean” menu command This is a requirement for moving the POUs to the configured memory locations. |
“Generate Code” |
Starting of the code generation for the application Corresponds to the “Build Generate Code” menu command This is a requirement for moving the POUs to the configured memory locations. |
“Objects” |
Objects of the application, including the objects from the referenced libraries |
“Type” |
Object type Examples: “Function Block”, “Method”, “Library” |
“Current Location” |
Current memory location of the POU: |
“Configured Location” |
Configured memory location where the POU is moved at the next code generation. Possible values:
|
“Code Size” |
Code size of the POU (in bytes) |
-
See also: ⮫ Build → Clean
-
See also: ⮫ Build → Generate Code