TephraMod V7
Just as a general note once I got around to testing the direct boost control I found the scalings for the kavlico were just a bit off.
I have played around with the scaling until i found one that matches my car at least with a 5 bar sensor. I then adjusted the formula to match up with the 3.5 Bar included in this post enjoy.
Major props to MrFred for providing the knowledge to crack this piece of the puzzle.
I have played around with the scaling until i found one that matches my car at least with a 5 bar sensor. I then adjusted the formula to match up with the 3.5 Bar included in this post enjoy.
Major props to MrFred for providing the knowledge to crack this piece of the puzzle.
PHP Code:
<scaling name="PSIa8 Kavlico3.5barMAP" units="PSIa" toexpr="x*0.124-3.324" frexpr="(x+3.324)/0.124" format="%.1f" min="0" max="24.9" inc="0.1" storagetype="uint8" endian="big"/>
<scaling name="PSIa8 Kavlico5barMAP" units="PSIa" toexpr="x*0.177-4.621" frexpr="(x+4.621)/0.177" format="%.1f" min="0" max="37.3" inc="0.1" storagetype="uint8" endian="big"/>
<scaling name="PSIa16 Kavlico3.5barMAP" units="PSIa" toexpr="x*0.124-3.324" frexpr="(x+3.324)/0.124" format="%.1f" min="0" max="34.3" inc="0.1" storagetype="uint16" endian="big"/>
<scaling name="PSIa16 Kavlico5barMAP" units="PSIa" toexpr="x*0.177-4.621" frexpr="(x+4.621)/0.177" format="%.1f" min="0" max="51.4" inc="0.1" storagetype="uint16" endian="big"/>
<scaling name="BoostErrorPsi Kavlico3.5barMAP" units="psi" toexpr="(x-128)*0.031" frexpr="(x/0.031)+128" format="%.1f" min="-4" max="4" inc="0.1" storagetype="uint16" endian="big"/>
<scaling name="BoostErrorPsi Kavlico5barMAP" units="psi" toexpr="(x-128)*0.04425" frexpr="(x/0.04425)+128" format="%.1f" min="-5.7" max="5.7" inc="0.1" storagetype="uint16" endian="big"/>
Might this mean that EvoScan is off too when it comes to logging the 3.5 bar sensor ? ?
EvoScan simply says "x" as the scaling. I would imagine that it accepts whatever is in the Zeitronix software as correct.
As for location, I have mine tied directly to the MDP sensor with a line running from the FPR. Will it make a difference that it is horizontal rather than vertical?
I ask because my AVC-R requires the sensor to be vertical for accuracy. Guess it is sensitive to baro pressure too.
As for location, I have mine tied directly to the MDP sensor with a line running from the FPR. Will it make a difference that it is horizontal rather than vertical?
I ask because my AVC-R requires the sensor to be vertical for accuracy. Guess it is sensitive to baro pressure too.
EvoScan simply says "x" as the scaling. I would imagine that it accepts whatever is in the Zeitronix software as correct.
As for location, I have mine tied directly to the MDP sensor with a line running from the FPR. Will it make a difference that it is horizontal rather than vertical?
I ask because my AVC-R requires the sensor to be vertical for accuracy. Guess it is sensitive to baro pressure too.
As for location, I have mine tied directly to the MDP sensor with a line running from the FPR. Will it make a difference that it is horizontal rather than vertical?
I ask because my AVC-R requires the sensor to be vertical for accuracy. Guess it is sensitive to baro pressure too.
But to answer your question yes evoscan assumes the output from zeitronix is correct. You may see how zero'ed out the sensor is, I found mine to be slightly off which i think was merely the altitude I'm at here 1200 ft.
PHP Code:
<scaling name="PSIa8 Kavlico3.5barMAP" units="PSIa" toexpr="x*0.124-3.324" frexpr="(x+3.324)/0.124" format="%.1f" min="0" max="24.9" inc="0.1" storagetype="uint8" endian="big"/>
<scaling name="PSIa8 Kavlico5barMAP" units="PSIa" toexpr="x*0.177-4.621" frexpr="(x+4.621)/0.177" format="%.1f" min="0" max="37.3" inc="0.1" storagetype="uint8" endian="big"/>
<scaling name="PSIa16 Kavlico3.5barMAP" units="PSIa" toexpr="x*0.124-3.324" frexpr="(x+3.324)/0.124" format="%.1f" min="0" max="34.3" inc="0.1" storagetype="uint16" endian="big"/>
<scaling name="PSIa16 Kavlico5barMAP" units="PSIa" toexpr="x*0.177-4.621" frexpr="(x+4.621)/0.177" format="%.1f" min="0" max="51.4" inc="0.1" storagetype="uint16" endian="big"/>
<scaling name="BoostErrorPsi Kavlico3.5barMAP" units="psi" toexpr="(x-128)*0.031" frexpr="(x/0.031)+128" format="%.1f" min="-4" max="4" inc="0.1" storagetype="uint16" endian="big"/>
<scaling name="BoostErrorPsi Kavlico5barMAP" units="psi" toexpr="(x-128)*0.04425" frexpr="(x/0.04425)+128" format="%.1f" min="-5.7" max="5.7" inc="0.1" storagetype="uint16" endian="big"/>
Do you have the scaling for that?
Personally my car is set for this
Map Kpa:
16.196
28.204
49.06
59.804
82.556
108.468
299.964
499.676
Load:
0
20.0219
40.0438
50.7531
70.03
100.016
299.956
499.988
Any idea on the ETA for the v7 IX .xmls, or did I miss them???
Im thinking bout ditching the v7 till the .xml's are out, as I can not add anything to the current .xml's, and have them show me the maps... Also tried editing the decel tables, and it just sets the values to "0", and stays that way. Wont even let me reset it back to the stock value...
Im thinking bout ditching the v7 till the .xml's are out, as I can not add anything to the current .xml's, and have them show me the maps... Also tried editing the decel tables, and it just sets the values to "0", and stays that way. Wont even let me reset it back to the stock value...
Any idea on the ETA for the v7 IX .xmls, or did I miss them???
Im thinking bout ditching the v7 till the .xml's are out, as I can not add anything to the current .xml's, and have them show me the maps... Also tried editing the decel tables, and it just sets the values to "0", and stays that way. Wont even let me reset it back to the stock value...
Im thinking bout ditching the v7 till the .xml's are out, as I can not add anything to the current .xml's, and have them show me the maps... Also tried editing the decel tables, and it just sets the values to "0", and stays that way. Wont even let me reset it back to the stock value...
Just typing this out from memory but basically the ToExpr can't be the same as the FrExpr.
<scaling name="Mult128" units="Factor" toexpr="x/128" frexpr="x*128" format="%.2f" min="0" max="5" inc="0.02" storagetype="uint8" endian="big"/>
I shouldnt take it out on the rom... lol the rom is not the problem!!! Love the new rom Tephra! 
Its just a bit irritating, not being able to add the ISCV findings by mrfred. I have a minor idle issue, Im trying to sort out. I had a couple other things I was trying to add, but @ the moment, cant recall what they were...
thanks roadspike, I'll look into that...
Thanks applaud, I have the .xml's, just cant get the new patchs to show up. I tried editing an older set of .xml's (non tephra) and am unable to see any of the new maps... weird. I took them out of both locations and replaced in both locations. Im running the normal 0715 If you already have the ISCV patch in, and dont mind sending it over, I would like to give it a shot... nonschlont @ aol
TIA
Its just a bit irritating, not being able to add the ISCV findings by mrfred. I have a minor idle issue, Im trying to sort out. I had a couple other things I was trying to add, but @ the moment, cant recall what they were...
thanks roadspike, I'll look into that...
Thanks applaud, I have the .xml's, just cant get the new patchs to show up. I tried editing an older set of .xml's (non tephra) and am unable to see any of the new maps... weird. I took them out of both locations and replaced in both locations. Im running the normal 0715 If you already have the ISCV patch in, and dont mind sending it over, I would like to give it a shot... nonschlont @ aol
TIA
Last edited by nonschlont; Dec 15, 2009 at 06:20 PM.
I shouldnt take it out on the rom... lol the rom is not the problem!!! Love the new rom Tephra!
Its just a bit irritating, not being able to add the ISCV findings by mrfred. I have a minor idle issue, Im trying to sort out. I had a couple other things I was trying to add, but @ the moment, cant recall what they were...
thanks roadspike, I'll look into that...
Thanks applaud, I have the .xml's, just cant get the new patchs to show up. I tried editing an older set of .xml's (non tephra) and am unable to see any of the new maps... weird. I took them out of both locations and replaced in both locations. Im running the normal 0715 If you already have the ISCV patch in, and dont mind sending it over, I would like to give it a shot... nonschlont @ aol
TIA
Its just a bit irritating, not being able to add the ISCV findings by mrfred. I have a minor idle issue, Im trying to sort out. I had a couple other things I was trying to add, but @ the moment, cant recall what they were...
thanks roadspike, I'll look into that...
Thanks applaud, I have the .xml's, just cant get the new patchs to show up. I tried editing an older set of .xml's (non tephra) and am unable to see any of the new maps... weird. I took them out of both locations and replaced in both locations. Im running the normal 0715 If you already have the ISCV patch in, and dont mind sending it over, I would like to give it a shot... nonschlont @ aol
TIA
Also, have you tried entering the new definitions manually through ECUFlash? (right click table --> select new --> add scaling for x axis blah blah blah) That always works for me when the new definitions won't take in the xml.
I've ran into this problem myself, and found that ECUFlash cannot be open when adding definitions directly to the xml. Have you tried this yet?
Also, have you tried entering the new definitions manually through ECUFlash? (right click table --> select new --> add scaling for x axis blah blah blah) That always works for me when the new definitions won't take in the xml.
Also, have you tried entering the new definitions manually through ECUFlash? (right click table --> select new --> add scaling for x axis blah blah blah) That always works for me when the new definitions won't take in the xml.
Boost control is fully tested and it works flawlessly with the new scaling. The other scalings are fine as this only relates to boost control. Also please see that note about the multi128 scaling being out of wack
, couple post above this one.
