ControlDesk 3.5p3 February 2011 Last-Minute Information ====================================================================== Copyright (c) 2011 dSPACE GmbH, Germany Contents: 1. General 2. Problems Fixed by This Patch 3. Limitations 4. Installing the Patch 1. General ---------------------------------------------------------------------- This patch can only be installed on an existing ControlDesk 3.5 installation (dSPACE Release 6.5). 2. Problems Fixed by This Patch ---------------------------------------------------------------------- a. Platform Management The loss of network connection to an expansion box with a slot CPU is repeatedly reported. Firmware management is not disabled during CAN replay so it may interfere with CAN replay. Firmware management is not disabled during CAN monitoring so it may interfere with CAN monitoring. When rebooted, MicroAutoBox enters the running state even if there is no application in the flash. The DS1005 and DS1103 processor boards in the network expansion box are not grayed out in the Platform View when they are no longer available. Loading applications from a single SDF file onto a DS1006 processor board and the associated DS2302 I/O board fails. Messages in dSPACE.log from DS2302 or DS2301 contain wrong board name: "ds230x (unregistered)" instead of "ds2302" or "ds2301". The warning dialog " have been changed" is sometimes placed at back (displayed in background). The clock frequency of a DS1006 Processor Board and its unit in the Support Info file do not match: the value is given in MHz, but the unit is "GHz". The second DS2302 board in a DS1006 multiprocessor system is wrongly displayed as unregistered. Wrong error message is displayed when one MicroAutoBox is replaced by another. The required firmware version is missing in the error message that the firmware does not fit the application to be loaded. Real-time messages from certain modules contain wrong module names. ControlDesk shows the wrong run state of a MicroAutoBox (DS1401). MATLAB/Simulink run-time error occurs on synchronization of the properties on the Simulink property page. Stimulus Editor (SE) files cannot be loaded onto the Simulink platform. It is not possible to register processor platforms, if Toggle42.ocx is deregistered. The property dialog for the DS802 PHS Link Board does not show the serial number and port properties. b. Instrumentation Status bar displays wrong text when certain Instrumentation menu options are selected. Help button on the General Properties --> Animation page is disabled. Layout scrollbars are sometimes missing. Coordinates of the plotter cursors are incompletely displayed. c. Parameter Editor, Variable Browser and Reference Data Manager Messages from the Parameter Editor contain quotation marks in parameter path names. When two processor boards of the same type are available and two SDF files are loaded, the second board is not assigned by default to the second SDF file. A vector consisting of two elements cannot be edited. Variable Browser does not display flags of variables by default. Vectors and matrices are not marked in the variable list although Highlight Variables is selected. The second time Replace SDF File is used, the user is prompted to reassign the board, which is not necessary. Parameter Editor does not check parameter ranges specified in the TRC file. The dialog to confirm board assignment is displayed, if cdautomationlib.VariableBrowser.Replace() is called twice. Path names of parameters in the messages of the Parameter Editor contain quotation marks. No board is assigned to the second SDF file, even if there is one more board available. Parameter Editor may sporadically crash (hardly reproducible). No error is reported on an attempt to write a single parameter while the application is not running. An array variable in the variable list cannot be expanded, if the Variable column is too narrow to display the whole name of the array. MATLAB workspace parameters are not found in the Model Root Parameter group. d. Bus Navigator A message box asks whether the user would like to save the open bus configuration, even if the call for closing is automated. An incorrect error is displayed stating that the RTICANMM file could not be found, if the RTILINMM file is missing. The monitoring window shows the name of a signal specified in the first database, even if another database is activated which also contains a signal with the same ID but a different name. If a replay-enabled bus configuration is loaded on a 1006MC system, the toolbar buttons for starting and stopping replay are incorrectly disabled, although replay is possible from the context menus of the respective replay nodes. It is not possible to create a CAN monitor at the level of an MP system node. Attempting to open the Edit Data Connections dialog for an instrument connected to a UDDB message signal can cause ControlDesk to freeze if the network connection is used. Overwriting a log file belonging to the administrator on Windows 7 throws an exception if the user has restricted rights for that file. Multiply selected messages in the filter grid are not moved properly using the Down Arrow. A message in the filter grid is deselected if the Up Arrow is applied in certain situations. The monitoring window shows certain negative signal values incorrectly. Variation values are overwritten on reloading an open configuration. In animation mode, if "Create/Open Bus configuration" is tried, no message is displayed saying that it is not possible. Errors which occur during the parsing of a bus configuration are not reported to the user. When Replace SDF File is used, the bus configuration corresponding to the new SDF file is not loaded. Renaming a monitor node does not lead to its monitor window being renamed. In certain scenarios, closing one of the two identically named monitoring windows can cause the other one to be disabled. On opening a previously saved bus configuration, which had an active logger, the logger is again shown as active even if the log file associated with that logger is inaccessible. The Network Node Hierarchy view does not show nodes for LIN controllers which only have RX frames. The ECU Enable checkbox is missing on some TX layouts. The Bus Navigator is unable to open a previously saved bus configuration file if the configuration contains a LIN controller without any frames under it. e. Data Capture ControlDesk freezes if the hard disk gets full during data streaming. The host service name gets the suffix ":2" and the experiment displays warnings if the SDF file has been moved to another folder. Captured data cannot be saved, converted or replayed if the user has read-only rights to any of the CLSID Registry keys. Capture files for multiprocessor systems are indexed incorrectly if the start index is greater than 999. It is not possible to start animation when the MicroAutoBox is switched off, although "Continue animation if MicroAutoBox gets disconnected" is selected on the Animation property page of the General Properties dialog. The deletion, export and import of capture variables may take a lot of time. f. Automation cdautomationlib.VariableBrowser.Replace() returns FALSE even if the SDF file has been successfully replaced. cdautomationlib.PlatformManager.Load() returns TRUE even when the board is locked. g. TRC Parser The number of semantic errors in the .err file is limited to 20. Stack overflow may occur during the parsing of very complex TRC files. The TRC parser crashes if a TRC file contains unnamed groups. TRC files containing vectors and matrices are now parsed faster. h. Text Editor Dragging an item from the Reference Data Manager and dropping it into a text document that was opened with the ControlDesk Text Editor, results in incomplete variable paths. i. General Memory leaks on reloading a TRC file which has read-write connections to instruments. Full Screen mode does not work on the secondary monitor. IDF files bigger than 3GB cannot be converted. Experiment toolbar buttons are missing (only if ControlDesk 3.5p1 installed) 3. Limitations ---------------------------------------------------------------------- No known limitations of this patch. ---------------------------------------------------------------------- End of File