|
Title: Start diagnostic session failed, ECU reports conditions HELPS!! Post by: Cablekid on November 13, 2011, 04:05:28 PM It can read the ECU INFO but then it cant validate the memory :( HELP!
The ECU IS in the CAR with the car ignition on. The engine is not running 1999 AUDI TT 1.8T USA Quote 13/Nov/2011 03:00:52.450: USER: Disabling Windows sleep mode. 13/Nov/2011 03:00:52.463: USER: Reading ECU info. 13/Nov/2011 03:00:52.483: USER: Reading ECU identification option: ECUIdentificationScalingTable 13/Nov/2011 03:00:52.489: LOG: Sent message with service ID ReadECUIdentification 13/Nov/2011 03:00:52.550: LOG: Received message with service ID ReadECUIdentificationPositiveResponse 13/Nov/2011 03:00:52.557: USER: Successfully read ECU identification information 13/Nov/2011 03:00:52.590: USER: Reading ECU identification option: systemSupplierECUHardwareNumber 13/Nov/2011 03:00:52.601: LOG: Sent message with service ID ReadECUIdentification 13/Nov/2011 03:00:52.648: LOG: Received message with service ID ReadECUIdentificationPositiveResponse 13/Nov/2011 03:00:52.658: USER: Read ECU Identification systemSupplierECUHardwareNumber: 0261206582, 13/Nov/2011 03:00:52.669: USER: Successfully read ECU identification information 13/Nov/2011 03:00:52.684: USER: Reading ECU identification option: systemSupplierECUSoftwareNumber 13/Nov/2011 03:00:52.687: LOG: Sent message with service ID ReadECUIdentification 13/Nov/2011 03:00:52.738: LOG: Received message with service ID ReadECUIdentificationPositiveResponse 13/Nov/2011 03:00:52.741: USER: Read ECU Identification systemSupplierECUSoftwareNumber: 1037352144, 13/Nov/2011 03:00:52.747: USER: Successfully read ECU identification information 13/Nov/2011 03:00:52.759: USER: Reading ECU identification option: calibrationDate 13/Nov/2011 03:00:52.762: LOG: Sent message with service ID ReadECUIdentification 13/Nov/2011 03:00:52.852: LOG: Received message with service ID ReadECUIdentificationPositiveResponse 13/Nov/2011 03:00:52.855: USER: Read ECU Identification calibrationDate: 8N0906018S , 0003, 0x000019C8, 0x00000000, 0x04D4, 1.8L R4/5VT , , 13/Nov/2011 03:00:52.862: USER: Successfully read ECU identification information 13/Nov/2011 03:00:52.880: USER: Reading ECU identification option: calibrationEquipmentSoftwareNumber 13/Nov/2011 03:00:52.887: LOG: Sent message with service ID ReadECUIdentification 13/Nov/2011 03:00:52.932: LOG: Received message with service ID ReadECUIdentificationPositiveResponse 13/Nov/2011 03:00:52.936: USER: Read ECU Identification calibrationEquipmentSoftwareNumber: 0x00000000, 13/Nov/2011 03:00:52.941: USER: Successfully read ECU identification information 13/Nov/2011 03:00:52.954: USER: 100% complete. 13/Nov/2011 03:00:52.962: USER: Reading ECU info succeeded. 13/Nov/2011 03:00:54.704: USER: Restoring Windows sleep mode. 13/Nov/2011 03:00:55.389: LOG: Sent message with service ID TesterPresent 13/Nov/2011 03:00:55.435: LOG: Received message with service ID TesterPresentPositiveReponse 13/Nov/2011 03:00:57.893: LOG: Sent message with service ID TesterPresent 13/Nov/2011 03:00:57.935: LOG: Received message with service ID TesterPresentPositiveReponse 13/Nov/2011 03:00:58.152: USER: Disabling Windows sleep mode. 13/Nov/2011 03:00:58.167: USER: Validating memory layout. 13/Nov/2011 03:00:58.180: USER: Reading ECU identification option: calibrationEquipmentSoftwareNumber 13/Nov/2011 03:00:58.183: LOG: Sent message with service ID ReadECUIdentification 13/Nov/2011 03:00:58.229: LOG: Received message with service ID ReadECUIdentificationPositiveResponse 13/Nov/2011 03:00:58.242: USER: Read ECU Identification calibrationEquipmentSoftwareNumber: 0x00000000, 13/Nov/2011 03:00:58.268: USER: Successfully read ECU identification information 13/Nov/2011 03:00:58.293: USER: ECU reports programming session preconditions have been met. 13/Nov/2011 03:00:58.301: USER: Negotiating communication timings. 13/Nov/2011 03:00:58.312: LOG: Reading current communication timings. 13/Nov/2011 03:00:58.327: LOG: Sent message with service ID AccessTimingParameters 13/Nov/2011 03:00:58.379: LOG: Received message with service ID AccessTimingParametersPositiveResponse 13/Nov/2011 03:00:58.383: LOG: Set timing parameters to new values. 13/Nov/2011 03:00:58.388: LOG: Reading communication timing defaults. 13/Nov/2011 03:00:58.446: LOG: Sent message with service ID AccessTimingParameters 13/Nov/2011 03:00:58.488: LOG: Received message with service ID AccessTimingParametersPositiveResponse 13/Nov/2011 03:00:58.492: LOG: Reading current communication timings. 13/Nov/2011 03:00:58.553: LOG: Sent message with service ID AccessTimingParameters 13/Nov/2011 03:00:58.599: LOG: Received message with service ID AccessTimingParametersPositiveResponse 13/Nov/2011 03:00:58.602: USER: Successfully changed to new communication timings. 13/Nov/2011 03:00:58.611: USER: Requesting security access. 13/Nov/2011 03:00:58.650: LOG: Sent message with service ID SecurityAccess 13/Nov/2011 03:00:58.687: LOG: Received message with service ID NegativeResponse 13/Nov/2011 03:00:58.692: LOG: Received negative response for service ID: SecurityAccess, with response code: ServiceNotSupported 13/Nov/2011 03:00:58.695: USER: ECU reports that security access is not supported. 13/Nov/2011 03:00:58.704: LOG: Starting diagnostic session type: ProgrammingSession 13/Nov/2011 03:00:58.716: USER: Starting diagnostic session. 13/Nov/2011 03:00:58.749: LOG: Sent message with service ID StartDiagnosticSession 13/Nov/2011 03:00:58.817: LOG: Received message with service ID NegativeResponse 13/Nov/2011 03:00:58.820: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: ConditionsNotCorrectOrRequestSequenceError 13/Nov/2011 03:00:58.823: USER: Start diagnostic session failed, ECU reports conditions not correct or sequence error. This can occur if the security lockout is running, or the engine is running. Please turn off the ignition and retry. 13/Nov/2011 03:00:58.830: USER: 100% complete. 13/Nov/2011 03:00:58.848: USER: Validating memory layout failed. 13/Nov/2011 03:01:01.270: LOG: Sent message with service ID TesterPresent 13/Nov/2011 03:01:01.312: LOG: Received message with service ID TesterPresentPositiveReponse 13/Nov/2011 03:01:01.994: USER: Restoring Windows sleep mode. 13/Nov/2011 03:01:03.791: LOG: Sent message with service ID TesterPresent 13/Nov/2011 03:01:03.832: LOG: Received message with service ID TesterPresentPositiveReponse 13/Nov/2011 03:01:06.314: LOG: Sent message with service ID TesterPresent 13/Nov/2011 03:01:06.450: USER: Disabling Windows sleep mode. 13/Nov/2011 03:01:06.461: USER: Reading ECU flash memory. 13/Nov/2011 03:01:06.480: USER: Reading ECU identification option: calibrationEquipmentSoftwareNumber 13/Nov/2011 03:01:06.496: LOG: Received message with service ID TesterPresentPositiveReponse 13/Nov/2011 03:01:06.543: LOG: Sent message with service ID ReadECUIdentification Title: Re: Start diagnostic session failed, ECU reports conditions HELPS!! Post by: Cablekid on November 13, 2011, 04:05:59 PM Had to split the log into 2 posts
Quote 13/Nov/2011 03:01:06.585: LOG: Received message with service ID ReadECUIdentificationPositiveResponse 13/Nov/2011 03:01:06.594: USER: Read ECU Identification calibrationEquipmentSoftwareNumber: 0x00000000, 13/Nov/2011 03:01:06.604: USER: Successfully read ECU identification information 13/Nov/2011 03:01:06.628: USER: ECU reports programming session preconditions have been met. 13/Nov/2011 03:01:06.636: USER: Negotiating communication timings. 13/Nov/2011 03:01:06.648: LOG: Reading current communication timings. 13/Nov/2011 03:01:06.720: LOG: Sent message with service ID AccessTimingParameters 13/Nov/2011 03:01:06.766: LOG: Received message with service ID AccessTimingParametersPositiveResponse 13/Nov/2011 03:01:06.769: LOG: Reading communication timing defaults. 13/Nov/2011 03:01:06.825: LOG: Sent message with service ID AccessTimingParameters 13/Nov/2011 03:01:06.869: LOG: Received message with service ID AccessTimingParametersPositiveResponse 13/Nov/2011 03:01:06.874: LOG: Reading current communication timings. 13/Nov/2011 03:01:06.930: LOG: Sent message with service ID AccessTimingParameters 13/Nov/2011 03:01:06.977: LOG: Received message with service ID AccessTimingParametersPositiveResponse 13/Nov/2011 03:01:06.980: USER: Successfully changed to new communication timings. 13/Nov/2011 03:01:06.987: USER: Requesting security access. 13/Nov/2011 03:01:07.015: LOG: Sent message with service ID SecurityAccess 13/Nov/2011 03:01:07.061: LOG: Received message with service ID NegativeResponse 13/Nov/2011 03:01:07.064: LOG: Received negative response for service ID: SecurityAccess, with response code: ServiceNotSupported 13/Nov/2011 03:01:07.067: USER: ECU reports that security access is not supported. 13/Nov/2011 03:01:07.077: LOG: Starting diagnostic session type: ProgrammingSession 13/Nov/2011 03:01:07.087: USER: Starting diagnostic session. 13/Nov/2011 03:01:07.122: LOG: Sent message with service ID StartDiagnosticSession 13/Nov/2011 03:01:07.181: LOG: Received message with service ID NegativeResponse 13/Nov/2011 03:01:07.186: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: ConditionsNotCorrectOrRequestSequenceError 13/Nov/2011 03:01:07.192: USER: Start diagnostic session failed, ECU reports conditions not correct or sequence error. This can occur if the security lockout is running, or the engine is running. Please turn off the ignition and retry. 13/Nov/2011 03:01:07.254: USER: 100% complete. 13/Nov/2011 03:01:07.260: USER: Reading ECU flash memory failed. 13/Nov/2011 03:01:09.643: LOG: Sent message with service ID TesterPresent 13/Nov/2011 03:01:09.689: LOG: Received message with service ID TesterPresentPositiveReponse 13/Nov/2011 03:01:09.778: USER: Restoring Windows sleep mode. 13/Nov/2011 03:01:12.166: LOG: Sent message with service ID TesterPresent 13/Nov/2011 03:01:12.206: LOG: Received message with service ID TesterPresentPositiveReponse 13/Nov/2011 03:01:13.631: USER: Disconnecting... 13/Nov/2011 03:01:13.696: LOG: Sent message with service ID StopCommunication 13/Nov/2011 03:01:13.736: LOG: Received message with service ID StopCommunicationPositiveResponse 13/Nov/2011 03:01:13.750: USER: Disconnected 13/Nov/2011 03:01:13.779: LOG: Closing FTDI device. 13/Nov/2011 03:01:13.792: LOG: Send receive thread now terminated. Title: Re: Start diagnostic session failed, ECU reports conditions HELPS!! Post by: Cablekid on November 13, 2011, 08:22:03 PM Nvm i got it reading by changing the baud rate
Title: Re: Start diagnostic session failed, ECU reports conditions HELPS!! Post by: Tony@NefMoto on December 09, 2011, 12:03:26 PM Which baud rate didn't work, and which did you have to use?
|