Transformation of CANdb into a hierarchical communication model
CAN2FUN transforms CANdbc files into a fully graphical ESCAPE communication model. It generates busses, nodes and a library of messages and signals.
The transformation also includes the definition of signals and value tables as data types. Messages are transformed into engineering objects. Thus the bus communication can be handled with existing PDM systems without the need for CANdb or own tool development.
Example: CAN-Communikation network of a field harvester
At the Transformation CAN2FUN generates a library of Messages and signals. CAN2FUN generates a “Sender”-object and a “Receive”-object for each messages as a type in the library. There will be a “Sender.message”-instance in the sending node and a “Receive-message”-instance in each receiving node.
Each message object has an interface representing the message itself and the signals mapped to the message.
The terminal representing the sender message will automatically be connected with the message terminal of all receiving messages (see the picture below)
The attributes of signals usually are defined in the CANdb. These attributes will all be transformed into the attributes of datatypes.
Each message object keeps an interface for the CAN message and all the signals mapped to a message. Each signal has a unique datatype which defines the signal with all its values and significations.
The definition of a datatype for a signal is the single point of truth for a signal throughout the whole engineering process. Attributes can be handled with existing data management systems like PDM/PLM.
Version- and variant management thus can also be applied to interface objects and software variables.
Example: CAN-Message with two receivers (here: ECU_gearbox and ECU_rear)
CAN-communication network (Connections of one node)
CAN-Communication network (effects of a fault of a node)
Graphical analysis of the Communication network
CAN2FUN