Is this possibly due to incorrect scaling of the IAT sensor, or just not having enough enrichment at colder temps? Going back to my Honda chipping and tuning days with obd0 and obd1 (factory SD setups) cold starts were usually pretty rich until the car reached proper coolant temperature. Perhaps finding out how to add more fuel into the cold start enrichment might help combat this issue.

I've been following this thread from the beginning, and pretty soon I'm going to attempt this conversion (when I get around to welding a bung onto my UICP). The IPW issue kind of concerns me though, and I'd like to find out exactly why it jumps around.

 

Is there a way to log in kPa instead of Psi for ease of use? If not, no big deal. Just seemed like less chance of user (me) error for converting psi to kpa for SD MAP table.

Edit: Also please tell me if I'm correct on my way of thinking too. When logging boost/kpa, you have to add 14.7 or whatever
your atmospheric pressure is. So if I see 5psi at x load, I would actually "make" that 19.7psi at x load and then convert that 19.7
psi to kpa?

 

You can certainly log in kpa. The map sensor sends a raw signal to the ecu which then sends a raw signal to evoscan. Kpa or psi are only units we put onto it to make it make sense to us. You should be able to use the same scaling in evoscan for kpa logging that you have defined in your ecuflash definitions and that show up in the second post of this thread.


Yes when logging if you want atmospheric compensation just start subtracting numbers until you get to 0 with the car off but the ignition on. Personally I use a compensated boost (psi) entry and an uncompensated MAP (kpa) entry. This allows me to think in uncompensated pressure for tuning SD and gives me a different frame of reference since I'm using a linear and zeroed scale, then I can reference "boost" to make sure that I'm sane. Once I learned to think in kpa all the time though I stopped using "boost" at all and I just log MAP which is more natural for me these days anyway.





As for my cold start problem, I've considered playing with cold start enrichment but I haven't gotten around to it, as it is I just let the car warm up for a minute which is a good thing anyway. What is weird is that it happens all the time when I start the car even if it has only been off for a few minutes though it does only persist for a very short time if the car is already warm. I'm also not sure it has anything to do with SD since I've seen some other DSM drivers reporting their cars feeling like crap when they first start them after the evo8 ecu swap. It may have something to do with the 96530006 rom. IIRC this was not an issue on the 90550001 rom but then again it may not have been noticeable because the car always felt like crap on the 9055 rom.

 

Here's the definition for logging the omni 4 bar:

<DataListItem DataLog="Y" Color="" Display="OMNI MAP" LogReference="OMNIMAP" RequestID="38" Eval="FORMULA HERE" Unit="psig" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="-15" GaugeMax="35" ChartMin="-15" ChartMax="35" ScalingFactor="1" Notes=""/>


Here's the definition from the second post:
<scaling name="MAP 16bit" units="kPa" toexpr="x*0.4072" frexpr="x/0.4072" format="%.1f" min="0" max="450" inc="0.4072" storagetype="uint16" endian="big"/>

So I'm guessing that the display name would be "MAP 16bit", log reference would be "MAP 16bit", would request ID be 38?, the EVAL would be "x*0.4072" or would it be "x/0.4072", unit would be kPa, gauge min 0 and max 450? Response bytes would be "1".

Please help me with any corrections that need to be made.

 

<DataListItem DataLog="Y" Color="" Display="MAP 16bit" LogReference="MAP 16bit" RequestID="38" Eval="FORMULA HERE" Unit="kPa" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="450" ChartMin="0" ChartMax="450" ScalingFactor="1" Notes=""/>

Something like that above?, Just not sure which formula to put in Eval.

 

I have absolutely no idea what I'm doing when it comes to writing definitions, so any help would be appreciated. All I tried to do was fill in the blanks, which are probably wrong. That evoscan definition for logging kpa with an Omni 4 bar would make my day.

 

Ahh, now that makes more sense! I helped a friend of mine do the same swap into his 96 Eclipse and his reacts the same way. I had just attributed it to his crappy 3.5" gm blow through setup, but maybe there's more to it.

 

That had happened on MAFTPro years ago when we first went speed density back in 2006-2007 on stock ECU.

 

RE: Logging MAP in kPa:

Here's how I did it,
http://www.lancerregister.com/showpo...4&postcount=54

Simply copied the same evoscan def for psi, and changed the formula.

Is this what you mean?

 

^ So the correct definition for evoscan logging in kPa would be:
<DataListItem DataLog="Y" Color="" Display="MAP 16bit" LogReference="MAP 16bit" RequestID="38" Eval="0.19348*x*6.894757293168361" Unit="kPa" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="450" ChartMin="0" ChartMax="450" ScalingFactor="1" Notes=""/>

 

could someone tell me the scaling for AEM 5 bar sensor

 

Pic of the sensor or a non-AEM part number read from the sensor body please.

 

Which load do I use? There are about 4 different one's (1byte, 2byte, load calc. or load ecu)
Thanks

 

^ 2byte

 

1byte also works if you have your rom and evoscan set up for it. 1byte is basically the same as 2byte but in 1byte form with a small loss in resolution.