CAN Tools
Classical CAN and ISO CAN FD reference
Bit timing calculator
Run the calculator with the nominal bounds, then use the controller’s data phase bounds for an FD data bitrate. SocketCAN reports the controller clock and timing limits in ip -details link show can0. Prescalers progress in increments from the minimum. Set the controller’s maximum SJW. The calculator checks the requested SJW against that maximum and both timing segments. TSEG1 combines propagation and phase segment 1, so verify that phase segment 1 can accommodate SJW after allocating propagation quanta.
Bitrate = clock ÷ (prescaler × (1 + TSEG1 + TSEG2)). Sample point = (1 + TSEG1) ÷ (1 + TSEG1 + TSEG2). For each feasible total quanta per bit, the calculator tries the nearest prescalers and segment splits. It orders the resulting candidates by absolute bitrate error, then absolute sample-point error, then more quanta per bit. It shows candidates even when the requested bitrate is unattainable. Check timing errors, clock tolerance, propagation, transceiver and driver constraints before applying a candidate. Linux SocketCAN, CiA 601 guidelines.
Arbitration simulator
Compare two contenders starting at the same SOF. The display uses logical bits and omits common stuff bits. Recessive is 1 and dominant is 0. A tie means there is no winner during arbitration. Differences later in the frame can cause errors instead of resolving priority.
Frame field visualizer
Inspect the logical field order. The display shows lengths for the data and CRC regions and lists fixed CRC stuff bits as a group. It leaves dynamic stuffing, payload values, CRC calculation and actual ACK observation to a wire trace.
Data length code mapping
| DLC | Classical CAN | CAN FD |
|---|---|---|
| 0 | 0 | 0 |
| 1 | 1 | 1 |
| 2 | 2 | 2 |
| 3 | 3 | 3 |
| 4 | 4 | 4 |
| 5 | 5 | 5 |
| 6 | 6 | 6 |
| 7 | 7 | 7 |
| 8 | 8 | 8 |
| 9 | 8 | 12 |
| 10 | 8 | 16 |
| 11 | 8 | 20 |
| 12 | 8 | 24 |
| 13 | 8 | 32 |
| 14 | 8 | 48 |
| 15 | 8 | 64 |
Identifier explorer
Use decimal, 0x hexadecimal or 0b binary. The identifier width determines format even when a 29-bit value fits in 11 bits. An identifier’s meaning is defined by the application protocol or a supplied message database.