1. Define the event
Write a single question, such as why idle speed falls when an electrical load is switched on. Describe the temperature, gear, load and sequence that produces it. A long recording without a marked event is harder to review than a short trace with a clear trigger and a timestamped note.
2. Choose channels that explain the sequence
Start with RPM, load or MAP, throttle position, temperatures and supply voltage where available. Add the command and feedback relevant to the symptom. Include status and fault channels for important sensors. Avoid selecting every possible channel without considering storage, sample rate and what the ECU actually supports.
3. Match rate and recording method
Fast events and slow temperature changes do not need identical sampling. Review laptop logging and internal logging separately because their capabilities can differ. The Haltech Elite article is a useful concrete example, but its channel and storage limits should not be copied to Platinum, Link or MaxxECU hardware.
4. Keep the calibration context
Save the map used for the log, ECU firmware, software version, channel units and any recent changes. Lambda and displayed AFR are not interchangeable without the selected fuel conversion. Mark missing or invalid readings rather than presenting them as real measurements. Keep the original log before making an edited export.
5. Package the evidence
Send the original file, event timestamp, a concise symptom description and the matching map through the agreed support channel. Request a controlled test plan before repeating a fault under load. A road test should not require the driver to operate a laptop, and a log review is not a substitute for checking the installation.
Official references
Editorial summaries; use the matching manufacturer manual for actual wiring and calibration.