Title: Failing to read Motronic 7.1.1 G VR6 24V BDE
Post by: Darkbound on September 06, 2017, 12:06:08 PM
Hey guys! My first post here, I am really excited that I started this journey. I tried to read the ECU on my VR6, but for some reason I could not. I tried to follow the "Getting Started" guide as closely as possible. The Nefmoto software us connecting successfully but not reading. I was connecting at 9600 baudrate. Also I could not figure out if my ecu memory size was 512kb or 1024kb, but neither of the memory layouts worked. My info: Motronic ME7.1.1 G VAG NUMBER: 022 906 032 BG The car is late 2002 Golf MK4 VR6 24V, Engine code is BDE I am a complete newbie and I am trying to learn :) not to save money, but I just like knowing whats going on with my car, and yes my end goal is to remap it and I realize that this will take a loooot of hours of reading and testing, like I said I just like knowing whats going on with my car, its easy to pay others to do the job, I don't like easy :D This is the full log of the Nefmoto console: Validated FTDI device is in dumb mode.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP2000 session.
Connected
Disabling Windows sleep mode.
Reading all ECU info.
Starting diagnostic session.
Unable to properly start diagnostic session, attempting to continue with current undefined session.
Negotiating communication timings.
Successfully changed to new communication timings.
0% complete.
20% complete.
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP2000 session.
Connected
Disabling Windows sleep mode.
Reading all ECU info.
Starting diagnostic session.
Unable to properly start diagnostic session, attempting to continue with current undefined session.
Negotiating communication timings.
Successfully changed to new communication timings.
0% complete.
20% complete.
40% complete.
60% complete.
80% complete.
100% complete.
Read 5 ECU info entries:
0x92, System Supplier ECU Hardware Number: 0261207350
0x94, System Supplier ECU Software Number: 1037362356
0x91, Vehicle Manufacturer ECU Hardware Number: 0x0D, , 0xFF
0x9B, Calibration Date: 022906032BG , 0004, 0x03000084, 0x00000000, 0x7AB6, MOTRONIC ME7.1., 1G
0x9C, Calibration Equiment Software Number: 0x00000000
Restoring Windows sleep mode.
Disabling Windows sleep mode.
Reading ECU flash memory.
ECU reports programming session preconditions have been met.
Negotiating communication timings.
Successfully changed to new communication timings.
Requesting security access.
Security access granted.
Starting diagnostic session.
Successfully started diagnostic session.
Negotiating communication timings.
Successfully changed to new communication timings.
Requesting security access.
Security access granted.
Validating flash memory starts at 0x00800000 and ends at 0x00900000.
Validation failed, ECU reports RequestUpload service is not supported. RequestUpload may have been disabled by aftermarket engine software.
Memory layout validation failed.
Reading ECU flash memory failed. Trying to force ECU to recognize read operation is complete.
Finished forcing ECU to recognize that failed read operation is complete.
Reading ECU flash memory failed.
100% complete.
Restoring Windows sleep mode.
Disabling Windows sleep mode.
Reading ECU flash memory.
Negotiating communication timings.
Successfully changed to new communication timings.
Requesting security access.
Security access granted.
Negotiating communication timings.
Successfully changed to new communication timings.
Requesting security access.
Security access granted.
Validating flash memory starts at 0x00800000 and ends at 0x00900000.
Validation failed, ECU reports RequestUpload service is not supported. RequestUpload may have been disabled by aftermarket engine software.
Memory layout validation failed.
Reading ECU flash memory failed. Trying to force ECU to recognize read operation is complete.
Finished forcing ECU to recognize that failed read operation is complete.
Reading ECU flash memory failed.
100% complete.
Restoring Windows sleep mode.
Disabling Windows sleep mode.
Reading ECU flash memory.
Negotiating communication timings.
Successfully changed to new communication timings.
Requesting security access.
Security access granted.
Negotiating communication timings.
Successfully changed to new communication timings.
Requesting security access.
Security access granted.
Validating flash memory starts at 0x00800000 and ends at 0x00880000.
Validation failed, ECU reports RequestUpload service is not supported. RequestUpload may have been disabled by aftermarket engine software.
Memory layout validation failed.
Reading ECU flash memory failed. Trying to force ECU to recognize read operation is complete.
Finished forcing ECU to recognize that failed read operation is complete.
Reading ECU flash memory failed.
100% complete.
Restoring Windows sleep mode.
Disabling Windows sleep mode.
Reading ECU flash memory.
Negotiating communication timings.
Successfully changed to new communication timings.
Requesting security access.
Security access granted.
Negotiating communication timings.
Successfully changed to new communication timings.
Requesting security access.
Security access granted.
Validating flash memory starts at 0x00800000 and ends at 0x00900000.
Validation failed, ECU reports RequestUpload service is not supported. RequestUpload may have been disabled by aftermarket engine software.
Memory layout validation failed.
Starting to read data block.
Requesting upload from ECU for address range 0x00800000 to 0x00803FFF.
Request upload from ECU failed, ECU reports service is not supported. Request upload may have been disabled by aftermarket engine software.
Reading ECU flash memory failed. Trying to force ECU to recognize read operation is complete.
Finished forcing ECU to recognize that failed read operation is complete.
Reading ECU flash memory failed.
100% complete.
Restoring Windows sleep mode.
Disconnecting...
Disconnected
Switching to KWP2000 session.
Validated FTDI device is in dumb mode.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP2000 session.
Connected
Disconnecting...
Disconnected
Disconnected
Connecting...
Starting bootstrap loader upload.
Sent bootstrap init zero byte.
Sent bootstrap init zero byte.
Sent bootstrap init zero byte.
Bootstrap loader upload failed. Failed to receive device ID response for init zero byte.
Disconnected
Connecting...
Starting bootstrap loader upload.
Sent bootstrap init zero byte.
Sent bootstrap init zero byte.
Sent bootstrap init zero byte.
Bootstrap loader upload failed. Failed to receive device ID response for init zero byte.
Disconnected
Connecting...
Starting bootstrap loader upload.
Sent bootstrap init zero byte.
Sent bootstrap init zero byte.
Sent bootstrap init zero byte.
Bootstrap loader upload failed. Failed to receive device ID response for init zero byte.
Disconnected
Validated FTDI device is in dumb mode.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP2000 session.
Connected
Disabling Windows sleep mode.
Reading ECU flash memory.
ECU reports programming session preconditions have been met.
Negotiating communication timings.
Timing negotiation failed. Communication timings are unchanged.
Requesting security access.
Security access granted.
Starting diagnostic session.
Successfully started diagnostic session.
Negotiating communication timings.
Successfully changed to new communication timings.
Requesting security access.
Security access granted.
Validating flash memory starts at 0x00800000 and ends at 0x00900000.
Validation failed, ECU reports RequestUpload service is not supported. RequestUpload may have been disabled by aftermarket engine software.
Memory layout validation failed.
Starting to read data block.
Requesting upload from ECU for address range 0x00800000 to 0x00803FFF.
Request upload from ECU failed, ECU reports service is not supported. Request upload may have been disabled by aftermarket engine software.
Reading ECU flash memory failed. Trying to force ECU to recognize read operation is complete.
Finished forcing ECU to recognize that failed read operation is complete.
Reading ECU flash memory failed.
100% complete.
Restoring Windows sleep mode.
Title: Re: Failing to read Motronic 7.1.1 G VR6 24V BDE
Post by: Darkbound on September 06, 2017, 12:09:54 PM
P.S. Could not find the edit button... is there a way to change the color scheme of the website, the black background is killing my eyes ::)
Title: Re: Failing to read Motronic 7.1.1 G VR6 24V BDE
Post by: nyet on September 06, 2017, 01:34:00 PM
Validation failed, ECU reports RequestUpload service is not supported. RequestUpload may have been disabled by aftermarket engine software.
Your ecu is not stock.
Title: Re: Failing to read Motronic 7.1.1 G VR6 24V BDE
Post by: Darkbound on September 06, 2017, 02:10:29 PM
Your ecu is not stock.
Thanks for the fast reply, does this mean that my ecu is already remapped and is this 100% sure? And how can I gain access to the ecu in such case ?
Title: Re: Failing to read Motronic 7.1.1 G VR6 24V BDE
Post by: aef on September 07, 2017, 03:59:50 AM
bootmode with mpps or galletto
Title: Re: Failing to read Motronic 7.1.1 G VR6 24V BDE
Post by: adam- on September 07, 2017, 04:23:51 AM
To be fair; I couldn't read my mates bone stock R32 either. It said the same thing, but's never had a tune in it's life.
Wrote fine.
Title: Re:
Post by: THANAS on September 07, 2017, 04:40:00 AM
I was under the impression that NMFlasher didn't work for these ecus.
|