Where To Download Free TCS CDP DS150E 2015.3 2014.3 2014.1 2013.3 Software

Here is Multidiag pro+ software download 2015.3 2014.3 2014.1 2013.3 Delphi DS150E software crack. Also can be used with TCS CDP pro+ china clone. Attached all details here.

NOTE: all chinese clone version!

Software: D-S-150-E (china clone)

Hardware: TCS CDP (pro) / Multidiag pro+

DS150E comparison: 2014r2 vs 2014r3 vs 2015r3
"2014.R2 is the most stable version, 2014.R3 support a little bit more models but ISS scan is not working with some models. 2015.3 is the newest at the moment but there are some bug in the software, all fault code descriptions are missing, it shows the fault code but the description only shows "unknown fault", ISS scan also not working on some models."

Operating system: Windows XP (better)/Windows 7

2015r3 -

Free download 2015.3 (clone)

https://mega.nz/#F!wBQlTBCT!tCm5jhowbLZ2nQWpaLBiXg

http://goo.gl/35RzDM (Tested OK)

Which device to work together with:

2015.R3 TCS CDP Pro with Bluetooth  2015.R3 TCS CDP Pro without Bluetooth (New Design) v2015.3 TCSCDP Pro without Bluetooth (New design) 2015.R3 TCSCDP Pro with Bluetooth and 4G Memory Card

2014r3 

Free download 2014 & 2013(clone):

clone2014.3V SN: 100251
http://www.obd2vip.com/search/?q=delphi
shows:

Free activation, Tested ok:

http://www.obdexpress.co.uk/wholesale/new-design-plus-multidiag-pro-cars-trucks-obd2.html  

China 2013.3
http://www.obdexpress.co.uk/wholesale/cdp-pro-latest-software-cd-31.html
attached file:
DS150E WIN7 User guide German.pdf

note: Delphi 2015 1.3 doesn't work on x64 ????
It works without any problems on win 7 x64, try to run in compatibility mode for win 7.

How to runTCS CDP and Multidiag pro crack software:

Chinese TCS CDP pro+ and Multidiag pro+ share the same software!

Please disable/uninstall anti-virus software before download this software!

Please note,anti-virus software can flag up this product software as having a virus. This is a false positive and is due to the software containing the application file like .exe. So Before setup the device software, please disable/uninstall anti-virus software or install a more reliable virus scanner! Our product software is completely safe and virus free and all other virus scanners confirm this.

How to use WOW 5.00.8 for CDP+:

If you want to use wow with your CDP+, you can find everything here:
http://mhhauto.com/Thread-Wurth-WoW-5-00...hlight=wow
http://obd2-diag.blogspot.com/2016/01/multidiag-pro-20153-20143-20141-20133.html

https://mega.nz/#F!aBgx0ajB!zX0vwWrLWGKvfLDb3hNsuQ 

Wurth WOW 5.00.8 download:

https://mega.co.nz/#!S8tDHabJ!uSeN9CkSNISCV34s62IsHcvMN2-9sKdvmRLAIkyhE2A 

1.) First thing you have to do is install wow 5.00.3, genuine install which you can find in post #1.
2.) Then install autocom/delphi if you want (or you can do this before wow, doesn't matter).
3.) Find and download firmware 1423 for wow from links in post #1
4.) Copy all firmware files to installs\ac_diagnosis_module\firmware and also to Delphi&or Autocom installs folders\Firmware
5.) Open wow 5.00.3 and update firmware from it. During installation choose snooper+
Now you can enjoy your tool and softwares. After you have done all this, you can download and install wow 5.00.8, cooked version, also from post #1 of given thread. But ONLY after you have updated firmware as I described.

The info is all over and all you had to search for is what I put above
But just to answer for the sake of it again 

Install any of the software you want or even install them all if wanted
Get the firmware for wow if you want to use wow and autocom/Delphi 
Put the firmware in all softwares firmware folder
Therefore you then have the same firmware for each software (wow being best)
It's always been advised to do any firmware updates using wow 5.003 ( seems to work best)
To do an update you must have 12v to hardware, so plug into car or have a lead made and power supply.
In wow software old cdp (gold) = snooper or snooperBT (if with Bluetooth)
Newer cdp+ = snooper+ or snooper+BT (if with Bluetooth)

Modified VCI firmware 1612 and 1622:

http://www102.zippyshare.com/v/M2iPyGgc/file.html

It is modified to work with Wurth WOW 5.00.8R2 and Autocom, Delphi etc. without need to flash your VCI. 
1612 works well with Autocom/Delphi 2014.1, 2014.2, 2014.3 not recommended for 2015.1/2015.1R3
1622 works well with Autocom/Delphi 2014.3, 2015.1, 2015.1R3 not recommended for 2014.1, 2014.2
Both fw work well with WOW. If used with not recommended software version, connection may not be stable and DTC description maybe missing. 
Can be used on original or Chinese clone. Tested on v4 and v5 dual board and v1 and v2 single board VCIs.

Which device to work together with:

Multidiag pro with single PCB: Multidiag pro 2015R3 DS150E Bluetooth, Multidiag pro 2015R3 DS150 without Bluetooth, basic configuration

Multidiag pro 2015R3 DS150E Bluetooth with a 4G memory card

(Full kit) Multidiag pro 2015R3 DS150E Bluetooth with a 4G memory card, with all cables 



Multidiag pro with double PCBs:

Multidiag pro+ without Bluetooth, 2015R3 DS150E, cheapest, 



Mutidiag pro Bluetooth 2015R3 DS150E, with a 4G memory card

1 PCB unit or 2 PCB unit, Which one should buy?

- 1 pcb unit works good

2- 2 pcb hardware works like a charm, but must have luck... 

3- the white tcs is a good tool

Chinese TCS CDP board comparison:

With full Multicolorindicator

 With single Multicolorindicator

 With Speaker

 Without Speaker

 With Bluetooth (two kinds of bluetooth module, one best, one normal)

 Without Bluetooth

A good tip: 2015r3 TCS CDP pro PCB v8 v6 v5 v3

VCI firmware 1423 and 1430:

WOW comes with 1423 firmware and it is optimised for Wurth VCI, which is a modified Autocom’s hardware.

1430 firmware is made by  Autocom and it is for VCI made by them. If you update your WOW and VCI with 1430 firmware, you may damage your VCI. Because WOW is more complex than Autocom and its firmware is optimised for modified VCI. It means what WOW diagnostic software is giving VCI commands which cannot be executed because of hardware incompatibility. Autocom’s firmware interprets WOW commands in a slightly different way. In that case VCI is stressed and depending on its quality may get damaged in a few hours or months.

You can actually hear intensive relay clicking and other noises.

If you intend to use WOW software, use it with its own 1423 firmware.

TCS CDP clone/ Multidiag pro, how much do you know?

1. With CARS, you are able to perform brand specific diagnostics for cars and light vans from 1988 onwards. A total of 47 different brands.

2. With Truck software package, you are able to perform brand diagnostics for light and heavy vehicles,buses and trailers from 1995 onwards.

3. The diagnostic program is designed for the legislation based diagnostics, specially targeted for emission related fault codes.

4. Support multiplexer function, 2xHS CAN (ISO 11898-2), SW CAN (SAE J2411), K/L (ISO 9141-2), RS485 (J1708), TTL and (SPI, analog in, 5volt out).

Functions:

FLIGHT RECORDER

With the flight recorder function, you can record parameters in real time while you are driving a vehicle. During recording, you can highlight the specific error with a press of a button so that you can investigate the detected error at a later time. CDP+ is equipped with built-in memory.

VOLTAGE CHECK

When CDP+ is connected to the vehicle, the unit will check the battery voltage of the vehicle and automatically adjusts itself to the vehicle’s voltage level of 12 or 24 volts. If the voltage gets too high or too low, CDP+ will warn you with both sound and light and you will also be alerted through the battery icon in our diagnostic software.

CHASSIS NUMBER VIN

In our CARS software, we have a smart function that allows you to read out the chassis number from the vehicle that you would like to diagnose. This ensures that the right model and year is selected automatically. In addition, engine code for vehicles, which are commonly available on the markets, is also selected automatically.

ISS

Intelligent System Scan (ISS) scans through all the systems in the vehicle and displays the fault codes that are stored in each system. This saves time and you get a quick overview of the actual status of the entire vehicle. When the ISS is complete, you can then select a specific control system to analyse the results further on.

ISI

Intelligent System Identification (ISI) identifies and selects automatically the type of controller that is mounted in the vehicle. This ensures that the diagnostic session is performed correctly with the correct parameters as required.

REPORT FUNCTION

Under this function tab, you will be able to see the adaptations and adjustments that are possible for a specific vehicle without having the vehicle near you. Together with the help texts as a guide, you can plan and be effective in your work; even under complex situations.

OBD-FUNCTIONS

CDP+ is equipped with an unique multiplexer technology, which allows it to be used on all types of vehicles, regardless of voltage levels and communication standards. For those vehicles that do not use the standard 16-pin connector, we offer a complete set of certified and customized adapter cables and kits.

UNIVERSAL

For most OBD functions, such as adjustments and programmings, there are detailed instructions and help texts to assist you in your diagnosis work. You will find step by step information about prerequisites, preparation and implementation of various functions; making even the most complex function simple to perform

HELP FUNCTION

For most OBD functions, such as adjustments and programmings, there are detailed instructions and help texts to assist you in your diagnosis work. You will find step by step information about prerequisites, preparation and implementation of various functions; making even the most complex function simple to perform.

Multi Color Indicator  
With the multi colour indicator on multidiag pro, you have full control of the diagnostic process. Different colors and sound communicates the status and the placement of the indicator allows you to see it from a far. For example, if the indicator alternates between blue and green the Multi-diag pro + is in communication with the vehicle control unit.

Connector with LED 
To locate the diagnostic connector in the vehicle with ease, even if it’s located in a dark and inaccessible place, there is a LED on the 16-pin connector to help you along. The location and the design allows the light to function even when using the adaptor cable for vehicles without a 16-pin diagnostic socket.

there is a guide to using the 150e with wurth wow. 

You need to copy and replace files from Wow>ac_diag>firmware to Delphi>firmware and then plug your interface to your car, start Delphi a update firmware manualy. When finished start WoW and update firmware as well manualy. Remember your ds150e interface must be plug in to your car an ignition must be on. Then it must work. 

Multidiag pro vs TCS CDP pro vs CAN CLIP vs autocom vs DDT2000

multidiag pro vs autocom

if you try autocom,you'll see that the top testers today...multidiag to various problems with drivers,codiffica injectors etc....autocom goes on the cars and trucks

The pass-trhu today works on texa and bosch for sure, the other I don't know, then multidiag has a unique function.

autocom better than multidiag for cars manufactured after 2000 year.
multidiag pro better than autocom for cars manufactured under 2000 year.
both good only for European cars
and for this using , try to have the both interfaces.

multi dialogue vs CDP (TCS CDP pro)

Only the shape and colour of the casing. What you should be looking for is the type of PCB inside, that is where the difference is. If you are buying ask to see pictures if the PCB. The links below show both sides of the single PCB that covers 99% of Cars. Make sure it has the two chips that are marked, they may also be red, maroon or cream in colour.

CAN Clip VS Multidiag Pro VS DDT2000

 I have the Can Clip it does all I need it to on my Megane as for diagnosing it will do it as long as you have a PC that includes its software. The main reason I got Clip is it covers all the rovers so the MRS, MGF, I can sort out when the car ever goes wrong and it never let me down.

About Multidiag Pro and Clip, I think the biggest difference is their vehicle coverage. Multidiag Pro is universal (works in a very large car brands), while Clip is for Renault cars. Besides, Multidiag Pro is cheaper than Clip.

The DDT2000 actually does not pass the test. I have got a MAF sensor disconnected and the software is not able to read it. It just states that no errors are present but in fact there is something going on. Then I plugged ELM327 scanner and run its software, there it is the fault present. For now the price is the only good thing, but so is the ELM327 cable and way more easy to use.

Final conclusion: 

Renualt CAN CLIP and Multidiag Pro are clearly above DDT2000 and both can do what DDT does. CAN Clip works good with Renault cars, Multidiag Pro supports other car brands. As a DIY-er, I would choose Renault CLIP without doubt. But, this rank may change if you own a car that works fully or almost fully in KWP protocol, cars before 2004 or so.

How to setup 2013.3 CDP Bluetooth on Windows 10

The system was working via Bluetooth under windows 8.1.

I cannot get Bluetooth to work since I upgraded to windows 10 ;(

Windows 10 Pairs the CPD ok and accepts a password of 1234 ok; however, the hardware detection software in Delphi 2013.3 fails to communicate.

I seem to be using the correct com port...
OBD11 paired with 1234 
Device manager says OBDII exists and is working 
Device manager says Port (Com & LPT) Standard Serial over Bluetooth link (Com17/Com18) and is upto date.

Delphi says that the Com17/18(BT) Unknown device

When I click test connection in the event log I see...

Administrative Events says :-The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (aa:bb:cc:11:22:33) failed.

So there must be some darn authentication mess up since updating to W10 

Windows 10 (build 10240)

Solved!! I found that when i set Compatibility mode Windows XP SP3 for WOW Bluetooth is working as expected!

HOW TO FORCE FLASH YOUR CDP+ BY USB

1.MAKE BRIDGE FOR BOOT0 - MCU IN BOOT MODE (LOOK AT PICTURES).Keep it until flash

procedure ends. This is in fact connection of legs 108 and 138 from STM32F2XX processor. Some

units have different PCB so you need to solder directly to the legs and make a connection between

them or find test points with multimeter.

2. Now you need to install and run "Flash Loader Demonstrator".

3. Connect your unit to USB and to power supply (OBD). It will light red this means boot0 active.

At the Flash Loader Demonstrator choose COM port nr that VCI is installed (check in device manager)

click NEXT- sometimes you need couple times try to have succesful connection.

Program will ask to erase content of MCU because it is secured.

When you will have connection with MCU you need choose type of MCU 1024K and on

next page "Download to device" check "global erase" and chose the firmware you want to put on

your cdp+.

Now press NEXT and wait about 10min.After this your CDP+ will work without problems.

CDP+ SINGLE BOARD - ENTER FORCED FLASH BOOT0 - LINK TP102 WITH

TP206 ON THIS PCB

CDP+ REV 2.0

Why TCS-CDP pro clone can't read BMW ECU [user solution]

I have recently purchased new TSC-CDP pro from China. Software supplied with its softwware 2014 release 2. The software installed and activated OK. i tested the unit and it passed the test OK; but unluckily, it does not communicate with any car... only use USB cable ( not bothered with Bluetooth). After vehicle selection, the system cannot read ECUs and generates silly error messages"Vehicle not responding (Fahrzeug antwortet nicht)". 

Error message:
Startup

Initiation of the tester... YES

Searching for the interface... YES

Establish communication... NO

(ISO 157656-4, SAW J1939-21)

Vehicle not responding

The vehicle is not responding to the diagnosis inquiry made. Please make sure that the tester is correctly connected to the vehicle and that the ignition is turned on, and try again to establish communication. If communication fails again, it is possible that the diagnosis function is not supported.

Software:

2014 release 2.

The software installed and activated OK...and tested the unit and it passed the test OK 

Hardware: (new VCI), Serial No.100251, eOBD 114, Firmware version 1423.

* First modification- FAILED!

I tested on Mercs and BMW. I opened the CDP unit and observed that two boards are not connected correctly. So, I pushed them together. This has improved a bit, as the unit now makes a clicking noise when connected to a car. Even can read the VIN, but on BMW failed to read the ECU. I will try later on a different car. But this is already a bad news (no BMWs). 

Then, I contacted the supplier and was informed that this TCS-CDP DOES NOT WORK with BMWs and Mercedes cars !!!!!

* Second modification- FAILED!

Then i was told that "the device actually does not work on any vehicle that uses SAE J1850 (PWM and VPW) because it has a fake OKI m6636 or it does not have it at all... The OKI chip is only for cars that support the PWM/VPWM protocol like Ford. BMW didn't use the PWM/VPWM protocol." And this user did fix the problem and used the same interface for all BMW cars..TCS CDP interface, removed from old devices like tv´s, radio´s etc. check all solder Joints of all components (especially relays)..

But I didn’t try that, and decided to purchase another TCS CDP from a different supplier. White this time... When it arrived I tested it immediately on the same BMW 7 E66… and guess what …. Same problems remained.

New TCS CDP white:

***** Third modification- Successfully SOLVED finally!

the problem with the m6636 is in the cdp pro, not in cdp+. replace the 2 diodes (D701 and D703) with 1n4148. back the pcb. 

Then gained the communication with BMW car which I could not communicate with before.

So, well DONE!

Ps. To avoid problems above, i recommend you all to buy the OK version as my friend used, without any issues so far. He bought this from

http://www.obdexpress.co.uk/wholesale/tcs-cdp-pro-diagnostic-bluetooth-a.html

it’s the best clone CDP from China

Multidiag pro/CDP car list: (try with luck)

Abarth, Acura, Alfa Romeo, Audi, Bentley, BMW, Cadillac, Chevrolet, Chrysler, Citroen, Dacia, Daewoo, DAF, Daihatsu, Dodge, Ferrari, Fiat, Ford (Europe), Freightliner, General Motors, GMC, Honda, Hummer, Hyunda, iIsuzu, Iveco, DVD, Jaguar, Jeep, Kia, Lamborghini, Lancia, Land Rover, Lexus, Lotus, Mahindra, MAN, Maserati, Mazda, Mercedes-Benz, Mercedes-Benz (Truck), MG, Mini, Mitsubishi, Nissan, OBDII, Opel, Peugeot, Porsche, Range Rover, Renault, Renault Trucks, Rolls-Royce, Rover, Saab, Scania, Seat, Skoda, Smart, Sprinter, Ssangyong, Subaru, Suzuki, Tata, Toyota, Vauxhall, Volkswagen, Volvo, Volvo Trucks

CDP+ Delphi Autocom Firmware Recovery, OTP Area, Firmwares

So i (@fantomel) was thinking these days to make a full pack at day regarding the the firmware our CDP+ interfaces.

As you all know we can flash our interface SAFE only inside Delphi 2012.3 (last version without clone blacklist) or in these days inside WOW (no matter what version).

We (at least me) prefer to write the firmware with WOW because like this i can use wow and delphi-autocom without problems since WOW writes some extra bits that delphi-autocom does not detect but wow does.

https://mega.co.nz/#F!aBgx0ajB!zX0vwWrLWGKvfLDb3hNsuQ


PASSWORD IF NEEDED IT'S: fantomel

Story short, what will you find inside this pack:

1. Mprog 3.5 and ept file for CDP+ (never seen one that has this problem)

2. How to recover your CDP+ from a bad flash or red lights problem via USB.

3. How to read your firmware with a ST-Link device via CDP+ J400 connector and also pinout of STLink to J400

4. How to read the OTP (One Time Programming) area responsable for the serial number of your interface - BE CAREFUL . This area can be modified only by incrementing the actual serial number in the already written ST chip or you can write any number in a new one if you know how.

5. Flash Loader Demonstrator v2.6.0 to restore your firmware via USB

6. STM32 ST-Link Utility v3.4.0 to read firmware and otp and if you are willing to risk to change them.

6. OTP area for CDP+ Clone 100251 bin file.

7. Firmware from programs: 1321 from WOW ;1331 from delphi, autocom, wow; 1410 from WOW, 1422 from Delphi and 1423 from Autocom.

8. Firmware recovery to flash your CDP+ interface in case of upgrade or bad flash:

a) Old ones already on web:2012.2; 2012.3; 2013.1; 2013.2.1; 2013.2.2; 2013.3.

b) My flash files written to CDP+ by WOW and read via ST-Link saved as .bin,.hex,.s19,.srec from my clone CDP+ FOR RECOVERY

2013.3 - Firmware 1331

2014.1 - Firmware 1410

2014.2 - Firmware 1422 from Delphi

2014.2 - Firmware 1423 from Autocom

9. 24.12.2014 Firmware 1430 from Autocom 2014 R3 2.14.3

10. 24.12.2014 New pack with RECOVERY FIRMWARE 1430 .bin,.hex,.s19,.srec included and all from 1->9

If you find something wrong or to add to this pack please write.

All you need to play with your CDP+ interface it's a ST-Link V2 Programmer CLONE like these HERE or the Original.

If you need a password for a file, like always it's fantomel

11. - 12.04.2015 - Added to MY COLLECTION for CDP and CDP+ Firmware 1513 from AUTOCOM 2015 R1 2.15.1 

12. - 12.04.2015 - Added MY COLLECTION for CDP and CDP+ where you will find all above + Complete Install kits to Delphi and Autocom 2013.3 , All my WOW 4 and 5 Collection, All Genuine Kits of 2014 and also The mixed 2014.1 Version with 2 patches(one already present in main archive and another one separated) - a little late but i forgot to post this also here.

13. - 20.04.2015 - Added to MY COLLECTION for CDP and CDP+ Firmware 1424 and 1430 from Wurth Group for WOW and W.EASY 

14. - 07.05.2015 - Added to MY COLLECTION for CDP and CDP+ Firmware 1515 from Wurth Group for WOW and W.EASY 

15. - 24.08.2015 - Added to MY COLLECTION for CDP and CDP+ Firmware 1520 from Delphi R2 2.15.2 

16. - 20.09.2015 - Added to MY COLLECTION for CDP and CDP+ Firmware 1521 from W.Easy WOW 

17. - 28.12.2015 - Added to MY COLLECTION for CDP and CDP+ Firmware 1532 from Autocom/Delphi 2016.0 

18. - 16.02.2016 - Added to MY COLLECTION for CDP and CDP+ Firmware 1532 from W.Easy WOW 

19. - 05.04.2016 - Added to MY COLLECTION for CDP and CDP+ Firmware 1534 & 1535 from W.Easy WOW 

20. - 03.06.2016 - Added to MY COLLECTION for CDP and CDP+ Firmware 1612 from Autocom/Delphi 2016.10 

21. - 08.08.2016 - Added to MY COLLECTION for CDP and CDP+ Firmware 1615 from W.Easy WOW 

22. - 15.10.2016 - Added to MY COLLECTION for CDP and CDP+ Firmware 1622 from W.Easy WOW and Autocom 2016.20 - Last fw for CDP interface since from 11.2016 is EOL

(BIG THANKS to fantomel, src: http://mhhauto.com/Thread-CDP-Delphi-Autocom-Firmware-Recovery-OTP-Area-Firmwares)


CDP PRO review:

- I get CDP+ double board s/n 100251. worked.

- I bought two CDP + from the same provider, I have wow, delphi, autocom, opus installed with the same firmware in all.

I tried them on another computer, both worked.

- I have delphi china 1pcb reworked and software 2014.3 work very good for all cars and truck


- Firmware from the Chinese is older than mine and mine works better in Wow, so I upgrade.
I have bought over 50 pieces from China and flash them without any problems.
I sell them in Sweden with the installation manual in Swedish and with a simplified installation process than that provided by the Chinese.

CDP PRO questions and answers:

problem with the m6636:

Q: the problem with the m6636 is in the cdp pro not in cdp+. replace the 2 diodes and check if it works. the 2 diodes is for bmw and maybe mercedes,honda ? and other ?

A: the 2 diodes are D701 and D703. back the pcb. you must replace it with 1n4148.  I have replaced these two diodes and gained the communication with BMW car which I could not communicate with before . So, well DONE 

not work with BMW / Mercedes:

Q: any solution for BMW with this CDP unit?

A: The OKI chip is only for cars that support the PWM/VPWM protocol like Ford. BMW didn't use the PWM/VPWM protocol. The info that the TCS CDP does not work with BMW and Mercedes is bullshit. 
I had the same problem with a lot of TCS CDP interfaces. You have to know that the components for TCS CDP interface, removed from old devices like tv´s, radio´s etc. check all solder Joints of all components (especially relays), so I have fixed the problem. I use the same interface for all BMW cars and it works without problems.

Q: I installed the wow wurth and delphi truck and car program on my personal computer at the workshop.
The delphi works with the 150e (model without bluetooth)
I would like to know if there is a guide to using the 150e with wurth wow. 

A: You need to copy and replace files from Wow>ac_diag>firmware to Delphi>firmware and then plug your interface to your car, start Delphi a update firmware manualy. When finished start WoW and update firmware as well manualy. Remember your ds150e interface must be plug in to your car an ignition must be on. Then it must work. 

Q: The firmware inside wow can be flash the vci delphi? But if i change software (delphi wow or wow delphi) i need to write firmware anytime?

A: You need to copy WOW firmware to Delphi folder(no  Delphi to WOW).
Just download any WoW firmware (best 1430) from fantomel post http://mhhauto.com/Thread-Wurth-WoW-5-00...#pid347845 and copy all files into Wow>ac_diag>firmware and to Delphi>firmware as well and then plug your interface to your car, start Delphi a update firmware manualy by pressing the update button in the software. Remember when you do update firmware, your interface must be plug in to your car an ignition must be on. If you do it this way, your interface will work with WoW, Delphi and Autocom.

Q: Can you post a picture of the vci motherboard with bluetooth? Because I disassembled it to see if it was bluetooth but I did not see bluetooth central hardware. I sold it as bluetooth

A: Bluetooth don't work well for me. Use cable connection, it's more stable.

Q: And the last question what type of original mark of diagnose are compatibilities? 
A: To see what firmware is in your software go to C:\wow5.00.8\ac_diagnosis_module\firmware and open this Firm.info with notepad. you will see this:

firmware_version_vci=1430
firmware_version_vci_plus=1430
firmware_version_weasy_plus=1430
firmware_version_eobd_vci=217
firmware_version_eobd_vci_plus=115
firmware_version_eobd_weasy_plus=115

My firmware is 1430 but your can be different. 

Good luck.

TCS CDP+ review:

Hello.
as i promissed i am sharing the feedback of updating from 2013.1 to 2013.3 + steps folowed:
1) dezinstal 2013.1 ;2)certificate removal ;3) Driver dezinstal from Device manager ; 4) CC cleaner for Reg file ; 4) deleting all files from prog files, usser doccuments app etc.
Clean instal of 2013.3 + full activation ( pease use only the original soft from delphi.europe) and apply the patch than activate with the full keygen. 
The firmware update was performed over USB and it was performed in 2.5 minutes with a success message at the end.
Car tested : Focus 2007 - 100% ok- ABS now is working - i do not have to switch to 2005 year 
VW golf 5 - 1.6 bse - 100% - ok - they have added also freeze frame.
Than i have tested EOBD and Advanced Eobd.- 100 % success.
Atention: please check and recheck the USB cable- normaly i am using BT, and when is test it , the chinese USB cable( it was sealed - 100% new) was deffective - somewere in the main connector.It disconect the VCI when i was moving it. Than i have ussed my printer cable and it worked perfectly.
My clone DS150E CDP+ new vc, I have open it and checked the soldering , "can filters". , switches - NEC ; and all it seems to be in place even after 250 diagnostics. Indeed my seler was sending quality A of the board.

poligrafika : it is about an software problem. You have to choose 2013.3 or 2013.1. For my side i am more intrested in ford B max and Renault 0.9 ; 1.2 TCE engines.

source:

http://www.obdexpress.co.uk/search/?q=multidiag

NEWS: Renault CAN CLiP updated to version 170


Renault CAN CLiP Youtube video: https://youtu.be/1dwg59BCSOQ
Renault CAN CLiP forum: http://www.topix.com/forum/autos/T62RC8FEVJQ96J9FN
Renault CAN CLiP manual: http://obd2-diag.blogspot.com/p/renault-can-clip.html