News

Download

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

• The assignment of CAN messages to default scenarios in the CAN timing analysis has been improved:
  • All periodic messages (either pure cyclic, or mixed) are considered in the scenario to calculate the base bus load.
  • In the worst case scenario the "ifActive" messages are considered with their fast cycle time
  • In the worst case scenario the "mixed" messages are considered with the minimum of their fast cycle time and their delay time

• Default scenarios renamed
  • Scenario "Periodic" renamed in "Base Load": Messages with a fixed cycle time independent of any events are considered with their fixed cycle time.
  • Scenario "Sporadic messages" renamed in "Worst case": Sporadic messages are considered with their minimum cycle time. Alternatively they messages may be considered with a fixed default cycle time.

• Consistency checks for timing properties of Vector Interaction Layer added:
  • Check that a message with send type "ifActive" at least has a signal with send type "ifActive" (Warning).
  • Check that a cyclic message has a cycle time greater than 0 (Warning). A message is a cyclic message if the message send type is cyclic or at least one signal has send type cyclic.
  • Check that a message that isn't send cyclically doesn't have a cycle time greater then 0 (Info).
  • Check that messages that are send repetitive have a repetition number greater than 0 and a fast cycle time greater than 0 (Warnings). A message is send repetitive if at least one signal has send type "OnChangeWithRepetition", "OnWriteWithRepetition", or "IfActiveWithRepetition".
  • Check that a message that isn't send repetitive doesn't has a repetition number greater than 0 (Info).
  • Check that a message that has send type "ifActive" or at least one signal has send type "ifActive" has a fast cycle time greater than 0 (Warning).
  • Check that a message's delay time is less than the message's cycle time and the message's fast cycle time (Warning).

• 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
• 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.