Software and coding

Firmware, coding and control units that refuse to talk. Including the ones locked after a crash.

When to have it looked at

  • A control unit that will not respond after a crash or a flat 12 V.
  • A replacement part fitted correctly that the car refuses to accept.
  • A fault that returns immediately after every clear.

Why it fails

Modern control units lock themselves after a crash signal, a failed update or a voltage drop mid-write, and a locked unit behaves exactly like a dead one. Most of them are not dead. Recovering the data, correcting it and writing it back is a different job from replacing hardware, and it is very often the whole repair.

How we work

  1. We record the condition in writing before anything is opened, and you get a copy.
  2. The unit is stripped and inspected. It is the only way to know the real state of it.
  3. Everything that matters is measured, not estimated.
  4. You get a written quote before any repair starts. Nothing proceeds without your agreement.
  5. We replace what has actually failed and what will fail next, not the whole assembly.
  6. It is tested under load and returned to you with the findings written up.

What decides the price

What moves the price is the platform, what we find once it is open — which nobody can know beforehand — and whether the original parts can be reused. That is why the quote comes after the inspection and not before it.

Turnaround, warranty and whether a teardown is chargeable are set by this workshop. Ask us before you commit.

What we have written about this

Book Software and coding, or ask us about it first.