ControlDesk 3.7.3p3                     August 2014
Last-Minute Information
======================================================================
Copyright (c) 2014 dSPACE GmbH, Germany



1. General


- This setup can only be installed on an existing ControlDesk 3.7.3 installation.


2. Enhancements


a. Bus Navigator

- RECU attribute in CAN configurations is no longer mandatory.

- The Bus Navigator does not load the application onto the platform any more when the simulation model has been rebuilt, reloaded or replaced. This prevents the same application being loaded twice.


b. Platform Management

- Piggy back modules in a MicroAutoBox are now displayed.



3. Fixed Problems


a. Bus Navigator

- Signal information may be missing in some message layouts.

- LIN monitoring does not work with multiprocessor systems.


b. Data Capture

- It is not possible to save or export capture variables with paths longer than 350 characters.

- Import of capture variables with slashes (/) in names is invalid.


c. Instrumentation

- A layout with dots in name loses connections.


d. Platform Management

- scoutcmd loads applications to FLASH instead of to RAM if ControlDesk is running and an application has been previously loaded to FLASH.

- ControlDesk loads applications to FLASH instead of to RAM if scoutcmd has previously loaded an application to FLASH.

- scoutcmd does not report that the application cannot be loaded if the program on the platform is locked.

- scoutcmd stops the ControlDesk animation in order to load an application onto a multiprocessor system.

- A message box appears if scoutcmd tries to load a multiprocessor application and the program of the multiprocessor system is locked.

- ControlDesk resets the platform and stops the real-time application even if the program on the platform is locked by another application.
- Multiple DS1006 multiprocessor systems with custom names cannot be used simultaneously.

- It is not possible to switch from a bus to a network connection if another dSPACE application is running, e.g., ControlDesk Next Generation (4.x).

- Switching from the network connection with a MicroAutoBox to the bus connection may cause problems with USB on some notebooks.

- Processor units are not sorted properly in the platform view.

- Automatically detected multiprocessor members are all named MASTER.

- It is not possible to register two processor boards as a multiprocessor system if some additional boards are connected to them via Gigalink.

- scoutcmd fails to load an application onto a multiprocessor system if some additional boards are connected to the system via Gigalink.

- ControlDesk may fail to load an application onto a DS1006 platform.

- Cryptic IDs (<#00000000000000...#>) sometimes appear in log entries.

- ControlDesk 3.7.3 reports wrongly that a MicroAutobox II is not connected, if it is locked.

- dSPACE tools, like ControlDesk Next Generation (4.x), lose connection to processor platforms when ControlDesk 3.7.3 starts.

- USB Flight Recorder does not show files with upper-case file extensions.

- ControlDesk 3.7.3 does not recognize a DS1006MC board as a multicore board, if it is registered by ControlDesk NG.

- ControlDesk 3.7.3 does not find processor platforms, if they are registered by both ControlDesk 3.7.3 and ControlDesk Next Generation (4.x) but in different order.

- Automatic FW update fails, if there two or more IO boards with firmware.

- Stand-alone DS2302 and DS2301 boards cannot be registered.

- ControlDesk does not detect automatically the third multiprocessor system.

- Loading an application onto a DS1006 board may fail in certain cases.


e. General

- ModelDesk cannot download parameters onto multiprocessor systems.

- Rtplib may crash on stream-to-disk, if the stream file cannot be opened.