DAQ Assistant x_value (usually Time Elapsed) is now "0"

[JJWatJCI]

Hello,

I am using DAQ Assistant (please, show mercy) to capture a few temperatures (from thermocouples) and a few voltages (from pressure transducers) and had been using the column X_Value as my time elapsed.  However, on a new computer (Win 10) writing a new VI, the X_Value column is now "0" all the way down.

The VI is in pieces right now which is why I haven't attached it yet.  If there is a need, after I get it back to where I had it, I can post it.  For what it's worth though, in troubleshooting, I created a new, different, and simplified VI and it did the same thing. 

Does anybody know why/how I'm blocking those values and getting 0 (not 0.0 or 0.1 etc.) in my X_Value column.

Thank you for all the help; as I am new here, if there's anything I missed, please let me know and I'll do what I can ASAP.

Thank you.

[Bob_Schor]

Well, you are using the Dreaded DAQ Assistant, so all bets are off.  Also, you failed to attach code, so we can't see what you did, where you went astray, and precisely what is happening.  Would you like us to guess?  How would you tell which "guess" was correct?

Bob Schor

[croohcifer]

Please post your example and clarify what you mean by the "X_Value" column.  That sounds like a log, which likely has nothing to do with the DAQ Assistant considering that the DAQ Assistant only natively supports logging TDMS files, which don't have any sense of an "X_Value" column.  Your problem is probably in the (still somewhat dreaded, though slightly less so) Write to Measurement File express VI, which I assume you're using.