I’ve been working on a CAN bus analyzer and wanted to try a different approach to signal identification.

Instead of manually scanning graphs and guessing which byte corresponds to a real-world action, this workflow is:

1. record a CAN log

2. mark an event (like brake press)

3. run correlation

4. see which CAN IDs / bytes reacted

5. jump directly into graph + byte/bit inspection

So instead of:

“this might be brake…”

you can do:

“press brake → see what actually changed”

(video below)

Curious if anyone here has tried similar approaches or has a better workflow.