time-based interrupt m-series

[A_squared]

I can't find anything directly related to what I'm hoping to do, so I'm back to ask more questions.

I'm running a hardware timed analog input acquisition (80 kHz currently) using dma transfers, on-demand analog output, and on-demand DIO on an M-series PCI-622x.  I'm exploring the possibility of using a counter to send an interrupt every 200 ms using an internal signal as the counter source.  I found this forum post, which looks like it is a least a good source of information about the counter registers.  I haven't found much else on internal routing, setting up a continuous digital output task to feed back to the counter (if I have to go with a round about way to do this), etc, but as you can see I'm really stabbing in the dark.

I'm hoping I can set the counter up in a trivial setup that counts like crazy to a specified number, triggers an interrupt, resets the counter, and automatically begins counting again repeating the process.  Any enlightenment people can provide to the possibility of this or even round about ways of accomplishing a similar task would be greatly appreciated.

Aaron

[Tom_W_[DE]]

Hi Aaron-

I'm a bit unclear on exactly what you're trying to accomplish.  Is the "interrupt" you're trying to generate just a pulse to be generated out to the I/O connector for interface to some external hardware, or are you looking for a way to route an internal event signal back to the host CPU as a software interrupt (to be handled by some ISR associated with your app).

If it's the former, you should be able to achieve what you want by setting up the M Series counter for pulse train generation.  We don't have an example of this for the M Series DDK, but the 660x DDK examples do show how to set this up (specifically, ni660x/Examples/gpct_ex3.cpp would be a good reference).

Hopefully this helps-

Message Edited by Tom W [DE] on 10-11-2007 09:56 AM

[A_squared]

I'm exploring the possibility of generating an interrupt to the computer on a regular time increment.  While I wait for a response, I'll check out the 660x documentation even though it is for the other solution that you suggested.  Thanks.

Aaron