What is MXAM?
MES Model Examiner® (MXAM) offers fast and reliable guideline compliance verification for Simulink®, Stateflow®, Embedded Coder®, TargetLink®, ASCET®, and Enterprise Architect® models, as well as Excel® data, using general and company-specific modeling guidelines and data rules.
Certified by TÜV SÜD for IEC 61508, ISO 25119, and ISO 26262
Highlights in MES Model Examiner® (MXAM) v.5.0
- Easy setup of a Jenkins-automated MXAM analysis:
Use the batch export function to create a batch file with your current configuration. Load the batch file into the MES Jenkins Plugin to set up an automated Jenkins job.
- Fast overview of differences in reports via the MXAM Report Comparison feature
- 'Fit for Testing' guideline document to help prepare models for testing
The following system requirements must be in place to use MXAM:
- Windows XP (32-bit version)
- Windows Vista, Windows 7, Windows 8, Windows 10 (32-bit and 64-bit versions)
- Web service Port 10117 (default) must be accessible and can be changed in the tool preferences.
- System requirements when using MXAM with MATLAB®/Simulink®/Stateflow®, and TargetLink®:
- MATLAB® version see table below
- TargetLink® (base suite) version see table below
- Port 5564 (default) must be accessible
- System requirements when using MXAM with ASCET: ASCET 6.1 to 6.4.3
- System requirements when using MXAM with EXCEL: Excel 2003 and higher
Compatibility of each MXAM release with MATLAB and TargetLink releases
|MXAM Release||MATLAB Release||TARGETLINK Release|
|5.0||R2011b - R2018a||TL 3.1 - TL 4.3|
|4.7||R2009b - R2017b||TL 3.1 - TL 4.3|
|4.6||R2009b - R2017b||TL 3.1 - TL 4.2|
|4.5||R2009b - R2017a||TL 3.1 - TL 4.2|
|4.4||R2009b - R2017a||TL 3.1 - TL 4.2|
|4.3||R2009b - R2016b||TL 3.1 - TL 4.2|
|4.2||R2009b - R2016b||TL 3.1 - TL 4.2|
|4.1||R2007b - R2016b||TL 2.2 - TL 4.1|
|4.0||R2007b - R2016a||TL 2.2 - TL 4.1|
|3.9||R2007b - R2015b||TL 2.2 - TL 4.1|
|3.8 and 1.9.0||R2007b - R2015b||TL 2.2 - TL 4.1|
Update to the latest version
- If you added MXAM folders permanently to the MATLAB path, please remove all of these folders from the path.
- If you installed the old version in a folder with a version postfix (e.g. x:\project\matlab\mxam_x_x), you can keep that directory as a backup.
- If you installed without a version postfix, you could rename the old installation directory to one with a version postfix as a backup.
Update from MXAM 1 to MXAM Drive
A migration kit to migrate customer-specific checksets and checks is available upon request.
Please contact email@example.com.
- Installer: Install MXAM by executing the setup file (.exe) and follow the setup instructions.
- The startup of the installation process might take a while depending on the security settings of the client machine.
- Installation to a write-protected directory: Right click the setup file and execute as administrator.
- Zip archive: Unzip the archive into any directory
Automatic headless installation
- Run the MXAM installation once on a machine and save your automatic installation data in the Finish Panel to auto-install.xml.
With this data, you will be able to run the same installation on another similar machine.
- Configure the auto-install.xml
- Run the automatic installation: >>[installer-name].exe [ABSOLUTE-PATH/auto-install.xml]
- For MATLAB platform: Open MATLAB, navigate to the MXAM installation directory, and execute >>mxam
- For other platforms: Start MXAM using the program shortcut or go to the MXAM installation directory and execute mxam.exe
Starting an analysis
For MATLAB platform:
- Open a model in MATLAB
- Press "Analyze" in MXAM
- Select the model in the artifact dialog
- Press "Finish"
- Press "Analyze" in MXAM
- Press "Open ASCET" in the artifact dialog if it is not yet open
- Press "Refresh" to fetch models from the database
- Press "Finish"
- In the Project perspective, press "Add..." in the Artifact Section to add an artifact
- Select the artifact and press "Finish"
- Press "Analyze"
- Go to the "Project Guidelines" perspective to see which guidelines will be checked during the analysis.
- To see the pool of all available guidelines, go to the "Library Browser" perspective and select the "Guidelines" view.
If you have any suggestions to help us improve the MES Model Examiner® DRIVE, please do not hesitate to contact us:
The MES User Guide presents clear instructions on how to work with the MES Model Examiner® (MXAM). It provides users with information about getting started and working with MXAM. .
You can easily call the User Guide by clicking on “Help > Help Contents” in the menu (see image).
Release Notes - V5.0.0 27-09-2018
Comprehensive support for the setup of an automated MXAM analysis.
- Simply export your MXAM DRIVE project to a MATLAB script file using the GUI.
- The generated file can directly be executed in MATLAB and uses the batch API of MXAM DRIVE.
- Use these scripts in conjunction with the new MES Jenkins Plugin to easily setup your continuous integration.
- This feature is only available with a Continuous Integration License (CIL).
- For further help, see MXAM DRIVE User Guide > User Interface > Wizards > Export Batch Wizard.
New report comparison checks to compare two MXAM DRIVE reports (BETA).
- Compare two MXAM DRIVE reports according to their structural and semantical equality.
- Differences are analyzed based upon findings, annotations and their guideline documents structure.
- See statistical information about the amount of equal and different findings.
- For further help, see MXAM DRIVE User Guide > Use Case Scenarios > Manage a Project Setup > Perform an MXAM Report Comparison.
- Updated the license module to support parallel execution on the same machine.
Compatibility with MATLAB 2018a
- Minor adjustments to ensure compatibility of framework and checks with MATLAB 2018a.
- Minimum required version of MATLAB is now R2011b.
- Enhanced memory management to enable analysis with larger models. (#6139, #5964, #5889)
- Reduced UI flaws in the document navigation tree when selecting findings. (#5714)
- Updated the ASCET tool adapter to version 220.127.116.11 that supports more precise coordinate information for hierarchy connectors. (#5903)
- Enhanced annotation handling from annotation libraries to reduce the time needed to map them. (#6032)
- Added a new CLI option 'copyDefaultUserDir' that allows to copy settings from the default user directory to a custom user directory.
- Removed public Java API that was previously marked as @Deprecated.
- Enhanced handling of content with obsolete ID information. (#6058)
- Minor improvements of displayed information in the UI. (#6151)
- Fixed that the tool artifacts tab in the artifacts wizard would not appear in certain cases (#6136)
- Fixed the relative paths handling for report names in the project settings and the export report dialog. (#6108)
- Fixed broken links in the MXAM DRIVE Developer Guide. (#6081)
- Fixed possible deadlocks between the customize check parameters and import report dialogs. (#6054)
- Fixed selection states of checks for imported reports that reference the same check multiple times with different selection states. (#6012)
- Fixed a problem where users without sufficient rights could save project settings. (#5882)
- The attempts to unload compiled referenced models after check execution have been prevented. (#5880)
- Added exception handling to the export report dialog in case no report has been opened. (#5792)
- Fixed occurrences of guidelines that have been deleted in the project guidelines view. (#5721)
- Fixed malfunction of filter options in the check parameter dialog. (#5654)