For USB Protocol Suite Software Version 7.45 and above
February 2017
1
Page 2
Document Disclaimer
The information contained in this document has been carefully checked and is
believed to be reliable. However, no responsibility can be assumed for inaccuracies
that may not have been detected.
Teledyne LeCroy reserves the right to revise the information presented in this
document without notice or penalty.
Trademarks and Servicemarks
CATC Trace, Voyager M310C, Voyager ReadyLink, USB Protocol Suite, and BusEngine
are trademarks of Teledyne LeCroy.
All other trademarks are property of their respective companies.
Integrated in Teledyne LeCroy’s Voyager M310C test platform, the Power Delivery
exerciser supports traffic generation, including both provider and consumer device
emulation. The Power Delivery exerciser continues to evolve with each software release.
Be sure to check for updated software and firmware before getting started with the
Exerciser.
Important Licensing Note:
Operating the PD Exerciser beta requires that the USB Power Delivery
Exerciser option is enabled on the M310C base unit:
Getting Started:
The “left” port of the Voyager should be used to
connect DUT to the PD Exerciser. The PD exerciser
also requires specific cable orientation (Red LED when
connected wrong side-up).
To enable the PD Trainer/Exerciser, use the PD Tab under “Recording Options”
to select the Exerciser mode.
Note – Allow VBUS > 5v is a safety feature which prevents sourcing above 5V. When
enabled, this mode will allow Voltage levels to be delivered to the DUT which may exceed
their current carrying capabilities. While the M310C system is designed to tolerate higher
current, these higher voltages may inadvertently cause damage to devices/cables under
test.
To set devices port name, use the General Tab under “Recording Options” to add
“alias labels” for your DUTs.
These labels will appear in the trace capture.
The Alias name is primarily for use in analyzer mode and requires that device names are
added before recording traffic. The device naming can also be used in Exerciser mode;
however message frames from the Voyager M310C will be always be labeled “M310C”.
Following Packet Templates can be used in Basic or High-Level commands as data
containers. All of these messages inherited from PD_Packet packet template except those
which are used as containers for Data Objects.
2.1 PD_ControlMessage
Available fields for PD_ControlMessage packet template are:
2.2 PD_GoodCrcMessage
PD_GoodCrcMessage packet template has same fields as PD_ControlMessage but default value
for MessageType is 1.
2.3 PD_GotoMinMessage
PD_GotoMinMessage packet template has same fields as PD_ControlMessage but default value
for MessageType is 2.
2.4 PD_AcceptMessage
PD_AcceptMessage packet template has same fields as PD_ControlMessage but default value
for MessageType is 3.
2.5 PD_RejectMessage
PD_RejectMessage packet template has same fields as PD_ControlMessage but default value
for MessageType is 4.
2.6 PD_PingMessage
PD_PingMessage packet template has same fields as PD_ControlMessage but default value for
MessageType is 5.
14
Page 15
2.7 PD_PsRdyMessage
PD_PsRdyMessage packet template has same fields as PD_ControlMessage but default value for
MessageType is 6.
2.8 PD_GetSourceCapMessage
PD_GetSourceCapMessage packet template has same fields as PD_ControlMessage but default
value for MessageType is 7.
2.9 PD_GetSinkCapMessage
PD_GetSinkCapMessage packet template has same fields as PD_ControlMessage but default
value for MessageType is 8.
2.10 PD_DataRoleSwapMessage
PD_DataRoleSwapMessage packet template has same fields as PD_ControlMessage but default
value for MessageType is 9.
2.11 PD_PowerRoleSwapMessage
PD_PowerRoleSwapMessage packet template has same fields as PD_ControlMessage but default
value for MessageType is 10.
2.12 PD_VConnSwapMessage
PD_VConnSwapMessage packet template has same fields as PD_ControlMessage but default
value for MessageType is 11.
2.13 PD_WaitMessage
PD_WaitMessage packet template has same fields as PD_ControlMessage but default value for
MessageType is 12.
2.14 PD_SoftResetMessage
PD_SoftResetMessage packet template has same fields as PD_ControlMessage but default
value for MessageType is 13.
2.15 PD_NotSupportedMsg
PD_NotSupportedMsg packet template has same fields as PD_ControlMessage but default value
for MessageType is 16. Applied to Power Delivery Rev3.0.
2.16 PD_GetSourceCapExtendedMsg
PD_GetSourceCapExtendedMsg packet template has same fields as PD_ControlMessage but
default value for MessageType is 17. Applied to Power Delivery Rev3.0.
15
Page 16
2.17 PD_GetStatusMsg
Field Name
Description
SourceCapabilitiesData
This field can contain one or more(up-to 7 according to PD Spec) PDO
packet variables. PDO types which can assign to this field are:
Used as SinkCapabilitiesData for PD_SinkCapabilitiesMessage. Available fields for this packet
template are:
2.20.3 PD_PowerDataObjectBatterySupply_Sink
Used as SinkCapabilitiesData for PD_SinkCapabilitiesMessage. Available fields for this packet
template are:
2.21 PD_RequestPacket
PD_RequestPacket packet template contains all the fields of PD_ControlMessage but default
value for MessageType is 2 and default value for NumberOfDataObjects field is 1. Following are
additional data fields for PD_RequestPacket packet template:
Default: {AA AA AA AA AA AA AA AA AA AA AA AA AA AA
AA AA AA AA AA AA AA AA AA AA}
Used as data for PD_RequestPacket. This packet template has same fields as
PD_RequestDataObject_Fixed_Variable_NoGiveBack packet template, but default value for
GiveBackFlag field is 1.
2.21.3 PD_RequestDataObject_Battery_NoGiveBack
Used as data for PD_RequestPacket. Available fields for this packet template are:
2.21.4 PD_RequestDataObject_Battery_GiveBack
Used as data for PD_RequestPacket. This packet template has same fields as
PD_RequestDataObject_Battery_NoGiveBack packet template, but default value for GiveBackFlag field
is 1.
2.22 PD_BISTCarrierModeMessage
PD_BISTCarrierModeMessage packet template contains all the fields of PD_ControlMessage but
default value for MessageType is 3 and default value for NumberOfDataObjects field is 1.
Following are additional data fields for PD_BISTCarrierModeMessage packet template:
2.23 PD_BISTTestDataMessage
PD_BISTTestDataMessage packet template contains all the fields of PD_ControlMessage but
default value for MessageType is 3 and default value for NumberOfDataObjects field is 7.
Following are additional data fields for PD_BISTTestDataMessage packet template:
2.24 PD_BatteryStatusMsg
Applied to Rev3.0. PD_BatteryStatusMsg packet template contains all the fields of
PD_ControlMessage but default value for MessageType is 5 and default value for
19
Page 20
NumberOfDataObjects field is 1. Following are additional data fields(fields of
Field Name
Description
Reserved_1
Default: 0x00
InvalidBatteryReference
Default: 0x00
BatteryIsPresent
Default: 0x00
BatteryChargingStatus
Default: 0x00
Reserved_2
Default: 0x00
BatteryPC
Default: 0xFFFF
Field Name
Description
Reserved_1
Default:0x00
HotSwappableBatteries
Default:0x00
FixedBatteries
Default:0x00
Reserved_2
Default:0x00
BatteryStatusChange
Default:0x00
OverCurProtection
Default:0x00
OverTempProtection
Default:0x00
OperatingConditionChange
Default:0x00
SourceInputChange
Default:0x00
OverVoltageProtection
Default:0x00
Reserved_3
Default:0x00
Field Name
Description
VDMCustom
Default: 0x00
VDMType
Default: PD_VDM_TYPE_UNSTRUCTURED_VDM
VDMSVID
Default: 0x00
Field Name
Description
VDMCommand
Default: PD_VDM_COMMAND_RESERVED_0
VDMReserved1
Default: 0x00
PD_BatteryStatusDataObject packet template) for PD_BatteryStatusMsg packet template:
2.25 PD_AlertMsg
Applied to Rev3.0. PD_AlertMsg packet template contains all the fields of PD_ControlMessage
but default value for MessageType is 6 and default value for NumberOfDataObjects field is 1.
Following are additional data fields(fields of PD_AlertDataObject packet template) for
PD_AlertMsg packet template:
2.26 PD_VDM_Unstructured_Header
Used as Header for Unstructured VDM messages. PD_VDM_Unstructured_Header packet
template contains all the fields of PD_ControlMessage but default value for MessageType is
0x0F and default value for NumberOfDataObjects field is 1. Following are additional data
fields for PD_VDM_Unstructured_Header packet template:
2.27 PD_VDM_Structured_Header
Used as Header for all Structured VDM messages. PD_VDM_Structured_Header packet
template contains all the fields of PD_ControlMessage but default value for MessageType is
0x0F and default value for NumberOfDataObjects field is 1. Following are additional data
fields for PD_VDM_Structured_Header packet template:
PD_VDM_Discover_Identity_Message packet template contains all the fields of
PD_VDM_Structured_Header but default value for VDMCommand field is
PD_VDM_COMMAND_DISCOVER_IDENTITY and default value for VDMSVID field is PD_VDM_SID.
2.29 PD_VDM_Discover_Identity_Response
PD_VDM_Discover_Identity_Response packet template contains all the fields of
PD_VDM_Discover_Identity_Message but default value for VDMCommandType field is
PD_VDM_COMMAND_TYPE_RESPONDER_ACK. Following are additional data fields for
PD_VDM_Discover_Identity_Response packet template:
2.29.1 PD_VDM_Discover_Identity_ID_Header_VDO
Used as VDOs for PD_VDM_Discover_Identity_Response packet template. Available fields of this packet
template are varies from Revision 2.0 to higher revisions:
2.29.1.1 Revision 2.0
2.29.1.2 Revision 3.0
21
Page 22
ModalOperationSupported
Default: 0x00
ProductType_UFP_Cable
Default: PD_PRODUCT_TYPE_UNDEFINED
DataCapableAsUSBDevice
Default: 0x00
DataCapableAsUSBHost
Default: 0x00
2.29.2 PD_VDM_Discover_Identity_Cert_Stat_VDO
Field Name
Description
CertStatVDO_XID
Default: 0x00
Rsvd
Default: 0x00
Rev2.0 only
Field Name
Description
ProductVDO_USBProductId
Default: 0x00
ProductVDO_BCDDevice
Default: 0x00
Field Name
Description
CableVDO_USBSuperSpeedSignalingSupport
Default:
PD_VDM_CABLE_VDO_USB31_GEN1_SIGNALING_SUPPORT
CableVDO_SOPDPrimeControllerPresent
Default: 0x00
CableVDO_VBusThroughCable
Default: 0x00
CableVDO_VBusCurrentHandlingCapability
Default: PD_VDM_CABLE_VDO_VBUS_HANDLING_NO_VBUS
CableVDO_SSRX2DirectionalitySupport
Default: 0x00
CableVDO_SSRX1DirectionalitySupport
Default: 0x00
CableVDO_SSTX2DirectionalitySupport
Default: 0x00
CableVDO_SSTX1DirectionalitySupport
Default: 0x00
CableVDO_CableTerminationType
Default: 0x00
CableVDO_CableLatency
Default: PD_VDM_CABLE_VDO_CABLE_LATENCY_UPTO_10ns
CableVDO_TypeCPlugToPlugOrReceptacle
Default: PD_VDM_CABLE_VDO_TYPEC_PLUG_TO_PLUG
CableVDO_TypeCPlugToTypeA_B_C_Captive
Default: PD_VDM_CABLE_VDO_TYPEC_PLUGTO_TYPEC
CableVDO_Reserved
Default: 0x00
CableVDO_FirmwareVersion
Default: 0x00
CableVDO_HardwareVersion
Default: 0x00
Field Name
Description
USBSsSignaling
Default: PD_CABLE_USB31_GEN1_SIGNALING
Reserved_1
Default: 0x00
VBusCurHandlingCap
Default: PD_CABLE_CUR_HANDLING_CAP_3A
Used as VDOs for PD_VDM_Discover_Identity_Response packet template. Available fields of this packet
template are:
2.29.3 PD_VDM_Discover_Identity_Product_VDO
Used as VDOs for PD_VDM_Discover_Identity_Response packet template. Available fields of this packet
template are:
2.29.4 PD_VDM_Discover_Identity_Cable_VDO
Applied to Revision 2.0 only. Used as VDOs for PD_VDM_Discover_Identity_Response packet template.
Available fields of this packet template are:
2.29.5 PD_DiscoverIdPassiveCableVdo
Applied to Rev3.0 only. Used as VDOs for PD_VDM_Discover_Identity_Response packet template.
Available fields of this packet template are:
22
Page 23
Reserved_2
Default: 0x00
MaxVBusVoltage
Default: PD_CABLE_MAX_VBUS_20V
CableTerminationType
Default: PD_CABLE_VCONN_NOT_REQUIRED
CableLatency
Default: PD_CABLE_LATENCY_MAX_10ns
Reserved_3
Default: 0x00
TypeCtoTypeC_Captive
Default: PD_CABLE_TYPEC_TO_TYPEC
Reserved_4
Default: 0x00
Version
Default: PD_CABLE_PASSIVE_VDO_VERSION_1
FirmwareVersion
Default: 0x00
HardwareVersion
Default: 0x00
2.29.6 PD_DiscoverIdActiveCableVdo
Field Name
Description
USBSsSignaling
Default: PD_CABLE_USB31_GEN1_SIGNALING
SOPDoublePrimeController
Default: 0x00
VBusThrough
Default: 0x01
VBusCurHandlingCap
Default: PD_CABLE_CUR_HANDLING_CAP_3A
Reserved_1
Default: 0x00
MaxVBusVoltage
Default: PD_CABLE_MAX_VBUS_20V
CableTerminationType
Default: PD_CABLE_TERM_ACTIVE_ACTIVE
CableLatency
Default: PD_CABLE_LATENCY_MAX_10ns
Reserved_2
Default: 0x00
TypeCtoTypeC_Captive
Default: PD_CABLE_TYPEC_TO_TYPEC
Reserved_3
Default: 0x00
Version
Default: PD_CABLE_ACTIVE_VDO_VERSION_1
FirmwareVersion
Default: 0x00
HardwareVersion
Default: 0x00
Field Name
Description
AMDVDO_USBSuperSpeedSignalingSupport
Default: 0x01
AMDVDO_VBusRequired
Default: 0x00
AMDVDO_VConnRequired
Default: 0x00
AMDVDO_VConnPower
Default: 0x00
AMDVDO_SSRX2DirectionalitySupport
Default: 0x00
AMDVDO_SSRX1DirectionalitySupport
Default: 0x00
AMDVDO_SSTX2DirectionalitySupport
Default: 0x00
AMDVDO_SSTX1DirectionalitySupport
Default: 0x00
AMDVDO_Reserved
Default: 0x00
AMDVDO_FirmwareVersion
Default: 0x00
AMDVDO_HardwareVersion
Default: 0x00
Applied to Rev3.0 only. Used as VDOs for PD_VDM_Discover_Identity_Response packet template.
Available fields of this packet template are:
Used as VDOs for PD_VDM_Discover_Identity_Response packet template. Available fields of this packet
template are varies from Revision 2.0 to higher revisions:
2.29.7.1 Revision 2.0
23
Page 24
Page 25
Page 26
2.37 PD_VDM_Exit_Mode_Response
Field Name
Description
VDO
This field may contain one VDO. The VDO can be a PD_VDO packet
variable which has 32bits data length.
Field Name
Description
StatusVdo
Contains only one VDO in type of
PD_VDM_DisplayPort_Status_VDO packet template.
Field Name
Description
DFPD_UFPD_Connected
Default: PD_DISPLAYPORT_DISCONNECTED
PowerLow
Default: 0x00
AdaptorEnabled
Default: 0x00
MultiFunctionPreferred
Default: 0x00
UsbConfigurationRequest
Default: 0x00
ExitDisplayModeRequest
Default: 0x00
HPD_State
Default: 0x00
IRQ_HPD
Default: 0x00
Reserved_DPS_1
Default: 0x00
PD_VDM_Exit_Mode_Response packet template contains all the fields of
PD_VDM_Exit_Mode_Message but default value for VDMCommandType field is
PD_VDM_COMMAND_TYPE_RESPONDER_ACK.
2.38 PD_VDM_Attention_Message
PD_VDM_Attention_Message packet template contains all the fields of
PD_VDM_Structured_Header but default value for VDMCommand field is PD_VDM_COMMAND_ATTENTION
and default value for VDMSVID field is PD_VDM_SID. Following are additional data fields for
PD_VDM_Attention_Message packet template:
2.39 PD_VDM_DisplayPort_UpdateStatus_Message
PD_VDM_DisplayPort_UpdateStatus_Message packet template contains all the fields of
PD_VDM_Structured_Header but default value for NumberOfDataObjects field is 2 and default
value for VDMCommand field is PD_VDM_COMMAND_DISPLAYPORT_STATUS_UPDATE and default value for
VDMSVID field is PD_DISPLAY_PORT_SVID. Following are additional data fields for
PD_VDM_DisplayPort_UpdateStatus_Message packet template:
2.39.1 PD_VDM_DisplayPort_Status_VDO
Used as StatusVdo for PD_VDM_DisplayPort_UpdateStatus_Message and
PD_VDM_DisplayPort_UpdateStatus_Response packet templates. Following are available data fields for
this packet template:
2.40 PD_VDM_DisplayPort_UpdateStatus_Response
PD_VDM_DisplayPort_UpdateStatus_Response packet template contains all the fields of
PD_VDM_DisplayPort_UpdateStatus_Message but default value for VDMCommandType field is
PD_VDM_COMMAND_TYPE_RESPONDER_ACK.
26
Page 27
Page 28
VendorId
Default: 0x00
ProductId
Default: 0x00
XId
Default: 0x00
FirmwareVersion
Default: 0x00
HardwareVersion
Default: 0x00
LoadStep
Default: 0x00
IOC
Default: 0x00
Reserved_1
Default: 0x00
HoldupTime
Default: 0x00
LPSCompliant
Default: 0x00
PS1Compliant
Default: 0x00
PS2Compliant
Default: 0x00
Reserved_2
Default: 0x00
LowTouchCurEPS
Default: 0x00
GroundPinSupport
Default: 0x00
GrndPinForProtectiveEarth
Default: 0x00
Reserved_3
Default: 0x00
PeakCur1_PercentOverload
Default: 0x00
PeakCur1_OverloadPeriod
Default: 0x00
PeakCur1_DutyCycle
Default: 0x00
PeakCur1_VBusVoltageDroop
Default: 0x00
PeakCur2_PercentOverload
Default: 0x00
PeakCur2_OverloadPeriod
Default: 0x00
PeakCur2_DutyCycle
Default: 0x00
PeakCur2_VBusVoltageDroop
Default: 0x00
PeakCur3_PercentOverload
Default: 0x00
PeakCur3_OverloadPeriod
Default: 0x00
PeakCur3_DutyCycle
Default: 0x00
PeakCur3_VBusVoltageDroop
Default: 0x00
TouchTemp
Default: 0x00
ExternalSupplyIsPresent
Default: 0x00
ExternalSupplyCondition
Default: 0x00
InternalBatteryIsPresent
Default: 0x00
Reserved_4
Default: 0x00
NumberOfFixedBatteries
Default: 0x00
NumberOfHotSwappableBatteries
Default: 0x00
2.45 PD_StatusMsg
Field Name
Description
InternalTemp
Default: 0x00
Reserved_1
Default: 0x00
ExternalPowerIsPresent
Default: 0x00
ExternalPower_AC_DC
Default: 0x00
InternalPowerBattery
Default: 0x00
InternalPowerNonBattery
Default: 0x00
Reserved_2
Default: 0x00
FixedBattery
Default: 0x00
Applied to Rev3.0. PD_StatusMsg packet template contains all the fields of PD_ExtMsgHeaders
but the default value of MessageType field is 2 and the default value of DataSize field is 0x03.
Following are the additional fields(fields of PD_StatusDataBlock packet template) for this
packet template:
28
Page 29
Page 30
Page 31
Page 32
MinProtVer
Default: 0x00
MaxProtVer
Default: 0x00
Capabilities
Default: 0x01
Rsvd
Default: 0x00
CertChainHash
Default: { 00 00 00 00 }
Salt
Default: { 00 00 00 00 }
ContextHash
Default: { 00 00 00 00 }
Signature
Default: { 00 00 00 00 }
2.52.4 PD_SRPDB_Error
Field Name
Description
AuthProtocolVersion
Default: PD_AUTH_PROT_VER_1
AuthMessageType
Default: PD_AUTH_TYPE_ERROR
AuthParam1
Default: 0x01
AuthParam2
Default: 0x00
Used as SecurityResponseDB for PD_SecurityResponseMsg packet template. Available data fields for
this packet template are:
32
Page 33
33
3 Type-C Commands
In addition to Power Delivery commands, PD Exerciser also provides a command set to
manage USB Type-C connection . It includes some low level commands for manipulating
voltages, capacitors and resistors as well as some high level commands that let you have
SINK, SINKAS, SOURCE and DRP state machines, described in Type-C specification, with the
facilities to customize different behaviors and characteristics. Note that at the present,
Type-C state machines are just followed when related commands are running. In other
words, Type-C state machines are not followed in parallel to other Power Delivery
commands execution.
The voltage which applied on VBus. Voltage should be in range of 5000 to 20500 mV. In order to apply
voltages greater than 5V, the corresponding check box should be set in recording options.
Using this command you can create a loop(containing other Exerciser commands) which is
bound to a predefined timer. On timer timeout, the loop will exit.
Note - The limit for using nested PD_TimerLoop() commands is 8.
Command failed. In this case corresponding sub results
for PD_SendPacket and PD_ReceivePacket are valid
also (depends on the error type which has been occurred
during sending or receiving data).
PD_SUBRESULT_REQUEST_MSG_INVALID_INDEX
Subresult - Invalid index in request message
PD_SUBRESULT_RESPONSE_WAIT
Subresult - Wait has been sent as request message
response
PD_SUBRESULT_RESPONSE_REJECT
Subresult - Reject has been sent as request message
response
None
Examples
local $power_data_object = PD_PowerDataObjectFixedSupply_Source
{
Adds Sink Capabilities to PD Exerciser. Before adding a group of sink caps make sure that
there is no unwanted sink cap in the list by calling PD_ResetSinkCaps command. This
command must be called before PD_NegotiatePower_Sink or PD_NegotiatePower or
PD_WaitForNegotiatePower or PD_DelayAutoResponse commands to take effect.
Note - By default there is one pre-defined sink cap in the list.
Clears all Sink Capabilities defined for PD Exercise. Should be called before adding one or
more sink capabilities.
Format
Call PD_ResetSinkCaps()
Parameters
None
Result
None
Page 62
Page 63
Page 64
Page 65
Examples
Result Value
Description
PD_RESULT_OK
Command succeeded
PD_RESULT_FAILED
Command failed. In this case corresponding sub results
for PD_SendPacket and PD_ReceivePacket are valid
also (depends on the error type which has been occurred
during sending or receiving data).
PD_SUBRESULT_RESPONSE_WAIT
Subresult - Wait has been sent as response
PD_SUBRESULT_RESPONSE_REJECT
Subresult - Reject has been sent as response
PD_SUBRESULT_MSG_NOT_RECEIVED
Subresult - PR_Swap message not received or PS_RDY
message not received(PD Exerciser as Sink)
PD_SUBRESULT_RESPONSE_NOT_SUPPORTED
Rev3.0 only. Subresult - Not_Supported has been sent as
response
call PD_SwapPowerRole()
5.1.14 PD_WaitForSwapPowerRole
Waits to receive PR_Swap message and will respond to incoming messages as part of the
Swap Power Role AMS.
Format
Call PD_WaitForSwapPowerRole()
Parameters
None
Result
User can evaluate the command results(including sub-results) using IfMatched/ElseMatched
command.
List of result values:
Examples
call PD_WaitForSwapPowerRole()
5.1.15 PD_FastRoleSwap
Sends the FastRoleSwap Signal and handles Fast Role Swap AMS.
Note- Received FastRoleSwap Signal will handle by FastRoleSwap event handler
automatically.
Format
Call PD_FastRoleSwap()
Parameters
None
Result
User can evaluate the command results(including sub-results) using IfMatched/ElseMatched
command.
List of result values:
65
Page 66
Page 67
Page 68
Page 69
Page 70
Page 71
Format
Result Value
Description
PD_RESULT_OK
Command succeeded
PD_RESULT_FAILED
Command failed. In this case corresponding sub results
for PD_SendPacket and PD_ReceivePacket are valid
also (depends on the error type which has been occurred
during sending or receiving data).
PD_SUBRESULT_MSG_NOT_RECEIVED
Subresult - GotoMin or PS_RDY message not received.
PD_SUBRESULT_RESPONSE_NOT_SUPPORTED
Rev3.0 only. Subresult - Not_Supported has been sent as
response
Field Name
Description
WaitTimeout
Wait time-out(micro second) for receiving GetSourceCap
message.
Default: PD_DEFAULT_TIMEOUT_INFINIT
ResponseType
Indicates the response type upon receiving
GetSourceCap message.
Possible values:
User can evaluate the command results(including sub-results) using IfMatched/ElseMatched
command.
List of result values:
Examples
call PD_WaitForGotoMin()
5.1.25 PD_SetGetSourceCapSetting
Applies settings to GetSourceCap related commands in PD Exerciser. It must be called
before PD_WaitForGetSourceCapabilities or PD_DelayAutoResponse to take effect.
Command failed. In this case corresponding sub results
for PD_SendPacket and PD_ReceivePacket are valid
also (depends on the error type which has been
occurred during sending or receiving data).
PD_SUBRESULT_RESPONSE_TIMEOUT
Subresult - No response received.
PD_SUBRESULT_RESPONSE_NOT_SUPPORTED
Subresult - Not_Supported message received.
Clears the source capabilities extended Data Block in PD Exerciser. Should be called before
calling PD_SetSrcCapExtDataBlock.
Format
Call PD_ResetSrcCapExtDataBlock()
Parameters
None
Result
None
Examples
Call PD_ResetSrcCapExtDataBlock()
5.1.38 PD_GetStatus
Starts the GetStatus AMS.
Format
Call PD_GetStatus()
Parameters
None
Result
User can evaluate the command results(including sub-results) using IfMatched/ElseMatched
command.
List of result values:
Examples
Call PD_GetStatus()
5.1.39 PD_SetGetStatusSetting
Applies settings to GetStatus related commands in PD Exerciser. It must be called before
PD_WaitForGetStatus or PD_DelayAutoResponse commands to take effect.
Clears the Status Data Block in PD Exerciser. Should be called before calling
PD_SetStatusDataBlock command.
Format
Call PD_ResetStatusDataBlock()
Parameters
None
Result
None
Examples
Call PD_ResetStatusDataBlock()
5.1.43 PD_GetBatteryStatus
Starts the GetBatteryStatus AMS.
Format
Call PD_GetBatteryStatus()
Parameters
None
Result
User can evaluate the command results(including sub-results) using IfMatched/ElseMatched
command.
List of result values:
Page 81
Page 82
Page 83
Page 84
Page 85
Page 86
Page 87
Result
Result Value
Description
PD_RESULT_OK
Command succeeded
PD_RESULT_FAILED
Command failed. In this case corresponding sub results
for PD_SendPacket and PD_ReceivePacket are valid
also (depends on the error type which has been
occurred during sending or receiving data).
PD_SUBRESULT_MSG_NOT_RECEIVED
Subresult - Get_Battery_Cap not received.
PD_SUBRESULT_RESPONSE_NOT_SUPPORTED
Subresult - Not_Supported message sent as response.
User can evaluate the command results(including sub-results) using IfMatched/ElseMatched
command.
List of result values:
Examples
Call PD_WaitForGetBatteryCap()
5.1.57 PD_SetBatteryCapDataBlock
Sets the BatteryCap Data Block in PD Exerciser. It must be called before
PD_WaitForGetBatteryCap or PD_DelayAutoResponse to take effect.
Applies setting to SecurityRequest related commands in PD Exerciser. It must be called
before PD_WaitForSecurityRequest or PD_DelayAutoResponse to take effect.