OK, I think I see what is happening. If I open PicoScope 6 without a device connected (just the application) and then open up a *.psdata file created from when I had a physical scope connected, the displayed waveform is "corrupted". If I physically connect a device to PicoScope (even if it is a Data...

I'm still having a problem with the saved file. I have the scope atatched to a laptop and save the file as a psdata. The scope display looks fine, but when I view the psdata file on another machine running picoscope what I see is the trigger marker at the correct point but the channel trace does not...

I have a Picoscope tied into a 3206MSO using both channels. It was set to trigger on Chan B and during repeat trigger operation both traces were (correctly) displayed on PIcoscope. I then saved the data (as psdata) but when I bought back the saved file Chan A only displayed a very small portion of t...

I guess rather than changing the exiting driver (which may break the one that works) I would adocate developing another driver. You can then allow a means for a user to install any particular driver based on their application. There aren't that many usb wireless hubs out there and this would give us...

Unfortunatly I needed to return the loaner scope. I did however get it to work flawlessly with an IO Gear GUWIP204 wireless hub. Exactly the same setup, just different USB hub. Regarding the Silex device, it still failed when I had the Silex interface using the wired port or the wireless port. It wo...

I have an application where I want to make your scope (a loaner right now) very portable by connecting it to a USB wireless device server from Silex (SX-DS-3000WAN). When I connect the scope to the USB server Windows (64-bit) Device Manager identifies the scope correctly as a PicoScope 3000 series P...