On Sat, May 11, 2013 at 09:19:40AM -0700, Jim Thompson wrote:
> On Fri, 10 May 2013 23:14:42 -0400, Uncle Steve <
stev...@gmail.com>
> wrote:
>
> >On Fri, May 10, 2013 at 07:27:39PM -0700, Jim Thompson wrote:
> >> On Mon, 06 May 2013 12:01:44 -0400, Uncle Steve <
stev...@gmail.com>
> >> wrote:
> >>
> >> >Back again for some more abuse.
> >> >
> >> >I'm building a 12V battery charger that will be controlled by a small
> >> >low-power microcontroller. I've not yet hooked up the
> >> >microcontroller, but most of the code is written and I'm trying to
> >> >finalize the charger electronics before I hook it up.
> >> >
> >> [snip]
> >>
> >> Remembered where I had stashed some ancient data...
> >>
> >>
http://www.analog-innovations.com/SED/AlternatorRegulatorTC.pdf
> >
> >What, no NDA? Holy crap!
>
> No NDA? You missed the dates. This was 46+ years ago ;-)
The lawyers have been busy since that time. 46 years ago farmers
could buy dynamite to remove tree stumps on their property. Kids
these days would find "Rocket Ship Galileo" utterly alien. Building
rocket motors? Radar? Preposterous.
We're all so much safer now that all that icky science and engineering
is restricted to licensed and regulated corporate facilities.
> "Jerry" Stenklyft was a nice engineer/friend from Anderson, Indiana,
> who, while visiting Motorola, would come over to my house, help me lay
> floor tile, then have dinner with us ;-)
>
> He died in 2004 at age 70.
Condolences. I suppose he didn't have his head frozen to be stored
and tended to by ultra-reliable robots at some autonomous cryogenic
facility in the far North.
> >I don't want to have to install plumbing to
> >keep the water level above the top of the plates.
>
> That's what following the TC curve does for you... minimizes water
> usage.
>
> BTW, the flattening at low and high temperatures is NOT lead-acid
> physics, it's to keep from burning out head lights when cold, and to
> minimize dimming when hot. A straight curve is quite adequate for
> your purposes.
I should think so. My reading on the matter tells me the key to
battery-longevity are gentle charge/discharge curves, minimizing
temperature excursions, and of course keeping them fully charged.
> (My ignition system designs work down to 3V cranking voltage ;-)
Heh. That's a lot of amps.
> >> These are the TC curves provided to me by GM and Ford back in the day
> >> when I designed alternator regulators.
> >>
> >> Your regulator should approximate such a TC if you want to hold a
> >> reasonable charge on your lead-acid battery.
> >
> >I suspect the thing will charge reasonably quickly with a fixed-
> >voltage set to the float charge level, but I have numbers from 13.1V
> >to 13.5V for the float from different sources. It may depend a little
> >on the battery. For EOC float, it may be easier to specify 50-150mA
> >or so charge current.
>
> You're in for a surprise... holding at 13.2V will give you a weenie
> capability charge.
I haven't decided on a charge voltage yet. Once I sort of have the
electronics where I want them, I'll run a discharge/charge cycle and
watch what actually occurs. If I start with 15V supply and PWM, the
battery voltage can be set to whatever is appropriate given battery
state-of-charge. I'm ready for surprises.
> >> What information do you actually need fed back to your
> >> microcontroller?
> >
> >Supply voltage, battery voltage, sense resistor voltage, battery
> >temperature. It would be nice to have load voltage and load current
> >as well, but I could do without if I had to since my NAS is a static
> >load.
>
> I still don't understand what you are trying accomplish. Charging a
> lead acid battery to a proper level is downright trivial with
> stand-alone simple-minded circuitry. How do you plan to measure
> battery temperature?
I'll tape a thermistor to the case, or maybe I'll use some glue.
This is a good first project with the microcontroller precisely
because it is so trivial. I could go out and buy a small UPS for less
than a hundred bucks but where's the fun in that? I'll probably write
it up afterwards, so you'll be able to see what it looks like then.
> >Serial I/O is one pin since as I'm only doing TX. The ATtiny85 I was
> >trying out has 5 I/O pins if I keep _RESET_, so I'll have to multiplex
> >all those measurements on one A/D channel, which actually simplifies
> >the software a lot. Should be doable, assuming I can make the
> >electronics work properly. I don't know if any extra safety devices
> >or sensors are recommended, but with three select bits available,
> >there are options. Sound reasonable?
>
> I don't speak micros... I hire that out. I have a long-time buddy in
> Columbus, OH, who adds any needed digital and bus needs (SPI, I2C,
> CAN, etc.) to my analog chips and he also does my layouts. He has a
> Master's from Ohio State and is a whiz at Verilog and VHDL. (Let me
> know if you have such needs, and I'll provide contact information.)
I'm just getting started with microcontrollers, but I already know
what I'm doing in so far as programming is concerned. It was
surprisingly easy to do the serial code; the Atmel part is full of
features that make everything super-easy without a lot of external
electronics.