Search the Community

Showing results for tags 'Analog Discovery'.



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
    • 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 113 results

  1. i have an Analog Discovery Oscilloscope, and normally use it with BNC connectors, but now wish to use it with a breadboard, so i'll be using the connector that comes with the 'scope. Unfortunately, all the wires leading out of the connector end in a female connector. Where can i get single header pins to turn the female connector into a male connector to plug into a breadboard? i've tried looking this up at Mouser, but all i see are 5 or more pin headers. i suppose i could break the 6 pin headers that came with the scope into 6 single pin headers, but i'd rather not be destructive if i can help it. Any thoughts or suggestions?
  2. I have the Analog Discovery with the NI Circuit Suite and "Virtual Instrumentation Suite (NI Elvis MX)" which I purchased while taking a class from UT-Austin. In my latest class, the instructors use NI Elvis with the myDAQ. Can Elvis be used with the Analog Discovery?
  3. I recently purchased the PmodMIC to use with my Nexys 3 board and Analog Discovery. Finally after a bit of coding, I seem to have gotten it to run continuously, but I have just a few questions. In the PmodMIC reference component PDF, it states: The VHDL component is an entity named PmodMicRefComp which has five inputs and five outputs.The input ports are a 50MHz clock,.... (BTW, I think the 5 inputs, 5 outputs thing is a typo ). But my first question is: 1) Is it possible to lower the sampling rate? Apparently the 50 MHz input clock gets divided down to 12.5 MHz inside the PmodMICRefComp. I need to record some audio data, but certainly not at 12.5 MHz! I am not sure why any audio source would ever need to be sampled that quickly, but in any case, I attempted to lower the input clock speed down a bit and my design seems to have failed. I am looking to record signals comprised mainly of human speech, so 8KHz is actually about what I need. The 2nd question is: 2) I see no mention anywhere of the format of the data output by the PmodMIC. It's 12 bits in parallel, but is that signed? unsigned? Couldn't seem to find this in the reference PDF anywhere. If this is an SPI standard convention that I'm just not aware of, sorry for asking. The 3nd question is: 3) In the state machine diagram, is there no transition directly from the "SyncData" state to the "ShiftIn" state? My code currently initiates continuous sampling by checking if nCS is HIGH and DONE is low, as indicated in the SyncData state. Then, it brings the START signal low again to return to the IDLE state, and increments a counter to keep track of the number of samples taken. On the next clock cycle, it checks if START is low, and # of samples is > 1, then pull START highagain, repeating the process. What I am wondering is: Instead of pulling START low to return to IDLE, would it not just be possible to keep START high and have nCS get pulled low again? I suppose this would need to be taken care of by the PmodMICRefComp VHDL code since that is the driver for the nCS signal after all. It would be nice if that provided VHDL component had a single bit control signal that allowed for selecting ONE TIME conversion and CONTINUOUS conversion. Thanks for taking the time to read this.
  4. Everyone, one of our customers - UMass Lowell use the Analog Discovery and chipKIT to teach the first year engineering student Intro to Engineering. The professor has put some of the materials online http://faculty.uml.edu/jweitzen/25.108(ECE)/25107Fall.htm Feel free to check it out.
  5. Hello. I was wondering if the digital bandwidth is the same as the analog ? Is it possible to capture a 25mhz spi signal with the logic analyzer or is it also limited to 5mhz ? Thanks !
  6. Would it be possible to Open Source all or part of the Analog Discovery? Since the FPGA is programmed by the Digilent instrumentation software you are one step away from having a development board with many front end interfaces already on-board. The main thing I would be looking at is that it is open sourced enough (or documented enough) that I could use the Analog Discovery as a custom acquisition and/or control board for advanced testing or even prototyping. I know there is an API to access some functionality but could this be expanded to allow even more opportunities to customize the board?
  7. Hello, I plan on using the Analog Discovery oscilloscope to capture data from an antenna, export as a .csv and then import to MATLAB for processing. Is there a limit on the amount of data I can collect using the WaveForms software? To capture more data, I can simply increase the base of the time scale, correct? I want to continuously send a data signal from the antenna and simultaneously receive using the scope. I believe it would be easiest to use the WaveForms software to capture the signal and then export to .csv and then re-import to MATLAB instead of using the MATLAB data acquisition. Is this an accurate claim? Thank you.
  8. Hello. I just received my analog discovery in the mail and want to start using it but before I do I want to understand what things I need to know before using the device. In particular, does the discovery have built in protection for over-current draw and over-voltage? What voltages/currents should never be used? I don't want to fry my new instrument so please tell me all I need to know with that goal in mind. For example, if I shorted the power supply strip or function generator pin, would the device be damaged or does it it have current limiting protectors built in?
  9. Are there any plans to add more interpreters? Can users create their own?
  10. We recently started accessing our Analog Discoveries with custom python scripts. We used to use matlab with direct dwf library calls using matlab's calllib() function, but are finding python to be a much more convenient option. Here is my question: while I can cause the waveform generator to output custom or predefined waveforms and can read them with single shot, PC-triggered acquisitions, I can't retrieve Analog Discovery information such as device type, name, and serial number. Here is some sample code: from __future__ import division from __future__ import print_function from ctypes import * from dwfconstants import * import collections #load dwf library and declare ctype variables if sys.platform.startswith("win"): dwf = cdll.dwf DADinfo['sysplatform'] = sys.platform #print(sys.platform) else: print("THIS IS NOT A WINDOWS SYSTEM") #print DWF version version = create_string_buffer(32) dwf.FDwfGetVersion(version) DADinfo['dwfversion'] = version.value print("DWF Version: "+version.value) #make sure any attached Analog Discovery is in a known state dwf.FDwfDeviceCloseAll() nDevice = c_int() result = dwf.FDwfEnum(enumfilterDiscovery, byref(nDevice)) print("Enum:", result, nDevice.value) isUsed = c_int() result = dwf.FDwfEnumDeviceIsOpened(c_int(1), byref(isUsed)) print("DeviceIsOpened:", result, isUsed.value) hdwf = c_int() result = dwf.FDwfDeviceOpen(c_int(-1), byref(hdwf)) print("DeviceOpen:",result, hdwf.value) result = dwf.FDwfEnumDeviceIsOpened(hdwf, byref(isUsed)) print("DeviceIsOpened:", result, isUsed.value) sn = create_string_buffer(32) result = dwf.FDwfEnumSN(hdwf,sn) print("Serial number:", result, sn.value) dn = create_string_buffer(32) dwf.FDwfEnumDeviceName(hdwf,dn) print("Device name:", result, dn.value) deviceID = c_int() devicerevision = c_int() result = dwf.FDwfEnumDeviceType(hdwf, byref(deviceID), byref(devicerevision)) print("Device type:", result, deviceID.value, devicerevision.value) And here is the output I get when I run this code: DWF Version: 2.7.5 Enum: 1 1 DeviceIsOpened: 0 0 DeviceOpen: 1 1 DeviceIsOpened: 0 0 Serial number: 0 Device name: 0 Device type: 0 0 0 Note that none of the requested information is returned. Any suggestions?
  11. Hi I have a question from one of our customers: Please can you tell me what the system requirements are for a Windows PC to use Analog Discovery? Does it require USB 3.0 to meet the published specifications? Can anyone answer this?
  12. Hi, I have V2.7.5 and an Analog Discovery. 1/ The oscilloscope help mentions Repeated, Scan Screen & Scan Shift Run Modes (section 2.3.3). Where is that selected? I have > 0.1sec/div timebase selected. 2/ The Trigger panel picture in 2.3.4 doesn't look like mine. 3/ Why is my Trigger Type selection disabled? 4/ When is the next update due? Thanks.
  13. Here is a question from a customer. The customer is looking for the datasheet of the Analog Discovery and wants to know the tolerance. Can anyone help on this?