Notices
ECU Flash

TephraMod V7

Thread Tools
 
Search this Thread
 
Old Oct 13, 2009 | 09:30 PM
  #271  
Fast_Freddie's Avatar
Evolved Member
Veteran: Navy
iTrader: (50)
 
Joined: Jun 2007
Posts: 2,706
Likes: 12
From: Lexington Park, MD
Originally Posted by simple_lancer
- You will probably need to adjust your low long term fuel trims, mine went really negative, so I had to rescale my MAF in the low Hz range (around 19-75Hz). You could also slightly reduce your latency, as the JDM cars run a higher value
- Your cold start will not be as smooth as before, but reasonable
I have noticed this going from the 0011 rom also... my fuel trims went about 6% more negative and cold start is all over the place. I spent 8 hours today messing with the car, and got the fuel trims back in check only to find out they are nowhere close to the AFR map values and will not have enough "play space" to get the AFR back in check. Before I was at about 11.6 actual AFR and an 11.5 displayed AFR... when I rescaled and got the fuel trims back in check, actual AFRs were 12.2 and displayed AFR was 10.1... this was scaling 750cc injectors at 713 and upping the latencies quite a bit, ending with a -4% for LTFT low and mid.

I switched every map under the "Fuel" tab from my 0011 rom to the 7006 and I am leaving it where it is... (LTFT Low= -9, LTFT Mid= -9) as the Actual AFR is very close to displayed AFR...

Cold start is still less than desired I will have to work on that some more... maf compensation helped but just messed up other stuff even worse...
Old Oct 13, 2009 | 10:32 PM
  #272  
dhammans's Avatar
Evolving Member
iTrader: (3)
 
Joined: Jun 2003
Posts: 105
Likes: 0
From: Dallas, TX
Originally Posted by Fast_Freddie
I have noticed this going from the 0011 rom also... my fuel trims went about 6% more negative and cold start is all over the place. I spent 8 hours today messing with the car, and got the fuel trims back in check only to find out they are nowhere close to the AFR map values and will not have enough "play space" to get the AFR back in check. Before I was at about 11.6 actual AFR and an 11.5 displayed AFR... when I rescaled and got the fuel trims back in check, actual AFRs were 12.2 and displayed AFR was 10.1... this was scaling 750cc injectors at 713 and upping the latencies quite a bit, ending with a -4% for LTFT low and mid.

I switched every map under the "Fuel" tab from my 0011 rom to the 7006 and I am leaving it where it is... (LTFT Low= -9, LTFT Mid= -9) as the Actual AFR is very close to displayed AFR...

Cold start is still less than desired I will have to work on that some more... maf compensation helped but just messed up other stuff even worse...
For some reason I seriously doubt that AFR was the value/scaling that the Mitsubishi engineers used when calibrating the factory ECU fuel tables.
Old Oct 13, 2009 | 10:36 PM
  #273  
GST Motorsports's Avatar
Account Disabled
iTrader: (8)
 
Joined: Sep 2007
Posts: 3,366
Likes: 0
From: Hayward
People still think the fuel map "AFR" values should match the actual AFR the car is running?
Old Oct 13, 2009 | 10:38 PM
  #274  
dhammans's Avatar
Evolving Member
iTrader: (3)
 
Joined: Jun 2003
Posts: 105
Likes: 0
From: Dallas, TX
Originally Posted by GST Motorsports
People still think the fuel map "AFR" values should match the actual AFR the car is running?
Apparently so. I've always assumed it was based on (some amount) of fuel per grams/rev like the DSM. I don't understand why ECUFlash still represents it as an AFR value though, it is misleading. That doesn't entirely explain it, as different values are required to maintain a flat AFR at different revs.

I have been doing some reading on the forums trying to get a better understanding of how the ECU calculates load. I'm hoping that there is someone out there that really knows exactly what it's doing but I have yet to read that post. Looking at the Motec for example if you choose to use a MAF you simply have a table that injects fuel proportional to the amount of air entering the engine as metered by the MAF. Assuming standard compensation tables (temp, etc) once the ECU is fully mapped it will run exactly what you told it to. You could swap fairly major parts and very little to no adjustment is necessary. In theory, there's no reason the EVO ECU can't do the same thing. However, in practice it appears that there is a reason.

Last edited by dhammans; Oct 14, 2009 at 01:30 AM.
Old Oct 14, 2009 | 01:29 AM
  #275  
project_skyline's Avatar
Evolved Member
iTrader: (30)
 
Joined: Jun 2007
Posts: 2,532
Likes: 1
From: Colorado
This thread has exploded. It would be awesome to have a V7 IX rom, any updates on it?
Old Oct 14, 2009 | 02:37 AM
  #276  
Slo_crx1's Avatar
Evolved Member
iTrader: (9)
 
Joined: Sep 2007
Posts: 821
Likes: 1
From: Simpson, PA
Originally Posted by GST Motorsports
People still think the fuel map "AFR" values should match the actual AFR the car is running?
I figured they just displayed it as a "dummy" value that was easily understandable at first glance and obviously not a real world value. Sure it looks weird, but it still beats looking at injector mS times instead lol.



Now to try and get this straight since I've been out of the loop for the past 8 pages...

MAP scaling does NOT need to be applied when using the Omni 4 bar? Only alterations to the VE table instead? Reason I'm double checking is this is for the SD patched version and not the maf version and the scaling for the Omni sensor is much different than the stock 3 bar. Possibility of perhaps using an "offset" table for different map sensors so major mods to the VE tables won't have to be done in order to get the car started?
Old Oct 14, 2009 | 03:39 AM
  #277  
fixem2's Avatar
Evolved Member
iTrader: (30)
 
Joined: Dec 2003
Posts: 929
Likes: 0
From: USA
FOrgive me if this has been answered. Phenem, when you "disable" bit 11 in FAA I show the ROM with a value of "0". In the spreadsheet that was made a awhile back it shows this is the enable code and disable is "1". Is the spreadsheet incorrect?
Old Oct 14, 2009 | 04:20 AM
  #278  
rolly1818's Avatar
Registered User
 
Joined: Nov 2007
Posts: 1,507
Likes: 2
From: Trinidad
Originally Posted by simple_lancer
I'd stick with 96530706 as there are ALOT more people running it and more tables available. There's always new tables being discovered, and far more support from the community. Tephra will be pushing the 96530706 to be the 'universal' evo 8 rom to ease his workload on future releases.

The JDM roms tend to get neglected by the guys here, because hardly anyone runs them.

By the way, it says you drive an evo ix in your profile, the 96530706 is for evo 8s and possibly 7s. Evo 9 roms are wayyyy different!
yeah i know i have a JDM IX lol..i am patiently waiting on 88570008

there is a lot of support for 9055 as well, there will be a V7 for it as well. i guess i can give both a try and see.

PS: its for a friend!
Old Oct 14, 2009 | 04:45 AM
  #279  
Oracle1's Avatar
Evolving Member
iTrader: (1)
 
Joined: Nov 2005
Posts: 425
Likes: 0
Ahh maan.....

More upgrades - loving it....

88570008 please Dave when your ready. Do you need an up-to-date XML for it?
Old Oct 14, 2009 | 05:00 AM
  #280  
SeanV's Avatar
Evolving Member
 
Joined: Feb 2008
Posts: 214
Likes: 1
From: South Africa
I am having problems with the new V7 patches.

I have downloaded both Tephra's original Rom he posted int the first post of this thread, and also this one from Phenem - see below



EDM Evo VIII

Option 2 (v7 + Mods) - Download | Mirror

* Immob. fixed to work on EDM cars
* 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)


I then used the XLS file posted up earlier and converted my old map tables over to the big version, and also copied over everything else from my V7T6 Rom into the new Bigmaps ROM.

I first flashed my car with Tephra's ROM he posted, the car starts perfectly and idles great.

I then rev the car a bit, while it is stationary, and at around 2000rpm there is a major misfire and at the same time I can hear a relay chattering by the drivers side fuse box. (My Evo is a RHD)
Release the throttle pedal and the car idles fine.

I then flash my car with Phenems ROM as I mentioned above, and I have the exact same problem.

I then disable Valet mode for both ROMS, and also set the Valet Mode RPM to 8000. Reflash the car again with both Tephra's and Phenems ROMS and I have the same problem.

This morning I tried converting my mates Evo to the BigMaps, his Evo8 has the same ROM as mine - 96530006 EDM models - to the new Bigmaps, flash his car after copying everything over and his car also starts fine but has the exact same problem when I try to rev it.

The only difference between the cars is that mine uses ECU controlled boost and my friends uses a EVC6 to control boost.

I have tripled checked everything to make sure that all the values I copied over are exactly the same as my previous ROM - 96530706 V7T6 and it all checks out fine.

Anybody have any ideas what may be wrong?
Have I missed something?

A shot in the dark here......I suspect it may have something to do with control of the fuel pump relays which sit by the cabins fuse box, which would explain why the car is misfiring in tune with the relay chattering.

any help appreciated... thx
Old Oct 14, 2009 | 05:06 AM
  #281  
evl08's Avatar
Evolving Member
iTrader: (2)
 
Joined: Apr 2005
Posts: 112
Likes: 1
From: Melbourne, Australia
Originally Posted by dhammans
I don't understand why ECUFlash still represents it as an AFR value though, it is misleading. That doesn't entirely explain it, as different values are required to maintain a flat AFR at different revs.
When lean spool is enabled, the ecu interpolates between the fuel map and the lean spool AFR map to calculate the AFR value. Lean spool causes the AFR to lean out the fuel map by around 1 AFR point and gradually richens the AFR closer to the fuel map values the longer you are accelerating, so you will find that a 4th gear pull will start to see the actual AFR's closer to the fuel map than a 1st or 2nd gear pull.

The fuel map is a close representation of what the actual AFR will be when lean spool is disabled. Rescaling the MAF can also help to get the actual values close to the fuel map.
Old Oct 14, 2009 | 05:06 AM
  #282  
simple_lancer's Avatar
Newbie
iTrader: (1)
 
Joined: Apr 2008
Posts: 32
Likes: 0
From: Sydney, Australia
Nah sounds like valet is on.
Leave valet on in tephramod options, and hold the accelerator pedal down for 3 sec until your engine light flashes.

make sure you haven't selected the accelerator as your alt map toggle setting.
Every tephramod I have used enables valet mode the first time you flash.
Old Oct 14, 2009 | 05:08 AM
  #283  
tephra's Avatar
Thread Starter
EvoM Guru
iTrader: (6)
 
Joined: Feb 2007
Posts: 9,486
Likes: 66
From: Melbourne, Australia
Sean - Launch mode?

Can you provide a log of said incident?

rpm/load/psi//knocksum/timing/afr/tps if you can
Old Oct 14, 2009 | 05:19 AM
  #284  
SeanV's Avatar
Evolving Member
 
Joined: Feb 2008
Posts: 214
Likes: 1
From: South Africa
Originally Posted by tephra
Sean - Launch mode?

Can you provide a log of said incident?

rpm/load/psi//knocksum/timing/afr/tps if you can
sure will do in the next 20 minutes or so.
Old Oct 14, 2009 | 05:27 AM
  #285  
Jack_of_Trades's Avatar
Evolved Member
iTrader: (17)
 
Joined: Jun 2007
Posts: 3,523
Likes: 2
From: Opelika,AL
These scalings SHOULD be correct now.

Originally Posted by Jack_of_Trades

Code:
<scaling name="psia16 JDM3barMAP" 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 JDM3barMAP" 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 JDM3barMAP" 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"/>

<scaling name="psia16 OMNI3BarMAP" units="psia" toexpr="x/(5.616*2)" frexpr="x*(2*5.616)" format="%.1f" min="0" max="29.6" inc="0.1" storagetype="uint16" endian="big"/>
<scaling name="psia8 OMNI3BarMAP" units="psia" toexpr="x/(5.616*2)" frexpr="x*(2*5.616)" format="%.1f" min="0" max="22.7" inc="0.1" storagetype="uint8" endian="big"/>
<scaling name="BoostErrorPsi OMNI3BarMAP" units="psi" toexpr="(x-128)/(8*5.616)" frexpr="x*8*5.616+128" format="%.1f" min="-2.8" max="2.8" inc="0.1" storagetype="uint16" endian="big"/>

<scaling name="psia16 OMNI4barMAP" units="psia" toexpr="x/(4.23*2)" frexpr="x*(2*4.23)" format="%.1f" min="0" max="39.2" inc="0.1" storagetype="uint16" endian="big"/>
<scaling name="psia8 OMNI4barMAP" 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 OMNI4barMAP" 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"/>

<scaling name="psia16 GM3barMAP" units="psia" toexpr="x/(5.728*2)" frexpr="x*(2*5.728)" format="%.1f" min="0" max="29" inc="0.1" storagetype="uint16" endian="big"/>
<scaling name="psia8 GM3barMAP" units="psia" toexpr="x/(5.728*2)" frexpr="x*(2*5.728)" format="%.1f" min="0" max="22.3" inc="0.1" storagetype="uint8" endian="big"/>
<scaling name="BoostErrorPsi GM3barMAP" units="psi" toexpr="(x-128)/(8*5.728)" frexpr="x*8*5.728+128" format="%.1f" min="-2.8" max="2.8" inc="0.1" storagetype="uint16" endian="big"/>

<scaling name="psia16 Kavlico3.5barMAP" units="psia" toexpr="(x/(4.098*2))-6.25" frexpr="(x+6.25)*(2*4.098)" format="%.1f" min="0" max="34.3" inc="0.1" storagetype="uint16" endian="big"/>
<scaling name="psia8 Kavlico3.5barMAP" units="psia" toexpr="(x/(4.098*2))-6.25" frexpr="(x+6.25)*(2*4.098)" format="%.1f" min="0" max="24.9" inc="0.1" storagetype="uint8" endian="big"/>
<scaling name="BoostErrorPsi Kavlico3.5barMAP" units="psi" toexpr="(x-128)/((8*4.098)-6.25)" frexpr="x*((8*4.098)-6.25)+128" format="%.1f" min="-4.8" max="4.8" inc="0.1" storagetype="uint16" endian="big"/>

<scaling name="psia16 Kavlico5barMAP" units="psia" toexpr="(x/(2.732*2))-9.39" frexpr="(x+9.39)*(2*2.732)" format="%.1f" min="0" max="51.4" inc="0.1" storagetype="uint16" endian="big"/>
<scaling name="psia8 Kavlico5barMAP" units="psia" toexpr="(x/(2.732*2))-9.39" frexpr="(x+9.39)*(2*2.732)" format="%.1f" min="0" max="37.3" inc="0.1" storagetype="uint8" endian="big"/>
<scaling name="BoostErrorPsi Kavlico5barMAP" units="psi" toexpr="(x-128)/((8*2.732)-9.39)" frexpr="x*(8*2.732)-9.39)+128" format="%.1f" min="-10.2" max="10.2" inc="0.1" storagetype="uint16" endian="big"/>


Quick Reply: TephraMod V7



All times are GMT -7. The time now is 06:26 AM.