Known Software and Documentation Problems

This document describes important known software and documentation problems:

Communications Blockset

Click on a problem area listed below for details.

Several Communications Blockset blocks are incompatible with Real-Time Workshop
Several Communications Blockset demos are incompatible with Real-Time Workshop

Several Communications Blockset blocks are incompatible with Real-Time Workshop

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:

Several Communications Blockset demos are incompatible with Real-Time Workshop

Several Communications Blockset demos are incompatible with Real-Time Workshop. As a result, Real-Time Workshop cannot generate code for these demos:

Communications Toolbox

Click on a problem area listed below for details.

Galois field manipulations cannot be compiled
Incorrect name of data file in printed documentation

Galois field manipulations cannot be compiled

The Galois field data type is not compatible with the MATLAB Compiler.

Incorrect name of data file in printed documentation

The section "Speed and Nondefault Primitive Polynomials" in the printed manual refers to a MAT-file called gftable.mat. It should say userGftable.mat. The online documentation uses the correct filename.

Dials & Gauges Blockset

Dialog box images in documentation for off-block controls show extra field

The "Placing ActiveX Controls in a Different Window" chapter of the documentation shows several images of the Block Parameters dialog box for off-block gauges. These images incorrectly show a field called "Event on which to output" that is not in the actual dialog box for off-block controls.

DSP Blockset

Sine Wave block "Best precision" error

If you select "Best precision" for the "Number of fractional bits" parameter in the Sine Wave block, you may obtain incorrect results. The resulting value will most likely be correct, however the output of the block may not be of best possible precision.

Embedded Target for TI C6000 DSP

Click on a problem area listed below for details.

Broken links for Reset blocks
Cannot generate code for DSP Blockset blocks that don't have TLC files
No online help for the targetting demos

Broken links for Reset blocks

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).

Cannot generate code for DSP Blockset blocks that don't have TLC files

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.

No online help for the targetting demos

The demonstration programs for the Embedded Target for TI C6000 DSP do not have descriptions available. You see only the name of the demo and a link to open the demo when you select a demo on the Demo tab in the Help browser. This includes: --Wavelet denoising demos --Reverberation demos --Quick Test demos --DIP Switch control demos --Automatic Gain Control demos

Filter Design Toolbox

Two demos error in PLAYSHOW mode

The "Run this demo" links on the introductory pages for the Fixed-Point Number Definition and Filter Quantization Noise Power demo programs do not work. Selecting the links is equivalent to the following commands at the MATLAB prompt:
playshow numbercircledemo
playshow noisepowerdemo

These two demos--Fixed-Point Number Definitions and Filter Quantization Noise Power--work only when viewed in the help browser. They generate errors when you run them as playshow demos. (Refer to demos in MATLAB online help for more information about playshow). Avoid the errors by viewing the demos in the Help browser only.

Fixed-Point Blockset

Internal rule will not work all the time for unified blocks without a Fixed-Point Blockset license

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 an int8 to an int16 and you choose the internal rule. The internal rule tries to check out an sfix(24), which causes the model to error due to licensing issues. Similarly, if you multiply an int8 by an int32 and choose the internal rule, the output container will be an sfix(40), which will cause the same problem.

MATLAB

Click on a problem area listed below for details.

Font not found warning on Linux
Help browser error when searching the Technical Support Online Knowledge Base
Help browser links sometimes display at wrong part of page
Keys misinterpreted on Linux with XFree86 4.x
Limited functionality of dos/! commands with ">," "<", "|" on Windows 98/ME
Netscape browser doesn't open
No file filters in Open and Save dialog boxes on UNIX platforms
Selection problems in Help browser
Solaris non-modal dialog boxes do not stay on top of parent dialog box
Viewlet playback demos do not work using UNC paths

Font not found warning on Linux

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.

Help browser error when searching the Technical Support Online Knowledge Base

When you search the MathWorks Technical Support Web site from the Search tab of the Help Browser, using the Online Knowledge Base search type, the results appear in the display pane. However, if you then search the Technical Support Web site from the site's search field, you get an error. Instead, search again from the Search tab of the Help Browser. This error also occurs when you go to the Technical Support Web site using the Help browser using another method and try to search it, such as by directly entering the Technical Support Web site URL in the Help browser.

Help browser links sometimes display at wrong part of page

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.

Keys misinterpreted on Linux with XFree86 4.x

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.

Limited functionality of dos/! commands with ">," "<", "|" on Windows 98/ME

On Windows 98 and ME platforms, the redirection operators ">", "<" and "|" have limited functionality when used in DOS commands (via the dos function or the ! operator). If used with a DOS primitive (such as dir or type), 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% /c to the beginning of the DOS command, as in this example

! %comspec% /c ping.exe -n 2 localhost > ping.txt

Netscape browser doesn't open

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 the web function 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 called lock in the .netscape directory. To correct the problem, delete the lock file.

No file filters in Open and Save dialog boxes on UNIX platforms

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.

Selection problems in Help browser

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.

Solaris non-modal dialog boxes do not stay on top of parent dialog box

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 using UNC paths

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).

MATLAB and Simulink Report Generator

Print sometimes throws an exception and does not print without first clicking on the display pane

"Print" on Report Generator (through button, or menu File -> Print) will throw an exception and not print. The workaround for this is to click on the report display to give it focus before printing.

MATLAB Link for Code Composer Studio

Click on a problem area listed below for details.

Cannot cast a pointer to any other data type representation
Code Composer remains in memory after an Rtdx.Open on illegal channel
Export to Code Composer Studio from FDATool does not work for cascade and parallel filters
READ REGISTER NUMERIC has source file typographical error

Cannot cast a pointer to any other data type representation

An attempt to cast a pointer in any datatype causes the following error:- ??? Error: File: D:\work\R12\toolbox\ccslink\ccslink\@ccs\@pointer\cast.m Line: 1 Column: 17 "identifier" expected, "=" found. There is no work around for this problem curently.

Code Composer remains in memory after an Rtdx.Open on illegal channel

Normally, If Code Composer is invisible and all links are deleted, the Code Composer task (cc_app.exe) will go away. This issues seems to break this standard COM behavior. This problem will occur if an unrecogized RTDX channel is accidently openned. For the RTDX open to succeed, the channel must exist in the most recently downloaded the program file. If open is attempted on an illegal channel, a normal MATLAB error message is produced and no problems are encountered using the link. However, after closing the link, cc_app.exe will persist in memory. To avoid this problem, be sure the correct program file has been loaded and avoid attempts to open illegal channels. If an illegal channel is open by mistake, start the task manager and peform an end process on "cc_app.exe".

Export to Code Composer Studio from FDATool does not work for cascade and paralle filters

If the current filter of FDATool is either a cascade or parallel filter, the Export to Code Composer Studio menu item will be disabled.

READ REGISTER NUMERIC has source file typographical error

This typo causes the deref on a REGISTER POINTER object not to work and throw a bogus error. Also the read on a REGISTER Numeric, String, Pointer and Enum will throw a bogus error if you specify an index of [] or 1. However specifying an invalid index (i.e., >1) gives a legitimate error message. For example,

deref(handle_register_pointer) errors out.
read(handle_rnumeric, []) OR read(handle_rnumeric, 1) errors out.

However, read(handle_rnumeric, [], timeout) works properly but read(handle_rnumeric, 1, timeout) does not work.

Model-Based Calibration Toolbox

Click on a problem area listed below for details.

Changing a table that is in a Tradeoff causes an error
Normaliser tables allow invalid inputs

Changing a table that is in a Tradeoff causes an error

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.

Normaliser tables allow invalid inputs

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.

Signal Processing Toolbox

Click on a problem area listed below for details.

Converting Cascade/Parallel dfilt Structures
Data markers on Magnitude and Phase plots
Data markers on multiple roots in Pole/Zero plots

Converting Cascade/Parallel dfilt Structures

You cannot convert a cascade/parallel dfilt of non-homogeneous filters to a quantized filter object (qfilt). You also cannot convert a cascade/parallel dfilt structure that contains cascades/parallels to a qfilt. qfilts are available only with the Filter Design Toolbox.

Data markers on Magnitude and Phase plots

When displaying the Magnitude and Phase plot in FDATool or FVTool, data markers can be added only to the Phase plot.

Data markers on multiple roots in Pole/Zero plots

You cannot display data markers on points where multiple roots exist in FDATool or FVTool Pole/Zero plots.

Simulink

Click on a problem area listed below for details.

Help->Blocksets submenu sometimes fails to appear
S-Function Builder causes MATLAB to hang if mex is not setup correctly
Simulink Scope will not update time offset when "Tick Labels" are set to "Bottom Axis Only"
Zero sample time limitation on discretizing models in the S domain

Help->Blocksets submenu sometimes fails to appear

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.

S-Function Builder causes MATLAB to hang if mex is not setup correctly

The S-function Builder block causes MATLAB to hang if the compiler options file is not setup correctly. To avoid this problem type the following at MATLAB command prompt to configure the compiler options file:

mex -setup

Simulink Scope will not update time offset when "Tick Labels" are set to "Bottom Axis Only"

The Simulink Scope has three modes for its "Tick Labels," which can be set in the scope parameters dialog box. The three settings are "all," "none", and "Bottom Axis Only" (the default). Using the third (default) setting triggers a bug in which the "Time Offset" in the bottom, left corner of the scope does not update properly. To work around this setting, set the "Tick Labels" to "all".

Zero sample time limitation on discretizing models in the S domain

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.

Simulink Accelerator

Code Generation Failure in Nested Directories Under Windows 98

This note describes a limitation affecting both Simulink Accelerator and Real-Time Workshop, under Windows 98. The problem is due to a limitation of Windows 98. If the present working directory (pwd) is a folder nested in 7 or more levels, Real-Time Workshop (or Simulink Accelerator) cannot generate code. The workaround is to connect to a higher-level (less deeply nested) directory before initiating the build process.

Virtual Reality Toolbox

Click on a problem area listed below for details.

Animation of virtual scenes
blaxxun Contact Version 4.4
Converting VRML1.0 to VRML97
Installing blaxxun Contact
Script nodes are not supported for the Virtual Reality Toolbox viewer on SGI platforms
Spaces in the names of inlined VRML files

Animation of virtual scenes

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.

blaxxun Contact Version 4.4

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.

Converting VRML1.0 to VRML97

Since some VRML worlds are automatically generated in VRML1.0 and the Virtual Reality Toolbox does not support VRML1.0, you need to save these worlds in the current standard for VRML, VRML97. For PC platforms, you can convert VRML1.0 worlds to VRML97 worlds by opening the worlds in V-Realm Builder and saving them. V-Realm Builder ships with the PC version of the Virtual Reality Toolbox. Other commercially available software programs can also perform the VRML1.0 to VRML97 conversion.

Installing blaxxun Contact

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.

Script nodes are not supported for the Virtual Reality Toolbox viewer on SGI platforms

Script nodes sometimes cause segmentation violations when used with the Virtual Reality Toolbox viewer on SGI platforms. Script nodes exist in the more complex virtual worlds such as the Virtual Reality Toolbox examples vrcrane and vrlights. If you want to work with virtual worlds containing script nodes, use Cosmo Player for SGI.

Spaces in the names of inlined VRML files

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"