Pages: [1]
Author Topic: Could not Read Flash...stuck at negotiating communication timings.  (Read 8143 times)
j2mc
Full Member
***

Karma: +15/-0
Offline Offline

Posts: 50



2000 a6 2.7t 6spd 4B0907551K
Validate Memory Layout and Read Flash both just sit at negotiating communication timings.  I've tried both slow init and fast init, here is the log from my last attempt:
Code:
24/May/2011 04:39:56.848: LOG: Opening NefMoto VW Audi ME7 ECU Flasher BETA 1.7.0.0
24/May/2011 04:39:59.203: LOG: Cannot load license file, file does not exist.
24/May/2011 04:40:00.093: LOG: Opened NefMoto VW Audi ME7 ECU Flasher BETA 1.7.0.0
24/May/2011 04:41:53.219: LOG: Opened FTDI device.
24/May/2011 04:41:53.224: LOG: FTDI device info - Description: FT232R USB UART Serial Number: A4008WfA Device Type: FT_DEVICE_232R Device ID: 0x4036001 Device Flags: 0x0
24/May/2011 04:41:53.229: LOG: FTDI ChipID DLL is loaded, checking chip ID...
24/May/2011 04:41:53.234: LOG: FTDI device chip ID: 0x91D2E7D5
24/May/2011 04:41:53.488: LOG: Starting send receive thread.
24/May/2011 04:41:53.560: LOG: Send receive thread now started.
24/May/2011 04:41:53.565: USER: Disconnected
24/May/2011 04:41:53.633: LOG: Set timing parameters to defaults.
24/May/2011 04:41:53.682: USER: Connection attempt number 1.
24/May/2011 04:41:53.690: USER: Connecting...
24/May/2011 04:41:53.701: LOG: Set timing parameters to defaults.
24/May/2011 04:41:53.718: USER: Starting fast init connection.
24/May/2011 04:41:53.724: USER: Connecting to address 0x01.
24/May/2011 04:41:54.153: LOG: Sent message with service ID StartCommunication
24/May/2011 04:41:54.170: LOG: Idle end: 325ms Low end: 350ms High end: 375ms Message Send Time: 375ms
24/May/2011 04:41:54.173: USER: Fast init succeeded, sending start communication request.
24/May/2011 04:41:54.216: LOG: Received message with service ID StartCommunicationPositiveResponse
24/May/2011 04:41:54.221: USER: Switching to KWP2000 session.
24/May/2011 04:41:54.226: USER: Connected
24/May/2011 04:41:56.759: LOG: Sent message with service ID TesterPresent
24/May/2011 04:41:56.797: LOG: Received message with service ID TesterPresentPositiveReponse
24/May/2011 04:41:59.314: LOG: Sent message with service ID TesterPresent
24/May/2011 04:41:59.351: LOG: Received message with service ID TesterPresentPositiveReponse
24/May/2011 04:41:59.764: USER: Disabling Windows sleep mode.
24/May/2011 04:41:59.771: USER: Reading ECU flash memory.
24/May/2011 04:41:59.861: USER: Reading ECU identification option: calibrationEquipmentSoftwareNumber
24/May/2011 04:41:59.878: LOG: Sent message with service ID ReadECUIdentification
24/May/2011 04:41:59.919: LOG: Received message with service ID ReadECUIdentificationPositiveResponse
24/May/2011 04:42:00.057: USER: Read ECU identification option with unknown scaling record.
24/May/2011 04:42:00.063: USER: Successfully read ECU identification information
24/May/2011 04:42:00.077: USER: ECU reports programming session preconditions have been met.
24/May/2011 04:42:00.086: USER: Requesting security access.
24/May/2011 04:42:00.122: LOG: Sent message with service ID SecurityAccess
24/May/2011 04:42:00.168: LOG: Received message with service ID NegativeResponse
24/May/2011 04:42:00.173: LOG: Received negative response for service ID: SecurityAccess, with response code: ServiceNotSupported
24/May/2011 04:42:00.180: USER: ECU reports that security access is not supported.
24/May/2011 04:42:00.187: LOG: Starting diagnostic session type: ProgrammingSession
24/May/2011 04:42:00.190: USER: Starting diagnostic session.
24/May/2011 04:42:00.254: LOG: Sent message with service ID StartDiagnosticSession
24/May/2011 04:42:00.298: LOG: Received message with service ID NegativeResponse
24/May/2011 04:42:00.301: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
24/May/2011 04:42:00.338: LOG: Received message with service ID NegativeResponse
24/May/2011 04:42:00.341: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
24/May/2011 04:42:00.378: LOG: Received message with service ID NegativeResponse
24/May/2011 04:42:00.381: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
24/May/2011 04:42:00.420: LOG: Received message with service ID NegativeResponse
24/May/2011 04:42:00.423: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
24/May/2011 04:42:00.460: LOG: Received message with service ID NegativeResponse
24/May/2011 04:42:00.464: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
24/May/2011 04:42:00.496: LOG: Received message with service ID NegativeResponse
24/May/2011 04:42:00.500: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
24/May/2011 04:42:00.536: LOG: Received message with service ID NegativeResponse
24/May/2011 04:42:00.540: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
24/May/2011 04:42:00.572: LOG: Received message with service ID StartDiagnosticSessionPositiveResponse
24/May/2011 04:42:00.580: LOG: Set timing parameters to defaults.
24/May/2011 04:42:00.583: LOG: Changed diagnostic session type to: ProgrammingSession
24/May/2011 04:42:00.587: LOG: ECU requesting specific baud rate.
24/May/2011 04:42:00.590: USER: Successfully started diagnostic session.
24/May/2011 04:42:00.597: USER: Negotiating communication timings.
24/May/2011 04:42:00.642: LOG: Reading current communication timings.
24/May/2011 04:42:00.693: LOG: Sent message with service ID AccessTimingParameters
24/May/2011 04:42:00.699: LOG: Read incorrect echo from ECU while sending message bytes
24/May/2011 04:42:00.703: LOG: Expected: 07 83 02 00 00 00 00 00 8C
24/May/2011 04:42:00.707: LOG: Read:     07 03 00 00 00 00 00 00 08
24/May/2011 04:42:00.710: LOG: Was ignoring first 0 bytes of the echo.
24/May/2011 04:42:00.970: LOG: Could not construct valid message from received data: NotResponseServiceID
24/May/2011 04:42:00.974: LOG: Removing first byte from the receive buffer to try to create a valid message.
24/May/2011 04:42:00.977: LOG: Could not construct valid message from received data: NotResponseServiceID
24/May/2011 04:42:00.981: LOG: Removing first byte from the receive buffer to try to create a valid message.
24/May/2011 04:42:00.984: LOG: Could not construct valid message from received data: NotResponseServiceID
24/May/2011 04:42:00.987: LOG: Removing first byte from the receive buffer to try to create a valid message.
24/May/2011 04:42:00.991: LOG: Could not construct valid message from received data: NotResponseServiceID
24/May/2011 04:42:00.994: LOG: Removing first byte from the receive buffer to try to create a valid message.
24/May/2011 04:42:00.999: LOG: Could not construct valid message from received data: NotResponseServiceID
24/May/2011 04:42:01.002: LOG: Removing first byte from the receive buffer to try to create a valid message.
24/May/2011 04:42:01.004: LOG: Could not construct valid message from received data: NotResponseServiceID
24/May/2011 04:42:01.008: LOG: Removing first byte from the receive buffer to try to create a valid message.
24/May/2011 04:42:01.011: LOG: Could not construct valid message from received data: NotResponseServiceID
24/May/2011 04:42:01.014: LOG: Removing first byte from the receive buffer to try to create a valid message.
24/May/2011 04:42:01.018: LOG: Could not construct valid message from received data: NotResponseServiceID
24/May/2011 04:42:01.021: LOG: Removing first byte from the receive buffer to try to create a valid message.

...continues on like that until I close the program.
« Last Edit: May 24, 2011, 05:06:07 PM by Tony@NefMoto » Logged

2.7t stg2
Tony@NefMoto
Administrator
Hero Member
*****

Karma: +132/-4
Offline Offline

Posts: 1389


2001.5 Audi S4 Stage 3


« Reply #1 on: May 24, 2011, 05:07:09 PM »

What happens if you change the baud rate from Maximum to 10400?
Logged

Remember you have to log in if you want to see the file attachments!
Info or questions, please add to the wiki: http://www.nefariousmotorsports.com/wiki
Follow NefMoto developments on Twitter: http://twitter.com/nefmoto
julex
Hero Member
*****

Karma: +79/-4
Offline Offline

Posts: 923


« Reply #2 on: May 24, 2011, 06:39:34 PM »

I've seen something similar trying to use VAG-COM USB cable in dumb mode. Timing problem.
Logged
j2mc
Full Member
***

Karma: +15/-0
Offline Offline

Posts: 50


« Reply #3 on: May 24, 2011, 07:50:38 PM »

What happens if you change the baud rate from Maximum to 10400?

That fixed it(can't believe I didn't try that before posting, just missed it I guess)...75% complete right now.
Thanks!
« Last Edit: May 24, 2011, 08:05:59 PM by j2mc » Logged

2.7t stg2
j2mc
Full Member
***

Karma: +15/-0
Offline Offline

Posts: 50


« Reply #4 on: May 24, 2011, 08:03:10 PM »

FYI - I bought my cable from ebay seller car-scanner, I bought the black one and it does have the FT232r chip and seems physically like a good quality cable(other than the problem above it has has worked longer than my official ross-tech one which is currently being repaired).

Logged

2.7t stg2
engineeredD-zyn
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 10


« Reply #5 on: April 01, 2015, 03:06:57 PM »

What happens if you change the baud rate from Maximum to 10400?

your the man. this must be the case for all the 551k - 005. fixed my problem right up 
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.017 seconds with 16 queries. (Pretty URLs adds 0s, 0q)