The standard exports and imports functions store configuration data in an .fhx file. Typically, you do not need to edit an .fhx file. Use the standard exports and imports functions to store or transfer configuration data. For example, you can export configuration data and then import it into another system.
Press the F5 key after an import to refresh DeltaV Explorer.
If you are reinstalling or upgrading DeltaV software on a system, you can export that system's configuration and then import the configuration to that system again. When exporting and importing the entire DeltaV system for an upgrade or reinstall, select the Include the data for a DeltaV software upgrade check box on the Export and Import dialogs so the DeltaV Upgrade Wizard can save and restore the following user-defined information:
custom engineering units
version history
recipe authorization history
download history
fieldbus device commissioning
alarm priorities
merging behavior on named sets
The commissioning status of fieldbus devices can also be retained when exporting and importing a partial configuration.
Standard exports and imports do not save history information.
If you are exporting and importing to move or merge configuration information, you do not need to select the Include the data for a DeltaV software upgrade check box.
Use standard exports as part of a system backup procedure. You can create standard export files of the entire configuration database, for an individual module, or at any level in between.
When importing modules, the values of parameters in the function block template definitions in the library can change depending on how you perform the import. Changes to the function block templates do not propagate to existing modules in the library or in areas.
For example:
In Control Studio, create a module that includes an AI block.
Save the module as AI_TEST.
From DeltaV Explorer, export the module to an FHX file.
Delete the module AI_TEST from the database.
Change the value of a parameter (for example, OUT) in the AI function block template in the library.
From DeltaV Explorer, import the FHX file containing the module AI_TEST.
A dialog appears asking if you want to update the existing AI object in the database (that is, the AI function block template in the library) with the AI block that is in the file you are importing.
If you click Yes, the AI block function block template in the library is replaced with the AI block from the import file.
If you click No, the AI function block template in the library will not be replaced.
The module AI_TEST retains its AI block parameter values (as defined in the FHX) in either import case.
The standard import and export functions are available using the following DeltaV Explorer commands:
To export, you can also right-click an object in the DeltaV Explorer hierarchy, and then click Export from the context menu.
The DeltaV Explorer also support drag and drop exports and imports. You can drag an item from DeltaV Explorer onto an application (for example, Windows Explorer, Microsoft Excel, Microsoft Outlook, Notepad, Desktop, Microsoft Word). This causes the item to be exported and then opened by or attached to the application, depending on how the application behaves. Dragging an FHX file to the highest level of the tree in DeltaV Explorer causes the file to be imported.
Exports do not include the OPC UA server endpoint URL information. To reconstruct the URL, you can use the node's information in this format: protocol://machine:port/path. For example, opc.tcp://192.168.1.2:4880/DVOpcUaServer (where 192.168.1.2 is the node's IP address. For workstation-based OPC UA servers, the hostname (the node's computer name) is valid in place of the IP address).
When importing a configuration, a message may appear stating that the database already contains an object with the same name. This message includes the following buttons:
Yes – update the currently importing item which already exists in the database (if their timestamps are not identical).
Yes to all – imports all items, updating those that already exist in the database (if their timestamps are not identical).
No – does not update the currently importing item.
No to all – does not import any items which already exist in the database.
However, there are certain objects that are always imported (or force updated) from the .fhx file. The force update list includes the following objects:
Alarm Priority
Alarm Type
Asset Server
Batch System Server
Device Manufacturer
Device Net Device Revision
Electronic Signatures (if online update)
Engineering Units (if online update)
Fieldbus Device Type
Field Security
Function Block (if online update and the block is primitive)
Function Security
Group
Lock
Named Sets (if not a fixed set)
Parameter Security
Plant Area (if online upgrade)
Profibus Device Revision (if no devices of that type exist in the database)
SIS Field Security
SIS Function Security
SIS Parameter Security
SIS Alarm Type
SIS Named Sets (if not a fixed set)
SIS Lock
User
If VCAT is enabled, this can result in import log errors where the system was not able to overwrite library items that were not checked out. To recover, run sync-database after importing.
When importing a database, any duplicate equipment IDs are renumbered. The equipment being imported is what gets renumbered. If two or more users are working concurrently on the same database, segment the equipment into specific IDs (for example, all tanks get 0-99, all agitators get 101-199, and so on). Then, when you combine the databases through an import, all of the equipment will retain the correct IDs, and your logic will reference the correct IDs.