Revision Notes - Bosch Motorsport

WinDarab v7.03.013

20.11.2013

Small performance improvement in graph display (OPL1917)



A small performance improvement was made by changing the style of the cursor cross.

 Note: It wasn’t possible to determine the reason of the reported issue (poor performance concerning the instrument panel) nor to reproduce the issue with the provided data. The only thing we found was a small decrease of the performance, because of the changed cursor style.

COMApi: WinDarab eats uncaught exceptions caused by COMApi clients (OPL1927)

 If a COMApi client (such as a plugin) throws excpetions which aren’t handled by the COMApi client itself, WinDarab eats the exceptions instead of crashing itself and creating a minidump for further analysis.



Note: We aren’t responsible for crashes caused by internal errors of a COMApi client/plugin.


18.11.2013

Windows taskbar in auto-hide mode cannot be activated, if main window is maximized (OPL1303)

 If the windows task bar is in auto hide mode and the WinDarab main window is maximized, it wasn’t possible to reactivate the windows task bar.


08.11.2013

WinDarab tolerates not monotone increasing distance information.



If the distance information is retrieved by channels containing a distance information (e.g. the lap distance channel: “distlap”) but the channel didn’t contain monotone increasing distance information, WinDarab didn’t accept this channel as a distance source, showed a message box and continued to look for some other distance source.



Now WinDarab tolerates not monotone distance information by extrapolating samples, which violate the monotone increasing rule.



Note: The change was required because the datalogger import allows to merge several recorded laps into a single data file. In this situation it’s normal, that a “distlap” channel starts with “0 m” after each lap trigger.



Note: Also the situation of an ECU reset (e.g. ignition off/on) let the “distlap” c

Datalogger import: Including/Excluding multiple entries from import task



If multiple entries are selected on the “current import” tab, the user can include/exclude all selected entries to/from the import task by clicking on the “Get”-Checkbox of an entry (Shift or Ctrl key has be held).

Channels pane: Typing channel names in the search field didn’t work reasonable (OPL1962)

 If the user types a channel name (or parts of it) into the search field, the auto completion didn’t work reasonably, if no channel name matches the text. This resulted in the impossibility to filter the channel list by entering multiple words/parts.

Datalogger import: Ensuring the import window to be visible on startup (OPL1960)



If the datalogger import is started, the main windows appears on its latest position and size. In multi-monitor scenarios (or after reducing the monitor resolution) it may happen, that the window wasn’t visible anymore because the restored position and size is outside of the available screen(s).

Now the datalogger import ensures the visibility of the main window on startup.

WinDarab crashed if a constant math channel was removed and later added again to a measurement window (OPL1955)



A crash was reported concerning the use of constant math channels: o The formula of constant math channel contains a constant number or refers to a comment field value o The math channel is added to a measurement view and removed again o WinDarab crashed, if the math channel is added to measurement view again.

WinDarab show a notification, if a file without valid distance is used and the current x-axis is set to distance (OPL1955)

 If the user opens a file, which doesn’t contain any channel usable as the source of distance information, WinDarab shows a message box if the x-axis of a measurement window is set to distance.

Note: The message box appeared previously only, if a valid distance information was available but actually the vehicle wasn’t moved.

WinDarab might crash, if a message box is shown while opening a file (OPL1955)

 A crash was reported where WinDarab crashed after showing a message box (“invalid dist information”) because the new opened file was automatically closed in the background.



Note: It wasn’t possible to reproduce the error nor to retrieve, who/what closed the file in the background. Nevertheless we added a barrier which denies the closure of a file while its still opened.

ComAPI: Command buttons can be added to the ribbon by ComAPI-Plugins (OPL1938)



The ComApi was improved by a possibility to add/create own command buttons in the ribbon. The

Api is mainly intended to be used by ComAPI-plugins but can also be created by any other ComApi client (e.g. Excel).



For more information see the ComApi documentation and the sample code provided in the Samples folder!



Note: If you use plugins, you should recompile your plugin against the new COMApi definitions!

Changes of WinDarab v7.2

File-Explorer sometimes shows laps mixed up, if reduced view is activated (OPL1965)

 If two overlays with different files are opened and the file explorer is switched into “reduce lap list” mode, the file explorer sometimes mixes the laps of the different files if the cursor is moved forward through the data.

Support of MDF data format (INCA) was improved (OPL1972)



Now, WinDarab supports some more features of MDF files: o Periodic, virtual time channels are supported.

o Big-Endian byte order (Motorola format) is supported.

Licensetool supports the use of Unicode characters in installation path (OPL1971)



The license tool now supports the use of Unicode characters (e.g. japanese symbols) in the installation path.

WinDarab crashed, because of accessing channel data behind the last sample (OPL1970)



A crash was observed where WinDarab crashed because of accessing channel data behind the last sample. The possibility is confirmed and fixed.

WinDarab crashed while loading a desktop (OPL1968/1969)



A crash was observed where WinDarab crashed while loading a desktop file. The issue seems to occur only, if there is another problem prior when loading the outing report configuration part.


30.09.2013

Datalogger-Import: Bit channel values were set to zero (OPL1954/1951)



The imported set the values of bit channels to zero, if the data mask to extract the value from a data byte was 0x01. Bit channels with other masks (e.g. 0x40) weren’t affected by this bug.

Datalogger-Import: All laps were marked as Out/In-Laps (OPL1951)



If recorded data is imported and each lap is written to a separate WinDarab file, the

DataLogger-Import marked all laps as Out/In-Laps.



Now only laps with counters lap=1 and fragment=1 are marked as Out-Laps.

 If a file is created for each lap no lap is marked as an “In-Lap”.

Note: If a group of single laps is opened in WinDarab, WinDarab will mark In-Lap implicitly, if the following lap is an Out-Lap!



If multiple laps are merged into a file, laps before an Out-Lap are marked as an In-Lap and the last lap is also marked as an Out-Lap.

Note: The latter assumes, that a whole outing is imported!


24.09.2013

Histogram: The results of a second overlay weren’t calculated sometimes (internal tests)



If a histogram is configured to evaluate two overlays, the results of the second overlay weren’t calculated sometimes. The issue was observed, if the evaluated range is changed by o Moving/Dragging the cursor in the graph window.

Note: The histogram worked, if the cursor is moved by a single click! o Scrolling in the graph window using the scroll bars o Scrolling the visible range through the outing bar.

Graph window settings dialog: Crash, if “Remove all traces” is clicked (internal tests)



If all traces are removed using the button in the settings dialog of a graph window, WinDarab crashed if a channel is assigned to a y-axis.

FFT window: Serveral issues fixed (internal tests)

 If a suspended FFT calculation task is canceled some internal events weren’t unregistered and caused a crash afterwards (e.g. the FFT window is on an inactive sheet and the overlay is removed in the file explorer)

 The “show all results” setting didn’t work. No results were shown.

 The performance of the bar control was very poor, if a lot of FFT results are shown (e.g. if “show all results” is enabled)

WinDarab crashed after deleting a math function (OPL1949)



The crash occurred in the following situation: o A math function references other math functions. o The corresponding math channel is/was used somewhere (e.g. shown in a graph window) o The math function is deleted. o One of the referenced math function is deleted/changed afterwards.

Channels pane: Issues with the channels property area (OPL1655)



WinDarab crashed if WinDarab was closed with a selected channel in the channels pane.



WinDarab crashed, if a group is selected in the hierarchy view of the channels pane.



The channels property area is updated now while searching for a channel in the text field.



A wrong block number was used to determine a channels frequency.



The property area was optically improved by using a header for the area showing the channels type and name.

Analysis windows: Some context menus couldn’t be shown



In some analysis windows the context menu wasn’t shown after a right click on the appreciate area

(e.g. axis settings context menu in the x-y-plot)


13.09.2013

FFT: The selection of a channel doesn’t work sometime (OPL1947)



If a channel is selected in the FFT setup, the selected channel was discarded.

Channels pane: An area was added, where some channel info is shown (OPL1655)



In the channels pane a info view was added, where WinDarab shows some information about the currently selected/focused channel.



If RaceCon provides information about the sampling settings a channel was record with, these settings will be shown.



Note: The sampling rate of a channel is also shown in the channel context info in the graph window.

Math formulas: IIR Filters improved



WinDarab is now capable to calculate IIR filters with individual settings.



Note: If a IIR filter is added using the UI, a fixed set of filter order and filter frequencies are offered.

Nevertheless you can change them later.



Supported filter types: o Lowpass o Highpass o Bandpass o Stopband



Supported filter methods o Bessel o Butterworth o Chebyshev-I o Chebyshev-II o Elliptic



IMPORTANT NOTE:

The “.Net Framework 4 Client profile” has to be installed. If the Frmnework isn’t installed the math functions cannot be used (an error is shown asking to install the framework)

DataLoggerImport: The importer couldn’t connect to the Datalogger after the connection was interrupted (OPL1946)

 If an active connection to the data logger was interrupted, the logger didn’t allow a reconnect until the data logger was reset. Now the importer tries to reconnect if the data logger reports an extended.



Note: A firmware update is also required to solve the issue.

DataLoggerImport: File template variables for fastest lap added



If the destination file contains multiple laps, the variables [fastouting], [fastlap] and [fastlaptime] can be used in the filename template to insert information of the fastest lap within the file.



Note: If a file is created for each fragment, the variables return the lap information of the fragment but only the time length of the fragment (not of the whole lap).


10.09.2013

WinDarab crashed sometimes, if the laptrigger were generated using the laptriggers manager

(OPL1945)



If lap trigger were generated using the lap trigger manager and the user entered an math expression and/or a filter function as the data source, WinDarab may crash afterwards.

WinDarab crashed if a diff overlay is removed/changed (OPL1937)



If the overlay used to calculate differences is changed/removed while WinDarab calculated the

signal in the background a crash can occur, because the main thr ead didn’t wait for the background task to stop.

WinDarab crashed after a diff overlay is removed (OPL1932)



WinDarab sometimes crashes after the overlay is removed, which was used for calculating difference channels.

In another step WinDarab may ask the user to select another reference file for differences from a list containing all opened files – and not only files assigned to an overlay. If the user selected a not assigned file WinDarab crashes sometime afterwards.

WinDarab crashes, if a channel setting is changed and the channel is viewed as a diff channel

(OPL1919)



WinDarab crashes, if a channel setting is changed and the channel is shown in a graph window as a difference channel.



Note: This issue/bug is responsible for various crashes in OPL1920,1922,1925,1933,1937.

Workdesk isn’t loaded at startup (OPL1916)

 A user reported that WinDarab doesn’t load the previous desktop on startup. For further investigation WinDarab writes log entries to the log file to examine the desktop loading decisions on startup.


15.08.2013

WinDarab v7 password protection handling (OPL1914)

 The “Save as” dialog used to save WinDarab files was changed.



If no password (or an empty password) is set in the current file the option “Set password” is shows.

If the source file is password protected, the option “Change password” is shown.

 As long as the “Set password” or “Change password” options isn’t selected, WinDarab will apply the file protection mechanism/settings of the source to the destination file.

 If a user activated the “Set password” option and the source file has no password yet, a hint is shown, that the file cannot be opened by WinDarab v6 anymore.



The password batch dialog (Main menu / Tools) supports the removal of a password protection to return the file format back to WinDarab v6.

Note: Removing the password will reactivate the project protection of the ECU. There is no way to create a unprotected WinDarab v6 compatible file !

If WinDarab is closed, the data logger import is also closed (OPL1913)



If the data logger import was started by WinDarab, it will also be shut down if WinDarb is closed.

Deadlock while closing WinDarab (OPL1907)



If a background task to create the trace of a channel in the graph view is scheduled but not running and WinDarab is closed, it could happen that the background task and the main thread of WinDarab run into a dead lock.

Laps can be omitted from the determination of the fastest lap (OPL1647)



Laps can be omitted from the determination of the fastest lap. The option can be found in the context menu shown in the file explorer, if the user right clicks onto a lap or in the lap trigger manager dialog.

Note: Only the fastest lap can be excluded from the fastest lap determination.

 The lap trigger manager dialog was only available in the “Start” ribbon category, if a graph view is selected. Now the lap trigger manager is available on the “Start” ribbon category for all views.


WinDarab crashed because of an invalid racetrack control (OPL1903)



An issue was observed where a racetrack control got invalid after opening a large number of files.

Actually the cause seemed to be a lack of memory causing the racetrack control not to initialize correctly.

Lookup-Table: Values are reduced to 6 significant digits, if the editor is opened (OPL1902)



If a lookup table is opened in the WinDarab lookup table dialog, the values in the lookup table were reduced to six significant digits. This was a problem since some customers generate the lookup table with external tools and using a higher precision.



Important: If the editor is opened, WinDarab shows the numbers with the configured decimals. As long as a cell is not entered/edited, values with more used decimals are still preserved. Only values touched by entering the cell will be reduced to the configured number of decimals.

 Note: As long as the editor wasn’t used and the lookup table saved, WinDarab worked with the values written by the external tool.

COMApi : Comment field changes weren’t saved

 Any changes of comment fields weren’t saved to the file.



The methods to Add/Remove comment fields (DataFileProperties) were added/implemented.

COMApi: Some channel properties returned incorrect information

 As long as a channel isn’t in use (whether by WinDarab nor a DataAccessor) some properties of a channel object returned incorrect values.

Affected properties were: TimeLine, TimeBegin and TimeEnd.



Note: Accessing these properties move the channel shortly into memory to provide correct values.

Nevertheless this is a more or less expensive operation and you should store the results instead of accessing them multiple times. The most expensive operation occurs, if the channel is a math channel using a periodically timeline for its calculation.

WDServer/Telemetry:



Starting with WDServer v2.02.010 the WDServer supports optionally the use of unicast transmission of online data to connected clients. A minor change was necessary in WinDarab to allow multiple instances of WinDarab running on a single computer while being connected to

WDServers.



Note: Prior versions of WinDarab work with WDServer v2.02.010 as long as only a single WinDarab instance is launched.



Note: These changes are only for the case, WDServer is using unicast packets. We still recommend the use of broadcast packets which is still the default mode for WDServer.


25.07.2013

Detection of disconnected networks may cause stack overflows (OPL1893)



If several network connections aren’t available over a longer period, WinDarab crashes because of a stack overflow.

“Channel Info” didn’t update immediately, if tag cursor is set/removed (OPL1894)

 If the tag cursor is set or removed, the channel info window didn’t update immediately until the user moved the cursor in the graph window.


Test: WinDarab crashed, if a channel attached to a y-axis is removed using the settings dialog



If the settings dialog of a graph window is used to remove a channel from the graph window,

WinDarab crashed, if the channel was also attached to a y-axis.

Test: Modifying exceptions in the unit conversion settings didn’t work, if an overlay is unused



If the user tried to modify exception rules in the unit conversion settings and at the same time an

overlay isn’t used (no file attached), the channels drop down list contained “not existing” channels of the unused overlay instead of the valid channels of the assigned overlay.

This may be a problem, because “not existing” channels doesn’t have a unit and therefore the exceptions page doesn’t work correctly, because the correct unit is required.

Now, “not existing” channels don’t overwrite valid channels of valid overlays.


13.07.2013

WinDarab supports automatic reopening of data files after being disconnected from the network

(OPL1859/1860)



If the user disconnected itself from the network for some time without exiting WinDarab, WinDarab could crash because all opened files on the network got invalid during the disconnected period. In some cases trying to continue to work caused a crash.

 Now WinDarab doesn’t crash anymore, if files are not available througt the network and the user causes operations on the file. After the network is reconnected, WinDarab reopens the files and also reads data requested during the disconnected period.



Note: After attaching the computer to the network, it may take some time (up to 1 minute) until the operating system allows these files to be reopened. This depends on which connection was interrupted: If the network card of the computer was disconnected, the computer will reconnect within seconds. If the server was disconnected, it takes much longer, because the operating system check the connectivity in longer periods.

Graph window: The visible range moved, if an overlay is shifted (OPL1858)



If an overlay is shift sometimes the visible range in the graph windows moved too. Because of this the current cursor position changed and the current channel values (the user may look at) also changed.

The behavior was fixed.

Math functions / Conditions



The update mechanism of math function and conditions was reimplemented.



The update mechanism works more efficient. E.g. if using complex math function, the old algorithm caused many redundant updates.



All views get notified, if a math function or condition changes.



Conditions can be defined in place: Simply enter your condition in the textbox of the drop-down field.

Nevertheless you can still use globally predefined conditions, which are recommended, if your conditions are complex.

FFT: New implementation of the FFT view





The FFT view was reimplemented.

Multiple FFT and 3D view was removed



Multiple files and/or channels can be evaluated



FFT analysis can be used for larger periods (e.g. lap, outing, file).



FFT supports the use of conditions

Data Logger Import: New implementation of the Data Logger Import



The data logger import was completely reimplemented.



Import now supports the use of all available CPUs.



Data conversion is running parallel/asynchronously to importing the data from media. If the computer and hard disks are fast enough (or organized efficiently) the converted data is available much earlier/faster as before.



The data logger import runs as a separate stand-alone process.


Lookup table: The Lookup function was very sensitive when getting the lookup table name (OPL

1879/1880)



The lookup function was very sensitive, if whitespaces appeared in the first argument containing the lookup table name. E.g. a space between the lookup table name and the semicolon was expected to be part of the name.



Now the lookup table name is expected to be a single word. Leading or trailing white spaces will be ignored.

If your lookup table name contains spaces, you can write the name within curly braces. The name within the curly braces is taken as is and can contain any whitespaces.



An example was added to the online help/manual showing the use of lookup tables.

File extract: The error reason is logged, if creating the destination file failed (OPL 1878)



If the destination file cannot be created if extracting a file, the error message show a brief error.

Datails can be found in the WinDarab log files.

Graph window: The order of channels wasn’t preserved (OPL 1872)



If the user arranged the channels using Drag & Drop, the order wasn’t saved/restored safely in the configuration file nor the desktop file.

COMApi improvements (OPL 1869,1871)



Several changes were made to the COM-Api.

Note: Some changes require minor changes in the source of your application!

For further information see the COMApi-Documentation or the language specific COM-Api samples.

Here’s a list of the major changes:

1. External applications using the COM-Api have the ability to choose whether they want to connect to a running instance of WinDarab or to open an own instance of WinDarab.

2 If WinDarab is launched by an external application, WinDarab won’t load the latest desktop nor opens any recently opened files. The same is true for the auto saving of the current desktop – as long as the MainWindow of WinDarab isn’t shown by the external application.

Note: If an application launches WinDarab it’s strongly recommended to quit WinDarab (or make WinDarab visible) if the external application ends with using WinDarab.

3 The tag cursor is accessible through the DataDomain class and Overlay class.

4 Creating new instances of WinDarab classed (VirtualChannel or DataAccessorConfig) cannot be created by “new” commands but through methods NewVirtualChannel and

NewDataAccessorConfig of the DataFile class.

Note: This change was necessary because if an application is connected to two instances of

WinDarab the “new” command doesn’t know within which WinDarab-Instance the object has to be created!

5 The WinDarab.Application class is set as the global application object. If creating applications in

VBA WinDarab can be easily accessed without creating an explicit instance of

WinDarab.Application.

Note: If WinDarab is already running, VBA will connect to this instance of WinDarab. If no

WinDarab is running, VBA will launch WinDarab automatically.

6 If a plugin was deactivated because of a loading error on startup, WinDarab won’t load it any more until the lock is removed. Instead of editing the settings.ini file, deactivated plugins can be activated in the “plugin” dialog (accessible through the ribbon “main category” / “Tools” /

“Plugins”).

File Open: During opening files some information is logged (OPL1866)



If a file is opened, WinDarab logs information about the used strategy to retrieve distance information for the file.



If incompatibilities are detected while opening a file group the reason of the incompatibility is logged.

Lap Analysis: Difference calculcation between two overlays changed (OPL1866)



If the difference of values of two overlays are displayed in the lap analysis, the calculation was implemented inversely as in the graph window.

Now both views calculate the difference value as <value overlay> - <value reference overlay>



If the lap analysis window is configured to show the results of two overlays and one is also used as the reference overlay, the lap analysis shows the absolute values of the reference overlay (the difference values would all be zero).

Crash while loading a desktop (OPL1864)



In the observed issue the cause was a failure while creating a view window during loading a desktop. The crash was fixed, but the desktop still won’t load correctly. For further investigation some log output was added containing the Windows error code.

 If a crash occurs during loading the startup desktop, we didn’t get the desktop which caused the crash. Now the desktop file is first copied to the Auto-Save location and afterwards the desktop is loaded.

Telemetry: Channel settings not restored, if a telemetry stream is opened (OPL1864)

 If a telemetry stream is opened, WinDarab didn’t apply the channel settings (like signal shape, number format, …)

Graph window: Changing the active overlay may fail, if a tag cursor is set (Test)



If a tag cursor is set in the graph window changing the active file may fail, if the tag cursor would get outside of the active file range.



Now switching the active file works, but a message is displayed if the cursor tag cursor goes outside the range of the new active overlay.



Note: Because the current tag position is internally saved as a time stamp, the tag cursor cannot be placed outside of the active file range, if the x-axis is in distance mode.

Outing report: After a double click into the cell the cursor i n the graph window wasn’t set as expected (Test)



If the user double clicks a result cell in the outing report, the cursor in graph window is set to the corresponding position. In the case that a data file is assign to two overlays, the outing report always choose the first overlay of the data file instead of the overlays the outing report is configured for.

Distribution: After switching from 2D to 3D view, the 3D graph wasn’t drawn immediately (Test)



The 3D graph was drawn after the user clicked into the window to turn/move the 3D graph.


29.05.2013

Telemetry: Networks adapters can be disabled for telemetry in program settings/telemetry



In the recent customers got problems using the telemetry because of several issues. Most of them were caused by firewall configuration or incompatibilities between WinDarab/WDServer and the computers network configuration.



Instead of letting WinDarab to guess, which network adapter should be used for telemetry communication, the user has the ability to select/disabled the network adapters and their network subnets to be used for telemetry.



On computers running WDServer or WinDarab which are also connected to the CAR LAN, we strongly recommend to disable the CAR LAN network adapter to be used for telemetry communication between WinDarab and WDServer.

 On client computers running WinDarab, we recommend to disable network adapters, which won’t

be used for telemetry communication at all (e.g. VPN adapters). Nevertheless, leaving the network adapters enabled doesn ’t matter, but, if necessary, WinDarab will send broadcast packets to search

WDServers.



WinDarab broadcasts discovery packets only on enabled network adapters and only for the subnets, the adapters are configured for. Multi-homed network adapters (having two IPs) are supported.

WinDarab enforces the use of v7 file extensions (OPL1852)



If the user saves a configuration which has originally a v6 file extension, WinDarab changes the extension to v7 prior to showing the “File save” dialog.



Note: If a file is s aved with the v7 extension, WinDarab doesn’t delete the existing file using the v6 extension.

Changes of WinDarab v6

WinDarab crashed on exit (OPL1847)



If WinDarab is closed a crash could occur, because of a file group was closed yet.

WinDarab crashes, if trying to open a file group twice (OPL1838)



Windarab crashes, if a file group is opened and following conditions are true: o The file group contains an invalid/corrupt file. o The header and status data of the corrupt file is correct – e.g. only the channels data is corrupt. o The corrupt file is the last selected file (the inform preview shows its content) o On first attempt to open the file, WinDarab doesn’t show the corrupt file in the member file list for the file group. o The user cancels the dialog and tries to open the file group again – without changing the file selection of the file open dialog. o WinDarab crashes



The crash was fixed.



A message box is shown, if the user tries to opens a corrupt (member) file.


14.05.2013

Linked files: “Permanent Zero Offset” not applied on open (OPL1835)



If files are opened as a linked files file, the permanent zero offsets of the files were not applied as expected whereby changing the zero offset (even a permanent one) was working.



Note: The zero offset of the first member file will be applied to all member files.



Note: If the files contain different zero offsets a notification message will be shown.

Min-Max-Table may show invalid/wrong results (OPL1834)



If a measurement file is opened and the current worksheet contains a Min-Max-Table, the

Min-Max-Table may show wrong results for a single lap.



The issue is caused by an interruption (a sequence of canceling and restarting) of the calculation of the Min-Max-Table. In case of a cancellation the Min-MaxTable still sets the “Results Valid Flag” and didn’t recalculate the lap results after the calculation is continued.

File Explorer Pane: New files may be listed twice in the “New Files” pane (OPL1833)



The issue occurred, if a file is opened from a parent folder and a second file from a sub folder. If new files arrive in the subfolder they were listed twice, because WinDarab observes both folders (and their subfolders hierarchy) and therefore received two notifications about the new file.

Now WinDarab checks, if a file is already listed in the “New files” pane before adding it.

Outing bar: Sometimes the selection of a lap wasn’t possible (OPL1827)



If the visible range is scrolled outside (to the left) of the visible part in the outing bar, it wasn’t possible to select a lap through the outing bar.

Several issues fixed (OPL1824)



WinDarab crashed, if the user enabled (disabled) the difference option of a channel in the measurement view.



WinDarab crashed, if the zero line is enabled/disabled in the ribbon bar but no channel is currently selected. Now the option is disabled, if no channel is selected.



WinDarab could crash, if a lookup table is deleted.



WinDarab could crash, if the math explorer pane is opened but the selected channel is invalid.



WinDarab could crash, if a lap trigger is added/deleted because some windows handled the events without checking, if the lap triggers belong to the file(s) shown in the window.


18.04.2013

The main window of WinDarab support the use of multiple tab groups (OPL1818)



By default the Microsoft library supports the creation of multiple tab groups in the main window.

Note: Only vertical or horizontal tab groups are supported. Thus with the creating of the second tab group, the orientation of the tab groups is fixed.



While creating a tab group was possible in WinDarab previously, i t wasn’t possible to delete a tab group anymore: Because after closing the last worksheet of a tab group WinDarab immediately created a new empty worksheet - preventing the tab group to be closed.



Now a tab group is closed after the last worksheet is closed. Only if all worksheets are closed,

WinDarab creates a new empty worksheet automatically.



The way how worksheet are moved between tab groups was changed, because the default implementation of the MFC library didn’t work if a tab group shows its tabs at the bottom.

WinDarab allowed opening incompatible data files as a file group (OPL1813)



If the user opens multiple files as a file group, WinDarab checks the compatibility between files. An issue was observed, where WinDarab allowed the user to open two files even they weren’t fully compatible: o Two of more files are opened.

o The files #2 .. #n contain the same channels as the first file (but may contain additional files) o The recording block structure of all files is the same.



Note: This kind of file compatibility can be reproduced, if channels are removed from the recoding setup without adding other channels.



Now the compatibility check is stricter and al so checks, that the first file doesn’t contain less channels as the other files.

Graph windows not updated after the active worksheet is changed (OPL1807)

 If the active worksheet is changed, the graph windows weren’t updated until the user did some change and caused a redraw of the window.

The issue occurred on Windows XP and Windows 7 (with Aero disabled). The issue didn’t occur using Windows 7 with Aero or Windows 8.



Now all views of a worksheet are redrawn, if a worksheet becomes active.

WinDarab crashed in the math function dialog (OPL1805)



From time to time crashes were observed in the math functions dialog because of a pointer to an invalid tree entry. Now the referencing is done via an entry index instead of entry pointer.

WinDarab crashed, if the telemetry configuration is changed while a channel signal is updated in the graph window (OPL1805)



WinDarab could crash, if the channel signal in a graph window is computed in the background and the telemetry configuration is changed in the meantime.

Now WinDarab stops the background tasks to calculate channel signals, if a the upcoming change

of the telemetry configuration is announced and restarts the tasks, if the new telemetry configuration is applied.

WinDarab crashed while retrieving telemetry data from WDServer (OPL1805)



An issue was observed, where WinDarab retrieves telemetry data from WDServer and in the meantime the allocated buffer was freed by the memory manager, because the aging counter for the data page exceeded its threshold.

WinDarab crashed while loading an instrument panel configuration (OPL1805)



WinDarab crashed while loading an instrument panel configuration, if the previously assigned overlay is not accessible/used anymore.

WinDarab crashed while calculating a math function (OPL1805)



WinDarab could crash because of a running condition between two threads accessing the same math function.

New files weren’t announced any more after the computer was disconnected from the network

(OPL1805)



If WinDarab observes network folder for new measurement files the observation was broken, if the network connection is interrupted/disconnected, and not reestablished after the file server is reachable again. Now WinDarab detects the reconnect as soon as the user accesses the network resources.



Note: The user has to access the network resource actively – WinDarab doesn’t try to reconnect itself, because this would block WinDarab for a couple of seconds!

Copy to clipboard uses decimal comma as defined in program settings (OPL1803)



If data is copies to the clipboard, WinDarab uses the same decimal comma character as defined for the ASCII export in the program settings.

Incorrect breakpoint values, if a distribution table is copied into to the clipboard (OPL1802)



The breakpoint values of a distribution table copies to the clipboard were wrong, if the x-/y-axis didn’t start at zero (Min-value of range <> 0).



Note: WinDarab shows the breakpoint values at the border of the value cells. Because such a table layout cannot be copied into the clipb oard (and used e.g. by Microsoft Excel®), WinDarab copies the median value of the cell borders to the clipboard.

Memory leak fixed in the background calculation of channel signals



If the background calculation of channel signals is interrupted/canceled, sometimes a small piece of memory got lost.

Results of math function “lapsigma” not correct / Crash



Because of the parallel background computing of the channel signals in the graph window the lapsigma function reset to 0 in the middle of a lap.



While fixing the calculation a deadlock was observed and fixed because of infinite loop while calculating the “lapsigma” results.

During startup WinDarab repeatedly asked for file password



During startup (or loading a work desk), WinDarab repeatedly asked for passwords under following conditions: o WinDarab is opened o The last work desk contains a password protected file o The password isn’t stored in the password safe


22.03.2013

WinDarab crashed, if a file is open with a (quick) double click (OPL1796)

 WinDarab crashed, if a measurement file is opened in the “File open” dialog by a double click.

The crash only occurs, if … o No file is/was selected since the dialog was opened o The inform preview windows is empty o The user selects/opens a file by a double click.



The issue is caused, because the inform window loads its configuration with a small delay after the user selected a file. If the file is opened before the inform window has actually loaded its configuration some messages were send to the inform window causing the crash, because the inform window didn’t expect messages at this time.

C40/CardMemory import: Cardinfo was retrieved correctly



If data is imported / opened from a CardMemory/C40 device and the CardInfo is retrieved (e.g. to be used in the file name template during importing from flashcard) the text was incorrect.

The issue was caused because WinDarab retrieved the text as UNICODE from the file, but it should be interpreted as ASCII.

WinDarab leaves disabled after importing data from flash (CardMemory/Data Logger) (OPL1792)



Multiple clients reported an issue that WinDarab hangs after importing data from CardMemory /

Data Logger. Currently it seems to be caused because the main window isn’t enabled completely after the import dialog closed.



Nevertheless the issue cannot be reproduced in any way. For further investigation additional logging was added to get a better sight on the issue.


Burst: WinDarab crash while transmitting data



WinDarab crashed at the beginning of a data transmission because the Request/Acknownledge packets become out of order.

The issue may be caused by delayed responses, which came in while the caller already canceled the request. Starting with this, the packets got out of order any may cause a crash.

WinDarab hung sometimes after pinging the ECU/data logger failed



After a ping to the ECU/data logger failed, WinDarab removed optionally the destination IP from the

ARP cache. Some internal tests showed a problem causing WinDarab to hang, if WinDarab tries to send the “Delete ARP entry” command to the FlashApiService. Sometimes writing to the pipe didn’t succeed and WinDarab was waiting an infinite time.

A timeout of 2 seconds was introduced to all “Write command to FlashApiService” actions.

WinDarab crash in Histogram (OPL1795)

 WinDarab crashes in the histogram because of an invalid file structure. It wasn’t possible to reproduce the issue, but we found a possibility where the affected memory may become inconsistent and fixed it.


15.03.2013

Settings dialog of the graph display shows configuration of another graph display (OPL1783)



If the user switches between different worksheets containing graph displays and calls immediately the “Settings / Edit” dialog (-> F5), the settings dialog showed the configuration of the graph display on the previous worksheet.

After the user clicks once into the graph display window, the settings dialog will show the correct configuration.

The issue was fixed.

WinDarab crashed sometimes, if new files are detected by the file system watcher (OPL1780)



If new files are detected by the file system watcher (e.g. after a flash card was imported), WinDarab sometimes crashed while updating the “new files” pane of the File Explorer dock window.



Actually the changes are some kind of workaround, because the crash occurred somewhere within the Microsoft MFC libraries. Also the crash was observed multiple times but it wasn’t possible to reproduce it yet.

If a CardMemory flashcard is initiali zed using the “Tools / Flashcard / Initialize” WinDarab asks for the DCP file to be used

 If a flashcard is initialized using “Tools / Flashcard / Initialize” WinDarab now asks for the DCP file in the same way as the Import dialog does: o The first initialization of a flash card after launching WinDarab, the DCP file has to be confirmed by the user. o If the flag “Ask for DCP file for each initialization” is set in the program settings, the DCP file has to be confirmed every time a flash card is initialized. o If the previously used DCP file isn’t available any more, another DCP file has to be selected by the user.

WinDarab uses WinAPI GetLocalTime instead of the standard ANSI-C routines



A strange behavior of WinDarab was reported, where WinDarab replaced the time variables in the filename template for imported files with a wrong time – depending if the user has admin rights or not. At the same time the log file entries reported the correct time …



Because the different routines used different ways to retrieve the system time, WinDarab was change to use only the WinAPI routines instead of the ANSI-C routines.

 Note: The problem occurred on a single system and wasn’t reproducible on any other Windows computer and independent from the kind of user account.

Test: A memory leak in the drawing routines of the graph display was fixed



If the background worker of the graph window is interrupted/canceled because the display range changes in the meanwhile, WinDarab lost some memory because releasing was skipped by the cancelation handler.


Sometimes the segment colors cannot be set in the racetrack segmentation dialog (OPL1782)



Because of an uninitialized flag (-> randomly set/unset) WinDarab sometimes disabled the segment color feature in the racetrack segmentation dialog. The flag is now properly initialized.

Commentfields: Loading/Saving comment field improved (OPL1779)



Loading / Saving a large number of comment fields was improved.


06.03.2013

Error message appears, if customer specific inform file “inform.dat” isn’t available 

 If the customer specific inform file “inform.dat” cannot be found in the “Config” folder, WinDarab displays a message box.

 By default, WinDarab uses the generic inform file “default.dat”, if no other inform file can be found.

But there was a lack in the inform file cache (introduced with v7.2) which isn’t using the fall back and still caused the display of the error message.

File explorer shows manually added laps at the end of the lap list (OPL1776)





If the user splits a lap into two or more parts, the File Explorer adds the new lap entries at the end of the lap list. After closing/opening the file, the laps appear in the correct order.



Note: The issue only occurred, if the file doesn’t have outing numbers (e.g. there is no outing number channel as specified in the program settings / special channels nor the file isn’t a single

datalogger file or a linked file of single datalogger files)


28.02.2013

Some minor text errors fixed in COM Api reference manual (OPL1761)





Some text error were fixed in the COM Api reference manual.


WinDarab displays notification message, if the current x-axis overlay is <unsed>





If the current x-axis overlay gets “unused”, e.g. because the user detaches the file from the overlay,

WinDarab shows a message box and ask the user, if he wants to switch the x-axis to an used overlay.



Note: The message box comes also in other situation (e.g. if the user assigns a file to an overlay while the current x-axis overlay is still unused).

Laptrigger Manager doesn’t show lap entries under Windows XP (OPL1772) 

 If the user opened the “Laptrigger Manager” Dialog, the list containing the lap entries didn’t show any information, but the entries exists and all function are available.

The issue only occurred on Windows XP computers because of a bug in the common controls DLL of Windows XP.

The inform preview of the Open File Dialog didn’t show the currently selected file (OPL1768) 

 If multiple measurement files are selected in the “Open File” dialog, the inform preview window always showed the content of the first selected file and not of the latest selected file.

Now the preview window shows the content of the latest selected file.

Changes in the “Channels” category weren’t applied to the selected channel (OPL1762)



It could occur, that changes in an ribbon edit control were applied to the wrong channel. The issue occurred, if the user did following steps: o The user clicks into an edit control in the ribbon bar (e.g. Channels / Signal Line Width or

Min/Max value) o The value is changed using the keyboard (without pressing enter) o The user clicks into the measurement window to select another channel o The changed value isn’t applied to the previously selected channel but to the new selected channel

The behavior is fixed.

Zooming into data by double clicking didn’t work while online data is playing (OPL1760)



If the user double clicks into playing online data, WinDarab zooms into the data and then resets the zoom immediately. This behavior is fixed and zooming in/out of the data while playing data is possible.

BurstTransmission: Burst didn’t work on Windows 7/8, if UAC is enabled (OPL1759)

 Burst also works, if user doesn’t have elevated administrator rights and/or UAC (User Access

Control) is enabled.


Burst: Connection establishment improved (OPL1769)



If data is transmitted using burst, searching for the ECU was improved. Instead of first pinging the

ECU, WinDarab immediately sends discovery packets with a period of 50ms. As soon as a discovery packet is answered by the ECU, WinDarab establishes the TCP connection to receive data from the ECU.

Opening measurement files take long time, if a lot of comment fields are defined (OPL1766)



If a lot of comment fields are defined in the program settings (several hundreds) opening a file (even for the preview in Darab Explorer) takes much time.

The issue is caused, because WinDarab read the comment field configuration file once for each file.

Now the settings are loaded once (or after they are changed) and cached as long as WinDarab is running.

Note: Because the comment field configuration file is a INIfile, saving settings on “Comment fields” tab in the program settings still takes some time after they are changed.


08.02.2013


FlashApiService: If accessing a media behind its size, the read command hung some time

(OPL1757)



If an application tries to access a sector behind the actual media size, the read command hung for some time. Now the requested read offset is checked against the media size and the command will fail immediately, if the request is invalid.

WinDarab crashes while opening a linked files file (OPL1740/1751)



Two occurrences of a crash were reported in the past, where WinDarab crashed while opening a linked files file. The MiniDumps showed a strange behavior where files seemed to be removed after the linked files file was opened. This should never happen and any efforts to find how a user can do this failed. Because of this additional logging was added to (hopefully) get more information, if the crash occurs the next time.

Support of USB sticks with a capacity of 2GB and more (OPL1748)



If a USB stick is used to record data, WinDarab wasn’t able to read the USB content correctly, if the recording exceeded the 2GB limit of the stick.

Note: In the past two setups an updated 3th-party DLL was missing. The incorrect DLL caused a file to be converted with some lost data.

Changes of FlashCardTool

The dialog layout was fixed (OPL1756)



The dialog layout of the FlashCardTool was fixed.


01.02.2013


Licence information of used Open Source Components included in program folder



A file containing the license information of all Open Source Components used by WinDarab is stored in the installation folder of WinDarab.


31.01.2013


Graph window: The minimum x-axis range is disabled (OPL1749)

 If a data file contains less data (e.g. 0.01s of data with about 50 samples), it wasn’t possible to zoom

into the data, because there is a minimum limit for the x-axis range (1s).



The minimum x-axis-range was disabled (previously 1s or 1m). If a data file contains less than 1s or

1m of data, the x-axisrange (zoom all) isn’t limited any more to 1s or 1m. So all data can be shown and its possible to zoom into the data.





The maximum zoom depth is still limited to about 20 samples in the visible range (assuming that samples are evenly spread in the whole x-axis-range).


WinDarab crashed because of a race condition at the end of using a math track (OPL1750)



If a math track is used only by a single analysis window and all data of the math channel is evaluated (e.g. Outing Report), WinDarab crashed sometimes because of a race condition between the calculating thread (releasing the channel) and the main thread (which handles an event to release required resources after all math channel data was calculated).



The race condition was fixed.

WinDarab crashed, because an event was posted to a destroyed UI control (OPL1750)



A crash was observed in the formula editor because of an event posted to a UI control after the editor dialog was closed.

The error wasn’t reproducible, but some changes were made to prevent sending of events to controls after they are deleted. Some logging was added to observe the issue closer.


28.01.2013

COMApi: If a client observed a telemetry stream, it didn’t receive change events of the lap list

 If an external client observes the lap list of a file, it didn’t receive any changed events, if the file is a telemetry stream.

WinDarab crashed, if no channel is selected in the graph window (Test/OPL1746)



WinDarab crashed, if no channel is selected in the current graph window and the ribbon category

“Channel” is activate.

WinDarab crashed, if the user enabled x-/y-interpolation for a 1-D-lookup table (OPL1738)



If the user enabled the x-/y-interpolation but the lookup table only contains a single row of data

(single column of data), WinDarab crashed because x-/y-interpolation requires a 2D lookup table.



Now x-/yinterpolation doesn’t have any effect unless the lookup table contains at least two rows/columns.

Instrument panel: The bar gauge display layout was changed (OPL1735)



The upper/lower limit and the recent lap min/max values are displayed left aligned while the min/max value of the bar is display right aligned to the bar.

 The recent lap min/max values are only shown, if the “Replay” mode is enabled and the Replay traversed a lap trigger. Note: The min/max value is calculated from the beginning of the replay – not from the beginning of the lap.


DataLogger: Data import fails on USB-Sticks larger as 2GB (OPL1748)



WinDarab fails while importing data import from USB sticks, if the stick capacity is larger than 2GB.

The failure only occurs, if a file exceeds the border at 2GB and continues at the beginning of the measurement partition (Info: the measurement partition is organized as a ring memory).

 On Windows 8 accessing a USB stick behind 2 GB RAM failed. Actually it doesn’t affect the data import, because the used portion of a USB disk is limited to 2GB. But it did affect the flashcard tool, which can be used to backup USB sticks larger than 2 GB (currently the limit is about 800GB).


Statusblock labels visible in channel list (OPL1743)



By default labels containing status block information (dynamic status block) shouldn’t be shown in the channel list. This wasn’t true, if a channel has a name with more than 21 characters. In this case the extension “\Statusblock” is truncated and WinDarab doesn’t detect the label as a status block label.

For new imported files, the labels are marked as status block labels during the import process. For existing files the detection is extended to all channels beginning matching the pattern “*\S*”.

WinDarab crashed, if WDServer stop/starts data receiption (OPL1741/OPL1728)



Another crash dump of WinDarab prior v6.34.007 was send, showing additional information about the crash which is already addressed by OPL1728. With the new information it was possible to investigate the problem a little more and to make some additional changes.

The failure is caused by a stop/start of WDServer in conjunction with a larger change of the channels configured in the telemetry setup. Nevertheless the reason of the crashes couldn’t be reproduced, because it is some kind of race condition.

Data Logger Import: Possible crash, if data is imported from USB stick (OPL1736)



If data is imported from USB stick, WinDarab could crash at the end of reading data from the USB stick because of a very small race condition between two threads.

It was possible to reproduce the issue technically to implement and test the fix.

ASCII import didn't work correctly, if channels weren't sorted in input file



If the channels in the input files weren't sorted by name, the ASCII-Import of WinDarab didn't assign the imported values to their channels.

ASCII import supports text files with quoted values



The ASCII import imports text files correctly, if the channel values are quoted (e.g. semicolon separated textfiles: "1.2" "100.3" "2302")


20.12.2012

WinDarab hanged up, if the display mode in a graph window is switched

 If an area in a graph window is switched between “Stacked mode” to another mode, WinDarab hanged up.



Several function concerning the yrange/axis were deactivated, because they don’t have any reason for binary channels.

The tag is set/reset for all graph windows (OPL1357)



If the users sets/removed a tag in a graph window, this is done for all graph windows at once.



Note: There is no possibility any more to set individual tags in the graph windows.

Used open source components are listed in the info window (OPL1729)

 

Open source components are listed in the info window.

Distribution: Configuration allows the use of a physical step width instead of a step count

(OPL1724)

 

The user can configure a physical step width instead of a step count.

Histogram: Several improvements implemented (OPL1393)



The maximum value can be included to the value range of the last histogram bar (optional).



The user can configure a physical step width instead of a step count.



The step value can be configured to be the border limit between two neighbor bars or the median value of a bar (-> e.g. useful for gear usage).

WinDarab also searches for plugin-DLLs in the plugin folder and its descendants (OPL1716)



WinDarab also searches for plugin-DLLs in the plugin-folder and its descendants. During loading a plugin, the current folder is set as a search folder so a plugin can load/find the required DLLs.

WinDarab crashed, if a graph window is closed while the channel signal is updated (OPL1716)



If the user closed a graph window while WinDarab is preparing the channel signal in the background, WinDarab could crashed because WinDarab didn’t wait for cancelation of the background process.

Drop down lists didn’t disappear in dialogs, if the user clicks outside of the list (OPL1565)



If a menu drop down list is shows (e.g. the display format in the channel settings dialog) and the user clicks outside of the list, the list left visible until the dialog was closed.

Unit converter: The configuration dialog of the unit converters was redesigned (OPL1565)



The configuration dialog for unit converters was completely redesigned.


FileExplorer pane: Right click in overlay column shows context menu (OPL1748)



If the user right clicks into the overlay column, WinDarab now shows the overlay context menu (as if, the column header is right clicked).

The previous action to detach a file to the overlay was removed and is now accessible through the context menu.

Order of file in file groups not correct (OPL1730)

 If the user opened file groups, it could happen that the files weren’t sorted in order of recording

(Outing, Lap, Fragement order). The issue only occurred, if the lap stack of files from within an outing weren’t compatible (in the reported issue, the last file of the outing didn’t contain a lap stack).



Now using the lap stack to determine the order of recording is skipped, if lap stack incompatible files are detected. Nevertheless WinDarab uses the outing, lap and fragment numbers and, if necessary, the file name to determine the order.



Note: In case the order still isn’t correct the user has the ability to press the Shift-Key while opening a file group. WinDarab will display the “File order” dialog (in WinDarab v6 shown by default) and the user can fix the order on his own.

Text color of 2D distribution table changed (OPL1723)



The text color used in the 2D distribution table was changed. Before the windows used the text color of the selected theme. But because the table always uses the dialog background color, the text color (White) used in the “Black Theme” wasn’t readable.

Datalogger Import: WinDarab lost filename template in long-term test (OPL1722)



During long-term tests of the DataLogger import WinDarab sometimes lost the filename template settings disabling the auto save feature. The UI and MRU-list of the filename template was previously updates with each data import.

Now the UI and MRU-list is only updated if necessary and certain notification messages are disabled which may be the cause of the update failures.

Auto zoom y-range on multiple selection changed (OPL1720)



If multiple channels are selected and the user wants to auto zoom these channels, WinDarab determines the min/max for groups of channels. WinDarab puts channels, in the same group under following conditions: o Channels attached to the same y-axis (channels may have different names) o Channels with the same name within the same area.



Note: If multiple channels are attached to a y-axis, but the user selects one of those channels and auto zooms the y-range, the min/max is only calculated using the single selected channel.

WinDarab Free shows vexing error message for unsupported math function (OPL1719)

 WinDarab Free has a limited support of math functions. Because of this the parser didn’t know about math functions supported by other versions WinDarab, the parser tries to interpret unknown keyword as potential channel names. In consequence the parser finds a syntax error because of a missing operator between unknown function names and the following brackets.

Now the parser detects the all keywords/function names but shows an error message telling the user, that a certain math function is not supported because of license restrictions.

After selecting a new file for an overlay, the overlay color couldn’t be changed (OPL1718)



If a new file is attached to an overlay, the overlay will be shown as selected in FileExplorer.

Nevertheless if the color of the overlay is changed too, sometimes the color was assigned to another overlay, because the code executing the color change has another selected overlay.

Now the overlay selection is announced correctly in WinDarab.

Some files has a very large x-axis time range (OPL1717)



When opening a file, WinDarab sets the min/max of the time axis, if the default min/max settings are very large. The files created by a file extract have min/max settings nearby the limit used when opening the files. Because of a change in OPL1668, the min/max of the file become smaller than the limit and WinDarab uses the min/max of the file without fixing.



Now WinDarab fixes the x-time range to the actual time axis values as soon as there are time stamps available (no time stamps may occur on telemetry data without a current data stream).

WinDarab could hang, if file group was opened



If a file group is opened with files containing GPS channels, WinDarab hangs in an endless loop, if no GPS data was recorded.

Note: Opening the single file didn’t cause any problems.

Test issue: After closing a distribution window while playing telemetry data, WinDarab downtimes crashed



If telemetry data is viewed and the distribution window is closed, WinDarab crashed, if the user right clicks into the empty worksheet area. The bug was fixed.

Test issue: Math inspector crashed, if the inspected file is detached from its overlay



If a math function is inspected using the math inspector and the user detaches the file from its overlay in the FileExplorer pane, the math inspector crashed.

Some files has a very large x-axis time range (OPL1717)



When opening a file, WinDarab sets the min/max of the time axis, if the default min/max settings are very large. The files created by a file extract have min/max settings nearby the limit used when opening the files. Because of a change in OPL1668, the min/max of the file become smaller than the limit and WinDarab uses the min/max of the file without fixing.



Now WinDarab fixes the x-time range to the actual time axis values as soon as there are time stamps available (no time stamps may occur on telemetry data without a current data stream).

WinDarab crashes, if math channel with calculation period <1ms is used (OPL1715)



If the user adds/uses a math channel with a sample period <1ms in an analysis window, WinDarab crashed. The bug is fixed.

 Additionally the formula editor doesn’t allow to save math formulas with a sample period <1ms.

(Re-)Play stops, if user scrolls in data (OPL1714)



If WinDarab is replaying data (e.g. telemetry data) and the user scrolls in the data using the scrollbar, WinDarab stops replaying data.

To continue replaying the user has to enable replaying in the ribbon.



As long as the user clicks into a measurement window, replaying data is interrupted to inspect the data at the mouse location. If the mouse button is released, replaying data continues.

Performance of math function “average” improved (OPL1713)



If the sample span of the average function is very large, the performance of calculating the math function is very poor. In the reported issue reported that WinDarab hangs, but actually WinDarab was calculating a math channel with an average({default};10000).

 The “average” function was implemented new and gives a much better performance (in the observed issue about >100x faster.

Fix/Test: A grid control menu button didn’t disappear, if the cell is left

 The grid control “menu button” didn’t disappear after the cell is left. This issue occurred, if the drop down menu of the menu button is opened and the user directly clicks into another cell. Because the

MFC library eats the window message to close/destroy the menu button, the control stayed visible in the grid control. Because the bug is located in the MFC libraries, a workaround is implemented posing a “dummy” window message which will be ate by the MFC bug.

Folder for incoming new measurement files can be set by user (OPL1712)



By default WinDarab monitors all folders of opened measurement files for incoming/new measurement files.

Now the user can select a user defined folder for monitoring for incoming files on the program settings dialog / miscellaneous tab.



Note: If a user selects a folder to be monitored, the default monitoring of the folders of opened files is disabled.


WinDarab crashed, if WDServer stop/starts data receiption (OPL1728)



Sometimes WinDarab crashes, if a telemetry stream is opened and WDServer stop/starts the data reception at the same time.

Because the crash occurs at a later point of execution, a workaround for the crash was implemented and a little logging was added to improve investigation of the issue in the future.

Fix: AsciiImport sometimes doesn’t succeed/hangs



If an ASCII file is imported using CR instead of LF/CR as line breaks, the data import could hang at some line of the file. The issue didn’t occur generally with this kind of ASCII files, but could be fixed.

Importing Burst data crashed (OPL1628)



An issue was observed where WinDarab crashed while receiving burst data. The crash was caused, because a response packet was received exactly in the moment the corresponding a request timed out. Because of this the reception buffer was discarded exactly at the moment the response was written into the buffer.

The access to the response buffer is now safe for concurrency.


15.11.2012

The visible range of the outing pane wasn’t updated immediately



If the visible range was changed, the outing bar didn’t update itself until the user changed the current cursor position.

COMApi: The installer delivers the API documentation and sample code



With this version of WinDarab v7.2 the installer creates a Samples folder containing code samples for the COMApi.



The API documentation help file can be found in the program folder and a link was added to the help menu item.


WinDarab doesn’t load the last racetrack in an emergency startup (OPL1710)



If WinDarab is launched after a crash and the latest desktop is not loaded, the racetrack won’t be loaded too.



The same is true, if the users pressed the SHIFT key while WinDarab is launched.

ASCII-Import crashed, if no data can be imported (OPL1706)



A client reported an ASCII file, which caused a crashed during the ASCII-Import.



He crashed is caused because no data could be imported from the file because of an unsupported structure (semicolon separated file with values in quotation marks).

 WinDarab won’t crash anymore, if no data can be imported.



The import now also supports semicolon separated file with values in quotation marks.

Notifcation “Car wasn’t moved” appeared for unused overlays (OPL1700)



If an unused overlay is examined by an analysis window (e.g. lap analysis), WinDarab showed a notification message saying that “The car wasn’t moved”. WinDarab won’t display the message (or similar messages) for unused overlays.



Additionally the current car position of unused overlays is not displayed in racetrack windows anymore.

Channel context menu in graph display shows wrong menu items (OPL1699)



If the user changes the selected channel in the graph window using the keyboard and then displays the context menu of the channel, the menu items weren’t updated for the selected channel. The issue was visible only, if the user changed the selection between a math channel to a measurement channel, because a math channel has an additional menu command “Edit formula”, which didn’t appear/disappear if the selection was changed.

Read data from logging device: The menu command is moved (OPL1696)

 The menu command “Read data from logging device” was moved from the submenu “Data

Import/Export” to an own item in the main menu.



The command is now directly accessible through the quick access toolbar (QAT).

Note: After an update users have to modify the QAT on their own.

Math inspector crashed (OPL1695)

 If the math inspector is used to examine a math formula containing the “Lookup” function, the window crashed, if the math formula or the lookup table is modified.

WinDarab crashed, if the settings dialog of a measurement views is opened (OPL1693)



Because of a not reproducible / unknown internal error the creation of the settings dialog failed.

WinDarab shouldn’t crash any more, if the issue occurs again, but still the dialog won’t appear.

WinDarab crashed, if WinDarab is about to close (OPL1692)



The issue is a duplicate of OPL1618 (fixed in v7.01.012).

WinDarab crashed, while editing a lookup table (OPL1691)

 The root cause couldn’t be reproduced/determined, because the crash was only a late consequence of the cause. For further investigations an exception handler was added to the

OpenGL renderer, which hopefully will catch the root cause the next time the error occurs.

Logging of flashcard/USB stick access (OPL1688)



If a data import dialog is opened, the activity of accessing flashcards / USB-Sticks is logged into log files. The files can be found in the “LogFiles” folder of WinDarab.



If customers have problems accessing/reading data from flash cards/USB sticks, we kindly ask for these log files and a brief description with the time of the issue.



A log files will be created for each day. The latest 7 files will be kept beginning with deleting the oldest files.

 The logging can be activated/deactivated in the “program settings” dialog / “Miscellaneous” tab. By default the option is activated.

WinDarab crashed, if a corrupt racetrack file is loaded (OPL1684/85)



If a corrupt racetrack file is selected, WinDarab could crash. Now WinDarab shows a message box to inform the user about the corrupt file, if a user selects one in the “Select racetrack” dialog. If

WinDarab mets a corrupt racetrack file during startup, the default racetrack is loaded instead.

Installer copies license file from existing installation (OPL1683)



If WinDarab is installed as a new/additional instance and the user selects to copy settings from an existing installation, the license file will be copied too.



After installation the user has the opportunity to replace the license file by another.

X-axis range is sometimes to large (OPL1668)



If the File Explorer pane shows two overlays, but only one has a file assigned with less than 60s seconds data, WinDarab configured the overall x-axis-ran ge to 60s. Now WinDarab doesn’t include unused overlays if determining the x-axis-range. This allows the x-axis-range to become as small as necessary.

Lap normalization can be influenced by program settings (OPL1649)



New options were added to the program settings / Miscellaneous tab to influence the lap normalization in WinDarab. The user has the options to o Set the max. drift of a measured lap to the racetrack length. If the drift is below the set value, the lap will be normalized to the racetrack o Disable lap normalization. o Normalize all laps – not regarding the drift between the measured lap and the racetrack length.

If selecting/changing the lap, the laptriggers of all overlays is synchonized (OPL1528)



If the user selects a lap in the File Explorer, WinDarab always aligns the overlays at their lap triggers. A single click will keep the current zoom depth, while a double click zooms the clicked lap.

 If the user changes the selected lap by pressing the keys for “previous”, “next” or “fatest lap” the lap trigger will be synchronized too.



If the user clicks into the outing pane the lap triggers of all overlays at this position are synchronized and the view scrolls to the same lap position as before. Additionally a double click will zoom the clicked lap.


26.10.2012

The file open dialog didn’t show WDServer streams, if a certain file type is selected (OPL1484)

 If the user selected a file type filter in the “Open file” dialog, WinDarab didn’t show the WDServer streams, if the user selects the “WDServer” location.

Actually the behavior is correct, some users were confused because they didn’t check the file type filter. Now the WDServer streams are always shown.

Unsupported file types removed from WinDarab Free (OPL1484)



WinDa rab free doesn’t show file types, which are not supported by WinDarab v7 Free.

Caption bar of a Min/Max-Window shows the loaded configuration file (OPL1666)



The name of the configuration file is shown in the caption bar of a Min/Max-window.

Flow Chart: The first row in the variables dialog can be deleted (OPL1665)



The user can delete the first row in the variables dialog of a flow chart.

Two constant lines per channel allowed in graph window (OPL1044)



The user has the ability to define two constant lines per channel in a graph window.

COMApi: External applications can access inform window values through the COM Api (OPL1611)



WinDarab offers all inform window variables to external applications through its COM Api

(DataFile.DataFileProperties).

3D analysis windows: “Bird view” disables “perspective view” (OPL1662)

 If the user selects “bird view” to watch on a 3D graphic from the top, WinDarab also disables the

“perspective view” option.

Tool tips set for all ribbon controls (OPL1578)



The tool tip text was set for all ribbon controls.

Before deleting a worksheet, the user is asked for confirmation (OPL1421)

 If the user selects “delete worksheet”, WinDarab asks for confirmation before the worksheet is deleted.

Hotkeys for “zoom marked” and “wide cursor” changed (OPL1664)

 The hot key for “wide cursor” was changed from “M” to “W”.

 The key “M” zoom the “marked range” now.

Wrong tool tip text changed (OPL1663)

 The tool tip of the “Show 2D Grafic” was fixed.


Data Logger Import: The prompt to connect the ECU was changed (OPL1671)

 The prompt “Waiting for connection” was supplemented by “Plugin USB stick”.

Graph Display: x-axis range too large for file after overlay was changed (OPL1668)



The range of the x-axis wasn’t adjusted after a new file was attached to an overlay. If the x-range of the new file is much smaller than before, the data was compressed at the left side. Even zooming into the data wasn’t possible, because of the automatic zoom depth limitation of WinDarab.

Data Logger Import: WinDarab seems to hang, if FTP data transmission is interrupted (OPL1667)



If a FTP data transmission is interrupted (e.g. by disconnecting the network cable) the data transmission stops after the network timeout. WinDarab updated the screen but stops responding for additional network timeout because WinDarab tried to send shutdown commands through the



Note: The user can immediately interrupt the FTP connection (even if waiting for the network timeout) by pressing the “Cancel” button

Outingreport weren’t updated (OPL1639)



If updating of an outing report was suspended because the worksheet got inactive while the outing report data was calculated, it could happen that the outing report wasn’t updated any more (unless the user changes settings or reload the outing report configuration).



FTP session.

Now WinDarab doesn’t send any FTP shutdown commands, if a FTP error was caught in the current FTP session.

The issue also affected other analysis windows showing the same symptom.

Crash, after a channel was detached from an y-axis (OPL1633)



WinDarab crashed after a channel was detached from its y-axis in a graph display and no other channel was assigned to the y-axis.

Cursor got outside of visible range, if graph displays with different zoom modes exist (OPL1631)



If there are several graph displays on a worksheet using different zoom modes (e.g. shared and individual) and the cursor is moved in one window, the cursor may jump somewhere outside while trying to synchronize the graph displays.



In some cases the cursor may jump that far, that the cursor goes in front of the first lap or behind the last lap causing the File Explorer to show a triangle in the current lap instead of the circle dot.

File signature batch dialog: The progress window shows the result of the operation (OPL1626)

 If the signatures of measurement files is changed using the “Change file password/signature” dialog, the progress window shows “Password successfully changed” for each processed file.

Before only the green/red check in front of the filename showed the result of the operation and the result column only contained error messages.

Open source component licenses are shown in the “About” dialog (OPL1624)



The licenses of uses Open Source Componen ts are listed in the “About” dialog.

WinDarab got inaccessible, if inform window configuration files are corrupt/incorrect (OPL1625)

 If the user selects a file in the “Open file” dialog, WinDarab loads the inform window configuration files. In case the files are corrupt/incorrect an error message is shows which has to be confirmed by the user (once after WinDarab is started).

Under Windows XP WinDarab got inaccessibly, because the “Open File” dialog captures all input while raising the “file selected” event and the user couldn’t access the “Ok” button of the error message to continue.

“File Open” in “replace file” doesn’t allow to open multiple files (OPL1614)

 If the user wants to replace a file by another, the open file dialog doesn’t allow to open multiple files

– but still allows to select multiple files to be opened as a linked files file.

Saving desktop shows current loaded desktop file (OPL1574)



If the current desktop was loaded the MRUlist of the “Open desktop” button, WinDarab didn’t store the current desktop file name. If the user clicked on “Save desktop”, the name of the desktop appeared which was loaded previously by using the “Open desktop file” dialog.

While loading a new measurement file, the hour glass cursor is shown longer (OPL1572)



If a new file is loaded, the hour glass mouse cursor is shown until the display is updated the first time.

Flow Chart improved (OPL1567/1568)



The behavior of the flow chart was improved: o The flow syntax is checked only, if the flow chart is on the current worksheet.

> E.g. if a file is replaced while the flow chart isn’t visible, the flow chart doesn’t cause any error messages. o If no file is attached to the selected overlay, no flow validation is done at all.

-> Because no error can occur, th e flow doesn’t switch to design mode any more. After assigning a new file to the overlay, the flow chart starts with evaluation. o If loading a desktop / after startup of WinDarab the Flow Chart isn’t switched to design mode always, the design/evaluation mode is restored from the configuration.

Graph window: Bit channels are handles like other channels (OPL1543)



WinDarab now handles bit channels like other channels. o No automatic stacking of bit channels o Bit channels can own a y-axis



To reproduce th e behavior of “Bit Areas” as supported in previous versions of WinDarab, Place bit channels in an own area and select “Stacked mode” for this area.

ASCII export: Progress window improved (OPL1510)



If the user exports data into an ASCII file, the operation can take a long time depending on the export settings. To give a better feedback of the operation the progress window was improved: o The progress shows the process of loading the selected channels into memory. o The progress bar is updated in 1% steps and the current time stamp is displayed. o The ASCII export can be cancelled.

Test issue: WinDarab doesn’t ask for password of protected files until the file is opened/accessed.



If a desktop is loaded referencing to files protected by a password, WinDarab only asks for the password if the file is assigned to an overlay.



If a password protected file is assigned to an overlay, WinDarab immediately asks for the password.

If the password is not provided/known, the file won’t be open but will be listed in the “File Explorer” pane.

 If a file not assigned to an overlay, the file will be listed in the “File Explorer” pane, but the password is requested only, if the file is opened by dropping down the lap list.



Note: In previous version of WinDarab, the user was asked two times for the password if the file was assigned to an overlay:

1. To open and assign the file to the overlay

2. If password was not known to open/show the unused file in the File Explorer Pane,

Test issue: Crash, if mouse is above a FileExplorer entry but not over any column



The crashed is caused, because WinDarab tries to update the quick help of the File Explorer Pane according to the item below the mouse cursor but doesn’t expect the “no column” value.

Test issue: Improved error message, if WinDarab cannot load invalid/corrupt inform files

 If WinDarab find errors while loading inform files, the error message didn’t contain information about the affected file. The message was repeated several times.



Now the error message comes up once (after WinDarab is started; until another inform file causes an error) and contains the affected filename, line number and error text.

Test issue: Inserting/Deleting of user lap triggers is fixed



After changes made to mark laps as In/Out lap ( OPL1594) it wasn’t possible to insert/delete user lap triggers.

Test issue: Graph window not refreshed correctly after marked area is cleared

 If the user reset the marked range of a graph window and the window wasn’t redrawn correctly.

Test issue: Cursor got behind the visible area of a graph window



If the cursor moves to a position behind the current visible range, it could happen, that the window content wasn’t scrolled far enough and the cursor got out of the visible range. The issue could happen, if the user jumps to a position by e.g. clicking in the racetrack window (double-clicking on a result of the analysis window, …)

Test issue: Settings dialog of graph window stayed inactive after a new file was opened



After a user opened a new file in the settings dialog of a graph window, the settings dialog stayed inactive. The user couldn’t continue working with WinDarab and had to kill the application.

 The action “Open file” was removed from the settings dialog because it’s misplaced regarding the UI logic of WinDarab v7.

Test issue: A channels y-axis was left, if the channels is moved to a new area



If the user moves a channel with a y-axis to a new area (not existing area!), the channel is created in the new area but the y-axis stayed in the previous area.

DataLogger/FTP/Burst: After enabling FTP/Burst WinDarab tried to connect immediately



If the user enables FTP/Burst transmission, WinDarab always tried to connect immediately, causing a delay if the device wasn’t reachable. Now WinDarab only tries to connect immediately, if the device is reachable (-> the previous ping was successful).


FlowChart crashes, if evaluation is started (OPL1627)



The flow chart crashed on starting the evaluation, if a table output control was deleted from the output tab but a flow table output item still references to the deleted control.



Another crash occurred after a column of a table was deleted, while the table is sorted by the last column.



If other controls were deleted but still references, no error message was shown if the flow is started.

Now flow items referencing not existent controls caused an error message and the flow cannot be started unless all errors are fixed.

“Open Racetrack” dialog allowed “open” but doesn’t do anything (OPL1622)



To select a racetrack/segmentation, the user has to select a segmentation of a racetrack. But

WinDarab offered “open” already if a racetrack (folder) is selected and not only, if a segmentation of a racetrack is selected.

The issue occurred only, if there is no current racetrack selected yet (e.g. after new installation).

FlowChart: Creating a racetrack segmentation modified (OPL1575)

 To create a racetrack segmentation the settings dialog of the flow item requires the “lap position” of se gment changes. Because users were confused, what “lap position” really means, the text was changed to “Use current position (xdist)” and “Use xdist position in <variable>”.



Note: “lapdist” cannot be used, because “lapdist” doesn’t reference to a concrete lap the segment should to be inserted in (e.g. in the case the evaluation passes the lap trigger this is a problem).

Measurement window: Values on the x-scale never overlap (OPL796)



If zooming deep into the data, the numbers on the x-scale overlapped each other making it impossible to read anything. Now WinDarab will skip numbers, if they would overlap with others

(actually WinDarab will skip every second number).


11.10.2012

Initial release of WinDarab v7.2

Revision Notes - Bosch Motorsport

Related documents

Products

Support

Revision Notes - Bosch Motorsport

Related documents

Add this document to collection(s)

Add this document to saved

Suggest us how to improve StudyLib