Rockbox.org home
Downloads
release
dev builds
extras
themes
Documentation
manual
wiki
device status
Support
forums
mailing lists
IRC
Development
bugs
patches
dev guide
Search



Donate

Rockbox mail archive

Subject: Re: PIC12C508A-based remote
From: Steve Russell (raichea_at_yahoo.com)
Date: 2002-12-18

Rob,

While this could be done with a home-grown remote and cooperation from
Rockbox, the standard remote would not benefit. That said, it might be worth
doing anyway....

Steve.

"Rob Ward" <wards_at_paradise.net.nz> wrote in message
news:3E002011.70402_at_paradise.net.nz...
> There is an easy way to tell if the keys are held down. The NEC protocol
> used in your TV remote control for example does the following...
>
> 1. If a button is pressed, it sends a device byte and it's complement,
> then a function byte and it's complement.
> 2. If the key is held, it sends the first packet as above, the changes
> to a simple "repeat key" packet.
>
> Rob
>
> Leif Sawyer wrote:
>
> >Linus writes in response to
> >
> >
> >>Steve Russell who wrote back:
> >>
> >>
> >>>Thanks Frank - I'd hoped the Archos unit would FF/REW, but
> >>>it seems not. There's no reason, of course, that rockbox
> >>>couldn't implement that.
> >>>
> >>>
> >>Yes there is. There is no way of telling that the repeated
> >>events sent from the remote are because the key is held
> >>down or repeatedly pressed.
> >>
> >>
> >
> >
> >So we don't have a method of determining how quickly the
> >key-presses come in? The keys are already 'de-bounced' when
> >we get the notification, right? So a timer would let us know
> >if the keypresses were faster than some threshold.. (100 ms?)
> >Anything under that threshold would be counted as 'continuous'
> >and anything over that would be individual keys..
> >
> >Could actually get tricky though, but I would think it's doable.
> >Whether the payoff is actually worth it, is another question.
> >
> >
> >
> >
>
>

Page was last modified "Jan 10 2012" The Rockbox Crew
aaa