# Export of SPI missing columns **URL:** \ **Category:** Logic 2 Software\ **Created:** [June 15, 2026, 4:36pm UTC](https://discuss.saleae.com/t/export-of-spi-missing-columns/3751 "2026-06-15T16:36:43Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![michael.moretti](https://avatars.discourse-cdn.com/v4/letter/m/43a26b/32.png) [@michael.moretti](https://discuss.saleae.com/u/michael.moretti)\ **Post date:** [June 15, 2026, 4:36pm UTC](https://discuss.saleae.com/t/export-of-spi-missing-columns/3751/1 "2026-06-15T16:36:43Z")
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 ---
**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:** [June 24, 2026, 9:49pm UTC](https://discuss.saleae.com/t/export-of-spi-missing-columns/3751/2 "2026-06-24T21:49:18Z")
@michael.moretti Sorry for the trouble with that! Can you share a copy of your [capture file](https://support.saleae.com/user-guide/using-logic/saving-loading-and-exporting-data) (in .sal file format) that we can use to reproduce the issue? This looks like a bug. ---
**Author:** ![michael.moretti](https://avatars.discourse-cdn.com/v4/letter/m/43a26b/32.png) [@michael.moretti](https://discuss.saleae.com/u/michael.moretti)\ **Post date:** [June 25, 2026, 4:34pm UTC](https://discuss.saleae.com/t/export-of-spi-missing-columns/3751/3 "2026-06-25T16:34:25Z")
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](https://discuss.saleae.com/uploads/short-url/8pKegUQlhExcpVkNlnyAlm059cb.sal) (4.0 MB) ---
**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:** [June 26, 2026, 9:24pm UTC](https://discuss.saleae.com/t/export-of-spi-missing-columns/3751/4 "2026-06-26T21:24:58Z")
@michael.moretti Thanks for sending that over! We’ll take a look. ---
**Author:** ![BitBob](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/bitbob/32/2292_2.png) [@BitBob](https://discuss.saleae.com/u/BitBob)\ **Post date:** [June 28, 2026, 11:35pm UTC](https://discuss.saleae.com/t/export-of-spi-missing-columns/3751/5 "2026-06-28T23:35:01Z")
FYI – It looks like the data table doesn’t show the mosi/miso columns on initial load: ![image](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/2X/6/6563a414650dfedab0c02ebe33d4ab36ae56f0df.png) … 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: ![image](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/2X/3/31368377d703f6ad2b71a7bfc0c4f51f0dd1c11b.png) … and then the export included the mosi/miso columns in the CSV. ---
**Author:** ![michael.moretti](https://avatars.discourse-cdn.com/v4/letter/m/43a26b/32.png) [@michael.moretti](https://discuss.saleae.com/u/michael.moretti)\ **Post date:** [June 29, 2026, 4:41pm UTC](https://discuss.saleae.com/t/export-of-spi-missing-columns/3751/6 "2026-06-29T16:41:23Z")
Exactly. It only works if you go to the data in the UI before exporting it (or cut out the bad data). ---
**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:** [July 3, 2026, 12:09am UTC](https://discuss.saleae.com/t/export-of-spi-missing-columns/3751/7 "2026-07-03T00:09:38Z")
@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. > **[Delete Part of your Capture](https://www.saleae.com/support/logic-software/viewing-and-analyzing-data/delete-data)** > > Parts of your captured data can be deleted as needed. In previous versions of the software, we referred to this action as a trim or crop of the data. This ca... ---
**Author:** ![markgarrison](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/markgarrison/32/23_2.png) [@markgarrison](https://discuss.saleae.com/u/markgarrison)\ **Post date:** [August 3, 2026, 5:42pm UTC](https://discuss.saleae.com/t/export-of-spi-missing-columns/3751/8 "2026-08-03T17:42:20Z")
Hello, This issue was fixed and shipped in Logic 2.4.46: [Downloads | Saleae](https://www.saleae.com/downloads) Let me know if you have any trouble with it! ---
**Author:** ![michael.moretti](https://avatars.discourse-cdn.com/v4/letter/m/43a26b/32.png) [@michael.moretti](https://discuss.saleae.com/u/michael.moretti)\ **Post date:** [August 4, 2026, 11:35am UTC](https://discuss.saleae.com/t/export-of-spi-missing-columns/3751/9 "2026-08-04T11:35:33Z")
Fantastic! That was quick turnaround for the bug fix. Thanks!