Timing runs at 1 sample per second with simulated DAQ, but runs slower when connected.

[LVIEWPQ]

This VI now write the readings to two separate tdms files at 1s intervals. The issue I am now finding is the tdms files are being written in a one reading per tab format. 

I have no idea why this is happening. 

[GerdW]

Hi LVIEWPQ,

---

@LVIEWPQ wrote:

The issue I am now finding is the tdms files are being written in a one reading per tab format. 

---

It's not an issue, it's a feature! 😄

What happens when you define the DAQmx task as "continuous" with 1Hz sample rate?

[LVIEWPQ]

---

@GerdW wrote:

Hi LVIEWPQ,

---

@LVIEWPQ wrote:

The issue I am now finding is the tdms files are being written in a one reading per tab format. 

---

It's not an issue, it's a feature! 😄

What happens when you define the DAQmx task as "continuous" with 1Hz sample rate?

---

If I switch to continuous, I get a single sheet with multiple readings but I lose the timestamp.

Is there a work around on that feature?

[GerdW]

Hi LVIEWPQ,

---

@LVIEWPQ wrote:
If I switch to continuous, I get a single sheet with multiple readings but I lose the timestamp.

Is there a work around on that feature?

---

You don't lose the timestamp, it's still given in the start time and sample rate/dt values!

You can easily recreate the timestamp column in Excel from these two values…

Reminder: what you see in Excel is a "translation"/conversion from the underlying TDMS file, done by the "TDMS Importer for Excel". You can edit the resulting Excel file or you can easily create your own conversion from TDMS to Excel.

(IMHO it's usually easier when you "divide and conquer" the whole requirements in small sub-steps. In your case that would be "logging all data into files" and "displaying the file content in Excel".)

[LVIEWPQ]

Thanks, when you break it down like that, it makes a lot of sense.

I guess my next step from here is to workout how to automate the excel processing, as it's not really something I want to have to do for everyone manually.