I'm running Windows 7 x64 with Labview x86
I recently install new Pico driver software PicoScope6_r6_10_6
PS4000sdk_r10_5_1_1
ps4000.dll version 1.2.4.12 (also tested on 1.0...)
Picoscope 4262
When I press either 'Run' or 'Stop' the VI did not respond and I have to force stop the VI.
Upon closer inspection, the PicoScope4000GetRapidBlock.vi is still executing the loop containing 'ps4000IsReady.vi'; however, the pico4262 device has already disconnected (Red LED lights up). Thus, the VI stalled because it is still waiting for the signal from the device indicating whether the capture is completed.
If I change the #segments to '1', the VI works fine. If #segments is larger than 1, i.e. 2 or 3+, the program stalled
Does anyone have any idea why?
Attachments
Last edited by nhanlm0601 on Thu Dec 04, 2014 2:04 pm, edited 1 time in total.
Details of the Labview probing:
In RunBlock Vi, there is a loop for PS4000IsReady.vi and the loop keeps repeating while the picoscope does not respond to stop the loop.
I made a mistake, the VI that is stalled is
PicoScope4000GetRapidBlock.vi
Within that VI, the loop around 'ps4000IsReady' does not stop as the picoscope does not respond back to the VI saying it is ready, the value is '0' all the time. The LED indicator on the picoscope is turned ON after the first loop, where it is supposed not to when it is in 'collecting' mode?
It works fine when the #segments is 1, when I change #segments to 2 or higher.
The 'capture complete' Indicator does not turn on, and it keeps repeating the loop 'PS4000IsReady.vi'. I left the device for several minutes and nothing happened (picture), the 'Capture Complete' is OFF but the Red LED on the pico device is ON.