If you have a capture of SPI data with bad data at the front of the capture, you won’t get any miso/mosi data columns when you export it. However, if you actually navigate in the table to where there is valid data before exporting, the columns will get exported properly. Also during export I selected “All” and not “Visible” for columns…
-m
@michael.moretti Sorry for the trouble with that! Can you share a copy of your capture file (in .sal file format) that we can use to reproduce the issue? This looks like a bug.
Here’s one file that I know it happens with. If you try to export SPI (all fields, all data, csv) as soon as you open it, you’ll see there is no miso/mosi data at all in the export, yet in the app UI you’ll see there is valid SPI data around 1.3853s in. If you ctrl-click to the data first before export, it will export properly. Or if you chop off the bad starting noise, it will also export properly.
batleg11.sal (4.0 MB)
@michael.moretti Thanks for sending that over! We’ll take a look.
FYI –
It looks like the data table doesn’t show the mosi/miso columns on initial load:
… until after you view a row with mosi/miso data content in it.
Note: I loaded the file, and just searched for “result” in the data table to get MOSI and MISO to show up:
… and then the export included the mosi/miso columns in the CSV.
Exactly. It only works if you go to the data in the UI before exporting it (or cut out the bad data).
@michael.moretti I wanted to let you know that we’ve got this on the backlog to fix. Sorry again for the trouble with this bug in the meantime. One workaround at the moment would be to delete the portion of your capture with the error data via the instructions below.
