From: Andrew Jamieson <ajamiesn_at_optusnet.com.au>
Date: Thu, 10 Oct 2002 07:11:39 +1000

> This makes sense to me, but sounds quite complicated, especially if we
want
> to keep it compatible to old remotes. For my purposes, I wouldn't need any
> battery saving features, so I'd rather like to keep it as simple at
> possible.

I tend to agree with you, and this would require different remote handling
code for the LCD version and non-LCD version, with some branching routine to
decide between the two. I'd really hoped to avoid this. I guess it all
depends on the current consumption of the LCD we find (even 500uA will drain
a 200mAh CF2032 in 400 hours, which is 50 days of 8 hours per day). It may
be worth the complexity for the extended battery life.

The absolute limit to this is the maximum supply current of the SH1, per
pin. This is listed on the datasheet as 2mA, which should be just enough
for our purposes.

While on the note of pushing things to thier limits; all the HDD used in the
Archos require 5V +- 5% supplies (ie 4.75V - 5.25 V), whilst the supply
given to the HDD is direct from the batteries, which scales between ~5.5V
and 5.8V whilst charging in my player (these values are about right for
NiMh's). So, the HDD in the Archos is overdriven at the moment, to the tune
of about 0.5V, which is probably just below the threshold of doing rather
nasty things :)
Received on 2002-10-09