compatibility issues between system platform v23 and kepware

Hi,

I have been having lot of problems with a system platform 23 setup which seems to be triggered by suitelink connections, I am using the newest version of kepware as an OPC. It is hard to pinpoint what the reason is but during my research a noticed there is a reported issue from PTC and Aveva regarding problems with 23 and kepware.

here is one example:

Compatibility Concerns: Users have reported difficulties in establishing OPC communication between Kepware servers and System Platform 2023, especially when the servers are on separate machines. Even after configuring DCOM settings and firewall rules, connections may fail. Installing Kepware locally on the same machine as System Platform IDE often resolves these issues, suggesting potential network or configuration challenges in distributed setups.

also here

Integrating Kepware with AVEVA's System Platform can present certain challenges. Notable issues include:

  1. DCOM Hardening Patches: Microsoft's Distributed Component Object Model (DCOM) hardening updates have impacted OPC-DA communications, affecting components like FS Gateway and connections to Kepware. These patches enhance security but may disrupt existing configurations. AVEVA has provided guidance on addressing these changes, recommending registry adjustments and thorough testing in non-production environments.

  2. Compatibility Concerns: There have been reports of compatibility issues between KEPServerEX and AVEVA System Platform 2023. Users have experienced challenges in establishing seamless communication between the two platforms. PTC has acknowledged these concerns and is investigating to provide solutions.

  3. System Failures: Instances where Kepware software ceases to function after a system failure have been documented. Such failures can corrupt the software or its licensing. The recommended solution involves reinstalling the Kepware software and, if necessary, contacting technical support for license reactivation.

My question is:  do we have some others here on this forum that have info or experiences related to something similar?

Parents
  • Hi   , I have done the exact above but with a slight change, I moved from OPC DA to OPC UA ( which Kepware and SP 23 support at no additional cost ) and problem solved. The issue you have stated is not Kepware or AVEVA but it's a Microsoft issue no longer supporting OPC DA without compromising on security

  • ok, thank you!

    did you start by using the ddesuitelink object? How did the issues look?

    I am referring to a problem related to the ddsuitelink object:

    • An issue has been observed with multiple versions of KEPServerEX / ThingWorx Kepware Server when interacting with Aveva System Platform 2023 when using the FastDDE/SuiteLink interface
      • The issue is being investigated 
      • At this time Aveva recommends utilizing OPC UA for connecting to the Kepware OPC UA interface
  • There was bad OPC quality data when the OPC in Kepware worked fine, but i tried a separate OPC client and still didnt work, figured this is not an AVEVA issue

  • ok I am having problems which i think has to do with suitelink connections, I am going to test with opc ua instead. 

  •   hi again, I configured one instance of opcclient to connect to kepware, it works fine, but how do I know if i am using opc da or ua, I assumed I should put the path from the OPC UA server (on the screenshot below .) somewhere in the instance settings.

    This works if I put this data in the opcclient instance , (screenshot below:)

    Is this configured as OPC UA connection?

  • Hi   you need to first add OPC UA connection in Operations Management console 

    Please see the link below for detailed instructions

    https://docs.aveva.com/bundle/sp-appserver/page/689813.html

    I would love to help you further but I need time and currently super busy

Reply Children
No Data