An application is a set of objects which are needed for running a particular instance of the controller program on a certain hardware device (controller). For this purpose, independent objects managed in the Global node of the Applications tree are instantiated and assigned to a device. This meets the concept of object-orientated programming. However, you can also use purely application-specific POUs.
An application is represented by an application object in the Applications tree. Below an application entry, insert the objects defining the application resource set.
One application is available for each controller. It is not possible to add further applications.
A part of each application is the Task Configuration controlling the run of a program (POU instances or application-specific POUs). Additionally, it can have assigned resource objects like global variable lists, libraries, and so on. These - in contrast to those managed in the Global node of the Applications tree - can only be used by the particular application and children. For the rules, refer to the description of arranging and configuring objects in the Devices tree.
When going to log in with an application on a target device (controller or simulation target), two checks are performed: Which application is currently in the controller? Are the application parameters in the controller matching those in the application within EcoStruxure Machine Expert? Appropriate messages indicate mismatches and offer some ways to continue in this case. Also you have the possibility to delete the application in the controller. Refer to the description of the Login command for more details.
