We're having trouble reading the resultant .mat files after converting from the .psdata file. The .psdata was taken from a Picoscope 3406D MSO using software version 6.11.10.1608 and has the following properties:
Sample interval: 1 ns
Sample rate: 1 GS/s
No. samples 100,000,004
Channel A
Range +/-5V
Coupling DC
Digital Channels: Off
When trying to load the data in MATLAB, it gives the error:
Error using load
Unable to read MAT-file ..\filename.mat
File may be corrupt.
I have also tried Octave and it gives a similar error. The reason we need to use the binary file format is for the large dataset. I think CSV and txt are both limited to 1 million per channel. Any ideas?
The PicoScope 6 software saves to MATLAB v4 file format. Unfortunately, MATLAB is only able to handle arrays with 100 million elements or less when saved in this format.
Please e-mail support@picotech.com and we will look to assist you further. It would be helpful if you can indicate which version of MATLAB you are using and whether it is 32-bit or 64-bit.
I have the same problem here.
(PicoScope 5444b, channels A&B&C, 500ms/div, 5mio samples total)
I use 3 channels with 5.000.000 samples each.
With R6.10.18 I got a truncated mat-file with partly invalid data.
(Only about 1.600.000 samples for A and B each and about 490.000 samples for C)
With R6.11.12 and R6.12.2beta I get the complete channels A and B with correct data, but for channel C I get the
message (GNU octave; no Matlab available):
I already tried Beta 6.12.2 with no success with mat files.
But I just tried as you suggested to save the data as txt file and it worked (so far).
The errors still present are:
- The first column, representing the time, starts with unit (ms) but the values switch then to (s) without notice, so I
would read out the wrong time stamps.
- Somewhere later on (at time 2.655116s) the header is repeated in the data stream, but now with time unit (s). The
measured data values at that timestamp are lost, which would represent a discontinuity in time.
For now I can continue with this workaround. Thank You!
Could you please send the corresponding PicoScope psdata file to support@picotech.com and I can check the export to see if I can repeat the issue described.