NefMoto

Technical => Flashing and Chipping => Topic started by: UrbanAssaultar on February 16, 2012, 02:56:59 PM



Title: Tried to read ECU, and now car will not start *IT'S ALIVE...AGAIN!*
Post by: UrbanAssaultar on February 16, 2012, 02:56:59 PM
2003 allroad, codes that came up after:


Thursday,16,February,2012,12:26:30:29657
VCDS Version: Release 11.11.2 (x64)

                Address 01: Engine       Labels: 078-907-551-AZA.lbl
Control Module Part Number: 4Z7 907 551 S
  Component and/or Version: 2.7L V6/5VT     G   0020
           Software Coding: 07755
            Work Shop Code: WSC 77875 
           Additional Info: WA1YD54B23N040128     AUZ7Z0B2207824
                      VCID: 53AF9487A1EE69B
2 Faults Found:

18089 - Control Module Programming Not Finished
            P1681 - 35-00 -
18010 - Power Supply Terminal 30
            P1602 - 35-10 - Voltage too Low - Intermittent

Readiness: 0110 1101
Car has a tune, but I am unaware of which vendor it is from.


Title: Re: Tried to read ECU, and now car will not start. 4Z7907551S
Post by: ta79pr on February 16, 2012, 05:37:40 PM
2003 allroad, codes that came up after:


Thursday,16,February,2012,12:26:30:29657
VCDS Version: Release 11.11.2 (x64)

                Address 01: Engine       Labels: 078-907-551-AZA.lbl
Control Module Part Number: 4Z7 907 551 S
  Component and/or Version: 2.7L V6/5VT     G   0020
           Software Coding: 07755
            Work Shop Code: WSC 77875 
           Additional Info: WA1YD54B23N040128     AUZ7Z0B2207824
                      VCID: 53AF9487A1EE69B
2 Faults Found:

18089 - Control Module Programming Not Finished
            P1681 - 35-00 -
18010 - Power Supply Terminal 30
            P1602 - 35-10 - Voltage too Low - Intermittent

Readiness: 0110 1101
Car has a tune, but I am unaware of which vendor it is from.

I had the same problem at first with a 4Z7907551T. I had to try a few times with nefmoto and eventually it worked. Oddly, it was only that first time. I have since been in and out without problems. I did reinstall nefmoto and cable drivers just in case, but I am not sure that helped.


Title: Re: Tried to read ECU, and now car will not start. 4Z7907551S
Post by: UrbanAssaultar on February 16, 2012, 06:55:15 PM
Did you have a stock tune in your car ta79pr?

I have a feeling that this is all because of the tune the previous owner had in this car. Not enough reading on my part. I  did disconnect the battery and was able to read ECU info with Nefmoto again, but the fault code still remains. Still no start.


Title: Re: Tried to read ECU, and now car will not start. 4Z7907551S
Post by: ta79pr on February 16, 2012, 06:57:35 PM
I did have a stock tune. Did you try to clear the codes with nefmoto or vagcom, probably a stupid question.


Title: Re: Tried to read ECU, and now car will not start. 4Z7907551S
Post by: UrbanAssaultar on February 16, 2012, 07:29:37 PM
I did have a stock tune. Did you try to clear the codes with nefmoto or vagcom, probably a stupid question.


Yep, I couldn't read codes with Nefmoto until I disconnected the battery and hooked it back up. VAG-COM always worked. But no, clearing codes did nothing.


Title: Re: Tried to read ECU, and now car will not start. 4Z7907551S
Post by: ta79pr on February 16, 2012, 07:39:11 PM
Try this
http://www.goapr.com/support/immobilizer.html
It has a clear dtc function.


Title: Re: Tried to read ECU, and now car will not start. 4Z7907551S
Post by: UrbanAssaultar on February 16, 2012, 07:46:39 PM
Try this
http://www.goapr.com/support/immobilizer.html
It has a clear dtc function.


If it is an APR tune, this looks like my last hope. I guess I will find out tomorrow! Car is locked up at work. Thank you for your help!


Title: Re: Tried to read ECU, and now car will not start. 4Z7907551S
Post by: UrbanAssaultar on February 16, 2012, 07:55:17 PM
Similar to this issue:
 http://nefariousmotorsports.com/forum/index.php?topic=633.0  (http://nefariousmotorsports.com/forum/index.php?topic=633.0)


Title: Re: Tried to read ECU, and now car will not start. 4Z7907551S
Post by: julex on February 16, 2012, 07:57:26 PM
Allroads are finicky. When flashing, make absolutely sure your radio and a/c modules are off, they frequently interfere with flashing. Pull the "K-Line" module fuse. It will disconnect other modules from ECU.

If you can afford, buy premium license from Tony. It reduces flashing time from 5 minutes to 1:09 (my average time) for flashing changes. This allows me to do successful flashing 90% of times.

If you fail a flash. DON'T TOUCH ANYHTING especially DO NOT TURN OFF THE CAR.

Let the software fail. Switch to "slow init" mode. Hit "Connect" again and re-peat the flash. It will work.

If you screw up, disconnect battery for FULL TWO MINUTES. Not ONE MINUTE. Not ONE ana A HALF MINUTES. Full TWO MINUTES. This wil actually reset the ECU and allow you to connect. Trying before two minutes expire is pointless, ECU won't respond to connect attempts.

I failed flashes numerous times, never needed boot mode flashing when followed the above.

Funny part is that the same ECUs that are stubborn inside the Allroad never fail when bench flashed. It is the car interfering with the process. Probably the suspension module ETC.

I hope this helps.


Title: Re: Tried to read ECU, and now car will not start. 4Z7907551S
Post by: UrbanAssaultar on February 16, 2012, 08:16:21 PM
julex, this does help and it all makes sense. At this point, if there is any hope to recover the ECU back to it's previous state, that is my goal. I would hate to loose the tune that is already there. If I am unable to recover it, which memory layout should I use for my ECU? I already found a 4Z7907551S.bin flash file from http://nefariousmotorsports.com/forum/index.php?topic=793.msg7865#msg7865 (http://nefariousmotorsports.com/forum/index.php?topic=793.msg7865#msg7865) here. As far as the immobilizer, is this going to be a problem?


Title: Re: Tried to read ECU, and now car will not start. 4Z7907551S
Post by: julex on February 16, 2012, 08:32:41 PM
F800BB

I think you'll be fine after 2 minute off-power reset.

Immobilizer code is kept in separate EEPROM chip which nefmoto software doesn't touch. If you flash stock program, it will use thedata from EEPROM.

If the reset doesn't help though you won't be able to flash the spftware to ECU though since it is blocked by APR crap. You will have to use galletto cable/software for that outside of car and it requires opening of ECU and putting it into boot mode. There is a sticky about this on top of this page (or in Tuning).



Title: Re: Tried to read ECU, and now car will not start. 4Z7907551S
Post by: UrbanAssaultar on February 16, 2012, 08:34:25 PM
Try this
http://www.goapr.com/support/immobilizer.html
It has a clear dtc function.


I'm afraid this will not work, it requests a serial port and all I have is a HEX+CAN USB cable.


Title: Re: Tried to read ECU, and now car will not start. 4Z7907551S
Post by: julex on February 16, 2012, 08:48:19 PM
The sticky "ME7_95040..." on top of this page contains software and procedure which will allow you to clone immo stuff to any number of ECUs without need for any codes.

But this is really not applicable in your situation at this moment unless you had a spare ECU or something.


Title: Re: Tried to read ECU, and now car will not start. 4Z7907551S
Post by: UrbanAssaultar on February 16, 2012, 08:56:56 PM
I will try to flash a stock file tomorrow. Thank you so much for your help julex.


Title: Re: Tried to read ECU, and now car will not start. 4Z7907551S
Post by: littco on February 17, 2012, 10:51:23 AM
Ive had this problem on an a4 only way I could fix was to flash a virgin 95040 image back to the EEPROM, started 1st after that.


Title: Re: Tried to read ECU, and now car will not start. 4Z7907551S
Post by: UrbanAssaultar on February 17, 2012, 01:04:19 PM
I might be making a trip to the dealer, we'll see how this evening pans out. I contacted a local APR vendor and his response didn't sound to promising.


Title: Re: Tried to read ECU, and now car will not start. 4Z7907551S
Post by: ta79pr on February 17, 2012, 01:22:52 PM
I'm afraid this will not work, it requests a serial port and all I have is a HEX+CAN USB cable.

It works with the ebay usb cables, just select the correct com port.



Title: Re: Tried to read ECU, and now car will not start. 4Z7907551S
Post by: UrbanAssaultar on February 17, 2012, 01:25:51 PM
It works with the ebay usb cables, just select the correct com port.



I will give this a shot and report back.


Title: Re: Tried to read ECU, and now car will not start. 4Z7907551S
Post by: UrbanAssaultar on February 17, 2012, 02:17:37 PM
 ;D

Car starts and runs now! I flashed a stock *.bin file and used the step by step instructions given by julex, finished the first time 100% no flaws. I thank you sir julex.

Allroads are finicky. When flashing, make absolutely sure your radio and a/c modules are off, they frequently interfere with flashing. Pull the "K-Line" module fuse. It will disconnect other modules from ECU.

If you can afford, buy premium license from Tony. It reduces flashing time from 5 minutes to 1:09 (my average time) for flashing changes. This allows me to do successful flashing 90% of times.

If you fail a flash. DON'T TOUCH ANYHTING especially DO NOT TURN OFF THE CAR.

Let the software fail. Switch to "slow init" mode. Hit "Connect" again and re-peat the flash. It will work.

If you screw up, disconnect battery for FULL TWO MINUTES. Not ONE MINUTE. Not ONE ana A HALF MINUTES. Full TWO MINUTES. This wil actually reset the ECU and allow you to connect. Trying before two minutes expire is pointless, ECU won't respond to connect attempts.

I failed flashes numerous times, never needed boot mode flashing when followed the above.

Funny part is that the same ECUs that are stubborn inside the Allroad never fail when bench flashed. It is the car interfering with the process. Probably the suspension module ETC.

I hope this helps.


Title: Re: Tried to read ECU, and now car will not start *car now starts and runs*!
Post by: julex on February 19, 2012, 02:05:04 PM
Glad to hear!


Title: Re: Tried to read ECU, and now car will not start *car now starts and runs*!
Post by: UrbanAssaultar on February 20, 2012, 05:44:27 PM
And since I can't leave well enough alone...the car won't start...again. flashed a modified .bin
from  http://nefariousmotorsports.com/forum/index.php?topic=1553.msg14867#msg14867  (http://nefariousmotorsports.com/forum/index.php?topic=1553.msg14867#msg14867) here. No start, flashedback to stock, no start. Will post a log when I get home. Each flash finished 100% successfuly. Ran each file through a checksum checker, and they checked out with no errors.


Title: Re: Tried to read ECU, and now car will not start *car now starts and runs*!
Post by: UrbanAssaultar on February 20, 2012, 07:25:36 PM
Log file from today.


Title: Re: Tried to read ECU, and now car will not start *back to no start*
Post by: erroob0977 on February 21, 2012, 06:15:00 AM
This has happened to me several times with 4z7907551S bins. Check your DTCs - I have been unable to flash a S bin (stock or modified) without getting a 'programming not finished' error. I have had better luck with 4z7907551R bins.


Title: Re: Tried to read ECU, and now car will not start *back to no start*
Post by: UrbanAssaultar on February 21, 2012, 09:11:37 AM
This has happened to me several times with 4z7907551S bins. Check your DTCs - I have been unable to flash a S bin (stock or modified) without getting a 'programming not finished' error. I have had better luck with 4z7907551R bins.

An R.bin file will work with an S ecu? Did not know this, will try today. Thank you for your feedback.


Title: Re: Tried to read ECU, and now car will not start *back to no start*
Post by: UrbanAssaultar on February 21, 2012, 06:55:37 PM
IT'S ALIVE! Flashed the attached .bin, I'm 1/2 way to my overall goal of what my intended purpose was. All I want is to delete EGT's and SAI. SAI readiness is set to passed now, I think I'm going to leave it be until I get a spare ECU and a bench flash setup completed. FML....


Title: Re: Tried to read ECU, and now car will not start *IT'S ALIVE...AGAIN!*
Post by: UrbanAssaultar on February 21, 2012, 08:23:01 PM
Only downside is the suspension control has an active fault for internal memory :-(


Title: Re: Tried to read ECU, and now car will not start *IT'S ALIVE...AGAIN!*
Post by: ta79pr on February 21, 2012, 09:26:49 PM
What exactly is the suspension module fault code via vagcom, can you connect to it?


Title: Re: Tried to read ECU, and now car will not start *IT'S ALIVE...AGAIN!*
Post by: UrbanAssaultar on February 21, 2012, 09:33:38 PM
I will have to scan and upload the fault description/code. I believe it is this code, I will have to pull a scan with VCDS to be sure:

65535 - Internal Control Module Memory Error

I will try and unplug it to reset it or search for another module. Clearing the code does nothing.


Title: Re: Tried to read ECU, and now car will not start *IT'S ALIVE...AGAIN!*
Post by: ta79pr on February 21, 2012, 09:40:08 PM
Here is the ssp. It refers to a self test (p27). Perhaps you pulled the fuses and it needs to relearn.
Edit, i cant seem to attach files with the galaxy.


Title: Re: Tried to read ECU, and now car will not start *IT'S ALIVE...AGAIN!*
Post by: ta79pr on February 21, 2012, 09:43:31 PM
Attached


Title: Re: Tried to read ECU, and now car will not start *IT'S ALIVE...AGAIN!*
Post by: UrbanAssaultar on February 21, 2012, 11:03:51 PM
Attached

thank you, I will combine this with my Bentley manual and see what I can dig up. I've already started sourcing other modules as I think I may have killed mine. I am going to see if there is any adaption procedure for group 34 through VCDS to bring it back to life. Hope is minimal, every time I have flashed the engine ecu in the past - the suspension warning light became dimly lit through-out the flashing process. During the last successful flash, it didn't light up at all.


Title: Re: Tried to read ECU, and now car will not start *IT'S ALIVE...AGAIN!*
Post by: ta79pr on February 22, 2012, 04:43:59 AM
I tried to google it, but I couldn't find it - but I remember reading on one of the Audi forums that a few guys "fixed" flakey suspension modules by opening them up and re-flowing the solder.