Recording of OPC UA symbols

	The function of recording symbols via OPC UA is available only with a Scope View Professional license.

In principle the recording of signals via OPC UA can be started as usual via the Start Record button.

However, you should note the following special features:

Sample Time: When recording OPC UA symbols there is no task sample time as with ADS symbols. The sample state is thus always set to "Free Sample". Therefore, set the desired sample time before starting the recording. Select only sampling rates that are also supported by the respective OPC UA Server. Otherwise an error message will appear when starting the recording and the sample time will be changed automatically to the sample time returned by the OPC UA Server.
Oversampling: For arrays it is also possible to use the oversampling function with OPC UA. However, since there is no task sample time and the oversampling actually refers to the task sample time, the interpretation does not correspond to the conventional oversampling with ADS. In the interpretation of the measured data this must be taken into account in particular with free sample times, which deviate widely from the actual task sample time.
Encrypted and/or authenticated connections: If the measured data are recorded by means of an encrypted and/or authenticated OPC UA connection, some further steps have to be performed following the first actuation of the Start Record button. More precise information on this can be found in the sections Encrypted connections and Authenticated access.
Determinism: The intervals between the data points that are transmitted via OPC UA correspond approximately to the set sampling rate. However, it is not necessarily to be expected that all data points are really equidistant as in the case of ADS. There may very well be deviations of 1-2 ms.
Missing data: If "gaps" should occur in the data when recording data via OPC UA (the interval between the data points is not equal to the set sample time), this may be due to the respective OPC UA Server and/or the quality of the connection. In this case, check the Scope Server log if necessary.