Emerson Exchange 365

• Not Answered

DeltaV Live runtime layout differs from graphics studio layout

We have a dual monitor layout file that has been in production use for over a year.  This week the layout in the runtime environment is showing up as a quad monitor layout after a graphics refresh was completed.  We have been working on display and GEM updates so the need to refresh doesn't suprise me, however we have not touched the layout files.  Looking in Graphics Studio the layout is still configured as a dual monitor layout, yet shows up as a quad in runtime.  I have verified the correct layout file is assigned to the station.  I tried refresh, as well as reset layout with no change to the runtime layout.  I have assigned a different layout to the station, published, verified the newly assigned layout was correct in both Graphics Studio and Live runtime.  I then reassigned the impacted dual layout, republished again, with no change to the impacted runtime layout (still showing up as a quad).  I have assigned the impacted layout to other dual monitor stations, including the ProPlus, and I am seeing the exact same issue with runtime showing a quad monitor layout, while Graphics Studio shows the layout file as a dual monitor configuration.

I'm wondering if anyone has seen this issue before?  How did you go about resolving the issue?  Do I need to delete the impacted layout and re-create from scratch?

Jesse Delanoy

• 23 Jan 2024 3:15 PM
• Cancel

3 Replies

• Andre Dicaire

  

  • 23 Jan 2024 4:24 PM

  This is likely best handled through the GSC as it sounds like a product issue. They would want to know what Hotfix version you are at and LTS or Feature Pack. If this is a known issue resolved in a later hotfix, you'd will be directed to update to the latest WS hotfix. If you are at this latest Hotfix, they need to know so the issue can be investigated.
  
  I would suggest that you export your affected layout and set this aside in case the GSC wants to look at it. Then I would delete the layout in Graphics studio, or build a new one. Then update the workstations to the new Layout. That appears to be a workable path to get you resolved. As for the root cause, the GSC will need to provide that. Unless someone responds to this thread with the explanation.

  Andre Dicaire

  • Cancel
• Jesse Delanoy

  

  • 23 Jan 2024 6:12 PM

  In reply to Andre Dicaire:

  Thanks for the response Andre.
  
  I just submitted a GSC ticket and walked through the issue and was instructed to un-publish and re-publish the layout file. This corrected the issue, however I didn't get a great response regarding the root cause. From my GSC call it was basically left at something happened to the layout file that corrupted or removed the file from the database. I'm leaning more towards it was corrupted since I tested assigning no layout and it resulted in a blank screen, not a quad layout. I'm make a leap here, but I assume if the layout selection can't be resolved correctly it will behave similar to no layout assigned. Also the layout was not flagged for publish in Graphics Studio when this issue was encountered, which I would expect would be the case if it was deleted from the database (again making a leap as I don't really understand how the comparison between the config and runtime DB atually works when it comes to setting the publish flag). Anyway I guess the fix for future issues is just re-publishing the layout file.

  • Cancel
• Andre Dicaire

  

  • 23 Jan 2024 7:08 PM

  In reply to Jesse Delanoy:

  Thanks for circling back and sharing the unpublish/publish approach. I should have thought of that. So the displays are stored in a local sql database, and when you publish, the runtime HTML5 display is generated. What you see in Graphics studio is the database version. I've never seen a layout grow to a Quad when there is a problem with the layout. I'm seen it default to a single screen with no navigation bar. Anyway, glad you got it resolved.

  Andre Dicaire

  • Cancel