I recently acquired your company’s PCSU1000 oscilloscope (through Jameco) and I am currently putting it through the paces. So far my impression is quite favorable. There are however a few details in the hardware and the included scope/spectrum analyzer software that I believe could/should be improved with little effort:
Software:
(1) I am missing a way to average over several waveforms in the oscilloscope display (interestingly enough, the spectrum analyzer mode does offer averaging). The scope’s intrinsic noise is remarkably low, but nevertheless there are many situations where one could benefit from removal of random noise.
(2) it would be helpful to have a “store to reference” function that stores the current waveform (it should be possible to turn the reference traces on and off like the CH1 and CH2 waveforms). That would simplify the search for small changes since they would be easily visible as mismatches between stored reference waveform and current waveform.
(3) in addition to existing measurements, RMS noise, peak-to-peak noise, and RMS jitter and peak-to-peak jitter would be nice to have.
(4) it would be great to have the option of manually setting the reference levels (high/mid/low) used in the measurement (right now 10%/50%/90% are hardcoded). At least let the user switch between 10%/90% and 20%/80% for the rise time thresholds.
(5) sometimes variation of the amount of post-trigger would help (at the moment it seems hard-coded to about 1/3 of the waveform record). E.g. allow pre-trigger of 10%/50%/90%.
As for the hardware, two things were less than optimal:
(1) The absolute levels are sometimes significantly off - e.g. probing ground the scope showed up to -0.4V in the 1V/div range. This was after scope calibration, and I even recalibrated to be on the safe side. (and yes, the probe ground lead WAS attached to another nearby system ground point). Could this be an issue with scope ground drift? (the system under test did not have direct connection to the computer ground except through the scope ground lead).
(2) Probing a fast-rising edge (<2ns) from a microcontroller (standard 5V CMOS output) showed close to 50% overshoot, which is not visible when I compare it with the waveform of a high-performance scope (Tektronix TDS 692, 3 GHz / 10GS/s, with 4 GHz probes). The size of the overshoot is present even in oversampling mode and cannot be explained by interpolation artifacts (the Gibbs phenomenon would be limited to <17%). I used the included probes in 10x mode, and they were compensated prior to the measurement. Is this a known issue of the probes?
Is there a way to get automatically informed about new releases of the software? (the About screen says it’s version 1.0 so I assume there will be updates).
Thanks and keep up the good work
Wolfgang