|
Title: Hard time connecting, log inside Post by: ddillenger on October 13, 2012, 09:40:41 AM Car is a 2001 a6 2.7t with a manual trans, It does have an immobilizer. Original ecu is in the car, I can connect with vcds, vag commander, read codes, etc, but when I attempt to read the flash memory with nefmoto it fails. When it does read, It never finishes. The furthest it got was 36 percent before the "read failed" pops up. Most of the time it gives an error saying security access was rejected, or not supported? When it does read, it says security access granted. Immobilizer?
13/Oct/2012 12:10:27.984: USER: 100% complete. 13/Oct/2012 12:10:28.062: USER: Restoring Windows sleep mode. 13/Oct/2012 12:10:29.046: LOG: Message received no replies. 13/Oct/2012 12:10:29.046: LOG: Resending message. Send attempts: 2 13/Oct/2012 12:10:29.062: LOG: Sent message with service ID TesterPresent 13/Oct/2012 12:10:31.078: LOG: Message received no replies. 13/Oct/2012 12:10:31.078: LOG: Resending message. Send attempts: 3 13/Oct/2012 12:10:31.093: LOG: Sent message with service ID TesterPresent 13/Oct/2012 12:10:33.062: LOG: User Prompt - Title: Confirm Full Read ECU Flash Memory Message: If you are ready to read, confirm the following things: 1) You have loaded a valid memory layout for the ECU. 2) The engine is not running. Note: Some non-standard flash memory chips may prevent reading the flash memory. Click OK to confirm, otherwise Cancel. Result: OK 13/Oct/2012 12:10:33.062: USER: Disabling Windows sleep mode. 13/Oct/2012 12:10:33.109: LOG: Message received no replies. 13/Oct/2012 12:10:33.109: LOG: Failed to send message 3 times, message send failed. 13/Oct/2012 12:10:33.109: USER: Disconnecting because no response was received for the Tester Present message. 13/Oct/2012 12:10:33.125: USER: Disconnected 13/Oct/2012 12:10:33.218: USER: Reading ECU flash memory. 13/Oct/2012 12:10:33.218: USER: Reading ECU flash memory failed. 13/Oct/2012 12:10:33.468: LOG: Closing FTDI device. 13/Oct/2012 12:10:33.484: LOG: Send receive thread now terminated. 13/Oct/2012 12:10:34.515: LOG: User Prompt - Title: Reading ECU Flash Memory Complete Message: Reading ECU flash memory failed. Result: OK 13/Oct/2012 12:10:34.515: USER: 100% complete. 13/Oct/2012 12:10:34.562: USER: Restoring Windows sleep mode. 13/Oct/2012 12:10:41.343: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F 13/Oct/2012 12:10:41.343: USER: Switching to KWP2000 session. 13/Oct/2012 12:10:41.593: LOG: Opened FTDI device. 13/Oct/2012 12:10:41.593: LOG: FTDI device info - Description: USB <-> Serial Serial Number: Device Type: FT_DEVICE_BM ID: 0x4036001 Device Flags: 0x0 13/Oct/2012 12:10:41.593: LOG: FTDI ChipID DLL is loaded, checking chip ID... 13/Oct/2012 12:10:41.593: LOG: Unable to read FTDI device chip ID 13/Oct/2012 12:10:41.640: USER: Validated FTDI device is in dumb mode. 13/Oct/2012 12:10:41.890: LOG: Starting send receive thread. 13/Oct/2012 12:10:41.890: LOG: Send receive thread now started. 13/Oct/2012 12:10:41.890: USER: Disconnected 13/Oct/2012 12:10:42.125: LOG: Setting communication timings to defaults. 13/Oct/2012 12:10:42.125: LOG: Changed diagnostic session type to: InternalUndefined 13/Oct/2012 12:10:42.156: LOG: Setting communication timings to defaults. 13/Oct/2012 12:10:42.156: USER: Connecting... 13/Oct/2012 12:10:42.671: LOG: Setting communication timings to defaults. 13/Oct/2012 12:10:42.687: USER: Starting slow init connection. 13/Oct/2012 12:10:45.296: USER: Connecting to address 0x01. 13/Oct/2012 12:10:47.468: USER: Slow init succeeded. 13/Oct/2012 12:10:47.468: LOG: Setting Address: 0x01 KeyByte1: 0x01 KeyByte2: 0x0A 13/Oct/2012 12:10:47.468: USER: Switching to KWP1281 session. 13/Oct/2012 12:10:47.765: LOG: KWP1281 read block 13/Oct/2012 12:10:47.828: LOG: KWP1281 sent block 13/Oct/2012 12:10:47.968: LOG: KWP1281 read block 13/Oct/2012 12:10:48.031: LOG: KWP1281 sent block 13/Oct/2012 12:10:48.203: LOG: KWP1281 read block 13/Oct/2012 12:10:48.265: LOG: KWP1281 sent block 13/Oct/2012 12:10:48.375: LOG: KWP1281 read block 13/Oct/2012 12:10:48.453: LOG: KWP1281 sent block 13/Oct/2012 12:10:48.484: LOG: KWP1281 read block 13/Oct/2012 12:10:48.546: LOG: KWP1281 sent block 13/Oct/2012 12:10:48.546: USER: KWP1281 connect info: THIS-IS-THE-RAM-PROGRAM- 13/Oct/2012 12:10:50.046: USER: Connecting to address 0x01. 13/Oct/2012 12:10:52.265: USER: Slow init succeeded. 13/Oct/2012 12:10:52.265: LOG: Setting Address: 0x01 KeyByte1: 0x6F KeyByte2: 0x0F 13/Oct/2012 12:10:52.265: USER: Switching to KWP2000 session. 13/Oct/2012 12:10:52.265: USER: Connected 13/Oct/2012 12:10:54.843: LOG: Sent message with service ID TesterPresent 13/Oct/2012 12:10:54.890: LOG: Received message with service ID: TesterPresentPositiveReponse 13/Oct/2012 12:10:57.375: LOG: Sent message with service ID TesterPresent 13/Oct/2012 12:10:57.421: LOG: Received message with service ID: TesterPresentPositiveReponse 13/Oct/2012 12:10:58.250: LOG: User Prompt - Title: Confirm Full Read ECU Flash Memory Message: If you are ready to read, confirm the following things: 1) You have loaded a valid memory layout for the ECU. 2) The engine is not running. Note: Some non-standard flash memory chips may prevent reading the flash memory. Click OK to confirm, otherwise Cancel. Result: OK 13/Oct/2012 12:10:58.250: USER: Disabling Windows sleep mode. 13/Oct/2012 12:10:58.468: USER: Reading ECU flash memory. 13/Oct/2012 12:10:58.765: LOG: Reading ECU identification option: 0x9C 13/Oct/2012 12:10:58.796: LOG: Sent message with service ID ReadECUIdentification 13/Oct/2012 12:10:58.843: LOG: Received message with service ID: ReadECUIdentificationPositiveResponse 13/Oct/2012 12:10:58.843: LOG: Read ECU identification option: 0x9C 13/Oct/2012 12:10:58.843: LOG: Successfully read ECU identification information 13/Oct/2012 12:10:58.859: USER: ECU reports programming session preconditions have been met. 13/Oct/2012 12:10:58.859: USER: Negotiating communication timings. 13/Oct/2012 12:10:58.875: LOG: Reading current communication timings. 13/Oct/2012 12:10:58.937: LOG: Sent message with service ID AccessTimingParameters 13/Oct/2012 12:10:59.000: LOG: Received message with service ID: NegativeResponse 13/Oct/2012 12:10:59.000: LOG: Received negative response for service ID: AccessTimingParameters, with response code: ServiceNotSupported 13/Oct/2012 12:10:59.000: USER: Timing negotiation failed. Communication timings are unchanged. 13/Oct/2012 12:10:59.015: USER: Requesting security access. 13/Oct/2012 12:10:59.046: LOG: Sent message with service ID SecurityAccess 13/Oct/2012 12:10:59.093: LOG: Received message with service ID: NegativeResponse 13/Oct/2012 12:10:59.093: LOG: Received negative response for service ID: SecurityAccess, with response code: ServiceNotSupported 13/Oct/2012 12:10:59.093: USER: ECU reports that security access is not supported. 13/Oct/2012 12:10:59.093: LOG: Starting ProgrammingSession diagnostic session with 124800 baud rate. 13/Oct/2012 12:10:59.093: USER: Starting diagnostic session. 13/Oct/2012 12:10:59.125: LOG: Sent message with service ID StartDiagnosticSession 13/Oct/2012 12:10:59.187: LOG: Received message with service ID: StartDiagnosticSessionPositiveResponse 13/Oct/2012 12:10:59.187: LOG: Setting communication timings to defaults. 13/Oct/2012 12:10:59.203: LOG: Changed diagnostic session type to: ProgrammingSession 13/Oct/2012 12:10:59.218: LOG: ECU requesting specific baud rate: 124800 13/Oct/2012 12:10:59.218: USER: Successfully started diagnostic session. 13/Oct/2012 12:10:59.218: USER: Negotiating communication timings. 13/Oct/2012 12:10:59.218: LOG: Reading current communication timings. 13/Oct/2012 12:10:59.296: LOG: Sent message with service ID AccessTimingParameters 13/Oct/2012 12:11:01.312: LOG: Message received no replies. 13/Oct/2012 12:11:01.312: LOG: Resending message. Send attempts: 2 13/Oct/2012 12:11:01.359: LOG: Sent message with service ID AccessTimingParameters 13/Oct/2012 12:11:03.375: LOG: Message received no replies. 13/Oct/2012 12:11:03.375: LOG: Resending message. Send attempts: 3 13/Oct/2012 12:11:03.437: LOG: Sent message with service ID AccessTimingParameters 13/Oct/2012 12:11:05.453: LOG: Message received no replies. 13/Oct/2012 12:11:05.453: LOG: Failed to send message 3 times, message send failed. 13/Oct/2012 12:11:05.453: LOG: Did not receive any replies to message. 13/Oct/2012 12:11:05.453: USER: Reading ECU flash memory failed. 13/Oct/2012 12:11:05.968: LOG: Sent message with service ID TesterPresent 13/Oct/2012 12:11:07.984: LOG: Message received no replies. 13/Oct/2012 12:11:07.984: LOG: Resending message. Send attempts: 2 13/Oct/2012 12:11:08.000: LOG: Sent message with service ID TesterPresent 13/Oct/2012 12:11:08.625: LOG: User Prompt - Title: Reading ECU Flash Memory Complete Message: Reading ECU flash memory failed. Result: OK 13/Oct/2012 12:11:08.625: USER: 100% complete. 13/Oct/2012 12:11:08.843: USER: Restoring Windows sleep mode. Title: Re: Hard time connecting, log inside Post by: f1torrents on October 13, 2012, 10:33:30 AM Is it a stock tune or does it have a aftermarket tune on the ECU?
Title: Re: Hard time connecting, log inside Post by: ddillenger on October 13, 2012, 10:56:54 AM Stock, never tuned, 2001 audi a6, AA code ecu.
|