MCXShape is the tool used to configure the software application for downloading in the MCX
programmable control.
You can use this configuration tool to define the model of MCX, the structure of the user interface
menu, the default values for each parameter, the alarms set and actions, the I/O configuration, the
interface languages and much more.
Moreover, by using MCXShape you can compile the software application, execute the Simulator
software and download the software application in the MCX controller via serial communication or
by copying it to the MyK memory (see MMIMYK Programming module – 080G0073).
Note that when MCXShape is used within the MCXDesign environment, some functionalities may be
hidden.
to print all of the project data (Variable List), the parameters with or without the Modbus address,
Input/Output configuration, alarms, status variables, enumerations (an enumeration is a string
associated with the value of a parameter, e.g. NO=0, YES=1)
Print Enum List:
For an explanation of the Enumeration elements listed in the UNIT column of a Print Report, you can
use the report generated by Print Enum List.
See, for example, E nu m 11 in the two images below where the first has been generated with the Print
Parameter List command.
The merge function is useful for importing a parameter configuration from an old MCXS file into a
new one.
The merge function is most commonly used to import a configuration already set for one application
into the configuration file of the newest version of the application.
The procedure for using the merge function is as follows:
• Open the new MCXS file.
• Verify the name filed in the application data: it must be the same for both new and old files.
•Select the merge function from the File menu and set the appropriate merge options as necessary.
Using the default basic options, the parameter values of the old file will overwrite the parameter
values of the new file. Usually this is all that you need to do. However, in the Merge Options you
can select other attributes for merging:
Level:
to import the access level for menus and parameters from the old file
Enabled:
to import the “enabled” attribute from the old file
Visibility:
to import the visibility conditions from the old file
RW or Read Only:
to import the R/W attribute from the old file
Modbus Address (in development):
to import the Modbus addresses from the old file and maintain compatibility with other devices
which refer to these addresses.
The descriptions of the parameters remain the same in the new file unless one of the advanced
options is selected. These can be used to import the following from the old file: the menu dictionary,
the parameters dictionary, the alarms dictionary, the strings dictionary and the I/O dictionary.
NOTE: Select these options only if you want to overwrite the descriptions in the new file with the
descriptions from the old file (not recommended).
• Click on the “Load File…” button to select the old file and then click on the Apply button.:
The View menu is useful for customising the way data appears in MCXShape.
Show/Hide column..:
to select a column to display. This is enabled only when the Menu & Parameters tab is selected
Show multilanguage columns:
to enable/disable the visualisation of the multilanguage columns on the right side of the workbench
Show unused params grayed out:
to grey out parameters not used and simplify the visualisation. Parameters are not used when their
visibility condition are not true or when the related functionality is not enabled.
Hide unused params:
to hide parameters not used and simplify the visualisation. Parameters are not used when their
visibility condition is not true or when the related functionality is not enabled.
Show locked parameters:
to highlight special parameters
Show compile result:
to show the report at the end of the compiling process. In this report you can find the used and
available value for each type of memory.
Enable developer mode: to enable the viusalization of advanced menu for developers (hereafter
“advanced”).
Launch MyK Manager to start the MyK Manager tool (see the MyKManager Manual).
5.2 Edit languages (advanded)
This is used to manage project languages. Here you can define the font for each language (advanced),
change the order of the languages using the Up and Down buttons and add a new language or
remove an existing one.
The available font files are in your project’s bin folder; for each font there are a couple of files with BIN
and DEF extensions. The structure of the font file name is font_XX, where XX = WE for Western
Europe, EE for Eastern Europe, RU for Russia etc.
For each language you must specify the name of the .BIN font file to be used. A .DEF file name can be
omitted if equal to .BIN.
This is used to import the application vocabulary from the special Excel file used for the translation.
The Excel file will have been created previously by the Export language file option.
5.4 Export language file…
This is used to export all the application vocabulary of the selected languages in an Excel file. This
option is used to facilitate the translation of all the strings present in the user interface of the
application.
A pop-up window allows you to select the language you want to export:
Here is an example of the .XLS file that is generated:
To the right of each language you can find a number representing the number of characters still
available before reaching the maximum number generally allowed by standard applications. This is
only a guide, as the effective number is defined by the application and may change accordingly. The
number is typically 21 characters (1 line on the MMIGRS2 user interface) for menus and 42 characters
(2 lines) for parameters and alarms.