Real-Time Workshop User's Guide | ![]() |
Application Modules - With respect to Real-Time Workshop program architecture, these are collections of programs that implement functions carried out by the system dependent, system independent, and application components.
Block Target File - A file that describes how a specific Simulink block is to be transformed to a language such as C, based on the block's description in the Real-Time Workshop file (model
.rtw
). Typically, there is one block target file for each Simulink block.
File Extensions - Below is a table that lists the file extensions associated with Simulink, the Target Language Compiler, and the Real-Time Workshop.
Generic Real-Time (GRT) target - A target configuration that generates model code for a real-time system, with the resulting code executed on your workstation. (Note that execution is not tied to a real-time clock.) You can use GRT as a starting point for targeting custom hardware.
Host System - The computer system on which you create your real-time application.
Inline - Generally, this means to place something directly in the generated source code. You can inline parameters and S-functions using the Real-Time Workshop.
Inlined Parameters (Target Language Compiler Boolean global variable: InlineParameters
) - The numerical values of the block parameters are hard coded into the generated code. Advantages include faster execution and less memory use, but you lose the ability to change the block parameter values at run-time.
Inlined S-Function - An S-function can be inlined into the generated code by implementing it as a .tlc
file. The code for this S-function is placed in the generated model code itself. In contrast, noninlined S-functions require a function call to S-function residing in an external MEX-file.
Interrupt Service Routine (ISR) - A piece of code that your processor executes when an external event, such as a timer, occurs.
Loop Rolling (Target Language Compiler global variable: RollThreshold
) - Depending on the block's operation and the width of the input/output ports, the generated code uses a for
statement (rolled code) instead of repeating identical lines of code (flat code) over the block width.
Make - A utility to maintain, update, and regenerate related programs and files. The commands to be executed are placed in a makefile.
Makefiles - Files that contain a collection of commands that allow groups of programs, object files, libraries, etc. to interact. Makefiles are executed by your development system's make utility.
Multitasking - A process by which your microprocessor schedules the handling of multiple tasks. The number of tasks is equal to the number of sample times in your model.
Noninlined S-Function - In the context of the Real-Time Workshop, this is any C MEX S-function that is not implemented using a customized .tlc
file. If you create an C MEX S-function as part of a Simulink model, it is by default noninlined unless you write your own .tlc
file that inlines it.
Non-Real-Time - A simulation environment of a block diagram provided for high-speed simulation of your model. Execution is not tied to a real-time clock.
Nonvirtual Block - Any block that performs some algorithm, such as a Gain block.
Pseudomultitasking - In processors that do not offer multitasking support, you can perform pseudomultitasking by scheduling events on a fixed time-sharing basis.
Real-Time System - A system that uses actual hardware to implement algorithms, for example, digital signal processing or control applications.
Run-time Interface - A wrapper around the generated code that can be built into a stand-alone executable. The run-time interface consists of routines to move the time forward, save logged variables at the appropriate time steps, etc. The run-time interface is responsible for managing the execution of the real-time program created from your Simulink block diagram.
S-Function - A customized Simulink block written in C or M-code. C-code S-functions can be inlined in the Real-Time Workshop.
Singletasking - A mode in which a model runs in one task.
System Target File - The entry point to the Target Language Compiler program, used to transform the Real-Time Workshop file into target specific code.
Target Language Compiler - A compiler that compiles and executes system and target files.
Target File - A file that is compiled and executed by the Target Language Compiler. A combination of these files describes how to transform the Real-Time Workshop file (model.rtw
) into target-specific code.
Target System - The computer system on which you execute your real-time application.
Targeting - The process of creating an executable for your target system.
Template Makefile - A line-for-line makefile used by a make utility. The template makefile is converted to a makefile by copying the contents of the template makefile (usually system.tmf
) to a makefile (usually system.mk
) replacing tokens describing your model's configuration.
Target Language Compiler Program - A set of TLC files that describe how to convert a model.rtw
file into generated code.
Task Identifier (tid) - Each sample time in your model is assigned a task identifier (tid
). The tid
is passed to the model output and update routines to decide which portion of your model should be executed at a given time.
Virtual Block - A connection or graphical block, for example, a Mux block.
![]() | Blocks That Depend on Absolute Time |