What this code means
Modern GNSS receivers don't just read a satellite position — they also run security checks on the signal itself, including OSNMA message authentication (Galileo's open service navigation message authentication) and anti-spoofing analysis that looks for signals designed to fake the receiver's position. Code 96, GNSS anomaly, means one of these checks failed: the tachograph detected a suspected spoofing attack, or a GNSS message it could not authenticate. On the VDO DTCO 4.1 this is logged as DTC 002E80.
Code 96 is a security event, not a broken part. It's different from code 82 (an internal hardware fault inside the GNSS receiver) and code 83 (no GNSS signal at all for three hours of driving). Codes 82 and 83 point to a broken or blocked receiver; code 96 means the receiver is working, but the signal it's getting looks wrong.
What to do now
The manual's guidance for code 96:
- Acknowledge the message on the display.
- Check the vehicle and antenna area for anything unusual — an unfamiliar device near the antenna, a damaged or repositioned antenna mount, or signs the cab has been tampered with.
- Restart the tachograph and confirm GNSS positioning returns to normal on the next drive.
- Consult an approved workshop if the anomaly persists or recurs — both a genuine spoofing attempt and a failing GNSS module need professional diagnosis.
Your tachograph logs this fault — TAGRA reads it
TAGRA doesn't resolve a GNSS anomaly — only an approved workshop can rule out tampering or a receiver fault. But once code 96 is written to the tachograph's memory and your driver card, TAGRA finds it in your downloaded data, evaluates it and documents it — exactly what you need at a roadside check, and to show the anomaly was investigated.
Stop looking up codes by hand — try TAGRA TRUCKER free for 30 daysWhy it happens
According to the manual, code 96 is triggered by:
- A suspected spoofing attack — a signal broadcast to make the receiver report a false position or time.
- A GNSS message that failed OSNMA authentication, Galileo's anti-spoofing signature check.
- Less often, heavy GNSS jamming or interference that the receiver's security logic misreads as an anomaly.
Unlike codes 82 and 83, the receiver itself is functioning — the fault is in what the signal claims to be, not in the hardware reading it.
Can you keep driving?
Yes, in principle — code 96 doesn't eject the card or stop recording by itself. But because it's flagged as a security-relevant, High severity event, the repair obligation under Article 37 of Regulation 165/2014 applies: have it checked as soon as circumstances permit. If the vehicle cannot return to base within a week of the fault, the repair must be carried out en route.
A GNSS anomaly is stored in the tachograph's mass memory and on your driver card, and shows up at every later download or control. Enforcement officers treat repeated GNSS-security entries as a possible tampering indicator, which can trigger a closer inspection — even where no tampering is ultimately found. Leaving the fault unresolved can itself be treated as a breach of the Article 37 repair obligation at a roadside check.
Also displayed as
Drivers across Europe see the same fault under different on-screen wording. These are the real search terms used for code 96:
- GNSS-Anomalie 96 — German
- Anomalie GNSS 96 — French
- Anomalia GNSS 96 — Italian
- GNSS-afwijking 96 — Dutch
- Anomalia GNSS 96 — Polish
Related codes
Frequently asked questions
Is GNSS anomaly (code 96) the same as a security breach?
No. A security breach — such as an opened housing — automatically ejects the driver card and is treated as the most critical case. Code 96 flags a suspected GNSS spoofing attack or a failed signal authentication check; the card stays inserted and recording continues, but the fault is still security-relevant and requires a workshop check if it persists.
How is code 96 different from codes 82 and 83?
Codes 82 and 83 point to a broken or blocked GNSS receiver — an internal hardware fault or no signal at all. Code 96 means the receiver is working and receiving a signal, but that signal failed a security check, such as OSNMA authentication or anti-spoofing analysis.
Can I keep driving with a GNSS anomaly (code 96)?
Yes, in principle — the tachograph doesn't eject the card or stop recording. Because it's a High-severity, security-relevant event, though, the repair obligation under Article 37 applies: a workshop visit as soon as circumstances permit. If the vehicle cannot return to base within a week of the fault, the repair must be carried out en route.
What should I check myself before calling a workshop?
Acknowledge the message, look around the antenna and cab for anything unusual — an unfamiliar device, a damaged or repositioned antenna mount, signs of tampering — and restart the tachograph. If the anomaly clears and doesn't return, note it in your records; if it persists or recurs, book an approved workshop.