In the Error Rate Calculation block, if you set "Output data" to "Workspace" and run the simulation, the block fails to create the workspace variable. As a workaround, set "Output data" to "Port" and attach a Signal to Workspace block (from the DSP Blockset).
Parameters in the RF Satellite Link Demo (rf_satlink),
including those accessible using the "RF Link Demo: Settings" block, must
not be changed while the simulation is running. This problem
will be investigated before the final release of Version 3.0.
Blocks in the CPM sublibrary of the Digital Baseband sublibrary of the Modulation library are incompatible with Real-Time Workshop. As a result, Real-Time Workshop cannot generate code for models that include these blocks.
Several Communications Blockset demos are incompatible with Real-Time Workshop. As a result, Real-Time Workshop cannot generate code for these demos:
- 256 Channel ADSL
- Adaptive Equalization
- Bluetooth Voice Transmission
- CPM Phase Tree Example
- Digital Video Broadcasting Model
- Discrete Multitone Signaling
- Filtered QPSK vs. MSK
- GMSK vs. MSK
- WCDMA Coding and Multiplexing Example
- WCDMA End-to-End Physical Layer
- WCDMA Spreading and Modulation Example
Dialog boxes do not display titles and are sometimes missing text and
controls using the fvwm window manager and JVM 1.3.
When you run a query in the VQB and double-click the resulting variable in the Data field, the variable opens in the Array Editor. The content should display, but instead metadata displays. This will be fixed in the final release. You can double-click a cell in the Array Editor to display the content of that cell. As an alternative to viewing the results in the Array Editor, type the variable name in the Command Window, which displays the content.
gmakemay fail to build certain models, such as the demo modelmpc555rt_ccp.mdl, if the directory name of your MATLAB installation is too long (more than 20 characters). We recommend using an installation directory name ofMATLAB6p5or equivalent.
When using DSP blocks in your Embedded Target for Motorola MPC555 model you may experience the problems below.
- When using the WindRiver Diab compiler, many of the C files in the DSP library may fail to compile (depending on the version of your compiler). An example error message is below. It is possible to modify these files so that they compile with the WindRiver Diab compiler (remove the “const” keyword from the lines causing failures). If you are using the Metrowerks CodeWarrior compiler these files should compile without any problem.
"d:\r13\toolbox\rtw\dspblks\c\dspburg/burg_a_c_rt.c", line 55: error (dcc:1552): initializer type `creal32_T' incompatible with object type `float'- The compilation process fails providing no error message. This error is related to the large number of files (the DSP library) being compiled. The workaround is to repeat the build of the model – the DSP library objects created during the first build will still be present, and should not be re-made since the two builds are identical. This means that during the second build, gmake will have to compile fewer files (just the remaining DSP library files), which leads to a successful build.
When configuring settings, Target specific options and/or Embedded Target for Motorola MPC555 real-time options(1) and (2), the new settings may not fully take effect.To work around this problem, you must change these settings via the "Launch old simprm dialog..." control.
For example, to set the compiler optimization mode to "debug"
Simulation --> Parameters
Select Target specific options tab.
Press Launch old simprm dialog... button.
Select ET MPC555 real-time options (1) from the drop down.
Select optimize compiler for debug.
All compiler settings will be optimized for debug in the Beta
2 Release of the Embedded Target for Motorola MPC555, regardless of what
you set for the 'Compiler optimization switches' parameter (in the
target-specific Real-Time Workshop options in the Model Explorer).
When you select the new Array Editor feature, File -> Print Selection, the printout is incomplete.
This problem, introduced in Version 6.5, still exists in Beta 2. When you run thedepfunfunction for a file that uses graphics functions, such aslegend, MATLAB might crash. You might also experience the problem when you rundepdirorprofile.
For Windows platforms, you cannot use cd or any directory tool
in the MATLAB desktop (including the Current Directory browser and Set Path
dialog box) to access the top level of a UNC (Universal Naming Convention)
path.
In Beta 2, the Edit -> Find and Incremental Search features are not working in the Command Window.
While editing an M-file function in the Editor, if you hover over a variable that also exists in the base workspace, the datatip displays the value of the base workspace variable, not the value of the variable in the funtion M-file. To avoid confusion, select File -> Preferences -> Display, and for General Display Options, clear the check mark for Enable datatips in edit mode.
For some Linux configurations, on MATLAB startup, several warnings of the form:
Font specified in font.properties not found ...
might appear in the Command Window. This happens because the JVM cannot find required fonts. It does not affect MATLAB performance. To resolve the problem, update your Linux system to include XFree 4.x.
For some UNIX platforms, the background color in the Editor/Debugger is gray. By default, MATLAB uses system colors, which for some windows managers, is gray. To change the color, select File -> Preferences -> Colors and clear the check box for Use system colors. Then select a new Background color from the palette.
In the Current Directory browser, if you run the Help Report or the Dependency Report and select the option to Show subfunctions, the reports will not be generated if any of the files in the directory produce a runtime error.
On Linux platforms with XFree86 4.x, when Num Lock is on, keys you type might be interpreted as hot keys instead of normal characters. This is because the keystrokes arrive in MATLAB with the META flag set. If you encounter this problem, turn off Num Lock.
If a regular expression contains a parenthesized subexpression which is quantified, and the inner expression is quantified as well, for example '(.+)+'; it can take the parser a long time to determine that a match can not be made. The computational complexity of this problem is exponential with the number of characters in the string that must be tested. In most practical applications, it is not difficult to rewrite the inner expression to be more specific such that each backup doesn't introduce a new set of matches for the outer loop.
If you cut a file from the Current Directory browser, and then paste the file into a file system browser outside of MATLAB, such as Windows Explorer, the file remains in its original folder; the cut is effectively a copy. Use Delete in the Current Directory browser to remove the file from its original location.
You cannot use the Array Editor Cut and Copy items in the Edit menu when you select a portion of the contents in a cell. They act on the entire cell. Instead use Ctrl+V or Ctrl+C, or the context menu items.
In MATLAB 7.0, you cannot save Profiler results for later use by using the Profiler graphical interface. But you can issue the following function to save the results to a file. After profiling, runprofinfo = profile('info')save profile_results profinfoLater, reload the results from the file by runningload profile_resultsprofview(0,profinfo).
On Solaris platforms, non-modal dialog boxes do not stay on top of the parent window. This is especially problematic when the non-modal dialog is completely within the MATLAB desktop area and you then click on the desktop or minimize MATLAB; it is difficult to find the non-modal dialog again. To avoid that situation, keep non-modal dialogs at least partially outside of the MATLAB desktop area.
Viewlet playback demos do not work with Universal Naming Convention (UNC) paths on Windows or Linux platforms for certain Internet browser versions, such as Internet Explorer 5.5 or Netscape 6.2. To make the viewlets play in the browser, map a drive to the specified path for MATLAB (for example, using Windows Explorer).
When you run an M-file that contains an input function, MATLAB
waits for the user to enter data. However, if the Command Window is hidden
behind another window, such as a Figure window, the user might not realize
MATLAB is waiting and it appears MATLAB is hung. Bring the Command Window
forward and provide input to continue.
The ability to drag and drop workspace variables from the Figure Palette into an axes, and thereby generate a plot is not enabled on Linux systems.
The plotting tools not supported on the Macintosh platform. This means the Figure Palette, Plot Browser, and Property Editor do not work these platforms. To use the MATLAB 6 Property Editor, see the propedit command.
If you use the -nojvn option when starting MATLAB, the plotting tools are not available.
If you set your MS-Windows copy options to use a bitmap format, you cannot copy and paste MATLAB figures. As a work around, use a vector format.
The feature (Undo item on the Edit menu) does not always work correctly when using to undo operations performed with the plotting tools.
The -dbitmap option to the print command is not working in Beta 2. See the print reference page for other print options.
You cannot create a .fig file using hgsave if the figure contains data tips.
In Version 5.x, when Building a Subsystem (right-click command) that has continuous sample time and inherited sample time, any Step Size set by the user in the Simulation Parameter Solver dialog will fail to be honored. Instead, the default step size (stop time / 50) is used. This problem does not occur when building the entire model.
If you attempt to close a model during while Real-Time Workshop is generating code or the code is beig compiled, unpredictable things may happen, up to and including segmentation violations. We plan on addressing this issue in a future release, but when using the current release and all prior releases, please do not close a model while a build is in process.
The For iterator block produces uncompilable code when expression folding is on. Expression folding removes all code that would be in the output function and hence the system is completely empty.
Page 9 of the shipped version of Real-Time Workshop 5.0 Release Notes indicates that in generated code,model_private.his sub- included bymodel.h. This is incorrect;model.hdoes not includemodel_private.h.The section "Application Modules for Application Components" on page 7- 33 of the Program Architecture chapter of the Real-Time Workshop documentation also incorrectly states that
model_private.his sub-included bymodel.h.On page 2-9 of “Getting Started with Real-Time Workshop” the section “Building an Application: Summary of Files Created by the Build Procedure” also incorrectly states that
model.hincludesmodel_private.h. The diagram of file inclusions in Figure 2- 12 on page 2-50 is correct, however.
When code is generated for the Look-Up Table 2-D or Look-Up Table 1-D block for floating-point parameters with binary search, extrapolation, and linear interpolation selected, the number and position of repeated zeros is generated explicitly into the generated code. If the breakpoint parameters are then tuned in the real-time code during execution and the number or position of repeated zeros changes, the generated code will in most cases get an incorrect answer when the input for that breakpoint set is near zero.The workaround is to avoid this problem, do not change the number or position of reapated zeros in breakpoint parameters for the Look-Up Table 1-D and Look-Up Table 2-D blocks.
Under Compiler Options on page 9-45 of the Real-Time Workshop Users Guide for Version 5, the following tip is given: "If you do not require double precision for your application, definereal_Tas float in your template make file, or you can simply specify-DREAL_T=floatafter make_rtw in the Make command field."This documentation is not correct. Various circumstances (such as the presence of literal constants) can cause this strategy to fail to remove all doubles from the generated code. The only reliable way to be sure that doubles are absent is to formally propagate single-precision signals in the Simulink model.
The build process can fail during the make compilation phase when all of the following conditions are true: (1) The selected system target file is ert.tlc; (2) the selected template make file is not one of the following: ert_unix.tmf, ert_vc.tmf or ert_lcc.tmf; (3) the "TLC options" edit field of the RTW General options page on the Configuration Parameters window is not empty.
There are two possible temporary workarounds. One is to delete all options from the the "TLC options" edit field. Alternatively, edit matlabroot/rtw/c/ert/ert.tlc and change the 1 to 0 in the following line:
%assign GenUtilsSrcInSharedLocation = 1
This problem will be fixed in the final release.
After clicking the MPT block on a model, if you select Configuration Parameters on the Simulation menu, the Configuration Parameters dialog box does not open. And, then the model will not close. For Beta 2, here is the workaround:This is planned to be fixed after Beta 2.
- With the model open, select Model Explorer on the Tools menu (or type daexplr on the MATLAB command line). The Model Explorer dialog box appears.
- In the Model Hierarchy (left) pane, select the model. The tab selections that are on the Configuration Parameters dialog box are now accessible as items in the middle pane of the Model Explorer dialog box.
- Make the desired selections.
On Linux systems, turning the FVTool grid off or on causes the x-axis and y-axis labels to disappear. The labels also disappear when switching from one response to another. To redraw the labels, resize the GUI.
If you use set on an FVTool object to change the frequency units and then
use get to obtain the frequency range, an error occurs.
When converting from a power spectral density (PSD) to a power spectrum (PS) or vice versa, the plot units do not change to the appropriate units for the converted plot. The units remain the same as the units of the original data.
Using the zerophase function with an odd number of points
causes
the function to error.
Simulink does not allow you to break library links in a configurable subsystem because Simulink needs the links to reconfigure the subsystem when you choose a new configuration. Breaking links would be useful only if you never intended to reconfigure the subsystem in which case you could simply replace the configurable subsystem with a nonconfigurable subsystem that implements the permanent configuration.
Changing the number of an input or output port number in a subsystem can cause an extra port to be added to the subsystem block in the parent system.To fix the problem:
- Copy the contents of the subsystem to the clipboard.
- Delete the old subsystem block.
- Create a new subsystem block in its place.
- Copy the contents from the clipboard to the subsystem.
- Reconnect the subsystem.
In simulation, the Deadzone block outputs NaN when input is NaN while it outputs 0 in Real-Time Workshop code generation. This bug is planned to be fixed in a future release.
If the link to a subsystem is disabled while the library subsystem is open and being edited, then the subsystem does not contain the latest contents from the source. This can lead to synchronization problems.
The new Extract Bits block outputs unsigned integers of various signal widths and values (0 or 1) when the input is Boolean, depending on the settings of the block's parameters.
The Blocksets submenu sometimes fails to appear when selected from the model window's Help menu. If this happens, click anywhere in the model window and then select "Blocksets" from the Help menu.
Current error checking of the block fails to report error on one mode that is not supported, that is, you can set the interpolation method to be 'none-flat' and at the same time set extrapolation method to be 'linear' or 'spline'. These modes should cause updating the diagram to error out, but did not (it is a bug). You can only know something is wrong when you see the code generation failure.
The Repeating Sequence block generates different numbers on Windows than on Linux. The differences are slight: on the order of 1e-16. However, the differences can be significant when simulation results depend on comparing the generated sequence, e.g., to zero. A workaround is to quantize the output of the Repeating Sequence block so that values near 0 become zero. For example, you could put a Dead Zone block with zone [0...1e-15] between the Repeating Sequence block and the block performing the comparison.
The S-function Builder block causes MATLAB to hang if the compiler options file is not set up correctly. To avoid this problem, type the following at MATLAB command prompt to configure the compiler options file:
mex -setup
This is a known problem. Will be fixed in later release. On linux, output is Nan, but on NT output is lower limit if input is Nan.
When discretizing a model in the S domain, you cannot specify a sample time of 0 if the model contains a Transfer Function, State Space, or Zero Pole block. If you do specify a sample time of 0, MATLAB generates an error.
For Beta 2, for some models, to use the Simulink Accelerator, you must have Real-Time Workshop installed.
If the model parameter "Parameters Inline" is deselected ("off"), the accelerated simulation result for enable subsystem blocks can differ from the normal mode simulation.
Using the right-click menus from signal lines in the model to add or remove linearization points, adds the points to the model but does not add entries to theAnalysis I/Os table if the active panel in the Simulink Tools Manager GUI is outside theLinearization Task node.
Command line functions for extracting operating conditions from a simulation of the model at designated times are not yet implemented.
The ability to cut, copy, and paste nodes within a project is not yet enabled. The ability to import a set of operating conditions into the Simulink Tools Manger is not yet enabled. The final version of this product will allow you to import operating conditions from the MATLAB workspace, another open Simulink Tools Manager project, or a MAT-file. The ability to rename a set of operating conditions in the Simulink Tools Manager is not yet enabled. The ability to rename a linearization result in the Simulink Tools Manager is not yet enabled. The ability to save and open Simulink Tools Manager projects is not yet enabled.
When adding blocks to the model diagram after opening the Simulink Tools Manager GUI, any new states, inputs, or outputs in the blocks will not be included in the GUI’s operating conditions tables. To work around this problem, close and then relaunch the Simulink Tools Manager GUI.
Due to a limitation in the internal viewer, scenes that have large scaled worlds might not be displayed correctly.
The workaround is to edit your virtual world through the V-Realm Builder or a text editor. Increase the
visibilityLimitfield of theNavigationInfonode to a number that is greater than the longest distance in the virtual world. For example
NavigationInfo
{
...
visibilityLimit 1e7
...
}