• State Not Answered
  • Replies 1 reply
  • Subscribers 62 subscribers
  • Views 35 views
  • Users 0 members are here
Options
Related

TCP/IP Client Communication

Vishal Yadav

Hi

I want to make the communication between two Aveva Edge 2023 SCADA System through TCP/IP like Heartbeat and Status. and I have configured TCP/IP Client worksheet at Client side; now do I have to configure anything at server side or not. And how I can pick Heartbeat at server?

Parents
  • 0

    I'm not to sure about the tcp/ip configuration.

    However, have you considered enabling one of your AVEVA Edge applications as an OPC UA server? You can look into the Help menu for guidance, which provides a step-by-step guide on setting it up.

    Once that’s done, configure the other Edge application as an OPC UA client, and connect it to the server instance. From there, you can browse available tags, including built-in system tags like "BlinkSlow" to use as a simple heartbeat signal. Alternatively, you can create a custom heartbeat tag that toggles at a set interval and monitor that instead.

Reply
  • 0

    I'm not to sure about the tcp/ip configuration.

    However, have you considered enabling one of your AVEVA Edge applications as an OPC UA server? You can look into the Help menu for guidance, which provides a step-by-step guide on setting it up.

    Once that’s done, configure the other Edge application as an OPC UA client, and connect it to the server instance. From there, you can browse available tags, including built-in system tags like "BlinkSlow" to use as a simple heartbeat signal. Alternatively, you can create a custom heartbeat tag that toggles at a set interval and monitor that instead.

Children
No Data
© 2025 AVEVA Group Limited or its subsidiaries. All Rights Reserved.