pulsin_max does not cut short the time used by PULSIN? It makes PULSIN ignore everything that happens after pulsin_max duration but the next command in line is not implemented until PULSIN has gone through all its 65,535 ticks.
If this is the case, what can I do to detect within, say, 25 millisec something that happens every 20 millisec or not at all?
Ken





Bookmarks