TephraMod V7
Oct 25, 2009, 02:03 PM
#736
Evolving Member
iTrader: (16)
Join Date: Feb 2007
Location: Fort Wayne, IN
Posts: 347
Likes: 0
Received 0 Likes
on
0 Posts
I thought maybe I hit the max number of items to be in the list box so I deleted some I'd never use and still had the error. Oh well at least there are ways around it.
Oct 25, 2009, 02:40 PM
#737
Hey, all. I had some problems when installing the v7 ROM. I have 94170008 and according to the first and second post I'm supposed to use 96530706, so I did that. I replaced the 9653xxxx with the information in the 9417xxxx file then I saved it. When I go to open Ecu flash a window pops up that says Xmlhandlerhelper: Parse error on line 1; column 1: error occured while parsing element. So I click on OK (the only option I can click on). Then Ecu flash opens. And I go to open my v7 ROM and another window opens that says Unknown ROM Image. What am I doing wrong? It's pretty straight forward. I didn't have this problem when doing the EGR mod... insight would be greatly appreciated. Thanks in advance.
Oct 25, 2009, 05:06 PM
#739
Evolving Member
iTrader: (16)
Join Date: Feb 2007
Location: Fort Wayne, IN
Posts: 347
Likes: 0
Received 0 Likes
on
0 Posts
Just got done with a small tuning session. I just want to say thanks for all your hard work, us evo guys really have a slick set-up with this awesome community!
From the ROMs to the Virtual Dyno...thanks!
From the ROMs to the Virtual Dyno...thanks!
Oct 25, 2009, 05:20 PM
#740
I asked to have the following EvoScan def added to the second post:
<DataListItem DataLog="Y" Color="" Display="Manifold Air Temp" LogReference="MAT" RequestID="09" Eval="1.8*x-40" Unit="deg F" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="-40" GaugeMax="300" ChartMin="-40" ChartMax="300" ScalingFactor="1" Notes="" />
Last edited by Creamo3; Oct 25, 2009 at 05:22 PM.
Oct 25, 2009, 05:41 PM
#741
Newbie
Join Date: Oct 2008
Location: SLC
Posts: 57
Likes: 0
Received 0 Likes
on
0 Posts
Help please1
Ok I tried to use 96530706-tephraMod V7 but after I flash it the car won't start. I noticed the Rom Info was blank where inherits usually is. Is that normal or could that be the reason it doesn't start?
Oct 25, 2009, 05:46 PM
#742
Ok guys, I'm having a slight issue with 96530716 SD version. I'm running the Omni 4 bar map sensor with the updated scaling added in that JOT posted earlier. Previously I was on a 94170015 map that I had set up to log MAP through the Omni 4 bar and it worked perfectly. Pre-SD I was seeing 24.5psi with a 291 load %, now with the SD patch I'm seeing 25.5psi and only 221 load % as called out in Evoscan. And on top of it all, my fuel map is being read so horribly (as in 8.0afr map is actually 11.7 on the WBo2, and my entire tuned fuel map is now being output in the 16-17afr range with a max of 13.6afr in boost according to the LC-1) that the only way I could run it safely was to swap in the entire low octane fuel map and add quite a bit of fuel to the lower load sections for throttle crossover points. Now I'm assuming that pretty much everyone else is running the standard 3 bar settings with no issue, so I'm leaning towards incorrect MAP sensor scaling.
Currently I'm still on stock turbo and stock injectors, with mild cams (hks 272's) and every other bolt-on part and open dump for no spiking and controlled through my homemade mbc (which works fantastic, never spikes or oscillates).
Has anyone else had this issue as well with the Omni 4 bar scaling? I can force it to sort of work for now, but it's really becoming aggravating. Help! LOL
*Edit: Been going over my last log for the night, and I hit a max of 26.6psi with a max load/"kpa" of 225. By my calculations it should be in the 290kpa range which would put me solidly where I used to be on my maf setup. Oh, and this was at 5250rpms as well, so it wasn't that high in the rpm range.
Currently I'm still on stock turbo and stock injectors, with mild cams (hks 272's) and every other bolt-on part and open dump for no spiking and controlled through my homemade mbc (which works fantastic, never spikes or oscillates).
Has anyone else had this issue as well with the Omni 4 bar scaling? I can force it to sort of work for now, but it's really becoming aggravating. Help! LOL
*Edit: Been going over my last log for the night, and I hit a max of 26.6psi with a max load/"kpa" of 225. By my calculations it should be in the 290kpa range which would put me solidly where I used to be on my maf setup. Oh, and this was at 5250rpms as well, so it wasn't that high in the rpm range.
Last edited by Slo_crx1; Oct 25, 2009 at 06:39 PM.
Oct 25, 2009, 06:36 PM
#743
First time tephra mod user here, I'm sure I'm not the first one lol.
Thanks for the help. One last question while I'm here (because I'm sure it's been covered), how do I open my rom using the tephra mod?
Oct 25, 2009, 06:46 PM
#745
Yes, that is what I did. I replaced the 9417xxxx with the info in the 9653xxxx file.
First time tephra mod user here, I'm sure I'm not the first one lol.
Thanks for the help. One last question while I'm here (because I'm sure it's been covered), how do I open my rom using the tephra mod?
First time tephra mod user here, I'm sure I'm not the first one lol.
Thanks for the help. One last question while I'm here (because I'm sure it's been covered), how do I open my rom using the tephra mod?
Oct 25, 2009, 06:47 PM
#746
Actually I have another rather dumb question to add to my post above...I'm re-reading through the older "links to jcsbanks Speed Density patches" thread, and it mentions that the scaling that I added has only to do with setting up the speed density patch itself and nothing at all to do with adapting the map sensor itself. If that's the case with this patch as well, then I am to assume that I need to update my scaling voltages for the sensor in the current v7 SD patch and I'm probably running on the stock 3 bar scaling voltages?
Oct 25, 2009, 06:55 PM
#747
Actually I have another rather dumb question to add to my post above...I'm re-reading through the older "links to jcsbanks Speed Density patches" thread, and it mentions that the scaling that I added has only to do with setting up the speed density patch itself and nothing at all to do with adapting the map sensor itself. If that's the case with this patch as well, then I am to assume that I need to update my scaling voltages for the sensor in the current v7 SD patch and I'm probably running on the stock 3 bar scaling voltages?
Oct 25, 2009, 06:59 PM
#749
Well then if that's the case I think I'm screwed so far, as I can't find any scaling definitions for 96530006 in order to rescale the voltages. 
I do think that's the root of my problem though. Might I suggest adding those tables to the xml for future reference for anyone using something other than the stock JDM9/evo X map sensor?
I do think that's the root of my problem though. Might I suggest adding those tables to the xml for future reference for anyone using something other than the stock JDM9/evo X map sensor?
Oct 25, 2009, 07:02 PM
#750
Well then if that's the case I think I'm screwed so far, as I can't find any scaling definitions for 96530006 in order to rescale the voltages.
I do think that's the root of my problem though. Might I suggest adding those tables to the xml for future reference for anyone using something other than the stock JDM9/evo X map sensor?
I do think that's the root of my problem though. Might I suggest adding those tables to the xml for future reference for anyone using something other than the stock JDM9/evo X map sensor?