[razzo]

You need Win7 for Vas5054. Old interfaces that used to work in older ODIS versions can sometimes work in 4.2.3 by using this trick:
1) install the for your interface latest working ODIS + PDU API
2) check again if this pdu api is working for your interface by using the PDU api test application
3) copy this directory: prog files/softing/pduapi/xxVERSIONxx/vecom/vas5054
4) uninstall this old odis and old pdu api
5) make sure everything is removed (if needed delete directories manually)
6) install new odis 4.2.3
7) replace the files in the prog files/softing/pduapi/xxNEWVERSIONxx/vecom/vas5054 by the old files from step 3. Don't change the 'xxNEWVERSIONxx' directory name.
8) repeat step 2
9) launch ODIS and enjoy.

[fantomel]

Sometimes meaning you are wrong. We are talinkg about very old firmware 1.20.020 and today we are at 1.20.41 or 1.20.42. How do you expect that old firmware to work ok on new programs with another structure?
Do you think VAG and Softing are fools and did upgrade of firmwares just to play?

Shit bluetooth, want it to work ok, use old program not new one. All rest is just smoke

Want to use all programs new and old find one AMB2300 good module and use it or a good vas head.

[kiranabc]

Just update the firmware and all is fine

best regards

[razzo]

Sometimes meaning you are wrong. We are talinkg about very old firmware 1.20.020 and today we are at 1.20.41 or 1.20.42. How do you expect that old firmware to work ok on new programs with another structure?
Do you think VAG and Softing are fools and did upgrade of firmwares just to play?

Shit bluetooth, want it to work ok, use old program not new one. All rest is just smoke

Want to use all programs new and old find one AMB2300 good module and use it or a good vas head.

Seems like you are wrong on this one... I own two interfaces, one with the crappy bluetooth module and a new interface with everything on it. As a matter of fact, the old module with crappy bluetooth module is functional on 4.2.3 when using the older PDU API file trick (don't know which version it was anymore). I tried this 'crappy' module with ODIS 4.2.3 on many cars, even newer ones. I'm not only talking about reading for faults, but also GFF, adaptations, offline interactive functions, reading measurement blocks, running test programs, flashing (in new ODIS-E) and so on... I never noticed anything that wasn't working on ODIS-S 4.2.3 with that 'crappy' module. BTW I never use the prehistoric technology called bluetooth anyway. So I'm sure for some people this could be a solution. Is it a good solution? Of course not. That's why I bought the new interface. But you can never say it's a good solution to use clone devices anyway.

[asztalos]

Please...can you provide me firmware and eventually also the procedure how to make firmware update on VAS 5054A ?
I got my chinese order and the interface is not working. Thanks!

[karlfrosch]

Hi Guys,

i need a bit help from the spacialists here. I have Win7x86 and a clone 5054a good or not i don´t know but it works with odis 4.1.4 in the past. I installed odis 5.0.6 replaced the dpu api verion with 1.20.041 but odis can´t detect the ignition status and wont connect to the car. in the api test app the ignition is detected correctly. what can i do to get this thing working?

kind regards.

EDIT: Solution found:

After replacing dpu api to v 1.20.041 its needed to edit the file C:\ODIS-DIAG-MODULES\MCD-SERVER\VWMCD\MCD3D_Server.ini

find MCD3D_MVCI_PDU_API_Shortname="D_PDU_API_DSA" and edit like this
MCD3D_MVCI_PDU_API_Shortname="EDIC_D_PDU_API_1_20_041"

the correct shortname is in file C:\ProgramData\D-PDU API\ pdu_api_root.xml the part with the 1.20.041 drivers

Now System is working