OBD, bench or boot: identify the method before the file request.

Alientech's connection-method documentation describes OBD as access through the vehicle's diagnostic port, bench as a connection through the control unit's connector without opening its casing, and boot as access with the control unit opened. The supported operations and required accessories depend on the selected application.

These definitions help you describe a job; they are not a procedure for carrying it out. Use the current protocol instructions in your tool software for connections, power requirements and the operation itself. A general online guide cannot replace the instructions for the control unit on your bench.

Start with the vehicle and ECU identification, then check the current coverage in the programming tool. Look at the particular read and write operations listed, rather than stopping when you see a familiar model name. If the required operation is not available, resolve that uncertainty with the tool provider and file service before taking the vehicle apart or promising a turnaround.

Record the tool, software version, chosen protocol and connection method in the job notes. If another technician takes over, that information explains how the read was obtained and which instructions apply. It also makes a support question much more precise than saying that a certain brand is not reading.

The connection method describes access. The read type describes the file's origin. A virtual read supplies an original associated with a software identifier; a direct read captures the ECU content being read. AutoTuner documents that a direct read can therefore contain existing tuning, while a virtual original does not reproduce those modifications.

Put both pieces of information in the request. A note saying OBD virtual read is more useful than OBD alone. If you are uncertain what the tool exported, preserve the file as created and ask before renaming it, converting it or treating it as a complete backup.

The file service needs to understand what it is receiving. Upload the requested file and include the hardware/software identifiers, operation used and any relevant messages from the tool. Keep other tool outputs in your workshop archive so they are available if support asks for them.

Do not assume that two files are interchangeable because they have the same extension or came from the same vehicle. A calibration export and a backup can have different purposes. AutoTuner, for example, documents a separate backup output for supported bench and boot reads. The required delivery format should be confirmed for your particular workflow.

A practical enquiry names the vehicle and engine, ECU identifiers, tool and protocol, intended method and requested file work. Add whether a read has succeeded and what output is available. This turns an open-ended question into a decision about a specific next step.

For example: We have this ECU identification, this tool protocol and a successful bench export; is this the correct input for the requested Stage 1 service? If a step fails, include the actual operation and message. Avoid experimenting with another file or connection method simply because a similarly named vehicle appeared in an online discussion.