The 3xMAP/MAF tables
Same here. It fit a lot better on the 8/9 manifold. I put a little grease on mine to help slide it in; almost not even necessary. Will have to do a leak test to see if it leaks at all. I'm sure we can source slightly enlarged o-rings too, that might be the way to go. Maybe omni could just supply them? I'll check into it.
Who's awesome? Tehpra is! Don't forget to send a donation, the man deserves every penny!
[youtube]gUK8KkU-8TQ[/youtube]
(write-up coming verrrrry soon!)
ps--no I didn't just sit in my garage and rev it, LOL! I drove around, will be logging and reporting back soon. Just thought I'd share, I know murlo is chomping at the bit for this one.
[youtube]gUK8KkU-8TQ[/youtube]
(write-up coming verrrrry soon!)
ps--no I didn't just sit in my garage and rev it, LOL! I drove around, will be logging and reporting back soon. Just thought I'd share, I know murlo is chomping at the bit for this one.

Shane has my 4 bar now and I forwarded him the email from Tephra, its in his hands now...
Since the load is calculated from the lowest of the sources, swapping in a 4bar will cause it to always use the map sensor then rather than maf to calculate load, since it will always be the lowest relatively. Do I have this correct?
If you could send me the same email about the 4bar you sent to Dave and Scheides I would appreciate it. I am going to order a 4bar sensor this week.
If you could send me the same email about the 4bar you sent to Dave and Scheides I would appreciate it. I am going to order a 4bar sensor this week.
Since the load is calculated from the lowest of the sources, swapping in a 4bar will cause it to always use the map sensor then rather than maf to calculate load, since it will always be the lowest relatively. Do I have this correct?
If you could send me the same email about the 4bar you sent to Dave and Scheides I would appreciate it. I am going to order a 4bar sensor this week.
If you could send me the same email about the 4bar you sent to Dave and Scheides I would appreciate it. I am going to order a 4bar sensor this week.
https://www.evolutionm.net/forums/ev...ml#post8704156
Could this in a roundabout way be used to simulate SD then?
Is there any reason we can't leave the stock and the omni 4bar scaled map tables in ECU flash and just activate the switches when we want to use the 4bar tables?
Last edited by kozmic27; Nov 4, 2010 at 05:53 PM.
Yes you can do that. Just make sure you are using the 4bar scaling on a 4bar car and the 3bar scaling on a 3bar car.
You should see all the random scalings I have in Ecuflash from testing various things.
- Bryan
You mean have both scalings in XML but select which one you need on a rom by rom or tune by tune basis?
Yes you can do that. Just make sure you are using the 4bar scaling on a 4bar car and the 3bar scaling on a 3bar car.
You should see all the random scalings I have in Ecuflash from testing various things.
- Bryan
Yes you can do that. Just make sure you are using the 4bar scaling on a 4bar car and the 3bar scaling on a 3bar car.
You should see all the random scalings I have in Ecuflash from testing various things.
- Bryan
This is what I think should appear in the evo10base.xml:
Code:
<scaling name="Loadify" units="%" toexpr="(x*10/512)*10/32" frexpr="(x*32/10)*512/10" format="%.1f" min="0" max="300" inc="1" storagetype="uint16" endian="big"/> <table name="MAP based Load Calc #1 - Hot/Interpolated" category="Fuel" type="3D" level="2" swapxy="true" scaling="Loadify"> <table name="MAP" type="X Axis" elements="19" scaling="JDMMAPpsi"/> <table name="RPM" type="Y Axis" elements="19" scaling="RPM"/> </table> <table name="MAP based Load Calc #2 - Cold/Interpolated" category="Fuel" type="3D" level="2" swapxy="true" scaling="Loadify"> <table name="MAP" type="X Axis" elements="19" scaling="JDMMAPpsi"/> <table name="RPM" type="Y Axis" elements="19" scaling="RPM"/> </table> <table name="MAP based Load Calc #3" category="Fuel" type="3D" level="2" swapxy="true" scaling="Loadify"> <table name="MAP" type="X Axis" elements="19" scaling="JDMMAPpsi"/> <table name="RPM" type="Y Axis" elements="19" scaling="RPM"/> </table>
When I put it under "fuel" and go to access it via ECUFlash, it's grayed out and I get a message that says "The current map description is invalid or incomplete. Please edit the map description to fix the problem and the map will be viewable again."
WTF?
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
You gotta put that ANYWHERE (preferable just before the </rom> at the end) in evo10base.xml
THEN you GOTTA grab the ROMID specific code and put that into your ROMID xml (again just before the </romid>)
THEN you GOTTA grab the ROMID specific code and put that into your ROMID xml (again just before the </romid>)
Anyone got the info for logging the two load calc outputs independantly??? In particular for 55590006/7 2010 usdm RA.
Also curious what affect these tables have on fuel in the case where the MAP based value IS NOT the lower of the two load calcs... as in do these tables affect the overall fueling even if the maf load is lower than the map load??? I have a hunch they do... and will probably just go ahead and test to find out for sure.
Also curious what affect these tables have on fuel in the case where the MAP based value IS NOT the lower of the two load calcs... as in do these tables affect the overall fueling even if the maf load is lower than the map load??? I have a hunch they do... and will probably just go ahead and test to find out for sure.
Got some interesting logs tonight. I did a global increase on the 3 map load tables by 20% and found that there are cases where the ecu does not use the lower of the two calcs.....
I've never hit 250 load before tonight and it just plain jump for no other reason that the ecu decided to use the map load rather than maf load. This happened on every pull and you could absolutely feel it while driving.
Not sure how this plays into Thephra's original finding that the ecu always used the lower of the two calcs....
I've never hit 250 load before tonight and it just plain jump for no other reason that the ecu decided to use the map load rather than maf load. This happened on every pull and you could absolutely feel it while driving.
Not sure how this plays into Thephra's original finding that the ecu always used the lower of the two calcs....





