How to setup VAS5054A PassThru Driver for Xentry Windows 10 x64

Something good to help you to make Xentry PassThru on Windows 10 x64 support new Mercedes models (Euro5/6, W205, W213, W222). Done with VAS5054A PassThru Driver

Xentry PassThru needs to be installed on Windows x64 to support new models, such as Euro5/6, W205, W213, W222 … However, VAS5054A didn’t work on 64bits as passthru. There is 64bits device driver for VAS5054A but there is no PassThru driver working on 64bits. You may try Actia driver instead but this is a patched 32bits PassThru API files with 64bit device drivers working on Windows 10 x64. Xentry recognizes it and works with W205 (confirmed), etc.

WARNING: Use it on your own risk, only for test purpose.

What you need:

(1) VAS5054A Bluetooth hardware. (genuine and good clone… both ok)
(2) (option) VAS5054A EDIC_PDU_API 1.20.4x driver installation file. You can find it somewhere on this forum.
(3) (option) New firmware. The firmware included here is version 1.20.41 for better compatibility, not 1.20.42.
(4) Softing_VAS5054A_PassThru_Driver_x64_v3.zip (attached here)
(5) 64bit Windows 10
(6) (option) DC 12V power adapter, 2 jumper wires for temporary power.

Pre Installation:

(1) Install Xentry PassThru and do all patches.
(2) (option) Install EDIC_PDU_API 1_20_42 driver (or EDIC_PDU_API 1_20_41). It’s for installing .NET framework or VC++ redistribution files.

If you are going to do clean install on fresh Windows 10, you might want to install the EDIC_PDU driver first. It installs .NET framework, VC++ files, some EDIC DLLs on /Windows/System32 or SysWow64. Other files will be overwritten by the below manual installation. 

Installation:

(1) Copy “Program Files (x86)\Softing\*” to your HDD “C:\Program Files (x86)\Softing\*”
(2) Copy “Program Data\D-PDU API” to your HDD “C:\Program Data\D-PDU API”.
(3) Double click on “Softing_VAS5054A_PassThru_1_20_042.reg” and install it.
(4) Make a shortcut of “SftngCM.exe” on Desktop.
(5) Right click on “C:\Program Files (x86)\Softing\EdicDriver\win7\softingedic7_ntamd64.inf” and install.
(6) Connect the VAS5054A hardware using an USB cable. Connect it to a temporary power(12V DC adapter) or OBD-2 port.
(7) Check “Control Panel/Devices Manager/Softing…”. If not installed correctly, update the device driver manually.
(8) Make a shortcut of “EDICConfig.exe” on Desktop.
(9) (option) If you have newer version than EDIC_PDU_API 1_20_42 driver and genuine VAS5054A hardware, you may install the API driver now.

Post Installation:

(1) Connect the VAS 5054a to a temporary power(12V DC adapter) or ODB-2 port.
(2) Run “SftngCM.exe” on desktop as administrator. Make a “C:\Temp” directory if not exists. This is for saving log files. If not exists, SftingCM.exe will cause error when doing test.
(3) Choose “VAS5054A” and type the serial number (maybe 0821xxxxx).
(4) Select “Test” and click on “Start Test”.
– RED dot : PC <-> VAS5054A does not communicate. Something wrong on your driver.
– YELLOW dot : PC <-> VAS5054A communicates.
– GREEN dot : PC <-> VAS5054A <-> Vehicle communicates.

Tip:

(1) “.NET Framework 2.0/3.0/3.5” needs to be installed if not installed automatically. You can install it by selecting on “Control Panel/Programs and Features/Turn Windows features on or off/.NET Framework 3.5(includes .NET 2.0 and 3.0)”. You also need to install VC++ redistributions if not done yet. (MSVCR100.dll, mfc100.dll, … errors)

(2) Temporary power to VAS5054A for test purpose : Ground to either pin 4 or 5. 12V DC to pin 16.

(3) You can upgrade the EDICDriver in “Program Files (x86)\Softing\EDICDriver” if you have newer version. Update the device driver on control panel.

(4) If you installed newer version EDIC_PDU_API driver than 1.20.42, edit the *.reg and change the number 1_20_42 to your number (for example, “EDIC_D_PDU_API_1_20_042” to “EDIC_D_PDU_API_1_20_0XX”). After editing, double click on it and install it again.

(5) If your device has different serial number but SftngCM.exe doesn’t allow the change, edit the *.reg file with text editor, double click on it and install it again.

Download:

Softing_VAS5054A_PassThru_Driver_x64_v3.zip

https://mega.nz/#!kfYHwahA!xws-PzV8xZaPhwgZ1bwOxr4vLpMVBIvr4SceQGclvgw

http://blog.obdii365.com/2019/03/10/make-xentry-passthru-work-for-new-models/

Benz W215 2003 diagnosis with DTS Monaco or Vediamo

This is for those maybe interested getting DTS 8 or Vediamo v5 working on 2003 Mercedes later.

My configuration:
X230 Lenovo
SD connect C4
No Xentry nor DAS (it seems better to not install this as it can created more probles in test phase)
Just InstallSDconnectToolkit 2.1.30 also have 2.1.14 but not installed (maybe should I use 2.1.14 ? )
and DTS Monaco 8.08.021
IP4 set to 172.29.127.100 255.255.255.0 dns 8.8.8.8

My actual settings:

Set up 2 computers for testing:
computer 1)  vediamo 4.02.02  on XP Xentry 09.2014
computer 2) DTS 8.08.21 on Windows 7 x32 clean NO Xentry, No Vediamo, with a custom 2.1.7.1 Toolkit and ToolkitApiDll_4.0.dll in sytem32

Vehicle: W215 2003 V12 Biturbo

Problem:

I found several source with W215 folder and 1 works, but partially
On the picture you can see, once I apply filter, these are the only few that connect

Only these ecus above turn green

other 20-30 not

Solution:

The solution in understanding that in 2003 year where there’s no any Vediamo and DTS8

Free solution is using DAS. It solves 99.99% tasks in this kind of vehicles.
Not free solution use other hardware and software.

From Vediamo manual:

CaesarGo: This firmware usually runs directly in the non-volatile memory of your CAESAR hardware, e.g., in Part A or Part Y. Supports older communication protocols as well, e.g., KWFB. The new UDS protocol is not supported.
TLSlave: This firmware runs on the computer used. The faster the computer, the quicker the different communication tasks can be completed (e.g., flash processes). Also allows the simultaneous opening of up to 50 CAN channels. This firmware supports “newer” protocols as well, e.g., UDS.

Good to know: CBF files is not about K-Line. CBF file use also W212 for example. Try to use Vediamo 4 for K-Line ecus.

For newbies: if you are not good at DTS or Vediamo settings, you could get a disk that installed all Mercedes software (Xentry/DAS, DTS, Vediamo, EPC, WIS, etc) before delivery. Tested successfully and plug-and-play!

Look here:

SSD version: http://www.obdii365.com/wholesale/2019-03-mb-star-software-ssd.html (runs faster and more stable)

HDD version: http://www.obdii365.com/wholesale/2019-03-mb-sd-connect-c4-hdd.html

Chart: explains the reason why many are looking for DTS

DTS-monaco vs. Vediamo
Functions	DTS monaco	Vediamo
All cars have one key code access	Yes	No
Vehicle control unit software, One key storage	Yes	No
Car fault codes reading	Yes	No
Data exchange	Yes	No
Quick test	Yes	No
Single control unit keys off-set code	Yes	No
Offline programming	Yes	Yes
Increase reduced SA codes	Yes	Yes
Personalize the control unit parameters	Yes	Yes

Definitely, DTS-monaco wins!

http://blog.obdii365.com/2019/03/05/w215-2003-k-line-diagnosis-dts-monaco-or-vediamo/