07-05-2005 02:48 PM
07-05-2005 02:55 PM
07-05-2005 02:56 PM - edited 07-05-2005 02:56 PM
Of course, there is a slight code flaw that there is a nonzero chance (1 in 4294967296 ;)) that the timer output is naturally zero, in thise case it would reset again, breaking the desired functionality.
To make it totally waterproof, you should modify it as shown for example in this attachment.
Message Edited by altenbach on 07-05-2005 12:56 PM
07-05-2005 03:12 PM - edited 07-05-2005 03:12 PM
Message Edited by Aquaphire on 07-05-2005 03:17 PM
07-05-2005 03:16 PM
07-05-2005 03:25 PM
07-05-2005 03:40 PM
07-05-2005 04:25 PM
Don't overdo it! 🙂
Why do you think you need to duplicate all that code at the bottom? (One little case structure does everything you possibly need for this.) Then you take the value in seconds and display it as a U32 and call it "millisecond timer value"? This makes little sense. You also have two boolean shift registers that always carry the same value. This is redundant.
U32 is unsigned integer, so you loose all decimal places. IF you want to show the raw millisecond timer value, just tap into it before you divide by 1000 to get the seconds. Right? 😉
Maybe I don't quite understand what you are trying to do.
07-06-2005 08:13 AM
07-06-2005 09:09 AM