DAQ

[hung19081997]

Hi  RavensFan,

I understand what you say. But if you make an Analog Waveform, the output signal will have a repetitive cycle. But I don't want that, for example, I have a first Digital Input signal that has an input from high to low, then Digital Output from low to high. Until the second Digital Input signal is also from low to high, right now the Digital Output signal must be high to low, these digital input signals do not follow any cycle. So how do I do with the above example? According to GerdW, should use triggers, what do you think?

[GerdW]

Hi hung,

According to GerdW, should use triggers, what do you think?

That's the point where you should not discuss the same thing in several threads!

Please keep discussions in one place!

[RavensFan]

---

@hung19081997 wrote:

Hi  RavensFan,

I understand what you say. But if you make an Analog Waveform, the output signal will have a repetitive cycle. But I don't want that, for example, I have a first Digital Input signal that has an input from high to low, then Digital Output from low to high. Until the second Digital Input signal is also from low to high, right now the Digital Output signal must be high to low, these digital input signals do not follow any cycle. So how do I do with the above example? According to GerdW, should use triggers, what do you think?

---

What do you mean they don't follow any cycle?  You say you want a  pulse pattern that has very specific timing with an  amount of time high and an amount of  time low.  So you need to use the clock in the DAQ hardware for precision.  That means making an analog waveform of whatever shape you want and letting it be output based on the hardware clock.  Right now you are relying on the LabVIEW software and the Windows operating system and however it decides timing to determine when it individually executes a high signal and executes a low signal.  The timing of the Windows clock has very poor precision.