[xaxaTyH]

Hello.

Can't get my VAS 5054a work with odis 4.3.3. I've uninstalled edic pdu 1.20.42, installed edic pdu 1.20.41. Edic test application shows that everything is fine (file test.txt in attachments). But Odis 4.3.3 can't identify my VAS 5054a (screenshots in attachments).

Please, help. I have no ideas..

P.S. Odis installed on VM Win 7 x64. Latest .Net Framework, latest java, latest windows updates.

[Tadk]

C / ProgramData / D-PDU API / pdu_api_root.xml. Correct the text editor all 1.20.42 to 1.20.41.

[xaxaTyH]

C / ProgramData / D-PDU API / pdu_api_root.xml. Correct the text editor all 1.20.42 to 1.20.41.

Greetings, Tadk. But I already have the correct values, problem is actual.
File:
<!-- D-PDU-API root file -->
<MVCI_PDU_API_ROOT xmlnssi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="C:/ProgramData/D-PDU API/pdu.xsd" MVCI_PART2_STANDARD_VERSION="2.2.0">
<MVCI_PDU_API>
<SHORT_NAME>XS_D_PDU_API_OS</SHORT_NAME>
<DESCRIPTION>D-PDU-API implementation used for MVCI of ACTIA I+ME GmbH</DESCRIPTION>
<SUPPLIER_NAME>ACTIA I+ME GmbH</SUPPLIER_NAME>
<LIBRARY_FILE URI="file:/C:/ODIS-DIAG-MODULES/PDUAPI/VOLKSWAGEN/PDUAPI_I+ME_ACTIA_XS.dll"/>
<MODULE_DESCRIPTION_FILE URI="file:/C:/ODIS-DIAG-MODULES/PDUAPI/VOLKSWAGEN/MDF_I+ME_ACTIA_XS.xml"/>
<CABLE_DESCRIPTION_FILE URI="file:/C:/ODIS-DIAG-MODULES/PDUAPI/VOLKSWAGEN/CDF_I+ME_ACTIA_XS.xml"/>
</MVCI_PDU_API>
<MVCI_PDU_API>
<SHORT_NAME>EDIC_D_PDU_API_1_20_041</SHORT_NAME>
<DESCRIPTION>EDIC D-PDU API Implementation</DESCRIPTION>
<SUPPLIER_NAME>Softing AG</SUPPLIER_NAME>
<LIBRARY_FILE URI="file:/C:/Program Files (x86)/Softing/D-PDU API/1.20.041/vecom/PDUAPI_SoftingAG_1.20.041.dll"/>
<MODULE_DESCRIPTION_FILE URI="file:/C:/Program Files (x86)/Softing/D-PDU API/1.20.041/vecom/MDF_SoftingAG_EDIC-PDU-API_1.20.041.xml"/>
<CABLE_DESCRIPTION_FILE URI="file:/C:/Program Files (x86)/Softing/D-PDU API/1.20.041/vecom/CDF_SoftingAG_EDIC-PDU-API_1.20.041.xml"/>
</MVCI_PDU_API>
</MVCI_PDU_API_ROOT>

[Tadk]

Did you test the adapter for version 41?

[xaxaTyH]

Did you test the adapter for version 41?

I tested it with "Softing D-PDUAPI Test Application" with version 041, test was successful (log attached in the first message). But ODIS 4.3.3 doesn't see my adapter.

Long time ago, I had an ODIS 2.2.3 and adapter worked fine.

May be I should uninstall odis 4.3.3. and try 4.2.3, I don't know what to try yet

[Tadk]

Extract from archive and copy with replacement:
c:\Program Files (x86)\Softing\D-PDU API\1.20.041\VeCom\

[xaxaTyH]

Extract from archive and copy with replacement:
c:\Program Files (x86)\Softing\D-PDU API\1.20.041\VeCom\

Thanks, I'll try it tomorrow and post results here

[adamos_22]

Extract from archive and copy with replacement:
c:\Program Files (x86)\Softing\D-PDU API\1.20.041\VeCom\

Thanks, I'll try it tomorrow and post results here

HI,

did you solve issue with Tadk solution ?

[xaxaTyH]

Extract from archive and copy with replacement:
c:\Program Files (x86)\Softing\D-PDU API\1.20.041\VeCom\

Thanks, I'll try it tomorrow and post results here

Thanks, Tadk.Unfortunally, It did not help.

---

Extract from archive and copy with replacement:
c:\Program Files (x86)\Softing\D-PDU API\1.20.041\VeCom\

Thanks, I'll try it tomorrow and post results here

HI,

did you solve issue with Tadk solution ?

Hello, no, the same problem

---

Is it possible to install ODIS 4.2.3 and latest PostSetup from odis 4.3.3?

[sunaj]

Can you post a screenshot of Virtual Machine

C:\
and
C:\Program Files (x86)


I am thinking that in some languages of Windows, that Program Files (x86) has a different name!


C:\Program Files (x86) English
C:\Programme (x86) German
C:\Archivos de programa (x86) Spanish
C:\Programmes (x86) French
C:\Programmi (x86) Italian
C:\Arquivos de Programas (x86) Portuguese
C:\Program (x86) Swedish
C:\Programmer (x86) Danish
C:\Programfiler (x86) Norwegian
C:\Fisiere Program Romanian
C:\Program Files (x86) Dutch / Russian / Polish / Czech / Chinese