The BMW G30 6WB digital instrument cluster can be coded to display a speed scale above 300 km/h. On compatible vehicles, the maximum display may reach 330 km/h, but the final result depends on the cluster version, encoder specifications and vehicle I-level.

This guide explains the main coding settings used in E-Sys, including the options for M Performance and Alpina-style displays.

Check the Encoder Specifications First

Before changing any coding values, confirm that the installed 6WB instrument cluster supports the required speed range. Not every display or encoder is designed to show the same maximum speed.

The G30 6WB cluster commonly supports a scale up to 330 km/h, but the available options can vary depending on the hardware and software installed in the vehicle.

Always save the original CAFD coding data before making changes. This gives you a safe backup if the display does not behave as expected.

Coding the DKOMBI2 Module

For clusters using DKOMBI2, the speedometer scaling option is usually found under the relevant display coding section.

To enable the higher speed range:

MPA_Enable → active

After coding, the display may show a speed scale extending up to 330 km/h, depending on the cluster hardware and software level.

Enabling the Alpina Tachostyle

For an Alpina-inspired instrument display, locate the following setting:

ALPIN(A)_ENABLE → active

This changes the tachometer and display appearance to the Alpina-style layout supported by the cluster.

The exact visual result can vary. Some vehicles may require a compatible I-level, software version or additional coding changes before the display works correctly.

Coding the DKOMBI4 Module

On vehicles equipped with DKOMBI4, navigate to:

3000 Display_Configuration
→ GLOBAL_LAYOUT_VARIANT

Choose the layout that matches your preferred display:

M       → m_gmbh
ALPIN(A) → alpin(a)

The m_gmbh setting provides an M-style layout, while alpin(a) enables the Alpina-style configuration when supported by the vehicle.

Important I-Level and Hardware Notes

BMW coding is not always identical across model years. The available parameters can change with the vehicle’s I-level, instrument cluster software and hardware revision.

If a setting is missing, produces an error or does not change the display, do not force the coding. The vehicle may require a compatible software level or a different parameter path.

Also remember that changing the visual speed scale does not increase the vehicle’s actual speed capability. Tyres, brakes, suspension, engine output and vehicle software must always match the car’s approved specifications.

Final Checks After Coding

After coding the 6WB cluster:

• Confirm that the speedometer starts and displays correctly.
• Check warning lights and driver-assistance information.
• Verify that the selected layout remains active after restarting the vehicle.
• Test the display only in a safe and legal environment.
• Keep the original coding backup for future restoration.

A correctly configured G30 6WB cluster can give the dashboard a sharper, more performance-focused appearance. However, hardware compatibility and accurate coding matter more than simply selecting a higher speed value.

For the cleanest result, use the correct E-Sys target, confirm the I-level and check the encoder specifications before changing DKOMBI2 or DKOMBI4.

Note: Vehicle coding should be carried out by someone familiar with BMW diagnostic systems. Keep all displayed speed information accurate and comply with local vehicle regulations.