This step is also demoed with this video :

(ongoing...)

Scope of the tutorial

This step in video : https://youtu.be/E_aBLpDPT6Q (it might be more convenient to copy/paste this link in your usual internet explorer).

The tutorial is based upon a classical Simulink model performing control :

• • with two inputs direction 1 and direction 2

  • the aim of the model is to control the 2 degrees of freedom yaw rate and lateral acceleration of a solid

  • thanks to commands u(yaw rate) and u(lateral acceleration)

  • and measurements yaw rate/lateral acceleration coming from both analog and can technologies

Here is the Simulink model :

MecaTroniX has its Graphical User Interface (GUI) available by typing * mtx_gui* :

There are mainly two zones :

• • Views zone : it enables to switch the view between the 3 standards MODULES, ASSEMBLIES, ARCHITECTURES

  • Functionalities zone :

All functionalities of MecaTroniX are available in this zone :

At the top of the GUI, there are 3 text fields :

• • MecaTroniX : it shows the version currently running

  • ACTIVE SERVER : this is the access to the active server if any. This is used for Community functionalities (see step 6)

  • USER LOCATION : this location is the MecaTroniX location dedicated to the user. It is located in the userpath Matlab definition. _TEST means that a TUTORIAL session is ongoing, as well as the green color of the TUTO button (grey otherwise).

At this location there are following folders :

• 1. folders 'Modules' and 'Assemblies' are dedicated to modules and assemblies (see step 0 and step 1)

  2. folder 'Impexport' is the import/export folder for sharing between users : see step 6 about Community functionalities

  3. folder 'RecycleBin' enables the user to recover some deleted elements

  4. folder 'Sources' : this folder is reserved for user code. This folder is in the Matlab path.

Note that tutorial session uses a specific context indepedantly of the user work context.

It is used to demonstrate functionalities of the tool and to enable the user to practise.

As a result, creations possibly made during tutorial session are not devoted to be maintained, and will be deleted when the user changes the step or quit the tutorial session.

Usually, step N installs what has to be achieved at step N-1.

How does MecaTroniX GUI work? This main GUI

enables the user to reach the targetted object (a module, an assembly, an architecture), and to execute the requested functionality on it (creation, removal, etc...), usually by pressing a button.

Buttons are enabled or disabled depending on the selection.

Once an action is possible and requested by pressing a button, usually a rank 2 GUI opens to complete the required datas. As an example, if the user creates a family of modules, MecaTroniX needs to know its name and its comment, this is the purpose of the rank 2 GUI :

Once the required informations are entered, the user can execute the action by pressing the Valid button or cancel it by pressing the Cancel button.

Most of the time, there is an Informations zone. It contains informations about the current action, such as impossibilities, wrong inputs, etc... but also acknowledgments when the action is completed.

Then, it might be useful in some cases to investigate the message displayed in the Informations zone. For that purpose, pushbutton Publish informations publishes this content in the Matlab Web Browser, for example :

To achieve the user requested action, it can take time for MecaTroniX. As any other task performed by Matlab, Matlab is then busy. This is indicated at the bottom of the Matlab Command Window :

In the same way, the MecaTroniX GUI or any rank 2 GUI has its Busy led ON while processing.

Moreover and during that time, user interface are disabled to avoid confusion :

It stays disabled until the rank 2 GUI is closed.

Depending on the executed action, there may be a progression indicator :

(use of progression indicator is deploying)

MecaTroniX is not garanteed bug free. We are sorry for inconvenience if it occurs. In case of bugs, this window pops up :

A bug report file is then associated to the bug. We would be grateful if user could send it back to MecaTroniX : info@mecatronixe.com

MecaTroniX may be named further by its short name MTX.

Important remark about MecaTroniX : this tool offers functionalities on Matlab/Simulink use. Hence, modules architectures or assemblies can still be used independently and without MecaTroniX.

We've seen the functionalities table :

Before going through these functionalities, it might be useful to define more precisely what is expected as a module, an assembly and an architecture for a Simulink model. This is the purpose of next step III.

Published with MATLAB® R2013a