What version of the PicoScope6 software are you using ? Are you doing anything at the time or is it just free running a normal trace ?

You need to use the 20V range so inputRanges(range) becomes 20000 as you are using mV values

If you are not able to common the grounds then the 1216 would not be correct for this situation. If you are able to then attach multiple grounds to each ground socket.

We would need to see the complete configuration and signal characteristics to see if the settings for auto trigger values are correct, however as it is now working I would suggest to continue testing.

If you find any other issues just post back.

Our newer scopes are not supported under Picolog.

However using the alarms features and saving data when buffers are full it is possible to configure PicoScope 6 to log data over extended periods of time. Please check out the videos at http://www.picoscope.tv/general/using-alarms.html

That sounds like you are trying to install Picolog software.

The 4424 only works with PicoScope6 software so if you install and run this it should find the scope.

Can you try with the attached dll

We have added a function into the driver to match our newer scopes.
Zero return value indicates the device is disconnected

This command hasn't made it to the documentation yet.

I still have no timescales for this enhancement as we do not have the development resource to perform the work, even if it was externally funded. Sorry.

Is this what you mean
Swapping in the dll file is fine, and exactly what we would recommend.

Are the ground reference points for the sixteen voltages the same ?

We have tried this on the latest beta release and by removing the serial decode settings and then adding them back but setting a falling edge clock, MSB first, we are able to decode 01, 03, 05 as a repeating sequence.

Is this what you would expect for the 20120620-0004.psdata file on D2, SD0

collect_block_immediate is the correct function to use, and you have the correct number of samples and sample interval. However you need to wait for the data to be collected before trying to get the values from the driver, the code to do this is there but you have commented it out //Wait until unit ...

The point at which the signal will pass through the trigger value you have set will not necessarily match an exact sample taken by the scope. With sine and ramp waves the rate of change of the signal is not as great as with a square wave and so the value will be close to the threshold you set, with ...

You have commented out the line that sets the scope channel which needs to be before you call