Highlights
GCAN came from a practical need: when embedded systems start talking over CAN, debugging gets much easier if the team has a tool that is fast to operate and tailored to its own workflow.
I used a Raspberry Pi with MCP2515 CAN hardware and built a PySide6 interface that could monitor, decode, record, and export data. The point was not just logging for logging's sake. The point was to give engineers a tool that makes fault analysis and validation faster during live testing.
Why this project is useful
It sits at the intersection of embedded systems and product-minded tooling. I was not only dealing with frames on a bus, but also designing the operator experience:
- what the user sees first
- how quickly logging starts
- how captured data is retained
- how future features can fit without a rewrite
That blend of systems understanding and usability is something I want to keep building on.