Best practices for using a large number of scopes

Which product is right for your exact requirements
Post Reply
jthanpicoscope
User
User
Posts: 3
Joined: Wed May 13, 2020 4:01 pm

Best practices for using a large number of scopes

Post by jthanpicoscope »

Hi Folks,

I'm considering a problem where I have to monitor 64 channels, which I could do, in principle, using 8 PicoScope 4824. What could possibly go wrong? I've already used a 4 channel PicoScope to acquire from 4 channels, so why not scale up to 64?

Each channel could trigger an acquisition on all channels for a particular scope (using the "or" function in the trigger mode). It would be common for several scopes to trigger simultaneously, in which case we'd want the data from all the scopes that triggered.

Questions:

1) Is it POSSIBLE to hook 8 PicoScope 4824s to a single computer?
2) Is it ADVISABLE to hook 8 PicoScope 4824s to a single computer?
2) What is the BEST WAY hook 8 PicoScope 4824s to a single computer?
(e.g., using 2x USB 3.1 PCI-E cards, perhaps)

Since this is a pretty expensive idea, any advice in advance is welcome.

bennog
Advanced User
Advanced User
Posts: 208
Joined: Mon Nov 26, 2012 9:16 am
Location: Netherlands

Re: Best practices for using a large number of scopes

Post by bennog »

What is the sample speed you want.
e.g. 100 k samples / sec or 100 m samples / sec
What bit resolution do you want 8 bit or 12 bit.

This scope does not have an external trigger input so there is no way to trigger them all at the same time without sacrificing 1 of the 8 inputs for trigger.
Also USB3 power consumption would be a problem and bandwidth of the USB3 controller if you have high sample rates.

Benno

jthanpicoscope
User
User
Posts: 3
Joined: Wed May 13, 2020 4:01 pm

Re: Best practices for using a large number of scopes

Post by jthanpicoscope »

We could live with 8 bits. I expect we could get the trigger rate below 1000/second, on average (asynchronous bursts). In any case, we have control of the mean rate. Each scope would trigger itself independently from the others based on its own inputs (using the OR function on all channels).

It would be essential to have a high-resolution time stamp to combine correlated trigger events. (I seem to recall that PicoScope offers that, but I don't know if the different unit clocks would be synchronized. I wonder if we could synchronize them somehow.)

Not sure if this approach is viable!

Martyn
Site Admin
Site Admin
Posts: 4500
Joined: Fri Jun 10, 2011 8:15 am
Location: St. Neots

Re: Best practices for using a large number of scopes

Post by Martyn »

Would you want to use the PicoScope 6 software ? or would you be writing your own application to control all the devices ?
Martyn
Technical Support Manager

jthanpicoscope
User
User
Posts: 3
Joined: Wed May 13, 2020 4:01 pm

Re: Best practices for using a large number of scopes

Post by jthanpicoscope »

Sorry to miss your question and thanks for any help:

We would probably ultimately write our own software in LabVIEW although it would be nice to get started with the included software.

Thanks!

bennog
Advanced User
Advanced User
Posts: 208
Joined: Mon Nov 26, 2012 9:16 am
Location: Netherlands

Re: Best practices for using a large number of scopes

Post by bennog »

what differences in time do you want to measure, you said 1000 triggers / second but not the number of samples for each trigger.

For example if you want to measure time differences of 1us you need to sample at at least 0.2us intervals so you need then 5.000.000 samples / sec.

P.S. the 1000 triggers / second is this a continues proces or some short event ?

Benno

Post Reply