Hi Chris,
Thank you very much for your help.
As you suggested, I've tried niTuner Simple Acq Example with niScopeConfigureTriggerEdge added.
This was a success.
I've analysed differences between the two softwares and in fact it seems that my problem comes from the use of analog demodulation (Modt.lfp).
If, in the Simple Acq Example, min data length is an input, in my software it is the result of an operation with acquisition duration and so on.
What is done in my software :
1. niTuner_init
2. niScope_init
3. niTuner_ConfigureReferenceClock
4. ModtCreateSessionHandle
5. ModtInitRecieverInfoForRFSA (associating Modt, niTuner and niScope configuration information)
6. ModtConfigDownconversionSettings (getting data length)
7. niScope_ConfigureHorizontalTiming (using data length)
8. niScope_ConfigureTriggerEdge
I've tried to run this software without line 5 => line6 returned an error and data length was set to 0.
I've went on executing code with data length manually set to 100385 (a value I often have in my application) and line8 (trigger) was successfully executed.
So I can tell that error comes from the use of ModtInitRecieverInfoForRFSA. But I think I really need this function.
I hope my problem becomes more easy to understand, and then to solve. 🙂
Best Regards,
Hervé MALLET