We have a simulator system which has the exact same control modules as the real system (other than the simulation loop-back configuration modules). The two systems have different pro+ server names so exporting from one and importing into another (with FHX files) does not work. I have tried patching the pro+ server name in the FHX file, but that does not work either.
The transfer has been accomplished in the past, but I was not involved at that time and do not know how it was done. Has anyone done this? Can you offer any tips on how to do this?
Sandy, I just did this last week (and have done this many, many times). The FHX file doesn't care what your Pro+ name is when importing modules. If you try to import the entire system it will give you errors on the licenses and the Pro+, but it will import the modules. Check your log file for the actual problem.
In reply to kdculb:
Thanks. I was intuitely thinking it should be that easy.....I will give it a try.....
In reply to Sandy:
Keep in mind that if you import the entire database and overwrite the Proplus (with a different name), you will need to run workstation configuration and select "Create Proplus" after importing.
A few other notes;
If you run a Simulate Convert to remove references to external I/O and you import and overwrite modules, you may have to run a convert again for the simulation tie-back modules to function (this depends entirely on how your simulation environment was created).
If prompted to import "site" I would probably select No. If this is a multi-node simulate system and you import "site" you may have to modify the SystemID in the registry of other simulate stations for them to connect to the database.
It probably goes without saying, but if the simulator is at a later version of DeltaV than the live system, you will need to migrate the configuration prior to import.
Regards,
Brock
Brock P.
In reply to DeltaCisco:
We have the database broken down into Areas, a manageable number which contain the control modules of interest. Will I save myself some work by exporting and importing Area-by-Area? And not importing the part of the database which contains workstations, I/O, etc.
If you use custom Named Sets or Engineering Units you will need to import these first or modules that use them will not import.