5142

[madd]

Hello

i have been going through this NI Digtizer help manual  when i came across this flow diagram(attachment) comparing fetch forever example. i have attched a document showing how fetch forever do software triggering and acqusition. But one point i do not understand is where the Send Software trigger Edge block maps on this example. Also any one who can reply to my downconverter external  reply 4. it's been a week no has answered my Question. Might be Questions are much stupid...... ones

Regards

Madd

[Speedy_Badger]

Hi Madd,

The fetch forever architecture is meant to continuously fetch data without triggering (and as a result without reconfiguring). We setup the task as if we were going to acquire a continuous acquistions using a software reference trigger. This trigger is never sent however which will keep the acquisition going. We then fetch a chunk of data from the onboard memory, manipulating the read pointer accordingly to account for each chunk of data we remove. This fetch is then repeated until the task it stopped.

The flow chart you are referring to is similar, but is not the same fetch architecture. In the flow chart you are actually sending your reference trigger via a software control and your fetch is referenced to that point in time, within the determinism of your software of course. Once this trigger is sent, you would need to reconfigure the scope again and wait for another software trigger.

Regards,

[Chris_W.]

Hello Madd,

Because your question on this post is the same as on other threads, we would like to consolidate your posts to one thread so that everyone who is interested can follow the progress of your issue. All further activity on this issue will continue on thread linked HERE. Thanks.

Chris W