attila

Hi @Leo_W Controlling the devices from separate threads should somewhat improve the performance but if these are connected to the same root hub the improvement may be little. https://docs.microsoft.com/en-us/dotnet/standard/threading/using-threads-and-threading

Hi @rim This seems to be a bug in the underlying libraries, Qt5.12, when 3D plots are above each other. It is solved in Qt5.15 and this will be used in the next installer if all other things work correctly. Thank you for the observation.

Hi @Virus That was a PRG18BB470MB1RB, similar to R145 but on AWG2 output: https://digilent.com/reference/test-and-measurement/analog-discovery/reference-manual#awg_out Is the digital part of the device working, USB controller... ?

Hi @Kirsan

Hi @Leo_W

Hi @AlanB Here you can find the new version in which there is no need for DataSet after Configure: Try with param stop. With run option, if the previously used application exited with shutdown the IO voltage level translators remain disabled. dwf.FDwfParamSet(DwfParamOnClose, c_int(1)) # 0 = run, 1 = stop, 2 = shutdown If the run option is needed, after open use the following to set the IO voltage and enable the translators: # set digital voltage between 1.2 and 3.3V dwf.FDwfAnalogIOChannelNodeSet(hdwf, c_int(0), c_int(0), c_double(3.3)) dwf.FDwfAnalogIOConfigure(hdwf, c_int(0)) The Digital Discovery play output captured with Analog Discovery:

Hi @Leo_W I just notice the Eclypse support is not enabled the WF software but it will be in the tomorrow version 3.18.50

Hi @Stephen Creswell Your use case is acceptable and will not violate the license agreement. Here is the newer eula license.txt that is/will be included in newer sw releases. PS: In the new license agreement 'The Software' specifically means Digilent's software component (Adept, WaveForms, etc) not the customer program.

Hi @AlanB The following is working for me, with internal loopback on DIO lines: DigitalDiscovery_PlayRecord.py

Hi @Stephen Creswell I've forwarded your question to the legal team. Hope to have a reply soon. Regarding the technical side, see the following post:

Hi @LJH Yes, the analog-in offset shifts the input range. The raw (16bit) ADC values are offset but the processed voltage samples are compensated for this to return the real input voltage.

Hi @Paul Rankin Triggering on multiple channels is only supported for digital IOs, in Logic Analyzer and in Oscilloscope interface using cross-trigger or after adding digital channels.

Hi @Stephen Creswell The restrictions in the agreement are only to prohibit the use of free Digilent software with cloned hardware. There is no restriction for your application to be used without Digilent product or other products, only the Digilent provided software (application, libraries...) should be used together with Digilent hardware.

Hi @Leo_W The DCFG_07_01_01.bin ! file should be programmed to the QSPI or copied to the SD card. The PL will be programmed only on software connection, so the PLGOOD will not light up on PS boot.

Hi @Bnm Which WaveForms version are you using? I've just tested the AD2 calibration with WF v4.18.1 and v4.18.49 bot are working fine. Use the links to calibrate it step by step ...

Hi @abia Use Ctrl+Space in Script tool or see the toolbar:

Hi @LJH See the following: adp3450.py I've added trigger for analog-in, changed analog-out to custom mode since the number of samples fits in the buffer, changed the rate and run length

Hi @towen This seems to be an unique (hub or driver) bug in earlier versions of RPIs since it is working fine with other SBC and computers. Reducing the transfer lengths and packing reduces the IN transfer oddness on RPI.

Hi @towen See the WF SDK: This API mostly handles raw data and processing (like measurements) need to be done in custom app/script. The API provides some functions for Network-Impedance Analysis and Spectrum/FFT processing.

Hi @AlanB Until this bug is solved use the following workaround, call DataSet twice, before and after Configure. FDwfDigitalOutPlayDataSet FDwfDigitalOutConfigure FDwfDigitalOutPlayDataSet

Hi @TheStumbler Interpretation of CANFD it is not yet supported but you can probably use the existing CAN interpreter/protocol to see the raw data.

Hi @Tiffany If you are looking for the AD2 AWG output impedance, this is zero ohms: https://digilent.com/reference/test-and-measurement/analog-discovery-2/hardware-design-guide#awg_out

Hi @SHall Probably some underlying OpenGL drivers are missing or not compatible with the 3D library.

Hi @Alicia865 1. This is what the above script does. 2. No, the csv files appear immediately when the script calls the export function. 3. When pressing the export menu or calling the function the current data is save, what you see is what you get. You could write a script to append data to file, see the Help tab/ Script/ File functions There are various export sources, the "Impedance Analyzer" contains all the opened views and traces. A constant frequency can also be used, like here 10s average and 60 steps will take about 10minutes, if this is what you are looking for.

Hi @Jklaus80211 In Wavegen you have the Basic mode with slider. In Scope and other interfaces the axis-scale can be used just like a slider... dragged with mouse, keyboard arrow keys, mouse wheel used, w/o Ctrl/Shift key for speed and Alt for swapping offset/range adjustment. The entry fields (combo-boxes) can be adjusted with mouse wheel. In newer beta version Ctrl/Shift key can be used for faster/slower adjustment speed.