In addition, there was no error message if an incorrect new version number was actually used when creating a new release. When creating a new release of a test object or subtree, in certain cases the smallest possible new version number was determined incorrectly if test objects were linked. Now this drag and drop action leads to a "link to" operation in case it fulfills all necessary requirements. In case you dragged and dropped an elementary test object to another elementary test object, it led to a "move" operation and later to an error message. The test protocol navigation with links like "
The HTML text editor now has a light gray border in "read-only" mode. The XY strip chart control tool tip did not show the converted signal values when a unit conversion was selected. The data acquisition conversion dialog showed a wrong value in the sample rate column per signal. We increased the maximum width and height of group and custom controls to 5000x5000 pixels. The AUTOSAR XML parser did not recognize IPv6 addresses in case they were specified with shortened hexadecimal numbers. The ASC file import possibly failed if the first message of the file was a CAN error frame. The MF4 file import crashed in case of unsupported signal variants like 3-bit signals. The MF4 file import did not import the signal limits correctly. Please update ModelCom to version 4.2.53 included in this Service Pack. This does not happen with older versions of ModelCom. ModelCom V4.2.51 caused the model to crash if starting a data acquisition with many signals.
Version 2022 SP2 (2022-February-15) ModuleĪdditional support for dSPACE Release 2021-B.
0 kommentar(er)
