Tuning Wiki
Applies to

Check the hardware and software limits stated in this article.

The Main Patch Map Switch is a product-specific modification described for selected Simos 8.5 3.0 TFSI software. It adds selectable torque and ignition-offset settings. These are patch functions, not a description of stock Simos 8.5 behaviour or a universal calibration recipe.

Scope and identification

The publisher lists S85K30, S85L00, S85L10 and S85L20 as supported software identifiers. Identify the ECU hardware, boxcode, software identifier and calibration on the actual vehicle, and check current patch and tool compatibility for that exact file. The patch documentation is the source for the functions below; it does not establish that every ECU, market, transmission or flashing device supports them.

Slots, axes and torque limits

The guide describes two to five selectable slots. Each has torque-limit maps for manual and automatic/dual-clutch applications and a separate Efficiency-mode torque-limit map. The relevant map depends on the transmission and operating mode. The Efficiency map only acts if the corresponding stock Efficiency limit is enabled; the guide says it is disabled in stock S85L20. An edited map that is not active cannot explain a lack of change by itself.

According to the patch documentation, its torque-limit maps use the original axes. Each slot also has an rpm-versus-load spark-offset map using the stock basic-ignition axes. The offset is added to the stock basic angle; it is not a standalone final ignition map. The document describes the trim as applying to both banks and to rich and lean operation. Verify the actual file and patch version before treating a displayed value as an active map or measured ignition.

Slot selection can use assigned cruise-control or indicator controls, or follow configured drive-mode profiles. A tachometer indication can show the selected slot. Check the active slot and profile before comparing logs; a modified slot is not evidence that it was selected during a run. See the publisher's guide for its button and profile behaviour.

Checking the selected slot

For the documented patch, the publisher’s switching guide describes holding the assigned cruise-control button to open selection: the tachometer shows the current slot, UP and DOWN step through the available slots and SET confirms it. If no confirmation is made, the shown slot is committed after the configured selection window; the guide gives five seconds as the default when that setting is zero. The displayed tachometer position is the patch’s slot indication while selection is open, not a measurement of engine speed. An optional post-start indication can also show the active slot for a configured time.

The turn-signal switching option, when configured, is described for a stationary vehicle: the left-then-right sequence opens selection, then further lever inputs step between slots until the selection window commits the displayed choice. With drive-mode following enabled, the configured drive profile also selects the assigned slot. Check the exact patch version, button assignments, selection window and profile settings before comparing the effect of different calibrations; these controls do not establish which fuel or hardware a slot requires.

Overrun settings and launch setup

The patch guide describes a per-slot overrun switch plus duration and intensity settings. Duration scales the original impulse-combustion activation time; intensity scales its ignition angle. The publisher says the original engine-speed, temperature and coasting conditions still decide whether overrun operation occurs. These are features of this patch and do not mean that every slot change activates overrun. Review the currently selected slot, enable state and operating conditions when a setting has no apparent effect.

For its standing-launch feature, the guide describes three progressively stronger rotating cylinder-cut levels on the six-cylinder engine. The patch uses separate arming conditions including road speed, oil and coolant temperature and, on a supported dual-clutch car, reported hydraulic brake pressure. Its arming and cut settings are product-specific controls, not proof that a chosen setting is suitable for the vehicle. Verify the feature's actual engagement and limits with the publisher's instructions and appropriate logs.

Launch and knock indication

The guide describes optional launch control enabled per slot, with rpm, torque, ignition and cylinder-cut controls plus arming conditions. It states the feature is for supported manual and dual-clutch cars, and does not provide launch on torque-converter automatics or CVTs. It also describes an optional warning-lamp indication based on average or individual-cylinder knock-retard thresholds. A lamp indication is not a replacement for logging timing, individual-cylinder corrections and operating conditions. The warning itself is a patch feature, not proof that a stock ECU has the same function.

Fuel-cut and spark-cut strategies have different exhaust effects. The publisher notes that a spark-cut option can send unburned fuel to the exhaust and heat the catalytic converters. Select features only with the hardware and intended use understood; this page does not prescribe launch, ignition or crackle values.

Validation and programming

The guide describes a VIN-linked fingerprint: until set, or if it does not match, the listed modified torque, spark and optional features revert to stock. If a change appears inactive, verify the exact patch, slot, gearbox-specific map, drive mode and any relevant enable condition before changing calibration again. Compare requested and actual behaviour with appropriately defined logs; a torque ceiling is not itself a measurement of delivered torque.

The guide says applying or removing its patch needs a full flash, while later parameter changes are calibration-only. This is a description of that patch workflow, not a guarantee of support by every flashing tool. The publisher's iOS release notes and product documentation cover different ECU versions and file operations; confirm current capability for the exact ECU and file. Establish a suitable original read, checksum handling, stable supply and a supported recovery route before programming.

Sources