Simotion Easy Basics (SEB) 15.11.04 V3.0 User ... - Home
Simotion Easy Basics (SEB) 15.11.04 V3.0 User ... - Home
Simotion Easy Basics (SEB) 15.11.04 V3.0 User ... - Home
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>Simotion</strong> <strong>Easy</strong> <strong>Basics</strong> reviewed<br />
2.2.4.3 States without any function<br />
If a project contains states, that do not have any function or it isn't even used, then the specified state<br />
model is not modified.<br />
We recommend that the functions, that represent the states and that are not used, are kept and that<br />
these only contain a variable assignment. This variable assignment then results in an immediate<br />
change into the next state. This means that states that are not used are run once "empty".<br />
Example 1: The STARTING state is not required. In this case, after the start condition has been<br />
fulfilled, this would mean a state change from STOPPED to STARTING. However, in the STARTING<br />
state, there is only the variable assignment g_eNewState := OM_AutomaticReady; this means that an<br />
immediate change to READY is initiated without any associated condition.<br />
This means that states without any function are run once without having any impact on the overall<br />
function of the application.<br />
Fig. 6: Assigning variables in the AUTOMATIC_STARTING state<br />
Example 2: The HOLDING and HELD states are not required. In this case, the states aren't even<br />
called by FCSelectState function in the first place. This means that the state model can remain<br />
unchanged - but it also not fully used.<br />
Version Date Page Document<br />
<strong>V3.0</strong> <strong>15.11.04</strong> 24 <strong>User</strong> documentation<br />
Copyright © Siemens AG 2003 All Rights Reserved For internal Use Only<br />
<strong>User</strong>_Manual_<strong>Simotion</strong>_<strong>Easy</strong>_<strong>Basics</strong>_V3_0.doc