Yes, a good idea! Demonstrating your own efforts heavily increases your chance to get help...


Beginners often think, that there's already a "ready-to-use code" somewhere. Well, there's no such thing! Because this ready-to-use code always depends on the actual application and hardware. For instance, it makes a difference, whether you need a precision of µsecs, 10µsecs, 100µecs, msecs, 10msecs, etc. It depends on maximum time period: Is it 1msec, 10msec, 100msec, 1sec, 24hours, 100days, etc. It depends on the repetition rate of time periods to be measured: Comes the next period within 10µsec, 100µsec, 1msec, 100msec, 2hours, 14days? This will determine whether you can poll the timer or need an interupt controlled timing. It also determines, how the main code has to be coded. What has the higher priority, the main code or the time period measurement?
It also highly depends on used hardware: Do you use an /INT input, or a standard port line? Is debouncing needed? Is rise time dependant triggering needed? Is noise suppression needed? Can the port line be polled, if yes, at which rate? Is windowing needed, which allows to suppress non-plausible sensor signals? Is any additional software needed for the sensor, like automatic gain control, sensor cable break detection, etc? Is a fail safe routine needed, if non-plausible sensor readings are detected? What priority is needed for the various code segments?

You see, a code is always a highly individual thing, which highly depends on actual application. There's no ready-to-use code, unless you have a typical homework problem.

Kai