ess logo  
 
 
 
     
     
  Products  
     
   
     
 
 
     
  Events & Promos  
 
     
 

 

 

 
 
     
Video Tutorial on using several PEAK-System Software and Hardware products are available on official YouTube channel of PEAK-System Technik GmbH.

PC CAN Softwares
Development Packages
PCAN-Developer 4

The professional programming interface PCAN-API of the PCAN-Developer package makes it possible to create complex Windows® applications with CAN and CAN FD support. The API (Application Programming Interface) provides an extensive function library using interface DLLs for 32-bit and 64-bit systems.

Unlike PCAN-Basic, the CAN communication is handled by Clients and offers significant advantages. Thus, not only a single but multiple applications can access a physical CAN channel. Furthermore, it works even without hardware: Via virtual connections, Clients establish a simulated CAN communication among Windows® applications.

Beginning with PCAN-Developer version 4, the PCAN-API and the included tools support the new CAN FD standard (CAN with Flexible Data rate) which is primarily characterized by a higher bandwidth for data transfer.

The API can be used with different programming languages. The scope of supply includes examples and header files for the languages C/C++ and Delphi. 

 
 
 
 
PCAN-Developer

PCAN is a flexible system for the planning, development and use of CAN networks. The basis for the communication of PCs to external hardware via a CAN bus are Windows® kernel mode drivers. These form the core of a complete CAN network environment on a PC running Windows®.  This device driver manages the entire data traffic of all hardware connected to the PC. The interface to the user or the operator of a CAN-networked system are so-called PCAN clients. Process variables can be visualized and influenced with their help. The driver allows the connection of several clients, which can communicate with CAN buses. It supports several hardware components, which are based on the CAN controller SJA1000 from NXP.  PCAN-Developer consists of a single-user user license for the development package as well as a distribution license for the PCAN-Developer Redistributable. This package contains the API DLLs as well as the software PCAN-View, PCAN-CPL, PCAN-Nets Configuration and PCAN status display. 

 
 
 
 
PCAN-RP1210 API

The Recommended Practice 1210 was defined by the Technology and Maintenance Council (TMC) as a standardized API for communication between Windows® applications and vehicle communications networks.  PCAN-RP1210 API of PEAK system is an implementation of RP1210 versions A and C with support for CAN and SAE J1939 networks. This allows the API to develop its own RP1210 applications as well as the use of existing RP1210 applications with CAN adapters from PEAK system.  With the PCAN-RP1210 API, you receive a single user license for the development package as well as for the RP1210 connection to PEAK-CAN interfaces. The PCAN-Developer RP1210-Extension also includes a distribution license for the PCAN-RP1210 API-DLLs.

 
 
 
 
     
PC Software
     
PCAN-Explorer 6

The PCAN-Explorer 6 is a versatile, professional program for working with CAN and CAN FD networks. The user is not just limited to the observation of the CAN traffic. Manual or periodic transmission of messages or entire transmission lists allows him a direct influence, for example, for control purposes or simulations.

The PCAN-Explorer 6 can connect to several CAN and CAN FD busses at the same time. Unlike previous versions, the hardware type of used CAN adapters is no longer a limiting factor.

 
 
 
 
 
PCAN-Explorer 6: Plotter Add-in 6

The Plotter Add-in allows the recording and graphical representation of any number of signal courses. Signal sources can be the data from incoming and outgoing CAN messages as well as virtual variables and results from macro calculations.

Plot Viewer: The free Windows® software Plot Viewer enables the display of the records without an installation of PCAN-Explorer.

 
 
 
 
 
PCAN-Explorer 6: Instruments Panel Add-in 6

The Instruments Panel Add-in allows the graphical representation of digital and analog signals using different display instruments. The integrated input options and controllers make it possible to also generate signals on the CAN bus, allowing easy simulation of complex CAN applications.

 
 
 
 
 
 
PCAN-Explorer 6: CANdb Import Add-in 6

The CANdb format is a common data description format for CAN bus information in the car industry.

CANdb Import allows the import of CANdb files. This is a useful function for all those who do not want to manually transcribe their database into the PCAN-Explorer symbol format.

 
 
 
 
 
 
PCAN-Explorer 6: J1939 Add-in 6

The SAE J1939 network protocol describes communication on a CAN bus in utility vehicles for the transmission of diagnostics data and control information. It contains a complete network definition using 29-bit CAN IDs (CAN 2.0B Extended Frame).

The J1939 Add-in for PCAN-Explorer supports all definitions established by the standard’s parameter groups and provides a simple means of accessing the parameters. A database with all the definitions and parameters contained is also supplied.

 
 
 
 
 
 
PCAN-View

The PCAN-View software for Windows® is a simple CAN monitor for viewing, sending and recording the CAN data traffic. The messages can be sent manually and periodically with an adjustable transmission rate of up to 1 Mbit / s. Faults on the bus system and memory overflows of the controlled CAN hardware are displayed. The CAN traffic can be recorded and stored via the trace function.  PCAN-View is part of the scope of delivery of every PCAN-PC hardware and enables its quick and easy commissioning. In the connection dialog, all available PEAK-CAN interfaces are listed for this purpose. After selecting the hardware and setting the transmission rate, you can use all functions of the software and access hardware-specific settings and information.

 
 
 
 
 
PCAN-View

The PCAN-View software for Windows® is a simple CAN monitor for viewing, sending and recording the CAN data traffic. The messages can be sent manually and periodically with an adjustable transmission rate of up to 1 Mbit / s. Faults on the bus system and memory overflows of the controlled CAN hardware are displayed. The CAN traffic can be recorded and stored via the trace function.  PCAN-View is part of the scope of delivery of every PCAN-PC hardware and enables its quick and easy commissioning. In the connection dialog, all available PEAK-CAN interfaces are listed for this purpose. After selecting the hardware and setting the transmission rate, you can use all functions of the software and access hardware-specific settings and information.

 
 
 
 
 
PLIN-View Pro

The LIN monitor is included with the PCAN-USB Pro PLIN-View Pro for Windows®. Incoming LIN messages can be viewed through this software, whereby the use of LDF files (LIN Description File) allows the symbolic representation of LIN messages. Outgoing LIN frames can be defined depending on the master or slave operating mode.  In addition, the LIN functionality of the PCAN-USB Pro hardware is accessed using PLIN-View Pro, such as the on-board scheduler or the automatic transmission rate detection.  The PCAN-USB Pro also includes the PLIN API from PEAK-Systemtechnik. It allows you to develop your own LIN applications for communication with the PCAN-USB Pro.

 
 
 
 
 
PCAN-Explorer 6

The PCAN-Explorer 6 is a versatile, professional program for working with CAN and CAN-FD networks. The user is not limited to monitoring the CAN traffic. The manual or periodic sending of messages or complete mailing lists allows him direct influence, for example for control purposes or simulations.  The PCAN-Explorer 6 can connect at the same time with several CAN and CAN-FD buses. Unlike previous versions, the hardware type of the CAN adapters used is no longer a limiting factor.  A crucial point in the use of the program is the symbolic representation of the CAN messages and their user data. The hexadecimal information is converted into a readable and intuitive format with the aid of symbol files. 

 
 
 
 
     
Plotter Add-in

This line recorder allows the recording and graphical display of any number of signal traces. The data of incoming and outgoing CAN messages as well as virtual variables and results of macro calculations can be used as a signal source.  Plot Viewer: The free Windows® software Plot Viewer allows you to display the recordings without installing the PCAN Explorer.

 
 
 
 
     
J1939 Add-in

The network protocol SAE J1939 describes the communication on a CAN bus in commercial vehicles for the transmission of diagnostic data and control information. It contains a complete network definition using 29-bit CAN-IDs (CAN 2.0B Extended Frame).  The add-in J1939 for the PCAN-Explorer 5 supports all the definitions defined by the parameter groups (parameter groups) of the standard and provides easy access to the parameters. A complete data base with all definitions and the included parameters is included.

 
 
 
 
     
API
     
PCAN-RP1210 API

The Recommended Practice 1210 was defined by the Technology and Maintenance Council (TMC) as a standardized API for communication between Windows® applications and communication networks in vehicles.

The PCAN-RP1210 API by PEAK-System is an implementation of the RP1210 versions A and C with support for CAN and SAE J1939 networks. Thus, the API makes it possible to develop own RP1210 applications and to use already existing ones with CAN interfaces by PEAK-System.

With the PCAN-RP1210 API you get a single user license for the development package and for the RP1210 connectivity to PEAK CAN interfaces. The PCAN-Developer RP1210 Extension contains a distribution license for the PCAN-RP1210 API DLLs. With this extension, your customers can install the DLLs via the PCAN-Developer redistributable package.

 
 
 
 
 
PCAN-CCP API

The PCAN-CCP API is a programming interface for the communication between Windows® applications (Masters) and electronic control units (Slave ECUs). The API is based on the CAN Calibration Protocol (CCP) by ASAM and is mainly deployed for development in the automotive area. The PCAN-CCP API uses the CAN bus as transmission medium.

For accessing the CAN hardware in the computer, PCAN-CCP utilizes the programming interface PCAN-Basic, which is part of the scope of supply of every CAN interface from PEAK-System. The PCAN-CCP API package is available free of charge.

 
 
 
 
 
PCAN-XCP API

The PCAN-XCP API is a programming interface for the communication between Windows® applications (Masters) and electronic control units (Slave ECUs). The Universal Measurement and Calibration Protocol (XCP) is a further development of the CAN Calibration Protocol (CCP) by ASAM. XCP supports multiple transmission mediums, but is not compatible to CCP.

For accessing the CAN hardware in the computer, PCAN-XCP utilizes the programming interface PCAN-Basic, which is part of the scope of supply of every CAN interface from PEAK-System. The PCAN-XCP API package is available free of charge.

 
 
 
 
 
PCAN-PassThru API

For the programming of control units (ECU), there are countless applications from various manufacturers which are used in the development and diagnosis of vehicle electronics. The interface for the communication between these applications and the control units is defined by the international standard SAE J2534 (Pass-Thru). Thus, the hardware for the connection to the control unit can be selected regardless of its manufacturer.

PCAN-PassThru allows the use of SAE J2534-based applications with CAN adapters from PEAK-System.

 
 
 
 
 
PCAN-ISO-TP API

ISO-TP (ISO 15765-2) is an international standard for the transfer of data packages via CAN. Above CAN (OSI layers 1 and 2), the protocol covers the OSI layers 3 (Network Layer) and 4 (Transport Layer). It can transmit data packages of up to 4095 bytes per CAN message. The data bytes are transmitted segmented with multiple CAN frames.

The PCAN-ISO-TP API implements the functionality of the standard on the basis of 10 functions. They are categorized in Allocation, Configuration, Address Mapping Configuration, Information, and Communication.

PCAN-ISO-TP uses the PCAN-Basic programming interface to access the CAN hardware in the computer. PCAN-Basic is supplied with each CAN interface of PEAK-System.

 
 
 
 
 
     
PCAN-UDS API

UDS (ISO 14229-1) stands for Unified Diagnostic Services and defines the communication with control units (ECUs). The Windows® software tests the controller using various services. The process is done on the client-server principle where the program is in the position of the client (also called tester). UDS uses the ISO-TP standard as transport protocol, thus UDS can transmit data blocks of up to 4095 bytes size. Besides the exchange of maintenance information, for example, the transfer of firmware is possible.

The PCAN-UDS API implements the functionality of the standard on the basis of 8 functions. They are categorized in Tester Allocation, Configuration, Information, Utilities, Services, and Communication.

 
 
 
 
 
PCAN-OBD-2 API

For on-board diagnostics, the OBD-2 standard defines the exchange of specific vehicle parameters. The client makes a request on the connected control units (ECUs) in the vehicle to which one or several ECUs are answering. As part of OBD-2, the ISO 15765-4 standard describes the CAN bus as a transmission option.

The PCAN-OBD-2 API implements the functionality of the standard on the basis of 15 functions. They are categorized in Tester Allocation, Configuration, Information, Services, and Communication.

According to ISO 15765-4, OBD-2 is based on UDS. Analog to this, PCAN-OBD-2 uses the PCAN-UDS programming interface for the exchange of diagnostic data.

 
 
 
 
 
PLIN-API

LIN (Local Interconnect Network) is a serial network protocol which is characterized by a master-slave architecture and transmission patterns. The master regulates the bus access and controls the communication of up to 16 participants. Only when the master prompts a slave, the latter is allowed to transmit its stored information. On each request of the master, answers defined within a schedule table follow in a fixed time sequence.

LIN was introduced by five automobile manufacturers in 1999 and further developed under the supervision of the LIN Consortium. Until today, the LIN bus has proven itself to be a cost-effective alternative to the CAN bus for networking sensors and actuators in vehicles, such as seat, door, mirror, and climate controls.