Some content on this site is available only to logged-in subscribers. Contact Us for information on becoming a subscriber.

InSource.Solutions | InSource Training | InSource Client Portal
InSource Solutions Logo
Log In Sign Up
InSource.Solutions InSource Training InSource Client Portal Log In Sign Up
  • Home
  • AVEVA Application Server
  • AVEVA Application Server Tech Notes

TN DAS178 Syntax for OPC Communication with OI Servers

Last updated: February 20th, 2025

Description

  • Author: Rich Brooks
  • Published: February 20th, 2025

Details:

Description

This article from InSource shows how to configure the syntax for Wonderware OI Server OPC communication from non-Wonderware clients.

  • Author: Rich Brooks
  • Published: 4/16/2020
  • Applies to: OI Core v6.0 and higher

Details

The OI Servers support OPC and SuiteLink communication with clients. SuiteLink is the typical protocol to use with Wonderware clients. Third party clients may use OPC for communication, if they do not support Suitelink. The example below shows the syntax required for the MBTCP driver.

Below is a typical Modbus TCP configuration. DAS is the name of the port in this example. ET05 is the name of the PLC connection.

ET05 is also the name of the device group. 

Note: The PLC connection and device group must be the same name.

The third party OPC client below uses an alias list to reference the items in the PLC.

The itemID is preceded by the port name and device group name as shown above. This is the proper syntax for OPC communication.

opc syntax oi servers
Give feedback about this article

Recommended articles

How to receive group emails

Read More
Support Icon

CONTACT SUPPORT

How to reach us

10800 Midlothian Turnpike Tpke, Suite 209, Richmond, VA 23235

1.877.INSOURCE

Technical Support - 1.888.691.3858

Contact Us

  • InSource Solutions
  • InSource Training
  • InSource Client Portal
  • Log In
InSource Solutions Logo

© 2025 InSource Solutions. All Rights Reserved.

Knowledge Base Software powered by Helpjuice

Expand