oltechie

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.

Don't know the answers to your questions, but that sure is a cool way to set up the AD2! I am hoping the USB C connection will deal with the flaky USB issues of the AD2. With the usual USB C docking station style hubs available these days the AD2 has a very great tendency to not have enough power to operate or suddenly disconnect. And the small cheap Windows tablets in my test stands no longer have USB2 or 3 slots at all! The only way I am able to use one with USB C is to get an ancient USB2 powered hub and use very short cables. Oddly, using an external power supply does not seem to help. If someone from Digilent checks in, here are my AD3 questions: 1. JTAG or SWD protocol? Does that mean we can program chips? Probably not, but that would make the AD3 my dream machine. I have to drop $500 on every test stand for hardware that is really just a serial port to SWD translator to program the chip. 2. Will it work with the PI finally? All the Raspberry PI derivatives I have tried do not seem to be able to find the AD2 device or keep it connected. Neither the USB3 or USB2 slots work. Believe me, I have tried all the tricks. 3. More informative winky light that you can actually see? The AD2 LED starts blinking as soon as you connect, and then goes on blinking until you power off. Not helpful when you are fighting disconnection issues from flaky hubs and cables. The cover is no longer partly translucent but there is something that could be an LED next to the USB C inlet. Hope it is not just power. Guess I'll find out when my units arrive.

Tried an old-style USB 2 powered hub, seems to be working again. It needs to be the kind of hub that has an external power supply and no USB-C connectors.

Similar problem here, only it was working until yesterday. I have tried: External power supply, powered hubs of various kinds, reloading software and drivers, many different combinations of all the above. All with fully patched Windows 11 22H2. The only way it works as of today is directly plugged into a tower with a very short cable. Or a USB C hub with the power-through feature by j5Create. Unfortunately the one hub I have that works also causes the tablet to change display orientation, making it unusable. I tried two Analog Discovery 2 devices, both of which used to work. Both now fail with the exact same hardware as before. The issue is not the drivers, there is a new error in Device Manager I've never seen before saying that the USB device "Failed to reset". Windows can't even retrieve the VID and PID so it doesn't load the drivers at all. Probably an old powered hub might work, but the new ones with USB-C connectors somehow send the wrong power configuration information to the FTDI chip, making it fail to start up properly. At least that's my theory. Either that or the initial power surge on starting up drops the 5V supply enough that it can't operate properly. My USB meter says the voltage is 5.17V and the current is 260 mA when it does operate properly, so the newer "Charger + Data" hubs should have no problems. But they do! If anybody knows how to get around this issue, please chime in!