Building Bin File with denon + denon-K protocols

[vickyg2003]

Hey Rob,

I found the Denon,Denon-k combo.

Aud 2857 sends out Denon 2 and Denon k 4.1 signals.

[vickyg2003]

Using the official executor we're going to run into trouble with the size limit.

I've computed the hex by hand, but my hex isn't all that sharp. I have no idea how we can get RM to do the translation of two totally different protocols.

https://www.hifi-remote.com/forums/dload ... le_id=9710

As you can see, the protocol alone is about 176 bytes, and then the 10 bytes of fixed data and then 2 bytes for every function, not to mention the overhead for a setup code, and we're going to hit that 255 byte limit before we have a useable upgrade.

I think we can probably eliminate the mini-combo aspect of the denon-k functions since all the denon-k for this device are using 4.3 That would save us 7 bytes of fixed data and some code in the executor.

Proudx, how many of these functions do you absolutely need to run this equipment?

[Proudx]

the size limit in sling appears to be about 250kb for each bin file to import into sling. I am happy to report that I have reduced unnecessary functions and have gotten the file imported into my slingbox. There is 1 or 2 more functions I would love to add, but can live without.

Any other tips to tweak/reduce the file size so I can fit more functions on the remote?

[vickyg2003]

Any other tips to tweak/reduce the file size so I can fit more functions on the remote?

There is one thing users need to be aware of when trying to keep the size down. If you are going to use the numbers keys, use ALL the numbers keys, otherwise find an alternate placement for the functions. You can see how the upgrade balloons if you use one of the number keys.

the size limit in sling appears to be about 250kb for each bin file to import into sling. I am happy to report that I have reduced unnecessary functions and have gotten the file imported into my slingbox. There is 1 or 2 more functions I would love to add, but can live without.

Yes there are some bells and whistles in the protocol that can be removed, reducing the size enough to add about 4 keys to your upgrade
This involves assembly language programming. If you are going to stick around and monitor this thread we can work on this to accomodate you. The current upgrade allows for multiple device combinations on the denon-k signals. Since you only need one, we can trim the extra 6 bytes of fixed data.

I'm really glad to see that you are sticking with us. I thought you were going to bail.

[Proudx]

Thank you so much for your help. I really do appreciate it. I didn't include every zone2 function but I think with 4 more keys we could have a complete/near complete zone2 remote. I'd be happy to make a seperate one for zone3 and zone4 for the community as well.

I will try and add in the additonal functions to zone2 to complete it out tomorrow.

[The Robman]

Proudx, which Slingbox are you using, PL or RV?

[Proudx]

I have the pl version

[The Robman]

I have trimmed a few bytes out of the protocol so it's now 17 bytes smaller than it was before, which should give you 8 more buttons (assuming it still works).

https://www.hifi-remote.com/forums/dload ... le_id=9717

[Proudx]

How would I add additional functions for the sharp codes? when I use IR tool to generate the device codes from pronto hex, it gives me device, obc and efc values. They do not match to the ones in the file. In the notes field the values device-2, obc-93 do match my irtool results.

Any formula to get the efc/obc/device or hex values?

[vickyg2003]

Because this combines two very different protocols, I'm afraid the tools are not going to work and you'll need to work the hex by hand.
-------------------------------------------------------------------------------------------
For Denon K
take the OBC and convert it to a 12 digit binary number,
make the number LSB (Reverse the digit order)

For the next 3 bits pick a number from the list below, 001 gives you device 4.3

EDIT, I corrected this just so that it reads correctly

000 =0 selects 28 = 4.1
001 = 1 selects 2C = 4.3

End Edit
then convert it to hex
D4 C3 = 110101001100-001-1 = OBC 811, Dev 4.3

------------------------------------------------------------------------------------------
Denon
When sending Denon, the left 5 variable bits are the device code,
the next 8 bits (3 from byte1, 5 from byte 2) are the OBC (in LSB non-comp format)

[The Robman]

011 = 3 selects 2A = 4.5
100 = 4 selects 2E = 4.7

Those two don't exist anymore in my upgrade file because I zeroed them out in order to remove the two assembler statements that zeroed them out.

[vickyg2003]

Thanks Rob, I hadn't looked at how you got the rest of the bytes.

Nice job.

[The Robman]

I haven't tested my upgrade at all, so I don't know if I broke anything in the process. If you have the time, could you test that it still works?

[Proudx]

I worked out the hex from the OBC value, but how do I determine the Byte 2 value?

I'll test out the revised code tonight

[Proudx]

Rob,

I tested the tweaked file and all functions I need work/fit.

I'm still trying to figure out how to calculate byte2. Trying to add more/all functions for the denon remote zone2. Based on instructions above I figured out OBC value converson from OBC, but my byte 2 field is still blank. how do I calculate byte 2?

for example take function OBC 958 (Zone2 USB Direct Play)

reverse lsb is 011111011100001

so how does that work out OBc, byte 2, etc?