clf

Members
 View Profile  See their activity

  • Content Count

    47

  • Joined

  • Last visited

Community Reputation

2 Neutral

See reputation activity

About clf

  • Rank
    Frequent Visitor

Recent Profile Visitors

1611 profile views
  1. clf
    Thanks @JColvin. Can those additional copies be installed on other computers? The wording of Section 5 of the EULA is a bit confusing to me. Chris
  2. clf
    1) How frequently should an Analog Discovery 2 be recalibrated? 2) Can devices be sent to Digilent for recalibration, or can Digilent recommend a calibration lab? Thanks in advance! Chris
  3. clf
    The EULA presented during installation of the WaveForms software indicates that only one copy of WaveForms is permitted to be installed per hardware product. How can additional WaveForms licenses be obtained? Thanks in advance! Chris
  4. clf
    Bought an additional AD2. USB cable fit perfectly, could definitely feel it snap into place.
  5. clf
    Hello @attila, Could you kindly cite a source for your above statement "BNC is 'by definition' single ended", please? I offer the Tektronix THS720 oscilloscope [1, page "1-2"] as a particular counterexample, and the Tektronix Application Note "Fundamentals of Floating Measurements and Isolated Input Oscilloscopes Application Note" [2] as a general counterexample. From my perspective, it's much more desirable to have a versatile instrument that maintains its differential channels all the way through: you can easily reconfigure them to have a common ground by tying their "-" inp
  6. clf
    @peter64, please: 1) post a photo of your entire setup that clearly shows all connections 2) post a photo of the switch settings on your uCurrent Gold 3) indicate the range of resistances your sensor is expected to produce - Chris
  7.    JColvin reacted to a question: USB 3.x for Analog Discovery, Digital Discovery
  8. clf
    When is Digilent planning to release Analog Discovery and Digital Discovery variants with USB 3.x support? I'd love to see higher streaming rates in these devices. Thanks in advance, Chris
  9. clf
    As a general rule of thumb, you can resolve the errors by resolving the associated problems. For a more descriptive answer, please post a more descriptive question. Chris
  10. clf
    Thanks @attila. I was looking at a time scale that was off by orders of magnitude. I hadn't realized the frequency parameter had different meanings for "funcCustom" (frequency = repeat rate of waveform) versus "funcPlay" (frequency = sample rate). This fact is mentioned, though, in the the SDK Reference Manual's entry for FDwfAnalogOutNodeFrequencyInfo(). For anybody curious, I've attached Waveforms 2015 oscilloscope screenshots of the AWG "funcCustom" and "funcPlay" renderings for the same sample vector. Screenshot "awg_custom_[...]" was produced using the "analogout_custom" C sample
  11. clf
    Hello All, I'm playing around with the "analogout_custom" C sample program that comes with the Waveforms SDK (/usr/share/digilent/waveforms/samples/c/analogout_custom.cpp). I've made some observations that don't align with my expectations. I'm hoping one (or more) of you could kindly offer some insight on what is happening. I'm running libdwf.so.3.4.7 on an Ubuntu 16.04 x86-64 machine. I have an Analog Discovery 1 and an Analog Discovery 2 wired such that ad1.aout1 --> ad2.ain1+ ad1.gnd --> ad2.ain1- I'm playing the waveform out through the Analog Discovery 1
  12. clf
    I've posted a makefile for building the sample programs at: https://github.com/cfeyer/cfeyer-makefile-dwf-c-samples-project/ Chris
  13. clf
    I've created a project on github at https://github.com/cfeyer/gr-dwf-analog-discovery-2-community-project Chris
  14. clf
    Looks like I've been writing "GNU Radio" wrong (it's not "GnuRadio"). Also, here's their code style guide: https://wiki.gnuradio.org/index.php/Coding_guide_impl
  15. clf
    @fusionimage, From Gqrx's design documentation at [1]: Gqrx is heavily based on GNU Radio using both DSP blocks as well as its famous runtime engine. [...] At lowest level we have various DSP and I/O blocks. These can be blocks from GNU Radio, gr-osmosdr or even implemented in gqrx. You've mentioned GnuRadio and Gqrx by name as desired applications. It's looking like we can satisfy these use cases by implementing a plain ol' GnuRadio module for the AD2. Chris [1] http://gqrx.dk/doc/gqrx-design#more-136
  16. clf
    @[email protected], you were correct when you previously stated that we'll need a "sync" block. Both source and sink blocks are implemented in code by inheriting from the "gr::sync_block" class. From [1]: "Sources and sinks are derived from gr::sync_block." Building on my previous post, we'll want to start by implementing: an "Analog Discovery 2 Analog Source" class that inherits from GnuRadio's gr::sync_block class, configures its gr::sync_block with an I/O signature of one 16-bit integer output, and sources its stream from one of the AD2's analog input channels an "Analog Discovery