Notices
ECU Flash

TephraMod V7

Thread Tools
 
Search this Thread
 
Old Oct 13, 2009 | 03:49 PM
  #256  
lan_evo_mr9's Avatar
Evolved Member
iTrader: (10)
 
Joined: Feb 2006
Posts: 1,097
Likes: 2
From: MD
I just downloaded the evo8 v7 just to see what it looks like. All I have to say is, Holy Crap! Awesome work, so organized, very simplistic, truly awesome. Thank you all for all the hard work and development put forth for this whole project. I can't wait for the 9 rom to be unleashed after seeing that! So excited!
Reply
Old Oct 13, 2009 | 03:53 PM
  #257  
simple_lancer's Avatar
Newbie
iTrader: (1)
 
Joined: Apr 2008
Posts: 32
Likes: 0
From: Sydney, Australia
Originally Posted by daymean
I am guessing that the EDM Evo VIII rom will work on my car JDM Evo 8 MR, currently running 96260009...?
I've got it running on my JDM8MR 96260009.
There are a few things which are a bit peculiar that you have to change.

- In Periphery bits F9A there's a mystery bit that you have to change or else the car won't start. My tuning laptop is broken at the moment so I can't look at the exact bit
Compare the periphery bits F9A between 96260009 and 96530706 and make sure the bit that is enabled in 96260009 gets copied across to 96530706
- Leave the Rear O2 periphery bit on, then you'll need to apply the rear o2 heater disable patch, and then you have to turn the rear o2 simulator on under tephramod options. Yes I know the JDM doesn't have a rear o2, but the rom goes spastic if you turn it off (fuel trims don't change)
- You have to turn FCA bit 15 off or the car will throw a CEL about there not being an EGR valve (JDM cars dont have one)
- You may have issues with the immobiliser codes, again I would need to look in my laptop I did have mine working with some tweaking.
- You will probably get mad throttle hang, theres a thread about fixing it
- 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
- You will probably need to adjust your decel fuel cut delay tables, or you will go really rich when you liftoff the throttle
- Your cold start will not be as smooth as before, but reasonable


It was a pain to get it running good, but once you do, the extra features are well worth it! 96530706 is also really smooth when cruising around!
PM me if you get stuck!
Reply
Old Oct 13, 2009 | 03:57 PM
  #258  
3gturbo's Avatar
Evolved Member
iTrader: (4)
 
Joined: Dec 2005
Posts: 571
Likes: 8
From: Charlotte
Originally Posted by Ted B
Ok, that's what we've always done, but when I think of reflashing my ECU (presently 94170015) with a 96530006 ROM, a red flag pops up in my mind. Am I just being paranoid? LOL If you're telling me that works, I'm fine.
Yes it works.
Reply
Old Oct 13, 2009 | 04:23 PM
  #259  
colonelfox's Avatar
Evolving Member
iTrader: (41)
 
Joined: Dec 2003
Posts: 242
Likes: 0
From: Coatesville PA
Originally Posted by Ted B
Ok, that's what we've always done, but when I think of reflashing my ECU (presently 94170015) with a 96530006 ROM, a red flag pops up in my mind. Am I just being paranoid? LOL If you're telling me that works, I'm fine.
It'll work. I thought I missed something with the beta V7 version when none of the version numbers made sense but the version number isn't what is important to the ECU ultimately.
Reply
Old Oct 13, 2009 | 04:30 PM
  #260  
JordanS4's Avatar
Evolved Member
iTrader: (11)
 
Joined: Nov 2006
Posts: 1,419
Likes: 2
From: Fairfax
I'm willing to test for IX MAF if you need more people
Reply
Old Oct 13, 2009 | 05:05 PM
  #261  
fostytou's Avatar
EvoM Community Team
iTrader: (15)
 
Joined: Sep 2006
Posts: 3,143
Likes: 7
From: Aurora, IL
I like the extra 1/0 naming scheme for SD/MAF. If nothing else it prevents having to totally re-do xml when tuning a basic/normal rom compared to your highly modified rom.

Last edited by fostytou; Oct 13, 2009 at 05:08 PM.
Reply
Old Oct 13, 2009 | 05:20 PM
  #262  
03whitegsr's Avatar
Evolved Member
iTrader: (8)
 
Joined: Nov 2006
Posts: 4,001
Likes: 17
From: Utah
Yep, I had a little incident where trying to help a local out just turned into a huge mess since my 94170015 ROM had so much more defined/renamed compared to the "stock" 94170008xml. After that, I started doing the xmls so I could always have a completely stock xml file for each rom in case I ever had to mess with somebody else's car.
Reply
Old Oct 13, 2009 | 06:14 PM
  #263  
lan_evo_mr9's Avatar
Evolved Member
iTrader: (10)
 
Joined: Feb 2006
Posts: 1,097
Likes: 2
From: MD
I found an excel sheet for converting the normal maps to big maps on an evo 8 but not a 9. Is there one out there?
Reply
Old Oct 13, 2009 | 06:31 PM
  #264  
tephra's Avatar
Thread Starter
EvoM Guru
15 Year Member
iTrader: (6)
 
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
see post #3

Last edited by tephra; Oct 13, 2009 at 08:29 PM.
Reply
Old Oct 13, 2009 | 06:35 PM
  #265  
Jack_of_Trades's Avatar
Evolved Member
iTrader: (17)
 
Joined: Jun 2007
Posts: 3,523
Likes: 2
From: Opelika,AL
Ok guys, before I finalize on anything here I need someone to look over everything for me.

MAP SENSOR SCALING FOR PSI BASED BOOST CONTROL

EDIT: errors were fixed on 10/14/09 these scalings should be correct now

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"/>

Last edited by Jack_of_Trades; Oct 14, 2009 at 05:26 AM.
Reply
Old Oct 13, 2009 | 06:51 PM
  #266  
lan_evo_mr9's Avatar
Evolved Member
iTrader: (10)
 
Joined: Feb 2006
Posts: 1,097
Likes: 2
From: MD
Originally Posted by tephra
https://www.evolutionm.net/forums/7604462-post202.html



Just copy/paste the new axis's for the IX into the top map - ensuring the last axis value is 1000000 still

Awesome! thanks
Reply
Old Oct 13, 2009 | 07:19 PM
  #267  
Ted B's Avatar
EvoM Guru
20 Year Member
Photogenic
Photoriffic
Liked
iTrader: (6)
 
Joined: Aug 2004
Posts: 6,334
Likes: 63
From: Birmingham, AL
Originally Posted by Jack_of_Trades
Ok guys, before I finalize on anything here I need someone to look over everything for me.
MAP SENSOR SCALING FOR PSI BASED BOOST CONTROL
Good job. This should be implemented into the base files when perfected.

On another note, can the large maps easily be made compatible with Map Tracer - either standalone or EVOScan based versions?
Reply
Old Oct 13, 2009 | 07:25 PM
  #268  
rolly1818's Avatar
Registered User
 
Joined: Nov 2007
Posts: 1,507
Likes: 2
From: Trinidad
I've got it running on my JDM8MR 96260009.
There are a few things which are a bit peculiar that you have to change.

- In Periphery bits F9A there's a mystery bit that you have to change or else the car won't start. My tuning laptop is broken at the moment so I can't look at the exact bit
Compare the periphery bits F9A between 96260009 and 96530706 and make sure the bit that is enabled in 96260009 gets copied across to 96530706
- Leave the Rear O2 periphery bit on, then you'll need to apply the rear o2 heater disable patch, and then you have to turn the rear o2 simulator on under tephramod options. Yes I know the JDM doesn't have a rear o2, but the rom goes spastic if you turn it off (fuel trims don't change)
- You have to turn FCA bit 15 off or the car will throw a CEL about there not being an EGR valve (JDM cars dont have one)
- You may have issues with the immobiliser codes, again I would need to look in my laptop I did have mine working with some tweaking.
- You will probably get mad throttle hang, theres a thread about fixing it
- 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
- You will probably need to adjust your decel fuel cut delay tables, or you will go really rich when you liftoff the throttle
- Your cold start will not be as smooth as before, but reasonable


It was a pain to get it running good, but once you do, the extra features are well worth it! 96530706 is also really smooth when cruising around!
PM me if you get stuck!
Thanks a million, thats the response i am looking for. the immo disable is no prob, and i have run an AUDM rom on my JDM IX, so i dont think that the rear O2 should be an issue...

my question is, would it make more sense to go 9055 (JDM VII)???

there should be no compatibility issues evo 7 and 8 are identical engine and drivetrain wise (ACD/AYC)... input anyone??
Reply
Old Oct 13, 2009 | 08:29 PM
  #269  
tephra's Avatar
Thread Starter
EvoM Guru
15 Year Member
iTrader: (6)
 
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
I've posted up my version of the BIGMAP translator. 3rd post

The only complicated thing is remembering to make the last axis value 1000000 (so when you copy your fuel map in and the rpm axis is shorter make the last value 1000000.

If someone can workout how to fix that I would be happy
Reply
Old Oct 13, 2009 | 08:35 PM
  #270  
simple_lancer's Avatar
Newbie
iTrader: (1)
 
Joined: Apr 2008
Posts: 32
Likes: 0
From: Sydney, Australia
Originally Posted by rolly1818
Thanks a million, thats the response i am looking for. the immo disable is no prob, and i have run an AUDM rom on my JDM IX, so i dont think that the rear O2 should be an issue...

my question is, would it make more sense to go 9055 (JDM VII)???

there should be no compatibility issues evo 7 and 8 are identical engine and drivetrain wise (ACD/AYC)... input anyone??
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!

Last edited by simple_lancer; Oct 13, 2009 at 08:38 PM.
Reply



All times are GMT -7. The time now is 03:35 PM.