From: George Styles <george_at_ripnet.co.uk>
Date: Thu, 3 Oct 2002 12:43:11 +0100

Maybe we should start off by connecting the IO pin on the headphone socket
to a PC's parallel port, and try 2 way exchange of data - that way we can
check if its possible to have reliable 2 way communication, without having
to build any hardware...

I assume that that would be OK with no voltage conversion etc. needed.

Once thats working, its on to the PIC programmers and PCB designers to make
a superior RemoClone :)
Perhaps if the remote contained a PIC it could be made to not send commands
which the LCD update signal was being sent out. This could be done by having
a BEGIN TRANSMITION and AND TRANSMISION signal surrounding the data burst.

The other idea I had earlier was to power the remote from the headphone
socket - basically putting a 1 on the output sets it to 5v, so we could
connect to a capacitor, which would 'store' enough charge to power the
remove, so each time the output because 1, it would re-charge the capacitor,
which would happen 'naturally' if we were constantly updating the LCD

It would be neat if the new remote could not need a battary like the Archos
one.

As a side note, if people do succeed in making a LCD remote for the Archos
then we will have overcome the only possible advantage of the rival Creative
jukebox, which is the possibility of a LCD in the future....

i hope this works

g

----- Original Message -----
From: "George Styles" <george_at_ripnet.co.uk>
To: <rockbox_at_cool.haxx.se>
Sent: Thursday, October 03, 2002 11:52 AM
Subject: Re: Remote control with display


> I am VERY interested in this... it sounds like a really cool idea.
>
> The only thing that was putting me off was the fact that I dont know much
> about PICs and LCDs...
>
> g
>
> ----- Original Message -----
> From: "ActiveSystems" <activesystems_at_caverock.net.nz>
> To: <rockbox_at_cool.haxx.se>
> Sent: Thursday, October 03, 2002 10:44 AM
> Subject: Re: Remote control with display
>
>
> > I haven't tried it in practice but I would think that you can connect an
> > output pin and the UART Rx pin together (with a current limiting
resistor
> on
> > the output pin).
> >
> > Bit-bash outgoing control signals from the remote - clear/ignore any
> > received data in the Rx buffer after sending something. Then just
monitor
> > the Rx via interrupt to receive data sent to the display. Make the
output
> > high impedance when it's not being used.
> >
> > hamish
> >
> >
> > ----- Original Message -----
> > From: "Stuart Tedford" <stuart.tedford_at_piresearch.co.uk>
> > To: <rockbox_at_cool.haxx.se>
> > Sent: Thursday, October 03, 2002 7:58 PM
> > Subject: RE: Remote control with display
> >
> >
> > > Hmmm, on the remote side, how do you both tx and rx data on the same
> piece
> > > of wire without upsetting the UART?
> > >
> > > Stu.
> > >
> > > > -----Original Message-----
> > > > From: ActiveSystems [mailto:activesystems_at_caverock.net.nz]
> > > > Sent: 03 October 2002 08:36
> > > > To: rockbox_at_cool.haxx.se
> > > > Subject: Remote control with display
> > > >
> > > >
> > > > Hi
> > > >
> > > > I was checking out the hw spec for the controller in the Jukebox
(and
> > > > reading some of the old postings to this group).
> > > >
> > > > Pin PB10 which the remote is connected to is usually
> > > > configured as serial
> > > > comms port so it can receive async data from the remote.
> > > >
> > > > The pins on port B can also be configured as a general I/O so
> > > > it could quite
> > > > easily output data to the remote as well. Good thing about
> > > > this is that we
> > > > could use this outgoing data to run an external display.
> > > >
> > > > It should be relatively easy to intermittently reconfigure
> > > > PB10 as an output
> > > > pin and throw out some data to the remote, then pop it back
> > > > in receive mode
> > > > to watch for commands from the remote. If the outgoing data
> > > > was at 100kbps
> > > > or so then it would be unlikely that the player will miss any remote
> > > > commands. - 50 bytes of data will only take 5ms. Each line
> > > > of text to be
> > > > displayed on the remote can have a byte or so of control data
> > > > saying if it's
> > > > to be scrolled, scrolling speed etc.
> > > >
> > > > I'd be quite happy to do the remote end of things - sw + pcb
> > > > etc for people
> > > > wanting to build their own.
> > > >
> > > > My question is how hard would this be to implement on the
> > > > Jukebox? If there
> > > > are any existing tasks that are executed at 100kHz or so then
> > > > I would think
> > > > that you could use that proc to bit-bang any waiting data out
> > > > PB10. Can
> > > > connect to a UART on the remote micro to receive the data.
> > > > Would just have
> > > > to check that the o/p on the Archos remote is buffered then
> > > > it should still
> > > > work.
> > > >
> > > > thoughts?
> > > >
> > > > Hamish
> > > >
> > > >
> > > >
> >
> >
>
>
Received on 2002-10-03