UpPweez wrote:
I downloaded and implemented this def file and opened up a stock '05 STI A2ZJB10J file. Some comments / questions ...
1) Boost and Wastegate values look great.
2) Injector flow scaling is set to 456cc. Why did you take this manner of scaling as opposed to using the actual scalar (like Cobb)?
3) Tip-In enrichment values are different than the Tip-Ins listed in StreetTUNER. FWIW, StreetTUNER has the same values for '04, '05, and '06 STI and they are about 25% of what you have listed.
4) I take it the Injector Pulse Width table is in debug mode and not usable? Should this be renamed to Injector Latency? 'Latency' makes more sense given what this table does.
5) Timing, MAF, and Speed Limiting look good.
6) CL modified Load is different than StreetTUNER (I think the values in the def are 100x what Cobb has listed ... i.e. 5900 = 5.9
7) Closed loop delay is in Debug mode?
TDC table looks good.
- Any idea when the debug mode tables will be usable?
- Can you describe in more detail what ENGINUITY does when the CheckSum fix is enabled? I take it that this always has be checked off?
1. Injector flow - Just thought is would be easier for someone with new injectors to visualize what they need to change, rather than the Cobb value.
2. Tip-in enrichment - Cobb probably uses the straight value off of the ECU. With the 32-bit ECUs, the 8-bit/16-bit values have multipliers stored to tell you the conversion formula and what Subaru intended with this value. In this case, the multiplier was 4.
3. Injector pulse width - To use debug mode tables, switch your user level to debug mode and you can access all of the red debug tables. The reason this is in debug mode is that the ECU calls for floating point values in this case, but the numbers weren't even close and could never be converted to anything resembling latency that I could tell. I switched to 16-bit as an experiment and apply a simple formula, the values came out exactly what I would expect. Since this is different that what the ECU calls for, use caution with this table. You're right it probably should be renamed. I'll do that for the next release.
4. CL MODIFIED LOAD - Again, this uses the multiplier supplied by Subaru, which is also 4. I didn't want any values resembling the 16-bit conversion formula, with reads in the single digits, because these are obviously in different units between the 16-bit and 32-bit versions. Cobb uses the straight value for the 16-bit ECUs. So, I not sure what they are doing with the 32-bit, other than maybe lowering the number to avoid confusion.
5. I'm not sure about the accuracy of the Closed Loop delay. Being a 1D table, it is more difficult to ascertain the length and it seems in the 32-bit ECUs that it may vary between the STi and the other models. The STi should be zero anyway, so this is not an issue with these cars. I'm working on figuring out what is going on.
Debug tables are fully usuable as long as you are in debug mode. With the cheksum fix, when you click on enabled, you are adding the fix to your ECU. When uncheck it, it goes back to the stock values. So, yes, you should always have this enabled.
