I use mostly AD2 for test equipment automation but have looked into the ADP series as well.
Do you know about the Embedded Linux Mode in the ADP3450 and ADP3250? Yes, looks very intriguing.
Have you used it? No
If NO:
What is the reason for not using it?
My uses need a user interface, typically a touch screen. Mostly it ends up being a tablet PC or a Raspberry PI derivative, and if so I already have an operating system.
Do you know about network connectivity (Ethernet) for the ADP3450 and ADP3250? YES
Have you used it? NO
If NO:
What is the reason for not using it? Using the less expensive AD2 instead, which doesn't have this feature. If I had a need for the higher performance features of the ADP series I would certainly use the Ethernet as I can with other power supplies and so on.
Do you know about WaveForms SDK? YES
Have you used it? YES
If YES:
Please describe the application for which you used WaveForms SDK. Two board test systems so far. Using the ADC inputs, GPIO inputs and outputs, waveform generator. I used the Python version communicating to a Node-red GUI front end as a daemon. Timing measurements and simulated IO.
What was your overall experience with WaveForms SDK? Once you get it working, it is very stable and effective. The feature set is very good, you can do just about anything that can be done with larger systems once you figure out the quirks.
What would you improve? Documentation is really hard to read. In most cases it is necessary to actually use the Waveforms app to do a parallel task, figure out which settings are reflected in which calls to the API, and then code it in the API. I agree with Reddish about the ctypes implementation, it is extremely non-Pythonic though it does work.
It would really help if there were some way to translate a Waveforms setup file to SDK calls that could then be copy-pasted into Python etc. The scripting language in Javascript is not related to the SDK at all, so you can't just get a script working and then translate it to SDK calls. Leaves you poring over the documentation trying to figure out what the cryptic function names really mean. Or trying to edit an example that almost does what you want but leaves out an important feature. Lots of cut-and-try.
What sampling rate and analog bandwidth do you typically need for your current and future measurements? 20 MHz is fine for what I am doing.
What features or improvements would you like to see in future products? Really implement USB C, not just USB 2 in a USB C cable. My cheap devices don't have USB 2 slots anymore. Not necessarily taking advantage of the higher power capabilities, as most of the USB C slots in the cheaper devices don't correctly implement the power features. Better winky light that actually shows connection state. (Dreaming:) Add Segger device programming code to the digital profiles. Make a unit in the ADP series with a touch-screen and Linux.