Tag values from OPC UA Servers update slowly

The

OPC

UA Server service is out of system resources.

Use

Windows

Resource Monitor to determine how much CPU capacity is used by the

OPC

UA Server service. If the

OPC

UA Server service uses 100% of host CPU capacity, move the service to a host with higher CPU performance. For best performance, use high power Server hosts instead of embedded controllers.

Use

Windows

Resource Monitor to determine how much Memory capacity is used by the

OPC

UA Server service. If the

OPC

UA Server service uses 100% of host Memory capacity, move the service to a host with higher Memory capacity. For best performance, use high power Server hosts instead of embedded controllers.

Use

Windows

Resource Monitor to identify services that may be competing for system resources with the

OPC

UA Server service. Disable unnecessary services on the

OPC

UA Server host, or move the

OPC

UA Server service to a dedicated host. For best performance, use high power Server hosts instead of embedded controllers.

The

FactoryTalk Linx

OPC

UA Connector service is out of system resources

Use

Windows

Event Viewer to determine if the

FactoryTalk Linx

OPC

UA Connector service crashed or was closed due to insufficient system memory.

Use

Windows

Resource Monitor to determine how much CPU capacity is used by the

FactoryTalk Linx

OPC

UA Connector service. If the

FactoryTalk Linx

OPC

UA Connector service uses 100% of host CPU capacity, move the service to a host with higher CPU performance. For best performance, use high power Server hosts instead of embedded controllers.

Use

Windows

Resource Monitor to determine how much Memory capacity is used by the

FactoryTalk Linx

OPC

UA Connector service. If the

FactoryTalk Linx

OPC

UA Connector service uses 100% of host Memory capacity, move the service to a host with higher Memory capacity. For best performance, use high power Server hosts instead of embedded controllers.

Use

Windows

Resource Monitor to identify services that may be competing for system resources with the

FactoryTalk Linx

OPC

UA Connector service. Disable unnecessary services on the

FactoryTalk Linx

OPC

UA Connector host, or move the

FactoryTalk Linx

OPC

UA Connector service to a dedicated host. For best performance, use high power Server hosts instead of embedded controllers.

Spread the

OPC

UA Server load across multiple

FactoryTalk Linx

OPC

UA Connectors. In the same application, create a new

FactoryTalk Linx

OPC

UA Connector hosted on another host. Remove

OPC

UA Servers from the

FactoryTalk Linx

OPC

UA Connector host that is out of system resources. Then, add the

OPC

UA Servers to the

FactoryTalk Linx

OPC

UA Connector on new host. Update tag browse paths in the

FactoryTalk

client application to use the new

FactoryTalk Linx

OPC

UA Connector path.

Other network traffic disrupts

OPC

UA Server packets

If the

FactoryTalk Linx

OPC

UA Connector or

OPC

UA Server is on a network with a ring, bus, or DLR topology, move it to a network with a star topology.

If the

FactoryTalk Linx

OPC

UA Connector or

OPC

UA Server is on a network carrying high priority or high velocity traffic, such as motion, video, or voice traffic, move it to an isolated or lower traffic network.

OPC

UA Server packets are dropped

Verify network continuity between the

FactoryTalk Linx

OPC

UA Connector workstation and

FactoryTalk

OPC

UA Server host.

If the

FactoryTalk Linx

OPC

UA Connector or

OPC

UA Server host is connected to a Wi-Fi network, move it to a 100 Mbit or higher Ethernet network.