Remote coding: how it actually works

Coding over a remote connection sounds like a trick to many people. It is not. Technically exactly the same thing happens as on site — the technician just sits at their computer rather than in your car.

The setup

Three links sit between your car and our software: an OBD interface at the diagnostic port, your laptop, and a remote support connection. The software runs on your laptop; we operate it through the connection.

• OBD interface — an ENET cable (BMW) or the matching adapter for your brand
• Windows laptop on mains power, not on battery
• Stable internet connection, wired preferred
• Charger on the car or a fully charged battery
• TeamViewer or AnyDesk

Why voltage matters so much

While a control unit is being written, the vehicle voltage must not drop. Ignition on means consumers on, and a weak battery gives up at exactly the worst moment. That is why we insist on a charger. It is the most common reason we postpone an appointment.

The sequence

First we read the vehicle order and back up the original state. Then we discuss what is actually possible — which often differs from the wish list. Only then do we write, item by item, with checks in between. You watch your own screen the whole time.

Where the limits are

Not everything works remotely. Engine software on locked control units needs removal. Anything requiring a visual inspection or a test drive does too. And if a control unit already has a fault, diagnostics come before coding.

The real advantage

No travel, no waiting around a workshop, and the appointment can be in the evening. For customers outside Switzerland it is the only practical option anyway.