attila

Hi @alex_alk It will be improved/fixed in the next version. Thank you for the observation.

Hi @MNSKev For the ADP5250 to be supported by LabVIEW/VirtualBench VIs the following DLL(s) needs to be replaced in Windows/System32 nilciuserapi.zip If you are using 64bit Windows and a 64bit app (like the File Explorer): - the nilciuserapi.dll from directory x64 should be copied to the Windows/System32 in order the 64bit apps to use it - the nilciuserapi.dll from directory x86 should be copied to the Windows/SysWOW64 in order the 32bit apps to use it For 32bit Windows the nilciuserapi.dll from directory x86 should be copied to the Windows/System32. These DLLs should be included in a newer version of VirtualBench installer (like v20) but I'm not sure if this will happen. I could include it in the WaveForms installer but it wouldn't be nice to overwrite files belonging to other kits.

Hi @R Hari Chandana It should be there.

Hi @Sangkyu Choi You could use 5VDC auxiliary supply for the device.

Hi @AbbyM It depends on how many samples were collected since the last call. Normally the maximum is the device buffer size but with ADP3X50's DDRam buffering it can be up to 4Mi chunk.

Hi @Hobs See the DigitalIO.py example on how to read the DIOs, FDwfDigitalIOStatus FDwfDigitalIOInputStatus You could also cross-trigger the instruments, like the analog-out, in, digital-out on digital-in trigger.

Hi @AbbyM See the Help and reference page:

Hi @alexconway I'm glad to hear that. Thank you for the update.

Hi @AbbyM The prints in your script can slow down the process/loop significantly causing device fifo overflow.

Hi @arnavguptagenerac Those measurements are performed in the WF application and are not available if the API only from the app's Script tool. For periodic signals FFT is a preferable method, see: AnalogIn_Frequency.py

Hi @R Hari Chandana It should be there if you install the newer sw version: dwfconstants.py See the AnalogIn_FFT.py AnalogIn_Spectrum.py examples

Hi @AbbyM Please take a look again on the provided WF SDK examples. test_adpro.cpp: the FDwfAnalogInStatus FDwfAnalogInStatusRecord should be outside of channel loop, read up to cAvailable samples in FDwfAnalogInStatusData16

Hi @AbbyM 2. The tested rate are from the device to the host RAM. The further operations, data processing, target storage (SSD, HDD, eMMC, USBdrive...) may slow down the process.

Hi @R Hari Chandana The DwfWindowRectangular should be in newer WF SDK/ samples/ py/ dwfconstants.py Have verified this ? Are you using this in the project ?

Hi @AbbyM 1. For better ethernet performance use a local switch or direct connection. With AD2 USB I can get 1-2MSps, this device always records at 2 channels. With ADP3X50 the earlier mentioned DDRam buffered recording limits (128MSps@125MHz/1ch...) and for longer or through linux mode 2-4MSps for 1 channel, this device will record on the enabled 1,2,4 channels. The sustainable streaming rate depends on the computer, available usb bandwidth, controller performance, cpu... 2. Yes, see the WF app Help The instruments (Scope, Wavegen...) are implemented in the Zynq Programmable Logic. The standard firmware or embedded Linux runs in the Zynq Processing System. The PL and PS communicates through AXI.

Hi @iitm04 Are you using the following as it is in the AnalogImpedance_Analyzer example ? # this option will enable dynamic adjustment of analog out settings like: frequency, amplitude... dwf.FDwfDeviceAutoConfigureSet(hdwf, c_int(3)) Otherwise, when calling the FDwfAnalogImpedanceFrequencySet the AWG will be stopped and configure/start will be required to restart it. dwf.FDwfAnalogImpedanceConfigure(hdwf, c_int(1)) Actually the FDwfAnalogImpedanceFrequencySet applies the AWG frequency and restarts the Scope, so the configuration is optional. dwf.FDwfAnalogImpedanceFrequencySet(hdwf, c_double(hz)) # frequency in Hertz # if settle time is required for the DUT, wait and restart the acquisition # time.sleep(0.01) # dwf.FDwfAnalogInConfigure(hdwf, c_int(1), c_int(1))

Hi @AbbyM 1. The USB 2.0 streaming can reach about 1-2MSps. 2. The recording with ADP3X50 in standard boot mode is backed with DDRam buffering, up to 128MS @ 125MHz / 1 channel 3. The embedded Linux in ADP3X50 has highspeed connection to the PL (T&M), depending on data processing performed this should also offer high transfer rate. See:

Hi @AbbyM The limited file system support is valid for the uboot, for boot and linux image flashing. The linux supports various file systems.

Hi @Ricky Sure, pic 1 With the 6th device configuration the supplies can also be used as slow AWGs, pic 2

Hi @reddish On newer devices with more ram 16bit samples are stored but for AD1,2 to maximize buffer depths 14bit is used.

Hi @iitm04 For faster operation after FDwfAnalogImpedanceStatus/done a new capture is immediately started. As a consequence if the frequency is changed the new capture will be invalid. Call configure again or ignore the following status. See the WF SDK/ samples/ py/ AnalogImpedance_Analyzer.py example " dwf.FDwfAnalogImpedanceStatus(hdwf, None) # ignore last capture since we changed the frequency "

Hi @reddish I thought this 0.012% error is a limitation of the HDL implementation, but it turned out it was an imperfection in the 15 year old C code. The averaging parameters were calculated for 16bits instead of 14. It will be fixed in the next sw version. Thank you for the observation.

Hi @tdeball @reddish The ADP3x50 stores 16bit samples. The offset with low range (2Vpk2pk) should be -1V..+1V

Hi @reddish This is the average calculation error, 1.22/10000, which I think it is acceptable for an oscilloscope.

Hi @Adam1973 I don't see obvious problem in your code. What error do you get exactly? Minor observations: use len(Hex_List) instead 8, c_uint(HEX_VAL) specially if you use 32bit values.