Question, ECU load determining accuracy
Originally Posted by -=SPECTRE=-
If you use the AIRFLOW/RPM*852 formula it seems to be pretty accurate for calculating what load cell you're in. I asked a similar question a few days ago and after a lot of back and forth this is what I came away with and it seems to work.
.
.
Thanks
Originally Posted by C6C6CH3vo
It's amaizing how accurate this "AIRFLOW/RPM*852" is,
Thanks
Thanks
If I'm just not getting this, you guys can feel free to make fun of my stupidity. I've been resorting to interpolating timing-rpm (providing I'm not getting knock) to located load cells for now.
So once again... Am I just wrong about the problems under high-load using that formula? Please advise.
Does the ECU roughly do the same calculation deciding what load it's at? Is the 1604hz an EvoScan thing or a MAF thing?
If so then the ECU will do the same math and also have a 1604hz cap
If so then the ECU will do the same math and also have a 1604hz cap
the ECU correctly handles values over 1609hz, only the MUT output is clipped at that value. I was told all mitsubishi ECUs did that (Older turbo DSMs)
Not sure if we'll ever find if the MUT/OBD protocol has two locations for the entire value..
I am using a piggyback/logger to overcome this stuff so its really not a problem for me.. but I did log a friends car with only Evoscan and I can see how frustrating it is.
Not sure if we'll ever find if the MUT/OBD protocol has two locations for the entire value..
I am using a piggyback/logger to overcome this stuff so its really not a problem for me.. but I did log a friends car with only Evoscan and I can see how frustrating it is.
MalibuJack, that is my understanding as well, and I belive you're using ECU+ which get's around that whereas Evosscan does not (yet).
Nj1266, wow, I'm suprised you're not going over 1566. My Evo IX went over 1603 even stock with nothing but a boost controller peaking at 20.* psi.
Nj1266, wow, I'm suprised you're not going over 1566. My Evo IX went over 1603 even stock with nothing but a boost controller peaking at 20.* psi.
Originally Posted by Roberto
MalibuJack, that is my understanding as well, and I belive you're using ECU+ which get's around that whereas Evosscan does not (yet).
Nj1266, wow, I'm suprised you're not going over 1566. My Evo IX went over 1603 even stock with nothing but a boost controller peaking at 20.* psi.
Nj1266, wow, I'm suprised you're not going over 1566. My Evo IX went over 1603 even stock with nothing but a boost controller peaking at 20.* psi.
Logs of stock UK IX FQ320 (JDM with a cat back exhaust and intercooler pipes) show about 1500 Hz at standard boost. With similar setup but catless with boost controller they seem to do about 1600 Hz at 5200 RPM or so depending on the boost level you use and the gear. These are on standard induction.
Not only that, but air density will affect it too, other mods that affect the intake tract too.. So altitude and temp will alter the value, hence the reason the we need baro and air temp sensors to put the values back in check.
so there's no easier way to determine load cells while tuning than the timing block method? there has to be an easier way! i wonder if my pocketlogger goes over 1604 Hz? probrably not since it's through the same port the tactrix cable uses, huh?
Originally Posted by Roberto
I just don't get how this could yeild any meaningfull result with Evoscan since it clips load values at 1603.95. Once you hit the 1603.95 ceiling and the airflow keeps climbing (like it obviously will unless your boost is dropping way off in the upper revs), you cannot count on the formula again until your airflow drops below that 1603.95. In my opinion, that makes the formula useless until the Evoscan author can get around this airflow ceiling.
Please correct me on how I'm wrong about this.
Please correct me on how I'm wrong about this.
You guys REALLY need to quit looking at MAF Hz values. It is meaningless. Your using the biggest part of a three part formula. Your going to get a lot further faster if you just unclick the MAF Hz in your logger.
If you want to see if your moving more lbs/min of air watch your injector pulsewidth (without changing your fuel tables). If your have more IPW your moving more air.
We need to know the grams/rev value in the ecu. It needs to be found. This is THE most important part of working with the stock ECU. Knowing this value is about all I need to know to tune my DSM. I'll be picking up an EVO 9 this weekend so hopefully that will speed my process of helping out.
In the meantime, what I used to do in my DSM before we found the grams/rev value is the timing lookup that you guys hate. For now, I'm sticking with my 1 deg timing retard per 3 counts of knock value. That is ***-U-ME ing an octane value of 255.
That brings me to another point. I'm gonna want to write come code to do some usefull things like reset the octane value every time you start the car. Anybody have the opcodes for the SH2 processor that the evo uses?
If you want to see if your moving more lbs/min of air watch your injector pulsewidth (without changing your fuel tables). If your have more IPW your moving more air.
We need to know the grams/rev value in the ecu. It needs to be found. This is THE most important part of working with the stock ECU. Knowing this value is about all I need to know to tune my DSM. I'll be picking up an EVO 9 this weekend so hopefully that will speed my process of helping out.
In the meantime, what I used to do in my DSM before we found the grams/rev value is the timing lookup that you guys hate. For now, I'm sticking with my 1 deg timing retard per 3 counts of knock value. That is ***-U-ME ing an octane value of 255.
That brings me to another point. I'm gonna want to write come code to do some usefull things like reset the octane value every time you start the car. Anybody have the opcodes for the SH2 processor that the evo uses?
Originally Posted by dan l
I'm gonna say this in a nice way. Airflow is not to be ****ing confused with load. Load is a value that the ecu uses for a lookup on your maps. It is in grams/rev. Airflow is a Hz value that your karmon vortex MAF spits out. The reason the value stops at 1603 is due to a math limitation in the data line to/from the ecu. Also your load value will be strongly affected by air temp and barometric pressure.
I do fully understand the differnce as you can tell by my other posts (that remain without such a typo, without being edited).
DanI, I've been dealing with DSM every bit as long as you, but am still capable of a typo here and there.
Last edited by Roberto; Aug 20, 2006 at 04:35 PM.
What stinks is my W/M controller not only uses boost but also uses that frequency to route VDC to my pump. At 1602 my pump will only run 90% max no matter what the boost.
Is it my imagination or does anyone else notice Ecu becomes a little picky in areas where load changes fast per rpm unless timing values aren't flat (redundant adjcent values)?
Is it my imagination or does anyone else notice Ecu becomes a little picky in areas where load changes fast per rpm unless timing values aren't flat (redundant adjcent values)?



