After working with CAN Bus in the automotive industry for 5 years and leaving my job, I tried several existing tools on the market. Since many of them are paid, I decided to build my own project focused on both mostly UI and functionality.
Introducing NexusCAN, an open-source, project-based CAN Bus analysis application.
Development was done with Claude and Gemini.
With your sponsorships and GitHub support, much better features can be added.
The project includes features—especially in the UDS section—that cannot be physically tested right now. Because I don't currently have a UDS-capable device on hand, I haven't been able to test it thoroughly enough. However, I have been able to test features like ISO-TP using a UDS simulator. It will grow with your ideas and feedback.
What it does today
Bus analysis
- Live trace and an overwrite view with full DBC / KCD decoding: Intel and Motorola layouts, signed and float signals, cascaded multiplexers, CAN-FD 64-byte frames, J1939 PGNs
- Multi-axis signal plotter, a bit-layout matrix for every message, drag-and-drop instrument panels bound to signals
- Import and export of .blf, .asc, .trc, .log and .csv, with replay speed control
- CAN error frames decoded into readable causes (stuff, form, ACK, CRC, error-passive, bus-off)
Reverse engineering
- A bit-level heatmap that shows how often each bit toggles, for every ID
- Baseline → Action: record a few seconds of the car doing nothing, then press the button or open the door. Only the bits that moved during the action stay highlighted. Counters, checksums and sensor noise are muted automatically.
- A field classifier that spots rolling counters, checksums (XOR, SUM, CRC8 J1850 / AUTOSAR), flags and physical values
- Correlation search: pick a reference, for example an OBD-II PID like vehicle speed. It tries every start bit, length and byte order, then gives you the matching signal with its factor and offset.
- Save to DBC: found signals go into a real .dbc file, or straight into the live decoder
- Coming next: a Cheat-Engine-style Value Scan. Scan for "80 km/h", change speed, scan "increased", and repeat until only one signal is left.
Diagnostics
- UDS client, an ECU map built by functional discovery, a DID inspector, DTC reports, and a traffic view that expands every ISO-TP frame together with its P2 and STmin timing
- Passive ECU discovery that works without transmitting anything
- A visual Flow Editor for building diagnostic sequences, flashing (34/36/37) and SecurityAccess key providers. Honest note: all of this has been tested only against simulated ECUs on vcan0, not real vehicles yet.
Safety first
Every channel opens in Listen-Only. Transmitting requires an explicit, confirmed "Arm", and Stop All TX is one click away on every screen. I didn't want a tool that can accidentally spam a real vehicle bus.
Under the hood
The core is Rust, the desktop app is Tauri v2 and the UI is React. Frames are fixed 80-byte structs with no heap allocation on the receive path, and the UI updates at 60 Hz
instead of sending one message per frame. In tests it handles 50,000 fram.
Hardware
- Works now: SocketCAN on Linux, SLCAN adapters on all operating systems,mulator, and replay of recorded logs
- Written but not yet tested on real hardware: gs_usb / candleLight (CANastall needed) and PCAN-Basic
This is where I need you. If you own a CANable, PCAN, Kvaser or a UDS-capable tool, a short report ("works / doesn't work on X") would help a lot. Real-world traces are also welcome.
Try it
- Windows, Linux and macOS builds are on the Releases page
- No hardware? It runs in five minutes on a virtual CAN bus with simulateME)
GitHub: https://github.com/kadirtunc/NexusCAN
It's a v0.1 preview, so expect rough edges. Bug reports, feature ideas and criticism are all welcome. A ⭐ helps the project get seen.
Hats off to all open-source developers—respects and greetings to you all.
Thanks for all your support https://github.com/sponsors/kadirtunc