|
Title: nefmoto cant write, car wont start Post by: wagstach on December 29, 2014, 04:38:25 PM 29/Dec/2014 06:24:56.989: LOG: Sent message with service ID AccessTimingParameters
29/Dec/2014 06:24:57.031: LOG: Received message with service ID: AccessTimingParametersPositiveResponse 29/Dec/2014 06:24:57.086: LOG: Sent message with service ID AccessTimingParameters 29/Dec/2014 06:24:57.105: LOG: Received message with service ID: AccessTimingParametersPositiveResponse 29/Dec/2014 06:24:57.158: LOG: Sent message with service ID SecurityAccess 29/Dec/2014 06:24:57.174: LOG: Received message with service ID: NegativeResponse 29/Dec/2014 06:24:57.183: LOG: Received negative response for service ID: SecurityAccess, with response code: ServiceNotSupported 29/Dec/2014 06:24:57.236: LOG: Sent message with service ID StartDiagnosticSession 29/Dec/2014 06:24:57.254: LOG: Received message with service ID: NegativeResponse 29/Dec/2014 06:24:57.263: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending 29/Dec/2014 06:24:57.276: LOG: Received message with service ID: NegativeResponse 29/Dec/2014 06:24:57.285: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending 29/Dec/2014 06:24:57.295: LOG: Received message with service ID: NegativeResponse 29/Dec/2014 06:24:57.304: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending 29/Dec/2014 06:24:57.314: LOG: Received message with service ID: NegativeResponse 29/Dec/2014 06:24:57.321: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending 29/Dec/2014 06:24:57.328: LOG: Received message with service ID: NegativeResponse 29/Dec/2014 06:24:57.335: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending 29/Dec/2014 06:24:57.343: LOG: Received message with service ID: NegativeResponse 29/Dec/2014 06:24:57.350: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending 29/Dec/2014 06:24:57.357: LOG: Received message with service ID: NegativeResponse 29/Dec/2014 06:24:57.364: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending 29/Dec/2014 06:24:57.374: LOG: Received message with service ID: NegativeResponse 29/Dec/2014 06:24:57.381: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending 29/Dec/2014 06:24:57.388: LOG: Received message with service ID: NegativeResponse 29/Dec/2014 06:24:57.395: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending 29/Dec/2014 06:24:57.401: LOG: Received message with service ID: NegativeResponse 29/Dec/2014 06:24:57.408: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending 29/Dec/2014 06:24:57.413: LOG: Received message with service ID: NegativeResponse 29/Dec/2014 06:24:57.420: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending 29/Dec/2014 06:24:57.427: LOG: Received message with service ID: NegativeResponse 29/Dec/2014 06:24:57.432: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending 29/Dec/2014 06:24:57.439: LOG: Received message with service ID: NegativeResponse 29/Dec/2014 06:24:57.445: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending 29/Dec/2014 06:24:57.454: LOG: Received message with service ID: NegativeResponse 29/Dec/2014 06:24:57.460: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending 29/Dec/2014 06:24:57.466: LOG: Received message with service ID: NegativeResponse 29/Dec/2014 06:24:57.472: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending 29/Dec/2014 06:24:57.478: LOG: Received message with service ID: NegativeResponse 29/Dec/2014 06:24:57.484: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending 29/Dec/2014 06:24:57.490: LOG: Received message with service ID: StartDiagnosticSessionPositiveResponse 29/Dec/2014 06:24:59.753: LOG: Sent message with service ID TesterPresent 29/Dec/2014 06:24:59.858: LOG: Message received no replies. 29/Dec/2014 06:24:59.864: LOG: Resending message. Send attempts: 2 29/Dec/2014 06:24:59.887: LOG: Sent message with service ID TesterPresent 29/Dec/2014 06:24:59.990: LOG: Message received no replies. 29/Dec/2014 06:24:59.996: LOG: Resending message. Send attempts: 3 29/Dec/2014 06:25:00.018: LOG: Sent message with service ID TesterPresent 29/Dec/2014 06:25:00.122: LOG: Message received no replies. 29/Dec/2014 06:25:00.128: LOG: Failed to send message 3 times, message send failed. 29/Dec/2014 06:25:00.134: USER: Disconnecting because no response was received for the Tester Present message. 29/Dec/2014 06:25:00.141: USER: Disconnected Title: Re: nefmoto cant write, car wont start Post by: ddillenger on December 29, 2014, 04:49:41 PM This is not nearly enough information with which to help you :(
Year? Make? Model? Ecu number? History (IE, what it was doing before it wouldn't start)? What baud rate are you using? What have you tried? What cable are you using? Title: Re: nefmoto cant write, car wont start Post by: wagstach on December 29, 2014, 07:00:13 PM 2000 audi s4
unspecified baud rate wrote 8D0907551M-0001.bin as a starting point, car would not start for a while, it would turn over and fire but only once every like 2 seconds and not start. i came back the next day and the car started immediately once, then continued to do the same. i tried flashing the same file in bootmode with gallatto and i could write but still had the same problems with nefmoto and starting. then tried ME7_95040 with immodef.bin with no changes. i have flashed other files and this one to the car with no problems before. Title: Re: nefmoto cant write, car wont start Post by: ddillenger on December 29, 2014, 07:02:12 PM 2000 audi s4 unspecified baud rate wrote 8D0907551M-0001.bin as a starting point, car would not start for a while, it would turn over and fire but only once every like 2 seconds and not start. i came back the next day and the car started immediately once, then continued to do the same. i tried flashing the same file in bootmode with gallatto and i could write but still had the same problems with nefmoto and starting. then tried ME7_95040 with immodef.bin with no changes. i have flashed other files and this one to the car with no problems before. Disconnect the battery. Wait 5 minutes. Reconnect the battery. Turn the key on. Is the engine light on? DO NOT ATTEMPT TO START THE CAR. IF the engine light is on, connect, lower the baud to 38400 and flash a stock file. Title: Re: nefmoto cant write, car wont start Post by: wagstach on December 30, 2014, 02:22:03 PM after reattaching the battery the check engine light was on when the ignition was turned on. I tried writing and it failed, attached is the log, now the check engine light is no longer lighting up.
Title: Re: nefmoto cant write, car wont start Post by: _nameless on December 30, 2014, 02:28:08 PM Shouldn't have turned the key off if you just reconnected lowered your rate and rewrote it odds are you'd be fine. A failed write normally means brick. Boot mode it with a stock file and be sure all is working as should be. Do you have a direct line in the car to k-line? Personally I've had my own problems with b5 s4's /c5 a6's because of "noise" from other modules that can interrupt programming
Title: Re: nefmoto cant write, car wont start Post by: ddillenger on December 30, 2014, 02:38:25 PM after reattaching the battery the check engine light was on when the ignition was turned on. I tried writing and it failed, attached is the log, now the check engine light is no longer lighting up. Next time consider following instructions. I specifically said lower the baud rate after connecting. You didn't do this, and as a result failed a flash and bricked the ecu. In the future, if you do not turn the key off, you can reconnect and flash again. As it is now, you need to bootmode the ecu. I choose my words very carefully in order to give the people reading them the very best chance of success. When people ignore them, it makes me less likely to assist them in the future :( Title: Re: nefmoto cant write, car wont start Post by: wagstach on December 30, 2014, 02:45:45 PM the key was off while I disconnected the battery ? then I turned the key on after I reconnected it was this wrong ?
Title: Re: nefmoto cant write, car wont start Post by: wagstach on December 30, 2014, 02:56:30 PM Sorry didnt know you had to change the baud twice once before connecting and again before writing
Title: Re: nefmoto cant write, car wont start Post by: ddillenger on December 30, 2014, 02:59:38 PM The first time the programming session was closed, so removing the battery did no harm. The second time it was in the process of programming it. Removing the power wiped the ecu.
Title: Re: nefmoto cant write, car wont start Post by: wagstach on December 30, 2014, 03:59:29 PM thank you for the help lowering the baud. I lowered the baud and successfully wrote the stock file on, the car trys the start but only fires once or twice every few seconds, seems like the ecu is cutting spark for some reason after the first ignition. this car is evil
|