Official Definition of the Waveform Data Type?

[tarheel_hax0r]

I'd like to know if there's an official, rock-solid, This Is The Final Word sort of a PDF document somewhere that defines the "Waveform Data Type."

I'd like to know National Instruments' official position on its constructors, its destructor, its public members, its public member methods, an encyclopedic list of the possible errors it can throw, etc.

I gather that it has at least an x0, a dx, and an array of observed values among its public members. Similarly, it can take an {x0, dx, array} bundle as arguments to one of its constructors. There appears to be another constructor which takes merely an Array as its argument, and then sets x0 = 0 and dx = 1 as defaults.

It looks like other people have had similar question
s, and didn't get much help. Compare this thread:

http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=135&HOID=5065000000080000006F8E0000

It also appears that some subtle changes were made to the Waveform Data Type between Labview Versions 6 & 7. Compare this KnowledgeBase Article:

http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/e29ef649e3dcd53186256db000565fba

So: Is there an official definition of the Waveform Data Type, and, if so, where does that definition reside?

Thanks!!!

[Greg_McKaskle2]

> I'd like to know if there's an official, rock-solid, This Is The Final
> Word sort of a PDF document somewhere that defines the "Waveform Data
> Type."
>

The waveform did change between LV6 and LV7, and it may change yet
again, and that is why it is treated somewhat opaquely.

As you mentioned, it has several nodes on the diagram that can construct
it,and lots of nodes for operating on a waveform. From the questions
you are asking, I'm assuming you want to manipulate waveforms in C/C++
code. I looked through extcode.h, and it doesn't seem like there is
much public info.

If you could explain what it is that you are trying to accomplish, there
might be easy ways of doing things through the public info. For
example, if you are looking to construct a
waveform, your DLL can return
the member info and a wrapper VI can build the waveform from the member
info. The user of the VI doesn't see any difference between your VI and
the ones from NI.

Anyway, with more background, I might be able to help you more.
Greg McKaskle

[falseth]

Hi everybody. Does anyone finally discovered the answer for this question? I have found a lot of topics about this, but without a conclusive reply. If someone could help me... Thanks in advice.

My regards,
Vinicius

[TCPlomp]

Hi Vinicius

The answer is given here:
LV data storage
Mainly it is a timestamp, dt, array, attributes

Might be hard to decode.

Ton

[falseth]

Hi TonP. I think it may help. Thanks a lot.

My regards,
Vinicius