Works on the car too!

 

Yeah, I spaced out the value for 1 bar. I think I subconsciously used the 0x64 value to get around the negative values for mov # greater than 0x80. The trick now is making it work with six commands.

Change to correct table header format is already done. :-)

 

You'll need to intall my MAT and JDM sensor patches as well. They can be found in the ECUFlash forum.

 

ok, I see what you did. Have done similar in 88590015. Now just need to create a scaling for the GM MAT sensor, and its done.

 

http://banks.myzen.co.uk/88570008SD.zip contains Tephra 5.10fix modified with SD and the xml additions needed.

 

Am I correct in thinking, that IF a JDM 3bar was fitted and the Mitsi MAT sensor.

Then no calibrations would need to be changed from the settings in your rom ?

 

Yes, apart from changes as a result of VE of your setup or due to the calibration of the intake system which you've previously mapped it for and are now trying to emulate.

 

Can't wait to try this out, shame I can't just ditch the 7 ecu and fit a 9

 

cossie1, I need details of how you log your MAP and MAT... addresses or MUT requests, what changes you have to make to your particular ECU to make them work. Pls give me the info or links.

 

I have sent you a PM with how they will wire in.

Once connected up, they should log in evoscan, just the same as the Evo 9 does.

I can't conenect the JDM 3bar up tomorrow and double check that it works as I think it should.

But I can't connect the MAT sensor, until the MAF is removed, as I would need to connect into that signal at the ecu, and it might screw the running of the car up, with the MAF connected still.

 

John,

OK, since the SD implementation is just about complete, I have a question...probably due to a lack of my understanding in the code. I know we have had several different threads and discussions on it already, but I just want to make sure that I have a clear understanding (and anyone else that may be thinking the same).

In my understanding, this is basically setting load = map at 25C, correct? So, our ignition and fueling maps are going to be following map basically as it's load axis.

What table do we then use to compensate for temperature changes in either direction? Or is the calculated load value still compensated for temperature change via pv=nrt? If the latter, then our load values are good for the ignition and fueling maps (will increase for colder temps and decrease for higher temps), but just not 'correct' in terms of being equal to map as it diverges from 25C.

I just wanted to be sure that I understood which is true. I believe everything is still temp compensated via pv=nrt based on what I understand and how you are implementing it and we will simply see our 'load' values change from winter to summer, just as they do now.

If so, great, nothing needs to be done and we have SD all set with the changes mentioned above. If not, then there has to be some other temp table that we may need to adjust so that our ignition changes due to mass airflow changes at the same map, dependent on the temperature.

 

John I have just emailed you some info, that I forgot I had.

Not sure if it's much use, but 98640014 seems to use the same address's as 90550001

 

Eric, it is compensated just like stock as you describe. The air temp density table is already suitably calibrated, but could be adjusted if necessary. It is described in honki's thread.

Cossie, thanks, working on your ROM presently.

 

Nice 1 John

 

Will this be easily ported into the Evo VIII roms? I'm currently running speed density with MaftPro on 94170015 and would love to ditch the MaftPro. I'm already set up to test with MAP sensor and MAT, so I'd be happy to test the system. Unfortunately, I have no disassembly skills, so I won't be much help in that arena.

-Paul