Thread: [tuxdroid-user] IR question
Status: Beta
Brought to you by:
ks156
From: Philippe T. <ph...@te...> - 2007-04-09 23:09:01
|
Hi, I try to understand how IR reception works. If I use the kysoh remote control, the tux gets the signals and its eyes blink as confirmation. It looks like, from the fw, any RC5 code would be accepted. But I tried with my tv and tv remote. The tux can control the tv, so sending RC5 commands. But my tv remote seems to not be understood by the tux, no led blinking :-( But in the fw I didn't see any check on the RC5 address before the led blink feedback so what does it means? The tux doesn't see my tv remote at all? Another question: RC5 greeting codes are: addr 0x4 + command random (light level sampling) addr 0x8 + command random (light level sampling) addr 0xC + command random (light level sampling) But couldn't they have bad effects on the devices mapped to those addresses? addr 0x4 is a Laser Vision Player (?) addr 0x8 is Sat1, a settopbox I assume addr 0xC is a CD-Video We could take some reserved addresses instead: 7, B, D, F, 18, 19, 1B-1F And what is the addr code sent by the Kysoh remote? Phil |
From: David B. <da...@ja...> - 2007-04-10 07:18:09
|
On Tue, 10 Apr 2007 01:08:52 +0200, Philippe Teuwen <ph...@te...> wrote: > Hi, > > I try to understand how IR reception works. > If I use the kysoh remote control, the tux gets the signals > and its eyes blink as confirmation. > It looks like, from the fw, any RC5 code would be accepted. > But I tried with my tv and tv remote. > The tux can control the tv, so sending RC5 commands. > But my tv remote seems to not be understood by the tux, > no led blinking :-( > > But in the fw I didn't see any check on the RC5 address before > the led blink feedback so what does it means? > The tux doesn't see my tv remote at all? Indeed I don't check the address, you can use any RC5 code but at the moment only the command is sent back in the status iirc. That should be no problem to send the address too. So if your remote is RC5, it should be seen by tux. I don't know why it doesn't, would need to have your remote to debug that. I have a KISS DVD remote control that mixes RC5 and other protocol keys (weird) but the RC5 keys work just fine. > > Another question: > RC5 greeting codes are: > addr 0x4 + command random (light level sampling) > addr 0x8 + command random (light level sampling) > addr 0xC + command random (light level sampling) > > But couldn't they have bad effects on the devices mapped to those > addresses? > addr 0x4 is a Laser Vision Player (?) > addr 0x8 is Sat1, a settopbox I assume > addr 0xC is a CD-Video > We could take some reserved addresses instead: 7, B, D, F, 18, 19, 1B-1F That code is to be removed or corrected. At a certain point in development, it somehow worked and 2 tuxs could see each other and do some greetings, but that doesn't work well anymore and this functionality should be implemented in another way. That was just a quick draft at that time and I never had the opportunity to rework it. But to answer your questions, I used the address as a command and the random number as a tux identifier. And that indeed could clash with your equipment though the probability is quite low. We can change to reserved adresses anyway. > And what is the addr code sent by the Kysoh remote? It's 0x1D david |
From: Philippe T. <ph...@te...> - 2007-04-10 14:50:14
|
> So if your remote is RC5, it should be seen by tux. I don't know why it > doesn't, would need to have your remote to debug that. I have a KISS DVD > remote control that mixes RC5 and other protocol keys (weird) but the RC5 > keys work just fine. I've a KISS too but I didn't try that remote yet. The one I tried is a Philips, the inventors of RC5, should be compliant with the spec ;-) http://www.vatelectronic.cz/photogallery/Philips/Philips%20RC2030%20RC2031%20RC2032%20RC2033%20RC2044.jpg Probably some timing issues. Maybe someone is not following exactly 36kHz in sending of receiving part. Phil |
From: Philippe T. <ph...@te...> - 2007-04-10 20:38:19
|
Ok I tried the Kiss one and te digits are working. > You're sure it uses RC5? Because Philips also uses other protocols. If > it's not exactly 26kHz, it should not be the problem, the receiver > should get it too. Well actually it came with my television but is kind of universal as it can control TV / Tuner / VCR / CD / DVD / Tape / Sat / CDR devices and TV mode is apparently not RC5 but when on CD mode most of the keys work. And, very funny, when pressing any key on Sat mode (addr 0x8) the Tux replies with its greeting msg :-D Phil |
From: David B. <da...@ja...> - 2007-04-11 06:17:55
|
> And, very funny, when pressing any key on Sat mode (addr 0x8) the Tux > replies with its greeting msg :-D > That's a great feature :-D I'll change that for the next firmware release. |
From: David B. <da...@ja...> - 2007-04-10 18:52:34
|
> I've a KISS too but I didn't try that remote yet. Only the digits are RC5 on mine > The one I tried is a Philips, the inventors of RC5, should be compliant > with the spec ;-) > http://www.vatelectronic.cz/photogallery/Philips/Philips%20RC2030%20RC2031%20RC2032%20RC2033%20RC2044.jpg > > Probably some timing issues. > Maybe someone is not following exactly 36kHz in sending of receiving > part. You're sure it uses RC5? Because Philips also uses other protocols. If it's not exactly 26kHz, it should not be the problem, the receiver should get it too. david |