9.27.2018

BMW Coding App Bimmercode vs. Carly vs. BimmerLink

What's the difference between Bimmercode, Bimmerlink and Carly?

Which one is best?

Which one is easier to use?




The three apps I could find and ultimately am reviewing are Bimmercode, Bimmerlink and Carly BMW. Let's break down the price first:



Bimmercode
Vgate iCar 2 Mini WiFi OBD - $22.99
BimmerCode App - $29.99
BimmerLink App - $29.99
Total for setup = $82.97 (plus local taxes)


Vgate icar 2 is the cheapest option, better use Vgate iCar 3.0 BT and Vgate iCar Pro 4.0 Bluetooth which has higher transmission rate.

vgate-icar-2



vgate-icar-2-3.0



vgate-icar-4.0


Carly BMW
Carly BMW Gen 2 WiFi OBD (iPhone) - $88.55 (not the best price)
Carly BMW Pro App - $44.99
iDrive Coding Add On - $14.99
Service Reset Add On - $4.99
Battery Registration Add On - $9.99
Total for setup = $163.51 (plus local taxes)

carly-bmw-app-1



carly-bmw-app-2

carly-bmw-app-3

Note* Now you can use Carly for BMW Pro cracked without special connector. Use default Bluetooth or WiFi OBD II adapter. Get the most out of your BMW by keeping it healthy, personalized and connected.

carly-bmw-app-4

I will compare what the apps do not share in common (features only available in one app). I will give my final thoughts on each app and final verdict.

A key note is that buying BimmerCode and BimmerLink will land you at the same price as Carly BMW Pro + iDrive Coding Add on. $60 and the apps try to be identical. Both will code/diag. The Lite or Free versions of both apps are for testing compatibility only.

*If you are using an Android phone, your only choice is Carly BMW. The reviews today are based off the iPhone apps. Bimmercode is iPhone ONLY*


General: Bimmercode

bimmercode-app


Bimmercode is unique in the sense that it splits its features into two individual apps. Both apps use the same OBD connector so no need to worry about purchasing another device. The interface is clean and easy to use. Cost savings can be had if you ONLY want to code. The BimmerCode app, codes, and thats about it. Unlike Carly BMW it does offer an advanced setting which looks to closely match the ability of dealership scanner. The modules turn to German text and the list grows very very long. Unfortunately, I am no expert, and really can't comment on how well Expert mode works or its ability to compete with a full PC/Software based setup. More on Expert mode later.

General: BimmerLink

bimmerlink-app

The BimmerLink app does the Sensor Values, Dashboard Values, ASD, and Exhaust Flap. Its the services app. BimmerLink has no official website and BimmerCode's website is pretty much just a landing page for the app. The website offers no insight as to the future direction that the apps will be taking. Additionally, it only covers Fxx Series BMWs and above.

General: Carly BMW

carly-bmw-app


Carly BMW packs all of its features into a single app. Ability to do everything via the Carly branded OBD connector. The interface is also clean and easy to use. The punch to the face comes when you purchase the Pro version only to find out that you must dole out more cash for Add-On packs. While you do get lifetime updates to both the connectors firmware and any features/packs you already purchased, it's fair to assume that any NEW Add-Ons will cost you. Carly BMW offers several additional features that Bimmercode does not(Service reset, Battery Programming, Used Car Check, Etc).

Unlike BimmerCode's website, Carly BMW's is full featured. Providing manuals, feature lists, and a spot that shows current projects/status. Carly promises to continue to update the app and the project list supports this claim. It covers both Exx and Fxx Series BMW's and above.



What the Apps do the same:
Diagnostics: Both apps appear to do the same. However BimmerLink fails to sort or translate into English. Carly BMW takes quite awhile longer to scan for errors, but offers the benefits of being able to scan all or select a specific module/s for scanning.


Coding: I can't do a full side by side comparison of every single possible feature. Both company websites have the full coding lists separated out by BMW Model. They match what many of the "Remote Services" offer. They backup the current reading and then allow you to code what you like. This is done on a module by module basis. Each module controlling certain features. BimmerCode was a major let down, while claiming to offer full coding on my model, I was only able to access 4 modules. Carly BMW had no issues accessing and coding them. Here are some screenshots: (Using one Module on each app as a display)


Exhaust Flap: For models that have an exhaust flap that opens or closes based on how heavy your foot is, both apps provide the ability to manually open or close it. Device needs to remain plugged in and connected to your iPhone. BimmerLink reported this was not available for my car and Carly BMW did give me the option. No screenshots as it's really a ON/OFF toggle.

Parameters / Sensors & Dashboard:
Both apps allow you to add and then track certain sensor values. However, (again) BimmerLink fails to translate in English. Carly BMW while limiting you to 6 parameters, does translate for you. Here are some screenshots:


What the Apps don't do the same:
This section is going to lean heavily in Carly BMW's favor. For a price, Carly BMW can do alot more. Let's start with Bimmercodes app's unique features:

BimmerLink
ASD or Active Sound Design is essentially using the speakers to create noise that sounds like your engine. I could not find this option in Carly BMW. However, the option was not available for my car using BimmerLink. I would assume it's just an on off toggle. No screenshots.

BimmerCode
Offers Expert mode which could be golden for the more technical coders. Unfortunately I don't know enough to give an in-depth analysis of this feature. But it looks to be a way to adjust the core values on each setting. However, this list is limited to the modules you can access, which was only a few on my car. Here is a screenshot: (Using coding module from above)


Carly BMW
Used Car Check: Essentially scans your car for parts that track miles. It will then analyze the miles vs your odometer. While no tampering was found on my car, it is a curious and potentially useful feature when it comes time to buy another car. Here is a screenshot:


Service Reset:
Does exactly what it says. Offers a quick way to reset the iDrive service settings. Here is a screenshot:


Battery Reset / Programming: Does exactly what it says. Allows you to program in a new battery. At $10 this is extremely useful, even if you only replace the battery once while owning your car. That savings alone pays for the entire app.


DPF ($9.99): I did not purchase this option as I don't have a Diesel car.


OBD Functions: I did not run this function during testing, but I do hope it comes in handy when I replace those o2 sensors.

Final Thoughts:

For my 2011 F10 535i, Carly BMW is the clear winner. Its easier to use and offers alot more functions than Bimmercode does at this time(For a price). While I assumed that Bimmercode will continue to get better, Carly BMW has a full company backing it. I don't see Bimmercode surpassing Carly BMW at anytime in the future. Overall I was disappointed with Bimmercodes apps. While the interface is cleaner and a cheaper setup, the non English translation and lack of available codings really hurts. Granted newer Fxx series may offer greater compatibility with BimmerCode, I cannot personally recommend it at this time. I still wanted to write the review since Bimmercode is cheaper and may do enough for some people at a much lower costs, it's just not as polished.


Suggestion:

It really depends on what your budget is.The biggest issue I have with BimmerCode is that it lacked support for two of the 6 modules in my car. Carly BMW can code all 8. If you have the money, I would go with Carly BMW at this time. If you are looking for the cheapest possible route than BimmerCode is the way to go.
Vgate iCar Pro Bluetooth 4.0 OBDII scanner for Android & iOS

9.25.2018

BMW E-sys 3.33.0 Windows 32/64 bit Download FREE


(10-2018) Free download BMW E-sys v3.33.0 to work on Windows 32 bit or 64 bit:

BMW E-sys v3.33.0 download:
e-sys-3-33
E-Sys_Setup-3.33.0-53640_32bit.exe:
https://mega.nz/#!MlpzBYaZ!DVCzwIE-XxHNypbUxLir_GpXPzSSZstCtNwfV2PRYS4
e-sys-3-33-32-bit
E-Sys_Setup-3.33.0-53640_64bit.exe:
https://mega.nz/#!J4pByAjZ!oGIekxD182UoKaclg5QlSvMdvxD_DOiPC9UzJiX_Pds 
e-sys-3-33-64-bit
IMPORTANT:
E-sys v3.33.0 software is the newest but has NOT been tested yet.
You should try it on your own risk.
 
If you want get BMW E-sys with security and relief, there is a tested version for you: E-SYS 3.23.4 software:
http://www.obdii365.com/wholesale/bmw-enet-interface-cable-e-sys-icom-coding-f-series.html 100% tested with a lot of BMW F series for coding
 
 
E-sys 3.33.0 released notes:
 
Version:
E-sys 3.33.0
Psdz 5.07.01
Prodias: 3.4.0

System requirement:
Processor: Pentium 4-Techner with minimum 1GHz clock frequency
RAM: at least 512MB
Hardware interface: (CAN / FD, Ethernet, ...)
Java version (secured with): 1.8.0.121 64 bit
Operating system: Windows 7 64 bit
Driver for HW interfaces: see ProDiaS Release notes

Infos - Bitte beachten:
During the vehicle programming with E-Sys, no further applications should be excuted in parallel on the flash processor
This includes, in particular, background processes, such as the indexing service for desktop search or automatic defragmentation services
E-sys is current not supported under Windows 10. Workaround for display problems under Windows 10: E-sys.exe->Properties->Compatibility->Override behavior at high DPI scaling->Scaling performed by “System”

Quality Center (edited points):
14206 - certmanagement: failed to convert Json Response from CBB to internal PSdZObject
14421 - Error in seen in LOG after the import of an RSU container
14423 - FDL: Datentype yte isn’t checked
14570 - Mme-Type for Deltamap is unknown
14719 - Cermanagement: CSRs can only be read from ECU in Expert Mode
14835 - Certmanagement: Json-File is necessary although the XML-binding and SVT are located
14998 - E-sys : Load SVT file behaves differently with SVT-IST and SVT-Soll

Quality Center (open points):
12616 - Import error after KC update with RSU PDX template
14192 - Display Problems with E-sys on Windows 10
14232 - Import of corrupt containers
14382 - no OMITEC connection at E-sys 3.32.1/PSDZ 5.6.1
14770 - TAL Status Viewer: Flowchart is only displayed if filename starts with “TAL”
14954 - PSLZ created and stored TAL filters can not be loaded or edited in E-sys
12981 - Adding a own attribute at the xml-Namespace of a SVT-file
15012 - Faulty E-sys function - Create FA from short VIN
15024 - E-sys loggt User Name

Change requests and small changes:
CR3565 - Esys support for secure ECU model LSI
CR3566 - Esys support for centificate management 2021 and SEC-OC
CR3640 - Esys: SVT cannot be saved or opened with the special character “#” in the file name
CR3647 - Integration of the SVT update function into the module Tal generation
CR3681 - Esys - Adaptations resulting from modified TAL-Schema (IDR for ISTA)
CR3707 - Esys: new SVT scheme due to SFA/SecOc
KA3720 - For generated TAL files, Esys should determine the scheme version attribute from the version value of TAL xsd
CR3724 - Esys: Implementation: deal with file-based SWEn
KA3727 - In the coding verification in Esys, the selection of several FA entries should be possible
KA3735 - RSU Delta containers should be accepted when importing to Esys (writing the psdadata xml)
CR3817 - Customize Esys released notes and welcome screen for privacy, and complete Diaglog settings
CR3829 - Esys customization to create an RSU KC (changed SSK)
KA3852 - Esys-Log should write off the vehicle order used in the TAL processing as a file name so that you can understand this later
KA3904 - Esys: Link how to se the module certmanagement at Esys Help
KA3934 - Esys: Adaptation to new SVT scheme (PSdZ-CR3907)
e-sys-3-33-release-notes

ENET E-sys cable for BMW coding:

1. Lock unlock sound confirmation ( to prevent radio interference, add sound to confirm car locked when turn light confirmation inconvenient. This is setup in cic)
2. Can operate the navigation menu including watching dvd when driving( for driving safety. Let the side driver operate the navigation menu )
3. Display engine output and torque meter ( purely fun, look engine output )
4. Cancel confirmation screen big screen boot delay
5. Open the voice recognition function
6. Three kind of bluetooth phone ringtones ( personality only )
7. Increasing the cic memory address to 50
8. The glass automatically rise to the top process is not terminated by the car door ( easy to get off to close the window waiting )
9. The digital speed display ( fun only )
10. Air-conditioned memory of the last off state ( without air conditioning season is more convenient )
11. Indoor cycling memories of the last time the state when engine off
12. A-pillar electric tailgate buttons and remote control a key to close the power tailgate. At any time terminate the reverse operation ( turn off 15 minutes or more reset )
13. Increasing shift paddles
14. The small screen to the large-screen display modify
15. Pdc display vertical and horizontal
16. Disable the seat belt status display - passenger seat
17. Disable the seat belt status display - driver seat
18. Disable seat belt reminder mistake ! The link is invalid. Device - passenger seat
19. Disable seat belt reminder - driving position
20. Disabled unfasten their seat belts voice prompts - passenger seat
21. Disabled unfasten their seat belts voice prompts - driving position
22. Intersection vehicle high beam automatic control ( no condition tested. Do not know if it is valid )
23. Angel eyes open and cancel functions
24 turn off the engine start-stop function turned on by default
25, gps time synchronization
26. Foot open the back cover
27. Ds show s1-s7 selection
28. Active sports gearbox program sport +
29. Single microphone settings
30. Engine off automatically unlock
31. Internet applications
32. Armrest usb playback video
33. The maximum distance disable front camera view
34. The maximum distance to disable the rear camera view
35. Maximum speed disable front camera view
36. The maximum speed to disable the rear camera view

BMW Enet Esys cable car list: 

BMW F chassis 2009 +:
       BMW 1-series: F20, F21, F44, F45, F46
       BMW 2-series: F22, F23
       BMW 3-series: F30, F31, F34
       BMW 4-series: F32, F33, F35
       BMW 5-series: F07, F10, F11, F18
       BMW 6-series: F06, F12, F13
       BMW 7-series: F01, F02, F03, F04
BMW X-series: F15, F16, F25
...

9.08.2018

INPA reprograms a new battery to BMW 328i: Done!

Tutorial + FAQs: BMW 328i new battery reprogramming/coding

Reason why you need “code” for a new battery:The answer to this varies. You may not have to! That is, so long as you replace your old battery with an exact replacement. However, if you switch from a wet-cell type battery to an AGM type battery, or vice versa, you must code for the change.
AGM and wet-cell batteries require a different rate of charge output from the alternator. Moving between these two types without coding can lead to over-charging or under-charging.
Also, batteries have a discharge rating called amp hours (ah). You must specify to the DME what the “ah” rating of your battery is so the car can run the proper charging algorithm.

Car: BMW 328i the year 2008
Software: INPA and Ediabas

How to reprogram a new battery with INPA software:
1: select BODY from the left hand pop-up menu
2: select POWER MODULE in the right hand list
3: select ACTIVATE from the next menu
4: Select ACTIVATE2 from the next menu
5: Then select F7 – Register battery replacement. Almost instantly you get the message: “Register battery replacement Activated properly.

THIS IS ONLY FOR REGISTERING AN OEM BATTERY FROM BMW! Alternate replacements will need additional coding to match voltage etc differences


Battery capacity / type in the FA change with NCS expert

FA read -> prepared following the new battery parameters in the FA change (eg,-A100,-B090 ..) -> FA in CAS and LM (depending on BJ o.FRM) Review – encode> Vehicles


FAQs for more details: 

1) Can I update the VO to CAS and FRM in expert mode? if not, what profile would I need?
only expertmode
2) Can I SG_Codieren to CAS in expert mode as well? Or would I need a profile with Manipulation enabled?
expertmode + sg_codieren = ecu to deflaut settings(factory)
3) When registering the battery in tool32… Do I use the MSD80.prg file for a 2008 328i?
yes but to be sure check what .prg use inpa to connect to your engine

  • Would NCS Expert be needed or just INPA alone?
Try with INPA

5) So will both NCS Expert and BST 2.12 run on win7 64 bit?
BST 212 will work on 64bit OS.

6) Any leads on where to find updated Datens or INPA?Here’s 2013 sp daten 2.51.2 full package for all cars (torrent download). Torrent files are split by chassis number so you can choose to download part or all of the archives: http://www13.zippyshare.com/v/94958605/file.html

7) If I only need e90 support, I can just use INPA and EDIBAS that comes with the above posted BST 2.12 ??? If that’s it, then I can go ahead and install this puppy… SP daten files are for Winkfp and NCS expert for programming and coding only.

Note: SP Daten E89 = E81,E82,E84,E87,E88,E90,E91,E92,E93.  Inpa is used for basic diagnosis and some adjustments, no coding. Mainly works on cars 2008 and below. Limited use on newer cars. You should install the package that comes with your cable as it’ll contain most of the ipo files needed to communicate with your car. But I recommend you install the new 2018 Rheingold software instead for diagnosis as it’ll do everything inpa does and a lot more. It’s easier to use and works on all cars and can be used with the K+DCAN USB cable or the blue GT1/DIS USB cable (note: the blue usb cable works on cars < 2007 only). You’ll find the Rheingold download and instructions on this blog http://blog.obdii365.com .

Related post:

9.05.2018

How to Diagnose BMW MSD80 DME with INPA software

In this entry: step-by-step diagnostics of, possibly, one of the most complicated engine management system of all times. Each of stages is kept as short as possible, references to previous posts for much more detailed information will regarding each knot/ theme be inserted.

Tools, used for diagnostics:
1. INPA loader 2.023; with OBD to USB connecting cable;
2. ISTA-D;
3. ELM327 with any of free-of-charge software, which can read OBD mode 6 data.
If any additional tools will be required, it will be marked in the specific section.

Preparation
1. Saving existing freeze-frame on the computer.
freeze frame is seen using INPA:
a) ../F4/F1/F3
b) ../F4/F2/F3

Information regarding each error message is displayed in separate “screen”. There are several ways, how to save information: you can print in on the virtual printer using INPA tools, it can be saved as a screenshot, or even take a picture with a mobile phone – it has no fundamental significance.
This is the very important stage of preparation! Error messages, recorded before, will give a lot of information in case of hidden defects!

2. Deleting existing error messages.
Deleting old error messages is important because only after this procedure the engine will try to restore normal functionality. The error messages (even with passive status) can define, that the damaged elements (or registered as damaged before) and the engine can switch to alternative (emergency) modes.
The error messages, which are marked as active (vorhanden) will restore immediately (during several minutes). If the error messages restore immediately – obviously, MSD80 has reason to “believe”, that current problem is present. Usually, active status (starting new driving session)  is maintained by:
error messages of sensors and/or actuator connection;
specific error messages, for example, 30E9, 30EA.

If MSD80 restore any of error messages immediately – this problem has to be solved before continuing with diagnostics. As the restored ones are “simplest” error messages, the damaged element is clearly stated in them. In this case is very convenient to use ISTA-D, choosing the option “Calculate test plan”. ISTA D contains schematics and “step-by-step” instructions, how to check the damaged knot.

Note: make special attention to errors 30EA and 30E9 (also: 29F4, 29F5, 2A26, 2A27, 2AF2, 2AF4, 2AF6 30DA, 30E0, 2EAE, etc.). If at least one of these errors are stored, following data may be incorrect:
  • voltages of warmed-up Lambda probes
  • Lambda values of wide-band probes
  • Rough run data
  • cylinder’s individual adaptation data
  • learnbits of injectors adaptations
  • misfire counters
and errors relating fuel mixture, misfires, Lambda probes, the performance of CO converters may appear without justification.
The engine should perform Stratified charge (Lambda of wide-band probes 2,0 .. 3,0) at medium loads (50 .. 90 km/h; 5/6th gear). If Engine performs Homogeneous injection only (with Lambda around 1,0) for a long time (more than 10 .. 15 min driving at medium speed/load) without errors displayed in the error message memory, check NOx converter status as described at p.3/part2 ‘Check the condition of NOx catalytic converter’ and follow instructions before continuing diagnostics.

In this entry we look at the situation, which does not fit in scenario of simple algorithms of ISTA D, it means, the engine, for example, is working unevenly; the defects are sporadic (for example, error messages regarding fuel trim, misfires etc.).
The typical user of N43/N53 has already tried most popular ways of repair – replacing spark plugs and ignition coils; at least half of them has already replaced also injectors, HPFP.

Note: the possibility of most popular exchangeable elements:
1. Spark plugs. The necessity to replace: average. N43/N53 uses multi ignition, it means, till 5 sparks one time (if it performs in Stratified charge) – the spark plugs are wearing out several times faster than in “regular” engines.
2. Ignition coils. The necessity to replace: very high! Unfortunately, even ignition coils, produced by Bosch (which are renowned for their longevity) can quickly get out of order. Reason – constructive defect of MSD80. Unfortunately, not many owners of N43/N53 engines allow interference in car’s electrical system – snubbers are installed in very rare cases, and the problem with ignition coils is still present. Snubbers, described in current entry, offers a radical and very efficient solution for coil damaging problem.
3. Injectors. The necessity to replace: comparingly low, very often injectors are replaced without reason. Even more – due to the incompetence of services (sometimes even dealer centers), it’s offered to replace all set of injectors, not even identifying the “guilty” one.

Diagnostics in idle
1. Checking cold Lambda probes for switched off engine
a) turn on the ignition, don’t start the engine;
b) open Analog values block No.6: ../F5/F2/F6
inpa-diagnose-msd80-1
c) evaluate two bottom bar lines;
bar of the left side has to show: 16K Ohm; a bar on the right side has to show: 65K Ohm;
d) open menu of fuel mixture ../F5/F6;
inpa-diagnose-msd80-2
e) check the voltage of the control probes, it has to be 0,42V for N53 engine (both banks) and 0,42 V for 1st bank in case of the N43 engine;
f) check wide-band probe voltages, probes for both banks has to be 2,0V +/-10%
inpa-diagnose-msd80-3
If the values are different from ones mentioned above, continue with further research. 

2. Checking injectors for leakage (especially efficient – for cold engine)
a) open menu for fuel mixture: ../F5/F6;
b) start the engine;
c) wait, till MSD80 starts to heat up the wide-band probes (bar of the first line reaches 99% after several seconds stabilizes limits of 30 .. 60%;
inpa-diagnose-msd80-4
d) observe Lambda values of wide-band probes;
e) observe values of integrators.
inpa-diagnose-msd80-5
If Lambda values are significantly different from 1,00 (in case of typical defect: below 0,97, but also values above 1,03 are incorrect), and if integrators “jump” out of -15 .. +15%, carry out the more detailed test for leakage of injectors. 
Note: if wide-band probes are not heated within 30 .. 60 seconds after engine start, check learnbits as described at p.1/part2 ‘Check learnbits’ and follow instructions.

3. Checking Nernst resistances of heated Lambda probes
a) switch on the engine, heat up for 5 minutes;
b) open menu of fuel mixture: ../F5/F6;
c) check, that all four probes are being heated up (bars of first two lines shows 30 .. 60% PWM);
inpa-diagnose-msd80-6
d) open Analog module 6: ../F5/F2/F6;
e) evaluate Nernst resistance values (bars of two bottom lines)
inpa-diagnose-msd80-7
If Nernst resistance values are 0/256/512 Ohm: probes are heated up and their chemical efficiency is acceptable.
1024 Ohm and more – the probe has aged or is damaged, it has to be replaced.
Note: if all Lambda probes are not heated within few minutes after engine start, check learnbits as described at p1/part2 ‘Check learnbits’ and follow instructions.

4. Checking Lambda probes
a) heat up the engine till work temperature;
b) keep the 2000 .. 3000 RPM for at least 10 seconds;
c) open test module for probes: ../F9/F3
inpa-diagnose-msd80-8
d) press F1, to perform the test.
Correct results of the test: Lambda 0,90/1,10 (+/-0,01) for wide-band probes, <0,1/>0,8V for control probe (1st bank for N43) or probes (both banks for N53).
inpa-diagnose-msd80-9
Typical defect: control probes generate a lowered voltage. If the test voltage identifies <0,8V, the probe is aged or clogged, it has to be replaced. After replacing:
a) delete adaptations (2nd group) ../F8/F2/Shift+F9,
b) create new adaptations.

5. Checking the crankcase ventilation
a) if the test is performed at cold engine – wait, till wide-band Lambda probes are heated up (see above);
b) turn on the fuel mixture menu ../F5/F6;
c) observe the integrators and offset type adaptations;
inpa-diagnose-msd80-10
d) slowly open the oil fill cork.
If integrators are growing rapidly and reach +20 .. 30% during few seconds or the offset adaptations are being rewritten (are increasing), the crankcase ventilation valve does not work properly. 
Note: a test of crankcase valve should be performed in Homogeneous mode. Control Lambda values of wide-band probes (should be around 1,0).

6. Evaluation of intake manifold air-tightness
a) open menu of fuel mixture: ../F5/F6 (wide-band probes should be warmed up);
b) evaluate offset type adaptations;
c) evaluate integrators.
inpa-diagnose-msd80-11
If the offset adaptations are highly above 0 (above 1,5 .. 2,0 mg/stk) and/or integrators reach +15 .. 20% (with normal and stable fuel pressure) in both banks, air suction in intake manifold is possible. Check the air-tightness of the intake manifold (with the smoke test), eliminate air suction. Additionally – check the air-tightness of EGR valve (manually blocking the channel of EGR valve). If offset adaptations are going back to normal – solve the problem with EGR system (EGR valve is closed, when idle).

7. Checking the fuel pressures
a) open Analogue value, block No.6: ../F5/F2/F6;
b) observe bar No.5 and No.6 on the right side.
inpa-diagnose-msd80-12
Value of low-pressure has to be 5000 hPa, maintaining stability: 4950 .. 5050 hPa, not worse;
high-pressure value has to be 150.000 .. 200.000 hPa, jittering (short-time unevenness) – not more than +/-2000 hPa. If difference or higher instability is observed, perform additional fuel supply system test.

8. Checking VANOS jittering
a) open VANOS menu: ../F5/F4;
b) evaluate offset adaptations for both camshafts. If any of them is outside +/-7,0 .. 8,5%, perform the repair of VANOS (it’s mounted incorrectly);
inpa-diagnose-msd80-13
c) press accelerator pedal and keep 2000 .. 3000 RPM. Evaluate differences in inquired and measured position. If the differences are higher than +/-0,5 degrees, perform more detailed evaluations of VANOS knot and, if necessary, perform the repair. 
inpa-diagnose-msd80-14
If the instability of VANOS is observed, definitely check the stability of oil pressure.

9. Stability of oil pressure (can be skipped, if VANOS works stable)
a) open menu of oil pressure: ../F6/F2/F2, observe inquired oil pressure if it fluctuates strongly (above +/-100 hPa);
b) evaluate PWM of oil pressure valve
inpa-diagnose-msd80-15
If PWM of the valve reaches 99% and/or oil pressure fluctuates strongly, perform more detailed inspection of oil pressure system
Note: reduce the value of inquired oil pressure by 1000 hPa, evaluating the inquired values.

10. Evaluation of misfire counters
If cold engine works significantly unevenly, check misfire counters.
a) connect the ELM327 adapter, open its software, OBD mode6;
inpa-diagnose-msd80-16
b) evaluate cylinder misfires of the actual session (and inter-sessional counters);
If misfire counters of any of cylinders are strongly different from 0, evaluate spark plug and ignition coil of this cylinder.
If the spark plug is covered with black residue – most likely cause: leaking injector.
For control – replace the spark plug with a new one, repeat the test.
If there are suspicions regarding leaking injector, take it off and send it to testing/cleaning.
Note: if the engine has errors relating NOx system, data reported by Rough run/misfire counters may be incorrect! Fix problems with NOx system first.

11. Evaluations of the Rough run.
a) open menu of Rough run: ../F5/F7;
b) is the status of flywheel adaptation in inactive (colorless) – the adaptation of flywheel is not performed, indications of cylinder efficiency can be incorrect. 
inpa-diagnose-msd80-17
c) evaluate measurements of mechanical efficiency of the cylinder.
Decreased mechanical efficiency – increased (above 0) bar value.
Attention: cylinders marked in firing order!  (It means, 1-5-3-6-2-4 for 6-cylinder engine or 1-3-4-2: 4-cylinder engine).

If any of cylinders regularly shows decreased efficiency (bar strongly larger than differences of other cylinders form 0), there is the reasonable suspicion regarding the incorrect performance of the injector. Check opening times for injectors (description below), send injectors to testing and cleaning.
Note: different software releases can have very different sensitivity regarding unevenness of cylinders. There are MSD80 software versions, which would identify significant unevenness with bar differences 1,000 .. 1,500; there are software versions, which would identify significant unevenness with bar differences 0,010 .. 0,015.
That’s why it is very important not to evaluate absolute values of bar differences (it can be small and far from red sector), but identify the cylinder, which differs most from others (bar value is positive against others).
If the unevenness of cold engine is especially significant in first few seconds after start, move this test stage as second after Lambda value test for switched off the engine.
If MSD80 will detect the unevenness for a longer time, it will try to solve this problem, changing the opening time of the injectors.
If the engine has errors relating NOx system, data reported by Rough run/misfire counters may be incorrect! Fix problems with NOx system first.

12. Checking opening time of injectors
a) open the injector opening menu: ../F5/Shift+F6/F1
inpa-diagnose-msd80-18
b) evaluate the differences in the injector’s opening time
If the opening time of any of injectors is significantly different (for more than 20 .. 25% from average opening time of other injectors) – send the injectors to cleaning and flow-rate test.

Note: Repeatedly compare the opening time of injectors with Rough run menu data. In both cases:
a) with similar injector opening, there is a large difference (more than 20 .. 25%) in Rough run values;
b) with the balanced mechanical efficiency of the Rough run (after a while), the opening time of anyone injector is significantly different (more than 20 .. 25%) from others.
Mark the cylinder, who is ” different”, check it’s injector, clean it (it would be recommended for all injectors) or replace it.


The set of above-mentioned processes will guarantee, that the “guilty” cylinder or knots will be identified in idle, both for the cold and warm engine.
In idle, N43/N53 series engine runs only in Homogeneous mixture mode (also warm engine, directly after switching on, if the RPM are not increased), accordingly – the diagnostics, which should be performed for Stratified charge mode, is not possible. The description will follow.

If the engine in idle runs smoothly, but unevenness is detected only at mid/high loads, and previous test stages didn’t show any deviations from the norm, continue the diagnostics with the driving session, during which you have to observe necessary parameters.

Before driving session
1. Check learnbits
a) open learnbits: ../F5/Shift+F6/F2
b) if the learnbits of the first line for some reason are not colored, the engine for some reason has not performed initial adaptations!
inpa-diagnose-msd80-19
Perform several short driving sessions, driving smoothly end evenly for some 10 .. 15 minutes with speed 60 .. 90 km/h, holding a pause in idle for 5 .. 10 minutes. Make sure, that the upper learnbits are colored.
If the learnbits of the first line are colored, the creating of adaptation continues, till following learnbits are getting colored:
X;X
X;X
0;0
X;X
Note: If the engine doesn’t start to color the learnbits, check the coding of injectors,  If the second row, first/second line learnbits are not colored, the engine has hidden problem with NOx system (30EA; 30E9 errors). Fix NOx problems first!

2. Evaluate multiplicative adaptations of fuel mixture
a) open menu of fuel mixture: ../F5/F6
inpa-diagnose-msd80-20
b) evaluate the multiplicative adaptations.
If the multiplicative adaptations of both banks differ (in one direction) for more than +/-20%, pay special attention to the high-pressure sensor (its indications can be incorrect), coding of injectors (the flow-rate could be inappropriate), definitely the Lambda probe test has to be performed.

If the multiplicative adaptations of both banks have large difference (above 10 .. 15%), pay special attention to Lambda probes and perform the test; also injectors have to be evaluated (pay attention to Rough run test).

3. Check the condition of NOx catalytic converter
a) open the menu of NOx catalytic converter: ../F9/Shift+F3/F1
inpa-diagnose-msd80-21
b) if the pollution level of NOx catalytic converter is 0 mg, most probably, the MSD80 had registered error message 30E9. Solution: follow the description of the current error message, when the normal performance of NOx catalytic converter is restored – create new adaptations and perform the tests again.
c) if the pollution of NOx catalytic converter is above 2000 mg (or 30EA is stored), perform the session of forced desulphation. After repeating the tests.

4. Check the thermostat
a) warm up the engine, open Analog values, module 6: ../F5/F2/F6
b) evaluate the working temperature of the engine;
inpa-diagnose-msd80-22
c) evaluate the temperature of the oil, coolant (before/after radiator)
inpa-diagnose-msd80-23
All indications have to be reliable. If any of sensors shows inadequate temperature, solve the problem with a current knot. The engine has to warm up to (at least) 90 oC. If the temperature of the engine is lowered, check the performance of thermostat. If necessary, replace them. The more detailed description regarding thermostats here.

5. Check performance of NOx sensor
a) open menu of the NOx sensor: ../F5/Shift+F2/F1
b) warm up the engine to 90 oC; start the movement, drive with at least 20 km/h;
c) warm up the exhaust at least till 220 oC;
inpa-diagnose-msd80-24
d) during two minutes, the NOx sensor has to start to report NOx value, which should be different from 0 ppm. If the NOx sensor continues to display the value of 0 ppm, perform a more detailed examination. If necessary, the NOx sensor has to be replaced.

Driving sessions in problematic mode
Try to drive in mode, where the unevenness can be observed.

Typical modes, when the defects can be observed:
1. Kick-down mode by low RPM (below 1500 .. 2000) – ignition problems (spark plugs, ignition coils);
2. Mode with maximum lean fuel mixture (50 .. 60km/h, gear 6, Stratified charge: required Lambda around 2,5 .. 3,0)
a) ignition problems (spark plugs, ignition coils);
b) incorrect Lambda (reaches 4 .. 5) – problems with adaptations, their creating;
3. changing mode (for example, smoothly pressing/releasing accelerator pedal, driving with speed 50 .. 60 km/h) – VANOS (jittering, position errors), throttle (jittering, reaching the position);
4. in the moment of rapid opening of throttle – problems with fuel pressure (LPFP, HPFP). 
5. unevenness of torque (smoother than in cases of misfire) – VANOS (jittering of positions).

In problematic mode:
1. observe Lambda of both banks and the performance mode of the engine
a) open fuel mode menu: ../F9/F1
inpa-diagnose-msd80-25
b) observe Lambda for both banks
If misfires start with increased Lambda (above 3,0) obviously, there is a problem with adaptations. If the old adaptations have been deleted recently, allow the engine to perform in other, similar modes (for example, with slightly higher speed/load), so the engine can perform correct Lambda value adaptations for both banks;
c) if the unevenness can be felt when the engine switches to the Homogeneous mode and back to Stratified charge;
a) allow the engine repeatedly switch to these modes (when/if MSD80 will identify the problem in the moments of switching, it will perform throttle jittering adaptations);
b) update the software – newest versions of MSD80 software perform the switching more slowly and smoothly – the unevenness cannot be identified (if all component of the engine is in work order).

2. Check misfire counters
a) connect the EML327 adapter;
b) read misfire counters;
c) for the reliable result: switch off/on the ignition, evaluate the counters once again after unevenness. Solve the problems with the cylinder, identified with misfire algorithm (start the solving of a problem with the cylinder, who’s misfire counter identifies the larger number of misfires).
Note: perform the test on the even road. The effect of the uneven road to misfire counter.
If the engine has errors relating NOx system, data reported by Rough run/misfire counters may be incorrect! Fix problems with NOx system first.

3. Check the performance of VANOS. It is possible, that the inquired and measured position in these modes are significantly different. If significant differences are observed (short term – by several degrees; long-term + jittering – not more than +/-0,5 degrees:
a) check the stability of oil pressure, as described above. If the oil pressure is unstable – solve the problem with oil pressure. If the oil pressure is stable,
a) solve the problem with VANOS.

4. Observe Lambda jittering.
a) open the Lambda and work mode menu: ../F9/F1
inpa-diagnose-msd80-26
b) observe Lambda in both banks in Stratified charge mode, evenly (ideally – using cruise control) drive with speed 60 .. 90 km/h.
If significant Lambda jittering while the engine performs the Stratified charge (Lambda is 2,0 .. 3,0) is observed (rapid value changes up/down for more than +/-5% from Lambda value) – the cleaning of injectors has to be done. Obviously, the amount of injected fuel or beam is unstable.
Additionally – check the stability of LPFP and HPFP in current moments, as described above.

2. Evaluation of spark plugs
a) screw off the spark plugs
b) compare the color of the insulation
If the insulation is Black, not light grey, most probable cause – leakage of the injector. Send injectors to leakage test and cleaning. If the cleaning doesn’t solve the problem – replace the damaged injector. If exactly any of bank’s spark plugs is darker, perform the following test.

6. Evaluation of Lambda in Homogeneous mode
a) open the menu of engine modes: ../F9/F1
b) switch the engine to Homogeneous mode, pressing F1.

Evaluate the Lambda values in both banks in different modes. If Lambda in any of the banks (except the rapid increase of speed) is below 1,00, perform an additional test of Lambda probes. Possible cause of the defect: the lowered voltage of the control probe (the probe has clogged and/or is aged).
Note: after test, switch off the Homogeneous mode: mode menu ../F9/F1, press F5

7. Evaluation of the adaptation creating for injectors
Perform the driving session for 10 .. 15 minutes with even driving conditions (50 .. 100km/h), let the engine run idle for 5 .. 10 minutes. Repeat several cycles.
a) open the menu of injector adaptations: ../F5/Shift+F6/F3
inpa-diagnose-msd80-27
b) evaluate the measured data if the injectors. Normal differences are up to +/-5%
c) open the efficiency measurements of Stratified charge idle: ../F5/Shift+F6/F5
inpa-diagnose-msd80-28
d) evaluate the measurements of efficiency. Normal differences: till +/-0,5 mg/stk
e) evaluate total corrections of the injectors: ../F5/Shift+F6/F1 (lines 4 to 6)
inpa-diagnose-msd80-29
If any of injectors shows very high differences – perform the test of the injectors, if necessary – clean it or replace it.
When the repeated test is performed, the differences in cylinder efficiency have to reduce substantially. If they still are significant, make the notes, which cylinders are regularly changing their measured efficiency, perform the test of injectors of them (flow-rate and leakage).

All the procedures described above provide a clear view of all major possible problems of MSD80.