Re: [tuxdroid-user] Some IR & RF questions...

[David B. <da...@ja...>]

On Tue, 20 Mar 2007 23:26:50 +0100, Philippe Teuwen <ph...@te...>  
wrote:

> Hi,
>
> How a dongle and a tux are paired?

They are not :-)

> Is it a unique code?
> What if many tuxes/dongles are present simultaneously?
> Could one single dongle command several tuxes?

At the moment, when the dongle is plugged, it sends an initialization  
frame. Then when you switch on Tux, it initializes in receiving mode  
looking for that frame. When it get's it, they exchange a code which is  
kept all the time the connection stays stable. When the connection drops  
(tux switched off or oo far), the dongle resets itself in init mode.

So now you have to power your dongl and tux simultaneously and when  
they're connected, you can power another set of tux/dongle, otherwise you  
may mix them.

One dongle won't never be able to control several tux with the current rf  
protocol. Right now, audio frames are taking the complete bandwidth  
continuously. It's a major rewrite of the RF modules to do such a thing  
and you won't be able to use the audio simultaneously on 2 tux anyway. And  
if you have 2 tux, you also have 2 dongles. btw, what's the plural of tux?  
Is it tux, tuxs or tuxes? :D

I personally don't think it's interesting to do that work, but to have a  
daemon that uses 2 dongles correctly would be great. One of my proposals  
were to be able to set a name inside a tux (in eeprom somewhere) from the  
computer interface, then whenever you reconnect the same tux, the daemon  
could get that name whatever dongle it's connected to and you can control  
your tux by it's name.

>
> How to get an IR RC5 code from the API?
> I saw only commands to send RC5 but I'd like to learn the codes from my
> own remote unit.

It's sent in the status. Whenever a code is received, there's a IR status  
sent back that the daemon should capture.
I'm going to rewrite the commands.h documentation, that should be clearer  
afterwards. Yes I'll do it someday ;-)

All the codes are listed in remote.h. Don't forget the toggle bit,  
whenever you push a key, the toggle bit get toggled. So if you push the  
same key, you get A then B then A then B where A is the code + togle low,  
and B is the same code and toggle high

Cheers,
david