Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Message

Re: [lpc2000] Re: Time between ext interrupt calls

2005-04-29 by Richard Duits

Hello Jase,

I would suggest to use a capture pin on timer 0 or timer 1 to capture 
the falling edge. This is more accurate because it eliminates the 
interrupt lattency.

Richard.


jase_ko wrote:

> --- In lpc2000@yahoogroups.com, Robert Adsett <subscriptions@a...>
> wrote:
> > At 04:36 AM 4/28/05 +0000, jase_ko wrote:
> > >I'm new at this. Can someone tell me the best way to measure the
> time
> > >between external interrupt calls?
> > >just point me in the right direction as to what to use..
> > >thanks!
> >
> > It depends on what you are trying to do, your question is a little
> > general.  Usually I just toggle an external pin and measure the
> result on a
> > 'scope.
> >
> > Robert
> >
> >
> > " 'Freedom' has no meaning of itself.  There are always
> restrictions,   be
> > they legal, genetic, or physical.  If you don't believe me, try to
> chew a
> > radio signal. "  -- Kelvin Throop, III
> > http://www.aeolusdevelopment.com/
>
> well i have calls to an external interrupt method every time a pin
> is grounded.. This happens extremely quickly and i need an accurate
> way of measuring the time between the successive calls of this same
> method. I'm using an LPC2129
>
> Thanks
>
>
>
>
> ------------------------------------------------------------------------
> *Yahoo! Groups Links*
>
>     * To visit your group on the web, go to:
>       http://groups.yahoo.com/group/lpc2000/
>        
>     * To unsubscribe from this group, send an email to:
>       lpc2000-unsubscribe@yahoogroups.com
>       <mailto:lpc2000-unsubscribe@yahoogroups.com?subject=Unsubscribe>
>        
>     * Your use of Yahoo! Groups is subject to the Yahoo! Terms of
>       Service <http://docs.yahoo.com/info/terms/>.
>
>

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.