MxPLT is the Danlaw Physical Layer Test Tool for MxSuite. It is a cost-effective desktop solution that automatically performs CAN Network physical layer tests and LIN conformance tests. MxPLT is an add-on option for MxSuite, the industry-leading embedded-software test environment. MxPLT reduces test time and operational costs over traditional automated testing.
The purpose of the MxPLT tool is to automate the physical layer tests for various CAN and LIN conformance test specifications. The basic modules required to achieve automation of physical layer tests are:
•The MxPLT Device
•A PC with MxSuite and the MxPLT Device Transform, the PLT Test Manager Transform, the PicoScope Transform, and the LVTVBS Transform
The main objectives are executing TestCases, generating test reports, and outputting the test results to an OEM formatted document.
•MxPLT with 12V Adapter
•ADD2 COMM dongle
oQuad core CPU
o6 GB RAM
oWindows 7 (32 or 64 bit)
Also see Recommended Configuration.
•Microsoft .NET Framework 4.0 (See Installing the MxSuite.)
•PicoScope setup 6.7.40 or latest (http://www.picotech.com/download.html)
•Microsoft Office 2007 or later
•CAN or LIN ID for your test
•The following (available from Danlaw support: firstname.lastname@example.org):
oDownload credentials for MxSuite and LVT
oMxPLT template project
oPassword (unlock code) for LVT installation
•LVTGO-VBS software (Download here. Use same credentials as above.)
•ADD2 COMM Dongle Drivers included in LVTGO-VBS download
Note: Change the power options in Windows Control Panel to ensure that your PC does not go into sleep mode.
1.Open Control Panel Power Options.
2.Select "Balanced (recommended)" under Select a power plan.
3.Select "Change when the computer sleeps"
4.Select “Never” for the “Turn Off the display” and “Put the computer to sleep” options.
5.Click "Save changes"
These options may vary depending on the Windows version.
1.Create a folder for LVT files.
3.Run DanlawLVTInstaller.exe, which is located in the Danlaw LVT Install folder.
4.Check all the boxes to install the add2 Dongle Driver.
5.Click Next and follow the wizard through approximately 30 prompts.
6.Update the add2 Dongle Driver. See: Driver Update for COMMDongle
7.Each time you are prompted, enter the password (also called the unlock code). If you don't have a password, contact email@example.com.
8.For a new installation, select Typical.
9.Follow the wizard until you see the VISUALCONNX CAN Drivers dialog. Select "add2 COMM Dongle Driver (32 and 64 bit)".
11.Plug the ADD2 Dongle into a USB port on the PC. Observe it configure to “COMMDongle USB Device”. Do not connect the other end at this time.
12.Click the Finish and Close buttons to close the installation wizards.
13.Open the Device Manager from the Windows Control Panel.
14.When successfully installed, "COMMDongle USB Device" is listed in the Device Manager as shown below. If it is not, use the following procedure.
1.Install the PicoScope software from the CD or download drivers from the PicoScope website. (Do not use PicoScope Automotive. Match the version to your PicoScope hardware.)
2.Connect the PicoScope USB connector to the PC.
3.Make connections between the PicoScope and the scope connectors on the MxPLT Device:
a.Connect Channel “A” on PicoScope to “CH1” on the MxPLT Device with male-to-male scope connector.
b.Connect Channel “B” on PicoScope to “CH2” on the MxPLT Device with male-to-male scope connector.
c.Connect Channel “EXT” on PicoScope to “TRG” on the MxPLT Device with male-to-male scope connector.
The MxPLT Test Conversion Tool is a generic tool for creating the Scenarios and Test case files to be used with MxSuite, which is executed to perform automated physical layer testing based on the following specifications:
•General Motors GMW14241
•Ford LIN: 000601.101AA, 000601.111.A
The TestCase Definition files are Excel (.xls or .xlsx) files. See the sample projects for examples of the file format. You can use Excel to view and modify the files.
1.Be sure the template project corresponding to the appropriate OEM specification is installed on your PC.
2.Run DANLAW LVT 6 and keep it running. Click the Configure and Run Test button. Go to the Captured Transfer tab, and click the Connect and sync button.
4.Open the template project. (File->Open->Project from the main menu.)
5.Click Edit Harness ( ) to start MxTransIt.
6.In MxTransIt, click on the PLT Test Manager Transform to select it and display its Properties box.
7.Click the Launch MxPLTConversionTool Verb to open the tool.
8.Select the TestCase Generation tab to generate Scenarios and TestCases dynamically based on selected inputs.
9.Following are the inputs for the ‘TestCases Generation’ tab of the MxPLT tool.
a.Select TestCase Definition File. Click the browse button () to select the file. Once the input test case definition file is selected fields in the GUI (Vendor Spec, Baud rate, CAN channel, Worksheet type, Comm enable type, Communication crank, LIN device type, LIN device clock, Supply voltage range, Load resistor) are automatically loaded.
b.Enter a valid CAN Id, LIN Id, High-Speed CAN Id, or Wakeup CAN Id as applicable based on the ECU under test.
c.Simulation Test. (Optional) Select the Simulation Test checkbox for MxPLT OEM testing without connecting a real module (ECU). In this mode, MxPLT transmits the messages on channel CAN1 and receives on channel CAN2. LIN is not supported for this testing.
d.Select MxV Project Folder. Click the browse button () to select the MxVDev project folder.
10.Click the Generate TestCases button to generate Scenarios and TestCases for a specific OEM.
11.Select the “Message Configuration” tab.
12.Configured default messages are displayed and you can edit the messages as applicable based on the ECU under test. This message is used to wake-up the DUT and to continue the ECU communication (BCM message).
13.Click the “Save Configuration” button. Observe the “XML file successfully generated” message.
Note: The CAN Configuration file path is same as the selected MxV Project folder path in the “TestCase Generation” tab.
14.Close the Test Conversion Tool, but leave MxVDev running.
Self tests are for testing all MxPLT hardware components, which include relays, DAQ, Voltage source, Current Source, CAN bus, LVT VBS, and scope channels. More self tests may be added in the future.
2.Select Help->Copy Samples. (See Sample Projects.)
3.Select File-> Open-> Project:
3.Use the Open dialog to select the project file:
4.Click the Open button.
The generated Scenarios and TestCases are displayed in the MxVDev Project Explorer.
6.Save the Harness.
7.In MxVDev, click Yes when this dialog is displayed:
8.In MxVDev, select Tools->Regression Test->New from the main menu.
9.Click the Add button in the Regression Command File dialog:
10.Enter User Details (Optional) in Test Info panel, click Next.
11.Click Next in the Regression Output Wizard.
12.Click Next in the Distribution List.
13.Click Next in the Execution Options.
14.Under Scenario Query Builder, expand the MxPLTSelfTest tree, and select the Scenario (for example: Relay Voltage Test.mxs).
15.Deselect these Scenarios:
•LSFT CAN Bus Test.mxs
•DWCAN Bus Test.mxs
•SWCAN Bus Test.mxs
•LIN Bus Test.mxs
Note: These tests are to verify the transceivers.
17.Click Finish to display the Save Regression Script dialog:
18.Save the Regression Script (.mxreg) file.
19.Click the "Close and Run" button in the Regression Command File window.
20.The Regression Test Progress Window shows the progress of the test for the selected Scenario.
21.After completion of Regression test, a HTML file automatically displays.
1.The Transceiver tests (LSFT, DWCAN, LIN, SWCAN) should run individually in regression by changing the applicable Transceivers:
•DWCAN Bus Test.mxs – Configuration 1 and Configuration 5
•LSFT CAN Bus Test.mxs – Configuration 2
•SWCAN Bus Test.mxs – Configuration 3
•LIN Bus Test – Configuration 4
2.Make sure that the DUT (Real ECU) and Transceiver do not connect to the MxPLT Device for testing the self tests.
1.Supply Voltage Test:
These tests checks whether the voltage available on Vbatt is probed correctly or not.
2.Relay Voltage Test:
These tests check the accuracy of Relay components in the MxPLT Board.
3.DAC Voltage Test:
These tests check the accuracy of DAC voltage levels in the MxPLT Board.
4.Pulse Test Sequence 1/2:
These tests check the accuracy of capacitance components in the MxPLT Board.
5.LSFT CAN/DWCAN/SWCAN/LIN Bus Test:
These tests check whether transceivers are able to communicate between channel 1 to Channel 2 and vice versa.
6.Current Source Test
This test checks the accuracy of Current Source in the MxPLT Board.
These tests check whether the LVT is setting appropriate voltages in the MxPLT board or not and checks the same voltage read back values from the LVT application.
8.LVT Offset Voltage Test
These tests check whether the LVT is setting appropriate Offset voltages in the MxPLT board and checks the same offset voltage read back values from the LVT application.
1.Connect the ECU to the MxPLT hardware.
2.Select Tools->Regression Test->New from the MxVDev main menu.
3.Click the Add button in the Regression Command File dialog.
4.Enter User Details (Optional) in the Test Info panel. Click Next.
5.Click Next in the Regression Output dialog.
6.Click Next in the Distribution List dialog.
7.Click Next in the Execution Options dialog.
8.In the Scenario Query Builder panel, expand the tree of any of the following folders which are displayed:
9.Select one or more Scenarios (for example:"188.8.131.52 RecessiveOutputVoltageLevels.mxs") and click Next.
11.Save the Regression Script File (for example: "RegressionTest1.mxreg").
12.Click the "Close and Run" button in the Regression Command File.
The Regression Test Progress Window shows the progress of the test and pass/fail information.
After completion of Regression Test, an HTML file is automatically generated to display the Reports and a folder (e.g: RegressionTest1) is created with the same file name as the default path.
Use the same Regression Report folder in MxPLT Test Conversion Tool for generating a Test Report for the Scenario in Word or Excel format as specified by the OEM.
Enter the following parameters for the MxPLT Test Report Generation tool:
1.In MxTransIt, click on the PLT Test Manager Transform to select it and display its Properties box.
2.Click the Launch MxPLTConversionTool Verb to open the tool.
3.Select the Test Report Generation tab.
4.Browse to select the TestCase Definition File.
5.In “Select Regression Report,” browse for Regression Report folder.
6.In “Select Test Report Template” browse for appropriate report template file as per selected input test case definition file.
MxPLT Test Conversion Tool (Test Report Generation)
7.Click on Generate Test Report.
Note: To create a Regression Script file, use MxVDev to run a Regression Test for the Scenarios generated by the utility. After regression execution of all the generated automated test cases from MxVDev, the regression reports are generated in the specific folder in native MxSuite format. The user can use this tool to convert the MxSuite native test report format to the appropriate test reports as per selected input test case definition file.
Transceiver Module (Part No: 9N0053):
Configuration – 01 DW CAN for GMW14241 and Chrysler Z0166 High-Speed physical layer tests
Configuration – 02 DW CAN FT for FIAT Z0140 Low-Speed tolerant physical layer tests
Configuration – 03 SW CAN for GMW14241 Low-Speed (SW) physical layer tests
Configuration – 04 LIN for J2602 physical layer tests
Configuration – 05 DW CAN for GMW14241 and Fiat Z0146 High-Speed physical layer tests
Note: For GMW14241 tests, use configuration 01 or 05.
Use this procedure when new MxPLT firmware is released:
1.Power on the MxPLT Device without the USB cable.
2.Connect the USB cable from the MxPLT device to the PC.
3.The device appears as a removable disk drive in the PC.
4.Open the disk and delete the firmware.bin file.
5.Paste the latest file from one of the following:
•64 bit: C:\Program Files (x86)\MicroMax\MxSuite 3.XX.XXX.XXXXX\Bin\MxPLT_Firmware.bin
•32 bit: C:\Program Files\MicroMax\MxSuite 3. 3.XX.XXX.XXXXX \Bin\MxPLT_Firmware.bin
6.Restart the device with the USB cable connected.
These specifications were used to design the sample projects: