General settings

mapp Services V5.16

•Show advanced parameter

Name
	General
		Program Device Name
		Sign Programs
			Passphrase
		Sign Macros
			Passphrase

General settings are defined in section "General".

"Program device name" defines the data storage device that contains the programs that are executed at runtime. The data storage device must already be defined in the target system configuration.

Interaction with the storage medium, such as deleting or importing programs, must always take place using function block MpCodeBoxManager. For additional information, see here.

filedevice

Programs and macros can be protected with "Sign programs" and "Sign macros". "Sign XXX" must be set to "Required" for this. "Passphrase" is the specification of the key used to sign the file. SHA256-HMAC is used for the encoding. The user cannot independently decrypt the file. "PassPhrase" is only needed to provide the application developer with the possibility of affecting the degree of security. "PassPhrase" must be changed in order to ensure encryption takes places sensibly.

The signature is automatically added to the file as soon as a program or macro file is created with widget "LadderEditor". The files are checked using "Sign XXX = Required". If the files are valid, they can be used. Errors occur in the following cases:

•If a faulty program is found at startup, this will generate a logbook error entry and the program will not appear in the list of existing programs.

•If an invalid signature is found during the import, error "Program invalid" is displayed on function block MpCodeBoxCore.

•If an invalid signature is found while loading a program, error "Signature for import is incorrect" is sent to widget "LadderEditor". The error is made visible with action "OnError".

•If an invalid signature is determined at startup, MpCodeBoxCore displays error "Program start failed". For more information, see the Logger.

With "Sign XXX = Required", all adjustments and changes to the files must be made using widget "LadderEditor".

Specifying texts localized using the text system

The texts in mapp Codebox can be specified as localized via the text system. The texts are displayed in widget "LadderEditor". For example, the following texts can be displayed localized:

localizedtext_example

The Automation Studio text system is used to localize texts. The text is not specified directly; instead, it is linked to the text system. Some texts are predefined for widget "LadderEditor" and can be used immediately. For more information, see here.

Arguments and macros can be specified as localized via the mapp CodeBox configuration. The target system must be linked to for this purpose.

A file containing the actual macro and argument texts was added in the Logical View beforehand. This file contains the text in each project language. The connection between the text system and mapp CodeBox is established using the namespace and text ID of the text. The namespace and the text ID are defined directly via the text file.

The namespace of the text file must begin with "IAT/xxx"! For example, the namespace "IAT/MacroTexts" or "IAT/ArgumentTexts" can be used.

localizedtext_projectlanguage

Fig.: Project languages to be used

localizedtext_config_tmx

Fig.: Connection between configuration and TMX file

The namespace of the text file is defined by parameter "Macro namespace" or "Argument namespace". It is important to enable the extended parameters to use "Macro namespace" or "Argument namespace"!

The text ID is defined by the name of the argument or macro. This means that the name of the text ID and the name of the Argument/Macro must match:

localizedtext_config_tmx_textids