Search the Community

Showing results for tags 'awg'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • News
    • New Users Introduction
    • Announcements
  • Digilent Technical Forums
    • FPGA
    • Digilent Microcontroller Boards
    • Non-Digilent Microcontrollers
    • Add-on Boards
    • Scopes & Instruments and the WaveForms software
    • LabVIEW
    • FRC
    • Other
  • General Discussion
    • Project Vault
    • Learn
    • Suggestions & Feedback
    • Buy, Sell, Trade
    • Sales Questions
    • Off Topic
    • Educators
    • Technical Based Off-Topic Discussions

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 8 results

  1. Hello. I have been using the Analog Discovery 1 (legacy version) as a portable oscilloscope and function generator. I am using the Wavegen as a function generator to test an analog front end (AFE) which includes an integrated instrumentation amplifier and an ADC ( Trying to characterise the performance of the AFE, I used the Analog Discovery's function generator to generate sine waves of different amplitudes (between 1mV and 100 mV pk-pk) and frequencies (between 40 and 200 Hz, in steps of 40 Hz). The gain of the instrumentation amplifier is fixed at 3.5 and the bandwidth of the AFE is programmable (ranging between 170 Hz and 340 Hz). I find that the gain of the system varies with frequency and is either 1 or slightly higher/lower than 1, depending on input voltage and frequency. I did not include any load resistance in my measurement circuit since the internal impedance of the voltage generator was 0 (as mentioned in and I would like to know if it would be necessary to include any load resistance while using the AWG as input to an instrumentation amplifier. If this is not the reason, what could be the reason for this mismatch in gain/amplification factor? I have posted a query in the TI forum (link: I have also attached the WaveForms workspace file I used. Thanks in advance for helping out with this. Best regards, Ganesh Load-resistance-test-2020-05-27.dwf3work
  2. I encountered a peculiar issue when using AWG2 of the Analog Discovery 2. Physical connections were as follows: 1+ to W2 1- to GND When AWG2 is set to generate a sine wave voltage <= 1.00V, the output seems to be a clipped version of a voltage referenced to +5V (USB +ve rail). At any voltage above that (>1.001), the output is fine. I'm using Waveforms 3.8.2 on a 64bit Win10 PC. I've attached a screen capture:
  3. Hi all, Most likely this question has already been answered, but I cannot find any info. Is it safe to feed the AWG of the Analog Discovery to the scope of the same device? can this somehow cause any damage to the AD2?
  4. """ DWF Python Example Author: Digilent, Inc. Revision: 2015/02/05 Requires: Python 2.7 Start synchronized the AWG outputs of multiple Analog Discovery devices. Connect the Trigger-1 pin of each device together. """ from ctypes import * import time import sys if sys.platform.startswith("win"): dwf = cdll.dwf elif sys.platform.startswith("darwin"): dwf = cdll.LoadLibrary("libdwf.dylib") else: dwf = cdll.LoadLibrary("") #print DWF version version = create_string_buffer(16) dwf.FDwfGetVersion(version) print "DWF Version: "+version.value cDevice = c_int() dwf.FDwfEnum(c_int(2), byref(cDevice)) # 2 = enumfilterDiscovery print "Found "+str(cDevice.value)+" devices" cChannel = 2 cOutput = cDevice.value*cChannel hdwf = c_int() #open device for iDevice in range (0, cDevice.value): dwf.FDwfDeviceOpen(c_int(iDevice), byref(hdwf)) if hdwf.value == 0: print "failed to open" quit() for iChannel in range (0, cChannel): print "Configure "+str(iDevice+1)+"/"+str(iChannel+1) # enable channel dwf.FDwfAnalogOutNodeEnableSet(hdwf, c_int(iChannel), c_int(0), c_int(True)) # 0 = AnalogOutNodeCarrier # configure dwf.FDwfAnalogOutNodeFunctionSet(hdwf, c_int(iChannel), c_int(0), c_int(1)) # 1 = funcSine dwf.FDwfAnalogOutNodeFrequencySet(hdwf, c_int(iChannel), c_int(0), c_double(1000.0)) dwf.FDwfAnalogOutNodeAmplitudeSet(hdwf, c_int(iChannel), c_int(0), c_double(1.0)) # set trigger source to external trigger 1 dwf.FDwfAnalogOutTriggerSourceSet(hdwf, c_int(iChannel), c_byte(11)); # 11 = trigsrcExternal1 #set different phase iOutput = iDevice*cChannel+iChannel dwf.FDwfAnalogOutNodePhaseSet(hdwf, c_int(iChannel), c_int(0), c_double(360.0*iOutput/cOutput)) # start the channel, this will wait for the trigger dwf.FDwfAnalogOutConfigure(hdwf, c_int(iChannel), c_bool(True)) # configure Trigger-1 pin to output the triggerPC signal for the last device dwf.FDwfDeviceTriggerSet(hdwf, c_int(0), c_byte(1)) # 1 = trigsrcPC # after open, before the first run wait a bit for the offsets to stabilize time.sleep(5) print "Pulse trigger to start generation..." dwf.FDwfDeviceTriggerPC(hdwf); time.sleep(60) print "done." dwf.FDwfDeviceCloseAll()
  5. Hi , while changing the frequency from WaveForms with Analog Discovery 2 the transition between frequencies is not a smooth, it forces the Wavegen to reset the start applying the new requested frequency. is it possible to have a smooth transition between frequencies for example while using the basic settings on WaveForms can I use the bar to set a new target frequency then the transition from the old running frequency to the new target one is controlled somehow like a small sweep to the new target frequency. hope that makes sense ..... regards
  6. In Waveforms 2015, is it possible to set up a wave in the AWG to be triggered by every other pulse in the scope? I'm currently trying to use a 10 Hz external pulse connected to the Analog Discovery's scope as the trigger for a 5 Hz waveform from the AWG, but I need to have the event trigger only once the 5 Hz waveform has finished one pulse. Effectively, I'm putting together a slower trigger for one device that's triggered from the AD's scope using a faster external pulse. It appears that Waveforms 2015 has some logic capabilities incorporated into the software, but as I don't have a background in logic circuits I'm not even sure if the logic circuit feature can work this problem out. Any help with this will be much appreciated~
  7. Hello All, I'm playing around with the "analogout_custom" C sample program that comes with the Waveforms SDK (/usr/share/digilent/waveforms/samples/c/analogout_custom.cpp). I've made some observations that don't align with my expectations. I'm hoping one (or more) of you could kindly offer some insight on what is happening. I'm running on an Ubuntu 16.04 x86-64 machine. I have an Analog Discovery 1 and an Analog Discovery 2 wired such that ad1.aout1 --> ad2.ain1+ ad1.gnd --> ad2.ain1- I'm playing the waveform out through the Analog Discovery 1 and the "analogout_custom" program. I'm capturing the resulting waveform through the Analog Discovery 2 and the Waveforms 2015 oscilloscope. I've attached my Waveforms 2015 oscilloscope configuration file. I've also attached a screenshot of the Waveforms 2015 oscilloscope showing the results of two runs of "analogout_custom". Channel 1 (yellow) displays the waveform produced by my most recent run of "analogout_custom". Reference 1 (gray) displays a waveform that was captured on Channel 1 during a prior invocation of "analogout_custom" and saved off as a reference waveform. Expectations: 1) A waveform consisting of 4096 samples played at 10 kHz should have a duration of ~0.5 seconds. 2) The waveform should play once, given the default of AnalogOutRepeat = 1. 3) The waveform should begin playing at the first sample, which always has the same value. 4) The generated waveform should be consistent for all invocations of "analogout_custom". Unexpected observations: 1) The waveform has a duration of ~1.8 seconds, as highlighted by the cursors' delta X in the oscilloscope screenshot. 2) The waveform plays more than once, as indicated by the multiple peaks on the yellow waveform in the oscilloscope screenshot. 3) The waveform does not begin playing at the first sample, as indicated by the different values at x=0 for the yellow and gray waveforms. 4) The played waveform is not consistent between invocations, as indicated by the yellow and gray waveforms not aligning. Here's the "analogout_custom.cpp" source code for your convenience: #include "sample.h" int main(int carg, char **szarg){ HDWF hdwf; double rgdSamples[4096]; char szError[512] = {0}; // generate custom samples normalized to +-1 for(int i = 0; i < 4096; i++) rgdSamples = 2.0*i/4095-1; printf("Open automatically the first available device\n"); if(!FDwfDeviceOpen(-1, &hdwf)) { FDwfGetLastErrorMsg(szError); printf("Device open failed\n\t%s", szError); return 0; } printf("Generating custom waveform for 5 seconds..."); // enable first channel FDwfAnalogOutNodeEnableSet(hdwf, 0, AnalogOutNodeCarrier, true); // set custom function FDwfAnalogOutNodeFunctionSet(hdwf, 0, AnalogOutNodeCarrier, funcCustom); // set custom waveform samples // normalized to ±1 values FDwfAnalogOutNodeDataSet(hdwf, 0, AnalogOutNodeCarrier, rgdSamples, 4096); // 10kHz waveform frequency FDwfAnalogOutNodeFrequencySet(hdwf, 0, AnalogOutNodeCarrier, 10000.0); // 2V amplitude, 4V pk2pk, for sample value -1 will output -2V, for 1 +2V FDwfAnalogOutNodeAmplitudeSet(hdwf, 0, AnalogOutNodeCarrier, 2); // by default the offset is 0V // start signal generation FDwfAnalogOutConfigure(hdwf, 0, true); // it will run until stopped or device closed Wait(5); printf("done\n"); // on close device is stopped and configuration lost FDwfDeviceCloseAll(); } Thanks in advance! Chris (This is a repost. Original post somehow ended up in Home > Digilent Technical Forums > Scopes & Instruments > WaveForms Live and OpenScope feedback.) analogout_custom.dwf3scope
  8. Hello, My question is about the output current of the AD2, AWG. I know the current Max. Output is 10mA, but, I can't find if that current is expressed in Irms or it is Ipeak. I need to know that, because I want to build a box with a potentiometer inside, in order to control the output amplitude in an analogic fashion, setting the AWG out (sinewave) to 10Vpp (5Vp or 3.53Vrms) and set the potentiometer to taste to achieve the voltage needed. Trying to figure out what potentiometer I should use, doing the math tells me that a 50ohm pot is way too low to load the AWG output, taking the 50ohm output impedance from the BNC board and adding the 50ohm potentiometer, it gives 50ohm + 50ohm = 100ohm then 5Vp/100ohm = 50mA ... five times the Max Rated current of the AWG output if the 10mA is expressed in peak current, or 50mA x 0.707 = 35.35mA thre and a half times if it is expressed in rms current. So, doing the inverse math, with a maximum current of 10mA, and the maximum voltage coming out of the AWG, it gives : 5Vp / 10mA = 500ohm potentiometer or 3.53Vrms / 10mA = 353ohm (not a standard value). Could I use a 500ohm potentiometer safely to control the amplitude of the AWG output with no drop of the 5Vp? If I'm at the maximum output voltage and current, will it present more THD at this output? Thanks in advance Albert