Transceiver and Logic Voltage

The transceiver decides your voltage. The TJA1050 and MCP2551 need a 5 V supply, which is perfect for an Arduino Uno but means the MCP2515 on the same board drives its SPI output at 5 V, too high for a 3.3 V ESP32 or Raspberry Pi pin. Boards built around the SN65HVD230 run entirely at 3.3 V and are the safe choice for a Pi or ESP32 with no modification.

Crystal Frequency

The MCP2515 derives every bit time from its crystal, so your code must be told the correct value. Generic blue modules usually carry an 8 MHz crystal, Arduino shields typically use 16 MHz, and Raspberry Pi HATs vary by revision. Read the marking on the metal can before you write a line of code. A mismatch halves or doubles your real bitrate and the bus stays silent.

Connector and Termination

A screw terminal is best for bench networks and twisted pair wiring. A DB9 connector with an OBD-II pinout lets you plug straight into a car with a standard cable. Either way, look for a switchable 120 Ω termination resistor, because a CAN bus needs exactly two terminators, one at each end, and a node in the middle must have its terminator disabled.

Isolation and Protection

On a bench, a bare transceiver is fine. On a vehicle, a motor controller or anything with a separate ground, a galvanically isolated board with TVS diodes protects your Raspberry Pi from ground loops, load dump spikes and ESD. It costs more, but it is cheap insurance compared with a dead Pi and an SD card full of lost logs.

Library and Driver Support

On Arduino, the MCP2515 is supported by several mature libraries, including mcp_can, autowp arduino-mcp2515 and Seeed’s own CAN library. On a Raspberry Pi, the Linux kernel’s mcp251x driver turns the chip into a standard SocketCAN interface, so you can use can-utils and python-can without any vendor code. Branded boards add a wiki with tested wiring and overlay settings.

The Raspberry Pi has no CAN controller, and wiring a 5 V blue module to its 3.3 V GPIO is asking for trouble. The Waveshare RS485 CAN HAT solves both problems in one board. It plugs onto the 40 pin header, runs entirely at 3.3 V, and pairs an MCP2515 with a SIT65HVD230 transceiver, a 3.3 V part in the SN65HVD230 family. Because the MCP2515 is supported by the Linux kernel, one dtoverlay line in config.txt turns the HAT into a standard SocketCAN interface, can0, and from then on candump, cansend and python-can just work. As a bonus you also get a half duplex RS485 port on the UART with automatic direction control, handy for Modbus RTU sensors on the same project. Both buses have 120 Ω termination on a DIP switch and TVS surge protection. The one detail to check is the crystal: Waveshare has shipped this HAT with different oscillator values across revisions, so read the can and set the oscillator= parameter to match.

Once a CAN project leaves the bench and meets a real vehicle, a motor drive or a battery pack, isolation stops being optional. This Waveshare HAT carries two independent MCP2515 controllers, each with its own SN65HVD230 transceiver, and separates both buses from the Raspberry Pi with galvanic isolation on power and signal. SM24CANB TVS diodes on each port add ESD and transient protection, the kind of spikes you meet on automotive and industrial wiring. In Linux the two channels appear as can0 and can1, which opens up projects a single channel board cannot do: bridging two networks at different bitrates, acting as a gateway between a vehicle bus and your own devices, or logging two buses at once with a single timestamp source. Waveshare publishes the overlay settings and C and Python examples on its wiki. It costs more than the single channel HAT, and two MCP2515 chips sharing one SPI bus still will not keep up with two fully loaded 1 Mbit/s networks, but for protected, real world use it is the right tool.

The SparkFun CAN-Bus Shield is built around one very specific job: turning an Arduino into an in-car data logger. It uses the familiar MCP2515 and MCP2551 pair with a 10 MHz SPI link, and its standard 9 way sub-D connector is wired for an OBD-II to DB9 cable, so you can poll the ECU for coolant temperature, throttle position, vehicle speed and engine RPM. What sets it apart is everything around the CAN chips: a microSD card holder for logs, a serial LCD connector for a dash display and a header for an EM506 GPS module, which together make a GPS tagged trip logger with very little extra wiring. The shield can also be powered from the vehicle through the DB9, with a resettable fuse and reverse polarity protection. The honest downsides: the DB9 cable is not included, the Amazon listing has only a handful of ratings and low stock, and the EM506 GPS it was designed around is no longer a current part, so plan on a different GPS module.

Two nodes prove your wiring. Three nodes teach you how CAN really behaves, because only then do you see arbitration, where the lowest ID wins the bus without a collision, acceptance filters and masks doing real work, and what happens when one node goes bus off. The WWZMDiB three pack is the easiest way to get there. The boards are the same MCP2515 + TJA1050 design as our top pick, with CAN 2.0B support up to 1 Mbit/s and a 120 Ω terminator, and the bundle adds Dupont jumper wires, so you can wire all three to microcontrollers without raiding your parts drawer. The listing mentions ESP32, STM32 and Raspberry Pi, which is true in the sense that the SPI interface is universal, but remember the TJA1050 still needs 5 V. On a 3.3 V board, either power the MCP2515 side from 3.3 V with the well known trace modification or put a level shifter on MISO.

The Comidox three pack is the no frills option when you simply need more boards: spares for a classroom, one node per sensor in a small robot, or a module you are happy to solder permanently into a prototype. It is the standard MCP2515 + TJA1050 layout with CAN 2.0B at up to 1 Mbit/s, 0 to 8 byte data fields, standard, extended and remote frames, a 120 Ω terminator and a 5 V supply. Comidox is one of the few sellers that lists the mechanical dimensions, 44 × 28 mm with mounting holes on a 23 × 38 mm pattern, which helps if you are designing an enclosure or a carrier PCB. It also carries one of the larger review counts among generic modules on Amazon. Like every clone, it arrives with an 8 MHz crystal and no instructions, and the industrial temperature rating on the listing refers to the chips rather than a tested module, so treat it as a maker part rather than production hardware.

Learning CAN on an Arduino?

Start with the HiLetgo two pack. Two MCP2515 + TJA1050 boards and two Unos give you a complete, acknowledging CAN bus for the price of a lunch.

Want plug in, no jumper wires?

The Seeed CAN-Bus Shield V2 stacks on an Uno or Mega and adds a switchable OBD-II DB9 port, a TF card slot and a maintained library.

Using a Raspberry Pi?

Take the Waveshare RS485 CAN HAT. It is 3.3 V native, becomes a SocketCAN interface with one overlay line, and throws in an RS485 port.

Connecting to a vehicle or machine?

The Waveshare 2-Channel Isolated CAN HAT protects the Pi with galvanic isolation and TVS diodes, and gives you two buses for gateways and logging.

Building a car trip logger?

The SparkFun CAN-Bus Shield combines an OBD-II DB9, microSD, a serial LCD header and GPS header on one Arduino board.

Want to see arbitration and filters?

Get the WWZMDiB three pack with jumpers, or the Comidox three pack if you already have wires. Three nodes make CAN behaviour visible.

Already using an ESP32 or STM32?

Use the chip’s built in CAN (TWAI on ESP32, bxCAN or FDCAN on STM32) with a 3.3 V SN65HVD230 transceiver, and keep an MCP2515 only for an extra channel.

Can I use the MCP2515 TJA1050 module with an ESP32 or other 3.3 V board?

Yes, but not straight out of the bag. The TJA1050 needs 5 V, and on these modules the MCP2515 shares that 5 V rail, so its SO (MISO) pin outputs 5 V, above what an ESP32 or Raspberry Pi GPIO is rated for. Plenty of people get away with it for a while, but it is not a safe long term setup. The two clean fixes are a level shifter or resistor divider on MISO, or the common modification of cutting the trace so the MCP2515 runs from 3.3 V while the TJA1050 stays on 5 V. Better still, on an ESP32 skip the MCP2515 and use its built in TWAI controller with a 3.3 V SN65HVD230 transceiver.

My MCP2515 initialises but never receives anything. What is wrong?

Check these in order. First, the crystal: blue modules use 8 MHz, so pass MCP_8MHZ (or the equivalent in your library) instead of the 16 MHz default. Second, bitrate: every node must use the same rate, for example 500 kbit/s. Third, termination: with power off, measure between CAN_H and CAN_L, and you should read about 60 Ω, meaning two 120 Ω terminators in parallel. Fourth, make sure there is at least one other active node to acknowledge frames, because a lone transmitter will simply retry and pile up errors. Finally, confirm CAN_H goes to CAN_H and that all nodes share a ground reference.

Can I read my car’s data with an MCP2515 module?

On most cars built since the late 2000s, yes. The OBD-II port exposes a CAN bus on pin 6 (CAN_H) and pin 14 (CAN_L), usually at 500 kbit/s, and you can send standard OBD-II PID requests to read speed, RPM, coolant temperature and more. A shield with a DB9 OBD-II pinout, such as the Seeed or SparkFun boards, plus an OBD-II to DB9 cable makes the connection clean. Three cautions: do not enable a terminator, because the car already has two; start in listen only mode while you explore; and never transmit arbitrary frames on a vehicle you are driving. For anything beyond a bench test, an isolated interface is strongly recommended.

How do I set up an MCP2515 HAT on a Raspberry Pi?

Enable SPI, then add an overlay line to config.txt in the form dtoverlay=mcp2515-can0,oscillator=XXXXXXXX,interrupt=YY, using the crystal frequency printed on your board and the interrupt GPIO from the vendor wiki. After a reboot, bring the interface up with sudo ip link set can0 up type can bitrate 500000, install can-utils, and test with candump can0 and cansend. From Python, the python-can library talks to the same SocketCAN interface. Dual channel boards add a second overlay for can1 with its own interrupt pin.

Does the MCP2515 support CAN FD, and when should I upgrade?

No. The MCP2515 is a classic CAN 2.0B controller limited to 1 Mbit/s and 8 byte payloads, and a classic controller will actually signal errors if it sees CAN FD frames on the bus. If you need CAN FD, with up to 64 byte payloads and a faster data phase, look for boards built on the MCP2518FD or a microcontroller with an FDCAN peripheral, such as many newer STM32 parts. You should also consider moving on if you are logging a busy bus, since the MCP2515 has only two receive buffers and an SPI link that can drop frames at high load. For learning, hobby networks and most OBD-II work, the MCP2515 remains the simplest and best supported option.