Known Issues Framegrabber SDK 5.10.0
This section provides information about known issues for the Basler Runtime version 5.10.0.
All Components
| Summary | mE5 Frame Grabbers Have Boot Partition Set to Partition 0 and Show Wrong Serial Number |
| Description | After booting, microEnable 5 frame grabbers always show partition 0 as boot partition even if another partition was defined as boot partition before booting and the boot partition can't be changed. In addition, the serial number isn't displayed correctly. |
| Affected OS | Windows |
| Workaround | Turn off the Fast Start-Up Feature under Windows. |
| Ticket ID | TFS 272272 |
| Summary | mE5 CXP Frame Grabbers Only Discover Cameras Connected in Correct Link Order |
| Description | microEnable 5 CXP frame grabbers only discover cameras, if they are connected in the correct link order: camera port 0 connected to frame grabber port 0, camera port 1 connected to frame grabber port 1 etc. If the cameras are connected in a different order, they are not discovered by the frame grabber. |
| Affected OS | Windows and Linux |
| Workaround | Connect the cameras in the correct link order with the frame grabber. |
| Ticket ID | TFS 259300 |
| Summary | For Windows 32-Bit Installations, the PATH Environment Variable Is Not Set Automatically |
| Description | If you install the Framegrabber SDK for a Windows 32-bit, the he windows installer does not set the win32 bin folder in the PATH environment variable. |
| Affected OS | Windows |
| Workaround | Set the win32 bin folder as PATH environment variable manually. |
| Ticket ID | TFS 260409 |
| 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, no correct images are delivered to the computer. 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 Slow Reactions to User Input |
| Description | When using the Framegrabber API library display_lib (only available on Windows), displaying images with high frame rates (about 10.000 frames per second) may lead to slow reactions to user input (e.g. keyboard and mouse) of the host computer. |
| Affected OS | Windows |
| Workaround | No workaround is available. |
| Ticket ID | – |
GenTL Producer
| Summary | Camera Parameters Changed after Image Acquisition Start Are Not 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 so, because the GenTL Producer enquires 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 that was queried with one applet can be used with a different board and a different applet only, if the applet has the same name as the original one 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 QT platform plugin xcb is missing. |
| Affected OS | Linux |
| Workaround | Install the missing plugin with the command sudo apt install libxcb-xinerama0. |
| 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 |