mrfred, thanks for the great write up on such valuable information. Excellent job!!!

Check your PM's!!!

 

I am almost done with revising the instructions. One last feature I'm adding is an option to specifically disable the EGR test. I know some of you have disabled it by entering an entirely different value in the ECU Periphery 2, but by doing it that way, you are also potentially enabling/disabling other subroutines.

Even though I've got the EGR test working properly now, I'm adding an optional "disable" feature because I figure that by disabling the EGR test, its one less thing the ECU has to waste time doing. Just be sure that all your vacuum hoses are zip-tied down, because one useful thing the EGR test can do is help alert the driver of a blown off vacuum hose.

With the EGR test disabled, it shows as "Not Supported" in ODB-II diagnostics. For a person with a hand-held ODB-II scanner, this would seem to be proof enough that there is no EGR test for the car. However, I would think that the scanning equipment at an emissions test center may have a database showing what functions should be supported for each car. Thus, if you decide to disable the EGR test for daily driving, when it comes time to take your car in for an emissions test (if you have one in your area), I recommend reenabling it to be sure there are no problems getting through emissions.

 

That's exactly what I was thinking while reading your posts. I am in SC, which is nice because there are no inspections of any kind here. But, in thinking that *eventually* there will be, it would be nice to be able to pass it that one day..

 

Instructions in the first post have been updated to allow EGR test to work properly. All JDM MAP sensor users should recopy the revised table definitions into their ROM XML file and then update their ROMs with the new and/or revised table values.

 

I preface my question with this...I am a ROM editing newb and will never, probably, understand disassembling the ROMs to be able to contribute a great deal. I know enough to get in trouble, that's all. I am not fully aware of what the factory ECU may be able to support, now or in the future.

My question: Is there any chance of the factory ECU supporting closed loop boost control via monitoring the JDM MAP sensor's output and then using that signal to modify the WGDC signal?

I will take my answer off the air.

Thanks for all the work that those who understand the nitty-gritty have put in to this. I admire all your skills.

-Andrew
(Eagerly awaiting the next batch of JDM MAP sensors to come in...)

 

Yes, that's a possibility. The JDM Evo 9 does use closed loop boost feedback for part of its boost control, so it could actually be relatively easy to implement. I'm starting to look into it now.

 

I thought of something today that might be worth looking in to ...

I know that there is a min temp for full boost control. I noticed today that I'm limited to about 18 psi when under this coolant temp. Is there a way to control the boost values while under this temp limit? I want to lower mine to WG pressure.

 

isnt that what the first map is for in the IX's ?

 

Apparently not since all of my maps are the same ... I don't believe in the often referred to "map #1 warm up, map #2 normal, map #3 limp" philosophy since I often saw interpolation between the #2 and #3 timing maps and was running completely on BDEL #3.

 

hmm, interesting. All mine are different, they were from the factory, i've had 3 custom tunes from 3 different people... 1 managed to adjust just the 2nd map, which is better to me if the theory is correct, while the other 2, more well known tuners set all 3 the same.

 

Yeah, I started by only adjusting the #2 maps and it was hit and miss. For a reliable tune you need to adjust all 3.

 

nevermind

 

Thanks a bunch for all the hard work, I installed the update today. You are underpaid and overworked.

 

so, do you think setting all 3 the same helps ?

 

I think that I've got everything pretty well sorted out with this update, so I'm hoping it will be the last for a while. I'm glad to be done with it. :-) Hoping that I know enough about reading the assy code now to figure out the boost/load control system.