Troubleshooting and performance
91
Alvium USB Cameras User Guide V1.1.0
Optimizing performance
Operating systems and bandwidth
Even if your hardware supports high bandwidths, you may encounter corrupted
frames. This is some best practice advice.
Windows and Linux
For smooth data transfer of USB3 Vision cameras, the host computer must be
equipped with a high-performance USB controller.
During free run, Alvium cameras do not automatically adapt the frame rate to the
USB controller's limits. If the data rate is too high for your USB controller, it receives
corrupted frames. The image transfer status in
Vimba Viewer
is signaled as
Running
. However, the corrupted frames are not displayed.
To avoid corrupted frames, adjust the
DeviceLinkThroughputLimit
value.
Consider that
Vimba Viewer
does not gray out values that exceed the supported
bandwidth. Avoid selecting values that result in corrupted frames.
Calculating DeviceLinkTroughputLimit
Values required for
DeviceLinkThroughputLimit
(D) for different fame rates:
RGB8:
D = H × V × 3 x frame rate [Byte/s]
Mono8:
D = H × V × 1 x frame rate [Byte/s]
Example calculation for RGB8:
D = 1944 pixels × 2592 pixels × 3 × 28 fps = 423,263,232 Byte/s
Adding 5% (estimation) for the overhead of the USB3 Vision protocol:
423,263,232 Byte/s × 1.05 = 444,426,393.6 Byte/s
Suitable USB 3.0 accessories
See
https://www.alliedvision.com/en/products/accessories
for suitable USB 3.0
host controller cards and cables or contact your Allied Vision Sales representative.
Numbers in this section
For readability, numbers are shown as
1,000
instead of
1000
. In program code and
in
Vimba Viewer
, values must be entered as
1000
.
i
