iDetect

Members
  • Content Count

    4
  • Joined

  • Last visited

  1. From attila: I'm planning to add support for lower latency captures with Analog Discovery, but it will take some time to implement it. The AD2 is a near-perfect device for embedded solutions in the RF world. Higher transfer rates would make it perfect! If it helps at all, our transfer needs are as follows: Samples per trigger event are 1000-4000 per analog channel (simultaneously triggered); trigger rate per second = 4000-12000 (4000 would seal the deal, but higher would permit it to work with more product line); Data rate must be sufficiently high to a PC array
  2. Thanks for the comments and information. The 1 MHz sustained transfer rate matches what I empirically found. We are going use the AD2 as a test instrument. I'm expanding the code to use it for triggering our radar systems and generating pulses during production builds. xc61x45's suggestion above is VERY similar to another project underway. We do like to use off-the-shelf solutions when we can, though. The software and hardware are more sustainable as the manufacturer takes on the responsibility of software expansion, and end-of-life issues on components. It's often worth
  3. 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