Record a ride log people can help you read
Choose the channels that match your question and provide enough context for a fair comparison.
Choose channels for the symptom
Scroll across to see all columns.
| What you’re looking at | Useful channels, when available |
|---|---|
| Throttle response | Time, RPM, gear, rider throttle request, actual throttle position, and engine load. |
| Fueling | Time, RPM, load, mixture target, measured lambda or AFR, fuel corrections, and closed-loop status. |
| Timing and knock | Time, RPM, load, commanded or delivered spark, cylinder-specific knock retard, and temperature. |
Names and units differ by tool and ECU. If you’re unsure what a channel represents, include its original header and units. A shorter set of relevant channels is often easier to interpret than every channel the logger offers.
Make the comparison fair
Use similar engine temperature, gear, fuel, and operating conditions. Record the tune version and the part or setting changed. If you need repeatable high-load testing, use a dyno or a controlled facility.
Mark the time where the symptom happened. Keep a few seconds on either side so someone can see how you entered and left the condition. Keep the original file if you trim a copy for sharing.
Include enough context in your forum post
- Bike, parts, fuel, tuning tool, and calibration version.
- What the bike did and the timestamp where it happened.
- A CSV or the original log format, along with a screenshot if it helps point out the event.
- What you want help deciding, such as which channels to compare on a follow-up ride.