Trailing throttle, fuel cut and restart
During suitable overrun conditions, deceleration fuel cut can stop fuel injection; fuel must resume as the operating state changes or the engine approaches idle. In the reference below, PU denotes trailing throttle and PUC denotes trailing-throttle fuel cut. Being in PU, or having an enabled transition, does not alone prove the injectors are off. A rev-limit cut, shift intervention, misfire or safety torque intervention is a separate possible cause of interrupted torque.
These stock-related calibration examples come from the community SC8S5031_C_OEM Simos 18.1 ENOS reference. Confirm ECU, software, transmission, gear encoding, definition, units, selectors, hysteresis and other state conditions in the actual file. A listed threshold is not the complete set of entry or exit conditions, and bracketed array names do not establish which element is active.
Entry thresholds and hysteresis
ip_n_min_puc[3]is a PUC engine-speed threshold in rpm versus coolant temperaturetcoandgear.ip_n_min_puc_eco[3]is the efficiency-mode counterpart. The reference describes other offsets and gearbox selection; it also notes an air-conditioning-related offset.id_n_hys_max_puc[3]andid_n_hys_min_puc[3]are gear-indexed engine-speed hysteresis values.c_t_hys_pucis a timer used in the hysteresis strategy. Their purpose includes preventing rapid repeated transitions; their units and exact application should be verified against the matching software.id_t_min_puis the minimum time in PU, in seconds, indexed by rpm and gear. It is not the minimum time spent in fuel cut.ip_n_min_puc_ofsis a speed-threshold offset involving engine-speed gradient and gear, not an independent full DFCO target.
Clutch and transition cases: The same ENOS application reference describes ip_t_min_pu_cs[1] as minimum PU time for a manual transmission with the clutch pressed, in seconds versus engine speed and predicted cylinder air mass; ip_t_min_pu_cs_gear_act is a separate clutch-pressed minimum PU-time map versus speed and active gear. The first map’s copied functional-description line is inconsistent with its heading and axes. These are conditional PU-state timing examples, not universal fuel-cut delays; establish the selected path and clutch and gear signals. The engine-gradient axis referenced by ip_n_min_puc_ofs is marked NO_INPUT_QUANTITY in the extraction, so verify its actual runtime input.
The same ENOS reference lists id_conf_ch_puc_inh as a gear-indexed configuration for inhibiting PUC during catalyst heating, and c_t_hys_puc_st as a post-start hysteresis timer. They help explain why the same lift-off may behave differently during warm-up; preserve the active safeguards and confirm the actual conditions.
The ENOS runtime reference lists n_min_puc, n_hys_puc, t_pu, t_puc, lv_pu_tran_puc_ena and lv_puc_inh_temp_cat. These are measurements or state/transition indicators, not maps; a transition enable differs from actual PUC state and injection inhibition. Check lv_puc and injection status if exposed by the matching logger.
Sequential cut and return of fuel
The separate TQDR sequential-cut parameters identify id_fcut_pu_puc_ena_gear and id_fcut_pu_puc_ena_maf as conditions for a sequential PU-to-PUC method, using rpm with gear or predicted cylinder air mass respectively. They do not establish a global fuel-cut enable or the complete entry threshold.
In the FMSP fuel-reactivation reference:
ip_fac_ti_reac_t_puc[1]is a reactivation correction factor against time in fuel cutt_pucin seconds.ip_fac_ti_ris[1]andip_fac_ti_rpl[1]are soft and hard reactivation correction maps. Their published axes include coolant and a reactivation-cycle axis markedNO_INPUT_QUANTITY; confirm indexing in the target definition.ip_fac_ti_reac_cor[1]corrects reactivation against engine rpm and basic fuel massmff_bas.ip_tps_grd_bol_aerelates to selection of soft or hard fuel-feed reactivation. These are restart controls, not PUC entry thresholds.
cycnr_reac[3], state_ti_reac and lv_inf are example runtime measurements from that reference. Compare actual injection resumption with idle target and torque/air response; a transient stumble after fuel returns may involve several paths, including wall-film modelling and fuel delivery.
Overrun sounds and diagnostics
Normal fuel cut should not be assumed to be a crackle strategy. The simos.app Main Patch describes its own settings acting while impulse combustion is active, subject to documented overrun, rpm and temperature conditions. Those patch labels and semantics do not define every factory or aftermarket PUC event. See the separate pops and bangs and crackle tuning guides.
For a repeatable lift-off and return to idle, log pedal, throttle, engine and wheel speed, gear/clutch, coolant, actual and requested torque, injector pulse/inhibition status, PUC and transition states, idle target, lambda and fault codes where available. Compare entry, time in cut and resumption rather than relying on an exhaust-sensor reading alone; fresh air in the exhaust during fuel cut can make lambda appear lean. Investigate leaks, throttle/air modelling and mechanical or fuel faults before attributing a stall to the cutoff calibration. Verify changes in a controlled setting with suitable engine and drivetrain protection.
In an MHH Auto Simos 18 discussion, a Golf R owner reported that an overrun sound calibration behaved differently at a standstill and asked about fuel-cut delay. The indexed discussion does not establish a cause or verified fix. Check vehicle speed, PU/PUC state, active impulse-combustion conditions and injection status separately; the absence of a sound at a standstill does not establish which condition blocked it.
Related: acceleration enrichment · idle control · throttle control · torque model · rev limiter. References reviewed 17 November 2026.
For driven-wheel slip during overrun and MSR request/monitoring fields, see Simos 18 engine drag torque and MSR control.