How to make a table retain values?

[LabNoob14]

I have a simple data log that records a sample, but it only updates in one row of the table. How do I get it to retain all the previous readings?

I know it has something to do with the shift register, but I can seem to find out what makes it work.

Thanks for you help

[Mancho00 · Accepted solution]

Your shift register needs to be fed through the false case, also. Otherwise it resets it to an empty array.

[LabNoob14]

Oh yeah, thanks lol.

Do you know how I can wire up the elapse time for the entire run duration instead of just the target time control?

[Mancho00]

 wrote:

Oh yeah, thanks lol.

Do you know how I can wire up the elapse time for the entire run duration instead of just the target time control?

---

Just get the current time and subtract the start time. (Get Date/Time in Seconds)

[altenbach]

---

@Mancho00 wrote:

 wrote:

Oh yeah, thanks lol.

Do you know how I can wire up the elapse time for the entire run duration instead of just the target time control?

---

Just get the current time and subtract the start time. (Get Date/Time in Seconds)

---

I typically use high resolution relative seconds instead. A DBL uses fewer bits than a timestamp. 😄

[Mancho00]

---

@altenbach wrote:

---

@Mancho00 wrote:

 wrote:

Oh yeah, thanks lol.

Do you know how I can wire up the elapse time for the entire run duration instead of just the target time control?

---

Just get the current time and subtract the start time. (Get Date/Time in Seconds)

---

I typically use high resolution relative seconds instead. A DBL uses fewer bits than a timestamp. 😄

---

It says don't use over long periods of time.  Any idea what a "long" time is?

[LabNoob14]

Haha I dunno, somewhere between 1 and infinity?

[Kyle97330]

"A long time" in this case is probably in the neighborhood of 49.7 days of PC uptime.  The "High resolution" VI returns a value that's just a more precise version of the "Tick count (ms)" VI, which is a 32-bit unsigned integer counting milliseconds since the last time your PC restarted.  When you reach the 49.7 day threshold they probably both loop back around to zero, messing up any calculations you're doing.

[altenbach]

I doubt the DBL will ever roll over, you'll just lose resolution when subtracting values that differ by a huge order of magnitude.