Speed Density 2.0 (3D VE Tables, Baro)
Feb 9, 2013, 12:53 AM
#541
Evolving Member
Hey BIGGY your scaling is correct for the JDM MAP sensor, but in your Map Sensor kPa table, the Map Volts (kPa) values are wrong.
They should look like this:
I made the same mistake.
The values change in the left hand column of this table when you first change the scaling. You have to make a copy of the values , then change the scaling, before finally pasting the original values back in.
This should increase the kPa values read by the ECU and therefore calculated as Load during transition from idle to boost. Let us know how you go.
They should look like this:
I made the same mistake.
The values change in the left hand column of this table when you first change the scaling. You have to make a copy of the values , then change the scaling, before finally pasting the original values back in.This should increase the kPa values read by the ECU and therefore calculated as Load during transition from idle to boost. Let us know how you go.
Clearly some people are having trouble grasping this relatively simple patch so i'll just draw it out for them picture are worth a thousand words right?
As you should be able to tell the Map volts vs kpa should always be 1:1 so you don't screw up the other table axis. What will happen is you'll measure 40kpa or something and it wont match to the point on the table because its not aligned.
If you want to effect load you do that with the kPA vs Load table while this should have been obvious I guess its not.
As you should be able to tell the Map volts vs kpa should always be 1:1 so you don't screw up the other table axis. What will happen is you'll measure 40kpa or something and it wont match to the point on the table because its not aligned.
If you want to effect load you do that with the kPA vs Load table while this should have been obvious I guess its not.
Feb 12, 2013, 11:39 AM
#549
It's not much work, I just drive around for a few days running my tuned MAF map (96530706) and log Load1B, VE, and JDMMAPkPa. Excel does the rest.
I thought 96534706 is a 3D ROM
I have tried to run this in a 3D ROM (96534706). So far, with kPaJDMMAP scaling selected and set up 1:1, and kPa to Load set 1:1, it is still way too lean on tip in and in transition to boost. I've yet to find time to troubleshoot why. I've tried increasing the logged 3D VE values in the 1500-2500 RPM and 70-100 kPa range with no success. My STFT's are still maxed at +12.5% in this zone. My fuel map, injector sizing, latencies, and MAF tables are all copied from my MAF tune. Asynch vs TPS is fattened up 10 units across the board.
Either I have screwed up logging kPa (the Evoscan conversion I'm using is x/3 for my JDMMAP sensor ), or miscalculated VE (=Load1B*100/kPaJDMMAP), when logging with MAF. When I double check kPa logged against a calibrated boost guage the calculation looks good.
Do you have any other suggestions for troubleshooting why this ROM doesn't seem to respond to increasing VE?
Last edited by CDrinkH2O; Feb 12, 2013 at 11:49 AM. Reason: typo
Feb 12, 2013, 08:13 PM
#553
I'm copying the tables over now to 94172715 and will try that one for giggles. Will report back.
Is 96534706 known to be a "bad" 3D ROM for the 2005 Evo8? I've not seen these "conversations" that 211ratsbud alluded to above. It would be useful to know if that is really the case as it would save people a bunch of time and frustration.
Feb 12, 2013, 08:57 PM
#555
The kpa Kavlico 3.5bar MAP scaling is wrong, the load values are too low (car runs lean). I added a 20kpa offset to the right side of the MAP Sensor kPa table and it was dead on at idle, but at higher loads it was off, so it's the scalar and the offset that are both incorrect. I tried to fix it but I'm not versed enough in scalings to do it properly myself. The Kavlico is the same as the SSI and AEM 3.5 bar and is as follows:
0.5v = 0kPa / 0PSIa
4.5v = 344.73kPa / 50PSIa
Old 2D SD scalings (psia) for this sensor are correct.
Beau
0.5v = 0kPa / 0PSIa
4.5v = 344.73kPa / 50PSIa
Old 2D SD scalings (psia) for this sensor are correct.
Beau
Code:
<scaling name="kPa JDM3barMAP" units="kPa" toexpr="x/3" frexpr="x*3" format="%.1f" min="0" max="350" inc="0.3333" storagetype="uint16" endian="big"/> <scaling name="kPa Kavlico3.5barMAP" units="kPa" toexpr="x*0.422245373-43.092233" frexpr="(x+43.092233)/0.422245373" format="%.1f" min="0" max="400" inc="0.422245" storagetype="uint16" endian="big"/> <scaling name="kPa Kavlico5barMAP" units="kPa" toexpr="x*0.63370927-64.6383455" frexpr="(x+64.6383455)/0.63370927" format="%.1f" min="0" max="500" inc="0.633709" storagetype="uint16" endian="big"/> <scaling name="kPa OMNI3barMAP" units="kPa" toexpr="x*0.30938772" frexpr="x/0.30938772" format="%.1f" min="0" max="300" inc="0.309388" storagetype="uint16" endian="big"/> <scaling name="kPa OMNI4barMAP" units="kPa" toexpr="x*0.4083631" frexpr="x/0.4083631" format="%.1f" min="0" max="400" inc="0.408363" storagetype="uint16" endian="big"/>
And here are the formulas for evoscan:
Code:
<DataListItem DataLog="N" Color="" Display="Kavlico 3.5 bar kPa" LogReference="Kavlico35barKPA_load" RequestID="38" Eval="x*1.68989149-43.092233" Unit="kPa" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="350" ChartMin="0" ChartMax="350" ScalingFactor="1" Notes="" Priority="1" PriorityOffset="0" LogHide="false" Visible="False" /> <DataListItem DataLog="N" Color="" Display="Kavlico 5 bar kPa" LogReference="Kavlico5barKPA_load" RequestID="38" Eval="x*2.53483708-64.6383455" Unit="kPa" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="500" ChartMin="0" ChartMax="500" ScalingFactor="1" Notes="" Priority="1" PriorityOffset="0" LogHide="false" Visible="False" /> <DataListItem DataLog="N" Color="" Display="OMNI 3 bar kPA" LogReference="OMNI3barKPA_load" RequestID="38" Eval="x*1.23755087" Unit="kpa" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="300" ChartMin="0" ChartMax="300" ScalingFactor="1" Notes="" Priority="1" Visible="False" LogHide="false" /> <DataListItem DataLog="N" Color="" Display="OMNI 4 bar kPA" LogReference="OMNI4barKPA_load" RequestID="38" Eval="x*1.63345239" Unit="kpa" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="400" ChartMin="0" ChartMax="400" ScalingFactor="1" Notes="" Priority="1" Visible="False" LogHide="false" />
Last edited by Dynotech Tuning; Feb 12, 2013 at 08:59 PM.
The following users liked this post:
mines5 (Oct 18, 2016)