Цитата:
Для начала убедится, что прибор нормально работает в D-PDU тестах.
|
************ Getting MVCI Module paths *************
Root description file contains 1 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.0 48.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: 1
----------------------------------------------------
Return of PDUGetResourceIds:
PDU_STATUS_NOERROR: PDU function call successful
----------------------------------------------------
Number of matching resource IDs: 1
----------------------------------------------------
Selected resource ID: 81
----------------------------------------------------
Return of PDUModuleConnect:
PDU_ERR_FCT_FAILED: PDU function call failed - вот тут какая то печалька.
Это оно?