Enabling Instrumentation for Debugging

To set the flag on or off, use the set_param command. The default is off.

set_param(model, 'TLCAssertion', 'on|off') 

To check the current setting, use get_param.

get_param(model, 'TLCAssertion')

• none — Loss of tunability can occur without notification.

• warning — Loss of tunability generates a warning (default).

• error — Loss of tunability generates an error.

For a list of supported operators and functions, see Tunable Expression Limitations

• User local settings

• Enable All

• Disable All

For Assertion blocks not disabled, generated code for a model includes one of the following statements, at appropriate locations, depending on the blocks input signal type (Boolean, real, or integer, respectively).

utAssert(input_signal);
utAssert(input_signal != 0.0);
utAssert(input_signal != 0);

By default, utAssert has no effect in generated code. For assertions to abort execution, you must enable them by specifying the followingmake_rtw command for Real-Time Workshop > Make command:

make_rtw OPTS="-DDOASSERTS"

Use the following variant if you want triggered assertions to print the assertion statement instead of aborting execution:

make_rtw OPTS="-DDOASSERTS -DPRINT_ASSERTS"

utAssert is defined as #define utAssert(exp) assert(exp).

To customize assertion behavior, provide your own definition of utAssert in a hand-coded header file that overrides the default utAssert.h. For details on how to include a customized header file in generated code, see Integrating External Code Using Model Configuration Parameters.

When running a model in accelerator mode, the Simulink engine calls back to itself to execute assertion blocks instead of using generated code. Thus, user-defined callbacks are still called when assertions fail.