??? 05/16/07 20:49 Read: times |
#139395 - the obvious way to do this is to use one timer as Responding to: ???'s previous message |
the obvious way to do this is to use one timer as a acounte=er and naother as a timer and get a count during, say 100mS.
when using a timer as a counter the input is sampled in one of the 12 states that a cycle comprise. This can lead to all knds of glitches if the frequency is anywhere close to the uC cycle. also, your code is defective in the respect that as it is it can not handle any frrequency >64kHz (counter overrun) Erik. |
Topic | Author | Date |
8051 frequency meter. Interrupt question | 01/01/70 00:00 | |
Formatted Code | 01/01/70 00:00 | |
Thanks Jon | 01/01/70 00:00 | |
No Problem - What about EA | 01/01/70 00:00 | |
EA | 01/01/70 00:00 | |
corrected code | 01/01/70 00:00 | |
that is a pipe dream | 01/01/70 00:00 | |
External hardware | 01/01/70 00:00 | |
Why no more than 100K? | 01/01/70 00:00 | |
the obvious way to do this is to use one timer as | 01/01/70 00:00 | |
there is a 3rd byte | 01/01/70 00:00 | |
no good | 01/01/70 00:00 | |
assuming you can do the math... | 01/01/70 00:00 | |
HUH | 01/01/70 00:00 | |
And what? | 01/01/70 00:00 | |
... and ... | 01/01/70 00:00 | |
Eh? | 01/01/70 00:00 | |
the counter is not 'a counter' | 01/01/70 00:00 | |
you should be on the safe side... | 01/01/70 00:00 | |
who cares who 'wins' | 01/01/70 00:00 | |
Continuation... | 01/01/70 00:00 | |
now let\'s cheat | 01/01/70 00:00 | |
Get something working first | 01/01/70 00:00 | |
I diasagree | 01/01/70 00:00 | |
It's WORKING!!![]() | 01/01/70 00:00 |