Search the Community

Showing results for tags 'ad2'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 75 results

  1. We're excited about using the AD2 for a whole bunch of courses in our college as we teach online for the foreseeable future. One useful feature would be if we could get the raw A to D data from the scope channels so we can use them in LabVIEW. At this point, niVB_MSO_ReadAnalogDigitalU64 provides the voltages, all cleaned up, instead. Is there another dwf that provides the raw data, or could this feature be added to the next revision? At this point, I'm taking the voltage and converting it back to a step count using the step size, but we'd be just a bit more accurate if we had the raw data.
  2. Hi. I have troubles using the trigger functions in the SDK to align the recording of a signal with the pattern generator (DigitalOut Instrument on AD2). What I want to do is essentially, using the SDK in a python script is: - I record a signal from the AWG on the AD2 I am sending through an analog circuit using two multiplexers. - I control the multiplexers with the digitalOut instrument on the AD2. - I want to align the starting point of the digitalOut-pattern and the starting point of the AnalogIn acquisition (record-mode, int16 data) As far as I understand from the SDK reference for this purpose I can trigger the analogIn with the digitalOut (use trigsrcDigitalOut from the dwf constants). However, when I implemented this, I get an undefined timelag between the acquistion of data and the start of the digitalOut signal. To illustrate this, I recorded the signal of one of the digital pins I use to generate the pattern for the multiplexers (I record the bare 16int ADC conversions, to read faster from the AD2). I sample at 1Mhz and the the pattern I output on this particular pin starts with (1,0,...) at 100Hz. As you can see, the timelag seems to be around ca. 1.5 ms. I also did another experiment, trying out the same thing in the WaveForms Software. Instead of outputting a custom pattern, I just output a clock at 100Hz on the same digital pin and record this signal through channel 1 of the oscilloscope. From what I understand, the two experiments should be pretty much equal, so I am puzzled I get this delay of approximately 1.5ms when I implement it with SDK functions. Does anyone have an explanation why the trigger is not correctly aligned in my python script, and why this timelag is not deterministic? Any help would be greatly appreciated! (PS: I can provide a code snippet, but right now my code is shared from different fies & classes, so it is not straightforward to copy it to here...) updated: I have a code snippet for illustration below: import math import sys import time from ctypes import * import matplotlib.pyplot as plt import numpy from dwfconstants import * if sys.platform.startswith("win"): dwf = cdll.dwf elif sys.platform.startswith("darwin"): dwf = cdll.LoadLibrary("/Library/Frameworks/dwf.framework/dwf") else: dwf = cdll.LoadLibrary("libdwf.so") # declare ctype variables hdwf = c_int() sts = c_byte() hzAcq = c_double(1e6) nSamples = 2 ** 17 rgSamples = (c_int16 * nSamples)() cAvailable = c_int() cLost = c_int() cCorrupted = c_int() fLost = 0 fCorrupted = 0 # print(DWF version version = create_string_buffer(16) dwf.FDwfGetVersion(version) print("DWF Version: " + str(version.value)) # open device print("Opening first device") dwf.FDwfDeviceOpen(c_int(-1), byref(hdwf)) if hdwf.value == hdwfNone.value: szerr = create_string_buffer(512) dwf.FDwfGetLastErrorMsg(szerr) print(str(szerr.value)) print("failed to open device") quit() ######################################################################################## # set up pattern generator data = [1, 0, 1, 0, 0, 1, 0, 0, 1] pin = 11 hzSys = c_double() dwf.FDwfDigitalOutInternalClockInfo(hdwf, byref(hzSys)) rgbdata = (c_ubyte * ((len(data) + 7) >> 3))(0) # array to bits in byte array for j in range(len(data)): if data[j] != 0: rgbdata[j >> 3] |= 1 << (j & 7) # var |= value is var = var | value print("bytestream of data " + str(pin) + ": " + str(list(rgbdata))) dwf.FDwfDigitalOutEnableSet(hdwf, c_int(pin), c_int(1)) dwf.FDwfDigitalOutTypeSet(hdwf, c_int(pin), DwfDigitalOutTypeCustom) dwf.FDwfDigitalOutIdleSet(hdwf, c_int(pin), DwfDigitalOutIdleLow) # set Divider to generate output at frequency f_scan. dwf.FDwfDigitalOutDividerSet(hdwf, c_int(pin), c_int(int(hzSys.value / 100))) dwf.FDwfDigitalOutDataSet(hdwf, c_int(pin), byref(rgbdata), c_int(len(data))) dwf.FDwfDigitalOutTriggerSourceSet(hdwf, trigsrcNone) # set up acquisition dwf.FDwfAnalogInChannelEnableSet(hdwf, c_int(0), c_bool(True)) dwf.FDwfAnalogInChannelRangeSet(hdwf, c_int(0), c_double(5)) dwf.FDwfAnalogInAcquisitionModeSet(hdwf, acqmodeRecord) dwf.FDwfAnalogInFrequencySet(hdwf, hzAcq) dwf.FDwfAnalogInRecordLengthSet( hdwf, c_double(nSamples / hzAcq.value) ) # -1 infinite record length dwf.FDwfAnalogInTriggerSourceSet(hdwf, trigsrcDigitalOut) # wait at least 2 seconds for the offset to stabilize time.sleep(2) print(f"Starting oscilloscope. Measure digitalout pin {pin}") dwf.FDwfAnalogInConfigure(hdwf, c_int(0), c_int(1)) # configure digitalOut instrument, don't run yet (enough time to fill buffer with data) dwf.FDwfDigitalOutConfigure(hdwf, c_int(0)) time.sleep(2) cSamples = 0 # start the digitalOut instrument dwf.FDwfDigitalOutConfigure(hdwf, c_int(1)) while cSamples < nSamples: dwf.FDwfAnalogInStatus(hdwf, c_int(1), byref(sts)) if cSamples == 0 and ( sts == DwfStateConfig or sts == DwfStatePrefill or sts == DwfStateArmed ): # Acquisition not yet started. continue dwf.FDwfAnalogInStatusRecord( hdwf, byref(cAvailable), byref(cLost), byref(cCorrupted) ) cSamples += cLost.value if cLost.value: fLost = 1 if cCorrupted.value: fCorrupted = 1 if cAvailable.value == 0: continue if cSamples + cAvailable.value > nSamples: cAvailable = c_int(nSamples - cSamples) dwf.FDwfAnalogInStatusData16( hdwf, c_int(0), byref(rgSamples, sizeof(c_int16) * cSamples), c_int(0), cAvailable, ) # get channel 1 data # dwf.FDwfAnalogInStatusData16(hdwf, c_int(1), byref(rgSamples, sizeof(c_int16)*cSamples), c_int(c), Available) # get channel 2 data cSamples += cAvailable.value dwf.FDwfAnalogOutReset(hdwf, c_int(0)) dwf.FDwfDeviceCloseAll() print("Recording done") if fLost: print("Samples were lost! Reduce frequency") if fCorrupted: print("Samples could be corrupted! Reduce frequency") f = open("record.csv", "w") for v in rgSamples: f.write("%s\n" % v) f.close() plt.plot(numpy.fromiter(rgSamples, dtype=numpy.int16)) plt.show()
  3. I am trying to get my Analog Discovery 2 to work with NI LabVIEW 2019. I've searched around and most of the info I see calls for LabVIEW 2014, so it is not clear to me if it does or does not. I have installed the AD2 Toolkit and the Digilent WaveForms VIs. My problem is what is the "Device Name" that need to be entered? I see the AD2 with the WaveForm 3.13.10 x64 using Windows 10 and full LabVIEW 2019 x32. Thanks for shedding any light on the situation. JoeD
  4. I've been trying to learn how to use the AD2 Logic Analyser. I got it to work with Serial.println("Hello world!"). I've learned that the Base: selection is critical to capturing the data. If you get it wrong, you get Framing Errors and the wrong characters. Now I am trying to use the Logic Analyser with an Arduino Uno running a clock/date ino that displays on a 16x2 LCD. I do not have the LCD connected, but when I wrote the program it was and it worked perfectly. I have also tried an ino that displays Hello World on the top line of the LCD. My connection is described below. I have tried several different setups in the Logic section of Waveforms and I am not able to capture ascii data. I've tried spi, spi mosi/miso, UART, and a few others. I have also tried to just add Signal lines to the connections below. With that, I am able to see the waveforms, but not the data. Is it possible to read the data with the AD2 and Waveform? The ino notes say to connect the Arduino to the LCD as follows. The number after the dash is the AD2 logic connection wire. I.E. I have a jumper from Arduino Digital pin 12 to AD2 Logic wire 0 and so on. As the LCD is not physically connected. some of the connections in the ino were not used (as noted). * LCD RS pin to digital pin 12 - 0 * LCD Enable pin to digital pin 11 - 1 * LCD D4 pin to digital pin 5 - 2 * LCD D5 pin to digital pin 4 - 3 * LCD D6 pin to digital pin 3 - 4 * LCD D7 pin to digital pin 2 - 5 * LCD R/W pin to ground - (Not Used) * LCD VSS pin to ground - (Not Used) * LCD VCC pin to 5V - (Not Used) I have a jumper from the Android ground to the AD2 Ground. Thanks JohnnyG
  5. I just purchased the Analog Discovery 2 and ran through the calibration procedure with no problems. My question is the calibration adjustment reside in the the AD2 or as a file on the computer I ran the calibration on? If it is stored within the AD2 than that should allow me to move it to another computer or must I recal it if I plug it in to another computer. Thanks for any calcification. JoeD
  6. Hi Allita My Analog Discovery AD2 crashes waveforms when I plug in a external +5V psu. My PSU has cable has the deminsions 5V DC voltage supply with at least 3A max current, Outer diameter 5.5 mm and inner pin 2.1mm diameter positive inner pin = 5v Outer case =0 V DC plug connected up as shown the in above photo. This solutions complies to the hand book rules here https://reference.digilentinc.com/reference/instrumentation/analog-discovery-2/reference-manual Normally my Analog Discovery AD2 when just powered by the USB cable works fine without any issues. Any ideas of how to fix the issue ?? Best wishes Simon
  7. Hi With the waveforms tool is it possible using python scripting in the Waveforms platform to do the following ?? Use the Digilent Analogue discovery 2 - Attach a device like a PMOD device eg accelerometer https://store.digilentinc.com/pmod-acl-3-axis-accelerometer/ using the Analogue discovery 2 ability to chat SPI & IC2 - pmod DEVICES SUPPORT 12-pin Pmod connector with SPI interface and 2×4-pin I²C interface - Then using the read information from the PMOD device treat it like an extra oscilloscope channel . Either as a Analog channel or Digital channel depending on the the signal type acquired from the PMOD device. This is possible with Labview but that would also require a lot of code writing. If this is possible this is outstanding feature when considering all the available PMOD devices available from the list https://store.digilentinc.com/by-function/input/ This would be a real product enhancement for Digilent and the Analog Discovery and help sell the AD2 in to many new places . Best wishes Simon
  8. Hi Digilent AD2 Team, I have a simple question, for which I don't find an quick answer. I want to measure the waveform of a the mains voltage 11VAC using the oscilloscope of the AD2. What is the best way, to achieve this? Thanks for your help and with best greetings, Lars
  9. Analogue Discovery 2 https://forum.digilentinc.com/applications/core/interface/file/attachment.php?id=12669 https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019Ls1SAE&l=en-US Hi Firstly I would like to say what great product the Analogue Discovery 2 is, I have used it for 8 months to develop a product. It is by far the best PC scope that , I have used. Far better than a PICOSCOPE from the UK company PICOSCOPE or any of the Chinese PC scope knock offs. Analogue Discovery 2 is a serious peice of professional kit and not a toy. This a summary of all of the useful information I found when working with the Analogue Discovery 2 for 8 months 1. Always use the latest WaveformsSDK https://forum.digilentinc.com/topic/8908-waveforms-beta-download/ 2. vb.net driver rapper https://forum.digilentinc.com/applications/core/interface/file/attachment.php?id=9726 https://forum.digilentinc.com/topic/17736-digilent-analog-discovery-2-dll-driver-for-vbnet-and-c-in-visual-studio-2017/#comment-45135 3. C# complete .net rapper than can be used for vb.net as well as C# https://github.com/Andrei-Errapart/WaveFormsSDK It is possible to take full control of the Analogue discovery 2 using C# or vb.net or python or labview. 4. C# oscilloscope GUI panel that works and can be used in both VB.net and C# https://www.codeproject.com/Articles/16350/High-Speed-Feature-Rich-and-Easy-To-Use-Graphs-and I have tested this C# plugin and it works really well . 5. KICAD PCB tool projects that are very intersting This way you can make your own projects which plug onto the analog discovery 2 https://github.com/jubeormk1/AnalogDiscovery_x20_powerMainsProbe https://github.com/jamescarruthers/analogdiscovery2io https://github.com/james-everitt/AnalogDiscovery2Eurorack https://reference.digilentinc.com/_media/reference/instrumentation/analog_discovery_impedance_analyzer_sch.pdf 6. General https://github.com/Elektrolab/AnalogDiscoveryScope https://github.com/AndrewQM/AnalogDiscoveryScripts https://github.com/bienata/AnalogDiscovery2 https://github.com/pascalhuerst/FreqResp https://github.com/HutzlerLab/AnalogDiscovery https://github.com/holla2040/ad2 https://github.com/ATPanetta18/ADAP https://github.com/michael-christen/digilent_interface <<<<-- linux command line interfasce for AD2 The question ============= Will the waveforms SDK every be compiled to work on the Windows10 ARM64 platfrom. ?? see https://www.altomdata.dk/guide-koer-komplet-windows-10-paa-raspberry-pi
  10. Hi, I would like to measure control loop gain of DC-DC converter using AD2 network analyzer. Is it possible to add a digital filter to input channels of AD2 and measure gain and phase shift after digital filtering?
  11. Hi Guys, I'm new to the AD2 & Waveforms, and in the need of some help. I'm trying to import a csv file into a custom wavegen and then output it. Here is my code: if(!('Wavegen1' in this)||!('Scope1' in this))throw"Please open a Scope and a Wavegen instrument"; var filename = "/Users/PaulBritten/Documents/AFWorkMain/AFWork/Waveform/single_qrst_improved_twave_1khz.csv"; var file = File(filename); print("exists? " + file.exists()); var arr = file.readArray(); print(arr); Wavegen1.Channel1.Mode.text = "Custom"; Wavegen1.Channel1.Custom.Type.set("MyWave", arr); Wavegen1.Channel1.Custom.Type.add(arr); Wavegen1.Channel1.Custom.Offset.value = 0; Wavegen1.Channel1.Custom.Frequency.value = 1; Wavegen1.Channel1.Custom.Amplitude.value = 1; Scope1.Trigger.Trigger.text = "Repeated"; Wavegen1.run(); Scope1.run(); Can anyone explain to me why I'm getting this error: Thanks for any help in advance. Best wishes Paul
  12. Hi folks - I have a Mac running 10.10.5 and another with 10.11 both not connecting to the Analog Discovery 2 hardware over USB. What I know: Hardware works fine from a Windows VM on the Mac Plugging in the AD2 loads kext com.digilent.driver.DigilentFtdiDriver AND com.apple.driver.AppleUSBFTDI Neither removing com.apple.driver.AppleUSBFTDI via kextunload nor deleting the kext file helps Following the *awesome* steps at this post didn't help - WaveForms sees and loads the driver (no logs spit out normally; logs spit out when I rename driver) but still no dice Keeping AD2 unplugged while restarting: no dice Reinstalling WafeForms and DigilentFtdiDriver-1.0.3.pkg - no dice Any ideas? Eager to get working on Macs.
  13. Hello, I am currently working with the FPGA Board ZYBO Z7020. Part of my current task is: Apply a voltage to the AD2, the FPGA contains some logic and has to output the same Voltage with a DA2. I configured a VHDL I2C Master for communication with the AD2. I also attached an image with how I added the pullup Resistor in the schematic. I am using the internal voltage reference, which equals VCC = 3,3V. I am also watching the SDA Line with an oscilloscope to have a look at the data the ADC sends to me. I can apply an input voltage (DC) to the AD2 with a Waveform Generator. The AD2 works in High Speed mode (1MHz Clock). The configuration I use is: "00010011". The big problem with the SDA Data from the AD2 is: It reaches its maximum at 1,65V Input Voltage, so at 1,65V input voltage, all bits of the 12 bit data are '1'. I just can't figure out, why that's the case. The jumper on the AD2 board is set to "REF", the configuration tells the AD to use this reference and not an external one and the VCC at the PMOD surely delivers 3,3V. Any idea about what I am doing wrong? EDIT: I am only using Channel 0 for conversion.
  14. Hello everyone, I have problem with impedance data exporting from AD2 and can't find-out the solution. I wasn't lucky to find people who had the same problem. Problem: exporting Impedance measurement data to CSV I got empty rows. Graph looks correct. All data point refer to only one number, so results only horizontal line. I had the same problem with older version WaveForms and from first was thinking that update solved my problem, but it still occurring. I had idea that I save to much reference lines in Workspace, but problem accures with 6 reference lines too. System: MacOS High Sierra. WaveForms 3.10.9 64-bit Qt5.6.3 macOS 10.13 If anyone has any ideas please let me know the solution.
  15. Hey there I'm thinking about to get a AD2 for my project and I want to make sure, if everything will be working fine. I want to achive a closed loop with the AD2. I want to set a PWM to control a motor though the Matlab Data Acquisition Toolbox and check simultaneously the pulse signals of the hall sensor with the ADC. Is this possible? The ADC should work with 10Ms/s to get the data. The PWM will be around 20KHz Square/Sinus output. Thanks in advance
  16. Hello I certainly miss something, but I cannot figure out how to trigger pattern with an AWG output. According to the reference manual: Each instrument generates a trigger signal when a trigger condition is met. It's rather easy to trigger the AWG and the pattern output with the scope, but I didn't figure out how to trigger patterm output with AWG. I certainly didn't found what a "trigger condition" is for an AWG. What I'm trying to do is to have two AWGs synchonized and one positive pulse at phase 0. I can imagine to use Ext trigger, and to wire T1 on T2, but that doesn't seems to make sens. Thanks for your help. default.dwf3work
  17. Hi, I'am currently using my AD2 in Matlab 2018b and altough I'm capable of using some functionalities (the ADCs, for ex), I couldn't find a way of setting the power supply. Which, by the way, is doable in Waveforms. Does anyone know how can I set the DC power supply from Matlab? Thank you in advance for your time!
  18. Hi all I would like to try the Protocol I2C function in WaveForms, and I set DIO7 as SCL, then I connect DIO7 to DIO15, and set Logic analyzer to watch I2C signal. After I clicking Write button on Protocol UI, the Logic UI didn't show the clock signal. Can't I do this? I tried UART also. It work fine. Thanks
  19. Hello, Some days ago I installed the new Waveforms software to update from Waveforms 2015. I have found that when running a loopback to check the Network Analyzer, the signals going to both scope inputs, randomly, stop the data adquisition, resulting in a bad representation of the bode plot. It happens in a random fashion, and when it fails, happens at the beggining of the sequence. I tryied to reinstall an older version of Waveforms and it works flawlessly. Checking the latest version in other computers, it fails too. Best regards Albert
  20. Hi, and thanks for the support so far. After a lot of experimenting and reading the help, I'd like to understand the "envelope" of possible triggered, repeated, logged acquisitions, which can run unattended for days or weeks. We need to leave a system in an inaccessible location and log at least 4 analog channels with at least 100 KHz sample rate, for a time of at least 100 usec after the trigger occurs for each triggered event. We believe these events have a time frame of 5 or so 60 Hz cycles, so that's 85 msec post-trigger and we'd like a cycle or two (16 or 32 msec) of pre-trigger. These events are rare and not on a predictable timetable. So we are rather searching for a needle in a haystack and we hope to find evidence it exists. Here I am talking about Scope function (Logger's sample rate of 100 msec is too slow for this case) and there are still many details I don't claim to understand. But since I need to make a report of what is possible with AD2, here goes. Record mode can capture much longer numbers of samples Device manager determines what is possible (e.g. Patterns) but some things seem ignored (e.g. Scope samples) Sample rate, number of samples, and pre-trigger samples are set with the "Config" button with the green diode-like symbol. This is intuitive with a % of total acquisition setting for trigger location. Zooming and scrolling in the display window does not change what you set with the Config button so subsequent captures use the same config. Actual sample rate and length is limited by USB connection speed to the host PC. On a 1.7 GHz dual core Linux with 16 GB RAM and SSD, it seems to be limited to 200 KHz sample rate. At 100 KHz we can capture up to 10 M samples, for a 100 second acquisition Acquisition in "record" mode can only be started with a button click and cannot be triggered by normal scope triggers even though those settings are still present on the GUI. Pressing Record is the only way to start capture and that immediately captures one acquisition. It can't wait for trigger conditions to be met. An acquisition can be saved using the logging settings if set for "each triggered acquisition", even though it really wasn't 'triggered'. Also "each acquisition" works. In record mode, if Device Manager is set to allow it, Patterns can work to use Scope Detector to make an external trigger output on a DIO pin, and this will trigger on the stated conditions but only *after* the Scope Record button is clicked. And I also have to remember to separately click the Pattern Run button or its output won't generate This can only record a single event and you have to click on the Scope Record button to start the acquisition. So Record mode won't work for us. In "repeated" mode, the scope will use the trigger settings Device Manager determines how many samples can be captured: 8K or 16K are the highest options of the 6 available and those seem to be the only ones possible. so it can wait until trigger conditions occur, then capture each time the trigger conditions are met. Sample length is a max of 16384 samples Settings - Options can make one of the trigger pins "Scope" which generates a single rising edge trigger per acquisition, to trigger other AD2s or other logging devices Sample rate and pre-trigger are confusing in repeated mode. It appears they can be set in the Time dialogs, also number of samples, pre-trigger (the "position" setting), but this interacts with the scope display screen: zooming and panning changes your intended settings. There seems to be no way to lock them like on a traditional desktop DSO. It's nothing like Config in Record mode. The display has 10 divisions so if I want to trigger at 2 divisions I'm better off to drag the white triangle on the top of the scope display to 2 divisions from the left. In repeated mode, Trigger takes place at time 0 and pretrigger time is negative. So for 16K samples at 100 KHz, that is about 16 msec/div. Trigger two divisions from left makes the leftmost time -32 msec and Time "Position" 48 msec, which doesn't make any sense to me. Time Base is 16 msec/div as expected. Don't dare zoom in the scope display or the time settings will also change, changing the next triggered acquisition! If you do this by accident its a tedious, multi-click process to get back to the settings you intended. At 100 KHz 16384 samples is 168 msec, long enough for us, we hope. At 8K samples we'd have to drop to 50 KHz samples Clicking Run button means scope will wait for trigger satisfied, then log both channels to PC memory, auto-incrementing the file name File name can include day hour min sec which is handy. Be careful entering this information or Waveforms will crash. I'll post a bug elsewhere. Full timestamp and setting values are included in the .csv log file You specify how many acquisitions to save, at which point logging halts. 1,000,000 is the largest number I could set. Saving workspace sometimes causes a ghost progress window which can be cleared with another save. So Repeated mode will work for us, with the limits of 16K @ 100 KHz samples Each 2-channel 16K log file is about 984 KBytes. As each 16K sample file is a bit under 1 MByte, you get 1000 log files per GB. Summary: For unattended, auto trigger and acquisition of multiple events, and logging to a computer file, "repeated" mode is the only option. We can log two analog channels per AD2, plus digital inputs if we wish. External trigger output: one rising edge per triggered acquisition. Trigger goes low at end of acquisition. Trigger other AD2s or external equipment. Samples per acquisition are 16K or 8K Logging can occur up to the maximum value you set (up to 1 M acquisitions), or the PC runs out of disk space, at about 1 MByte per 16K acquisition.
  21. I am having an issue generating back to back analog input single-shot acquisitions using the AD2 with Python scripting. Modified the AnalogIn_Trigger.py example script sample as the basis. This script has a comment that acquisition is started automatically after the done state which is causing the AD2 to trigger twice instead of doing a single-shot. Tried several things to configure for single-shot mode but not having any success. What commands are required to configure the device for single acquisition mode?
  22. To have a better FFT resolution we want to reduce the sample rate to around 1Msps either in AD2 or Openscope, can we replace the main clock or have other option to accomplish it? Thanks
  23. Hi, I just added a function generator amplifier to my AD2, and i recognized the following: - When everything is hooked up (function gen + 21W lamp for testing) and i start waveforms, it seems that the output of the AD2 goes unwanted high. (There is some current drawn from the power supply at the same time) - The same thing happens: -when you click in the close window button on the top rigth corner when the window pops up that asks you to save the current workspace. but in this case the current drops much slower. (as seen on the power supply) Waveforms Version 3.8.2 64-bit Windows 10
  24. Hi All I used AD2 with a Digilent Impedance Add-on board, and absent-mindedly pulled it off while it was still on and active! The result is that, although the impedance measuring process works ok, and I can use the wavegen 1/2 on the scope 1/2 with jumpers externally, it won't trigger internally now. A curious thing is that in Static DIO, the pins react with a flickering when I run my fingers along the pins. Looking at the CCT, it seems I could have damaged the internal digital 3.3V supply, IC30 AD2503, which just seems to be for the diode protection ccts of the dio's. What to do do now? I Re-installed Waveforms, reset calibration...
  25. New here in these forums. I have an Analog Discovery 2 for a few months now ... Cheers