Сообщение от veloseeped
Для просмотра ссылок или изображений в данном разделе, у Вас должно быть не менее 15 сообщение(ий). Сейчас у Вас 0 сообщение(ий).

Твоя проблема кроется не в версии PDU-API.
Исправный адаптер должен работать в любой из них.
Вот для примера лог, снятый в течении 3-минут с одного и того же адаптера, без перетыкивания USB в разных версиях драйвера.

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

Root description file contains 4 MVCI modules.
----------------------------------------------------
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...
Loading successful!
----------------------------------------------------
Return of PDUConstruct:
PDU_STATUS_NOERROR: PDU function call successful
----------------------------------------------------
Parsing MDF file...
MDF parser initialisation successful, MDF file loaded!
MDF file parsing completed!
Fixing references completed!
MDF information successfully extracted!
----------------------------------------------------
Return of PDUGetModuleIds:
PDU_STATUS_NOERROR: PDU function call successful
----------------------------------------------------
Number of modules found: 3
----------------------------------------------------
Return of PDUGetResourceIds:
PDU_STATUS_NOERROR: PDU function call successful
----------------------------------------------------
Number of matching resource IDs: 1
----------------------------------------------------
Selected resource ID: 81
----------------------------------------------------
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.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 PDUModuleDisConnect:
PDU_STATUS_NOERROR: PDU function call successful
----------------------------------------------------
Return of PDUDestruct:
PDU_STATUS_NOERROR: PDU function call successful

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

----------------------------------------------------
Selected MVCI module: EDIC_D_PDU_API_1_20_013
----------------------------------------------------
PDU-API dll:
C:\ODIS-DIAG-MODULES-ENGIN\PDUAPI\VEN-SOFTING\1.20.013\vecom\PDUAPI_SoftingAG_1.20.013.dll
PDU-API ModuleDescriptionFile:
C:\ODIS-DIAG-MODULES-ENGIN\PDUAPI\VEN-SOFTING\1.20.013\vecom\MDF_SoftingAG_EDIC-PDU-API_1.20.013.xml
PDU-API CableDescriptionFile:
C:\ODIS-DIAG-MODULES-ENGIN\PDUAPI\VEN-SOFTING\1.20.013\vecom\CDF_SoftingAG_EDIC-PDU-API_1.20.013.xml
Loading PDU-API library file...
Loading successful!
----------------------------------------------------
Return of PDUConstruct:
PDU_STATUS_NOERROR: PDU function call successful
----------------------------------------------------
Parsing MDF file...
MDF parser initialisation successful, MDF file loaded!
MDF file parsing completed!
Fixing references completed!
MDF information successfully extracted!
----------------------------------------------------
Return of PDUGetModuleIds:
PDU_STATUS_NOERROR: PDU function call successful
----------------------------------------------------
Number of modules found: 3
----------------------------------------------------
Return of PDUGetResourceIds:
PDU_STATUS_NOERROR: PDU function call successful
----------------------------------------------------
Number of matching resource IDs: 1
----------------------------------------------------
Selected resource ID: 81
----------------------------------------------------
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.13
Module FW-Date : 21.5.2013 (Calendar week 21)
Module PDU-API SW Name : Softing D-PDU API for VCIs
Module PDU-API Version : 1.20.13
Module PDU-API SW Date : 21.5.2013 (Calendar week 21)
----------------------------------------------------
Return of PDUGetResourceIds:
PDU_STATUS_NOERROR: PDU function call successful
----------------------------------------------------
Number of matching resource IDs: 1
----------------------------------------------------
Selected resource ID: 81
----------------------------------------------------
Return of PDUModuleDisConnect:
PDU_STATUS_NOERROR: PDU function call successful
----------------------------------------------------
Return of PDUDestruct:
PDU_STATUS_NOERROR: PDU function call successful

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

----------------------------------------------------
Selected MVCI module: EDIC_D_PDU_API_21_14_008
----------------------------------------------------
PDU-API dll:
C:\PDU-API\Softing\21.14.008\vecom\PDUAPI_SoftingAG_21.14.008.dll
PDU-API ModuleDescriptionFile:
C:\PDU-API\Softing\21.14.008\vecom\MDF_SoftingAG_EDIC-PDU-API_21.14.008.xml
PDU-API CableDescriptionFile:
C:\PDU-API\Softing\21.14.008\vecom\CDF_SoftingAG_EDIC-PDU-API_21.14.008.xml
Loading PDU-API library file...
Loading successful!
----------------------------------------------------
Return of PDUConstruct:
PDU_STATUS_NOERROR: PDU function call successful
----------------------------------------------------
Parsing MDF file...
MDF parser initialisation successful, MDF file loaded!
MDF file parsing completed!
Fixing references completed!
MDF information successfully extracted!
----------------------------------------------------
Return of PDUGetModuleIds:
PDU_STATUS_NOERROR: PDU function call successful
----------------------------------------------------
Number of modules found: 3
----------------------------------------------------
Return of PDUGetResourceIds:
PDU_STATUS_NOERROR: PDU function call successful
----------------------------------------------------
Number of matching resource IDs: 1
----------------------------------------------------
Selected resource ID: 5
----------------------------------------------------
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 AG
Module HwName : VAS5054
Module SerialNumber : 82145725
Module FW Name : VeCom
Module FW-Version : 2.14.8
Module FW-Date : 21.9.2010 (Calendar week 38)
Module PDU-API SW Name : Softing D-PDU API for VCIs
Module PDU-API Version : 21.14.8
Module PDU-API SW Date : 21.9.2010 (Calendar week 38)
----------------------------------------------------
Return of PDUGetResourceIds:
PDU_STATUS_NOERROR: PDU function call successful
----------------------------------------------------
Number of matching resource IDs: 1
----------------------------------------------------
Selected resource ID: 5