Skip to main content

MicroPeckerX SocketCAN Driver

Frequently asked questions about the MicroPeckerX SocketCAN driver.

Product Specifications​

Can users change the communication baud rate?

Currently there is no way for users to change the baud rate. Although SocketCAN communication uses the baud rate specified at startup, the driver itself operates at a fixed rate.

If the SocketCAN driver uses a fixed 500 kbps arbitration rate and 2 Mbps data rate, is it dedicated to CAN FD?

The SocketCAN driver supports both Classic CAN and CAN FD. In Classic CAN mode, it communicates only at the 500 kbps arbitration rate. In CAN FD mode, it uses a 500 kbps arbitration rate and 2 Mbps data rate. Reception also supports both 500 kbps Classic CAN messages and 500 kbps/2 Mbps CAN FD messages.

Can I use MicroPeckerX in a Windows 11 + WSL2 (Ubuntu 20.04) + USBIPD-WIN environment?

WSL2 generally does not require additional drivers for USB recognition, but SocketCAN itself is not officially supported on WSL2. Because USB device pass-through may also be restricted, we recommend using a native Linux machine.

Can I build the driver on Raspberry Pi OS (PiOS)?

PiOS does not include kernel headers by default, so the driver cannot be built until you install them. Use the following apt command and confirm that your kernel version and environment are supported:
sudo apt-get install raspberrypi-kernel-headers (or sudo apt install raspberrypi-kernel-headers)

Can the SocketCAN driver run in virtual Linux environments such as VirtualBox?

If VirtualBox does not support USB 2.0 connections, it may not meet MicroPeckerX requirements. Virtual machines are not officially supported, but the driver may work if USB 2.0 or higher is enabled and device pass-through functions correctly.