Since there's really no manual for ECUFlash, I've decided that we should make our own on here, section at a time.

I'd like to start with the Turbo related maps under ECUflash. This thread can be used for a discussion, and once we iron out the details, I'll start a new thread with the final info that we come up with and lock that thread as to preserve it for reference only. This thread will remain open in case we need to discuss updates and such.

Please use the format below for each map:

Map Name:
Map Dimensions:
Map Axes:
Map Units:
Min/Max values of Units:
Map Description:
Reasons to modify this map:
Tuning Tips:
Warnings & Considerations:

I'll start - if you can add or improve on what I'm writing, please quote me and reword/correct it in your post.

Map Name: Boost Control Load Offset (aka BCLO)
Map Dimensions: 1x1
Map Axes: N/A
Map Units: Load
Min/Max values of Units:
Map Description: This value is added to your Boost Target Engine Load to determine your Target Load.
Reasons to modify this map: Modify this map to change your target loads.
Tuning Tips: Larger values will increase your target load, lower values will reduce it. With a stock boost solenoid setup, modify this value in increments of 10 or so. For a 3 port solenoid setup, modify it by increments of about 5.
Warnings & Considerations: Since modifying this value changes your load calculation (on which everything is based), it may result in you hitting different load points in other maps. These load cells may contain values that are dangerous or not optimal. Proceed with caution.

Map Name: Boost Target Engine Load #2 (Low Gear Range)
Map Dimensions: 9x18
Map Axes: TPS vs RPM
Map Units: Load
Min/Max values of Units: 0 / 255 minus your BCLO value .
Map Description: The contents of this map are added by the BCLO to determine target load while boosting. This map controls your Low Gear Range, which is defined as any speed lower than your Boost Control RPM Per MPH Xover (Gear Based).
Reasons to modify this map: This would allow you to change the boost characteristics of a car.
Tuning Tips: In the high (70+) throttle positions and high RPM, consider using high values that you know cannot be attained if you'd like to allow the turbo to hold as much boost as possible.
Warnings & Considerations: Setting numbers that are too high can cause overboost.

Map Name: Boost Target Engine Load #1A (High Gear Range)
Map Dimensions: 9x18
Map Axes: TPS vs RPM
Map Units: Load
Min/Max values of Units: 0 / 255 minus your BCLO value .
Map Description: The contents of this map are added by the BCLO to determine target load while boosting. This map controls your High Gear Range, which is defined as any speed equal to or greater than than your Boost Control RPM Per MPH Xover (Gear Based) at or near sea level.
Reasons to modify this map: This would allow you to change the boost characteristics of a car.
Tuning Tips: In the high (70+) throttle positions and high RPM, consider using high values that you know cannot be attained if you'd like to allow the turbo to hold as much boost as possible.
Warnings & Considerations: Setting numbers that are too high can cause overboost.

Map Name: Boost Target Engine Load #1B (High Gear Range)
Map Dimensions: 9x18
Map Axes: TPS vs RPM
Map Units: Load
Min/Max values of Units: 0 / 255 minus your BCLO value .
Map Description: The contents of this map are added by the BCLO to determine target load while boosting. This map controls your High Gear Range, which is defined as any speed equal to or greater than than your Boost Control RPM Per MPH Xover (Gear Based) significantly above sea level.
Reasons to modify this map: This would allow you to change the boost characteristics of a car.
Tuning Tips: In the high (70+) throttle positions and high RPM, consider using high values that you know cannot be attained if you'd like to allow the turbo to hold as much boost as possible.
Warnings & Considerations: Setting numbers that are too high can cause overboost.

Map Name: Boost Control RPM Per MPH Xover (Gear Based)
Map Dimensions: 1x1
Map Axes: N/A
Map Units: N/A
Min/Max values of Units: 0/255?
Map Description: This is the speed, in mph, at which the Boost Target Engine Load, Reactive Solenoid Base WGDC, Reactive Solenoid WGDC Correction Interval, and Passive Solenoid Base WGDC maps switch from the Low Gear Range map to High Gear Range map. High Gear Range 1A is used @ sea level and 1B is used at high altitude.
Reasons to modify this map: If you'd like to run different amounts of boost at different speeds or gears, this is where you'd define the cut off point.
Tuning Tips: For most people, setting this somewhere between 70 and 90 mph is best so that you can set your car up to run slightly less boost in 4th and 5th gear for safety.
Warnings & Considerations: None

Map Name: Reactive Solenoid Base WGDC Map - (Low Gear Range), #1A (High Gear Range), #1B (High Gear Range)
Map Dimensions: 9x18
Map Axes: TPS vs RPM
Map Units: Duty Cycle
Min/Max values of Units: 0/100
Map Description: Controls the fine boost solenoid to change boost properties.
Reasons to modify this map: Fine Tuning of boost.
Tuning Tips: A duty cycle of 100 fully closes the solenoid (resulting in maximum boost), whereas the duty cycle of 0 full opens the solenoid and results in the minimum amount of boost the system will allow.
Warnings & Considerations:

Map Name: Reactive Solenoid WGDC Correction Interval - (Low Gear Range), (High Gear Range)
Map Dimensions: 1x1
Map Axes: N/A
Map Units: Tenths of a second.
Min/Max values of Units:
Map Description: Frequency at which the ECU tests for boost correction.
Reasons to modify this map: Allows more precision over boost correction.
Tuning Tips: Lowering this value will result in a faster response time to any necessary boost corrections. Running too low of a time may make boost jittery.
Warnings & Considerations: A high value (of over 1) may result in very poor boost correction.

Map Name: Reactive Solenoid Turbo Boost Error Correction
Map Dimensions: 1x17
Map Axes: Load Error
Map Units: Correction Percentage
Min/Max values of Units: 0/?
Map Description: The Load Error is the difference between your actual load and your Target Load. For example, a Load Error of -20 would mean that you're 20 below the Target Load. A Load Error of 20 would mean that you're 20 above your Target Load. A Load Error of 0 means that you are at your Target Load. The Correction Percentage is applied to your Solenoid maps in order to match your Target Load.
Reasons to modify this map: If you are overboosting, underboosting, etc.
Tuning Tips: If you are overboosting, make your Correction Percentage MORE negative in the Positive Load Errors. If you are underboosting, make your Correction Percentage MORE positive in the Negative Load Errors.
Warnings & Considerations: If you make abrupt changes, it can have undesired effects.

Map Name: Reactive Solenoid Max Total Upward WGDC Correction vs TPS
Map Dimensions: 1x9
Map Axes: TPS
Map Units: Percentage of Wastegate Duty Cycle Change of Boost Solenoids
Min/Max values of Units: ?
Map Description: Works like Reactive Solenoid Turbo Boost Error Correction, except it's throttle position based rather than load based.
Reasons to modify this map: If you are underboosting.
Tuning Tips:
Warnings & Considerations:

Map Name: Reactive Solenoid Max Total Downward WGDC Correction
Map Dimensions: 1x1
Map Axes: N/A
Map Units: Percent Waste Gate Duty Cycle Change.
Min/Max values of Units: 0/100
Map Description:
Reasons to modify this map:
Tuning Tips:
Warnings & Considerations:

Map Name: Passive Solenoid Base WGDC Map - (Low Gear Range), #1A (High Gear Range), #1B (High Gear Range)
Map Dimensions: 1x18
Map Axes: RPM
Map Units: Duty Cycle
Min/Max values of Units: 0/100
Map Description: Controls the coarse boost solenoid to change boost properties.
Reasons to modify this map: Coarse Tuning of boost.
Tuning Tips: A duty cycle of 100 fully closes the solenoid (resulting in maximum boost), whereas the duty cycle of 0 full opens the solenoid and results in the minimum amount of boost the system will allow.
Warnings & Considerations:

Map Name: Boost Limit
Map Dimensions: 1x9
Map Axes: RPM
Map Units: Load
Min/Max values of Units:
Map Description: These are the maximum Load values allowed at the given RPMs. If your Actual Load exceeds the Load values defined here for a time greater than or equal to the Boost Cut Delay Timer, a hard boost cut will occur (the car will buck).
Reasons to modify this map: If you want to run more load.
Tuning Tips: Keep the values listed in this map as low as you can without exceeding them under normal conditions.
Warnings & Considerations: Entering values that are too high essentially bypasses this safety mechanism. Use with caution.

Map Name: Boost Cut Delay Timer
Map Dimensions: 1x1
Map Axes: N/A
Map Units: Time in milliseconds
Min/Max values of Units: 0/?
Map Description: If Actual Load exceeds the Boost Limit for more than the time specified here, a hard boost cut will occur (the car will buck).
Reasons to modify this map: Allowing a boost spike in certain situations.
Tuning Tips: Increase this value little at a time if you want to allow some mild boost spikes.
Warnings & Considerations: Entering a value that istoo high essentially bypasses this safety mechanism. Use with caution.

*reserved2*

Ftw!

;)

UPWARD WGDC correction vs TPS

This is the amount the error correction system will add WGDC *above* the base WGDC table. Stock it's 10 at higher TPS %.

If you zero this table out it will *never* add WGDC above the base WGDC, but if the WGDC is under the base WGDC (from error correction pulling it down), the Ecu will add WGDC up until it meets base WGDC. (if you have additive correction in the error correction table)

- Bryan

UPWARD WGDC correction vs TPS

This is the amount the error correction system will add WGDC *above* the base WGDC table.

Sounds good. So in other words, if you're underboosting, this will increase your WGDC to help you hit your boost targets, yes?

Stock it's 10 at higher TPS %.

Explain?

If you zero this table out it will *never* add WGDC above the base WGDC, but if the WGDC is under the base WGDC (from error correction pulling it down), the Ecu will add WGDC up until it meets base WGDC. (if you have additive correction in the error correction table)

- Bryan

Ok, so which map are you considering the BASE WGDC? The Passive Solenoid Base WGDC?

Ftw!

;)

Couldn't have done it without ya!

:bump:

nice write up dino !

Subscribed. Trying to learn how to tune myself and this will help. Any other posts you can link me to?

subscribed - i love this forum!

:-)

Does anyone have anything they'd like to correct on this before I solidify it into a PDF?

nice!

First version of the manual is up. It only contains the turbo stuff so far.

PS - does anyone have more info on the "Reactive Solenoid Max Total Downward WGDC Correction" map?

http://www.evoxforums.com/forums/showthread.php?t=31134

First version of the manual is up. It only contains the turbo stuff so far.

PS - does anyone have more info on the "Reactive Solenoid Max Total Downward WGDC Correction" map?

http://www.evoxforums.com/forums/showthread.php?t=31134

What info do you need?

Very useful guide.
I really wait for the other sections... ;)

Don't wait for things to happen, do something about it!
jk
lol

wayne

Has anyone put together a list of expected values for Data Logging to help n00bs like myself interpert results until I gain more experience? I'm just starting to read up on everything I can so I can start playing around.

I would find something like this extremely useful. Based on the knowledge base on this forum I'm sure this could be put together rather quickly and would be a big help for a majority of the inexperienced users. Something on the 10 most import data logging elements would be a good place to start. From what i've read so far it looks like something that may be useful to start with would be:

Air/Fuel Ratio
Mass Air Flow
Boost Pressure
Knock Retard
Learned Knock
Waste Gate Duty Cycle
Long Term Fuel Trim
Short Term Fuel Trim
Ignition Advance
Upper Ignition Timing
Lower Ignition Timing

For Example (I made up the values since I have no clue what the vals should be)

(Data Logging Column Headings) - (My Sample/Example Data)

Datalog Parameter - Knock Retard
Common Acronym - KNKRTD (Not sure if it applies to all but like AFR,MAF)
Parameter Type - Expressed as a % (Other possible Values would be PSI, Volts, RPM, Load, etc...)
Parameter Type Description - Determined by val1/val2 * val3 (or whatever - for PSI it would just say "Pounds per Square Inch")
Range of Values - 0.0 to 7.0
Normal (Safe) Range - 0.0 - 3.0
Unusual Range - 3.0 - 4.0
Extremely High (Unsafe Range) - 4.0 and Higher
Common Associated CEL Codes - P######, P######
Description of parameter (Borrowed from Travis@Cobb post) - The processes that manage optimal ignition timing at light load are complex and vary by vehicle type. Some ignition timing adjustments are active and based upon sensor feedback. One such sensor is the "knock sensor." This sensor is a simple microphone that listens for engine noise. Complex signal processing inside the ECU helps discriminate detonation from other types of engine noise. The thresholds for noise vs knock vary not only by engine speed but by engine load. The ECU will react to engine noise by actively removing ignition timing. This low-load "knock correction" is a normal and desirable process that promotes optimal ignition timing.

Is there any interest in putting this together?