宝视纳Basler-pylon 7.5.0相机软件套装Linux x86 (64位) - tar.gz~pylon-7.5.0.15658_linux-x86_64_setup.tar.gz

石鑫华视觉

宝视纳Basler-pylon 7.5.0相机软件套装Linux x86 (64位) - tar.gz~pylon-7.5.0.15658_linux-x86_64_setup.tar.gz

pylon 7.5.0
2024年3月
7.5.0

pylon相机软件套装包含易于使用的SDK、驱动程序和工具，让您可通过Linux嵌入式PC来操作任意一款Basler相机。pylon采用最新GenICam技术，可无限制使用最新型号的Basler相机并使用相关的硬件功能。Basler pylon支持GigE Vision、USB3 Vision、BCON（基于MIPI）和GenICam GenTL。
pylon SDK简单易用，可帮助您开发完整的机器视觉应用、医疗应用和包括图像采集和图像处理在内的其他应用。仅需几行代码即可设置相机、采集图像，并将其保存。
pylon可为采用受支持的编程语言（如C、C++）开发的所有典型相机应用提供大量丰富的文档资料和示例程序以供参考，可大大促进应用的开发工作。
pylon提供的编程界面独立于正在使用的相机接口，这意味着可以轻松将使用pylon创建的应用程序移植到另一种相机接口技术。
由于pylon不仅支持Linux，还支持Windows和macOS，因此在pylon中为Linux开发的应用程序也可以轻松移植到其他操作系统和架构。
pylon Linux ARM（64位）可提供适用于Debian和相关Linux发行版（如Ubuntu）的Debian安装软件包，另外也可提供适用于其他Linux发行版的tar.gz压缩包。

pylon 7.5.0相机软件套装Linux x86 (64位) - tar.gz
文件名: pylon-7.5.0.15658_linux-x86_64_setup.tar.gz
文件大小: 640620971 字节 (610.94 MB)
修改日期: 2024-10-24 17:35
MD5: 31223a576da03796489a3e4a3da51fcb
SHA1: c9f5b0b5498296b1847fa95f5922d599dc2b952b
SHA256: 69b1cf08f05e0cbf27ff5ac6cfb447b57a375c94bfa1797e2db6fb0719633cb2
CRC32: 5ec0e3a0

Basler官方下载：

游客，如果您要查看本帖隐藏内容请回复

百度网盘下载：
链接：https://pan.baidu.com/s/10xahPVlxzUyewUPZfzMpqw
提取码：

游客，如果您要查看本帖隐藏内容请回复

pylon 7 Camera Software Suite for Linux

RELEASE NOTES

Note: Patch versions of pylon for Linux OS are not released publicly.
      All changes made in patch versions are included in the following minor or major
      version of pylon. The version number scheme for pylon is as follows: x.y.z
      * First digit (x): Major version
      * Second digit (y): Minor version
      * Third digit (z): Patch version


################################################################################

RELEASE DATE:    2024-05-21

VERSION:         7.5.0 (x86_64, aarch64)

################################################################################


BINARY COMPATIBILITY
====================
* pylon C++ SDK = 8.0.0: Applications built with earlier versions of the pylon C++ SDK
                         are incompatible.
* pylon C SDK = 8.0.0: Applications built with earlier versions of the pylon C SDK
                       are incompatible.
* Data Processing SDK = 2.0.0: Applications built with earlier versions of the Data
                           Processing SDK are incompatible


NEW FEATURES / CHANGES
======================
* General: The versioning scheme of some pylon modules, e.g., C++ SDK, has been changed
           and has been decoupled from the pylon release version.
* CXP: Added support for Basler racer 2 L CoaXPress line scan cameras. These cameras
       are for use with the Basler CXP-12 Interface Card 2C/4C or imaWorx CXP-12
       Quad acquisition cards, which require a host interface with PCIe Gen 3x8
      (Direct Memory Access) or better.
* CXP: Added support for Basler ace 2 V CoaXPress cameras. These cameras
       are for use with the Basler CXP-12 Interface Card 1C/2C/4C or imaWorx CXP-12
       Quad acquisition cards, which require a host interface with PCIe Gen 3x8
      (Direct Memory Access) or better.
* GigE: Added support for Basler dart M GigE Vision cameras.
* GenTL/CXP: New line scan applets (version 1.1.1.0) for Basler CXP-12 Interface
             Card 1C/2C/4C and imaWorx CXP-12 Quad have been added.
* GenTL/CXP: The applets for Basler CXP-12 Interface Card 2C/4C and
             imaWorx CXP-12 Quad with static version S1.0 have been updated to
             version 2.3.7.
* GenTL/CXP: The applet for Basler CXP-12 Interface Card 1C with static
             version S1.2 has been updated to version 5.3.7.
* CXP/GenTL: [269821] The CXP GenTL Producer, ProducerCXP.cti, has been updated to
             version 1.0.2.
* GenTL/CXP: [269821] The CXP driver has been updated to version 5.4.0.
* CXP: The CoaXPress trigger packets have been updated to CoaXPress version 2.1.
* CXP: Some missing features for CXP 2.0 have been implemented.
* CXP: [292767] Added an alternative handler for IOCTL_QUEUE_BUFFER that is
       called when a transfer length has been provided.
* CXP: Added firmware files to upgrade Interface Card 1C to Static 1.2 P0.
* GigE: [300043] The PylonGigEConfigurator now sets the interrupt moderation
        rate of NICs  to 'High' by default. This has shown to deliver a better
        performance and a lower CPU load in some cases.
* pylon Viewer: [290156] The pylon Line Profile tool has been added in the
                Window menu of the pylon Viewer. This GUI tool displays the
                brightness along a freely placeable line in the image window.
* pylon Viewer: [295575] When using Single Shot with line scan cameras with a
                CoaXPress frame grabber that supports the height feature, the
                pylon Viewer will use the continuous acquisition mode, resulting
                in the acquisition of an image with the specified height instead
                of a single line.
* pylon Viewer: [290499] The Color Calibrator now supports Basler ace 2 GigE
                Vision and USB3 Vision and boost R CoaXPress color cameras.
* pylon Viewer: [275057] The docking framework used in the pylon Viewer has been
                replaced. This results in a new look and feel and docking behaviour.
* pylon Viewer: [303875] The New Features tab in the 'Welcome to pylon' dialog
                has been updated.
* pylon Viewer: [289871] The pylon Viewer GUI tools have been updated to Qt
                6.5.3.
* vTools: [277423] The new OCR Basic vTool has been added.
* vTools: [297867] In vTool dialogs with image display, the pixel coordinates of
          the current mouse pointer position are shown below the image.
* vTools: [282974] Improved Template Matching Basic with angle limitation and
          wait indicator.
* vTools: [290464] vTools Starter: Improved recognition times for code reader
          vTools.
* Workbench: [275056] The design of the vTools pane has been updated. vTools are
             now grouped by use cases and can be added as favorites. A search
             feature makes it easier to find the vTool you are looking for.
* Workbench: [275052] Results in the pin data view can now be matched to the
             corresponding region in the image. If there are several results from
             the same output pin, you can clickÂ′ "Show related Region" next to a
             result to highlight the corresponding region.
* Data Processing: [275724] Added a generic output observer that collects recipe
                   outputs in a queue.
* Data Processing: [275631] Removed type names from the Data Processing SDK
                   interface and replaced them with EVariantDataType and
                   EVariantContainerType.
* Data Processing: [282500] The acquisition mode can now be set for Camera
                   and Image Loading vTools when starting a recipe (see
                   EAcquisitionMode for more details).
* Data Processing: [282501] Allowed using callables as observers in Data
                   Processing SDK.
* Data Processing: [302347] Added a sample showing how to handle region data.
* Data Processing: [299393] Added a sample demonstrating how to use the OCR Basic
                   vTool.
* Data Processing: [301327] Improved the documentation of ellipse and rectangle
                   data types regarding rotation.
* Data Processing: [300915] Simplified Barcode and Composite Data Types samples.
* Data Processing: [299163] Added information about the pylon Viewer Recipe Code
                   Generator to documentation and samples. Added overview
                   diagram to programmer's guide.
* BPD: The offline BPD has been updated.


CORRECTIONS
===========
* GigE: [292109] An EmitResend is skipped for empty lists. This reduces the system
        load. (Version 5.4.0.1250)
* GigE: [287757] Timeouts for read or write requests are no longer ignored.
* GenTL/USB: [305224] A GenTL Producer (USB) issue with with packed pixel formats
             on ace 2 cameras has been fixed.
* GenTL/GigE: [305224] A GenTL Producer (GEV) issue with with packed pixel formats
              on ace 2 cameras has been fixed.
* pylon C++ SDK: [302425] A potential memory leak of the CPylonDataComponent has
                 been fixed.
* pylon C++ SDK: [284623] Changed the "pylonutilitypcl" library from loading at
                 start-up to on demand at runtime.
* CXP: The maximum image width for mirroring has been improved.
* CXP: The FG_SYSTEMMONITOR_USED_CXP_CONNECTIONS did not show correct values
       before. This has been fixed.
* CXP: An incorrect default for FG_LINETRIGGERINSRC and FG_SHAFTENCODERINSRC has
       been fixed.
* CXP: [285576] When WaitForFrame returns, buffers are always fully
       accessible by the application in all acquisition modes. This fixes issues
       when re-queuing a buffer very quickly.
* CXP: Fixed an issue which caused wrong setting for FG_DIGIO_INPUT when
       configuring a GPIO.
* GenTL/CXP: [274400] Fixed the length of CXP_BOOTREG_MANUFACTURE_INFO.
             Fixed unset Camera Link config value. Fixed discovery for cameras
             that start with 1.25 GB/s.
* GenTL/CXP: [291818] Fixed the Fg_unregisterApcHandler(), which has always been
             waiting for a timeout.
* GenTL/CXP: [271134] The range verification when reading values from the camera
             via GenAPI has been disabled to avoid caching issues.
* GenTL/CXP: [230948] A potential race condition have been fixed where a remote
             device could have been considered as discovered before the internal
             discovery has ended.
* GenTL/CXP: [270982] Changed the version of *.cti files.
* pylon Viewer: [295574] Improved the overall stability and performance when
                images are acquired at high frame rates.
* pylon Viewer: [303499] Fixed a potential crash when opening a camera while a CXP
                device was connected to the system.
* pylon Viewer: [300040] Fixed a potentially incorrect handling of camera grabbing
                state in Static Defect Pixel Correction plugin when switching
                cameras.
* pylon Viewer: [290499] Improved the way the Color Calibrator accesses cameras
                to support more camera models.
* pylon Viewer: [292677] Fixed an issue where images with height or width
                greater than 32767 would not be displayed.
* pylon Viewer: [303720] The behavior of the pylon Welcome dialog has been improved.
                Now, it only stays on top application-wide rather than system-wide.
* pylon Viewer: [292316] Fixed potential crash after stopping a recording with
                large images.
* pylon Viewer: [289709] Fixed an issue where moving the mouse in an empty image
                window would display invalid coordinates in the status bar.
* pylon Viewer: [287963] Fixed an issue where the Welcome dialog was not on top.
* pylon Viewer: [305588] Fixed an issue where the correct BPD topic wasn't opened
                when clicking the "Get help" link in the flat-field correction
                wizard.
* pylon Viewer: [305815] Fixed an issue that caused tooltips to be incorrectly
                displayed in some rare cases.
* Firmware Updater: [285018] Fixed an issue where cameras could not be
                    rediscovered after reset.
* vTools: [302805, 284218] Calibration Basic/Pro: Cosmetic improvements
          of the GUI.
* vTools: [297120] Fixed zoom focus in vTools with image editors.
* vTools: [303232, 283992] Fixed limit handling and readability in Image
          Enhancer Basic GUI.
* vTools: [303585] Fixed a typo in the feature documentation of the
          Gray Value Transformer vTool.
* vTools: [289438] Improved error message for Template Matching Basic and
          Image Morphology Basic if the format of the training image differed
          from runtime data.
* vTools: [292333] Updated vTool documentation for Template Matching Basic.
* vTools: [295169] In the settings dialog of the Camera vTool it's not possible
          anymore to change the selected camera while the recipe is running.
* vTools: [298850, 298846, 298792] Added missing icons in the settings dialog of
          the Image Loading vTool.
* vTools: [298735] Fixed crash during refresh of the available camera devices in
          the Camera vTool settings dialog.
* vTools: [290452] The type of output error for Gray Value Transformer Starter
          was changed from RegionArray to Image (pin type is Image).
* vTools: [PYVTO-535] Updates for Image Sharpening Starter vTool documentation and
          fixes for inaccuracies in vTool settings:
          A maximum mask size has been introduced, the maximum sharpening filter
          value is 25, and the maximum unsharp mask value is 101. The default factor
          for the sharpening filter is set to 9.
* vTools: [PYVTO-537] Fixed inaccuracies in Image Sharpening Starter settings:
          An error now appears in the pin data view if the mask size entered is
          greater than the maximum size.
* vTools: [PYVTO-550] Fixed inaccuracies in Image Sharpening Starter settings:
          When changing the mask height and width in the settings dialog, the
          parameter values in the API are updated accordingly.
* vTools: [283821] Fixed some layout issues in the Template Matching Starter dialog.
* Workbench: [304765] Fixed an issue that prevented scrolling in the Statistics tab
             of the Recipe Management pane.
* Workbench: [303281] Fixed an issue that could prevent recipes from being saved and
             loaded correctly when the user interface language was set to Japanese.
* Workbench: [306122] Changed the Sales inquiry URL in the vTool Licensing window
             for easier evaluation license access.


RESTRICTIONS
============
* GigE Vision: [259058] 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: [259100] In case the error message "Failed to allocate ressources." has
        been reported, Basler recommends using the pylon GigE Configurator tool
        to optimize the IP configuration of NICs and cameras.
* 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.
* GigE Vision: Multiple IP configurations on a single network interface are not
               fully supported by the IP Configurator tool.
* GigE Vision: Assigning a static IP address to a camera that is not in the same
               subnet as the network adapter may make the camera unreachable. To prevent
               this, set the rp_filter (reverse path filter) to 2 ("loose mode") on the
               camera's network interface. For more information, see the Assigning an IP
               Address to a Camera topic in the Basler Product Documentation.
* CXP IC: 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.
* CXP IC: For line scan applets, ranges of line period and line exposure are not
          handled properly. The maximum values may be lower than expected.
* CXP IC: For line scan applets with image mirroring enabled (VantagePont = TopRight
          or BottomRight), the actual maximum image width may be smaller than
          documented and depends on the applet and pixel format used. However,
          all applets support the maximum camera width of the Basler racer 2 L
          cameras (r2L8192-200cm). Contact Basler if a larger image width
          is required.
* CXP IC: When the CXP link speed is changed frequently on one port, it may
          happen that the speed change doesn't have any effect anymore. In that case,
          the error messages "Failed to set bitrate of uplink transceivers" and
          "Failed to set bitrate of downlink transceivers" are logged. Since the
          camera discovery probes the unconnected ports and therefore changes their
          link speed, this issue may occur when an application frequently tries to
          discover new cameras on unconnected ports.
* GenTL/CXP: The actual buffer size limit is 2 GB, which consequently imposes
             a restriction on the permissible values for Width and Height
             in the producer and results in that the maximum size of image is 2 GB.
* GenTL/CXP: The fps limit is between 50000 and 90000 fps depending on the number
             of buffers and image size.
             Examples for approximate values: 10 buffers and a minimum
             image size of 48x1 give a limit of approximately 50000 fps. 50
             buffers and a minimum image size of 48x1 give a limit of about 90000 fps.
             50 buffers and an image size of 8192x1 give a limit of approximately
             50000 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.
* 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.
* 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.
* 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.
* 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.
* CXP: In rare cases, the camera is not found after booting the computer. Power-cycle
       the camera to resolve this.
* CXP: When changing the PCIe slot used by the Basler CXP-12 Interface Card 1C
       in a computer, the computer must be in shutdown state. Problems may occur if the computer
       is in hibernation state, where the state of the OS has been persisted to
       disk.
* 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.
* CXP: Under rare circumstances, when the CXP link speed is changed frequently on one port, at
       some point a speed change has no effect anymore. To work around that,
       either reload the applet by loading a different applet and then loading the original
       one again or set the value of the SISO_FORCE_RELOAD_APPLET environment variable to 'yes'.
* 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
* 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: Limited GenTL support for producers with GenTL version 1.4 and below.
* 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.
* 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: To use the pylon Viewer, you must install the latest Mesa OpenGL driver for
                your system. On Debian-based platforms, you also need to install the
                following packages: libgl1-mesa-dri, libgl1-mesa-glx, libxcb-xinerama0,
                and libxcb-xinput0
* pylon Viewer: Under circumstances, the pylon Viewer may experience issues when using
                the Wayland display server protocol. It is recommended to use Xorg instead.
* 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 by 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).
* Workbench: Pixel values in the pin data view will not be updated if no new images are
             acquired.
* Workbench: When switching to full screen in a pin data view, the screen will remain black
             when no new images are acquired.
* Workbench: When loading recipes containing multiple pin data views, the limit of 16
             pin data views will be reached early, even if there are fewer than 16 pin
             data views present. Restarting the pylon Viewer may solve this issue.
* Workbench: The context menu in the Workbench may be too small to show all
             vTools when it is opened near the edges of the Workbench.
* Workbench: The pin data view may not show RGB values in the status bar when recipe is not
             running.
* Workbench: The pin data view may not allow cleaning up deleted pins.
* SDK: Under rare circumstances some SDK samples may terminate abnormaly. To workaround this,
       you can either rename the "pylonutilitypcl.so" library located e.g., under
       /opt/pylon/lib, unset the GenTL path, or prevent loading the U3V GenTL producer.
* 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: The pylon C API doesn't provide convenient functions to use GenDC
           and the Basler blaze 3D camera yet.
* pylon C: 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 guides yet.
           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.
* SDK: Kernel 3.x or higher is required to use the pylon C API.
* MP4: MP4 video recording requires the pylon Supplementary Package for MPEG-4 to
       be installed. 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: [139274] 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, pylon first disables the Compression Beyond
       feature in the camera and then starts recording.
* BPD: The Basler Product Documentation (BPD) requires advanced JavaScript support. Open the
       Basler Product Documentation in a modern browser, e.g., Firefox 44 (or higher) or
       Chrome 49 (or higher).
* BPD: On Ubuntu 22.04 (or higher), the offline Basler Product Documentation (BPD) may not be
       accessible when using Firefox due to permission restrictions. To work around this issue, you can
       set the environment variable TMPDIR to a location in the user's home directory, use a
       different browser, or install Firefox from a different source than snap.