07-21-2010 05:29 PM
Hi Adam,
with the last program you gave us, these are the outputs we get.(see attached)
The first iteration is good, but when it changes frequency, the output becomes wrong.
We were able to bypass the problem by selecting "Start this step after previous generation step" in the execution control tab of the DAQmx acquire step.
All the outputs became similar in duration to the first iteration.
Thanks for all your help.
Regards,
Gary.
07-22-2010 10:12 AM
Hi Gary,
I am glad to help, although I am not too sure I did much other than address the triggering issue 🙂 I was able to run the SigEx project without an error and got data output without any hang-ups. Nevertheless, I am glad it is now working for you, and that is a good approach by selecting the start this step... option. Best of luck with the rest of the application.
Best,
07-22-2010 11:08 AM
Hi Adam,
I'm wondering whether our previous problem (not the trigger issue, but the issue of output cut) comes from SignalExpress or from our card. Have you tested the file I posted in the message #8? There is no error during the execution but the output signal is cut as Gary illustrated before.
Best,
Guillaume
07-23-2010 03:38 PM - edited 07-23-2010 03:39 PM
Hi Guillaume,
When I open the project form example 8, I can only output one sine wave. This is because we are using the "N Samples" mode, , and using the waveform settings without specifying enough sample to write.
I made the following changes in order to output a longer waveform.
1. Continuous Generation Mode with Use Waveform mode
2. Sample to Write = 55.055k = 5001*11
3. Advanced Timing»Do not Allow regeneration: Try changing this around if you would like, it gives a warning because it gets overwritten, but it might give you the desired result if it does regen.
I was able to validate that it output the signal for just over 4 seconds and it changed the frequency is 500ms chunks.
File attached.
Best,