A couple notes for you:
1. There's no need (and some danger!) unpacking those time stamps into "date-time records" before doing all your math to figure out delta time. All you need to do is subtract one timestamp from another! The result will be delta time in seconds, including sub-millisec resolution.
The "danger" is that your method will fail when time wraps around midnight to a new day. That may or may not affect you, depending on when this equipment can be running.
2. Another concern with your debounce method is that you're setting yourself to react to the *beginning* of bounce. If every bounce always ends up with a stable transition to a different state, you'll be ok. But if the bounce might end by reverting back to the original state, then you'll have reacted to a false transition.
Looking back to the beginning of the thread, I see you're using an X-series device that will support debounce in the hardware via "digital filtering". That method will only pass through stable states after all the bounce is done, so the issue raised above wouldn't affect it.
-Kevin P
CAUTION! New LabVIEW adopters -- it's too late for me, but you *can* save yourself. The new subscription policy for LabVIEW puts NI's hand in your wallet for the rest of your working life. Are you sure you're *that* dedicated to LabVIEW? (Summary of my reasons in this post, part of a voluminous thread of mostly complaints starting here).
