Hi EFG, How about One Shot Pulse Generator?
The rates and pulse period sufficiently slow you could do this entirely in code.
You have not stipulated decision latency.
Your tasks are -
1) Detect missing pulse, no input
2) Detect pulse too short/long, period OK
3) Detect pulse OK, but period is not
You could use a counter that is enabled by input, when input returns low
look at counter value to determine if runt pulse, or if pulse too long.
A secondary timer/counter to implement period checking, to make
sure no pulse case is handled, as well as out of spec period for
Cocde or HW can be used, consider a LUT to implement a state machine
along with counters/timers to measure pulse parameters.
This reference has a one shot approach, but keep in mind one
shots notorius for poor timing accuracy.
You could implement a one shot with comparator and reference
to get more accurate timing.
hello dear colleagues
many thanks for your fast responses and all the inspiration.
i did the PWM single shot solution and it works very well.
it really helped me out with no additional software overhead.
best regards Markus
(EFG is the name of the company i work for ;.)
my_solution.JPG 40.2 K
Very Good! However I have one anxiety. Your signal_in and Clock_2 is wired OR. It may ok, that is a test wired, will never got collision.