I recently play a bit with TDMS files, because I need to store lots of measurement settings and results in such file. First of all, since I want to make the TDMS human readable as much as possible, I decided not to store measurement settings as "properties", but in Channels, at the different Groups (I will have several Groups, one will contain a 2D array of I32s, all the other Groups settings and measurement results, but mostly as name-value pairs).
I started to play with a test VI, see its snippet here (I also attached the result TDMS file):
I have got several questions, maybe some people can give better ideas for what I want to do, and explain some certain strange things I see and not clear why 🙂
So, the list:
Crap, I typed a long reply and NI lost it some how. Checkout my XLSX conversion which can have custom things done for properties so they are more human readable. Run the batch demo in it to see. As for 2, and 3 I agree. With 2 I'd iterate over all properties with a for loop, but I'd expect it to work or return an error. And 3 would be more intuitive if it was a variant.
Thanks much! I will check out this conversion tool tomorrow, looks very useful! 🙂
AFAIK, wiring up to read a single property of a TDMS file (wiring Property Name, Group and Channel) allows you to specify a datatype via the "Datatype" input and it will return a single element of that type, not variant.
I can't remember how it behaves when returning multiple properties, I suppose it always defaults to Variant there.