$0.00
0

Cart

Flipper Add-On: CANBus

Sniff, inject, and analyze CAN bus traffic from your Flipper Zero — plus OBD2 scanning and UDS diagnostics on vehicles you're authorized to test.

$35.00

In stock

In the box

Flipper Add-On CANBus board
Cable with OBD2 connector

Not included

The Flipper Zero itself is not included, and neither is the free SavvyCAN software for deeper signal analysis on a PC.

You also need

A Flipper Zero
The Flipper MCP2515 CANBUS app, installed from the wiki’s First steps page
A Windows or Linux PC, if you want to analyze signals in SavvyCAN
Your own vehicle or one you are authorized to test — or a RAMN bench testbed

What is the Flipper Add-On CANBus?

The Flipper Add-On CANBus is an add-on board built around an MCP2515 CAN controller, paired with a companion Flipper Zero app called Flipper MCP2515 CANBUS. Together they let you interact with CAN bus networks: sniffing and displaying the data being transmitted, and injecting packets, for CAN network analysis, error detection and peripheral control. The Flipper MCP2515 CANBUS app also adds an OBD2 scanner with basic PID codes and UDS services: read the VIN, reset an ECU, read or delete diagnostic trouble codes (DTC), or send a manual UDS service. For deeper analysis it bridges over USB to SavvyCAN, a CAN frame analysis tool for Windows and Linux, using the SLCAN protocol. Electronic Cats frames all of this as authorized research on a vehicle you own or are authorized to test — showing how accessible data and commands are over this unencrypted network, not bypassing security features.

Read live diagnostics from your own car's OBD2 port

Your dashboard light says something is wrong; it does not say what. Connect the add-on to the OBD2 port of a vehicle you own or are authorized to test, then run the OBD2 scanner and the UDS services from the Flipper Zero. Live engine RPM, the VIN and the stored trouble codes come up on screen — and you can clear the codes from the same menu.

Decode CAN signals on your PC with SavvyCAN

Sniffing on the Flipper Zero screen shows you the traffic; turning those frames into named signals takes a DBC file and a bigger screen. Bridge the add-on to a Windows or Linux PC over USB with the SLCAN protocol and open SavvyCAN, the Electronic Cats fork, to load, capture, decode and analyze frames from a vehicle you own or are authorized to test. A Hackster.io tutorial validated exactly this path as a low-cost alternative to proprietary CAN analysis hardware.

Practice sniffing and injection on a bench testbed, not a car

In a workshop or on a bench, someone will eventually send a malformed packet — better not on a real car, since wiring straight into a live ECU network can damage a vehicle. Wire the add-on to a RAMN testbed instead: a miniature network of four ECUs, connected over CAN-High and CAN-Low. Sniffing and packet injection can then be practiced safely. Note that RAMN does not emulate VIN or DTC, so those OBD2 features fail against it.

Start in 10 minutes

  1. Update your Flipper Zero to the latest official firmware with qFlipper (connect over USB, Install from file, then Install) or the official mobile app. Custom firmware such as Unleashed also works if it uses the same API version the app was compiled with, but it is no longer required.
  2. Install the Flipper MCP2515 CANBUS app following the First steps page of the wiki.
  3. Attach the add-on to your Flipper Zero and connect it to the CAN network: a vehicle’s OBD2 port, or direct CAN-High (white wire) and CAN-Low (black wire) wiring. Going straight into a live ECU network instead of the OBD2 port can damage the vehicle — do it carefully, and only on hardware you own or are authorized to test.
  4. Open the app and pick a function: sniffing with CAN masks and filters, the Sender (once after a delay, or periodically), the Replayer for log playback, the OBD2 scanner, or UDS. Logs export to CSV.
  5. Optional — connect the Flipper Zero to a Windows or Linux PC over USB and open SavvyCAN (Electronic Cats fork) to decode the frames with DBC files.
CAN controller

MCP2515 (Microchip), stand-alone CAN 2.0B controller

CAN protocol

CAN 2.0B — standard and extended data and remote frames

Host interface

SPI, up to 10 MHz

Supply voltage

2.7 V – 5.5 V

Active current

~5 mA typical

CAN wiring

CAN-High = white wire · CAN-Low = black wire

Firmware license

GNU AGPL v3.0

Hardware license

CERN Open Hardware Licence v1.2

Is my car compatible with the app and hardware?
It depends on the vehicle. The wiki keeps a community-maintained compatibility table: sniffing, the OBD2 scanner and UDS are confirmed working on a Hyundai Accent / Dodge Attitude 2006 and on a Chevrolet Tornado 2017, and confirmed not working — all three — on a Volvo (model unspecified). Any vehicle using CAN FD is directly incompatible: “the hardware is not compatible with it.” Use it only on your own vehicle or one you are authorized to test: the point is to show how accessible data and commands are over this unencrypted network, not to bypass security features or gain unauthorized access. Connecting directly to a live ECU network instead of through the OBD2 port can damage the vehicle, so do it carefully.
Not for this board yet: the 3D-printable STL case files in the flipper-addons repo currently cover the Marauder, SubGHz and MagSpoof add-ons only. There is no published case file for the CANBus add-on.
Contact the Electronic Cats Support Team through the <a href=”https://electroniccats.com/contact/”>Contact Us page</a>.
Free shipping to the US on orders +$200 USD · to Mexico on orders +$75 USD