Skip to main content
F
FZ_144411004-Participant
4-Participant
February 6, 2026
Solved

FTVIew SE 16 and OPC UA

  • February 6, 2026
  • 1 reply
  • 99 views

We are currently experiencing a performance issue with our OPC UA communication. We have an application developed in FactoryTalk View SE version 15, which displays several graphical screens that rely on data coming from Kepware 6 through an OPC UA connection.

The problem is that the graphical elements take a long time to receive updated information from Kepware. The data refresh rate is significantly slower than expected, causing delays in the visualization of real‑time values.

We would like to understand what could be causing this slow performance and what actions we can take to improve the responsiveness of the OPC UA communication. Specifically, we are looking for recommendations to optimize OPC UA settings, data update rates, server load, or any other configuration that could help increase the communication speed between Kepware and FactoryTalk View.

Best answer by MKhatri

Greetings!

 

Kepware‑focused explanation of what typically causes slow OPC UA updates between Kepware 6.x 
and FactoryTalk View SE v15, along with actionable tuning steps, all supported by the search results you provided

 

Slow data refresh is almost always caused by one or more of the following
   Kepware scan rates being too slow
   FactoryTalk View SE Group Update Rates
   High server CPU load or too many tags updating too fast
   Faulty or overloaded FactoryTalk service

Regards,
Mohit

1 reply

M
MKhatri15-MoonstoneAnswer
15-Moonstone
February 20, 2026

Greetings!

 

Kepware‑focused explanation of what typically causes slow OPC UA updates between Kepware 6.x 
and FactoryTalk View SE v15, along with actionable tuning steps, all supported by the search results you provided

 

Slow data refresh is almost always caused by one or more of the following
   Kepware scan rates being too slow
   FactoryTalk View SE Group Update Rates
   High server CPU load or too many tags updating too fast
   Faulty or overloaded FactoryTalk service

Regards,
Mohit

Terms & ConditionsCookie settingsAccessibility statement