Apple Mac Mini Remote

Post by **The Robman** » Wed Aug 01, 2007 11:17 am

That's not a good file to work with, try this one instead...
https://www.hifi-remote.com/forums/dload ... ile_id=791

gfb107 · Post by **gfb107** » Wed Aug 01, 2007 11:33 am

The Robman wrote:That's not a good file to work with, try this one instead...
https://www.hifi-remote.com/forums/dload ... ile_id=791

Are you going to delete the "not good" file?

Never mind. I deleted it, as apparently I uploaded it. Must have been part of the mass transfer from yahoo groups.

km · Post by km » Sat Aug 04, 2007 2:30 pm

Well, I got the Tivo and Olevia codes to work. The Apple is tricker. I don't completely understand the relationship between the EFC/OBC/Hex setting with what I see in irrecord/Lirc on Linux.

Here is what my experiment shows

EFC OBC Hex Lirc
=========================

057 09 6f 0x87EE6409
182 06 9f 0x87EE6406
055 10 af 0x87EE640A
052 12 cf 0x87EE640C
184 05 5f 0x87EE6405
187 03 3f 0x87EE6403

116 20 d7 0x87EE6414
120 21 57 0x00000000
118 22 97 0x00000000
122 23 17 0x87EE6417
245 24 e7 0x87EE6418
249 25 67 0x00000000
247 26 a7 0x00000000
251 27 27 0x87EE641B
244 28 c7 0x00000000
248 29 47 0x87EE641D

The first 6 are the one from the Apple TV txt/rdmu. I added the next 10 with consecutive OBC's.

Clearly the OBC maps to the last byte of what Lirc sees. However, only 6 out of 10 of the OBC's are valid. Apparently only 6 OBC's are vallid within a range, but its not clear to me which 6 and what range.

I'm sure I could continue experimenting and find enough valid OBC's to map all my keys, but it would be more satisfying to understand whats going on.

Besides the validity pattern, I also don't see where the 0x87ee64 that Lirc sees is coming from.

johnsfine · Post by **johnsfine** » Sat Aug 04, 2007 4:07 pm

km wrote:Clearly the OBC maps to the last byte of what Lirc sees.

The OBC is decimal. The "last" byte Lirc sees is hex. It is the same number, not just "maps to". (It happens to be the third of the four bytes in the sequence actually transmitted).

km wrote: I'm sure I could continue experimenting and find enough valid OBC's to map all my keys, but it would be more satisfying to understand whats going on.

If you looked ant the numbers in binary, rather than decimal or hex, it would be more obvious. In binary, the values that worked had two or four '1' digits. The values that didn't work had three '1' digits. I expect all values with two or four '1' bits would work, and likely values with six '1' bits. Probably 0 and 255 (with zero and eight '1' bits) would also work.

Numbers with an odd number of '1' bits won't work (though you only tested numbers with three '1' bits).

km wrote:Besides the validity pattern, I also don't see where the 0x87ee64 that Lirc sees is coming from.

The upgrade is sending those. I think this thread already contains good explanation of that. I don't know how to make it clearer.

km · Post by km » Sun Aug 05, 2007 7:57 pm

Thanks for pointing out the parity issue, I should have caught that myself.

Lirc now sees almost all my keys. The exception are rew/play/fwd which lirc doesn't see at all. rec also has a special behavior, lirc sees it once for every two times its pressed.

Is the special behavior on these keys coming from the upgrade, or the 9910 itself? How can I work around it?

johnsfine · Post by **johnsfine** » Mon Aug 06, 2007 5:53 am

I don't know what the problem might be with rew/play/fwd. Maybe I'll know if I see your .ir file.

REC behavior is a "feature" designed into the remote. You need to press it twice. You can use a KeyMove to disable that feature.

km · Post by km » Mon Aug 06, 2007 6:44 am

EDIT: Deleted ir file which should have never been posted.

Post by **The Robman** » Mon Aug 06, 2007 8:12 am

please post the IR file to the Diagnosis Area and then post a LINK to it here, do not include the file contents in your posts.

km · Post by km » Mon Aug 06, 2007 8:34 am

The Robman wrote:please post the IR file to the Diagnosis Area and then post a LINK to it here, do not include the file contents in your posts.

Sorry! It's a little late but I did now upload it as

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

km · Post by km » Mon Aug 06, 2007 9:31 am

OOPS!

This was a stupid mistake on my part. The 3 "bad" keys had been IR learned on a previous use of that device selection, and was overriding the upgrade definitions. I deleted the learned codes and all is well.

Sorry for the noise. I will delete the download file.

johnsfine · Post by **johnsfine** » Mon Aug 06, 2007 9:35 am

When I asked for your .ir file, I forgot you were using .wav files to upgrade and/or I didn't know you were using .wav files with just the upgrades.

Anyway, you can't show us the General, KeyMoves, and Learned sections of what you are testing in your remote because those are only in your remote and not in any files on your PC.

So I don't know any easy way to narrow down what is going wrong with rew, play, and fwd.

In case you have keymoves, macros or learned signals on those keys that you have forgotten about, you ought to go through the process of selectively deleting those and see if it makes a difference.

Edit: I type too slowly. I see you found that yourself while I was typing.