cDAQ 9172 USB is not recognized after PC power is cycled

[Seth_B.]

We recent updates we've been able to address some of the causes of issues that fall in to this vein.  However, certain chipsets are still behaving erratically in ways that we can't fully address at this time.  At the moment, the only effective workaround has been to use a PCI-to-USB card with a different chipset.  We're still working on finding other ways to address this issue, but given the fact that the issue presents differently based on the model of the USB controller, we are limited in the number of options we have to alter how we react to certain chipsets misbehaving.  We've had issues where fixing the problem for one USB controller can break it for others.

Regards,

[sfm-dss]

Thank you for your quick response.  I was a little hasty in reporting this issue.  The first power cycle of the PC after updating NI-DAQ showed the problem of not recognizing the cDAQ-9172 until after separately cycling power on the cDAQ-9172 while the PC was powered up.  However after the second PC power cycle, the hardware was recognized in MAX without having to cycle power to the cDAQ-9172 after the PC was at the desktop.  Maybe the first power cycle sequence was required and subsequent PC power cycles are fine.  The system is off now and unplugged. When I power it back up next I will see if all is well.