blindgoat

Members
  • Content Count

    7
  • Joined

  • Last visited

About blindgoat

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks a bunch, attila. That was exactly what we needed to know.
  2. We are currently using an AD2 as a data acquisition device in a configuration in which an external trigger is delayed by the DigitalOut device and then routed to one of the AnalogIn channels to trigger the latter. The DigitalOut generates its trigger on digital i/o line 0. We now wish to use some of the other digital i/o lines for simple i/o. The question is can we do both things at once: namely, trigger digital i/o channel 0 with the DigitalOut device while using digital i/o lines 1-15 as simple Digital I/O devices? Our guess is that we can use lines 1-15 for digital input but not digital output. We'd very much appreciate any insight into this issue.
  3. Exactly what I need to know. Thanks for the helpful answer and the capable hardware.
  4. We're using an Analog Discovery 1 as a delayed-trigger oscilloscope. We route the incoming trigger to the digital pattern generator, delay it by a user selectable amount, and send the result to the analog scope channel two as a trigger. This allows us to sweep the 8192 sample buffer of the analog scope along a repetitive trace and capture more samples, one buffer at a time. Our question is about the accuracy of the digital pattern generator's wait state. Is the wait delay determined by counting down from a clock? If so, which one? The 100 MHz master clock? Does that mean you have implemented a 36 or 37 bit counter in the system, in order to reach one day (86400 seconds) with 10 nS precision? We'd really appreciate any information on this topic. Right now we're not relying on the wait state out of uncertainty about how it's determined. If we could use wait, it would make our lives and our code nicer Thanks.
  5. Searched for this issue but couldn't find any earlier queries. I've just installed the software tree up through waveform3 on a debian box. Dwfcmd returns nothing when I run it as an unprivileged user but gives the correct result (finds the Analog discovery) if I run it as root. Same is true for my python scripts that access the AD. Is there anything I can do to be able to access the AD as a normal user? Thanks. O/S details are: Description: Debian GNU/Linux 7.9 (wheezy) Linux debian73-Iguana 3.2.0-4-686-pae #1 SMP Debian 3.2.73-2+deb7u2 i686 GNU/Linux libc is 2.21
  6. The Analog Discovery SDK has a number of functions for sampling and reporting "noise." I cannot tell from the documentation what the noise refers to. It appears that the length of the noise data is 1/16th the length of the analog sample data. Is it simply a way of doing min/max samplings on the regular analog data? Is there a discussion of these functions somewhere? I'd be most grateful for any further information on this topic.
  7. I'm using the python version of the Analog Discovery SDK to directly access the device. When I interrogate the device for its analog input ranges, it tells me that it has two: 5.0 and 50.0 volts. If I run the Waveform software I see many more possibilities, many decades of 1-2-5 steps. A 14 bit adc with an input range of 5V has a step of about 300 uV. From this I infer that the extra resolution Waveform provides is not simply a matter of zooming in on the 5V range. Does anyone know what's going on?