attila

Hi @mnorth The trigger can't be set exactly to the right, to be the last sample. Due to the pipelining delays, depending on the sample rate it may require 2-20 samples after the trigger. You can configure it with such margin, for instance to collect 200samples and ignore the last 50 and use the first 150.

Hi @Stetramp Displaying the AWG data (theoretical voltage output) in the Scope may be misleading since the output may be attenuated, clipped, distorted... depending on the load. You could perform a well triggered capture of the AWG output with a Scope channel and add it as Reference channel. Thank you for the encouraging feedback.

Hi @Rick314 I'm trying to keep backward compatibility but there may some discordances, like here missing the "Auto sync" preset replacement by separate "Auto" option. I've added compatibility for this, so 3.18.60 or 3.19.4 will load this 3.12.2 setting appropriately.

Hi @Rick314 The next version will remember the used four symmetry/power separately values for ramp-up, down, sine-power and others. Thank you for you feedback.

Hi @EngineerAmjad In the Measurements view under Show menu select the Mean, Median...

Hi @Aye What operating system and architecture (32 or 64 bit or ARM) are you using ? In the WaveForms/ Settings/ Device Manager you can find a "My device is not listed" button, press this then "Find Devices". Does it detect anything ? If you are using Windows does Windows Device Manager detect "USB Serial Converter" under USB Controller after you connect the device ?

Hi @XerXes777 1. You can use Logic Analyzer and Export SPI (Events) or Protocol/SPI/Spy/Receive to File. 2. The Logic Analyzer shows the analog representation with taller rows. 2-3. You can also import data from file in the Oscilloscope interface where you have various data processing (Views) available or the Script tool.

Hi @piyush The driver is only available for 32 and 64 bit (Intel) Windows.

Hi @Rick314 This is intentional, when changing signal type the symmetry/power to be set to default value, like for ramps 0 or 100%, sinepower 0 and others 50%.

Hi @Rick314 You have set the Run time to 2ms, so the signals will restart every 2ms. Set this to 0/continuous or check Auto.

Hi @ssm The device has one, common GND which is connected to the computer through the USB cable. Connecting V+ to GND will short it and the supplies (V+/-) will shut down. You could for instance use V- as virtual ground for the circuit under test, so with V+/- +/-5V you could supply your circuit with 10Vpk2pk. In this case the W1 0V will be +5V for the circuit, -5V will be 0V, +5 will be +10V ...

Hi @cepp6 Did you try cleaning the receptacle by blowing or with a fine brush ?

Hi @DigilentFan I didn't hear such plans but if you want I can give you the schematic/layout to be able to modify the Digital Discovery, such would void the warranty.

Hi @cepp6 Isn't the problem a short micro-USB tip that doesn't fit all the way in and can't make proper contact? Have you tried using the original cable or other cables you have at hand? The part is USBC-FC05RB2N4, see:

Hi @ssm I don't know exactly your experiment details but you can configure the AWG offset, wait 100ms then generate signals... or you could use custom waveforms which does not need analog offset. The supplies have about 10ms, the AWG offsets 15ms and the Scope offset 0.5sec settle time. Due to this, after (the first) connection to the device or adjusting Scope offset or range you should wait at least 0.5-2sec.

Hi @YagoMonteiro For now, there is support for one UART receiver in the WF SDK/API

Hi @reddish The typical transfer and capture rates are done on my current setup. This, to have comparison between the 10 connection methods. The transfer rate is not only between the host-app and device firmware-system but also to/from the instrument/PL/FPGA. For both tests you can find the script in WF SDK/ samples/ py/ Device_Speed.py and AnalogIn_Wps.py The devices provide multiple instruments via one communication channel so the record/streaming is chopped up and the latency of this reduces the achievable rate. As I've told earlier, the ADP3X50 in Standard boot mode uses DDRam buffering can capture up 128MiSamples @ 125MHz for 1 channel and offers the best record rate due to large transfer chunks. For the other modes and devices you could use the device configuration with more oscilloscope buffer, like for ADP3X50 the 2nd. With ADP3X50 the capture is done on the enabled 1, 2 or 3/4 channels, when 3 are enabled the capture is done on 4 channels. Fully DDRam buffered 32MiSamples @ 31.25MHz / 4ch on USB or Ethernet: 200MiS @ 5MHz / 4ch, 5MHz = ~40MiBps/2B/4ch via USB: The Ethernet is not that reliable for streaming. It may have hiccups, intermittent longer latency which cause buffer overflow.

Hi @minghan chao Use FDwfDigitalOutRunSet to specify finite run length. By default this is zero which stands for continuous, the signals depending on their configuration are repeated indefinitely.

Hi @Arde What device/board are you trying to use ? and what computer/operating system are using ?

Hi @displaynam Try to increase the Rate, above twice of the I2C rate. You may also want to use trigger to capture useful data, communication phase. You can also increase the number of Samples or use Record mode instead Normal.

Hi @reddish The DDRam buffering is transparent to the user. The same record method can be used as with other devices, as it is in the examples. The option in the application was added because there was a bug with this buffering but it is solved in newer versions.

Hi @reddish The root requirement for the AXI probably will remain, at least I didn't hear any feedback on this from the Linux guys since the prototype phase. The digilent.adept.runtime...armhf.deb and digilent.waveforms.adp3x50...armhf.deb or digilent.waveforms...armhf.deb can be updated. digilent.waveforms.adp3x50...armhf.deb: contains WF runtime/API, and SDK (manual,examples,wrappers) digilent.waveforms...armhf.deb: contains WF application as well but it requires Qt libs. Intended for SBCs but newer versions of this package also support ADP3X50's AXI.

Hi @Kimson Lam For warranty and replacement contact the support.digilent at ni.com specifying the Date of Purchase, Seller and Purchase Order/ Web order Number.

Hi @Chris Marcellino The Impedance Analyzer uses AWG channel/voltage driver so the constant current mode can be implemented in custom software/script like it is in the application's example:

Hi @reddish The (version>>8)&3 identifies boot/connection mode: 0 - Linux 1 - Standard Recovery 2 - Standard 3 - AXI (embedded Linux interface)