Coding Alpina Sport software to a BMW equipped with the ZF 8HP70 automatic transmission can change the transmission’s shifting behavior, throttle response and overall driving character. The Alpina calibration is generally associated with quicker, more performance-oriented gear changes while retaining smooth operation during normal driving.
This procedure requires BMW E-Sys, suitable PSdZData files, a stable programming power supply and a reliable connection to the vehicle. Incorrect coding or an interrupted flash can cause serious vehicle faults, so preparation is essential.
Important: Always connect a suitable battery charger or power supply before starting. Do not attempt transmission programming with a weak battery or an unstable power source.
Required Equipment and Software
For the best compatibility, use:
- E-Sys 3.33 or newer
- The latest available PSdZData Full Edition
- A reliable ENET cable or approved BMW programming interface
- A stable battery charger or workshop power supply
- ISTA-D/Rheingold for fault-code diagnosis and deletion
- The correct BMW chassis type code
- The correct vehicle order, or FA/VO, for the intended Alpina software configuration
The Full Edition of PSdZData is very large, so ensure that sufficient storage space is available before installation.
Recommended Coding Conditions
Before beginning, observe the following precautions:
- Connect the vehicle to a stable charger.
- Switch off unnecessary electrical consumers.
- Do not open or close doors during programming.
- Do not disconnect the ENET cable.
- Do not shut down the laptop or allow it to enter sleep mode.
- Keep the ignition switched on for the entire procedure.
- Confirm that the vehicle battery voltage remains stable.
A programming interruption can leave the EGS—the electronic transmission control unit—in an incomplete or unusable state.
BMW Equipment Codes for Alpina Software
The following equipment codes may be used when preparing the vehicle order:
SA CodeDescription931Winter tires instead of summer tires ex works920Alpina without registration document9XAAlpina package
The exact FA/VO configuration depends on the vehicle, chassis and intended software integration. Equipment codes should only be added when they are appropriate for the vehicle and software configuration.
A complete list of BMW SA equipment codes can be found in a dedicated BMW SA-code reference.
Locating the Correct BMW Type Code
The correct type code is required when working with E-Sys. Examples include:
VehicleType CodeBMW F10 / F06XA71BMW F303E51
BMW chassis and type-code references are available through the BMW model archive and E-code database.
Vehicle Requirements
The vehicle should meet the following requirements before attempting the flash:
- Production date of 1211 or later
- Appropriate vehicle type code
- Compatible 8HP70 transmission hardware
- Suitable current vehicle integration level
- Correct EGS software target
- Stable battery voltage throughout the procedure
The production-date requirement should be interpreted according to BMW’s date format and the specific vehicle data in E-Sys. Always verify the vehicle’s FA and current I-Level before proceeding.
Adding the Alpina Equipment Codes to the FA
Before calculating or writing a modified FA, the new vehicle order must be checked.
Procedure
- Open E-Sys and connect to the vehicle.
- Read the existing FA from the vehicle.
- Add the required equipment codes.
- Right-click the FA.
- Select Calculate FP.
- Check whether E-Sys accepts the modified FA.
- If the FA is valid, save the new FA.
If the FA contains an invalid entry, E-Sys will display an error. For example, an incorrectly entered code such as DDD is not a valid FA entry and will be rejected.
Do not write an unverified FA to the vehicle. The FA must first be recalculated and validated successfully.
Selecting the Correct Integration Level
Select an I-Level of:
11-09-507 or higher
The available I-Level options depend on the installed PSdZData version and the software supported by the vehicle. The selected target must be compatible with the vehicle’s current integration level and EGS hardware.
E-Sys Flashing Procedure
The following procedure describes the general E-Sys workflow for preparing and programming the EGS.
1. Open Comfort Mode
Start E-Sys and select Comfort Mode.
2. Calculate the TAL
Open the TAL Calculation section.
3. Read the Vehicle
Click Read to load the vehicle data.
4. Save the FA
Select the FA folder and save the vehicle order as:
1.xml
Use a clear file location so the saved files can be found easily during the later TAL-processing stage.
5. Read the ECU List
Click Read ECU on the right side of the screen.
6. Select the Target Integration Level
Under SVT_SOLL, select the required:
- Build I-Level
- Target I-Level
Choose Total Flash where applicable.
7. Calculate and Save the SVT Target
Click Calculate, then save the resulting file as:
2.xml
8. Calculate and Save the TAL
In the TAL section below, click Calculate and save the resulting TAL file as:
3.xml
These XML files are used during the TAL-processing stage.
TAL Processing in Expert Mode
After creating the required files, switch E-Sys to Expert Mode.
1. Open TAL Processing
Select TAL Processing.
2. Load the TAL
Load the previously saved TAL file:
3.xml
3. Load the SVT Target
Under SVT Target, select:
2.xml
4. Read the Vehicle Order from the VCM
Under FA, click Read VCM.
5. Clear the Default Selections
Uncheck all selected programming options.
6. Select Only the EGS Flash Functions
For the EGS, select only:
- blFLASH
- swDEPLOY
- cdDEPLOY
Do not select programming operations for unrelated control units.
7. Start the Procedure
Click Start and confirm the programming operation when prompted.
The EGS programming process may take approximately three minutes, although the actual duration depends on the vehicle, computer, interface and current software configuration.
After the EGS Flash
Once the procedure has completed:
- Allow E-Sys to finish fully.
- Do not immediately disconnect the charger.
- Switch off the ignition according to the software instructions.
- Wait for the vehicle to enter its normal sleep or shutdown sequence.
- Connect to the vehicle using ISTA-D/Rheingold.
- Read the vehicle fault memory.
- Delete the EGS-related errors.
- Cycle the ignition and scan the vehicle again.
Some communication or voltage-related errors can be stored during programming. These should be assessed before deletion rather than cleared blindly.
Test Drive and Adaptation
After coding, the transmission may need time to relearn its shift adaptations. The initial drive should be gentle:
- Allow the transmission to warm up.
- Avoid full-throttle launches immediately after flashing.
- Check for warning lights or drivetrain messages.
- Confirm that all gears engage normally.
- Test reverse, manual mode and automatic mode.
- Monitor for harsh shifts, slipping or delayed engagement.
If abnormal behavior remains after adaptation, stop driving the vehicle aggressively and investigate the EGS software version, hardware compatibility, vehicle order and stored diagnostic faults.
Alpina EGS Software Overview
The following table summarizes the listed transmission families, drive configurations, gear counts and rated input torque.
ProductDrive TypeNumber of GearsInput Torque8HP45Standard / All-wheel drive8500 Nm8HP55AAll-wheel drive8650 Nm8HP70Standard / All-wheel drive8700 Nm8HP70HStandard / All-wheel drive8700 Nm8HP90Standard / All-wheel drive81,000 Nm8P70HStandard / All-wheel drive8650 Nm
The transmission family alone does not guarantee compatibility. Software, mechatronics, drivetrain layout, vehicle order and control-unit hardware must all match.
Important Compatibility Notes
An Alpina-style EGS flash should not be treated as a universal software upgrade. Before programming, verify:
- The exact BMW chassis
- The vehicle production date
- The transmission model
- Rear-wheel-drive or all-wheel-drive configuration
- EGS hardware identification
- Current and target I-Level
- FA/VO compatibility
- Availability of the required PSdZData files
Using an incorrect software target may result in gear-selection faults, drivetrain warnings, communication errors or a non-operational transmission controller.