Loading 3D model… large boards can take a moment.
This project is meant to help visualize messages on a CAN bus, with an affordable and open-source solution. We provide the design and firmware files for an affordable hardware solution (we were able to manufacture it for less than INR 2000).
Key features:
Please see the README files in each folder of this repository for detailed instructions on how to use the hardware and software.
Please see the manual for further guidance.
Our hardware uses an ESP32-S3 microcontroller and an MCP2561 CAN transceiver to communicate with the CAN bus. We use the on-board USB-to-UART converter to communicate with the computer.
The firmware is written in C++ using the ESP-IDF framework, and is provided as open-source software in this repository.
The GUI software is written in Python using the Tkinter library and matplotlib for plotting. We use to parse the CAN messages. The GUI software is also provided as open-source .
It is expected that the user provides the CAN database file (DBC) to tell our software how to interpret the messages on the CAN bus.
We chose to use an ESP32-S3 microcontroller for the following reasons:
ESP32-S3 DevKitC 1 was chosen. The additional USB-OTG port allows us the possibility of upgrades later down the line.
Datasheets:
Let us first review the status, features, and drawbacks of each transceiver we considered.
| Part | Status | Fastest CAN version | Cross-compatible footprint |
|---|---|---|---|
| MCP2551 | EOL (end of life) | CAN 2.0 classic CAN | None |
| MCP2561 | EOL (end of life) | CAN 2.0 classic CAN | with MCP2561FD |
| MCP2561FD | Active | CAN FD | with MCP2561 |
Most of our testing was done with the MCP2551, which cannot be considered for new designs. We wanted to choose the MCP2561FD, however it is often not in stock. Finally, the MCP2561 is a good compromise, as it is still in stock and can be replaced by the MCP2561FD in the future.
MCP2561 was chosen, with the possibility of upgrading to MCP2561FD in the future.
Datasheets:
Migration guide:
Rs pin (normal, standby, internal slope control), and the MCP2561FD has 2 modes only (normal, standby).menuconfig of IDF.Internal UART0 was chosen for now. This to ensure we can quickly develop the device without introducing additional complications.
Datasheets:
For real-time plotting, a fast framework like PyQtGraph and PyQt is recommended. However, we chose to use matplotlib and Tkinter for the GUI software. This is because it is easier to use and has a lower learning curve.
We will consider using PyQtGraph and PyQt in the future if we need to increase the sampling rate.
We chose to use an SQLite database for logging. This allows us to use the Python standard library to interact with the database. Moreover, the database exists as a file, which means our users do not need to install a database server.
This work was published in HardwareX, available at DOI 10.1016/j.ohx.2026.e00743.
If you use this in your work, please cite our paper:
@article{can_daq,
title = {CAN-DAQ: An open-source, cost-effective data capture device and software for automotive research},
journal = {HardwareX},
volume = {25},
pages = {e00743},
year = {2026},
issn = {2468-0672},
doi = {https://doi.org/10.1016/j.ohx.2026.e00743},
url = {https://www.sciencedirect.com/science/article/pii/S2468067226000039},
author = {Anuj Verma and Chandram Millon Dutta and Aritra Ghosh and Sakshin M. Kanchibail and Sneha Harish and Rishvanth S.K. and Shaurya Chandra and Siddharth Das and Selvakumar K.},
keywords = {Automotive, Controller Area Network (CAN), Data acquisition (DAQ), CAN database (DBC), Real-time graphing, Database management},
}
No comments yet. Be the first to ask about this board.