|
Title: Can't read from ECU 2001 VR6 Jetta 021906018R Post by: kitson12 on February 11, 2019, 09:32:19 AM Hey everyone, I'm having a few issues reading the ECU in my car. I swapped a VR6 into my Golf, the ECU comes from an '01 Jetta. The immobilizer is defeated, car runs amazing, I'm just trying to code out my engine light for emissions related stuff. I run into some weird problems when I try to read or write flash to the ECU. The same errors come up no matter what I try. I can see that its reporting security access is not supported and from what I've read that has to do with the immo still being on when trying to bench flash but my immo is completely defeated already. Here is the log from my recent session. Hopefully I can be steered in the right direction! Thanks!
Title: Re: Can't read from ECU 2001 VR6 Jetta 021906018R Post by: kitson12 on February 11, 2019, 09:35:50 AM 11-Feb-2019 11:10:57.957: USER: 0x9C, Calibration Equiment Software Number: 0x80010100
11-Feb-2019 11:10:57.982: LOG: Restoring Windows sleep mode. 11-Feb-2019 11:11:00.102: LOG: Sent message with service ID TesterPresent 11-Feb-2019 11:11:00.126: LOG: Received message with service ID: TesterPresentPositiveReponse 11-Feb-2019 11:11:02.604: LOG: Sent message with service ID TesterPresent 11-Feb-2019 11:11:02.624: LOG: Received message with service ID: TesterPresentPositiveReponse 11-Feb-2019 11:11:05.106: LOG: Sent message with service ID TesterPresent 11-Feb-2019 11:11:05.135: LOG: Received message with service ID: TesterPresentPositiveReponse 11-Feb-2019 11:11:07.608: LOG: Sent message with service ID TesterPresent 11-Feb-2019 11:11:07.632: LOG: Received message with service ID: TesterPresentPositiveReponse 11-Feb-2019 11:11:10.112: LOG: Sent message with service ID TesterPresent 11-Feb-2019 11:11:10.131: LOG: Received message with service ID: TesterPresentPositiveReponse 11-Feb-2019 11:11:12.613: LOG: Sent message with service ID TesterPresent 11-Feb-2019 11:11:12.638: LOG: Received message with service ID: TesterPresentPositiveReponse 11-Feb-2019 11:11:15.117: LOG: Sent message with service ID TesterPresent 11-Feb-2019 11:11:15.139: LOG: Received message with service ID: TesterPresentPositiveReponse 11-Feb-2019 11:11:17.620: LOG: Sent message with service ID TesterPresent 11-Feb-2019 11:11:17.647: LOG: Received message with service ID: TesterPresentPositiveReponse 11-Feb-2019 11:11:20.122: LOG: Sent message with service ID TesterPresent 11-Feb-2019 11:11:20.145: LOG: Received message with service ID: TesterPresentPositiveReponse 11-Feb-2019 11:11:22.624: LOG: Sent message with service ID TesterPresent 11-Feb-2019 11:11:22.643: LOG: Received message with service ID: TesterPresentPositiveReponse 11-Feb-2019 11:11:24.396: LOG: User Prompt - Title: Confirm Full Write ECU Flash Memory Message: If you are ready to write, confirm the following things: 11-Feb-2019 11:11:24.425: LOG: Disabling Windows sleep mode. 11-Feb-2019 11:11:24.436: USER: Writing ECU flash memory. 11-Feb-2019 11:11:24.486: LOG: Reading ECU identification option: 0x9C 11-Feb-2019 11:11:24.497: LOG: Sent message with service ID ReadECUIdentification 11-Feb-2019 11:11:24.518: LOG: Received message with service ID: ReadECUIdentificationPositiveResponse 11-Feb-2019 11:11:24.537: LOG: Read ECU identification option: 0x9C 11-Feb-2019 11:11:24.552: LOG: Successfully read ECU identification information 11-Feb-2019 11:11:24.593: USER: ECU reports programming session preconditions have been met. 11-Feb-2019 11:11:24.605: USER: Negotiating communication timings. 11-Feb-2019 11:11:24.617: LOG: Reading current communication timings. 11-Feb-2019 11:11:24.631: LOG: Sent message with service ID AccessTimingParameters 11-Feb-2019 11:11:24.667: LOG: Received message with service ID: AccessTimingParametersPositiveResponse 11-Feb-2019 11:11:24.679: LOG: Setting communication timing to defaults. 11-Feb-2019 11:11:24.691: LOG: Sent message with service ID AccessTimingParameters 11-Feb-2019 11:11:24.724: LOG: Received message with service ID: AccessTimingParametersPositiveResponse 11-Feb-2019 11:11:24.731: LOG: Reading current communication timings. 11-Feb-2019 11:11:24.743: LOG: Sent message with service ID AccessTimingParameters 11-Feb-2019 11:11:24.798: LOG: Received message with service ID: AccessTimingParametersPositiveResponse 11-Feb-2019 11:11:24.808: USER: Successfully changed to new communication timings. 11-Feb-2019 11:11:24.822: USER: Requesting security access. 11-Feb-2019 11:11:24.834: LOG: Sent message with service ID SecurityAccess 11-Feb-2019 11:11:24.863: LOG: Received message with service ID: NegativeResponse 11-Feb-2019 11:11:24.874: LOG: Received negative response for service ID: SecurityAccess, with response code: ServiceNotSupported 11-Feb-2019 11:11:24.892: USER: ECU reports that security access is not supported. 11-Feb-2019 11:11:24.901: LOG: Starting ProgrammingSession diagnostic session with 10400 baud rate. 11-Feb-2019 11:11:24.912: USER: Starting diagnostic session. 11-Feb-2019 11:11:24.926: LOG: Sent message with service ID StartDiagnosticSession 11-Feb-2019 11:11:24.975: LOG: Received message with service ID: NegativeResponse 11-Feb-2019 11:11:24.986: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending 11-Feb-2019 11:11:25.014: LOG: Received message with service ID: NegativeResponse 11-Feb-2019 11:11:25.026: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending 11-Feb-2019 11:11:25.053: LOG: Received message with service ID: NegativeResponse 11-Feb-2019 11:11:25.062: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending 11-Feb-2019 11:11:25.088: LOG: Received message with service ID: NegativeResponse 11-Feb-2019 11:11:25.098: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending 11-Feb-2019 11:11:25.128: LOG: Received message with service ID: NegativeResponse 11-Feb-2019 11:11:25.137: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending 11-Feb-2019 11:11:25.162: LOG: Received message with service ID: StartDiagnosticSessionPositiveResponse 11-Feb-2019 11:11:25.173: LOG: Setting communication timings to defaults. 11-Feb-2019 11:11:25.183: LOG: Set timing parameters to defaults. 11-Feb-2019 11:11:25.192: LOG: Changed diagnostic session type to: ProgrammingSession 11-Feb-2019 11:11:25.201: LOG: ECU requesting specific baud rate: 89600 11-Feb-2019 11:11:25.210: USER: Successfully started diagnostic session. 11-Feb-2019 11:11:25.219: USER: Negotiating communication timings. 11-Feb-2019 11:11:25.229: LOG: Reading current communication timings. 11-Feb-2019 11:11:25.280: LOG: Sent message with service ID AccessTimingParameters 11-Feb-2019 11:11:27.282: LOG: Message received no replies. 11-Feb-2019 11:11:27.302: LOG: Resending message. Send attempts: 2 11-Feb-2019 11:11:27.351: LOG: Sent message with service ID AccessTimingParameters 11-Feb-2019 11:11:29.355: LOG: Message received no replies. 11-Feb-2019 11:11:29.364: LOG: Resending message. Send attempts: 3 11-Feb-2019 11:11:29.417: LOG: Sent message with service ID AccessTimingParameters 11-Feb-2019 11:11:31.421: LOG: Message received no replies. 11-Feb-2019 11:11:31.430: LOG: Failed to send message 3 times, message send failed. 11-Feb-2019 11:11:31.438: LOG: Did not receive any replies to message. 11-Feb-2019 11:11:31.936: LOG: Sent message with service ID TesterPresent 11-Feb-2019 11:11:33.941: LOG: Message received no replies. 11-Feb-2019 11:11:33.950: LOG: Resending message. Send attempts: 2 11-Feb-2019 11:11:33.974: LOG: Sent message with service ID TesterPresent 11-Feb-2019 11:11:35.978: LOG: Message received no replies. 11-Feb-2019 11:11:35.987: LOG: Resending message. Send attempts: 3 11-Feb-2019 11:11:36.017: LOG: Sent message with service ID TesterPresent 11-Feb-2019 11:11:38.020: LOG: Message received no replies. 11-Feb-2019 11:11:38.031: LOG: Failed to send message 3 times, message send failed. 11-Feb-2019 11:11:38.053: USER: Disconnecting because no response was received for the Tester Present message. 11-Feb-2019 11:11:38.062: USER: Disconnected 11-Feb-2019 11:11:38.112: LOG: Closing FTDI device. 11-Feb-2019 11:11:38.174: LOG: Send receive thread now terminated. Title: Re: Can't read from ECU 2001 VR6 Jetta 021906018R Post by: nyet on February 11, 2019, 09:50:56 AM Is it stock?
Title: Re: Can't read from ECU 2001 VR6 Jetta 021906018R Post by: kitson12 on February 11, 2019, 09:52:34 AM As far as I know, yes. I only had someone defeat the immo on it when I bought the ECU.
Title: Re: Can't read from ECU 2001 VR6 Jetta 021906018R Post by: dilly on February 11, 2019, 04:21:57 PM As far as I know, yes. I only had someone defeat the immo on it when I bought the ECU. i can't find it but there is a topic on here about the pin 121 issuei believe you apply +12v to pin 121 on the bench and read and write all you want at least thats how it is with my vr ecu (018M) Title: Re: Re: Can't read from ECU 2001 VR6 Jetta 021906018R Post by: kitson12 on February 11, 2019, 04:26:44 PM i can't find it but there is a topic on here about the pin 121 issue Ok awesome, I wasn't sure if that applied to my ECU, I assumed it was a ME7.5 issue only.i believe you apply +12v to pin 121 on the bench and read and write all you want at least thats how it is with my vr ecu (018M) Sent from my Pixel 3 XL using Tapatalk Title: Re: Re: Can't read from ECU 2001 VR6 Jetta 021906018R Post by: dilly on February 12, 2019, 10:49:13 PM Ok awesome, I wasn't sure if that applied to my ECU, I assumed it was a ME7.5 issue only. Sent from my Pixel 3 XL using Tapatalk actually don't take my word for it i tried it again and it didn't work for me on my me7.1 018M vr ecu have to search again on how or if the vr me7.1 can be obd bench read. i may have seen something about it only being able to boot mode. but i am not 100% sure someone who knows exactly may chime in for you |