I hope it's OK to ask that question: are there any open source drivers for 2000 series? I don't mind a limited functionality. Alternatively is there any available documentation that would help to create them?
You're unlikely to find any open source drivers for our data acquisition devices, as we don't divulge how to communicate with them over USB, and we don't release any essential information about the Firmware (and changes to it that are inevitably made). This is deliberate as the information is intellectual property and therefore proprietary.
However, you shouldn't need that information if what you had in mind was creating your own application to control and use our devices instead of our PicoScope 6 and PicoLog 6 software. The low-level stuff is not related to data acquisition applications (as it is the nuts and bolts of getting the hardware working with the low-level computer hardware).
What we do have is a Software Development Kit (see here: https://www.picotech.com/library/oscilloscopes/picoscope-software-development-kit-sdk) which allows you to (1) Create your own application using our drivers, (2) select from a number of popular development environments, and (3) use example code (see here: https://github.com/picotech) as a starting point (which provides basic setup, capture and control functions).
Thank you very much for detailed information! While I understand Picotech position I know that using proprietary drivers lead sooner or later to debugging problems, problems with software being accepted into some linux distribution repositories and compatibility problems after driver upgrade (back compatibility is rarely priority for proprieary stuff).
If you ever change your position I'll be happy to help.
P.S. I'll also send a PM as I'm not sure how much I can discuss here.
The lower level code is just as proprietary as the top level code (may be even more so) because, in order to understand how to control the PicoScope you need to understand exactly what is being communicated and why. This means that you need to understand the functionality of the hardware being controlled over the USB interface and, as I'm sure that you can appreciate, releasing complete functional explanations of Intellectual Property is not something that companies tend to do (as it also likely to give competitors a great gift).