|
vwnut8392
|
 |
« on: February 22, 2011, 07:15:40 PM »
|
|
|
been trying to read the ECU in a 2000 1.8T GTI. but i keep getting "ECU reports that security access is not supported" i tried 2 different ECU's and no luck. the car runs fine and there is no aftermarket programming done to it. i could not access the ECU at all unless i pulled the cluster fuse. i pulled the ECU and the chip inside is a 29F400BB. am i doing something wrong or will this tool not work with this ECU?
here's a log from NEFMOTO.
here's the ECU info.
Disabling Windows sleep mode.
Reading ECU info.
Negotiating communication timings.
Timing negotiation failed. Communication timings are unchanged.
Reading ECU identification option: ECUIdentificationScalingTable
Successfully read ECU identification information
Reading ECU identification option: systemSupplierECUSoftwareNumber
Read ECU Identification systemSupplierECUSoftwareNumber: 0x1205,
Successfully read ECU identification information
Reading ECU identification option: calibrationDate
Read ECU Identification calibrationDate: 06A906032CL , V004, 0x00001964, 0x00000000, 0x0000,
Successfully read ECU identification information
Reading ECU identification option: calibrationEquipmentSoftwareNumber
Read ECU Identification calibrationEquipmentSoftwareNumber: 0x00000000,
Successfully read ECU identification information
100% complete.
Reading ECU info succeeded.
Restoring Windows sleep mode.
this is what i get when i try to validate the memory layout.
Disabling Windows sleep mode.
Validating memory layout.
Reading ECU identification option: calibrationEquipmentSoftwareNumber
Read ECU Identification calibrationEquipmentSoftwareNumber: 0x00000000,
Successfully read ECU identification information
ECU reports programming session preconditions have been met.
Requesting security access.
ECU reports that security access is not supported.
Starting diagnostic session.
Start diagnostic session failed, ECU reports conditions not correct or sequence error. Please turn off the ignition and retry.
100% complete.
Validating memory layout failed.
Restoring Windows sleep mode.
Disconnecting because no response was received for the Tester Present message.
Disconnected
|
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
 Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #1 on: February 22, 2011, 07:31:02 PM »
|
|
|
It's failing because of this:
"Start diagnostic session failed, ECU reports conditions not correct or sequence error"
Can you go to the file menu in the flashing software, and then open the log file location. Then please post that log file so we can see the detailed information of what may have gone wrong.
|
|
|
|
|
Logged
|
|
|
|
|
vwnut8392
|
|
« Reply #2 on: February 22, 2011, 11:26:03 PM »
|
|
|
2/Feb/2011 08:10:27.338: USER: Connecting...
22/Feb/2011 08:10:27.368: USER: Starting fast init connection.
22/Feb/2011 08:10:27.370: USER: Connecting to address 0x01.
22/Feb/2011 08:10:27.775: LOG: Sent message with service ID StartCommunication
22/Feb/2011 08:10:27.779: LOG: Idle end: 325ms Low end: 350ms High end: 375ms Message Send Time: 375ms
22/Feb/2011 08:10:27.780: USER: Fast init succeeded.
22/Feb/2011 08:10:27.815: LOG: Received message with service ID StartCommunicationPositiveResponse
22/Feb/2011 08:10:27.816: USER: Switching to KWP2000 session.
22/Feb/2011 08:10:27.818: USER: Connected
22/Feb/2011 08:10:30.347: LOG: Sent message with service ID TesterPresent
22/Feb/2011 08:10:30.387: LOG: Received message with service ID TesterPresentPositiveReponse
22/Feb/2011 08:10:32.297: USER: Disabling Windows sleep mode.
22/Feb/2011 08:10:32.300: USER: Reading ECU info.
22/Feb/2011 08:10:32.308: USER: Negotiating communication timings.
22/Feb/2011 08:10:32.310: LOG: Reading current communication timings.
22/Feb/2011 08:10:32.362: LOG: Sent message with service ID AccessTimingParameters
22/Feb/2011 08:10:32.406: LOG: Received message with service ID NegativeResponse
22/Feb/2011 08:10:32.406: LOG: Received negative response for service ID: AccessTimingParameters, with response code: ServiceNotSupported
22/Feb/2011 08:10:32.408: USER: Timing negotiation failed. Communication timings are unchanged.
22/Feb/2011 08:10:32.410: USER: Reading ECU identification option: ECUIdentificationScalingTable
22/Feb/2011 08:10:32.484: LOG: Sent message with service ID ReadECUIdentification
22/Feb/2011 08:10:32.538: LOG: Received message with service ID ReadECUIdentificationPositiveResponse
22/Feb/2011 08:10:32.539: USER: Successfully read ECU identification information
22/Feb/2011 08:10:32.542: USER: Reading ECU identification option: systemSupplierECUSoftwareNumber
22/Feb/2011 08:10:32.616: LOG: Sent message with service ID ReadECUIdentification
22/Feb/2011 08:10:32.656: LOG: Received message with service ID ReadECUIdentificationPositiveResponse
22/Feb/2011 08:10:32.658: USER: Read ECU Identification systemSupplierECUSoftwareNumber: 0x1205,
22/Feb/2011 08:10:32.660: USER: Successfully read ECU identification information
22/Feb/2011 08:10:32.662: USER: Reading ECU identification option: calibrationDate
22/Feb/2011 08:10:32.734: LOG: Sent message with service ID ReadECUIdentification
22/Feb/2011 08:10:32.798: LOG: Received message with service ID ReadECUIdentificationPositiveResponse
22/Feb/2011 08:10:32.801: USER: Read ECU Identification calibrationDate: 06A906032CL , V004, 0x00001964, 0x00000000, 0x0000,
22/Feb/2011 08:10:32.805: USER: Successfully read ECU identification information
22/Feb/2011 08:10:32.807: USER: Reading ECU identification option: calibrationEquipmentSoftwareNumber
22/Feb/2011 08:10:32.876: LOG: Sent message with service ID ReadECUIdentification
22/Feb/2011 08:10:32.918: LOG: Received message with service ID ReadECUIdentificationPositiveResponse
22/Feb/2011 08:10:32.919: USER: Read ECU Identification calibrationEquipmentSoftwareNumber: 0x00000000,
22/Feb/2011 08:10:32.921: USER: Successfully read ECU identification information
22/Feb/2011 08:10:32.924: USER: 100% complete.
22/Feb/2011 08:10:32.934: USER: Reading ECU info succeeded.
22/Feb/2011 08:10:34.545: USER: Restoring Windows sleep mode.
22/Feb/2011 08:10:35.439: LOG: Sent message with service ID TesterPresent
22/Feb/2011 08:10:35.479: LOG: Received message with service ID TesterPresentPositiveReponse
22/Feb/2011 08:10:37.998: LOG: Sent message with service ID TesterPresent
22/Feb/2011 08:10:38.034: LOG: Received message with service ID TesterPresentPositiveReponse
22/Feb/2011 08:10:40.553: LOG: Sent message with service ID TesterPresent
22/Feb/2011 08:10:40.589: LOG: Received message with service ID TesterPresentPositiveReponse
22/Feb/2011 08:10:43.106: LOG: Sent message with service ID TesterPresent
22/Feb/2011 08:10:43.144: LOG: Received message with service ID TesterPresentPositiveReponse
22/Feb/2011 08:10:45.662: LOG: Sent message with service ID TesterPresent
22/Feb/2011 08:10:45.698: LOG: Received message with service ID TesterPresentPositiveReponse
22/Feb/2011 08:10:48.217: LOG: Sent message with service ID TesterPresent
22/Feb/2011 08:10:48.253: LOG: Received message with service ID TesterPresentPositiveReponse
22/Feb/2011 08:10:50.773: LOG: Sent message with service ID TesterPresent
22/Feb/2011 08:10:50.809: LOG: Received message with service ID TesterPresentPositiveReponse
22/Feb/2011 08:10:53.327: LOG: Sent message with service ID TesterPresent
22/Feb/2011 08:10:53.365: LOG: Received message with service ID TesterPresentPositiveReponse
22/Feb/2011 08:10:55.884: LOG: Sent message with service ID TesterPresent
22/Feb/2011 08:10:55.920: LOG: Received message with service ID TesterPresentPositiveReponse
22/Feb/2011 08:10:58.437: LOG: Sent message with service ID TesterPresent
22/Feb/2011 08:10:58.475: LOG: Received message with service ID TesterPresentPositiveReponse
22/Feb/2011 08:11:00.993: LOG: Sent message with service ID TesterPresent
22/Feb/2011 08:11:01.031: LOG: Received message with service ID TesterPresentPositiveReponse
22/Feb/2011 08:11:03.549: LOG: Sent message with service ID TesterPresent
22/Feb/2011 08:11:03.585: LOG: Received message with service ID TesterPresentPositiveReponse
22/Feb/2011 08:11:06.104: LOG: Sent message with service ID TesterPresent
22/Feb/2011 08:11:06.140: LOG: Received message with service ID TesterPresentPositiveReponse
22/Feb/2011 08:11:08.660: LOG: Sent message with service ID TesterPresent
22/Feb/2011 08:11:08.696: LOG: Received message with service ID TesterPresentPositiveReponse
22/Feb/2011 08:11:11.214: LOG: Sent message with service ID TesterPresent
22/Feb/2011 08:11:11.252: LOG: Received message with service ID TesterPresentPositiveReponse
22/Feb/2011 08:11:13.769: LOG: Sent message with service ID TesterPresent
22/Feb/2011 08:11:13.807: LOG: Received message with service ID TesterPresentPositiveReponse
22/Feb/2011 08:11:16.324: LOG: Sent message with service ID TesterPresent
22/Feb/2011 08:11:16.362: LOG: Received message with service ID TesterPresentPositiveReponse
22/Feb/2011 08:11:18.882: LOG: Sent message with service ID TesterPresent
22/Feb/2011 08:11:18.916: LOG: Received message with service ID TesterPresentPositiveReponse
22/Feb/2011 08:11:19.473: USER: Disabling Windows sleep mode.
22/Feb/2011 08:11:19.478: USER: Validating memory layout.
22/Feb/2011 08:11:19.483: USER: Reading ECU identification option: calibrationEquipmentSoftwareNumber
22/Feb/2011 08:11:19.510: LOG: Sent message with service ID ReadECUIdentification
22/Feb/2011 08:11:19.550: LOG: Received message with service ID ReadECUIdentificationPositiveResponse
22/Feb/2011 08:11:19.595: USER: Read ECU Identification calibrationEquipmentSoftwareNumber: 0x00000000,
22/Feb/2011 08:11:19.599: USER: Successfully read ECU identification information
22/Feb/2011 08:11:19.602: USER: ECU reports programming session preconditions have been met.
22/Feb/2011 08:11:19.605: USER: Requesting security access.
22/Feb/2011 08:11:19.628: LOG: Sent message with service ID SecurityAccess
22/Feb/2011 08:11:19.668: LOG: Received message with service ID NegativeResponse
22/Feb/2011 08:11:19.669: LOG: Received negative response for service ID: SecurityAccess, with response code: ServiceNotSupported
22/Feb/2011 08:11:19.670: USER: ECU reports that security access is not supported.
22/Feb/2011 08:11:19.674: LOG: Starting diagnostic session type: ProgrammingSession
22/Feb/2011 08:11:19.675: USER: Starting diagnostic session.
22/Feb/2011 08:11:19.753: LOG: Sent message with service ID StartDiagnosticSession
22/Feb/2011 08:11:19.797: LOG: Received message with service ID NegativeResponse
22/Feb/2011 08:11:19.798: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: ConditionsNotCorrectOrRequestSequenceError
22/Feb/2011 08:11:19.799: USER: Start diagnostic session failed, ECU reports conditions not correct or sequence error. Please turn off the ignition and retry.
22/Feb/2011 08:11:19.803: USER: 100% complete.
22/Feb/2011 08:11:19.806: USER: Validating memory layout failed.
22/Feb/2011 08:11:21.114: USER: Restoring Windows sleep mode.
22/Feb/2011 08:11:22.315: LOG: Sent message with service ID TesterPresent
22/Feb/2011 08:11:22.351: LOG: Received message with service ID TesterPresentPositiveReponse
22/Feb/2011 08:11:24.937: LOG: Sent message with service ID TesterPresent
22/Feb/2011 08:11:24.994: LOG: Resending message. Send attempts: 2
22/Feb/2011 08:11:25.013: LOG: Sent message with service ID TesterPresent
22/Feb/2011 08:11:25.070: LOG: Resending message. Send attempts: 3
22/Feb/2011 08:11:25.086: LOG: Sent message with service ID TesterPresent
22/Feb/2011 08:11:25.143: LOG: Failed to send message 3 times, message send failed.
22/Feb/2011 08:11:25.144: USER: Disconnecting because no response was received for the Tester Present message.
22/Feb/2011 08:11:25.149: USER: Disconnected
22/Feb/2011 08:11:25.244: LOG: Closing FTDI device.
22/Feb/2011 08:11:25.264: LOG: Send receive thread now terminated.
|
|
|
|
|
Logged
|
|
|
|
|
vwnut8392
|
|
« Reply #3 on: February 23, 2011, 08:46:16 PM »
|
|
|
what that enough information from the log?
|
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #4 on: February 24, 2011, 03:12:23 PM »
|
|
|
That's enough info.
hmmm... preconditions met, but can't start programming session...
The ECU is installed in the car, and the engine was not running correct?
|
|
|
|
« Last Edit: February 24, 2011, 03:17:01 PM by Tony@NefMoto »
|
Logged
|
|
|
|
|
vwnut8392
|
|
« Reply #5 on: February 24, 2011, 05:21:17 PM »
|
|
|
no, i have them out on the bench with a harness i made. im using a computer power supply to to power the ECU and all that fun jazz.
|
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #6 on: February 24, 2011, 08:10:07 PM »
|
|
|
My best guess at this point, is that the ECU wants to be installed in the car talking to the immobilizer, even though it says all of the programming preconditions have been met.
|
|
|
|
|
Logged
|
|
|
|
|
vwnut8392
|
|
« Reply #7 on: February 24, 2011, 11:06:58 PM »
|
|
|
well i am working on adding the connectors in for an instrument cluster so that it has access to it and i can recode my cluster to the ECU im working with. seems like the only option i have to be able to access an ECU without a car.
|
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #8 on: February 25, 2011, 03:34:54 PM »
|
|
|
If you can disable the immobilizer coding in the ECU, then that should also allow you to connect.
|
|
|
|
|
Logged
|
|
|
|
|
vwnut8392
|
|
« Reply #9 on: February 26, 2011, 09:13:04 PM »
|
|
|
ok, i'll try that tony thanks. if it still gives me issues i'll post up a new log.
|
|
|
|
|
Logged
|
|
|
|
sean337
Newbie
Karma: +1/-0
Offline
Posts: 12
|
|
« Reply #10 on: March 02, 2011, 06:17:53 PM »
|
|
|
If you can disable the immobilizer coding in the ECU, then that should also allow you to connect.
Hey Tony, I've been lurking here a bit, but finally posting. I am trying to clone a replacement ECU for a family members A4. I need to do this on the bench as they live a ways from me. Could you elaborate on how to disable this immo coding on the bench so that I can utilize your software to complete this. I'll also open this up to anyone else reading, if you can help me get squared away I would appreciate it. As of now I am thinking I need to purchase some sort of SO8 test clip to read out and modify an eprom on the bottom of the ECU. Is there a better method? Thanks in advance... Sean |
|
|
|
|
Logged
|
|
|
|
kls
Full Member
Karma: +12/-0
Offline
Posts: 97
|
|
« Reply #11 on: March 02, 2011, 07:33:00 PM »
|
|
|
If you're doing a true clone of an ECU there is no need to disable the immobilizer.
Either way, cloning the ecu or disabling the immobilizer does require you to be able to read/write the serial eeprom. I use a UPA-USB with an SOIC-8 clip to read/write them in circuit.
btw 337 FTW !
|
|
|
|
|
Logged
|
|
|
|
sean337
Newbie
Karma: +1/-0
Offline
Posts: 12
|
|
« Reply #12 on: March 02, 2011, 07:39:42 PM »
|
|
|
If you're doing a true clone of an ECU there is no need to disable the immobilizer.
Either way, cloning the ecu or disabling the immobilizer does require you to be able to read/write the serial eeprom. I use a UPA-USB with an SOIC-8 clip to read/write them in circuit.
btw 337 FTW !
Thanks kls, So all I really need to do is copy the contents of the original serial eeprom off the back off the ecu and flash that onto the replacement ECU. This is going to transfer all of the immo settings, VIN # etc correct? Edit - and to keep this relevant to the original thread, this would be where the immo could be disabled if needed? Sean |
|
|
|
|
Logged
|
|
|
|
kls
Full Member
Karma: +12/-0
Offline
Posts: 97
|
|
« Reply #13 on: March 03, 2011, 01:49:05 AM »
|
|
|
Yes, if you use an eeprom reader/writer and copy the entire serial eeprom it will preserve all settings.
To disable the IMMO change the $01 to $02 at addresses $12 and $22.
Then correct the checksums at addresses $1E and $2E by subtracting one from each.
I have verified this to work on both ME7.1.1 and ME7.5
|
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #14 on: March 03, 2011, 12:50:15 PM »
|
|
|
I've been lurking here a bit, but finally posting. I am trying to clone a replacement ECU for a family members A4. I need to do this on the bench as they live a ways from me. Could you elaborate on how to disable this immo coding on the bench so that I can utilize your software to complete this.
From what I have seen, if the ECU has an immobilizer, then you can only flash it in car where it can talk to the immobilizer. To allow flashing on the bench, the immobilizer must be disabled. This of course only applies to flashing with the KWP1281 or KWP2000 protocols, because flashing with bootmode bypasses everything. |
|
|
|
|
Logged
|
|
|
|
|
