Device group definitions

The Device Groups tab in the OI Server Manager user interface is used to create new, modify, or delete device group definitions for an object. For DDE/SuiteLink communications, one or more device group definitions must exist for each PLC that the Communication Driver will communicate with.

Important: For DDE/SuiteLink, it is strongly recommended that each device group (topic) definition contain a unique name for the PLC associated with it. The OPC, however, has the flexibility to use any names, including duplicate names, for the device group definitions.

Each device group (topic) definition should contain a unique name for the PLC associated with it.

The Device Groups dialog box, which is displayed by clicking the Device Groups tab in the New_<Name>PLC_000 Parameters configuration view, is used to perform the following activities:

• Adding, defining, and deleting device groups.

  Note: When you add a new device group, enter a unique name.

• Configuring the Communication Driver to receive unsolicited messages.

• Configuring default update intervals.

Editing update intervals for the device groups.

Note: When you select another part of the Communication Driver tree hierarchy, you are prompted to save the modifications to the configuration set.

Create or add device groups

1. Right-click in the Device Groups dialog box.

2. Select the Add command from the shortcut menu.

   • When you add a new device group, enter a unique name (up to 32 characters long).

Make changes on device groups’ names

Change a device group’s name for an object as follows:

• In the Name column, double-click on the device group’s name to be modified and make the change.

Delete device groups

Deleting a device group from the list can be performed as follows:

3. Right-click on the device group to be deleted.

4. Select the Delete command from the shortcut menu.

Note: When you select another part of the MBTCP Communication Driver tree hierarchy, you are prompted to save the modifications to the configuration set.

Configure the MBTCP Communication Driver to receive unsolicited messages

This option is available only to the PLC nodes that are directly connected to the TCPIP_Port node. PLC nodes that are connected underneath the ModbusBridge node do not have this capability.

Some PLCs, for example the TSX Premium PLC, can send Holding Register and Coil unsolicited data to the MBTCP DASever, while other PLCs, for example the TSX Quantum PLC, can send the Holding Register unsolicited data only to the Communication Driver.

Note: If you have globally disabled unsolicited messages using the DASMBTCP.aarul file, configuring Device Group parameters to support unsolicited messages will have no effect. For more information about enabling and disabling unsolicited messages, see Unsolicited message handling.

5. Click on the PLC’s name in the PLC branch of the Communication Driver hierarchy.

6. Select the Device Group tab of the configuration view pane at right.

7. Add a new device group or select an existing device group.

8. Right-click on the device group name, then select Edit from the shortcut menu.

   • The Device Group Parameters dialog box is displayed.

     

9. In the Device Group Parameters dialog box, select the Support Unsolicited Messages check box.

10. Click the OK button to close the dialog box.

Note: Since the status of Support Unsolicited Messages check box cannot be readily viewed from the Device Groups tab, proper naming of device groups which support unsolicited messages is strongly recommended. Unsolicited messages are only supported in the base instance of the Communication Driver (the instance of the Communication Driver without the custom name).

11. Save the configuration change by clicking the Save icon located at the upper-right corner of the configuration view pane.

Note: For more information on unsolicited messages, see Unsolicited message handling.

Configure default update intervals

12. To configure a default update interval for the object, right-click in the Device Groups dialog box.

13. Select Config Default Update Interval from the shortcut menu.

Make changes on update intervals

A change on an update interval for an object can be made as follows:

• Double-click on the value to be modified in the Update Interval column and make the change.

  • Update Interval is the frequency (in milliseconds) that the Communication Driver acquires data from the topics associated with that device group.

  • Different topics can be polled at different rates in a PLC by defining multiple device-group names for the same PLC and setting a different Update Interval for each device group.

  • If you also select the "Support Unsolicited Message" checkbox as described above, duplicate updates could be received by the items associated with the device group. To avoid duplicate updates, set the Update Interval to 0 (zero).

    Note: When you select another part of the MBTCP Communication Driver tree hierarchy, you are prompted to save the modifications to the configuration set.

Each configuration view associated with nodes/objects in the Communication Driver hierarchy tree has a common feature, the Save button.

14. When you modify any parameters in the Device Groups dialog box, click Save to save and implement the new modifications.

    • If you do not click Save, the configuration is reset to its original condition (since the last save).

15. After all modifications, you must save when prompted for the new data to be saved to the configuration set.