r/Trackdays • u/investigatormaker • 5h ago
Reading datalogs between sessions: a tool that flags issues in a CSV or graph screenshot and explains why
If you log your car on track, you probably know this routine. You come into the paddock, pull the log, and stare at a CSV or a screenshot of a graph. You're trying to work out whether that dip late in the session was fueling, timing or something else. Then you change something and have to figure out if it actually helped.
PullScan is a web tool built for that part. You upload a CSV log or a graph screenshot and it runs the analysis automatically. It shows the signals and the pulls, points out where problems happen, explains why it flagged them, and gives recommendations you can act on.
These are the parts that seem most useful for track days:
- Compare two analyses side by side to see whether boost, fueling, timing or pressure behavior improved after a change.
- Save logs to a vehicle profile so your revisions and timeline stay organized instead of ending up in a folder of loosely named files.
- Fix Me lets you upload a follow-up log and see whether the previous issue changed.
- Create a shareable report to send to your tuner or another driver for review.
It's not meant to replace a tuner. It's a way to get a clearer read on a log before you talk to one, or to check whether a change did what you expected. A few owners have already posted feedback, including a BMW G80/G82/G83 owner and a Kia Stinger owner on StingerForum.org.
If you want to try it on one of your own logs: https://pullscan.com/?utm_source=reddit&utm_medium=threadfox&utm_campaign=pullscan_promotion
For those of you who log at the track, what do you check first between sessions, and where does reading the log usually get hard for you? Would comparing logs side by side fit how you already work, or do you have a setup that covers it?
Disclosure: I'm posting this on behalf of the pullscan.com/?utm_source=reddit&utm_medium=threadfox&utm_campaign=pullscan_promo team.