Search the Community

Showing results for tags 'triggering'.

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

  1. I build radar systems for a living, and I'm testing the Analog Digilent 2 as an A/D, timing control for other RF hardware, RF switch control, trigger source. Here's what I need to do: Write the software with python using the Waveforms SDK running on Windows 10. Acquire signals on 2 analog channels simultaneously. This must be triggered at a periodic rate on an input other than the two analog in channels. Generate a pulse width of p nanoseconds at an x kilohertz rate. This is a TTL signal. This pulse is used for RF pulse generation, but also as a trigger fo
  2. Hello again! I'm trying to use the AD2 to act as both a signal source (wavegen1) and a measurement (scope1) device for the purpose of tracking conduction delay of the signal. Currently, I simply have the wavegen1 connected directly to scope1 with 3 cycles of a sine wave being put out. I am aware of the measure command to find the maximum on my scope1 but I was wondering if there was a way to find N (3 in my case) maximums AND find the corresponding times with respect to the timing of wavegen1? I plan to assume the timing of the wavegen1 is relatively accurate to my input frequency and c
  3. Hello, I think the latest waveforms software is fantastic. However, I still have a problem with triggering, specifically protocol triggering. In the enclosed screenshot, I have a UART and OneWire and a SPI protocol decoder. If I choose Simple triggering, everything is ok, but if I choose Protocol-UART-TX-GPIO1 (UART decoder form the Protocol selection button pull down menu) then the OneWire and SPI decoders trigger-selection-arrows switch too! What I would like is that I can only choose the UART OR only the OneWire OR only the SPI decoder as suggested by te Protocol selection button pull
  4. I seem to be having trouble getting the AD2 to trigger on a repeated pulse. If I trigger on the edge of DIO 7 then it triggers OK (see logic_trigger_simple), problem is that power up sends spurious signals sometimes and so I'm tring to pulse on the counter. I have the counter set up as the other screenshot but it just will not trigger like that. There is no reset so I've set reset to DIO 15 which is unused and tied to ground. How can I get this to trigger on the number of pulses. Also, in the protocol triggeringl, is there any way to trigger on a sequence of hex val
  5. Hi, I am working for an instructional laboratory where we have a number of the Analog Discovery devices that we are using as oscilloscopes. Our primary issue is triggering? We have some experiments that require at least three scope inputs and a waveform generator. We are trying to get two of the devices to sync nicely with each other using the in/out triggers, to trigger two scopes simultaneously. Much to our surprise, we found that the wavegen trigger out, is simply high when running and low when it is not as opposed to the standard TTL sync out found on most devices. Is there a
  6. Hi, I have an analog discovery with the 2015 firmware, 3.2.6 on a 64bit machine. I need to trigger on a waveform(a good solid edge, like a reset deassert), then zoom in on a glitch about 450ms post trigger. By "zoom in" I mean expand the timebase so I can see the nature of the glitch. With the single timebase setting, there is inadequate granularity to see what might be going on. See attached pic. Can analog discovery do this? If so, how? if a different product is needed, please suggest it. thanks, tim