Add new features
Updated frame descriptor information.
Added support for our new PL-D USB3 cameras.
Added new features:
Added new function
Updated frame descriptor information
Added support for our new PL-C USB cameras.
Don't bother looking for the GEV cameras if the GEV driver is not loaded.
Better version on ENABLE_FEATURE macros in PixeLINKTypes.h.
New Frame descriptor for our PL-C cameras.
Executables and runtime environment moved to Visual Studio 2008 SP1.
PxLGetNextFrame could return very old frames.
Aborting a debug session while streaming a USB camera could cause a blue screen.
Changes to environment variables during install would not take effect until after reboot.
FEATURE_IMAGER_CLK_DIVISOR has been deprecated.
Save/Load factory settings did not update the ROI on GEV cameras.
Stopping the stream could take up to 10 seconds to complete.
PxLInitialize would only find cameras that were connected when the application started.
FEATURE_PIXEL_FORMAT is not persistent on GEV cameras, therefore it should not have the FEATURE_FLAG_PERSISTENT set.
Capture OEM: When loading user or factory settings, restore FEATURE_PIXEL_FORMAT to an 8-bit format if FEATURE_FLAG_PERSISTENT not set.
Default firewire stack on Windows 7 could cause blue screens.
Legacy firewire stack on Windows 7 cannot stream full rate on some computers (e.g HP). See the PixeLINK Knowledge Base Article 274 for more information.
32-bit drivers would unnecessarily be installed in %SystemRoot%\Syswow64\drivers on 64-bit machines.
Added 64-bit version of ApiSpy.
For GigE cameras, FRAME_DESC::uFrameNumber field now uses a camera-based counter, rather than one generated by driver on host.
Added support for development of 64-bit applications.
Several GigE bug fixes.
Callbacks for CALLBACK_FRAME applied neither flips nor rotations.
Fixed a Blue-Screen seen when using "Stop Debugging" in Visual Studio when debugging an application using callbacks.
PxLGetNumberCameras would not find a GigE camera that has already been initialized with PxLInitialize(Ex).
PxLSetCameraIpAddress would sometimes return an error when setting a static IP address.
PxLGetNextFrame would occasionally time-out when using very low frame rates.
PxLGetCameraFeatures was reporting an incorrect FEATURE_GAIN maximum.
Added support for PL-E and PL-H CCD series of GigE cameras.
Capture OEM now defaults to Advanced Mode.
API 3.2 for PL-A66x cameras now available as a separate install.
Added new feature, FEATURE_PACKET_SIZE, supported on GigE cameras.
New function PxLInitializeEx and new error codes.
Reduced dependencies on third-part libraries
Several bug and blue-screen fixes for GigE.
Addressed a streaming bug with some Firewire cameras.
Several bug and blue-screen fixes for USB, Firewire, and GigE.
Note: As of this release, GigE cameras do not support the following features:
This will be addressed in future releases Please contact PixeLINK support for more information.
Added support for new feature FEATURE_BODY_TEMPERATURE.
Improvements to make USB communications more robust.
Fixed some blue screens seen with USB.
A fix for frame loss at very high frame rate on Firewire.
Bug fix for GigE when rapidly starting and stopping streaming.
Now returning an error when calling START_PREVIEW on a USB or GigE camera that is not streaming.
Updated signature files for silent installs.
Fixed several blue screen issues associated with USB-over-Ethernet devices.
PixeLINK API is now const-correct.
Addition of FEATURE_FLAG_VOLATILE to feature flags.
Removal of support for Image Pro Plus.
Added Tips, Tricks and Gotchas section to documentation.
Removal of IP_ENGINE_INFO struct.
Changes to CAMERA_ID_INFO struct.
New feature flags
New PixeLINK.API.NET assembly:
- changes to reflect changes to CAMERA_ID_INFO and new feature flags.
- an error was incorrectly being reported when calling GetCameraFeatures on WHITE_BALANCE.
Documentation for PixeLINK.API .NET assembly now a separate help file.
More demonstration applications.
Changes to Capture OEM to allow it to compile and run under Visual Studio 2005.
USB and GigE cameras would return wrong Top and Left values for PxLGetCameraFeatures.
The frame rate recorded in the .avi files was incorrect.
Ability to control GigE heartbeat timeout via registry or PxLPrivateCmd.
More demonstration applications.
#defines previously in PixeLINKDefines+.h now in PixeLINKTypes.h.
Minor (benign) revisions to PixeLINKTypes.h.
Fixes for PixeLINKApi.bas.
Addition of PxLPrivateCmd.
Capture OEM preview overlay did not work with MONO8 images.
PxLGetCameraFeatures would return the wrong max value for ROI.Left and ROI.Top on 1394 based cameras.
Added a "launch pad" for the API to documentation.
Added information related to GigE tools.
Added extensions to support GigE cameras. Specifically:
Added .NET support and example code to the API documentation.
.NET assembly was missing enum for PixelAddressingType.
Added new feature MAX_PIXEL_SIZE - to report the maximum number of pixels used in the camera.
Changes to LabVIEW interface module.
Major changes to Help files.
Fixed resource leak when handling frame data.
Fixes problems setting knee-points on USB cameras.
Fixes to USB cameras for auto-exposure.
Various bug fixes
USB driver tested and signed by Microsoft.
Support for FEATURE_SHARPNESS.
Various LabVIEW fixes.
Support for non-blocking calls to PxLGetNextFrame (when callbacks configured) with software triggering.
Added new feature IMAGE_CLOCK_DIVISOR - Reduces frame rates by a factor of 2 for machines unable to process frames at the lowest frame rate setting.
Fixed playback bug when AVI is captured. Frame rate information saved in AVI header now reflects the speed of capture rather than a default of 50 fps.
PxLFormatImage can now output in RGB24.
Improvements to PxLFormatClip to improve performance and limit dropped frames.
Fix for using multiple descriptors. These were not working properly if tabs were switched in the Dev App.
There is a new PixeLINKApi.bas file included in the install for use with Visual Basic.
From version 4.0, the following changes have been made:
Modified on: Thu, 13 Jun, 2019 at 4:21 PM
Did you find it helpful?Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.