Logging

The MxSuite logs significant events and errors. To view MxSuite log files, select Help->View Log Files from the main menu in MxVDev or MxTransIt.  When reporting problems, it is helpful to zip these files and send them to mxsupport@danlawinc.com with the support request.

For a description of the files, see MxSuite Files and Folders.

It is not usually necessary to include files with a date and time in the file name. For example:

MxVGUI_08_05_2019 15_22_03.log

These files may be omitted when reporting problems.

Use the options on the Project Settings–Logging Tab to enable logging during Scenario execution. You can log stimulus or result data for the Scenario or for each TestCase. By default, these files are stored in the ScenariosAndTestCases subfolder in the project folder. The log file name is the name of the Scenario followed by .mxlog. For example:

DoorTurnScenario.mxlog

If you double-click the .mxlog file, the Scenario and its jobs are loaded into MxVDev and all the results are displayed as if the Scenario had just run.

When you compile a Visual Studio solution, a build log is created. When you build a SUT file associated with an MxVMC, the build log is written to the SUT subfolder inside the project folder. For example:

C:\Users\Documents\MxSuiteSamples\TurnDoorSample\SUT\MxVTarget.buildlog.txt

Installation errors are logged in a version-specific log file in this format:

MicroMax_MxSuite_<version>_<date and time>.log

For example:

\MicroMax_MxSuite_3.40.3.44034_(x86)_20190116172015.log

This installation log is saved in this folder:

C:\users\<username>\AppData\Local\Temp