Emerson Exchange 365

Issues with DeltaV Live GEM Instances

Recently we have been seeing lines and connectors within newly developed GEMs shift position when placing instances of the GEM on a new display.  Looking at the configuration properties for the instance there are overrides applied to all of the lines/connectors that shifted.  At the GEM level all of the lines that are shifting are part of the base GEM, not a sub/embedded GEM.  There is no option to add overrides to base GEM elements until an instance exists (or the GEM is embedded within another GEM).  Initially we thought it might be a copy/paste issues during GEM development, so we completely rebuild several GEMs from scratch which did not resolve the issue.  The question is how are these overrides getting applied when dropping an instance of the GEM onto a new display?  We have not seen this issue with past GEM development work.  We have seen numerous other coordinate system issues with DV Live / Graphics Studio such as grouping objects, then ungrouping, and all the lines shift position, but this is a new one.  Any input is appreciated.  This is driving a lot of wasted engineering hours at the moment. 

Jesse Delanoy

• 14 Sep 2023 3:54 PM
• Cancel

2 Replies

• Andre Dicaire

  

  • 14 Sep 2023 7:09 PM

  I've seen the grouping ungrouping thing. When you group a couple of lines, their position information gets redefined relative to the group they are now in. example. A line that starts at the left side of the group will have horizontal value of 0. When you ungroup. It keeps the value in the group, rather than recalculating based on the group position plus relative. The result is the items shift in the new level. I don't know if this is marked for being fixed.
  
  As for random Overrides, I have not seen. have you filed a CTS call? Can you reproduce this? Wondering if you copy to a new GEM, does the issue follow? Can you simplify the GEM (or copy) so that you can export. Then you could look at the XML file and see if there is some "extra" definition that is not there on a new one, If so, you might be able to "fix" the XML and re-import. If you can simplify a GEM to reproduce, it will also help GSC to reproduce. But the way I see it, if the issue is being preserved in the XML export to send to GSC, then we should be able to see the "anomaly". I'm really guessing here in trying to offer something to look at.

  Andre Dicaire

  • Cancel
• Jesse Delanoy

  

  • 15 Sep 2023 3:03 PM

  In reply to Andre Dicaire:

  Thanks for the info Andre. I think we figured out what is happening. The GEMs we have been building have embedded GEMs (valves) with overrides to rotate the orientation. When we hook a line or connector to the embedded GEM connection points it appears the override is calculated based on the embedded GEMs non-overridden position. The calculated overrides are not accurate when the line, or connector end points are all hooked. It appears based on our limited testing that leaving some of the end points disconnected resolves this issue. We will be submitted a GSC request for this issue.

  • Cancel