ellen wrote:Would it be beneficial to the group to create a devices6011.xls, devices810.xls, etc?
If I interpret, what you asked, correctly – by all means, please, build/update any crossrefs you can. Perhaps all in one spreadsheet. In Devices4, for example, the history stopped at 3 universal remotes. And, likely, not all codes are in. I would think, unless you have every remote and equipment in the world, this should be a group effort with many people updating. People like me will be grateful and it might save some experts’ time looking up codes for us.
robman wrote:That's what "experts" are for!.
Trying to avoid just that, if the info just might be in front of my face someplace. But the ideas in this whole thread just make me ask more questions …
robman wrote:You can get some of this info yourself from the devices.xls and devices4.xls spreadsheets.
I saw somewhere that Devices.xls is obsolete and/or not to use. So it sits in my collection, unused.
That is a useful file! The data is there – filter for 160 reveals 4 or so device protocol rows. (List possibly missed 20. I use it for the receiver with Panasonic Combo2).
Devices4 likely has the info but you have to know first, what Mark found, that CD/0303 uses 160 (no data in Devices4 that’s useful, but advanced code list has it). Codes sheet is padlocked. I don’t do password breaking unless value added is going to be enormous.
I’m still puzzled about how to know what’s built into
Panasonic Combo2 (my original question, which by now, of course we know should have asked about 160 not 128). How can I, by looking at that protocol, know which device protocols were included? How come actual subdevice numbers (not index) are used in coding?
I’m making a mental parallel (perhaps erroneously) with a file
Panasonic Combo PV-D4732 which uses device combiner from KM. It clearly shows what’s been scrambled into it: there’s a list in a lower-left corner and fixed bytes are shown in the Protocol section for each part of the combination. On the Functions sheet just zero based index is used and that’s that.
Panasonic MIX seems to have mixed some/all of above, and subdevices 0,1,5 are clearly shown, and on the Functions sheet, subdevice is always 1 (plus delay byte). So how come I don’t see such a clear connection to protocols in Combo2 or PanasonicMIX as I see in the combiner and how can that be unscrambled? Would actually making an experimental combiner show me the light if I could just watch its footprints?
I imagine a situation of some unknown equipment from which you learn that it uses protocol(s) list and subdevice(s) list – how would I go about knowing which of the combo protocols might include what’s needed? Trial and error only?
. With the Panasonic Combo2 protocol, it needs byte 2 to be zero, not 4. It works great in the power on/off macros in spite of all our complaints in several threads here. Consequently, I updated Rob’s CompositeSpreadsheet. At the tail end, I fell out of yahoo, so I can’t tell whether file really got through. I’ll check later.
, and I don’t know yet how to rebalance other than by extender]
(unlike their TV remote). Then, I followed 8910 instructions to setup this receiver, and most keys didn't even work. And that's how I found myself in this amazing JP1 land 
The only way that we know that CD/0303 uses 160.10 is because somewhere along the line, someone learned the signals from a remote using CD/0303 and made a note of it. Most experts have files compiled from such findings which we use to look up info like the stuff that mark posted.