Title: Flash fails at Negotiating Communication timing
Post by: EarthWalker on July 17, 2019, 07:44:08 PM
Greetings. I've successfully flashed my ECU about 3 times since getting this going. This last time around I did some o2 deletes to pass readiness. When I go to upload my new flash the write dies at Negotiating Communication Timings, from the log it's not getting a response to Service ID AccessTimingParameters I've uninstalled and reinstall the drives for the FTDI chipset, I've tried all the baud rates. VCDS-Lite connects and can do the basic crippleware functions. My vag401 tool still accesses the ecu just fine. I've rebooted my computer, a few times. I even walked away for about an hour. I've got a trickle charger on the battery. What am I missing? I looked at some of the settings inside on the kwp2000 settings tab but didn't really see one relating to communication timings. 17/Jul/2019 07:31:57.497: USER: Connecting...
17/Jul/2019 07:31:57.514: LOG: Setting communication timings to defaults.
17/Jul/2019 07:31:57.520: USER: Starting slow init connection.
17/Jul/2019 07:32:00.126: USER: Connecting to address 0x01.
17/Jul/2019 07:32:02.280: USER: Slow init succeeded.
17/Jul/2019 07:32:02.286: LOG: Setting Address: 0x01 KeyByte1: 0x01 KeyByte2: 0x0A
17/Jul/2019 07:32:02.291: USER: Switching to KWP1281 session.
17/Jul/2019 07:32:02.462: LOG: KWP1281 read block
17/Jul/2019 07:32:02.527: LOG: KWP1281 sent block
17/Jul/2019 07:32:02.825: LOG: KWP1281 read block
17/Jul/2019 07:32:02.899: LOG: KWP1281 sent block
17/Jul/2019 07:32:03.065: LOG: KWP1281 read block
17/Jul/2019 07:32:03.129: LOG: KWP1281 sent block
17/Jul/2019 07:32:03.276: LOG: KWP1281 read block
17/Jul/2019 07:32:03.340: LOG: KWP1281 sent block
17/Jul/2019 07:32:03.376: LOG: KWP1281 read block
17/Jul/2019 07:32:03.440: LOG: KWP1281 sent block
17/Jul/2019 07:32:03.447: USER: KWP1281 connect info: 8D0907551M 2.7l V6/5VT G 0002 4qTO
17/Jul/2019 07:32:04.953: USER: Connecting to address 0x01.
17/Jul/2019 07:32:07.128: USER: Slow init succeeded.
17/Jul/2019 07:32:07.134: LOG: Setting Address: 0x01 KeyByte1: 0x6F KeyByte2: 0x0F
17/Jul/2019 07:32:07.139: USER: Switching to KWP2000 session.
17/Jul/2019 07:32:07.145: USER: Connected
17/Jul/2019 07:32:09.670: LOG: Sent message with service ID TesterPresent
17/Jul/2019 07:32:09.706: LOG: Received message with service ID: TesterPresentPositiveReponse
17/Jul/2019 07:32:12.189: LOG: Sent message with service ID TesterPresent
17/Jul/2019 07:32:12.231: LOG: Received message with service ID: TesterPresentPositiveReponse
17/Jul/2019 07:32:14.707: LOG: Sent message with service ID TesterPresent
17/Jul/2019 07:32:14.744: LOG: Received message with service ID: TesterPresentPositiveReponse
17/Jul/2019 07:32:17.226: LOG: Sent message with service ID TesterPresent
17/Jul/2019 07:32:17.269: LOG: Received message with service ID: TesterPresentPositiveReponse
17/Jul/2019 07:32:19.744: LOG: Sent message with service ID TesterPresent
17/Jul/2019 07:32:19.783: LOG: Received message with service ID: TesterPresentPositiveReponse
17/Jul/2019 07:32:22.263: LOG: Sent message with service ID TesterPresent
17/Jul/2019 07:32:22.338: LOG: Received message with service ID: TesterPresentPositiveReponse
17/Jul/2019 07:32:24.781: LOG: Sent message with service ID TesterPresent
17/Jul/2019 07:32:24.821: LOG: Received message with service ID: TesterPresentPositiveReponse
17/Jul/2019 07:32:27.299: LOG: Sent message with service ID TesterPresent
17/Jul/2019 07:32:27.335: LOG: Received message with service ID: TesterPresentPositiveReponse
17/Jul/2019 07:32:29.818: LOG: Sent message with service ID TesterPresent
17/Jul/2019 07:32:29.859: LOG: Received message with service ID: TesterPresentPositiveReponse
17/Jul/2019 07:32:32.337: LOG: Sent message with service ID TesterPresent
17/Jul/2019 07:32:32.374: LOG: Received message with service ID: TesterPresentPositiveReponse
17/Jul/2019 07:32:34.855: LOG: Sent message with service ID TesterPresent
17/Jul/2019 07:32:34.899: LOG: Received message with service ID: TesterPresentPositiveReponse
17/Jul/2019 07:32:37.372: LOG: Sent message with service ID TesterPresent
17/Jul/2019 07:32:37.413: LOG: Received message with service ID: TesterPresentPositiveReponse
17/Jul/2019 07:32:37.850: LOG: User Prompt - Title: Confirm Full Write ECU Flash Memory Message: If you are ready to write, confirm the following things:
1) You have loaded a valid file and memory layout for the ECU.
2) The engine is not running.
3) Battery voltage is at least 12 volts.
4) It is OK the ECU adaptation channels will be reset to defaults
5) Flashing process can run uninterrupted until complete.
6) You agree to release Nefarious Motorsports Inc from all liability.
Note: Some non-standard flash memory chips may prevent writing the flash memory.
Click OK to confirm, otherwise Cancel. Result: OK
17/Jul/2019 07:32:38.134: LOG: Disabling Windows sleep mode.
17/Jul/2019 07:32:38.139: USER: Writing ECU flash memory.
17/Jul/2019 07:32:38.153: LOG: Reading ECU identification option: 0x9C
17/Jul/2019 07:32:38.168: LOG: Sent message with service ID ReadECUIdentification
17/Jul/2019 07:32:38.213: LOG: Received message with service ID: ReadECUIdentificationPositiveResponse
17/Jul/2019 07:32:38.218: LOG: Read ECU identification option: 0x9C
17/Jul/2019 07:32:38.226: LOG: Successfully read ECU identification information
17/Jul/2019 07:32:38.230: USER: ECU reports programming session preconditions have been met.
17/Jul/2019 07:32:38.236: USER: Negotiating communication timings.
17/Jul/2019 07:32:38.241: LOG: Reading current communication timings.
17/Jul/2019 07:32:38.287: LOG: Sent message with service ID AccessTimingParameters
17/Jul/2019 07:32:40.289: LOG: Message received no replies.
17/Jul/2019 07:32:40.294: LOG: Resending message. Send attempts: 2
17/Jul/2019 07:32:40.341: LOG: Sent message with service ID AccessTimingParameters
17/Jul/2019 07:32:42.344: LOG: Message received no replies.
17/Jul/2019 07:32:42.349: LOG: Resending message. Send attempts: 3
17/Jul/2019 07:32:42.395: LOG: Sent message with service ID AccessTimingParameters
17/Jul/2019 07:32:44.399: LOG: Message received no replies.
17/Jul/2019 07:32:44.416: LOG: Failed to send message 3 times, message send failed.
17/Jul/2019 07:32:44.426: LOG: Did not receive any replies to message.
17/Jul/2019 07:32:44.913: LOG: Sent message with service ID TesterPresent
17/Jul/2019 07:32:46.457: LOG: User Prompt - Title: Communication Error Message: A communication error was encountered while flashing. Press Cancel to abort, or OK to continue after reconnecting. Result: CANCEL
17/Jul/2019 07:32:46.471: USER: Writing ECU flash memory failed.
17/Jul/2019 07:32:46.491: USER: 100% complete.
17/Jul/2019 07:32:46.916: LOG: Message received no replies.
17/Jul/2019 07:32:46.933: LOG: Resending message. Send attempts: 2
17/Jul/2019 07:32:46.966: LOG: Sent message with service ID TesterPresent
17/Jul/2019 07:32:48.650: LOG: User Prompt - Title: Writing ECU Flash Memory Complete Message: Writing ECU flash memory failed. Result: OK
17/Jul/2019 07:32:48.667: LOG: Restoring Windows sleep mode.
17/Jul/2019 07:32:48.969: LOG: Message received no replies.
17/Jul/2019 07:32:48.986: LOG: Resending message. Send attempts: 3
17/Jul/2019 07:32:49.018: LOG: Sent message with service ID TesterPresent
17/Jul/2019 07:32:51.019: LOG: Message received no replies.
17/Jul/2019 07:32:51.028: LOG: Failed to send message 3 times, message send failed.
17/Jul/2019 07:32:51.036: USER: Disconnecting because no response was received for the Tester Present message.
17/Jul/2019 07:32:51.041: USER: Disconnected
Thanks
Title: Re: Flash fails at Negotiating Communication timing
Post by: nyet on July 17, 2019, 07:57:28 PM
I'd restore the ECU to stock using bootmode, and see if you can flash over that. If not, maybe get a spare ecu to make sure your set up is good.
Title: Re: Flash fails at Negotiating Communication timing
Post by: EarthWalker on July 17, 2019, 10:40:44 PM
I'd restore the ECU to stock using bootmode, and see if you can flash over that. If not, maybe get a spare ecu to make sure your set up is good.
So there isn't a whole slew of allroads at the jy's near me, I do have an ecu out of an 04 a6 4b0907551t ecu - I was using an 8d0 file for my 01 allroad (originally a 4z7907551M). I just dropped in a 6mt and did a sai delete. Will I be able to flash the a6 ecu in the car or do I need a bench setup?
Title: Re: Flash fails at Negotiating Communication timing
Post by: nyet on July 17, 2019, 11:01:49 PM
You will unfortunately need a bench setup to bootmode it. But NEF will work non-bootmode via OBD if the ECU allows it (i.e. it is stock or doesn't have a riser and the flash allows it)
You also don't need an allroad/a6 ECU, you can use any ME7 2.7t ecu. You will have to transfer the eeprom if you have immo and don't want to disable it.
http://files.s4wiki.com/stock/part-numbers.txt
Title: Re: Flash fails at Negotiating Communication timing
Post by: EarthWalker on July 18, 2019, 08:14:56 AM
You will unfortunately need a bench setup to bootmode it. But NEF will work non-bootmode via OBD if the ECU allows it (i.e. it is stock or doesn't have a riser and the flash allows it)
You also don't need an allroad/a6 ECU, you can use any ME7 2.7t ecu. You will have to transfer the eeprom if you have immo and don't want to disable it.
http://files.s4wiki.com/stock/part-numbers.txt
But still needs to be a bench setup to flash correct? - i just can't drop another me7.1 ecu into my allroad -> immo flash -> ecu flash from there?
Title: Re: Flash fails at Negotiating Communication timing
Post by: nyet on July 18, 2019, 10:23:33 PM
But still needs to be a bench setup to flash correct? - i just can't drop another me7.1 ecu into my allroad -> immo flash -> ecu flash from there?
You only need bench to bootmode (ecu is bricked, or non-riser aftermarket chip disabled OBD flash) or to write the eeprom (for immo)
|