AFC---->Uberdata (all in theory)
12-14-2003, 10:15 AM
#1
0.0 BAR
Thread Starter
Join Date: Sep 2003
Posts: 0
AFC---->Uberdata (all in theory)
Okay, i read this on pgmfi.org and i figured i would do a walk through and someone could test it out....in theory it should be a good start for a basemap.
Okay we will use this as our example.
First open uberdata and open the bin that goes with your ECU. In this case I will be using a stock bin for a P28 ECU.
Bascially the idea behind this is to use the precentages from your AFC and just use them in Uberdata. First, go to the boost tab and set your fuel efficency at 120...your timing you can set at whatever you like. 1.0 is always a safe setting. Next, select the values in the fuel lo table below 1000rpm and multiply it by 100-35=65% Do the same for the rest of the vaules. and then go into the Fuel HI and do the same as you did for the Low Fuel. if you dont have V-tec Skip this step.
This should be a good basemap to start.
NOTE: This hasnt been tested its all theoretical, if someone would test it then we would know if this would basically work but in theory the numbers seem damn close to what i would plug in for uberdata...although these numbers seem a little lean..so you might want to add like 2-5 onto the AFC percentage (35+5 in this case)...but its really your choice.
Originally Posted by Johnyquest
Stock D16Z6, '95 Civic Ex Coupe
Volvo t3, ~10psi, stock timing, DSM450's, black-top
NE POINTS: 1k,2,3,4,5,6,7,8
LO/HI Cross: 70% / 71%
Settings:
.....LO: ..... HI:
1k: -34 ..... -36
2k: -36 ..... -36
3k: -36 ..... -36
4k: -36 ..... -36
5k: -36 ..... -36
6k: -36 ..... -36
7k: -36 ..... -36
8k: -36 ..... -36
-34 at idle holds it perfect, and -36 is the lowest i can go without a 'bog' if i floor it real quick. It is rich as can be, but better rich than sorry!
Runs awesome, pretty sick power.
Volvo t3, ~10psi, stock timing, DSM450's, black-top
NE POINTS: 1k,2,3,4,5,6,7,8
LO/HI Cross: 70% / 71%
Settings:
.....LO: ..... HI:
1k: -34 ..... -36
2k: -36 ..... -36
3k: -36 ..... -36
4k: -36 ..... -36
5k: -36 ..... -36
6k: -36 ..... -36
7k: -36 ..... -36
8k: -36 ..... -36
-34 at idle holds it perfect, and -36 is the lowest i can go without a 'bog' if i floor it real quick. It is rich as can be, but better rich than sorry!
Runs awesome, pretty sick power.
First open uberdata and open the bin that goes with your ECU. In this case I will be using a stock bin for a P28 ECU.
Bascially the idea behind this is to use the precentages from your AFC and just use them in Uberdata. First, go to the boost tab and set your fuel efficency at 120...your timing you can set at whatever you like. 1.0 is always a safe setting. Next, select the values in the fuel lo table below 1000rpm and multiply it by 100-35=65% Do the same for the rest of the vaules. and then go into the Fuel HI and do the same as you did for the Low Fuel. if you dont have V-tec Skip this step.
This should be a good basemap to start.
NOTE: This hasnt been tested its all theoretical, if someone would test it then we would know if this would basically work but in theory the numbers seem damn close to what i would plug in for uberdata...although these numbers seem a little lean..so you might want to add like 2-5 onto the AFC percentage (35+5 in this case)...but its really your choice.
12-14-2003, 11:16 AM
#4
0.0 BAR
Thread Starter
Join Date: Sep 2003
Posts: 0
Re:AFC---->Uberdata (all in theory)
Originally Posted by TurboEF9
... 
12-15-2003, 11:02 AM
#6
3.0 BAR
Join Date: Apr 2003
Posts: 2,260
Re:AFC---->Uberdata (all in theory)
Depending on how much boost you're planning on running, you'll throw code 10 with those settings.
Using the "AFC hack" as an engine management tool to control boost, while functional, is not really a method of "tuning". Anything at 9psi or above, I would strongly recommended boost modified ECUs. This way, your static timing can remain stock, while still being able to manipulate your ignition able and apply adequate fuel without ruining your MAP sensor input... anyway, this is just how I feel. Not to mention, I have derived this knowledge from personally running the "AFC hack" for 6 months before running boost modified chips.
Using the "AFC hack" as an engine management tool to control boost, while functional, is not really a method of "tuning". Anything at 9psi or above, I would strongly recommended boost modified ECUs. This way, your static timing can remain stock, while still being able to manipulate your ignition able and apply adequate fuel without ruining your MAP sensor input... anyway, this is just how I feel. Not to mention, I have derived this knowledge from personally running the "AFC hack" for 6 months before running boost modified chips.
12-15-2003, 05:13 PM
#7
0.0 BAR
Thread Starter
Join Date: Sep 2003
Posts: 0
Re:AFC---->Uberdata (all in theory)
I'm confused by your post. In uberdata you generally open the stock map and edit it. There are no "boost maps". by changing the fuel efficiency, changing the timing, and scaling for the different sized injectors, that is converting a once stock map to a boosted basemap.
Going by just the FAQ, fuel efficiency=120, timing=1.0(less boost less timing taken away obviously), and for injector scaling it is 240/(injector size)x100+5...in the case of a 450cc injector you get 58.333....so if your afc settings are -38...100-38=62...62 is damn close to 58.33...i would probably round down to 60 just to be on the safe side though. I really dont understand what is wrong about doing this for a basemap.
Going by just the FAQ, fuel efficiency=120, timing=1.0(less boost less timing taken away obviously), and for injector scaling it is 240/(injector size)x100+5...in the case of a 450cc injector you get 58.333....so if your afc settings are -38...100-38=62...62 is damn close to 58.33...i would probably round down to 60 just to be on the safe side though. I really dont understand what is wrong about doing this for a basemap.
12-15-2003, 05:37 PM
#8
3.0 BAR
Join Date: Apr 2003
Posts: 2,260
Re:AFC---->Uberdata (all in theory)
If that is true, then Blake is scaling MAP sensor input internally which results in loss of resolution of the overall fuel and ignition maps, which we all know is not desirable.
However, I think you are mistaken, as I know Blake would not code that way. From what I see, there are boosted tables. Those sections on the right hand side, that when a stock map is loaded, have null values in them, those are the boost tables. These should be in use on a boosted application.
What you're talking about is simply scaling for larger injectors. The hole in your logic is you're not compensating (or forgetting to explain) MAP input signal when running a "stock" MAP.
However, I think you are mistaken, as I know Blake would not code that way. From what I see, there are boosted tables. Those sections on the right hand side, that when a stock map is loaded, have null values in them, those are the boost tables. These should be in use on a boosted application.
What you're talking about is simply scaling for larger injectors. The hole in your logic is you're not compensating (or forgetting to explain) MAP input signal when running a "stock" MAP.
