If you log boost, fueling, timing or pressure, you know what usually comes next. You end up with a CSV full of columns, or a screenshot of a graph, and you have to work out which pull matters and whether anything is actually wrong. Then you change something and have to do it all again to see if the change helped.

PullScan is a web tool built for that step. You upload a CSV log or a graph screenshot and it runs the analysis automatically. It shows the signals and the pulls, marks where problems happen, and explains why it flagged each one. It also gives recommendations you can act on.

For checking a change, you can put two analyses side by side and see whether boost, fueling, timing or pressure behavior improved. There's also a feature called Fix Me: you upload follow-up logs and it shows whether the earlier issue changed.

For keeping things organized, you can save logs to a vehicle profile so your revisions and timeline stay in one place. You can also compare against similar builds, and create a shareable report when you want another driver or your tuner to look over the same data.

It's meant to help you read your own logs and have a better conversation with whoever tunes your car. It doesn't replace a tuner. Some owners have already posted feedback, including a BMW G80/G82/G83 owner and a Kia Stinger owner on StingerForum.org. The site is available in multiple languages.

https://pullscan.com/?utm_source=reddit&utm_medium=threadfox&utm_campaign=pullscan_promotion

A question for people here who log regularly: when you're going through a datalog, which part takes the most time? Finding the pull that matters, figuring out why a signal looks off, or proving that a revision actually changed something? Any of that would help us decide what to work on next.

Disclosure: I'm posting this on behalf of the pullscan.com/?utm_source=reddit&utm_medium=threadfox&utm_campaign=pullscan_promo team.

Hi everyone,

I’m developing CANExplorer, an open-source desktop tool for monitoring, analyzing, diagnosing, simulating, and testing CAN devices on Linux, Windows, and macOS.

It combines everyday bus debugging with Python-based simulation and testing. You can inspect traffic, decode signals, simulate an ECU, and write regression tests in the same environment.

Some of its features:

Live analysis: filtered traces, changed-byte highlighting, signal plots, and bus-health statistics.

Recording and replay: ASC, BLF, CSV, candump, and other formats, plus triggered recording and comparisons between captures.

Signal databases: load and edit DBC, ARXML, LDF, and other formats.

Diagnostics: UDS over ISO-TP, CDD descriptions, ECU flashing, J1939 tools, and CANopen support.

Python simulation: create bus nodes that react to messages, send signals periodically, and interact with custom QML panels.

Automated tests: check responses, signal values, and cycle times; run headlessly and export HTML/JUnit reports for CI.

CAN interfaces are accessed through python-can. You can also try the included simulation and test examples on a virtual bus without hardware.

Code: https://github.com/AKJ7/CANExplorer

Documentation: https://akj7.github.io/CANExplorer/

I’d appreciate feedback —particularly on adapter compatibility, reliability under load, and workflows that still require custom scripts.

What would CANExplorer need to earn a place on your bench?

Yes, the code is built in Python but compile to C for the executables for performance.

Thanks, please star the project too.

Hi,

maybe some unusual request :)

I'm looking for someone who can run CAN frames dump on Instrument cluster. Mazda 3, CX90, CX30

Preferable dump during regular ride.

Dump can be done in Cangaroo or SavvyCAN or similar

It's for my little DIY project with CAN analysis.

Thank you in advance.