Network Configuration

The Network configuration is stored in a fixed name XML file that includes the machine name.  This is done since the CAN hardware attached to the PC is uniquely identified to ensure the same device is connected to the same virtual bus every time MxVDev is launched and different machines will likely have different CAN hardware connected.  However, if the hardware is the same, you can import another configuration file.

Search for New Hardware

•List of devices detected by MxVDev

•If connected devices are not listed, ensure they are functional with the utilities that accompany the hardware.  Once the devices are installed and configured properly, they are available to MxVDev.

On start-up, MxVDev queries the system for the available hardware.  If hardware is connected or removed while MxVDev is running, select "Search..." to update the list of available devices.

Associate the device with a bus by dragging it onto the bus in the Virtual Communications Buses panel:

MxVDev supports several independent CAN devices (limited only by your PC), so it can be used to test on several CAN buses simultaneously. Interface drivers are provided for the following devices:

•ValueCAN and NeoVI from Intrepid Controls, Inc.

•CANCard, CANBoard, and CANCase (for both X and XL) from Vector CANtech

•CAN Interface devices from National Instruments

Refer to the procedure for Connecting to a Hardware Bus.

The following commands apply to the Virtual Communication Buses box:

Add CAN, Add LIN, Add J-1850, Add K-Line - The drop-down list inserts a new virtual bus at the end of the list.

Remove - Removes the selected virtual bus.

Associate Device and Bus - Drag a device from the Devices to the desired Virtual Communication Bus.

When you add or select a bus, the corresponding Configuration form is displayed on the right side of the Network Configuration dialog box.

CAN Network

Click in the second column to set values.

•CAN Database - Click in the CAN Database row to display the button.  Click the button to display the CAN Bus Configuration dialog box shown below.

•GM Lan - Set to True for GM LAN CAN buses. This parameter is used to alter the baud rate generators register values for some devices (such as the ValueCAN series of hardware).

•Single Wire - Set to True if using a single-wire configuration.  This is particularly important when using devices that support multiple target buses, such as the NeoVI devices.

Network

•Baud Rate - bit rate of the bus.

•Name - name used visually throughout MxVDev to identify the bus.

CAN Bus Configuration

Database Files

Select one or more CAN DBC files. This file is typically provided by the automobile manufacturer.

Configure Bus Drivers between MxVDev and bus

You can use TestCases to send messages to one or more nodes on the bus. The destination of the messages is defined in the DBC file. To receive responses from a node, select the node in the Receive From column.

Example 1: The Simplest Case

Node A receives messages from an MxVDev TestCase and sends responses. Node A must be selected in the Receive From column so MxVDev can receive the responses. The destination of CAN signals from a TestCase (and other sources) is defined in the DBC file. Other nodes may be simulated as described below.

Node Simulation

When testing one or more nodes on a CAN bus, MxVDev can simulate messages from other nodes on the bus. In a typical configuration, the nodes under test are marked as Receive From and some or all of the other nodes are simulated. See Types of Nodes.

If a node is simulated, you can use the tree structure in the Simulate and Transmit for column to specify which messages to transmit.

Note: If a node is simulated by a Transform in the Harness, be sure that the same node is not simulated by MxVDev. Selecting a node in both places can result in duplicate messages on the bus.

In the first column (Receive From), select one or more nodes. We call these Receive From nodes. The meaning of your selections is controlled by the buttons and check box described below:

•If you select Simulate all nodes that are not selected in the Receive Filter (the first button) AND check the Import All box, MxVDev simulates all messages from all nodes except the Receive From nodes.
 
If you select the first button, but do NOT check the Import All box, MxVDev simulates only messages that are used by a Receive From node.
 
When the first button is selected, the third column (Simulate and Transmit for) is not used.
 
Example 2:

oThe first button is selected; the Import All box is NOT checked.

oNode B is checked in the Receive From column.

oNode A sends messages used by Node B and Node C; Node C sends messages for Node B.

Node A is simulated because it sends messages for Node B, but only the message used by Node B is imported.

•If you select Manually configure which nodes to simulate (the second button), use the third column to select which other nodes are to be simulated. If the Import All box is not checked, the node is not simulated unless it sends messages read by a Receive From node.
 
Example 3:

oThe second button is selected; the Import All box is NOT checked.

oNode B is checked in the Receive From column.

oNode A sends messages used by Node B and Node C; Node C sends messages for Node B.

oThe Simulated Nodes column is checked for Nodes A and C.

Node A is simulated because it sends messages for node B, but only the message used by node B is imported.

Node C is not simulated even though it is checked, because it does not send any messages for the Receive From node.

•Import all messages from all nodes not under test (the Import All box).  If you check this box, all message signals from nodes not marked Receive From are imported into the Signal Dictionary. When this box is not checked, nodes that do not send messages to a node under test are not simulated. See the previous two bullets.

Message Name Translation

If you have messages on different buses with the same name, this creates a conflict in MxVDev.  Likewise, if you have an input and output signal with the same name, that also creates a conflict. To avoid this problem, add placeholder fields to create unique message names.

Also, see CAN Overview  and Connecting to a Hardware Bus.

To configure a LIN bus, an LDF is required. Set the File Path property first. The file is usually provided by the automobile manufacturer.

LIN Network

•LIN Database - Click the box in the second column of the LIN Database row to display the button.  Click the button to display the LIN Bus Configuration dialog box shown below.

Network

•Baud Rate - Bit rate of the bus.

•Name - The name used visually throughout MxVDev to identify the bus.

LIN Bus Configuration

LIN Bus Configuration is similar to CAN Bus Configuration.

Schedule Table - Select the schedule table you wish to use. Schedule tables are defined in the LDF.

If you are performing Diagnostic testing, select schedule tables for Diagnostic Request and Diagnostic Response.

Also, see Connecting to a Hardware Bus.