Jump to content

CraigC

Members
  • Posts

    54
  • Joined

  • Last visited

Community Answers

  1. CraigC's post in Quick and dirty way for optional dependency in source code? was marked as the answer   
    I believe you can edit the custom symbols found in the project / application. found here
     
    http://forums.ni.com/t5/LabVIEW/Programmatic-read-access-to-project-symbols/td-p/505952
     
    Thus it might be possible to launch via a splash  screen and set this symbol if the plugin is found? Just a though
     
    Craig
  2. CraigC's post in Basic level trigger detection not working as expected was marked as the answer   
    Hi,  I have tried to make a scenario to explain this better.  The main use of reset is to reset between samples or to "Stitch" together samples when in continuous mode.
     
    In the Scenario Continuous Acquisition With Reset off the VI stores the last Array value in the 1st Sample (White) and uses it as the first Array Value in the 2nd Sample (Red).  This effectively "Stitches" together the white and red waveforms in the graph.  This helps with data processing as there is no erroneous data point in between samples.  although not that important in the time domain it can really skew frequency type stuff.
     
    In the Scenario Single shot Acquisition I have emulated a time delay between samples.  With the reset off we can see that the VI attempts to "Stitch" together the white and red waveforms and we end up with a flase trigger.  Hence when using single shot sampling or using the same vi to sample different waveform we would want to always reset this VI in between calls.
     
    This is illustrated in the scenario "Trigger Single shot with reset On"
     
    Craig



    Trigger Reset.vi
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.