Skip to main content

Introduction

Purpose of This Manual​

This manual is the user's manual for the MicroPeckerX SocketCAN driver.
SocketCAN extends the Linux socket communication API and enables CAN communication in the same way as using Internet protocols via sockets.


How to Use This Manual​

Each chapter explains how to install this product, sample scripts, and related topics.
If you have any questions, please refer to the FAQ or contact us.
However, technical inquiries regarding the MicroPeckerX SocketCAN driver require a separate paid support contract.


Terminology​

The terms used in this manual are described below.

TermDescription
CANAbbreviation for Controller Area Network.
A communication protocol developed for in-vehicle networks. It is an international standard specified by ISO 11898.
CAN FDAbbreviation for CAN with Flexible Data-rate.
A communication protocol that extends CAN and enables faster and larger-capacity data transmission and reception.
BRSAbbreviation for Bit Rate Switch. A CAN FD function that switches the data phase to a faster bit rate.
SocketCANThe standard Linux CAN communication framework. It handles CAN devices as network interfaces and can work with can-utils and other tools.
Arbitration BaudrateThe transfer speed for the section that sends the frame identifier ID and similar information. In CAN FD, this is slower than the data phase.
Data BaudrateThe transfer speed for the data phase. This can be configured only for CAN FD.
Kernel moduleA driver that can be dynamically added to the Linux kernel. The SocketCAN driver also falls into this category.
module parameterA parameter specified when loading the driver. It specifies the default baud rate, termination, hardware timestamp, and similar settings.
hardware timestampReception time information added on the device side. This driver supports reading receive timestamps.
can-utilsA standard utility set for handling CAN communication on Linux. It includes cansend, candump, and other tools.
mpdrv_runA management script for the MicroPeckerX SocketCAN driver. It loads and unloads the driver, starts and stops channels, and checks the status.
start-allA command of mpdrv_run. This is the normal startup method for starting can0 / can1 in sequence.
can0 / can1Examples of CAN interface names recognized on Linux. If another CAN interface already exists in the environment, different names may be used.
terminationCAN bus termination setting. This driver can enable or disable device-side termination with a module parameter.
SavvyCANOpen-source CAN log analysis and send/receive software. It can visualize CAN bus communication with a GUI.
WiresharkNetwork analysis software. It supports packet reception and analysis for various protocols, including CAN bus.
chmodA Linux command for granting execution permission to files and scripts.
AppImageA portable executable file format for Linux. Software can be run without installation.

Notes on Using This Manual​

  • Reproducing, modifying, or translating part or all of this manual without permission from the copyright holder is prohibited except where permitted by copyright law.
  • The information and images in this manual are current as of the time of writing and may differ from the latest product or product website content, such as wording or design.
  • Company names and product names described in this manual are trademarks or registered trademarks of their respective companies.

Verified Operating Environment​

The MicroPeckerX SocketCAN driver is used in a Linux SocketCAN environment.
An example of a verified operating environment is shown below.

ItemDetails
OSUbuntu 24.04.4 LTS (64-bit)
Kernel6.17.0-22-generic
Compilergcc 13.3.0
Related toolscan-utils, iproute2
note

This manual uses can0 / can1 for explanation. In an environment where another CAN network interface already exists, the actual interface names may be other than can0 / can1. Check the actually assigned names with ip link or ./mpdrv_run status.