Hi

has this bug been dealt with yet? I still seem to have the same problem in v6.10.11.15. It would be nice to work directly rather than having to separately record and then stitch back together the data.

Bob

Ah, I had not appreciated that channel hide had that power. I must save data before looking at it to avoid that problem / benefit. Thanks for the info.

The file is too large to attach so I will send it. I presume when you say "The workaround is to load in only channel A into MATLAB, and then export only channel B to .mat file." you are not referring to using the Picosoft 'save as' function. Our process is having recorded the data and saved it as a ...

Hi just came across this bug from another direction. I normally save my 2 channels worth of data to psdata file format and subsequently transform it to a mat file format for onward processing. Usually my 2 channels of data is collected using the single trigger mode, so I collect one full buffer memo...

Having also found this phenomena and identified a work around, one additional minor point still irritates me. The Properties pane shows summary data in use including a value for the number of samples per waveform. Tests with a 4424 and a 4224 and several software versions (6.6 & 6.7) show that the a...

many thanks for the advice which worked!

I am running a 32bit machine using Windows XP plus SP3. I ticked the box but got no option to select a second device. It just went straight on to load the software. I uninstalled 5.20.8 and tried installing 5.21.2 but all that happened was the installed ran through to some point and then rolled back...

I am trying to run both Picoscope 6 (with my 4424) and Picoscope v5.20.8 (with my 200) on a lap top, though (not yet) at the same time. I am getting a curious message that Picoscope v5.20.8 can't load because "The file adc1032.dll failed to load correctly". But Picolog v5.20.8 runs OK in this set up...

I used to be able to directly save the whole screen into a jpg with v6_6_18. With v6_6_28, I now have to paste it into imaging software which is a bit of a pain. I want to save the whole screen because it also records settings which I can then easily share first impressions with my colleagues and gi...

Hmmm, the number of bits is not always 256 this is because in each of the ranges there is calibration and offset information. How curious, though I am unclear as to how this explains the 4.15mV / 3.9mV increment pattern. :? Or are these values indicative of the inherent error span in the accuracy o...

attached as BPC 4 59. Please note this seems to be standard behaviour and also occurs when using both channels, see 100817 BPC 6 5.

My set up is a Pico ADC 200/100 and a PP/USB converter using Pico Log V5.20.3 software. We have just realised that the step interval between ordered data points does not equate to that predicted. For example, using a +/-500mV range with 8 bits, I expect to see a 1000/256 = 3.9mV step when the data s...

sorry wrong sample, the previous was set at 10ns which gave 20ns time steps as you predicted. Attached is one set at 164ns but the recording shows 327ns.

ziko wrote:Hi are you writing your own software or are you using PicoLog or PicoScope?

Kind regards

Picolog. see attached for example

Thanks for the info. I did mean 10us and not ns. I got this curious doubling in timebase for 1280ns and 640ns as well. Checking with AC mains noise, the clock is not a factor of two out. A separate check on a pulse shows that both channels are sampling at the same time, even at 640ns timebase settin...