ABCIP DIObjects

Wonderware DIObjects for MBTCP DAServer 1.1 (1.1.0)

# About DIObjects

These DIObjects encapsulate the functionality of MBTCP DAServer 1.1 (1.1.0) in the ArchestrA environment. DIObjects are representations, or models, of the network and devices associated with a particular application to which the Industrial Application Server is connected. The hierarchy of the actual devices is the same as the hierarchy of the DI Objects.

# Installation Information

Installing a DIObject requires knowledge of the ArchestrA Integrated Development Environment (IDE). Consult the IDE documentation to learn how to fully exploit the features of DIObjects.

Detailed installation instructions are included in the IDE User’s Guide. You can find instructions on how to use the DIObjects in the IDE User's Guide, as well as in the individual DIObject help files, which are accessible once the DIObject has been imported into the IDE.

## Saving DIObjects to Disk

In order to import the DIObjects into ArchestrA, please first save the DIObjects to your local disk.

To save, click on directory DiModbusEnet DIObjects Directory. The Windows Explorer window will be posted. Copy all files in the directory to the appropriate location on your disk. After the DIObjects have been copied to your disk, you can proceed to import the objects into the ArchestrA IDE.

If you want to read the Readme file, please click here: Readme file.

## Importing Objects

To use an object, you must first import it into your Galaxy using the import function of the IDE. Objects can be imported from two types of ArchestrA-specific "package" files, typically with a .aaPKG extension. More than one object can be contained in a package file.

Note: You can also import object instances that were previously exported from a Galaxy. All previous associations are retained, such as assignment, containment, derivation, and area.

The Galaxy database does not allow two objects with the same name or more than one copy of the same version of an object. When you import an object, use the Import Preferences dialog box to specify how to handle naming conflicts and version upgrades.

### To import an object

1. On the Galaxy menu, point to Import and click Automation Object(s). The Import AutomationObject(s) dialog box appears.

2. Browse for an object file (.aaPKG extension), and click Open. The Import Preferences dialog box appears.

3. In the Import Preferences dialog box, set the behavior of the import process and click OK to continue or Cancel to terminate the import process. If you click OK, a progress dialog box appears.

4. Click Close when the import process is finished. Imported templates are displayed in the proper toolset in the Template Toolset. Imported instances are displayed in the Application Views. The following post-import rules apply:

• If the toolset does not exist, it is created.

• If the object belongs to a security group that does not exist, it is associated with the Default security group.

• If the object belongs to an area that does not exist, it is associated with the Unassigned Area.

• If the host to which the object is assigned does not exist, it is assigned to the Unassigned Host.

Note: If you import a new version of an existing instance, the new version is marked as requiring deployment if the existing object was already deployed.