Page 1 of 1

Extender Macro delay problem - help?

Posted: Wed Apr 14, 2004 11:39 am
by chas6000
Thanks to all who have helped me get this far!

I have gotten rid of all my learned codes (into keymoves) and have installed the extender and things work!

But i am having trouble with putting in delays in macros - things are going to fast for my TV to respond correctly.

9910 remote
8910ex1._1 extender
extInstall_3

i have tried unprogrammed keys like the included readme suggests. i have tried using keymove to define a MISC/1104 pause with different hex code time lengths. i dont see anything different with the way the TV responds to the macro.

below is a link to the IR file as it exists.
file

Posted: Wed Apr 14, 2004 12:26 pm
by The Robman
Please read the sticky post about posting links to yahoo files, then fix your link

Posted: Wed Apr 14, 2004 1:36 pm
by chas6000
The Robman wrote:Please read the sticky post about posting links to yahoo files, then fix your link
Thanks Rob -- I fixed it in the original post ...

Posted: Wed Apr 14, 2004 3:45 pm
by Nils_Ekberg
Try replacing the TV in the beginning of the M2 macro with DEV_TV and see if that makes a difference. Not sure it will.

Then create this macro on XShift-Phantom3 and delete the pause keymove:

Shift-Phantom2;Shift-Phantom2;Shift-Phantom2;Shift-Phantom2;Shift-Phantom2

And see if that makes a difference since I remember something in the past that the 8910/9910 extender pause does not create much of a pause.

Posted: Wed Apr 14, 2004 3:54 pm
by chas6000
Hello Nils -- i tried both your suggestions and they did not seem to change the behavior or timing. still does not complete and moves very fast through what it does do. anything else to try?

Posted: Wed Apr 14, 2004 4:05 pm
by Nils_Ekberg
Try replacing the PAUSE device upgrade and protocol with these and see if this helps.

DEVICE UPGRADE (Copy and paste the following bolded text to replace the existing MISC/1104)

Upgrade code 0 = 0C 50 (TV/1104)
FB 00 01
End


PROTOCOL UPGRADE (Copy and paste the following bolded text to replace the existing 01 FB protocol)

Upgrade protocol 0 = 01 FB (S3C80)
00 00 01 E4 03 C2 C6 C0 00 00 0A FE 1A FC 2A FA
AF
End

Posted: Wed Apr 14, 2004 4:17 pm
by Nils_Ekberg
I am also assuming that since the M2 macro is the only one using the PAUSE and M2 is not called by any other keymove or macro, that you are just pressing the M2 and not seeing any differences. Correct?

Posted: Wed Apr 14, 2004 4:21 pm
by chas6000
Thanks again Nils - but no change - still executes fast and stalls after first 2 or 3 commands

Posted: Wed Apr 14, 2004 4:24 pm
by chas6000
Yes Nils- the M2 is the only one im messing with and this is the one giving the observations im reporting

Posted: Wed Apr 14, 2004 4:37 pm
by Nils_Ekberg
Let me think about this on my drive home and see if I come up with anything. I may even try it myself and see what I get.

Try putting the PAUSE on the Shift-Pause button in TV and change your M2 macro to Shift-Pause (instead of Xshift-Phantom3) just to rule out the Xshift

By the way, with the one I gave you $FF will make it look like it stalled since that is very long for that protocol

Posted: Wed Apr 14, 2004 4:40 pm
by chas6000
Thanks Nils - i will try your suggestions - i have tried various timings from 10 to 30 to ff and using 10 or 20 for the recent trials

Posted: Wed Apr 14, 2004 4:50 pm
by chas6000
Hello Nils -- shift-pause works!! but only with the protocol you gave me - not the one included with the upgrade

so i can work with this now - but why is there a diff between this and the other way with xshift-phantom3??

Posted: Wed Apr 14, 2004 5:47 pm
by Nils_Ekberg
chas6000 wrote:Hello Nils -- shift-pause works!! but only with the protocol you gave me - not the one included with the upgrade

so i can work with this now - but why is there a diff between this and the other way with xshift-phantom3??
I am glad that worked for you. Before Paul was nice enough to put notes and protocol names in IR I always put my pause functions on Shift-Pause so I would remember what the keymove was for and I know it works.

By the way, the pause in the package does work but does not generate long enough pause for most uses.

Since I did not write the 8910/9910 extender or even reviewed it lately I am not sure how it handles xShifted buttons but in all extenders there is extra code for handling them. I will try to take a look at the code or maybe David (who wrote the extender) will see this and offer a reason.

So anyway, since we tried everything else and I was confident with the way you had it set up I just wanted to try the last thing I suspected. Sometimes debugging is just a matter of hit and miss until you hit on what works.

Posted: Wed Apr 14, 2004 5:53 pm
by chas6000
Well i thank you Nils for all your help -- and thanks to all the rest of the community who have helped me get this far! great group!