01 · Safety first
The vehicle manual gives instructions on what to do
The instructions depend on the model and associated alerts. Consult your instructions and send the exact message to support if in doubt. This guide does not guarantee that you can reach the garage.
The Renault Mégane IV instructions, for example, distinguishes an ABS anomaly from a braking failure accompanied by other alerts. This example does not automatically translate to your car.
A photo of the lights can be useful, only with the vehicle stationary and without exposing yourself. Do not test the braking and do not try to reproduce the fault to complete your description.
02 · Related functions
Two lights do not necessarily mean two rooms
ABS helps prevent the wheels from locking when braking. Stability control, often called ESP or ESC, helps to control the trajectory. These systems use some common information, including wheel speed.
An anomaly can thus affect several functions. HELLA describes this information sharing and the necessary checks around the wheel sensors: connections, wiring, power supply and associated mechanical elements.
A code guides the search
A wording that mentions a sensor is not enough to declare this sensor defective. The cause must be checked on the vehicle before choosing a part.
If your report contains several defects, our guide several codes present together explains how to keep leads distinct without confusing them with conclusions.
03 · Facts, with their limits
Describe what you actually noticed
Gather the information already known once it is safe. If you are missing a detail, write “unknown”; no further testing is necessary.
- The moment: When starting or during the journey? Note the date and circumstances already known.
- The exact alert: Indicators, colors, messages displayed and progress: remained lit, intermittent or disappeared.
- The behavior: Describe only a braking change or unusual behavior already noticed. Do not attempt to complete the file.
- Recent history: Intervention or incident, with the date if you know it. This is an element of context, not proof of the cause.
“I didn’t notice any change in braking” describes one observation. “The braking has been checked” implies an actual check. Keep this distinction in your message to the workshop.
04 · The scope of the survey
Has the ABS computer really been questioned?
A reader which only consults the engine cannot conclude that there is no ABS fault. Ask which control units were read and if any were inaccessible.
ABS not questioned
The reading did not relate to this calculator. Its contents are unknown.
ABS connection not possible
The communication attempt failed. Keep the message from the tool; This does not prove that the computer is defective.
ABS read, no fault noted
The report does not indicate any defects within the scope of this reading. This result is not enough to explain the warning light or to certify braking.
OBDeleven distinguishes engine reading from access to other computers. The possibilities depend on the tool and the vehicle: check their compatibility and the actual content of the report.
If communication fails, also consult the guide diagnostic scan tool that does not connect, retaining the exact error message.
05 · Keeping the clues
Keep the report before erasing
If a reading has already been taken, keep the original report or readable captures. For each fault, keep the computer concerned, the complete code, its wording, its status and associated data available.
An erase can remove clues; it does not repair the cause. Let the workshop decide the appropriate time to erase, according to its diagnostic approach.
06 · To be sent to the garage
Your file, in six points
This form can be used over the telephone or accompany your request for support. Leave “unverified,” “not queried,” or “unknown” when this is the case.
- Vehicle
- Make, model, year, engine and mileage.
- Alerts
- Exact messages, lights and colors, date, circumstances and observed evolution.
- Behavior and instructions
- What you noticed and the instructions in the instructions. Without verification carried out, indicate “not verified”.
- History
- Recent intervention or incident and date, if known.
- Reading completed
- Date, tool, control units questioned or not, communication failures, complete codes, labels and statuses.
- Documents and erasure
- Report or captures available. Faults already cleared: yes, no or unknown; when and with what tool, if you know.
Completely fictional example
“The ABS and ESP lights came on during the trip. I am attaching a photo taken after the stop. I did not notice any change in braking, but no checks were carried out. My reader queried the engine only: ABS was not read. I haven't erased the flaws. How to organize support? »
Before posting a capture in a public space, hide contact details and vehicle identifiers that are not necessary.
FAQ
Frequently asked questions
Points of reference to keep before treatment.
Can I reach the garage with these lights?+
LEDs alone do not allow remote response. Follow the instructions and assistance instructions. In the event of abnormal braking, red braking alert, STOP or stop instruction, move to safety as soon as possible and seek assistance. Do not continue the journey to read the faults.
My reader finds nothing: the fault has disappeared?+
Not necessarily. Check which ECUs were polled and if any communications failed. A reading of the engine only does not provide information on ABS computer faults. Even a faultless ABS reading is no substitute for appropriate checks.
The light has gone out: should we report it?+
Yes. Specify the circumstances already observed and keep the record available. The disappearance of the light does not prove that its cause has been treated. Don't try to bring it back while driving.
Should you buy an ABS sensor?+
Not just based on a light or fault label. The professional must check the cause: the connections, wiring, power supply or associated elements may also require checks.
I have already erased the defects: what should I transmit?+
Indicate when, with which tool and if you kept a report before erasure. If any information is missing, leave it unknown. Do not make multiple trips to bring back the visionaries; ask the workshop how to organize the rest.
Sources and limits
References consulted on November 12, 2026. The instructions specific to the model and its version remain priority.
- Renault Mégane IV: correction and driving assistance devices
- HELLA: ABS sensors, checks and fault finding
- OBDeleven: scope of ECU diagnostics
Renault provides a manufacturer example; HELLA describes professional controls; OBDeleven specifies the scope of its tool. Their procedures and compatibilities are not universal. This guide helps prepare a file, without establishing a diagnosis or replacing vehicle checks.
Clear observations to prepare for diagnosis
Diagolia helps organize symptoms and available readings to prepare for checks. The checks on the vehicle and the final decision remain with the professional.
