[fabrice17n]

Hello friends. I have buy 2 vas 5054 with amb2300 but chip in 55 ns.i have flash the firmware and it has crashed. Possible causes the chip are 55 ns and not 10ns ? And what can i do now for flash it manually ? Thanks you

[intruder]

I can get my hands on OEM VAS 5054, if anyone need i can take pictures and share.
Its from 4 years ago, when we open VW service.

[fabrice17n]

I have a clone from about 3 years. I think the chip are 10 ns.and the clone has crashed 55 ns. Can be the reason of firmware upgrade crash ? Now i must flash the firmware in the infineon chip ? And with which tool ?

[1 6 D]

Does somebody have photos of rear side PCD from BT modules? I have two VAS5054, first is blue PCD with 1 RAM k6x4016c3f-uf55, without OKI and TJA and A5780A, but with BT like AMB, second is green PCB with 2 RAM k6r4016v1d, OKI, TJA, but with BT CSR. One time I add second RAM and TJA but I haven't seen that something is better.

My CSR module have only 2 resistors on rear side, not 4 like in one from photos in this thread. Maybe I should swap blue PCD BT to breen PCB VAS and then update firmware for ODIS?

First one (blue PCB with AMB) doesn't work with UDS only works with VAS v19.01.01, in second (green PCB with CSR) UDS works in VAS v19.01.01 and it works with ODIS E 5.0.14.

I will make some photos of both PCB and somebody will tell me which components show I use to make one good device?

[1 6 D]

Here are photos of both VAS which I have, how can I make one good piece?

[mattydr67]

Try blue PCB AMB bluetooth in VAS green PCB
Check if you can upgrade/downgrade the firmware
Good luck

[1 6 D]

So I changed BT PCB, have installed D-PDU API 1.20.23, still I have D-PDU API 1.10.48 for VAS on my laptop. I have choice like in attachment. when I choose 1_10_48 I click "Parse MDF File", choose "VAS5054.... " which is the only one. Then PDUModuleConnect and there are all informations.

Log looks:

************ Getting MVCI Module paths *************

Root description file contains 2 MVCI modules.

*********** Changing the PDU-API module ************

----------------------------------------------------
Selected MVCI module: EDIC_D_PDU_API_1_10_048
----------------------------------------------------
PDU-API dll:
C:\PDU-API\Softing\1.10.048\vecom\PDUAPI_SoftingAG_1.10.048.dll
PDU-API ModuleDescriptionFile:
C:\PDU-API\Softing\1.10.048\vecom\MDF_SoftingAG_EDIC-PDU-API_1.10.048.xml
PDU-API CableDescriptionFile:
C:\PDU-API\Softing\1.10.048\vecom\CDF_SoftingAG_EDIC-PDU-API_1.10.048.xml
Loading PDU-API library file...

PduApiLibPath:"C:\PDU-API\Softing\1.10.048\vecom\PDUAPI_SoftingAG_1.10.048.dll"

LoadLibrary Error:126
Error LoadLibrary(C:\PDU-API\Softing\1.10.048\vecom\PDUAPI_SoftingAG_1.10.048.dll).
Trying LoadLibraryEx...
LoadLibraryEx succeeded.
Loading successful!
----------------------------------------------------
Parsing MDF file...
MDF parser initialisation successful, MDF file loaded!
MDF parsing completed!
Fixing references completed!
Warning: ComParam ID=3, value Overflow (Max or Min value is set) !
Warning: ComParam ID=4, value Overflow (Max or Min value is set) !
Warning: ComParam ID=5, value Overflow (Max or Min value is set) !
Warning: ComParam ID=6, value Overflow (Max or Min value is set) !
Warning: ComParam ID=37, value Overflow (Max or Min value is set) !
Warning: ComParam ID=38, value Overflow (Max or Min value is set) !
Warning: ComParam ID=39, value Overflow (Max or Min value is set) !
Warning: ComParam ID=130, value Overflow (Max or Min value is set) !
Warning: ComParam ID=132, value Overflow (Max or Min value is set) !
----------------------------------------------------
Parsing CDF file...
CDF parser initialisation successful, CDF file loaded!
CDF parsing completed!
----------------------------------------------------
Return of PDUConstruct:
PDU_STATUS_NOERROR: PDU function call successful
----------------------------------------------------
Return of PDUGetModuleIds:
PDU_STATUS_NOERROR: PDU function call successful
----------------------------------------------------
Number of modules found: 1
hMod: 1, ModuleStatus: PDU_MODST_AVAIL,
Module Type ID: 531,
Vendor Module Name: VendorName='Softing AG' ModuleName='VAS5054' SerialNumber='082145725',
Vendor Additional Info:
----------------------------------------------------
Return of PDUModuleConnect:
PDU_STATUS_NOERROR: PDU function call successful

************* Get module version Info **************

----------------------------------------------------
Module Short Name : VendorName='Softing AG' ModuleName='VAS5054' SerialNumber='082145xxx'
Module Vendor Name : Softing Automotive Electronics GmbH
Module HwName : VAS5054
Module SerialNumber : 82145xxx
Module FW Name : VeCom
Module FW-Version : 2.10.48
Module FW-Date : 7.11.2011 (Calendar week 45)
Module PDU-API SW Name : Softing D-PDU API for VCIs
Module PDU-API Version : 1.10.48
Module PDU-API SW Date : 7.11.2011 (Calendar week 45)
----------------------------------------------------
Return of PDUGetResourceIds:
PDU_STATUS_NOERROR: PDU function call successful
----------------------------------------------------
Number of matching resource IDs: 1
----------------------------------------------------
Selected resource ID: 81
----------------------------------------------------
Return of PDUGetResourceIds:
PDU_STATUS_NOERROR: PDU function call successful
----------------------------------------------------
Number of matching resource IDs: 1
----------------------------------------------------
Selected resource ID: 81

When I click Update Resource Status I see only:

----------------------------------------------------
Return of PDUGetResourceIds:
PDU_STATUS_NOERROR: PDU function call successful
----------------------------------------------------
Number of matching resource IDs: 1
----------------------------------------------------
Selected resource ID: 81

After new pairing of AMB BT module with laptop, I can't cofigure EDIC but VAS v19 works by BT and USB cable. Maybe I should fully uninstall VAS v19 or install odis on other system?

[1 6 D]

I use now PDU API 1.20.15 and odis s 2.2.6 works, but odis e 6.6.1 FE doesn't.

[1 6 D]

Hi, I have found newer PDU API 1.20.23/29/35/37 which works correct on test Application, and looks that FW update is correct I think. ODIS-S 3.0.3 and ODIS-E 6.6.1 still doesn't see ignition and car. Does somebody have other advise? ODIS-S 2.2.6 works on all PDU API's

[vagvag]

Hi, I have found newer PDU API 1.20.23/29/35/37 which works correct on test Application, and looks that FW update is correct I think. ODIS-S 3.0.3 and ODIS-E 6.6.1 still doesn't see ignition and car. Does somebody have other advise? ODIS-S 2.2.6 works on all PDU API's

PDU API 1.20.23 supported versions:
Odis Service 2.2.3
Odis Service 2.2.4
Odis Service 2.2.5 till PS 6.60.20
Odis Engineering 6.2.2

PDU API 1.20.29 supported versions:
Odis Service 2.2.5 from PS 6.60.50
Odis Service 2.2.6
Odis Service 2.2.7

PDU API 1.20.35 supported versions:
Odis Service 3.0.1

PDU API 1.20.37 supported versions:
Odis Service 3.0.2
Odis Service 3.0.3

Regarts........