New to range: August 2026 - New products at a glance:

Headlight levelling sensors are a small part with a big job. Correct beam position supports safety, visibility and compliance. Automatic levelling depends on correct sensor input, control unit logic and actuator response across the whole system

• “Beam too high or too low” — check whether the levelling system reacts correctly to load changes before adjusting the lamp mechanically
• “Levelling function not working” — inspect the sensor, linkage, mounting points and actuator response first
• “Complaint started after body or suspension work” — remember that system alignment and calibration can be affected by vehicle changes, and calibration may be required afterwards

Levelling faults should start with a diagnostic routine, not a guess. Modern systems rely on fault-code readout, correct adjustment conditions and, where relevant, calibration after repairs or vehicle changes

• Read out stored faults before replacing the sensor
• Check signal plausibility, wiring condition and supply voltage first
• Confirm whether calibration or basic setting is needed after repair work

Fuel supply units remain a practical workshop category because reliable fuel delivery still depends on clean pressure control and stable feed from tank to engine.

• “Poor starting” or “long crank” — begin with a visual inspection for leaks, damaged
• “Erratic engine running” — first determine whether the fault lies in the low-pressure or high-pressure system, then use the relevant pressure values to narrow down the cause before replacing parts.
• “No power in the upper speed range” — check whether the pre-supply side is delivering enough fuel quantity and whether there are kinks, blockages or tank-ventilation issues

Fuel-system faults are often only solved properly when the whole supply chain is checked in sequence. Here is how a practical workflow should look like: visual inspection first, then fault-memory readout, parameter comparison, low-pressure testing and fuel-quantity checks. The high-pressure side should only be assessed after the low-pressure circuit has been checked and found OK

• Read out the fault memory and use pressure-related entries to guide the next tests
• Check the low-pressure sensor values against the vehicle manufacturer’s specifications before continuing with further diagnosis.
• If values are implausible, measure low-pressure supply and holding pressure, then check delivery quantity before moving on
• Keep the diagnosis system-level: blocked lines, filter condition, tank ventilation and the fuel delivery unit can all influence the complaint

ABS Sensors are one of those everyday electronics jobs that now sit right at the centre of vehicle safety systems . These signals are widely used, not only by ABS, TCS and ESP, but also by other systems via the control unit, which is why a clean diagnostic workflow matters before any replacement is made.

• “ABS warning lamp on” - read out the fault memory first, because the stored code helps direct the next diagnostic steps
• “ABS or stability system intervenes incorrectly” - compare the measured values or signal curves of all four wheel speed sensors, not just the reported corner
• “Repeated sensor fault” - check wheel bearing play, axle suspension and the impulse ring or encoder ring before fitting another sensor

This is exactly the kind of job where OE meets diagnostics.

The fault code alone does not automatically prove the sensor is defective. Good workshop practice is to confirm the complaint, check battery voltage and fuses, compare live data, verify supply and inspect the installation point before replacing parts

• Start with fault-code readout and measured-value comparison across the wheel speed sensors
• Check battery voltage and system-related fuses before deeper diagnosis
• Use a multimeter or oscilloscope as appropriate, bearing in mind that active and passive sensors are tested differently
• After replacement, clear faults, road test the vehicle and recheck all relevant control units because ABS faults may also be stored elsewhere in the network