|
Tim |
Currently, many pre-installed analyzers, including custom LLAs (low level analyzers) show data in the Data Table as the framev1 type, which offers only a single column.
We should add support for multiple columns for more analyzers, including custom LLAs.
Activity Newest / Oldest
Tim
discuss.saleae.com/t/missing-v1-analyzer-sdk-plugin-features-and-ideas/684/3
"The export is a very useful feature, is there any progress on adding it back to Logic 2.x?
I can export the data from my custom low-level analyzer as it is shown in the data table by clicking on the three vertical dots next to the table search bar and then clicking “Export Table”. However, since there is only v1frame type available, only the value column can be used to display information. Thus if you don’t want to just show the hex value, you have to use text in the value column and not in a dedicated “description” column, for example. This is bad for further automated processing.
In Logic 1.x the AnalyzerResults::GenerateExportFile() function was used to generate a custom export. This seems to no longer be supported in Logic 2.x. If I click on the three vertical dots next to my analyzer and then select “Export to TXT/CSV”, I simply get an empty file."
Tim
(#61096)
The user below requires building a custom analyzer (based off our SPI analyzer) that supports Frame v2
"The built in SPI Analyzer tool is different to the SPI Protocol Analyzer Source Code that I’ve found and compiled
Can you please upload the build in SPI analyzer source code."
Tim
One use case here: discuss.saleae.com/t/custom-analyzers/187/17