Porovnávané verzie

Kľúč

  • Tento riadok sa pridal
  • Riadok je odstránený.
  • Formátovanie sa zmenilo.

...

Full nameDescriptionUnitDefault value
Kotva
subrpi
subrpi
Requested Publishing Interval

Defines the time interval for the server to send the information about the change of monitored items within the instance subscription by "Publish message".
Note: This parameter defines a proposed value that the OPC UA server can change, e.g. Bernecker-Rainer always returned a value of "Publishing Interval" at least 50 ms, although the requested interval was smaller.

mi:ss.mss00:05.000
Kotva
subrlc
subrlc
Requested LifeTime Count

If the client does not send the request for data till the time defined by (LifeTime Count * Publishing Interval), the subscription expires. The value should be minimally 3 times higher than the "Requested Max KeepAlive Count".
Note: This parameter defines a proposed value that the OPC UA server can change, e.g. Bernecker-Rainer always returned as a value of "LifeTime Count" a maximum of 600, although the requested value was greater.

Number1000
Kotva
subrmkc
subrmkc
Requested Max KeepAlive Count

If the objects of subscription are not changed, the server will send a keep-alive message after elapsing the time (Max Notifications Per Publish * Publishing Interval). The client will confirm this message when it sends a new request for data.
Note: This parameter defines a proposed value that the OPC UA server can change, e.g. Bernecker-Rainer has always returned as a value of "Max KeepAlive Count" a maximum of 200, although the requested value was greater.

Number5
Kotva
mnpp
mnpp
Max Notifications Per Publish
The parameter defines the maximum number of notifications about the object change, which the server can send in one "Publish message". Zero indicates that the number of notifications is unlimited.Number0
Kotva
pe
pe
Publishing Enabled
The parameter enables/disables the publishing within the subscription.YES/NOYES
Kotva
p
p
Priority
It defines a relative priority of a subscription. If the server should send more notifications, the subscription with higher priority is preferred.0-2550

Kotva
mqs
mqs
Samples Queue Size

This parameter enables creating an object queue with the defined length on the OPC UA server's side for each monitored item in a subscription.Number0

Kotva
rt
rt
Read Timestamp

Timestamps used while reading a value:

  • None - timestamp received from OPC server is not used (value will be timestamped by the current time)
  • Source - SourceTimestamp is used
  • Server - ServerTimestamp is used (default)
  • Newer - newer timestamp is used (SourceTimestamp or ServerTimestamp)
-Server

Kotva
wt
wt
Write Timestamp

Timestamps used to write a value:

  • None - no timestamp is set
  • Source - SourceTimestamp is set (equal to the timestamp of written value)
  • Server - ServerTimestamp is set (equal to current time)
  • Both - both SourceTimestamp and ServerTimestamp are set

Note: If the OPC server does not support the writing of timestamps, according to the standard it should return the Bad_WriteNotSupported (2155020288) error code.

-None

Kotva
wsc
wsc
Write Status Code

StatusCode item will be used when writing.
Note: According to the standard, the OPC UA Wrapper returns the Bad_WriteNotSupported (2155020288) error code if the StatusCode entry is used when writing to the OPC DA Server version 2.05a.
YES/NOYES

Kotva
wwa
wwa
Write Whole Array

When an item of an array is written, the entire array is read first and then written. If this parameter is set to NO, only a specific array item is written,
Note: According to the standard, if the OPC server does not support writing a specific array item, it should return the Bad_WriteNotSupported (2155020288) error code.
Note: If this parameter is active, the "Write only" parameter must not be set at the I/O tag which addresses an item of the array.
YES/NONO

Kotva
aot
aot
Accept Older Time

Values that are not older than the specified time interval (compared to the timestamp of the current value of the I/O tag) will be accepted. After writing, it may happen that the value read back is older (usually by several ms) compared to the time of writing unless the communication computer and the OPC UA server have exact time synchronization. Error messages may appear in the line log:
Ignoring value for I/O tag <name>, current timestamp=<current_time> is newer than received <old_time>
Increasing the value of the Accept Older Time parameter will cause such older values to be processed and the error message to be suppressed.

hh:mi:ss00:00:00

Kotva
rm
rm
Read Mode

A way of reading values:

  • Subscribe: communication via subscriptions and notifications (standard)
  • Subscribe + Read: like Subscribe, in addition, periodic Read requests are sent (according to the time parameters of the station)
  • Read: send Read requests only

Note: The Subscribe+Read and Read modes should only be used if there is a problem with standard communication, as they are less efficient and have a higher overhead.

Subscribe
Subscribe+Read
Read
Subscribe

Kotva
nf
nf
No Filter

Ignoring filter parameters in the I/O tag configuration (Sampling type, DeadBand type, Trigger type).
In the specific case, the OPC UA server did not work correctly if monitored items with the specified filter parameters were inserted into the subscription.

YES/NONO

Kotva
mpp
mpp
Max Pending Publish Requests

The maximum number of consecutive unconfirmed Publish requests (to which OPC UA server does not reply with a Publish Message), after which the connection will be closed. A value of 0 causes the connection to not be closed.
Note: This parameter can be used to speed up the detection of a broken connection to the OPC UA server.
-0

...