You can import data from the ETS project to your HS/FS Expert project. The imported data is structured by main group/middle group/subgroup in HS/FS Expert. The folder structure consists of the main and middle groups. The subgroup becomes the name of the communication object.
If no further data types appear in the respective import file, and corresponding data types exist in the HS, the file can be adapted correspondingly.
There are four different options for adopting group addresses. There are corresponding control files for these data imports that are saved in the directory "[expert]\dat".
These control files determine the assignment between HS data type and the import data type.
If no further data types appear in the respective import file, and corresponding data types exist in the HS, the file can be adapted correspondingly.
There are four different options for adopting group addresses. There are corresponding control files for these data imports that are saved in the directory "[expert]\dat".
These control files determine the assignment between HS data type and the import data type.
1.Print file (only from ETS2)
Upon import, a folder structure is automatically created (main group/middle group). To import the data, you must export your ETS project to a print file and read it into HS/FS Expert. During the import, 2 and 3-figure group addresses are automatically taken into account.
Instructions are available for creating the print file.
Instructions are available for creating the print file.
Note
Group addresses from the import file whose data type is not detected are imported with HS data type key '0'!
Implementation of the data types in the control file import.txt
| ETS data type | HS data type key |
|---|---|
| 1 bit | 0 |
| 1 byte | 1 |
| 4 bytes | 9 |
| 14 bytes | 10 |
| 3 bytes (DPT11.001=Date) | 12 |
| 3 bytes (DPT10.001=Time) | 11 |
| 2 bytes | 3 |
| 4-bit | 13 |
| 2-bit | 15 |
2.OPC file (ETS2 and ETS3)
The OPC file can be created with the ETS2 and ETS3. The file contains no central addresses. The ETS export is found in File/Data exchange/Export to OPC server in the ETS3.
Data set structure of a line in the control file:
ETS data type {TAB} HS data type key
Data set structure of a line in the control file:
ETS data type {TAB} HS data type key
Note
Group addresses from the import file whose data type is not detected are imported with HS data type key '0'!
Implementation of the data types in the control file importopc.txt
Note
The complete string entered in the column "ETS data type" is searched for.
| ETS data type | HS data type key |
|---|---|
| EIS 1 'Switching' (1 bit) | 0 |
| (1 bit) | 0 |
| Uncertain (1 byte) | 1 |
| (1 byte) | 1 |
| Uncertain (2 bytes) | 3 |
| (2 bytes) | 3 |
| Uncertain (3 bytes) | 11 |
| (3 bytes) | 11 |
| Uncertain (4 bytes) | 9 |
| (4 bytes) | 9 |
| (14 bytes) | 10 |
| EIS 2 'Dimming - control' (4 bit) | 13 |
| (4 bit) | 13 |
| EIS 8 'Scaling - control' (2 bit) | 15 |
| (2 bit) | 15 |
3.ETS3 HSXML file
A corresponding file can be created with the ETS3F add-in contained in the directory "[Public Documents]\[Company]\HS+FS Expert [VersionNo]\tools\ets3f" and imported into HS/FS Expert.
More information on this add-in can be found in the PDF documentation that is enclosed there.
More information on this add-in can be found in the PDF documentation that is enclosed there.
Note
Group addresses from the import file whose data type is not detected are imported with HS data type key '0' (see lower line in the table "all others"). The "Default" data type can be adapted here.
The mode in this control file specifies how the information on the right is to be read:
1 - HSXML data type assignment (see following table)
2 - DPT data type, if available (see following table)
����� Is used if DPT (in co tag) is specified and the GA tag corresponds to the HSXML data type. Overwrites mode '1' details on the same data type.
7 - Filter: Number of (permitted) CO overruns per device
8 - Filter: Number of (permitted) listening addresses per CO
9 - Specification of the "Default" data type. Applies if a data type occurring in the import file is found neither in the table in mode "1" nor in mode "2".
If "-1" is entered as the default data type, no HS data type is specified at import. This has to be specified manually in Expert later.
Implementation of the data types in the control file importxml.txt
1 - HSXML data type assignment (see following table)
2 - DPT data type, if available (see following table)
����� Is used if DPT (in co tag) is specified and the GA tag corresponds to the HSXML data type. Overwrites mode '1' details on the same data type.
7 - Filter: Number of (permitted) CO overruns per device
8 - Filter: Number of (permitted) listening addresses per CO
9 - Specification of the "Default" data type. Applies if a data type occurring in the import file is found neither in the table in mode "1" nor in mode "2".
If "-1" is entered as the default data type, no HS data type is specified at import. This has to be specified manually in Expert later.
Implementation of the data types in the control file importxml.txt
| Mode | ETS data type | HS data type key |
|---|---|---|
| 1 | 0, 2, 4, 5, 6, 11, 13 | 0 |
| 1 | 1 | 15 |
| 1 | 3 | 13 |
| 1 | 7 | 1 |
| 1 | 8 | 3 |
| 1 | 9 | 11 |
| 1 | 10 | 9 |
| 1 | 12, 14 | 10 |
| ETS data type | ETS data type | ||
|---|---|---|---|
| Mode | HSXML | DPT | HS data type key |
| 2 | 9 | Time | 11 |
| 2 | 9 | Date | 12 |
| Mode | Filter |
|---|---|
| 7 | 0 |
| 8 | 5 |
| Mode | Default data type |
|---|---|
| 9 | 0 |
4.ETS4 project file
All group addresses from an ETS 4 project file can be imported via this menu item.
Note
Group addresses from the import file whose data type is not detected are imported with HS data type key '0' (see lower line in the table "all others"). The "Default" data type can be adapted here.
The mode in this control file specifies how the information on the right is to be read:
1 - HSXML data type assignment (see the following table)
7 - Filter: Number of (permitted) CO overruns per device
8 - Filter: Number of (permitted) listening addresses per CO
9 - Specification of the "Default" data type. Applies if one of the data types occurring in the import file is not found at mode "1" in the table.
If "-1" is entered as the default data type, no HS data type is specified at import. This has to be specified manually in Expert later.
Implementation of the data types in the control file importxml2.txt
1 - HSXML data type assignment (see the following table)
7 - Filter: Number of (permitted) CO overruns per device
8 - Filter: Number of (permitted) listening addresses per CO
9 - Specification of the "Default" data type. Applies if one of the data types occurring in the import file is not found at mode "1" in the table.
If "-1" is entered as the default data type, no HS data type is specified at import. This has to be specified manually in Expert later.
Implementation of the data types in the control file importxml2.txt
| Mode | ETS data type | HS data type key |
|---|---|---|
| 1 | 0, 2, 4, 5, 6, 11, 13 | 0 |
| 1 | 1 | 15 |
| 1 | 3 | 13 |
| 1 | 7 | 1 |
| 1 | 8 | 3 |
| 1 | 9 | 11 |
| 1 | 10 | 9 |
| 1 | 12, 14 | 10 |
| Mode | Filter |
|---|---|
| 7 | 0 |
| 8 | 5 |
| Mode | Default data type |
|---|---|
| 9 | 0 |
5.Import mask
File name
The path and file name of the import file are entered here.
A file selection mask can be opened via the button next to the input field.
A file selection mask can be opened via the button next to the input field.
Project language
For ETS import only.
The ETS project language used in the import file is set here.
In this case the terms for the main, middle and sub-group are defined here.
The automatic folder structure is then generated automatically from this.
The ETS project language used in the import file is set here.
In this case the terms for the main, middle and sub-group are defined here.
The automatic folder structure is then generated automatically from this.
Import central addresses
Not for OPC import.
Yes: Central addresses are imported and created under the associated communication object.
Yes: Central addresses are imported and created under the associated communication object.
Import empty groups
Not for OPC import.
Yes: Group addresses that have no further connection in the ETS project are imported.
Yes: Group addresses that have no further connection in the ETS project are imported.