← Latest papers
💻 computer science

Fault Detection and Explainable Classification in Automotive HIL Validation via Denoising Autoencoders and In-Context Large Language Models

This paper proposes a generalizable and explainable two-phase framework for automotive HIL validation that combines a denoising autoencoder for unsupervised fault detection with a few-shot prompted large language model to classify anomalies and generate interpretable diagnostic reports, achieving high accuracy without requiring labeled fault data.

Original authors: Mohammad Abboush, Hamza Ouarrad, Andreas Rausch

Published 2026-07-07
📖 4 min read☕ Coffee break read

Original authors: Mohammad Abboush, Hamza Ouarrad, Andreas Rausch

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are a mechanic trying to figure out why a car is making a weird noise. In the past, you'd have to listen to hours of engine recordings, guess what's wrong, and check a long list of rules to see if the noise matches a known problem. If the noise was something new, you'd be stuck.

This paper proposes a smarter, two-step assistant to help engineers validate automotive software. Think of it as a super-smart detective that works in two stages: first, it spots that something is wrong, and second, it explains exactly what is wrong and why.

Here is how the system works, broken down into simple concepts:

1. The "Silent Alarm" (Phase 1: The Denoising Autoencoder)

Imagine you have a perfect recording of a healthy car engine running smoothly. You teach a computer to memorize exactly what that "healthy" sound looks like.

  • How it works: The computer listens to the car's data. If the data sounds exactly like the healthy recording, it says, "All good." But if the data is even slightly "off" (like a scratchy record), the computer gets confused because it can't recreate the sound perfectly.
  • The Magic: It doesn't need to know what the specific problem is yet. It just knows, "This doesn't sound like a healthy car." This is like a smoke detector: it doesn't need to know if the fire is caused by a candle or a short circuit; it just knows there is smoke and sounds the alarm.
  • The Result: This step catches almost every problem (97% accuracy) without needing a list of every possible fault beforehand.

2. The "Detective with a Cheat Sheet" (Phase 2: The Large Language Model)

Once the alarm sounds, the system takes a snapshot of the "sick" data and turns it into a short, easy-to-read story (text) for a Large Language Model (LLM)—the same kind of AI that powers chatbots.

  • The Setup: The AI is given a "cheat sheet" (called few-shot prompting). This cheat sheet contains examples of past problems and their solutions. For example: "When the battery voltage drops and the speed stays steady, it's a battery fault."
  • The Task: The AI looks at the new "sick" story, compares it to the cheat sheet, and acts like a detective. It doesn't just guess the answer; it ranks the top suspects, tells you how confident it is, points to the exact part of the car that is broken, and writes a short explanation.
  • The "Zero-Shot" Failure: The researchers tried asking the AI to guess without the cheat sheet (Zero-Shot). It was like asking a detective to solve a crime without looking at any past cases. It failed miserably (only about 50% accuracy).
  • The "Few-Shot" Success: Once the cheat sheet was added, the AI became a genius. Even a smaller, cheaper AI model (with 9 billion "brain cells") outperformed massive, expensive models that didn't have the cheat sheet.

3. The "Why" Matters (Explainability)

Old computer programs often just say "Error 404." This system is different. It gives a report that says:

  • Diagnosis: "The accelerator pedal sensor is faulty."
  • Evidence: "The pedal position signal jumped unexpectedly."
  • Reasoning: "Other signals changed too, but they changed because of the pedal, not the other way around."

This helps human engineers trust the AI because they can see the logic, just like a detective showing their evidence.

The Big Takeaway

The researchers tested this on two types of cars (gasoline and electric) and three driving styles (city, highway, and mixed).

  • The Detector caught 97% of the problems.
  • The Detective (with the cheat sheet) got nearly perfect scores in stable driving conditions.
  • The Lesson: It's not about having the biggest, most expensive AI brain. It's about giving the AI the right context (the cheat sheet). A smaller, smarter AI with a good guide works better than a giant AI with no guide.

In short: This system acts like a tireless, super-observant mechanic who knows exactly what a healthy car sounds like, instantly spots when something is wrong, and then writes a clear, evidence-based report explaining exactly what broke and why, all without needing to be retrained for every new type of car.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →