Overview
The node of a system project the objects that are contained in a compatible export file (.xpt).
command lets you add to theThe software may modify the attribute values of imported objects in some cases. Existing objects of the target system project are not impacted.
Software Version Compatibility
You may be able to import a topology export file in a later version of Control Expert. For details, refer to the topic describing the upward compatibility.
DTM Requirements
You can import a device, which is configured by using a device type manager (DTM) even if the DTM is not present in the of the target system project. However, you cannot open the DTM.
Import Settings
You can select the strategy that the software applies to create objects that you are importing.
Keep relative folder organization |
Result |
---|---|
Yes |
The hierarchy of objects (folder structure) as it is contained in the export file is recreated. The parent folder of this hierarchy is the folder from which you select the command. |
No |
The devices contained in the export file are imported without the original folder structure into the folder from which you select the command. |
Importing PACs
The table describes the impact on the data associated to an exported PAC when you import it.
Associated data |
Result |
---|---|
Control project |
The control project is imported. If the build state of the control project was , it is set to ; otherwise, the state is unchanged.The build target is unchanged. |
Communication mapping |
Communication mapping is recreated for scanned devices that are exported and imported together with the PAC. |
Impact on Attributes When Importing Objects
The objects contained in the export file are created in the topology of the target system project with the same configuration. Existing objects are not impacted.
In some scenarios however, the software may modify the value of certain attributes of imported objects.
The table describes the impact on attributes of imported objects depending on the scenario.
Attribute of Imported object |
Object in the target system project |
Result |
|
---|---|---|---|
Folder name |
A folder with the same name already exists for the same parent folder. |
The folder is renamed(1). |
|
Device and/or module name |
A device/module with the same name already exists. |
The device is renamed(1). |
|
I/O profile of imported device |
A profile attribute with the same name already exists. |
I/O profile attribute name is renamed(1). |
|
Logical network and IP addresses of imported device |
Import in the same system project |
A logical network with the same name already exists. |
The logical network is kept and IP addresses(2) are recalculated if already used. NOTE:
|
A logical network with the same name does not exist. |
The import does not create logical networks. The logical network is set to NOCONF and IP addresses(2) are kept. |
||
Imported in a different system project |
The logical network is set to NOCONF and IP addresses are kept. |
||
|
Import in the same system project |
The attribute value is unchanged unless the configured DHCP server does not exist anymore when the device is pasted. When import several devices between which a DHCP client/server relationship exists, the relationship is maintained. |
|
Imported in a different system project |
The attribute value is set to None. When you import several devices between which a DHCP client/server relationship exists, the relationship is maintained. |
||
Name of physical view in which imported devices appear |
A physical view with the same name already exists. |
The physical view is renamed(1). |
|
(1) To satisfy the name uniqueness rule, the software adds a _x suffix where x is an integer starting at 1 or increments existing _x suffixes. (2) Does not apply to IP addresses that correspond to the gateway address of the logical network (for example, IP addresses of ports whose routing capability is enabled (interface)). These IP addresses and the logical network are set to 0.0.0.0 and NOCONF respectively. |
Importing Objects
To import the content of a topology export file into a system project, proceed as follows.
Step |
Action |
---|---|
1 |
Right-click the node or a topology folder in the pane and select .Result: The dialog box opens. |
2 |
Select a topology export file (.xpt). |
3 |
Click .Result: A dialog box opens prompting you to select import settings. NOTE:
The dialog box opens even if the export file contains no folder structure. Closing the dialog box cancels the import operation. NOTE: If the topology export file was exported
from a password-protected system project, you must enter the system project password when prompted. Otherwise, you cannot import the file.
|
4 |
Select an import setting. Result: The software imports the contents of the export file in the topology of the system project. NOTE: You can see a list of devices and physical
views that have been imported by double-clicking the entry that corresponds
to the import operation in the notification pane.
|