Windows 11 not getting 16ms accuracy VIA Timed Loop (timestamp in file jitters between 15 and 17ms)

[nayil100]

To get the scaling from NI MAX, this is how I need to set it up right? I am trying to get the scaling off MAX for the slower loops,

[GerdW]

Hi nayil,

---

@nayil100 wrote:

To get the scaling from NI MAX, this is how I need to set it up right? 

---

There is nothing visible in your image related to "scaling"…

You just start a DAQmx task, read waveforms and use only the first sample of each waveform!

[altenbach]

---

@nayil100 wrote:

To get the scaling from NI MAX, this is how I need to set it up right? I am trying to get the scaling off MAX for the slower loops,

---

• You code does not show any scaling
• If you only need one sample, why do you collect N samples per channel and discard the rest?
• Why not just collect an array of N channels 1 sample, eliminate all that duplicate data juggling??
• If you want the elements order, don't wire all these indices to 'index array". Same for element zero. Except for the wait, you can delete everything blue inside the loop and nothing will change.
• Where is the terminal of the stop button?

[nayil100]

Hey GerdW,

This is how I created tasks in NI MAX and scaled them via custom scale,

I have had some Labview consultants program it this way and I could never get around to why they did. 

[nayil100]

Oh, my goodness! 

I didn't know this existed. LMAO!

Scaling is done here,

Stop button is in a while loop far away in the block diagram :S.
I am sorry but, I have no idea how to make the Block Diagram smaller. I have tried and none of my codes ever end up looking like post cards. 

[GerdW]

Hi nayil,

---

@nayil100 wrote:

I am sorry but, I have no idea how to make the Block Diagram smaller. I have tried and none of my codes ever end up looking like post cards. 

---

• You could start by combining all loops running at the same iteration rate, like those two "100ms wait" loops in your image.
• You could use the PtByPtMean function instead of creating shift registers with several read taps (at the left border) to calculate a running average.
• You could apply the same rules for index inputs at IndexArray you just learned on that loop to the right of the image! Why not index the complete row, then use one (1) IndexArray function to get those 4 elements of the row?
• Why do you hide boolean indicators when they are FALSE? IMHO this makes a bad UX!
  Design the boolean indicators to be transparent when FALSE or any other way to indicate the "no problem" state…
• USE subVIs to create readable code…