Preserve the source file
Keep the original and problematic version separate.
TROUBLESHOOTING
Analyze jerking after chiptuning
Understand the technical context, compare source files and review changes in a traceable Suite project.
TECHNICAL CONTEXT
What matters for this topic.
Note the issue, timing, fault codes and whether it started after a file, test drive or hardware change.
This page focuses on the symptom itself and which details are needed for clear classification.
One map value is rarely the full cause. Limiters, driver wish and the air system often work against each other.
ECU-JOBS SUITE
How the Suite supports the workflow.
Compare changes
Review maps, axes and binary changes against the original.
Create a new version
Store corrections separately without overwriting the original.
NEXT STEPS
Put technical knowledge into practice.
Create a project from the original, check available detection and Solutions, and edit changes as a separate version.