From: George Styles <george_at_ripnet.co.uk>
Date: Thu, 3 Oct 2002 15:04:36 +0100

The problem with that is that it would require the remote to 'poll' the
Archos for screen updates, even when there are none. This would drain the
battary in the remote.

g

----- Original Message -----
From: "Andreas Stemmer" <Andreas.Stemmer_at_web.de>
To: <rockbox_at_cool.haxx.se>
Sent: Thursday, October 03, 2002 1:21 PM
Subject: RE: Remote control with display


> Great idea to use this pin in both ways. I'd love such a solution, but
> as many others I don't want to open my jukebox and solder it, at least
> until warranty runs out. But I don't have any problems to build my own
> remote with a µ-controller. There would be many great applications, a
> interface to a car stereo for example that displays song name etc. in
> the display...
> My suggestion for the communication is the following: leave the
> remote-pin of the archos as an input all the time, except the remote
> sends a special "give-me-data"-command. Only then the archos should
> change the port to output, send the requested data and change to input
> again. This way, you can use the standard remote as well and there won't
> be any situations where both units try to send data, which wouldn't be
> very nice (imagine one device trying to pull the line to "1", the other
> one trying to pull it to "0" at the same time!). The negative side is,
> that all data has to be polled frequently, but I think it is not too
> much work for the archos, handling this every 500ms or something like
> this...
> What do you think?
>
> Andreas Stemmer
>
>
Received on 2002-10-03