06-26-2007 04:20 PM
06-27-2007 03:33 PM
06-27-2007 04:07 PM
Thanks so much for your reply. I still have a few questions remaining:
In the example file, DOsingleBufBurstHandshake653x.c, the general programming is as follows:
1. call DIG_Grp_Config (configure groups of ports as output, with handshaking)
2. call DIG_Grp_Mode (configure the handshaking parameters)
3. call SET_DAQ_Device_Info (setup for internal PCLOCK)
BEGIN WHILE (forever)
4a. DIG_Block_Out (initiate the burst transfer of a single buffer of my data)
4b. DIG_Block_Check (check if burst transfer complete...this is not a necessary step)
ENDWHILE (does it go here ???....)
5. DIG_Block_Clear (clear the block operation)
ENDWHILE ( -OR- does it go here ???....)
6. DIG_DAQ_Device_Info (restore default PCLOCK direction)
7. DIG_GRP_CONFIG (unconfigure group)
QUESTION: since I want to output a continuous stream of buffers, should my BEGIN/END WHILE stamement include the call to DIG_BLOCK_CLEAR or not ?
IN response to your last reply, I am actually more worried that I will not be able to output 2 consecutive buffers quickly enough.I am worried that the call to DIG_Block_Check() will slow down my program. I need to output consecutive fixed-length buffers (in a continuous WHILE loop) in a very specific time period, where each individual buffer is output using the burst protocol. So I am just , for now, trying to make sure that I am configuring the card correclty to begin with.
Thanks very much !!!!!!!
06-27-2007 05:52 PM
"After Traditional NI-DAQ (Legacy) starts a block transfer, you must call DIG_Block_Clear before Traditional NI-DAQ (Legacy) can initiate another block transfer. Notice DIG_Block_Check makes this call for you when it senses that Traditional NI-DAQ (Legacy) has completed a transfer. DIG_Block_Clear does not change any current group assignments, alter the current handshaking settings, or affect the state of the pattern generation mode."
06-28-2007 08:45 AM