TephraMod V7
yep. gotta log AFR to tune. i tried everything from 14.7 to 16.0. our freeways here are not all that flat and, when i drive to work, there are a few stop lights. between that and around town, i just didn't see much change in MPG. plus, with the stock turbo, the slightest bit of acceleration or hill in the road puts me into boost. if i could stay in vacuum, i'd probably see more of an improvement.
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
:|
I feel bad... I will try and get something done for both 90550001 and 88580007.
looks like I will be out of a job and have HEAPS of time in the nearish future :| hehe
I feel bad... I will try and get something done for both 90550001 and 88580007.
looks like I will be out of a job and have HEAPS of time in the nearish future :| hehe
yep. gotta log AFR to tune. i tried everything from 14.7 to 16.0. our freeways here are not all that flat and, when i drive to work, there are a few stop lights. between that and around town, i just didn't see much change in MPG. plus, with the stock turbo, the slightest bit of acceleration or hill in the road puts me into boost. if i could stay in vacuum, i'd probably see more of an improvement.
just a quick note about the Load Axis for bigmaps:
both Fuel AND Timing use the same Load that the Fuel maps would normal use (ie Load_Baro_n_Temp_Compensated), please keep this in mind for high-altitude tuners
obviously 1byte load is based off Load_Raw - probably a oversight on my behalf now that I think about it
both Fuel AND Timing use the same Load that the Fuel maps would normal use (ie Load_Baro_n_Temp_Compensated), please keep this in mind for high-altitude tuners
obviously 1byte load is based off Load_Raw - probably a oversight on my behalf now that I think about it
Okay.
Its fine. Its actually easiest/best if the BIGMAP just follow teh 1/2byte load we normally log.
Appauldd, it actually doesnt matter, even at high elevation. As long was you know what load the timing and fuel maps are following and your logging that load, your all good.
Tephra any reason why you didnt make all versions of V7 BIGMAPs just follow 1/2byte? It seems like 9417 is the only one following 1/2byte. Probably would be best if they all followed 1/2byte load, so there wasnt any discrepancy about which load to log.
Its fine. Its actually easiest/best if the BIGMAP just follow teh 1/2byte load we normally log.
Appauldd, it actually doesnt matter, even at high elevation. As long was you know what load the timing and fuel maps are following and your logging that load, your all good.
Tephra any reason why you didnt make all versions of V7 BIGMAPs just follow 1/2byte? It seems like 9417 is the only one following 1/2byte. Probably would be best if they all followed 1/2byte load, so there wasnt any discrepancy about which load to log.
I just did some logging of different loads at elevation on 9653 V7.
Its seems that 9653 V7, despite what Tephra said, is following 1/2byte load aka LOAD_RAW.
Tephra, I thought you said that only 9417 V7 followed LOAD_RAW and the other V7 ROMs followed LOAD_BARO+TEMP_COMP?
Would you like to chime in?
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
I just did some logging of different loads at elevation on 9653 V7.
Its seems that 9653 V7, despite what Tephra said, is following 1/2byte load aka LOAD_RAW.
Tephra, I thought you said that only 9417 V7 followed LOAD_RAW and the other V7 ROMs followed LOAD_BARO+TEMP_COMP?
Would you like to chime in?
Its seems that 9653 V7, despite what Tephra said, is following 1/2byte load aka LOAD_RAW.
Tephra, I thought you said that only 9417 V7 followed LOAD_RAW and the other V7 ROMs followed LOAD_BARO+TEMP_COMP?
Would you like to chime in?
whatever they happen to come out as...
Evolving Member
Joined: Jan 2005
Posts: 184
Likes: 15
From: Wiesbaden, germany
Question to all developers here I converted an Evo9 EDM ( Rom 88840013 ) to an speed density setup.
Rom used is 88591715. AEM IAT and Evo X Map sensor Car is up and running, but has a few problems: Every Engine start, it throws a P0462 Code (FUEL LEVEL SENSOR LOW VOLTAGE)
Since our European Evo9 doesnt have these connection for the both Fuel Level sensors ( Sub and Main ), how we can come around that?
Is there an Periphery Bit we can change? If not, should we have to wire them in ( would be a real pita ) with best regards Steffen
Rom used is 88591715. AEM IAT and Evo X Map sensor Car is up and running, but has a few problems: Every Engine start, it throws a P0462 Code (FUEL LEVEL SENSOR LOW VOLTAGE)
Since our European Evo9 doesnt have these connection for the both Fuel Level sensors ( Sub and Main ), how we can come around that?
Is there an Periphery Bit we can change? If not, should we have to wire them in ( would be a real pita ) with best regards Steffen
Last edited by german_evoVII; Jul 22, 2010 at 01:23 AM.
Evolving Member
Joined: Jan 2005
Posts: 184
Likes: 15
From: Wiesbaden, germany
@acamus
Do you really have an 88841717 SD
That would be the perfect match for me.
How can i get the Rom ( and XML ) from you?
I will test it, and post the results.
The car is an 2.3 L Stroker, GT35R-hta, Buschur setup with Cosworth M2´s
I have the Evo X and the Omni 4 Bar available ( wired as the USDM straight to ECU, AEM IAT sensor to IAT @Maf plug
Contact me by E-mail, please
Steffen
Do you really have an 88841717 SD
That would be the perfect match for me.
How can i get the Rom ( and XML ) from you?
I will test it, and post the results.
The car is an 2.3 L Stroker, GT35R-hta, Buschur setup with Cosworth M2´s
I have the Evo X and the Omni 4 Bar available ( wired as the USDM straight to ECU, AEM IAT sensor to IAT @Maf plug
Contact me by E-mail, please
Steffen
