跳转到内容

pylon Software Suite 8.1.0 Release Notes#

Release date: 2024-03-14

Binary Compatibility#

  • Data Processing = 3.0.1
    Applications built with 3.0.x or earlier 3.x.x versions of the Data Processing are compatible.
  • pylon C SDK = 10.0.0
    Applications built with earlier versions of the pylon C SDK are incompatible.
  • pylon C++ SDK = 10.2.0
    Applications built with earlier versions of the pylon C++ SDK are incompatible.

New Features / Changes#

====================== - pylon C++ SDK: [322697] Fixed a problem when running EltAppender with .NET applications. - pylon C++ SDK: [323481] The CBaslerUniversalInstantCamera class has been updated. - pylon C++ SDK: [324026] Added version suffix to GenICam libraries. - pylon C++ SDK: [324026] Added back channel server to allow runtime configuration of the Basler logging system (EltAppender / pylon Event Logger). - pylon C++ SDK: [316909] PylonGigEConfigurator: Fixed Windows auto-opt function. It now sets optimization values again. - pylon C++ SDK: [321363] Improved the error handling for decompression and the documentation. - pylon .NET SDK: [323481] Parameter lists have been updated. - CXP IC: [318735] Changed biColor interpolation coefficients to -0.5 1 -05 to follow camera version of interpolation. - CXP IC: [318735] Removed biColor modes GBGR and GRGB. - CXP IC: [318735] Extended CameraStreamStatus event information. - GenTL: [323605] The DeviceInfo object of a GEV/blaze GenTL enumeration now holds the correct values for the entries of IP address, MAC address, subnet mask, default gateway, and device manufacturer info. - GenTL: [326394] Chunk data aren't fetched anymore if no chunks are available. - GenTL/CXP: [320807,323583,320739,320740,320738,323587] Multiple changes regarding logging. - Top level log category inside the GenTL producer is now called FgSdk instead of FgSdk. - For every received frame, additional information (time stamp, payload size etc.) is logged to the log category FgSdk.GenTL.Acq. This category is by default set to log level FATAL because it has a severe impact on the performance for higher frame rates. Setting the log level for this category to NOTICE or higher enables the logging. - Another log category, FgSdk.fglib.Acq was introduced for a similar purpose, but only when using the Frame Grabber SDK directly. For pylon applications, this should always be set to FATAL. - To get information about frame grabber (resp. applet) events, a new log category FgSdk.fglib.Events was introduced. Because events can also occur in a very high frequency, every frame grabber event is logged to the category FgSdk.fglib.Events.<EventName> where <EventName> is the actual name of the event. Use these categories for a fine grained logging configuration. Please note that frame grabber events must be enabled by your application to be generated and logged. - Additional log messages for detecting problems with a CXP link connection. - vTools: Upgraded CodeMeter to 8.20a. - vTools: [320336] Added Anomaly Detection vTool. - vTools: [316670] Added Batching feature to the Classification vTool. Batching allows you to process multiple regions of interest (ROI) simultaneously which increases processing speed. - vTools: [298566] Added Multiplexer vTool. - vTools: [307044] Added the OPC UA Client vTool. - Data Processing: [275911] Improved thread pool implementation to favor older graph updates and added thread priority. - Data Processing: [319406] Added information about CBuildersRecipe and how to use recipe compression via the pylon Data Processing C++ API. - Data Processing: [319578] Updated sample finder to be compatible with future Basler internal GenICam versions. - Data Processing: [317568] Updated sample finders to be compatible with future pylon versions. - Data Processing: [310128] Added the SaveAs method to the CBuildersRecipe class to allow the user to specify the recipe file format. - pylon Event Logger: [323553] Changed log4j.category.basler to log4j.category.FgSdk. - pylon Event Logger: [321118] Added launch profiles to configure the launched or running logging application. - pylon Event Logger: [320249] Improved the handling of adding new log messages in the message view. There used to be a lag when updating the message view which meant that several new messages were added at the same time. Now, new messages are added one by one, creating a smoother experience. - pylon Event Logger: [320856] Improved status names, tooltips, and other user interface text. - pylon Event Logger: [320418] Fixed an issue with the performance of display filters. - pylon Event Logger: [320312] Display and highlight filter settings can now be imported and exported. - pylon Event Logger: [319932] Maximum number of messages in view can now be configured. - pylon Event Logger: [320428] Changed the log levels enabled by default in the activity view to WARN, ERROR, AND UNKNOWN. - pylon Event Logger: [319443] Added the Scroll to End button in the navigation view. - pylon Event Logger: [319447] Improved the scrolling behavior in the message view. - pylon Event Logger: [319890] Added the Not Equals and Not Contains operators to the Display/Highlight Filter dialogs. - pylon Event Logger: [319441] If multiple properties files are detected, a warning is now displayed. - pylon Event Logger: [319892] Added the Export Graph command in the Capture menu. - pylon Event Logger: [319928] Scrolling or using other navigation features in the message view, disables the Autoscroll to End option. - pylon Event Logger: [319889] Added the Copy All command in the context menu of the message view. - pylon Event Logger: [319439] Updated icons in the navigation view.

Corrections#

  • GigE: [329078] Fixed an issue with the FrameRetention parameter not functioning as intended. If image transport exceeds 300 ms, you need to increase the FrameRetention parameter value. Otherwise, the image grab will fail, reporting the buffer as incomplete.
  • GigE: [329076] Fixed an issue where resend requests were generated incorrectly. This is included in pylon GEV Driver version 5.5.0.1290.
  • GigE: [316669] BlockID64 data is no longer cast to BlockID16 data by the driver.
  • pylon Viewer: [322017] Fixed CTRL+C shortcut always copying the histogram / line profile data when those panes are present and docked.
  • pylon Viewer: [321363] Fixed high CPU load that occurred when grabbing dark images.
  • pylon Viewer: [305905] Updated the icons of the Firmware Updater.
  • pylon Viewer: [319360] Fixed a bug where you couldn't move the line of the Line Profile feature when the Sharpness Indicator was enabled.
  • vTools: [324010,323143,323161] Updated some parameter names, tooltips, and descriptions in the nodemaps of PatternMatching vTools.
  • vTools: [314793] Fix handling of invalid source in calibration basic.
  • vTools: [314945] In the Image Morphology Starter vTool, the Width and Height parameters for the Median filter are now linked.
  • pylon C++ SDK: [316618] Fixed a potential deadlock in the EltAppender when closing pylon.
  • pylon C++ SDK: [321363] Provided a fix to avoid getting compression information from an already decompressed grab payload.
  • DirectShow: [320992] CoaXPress cameras are now supported by the DirectShow driver.
  • Twain: [320992] CoaXPress cameras are now supported by the Twain driver.
  • CXP IC: [318735] Corrected interpolation of right edge pixel for biColor interpolation.
  • CXP IC: [318735] corrected MCF file saving of trigger parameters.
  • pylon Event Logger: [329848] Console applications are now visible when launched via the pylon Event Logger.
  • pylon Event Logger: [321046] Fixed an issue where the properties file wasn't created when starting the pylon Event Logger.
  • pylon Event Logger: [321028] Fixed some path handling issues.
  • pylon Event Logger: [321207] The Settings dialog is now unavailable while the pylon Event Logger is capturing messages.
  • pylon Event Logger: [320195] Disabled searching in the navigation view when the status of the pylon Event Logger is Capturing or Cleared.
  • pylon Event Logger: [319933] Disabled the Start and Launch Logging Source option until the active process has finished or produced an error.
  • pylon Event Logger: [319120] Fixed an issue that caused an error to be displayed in the notification view when creating a filter group from an active filter.
  • pylon Event Logger: [319516] Session directory will now be deleted when a session is cleared.
  • pylon Event Logger: [319446] When closing the pylon Event Logger while there is unsaved data in the message view, a warning is displayed allowing the user to save the data.
  • pylon Event Logger: [315944] Fixed the text color of notifications in dark mode.
  • pylon Event Logger: [315370] Fixed the default directory for open and save dialogs. Now, the user's root directory is used.

Restrictions#

  • vTools: If you downgrade CodeMeter from 8.20a to 7.4x, the CmActLicense container will no longer work. In this case, you will need to delete the container and create a new one.
  • 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).
  • 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 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.
  • 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