Support MES Model & Refactor® (MoRe)

What is MoRe?

MES Model & Refactor® (MoRe) is a productivity tool that makes modeling with MATLAB Simulink® faster, easier and less error-prone. MoRe supports users by simplifying and accelerating model editing and reducing monotonous work steps. The tool facilitates the modeling process as a whole, in particular the refactoring of models.

What's New?

Highlights in MES Model & Refactor® (MoRe) v.1.4

Usability improvements include a hook function to set block parameters for blocks generated by MoRe precisely, significant runtime acceleration for partition actions, support of branched signals when jumping to signal usage destinations, and the cleaning up of unconnected signal lines after break/merge subsystem actions.


MoRe v.1.3

Highlights in MES Model & Refactor® (MoRe) v.1.3

More actions for port blocks and signal lines
New actions "Arrange Port Blocks" and "Convert Goto/Froms to Lines" are available.

Improved handling of signal line parameters on "Add Cross-Hierarchy Signal" action

MoRe v.1.2

Highlights in MES Model & Refactor® (MoRe) v.1.2

Extended TargetLink support
Route cross-hierarchy signals into and out of TargetLink subsystems. Automatic guideline-compliant use of TargetLink port blocks. Ability to also move TargetLink simulation blocks within the subsystem hierarchy.

MoRe v.1.1

Highlights in MES Model & Refactor® (MoRe) v.1.1

Advances in usability and runtime
Dialog alignments are optimized to reduce obstruction of views. Reduced runtime of typical actions.

Improved drawing of branched signal lines


System Requirements

The following system requirements must be in place to use MES MoRe:

  • Windows (XP, Vista, Windows 7+8+10 - 32 and 64-bit versions)
  • MATLAB® R2012b ... R2020a
  • Simulink

Update to the Latest Version

  • If you added a call to init_MoRe to your startup.m and used a folder with version postfix (e.g. x:\project\matlab\MES_MoRe_1_2), then please update the call to the folder of the new installation (e.g. run('C:\Program Files\MES_MoRe_1_4\MoRe\init_MoRe');
  • If you installed the old version to a folder with version postfix (e.g. x:\project\matlab\MES_MoRe_1_2), you can keep that directory as a backup.
  • If you installed without version postfix, you could rename the old installation directory to one with version postfix as a backup.
  • Then proceed according to the installation instructions given below (including license configuration).


  • Extract the MES MoRe zip file (e.g. into a target folder with write access. Suggestions:
    • C:\Program Files\MES_MoRe
    • %MATLAB_ROOT%\toolbox\MES_MoRe_1_4
    • %MATLAB_ROOT%\toolbox\MES_MoRe
    • x:\project\matlab\MES_MoRe_1_4
    Please keep all the subdirectories.

  • For permament installation (recommended):
    • Add a call to the MoRe\init_MoRe.m script from the target folder to your MATLAB startup.m file. Example call: run('C:\Program Files\MES_MoRe\MoRe\init_MoRe');
      Please make sure that there is no call to init_MoRe of an old installation left!
      If you are not sure whether you have any startup.m file yet, type which startup.m in MATLAB command line.
      If result is not empty, add the call from above to this file.
      If result is empty, create a new startup.m file in your userpath. Type userpath in MATLAB command line to get your userpath. Add the call from above to the newly created file (type also doc startup in MATLAB command line for help).
    • Restart MATLAB. There should be an MES MoRe menu entry in Simulink now.
  • For temporary usage (not recommended):
    • Call init_MoRe from the MoRe subfolder of the target folder in the MATLAB command line. This might throw warnings like 'Objects of XXX class exist - not clearing java', if other tools are holding locked references to java objects. In that case, please follow the instructions for permanent installation above.
  • (Optional) Some actions from the 'Analyze' submenu require Graphviz to be installed:
    • Download and install Graphviz from
    • Add the folder containing the dot.exe of Graphviz to the PATH environment variable of Windows (e.g. C:\Program Files (x86)\Graphviz 2.28\bin).

Quick start

Starting MoRe

  • After installation, "MES MoRe" is available as a separate entry in the Simulink menu and context menu. It does not need to be started manually.

Starting an Analysis

  • Open a demo model by typing “fuelsys” in the MATLAB command prompt
  • Select the two subsystems on the root level of the fuelsys model
  • Click “MES MoRe” in the Simulink menu and then select "Merge Subsystems"
  • To undo the action, select "Undo" from the “MES MoRe” menu


If you have any suggestions to help us improve MES Model & Refactor, please do not hesitate to contact us:

MoRe Videos


User Guide

MXRAY User Guide

The MES User Guide presents clear instructions on how to work with MES Model & Refactor® (MoRe). It provides users with information about getting started and working with MoRe.
Click on “MES MoRe”->”Help”->”Documentation” to find a description of all actions available in MoRe (see image).

Release Notes - MoRe v.1.4 (July 2020)

New hook function for setting block parameters

  • With the new hook function MoRe_hook_BlockParameters.m, parameters for blocks created by MoRe can be set more precisely than with the MoRe.ini config file. For example, the color of all created inport blocks can be set in this file.
  • The parameters set via this function have priority over the general block parameters from the MoRe.ini config file.
  • The MoRe_hook_BlockParameters.m function is located in the hooks folder and can be freely extended according to the documentation in the file.

Other Improvements

  • The configuration file ('MoRe.ini') can now be accessed directly via a new entry in the MoRe menu under the category 'Preferences & Help'.
  • All "Partition" Actions (Move Blocks Up/Down, Split Subsystem, Merge Subsystems, Create/Break Subsystem): The runtime of the actions for large subsystems has been significantly reduced.
  • Jump to Usage Destinations: The action can now also be applied if the selected signal line is branched.
  • Break and Merge Subsystem: If a subsystem that is broken up using "Break Susbystem" or merged into another subsystem using "Merge Subsystem" is externally connected to signal lines, but these lines are not connected to other blocks in the subsystem, these lines are automatically deleted when the action is applied.

Bug Fixes

  • All actions that modify or delete signal lines: Fixed a bug that caused certain line parameters to lose their original value after undoing the action. This affected all line parameters that are not stored in the source port, such as 'FontSize' or 'FontAngle'.
  • All actions that modify or delete signal lines: Fixed a bug that in rare cases caused segments of a branching line not to connect properly after undoing the action.
  • All actions that move annotations (e.g. Move Blocks Up/Down, Create Subsystem, Break Subsystem, ...): Fixed bug that caused the undo action to fail when moving two or more annotations with the same name.
  • Arrange Port Blocks: Fixed a bug that caused an error when an outport block was arranged that was connected to an open line.
  • Create Bus: Fixed a bug that caused an error if the signal hierarchy could not be determined for at least one of the selected signal lines.