...
| Full name | Description | Unit | Default value | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Defines the time interval for the server to send the information about the change of monitored items within the instance subscription by "Publish message". | mi:ss.mss | 00:05.000 | ||||||
| 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". | Number | 1000 | ||||||
| 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. | Number | 5 | ||||||
| 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. | Number | 0 | ||||||
| The parameter enables/disables the publishing within the subscription. | YES/NO | 0 | ||||||
| It defines a relative priority of a subscription. If the server should send more notifications, the subscription with higher priority is preferred. | 0-255 | 0 | ||||||
| This parameter enables to create the object queue with the defined length on the OPC UA server's side for each monitored item in a subscription. | Number | 0 | ||||||
| Timestamps used to write a value:
Note: If the OPC server does not support writing of timestamps, acording to the standard it should return the Bad_WriteNotSupported (2155020288) error code. | - | None |
| Kotva | ||||
|---|---|---|---|---|
|
...