DS1005 applications which use the DS2210 slave DSP or DS2210 wave tables do not work properly when they are booted from flash memory. In this case the slave DSP application and/or wave tables are not loaded. Additionally, loading such an application to flash can cause a verify error. It can also destroy the boot firmware and lock the flash. In this case the flash can be cleared with ClearFlash1005. The procedure is described in ClearFlash1005.txt, which is copied to the ReadMe folder.

RTLib1401 1.3.7:

When a machine check exception occurs, MicroAutoBox may crash. A machine check exception is generated when the main processor or the MicroAutoBox case becomes overheated or the watchdog is not cleared in the preset time interval.

The Flight-Recorder handling in "Discard new data" mode differs from the handling under CD 2.2. If a task contains more than 46 DS1401REC blocks, data may be lost.

ControlDesk® Basic 2.0:

DS1005 support: During firmware update on a DS1005 board without the DS910 Gigalink Module, the error message: 'Platform: Timeout while reading board status. Config section is not valid.' no longer appears.

Experiment Manager:

ZIP archives are created using a file name format that is not fully compatible with other ZIP tools (e.g. WinZip). This affects only ZIP archives containing file names with umlauts and/or other special characters.

Files that are removed from an experiment during the consistency check may still be displayed in the experiment navigator with no means of removing them.

Simulink® Simulation: Various minor bug fixes.

ControlDesk Standard 2.0:

Parameter Editor: The Parameter Editor now handles the values "+Inf" and "-Inf" correctly. A problem with the automation interface has also been fixed. Source and destination files are not mixed when parameter files are merged.

All Real-Time instruments: Copy to Clipboard is now possible via Python.

While a reference signal is dragged over an instrument, a lot of memory gets lost.

Event connections are not marked as invalid when the trigger event does not exist.

When the Save button is pressed, a layout document is saved only if it has been modified.

Dropping variable(s) on a selection of instruments is aborted after a connection could not be built.

Errors that occurred during "Import Connections" are not displayed in a message box.

The file dialog for selecting a script file to write event handler backup code to is an Open dialog.

Highlight Variables does not work when a grouped instrument is selected or when another instrument is selected via the TAB key.

After a new layout with instruments and connections is created, the connections do not work if the layout is saved under its default name.

Experiment Connection Converter: The connections from DSM blocks (data store memory) and from user-defined TRC files are now convertible. A problem with path information inside SDF files has also been fixed. Additionally, the captions of all instruments are set to the macro "{%BLOCK%}/{%VARIABLE%}".

Event Handling:

Experiment events are now available from the event "On_ExperimentManager_OpenExperiment" to "On_ExperimentManager_CloseExperiment".

Experiment events are now sent if the experiment is opened via a command line parameter.

Events are now asynchronous, i.e. you can close a layout in an instrument event handler.

ControlDesk Test Automation 2.0:

Stimulus Editor: The Stimulus Editor now handles the slash symbol ("/") in variable names correctly. To correct the problem with existing Stimulus Editor documents created with ControlDesk 2.0, you must reassign the affected variables.

Demos for ControlDesk 2.0:

Problems with the demo for using the Python module "iocilib" (accessing external devices) have been fixed.

In linked systems, numeric block handles are sometimes changed during system initialization. This leads to an invalid block handle error during the build process.

Setting the storage class of signals coming from virtual blocks to ImportedExtern or ExportedGlobal results in incorrect TRC entries. These signals cannot be accessed within ControlDesk.

When online help is called for RTICAN (DS1401) from the RTICAN library or RTICAN GUI, the wrong RTICAN help is opened.

Minor bug fix in support of mask and workspace parameters for ControlDesk.

RTI-MP 3.6 / 4.0:

Minor bug fix in support of mask and workspace parameters for ControlDesk.

RTICAN 1.4 / 1.5:

Reopening a model with RTICAN blocks and Stateflow® Charts automatically increments the channel numbers of the RTICAN blocks.

DS1103 RTI Reference documentation:

The termination resistance cannot be specified for the DS1103. (Radio buttons in the RTICAN CONTROLLER SETUP block are disabled). The description in the original documentation was wrong.

DS1401 RTI Reference documentation:

The termination resistance cannot be specified for the DS1401 (MicroAutoBox). (Radio buttons in the RTICAN CONTROLLER SETUP block are disabled). The description in the original documentation was wrong.

The correct Help file is now opened when the RTICAN online help for RTI1401 is called from within the RTICAN library or the RTICAN user interface.

If you use one or more of these products from Release 3.0, it is recommended that you install Patch 3.0p1. Please remember that you have to reinstall the patch after reinstalling dSPACE software.

NOTE: Do not use this patch for releases other than those stated in the header. If in doubt, make sure that the Build-No. given matches your CD Build-No.Preparing Patch 3.0p1
Download Patch 3.0p1 (9.4 MB) and save it to your hard disk. Installing the Patch
Install the dSPACE software from your CD. Make sure that the version and Build-No. of your CD match the information given in the header of this file.Reboot the system.
Change to the drive and directory containing the patch. Invoke 30p1.exe.
For Windows 9x only: Reboot the system again. NOTE: You need to close any dSPACE software and MATLAB® before invoking the patch.The software patch also generates an entry in the dSPACE.vs file for each product being patched, which can be accessed via the dSPACE Installation Manager.
Log files are also generated in the %DSPACE_ROOT%\Setup directory.