People hesitate to book remote work because they cannot picture it. Fair enough — here is the whole thing, start to finish.
Before the session
- You order and pay. You get a receipt and an invoice PDF straight away.
- We ask for the engine details — ESN or VIN (see where to find them). Nothing starts until we have this.
- We check the calibration matches your engine before booking. Occasionally this is where we tell you the job is not what you thought it was; better now than with the truck stripped.
- We agree a time. Give us two or three windows that suit you, and your time zone.
What you need in front of you
- The truck, with the ECM reachable
- A laptop with your diagnostic software and your interface (INLINE 7, Nexiq, DPA5 — whatever you normally use)
- TeamViewer or AnyDesk installed on that laptop
- A stable internet connection at the truck. Phone hotspot is usually fine; a connection that drops every two minutes is not.
- The battery on a charger
That last one is not a formality. Writing to an ECM can take a while, and voltage sagging mid-write is the one failure that turns a routine job into a recovery job. More on why.
During the session
You start TeamViewer and send us the ID. We connect to your laptop — your software, your interface, your licence. Nothing is installed behind your back and you watch the whole thing on your own screen.
We read the current calibration out first and keep a copy. Then we load the calibration for the job and write it. Depending on the ECM this takes anywhere from a few minutes to the better part of an hour.
You stay on the line. If something needs the key cycled or the engine cranked, you are the one at the truck.
After
We verify the ECM reports what it should, clear the codes that need clearing, and you run it. If the truck does not behave the way it should, tell us there and then while the connection is still open — that is the whole point of doing it live rather than emailing you a file.
How long, realistically
Most jobs are done in 45 to 90 minutes, including the setup chat. The write itself is rarely the long part; getting the interface talking is.
If it goes wrong
The original calibration we read out at the start is exactly what we put back. That is why we read first and ask second.