Hello Martyn, Thank you. With your help I better understand how it works. 1/ Firsty, only the time scale is respected. The number of sample selected is a wish and software is going to select the highest possible which can be very different from the request for many reasons. It can be scope real memo...

Hello Martyn, Here is the info: >> PicoScope® 6 - PC Oscilloscope software version: 6.11.12.1692 >> Copyright © 1995-2016, Pico Technology Ltd. >> Model: PicoScope 6403C >> Serial Number: CO808/001 >> USB Version: 3,0 >> Calibration Date: mardi 3 novembre 2015 >> Hardware Version: 1 1 >> Driver Vers...

Thank you Martin, However this doesn't solve my issue. In order to avoid already solved issues, before applying your recommendation, I decided to upgrade Picoscope 6. Firstly, since I installed the latest revision, with 100ms/div and 2GS range settings I see that the scope gets 156M samples at 156.3...

Hi, Reading your explanations I tried the following: Time base = 100ms/div Number of sample = 2GS Which resulted in an automatic setting at 312.5 MS/s, 312 M samples record with my 6403C With my application 109MS/s is enough and I need 2 to 3 sec recording. Thus I set Time base = 200ms/div Number of...

Thank you bennog, Characteristics of the signal seems to be accurately retreived by Scilab. It seems to be a solution if enough RAM is available on the host PC.In order to avoid increasing RAM on all our PC it would be good to have a solution from Picoscope with an option to export signals by parts ...

Yes. One example file is here:
https://www.dropbox.com/s/8ct917fg0bukz ... e.mat?dl=0
Regards,
François

I'm working with Win7 64Bits and tried with Scilab6 b2 64bits and Octave "i686-w64-mingw32". Both platforms understand the structure but tell me that the array dimention is out of range. Maybe the only solution is that PicoScope6 allows to split the export into several parts or allows to export a se...

In order to apply signal processings to my acquisitions I need to export files. The .mat format is convenient however I end up with .mat files exceeding 1GB. My usual tools fail to import .mat files of such size. They report an issue "dimension too large". I'm working with Scilab 6b2 but I also trie...