# Export formats for low-level analyzers

**URL:** <https://discuss.saleae.com/t/export-formats-for-low-level-analyzers/1040>\
**Category:** Uncategorized\
**Created:** [May 24, 2021, 12:03pm UTC](https://discuss.saleae.com/t/export-formats-for-low-level-analyzers/1040 "2021-05-24T12:03:50Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![MitekPL](https://avatars.discourse-cdn.com/v4/letter/m/a9adbd/32.png) [@MitekPL](https://discuss.saleae.com/u/MitekPL)\
**Post date:** [May 24, 2021, 12:03pm UTC](https://discuss.saleae.com/t/export-formats-for-low-level-analyzers/1040/1 "2021-05-24T12:03:50Z")

</div>

I found I’m able to load my low-level analyzer to Logic 2.  
It works fine with 1.1.29 and I see all export types I declared in my analyzer:  
 ![image](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/5504c54dff27d53d2fe9a05aa3bfad96a822ff63.png)  
However when using Logic 2 I do not see my own export types:  
 ![image](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/2504b6ab51f97cdbfdbe0df7ba2e2230ed106d64.png)  
Is this a bug in implementation support low-level analyzer in Logic 2?

---

<div class="post-metadata">

**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:** [May 25, 2021, 2:44am UTC](https://discuss.saleae.com/t/export-formats-for-low-level-analyzers/1040/2 "2021-05-25T02:44:14Z")

</div>

@MitekPL That’s strange. Thanks for reporting this behavior to us. Low-level analyzers should work in Logic 2. One thing I notice is that the Data Table is not being populated. Have you added your I2S / TDM analyzer (I assume this is your custom analyzer?) on top of already captured data? If not, then the Export to TXT/CSV will be greyed out if there is no data to export.

In case the above doesn’t help, would you mind sending over your Low-level analyzer files via the link below? Please also include a sample capture file (.sal file format) with the proper data so we can test exporting it.  
[https://contact.saleae.com/hc/en-us/requests/new](https://contact.saleae.com/hc/en-us/requests/new)

Instructions on exporting a .sal file:

> **[Capture & Preset File Management](https://support.saleae.com/user-guide/using-logic/saving-loading-and-exporting-data)**

Please also let us know in the “description” section that we spoke via this Discuss Forum post so that I know it’s you when the file comes in. We can take a look and try to reproduce this on our end once you send those over.

---

<div class="post-metadata">

**Author:** ![MitekPL](https://avatars.discourse-cdn.com/v4/letter/m/a9adbd/32.png) [@MitekPL](https://discuss.saleae.com/u/MitekPL)\
**Post date:** [May 25, 2021, 6:20pm UTC](https://discuss.saleae.com/t/export-formats-for-low-level-analyzers/1040/3 "2021-05-25T18:20:51Z")

</div>

Even with data captured I see only CSV format export on the list (with captures data it is not grayed out).  
I sent message via link you have provided.

---

<div class="post-metadata">

**Author:** ![Jonathan](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/jonathan/32/2142_2.png) [@Jonathan](https://discuss.saleae.com/u/Jonathan)\
**Post date:** [May 25, 2021, 8:56pm UTC](https://discuss.saleae.com/t/export-formats-for-low-level-analyzers/1040/4 "2021-05-25T20:56:04Z")

</div>

I had also noted this limitation quite some time ago. So it is not just an issue with his analyzer but perhaps an oversight in the V2 implementation. For me this is a very useful/important feature to have.

For what is it worth, here is my post which also discussed this:

> [@Missing V1 analyzer SDK plugin features and ideas](https://discuss.saleae.com/t/missing-v1-analyzer-sdk-plugin-features-and-ideas/684):
>
> Perhaps these are already on the list of TODOs/backlog but I figure I would mention them here: In V1 an analyzer had the option to define any given “export” option. This is currently not available in V2 and is a major feature that is missing in my opinion. While the integrated spreadsheet in V2 is nice, it is quite limited in nature and it cannot possibly cover all the use cases that a developer of a plugin may want. Is there a plan to support this? Here is an example of a plugin running o…

---

<div class="post-metadata">

**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:** [May 25, 2021, 10:50pm UTC](https://discuss.saleae.com/t/export-formats-for-low-level-analyzers/1040/5 "2021-05-25T22:50:48Z")

</div>

@Jonathan Thanks for clearing that up and for sharing your post from last year.

@MitekPL It looks like we haven’t added support for custom export options in Logic 2. Apologies for missing that in your previous message. This is not a bug with the software, but something we just haven’t implemented yet. I had initially thought you were referring to the greyed out “Export to TXT/CSV” option in the Logic 2 menu.

I went ahead and added both of your posts as comments in the meantime in the idea post below so we can track your need for it. I’ll also bring this up with the team here:  
[https://ideas.saleae.com/b/feature-requests/custom-export-options-via-extensions/](https://ideas.saleae.com/b/feature-requests/custom-export-options-via-extensions/)
