ASE L4 ADAS Specialist cheat sheet

ADAS levels: L0 no automation, L1 driver assistance (either steering or speed), L2 partial automation (both simultaneously), L3 conditional, L4 high, L5 full.

Perception → fusion → planning → actuation is the standard ADAS pipeline; a fault in any stage can disable multiple features.

Sensor fusion combines complementary modalities: camera (classification, text), radar (range/velocity in weather), lidar (3D geometry), ultrasonic (short-range).

Redundancy: safety-critical functions (e.g., AEB) often use at least two independent sensing paths or plausibility checks to avoid false actuation.

CAN, CAN FD, FlexRay, and Automotive Ethernet are common in-vehicle buses; ADAS domain controllers typically bridge multiple buses.

Feature availability depends on enable conditions (speed window, temperature, sensor health, driver attention) and may be suppressed without a hard DTC.

A system architecture diagram shows sensor inputs, ECU processing, HMI outputs, and actuator commands; use it to trace which module owns a function.

Over-the-air (OTA) updates can change ADAS behavior; verify software version and calibration state after any update.

Functional safety (ISO 26262) defines ASIL levels; ADAS components are often ASIL B or higher, affecting repair and replacement procedures.

Forward camera: monocular or stereo; provides object classification, lane markings, signs, and free-space; sensitive to glare, occlusion, and windshield optics.

Radar: measures range and radial velocity via Doppler; robust in rain/fog/darkness but has angular resolution limits and can be affected by metallic obstructions or bumper coatings.

Lidar: time-of-flight or FMCW; produces 3D point clouds; sensitive to dirty lenses, rain, and retroreflective surfaces; often used for high-resolution mapping.

Ultrasonic sensors: short range (typically <5 m), used for park assist and low-speed AEB; affected by temperature, wind, and surface angle.

Mounting angle and height are critical; a small pitch or yaw error causes large range/azimuth errors at distance.

Radar behind a bumper requires a paint thickness and material specification; metallic or thick paint can attenuate the signal.

Camera field of view must be kept clear; stickers, tint, cracks, or aftermarket coatings in the optical path can degrade performance.

Sensor cleaning and heating systems are part of the sensor subsystem; a clogged washer nozzle or failed heater can set a performance DTC.

AEB (Autonomous Emergency Braking) uses forward sensor data to detect imminent collision and command braking; may be split into city (low speed) and interurban (high speed) functions.

ACC (Adaptive Cruise Control) maintains a set speed and a driver-selected time gap to a lead vehicle; gap settings are usually time-based (e.g., 1.0–2.5 s).

LKA (Lane Keeping Assist) applies steering torque to keep the vehicle in lane; LDW (Lane Departure Warning) only alerts; LCA (Lane Centering Assist) is a continuous centering function.

BSM (Blind Spot Monitoring) uses rear/side radar; RCTA (Rear Cross Traffic Alert) warns of crossing traffic when reversing.

TSR (Traffic Sign Recognition) uses camera data; speed limit info may be fused with navigation data and can be wrong if signs are misread.

Driver monitoring systems (DMS) use infrared cameras to detect distraction/drowsiness and may inhibit other ADAS features.

Feature performance is bounded by sensor field of view, weather, road geometry, and object classification confidence.

HMI warnings escalate (visual → audible → haptic) and may include a takeover request in L2/L3 systems.

After repair, verify feature operation per OEM procedure; some features require a dynamic test drive to relearn or confirm.

Static calibration uses precisely positioned targets at specified distances and heights in a controlled bay; dynamic calibration uses road features during a drive.

Calibration prerequisites: correct tire pressures, ride height, fuel level, and no heavy loads; vehicle must be on a level surface.

Target placement tolerances are typically tight (e.g., ±1–2 cm and ±0.1°); use OEM-specified target types and distances.

Camera calibration corrects intrinsic (focal length, principal point) and extrinsic (mounting pose) parameters; windshield replacement almost always requires camera recalibration.

Radar aiming may use a corner reflector or a metal plate target; check for bumper damage, misalignment, or non-OEM paint before aiming.

Lidar calibration aligns point clouds to the vehicle coordinate frame; may require a target-rich environment or a specific calibration rig.

Calibration can fail due to low battery voltage, incorrect target distance, dirty lenses, or unresolved DTCs; clear faults before retrying.

Record calibration results and software versions; some scan tools require a completed calibration record to clear certain DTCs.

Dynamic calibration requires specific driving conditions (speed range, lane markings, daylight) and may take 10–30 minutes.

DTC format: P/C/B/U system letter, 4-digit code; first digit 0 = generic, 1 = manufacturer-specific.

Freeze frame data captures operating conditions at fault set; use it to reproduce the fault environment.

Pending vs. confirmed vs. permanent DTCs: permanent codes clear only after the monitor runs and passes; they cannot be erased with a scan tool.

ADAS modules may store internal codes (e.g., calibration not learned, sensor blocked) that do not illuminate a dash lamp.

Bidirectional scan tool functions (actuator tests, calibration routines, sensor initialization) are required for many ADAS repairs.

Check for communication codes (U-codes) first; a bus fault can cause multiple false sensor DTCs.

After repairs, run all monitors and verify readiness; some ADAS functions require a road test to complete self-checks.

Compare live sensor data (e.g., radar object list, camera lane confidence) against known-good values to isolate intermittent faults.

Document pre- and post-repair DTCs and calibration status for warranty and liability.

CAN bus: differential pair (CAN-H, CAN-L), 120 Ω termination at each end; measure resistance with power off (~60 Ω across the bus).

CAN FD supports higher data rates and larger payloads; not all modules on a vehicle support FD-check topology.

Automotive Ethernet (100BASE-T1/1000BASE-T1) uses single twisted pair; connectors and cable routing are sensitive to damage.

Voltage drop testing is preferred over resistance testing for high-current sensor/actuator circuits.

Sensor supply voltages are typically 5 V or 12 V; a shorted or out-of-range supply sets a reference voltage DTC.

Ground integrity is critical; a poor ground can cause multiple sensor faults and communication errors.

Oscilloscope checks of CAN waveforms reveal shorts, opens, and termination issues that static tests miss.

After battery disconnect, some ADAS modules require initialization or calibration; follow OEM power-down/up sequences.

Network security: unauthorized modifications or aftermarket devices on the bus can cause ADAS faults; verify OEM configuration.

Frame/structural straightening can alter sensor mounting points; measure and document before and after repairs.

Windshield replacement: camera bracket location, glass thickness, and optical properties must match OEM; aftermarket glass may require recalibration or may not be compatible.

Bumper replacement: radar/lidar behind bumper requires correct material, thickness, and paint; metallic paint can attenuate radar.

Panel gap and flushness affect sensor aim; check against OEM specifications after body repairs.

Suspension and steering repairs change ride height and thrust angle; perform alignment before calibrating forward-facing sensors.

Airbag deployment often requires replacing or inspecting ADAS modules and performing post-repair diagnostics.

Corrosion protection and seam sealers must not obstruct sensor fields of view or drainage paths.

Post-repair, verify all ADAS features and perform required calibrations; document with before/after scan reports.

FMVSS 127 (US) mandates AEB and related performance; verify compliance-relevant repairs per OEM procedures.

NHTSA and OEM recall campaigns may include ADAS software updates; check VIN for open recalls before delivery.

High-voltage safety: ADAS work on electrified vehicles requires PPE and proper de-energization procedures.

Eye safety: never look directly into lidar or infrared emitters; use appropriate eye protection.

Customer handoff must explain feature limitations (weather, road conditions, driver responsibility) and any changes after repair.

Provide written documentation of calibrations, software versions, and test results; retain records per shop policy.

Test drive routes should include highway, urban, and low-light conditions as applicable to the features repaired.

Warn customers that ADAS is assistive, not autonomous; driver must remain attentive and in control.

Follow OEM position statements and repair procedures; deviations can affect safety and warranty.