LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Pulse generation

I'm sorry.

I will explain in detail.

 

Value of the box written as pulse in the image is output voltage. It outputs the values written in that box in order by using DAQmx(analog 1D DBL 1 channel N samples). The speed of outputting in order is output at regular intervals by using DAQmx sample clock.This is program that I want to make.

 

The latest problem is that the output speed is not output at the requested interval.

 

I thought there was a problem with the placement of the DAQmx sample clock and the DAQmx sample clock should be placed before writing data. But, when I move the DAQmx sample clock before DAQmx write date, error code 200479 is displayed.

In what order should I place DAQmx write, DAQmx timing, and DAQmx playback?  Is there anything I need to add?

 

The image below is the latest program I made.

 

puls.png

 

 

 

0 Kudos
Message 11 of 12
(363 Views)

You keep posting the same code screenshot repeatedly.   I don't really have anything new to say until you try something new and have a new question.   

 

Here's one new thing you should try.  Take a shipping example for continuous analog output.  It should run without error.  Save it under a new name in one of your own folders.  

   Then substitute your own data array named 'Pulse' for the original data used in the example.  Get this to run without error.  Store the 'Pulse' data inside the vi by right-clicking and choosing "make current value default".  Then post back with the *code* (not just a picture) and your next question.

 

Meanwhile, study the differences between the example code and yours.  Notice that (as I mentioned in msg #8) DAQmx Timing is called *before* writing to the buffer.  Notice that "auto-start" is left unwired at its default value of "False" before the explicit call to DAQmx Start.  Notice the loop that iterates until a user decides to stop and only *after* that is there a call to DAQmx Stop or DAQmx Clear.

 

 

-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.
0 Kudos
Message 12 of 12
(358 Views)