VAS5054A PCB Difference - Printable Version

VAS5054A PCB Difference - Printable Version

+- CarTechnoloGY (https://cartechnology.co.uk)
+-- Forum: Discussions All about Software and Hardware (https://cartechnology.co.uk/forumdisplay.php?fid=310)
+--- Forum: Automotive Help & Discussions / Software and Hardware (https://cartechnology.co.uk/forumdisplay.php?fid=40)
+---- Forum: VAG Group (VW - Audi - Seat - Skoda - Bentley) (https://cartechnology.co.uk/forumdisplay.php?fid=55)
+---- Thread: VAS5054A PCB Difference (/showthread.php?tid=4905)

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27

RE: VAS5054A PCB Difference - rightpcb - 16-05-2018

I am still waiting for components to arrive, so after a little bit of work combining the 2 together I have one, I think that is working, with there 3 parts

[Image: attachment.php?aid=68699]

This I what I get when I do a test

[Image: attachment.php?aid=68703]

I have not tried it on car yet, can anyone see if there is any problems

I have tried using the board with the faster memory but get this problem

[Image: attachment.php?aid=68704]

Does anyone know what I can check to solve this problem

Thank you

RE: VAS5054A PCB Difference - Enabled - 16-05-2018

That is usually a software issue or maybe the VAS5054a isn't added correctly to the computer. Is that through Bluetooth or USB?

RE: VAS5054A PCB Difference - rightpcb - 16-05-2018

Thats through USB but only when I connect the board with the faster memory,if I use the board with the slower memory as you can see its OK

RE: VAS5054A PCB Difference - rightpcb - 22-05-2018

(16-08-2017, 08:54 AM)fantomel Wrote: Some time ago a friend of mine asked me for a rework on his vas, and i have made this for him:

As you can see bluetooth module is a fake one since it has no capacitors and no resistences on the back.

Open these images if you are interested and save them on your computer. Then you can zoom on them and see more clear all parts.

A BIG THANK YOU to you all for you help, I have I think managed to get one working out of the 2 I have, I am still waiting for components to arrive to finish the work

I have run the test and I get this

[Image: attachment.php?aid=69091]

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

Root description file contains 1 MVCI modules.

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

----------------------------------------------------
Selected MVCI module: EDIC_D_PDU_API_1_20_041
----------------------------------------------------
PDU-API dll:
C:\Program Files\Softing\D-PDU API\1.20.041\vecom\PDUAPI_SoftingAG_1.20.041.dll
PDU-API ModuleDescriptionFile:
C:\Program Files\Softing\D-PDU API\1.20.041\vecom\MDF_SoftingAG_EDIC-PDU-API_1.20.041.xml
PDU-API CableDescriptionFile:
C:\Program Files\Softing\D-PDU API\1.20.041\vecom\CDF_SoftingAG_EDIC-PDU-API_1.20.041.xml
Loading PDU-API library file...

PduApiLibPath:"C:\Program Files\Softing\D-PDU API\1.20.041\vecom\PDUAPI_SoftingAG_1.20.041.dll"
Loading successful!
----------------------------------------------------
Parsing MDF file...
MDF parser initialisation successful, MDF file loaded!
MDF parsing completed!
Fixing references completed!
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=7, 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=40, value Overflow (Max or Min value is set) !
Warning: ComParam ID=132, value Overflow (Max or Min value is set) !
Warning: ComParam ID=134, 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: ConnectionType='Bluetooth'
----------------------------------------------------
Return of PDUModuleConnect:
PDU_STATUS_NOERROR: PDU function call successful

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

----------------------------------------------------
Module Short Name : VendorName='Softing AG' ModuleName='VAS5054' SerialNumber='082145725'
Module Vendor Name : Softing Automotive Electronics GmbH
Module HwName : VAS5054
Module SerialNumber : 82145725
Module FW Name : VeCom
Module FW-Version : 2.20.41
Module FW-Date : 16.1.2017 (Calendar week 3)
Module PDU-API SW Name : Softing D-PDU API for VCIs
Module PDU-API Version : 1.20.41
Module PDU-API SW Date : 16.1.2017 (Calendar week 3)
----------------------------------------------------
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
----------------------------------------------------
Return of PDUGetResourceIds:
PDU_STATUS_NOERROR: PDU function call successful
----------------------------------------------------
Number of matching resource IDs: 1
----------------------------------------------------
Selected resource ID: 81

I dont know if that is good or bad?

[Image: attachment.php?aid=69090]

Is the A5780A chip the correct way up?

Thanks

RE: VAS5054A PCB Difference - Marcos - 22-05-2018

(22-05-2018, 21:48 PM)rightpcb Wrote: Is the A5780A chip the correct way up?

Thanks

It's upside-down. You must rotate it.

RE: VAS5054A PCB Difference - test22 - 23-05-2018

Does it work with pdu 1.20.42?

RE: VAS5054A PCB Difference - rightpcb - 23-05-2018

(23-05-2018, 03:28 AM)test22 Wrote: Does it work with pdu 1.20.42?

I dont know, I have not tried it yet, when the other components are fitted I will see

RE: VAS5054A PCB Difference - rightpcb - 24-06-2018

I need a little bit of help to finish of my VAS head please, here is a pic of an original head with the proper resistors, the one behind the white relay on the inner side of the board (paisted into the foto, red square) and the 2 on the other side of the same board, to me they all look like they have the same markings,
green, blue, black, silver, brown = 56Ω

[Image: attachment.php?aid=70494]

Is that correct or is one of them a 56Ω and the other 2 are 5.6Ω ?

Thank you

RE: VAS5054A PCB Difference - Marcos - 24-06-2018

(24-06-2018, 20:08 PM)rightpcb Wrote: Is that correct or is one of them a 56Ω and the other 2 are 5.6Ω ?

All of them are 5.6Ohms

RE: VAS5054A PCB Difference - zmann - 25-06-2018

Alternatively, use ohm meter and measure it in circuit. The readouts should always be close to the resistor actual values, now the actual value can be reckoned. This method is useful to apply on SMD resistors size of 0402 which is too small as dust and nothing at all to read out. There are a lot of them used on EDC17, MED17, MEV17 and some other ECU's. The ECU's are known as hard to open and with risk to damage those dusty components.