counter/timer pulse AND toggle : routing / triggering

[paulus19]

Hi guys,

I'm using two timers on the PCI-16-MIO-1. One to generate a pulse train and another to count the pulses in labview 8.2.

I have only two counters available and on terminal count I managed to send a pulse to the RTSI2 bus to trigger another board (to start generating a waveform).

So far it works fine only problem is that the output of the counter also outputs the pulse and I want this output to be a toggled signal (to start blanking on the amplifier). 

What I had before in labview 6.1 that worked was a 2 phase downcounter that toggled the output of one counter but also send a trigger to the RTSI2, this was possible with the CTR mode config in traditional DAQ (I think using the gate but I didn't program this) (sleep.vi).

However in the new DAQmx (count digital events.vi) I cannot get this to work. Please send me any comments!

Thanks,

Paul

[paulus19]

I made a better example ... With the two options I see so far ...

[KvZ]

Hi,

You can still configure the toggle behaviour on the counters see the following KB for more information:

Determining in Hardware When the Terminal Count of a Counter is Reached

This should also apply to the TC count for a pulse train generation.

Hope this helps

Karsten

[paulus19]

Hi all / Karsten,

I found out it was NOT possible to use toggle AND pulse in different terminals.

However I worked a way around it. Later on I saw that it was also possible to trigger acquisition on the 'toggled' signal via the RTSI bus and to use the counter output as my amplifier blanking. I guess one could also use 'pulse mode' and an external flipflop device on another output, with this solution no external electronics were needed.

Finally I used two OUT-counters, clocked with the same timebase and one is triggered on the others up-flank so they are synchronized (otherwise they can have 180' shift!!!!).

I used one "pulse freq." counter to down-divide the 20 MHz clock (master) and the other to count the flanks (slave). Using 'CO Pulse ticks' one can count in the up stage as well as in the low stage, which was convenient for my application (this didn't seem possible with 'CI cnt edges'). In CO pulse ticks: when u set the initial state to 'high' one can only use the 'low time' and 'initial delay', same goes for initial low, only 'high ticks' can be used. I didn't find this in any manual !!!  

The blanking and triggering of the acquisition is now HW timed and synchronized with my Wave Form Generation.

Thanks, Greetings,

Paul Knijn