CAN Bus

Overview
The CAN bus is an ISO standard bus originally developed for vehicles. It manages the Chassis Electrical System Control and is responsible for critical activities like engine electrical, and skid control. This system is also used to provide vehicle diagnostic information for maintenance. A multi-star configuration seems typical of this bus with a primary bus line that branches into sub bus lines at its extremities then attaches to multiple device nodes. Differential voltage is applied over twisted pair at 1.5 to 2.5V and 2.5 to 3.5V for noise resistant signaling. Bit rates up to 1 Mbit/s are possible at network lengths below 40 m. Decreasing the bit rate allows longer network distances (e.g., 500 m at 125 kbit/s). (Jeremiah J. Flerchinger [[media:avc-lan.pdf|Source]]) Controllers supporting CAN FD, an enhanced CAN version with frames up to 64 byte and bit rates up to 4 Mbit/s, will be available in the second half of 2014. A can4linux version supportig CAN FD on a IFI CAN is ready to be used.

Although developed as car communication network CAN is used in many other areas, industrial, medical, maritime laboratory and more. Most often with a CAN based higher layer protocol like CANopen on top of it.

Additional information can be found at:
 * http://en.wikipedia.org/wiki/CAN_bus
 * SocketCAN News
 * CiA CAN in Automation CAN user association
 * CAN Wiki
 * CAN FD Specification Version 1.0
 * CiA CAN in Automation CAN user association
 * CAN Wiki
 * CAN FD Specification Version 1.0

CAN Support in Linux
CAN is supported by Linux device drivers. Mainly two types exist. Character device based drivers and network socket based drivers. The Linux kernel supports CAN with the SocketCAN framework.


 * SocketCAN Documentation
 * mailing list for Linux Kernel CAN development
 * linux-can git repository
 * Berlios Project Page (obsolete)

One of the character based drivers is can4linux.


 * SourceForge project page
 * German Wikipedia article
 * English Wikipedia article

SocketCAN Supported Protocols

 * RAW: send & receive raw CAN frames
 * BCM: Broadcast manager, offload repetitive work to the Linux kernel
 * ISOTP ...
 * SAE J1939

SocketCAN Supported Controllers

 * Microchip MCP251x
 * Atmel AT91 SoCs
 * ESD 331 CAN Cards
 * NXP (Philips) SJA1000
 * Freescale MPC52xx SoCs
 * Bosch CC770
 * Intel AN82527
 * TIs SoCs
 * Serial/network devices utilizing ASCII protocol (slcan driver)

SocketCAN Support in Programming Languages/Environments

 * Android
 * Java
 * Python

can4linux Supported Controllers

 * Allwinner A20 with integrated CAN (on the popular BananaPi single-board computer.)
 * Analog Devices BlackFin BF537
 * Atmel AT91 SoCs
 * Freescale FlexCAN (ColdFire 5282, i.MX25, i.MX28, i.MX35)
 * Microchip Stand Alone CAN MCP2515
 * NXP Stand Alone CAN SJA1000 (on different ISA or PCI/PCIe boards)
 * Xilinx Zynq with XCAN
 * 'virtual' CAN mode without CAN hardware
 * 'virtual' CAN mode supporting CAN FD
 * IFI CAN FPGA IP, in classic CAN mode and CAN FD mode

can4linux Support in Programming Languages/Environments

 * Tcl/Tk
 * Python

CAN Controllers Emulation (WIP/experimental)

 * SJA1000 CAN controller based PCI board emulation for QEMU
 * Cards models provided:
 * Simple memory mapped SJA1000 in the first PCI BAR with ad-hoc PCI ID
 * Kvaser PCIcan-S single I/O mapped SJA1000 model compatible with kvaser_pci Linux driver on guest side
 * The emulated CAN buses can be connected to virtual or physical SocketCAN interface if Linux is used as host system
 * Project repository: https://github.com/CTU-IIG/qemu
 * Work started by 2013 GSoC project when RTEMS project donated its slot to work on QEMU CAN support - see RTEMS related page for more info and use instructions

SocketCAN Bechmarking

 * CAN gateway timing analysis and repository with benchmark infrastructure

SocketCAN Tutorials

 * Bringing CAN interface up
 * can-utils
 * libsocketcan
 * libnl