Analog Discovery Pro ADP2230

[Dan_Hay]

I was curious in purchasing this product. If you had to quantify it, how fast is this able to take a trigger for acquisition and then save the collected data to a file, and then take another triggered response? I currently have the analog discovery 2 which seems to need a half second delay in between each trigger in order to not miss any. 

[artvvb]

Moved to another section of the forum where this might get more visibility.

Gut feel, time between repeated acquisitions (if fully offloading over USB before arming another one) should be similar. Unlike AD2, the ADP2230 has rapid triggers for buffering subsequent acquisitions in DDR, where the blind time is only a couple microseconds (1-2 us). Data still needs to be offloaded over USB eventually, so you're typically limited by the internal buffer for the number of acquisitions that can be taken (it should be split evenly).

Thanks,

Arthur

[Dan_Hay]

Awesome, thank you for getting back to me and moving this in a better location. From what I gather, is that if I continue doing the implementation I have currently it will exhibit the same time restrictions; however, if I store it in the internal buffer, it can run 1-2 us. How large is this internal buffer? Can it hold a lot of data? Can I determine what data gets stored in the buffer, like sliced down data or max points from an acquisition window? 

 

I am looking to speed up a laser process that implements data acquisition, hopefully faster than the current half second per pulse collection. I'm open to advice on how to better implement this procedure if you know of a way to do so. The current approach is to use the data logger in the waveforms application, grab the data from channel 1 after a trigger occurs from channel 2, slice the data down, sample the max point, and then append that point to a created csv file. Thank you for anything that you can help with it. It is much appreciated

[artvvb]

@attila may have some more accurate information or other ideas on this.

Some of these questions will be answered by the spec sheet and reference manual, which you can find here: Analog Discovery Pro (ADP2230) - Digilent Reference. In general, the buffer will store 128 MS per channel of raw data (plus some extra stuff like some extra samples to calculate noise) from however many acquisitions are specified, down to something like 10 samples per acquisition. I believe that all measurements, like finding the maximum value in an acquisition, are done in host software rather than on device, so pre-calculating that kind of thing can't currently be used to help further compress.

When you say you're currently using the data logger, out of curiosity, do you mean you're using the "Logger" top-level instrument, or the "Logging" feature inside of the Scope instrument? The latter can do scripted measurements and might also help improve on your existing system, if you're not using it already.

[attila]

Hi @Dan_Hay

The scope channel of AD1,2,3,ADP2230,ADP3x50 can be configured to capture min/max values.
If you want continuous capture or control loop, you can use scan or record capture.

If you need separate captures AD1,2,3 can do about 100 waveforms/sec, depending on trigger and capture length.
The ADP2230, ADP3X50 provides memory segmentation with ~1us latency between captures.

[Dan_Hay]

So the buffer size for this equipment is essentially the Hi @attila, I appreciate the help. When I was testing the scan and record feature it would trigger once and then just run continously. I would need to do separate triggers for max point saving. Is that possible for the scan and record feature that I looked over? I am running this alongside a laser at an operating environment of 500 kHz. That rate would be my end goal but if I can do data collection faster than what I am currently doing, that would be awesome. 

[attila]

Hi @Dan_Hay

The latest version lets you capture min/max values FDwfAnalogInChannelFilterSet filterMinMax with trigger sampling. See FDwfAnalogInSamplingSourceSet in AnalogIn_SamplingClock.py which you can also use with acqmodeRecord AnalogIn_Record.py for continuous capture. There is one min/max pair saved for two consecutive events, so you could select FDwfAnalogInSamplingSlopeSet DwfTriggerSlopeEither

[Dan_Hay]

Is that min/max feature only available in the sdk? I have done everything in the provided software. If it would be better to switch to the python variant, I will. How fast can I collect and save data from the daq using that approach? 

[attila]

Hi @Dan_Hay

See the earlier mentioned examples and functions.
You could probably get about 50M 100M samples/s, 200-300MB/s / 16bit sample / 2 samples (min-max).
If considerable software processing is performed on the data, use separate thread/process for data transfer function call.

On 9/2/2024 at 4:44 PM, attila said:

The latest version lets you capture min/max values FDwfAnalogInChannelFilterSet filterMinMax with trigger sampling. See FDwfAnalogInSamplingSourceSet in AnalogIn_SamplingClock.py which you can also use with acqmodeRecord AnalogIn_Record.py for continuous capture. There is one min/max pair saved for two consecutive events, so you could select FDwfAnalogInSamplingSlopeSet DwfTriggerSlopeEither

 

[Dan_Hay]

Awesome, thank you @attila. I'll let you know if I have any follow up questions after taking this approach. I currently do not have any processing being done on the data right after collecting it. If I do, it happens post processing so I should get close to those rates you mentioned.