Advanced fuel control options
#166
Planned on pulling the sensor tomorrow and taking a look, I've heard some stories about vibrations causing the leads to break off or loosen on the thermistor.
As for the scaling, how it displays wasn't really what bothered me, it was the physical addresses being different between the table in the rom and the one listed here for 9653 that really got me wondering.
As for the scaling, how it displays wasn't really what bothered me, it was the physical addresses being different between the table in the rom and the one listed here for 9653 that really got me wondering.
#168
Evolved Member
iTrader: (9)
I finally had some ambition to drag myself out to the car again. Here's what I found out...
There's nothing wrong with the IAT sensor. Sensor tested good, looks intact and the resistance changed with heat changes.
I ended up getting a really nasty malware virus on my tuning laptop (thanks photobucket) and I have a feeling that maybe, somehow, in some weird way, that it might have damaged the rom I was working on at the time. I went back to a previous set point that still had my original rom I had on the car, reloaded it today, and mysteriously (with still around the same ambient temps) it ran perfect again. The other scenario involves a modified bov that I was working and testing on, but I really can't see how a bov (especially one with the same spring rate as a stock Evo 9 bov) would have that big of an impact on speed density lol.
Either way, it's back to normal.
There's nothing wrong with the IAT sensor. Sensor tested good, looks intact and the resistance changed with heat changes.
I ended up getting a really nasty malware virus on my tuning laptop (thanks photobucket) and I have a feeling that maybe, somehow, in some weird way, that it might have damaged the rom I was working on at the time. I went back to a previous set point that still had my original rom I had on the car, reloaded it today, and mysteriously (with still around the same ambient temps) it ran perfect again. The other scenario involves a modified bov that I was working and testing on, but I really can't see how a bov (especially one with the same spring rate as a stock Evo 9 bov) would have that big of an impact on speed density lol.
Either way, it's back to normal.
#171
Evolved Member
iTrader: (8)
For 96530006, the addresses to add to the MUT table (from mrfred's second post) appear to be; note that these are two-byte values, so each value is two MUT table entries:
For "Sync Base FPW", we'll need to get the patch portion of mrfred's post ported over first, but I thought it might be helpful to get this into people's hands sooner rather than later.
(It looks like FFFF8A68 or 8A64 should be workable for Sync Base FPW, in case Eric or someone else gets a chance to look at the patch before I do. And on that note, time for lunch. )
Code:
60-61 Sync Base FPW (to be determined) 62-63 Sync Load Accel FPW ffff8a72 & ffff8a73 64-65 Sync Load Decel FPW Subtraction ffff8a74 & ffff8a75 66-67 Sync Load Change Idle FPW (doesn't exist) 68-69 Total Sync FPW ffff8a6a & ffff8a6b 6A-6B Async Accel FPW ffff8b38 & ffff8b39 6C-6D Cranking FPW ffff8afa & ffff8afb 6E-6F Primer Pulse ffff8ba8 & ffff8ba9
(It looks like FFFF8A68 or 8A64 should be workable for Sync Base FPW, in case Eric or someone else gets a chance to look at the patch before I do. And on that note, time for lunch. )
When I log that address, I get something that seems to depend on Delta TPS, but it never goes to zero.
For example, if it was sitting at 3, you blip the throttle and it might jump up to 4, 7 or maybe go down to 2 with the blip. But it isn't like the Sync accel/decel stuff where it's normally at zero and then only when TPS changes does it become active.
#172
Evolving Member
Join Date: Oct 2007
Location: Seattle
Posts: 133
Likes: 0
Received 0 Likes
on
0 Posts
Lean tip in
Suffering from the lean tip in, between 1500 to 2500. I was looking at the global fuel settings-accel enrichment area and found this.
Async Accel vs Rpm Adder table, the areas between 1500 and 2500 are set to 0 on the graph.
Also the Sync Load Accel Compensation vs Rpm table has the values between 1500 to 2500 set to 1.00, which shows 0 on the graph.
My question is, should I be looking at these area's ref the lean tip in?
Async Accel vs Rpm Adder table, the areas between 1500 and 2500 are set to 0 on the graph.
Also the Sync Load Accel Compensation vs Rpm table has the values between 1500 to 2500 set to 1.00, which shows 0 on the graph.
My question is, should I be looking at these area's ref the lean tip in?
#174
Evolving Member
Join Date: Oct 2007
Location: Seattle
Posts: 133
Likes: 0
Received 0 Likes
on
0 Posts
It works!
Suffering from the lean tip in, between 1500 to 2500. I was looking at the global fuel settings-accel enrichment area and found this.
Async Accel vs Rpm Adder table, the areas between 1500 and 2500 are set to 0 on the graph.
Also the Sync Load Accel Compensation vs Rpm table has the values between 1500 to 2500 set to 1.00, which shows 0 on the graph.
My question is, should I be looking at these area's ref the lean tip in?
Async Accel vs Rpm Adder table, the areas between 1500 and 2500 are set to 0 on the graph.
Also the Sync Load Accel Compensation vs Rpm table has the values between 1500 to 2500 set to 1.00, which shows 0 on the graph.
My question is, should I be looking at these area's ref the lean tip in?
#177
Evolving Member
iTrader: (2)
SyncLoadAccel only contributes continually to the fuel pulse width when uncompensated load is below a ceiling value defined by a table described below. When the uncompensated load rises above the value in the table, the SyncLoadAccel contribution is quickly decayed to zero even if load is still increasing. DeltaMasterLoadPos must exceed a threshold value before a SyncLoadAccel contribution is generated. There is a table of threshold values for steady throttle and another table for increasing throttle. The steady throttle threshold values are replaced with a constant when a flag is set. There is also a table that limits the maximum value for DeltaMasterLoadPos.
If I understood this right, for 94170715 V7 rom (Same as 96530706 V7 rom)
"Ceiling load vs. rpm for sync load accel/decel contributions" sets the ceiling load 126~134 near 2500~3500rpm, Accelenrichment is not adding more fuel loads over 140 even the load keeps increasing @ WOT? (Assuming Async accelenrichment is temporary only during TPS increase)
This might be related to why my log (attached) shows much more deviation from AFRMAP to Wideband AFR at green-marked zone than yellow-marked zone?
Or is this just from MAF reading has more error at specific rpm and load range?
I have stock air box and stock turbo inlet. (DP + LICP + intercooler upgraded recently)
Last edited by ace33joe; Apr 8, 2010 at 07:11 PM.
#178
Evolved Member
iTrader: (2)
I went through 9653 a while back to find these tables. Let me see what I have.
Here is what I have...you will have to test out to be sure they are right as I found them way back when mrfred posted for his ROM:
Here is what I have...you will have to test out to be sure they are right as I found them way back when mrfred posted for his ROM:
Code:
<table name="Sync Load Accel DeltaMasterLoadPos Ceiling Value" category="Fuel" address="163a" type="1D" level="1" scaling="LoadMaster16"/> <table name="Ceiling Load vs RPM for Sync Load Accel/Decel Contributions" category="Fuel" address="391e" type="2D" level="1" scaling="x54d16"> <table name="RPM" address="6576" type="Y Axis" elements="10" scaling="RPM"/> </table> <table name="Min Uncomp Load Change at Steady Throttle for SyndLoadAccel/Decel Contribution" category="Fuel" address="3888" type="2D" level="1" scaling="LoadUncompDelta"> <table name="Uncompensated Load" type="Static Y Axis" elements="13"> <data>0</data> <data>24</data> <data>48</data> <data>72</data> <data>95</data> <data>119</data> <data>143</data> <data>167</data> <data>191</data> <data>215</data> <data>238</data> <data>262</data> <data>286</data> </table> </table> <table name="Min Uncomp Load Change at Changing Throttle for SyncLoadAccel/Decel Contribution" category="Fuel" address="3895" type="2D" level="1" scaling="LoadUncompDelta"> <table name="Uncompensated Load" type="Static Y Axis" elements="13"> <data>0</data> <data>24</data> <data>48</data> <data>72</data> <data>95</data> <data>119</data> <data>143</data> <data>167</data> <data>191</data> <data>215</data> <data>238</data> <data>262</data> <data>286</data> </table> </table>
Last edited by l2r99gst; Apr 13, 2010 at 07:10 AM.
#179
Evolved Member
iTrader: (2)
Eric, your definitions look right to me. There's actually a few more missing from my post as well, so I just went through and updated it, doing a side-by-side comparison with mrfred's post (and adding comments as section separators, so it should be easier to see if anything has been missed in the future).
If anyone sees anything else missing (that wasn't addressed in the post right before it; some of this code doesn't exist in 9653), let me know and I'll update my post.
If anyone sees anything else missing (that wasn't addressed in the post right before it; some of this code doesn't exist in 9653), let me know and I'll update my post.