Driveability changes after a CVT update: distinguish new calibration behaviour from a fault
A change noticed after programming deserves documentation, but timing alone does not establish a defective update. The actual calibration, campaign/remedy history and current symptoms must be compared before resetting or replacing the transmission.
Obtain the work record
Record VIN/market, transaxle identity, old/new calibration if available and exactly what was completed. A historical JSD reference applies only to eligible vehicles and should not be used as a universal explanation for all E170 CVTs.
Describe the change: ratio behaviour, engagement delay, judder or engine-speed fluctuation are not the same complaint. Save current codes before further resets.
Compare command with achieved operation
A workshop should assess relevant engine/transmission data under the original condition and confirm the specified post-programming procedures were completed. A required learning/check sequence is not evidence that every symptom will disappear with mileage.
If the applicable remedy also required hardware inspection, establish that it was completed rather than treating software installation as the entire job. If the campaign is inapplicable, follow the correct local transaxle diagnosis instead.
Correct demonstrated faults, not the chronology alone
A supply/programming completion issue, an installation/service error and an internal control/mechanical fault need different evidence. Avoid unofficial rollback software or repeated adaptation clears that erase useful comparisons.
If operation is within the verified expected behaviour but feels different, explain the specific observation and test result. If it is abnormal, record the failing state rather than dismissing it as learning indefinitely.
Outcome & verification
Verify the original engagement/ratio condition with the correct calibration and required procedures, and confirm no renewed relevant fault. A campaign entry marked complete does not by itself assess every current driveability complaint.
Community discussion
Owner experiences, questions and other possible solutions.
No owner experiences yet. Share what was checked and what happened.
Sign in to share your experienceHelpful votes reflect community experience. Repair outcomes are self-reported.