Trying to reset 'Analog SW Trigger.VI' after occurence of trigger

[cincidude]

Hi,

I am using 'Analog SW Trigger.VI' to trigger data acquisition via software, which works fine. I'm using a scan rate of 200 samples per second. The data acquisition using the software trigger works fine. However, once the trigger is encountered, I would like to reset the trigger (the VI) so that on the second occurence of the trigger, the VI should be able to detect it again.

Presently, on the first occurence of the trigger, the acqusition starts fine, but the trigger is not reset and the second and all trigger occurences hence forth go unnoticed.

I have attached my main VI below (Data_collecting_V8_MultipleFlexTrigger.vi). The sub-vi for the software 'Analog SW Trigger.VI'

[e-Cash-Money]

Hello cincidude,

I think I have figured out how to modify the Analog SW Trigger Vi to be retriggerable.  All I did was set the "Triggered?" input to always be false and set the "Force Restart" input to always be true.  I have attached my modifications in the code attached below.  It seemed to work accurately when I tested it.

[cincidude]

Hey E.Lee,

Actually I remember trying this out, but maybe I missed out something. Anyhow, your VI seems to be compiled in 7.1 and I have problems opening it in LabView 7.0. Is there a chance that you could compile it in 7.0?

Thanks,

-Sachin

[e-Cash-Money]

Hello Sachin,

Here is the same program saved in LabVIEW 7.0!

[cincidude]

Hi E.Lee,

Thanks once again. However, I have noticed that I get erroneous triggering sometimes using this VI. I have set a 'level = 2.5' and windo amplitude to 0. The condition for triggering is rising edge. I notice that inspite of the signal being high, the VI triggers data acquisition. Could it have something to do with the 'window amplitude' which is set to o?

Please let me know if you have any insights.

Thanks,

-Dude

[e-Cash-Money]

Hello Dude,

Analog window triggering and analog edge triggering are two different types of triggering.  If you have the condition set to "Rising Edge" the VI might not be using the value you put in for the window ampiltude.  However, it might be using the Window Ampiltude control to get a hysteresis value to apply to the rising edge trigger.  My guess is that it is the latter.  Setting Window Amplitude to zero should have the same affect as doing a normal rising edge trigger, so I don't think that the behavior you are seeing is related to that.  The nice the about this example is that you can open it up and see how the algorithm is implemented.  One thing I would like to let you know is that the "trigger" is a actually just a trigger to tell LV what data to display and when to display it.  The actual program is acquiring data continuously.  This means that you could impelment your own algorithm that goes through the data and checks for certain conditions being met!