Search the Community

Showing results for tags 'analog discovery 2'.



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
    • LabVIEW
    • Other
  • General Discussion
    • Project Vault
    • Learn
    • Suggestions & Feedback
    • Buy, Sell, Trade
    • Sales Questions
    • Off Topic
    • Educators
    • Technical Based Off-Topic Discussions

Calendars

  • Community Calendar

Found 94 results

  1. AD2 device name in c#

    I’m writing a custom application in c# for the Analog Discovery 2. Things are working fine except I cannot get the device name and device serial number. dwf.FDwfEnumSN and dwf.FDwfEnumDeviceName execute but do not return a string. How should I declare the variables? I’ve tried all I can think of. Thanks
  2. I am having a similar issue when running as a normal user under Ubuntu 16.04.4 LTS and have installed the following packages per the standard instructions for running the Analog Discovery 2 device. ii digilent.adept.runtime 2.17.1 amd64 Digilent Adept Runtime ii digilent.waveforms 3.7.5 amd64 Digilent WaveForms Currently I am only able to run waveforms under "sudo" and not as a standard user. As a standard user executing env LD_LIBRARY_PATH=/usr/lib/digilent/waveforms/qtlibs gdb /usr/lib/digilent/waveforms/waveforms Thread 10 "waveforms" received signal SIGSEGV, Segmentation fault 0x00007fffecce2fc6 in libusb_close () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 The Full Backtrace is as follows #0 0x00007fffecce2fc6 in libusb_close () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 #1 0x00007fff375e492d in CloseDevice () from /usr/lib64/digilent/adept/libftd2xx.so #2 0x00007fff375e5c91 in OpenDevice () from /usr/lib64/digilent/adept/libftd2xx.so #3 0x00007fff375e61ed in FTCommonOpen () from /usr/lib64/digilent/adept/libftd2xx.so #4 0x00007fff375e633e in FT_OpenEx () from /usr/lib64/digilent/adept/libftd2xx.so #5 0x00007fffefd55cae in ?? () from /usr/lib64/digilent/adept/libdpcomm.so.2 #6 0x00007fffefd501b3 in ?? () from /usr/lib64/digilent/adept/libdpcomm.so.2 #7 0x00007fffefd4c6f8 in ?? () from /usr/lib64/digilent/adept/libdpcomm.so.2 #8 0x00007fffefd4a3d6 in ?? () from /usr/lib64/digilent/adept/libdpcomm.so.2 #9 0x00007fffefd498dc in ?? () from /usr/lib64/digilent/adept/libdpcomm.so.2 #10 0x00007ffff395a6ba in start_thread (arg=0x7fffc4907700) at pthread_create.c:333 #11 0x00007ffff48b941d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Running strace this line appears 3 times: open("/dev/bus/usb/002/004", O_RDWR) = -1 EACCES (Permission denied) At a glance this appears to be a permission issue for accessing the USB port/driver for this device; is there a recommended adjustment or fix for this at this time?
  3. How can I setup Analog Discovery 2 to measure the time between two rising edges on two different channels? I'm just interested in the time, not collecting the waveform.
  4. I had a working Debian 8 production system using python2.7 to talk to an Analog Discovery 2. I decided to update the .deb packages to be current and now I get "Segmentation fault" "stack smashing detected" when I try to start my python program. I was using the amd64.deb files: digilent.adept.runtime 2.16.6 digilent.waveforms 3.5.4 (for the libdwf.so file) Upgraded to digilent.adept.runtime 2.17.1 digilent.waveforms 3.7.5 Also on the system is digilent.adept.utilities 2.2.1. I tested just upgrading the runtime package and my program works. Upgrading the waveforms package (and thus libdwf.so) causes the segfault. Any thoughts on how I might track down where the problem is?
  5. Hello, I use the internal circuit board of Analog Discovery 2 on my test fixture board but the external case is not used. Would you please provide a 3D model of the internal circuit board assembly (PCBA)? Thanks, Choon Shin
  6. Received my Analog Discovery 2 last weekend and now I am debugging a hardware of us where analog and digital is involved... In the device manager I chose 2x8k for scope and 16x4k for logic. When displaying scope and 2 logical inputs I see that the analog scope shows: 8192 samples @ 800kHz, which makes 10msec in total...this is also the whole screen. In the logic part it tells 2048 samples @ 200kHz... Why doesn't the logic part sample at 400kHz as it has half the memory depth per channel as the analog part? (4k versus 8k) Is there a way to capture or log based on analog trigger where the timescale is around 50msec but the logic part should be able to decode 115.2kBaud?
  7. Hi Everyone, I was going to order an analog discovery 2 pro bundle but I qualify for the educational discount and wanted to figure out what accessories I really need. 1) Definitely wanted the BNC adapter board for $19.99 2) I can use any BNC probes with this, right? Like I could order them from Amazon, etc. or use existing ones that I have? 3) I need to measure current on a 5V circuit around 1-5 AMPS for a battery powered project. I bought two higher current .10 ohm resistors figuring I could connect probes against that to measure current and they would only slightly drop the voltage at these amperage ranges, but with a high resolution scope, I could go lower resistance. Or can I get probes that do this for me? 4) Do I need the Mini Grabber test clips -- what are they for? 5) What is meant by "The Analog DIscovery BNC adapter board does not have differential analog scope inputs? 6) Any other must have accessories? Thanks in advance for any help or input -- this looks like a great little device (and sniffing various protocols and simulating GPIO will be great)! MetroWestMA
  8. Waveforms allows the user to turn the power supplies on and off, and set the voltage for the Analog Discovery 2. How do you do this with the SDK? Also, what is the default setting? I cannot find anything in the documentation. Thanks!
  9. I want to capture UART data and SPI data at the same time in the Logic analyzer of Analog Discovery 2. UART baud is 115.2kHz and SPI is at 8Mhz. when i increase the sample rate, UART data is not captured. and without increasing the sample rate i can not capture SPI data. what is the optimal setting to capture both low frequency and high frequency signals at the same time?
  10. What is the maximum operating temperature of the Analog Discovery 2? Is there an ideal temperature range for accuracy, or is it just recommended to re-calibrate at different temperatures.
  11. Waveforms 3.7.5 and oversampling

    Hi, I have updated WF application and I see that oversampling is performing worse than in previous version. 3.7.5: 3.6.8: Also for higher oversampling values there are visible some levels in the waveform: 3.6.8: Is this physical effect (ex. sample & hold), or a bug? Best wishes for everyone. PR
  12. Hi, I am recently developing system using Altera FPGA's that is featuring A/D and D/A converters. I want to use the AD2 for debugging, but as soon as I plug original Altera USB Blaster and AD2 into my PC (they are not connected using hub, I tried even plugging one device to USB3.0 and other to USB2.0 port, as well as connecting one of them to separate ports using PCI-express USB extension) both USB Blaster and AD2 stop working... Kind regards PR
  13. Hi, First of all I think an averaging option is what we really needed Thank you @attila Unfortunately the option is not available when triggering from source other than Channel 1/2. I think the option should be available in all triggering modes - user have to be aware what can cause averaging with selected trigger option, and have an ability to turn it on or off - not having restricted access. (for example triggering one AD2 form CH1, then triggering second AD2 using external trigger - I have no ability to run averaging on second AD2...) @attila- is there something that can be done in future releases? Or is there a trick to have averaging with these trigger options? Kind regards, PR
  14. Hi, I was playing for quite a bit with single AD2 and I find it great tool. Now I have two devices and I successfully connected them using triggers to have 4 analogue channels in scope, but i have to use two scope windows, with separate timebase... I have noticed other users' therads: It would be great if one instance of Waveforms could manage two or more AD2 devices to result in multi-channel scope/generator/etc.Of course user would have to be aware of using separate clock systems on each device, what could cause some problems in specific situations. @attila - is something like that possible in nearby future? Kind regards PR
  15. I have a brand new AD2 that I'm having trouble getting to work on macOS 10.13.x. WaveForms 2015 reports "No device detected", and the "Find Devices" button also fails to show my AD2. The Mac is a MacBookPro13,1 [MacBook Pro (13-inch, 2016, Two Thunderbolt 3 ports)], the new type with the USB-C ports, but without the Touch Bar. The AD2 is connected directly to the Mac using the USB cable that came with the AD2, using a pretty generic USB-A-to-USB-C adapter. The device appears on the USB in System Information, and browsing the I/O registry, an instance of the com_digilent_driver_DigilentFtdiDriver class has been instantiated at the corresponding node in the tree. Attaching the device results in the following log messages from the driver: default 06:34:22.398724 -0800 kernel Digilent probe8: initial probe score = 100000 default 06:34:22.398748 -0800 kernel Digilent probe: Manufacturer Name = Digilent default 06:34:22.398919 -0800 kernel Digilent probe8: final probe score = 100001 default 06:34:22.398937 -0800 kernel Digilent Starting interface 0 Detaching the device: default 06:39:37.691288 -0800 kernel Digilent Stopping interface 0 There are no /dev/tty.usb* device nodes. I don't see any errors in the system log. I'm using WaveForms 2015 v. 3.6.8, and installed the 1.1.0 driver.
  16. Hi All, I am having trouble with the Waveforms SDK (using the VBA DLL wrapper), where in I am trying to load more than 500 samples from the AnalogIn instrument on the Analog Discovery 2. Any samples above the 500 first samples are empty. This is using the single acquisition mode. Is there a way to get more than 500 samples per Acquisition, as the buffer is set to around 8k. If not, what is the buffer size there for? Regards, ELy
  17. AD2 I2C via C++

    Hi, I've created a custom software program in C++ that uses analog discovery 2 and I have two questions. 1. I want to read some data using I2C interface, but I'm having trouble on the idea of how should I set up a "typical I2C" interface in C++. Is there an example anywhere on how exactly can this be accomplished in C++? 2. When reading the on-board temperature value in C++ I keep receiving a constant value if I'm doing multiple reads in a row. How can I fix it so that every time I read the AD2 on-board temp value I would get an updated temp value not the initial value? Thank you!
  18. Hey Everyone! I've been playing around with the AD2 for the past week or two and I'll have to say, I'm impressed at the bang for the buck here. However, in its current state, it seems to be a tool for hobbyists and tinkerers (which is great!), but can be lacking for creating a really sophisticated control system. I was wondering if it is possible to scale up the number of ADC (specifically) by making use of the trigger I/O pins in a daisy chain fashion to create maybe a 10 ADC channel system (5xAD2). I'm not sure it is available (or I just did not Google hard enough) but it would be great if Waveforms 2015 could interface multiple AD2 in a single script. This would allow a syncing up to the 5 AD2s allowing all data collected from each AD2 to be used in the script to adjust certain aspects of each AD2s outputs. Is this possible, within Waveforms 2015 or would I need to move to a custom piece of UI to handle this? If it is the latter are there any good resources? I'd rather not invest the time to start from scratch...
  19. Is there anyone that has a direct link to download just the USB drivers for the Analog Discovery II (not part of Waveforms 2015)? We are having driver issues on Windows 10. We've tried every other solution that we could find on these forums. (Manually pointing to the drivers, rebooting, reinstalling waveforms including the Adept Runtime, etc.) We are looking for JUST the drivers that someone from tech support can send us while trying to fix this problem.
  20. I am trying to figure out exactly what components on the Analog Discovery 2 are/contain non-volatile memory. I see that there is the calibration memory which must be NV because the user can re calibrate the device (I'm assuming that you don't have to do this at every power on, I may be wrong). Is this calibration memory Non-volatile? Are there any other IC's on the board that have NV memory on them? Are there any other NV memory IC's on the board? I saw that in the Analog Discovery 2 reference manual, you guys provide schematics of all of the functional parts of the Analog Discovery 2 device (i.e. ADC - analog section, ADC - digital section, etc.). I was wondering if there was a place I could find the full schematics for this device or at least a full BOM that I could cross reference each IC to and determine whether or not each component has NV memory. In our lab, anything that has any form of NV memory creates complications for us and I would need verification that this device does not in fact have any NV memory, or, if it does, I need to know exactly where on the device this NV memory resides and how it is written to if we are going to use these in our lab.
  21. USB Isolation

    Does anyone know if there is available for USB 2 with the Analog Discovery 2 isolation, that will operate at high speed (480 Mbps)?
  22. Hi, I've noticed a strange behaviour with my AD2. Doing some measurements I noticed that I read lower values on the AD2 and on my good old Tektronix 466 CRT scope, with 10x probes. I decided to investigate the issue and noticed that I had a significant difference on the AD2 between using no probe and a 10x probes. Without probes I used AD2 BNC adapotor + BNC>banana + hookup wire, and with 10x probes it was Tektronix P6106 and Tektronix 010-128. I used 2 different probes to make sure the probe isn't part of the issue. For example with an external 50R waveform generator I get 5VRMS without probes and 4,01VRMS with 10x probes for the same genertor setting. That's nearly a 20% difference ! I then put a 1M series resistor, without probe and with the same 5VRMS setting of the generator. I get a 2,07VRMS reading, which means the input resistance of the AD2 is about 706k instead of 1M, and that's what causes the error. I get the same results on both channels. I didn't find any reference on that issue on the forum. Can someone else that owns an AD2 do that test ? Do I have a faulty device ? Thanx in advance. Best regards. Eric B
  23. Hello All, We currently have the Discovery 2 in lab and use Waveforms to collect data. Is there anyway I can build a UI( think a simple form, name , value pairs ) into waveform to capture meta data while collection a sequence of scans ? I would like to embed the data into the scan file header or maybe in a txt file that I can write into the directory where the data is being written. Thanks so much for your help ! PS: I see that Matlab Supports the first version of the card, but nothing announced for version 2 https://www.mathworks.com/hardware-support/digilent-analog-discovery.html
  24. 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
  25. Regarding the oscilloscope on the Analog Discovery 2, is there a maximum amperage the device can handle? I am looking for an oscilloscope capable of looking at the output of a motor driver. While the driver's output is lower voltage, the datasheet says it can be anythere from 0.5-7.5 A per phase of output. If I want to look at one phase, will this level of current damage the Analog Discovery 2 in any way? Or can this device handle the task at hand? Thanks