石鑫华视觉
宝视纳Basler-pylon 7.4.0相机软件套装（Windows版）~basler_pylon_7_4_0_14900.exe
pylon 7.4.0
2023年9月
7.4.0
pylon相机软件套装（Windows版）的完整软件包。
pylon相机软件套装包含易于使用的SDK、驱动程序和工具，让您可通过Windows PC来操作任意一款Basler相机。pylon采用最新GenICam技术，可无限制使用最新型号的Basler相机并使用相关的硬件功能。Basler pylon支持CoaXPress 2.0、GigE Vision、USB3 Vision、Camera Link和GenICam GenTL。
pylon SDK简单易用，可帮助您开发完整的机器视觉应用、医疗应用和包括图像采集和图像处理在内的其他应用。仅需几行代码即可设置相机、采集图像，并将其保存。
pylon可为所有典型相机应用提供大量丰富的文档资料和示例程序以供参考，支持各种编程语言（C、C++、C#、VB.Net等），可大大促进应用的开发工作。
pylon提供的编程界面独立于正在使用的相机接口，这意味着可以轻松将使用pylon创建的应用程序移植到另一种相机接口技术。
Basler pylon支持所有当前的Windows版本，最高可支持Windows 11（64位）。由于pylon不仅支持Windows，还支持macOS和Linux（x86和ARM），因此在pylon下为Windows创建的应用程序可以轻松移植到其他操作系统和架构（如嵌入式系统）。
pylon 7.4.0相机软件套装（Windows版）
文件名: basler_pylon_7_4_0_14900.exe
文件大小: 611629696 字节 (583.30 MB)
修改日期: 2024-03-12 22:13
版本: 7.4.0.14900
MD5: d0e5fe0b87c9dd04b016546a7e89dd32
SHA1: 8a759b37f4462034ce377ef4828ee3d30f628e8f
SHA256: f71659e7960e938b4de18194835ec4a5329fa49f3ce6d55c0fc716b5d4139bdd
CRC32: b2814db0
Basler官方下载和百度网盘下载：
宝视纳Basler-pylon 7.4.0相机软件套装（Windows版）~basler_pylon_7_4_0_14900.exe
http://visionbbs.com/thread-32757-1-1.html
(出处: 石鑫华视觉论坛)
pylon 7 Camera Software Suite for Windows
RELEASE NOTES
Note: Patch versions of pylon for Windows 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: 2023-09-26
VERSION: 7.4.0 (Windows 10/11 64-bit)
################################################################################
BINARY COMPATIBILITY
====================
* pylon C++ API = 7.4.0: Applications built with earlier versions of the pylon C++
API are incompatible.
* pylon C API = 7.4.0: Applications built with earlier versions of the pylon C API
are incompatible.
* pylon.NET API = 1.2.0: Applications built with earlier versions of the pylon .NET
API are compatible.
* pylon Data Processing API = 1.3.0: Applications built with earlier versions of
the pylon Data Processing API are incompatible.
NEW FEATURES / CHANGES
======================
* CXP: [269821] Added support for Basler boost V CoaXPress cameras with GSPRINT
sensors. These cameras are for use with the Basler CXP-12 Interface Card 4C
or imaWorx CXP-12 Quad acquisition cards, which require a host interface
with PCIe Gen 3 x8 (Direct Memory Access) or better.
* CXP/GenTL: [269821] The CXP GenTL Producer, ProducerCXP.cti, has been updated to
version 5.11.1.
* CXP: [269823] The applet for Basler CXP-12 Interface Card 1C with static version
S1.2 has been updated to version 5.2.7.
* CXP: [269823] 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.2.7.
The TapGeometry, SensorGeometry, ImageSelector, and WhiteBalance parameters are
supported now.
* CXP: [269821] The CXP driver has been updated to version 2.2.0.
* CXP/GenTL: [273804] Added DeviceTapGeometry capability negotiation between a CXP
camera and an applet.
* CXP/GenTL: [248643] Added the Compatibility Status category that provides information
about the status of interfaces and devices:
- Interface Driver Version
- Interface Producer Version
- Interface PCIe Status
- Interface Power Supply Status
- Device Pixelformat Status
- Device Automatic ROI Control Status
- Device Tap Geometry Status
* GigE Vision: [283882] The pylonGigEConfigurator tool has been updated to configure
any 5G/10G network adapters.
* GigE Vision: [279190] The PylonGigEConfigurator tool has been extended to enable
Receive Side Scaling (RSS) on supported network adapters.
The RSS feature enables the efficient distribution of network receive
processing across multiple CPUs in multiprocessor systems.
Basler recommends using the PylonGigEConfigurator for all ace 2 1GigE
and 5GigE cameras.
* SDK/.NET: [268070] Added a new BufferHandlingMode feature to Pylon::CInstantCamera
and to Basler.Pylon.Camera. It may be set either to "Pool" (default mode)
to use a pool of preallocated buffers for grabbing or to "Stream" to let
pylon allocate new buffers on demand.
* pylon Viewer: [274876] The Recipe Code Generator has been added. This tool allows
you to quickly and easily generate C++ code examples from a recipe.
You can access this feature from the Workbench menu or toolbar.
* pylon Viewer: [275068] The Flat-Field Correction feature for boost V CoaXPress cameras
has been added.
* pylon Viewer: [12789] The Color Calibrator has been unlocked for all Basler color
cameras that support the Color Transformation feature, e.g., Basler ace
Classic, ace U, ace L GigE Vision and USB3 Vision cameras.
* vTools: The following vTools have been added:
- Calibration Pro
- Image Smoothing Starter
- Image Morphology Starter
- Gray Value Transformer Starter
- Image Combiner Starter
- Image Sharpening Starter
- Document Cropper
- Aztec Code Reader Basic
- Aztec Code Reader Pro
- PDF417 Code Reader Basic
- PDF417 Code Reader Pro
- Image Sharpening Basic
- Image Enhancer Basic
* vTools: [433,435] Template Matching Starter: The Template Matching Starter vTool now
offers support for rotated templates.
Recipes created with previous versions of the Template Matching Starter vTool
are incompatible.
* vTools: [1156, 1080, 12374] Calibration Basic: Improved table visualization and GUI.
* vTools: [6992] Barcode Reader Pro: Improved GUI Design.
* vTools: [5321] Improved scaling for 4K displays.
* vTools: [11381] Region Feature Extraction: Supports inverse transformation with
InverseTf now.
* vTools: [12150] ROI Creator: ROI settings in nodemap adapt to size of image loaded.
* vTools: [277410] QR Code Reader Basic/Pro and Data Matrix Code Reader Basic/Pro allow
selection of data code types now, e.g., GS1 and Micro QR codes.
* vTools: [277409] Image editors support TIFF format now.
* vTools: [436] Template Matching Starter: Improved GUI for marking rectangular
templates.
* vTools: [275701] The Camera vTool provides a settings dialog to make camera selection
easier.
* vTools: [283754] Added recipe templates to show how to use the PDF417 and Aztec Code
readers.
* vTools: [6512] vTools now provide additional information about node maps for display
in the Features - All pane.
* Data Processing: [275636] Simplifed C++ SDK for working with the Point,
Line, Rectangle, Circle, and Ellipse data types.
* Data Processing: [275634] Added C++ SDK access to the Transformation Data data type.
* Data Processing: [275633] Added C++ SDK access to the Region data type.
* Data Processing: [275635] Simplified the access to arrays of values.
* Data Processing: [281192] Added CVariant::SetError() method for testing purposes.
* SDK/CXP: [271889] The "Utility_FFC" C++ sample has been added to demonstrate the use
of the Flat-Field Correction feature of Basler boost V CoaXPress cameras.
* SDK: [273873] Added a new internal 3PCL feature.
* SDK: [279165] The CBaslerUniversalInstantCamera class has been updated.
* General: [283722] The New Features dialog has been updated.
* BPD: Updated the offline Basler Product Documentation.
CORRECTIONS
===========
* CXP/GenTL: [271134] The range verification when reading values from the camera via
GenAPI has been disabled to avoid caching issues.
* CXP/GenTL: [230948] A potential raise condition have been fixed where a remote
device could have been considered as discovered before the internal
discovery has ended.
* GenTL: [270982] Fixed the version of *.cti files.
* GenTL: [270713] The GetAccessMode function returns the current version of a GenTL
producer now.
* SDK: [270082] The toolbar of the GUI_MFC sample is now DPI-aware.
* vTools: [12538] Measurements Basic, Line/Circle/Ellipse/Rectangle Measurements Pro:
Inverse transformation is always applied when connected.
* vTools: [282714] Image Morphology: Parameter values changed in the Features pane
are now immediately visible when reopening the vTool’s settings dialog.
* vTools: [9422] Camera vTool: The device handling support for transport layers and
interfaces has been improved.
* vTools: [282714] Image Morphology Basic: Fixed data handling in the node map.
* vTools: [164] Template Matching Starter: The Positions_px and Positions_m output pins
now output the center point of a match.
* vTools: [285511] Template Matching Basic: Improved performance for large template images.
* pylon Viewer: [280331] Fixed an issue that caused a saved BMP image to be distorted
if the width was not a multiple of 4.
* pylon Viewer: [278762] Fixed an issue that caused the displayed image to be distorted
if the width was not a multiple of 4.
* pylon Viewer: Fixed spelling mistakes in the pylon GigE Configurator.
* pylon Viewer: [282994] The zoom feature of the Histogram pane works for color images now.
* pylon Viewer: [284222] An issue that caused incomplete loading of recipes with zero
output Pin Data Views in the Workbench has been fixed.
* Data Processing: [275700] Fixed an issue in the Camera vTool sample when working with
ace 2 cameras.
* Data Processing: [282343] Improved the behavior when evaluation licenses time out.
* Camera Emulation: [271091] Fixed an issue where the configured frame rate was not
always met.
* BPD: [269812] Fixed some missing links in the PylonC API documentation.
* BPD: [269415] Added information about supported file types for the
CImagePersistence::Load() and the CImagePersistence::Save() functions.
RESTRICTIONS
============
* Color Calibrator: [12789] The Color Calibrator does not support all Basler color
cameras yet. Basler ace 2 GigE Vision and USB3 Vision and boost R
CoaXPress cameras will be supported in one of the next releases.
Due to a different camera feature set, Basler dart and boost V
cameras are not supported by the Color Calibrator.
* 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.
* 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 asquisition frame rate
and cause image loss.
* 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 directoy with a shorter
path not exceeding 80 characters, i.e., directly in your user profile:
C:Users<username>Samples.
You can enable long paths on Windows 10, Version 1607, and later. See the Microsoft
documentation for more information.
* 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).
Therefore, the times measured may vary depending on the configuration of your
system and the overall CPU load.
* CXP: When camera parameters are changed during image acquisition, the change is
not reflected in the interface card.
* 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 device ID changes when an applet is changed. Therefore, the device ID that
was queried with one applet can be used with a different board and a different applet
only if the applet has the same name as the original one with which the device ID
was generated.
* 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: 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: 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: In rare cases, the camera is not found after booting the computer. Power-cycle
the camera to resolve this.
* CXP: Grabbing with very high frame rates above 50000 fps using the Basler CXP-12
Interface Card 1C is not supported.
* CXP: When allocating buffers used for grabbing, the buffer address must be
aligned to 8-byte increments on 64-bit operating systems. This is
automatically the case if you use heap memory.
* 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.
* Camera Link: The pylon Viewer may fail to enumerate Camera Link cameras when connected to
some Camera Link frame grabbers. To avoid that, run the pylon CL Configurator
tool from Applicationsdin instead. The pylon APIs are not affected by
that issue.
* 3D: To use 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.
* 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);
For C# you can use:
Parameters[(BooleanName)"EventNotification"].TrySetValue(true);
in addition to:
Parameters[PLCamera.EventNotification].TrySetValue(PLCamera.EventNotification.On);
For VB the syntax is:
camera.Parameters(CType("EventNotification ", BooleanName)) .TrySetValue(true);
* 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 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: On computers with an Intel HD graphics card, it may be necessary to
update the graphics driver to the current version.
* GenTL: [133711] Limited GenTL support for producers with GenTL version 1.4
and below.
* MP4: Recording of video files with cameras with resolutions of 20 MP or more
may fail if the Quality parameter is set to 80 % or more. To work around that,
set the Quality parameter to a lower value.
* MP4/AVI: [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 will first disable the Compression Beyond
feature in the camera and then start recording.
* MP4: If the pylon Supplementary Package for MPEG-4 was already installed with a
pylon 5.x.x installation and pylon 6.x.x is installed afterwards, the pylon
Supplementary Package for MPEG-4 has to be uninstalled and installed again.
* 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.
* AVI video recording:
- When compression is enabled for AVI recording, some codecs may have
certain restrictions with respect to the camera pixel format and image size.
Example: When selecting the Xvid codec, the use of image resolutions like
640 x 480, 1280 x 720, 1280 x 960, and 1280 x 1024 may not work. In
that case, adjust the image height or width slightly.
- It is recommended to use the Windows Media Player for viewing the AVI files.
- Depending on the camera's pixel format, image size, and the codec used for
compression, the VLC Media Player may not play the recorded videos
correctly.
- For rendering uncompressed video files, the VLC Media Player requires the
image width to be a multiple of 4.
- The VLC Media Player may not render a video if the recording speed is less
than 5 frames per second. As a workaround, navigate to the "Input
Codecs" section in the VLC's "Advanced Preferences" dialog and increase
the value for the "File caching (ms)" setting.
* DirectShow and Twain: CoaXPress cameras are not supported with the DirectShow
and Twain drivers.
* 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:
- Open the Power Options in the control panel.
- Click "Change plan settings" for the selected power plan.
- Click "Change advanced power settings".
- In the "Power Options" dialog on the "Advanced settings" tab, select
"USB settings".
- Set "USB 3 Link Power Management" to "Off".
* GenTL: The GenTL producer for GigE Vision does not support action commands.
* GenTL: The GenTL producer for GigE Vision does not support multicast configurations.
* 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).
* SDK: The InstantCameraArray classes can acquire images from a maximum of 21 cameras.
* pylon .NET: 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: 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.
* General: If you run the GUI applications using the built-in Administrator
account on Windows 10, some Help/Support features may not work due to
security restrictions.