NefMoto

Hi, my car is a 2002 Audi A4 1.8T AVJ. I started tuning it a few weeks ago and I've done over a dozen reflashes. The last thing I did was set ESCONF bit 3 from 30 to F0 (my rear O2 is disconnected) and KFNWSE to 18 in the whole map (switch off VVT in normal conditions). After the last flash the car worked fine. The next day it wouldn't start.

It just cranks on starter and it feels like there's no fuel or no spark. VCDS connects and there are no error codes. I tried cranking for over 10 seconds continuously and still nothing. I can hear the fuel pump working for a second or two when I turn the ignition key to ON. I did output test for injectors in VCDS and they seem to work. I still didn't check if there is any current after the ignition coils.

Strange thing is I tried starting with the MAF disconnected and there were no error codes in VCDS after that. My ESCONF bits are from 10D19 to 10D1F, which I'm not sure if it's right. I've set all the other maps for rear O2 delete except CWDLSAHK (I can't find it) in previous flashes and there were no problems. Maybe ESCONF isn't there and I set something else... There are no checksum errors in the file I flashed. I'm afraid to flash the original version because I don't have enough power in the battery anymore, but I will buy a charger if I need to write the ECU.

I'm attaching my current tune and the original. The ECU is 8E0906018B, HW 0261206868, SW 1037360990.

Please, help.

Read out the eeprom with argdub's tool and see if you have the death code set, not sure if that will cause this condition but easy to check.

Did you try flashing your original bin back onto it and see if it starts with that?

Thanks for your reply. I didn't flash the original because my battery is almost dead. I wanted to know if ESCONF bits are there where I wrote above, before I suspect the file and buy a battery charger. My file had no errors and the last writing to ECU was fine. Car started fine and I made more than 20 miles including another couple of engine stop-start. But maybe that's silly, I'll just go buy a charger and flash the original file just to exclude that issue...

P.S. I also need to see if there is some module between the ECU and the coils and check if it's OK, because I had (rarely) starting issues even before I started tuning. The difference is the car started after 6-10 sec cranking and now it doesn't start at all.

Maybe problem with speed sensor or fuel pump, or smth like that.

Yes, it could be those too. But can a file without checksum errors and with a successful flash cause these symtoms?

No. IMHO
If you doubt just read EEPROM.

Coldstart routine? Might a faulty sensor thro it off?

Will it start if you clear your codes ? This happened to me bc i didnt wait long enough after the flash was done before I turned ignition off

After the writing finished, nefmoto flasher disconnected, I waited about 5 sec (like I always did), turned ignition on and the car started fine. It worked fine for over 20 miles. I parked it and the next day (20 hours later) it wouldn't start.

It won't start when I clear the codes and there were no codes after that, which is strange to me. I disconnected the maf and radiator fans while ignition on, but no fault codes in VCDS.

Now I remember that some time ago (I had starting issues occasionally) I saw an Engine Speed Sensor error (intermittent) in VCDS (along with EPC lamp lit). I'll buy the sensor tomorrow and see if it'll start.

Thats what I mean on a in finished flash on older m boxes it will start once and drive the next time you try and start it. It won't, I had to do mine and wait for at least 10 seconds after the flash i know it sounds weird but I had to reflash it and wait and everything was fine i would try this

Thanks, I'll try that tomorrow. By reflash you mean normal reflash (not in boot-mode)?

Yeah just a standard flash flash in car

Hi, I charged the battery and successfully wrote the original file to the ECU. But it wouldn't start. I used argdub's tool to read via OBD and I attach the file. No errors in VCDS.

Looks ok, no death code, ok checksum.

I lol'd when I saw that you have flashed this car 43 times.

I have nothing to add to your issue though :(

Yeah, but I'm not even close to finishing my tune (only VVT experimenting took 10 flashes), so there will be at least 20 more flashes...  ;D

And your a 100% its a tune related issue i mean can you confirm a rpm signal on crank and fuel press. I am not a tune guy the ppl that help me are already here but I am a mechanical guy.

Well, I never was 100% sure it was a tune problem, I was just suspecting I could have done something wrong and now I see no logic to say it's a tune problem. As to the hardware side, I already had the RPM sensor error code (and EPC lit) appear some times and the car was hard to start on these (rare) occasions. So I surely need to change that sensor. When I tried to start the car today I saw the rpm needle jumping from 0 to approx. 300rpm while cranking - I'm not sure if this means my RPM sensor is OK - I'm going to change it anyways. As to the fuel pump I can hear it building pressure when I put the ignition to ON.

In a few words, I need to change the RPM sensor and if the car won't start then I'll look at the fuel pump. Correct me if I'm doing it the wrong way.

ME7 has counter? :o Or nefmoto flasher has?  :)

Well rpm signal means your crank sensor is good. I would take a old spark plug and pull a coil out plug it in and see if you have spark. If you do then if you have carb cleen spray it in a vacuum hose on your intake while cranking after you plug your coil back in that is

Dumb thought, but might be worth checking you still have a cambelt.

it is in the e2p :)

Thanks for the advice, I'll do that next. Actually, that was the first thing I was about to do, but I thought what is the chance more than one coil or spark plug to fail while the car was parked... Anyway, I'll try it on all coils.

It would really be a surprise if I hadn't :) I would never have though about that, I'll check that too.

I need to mention I hear a repeating clicking sound when cranking (just like a relay constantly switching On-Off) from the are that fuses are located (to the left of steering wheel).
I was also wondering - would I have these symptoms with a faulty MAF?

Yes, but if I'm right nefmoto flasher changes eeprom content... I'm not sure other flashers change it too.

It definitely writes a tuner tag and increments the flash counter, I've seen other tools add their own tag too. I was under the impression that the flash counter was built into the ECU, not a number that nef actively incremented.

$ python eepromtool.py 95040_nostart.bin
Read in 512bytes
EEPROM Status:
- Version: Immo3
- VIN: WAUZZZ8E22A045873 (Audi 2002 - A4 01-08, Ingolstadt, Germany)
- Immobiliser: On
- Checksum: OK
- Size: 512bytes
- P0601 DTC: not set
- Softcoding ID: 11701
- Tuner Tag: NEFMTO
- Flash Read/Write (successful): 43
- Flash Read/Write (attempts): 1

Should I have any concerns about that part?

P.S. RPM sensor is on its way.

Only if you have P1681.

I changed the RPM sensor today and car started. Problem solved.

Thanks to everyone for the help.

 ;D ;D ;D

Great news! Thanks for the update!

Sweet i was thinking it was a mechanical thing and thanks for the closure

You can check this in VCDS next time too, my rpm needle does not move during starts but vcds always gives a value. I had a no start 2 days ago when I forgot to plug in the sensor plugs when I moved the loom, you cant feel the relay pull when you turn the key and it will not fire :-) or just look in vcds block 1, it will stay static.

That was exactly my case, but I just didn't think VCDS updates during cranking...  :)