Page 2 of 2
Posted: Mon Jan 31, 2005 9:27 am
by JustinG
Thanks Mark. It works just fine.
One weird thing however. The aspect button from the original remote does not work if I put the codes in manual and set it to a button on the remote. But if I learn the button, I can see the codes it learns and they are the same as I plugged into KM. Any ideas as to why it would work on a learn button but not one assigned in KM with the same exact codes?
Posted: Mon Jan 31, 2005 5:01 pm
by Mark Pierson
JustinG wrote:But if I learn the button, I can see the codes it learns and they are the same as I plugged into KM. Any ideas as to why it would work on a learn button but not one assigned in KM with the same exact codes?
Are you sure everything matches? The particular Panasonic protocol you're using can have several device/sub-device code combinations. The upgrade I created only uses Device=128. Double-check the learned signal decode in IR to see if there's a sub-device code being used.
Posted: Tue Feb 01, 2005 8:58 am
by JustinG
yeah there it is. Sub-Device 4. The other learned signals are on Subdevice 0.
So in KM, can I input subdevice 4 in the device section?
In which section do I put 4?
Device1: 128
Dev2 / Sub 2:
Dev3 / Sub 3:
Dev4 / Sub 4:
Dev5 / Sub 5:
Sub-Dev 6:
and for reference, the info from the learned signal is
Device 128
Sub-Dev 4
OBC 222
Hex Cmd 84
EFC 238
thanks
Posted: Tue Feb 01, 2005 9:11 am
by johnsfine
The Panasonic Mix protocol is rather confusing in KM (at least to me). It's a lot more combination power than you really need for this situation.
What model JP1 remote do you have (in case you want to pick a Panasonic combo protocol that is built-in)?
The Panasonic Combo or Panasonic Combo2 protocol may be much simpler to use, since you need just the device on the setup sheet (the subdevice there is just a default) and specify the subdevice and OBC for each function on the functions sheet.
If you insist on using the Panasonic Mix protocol, read the Protocol Help. According to that, you would need the three numbers 128, 0 and 4 in the fields 1 through 6, in any arrangement that has the 128 before the 0 or the 4.
Say you used the first three field for 128, 0 and 4 in that order.
In the byte2 column you put 1 2 for any commands that decode as device 128, subdevice 0 and 1 3 for any commands that decode as device 128, subdevice 4.
Posted: Tue Feb 01, 2005 10:52 am
by JustinG
Im using the 8910 with the KM upgrade file that Mark made from the OFA factory code of 650 I got from them over the phone.
Posted: Tue Feb 01, 2005 11:41 am
by johnsfine
I'm not sure why that upgrade is missing the subdevice numbers. I think TV/0650 is supposed to include subdevice numbers 0, 1 and 4.
Since the Sub2 field was left blank, it defaults to 0, which is what it should be and that covers all the subdevice 0 commands.
I think sub3 should be 1 and sub4 should be 4.
Then in the byte2 column in the functions sheet you would put 1 4 for any commands using subdevice 4.
Posted: Tue Feb 01, 2005 1:28 pm
by Mark Pierson
johnsfine wrote:I'm not sure why that upgrade is missing the subdevice numbers.
It's missing them because I recreated the KM file based on an official upgrade Justin got from UEI. All the commands were using no sub-dev, so I opted to not include any in the KM file.
I don't have the details here at work, but I think you may be right about the sub2=blank, sub3=1, and sub4=4 in the factory upgrade... I'll check when I get home.
Posted: Tue Feb 01, 2005 3:54 pm
by Mark Pierson
JustinG wrote:Device 128
Sub-Dev 4
OBC 222
Hex Cmd 84
EFC 238
Open the upgrade file and enter these values on the Setup sheet to match the original upgrade from UEI:
Device1 = 128
Dev2 / Sub 2 = 0
Dev3 / Sub 3 = 1
Dev4 / Sub 4 = 4
Dev5 / Sub 5 = 0
Sub-Dev 6 = 255
Then on the Functions sheet, enter the function name ("aspect"), the EFC of "238", and as John said, a "1 4" in the byte2 column. Assign the function on the Buttons sheet, copy the upgrade code into IR, upload it to the remote, and test it out. Be sure to delete the learned signal so it doesn't override the upgrade.
Posted: Tue Feb 01, 2005 4:38 pm
by JustinG
cool. Thanks mark. I had already added the aspect to the functions and did the button assign. But as you and john say, I think the 1 4 missing kept it from working. Will try tonight.
Posted: Tue Feb 01, 2005 11:22 pm
by JustinG
yay! some success. I put the 1 4 in the byte code column and it did fix the problem with the aspect key. The PIP functions don't work at all however. Even with the factory code the didn't work. So, I'll have to learn all the keys and then see what codes I get out of it. thanks again.