# PD3.1 Analyzer

**URL:** <https://discuss.saleae.com/t/pd3-1-analyzer/2855>\
**Category:** Uncategorized\
**Created:** [May 2, 2024, 12:08pm UTC](https://discuss.saleae.com/t/pd3-1-analyzer/2855 "2024-05-02T12:08:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![haia.amsha98](https://avatars.discourse-cdn.com/v4/letter/h/eb8c5e/32.png) [@haia.amsha98](https://discuss.saleae.com/u/haia.amsha98)\
**Post date:** [May 2, 2024, 12:08pm UTC](https://discuss.saleae.com/t/pd3-1-analyzer/2855/1 "2024-05-02T12:08:38Z")

</div>

Hi ,  
I’m using PD3.1 analyzer in saleae to parse CC lines.  
I was able to do it , but now I want to export it to a csv file using the HLA-USB-PD , is it possible?

I’m using this code line in a script: PD\_CC1\_analyzer = capture.add\_high\_level\_analyzer(‘C:\Users\lab\_ccd01\Downloads\hla-usb-pd-master\hla-usb-pd-master’,‘PD3.1 Analyzer’,input\_analyzer=Manch\_CC1\_analyzer, label=f’PD\_CC1’)  
but getting this error:

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/2X/2/250005afb68431df1e94037d18a2d5d40f395e41.png)  
Although the analyzer is installed indeed.  
thanks

---

<div class="post-metadata">

**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:** [May 2, 2024, 2:09pm UTC](https://discuss.saleae.com/t/pd3-1-analyzer/2855/2 "2024-05-02T14:09:48Z")

</div>

Did you install the HLA from the path indicated:

> [@haia.amsha98](#):
>
> ‘C:\Users\lab\_ccd01\Downloads\hla-usb-pd-master\hla-usb-pd-master’

… or was installed from Saleae marketplace, such as:  
`'C:\Users\<user-id>\AppData\Roaming\Logic\Marketplace\\<#>'`

**OR** (more generically)

`os.path.expandvars('%APPDATA%\Logic\Marketplace\\<#>')`

… which _might_ be (for you):  
`'C:\Users\lab_ccd01\AppData\Roaming\Logic\Marketplace\\155'`  
**OR**  
`os.path.expandvars('%APPDATA%\Logic\Marketplace\\155')`

… assuming that `155` is always assigned by Saleae marketplace for ‘PD3.1 Analyzer’ HLA for everyone who installs it (??)

Note: the `<#>` above needs to be replaced with whatever Saleae Logic 2 chose for the extension number when installed. It would be nice if Saleae included a pre-defined variable that corresponded to the marketplace path regardless of host (Windows, Linux or Mac), as well as a way to identify this subdirectory/extension number automatically.

Just confirm or find the path in the extensions subdir on your PC with the `extension.json` that contains:  
`"name": "PD3.1 Analyzer",`

Unfortunately, Saleae does not have a universal method of finding extensions and especially their path strings. It is [even a problem for the save files](https://ideas.saleae.com/b/feature-requests/identify-extension-by-name-and-not-by-path-of-extensionjson-file/) (\*.sal), as the extension directory is based on a user-specific pathname.

Note: you can save a capture file with the `"PD3.1 Analyzer"` added, and confirm the path string used by the Saleae software. Just ‘unzip’ the saved capture file (\*.sal) **[1]** and search for `"name":"PD3.1 Analyzer","path":"C:\Users\<...>"` within the `meta.json` to see the path saved.

**[1]** For reference, a saved capture file (extension `*.sal`) can be unzipped to see the internal contents. You can right-click and select (from [7-Zip](https://www.7-zip.org/) context menu) to “Extract files…”, or rename the file extension from `*.sal` to `*.zip` and use any other unzipping utility.