Klinkmann Omron Ethernet DeviceIntegration Objects ReadMe

Last revision: 21/06/2010

This ReadMe file describes the Klinkmann Omron Ethernet DeviceIntegration (DI) Objects and how to install them. Also, known issues are documented.

DIObject Package: DIOmronEth_118.aaPkg

Objects in the Package:

OmronEthNet 1.18

OmronEthNetController 1.4

 

Encapsulated DAServer: DASOmronEth 1.18

Known Issues

About DIObjects

Installation Information

 

Known Issues

Configuration

The Omron Etherent Direct DAServer can be configured to connect a large network of Omron PLCs. System resources such as CPU cycles, physical memory, and system threads are consumed with each PLC that is configured into the DAServer. You must specify appropriate device group update-interval and reply-timeout values for the number of PLCs being connected.

Configuring a high number of PLCs connected to Omron Etherent Direct DAServer can potentially reduce the performance of this DAServer.

L00019525:

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

< 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

 

Complete following steps to install Klinkmann Omron Ethernet DeviceIntegration (DI) Objects. 

1)     If on current galaxy is any previously installed Klinkmann Omron Ethernet DeviceIntegration (DI) Objects delete them and undeploy platform.

2)     Import Klinkmann Omron Ethernet DeviceIntegration (DI) Objects.       

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.

  1. Browse for an object file (.aaPKG extension), and click Open.

·         The Import Preferences dialog box appears.

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

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