User manual MATLAB REAL-TIME WORKSHOP 7

[. . . ] Real-Time Workshop® 7 User's Guide How to Contact The MathWorks Web Newsgroup www. mathworks. com/contact_TS. html Technical Support www. mathworks. com comp. soft-sys. matlab suggest@mathworks. com bugs@mathworks. com doc@mathworks. com service@mathworks. com info@mathworks. com Product enhancement suggestions Bug reports Documentation error reports Order status, license renewals, passcodes Sales, pricing, and general information 508-647-7000 (Phone) 508-647-7001 (Fax) The MathWorks, Inc. 3 Apple Hill Drive Natick, MA 01760-2098 For contact information about worldwide offices, see the MathWorks Web site. Real-Time Workshop® User's Guide © COPYRIGHT 1994­2010 by The MathWorks, Inc. The software described in this document is furnished under a license agreement. The software may be used or copied only under the terms of the license agreement. [. . . ] The 22-17 22 Generating Code makefile can be used as a starting point to determining the dependencies that the generated model code has. An additional approach to determining the dependencies is by using linker information, such as a linker map file, to determine the symbol dependencies. The location of Real-Time Workshop and blockset source and header files is provided below to assist in locating the dependencies. Real-Time Workshop Static File Dependencies Several locations in the MATLAB directory tree contain static file dependencies specific to the Real-Time Workshop product: · matlabroot/rtw/c/src/ This directory has subdirectories and contains additional files that may need to be compiled. Examples include solver functions (for continuous time support), external mode support files, C API support files, and S-function support files. Source files in this directory are included into the build process using in the SRC variables of the makefile. · matlabroot/rtw/extern/include/*. h · matlabroot/simulink/include/*. h These directories contain additional header file dependencies such as tmwtypes. h, simstruc_types. h, and simstruc. h. Note For ERT-based targets, several header dependencies from the above locations can be avoided. ERT-based targets generate the minimum necessary set of type definitions, macros, and so on, in the file rtwtypes. h. Blockset Static File Dependencies Blockset products leverage the rtwmakecfg. m mechanism to provide the Real-Time Workshop software with dependency information. As such, the rtwmakecfg. m file provided by the blockset contains the listing of include path and source path dependencies for the blockset. Typically, blocksets create a library from the source files which the generated model code can then link 22-18 Generated Source Files and File Dependencies against. The libraries are created and identified using the rtwmakecfg. m mechanism. The locations of thertwmakecfg. m files for the blocksets are · matlabroot/commblks/commblksdemos/rtwmakecfg. m · matlabroot/commblks/commmex/rtwmakecfg. m · matlabroot/dspblks/dspmex/rtwmakecfg. m · matlabroot/fuzzy/fuzzy/rtwmakecfg. m · matlabroot/physmod/drive/drive/rtwmakecfg. m · matlabroot/physmod/mech/mech/rtwmakecfg. m · matlabroot/physmod/powersys/powersys/rtwmakecfg. m If the model being compiled uses one or more of these blocksets, you can determine directory and file dependency information from the respective rtwmakecfg. m file. Specifying Include Paths in Real-Time Workshop Generated Source Files You can add #include statements to generated code. Such references can come from several sources, including TLC scripts for inlining S-functions, custom storage classes, bus objects, and data type objects. The included files typically consist of header files for legacy code or other customizations. Additionally, you can specify compiler include paths with the -I compiler option. The Real-Time Workshop build process uses the specified paths to search for included header files. Usage scenarios for the generated code include, but are not limited to, the following: · Real-Time Workshop generated code is compiled with a custom build process that requires an environment-specific set of #include statements. In this scenario, the Real-Time Workshop code generator is likely invoked with the Generate code only check box selected. It may be appropriate to use fully qualified paths, relative paths, or just the header filenames in the #include statements, and additionally leverage include paths. 22-19 22 Generating Code · The generated code is compiled using the Real-Time Workshop build process. In this case, compiler include paths (-I) can be provided to the Real-Time Workshop build process in several ways: - The Real-Time Workshop > Custom Code pane of the Configuration Parameters dialog box allows you to specify additional include paths. The include paths are propagated into the generated makefile when the template makefile (TMF) is converted to the actual makefile. The rtwmakecfg. m mechanism allows S-functions to introduce additional include paths into the Real-Time Workshop build process. [. . . ] System integrator solutions that are based on xPC Target are also available. For more information about xPC Target, see the xPC Target documentation. 46-3 46 Verifying a System With Hardware-In-the-Loop Simulation Setting Up and Running HIL Simulations To set up and run HIL simulations iterate through the following steps: 1 Develop a model that represents the environment or system under development. For more information, see: · Chapter 18, "Selecting and Configuring a Target " · Chapter 34, "Interfacing With a Real-Time Operating System " 2 Generate an executable for the environment model. 3 Download the executable for the environment model to the HIL simulation platform. 4 Replace software representing a system component with corresponding hardware. 5 Test the hardware in the context of the HIL system. [. . . ]