JP1 Remotes

Does anyone know of a resource for advanced Kenwood CD codes? Looking for +10, +100, and a few other original remote functions, or should I just learn them onto my 8810w?

Please read the #1 Code Search FAQ thread.

Yeah, Rob, I know I was being lazy....but learning codes seems so much less attractive now if I can download them instead!

doninwny wrote:learning codes seems so much less attractive now if I can download them instead!

If they're not published anywhere and you already have a working upgrade, learning the missing codes and adding them to the upgrade is relatively quick and easy to do.

In fact, if you had learned them when you posted your original message, you could have had them in the upgrade before Rob's reply!

Well, I'm off work now for two days, the promise of spring (and golf) is being buried here in Buffalo by a freak snowstorm....nothing else to do but this! So let me see if I have this correct....learn the missing features from the original remote to the 8810, download into IR, check out the EFCs for the learned keys, and paste them into my upgrade in the functions tab......right?

Right, although once you've added them to the Functions page, you'll probably also want to assign them to a button on the Buttons page.

You'll also want to double check that the device and sub-device codes are the same for these new buttons as the ones that you have entered into KM/RM.

Hey, I knew that! By George, I just might be getting the hang of this!

And don't forget to delete the learned signals when you upload the upgrade.

very thorough Mark!

I just discovered a possible flaw in the devices4 spreadsheet. When I go to copy the EFC column, I select the whole column by clicking on the F column header, then right click and select copy, go over to KM functions page, right click on column B, select paste special, check values. There is a subheader in devices4 that gets copied into row 1, setting the data one row off, with the "0 button" assigned an EFC value of "EFC". Am I correct here?

I've taken some learned codes and put them into KM, only one of them so far has a subdevice code (+100 key, sub 72). This doesn't match the device2 code in devices4, which, for a Kenwood cd code 0190, uses 182 for both device1 and 2. So which of them goes into the subdevice field? Does the 72 go into the byte2 field on the functions page of KM? And why can't I get this to work on the 8810 after I upload it?

doninwny wrote:There is a subheader in devices4 that gets copied into row 1, setting the data one row off, with the "0 button" assigned an EFC value of "EFC". Am I correct here?

That appears to be the case (I haven't used devices4 in ages so I haven't noticed it). Just copy the EFC values starting in Row 3 and then paste them into the corresponding cell of KM's Functions sheet.

doninwny wrote:I've taken some learned codes and put them into KM, only one of them so far has a subdevice code (+100 key, sub 72).

That's so strange that I was ready to suggest it might be a learning glitch until I found two samples in my library of downloaded CCF files. Both are Kenwood CD's. Each has only one command using subdevice 72.

In one file NEC1:182.72:0 is the "+100" command.
In the other file NEC1:182.72:3 is the "mode" command.

Both are very clean learns. One very small learning glitch would change 182 with no subdevice into 182 with subdevice 72. Such a glitch would easily fool my decoding software, but would leave a very specific distortion in the timing data that I would see in a manual check. Those two samples have no such distortion.

doninwny wrote:This doesn't match the device2 code in devices4, which, for a Kenwood cd code 0190, uses 182 for both device1 and 2.

Are we looking at different versions of Devices4?

Everything (including Device4) that I can find says that CD/0190 has device of 182 and NO subdevice.

In some older remotes, including the 15-1994, "no subdevice" for NEC1 was encoded strangely. I expect Rob built Devices4.xls before he had all those details nailed down, so I'd expect the original Devices4 to get that wrong (and report exactly what you described). But I can't find that. The copy of Devices4 I have gets that right.

doninwny wrote:So which of them goes into the subdevice field? Does the 72 go into the byte2 field on the functions page of KM? And why can't I get this to work on the 8810 after I upload it?

KM's NEC1 protocol (which CD/0190 uses) is a non combo protocol. The byte2 field is disabled.

If you're staying close to CD/0190 you must leave subdevice blank on KM's setup sheet and you can't directly include that signal.

The easiest way to (indirectly) include that signal is to generate another device upgrade with a different setup code and with subdevice 72. Then use that as the basis for an external function definition in KM which will become a KeyMove in IR.

If you are already using some NEC combo protocol instead (which would make the "byte2" etc. parts of your question a little more plausible) then you need to be more specific about what you're trying. A combo protocol is a reasonable alternative to the method of using an extra upgrade, but it isn't an easier alternative and in this case probably isn't a better alternative.

Thanks for the detailed post John. I downloaded the latest version of devices4 (I think, the one posted now at hifi-remote), thinking that might be a problem, I think it's one from 10/04. That file generated a device1 and device2 of 182. What I will do, if I'm following you correctly, is leave subdevice blank in KM, and delete the +100 key for now, putting it in on another device code after and keymoving, as you have suggested. I left the protocol at NEC1, as was generated by the program. Am I understanding this right?