DLO HomeDock Deluxe

johnsfine · Post by **johnsfine** » Mon Dec 11, 2006 10:17 am

In the other .ir file you posted, you also had EE.87.A.F2 and EE.87.C.F2 so your single digit theory is working based on a hex single digit.

It would be nice to check the remaining commands before creating a new executor that uses that method of deciding the value for the last byte (5E when the OBC is 0x10 to 0xFF and F2 when it is 00 to 0F).

The executor must work with both the OBC and the 5E vs. F2 in an MSB or MSB-comp form, so the operation at the asm code level is a transformed version of what I just described, but it still would be simple.

floyd1977 · Post by **floyd1977** » Mon Dec 11, 2006 10:41 am

Actually, the EE.87.A.F2 and EE.87.C.F2 values were in the IR posted by the person who started this thread. He said he went from left to right, top to bottom on the remote, so that means the remaining three functions are:

Vol+: EE.87.C.F2
Vol-: EE.87.A.F2
Mute: EE.87.4D.5E

I can confirm this when I get home, but the rest of the commands that Mike decoded match up perfectly with the results I got. As you can see, the above 3 commands all use a single hex digit when the check byte is F2.

--Nathan

Post by **The Robman** » Mon Dec 11, 2006 12:24 pm

floyd1977 wrote:Well, when the command byte (that's what I'm calling the next-to-last byte) is a single digit value, the check byte is F2, otherwise it is 5E.

I agree. When the right-nibble of the command byte is zero, the alternate checksum value is used, but we will need to see the remaining buttons to see if that holds true.

I see on the remote that there are REWIND, FFWD, SKIP+ and SKIP- buttons. In your learns, you have F.REW, F.FWD, Prev Playlist and Next Playlist buttons, which original buttons do these tie back to?

Here are my decodes...

Code: Select all

freq: 35242
leadin +9200 -4600 (1/2 subsequent times, NEC1 format)
leadout: +600 -98300 (off as total)
1 = +600 -1800 
0 = +600 -600 

01110111 11100001 00101011 01111010 Mode (bullseye) 
01110111 11100001 01001001 01111010 down 
01110111 11100001 01011000 01111010 left 
01110111 11100001 01100111 01111010 right 
01110111 11100001 10010100 01111010 shuffle 
01110111 11100001 11000001 01111010 info 
01110111 11100001 00111010 01111010 up 
01110111 11100001 00011100 01111010 power 
01110111 11100001 10000101 01111010 next playlist 
01110111 11100001 01110110 01111010 prev playlist 
01110111 11100001 10100011 01111010 repeat 
01110111 11100001 10110010 01111010 mute

01110111 11100001 10100000 01001111 play/pause
01110111 11100001 11000000 01001111 select 
01110111 11100001 10010000 01001111 rewind / skip-
01110111 11100001 01100000 01001111 ffwd / skip+
01110111 11100001 10100000 01001111 backlight
01110111 11100001 00110000 01001111 vol+
01110111 11100001 01010000 01001111 vol-

floyd1977 · Post by **floyd1977** » Mon Dec 11, 2006 12:52 pm

The Robman wrote:
floyd1977 wrote:Well, when the command byte (that's what I'm calling the next-to-last byte) is a single digit value, the check byte is F2, otherwise it is 5E.
I agree. When the right-nibble of the command byte is zero, the alternate checksum value is used, but we will need to see the remaining buttons to see if that holds true.

I see on the remote that there are REWIND, FFWD, SKIP+ and SKIP- buttons. In your learns, you have F.REW, F.FWD, Prev Playlist and Next Playlist buttons, which original buttons do these tie back to?

Rob,

If you are referring to the picture of the actual DLO remote, the buttons that look like standard REWIND/FFWD buttons are actually "next playlist" "prev playlist" buttons which I mapped to CH+ and CH- respectively in my last uploaded IR file.

I mapped the Skip+/Skip- buttons (which act as next/prev track buttons when pushed quickly and REW/FFWD when held down) to F.FWD and F.REW.

By the way, the button that looks like a bullseye at the upper left corner of the remote I have mapped to TV/VID. This button switches between "iPod mode" and "on screen display mode".

SWAP = Shuffle
Prev = Repeat
Info = Backlight

I think the other functions are self-explanatory.

--Nathan

floyd1977 · Post by **floyd1977** » Mon Dec 11, 2006 2:13 pm

For completeness, Mike's original IR file has all the functions, including volume controls, and the mappings are as follows:

http://www.hifi-remote.com/forums/dload ... le_id=3656

TV: 1 Mode (bullseye)
TV: 2 Up
TV: 3 Power
TV: 4 Left
TV: 5 Enter
TV: 6 Right
TV: 7 Down
TV: 8 Vol +
TV: 9 Vol -
TV: 0 |<<
CD: 1 Play/Pause
CD: 2 >>|
CD: 3 << (previous playlist)
CD: 4 >> (next playlist)
CD: 5 Shuffle
CD: 6 Repeat
CD: 7 Mute
CD: 8 Backlight

Post by **The Robman** » Mon Dec 11, 2006 2:38 pm

Thanks, I didn't look at Mike's file originally because he said the learned signals didn't work, so there wouldn't be any point in replicating them, however there is enough info in them for me to get what I need regarding the volume buttons. The good news is that they do follow the rules established earlier regarding when to use which value for the checksum byte. I have updated the list in my previous post accordingly.

When I get a chance, I will put together an executor for this.

johnsfine · Post by **johnsfine** » Mon Dec 11, 2006 2:53 pm

Now that we've seen working signals, it's even less understandable that those were reported as non working. I expect some other error or misuse and not any problem directly related to the learned signals.

But what do you make of the frequency difference?
The first file is all 38.4Khz. The second is mainly 35.4Khz (range 33.9 to 36.5).

I assume the 38.4 is correct (even though that's the one reported not to work). If I understand correctly, the second was learned indirectly, which could cause the error in frequency. I expect the device doesn't care about the error in frequency.

floyd1977 · Post by **floyd1977** » Mon Dec 11, 2006 5:42 pm

Final version of IR file with learned commands:

http://www.hifi-remote.com/forums/dload ... le_id=3934

This includes Vol +/- and Mute, and I have labelled each function. I have verified that all commands work. For some reason, holding down F.FWD does not fast forward, although holding down F.RWD rewinds.

Thanks Rob and johnsfine for helping out with this.

--Nathan

Post by **The Robman** » Mon Dec 11, 2006 6:15 pm

I had assumed that the difference in frequency was the reason why one set of learns worked and the other didn't, but if that's not the case, we should find out.

Nathan,
I have just cut & pasted the learns from Mike's URC-8811 file over to your URC-8910 file. They show up on the TV and DVD modes now. Could you test these and see if they work for you.

http://www.hifi-remote.com/forums/dload ... le_id=3935

If they do, that would leave us baffled as to why they didn't work for Mike, but it would tell us that the frequency isn't that important, but if they don't work it tells us that the freq needs to be closer to 35 khz than 38 khz.

Apparently UEI has a code for this also, but predictably they made it a 2-byte code. If they send me their executor before I attempt to write one myself, I'll just hack their one to make it use 1 variable byte.

floyd1977 · Post by **floyd1977** » Mon Dec 11, 2006 6:47 pm

The Robman wrote:I had assumed that the difference in frequency was the reason why one set of learns worked and the other didn't, but if that's not the case, we should find out.

Nathan,
I have just cut & pasted the learns from Mike's URC-8811 file over to your URC-8910 file. They show up on the TV and DVD modes now. Could you test these and see if they work for you.

http://www.hifi-remote.com/forums/dload ... le_id=3935

Rob,

None of those commands worked for me.

Thanks.
--Nathan

floyd1977 · Post by **floyd1977** » Mon Dec 11, 2006 6:52 pm

By the way, would you guys care to tell me where you're seeing the frequency information, etc.? I don't see it in IR under Learned Signals. Is it encoded somehow in the Raw Data?

Just curious...

Post by **The Robman** » Mon Dec 11, 2006 9:44 pm

Go to the Advanced menu in IR, then select "Force Learned Timings". This will let you see the raw timing data for the learned signals.

John, would you agree that Nathan's test results confirm that 38 kHz is the wrong freq and 35 kHz is the correct one?

Post by **The Robman** » Mon Dec 11, 2006 11:10 pm

Here's an upgrade for you to try...
http://www.hifi-remote.com/forums/dload ... le_id=3936

johnsfine · Post by **johnsfine** » Tue Dec 12, 2006 6:34 am

The Robman wrote:John, would you agree that Nathan's test results confirm that 38 kHz is the wrong freq and 35 kHz is the correct one?

It's not easy for me to believe that the consistent learns of the common frequency are wrong and inconsistent learns of an uncommon frequency are right.

Obviously the reported test results imply 38 khz is wrong. But my guess is still user error or other unknown factor.

Also I've read the spec's on a lot of modulated IR detectors, similar to the ones I'm sure are used in most of the devices we are controlling. The ones that are pickiest about frequency document that a 10% error in frequency creates the same reduction in effectiveness as doubling the distance. I doubt that the testing was done from more than half the maximum distance (most rooms aren't that big) so whichever frequency is right I think both those frequencies would work until you test from considerably further away.

floyd1977 · Post by **floyd1977** » Tue Dec 12, 2006 6:51 am

The Robman wrote:Here's an upgrade for you to try...
http://www.hifi-remote.com/forums/dload ... le_id=3936

Rob,
This upgrade doesn't seem to work.

--Nathan