[6.5.1] - 2018-12-20

Fixed

[6.5.0] - 2018-11-13

Added

Fixed

Issue where some 32-bit applications would not work on 64-bit systems with
drivers v6.3.0 and later

Changed

No change in the driver for this release

[6.4.2] - 2018-11-30

Added

Support for infinite buffers per trigger enable

[6.4.1] - 2018-11-12

Added

AlazarExtractNPTFootersEx(), which allows to extract NPT footers correctly in
all acquisition modes for all boards that support this feature.

Deprecated

AlazarExtractNPTFooters(), AlazarExtractFFTNPTFooters() and
AlazarExtractTimeDomainNPTFooters(). These functions have been superseded by
AlazarExtractNPTFootersEx().

Fixed

Issue where AlazarAbortAsyncRead() would not properly terminate a running
acquisition on ATS9360, ATS9371, ATS9373 and ATS9416. This could cause data
alignment problems with applications that stop and start acquisition multiple
times consecutively, or with LabVIEW code samples.

Changed

No change in the driver for this release

[6.4.0] - 2018-10-18

Added

AlazarConfigureFastBufferLock() function

Changed

Deactivate SetCaptureClock for ATS9352

[6.3.0] - 2018-09-24

Added

Support for ATS9453

Fixed

Issue where the version number of the driver was incorrectly reported as 0.0.0

ATS9352 not recognized

[6.2.1] - 2018-08-16

Added

CAP_SUPPORT_8_BIT_PACKING and CAP_SUPPORT_12_BIT_PACKING entries to
AlazarQueryCapability().

Changed

Various API function descriptions to make them easier to understand.

[6.2.0] - 2018-07-31

Added

Support for ATS9352

Fixed

Channel memory sharing on ATS9637.

[6.1.4] - 2018-06-19

Changed

No user visible changes

[6.1.3] - 2018-06-12

Changed

No user visible changes

[6.1.2] - 2018-05-16

Fixed

Regression introduced in version 5.10.25 that caused ATS9870 master/slave
systems to show acquisition timeout problems.

[5.10.22] - 2016-11-25

Added

[5.10.21] - 2016-11-08

Removed

[5.10.20] - 2016-11-07

Added

Support for Windows Driver Kit 10

[5.10.19] - 2016-10-20

Fixed

Bug under Windows in ATS9360/ATS9373/ATS9416 driver and library that was not
reading EEPROM data at initialization time, which could cause an incorrect
input offset and not detect available memory with user-created applications.
Workaround for this bug used to be to run AlazarDSO or AlazarSysInfo before
launching user-created application, thus forcing the EEPROM data to be read.
This workaround is no longer required.

[5.10.18] - 2016-09-19

Deprecated

AlazarExtractNPTFooters(). This function has been superseeded by
AlazarExtractFFTNPTFooters() and AlazarExtractTimeDomainNPTFooters().