Simulated and Real (Hardware) Nodes Connected with a Device Interface Transform

Simulated and Real (Hardware) Nodes Connected with a Device Interface Transform

CAN and LIN Buses

The MxSuite provides a bus simulation that enables you to send and receive CAN or LIN messages between nodes.  Each bus must have a DBC or LDF file. The file defines the nodes connected to the bus and the type and format of messages. This file is typically provided by the automobile manufacturer. If necessary, you can edit the file or create your own using the Vector CANdb++ Editor or other tool.

Note:

A CAN bus simulation can operate in MxVDev, MxTransIt, or both.

A LIN bus simulation can operate in MxVDev or MxTransIt, but not both.

A MOST bus simulation operates in MxTransIt only.

The nodes can be:

A hardware node

A node simulated by MxVDev

A node simulated by Transforms in MxTransIt

A node simulated by an MxVMC

hmtoggle_plus1Types of Nodes
hmtoggle_plus1Message Definition
hmtoggle_plus1Using Buses in Mx-VDev
hmtoggle_plus1Using Buses in Mx-TransIt
hmtoggle_plus1Supported Hardware

 

If you need to send or assemble messages longer than 8 bytes over a CAN, you can use ISO 15765 Transport Layer Transforms or messages. See Transport Request/Response Transforms or Configuring a Transport Layer.

You can use the CCP Transform to flash program your SUT. See CCP/XCP.

In this Section:

Working with a CAN Bus

Working with a LIN Bus

Automatic Message Transmission

Configuring a Transport Layer

Connecting to a Hardware Bus

CAPL Scripts

Tx Echo

Transferring a Bus from MxVDev to the Harness

Virtual Bus Monitor

Related Topics:

Diagnostics Testing

Network Configuration

CAN Transforms (includes examples)

LIN Transforms

MOST Transforms

Importing Vector CAN Log Files