ECU ROM mod - double the "Fuel Cut Load Limit" range to 638
#18
Evolving Member
Join Date: Jun 2007
Location: NorCal
Posts: 154
Likes: 0
Received 0 Likes
on
0 Posts
#20
Evolved Member
iTrader: (39)
mrfred am I correct in my assumption?
~Zach
#23
Evolved Member
iTrader: (48)
It doesn't really matter what MAP sensor you're running; when you convert to SD you dictate what you want your load to be for a give pressure. For me; I'm running a 1:1 value over 100Kpa. I'm pretty sure I remember reading that once you go SD it removes the load limits associated w/ the MAF based setups. I used to have the load limit/IPW limit removed on the MAF setup w/ a patch from JCS that I had to set back to stock values once going SD.
And yes, it was a question in the form of a clarifying statement hence the question mark
And yes, it was a question in the form of a clarifying statement hence the question mark
#24
Evolved Member
iTrader: (39)
It doesn't really matter what MAP sensor you're running; when you convert to SD you dictate what you want your load to be for a give pressure. For me; I'm running a 1:1 value over 100Kpa. I'm pretty sure I remember reading that once you go SD it removes the load limits associated w/ the MAF based setups. I used to have the load limit/IPW limit removed on the MAF setup w/ a patch from JCS that I had to set back to stock values once going SD.
And yes, it was a question in the form of a clarifying statement hence the question mark
And yes, it was a question in the form of a clarifying statement hence the question mark
#25
Evolved Member
iTrader: (48)
#26
It doesn't really matter what MAP sensor you're running; when you convert to SD you dictate what you want your load to be for a give pressure. For me; I'm running a 1:1 value over 100Kpa. I'm pretty sure I remember reading that once you go SD it removes the load limits associated w/ the MAF based setups. I used to have the load limit/IPW limit removed on the MAF setup w/ a patch from JCS that I had to set back to stock values once going SD.
And yes, it was a question in the form of a clarifying statement hence the question mark
And yes, it was a question in the form of a clarifying statement hence the question mark
1) A properly tuned SD setup will show exactly the same load values as the original MAF setup. That is the goal of the tuning process after converting to SD. This is true regardless of the MAP sensor that is used (e.g., 3-bar, 4-bar, 5-bar, etc).
2) The MAF algorithm includes code to *clip* the load value. If the load calculated from the MAF exceeds the clip value, then the algorithm will use the clip value. That code has nothing to do with the load limit tables I have posted here.
3) The load limit tables I have posted here will cause fuel cut to occur when the load, calculated either from MAF or SD, exceeds the value in the table (and the delay time has passed).
#28
Evolved Member
iTrader: (17)
I think what they were trying to say was that when going to SD, you can fudge the settings so the maximum load you hit can stay under the 319 load limit. I know the old school MAFT guys did this so they had maximum resolution with the factory ECU scaling since it wasn't able to be edited by the averge user like we can so they were forced to make their peak load stay within the factory map scaling.
I agree that its best to match the MAF scaling since we don't REALLY need to fudge the max load values reached with SD. Unless of course you're running insane loads and the amount of load scaling steps we have available (its around 20 load points right?) doesn't offer enough resolution, then it would make sense.
I agree that its best to match the MAF scaling since we don't REALLY need to fudge the max load values reached with SD. Unless of course you're running insane loads and the amount of load scaling steps we have available (its around 20 load points right?) doesn't offer enough resolution, then it would make sense.
#29
I think what they were trying to say was that when going to SD, you can fudge the settings so the maximum load you hit can stay under the 319 load limit. I know the old school MAFT guys did this so they had maximum resolution with the factory ECU scaling since it wasn't able to be edited by the averge user like we can so they were forced to make their peak load stay within the factory map scaling.
I agree that its best to match the MAF scaling since we don't REALLY need to fudge the max load values reached with SD. Unless of course you're running insane loads and the amount of load scaling steps we have available (its around 20 load points right?) doesn't offer enough resolution, then it would make sense.
I agree that its best to match the MAF scaling since we don't REALLY need to fudge the max load values reached with SD. Unless of course you're running insane loads and the amount of load scaling steps we have available (its around 20 load points right?) doesn't offer enough resolution, then it would make sense.