In This Guide

Identify the vehicle and the log source

Begin with registration, engine, current hardware and ECU software identity. State which diagnostic or logging tool produced the file and when it was recorded. A log without that information can be difficult to interpret, especially if software or hardware has changed since the recording.

Preserve the original export rather than only a graph screenshot. Include the parameter names and units as presented by the tool. Different controllers expose different information, and similarly named channels can represent different values. Available logging does not itself confirm a supported calibration or replacement operation.

Separate a target from a reported result

A requested value describes a demand or target reported by the system. An actual channel may describe a sensor reading, a calculated value or a filtered result, depending on the controller. Ask the technician to identify what each channel represents before drawing conclusions from a gap between them.

The operating state matters. Temperature, engine speed, load, control limits and related faults can change the expected relationship. One disagreement on a chart does not by itself condemn a turbo, injector or map. Useful analysis combines the log with diagnostic findings and the known configuration.

Keep the measurement conditions together

State the fuel used, ambient conditions where known, relevant vehicle temperatures and any warnings during recording. If results are being compared, identify what changed between files. Preserve the time series so transient behaviour is not reduced to unrelated peak numbers.

Avoid mixing units or assuming every pressure channel has the same basis. Record whether a channel is measured or calculated when the tool identifies that distinction. Alientech documents parameter recording on supported applications; the available channels and interpretation still belong to the exact vehicle.

Arrange verification within the accepted scope

Logging should answer an agreed question, such as whether an existing symptom remains or how the accepted calibration behaves under appropriate conditions. Do not carry out unsafe road testing or try to reach an advertised output merely to complete an enquiry. The technician can advise what evidence is useful.

Send Precision Remaps UK the registration, postcode, software history, symptom or goal and available original files through Northern Calibration. Discuss any further logging or measurement as part of the quote. Keep a claimed gain separate from a verified before-and-after result for the finished vehicle.

Technical reference: Alientech: supported ECU parameter recording. Reviewed 7 October 2026. Work and any remaining installation requirements are assessed for the exact application.

YOUR ENQUIRY CHECKLIST

Send the information that helps.

  • Vehicle, hardware and ECU / TCU software identity
  • Tool, recording date and original log export
  • Parameter names, units and measured / calculated status
  • Fuel, temperatures, conditions and related faults
  • The question the log is intended to answer
PLAN THE NEXT STEPKeep tuning evidence and support recordsCompare supplied performance figures
RELATED TUNING OPTIONSStage 1 ECU remappingStage 2 hardware-matched tuningBuild a vehicle-specific tuning enquiry

Questions about this enquiry

Does requested torque prove the engine produced that torque?

No. Identify the channel and measurement basis. A control request is different from a verified output measurement.

Should I send only a screenshot of the highest numbers?

Send the original file where possible, with vehicle identity, parameter names, units and recording conditions.