Unified Automation Forum

In datalogger setting, I need to understand what are the follwing parameters:
Publish Interval: what is ? millisecond, apples, bananas, litres?
Keep Alive Count: What is? Count of what? cars, stars, sheep?
Lifetime Count: What is?

Sampling Interval: What is? millisecond, apples, bananas, litres?
Queue Size? size of What? meter, Kilograms?

Thanks in advance for your help

Hi,

as always in OPC UA all duartion values are "milliseconds".
And all count/size values are "per piece" numbers.

The DataLogger view is for demonstrating the monitored item and subscription parameters/settings in OPC UA. Whereas sampling is the scan rate on the source, and publish is the rate transfered to the client, and queue is filled when sampling is faster that publish (to not loose data). The keep alive is the number of publish-durations before an empty publish is sent (in case no velue has changes = keep alive) .

The Datalogger creates a subscription on the server and ask for e.g. the list of MonitoredItems to be sampled (checked for change) with "250ms" interval, and queued into a queue of "10" pieces of DataValues, whereas such queues (when containing values) will be published to the Client/DataLogger every "500ms", and if no changes in value (no content in queue) have occured, at least send a keep-alive after "10" counts of publish intervals (10x500ms meaning 5 seconds), which is an "empty" publish to evidence that the connection is still working.

I agree that some tooltip explanation would be helpful here.

Hi,

as always in OPC UA all duartion values are "milliseconds".
And all count/size values are "per piece" numbers.

The DataLogger view is for demonstrating the monitored item and subscription parameters/settings in OPC UA. Whereas sampling is the scan rate on the source, and publish is the rate transfered to the client, and queue is filled when sampling is faster that publish (to not loose data). The keep alive is the number of publish-durations before an empty publish is sent (in case no velue has changes = keep alive) .

The Datalogger creates a subscription on the server and ask for e.g. the list of MonitoredItems to be sampled (checked for change) with "250ms" interval, and queued into a queue of "10" pieces of DataValues, whereas such queues (when containing values) will be published to the Client/DataLogger every "500ms", and if no changes in value (no content in queue) have occured, at least send a keep-alive after "10" counts of publish intervals (10x500ms meaning 5 seconds), which is an "empty" publish to evidence that the connection is still working.

I agree that some tooltip explanation would be helpful here.