Troubles with USB Hubs and Colibrick. Acquisition stops suddenly.

Most problems with Colibrick are related to the USB power supply. So if USB hub is used, we recommend using a hub with an external power source.

It's important to note that Colibrick is sensitive to communication delays. These delays can be caused by issues with the computer's hardware or software, such as processor overload, low RAM memory or running processes blocking the processor or communication lines. If there is no communication for more than 10 seconds, an error message will be displayed, such as "No data from Acquisition" or "No data received for...". This will cause the acquisition to stop and the running sequence to be interrupted. If the problem is temporary, resending the method may solve the problem. Otherwise, try disconnecting and reconnecting the USB hub.  

To check for issues, use the Task Manager to inspect the processor load and processes consuming a large amount of CPU time or memory. Programs that can cause issues include incorrectly set anti-virus programs that continuously check file types used by Clarity during data acquisition. To avoid this, disable the *.raw, *.prm, *.audit, and *.tmp file types for scans. Other programs that monitor files on exchangeable media, such as programs for organizing and presenting pictures, music or video may also interrupt the acquisition. It's also important to note that any actions started during the acquisition, such as printing to a slow USB or network printer, large file transfers over network or USB, connecting or disconnecting USB devices, computer entering sleep mode can cause the acquisition to be interrupted.

Finally, it's worth noting that the communication problem with Colibrick can be avoided by connecting the USB hub to the USB C connector on the PC.