Python API, for loop, trigger delay

[cmacrom]

Hello,

I am trying to write the attached LabView code (courtesy of a NI: Gregor Hufnagel)  in the python API, but I have a few questions:

1. How’s the for while loop treated in Labview?
   1. Is it also HW programmed into the DAQ?
   2. Or is it still controlled by windows?
2. How is the while loop treated in the python API?
   1. Can I expect an issue with the windows timing?
3. Does the trigger delay exists in the python API? I could not find it anywhere in the documentation.

[GerdW]

Hi cmacrom,

---

@cmacrom wrote:

I have a few questions:

1. How’s the for loop treated in Labview?
   1. Is it also HW programmed into the DAQ?
   2. Or is it still controlled by windows?

---

There is no FOR loop visible in your image…

In case you are talking about the WHILE loop: it is executed in software, there is no way to implement it in DAQ hardware (except you start to program a FPGA). That loop execution is of course dependent on Windows execution timing/influences.

[cmacrom]

...

[ZYOng]

The while or for loops are software-timed, regardless of whether it is executed in LabVIEW or Python. The DAQ is hardware-timed because of the sample clock. The calling of DAQmx Read API is still software-timed but the sample points acquired by the hardware are timed by the onboard sample clock in the DAQ.