Several Communications Blockset blocks are incompatible with Real-Time Workshop. As a result, Real-Time Workshop cannot generate code for models that include these blocks:
- Continuous-Time Eye and Scatter Diagrams
- Multipath Rayleigh Fading Channel
- Rician Fading Channel
- Triggered Read from File
- Triggered Write to File
- Integer-Input RS Encoder
- Integer-Output RS Decoder
- Binary-Input RS Encoder
- Binary-Output RS Decoder
- Blocks in the CPM sublibrary of the Digital Baseband sublibrary of the Modulation library
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
- Bluetooth Voice Transmission
- CPM Phase Tree Example
- Digital Video Broadcasting Model
- Discrete Multitone Signaling
- Filtered QPSK vs. MSK
- GMSK vs. MSK
- Rayleigh Fading Channel
- WCDMA Coding and Multiplexing Example
- WCDMA End-to-End Physical Layer
- WCDMA Spreading and Modulation Example
The Galois field data type is not compatible with the MATLAB Compiler.
The DSP Blockset 5.0 version of the Cumulative Sum block is currently not backwards compatible with the version from DSP Blockset 4.1 (Release 12).The new version of the block does not behave the same as the previous version when given a frame-based input and set to sum along columns. To set the new version to behave the same as the previous version this setting, set the new version to sum along channels rather than columns.
Background: Most C-mex s-function blocks generate code via a parallel implementation in the TLC language. If a block does not have a TLC file, then RTW knows a few ways to still incorporate it into the generated code, but the result does not perform as well as if there were TLC. The DSP Blockset has a handful of blocks (mostly in the Linear Algebra category) without TLC implementations.
Bug: TLCless blocks do not work with the TI EVM Target. The CMEX S-function is missing from the Code Composer project.
If you try to open an old model (i.e., one created with the Developer's Kit for Texas Instruments DSP) with Release 13 and the Embedded Target for C6000 DSP 1.0, you may have a problem with Reset blocks. The names of these blocks have changed, and the result is a red outline on the block and the text "Bad link". To fix the library link, double-click on the block and change the "Source block" parameter from c6701evmlib/Reset C6701 EVM to c6701evmlib/Reset (replacing C6701 EVM with C6711 DSK if applicable).
Many Fixed-Point Blockset and unified blocks have an "Inherit via internal rule" selection for the "Output data type mode" parameter. Currently, these blocks may not function properly if you make this parameter selection while using built-in data types and without having a Fixed-Point Blockset license. When using the internal rule, the block may try to register a fixed-point data type even if you are using built-in data types. If you do not have a Fixed-Point Blockset license, you then get an error stating that you do not have the proper license, even though you are not using fixed-point data types. For example, suppose you try to add anint8to anint16and you choose the internal rule. The internal rule tries to check out ansfix(24), which causes the model to error due to licensing issues. Similarly, if you multiply anint8by anint32and choose the internal rule, the output container will be ansfix(40), which will cause the same problem.
Because most FIS contain Min, Max, and other blocks with zero-crossing detection, the default ODE solver can perform poorly in some cases.Two remedies are available:
- Choose a stiff solver. Several choices are available on the Solver page of the Simulation Parameters dialog box in Simulink.
- Disable zero crossing detection on the Advanced page of the Simulation Parameters dialog box
On the Linux, SGI, and Alpha platforms, when the preference for key bindings in the Editor is set to Emacs, Ctrl+Shift+t should uncomment selected lines but instead does nothing. To uncomment selected lines, select Text -> Uncomment.
For some Linux configurations, on MATLAB startup, several warnings of the form:
Font specified in font.properties not found ...
may 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.
In the Help browser, when you click a link in a displayed page, sometimes the correct page displays but it is scrolled to the wrong part of the page. To quickly go to the correct part of the page, use the back arrow button in the Help browser toolbar to return to the page that contained the link, and click the link again. The page you linked to appears, scrolled to the correct part of the page.
On UNIX platforms, in the Help browser, when you click a PDF file, it does not display if the PDF reader location is not specified or is incorrect. To resolve the problem, select File -> Preferences -> Help. Enter or correct the PDF reader location. Use the ... button to browse your file system to select the location.
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.
The M-file help for the rotate3d functions states that you
can double click on the figure to return to the original view. This is not
correct.
In the Help browser display pane, when you try to select code from an example in the documentation, the entire line is automatically selected. You cannot select just part of the line. Similarly, with the Find in page feature, if the term you are looking for appears in code, the entire line of code is selected rather than just the term. If you have trouble selecting content in the Help browser, try moving the cursor closer to the start of the area you want to select. If the cursor is on white space rather than on content, it will not begin the selection.
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.
The serial port is not locked by MATLAB, so other applications or other instances of MATLAB can access the same serial port. This may result in a conflict.
On Windows 98 and ME platforms, the redirection operators ">", "<" and "|" have limited functionality when used in DOS commands (via thedosfunction or the ! operator). If used with a DOS primitive (such asdirortype), they will function, so that
! dir > dir.txt
works fine.
But if used with a .exe file, they will not work. For example,
! ping.exe -n 2 localhost > ping.txt
will fail with a message from ping stating that ">" is a bad input.
This can be fixed by prepending%comspec% /cto the beginning of the DOS command, as in this example
! %comspec% /c ping.exe -n 2 localhost > ping.txt
If your system's Web browser is Netscape and it is not open, you may have a problem when you try to go to a Web page from within MATLAB. For example, when you select an item from the Web menu, the selected page should appear in Netscape, but Netscape does not open. This might also happen when you run thewebfunction or follow links to The MathWorks Web site or other URLs from the Help browser. The problem may be due to a Netscape lock file. If Netscape has previously crashed, it creates a file calledlockin the.netscapedirectory. To correct the problem, delete thelockfile.
On UNIX platforms, the Open and Save dialog boxes do not allow you to select the Files of Type, so all file types are always shown.
On Solaris platforms, non-modal dialog boxes do not stay on top of the parent dialog box. 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.
When you run lookfor, results do not automatically display in
the Command Window. Press Ctrl+c to display results.
When you open a GUI that is not on the MATLAB path using theguidecommand, MATLAB might display an error message. For example, enteringguide('C:\Work\my_gui')might display an error message if theWorkdirectory is not on the MATLAB path. GUIDE loads the GUI correctly, so you can ignore the error message.
When you open an example GUI in the GUIDE documentation by clicking a link in the Help Browser, MATLAB might display an error message. GUIDE loads the GUI correctly, so you can ignore the error message.
Function 'main' behaves differently when run. It overwrites the location where the return address is stored, thus returning to a different place in memory after execution.
Once a table has been added to a Tradeoff Calibration study, changing its properties from elsewhere, for example by changing the table size in the Calibration Manager, may cause an error in CAGE. To avoid the error first delete the Tradeoff, then edit the table and then construct a new Tradeoff using the changed table.
When you edit values in the Output column of a Normaliser table, the table will constrain the value you type to be displayed as an integer. However it does not correctly constrain the value that is saved internally, so the accompanying graph is updated to show the typed value. Normaliser outputs should be constrained to be integers, so typing in a non- integer value may lead to errors in CAGE. The Normaliser graph, which can also be used to edit the breakpoints, correctly constrains the saved value to be an integer.
When displaying the Magnitude and Phase plot in FDATool or FVTool, data markers can be added only to the Phase plot.
You cannot display data markers on points where multiple roots exist in FDATool or FVTool Pole/Zero plots.
SimMechanics will rebuild the accelerator shared object/dll on every simulation.
The blaxxun Contact VRML plug-in can fail to update the virtual scene when used with the Virtual Reality Toolbox 3.0 and Microsoft Internet Explorer 5.5 and above. Netscape users do not experience this problem. If you are using Internet Explorer 5.5 or above, you must manually change a network security setting before you use the blaxxun Contact plug-in with the Virtual Reality Toolbox 3.0. To view the procedure for changing your default network security settings, please see "Installing a VRML Plug-in (Windows)" in the Virtual Reality Toolbox documentation.
The Virtual Reality Toolbox Version 3.0 is most stable with blaxxun Contact Version 4.4. We do not recommend upgrading to blaxxun Contact Version 5.0.
If you have the MATLAB Web Server installed on your machine, you must stop the MATLAB Web Server before installing the blaxxun Contact plug-in.
The VRML97 standard allows you to include objects, which are defined in different files, in the main virtual scene. This functionality is performed by the Inline node. Although it is not forbidden by the VRML97 standard, the Virtual Reality Toolbox does not allow spaces in the file names used to define inlined objects. Example of incorrect Inline node definition: DEF my_object Transform { center 0 10 0 children Inline { url "MY OBJECT.WRL" } } The correct URL string is: url "MY_OBJECT.WRL"