cordm

Also, if you are exporting large TDMS files to even larger text files, you should think hard if that is really the right move. Find a way to handle TDMS files in the next program. People have written importers for e.g. MATLAB and Python.

I don't see why there should be samples missing. If writing cannot keep up with acquisition, the DAQmx buffer will overflow and you get an error during acquisition. If you doubt your own code, use the built-in DAQmx logging shown above. Otherwise, use NI_MABase.lvlib::ma_time continuity checker.vi to to build a continuity checker for waveforms

Two possibilities: use 64 bit version and have more memory, or use the offset and count terminals of TDMS Read to read data subsets.

I don't think that's true. Most likely a problem with the exporting.

right-click the node, select "help" and read the manual, please why use a while loop? use an auto-indexing for loop!

Use Get Waveform Attribute (Waveform>>Get Attribute) to read the NI_ChannelName string attribute from each waveform. Add another loop before the first one where you get it from each waveform and then write it to the file. DAQmx creates that attribute automatically. This is what Waveform Graphs use for plot names.

First search result for "labview loop tunnel mode": Auto-Indexing Tunnels with For Loops and While Loops in LabVIEW In your case:

If the time appears for each channel, then you didn't set the loop tunnel mode to last value.

Use probes to check if there is an error: right click the wire and select "Probe" in the read loop. Do Hi_Rate_Volt and Hi_Rate_Trig use the same channels? You cannot run two tasks at once that use the same channels.

Sorry, I misunderstood. So when the threshold is crossed, the Hi_Rate_Trig task should start, but Hi_Rate_Volt should continue? There are plenty of ways to do that. One is to use a notifier for communicating from one loop to another. The loop that should be triggered waits for a notification, which the slow sampling loop will send when the threshold is crossed. The data and type of the notifier don't matter in this case. The triggered task can run multiple times, which may or may not be desired. A notification can also be send while the trigger task is running and it will then run again after it has finished. R_R_9_MTDS_Split_Rec_retrig_CM.vi

Sure, just wire another button to stop those loops.

That is just the first value of the Y array, not its maximum. I assume you want to start the Hi_Rate_Trig task after reaching the threshold, right? Your VI won't do that, because the case structure executes once at the start when the boolean is still false. Get rid of the local variables and use data flow instead. Some more points: either wire a number of samples to read or a duration to the DAQmx Read VIs. That makes your waveforms the same length which makes postprocessing easier. Check what works with your resampling duration For continuous sampling mode, it is usually not necessary to wire the samples per channel terminal. labels keep the block diagram and front panel readable See if the attached VI does what you want. R_R_9_MTDS_Split_Rec_trig_CM.vi

Use the builtin TDMS logging function and set the samples per file via property node (DAQmx Read class): https://www.ni.com/docs/en-US/bundle/ni-daqmx/page/multiplefiles.html R_R_9_MTDS_2_CM.vi

You are trying to wire an array to the case selector. Extract the maximum value from the Y array using Array Max & Min. You might also want to take the absolute value of the Y array.

There is a list of discord servers on the wiki: https://labviewwiki.org/wiki/LabVIEW_Community_Managed_Discord_Servers