MSFC editor

MSFC Editor
Using MSFC − overview...................................................................................................................1

The programming language MSFC.................................................................................................2

Operational modes...............................................................................................................2
Automatic cycle mode............................................................................................2
Automatic step mode.............................................................................................2
Manual mode.........................................................................................................3
Set up mode...........................................................................................................3
Supervision and diagnostics.................................................................................................3
Supervision while operation...................................................................................4
Step priorities.........................................................................................................4
Criteria analysis.....................................................................................................5
Timeout..................................................................................................................5
Interlock faults........................................................................................................6

Editing in MSFC using the graphic editor......................................................................................7

Editing step details in MSFC................................................................................................7
Changing the properties of a step in MSFC.........................................................................7
Changing the names of actions or transitions in MSFC.......................................................7
Editing action and transition details in MSFC.......................................................................8
Inserting branches in MSFC.................................................................................................8
Deleting unused details in MSFC.........................................................................................8
Entering a new Step Number in MSFC................................................................................9

Using MSFC in online mode..........................................................................................................11

Setting steps for automatic mode.......................................................................................11

Dialogs in MSFC.............................................................................................................................12
Dialog 'Action Properties'...................................................................................................12
Dialog 'Set Step ...'.............................................................................................................12
Dialog 'Step'.......................................................................................................................12
Dialog 'Transition'...............................................................................................................13
Dialog 'Enter new Step Number'........................................................................................13

Objects in MSFC.............................................................................................................................15
MSFC step sequence.........................................................................................................15
Steps in MSFC...................................................................................................................15
Initial step in MSFC..............................................................................................16
Wait step in MSFC...............................................................................................16
Check step in MSFC............................................................................................16
Move step in MSFC.............................................................................................16
Step detail in MSFC...........................................................................................................17
Transition in MSFC.............................................................................................................17
Action block in MSFC.........................................................................................................17
Action in MSFC..................................................................................................................18
Action qualifier in MSFC.....................................................................................................18
Branch in MSFC.................................................................................................................18

i
Using MSFC − overview
Note, that the programming language MSFC is not available in each software version because it is
an additional feature which has to be installed and enabled explicitly by the use of a specific
software key.

Normally the machine cycle which has to be realized in the controlling software, is fixed in a flow
chart. In this flow chart all single movements and their dependencies are explicitly and implicitly
represented. Additional requirements for the controlling software result of the sensor technology,
the actuators and constructional demands.

In the flow chart the machine cycle is divided into functional units, the steps. Between the single
steps a chronological and/or a functional relation exists. In MSFC this relationship is represented by
arranging steps graphically in one or several step sequences. Only active steps are processed in a
cyclic way by the PLC for reducing cycle times. Parallel machine cycles can be programmed in
distinct step sequences. Active steps in distinct step sequences are processed parallel.

To reduce the programming effort for the controlling software different types of steps have been
created in MSFC. The step type determines the functional characteristics of a step, including some
processing rules and properties for supervision and diagnostics. These characteristics are realized
by the programming system and do not have to be programmed by the application programmer.

In MSFC different operational modes can be used. The step sequences and the step inherent
functionality is processed according to the selected operational mode.

1
The programming language MSFC
For using MSFC it is important to have some knowledge about the basics of this programming
language. The most important topics to know are given in the topics listed below.

Operational Modes

Supervision and diagnostics

Operational modes
For machines or plants controlled by a PLC application programmed in MSFC the following four
operational modes can be used:

• Automatic cycle mode

• Automatic step mode

• Manual mode

• Set up mode

Automatic cycle mode

The automatic cycle mode is the operational mode which should be used for the normal machine
operation.

If the machine is started for the first time or in case of a reset the initial steps of all step sequences
become active and the step sequences are processed. If a transition becomes TRUE the next step
of a step sequence is processed immediately. If the machine is restarted after a stop, the
processing of the step sequences continues at the point where it has been stopped.

In automatic cycle mode the time monitoring for check steps and move steps is active.

The automatic cycle mode is active if the input variable 'auto' is TRUE and the input variable
'autostep' is FALSE.

Automatic step mode

The automatic step mode is the operational mode which should be used if parts of a machine have
failed. In case of a failure in a machine part the related function can be performed by an operator.
This operator manually fulfills the transition condition of the failed machine part. Pressing the start
button the program execution continues. The automatic step mode can also be used for teach−in
processes for robots.

In automatic step mode the step sequences are processed automatically till the first move step is
reached. Reaching a move step the step sequence is deactivated, outc is not set, the auto interlock
detail is not processed and the time monitoring is not active. If the transition condition of the move
step is manually fulfilled the next step becomes active. Pressing the start button the step sequence
is processed till the next move step is reached.

2
The programming language MSFC Manual mode

The automatic step mode is active if the input variables 'auto' and 'autostep' are TRUE.

Manual mode

The manual mode can be used to drive the machine manually. If a button on the operator panel is
pressed, the manual request detail and the manual interlock detail of the corresponding step are
processed. The time monitoring is started for check steps and move steps. If the manual interlock
detail is TRUE, outc is set and the action is processed.

It is up to the application programmer to edit the manual interlock detail in a way that no damages
will result in manual mode.

The buttons of the operator panel are dead man's buttons, i.e. the action is set as long as the
button is pressed. If the button is released the movement is stopped. The time monitoring is started
if the button is pressed once. Pressing the button for a second time the time monitoring is started
again.

If several buttons are pressed at the same time the corresponding steps are processed one after
another.

The manual mode is active if the input variables 'auto' and 'setup' are FALSE.

Set up mode

The set up mode can be used to take the whole machine or parts of it into operation. This mode is
useful if only parts of a machine have already been set and the functionality of these parts should
be checked. In set up mode the interlock and release details are not processed and the time
monitoring is not active. It is up to the machine operator to check that no damages will result
activating a certain movement. Pressing the button on the operator panel and setting the
corresponding manual request the action of the corresponding step is immediately processed and
e.g. the movement is done.

The set up mode is active if the input variable 'auto' is FALSE and the input variable 'setup' is
TRUE.

Supervision and diagnostics

Having started the machine or plant operation it is necessary to survey the machine cycles which
are executed. In case of machine failures it is necessary to display the cause of the failure, i.e. the
corresponding step, and the failed I/O signal. Therefore the following possibilities for supervision
and diagnostics have been implemented in MSFC.

• Supervision while operation

• Step priorities

• Criteria analysis

• Timeout

• Interlock faults

3
The programming language MSFC Supervision while operation

Supervision while operation

While machine operation texts can be displayed describing each single machine step or transition.
This way the machine operator is able to survey the correct machine operation or to know the
machine step where the error occurred in case of a machine failure.

The programming system allows to enter two different types of texts: Processing texts for steps and
processing texts for transitions.

The text 'Processing text for step' is displayed if an interlock error occurred.

The text 'Processing text for transition' is displayed if outc is TRUE, the transition is FALSE and the
step sequence is not active.

Both texts can be entered in the dialog 'Step' which can be called choosing the menu item 'Object
Properties...' in the context menu of the step in the MSFC worksheet. During machine operation the
current text is stored at the output variable 'processtext' of the MSFC function block. If several
steps in parallel step sequences are active the text of the step with the highest priority is stored at
the variable 'processtext'.

Step priorities

In POUs with several parallel step sequences normally several steps are active at the same time.
But only one text can be displayed on the operator panel. Therefore it is necessary to determine
the step with the highest priority. Only the text of this step is going to be displayed on the operator
panel. The step with the highest priority is determined using the following criteria:

• Interlock condition is FALSE

• Timeout detected

• Priority of the step type

• Outc is set

The first criteria is the criteria with the highest priority, the last with the lowest priority.

For determining the step with the highest priority while troublefree operation the third and the last
criteria are relevant. Each step type includes a step type priority as an inherent characteristic. The
step type priority is shown in the following table:

Step type Priority

Initial step Lowest
Wait step
Check step
Move step Highest

If several move steps have set their outc at the same time they have all the same priority. In this
case the text of the first move step in the first worksheet of the project tree is displayed.

4
The programming language MSFC Criteria analysis

For determining the step with the highest priority in case of machine failure all criteria are relevant.
If several steps in different step sequences have the same priority also the step in the first
worksheet of the project tree is displayed.

If several MSFC POUs are used within one project, the variable 'diagprio' can be used. Comparing
the variable 'diagprio' of the different POUs, the text of the POU with the highest value of the
variable 'diagprio' can be displayed on the operator panel.

Criteria analysis

In complex machines and plants a machine failure stops the whole production and high costs for
machine down−times result. Often the part of machine causing the failure is just a limit switch or a
cable which does not work anymore. In these cases the machine operator is able to remove the
error if he knows the cause of it.

Therefore the criteria analysis has been implemented in MSFC. The criteria analysis determines
the name of the variable or the I/O signal causing the error.

The criteria analysis checks which variable prevents the detail from getting TRUE and displays its
name on the operator panel.

If there are several variables preventing a detail from getting TRUE the names of the relevant
variables are displayed separated by Boolean integrations like AND or OR.

Timeout

Timeout occurs if the control time which has been set for check or move steps in the dialog 'Step' is
exceeded.

In case of timeout the following things happen:

1. The output variable 'timeout' is TRUE.

2. The current step sequence is deactivated in case of move steps.

3. The criteria analysis is activated.

Timeout by move steps

A timeout by move steps occurs if either the release detail or the transition is FALSE and the
control time is exceeded.

In automatic mode with a timeout by move steps the next step is not processed. The step switching
is stopped. In manual mode with a timeout by move steps all other manual request are not
processed.

Timeout by check steps

A timeout by check steps occurs if the transition is FALSE and the control time is exceeded. If an
interlock detail is FALSE an interlock fault is generated.

5
The programming language MSFC Interlock faults

In case of a timeout by a check step, the step sequence is still active and outc is set.

Interlock faults

Interlock faults occur if an interlock detail of a step is FALSE when the step is processed. Interlock
faults do not occur in case of move steps. If a release detail of a move step is FALSE, the control
time passes and a timeout is generated. Furthermore interlock faults do not occur in set up mode
because interlock details are not processed in set up mode.

In case of interlock faults the following things happen:

1. The output variable 'interlockfault' is TRUE.

2. All parallel step sequences of the MSFC POU are deactivated.

3. The criteria analysis is done basing on the data of the current processing cycle.

In automatic mode it is not possible to restart the machine until the fault has been reset, this means
the input variable 'faultreset' is TRUE. After the faultreset the machine is restarted if the input
variable 'start' is TRUE.

In manual mode it is not possible to activate a step using the corresponding manual request detail
until the fault has been reset, this means the input variable 'faultreset' is TRUE. After the faultreset
the next step is activated if the corresponding manual request detail is TRUE.

6
Editing in MSFC using the graphic editor
In the graphic editor you can edit in the programming language MSFC using different features.

The way to edit in MSFC is in most cases similar to edit in SFC. In this chapter only the topics are
described which are different regarding to SFC. Jumps to relevant topics of editing in SFC are
provided where necessary.

Editing step details in MSFC

In MSFC each step has the following details: Auto interlock, manual interlock and manual request.
These details have their own code body which is edited in a subordinate worksheet for each step
detail.

How to proceed:

• Double click on the step.

The dialog 'Select Step Detail' appears.

• Double click on the detail you want to edit.

The dialog 'Insert' appears.

• Choose the programming language for the detail.

• Confirm the dialog.

The detail worksheet is inserted in the project tree and the worksheet is opened.

• Edit the step detail.

Note: The output variable of this detail has to be 'detailresult'. The variable 'detailresult' has already
been declared in the variable declaration of the POU.

Changing the properties of a step in MSFC

You can change the properties of a step such as the type or the processing texts.

How to proceed:

• Choose the menu item 'Object Properties...' in the context menu of the step.
The dialog 'Step' appears.

• Change the properties you want to.

Changing the names of actions or transitions in MSFC

In MSFC worksheet you can change the name of an action or a transition.

How to proceed:

7
Editing in MSFC using the graphic editor Editing action and transition details in MSFC

• Choose the menu item 'Object Properties...' in the context menu of the action or transition
if you want to change the name first.
The properties dialog appears.

• Enter a new name.

• Confirm the dialog.

Editing action and transition details in MSFC

In MSFC each action or transition has a detail code body which is edited in a subordinate
worksheet.

How to proceed:

• Double click on the action or transition.

The dialog 'Insert' appears.

• Choose the programming language for the detail.

• Confirm the dialog.

The detail worksheet is inserted in the project tree and the worksheet is opened.

• Edit the action or transition detail.

Note: The output variable of this detail has to be 'detailresult'. The variable 'detailresult' has already
been declared in the variable declaration of the POU.

Inserting branches in MSFC

You can insert only alternative branches in an MSFC step sequence if they do not succeed a move
step.

Simultaneous branches cannot be used in MSFC.

Branches in MSFC are edited the same way as in SFC either using the SFC branch edit mode or
the icon 'Insert Simultaneous/Alternative Branches':
.

Deleting unused details in MSFC

This feature is not yet implemented in the current system version.

You can delete unused MSFC action, transition and step details automatically by selecting one of
the menu items 'Delete Unused Details' or 'Delete unused details (selected POU's)' in the submenu
'Extras'.

Unused details are worksheets, which are never accessed in the current project, even if they
contain code. On the other hand, an empty detail is not deleted in every case, because it might be
used although it does not contain code.

8
Editing in MSFC using the graphic editor Entering a new Step Number in MSFC

The menu item 'Delete unused details (only selected POU's)' is also available in the context menu
of an MSFC POU icon in the project tree editor.

When performing one of the following procedures, the unused details are deleted irretrievable. So
make sure, that you don't need the unused details for future purposes before executing the
automatic deletion.

How to delete unused details automatically in all MSFC POUs of a project:

• Make sure that the project tree editor is the active window.

• Select the menu item 'Delete Unused Details' in the submenu 'Extras'.
The system compiles and links all MSFC POUs to get information about the existing
MSFC details and which of them are used.
Afterwards the unused details are deleted automatically.

How to delete unused details automatically in a certain MSFC POU:

• In the project tree mark the node icon(s) of the desired MSFC POU(s), of which you want
to delete unused details.

• Select the menu item 'Delete Unused Details (selected POU)' in the submenu 'Extras'.
Note: If you select the menu item although you have marked any other icon in the project
tree than an MSFC POU, a message box appears, asking you whether you want to delete
the unused details of all MSFC POUs in the project.

After selecting the menu item, the system compiles and links the selected POU(s) to get
information about the existing MSFC details and which of them are used.
Afterwards the unused details are deleted automatically.

Entering a new Step Number in MSFC

This feature is not yet implemented in the current system version.

The MSFC editor provides the possibility to enter a new step number for the next step to be
inserted in an MSFC code body.

This feature can be used to determine a certain step number in a given step transition sequence.

Example: Assume, that you have to expand an existing MSFC code body with new steps and
transitions, in which step numbers between 1 and 100 are used. In this case it might be difficult to
determine, which numbers are already used by existing steps and which is the first free number. In
order to avoid the double usage of a number you can call the dialog 'Enter new Step Number'. This
dialog displays the first free number and provides the possibility to enter a step number for the next
step to be inserted (in our example this could be '200'). This ensures, that none of the already
existing step numbers is used twice. The number of every further step is increased by one.

How to enter the new step number:

• In the project tree click on the node icon of the desired MSFC POU, for which you want to
determine the next free step number.

9
Editing in MSFC using the graphic editor Entering a new Step Number in MSFC

• Select the menu item 'Enter new Step Number' in the submenu 'Extras'.
The dialog 'Enter new Step Number' appears, showing you the first free number which can
be used for a new step.

• Enter the new step number and confirm the dialog.

The first new step which you insert now in any code body worksheet within this POU
obtains the entered number.

10
Using MSFC in online mode
The graphic editor in online mode can also be used to debug MSFC worksheets. After compilation
the graphic editor is called in online mode by double clicking on an icon 'Worksheet in MSFC' in the
instance tree editor.

The way to debug MSFC worksheets is in most cases similar to debugging SFC worksheets. In this
chapter only the topics are described which are different regarding to SFC.

Setting steps for automatic mode

If you switch from automatic mode into manual mode the step where the processing of the step
sequence stopped is stored. In online mode this step is represented with a green color. Switching
back to automatic mode this step is the first step to be processed. If you want to be a different step
the first step to be processed you can set a new step.

How to proceed:

• Choose the menu item 'Object Properties...' in the context menu of the step.
The dialog 'Set Step ...' appears.

• Press the button 'Yes'.

11
Dialogs in MSFC
The following dialogs are used to edit MSFC:

• Dialog 'Action Properties'

• Dialog 'Set Step...'

• Dialog 'Step'

• Dialog 'Transition'

• Dialog 'Enter new Step Number'

Dialog 'Action Properties'

The dialog 'Action Properties' appears either if you choose the menu item 'Object Properties...' in
the context menu of an action in an MSFC worksheet or if you mark an action and choose the
menu item 'Action Block' in the submenu 'Objects' or if you click on the icon 'Create action':

It is used to change the name of the action.

Dialog 'Set Step ...'

The dialog 'Set Step ...' appears if you choose the menu item 'Object Properties...' in the context
menu of a step in an MSFC worksheet in online mode. It is used to set the step to start with in
automatic mode if you switch from manual mode into automatic mode.

The dialog fields and buttons have the following meaning:

Yes sets the current step as the first step to be processed in automatic mode.
No lets the green represented step to be the first step to be processed in
automatic mode.
Dialog 'Step'
The dialog 'Step' appears if you choose the menu item 'Object Properties...' in the context menu of
a step in an MSFC worksheet. It is used to change the step type, to set the control time for the time
monitoring or to enter the processing texts.

The dialog fields and buttons have the following meaning:

Name specifies the name of the step.

Initial position specifies that the step represents the initial position of the machine.
No restart allowed specifies that the machine cannot restart in this position.
One interlock detail specifies that only one interlock detail has to be edited for this step. This
interlock detail is going to be checked in automatic and in manual mode.
Control time

12
Dialogs in MSFC Dialog 'Transition'

specifies the time interval for the time monitoring. The control time should not
be shorter than the system tick. The time monitoring is only available for
check steps and move steps.
Processing text for specifies the text of the output variable 'processtext' if outc of the step is
step FALSE.
Processing text for specifies the text of the output variable 'processtext' if outc is TRUE and the
transition transition is FALSE.
Type changes the step type.

How to work with the dialog

• Activate the check box 'Initial position' if the step represents the initial position.

• Activate the check box 'No restart allowed' if you do not want to restart the program
execution at this step.

• Activate the check box 'One interlock detail' if you want to have the same detail for
automatic and manual mode.

• Enter a time interval for the time monitoring for check or move steps.

• Enter the processing texts.

• Change the step type if necessary.

Dialog 'Transition'
The dialog 'Transition' appears if you choose the menu item 'Object Properties...' in the context
menu of a transition in an MSFC worksheet.

In the dialog field 'name' you can change the name of the transition.

Dialog 'Enter new Step Number'

This dialog is not yet implemented in the current system version.

The dialog 'Enter new Step Number' appears if you select the menu item 'Enter new Step Number'
in the submenu 'Extras'.

The dialog is used to display the first free (i.e. unused) step number in an existing MSFC POU and
to set the number of the next step to be inserted in an MFSC code body of this POU. This feature
prevents from using a step number twice in one POU when expanding an existing code body with
new steps and transitions.

The dialog fields and buttons have the following meaning:

Actual step number indicates the first free step number in the current POU, which can be used for
a new step.
New Step Number allows to define the number for the next step to be inserted.

13
Dialogs in MSFC Dialog 'Transition'

How to work with the dialog

For information how to work with the dialog please refer to the following topic:

Entering a new Step Number

14
Objects in MSFC
While editing in MSFC you can use different objects, such as steps, transitions and action blocks.
These MSFC objects have a different functionality than SFC objects although they may remember
at SFC objects.

Please refer to the following topics for detailed descriptions:

• Step sequence

• Step

• Step detail

• Transition

• Action block

• Action

• Action qualifier

• Branch

For information about using these objects please refer to the topic Editing in MSFC.

MSFC step sequence

MSFC step sequences consist basically of steps and transitions. A step always belongs to a
transition and it is not possible to create a structure with two steps or two transitions directly
following. The connection between a step and a transition is represented as a vertical line. MSFC
step sequence can also be called MSFC network.

Steps in MSFC
Steps are basic elements of MSFC networks. One or several action blocks can be associated to a
step.

The state of a step can either be active or inactive. Active means that the step is actually processed
by the PLC. According to the operational mode the corresponding step detail is processed. If the
step detail is TRUE and no error occurred, the variable 'stepname.outc' is also TRUE. In this case
outc is set and the action associated to the step is executed.

Note: The variable is created internally by the programming system. There is no need to declare it
in the variable declaration of the POU.

Steps are associated with its preceding and succeeding transitions via direct links which are
represented as lines. The name of the step is indicated in the rectangle which symbolizes a step in
the graphic editor.

15
Objects in MSFC Initial step in MSFC

Several types of steps can be used:

• Initial steps

• Wait steps

• Check steps

• Move steps

Initial step in MSFC

The initial step is the first active step if the machine is started for the first time or if a reset has been
done before. For initial steps no time monitoring is available. In a step sequence only one initial
step can be used. The first is not necessarily the initial step. Initial steps are represented
graphically with a double−lined rectangle.

Wait step in MSFC

Wait steps can be used if an unlimited time interval is allowed for processing the step. A wait step
has the same functionality as an initial step. Within a step sequence several wait steps can be
used.

Wait steps are typically used for the synchronization of several step sequences. If a second step
sequence should be processed after a first step sequence has been finished, a wait step is inserted
in the second step sequence. In this case the transition detail of the wait step loads the variable
'stepname.outc' of the step in the first step sequence and stores it to the variable 'detailresult'.

Wait steps are represented graphically with a rectangle and the letter 'W'.

Check step in MSFC

Check steps can be used to check if a certain process passes correctly within a given time interval.
Check steps are time monitored.

Check steps are represented graphically with a rectangle and the letter 'C'.

Move step in MSFC

Move steps can be used to program the single movements of a machine. Via this step the output
variables of the action blocks are set and the corresponding actuators are controlled. Move steps
are time monitored.

Move steps are represented graphically with a rectangle and the letter 'M'.

Note: It is not possible to use alternative branches behind move steps.

16
Objects in MSFC Step detail in MSFC

Step detail in MSFC

Normally in MSFC each step has the following details Auto interlock, manual interlock and manual
request. These details have their own code body which is edited in a subordinate worksheet for
each step detail.

The auto interlock detail of a step is processed if the automatic mode has been chosen. In case of
move steps the auto interlock detail is called auto release.

The manual interlock detail is processed if the manual mode has been chosen. In case of move
steps the manual interlock detail is called manual release.

The manual request detail of a step is processed if the manual or the set up mode have been
chosen. The manual request detail is available for all step types.

Note: It is also possible to edit one interlock or release detail for a step if the interlock or release
conditions are the same for automatic and manual mode. In this case a check box in the dialog
'Step' has to be activated.

Transition in MSFC
Transitions are basic elements of MSFC step sequences. A transition characterizes the condition
when the PLC passes from one step to another. If the condition is TRUE the preceding step
becomes inactive and the succeeding step becomes active immediately. In difference to IEC
1131−3 the action block of the preceding one is not executed once again.

In MSFC the code body for a transition is always programmed in a separate code body worksheet
which is called transition detail. The output variable of this detail has to be 'detailresult'.

Note: It is absolutely necessary to store the result of the detail on the variable 'detailresult'.

The variable 'detailresult' has already been declared in the variable declaration of the POU. It is not
necessary to declare it by the application programmer.

In case of a transition detail always a variable is created by the programming system which has the
same name as the transition and which can be used. There is no need to declare it in the variable
declaration of the POU. In automatic mode only the value of the transition preceding the active step
is written in the processing cycle. In manual mode all variables of all transitions are written in the
current processing cycle of the step sequence.

Transitions are represented graphically as a horizontal line.

Action block in MSFC

MSFC action blocks are basic elements of MSFC step sequences. It consists of an action and the
MSFC action qualifier 'M'. The action block is always associated to a step.

Concatenated action blocks are several action blocks associated to one step.

17
Objects in MSFC Action in MSFC

Action in MSFC
In MSFC the code body for an action is always programmed in a separate code body worksheet
which is called action detail. The output variable of this detail has to be 'detailresult'.

It is absolutely necessary to store the result of the detail on the variable 'detailresult'.

The variable 'detailresult' has already been declared in the variable declaration of the POU. It is not
necessary to declare it by the application programmer.

Note: In difference to SFC action details associated to a step are not executed once again after the
step has become inactive.

Action qualifier in MSFC

MSFC action qualifiers do not have any significance. They only show that an MSFC network has
been edited. The MSFC action qualifier is represented with the letter 'M'.

Note: In difference to SFC action details associated to a step are not executed once again after the
step has become inactive.

Branch in MSFC
Branches in MSFC worksheets exist if the MSFC network is separated into 2 or more different
arms. Only alternative branches can be used if they do not succeed a move step. Simultaneous
branches cannot be used.

Alternative branches are executed alternatively. This means that the succeeding transition
becomes TRUE if the step in one branch has been executed. Alternative branches are represented
in the graphic editor using one bold, horizontal line.

Branches in MSFC are edited the same way as in SFC either using the SFC branch edit mode or
the icon 'Insert Simultaneous/Alternative Branches':
.

18