Object, area, engine, and platform assignments

Getting Started with the IDE shows the basic Galaxy structure. When you create an application object, such as a User Defined Object, it must be assigned to an area. When you look at your objects in the Deployment view, an area is assigned to an AppEngine, and an AppEngine is assigned to a WinPlatform.

The Deployment view uses the WinPlatform as its foundation, and all objects cascade from the WinPlatform object. The WinPlatform object can be thought of as the node (computer) that hosts the rest of the objects. The basic hierarchy of objects in the Deployment view is:

Data Integration (DI) Objects provide the interface between application objects and PLCs in the physical environment. DI Objects contain scan groups, and application objects are assigned to scan groups; this assignment can be done in the IO Devices view.

The relationship of other objects in the Galaxy to DI Objects is most clearly viewed in the IO Devices view. All IO between objects in the Galaxy and the PLC is through a DI Object. Scan groups are configured in the DI Object, and objects are assigned to a scan group.

While objects can be deployed from any IDE view, the Deployment view provides the simplest way to understand the object hierarchy during deployment. The IO Devices view provides the simplest view of the relationship of each scan group and its assigned objects.