![]() ![]() Trigger Counter/ Timing I/O RTSI Bus Interface DMA/IRQ Bus Interface DAC. S Series Multifunction DAQ 12 or 16-Bit, 1 to 10 MS/s, 4 Analog Inputs 2 National Instruments Tel: (800) 813 3693. So I force the generation to 0Volt rather than just stopping the task. Family (samples) Antialias Filters1 Coupling Configuration DIO NI 6120 64 M 5-pole Bessel, AC and DC Pseudodifferential Hardware. I want to control the value generated by the board at any time to avoid damaging the device I send the signal to. The AO starts generating a constant value of 0Volt. (AO), digital input output (DIO), and counter Features: 64 opto-isolated lines that can meet demand up to 24 V. P.S.: when the switch is set to OFF, the AO task is not completely stopped. High-speed USB 2.0 SSI/Star trigger bus synchronization between external trigger source and modules. Why is it working right after running the VI, but not after using the switch on the front panel? The AO task begins generating samples right after starting the task, without waiting for the next rising edge of the counter output.Ĭould anyone help me to understand what is going on, please? BUT! After turning the switch to OFF and then back to ON, the signals are not synchronized anymore. The two signals being generated are perfectly synchronized (AO and Ctr). When I run the VI, the very first start of the AO is indeed triggered by the counter. I would like to use this counter as the Start Trigger for the AO so that, when the switch on the front panel is set to ON, the AO task waits for the next rising edge of the counter output to start the generation. The generation can be stopped and (re-)started at any time using a switch on the front panel.Īside from this AO Channel, there is a counter. The regeneration is enabled so that the signal is generated continuously. In the VI I attached to this post, I have one Analog Output channel that generates a predefined signal stored in the board memory. Y- Volts.I am currently using a PCI-6120 with a BNC-2120. National Instruments PXI-6250 with 1 analog trigger: In Stock Ships Today: PXI-6251: National Instruments PXI-6251 with 16 AI, 24 DIO, 2 AO: In Stock Ships Today: PXI-6254: National Instruments PXI-6254 with 1 MS/s sample rate: In Stock Ships Today: PXI-6255: National Instruments PXI-6255 Multifunction I/O Module- 1.25 MS/s sample rate: In. ![]() Sample Data from oscilloscope: (I think the noise is from the data acquisition process). # DAQmx Configure Code (Counter Laser Trigger)ĭAQmxCreateCOPulseChanTime(taskHandleD,"DAQ/ctr0","",DAQmx_Val_Seconds,ĭAQmx_Val_Low,DELAY_D,LOW_TIME_D,HIGH_TIME_D)ĭAQmxCfgImplicitTiming(taskHandleD,DAQmx_Val_FiniteSamps,TotalSamps)ĭAQmxCfgDigEdgeStartTrig(taskHandleD, "PFI14", DAQmx_Val_Falling)ĭAQmxCreateAOVoltageChan(taskHandleAO,"DAQ/ao0:1","",-9.0,9.0,DAQmx_Val_Volts,None)ĭAQmxCfgSampClkTiming(taskHandleAO,"PFI14",1000,DAQmx_Val_Falling,ĭAQmxWriteAnalogF64(taskHandleAO,TotalSamps,0,2.0,ĭAQmx_Val_GroupByScanNumber,VoltageXY,None,None)ĭAQmxWaitUntilTaskDone(taskHandleC, TotalSamps*2*TOT_TIME) Also, using the counter clock to trigger another, and adjusting the initial delay of that counter wrt the clock, I was able to achieve my goals.ĭAQmxCreateCOPulseChanTime(taskHandleC,"DAQ/ctr2","",DAQmx_Val_Seconds,ĭAQmx_Val_Low,0.00,LOW_TIME_C,HIGH_TIME_C)ĭAQmxCfgImplicitTiming(taskHandleC,DAQmx_Val_FiniteSamps,TotalSamps+1) If you run the VI normally (and not in step by step) there is still a short delay between the two signals. The biggest realization was that, on interleaving the samples to be written to different channels, and setting up the trigger, all channels are written to at the same rising/falling counter pulse. When you execute the VI step by step, you see that the AO channel starts right away, without waiting for the counter to be restarted. I configured my code the following way and things seem to be in order. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |