Yes, you can do pulse generation based on ticks. You need a minimum of 2 ticks each for high time and low time, so you'll end up dividing the incoming frequency by at least 4. This will only require the use of 1 counter, I'm not sure I follow your question about combining 2 counters.
There are 2 other approaches I can only briefly outline:
1. Use a DI task set for "change detection" sampling, sensitive to the incoming rising edge. Also set up a continuous DO task whose buffer is filled with alternating Trues and Falses. Run DO sampling off the DI task's "change detect event". Then every incoming rising edge causes a new DO sample to be generated, and your DO buffer defines those samples to alternately toggle the output state. The output will be at 1/2 the frequency of the input.
2. Use a counter set for retriggerable single pulse generation. Set pulse parameters with both low time and initial delay very minimal. Set high time to be half the known incoming interval (i.e. 5 msec, half of 10). This method depends on knowledge of the incoming frequency and its steadiness. It will produce an output that's approximately square-ish but not exactly. The output will be at the same frequency as the input.
-Kevin P
ALERT! LabVIEW's subscription-only policy came to an end (finally!). Unfortunately, pricing favors the captured and committed over new adopters -- so tread carefully.
