LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Trigger Detection for 1 Channel.vi detects the wrong edge

Solved!
Go to solution

I was expecting the "Trigger Detection for 1 Channel.vi" to return the time of the first rising edge, instead for the signal in the attached VI, it returns the time of the second falling edge.

 

I have manually placed cursor 0 on the expected result.

Cursor 1 is the actual result.

 

Thanks in advance for your suggestions.

0 Kudos
Message 1 of 3
(230 Views)

First off, I would like to say that you did an A+ job of presenting the problem.  Extremely easy to play with and try various things.

 

I can't find the exact reason but there was one thing I did find, and that is if you set it to something that has no trigger at all (like a level of 1.5, for instance), it outputs a trigger location of "2.2052E-6", which is almost exactly what your value is off by. 

 

Changing it to "index" mode instead of location reveals that it is detecting the trigger correctly (index 282 is found, which is 112.8, almost exactly what your manual cursor is set to).

 

I still can't figure out why it does this and I can't spend more time on it, but somehow it's got an incorrect timing offset added.

0 Kudos
Message 2 of 3
(193 Views)
Solution
Accepted by DM83

Got it working by resetting the t0 to 0

santo_13_0-1719367034978.png

santo_13_1-1719367045944.png

 

 

Santhosh
Soliton Technologies

New to the forum? Please read community guidelines and how to ask smart questions

Only two ways to appreciate someone who spent their free time to reply/answer your question - give them Kudos or mark their reply as the answer/solution.

Finding it hard to source NI hardware? Try NI Trading Post
Message 3 of 3
(173 Views)