Yahoo Groups archive

Lpc2000

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

Thread

AW: [lpc2000] Re: Rise and fall time of capture inputs

AW: [lpc2000] Re: Rise and fall time of capture inputs

2006-02-06 by Huber Martin

________________________________

Von: Karl Olsen [mailto:kro@...] 
Gesendet: Montag, 6. Februar 2006 10:30
An: lpc2000@yahoogroups.com
Betreff: [lpc2000] Re: Rise and fall time of capture inputs

 
I don't think it is possible to miss a capture event because of slow 
rise/fall times.  You get a capture event when the input is e.g. low at 
one pclk edge and high at the next, and this will happen at least once 
no matter how slow the input rises.

[MEH]  This is an interesting fact. Thank you.
 
Another problem might be noise on the input so that you get multiple 
rise and fall events around the switching level.  The datasheets say 
that there is a hysteresis of typically 0.4V on all standard port pins 
and some more on the I2C pins, so this should filter most noise.

[MEH]  That's the reason my signal is so slow. It's filtered with an
EMI-Filter, so no flicker should be on the line.

Karl Olsen







SPONSORED LINKS 
Microcontrollers
<http://groups.yahoo.com/gads?t=ms&k=Microcontrollers&w1=Microcontroller
s&w2=Microprocessor&w3=Intel+microprocessors&w4=Pic+microcontrollers&c=4
&s=95&.sig=mfaAujKZXA2Z_vxre9sGnQ>  	Microprocessor
<http://groups.yahoo.com/gads?t=ms&k=Microprocessor&w1=Microcontrollers&
w2=Microprocessor&w3=Intel+microprocessors&w4=Pic+microcontrollers&c=4&s
=95&.sig=9jjd2D3GOLIESVQssLmLsA>  	Intel microprocessors
<http://groups.yahoo.com/gads?t=ms&k=Intel+microprocessors&w1=Microcontr
ollers&w2=Microprocessor&w3=Intel+microprocessors&w4=Pic+microcontroller
s&c=4&s=95&.sig=OMnZuqMZX95mgutt4B-tDw>  	
Pic microcontrollers
<http://groups.yahoo.com/gads?t=ms&k=Pic+microcontrollers&w1=Microcontro
llers&w2=Microprocessor&w3=Intel+microprocessors&w4=Pic+microcontrollers
&c=4&s=95&.sig=Malspbd0T4Rq3M4Q0nHrfw>  	

________________________________

YAHOO! GROUPS LINKS 


	
*	 Visit your group "lpc2000
<http://groups.yahoo.com/group/lpc2000> " on the web.
	  
*	 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/> . 


________________________________




[Non-text portions of this message have been removed]

Re: AW: [lpc2000] Re: Rise and fall time of capture inputs

2006-02-06 by Tom Walsh

Huber Martin wrote:

> 
>
>________________________________
>
>Von: Karl Olsen [mailto:kro@...] 
>Gesendet: Montag, 6. Februar 2006 10:30
>An: lpc2000@yahoogroups.com
>Betreff: [lpc2000] Re: Rise and fall time of capture inputs
>
> 
>I don't think it is possible to miss a capture event because of slow 
>rise/fall times.  You get a capture event when the input is e.g. low at 
>one pclk edge and high at the next, and this will happen at least once 
>no matter how slow the input rises.
>
>[MEH]  This is an interesting fact. Thank you.
> 
>Another problem might be noise on the input so that you get multiple 
>rise and fall events around the switching level.  The datasheets say 
>that there is a hysteresis of typically 0.4V on all standard port pins 
>and some more on the I2C pins, so this should filter most noise.
>
>[MEH]  That's the reason my signal is so slow. It's filtered with an
>EMI-Filter, so no flicker should be on the line.
>
>  
>
How stable and quiet is your ground between the two units?  Ground shift 
can also occur between unit introducing "noise"?  Just a FWIW to name 
another thing that has bitten me in the past...

Regards,

TomW

>
>  
>


-- 
Tom Walsh - WN3L - Embedded Systems Consultant
http://openhardware.net, http://cyberiansoftware.com
"Windows? No thanks, I have work to do..."
----------------------------------------------------

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.