Thanks again for fast reply. The acquired voltage values I sent you was generated from traces in 6000 psfiles converted to csv (using the DOS command Picoscope /c *.psdata /f csv /b all). In a Linux bash script I then selected the maximum value of each file. This gave me 6000 values that included multiple instances of nearly all possible voltage levels. Than I ran the bash commands "sort" before "uniq" that gave me the single instances of nearly all possible voltage levels, i.e. the range of data that I sent to you. None of the above Linux operations altered any of the values, but I did multiply them by 1e8 before I sent them to you.
I also have tried to use the measurement "Maximum" feature, and upon each trigger Alarm, run the script Picoscope.com /a Measurements.CSV? >> mydata.csv. This is more effective and would be my preferred method, but in that case the voltage homogeneity between ADC levels is even worse. A set of these data (~34000 acquisitions) I have attached 1: rawdata directly after the Picoscope script, appended values, 2: only the max values (with removal of other columns, removal of the "mV" string and deletion of all header lines), and 3: only single instances of the max values. The last one is similar to what I sent you before and if you plot these values against a linear X, you will again see the inhomogeneity between the steps.
Regarding API & trigger. This is not so much about type of trigger, it is about recognizing the trigger remotely so that buffers can be read only upon each new trigger. You may imagine that if triggered events are rare, as in my case now, I don't want to read the same buffer over and over again. I want to wait until I get a new trigger and then read. Maybe this is possible (?), but it is more preferred anyway for me to just get correctly binned data directly generated from Picoscope 6 (programming is time consuming).
Thank you again very much for your assistance.
Best regards, Einar