For a better experience on dSPACE.com, enable JavaScript in your browser. Thank you!

Patch 3.1p1 for dSPACE Release 3.1

Patch 3.1p1 is intended for the following dSPACE products on dSPACE Release 3.1, Build-No. 2001070901, only. It corrects the following problems:

ControlDesk® Basic 2.0.1:

  • Framework Application has to be adapted to event handling procedures
  • Platform Management
  • DS1005: Downgrading the boot firmware from Version 1.2 to Versions 1.1.2 and earlier is now possible.
  • DS1401: In flight recorder blocked mode, the last flash block containing data is now cleared.
  • Flight Recorder: Bug in saving flight recorder data in MAT or CSV files fixed.

ControlDesk Standard 2.0.1:

  • Python Base Installation: Crash under Windows 2000 has been fixed.
  • All Real-Time instruments: Display bug has been fixed.
  • Instrumentation: The following bugs have been fixed:
  • Connections to grouped instruments got the wrong instrument during loading. This deleted existing connections and might have produced unexpected effects.
  • When an SDF file was reloaded or removed, the Variable Browser's variable list was not updated. In this case the old variable tree was not released in memory and the "Take Snapshot" feature did not work afterwards.
  • Application Servers:

The reload of an SDF file wasted memory for multiprocessor systems. This problem no longer occurs.

  • Event Handling:
  • On shutdown, no events were fired.
  • Event handler dialog lost focus.
  • CSV File Type:

Bug with erroneous date handling, causing the output to be truncated, has been fixed.

  • Simulink Platform:
  • Handling of mask and workspace parameters
  • Matrices were sometimes scrambled while row and column dimensions were swapped.
  • Variable Browser:

Memory consumption by variable access via Python ControlDesk Automation reduced.

ControlDesk Test Automation 2.0.1:

  • RTPLib: Memory leaks have been fixed.

RTLib1401 1.3.9:

  • The ADC read function may return erroneous values only when the current value is read.
  • When an application is programmed into flash memory an error message is raised after power-up. The error only occurs when the application uses the flight recorder in blocked mode and the flight recorder flash memory is filled.

RTLib1005 1.1.5:

  • After updating the DS1005 firmware to Version 1.2 or higher, it is not possible to flash older applications. The flash problem only occurs with applications built with RTLib1005 up to Version 1.1.5 and ControlDesk up to Version 2.0.1. With ControlDesk 2.1, older applications can be programmed to flash without problems after the firmware update.

RTI1003 3.6.1:

  • Timer Task Assignment block used with RTI-MP causes compiler or download error. The connected HW interrupt block unintentionally generates initialization code on the slave CPU. Applies only in conjunction with DS4002, DS4201, DS4201S, and S5101 HW interrupt blocks.
  • When the DS1005, DS4201S or DS2210 serial blockset is used, interprocessor interrupts do not work with RTI-MP. You cannot transmit interrupts from source CPU to target CPU using the interrupt blocks DS1005SER_INT_Ix, DS2210SER_INT_Bx_Ix or DS4201SER_INT_Bx_Cx_Ix.
  • The build process aborts with an error message if the generation of mask and workspace parameters is selected and if the model contains mask parameters containing certain characters, for example a ' (transpose operator).
  • When there is a Stateflow® system inside a masked subsystem, no (mask parameter) code is generated for any blocks inside that subsystem.
  • If the model uses vectorized Data Store Memory blocks, it may happen that ControlDesk reports a syntax or semantic error for a data store memory variable (rtDSM) in the model's TRC file.
  • If a serial block resides in an atomic subsystem whose code is generated to an extra file or if the block resides in a subsystem which is triggered by a Stateflow block, compiler errors could occur.

RTI1005 3.6.1:

  • Timer Task Assignment block used with RTI-MP causes compiler or download error. The connected HW interrupt block unintentionally generates initialization code on the slave CPU. Applies only in conjunction with DS4002, DS4201, DS4201S, and S5101 HW interrupt blocks.
  • When the DS1005, DS4201S or DS2210 serial blockset is used, interprocessor interrupts do not work with RTI-MP. You cannot transmit interrupts from source CPU to target CPU using the interrupt blocks DS1005SER_INT_Ix, DS2210SER_INT_Bx_Ix or DS4201SER_INT_Bx_Cx_Ix.
  • The build process aborts with an error message if the generation of mask and workspace parameters is selected and if the model contains mask parameters containing certain characters, for example a ' (transpose operator).
  • When there is a Stateflow system inside a masked subsystem, no (mask parameter) code is generated for any blocks inside that subsystem.
  • If the model uses vectorized Data Store Memory blocks, it may happen that ControlDesk reports a syntax or semantic error for a data store memory variable (rtDSM) in the model's TRC file.
  • If a serial block resides in an atomic subsystem whose code is generated to an extra file or if the block resides in a subsystem which is triggered by a Stateflow block, compiler errors could occur.

RTI1102 3.6.1:

  • The build process aborts with an error message if the generation of mask and workspace parameters is selected and if the model contains mask parameters containing certain characters, for example a ' (transpose operator).
  • When there is a Stateflow system inside a masked subsystem, no (mask parameter)code is generated for any blocks inside that subsystem.
  • If the model uses vectorized Data Store Memory blocks, it may happen that ControlDesk reports a syntax or semantic error for a data store memory variable (rtDSM) in the model's TRC file.

RTI1103 3.6.1:

  • The build process aborts with an error message if the generation of mask and workspace parameters is selected and if the model contains mask parameters containing certain characters, for example a ' (transpose operator).
  • When there is a Stateflow system inside a masked subsystem, no (mask parameter) code is generated for any blocks inside that subsystem.
  • If the model uses vectorized Data Store Memory blocks, it may happen that ControlDesk reports a syntax or semantic error for a data store memory variable (rtDSM) in the model's TRC file.
  • If a serial block resides in an atomic subsystem whose code is generated to an extra file or if the block resides in a subsystem which is triggered by a Stateflow block, compiler errors could occur.

RTI1401 3.6.1:

  • The build process aborts with an error message if the generation of mask and workspace parameters is selected and if the model contains mask parameters containing certain characters, for example a ' (transpose operator).
  • When there is a Stateflow system inside a masked subsystem, no (mask parameter) code is generated for any blocks inside that subsystem.
  • If the model uses vectorized Data Store Memory blocks, it may happen that ControlDesk reports a syntax or semantic error for a data store memory variable (rtDSM) in the model's TRC file.
  • If a serial block resides in an atomic subsystem whose code is generated to an extra file or if the block resides in a subsystem which is triggered by a Stateflow block, compiler errors could occur.

If you use one or more of these products from Release 3.1, it is recommended that you install Patch 3.1p1. 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.1p1
Download Patch 3.1p1 (2.9 MB) and save it to your hard disk.
Installing the Patch
1. 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.
2. Reboot the system.
3. Change to the drive and directory containing the patch. Invoke 31p1.exe.
4. 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.

Download
Installation Notes (10KB)
31p1.exe (3003KB)