5.0.1 31/03/2026

PCAN-Basic API DLL

Corrections de bugs

• The functions CAN_Read, CAN_ReadFD, and CAN_ReadXL failed to handle messages of type status
• Querying the parameter BUSSPEED_NOMINAL did not work with Gateway FD devices
• The conversion of the STARTTIME value in generated PCAN trace files did not take time zones into account

PCAN-Basic.NET Assembly

Améliorations

• Added support for CAN with Extended Data-Field Length (XL) within the Api class
• The assembly is now strong-name signed

Changements

• Support for non–plug-and-play hardware within the Api class has been discontinued
• Support for PC card devices within the Api class has been discontinued
• Changes to the TPCANParameter type:Removed deprecated parameter PCAN_DEVICE_NUMBERRenamed parameter PCAN_BITRATE_INFO to PCAN_BITRATE_INFO_BTR; PCAN_BITRATE_INFO is now deprecatedRenamed parameter PCAN_BUSSPEED_DATA to PCAN_BUSSPEED_FD; PCAN_BUSSPEED_DATA is now deprecatedAdded new parameters: PCAN_BITRATE_INFO_CC, PCAN_BITRATE_INFO_XL, PCAN_BUSSPEED_XL
• Removed deprecated parameter PCAN_DEVICE_NUMBER
• Renamed parameter PCAN_BITRATE_INFO to PCAN_BITRATE_INFO_BTR; PCAN_BITRATE_INFO is now deprecated
• Renamed parameter PCAN_BUSSPEED_DATA to PCAN_BUSSPEED_FD; PCAN_BUSSPEED_DATA is now deprecated
• Added new parameters: PCAN_BITRATE_INFO_CC, PCAN_BITRATE_INFO_XL, PCAN_BUSSPEED_XL

5.0.0 09/12/2025

PCAN-Basic API DLL

Améliorations

• Added support for CAN with Extended Data-Field Length (XL) through three new functions: CAN_InitializeXL, CAN_ReadXL, CAN_WriteXL
• Added support for the new Trace Format 3.0 (XL Trace)
• New parameters added: PCAN_BITRATE_INFO_CC, PCAN_BITRATE_INFO_XL, PCAN_BUSSPEED_XL

Changements

• Support for non–plug & play hardware has been removed
• Support for PC card devices has been removed
• Delphi sample projects have been replaced with Free Pascal projects
• Sample projects with a user interface were split into separate protocol-specific versions. For each programming language, there are now three samples: CAN CC, CAN FD, and CAN XL
• Deprecated parameter PCAN_DEVICE_NUMBER was removed
• Parameter PCAN_BITRATE_INFO renamed in PCAN_BITRATE_INFO_BTR. Parameter PCAN_BITRATE_INFO was deprecated
• Parameter PCAN_BUSSPEED_DATA renamed in PCAN_BUSSPEED_FD. Parameter PCAN_BUSSPEED_DATA was deprecated

PCAN-Basic.NET Assembly

Améliorations

• Prerelease/beta version supporting CAN with Extended Data-Field Length (XL) via the Api class

Changements

• Support for non–plug & play hardware within the Api class has been discontinued
• Support for PC card devices within the Api class has been discontinued
• Changes within TPCANParameter type:Deprecated parameter PCAN_DEVICE_NUMBER was removedParameter PCAN_BITRATE_INFO renamed in PCAN_BITRATE_INFO_BTR. Parameter PCAN_BITRATE_INFO was deprecatedParameter PCAN_BUSSPEED_DATA renamed in PCAN_BUSSPEED_FD. Parameter PCAN_BUSSPEED_DATA was deprecatedNew parameters added: PCAN_BITRATE_INFO_CC, PCAN_BITRATE_INFO_XL, PCAN_BUSSPEED_XL
• Deprecated parameter PCAN_DEVICE_NUMBER was removed
• Parameter PCAN_BITRATE_INFO renamed in PCAN_BITRATE_INFO_BTR. Parameter PCAN_BITRATE_INFO was deprecated
• Parameter PCAN_BUSSPEED_DATA renamed in PCAN_BUSSPEED_FD. Parameter PCAN_BUSSPEED_DATA was deprecated
• New parameters added: PCAN_BITRATE_INFO_CC, PCAN_BITRATE_INFO_XL, PCAN_BUSSPEED_XL

4.10.1 14/03/2025

PCAN-Basic.NET Assembly

Corrections de bugs

• When using the Worker class, a connection to a PCAN-LAN channel could not be established
• The LOOKUP_DEVICE_GUID parameter was not included in the backward compatibility class

4.10.0 18/12/2024

PCAN-Basic API DLL

Améliorations

• Includes the new parameter PCAN_DEVICE_GUID, which allows a clear distinction between USB-based PCAN devices

PCAN-Basic.NET Assembly

Améliorations

• Includes the new parameter PcanParameter.DeviceGUID, which allows a clear distinction between USB-based PCAN devices

4.9.0 24/04/2024

PCAN-Basic API DLL

Améliorations

• Includes the new parameter PCAN_LAN_CHANNEL_DIRECTION, which gives information about the communication flow of a PCAN-LAN channel

PCAN-Basic.NET Assembly

Améliorations

• Includes new parameter PcanParameter.LanChannelDirection, which gives information about the communication flow of a PCAN-LAN channel
• The number of times a Broadcast message was sent can now be read using a new property, Broadcast.Counter, and cleared by calling the new Broadcast.ResetCounter method

Corrections de bugs

• Fixed a race condition that allowed access to a discarded object (WaitHandle)

4.8.2 22/01/2024

PCAN-Basic.NET Assembly

Corrections de bugs

• A bug introduced in version 4.8.1 prevented the assembly from being loaded when using a debugger
• The required PCANBasic.DLL was only found when it was located directly next to the assembly

4.8.1 15/12/2023

PCAN-Basic API DLL

Corrections de bugs

• CAN_GetStatus always returned PCAN_ERROR_OK for a connected PCAN-LAN channel

Changements

• JAVA projects updated:Changed value of MAX_LENGTH_VERSION_STRING to 256Added enum TPCANParameter.PCAN_HARD_RESET_STATUSFixed issues within the JAVA PCANBasicExample, regarding CAN FD message receptionFixed issues with the SetValue functionFixed issue with TPCANFDMsg.getTypeEnum method
• Changed value of MAX_LENGTH_VERSION_STRING to 256
• Added enum TPCANParameter.PCAN_HARD_RESET_STATUS
• Fixed issues within the JAVA PCANBasicExample, regarding CAN FD message reception
• Fixed issues with the SetValue function
• Fixed issue with TPCANFDMsg.getTypeEnum method

PCAN-Basic.NET Assembly

Changements

• Adjustments to the native library validation process

4.8.0 04/10/2023

PCAN-Basic API DLL

Améliorations

• Includes the new parameter PCAN_HARD_RESET_STATUS, which enables the CAN_Reset function to additionally perform a hardware reset

Changements

• Missing description of the constant values MAX_LENGTH_HARDWARE_NAME and MAX_LENGTH_VERSION_STRING included to the documentation
• The help code in the PDF documentation has been improved

PCAN-Basic .NET Assembly

Améliorations

• Includes new parameter PcanParameter.HardResetStatus, which enables the Api.Reset method to additionally perform a hardware reset

4.7.1 12/07/2023

PCAN-Basic API DLL

Améliorations

• General code enhancements

Corrections de bugs

• All sample projects adjusted due to a wrong conversion of a TPCANTimestamp structure into a 64-bit value (microseconds)

Changements

• The internal procedure for cleaning abandoned nets and clients is not performed anymore. This is carried out by the device driver
• The header file for Visual Basic 6 was deprecated and is not delivered anymore

PCAN-Basic .NET Assembly

Améliorations

• The number of broadcast messages that the Worker class supports has been increased to 100

Corrections de bugs

• When having several Worker objects connected, calling Worker.Stop() in one of them was causing all other to get their channels disconnected
• The Api.Read(PcanChannel, out PcanMessage, out ulong) method returned incorrect timestamp values in some scenarios due to a calculation overflow
• A 'KeyNotFoundException' exception was being generated by accessing internal components that were erroneously garbage collected
• When updating a broadcast with the Worker.UpdateBroadcast(int, int, PcanMessage) method, the object's address was internally overwritten, so references to it no longer worked

Changements

• It is not more possible to add the same Broadcast object several times to the same Worker object
• It is not more possible to add the same Broadcast object to different Worker objects

4.7.0 07/03/2023

PCAN-Basic API DLL

Améliorations

• New TRACE_FILE_DATA_LENGTH value to be used with the PCAN_TRACE_CONFIGURE parameter, which allows showing the data length column instead of the DLC column within generated trace files
• Enhancements regarding ARM64

Corrections de bugs

• Querying the PCAN_RECEIVE_EVENT parameter failed on x64 systems
• Generating multiple trace files during a long time was generating an Access Violation error in some scenarios

Changements

• Input of Device ID in the sample projects is now done in hexadecimal

PCAN-Basic .NET Assembly

Améliorations

• A new value, ParameterValue.Trace.UseDataLength, can be used to configure traces to show the data length column instead of the DLC column

Corrections de bugs

• Querying the PcanParameter.ReceiveEvent parameter failed on x64 systems
• Generating multiple trace files during a long time was generating an Access Violation error in some scenarios
• The Worker class did not configure the reception of echo frames at connection time
• The constructor parameter “bool closedFilter” of the Worker class was ignored
• Adding a filter to receive only standard CAN frames was causing any message to pass the filter

4.6.2 24/10/2022

Améliorations

• New ARM64 API library
• New assembly PCAN-Basic.NET available as NuGet package

Corrections de bugs

• The Device ID of a hardware couldn't be read when its value was 0xFFFFFFFF

4.6.1 31/08/2022

Améliorations

• The PCAN_IP_ADDRESS parameter can now be read without having the channel initialized

Corrections de bugs

• The value returned for PCAN_CHANNEL_CONDITION was wrong when retrieving this information from a PCAN-Gateway device
• The BitrateFD parameter of the CAN_InitializeFD function was not written into the log file even though the function parameters were configured to be logged
• Initialization of a PCAN-LAN channel succeeded even when the PCAN_BITRATE_ADAPTING parameter was not specified and the bit rate passed to the function did not match the bit rate used by the channel
• Echo messages were not being marked as such when the channel used was a PCAN-LAN channel initialized for CAN FD communication
• The PCAN_HARDWARE_NAME parameter couldn't be retrieved from an uninitialized PCAN-LAN channel, if the hardware associated to it was configured for CAN FD communication

Changements

• The documentation of status frames within the CAN_ReadFD function was lacking of information about the status frame with a CAN_ERROR_OK as value

4.6.0 10/12/2021

Améliorations

• Includes new parameter ALLOW_ECHO_FRAMES that allows the reception of self-sent messages
• Includes new parameter PCAN_DEVICE_PART_NUMBER to get the part number of a PCAN hardware (a.k.a. IPEH number)
• New set of samples in console mode in all supported programming languages (except Java)
• Internal code enhancements

Corrections de bugs

• The function CAN_InitializeFD returned a wrong error code when the channel was already in use by PCAN-View, but with a different bit rate as the requested one
• The function CAN_Initialize returned a wrong error code when the channel to be initialized was already connected by PCAN-View as 'FD' channel
• The functions CAN_GetValue and CAN_SetValue returned a wrong error code when the channel used was wrong or PCAN_NONEBUS
• The function 'CAN_LookUpChannel' returned a wrong error code when the buffer for the channel handle was NULL
• The function 'CAN_GetErrorText' returned PCAN_ERROR_OK when the language code passed to the function was invalid or not found
• The parameter “PCAN_BITRATE:INFO_FD” returned always PCAN_ERROR_ILLMODE on an uninitialized channel, if that channel has been initialized as FD before, using a bit rate different than 500 kBit / 2MB @24 MHz
• The PCAN_TRACE_SIZE parameter configured the log file size to its maximum possible (100 MB) instead of 10 MB, if it was intended to set the default value (using 0 as the size value)
• The condition of a channel (PCAN_CHANNEL_CONDITION parameter) was erroneously returned as PCAN_CHANNEL_AVAILABLE in some scenarios
• When an application used the parameter PCAN_ATTACHED_CHANNELS while having one or more channels initialized, the returned status for those channels was 'PCAN_CHANNEL_PCANVIEW' instead of 'PCAN_CHANNEL_OCCUPIED'
• The function CAN_SetValue was failing for numeric values, if the buffer passed to the function was smaller than 4 bytes
• The function CAN_GetValue truncated numeric values when the buffer passed to the function was too small for the data, instead of returning an error
• The 64-bit parameters PCAN_ACCEPTANCE_FILTER_11BIT and PCAN_ACCEPTANCE_FILTER_29BIT were erroneously treated as 32-bit values under Python
• Wrong casting of the type TPCANStatus within the Pascal header file corrected
• An exception was thrown when the location of the log file (PCAN_LOG_LOCATION) was changed after activating the logging feature on French systems

Changements

• The value of the constant/define MAX_LENGTH_VERSION_STRING was changed from 18 to 256
• The function CAN_InitializeFD does not fail anymore, if the parameter PCAN_BITRATE_ADAPTING is used and the given bit rate string is not valid
• The sample projects are now shipped as a zip file within the PCAN-Basic package
• French text translations were revised/corrected

4.5.4 28/04/2021

Corrections de bugs

• Error frames were not written correctly into trace files using trace file format 2.0

4.5.3 10/02/2021

Corrections de bugs

• Starting with PCAN-Basic API v4.5.1, channel initialization failed if a PCAN driver with a version older than 4.2.1 was used

4.5.2 27/01/2021

Corrections de bugs

• PCAN-Basic API v4.5.1 returned the error PCAN_ERROR_ILLMODE when trying initializing CAN FD devices with regular CAN bit rates

4.5.1 21/01/2021

Améliorations

• Adjustments regarding the new PCAN-Gateway FD devices
• PCANBasic.py header file now includes code to try to load the API from the third-party PCAN-USB driver for Mac, PCBUSB (MacCAN)
• Documentation updated

Corrections de bugs

• The LookUpChannel function of the Python file PCANBasic.py returned a wrong data type

4.5.0 03/12/2020

Améliorations

• New function added, CAN_LookUpChannel, for finding PCAN-Basic channels through some attributes

Corrections de bugs

• The function CAN_SetValue returned PCAN_ERROR_OK for the parameters PCAN_LOG_STATUS, PCAN_LOG_LOCATION, and PCAN_LOG_TEXT, even if the log file could not be created (e.g. due to permission issues)

4.4.1 16/07/2020

Améliorations

• General code enhancements
• Documentation was updated

Corrections de bugs

• When using the tracing functionality, echoed messages (hardware self-received frames) were being included in the trace file as "Tx" messages

4.4.0 21/11/2019

Améliorations

• New structure TPCANChannelInformation to store information about a PCAN-Basic channel
• New constant values added:MAX_LENGTH_HARDWARE_NAMEMAX_LENGTH_VERSION_STRING
• New parameters added:PCAN_FIRMWARE_VERSION: reads firmware version of devicesPCAN_ATTACHED_CHANNELS_COUNT: returns the number of PCAN-Basic channels attached to the PCPCAN_ATTACHED_CHANNELS: returns a list of TPCANChannelInformation items with information on channels found
• New example with UI for Python 3.x
• New error code PCAN_ERROR_ILLMODE added
• General code enhancements
• MAX_LENGTH_HARDWARE_NAME
• MAX_LENGTH_VERSION_STRING
• PCAN_FIRMWARE_VERSION: reads firmware version of devices
• PCAN_ATTACHED_CHANNELS_COUNT: returns the number of PCAN-Basic channels attached to the PC
• PCAN_ATTACHED_CHANNELS: returns a list of TPCANChannelInformation items with information on channels found

Corrections de bugs

• CAN_GetValue(PCAN_CHANNEL_FEATURES) couldn't recognize if a channel was I/O capable
• PCAN-Basic channel enumeration was wrong, if the device driver was configured to enumerate devices in a new way
• When a read event was configured and the reception of messages was deactivated by a call to CAN_SetValue(PCAN_RECEIVE_STATUS), the event was still being triggered, even if no messages were placed in the reception queue

Changements

• The parameter PCAN_DEVICE_NUMBER:was marked as deprecatedwas renamed to PCAN_DEVICE_IDis applicable not only for USB devices, but also for PCI devices (beginning with PCAN device drivers v4.2.0)
• The following parameters can now be requested without having a channel initialized:PCAN_DEVICE_ID (formerly PCAN_DEVICE_NUMBER)PCAN_5VOLTS_POWERPCAN_BITRATE_INFOPCAN_BITRATE_INFO_FD
• was marked as deprecated
• was renamed to PCAN_DEVICE_ID
• is applicable not only for USB devices, but also for PCI devices (beginning with PCAN device drivers v4.2.0)
• PCAN_DEVICE_ID (formerly PCAN_DEVICE_NUMBER)
• PCAN_5VOLTS_POWER
• PCAN_BITRATE_INFO
• PCAN_BITRATE_INFO_FD

4.3.4 09/07/2019

Améliorations

• General code enhancements
• Documentation: List of PEAK devices updated

Corrections de bugs

• Calls of the function CAN_Read were ending with the error 0x1C20 (PCAN_ERROR_ILLCLIENT + PCAN_ERROR_QRCVEMPTY)
• The CHANNEL_IDENTIFYING parameter was behaving wrong on PCAN-USB devices with firmware version v8.4 or later
• Internal calculation for bit rates were causing a division by zero in some specific scenarios

4.3.3 22/05/2019

Corrections de bugs

• The generated PCAN-Trace file contained negative timestamps in some scenarios
• The chronological inclusion of sent messages (Tx) in the generated PCAN-Trace file was not accurate enough

4.3.2 04/02/2019

Améliorations

• The PCAN-Trace files generated with PCAN-Basic now contain information about the API version used to generate them

Corrections de bugs

• Compatibility issues fixed

4.3.1 14/12/2018

Corrections de bugs

• PCAN-USB X6 and PCAN-Chip USB modules were treated as standard PCAN-USB adaptors when identifying their channels. This caused the LEDs to remain on (orange color) until the devices were plugged out

4.3.0 23/11/2017

Améliorations

• New parameters added:PCAN_IO_DIGITAL_CONFIGURATION: Configures the digital pins of a device as digital outputsPCAN_IO_DIGITAL_VALUE: Sets the values of all digital pins of a devicePCAN_PARAM_IO_DIGITAL_SET: Sets selected digital pins of a device to 'high'PCAN_PARAM_IO_DIGITAL_CLEAR: Sets selected digital pins of a device to 'low'PCAN_PARAM_IO_ANALOG_VALUE: Reads the value of the analog pin of a device
• Parameters enhanced:PCAN_CHANNEL_FEATURES can now determine if a channel supports using I/OsPCAN_FEATURE_IO_CAPABLE: Device with I/O capabilities
• PCAN_IO_DIGITAL_CONFIGURATION: Configures the digital pins of a device as digital outputs
• PCAN_IO_DIGITAL_VALUE: Sets the values of all digital pins of a device
• PCAN_PARAM_IO_DIGITAL_SET: Sets selected digital pins of a device to 'high'
• PCAN_PARAM_IO_DIGITAL_CLEAR: Sets selected digital pins of a device to 'low'
• PCAN_PARAM_IO_ANALOG_VALUE: Reads the value of the analog pin of a device
• PCAN_CHANNEL_FEATURES can now determine if a channel supports using I/Os
• PCAN_FEATURE_IO_CAPABLE: Device with I/O capabilities

Corrections de bugs

• Calling CAN_GetValue with the parameter PCAN_CHANNEL_FEATURES returned an error when the channel had no support for INTERFRAME_DELAY

4.2.0 08/09/2017

Améliorations

• Added support for Error frames
• New parameters added:PCAN_ALLOW_STATUS_FRAMES: Enables/disables the reception of Status framesPCAN_ALLOW_RTR_FRAMES: Enables/disables the reception of RTR framesPCAN_ALLOW_ERROR_FRAMES: Enables/disables the reception of Error framesPCAN_INTERFRAME_DELAY: Pause between frames within the sending processPCAN_ACCEPTANCE_FILTER_11BIT: Acceptance code and mask for 11-bit CAN IDsPCAN_ACCEPTANCE_FILTER_29BIT: Acceptance code and mask for 29-bit CAN IDs, as 64-bit value
• Parameter behavior changed: PCAN_HARDWARE_NAME and PCAN_CONTROLLER_NUMBER can now be read without the channel being connected
• Parameter enhanced: PCAN_CHANNEL_FEATURES can be used to determine whether a channel supports the INTERFRAME_DELAY parameter
• Unused dependencies removed
• Library size optimized
• General update of sample projects
• Microsoft sample projects (.NET, MFC) were upgraded to Visual Studio 2010
• Documentation was updated
• PCAN_ALLOW_STATUS_FRAMES: Enables/disables the reception of Status frames
• PCAN_ALLOW_RTR_FRAMES: Enables/disables the reception of RTR frames
• PCAN_ALLOW_ERROR_FRAMES: Enables/disables the reception of Error frames
• PCAN_INTERFRAME_DELAY: Pause between frames within the sending process
• PCAN_ACCEPTANCE_FILTER_11BIT: Acceptance code and mask for 11-bit CAN IDs
• PCAN_ACCEPTANCE_FILTER_29BIT: Acceptance code and mask for 29-bit CAN IDs, as 64-bit value

Corrections de bugs

• Inconsistences between return code of CAN_Initialize and CAN_InitializeFD corrected
• The function CAN_GetStatus didn't take into account if a channel was initialized as FD or not
• MFC example edited: BRS checkbox was active at program start
• Header file for Python was adjusted: literal strings were not being interpreted as "byte string"
• Header file for Delphi was adjusted: The type TPCANBitrateFD was defined as "string", instead of "PAnsiChar"
• Some compatibly issues were solved

4.1.0 20/06/2016

Améliorations

• New Get-Parameter used to check the running status of the PCAN-LAN service
• Samples were updated to use the new parameter
• Python header file was updated to allow using it within Python 3.0
• Documentation was updated

Corrections de bugs

• Fixed incompatibility issues that were causing malfunctions of the library when using it within a Windows service

4.0.4 22/04/2016

Améliorations

• Change regarding PCAN-Trace handling: The relative start time in a trace is no more the file creation time but the timestamp of the first message written in the trace. Therefore, the first entry will now always have the time offset 0
• General code enhancements

4.0.3 06/11/2015

Améliorations

• The PCANBasic.py header file and the Python example were enhanced to support multiple platforms
• There is now a single file as Python example, which also includes Windows event support
• General code optimization

Corrections de bugs

• Compatibility issue fixed: The ReadFD function was adjusted to return the status code represented by a received status message, as done in earlier driver versions
• Compatibility issue fixed: It was possible to connect a PCAN-Light application and a PCAN-Basic application to the same channel simultaneously
• Trace Format 2.0 adjustment: The word "RTR" was removed from Remote Frames records

4.0.2 01/07/2015

Améliorations

• The parallel port CAN interface (PCAN-Dongle) is now supported as a Plug & Play device. Please note that this feature is in BETA state

4.0.1 24/06/2015

Améliorations

• Extra information was added to the properties of the PCANBasic.dll file, to show the platform for which the file was compiled (32-Bit or 64-Bit)

Corrections de bugs

• A problem regarding the creation of PCAN-Trace files was avoiding the storing of messages in the file
• The Delphi sample had a text formatting problem. An error message appeared while the list of available channels has been filled out

4.0.0 21/05/2015

Améliorations

• Added support for CAN with Flexible Data rate (FD) through 3 new functions: CAN_InitializeFD, CAN_ReadFD, CAN_WriteFD.
• Added support for the new Trace Format 2.0 (FD Trace)
• New device type support included: PCAN-LAN (Virtual PCAN-Gateway channels)
• The maximum amount of channels that can be connected simultaneously was increased from 8 to 16 for devices of the types PCAN-USB, PCAN-PCI, and PCAN-LAN
• Added seven new parameters: PCAN_CHANNEL_FEATURES, PCAN_BITRATE_ADAPTING, PCAN_BITRATE_INFO, PCAN_BITRATE_INFO_FD, PCAN_BUSSPEED_NOMINAL, PCAN_BUSSPEED_DATA, PCAN_IP_ADDRESS. More information about them can be found in the help file
• New version is backward compatible, i.e. applications compiled for PCAN-Basic version 1.x still work with the new version

1.3.3 13/12/2013

Corrections de bugs

• Preconfiguring the Listen-Only mode was not being done fast enough, which could cause bus errors when the bit rate was not correct
• The delay used in CAN_Uninitialize in order to transmit messages not yet sent was too short. This could cause that messages were truncated and generate bus errors in this way

1.3.2 25/09/2013

Améliorations

• PCAN-Basic can now be used in multi-session environments (from different Windows-Sessions at the same time), for example, from a Windows-Service and a normal User-Application
• Some compatibly issues were solved

1.3.1 06/09/2013

Améliorations

• The CAN trace records the status errors (BUSLIGHT, BUSHEAVY, BUSOFF) too
• Some compatibly issues were solved

Corrections de bugs

• An incompatibility issue with theFixed Hardware-Handle Procedurewas corrected. This was causing some channels to be marked as available when they were not
• Problem in header file for Python corrected. The functions GetValue and SetValue were failing and returning the error PCAN_ERROR_ILLPARAMVAL, when the Parameters PCAN_TRACE_LOCATION and/or PCAN_HARDWARE_NAME were used
• Sent messages were not included in the Trace file, if the status of the CAN bus was BUSHEAVY, BUSLIGHT, or BUSOFF

1.3.0 27/03/2013

Améliorations

• With PCAN-Basic is now possible to record transmitted CAN data (CAN_Read and CAN_Write data) using PCAN-Trace files. The configuration of the Traces as well as the activation of it is achieved using new parameters within the functions CAN_SetValue and CAN_GetValue
• It is now possible to physically identify an USB channels, by blinking its associated LED. The use of this feature is achieved using the functions CAN_SetValue and CAN_GetValue
• Some compatibility issues were solved
• The logging file shows now the API version being used, including platform version (32- or 64-bits)
• Internal code-optimizations

Corrections de bugs

• Problem in header file for C/C++, when compiling as C Code. Default-Parameters within the function CAN_Initialize will only used when C++ is declared (Compiled as C++ Code)

1.2.3 26/10/2012

Changements

• Bug fix: Memory leak in CAN-Send function removed
• Some smaller performance problems solved
• Enhanced the PCAN-Basic Java sample with a send timer

1.2.2 13/03/2012

Améliorations

• Some compatibility issues were solved

1.2.1 25/01/2012

Améliorations

• Some compatibility issues were solved

1.2.0 16/11/2011

Améliorations

• A new read-only parameter, PCAN_CONTROLLER_NUMBER, makes possible to ask the index of the physical channel(s) in a PCAN device
• The examples were changed to support the new parameter
• The new error code PCAN_ERROR_ILLDATA was added

Corrections de bugs

• Minor issues fixed within the function CAN_SetValue
• A access-problem using the Log functionality from different threads was fixed
• The example for C++ / MFC was edited. The read-thread was blocking the application in some scenarios

1.1.0 17/08/2011

Améliorations

• New pre-initialization capable parameter, PCAN_RECEIVE_STATUS, makes possible to allow/disallow reading of messages regardless of the filter configuration
• A full open filter needs no more to be first closed, before calling the function “CAN_FilterMessages” in order to restrict the reception of messages
• The new define LOG_FUNCTION_ALL makes it possible to configure all the available Log functionality with only one value
• The format of the Log file was updated in order to make the information more readable
• The log file can now be read/opened while it is being written

Corrections de bugs

• A small bug when closing the filter within the example C++ MFC Project was fixed
• An internal cast of a handle was wrong. This could cause problems on 64-bit platforms

Changements

• The examples were updated to support the new parameter. Added to this, they have now a new configuration for x64 platforms

1.0.10 09/06/2011

Améliorations

• The header file for Visual Basic 6 was changed to support optional parameters within the function CAN_Initialize
• Some compatibility issues were solved

1.0.9 13/05/2011

Corrections de bugs

• Incoming messages were not logged even though having configured the logging functionality with the value LOG_FUNCTION_READ

1.0.8 08/03/2011

Améliorations

• The examples were adjusted to work with a better performance when a lot of CAN data is being received

Corrections de bugs

• Minor issues within 32/64 bits data types were solved
• Some problems regarding backward compatibility to PCAN-Light were solved
• Problems with the Clean-up of orphaned connections has been fixed

1.0.7 25/01/2011

Améliorations

• New bit rate register values were added to the definitions / enumerations used to set the bit rate of a connection

Corrections de bugs

• The function CAN_GetErrorText did not work correctly if the given buffer was not empty
• Some compatibility issues were solved

1.0.6 15/10/2010

Améliorations

• New parameter added "PCAN_HARDWARE_NAME". Now it is possible to differentiate models of a same device, e.g. PCAN-USB and PCAN-USB Pro
• The property PCAN_LISTEN_ONLY was adjusted to be used with an uninitialized channel. Now it is possible to pre-initialize a channel in Listen-Only mode, I order to avoid arbitration problems at the moment of connecting the channel
• The Help files were updated

Corrections de bugs

• In some scenarios, the detection of available channels was reporting channels as occupied when they aren’t

1.0.5.17 08/09/2010

Améliorations

• The Header file and the example for Delphi were edited to avoid compile errors when using them within new versions of Delphi

Corrections de bugs

• The core CAN communication was actualized

Changements

• The German resources where edited

1.0.5 17/08/2010

Améliorations

• The functionality of the parameter PCAN_BUSOFF_AUTORESET was adjusted due to some compatibility issues between some device drivers

1.0.4 06/07/2010

Corrections de bugs

• Checking the availability of channels in a computer with the function CAN_GetValue and the parameter PCAN_CHANNEL_CONDITION was retuning wrong values

Changements

• The header files were edited. The defines related to the parameter PCAN_CHANNEL_CONDITION were changed
• The samples and the Help files were edited due to the mentioned changes

1.0.3 21/06/2010

Améliorations

• New example for Python 2.6 available

Corrections de bugs

• Some compatibility issues were solved

1.0.2 26/05/2010

Améliorations

• New PCAN-Basic examples for Delphi and for C++ Builder
• German documentation added

Corrections de bugs

• The return value of the CAN_Initialize function was still wrong in some scenarios
• More than one channel could not be connected at the same time under 64-bit systems

1.0.1.7 04/05/2010

Corrections de bugs

• The return value of the function CAN_Initialize could be CAN_ERROR_OK even when the initialization was not successful

1.0.1 30/04/2010

Améliorations

• A PCAN-Basic header file for VB-6 was included

Corrections de bugs

• All CAN_* functions were updated due to possible wrong return values in multi-threading scenarios
• The return value of the function CAN_Write could be wrong in multi-threading scenarios
• A wrong declaration of the overloaded method Read() caused problems in C# and VB.Net. Both headers were edited

Changements

• Adjustment of the supported operating systems to Windows® 7/Vista/XP

1.0.0.4 21/01/2010

Améliorations

• The functions CAN_Read and CAN_Write were improved to accept the structures TPCANMsg and TPCANTimestamp without byte-alignment information (using the default alignment)

Corrections de bugs

• A wrong German text resource for showing CAN messages was corrected

Changements

• The header files were modified. The byte alignment information was deleted from all headers

1.0.0.3 20/01/2010

Changements

• Inclusion of new error codes: HWINUSE, NETINUSE, ILLHW, ILLNET, ILLCLIENT in all header files
• Inclusion of description texts for the new error codes in the languages: English, Spanish, French, Italian, and German
• Modification of the PCAN-Basic function GetErrorText in order to support the new error codes

1.0.0.2 07/01/2010

Changements

• Inclusion of the project's configuration for 64-bit platforms

1.0.0.1 16/12/2009

Changements

• Inclusion of the new header file PCANBasic.py. This is a python module which represents the PCAN-Basic header file

1.0.0 11/12/2009

Changements

• Changed the default value of the parameter AUTO_RESET_ON_BUSOFF to false
• FIRST release version

0.0.6 02/12/2009

Changements

• First BETA released