SD - first test success
#31
Evolved Member
Thread Starter
While working with the other MAP to MAF patch I noticed that changing the values would change values for other maps. I would think, to get your patch to work correctly, you will need to ensure that any values in the patch only affet the patch and not other base map values.
Currently the VE table in the MAP to MAF patch will change the Lean Spool tables.
Currently the VE table in the MAP to MAF patch will change the Lean Spool tables.
#34
Evolved Member
Thread Starter
There are many routines that use it, easier to clamp it to one value I think.
The only reason to have it with SD is the effect on VE that you have at altitude. It is not needed for basic airflow estimation like it is with a volume airflow sensor.
When the barometric pressure drops, the turbine speed will need to be higher to maintain the same MAP. This will increase exhaust manifold pressure and reduce VE. Without barometric pressure compensation you will get a richening as the baro drops. I think this effect will be minor in the UK with its relatively flat elevation. It may be an issue in the US. Unfortunately I have no experience of altitude tuning, but you could keep a sensor and still compensate for it. Whether the stock baro adjustments will be too much I don't know, someone will need to test.
The only reason to have it with SD is the effect on VE that you have at altitude. It is not needed for basic airflow estimation like it is with a volume airflow sensor.
When the barometric pressure drops, the turbine speed will need to be higher to maintain the same MAP. This will increase exhaust manifold pressure and reduce VE. Without barometric pressure compensation you will get a richening as the baro drops. I think this effect will be minor in the UK with its relatively flat elevation. It may be an issue in the US. Unfortunately I have no experience of altitude tuning, but you could keep a sensor and still compensate for it. Whether the stock baro adjustments will be too much I don't know, someone will need to test.
#36
Evolved Member
iTrader: (22)
Join Date: Nov 2003
Location: Northern KY near Cincy
Posts: 2,408
Likes: 0
Received 6 Likes
on
6 Posts
Couldn't we just stay in open loop and do away with the ISCV? We could use our base timing and fuel maps to tune for idle. Prior to advanced throttle bodys...this is how it was done. I may have it backward....open loop vs closed loop always confuses me.
#37
Evolved Member
Thread Starter
ISCV idle is nicer though if it can be made to work. A very heatsoaked car with a hot MAT may try for a different set point perhaps.
If we keep IAT, it would be more correct to compensate the load calculations with MAT though.
For simplicity I'd be tempted to just substitute for my own car and then junk the whole MAF housing/sensor and put a pretty pink lampshade onto the turbo inlet pipe with some heat shielding.
If we keep IAT, it would be more correct to compensate the load calculations with MAT though.
For simplicity I'd be tempted to just substitute for my own car and then junk the whole MAF housing/sensor and put a pretty pink lampshade onto the turbo inlet pipe with some heat shielding.
#38
Evolved Member
Join Date: Mar 2008
Location: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude
Posts: 730
Likes: 0
Received 2 Likes
on
2 Posts
I've never got MUT fault code reading to work, but I suspect on JDM this is what determines if the CEL is on or off rather than OBD codes. What will read MUT fault codes? Never managed to get this working in Evoscan?
Whilst I could log or correct the internal sensor fault codes, I don't have the overview of how these are converted to a MUT fault and then logged...
Whilst I could log or correct the internal sensor fault codes, I don't have the overview of how these are converted to a MUT fault and then logged...
What I can say is that Clearing of DTC clears MUT_40-MUT_49 values,
these values are OR-ed when creating PXXX DTC value,
moreover MUT_36 and MUT_37 are zero-ed, they seem to be DTC counters.
When clearing also MUT_71 (sensor errors) gets cleared, and MUT_8D is zeroed.
its 0xFA or 0xFC, they always clear DTC, but also some other different data (Freezed frames vs. Pending DTC?).
Moreover it seems that 0xF8 gives engine info summary.
Load + RPM + Battery + Barometer + Speed + Coolant temperature and some others that I do not have yet disassembled.
#39
EvoM Guru
iTrader: (50)
jcsbanks, I definitely agree that MAT needs to be used for the SD stuff. Just want to make sure that things that depend on IAT (and baro) continue to work properly.