Author Topic: Flashing 1999/2000 ECU's (Read 7411 times)

foxbrand · « **Reply #50 on:** April 05, 2011, 01:28:31 PM »

You are not allowed to view links. Register or Login

anyone know if I can get a flash for my ECU for running 89 octane?

screw it, since low grade gas can damage my motor (87 octane), does anyone have the ROM file for running 87?

beam514 · « **Reply #51 on:** April 05, 2011, 02:33:18 PM »

You are not allowed to view links. Register or Login

You are not allowed to view links. Register or Login
anyone know if I can get a flash for my ECU for running 89 octane?

screw it, since low grade gas can damage my motor (87 octane), does anyone have the ROM file for running 87?

The ROM has two separate maps, one for high octane fuel, one for low octane fuel. I don't know if it's just me, but I'm kind of confused as to what you are asking for.

foxbrand · « **Reply #52 on:** April 05, 2011, 04:51:02 PM »

wait, so my ECU has ROM for use with high and low octane? I thought that I could only use higher octane fuel only without damage to my engine

beam514 · « **Reply #53 on:** April 05, 2011, 05:48:34 PM »

The engine is designed for higher octane fuel, yes. But I believe in the event that low octane fuel is introduced (which is not ideal) it will resort to using the Low Octane Fuel and Timing maps, which are different than the High Octane maps in order to partially compensate.

beam514 · « **Reply #54 on:** April 05, 2011, 05:53:45 PM »

Basically the ECU has one ROM. If you really wanted to run 87 properly, I believe you would have to tune for it and make sure you are minimizing knock. There's no "low octane" ROM because no one has made one. Have you downloaded EcuFlash and looked at ROMs just to see what they look like?

beam514 · « **Reply #55 on:** April 06, 2011, 03:48:08 AM »

Good news: Someone over on openecu.org is really cleaning up the definition. Hopefully this thing gets completely smoothed out!

mysticj · « **Reply #56 on:** April 06, 2011, 05:23:15 PM »

Glad to hear that!

beam514 · « **Reply #57 on:** April 07, 2011, 12:17:11 PM »

I am posting an updated definition file, as well as ROM to the original post. I'll be deleting those old ones since they might not work anyway. If anyone wants to check out the definition, feel free. Otherwise, I think it's not complete yet. I do believe this guy will be working on it in his free time.

SPD_FRK · « **Reply #58 on:** April 13, 2011, 10:02:01 PM »

Adrian, I have another 99 V6 ROM file that apparently needs a new definition file made for it. Neither of the two posted up so far are working. This is a Cali spec ECU for sure (4 O2 sensors), that much I am aware of.

beam514 · « **Reply #59 on:** April 13, 2011, 11:15:09 PM »

yeah I'm not sure who wrote the Fed spec definition. Might have been Jamie, but there's still kinks in that one too. I haven't gotten an update from that guy recently so we'll see what's up. I want to look at the Cali spec definition and compare it to the Fed spec, and see how similar they are. If they are relatively similar, I'm sure we could make the Cali spec definition work for the Fed specs once it's done.

SPD_FRK · « **Reply #60 on:** April 14, 2011, 12:39:10 PM »

Yea I am not sure what the deal is with the ROM I posted. I am able to pull up Jmath's 99 ROM file and the definition works just fine, the ROM I posted for some reason will not work at all though.

mysticj · « **Reply #61 on:** April 14, 2011, 05:13:41 PM »

Rom 20510015

SPD_FRK · « **Reply #62 on:** April 14, 2011, 05:27:54 PM »

Thank you Jamie!

SPD_FRK · « **Reply #63 on:** April 14, 2011, 05:46:04 PM »

Looks like the load and rpm tables are still a little screwy

beam514 · « **Reply #64 on:** April 14, 2011, 07:38:41 PM »

You are not allowed to view links. Register or Login

Rom 20510015

So this Cali spec ROM that Matt posted needs to use 20410015, and mine needs to use 20410017. Would this be because of updating the ROM from the dealer? (because of recallsl)

mysticj · « **Reply #65 on:** April 14, 2011, 09:50:15 PM »

Adrian, probably so. I forgot about the recall for 99/00 because of misfire and cold start.

beam514 · « **Reply #66 on:** April 17, 2011, 02:05:42 PM »

Jamie, is the only thing that's different between the two files(20410017 and 20410015) is the definition ID within the file? (so that EcuFlash knows to utilize that specific definition)

And Matt, who's 3.5L swapped Galant are we talking about?

Deeznutz · « **Reply #67 on:** April 17, 2011, 05:52:43 PM »

^^^ mine! Isuriao was playing around with ecu flash today and was able to pull this from my rom

SPD_FRK · « **Reply #68 on:** April 17, 2011, 07:15:01 PM »

Apparently the definition 20410015 requires another definition to be inlcuded (24590024), I do not have this definition and the RPM values as well as load values are all set to like 2559 (not definied correctly perhaps?.

beam514 · « **Reply #69 on:** April 17, 2011, 08:58:03 PM »

You are not allowed to view links. Register or Login

Apparently the definition 20410015 requires another definition to be inlcuded (24590024), I do not have this definition and the RPM values as well as load values are all set to like 2559 (not definied correctly perhaps?.

My RPM values and some Load values are still showing up like that with the newer 20410017 definition as well. Anyway, here is the 24590024 file.

mysticj · « **Reply #70 on:** April 17, 2011, 09:33:10 PM »

You are not allowed to view links. Register or Login

Jamie, is the only thing that's different between the two files(20410017 and 20410015) is the definition ID within the file? (so that EcuFlash knows to utilize that specific definition)

it appears so. i'll have another look at it.

foxbrand · « **Reply #71 on:** April 19, 2011, 12:45:57 AM »

You are not allowed to view links. Register or Login

^^^ mine! Isuriao was playing around with ecu flash today and was able to pull this from my rom

what definitions were you using?

beam514 · « **Reply #72 on:** April 19, 2011, 12:41:24 PM »

You are not allowed to view links. Register or Login

You are not allowed to view links. Register or Login
^^^ mine! Isuriao was playing around with ecu flash today and was able to pull this from my rom

what definitions were you using?

He doesn't have a complete, fully working definition yet. You don't need the definition to pull the ROM, you just need it to view the ROM in EcuFlash. You can save the ROM without being able to actually see it, all the data is still there. The definition just sets up how the data will be seen. This is why Matt was asking for the definition to be made.

Deeznutz · « **Reply #73 on:** April 19, 2011, 03:37:57 PM »

well i had enough of this definition crap for the G so i'm swapping out ecm's with an 02 eclipse m/t ecm and should have no problem flashing it!!! hopefully by the end of next week it should be up n running...

beam514 · « **Reply #74 on:** May 04, 2011, 01:04:07 PM »

all right, I haven't updated in awhile so I figured it's time..

GOOD NEWS!!

1) Isaurio on TGC has been working on Dion's definition file (also Cali spec V6) and was able to find the memory locations for the RPM and Load values so that they will show up correctly in EcuFlash. This is great because this was a major problem before.

2) A member on openecu.org has been working on a definition for me, but it wasn't complete. It has some extra things like EVAP maps and stuff, which is cool.

3) Another member on openecu.org just made a pretty much fully-functional definition, with most values being correct (even injector latency). The only problem is the RPM and Load values are unassigned again.

What does this mean? It means we can frankenstein these definitions to get everything working. Since Isaurio has the memory locations for RPM and load, we can change those locations in the openecu definition. We can also add in the EVAP map and stuff. I still need to go over my ROM too see if anything else is goofy, but this is all looking very, very good! I haven't been this excited in weeks hahah