We use cookies on our website to provide you with the best possible service and to further improve our website. By clicking the "Accept All" button, you agree to the use of all cookies. You can limit the cookies used by clicking on "Accept selection". Further information and an option to revoke your selection can be found in our privacy policy.
These cookies are necessary for basic functionality. This allows you to register on our website and forum or order products with our online shop.
With these cookies, we collect anonymized usage data for our website. For example, we can see which content is interesting for our visitors and which resolutions are used. We use the information to optimize our website to provide you with the best possible user experience.
show more
For the development of CAN applications, we provide different APIs (Application Programming Interfaces): the PCAN-API from the PCAN-Developer package and the cost-free PCAN-Basic API. This section includes a direct side-by-side comparison of our development packages.
Features | PCAN-Basic | PCAN-Developer 4 |
---|---|---|
Based on the API | PCAN-Basic API | PCAN-API 4 |
Development for the platforms | Windows® 11 (x64/ARM64), 10 (x86/x64), and Linux | Windows® 11 (x64/ARM64), 10 (x86/x64) |
Enables the connection to CAN busses | ||
Enables the connection to CAN FD busses | ||
Supports all PEAK CAN interfaces (Parallel port CAN interfaces are only supported on x86 systems) | ||
Maximum number of CAN channels supported per hardware type | A maximum of 16 (depending on the PEAK CAN interface used) | 64 |
Maximum number of applications per physical CAN channel | A single application of your own and multiple by PEAK-System | 64 |
Access to hardware parameters | Access to specific parameters | Full access to all parameters |
Precision of time stamps of received messages (depending on the PEAK CAN interface used) | 1 µs | 1 µs |
Control of transmission time by time-stamping outgoing messages | - | |
Configuration of single-shot and self-receive-request transmissions | - | |
Notification of the application through Windows events when a message is received | ||
Support of CAN error frames | ||
Generation of CAN error frames | - | |
Driver-internal CAN message buffer | up to 32.768 per CAN channel | up to 32.768 per Client* |
Simulated CAN communication between the applications | - | |
Use of a single Windows DLL as an interface for all PEAK CAN interfaces | ||
Hotline support for developers | - | |
Hardware configuration | Via application | Via control panel or application |
Hardware reset during an active connection | ||
Free definable message filter | One filter for each CAN channel | One filter per Client* |
Licensing | License for PCAN-Basic included in the scope of supply of the hardware | Unlimited licenses for the PCAN-API 4 |
Software supplied | PCAN-View | PCAN-View PCAN-Nets Configuration PCAN-Status Display |
* Information on PCAN-API and Clients can be found on PCAN-Developer product details.