PCAN-API (CANAPI2.DLL) Version History

23.02.2011 - Version 2.56.2

Type of value parameter in CAN_Set..Param() functions was changed from DWORD to UINT_PTR, to make it possible to pass 64-bit pointers to the API DLL on 64-bit platforms
Added support for PCAN-USB Pro Error Generator feature
Added support for new device "PCAN_VIRTUAL"

The initialization of the DLL is no longer carried out when loading the DLL, but only if the first API function is called
Bug fix: If CAN_SetDeviceName was called with an unsupported device name parameter, the DLL used a previously opened device for subsequent API calls instead of returning the error code CAN_ERR_NODRIVER
Bug fix: If the DLL was loaded after system start first from a Windows service using System account privileges, accessing the DLL functions was no longer possible with normal user privileges
Bug fix: CAN_GetErrText did not return strings for the error codes CAN_ERR_UNKNOWN and CAN_ERR_ILLFUNCTION

Supports a new data transfer mechanism between device driver and DLL that was introduced with PCAN drivers V2.49

A call to CAN_SetDeviceName no longer closes a previously opened device if the device name is different. All devices are now being kept open until the DLL is unloaded. This reduces the overhead when switching repeatedly between devices
CAN_Read_Multi now uses a safe non-paged memory block to transfer received messages from the driver to the calling application, to make the data transfer safer and to prevent Blue Screens

New API functions CAN_RegisterMemory, CAN_GetMemory, and CAN_RemoveMemory to allocate non-paged memory. All function parameters are copied using a safe non-paged memory block before calling into the device driver

Bug fix: CAN_SetDriverParam and CAN_VersionInfo still did not use the Mutex object, which was introduced in V2.20.1 to serialize the API function calls

Bug fix: Conversion of Receive Event Handles did not work correctly for Non-WDM Windows 95/98 drivers

New API function CAN_Read_Multi
Some API functions did not use the Mutex object, which was introduced in V2.20.1 to serialize the API function calls

Bug fix: The Receive Event Handle was not converted in dependency of the used platform before it was passed to the device driver

The DLL reads the Registry value HKLM\Software\PEAK-System\CanApi2\Device when the DLL is loaded to determine the device that shall be opened by default