The driver has now been fixed and will be released in SDK 10.4.2.2 shortly. The previous driver I posted was produced 1 hour before the bug was fixed so when looking at dates it seemed correct.
If you ensure that the scope software is running in streaming mode, with a timebase of 100ms/div or slower as set in Tools->Preferences->Sampling->CollectionTime, then set a single or repeat trigger with a threshold outside of your signal range, and a pre-trigger delay of 95%, and you should find th...
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.
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
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.
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 ...