I am using a PicoLog 1012 with PicoLog R 5.20.9.
With a Sample interval of 5 minutes, as many samples as possible & 288 samples this should be a total period of 24 hours, this run actually completes in 22 Hrs 54 minutes. A sample interval of 1 second, as many samples as possible & 3600 samples completes in 58 mins 25 secs. A sample interval of 1 second, single sample & 3600 samples completed in 1 Hr 6 mins.
Can you throw any light on where the timing innacuracy could be comming from & how it can be improved.
Hello,
I've got a PicoLog-1216 and I'm writing a Visual Basic .NET software to control it. I can achieve 1us sampling rate using one single channel, but I've noticed that it is impossible to capture samples in a time-windows less than 32us. Could somebody tell me why, please?
I'm working in block mode and I'm using Pico.Drivers.dll functions.
Under here there is the section with which I get the samples. I have to use Thread.Sleep because the function PL1000.Ready() doesn't work.... (any suggestion?)
I've tested the code more accurately and I've found that the time I wait between the Run command and the GetValues one became too short if I use a window <32us. In this case Thread.Sleep command put the thread to sleep for 32ms that maybe is too little. It is sufficient increase Thread.Sleep time.
However now the problem is Ready command that doesn't work. Without this function I can't wait the correct time needed for conversion. I have to wait always a bigger time. Could you help me to use Ready command?
Under here the code that wait for conversion but that doesn't work. It use always Pico.Drivers.dll functions.
The unit is not going to work properly if you are not calling the pl1000ready function as this function polls the driver and determines when the data has been collected. If the function is not working, there must be an incorrect value getting past somewhere along the way. Attached is a quick example that I made in VB.NET...