TephraMOD V6 - testing!
#1186
Ok, 1byte does display realistic load values for me so I'm not sure what was going on with 2byte. Making it work with maptracer was as easy as changing the reference name to loadcalc and making loadcalc something else.
Turns out I wasn't as accurate as I thought with my crossover points for gear based boost but I found a clean pull that should help and I'll see for tomorrow. Am I right to assume that this goes to the closes crossover point? Such as if I appear to have 1=105 2=65 3=35 4=24 then I should put them in exactly as I see them?
Thanks Phenem for your help so far.
Turns out I wasn't as accurate as I thought with my crossover points for gear based boost but I found a clean pull that should help and I'll see for tomorrow. Am I right to assume that this goes to the closes crossover point? Such as if I appear to have 1=105 2=65 3=35 4=24 then I should put them in exactly as I see them?
Thanks Phenem for your help so far.
#1188
I'm pretty sure ecuflash takes care of the interface part here so when you move to a 5bar or whatever you just change your scaling in your rom xml. What the ecu is shooting for isn't a boost pressure, it is shooting for a voltage from the MAP sensor. If we know what that voltage is with a scaling formula that we punch into ecuflash then it takes care of converting our human readable units to a value that represents the voltage we want.
#1190
*UNTESTED*
I did some work on the MAP sensor I bought, a 3.5 bar unit made by SSI Technologies. It is 0-50psia and works from 0.5-4.5 VDC.
The EvoScan formula is:
The ecuflash scaling that you need to add to your xml (to the top of the TephraMOD xml):
Like I said this is untested but the math works out.
I am using SSI Technologies part # : P51-50-A-B-I36-4.5V-R which you can find at digikey for $70 or so. It is rated for automotive use and is accurate to within 1% of full scale (half a psi on this application). Digikey doesn't't offer it but they offer them with packard 3 pin connectors, 50, 65, 75, and 100psi (and more) flavors, just call the manufacturer.
I did some work on the MAP sensor I bought, a 3.5 bar unit made by SSI Technologies. It is 0-50psia and works from 0.5-4.5 VDC.
The EvoScan formula is:
PHP Code:
<DataListItem DataLog="N" Color="" Display="SSI 3 BAR MAP" LogReference="SSI 3 BAR MAP" RequestID="38" Eval="0.248795*x-20.9687" Unit="psi" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="-14.5" GaugeMax="40" ChartMin="-14.5" ChartMax="40" ScalingFactor="1" Notes="" Priority="1" Visible="False" />
PHP Code:
<scaling name="SSI 0-50psia MAP" units="psi" toexpr="(0.248795*x)-20.9687" frexpr="(4.019373*x)+84.2810" format="%.1f" min="-14.5" max="36.254" inc="1" storagetype="uint8" endian="big"/>
I am using SSI Technologies part # : P51-50-A-B-I36-4.5V-R which you can find at digikey for $70 or so. It is rated for automotive use and is accurate to within 1% of full scale (half a psi on this application). Digikey doesn't't offer it but they offer them with packard 3 pin connectors, 50, 65, 75, and 100psi (and more) flavors, just call the manufacturer.
#1193
Big Thanks Tephra for your mods ... Now it work great ...
But i still getting CEL P0135, is this soft related error? Or need to change o2 sensor?
And my Launch map is knocking, no matter stock or tuned (exactly the same to my tuned non knocking Hi Fuel/Ign Maps) ... How to see is it Phantom knock or not?
But i still getting CEL P0135, is this soft related error? Or need to change o2 sensor?
And my Launch map is knocking, no matter stock or tuned (exactly the same to my tuned non knocking Hi Fuel/Ign Maps) ... How to see is it Phantom knock or not?
#1195
Big Thanks Tephra for your mods ... Now it work great ...
But i still getting CEL P0135, is this soft related error? Or need to change o2 sensor?
And my Launch map is knocking, no matter stock or tuned (exactly the same to my tuned non knocking Hi Fuel/Ign Maps) ... How to see is it Phantom knock or not?
But i still getting CEL P0135, is this soft related error? Or need to change o2 sensor?
And my Launch map is knocking, no matter stock or tuned (exactly the same to my tuned non knocking Hi Fuel/Ign Maps) ... How to see is it Phantom knock or not?
I have found that using the launch control you need to push the accelerator slowly. For me that caused less knock.
#1198
Ok. Bear with me. That log was huge, even zipped and I'm not sure how to edit it down. Or do you mean open it in Excel and display as data?
Here is another pull on the way to work this AM. I have some knock to clean up and load is f'd up. (I have to read the load thread again)
Anyway, I can see WGDC, JDM MAP and gear... It's a start i guess
Thanks in advance for any tips.