Panasonic SA-HE100 and Panasonic Combo2 (with 15-1995)

tbsmith · Post by **tbsmith** » Thu Apr 29, 2004 8:55 am

I am trying to upgrade my remote for a Panasonic SA-HE100. I downloaded the latest version of KM, IR and the RDF. But when I select my remote in KM, there are some messages on the setup screen that I'm not sure how to deal with.

It reads something like "Enter the Main Device Code, Sub Device Code, OEM codes (1 and 2) and set byte2=subdevice on functions". There are some codes just to the right of these boxes, so I entered them into the yellow cell. I think I did that right, but what does "set byte2=subdevice" mean? I tried entering '0' in all the byte2 cells on the functions sheet, since the RDF value for subdevice on the setup screen is 0, but that didn't work. What should I do?

Also, there was a message about deleting 11 button assignments. I did that on the buttons sheet and the message went away after excel recalculated the values. I assuming that isn't the problem then?

I copied the upgrade and protool codes per the instructions. I know my cable is working since I tested some other changes. I searched the archives but only saw that there are some possible flaws in the Panasonic Combo2, however, other people seem to have got it to work.

Thanks for any help. I love this web site!

Tom

gfb107 · Post by **gfb107** » Thu Apr 29, 2004 9:22 am

Have you tried using the Panasonic_SA-HE200.txt. All the work may already be done.

Post by **The Robman** » Thu Apr 29, 2004 9:38 am

What kind of device is an SA-HE100, is it one of those "home theater in a box" type devices? If so, you'll probably be better off creating seperate upgrades for each of the virtual components.

The problem with remotes like the 15-1995 (ie, remotes that use the Mitsubishi 740 processor) is that upgrades are limited to something like 50 bytes or so. This isn't a problem for 1-byte protocols as it would allow you to program around 40 buttons, but for 2-byte protocols (like the Panny Combo2) it limits you to about 20 buttons.

If you still want to use the Combo2 protocol, I assume that all of the buttons you need to program use the same main device code (probably 160) and different sub-device codes. So, you would enter the main device code in the Device Code cell in the setup sheet. You can ignore the sub-device field and the OEM codes.

Then switch to the Functions sheet and enter the function codes (using either OBCs or EFCs, depending on which option you selected in the Setup sheet). In the "byte2" column, enter the sub-device code. For example, if the POWER button uses device code 160, sub-device code 4 and OBC 5 (I'm making these codes up), you would enter 160 in the device code cell (setup sheet), you would then enter "power" as the description (in the Functions sheet), enter 5 as the OBC and enter 4 in byte2 as the sub-device code.

OK, now that I've written all that, I decided to check the file section, and sure enough, there's a file for the SA-HE100 already there, so all of this is moot:
Panasonic-SA-HE100-keymap.txt

Post by **ElizabethD** » Thu Apr 29, 2004 10:50 am

There is also a superb file HE75 posted by user Nikon. I used it for my HE100. It was closest to what I wanted for URC8910 and had good function codes which worked for me better than the HE100 list.
I still have some rough spots to figure out for extras, but it's a joy to use already.

SA-HExx models are not home theater in a box. It's a A/V receiver with zillions of inputs and outputs (never enough, however...)

tbsmith · Post by **tbsmith** » Thu Apr 29, 2004 12:24 pm

Thanks for the suggestions! I will try the SA-HE200 and the HE75 since the file SA-HE100-keymap.txt didn't work at all.

SA-HE100 is just a standard Panasonic Receiver. It was rated as a Best Buy in Consumers Reports which is why I bought it.

If you still want to use the Combo2 protocol, I assume that all of the buttons you need to program use the same main device code (probably 160) and different sub-device codes.

How do I determine if all the buttons use the same main device code and the proper sub-device code?

Then switch to the Functions sheet and enter the function codes (using either OBCs or EFCs, depending on which option you selected in the Setup sheet). In the "byte2" column, enter the sub-device code. For example, if the POWER button uses device code 160, sub-device code 4 and OBC 5 (I'm making these codes up), you would enter 160 in the device code cell (setup sheet), you would then enter "power" as the description (in the Functions sheet), enter 5 as the OBC and enter 4 in byte2 as the sub-device code.

I'll have to look at this tonight and see if it makes sense. I thought I understood this when I read the readme files and JP1 manuals

I know you made the example up, but how would I determine what the sub-device code is to enter for each button?

Sorry for these basic questions, but I've spent many late nights trying different variations with no luck. I just don't know what I'm doing wrong since I get absolutely no response from the remote.

Thanks,
Tom

Post by **ElizabethD** » Thu Apr 29, 2004 1:17 pm

To save you a bit of time, I just posted my work-in-progress file on yahoo. Not sure the link will work but it's in files/device codes/audio section (the HE75 base code was in home theater section):
http://groups.yahoo.com/group/jp1/files ... 0[egd].txt
Try it after changing remote in C2 cell on the Setup sheet. Nikon had few comments there and I added lots and lots so that I know what I'm doing. They might help you a bit.

I too used all the docs provided by the good people here, but things really begin slowly to click when you do it. My method was to use learning of number keys and others in IR and then looking at the Function sheet to confirm. Likewise, IR and KM comparison was great for learning how to do keymove. I too am just starting and the first step is always the big one.
Good luck, enjoy!

tbsmith · Post by **tbsmith** » Thu Apr 29, 2004 1:27 pm

Thanks Elizabeth, the link worked fine. I also appreciate and will use your tips on getting up to speed. I can't imagine trying to do this without all the hard work and tools that everyone before me developed.

Cheers,
Tom

Post by **ElizabethD** » Thu Apr 29, 2004 1:40 pm

If there are limitations to #of buttons and #of devices, as I think Rob is saying, then you will have a problem 'cause there are more devices on the Functions sheet than you can swing a stick at (but it all works great on the 100). I'm still learning and reading Rob's notes here already taught me a bunch of new things. BTW it was Rob's great suggestion to pop all the device selection in 100 onto a macro key which saved a whole mess of buttons!

tbsmith · Post by **tbsmith** » Thu Apr 29, 2004 2:01 pm

Yes, as Rob said, KM gives a warning to delete some buttons to get the memory usage down. I hope I'm doing that right as there are little instructions to go by. Since you have already gone through this, can you tell me what to search for since I didn't see anything when I did my search.

Also, do you know what it means to "set byte2=subdevice"?

BTW it was Rob's great suggestion to pop all the device selection in 100 onto a macro key which saved a whole mess of buttons!

What does this mean? Is it incorporated in your RDF?

Thanks again,
Tom

Mark Pierson · Post by **Mark Pierson** » Thu Apr 29, 2004 3:00 pm

tbsmith wrote:Also, do you know what it means to "set byte2=subdevice"?

In KM, 'byte2' is located on the Functions sheet. Many protocols require additional data besides just an EFC/OBC value in order to contruct the correct hex command. Generally, this is explained on the Protocol Help sheet, or sometime just by the on-screen notes.

In this case, "set byte2=sub-device" means that for all the functions you create, the byte2 column should contain the sub-device value.

tbsmith · Post by **tbsmith** » Thu Apr 29, 2004 3:39 pm

Mark,

Just to confirm then, my sub-device value on the setup sheet is 0, so is that what I enter on the buttons sheet in each byte2 cell?

Tom

Post by **The Robman** » Thu Apr 29, 2004 6:12 pm

Tom,
You're working at a great disadvantage because you don't have a learning JP1 remote at your disposal, which is why you are dependant on the work of others.

If you had a learning remote, you could learn the signals from your Panasonic remote and then you could let IR.exe tell you what device and sub-device codes each button uses.

However, as Elizabet and others have already created KM files that you can use, there's no need to worry about what values go in the byte2 column.

tbsmith · Post by **tbsmith** » Thu Apr 29, 2004 7:42 pm

I tried using Elizabeth's code but no luck. Arrrgghh. I'm thinking it would be worth a few bucks to get a learning remote, but I need the RF capability.

Anyway, a few more questions...

I know this remote has a 50 byte memory limit, but does that include just the Device Upgrade code (currently at 42 bytes), or do I have to add in the Protocol also (currently at 32 bytes)?

Another thing I noticed is that after transferring data to IR, the setup screen never updated itself to show the device code where I would have expected (amp or tuner). I tried entering it manually but that didn't help. Any ideas?

Lastly, why does the message in KM still say to "set byte2=subdevice"? My subdevice is apparantly 0, but if I go to the functions page, there are all different values entered.

thanks!!!
Tom

Post by **The Robman** » Thu Apr 29, 2004 9:10 pm

Where did you get the idea that you need to enter the same sub-device for all the buttons? If that were the case, you wouldn't need the combo protocol, you could use the regular Panasonic protocol.

Btw, there is such a thing as a learning remote with RF, it's the One For All URC-9910, which I have available for $33.

AFAIK, the 50 byte limit does not include the protocol.

mr_d_p_gumby · Post by **mr_d_p_gumby** » Thu Apr 29, 2004 11:45 pm

tbsmith wrote:I tried using Elizabeth's code but no luck.

Well, considering she has the exact same model of Panasonic equipment as you do, and it's working for her, I'd have to conclude that you are doing something wrong.

tbsmith wrote:I know this remote has a 50 byte memory limit, but does that include just the Device Upgrade code (currently at 42 bytes), or do I have to add in the Protocol also (currently at 32 bytes)?

The 50-byte limit applies to the upgrade only.

tbsmith wrote:Another thing I noticed is that after transferring data to IR, the setup screen never updated itself to show the device code where I would have expected (amp or tuner). I tried entering it manually but that didn't help. Any ideas?

Yes. It will never work if you do not assign a device button to the upgrade. IR will not do this automatically, as you discovered. You must assign both the Type and setup Code on IR's General tab.

tbsmith wrote:Lastly, why does the message in KM still say to "set byte2=subdevice"? My subdevice is apparantly 0, but if I go to the functions page, there are all different values entered.

That message is a static general help message that is displayed when you select the Panasonic Combo2 protocol. As Rob said, you have no information on what sub-devices are used by your unit, so what led you to conclude that 0 was correct? Elizabeth (and/or Nikon) has already learned the codes for your HE-100 and decoded them, and entered them into KM. As you can see, several different sub-devices are in fact used.

As to why it's not working for you, about all we can conclude is that you've missed a step somewhere. If you post your saved IR file (with the non-working upgrade installed) in the Yahoo group diagnostic folder, and post a link & a message here to say you've done so, maybe someone could tell what might be wrong. Oh, and before Rob has to scold you, be sure to read the Sticky about posting links to Yahoo.