Car OBD2 Tools global one-stop shopping supplier
--OBDexpress.co.uk is a professional OBD2 tool online seller supplies car truck diagnostic tools, car ECU programmer,car key programmer, mileage correction tool, airbag reset tool, ECU chip tunning and Provide good service
NOTICE：
Before doing the MQB model car, you must first read the dashboard information to distinguish whether it is a VDO dashboard or not.
The MQB function support most the VDO dashboard, if the car you have done doesn't support programming or dashboard odometer adjustment, please give us feedback or you can try for the online programming.
This function does not support the JCI dashboard offline programming no matter which car and year, but you can try using the online programming to do.
(Online need to charge).
Part 1. How to use Ford UCDS Pro+ V1.26.008 Full license?
There is no user manual, but obdexpress.co.uk made a test video and uploaded on Youtube:
Works on XP (try WIN7 8 10 as you will).
Part 2. Ford UCDS Pro+ V1.26.008 Test Results
- full mode activated, access to existing sections of the software, such as: VBF Loader, Update Wizard and Direct Config.
- with 35 tokens: token only need for mileage programming & ECU chip tuning function.
- Support the reconfiguration of the car, the engine firmware stock firmware
Ford UCDS Pro+ V1.26.008 VS VCMII
1) Data
UCDS 1.26.008 = Ford VCMII IDS
2) online and offline programming
UCDS 1.26.008: Yes
Ford VCMII IDS: Yes
3) special functions like: VBF LOADER, UPDATE WIZARD, DIRECT CONFIG
UCDS 1.26.008: Yes
Ford VCMII IDS: No
4) Vehicle coverage:
UCDS > VCMII IDS
5) odometer correction
UCDS 1.26.008: Yes
Ford VCMII IDS: No
6) the reconfiguration of the car, the engine firmware stock firmware, chip tuning
UCDS 1.26.008: Yes
Ford VCMII IDS: No
7) key programming
UCDS 1.26.008: No
Ford VCMII IDS: Yes
8) Price
UCDS 1.26.008 < VCMII IDS
The price of UCDS 1.26.008 is one-half of VCMII IDS UCDS 1.26.008: €41.99 best VCMII: €109
Part 4. Ford UCDS Pro+ V1.26.008 technical issues and solutions First Issue: The laptop ONLY runs in AHCI mode and UIDE won’t ‘talk’ to AHCI disks. Solution:
I took your Windows XPSP3 CD and installed it on an old PC – this worked fine. Ghost-Windows-XP-Professional-SP3.zip (620.8MB)
1). Type CDROM.BAT
2). CDROM.BAT Contents
3). Type Command for UIDE
4). UIDE Error
However, as stated right from the beginning, the UCDS CD DOES NOT CONTAIN A DRIVER! Therefore the cable will not work.
I have been working on and repairing PCs for over 30 years. There is something missing from your setup. More issues and solutions:
Windows XP Service Pack 3 (your .NRG file) is not needed. UCDS runs perfectly on Windows 7.
If someone uses your .NRG, you should warn them it wipes the hard disk and takes over sole use of the computer.
Your .NRG is not compatible with computers that only use the AHCI interface (specifically UIDE only ‘talks’ to legacy IDE interfaces).
You can get around this by doing the first boot (when pressing ‘A’) by putting the .NRG disk and your HDD into a compatible PC. When it is going to reboot, switch off and put everything back into the original laptop. XP SP3 is fine with AHCI, it’s just your .NRG disk that is not.
Remember the errors that I sent you. Memorise them. They mean that your CD IS CORRUPT. I downloaded the UCDS1.26.008 software from another website and it works PERFECTLY on WINDOWS 7, FIRST TIME – including installing the DRIVERS.
Part 5: How to use Ford UCDS adapter with Forscan?
Confirmed: A lot of FORScan users successfully use it UCDS adapter with Forscan.
The method: If you've got the UCDS adapter drivers loaded you should see it listed in FORScan settings, connection tab under J2534 Adapters section.
Some new drivers needed? I have the v3 UCDS adapter and after I installed the drivers it showed up automatically in FORScan for me and works on my Windows 8 & 10 laptop.
The meaning for an UCDS v3 adapter with Forscan:
It means that if you use UCDS v3 and it doesn't work with FORScan, copy ftd2xx.dll from UCDS exe folder to FORScan exe folder. This is an incorrect J2534 library implementation by UCDS, and not a problem of FORScan. Also, if you have FTDI drivers installed in your system (so ftd2xx.dll is available in Windows system folder) everything should work "out of the box". This is why it works "out of the box" for some people (who seems to have FTDI drivers installed) and doesn't work for others (who have no FTDI drivers installed).
Tips and guides on Ford UCDS adapter connection with Forscan:
FORScan implements standard J2534 Passthru API to access J2534 Passthru adapters, no matter if it is UCDS , Ford VCMII, CanTieCar, Tactrix OpenPort, Vxdiag VCX Nano etc . Yes, different adapters implement some aspects of J2534 standard differently, so we periodically fix J2534 issues in FORScan. For example, in latest versions we added J2534 message send timeout that, as realized later, doesn't work properly in adapters like VXDIAG Nano (makes them extremely slow). We are going to fix it in the next release. But connection procedure is quite simple and straightforward. This procedure in FORScan works well and not changed for months if not years. Connection issues, if any, most likely caused by adapter or it's drivers.
As for UCDS, we researched connection problem with this adapter several months ago and found out the following:
Old versions of UCDS (v2?) had problem with J2534 drivers. FORScan was able to access the DLL that implements J2534 API (ucdsj2534.dll) in a standard way. But this library had additional dependencies (unknown for FORScan and other s/w) - libusb0.dll and ftd2xx.dll available in the same folder. This is incorrect driver implementation, However it can be fixed quite easily by copying the libusb0.dll and ftd2xx.dll from UCDS folder to any place FORScan can access it - either in Windows DLL system folder or in FORScan EXE folder.
New versions of UCDS (v3) seems to have no libusb0.dll dependency anymore, but ftd2xx.dll dependecy still exists. FORScan has NO ftd2xx.dll distributed, it uses FTDI drivers installed in the system, if any. So if there are no FTDI drivers installed in the system (so FORScan can reach this DLL in Windows system DLL folder), FORScan may not be able to access UCDS J2534 API. Again, we consider it incorrect J2534 API implementation. However it can be easily fixed by copying ftd2xx.dll from UCDS folder to FORScan EXE folder.
New UCDS versions have complex anti-piracy protection system. In our tests we noticed that couple of times FORScan was unable to connect to UCDS until we ran native UCDS software that connected to their server and verified the license, also enabled CAN mode ON.
How to install V2018.3 (43.06) Actia Multi-Diag Office on Win7 sp1 x32 (without activation). It is running well with J2534 PassThru device to diagnose all cars up to 2018 such as VW Passat VIII (2015-2018).
Car model and year for test: VW Passat VIII (2015-2018)
V2018.3 (43.06) Actia Multi-Diag Office install on win7 and diagnose VW Passat VIII (2015-2018):
Video first:
Then Images and words' explanation:
Open "Daemon Tools Lite" as administrator.
Select language, then Next ->I agree -> Next.
Free license.
Next
Not install Google Chrome.
Next
Install.
Get a windows message "Device driver software installed successfully".
Install Desktop Gadgets.
Finish The Daemon Tools Lite setup wizard.
1) Open DVD multidiag 2018, copy "Crack" on the desktop.
2) run ACTIA_NET_BLOCK.bat (Run as administrator if possible)
3) run Activation MAJ MD 033918/keyUpdate (Run as administrator if possible).
Install Actia Multidiag Standard Profil (if the case, use S/N: 033918 instead of xxxxxxx)
RESTART COMPUTER after installation finished.
Go to C:\ACTIA\Portal, Remove Wget.exe
Go to control panel -> uninstall or change a program -> there are 3 drivers made by ACTIA. Remove all 3 drivers.
Then: (supplier told me it is optional, I have done it anyway)
Go to C:\ACTIA\Portal\chrome\multidiag\content\scripts
Open in a text editor file multidiag.js
Go to line "var showWarningPT1Window=true" and make this line like
"var showWarningPT1Window=false"
Save " multidiag.txt" Rename " multidiag.txt" as " multidiag. js "
The answer is it’s not possible to downgrade if using micropod ii clone .
downgrade is not a simple process and sometimes bad quality clone may be lost. downgrade is needed in next situations: return from witech 2 to witech 1. make vci pod/micropod compatible with cda. if micropod setup utility failed during update.
Supposing your got Witech 2.0 warning:
“This vehicle is supported by wiTECH 2.o software. This vehicle is no longer supported by wiTECH 1.0. Please use wiTech 2.0 to service this vehicle. You will return to discovery. ”
Wrong solution:
To update to wiTECH 2.o software from wiTECH 1.o
You may think you have online account and tried to update, actually it will have risk of being locked by Chrysler server or you can’t downgrade anymore.
Vocom II interface Vs. Vocom I interface:
Improved LED indicators
Improved quality of cables
Military standard on connectors
Better liquid and dust ingress protectors
Metal casing and rubber bumpers for better protection
Operates from -40 Celsius to +85 Celsius
Shock resistance: 2 meters Here we go for changing Volvo Truck's Chassis ID in TechTool Offline:
Click on "Tech tool" icon.
Tick off "Work offline", then click on "OK".
Version 2, FH12. Vocom II(USB) s connected to the computer.
Product data: collecting parameter data...
Click on "Diagnose" and get DTCs.
Click on "Program", then "Service and maintenance".
Parameter, programming.
All levels -> Start -> tick off "the engine must be switched off" and "The parking brake must be applied".
Read data from the control units...
Chassis ID B 220228
Open "Tech Tool" to enter "Chassis", then click on "Chassis ID", then "Set Programmable", then "OK" (Parameter is stetted for programming).
Click on "Stop", then "Start", tick off "the engine must be switched off" and "The parking brake must be applied".
Reading data from the control units.
Set the new chassis ID to B444444, click on "Program".
Use current chassis ID B 444444.
Have new Chassis ID B 444444, Model FH12, Version 2. Vocom II (USB) s connected to the computer.
Product data: collecting parameter data...
Job is done.
