Kontakt
With Service Pack 9 (Update to 2.7 Build 109, click here to download), the following changes become effective:
Support of the new CANdb database format for J1939 (storage of complete 29Bit CAN Id in-stead of only the PGN). The CANdb plug-in J1939 expands the functionality of the CANdb++ editor by simplifying the creation of communication relationships on a J1939 network. So that the functionality of the plug-in is available, a J1939 database must be opened or created.
The plug-in offers the following functionalities:
- Display/Change the attributes of parameter groups
- Adjust the source address of a parameter group
- Change the destination address of a parameter group
- Change the node address and adjust addresses of assigned parameter groups
- Support for defining communication relationships
Export of DBC-files for several ECUs in a single operating step. With menu function "Export ECUs..." in the object menu of item "ECUs" in the object hierarchy DBC-files for several ECUs can be exported.
The names of environment variables and the text descriptions of value descriptions can have a length of up to 80 characters. These have been restricted to 32 characters up to now. The length that can be entered will be defined in the "Settings" dialog on dialog page "Long names".
Extended support for the design of communication relations between nodes, messages and signals:
- While mapping a signal in a message the signal will automatically be inserted as a Tx-signal of the sender nodes of the message.
- While removing a message as a Tx-message of a node the use will be asked whether the signals mapped on the message should be removed from the list of Tx-signals of the sender node as well.
- While removing a signal from a message the user will be asked whether the signal should be removed out of the list of Tx-signals of the sender node as well.
Extended consistency checks:
- The initial value of signals will only be checked if the minimum or the maximum value of the signal is unequal to 0. If both values are set to 0, no check will be per-formed.
- The check whether a message is received from any node is only performed if at least one signal is mapped on the message.
- The consistency check additionally checks whether a signal is received by an ECU multiple times.
Further changes:
- The configuration of a multiplexed signal a multiplexer signal within a message is not allowed any more, since multi level multiplexing is not supported.
- The initial value of signals will be stored in the user defined attribute "GenSigStart-Value" by default, and no longer in attribute "GenSigInavticeValue". If needed this can be changes in entry "AttrGenSigInitialStartValue" of the CANdb.ini configuration file.
- Because in DBC files no comments for attribute definitions can be stored, the entry of the comments is not possible if a DBC files is opened. Hint: The comments of attribute definitions will not be exported during the export of data from an MDC database to a DBC file.
- The position of a signal in a message will be adjusted as well as possible when changing the byte order of the signal (Intel to Motorola or vice versa). If possible the signal will still be placed on the same bits in the data field of the message.
- While importing messages no automatic adjustment of the DLC to the minimum size needed by the mapped signals will be performed. The DLC will be copied unchanged into the destination database. This change has effect on the import of whole databases (menu function "Import Database...") an on the copy operation of messages in the difference view.
- Signal groups and value tables of signals will be imported into the destination data-base as well when a database is imported with menu function "Import Database...".
- Multiplexer values of signals can be entered in hex-format as well. The multiplexer values will always be displayed according to the global display settings. If the global display setting is set to decimal display the value has to be preceded by a "0x".
- Float values can be entered in hex format. The entered value has to be preceded by a "0x". The entered value will always be interpreted as an integer value without fractional part. The display of float values is always performed in decimal format.
- Errors when performing an undo operation after creation or deletion of a network node in DBC files have been solved.