DIY ECU Flash

lostFinn · **Posted:** Thu Apr 17, 2014 10:09 am

Yeti wrote:

PS: for LostFinn , don't load it , but copy the increment on your file , that you have read with MPPS , I think the problem of Eskimo , is a different read mode that modify the original o the file you read , I have another 809 original , but read with different hardware

I'll do that. Can you send this tune file to me?

So did you use the 809 egr fcv delete file that I sent to you and did the tune to that? Or did you use someone else's 809 original?

Yeti · **Posted:** Thu Apr 17, 2014 10:54 am

lostFinn wrote:

Yeti wrote:

PS: for LostFinn , don't load it , but copy the increment on your file , that you have read with MPPS , I think the problem of Eskimo , is a different read mode that modify the original o the file you read , I have another 809 original , but read with different hardware

I'll do that. Can you send this tune file to me?

So did you use the 809 egr fcv delete file that I sent to you and did the tune to that? Or did you use someone else's 809 original?

I'll send you after write this post , I have used an 809 that I have , but I'm watch if I have your

for Grant , I have only put original the map regarding the torque when in lock up and the torque limiter on the gear , for limiting problem on TC , but let me know precisely what you feel wrong

for Eskimo ......thanks and let me know your progress , if you can not load the file , you need to open the ECU and reprogram totally the Eprom , but this work can do it only by a professional tuner with complete original file that contain not only the engine part , but all other parameter

disjaukifa · **Posted:** Thu Apr 17, 2014 11:06 am

Yeti wrote:

for Grant , I have only put original the map regarding the torque when in lock up and the torque limiter on the gear , for limiting problem on TC , but let me know precisely what you feel wrong

Yeti,

I'm going to start data logging my drives and see if that data can help you at all. Regardless great work! Also I'm going to go back to the ECO Tune again and get a full tank result for that one as well!

-Grant

Yeti · **Posted:** Thu Apr 17, 2014 11:59 am

Ok Grant ,

Update , speaking with Grant , he have read somewhere that we must write with MPPS at low possible speed for avoid problems

hope this help

disjaukifa · **Posted:** Thu Apr 17, 2014 12:30 pm

Yeti wrote:

Ok Grant ,

Update , speaking with Grant , he have read somewhere that we must write with MPPS at low possible speed for avoid problems

hope this help

Yes Yeti beat me too it. The last two times I've flashed my ECU it felt like my Liberty was not driving correctly, I would get times where I had no turbo. Now realize I have now flashed my ECU about 8 or 9 times, basically every single tank that I have done recently.

In MPPS I had set my speed to Fast, I read somewhere online this morning, I see if I can find the link again and post it, that you really should flash your ECU on Medium, and if you have the time, you really should do it on Slow (Recovery), it was to do with how long the voltage is applied to the destination address memory in your ECU Flash storage. The reason for this is if you just do the fast settings it might not write the new tune you are putting on your ECU correctly and parts of the old tune might still be there.

SO with that being said, I just filled my tank again during lunch and did the Medium speed flash of my ECU with Yeti's ECO Tune that I am testing. I will be traveling somewhat frequently over the next few days so I think I will have to fill my tank again on Sunday or Monday at the latest. I will go the entire tank with Yeti's ECO Tune he sent me and post results and then send the file to Squeeto to post on the first page.

Thanks Guys!
-Grant

Squeeto · **Posted:** Thu Apr 17, 2014 12:41 pm

lostFinn wrote:

Yeti wrote:

PS: for LostFinn , don't load it , but copy the increment on your file , that you have read with MPPS , I think the problem of Eskimo , is a different read mode that modify the original o the file you read , I have another 809 original , but read with different hardware

I'll do that. Can you send this tune file to me?

So did you use the 809 egr fcv delete file that I sent to you and did the tune to that? Or did you use someone else's 809 original?

Can you send me your original stock map file for your 809? I want to compare it to Eskymo's 809.

lostFinn · **Posted:** Thu Apr 17, 2014 1:00 pm

Squeeto wrote:

lostFinn wrote:

Can you send me your original stock map file for your 809? I want to compare it to Eskymo's 809.

Yes of course, can I have your e-mail address?
thanks

Squeeto · **Posted:** Thu Apr 17, 2014 1:25 pm

lostFinn wrote:

Squeeto wrote:

lostFinn wrote:

Can you send me your original stock map file for your 809? I want to compare it to Eskymo's 809.

Yes of course, can I have your e-mail address?
thanks

PM sent

Yeti · **Posted:** Thu Apr 17, 2014 1:33 pm

good thing

lostFinn · **Posted:** Thu Apr 17, 2014 1:58 pm

Squeeto wrote:

Can you send me your original stock map file for your 809? I want to compare it to Eskymo's 809.

You have email

Yeti · **Posted:** Thu Apr 17, 2014 2:45 pm

look at the start of the map , there are some differences , I think is the problem

Squeeto · **Posted:** Thu Apr 17, 2014 7:20 pm

Looks to be the same.

Eskymo, back to basics first, before you spend at lot of money.
Download the 809 from the first post and compare it to yours, just to make sure that you have the original.
In Windows, you can use fc.exe (file compare). It works fine for binary files. You should get the same message as above.

Unplug the Jeep battery for 15 minutes then put it on charge and make sure that your laptop is charged (or plugged in). Shut off all unnecessary running apps (even screen saver, widgets, antivirus). See if you can do an identification and a read. Then try to write the original in medium speed.

Maybe GDE modifies things outside of the 1Meg maps that we write. Maybe you are having a checksum issue.
Try to put back GDE's as well.

lostFinn did you write the 809 egr delete map (that you sent me) to your vehicle without any problems?

disjaukifa · **Posted:** Thu Apr 17, 2014 9:05 pm

Hey guys I just wanted to give an update I've been driving Yeti's eco tune for about 70 miles so far after I flashed it correctly to my ECU and it has been fantastic good torque, good amount of boost and so far looks like my diesel mileage is going to be fantastic! I will post results as soon as I fill up my tank and once we are satisfied with it I'll send it to you Squeeto!

-Grant

Eskymo · **Joined:** Fri Aug 17, 2012 9:15 am **Posts:** 31

Squeeto wrote:

Eskymo, back to basics first, before you spend at lot of money.
Unplug the Jeep battery for 15 minutes then put it on charge and make sure that your laptop is charged (or plugged in). Shut off all unnecessary running apps (even screen saver, widgets, antivirus). See if you can do an identification and a read. Then try to write the original in medium speed.

Maybe GDE modifies things outside of the 1Meg maps that we write. Maybe you are having a checksum issue.
Try to put back GDE's as well.

Thanks Squeeto, I'll do that now. I have my original file, copied and saved before I started to fiddle with anything else. I'll use that rather than GDE or any other. I've looked at the GDE files, they don't seem to change anything except std parameters within the file. What I'm missing is the vin ID that is part of the file... Will let you know how it goes.

Squeeto · **Posted:** Fri Apr 18, 2014 12:29 am

Eskymo wrote:

What I'm missing is the vin ID that is part of the file... Will let you know how it goes.

That is the part that may be different with GDE. Try using the GDE tool to put back on either their tune or stock.
GDE does give you the option to load back the stock tune, correct?

In the future (after you get it working), you may need to use the GDE tool to put back the stock tune before you try tunes with MPPS. And the same going the other way:

eg. have GDE eco tune - use GDE tool to load stock tune - then use MPPS to load Yeti
or have Yeti tune - use MPPS to load stock tune - then use GDE to load GDE eco tune

Squeeto · **Posted:** Fri Apr 18, 2014 12:35 am

disjaukifa wrote:

Hey guys I just wanted to give an update I've been driving Yeti's eco tune for about 70 miles so far after I flashed it correctly to my ECU and it has been fantastic good torque, good amount of boost and so far looks like my diesel mileage is going to be fantastic! I will post results as soon as I fill up my tank and once we are satisfied with it I'll send it to you Squeeto!

-Grant

Keep us posted on any torque converter shutter.

Eskymo · **Joined:** Fri Aug 17, 2012 9:15 am **Posts:** 31

Squeeto wrote:

Eskymo wrote:

What I'm missing is the vin ID that is part of the file... Will let you know how it goes.

That is the part that may be different with GDE. Try using the GDE tool to put back on either their tune or stock.
GDE does give you the option to load back the stock tune, correct?

In the future (after you get it working), you may need to use the GDE tool to put back the stock tune before you try tunes with MPPS. And the same going the other way:

eg. have GDE eco tune - use GDE tool to load stock tune - then use MPPS to load Yeti
or have Yeti tune - use MPPS to load stock tune - then use GDE to load GDE eco tune

That makes sense. I tried the batt disconnect, but no go. It's almost as if yeti's tune left some residue that is not recognized. When I try MPPS to read, it says mode not available. Try to write, it says Unable to write to specified address... My only hope now I guess is that a Chrysler dealership can access the ecu, wipe it clean and reinstall my original. I feel accessing is the issue. Thanks for your input- very valuable so far. Will keep y'all informed. (If you see a big mushroom cloud hanging over Oz, you'll know I've given up and bombed it!) :dead:

lostFinn · **Posted:** Fri Apr 18, 2014 3:57 am

Squeeto wrote:

lostFinn did you write the 809 egr delete map (that you sent me) to your vehicle without any problems?

Yes, there were no problems. I used medium speed to write and read option was "Data Only". Chargers on both the Jeep and the computer.

I too did compare my original and Eskymo's original with ecm titanium's compare files function and it says files are identical. But this tune file I received seems weird. Its almost like the beginning is erased? Curve is flat with value 65535, while mine has all kinds of bumps in same area...

lostFinn · **Posted:** Fri Apr 18, 2014 8:45 am

A little report of 809 Yeti tune:

I copied modifications to my 809 EGR/FCV delete file and flashed it to the Jeep. It went fine and then to test drive. Very nice tune this is, there is clearly more power and a lot of torque. A little too much in fact to my poor torque converter. It started to shudder in 4th gear when it was locked and when pedal was about 1/2 way down. So I think torque has to be reduced when TQ is locked. What is the current torque limit at locked converter? There are so many torque limiter maps in the file that I'm not sure yet which is which.

Otherwise excellent tune...

Thanks Yeti

After my driving checked that there were no fault codes in memory.

Yeti · **Posted:** Fri Apr 18, 2014 9:58 am

Eskymo wrote:

Squeeto wrote:

Eskymo wrote:

What I'm missing is the vin ID that is part of the file... Will let you know how it goes.

That is the part that may be different with GDE. Try using the GDE tool to put back on either their tune or stock.
GDE does give you the option to load back the stock tune, correct?

In the future (after you get it working), you may need to use the GDE tool to put back the stock tune before you try tunes with MPPS. And the same going the other way:

eg. have GDE eco tune - use GDE tool to load stock tune - then use MPPS to load Yeti
or have Yeti tune - use MPPS to load stock tune - then use GDE to load GDE eco tune

That makes sense. I tried the batt disconnect, but no go. It's almost as if yeti's tune left some residue that is not recognized. When I try MPPS to read, it says mode not available. Try to write, it says Unable to write to specified address... My only hope now I guess is that a Chrysler dealership can access the ecu, wipe it clean and reinstall my original. I feel accessing is the issue. Thanks for your input- very valuable so far. Will keep y'all informed. (If you see a big mushroom cloud hanging over Oz, you'll know I've given up and bombed it!) :dead:

try to a Jeep dealer and if you can , post your OM ECU code .......I'll try to make a search

DIY ECU Flash

Who is online