Hi John,

The PicoScope 6 is running alone, no other application is running at the time I observe this problem.

Hi MarkB, How about we put it this way: - the trigger threshold level, which displayed at the bottom left of the screen, should always match the vertical scale of the selected trigger source channel. I understand that the PicoScope 6 allow user to define their custom probe with custom unit, mx+c sca...

I am using the PicoScope 6.0.15 with my PicoScope 5204. I notice that when I let the software run for a long repiod, says overnight, the screen update rate reduce significantly to about 2~3 frame/sec. I've checked the Preference > Power Management > Capture Rate is set to [unlimited]. When I close t...

Hi MarkB,

OK, I understand now. But from user point of view, is kind of mis-leading. Will this "problem" be alligned in future for PicoScope 6 release?

Hi MarkB, Thank you for your reply. I tried with PicoScope 5.20.1 (with PicoScope 3204) and here is the screen shot. When I set the probe to x10, & place the "Trigger diamond" to 800mV level, the botton screen shows 800mV (scaled). However, the vertical range at the top of the screen says +/-200mV (...

Just updated to 6.0.15, same problem exist.

I am using the PicoScope 6.0.13 together with PicoScope 5204. I am using the supplied 250MHz passive prove & I set the attenuation to x10. At the same time, I also set the "Probe Setting" to x10, so I get exactly what I input into the probe tip. I then set the trigger to "Rising Edge Trigger". I do ...