Describe the symptom precisely
Record engine speed, gear, load, temperature, fuel, drive mode and whether the condition is cold, warm or intermittent. Separate drivability, power, smoke, noise, diagnostic and programming concerns.
Avoid descriptions such as not good or needs more power without evidence. A repeatable test condition helps distinguish calibration from hardware, adaptation or environmental causes.
Collect the right channels
Choose logging channels relevant to the concern: requested and actual boost, rail pressure, lambda, ignition correction, air mass, torque request, limiters, temperatures and transmission intervention where supported.
More channels are not always better because low sample rate can hide an event. Use the tool and platform guidance, log safely and avoid public-road testing that creates risk.
Keep file history intact
Attach the exact file currently installed and identify which revision it is. Do not rename unrelated files into the operation or make undocumented third-party edits between tests.
AllChip stores the original, calibrated result and subsequent revisions separately so the workshop and engineer can refer to the same version.
Validate one change at a time
After a revision, repeat the same controlled test and compare results. If hardware, fuel or conditions also changed, record that difference so the comparison remains meaningful.
Use the secure file workflow to keep logs, messages and revisions attached to the operation instead of spreading them across unrelated chats.