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.2.0

New design of menu speeds up modeling. The new menu allows one-click access to frequently used actions. All available actions are categorized in submenus, sorted in descending order of estimated frequency of use.


Easily add new high-level input signals to the current subsystem. You can add new input signals from higher levels without leaving the subsystem you are working on in the editor.



MoRe v.1.4

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



  • 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_2_0
    • %MATLAB_ROOT%\toolbox\MES_MoRe
    • x:\project\matlab\MES_MoRe_2_0
    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).

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_3), then please update the call to the folder of the new installation (e.g. run('C:\Program Files\MES_MoRe_2_0\MoRe\init_MoRe');
  • If you installed the old version to a folder with version postfix (e.g. x:\project\matlab\MES_MoRe_1_3), 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).

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 ... R2019b
  • Simulink

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:

User Instruction

MXRAY User Guide

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).

MoRe Videos


Release Notes - MoRe v.2.0 (October 2020)

New Menu Design

  • The menu has been redesigned to improve clarity while allowing quick access to recently used actions.
  • To improve clarity, the actions are categorized in submenus. They are sorted in descending order of estimated frequency of use.
  • For quick access, a new list at the top of the menu allows you to directly start a recently used action.
      • The most recently used action always appears at the top of this list.
      • The list is kept short by displaying only actions that are applicable to the current selection.
      • The maximum number of list elements can be configured in the MoRe.ini file. The default value is 5.

New Action "Add Input Signal From Higher Level"

  • Use this action to add a new input signal coming from a higher-level (or top-level) subsystem to the current subsystem you are working on. This helps you to focus your work on the current subsystem and connect the new high-level inport to an external signal later. Often these high-level connections are established by additional tools, which automatically generate the highest levels of the model.
  • The dialog remembers the level of the last source system and selects the subsystem on this level as the source at the next start. This speeds up the action if the signals should always come from the same level.
  • The name of the ports and lines to be created is taken from the clipboard when the dialog is started. This speeds up the action if the name was copied elsewhere before.

Other Improvements

  • Rename Signal and Ports: When renaming a signal, the action now updates all dependent propagated signal labels and bus signal names.
  • Remove Cross-Hierarchy Signal Forward: The action now also follows the data flow into atomic subsystems and continues the removal process there. Previously, the process stopped at the inport of an atomic subsystem.
  • Jump to Usage Destinations: When the "Back to Selected Signal" button is selected in the "Usage Places" dialog, the function now also highlights the virtual blocks on the signal path to the selected usage place. Previously, only the lines on the signal path were highlighted.
  • Highlight to all Sources: The action now asks to remove existing highlighting before adding a new one.
  • The hook function file for setting block parameters ('MoRe_hook_BlockParameters.m') can now be accessed directly via a new entry in the MoRe menu under the category 'Preferences'.

Bug Fixes

  • All actions that delete or move signal lines: Fixed a bug that caused the propagated signal label of a line to be empty ('<>') after undoing the action. This only affected lines with activated signal label propagation.
  • All actions that add or redraw lines: Fixed a bug that caused an error when the action created a line where signal label propagation is not possible (e.g. the outgoing line of a bus selector) and signal label propagation was activated in the MoRe.ini config file.
  • Remove Cross-Hierarchy Signal Forward: Fixed a bug that caused the entire bus leaving a bus creator to be deleted when only a single input signal was selected for removal. The error occurred only when the signal was not named at the selected line itself but further ahead in the data flow (e.g. in an upstream subsystem).
  • Remove Cross-Hierarchy Signal Forward: Fixed a bug that, when removing the only sub-signal of a bus, caused the corresponding signal lines and virtual blocks to not be deleted.
  • Jump to Usage Destinations: Fixed a bug that caused no destination blocks to be found when the input signal of a bus creator was selected. The error occurred only when the signal was not named at the selected line itself but further ahead in the data flow (e.g. in an upstream subsystem).
  • Redraw Line: The action now preserves font-specific parameters of the line labels, so that e.g. font sizes and styles remain the same.