Exchange via Microsoft Excel®

The XLSX file must have a specific structure so that it can be used in the Project Builder.

To assign the contents of an XLSX file to the configuration variables, Macro-Typicals and Typical-Groups available in the Project Builder, the internal name of the corresponding element must be available in the XLSX file. If a translated display name is available, it is therefore supplemented with the technically required, model-internal name. The model-internal name is enveloped by braces { }. If no translated displayed names are available for an element, these braces are not used.

Example: Internal name and translated displayed names of a configuration variable

The configuration variable with your internal name Var01 and the field for the displayed name are shown here:

The representation of the internal name and the translated displayed name of the configuration variable in an XLSX file are shown here:

	A	B
1	*
2	`Display name of Var01 {Var01}`	`Value`
3

* The Cell A1 of an XLSX file is reserved for the information of the configurator element.

Notes

Only the first worksheet of an XLSX workbook is considered during a data exchange.

Tip:

During a data exchange via XLSX files braces { } in the displayed names as well as entries in the selection lists of configuration variables should not be used, since the required uniqueness can otherwise not be guaranteed during the import.

Example: Configurators and elements

Here you see the definition of a configurator with the name Configurator in the Designer consisting of two configuration elements, Element 1 and Element 2:

Here you see the representation in the Project Builder:

Here you see the export result of an XLSX file of the configuration element Element 1:

	A	B
1	`Element 1`
2	`Display name of Var01 {Var01}`	`Value`
3	`Display name of Var02 {Var02}`	`Value`
4	`Display name of Var03 {Var03}`	`Value`

Notes

A configurator element must only be specified during the usage of the silent mode. During a manual import of an XLSX file in the Project Builder this is irrelevant. The contents of Cell A1 in the XLSX file are not checked in this use case.

Tip:

A structurally correct XLSX file of a configuration element is generated easiest by using the Export *.xlsx function from the Project Builder.

Information about the superordinate configuration variables follows as of Row 2 of the XLSX file. Column A contains the name, and Column B the value for a specific configuration variable. The exact designation of the configuration variable must be entered as the name. The value to be defined must be available in the variable for selection and match the data type. The sequence of the variables is irrelevant.

Example: Basic structure of an XLSX file (without translated displayed names)

	A	B
1
2	`OP_Measuring_Transformer`	`True`
3	`SE_Light_power`	`True`
4	`SE_Receptacles_power`	`2`
5	`SE_Light_control`	`True`
6	`SE_Receptacles_control`	`2`
7	`OP_Control_panel`	`false`
8	`OP_Panel_Enclosure`	`True`
9	`OP_Panel_Control`	`false`
10	`SE_Drive_Transport`	`Frequency Control`
11	`SE_Method`	`Electric`

Example: Basic structure of an XLSX file (with translated displayed names)

	A	B
1
2	`Option: Measuring transducer {OP_Measuring_Transformer}`	`True`
3	`Lightning, required for enclosure 1 {SE_Light_power}`	`True`
4	`Number of female receptacles required in the enclosure 1 {SE_Receptacles_power}`	`2`
5	`Lightning, required for enclosure 2 {SE_Light_control}`	`True`
6	`Number of female receptacles required in the enclosure 2 {SE_Receptacles_control}`	`2`
7	`Option: Control panel {OP_Control_panel}`	`false`
8	`Option: Panel Enclosure {OP_Panel_Enclosure}`	`True`
9	`Option: Panel Control {OP_Panel_Control}`	`false`
10	`Drive type {SE_Drive_Transport}`	`Frequency Control`
11	`Method {SE_Method}`	`Electric`

Instances and their configuration variables

Instances are introduced with a header. The name of the instantiable Typical is available in Column A, followed by the configuration variables in the subsequent columns. The instantiable elements including their values for the configuration variables stand in the rows below the header. The end of a block of instantiable elements must take place through a blank line.

	A	B	C
1
2
3	`InstanceObject1`	`obj1_parameter1`	`obj1_parameter2`
4	`InstanceObject1`	`Value A`	`Value B`
5	`InstanceObject1`	`Value C`	`Value D`
6
7	`InstanceObject2`	`obj2_parameter1`	`obj2_parameter2`
8	`InstanceObject2`	`Value Y`	`Value Z`
9

Notes

The opening header is only displayed in bold in the table for clarification. In general, formatting has no influence on the processing of an XLSX file through the Project Builder.

Example: Structure of an XLSX file for the configuration of instances (without translated displayed names)

	A	B	C
1
2
3	`Conveyor`	`parameter1`	`parameter2`
4	`Conveyor`	`some string .... 1`	`1.234`
5	`Conveyor`	`some string .... 2`	`5.678`
6	`Conveyor`	`some string .... 3`	`9.012`
7
8	`Enclosure`
9	`Enclosure`
10

Export a configuration as an XLSX file

Click the dropdown list.
Click XLSX file.
Enter the desired name and a storage location for the file to be exported.
Click Save.
The configuration carried out in the Project Builder is exported as an XLSX file.

Import a configuration as an XLSX file

Click the dropdown list.
Click XLSX file.
In your file system select the file to be imported.
Confirm the dialog with Open.
The configurator is enriched with the information from the XLSX file.

Notes

The information in the XLSX file on designation, type and value of a configuration variable must match the elements in the configurator. If the information does not match, a corresponding error message is displayed. If possible, the import is continued despite the error message.
The specifications that were already made in the configurator and which are not contained in the file to be imported, remain in the input mask of the Project Builder even after the import.
Only the first worksheet of an XLSX workbook is considered during an import.

"The Project Builder: Basics"

"Exchange via XML"

"Data exchange: Basics"