Jump to content
Sign in to follow this  
Ton Plomp

Periodic Trigger: Maintain Phase

OpenG Periodic Trigger  

7 members have voted

You do not have permission to vote in this poll, or see the poll results. Please sign in or register to vote in this poll.

Recommended Posts

I have added feature request to the OpenG tracker for this functionality.

Some detail on the code change is in this discussion.

This review has the following options:

  • Do not add a 'Maintain Phase' input
  • Add a 'Maintain Phase' input, defaults to 'False' (means that we don't need to deprecate the old code)
  • Add a 'Maintain Phase' input, defaults to 'True' (means that we need to deprecate the old code)

Please add your vote (it's public voting), if you have input for this discussion please add it!

Share this post


Link to post
Share on other sites

I haven’t used this function, but I’ve done similar timing, and I find that both forms of timing ("since last", and “on schedule”) are both needed. There is no reason to prefer one over the other as default, and thus it would be simpler to stick with the current behavior as default, with the new one as an option.

Share this post


Link to post
Share on other sites

I added another 'mode' for this VI:

  • Maintain phase, dismiss missed

To show the effect of the three modes I made this table (with a dT of 50 msec), all times are in msec:

post-2399-0-94357900-1351955966.png

Graphical this is the representation:

post-2399-0-67588400-1351956011.png

Now for the difference between 'Maintain phase' and 'Maintain phase, dismiss missed' some more zooming in:

post-2399-0-90174100-1351956135.png

Where at 3.35, 3.36 and 3.51 a call was made.

All three models will return a True for the first call (the wait time before was > 500 msec).

When 'Maintain phase' is selected 3.36 returns a True as well, (the wait time was > 1000 msec).

The 3.51 call returns True for the 'Maintain phase' and for 'Maintain phase, dismiss missed', since the phase is stuck at 3.50. 'Since last' returns a False since the time since the last trigger is < 500 msec).

Here's my current VI:

post-2399-0-60739200-1351957411_thumb.pn

post-2399-0-63964800-1351957453.pngpost-2399-0-07430900-1351957485.png

Periodic Trigger.vi and the test VI Periodic TriggerTest.vi

so you can run your own scenarios.

Ton

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...

Important Information

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