EWS delete and I have a crank with no start

[D-O]

I am in the process of installing a CSL intake. I opted for a used DME so that I could easily revert to stock.

Rather than the modified CSL binary I used Mpowere36's bootloader converstion tool to convert to the CSL 32500 bootloader and the stock CSL tune. This turned out to be a bit of an ordeal as the used MSS54HP I bought was rather recalcitrant. I ended up getting the DME stuck in programming mode and had to recover it with WinKFP. Mpowere36 determined that my DME would not tolerate a fast write speed, so he reconfigured the tool to write slowly and that proved successful. I flashed the Mullet tune (which is configured with EWS delete) using MSSFlasher and then changed the VIN using Tool32 and the ecuworx diy.

CSL intake, MAP, and IAT are installed and wired up. The car will crank but it won't start. It sounds like there is spark but no fuel. INPA does have a code 130 for EWS Manipulation, and my scan tool shows code 0F.

My Schwaben (foxwell) scan tool does have an EWS sync feature which I tried. No change.

I fired up BMWFlash and grabbed a partial bin and loaded it into the ecuworx binary modification tool. The EWS delete box is checked, so it sure looks like the Mullet tune has it disabled.

I tried reflashing the partial with BMWFlash. No change.

I tried reflashing the tune with MSSFlasher. No change.

I tried flashing an earlier version of the Mullet tune (this was the first version I received - Bry5on provided an update by the time I got the bootloader converted). No change.

The all knowing google does indicate that an EWS alignment may be required after a WinFKP ZGB update - which is how I recovered after the failed bootloader conversion. I have found instructions for using Tool32:

"First load EWS3.prg then execute "wechselcode_sync_dme".
Then load MSS54DS0.prg and execute "ews3_initialisieren" with 0x01 argument (just write 0x01 in the argument line).
To finish execute "ews3_sync". If every job returned "OKAY" the code 130 should clear and the car should fire up correctly.

I did it with my ISN written in the DME throught BDM, I'm not sure if it works with a virgin ISN. I'm also wondering why it wasn't working with INPA maybe someone can clarify this."

Its the last sentence that gives me enough pause that I have not tried it.

There are also claims that virginizing with MSSFlasher will do the trick. Everything else I found about MSSFlasher virginizing says not to do it....

I tried looking in INPA and there is a "Synchronize EWS 3 initial value" function. When I select it I get a stream of EDIABAS pop up error messages and then finally get to having to select F1 or F2 to proceed. They are labeled in German, but at the bottom of the screen F1 is "store" and F2 is "reset." Not being sure of which to select I backed out.


Any guidance would be appreciated.

D-O

[eacmen]

You still have the EWS box installed, correct? Still using the same key?

[D-O]

You still have the EWS box installed, correct? Still using the same key?

Yes to both. Only change was DME.

Thanks.

[eacmen]

Yes to both. Only change was DME.

Thanks.

Do you hear the fuel pump prime when turning the key to ACC?

[D-O]

Do you hear the fuel pump prime when turning the key to ACC?

Yes.

[D-O]

When I attempt to start it it cranks and fires once or twice and then dies.

[eacmen]

If your scan tool shows code 0F at least on google that shows its the following error:

15 Camshaft Sensor Bank 1 Synchronisation

Did you touch timing? Any sensors unplugged?

[D-O]

I did not make any adjustments to the timing.

I pulled the 0F code from a scan of the EWS. I came up with a low voltage issue when I searched for it.

As for sensors, I did add the MAP and IAT. They are wired through the MAF connector and one wire in DME connector X60003 had to be moved. Details are here:

[D-O]

For what it is worth, the car ran just fine when I pulled it into the garage a week ago to do the conversion.

[eacmen]

It's acting like the EWS isn't actually deleted. Maybe the tool isn't modifying the right value for the tune you're flashing?

[D-O]

It's acting like the EWS isn't actually deleted. Maybe the tool isn't modifying the right value for the tune you're flashing?

Sure seems like it. The bootloader converter also installs the stock CSL bin file. I did make a backup of this with MSSFlasher before flashing the Mullet tune. I am going to try flashing the stock CSL bin back onto the DME, disabling EWS with the ecuworx tool, and see if it will start.

[eacmen]

Sure seems like it. The bootloader converter also installs the stock CSL bin file. I did make a backup of this with MSSFlasher before flashing the Mullet tune. I am going to try flashing the stock CSL bin back onto the DME, disabling EWS with the ecuworx tool, and see if it will start.

To eliminate sensor issues you could unplug MAP/IAT etc. You should be able to start with those unplugged.

[D-O]

To eliminate sensor issues you could unplug MAP/IAT etc. You should be able to start with those unplugged.

Tried it. No change.

Oddly, after having MSSFlasher flash the OE CSL bin the ecuworx tool still shows all the options from the Mullet tune - including EWS delete. Strange. I must have made some error in the backup.

Going to try flashing the OE CSL bin from the github page that also hosts terra's bin.

[D-O]

Will the car start with the csl intake if I put my original DME back in? Maybe worth it just to make sure something else is not wrong.

[eacmen]

Will the car start with the csl intake if I put my original DME back in? Maybe worth it just to make sure something else is not wrong.

Unplug the CSL specific sensors and i think it should start with a VE/AlphaN map. But i've honestly never worked on a car that's had the CSL conversion done.