That would be within the working parameters of the scope, and is the gaussian noise inherent in the signal and the scope. You can clean up the signal by filtering, or applying resolution enhancement, both selectable from the channel options button in the Picoscope software.

We have identified an issue with the driver, which the development team have fixed, so please try the attached version.

Unzip the file and drop it into C:\Program Files\Pico Technology\PicoScope6

Please go to http://www.picotech.com/software.html and select ADC-42 at Step 1 and you will be presented with appropriate software at Step 2.

Disable it by setting the IP address to 0, although there is no issue with leaving it in and just unplugging the device. What IP address and port have you selected ? Can you ping the CM3 from a command prompt window on your computer ? Do you have a firewall enabled on your PC blocking the telnet req...

This is not currently on the development plan although we continue to raise the question with the development team.

Exactly how are you calculating the sample interval of the data that is returned to your application by the scope ?

Have you run the EthernetSettings program to set up the IP address of the CM3 ?

You will find it in the SDK or installed here "C:\Program Files\Pico Technology\Pico Full"

Yes, the conversion time per channel is 720 msecs, and for that reason the CM3 is not designed for looking at spikes. If spikes are of interest then you would need to use the current clamps with one of our oscilloscopes.

The 2208 is one of the newer 2000 series units and requires the "a" version of the sdk, (including example vi's for block, rapidblock, and streaming), the file you mention is from the older one Please go to http://www.picotech.com/software.html and select PicoScope 2208 at Step 1 and the SDK at Step 2

As the input signal level is reduced the averaging time constant increases to maintain the accuracy of the measurements. It is the way the unit has been designed to operate.

The response time is asymptotic towards zero and if you are only measuring a few amps of current then you are only using a fraction of the full scale deflection of the CM3. From 80A, or higher, towards zero and back up will show a much more rapid response.

If you apply any signal does the display change at all ?

I have looked and can't find any emails, from your email address, on our system so please retry to support@picotech.com

Sorry for not replying. The developers have found a memory leak in the code related to the saving of multiple files and this has now been fixed although is not yet in a released version. This should be available soon once further testing has been completed.

The team have found an issue with trying to save a file when there is no data on the display, and this will be included in a future release. Your macro creates this issue so we believe it is the reason for your crash.

In simple terms you will need a potential divider to drop the voltage that you have down to a suitable level for the logging device you select.