by andromodon » Fri Jan 09, 2009 8:12 pm
Hi. I would really like to buy a Picoscope, partially because of the great user interface available in the software, and I run an all-Linux shop.
Wine seems like a great way to gain access to the picoscope software without requiring duplicate development and support effort. PicoTech could write one piece of (possibly tweaked) code and allow it to be run on both platforms.
Earlier in this post it was mentioned that the Picoscope software does not currently work in Wine when the hardware is connected. Why is that? We're all Engineers here... What is the fundamental, low-level issue? I assume it has to do with communicating with the scope. If the linux drivers provide a /dev/ interface for the scope, can the Picoscope software include a way to interact with that /dev special file? The software could take a command-line option, for example "PicoScope.exe -d /dev/pico0", which would communicate that it is being run from within Wine and should use the Linux-driver interface. That would solve a lot of development effort as most of the key elements are already implemented. It could take less than a week of development time to write the mapping between linux driver commands and windows driver commands, and that would open up the PicoScope market to everyone from ultra-mobile-PC buyers to uber-geek Linux enthusiasts.
The current open-source oscilliscope interfaces I've seen are lacking in features and have archaic interfaces. If given access to the PicoScope software in Linux, I would buy two scopes off the bat and would advertise the scope to all of my colleagues. I would hate to be forced into buying a Bitscope because they fully support Linux.
I look forward to a reply from one of your engineers involved with the software development process.
Thank you very much.
Sincerely,
Andy Doucette
Electrical Design Engiener