All map now have the Load as the X-Axis and RPM as Y-Axis, like the EVOs do.
Makes maps easier to read, and are now able to copy and paste EVO maps.
Big addition are the Knock Control maps.
For people who have knock at low rpms/phantom knock/lifter knock, there is an easy fix.
The stock EVO Knock Control Above Load maps have the lower rpm values max out, so knock won't be read at lower rpms. Simply do the same with your maps to get rid of low rpm false knock.
Advertisement
To browse the forums without the advertisements above, Login/Register
Maybe I missed it.. but is there support to turn off the CEL? Or use the CEL as a knock light? Possibly passing emissions by setting OBD2 tests to ready?
You should be able to cross flash the 20550011. A ecu reset needs to be done after cross flashing.
No one has really tested this yet though.
The only real difference between the GST and GSX is the speed limiter , which can be switched off in the periphery bits.
I'll have a big update for the 20550011 very soon, 20+ more maps, knock control, and more.
Putting my id in the 20550011 will allow me to use the program but I got an error on a test write so i'll have to look into it sat. I don't mind being the test goat. Should I leave the fwd info or swap it on the def?
Putting my id in the 20550011 will allow me to use the program but I got an error on a test write so i'll have to look into it sat. I don't mind being the test goat. Should I leave the fwd info or swap it on the def?
Just do:
File->Open Rom->20550011.bin
Then press "Write to ECU" button.
An ECU Reset must be done after a cross flash, or else you will get lots of CELs and run bad, if it runs at all.
Remember to save a copy of your original ROM.
The only difference between FWD and AWD is the SpeedLimiter.
ECUFlash will automatically change the DEF for what ever ROM is loaded.
Maybe I missed it.. but is there support to turn off the CEL? Or use the CEL as a knock light? Possibly passing emissions by setting OBD2 tests to ready?
Some emission equipment can be turn off in the Periphery Bits.
The Readyness and Completion Tests haven't been found yet, so if your emissions station plugs into your OBD2 port you won't pass, if your equipment isn't hooked up.
I've been getting help from some of the EVO EcuFlash gurus with the OBD2 stuff, finding the Tests shouldn't be a problem. I'm trying to get the more important performance things done first.
I would like to turn the boost gauge into a knock gauge, I think thats more informative than a knock light.
It might be but knock light is much harder to miss and can tell you a fair amount. I have mine set to a slow flash for 3 counts and a fast flash for 5 counts. What more will the gauge tell you? Two more values? Useful but not necessary. I'll agree though that since it is there already and otherwise useless it is definitely the point to focus on but I would suggest that someday knock light become a project worth pursuing.
Putting my id in the 20550011 will allow me to use the program but I got an error on a test write so i'll have to look into it sat. I don't mind being the test goat. Should I leave the fwd info or swap it on the def?
You should check the cable and all connections, IIRC you also had problems with downloading your ROM. Theoretically this can lead to a bad flash and bricked ECU.
Also, the GST and GSX ROMs have some very minor differences, but I guess only Ceddy will be able to tell us what are they.
The crossflash worked, so far to the gas station and home with no issue. I only messed with injector comp. and got my afc almost zero'd out. I put my ID and trim level into the XXXXXX11 rom and double checked the cables shazam. Thank you guys so much for the help. Ceddy, can I buy you a beer?
The crossflash worked, so far to the gas station and home with no issue. I only messed with injector comp. and got my afc almost zero'd out. I put my ID and trim level into the XXXXXX11 rom and double checked the cables shazam. Thank you guys so much for the help. Ceddy, can I buy you a beer?
Glad to hear everything is working.
Having one ROM and cross flashing it makes things easier, instead of trying to update DEFs for ten different ROM versions.
Only thing is my rpm axis is displaying meaningless numbers, NBD for now cause i'm turning off all mil codes for things that the previous owner didn't think should be on the car, and inj. scaling.
Does the car feel any different performance wise after changing the injector scaling to 660 inside the ecu instead of using the AFC to tune by zeroing it out? Smoothness, drivability etc.
It probably feels slower because you arnt getting as much timing now...you can always up the timing on the timing maps now
Quote:
Originally Posted by rstchris
The crossflash worked, so far to the gas station and home with no issue. I only messed with injector comp. and got my afc almost zero'd out. I put my ID and trim level into the XXXXXX11 rom and double checked the cables shazam. Thank you guys so much for the help. Ceddy, can I buy you a beer?
If the axis numbers are messed up, then you're using the wrong def. If you're using the 2055011 rom, then make sure that def is in the rommetadata/eclipse folder. I have found that if I have both 2055010 and 2055011 def files in there, then it will only use one of those defs. I made an "other" folder in rommetadata and threw all the def files in there for the hell of it, while keeping the correct def file in the /eclipse folder. This way they don't seem to interfere.
This is a read template if anyone wants it. It needs to get saved as a .xml, and saved in the rommetadata/read template folder. It's obviously not needed, but when you read from the ecu you'll now have the 98-99 eclipse option instead of using the EVO 5 or whatever.
You shouldn't change the ROM ID, leave it as 20550011.
Thats why you are getting a corrupted rpm axis. Its confusing EcuFlash into using the wrong DEF.
I figured it would want the stock ID but i'll try it and see how it goes. As for the feel of the car, it always drove smooth cause I tuned the afc in open loop then plugged the o2 back in but i'm running the 1g fpr so I didn't use 660cc on the scale. I still have to reset my base timing and check wot timing on the scan tool vs the map i'm using. I don't have a logger so i'll be tuning in open once again.
I put my ID and trim level into the XXXXXX11 rom and double checked the cables shazam.
That's the wrong thing to do, don't change the IDs and trims because you are changing wrong things, not in the def and not in the ROM.
Moreover, there are 4 ID's in the ROM, so there's no way you can fix them all. One one of which is like repeated 10 times.
Quote:
Originally Posted by draculia
This is a read template if anyone wants it. It needs to get saved as a .xml, and saved in the rommetadata/read template folder. It's obviously not needed, but when you read from the ecu you'll now have the 98-99 eclipse option instead of using the EVO 5 or whatever.
I wouldn't throw GST and GSX in one bag for now though. There are 4 unknown maps that differ between those models, and although they work fine, it's better to know that they do have a difference and leave them separated for now.
EDIT: oops, read templates are something else... We should report that to OpenECU guys, so that they would put that in next version, and removed all EMxxxx stuff from rommetada folder, so that it wouldn't confuse everything in future.
Quote:
Originally Posted by draculia
If the axis numbers are messed up, then you're using the wrong def. If you're using the 2055011 rom, then make sure that def is in the rommetadata/eclipse folder. I have found that if I have both 2055010 and 2055011 def files in there, then it will only use one of those defs. I made an "other" folder in rommetadata and threw all the def files in there for the hell of it, while keeping the correct def file in the /eclipse folder. This way they don't seem to interfere.
You definitely shouldn't keep EMxxxx and 2xxx00xx definitions there, because they use different addressing scheme, so they can mess things up. In a way that you'll have 2 correct definitions, and no way of knowing what will happen.
Now I wonder if EM2364 cross flash is OK. Or even that mysterious EM3284 nobody have seen.
That's the wrong thing to do, don't change the IDs and trims because you are changing wrong things, not in the def and not in the ROM.
Moreover, there are 4 ID's in the ROM, so there's no way you can fix them all. One one of which is like repeated 10 times.
I wouldn't throw GST and GSX in one bag for now though. There are 4 unknown maps that differ between those models, and although they work fine, it's better to know that they do have a difference and leave them separated for now.
I changed the def. back from xx560008 to xx550011 and moved my copy and tried do flash but the ecu don't want anything to do with it. I can't even open it with ecutune. When I read the stock image it knows the id so it won't let me use a def that don't match. Any other way I can fix my rpm and load axis? Btw, I didn't change the id in the rom, only the def.
If I alter the fuel and ignition maps with a retarded axis will it be ok or will I be changing numbers from unknown places?
I changed the def. back from xx560008 to xx550011 and moved my copy and tried do flash but the ecu don't want anything to do with it. I can't even open it with ecutune. When I read the stock image it knows the id so it won't let me use a def that don't match. Any other way I can fix my rpm and load axis? Btw, I didn't change the id in the rom, only the def.
If I alter the fuel and ignition maps with a retarded axis will it be ok or will I be changing numbers from unknown places?
Sounds like you have your DEF files messed up somehow.
I would delete your current DEFs, and delete EM2055 and EM2056 if you have them.
Then redownload the DEFs and copy them to the eclipse folder.
You need to use the correct DEF for the ROM, or you could edit things in the wrong spot.
You shouldn't edit any of the ROM Ids in the ROM or DEF, they are there for info only.
You could edit the fuel and timing maps because they are at the same location in all the ROMs, but its better to do things right the first time or you will run into problems later on.
I found some flash files and info for a recall done in 2004 for the ECU misreporting a bad TPS in a bunch of mitsu vehicles.
The latest 99s with the TPS fix are 23630004 and 23640004.
Nice, the 23640004 is already known. Given that this info showed up here http://www.ae-diagnosticsolutions.co...df/mut3ecu.pdf as well, it seems that we can be pretty sure that 236x ROMs can be upgraded to 236x0004 without ill effects. And no part replacement is necessary.
Unfortunately they have no info about 205x -> 236x flashing, or about 205x flashing at all.
Quote:
Originally Posted by Ceddy
The 2384 is a 3000GT, someone must have mislabeled a DEF file.
So you mean 3000GT's had H8 ECUs as well? They are not listed in MUT3 tables, contrary to 420As?
So you mean 3000GT's had H8 ECUs as well? They are not listed in MUT3 tables, contrary to 420As? Few guys in our club will be very happy if it's true.
Yes, I think they have dual CPUs. Each 3 cylinder bank is treated as a motor.
I know the 99s are flashable, there is a flash upgrade for the TPS CEL. I think the 98s are flashable also, but not sure.
A black 99 3000GT VR-4 with twin 16Gs has always been my dream car, they look so nice.
The 420a have a programming cartridge for the MUT3 Dealer Tool, because the Mitsu Dealers need to service them. But they are a Chrysler ECU, completely different, can't use the MUT3 protocol for logging or anything like that.
So, does anyone know why DSM ECUs have 4 fuel and 4 ignition maps?
I found somewhere that EVO ECUs use them to compensate for MIVEC stuff, and they have an extra set of high/low maps. But I don't see how it could be related to DSMs.
So, does anyone know why DSM ECUs have 4 fuel and 4 ignition maps?
I found somewhere that EVO ECUs use them to compensate for MIVEC stuff, and they have an extra set of high/low maps. But I don't see how it could be related to DSMs.
The High and Low Octane Maps are interpolated between based on the Octane number.
Octane is a trim modified by knock over a long period of time.
Basically zero knock, high octane map used.
Lots of knock, low octane map used.
Some knock, average of maps used.
The second set of maps are selected by a bit located before the periphery bits.
I am unsure if it that bit signifies California/Federal Emissions or FWD/AWD, or something else. All the ROMs I have looked into deeply so far have the bit set to zero, making the first set of maps used.
So the four maps are:
Hi Octane Cali, Hi Octane Fed
Lo Octane Cali, Lo Octane Fed
The periphery bits, ROM Ids, and a couple other items; have sets of eight items.
Sounds like you have your DEF files messed up somehow.
I would delete your current DEFs, and delete EM2055 and EM2056 if you have them.
Then redownload the DEFs and copy them to the eclipse folder.
You need to use the correct DEF for the ROM, or you could edit things in the wrong spot.
You shouldn't edit any of the ROM Ids in the ROM or DEF, they are there for info only.
You could edit the fuel and timing maps because they are at the same location in all the ROMs, but its better to do things right the first time or you will run into problems later on.
My ecu is now a GST, the def was fine but somehow the rom image got stupid. I deleted it and redownloaded and flashed it. So far it runs fine. The axis's are fixed. How about a fix for the genric obd2 MAP codes?
so i'll be tuning in open once again.
