CAN-nodes

In a real system, messages are transmitted serially, usually on a pair of wires, from one component to another. In the Virtual Wiring Harness, Virtual Buses accommodate delivery of message-based information from one component to another.

MxSuite provides Virtual Buses to emulate network communications. A Virtual Bus can be configured as a CAN or LIN bus.  Communication parameters, such as baud rate or single-wire are attached to the Virtual Bus (as opposed to devices).  Devices attached to the virtual bus should be configured to support the configuration of the bus.

The implementation of the Virtual Buses is quite generic.  Some characteristics include:

Buses can have a point to point topology, or there can be several peers such as in CAN, or master/slave such as in LIN.

Bus traffic can be monitored and traced.

For CAN buses, a DBC file can be associated with each bus.  It is then possible to simulate nodes that are not present on the bus.

If an appropriate interface device is configured, the virtual bus can be connected to a real physical bus.  In this way the virtual system can interchange information in real time with a real system outside the computer.

Other products can connect to an MxSuite Virtual Bus.  For example, CANalyzer, CANoe and CANape can be connected to a Virtual CAN Bus.  This means for example you can use CANape to calibrate a virtual system.

Bridging

Physical CAN (or LIN) buses can be bridged to the Virtual Bus using supported Device Interface hardware.  Vector, Intrepid, and PEAK devices are supported. There is no practical limit to the number of devices that can be attached to a Virtual Bus.

SUT Interface

The MxVuC library provides an API and emulated interrupts to connect a SIL SUT to the Virtual Buses. This makes it easy to redirect an existing CAN & Transport stack from target microcontroller registers/hardware to the Virtual Bus. In addition, new development can utilize the ISO15765 Transport Layer built-in into our Virtual Bus infrastructure to streamline development and testing of diagnostics prior to the integration of the production transport stack.

GUI Interface

The MxVGUI snoops all Virtual Buses and decodes the messages into CAN signals allowing the user to monitor messages as a whole or particular fields of the messages.

Protocols

CAN/LIN

CAN (both standard and extended) and LIN virtual buses are available at this time.

CAN ISO15765 Transport Layer

ISO15765 compliant CAN Transport Layer to support vehicle CAN diagnostics testing is supported.

 

For detail on setting up a Virtual Bus, see Bus Overview.

Related Topics:

Network Configuration

Virtual Wiring Harness