Signed 16 bit as the voltages can be positive or negative.

There is nothing in the SDK to handle this, you just need to apply the corrections using simple maths in your application.

So what issues do you have with the GitHub example?

Have you taken a look in the Picotech GitHub Pages

Make sure you leave it a few minutes on first run, it takes a significant time to sort out mono the first time around.

Which 5000 series device do you have ?
and which PicoSDK have you installed ?

If you use View->ViewProperties you will get a panel on the right hand side that shows exactly how the scope is set up. The number of the samples at the top is how many you would like to connect, however depending upon the time you have selected across the screen, and the number of channels enabled,...

Have you tried the example code from GitHub?

Not sure, it has been like that from the start of Picoscope 6. I have a feature request to add a tracking cursor so that you drag in a time ruler and you get the related levels for all active channels.

Have you used ps4000aSetProbeInteractionCallback as this will setthe driver up to allow you to use the correct ranges for the probe that it detects. Otherwise it will only allow standard ranges as you have found.

You need PicoLog 5.25.3

If you extend the B scale beyond the 10V, the blue line intersects at roughly where 20V would be. The box is just a position on the screen, nothing to do with the traces.

You will need to call the function twice with the segment index changing, but this can easily be done in a loop.

Please email support@picotech.com and the LabVIEW specialists in the team will be able to assist. The error code number itself does not highlight the issue, and I am unable to translate the German error message.

This is already on the feature request list but is not a simple fix due to the architecture of the software and drivers.