Re: [milo-dev] eclipse milo - there are too many data updates from serve

[Lenovo K3 Owner <lenovo.k3.1.owner@xxxxxxxxx>]

Thanks, Kevin

Here is how I subscribe for items:

                //and subscribe as usually
                MonitoringParameters parameters = new MonitoringParameters(
                        clientHandle,
                        (double) 1000,     // sampling interval
                        null,       // filter, null means use default
                        uint(10),   // queue size
                        true
                );

                MonitoredItemCreateRequest request = new MonitoredItemCreateRequest(readValueId, MonitoringMode.Reporting, parameters);

I don't see here anything suspicious.

But just to make it clear how the client works - we specify publish_interval (when making subscription) and client makes publishRequests with specified frequency 1000 milliseconds. 

And the server sends us updates in response to each individual publish request. As a result the server cannot send anything faster than the client asks for data ?

And even if this happens, will the client ignore this response as unexpected ? 

---

Mikalai

On Tue, Jul 14, 2020 at 7:08 PM Kevin Herron <kevinherron@xxxxxxxxx> wrote:

This behavior is something the server is responsible for. Whether that is correct or not probably depends on the sampling interval, queue size and DataChangeTrigger trigger you configured your items for.

On Tue, Jul 14, 2020 at 7:45 AM Lenovo K3 Owner <lenovo.k3.1.owner@xxxxxxxxx> wrote:

Hello Milo-dev

We are using a milo client to connect to zenon server using UaSubscriptionManager:

 subscriptionRef = client.getSubscriptionManager().createSubscription(1000).get();

Recently we noticed a strange situation when the server began to send us data updates too frequently (see logs excerpt below).

value received: item=NodeId{ns=2, id=aaa}, value=Variant{value=33.97} at source time 2020-07-13 14:58:25.594 and server time 2020-07-13 14:58:25.636

value received: item=NodeId{ns=2, id=aaa}, value=Variant{value=33.97} at source time 2020-07-13 14:58:25.594 and server time 2020-07-13 14:58:25.640

value received: item=NodeId{ns=2, id=aaa}, value=Variant{value=33.97} at source time 2020-07-13 14:58:25.594 and server time 2020-07-13 14:58:25.643

You may see that source time of data did not change at all and server time changes by matter of milliseconds (2 and later 3 milliseconds).

So right now we are puzzled by the possible reason behind these influx of data notifications: is it something that we can manage on client side or its purely on the server side.

---

with best regards

Mikalai

_______________________________________________
milo-dev mailing list
milo-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/milo-dev

_______________________________________________
milo-dev mailing list
milo-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/milo-dev