TephraMod V7
Oct 12, 2009, 11:55 AM
#167
Whoa whoa whoa... chill out fam!
https://www.evolutionm.net/forums/5627574-post366.html
There are your instructions for 96530006 direct boost control.
https://www.evolutionm.net/forums/5627574-post366.html
There are your instructions for 96530006 direct boost control.
Oct 12, 2009, 12:02 PM
#168
Whoa whoa whoa... chill out fam!
https://www.evolutionm.net/forums/5627574-post366.html
There are your instructions for 96530006 direct boost control.
https://www.evolutionm.net/forums/5627574-post366.html
There are your instructions for 96530006 direct boost control.
We need MrFred to explain in detail WHY we don't need those MAP tables to adjust for ANY map sensor since he found the tables and figured out the different scaling required for each of the popular ones.
Last edited by Jack_of_Trades; Oct 12, 2009 at 12:04 PM.
Oct 12, 2009, 12:19 PM
#169
Because the scale doesn't matter, only the targeted values (which you're specifying based on a scaling in EcuFlash). Hence, the ECU doesn't care about the difference. As a mental exercise, try changing the EcuFlash scalings to voltage. 
It's a similar situation to the BCS; the ECU has no idea that we've replaced our stock BCS with an EGR valve, GM BCS, or some other electronic valve; it only cares about voltage and duty cycle.
It's a similar situation to the BCS; the ECU has no idea that we've replaced our stock BCS with an EGR valve, GM BCS, or some other electronic valve; it only cares about voltage and duty cycle.
Oct 12, 2009, 12:22 PM
#170
So we would need to just create a seperate scaling table for each of the popular MAP sensors off of the voltage/bit value readings?
That would work. would anyone want to make the scalings for these MAP sensors to add to the scaling dropdown list for v7? I definitely want to be able to just punch in the PSI target rather than mess with bit values and voltages, especially when every car I tune could have a different map sensor.
That would work. would anyone want to make the scalings for these MAP sensors to add to the scaling dropdown list for v7? I definitely want to be able to just punch in the PSI target rather than mess with bit values and voltages, especially when every car I tune could have a different map sensor.
Oct 12, 2009, 12:23 PM
#171
Exactly! Logic has the right idea. The MAP sensor does not matter at all! It's just the targeted values which we control through the XML def. and EVOScan logging def.
Changing those two change what MAP sensor you are running because to us the values look different but to the computer they are just formulas which alter the voltages going to the BCS.
The 9653 has no emissions code so that is why you don't have to change the scaling and that is why you have to change the scaling on the 9417 ROM's because it does depend on the values for emissions only!
Changing those two change what MAP sensor you are running because to us the values look different but to the computer they are just formulas which alter the voltages going to the BCS.
The 9653 has no emissions code so that is why you don't have to change the scaling and that is why you have to change the scaling on the 9417 ROM's because it does depend on the values for emissions only!
Oct 12, 2009, 12:28 PM
#173
I found them and changed the scaling names to represent the map sensors they are used for. That way the user can just choose from the scaling list.
Code:
<scaling name="JDM MAP" units="kPa" toexpr="x/3" frexpr="x*3" format="%.1f" min="0" max="350" inc="0.3333" storagetype="uint16" endian="big"/> <scaling name="OMNI 3 BAR MAP" units="kPa" toexpr="x*0.3074" frexpr="x/0.3074" format="%.1f" min="0" max="350" inc="0.3074" storagetype="uint16" endian="big"/> <scaling name="GM 3 BAR MAP" units="kPa" toexpr="x*0.3014" frexpr="x/0.3014" format="%.1f" min="0" max="350" inc="0.3014" storagetype="uint16" endian="big"/> <scaling name="AEM 3.5 BAR MAP" units="kPa" toexpr="x*0.4213-43.1" frexpr="(x+43.1)/0.4213" format="%.1f" min="0" max="400" inc="0.4213" storagetype="uint16" endian="big"/> <scaling name="OMNI 4 BAR MAP" units="kPa" toexpr="x*0.4072" frexpr="x/0.4072" format="%.1f" min="0" max="450" inc="0.4072" storagetype="uint16" endian="big"/> <scaling name="Kavlico 5 BAR MAP" units="kPa" toexpr="x*0.6320-64.7" frexpr="(x+64.7)/0.6320" format="%.1f" min="0" max="550" inc="0.6320" storagetype="uint16" endian="big"/>
Last edited by Jack_of_Trades; Oct 12, 2009 at 06:36 PM.
Oct 12, 2009, 12:31 PM
#174
With this new universal rom for evo 8-9, is possible retarded ign to -15 or -20 degrees? Old roms limited to -10º igntion.
How-to for create this launch phenem!
http://www.youtube.com/watch?v=LRBHANh-_Yg
How-to for create this launch phenem!
http://www.youtube.com/watch?v=LRBHANh-_Yg
https://www.evolutionm.net/forums/7171893-post961.html
Oct 12, 2009, 12:34 PM
#175
JoT, Perfect! That's that data I was referring to!
Can you create an XML so all we have to do is change the scaling in ECUFlash? Just add those scalings in and call the scaling each sensor by name? Then the user can just choose the scaling they want based on the sensor they have?
Also did you see my post above about adding the XML data to the main XML that you sent me? Link here: https://www.evolutionm.net/forums/7600409-post117.html
Can you create an XML so all we have to do is change the scaling in ECUFlash? Just add those scalings in and call the scaling each sensor by name? Then the user can just choose the scaling they want based on the sensor they have?
Also did you see my post above about adding the XML data to the main XML that you sent me? Link here: https://www.evolutionm.net/forums/7600409-post117.html
Oct 12, 2009, 12:37 PM
#176
There are a few others that need to be changed for direct boost control as well...
These are for the JDM3bar. You need all 4 of them for each sensor.
Here they are for the Omni 4-bar
These are for the JDM3bar. You need all 4 of them for each sensor.
Code:
<scaling name="MAP 16bit" units="kPa" toexpr="x/3" frexpr="x*3" format="%.1f" min="0" max="350" inc="0.3333" storagetype="uint16" endian="big"/> <scaling name="psia16" units="psia" toexpr="x/(5.18*2)" frexpr="x*(2*5.18)" format="%.1f" min="0" max="32" inc="0.1" storagetype="uint16" endian="big"/> <scaling name="psia8" units="psia" toexpr="x/(5.18*2)" frexpr="x*(2*5.18)" format="%.1f" min="0" max="24.6" inc="0.1" storagetype="uint8" endian="big"/> <scaling name="BoostErrorPsi" units="psi" toexpr="(x-128)/(8*5.18)" frexpr="x*8*5.18+128" format="%.1f" min="-3.1" max="3.1" inc="0.1" storagetype="uint16" endian="big"/>
Code:
<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"/> <scaling name="psia16" units="psia" toexpr="x/(4.23*2)" frexpr="x*(2*4.23)" format="%.1f" min="0" max="32" inc="0.1" storagetype="uint16" endian="big"/> <scaling name="psia8" units="psia" toexpr="x/(4.23*2)" frexpr="x*(2*4.23)" format="%.1f" min="0" max="30.1" inc="0.1" storagetype="uint8" endian="big"/> <scaling name="BoostErrorPsi" units="psi" toexpr="(x-128)/(8*4.23)" frexpr="x*8*4.23+128" format="%.1f" min="-3.8" max="3.8" inc="0.1" storagetype="uint16" endian="big"/>
Last edited by 03whitegsr; Oct 12, 2009 at 12:49 PM.
Oct 12, 2009, 12:42 PM
#177
JoT, do you want me to add all this stuff to the main XML distribution or can you do it and shoot me an email?
Oct 12, 2009, 12:51 PM
#178
If you are interested in setting you car up like mine in my video, here is the post I made about what I have in order to get this result:
https://www.evolutionm.net/forums/7171893-post961.html
https://www.evolutionm.net/forums/7171893-post961.html
I do look forward to playing with the launch map settings though. I'm sure that having the little blip in my maps for the launch has affected some transitions at autocross and track events.
Oct 12, 2009, 01:00 PM
#179
There are a few others that need to be changed for direct boost control as well...
These are for the JDM3bar. You need all 4 of them for each sensor.
Here they are for the Omni 4-bar
These are for the JDM3bar. You need all 4 of them for each sensor.
Code:
<scaling name="MAP 16bit" units="kPa" toexpr="x/3" frexpr="x*3" format="%.1f" min="0" max="350" inc="0.3333" storagetype="uint16" endian="big"/> <scaling name="psia16" units="psia" toexpr="x/(5.18*2)" frexpr="x*(2*5.18)" format="%.1f" min="0" max="32" inc="0.1" storagetype="uint16" endian="big"/> <scaling name="psia8" units="psia" toexpr="x/(5.18*2)" frexpr="x*(2*5.18)" format="%.1f" min="0" max="24.6" inc="0.1" storagetype="uint8" endian="big"/> <scaling name="BoostErrorPsi" units="psi" toexpr="(x-128)/(8*5.18)" frexpr="x*8*5.18+128" format="%.1f" min="-3.1" max="3.1" inc="0.1" storagetype="uint16" endian="big"/>
Code:
<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"/> <scaling name="psia16" units="psia" toexpr="x/(4.23*2)" frexpr="x*(2*4.23)" format="%.1f" min="0" max="32" inc="0.1" storagetype="uint16" endian="big"/> <scaling name="psia8" units="psia" toexpr="x/(4.23*2)" frexpr="x*(2*4.23)" format="%.1f" min="0" max="30.1" inc="0.1" storagetype="uint8" endian="big"/> <scaling name="BoostErrorPsi" units="psi" toexpr="(x-128)/(8*4.23)" frexpr="x*8*4.23+128" format="%.1f" min="-3.8" max="3.8" inc="0.1" storagetype="uint16" endian="big"/>
- MAP scaling
- Psia16
- Psia8
- BoostErrorPSI
let me work on adding this stuff in the XML and I'll email it to you Phenem.
Last edited by Jack_of_Trades; Oct 12, 2009 at 01:02 PM.
Oct 12, 2009, 01:00 PM
#180
....orrrrrr you need it for PSI based ECU boost control!!! Which apparently can't be done with this rom if we can't calibrate the MAP sensor signal for the ECU to make any use of it. It needs to be done for the ECU to control boost with it at all. If that can't be done already (or added), looks like Tephra's doing the 94170015 rom as well. 