USB6216 - AI read alone not happening..

[MogaRaghu]

On a machine running on Beckhoff CP22xx Panel PC, the code uses LV2015 + USB6216 + 2 Nos USB6001. Platform is WIN-10 Pro.  All well for about 8 months. 

Last week tried to bring in some features to the code  ( not impacting the DAQMx segments at all ) and tried to compile and upload.  Surprisingly all the AI read channels have become dead.

Fearing HW issue, reloaded the old code. All fine. 

This is extremely funny ... and irritating. My PC uses DAQMx Version 15.0.1 and  the machine PC uses DAQMx Version 15.1.0 ... Can this cause so much trouble ? What else can be the reason ?

Anyway i think i made a mistake of migrating to the USB versions from the time proven PCIe  version hardware - they were so good and reliable. In contrast the USB cards are a real pain to get going reliably - they work today and not tomorrow.  ( Using a powered USB hub made matters better ) 

Any pointers to a solution appreciated. 

[Blokk]

1. Yourself mention that the DAQmx versions are different. Why do not you try to match the versions?
2. USB hardware connected to problematic USB hubs/ports can cause problems. If you use a desktop PC that best is if you buy a PCI USB card. I use USB cDAQ for a long time, connected to a laptop's USB port. Runs without any problem for years. However, when I used the USB3.0 ports on the laptop, I used to have unexpected errors produced by the USB driver. Moving the cDAQ to the "normal" USB2.0 port solved these bugs.

[JensG69]

This is extremely funny ... and irritating. My PC uses DAQMx Version 15.0.1 and  the machine PC uses DAQMx Version 15.1.0 ... Can this cause so much trouble ?

AFAIK, no, that shouldn't be a problem. Only the DLL-calls to DAQmx are part of the executable, and as long as all DLL-calls are also available in the other DAQmx version, everything runs fine.

What else can be the reason ?

Any pointers to a solution appreciated. 

[MogaRaghu]

---

@Blokk wrote:

1. Yourself mention that the DAQmx versions are different. Why do not you try to match the versions?
2. USB hardware connected to problematic USB hubs/ports can cause problems. If you use a desktop PC that best is if you buy a PCI USB card. I use USB cDAQ for a long time, connected to a laptop's USB port. Runs without any problem for years. However, when I used the USB3.0 ports on the laptop, I used to have unexpected errors produced by the USB driver. Moving the cDAQ to the "normal" USB2.0 port solved these bugs.

---

Of course... just now downloaded the DAQMx 16.0 and installed. Will do the same on the Panel PC and check on Monday. It better behave thhis time around !! So in your case USB2.0 seems to be better than USB3.0 ... the problem with evolving technologies. Atleast with PCI this issue is not there ...