alexanderkeller9
Seat Cordoba incomplete system readiness after OBD2 diagnostics
Summary of the thread
A 2001 Seat Cordoba exhibited an incomplete system readiness check following an OBD2 diagnostics readout, with an error message displayed. The issue was likely due to the onboard diagnostics not being fully reset. A suggested solution was to perform a complete drive cycle, involving specific driving conditions, to reset the system readiness. After clearing the error memory and completing a drive cycle, the system readiness was restored, and the vehicle passed inspection.
Did this summary help you solve your problem?
4 comment(s)
alexanderkeller9 (community.author)
Can you elaborate on what you mean by 'complete drive cycle'? What specific conditions need to be met for the system readiness to reset? I'm concerned about the exhaust system and its readiness status for the upcoming vehicle inspection.
timsteel1
Yeah, a drive cycle is basically a set of driving conditions that the car needs to experience for the onboard diagnostics to run all its tests. It's different for every car, but usually involves a mix of city and highway driving, with specific acceleration and deceleration patterns. I didn't have the patience to figure it out myself and took it to a workshop. They reset the system readiness, which cost me 0€ since it was a quick job.
alexanderkeller9 (community.author)
Thanks for the insight. I cleared the error memory using VCDS and performed a drive cycle. The system readiness check is now complete. Vehicle inspection passed without issues. Apparently, the OBD2 diagnostics tool caused the problem.
rmh_community_comment_box_header
community_crosslink_scanner_headline
community_crosslink_scanner_intro
community_crosslink_scanner_title
community_crosslink_scanner_price
community_crosslink_rmh_headline
community_crosslink_rmh_intro
community_crosslink_rmh_title
community_crosslink_rmh_subtitle
community_crosslink_rmh_brand
SEAT
community_crosslink_rmh_model
CORDOBA
timsteel1
I had a similar issue with my Cordoba after a diagnostic check. It's probably related to the onboard diagnostics not being fully reset after the scan. Have you tried performing a complete drive cycle to see if the system readiness status clears?