TephraMOD V6 - testing!
#17
Evolved Member
iTrader: (2)
Thank you for the startup IPW adder alt map addition! Chalk up another guy willing to try out 96530006 whenever you have a chance to get to it.
The min load for WGDC control change ought to make for an interesting change in behavior; I'm looking forward to testing that.
Did mrfred's rear O2 heater sim make it's way into this one, or the stuff acamus was doing regarding manual setting of the OBD-II readiness codes?
The min load for WGDC control change ought to make for an interesting change in behavior; I'm looking forward to testing that.
Did mrfred's rear O2 heater sim make it's way into this one, or the stuff acamus was doing regarding manual setting of the OBD-II readiness codes?
#25
Evolved Member
iTrader: (17)
Join Date: Nov 2005
Location: NNJ
Posts: 2,544
Likes: 0
Received 0 Likes
on
0 Posts
He said most people just set them the same anyway. I know I do. Sure some people argue thats not the right way to tune, but the ECU will still compensate for knock even with both maps the same. Especially now that we have more controll over the stock knock control system I have to agree that low octane maps are not really needed.
#26
EvoM Community Team
iTrader: (15)
For a breakdown:
1) Full gear based WGDC and BDEL lookups
- The gear is selected by looking up "RPM/Speed to Gear" map.
- You can log MUT42 + MUT43 (like 2byte load) to see what values to put on the left side of the map
=Allows you to set a base wastegate duty cycle map for each gear. This helps prevent overshooting boost in higher gears if it is tuned for lower gears, and in the same respect helps to get correct boost in lower gears
--RPM/speed is the best way to calculate gear since the ECU doesn't inherently know what gear it is in
-logging these two items gives you the 2 byte verson of your RPM/speed so that you can use an accurate value for each gear
2) Increased resolution for WGDC, normally its 2%, now it's 1%
WGDC resolution is [by design in the original ECU] only accurate to 2%. IE changing from 50 to 51% duty cycle may actually be the same thing. The resolution has no been increased to allow for 1% changes.
3) Added MrFred/Acamus airflow calc
Allows you to log g/s of airflow
4) Added a min-load otherwise 100% WGDC value
Allows you to run 100% duty cycle until you hit a certain load. This can help spool. It is similar to the older ROM's "min load for boost control" value. On newer roms [by default design] it is set to 0% until minimum load is reached
5) Added boost drop for certain scenarios:
- added boost drop for high-knock
- added boost drop and CEL flash code for AFR mismatch
NOTE: I personally feel these measures could actually do more damage - ENABLE at your own risk!
Allows you to drop boost for high knock or AFR out-of-range events (if you have a wideband wired to the ECU)
6) Buggered off the low oct timing+fuel maps - everyone made them the same anyways...
To save space and confusion these were removed. I'm still not sure how I feel about it, but I haven't ever seen my octane value deviate from 100%
7) Added TPS + MAFIAT corrections to WGDC
Allows you to reduce base wastegate duty cycle based on TPS or based on air temp. Prevents overshooting boost in the cold or too low of boost when hot if used properly. Prevents you from having to shift maps when the weather changes.
8) Added "startup IPW adder" to altmaps - good for E85 dudes
Allows you to add more IPW on startup IE spray more fuel when starting. With E85 in the cold it requires a significant amount of extra fuel on startup for an easy turnover.
#27
Evolved Member
iTrader: (26)
Join Date: Oct 2005
Location: Pittsburgh
Posts: 1,712
Likes: 0
Received 0 Likes
on
0 Posts
Least this is what I read before - Maybe this changed?
Update: Tephra beat me by 1 minute, darn........
#29
in 2.5+ they need to go in the "<Mode2 name="Mode2" type="Data List Items">" section...
in answer to the previous Q about 1.2 v 1.3. Sorry the ROM is still setup for 1.2, but my XML is 1.3 (I use 1.3 in my ROM... and I just copied the XML from my evoscan... oops)
in answer to the previous Q about 1.2 v 1.3. Sorry the ROM is still setup for 1.2, but my XML is 1.3 (I use 1.3 in my ROM... and I just copied the XML from my evoscan... oops)