TephraMod V7
Oct 18, 2009 | 10:24 AM
#437
Very well I'll do it then and post it.
Think thats everything added may have missed one :shrug:
PHP Code:
<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="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="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="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.632" 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="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"/>
Oct 18, 2009 | 10:25 AM
#438
phenem and JOT are you guys going to rewrite the xml for the 88590715 rom to make it as neat as the 96530706 
? Also I'm missing the stupid Alternate WG Duty maps again on the 88590715..can anyone see them?
? Also I'm missing the stupid Alternate WG Duty maps again on the 88590715..can anyone see them?
Last edited by ohhgyeahfasho; Oct 18, 2009 at 10:31 AM.
Oct 18, 2009 | 10:27 AM
#439
I can probably make it match the layout that is currently used in 96530706 for everyone. It's a heck of a lot of work so it'll take me a few days though. Its best if we stick with a certain layout rather than have things totally different in each XML.
Oct 18, 2009 | 10:31 AM
#440
Oct 18, 2009 | 10:31 AM
#441
And on a side note, under 'Mods' I am seeing Alternate Lo Octane Fuel/Timing, but the values are somewhat messy and all over the place, is this how its supposed to look?
And as you can see I have no way of changing my Alt Map WG Duty and BDEL. Can anyone else see them?
Last edited by ohhgyeahfasho; Oct 18, 2009 at 10:38 AM. Reason: NINJA EDIT
Oct 18, 2009 | 10:42 AM
#442
Awesome work guys....
I have loaded the latest XML file, as posted this morning, on my car now and it is working perfectly. Thx to everyone involved.
This is the one I am using
Option 4 (v7 + Mods) - Download | Mirror
* Set Immob. HEX to 0x0040 (check to make sure your old ROM was the same)
* mrfred psi based boost implemented as default (just edit Tephra's gear dependant map)
* OBD II Inspection ready for EVAP and EGR
* Disabled EGR, EVAP, and Idle Tests
* Disabled P0300 code
* Disabled lean spool
* mrfred double fuel cut load limit implmeneted and set to 300 load (change to whatever you need this to be, read more)
This may not be the right place to ask this question.... but if someone can steer me in the right direction, it will greatly appreciated.
Currently I am making us of ECU Controlled boost using LOAD to control the boost.
At this point in time, I have a Defi boost sensor wired into the ECU purely to log boost in Bar.
I want to change over to an Omni4Bar map sensor and then use it for PSI Based Boost Control. Well actually BAR Based boost control will be preferred.
A few questions I have....
1.)
Right now I am a bit confused as to what exactly needs to be done.
As I understand, this thread over here how-to: ECU-based direct boost control , and in particualr, with the instructions posted by Tephra in post number 366.
Does ECU Direct Boost Control without per gear boosting?
While the latest XML files posted in this thread, does ECU Direct Boost Control with per gear boosting?
2.)
If this is the case......Will it be possible to change the XML files posted this morning in Option 4....in particular this table "Boost Desired Engine 'PSI' " to display the units in BAR in the table.
There already seems to be scalings for "Bar" in the XML file based on this
3.)
Lastly... When using the latest XML posted here, Is it just a matter of wiring the Omni4 Bar map sensor into the ECU, setup EvoScan to log boost, and then make the changes to this table "== EDIT THE TABLES BELOW FOR LOAD OR PSI BOOST TARGETING ==" to run Per Gear/ PSI Based Boost?
Thx for helping me clear this up.
I have loaded the latest XML file, as posted this morning, on my car now and it is working perfectly. Thx to everyone involved.
This is the one I am using
Option 4 (v7 + Mods) - Download | Mirror
* Set Immob. HEX to 0x0040 (check to make sure your old ROM was the same)
* mrfred psi based boost implemented as default (just edit Tephra's gear dependant map)
* OBD II Inspection ready for EVAP and EGR
* Disabled EGR, EVAP, and Idle Tests
* Disabled P0300 code
* Disabled lean spool
* mrfred double fuel cut load limit implmeneted and set to 300 load (change to whatever you need this to be, read more)
This may not be the right place to ask this question.... but if someone can steer me in the right direction, it will greatly appreciated.
Currently I am making us of ECU Controlled boost using LOAD to control the boost.
At this point in time, I have a Defi boost sensor wired into the ECU purely to log boost in Bar.
I want to change over to an Omni4Bar map sensor and then use it for PSI Based Boost Control. Well actually BAR Based boost control will be preferred.
A few questions I have....
1.)
Right now I am a bit confused as to what exactly needs to be done.
As I understand, this thread over here how-to: ECU-based direct boost control , and in particualr, with the instructions posted by Tephra in post number 366.
Does ECU Direct Boost Control without per gear boosting?
While the latest XML files posted in this thread, does ECU Direct Boost Control with per gear boosting?
2.)
If this is the case......Will it be possible to change the XML files posted this morning in Option 4....in particular this table "Boost Desired Engine 'PSI' " to display the units in BAR in the table.
There already seems to be scalings for "Bar" in the XML file based on this
3.)
Lastly... When using the latest XML posted here, Is it just a matter of wiring the Omni4 Bar map sensor into the ECU, setup EvoScan to log boost, and then make the changes to this table "== EDIT THE TABLES BELOW FOR LOAD OR PSI BOOST TARGETING ==" to run Per Gear/ PSI Based Boost?
Thx for helping me clear this up.
- I set the scalings for the JDM MAP Sensor since it's the most common. If you run anything other than that sensor, you need to edit the scalings in any of the BLUE tables involved with boost control.
- Right-Click on the table you want to edit and choose 'EDIT MAP'
- Find the Scaling that says 'JDM MAP', click on it and a dropdown list will appear. Choose the appropriate scaling for the MAP Sensor you are using from the dropdown list. Make sure they match whatever scaling type was previously used for the JDM MAP Sensor (i.e; PSIa8,PSIa16 or BoosrErrorPSI).
- Click 'OK' and move on to the next BLUE table for Boost Control.
- That's it, now your tables are scaled for whichever MAP Sensor you are running
Last edited by Jack_of_Trades; Oct 18, 2009 at 10:45 AM.
Oct 18, 2009 | 10:48 AM
#443
Oct 18, 2009 | 11:15 AM
#444
Evolving Member
Joined: Feb 2008
Posts: 214
Likes: 1
From: South Africa
To run PSI base boost control, the first thing required is to make sure all of the tables in the 'Global Boost Control 'TYPE' section have all been edited to match the PSI settings in the parethesis next to the name of each table. Once they all match the PSI settings, the ECU will now target the map sensor instead of load. (no scaling changes ever need to made in the 'Global Boost Control 'TYPE'' section!)
1. I set the scalings for the JDM MAP Sensor since it's the most common. If you run anything other than that sensor, you need to edit the scalings in any of the BLUE tables involved with boost control.
2. Right-Click on the table you want to edit and choose 'EDIT MAP'
3. Find the Scaling that says 'JDM MAP', click on it and a dropdown list will appear. Choose the appropriate scaling for the MAP Sensor you are using from the dropdown list. Make sure they match whatever scaling type was previously used for the JDM MAP Sensor (i.e; PSIa8,PSIa16 or BoosrErrorPSI).
4. Click 'OK' and move on to the next BLUE table for Boost Control.
5. That's it, now your tables are scaled for whichever MAP Sensor you are running
1. I set the scalings for the JDM MAP Sensor since it's the most common. If you run anything other than that sensor, you need to edit the scalings in any of the BLUE tables involved with boost control.
2. Right-Click on the table you want to edit and choose 'EDIT MAP'
3. Find the Scaling that says 'JDM MAP', click on it and a dropdown list will appear. Choose the appropriate scaling for the MAP Sensor you are using from the dropdown list. Make sure they match whatever scaling type was previously used for the JDM MAP Sensor (i.e; PSIa8,PSIa16 or BoosrErrorPSI).
4. Click 'OK' and move on to the next BLUE table for Boost Control.
5. That's it, now your tables are scaled for whichever MAP Sensor you are running
Makes perfect sense now.
I think.One last thing for now......anyway of getting getting the "Boost Desired Engine `PSI`" and "Boost Adder (PSI)" tables to show targeted boost values in "Bar" instead off PSI?
Thx.
Last edited by SeanV; Oct 18, 2009 at 11:45 AM.
Oct 18, 2009 | 11:20 AM
#445
Here's the 88590715 ROM with mods applied:
Download
INSTRUCTIONS: Copy all XML files to %Program Files%\OpenECU\EcuFlash\rommetadata\mitsubishi\evo . No editing needed.
IMPORTANT: If you do not have a JDM MAP, revert all tables in the "MAPSensor" category back to your old ROM's settings. Also, set FEA bit.14 (MAP vs. Baro) to 1.
These are all changes applied to this ROM:
Here are all EvoScan data items that are added with this patch (the Lbs/min below is ACTUAL, not estimated, thanks to Airflow rate calc patch):
Download
INSTRUCTIONS: Copy all XML files to %Program Files%\OpenECU\EcuFlash\rommetadata\mitsubishi\evo . No editing needed.
IMPORTANT: If you do not have a JDM MAP, revert all tables in the "MAPSensor" category back to your old ROM's settings. Also, set FEA bit.14 (MAP vs. Baro) to 1.
These are all changes applied to this ROM:
- Setup for JDM MAP and PSI based boost control (mrfred)
- WGDC Correction Interval set to 1 (Stock = 10)
- Max Total Upward WGDC Correction @ 100% TPS set to 0 (Stock = 10)
- EGR System Disabled (mrfred)
- Max Timing Retard set to -20 degrees (tephra)
- FAA bit.10 disabled ("weird unknown" timing pull at cruise)
- FAA bit.09 disabled (cat-warmup ignition retard)
- FBA bit.00 disabled (lean spool)
- FCA bit.09 disabled (EGR Test)
- OBD Inspection set to Pass all tests (acamus)
- Rear O2 Heater patch applied (mrfred)
- Airflow Rate calculation patch applied (mrfred)
Here are all EvoScan data items that are added with this patch (the Lbs/min below is ACTUAL, not estimated, thanks to Airflow rate calc patch):
PHP Code:
<DataListItem DataLog="Y" Color="" Display="Load1Byte" LogReference="Load1Byte" RequestID="41" Eval="1.2*x" Unit="load" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="270" ChartMin="0" ChartMax="270" ScalingFactor="1" Notes="" Priority="1" Visible="False" />
<DataListItem DataLog="Y" Color="" Display="Boost Error" LogReference="BoostError" RequestID="8A" Eval="0.0241*x-3.087" Unit="psi" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="-25" GaugeMax="25" ChartMin="-25" ChartMax="25" ScalingFactor="1" Notes="" Priority="1" Visible="False" />
<DataListItem DataLog="Y" Color="" Display="Lbs/min" LogReference="LbsMin" RequestID="46" RequestID2="47" Eval="0.00312*x" Unit="lbs/min" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="10000" ChartMin="0" ChartMax="10000" ScalingFactor="1" Notes="" Priority="1" Visible="False" />
<DataListItem DataLog="Y" Color="" Display="Gear" LogReference="Gear" RequestID="40" Eval="x" Unit="units" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="300" ChartMin="0" ChartMax="300" ScalingFactor="1" Notes="" Priority="5" Visible="False" />
Oct 18, 2009 | 12:00 PM
#446
Yeah, that can be added during the next revision. Basically we just need to divide the scaling by 14.7 (atmospheric pressure at sea level).
Oct 18, 2009 | 01:34 PM
#447
Yep, I put two sets of tables in for boost, one scaled for Load and one scaled for PSI. Just use whichever makes sense in your application
Oct 18, 2009 | 02:03 PM
#448
Also, for anyone adding NEW scalings, be sure the FIRST letter is capitalized so the ECUFlash will organize them in alphabetical order in the XML. This makes it much easier for users to find the appropriate scaling in the dropdown lists. The only 2 I didn't update to capital letters was uint8 and uint16 since they were used SOOOO much in all of the tables already and would have taken eon's to change.
Last edited by Jack_of_Trades; Oct 18, 2009 at 02:06 PM.
