Notices
ECU Flash

Sputtering/misfire when going from v5 to v7

Thread Tools
 
Search this Thread
 
Old Mar 7, 2016 | 04:31 PM
  #1  
jmrussell89's Avatar
Thread Starter
Newbie
Veteran: Air Force
 
Joined: Aug 2013
Posts: 70
Likes: 2
From: Toytaville, Overit
Sputtering/misfire when going from v5 to v7

Evening!

I've been spending a few days converting my v5 to v7 of Tephramod on my '06 Evo IX. Everything was going pretty well, until I realized it was sputtering a bit, and the IDC was considerbly higher than normal. It would seem like fuel cut, or maybe I had some sort of spark issue.

However, I went home, and reflashed v5 and doing the same sort of pull, it was gone. Now, I'm no expert on this by any means, but I followed all instructions when copying maps and they look fine. I've attached a zip with the log I noticed it, and the v5 and v7 roms. I converted with big map translator, etc.

The knock isn't bad, and everything else is great. The sputter/misfire has to go, and I really don't know where to start. Oh, and for the record, I use a MBC and have not really touched the boost tables (probably where my error is anyway).

Thanks!
Attached Files
File Type: rar
Roms.rar (276.5 KB, 0 views)
Old Mar 8, 2016 | 02:49 PM
  #2  
nissanfanatic's Avatar
Newbie
iTrader: (1)
 
Joined: Jan 2016
Posts: 44
Likes: 1
From: Gainesville, Florida
Check these:

Global Fuel Settings
Fuel Cut Multiplier - Allows you to choose whether you want to use the Fuel Cut Load X1 table or Fuel Cut Load X2 table for your fuel cut.
Fuel Cut Load X1 - Allows input of the fuel cut load values for varied RPM. If load exceeds these values for a given RPM, fuel cut will be activated to protect from an overboost.
Check to see if you are hitting the load values in these tables.
Old Mar 8, 2016 | 04:22 PM
  #3  
Klaiceps's Avatar
Evolved Member
iTrader: (18)
 
Joined: Nov 2014
Posts: 508
Likes: 28
From: Honolulu, HI
What MAP sensor are you using? Did you change it? Ensure your MAP sensor scaling is correct in V7. If the values are incorrect the ECU will target the wrong load cells, which may be the cause of your IDCs being higher than normal.
Old Mar 8, 2016 | 08:47 PM
  #4  
jmrussell89's Avatar
Thread Starter
Newbie
Veteran: Air Force
 
Joined: Aug 2013
Posts: 70
Likes: 2
From: Toytaville, Overit
I looked around in my v5 file, and could not find anything related to the MAP sesnsor. Hmm.

Edit: Changed around the xmls for mrfred's JDM MAP tables and have them in my v5 now. Definitly a difference there. Will report on good or bad results!

Last edited by jmrussell89; Mar 8, 2016 at 09:06 PM.
Old Mar 15, 2016 | 04:55 PM
  #5  
jmrussell89's Avatar
Thread Starter
Newbie
Veteran: Air Force
 
Joined: Aug 2013
Posts: 70
Likes: 2
From: Toytaville, Overit
Sorry for the delay, busy week.

Anyway, changed MAP data over, went around and cruised and fine...well sorta. Seems to still happen in second gear...hmm. To clarify, this is under load, not daily driving.
Old Mar 15, 2016 | 05:18 PM
  #6  
Klaiceps's Avatar
Evolved Member
iTrader: (18)
 
Joined: Nov 2014
Posts: 508
Likes: 28
From: Honolulu, HI
Couple questions:
  1. Are you on SD or still running a MAF?
  2. What MAP sensor are you using?
  3. Do you have a wideband sensor? If so try to log it in Evoscan during a pull.
  4. Around what rpm is your sputtering happening?
Cant' tell much from your datalog other than your IDCs are super high.
Old Mar 15, 2016 | 05:25 PM
  #7  
jmrussell89's Avatar
Thread Starter
Newbie
Veteran: Air Force
 
Joined: Aug 2013
Posts: 70
Likes: 2
From: Toytaville, Overit
1. Running MAF
2. Standard one...I know, useless, but not in the market for one currently.
3. Running one, but have yet to have it working with the log.
4. Seems like the 3500-4500 range.

I just noticed my Open Loop throttles were not even brought over... Gonna go try again here shortly and see what I get.

Update: Seems all good now! I'll post again if not.

Last edited by jmrussell89; Mar 15, 2016 at 07:00 PM.
Old Mar 17, 2016 | 11:11 AM
  #8  
Klaiceps's Avatar
Evolved Member
iTrader: (18)
 
Joined: Nov 2014
Posts: 508
Likes: 28
From: Honolulu, HI
Awesome! Glad you got that resolved. Just to be on the safe side, I would suggest taking a look at your high IDCs. If you haven't already, might be a good time to upgrade injectors.
Old Mar 17, 2016 | 07:10 PM
  #9  
jmrussell89's Avatar
Thread Starter
Newbie
Veteran: Air Force
 
Joined: Aug 2013
Posts: 70
Likes: 2
From: Toytaville, Overit
Well...
That didn't take long

It went back to doing it, stopped at a rest stop and switched back to v5 until further notice. The IDCs running v5 are fine...so I'm just at a loss at to why I'm getting this issue. A friend mentioned it could be because it's just running too rich. I didn't think so at first, but could the big maps (directly copied over and through the translator) be causing this? AFR gauge isn't reading any different really, so I'm at a bit of a loss.
Old Mar 17, 2016 | 07:12 PM
  #10  
nissanfanatic's Avatar
Newbie
iTrader: (1)
 
Joined: Jan 2016
Posts: 44
Likes: 1
From: Gainesville, Florida
Yep. You would definitely want to recheck AFR and also where you are at with timing. Big map translators don't 100% translate your old map to a new "bigger" map. They just give you a ballpark starting point based on your old map so you aren't starting from scratch.
Old Mar 17, 2016 | 07:34 PM
  #11  
jmrussell89's Avatar
Thread Starter
Newbie
Veteran: Air Force
 
Joined: Aug 2013
Posts: 70
Likes: 2
From: Toytaville, Overit
Yeah, just realized that with a bit more reading...I'll fine tune some stuff and see what I get. Thanks all. Gotta work for a while, so it's gonna be a bit before I'll be back with results.
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
pumpdog720
Lancer Troubleshooting
57
Jul 19, 2017 10:04 PM
Saint47
Evo General
33
Feb 23, 2017 12:42 PM
LancerBenny
Lancer Troubleshooting
3
Jun 30, 2016 09:11 PM
evodrivesme
Evo Engine / Turbo / Drivetrain
15
Aug 23, 2006 08:15 AM
EVOONYOASS
Evo Engine / Turbo / Drivetrain
33
Apr 19, 2006 06:02 PM




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