The Top DSM Community on the Web

For 1990-1999 Mitsubishi Eclipse, Eagle Talon, Plymouth Laser, and Galant VR-4 Owners. Log in to remove most ads.

  • Join the Community!

    DSMtuners is a massive archive of DSM information - but more importantly, it's a COMMUNITY! Join in and participate with other DSMers, and invite all of your DSM friends to make this place their home. Chat with others, create a build thread, post questions and answers. Get involved! Logging in will also remove many of the advertisements, along with this notice. ;) It will also allow you to view images in threads.

Please Support ExtremePSI
Please Support ExtremePSI

ECUflash Ceddymods and Emissions Readiness BRICK

DSM Chase

Proven Member
778
49
Sep 19, 2011
Senoia, Georgia
Hey guys been a while, Having some trouble passing readiness testing on my 99' 2G GSX.. Cars all stock no codes etc, I attempted flashing the CeddyMods_1v9Cb_Emissions.zip rom found here https://evoecu.logic.net/mirror/2g/...mV-vvVhg8dnfhUNYkQw86MlgvNW-q36WoCfLFzIo4o8-I and upon midway thru the flash it bricked the ECU OR the cable glitched im not sure.. After that I changed the ECU and have been playing around with a ceddy rom with zero issues flashing, Can anyone verify this emissions tune currently works and will not brick any further ECUS?
 

Galant665

Proven Member
91
14
Oct 1, 2004
Las Vegas, Nevada
Your original ecu might not be bricked. I have flashed 2g and Evo Ecu that preciously wouldn’t read or write. Don’t toss it. If you are using another good ecu. Make sure you have a decent battery charger hooked to the car when flashing. Have flashed many with ceddy roms and haven’t had one not run yet.
 

95REGF150

Proven Member
430
215
Mar 7, 2012
Elk Grove, California
Copied from your other thread:

I have used the definitions in that .xml for years after finding them in that thread. Its a pretty awesome resource for me here in Cali. I don't have to drive around to set the monitors just flash it with them on and go get a smog.

The important thing to remember is that they did not modify that ROM to make the emissions setable all they did was find the volitile memory locations of the bit flags for the monitors. The volatile memory in the ECU is reset whenever the power is removed from the ECU so thats why all the monitors become unset when you take the battery cable off.

So when you reflash to set the monitors you are not actually modifying the ROM or tune you are really just flashing the volitile memory with the bit flags set to 1 instead of 0. The ECU normally executes code based on different conditions to set those to 1 and you are just doing it manually.

Hopefully that makes sense. Long story short it is the ECUFlash definition .xml file that is important there as it defines those memory locations. The 2055 Ceddymods ROM they give there is the same as all the standard 2055 Ceddymods ROM you get from him. The cool thing is if you get the big maps or SD version of his 2055 ROM the memory locations for the monitors are the same so you can use the same .xml memory locations for the monitors.
 

DSM Chase

Proven Member
778
49
Sep 19, 2011
Senoia, Georgia
If I am understanding correctly all I have to do is have the emissions .hex and .xml files in my rom folder? Am I actually flashing a different tune or what? since there is no modfied .BIN file to flash, That leaves only the .hex file..
Copied from your other thread:

I have used the definitions in that .xml for years after finding them in that thread. Its a pretty awesome resource for me here in Cali. I don't have to drive around to set the monitors just flash it with them on and go get a smog.

The important thing to remember is that they did not modify that ROM to make the emissions setable all they did was find the volitile memory locations of the bit flags for the monitors. The volatile memory in the ECU is reset whenever the power is removed from the ECU so thats why all the monitors become unset when you take the battery cable off.

So when you reflash to set the monitors you are not actually modifying the ROM or tune you are really just flashing the volitile memory with the bit flags set to 1 instead of 0. The ECU normally executes code based on different conditions to set those to 1 and you are just doing it manually.

Hopefully that makes sense. Long story short it is the ECUFlash definition .xml file that is important there as it defines those memory locations. The 2055 Ceddymods ROM they give there is the same as all the standard 2055 Ceddymods ROM you get from him. The cool thing is if you get the big maps or SD version of his 2055 ROM the memory locations for the monitors are the same so you can use the same .xml memory locations for the monitors.
 
Last edited:

95REGF150

Proven Member
430
215
Mar 7, 2012
Elk Grove, California
First lets clear up the .bin vs .hex thing:

Each byte of memory in every computer on earth is a number between 0-255 in decimal representation.The H8 blackbox ecu uses in our cars interprets these bytes with a hexidecimal representation so the instead of 0-255 the numbers are 0-FF. However, no matter the data structure all digital information stored in memory no matter what computer it is has to be stored as a combination of 1's & 0's which is called binary.

That explanation is so you can understand that when we copy the ROM off of the ECU we are just taking a copy of all those 0's & 1's and storing them as a file which can be named a binary file with the .bin extension. In reality for the H8 those 0's and 1's actually represent bytes of hexidecimal numbers so often you will see the ROM files with the .hex extension instead. However, as long as it is a ROM for an H8 ECU they are exactly the same thing.

Since ECUflash defaults to .bin you then you can just change the file extension from .hex to .bin for the program to pick it up.

Now as I said in my last post the emissions are there from the factory. Nothing has been changed in the ROM itself to mess with the emissions. If you have already flashed the Ceddymods 2055 ROM then you do not need to flash a different ROM to get control of the emissions monitors.

All you have to do is change the .XML file that ECUflash is using for the 2055 ROM. You go into the program files and find the 2055 ROM .XML that is currently there and replace it with the one that has the emissions defined. Then the next time you open the 2055 ROM in ECUflash the OBD will show up.

In reality there is only 2 tables that have been added to the emissions .XML and here they are below:

<table name="Monitor Available(1)/Not Available(0)" category="OBD Inspection" address="1f207" type="2D" level="2" scaling="blobbits">
<table name="Non-Continuous Monitor Availability Bits" type="Static Y Axis" flipy="true" elements="8">
<data>EGR system</data>
<data>Oxygen heater sensor</data>
<data>Oxygen sensor</data>
<data>A/C system refrigerant</data>
<data>Secondary air system</data>
<data>Evaporative system</data>
<data>Heated catalyst</data>
<data>Catalyst</data>
</table>
</table>

<table name="Monitor Passed(0)/Failed(1)" category="OBD Inspection" address="1f210" type="2D" level="2" scaling="blobbits">
<table name="Non-Continuous Monitor Completion Bits" type="Static Y Axis" flipy="true" elements="8">
<data>EGR system</data>
<data>Oxygen heater sensor</data>
<data>Oxygen sensor</data>
<data>A/C system refrigerant</data>
<data>Secondary air system</data>
<data>Evaporative system</data>
<data>Heated catalyst</data>
<data>Catalyst</data>
</table>
</table>

If you just open the .XML that ECUflash is currently using for the 2055 ROM and past these into the .XML file and save it then the monitor controls will show up.
 
Last edited:

DSM Chase

Proven Member
778
49
Sep 19, 2011
Senoia, Georgia
When I try to open my current rom file to add to the code it just looks like this font
( €
ƒ ƒ € ( È zÿÿ`  @
etc... With that being said could I just go ahead and flash the CeddyMods_1v9Cb_Emissions.zip .hex file?
 

95REGF150

Proven Member
430
215
Mar 7, 2012
Elk Grove, California
When I try to open my current rom file to add to the code it just looks like this font
( €
ƒ ƒ € ( È zÿÿ`  @
etc... With that being said could I just go ahead and flash the CeddyMods_1v9Cb_Emissions.zip .hex file?

Ok I think your missing how ECUFlash works. If you open a .hex or .bin file in a text editor all you are going to get is jibberish like that. Like I keep saying it is the memory of the ECU in it rawest form only the processor and smart people like Ceddy can decipher that craziness. It's the .XML file that you can open with a text editor and modify. So yest you can flash the 2055 ROM to the ECU all you want but the emissions tables I posted above will not show actually show up in the ECUFlash. Something has to tell ECUFlash what to display for tables and that is the .XML file.

Thats why there are 2 separate files at all. The .hex or .bin file as we keep saying is the memory file that gets written to the ECU. The .xml file is the definition file that the ECUFlash software uses to show the tables that are defined for that particular ROM. The .XML file is not part of the "Tune" or in anyway gets flashed to the ECU. The .XML file is what Ceddy and many others spent much of the time creating back in the day. It gives the memory locations where things are located within the ROM. That way ECUFlash can display it in a nice table for you. The .XML has to match the ROM and not all of the ROM's have stuff in the same place. You can flash read any ROM from your car no problem and save it on your PC but without the .XML to define where the tables are in it there is now way to tune it. ECUFlash wouldn't know where things like the timing map are or the emissions monitors your looking for.

Thats why the ECUflash program comes preloaded with .XML files for many ROM's and it has a standard one for the 2055 ROM. So that's why when you open the 2055 ROM in ECUFlash most of the tables show up. But until you go into the ECUFlash program folder ON YOUR PC where the .XML definition files are stored and modify the 2055 .XML or replace it with the emissions one given then the monitor tables will never show up.
 

DSM Chase

Proven Member
778
49
Sep 19, 2011
Senoia, Georgia
Thanks for the help, I replaced the normal 2055 .XML in the ceddy folder that ECUFlash was using with the 2055 emissions .xml and It is now using that one and has shown me the readiness tables!
You must be logged in to view this image or video.
Ok I think your missing how ECUFlash works. If you open a .hex or .bin file in a text editor all you are going to get is jibberish like that. Like I keep saying it is the memory of the ECU in it rawest form only the processor and smart people like Ceddy can decipher that craziness. It's the .XML file that you can open with a text editor and modify. So yest you can flash the 2055 ROM to the ECU all you want but the emissions tables I posted above will not show actually show up in the ECUFlash. Something has to tell ECUFlash what to display for tables and that is the .XML file.

Thats why there are 2 separate files at all. The .hex or .bin file as we keep saying is the memory file that gets written to the ECU. The .xml file is the definition file that the ECUFlash software uses to show the tables that are defined for that particular ROM. The .XML file is not part of the "Tune" or in anyway gets flashed to the ECU. The .XML file is what Ceddy and many others spent much of the time creating back in the day. It gives the memory locations where things are located within the ROM. That way ECUFlash can display it in a nice table for you. The .XML has to match the ROM and not all of the ROM's have stuff in the same place. You can flash read any ROM from your car no problem and save it on your PC but without the .XML to define where the tables are in it there is now way to tune it. ECUFlash wouldn't know where things like the timing map are or the emissions monitors your looking for.

Thats why the ECUflash program comes preloaded with .XML files for many ROM's and it has a standard one for the 2055 ROM. So that's why when you open the 2055 ROM in ECUFlash most of the tables show up. But until you go into the ECUFlash program folder ON YOUR PC where the .XML definition files are stored and modify the 2055 .XML or replace it with the emissions one given then the monitor tables will never show up.
 

95REGF150

Proven Member
430
215
Mar 7, 2012
Elk Grove, California
Awesome glad you got it. So like I was saying at the beginning if you ever want to use one of his other Mod ROM's like Big Maps or Speed Density the same .XML will work for all since he based everything on that 2055 ROM.

It really is a shame more people don't use ECUFlash and the black boxes the system really does work great. But I get it Link is so well developed and established makes sense to use the tool with the most support & development.
 

DSM Chase

Proven Member
778
49
Sep 19, 2011
Senoia, Georgia
Well Im about to abandon ship.. bricked another ECU, Every time ive tried to flash anything to do with this emissions file it bricks my ecu. Ive had zero issues flashing any normal 2055 ceddy rom, as soon as its using the modifed emissions .xml it bricks my ecu.. Now I cant write any file to this ecu and get this error just like my 1st go around. beyond fed up...
You must be logged in to view this image or video.
 

95REGF150

Proven Member
430
215
Mar 7, 2012
Elk Grove, California
The .XML has no effect on what is flashed or the flashing process. The error your getting is a flash error caused by a communication problem with your cable. Are you using a Openport 2.0?

Also I have gotten that error in the past. The ECU is not bricked its just not communicating. Look at your flash log. It failed to start. Thats usually the error I get when I have low voltage at the OBD Pin. The Openport needs a solid 5v min to be able to flash correctly.
 

DSM Chase

Proven Member
778
49
Sep 19, 2011
Senoia, Georgia
I have flashed this ecu probably 15 times in the last week zero issues, just like before. Like I said as soon as I start messing with the emissions stuff bam that error and now it won't flash, it will read fine. This is the second time this exact thing has happened, I spent days trying to make ot work and wound up replacing ecu to just do it once again now.
The .XML has no effect on what is flashed or the flashing process. The error your getting is a flash error caused by a communication problem with your cable. Are you using a Openport 2.0?

Also I have gotten that error in the past. The ECU is not bricked its just not communicating. Look at your flash log. It failed to start. Thats usually the error I get when I have low voltage at the OBD Pin. The Openport needs a solid 5v min to be able to flash correctly.
 
Last edited:

95REGF150

Proven Member
430
215
Mar 7, 2012
Elk Grove, California
Well I'll tell you without doubt that the .XML definition for the emissions monitors works on the standard 2055 ROM's that you download from Ceddy's website. I can't speak to the ROM that was in the .zip file you downloaded as I just used the .Xml on my existing tuned 2055 ROM. There may be some issue or corruption with it.

But the .XML does contain the correct address for the emission monitor bits on the 2055 ROM. Been using it for years
 

jinscho

Proven Member
636
277
Jun 16, 2017
Bangor, Pennsylvania
Reviving this post as I'm trying to get my car through emissions. I have SD/Big Maps purchased and downloaded from Ceddy.us, but I don't have access to ANY of the emissions monitors here. Here's a screenshot of what I have.

You must be logged in to view this image or video.


was the emissions version released after I purchased CeddyMods?
 
Last edited:

jinscho

Proven Member
636
277
Jun 16, 2017
Bangor, Pennsylvania
I gave myself a crash course in XML file editing and was able to unlock the tables and adjust the monitors using the table data posted above.

For anyone who runs into this in the future:

Open the 20550011 file in your ECUFlash folder with notepad. Scroll to the very bottom of the file and paste the table data shown in post 5 just before the "</ROM>" at the end. You can then save the file OR save as and generate a different file name so you can save the original. When saving, put the file name in quotations with .xml at the end in order to force the file type accordingly (ie, I named my new file "20550011_emissions.xml" which forced the file type from a text document to .xml). Once this was done, I removed the original file from the folder and opened up ECUFlash, voila the tables were there and everything worked perfectly.
 

95REGF150

Proven Member
430
215
Mar 7, 2012
Elk Grove, California
I gave myself a crash course in XML file editing and was able to unlock the tables and adjust the monitors using the table data posted above.

For anyone who runs into this in the future:

Open the 20550011 file in your ECUFlash folder with notepad. Scroll to the very bottom of the file and paste the table data shown in post 5 just before the "</ROM>" at the end. You can then save the file OR save as and generate a different file name so you can save the original. When saving, put the file name in quotations with .xml at the end in order to force the file type accordingly (ie, I named my new file "20550011_emissions.xml" which forced the file type from a text document to .xml). Once this was done, I removed the original file from the folder and opened up ECUFlash, voila the tables were there and everything worked perfectly.
Glad it worked out for you and now there is someone else to back me up on the data address's being correct. All of @DSM Chase problems must have been with the rom that he downloaded. Which they didn't even have to post because these definitions work with any 2055 ROM. They could have just posted the .XML and he wouldn't have bricked 2 ecu's. So that's where it's definitely good to understand what the .XML does and when you need to change the actual ROM.

If someone has done custom coding like Ceddy or Tephra and added something like big maps, 2 step, etc. then you need the ROM with their code. Otherwise when people find "New" maps they are really just finding the location where maps already were from the factory. So in that case the ROM does not change they just add the definition with the data address location to the .XML so you can find it in the existing ROM.
 
Support Vendors who Support the DSM Community
Boosted Fabrication ECM Tuning ExtremePSI Fuel Injector Clinic Jacks Transmissions JNZ Tuning Kiggly Racing Morrison Fabrications MyMitsubishiStore.com Raven Fabrication RixRacing RockAuto RTM Racing STM Tuned VR Speed Factory

Latest posts

Build Thread Updates

Vendor Updates

Latest Classifieds

Top