We've been having nothing but problems, since April, trying to run an older ADC11 with your USB/parallel port adapter. The ADC11 had operated fine for years on a parallel port.
I have removed and reinstalled and repaired Picoscope 5 more times than I care to remember, trying to fix this, on two, maybe three laptops. A Picoscope 2203 runs fine (using Picoscope 6) on any of them.
Some of the problems: (On one WXPSP2 machine) "Error: ADC11 not connected." (on another WXPSP2 machine) "The file ADC1132 failed to load correctly." Either of these result in "Waiting for ADC" when Picoscope 5 starts. We have not once (out of about 20 tries, since April) been able to capture a single-triggered event (a voltage spike and decay over 3 channels) whose capture had been routine using a direct parallel port connection. We have gotten one (maybe two) captures, of signals we don't recognize and that may be the far tail end of what we were trying to capture. Sometimes Picoscope 5.20.1 shows "running" but there are no traces whatsoever visible on the screen, when we know there are measurable signals applied to the terminals.
I'm wondering if this is the same problem on which Michael (Guru, Location: St Neots, Cambridgeshire) advised another poster to send back his old ADC212/100 to have it modified by Picotech so it would work with the new USB adapter. (Posted: Wed Sep 28, 2005 3:19 pm Post subject: Error - ADC 212)
Cart

