DAQmx Timing change with LV2009?

[Peg]

With LV7.1, I have used the attached subvi (modified here with the addition of a case structure around the DAQmx Timing to illustrate the current issue) in many applications. Now we have upgraded to LV2009 and I get the error message -50400 if  DAQmx Timing is part of the task. I don't mind changing the subvis in these applications if that is necessary, but I don't want to do that if I'm missing something else.

I have NiMax 4.6.2 and DAQmx Driver 9.0.2

Thanks, Peg

[cirrusio]

Hey Peg,

I am unable to reproduce this error and I am using similar versions of the same software.  I am using a USB-9162 with a cRIO-9263 for the output.  Could this be a hardware issue that you are having?  Is the card seated properly?

Cheers,

Matt

[Peg]

Hi Matt,

Thanks for checking. I am using a PCMCIA card 6715. I have the same error in two computers with LV2009, so I doubt that I failed to seat it well twice. Plus, when the timing is not used, it outputs a voltage as asked. I wonder if there is a driver issue but as far as I know, I have the right DAQmx drivers.

So to be clear, it runs ok for you when the case structure is True, allowing the DAQmx Timing to be included?

I'll have to keep trying. Maybe I'll try a different device.

Thanks,

Peg

[cirrusio]

Oops, my fault;  I was writing to the wrong device.  I initially had the error -200294:

Not enough samples were written to satisfy the initial data transfer request condition.

To successfully start a generation, increase the number of samples initially written to the buffer before starting.  Alternatively, decrease the number of samples required to start by changing the data transfer request condition.

Not enough samples were written to satisfy the initial data transfer request condition.
To successfully start a generation, increase the number of samples initially written to the buffer before starting.  Alternatively, decrease the number of samples required to start by changing the data transfer request condition.

After adding a node to fix this, I was able to execute with no error.  Here was my final VI:

Peace, Matt

[cirrusio]

Peg,

That would definitely be my second suggestion.  If you are not having issues with the data transfer mechanism, then this might be an actual hardware issue.

Matt

[Peg]

Matt, Thanks for helping me to widen my search beyond our recent LV upgrade. It does appear to be the 6715 since the example vi works fine with the USB-6211. I'll have to see if the 6715 is repairable.

Many thanks,

Peg