DeviceIntegration Objects ReadMe

# Wonderware DeviceIntegration Objects ReadMe

Last revision: 8/31/2004

This ReadMe file describes the WonderwareÒ ModbusEnet DeviceIntegration (DI) Objects and how to install them. Also, known issues are documented.

DIObject Package: DiModbusEnet_1.1.aaPkg

Objects in the Package:

ModbusEnet 1.5 | ModbusEnetBridgeModbusPLC 1.1
ModbusEnetBridgeModbus 2.1 | ModbusEnetMomentum 2.1
ModbusEnetBridgeModbusComp984 2.1 | ModbusEnetPLC 1.1
ModbusEnetBridgeModbusMicro 2.1 | ModbusEnetPremium 1.1
ModbusEnetBridgeModbusMomentum 2.1 | ModbusEnetQuantum 2.1

Encapsulated DAServer: MBTCP 1.1

Known Issues

About DIObjects

Installation Information

# Known Issues

L00019525:

ArchestrATM will not enforce a limit on the number of device objects that can be assigned to a parent object.

L00028210:

A warning message will be displayed in the logger when an object having multiple “Required Host Feature” is imported and an instance of it is created. Please ignore this warning; this functionality works fine.

L00028213:

ArchestrATM does not enforce a limit on the number of TCP ports that can be assigned to each engine on each platform. This is misleading, since only one TCP port is allowed to be configured and deployed; illegal configurations will result if you configure more than one port.

L00029132:

Importing the Galaxy dump file for PLC objects will disable the Support unsolicited message pull-down list in Scan Groups. When a dump file is imported, the existing scan group name will not have the selection for whether it supports unsolicited messages.

< top of document >

# About DIObjects

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 DIObjects.

< top of document >

# 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.

## 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 ArchestrA-specific "package" files 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.

< top of document >

© 2004 Invensys Systems, Inc. All Rights Reserved.