Exporting Triggered Data in Sequencer
I'm a relatively new user to DEWESoft, so forgive me if this is an easy answer.
I have a workspace that uses start and stop triggers to acquire and store data. The triggers are set up to only record fast, and not record when the triggers are not active. I have the storing set up to save a new file after every 1 trigger, and the multifile set up to append date and time to the filename.
I have a sequence that launches this workspace, and starts the acquisition. If I try to export after I detect a StopTrigger, the exported file has no data (is empty, except for headers in some cases). If I wait for StartTrigger, then delay for a few seconds and manually stop the recording, export works.
From trial and error, it seems as though if storing is not active when the export occurs, the recorded data is not exported. If storing is active, the data is exported.
To me this doesn't make sense. If I open the saved data file (that the export didn't work on), the data is there and I can manually export the data.
Is there any trigger based work around here?
the sequence that you have created should work, but problems can appear if the trigger levels for starting and stopping storing happen in the same moment. For example, if the trigger for starting storing is a voltage level of 2 V, and the trigger for stopping storing a voltage level of 5 V, and the input signal is quick peak of 6 V, this could mean that both triggers are activated at once. You can see an example of this in the attached image.
Because the sequencer is a bit slower in its reaction time that the setup itself, it gets stuck on the stop storing block, waiting for a stop trigger, even though it already occurred.
Please check if this is also happening in your setup. The result of this is an empty exported data file since acquisition started and stopped in the same millisecond.
One solution to this is to use a time condition for stopping storing, or define the stop storing condition in such a way that it will never happen in the same moment as the start condition. I'm also still awaiting on a developer's response to see if there are any better solutions available.
I appreciate your quick response. I've attached a few more images below. I'm almost certain that the stop trigger is not happening right after the start trigger as they are both position based and very far apart. I'd rather not use a timed approach as then I would have to either edit my sequence or my trigger based every time I change velocities with what I am measuring.
I'm not quite sure why the start and stop triggers don't show up on that screenshot, but the start trigger occurs when the position transitions from less than -100 to greater than -100, and the stop trigger occurs with the position transitions from less than 0 to greater than 0.
thank you for the additional information you have provided. It looks like that you're experiencing a different kind of problem.
In order to be able to reproduce this on our end, we would ask you if you can please provide us also the setup and sequence files. After we review these files, we should be able ti give you a better solution. If you don't want to share them on the public thread, you have the alternatives of uploading them to either the private forum or sending them to our [email protected] email.
As a side note, the reason that you're not seeing the notices is because the sequencer turns that option off by default. By checking the first check box (see the attached image) you should also be able to see the missing information on your screen when running a sequence.
I've sent an email to Support containing the setup file and the sequence file. Thank you!