While running a test I developed I noticed an odd DAQmx behavior. After a USB 6212 connection was momentarilly interupted all read and write tasks associated with the device hung until the USB cable was disconnected. It would have been easy to code around if there was a Dev connection event and a Dev disconnection event that I could use to pause operations and trigger a Device reset. Since the devices are PnP couldn't the DAQmx API simply make the system hardware connect/disconnect events visable?
"Should be" isn't "Is" -Jay