Professional CAN and CAN FD development kit for Windows®
The professional PCAN-API, at the heart of the PCAN-Developer package, allows advanced Windows® applications integrating CAN and CAN FD to be developed. This programming interface provides a complete function library via DLLs for x86, x64 and ARM64 architectures.
Unlike PCAN-Basic, CAN communication here relies on the concept of "Clients", which brings numerous benefits. Several applications can, in particular, access the same physical CAN channel simultaneously. In addition, virtual connection lines allow "Clients" to establish simulated CAN communication between Windows® applications, without requiring any hardware.
Since version 4, PCAN-API and its integrated tools support the CAN FD standard (CAN with Flexible Data rate), whose main benefit is a significant increase in transfer bandwidth.
The API can be used with several programming languages. Header files are provided for C/C++, Delphi and Python. An assembly is provided for C#, VB.NET and C++/CLR. Sample code is included for each supported language.
CAN connection via "Clients"
Applications developed with PCAN-API rely on "Clients" to communicate with "Nets". A "Net" combines the link to an external bus via the appropriate hardware and the interconnection of several applications.
The following rules govern CAN connections via "Clients":
- One or more "Clients" can join the same "Net"
- A "Client" can be attached to several "Nets"
- A "Net" is associated with either no hardware or a single valid piece of hardware
- A piece of hardware can be configured with connections to different "Nets"
- Only one configured link to a "Net" can be active at a time for a given piece of hardware
- When a "Client" sends a message, it is relayed to all other "Clients" on the same "Net" as well as to the external CAN bus via the hardware
- Any message received by the hardware is distributed to all "Clients" connected to the "Net"
- PCAN-API 4 interface DLLs (x86/x64/ARM64)
- PCAN-Developer 4 license package
- Applications: PCAN-View, PCAN-Nets Configuration and PCAN-Status Display
- Header files for the C/C++, Delphi and Python languages
- An assembly for the C#, VB.NET and C++/CLR languages
- Examples for all supported languages
- Documentation in PDF format
Professional CAN and CAN FD development kit for Windows®
The professional PCAN-API, at the heart of the PCAN-Developer package, allows advanced Windows® applications integrating CAN and CAN FD to be developed. This programming interface provides a complete function library via DLLs for x86, x64 and ARM64 architectures.
Unlike PCAN-Basic, CAN communication here relies on the concept of "Clients", which brings numerous benefits. Several applications can, in particular, access the same physical CAN channel simultaneously. In addition, virtual connection lines allow "Clients" to establish simulated CAN communication between Windows® applications, without requiring any hardware.
Since version 4, PCAN-API and its integrated tools support the CAN FD standard (CAN with Flexible Data rate), whose main benefit is a significant increase in transfer bandwidth.
The API can be used with several programming languages. Header files are provided for C/C++, Delphi and Python. An assembly is provided for C#, VB.NET and C++/CLR. Sample code is included for each supported language.
CAN connection via "Clients"
Applications developed with PCAN-API rely on "Clients" to communicate with "Nets". A "Net" combines the link to an external bus via the appropriate hardware and the interconnection of several applications.
The following rules govern CAN connections via "Clients":
- One or more "Clients" can join the same "Net"
- A "Client" can be attached to several "Nets"
- A "Net" is associated with either no hardware or a single valid piece of hardware
- A piece of hardware can be configured with connections to different "Nets"
- Only one configured link to a "Net" can be active at a time for a given piece of hardware
- When a "Client" sends a message, it is relayed to all other "Clients" on the same "Net" as well as to the external CAN bus via the hardware
- Any message received by the hardware is distributed to all "Clients" connected to the "Net"