It has come up a few times from customers, and I wanted to gauge interest and solicit ideas on how this should work.
Currently, with the built-in TDMS logging support, if you want to change to a new file in the middle of logging, you need to stop the task and start again. For some use cases, this isn't practical (for example, http://forums.ni.com/t5/LabVIEW/Why-the-TDMS-file-is-larger-than-it-should-be/m-p/1176139#M511099).
The question is: How would you like to specify the "new file" behavior and what are your use cases?
For instance, a couple ideas to get the ball rolling:
Thank you for your input!
Andy McRorie
NI R&D
It has come up a few times from customers, and I wanted to gauge interest and solicit ideas on how this should work.
Currently, with the built-in TDMS logging support, if you want to change to a new file in the middle of logging, you need to stop the task and start again. For some use cases, this isn't practical (for example, http://forums.ni.com/t5/LabVIEW/Why-the-TDMS-file-is-larger-than-it-should-be/m-p/1176139#M511099).
The question is: How would you like to specify the "new file" behavior and what are your use cases?
What I'm currently thinking (because it seems the most flexible to different criteria and situations) is to simply allow you to set the file path property while the task is running (on DAQmx Read property node). The only downside I can think of with this approach is that you wouldn't know exactly when we change to the new file. We could guarantee within (for example) 1 second, but you wouldn't be able to specify the exact size.
Would this be a good solution for you? Can you think of a better way to specify this behavior?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.