(, 12:15 PM)Huntsman2 Wrote: 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.Any ideas people?P.S. The system works using a USB lead in windows 10You may not have the correct com port number selected in the hardware setup section under settings in Delphi software, do you have usb/bt selected or bluetooth direct selected. You say the cdp pairs with a password of 1234, so when it is paired look in device manager in control panel of windows 10 to find out what com port number the interface has been allocated, then go back to your Delphi software select usb/bt in the hardware setup section and then select the correct com port number, then hit the test button to see if it finds your interface. Do all this without the usb cable connected so you are just using bluetooth on its own.
If all the above fails might be worth trying a firmware update again or even uninstalling Delphi software and doing a fresh install of the Delphi software. I personally have not had any problems with the Delphi siftware when upgrading laptops from windows 8.1 to Windows 10, only problems i have ever had after the upgrade have been delphi becoming deactivated, so having to just activate the software again. King Cat,I seem to be using the correct com port.OBD11 paired with 1234Device manager says OBDII exists and is workingDevice manager says Port (Com & LPT) Standard Serial over Bluetooth link (Com17/Com18) and is upto date.Delphi says that the Com17/18(BT) Unknown deviceWhen 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 W10Windows 10 (build 10240). (, 03:49 AM)king cat Wrote: (, 12:15 PM)Huntsman2 Wrote: 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.Any ideas people?P.S. The system works using a USB lead in windows 10You may not have the correct com port number selected in the hardware setup section under settings in Delphi software, do you have usb/bt selected or bluetooth direct selected. You say the cdp pairs with a password of 1234, so when it is paired look in device manager in control panel of windows 10 to find out what com port number the interface has been allocated, then go back to your Delphi software select usb/bt in the hardware setup section and then select the correct com port number, then hit the test button to see if it finds your interface.
Do all this without the usb cable connected so you are just using bluetooth on its own. If all the above fails might be worth trying a firmware update again or even uninstalling Delphi software and doing a fresh install of the Delphi software. I personally have not had any problems with the Delphi siftware when upgrading laptops from windows 8.1 to Windows 10, only problems i have ever had after the upgrade have been delphi becoming deactivated, so having to just activate the software again.Hi mate, have you tried connecting a different device for example a mobile phone etc to your bluetooth Windows 10 laptop to see if it can pair and receive files? Is the bluetooth device a mini pci board on the laptop or are you using a plug in USB bluetooth dongle?
I would try uninstalling the device drivers for your bluetooth device in device manager and then reinstalling the drivers to see if you have success. Also may be worth trying a third party bluetooth suite like bluesoleil to see if you can get it to connect. If the bluetooth module is on baord (mini pci) go the manufacturers web site for the bluetooth card and check to see if there is an updated driver available for windows 10 for the bluetooth device.
Autocom/delphi 2016.00 Keygen V1
If after installation the problem occurs, the VCI is not recognized or only partially.check1. PC cable not properly connected to the tester.2. Power cable is not connected to tester3. Incorrect Com Port selected1. Lookup whether the inserted VCI VCI has been recognized under a Comport - yes - com port select, if not please reinstall drivers.
Autocom Keygen For Windows 7
(Control Panel)2. OBD connector from VCi not connected to the vehicle, no power supply 12V for VCI.3. Wrong ID at the beginning of the installation: for example. For CDP rather than A-710-479 was a CDP-710-142 for CDP + then input comes the mistake is not recognized.4. Incorrect serial number for the VCI.
Change the VCI serial and HW Key in the installations.xlm make new activation and VCI run fine.5. USB cable is defective, broken, or cross-section of cable too small, take thicker USB cable.6. Firmware broken: re-record with Flash loader demonstrator.7. VCI has polluted or cold solder joints, take the VCI apart and solder / clean.Message 'Communication Error vehicle is not responding'USB jack soldered incorrectly. 12V not okay.
If the VCI has 2 boards then they are not put together correctly.check.Message: 'Unknown Serial Number Please check whether the installed version for their VCI-type is valid'Incorrect Main.exe copied / installed, patch 'Main.exe' copy back into the installation directoryImportant for Windows 64-bit versions:If you have a 64 bit Windows system on the computer then you have after installing the Delphi folder or Autocom in the following directory copying: C: / Program Files (x86) then the program will run without any problems. If this is not done has to when every time you start over again the first configuration screen.If the Delphi / Autocom folder in the directory C: / Program Files (x86) has been moved then just a new shortcut on the desktop to create and launch.After installing the error comes:'Installation of product ducuments failed! The installation will quit'dotnetfx 4.0' installed. With this version definitely takes the above-mentioned error during installation.' Dotnetfx3.5' install and the installation is running.If I helped you do not forget to thank and reputation:-).