Tuning Wiki
Applies to

Check the hardware and software limits stated in this article.

A changed throttle response or unstable idle on a Simos 9.1 car can follow a repair, an adaptation issue or a separate air, fuel or electrical fault. Establish which before changing the calibration. This guide uses the documented naturally aspirated 1.2-litre BXV application and product-specific diagnostic guidance; another engine or software version may use different procedures.

Documented 1.2 MPI example

The SEAT Córdoba/Ibiza 1.2-litre workshop manual, edition March 2011, identifies the BXV 1.2-litre 12-valve engine with Simos 9.1 in its technical-data table. Its component overview includes throttle control unit J338, manifold-pressure sender G71 combined with intake-temperature sender G42, engine-speed sender G28 and knock sensor G61. These are the equipment and identifiers shown for that example, not a pinout or a universal fitment list.

The manual's J338 checking procedure says the throttle must be clean and undamaged and, for its described component check, coolant must be at least 80 °C. Those are prerequisites for that particular test, not a universal prerequisite for every basic-setting procedure. Diagnose the actual engine using its current workshop information.

Throttle alignment and a failed basic setting

The SEAT manual says a replacement J338 must be adapted to the engine ECU. Separately, Ross-Tech's throttle-body alignment guidance explains that different VW/Audi diagnostic protocols and controller types use different basic-setting interfaces and that alignment may also be needed following certain cleaning, disconnection or replacement work. Its general examples are not a claim that every Simos 9.1 supports the same group number or that every battery disconnection requires an alignment.

Use the vehicle-specific diagnostic procedure to check fault memory and prerequisites, ensure adequate stable supply voltage and a mechanically free, clean throttle, then perform the specified alignment if applicable. Follow the tool's instructions for ignition and accelerator state and record the final result. Do not assume that a procedure which started has completed successfully. The independent Simos 9.1 CAN diagnostic listing gives a tool-specific example of an adaptation result and warns that erasing learned values can affect other adapted actuators; do not indiscriminately reset adaptations.

Ross-Tech lists sticking or inability to close, wiring issues, and an alignment not performed among possible lines of investigation for throttle basic-setting faults. These generic diagnostic suggestions are not specific proof of a failed J338 on the BXV. Save full fault descriptions and freeze-frame data, check the applicable supply and wiring, and use the guided tests rather than replacing a component solely from a code. P1559 reference; P1581 reference.

Reviewing a response or idle complaint

  1. Record engine and ECU identifiers, software version, recent work, fault codes, fuel and modifications. Identify whether the concern began after throttle cleaning, a replacement, a wiring repair or a calibration change.
  2. Check for intake leaks, obstructed or binding throttle, connector and wiring damage, ignition faults, and fuel-delivery problems under the current service procedure. An alignment does not repair an air leak or faulty actuator.
  3. Where the actual logger supports them, capture engine speed, accelerator position, throttle command and feedback, manifold pressure, intake and coolant temperatures, lambda feedback and fuel trims. Compare warm, repeatable idle and light-load conditions; verify channel units and whether each is commanded, measured or calculated.
  4. If pedal input changes but the throttle response differs from expectation, compare command and actual position with stored faults and operating conditions. A commanded reduction and a throttle failing to follow a command are different observations; neither alone identifies the cause.
  5. After a repair or correctly completed basic setting, repeat the same observations. The cited sources do not identify a software-specific torque or pedal map, so they do not justify copying map addresses or target values from another Simos file.

Example: reduced throttle during a loaded pull

In an HP Academy discussion, an owner describes a 2006 Fox 1.2 with Simos 9.1 and reports a throttle angle near 45% under high load, checked visually as well as through OBD. The post does not establish that the calibration caused a power loss or identify the ECU's active control mode. A respondent unfamiliar with this ECU suggests torque control or a protective intervention as possibilities and asks about lambda; these are hypotheses, not a diagnosis or verified Simos 9.1 map sequence.

For a comparable complaint, first verify the pedal, throttle command and feedback definitions and their angular reference, and review fault memory, temperature, load and lambda alongside them. A commanded restriction and an actuator that cannot follow its command call for different investigations. Use comparable baseline tests and the correct diagnostic procedure; do not assume the cause is a torque limiter or change a calibration from the throttle percentage alone.

Sources

Continue the conversation

If this topic interests you, consider joining the following forums. They host material referenced in this article.