Denon Combo Protocol 0047 not Compatible with 8820

garypen · Post by **garypen** » Sun Oct 28, 2007 10:40 am

I was going to program my 8820 for my new Denon 3808 using my old Denon 2805 RM file. But, it says that 0047 is not compatible with the 8820, and I can't seem to get the file to work with the device using the "official" Denon Combo protocol.

Is there a way to make 0047 work with the 8820. Or, is there a protocol that works just like it that is compatible?

binky123 · Post by **binky123** » Mon Oct 29, 2007 8:52 am

Do you have a pointer to the files you are using? It's most likely that your protocol upgrade is for the S3C80 and the 8820 uses the HCS08 chip.

garypen · Post by **garypen** » Mon Oct 29, 2007 10:10 am

Is there a way to convert the 0047 protocol to the HCS08 chip? Or, to convert the commands from that file that currently use the 0047 protocol to ones that use the Denon Combo (official) protocol?

The file that I was working from is located at:
https://www.hifi-remote.com/forums/dload ... ile_id=405

To further complicate matters, the new Denon line has a few remote functions that are new, and when I learn them and download to IR, I see that they are Denon-K protocol!

Is there a way to have one protocol that combines Denon commands with different device number, like the Denon Combo protocol, PLUS commands that use the Denon-K protocol?

binky123 · Post by **binky123** » Mon Oct 29, 2007 12:01 pm

You should be able to use protocol 009C in your device upgrades on the 8820 as it looks to be the same as the 0047 Denon Combo Hacked.

The Denon-K protocol(00CD:2) is a different protocol so you probably want to keep these separate.

garypen · Post by **garypen** » Mon Oct 29, 2007 12:05 pm

Thanks. Where would I find 009C? Is that the Denon Combo (official)? If so, it doesn't work when I take the above file, and change the protocol to Denon Combo (official).

Also, keeping those functions that use Denon-K separate isn't practical as they would need to be used with the same device.

binky123 · Post by **binky123** » Mon Oct 29, 2007 12:57 pm

I think I see the issue. Open up RemoteMaster's protocol.ini and goto the Denon Combo (Official) PID=00 9C section. Copy the line beginning with Code.HCS08= and paste that at the end of the Denon Combo (Hacked version) right after Code.740.

You should then be able to use the above KM file and RM shouldn't give you the not compatible error anymore. However, RM will note that you need to also copy over the 0047 protocol upgrade. This protocol isn't needed though as the built-in 009C is equivalent. If you choose not to copy the protocol upgrade into IR, go into the device upgrade tab in IR and change the protocol id from 47 to 9C for your device upgrade.

garypen · Post by **garypen** » Mon Oct 29, 2007 2:13 pm

I've already tried changing the protocol ID in RM, as I mentioned in one of the posts above. Changing protocols changes the EFC and HEX values, and the remote doesn't work with the device.

But, I will try the modification to the hacked protocol, that you recommend. I will let you know.

garypen · Post by **garypen** » Mon Oct 29, 2007 2:26 pm

OK. Modifying the protocols.ini file allows me to choose the 0047 protocol with the 8820 remote in RM. Now, it remains to be seen whether the commands will work or not. I will know tonight, when I try it at home.

The one thing I still find puzzling is why the 009C Denon Combo (official) protocol changes the EFC and Hex values, rendering the upgrade file unusable.

I think there may be something wrong with the 009C protocol in general. When I learn functions, take the results from IR, and enter them into RM using the 009C protocol, the OBC and Hex codes are wrong there as well. 0047 works OK, though

FYI - IR says the protocol is Denon. But, the Denon protocol doesn't have a "device" parameter, which is required. So, a "combo" protocol is required. I would prefer to us the "official" protocol if possible. Is it possible that there is an error in the Denon Combo (official) 009C protocol in the protocols.ini file?

Below are the protocols.ini entries for both, before adding the HCS08 section to 0047.

[Denon Combo (Official)]
PID=00 9C
CmdParms=Device:5=0,Protocol:Sharp|Denon=1,OBC=0
CmdTranslator=Translator(lsb,comp,0,5,0) Translator(lsb,comp,2,8,8) Translator(lsb,comp,1,1,5)
Notes=Official version
DefaultCmd=F8 00
CmdIndex=1
Code.S3C80=3D 92 02 8B 0D 49 05 08 00 84 01 75 00 84 03 87 83 C2 E6 24 03 20 10 0C 05 E4 03 05 60 05 90 05 0A FC B0 C6 A6 0D 02 EB 03 E6 0D 05 F6 01 46 60 04 60 05 F6 01 0A 7B 02 60 C6 F6 01 46 37 61 09 60 04 60 05 F6 01 0A 7B E3 AF
Code.740=0B 1A 02 80 11 E8 80 01 0A 05 08 01 F5 03 53 41 EB 00 2F CF 00 03 44 5E E6 69 3C 02 5C A2 05 17 5D 0F 3C 02 77 A5 74 A6 75 85 71 86 72 A2 03 86 6B A5 5D 0A CA D0 FC 85 5F 3C 00 57 44 5F 44 5E 22 00 44 57 D0 F6 22 06 90 EF 60
Code.6805-RC16/18=0F 26 02 20 12 49 05 08 00 41 C5 01 41 CE 41 EB 00 00 00 00 00 00 03 3C_66 A6 05 BE 5A 58 4A 26 FC 53 BF 5C 3F 54 CD 01 AF 33 5B 33 5C CD 01 89 24 02 33 54 CD 01 AF 00 54 09 33 5B 33 5C CD 01 89 24 E3 81
Code.HCS08=20 12 1F 4B 02 49 05 08 00 81 01 8B 00 81 03 9D 83 D6 5F B4 AE 03 33 61 3C A9 A6 05 01 60 08 BF 6A 55 76 35 74 AE 02 BF 7C BE 60 58 4B FD BF 62 3F 56 33 61 33 62 CD FF 5F 33 56 26 F5 CD FF 92 25 EE 81

[Denon Combo]
PID=00 47
CmdParms=Device:5,OBC=0
CmdTranslator=Translator(lsb,comp,0,5,0) Translator(lsb,1,8,8)
Notes=hacked version
DefaultCmd=F8 00
CmdIndex=1
Code.S3C80=3D 92 02 8B 16 49 05 08 00 84 01 75 00 84 03 87 83 C2 00 00 00 00 00 00 03 5F A0 20 10 0C 05 76 03 01 6B 0D E4 25 1C E4 26 1D 0C 03 09 12 E6 24 02 18 03 90 C1 0A FC 19 05 B0 C6 60 04 60 05 F6 01 46 60 C6 EB F5 F6 01 0A 7B EE AF
Code.740=0B 19 12 80 11 E8 80 01 0A 05 08 01 F5 03 53 41 EB 00 2F CF 00 03 3C 02 5C A2 05 A5 5E 85 5D A5 5F 85 5E A5 5D 0A CA D0 FC 85 5F 3C 00 57 44 5F 44 5E 22 00 44 57 D0 F6 22 06 90 EF 60

binky123 · Post by **binky123** » Mon Oct 29, 2007 2:53 pm

The CmdTranslator lines are different between the two protocols.

garypen · Post by **garypen** » Mon Oct 29, 2007 2:56 pm

I noticed the differences in the first few lines. I have no idea what any of it means. However, there is obviously something wrong with the "official" version as a whole, not just as it relates to HCS08, as it changes OBC and Hex values regardless of chipset.

binky123 · Post by **binky123** » Mon Oct 29, 2007 2:57 pm

Also, you can use keymoves to point to another device upgrade that uses the Denon-K protocol.

garypen · Post by **garypen** » Mon Oct 29, 2007 3:00 pm

Interesting. I can use a hidden device key, I guess. OTOH, if it's just a couple of functions, I may just learn a couple of keys.

Mark Pierson · Post by **Mark Pierson** » Mon Oct 29, 2007 4:33 pm

Try this:

Open the upgrade file, select the 8820 remote, copy the upgrade code (ignoring the protocol error). Paste it into IR but before hitting the OK button, change the first byte from "47" to "9C". This will tell the upgrade to use the "official" protocol (which is built-in) with the "hacked" hex commands. If this works then we know that the "official" protocol entry isn't coded correctly.

garypen · Post by **garypen** » Mon Oct 29, 2007 4:55 pm

OK. Makes sense. I will try that tonight.

binky123 · Post by **binky123** » Mon Oct 29, 2007 6:03 pm

garypen wrote:Interesting. I can use a hidden device key, I guess. OTOH, if it's just a couple of functions, I may just learn a couple of keys.

No need to use a device key. A keymove can reference a device upgrade that is not assigned to a device button key.