topblog Ivoire blogs


How to solve Communication unit minitor after you update VOLVO VOCOM PTT 1.12 software?

As the most cost efficient and multi-functional volvo diagnostic scanner with multi-language. VOLVO VOCOM is welcomed by most repair shop and individual users.


VOLVO VOCOM has two version software available. PTT1.12/2.40 and  PTT2.03/3.02. PTT1.12 comes with the package, Mainly can work on volvo vehicles till 2012 and euro 5. It is provided for free. Only used on XP system. PTT2.23 software need to buy. It can work on volvo vehicles till 2015 and euro 6. Can be used on WIN7 system. Both of this two software cannot be updated online!


How do you do after you update the PTT1.12 software for VOLVO VOCOM?

I bought VOLVO VOCOM on February 2015. I install the PTT 1.12 on XP system and run smoothly. But today, I have updated the Tt 1.12 software to the latest version but know I get the following error:


Communication unit minitor

Connected communication unit 88890020/88840133/88890300updated.

The software in the communication unit 88890020/88840133/88890300 must also be updated to be compatible.


See the Tech Tool help file for instructions on how to update hte software



Attention: This software and solution is only for customer who update the PTT1.12 software. If you do not update. Just use the PTT1.12 software comes with the CD on XP laptop.


1) download our WIN7 system:

2) follow video to install the win7 system:

3) after done, better do not connect internet for this laptop, to avoid update it again

4) download this 1.12 software, and follow the video inside to install again:!YR1BlQJb!0-RJkT1gGJvCMlLA1c86dg

For more information, click

05:36 Publié dans Blog, Shopping, Web | Lien permanent | Commentaires (0)


BMW Diagnostics and Procedures FAQ: Check Engine Light

If the BMW Check Engine Light (CEL) is, or has been, on there will be stored codes pointing to what is wrong. It is critically important that these codes be read with the proper diagnostic system. That means a dealer or very well equipped BMW indie shop. The entire car needs to be scanned, especially on later cars as there are a lot of electronics and they interact. Examples of proper diagnostic systems would include:


BMW's DIS/TIS ("GT-1")... ('07 and older)

BMW's newer systems, known by various names: ISIS, ISTA and ICOM



SnapOn systems with the proper BMW S/W

Matco Launch with the proper BMW S/W


Understand that the fault codes are not necessarily to be taken literally. In many cases a particular fault code just tells you what the car is unhappy about, not necessarily what the real cause is. And that is where the experience and skills of a pro are important in interpreting what the codes could mean.


While P codes below 1000 are federally mandated, the codes above that are left to the vehicle manufacturer to define. They frequently vary by model, year, and engine. BMW diagnostic systems don't use P codes, but the generic OBD do. Generic OBD code readers can't scan everything and they frequently produce invalid or misleading results because they don't have tables for the variants in codes for the various model, year, and engine. So that is usually a meaningless exercise.


In states that require emissions testing it isn't uncommon for part of the test to include a scan for codes. In that case the car will fail if any codes are found. Which means that the fault(s) must be fixed, the DME cleared of codes, and the car driven long enough for the DME to go "ready" which requires that all of the conditions of the "Federal Test Procedure (FTP) Driving Cycle" have been satisfied. The car won't pass testing until the DME is in a "ready" state.

10:30 Publié dans Blog, Shopping, Web | Lien permanent | Commentaires (0)


Encypt CAS lost ISN value, solved with VVDI Prog


Have an BMW X5 here with all keys lost CAS3+, read the CAS with rosfar as usuall

Tries to make a key from file and get these errors ”Detect encrypt CAS version. But CAS lost ISN value. Continue prepare key may cant start engine. ” and the second picture error “Can not find useful combine data, please check the EEPROM file.”



Working Solution:

This bmw eeprom don’t have enough data for combine test

For this car, you need read ISN from engine with other tool, the best working tool which can read BMW ISN from engine is VVDI prog made by Xhorse Company. 


The Procedure to Read BMW Engine ECU ISN with VVDI PROG

YouTube video:



Open VVDI PROG software.

Select type: 3-ECU  Brand: BMW_F_ENGINE  Device: MEVD172(N20) 

Click “Wiring Diagram”


Wiring Diagram is open, it prompts NO.2 connector. 


NO.2 connector picture as follows.


Pull down the wiring diagram, attention: the left corner is NO.33 pin, and the right corner has pin, follow its pin number and order to connect the cable.


This is real BMW Engine ECU 


All of pin numbers are marked as follows.


Next, to plug the cable into VVDI PRO 


Firstly, connect red power cables, there are 2 power cables, one is No.1 pin, one is NO.22 pin.



Next, connect GND cable, it is NO.10 pin.


Finally, connect blue CANH cable and yellow CANL cable.


This group of cables are connected well.


This is Bootm line.


Open a hole on Engine ECU and locate the pin position by following the wiring diagram, then use Boot line to point at this pin and to read data. 


Note: an external power adapter is necessary for VVDIprog, because it reads Engine ECU.


Close wiring diagram on VVDI Prog 


Select “New Create”


Select “Read”


Wait until the data is read out successfully. 


Select “Save” to save data.


Last note: 

If BMW CAS4+ all key lost, firstly read CAS data then Engine ECU data, when it asks for ISN code, just load Engine ECU EP data to generate dealer key.



Hope this helps.