u/HotWelcomeA

Image 1 — I got tired of dragging a laptop around just to debug LIN, so I built my own standalone analyzer.
Image 2 — I got tired of dragging a laptop around just to debug LIN, so I built my own standalone analyzer.

I got tired of dragging a laptop around just to debug LIN, so I built my own standalone analyzer.

Hi everyone,

I work with LIN almost every day.

The company tool I had was expensive, bulky, and every single job meant carrying around a laptop just to sniff a few frames. If I was working under a dashboard or in a cramped space, it was even worse.

Eventually I got annoyed enough that I started building something for myself.

The original goal was actually pretty small:

• power it on

• connect LIN

• immediately see frames

• no laptop required

Then feature creep happened.

I kept adding things that solved problems I ran into at work:

auto baud detection

master/slave simulation

duplicate frame filtering

PID filtering

Bluetooth notifications so I could walk away from the bench

buzzer because I got tired of staring at a screen waiting for something to happen

Eventually it turned into a complete standalone LIN analyzer.

I even ended up making an enclosure and writing documentation because coworkers kept asking to borrow it.

I'm honestly curious whether other people working with LIN would actually find something like this useful.

If you use LIN regularly:

What's the most annoying part of your workflow?

If anyone's interested, I can share more photos and documentation.

u/HotWelcomeA — 3 days ago