Why Wait Days? Understand Your Datalog on the Spot with PullScan

You have recorded a pull, exported the CSV, and shared it for feedback. Now you are waiting—and still wondering what the log shows.

Did anything deserve attention? Where did it happen? What should you ask your tuner?

PullScan gives you a starting point while those questions are fresh. Upload your CSV, review findings alongside graph evidence, and use Fix Me to explore what to investigate next.

You can ask follow-up questions in chat, with guidance informed by reviewed real-world cases and the evidence in your log.

Here is how to move from a file full of numbers to a clearer next step.

1. Open PullScan and upload your CSV

Start with PullScan on your preferred platform:

• Android: Get PullScan on Google Play
• iPhone and iPad: Download PullScan on the App Store
• Web: Open PullScan in your browser

Upload your CSV and provide accurate vehicle information, along with relevant details about your setup, fuel, and symptoms.

You do not need to diagnose the vehicle first. Describe what happened and what you want to understand.

For example:

“I noticed a hesitation toward the end of the pull. The hardware and map are unchanged from my previous log. What do the recorded signals show around that interval?”

That gives your review a specific starting point.

If you did not notice a symptom, begin by reviewing the analysis and asking PullScan to explain its main findings.

2. Understand how PullScan analyzes your log

A CSV contains recorded channels over time. Depending on your vehicle and logger, those channels may include RPM, boost, throttle position, ignition timing, fueling, temperatures, and fuel pressure.

PullScan parses the file, identifies the logging platform and source format, and normalizes supported channels for analysis.

The analysis examines measured behavior using the information available in your file. Related signals provide context: a change in one channel becomes more useful when you can see what happened around it.

When compatible target and actual channels are present, their relationship can help explain the behavior. When an important channel is missing, the remaining telemetry may still provide useful evidence, but that limitation matters.

As you read the report, ask:

• What did the log record?
• Where did the behavior occur?
• Which signals support the finding?
• What remains uncertain?

A finding can identify a pattern without establishing its underlying cause.

3. Review a finding alongside its evidence

Start with one finding you want to understand, then inspect its supporting graph.

Look at the relevant interval and the surrounding signals. Read the explanation, confidence information, and limitations together.

Example: throttle opening decreases during a pull

Imagine a log in which throttle opening decreases during part of a pull.

This is a hypothetical example for explaining the workflow. It is not a real vehicle case, an actual PullScan result, or a transcript of a chat response.

The throttle change gives you an interval to investigate.

If accelerator position is available, did the driver lift? What did the available boost and target channels show? Did other recorded signals change around the same time?

A reduction in throttle opening is an observation. By itself, it does not establish a failed component or prove why the change occurred.

The graph helps you move from “something happened” to a focused question about the recorded behavior.

For more background, read Why Does the Throttle Close During a Pull?.

4. Choose Fix Me

For an eligible analysis, choose Fix Me from your results and follow the prompts to start or continue a session.

Complete the required vehicle information and review the participation terms when prompted. Then read the suggested next steps alongside the original finding.

Fix Me draws on reviewed real-world cases and the evidence available in your analysis. Those cases provide context for the investigation, while your own telemetry determines what can be observed in your log.

A similar symptom or pattern does not automatically mean the same cause applies to your vehicle. Differences in hardware, fuel, calibration, operating conditions, and recorded channels still matter.

Keep three questions in mind:

The next step might involve supplying missing context, reviewing another signal, or preparing a focused discussion with your tuner.

5. Ask PullScan what your log means

Inside your Fix Me session, use Ask PullScan to discuss the analysis.

The conversation stays connected to your findings and current guidance. You can ask PullScan to explain what it found, clarify uncertainty, and help you understand the next investigation step.

You do not need to know every logging term before asking a useful question. Start with the finding you want explained.

For example:

“Explain the main finding in plain language. What happened, where did it happen, and which signals support it?”

For the hypothetical throttle example, you could ask:

“What does this log show around the throttle reduction? Can the available channels distinguish driver lift from control intervention?”

Then follow up:

“What remains uncertain, and what additional information would help?”

These are example questions. PullScan’s response depends on the evidence in your analysis and its available guidance.

Connect a symptom to the recorded data

If you felt something during the pull, describe it:

“I felt a hesitation near this interval. Does the recorded behavior help explain that symptom, or is more information needed?”

Include relevant details about when it happened and your vehicle setup. Your description provides context, while the telemetry helps establish what was recorded.

Understand why a next step was suggested

Ask PullScan to connect its guidance to your log:

“Why is this next step relevant to my analysis? Which findings support it, and what would make it less applicable?”

This helps you understand the reasoning behind the suggestion and its limits.

Prepare a better question for your tuner

You can also ask:

“What should I discuss with my tuner based on this analysis, and which parts of the log should I share?”

You can then bring the specific finding, relevant interval, symptoms, and unresolved questions into that conversation.

That gives your tuner more context than sending a file with only “Does this look okay?”

Ask about the next useful observation

When you are unsure how to continue, ask:

“What context and channels would make a follow-up log useful for investigating this pattern?”

Start with one clear question. Review the answer and inspect the evidence it refers to before moving to the next question.

6. Follow up to see whether the issue changed

When you have a follow-up log, record what changed between sessions.

Relevant differences may include fuel, hardware, calibration, symptoms, and logging conditions. If several things changed together, include that context.

Continue your Fix Me session and review the comparison evidence. Ask:

“Did the earlier pattern repeat in this log?”

Or:

“Are these logs comparable enough to interpret the difference? Which changes in measured behavior matter?”

A changed graph does not automatically establish that an issue was resolved. Consider which signals changed, whether the conditions were comparable, and what remains uncertain.

Record your observed outcome when prompted, including when the result is unclear.

Our guide to comparing WOT datalogs explains why conditions matter when reviewing successive pulls.

Understand your log and take the next step

You do not need to leave your CSV unopened while waiting for someone else to review it.

Use PullScan to understand the recorded behavior and inspect the evidence. When you need help moving forward, choose Fix Me, ask your questions, and explore next steps informed by reviewed real-world cases and your analysis.

Bring that context to your tuner, and return with follow-up data when you have it.

Start with one log, one finding, and one question.

Ready to review your datalog?

• Get PullScan for Android
• Download PullScan for iPhone and iPad
• Use PullScan on the web