Updates existing installations of version 19.0 to 19.0.11 SP1 Hotfix 1. The following changes become effective with version 19.0.11:
User Operation and Display
Copying windows via drag and drop between configuration tabs is possible again.
When importing devices from other projects, the Project Selection dialog contains more information.
When selecting signals from measurement files, the signals of bus messages are offered in the dialog again.
Ethernet monitor: Stability improvement in case many signals are received via duplicated PDUs
DHPR/RIF: XCP protocol layer version 1.0 can again be selected in the extended settings.
Measurement Data Acquisition
VP6400: Limit the integrated XL NIC adapters to CSM modules
Enhanced message decoding checks for PDUs within container PDUs for bus monitors
DHPR: Synchronization improvement in case of synchronized measurement time
Vector IO: During measurement start digitial output will not get a short reset anymore
RIF devices no longer use XCP Connection mode 2.
Issues related to trigger definition were resolved.
Ethernet monitor: An error that occurred when using the discontinued import strategy for array elements was fixed.
CAN: Improved error messages in case measurement hardware is not synchronized
XCP: An error was fixed which occurred during calculation of time information when using measurement devices synchronized via PTP.
XCP: Improved handling when sending XCP 1.3 multicasts (fix for "internal error code 12")
VP6400: Improved precision of time synchronization by using XCP 1.3
XCP: Bugfix for supposed timeouts during measurement start
The recording of bus messages into PCAP format can be split into several files.
The macros for the recorder events also deliver the associated events when the data is split into multiple files.
When recording bus messages in several BLF files, empty temporary files are removed again.
(HF1) ETH monitor: An issue that occured when using network based mode in combination with the Vector Time Synchronization Sercvice was fixed.
File extensions of MAP files are no longer truncated to 3 characters.
The path to the ASAP2 file is now also correctly transferred to ASAP2 Studio when it contains UTF-8 multibyte characters.
Calibration Data Management (Parameter sets & vCDMstudio)
Improved robustness when activating datasets: The calibration data history is reset correctly.
Improved robustness when inserting parameters into the CANape configuration: If dataset management is active and the current dataset does not contain all parameters, a check for this is done upon inserting.
Fixed treatment of HEX files in dataset management: Upon saving the datasets, data segments are not shortened anymore.
Extended MATLAB/Simulink Support
Conversion rule and unit definitions are displayed for MATLAB/Simulink functions.
If the Advanced Code Check fails, the device will not be switched to "measurement only" mode automatically. Instead, the user can choose to continue or abort in the info dialog.
An application crash when loading a project without connected AXIS cameras has been solved.
Improved video recording with pre-trigger time
Added support for VX1161.51C/D
The controls of the Video window are automatically activated after a measurement.
Functions and Scripts
Speed up of execution time of CASL scripts in case of calling many other CASL scripts.
The CASL modifier "interpolate" can now be used for measured curves or maps.
A sporadic problem at the start of data mining has been fixed.
A new column with consecutive numbers allows easier mapping of error messages for signals which are assigned to a Data Mining analysis profile.
Arrays of structures from bus messages can be used for visualization with GFX objects.
The calibration file for DHPR devices with video data is saved correctly again.
Measurement Data Visualization and Manual Analysis
A problem was solved that occurred when multiple signals with same name and same source existed inside measurement configuration and mode "Display Values from Measurement File" was used.
In "Display from measurement file" mode, identically named measurement signals from different devices are correctly assigned.
Working with Measurement Files
CANconv: Support dynamically assigned ports for AUTOSAR PDUs
Deanonymization of structures with only one component does work now.
The measurement export converter into ASCII format does not change dots inside string values into commas anymore.
The measurement file export converter into MATLAB format includes signal values marked with the invalid flag.
During deanonymisation, single recorded signals with a structure name are added using the correct offset.
The measurement data Import converter for ASCII files supports UNIX epoch timestamps (nano seconds since 1.1.1970).
Additionally defined templates for the ASCII Import converter are taken into account when loading text files.
The new 64bit version of the measurement data export converter to MATLAB format supports larger data volumes.
To convert measurement data in TTL format, a TTTechlog.ini file can be saved in the settings directory.
When merging MDF files from a file series, special signals, which are contained in each single file since start of measurement, will not be considered for determination of the time range.
A new option bit for the MdfMerge converter can be used to ignore multimedia signals stored with AVI attachment and a sync signal, e.g. if the merge operation is not possible due to different conversion rules of the sync signal. Note: AVI attachments cannot not be merged using MdfMerge.
Merging MDF files now also works when only some files contain a signal (group), e.g. as with "bus sorted" MF4 files containing raw CAN messages.
When extracting a time range from an MF4 file with compressed signal data, the data blocks containing variable length signal data (VLSD) will be written compressed in the result file, too (using the default settings).
Measurement Data Management
The vMDM add-in also works after performing an upgrade installation.
Files now can be moved to another collection via context menu command in Search Result view (only available starting with vMDM server 3.2.x)
User will be informed via message box if vMDM connection credentials cannot be found in the Windows vault.
The shell extension commands to copy or move MDF files to vMDM now also accept files with extension DAT.
Usability improvement by directly executing a search when switching a collection in vMDM Search view while staying in the view (instead of switching to Home view).
Easier management of computer collection for local vMDM as own use case in GUI.
Bulk deletion of all filtered files in a search result is possible via a new context menu command (only available starting with vMDM server 3.2.x).
Both the CASL method MdmCheckFileStatus() and the respective command line option for vMDM now deliver more detailed state or error information about an uploaded file.
It now is possible to move more than 16 files to vMDM via the Vector Shell Extension .