Tuning Wiki

This is a historical revision. Read the current page or return to its history.

Page organisation in this revision
Page type
Reference hub
Subject
Engine ECU
Parent
Simos
Applies to
No ECU-specific applicability
Tool groups
None
Manufacturers
None

Continental Simos 12 is a petrol engine-management family used on examples of the Volkswagen Group's third-generation 1.8 and 2.0 TSI/TFSI engines. Simos 12.1 and 12.2 are variants named in tool and definition listings. Identify the actual ECU and software before choosing a definition, programming procedure or tuning file: neither engine family nor vehicle badge alone establishes the installed controller.

Applications and identification

Audi's eSelf-Study Programme 920243 identifies Simos 12 on the 1.8 TFSI CNSB and the 2.0 TFSI CNTA and CYFB examples. It gives the ECU family without a 12.1 or 12.2 suffix. SEAT's Self-Study Programme 158 describes Simos 12 control of a third-generation 1.8 TSI with direct and port injection. Those documents describe particular engine specifications and markets, not every ECU fitted to each engine code.

As examples of tool-supplier listings, Alientech's vehicle list names a 2014 Audi A3 Sedan 1.8 TFSI CJSA with Simos 12.1, and a 2012 Volkswagen Beetle Cabriolet 2.0 TSI CESA with Simos 12.2. Such entries describe coverage offered by that product and are not an exhaustive fitment list. Compare the ECU label and diagnostic identification, part number, hardware number, software version and calibration or EPK with the actual tool and definition. Alientech vehicle list; Powergate vehicle list.

Volkswagen’s June 2015 Golf maintenance manual, engine overview, lists the Golf 5G1 2.0-litre CHHA example as Simos 12.1, with 169 kW at 4,200–6,000 rpm and 350 Nm at 1,500–4,000 rpm. This is a manufacturer table for the documented configuration, not evidence that every CHHA car has that ECU or that a modified vehicle should reach those outputs. The table does not give the ECU calibration identifier; confirm the actual diagnostic identification and fuel requirements before comparison.

Charge control on the SEAT 1.8 TSI example

SEAT SSP 158 describes an electric charge-pressure actuator V465 moving the turbocharger wastegate, with position feedback G581. The control unit regulates charge pressure to meet the torque request using accelerator and engine-speed inputs, with correction inputs including coolant temperature, intake-manifold information and ambient pressure. It monitors charge pressure using G31 and the actuator position using G581. If requested and actual pressure differ, the cause may lie in the request, actuator, air system, sensor or an intervention; the discrepancy alone does not identify which one.

That programme also describes the cooling and oil-management systems. Sensor and actuator functions, substitutions and available diagnostic channels should be checked against the actual installation and current workshop documentation. The self-study text is a description of operation, not a repair procedure. SEAT SSP 158, charge-pressure regulation.

For a focused logging and diagnostic workflow, see Simos 12 1.8 TSI wastegate and recirculation diagnosis, including the distinction between V465 and N249.

Direct and port injection are application dependent

The 1.8 TSI in SEAT SSP 158 has both direct injection (FSI) and intake-port injection (MPI). For the installation described, the ECU selects FSI or MPI according to operating state and coolant temperature; the two systems are used separately in that description. SEAT also documents low-pressure sender G410 and high-pressure sender G247 and fallback modes when their signals are lost. These behaviours apply to its documented dual-injection system; check actual equipment and diagnostic information before applying them to another vehicle.

Audi SSP 920243, by contrast, identifies its North American CNSB, CNTA and CYFB examples as having direct injectors without intake-manifold injectors. Therefore an EA888 or Simos 12 label alone does not establish whether port injection is fitted or which injection-mode strategy applies. Audi SSP 920243, engine overview.

For the SEAT example's FSI/MPI selection, sensor fallbacks and diagnostic context, see Simos 12 1.8 TSI direct and port injection diagnosis.

Calibration and diagnosis

Record the engine, ECU variant, hardware and software IDs, calibration, transmission, fuel and modifications. Establish a healthy baseline and identify the source of the file being edited: a physical read, a virtual read supplied by a service, and a calibration-only file are not necessarily equivalent recovery data. Match definitions, axes, scaling and units to that software before changing a map. A plausible name or shape is not proof of a map's function.

At comparable operating conditions, use channels supported by the actual ECU and logger to review requested and permitted torque or load, charge pressure target and actual, throttle, wastegate command and position where available, lambda target and actual, fuel pressure, ignition timing and knock correction, temperatures and intervention flags. Confirm which values are measured or calculated, whether pressure is absolute or relative, and the logger's units and sampling rate. A request that is limited and a request that is not achieved lead to different diagnostic checks.

TuningBot's Simos 12 identification and calibration guide discusses file provenance, interacting torque, ignition and lambda functions, and investigating a modified file that produces no measurable gain. It is general tuning guidance, not a software-specific map definition or a validated recipe. Reference ignition used by a torque model must not automatically be assumed to be commanded ignition timing; identify the function on the particular calibration. Preserve relevant protections and investigate faults and hardware limits before changing targets.

For a specific 12.1 file example and a request-to-result workflow, see Simos 12.1 software-specific torque and load calibration review.

Clutch load and the shape of a tune

A 2014 reproduction of APR’s 1.8 TSI MQB announcement identifies its example as Simos 12 and describes a lower-torque version intended to reduce the chance of slipping a stock manual clutch. APR says it caps low-speed torque while retaining the same peak horsepower as its standard Stage I product. This is the supplier’s statement about its own historical software and test context, not proof that the two versions are interchangeable, produce the same complete curve, or suit every clutch, gearbox or ECU software revision.

It illustrates why peak power alone does not describe the torque demanded of the drivetrain throughout the rev range: power depends on both torque and engine speed. Record the actual transmission, clutch condition, fuel, hardware and calibration identification, and compare torque and power curves at the same engine speeds using suitable measured data. An ECU-reported torque value is an estimate rather than direct measurement of clutch load. A lower requested torque or a supplier’s peak claim does not guarantee that a worn or modified clutch will hold.

Examples of software-specific definitions

The simos.app definition catalogue indexes individual software identifiers, known boxcodes and patch names. For example, its SC1CC5 page labels the definition Simos 12.1 and lists boxcode 8V0906259 with software 0006. The same page indexes an Easy Wastegate patch, Flex Fuel patch, HSL and Main Patch Mapswitch for SC1CC5. Its SC2EB0 page labels the definition Simos 12.2 and lists 06K906070AA with software 8051, 8098 and 9347; it indexes HSL and Main Patch Mapswitch for SC2EB0.

These are vendor catalogue examples, not factory features or proven vehicle fitments. The supplier says its boxcode and software combinations were matched from BIN filenames and the identifier must be checked in the loaded file. Patch entries and their version numbers apply to the named software and product; they do not establish interchangeable patch behaviour, map functions, safe settings, or write access for another file or ECU. A definition count is not proof that each parameter has been independently validated. Check the exact file and the supplier's compatibility procedure.

A separate Auto-Remap listing for Simos 12.2 calibration 06K906070AB 9344 labels examples including standard-condition torque request, clutch-protection torque limiter, requested engine load, turbo-pressure limiter, wastegate duty cycle, rail pressure and requested lambda. The publicly visible listing supplies names only; it says sizes, axes and positions are in the separately sold export. These are the seller’s labels for this specific file, not independently validated map identities or evidence that another software version has the same definitions.

12.2 file-format and identity example

A public Simos 12.2 directory lists 06K906070F_6865.bin, a JSON sidecar and a WinOLS .kp file labelled SC200G5100000. The sidecar itself names that BIN, describes the ECU as Simos 12.2 and associates it with software string SC200G5100000 and version 6865. This records what the sidecar claims; its provenance, accuracy, usage rights and relationship to the map pack are unverified. A matching name is a lead, not validation of the contents or permission to use them.

The sidecar states a file size of 3,801,088 bytes. A separate commercial catalogue lists the same identifier combination with a 4,194,304-byte file and named reading tools. The different stated sizes do not identify which memory regions either contains or prove a fault; formats and operations can differ. Before relying on a file, confirm its exact ECU identity, data scope and compatibility with the particular reading and writing tool, and retain a recoverable original from the actual vehicle.

For torque request, transmission-monitoring and protection labels from a separate Simos 12.2 C30 definition, see Simos 12.2 C30 torque and protection definition reference. Its file identity and vehicle applicability remain unverified.

Definitions, tools and recovery

SMS-Soft’s ChipTuningPRO Simos 12.x module page provides a second, product-specific editing reference. It describes a third-party module by Vladimir Kulikov for selected 1.8 and 2.0 TFSI software, naming versions including CASC1C58, CASC1CC5 and CASC2G70. The publisher says more than 850 base calibrations are available for modification and that the module calculates checksums when saving a file. Its support list is a software-coverage statement, not proof that every listed map is verified, that all identifiers use the same layout, or that the editor can read or flash the ECU. Confirm the exact identifier, file format and current module coverage with the provider; a calculated checksum does not validate the calibration or supply a recovery read.

The simos.app definitions index lists Simos 12.1 and 12.2 definitions by identifiers. The product's compatibility page describes Mode 0x22 logging, fault-code workflows and supported factory updates, but says custom CAL and full BIN flashing are not supported. Its iOS release notes separately describe auto, full and CAL flashing without unlock for Simos 12.1/12.2; the listing also refers to stock files or pre-unlocked ECUs. The publisher's descriptions therefore do not settle custom-file support for a specific ECU and app version. Confirm the exact operation and file type with the provider. These are statements about that product, not other tools; an editor definition does not itself establish read or write support.

Tool capabilities differ even for the same family. BitBox’s Simos 12.X module (FID 401/406) describes a bench-CAN FullFlash read and calibration write with checksum correction for 12.1 and 12.2 without opening the ECU; it specifies a Scanmatik 2, 2 Pro or 3 and a GPT-capable bench adapter. By contrast, the PCMflash manual lists module 57 for 12.1/12.2 as virtual read, write and checksum check/correction. Its virtual-read procedure retrieves a matching file from a server after ECU identification, rather than reading the current flash contents. A flash read does not by itself establish that EEPROM or all recovery data was captured. Check the provider’s current coverage and instructions for the exact ECU and operation.

Connection diagrams and protocol-operation lists answer different questions. PCMflash's module 57 connection document includes a page labelled “SIMOS12/PCR2.1 BOOTLOADER”, with a separate Simos 12.X connector diagram and a Scanmatik 2/Pro/3 requirement. The page provides a connection diagram, but does not itself specify which flash or EEPROM operations are supported for a particular Simos 12 software version. This is separate from the virtual-read listing in its general manual; verify the exact operation and current requirements with PCMflash instead of inferring full-memory access from the word “bootloader”.

As another product-specific example, Microtronik's HexProg II Simos 12.2 page lists bench, boot and OBD connection modes, and explicitly lists virtual read and write under OBD details. It says its bench connection does not require opening the ECU, while its boot mode does. The page does not specify the contents of every mode's read, or prove coverage for every 12.2 calibration; confirm the provider's current instructions and recovery path for the identified ECU. Do not transfer a connector diagram or method between tools based on a common family name.

Confirm the chosen tool's current connection method and its support for the exact ECU, software and operation. Verify stable supply, file integrity and checksum handling, and a practical recovery method before writing. A corrected checksum cannot prove that a file matches the vehicle or that the calibration is safe. Keep the tool-specific original read and record what it contains; do not call a calibration-only or virtual file a full ECU backup.

See Simos 12 1.8 TSI coolant and piston cooling diagnosis for N493 and N522 control and interpreting related logs.

Sources