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.

Please Support Fuel Injector Clinic
Please Support ExtremePSI

Ceddy mods and P0446

kthackst

Proven Member
410
8
Oct 1, 2008
York, Pennsylvania
OK so I have a 96 talon awd and just installed a 98 ecu with ceddy mods. Runs great I have no issues with any of the power bands. I love it. However I have always had a EVAP solenoid issue (P0446) CEL. Now that I have to pass inspection I cant get it fixed. I have switch out from a 96 EVAP solenoid to a 97. Erased codes comes right back. I put a 98 EVAP solenoid in it, the one located below the IM, no change. I put the second 98 EVAP solenoid in the firewall location for the 96 EVAP solenoid, no change.

Now I am wondering since it is a 98 does it need both solenoids? the one by the front bumper and the one below the IM? If so where does the front bumper solenoid hook up to?
Does anyone know which ECU pin the 98 EVAP sensor by the front bumper goes into?
 

kthackst

Proven Member
410
8
Oct 1, 2008
York, Pennsylvania
If you are referring to the Preriffery bits they get rid of the CEL but the sensor will then show up "not ready" and in PA you will fail for a sensor in the "not ready" position.

Thanks and I'll keep looking.
 

rlmeskimen

Probationary Member
17
0
Dec 27, 2006
Chesapeake, Virginia
Does anyone know which ECU pin the 98 EVAP sensor by the front bumper goes into?

I believe the Evap Emission Ventilation Solenoid (P0446) goes to pin 55. I don't believe it is wired on our car. I have a 97 with a 98 ECU (non-Ceddy) and have the CEL P0446. The only thing I can think to do is run the solenoid directly to pin 55 as I don't believe it is wired in our harness.

Let me know if you get it figured out. I could use a solution as well.

Ryan
 

Turbo Demon

Proven Member
50
1
Aug 23, 2005
Alvin, Texas
I am very interested as well. I am suffering from the same problem. I cleared it and within minutes it was back. I'm also throwing a P1105 code.
 

Th3ory

Proven Member
225
29
Aug 6, 2015
Centralia, Washington
Bump! Has anyone worked on this issue at all? It seems installing a 98/99 blackbox ecu in a 97 car throws this code. Ceddys mods are working great and I am able to tune nicely, but this damned p0446 code always on is getting old. Anyone ever figure out a fix to this issue?​
 

Th3ory

Proven Member
225
29
Aug 6, 2015
Centralia, Washington

kanusky1990

10+ Year Contributor
95
8
Sep 14, 2011
Easton, Pennsylvania
Wow this is great information! I have to use post 62, as 57 doesn't work right. If I download the link from post 62 (I gives me a new 20550011 hex and xml file), do I delete my original 20550011 hex and xml files in ceddy mods and completely replace them with this new emissions 20550011 hex and xml files? That's what it seems like?

Its been a long time since I did this, but I believe I replaced the ceddy mod hex and xml files with the ones in the zip file that included the emissions tables. You should compare them, just to make sure. They should be the same until the end, then there is code written that creates the emission tables in ecuflash.

Here is a video series of ECUFlash for Evos. The program is the same for DSM's and the process is the same. Obviously the ROMS are different in the video. Its long and has a bunch of information. I watched it twice before I messed with anything to make sure I had an idea of what I was doing. Hope this helps. There is a section that discusses adding code for patches.

http://www.youtube.com/playlist?list=PL13C9F1BF5C03E946
 

Th3ory

Proven Member
225
29
Aug 6, 2015
Centralia, Washington
Well, I did some more reading and figured out how to use both post #57 and post #62. If I download the link from post #57 and open it in word, it gives me the new coding to add to the bottom of my existing .xml 20550011. Its like 8 lines to add, which, when reflashed to the ecu, tells it not to throw a code for a hand full of emission cods. And it makes perfect sense, also post #62 is great, it is the whole .xml and .hex files, which are really the new updated emission roms. And I checked and compaired many many lines of coding from my orginal .xml rom and they are the SAME, besisdes the 8 or so lines of new coding telling the ecu not to throw a cel for those few emissions codes.

So, it all made sense to me. And I checked and compaired so many lines of coding, and they all matched up, so I downloaded the the new emission .xml rom and .hex files and put them in my "eclipse" file in ECUflash program, I also removed the original .xml and .hex files.

At which time I open the new emission rom in ecu flach and checked it over, everything looked the same, I mean EVERYTHING even down to ceddymods. It was the same rom with the new coding at the end. It looked very safe to me and it worked the same, so I opened it and input my "560" tune like I always have. I test wrote the rom and it worked perfect, so I went ahead and downloaded it to the car ecu and it all went down hill! It stoped writing halfway through and froze for about 20 seconds and then flashed an error message. My stomatch turned, this has never happened before while reflashing the ecu. I tried so many things, and all resulted in the same error message.


" You were in the process of reflashing your ECU and
some memory areas have already been erased / written -
Start the reflashing process again, and the software
should be able to resume where it left off. If you are
still having trouble, save the log file, and send it to
http://openecu.org or [email protected] and see if
someone can help you. "

With this at the coding level:
" [17:07:27.179] kernel flash enable
[17:07:27.211] kernel blank flash page: addr: 0002C000
[17:07:42.234] WARNING: failed to erase page at 0002C000!
[17:07:42.234] kernel flash disable
[17:07:44.247] interface close
Offline "


After an hour or so of researching, it looks as though I have bricked my ecu... SO, now I might try and figure out what caused it to brick, however, I am havily considering dsmlink at the moment! Its so strange as everything looked like it always had when I have reflashed in the past. The newer emission .xml and .hex files looked great and the same in everyway to the old files beside the very end lines, I cant imagine it bricking because of the new emission xml and hex rom.
 

Tiki2777

5+ Year Contributor
1,006
66
Oct 9, 2011
Omaha, Nebraska
Bump for any ECUflash tuners, have you received this message and made your way out, or is it most likely the ecu is bricked?
Try wiggling the cable and or obd2 module to get a good connection. I have to hold mine into place and not breathe.
 

Th3ory

Proven Member
225
29
Aug 6, 2015
Centralia, Washington
Happens a lot because of the more than crappy connection caused by the 2.0 cable. Sometimes I can get it to finish the flash, other times it reflashes the tune completely.

I tried many times and wiggled it good, in the past I had to pull the obd2 openport connector firmly towards the rear of the car and hold it. But this issue seems to be a bit different then connection issue (I would hope its just a con issue-but I have a bad feeling its bricked). The first few times it would write halfway threw and then stop with an error message, now when I try and flash the car, the top load bar does a quick few loads then when the bottom load bar says. "writing" it wont even start at all. It just throws the error code, dosnt even write 1%.

I did just check my voltage at the re-flash plug, and its at 3.75 volts. But it seems like its been around that voltage before and flashed fine. I have also tried flashing with a trickle charger on the car battery with no success.
 

Th3ory

Proven Member
225
29
Aug 6, 2015
Centralia, Washington
I have tried to reflash a few more times, I also removed ceddymods. .xml and .hex files from ecuflash and set them on desk top, re-downloaded ceddymods, .xml and .hex. then tried to do a simple 560cc tune reflash, and now all I get is this message.

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


I'm not sure what happened. This all stared as I tried to re-flash with the added emission coding, which seems very legit, perhaps there was a voltage drop and it bricked the ecu. I will be forced to un-install the 560's, turn boost back to stock, re-install 450, and re-install the original 97 ecu. Unless, I can get away with running the 560's on the stock 97 ecu, ill re-install the ecu and see how it runs on the 560's, if its bad ill just re-install the 450.

I'm out a $130 for the blackbox ecu, plus the cost of a new tuning devise, which I'm concerned to ever re-flash now, I have flashed a number of times, and nothing seemed to different beside the emission coding.
 
Last edited:

Th3ory

Proven Member
225
29
Aug 6, 2015
Centralia, Washington
you can always try another black box ecu or different tune

Yeah, there is a local blackbox for sale, and using ecuflash did work great until this happened. I'm still at a lose to why it screwed up. If I get another blackbox, which is still a lot cheaper than dsmlink, whats to say it wont brick that ecu.

What do you mean by, "different tune" you mean like s-afc or dsmlink?
 

kanusky1990

10+ Year Contributor
95
8
Sep 14, 2011
Easton, Pennsylvania
I tried many times and wiggled it good, in the past I had to pull the obd2 openport connector firmly towards the rear of the car and hold it. But this issue seems to be a bit different then connection issue (I would hope its just a con issue-but I have a bad feeling its bricked). The first few times it would write halfway threw and then stop with an error message, now when I try and flash the car, the top load bar does a quick few loads then when the bottom load bar says. "writing" it wont even start at all. It just throws the error code, dosnt even write 1%.

I did just check my voltage at the re-flash plug, and its at 3.75 volts. But it seems like its been around that voltage before and flashed fine. I have also tried flashing with a trickle charger on the car battery with no success.

Sorry to hear. More than likely its bricked. I believe its from the connector and voltage.

Years ago when I first started messing with ecuflash, my laptop locked up and got blue screen of death in the middle of a flash. I shit a brick cause my car wouldn't run at all. I was able to reflash it again and the car ran 100%. My point is, the code wasnt able to be completely written to the ecu and it didn't brink it. I was able to flash it again.

This leads me to believe its from the voltage. Tuning guides stress battery voltage should be 12+ volts when reflashing. You may be a little gun shy but if you're comfortable with the ecuflash/evoscan tuning method, I say stick with it.

Also, if you only want the P0446 code to stop and don't trust the emissions xml and hex, you can change the bits in the standard ceddymods to tell the ECU to stop doing the test that fails and throws the code.
 

Th3ory

Proven Member
225
29
Aug 6, 2015
Centralia, Washington
Sorry to hear. More than likely its bricked. I believe its from the connector and voltage.

Years ago when I first started messing with ecuflash, my laptop locked up and got blue screen of death in the middle of a flash. I sh** a brick cause my car wouldn't run at all. I was able to reflash it again and the car ran 100%. My point is, the code wasnt able to be completely written to the ecu and it didn't brink it. I was able to flash it again.

This leads me to believe its from the voltage. Tuning guides stress battery voltage should be 12+ volts when reflashing. You may be a little gun shy but if you're comfortable with the ecuflash/evoscan tuning method, I say stick with it.

Also, if you only want the P0446 code to stop and don't trust the emissions xml and hex, you can change the bits in the standard ceddymods to tell the ECU to stop doing the test that fails and throws the code.

Thanks for the info, I wasn't aware that I could change it in ceddymods that easy. I have 12.6 volts at the battery, however I only have a little over 3 volts at the re-flash plug. I might pick up another blackbox, re-install ecuflash and start over.
 

JaysGSX

Proven Member
68
13
Feb 18, 2016
Saginaw, Michigan
Bump for any ECUflash tuners, have you received this message and made your way out, or is it most likely the ecu is bricked?

I doubt the ECU is bricked. Have you tried reinstalling the newest version of EcuFlash? EcuFlash WILL report both high and low voltage issues. From what I can see in your image above, you got none... on that attempt. Normally when it fails to flash, it goes into protect mode to prevent damage to the ECU. Did you try a test flash? What about reading the current rom image? I'd suspect something with your Tactrix cable before the ECU.
 

Th3ory

Proven Member
225
29
Aug 6, 2015
Centralia, Washington
I doubt the ECU is bricked. Have you tried reinstalling the newest version of EcuFlash? EcuFlash WILL report both high and low voltage issues. From what I can see in your image above, you got none... on that attempt. Normally when it fails to flash, it goes into protect mode to prevent damage to the ECU. Did you try a test flash? What about reading the current rom image? I'd suspect something with your Tactrix cable before the ECU.

Yes, I re-installed ecuflash and attempted to flash with ceddy mods. It keeps giving me the same error message, "kernel flash enable, kernel blank flash page: arrd: 0002c000, warning: failed to erase page at 0002c000!" I have no idea, I tried jiggling the openport connector in every dicrection. I pulled the ecu out, have another blackbox in route. It's just upsetting because I'm not sure what caused it, I feel I cant learn from this mistake.

As far as reading the ecu, while I attempted to read; the load bar would go about 75% of the way and stop. However, it would pop up as a read ROM. At which time I would try and flash that ROM back, and I would get the same error message. And yes, I test write the ROMs before I flash, and they always run through perfect. IDK :(

Every time I go to flash the ecu, it does a few fast load bars, then it goes to "flash memory" load bar, and it just freezes, it wont download any data, then I get that error message.
 
Last edited:
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 RixRacing RockAuto RTM Racing STM Tuned VR Speed Factory

Latest posts

Build Thread Updates

Vendor Updates

Latest Classifieds

Top