Local block output variables

Customize generated local block output variable identifiers

Model Configuration Pane: Code Generation / Identifiers

Description

Customize generated local block output variable identifiers.

Dependencies

This parameter:

Appears only for ERT-based targets.
Requires Embedded Coder^® when generating code.

Settings

rtb_$N$M (default) | string

Enter a macro that specifies whether, and in what order, certain text is to be included in the generated identifier. The macro can include a combination of the following format tokens.

Token	Description
`$A`	Insert data type acronym (for example, `i32` for integers) into signal and work vector identifiers.
`$M`	Insert name-mangling text if required to avoid naming collisions. Required.
`$N`	Insert name of object (block, signal or signal object, state, parameter or parameter object) for which identifier is being generated.
`$U`	Insert text that you specify for the `$U` token. Use the Custom token text parameter to specify this text.

Tips

Avoid name collisions in general. One way is to avoid using default block names (for example, Gain1, Gain2...) when your model has many blocks of the same type.
Where possible, increase the Maximum identifier length to accommodate the length of the identifiers you expect to generate. Reserve at least three characters for name-mangling text.
To control the case (upper or lower case) of the text that each token represents, include decorators such as [U_] in your macro. See Control Case of Identifiers by Using Basic Token Decorators.
This option does not impact objects (such as signals and parameters) that have a storage class other than Auto (such as ImportedExtern or ExportedGlobal).

Recommended Settings

Application	Setting
Debugging	No impact
Traceability	Use default
Efficiency	No impact
Safety precaution	No recommendation

Programmatic Use

Parameter: CustomSymbolStrBlkIO

Type: character vector

Value: valid combination of tokens

Default: rtb_$N$M

Version History

Introduced before R2006a