01-08-2020 11:06 AM - edited 01-08-2020 11:07 AM
Maybe not the best way to do this but I currently have the following setup to plot 8 digial signals and 8 Analog signals to a mixed signal graph:
I now would like to save those signals to the a TDMS file
From examples I've looked at, it I seems that I could use the 'configure logging.vi' block
Can I use this block in the same way with my setup?
Where I am unclear is, if yes, how to wire these blocks so that the digital and analog signals are written to the same TDMS file correctly.
Alternatively I could always export the plot to excel but I feel that its not the best way to store the data....
any advice on improving my current setup is also welcomed! 😉
01-09-2020 03:37 AM
found my solution here! 🙂
01-09-2020 05:27 AM - edited 01-09-2020 05:29 AM
@sherzaad wrote:
found my solution here! 🙂
TDMS Data Logging From Multiple DAQmx Tasks in LabVIEW
I till have a problem.... 😒
the TDMS write Function block is not accepting the digital waveform input!
from the help for that block its seem that:
"If the data input contains compressed digital data, you must enter the name of the compression channel as the first entry in the channel name(s) in array."
"channel name(s) in" accepts a string but what should I write in it is not clear to me! 😞
How to setup the block to accept digital waveform input?
Any help would be much appreciated...
01-09-2020 07:17 AM
the TDMS write Function block is not accepting the digital waveform input! ....
Ok.... from what I have been able to understand is that this block does not accept a 1D digital array waveform.
So... the next question is:
How to save the digital waveforms to TDMS?
Anyone any ideas????
Really need a solution to this problem....
01-09-2020 10:38 AM
TDMS is a very flexible way for storing data.Some ideas:
1) Convert each digital channel to an analog waveform, make an array and save it to TDMS (this creates a very redundant data file, a good and fast approach only if your sampling rate is low and your recording time is not too high);
2) Save your binary port data as U8/U16 and store only port status variations with relative event timestamps (like xy couples, where X is timestamp, Y is port status). This is a more compact way to store, but not as a waveform data type.