fat_chris
Newbie
Karma: +0/-0
 Offline
Posts: 13
|
 |
« on: July 22, 2021, 05:15:59 PM »
|
|
|
Hi All,
I've been using this software for awhile and have never had any issues flashing me7.1.1 and me7.5 ecu's using a blue ebay cable until recently
I get the following when trying to flash a me7.1.1 ecu can anyone give me some guidance. I have also tried using a hexcan cable in dumb mode with the same error message.
Thanks
" Successfully changed to new communication timings.
Requesting security access.
Security access granted.
Validating flash memory starts at 0x00800000 and ends at 0x00900000.
Memory layout is valid.
Starting to flash data block.
Requesting flash memory erase for address range 0x00800000 to 0x00803FFF.
Disconnecting because no response was received for the Tester Present message.
Disconnected
Writing ECU flash memory failed.
100% complete.
"
|
|
|
|
|
Logged
|
|
|
|
|
_nameless
|
|
« Reply #1 on: July 22, 2021, 06:02:58 PM »
|
|
|
Hi All,
I've been using this software for awhile and have never had any issues flashing me7.1.1 and me7.5 ecu's using a blue ebay cable until recently
I get the following when trying to flash a me7.1.1 ecu can anyone give me some guidance. I have also tried using a hexcan cable in dumb mode with the same error message.
Thanks
" Successfully changed to new communication timings.
Requesting security access.
Security access granted.
Validating flash memory starts at 0x00800000 and ends at 0x00900000.
Memory layout is valid.
Starting to flash data block.
Requesting flash memory erase for address range 0x00800000 to 0x00803FFF.
Disconnecting because no response was received for the Tester Present message.
Disconnected
Writing ECU flash memory failed.
100% complete.
"
Are you trying to read/ write a ecu that was already tuned? |
|
|
|
|
Logged
|
If you are broke or expecting free handouts DO NOT message me. I'll probably put you on blast if you do.
|
|
|
fat_chris
Newbie
Karma: +0/-0
Offline
Posts: 13
|
|
« Reply #2 on: July 22, 2021, 06:18:40 PM »
|
|
|
ecu is stock, the 3 others I tired were stock.
its been a few years since I've needed to write one of these but don't recall ever having any issues. I was able to flash the 95040 to off no problem on all 4 ecus
|
|
|
|
|
Logged
|
|
|
|
|
_nameless
|
|
« Reply #3 on: July 22, 2021, 06:27:34 PM »
|
|
|
well me7.1.1 doesnt have 95040 eeproms so... not sure how you did that considering they are 95080 or 95p08. Also, you could always just bootmode it . dont forget nefmoto flasher was never finished and has known bugs. By the sounds of it you do this semi regularly might wanna invest in some real tools.
|
|
|
|
|
Logged
|
If you are broke or expecting free handouts DO NOT message me. I'll probably put you on blast if you do.
|
|
|
|
nyet
|
|
« Reply #4 on: July 22, 2021, 06:42:25 PM »
|
|
|
What ECU P/N? Nef will not flash ST10
|
|
|
|
|
Logged
|
ME7.1 tuning guideECUx PlotME7Sum checksumTrim heatmap toolPlease do not ask me for tunes. I'm here to help people make their own. Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
|
|
|
fat_chris
Newbie
Karma: +0/-0
Offline
Posts: 13
|
|
« Reply #5 on: July 22, 2021, 08:06:49 PM »
|
|
|
well me7.1.1 doesnt have 95040 eeproms so... not sure how you did that considering they are 95080 or 95p08. Also, you could always just bootmode it . dont forget nefmoto flasher was never finished and has known bugs. By the sounds of it you do this semi regularly might wanna invest in some real tools.
These are all BDF Mk4 ecus. I used the 95040 tool with zero issues to turn the immo off. |
|
|
|
|
Logged
|
|
|
|
fat_chris
Newbie
Karma: +0/-0
Offline
Posts: 13
|
|
« Reply #6 on: July 22, 2021, 08:07:20 PM »
|
|
|
What ECU P/N? Nef will not flash ST10
022906032CS |
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #7 on: July 22, 2021, 08:12:07 PM »
|
|
|
Pretty sure those are ST10
anyway, not a lot of community support for them, tuning NA motors is mostly a waste of time
|
|
|
|
|
Logged
|
ME7.1 tuning guideECUx PlotME7Sum checksumTrim heatmap toolPlease do not ask me for tunes. I'm here to help people make their own. Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
|
|
|
fat_chris
Newbie
Karma: +0/-0
Offline
Posts: 13
|
|
« Reply #8 on: July 22, 2021, 08:34:32 PM »
|
|
|
Pretty sure those are ST10
anyway, not a lot of community support for them, tuning NA motors is mostly a waste of time
Unfortunately this is true. I’m needing to write a file for a swapped car. The 2.8 was taken out and a3.2 was swapped in. |
|
|
|
|
Logged
|
|
|
|
|
R32Dude
|
|
« Reply #9 on: July 23, 2021, 04:38:09 AM »
|
|
|
Its a c167, ST10s started with the MK5. It probably screwed up due to bad luck.
So you are trying to put the mk4 3.2 software on the originally 2.8 ecu ?
|
|
|
|
« Last Edit: July 23, 2021, 04:40:21 AM by R32Dude »
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #10 on: July 23, 2021, 11:00:43 AM »
|
|
|
Its a c167, ST10s started with the MK5. It probably screwed up due to bad luck.
So you are trying to put the mk4 3.2 software on the originally 2.8 ecu ?
Ya, verified, those are C167 and should work with the nef flasher. Something else is up. |
|
|
|
|
Logged
|
ME7.1 tuning guideECUx PlotME7Sum checksumTrim heatmap toolPlease do not ask me for tunes. I'm here to help people make their own. Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
|
|
|
fat_chris
Newbie
Karma: +0/-0
Offline
Posts: 13
|
|
« Reply #11 on: July 25, 2021, 02:34:34 PM »
|
|
|
Its a c167, ST10s started with the MK5. It probably screwed up due to bad luck.
So you are trying to put the mk4 3.2 software on the originally 2.8 ecu ?
Yes, finding stock r32 computers are very difficult at this point but 2.8 ecu are easy to find. Happy to order another cable if that's the issue but I'm unsure. I've also tired a HEX-NET cable in DUMB mode as well with same results. |
|
|
|
|
Logged
|
|
|
|
krawciox
Newbie
Karma: +1/-0
Offline
Posts: 18
|
|
« Reply #12 on: February 21, 2025, 09:12:14 AM »
|
|
|
Hello, I'd like to dig out a thread a bit, I'm facing a similar problem, ECU is now a 07K906032AR me 7.1.1 on c167 cpu, very similar to 3.2 c167 versions I can't read or write it by OBD with nefmoto. Kess Clone works fine on both read and write by OBD. Memory is 100% 29F800BB - checked inside when doing immo off. Things I've done so far - edited in Flash and put with kess: Changes from reply #36 and #43 from thread http://nefariousmotorsports.com/forum/index.php?topic=21516.30and I Found and changed string described in Reply #1 from thread: http://nefariousmotorsports.com/forum/index.php?topic=5165.0Security Access is Granted but no luck on reading and writing Attaching log from nefmoto: 21-lut-2025 03:29:01.658: USER: Writing ECU flash memory.
21-lut-2025 03:29:01.699: LOG: Reading ECU identification option: 0x9C
21-lut-2025 03:29:01.715: LOG: Sent message with service ID ReadECUIdentification
21-lut-2025 03:29:01.759: LOG: Received message with service ID: ReadECUIdentificationPositiveResponse
21-lut-2025 03:29:01.766: LOG: Read ECU identification option: 0x9C
21-lut-2025 03:29:01.766: LOG: Successfully read ECU identification information
21-lut-2025 03:29:01.788: USER: ECU reports programming session preconditions have been met.
21-lut-2025 03:29:01.792: USER: Negotiating communication timings.
21-lut-2025 03:29:01.793: LOG: Reading current communication timings.
21-lut-2025 03:29:01.838: LOG: Sent message with service ID AccessTimingParameters
21-lut-2025 03:29:01.882: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
21-lut-2025 03:29:01.887: LOG: Set timing parameters to new values.
21-lut-2025 03:29:01.888: LOG: Setting communication timing to defaults.
21-lut-2025 03:29:01.935: LOG: Sent message with service ID AccessTimingParameters
21-lut-2025 03:29:01.975: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
21-lut-2025 03:29:01.975: LOG: Reading current communication timings.
21-lut-2025 03:29:02.031: LOG: Sent message with service ID AccessTimingParameters
21-lut-2025 03:29:02.081: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
21-lut-2025 03:29:02.081: USER: Successfully changed to new communication timings.
21-lut-2025 03:29:02.086: USER: Requesting security access.
21-lut-2025 03:29:02.102: LOG: Sent message with service ID SecurityAccess
21-lut-2025 03:29:02.149: LOG: Received message with service ID: SecurityAccessPositiveResponse
21-lut-2025 03:29:02.156: LOG: Received security seed, sending security key.
21-lut-2025 03:29:02.194: LOG: Sent message with service ID SecurityAccess
21-lut-2025 03:29:02.237: LOG: Received message with service ID: SecurityAccessPositiveResponse
21-lut-2025 03:29:02.237: USER: Security access granted.
21-lut-2025 03:29:02.244: LOG: Starting ProgrammingSession diagnostic session with 9600 baud rate.
21-lut-2025 03:29:02.245: USER: Starting diagnostic session.
21-lut-2025 03:29:02.272: LOG: Sent message with service ID StartDiagnosticSession
21-lut-2025 03:29:02.317: LOG: Received message with service ID: NegativeResponse
21-lut-2025 03:29:02.325: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SubFunctionNotSupported_InvalidFormat
21-lut-2025 03:29:02.353: LOG: Starting ProgrammingSession diagnostic session without baud rate.
21-lut-2025 03:29:02.354: LOG: Start diagnostic session failed, ECU reports sub function not supported or invalid format. Trying again with a different format.
21-lut-2025 03:29:02.371: LOG: Sent message with service ID StartDiagnosticSession
21-lut-2025 03:29:02.407: LOG: Received message with service ID: NegativeResponse
21-lut-2025 03:29:02.408: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SubFunctionNotSupported_InvalidFormat
21-lut-2025 03:29:02.410: LOG: Starting ProgrammingSession diagnostic session without baud rate.
21-lut-2025 03:29:02.412: LOG: Start diagnostic session failed, ECU reports sub function not supported or invalid format. Trying again with a different format.
21-lut-2025 03:29:02.443: LOG: Sent message with service ID StartDiagnosticSession
21-lut-2025 03:29:02.486: LOG: Received message with service ID: NegativeResponse
21-lut-2025 03:29:02.487: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SubFunctionNotSupported_InvalidFormat
21-lut-2025 03:29:02.487: USER: Unable to properly start diagnostic session, attempting to continue with current undefined session.
21-lut-2025 03:29:02.488: USER: Negotiating communication timings.
21-lut-2025 03:29:02.489: LOG: Reading current communication timings.
21-lut-2025 03:29:02.540: LOG: Sent message with service ID AccessTimingParameters
21-lut-2025 03:29:02.580: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
21-lut-2025 03:29:02.581: LOG: Reading communication timing limits.
21-lut-2025 03:29:02.637: LOG: Sent message with service ID AccessTimingParameters
21-lut-2025 03:29:02.681: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
21-lut-2025 03:29:02.682: LOG: Requesting communication at timing limits.
21-lut-2025 03:29:02.733: LOG: Sent message with service ID AccessTimingParameters
21-lut-2025 03:29:02.775: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
21-lut-2025 03:29:02.775: LOG: Set timing parameters to new values.
21-lut-2025 03:29:02.776: USER: Successfully changed to new communication timings.
21-lut-2025 03:29:02.776: USER: Requesting security access.
21-lut-2025 03:29:02.778: LOG: Sent message with service ID SecurityAccess
21-lut-2025 03:29:02.799: LOG: Received message with service ID: SecurityAccessPositiveResponse
21-lut-2025 03:29:02.800: USER: Security access granted.
21-lut-2025 03:29:02.802: USER: Validating flash memory starts at 0x00800000 and ends at 0x00900000.
21-lut-2025 03:29:02.806: LOG: Sent message with service ID RequestUpload
21-lut-2025 03:29:02.827: LOG: Received message with service ID: NegativeResponse
21-lut-2025 03:29:02.827: LOG: Received negative response for service ID: RequestUpload, with response code: ServiceNotSupported
21-lut-2025 03:29:02.832: USER: Validation failed, ECU reports RequestUpload service is not supported. RequestUpload may have been disabled by aftermarket engine software.
21-lut-2025 03:29:02.833: USER: Memory layout validation failed. EDIT: Software is stock with some tweaks like: n112, j299, LDP, rear o2 off, know it 100% because I sent it by myself on a start by Kess. |
|
|
|
« Last Edit: February 21, 2025, 09:18:01 AM by krawciox »
|
Logged
|
|
|
|
Artemisia
Full Member
Karma: +18/-0
Offline
Posts: 83
|
|
« Reply #13 on: February 21, 2025, 03:50:00 PM »
|
|
|
Hello, I'd like to dig out a thread a bit, I'm facing a similar problem, ECU is now a 07K906032AR me 7.1.1 on c167 cpu, very similar to 3.2 c167 versions I can't read or write it by OBD with nefmoto. Kess Clone works fine on both read and write by OBD. Memory is 100% 29F800BB - checked inside when doing immo off. Things I've done so far - edited in Flash and put with kess: Changes from reply #36 and #43 from thread http://nefariousmotorsports.com/forum/index.php?topic=21516.30and I Found and changed string described in Reply #1 from thread: http://nefariousmotorsports.com/forum/index.php?topic=5165.0Security Access is Granted but no luck on reading and writing Attaching log from nefmoto: 21-lut-2025 03:29:01.658: USER: Writing ECU flash memory.
21-lut-2025 03:29:01.699: LOG: Reading ECU identification option: 0x9C
21-lut-2025 03:29:01.715: LOG: Sent message with service ID ReadECUIdentification
21-lut-2025 03:29:01.759: LOG: Received message with service ID: ReadECUIdentificationPositiveResponse
21-lut-2025 03:29:01.766: LOG: Read ECU identification option: 0x9C
21-lut-2025 03:29:01.766: LOG: Successfully read ECU identification information
21-lut-2025 03:29:01.788: USER: ECU reports programming session preconditions have been met.
21-lut-2025 03:29:01.792: USER: Negotiating communication timings.
21-lut-2025 03:29:01.793: LOG: Reading current communication timings.
21-lut-2025 03:29:01.838: LOG: Sent message with service ID AccessTimingParameters
21-lut-2025 03:29:01.882: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
21-lut-2025 03:29:01.887: LOG: Set timing parameters to new values.
21-lut-2025 03:29:01.888: LOG: Setting communication timing to defaults.
21-lut-2025 03:29:01.935: LOG: Sent message with service ID AccessTimingParameters
21-lut-2025 03:29:01.975: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
21-lut-2025 03:29:01.975: LOG: Reading current communication timings.
21-lut-2025 03:29:02.031: LOG: Sent message with service ID AccessTimingParameters
21-lut-2025 03:29:02.081: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
21-lut-2025 03:29:02.081: USER: Successfully changed to new communication timings.
21-lut-2025 03:29:02.086: USER: Requesting security access.
21-lut-2025 03:29:02.102: LOG: Sent message with service ID SecurityAccess
21-lut-2025 03:29:02.149: LOG: Received message with service ID: SecurityAccessPositiveResponse
21-lut-2025 03:29:02.156: LOG: Received security seed, sending security key.
21-lut-2025 03:29:02.194: LOG: Sent message with service ID SecurityAccess
21-lut-2025 03:29:02.237: LOG: Received message with service ID: SecurityAccessPositiveResponse
21-lut-2025 03:29:02.237: USER: Security access granted.
21-lut-2025 03:29:02.244: LOG: Starting ProgrammingSession diagnostic session with 9600 baud rate.
21-lut-2025 03:29:02.245: USER: Starting diagnostic session.
21-lut-2025 03:29:02.272: LOG: Sent message with service ID StartDiagnosticSession
21-lut-2025 03:29:02.317: LOG: Received message with service ID: NegativeResponse
21-lut-2025 03:29:02.325: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SubFunctionNotSupported_InvalidFormat
21-lut-2025 03:29:02.353: LOG: Starting ProgrammingSession diagnostic session without baud rate.
21-lut-2025 03:29:02.354: LOG: Start diagnostic session failed, ECU reports sub function not supported or invalid format. Trying again with a different format.
21-lut-2025 03:29:02.371: LOG: Sent message with service ID StartDiagnosticSession
21-lut-2025 03:29:02.407: LOG: Received message with service ID: NegativeResponse
21-lut-2025 03:29:02.408: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SubFunctionNotSupported_InvalidFormat
21-lut-2025 03:29:02.410: LOG: Starting ProgrammingSession diagnostic session without baud rate.
21-lut-2025 03:29:02.412: LOG: Start diagnostic session failed, ECU reports sub function not supported or invalid format. Trying again with a different format.
21-lut-2025 03:29:02.443: LOG: Sent message with service ID StartDiagnosticSession
21-lut-2025 03:29:02.486: LOG: Received message with service ID: NegativeResponse
21-lut-2025 03:29:02.487: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SubFunctionNotSupported_InvalidFormat
21-lut-2025 03:29:02.487: USER: Unable to properly start diagnostic session, attempting to continue with current undefined session.
21-lut-2025 03:29:02.488: USER: Negotiating communication timings.
21-lut-2025 03:29:02.489: LOG: Reading current communication timings.
21-lut-2025 03:29:02.540: LOG: Sent message with service ID AccessTimingParameters
21-lut-2025 03:29:02.580: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
21-lut-2025 03:29:02.581: LOG: Reading communication timing limits.
21-lut-2025 03:29:02.637: LOG: Sent message with service ID AccessTimingParameters
21-lut-2025 03:29:02.681: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
21-lut-2025 03:29:02.682: LOG: Requesting communication at timing limits.
21-lut-2025 03:29:02.733: LOG: Sent message with service ID AccessTimingParameters
21-lut-2025 03:29:02.775: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
21-lut-2025 03:29:02.775: LOG: Set timing parameters to new values.
21-lut-2025 03:29:02.776: USER: Successfully changed to new communication timings.
21-lut-2025 03:29:02.776: USER: Requesting security access.
21-lut-2025 03:29:02.778: LOG: Sent message with service ID SecurityAccess
21-lut-2025 03:29:02.799: LOG: Received message with service ID: SecurityAccessPositiveResponse
21-lut-2025 03:29:02.800: USER: Security access granted.
21-lut-2025 03:29:02.802: USER: Validating flash memory starts at 0x00800000 and ends at 0x00900000.
21-lut-2025 03:29:02.806: LOG: Sent message with service ID RequestUpload
21-lut-2025 03:29:02.827: LOG: Received message with service ID: NegativeResponse
21-lut-2025 03:29:02.827: LOG: Received negative response for service ID: RequestUpload, with response code: ServiceNotSupported
21-lut-2025 03:29:02.832: USER: Validation failed, ECU reports RequestUpload service is not supported. RequestUpload may have been disabled by aftermarket engine software.
21-lut-2025 03:29:02.833: USER: Memory layout validation failed. EDIT: Software is stock with some tweaks like: n112, j299, LDP, rear o2 off, know it 100% because I sent it by myself on a start by Kess. Required services for flash programming have been moved over to the can-bus (TP2.0) on the 07K906032AR ECU. NefMoto does not support it. If you want to use NefMoto, you can look for an early Beetle ECU (Pre-2007) like 07K906032B/C |
|
|
|
|
Logged
|
|
|
|
krawciox
Newbie
Karma: +1/-0
Offline
Posts: 18
|
|
« Reply #14 on: February 21, 2025, 04:54:56 PM »
|
|
|
Thank You, unfortunately I live in Poland where access to VW parts from US market VWs is poor. I'll stay with 032AR ecu. Just need fo found any sollution to flash it faster for tunning. Whole write with kess lasts ~10mins
|
|
|
|
|
Logged
|
|
|
|
|
