From: "Bob Ammerman"


> What current does your multimeter read if placed in series with your
power
> supply and a 1M resistor, how about a 5M or so?

With a 1M, I get 5uA  With a 5M the reading starts to get a bit "jumpy"
but still gets the point across.  10M is hopeless though.

> when all else fails: check your tools

Thanks for the advice.  I guess I can admit that my meter is from radio
shack (looks just like a Fluke, just the wrong color).  It's a Micronta
22-167 circa 1992ish.  I don't know whose design/build it is, but it has
been a decent meter.  Any recommendations for something in the $100-$200
range from Fluke?  Maybe a Fluke 179?  ;-)

> Bob Ammerman
> RAm Systems
>
> ----- Original Message ----- 
> From: "michael brown" <spam-me@houston.rr.com>
> To: "Microcontroller discussion list - Public." <piclist@mit.edu>
> Sent: Sunday, March 27, 2005 11:19 AM
> Subject: Re: [PIC:] High sleep current on 16F88
>
>
> >
> > ----- Original Message ----- 
> > From: "Bob Axtell" <engineer@cotse.net>
> > To: "Microcontroller discussion list - Public." <piclist@mit.edu>
> > Sent: Saturday, March 26, 2005 9:40 PM
> > Subject: Re: [PIC:] High sleep current on 16F88
> >
> >
> >> Jinx wrote:
> >>
> >> >>RB0 is driven by the square wave output of a Dallas 1307 RTC
> >> >>
> >> >>
> >> >
> >> >That's the only i/p ?
> >> >
> >> >Have you tried starting with a totally disconnected F88 and adding
> >> >connections, measuring as you go ?
> >> >
> >> >
> >> >
> >> Yes, how about just raising the VDD pin, see if its REALLY caused
by
> > the
> >> F88.
> >
> > I put the same PIC on another breadboard and got exactly the same
> > results.  Sleep current is right at 119uA-120uA.  I'm going to try
> > another PIC right now......well I'm back and a different chip does
> > exactly the same thing (well it's 118uA-119uA).  Now, I'm sure that
it's
> > something I've missed, does anyone have any ideas?
> >
> > There must be something turned on (at reset) that I don't know
about.
> > Could it be the internal oscillator block?  The datasheet doesn't
show a
> > SLEEP "input" to it like the xtal oscillators have.  Is it possible
that
> > the internal oscillator block is really running all the time, even
> > during sleep?
> >
> > Perhaps I don't understand the oscillator block fully and I am
subject
> > to the errata after all.  I will try setting the clock back to 31.25
(by
> > clearing OSCCON) before I sleep and see if that makes any
difference.
> >
> > Here is my CONFIG word stuff:
> >
> >  __CONFIG    _CONFIG1, _CP_OFF & _CCP1_RB3 & _DEBUG_OFF &
> > _WRT_PROTECT_OFF & _CPD_OFF & _LVP_OFF & _BODEN_OFF & _MCLR_OFF &
> > _PWRTE_ON & _WDT_OFF & _INTRC_IO
> >
> > Ends up a 0x2F10 for __CONFIG1
> >
> >  __CONFIG    _CONFIG2, _IESO_OFF & _FCMEN_OFF
> >
> > Results in 0x3FFC for __CONFIG2
> >
> > -- 
> > http://www.piclist.com PIC/SX FAQ & list archive
> > View/change your membership options at
> > http://mailman.mit.edu/mailman/listinfo/piclist
> >
>
>
> -- 
> http://www.piclist.com PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist