General
CPU | NVIDIA Carmel ARMv8.2 @ 2.26GHz |
Cores | 8 |
RAM | 32GB |
USB2.0 Interfaces | 4 |
USB3.1 Interfaces | 3 |
Ethernet | 10/100/1000 MBit |
PCIe | 1x8 + 1x4 + 1x2 + 2x1
Gen 4.0 |
- Note
- The above table describes the specification of the NVIDIA Jetson AGX Xavier Developer Kit.
-
The following tests were conducted on JetPack 4.6.0.
Test Setup
Test setup
Additional Settings
Impact Acquire - System Settings
- Note
- A
Request
in the Impact Acquire API represents a buffer where an image with the current device configuration is captured into. In order to avoid losing images at a high FPS, it's recommended to increase the number of these request buffers (i.e. ' RequestCount'
in ' SystemSettings'
, by default the value is set to 4 for Balluff USB2.0 cameras), so that the device driver can continue capturing image data even if the host application is sometimes slower at processing an image than the camera at transferring one. As a rule of thumb, the number of capture buffers should be configured roughly within the range of FPS/2 and FPS/5. In the following test, the RequestCount
is set to 20 which is roughly FPS/5.
Benchmarks
mvBlueFOX-ML/IGC200wC | 752 x 480 | Mono8 | 93.71 | 33.88 | ~16% |
|
|
- Note
- Camera models of type
BVS CA-UB1*
are recommended. The following problems might be observed when using the camera models of type mvBlueFOX-ML/IGC*
:
- On ARM platforms, there might be several lost frames at the beginning of acquisition start.
- If the device has already been initialized, between acquisition stop and restart, there will be lost frames registered in the statistics, because the image sensor keeps generating image data also after the acquisition stop as long as it has been initialized.