1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 <2009> 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 <2009> 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: state notation code flags |
From: | Patrick Thomas <[email protected]> |
To: | Mark Rivers <[email protected]> |
Cc: | [email protected] |
Date: | Fri, 02 Oct 2009 22:37:18 -0700 |
Mark Rivers wrote:
The pvPut command did "finish" before the efClear command was executed. That means that it wrote its value to the record, and processed that record and any records that process as a result of processing that record. That record told channel access to send out monitors on that PV to all clients, including your SNL program. It does NOT wait for those monitors to be received; it simply requests channel access to send them, which is then done asynchronously. So the event flag in your SNL program will be set some time after you do the pvPut. What you are observing is the expected and documented behavior of EPICS. MarkI think I have figured it out, the following code shows it the most clearly. Adding SYNC to the pvPut command does not seem to ensure that it will finish before the next command is processed:________________________________ From: Patrick Thomas [mailto:[email protected]] Sent: Fri 10/2/2009 7:03 PM To: [email protected] Cc: Mark Rivers; [email protected] Subject: Re: state notation code flags I think I have figured it out, the following code shows it the most clearly. Adding SYNC to the pvPut command does not seem to ensure that it will finish before the next command is processed: program sncTest float request_maximum_velocity; assign request_maximum_velocity to "H3:TEST"; monitor request_maximum_velocity; evflag request_maximum_velocityEvent; sync request_maximum_velocity request_maximum_velocityEvent; ss ss1 { state init { when () { efClear(request_maximum_velocityEvent); request_maximum_velocity = 40; pvPut(request_maximum_velocity, SYNC); efClear(request_maximum_velocityEvent); } state wait } state wait { when () { if (efTest(request_maximum_velocityEvent)) { printf("flag set\n"); } } state wait } } Pete R. Jemian wrote:
sounds a bit off ... show the code Patrick Thomas wrote:I think I have it narrowed down. It appears that when I set variable1 equal to variable2 and variable2 has a flag synced to it (variable1 does not), and then do a pvPut on variable1, sometimes the flag is set on variable2 and sometimes it isn't. Am I correct? Why does this occur? Thank you, Patrick Mark Rivers wrote:Patrick, Event flags can be explicitly set, which is typically used to allow communication between state sets. Or event flags can be synced to a PV, and will be set whenever a monitor is received for that PV, as in the example I sent you. You can use the efTest() function outside of a when statement, just like any other function. Mark -----Original Message----- From: Patrick Thomas [mailto:[email protected]] Sent: Thursday, October 01, 2009 5:20 PM To: Mark Rivers Cc: [email protected] Subject: Re: state notation code flags Hi Mark, Are the flags on a monitored variable set whenever the monitored variable is used in the code, including a pvPut, pvGet, assignment, calculation, or print statement? Is there a way to test if the flag is set besides an efTest in a when statement? Thank you, Patrick Mark Rivers wrote:
Hio Patrick, Here are some code snippets from one of my SNL programs. It has avariable nelements assigned to a PV, and a monitor on that PV. It has an event flag, nelementsMon that is synced to nelements. Whenever nelements changes the event flag will be set. In the init state I clear the event flag, just to be sure it is clear when the SNL code starts running (after all PVs connect). I then use efTestAndClear in a when statement to take actions when that event flag is set, and to clear it. This works fine for me.int nelements; assign nelements to "{P}{R}Nelements.VAL"; monitor nelements; evflag nelementsMon; sync nelements nelementsMon; /* Initialize things when first starting */ state init { when() { /* Clear all event flags */ ... efClear(nelementsMon); } state monitor_inputs } ... state monitor_inputs { ... when(efTestAndClear(nelementsMon) && (nelements>=1)) { /* If nelements changes, then change endPulses to thisvalue,* since this is what the user normally wants. endPulsescan be* changed again after changing nelements if this isdesired. */if (moveMode == MOVE_MODE_RELATIVE) endPulses = nelements; else endPulses = nelements-1; pvPut(endPulses); } state monitor_inputs } Mark ________________________________ From: [email protected] on behalf of Patrick Thomas Sent: Wed 9/30/2009 10:35 PM To: [email protected] Subject: state notation code flags Hi, I was wondering if there is a way to track at what point in the state notation code evflags are getting set and cleared, or if someone could clarify under what conditions they get set. I'm having trouble withthemgetting set somewhere and not being cleared, but I'm not sure where. Thank you, Patrick