Originally Posted by Peter M
That's very odd. I hoped that this would be straight forward ! We never give up in the Demopad thread !!
You don't say what delays you'e tried, but if I was setting this up I'd probably go with 2 secs repeat on the macro call and in the macro -
0.0 PannyResponse = OFF
1.0 PannyPwr = ON depends on PannyResponse = ON
1.0 PannyPwr = OFF depends on Pannyresponse = OFF
This should allow plenty of time for the Mute query to set PannyResponse = ON.
If this doesn't work then I suggest you post some screen shots so we can check your settings.
Well guys you goaded me to get back to the keyboard. I was just voicing my fatigue and frustration in the moment. After 40+ years in R&D it's not my nature to give-up and we never really cross the finish line in a project like this. I am just neglecting my other hobbies (classic cars) and with spring here in the North, it's time for me to get out and about.
With your and mpg7321 suggestions, I got it working. It is definitely a timing issue, and maybe the dreaded "Off-By-One-Bug" as well, but I need to experiment more to confirm if it is indeed a bug or just a timing artifact.
Here is my solution: I set the repeat frequency in the Page_Load Actions to 5 sec. for the macro call and I call the macro twice in succession(If I only call it once it won't work). I also used the delays Peter M suggested. I had tried similar delays in the past, but without the successive macro call. I found that I need both, but now it works great, no periodic flashing button. It does take a few sec. to get the button to light on or go off, but not an intolerable delay by any means.
The potential bug may turn turnout to just be timings also, but I have found in other Page_Load Actions, that I need to call the last command in the sequence twice to get it to respond which is I why tried the idea using the successive macro call. Strangely with the macro call it doesn't seem to matter where in the sequence it is called, however it must be called twice in succession to work and why I am not 100% sure it is bug or just timing. Now I do have quite a number (10-15)of device queries as startup actions on some pages and they do repeat(.5 -1.5 sec) so things could get overloaded, a buffer overrun etc, but nonetheless if I call the last command twice in sequence on these pages, the command executes. Further I removed a number of the Page_Load actions on this particular page but saw no benefit so I need to look into this a bit more when I have some time.
For now at least this problem is solved and I can go play with my cars.
Thanks again to both of you.
EDIT: As I was typing my response a couple of other thoughts occurred to me and I could not resist trying them out. Instead of calling the macro twice from Page_Load Actions, I instead added a 2nd QueryMute command in the macro and only called the macro once from the Page_Load actions. Sure enough that works, however I get intermittent button flashing. Not periodic but intermittent. I think the commands and responses get out of sync or overlapped and this is the result. I see this as well if I double call the macro from Page_Load Actions using too small of a repeat, hence my choice of 5 sec. ( and it still happens even with 5 sec but at such a long interval as to be unimportant). There seems to be high latency in the system, which may be related to the Panny but I'm not ruling out DemoPad just yet. I'll know better when I fully implement the same approach on the HTPC. If I see the same issues there then I would conclude it is a DemoPad issue, otherwise likely just related to the Panny.
EDIT2: Its the Panny and its latency that are causing the issues. No problem at all with the HTPC.