Digilent Analog Discovery acquisition question

[AJ3D]

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.

However, I have had the AD2 trigger and get stuck in the "Running" state until I provide a second trigger.

Very p

[Bob_Schor]

There's no code provided, nothing that shouts "LabVIEW".  What does Digilent say about their software?  If you have a LabVIEW question, post your LabVIEW code (no pictures, please) and we might have something useful to suggest.

Bob Schor

[AJ3D]

Hi Bob,

Please see attached VI. Digilent has not replied yet.

It's a simple state machine where each state initializes, configures, and runs the AD2 Oscilloscope.

It seems that every time I supply the input trigger condition, my VI gets stuck in the "Read & Save Data" state when the DWF MSO Read vi is called until I supply it with a second trigger.

So basically I have to supply it with 2 triggers for each complete loop.

I'm stomped!

Thanks

[Bob_Schor]

Sorry, there is so much "missing code" and so much "magic functioning" (the function of the missing Status function is unclear, nor is the presence of a "trigger" obvious).  This would probably benefit by having someone with some LabVIEW experience come and take a look at your code, running on your machine (so they could ask questions and get LabVIEW "Help" for some of the Digilent functions we can't see).  The first thing you should explain is what it is you are trying to do.  The code shows how you are doing things (things which are not that clear to me, as I don't know what the missing functions do, nor what their responses signify), but the "what" is not obvious.

A useful thing might be to put LabVIEW away for an hour, and spend the time with Microsoft Word (or your favorite Word Processor) writing some Documentation about what you are trying to do (don't describe, at all, how you are doing it).  Read it, see if it makes sense, show it to your Significant Other (or teenage child) and see if it makes sense to them.

Bob Schor

[AJ3D]

Bob,

Digilent got back to me. There was a bug in their DWF MSO Query Acquisition Status.vi which would cause the AD2 device to be re-armed when queried. 

They provided a fix (v3.13.20-2) and all is good now.

Thanks