Skip to content
STAGING SERVER
DEVELOPMENT SERVER

pylon Software Suite 25.11 Release Notes#

Release date: 2025-11-17

Binary Compatibility#

  • pylon C++ SDK = 11.2.0
    Applications built with 11.2.x or earlier 11.x.x versions of the pylon C++ SDK are compatible.
  • pylon .NET SDK = 9.0.0
    Applications built with earlier versions of the pylon .NET SDK are incompatible.
  • pylon C SDK = 10.1.0
    Applications built with 10.1.x or earlier 10.x.x versions of the pylon C SDK are compatible.
  • Data Processing = 3.5.2
    Applications built with 3.5.x or earlier 3.x.x versions of the Data Processing are compatible.

New Features / Changes#

vTools: [340058] The Camera vTool now supports GenDC grab results. When a single image-like data component is available, it is passed directly to the Image pin. For image containers with multiple components, the Intensity component is preferred. vTools: [345795] The Mini Script vTool can now handle images and regions, providing access to their metadata and supporting routing from input pins to output pins. vTools: [292218] Introduced significant performance improvements and expanded functionality. Decoding for QR and GS1 Data Matrix codes has been enhanced. The QR Code Reader has been optimized further for speed and efficiency. Additionally, shape-based matching algorithms have been improved, delivering higher processing speed and greater robustness.

Corrections#

GenTL/GigE: [349506] Fixed an issue where files downloaded from a GigE camera via GenICam File Access were saved as 0-byte when their size was not divisible by 4. pylon C++ SDK: [349506] Fixed an issue where files downloaded from a GigE camera via GenICam File Access were saved as 0-byte when their size was not divisible by 4.

Restrictions#

  • pylon C++ SDK: If you download a file from a GigE camera using the GenICam File Access feature and if the file size is not divisible by 4, a file with 0 bytes is currently downloaded. This may cause issues, especially with calibration and configuration files containing user data (e.g., vignetting correction data, shading correction data, 3D data).
  • 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);
  • pylon C++ SDK: The InstantCameraArray classes can acquire images from a maximum of 21 cameras.
  • 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.
  • 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.
  • 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.
  • 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.
  • GenTL/GigE: The GenTL producer for GigE Vision does not support action commands.
  • pylon C SDK: The pylon C API doesn't provide convenient functions to use GenDC and the Basler blaze 3D camera yet.
  • pylon C SDK: For using the GenTL Consumer (e.g., with CoaXPress), additional functionality was added to pylon C to be able to start and stop streaming explicitly. This functionality has not been documented in the pylon C programmer's guide yet. Please refer to the pylon C++ programmer's guide (see chapter "Migrating from Previous Versions - Changes in the IStreamGrabber API") or the pylonC OverlappedGrab programming sample.
  • 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.
  • 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).
  • GenTL: Limited GenTL support for producers with GenTL version 1.4 and below.

Download#

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