How Do I Get A Repair Code From My 201 Jetta

you guys are mistaking the edc15 "login" for the edc16 "security admission"
these are split up and different functions and are NOT the same. They should not be mistaken for one another.

(though you lot could refer to the "login lawmaking" of 12233 every bit a password)

Just to be clear... there are NO manual accommodation channels in ECDC16 similar they had in the older cars. Any required adaptations are done automatically by the ecu (also referred to as "ecu learning" past some). At that place are extra functions that are accessible through "basic settings" that act every bit "adaptations" of sorts, just you don't have the power to manually modify the value stored in the diagnostic section of retention (eeprom) as in ecd15. The ecu does information technology automatically through an internal programming routine.

However... in that location is a security layer or two acting equally a gatekeeper for sure diagnostic routines- reading/writing the ecu being among these. (IOW flashing is included in the diagnostic routines of the ECU's internal programming "instructions" ) At that place's a command sequence sent by the user tool to admission these diagnostic routines, whether information technology's to read/clear codes or identify the ecu, or read the flash or write the flash. To initialize these certain kinds of diagnostic session, the ecu responds to any request from the "tester tool" to initiate a session, with it'southward own "request" for a password. (login if yous will) In EDC16, If the incorrect password is supplied by the "tester tool", and so the ecu refuses to commencement the diagnostic session, (response = 7F) with a reason code of "wrong password", and it's "strike one". (a "counter" increments +i) Try once more with the wrong countersign, "strike two". After four failures, BAM, security lockout.

In one case security lockout becomes agile: So Fifty-fifty IF you input the correct countersign, along the 7F ("session refused" A.Chiliad.A. "negative") response, you lot will get the "reason" for refusal of access = 37 = "requiredTimeDelayNotExpired". The response cord is: 7F,27,37 where 7F is the response (negative), 27 is the request received (security admission requested), and 37 is the reason (requiredTimeDelayNotExpired)

Q-loader will display this mistake equally 01 02 which refers to where in the routine the error occurred (what footstep it happened at). Reading the device log will show the error cord of 7F,27,37 (this info is encrypted and must be sent to us for estimation)

In other words one time the lockout is triggered, in that location is a time filibuster earlier farther admission attempts tin can be made (fifty-fifty with the proper password). This lockout begins at xx minutes, then after another round of failed passwords the time doubles to twoscore minutes, and and then on, upwardly to a maximum of 255 minutes.

To reset this kind of security lockout, get out the diagnostic interface connected and "handshaked", leave the ignition fundamental on (automobile not running), with the door open, for the minimum required time. This resets the security access lockout. Usually 40 minutes does the trick. I suspect some companies similar revo may just alter the value that'due south stored in the eeprom to set the "required time" to 255 minutes every bit part of their flashing routine. This would serve every bit an constructive way to "lock" the ecu from reading for most intents and purposes. The value is in the eeprom not the wink, and then it won't affect the actual tuning being done, just prevent hereafter admission to that particular grouping of diagnostic routines. IOW a somewhat melancholia "read protection". (but non the only way... )

Usually 40 minutes does the flim-flam. But upwardly to 4 hours fifteen minutes may be required. Then the correct password can be entered to reset security access- and this password is 12233 if using VCDS (through the "security access" subroutine" or else simply using the flash tool (which inputs the correct access code automatically)

Promise this clears some things up