How to solve TCSCDP DS150 Unknown diagnostic id error

I bought a TCSCDP DS150 Bluetooth pro scan tool from EOBD2.fr in late November and received it last Thursday. The tool looks neat and works fine. But when I connected it to my 05 BMW X3 via Bluetooth, something seemed wrong. I got a message “Unknown diagnostic id. Generic protocol with standard information will be used”. I disassemble the CDP 150 and but had no idea where to start. Then I sent the seller an email and it provided me a solution that finally got the issue fixed.
1252001

image002
According to the seller, there are some gadgets I should check. The first are the marked parts on the PCB showed in the following picture.
image003
Second are the FTDI chips marked in below picture.
image004
Third is the 513A 0523 IC (integrated circuit) which works as a bridge to connect TCSCDP DS150 Bluetooth and BMW vehicles.
image005
Finally, the diode GEX28A marked in red circle.
image006
I checked all the parts and found out that the diode GEX28A was a little bit loose. I removed it and soldered it back. Then I tried the Bluetooth connection again. It would work! If your CDP DS150 has the same issue, like mine, a little soldering may fix it. If you do not know how to do the soldering, you had better get a professional.

FGTech 2 “Can not find driver”,how to do?

Problem:
When install FGTech 2, the FTReadWrite replied “Can’t find device” error message. When trying to uninstall the driver, the window screen warmed it is not FGTECH device, but USB-to-Serial device. If install the driver, fgtech software did not run and FTReadWrite or MProg didn’t find the ftdi chip. Try to install the driver on both win 7 and win xp computer over and over, but in vain.
Solution:
1) Download and install the Virtual Com Port drivers from FTDI website:
Virtual COM Port Drivers
http://www.ftdichip.com/Drivers/VCP.htm
2) Then connect the FGTech to computer via USB port which had no device programmed and 1 blank device when the MProg Utility it shows.
NOTE: If you had backup and reprogram with the ept file. The system will not recognize the FGTECH Galletto 2 and will not reprogram the firmware bin file. The Virtual Com Port Drivers would overlay the fgtech ECU programmer. Then you have to again download the related driver in FTDI website.
CMD Uninstaller 1.4
http://www.ftdichip.com/Support/Utilities.htm
3) After install the right drivers, FTReadWrite programmed the backup firmware file, run FGTech software by referring to the user manual on EOBD2 webpage.