Identify the fitted front sensor
ME7.5 is not synonymous with wideband feedback. NefMoto's ATW discussion identifies a narrowband ME7.5 application; another ECU compatibility discussion describes narrowband and wideband ME7.5 examples. These are application reports, not a rule that identifies every ECU by engine code, flash size or suffix. Confirm the ECU part and software, sensor part number, vehicle wiring and control strategy.
A switching narrowband sensor is most useful around stoichiometric mixture. A wideband sensor and its matched controller can report mixture across a wider range, but measurement does not prove the ECU is using that signal for closed-loop correction in every state. Bosch's lambda-sensor overview describes the two sensing approaches. Confirm the operating range, readiness, bank and final lambda request.
Measurement is not automatically ECU feedback
A separate wideband gauge or logger can provide an additional measurement without changing a stock ECU's sensor input or feedback strategy. Conversely, installing a wideband sensor in place of a switching sensor does not by itself provide the correct controller hardware, heater control, signal processing or software. Bosch Motorsport describes the controlled pump current and sensor interface of its Lambdatronic LT4; that aftermarket controller is an example of the interface requirement, not a description of a particular factory ME7 circuit.
Identify the sensor and controller combination specified for the exact ECU or external controller. LSU sensor generations, connectors, heater strategy, calibration and outputs are not interchangeable merely because both devices are called wideband. Keep an external measurement's sensor location, calibration and transport delay with the log. The post-catalyst sensor has a different diagnostic role and should not be assumed to substitute for the front control sensor.
Conversion is a system change
A conversion can involve the ECU hardware, software, sensor, vehicle harness and other equipment differences. In one NefMoto ME7.5 conversion, the owner observed a live mixture display but then reported a P0130 fault and loss of closed-loop operation; they later reported improvement after correcting an omitted sensor connection. Earlier replies in that thread had offered conflicting wiring advice. This is a single reported repair, not a pinout or proof that another P0130 has the same cause.
Use the wiring and diagnostic information for the source and destination ECUs, the actual sensor and the vehicle. A running engine or a plausible displayed value does not by itself verify sensor readiness, heater control, diagnosis, mixture regulation or all operating states. Preserve diagnostic and protection functions and address reported faults instead of hiding them.
Check tables and operating points when software changes
In a 1.8T narrowband-to-wideband discussion, an owner reported different KFMIRL dimensions in the two files they were comparing. That does not establish the dimensions of all narrowband or wideband software. A table copied between files can have different axes, scaling, sensor inputs or associated maps. Verify each definition and the hardware, re-evaluate interpolation and related torque, fueling and ignition functions, and validate with appropriate logging.
Continue with ME7 map names and definition checks, map axes and torque-model consistency, lambda-control state during boost and misfire and lean lambda log diagnosis. The wiki has not independently tested the cited conversions.