I/O auto-assignment workflow example

This section describes the basic steps for implementing I/O auto-assignment, from start to finish. The basic steps are:

1. Use the Attributes page of the Object Editor to prepare system objects and application objects for I/O auto assignment.

2. Use the Object Editor to configure DI objects and scan groups.

3. Use the IO Devices view to assign system and application objects to scan groups (objects must be undeployed).

4. Use the Mapping view to validate I/O references. You can enter overrides in this view, if necessary.

To prepare objects for I/O auto assignment

5. Create a derived template from the $UserDefined base template and open it in the Object Editor.

6. Add attributes as needed. For each attribute that requires input or output, select the I/O button.

   The default I/O mode is Read/Write, and the default string indicating that the attribute is primed for I/O auto assignment appears in the Read from / Write to field.

7. Change the I/O mode as needed.

   Important: Do not change the default string if you want to use auto assignment for the attribute. The default string indicates that auto assignment is not yet complete and the object is not linked to a PLC.

8. Save and check in the template, then close the Object Editor.

9. In the Template folder, create instances from the UDO derived template. The instances appear in the Model view, under Unassigned Area.

To configure DI objects and scan groups

10. In the Template folder, create a Device Integration (DI) object from the $OPCClient, $DDESuiteLinkClient, or $Redundant DIObject template. The DI object appears under "Unassigned Area" in the Model view and under "Unassigned IO Devices" in the IO Devices view.

11. Add one more scan groups to the DI object you created in the previous step. The naming convention for the scan groups must conform to the naming convention of the PLC with which you are connecting.

    The scan groups will show as belonging to the DI object in the IO Devices view.

To assign system and application (user created) objects to scan groups

12. Create a new area and set it as the default. Do not deploy the area yet.

13. In the IO Devices view, drag and drop the area to a scan group.

14. Create new application objects. As you create new objects, they will appear in the IO Devices view under the default area.

    The IDE will complete the references for each I/O attribute for you.

15. If you need to change the scan group assignment for an object, drag and drop it to the new scan group.

To assign system and application (user created) objects to scan groups - alternate method

16. Create a new area and assign it to a scan group.

17. Create new application objects. These will appear under the Unassigned folder in the Model view.

18. Assign the application objects to the area assigned to the scan group in step 1. All application objects assigned to the area will inherit the area’s linkage to the DI object and scan group.

19. If you need to change the scan group assignment for an object in the area, drag and drop it to the new scan group.

To validate I/O references (and override auto assigned values, if necessary)

20. Open the Mapping view. This view opens automatically if you select an object, scan group, or DI object in the IO Devices view.

    Each row in the Mapping table contains the I/O reference for one attribute.

21. Enter an override value for the attribute in one of the override columns.

    Note: The DI Object.Scangroup Override column can only contain the DI object name and scan group name, separated by a period (.).

22. Deploy the platform and associated DI objects.

23. Select the Validate References button to check that communication is established with the PLC.

24. Deploy the objects.