The Suzuki code that isn't really about the glow plugs
P0683 is the fourth most-scanned code in our entire dataset, and it is Maruti Suzuki's almost exclusively — a communication fault, not a glow plug failure.
P0683 is the fourth most-scanned code out of 9,298 generic codes in our entire dataset — ahead of codes most drivers would guess as more common — and it belongs almost entirely to one manufacturer's diesels. That is a strong enough pattern to be worth a post of its own, in the same spirit as the Toyota hard-start code covered earlier on this blog.
What the code actually means
P0683 is a communication fault, not a heating-element fault. The glow plug control module — the box that decides when and for how long to energise the glow plugs on a cold diesel start — talks to the main engine computer over a dedicated circuit. This code sets when that conversation breaks down: the PCM sends a request and does not get the response it expects back from the GPCM, or the message that does come back does not check out.
That distinction matters for where you look. A code about the glow plugs themselves would point you at the heating elements. This one points you at the wire between two computers, and at the connectors on either end of it.
Who actually sees this code
Maruti Suzuki accounts for 92.48% of every scan carrying P0683 — 4.3 times its 21.5% share of the fleet we see overall. Among the vehicles we could identify, the Vitara Brezza alone makes up 46.55%, with the Swift at 14.18%, the Baleno at 8.60% and the Ertiga at 7.61%. Outside that lineup this code is close to a non-event; inside it, it is one of the most common faults in our entire dataset.
What shows up alongside it
P0110 is an intake air temperature circuit fault and P0100 is a mass airflow circuit fault — a diesel-side pair that tends to travel together for the same reason the P0113/MAF pairing does in a separate post here: shared wiring, shared connectors. C1057 and C1091 are Suzuki-specific ABS and ESP communication codes with no public lookup page of their own, but their presence alongside a glow-plug-module communication fault is the real signal — this is not one broken sensor, it is a coherent pattern of communication faults across several modules on the same vehicle. P0089, a fuel pressure regulator performance code, appears in roughly one scan in ten and is worth checking independently rather than assuming it shares the same root cause.
What that pattern suggests
When one module's communication fails in isolation, look at that module and its wiring. When several modules on the same platform show communication faults together — glow plug control, ABS, ESP — the more efficient place to start is the shared backbone: the CAN bus wiring harness, a chassis ground common to several modules, or a battery/charging fault feeding all of them at once, in the same way a sagging supply voltage was shown to cascade across an ABS module's wheel sensors in a separate post on this blog. Chase the individual module fault first and you may fix the same underlying problem four times.
What to do next
If you are working on a Vitara Brezza, Swift, Baleno or Ertiga and see P0683, scan for C1057 and C1091 before doing anything else — their presence changes the diagnosis from "one module's connector" to "check the shared wiring and the battery/charging system first." Check battery voltage and the main chassis ground strap, since a marginal supply is a plausible common cause across several modules on the same platform. If P0683 is genuinely isolated — no ABS or ESP comms faults alongside it — then the glow plug control module's own connector and the wiring run to the PCM are the next place to look.
Can you keep driving?
A communication fault with the glow plug control module mainly affects cold starts — expect harder starting in cold weather rather than a drivability problem once the engine is running. It is not an emergency, but a diesel that struggles to start reliably is worth getting looked at before winter rather than after the first morning it does not catch.
Read & clear your own codes
Scan your car, see what every code means in plain English, and clear it once it's fixed — with OBD DashX on your phone.
Related codes
Figures reflect only diagnostic scans recorded through our own apps and tools. Cars are typically scanned because a symptom or warning light prompted it, so these counts describe our scan records — not the incidence of faults in any model, and not the quality, reliability, or safety of any vehicle. No comparison between manufacturers or models is implied. All trademarks belong to their respective owners; no affiliation or endorsement is implied.