In reply to TreyB:

Trey, migrating displays is going to cost something. as you are finding out, you will have significant effort to figure out how to get it all done and be left with a manageable display library/database. I mean, you could simply migrate your displays and publish them as is, and only fix what did not migrate. But then you won't have the benefits of the Standards and Functions in the library for consistency, and all disconnected GEM items. And you will still have end of line alignment issues as each line is migrated independently, and not connected to the end of the next segment. Etc. Etc.

So if you can figure out what your In house cost is, figuring that this is not your primary function, and you don't know what you don't know, you can define this cost as a bench mark. Then if you go for a services quote, you have something to compare. I don't yet know what an Emerson migrated display will look like, but if I were you, I would ask for Quote, get details of exactly what Emerson will deliver, and maybe ask for an example display for them to migrate. They have dedicated resources that do display migrations for a living. You should not be able to do better. ( that's my expectation, may not be reality).

Anyway, the XML file is located in DeltaV/DVData/Graphics-iFix/Local and is called DynamoCrossReference.XML. here is an example:

-<DeltaVDynamo Name="HP_MA1_CH_">
-<DeltaVLiveGem>
<Value>HP_MA1_CH_</Value>
</DeltaVLiveGem>
</DeltaVDynamo>

As you look through this file, you'll see that other Dynamos are mapped to the high Performance Gems. As you migrate, you can align various Dynamos to use the new multipurpose GEM's.

There is a second file called DynamoCrossReferenceAddition.XML, which is empty. Not sure if it is intended for additional custom replacement. Here is what I would try. In a test display, add some of your Dynamos that are not in this file. (and some that are). find a defined mapping that uses the GEM you would like to replace the Dynamo with, Copy and past this to the end of the file and modify the Dynamo name to match your dynamo. Run the tool and see if you dynamo was replaced.

Then, in the ...Additional.xml file, copy in the same text. Note that all the phrases in the first file are under an overarching <DeltaVDynamoCrossReference> …..</DeltaVDynamoCrossReference> syntax.


<DeltaVDynamoCrossReference>
:
:
- <DeltaVDynamo Name="HP_MA1_CH_">
- <DeltaVLiveGem>
<Value>HP_MA1_CH_</Value>
</DeltaVLiveGem>
</DeltaVDynamo>
:
:
</DeltaVDynamoCrossReference>

I don't know if you need to use the following or not.
<DeltaVDynamoCrossReferenceAddition>
- <DeltaVDynamo Name="HP_MA1_CH_">
- <DeltaVLiveGem>
<Value>HP_MA1_CH_</Value>
</DeltaVLiveGem>
</DeltaVDynamo>
</DeltaVDynamoCrossReferenceAddition>

I'm thinking the Additional file is for your customizations. If you modify DynamoCrossReference.xml, this gets overridden? It may be easier to keep/save your custom mappings separately.
I'd give it a try and if the Additional file works, use that for organization. If not, and you find adding the new mappings to the existing file works better, do that.

That's should get your Dynamos replaced.

When I dug into this, there was some prechecking of dynamo structure for the frs_variables and Information variables. if not found in the group, it was not a supported DeltaV dynamo. For these, I would fix in Graphics Studio rather than try to fix in Operate. If you have to touch a display, better to do it in Graphics Studio.

Good luck.

Andre Dicaire