File handling
Batch converting PicoScope (.psdata) files to CSV
Native .psdata captures are stored in a protected container that only PicoScope can open. CSV exports load instantly in WaveWrench Pro — and you can convert an entire folder in one command.
1. Put your captures in one folder
Copy every .psdata file you want to analyze into a single folder, for example C:\Captures. Sub-folders are not converted, so flatten them first.
2. Open Command Prompt or PowerShell in that folder
In File Explorer, hold Shift, right-click empty space inside the folder and choose Open in Terminal (or Open PowerShell window here). You can also type cmd in the Explorer address bar and press Enter.
3. Run the batch conversion
This converts every capture in the folder to a matching .csv file:
picoscope /c "*.psdata" /f csvTo convert a single capture and name the output yourself:
picoscope /c filename.psdata /f csv /o output.csvIf Windows reports that picoscope is not recognized, the PicoScope install folder isn't on your PATH. Call it with the full path instead:
"C:\Program Files\Pico Technology\PicoScope 7\picoscope.exe" /c "*.psdata" /f csvPowerShell: convert a whole folder
If the wildcard form doesn't pick up every capture, loop over the folder in PowerShell so each file is passed by its full path:
Get-ChildItem *.psdata | ForEach-Object { picoscope /c $_.FullName /f csv }Run it from inside the capture folder (for example C:\Captures), or add -Path "C:\Captures" to Get-ChildItem to target it from anywhere. Add -Recurse if your captures are spread across sub-folders.
Output file naming
Converted files keep the original filename and only swap the extension — 2018_F150_CrankSync.psdata becomes 2018_F150_CrankSync.csv, saved next to the original. Name your captures by vehicle and test before converting and you can drop the whole batch straight into WaveWrench Pro without renaming anything.
4. Upload the CSV files
Drop the resulting .csv into the analyzer. WaveWrench Pro handles captures up to 100 MB, keeps full resolution for the diagnostic math, and downsamples only what's drawn on screen.
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.
Can't read this PicoScope file
Reference: this is the same alert the uploader shows when a native .psdata capture can't be decoded.
Run this in Windows Command Prompt or PowerShell from the folder that holds your captures to convert every .psdata file at once:
picoscope /c "*.psdata" /f csv