Truth tables implement combinatorial logic design in a concise, tabular format. Typical applications for truth tables include decision making for:
Fault detection and management
Mode switching
Truth tables are supported only in Simulink^{®}.
You can add a Truth Table block directly to your Simulink model, or you can define a truth table function in a Stateflow^{®} chart, state, or subchart. Truth Table blocks in a Simulink model execute as a Simulink block, while truth table functions in a Stateflow chart execute only when you call the truth table function. The location of the function determines the set of states and transitions that can call the function.
If you want to call the function from within one state or subchart and its substates, put your truth table function in that state or subchart. That function overrides any other functions of the same name in the parents and ancestors of that state or subchart.
If you want to call the function anywhere in a chart, put your truth table function at the chart level.
If you want to call the function from any chart in your model, put your truth table at the chart level and enable exporting of chartlevel functions. For more information, see Export Stateflow Functions for Reuse.
Note
A truth table function can access chart and state data above it in the Stateflow hierarchy.
This truth table function has the name ttable
. It takes three
arguments (x
, y
, and z
) and returns
one output value (r
).
The function consists of this arrangement of conditions, decisions, and actions.
Condition  Decision 1  Decision 2  Decision 3  Decision 4 

x == 1  T  F  F   
y == 1  F  T  F   
z == 1  F  F  T   
Action  r = 1  r = 2  r = 3  r = 4 
Each of the conditions entered in the Condition column must evaluate to true (nonzero value) or false (zero value). Outcomes for each condition are specified as T (true), F (false), or  (true or false). Each of the decision columns combines an outcome for each condition with a logical AND into a compound condition, which is referred to as a decision.
You evaluate a truth table one decision at a time, starting with Decision 1. The Decision 4 covers all possible remaining decisions. If one of the decisions is true, the table perform the associated action, and then the truth table execution is complete.
For example, if conditions x == 1
and y == 1
are
false and condition z == 1
is true, then Decision 3
is true and the variable r
is set equal to 3. The remaining decisions are
not tested and evaluation of the truth table is finished. If the first three decisions are
false, then the default decision is automatically true and its action
(r=4
) is executed. This table lists pseudocode corresponding to the
evaluation of this truth table example.
Pseudocode  Description 

if ((x == 1) & !(y == 1) & !(z == 1)) r = 1;  If Decision 1 is true, then set

elseif (!(x == 1) & (y == 1) & !(z == 1)) r = 2;  If Decision 2 is true, then set

elseif (!(x == 1) & !(y == 1) & (z == 1)) r = 3;  If Decision 3 is true, then set

else r = 4; endif  If all other decisions are false, then default decision is true. Set

To define a truth table function:
In the object palette, click the truth table function icon . Move your pointer to the location for the new truth table function in your chart.
Enter the signature label for the function.
The function signature label specifies a name for your function and the formal names for its arguments and return values. A signature label has this syntax:
[return_val1,return_val2,...] = function_name(arg1,arg2,...)
You can use the same variable name for both arguments and return values. For example, a function with this signature label uses the variables y1
and y2
as both inputs and outputs:
[y1,y2,y3] = f(y1,u,y2)
y1
and y2
are passed by reference (as pointers), and u
is passed by value. Passing inputs by reference reduces the number of times that the generated code copies intermediate data, resulting in more optimal code.Note
Do not use the name of a chart symbol as a function argument or return value. For example, if either x
or y
are chart data, defining a function with the signature y = f(x)
results in a runtime error.
To program the function, open the truth table editor by doubleclicking the function box.
In the truth table editor, add conditions, decisions, and actions. For more information, see Program a Truth Table.
In the Model Explorer, expand the chart object and select the truth table function.
The arguments and return values of the function signature appear as data items that
belong to your function. Arguments have the scope Input
. Return
values have the scope Output
.
In the Data properties dialog box for each argument and return value, specify the data properties, as described in Set Data Properties.
Create any additional data items required by your function. For more information, see Add Data Through the Model Explorer.
Your function can access its own data or data belonging to parent states or the chart. The data items in the function can have one of these scopes:
Constant
— Constant data retains its initial value through
all function calls.
Parameter
— Parameter data retains its initial value through
all function calls.
Local
— Local data persists from one function call to the
next function call. Valid only for truth tables that use C as the action
language.
Temporary
— Temporary data initializes at the start of every
function call. Valid only for truth tables that use C as the action language.
In truth table functions that use C as the action language, define local data when
you want your data values to persist across function calls throughout the simulation.
Define temporary data when you want to initialize data values at the start of every
function call. For example, you can define a counter with
Local
scope if you want to track the number of times that
you call the function. In contrast, you can designate a loop counter to have
Temporary
scope if you do not need the counter
value to persist after the function completes.
In truth table functions that use MATLAB^{®} as the action language, you do not need to define local or temporary function data. If you use an undefined variable, Stateflow creates a temporary variable that is available to the rest of the function. To store values that persist across function calls, your function can access local data at the chart level.
Tip
You can initialize local and temporary data in your function from the MATLAB workspace. For more information, see Initialize Data from the MATLAB Base Workspace.
You can call truth table functions from the actions of any state or transition. You can also call truth table functions from other functions. If you export a truth table function, you can call it from any chart in the model. For more information about exporting functions, see Export Stateflow Functions for Reuse.
The syntax for a call to a truth table function is the same as the function signature, with actual arguments replacing the formal ones specified in a signature. If the data types of an actual and formal argument differ, a function casts the actual argument to the type of the formal argument.
To call a truth table function, use the function signature and include an actual argument value for each formal argument in the function signature. If the data types of the actual and formal arguments differ, the function casts the actual argument to the type of the formal argument.
You can specify properties for a truth table function in the Model Explorer or the Truth Table properties dialog box.
To use the Model Explorer:
To open the Model Explorer, in the Modeling tab, select Model Explorer.
In the Model Hierarchy pane, select the truth table function.
In the Truth Table pane, edit the truth table function properties.
To use the Truth Table properties dialog box:
In the Stateflow Editor, rightclick the truth table function.
Select Properties.
Edit the truth table function properties.
You can also specify truth table function properties programmatically by using Stateflow.TruthTable
objects. For more information about the Stateflow programmatic interface, see Overview of the Stateflow API.
Function name. Click the function name link to bring your function to the foreground in its native chart.
Controls the inlining of your function in generated code:
Auto
— Determines whether to inline your function
based on an internal calculation.
Inline
— Inlines your function if you do not export
it to other charts and it is not part of a recursion. (A recursion exists if your
function calls itself directly or indirectly through another function call.)
Function
— Does not inline your function.
Signature label for your function. The function signature label specifies a name for your function and the formal names for its arguments and return values.
Controls the level of diagnostics for underspecification in your truth table function. For more information, see Correct Overspecified and Underspecified Truth Tables.
Controls the level of diagnostics for overspecification in your truth table function. For more information, see Correct Overspecified and Underspecified Truth Tables.
Controls the action language for your Stateflow truth table function. Choose between MATLAB or C. For more information, see Differences Between MATLAB and C as Action Language Syntax.
Function description. You can enter brief descriptions of functions in the hierarchy.
Link to online documentation for the function. You can enter a web URL address or a MATLAB command that displays documentation in a suitable online format, such as an HTML file or text in the MATLAB Command Window. When you click the Document link hyperlink, Stateflow displays the documentation.
To open the Truth Table properties dialog box, in the Modeling tab, click Table Properties.
The properties for Truth Table blocks are a combination of properties of truth table functions and charts that use MATLAB as the action language. For a description of each property, see Specify Properties of Truth Table Functions and Specify Properties for Stateflow Charts.
You can also specify Truth Table block properties programmatically by
using Stateflow.TruthTableChart
objects.
For more information about the Stateflow programmatic interface, see Overview of the Stateflow API.