Default Timestamp Source for new OPC-UA connections

Ignition
1

Ignition 8.3.1 introduced the new timestamp source setting (OPC_PREFER_SOURCE). This must be configured individually for each OPC-UA connections. The default for new OPC-UA Connections is Ignition_Source.

Is anyone aware of an existing way to always set OPC_PREFERE_SOURCE as the default (beside using a script to create the OPC UA Connection?

Thank you,
André

2

Really? This was a mistake... maybe a UI/frontend thing, because in the definition of the config object on the backend it's OPC_PREFER_SOURCE.

3

Tracking this as IGN-15585.

1 Like
4

@Kevin.Herron The configuration says OPC_PREFERE_SOURCE. Is our assumption correct, that when the OPC-UA server does not provide a source timestamp, Ignition will fallback to Source Timestamp IGNITION? If this is the case: Can we disable this functionality or can we see somewhere that a fallback happend?

Thank you!

5

The order of preference has always been:

  1. OPC Source
  2. OPC Server (if source not available)
  3. Ignition (if neither available)

You’re just choosing a starting place in this list with that setting. A timestamp will always be chosen; the Ignition tag system needs one.

There is no indication which one was chosen.

There will always be an OPC Server timestamp available unless you're dealing with a server with a broken implementation.

The primary use case for this setting is to change timestamp source to IGNITION when you're dealing with a server that has not had its time synchronized yet. Ideally it's temporary, because a relatively synchronized clock is a baseline requirement for all OPC UA applications.

Secondary use case would be if your server is reporting values from some downstream source (DNP3, another OPC UA server, etc...) that has its own timestamps, in which case the downstream timestamps usually end up in the OPC UA SourceTimestamp, and for some reason you don't want those and would rather use the OPC UA ServerTimestamp.

2 Likes