Need help with long duration power key

Support forum for extenders. If you're having trouble getting one up and running, this is the place to come.

Moderator: Moderators

Post Reply
ripple
Posts: 11
Joined: Fri Feb 20, 2004 12:31 am

Need help with long duration power key

Post by ripple »

I have a URC-8910 using Extender 1. My Panasonic LCD TV (TV/250) seems to need a longer duration power key signal when it first starts up. It would power on if I physically push the power key when initially starting up, but not when I used the power key in a macro. I eventually determined that the 8910 extender must be sending the power code too quickly to wake it up.

Most of the forums I looked through suggested using the Device Combiner protocol to create a longer duration power code so I tried implementing it. Unfortunately every time I try to use it, my 8910 locks up (solid red light). This is my first try at Device Combiner so I could use some help to steer me straight.

Here's the steps I did, maybe you can see where I went wrong:

1. In KM, I created an upgrade for Device Combiner protocol and called it TV/1252

2. Since my TV is TV/250 with Panasonic protocol, for index 0 in the combiner table I used the Protocol ID=00 c9 and Fixed Data=FE BF FB FE FF

3. On the functions tab I defined the power key to use index 0 and have 5 times the normal duration:
EFC=024
byte2=0 5
hex=50 43

4. This resulted in the upgrade code below:
Upgrade Code 0 = 0C E4 (TV/1252)
44 00 11 00 00 50 43
End
which I pasted into IR. (I also pasted in the protocol code 0144)

5. In IR, I assigned the unused device button CD to 1252 (Do I need to even do this?)

6. The I created a KeyMove so that if I push L2 while in TV mode it will send a long duration power code:
Device Button=TV
Key=L2
=
Device Button=CD
Device Type=TV
Setup Code=1252
Hex Cmd=$50 $43
EFC or Key Name=51334

7. Upload to remote, activate extender, push TV, push L2 and red light stays on.

What am I doing wrong?

my IR and KM files

Thanks,
Kevin
e34m5
Posts: 675
Joined: Tue Oct 14, 2003 1:04 pm
Location: Atlanta

Post by e34m5 »

Try this.

Create a key move like this:

Bound Device: TV
Bound Key: REC
Device Button: VCR
Setup Code: 0039

Basically this is the record command for Zenith. Since there is no REC for TV all it really does is introduce a delay.

You can then use this as on of the steps in your macro. You may have to use several of these in a row to obtain the necessary delay.

There is also a delay protocol available but I was never able to get the proper delay values to work.

BTW, the situation with your TV is very common.
Paul
ripple
Posts: 11
Joined: Fri Feb 20, 2004 12:31 am

Post by ripple »

e34m5 wrote:You can then use this as on of the steps in your macro. You may have to use several of these in a row to obtain the necessary delay.
Maybe I wasn't clear on the problem I'm trying to solve...I'm not looking for a pause or delay between keypresses, I'm looking to "hold the power key down" and send the power code for a longer time. In my power-up-everything macro the TV doesn't see the power up code at all when the TV has been off for a long time. If I've just turned the TV off and use that same macro, it powers up like it's supposed to. I assume this is due to the fact that the 8910 extender macro is sending the ir signal quickly and the TV doesn't "see" it.

Kevin
gfb107
Expert
Posts: 3411
Joined: Sun Aug 03, 2003 7:18 pm
Location: Cary, NC
Contact:

Post by gfb107 »

Have you tried uaing the power key more than once?

THe other alternative is to use Device Combiner, which allows specifying a duration for each command.
ripple
Posts: 11
Joined: Fri Feb 20, 2004 12:31 am

Post by ripple »

gfb107 wrote:Have you tried uaing the power key more than once?
Nope. I'll try it and see. I was afraid multiple keys would mess up those times when my macro *did* work...
gfb107 wrote:THe other alternative is to use Device Combiner, which allows specifying a duration for each command.
Umm...that's what I'm trying to do (See steps 1-7 in my original post). If you're familiar with Device Combiner can you look at those and see if I'm doing it right?

Thanks,
Kevin
gfb107
Expert
Posts: 3411
Joined: Sun Aug 03, 2003 7:18 pm
Location: Cary, NC
Contact:

Post by gfb107 »

I use RM instead of KM, and when I load your KM file, I get a different protocol upgrade than what I see loaded in your IR file.

Here's my protocol code:

Code: Select all

Upgrade protocol 0 = 01 44 (S3C80) Device Combiner (RM v1.12)
 00 00 22 08 06 96 10 04 90 05 6b 03 e4 05 0d 38
 04 2c ff e7 62 45 e7 32 44 e3 42 e3 52 1c 03 e3
 72 d7 17 1e a2 36 3b f7 97 01 ff 06 d9 02 56 94
 bf c6 ca 01 00 c6 c2 23 82 70 c3 70 c2 c6 da 44
 78 1f 44 13 46 4d 00 c9 fe 3f 7f fe ff
End
Here's what KM produces:

Code: Select all

Upgrade Protocol 0 = 01 44 (S3C8+) Device Combiner (KM v8.30)
 00 00 22 08 06 96 10 04 90 05 6B 03 E4 05 0D 38
 04 2C FF E7 62 45 E7 32 44 E3 42 E3 52 1C 03 E3
 72 D7 17 1E A2 36 3B F7 97 01 FF 06 D9 02 56 94
 BF C6 CA 01 00 C6 C2 23 82 70 C3 70 C2 C6 DA 44
 78 1F 44 13 46 4D 00 C9 FE BF FB FE FF
End
Here's what's in your IR file, as shown by IR 6.01 RC1:

Code: Select all

00 00 22 08 06 96 10 04 90 05 6B 03 E4 05 0D 38 
04 2C FF E7 62 45 E7 32 44 E3 42 E3 52 1C 03 E3 
72 D7 17 1E A2 36 3B F7 97 01 FF 06 D9 02 56 94 
BF C6 CA 01 00 C6 C2 23 82 70 C3 70 C2 C6 DA 44 
78 1F 44 13 45 
It looks like the protocol upgrade got truncated somehow, or you copied it before entering the PID and fixed data on the setup sheet.
ripple
Posts: 11
Joined: Fri Feb 20, 2004 12:31 am

Post by ripple »

gfb107 wrote:It looks like the protocol upgrade got truncated somehow, or you copied it before entering the PID and fixed data on the setup sheet.
I'll be damned...you're absolutely right! My final protocol code in KM matches what you showed in RM, but not what I put in IR. I pasted the corrected protocol code into IR and it worked the first time. :D How you were able to spot that is truly impressive. I owe you one...

BTW, I also tried the power key twice in a row and that works as well. Not bad...I come with one problem and you give me 2 solutions :)

Thanks,
Kevin
Post Reply