Why doesn't EZ-PD Analyzer show decoded Request messages with bad PDO number?

[PeJa_4320651]

Much better behavior would be to show the decoded message with the bad PDO number flagged, perhaps by highlighting in red. As it is, the analyzer gives no clue to the developer to why the request message's RDO isn't being shown.

[ShifangZ_26]

Hi ,

Thank you for your feedback. We would like to understand more details about your feedback. Could you please kindly share the .ccgx file which is includes the bad PDO number flagged in this threads?

Please kindly noticed that EZ-PD Analyzer is decoding the message as per PD2.0 SPEC. We are going to support PD3.0, the schedule is not settled currently.

Best Regards,

Lisa

[PeJa_4320651]

I've attached two capture files. BadPDONum has the Object Position field in the Request message set to 2 which is incorrect - the previous source capabilities message only supplied one Power Data Object.

GoodPDONum has corrected the Object Position field value to 1.

Note that EZ-PD Analyzer only shows the SOP Type line in the Detail View for the Request message containing the bad Object Position value:

[ShifangZ_26 · Accepted solution]

Hi Peter,

The Request package is strange, there are only one source cap on CC line, but the REQUEST is asking second Object Position.

We have received your feedback, it will report to software team. Please take a attention on the updates of Ez-PD Analyzer Tools.

Best Regards,

Lisa