All guides

File handling

Batch converting PicoScope 7 (.psdata) files to CSV

Native .psdata captures are stored in a protected container that only PicoScope can open. PicoScope 7 ships a headless BatchConvert command that converts a whole folder in one go — no window opens, and the CSVs load instantly in WaveAssist Pro.

1. Put your captures in one folder

Copy every .psdata file you want to analyze into a single folder, for example C:\Captures (Windows) or ~/Captures (macOS). Sub-folders are not converted, so flatten them first.

2. Run the batch conversion

BatchConvert takes three arguments: the folder with your captures, the folder for the CSVs (it is created for you), and the target extension. Adjust the two paths and run it — Command Prompt or PowerShell on Windows, Terminal on macOS:

"C:\Program Files\Pico Technology\PicoScope 7 Automotive\PicoScope.exe" BatchConvert "C:\Captures" "C:\Captures\csv-export" .csv
"/Applications/PicoScope 7 Automotive.app/Contents/MacOS/PicoScope7" BatchConvert ~/Captures ~/Captures/csv-export .csv

On a Mac, PicoScope 7 runs through Apple's Rosetta. If the command answers Bad CPU type (common after a macOS upgrade), run softwareupdate --install-rosetta in Terminal once, then run the command again.

Using the T&M edition instead of Automotive? Same command, different install folder:

"C:\Program Files\Pico Technology\PicoScope 7 T&M\PicoScope.exe" BatchConvert "C:\Captures" "C:\Captures\csv-export" .csv

Don't put a trailing backslash on the folder paths — the command fails with one. The old PicoScope 6 flags (/c ... /f csv) no longer exist; PicoScope 7 ignores them and simply opens its window.

3. What comes out

The converter reports progress per file (SUCCESS or a reason) and ends with a summary. Each capture becomes a folder named after the file, holding one CSV per stored waveform buffer — 2018_F150_CrankSync.psdata with four buffers becomes 2018_F150_CrankSync/2018_F150_CrankSync_1.csv through _4.csv. Every CSV keeps the original channel headers and declared units, which drive channel mapping in WaveAssist Pro.

If a file is reported as "conversion of this file is prohibited", the export lock is inside the capture itself — demo captures and files from shared waveform libraries carry it, and no PicoScope edition can convert them. Your own recordings convert normally.

4. Upload the CSV files

Drop the resulting .csv into the analyzer. WaveAssist Pro handles captures up to 300 MB, keeps every sample for the diagnostic math, and downsamples only what's drawn on screen. Full-length captures at high sample rates can exceed that — zip each CSV (they compress roughly 6:1 and WaveAssist Pro reads zipped CSVs directly), or zoom into the fault window in PicoScope and re-save before converting.

Manual export (no command line)

In PicoScope 7, open the capture and choose File → Save As, then pick CSV (*.csv) or Text file. Keep all channels enabled so timing comparisons stay intact.

Tips for clean exports

  • Export the full capture buffer, not just the visible window.
  • Keep the sync / cylinder-1 trigger channel in the export.
  • Use seconds or milliseconds for the time column — both are parsed automatically.
  • Avoid renaming channel headers; they drive channel mapping.