Bus-Profi Forum

Mir ist es aufgefallen das Bineingänge nicht richtig angezeigt werden. Die werden nur beim ersten mal richtig eingelessen und bleiben eingeforen. Die Eingänge werden nach paar Minuten später aktuallisiert.Kann schon einige 5 Minuten dauern.

Im Display von der Domiq/Base werden die sofort Eingänge über den PC richtig animiert.

Kann mir einer sagen warum das so ist.

Ich lese folgende Binärausgänge ein
LCN.sensor.0.10.1
LCN.sensor.0.10.2
LCN.sensor.0.10.3
LCN.sensor.0.10.4

Can you post a printscreen with configuration of an examplary control?

Hallo,

das gleiche Verhalten habe ich bei meinem Impulszählerwert, der so konfiguriert wurde:

[img]1[/img]

gehen tut bei mir (mit einer leichten Verzögerung) der Binäreingang im Remote und so koniguriert wurde:

[img]2[/img]

Grüße

Xtof

Hallo

Es werden die Bin-Eingänge verzögert im Display-Mode oder Remote-Mode angezeigt.

Die Einstellungen habe ich angehängt.

Remote-Mode - Bineingang
[img]1[/img]

Display-Mode ist mit eiin Licht - Element
[img]2[/img]

Try to use the Status control instead of binary sensor.

The Status Control reacts much faster and works for single binary values.

However I did a lot of testing trying to find out where the delays come from.
It seems that the variables are not refreshed in the base for quite a while (sometimes some minutes).

This is my test:
I changed the counter variable LCN.value.0.51.t through LCN-PRO or by hardware and observed the reaction on the LOGIC-tab of the base and in paralel on Remote



In fact it takes a long time until the change is printed to the output window and then displayed in Remote by the Text Control (Channel: MEM.HeatingEnergy).

To find out, if it is the onchange-Event which is slow, I tried to read on each tick:




I can see my change in the LCN-PRO observation immediately while the ontick-function prints the old value for a long time (seconds to minutes) until it refreshes.

I would appreciate a faster refresh rate here to get a more fluent HMI interaction and being able to react in LUA in a timely manner upon changes.

Best regards

Xtof

It's normal behaviour that LCN.value identifier refreshes in couple of minutes. We don't update it in realtime. In order to update it we need to query LCN module about specific variable. And as you can imagine querying every module and every variable in few seconds intervals would be impossible:)

Of course you can not query each and every variable in realtime, but my expectation was that I can start a query of a dedicated variable with the get('varName') command. Base could use this request for a event based query of just that variable. It somehow works with binary values quiet fast.

When I run Display on an iOS device I can see text in MEM-variables generated upon LCN-Events almost immediately. And I am talking about a lot of text which is displayed.
Besides: There are solutions e.g. for PLCs which have a mechanism for exactly these problems (ADS-Server, Libnodave...)

No plans for an improvement?

Xtof

You can query LCN variables explicitly by calling LCN.query command - I don't know why, but it's not described in documentation:confused:
The syntax is as follows: LCN.query.S.M.V=query, where S - segment, M - module, V - variable (t,r1 or r2). So examplary command should look like this:
LCN.query.0.16.t=query
If value has changed since last query, then event will be dispatched (you can create E.LCN.value event to listen).
You can also use other version of LCN.query command, which has the following syntax:
LCN.query.S.M=values/sensors/relays (you need to choose one of them).

This is exactly what I asked for and it works!
I use the ontick() event to trigger this query.
Now the value refreshes much faster.

Thanks for making this hidden feature available.

Xtof