コンテンツにスキップ
STAGING SERVER
DEVELOPMENT SERVER

pylon Software Suite 25.06 Release Notes#

Release date: 2025-06-20

Binary Compatibility#

  • pylon C++ SDK = 10.3.0
    Applications built with 10.3.x or earlier 10.x.x versions of the pylon C++ SDK are compatible.

New Features / Changes#

  • vTools: [322976] Added Grid Creator vTool.
  • pylon Viewer: [336981] Improved the usability of 3D cameras.
  • pylon Viewer: [336090] The Recording feature now supports saving sequences of still images in bmp, tif, png, jpeg, and raw formats.
  • pylon Viewer: [326399] You can now save the current image in bmp, tif, png, jpeg, dng, and raw formats.
  • pylon Viewer: [329111] The performance of the Histogram and Line Profile features has been improved.
  • vTools: [335669, 335660, 337193, 334690] Added the Histogram Extractor vTool. This tool extracts a histogram from an image, placing it into the mono channel for monochrome images or into the appropriate color channel for color images.
  • vTools: [321505] Added the Array Element Selector vTool. The Array Element Selector vTool allows you to select a single element of an array and output the data at the index position that you have specified.

Corrections#

  • pylon Viewer: [338283] Fixed an issue with scaling in the Firmware Updater.
  • pylon IP Configurator: [337978] Fixed an issue where the font family wasn't set properly.
  • pylon C++ SDK: [329360] Fixed an issue with boost V cameras where opening the InstantCamera object could fail if the TriggerSelector was set to a new value.
  • Doc: [313977] The sample for creating a device object for a GigE camera with a specific IP address now includes the previously missing device class.
  • vTools: [337959] Improved the OPC UA client vTool by eliminating console messages.
  • vTools: [334601] Moved the OPC UA Client vTool to the new Interface group.
  • vTools: [335779] Fixed an issue where server addresses weren't saved if the recipe didn't have any input pins. Now, the server address will always be saved.
  • PylonVToolCreatorRuntime: [336519] Fixed an issue where region metadata could not be set properly.
  • vTools: [338632] Added missing documentation of the PaddingValue parameter of the Image Stitcher vTool.
  • vTools: [338143] Ensured thread safety during the loading and saving of settings.

Restrictions#

  • Workbench: Using multiple pin data views actively displaying data in the Workbench may cause an increase of the CPU load and degradation of the overall performance. Basler recommends using fewer pin data views whenever possible.
  • Workbench: The Statistics feature of the Workbench measures the execution times of vTools. The times measured in the Statistics feature may vary depending on the configuration of your system and the overall CPU load. This is so, because CPUs may run with different frequencies depending on the current load (e.g., due to dynamic frequency scaling).
  • pylon Viewer: A new image throttle has been implemented in the pylon Viewer to improve overall stability and performance. This introduces a new restriction which affects the video recording feature of the pylon Viewer. Allowing only 250 images per second and camera in the imaging pipeline limits the ability to record every frame when exceeding this limit.
  • pylon Viewer: The Color Calibrator does not support all Basler color cameras. Due to a different camera feature set, Basler dart and boost V cameras are not supported.
  • pylon Viewer: Under certain circumstances, e.g., a very slow or busy computer, the Color Calibrator may not work if the camera has already been opened in the pylon Viewer. To prevent this, close the camera before using the Color Calibrator.
  • pylon Viewer: On computers with an Intel HD graphics card, it may be necessary to update the graphics driver to the current version.
  • pylon Viewer: Images grabbed by Stereo ace 2 cameras can't be displayed yet.
  • pylon C++ SDK: When building samples using CMake, you may run into a path length limitation of the operating system. You may get build errors stating the paths exceed the maximum path length of 260 characters. This may happen if the absolute path of your CMake build directory exceeds 80 characters. The build directory is the current working directory or the directory specified by the '-B' option when you call cmake. If you experience this error, use a build directory with a shorter path not exceeding 80 characters, i.e., directly in your user profile C:\Users\\Samples. You can enable long paths on Windows 10, Version 1607, and later. See the Microsoft documentation for more information.
  • pylon C++ SDK: Using Visual Studio 2017, you may get the MSB4211 warning. To remove the warning, specify the version of the Windows SDK in the Release and Debug project properties (Configuration Properties -> General -> Windows SDK Version).
  • pylon C++ SDK: Some ace 2 cameras may use a Boolean parameter instead of the usual enumeration for event notifications. The following code snippets can be used to work around this issue. For C++ you can use: CBooleanParameter(camera.GetNodeMap(), "EventNotification").TrySetValue(true); in addition to: camera.EventNotification.TrySetValue(EventNotification_On);
  • GigE: In case the error message "Failed to allocate resources." has been reported, Basler recommends using the pylon GigE Configurator tool to optimize the IP configuration of NICs and cameras.
  • GigE: Multiple IP configurations on a single network interface are not fully supported by the IP Configurator tool.
  • pylon C++ SDK: The InstantCameraArray classes can acquire images from a maximum of 21 cameras.
  • GigE: For optimum use of Basler's ace 2 5GigE and 1GigE cameras, Basler recommends using dual-channel DDR4-3600 RAM or better. Using slower RAM may cause buffer underruns and image loss. In addition, Basler recommends using the pylon GigE Configurator tool to optimize the complete setup.
  • GenTL: Limited GenTL support for producers with GenTL version 1.4 and below.
  • USB: The Power Management used by the Intel USB host must be turned off since Basler U3V devices may get desynchronized. If this is the case, the Basler U3V devices may be not available after booting the system in some cases. Disable LPM packages on the USB3 bus with the following steps:
    1. Enable advanced settings by executing the following command:
      powercfg -attributes 2a737441-1930-4402-8d77-b2bebba308a3 d4e98f31-5ffe- 4ce1-be31-1b38b384c009 -ATTRIB_HIDE
    2. Change the LPM settings in the power options.
      1. Open the Power Options in the control panel.
      2. Click "Change plan settings" for the selected power plan.
      3. Click "Change advanced power settings".
      4. In the "Power Options" dialog on the "Advanced settings" tab, select "USB settings".
      5. Set "USB 3 Link Power Management" to "Off".
  • MP4: MP4 video recording requires the pylon Supplementary Package for MPEG-4 to be installed in order to work. The pylon Supplementary Package for MPEG-4 is available for download on the Basler website.
  • MP4: Recording of video files with cameras with resolutions of 20 MP or higher may fail, if the Quality parameter is set to 80 % or more. As a workaround, set the Quality parameter to a lower value.
  • MP4: The Recording feature doesn't support the Compression Beyond feature in ace 2 Pro cameras. When recording is started and the Compression Beyond feature is enabled, the pylon Viewer first disables the Compression Beyond feature in the camera and then starts recording.
  • 3D: Using Basler blaze 3D cameras requires the pylon Supplementary Package for blaze to be installed. The pylon Supplementary Package for blaze is available for download on the Basler website.
  • 3D: Using Stereo ace 3D cameras requires the pylon Supplementary Package for Stereo ace to be installed. The pylon Supplementary Package for Stereo ace is available for download on the Basler website.
  • vTools: Alternative data types aren't available anymore if a connection of a certain data type has been saved in a recipe. When reloading the recipe and deleting the original connection to an input pin, the input pin only offers the data type of the original connection.
  • GenTL/GigE: The GenTL producer for GigE Vision does not support action commands.
  • GenTL/GigE: The GenTL producer for GigE Vision does not support multicast configurations.
  • pylon .NET SDK: Updating to this version of the .NET API requires you to update your .NET project files to reference the new assembly. This is required due to the VB2015 compatibility fix (interface class Basler.Pylon.IParameterListEnum was changed to ref class Basler.Pylon.ParameterListEnum).
  • pylon .NET SDK: If native debugging is enabled for your .NET project and if your project is referencing pylon assemblies, the application may crash when running it under the Visual Studio 2012 or Visual Studio 2013 debugger. To avoid this issue, enable the Managed Compatibility mode in the Visual Studio Debugger options.
  • CXP IC: For linescan applets, ranges of line period and line exposure are not handled properly. The maximum values might be less than expected
  • GenTL/CXP: The compilation is done now with Visual Studio 2022, which makes the installation of the Visual Studio 2022 redistributables necessary in order to load the libraries.
  • GenTL/CXP: The actual buffer size limit is 2 Gbit, which consequently imposes a restriction on the permissible values for Width and Height in the producer and result in that the maximum size of image is 2GB.
  • GenTL/CXP: The fps limit is from 50.000 fps to 90.000 depending on the number of buffers and image size. For more detailed approximate values, 10 buffers and a minimal image size of 48x1 give a limit of approximately 50,000 FPS, 50 buffers and a minimal image size of 48x1, a limit of about 90,000 FPS and 50 buffers and an image size of 8192x1 a limit of approximately 50,000 FPS.
  • GenTL/CXP: 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.
  • GenTL/CXP: 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.
  • GenTL/CXP: If a version of the Basler Framegrabber SDK is installed on your computer, you may experience incompatibility issues when using CoaXPress cameras and interface cards. Therefore, Basler advises against installing pylon in parallel to the Framegrabber SDK.
  • GenTL/CXP: 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. To work with the driver, secure boot can be disabled. Alternatively, the driver can be self-signed as described in this Ubuntu blog entry: https://ubuntu.com/blog/how-to-sign-things-for- secure-boot
  • GenTL/CXP: When allocating buffers used for grabbing, the buffer address must be aligned to 8-byte increments. This is automatically the case, if you use heap memory.
  • GenTL/CXP: Grabbing with very high frame rates above 50000 fps using the Basler CXP-12 Interface Card 1C is not supported.
  • GenTL/CXP: In rare cases, the camera is not found after booting the computer. Power-cycle the camera to resolve this.
  • GenTL/CXP: When the DeviceUserID of a camera is changed, a restart of the GenTL Producer is required for the change to be reflected via the GenTL API. When using a GUI to interact with the camera via GenTL (i.e., the pylon Viewer), a restart of that application is required for the change to become visible.
  • GenTL/CXP: During an applet change, the cameras attached to an interface card are still displayed in the devices list even though they are not accessible anymore. An attempt to open a camera in this state leads to an error message.
  • GenTL/CXP: The GenTL BUFFER_INFO_FRAME_ID, which can be queried via DSGetBufferInfo, doesn't contain the source tag from the CXP image header. Instead, it contains a counter for all frames that have been delivered to the computer.
  • GenTL/CXP: If images are lost on the interface card due to a buffer overflow, e.g., when the user application doesn't (re)queue buffers fast enough to deliver the images, the images lost are indicated by the next delivered buffer. The lost images are marked as INCOMPLETE, their file size will be 0, and the custom error code BUFFER_INFO_BASLER_XAPI_ERROR_CODE is set to 42. Additionally, one lost frame is added to the stream info. Note that exactly one lost frame is added regardless of how many frames were lost due to the overflow.
  • GenTL/CXP: The Basler CXP-12 Interface Card 1C/2C/4C and imaWorx CXP-12 Quad acquisition cards require a host interface with PCIe Gen 3 x8 (Direct Memory Access) or better. Using slower host interfaces may reduce the camera's acquisition frame rate and cause image loss.

Download#

You can download this version of the pylon Software Suite here.