Jump to content

TDMS wavform store - not working with some data


Recommended Posts

I know this was working with LV8.2. I just downloaded 8.2.1 and it's not working. I've enclosed a simplified example. I get error -2513 when I run it.

Possible reason(s):LabVIEW: LabVIEW does not support properties of the specified data type.

First could someone who has 8.2 please confirm that it doesn't give an error?

If I delete array elements 0 and 1 from the "data" control it works. If delete any other combination of elements I get the error. I tried deleting all the elements and created some new waveform elements without attributes and it worked. I can't see anything wrong with the existing attributes. Can anyone see what could be wrong?

Thanks,

George

Link to comment

George,

I have tried your VI and I can reproduce the problem. The root cause is that the data type of the "NI_ChannelName" property on some of your waveforms is "tag" instead of "string". My first thought would be that the change in data types was introduced by a new driver version. Did you recently update your drivers?

The issue is filed as CAR# 489IR4WJ. There is a workaround, which is converting the property type from tag to string (that's a perfectly valid conversion). It's not nice, but at least it is simple.

http://forums.lavag.org/index.php?act=attach&type=post&id=5459

Sorry for the inconvenience,

Herbert

Link to comment

QUOTE(george seifert @ Apr 11 2007, 06:28 AM)

I was taking the AI.CustomScaleName from the DAQmx Channel node and feeding it directly to the Set Attributes VI.

I see. I thought you had taken the whole waveform from a DAQmx VI, in which case it should have been a string. We normally coerce tags to strings in most LabVIEW functions, but if they are "hiding" in variant/waveform attributes, that doesn't happen automatically. Need to add that in TDMS Write.

Thanks,

Herbert

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.