[kmfspb]

Good afternoon friends.
I followed the installation guidelines.
VAS5054A works correctly: W211, W245


But when I connect for example W212, W213 new models, the light on the device doesn't even light up on me. and when passing the test it shows: - RED dot: PC <-> VAS5054A does not communicate. Something wrong on your driver.

The device in the device manager is displayed like this:




Any ideas?

[getaibose]

Amazing work medianjoe!

Today, I tested this with Xentry OpenShell 7.2019 on a W176 - works very well

[andi8513]

Hello, I tried on two cars, and communicates only with the engine. Does this mean that vas5054a works only through can and not k-line?

       

[medianjoe]

Hello, I tried on two cars, and communicates only with the engine. Does this mean that vas5054a works only through can and not k-line?

The models (W203, W220) might be too old to support full path thru mode. Later models do all functions.

[Mini Tool]

Run "SftngCM.exe" on desktop as administrator but Fault ERROR
i Make a "C:\Temp" directory if not exists. but not works please help me

[Marko1337]

Hey guys, I hope somebody can help me with this Problem, because I have been trying to fix it for days.

I Installed Xentry 3/2019 on my Laptop with Windows 10 - 64bit and used the Xentry Patcher from Blue sky to activate Xentry and Patch everything. So far so good, then after some playing around I managed to get the SftingCM.exe to recognize my vas5054a with the green light, and everything should be working there too.

So when I launch Xentry the Window from SelectPTDevice.exe doesn't show up, and I cant select the Vas5054, but I think that could be because the VAS is the only available Device installed on the PC.

But my real Problem is, that when i try to test a Vehicle (w211) in Xentry, it automatically goes into DAS, which it should, but DAS gives me an error, where it describes that the Application could not Communicate with the Multiplexer.

Edit:
I fixed it, had to reinstall xentry

[no_name]

Thanks worked for me, both on Xentry and Forscan...
Only issue is that I get on softing EDIC error, both on BT and USB: Device is not accessible. But I think issue here is BT is not ori since I cannot manage buzzer settings...

Anyway thanks a lot!