Hi, is there already a zero calibration for the probes in R6.
My 3205 always displayed -2,5mv. In R5 I can zero it, but did not find this option in R6.
Changing the offset will also change the Y values, that is no calibration. When I short the probe the reading is still -2.5mV, i need to use that value as zero.
Also in the FFT screen there is a peak in bin 0 (DC value) when the input is not calibrated. Measuring small signals "At Peak" will select the bin 0 (0 Hz) (Maybe that bin need to be skip in selecting the Peak bin, or a new range between ruler 1 and 2).
You are correct about the differences in the offset effect between PS5 and PS6, and though it is intended to eventually incorporate the majority of PS5 features into PS6, it is not possible for me to define the order of implementation or timescales involved.
Ok, I understand that not every thing is present in the new release now.
I'm new on this list but are you maintaining a problem and change list for this new software release. Can I keep on posting my request for the software in this list?
The new software PS6 is in my point of view so much better than the old one, I hope there will be many new releases with new features in it.
I still have some problem's with the zero calibration of my 3205 scoop. The unit read a DC average of -2.2mV with a closed probe.
There is still no correction in the R6 software (in R5 it is there) and is it very enoiing when using the spectrum display. There is always a strong signal at 0Hz (bin 0) of -18dBV.
Is there a possibility to add the zero correction or to calibrate the hardware?
Hi i think you refer to what was in PicoScope 5 as offset null. This feature is something that we are thinking of implementing and may be on our to do list.
Don't get me wrong, I do love v.6 - but missing _basic features_ like probe nulling makes me really confused...
How can you NOT implement such a feature (without having to rescale axis or ranges showing strange values)??
I have two picoscopes and they both need probe nulling before use...
I mean - how hard can it be to implement? It's been years now and still nothing?
It's been a part of previous versions like forever...
I'm not ungreatful, I really do appreciate your hard work.
But some software should never even be realeased without fulfilling even the most basic features...
At the risk of sounding vague, we will actually be implementing this in 2011. We have a list of features to add and we are working our way through them. In the meantime the custom probe as sv2dgi pointed or using maths channels are the alternatives.
I just got two Picoscope 3205 and this was going to be my first question. So bad to read that someone asked the same thing three (3) years ago! I cannot wait to get to 2011.