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

Patch 3.4p1 for dSPACE Release 3.4

8-MB Main Memory Support for MicroAutoBox

This patch adds software support for using the whole 8-MB main memory of an 8-MB MicroAutoBox. With the original software on dSPACE Release 3.4, you can use only 2 MB of the main memory.

The following points have to be taken into account:

  • Programs or models that were prepared and compiled for the 2-MB MicroAutoBox do not need to be recompiled.
  • MicroAutoBox has to be updated with the new boot firmware installed with this patch.
  • This patch and the new boot firmware can also be used to work with a MicroAutoBox containing 2-MB main memory.
  • You can check the characteristics of MicroAutoBox's memories via ControlDesk®. Select Platform - Properties in the main menu to display the local RAM size on the memory page.
  • Without this patch, only 2 MB of the 8-MB main memory are supported and shown in ControlDesk.

 

Products Revised by This Patch

This patch is intended for the following dSPACE products on dSPACE Release 3.4 only. It corrects the following problems:

RTLib1003 3.3:

  • DS5001: The duty cycle returned by the function ds5001_pwm2d_overl() does not follow the level of the connected signal if not enough events are available to perform a PWM frequency measurement.

RTLib1005 1.3:

  • DS5001: The duty cycle returned by the function ds5001_pwm2d_overl() does not follow the level of the connected signal if not enough events are available to perform a PWM frequency measurement.
  • DSNVData: Problems with arrays exceeding the size of 256 Bytes, causing a wrong entry in the DSNVData section of the flash memory. The identifier string is affected in such a way that its termination is missing. The corresponding data is not found when read from flash. The affected RTI blocks are STORE_TO_FLASH and RESTORE_FROM_FLASH.
  • Flash1005: The flight recorder unexpectedly stops the data recording.

RTLib1401 1.5.1:

  • DSNVData: Problems with arrays exceeding the size of 256 Bytes, causing a wrong entry in the DSNVData section of the flash memory. The identifier string is affected in such a way that its termination is missing. The corresponding data is not found when read from flash. The affected RTI blocks are STORE_TO_FLASH and RESTORE_FROM_FLASH.
  • Flash1401: The flight recorder unexpectedly stops the data recording.

RTI 4.3:

  • When building a model with the Inline Parameters option enabled and tunable parameters specified, the following error message may appear during loading of the TRC file in ControlDesk: "Encountered a syntax error or semantic error in the TRC file <model>.trc. Please see <model>.err for detailed error information." In the <model>.trc file, there are block entries which contain an uppercase "U" in the address offset, e.g. ([17U] instead of [17]): p_rtP_real_T_0[17U] { type: ArrayDT0_7_1_Col* alias: "ID_FAC_PL_IS__DRI" flags: PARAM } In the generated <model>.err file, the faulty lines are marked with: ^ syntax error: illegal index or array declaration
  • By reopening a model with RTICAN blocks and Stateflow charts, the channel numbers of the RTICAN blocks are incremented automatically.
  • When using Task Transition Read and Write blocks with the input signal of single or integer data type, the Task Transition Read block might output garbage data. In addition, an error like the following occurs: ds1005: Exception at address 0x6AC4: Data access error (27332) Other error messages might also be observed.
  • RTI Task Transition blocks not re-entrant. When a reader or writer block interrupts itself, the real-time simulation might crash and a run-time error occur.

RTICAN 2.0:

  • The following error message is issued by the TLC process: error($DSPACE_ROOT\matlab\rtican\tlc\rtican_postprocess.tlc): 1801 - The == and != operators can only be used to compare values of the same type.

ControlDesk Basic 2.2:

  • Simulink Simulation: Bug in the TRC file generation routine: missing label entries in subsystems and ModelRoot groups (generation of label group works)

ControlDesk Standard 2.2:

  • Experiment Connection Converter: Exception index error after changing the return values of some Python ControlDeskAutomation modules fixed.
  • Event Handling: Events in Operator Mode now work.
  • Plotter and XYPlot Instruments: Instruments now accept more than 100 data connections.
  • Template Instrument: Instrument now accepts the width and height settings via its property page.
  • TableEditor Instrument: When the instrument's automation interface is used, it stores the values to a MAT file correctly. Setting values via the instrument's old automation library now functions correctly.
  • SelectionBox Instrument: Improved appearance of the values in the instrument's list box. The VALUE macro of the instrument's caption now works properly. The instrument now stores its last current value. The Texts property page of the instrument now shows the values correctly.

ControlDesk Test Automation 2.2:

  • Stimulus Editor: If a 3*DS1005 platform was used and a Dual1005 application was loaded, it was not possible to download the SEQ file to the platform using StimulusEditor. When a user tried to download the SEQ file, a message was displayed: "It is not possible to download the SEQ file because the application on the platform does not correspond to the SE file".

MLib 4.4:

  • The MLIB command 'IsApplRunning' formerly returned 1 (true) on DS1005 and DS1104 platforms even if the RT application had been stopped (e.g. from within ControlDesk with 'Stop RTP'). This bug has been fixed.
  • A bug affecting floating network license handling on Windows NT 4.0 has been fixed

 

Installing the Patch

To install the patch, follow these steps:

  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 Patch34p1.exe.
  4. 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 directory %DSPACE_ROOT%\Setup.