FAQ

FAQ – GRL Power Deliver Compliance Test Software and USB Type-C Test Controller

 

In GRL-USB-PD software, can the user disable the pop-up windows that require manual mouse click – specifically the ones asking if scope capture looks correct? If so, how? The desire is a single “go” and have the software complete all the tests without intervention. Not sure this is possible given reversal of the current probe for source and sink mode.

  • [GRL] We have taken care to reduce the number of dialog boxes that the user needs to click through in order to ensure proper sequencing for testing. Currently, the user may experience a hand full of dialog boxes that require user intervention. We hope to reduce or eliminate user intervention in the future.

 

How do I determine which direction current probe should be connected – or does it not matter? I started the run with arrows both pointing same direction. I noticed the software prompts me for “same” or “opposite” during the run.

  • [GRL] The direction that the current probe is connected does matter to insure proper polarity of the captured current waveform. The user is prompted to change the direction as shown in the following figure(s). The top Arrow ‘Current’ loop represents the Current Loop arrow on the front of the GRL-USB-PD-C1 unit, the bottom arrow represents the Arrow on the Current probe that indicates the direction of current flow. Before pressing ‘OK’ in the dialog box, make sure that the current probe arrow corresponds to the bottom arrow in the diagram.

    FAQ01

    Figure 1: Source Testing-The Current Probe should be in opposite direction of the Current Loop

    FAQ02

    Figure 2: Sink Testing- The Current Probe should be in the same direction of the Current Loop.

 

What if vendor provided text file and Get Capabilities file mis-match? How does this get resolved by your software?

  • [GRL] The vendor has to provide the vendor information file with correct values. The tests could
    fail if there is mismatch between the vendor information and values got from Get Capabilities function. In the test report the Device Info Capabilities table shows the difference in the field values obtained during Get Capabilities and those read from Vendor Information file. In case of any difference the vendor information file has to be corrected as shown in the Device Info Capabilities table. The latest Vendor Information File generator is available on the USB-IF website at:

    http://www.usb.org/developers/tools/VendorInfoFileGenerator_v1.0.0.1.zip

    GRL tracks changes to the VIF Generator tool and verifies mismatches as part of its ‘Get Capabilities’ Feature.

 

It appears host needs to be booted to Win10 OS with special drivers (redstone1) for USB-PD. Are you aware of this host OS dependency? Is there any way around this Windows OS dependency that you are aware of?

  • [GRL] The current software driver is dependent on the type of the operating system. If driver issues occur, please contact support@graniteriverlabs.com

 

Is there any mechanism to pause the test run from the main control window?

  • [GRL] This feature is not supported in the software at this time.

 

During one test run, I was prompted to disconnect type-C cable from the port, and power cycle the PD controller. Why is this?

  • [GRL] The GRL-USB-PD-C1 Controller sometimes needs to be reset to ensure proper sequencing with the DUT, these messages were greatly reduced in version 1.2.3 of the SW during testing, but it is required during some test operations.

 

When I flip the cable, it can make contract so I guess that tester couldn’t find appropriate CC pin for some reason. (or due to fixed scope probe pin on the daughter board)?

  • [GRL] When doing a Get Capabilities it doesn’t matter which direction the CC like is connected CC1 or CC2. However, when capturing the Waveforms on the CC line, the probe capturing the CC signal must be on the pin that corresponds to which CC signal is active. If you do not see proper CC communication when probing CC1, try to flip the cable or probe on CC2.

 

Do you have any standalone application to convert R&S bin to csv file without using scope itself?

  • [GRL] GRL does not support any standalone application for converting scope waveform file to .csv format. Waveforms must be saved as .csv from the Scope. Consult with vendor specific documentation for how do this.

 

Is there a way to check if the current SW version installed on my scope is up to date?

  • [GRL] The current released version is posted on graniteriverlabs.com/usb-pd Support page. As a customer you will receive email notice when new updates are available.

 

Regarding the menu of the Controller Configuration Utility, in Configure tab, request messages always configures with the Giveback bit set to 1. Is there a possibility to send a Request command with Giveback bit (header) set to 0? My UUT doesn’t have the possibility to accept a request with the Giveback bit set to.

  • [GRL] In the Configure Tab “Clear GiveBack Flag” would set the Give Back Flag bit to zero.

 

What eLoads does GRL Support with their GRL-USB-PD/C1 Solution?

 

Do probing adapters in GRL’s USB-PD presentation come with the GRL-USB-PD-C1 Type-C Test Controller?

  • [GRL] Yes, the EXT-1 and EXT-2 Boards that plug into are included in the GRL-USB-PD-C1. Refer to Appendix A (Section 7) of the MOI and User Guide for included accessories.

 

Do power delivery coupon adapters shown in GRL’s USB-PD presentation come with the GRL-USB-PD-C1 Type-C Test Controller?

  • [GRL] No, Power Delivery Coupons that provide a ‘pass-through’ of the Type-C Connector and break out the low speed signals from the Type-C connector are not included in the GRL-USB-PD-C1 product. Power Delivery Coupons are available from:

    http://www.wilder-tech.com/usb-typ-c-pd.htm

 

Does the software have a separate mask for far end Testing?

  • [GRL] In all cases we currently test to the Tx masks with no load on Vbus. The lower amplitudes on the Rx mask in the spec assume worst case loading on the DUT. In order to do this test, we’d need to reference the ground of the measurement (scope ground) to the ground at the near end and make the far
    end eye measurement while Sinking load current out of the DUT. For compliance testing we use Tx mask only.

 

Electronic Loads not getting detected with Tektronix VISA.

  • [GRL]
    Please refer to section “Tektronix VISA Configuration and eLoad Detection” in the document “C:\GRL\Documents\GRL USB Type-C Power Delivery and Alt Mode Test Method of Implementation (MOI) and User Guide.pdf” to do the required configuration.

 

Will there be any near term changes to PD spec, and if there are, how will GRL handle this? Will we get assurance that the software will be updated accordingly (and for free vs a charge)?

  • [GRL]
    Not PD 2.0 CTS (Test Plan). There is a USB PD 3.0 CTS under development, but testers supporting
    this (including GRL) will not be available until Q3 of 2017. So if customers are testing PD2.0 Designs, they should purchase Solution now and not worry about major changes in 2.0 CTS.

 

What is the lead time for PD controller?

  • [GRL]
    In Stock, we can fulfill an order placed today in a few days.

 

Why is PD coupon now optional? (PD coupons are now part of GRL USB PD controller)

 

Within the GRL SW, can different profiles be created and recalled to test different products (e.g. with different voltage levels)?. Is SW flexible to be able to change limits (e.g stricter than the specification)?

  • [GRL]
    The DUT Profiles (Different Voltage Levels) are determined by doing a ‘Get Capabilities’ with from the DUT, combination of DUT Capabilities and Type of DUT defines the Test List to be tested. Tests are done on a Pass/Fail Basis as defined in the spec and a report is generated. If there are Failures, you can go back and re-test failures against spec limits. Currently we don’t have any way to change the limits to be stricter than the Specification, but would be open to accepting more detail on what the customer is looking for. Kindly email your request to support@graniteriverlabs.com

 

Does GRL-USB-PD/C1 Solution Support USB-PD 3.0?

  • [GRL]
    No, USB 3.0 is the latest spec, but there is NO CTS or compliance program for 3.0 – look for these later 2017. Contact info@graniteriverlabs.com to learn about GRL plans to support USB-PD 3.0 and how to get your current USB PD 3.0 design tested. GRL Lab testing for USB PD 3.0 may be an option before Complete USB PD 3.0 Solutions are available.

 

What is the latest Revision of the USB-PD 2.0 Specification and CTS (Test Plan) used for Certification?

  • [GRL]
    The current USB PD compliance program addresses the 2.0 version of the PD specification. The Compliance Plan itself happens to be Revision 1.0 Version 2.

 

What are the Compliance Test Program requirements to get a USB PD 2.0 device Certified and how does GRL-USB-PD/C1 address these requirements?

  • [GRL]
    For USB PD 2.0, there are two MOIs (Methods of Implementation) that support the USB PD 2.0 compliance plan:

    • GRL’s solution is used to perform the Communications Engine MOI
    • Ellisys solution is used to perform the Deterministic Engine MOI
    • Both MOI’s are required to test for USB PD compliance.

    There is a table in Chapter 12 of the Compliance Plan that maps test requirements to the two MOIs. GRL (Communications MOI) supports all required test items. Ellisys (Deterministic MOI) does not.