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
Version 7 of PCAN-Explorer introduces a suite of new features to streamline your daily tasks in the CAN world, making them more efficient, comfortable, and straightforward. It includes the latest CAN standards, namely CAN XL and J1939 FD, along with the ability to script tasks with Python. Thus, you’ll be ready to explore the future of CAN.
CAN XL is the next generation of the CAN bus. CAN XL nodes use the same two-line High-speed CAN cabling as previous versions and are backward-compatible with CAN FD and CAN CC (Classic) devices. CAN XL provides data bit rates of up to 20 Mbit/s and a significantly higher payload of up to 2048 bytes per message. Additionally, CAN XL has predefined structure elements that signal specific data types to other XL nodes. This includes tunneling, virtual networking, and protocol extensions, such as security enhancements.
PCAN-Explorer 7 can handle the new structure of CAN XL message frames and shows the corresponding information chunks.
Up to PCAN-Explorer 6, only a single Symbol file, the CAN database format by PEAK-System, could be applied to a connection. When a new device was integrated into the CAN network, the corresponding definitions for CAN messages had to be merged into the existing Symbol file.
Now it is easy to add CAN message definitions flexibly to a Connection in PCAN-Explorer 7 by just applying the necessary additional Symbol file. The same can be done with third-party databases. The corresponding software support is provided by the Add-ins CANdb Import and AUTOSAR XML Import (available as bundle).
In addition to VBScript, PCAN-Explorer 7 now has an implementation of the widely used Python scripting language, known for its clear structure and its powerful standard library. With Python you can access the full Object Model of PCAN-Explorer 7 and create small automation tasks for your daily work in CAN environments.
PCAN-Explorer 7 uses the established CodeMeter licensing tool, with which you may already be familiar from other software applications. This offers flexible licensing options, including the new floating licenses for your enterprise environment. You can also use a self-hosted licensing server. Of course, single-user licenses and those using license dongles are available.
When playing back a CAN trace file to your CAN bus for testing purposes, for example, you may not only want to replay the entire data stream at once but also go through the CAN messages in meaningful chunks using breakpoints. You can even single-step through the trace files. Text-based trace files from PEAK-System tools can be used directly. Many other file formats, such as MDF4 and BLF, can be imported.
The SAE J1939 standard has been extended with J1939 FD which defines the use of CAN FD frames. The same Parameter Groups are used as in classic J1939, while the transport layer is optimized to benefit from higher data rate and larger payloads of CAN FD, especially for multi-packet messages.
You can take advantage of analyzing J1939 FD traffic with PCAN-Explorer 7 and its J1939 Add-in.
Wondering if any incoming CAN message has changed its data since the previous reception? In the Receive list of CAN messages and in the Watch window for Signals, this can now easily be detected visually, as changes in data bytes are highlighted.
The daily work experience with PCAN-Explorer 7 benefits from the 64-bit foundation and separate engines for communication tasks and the user interface.
For a comprehensive overview of all features, please refer to the product pages for the PCAN-Explorer 7 and its add-ins (optional functionality extensions):
The FAQ section is currently under construction and is being continuously expanded.
Q: What are the main differences between PCAN-Explorer 6 and PCAN-Explorer 7?
A: The key differences are described in the “New Features and Highlights” section above. Concerning usage, you will feel at home with the updated version because the main user interface structure hasn’t changed.
Q: Do the existing add-ins for PCAN-Explorer 6 also work with the new version 7?
A: No, the functionality of an Add-in is based on the code of PCAN-Explorer 7. Add-ins cannot be transferred between major versions of PCAN-Explorer.
Q: Can I use projects from earlier versions of PCAN-Explorer in PCAN-Explorer 7?
A: Yes, in principle you can open projects from earlier PCAN-Explorer versions directly in PCAN-Explorer 7. However, two element types do no longer work in PCAN-Explorer 7: The former Line Writer is not available, and Callback Libraries do not work because there has been a change from 32-bit to 64-bit architecture. A Callback Library (.dll) must be recompiled for PCAN-Explorer 7 to create a 64-bit DLL.
Q: How is PCAN-Explorer 7 installed?
A: The software, including the Add-ins, is provided as a single Windows setup file (.exe). You need administrator privileges to install the software. The Installation usually takes less than two minutes. You are then prompted to activate your license(s).
Q: Are there any features from PCAN-Explorer 6 that are not available in version 7 anymore?
A: The simple Line Writer Add-in is not provided with PCAN-Explorer 7 anymore. Please use the more powerful Plotter Add-in instead (Add-in license required).
Q: I am creating a new Symbol file in PCAN-Explorer 7 but cannot insert Variables. Why not?
A: The new Symbol file format version 7 doesn’t implement definitions by Variables anymore. You define Signals instead in the first step and insert those Signals in the CAN message (Symbol) definition in the second step.
English
Deutsch
Français
Chinese 中文
Korean
