2116 Device type change

throgm · Post by **throgm** » Sun Dec 28, 2003 5:20 pm

Well, I think we're making progress. The loop has stopped but I'm only getting 1 FFWD. The light on the remote is blinking twice but it's only sending one.

usblipitor · Post by **usblipitor** » Sun Dec 28, 2003 5:24 pm

ok, try it now, i added a long delay in the macro. if the macro works, you might try shortening the delay as much as you can and still have it work reliably.

throgm · Post by **throgm** » Sun Dec 28, 2003 5:54 pm

It didn't seem to make any difference. The timing between the light flashes appears about the same.

Actually, I tried that very change after your last update. I knew we just had to get an extra few ms of pause in between the FFWDs. Can you think of any other way to accomplish this?

throgm · Post by **throgm** » Sun Dec 28, 2003 6:03 pm

Dude! I did it. I created another macro for phantom2 with contained 15 DEV_AUX. I filled the FFWD macro with that and now the pause is actually too long but I can back it off and all will be well.

I need to acknowledge that I didn't get here without a whole bunch of your dedication and assistance. Thanks. But it was intriguing, wasn't it?

JP1 rulez!
Jim

throgm · Post by **throgm** » Sun Dec 28, 2003 6:26 pm

You're not going to believe this. First let me say that AUX is associated with my Tivo unit. Anyway, now that I have the FFWD working as I like .. the move button used to perform the Tivo/advance function. Now it turns on my TVs timer setup. I tried remapping it to AUX but it didn't work. I'm assuming that it's a punch-thru feature built into the extender somewhere. I see nothing in the .txt file that would cause this. Am I just not supposed to use the extender? I'd much rather work it out but I'm still learning what a lot of this stuff means.

usblipitor · Post by **usblipitor** » Sun Dec 28, 2003 6:38 pm

the move key is a member of the PIP key group.

you must associate the tivo device to the pip key group. or maybe I should say you should associate the pip key group with the tivo device.

when the pip key group is associated with the tivo, it will cause the move key to do the tivo advance function; when the pip key group is associated with the tv, it will cause the move key to activate your tv's timer setup..

it is not a punch through problem, as the punch through features are all non-existant in extenders, just as the home theater mode is gone in extenders. you have to associate the key groups you want with the devices you want for all this to work.

at least, this is what it sounds like is wrong to me. i could be wrong. i am usually wrong. I am probably wrong in this case. 8)

throgm · Post by **throgm** » Sun Dec 28, 2003 6:48 pm

Cool, dude. That was all it was. Thank you so much for devoting the time to help me through this. I've learned a lot today. And I want to thank you for that, too.

If I post "usblipitor is the man!" in this email in this forum, does it make it official? If nothing else, it'll be documented for whenever you want to recall it as proof.

You da man, man!
Jim

usblipitor · Post by **usblipitor** » Sun Dec 28, 2003 6:55 pm

Glad you got it working. In your AUX macro you just needed to add a SET_PIP_KEYS to the other "SET" keys, which is what I am guessing you already did to make it work.

Good Job!

___________________
Got JP1?
-Steve

throgm · Post by **throgm** » Sun Dec 28, 2003 7:03 pm

Well, you're wrong again. What I did was changed "My system PIP device" to AUX under Other Settings. The method you described sounds more appropriate so I removed SET_PIP_KEYS from phantom1 and added it to AUX.

So many ways to do almost meaningless things.

I hope I don't discover any more problems.

Post by **The Robman** » Sun Dec 28, 2003 7:41 pm

The thing with extenders is they certainly give you enough rope to hang yourself. Of course, the reason we need extenders is because UEI doesn't trust us to be able to program our own remotes!