SYSTEM REQUIREMENTS

The following system requirements must be in place to use MXRAY:

  • Windows (XP, Vista, Windows 7+8+10 - 32 and 64-bit versions)
  • MATLAB® R2009b ... R2016b
  • Simulink and Stateflow, depending on the models you wish to analyze
  • (Optional) TargetLink V 2.x, 3.x, 4.x (base suite)

UPDATE FROM AN OLDER VERSION

  • You should keep a backup of your old M-XRAY installation (at least if you did some changes to the configuration files).
  • In case you installed the old version to a folder with version postfix (e.g. x:\project\matlab\mxray_3_1) you can keep that directory as it is.
    Important: Remove all entries of the old folder from the Matlab path! Otherwise you could end up with strange behaviour of the new installation which is even hard to debug.
  • In case you installed without version postfix, rename the old installation directory to one with version postfix. If you dont want to use the old installation directory for the new installation, remove all entries of the old folder from the Matab path.
  • Then proceed according to the installation instruction given below (including license configuration). If you use the previous installation folder, you do not have to include the 'mxray' directory in your Matlab path again.

INSTALLATION

  • Extract the MXRAY zip file (e.g. mxray_3_1.zip) into a target folder with write access. Suggestions:
    • %MATLAB_ROOT%\toolbox\mxray_3_1
    • %MATLAB_ROOT%\toolbox\mxray
    • C:\Programme\mxray
    • x:\project\matlab\mxray_3_1
    Please keep all the subdirectories.
  • Use the 'Set Path' dialog of Matlab to add the 'mxray' directory from the target folder (e.g. x:\project\matlab\mxray_3_1\mxray) to your Matlab path (without subfolders). Please check if you correctly added the 'mxray' directory to the Matlab path by typing which('mxray') in the Matlab command prompt which should return the path of the mxray.p file.

LICENSE CONFIGURATION

All license types

You can check the license installation of all license types by launching the MATLAB command mxray_printLicenseInfos() after following the steps below. In case of a successful installation, the license infos are printed without error. You can also use the same command to get the license information of a running M-XRAY instance.

Node-locked license

Copy the license file (.lic) into the 'license' directory of your tool installation. You receive your license file by email from MES or from your admin.

Dongle license

  • Copy the license file (.lic) into the 'license' directory of your tool installation. You receive your license file by email from MES or from your admin.

...

QUICK START

Starting MXRAY

  • Open MATLAB.
  • Type mxray in the command prompt.

If an 'Undefined function' error occurs, please ensure that you added the correct folder to the MATLAB path (see installation instructions above). If a license exception occurs, please ensure that you followed the license configuration instructions above.

Starting an analysis

  • Open a model in MATLAB/Simulink
  • Press 'Add open models' in the MXRAY GUI
  • Press 'Create Report' in the MXRAY GUI

Help

The comprehensive user guide (as pdf) and release notes (as txt) are part of the MXRAY zip file (and CD) and are extracted to the directory of tool installation.

Support

If you have any questions or suggestions which can help us to improve MES M-XRAY® please do not hesitate to contact us:

KONTAKTIEREN SIE UNS!
+49 (0) 30 20916463 22
mxray@model-engineers.com


USER GUIDE



RELEASE NOTES

3.4.0 / October 2017

  • Elementary inputs unused listed in HTML report: To supplement the ineffective interface analysis introduced in M-XRAY 3.3, a new 'Ineffective Interface' section was introduced in the HTML report that lists the signal names of the elementary inputs unused. The names can be used to directly start refactoring the subsystem's interface. The new section is linked from the main part so that you can still work in the main table and jump into the details by clicking on and following the linked metric value.
  • Faster analysis:
    Reduced the runtime of the general model analysis and HTML report generation. For a reference model with global complexity of approx. 20000 and all details selected for analysis, the runtime of analysis and HTML report generation has been reduced by approx. 50%.
  • Rework of detailed subsystem quality distributions in HTML report:
    • Changed plots so that distribution bars are centered on the distribution bin. As a result, distributions for small discrete value ranges become clearer (e.g. bars for 'Level' or 'Inport' are now centered on 0, 1, 2 (...) and not on 0.5, 1.5, 2.5 (...)).
    • Changed font size to improve appearance on different browsers and to avoid truncated titles when title gets too long (e.g. 'Detailed distribution of %Elementary Inputs Unused (globally)' was previously truncated).
  • Improved HTML report readability for big models:
    • The library and model references were excluded from the table of contents to keep it readable for models with many references.
    • The maximum column width of the 'Path' and 'Name' columns were limited (with word wrap enforced) to keep the first metric values in the visible range without having to scroll horizontally.

FAQ

Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet.