How to connect OPCDA - InTouch (HMI) via KepServer EX as an OPC server

[MS_10266539]

As per the original post. 

Wonderware, InTouch, AVEVA (all the same thing) have a do not have a good OPC implementation (UA or DA).  Only the loopback IP address (127.0.0.0) can be used by AVEVA to address the server.  Thus, ANY server software must be on the same machine as AVEVA.  This is not the way OPC was meant to work.  I have been experimenting with have a copy of Kepserver on the server hardware (Kepserver/server) and additional copies on each workstation (Kepserver/AVEVA/worikstation).  The objective is to use the Kepserver/server to communicate with multiple PLCs to collect data via Modbus and then share the data with Kepserver/AVEVA/workstations.  This is a lousy way to implement OPC, but I haven't found an HMI that works any better.  Does anyone have any suggestions for an alternate HMI?

[pshashipreetham · Accepted solution]

Hi  @MS_10266539,

One option that many have had success with is Ignition by Inductive Automation. Ignition is built on modern OPC UA standards, so you don't have to deal with local loopback IP addressing limitations. It’s designed to connect to remote OPC servers seamlessly, so a centralized OPC server can communicate with your PLCs while distributing the data to HMIs on different workstations.

In addition to Ignition, here are a few points to consider:

• Ignition is web-based and modular, allowing you to scale your deployment as needed without installing multiple copies on different machines.
• Its robust OPC UA module helps avoid many of the issues inherent in traditional OPC DA implementations, such as those found with some older HMI packages.
• Ignition's flexibility makes it easier to integrate with various data sources, which could be beneficial if you have mixed environments or legacy systems.

Another alternative could be exploring solutions from other vendors like Siemens WinCC or Rockwell’s FactoryTalk. However, these are more tightly integrated with their respective ecosystems and might come with their limitations. Overall, suppose the goal is to have a more flexible, modern OPC architecture without being forced to install the OPC server locally on every machine. In that case, Ignition is worth a closer look.

Thanks,