ControlDesk 3.7.2p4 June 2014 Last-Minute Information Copyright (c) 2014 dSPACE GmbH, Germany 1. General This setup can only be installed on an existing ControlDesk 3.7.2 installation. 2. Enhancements a. Data Capture - Access to MicroAutoBox during animation has been optimized. b. 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. c. Platform Management - Piggy back modules in a MicroAutoBox are now displayed. 3. Fixed Problems a. Automation - Clearing the flash with cdautomationlib does not work for a MicroAutoBox. - Layouts.Save() of the cdautmationlib.Instrumentation does not work. - PythonWin crashes if the Convert method from the idfconverter module is called. - Python scripts generated by the Stimulus Editor are not Python 2.5 compliant. b. Bus Navigator - Incomplete error report is shown if the user tries to create a message layout whose path name would exceed 260 characters. - No bus configurations can be created for models containing only free raw messages. - No bus configurations can be created for a model containing patch, alpha or beta versions of the RTILINMM. - A bus configuration from a copy of an experiment still references the model from the original experiment. - Signal information may be missing in some message layouts. c. Data Capture - It is not possible to save or export capture variables with paths longer than 350 characters. - Capture from slaves of a multiprocessor system does not run if all the capture variables of the master subsystem are deselected. d. Failure Simulation - The Excel file in the demo model %DSPACE_ROOT%\Demos\ControlDesk\ControlDeskTestautomation\AccessingExternalDevices\FailureSimulation\MidSizeBasedOnDS2211 does not contain a macro for CSV files. - Parsing a failure simulation for DS1450 with zero port address leads to an error. e. Instrumentation - A layout with dots in name loses connections. f. Parameter Editor - Memory leaks when single parameters are read or written using cdautomationlib. - Some Parameter Editor entries may be missing in the experiment file if the experiment has been saved in another folder. g. 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. - Refreshing the platform connection sometimes restarts DS1006 boot firmware even if an application is running. - An unspecified error is reported if the user tries to load an application to the flash memory of a switched-off multiprocessor system. - After the application in the MicroAutoBox flash has been cleared using cdautomationlib, the Clear Flash Memory dialog still displays the old application. - Verify Boot Firmware does not report the result of the verification. - A corrupted Gigalink topology is displayed if unregistered processor boards are connected to a multiprocessor system. - 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. - ControlDesk 3.7.2 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.2 starts. - USB Flight Recorder does not show files with upper-case file extensions. - ControlDesk 3.7.2 does not recognize a DS1006MC board as a multicore board, if it is registered by ControlDesk NG. - ControlDesk 3.7.2 does not find processor platforms, if they are registered by both ControlDesk 3.7.2 and ControlDesk Next Generation (4.x) but in different order. - Automatic FW update fails, if there are 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. h. General - ModelDesk cannot download parameters onto multiprocessor systems. - Rtplib may crash on stream-to-disk, if the stream file cannot be opened.