Aller au contenu

U0078 Élevée Générique / SAE

U0078: Bus de communication des calculateurs F — désactivé

WhatsApp Telegram X E-mail

Que faire

If this has been "fixed" before and keeps coming back, read this — because it may never have been fixed at all.

One of your car's computers deliberately stopped talking to the network to protect it — see U0073.

Here is the trap. On many cars, that computer rejoins the moment the fault codes are cleared. So the warning lights go out, everything works, and the car drives away.

That looks exactly like a repair and it is not one. The wiring fault is untouched, and the computer will withdraw again as soon as enough errors build up — which might be minutes or might be weeks.

So the question worth asking is not what was done, but what was found. "We cleared the codes and it was fine" is not a diagnosis, and a fault that has come back three times has probably never actually been investigated.

Ask what was measured, and what the result was.

One thing that genuinely helps: ask for the codes to be read and recorded before they are cleared, and then cleared once deliberately. That way the next occurrence is a clean record rather than a mixture of old and new faults, which makes it far easier to find.

Ce que signifie ce code

A module has taken itself off communication bus F. See U0073 for what bus off means and U0080 for what a sixth lettered network usually implies about the vehicle.

One point belongs here and it is about what a repair actually is: clearing the code is not one.

U0073 explains that recovery differs between designs — some modules rejoin automatically, some after an ignition cycle, some only when the fault memory is cleared. So on a good many vehicles, clearing the codes brings everything back to life.

And that is genuinely misleading, because it looks exactly like a repair. The module rejoins, the warning lamps go out, the vehicle drives away, and the underlying wiring fault is untouched. It returns as soon as enough errors accumulate again — which may be minutes or weeks depending on how marginal the fault is.

Which produces a pattern worth naming: a vehicle that has been "fixed" several times by having its codes cleared. Each visit ended with everything working. None of them changed anything.

So the instruction is to establish what was found rather than what was done. "The codes were cleared and it drove away fine" is not a diagnosis, and a fault that has come back three times has never actually been looked at.

And it is worth clearing the codes deliberately once, after reading them, precisely so that the next occurrence is a fresh record rather than a mixture of old and new — see U0064.

Causes probables

Commencez ici

Moins fréquent

Symptômes

Composants concernés

Des informations, pas des instructions

CarGeek est un ouvrage de référence, pas un manuel d'atelier. Ses pages sont rédigées à partir de sources publiques et de ce que d'autres ont constaté, jamais à partir de la documentation technique du constructeur ; elles peuvent donc être erronées ou incomplètes pour votre véhicule précis. Une partie de ce qu'elles décrivent présente un risque réel : haute tension, carburant sous pression, énergie accumulée, pièces chaudes ou en mouvement.

Avant d'agir sur quoi que ce soit, faites-le vérifier par une personne formée, en suivant la procédure du constructeur pour votre véhicule. Rien ici ne remplace cette procédure.

Expérience de la communauté

Soyez le premier à en faire le compte rendu

Rien n'a encore été publié à ce sujet. Tout ce que vous avez trouvé mérite d'être noté — même une impasse épargne à quelqu'un le même après-midi.

Ce qui rend un compte rendu utile :

  • La voiture — marque, modèle, année et moteur. La même panne ne se comporte pas pareil sur chacune.
  • Ce que vous avez mesuré, pas seulement ce que vous avez remplacé.
  • Ce qui a réellement résolu le problème — ou que rien ne l’a résolu, ce qui est utile aussi.

Se connecter ou créer un compte pour ajouter ce que vous avez trouvé à propos de U0078.