How GhostTune handles ECU changes

Changing an ECU value is more than editing a number on a screen. GhostTune keeps temporary changes, permanent storage, and result checking as separate parts of a guarded workflow.

Temporary Write and Permanent Burn are different actions

GhostTune does not treat every edit as a permanent change. It presents two distinct choices:

• Temporary Write changes the active ECU value for the current powered session. The change does not survive an ECU power cycle.
• Permanent Burn stores the supported change so it remains after a power cycle.

Keeping these actions separate lets a user evaluate a supported change temporarily before deciding whether it should be retained.

Compatibility is checked before changes are enabled

GhostTune only enables supported ECU changes when the connected hardware and firmware match a published supported configuration. A working network connection by itself does not establish compatibility.

What the user sees during a supported change

1. Current ECU data is read. The app starts from the connected ECU's current information.
2. The user chooses temporary or permanent. Temporary changes and permanent storage remain separate choices.
3. Normal live updates pause briefly. This prevents routine display traffic from competing with the change.
4. The requested change is applied.
5. The affected data is read again.
6. The result is compared. GhostTune checks the returned value before reporting the operation as complete.
7. Normal live updates resume.

Why result checking matters

Sending a command does not by itself prove that the ECU accepted and retained the expected value. A connection interruption, rejected response, unexpected data, power issue, or hardware problem can prevent the requested result.

GhostTune therefore reads the affected information again and compares the result. A mismatch is reported as a mismatch rather than being presented as a successful change.

What happens when communication is interrupted

If communication does not complete normally, GhostTune reports the detected condition rather than silently assuming success. Restore the connection and confirm the relevant ECU state before continuing.

This does not eliminate every possible risk. Power loss, wiring faults, ECU faults, firmware behavior, and other hardware conditions can still affect an operation. A known-good backup and a safe working environment remain essential.

A practical way to use the workflow

• Keep a known-good tune backup before making live changes.
• Use Temporary Write when evaluating a supported adjustment that should not yet survive a power cycle.
• Use Permanent Burn only after confirming that the change is intended to remain.
• Do not attempt ECU changes with an unsupported configuration.
• Treat a reported mismatch or interruption as unresolved until the ECU state is confirmed.