Problem with Simple Timer - in relation with CM11 Plugin

[mhund]

Hello,

sorry for serving more and more bug reports:

While a simple timer is aktiv (means startet and not finished), G4 seems to wait for the end of the timer and caches at least all incoming x10-events. Some seconds before the timer runs out, the cached events are comming allt together at the same time.

When no timer is running, everything seems to be fine.

Can you reproduce this?

[Ron]

please supply a gml demonstrating this with as little actions as possible. I didn't test with X10 events but keyboard events seem to come in normally.

[mhund]

It seem to deal with x10 issues. The timer is shot by a x10 event. And I use a x10-remote with the generic x10 plugin in combination with CM11g and the CM1x plugin. Strange. When I find out more about this, I will post it here. To send my gml-File to you will not help because you will not have my specific environment. Its real komplex ...

[Ron]

Alright let me get this straight.

1. Events comes in from the Generic X10 Remote plugin
2. This trigger an action
3. This action is a Simple Timer start
4. Now no more Generic X10 Remote events come in?

[mhund]

1. Events comes in from the Generic X10 Remote plugin
2. This trigger an action
3. This action is a Simple Timer start
4. Now no more Generic X10 Remote events come in?

yes. Thats right. To analyse the issue I changed the process a little bit: I changed the triggering events coming from cm11 now instead of generic x10 (Both plugins receive the radio x10-signals coming from some moving detectors :roll: ). Now The behavior has changed a little bit: The caching is rarely now. Much better but not totaly realtime. Strange ...

I dont see the relation to the simple timer funktion. But when no timer is active, everything is fine :(

[Ron]

Can you run this GML and see if the trouble is caused by this too?

You might have to reassign the events, but please only use the generic x10 remote events.

[mhund]

I changed some things and I can reproduce it. But you need some x10 things :wink: because it happens only, when the triggered actions are x10 actions.

One question: Wy did you implement this generic X10 stuff in G4 and additionally the CM11 plugin? What is the relation or the difference? I see events from both devices (logger says "x10" and "x10 cm1x") and I see two different action groups for X10 stuff

[Ron]

Thanks, I'll check it out right away.

Basically those are two totally different system. For me they don't interact at all.

[Ron]

I think I see what you mean, this looks like the CM11 plugin working on the main thread. Meaning it appears to be blocking Girder's main thread until it is done with it's thing.

[mhund]

Sounds clear. Is there a chance to change this? Is it in your hands?

Thanks for your excellent help, in either case !!!!

[Ron]

Yep, confirmed, the CM11 blocks waiting for a previous command to go out. Note sure if I can solve this without tearing up some major sourcecode.

[Promixis]

Yep, confirmed, the CM11 blocks waiting for a previous command to go out. Note sure if I can solve this without tearing up some major sourcecode.

How long is it blocking for?

The PowerLinc Serial does this async but I am not sure the PowerLinc USB does this. The CM15A does not quueu commands but I am not sure the COM object blocks ...

[Ron]

~1-2 seconds. Just enough to be annoying.

[mhund]

Cheer up! :wink: Would be nice to have this optimized

Alternativly I could use the second X10-Plugin. It seems to work too :) But at the bright/dim-command, I can only select values 1-16 which is interpreted as percent from my x10 devices. Why can I not select values up to 100?

[mhund]

~1-2 seconds. Just enough to be annoying.

in extrem cases like I got (X10 serves triggering event; all timer-related actions are x10 ones, and the delayed actions are X10 too) there are not 1-2 seconds but 10 - 20 seconds. :cry:

[Ron]

.. i've got something... I'll try to get it out today, maybe tomorrow.

[mhund]

You are my hero!! :D

[Ron]

:-) Try this one.

[mhund]

You did it. :D Seems to work well. I will observe the long term effects but I think you can put it in your next public release.

Thanks a lot. :D