One good reason could be the 2 DIV32 INSIDE the test loop ...
I measured once DIV32 took ~ 700µs ...
this is at least one very good reason for the PULSIN way to show a false result on the scope ... despite calculated RPM value to be right.
Alain
|
method problem ...
One good reason could be the 2 DIV32 INSIDE the test loop ...
I measured once DIV32 took ~ 700µs ...
this is at least one very good reason for the PULSIN way to show a false result on the scope ... despite calculated RPM value to be right.
Alain
************************************************** ***********************
Why insist on using 32 Bits when you're not even able to deal with the first 8 ones ??? ehhhhhh ...
************************************************** ***********************
IF there is the word "Problem" in your question ...
certainly the answer is " RTFM " or " RTFDataSheet " !!!
*****************************************
Members who have read this thread : 0You do not have permission to view the list of names.
Posting Permissions
Bookmarks