• Device Integration Objects

• A DeviceIntegration object (DIObjects) is an AutomationObject that represents communication with external devices. DIObjects run on an AppEngine, and include DINetwork Objects and DIDevice Objects. 
• A DIDevice Object is a representation of an actual external device (for example, a PLC or RTU) that is associated with a DINetwork Object. A DINetwork Object is a representation of a physical connection to a DIDevice Object via the Data Access Server.
• DDESuiteLinkClient
  

• The DDESuiteLinkClient object is a DeviceIntegration object that allows access to a running I/O Server.
• The reference syntax for a DDESuiteLinkClient object data point is:
• <objectname>.<topicname>.<itemname>

• <objectname>.<topicname>.<attributename>
• The <objectname> is the name that you choose to give to the DDESuiteLinkClient object.
• Each I/O topic for a DDESuiteLinkClient object is also known as a "scan group." Run-time object attributes allow you to monitor errors related to the data quality for item values in a scan group.
• InTouchProxy
• The InTouchProxy Object is a gateway between Galaxy application objects and data that is available through an InTouch application. The InTouchProxy object allows you to browse a selected InTouch application tagname dictionary, add selected tags as attributes in the Galaxy application, then read these attributes from the InTouch application at run time.
• syntax for an InTouchProxy object data point is:

• The <objectname> is the name that you choose to give to the InTouchProxy object.
• Note: Before using the tagname browser to browse for tags, make sure that InTouch WindowMaker is not running on the InTouch node. WindowViewer, however, can be running. Also, be sure that you have given share permission of Read to the InTouch folder that contains the Tagname.X file.
• OPCClient
• The OPCClient object is a key member of the core set of AutomationObjects within the ArchestrA system infrastructure. The OPCClient object is a DeviceIntegration (DI) object that allows access to a running OPC Data Access (DA) Server. A third-party OPC DA Server can provide data points to Galaxy application objects through the OPCClient object.
• RedundantDIObject
• The RedundantDIObject provides you with the ability to configure a single object with connections to two different data sources. In the event of a failure of the active data source, this object automatically switches to the standby data source.
• The RedundantDIObject is a DeviceIntegration object that makes redundant connections to a field device possible. If one of the source objects is unable to provide connection to the field device, the RedundantDIObject automatically switches to the other source object for continued data acquisition.