Known Issues Runtime Release Version 5.7
- Under Windows 8 or higher, the option Fast Startup should be turned off. (Option Fast Startup is also known as hybrid boot or hybrid shutdown.) See section How to Turn off Window's Fast Startup.
- Disabling energy safe mode for PCI Express: For safely running Basler frame grabber applications it is strongly recommended to disable energy safe mode for PCI Express. Concerns Windows XP 32bit, Windows XP 64bit, Windows Vista 32bit, Windows Vista 64bit, Windows 7 32bit and Windows 7 64bit, Windows 8 32bit and Windows 8 64bit. See How to Disable Save Mode for PCIe.
Only runtime version 5.5 or higher, due to the new possibility to flash multiple partitions on microEnable 5 marathon: Flashing and/or activating an applet on one microEnable 5 frame grabber board will result in the following system behavior if the Siso Generic Service (gs) is used to manage camera connections:
- The Siso Generic Service (gs) is re-started for all boards in the host PC that use the service. Depending on the number of boards installed in the host, this may take some time.
- On the frame grabber that is flashed/on which a new applet is activated, the connection to the camera(s) is reset. The camera(s) need to be re-discovered.
- During restart of the Siso Generic Service (gs) , all GUI applications (microDisplay, microDiagnostics, GenICam Explorer) will appear as "Not Responding".
Only one process can carry out Fg_Init at a time. If the function
Fg_Initis called in multiple threads (for different frame grabber boards) simultaneously, and if the simultaneous calls result in simultaneous live reconfiguration of multiple frame grabber boards: Only one frame grabber board is reconfigured successfully. For all other boards, the error message
FG_RECONFIGURATION_DISABLED is returned. However, despite this error message: Frame grabber live reconfiguration is still enabled. Please simply re-start the reconfiguration of the other frame grabber boards one after the other.
In very rare cases, this behavior is also visible when working with microDiagnostics: If you
- flash multiple boards simultaneously and, by chance,
- flashing the active partitions is completed simultaneously on multiple boards,
reconfiguration of these frame grabber boards starts simultaneously. In this case, you will get the same error message. Please simply re-start the reconfiguration of the frame grabber boards one after the other.
- Live Configuration of microEnable 5 (marathon, ironman, and LightBridge) is not supported by all motherboards.
- In the two LAGx2 applets
- Acq_DualGEx2AreaGray12 and
- The Camera Simulator Module in applet Acq_SingleCXP6x4AreaBayer is malfunctioning.
- Firmware flashing on microEnable 5: At the end of the flashing process on mE5 frame grabbers, Runtime 5.4 activates a firmware write protection on the frame grabber. Attention: Older versions of the runtime software are not able to de-activate the firmware write protection during the flashing process. Thus, a frame grabber with activated firmware write protection cannot be re-flashed by an older runtime software (prior to version 5.4.). In this case, microDiagnostics displayes the error message „Readback and bitstream don't match.“. For resolving the situation, you have two options. Either
- flash the frame grabber again, this time using the latest version of the runtime, or
- de-activate the firmware write protection manually, using an additional tool. If you prefer this option, please contact Basler directly.
- The revised implementation of the DMA900 technology requires an activation of the "Turbo DMA mode" to achieve a maximum DMA transfer performance, when running on PC setups with maximum PCIe payload size of 128 Bytes. In case of doubts run microDiagnostics performance tests in order to get the system specific performance and adjust the Turbo DMA mode setting, accordingly.
- Frame grabber products, running Advanced AcquisitionApplets: During start-up phase spikes can occur at the trigger outputs.
- If the grabber is configured to check for DVAL camera signal (which is the default) but the camera does not send DVAL for the whole frame one line of data is still returned. The FullArea and FullLine applets correctly return empty frames (frames of length 0).
- When very short frames (at most 128 bytes) are transferred on an PCIe x4 frame grabber and the end of the transfer is 4, 8, or 12 bytes before any 128 byte boundary, an additional empty frame is marked as transferred. The frame data of the original frame remains intact. VA processing applets, e.g., applets using the blob operators, are very likely to show this behavior. If you see empty frames, the following example code might help you detect if they have been created because of the behavior described above.
int isDmaFrameSkip(Fg_Struct *fg, dma_mem *membuf, int dmaport, int picnum)
Fg_getParameterEx(fg, FG_TRANSFER_LEN, &len, dmaport, membuf, picnum);
if (len != 0) return 0;
Fg_getParameterEx(fg, FG_TRANSFER_LEN, &len, dmaport, membuf, picnum - 1);
if (len > 128) return 0;
uintptr_t bufaddr = (uintptr_t)Fg_getImagePtrEx(fg, picnum - 1, dmaport, membuf);
if (((bufaddr + len) % 128) < 116) return 0;
- IMPORTANT ISSUE concerning operating systems Microsoft Windows 8 32bit/64bit, Microsoft Windows 7 32bit/64bit, Microsoft Windows Vista 32bit/64bit and Microsoft Windows XP 64bit/32bit:
- Runtime usage stand-alone: No known issues
- Runtime usage with VisualApplets: It is recommended to choose the user folder (or any other folder with full access rights) as installation folder. At least the folder "hardware applets" needs to have full access rights.
- When using the Applets for GigE Vision Link Aggregation: The DMA transfer of a certain frame terminates at the next received frame from the camera or when an adjustable timeout occurs. The effect can be seen especially, when the camera acquisition is stopped. To speed up the point of time of transfer, the timeout therefore can be adjusted.
- When using older hardware revisions of microEnable IV VD4-CL boards (revisions < 2.1 ) in combination with PixelPlant200e errors might occur, even when using the newer firmware. Please contact our support team in such cases.
- Board detection problems, microEnable IV VD1-CL only: Due to a defect within the Phy chip which is built-in into microEnable IV VD1-CL, in some computer systems problems with the board dectection of microEnable IV VD1-CL may occur. Solution: Deactivation of the Power Save Modi in the Bios of the computer.
- Sporadically occurring reporting error, all microEnable IV frame grabbers with Camera Link Full configuration applets: SDK reports an image size of 0 byte if the image size is = 4 Byte.
microEnable 5 ironman: Frame grabber is not recognized by microDiagnostics (and Windows Device Manager) when a defective applet has been flashed onto the frame
grabber, or when the flashing process has been interrupted. To be fixed by Silicon Software
Support. Affected microEnable 5 ironman frame grabbers: mE5 AD8-PoCL, mE5 VD8-PoCL, mE5 AQ8-CXP6D, mE5VQ8-CXP6D, mE5AQ8-CXP6B, mE5AQ8-CXP6B. This issue has been addressed in the design of microEnable 5 marathon frame grabbers.
- Camera Simulator: The usage of an applet’s internal Camera Simulator may show a lower bandwidth than expected. This does mean that certain overflow conditions may occur when the current simulator is used. When a real camera is used, this behavior doesn't show. The issue is only related to the internal Camera Simulator. It will be solved in the next service release.
- LightBridge Pre-Production and marathon boards: Flashing may result in the failure message "Readback and bitstream don't match". This happens with the probability of around 1 per 40.000 flashing times. When this message occurs, simply flashing the board again solves the problem. The same underlying problem may occur (with a probability of 1 per 1.6 billion times) when activating a partition in microDiagnostics (or using Fg_Init). If partition activation in microDiagnostics normally works fine and you get a message "Please powercycle the computer" after activating a partition, please try again. When the problem occurs when you are activating via Fg_Init, the function returns NULL and function Fg_getLastErrorNumber returns FG_DEVICE_IO_ERROR. Please try again.
- Line applets for mE5 marathon ACL, mE5 marathon VCL, and LightBridge VCL: The software trigger cannot be selected via parameter FG_IMGTRIGGERINSRC. (6483)
- Line trigger module in Line Scan Acquisition Applets for marathon ACL / marathon VCL / LightBridge VCL: The applets show unwanted dependencies between parameters FG_LINETRIGGERDELAY, FG_LINETRIGGERPERIODE, and FG_LINEEXPOSURE. (6567)
- Area trigger module in Area Scan Acquisition Applets for marathon ACL / marathon VCL / LightBridge VCL: Parameters FG_TRIGGER_PULSEFORMGEN0_DELAY to FG_TRIGGER_PULSEFORMGEN3_DELAY do sometimes not accept new values. The actual value range for these parameters is smaller than the stated range of [0, 3.4e+07]. The according slider in microDisplay doesn't work correctly. Workaround for parameter configuration: If you re-load the applet in microDisplay (menu File-> Load Applet), parameters FG_TRIGGER_PULSEFORMGEN0_DELAY to FG_TRIGGER_PULSEFORMGEN3_DELAY are configurable again. (6568)
- Area trigger module in Area Scan Acquisition Applets for marathon ACL / marathon VCL / LightBridge VCL: The actual value range for parameter FG_TRIGGERFRAMESPERSECOND is smaller than the stated range of [0.0291038,1.25e+07].
Tap geometry mode 5X2 in marathon and LightBridge Camera Link applets: Tap Geometry mode 5X2 might not work correct for some sensor widths. Requirements 1020, 4090, 8190, 16380 work as expected. (7217)
- When using the SDK library display_lib under Windows, to display images with high frame rates (about 10.000 frames per second) may lead to slow reaction times to user input (keyboard and mouse) of the host PC.
- Some CXP cameras are not fully supported by the Basler runtime discovery (for example Adimec Q-12A180 series or Miktrotron MC408X series). Some camera models will be connected using a single link only and cannot be configured to use more than one link. (7974) Under certain rare circumstances the discovery fails to detect some camera models. (7257)
- The current Basler driver for Linux does not work with some Linux distributions (for example Debian 9). On host PCs using such distributions, boards plugged into the host will be detected by the driver, but cannot be accessed by the Basler runtime software and user programs. To work around this issue, try booting the Linux operating system using the boot option iomem=relaxed, or recompile the kernel with configuration CONFIG_IO_STRICT_DEVMEM set to NO. (7026)
- Using secure boot (UEFI mode) with Linux requires driver signing. This is currently not supported by the Basler driver out of the box. The user can self-sign the driver by creating their own signature and registering the signature with the UEFI subsystem.
- Update check (update feature implemented since runtime release RT 5.6) results in error message "Unknown network error":
- Under Windows: To use the new feature, during runtime installation you need to agree that SSL files are downloaded automatically for update checks. If you get the message when trying to look for newer runtime versions, re-install the runtime and consent to SSL file download by clicking the according disclaimer.
- Under Linux: To use the update feature, make sure you install OpenSSL on your Linux System. Otherwise, you will receive the above message.
- Applet Acq_SingleFullLineBayer_RB_GG on microEnable 5 ironman AD8-PoCL and microEnable 5 ironman VD8-PoCL frame grabbers: Colours red and blue are swapped in double sampling mode. Until the fix of this issue (applet set version 2.6), you will need to correct the Bayer pattern accordingly.
- If a driver version older than 4.4.0 is used on Windows, reconfiguration of a board may be reported as failed by the runtime despite having been performed correctly. Loading the same applet a second time will work.
- microEnable 5 ironman AQ8-CXP6D, applet set version 2.8 or higher/ microEnable 5 ironman VQ8-CXP6D, applet set version 2.7 or higher: Use either only new applets or only legacy applets on one host. Don't run new acquisition applets AND legacy acquisition applets at the same time on boards that are plugged into the same host.
- marathon ACL, marathon VCL, marathon VCLx, LightBridge 2 ACL, LightBridge 2 VCL: Only in Camera Link Base mode and only on port B: The CC2 and CC4 signals are inverted, so that "1" on the corresponding port of CameraControl corresponds to a "0" at the output and vice versa. In Medium or Full mode on port B, and on port A in all three modes (Base, Medium, and Full), all CC signals work correctly.