how to count rising edges of a pulse in ADUC842

And you didn't notice the different color around my waveform, and then suspected that maybe I had used some special tags? So no reason to look at the posting instructions directly above the message input box to see what tags they mention there?

By the way - counting edges only tells us how many edges you will see. It doesn't tell you what pattern. And since you still haven't told us the answer to my questions, we still don't know if there could be other patterns with similar number of pulses.

Another thing - when using a 14ms measurement window, that window may not be perfectly aligned with the pattern. So sometimes you may start the window at a zero. Sometimes at a one. Sometimes just at a flank. If the pattern is "exactly" 14ms and your timer code takes "exactly" 14ms, then you can get the wrong count because the 14ms are never really _exactly_ 14ms. The side generating the pulses have a limited precision to the time-generating hardware. So have your processor. And there are latencies and jitter in the code execution.

How that affects your code is still unknown - without full answers to all questions, there are no proper specification available to know exactly what the full requirements are. All we know is that counting flanks does not detect a specific pattern. It can be enough to decide that the correct pattern is there if it is known that there can't be any other pattern that gives similar edge counts. But that is not covered by your descriptions of your problem.

How fast do you think this project will progress, if you can't manage to give a proper - and complete enough - description of the problem? Did you find my itemized questions unreasonable? Can you then explain why you think they are unreasonable?

And you didn't notice the different color around my waveform, and then suspected that maybe I had used some special tags? So no reason to look at the posting instructions directly above the message input box to see what tags they mention there?

By the way - counting edges only tells us how many edges you will see. It doesn't tell you what pattern. And since you still haven't told us the answer to my questions, we still don't know if there could be other patterns with similar number of pulses.

Another thing - when using a 14ms measurement window, that window may not be perfectly aligned with the pattern. So sometimes you may start the window at a zero. Sometimes at a one. Sometimes just at a flank. If the pattern is "exactly" 14ms and your timer code takes "exactly" 14ms, then you can get the wrong count because the 14ms are never really _exactly_ 14ms. The side generating the pulses have a limited precision to the time-generating hardware. So have your processor. And there are latencies and jitter in the code execution.

How that affects your code is still unknown - without full answers to all questions, there are no proper specification available to know exactly what the full requirements are. All we know is that counting flanks does not detect a specific pattern. It can be enough to decide that the correct pattern is there if it is known that there can't be any other pattern that gives similar edge counts. But that is not covered by your descriptions of your problem.

How fast do you think this project will progress, if you can't manage to give a proper - and complete enough - description of the problem? Did you find my itemized questions unreasonable? Can you then explain why you think they are unreasonable?