Dual Mini PCIe CAN FD

Package contents

The hardware package includes the module and the following accessories.

Connection example · two DB9 breakout cables →

Documentation & software

The supplied support materials are organized into the following folders and README. Start with the README, then follow the user manual to connect the hardware and install the driver. Use the SDK when integrating DualCANFD into your own application.

English labels above correspond to the supplied folders 01_用户手册, 02_SDK, 03_驱动 and README_开始这里.md.

For the complete user manual, SDK, drivers and README, contact Xilume. The driver package and host software are also available from the download links below.

Hardware connection

The module uses a Mini PCIe form factor with a USB host data path.

1. Check the host connection

   Confirm that the target slot routes USB signals, and check module power and mounting compatibility. A slot with PCIe signals alone cannot provide this module’s USB data path.

2. Install the module

   Power down the host, secure the module in its matching slot and mounting position, and connect one included DB9 breakout cable to each CAN channel.

3. Connect the bus

   Follow the module and harness labels for CANH, CANL and the associated signal reference. Fit 120 Ω termination at the two physical bus ends.

Windows

1. Install the driver first

   Download and fully extract the matching package below. In its Windows folder, run Xilume_Dual_CANFD_Windows_Driver_V1.0.0.1.exe.

2. Connect and verify the device

   Connect the device after installation. In Device Manager, under Ports, check for two Xilume CAN/CAN FD COM endpoints. Windows assigns the COM numbers.

3. Open CAN FD software

   Select the corresponding CAN channel in Xilume CAN FD Control Center, match the bus settings and connect. TraceBox Analyzer Pro provides capture and diagnostic reporting.

CAN FD COM endpoints carry the Xilume CAN command protocol. Use CAN FD Control Center or an application that implements this protocol to exchange frames.

Linux

DKMS, a compiler toolchain and headers matching the running kernel are required. The installer builds the driver for the local kernel.

Fully extract the driver package and open a terminal in its Linux folder.

chmod +x install.sh uninstall.sh verify.sh
sudo ./install.sh

Reconnect the device after installation, then run the verification script.

./verify.sh

Use the CAN interface names reported by the check. The operating system does not guarantee the names can0 and can1.

First CAN connection

This example uses a correctly wired test bus and assumes the verification script reports can0. Substitute the actual interface name and match the peer’s bit rate.

Classical CAN · 500 kbit/s

sudo ip link set can0 down
sudo ip link set can0 type can bitrate 500000
sudo ip link set can0 up
ip -details -statistics link show can0

With your distribution’s can-utils installed, display received frames in a terminal.

candump can0

CAN FD · 500 kbit/s + 5 Mbit/s

Confirm the peer supports and uses these CAN FD rates before switching to this configuration.

sudo ip link set can0 down
sudo ip link set can0 type can bitrate 500000 dbitrate 5000000 fd on
sudo ip link set can0 up

Higher data rates depend on the transceiver, wiring, termination and peer configuration. The 8 Mbit/s specification refers to the CAN FD data phase.

Interface compatibility

The current CAN text protocol does not represent RTR remote frames or distinguish extended frames with numeric IDs at or below 0x7FF from standard frames. Check these conditions when selecting an application protocol or developing an interface.

Connection checks

Related downloads

This guide follows the README, installer and verification script distributed in the current driver package. See Software & Drivers for release versions.