Custom Export Options via Extensions

Voters 13

C
J
C
B
A
R
+ 7 voters
K
C
P
C
G

Open
Subscribe

Tim

Allow custom capture export options for custom protocol analyzer exports.

30-01-2021 -

Activity Newest / Oldest

Richard

We would like to be able to save pre-processed data into a binary file for further offline processing. Since the .sal format is proprietary and undocumented we can't use that directly for offline processing. The .bin file format is inefficient (a 31MB .sal converts to >2GB of .bin) and it creates one file per channel instead of a single dump.

We can workaround this by having an analyzer config string that is the path to where a file should be dumped, but a this doesn't provide any user interaction for file choice so on each run of the analyzer we must either overwrite any existing dump file, or create another file. A custom export option would be better.

Tim

(#86022)
"Export to Pcap File Format
Is there a export to pcap format availalble.
Reason for the question is I want to display UART Data within a wireshark."

Tim

(#85070)
"It would be great if the Logic software could play the captured waveform through the speaker, or failing that, export it as WAV file data."

Tim

(#66885)
"Hi, have you disabled custom analyzer output formats in Logic 2?

I have written a TDM decoder that has more decode options than the built in I2S allows (mainly more than 2 channels per line). In Logic 1, this plugin also supports a WAVE file export, that takes the decoded audio data and saves it straight to a WAVE file to be loaded into a tool like Audacity. This works fine in Logic 1, where I can select TXT/CSV output or WAVE output, but this feature seems to have been disabled in Logic 2 even though everything else works. The extra menu option simply doesn't show up. Was this intentional, and can I expect this feature to return? Or should I work on another little program to convert the TXT output to a WAVE file instead?"

Tim

Support export options that would allow importing into Wireshark for further analysis of captured data.

(66278)
"It should help/facilitate resolving some kind of issues just by using well known and powerful Wireshark tool for filtering/searching some kind of messages. Moreover it should enable using user defined Wireshark parsers to further parse messages captured from physical lines (like I2C/UART/USB and so on)"

Asger

We are currently stuck at Logic 1.x because we use this feature for exporting large amounts of captured digital data as binary files - the CSV export is very slow for us and take up a lot of diskspace. I would really like to see this (re-)implemented in Logic 2.

Tim

(#60914)
"Our custom analyzer supports it own export types

These are not visible in the logic 2 SW – at least I have not been able to find them.

In logic 1.2.18 they appears as menu items in the analyzer’s context menu.

In logic 2 only “Export to TXT/CSV” is shown as an option and it does not seem to be the custom analyzers own export."

Tim

discuss.saleae.com/t/missing-v1-analyzer-sdk-plugin-features-and-ideas/684
"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?"

Tim

discuss.saleae.com/t/export-formats-for-low-level-analyzers/1040
"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:
However when using Logic 2 I do not see my own export types:"

Peter Jaquiery

Doing this as a plugin along the lines of a HLA, but with access to both data and analyzer output, would make tasks like writing a CAN trace specific output file (see ideas.saleae.com/b/feature-requests/can-trace/), for example, easy.

Tim

I completely agree! I actually changed the title of their feature request to reflect that.