Test and Measurement Forum

Picoscope 6402B (hardware?) problem for many long captures

Post any questions you may have about our current range of oscilloscopes

Picoscope 6402B (hardware?) problem for many long captures

Postby david_oswald » Thu Jan 29, 2015 11:23 am

Hi,

I'm using a Picoscope 6402B (FW 1.1.5.0 / 1.1.25.0, HW 1 1, Driver 1.4.4.24) w/ the (most recent) SDK on Win7 to aquire many (relatively) long captures at one of the higher sample rates (1.25 GSPS). The scope is triggered from channel C, acquires channels A & B.

After a (somewhat random) number of acquisitions (hundreds to thousands, depending on the exact parameters) , the scope is not triggered (although the signal is fine and there should be at least an auto-trigger in any case) and it is also impossible to stop and re-arm it (any subsequent RunBlock fails). I checked all my code as I suspected the problem there initially, however, at some point I swapped the unit against a second, identical scope (even bought in the same order).

With the second scope, everything is working as expected, no problems... Does this indicate a HW problem or is there a newer firmware that solve the issue? Is this a known problem?

Thanks,

David
david_oswald
Newbie
 
Posts: 0
Joined: Thu Jan 29, 2015 11:13 am

Re: Picoscope 6402B (hardware?) problem for many long captur

Postby Hitesh » Fri Jan 30, 2015 4:28 pm

Hi David,

Which programming language are you using?

Are there any status codes other than PICO_OK or PICO_BUSY returned from polling ps6000IsReady or the block callback function?

When the next ps6000RunBlock function call is made is there a status code other than PICO_OK returned?

Regards,
Hitesh

Technical Specialist
Pico Technology
Hitesh
Site Admin
Site Admin
 
Posts: 2058
Joined: Tue May 31, 2011 3:43 pm
Location: St. Neots, Cambridgeshire


Return to USB PC Oscilloscopes

Who is online

Users browsing this forum: No registered users and 0 guests