Title: ECU reports that security access is not supported.
Post by: gareth_iowc on May 05, 2017, 04:10:21 PM
Evening all, so i am very new to this. on my first attempt at connected to this ecu on the bench nefmoto gave me a message about the immob being active. so i bought the eeprom programmer and flashed it with the replacement immo off file. I no longer have that message but i get this new one - ECU reports that security access is not supported. is that something to worry about? the read is failing and i have attached the log. is it failing because it's a stock map? ECU Taken from a golf mk4 arz - 06A906032AR 1.8L R4/5VT Mem layout i have chosen - 29f400bb i bought this ecu second hand so i can understand things before i try it on my own. any help would be great. thanks 06/May/2017 12:02:19.906: LOG: Sent message with service ID TesterPresent
06/May/2017 12:02:19.953: LOG: Received message with service ID: TesterPresentPositiveReponse
06/May/2017 12:02:22.437: LOG: Sent message with service ID TesterPresent
06/May/2017 12:02:22.484: LOG: Received message with service ID: TesterPresentPositiveReponse
06/May/2017 12:02:24.968: LOG: Sent message with service ID TesterPresent
06/May/2017 12:02:25.015: LOG: Received message with service ID: TesterPresentPositiveReponse
06/May/2017 12:02:27.500: LOG: Sent message with service ID TesterPresent
06/May/2017 12:02:27.546: LOG: Received message with service ID: TesterPresentPositiveReponse
06/May/2017 12:02:30.046: LOG: Sent message with service ID TesterPresent
06/May/2017 12:02:30.093: LOG: Received message with service ID: TesterPresentPositiveReponse
06/May/2017 12:02:32.593: LOG: Sent message with service ID TesterPresent
06/May/2017 12:02:32.640: LOG: Received message with service ID: TesterPresentPositiveReponse
06/May/2017 12:02:35.125: LOG: Sent message with service ID TesterPresent
06/May/2017 12:02:35.171: LOG: Received message with service ID: TesterPresentPositiveReponse
06/May/2017 12:02:37.656: LOG: Sent message with service ID TesterPresent
06/May/2017 12:02:37.703: LOG: Received message with service ID: TesterPresentPositiveReponse
06/May/2017 12:02:40.187: LOG: Sent message with service ID TesterPresent
06/May/2017 12:02:40.234: LOG: Received message with service ID: TesterPresentPositiveReponse
06/May/2017 12:02:42.546: LOG: User Prompt - Title: Confirm Full Read ECU Flash Memory Message: If you are ready to read, confirm the following things:
1) You have loaded a valid memory layout for the ECU.
2) The engine is not running.
Note: Some non-standard flash memory chips may prevent reading the flash memory.
Click OK to confirm, otherwise Cancel. Result: OK
06/May/2017 12:02:42.546: USER: Disabling Windows sleep mode.
06/May/2017 12:02:42.578: USER: Reading ECU flash memory.
06/May/2017 12:02:42.609: LOG: Reading ECU identification option: 0x9C
06/May/2017 12:02:42.640: LOG: Sent message with service ID ReadECUIdentification
06/May/2017 12:02:42.687: LOG: Received message with service ID: ReadECUIdentificationPositiveResponse
06/May/2017 12:02:42.687: USER: Failed to start diagnostic session.
06/May/2017 12:02:42.687: LOG: Read ECU identification option: 0x9C
06/May/2017 12:02:42.687: LOG: Successfully read ECU identification information
06/May/2017 12:02:42.687: USER: ECU reports programming session preconditions have been met.
06/May/2017 12:02:42.687: USER: Negotiating communication timings.
06/May/2017 12:02:42.687: LOG: Reading current communication timings.
06/May/2017 12:02:42.687: LOG: Received unhandled message with service ID: ReadECUIdentificationPositiveResponse
06/May/2017 12:02:42.750: LOG: Sent message with service ID AccessTimingParameters
06/May/2017 12:02:42.796: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
06/May/2017 12:02:42.796: LOG: Set timing parameters to new values.
06/May/2017 12:02:42.796: LOG: Setting communication timing to defaults.
06/May/2017 12:02:42.859: LOG: Sent message with service ID AccessTimingParameters
06/May/2017 12:02:42.906: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
06/May/2017 12:02:42.906: LOG: Reading current communication timings.
06/May/2017 12:02:42.968: LOG: Sent message with service ID AccessTimingParameters
06/May/2017 12:02:43.015: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
06/May/2017 12:02:43.015: USER: Successfully changed to new communication timings.
06/May/2017 12:02:43.015: USER: Requesting security access.
06/May/2017 12:02:43.046: LOG: Sent message with service ID SecurityAccess
06/May/2017 12:02:43.093: LOG: Received message with service ID: NegativeResponse
06/May/2017 12:02:43.093: LOG: Received negative response for service ID: SecurityAccess, with response code: ServiceNotSupported
06/May/2017 12:02:43.093: USER: ECU reports that security access is not supported.
06/May/2017 12:02:43.093: LOG: Starting ProgrammingSession diagnostic session with 124800 baud rate.
06/May/2017 12:02:43.093: USER: Starting diagnostic session.
06/May/2017 12:02:43.125: LOG: Sent message with service ID StartDiagnosticSession
06/May/2017 12:02:43.171: LOG: Received message with service ID: NegativeResponse
06/May/2017 12:02:43.171: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
06/May/2017 12:02:43.218: LOG: Received message with service ID: NegativeResponse
06/May/2017 12:02:43.218: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
06/May/2017 12:02:43.250: LOG: Received message with service ID: NegativeResponse
06/May/2017 12:02:43.250: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
06/May/2017 12:02:43.296: LOG: Received message with service ID: NegativeResponse
06/May/2017 12:02:43.296: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
06/May/2017 12:02:43.343: LOG: Received message with service ID: NegativeResponse
06/May/2017 12:02:43.343: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
06/May/2017 12:02:53.156: LOG: Sent message with service ID TesterPresent
06/May/2017 12:02:53.265: LOG: Message received no replies.
06/May/2017 12:02:53.265: LOG: Resending message. Send attempts: 2
06/May/2017 12:02:53.281: LOG: Sent message with service ID TesterPresent
06/May/2017 12:02:53.390: LOG: Message received no replies.
06/May/2017 12:02:53.390: LOG: Resending message. Send attempts: 3
06/May/2017 12:02:53.406: LOG: Sent message with service ID TesterPresent
06/May/2017 12:02:53.515: LOG: Message received no replies.
06/May/2017 12:02:53.515: LOG: Failed to send message 3 times, message send failed.
06/May/2017 12:02:53.515: USER: Disconnecting because no response was received for the Tester Present message.
06/May/2017 12:02:53.515: USER: Disconnected
06/May/2017 12:02:53.531: USER: Reading ECU flash memory failed.
06/May/2017 12:02:53.593: LOG: Closing FTDI device.
06/May/2017 12:02:53.640: LOG: Send receive thread now terminated.
06/May/2017 12:02:56.281: LOG: User Prompt - Title: Reading ECU Flash Memory Complete Message: Reading ECU flash memory failed. Result: OK
06/May/2017 12:02:56.281: USER: 100% complete.
06/May/2017 12:02:56.312: USER: Restoring Windows sleep mode.
Title: Re: ECU reports that security access is not supported.
Post by: nyet on May 05, 2017, 10:18:17 PM
the read is failing and i have attached the log. is it failing because it's a stock map?
If anything, it is failing because it isn't stock.
Title: Re: ECU reports that security access is not supported.
Post by: gt-innovation on May 06, 2017, 01:47:12 AM
Evening all, so i am very new to this. on my first attempt at connected to this ecu on the bench nefmoto gave me a message about the immob being active. so i bought the eeprom programmer and flashed it with the replacement immo off file. I no longer have that message but i get this new one - ECU reports that security access is not supported. is that something to worry about? the read is failing and i have attached the log. is it failing because it's a stock map? ECU Taken from a golf mk4 arz - 06A906032AR 1.8L R4/5VT Mem layout i have chosen - 29f400bb i bought this ecu second hand so i can understand things before i try it on my own. any help would be great. thanks 06/May/2017 12:02:19.906: LOG: Sent message with service ID TesterPresent
06/May/2017 12:02:19.953: LOG: Received message with service ID: TesterPresentPositiveReponse
06/May/2017 12:02:22.437: LOG: Sent message with service ID TesterPresent
06/May/2017 12:02:22.484: LOG: Received message with service ID: TesterPresentPositiveReponse
06/May/2017 12:02:24.968: LOG: Sent message with service ID TesterPresent
06/May/2017 12:02:25.015: LOG: Received message with service ID: TesterPresentPositiveReponse
06/May/2017 12:02:27.500: LOG: Sent message with service ID TesterPresent
06/May/2017 12:02:27.546: LOG: Received message with service ID: TesterPresentPositiveReponse
06/May/2017 12:02:30.046: LOG: Sent message with service ID TesterPresent
06/May/2017 12:02:30.093: LOG: Received message with service ID: TesterPresentPositiveReponse
06/May/2017 12:02:32.593: LOG: Sent message with service ID TesterPresent
06/May/2017 12:02:32.640: LOG: Received message with service ID: TesterPresentPositiveReponse
06/May/2017 12:02:35.125: LOG: Sent message with service ID TesterPresent
06/May/2017 12:02:35.171: LOG: Received message with service ID: TesterPresentPositiveReponse
06/May/2017 12:02:37.656: LOG: Sent message with service ID TesterPresent
06/May/2017 12:02:37.703: LOG: Received message with service ID: TesterPresentPositiveReponse
06/May/2017 12:02:40.187: LOG: Sent message with service ID TesterPresent
06/May/2017 12:02:40.234: LOG: Received message with service ID: TesterPresentPositiveReponse
06/May/2017 12:02:42.546: LOG: User Prompt - Title: Confirm Full Read ECU Flash Memory Message: If you are ready to read, confirm the following things:
1) You have loaded a valid memory layout for the ECU.
2) The engine is not running.
Note: Some non-standard flash memory chips may prevent reading the flash memory.
Click OK to confirm, otherwise Cancel. Result: OK
06/May/2017 12:02:42.546: USER: Disabling Windows sleep mode.
06/May/2017 12:02:42.578: USER: Reading ECU flash memory.
06/May/2017 12:02:42.609: LOG: Reading ECU identification option: 0x9C
06/May/2017 12:02:42.640: LOG: Sent message with service ID ReadECUIdentification
06/May/2017 12:02:42.687: LOG: Received message with service ID: ReadECUIdentificationPositiveResponse
06/May/2017 12:02:42.687: USER: Failed to start diagnostic session.
06/May/2017 12:02:42.687: LOG: Read ECU identification option: 0x9C
06/May/2017 12:02:42.687: LOG: Successfully read ECU identification information
06/May/2017 12:02:42.687: USER: ECU reports programming session preconditions have been met.
06/May/2017 12:02:42.687: USER: Negotiating communication timings.
06/May/2017 12:02:42.687: LOG: Reading current communication timings.
06/May/2017 12:02:42.687: LOG: Received unhandled message with service ID: ReadECUIdentificationPositiveResponse
06/May/2017 12:02:42.750: LOG: Sent message with service ID AccessTimingParameters
06/May/2017 12:02:42.796: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
06/May/2017 12:02:42.796: LOG: Set timing parameters to new values.
06/May/2017 12:02:42.796: LOG: Setting communication timing to defaults.
06/May/2017 12:02:42.859: LOG: Sent message with service ID AccessTimingParameters
06/May/2017 12:02:42.906: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
06/May/2017 12:02:42.906: LOG: Reading current communication timings.
06/May/2017 12:02:42.968: LOG: Sent message with service ID AccessTimingParameters
06/May/2017 12:02:43.015: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
06/May/2017 12:02:43.015: USER: Successfully changed to new communication timings.
06/May/2017 12:02:43.015: USER: Requesting security access.
06/May/2017 12:02:43.046: LOG: Sent message with service ID SecurityAccess
06/May/2017 12:02:43.093: LOG: Received message with service ID: NegativeResponse
06/May/2017 12:02:43.093: LOG: Received negative response for service ID: SecurityAccess, with response code: ServiceNotSupported
06/May/2017 12:02:43.093: USER: ECU reports that security access is not supported.
06/May/2017 12:02:43.093: LOG: Starting ProgrammingSession diagnostic session with 124800 baud rate.
06/May/2017 12:02:43.093: USER: Starting diagnostic session.
06/May/2017 12:02:43.125: LOG: Sent message with service ID StartDiagnosticSession
06/May/2017 12:02:43.171: LOG: Received message with service ID: NegativeResponse
06/May/2017 12:02:43.171: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
06/May/2017 12:02:43.218: LOG: Received message with service ID: NegativeResponse
06/May/2017 12:02:43.218: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
06/May/2017 12:02:43.250: LOG: Received message with service ID: NegativeResponse
06/May/2017 12:02:43.250: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
06/May/2017 12:02:43.296: LOG: Received message with service ID: NegativeResponse
06/May/2017 12:02:43.296: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
06/May/2017 12:02:43.343: LOG: Received message with service ID: NegativeResponse
06/May/2017 12:02:43.343: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
06/May/2017 12:02:53.156: LOG: Sent message with service ID TesterPresent
06/May/2017 12:02:53.265: LOG: Message received no replies.
06/May/2017 12:02:53.265: LOG: Resending message. Send attempts: 2
06/May/2017 12:02:53.281: LOG: Sent message with service ID TesterPresent
06/May/2017 12:02:53.390: LOG: Message received no replies.
06/May/2017 12:02:53.390: LOG: Resending message. Send attempts: 3
06/May/2017 12:02:53.406: LOG: Sent message with service ID TesterPresent
06/May/2017 12:02:53.515: LOG: Message received no replies.
06/May/2017 12:02:53.515: LOG: Failed to send message 3 times, message send failed.
06/May/2017 12:02:53.515: USER: Disconnecting because no response was received for the Tester Present message.
06/May/2017 12:02:53.515: USER: Disconnected
06/May/2017 12:02:53.531: USER: Reading ECU flash memory failed.
06/May/2017 12:02:53.593: LOG: Closing FTDI device.
06/May/2017 12:02:53.640: LOG: Send receive thread now terminated.
06/May/2017 12:02:56.281: LOG: User Prompt - Title: Reading ECU Flash Memory Complete Message: Reading ECU flash memory failed. Result: OK
06/May/2017 12:02:56.281: USER: 100% complete.
06/May/2017 12:02:56.312: USER: Restoring Windows sleep mode. Easiest way to bypass that is using MPPS over obd or any other tool that will boot mode it on the bench.You can also desolder the chip but this requires some previous experience.
Title: Re: ECU reports that security access is not supported.
Post by: gareth_iowc on May 06, 2017, 05:19:16 PM
thanks for the help guys.
so ECU reports that security access is not supported is normal for an ecu with the disabled immobiliser?
after talking to the guy i got it from he said yes it was stage 1 mapped by the previous owner. unsure who mapped it.
so i will have to look into boot mode to read the current data.
on a side note i plugged it into my car today to see if the immobiliser had been disabled and it started up.
but...... from cold it started up not on choke and there was no response from the electronic throttle pedal.
has something happened to the map from trying to read it?
are the ecu's interchangeable on the FBW 7.5s?
My Engine - AJQ - ECU - 06a 906 032 r
Test ECU Engine - ARZ - ECU - 06a 906 032 ar
Thanks
Title: Re: ECU reports that security access is not supported.
Post by: aef on May 08, 2017, 02:25:23 AM
You have to read more.
Try to compare stock injector size and maf part number on both engines.
After you read the s4 wiki you can also compare krkte and mlhfm and so on :)
Title: Re: ECU reports that security access is not supported.
Post by: gareth_iowc on May 08, 2017, 02:42:33 AM
Ok thanks.
Yeah sorry i know my knowledge is very basic at this point. It's a lot to take in :)
Title: Re: ECU reports that security access is not supported.
Post by: fknbrkn on May 08, 2017, 03:47:09 AM
+12v to pin121
Title: Re: ECU reports that security access is not supported.
Post by: gt-innovation on June 17, 2017, 03:26:01 PM
thanks for the help guys.
so ECU reports that security access is not supported is normal for an ecu with the disabled immobiliser?
after talking to the guy i got it from he said yes it was stage 1 mapped by the previous owner. unsure who mapped it.
so i will have to look into boot mode to read the current data.
on a side note i plugged it into my car today to see if the immobiliser had been disabled and it started up.
but...... from cold it started up not on choke and there was no response from the electronic throttle pedal.
has something happened to the map from trying to read it?
are the ecu's interchangeable on the FBW 7.5s?
My Engine - AJQ - ECU - 06a 906 032 r
Test ECU Engine - ARZ - ECU - 06a 906 032 ar
Thanks
BTW i had the same ecu last week (06a 906 032 ar)in a k04 s3 setup conversion and ecu was locked too so cmd couldn`t read but by removing the fuse 11 (tacho) i was able to read with mpps.However i used ktag too so if you need working eeprom read let me know.
Title: Re: ECU reports that security access is not supported.
Post by: b3q on August 01, 2020, 02:41:55 AM
+12v to pin121
That worked. Overlooked that pin on the schematic.
|