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
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 " !!!
*****************************************
With some little reflexion ....
I'd ask you to scope the signal you use from your gadget ...
Is it really a nice symmetrical square wave ???
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 " !!!
*****************************************
Its not a perfect function generator type square wave for sure. My scope has a USB output on it. This will be a good reason to learn how to send screen shots to my laptop. I will work on that tonite.
Bookmarks