Tuning Wiki

This is a historical revision. Read the current page or return to its history.

Page organisation in this revision
Page type
Technical article
Subject
Tuning
Parent
Section level
Applies to
No ECU-specific applicability
Tool groups
None
Manufacturers
None

Changes from revision 7 to revision 9

Removed text is struck through; added text is highlighted.

When an engine is modified, its control strategy must suit the hardware and the vehicle around it. The usual choices are to recalibrate the factory controller, add another controller alongside it, or install an aftermarket ECU. These labels describe different architectures, not guarantees about the features, performance or legality of a particular installation.

Recalibrating the factory ECU

A supported reflash changes data in the original controller. It can retain factory integration, diagnostics and control functions when they remain supported by the particular calibration. The available tables and access methods depend on the ECU, software version and tool; a tuning device cannot automatically make an unsupported sensor, injector or actuator compatible. How an ECU is remapped explains the read, edit and write process.

A supplied forced-induction kit calibration is matched to a stated vehicle and hardware configuration. Confirm the exact application, fuel requirement, included parts and restrictions before installation; later changes to the intake, exhaust, injectors or engine may require a different calibration and validation. For example, Edelbrock's supercharger FAQ limits the supplied calibration of certain systems to specified stock configurations. That restriction is product-specific, as are any emissions approvals.

For a concrete fitment contrast, Edelbrock lists its 15630 kit for specified 2010–15 Camaro SS LS3 manual-transmission applications without a supplied handheld programmer, while its 1597 kit is listed for specified 2010–13 Camaro SS L99 automatic applications with a tune intended for the stated stock configuration. Both product descriptions include charge cooling. These are distinct packages; check the current instructions, emissions approval and exact vehicle before ordering or applying a calibration. A listing for one does not establish fit or safe settings for another.

Auxiliary and parallel controllers

An auxiliary device works with the factory ECU rather than replacing every function. Depending on its design, it may observe signals, modify selected signals or take over particular outputs. A parallel ECU may control fuel and ignition while the factory controller retains other duties; Haltech documents such an arrangement for a specific Holden/Buick V6 installation. The exact functions are product- and vehicle-specific. Haltech: Holden/Buick V6 example

Changing a signal seen by the factory ECU can also change its other calculations or trigger plausibility checks. Verify the complete effect using the relevant documentation and measured results; do not assume only the intended output changes. Some patch-harness controllers have a manufacturer-specific pass-through function. For example, Haltech states that the corrections in its documented copy-through mode are ignored; that detail must not be generalised to other products. Haltech: copy-through feature

What the auxiliary device changes

ApproachExample and checks Alter a sensor signalA programmable unit may report a modified MAP or MAF signal to the ECU. The same input may affect several calculations, so check fuel, ignition, boost and diagnostics where applicable. Split Second PSC1-001 documentation describes one such device. Modify an actuator commandSome fuel controllers alter the injector pulse after the ECU calculates it. Dobeck describes an early product that added pulse width; other designs can behave differently. Confirm the injector and driver type, the control range and how factory feedback reacts. Dobeck product history. Control an additional actuatorAn auxiliary controller can drive an additional injector if designed and configured for it. Its fuel supply, electrical load and failure response must be considered as part of the system. Split Second documents additional-injector and signal-calibrator versions of its FTC1; the connection and setup depend on the exact version. FTC1 documentation.

These are different functions, and a product may combine them. A programmer that writes a calibration and is then disconnected is also a different arrangement from a controller that stays in the signal path. Establish which signals are altered, what happens on loss of power or a sensor fault, and whether a documented pass-through exists. Validate operation and fault response for the actual installation; do not assume any device leaves factory safeguards or diagnostics unchanged.

Signal range and device modesMatch the sensor's output type and range, the auxiliary device's input and output capabilities, and the factory ECU's expected signal and diagnostic limits. A voltage-based device is not automatically compatible with a frequency, digital or SENT sensor, and an output within the electrical range can still represent an implausible or incorrect load to the ECU.For example, Split Second's PSC1-001 documentation describes a direct-output mode with a programmable 0–5 V output as well as signal-modification arrangements. That range and those modes belong to this model, not every signal calibrator or ECU. Its FTC1 family datasheet describes different versions for MAP, MAF and additional-injector functions; check the precise part and configuration. The physical pressure or airflow, the device input and output, and the ECU's interpreted load are different observations. Verify them with suitable independent measurement and logging over the operating range, including diagnostics and fault responses.

Feedback and unintended effects

When an auxiliary device changes a load signal to influence fuelling, the factory ECU may also use that signal in ignition, boost, torque or diagnostic calculations. If a changed reading selects a different ignition operating point, the resulting timing must be checked as well as the measured mixture. A corrected air–fuel reading alone does not validate the complete calibration.

Where closed-loop mixture control is active, feedback can respond to an imposed fuelling change and learned corrections may persist into later operation. Record the control mode and available short- and long-term corrections alongside the measured result; behaviour and learning ranges depend on the particular ECU. See adaptations and calibration drift.

Knock feedback is another independent interaction: actual knock and unrelated mechanical noise can both influence what a detection system reports. Some systems use both immediate and learned ignition corrections, as described for Haltech knock control. Investigate the signal, installation and combustion conditions using the relevant manufacturer's procedures; a quieter or absent indication does not prove knock has stopped. Preserve effective engine protection and confirm the cause before changing a sensor or its mounting.

Diesel pressure signals also need system-specific interpretation. On the 6.0-litre Power Stroke described in Ford’s 2003 OBD summary, injection control pressure refers to the high-pressure oil that actuates the injectors, not a common-rail fuel-pressure sensor. As a separate example, Edge’s Ford Juice installation guide shows an ICP connection for its specified 1999–2003 7.3-litre application and different connections for its 6.0-litre application. A connection list alone does not establish how the module processes each signal. Identify the exact product, engine and wiring, and verify measured versus requested pressure and diagnostic behaviour using the applicable procedures. A modified or intercepted signal may not represent an independent measurement of the physical pressure. See HEUI fuel systems.

Aftermarket standalone ECU

A standalone controller can take responsibility for the engine functions its hardware and software support. A plug-in or patch-harness installation may simplify connections on a documented application; a universal ECU requires appropriate wiring and configuration. Either still needs correct sensor calibration, trigger settings, injector and ignition compatibility, and a suitable engine calibration. Factory instruments, immobiliser, transmission, air conditioning and CAN communications may require separate support or retained modules. Check the specific product and vehicle rather than assuming that every original function remains available. Standalone ECU fuel tuning guide.

Standalone selection checklist

Before choosing a controller, list the engine's requirements and assign each signal to a compatible input or output. Count functions needed at the same time, including future expansion; a configurable channel already assigned to an injector is not also available for a fan or boost valve.

Engine and synchronisation: confirm engine type, cylinder count, supported crank and cam patterns and required injection and ignition modes. Full sequential operation requires suitable cycle synchronisation; Haltech's fuel configuration documentation gives one implementation. Outputs and loads: check the number and electrical ratings of injector and ignition outputs, coil igniters, staged injectors, idle control, boost, fans and relays. Direct-injection drivers and electronic throttles may need specific support or hardware. Output current and wiring limits are model-specific; see this MoTeC M142 datasheet for an example. Inputs and vehicle integration: confirm sensor ranges and types, trigger conditioning, wideband controller, fault inputs, transmission, instruments, immobiliser and communications. A sensor that physically plugs in still needs compatible electrical characteristics and calibration. Installation and support: check supply voltage, current, mounting environment, enclosure and connector clearance; include the harness, sensors, external drivers, software access, logging, calibration and professional support in the total cost. Follow the actual product's mounting and wiring instructions. Calibration and logging: a matching connector or base map can shorten setup but does not verify fuel, ignition, protection or road behaviour. Check logging channels, rates and storage, then validate the installation and its fault responses with suitable equipment.

Electrical integration and validation

Map which controller supplies each sensor and drives each actuator. Do not connect two outputs together without a documented compatible arrangement.Shared sensors need particular care: an additional input can alter a circuit. Haltech notes that a shared temperature sensor may already have a pull-up in the factory ECU, so its additional controller's pull-up must be disabled for the installation it describes. Other devices must be checked against their own wiring instructions. Haltech: temperature-sensor diagnosisVerify fuel pressure, injector operation, sensor readings and commanded versus measured lambda under controlled conditions. Check cold start, idle, transients, faults and interactions with other vehicle modules, not just peak power.Document the installed hardware, original calibration and wiring, and the approved recovery method before changes. Retain engine and vehicle protection functions appropriate to the application.

Emissions and road-use requirements depend on the vehicle, modification and jurisdiction; confirm the applicable requirements before choosing an installation.

For a complete conversion, see planning and integrating an EFI engine swap.

Rendered revisions

Open each version to inspect formatting, tables and photographs.

Revision 7: Choosing factory remapping, auxiliary control or a standalone ECU

When an engine is modified, its control strategy must suit the hardware and the vehicle around it. The usual choices are to recalibrate the factory controller, add another controller alongside it, or install an aftermarket ECU. These labels describe different architectures, not guarantees about the features, performance or legality of a particular installation.

Recalibrating the factory ECU

A supported reflash changes data in the original controller. It can retain factory integration, diagnostics and control functions when they remain supported by the particular calibration. The available tables and access methods depend on the ECU, software version and tool; a tuning device cannot automatically make an unsupported sensor, injector or actuator compatible. How an ECU is remapped explains the read, edit and write process.

A supplied forced-induction kit calibration is matched to a stated vehicle and hardware configuration. Confirm the exact application, fuel requirement, included parts and restrictions before installation; later changes to the intake, exhaust, injectors or engine may require a different calibration and validation. For example, Edelbrock's supercharger FAQ limits the supplied calibration of certain systems to specified stock configurations. That restriction is product-specific, as are any emissions approvals.

Auxiliary and parallel controllers

An auxiliary device works with the factory ECU rather than replacing every function. Depending on its design, it may observe signals, modify selected signals or take over particular outputs. A parallel ECU may control fuel and ignition while the factory controller retains other duties; Haltech documents such an arrangement for a specific Holden/Buick V6 installation. The exact functions are product- and vehicle-specific. Haltech: Holden/Buick V6 example

Changing a signal seen by the factory ECU can also change its other calculations or trigger plausibility checks. Verify the complete effect using the relevant documentation and measured results; do not assume only the intended output changes. Some patch-harness controllers have a manufacturer-specific pass-through function. For example, Haltech states that the corrections in its documented copy-through mode are ignored; that detail must not be generalised to other products. Haltech: copy-through feature

What the auxiliary device changes

ApproachExample and checks
Alter a sensor signalA programmable unit may report a modified MAP or MAF signal to the ECU. The same input may affect several calculations, so check fuel, ignition, boost and diagnostics where applicable. Split Second PSC1-001 documentation describes one such device.
Modify an actuator commandSome fuel controllers alter the injector pulse after the ECU calculates it. Dobeck describes an early product that added pulse width; other designs can behave differently. Confirm the injector and driver type, the control range and how factory feedback reacts. Dobeck product history.
Control an additional actuatorAn auxiliary controller can drive an additional injector if designed and configured for it. Its fuel supply, electrical load and failure response must be considered as part of the system. Split Second documents additional-injector and signal-calibrator versions of its FTC1; the connection and setup depend on the exact version. FTC1 documentation.

These are different functions, and a product may combine them. A programmer that writes a calibration and is then disconnected is also a different arrangement from a controller that stays in the signal path. Establish which signals are altered, what happens on loss of power or a sensor fault, and whether a documented pass-through exists. Validate operation and fault response for the actual installation; do not assume any device leaves factory safeguards or diagnostics unchanged.

Feedback and unintended effects

When an auxiliary device changes a load signal to influence fuelling, the factory ECU may also use that signal in ignition, boost, torque or diagnostic calculations. If a changed reading selects a different ignition operating point, the resulting timing must be checked as well as the measured mixture. A corrected air–fuel reading alone does not validate the complete calibration.

Where closed-loop mixture control is active, feedback can respond to an imposed fuelling change and learned corrections may persist into later operation. Record the control mode and available short- and long-term corrections alongside the measured result; behaviour and learning ranges depend on the particular ECU. See adaptations and calibration drift.

Knock feedback is another independent interaction: actual knock and unrelated mechanical noise can both influence what a detection system reports. Some systems use both immediate and learned ignition corrections, as described for Haltech knock control. Investigate the signal, installation and combustion conditions using the relevant manufacturer's procedures; a quieter or absent indication does not prove knock has stopped. Preserve effective engine protection and confirm the cause before changing a sensor or its mounting.

Diesel pressure signals also need system-specific interpretation. On the 6.0-litre Power Stroke described in Ford’s 2003 OBD summary, injection control pressure refers to the high-pressure oil that actuates the injectors, not a common-rail fuel-pressure sensor. As a separate example, Edge’s Ford Juice installation guide shows an ICP connection for its specified 1999–2003 7.3-litre application and different connections for its 6.0-litre application. A connection list alone does not establish how the module processes each signal. Identify the exact product, engine and wiring, and verify measured versus requested pressure and diagnostic behaviour using the applicable procedures. A modified or intercepted signal may not represent an independent measurement of the physical pressure. See HEUI fuel systems.

Aftermarket standalone ECU

A standalone controller can take responsibility for the engine functions its hardware and software support. A plug-in or patch-harness installation may simplify connections on a documented application; a universal ECU requires appropriate wiring and configuration. Either still needs correct sensor calibration, trigger settings, injector and ignition compatibility, and a suitable engine calibration. Factory instruments, immobiliser, transmission, air conditioning and CAN communications may require separate support or retained modules. Check the specific product and vehicle rather than assuming that every original function remains available. Standalone ECU fuel tuning guide.

Standalone selection checklist

Before choosing a controller, list the engine's requirements and assign each signal to a compatible input or output. Count functions needed at the same time, including future expansion; a configurable channel already assigned to an injector is not also available for a fan or boost valve.

  • Engine and synchronisation: confirm engine type, cylinder count, supported crank and cam patterns and required injection and ignition modes. Full sequential operation requires suitable cycle synchronisation; Haltech's fuel configuration documentation gives one implementation.
  • Outputs and loads: check the number and electrical ratings of injector and ignition outputs, coil igniters, staged injectors, idle control, boost, fans and relays. Direct-injection drivers and electronic throttles may need specific support or hardware. Output current and wiring limits are model-specific; see this MoTeC M142 datasheet for an example.
  • Inputs and vehicle integration: confirm sensor ranges and types, trigger conditioning, wideband controller, fault inputs, transmission, instruments, immobiliser and communications. A sensor that physically plugs in still needs compatible electrical characteristics and calibration.
  • Installation and support: check supply voltage, current, mounting environment, enclosure and connector clearance; include the harness, sensors, external drivers, software access, logging, calibration and professional support in the total cost. Follow the actual product's mounting and wiring instructions.
  • Calibration and logging: a matching connector or base map can shorten setup but does not verify fuel, ignition, protection or road behaviour. Check logging channels, rates and storage, then validate the installation and its fault responses with suitable equipment.

Electrical integration and validation

  • Map which controller supplies each sensor and drives each actuator. Do not connect two outputs together without a documented compatible arrangement.
  • Shared sensors need particular care: an additional input can alter a circuit. Haltech notes that a shared temperature sensor may already have a pull-up in the factory ECU, so its additional controller's pull-up must be disabled for the installation it describes. Other devices must be checked against their own wiring instructions. Haltech: temperature-sensor diagnosis
  • Verify fuel pressure, injector operation, sensor readings and commanded versus measured lambda under controlled conditions. Check cold start, idle, transients, faults and interactions with other vehicle modules, not just peak power.
  • Document the installed hardware, original calibration and wiring, and the approved recovery method before changes. Retain engine and vehicle protection functions appropriate to the application.

Emissions and road-use requirements depend on the vehicle, modification and jurisdiction; confirm the applicable requirements before choosing an installation.

For a complete conversion, see planning and integrating an EFI engine swap.

Revision 9: Choosing factory remapping, auxiliary control or a standalone ECU

When an engine is modified, its control strategy must suit the hardware and the vehicle around it. The usual choices are to recalibrate the factory controller, add another controller alongside it, or install an aftermarket ECU. These labels describe different architectures, not guarantees about the features, performance or legality of a particular installation.

Recalibrating the factory ECU

A supported reflash changes data in the original controller. It can retain factory integration, diagnostics and control functions when they remain supported by the particular calibration. The available tables and access methods depend on the ECU, software version and tool; a tuning device cannot automatically make an unsupported sensor, injector or actuator compatible. How an ECU is remapped explains the read, edit and write process.

A supplied forced-induction kit calibration is matched to a stated vehicle and hardware configuration. Confirm the exact application, fuel requirement, included parts and restrictions before installation; later changes to the intake, exhaust, injectors or engine may require a different calibration and validation. For example, Edelbrock's supercharger FAQ limits the supplied calibration of certain systems to specified stock configurations. That restriction is product-specific, as are any emissions approvals.

For a concrete fitment contrast, Edelbrock lists its 15630 kit for specified 2010–15 Camaro SS LS3 manual-transmission applications without a supplied handheld programmer, while its 1597 kit is listed for specified 2010–13 Camaro SS L99 automatic applications with a tune intended for the stated stock configuration. Both product descriptions include charge cooling. These are distinct packages; check the current instructions, emissions approval and exact vehicle before ordering or applying a calibration. A listing for one does not establish fit or safe settings for another.

Auxiliary and parallel controllers

An auxiliary device works with the factory ECU rather than replacing every function. Depending on its design, it may observe signals, modify selected signals or take over particular outputs. A parallel ECU may control fuel and ignition while the factory controller retains other duties; Haltech documents such an arrangement for a specific Holden/Buick V6 installation. The exact functions are product- and vehicle-specific. Haltech: Holden/Buick V6 example

Changing a signal seen by the factory ECU can also change its other calculations or trigger plausibility checks. Verify the complete effect using the relevant documentation and measured results; do not assume only the intended output changes. Some patch-harness controllers have a manufacturer-specific pass-through function. For example, Haltech states that the corrections in its documented copy-through mode are ignored; that detail must not be generalised to other products. Haltech: copy-through feature

What the auxiliary device changes

ApproachExample and checks
Alter a sensor signalA programmable unit may report a modified MAP or MAF signal to the ECU. The same input may affect several calculations, so check fuel, ignition, boost and diagnostics where applicable. Split Second PSC1-001 documentation describes one such device.
Modify an actuator commandSome fuel controllers alter the injector pulse after the ECU calculates it. Dobeck describes an early product that added pulse width; other designs can behave differently. Confirm the injector and driver type, the control range and how factory feedback reacts. Dobeck product history.
Control an additional actuatorAn auxiliary controller can drive an additional injector if designed and configured for it. Its fuel supply, electrical load and failure response must be considered as part of the system. Split Second documents additional-injector and signal-calibrator versions of its FTC1; the connection and setup depend on the exact version. FTC1 documentation.

These are different functions, and a product may combine them. A programmer that writes a calibration and is then disconnected is also a different arrangement from a controller that stays in the signal path. Establish which signals are altered, what happens on loss of power or a sensor fault, and whether a documented pass-through exists. Validate operation and fault response for the actual installation; do not assume any device leaves factory safeguards or diagnostics unchanged.

Signal range and device modes

Match the sensor's output type and range, the auxiliary device's input and output capabilities, and the factory ECU's expected signal and diagnostic limits. A voltage-based device is not automatically compatible with a frequency, digital or SENT sensor, and an output within the electrical range can still represent an implausible or incorrect load to the ECU.

For example, Split Second's PSC1-001 documentation describes a direct-output mode with a programmable 0–5 V output as well as signal-modification arrangements. That range and those modes belong to this model, not every signal calibrator or ECU. Its FTC1 family datasheet describes different versions for MAP, MAF and additional-injector functions; check the precise part and configuration. The physical pressure or airflow, the device input and output, and the ECU's interpreted load are different observations. Verify them with suitable independent measurement and logging over the operating range, including diagnostics and fault responses.

Feedback and unintended effects

When an auxiliary device changes a load signal to influence fuelling, the factory ECU may also use that signal in ignition, boost, torque or diagnostic calculations. If a changed reading selects a different ignition operating point, the resulting timing must be checked as well as the measured mixture. A corrected air–fuel reading alone does not validate the complete calibration.

Where closed-loop mixture control is active, feedback can respond to an imposed fuelling change and learned corrections may persist into later operation. Record the control mode and available short- and long-term corrections alongside the measured result; behaviour and learning ranges depend on the particular ECU. See adaptations and calibration drift.

Knock feedback is another independent interaction: actual knock and unrelated mechanical noise can both influence what a detection system reports. Some systems use both immediate and learned ignition corrections, as described for Haltech knock control. Investigate the signal, installation and combustion conditions using the relevant manufacturer's procedures; a quieter or absent indication does not prove knock has stopped. Preserve effective engine protection and confirm the cause before changing a sensor or its mounting.

Diesel pressure signals also need system-specific interpretation. On the 6.0-litre Power Stroke described in Ford’s 2003 OBD summary, injection control pressure refers to the high-pressure oil that actuates the injectors, not a common-rail fuel-pressure sensor. As a separate example, Edge’s Ford Juice installation guide shows an ICP connection for its specified 1999–2003 7.3-litre application and different connections for its 6.0-litre application. A connection list alone does not establish how the module processes each signal. Identify the exact product, engine and wiring, and verify measured versus requested pressure and diagnostic behaviour using the applicable procedures. A modified or intercepted signal may not represent an independent measurement of the physical pressure. See HEUI fuel systems.

Aftermarket standalone ECU

A standalone controller can take responsibility for the engine functions its hardware and software support. A plug-in or patch-harness installation may simplify connections on a documented application; a universal ECU requires appropriate wiring and configuration. Either still needs correct sensor calibration, trigger settings, injector and ignition compatibility, and a suitable engine calibration. Factory instruments, immobiliser, transmission, air conditioning and CAN communications may require separate support or retained modules. Check the specific product and vehicle rather than assuming that every original function remains available. Standalone ECU fuel tuning guide.

Standalone selection checklist

Before choosing a controller, list the engine's requirements and assign each signal to a compatible input or output. Count functions needed at the same time, including future expansion; a configurable channel already assigned to an injector is not also available for a fan or boost valve.

  • Engine and synchronisation: confirm engine type, cylinder count, supported crank and cam patterns and required injection and ignition modes. Full sequential operation requires suitable cycle synchronisation; Haltech's fuel configuration documentation gives one implementation.
  • Outputs and loads: check the number and electrical ratings of injector and ignition outputs, coil igniters, staged injectors, idle control, boost, fans and relays. Direct-injection drivers and electronic throttles may need specific support or hardware. Output current and wiring limits are model-specific; see this MoTeC M142 datasheet for an example.
  • Inputs and vehicle integration: confirm sensor ranges and types, trigger conditioning, wideband controller, fault inputs, transmission, instruments, immobiliser and communications. A sensor that physically plugs in still needs compatible electrical characteristics and calibration.
  • Installation and support: check supply voltage, current, mounting environment, enclosure and connector clearance; include the harness, sensors, external drivers, software access, logging, calibration and professional support in the total cost. Follow the actual product's mounting and wiring instructions.
  • Calibration and logging: a matching connector or base map can shorten setup but does not verify fuel, ignition, protection or road behaviour. Check logging channels, rates and storage, then validate the installation and its fault responses with suitable equipment.

Electrical integration and validation

  • Map which controller supplies each sensor and drives each actuator. Do not connect two outputs together without a documented compatible arrangement.
  • Shared sensors need particular care: an additional input can alter a circuit. Haltech notes that a shared temperature sensor may already have a pull-up in the factory ECU, so its additional controller's pull-up must be disabled for the installation it describes. Other devices must be checked against their own wiring instructions. Haltech: temperature-sensor diagnosis
  • Verify fuel pressure, injector operation, sensor readings and commanded versus measured lambda under controlled conditions. Check cold start, idle, transients, faults and interactions with other vehicle modules, not just peak power.
  • Document the installed hardware, original calibration and wiring, and the approved recovery method before changes. Retain engine and vehicle protection functions appropriate to the application.

Emissions and road-use requirements depend on the vehicle, modification and jurisdiction; confirm the applicable requirements before choosing an installation.

For a complete conversion, see planning and integrating an EFI engine swap.