Ypsilon yeni nesil

Technical identity summary

Source variant count: 1 · Status: CURRENT

This page does not treat the same sales name as one vehicle across all years and markets. Rows below remain separated by source region and variant identity.

Ypsilon yeni nesil · Italy

Where should diagnosis start?

• Evaluate HV/12 V boundary, battery thermal management and energy flow together.
• Check charging, HV isolation, 12 V supply, thermal management and software state as separate evidence chains.

Exact OEM torque, pressure, capacity, pin or calibration values are not inferred from this normalized identity record; a verified service source is required for the exact vehicle application.

System architecture: what does this record indicate?

• On turbo-petrol architecture, load calculation, boost target/actual, lambda/fuel trim, ignition and knock control are compared in the same event window.
• ICE, 12 V, HV/48 V, DC-DC, motor-generator and thermal management are separate control layers; energy flow is aligned with the fault event.
• In an EV, HV battery/BMS, contactor-HVIL/isolation, inverter-motor, OBC/DC-DC, 12 V and cooling circuits are separate evidence branches.
• For DCT/DSG, TCU-mechatronics, K1/K2 clutches, actuator/line pressure and input/output speeds are evaluated together.

Freeze-frame and live-data package

• Freeze frame: first/last fault time, RPM, load, vehicle speed, system voltage, core temperatures and companion DTCs.
• Live data: calculated load, MAP/boost target-actual, throttle angle, lambda/O2, STFT/LTFT, ignition advance and knock retard.
• Electrified layer: SOC/SOH where available, cell delta, pack temperatures, HVIL/isolation, contactor permission, DC-DC output and 12 V voltage.
• Driveline: input/output speeds, commanded/actual ratio, clutch/TCC slip, fluid temperature, actuator/solenoid command and adaptations.

Measurement sequence

1. 1) Match vehicle/generation/market/powertrain/driveline identity to the source record; family name alone is not fitment evidence.
2. 2) Preserve freeze frame and companion DTCs before clearing; make the first-fault condition reproducible.
3. 3) Verify power/ground and network communication under load; do not decide from key-on static measurement alone.
4. 4) Compare commanded air/fuel/pressure with an independent physical result; separate sensor bias from real performance loss.
5. 5) Compare electronic command → hydraulic/actuator response → mechanical slip/ratio result at the same temperature and load.
6. 6) After repair, recreate the same load/temperature and verify DTC state, live-data deviation and user symptom together.

Root-cause discrimination matrix

• On lean/misfire/boost complaints, align fuel trim, lambda, ignition retard and boost deviation on one time base to separate air leak, fuel-delivery and ignition causes.
• For READY/charging faults, separate 12 V supply from the HV permission chain first; low 12 V can mimic contactor/HVIL/isolation faults.
• For battery performance, use cell delta, temperature spread and voltage deviation under load/charge instead of one SoH percentage alone.
• For DCT harshness/slip, separate TCU command from clutch slip and actuator/hydraulic response; adaptation result alone does not prove mechanical wear.

Connected technical centers

Engine Atlas · Transmission Atlas · DTC Academy · Recall

Market and generation variants

Ypsilon yeni nesil · Italy · 2024–