News

Download

With Service Pack 1 (Update to 2.0 Build 42), the following changes become effective:

• Positioning of signals and signal groups in messages has been improved:
  • Initial positioning of signal group now works correct. In older versions signal groups aren't positioned optimally.
  • Positioning of signals with byte order "Motorola" and display format set to "Motorola forward LSB" no works correct. An error is reported if the signal is placed outside of the message's data field. In previous versions a default position has been taken as the signal's position.

• Messages for validation of value range check for signal initial and inactive values has been improved:
  • If the value can't be represented in a signal with the given length an error is reported.
  • If the value exceeds or is below the maximum or minimum value defined for the signal a warning is reported.
  • The warning messages now indicate clearly which value violation occurs. Either the value can't be represented with a signal of the given size or the value violates the min-max range defined for the signal.

• The performance of CM-related operations has been improved. Especially when working with large CM repositories, the following operations are much faster now:
  • CM Disconnect / Re-Connect
  • Creation and renaming of library objects
  • Import of databases
  • Initial connection with a CM repository and retrieval of a large number of objects from CM repository
  • Adding an object with a large number of referenced library objects to CM repository

• The vehicle project - based consistency check now reports the usage of signals in different versions
• Check and calculation of the assumed precision parameter of FlexRay clusters improved. The adjustment now uses the "best case" and the "worst case" precision for the adjustment.
• Check for Constraint 15 of the FlexRay protocol specification added.
• Minor improvements:
  • Automatic calculation of a signal's minimum and maximum values corrected if factor is negative.
  • All networks are shown for gateway ECUs in the ECU list of a vehicle project. In previous versions only two networks have been displayed with their names. If a gateway has been connected to more than two networks only the string "<>" was displayed.