A forum community dedicated to BMW owners and enthusiasts. Come join the discussion about Bimmerfest events, production numbers, programming, performance, modifications, classifieds, troubleshooting, maintenance, and more! Bringing the BMW community together. 12) When you use NCSEXPER (with BMW Coding tools) you will load the profile 'FSW PSW MAN' (this is the only one that would work for me). 13) Your desktop should have Both BMW Coding tools and the NCS Expert programs there. If not they are in your programs (BMW Coding tools) and in C: NCSEXPER64 BIN NCSEXPER.exe for NCS Expert.
- Bmw Coding Options
- Bmw Coding App
- Diy Bmw Coding
- Bmw Enhanced Bluetooth Coding Tutorial (f30)
- Bmw Coding Tutorial
What is Coding?
It is a process utilized by BMW, which groups system specific operating requirements (Data) together and then assigns a label/code to each of these groups of data. The various groups of data are all pre-loaded into system specific 'codable' control modules, along with a basic set of operating instructions (Program).
There are various types of operating requirements such as; O2 sensors, emissions controls, fuel type, Manual or Auto transmission.
The procedure of assigning one specifically labeled group of data to the operating program of a specific control module/component is referred to as 'coding'. Coding allows a specific set of data already present in the module to be selected.
A 'codable' control module has a basic operating program already installed along with several specific variations of operating data. The coding process allows a specific set of operating data to be assigned to the basic operating program of that module/component, with respect to its specific application.
Coding can be performed for some systems/components via ISTA/P or the older DIS/Plus/GT1/SSS device. By entering a variant code via the device, selecting customer specific operational settings from a list of available features (VKM) or automatically by selecting a specific coding process.
Note: Codable control modules/components are system specific, which means that not all control modules are codable.
What is Programming?
It is a process utilized by BMW to load application/system specific operating instructions. Programming loads control functions instructions into a specific control module.
(Program) into a module/component which already has the systems operating requirements (Data) installed, plus it can be used as a means of updating data and operating instructions previously installed in a control module. Basic programmable control modules have a pre-defined set of operating data already installed which allows the module to be fairly generic until a specific operational program is installed.
The ability to program a module is limited to the number of times it has already been programmed and the hardware version of the control module itself.
What is I-level (or Integration Level)?
The ECU's in a BMW are not meant to be updated individually, rather as a collection which BMW tested and knows all work fine together. The collective version number of all programmed ECU's is called the I-level, or Integration level (German: I-stufe). The term I-level was adopted by BMW around the year 2004 and applies only to lines which were in development/production in 2004 or after (E60, E70, E90, etc.).
The I-level is a set of numbers that looks like E89X-11-09-410. The first part represents the chassis group, which is followed by the year and month of the release and a build number for that release. So, E89X-11-09-410 would mean an E80/E90, 09/2011, version 410.
You will often see a set of two I-levels, something like E89X-05-10-026, E89X-11-09-410. In this case the first set is called the Factory I-level, or the level with which the car left the factory, and the second the Dealer Organization I-level, or the current version programmed by the dealer.
Tagged on: bmw encoding, bmw programming, E36, E39, E46, E60, E61, E63, E64, E65, E66, E67, E70, E71, E72, E81, E82, E84, E87, E88, E89, E90, E91, E92, E93, F01, F10BMW F30 coding manual:
bmw f series coding tool:
For coding only:BMW ENET cable is ok
There are basically two ways to get the ENET cable. You can buy a complete cable, or you can simply build one.
DIY an ENET cable BMW with the help of the how-to's (Google 'DIY enet cable'; it's easy to find guides you wan)- it's a piece of cake for you if you're equipped with technique. You can have a try and then decide to whether buy a complete one.
Don't spend too much on it- that is, just buy a cheap knock-off online:
I wouldn't recommend other sites, although they may work, problem is that they have not been confirmed working yet.
For coding & programming: you must have a BMW ICOM emulator (ICOM A2 or ICOM Next). Also, if you have a new BMW or wanna use the tool for future cars, you should have bmw icom.
bmw f series coding software:
bmw e-sys software download:
bmw f30 coding software download: E sys 3.24.5 worked 100%
Note: E-sys software is used for bmw f series coding only; if you want to have ECU programming, please you should have Ista-p.
Bmw icom ista-p latest version 07.2017: bmw programming
bmw f series coding software install:
Usually, Windows system is your first option. But now, Mac OX also be the one you can have a try. This is how to install BMW E sys on Macbook pro:
bmw f30 coding cheat sheet:
FA Codes (VO Coding)
Activate Active High Beam Assistant (Anti-Dazzle)
Activate Variable Light Distribution
Activate Enhanced Bluetooth
Activate iDrive Office
Activate Sport Automatic Transmission
CAFD Codes (FDL Coding)
Angel LED Brightness (Xenon Headlamps or LED Headlamps required)
Cornering Lights (Fog Lamps) & Fog Lamp Welcome Lights
Day-Running Lights & Activate Rear Fog Lamps
Assorted Lighting Features
LED Replacement Turn Signal Bulbs Activation
Instrument Cluster
Safety Features & Precautions
Vehicle Drivetrain Features, Sport Features, & Active Sound Design
General Locking/Window Features & Convenience Features
iDrive Features
Video In Motion & Playback Features, Owner's Manual in Motion, and Camera in Motion
Advanced Real-Time Traffic Information Activation
Heads-Up Display
BMW Live Enabling
Active Spoiler (F34 3-Series GT only)
Seat Heating Temperature Levels/Memory Seats
Headlamp Washers Configuration
CODES THAT NEED TO BE TESTED OR CHECKED
INEFFECTIVE OR UNAVAILABLE CODES
f30 coding cheat sheet 2016 download:
bmw f30 ECU coding list:
AAG – Trailer Hitch Module
ACC – Active Cruise Control
ACSM – Advanced Crash and Safety Management
AHM – Trailer module
AMP – Amplifier
AMPH – HiFi Amplifier
AMP_TOPHB – Top HiFi Amplifier/System
AMP – Amplifier/System
AMP_TOPHB – Top HiFi Amplifier/System
ASA – Active steering
ASD – Active Sound
BDC – Body Domain Controller (ZGW, FEM, REM, SZL, IHKA, TCB, CAS, JBBF Combined)
CAS – Car Access System
CID – Central Information Display
CMB_ECALL – Combox Emergency Caller
CMB_MEDIA – Combox Media
CVM – Soft top module (Convertable Top)
DKOMBI – MFID Instrument cluster (6WB)
DDE – Digiatl Diesel Electronics
DME – Digital Motor Electronics
DSC – Dynamic Stability Control
DWA – Immobilizer (Alarm)
Bmw Coding Options
DVDC – DVD Changer
EGS – Electronic Transmission Control Unit
EHA – Electronic ride-height control
EHC – Electronic ride-height control
EKPM – Electronic fuel pump control
EMF – Electromechanical parking brake
EPS – Electronic power steering
FEM_BODY – Front electronics module (ZGW, FRM, CAS, and JBBF Combined)
FEM_GW – Front electronics module gateway
FKA – Rear-cabin automatic A/C
FLA – Automatic High Beam Camera Only
FRM – Footwell module (Lighting)
FRR – Active cruise control
FZD – Function unit roof
GWS – Gear selection switch
HKFM – Rear Lift-Lid (Trunk)
HKL – Rear Lift-Lid (Trunk)
HU_ENTRY – Head Unit Entry Level (no iDrive System)
HU_CHAMP (Head Unit CIC Mid) (iDrive system)
HU_CIC – Head Unit CIC High (iDrive system)
HU_NBT – Head Unit NBT (iDrive system)
HC2 – Lane Change Warning
HUD – Heads-Up Display
ICM_QL – Integrated Chassis Management
ICM_V – Integrated Chassis Management Vertical (Vertical dynamics management)
Bmw Coding App
IHKA – Integrated automatic heating/air conditioning system
JBBF – Junction box electronics
JBE – Junction box electronics
KAFAS – Cameras System (LDW, AHB, SLI)
KOMBI – Instrument cluster
LHM – LED Headlights main light modules (fan and LEDs for the cornering light, low-beam and high-beam
headlights).
NIVI – Night Vision Camera
PDC – Park distance control
PMA2 – Parking Assist
RDC – Tyre pressure control
REM – Rear Electronics Module
RSE – Rear Seat Entertainment
Diy Bmw Coding
SM – Seat module / Seat Memory
SME – Accumulator-management electronics
SMBF – Seat module / Seat Memory Passenger
SZL_LWS – Steering column control unit
SVT – Servotronic
TCB – Telematics Communications Box (BMW Assist)
TMS – LED Headlights (stepper motors for the Adaptive LED Headlights and LEDs for the side marker light,
the positioning light and the turn indicator)
TRSVC -All around view camera
TBX – iDrive Controller Touch Handwriting Module
VDM – Vertical dynamics Management
ZBE – iDrive Controller
ZGW – Central gateway module
f30 coding manual:
The steps of BMW F series ECU flash…. Just remember to identify the dependencies and select appropriately in step 15 in the below procedure.
When flashing involves ZGW it is widely said that the ZGW module should be updated BEFORE other
modules. The TAL (transaction list) generated by E-Sys should take care of this. But if you want, you could
flash the ZGW all by itself and then restart and do the rest. The steps remain the same.
Flashing all modules at once is also as easy as flashing individual modules. Just select all the modules in step
15 (still blFlash, swDeploy, cdDeploy, and ibaDeploy columns)
HU_CIC Depends (PreRequisites) on: 38 + 14 (BOTH ZGW)
KOMBI Depends on: 38 + 10 + 14 + 53 + 57 (ZGW + HU_CIC + ZGW + CMB_MEDIA + HU_CIC)
CMB_MEDIA Depends on: 57 (HU_CIC)
ZGW does not have dependencies.
How to identify dependencies in E-SYS interface:
Open TAL IN TAL Editor, and it will show you under ECU (TalLine_ID) if it has any PreRequisite ECU (TalLine_ID's).
As you can see here, TalLine_ID=13 (Kombi) has a PreRequisite of TalLine_ID=11 (HU_CHAMP):
HU_CIC:
KOMBI:
CMB_MEDIA:
ZGW:
Here are the basic steps:
Go to Comfort Mode => TAL-Calculating
– Read and Save FA
– Activate FA
– Read and Save SVT Actual as SVT_ist
– Create an SVT Target
Under KIS/SVT Target Calculation Strategy, select Complete Flash
Select I-Step (shipm.) to match your original I-Level as read and shown in VCM I-Step (Shipment)
I-Step (target.) will be unselectable as it is fixed based on current PSdZData I-Level
Do a KIS/SVT Target Calculation and Save as SVT_soll
– Do a TAL Calculation and Save as SVT_tal
Go to Expert Mode => TAL-Processing
Load TAL (SVT_tal)
Load SVT Target (SVT_soll)
Select 'Read FA' button.
Check radio button for 'read VIN out of FA'
On ECU Tab, uncheck let top box in column 'All' (All checked boxes should toggle to unchecked)
On ID Base Row for Kombi, make check boxes in blFlash, swDeploy, cdDeploy, and ibaDeploy columns.
Press Check software availability
Press Start and it will proceed with processing TAL to flash Kombi with new firmware.
Please go on your reading for details.
- Connect external charger (at least 50AMPs, preferably 70AMPs) to the car battery. Connect laptop to power supply. This step is essential!
- Turn lamp switch to parking light – this will keep the ignition on beyond 20 minutes.
Turn light switch to Parking Lamp On – first position/stop to the right.
Please refer to Appendix B for further info regarding the light switch and the 20
minutes.
- Connect via 'Connection via Gateway URL'
In the Connection window, select the ‘Connection via gateway URL' instead of via VIN, and use the car's IP address with the default port number 6801.
Passed with flying colors
(else flashing ZGW will fail)
- Select Comfort Mode TAL Calculating
- Read and save FA
- Activate FA
- Read and save SVT Actual as 'SVT_ist'
- Create an SVT Target:
- Select Complete Flash
- Select I-Step (shipm.) to match vehicles shipment I-Step level
- Select Expert Mode VCM button
- On the right bottom box, select 'Master' tab
iii. In I-Steps box, click on 'Read' button.
- Integration Steps boxes above will be populated with the data. Note down the IStep
(Shipment).
- I-Step (target.) will be unselectable as it is fixed based on current PSdZData I-Level. Select
the appropriate level in I-Step (shipm.) as obtained in step above
- Do a KIS/SVT Target Calculation and Save as 'SVT_soll'
- Do a TAL Calculation and Save as 'SVT_tal'
- Go to Expert Mode TAL-Processing
- Load TAL [SVT_tal) created in step 8.e
- Load SVT Target ('SVT_soll') created in step 8.d
- Click the 'Read FA' button
this will result in the FA_aus_VCM.xml file:
- Check radio button for 'read VIN out of FA' and click the 'Read VIN' button
- On ECU Tab, uncheck let top box in column 'All' (All checked boxes should toggle to unchecked)
- On ID Base Row for HU_CIC, CMB_MEDIA, KOMBI and ZGW check the boxes in blFlash, swDeploy,
cdDeploy, and ibaDeploy (please see Appendix C) columns.
- Press Check software availability (this, among other, ensures that you have the correct PSdZdata
and the FULL version of them)
- Press Start and it will proceed with processing TAL to flash Kombi with new firmware
- Cross your fingers and watch it work
END. That's all above BMW F30 coding with BMW ENET E-sys software.
Bmw Enhanced Bluetooth Coding Tutorial (f30)
Credits to all contributors, esp. http://www.obdii365.com/