Known Issues Framegrabber SDK 5.11.2
This section provides information about known issues for the Basler Framegrabber SDK version 5.11.2.
All Components
| Summary | Storing and Loading MCF-Files Results in Double Values Rounded to a Whole Number |
| Description | When loading a configuration from an MCF-file, double values with comma delimiter might be rounded to the nearest whole number. This is caused by the current locale setting of the Linux operating system. Rounding doesn't occur if the locale defines a dot as delimiter. |
| Affected OS | Linux |
| Workaround | Set an appropriate locale, e.g., LC_NUMERIC="C" ./<applicationName>, before you start microDisplay X or microDiagnostics. |
| Ticket ID | 265213 |
| Summary | Camera Doesn't Deliver Correct Images |
| Description | If a camera with multiple links doesn't comply with the CXP standard regarding the distribution of the image data over the links, the camera won't transmit images correctly. This issue was observed with a JAI SP-12000C-CXP4 camera. |
| Affected OS | Windows and Linux |
| Workaround | No workaround is available. |
| Ticket ID | TFS 211645 |
| Summary | Linux Drivers Can't Be Signed with a Trusted Basler Certificate |
| Description | Using secure boot (UEFI mode) with Linux requires a driver that is signed with a trusted certificate. Since the driver is provided as source code, there is no way to sign it with a trusted Basler certificate. |
| Affected OS | Linux |
| Workaround | To work with the driver, secure boot can be disabled. Alternatively, you can sign the driver as described in this Ubuntu blog entry. |
| Ticket ID | – |
Framegrabber API
| Summary | Displaying Images with High Frame Rates May Lead to Input Lag |
| Description | When using the display_lib Framegrabber API library (only available on Windows), displaying images with high frame rates (about 10.000 frames per second) may lead to input lag (e.g., keyboard and mouse lag) on the host computer. |
| Affected OS | Windows |
| Workaround | No workaround is available. |
| Ticket ID | – |
CLComDriver
| Summary | There Are More Drivers Installed Than CLSer Ports in the System |
| Description | Sometimes when using Install COM driver(s) for all Ports, more drivers are installed than there are CLSer ports in the system. |
| Affected OS | Windows |
| Workaround | Select the additional port(s) and remove them using the command Remove selected COM driver. |
| Ticket ID | – |
| Summary | With Basler Runtime 5.9.0 or Earlier, the Board Type Isn't Recognized |
| Description | With Basler Runtime 5.9.0 or earlier, the board type isn't recognized and ports are only displayed using the CLSer identifier. |
| Affected OS | Windows |
| Workaround | Update your Basler Runtime/Framegrabber SDK version to 5.10 or higher. |
| Ticket ID | – |
| Summary | Port Settings in the Device Manager Don't Reflect Actual Settings |
| Description | Port settings in the device manager don't reflect actual settings and changes aren't considered. |
| Affected OS | Windows |
| Workaround | Use the Windows COM Port API to change port settings. |
| Ticket ID | – |
GenTL Producer
| Summary | Camera Parameters Changed after Image Acquisition Start Aren't Reflected in the Frame Grabber |
| Description | When camera parameters are changed during image acquisition, the change isn't reflected in the frame grabber. This is because the GenTL Producer retrieves the relevant parameters (width, height, image format, etc.) before starting the acquisition and synchronizes these with the frame grabber. |
| Affected OS | Windows and Linux |
| Workaround | No workaround is available. |
| Ticket ID | TFS 195482 and 225591 |
| Summary | The GenTL Device ID Changes When the Applet Is Changed |
| Description | According to the GenTL standard, the device ID should remain constant between two sessions. However, the GenTL device ID changes when the applet is changed. Therefore, the device ID can only be reused if the applet has the same name as the applet with which the device ID was generated. |
| Affected OS | Windows and Linux |
| Workaround | No workaround is available. |
| Ticket ID | – |
microDisplayX
| Summary | On a Clean Linux Installation, microDisplayX Doesn't Start |
| Description | On a clean Linux installation, microDisplayX doesn't start. The reason for this issue is that on a clean Linux installation, the xcb QT platform plugin is missing. |
| Affected OS | Linux |
| Workaround | Install the missing plugin with the sudo apt install libxcb-xinerama0 command. |
| Ticket ID | TFS 259941 |
| Summary | On Linux, microDisplayX Might Crash When It Is Being Closed |
| Description | On Linux, microDisplayX might crash when it is being closed. This has no further consequences and can be ignored. |
| Affected OS | Linux |
| Workaround | No workaround is available. |
| Ticket ID | TFS 211811 |