3

Export Raw Data - export every sample


Avatar
Tim

Currently, digital channel entries are only recorded in the export file when data changes (not on every sample). Therefore, the number of entries in the resulting export file are dependent on the number of transitions that occur and not on the number of digital samples in the capture. Although this helps reduce the file size of the export file, it is not always preferred.

In some cases, such as with the intention to recreate the signal in external software, this is unfavorable, and it would be preferred to export every sample. This option was possible in the older Logic 1.x software, but has been removed in Logic 2.x.

A

Activity Newest / Oldest

Avatar

Tim

discuss.saleae.com/t/exporting/1330/2
"One feature that existed on the logic1 long time ago (but was removed) that can helps is when exporting to csv, put the check box “save on sample”, because today it don’t have anymore, so always export as “save on change”
“save on sample” = 1 line on the csv per sample
“save on change” = 1 line on the csv per changed logic (the only one existing now a days)"


Avatar

Tim

(#62265)
"while testing the software Logic 2 (Ver 2.3.26, demo version), I became aware that for the exported CSV-Flies (at least for digital data) the sampling intervalls are not equally spaced but the data is (presumably) only given when there was a change in one of the logic levels. I understand that this problably does save time, computing power and storage space as well.

However, this is undesirable for one of my projects, where a regular spaced intervall is needed for further calculations. Is it possible to change this behaviour in the software (demo or full version)?"


Avatar

Tim

(#61760)
"When exporting trace data to a CSV file, the sample intervals are not uniform. Why?"