The conditions for a transition are set up after the entry block is exectued. The state machine is event driven. After the entry block, events are set up on timers and values of process variables. Asynchronous events on those PV changes or timers expiring cause the state machine to process, check if any of the events have occurred, and then either take action and make a state transaction - or just sleep again and wait for subsequent events that are interesting in the current state.
________________________________
From: [email protected] [[email protected]] on behalf of Eric Williams [[email protected]]
Sent: Friday, March 13, 2015 8:36 PM
To: EPICS tech-talk
Subject: SNL: state change statement in entry block
I had put a state change statement in the entry block of one of my states and the 2.2.1 compiler kicked it out. Evidently it only allowed them in transition blocks. I re-arrange my code to get around the restriction but I was curious: What is the problem with having a state change statement in an entry block?
--
Eric Williams
ALS Controls, LBL
<http://www.grammarly.com/?utm_source=dict&utm_medium=link&utm_campaign=chrome_plg>
- References:
- SNL: state change statement in entry block Eric Williams
- Navigate by Date:
- Prev:
StatusCreate class with Throwable Ricardo Herrero
- Next:
Re: SNL: state change statement in entry block John William Sinclair
- 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
- Navigate by Thread:
- Prev:
Re: SNL: state change statement in entry block Eric Williams
- Next:
Re: SNL: state change statement in entry block John William Sinclair
- 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
|