Troubles with USB Hubs and Colibrick or U-PAD2. Acquisition stops suddenly.

At first, check if Colibrick/U-PAD2 isn't connected to a USB hub. Problems are mostly related to the USB power supply, so the hub should definitely have an external power source.

Note that Colibrick/U-PAD2 is sensitive to communication delays. Responsible for those delays in USB communication may be the computer hardware or software. Processor overload, low RAM memory or running processes blocking the processor or communication lines should be checked. In case the communication is interrupted for more than 10 seconds, an error will be invoked. Error messages "No data from Acquisition", "No data received for ..." and similar may appear randomly. As a consequence, the running acquisition is stopped and the running sequence is interrupted. In case the problem is temporary, sending the method again may solve the problem. If not, disconnect and reconnect the USB hub.

Try the Task Manager and inspect the processor load and processes consuming a large amount of CPU time or memory. Suspected programs are incorrectly set anti-virus (continuously checking file types used by Clarity during data acquisition). The *.raw, *.prm, *.audit, *.tmp file types should be disabled for scans. Any other programs monitoring files on exchangeable media (i.e. programs for organizing and presenting pictures, music or video, including some CD/DVD burning programs) may also interrupt the acquisition.

Also, when the acquisition is running, it may be interrupted by any actions started during this, like printing to a slow USB or network printer, large file transfer over network or USB, connecting or disconnecting USB devices, computer entering sleep mode or screen-saver activation.

The above-mentioned problem with communication with Colibrick/U-PAD2 was not observed when the USB hub is connected to the USB C connector on the PC.