topblog Ivoire blogs


Single VCI + Multiple Diagnostic Software + One Laptop

Tips and guides:

Purpose: a single VCI - a few different diagnostic programs - one laptop - different cars diagnostics

  • BMW
  • JLR
  • Toyota
  • Mazda

may add more in the future...

There is a single VCI that can be connected to and operate with these multiple software bundles


You could cover all of these using either...

1. Autocom/Delphi 2014.3 software (2015 & 2016 versions are fake) with DS150e /CDP vci

2. Launch Pro with Launch Easydiag 2 or Easydiag 3 vci. Look in the forums for free solutions or get it with tech support from a reliable source (i’m using

Launch is up to current vehicles.

This will be sufficient for most diagnostic work needed to repair all brands of vehicles you might expect to encounter.

If you want to get into software updates or chip tuning then you will need many more expensive tools.


  1. AVDI and for the matter FVDI work as pass through's I have both gen avdi and ori fly fvdi and we use the fly for ford,jag,honda and toyota as it also has the free loader that means you can use the latest manufacture applications direct
    What you do need to be aware of is what versions of can you need to communicate over there are many ISO protocols and also pin out options of the obd2 plug
    For example ford use J1850 on pins 3 and 11 as it will work in single wire config avdi doesnt talk on this so relies on using the vehicles can interface which is ok until you have an isue on that can interface
    But Ford KA (edge 2009 on) is actually Fiat so it uses pins 1 and 8
    You need to know exactly what you need in terms of protocols (there is 6 common ones) then work out if you can find the drivers for a tool that works with your software

    4. A different option is to get a can sniffer dependent on type and software options (VXDIAG Multi Tool should a good option for you) - then you can diag every car and you can enter into many functions hidden to your scanner
    The OBD2 connector protocol is a mandated law (this started in USA but is worldwide now) that means every module on the vehicle must be accessible and programmable via this socket this goes way beyond the flashing of maps etc. Manufactures are allowed to password protect parts of the system like the incode/outcode of Ford but as manufactures are by nature bean counters and lazy they buy in there electronics so a Delphi code is a delphi code no matter if it is ford or peugeot or even geely

    I am looking at getting a ADR soon (about £3500) as they have some amazing access to modules they can tell you that at x time on x day x mileage/rpm/outside temp "colour of your pants" you entered the speedo module and reprogrammed the vin and the real vin is x from this stolen car... (even if you reprogram chip of the board as its done by snapshots)
    The police have this and its made by Bosch and anyone can buy it


Clone VCM2 Ford IDS 111 Update

Issues: VCM2 doesn't connect to the PC anymore.

Hardware: VCM2 clone (not VXDiag VCX Nano Ford) which has worked fine

Software version used: IDS v109 on VMware.... worked fine

Software updated version: IDS version 111 native...not working

Error message:

Tried the last IDS version 111 native install but at the first connection , IDS requested a VCM software upgrade. After few seconds i received an error message (there was an error updating your VCM2).

Since then I've tried recovering my VCM2 using IDS V86, VCM II manager v2.1.119.3, new SD card, with OBD power, without OBD power. The process stars good but after 2-3 minutes i receive an error message (There was an error reprogramming your VCM2 and your VCM2 requires a factory reset).



Tips & guides:

some clone vcm's are prone to this
I found that it was usually the output voltage/amps on the computers usb as I could always reset them on my trusty old Dell

To do this it had to be V86 on XPs3 and not on a VM I also powered up the vcm on its 12v power jack directly
I reset literally 20 plus for friends with this set up many times over years ago

the only other issue I found was the little reset button falls off the board very easily if you press too hard



I used a PC with a fresh windows 7 32bit and IDS86 installed without VM  .
I finally found the issue and it was actually a simple intermittent connection with the USB cable. (although the message was not the loss of communication..)
After the cable was replaced, the software update was successful.

Now IDS version 111 works like a charm!


2018 latest version ODIS 4.4.10 released notes

2018 latest version ODIS 4.4.10 released notes: working with VAS 5054a or 6154?


ODIS 4.4.1 Service incl. Postsetup 69.0.10

latest version 08.2018 incl. license until 2030


The flashing was integrated.

for the brands: VW (cars), VW (commercial vehicles), AUDI, Seat, Skoda.

Multilingual / Multilingual

Windows 7,8, 10 (32 and 64bit)

Year / Date of publication: 08/2018


Incl. Postsetup 69.0.10

(Postsetup only in German, English, Polish)



ODIS Service - O ffboard D iagnostic I nformation S ystem service for the vehicles of the VAG group (Audi, VW cars, VW Commercial Vehicles, Seat, Skoda)

Works with VAS 5051B, VAS 5052A, VAS 5054A, VAS 5055, VAS 6150, VAS 6150A, VAS 6150B, VAS 6154, VAS 6160, CarDiag-Plus, iFlash, PassThru SAE J2534.

ODIS Service 4.4.1 only works under Windows 7 32bit with the VAS 5054a

For all other Windows, use the VAS 6154 or a PassThru-compatible adapter.


In order to work under Windows 10 with the VAS 5054a, a VAS5054A fix driver is included, but it will work only 50/50% with the VAS 5054a. Is dependence on the quality of your VAS 5054a clones.

Otherwise, use the newer VAS 6154 instead.

It only works with a high quality VAS 5054a.


The ODIS system integrates the main application system of the VW Group and significantly improves the efficiency of the diagnosis.

ODIS system offers flexible fault diagnosis, clear data check display, convenient diagnostic input.


note that the 100% successful solution is

VAS 5054a + odis 4.3.3

VAS 6154 + odis 4.3.3



ODIS System v4.4.1 Advantages:

* Higher quality and lower repair costs through highly efficient diagnostic procedures

* The central administration-managed GFF database directly outputs error information and solutions.

* A full range of integration from development to after-sales service makes the process base more reliable.

* The integration of the diagnostic system (eg: Elsa pro) further improves the core processes of the service.

* Systematically optimizes the technician's diagnostic procedure and saves time.

The optimization of the diagnostic procedure makes the costs of the dealer reasonable.


ODIS v4.4.1 Features:

* Diagnostic logs are saved automatically.

* You can choose a dynamic brand layout. This then changes depending on the make of the vehicle.

* The special functions are displayed thematically sorted.

* You have the possibility to generate a self-diagnostic protocol.

* You can check the connections to backend systems.

* The enforcement of an update has been optimized.

* The data download takes place in the background.

* An intermittent download will continue automatically.

* You have the option of automatically shutting down the system after an update.

* If there is no online connection, the login dialog in the diagnostics entry is skipped.

* The view Test Instruments is printed with white background.

* You can use a standard mail client to send a support message.

* Certain features can be set manually, if available, national variant.

* There is a mode self-diagnosis.

* Self-diagnosis can also be used during contract work.

* OBD functions can be performed in self-diagnosis.

* Various small optimizations on the graphical user interface.


ODIS 4.4.1 Images:

odis-4.4.10-image-1 odis-4.4.10-image-2 odis-4.4.10-image-3 odis-4.4.10-image-4 odis-4.4.10-image-5 odis-4.4.10-image-6 odis-4.4.10-image-7 odis-4.4.10-image-8 odis-4.4.10-image-9 odis-4.4.10-image-10

ODIS v4 source: