• Content Count

  • Joined

  • Last visited

About [email protected]

  • Rank
    Frequent Visitor

Recent Profile Visitors

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

  1. Hello, I am using the IOSTANDARD = LVCMOS12 directive in my xilinx .ucf file but I notice that CMODS6 IO's are still operating at 3.3V. Is there a way to change that? Does Digilent offer any FPGA modules capable of LVCMOS 1.2V IO's? Thanks
  2. Hello, Is it possible to use all 40 pins as logic analyzer inputs? I can't seem to use anything above pin 31 at the moment. Thanks
  3. Hello, I have a pretty basic question: How do I select between the various LVCMOS I/O levels supported by the DD logic analyzer (eg: LVCMOS3.3 vs LCCMOS1.2) Thanks
  4. Hello, Is it possible to run Xilinx ChipScope on the CMOD S6? Is it done via the USB port? Thanks
  5. Hi Attila, Yes that's how I set trig/1 as the source and the slope but I don;t see how to set the level (threshold). For example, 1.5V or 0.9V. Thanks
  6. Hello, I'm using AD2 with Labview and I am wondering if there's way to set the trigger level for trig/1 or trig/2 inputs. I don't want to use the analog channels for triggering, since I am using them for capturing. Thanks
  7. Any updates on stock and availability of the Analog Discovery 2?
  8. I updated to the latest Beta release of the DWF. My issue got resolved
  9. Greetings, Question about the Analog Discovery: When does the acquisition state transition from "Running" to "Acquisition Complete"? Is it when the internal buffer is full? or is it when the number of samples requested have been acquired? When setting up the MSO timing using the DWF MSO Configure Timing VI, I can specify the Sample Rate and the Acquisition Time . This leads me to believe (I'm guessing) that the condition for transitioning from "Running" to "Acquisition Complete" is when the number of samples acquired has reached the value: Sample Rate x Acquisition Time.
  10. I changed my VI and inserted a MSO Query Acquisition Status between the MSO Run and the MSO Read. I also put an event structure and a loop to check for Stop button in the same loop. This allows me to hold off on trying to read the data from the instrument until acquisition is complete and check for stop button event. I still can't stop the execution with the Stop button on my front panel. I'm just trying to emulate the functionality of the Stop button in the WaveForms app, in which, regardless of the status of the MSO, you can hit stop and halt execution. This should be simple to em
  11. I'm wondering if the DWF MSO Stop.vi function would be able to stop or interrupt the DWF MSO Read.vi function if I invoke it using the same instrument handle from a structure running in parallel. Would it have equal or greater priority? I'll wait for @attila's input. Thanks
  12. Hi JColvin, Yes the DWF MSO Stop.vi is available but I am wondering how to use it once the DWF MSO Read.vi has been called. It seems like once once we are inside DWF MSO Read.vi there's no way to abort or return unless all data has been read from the device data buffer. I'm hoping there's a simple solution that someone can suggest. Thanks!
  13. Hi JColvin, After I hit the Start Button, the execution starts fine and the AD2 waits for the trigger condition. I turned on "Highlight Execution" I noticed that execution is stopped inside the DWF MSO Read vi (see image attached) which is expected since the trigger has not arrived yet. However, I want to be able to interrupt it when I hit the STOP button but it seems like no other event has the ability to interrupt the DWF MSO Read vi (other than unplugging the AD2). Any suggestions?