Failed flash - 4Z7907551M -> 8D0907551M

Pages: [1]

« previous next »

Author

Topic: Failed flash - 4Z7907551M -> 8D0907551M (Read 6936 times)

Kristopher

Newbie

Karma: +0/-0
Offline

Offline

Posts: 6

	Failed flash - 4Z7907551M -> 8D0907551M « on: February 17, 2014, 02:06:02 PM »

Victim:
2002 Audi Allroad - 2.7tt APB TIP
4Z7907551M - stock bin, IMMO

Tools:
Neftmoto 1.9.1.2
RossTech HEX CAN cable in dumb mode in VCDS
2A charger to maintain voltage. All accessories off.
schnell-mbox_2.7T_stg2++_rev2.bin to write

Issue:
Connected successfully using "Slow Init".
Writing was taking a long time, voltage remained okay.
I've reviewed the log which refers to a checksum issue, though the ME7check doesn't flag any checksum errors.
log attached.
The car won't read, ECU ID has some other text in the field. I haven't disconnected ECU power yet to clear the RAM.
It took an hour to get to 11% before it failed.

I thought I had all my i's dotted and t's crossed. While this is my first flash with the ME7, I've done some tuning (hex programming) with the mitsubishi eeproms and haven't run into problems there. I compared both files and, being my first write to this ECU, felt it was a good one to start with to see how smoothly the flashing process goes. If the flash was successful and the car runs, my aim is to work with my stock bin and incorporate slight modifications to get a nice stable tune on this car. Too bad I didn't get past the writing!

Any help is greatly appreciated.

Code:

Starting loading of DTCs.
Cancelling loading of DTCs.
Starting loading of info.
Cancelling loading of info.
Validated FTDI device is in dumb mode.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP1281 session.
KWP1281 connect info: ´Z7907551M  2.7l V6/5VT     G   0001
...
Calculating flash checksum to determine if flashing was successful for range: 0x00808000 to 0x00810000
Flash checksum matches new data, flashing was successful.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x00810000 to 0x00820000
Flash checksum does not match new data, flashing is necessary.
Requesting flash memory erase for address range 0x00810000 to 0x0081FFFF.
Successfully erased flash memory.
Requesting download to ECU for address range 0x00810000 to 0x0081FFFF.
Request download to ECU succeeded.
Starting data transfer.
7% complete.
8% complete.
9% complete.
10% complete.
11% complete.
Writing ECU flash memory failed.
100% complete.
Restoring Windows sleep mode.
Disconnecting because no response was received for the Tester Present message.
Disconnected
Switching to KWP2000 session.

http://nefariousmotorsports.com/forum/index.php?topic=689.msg8343#msg8343 suggests the IMMO shouldn't be the issue.


	Logged

ddillenger

Hero Member

Karma: +640/-21
Offline

Offline

Posts: 5640

	Re: Failed flash - 4Z7907551M -> 8D0907551M « Reply #1 on: February 17, 2014, 03:01:53 PM »

If the flash failed, try reconnecting WITHOUT turning the key off. Ensure your battery is fully charged. If you turned the key off, it's time for bootmode.


	Logged

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 experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM

userpike

Hero Member

Karma: +22/-1
Offline

Offline

Posts: 763

	Re: Failed flash - 4Z7907551M -> 8D0907551M « Reply #2 on: February 17, 2014, 07:27:52 PM »

I get the same error every once in a while. It usually happens before I start flashing though and i disconnect the dongle from both the car and the computer and wait for the alert sound of the dongle being recognised by the computer after its plugged back in before I try to init. The last time it did fail but I left the key in the on position ,disconnected and reconnected the dongle but didn't close nefmoto. I attempted a slowinit and it failed so not thinking I cycle the ignition once super quick and then slow init, again NOT closing Nef, it actually picked up where it left off at 7% and completed the flash 100% success.


	Logged

Kristopher

Newbie

Karma: +0/-0
Offline

Offline

Posts: 6

	Re: Failed flash - 4Z7907551M -> 8D0907551M « Reply #3 on: February 17, 2014, 11:50:05 PM »

You guys rock!

I got away with not having to flash in boot mode with a galletto.

Even though I turned the ignition off (I went inside for the night) , I did keep the nefmoto application running. Tonight I connected with the $5 ebay cable, switched to fast init and got an error. I changed to slow init and I was in business! It quickly began to flash up to 100% w/o errors in just over 3 minutes.

I suppose it's one for the archives. Don't use the RossTech cable, and don't close out nefmoto if you crash during writing (?)

Now the car starts, idles up and comes down when warm. Yet my ABS/ESP, and trans (TIP) modules are displeased. And for good measure, it's an allroad so I'm fortunate to get a bonus suspension level light. (probably xenon light related)

I found this link from Notorious VR on what seems to be the same problem:
http://nefariousmotorsports.com/forum/index.php?topic=264.0 but the solution doesn't seem to be apparent.

I'm looking to find out why my engine control module is incorrectly coded and a bunch of other modules have incompatibility issues.

Before flashing:

Code:

VIN: WA1YD64B72N   Mileage: 200940km/124858miles
-------------------------------------------------------------------------------
Address 01: Engine        Labels: 078-907-551-AZA.lbl
   Part No: 4Z7 907 551 M
   Component: 2.7l V6/5VT     G   0001  
   Coding: 06752
   Shop #: WSC 00000  
   VCID: 4D9F975D87CA3F1
   WA1YD64B72N107407     AUZ7Z0B2051336

No fault code found.
Readiness: 0000 1000

After flashing

Code:

                Address 01: Engine       Labels: 078-907-551-AZA.lbl
Control Module Part Number: 8D0 907 551 M
  Component and/or Version: 2.7l V6/5VT     G   0001
           Software Coding: 06752
            Work Shop Code: WSC 87119  
                      VCID: 3469E2B904BE4CBE40B-5120
2 Faults Found:

18010 - Power Supply Terminal 30 
            P1602 - 35-00 - Voltage too Low
18020 - Engine Control Module Incorrectly Coded 
            P1612 - 35-00 - 

Readiness: 0110 0100


	Logged

ddillenger

Hero Member

Karma: +640/-21
Offline

Offline

Posts: 5640

	Re: Failed flash - 4Z7907551M -> 8D0907551M « Reply #4 on: February 17, 2014, 11:57:16 PM »

You need to flash an 8D0907551L file if you have a tiptronic Tongue


	Logged

nyet

Administrator
Hero Member

Karma: +605/-168
Offline

Offline

Posts: 12243

	Re: Failed flash - 4Z7907551M -> 8D0907551M « Reply #5 on: February 18, 2014, 12:06:54 AM »

Generally works for me at slower speeds...


	Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

Please 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 experience.

Kristopher

Newbie

Karma: +0/-0
Offline

Offline

Posts: 6

	Re: Failed flash - 4Z7907551M -> 8D0907551M « Reply #6 on: February 21, 2014, 09:49:04 PM »

DOH !!!

I should have saw that coming.

My ignorance from notes I made 2 years ago led to my assumption that a TIP car can still run a manual program. So now with that sorted and my tail between my legs, I do want to state that the rosstech cable in dumb mode seemed to really slow down communications. Connecting with slow init on the $5 ebay cable worked like a charm and was super speedy.

The tune I applied is a little rough, so now the fun begins and I get to work out the rest of these maps

Thanks for the help guys


	Logged

Pages: [1]

« previous next »

Jump to:

Navigation

Personal Tools

September 23, 2024, 07:34:49 AM

Welcome, Guest. Please login or register.
Did you miss your activation email?

Navigation

Personal Tools

Search