Sign Up
EU Cyber Resilience Act (CRA) — First Deadline September 2026
If you sell LabVIEW-based software and systems in the EU, please be aware that new CRA regulations may require you to implement security vulnerability reporting starting September 11, 2026. The VIPM Team has prepared guides to help you understand how this applies to your software applications and published packages, since it's important you understand these regulatory requirements (click the Learn More link to read these guides). Thank you for your help in keeping security front-and-center within the LabVIEW community.
Learn more

Details

First of all, thank you for the Tremendous TDMS toolkit — we use the Circular TDMS class in production for sensor data logging, and it really helps us a lot.

I want to report a timing issue that one of my users noticed today, and I was able to reproduce it myself. We feed our sensor data into the Write function as waveform data type. When I inspect the resulting TDMS file, the waveform start time (wf_start_time) saved for the channel matches the t0 of the last waveform written before the circular buffer is closed — not the t0 of the waveform that is actually the oldest (first) one chronologically in the buffer. This shifts the timestamps of all the data in the file.

When I briefly looked at the Close Circular part, I see that the data is written to the file using the circular references. Do the circular references maybe need to be reversed before writing? I'd really appreciate your help with this.

Comments


Please sign in to leave a comment.