USB 6210 times out with 200284 on RHEL5 using nidaqmxbase 3.6 while trying to sample continuously.

[Chris-NI]

Thanks, Jim.  I know the Applications Engineer you are working with on your other thread.  I will reach out to them here at corporate and collaborate.

Regards,

[ase-tom]

Hi Chris,

I'm running Linux native to the laptop I'm using - no virtual machine in use. The four USB-6210 devices are also plugged directly into the laptop.

I tried using niiotrace and I've captured some data that appears to be too big to post (58MB). The timeout begins at 15:23:30 in this data. Do you want to look at this data and if so, how do I get it to you?

Hopefully this will provide some clues. I seem to be able to consistently reproduce this timeout, but it doesn't happen at the exact same point each time.

Thanks for looking into this.

Best Regards,

-Tom

[Chris-NI]

Hi Tom,

Thanks for the update.  As for the I/O Trace, could you decimate the file to only contain the last bit of information that is pertinent to the timeout?  I imagine most of the trace consists of the same calls over and over again.

We're getting a Linux box setup to run some tests next week to see if we can reproduce the issue here.  I'll keep you posted on that as well.

Regards,

[ase-tom]

Hi Chris,

This file is a little smaller.

-Tom

[ase-tom]

Hi Chris,

I should have mentioned - the timeout-2.zip file is just a smaller version of the timeout-smaller.zip file.

-Tom

[Chris-NI]

Thanks for the info, Tom.

We are working on getting a Linux box here.  It may be Wednesday before we have a test station setup to replicate this setup.  I plan to have an update before the end of the week.

Regards,

[Chris-NI]

Hi Tom,

I have reproduced your issue here and we are currently investigating the cause.  We should have a Corrective Action Request (CAR) # soon that you can reference to see when a fix is issued.  I'll also let you know of any work-arounds we come up with.

Regards,

[Calmor]

Chris,

I'm excited about this turn of events, even if it doesn't help my particular issue.  I'm happy to see NI taking quick action.  I'm hoping that my issue is related to Tom's and both are remedied.

Thanks,

Jim

[ase-tom]

Hi Chris,

Thanks for the update and I'm glad you were able to reproduce the problem. I'll keep a look out for the CAR.

Thanks again,

-Tom

[Chris-NI]

Hi Tom and Jim,

I have filed CAR # 387231 with R&D to further investigate this issue.  I am going out of office next week for a long while, but I am not the one looking into this potential bug.  Once I'm out, I'll make sure another one of my colleagues keeps this thread up to date if R&D uncovers anything.

Regards,