General
CPU | ARM Cortex®-A53 @ 1.6GHz |
Cores | 4 |
RAM | 1 GB |
USB2.0 Interfaces | 2 |
USB3.0 Interfaces | None |
Ethernet | 1000 MBit |
PCIe | 1 x 1 Lane
Gen 2.0 |
The carrier-board used in this test: MBa8Mx from TQ-Systems GmbH
- Note
- If you are looking for more information and guidance about installing Impact Acquire packages via the Yocto Project, please choose an API-manual suited for your programming language and then go to chapter "Installation From Private Setup Routines → Embedded Linux → Yocto Project". All API-manuals can be found under https://www.balluff.com/en-de/online-manuals-mv.
Test Setup
Test setup - Note
- The i.MX8M Mini doesn't have a USB3.0 host controller. USB3 Vision™ devices can therefore operate with USB2.0 speed only.
Benchmarks
The following tests have been performed using different de-Bayering scenarios to achieve the max. FPS while maintaining 0 lost images. The CPU load during the acquisition is also documented below.
Scenarios that have been tested are listed as follows:
- When de-Bayering is carried out on the camera: The camera delivers RGB8 image data to the host system. This setting results in a lower CPU load but a lower frame rate.
- When de-Bayering is carried out on the host system: The camera delivers Bayer8 image data to the host system. The Bayer8 image data then get de-Bayered to RGB8 format on the host system. This setting results in a higher frame rate but a higher CPU load as well.
- When no de-Bayering is performed: The camera delivers Bayer8 image data to the host system. No de-Bayering is performed. This settings results in a lower CPU load and a higher frame rate. The behavior is identical to monochrome cameras.
mvBlueFOX3-2024C | 1936 x 1216 | RGB8 (on camera) → RGB8 (on host) | 5 | 35.3 | ~2.8% |
mvBlueFOX3-2024C | 1936 x 1216 | BayerRG8 (on camera) → RGB8 (on host) | 15.2 | 35.7 | ~25% |
mvBlueFOX3-2024C | 1936 x 1216 | BayerRG8 (on camera) → BayerRG8/Raw (on host) | 15.2 | 35.7 | ~3.7% |