LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

usb-6008 crashes

Hello,

 

My USB-6008 OEM card crashes after approximately 6 runs of my test.  In order for it to work again I have to unplug the USB cable...  I have it connected to a USB hub that has a seperate power supply.  This seems to help a bit.

 

Does anyone know what can be done to correct this from happening?

 

 

Thanks,

0 Kudos
Message 1 of 14
(4,537 Views)

Care to share your code?  One of the things that could possibly be causing this is not cleaning up your DAQmx tasks.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 2 of 14
(4,534 Views)

Hi floresma,

 


I have it connected to a USB hub that has a seperate power supply.  This seems to help a bit.


 

I had a similar problem with an "in-box" NI6008: when you draw too much current over some of the in/out pins the 6008 needs a cold start (aka USB unplug/re-plug) to work properly again. (It didn't report an error as long as the DAQmx task is running, but on restart of the DAQmx task the 6008 isn't available anymore.)

 

Could you check all your I/O pins for shortcuts or low impedance shunts?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 3 of 14
(4,528 Views)
0 Kudos
Message 4 of 14
(4,515 Views)

You really should clear out your tasks in your cleanup state.  But I think GerdW is on the right track.  You likely have a condition where you are drawing too much current.  The DIO can only drive 8.5mA, 102mA total.  I know the current ratings are a little higher using the external power supply than using the USB power.  So you really should make sure you are not on the edge of how much current you are drawing.  Adding buffer circuits to the DIO should help.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 5 of 14
(4,511 Views)

I checked my circuit.  There are no shorts, or low impedance shunts...

 

0 Kudos
Message 6 of 14
(4,509 Views)

Hi 

 

This is a known problem with the NI USB devices. I don't understand why there is till today not a official solution from NI !?

What do you mean by "crashes"? The problem I have is the USB device does not exist any more in the system hardware list. As a result, you have to unplug the USB cable and plug in again... And this is really annoying!

 

You may restart the USB device programmatically: https://decibel.ni.com/content/docs/DOC-22660 And also I wrote in the command that you may use another way to make it more smoothly (devcon64 restart *PID_729B*).

 

I remember that the problem because of the bad USB structure of the computer. Most of the laptops don't do this well. So the solution with devcon is the one I have. 

0 Kudos
Message 7 of 14
(4,481 Views)

I had same problem for me this solution worked, in the initialization fase I added the following DAQmx channel property: Analog Input ->General Properties->Advanced->Data transfer and memory->USB Transfer Request count and set the property to 1DAQmx channel property.png

0 Kudos
Message 8 of 14
(4,474 Views)

Hi,

 

I tried this method, but it only seems to run on XP.  Do you know what the command lines would be for windows 7?

 

 

Thanks,

0 Kudos
Message 9 of 14
(4,456 Views)

Hi,

 

How did you configure your DAQmx chanels?

 

 

Thanks,

0 Kudos
Message 10 of 14
(4,455 Views)