# PD 3.1 analyzer **URL:** \ **Category:** Uncategorized\ **Created:** [March 22, 2024, 7:14am UTC](https://discuss.saleae.com/t/pd-3-1-analyzer/2788 "2024-03-22T07:14:41Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![fei.wu](https://avatars.discourse-cdn.com/v4/letter/f/e274bd/32.png) [@fei.wu](https://discuss.saleae.com/u/fei.wu)\ **Post date:** [March 22, 2024, 7:14am UTC](https://discuss.saleae.com/t/pd-3-1-analyzer/2788/1 "2024-03-22T07:14:41Z")
Hi Saleae, Why can’t set up for the PD 3.1 analyzer ![image](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/2X/e/e15cd7064f54e7a3829556025c8448e9f9179d93.png) ---
**Author:** ![timreyes](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/timreyes/32/108_2.png) [@timreyes](https://discuss.saleae.com/u/timreyes)\ **Post date:** [March 22, 2024, 10:22pm UTC](https://discuss.saleae.com/t/pd-3-1-analyzer/2788/2 "2024-03-22T22:22:06Z")
@fei.wu Thanks for writing in. The USB PD HLA (high level analyzer) needs to be configured with an existing supported LLA (low level analyzer) as an input — in particular, the Manchester analyzer. Instructions for this are provided on the USB PD (Biphase Mark Code) extension page like shown below. ![Screenshot 2024-03-22 at 5.19.20 PM](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/2X/3/3450f8a713b313f350ab2542897bac241cf7c68e.png) ---
**Author:** ![timreyes](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/timreyes/32/108_2.png) [@timreyes](https://discuss.saleae.com/u/timreyes)\ **Post date:** [March 22, 2024, 10:24pm UTC](https://discuss.saleae.com/t/pd-3-1-analyzer/2788/3 "2024-03-22T22:24:53Z")
@fei.wu I just realized that you are using a different USB PD analyzer developed by a community user and not by us. Have you followed their instructions on their extension overview page? ![Screenshot 2024-03-22 at 5.23.13 PM](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/2X/1/15a8f6eb365b1c09e0f17679991eb0176a49eff5.png) ---
**Author:** ![fei.wu](https://avatars.discourse-cdn.com/v4/letter/f/e274bd/32.png) [@fei.wu](https://discuss.saleae.com/u/fei.wu)\ **Post date:** [March 25, 2024, 9:15am UTC](https://discuss.saleae.com/t/pd-3-1-analyzer/2788/4 "2024-03-25T09:15:30Z")
Thanks Timreyes, Yes, the PD 3.1 CC signal is the Manchester coding, but when I switch to Manchester protocol, and follow the PD3.1’s setting, mode is FN1, bit rate is 300000, the script show below error, do you know what reason cause it, thanks. ![image](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/2X/d/d42bc24cec01f68c265aefe1ae38cbc03a30e2eb.png) ---
**Author:** ![timreyes](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/timreyes/32/108_2.png) [@timreyes](https://discuss.saleae.com/u/timreyes)\ **Post date:** [March 25, 2024, 11:09pm UTC](https://discuss.saleae.com/t/pd-3-1-analyzer/2788/5 "2024-03-25T23:09:38Z")
@fei.wu As a quick check, it looks like the original developer uploaded 2 versions of their extension (one is version 0.0.6, and the other is 0.0.4). Are you using 0.0.6? It’s possible they may have fixed this bug in that version. ![Screenshot 2024-03-25 at 6.07.03 PM](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/2X/b/bd8449f131ad3a555e980de1e03d44e137744ced.png) In any case, since we did not develop the HLA, your best bet would be to reach out to the original developer who uploaded the extension to our extensions marketplace in case you are still running into issues with version 0.0.6 if their extension. It looks like they’ve allowed for posting issues on their GitHub repository for this extension via the link below. > **[Issues · eugenecyyeh/Saleae-PD3.0-analyzer](https://github.com/eugenecyyeh/Saleae-PD3.0-analyzer/issues)** > > Contribute to eugenecyyeh/Saleae-PD3.0-analyzer development by creating an account on GitHub. ---
**Author:** ![fei.wu](https://avatars.discourse-cdn.com/v4/letter/f/e274bd/32.png) [@fei.wu](https://discuss.saleae.com/u/fei.wu)\ **Post date:** [March 26, 2024, 7:26am UTC](https://discuss.saleae.com/t/pd-3-1-analyzer/2788/6 "2024-03-26T07:26:35Z")
Thanks Timreyes, I have fixed this issue. Thanks again, Another question for DP AUX analyzer, I found a DP AUX analyzer on the github, can you let me know where folder path should be put the compiled \*dll file [Alex-the-Smart/DPAUXAnalyzer: Display Port AUX Analyzer for Saleae Logic (github.com)](https://github.com/Alex-the-Smart/DPAUXAnalyzer/tree/master) ![image](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/2X/f/f4b0c703834f7f0ff404e48e8034eb7bc8a3ba75.png) ---
**Author:** ![timreyes](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/timreyes/32/108_2.png) [@timreyes](https://discuss.saleae.com/u/timreyes)\ **Post date:** [March 26, 2024, 10:41pm UTC](https://discuss.saleae.com/t/pd-3-1-analyzer/2788/7 "2024-03-26T22:41:38Z")
@fei.wu I’m glad to hear you were able to solve that! Instructions for installing a custom analyzer LLA (low level analyzer) are provided below. > **[Import Custom Low Level Analyzer | Saleae Support](https://support.saleae.com/faq/technical-faq/setting-up-developer-directory)** ---
**Author:** ![ahmed](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/ahmed/32/1897_2.png) [@ahmed](https://discuss.saleae.com/u/ahmed)\ **Post date:** [November 24, 2024, 11:36pm UTC](https://discuss.saleae.com/t/pd-3-1-analyzer/2788/8 "2024-11-24T23:36:13Z")
Hey I am running in to the exact same issue can you please share how did you fix it ? Tx, Ahmed ![Screenshot 2024-11-24 at 6.38.06 PM](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/2X/b/bb47928922e70e5bf187f6c2f8d08c19801bf9be.png) ---
**Author:** ![BitBob](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/bitbob/32/2292_2.png) [@BitBob](https://discuss.saleae.com/u/BitBob)\ **Post date:** [November 25, 2024, 12:15am UTC](https://discuss.saleae.com/t/pd-3-1-analyzer/2788/9 "2024-11-25T00:15:02Z")
According to the issue reported: > > > Hi, > > When I load this HLA, it shows as below error, can you help to check it,… thanks. > > !\[image\](https://github.com/eugenecyyeh/Saleae-PD3.0-analyzer/assets/164975467/5aba8c13-de11-4739-85ea-50be3a5c7066) The proposed fix was: > Could you please check if the input data was set correctly? > > The input data for Manchester coding should be set to send one bit per frame. Hope that helps. ---
**Author:** ![ahmed](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/ahmed/32/1897_2.png) [@ahmed](https://discuss.saleae.com/u/ahmed)\ **Post date:** [November 25, 2024, 12:34am UTC](https://discuss.saleae.com/t/pd-3-1-analyzer/2788/10 "2024-11-25T00:34:59Z")
Yeah It’s all well set. It’s start decoding then it stops for some reasons example here ![Screenshot 2024-11-24 at 6.45.26 PM](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/2X/a/a99b2fe65fe99b8dd521e095707ecb5af478c3f8.png)