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.
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: