PicoScope 7 Software
Available on Windows, Mac and Linux
Picolog out of range
Picolog out of range
I am currently running Picolog 6.2.8, when channels inputs are zero, it displays 'out of range' and a blank field is recorded in the table. It also did this in 6.2.7 but displayed correctly as zero in 6.2.5. Any ideas?
Re: Picolog out of range
Hi Paul,
Just had a support request on our Helpdesk with a similar question, so I will paste my answer here.
The issue is that, when the data being captured by the Logger goes out-of range of the Input Channel, It can’t be recorded as data (as a Manufacturer of Test & Measurement we are obligated to handle out-of-range data this way). Because the PicoLog 1000 Series Data Loggers have Single-Ended inputs, they will effectively go out-of-range if the data drops below 0 volts (and because the Loggers are calibrated to give you access to the maximum Range for maximum resolution of your data, this can happen on some models with noisy data that is supposed to be at 0 volts), So, there are missing samples of data, in both the Data Table and the Data Graph, at the instants in time when this happens and the Table and Graph have a Red Exclamation Mark to show that this was the case. When you have only a few samples that go out of Range, with a sample rate of 1kHz, it's difficult to see the out of Range data in the Graph, when it is just the noise in the signal that goes out-of-Range, as you need to zoom in many times to do it. So, I have created a file where, at a sample rate of 1kHz the waveform slowly goes out-of-Range for short time (but long enough to see without zooming in) near the end of the capture. you can download the file from here:
https://drive.google.com/file/d/1Gz56by ... sp=sharing
Fortunately, when this happens the data that is not out-of-range is still captured, so you can either just ignore the missing (i.e. corrupted) data, or you can avoid it by ensuring that you have a waveform source that either can’t go out-of-Range or, if it can, you need to take steps to condition the waveform so that it doesn’t, such as using resistors on the Terminal Board to offset (and scale, if necessary) the data. If you're interested, I will post a solution that you can use when I can block off a little time to do it.
Regards,
Gerry
Just had a support request on our Helpdesk with a similar question, so I will paste my answer here.
The issue is that, when the data being captured by the Logger goes out-of range of the Input Channel, It can’t be recorded as data (as a Manufacturer of Test & Measurement we are obligated to handle out-of-range data this way). Because the PicoLog 1000 Series Data Loggers have Single-Ended inputs, they will effectively go out-of-range if the data drops below 0 volts (and because the Loggers are calibrated to give you access to the maximum Range for maximum resolution of your data, this can happen on some models with noisy data that is supposed to be at 0 volts), So, there are missing samples of data, in both the Data Table and the Data Graph, at the instants in time when this happens and the Table and Graph have a Red Exclamation Mark to show that this was the case. When you have only a few samples that go out of Range, with a sample rate of 1kHz, it's difficult to see the out of Range data in the Graph, when it is just the noise in the signal that goes out-of-Range, as you need to zoom in many times to do it. So, I have created a file where, at a sample rate of 1kHz the waveform slowly goes out-of-Range for short time (but long enough to see without zooming in) near the end of the capture. you can download the file from here:
https://drive.google.com/file/d/1Gz56by ... sp=sharing
Fortunately, when this happens the data that is not out-of-range is still captured, so you can either just ignore the missing (i.e. corrupted) data, or you can avoid it by ensuring that you have a waveform source that either can’t go out-of-Range or, if it can, you need to take steps to condition the waveform so that it doesn’t, such as using resistors on the Terminal Board to offset (and scale, if necessary) the data. If you're interested, I will post a solution that you can use when I can block off a little time to do it.
Regards,
Gerry
Gerry
Technical Specialist
Technical Specialist