<< Click here to display Table of Contents >>

MxDrive

Contents

MxDrive is a separately-priced system of Transforms and hardware for testing ADAS.

MxDriveBlue

Requirements

Set Up

These are the high-level steps to create an MxDrive test:

1.Create a Harness using MxTransIt. Use the Transforms listed below.

2.Define your Resources.

3.Create your TestCases.

4.Populate the TestCases.

There is a sample project provided to demonstrate MxDrive capabilities.

Transforms

MxDrive Simulator

MxDrive-Simulator

The MxDrive Simulator Transform accepts data, such as location and path,. It uses this data to simulate the movement and interaction of the vehicles and display the simulation in a graphical display. The current status of all vehicles in the simulation is transmitted from the Vehicle Data Out outport.

Ports

Inports:

Reset Simulation. A transition on this Event port causes all vehicles and drive commands that were created by transitions to be deleted.

Simulation Configuration. Create a transition on this Signal to set the starting time and date of the simulation or to select a map.

MxDrive-SimConfig-editor

Start/Stop Simulation. Use this port to issue Start Simulation and Stop Simulation commands. Use the transition editor to associate a Vehicle Name (from a Define Vehicle transition) with a Vehicle of Interest label. For example, you could specify a vehicle named HeavyTruck as Vehicle of Interest 1 (VOI1).

Transition Editor dialog for Start/Stop Simulation Signal

Drive Command PreDefined. Use this port to issue Define Vehicle, Define Route, Set Acceleration, Set Gradients, and Set Path commands. When you export the port to MxVDev, you can use transition editors such as these to enter the commands in a TestCase:

DriveCmd-PreDefined1 DriveCmd-PreDefined2

Drive Command On The Fly. Use this port to issue drive commands. These commands are executed at the time of the transition.

When you export the port to MxVDev, you can use transition editors such as this to enter the commands in a TestCase:

MxDrive-OntheFly-editor

Roadside Unit Configuration.

MxDrive-RUConfig

Roadside Unit On the Fly Command.

Vulnerable Road User Configuration.

MxDrive-VulRoadUserConfig

Vulnerable Road User On the Fly Command.

Outports:

Simulation State.

Host Vehicle Data. This message port provides data about the simulated host vehicle at the current simulation time. Usually, this port is connected to MxDrive Derived Data Decoder Transforms.

Remote Vehicle Data. This message port provides data about all simulated remote vehicles at the current simulation time. Usually, this port is connected to MxDrive Derived Data Decoder Transforms.

Roadside Unit Data. This message port provides data about all simulated ... at the current simulation time.

Vulnerable Road User Data. This message port provides data about all simulated ... at the current simulation time.

Properties

Resource File Path. Browse to the location of the resource file. Resources are the components of a simulation. Resources include: Vehicle types, maps, and routes.

Resources

You can define Resources of the following types for use in Simulations:

Vehicle Types, Roadside Unit Types, Maps, Routes, Acceleration Profiles, and Gradient Profiles

To create Resources, click the Create Resources verb in the Properties box of the MxDrive Simulator Transform.

MxDrive-resources-marked

MxDrive Vehicle Data Decoder

This Transform accepts messages on the Vehicle Data In port and extracts data for the specified vehicle only. The data is decoded and transmitted from the outports. Each Vehicle Data Decoder Transform corresponds to one vehicle.

MxDrive-VehicleDecoder

Properties

Use the properties to specify which data to extract from the input messages.

Filter Type. Select Filter by Name or Filter by Label.

Vehicle Label. The Vehicle Label is defined in Start Simulation transitions.

Vehicle Name. The Vehicle Name is defined in Define Vehicle transitions. When Filter by Name is selected, messages that contain this name are decoded.

The Vehicle Id is also used in the names for the outports.

MxDrive-VehicleDecoder-properties-marked