Brett,
Thanks for the reply. I looked at the "Create wfm example.vi" I guess it side-steps the problem of the null timestamp with the wfm generation functions.
I not really getting, t0, dt, etc are attributes of the wfm. Also it's really 2 bug issues:
1. Why are the 'generate sample wfm" functions returing a null timestamp?
2. How would one - then modify the t0 to correct this problem?
It's very clumsy to deconstuct the wfm using the "Get" and "Build" functions - Also I'm trying to extract some data for real-time analysis and this is a whopping amount of code to do something so simple! I would also suspect the "Build wfm" function would create a new copy of the entire wfm in memory - very bad for performance. My code is clocking at 60kHz.
If I acquired the data as a 1D array - the parsing would be simple - the wfm parse should be analogous, I just shake my head when I look at all the coding I have to do to get a portion of the array out. Not to mention that I am slicing part of the array out to actually do something with it! I've already used up quite alot of CPU budget, manipulating the wfm data.
I've been coding in LabVIEW for awhile - I'm not new to it. But the more I work with the wfm data type it seems clumsy and not well planned out.
This concept of the t0, dt and data is pretty simple - it seems NI has made it overly complex.
