Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

So the car was fine 2 weeks ago it's a 95 m3 with turbo tune kit
The car was parked for a whole week last weekend i replaced the clutch oil line and over filled the brake oil tank and it dripped all over the driver side I sprayed it with some brake cleaner and tried to crank the car it won't crank !! Could the war chip erase itself!!
Or it's something else helpppp please

Brand new to the site and brand new to WAR Chip. I see there is a tune for 3.5 Inch MAF but Im curious if anyone here has one for the 3" Miller MAF NA or stock MAF. Thanks guys!

I will upload a video to YouTube and link it here when I get the chance. And I'm not exactly sure. It burbles normally for me on the "stock" 93 octane tune from the tune cache, but of course I'm decatted. It's more of a crackle, sort of like a combination of machine guns and fireworks.

Can we get a video on this and is it similar to the rk tunes burble tune.

FINISHED -

The M50 Crackle Tune is now finished after 4 days of work. I've attached it to this reply.

Now, I drive a manual so the fuel cutoff usually stops it from crackling, however there's a sweet spot just off "off-throttle" that makes it sound like a machine gun. Just be careful if you use this tune. If you make it crackle too much and too often, it can burn your exhaust valves. I usually do it only when decelerating at lights and on the highway. Between each "crackle session," give your exhaust valves and manifolds time to cool off. This tune gives it more fuel during off-throttle conditions, as well as retards the timing a considerable amount.

YOU MUST RUN 93 OCTANE WITH THIS TUNE.

Thank you for reading, and have a great day!

Yours in BMW,
Johnny Redline

Hey all,

I'm trying to make an M50 crackle tune but honestly have no idea how to retard my timing in no throttle conditions. What I mean by crackle tune is (since I'm decatted) retarding the timing when there's no throttle input to the extent that the fuel ignites in the exhaust and creates a popping/burbling/crackling noise.

I'll try out a tune that I made and see what happens, but it may also create a loss of power in P/T so I have no idea.

Let's see what happens.

THANKS A LOT!!! 

That was the solution for the problem.

It is not only using a US XP, it is also using the US Formats for comma and point! German numbers have a different format...

Yes, in the "0" cells is written "0,00" what is not usable for your software, it must be "0.00"

And this is also the difference between a 153 ECU file and a 173 ECU file.
In the 153 ECU File the cells are filled with integer numbers like "25".
In the 173 ECU File the cells are filled wit number like "4.25"

This was also the problem when i filled the 173 test file with the ignition tables of the 153 ECU. Filled with integer numbers it worked for a while, but restarting with german XP numbers formats it killed the data set.

OK, PROBLEM SOLVED!     

Update: i used the 173 ecu stock file, opened the file, all ignition tables are 0.

I filled the tables with values making sense and saved the file. I could work with the file, editing, switching, copying... i filled the 173 file with the data of a 153 file so all tables were filled with data... saved it complete...

... closed the application and reopened the file again and .... the tables were empty again, completly filled with 0 again!

so there is a bug killing data!

Please post a screen shot of the values. If your language setting uses a comma "," for a decimal place instead of "." that will cause the 0's to happen. Numbers must look like "25.5" instead of "25,5"

Update: i used the 173 ecu stock file, opened the file, all ignition tables are 0.

I filled the tables with values making sense and saved the file. I could work with the file, editing, switching, copying... i filled the 173 file with the data of a 153 file so all tables were filled with data... saved it complete...

... closed the application and reopened the file again and .... the tables were empty again, completly filled with 0 again!

so there is a bug killing data!

I have exactly the same problem.

All tunes for the 173 and 179 ecu have ignition tables completely filled with 0. Just ignition (idle, P/T and WOT), all other tables are OK and make sense.

I'm using a P4 Laptop with a original US Windows XP and Java 7.76... since the warchip software does not work with a german XP.

The computer works perfect for the ecu 153, all tables are OK including ignition.